Database synchronization

• US 9,298,792 B2
• Filed: 12/08/2005
• Issued: 03/29/2016
• Est. Priority Date: 12/10/2004
• Status: Expired due to Fees

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Ylinen, Heikki
• Primary Examiner(s): Parry, Chris
• Assistant Examiner(s): Chou, Alan S
• Application Number:
  US11/296,255
• Publication Number:
  US 20060149794A1
• Time in Patent Office: 3,764 Days
• Field of Search: 709/221
• US Class Current: 1/1
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

Synchronization of data items between parties A and B. A maintains copies of data items and an A change count and a B change count for each data item. The A change count indicates the number of changes made by A, and the B change count indicates the number of changes made by B and known to A. After a synchronization trigger, A sends to B each data item that A has changed, plus the A change count and the B. change count for each sent data item. A receives from B each data item that B has changed, plus the A change count and the B change count for each received data item. A detects a conflict if the received A change count differs from the maintained A change count.

Claims

1. A method for synchronizing a first data storage and a second data storage, the method comprising:

maintaining by a processor a first change count and a second change count for a data item a first data storage, wherein the first change count maintained the processor indicates a number of changes made to the data item at the first data storage, wherein the second change count maintained by the processor indicates a number of changes made to a corresponding data item at a second data storage; and

responsive to a synchronization trigger that is generated when the data item is changed and a data connection is available;

receiving an identifier for the changed data item along with a first change count and a second change count maintained at the second data storage;

detecting a conflict in the data item between the first and second data storages based on the maintained first and second change counts and the received first and second change counts; and

resolving the conflict according to a set of predetermined rules,

wherein applicable rules of the set of predetermined rules are displayed as a menu on a user interface for selection by a user; and

wherein one application is responsible for receiving the identifier for the changed data item and another application is responsible for the changes made to the data item at the first data storage.

2. The method of claim 1, wherein, if the data item is a document, the conflict is resolved by merging conflicting versions for subsequent editing.

3. The method of claim 2, wherein, if the data item having conflicting versions is a calendar event, the conflict is resolved by replacing an older version with a newer version of the conflicting versions.

4. The method of claim 1, wherein resolving the conflict includes displaying conflicting versions of the data item in the user interface and receiving an input from the user interface to resolve the conflict.

5. The method of claim 4, further comprising offering the conflicting versions for user selection via the user interface.

6. The method of claim 1, wherein, the first data storage and the second data storage are coupled via a mobile communication network.

7. The method of claim 1, further comprising:

sending an indication that the data item in the first data storage has changed after the synchronization event, plus the first change count and the second change count maintained in the first data storage.

8. The method of claim 7, further comprising:

sending the first data item, and replacing the corresponding data item in the second data storage with the sent data item if;

the second change count maintained at the second data storage for the data item corresponds to the second change count maintained in the first data storage for the data item; and

the first change count maintained at the second data storage for the data item does not correspond to the first change count maintained in the first data storage for the data item.

9. A system for performing a method for synchronizing a first data storage and a second data storage over a mobile communications network, the system comprising:

means for maintaining in a first data storage a first change count and a second change count for a data item in the first data storage,

wherein the first change count maintained in the first data storage indicates a number of changes made to the data item in the first data storage,

wherein the second change count maintained in the first data storage indicates a number of changes made to a corresponding data item maintained in a second data storage;

means for receiving an indication that the data item in the second data storage has changed after a synchronization event, the indication including an identifier of the changed data item,

means for requesting the changed data item; and

means for resolving a conflict detected from the first and second change counts according to a set of predetermined rules;

wherein applicable rules of the set of predetermined rules are displayed as menu selections on a user interface for selection by a user; and

wherein one application is responsible for receiving an indication that the data item in the second data storage has changed and another application is responsible for the changes made to the data item at the first data storage.

10. The system of claim 9, further comprising means for displaying conflicting versions of the data item in the user interface.

11. The system of claim 10, further comprising means fir offering the set of user selectable options for manipulating the conflicting versions of the data item to resolve the conflict.

12. The system of claim 10, wherein, if the data item having conflicting versions is a calendar event, the conflict is resolved by replacing an older version with a newer version of the conflicting versions;

wherein, if the data item is a document, the conflict is resolved by merging the conflicting versions for subsequent editing.

13. The system of claim 9, further comprising means for connecting the first data storage to the second data storage via the mobile communication network.

14. The system of claim 9, further comprising,

means for receiving, after the latest synchronization event, a first change count maintained in the second data storage for the data item,

wherein the first change count maintained in the second data storage indicates a number of changes made to the data item maintained at the first data storage.

15. The system of claim 14, wherein the conflict is detected from the first change count maintained in the second data storage and the first change count maintained in the first data storage.

16. The system of claim 9, further comprising,

means for receiving, after the latest synchronization event, a second change count maintained at the second data storage for each received data item,

wherein the second change count maintained at the second data storage indicates a number of changes made to the data item at the second data storage.

17. An apparatus for synchronizing a first data storage and a second data storage, the apparatus comprising:

a memory configured to;

maintain a first change count and a second change count for each data item in a first data storage, wherein the first change count indicates a number of changes made to the data item in the first data storage,

wherein the second change count indicates a number of changes made to a corresponding data item in a second data storage;

a processor configured to execute instructions to;

detect a conflict in the data item between the first and second data storages based on the first and second change counts, in response to a synchronization trigger; and

resolve the conflict according to a set of predetermined rules,

wherein applicable rules of the set of predetermined rules are displayed as menu selections on a user interface for selection by a user; and

wherein one application is responsible for receiving an indication that the data item in the second data storage has changed and another application is responsible for the changes made to the data item in the first data storage.