Peer-to-peer data concurrence processes and apparatus

• US 5,546,574 A
• Filed: 06/30/1994
• Issued: 08/13/1996
• Est. Priority Date: 06/30/1994
• Status: Expired due to Term

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.), BellSouth Corporation (AT&T, Inc.)
• Inventors: Shih, Jerry C., Grosskopf, Joseph R., Reuss, Carolyn K., Niaz, Hasan S., Watson, Paul T.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Lintz, Paul R.
• Application Number:
  US08/268,623
• Time in Patent Office: 775 Days
• Field of Search: 395/600, 395/200.12, 379/379, 379/58, 379/38, 379/201, 379/211, 379/58, 379/38, 379/201, 379/211, 370/60, 370/110.1
• US Class Current: 379/221.09
• CPC Class Codes: G06F 11/1402 Saving, restoring, recovering or retrying
• CPC Class Codes: H04Q 2213/13513 UPT - personal as opposed to terminal mobility, inc. number portability
• CPC Class Codes: H04Q 2213/13527 protocols - X.25, TCAP etc.
• CPC Class Codes: H04Q 2213/13547 subscriber, e.g. profile, database, database access
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/967 Peer-to-peer
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

Data concurrence processes and systems for maintaining concurrence of parallel sets of data stored in telecommunication Network Elements. According to a preferred embodiment of such processes, a Network Element such as a Service Node sends a Request Message to a second Network Element such as a Source Service Control Point in order to update data on that Source. The Source then sends a Request Message to the other Network Element, such as a Target Service Control Point, in order to update the parallel data contained in that Service Control Point. The Network Elements whose data are updated may send appropriate Result Messages in order to verify integrity of the data. The processes and apparatus also allow resynchronization of the data to occur at desired predetermined interval. These data concurrence processes and systems are particularly useful for implementing new services such as Personal Number Calling services in an intelligent telecommunications network, because they allow updating of the parallel databases quickly, efficiently, and with a minimum of required coordination, management and opportunity for lost communications, stale data, and mishandled call processing.

Claims

1. A process for maintaining peer to peer data concurrence in a plurality of concurrent and redundant databases, each of which is contained at least in part in its corresponding telecommunications Network Element, comprising the steps of:

a. providing to a Service Node information relating to changes that are desired in data stored in the databases and corresponding to a particular subscriber;

b. communicating to a Source Network Element that contains at least one of the databases, from the Service Node, a First Request Message that contains information about the data in the concurrent and redundant databases that is desired to be changed;

c. attempting to change information in the database in the Source Network Element based on information in the First Request Message received by the Source Network Element;

d. communicating to the Service Node from the Source Network Element a First Result Message regarding level of success in changing the data in the Source Network Element database;

communicating to a Target Network Element that contains the database that is desired to be maintained as concurrent to said database in the Source Network Element, from the Source Network Element, a Synchronization Request Message that contains information about the data that is desired to be changed in said database in the Target Network Element in Order to cause said Target Network Element database to be concurrent to said Source Network Element database;

f. attempting to change information in the Target Network Element database based on information in the Synchronization Request Message received by the Target Network Element in order to cause said Target Network Element database to be concurrent and redundant with said Source Network Element database; and

g. communicating to the Source Network Element from the Target Network Element a Second Result Message regarding level of success in changing the data in the Target Network Element database and thus whether said Target Network Element database is concurrent and redundant to said Source Network Element database.

2. A process according to claim 1 further comprising the step of setting out of sync flags corresponding to data changes which have not occurred in the Target Network Element database.

3. A process according to claim 1 further comprising the step of scheduling a resynchronization process if data changes have not occurred to cause said Source Network Element database and said Target Network Element database to be concurrent.

4. A process according to claim 1 in which, if appropriate Result Messages are not received indicating successful data changes, the process is discontinued.

5. A process according to claim 1 in which the Source Network Element and the Target Network Element are Service Control Points.

6. A process according to claim 1 in which the Request Messages and the Result Messages are sent using X.25 data links.

7. A process for maintaining peer to peer data concurrence in a pair of concurrent and redundant databases, each of which is contained in a corresponding telecommunications Service Control Point, comprising the steps of:

a. providing to a Service Node information relating to changes that are desired in data stored concurrently and redundantly in the databases and corresponding to a particular subscriber;

b. communicating to one of the Service Control Points that contains one of the databases (the "Source SCP"), from the Service Node, a First Request Message that contains information about the data in the databases that is desired to be changed;

c. attempting to change information in said Source SCP database based on information in the First Request Message received by the Source SCP;

d. communicating to the Service Node from the Source SCP a First Result Message regarding level of success in changing the data in the Source SCP database;

e. communicating to a Target Service Control Point ("Target SCP") that contains the database that is desired to be maintained as concurrent and redundant to said database in the Source SCP, from the Source SCP, a Synchronization Request Message that contains information about the data that is desired to be changed in said Target SCP database in order to cause said Target SCP database to be concurrent and redundant to said Source SCP database;

f. attempting to change information in the Target SCP database based on information in the Synchronization Request Message received by the Target SCP in order to cause said Target SCP database to be concurrent and redundant to said Source SCP database; and

g. communicating to the Source SCP from the Target SCP a Second Result Message regarding level of success in changing the data in the Target SCP database and thus whether said Target SCP database is concurrent with said Source SCP database.

8. A process according to claim 7 in which Second Result Messages are also sent to other Service Control Points in addition to the one which sent the Synchronization Request Message.

9. A process according to claim 7 in which the Request Messages and the Result Messages are sent using X.25 data links.

10. Apparatus for maintaining peer to peer data concurrence in a plurality of concurrent and redundant databases, each contained in a corresponding Network Element in a telecommunications network, comprising:

a. a Service Node adapted to receive information regarding data in at least one of the databases which is desired to be changed;

b. means in the Service Node for preparing an original update request message that contains information about the data that is desired to be changed;

c. means for communicating the original update request message to a Source Network Element in Order to change data in the concurrent and redundant database in the Source Network Element;

d. means in the Source Network Element for changing information in the concurrent and redundant database in the Source Network Element based on information in the original update request message received by the Source Network Element;

e. means in the Source Network Element for preparing a synchronization update request message that contains information about the data that is desired to be changed;

f. means for communicating the synchronization update request message to a Target Network Element in order to change data in the concurrent and redundant database in the Target Network Element that is concurrent and redundant to the concurrent and redundant database in the Source Network Element; and

g. means in the Target Network Element for changing information in the concurrent and redundant database in the Target Network Element based on information in the synchronization update request message received by the Target Network Element.

11. Apparatus according to claim 10 further comprising means in each Network Element for preparing a synchronization result message to be sent to the Network Element from which a corresponding synchronization update request message was received, regarding level of success in accomplishing data changes requested in the request message to the concurrent and redundant database in the Network Element sending the result message.

12. Apparatus according to claim 10 in which the Source Network Element and the Target Network Element are Service Control Points.

13. Apparatus according to claim 10 in which the means for sending the update request messages and the synchronization update request messages comprises X.25 data links.