System and method for synchronization of version annotated objects

• US 20070180075A1
• Filed: 04/25/2002
• Published: 08/02/2007
• Est. Priority Date: 04/25/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Chasman, Doug, Shay, Bruce, Parrett, Jeff, Heinke, Joel
• Granted Patent: US 7,606,881 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• 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

Abstract

Objects in a master database and objects in a replicated database are synchronized using identifiers and version stamps of the objects. Each object has a unique identifier and a version stamp that is incremented when the object is updated at the master database. A synchronization server uses the identifiers and version stamps of objects to perform out-of-date detection and conflict detection. The synchronization server resolves update conflicts according to rules.

Claims

1. A system for synchronization of business objects, comprising:

a master database configured to store business objects, each business object having a version stamp and an identifier, wherein at least one of the business objects is updateable by a plurality of users;

a plurality of replicated databases configured to store business objects, each business object in the plurality of replicated databases having a version stamp and an identifier, wherein the plurality of replicated databases are associated with the plurality of users; and

a synchronization server configured to operate in conjunction with a synchronization processor to synchronize a business object in a first replicated database in the plurality of replicated databases with a corresponding business object in the master database based on a synchronization request from a first user in the plurality of users, an update request being generated and stored in an update queue in response to an update of the business object in the first replicated database by the first user, the update request including the version stamp, identifier, and identity of the first user, the update request being sent to the synchronization server in response to the synchronization request,

wherein if a conflict exists between identifier and the version stamp and of the business object in the first replicated database included in the update request and the identifier and the version stamp of the corresponding business object in the master database, and where an update to the corresponding business object in the master database has been performed by a second user, the synchronization server is configured to resolve the conflict according to at least one conflict resolution rule configured to override the update by one of the first and second users based on a priority of one of the first and second users over the other of the first and second users.

2. The system of claim 1, wherein the synchronization server and the synchronization processor operate in conjunction as a distributed software application.

3. The system of claim 1, wherein the master database is coupled to an application server that includes the synchronization server.

4. The system of claim 1, wherein the first replicated database and the synchronization processor reside in a first remote device and the second replicated database and the synchronization processor reside in a second remote device.

5. The system of claim 4, wherein the synchronization processor is configured to communicate with the synchronization server via a network.

6. The system of claim 4, wherein at least one of the first remote device and the second remote device is a personal computer.

7. The system of claim 4, wherein at least one of the first remote device and the second remote device is a handheld device.

8. The system of claim 4, wherein at least one of the first remote device and the second remote device is a mobile telephone.

9. The system of claim 1, wherein the synchronization server is configured to perform out-of-date detection using identifiers and version stamps of the objects in the master database and identifiers and version stamps of the objects in the replicated database to determine whether any of the objects in the replicated database are out-of-date.

10. The system of claim 9, wherein the synchronization server is configured to perform out-of-date detection by comparing version stamps of the objects in the replicated database with version stamps of corresponding objects in the master database to determine whether any of the objects in the replicated database are out-of-date, and the synchronization server and the synchronization processor are configured to replace an out-of-date object in the replicated database with a copy of an up-to-date object in the master database.

11. The system of claim 10, wherein the version stamp of each object in the first replicated database is a date/timestamp and the version stamp of each object in the master database is a date/timestamp.

12. The system of claim 10, wherein the version stamp of each object in the first replicated database is an integer and the version stamp of each object in the master database is an integer.

13. The system of claim 10, wherein the version stamp of each object in the first replicated database is a character and the version stamp of each object in the master database is a character.

14. The system of claim 1, wherein the synchronization processor is configured to create the update request.

15. The system of claim 14, wherein the synchronization server is configured to perform update conflict detection using the identifier and the version stamp of the update request.

16. The system of claim 15, wherein the synchronization server is configured to perform update conflict detection by comparing the version stamp of the corresponding object in the master database with the version stamp of the update request to determine if an update conflict exists.

17. The system of claim 16, wherein an update conflict exists if the version stamp of the update request does not match the version stamp of the corresponding object in the master database.

18. The system of claim 16, wherein the synchronization server is configured to update the corresponding object in the master database and to copy the updated object to the replicated database if no update conflict exists.

19. The system of claim 18, wherein the synchronization server is configured to increment the version stamp of the updated object.

21. The system of claim 1, wherein the at least one conflict resolution rule is based on processes of a business application domain of the system.

23. The system of claim 1, wherein the at least one conflict resolution rule is based on ownership of the corresponding object in the master database.

24. The system of claim 16, wherein if the conflict exists and if the synchronization server cannot resolve the conflict, the synchronization server is further configured to communicate with the synchronization processor to notify a user of the replicated database that the conflict was not resolved.

25. The system of claim 1, wherein the synchronization server is configured to increment the version stamp of an object in the master database if that object has been updated.

26. The system of claim 16, wherein the version stamp of each object in the replicated database is a date/timestamp and the version stamp of each object in the master database is a date/timestamp.

27. The system of claim 16, wherein the version stamp of each object in the replicated database is an integer and the version stamp of each object in the master database is an integer.

28. The system of claim 16, wherein the version stamp of each object in the replicated database is a character and the version stamp of each object in the master database is a character.

29. The system of claim 3, further comprising a second master database coupled to a second application server that includes a second synchronization server.

20. (canceled)

22. (canceled)

30. A method for synchronizing objects, comprising the steps of:

receiving an update request from a first user at a synchronization server, the update request including an identifier and a version stamp for an object in a first replicated database and an identity of the first user;

comparing the identifier and the version stamp of the update request with an identifier and a version stamp of an object in a master database to determine whether a conflict exists, wherein the object is updateable by a plurality of users, wherein a plurality of replicated databases are associated with the plurality of users; and

if a conflict exists where an update to an object in the master database has been performed by a second user in the plurality of users,

resolving the conflict according to at least one conflict resolution rule configured to override the update by one of the first and second users based on a priority of one of the first and second users over the other of the first and second users, where the version stamp of the update request and the version stamp of the object in the master database provide update sequence information that is used to determine if the conflict exists;

updating the object in the master database; and

sending a copy of the updated object to the first replicated database in the plurality of replicated databases.

31. The method of claim 30, wherein the step of updating the object includes incrementing the version stamp of the object.

32. The method of claim 30, wherein the update request includes a before value and an after value of a changed property.

33. The method of claim 30, wherein the master database is coupled to an application server that includes the synchronization server.

34. The method of claim 30, wherein the first replicated database is coupled to a first remote device and the second replicated database is coupled to a second remote device.

35. The method of claim 34, wherein the first replicated database communicates with the synchronization server via a network.

36. The method of claim 34, wherein the first remote device includes a synchronization processor configured to access the first replicated database.

37-41. -41. (canceled)

42. A method for synchronizing objects, comprising the steps of:

changing an object in a first replicated database for a first user;

creating an update request having an identifier and a version stamp that corresponds to an identifier and a version stamp of the changed object in the replicated database, the update request further including an identity of the first user;

sending the update request to a server including a master database, wherein an object in the master database is updateable by a plurality of users, wherein a plurality of replicated databases are associated with the plurality of users, wherein if an update to the object has been performed by a second user, the synchronization server is configured to resolve the conflict according to at least one conflict resolution rule configured to override the update by one of the first and second users based on a priority of one of the first and second users over the other of the first and second users;

receiving an object from the server in response to the update request; and

replacing the changed object in the replicated database with the object from the server.

43. The method of claim 42, wherein the update request includes a before status and an after status of a changed field.

44. The method of claim 42, wherein the object from the server is a copy of an updated object that corresponds to the changed object in the replicated database.

45-65. -65. (canceled)

66. A system for synchronizing objects, comprising:

means for changing an object in a first replicated database associated with a first user;

means for creating an update request having an identifier and a version stamp that corresponds to an identifier and a version stamp of the changed object in the first replicated database, the update request further including an identity of the first user;

means for sending the update request to a server;

means for receiving the update request at the server;

means for comparing the identifier and the version stamp of the update request with an identifier and a version stamp of a corresponding object in a master database, wherein the corresponding object in the master database is updateable by a plurality of users;

means for determining if a conflict exists between the update request and the corresponding object in the master database;

if an update to the object has been performed by a second user, means for resolving the conflict according to at least one conflict resolution rule configured to override the update by one of the first and second users based on a priority of one of the first and second users over the other of the first and second users;

means for updating the corresponding object in the master database;

means for sending a copy of the updated object to the replicated database;

means for receiving the copy of the updated object from the server in response to the update request; and

means for replacing the changed object in the replicated database with the copy of the updated object from the server.

67-68. -68. (canceled)

69. A computer-readable medium comprising program instructions for synchronizing objects, by performing the steps of:

receiving an update request from a first user at a synchronization server, the update request including an identifier and a version stamp for an object in a first replicated database, the update request further including an identity of the first user;

comparing the identifier and the version stamp of the update request with an identifier and a version stamp of the object in a master database to determine whether a conflict exists, wherein the object is updateable by a plurality of users, wherein a plurality of replicated databases are associated with the plurality of users;

if a conflict exists where an update to an object in the master database has been performed by a second user in the plurality of users,

resolving the conflict according to at least one conflict resolution rule configured to override the update by one of the first and second users based on a priority of one of the first and second users over the other of the first and second users, where the version stamp of the update request and the version stamp of the object in the master database provide update sequence information that is used to determine if the conflict exists;

updating the object in the master database; and

sending a copy of the updated object to the first replicated database in the plurality of replicated databases.

70. The computer-readable medium of claim 69, wherein the step of updating the object includes incrementing the version stamp of the object.

71. The computer-readable medium of claim 69, wherein the update request includes a before value and an after value of a changed property.

72. The computer-readable medium of claim 69, wherein the master database is coupled to an application server that includes the synchronization server.

73. The computer-readable medium of claim 69, wherein the first replicated database is coupled to a first remote device and the second replicated database is coupled to a second remote device.

74. The computer-readable medium of claim 73, wherein the first replicated database communicates with the synchronization server via a network.

75. The computer-readable medium of claim 73, wherein the first remote device includes a synchronization processor configured to access the first replicated database.