Distributed database control for fault tolerant initialization

• US 20030046375A1
• Filed: 01/22/2002
• Published: 03/06/2003
• Est. Priority Date: 08/31/2001
• Status: Abandoned Application

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Parkman, David S., Stephenson, Gary V.
• Application Number:
  US10/054,839
• Publication Number:
  US 20030046375A1
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A network for a mobile platform includes first and second servers that provide first and second services and include a first and second configuration databases, respectively. If both of the first and second servers successfully boot up and complete self-testing, the first and second servers compare the first and second configuration databases. If the first and second configuration databases do not match, one of the first and second configuration databases having an older update date is replaced with the other of the first and second configuration databases having a newer update date. The first server to boot up and complete self-testing is designated a primary server that tracks network status. If the first (or second) server does not boot up and complete self-testing, the second (or first) server performs a subset of the first (or second) service.

Claims

1. A network for a mobile platform, comprising:

a first server that provides a first service and includes a first configuration database;

a second server, connected to said first server, that provides a second service and includes a second configuration database,

wherein when said first and second servers boot up, said first and second servers compare said first and second configuration databases.

2. The network of claim 1 wherein said comparison occurs after boot up and self-testing.

3. The network of claim 1 wherein if said first and second configuration databases do not match, one of said first and second configuration databases having an older update date is replaced with the other of said first and second configuration databases having a newer update date.

4. The network of claim 3 wherein a first of said first and second servers to boot up and complete self-testing is designated a primary server.

5. The network of claim 4 wherein said primary server tracks network status.

6. The network of claim 3 wherein if said first server does not boot up and complete self-testing, said second server performs a subset of said first service.

7. The network of claim 3 wherein if said second server does not boot up and complete self-testing, said first server performs a subset of said second service.

8. The network of claim 1 further comprising:

a third server, connected to said first and second servers, that provides a third service and includes a third configuration database.

9. The network of claim 8 wherein said mobile platform is an aircraft and one of said first, second and third servers is a web server.

10. The network of claim 8 wherein said mobile platform is an aircraft and one of said first, second and third servers is a media server.

11. The network of claim 8 wherein said mobile platform is an aircraft and one of said first, second and third servers is a data transceiver server.

12. A method for initializing a network for a mobile platform, comprising:

connecting first and second servers;

powering on said first and second servers;

providing a first service with said first server that includes a first configuration database;

providing a second service with said second server that includes a second configuration database;

comparing said first and second configuration databases when said first and second servers boot up and complete self-testing.

13. The method of claim 12 further comprising the step of:

if said first and second configuration databases do not match, replacing one of said first and second configuration databases having an older update date with the other of said first and second configuration databases having a newer update date.

14. The method of claim 13 further comprising the step of:

designating a first of said first and second servers to boot up and complete self-testing as a primary server.

15. The method of claim 14 further comprising the step of:

tracking network status using said primary server.

16. The method of claim 12 further comprising the step of:

performing a subset of said first service using said second server if said first server does not boot up and complete self-testing.

17. The method of claim 12 further comprising the step of:

performing a subset of said second service using said first server if said second server does not boot up and complete self-testing.

18. The method of claim 12 further comprising:

connecting a third server to said first and second servers, wherein said third server provides a third service and includes a third configuration database.

19. The method of claim 18 wherein one of said first, second and third servers is a web server.

20. The method of claim 18 wherein one of said first, second and third servers is a media server.

21. The method of claim 18 wherein one of said first, second and third servers is a data transceiver server.