Processes and apparatus for maintaining data concurrence between databases in telecommunications networks

• US 5,579,318 A
• Filed: 06/30/1994
• Issued: 11/26/1996
• Est. Priority Date: 06/30/1994
• Status: Expired due to Term

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: BellSouth Corporation (AT&T, Inc.)
• Inventors: Watson, Paul T., Shih, Jerry C., Reuss, Carolyn K.
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): HOM, SHICK C
• Application Number:
  US08/269,917
• Time in Patent Office: 880 Days
• Field of Search: 370/94.2, 370/93, 370/103, 455/7, 455/13.1, 455/33.1, 455/33.2, 455/33.4, 375/356, 395/60
• US Class Current: 370/410
• CPC Class Codes: G06F 11/1402 Saving, restoring, recovering or retrying
• CPC Class Codes: H04J 3/14 Monitoring arrangements for SDH/SONET rings H04J3/085
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

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, an originating entity such as a Service Node sends a Request Message to a 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. Synchronization according to the preferred embodiment is preferably implemented by time stamping particular data in Request Messages at the first level, such as in the Service Node; the Request Messages and the updated data, together with Result Messages, then contain that time stamp which greatly simplifies reconciliation and verification efforts. The processes and apparatus also allow resynchronization of the data to occur at desired predetermined intervals, as well as data updating to occur during Area Transfer Operations in which particular subscriber data is being transferred from one mated pair of Network Elements to another. 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 data concurrence in a plurality of databases in a telecommunications network, including the steps of:

a. providing to a Control Network Element information regarding data in at least one of the databases which is desired to be changed;

b. communicating to a Source Network Element that contains at least one of the databases, via the Control Network Element, a first message that contains (i) information about the data that is desired to be changed; and

(ii) a time stamp;

c. changing information in the database in the Source Network Element based on information in the message received by the Source Network Element;

d. communication to a Target Network Element that contains at least one of the databases, via the Source Network Element, a second message that contains (i) information about the data that is desired to be changed; and

(ii) the time stamp; and

e. changing information in the database in the Target Network Element based on information in the message received by the Target Network Element.

2. The process according to claim 1 comprising the further step of communicating a result message to the Control Network Element via the Source Network Element regarding level of success in accomplishing data changes in at least the Source Network Element.

3. The process according to claim 1 comprising the further step of communicating a result message to the Source Network Element via the Target Network Element regarding level of success in accomplishing data changes in at least the Target Network Element.

4. The process according to claim 1 in which the step of communicating the first message to the Source Network Element that contains at least one of the databases, via the Control Network Element, includes the steps of attempting to send the first message to a first Network Element in a pair of network elements a predetermined number of times, upon failure of which attempts the first message is sent to the other Network Element in the pair (which Network Element is considered the Source Network Element).

5. The process according to claim 4 in which the step of communicating the message to the other Network Element further comprises the steps of attempting to send the message to that Network Element a predetermined number of times, upon failure of which attempts the Control Network Element discontinues the process of attempting to communicate to the Source and the Target Network Elements information about the data that is desired to be changed.

6. The process according to claim 1 in which the Control Network Element is a Service Node and the Source Network Element and the Target Network Element are Service Control Points.

7. The process according to claim 1 in which communication occurs using non-overlay communication links.

8. The process according to claim 1 in which communication occurs using Signalling System Seven architecture.

9. The process according to claim 1 in which the time stamps form the only basis for comparing currency of subscriber data between the Source and Target Network Elements.

10. The process for maintaining data concurrence in a plurality of databases, each of which is contained, at least in part, in its corresponding telecommunications Network Element, comprising the steps of:

a. providing to a Control Network Element 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, via the Control Network Element, a first message that contains (i) information about the data that is desired to be changed; and

(ii) a time stamp;

c. attempting to change information in the database in the Source Network Element based on information in the first message received by the Source Network Element;

d. communicating to the Control Network Element via the Source Network Element a second, result message regarding level of success in changing the data in the Source Network Element;

e. communicating to a Target Network Element that contains at least one of the databases, via the Source Network Element, a third message that contains (i) information about the data that is desired to be changed; and

(ii) the time stamp;

f. attempting to change information in the database in the Target Network Element based on information in the third message, received by the Target Network Element; and

g. communicating to the Source Network Element via the Target Network Element a fourth, result message regarding level of success in changing the data in the Target Network Element.

11. The process according to claim 10 in which the step of communicating the first message to a Source Network Element that contains at least one of the databases, via the Control Network Element, includes the steps of attempting to send the message to a first Network Element in a pair of network elements a predetermined number of times, upon failure of which attempts the message is communicated to the other Network Element in the pair (which Network Element is considered the Source Network Element).

12. The process according to claim 11 in which the step of communicating the message to the other Network Element further comprises the steps of attempting to send the message to that Network Element a predetermined number of times, upon failure of which attempts the Control Network Element discontinues the process of attempting to communicate to the Source and the Target Network Elements information about the data that is desired to be changed.

13. The process according to claim 10 further comprising the steps of setting out-of-sync flags corresponding to data changes which have not been updated.

14. The process according to claim 10 in which, if either of the result messages is not received indicating a successful data change, the process is discontinued.

15. The process according to claim 10 in which the Control Network Element is a Service Node and the Source Network Element and the Target Network Element are Service Control Points.

16. The process according to claim 10 in which communication occurs using non-overlay communications links.

17. The process according to claim 10 in which communication occurs using Signalling System Seven architecture.

18. The process according to claim 10 in which the time stamps form the only basis for comparing currency of subscriber data between the Source and Target Network Elements.

19. The process for maintaining data concurrence in a pair of databases, each contained in a corresponding telecommunications Network Element, including the step of:

a. providing to a Control Network Element information corresponding to a subscriber that is desired to be changed;

b. attempting to communicate to a first Network Element in the pair, via the Control Network Element, and for a predetermined number of attempts, a first message that contains information about the data that is desired to be changed and a time stamp;

c. if the attempts stated in step (b) are successful, and relevant data is located, changing data in the first Network Element, sending a second, success result message to the Control Network Element, and attempting to communicate to the second Network Element in the pair for a predetermined number of attempts a third message that contains information about the data that is desired to be changed and the time stamp;

d. if the attempts stated in step (c) are successful, interpretation of the third message is successful, and relevant data is located, changing data in the second Network Element and sending a fourth, success result message to the first Network Element;

e. if the attempts stated in step (b) fail, attempting to communicate to the second Network Element in the pair, via the Control Network Element, and for a predetermined number of attempts, a second message that contains information about the data that is desired to be changed and the time stamp; and

doing the following;

1. if the attempts stated in step (e) (excluding these subparts (1)-(3)) are successful, interpretation of the second message is successful, and relevant data is located, changing data in the second Network Element, sending a fourth, success result message to the Control Network Element, and attempting to communicate to the first Network Element in the pair for a predetermined number of attempts a fifth message that contains information about the data that is desired to be changed and the time stamp;

2. if the attempts stated in step (1) are successful, interpretation of the fifth message is successful, and relevant data is located, changing data in the first Network Element and sending a sixth, success result message to the second Network Element; and

3. if the efforts stated in steps (1) or (2) fail, sending a seventh, failure message and discontinuing the data concurrence process at least temporarily; and

f. if the attempts stated in step (e) to communicate to the Second Network Element fail, discontinuing the data concurrence process at least temporarily.

20. The process according to claim 19 in which the steps of sending a success result message comprise the steps of attempting to send the success result message a predetermined number of attempts and if the attempts are unsuccessful, discontinuing the data concurrence process at least temporarily.

21. The process according to claim 19 in which, if data is not changed successfully, an out of sync flag is set in the relevant database.

22. The process according to claim 21 further comprising the step of resynchronizing, between the databases, and at a subsequent time, all data marked with out of sync flags.

23. The process for synchronizing data in a pair of databases, each contained in a corresponding telecommunications Network Element and each containing data relating to a plurality of subscribers, the currency status of at least some of the data for each subscriber being denoted by at least one flag, including the steps of:

a. at a predetermined time, reviewing the data in the database of a first of the Network Elements for presence of out-of-synchronization flags and if at least one is found, determining whether the second of the Network Elements is out of synchronization;

b. if out-of-synchronization flags exist in the first Network Element and the second Network Element is determined to be out of synchronization, sending a resync message to the second Network Element via the first Network Element a predetermined number of times, which resync message contains information relating to at least one subscriber and a time stamp;

c. changing data in the second Network Element based on the information contained in the resync message and resetting flags corresponding to such changed data;

d. again, conducting step (a) and, if necessary, steps (b) through (d) until no data is found to be out of synchronization and then discontinuing the process.

24. The process according to claim 23 in which, if no out-of synchronization flags are found or the second of the Network Elements is not out-of-synchronization in step (a), the process is discontinued for a predetermined time.

25. The process according to claim 24 in which includes, if the resync message fails to reach the second Network Element, the step of discontinuing the process for a predetermined time.

26. The process according to claim 23 which is initiated and terminated automatically.

27. The process according to claim 23 which is initiated via manual intervention.

28. The process for maintaining data concurrence in a plurality of databases in a telecommunications network, including the steps of:

a. communicating to a Source Network Element that contains at least one of the databases, a first request message that contains information about the data that is desired to be changed;

b. changing information in the database in the Source Network Element based on information in the first request message received by the Source Network Element;

c. communicating to a Target Network Element, that contains at least one of the databases, using platform based logic in the Source Network Element, a second request message that contains information about the data that is desired to be changed; and

d. changing information in the database in the Target Network Element based on information in the second request message received by the Target Network Element.

29. The process according to claim 28 in which the request messages are different from each other.

30. The process according to claim 28 in which the request messages are the same as each other.

31. The process according to claim 28 comprising the further steps of communicating a result message to the Network Element from which a corresponding request message was received regarding level of success in accomplishing data changes in the Network Element that received the request message.

32. The process according to claim 31 in which result messages are also sent to other Network Elements in addition to the one which sent the request message.

33. The process according to claim 28 in which at least one request message contains timing information that is used by at least one Network Element to determine currency of its data.

34. The process according to claim 33 in which all request messages contain the timing information from the same source, and that timing information is the sole timing information that is employed to determine currency of at least some of the data stored in the Network Elements.

35. The process according to claim 28 in which the Source Network Element may be any Network Element that contains relevant data, and if a request message fails to be communicated to a designated Source Network Element, an attempt is made to send a request message to another Network Element which then becomes the Source Network Element.

36. The process for maintaining data concurrence in a plurality of databases in a telecommunications network, including the steps of:

a. providing to a Control Network Element information regarding data in at least one of the databases which is desired to be changed;

b. communicating to a Source Network Element that contains at least one of the databases, via the control Network Element, a first message that contains (i) information about the data that is desired to be changed; and

(ii) a first time stamp;

c. changing information in the database in the Source Network Element based on information in the first message received by the Source Network Element;

d. communicating to a First Target Network Element that contains at least one of the databases, via the Source Network Element, a second message that contains (i) information about the data that is desired to be changed; and

(ii) the time stamp;

e. changing information in the database in the First Target Network Element based on information in the second message received by the First Target Network Element;

f. communicating to a Second Target Network Element that contains at least one of the databases, via the Source Network Element, a third message that contains (i) information about the data that is desired to be changed; and

(ii) the time stamp;

g. changing information in the database in the Second Target Network Element based on information in the third message received by the Second Target Network Element;

h. communicating to a Third Target Network Element that contains at least one of the databases, via the Second Target Network Element, a fourth message that contains (i) information about the data that is desired to be changed; and

(ii) the time stamp; and

i. changing information in the database in the Third Target Network Element based on information in the fourth message received by the Third Target Network Element.

37. The process according to claim 36 comprising the further steps of communicating a result message to the Network Element from which a corresponding request message was received regarding level of success in accomplishing data changes in the Network Element that received the request message.

38. The process according to claim 36 in which the step of communicating a message to Network Element that contains at least one of the databases includes the steps of attempting to send the message to the Network Element a predetermined number of times, upon failure of which attempts the message is communicated to another Network Element.

39. The process according to claim 38 in which the step of communicating the second message to the First Target Network Element further comprises the steps of attempting to send the message to that Network Element a predetermined number of times, upon failure of which attempts the Control Network Element discontinues the process of attempting to communicate to the Source and the First Target Network Elements information about the data that is desired to be changed.

40. The process according to claim 36 in which the Control Network Element is a Service Node and the Source and Target Network Elements are Service Control Points.

41. The process according to claim 36 in which communication occurs using non-overlay communications links.

42. The process according to claim 36 in which communication occurs using Signalling System Seven architecture.

43. The process according to claim 36 in which the Source and First Target Network Elements constitute a mated pair of Service Control Points that contain redundant databases of subscriber information, and the Second and Third Target Network Elements constitute a second mated pair of Service Control Points to which the subscriber information is being transferred during an area transfer operation.

44. Apparatus for maintaining data concurrence in a plurality of databases, each contained in a corresponding Network Element in a telecommunications network, comprising:

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

b. means for causing an original update request message to be prepared that contains information about the data that is desired to be changed and for communicating the original update request message to a Source Network Element;

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

d. platform based means in the Source Network Element for causing a synchronization update request message to be prepared that contains information about the data that is desired to be changed;

e. platform based means for communicating the synchronization update message to a Target Network Element that contains at least one of the databases; and

f. means in the Target Network Element for changing information in the database in the Target Network Element based on information in the synchronization update request message received by the Target Network Element.

45. Apparatus according to claim 44 further comprising platform based means in each Network Element for causing a result message to be sent to the Network Element from which a corresponding request message was received, regarding level of success in accomplishing data changes requested in the request message.

46. Apparatus according to claim 44 in which the means for preparing request messages also contains means for including a time stamp in the request messages.

47. Apparatus according to claim 46 in which the time stamp is originated in the Control Network Element.

48. Apparatus according to claim 47 in which the time stamp is the only means for determining currency of at least some of the data contained in the Source and Target Network Elements.

49. Apparatus according to claim 44 in which the Control Network Element is a Service Node and the Source Network Element and the Target Network Element are Service Control Points.

50. Apparatus according to claim 44 in which the communication means comprises non-overlay communications links.

51. Apparatus according to claim 44 in the communication means conforms to Signalling System Seven architecture.