Systems and methods for updating an LDAP

• US 8,341,116 B2
• Filed: 03/15/2002
• Issued: 12/25/2012
• Est. Priority Date: 03/20/2001
• Status: Expired due to Fees

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Trivedi, Prakash A., Robohm, Kurt W.
• Primary Examiner(s): SOMERS, MARC S
• Application Number:
  US10/097,868
• Publication Number:
  US 20020138489A1
• Time in Patent Office: 3,938 Days
• Field of Search: 707/1, 707/201, 707/202, 707/609, 707/610, 707/624, 707/625, 707/634, 707/687
• US Class Current: 707/625
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 12/1446 inter-operator billing
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/14 : Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04M 15/00 : Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/43 : Billing software details
• CPC Class Codes: H04M 15/47 : Fraud detection or prevention means
• CPC Class Codes: H04M 15/53 : using mediation
• CPC Class Codes: H04M 15/55 : for hybrid networks
• CPC Class Codes: H04M 15/56 : for VoIP communications
• CPC Class Codes: H04M 15/63 : based on the content carried by the session initiation protocol [SIP] messages
• CPC Class Codes: H04M 15/8292 : Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2215/0148 : Fraud detection or prevention means
• CPC Class Codes: H04M 2215/0172 : Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
• CPC Class Codes: H04M 2215/202 : VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/22 : Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/44 : Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking

Abstract

A system updates a lightweight directory access protocol (LDAP) database based on changes made to a second database. The system determines differences between Internet Protocol (IP) communication service records stored in the second database and IP communication service records stored in the LDAP database and creates a transaction file based on the differences. The system updates the LDAP database using the transaction file.

Claims

1. A computer-implemented method for updating a lightweight directory access protocol (LDAP) database based on changes made to a second database, the method comprising:

determining differences between Internet Protocol (IP) communication service records stored in the second database and IP communication service records stored in the LDAP database, information regarding the IP communication service records being stored in a first set of tables and a second set of tables, the second database including the first set of tables and the second set of tables;

creating a transaction file based on the differences;

updating the LDAP database using the transaction file;

determining whether the updating was successful;

appending the transaction file to a new transaction file to create a second new transaction file when the updating was unsuccessful; and

storing the second new transaction file.

2. The computer-implemented method of claim 1 where the determining differences occurs automatically at predetermined time intervals.

3. The computer-implemented method of claim 1 where the determining differences is performed hourly.

4. The computer-implemented method of claim 1 where the determining differences occurs based on a command from a system administrator.

5. The computer-implemented method of claim 1 where the determining differences includes:

comparing one or more first tables containing current IP communication service records with one or more second tables containing IP communication service records from a previous comparison operation, and

determining, for each difference between the one or more first tables and the one or more second tables, a transaction type.

6. The computer-implemented method of claim 5 where the transaction file includes:

a list of the differences between the one or more first tables and the one or more second tables, and

an indication, corresponding to each difference, of the transaction type.

7. The computer-implemented method of claim 6 where the transaction type includes at least one of addition, deletion, or modification.

8. The computer-implemented method of claim 1 where the second database includes an operational data store.

9. A system for updating a lightweight directory access protocol (LDAP) database based on changes made to a second database, the system comprising:

a memory to store a plurality of instructions; and

a processor to execute the instructions to;

compare a first set of tables to a second set of tables, the first set of tables comprising current Internet Protocol (IP) communications information, the second set of tables comprising IP communications information from a previous LDAP database update, the second database including the first set of tables and the second set of tables;

identify, based on the comparing, differences between the first set of tables and the second set of tables;

create a transaction file based on the identified differences;

update the LDAP database using the transaction file;

determine whether the LDAP database update was successful; and

append the transaction file to a new transaction file when the LDAP database update was unsuccessful,

the processor, when identifying the differences, being further to;

identify, for each difference, a transaction type, and

the processor, when creating the transaction file, being further to;

store the transaction type with each difference in the transaction file.

10. The system of claim 9 where the second database includes an operational data store.

11. The system of claim 9 where the processor is further to:

compare the first set of tables to the second set of tables automatically at predetermined time intervals.

12. The system of claim 9 where the processor is further to:

compare the first set of tables to the second set of tables on an hourly basis.

13. The system of claim 9 where the processor is further to:

compare the first set of tables to the second set of tables based on a command from a system administrator.

14. A computer-implemented method for updating a lightweight directory access protocol (LDAP) database, the method comprising:

comparing one or more first tables to one or more second tables, the one or more first tables comprising a set of current records, the one or more second tables comprising records from the LDAP database, and the one or more first tables and the one or more second tables being stored in a second database;

identifying one or more transactions based on the comparing;

storing the one or more identified transactions in a transaction file;

associating a transaction type with each of the one or more identified transactions;

updating the LDAP database using the transaction file;

determining whether the LDAP database update was successful;

appending the transaction file to a new transaction file to create a second new transaction file when the LDAP database update was unsuccessful; and

storing the second new transaction file.

15. The computer-implemented method of claim 14 where the second database includes an operational data store.

16. The computer-implemented method of claim 14 where the storing includes:

storing the one or more identified transactions and the associated transaction types in the transaction file.

17. The computer-implemented method of claim 14 where the comparing occurs automatically at predetermined time intervals.

18. The computer-implemented method of claim 14 where the comparing occurs based on a command from a system administrator.

19. A system for updating a lightweight directory access protocol (LDAP) database, the system comprising:

means for comparing one or more first tables to one or more second tables, the one or more first tables comprising a set of current records, the one or more second tables comprising records from the LDAP database, and the one or more first tables and the one or more second tables being stored in a second database;

means for identifying one or more transactions based on the comparing;

means for updating the LDAP database based on the one or more identified transactions;

means for updating the one or more second tables based on the one or more identified transactions

means for determining whether the LDAP database update was successful;

means for appending the transaction file to a new transaction file to create a second new transaction file when the LDAP database update was unsuccessful; and

means for storing the second new transaction file.

20. The system of claim 19 further comprising:

means for storing the one or more identified transactions in a transaction file, and where the means for updating the LDAP database includes;

means for updating the LDAP database using the transaction file.