Systems and methods for notifying multiple systems and applications of changes to data attributes

• US 7,865,464 B2
• Filed: 08/03/2007
• Issued: 01/04/2011
• Est. Priority Date: 09/29/2006
• Status: Expired due to Fees

• Current Assignee: Presenceid Incorporated
• Original Assignee: Presenceid Incorporated
• Inventors: Walker, Douglas Jock
• Primary Examiner(s): Vo; Tim T.
• Assistant Examiner(s): SANDERS, AARON J
• Application Number:
  US11/833,857
• Publication Number:
  US 20080082989A1
• Time in Patent Office: 1,250 Days
• Field of Search: None
• US Class Current: 707/612
• 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/289 Object oriented databases

Abstract

A system for managing changes to identity data is described. A first spoke managing system is described which includes a first database, a first application in communication with the first database, and a first spoke manager in communication with the first application. A first message is generated including a plurality of common data attributes. The first message is sent to a hub managing system. The hub managing system includes a hub manager. The first message including the plurality of common data attributes is received from the first spoke managing system. A plurality of common data attributes are updated. A determination is made if a unique data attribute that uniquely identifies a reference object is being updated. A second message is generated based on the determination. A third message is generated based on the updates of the plurality of common data attributes. The second message and third message are sent.

Claims

1. A system for managing changes to identity data, the system comprising:

a first spoke managing system, wherein the first spoke managing system comprises;

a first database comprising a plurality of reference objects, wherein each reference object includes data attributes related to the reference object;

a first application in communication with the first database; and

a first spoke manager in communication with the first application, the first spoke manager being configured to;

generate a first synchronization message in a first data format readable by the first spoke manager including a plurality of one or more common data attributes and a first unique data attribute, wherein the first unique data attribute is a data attribute used by the first spoke manager to identify a particular reference object in the first database, wherein the one or more common data attributes are data attributes not used by the first spoke manager to identify a particular reference object;

translate the first synchronization message into a second data format, the second data format being different than the first data format, the second data format being readable by a hub managing system; and

send the first synchronization message to the hub managing system;

wherein the hub managing system comprises;

a hub manager, wherein the hub manager comprises;

a processor;

memory in electronic communication with the processor; and

instructions stored in the memory, the instructions being executable to;

receive the first synchronization message including the one or more common data attributes and the first unique data attribute from the first spoke managing system;

update a plurality of data attributes stored in a repository based upon the one or more common data attributes and the first unique data attribute received in the first synchronization message;

determine whether one of the data attributes stored in the repository that is being updated is a second unique data attribute that is used by a second spoke managing system to uniquely identify the particular reference object in a second database, the second database being part of the second spoke managing system, the second spoke managing system further comprising a second spoke manager, wherein at least one of the data attributes in the second database is different than at least one of the data attributes in the first database, wherein the second unique data attribute is different than the first unique data attribute, wherein the hub manager stores which of the data attributes stored in the repository constitutes the first unique data attribute and which of the data attributes stored in the repository constitutes the second data attribute;

generate a key change message when the second unique data attribute is being updated, wherein the key change message includes an update to the second unique data attribute;

generate a second synchronization message based on the updates of the plurality of data attributes stored in the repository;

send the key change message to the second spoke managing system when the key change message is generated; and

send the second synchronization message to the second spoke managing system, wherein the second synchronization message comprises the second unique data attribute, updated data attributes stored in the repository as well as any data attributes stored in the repository that were not updated, wherein the second spoke managing system determines which of the data attributes are applicable and ignores any remaining data attributes that are not applicable.

2. The system of claim 1, wherein the second spoke managing system further comprises:

a second application in communication with the second database, wherein the second spoke manager is in communication with the second application; and

wherein the second spoke manager is configured to;

generate a message in a data format that is readable by the hub managing system, the message including a plurality of data attributes; and

send the message to the hub managing system.

3. The system of claim 1, further comprising:

one or more additional second spoke managing systems, wherein each of the additional second spoke managing systems comprise;

a database;

an application in communication with the database; and

a spoke manager in communication with the application and the database, each of the additional second spoke managers being configured to;

generate a message in a data format from the application;

translate the message into a different data format; and

send the message in the different data format to the hub managing system.

4. The system of claim 1, wherein the first spoke manager is in communication with the first database.

5. The system of claim 1, wherein the first synchronization message is generated if a spoke manager detects a queue record stored in a database.

6. The system of claim 1, wherein the first unique data attribute includes data that uniquely identifies a certain entity.

7. The system of claim 3, wherein each of the one or more additional second spoke managing systems associates a unique data attribute with the reference object.

8. The system of claim 3, wherein each of the one or more additional second spoke managing systems sends the message to the hub managing system over a unique network connection.

9. The system of claim 3, wherein each of the one or more additional spoke managing systems is located in a different geographic region.

16. The system of claim 1, wherein if the second spoke manager is unavailable to receive the second synchronization message, the hub managing system delays the sending of the second synchronization message until the second spoke managing system is available.

10. A method for managing changes to identity data, the method comprising:

generating, by a first spoke manager, a first synchronization message in a first format readable by the first spoke manager, wherein the first spoke manager is in communication with a first application and a first database, wherein the first database comprises a plurality of reference objects, wherein each reference object includes data attributes related to the reference object, wherein the first synchronization message one or more common data attributes and a first unique data attribute, wherein the first unique data attribute is a data attribute used by the first spoke manager to identify a particular reference object in the first database, wherein the one or more common data attributes are data attributes not used by the first spoke manager to identify a particular reference object;

translating the first synchronization message into a second format, the second data format being different than the first data format, the second data format being readable by a hub managing system;

sending the first synchronization message in the second format to the hub managing system;

receiving the first synchronization message that includes the one or more common data attributes and the first unique data attribute at the hub managing system;

updating a plurality of data attributes stored in a repository based upon the one or more data common attributes and the first unique data attribute received in the first synchronization message;

determining whether one of the data attributes stored in the repository that is being updated is a second unique data attribute that is used by a second spoke managing system to uniquely identify the particular reference object in a second database, the second database being part of the second spoke managing system, the second spoke managing system further comprising a second spoke manager, wherein at least one of the data attributes in the second database is different than at least one of the data attributes in the first database, wherein the second unique data attribute is different than the first unique data attribute, wherein the hub manager stores which of the data attributes stored in the repository constitutes the first unique data attribute and which of the data attributes stored in the repository constitutes the second data attribute;

generating a key change message when it is determined that the second unique data attribute is being updated, wherein the key change message includes an update to the second unique data attribute;

generating a second synchronization message based on the updates of the plurality of data attributes stored in the repository;

sending the key change message to the second spoke manager when the key change message is generated; and

sending the second synchronization message to the second spoke manager, wherein the second synchronization message comprises the second unique data attribute, updated data attributes stored in the repository as well as any data attributes stored in the repository that were not updated, wherein the second spoke managing system determines which of the data attributes are applicable and ignores any remaining data attributes that are not applicable.

11. The method of claim 10, wherein the first spoke manager generates the first synchronization message if it detects a queue record in a database.

12. The method of claim 10, wherein a first unique data attribute includes data that uniquely identifies a certain entity.

13. The method of claim 10, further comprising one or more additional second spoke managing systems, wherein each of the additional second spoke managing systems associate a unique data attribute with the reference object.

14. The method of claim 10, wherein the first synchronization message is sent to the hub managing system over a networks.

15. The method of claim 13, wherein each of the additional second spoke managing systems is located in a different geographic region.