System and method for accessing different types of back end data stores

• US 7,404,011 B2
• Filed: 04/04/2003
• Issued: 07/22/2008
• Est. Priority Date: 05/31/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Merk, Lothar, Hepper, Stefan, Stober, Thomas, Hansmann, Uwe
• Primary Examiner(s): Etienne; Ario
• Assistant Examiner(s): Kim; Hee Soo
• Application Number:
  US10/516,427
• Publication Number:
  US 20050228812A1
• Time in Patent Office: 1,936 Days
• Field of Search: 709/204, 709/224, 709/217, 709/248
• US Class Current: 709/248
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• 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: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A system for exchange of data between a plurality of clients and at least one back end data store by using a central synchronization server having a connection to the clients. The clients generate data to be synchronized. The system includes a sync engine connected to the central synchronization server for performing synchronization with the central synchronization server, a single back end neutral interface associated with and connected to the sync engine, and a component assigned to each of the at least one back end data store. Each of the components include a back end dependent part having an interface with the single back end neutral interface and an interface with the assigned back end data store.

Claims

1. A system for exchange of data between a plurality of clients and at least one back end data store by using a central synchronization server having a connection to said clients, said clients generating data to be synchronized, said system comprising:

a sync engine for performing synchronization with said central synchronization server and connected to said central synchronization server;

a single back end neutral interface associated with and connected to said sync engine; and

a component assigned to each of said at least one back end data store, each of said components comprising a back end dependent part having an interface with said single back end neutral interface and an interface with said assigned back end data store, each of said components further comprising an abstract Back End independent part, wherein said abstract Back End independent part provides common functionalities for use by all the Back End dependent parts; and

,

a cache for permanently buffering of updates of said at least one back end data store and said clients, and wherein

each component comprises a caching mechanism for controlling and executing buffering updates into said cache and replicating buffered updates to said respective clients and said assigned back end data store, said caching mechanism having a Back End Monitor; and

,

said caching mechanism provides for each of said at least one back end data store its own Back End Monitor, Cache Monitor, and Back End Manager with its Back End dependent part and its abstract Back End independent part.

2. A system according to claim 1, wherein each of said components further comprises an abstract Back End independent part, wherein said abstract Back End independent part provides common functionalities for use by all the Back End dependent parts.

3. A system according to claim 2, wherein each of said at least one back end data store is assigned its own said component.

4. A system according to claim 2, further comprising a cache for permanently buffering of updates of said at least one back end data store and said clients, and each said component comprises a caching mechanism for controlling and executing buffering updates into said cache and replicating buffered updates to said respective clients and said assigned back end data store.

5. A system according to claim 4, wherein said caching mechanism has a Back End Monitor.

6. A system according to claim 5, wherein said caching mechanism further includes a Back End Manager.

7. A system according to claim 5, wherein said Back End Monitor replicates updates between said cache and the associated one of said at least one back end data store in a batch or a continuous trickle mode.

8. A system according to claim 4, wherein said caching mechanism includes a Cache Monitor.

9. A system according to claim 8, wherein said Cache Monitor replicates updates from said cache to the associated one of said at least one back end data store in a batch or a continuous trickle mode.

10. A system according to claim 4, wherein said caching mechanism further comprises a persistent store.

11. A system according to claim 4, wherein said cache and said at least one back end data store are databases.

12. A system according to claim 1, wherein said exchange of data is synchronization of data.

13. A system according to claim 12, wherein SyncML is employed as a synchronization protocol.

14. A system according to claim 1, wherein said clients are mobile clients.