Sharing Data on Mobile Devices

• US 20120036199A1
• Filed: 08/09/2010
• Published: 02/09/2012
• Est. Priority Date: 08/09/2010
• Status: Active Grant

• Current Assignee: iAnywhere Solutions Incorporated (SAP SE)
• Original Assignee: iAnywhere Solutions Incorporated (SAP SE)
• Inventors: Slee, Thomas Stephen, Graham, James David, Hurst, Adam
• Granted Patent: US 9,977,819 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• 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: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning

Abstract

System, methods and articles of manufacture for replicating relational data on multiple nodes. An embodiment comprises receiving an update request message from a node, wherein the update request message comprises a node identification and an application identification, accessing an application schema based on the application identification, identifying a partition residing in the application schema based on the node identification, accessing a server schema, identifying a second partition residing in the server schema based on the application identification, determining at least one data change stored in the second partition that changes data associated with the first partition, retrieving at least one data change from the second partition, formatting data change in an update response message, and transmitting the update response message to the node.

Claims

1. A method for retrieving data from a central server system, comprising:

receiving an update request message from a node, wherein the update request message comprises a node identification and an application identification, and wherein the node comprises a computing device, an Internet browser and a database and wherein the application identification identifies a database application;

accessing an application schema in a central database server based on the application identification;

determining a partition of the application schema based on the node identification;

determining a set of operations that describe data changes to the database application;

retrieving at least one operation from the set of operations in the central database server that change data in the partition;

formatting the at least one operation in an update response message; and

transmitting the update response message to the node.

2. The method of claim 1, wherein the determining a set of operations comprises determining a second partition that includes a list of nodes associated with the database application and selecting the node having the node identification from the list of nodes.

3. The method of claim 1, wherein the formatting comprises of storing the at least one operation in a text document.

4. The method of claim 1, wherein the determining the set of operations comprises of the operations posted to the central database after a previous update message request.

5. The method of claim 1, wherein at least one table in the application schema comprises at least one primary key and at least one foreign key, and the determining the partition comprises determining if at least one primary key is equal to at least one foreign key.

6. The method of claim 1, wherein the partition includes data for one user of the node, a group of users or a subset of a group of users.

7. The method of claim 1, further comprising:

determining a frequency with which data changes post to the central server system;

determining a time the node is operable to send a next update request message based on the frequency; and

transmitting, the determined time to the node.

8. A central server system for replicating data, comprising:

a receiver, configured to receive an update request message from a node, wherein the update request message comprises a node identification and an application identification, wherein the node comprises a computing device, an Internet browser and a database and wherein application identification identifies a database application;

a memory, configured to store an application schema and a set of operations, wherein the set of operations describe data changes made to the database application;

a processor, configured to determine a partition of the application schema based on the node identification;

the processor, further configured to determine at least one operation associated with the partition and retrieve the at least one operation; and

a transmitter, configured to transmit the at least one operation to the node.

9. The system of claim 8, wherein the processor, determines at least one operation associated with the partition by evaluating each operation in the set of operations and determining a second partition that includes a list of nodes associated with the database application and selecting the node having the node identification from the list of nodes.

10. The system of claim 8, wherein the processor, further configured to store the at least one operation in a text document.

11. The system of claim 8, wherein at least one table in the application schema, further comprises at least one primary key and at least one foreign key and wherein the processor determines the partition by determining if at least one primary key is equal to at least one foreign key.

12. The system of claim 8, wherein the partition includes data for one user of the node, a group of users or a subset of a group of users.

13. The system of claim 8, wherein:

the processor is further configured to determine a frequency of the data changes posted to the central server system and to determine a time the node is operable to send a second update request message based on the frequency; and

wherein the transmitter is further configured to transmit the determined time to the node.

14. An article of manufacture including a computer-readable medium having instructions stored thereon that, when executed by a computing device, cause said computing device to perform operations comprising:

receiving an update request message from a node, wherein the update request message comprises a node identification and an application identification, and wherein the node comprises a computing device, an Internet browser and a database and wherein the application identification identifies a database application;

accessing an application schema in a central database server based on the application identification;

determining a partition of the application schema based on the node identification;

determining a set of operations that describe data changes to the database application;

retrieving at least one operation from the set of operations in the central database server that change data in the partition;

formatting the operation in an update response message; and

transmitting the update response message to the node.

15. The method of claim 14, wherein the determining a set of operations comprises determining a second partition that includes a list of nodes associated with the database application and selecting the node having the node identification from the list of nodes.

16. The method of claim 14, wherein the formatting comprises of storing the at least one operation in a text document.

17. The article of manufacture of claim 14, wherein the determining the set of operations comprises of the operations posted to the central database after a previous update message request.

18. The article of manufacture of claim 14, wherein at least one table in the application schema comprises at least one primary key and at least one foreign key, and the determining the partition comprises determining if at least one primary key is equal to at least one foreign key.

19. The article of manufacture of claim 14, wherein the partition includes data for one user of the node, a group of users or a subset of a group of users.

20. The article of manufacture of claim 14, further comprising:

determining a frequency with which data changes post to the central server system;

determining a time the node is operable to send a next update request message based on the frequency; and

transmitting, the determined time to the node.