Process for synchronizing data between remotely located devices and a central computer system

• US 20030037254A1
• Filed: 06/05/2002
• Published: 02/20/2003
• Est. Priority Date: 06/06/2001
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: Sapmarkets Incorporated
• Inventors: Muller, Franz, Schmidt-Karaca, Markus, Fischer, Claudius, Stephan, Thorsten, Hertweck, Jochen
• Granted Patent: US 7,162,543 B2
• Time in Patent Office: Days
• US Class Current: 713/200
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A process for synchronizing data between a remotely located device, such as a personal digital assistant, Internet-enabled phone, handheld computer, laptop or desktop computer, and a central computer system. The data may be related to offline applications running on the device.

Claims

1. A synchronization process for a device for synchronizing data between said device and a computer system comprising the steps of:

creating a first data container to be sent to said computer system;

storing said first data container on said device;

sending said first data container to said computer system; and

receiving a second data container from said computer system,

said first and second data containers each comprising a header.

2. A synchronization process as in claim 1, wherein said header comprises a container ID, a user ID, an indication of a type of said container, a method ID, a send date, a send time, an execution date, an execution time and a status.

3. A synchronization process as in claim 1, wherein said first data container further comprises a body, said body comprising a container ID, line number, field name and field value.

4. A synchronization process as in claim 1, wherein said first data container is sent upon the existence of a connection to said computer system and an indication by a user that synchronization is desired.

5. A synchronization process as in claim 1, wherein said second data container comprises information responsive to an earlier data container sent from said device to said computer system during a previous synchronization.

6. A synchronization process as in claim 1, wherein said second data container comprises information responsive to said first data container.

7. A synchronization process as in claim 1, wherein said device comprises a personal digital assistant.

8. A synchronization process as in claim 1, wherein said device comprises a handheld computer.

9. A synchronization process as in claim 1, wherein said device comprises a laptop computer.

10. A synchronization process as in claim 1, wherein said device comprises a desktop computer.

11. A synchronization process as in claim 1, wherein said device comprises an Internet enabled phone.

12. A synchronization process as in claim 1, wherein said computer system comprises an applications server.

13. A synchronization process as in claim 1, further comprising the steps of:

receiving an indication that said first data container was received by said computer system; and

deleting said first data container off of said device upon receiving said indication.

14. A synchronization process as in claim 13, wherein said indication comprises a unique identification of said first data container.

15. A synchronization process as in claim 14, further comprising the step of writing said unique identification of said first data container in a history table after receiving said indication.

16. A synchronization process as in claim 15, further comprising the steps of:

comparing said unique identification of said first data container to entries in said history table prior to sending said first data container;

if said unique identification of said first data container matches an entry in said history table, deleting said first data container without sending said first data container.

17. A synchronization process for computer system for synchronizing data between said computer system and a device comprising the steps of:

receiving a first data container from said device;

saving said first data container in memory associated with said computer system;

reading a second data container intended for said device from said memory; and

sending said second data container to said device;

reading out said first data container from said memory;

mapping data from said first data container;

calling an application function module to process said data;

retrieving response data from said application function module;

creating a responsive data container comprising information related to said response data;

saving said responsive data container in said memory.

18. A synchronization process as in claim 17, wherein said first data containers are received upon the existence of a connection to said computer system and an indication by a user of said device that synchronization is desired.

19. A synchronization process as in claim 18, wherein said first, second and responsive data containers each comprising a header.

20. A synchronization process as in claim 19, wherein said header comprises a container ID, a user ID, an indication of a type of said container, a method ID, a send date, a send time, an execution date, an execution time and a status.

21. A synchronization process as in claim 19, wherein said first data container further comprises a body, said body comprising a container ID, line number, field name and field value.

22. A synchronization process as in claim 18, wherein said second data container comprises information responsive to an earlier data container sent from said device to said computer system during a previous synchronization.

23. A synchronization process as in claim 18, wherein said second data container comprises information responsive to said first data container.

24. A synchronization process as in claim 18, further comprising the step of sending said responsive data container to said device.

25. A synchronization process as in claim 17, wherein said memory comprises first and second databases, said first database storing said first data container and said second database storing said second data container and said responsive data container.

26. A synchronization process as in claim 17, wherein said device comprises a personal digital assistant.

27. A synchronization process as in claim 17, wherein said device comprises a handheld computer.

28. A synchronization process as in claim 17, wherein said device comprises a laptop computer.

29. A synchronization process as in claim 17, wherein said device comprises a desktop computer.

30. A synchronization process as in claim 17, wherein said device comprises an Internet enabled phone.

31. A synchronization process as in claim 17, wherein said computer system comprises an applications server.

32. A synchronization process as in claim 17, further comprising the step of deleting said first data container from said memory after said responsive data container is stored in said memory.

33. A synchronization process as in claim 17, further comprising the step of deleting said responsive data container from said memory upon receipt of an indication from said device that said responsive data container was received.

34. A synchronization process as in claim 17, further comprising the steps of:

receiving an indication that said second data container was received by said device; and

deleting said second data container off of said computer system upon receiving said indication.

35. A synchronization process as in claim 34, wherein said indication comprises a unique identification of said second data container.

36. A synchronization process as in claim 35, further comprising the step of writing said unique identification of said second data container in a history table after receiving said indication.

37. A synchronization process as in claim 36, further comprising the steps of:

comparing said unique identification of said second data container to entries in said history table prior to sending said second data container;

if said unique identification of said second data container matches an entry in said history table, deleting said second data container without sending said second data container.