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

• US 7,162,543 B2
• Filed: 06/05/2002
• Issued: 01/09/2007
• Est. Priority Date: 06/06/2001
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Fischer, Claudius, Stephan, Thorsten, Schmidt, Markus, Muller, Franz, Hertweck, Jochen
• Primary Examiner(s): Winder; Patrice
• Assistant Examiner(s): WANG, LIANG CHE A
• Application Number:
  US10/164,225
• Publication Number:
  US 20030037254A1
• Time in Patent Office: 1,679 Days
• Field of Search: 709/220, 709/248, 709/224, 709/229, 709/236, 707/201, 455/430
• US Class Current: 709/248
• 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, said first data container comprising a body portion and a header portion,

said body portion comprising data from an application executed on said device, said data from said application to be synchronized with said computer system,

said header portion comprising a field for indicating which function module to call in said computer system to process said data from said application, a send date, a send time, an execution date, an execution time, and a status;

storing said first data container on said device;

sending said first data container to said computer system;

sending during a synchronization a second data container including data that identifies one or more applications installed on said device; and

receiving from said computer system a third data container that includes data for performance of an application update, wherein said update is determined by said computer system to be required based on a comparison of said data that identifies one or more applications with a stored identification of applications that should be installed on said device.

2. A synchronization process as in claim 1, wherein said header portion comprises a container ID, a user ID, an indication of a type of said container, and 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 body portion comprises 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, further comprising, receiving a fourth data container from said computer system in a common communication session in which said first data container is transferred to said computer system, wherein said fourth 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, further comprising, receiving a fourth data container from said computer system in a common communication session in which said first data container is transferred to said computer system, wherein said fourth 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 as in claim 1, further comprising the step of, for entry of said data from said application, providing said application via an interface of a web server that has a same visual and behavioral appearance as an interface of said computer system that is provided when said application is executed on said computer system.

18. A synchronization process as in claim 17, wherein a servlet engine enables said application to be executed via said web server.

19. A synchronization process as in claim 1, further comprising the step of initially storing said data from said application in a database of said device;

wherein;

an application program interface (API) layer forms an interface between said database and a plurality of applications including said application; and

said API layer provides for replaceability of one or more of said plurality of applications with one or more other applications while maintaining operability of said database and data of said database.

20. A synchronization process as in claim 19, wherein said API calls a first module for sending said first data container and calls a second module for sending said second data container.

21. A synchronization process as in claim 1, wherein:

if said required application update is an application uninstall, said data of said third data container includes an identification of an uninstall function module of said device for instructing said device to call said uninstall function module in response to receipt of said third data container; and

if said required application update is an application install, said data of said third container includes an identification of an install function module of said device for instructing said device to call said install function module in response to receipt of said third data container.

22. A synchronization process as in claim 1, wherein said second data container is sent during every synchronization.

23. A synchronization process as in claim 1, wherein to which of a plurality of stored identifications of applications said data that identifies one or more applications is compared depends on a user role assigned to the device.

24. A synchronization process as in claim 1, wherein:

said application is a shopping application; and

said data from said application is synchronized for an update of at least one of a catalog content and an order.

25. A synchronization process as in claim 1, wherein said synchronization process is triggered one of (a) in response to a click of one of an icon, a button, and a link and (b) in response to establishment of a connection between said device and said computer system.

26. A synchronization process as in claim 1, wherein:

said data from said application is entered while said device is connected to the computer system; and

said synchronization process is triggered in response to said data becoming available for transmission to the computer system.

27. A synchronization process as in claim 1, wherein Java code is executed to initiate said synchronization process.

28. 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, said first data container comprising a body portion and a header portion,

said body portion comprising data from an application executed on said device, said data from said application to be synchronized with said computer system,

said header portion comprising a field for identifying an application function module;

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

during a synchronization, receiving from said device a second data container including data that identifies one or more applications installed on said device;

reading a third data container intended for said device from said memory;

sending said third data container to said device;

based on a comparison of said data that identifies one or more applications with a stored identification of applications that should be installed on said device, determining whether an application update is required at said device;

if it is determined that the application update is required, sending to said device a fourth data container that includes data for performance of the application update;

reading out said first data container from said memory;

mapping said data of said body portion to said application function module;

calling said application function module to process said data of said body portion;

retrieving response data from said application function module;

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

saving said responsive data container in said memory.

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

30. A synchronization process as in claim 29, wherein said third and responsive data containers each comprises a header portion.

31. A synchronization process as in claim 30, wherein said header portions of said first, third, and responsive data containers each 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.

32. A synchronization process as in claim 30, wherein said body portion comprises a container ID, line number, field name and field value.

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

34. A synchronization process as in claim 29, wherein said third data container comprises information responsive to said first data container.

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

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

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

38. A synchronization process as in claim 28, wherein said device comprises a handheld computer.

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

40. A synchronization process as in claim 28, wherein said device comprises a desktop computer.

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

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

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

44. A synchronization process as in claim 28, 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.

45. A synchronization process as in claim 28, further comprising the steps of:

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

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

46. A synchronization process as in claim 45, wherein said indication comprises a unique identification of said third data container.

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

48. A synchronization process as in claim 47, wherein sending a data container to said device comprises the steps of:

comparing a unique data container identification received from said device to entries in said history table;

if said unique data container identification matches an entry in said history table, deleting a data container corresponding to said entry without sending said corresponding data container; and

sending to said device one or more data containers corresponding to one or more entries of said history table other than said entry.

49. A synchronization process as in claim 28, wherein said mapping comprises determining that said function module is most suitable of a plurality of function modules of said computer system for processing said data of said body portion, wherein said determination is based on mapping a structure of said first data container to an interface of said function module.

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

receiving from said device a first data container that includes a data to be processed by said computer system and an identification of an application function module to be called for processing said data to be synchronized;

in response to receipt of said first data container, calling said application function module to process said data;

retrieving response data from said application function module;

creating a second data container that is responsive to said first data container, said second data container including information related to said response data;

during a synchronization, receiving from said device a third data container including data that identifies one or more applications installed on said device;

based on a comparison of said data that identifies one or more applications with a stored identification of applications that should be installed on said device determining whether an application update is required at said device;

if it is determined that the application update is required, creating a fourth data container that includes data for performance of the application update; and

sending said second and fourth data containers to said device.

51. A synchronization process as in claim 50, wherein said second data container is sent to said device during a synchronization in which said computer system receives said first data container from said device.

52. A synchronization process as in claim 50, wherein said computer system receives said first data container during a first synchronization and sends said second data container during a second synchronization after said first synchronization is completed.

53. A synchronization process as in claim 50, further comprising:

receiving a fifth data container that includes a status-notification request regarding a status of previously sent data containers;

retrieving all data containers stored in a memory at said computer system that are associated with a user who is also associated with said fifth data container; and

sending said retrieved data containers to said device in response to receipt of said fifth data container;

wherein said retrieved data containers include status data.

54. A synchronization process as in claim 50, further comprising:

in response to receipt of said third data container, calling an application synchronization function module for performing said comparison;

retrieving response data from said synchronization function module;

wherein whether said device requires said application update is determined based on said response data retrieved from said synchronization function module.

55. A synchronization process as in claim 50, wherein:

if said required application update is an application uninstall, said data of said fourth container includes an identification of an uninstall function module of said device for instructing said device to call said uninstall function module in response to receipt of said fourth data container; and

if said required application update is an application install, said data of said fourth container includes an identification of an install function module of said device for instructing said device to call said install function module in response to receipt of said fourth data container.

56. A synchronization process as in claim 50, wherein said third data container is received during every synchronization.

57. 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 that includes a data to be processed by said computer system and an identification of an application function module to be called by said computer system for processing said data to be processed;

sending said first data container to said computer system;

receiving from said computer system a second data container that is responsive to said first data container and includes information related to response data retrieved by said computer system from said application function module;

during a synchronization, sending a third data container including data that identifies one or more applications installed on said device; and

receiving from said computer system a fourth data container that includes data for performance of an application update, wherein said update is determined by said computer system to be required based on a comparison of said data that identifies one or more applications with a stored identification of applications that should be installed on said device.

58. A synchronization process as recited in claim 57, further comprising:

providing a single user interface for receiving data entry in an offline mode and in an online mode;

prior to a particular synchronization, locally storing data entered in said offline mode, said data entered in said offline mode being sent during said particular synchronization in a data container that indicates a function module to be called for processing said data entered in said offline mode;

providing in said user interface a selectable control;

in response to a selection of said selectable control, initiating said particular synchronization in an online mode; and

sending data entered in said online mode to said computer system without a corresponding data container that indicates a function module to be called.

59. 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, said first data container comprising a body portion and a header portion,

said body portion comprising data from an application executed on said device, said data from said application to be synchronized with said computer system,

said header portion comprising a field for identifying an application function module;

mapping said data of said body portion to said application function module;

calling said application function module to process said data of said body portion;

retrieving response data from said application function module;

sending to said device a second data container responsive to said first data container and comprising information related to said response data;

during a synchronization, receiving from said device a third data container including data that identifies one or more applications installed on said device;

based on a comparison of said data that identifies one or more applications with a stored identification of applications that should be installed on said device, determining whether an application update is required at said device; and

if it is determined that the application update is required, sending a fourth data container that includes data for performance of the application update.