Data change controller

• US 10,255,339 B2
• Filed: 12/23/2013
• Issued: 04/09/2019
• Est. Priority Date: 12/23/2013
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Alonso Alarcon, Antonio, Åstrom, Bo, Castellanos Zamora, David, Lemark, Jan
• Primary Examiner(s): Arjomandi, Noosha
• Application Number:
  US15/106,638
• Publication Number:
  US 20160335337A1
• Time in Patent Office: 1,933 Days
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• 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 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064

Abstract

A technique is disclosed for synchronizing first and second data sets stored in a data repository. A method includes triggering, by the data repository, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply data modification(s) on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller. The method includes receiving, by the data repository, a notification event response message relating to the ongoing transaction from the data consistency controller, the notification event response message indicating to the data repository whether (i) to commit the data modification(s) instructed by the commit order on the first data set and corresponding data modification(s) on the second data set, or (ii) to roll back the data modification(s) instructed by the commit order on the first data set.

Claims

1. A method of synchronising a first data set and a second data set stored in a data repository, the method comprising the steps of:

triggering, by the data repository, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply one or more data modifications on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller;

receiving, by the data consistency controller, the notification event message triggered by the data repository;

transmitting, by the data consistency controller, a notification event response message relating to the ongoing transaction to the data repository, the notification event response message indicating to the data repository whether

to commit the one or more data modifications instructed by the commit order on the first data set and one or more corresponding data modifications on the second data set, or

to roll back the one or more data modifications instructed by the commit order on the first data set;

receiving, by the data repository, the notification event response message relating to the ongoing transaction from the data consistency controller; and

receiving, by the data repository, one or more request messages relating to the ongoing transaction from the data consistency controller, the one or more request messages requesting the data repository to apply one or more additional data modifications on the first data set and one or more corresponding additional data modifications on the second data set.

2. The method of claim 1, the method further comprising the steps of:

committing, by the data repository, the one or more data modifications instructed by the commit order on the first data set and the one or more corresponding data modifications on the second data set, or

rolling back, by the data repository, the one or more data modifications instructed by the commit order on the first data set,

depending on the indication by the notification event response message.

3. The method of claim 2, the method further comprising the step of committing, by the data repository, all data modifications relating to the ongoing transaction including the one or more additional data modifications on the first data set as well as all corresponding data modifications including the one or more corresponding additional data modifications on the second data set.

4. The method of claim 1, wherein the step of triggering the transmission of the notification event message is performed only if the commit order instructs the data repository to apply the one or more data modifications on specific data of the first data set.

5. The method of claim 1, wherein the method further comprises the step of including, by the data repository, a transaction identifier identifying the ongoing transaction into the notification event message.

6. The method of claim 1, wherein the method further comprises the step of reporting, by the data repository, a report message to the client, the report message indicating to the client whether the one or more data modifications on the first data set as instructed by the commit order, were committed or rolled back.

7. The method of claim 1, wherein the notification event message and the notification event response message are based on Simple Object Access Protocol (SOAP) and/or the ongoing transaction is a Lightweight Directory Access Protocol (LDAP) transaction.

8. The method of claim 1, wherein the first data set comprises data for circuit switched (CS) services and the second data set comprises data for IP Multimedia Subsystem (IMS) services.

9. The method of claim 1, wherein the first data set and the second data set are distributed data sets, the data repository is a distributed data repository, and the data consistency controller is a Distributed Data Consistency Controller (DDCC).

10. A method of supporting synchronisation of a first data set and a second data set stored in a data repository, the method comprising the steps of:

triggering, by the data repository, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply one or more data modifications on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller;

receiving, by the data repository, a notification event response message relating to the ongoing transaction from the data consistency controller, the notification event response message indicating to the data repository whether

to commit the one or more data modifications instructed by the commit order on the first data set and one or more corresponding data modifications on the second data set, or

to roll back the one or more data modifications instructed by the commit order on the first data set; and

receiving, by the data repository, one or more request messages relating to the ongoing transaction from the data consistency controller, the one or more request messages requesting the data repository to apply one or more additional data modifications on the first data set and one or more corresponding additional data modifications on the second data set.

11. A data repository for supporting synchronisation of a first data set and a second data set stored in the data repository, the data repository being configured to perform the method according to claim 10.

12. A method of controlling synchronisation of a first data set and a second data set stored in a data repository, the method comprising the steps of:

receiving, by a data consistency controller, a notification event message triggered by the data repository in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply one or more data modifications on the first data set;

transmitting, by the data consistency controller, a notification event response message relating to the ongoing transaction to the data repository, the notification event response message indicating to the data repository whether

to commit the one or more data modifications instructed by the commit order on the first data set and one or more corresponding data modifications on the second data set, or

to roll back the one or more data modifications instructed by the commit order on the first data set; and

transmitting, by the data consistency controller, one or more request messages relating to the ongoing transaction to the data repository, the one or more request messages requesting the data repository to apply one or more additional data modifications on the first data set and one or more corresponding additional data modifications on the second data set.

13. A data consistency controller for controlling synchronisation of a first data set and sa econd data set stored in a data repository, the data consistency controller being configured to perform the method of claim 12.

14. A data repository for supporting synchronisation of a first data set and a second data set stored in the data repository, the data repository comprising:

a triggering component configured to trigger, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply one or more data modifications on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller; and

a receiving component configured to;

receive a notification event response message relating to the ongoing transaction from the data consistency controller, the notification event response message indicating to the data repository whether

to commit the one or more data modifications instructed by the commit order on the first data set and one or more corresponding data modifications on the second data set, or

to roll back the one or more data modifications instructed by the commit order on the first data set; and

receive one or more request messages relating to the ongoing transaction from the data consistency controller, the one or more request messages requesting the data repository to apply one or more additional data modifications on the first data set and one or more corresponding additional data modifications on the second data set.

15. The data repository of claim 14, the data repository being configured as a distributed data repository.

16. The data repository of claim 14, wherein the data repository is configured as a User Data Repository (UDR) in a User Data Convergence (UDC) environment.