Method and system for database synchronization

• US 20040010510A1
• Filed: 07/10/2002
• Published: 01/15/2004
• Est. Priority Date: 07/10/2002
• Status: Abandoned Application

• Current Assignee: Solid Information Technology Oy (International Business Machines Corporation)
• Original Assignee: Solid Information Technology Oy (International Business Machines Corporation)
• Inventors: Hotti, Timo
• Application Number:
  US10/191,114
• Publication Number:
  US 20040010510A1
• Time in Patent Office: Days
• US Class Current: 707/103R
• 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/275 Synchronous replication

Abstract

The invention relates to a method, arrangement and content router node for database synchronization. Especially the invention relates to synchronization messaging using a content routing mechanism. In particular the invention relates to content routing where data elements are delivered between master and replica databases through a number of content router nodes. The content router node receives the data elements and decides next recipient of the data elements based on the data element and routing information of the current content router node or any of the route'"'"'s previous content router nodes or the originating database. The content router node may also be arranged to wait a specified wait time for other data elements whose next destination address is the same node as that of the received data elements and if the addresses are same, the content router node aggregates the received data elements into one message.

Claims

1. A method for data synchronization, characterized in that at least one data element is delivered between at least one master and replica database through at least one content router node, where next recipient of the data element is selected in the content router node based on destination address of the data element and routing information of the current content router node or any of the route'"'"'s previous content router nodes or the originating database.

2. A method according to claim 1, characterized in that at least one second data element, whose next destination address is the same node as that of said data element is aggregated into one message with said data element.

3. A method according to claim 1, characterized in that said content router node is at least one of the following:

edge router, core router, database server managing at least one master database and database server managing at least one replica database.

4. A method according to claim 3, characterized in that said database servers have at least one specific edge router, through which the servers transmit data elements.

5. A method according to claim 3, characterized in that said edge router node serves a number of database servers.

6. A method according to claim 3, characterized in that said edge router node has information of a number of core routers and/or other edge routers to which said edge router can forward the messages it receives from its database server.

7. A method according to claim 3, characterized in that said node maintains a data communication connection with at least one other content router or database server node also during periods when no data is transmitted between the nodes.

8. A method according to claim 2, characterized in that a wait time is specified for said node that it may stay idle after receiving the first data element for waiting other data elements to be aggregated with the first element, if next node of the other data elements is the same as that of the first data element.

9. A method according to claim 1, characterized in that at least one router node keeps the data element to be delivered in a persistent store until the data element has been successfully processed by the recipient database server.

10. A method according to claim 1, characterized in that delivered data between the database nodes is encrypted using at least one disposable key assigned by the receiving database.

11. A method according to claim 1, characterized in that management information about said router node is gathered into a local replica database and synchronized with a master database of a separate router manager node.

12. A method according to claim 11, characterized in that said router manager node analyses and summarizes management information of said router nodes and updates routing information of at least one router node based on the analysed management information.

13. A method according to claim 1, characterized in that configuration of said routing information of the content router nodes is managed by a separate router manager node, which has a global view of at least part of the network arrangement.

14. A method according to claim 1, characterized in that gathering and analysing of statistics and updating of routing information is performed in near real time.

15. A method according to claim 1, characterized in that the master database executes the received synchronization message and assembles the reply message to be delivered to the replica database.

16. A method according to claim 1, characterized in that the method is compatible with at least one of the following communication specifications:

TCP/IP, Ethernet, CDMA, GSM, HSCSD, GPRS, WCDMA, EDGE, Bluetooth, UMTS, Teldesic, Iridium, Inmarsat, WLAN, DIGI-TV, ISDN, xDSL, RPC, Home-PNA, and imode.

17. A method according to claim 1, characterized in that at least one of the following operating systems is used in at least one node:

Unix, MS-Windows, Symbian, VxWorks, OSE, QNX, Linux, PalmOS and GEOS.

18. An arrangement for data synchronization through content routing network, characterized in that the arrangement comprises at least one database server managing a replica database, at least one database server managing a master database and an information network comprising a number of content router nodes, wherein the arrangement further comprises means for delivering at least one data element between at least one master and replica database through a number of content router nodes and means for selecting next recipient of the data element in the content router node based on destination address of the data element and routing information of the current content router node or any of the route'"'"'s previous content router nodes or the originating database.

19. An arrangement according to claim 18, characterized in that the arrangement comprises means for aggregating at least one second data element, whose next destination address is the same node as that of said first data element into one message with said first data element.

20. An arrangement according to claim 18, characterized in that the said content router node is at least one of the following:

edge router, core router, database server managing at least one master database and database server managing at least one replica database.

21. An arrangement according to claim 18, characterized in that said database servers have at least one specific edge router, through which the servers transmit data elements.

22. An arrangement according to claim 20, characterized in that said edge router node is arranged to serve a number of database servers that each manage at least one database.

23. An arrangement according to claim 20, characterized in that said edge router node is arranged to be in data connection with a number of core routers and/or other edge routers to which said edge router can forward the messages it receives from its database server.

24. An arrangement according to claim 20, characterized in that said content router node is arranged to maintain a data communication connection with at least one other router or database server node also during periods when no data is transmitted between the nodes.

25. An arrangement according to claim 18, characterized in that said node is arranged to wait a specified wait time that it may stay idle after receiving the first data element for waiting other data elements and further said node is arranged to aggregate other data elements with the first element, if next node of the other data elements is the same as that of the first data element.

26. An arrangement according to claim 18, characterized in that at least one router node is arranged to keep the data element to be delivered in a persistent store until the data element has been successfully processed by the recipient database server.

27. An arrangement according to claim 18, characterized in that management information about said router node is gathered into a local replica database and synchronized with a master database of a separate router manager node.

28. An arrangement according to claim 27, characterized in that said router manager node is arranged to analyse and summarize management information of said router nodes and to update routing information of at least one router node based on the analysed management information.

29. An arrangement according to claim 18, characterized in that a separate router manager node is arranged to manage routing information of the routers, where the separate router manager node has a global view of at least part of the network arrangement.

30. An arrangement according to claim 18, characterized in that the master database is arranged to execute the received message and assemble the reply message to be delivered to the replica database through the network of router nodes.

31. An arrangement according to claim 18, characterized in that the arrangement is compatible with at least one of the following communication specifications:

TCP/IP, Ethernet, CDMA, GSM, HSCSD, GPRS, WCDMA, EDGE, Bluetooth, UMTS, Teldesic, Iridium, Inmarsat, WLAN, DIGI-TV, ISDN, xDSL, RPC, Home-PNA, and imode.

32. An arrangement according to claim 18, characterized in that said node has at least one of the following operating systems is used in at least one node:

Unix, MS-Windows, Symbian, VxWorks, OSE, QNX, Linux, PalmOS and GEOS.

33. A content router node for content routing of data synchronization messages, characterized in that the content router node is arranged to deliver at least one data element between a master and replica database, and further the content router node is arranged to select next recipient of the data element based on destination address of the data element and routing information of the current content router node or any of the route'"'"'s previous content router nodes or the originating database.

34. A content router node according to claim 33, characterized in that the router node is arranged to aggregate at least one second data element, whose next destination address is the same node as that of the first data element into one message with the first data element.

35. A content router node according to claim 33, characterized in that the content router node comprises application logic to implement the message routing logic.

36. A content router node according to claim 33, characterized in that said node is at least one of the following:

edge router, core router, database server managing a master database and database server managing a replica database.

37. A content router node according to claim 33, characterized in that said router node is edge router and it is arranged to be in data connection with at least one database server from which the router node receives data elements to be delivered.

38. A content router node according to claim 33, characterized in that said content router node is edge router and it is arranged to serve a number of database servers.

39. A content router node according to claim 33, characterized in that an edge router node is arranged to be in data connection with at least one core router to which said edge router can forward the messages it receives from its database servers.

40. A content router node according to claim 33, characterized in that said content router node is arranged to maintain a data communication connection with at least one other content router or database server node also during periods when no data is transmitted between the nodes.

41. A content router node according to claim 33, characterized in that said content router node is arranged to wait a specified wait time that it may stay idle after receiving the first data element for waiting other data elements and further said node is arranged to aggregate other data elements with the first element, if next node of the other data elements is the same as that of the first data element.

42. A content router node according to claim 33, characterized in that at least one content router node is arranged to keep the data element to be delivered in a persistent store until the data element has been successfully processed by the recipient database.

43. A router node according to claim 33, characterized in that said node is arranged to gather management information about said router node into a local replica database and synchronize it with a master database of a separate router manager node.

44. A content router node according to claim 33, characterized in that the content router node has a local database comprising routing information and a separate router manager node is arranged to manage the routing information of the router nodes, where the separate router manager node has a global view of at least part of the network arrangement.

45. A content router node according to claim 33, characterized in that the content router node comprises a separate storage for incoming and outgoing data elements and a program logic means for moving the flow data elements from an inbox to an appropriate outbox.

46. A content router node according to claim 33, characterized in that the content router node is compatible with at least one of the following communication specifications:

TCP/IP, Ethernet, CDMA, GSM, HSCSD, GPRS, WCDMA, EDGE, Bluetooth, UMTS, Teldesic, Iridium, Inmarsat, WLAN, DIGI-TV, ISDN, xDSL, RPC, Home-PNA, and imode.

47. A content router node according to claim 33, characterized in that said content router node has at least one of the following operating systems is used in at least one node:

Unix, MS-Windows, Symbian, VxWorks, OSE, QNX, Linux, PalmOS and GEOS.