# US 2008/0082989 A1 · Systems and methods for notifying multiple systems and applications of changes to data attributes

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0082989 A1
- Document ID: US20080082989A1
- Status: Published application
- Kind: A1
- Application number: 11/833,857
- Filed: 2007-08-03
- Published: 2008-04-03
- Earliest claimed: 2006-09-29
- Assignees: PresenceID, Inc.
- Inventors: Douglas Jock Walker
- Web page: https://patentgrep.com/patent/US20080082989A1

## CPC

- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/289: {Object oriented databases}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim 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;
a first application in communication with the first database;
a first spoke manager in communication with the first application, the first spoke manager being configured to:
generate a first message including a plurality of common data attributes;
send the first message to a hub managing system;
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;
instructions stored in the memory, the instructions being executable to:
receive the first message including the plurality of common data attributes from the first spoke managing system;
update a plurality of common data attributes stored in a repository;
determine if a unique data attribute that uniquely identifies a reference object is being updated;
generate a second message if the unique data attribute is being updated;
generate a third message based on the updates of the plurality of common data attributes; and
send the second message and third message to one or more spoke managing systems.

### Claim 2 (depends on 1)

The system of claim 1, further comprising:
a second spoke managing system, wherein the second spoke managing system comprises:
a second database;
a second application in communication with the second database;
a second spoke manager in communication with the second application and the second database, the second spoke manager being configured to:
generate a message in a first data format including a plurality of common data attributes; and
send the message in the first data format to the hub managing system.

### Claim 3 (depends on 1)

The system of claim 1, further comprising:
a plurality of spoke managing systems, wherein the plurality of spoke managing systems comprise:
a plurality of databases;
a plurality of applications in communication with the plurality of databases;
a plurality of spoke managers in communication with the plurality of applications and the plurality of databases, the plurality of spoke managers being configured to:
generate a message in a plurality of data formats from the plurality of applications;
translate the message into the second data format; and
send the message in the second data format to the hub managing system.

### Claim 4 (depends on 1)

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

### Claim 5 (depends on 1)

The system of claim 1, wherein the instructions are further executable to update a plurality of common data attributes that are stored in a data repository.

### Claim 6 (depends on 1)

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

### Claim 7 (depends on 1)

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

### Claim 8 (depends on 3)

The system of claim 3, wherein each of the spoke managing systems within the plurality of spoke managing systems associate a unique data attribute with the reference object.

### Claim 9 (depends on 3)

The system of claim 3, wherein each of the spoke managing systems within the plurality of spoke managing systems send the message to the hub managing systems over a unique network connection.

### Claim 10 (depends on 3)

The system of claim 3, wherein each of the spoke managing systems within the plurality of spoke managing systems is located in a different geographic region.

### Claim 11

A method for managing changes to identity data, the method comprising:
generating a first synchronization message that includes information associated with common data attributes;
sending the message to a hub managing system;
receiving the message that includes common data attributes;
updating common data attributes;
determining if a unique data attribute that uniquely identifies a reference object is being updated;
generating a key change message if it is determined that the unique data attribute is being updated;
generating a second synchronization message that comprises information associated with common data attributes; and
sending the synchronization message and the key change message to the one or more spoke managers.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
generating the synchronization message in a first format;
translating the message into a second format; and
sending the synchronization message in the second format to a hub managing system.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
generating a message in a plurality of formats;
translating the message into a second format; and
sending the message in the second format to the hub managing system.

### Claim 14 (depends on 11)

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

### Claim 15 (depends on 14)

The method of claim 14, wherein the spoke manager communicates directly with the database.

### Claim 16 (depends on 11)

The method of claim 11, wherein a hub manager updates common data attributes stored in a data repository.

### Claim 17 (depends on 11)

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

### Claim 18 (depends on 11)

The method of claim 11, wherein each of the spoke managing systems within a plurality of spoke managing systems associate a unique data attribute with the reference object.

### Claim 19 (depends on 11)

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

### Claim 20 (depends on 18)

The method of claim 18, wherein each of the spoke managing systems within the plurality of spoke managing systems is located in a different geographic region.
