Method and system for client-based operations in server synchronization with a computing device

• US 7,526,575 B2
• Filed: 11/05/2001
• Issued: 04/28/2009
• Est. Priority Date: 09/28/2001
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Hansen, Aaron B., George, David J., Susser, Martin, Chung, Pi-Yu, Rabbers, David L.
• Primary Examiner(s): Kang; Paul H
• Application Number:
  US09/992,511
• Publication Number:
  US 20070016695A1
• Time in Patent Office: 2,731 Days
• Field of Search: 709/248, 709/217, 707/200, 707/201, 707/203, 707/1, 707/220, 707/221, 707/222, 707/217, 707/227, 717/171
• US Class Current: 709/248
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A method and system for synchronizing a main database of a server and a local database of a handheld device. A user can use an application residing in the handheld device to make transactions in the local database. In a synchronization operation, a synchronization client is used to: establish a connection between a server and the synchronization client; receive an identifier for the main database'"'"'s structure from the server; receive an identifier for the version of the handheld application from the server; send transaction information to the server; receive metadata to update the handheld application; and receive data extracted from the main database from the server. The synchronization client is also used to update filter information used by the server to reduce the size of the data downloaded to the handheld device.

Claims

1. A method, comprising:

establishing a connection between a server and a synchronization client associated with a handheld device, the server having access to a first database and the handheld device having access to a second database, the handheld device comprising an application configured to allow user write access to the second database, wherein the synchronization client is configured to use the connection in an operation to synchronize the second database and the first database;

receiving, from the server, first information indicative of a version of the application;

comparing the first information with information stored on the handheld device that is indicative of a version of the application on the handheld device;

updating the application on the handheld device using metadata received from the server if the first information does not compare equally with the information that is indicative of the version of the application on the handheld device;

receiving, from the server, data to update the second database.

2. The method of claim 1, further comprising the acts of receiving, from the server, second information indicative of a structure of the first database and determining whether the structure of the first database has been updated since a previous synchronization operation.

3. The method of claim 2, wherein determining whether the structure of the first database has been updated since the previous synchronization operation, comprises:

comparing the second information with information stored on the handheld device that is indicative of the structure of the first database when the previous synchronization operation was performed.

4. The method of claim 2, further comprising:

sending, to the server, filter information;

filtering data based on the filter information; and

receiving, from the server, the filtered data;

wherein receiving, from the server, the filtered data comprises;

receiving, from the server, a first set of data extracted from the first database when the structure of the first database has been updated since the previous synchronization operation, the first set of data including data that has not changed in the second database since the previous synchronization operation was performed.

5. The method of claim 2, further comprising:

sending, to the server, filter information;

filtering data based on the filter information; and

receiving, from the server, the filtered data;

wherein receiving, from the server, the filtered data comprises;

receiving, from the server, a second set of data extracted from the first database when the structure of the first database has not been updated since the previous synchronization operation, the second set of data not including data that has not changed in the second database since the previous synchronization operation was performed.

6. The method of claim 1, further comprising determining whether the application has been updated since a previous synchronization operation.

7. The method of claim 1 further comprising sending, to the server, information of transactions performed on the second database, wherein sending, to the server, information of transactions performed on the second database, comprises:

receiving, from the server, an identifier of information of a last transaction received by the server; and

sending, to the server, transaction information that includes an identifier for each transaction made after the last transaction received by the server.

8. The method of claim 7, wherein sending to the server information of transactions performed on the second database, further comprises:

receiving, from the server, error information when the server detects a transaction error;

providing an indication of the error information to a user; and

receiving input from the user to process the transaction error.

9. An system, comprising:

means for establishing a connection between a server and a synchronization client associated with a handheld device, the server having access to a first database and the handheld device having access to a second database, the handheld device comprising an application to allow user access to the second database, wherein the synchronization client is configured to use the connection in an operation to synchronize the second database and the first database;

means for receiving, from the server, first information indicative of a version of the application from the server;

means for comparing the first information with information stored on the handheld device that is indicative of a version of the application on the handheld device;

means for updating the application on the handheld device using metadata received from the server if the first information does not compare equally with the information that is indicative of the version of the application on the handheld device;

means for sending, to the server, information of transactions performed on the second database by the user via the handheld device.

10. The system of claim 9, further comprising:

means for receiving, from the server, second information indicative of a structure of the first database;

means for determining whether the structure of the first database has been updated since a previous synchronization operation.

11. The system of claim 10, wherein the means for determining whether the structure of the first database has been updated since the previous synchronization operation, comprises:

means for comparing the second information with information stored on the handheld device that is indicative of the structure of the first database when the previous synchronization operation was performed.

12. The system of claim 10, further comprising:

means for sending, to the server, user-specific filter information;

means for identifying, in the first database, data visible to the user of the synchronization client;

means for filtering the identified data based on the user-specific filter information; and

means for receiving, from the server, the filtered data;

wherein the means for receiving, from the server, the filtered data, comprises;

means for receiving, from the server, a first set of data extracted from the first database when the structure of the first database has been updated since a previous synchronization operation, the first set of data including data that has not changed in the second database since the previous synchronization operation was performed.

13. The system of claim 10, further comprising:

means for sending, to the server, user-specific filter information;

means for identifying, in the first database, data visible to the user of the synchronization client;

means for filtering the identified data based on the user-specific filter information; and

means for receiving, from the server, the filtered data;

wherein the means for receiving, from the server, the filtered data, comprises;

means for receiving, from the server, a second set of data extracted from the first database when the structure of the first database has not been updated since the previous synchronization operation, the second set of data not including data that has not changed in the second database since the previous synchronization operation was performed.

14. The system of claim 9, further comprising means for determining whether the application has been updated since a previous synchronization operation.

15. The system of claim 9, wherein the means for sending to the server information of transactions performed on the second database, comprises:

means for receiving, from the server, an identifier of information of a last transaction received by the server; and

means for sending, to the server, transaction information that includes an identifier for each transaction made after the last transaction received by the server.

16. The system of claim 15, wherein the means for sending to the server information of transactions performed on the second database, further comprises:

means for receiving, from the server, error information when the server detects a transaction error;

means for providing an indication of the error information to a user; and

means for receiving input from the user to process the transaction error.

17. A machine-readable medium having stored thereon a plurality of instructions that when executed by a handheld device cause the handheld device to perform operations comprising:

establishing a connection between a server and a synchronization client, the synchronization client associated with the handheld device, the server having access to a first database and the handheld device having access to a second database, the handheld device comprising an application configured to allow user access to the second database, wherein the synchronization client is configured to use the connection in an operation to synchronize the second database and the first database;

receiving, from the server, first information indicative of a version of the application;

comparing the first information with information stored on the handheld device that is indicative of a version of the application on the handheld device;

updating the application on the handheld device using metadata received from the server if the first information does not compare equally with the information that is indicative of the version of the application on the handheld device;

sending, to the server, filter information;

receiving, from the server, data filtered based on the filter information;

determining whether the handheld device has sufficient unused memory to store the filtered data.

18. The machine-readable medium of claim 17, wherein the plurality of instructions further comprise instructions that when executed by the handheld device cause the handheld device to perform operations comprising:

receiving, from the server, second information indicative of a structure of the first database;

determining whether the structure of the first database has been updated since a previous synchronization operation.

19. The machine-readable medium of claim 18, wherein the instructions for performing the operation of determining whether the structure of the first database has been updated since the previous synchronization operation, include instructions that when executed by the handheld device cause the handheld device to perform operations comprising:

comparing the second information with information stored on the handheld device that is indicative of the structure of the first database when the previous synchronization operation was performed.

20. The machine-readable medium of claim 18, wherein the instructions for performing the operation of receiving, from the server, the filtered data, include instructions that when executed by the handheld device cause the handheld device to perform operations comprising:

receiving, from the server, a first set of data extracted from the first database when the structure of the first database has been updated since the previous synchronization operation, the first set of data including data that has not changed in the second database since the previous synchronization operation was performed.

21. The machine-readable medium of claim 18, wherein the instructions for performing the operation of receiving, from the server, the filtered data, include instructions that when executed by the handheld device cause the handheld device to perform operations comprising:

receiving, from the server, a second set of data extracted from the first database when the structure of the first database has not been updated since the previous synchronization operation, the second set of data not including data that has not changed in the second database since the previous synchronization operation was performed.

22. The machine-readable medium of claim 17, wherein the plurality of instructions further comprises instructions that when executed by the handheld device cause the handheld device to perform operations comprising:

determining whether the application has been updated since a previous synchronization operation.

23. The machine-readable medium of claim 17, wherein the plurality of instructions further comprises instructions that when executed by the handheld device cause the handheld device to perform an operation of sending, to the server, information of transactions performed on the second database, wherein the instructions for performing the operation of sending, to the server, information of transactions performed on the second database, include instructions that when executed by the handheld device cause the handheld device to perform operations comprising:

receiving, from the server, an identifier of information of a last transaction received by the server; and

sending, to the server, transaction information that includes an identifier for each transaction made after the last transaction received by the server.

24. The machine-readable medium of claim 23, wherein the instructions for sending to the server information of transactions performed on the second database, include instructions that when executed by the handheld device cause the handheld device to perform operations comprising:

receiving, from the server, error information when the server detects a transaction error;

providing an indication of the error information to a user; and

receiving input from the user to process the transaction error.

25. A handheld device, comprising:

a local database;

a user interface coupled to the local database;

a transaction recorder coupled to the local database, wherein the transaction recorder is configured to record information related to changes made to the local database by a user of the handheld device via the user interface and to provide the recorded information to a server during a synchronization operation;

a metadata importer coupled to the user interface, wherein the metadata importer is configured to receive metadata from the server during the synchronization operation, the metadata comprising information for updating the user interface;

a data importer coupled to the local database, wherein the data importer is configured to receive data provided by the server during the synchronization operation, the data being a subset of data extracted from a main database based on visibility rules and filter information; and

a device configured to determine whether the handheld device has sufficient unused memory to store the data provided by the server.

26. The handheld device of claim 25, wherein the data importer is configured to determine whether a structure of the main database has been changed since a previous synchronization operation.

27. The handheld device of claim 26, wherein the data importer is configured to receive an identifier corresponding to the structure of the main database and compare the received identifier with a stored identifier corresponding to the structure of the main database when the previous synchronization operation was performed.

28. The handheld device of claim 26, wherein the data importer is configured to receive a first set of data extracted from the main database by the server when the structure of the main database has changed since the previous synchronization operation, the first set of data including data that has not changed in the local database since the previous synchronization operation was performed.

29. The handheld device of claim 26, wherein the data importer is configured to receive a second set of data extracted from the main database by the server when the structure of the main database has not changed since the previous synchronization operation, the second set of data omitting data that has not changed in the local database since the previous synchronization operation was performed.

30. The handheld device of claim 25, wherein the metadata importer is configured to determine whether the user interface has been updated since the previous synchronization operation.

31. The handheld device of claim 30, wherein the metadata importer is configured to receive version information of a most currently available user interface and to compare the received version information with version information corresponding to the user interface included in the handheld device.

32. The handheld device of claim 25, wherein the transaction recorder is configured to receive from the server an identifier of a last transaction recorded by the transaction for which transaction information was received by the server from the handheld device, and to send to the server transaction information that includes an identifier for each transaction made after the last transaction.

33. The handheld device of claim 32, wherein the transaction recorder is configured to receive from the sewer error information when the server detects a transaction error, to provide an indication of the error information to a user, and to receive input from the user to process the transaction error.

34. A method, comprising:

establishing a connection between a server and a synchronization client associated with a handheld device, the server having access to a first database and the handheld device having access to a second database, the handheld device comprising an application configured to allow user write access to the second database, wherein the synchronization client is configured to use the connection in an operation to synchronize the second database and the first database;

sending, to the server, information of transactions performed on the second database;

comparing the first information with information stored on the handheld device that is indicative of a version of the application on the handheld device;

receiving metadata from the server;

determining whether the handheld device has sufficient unused memory to store the metadata;

updating the application on the handheld device using metadata received from the server if the first information does not compare equally with the information that is indicative of the version of the application on the handheld device and if it is determined that the handheld device has sufficient unused memory to store the metadata;

receiving, from the server, data to update the second data base.