Database synchronization via a mobile network

• US 20060184591A1
• Filed: 12/28/2005
• Published: 08/17/2006
• Est. Priority Date: 12/29/2004
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks International Oy (SoftBank Group Corp.)
• Inventors: Groeber, Marcus, McLeod, Allan, Ikonen, Rauli, Everitt, Andrew, Ahonen, Jukka, Salorinne, Seppo, Vuornos, Lauri, Backholm, Ari, Salmi, Petri, Ylinen, Heikki
• Granted Patent: US 8,620,858 B2
• Time in Patent Office: Days
• 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 data-base 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 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 generating a changed data item, the party having generated the changed data item initiating a synchronization event via the client part of its client-server communication module.

2. A method according to claim 1, further comprising buffering changed data items during connection interruptions between the parties and sending the buffered data items after connection re-establishment.

3. A method according to claim 2, further comprising combining a newly-detected changed data item with a buffered changed data item.

4. 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.

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

6. 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.

7. A method according to claim 1, wherein the synchronization event comprises sending a notification message via the mobile communication network, the notification message indicating said changed data item.

10. A computer program product executable in a data processor, comprising program instructions for causing the data processor to carry out the method according to claim 1 when the program product is executed in the data processor.

8. An apparatus adapted to operate as an A party in a database synchronization with a B party via a mobile communication network wherein the database contains data items to be synchronized, the apparatus comprising:

a client-server communication module comprising a client part and a server part, wherein the client part of the client-server communication module is configured to communicate via the mobile communication network with the server part of the client-server communication module of the B party;

means for maintaining a copy of the database;

means responsive to a detection of a changed data item, for initiating a synchronization event via the client part of the client-server communication module.

9. An apparatus according to claim 8, further comprising:

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

means for 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;

means responsive to a synchronization trigger;

for 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;

for 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

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