Systems and methods for communicating from an integration platform to a lightweight directory access protocol based database

• US 20020138488A1
• 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: MCI Incorporated (Verizon Communications Inc.)
• Inventors: Trivedi, Prakash A.
• Granted Patent: US 7,043,480 B2
• Time in Patent Office: Days
• US Class Current: 707/10
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
• 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/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 67/565 : Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• 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: H04L 9/40 : Network security protocols
• 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: H04M 3/2218 : Call detail recording
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking
• CPC Class Codes: Y10S 707/99943 : Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 : Object-oriented database structure

Abstract

A method for communicating from an integration platform to a directory server includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the directory server. The connector receives the event information, transforms the event information to a format compatible with the directory server and establishes communications with the directory server. The connector downloads the information to the directory server and the directory server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the directory server.

Claims

1. A method for communicating from a first system to a directory server, comprising:

receiving user-entered information at the first system;

sending, by the first system, event information to a channel, the event information being based on the user-entered information and the channel being subscribed to by a lightweight directory access protocol (LDAP) connector;

receiving, by the LDAP connector, the event information;

transforming the event information to a format compatible with the directory server;

establishing, by the LDAP connector, communications with the directory server, the directory server controlling access to an LDAP-based database;

downloading the transformed event information to the directory server;

preparing, by the directory server, to write the transformed event information to the LDAP-based database;

determining, by the LDAP connector, whether a message from a billing system and a message from a database system have been received; and

signaling the directory server to write the transformed event information to the LDAP-based database when messages from both the billing system and the database system has been received.

2. The method of claim 1, further comprising:

writing the transformed event information to the LDAP based database in response to the signaling.

3. The method of claim 1, wherein the sending includes:

sending the event information to a channel subscribed to by the billing system and the database system.

4. The method of claim 3, further comprising:

signaling the directory server to not write the transformed event information to the LDAP-based database if the determining indicates that either the billing system or the database system has not received the event information.

5. The method of claim 1, further comprising:

queuing the event if the LDAP connector is unable to establish communications with the directory server; and

periodically attempting to establish communications with the directory server.

6. The method of claim 5, further comprising:

generating an alarm if communications with the directory server are not established after a predetermined period of time or after a predetermined number of attempts.

7. The method of claim 1, wherein the user-entered information comprises information associated with at least one of call blocking, follow me, 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.

8. A computer-readable medium having stored thereon a plurality of sequences of instructions, said sequences of instructions including instructions which, when executed by a processor, cause the processor to:

monitor an input channel for data associated with at least one of adding, deleting and modifying information stored in a lightweight directory access protocol (LDAP) based database;

receive the data associated with at least one of adding, deleting and modifying information stored in the LDAP based database;

format the data based on a type associated with the received data;

establish communications with a server based on the type associated with the received data, the server controlling access to the LDAP based database;

determine whether an operational data storage system received the data; and

download the formatted data to the server, when the determining indicates that the operational data storage system received the data.

9. The computer-readable medium of claim 8, including instructions for causing the processor to:

forward event information associated with the received data to a channel subscribed to by the operational data storage system and a billing system.

10. The computer-readable medium of claim 9, including instructions for causing the processor to:

receive a message from the operational data storage system, the message indicating that the operational data storage system was unable to store the data.

11. The computer-readable medium of claim 10, wherein the message includes information indicating why the operational data storage system was unable to store the data and the instructions further cause the processor to:

forward an error message to a user.

12. The computer-readable medium of claim 8, including instructions for causing the processor to:

queue the event if communications with the server are not established; and

periodically attempt to establish communications with the server.

13. The computer-readable medium of claim 12, including instructions for causing the processor to:

generate an alarm if communications with the server are not established after a predetermined number of attempts or after a predetermined period of time.

14. The computer-readable medium of claim 8, including instructions for causing the processor to:

send a message to the operational data storage system if communications with the server cannot be established, the message instructing the operational data storage system to return the operational data storage system to a state prior to when the operational data storage system received the data.

15. The computer-readable medium of claim 8, wherein the data associated with at least one of adding, deleting and modifying information stored in the LDAP based database comprises information associated with at least one of call blocking, follow me, 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.

17. The support system of claim 16, wherein the at least one system comprises a data storage system.

18. The support system of claim 17, wherein the processor is further configured to:

send a message to the data storage system if communications with the server cannot be established, the message instructing the data storage system to return the data storage system to a state prior to when the data storage system received the data.

19. The support system of claim 16, wherein the processor is further configured to:

queue the event if communications with the server cannot be established, and

periodically attempt to establish communications with the server.

20. The support system of claim 19, wherein the processor is further configured to:

generate an alarm if communications with the server are not established after a predetermined period of time or after a predetermined number of attempts.

21. The support system of claim 15, wherein the input data is associated with at least one of call blocking, follow me, 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.

16. A support system, comprising:

a memory configured to store an application program to integrate a number of hardware platforms; and

a processor configured to execute the application program and;

receive input data,

transform the data into an appropriate format based on a type associated with the input data,

output event information associated with the input data to a channel subscribed to by at least one connector,

forward the data to at least one system,

receive an indication that the at least one system has stored the data,

establish communications with a server controlling access to a lightweight directory access protocol (LDAP) based database, in response to receiving the indication, and

download the transformed data to the server.

22. A software-based connector for interfacing between an integration platform and a lightweight directory access protocol (LDAP) based repository, the connector comprising:

a transformer module configured to;

receive input information associated with at least one of a request to change attributes associated with a service or add a new service, and

transform the data into an appropriate format based on the request; and

a client module configured to;

establish communications with the LDAP based repository, and

download the formatted data to the LDAP based repository.

23. The software-based connector of claim 22, wherein the transformer module is further configured to:

output event information associated with the received input information to a channel subscribed to by a connector associated with at least one other system.

24. The software-based connector of claim 23, wherein the at least one other system comprises a billing system and an operational data storage system and the client module is further configured to:

receive a message from the billing system when the billing system has successfully received the event information, and

receive a message from the operational data storage system when the operational data storage system has received the event information.

25. The software-based connector of claim 22, wherein the client module is further configured to:

queue the transformed data if communications with the LDAP based repository cannot be established, and

periodically attempt to establish communications with the LDAP based repository.

26. The software-based connector of claim 22, wherein the input information comprise information associated with at least one of least one of call blocking, follow me, 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.