System and method for synchronizing databases

• US 8,170,988 B2
• Filed: 07/14/2008
• Issued: 05/01/2012
• Est. Priority Date: 04/17/2008
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Yukawa, Steven J., Jain, Rajit, Anstey, Tim W.
• Primary Examiner(s): Truong, Cam
• Assistant Examiner(s): Pham, Michael
• Application Number:
  US12/172,792
• Publication Number:
  US 20090265393A1
• Time in Patent Office: 1,387 Days
• Field of Search: 707/622
• US Class Current: 707/622
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A method for synchronizing information shared by a subsystem on-board a mobile platform and a subsystem remote from the mobile platform. The method may involve designating one of the subsystems as a first system having a first database, and designating one of the subsystems as a second system having a second database. The first subsystem may be used to transmit a synchronization request to the second subsystem, with the synchronization request including a synchronization point to be used as a reference for future synchronization operations between the subsystems. The second subsystem may be used to receive the synchronization request and to check the second database for any records that have been created or modified since a previously performed synchronization operation. Information may then be transmitted back to the first subsystem that includes information concerning the new or modified records.

Claims

1. A method for synchronizing information shared by a subsystem on a mobile platform and a subsystem remote from the mobile platform, method comprising:

designating one of the subsystems as a first subsystem having a first database;

designating one of the subsystems as a second subsystem having a second database;

using the first subsystem to transmit a synchronization request to said second subsystem, said synchronization request including a synchronization point to be used as a reference for future synchronization operations between said subsystems;

using said second subsystem to receive said synchronization request and to check said second database for any records that have been created, modified, or missing since a previously performed synchronization operation;

using said first subsystem to create creating a message payload list that includes a new synchronization point, and a list of records stored in said first database that each have an associated identification number, and further that have been created since a previously performed synchronization operation;

transmitting said message payload list to said second subsystem;

using said second subsystem to compare said list of records in said message payload list to records stored in said second database since said previously performed synchronization point, to identify any one of said records in said message payload list that do not have a corresponding record stored in said second database;

sending a subsequent communication to said first subsystem to request data associated with any one of said records in said message payload request that does not include a corresponding record in said second database;

using said second subsystem to identify a new record in said second database that was created subsequent to said previously performed synchronization point, and that does not have a corresponding record listed on said message payload list; and

forwarding data concerning said new record to said first subsystem.

2. The method of claim 1, further comprising using a plurality of first subsystems each having an associated first database to form a first peer domain, and performing a synchronization operation by which each one of said first databases is updated with all other ones of said first data sources before using one of said first subsystems to transmit said synchronization request to said second subsystem.

3. The method of claim 1, further comprising using a plurality of second subsystems each having an associated second database, to form a second peer domain, and performing a synchronization operation by which each one of said second databases is updated with all other ones of said second databases before any one of said second database is allowed to respond to said synchronization request from said first subsystem.

4. The method of claim 1, further comprising generating a new synchronization point for each message payload list that is generated.

5. The method of claim 1, further comprising using said second subsystem to generate a subsequent message payload list having a new synchronization point, at a point in time subsequent to said second subsystem receiving said message payload list from said first subsystem.

6. The method of claim 1, wherein communications between said first and second subsystems are performed asynchronously.

7. The method of claim 1, wherein communications between said first and second subsystems are performed synchronously.

8. A method for synchronizing information shared by a subsystem within a mobile platform and a subsystem remote from the mobile platform, the method comprising:

designating one of the subsystems as a first system having a first database;

designating one of the subsystems as a second system having a second database;

using the first subsystem to generate and transmit a message payload list that includes a synchronization point and a list of records stored in said first database, with each one of said records including a unique identification code;

using said second subsystem to receive said message payload list and to update said second database using said records;

using said second subsystem to notify said first subsystem of all records stored in said database that have been created since a previously defined synchronization point between said first and second subsystems; and

using said second subsystem to send a communication to said first subsystem to request data associated with any one of said records in said message payload request that does not include a corresponding record in said second database;

using said second subsystem to identify a new record in said second database that was created subsequent to said previously defined synchronization point, and that does not have a corresponding record listed on said message payload list; and

forwarding data concerning said new record to said first subsystem.

9. The method of claim 8, wherein using said second subsystem to update said second database comprises using said second subsystem to compare said identification code of said record included in said message payload list with identification codes of records stored in said second database.

10. The method of claim 8, further comprising:

using a plurality of said first subsystems each having a database associated therewith and identifying said first subsystems as a domain of peer data sources; and

performing a synchronization operation to synchronize data stored in all of said first databases before performing a synchronization between any one of said first subsystems and said second subsystem.

11. The method of claim 8, further comprising:

using a plurality of said second subsystems each having a database associated therewith and identifying said second subsystems as a domain of peer data sources; and

performing a synchronization operation to synchronize data stored in all of said second databases before performing a synchronization between any one of said second subsystems and said first subsystem.

12. The method of claim 8, further comprising using said second subsystem to generate a subsequent message payload list having a new synchronization point, at a time subsequent to responding to said message payload request, and transmitting said subsequent message payload list to said first subsystem.

13. The method of claim 8, wherein communications between said subsystems are performed in accordance with at least one of asynchronous and synchronous communications protocols.

14. A network system for synchronizing information shared between a mobile platform and a facility remote from the mobile platform, the system comprising:

a first subsystem, located on-board the mobile platform and having a first database;

a second subsystem located at the facility remote from the mobile platform, the second subsystem including a server and having a second database, the server connected to a network;

the first subsystem configured to generate and transmit a synchronization request to said second subsystem, said synchronization request including a synchronization point to be used as a reference for future synchronization operations between said subsystems, and a message payload list that includes said synchronization point and a list of records stored in said first database that each have an associated identification number, and further that have been created since a previously performed synchronization operation;

said second subsystem configured to;

receive said synchronization request and to check said second database for any records that have been created or modified since said previously performed synchronization operation, and to transmit information back to said first subsystem that includes information concerning said new or modified records;

to send a communication to said first subsystem to request data associated with any one of said records in said message payload request that does not include a corresponding record in said second database;

to identify a new record in said second database that was created subsequent to said previously performed synchronization point, and that does not have a corresponding record listed on said message payload list; and

forward data concerning said new record to said first subsystem.