System and method for a generic mobile synchronization framework

• US 20050114431A1
• Filed: 11/25/2003
• Published: 05/26/2005
• Est. Priority Date: 11/25/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Singh, Uma Kant, Narayanan, Ajit Kumar
• Granted Patent: US 8,909,712 B2
• Time in Patent Office: Days
• US Class Current: 709/201
• 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: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A generic mobile synchronization framework facilitates synchronization of data objects between platforms by comparing these data objects from one platform with a replica of data objects on the other platform. Generic messages identifying the differences in the data objects are converted into an adaptive message suitable for use by the underlying synchronization hardware and sent to eh platform needing synchronization. That platform converts the adapted messages them to the original generic message, and executes them, synchronizing the data objects in that platform with the originating platform.

Claims

1. A method of synchronizing data objects between a first platform and a second platform comprising:

creating a set of generic messages identifying changes to the data objects since a previous synchronization;

converting the generic messages to adapted messages;

sending the adapted messages from the first platform to the second platform;

converting the adapted messages to generic messages on the second platform; and

updating the data objects on the second platform using the generic messages.

2. The method of claim 1, wherein creating the set of generic messages includes:

fetching the data objects from an application in the first platform; and

comparing the fetched data objects in the first platform with a replica of the data objects in the second platform to identify changes.

3. The method of claim 2, wherein fetching the data objects from an application in the first platform includes:

selecting data objects to be fetched; and

fetching only the selected data objects.

4. The method of claim 2, further including categorizing the data objects into a first category and a second category.

5. The method of claim 4, further including wherein creating the generic messages includes:

generating generic messages for only the first category of data objects.

6. The method of claim 2, further including:

grouping data objects into a first transaction group and a second transaction group.

7. The method of claim 6, further including:

sending a failure notification from the second platform to the first platform if the update on the data object of the first transaction group in the second platform fails; and

rolling back all updating of data objects of the first transaction group on the second platform upon the failure notification.

8. The method of claim 1, wherein converting the generic messages to adapted messages includes converting the generic messages to adapted messages based on the requirements of an underlying synchronization software.

9. The method of claim 1, wherein sending the adapted messages from the first platform to the second platform includes sending the adapted messages using an underlying synchronization software.

10. The method of claim 1, wherein updating the data objects on the second platform using the generic messages includes executing the generic messages so that they act on the data objects of the second platform.

11. A system for synchronizing data objects between a first platform and a second platform comprising:

a memory; and

a microprocessor coupled to the memory and programmed to;

create a set of generic messages identifying changes to the data objects since a previous synchronization;

convert the generic messages to adapted messages;

send the adapted messages from the first platform to the second platform;

convert the adapted messages to generic messages on the second platform; and

update the data objects on the second platform using the generic messages.

12. The system of claim 11, wherein the microprocessor is further programmed to:

fetch the data objects from an application in the first platform;

compare the fetched data objects in the first platform with a replica of the data objects in the second platform to identify changes.

13. The system of claim 12, wherein the microprocessor is further programmed to:

select data objects to be fetched; and

fetch only the selected data objects.

14. The system of claim 12, wherein the microprocessor is further programmed to categorize the data objects into a first category and a second category.

15. The system of claim 14, wherein the microprocessor is further programmed to only generate generic messages for the first category of data objects.

16. The system of claim 12, wherein the microprocessor is further programmed to:

group data objects into a first transaction group and a second transaction group.

17. The system of claim 16, wherein the microprocessor is further programmed to:

send a failure notification from the second platform to the first platform if the update on the data object of the first transaction group in the second platform fails; and

roll back all updating of data objects of the first transaction group on the second platform upon the failure notification.

18. The system of claim 11, wherein the microprocessor is further programmed to convert the generic messages to adapted messages based on the requirements of an underlying synchronization software.

19. The system of claim 11, wherein the microprocessor is further programmed to send the adapted messages using an underlying synchronization software.

20. A system for synchronizing data objects between a first platform and a second platform comprising:

a memory; and

processing means, coupled to the memory, for

creating a set of generic messages identifying changes to the data objects since a previous synchronization;

converting the generic messages to adapted messages;

sending the adapted messages from the first platform to the second platform;

converting the adapted messages to generic messages on the second platform; and

updating the data objects on the second platform using the generic messages.