Systems and methods for communicating from an integration platform to a profile management server

• US 8,195,738 B2
• Filed: 03/15/2002
• Issued: 06/05/2012
• Est. Priority Date: 03/20/2001
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Trivedi, Prakash A.
• Primary Examiner(s): Blair, Douglas
• Assistant Examiner(s): AILES, BENJAMIN A
• Application Number:
  US10/097,934
• Publication Number:
  US 20020138563A1
• Time in Patent Office: 3,735 Days
• Field of Search: 709200-203, 709/206, 709217-219, 709/227, 709/246, 708/110, 455 301- 304, 370420-421, 370/259, 370/431, 705/53, 707/202
• US Class Current: 709/203
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• 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/19 at layers above the network layer network arrangements for networked applications for scheduling or organising the servicing of application requests H04L67/60
• 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/401 : wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• 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/085 : specially adapted for interworking of IP-based networks with other networks
• 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/06 : Recording class or number of calling , i.e. A-party or called party , i.e. B-party
• CPC Class Codes: H04M 15/41 : Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/43 : Billing software details
• CPC Class Codes: H04M 15/44 : Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/47 : Fraud detection or prevention means
• CPC Class Codes: H04M 15/49 : Connection to several service providers
• 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/58 : based on statistics of usage or network monitoring
• 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/8214 : Data or packet based
• CPC Class Codes: H04M 15/8292 : Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2215/0104 : Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
• 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/0164 : Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• 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/0188 : Network monitoring; statistics on usage on called/calling number
• CPC Class Codes: H04M 2215/2013 : Fixed data network, e.g. PDN, ATM, B-ISDN
• CPC Class Codes: H04M 2215/202 : VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/2046 : Hybrid network
• 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/46 : Connection to several service providers
• 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 2215/782 : Data or packet based
• CPC Class Codes: H04M 3/2218 : Call detail recording
• CPC Class Codes: H04M 7/006 : Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking

Abstract

A method for communicating from an integration platform to a profile management 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 server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server via hypertext transfer protocol (HTTP). The connector downloads the information to the server and the 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 server.

Claims

1. A method for communicating from a first system to a first server, the first server storing profile management information for a number of users, the method 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 connector configured to communicate with the first server;

receiving, by the connector, the event information;

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

establishing, by the connector, communications with the first server using hypertext transfer protocol (HTTP), the first server controlling access to a first database;

downloading the transformed event information to the first server;

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

signaling the first server to write the transformed event information to the first database when messages from both the data storage system and the billing system have been received;

queuing the transformed event information if the connector is unable to establish communications with the first server;

periodically attempting to establish communications with the first server; and

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

2. The method of claim 1, further comprising:

writing the transformed event information to the first 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 data storage system and the billing system.

4. The method of claim 3, further comprising:

signaling the first server to not write the transformed event information to the first database if the determining indicates that either the data storage system or the billing system has not received the event information.

5. The method of claim 1, wherein the user-entered information comprises information associated with at least one of banking, brokerage, financial, travel, sports, weather, entertainment, distribution, shipping, insurance, health or manufacturing services.

6. The method of claim 5, wherein the receiving user-entered information includes receiving information identifying a device with which the user wishes to receive information.

7. A non-transitory 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 or modifying information stored in a profile management server, the profile management server storing information identifying services to which a user subscribes and device preference information identifying a device with which the user wishes to receive information;

receive the data associated with at least one of adding, deleting or modifying information stored in the profile management server;

format the data based on an event type associated with the received data;

establish communications with the profile management server using hypertext transfer protocol (HTTP);

determine whether a data storage system received the data;

download the formatted data to the profile management server via HTTP, when the determining indicates that the data storage system received the data;

queue the formatted data if communications with the profile management server are not established; and

periodically attempt to establish communications with the profile management server.

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

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

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

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

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

forward an error message to a user.

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

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

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

send a message to the data storage system if communications with the profile management 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.

13. The computer-readable medium of claim 7, wherein the data associated with at least one of adding, deleting or modifying information stored in the profile management server comprises user-entered information associated with at least one of banking, brokerage, financial, travel, sports, weather, entertainment, distribution, shipping, insurance, health or manufacturing services.

14. The computer-readable medium of claim 13, wherein user-entered information identifies a device with which the user wishes to receive information for a service.

15. 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 an event 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 a data storage system and a billing system,

receive an indication that the data storage system has stored the data,

establish communications with a server using hypertext transfer protocol (HTTP), in response to receiving the indication,

download the transformed data to the server,

queue the transformed data if communications with the server cannot be established,

periodically attempt to establish communications with the server, and

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

16. The support system of claim 15, 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.

17. The support system of claim 15, wherein the input data is associated with at least one of one of banking, brokerage, financial, travel, sports, weather, entertainment, distribution, shipping, insurance, health or manufacturing services.

18. The support system of claim 17, wherein the input data identifies a device with which a user wishes to receive information associated with a service.

19. A software-based connector, at least partially implemented in hardware, for interfacing between an integration platform and a server, the connector being executable by a processor and causing the processor to:

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

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

establish communications with the server via hypertext transfer protocol (HTTP);

download the transformed data to the server via HTTP;

output event information associated with the received input information to a channel subscribed to by a connector associated with a billing system and a first system;

receive a message from the billing system when the billing system has received the event information;

receive a message from the first system when the first system has received the event information;

queue the transformed data if communications with the server cannot be established; and

periodically attempt to establish communications with the server.

20. The software-based connector of claim 19, wherein the first system comprises a data storage system.

21. The software-based connector of claim 19, wherein the server stores profile management information for a plurality of users.

22. The software-based connector of claim 19, wherein the input information comprise information associated with at least one of banking, brokerage, financial, travel, sports, weather, entertainment, distribution, shipping, insurance, health or manufacturing services to which a user subscribes.

23. The software-based connector of claim 22, wherein the input information identifies a device with which the user wishes to receive information for a service.