Systems and methods for updating IP communication service attributes using an LDAP

• US 20020136222A1
• Filed: 03/15/2002
• Published: 09/26/2002
• Est. Priority Date: 03/20/2001
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: W. Robohm, Kurt
• Granted Patent: US 8,660,017 B2
• Time in Patent Office: Days
• US Class Current: 370/395.31
• 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 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/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: H04L 69/329 : in the application layer [OSI layer 7]
• 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/51 : for resellers, retailers or service providers
• CPC Class Codes: H04M 15/52 : for operator independent billing system
• 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/745 : Customizing according to wishes of subscriber, e.g. friends or family
• CPC Class Codes: H04M 15/8292 : Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2215/0108 : Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
• CPC Class Codes: H04M 2215/0148 : Fraud detection or prevention means
• CPC Class Codes: H04M 2215/0168 : On line or real-time flexible customization or negotiation according to wishes of subscriber
• 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/0176 : Billing arrangements using internet
• 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: H04M 2215/54 : Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04M 3/42161 : via computer interface
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking

Abstract

A system processes calls in an Internet Protocol (IP) communications network. The system includes a lightweight directory access protocol (LDAP) database, an LDAP sever, and a redirect server. The LDAP database stores a group of IP communication service attributes. The LDAP server receive a request for a database update, extracts the group of IP communication service attributes from the LDAP database, and transfers the extracted IP communication service attributes to the redirect server. The redirect server stores the extracted IP communication service attributes and processes a call using the stored IP communication service attributes.

Claims

1. A method for updating a redirect server, comprising:

sending a request for a database update to a lightweight directory access protocol (LDAP) server, the LDAP server being associated with a database storing a plurality of Internet Protocol (IP) communication service attributes;

extracting the plurality of IP communication service attributes from the database;

transferring the extracted IP communication service attributes to the redirect server; and

storing the plurality of IP communication service attributes at the redirect server.

2. The method of claim 1 further comprising:

processing, after the storing, a call based on one or more of the IP communication service attributes.

3. The method of claim 1 wherein the plurality of IP communications service attributes includes attributes relating to one or more of follow me, call blocking, call forwarding, voice mail, conference calling, single line extension, call screening, quality of service, class of service, dial-plan restrictions, dynamic registration, secondary directory number, and call transfer processing.

4. The method of claim 1 wherein the storing includes:

storing the plurality of IP communication service attributes in a database associated with the redirect server.

5. The method of claim 1 wherein the sending occurs in response to the redirect server being powered up.

6. The method of claim 1 wherein the sending occurs in response to a command from a user.

7. A system for processing calls in an Internet Protocol (IP) communications network, comprising:

a lightweight directory access protocol (LDAP) database configured to store a plurality of IP communication service attributes;

an LDAP server configured to;

receive a request for a database update,

extract the plurality of IP communication service attributes from the LDAP database, and

transfer the extracted IP communication service attributes; and

a redirect server configured to;

receive the extracted IP communication service attributes from the LDAP server,

store the extracted plurality of IP communication service attributes, and

process a call using one or more of the stored plurality of IP communication service attributes.

8. The system of claim 7 wherein the plurality of IP communication service attributes includes attributes relating to one or more of follow me, call blocking, call forwarding, voice mail, conference calling, single line extension, call screening, quality of service, class of service, dial-plan restrictions, dynamic registration, secondary directory number, and call transfer processing.

9. The system of claim 7 wherein the redirect server is further configured to:

transmit the request to the LDAP server.

10. The system of claim 9 wherein the redirect server transmits the request automatically upon powering up.

11. The system of claim 9 wherein the redirect server transmits the request in response to a command from a user.

12. The system of claim 11 wherein the user is a system administrator.

13. The system of claim 7 further comprising:

a process management system configured to route communications between the LDAP server and the redirect server.

14. The system of claim 7 wherein, when storing the extracted IP communication service attributes, the redirect server is configured to:

store the extracted IP communication service attributes in a database associated with the redirect server.

16. The method of claim 15 wherein the plurality of records relate to Internet Protocol (IP) communication service attributes.

17. The method of claim 16 wherein the plurality of records includes attributes relating to one or more of follow me, call blocking, call forwarding, voice mail, conference calling, single line extension, call screening, quality of service, class of service, dial-plan restrictions, dynamic registration, secondary directory number, and call transfer processing.

18. The method of claim 15 wherein the comparing is performed by the LDAP server.

19. The method of claim 15 wherein the comparing is performed by the redirect server.

20. The method of claim 15 wherein the sending occurs automatically in response to the redirect server powering up.

21. The method of claim 15 wherein the sending occurs in response to a command from a user.

22. The method of claim 15 wherein the user is a system administrator.

23. The method of claim 15 wherein the storing includes:

storing the extracted records in a database associated with the redirect server.

25. The system of claim 24 wherein the first configuration of records and the second configuration of records include IP communication service attributes.

26. The system of claim 25 wherein the first configuration of records and the second configuration of records include attributes relating to one or more of follow me, call blocking, call forwarding, voice mail, conference calling, single line extension, call screening, quality of service, class of service, dial-plan restrictions, dynamic registration, secondary directory number, and call transfer processing.

27. The system of claim 24 wherein the redirect server sends the partial database update request automatically in response to the redirect server powering up.

28. The system of claim 24 wherein the redirect server sends the partial database update request in response to a command from a user.

29. The system of claim 28 wherein the user is a system administrator.

30. The system of claim 24 wherein the LDAP server transfers the extracted records to the redirect server for storage in a database associated with the redirect server.

15. A method for updating a redirect server storing a plurality of records, comprising:

sending a request for a database update to a lightweight directory access protocol (LDAP) server, the LDAP server being associated with a database configured to store a plurality of records that corresponds to the plurality of records stored by the redirect server;

comparing each of the plurality of records stored at the redirect server to the corresponding records stored in the database;

extracting records from the database that differ from the corresponding records stored at the redirect server;

transferring the extracted records to the redirect server; and

storing the extracted records at the redirect server.

24. A system for updating a redirect server configured to store a first configuration of records relating to processing calls in an Internet Protocol (IP) communications network, comprising:

a lightweight directory access protocol (LDAP) database configured to store a second configuration of records corresponding to the first configuration of records; and

an LDAP server configured to;

receive a request for a partial database update from the redirect server,

compare the first configuration of records to the second configuration of records,

extract records from the second configuration that differ from the corresponding records in the first configuration, and

transfer the extracted records to the redirect server for storage.