Method and apparatus for transaction processing in a distributed database system

• US 5,978,577 A
• Filed: 03/17/1995
• Issued: 11/02/1999
• Est. Priority Date: 03/17/1995
• Status: Expired due to Term

• Current Assignee: CSG Systems Incorporated (CSG Systems International Incorporated)
• Original Assignee: CSG Systems Incorporated (CSG Systems International Incorporated)
• Inventors: Gollob, David, Marusin, Mark, Rierden, William
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US08/405,766
• Time in Patent Office: 1,691 Days
• Field of Search: 395/600, 395/200, 395/275, 395/603, 395/604, 395/610, 395/611, 395/200.31, 395/200.33, 340/825.52, 379/115
• US Class Current: 1/1
• 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/275 Synchronous replication
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A subscriber management system includes at least one Data Directory Server (DDS) located between one or more transaction generators and one or more data servers. The DDS efficiently routes transactions and provides data location functions. The DDS provides high data availability, high on-line transaction rates, batch capabilities, scalability and maintainability. In particular, based upon internal rules within the DDS and the particular transaction type, the DDS routes transactions to the appropriate server(s). Transactions are classified according to where they may be executed. Specifically, transactions may be classified as SPECIFIC, ANY or ALL. A SPECIFIC transaction must be processed at one or more specific servers irrespective of the accompanying arguments. An ANY transaction may be processed at any of the enterprise servers and selection is made randomly. Finally, an ALL transaction requires sequencing through each of the data servers within the enterprise and repetitively performing the transaction.

Claims

1. A distributed database system comprising:

transaction generator means for generating database transactions;

a plurality of data servers; and

data directory server means in communication with said transaction generator means and each of said data servers, said data directory server means receiving database transactions from said transaction generator means and selecting at least one data server for processing each said database transaction.

2. The system of claim 1 wherein said data directory server means determines the type of database transaction received and determines whether the received database transaction is processed by a specific data server, by any data server or by all data servers.

3. The system of claim 1 further comprising at least one cross-reference server, said cross-reference servers providing data location information to said data directory servers.

4. The system of claim 3 wherein said cross-reference servers further provide a rules base to said data directory servers.

5. The system of claim 1 further comprising a control application, said control application initiating and modifying a rules base implemented by said data directory servers.

6. The system of claim 1 wherein said database transactions are routed by said data directory server based upon a transaction type.

7. The system of claim 6 wherein said transaction types consist of Specific, Any and All.

8. The system of claim 6 wherein said data server for processing each said database transaction is further selected based upon transaction arguments.

9. The system of claim 1 wherein at least one of said transaction generators comprises an automatic response unit.

10. The system of claim 9 wherein said transaction unit comprising an automatic response unit further includes an automatic number indicator for determining caller telephone numbers.

11. The system of claim 1 wherein said transaction generators comprise personal computers.

12. The system of claim 1 wherein said data servers and said data directory servers comprise open servers.

13. A subscriber management system for processing subscriber account records comprising:

a plurality of client terminals for operation by a customer service representative for initiating database transactions;

a plurality of servers for storing said subscriber account records and allowing read and write access to said subscriber account records; and

at least one data directory server for determining which of said servers is to be accessed for processing said database transactions, said data directory server being in communication with each of said client terminals and each of said servers;

further comprising at least one cross reference server, said cross reference servers indicating each of the accessible servers in said subscriber management system.

14. The subscriber management system of claim 13 wherein said cross reference servers farther indicate rule boundary information binding particular database transactions to particular servers.