Database synchronization via a mobile network

• US 9,460,104 B2
• Filed: 12/31/2013
• Issued: 10/04/2016
• Est. Priority Date: 12/29/2004
• Status: Expired due to Fees

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Backholm, Ari, Salorinne, Seppo, Ylinen, Heikki, Groeber, Marcus, Vuornos, Lauri, Ikonen, Rauli, Ahonen, Jukka, Everitt, Andrew, McLeod, Allan, Salmi, Petri
• Primary Examiner(s): NGUYEN, KIM T
• Application Number:
  US14/145,843
• Publication Number:
  US 20140324504A1
• Time in Patent Office: 1,008 Days
• Field of Search: 707/609, 707/617
• US Class Current: 1/1
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• 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
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: G06Q 10/1095 Meeting or appointment
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems

Abstract

An apparatus adapted to operate as an A party in a database synchronization with a B party via a mobile communication network. The database contains data items to be synchronized. The apparatus includes mechanisms for maintaining a copy of the database and a client-server communication module with a client part and a server part. The client part is configured to communicate via the mobile communication network with the server part of the B party. The apparatus also includes change detection mechanisms responsive to a detection of a changed data item, for initiating a synchronization event via the client part of the client-server communication module.

Claims

1. A method for synchronizing a database between an A party and a B party, wherein the parties communicate with each other via a mobile communication network and the database contains data items to be synchronized, the method comprising:

installing in each of the A party and the B party a client part and a server part of a client-server communication module, wherein the client part of the client-server communication module of a party communicates via the mobile communication network with the server part of the client-server communication module of the other party;

maintaining in each of the A party and the B party a respective copy of the database; and

in response to a changed data item being generated by either the A party or the B party, a change detection logic located in the party having generated the changed data item detects the changed data item and signals the changed data item to the client-server communication module of the party having generated the changed data item thereby causing the party having generated the changed data item to initiate a synchronization event via the client part of its client-server communication module, wherein the synchronization event comprises sending a notification message that indicates said changed data item to the other party via the mobile communication network;

wherein the method further comprises;

storing changed data items in a buffer during connection interruptions between the parties;

sending the changed data items stored in the buffer after connection re-establishment; and

if a newly-changed data item relates to a changed data item stored in the buffer, combining the newly-detected changed data item with the changed data item stored in the buffer;

wherein combining the newly-detected changed data item with the changed data item stored in the buffer includes the newly-changed data item overriding the changed data item stored in the buffer.

2. A method according to claim 1, further comprising:

maintaining a copy of the database and an indication of the latest synchronization event between the A party and the B party;

maintaining an A change count and a B change count in respect of each data item to be synchronized;

wherein the A change count indicates the number of changes made to the data item by the A party, and the B change count indicates the number of changes made to the data item by the B party and known to the A party;

in response to a synchronization trigger;

sending from the A party to the B party an indication of each data item that the A party has changed after the latest synchronization event, plus the A change count and the B change count in respect of each sent data item;

receiving at the A party from the B party an indication of each data item that the B party has changed after the latest synchronization event, plus the A change count and the B change count in respect of each received data item; and

detecting a conflict if the received A change count differs from the maintained A change count.

3. A method according to claim 1, wherein each data item indicates a calendar event or meeting request.

4. A method according to claim 1, wherein each data item comprises a control message, wherein each control message indicates an act to be performed on an e-mail message but does not include an e-mail message.

5. A method according to claim 1, wherein sending a notification message that indicates said changed data item to the other party via the mobile communication network comprises sending the notification message to an intervening network element that stores the notification message in a buffer during a connection interruption.

6. A method according to claim 1, wherein sending a notification message that indicates said changed data item to the other party via the mobile communication network comprises buffering, during a connection interruption, the notification message in the client part of the client-server communication module of the party having generated the changed data item.

7. A method according to claim 1, wherein the synchronization event comprises proceeding with full synchronization after an interruption and a subsequent re- establishment of a connection without beginning from scratch.

8. A method according to claim 1, further comprising comparing a time stamp of a data item with a time of a latest synchronization event.

9. A method according to claim 1, further comprising setting a flag in response to the changed data item being generated and resetting the flag after the synchronization event.

10. A method according to claim 9, wherein setting a flag comprises setting a one-bit flag.

11. A method according to claim 1, wherein, in the party having generated the changed data item, one application is responsible for changing data items and another application is responsible for sending the changed data items.

12. A method according to claim 11, wherein said one application responsible for changing data items comprises a calendar application.

13. A method according to claim 12, wherein said another application responsible for sending the changed data items comprises a communication application.

14. A method according to claim 1, wherein sending the changed data items comprises providing each data item without a time stamp.

15. A method according to claim 14, wherein an A party clock and a B party clock are offset.

16. A method according to claim 1, wherein the party sending the changed data items determines if the sent changed data items are received without reception being acknowledged.

17. A method according to claim 16, wherein:

the A party maintains an A change count and a B change count in respect of each data item to be synchronized;

the B party maintains an A change count and a B change count in respect of each data item to be synchronized;

sending the changed data items comprises sending the A change count and a B change count maintained by the party sending the changed data items.

18. A method according to claim 17, wherein the party sending the changed data items determines if the sent changed data items are received without reception being acknowledged by comparing received change counts with corresponding change counts maintained locally.

19. A method according to claim 1, the newly-changed data item overriding the changed data item stored in the buffer comprises a most recent change to a calendar event overriding an earlier change to the same calendar event stored in the buffer.

20. A method according to claim 1, wherein the changed data item being generated by either the A party or the B party comprises the marking of an email message as read.