SCALABLE RULE-BASED DATA SYNCHRONIZATION SYSTEMS AND METHODS

• US 20120023074A1
• Filed: 07/22/2010
• Published: 01/26/2012
• Est. Priority Date: 07/22/2010
• Status: Abandoned Application

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Liu, Tsehsin Jason, Ahamed, Vazir, Greene, Eric
• Application Number:
  US12/841,352
• Publication Number:
  US 20120023074A1
• Time in Patent Office: Days
• US Class Current: 707/694
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• 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

Exemplary scalable, rule-based data synchronization systems and methods are disclosed. An exemplary method includes at least one computing device executing a database trigger process in response to a database trigger event, the database trigger process including writing a general data message to a general message repository. The method further includes the at least one computing device executing an independent process including monitoring the general message repository, detecting the general data message in the general message repository, and processing, in response to the detecting of the general data message in the general message repository, the general data message in accordance with a predefined set of rules. Corresponding systems and methods are also disclosed.

Claims

1. A method comprising:

executing, by at least one computing device, a database trigger process in response to a database trigger event, the database trigger process including writing a general data message to a general message repository; and

executing, by the at least one computing device, an independent process including

monitoring the general message repository,

detecting the general data message in the general message repository, and

processing, in response to the detecting of the general data message in the general message repository, the general data message in accordance with a predefined set of rules.

2. The method of claim 1, further comprising completing, by the at least one computing device, the executing of the database trigger process directly following the writing of the general data message to the general message repository.

3. The method of claim 1, wherein the database trigger process includes no processing steps other than the writing of the general data message to the general message repository.

4. The method of claim 1, wherein:

the database trigger process is associated with a specific data element in a database; and

the method further comprises executing, by the at least one computing device before completion of the independent process, an additional database trigger process associated with the specific data element in the database in response to an additional database trigger event, the additional database trigger process including writing an additional general data message to the general message repository.

5. The method of claim 1, wherein the independent process is a background process executed independently of the database trigger process.

6. The method of claim 1, wherein:

the independent process is implemented as a stored procedure of a database; and

the predefined set of rules are maintained in a data element in the database.

7. The method of claim 1, wherein the database trigger process has a constant overhead.

8. The method of claim 1, wherein:

the general data message comprises an incoming data message;

the predefined set of rules comprises one or more data integrity checking rules; and

the processing of the general data message in accordance with the predefined set of rules comprises checking data integrity of the incoming data message in accordance with the one or more data integrity checking rules.

9. The method of claim 1, wherein:

the general data message comprises an outgoing data message;

the predefined set of rules comprises one or more routing rules; and

the processing of the general data message in accordance with the predefined set of rules comprises determining one or more destinations for the outgoing data message.

10. The method of claim 9, wherein the one or more destinations comprise one or more backend data subsystems.

11. The method of claim 9, wherein the processing of the general data message in accordance with the predefined set of rules further comprises:

generating one or more destination-specific data messages for the one or more destinations based on the outgoing data message in the general message repository and on the one or more routing rules; and

writing the one or more destination-specific messages to one or more destination-specific message queues corresponding to the one or more destinations.

12. The method of claim 11, wherein the writing of the one or more destination-specific messages to the one or more destination-specific message queues is performed at a physical computing layer.

13. The method of claim 1, embodied as computer-executable instructions on at least one non-transitory computer-readable medium.

14. A method comprising:

maintaining, by a data integration computing subsystem in a data integration database, integrated data that is mapped to local data maintained by a plurality of backend data subsystems; and

synchronizing, by the data integration computing subsystem, the integrated data in the data integration database and the local data maintained by the plurality of backend data subsystems in accordance with a predefined set of rules;

wherein the synchronizing comprises

executing, by the data integration computing subsystem in response to a database trigger event, a database trigger process associated with the data integration database, the database trigger process including writing a general data message to a general message repository, and

executing, by the data integration computing subsystem, an independent process including

monitoring the general message repository,

detecting the general data message in the general message repository, and

processing, in response to the detecting of the general data message in the general message repository, the general data message in accordance with the predefined set of rules.

15. The method of claim 14, wherein the synchronizing further comprises completing, by the data integration computing subsystem, the executing of the database trigger process directly following the writing of the general data message to the general message repository.

16. The method of claim 14, wherein the database trigger process includes no processing steps other than the writing of the general data message to the general message repository.

17. The method of claim 14, wherein the independent process is a background process executed independently of the database trigger process.

18. The method of claim 14, wherein:

the general data message comprises an incoming data message;

the predefined set of rules comprises one or more data integrity checking rules; and

the processing of the general data message in accordance with the predefined set of rules comprises checking data integrity of the incoming data message in accordance with the one or more data integrity checking rules.

19. The method of claim 14, wherein:

the general data message comprises an outgoing data message;

the predefined set of rules comprises one or more routing rules; and

the processing of the general data message in accordance with the predefined set of rules comprises determining one or more destinations for the outgoing data message.

20. The method of claim 14, embodied as computer-executable instructions on at least one non-transitory computer-readable medium.

21. A system comprising:

a data integration computing subsystem configured to

maintain integrated data that is mapped to local data maintained by a plurality of backend data subsystems,

synchronize the integrated data and the local data in accordance with a predefined set of rules;

an integration database within the data integration computing subsystem;

a database trigger process facility associated with the integration database and configured to execute a database trigger process in response to a database trigger event, the database trigger process including writing a general data message to a general message repository; and

an independent process facility configured to execute a background process independently of the database trigger process, the background process including

monitoring the general message repository,

detecting the general data message in the general message repository, and

processing, in response to the detecting of the general data message in the general message repository, the general data message in accordance with the predefined set of rules.

22. The system of claim 21, wherein:

the background process is implemented as a stored procedure in the integration database; and

the predefined set of rules are maintained as a data element in the integration database.

23. The system of claim 21, wherein the database trigger process has a constant overhead.