Claims
- 1. A method for synchronizing processors in a telecommunication system, comprising the steps of:a first processor unit retrieving a current value of a change counter associated with a second processor unit, a first database associated with said first processor unit to be synchronized with a second database associated with said second processor unit; said first processor unit storing said current value of said change counter; said first processor unit retrieving a substantial portion of data stored in said second database; said first processor performing a synchronization procedure for said substantial portion of all data retrieved said second processor unit incrementing said change counter for a change of said data stored in said second database; said second processor unit determining whether new data has been stored in said second database; if said new data has been stored in said second database, sending a unique identifier associated with said new data to said first processor unit; and sending said current value of said change counter to said first processor unit.
- 2. The method of claim 1, wherein said first processor unit comprises a synchronization engine.
- 3. The method of claim 1, wherein said second processor unit comprises a synchronization engine.
- 4. The method of claim 1, wherein said processors comprise a plurality of parallel processors.
- 5. The method of claim 1, further comprising the steps of:said first processor unit receiving said current value of said change counter; said first processor unit determining whether there is a difference between said received current value of said change counter and a previous value of said change counter; and if there is said difference between said received current value of said change counter and said previous value of said change counter, said first processor unit retrieving a change log from said second processor unit; otherwise, if there is no said difference, said first processor unit updating said change counter with a new change counter value retrieved from said second processor unit.
- 6. The method of claim 5, further comprising the steps of:said first processor unit determining whether any of said new data in said second database has not been processed; and if said new data has been processed, said first processor unit updating said change counter with a value from said change log.
- 7. The method of claim 1, further comprising the steps of:clearing said data in said second database; setting said change counter to an initial value; clearing entries in a change log associated with said second database; generating an identifier associated with said second database; and storing new data in said second database.
- 8. The method of claim 1, further comprising the steps of:storing in said first database a first identifier associated with said first database; storing in said second database a second identifier associated with said second database; said first processor unit retrieving a change log from said second processor unit; said first processor determining whether said retrieved change log includes said second identifier; and if said retrieved change log does not include said second identifier, said first processor performing a slow synchronization procedure.
- 9. A system for synchronizing processors in a telecommunication system, comprising:a first processor unit; a first database associated with said first processor unit; a second processor unit; a second database associated with said second processor unit; means for interconnecting said first processor unit with said second processor unit; said first processor unit including means for retrieving a current value of a change counter associated with said second processor unit, storing said current value of said change counter, retrieving a substantial portion of data stored in said second database, and performing a synchronization procedure for said substantial portion of all data retrieved wherein said second processor unit is adapted to increment said change counter for a change of said data stored in said second database; wherein said second processor unit is adapted to determine whether new data has been stored in said second database; wherein, if said new data has been stored in said second database, a unique identifier associated with said new data is sent to said first processor unit; and wherein said current value of said change counter is sent to said first processor unit.
- 10. The system of claim 9, wherein said first processor unit comprises a synchronization engine.
- 11. The system of claim 9, wherein said second processor unit comprises a synchronization engine.
- 12. The system of claim 9, wherein said processors comprise a plurality of parallel processors.
- 13. A method for synchronizing processors in a telecommunication system, comprising the steps of:a first processor unit retrieving a current value of a change counter associated with a second processor unit, a first database associated with said first processor unit to be synchronized with a second database associated with said second processor unit; said first processor unit storing said current value of said change counter; said first processor unit retrieving a substantial portion of data stored in said second database; and said first processor performing a synchronization procedure for said substantial portion of all data retrieved; clearing said data in said second database; setting said change counter to an initial value; clearing entries in a change log associated with said second database; generating an identifier associated with said second database; and storing new data in said second database.
- 14. The method of claim 13, further comprising the steps of:storing in said first database a first identifier associated with said first database; storing in said second database a second identifier associated with said second database; said first processor unit retrieving a change log from said second processor unit; said first processor determining whether said retrieved change log includes said second identifier; and if said retrieved change log does not include said second identifier, said first processor performing a slow synchronization procedure.
- 15. The method of claim 13, further comprising the steps of:said second processor unit incrementing said change counter for a change of said data stored in said second database; said second processor unit determining whether new data has been stored in said second database; if said new data has been stored in said second database, sending a unique identifier associated with said new data to said first processor unit; and sending said current value of said change counter to said first processor unit.
- 16. The method of claim 15, further comprising the steps of:said first processor unit receiving said current value of said change counter; said first processor unit determining whether there is a difference between said received current value of said change counter and a previous value of said change counter; and if there is said difference between said received current value of said change counter and said previous value of said change counter, said first processor unit retrieving a change log from said second processor unit; otherwise, if there is no said difference, said first processor unit updating said change counter with a new change counter value retrieved from said second processor unit.
- 17. The method of claim 13, wherein said first processor unit comprises a synchronization engine.
- 18. The method of claim 13, wherein said second processor unit comprises a synchronization engine.
- 19. The method of claim 13, wherein said processors comprise a plurality of parallel processors.
CROSS-REFERENCES TO RELATED APPLICATIONS
This Application for Patent claims the benefit of priority from, and hereby incorporates by reference the entire disclosures of, co-pending U.S. Provisional Applications for U.S. Pat. Ser. Nos. 60/108,902, filed Nov. 17, 1998, and U.S. Pat. Ser. No. 60/110,485, filed Dec. 1, 1998.
US Referenced Citations (6)
Number |
Name |
Date |
Kind |
5247684 |
Tavares et al. |
Sep 1993 |
A |
5307487 |
Tavares et al. |
Apr 1994 |
A |
5495609 |
Scott |
Feb 1996 |
A |
6006274 |
Hawkins et al. |
Dec 1999 |
A |
6247135 |
Feague |
Jun 2001 |
B1 |
6330568 |
Boothby et al. |
Dec 2001 |
B1 |
Foreign Referenced Citations (1)
Number |
Date |
Country |
9902003 |
Jun 2000 |
WO |
Non-Patent Literature Citations (3)
Entry |
IBM TDB vol.36, issue 11, p. 595-598, Pub. Date Nov. 1, 1993.* |
IBM TDB vol.32, issue 12, p. 71-72, Pub. date May 1, 1990.* |
Bounding Journal Back-Off during Recovery of Data Base Replica in Fault-Tolerant Clusters; IBM Technical Discloure Bulletin, vol. 36, No. 11, pp. 675-678; XP002138512. |
Provisional Applications (2)
|
Number |
Date |
Country |
|
60/108902 |
Nov 1998 |
US |
|
60/110485 |
Dec 1998 |
US |