[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

US20020138427A1 - Systems and methods for communicating from an integration platform to a billing unit - Google Patents

Systems and methods for communicating from an integration platform to a billing unit Download PDF

Info

Publication number
US20020138427A1
US20020138427A1 US10/097,866 US9786602A US2002138427A1 US 20020138427 A1 US20020138427 A1 US 20020138427A1 US 9786602 A US9786602 A US 9786602A US 2002138427 A1 US2002138427 A1 US 2002138427A1
Authority
US
United States
Prior art keywords
information
billing system
connector
billing
communications
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/097,866
Inventor
Prakash Trivedi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Verizon Patent and Licensing Inc
Original Assignee
Worldcom Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Worldcom Inc filed Critical Worldcom Inc
Priority to US10/097,866 priority Critical patent/US20020138427A1/en
Assigned to WORLDCOM, INC. reassignment WORLDCOM, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TRIVEDI, PRAKASH A.
Publication of US20020138427A1 publication Critical patent/US20020138427A1/en
Assigned to MCI, INC. reassignment MCI, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: WORLDCOM, INC.
Assigned to VERIZON BUSINESS GLOBAL LLC reassignment VERIZON BUSINESS GLOBAL LLC CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: MCI, LLC
Assigned to MCI, LLC reassignment MCI, LLC MERGER (SEE DOCUMENT FOR DETAILS). Assignors: MCI, INC.
Assigned to VERIZON PATENT AND LICENSING INC. reassignment VERIZON PATENT AND LICENSING INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VERIZON BUSINESS GLOBAL LLC
Assigned to VERIZON PATENT AND LICENSING INC. reassignment VERIZON PATENT AND LICENSING INC. CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE PREVIOUSLY RECORDED AT REEL: 032734 FRAME: 0502. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Assignors: VERIZON BUSINESS GLOBAL LLC
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/04Recording calls, or communications in printed, perforated or other permanent form
    • H04M15/06Recording class or number of calling, i.e. A-party or called party, i.e. B-party
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102Bill distribution or payments
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/04Billing or invoicing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1442Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
    • H04L12/1446Charging, metering or billing arrangements for data wireline or wireless communications at network operator level inter-operator billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • H04L47/125Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/19Flow control; Congestion control at layers above the network layer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433Allocation of priorities to traffic types
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4505Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4523Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using lightweight directory access protocol [LDAP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4535Network directories; Name-to-address mapping 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4557Directories for hybrid networks, e.g. including telephone numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272Virtual private networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102Entity profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H04L63/1416Event detection, e.g. attack signature detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441Countermeasures against malicious traffic
    • H04L63/1458Denial of Service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/102Gateways
    • H04L65/1023Media gateways
    • H04L65/103Media gateways in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/102Gateways
    • H04L65/1033Signalling gateways
    • H04L65/104Signalling gateways in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/102Gateways
    • H04L65/1043Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1069Session establishment or de-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1083In-session procedures
    • H04L65/1094Inter-user-equipment sessions transfer or sharing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1096Supplementary features, e.g. call forwarding or call holding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1101Session protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1101Session protocols
    • H04L65/1104Session initiation protocol [SIP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40Support for services or applications
    • H04L65/401Support for services or applications 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/61Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/612Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/75Media network packet handling
    • H04L65/762Media network packet handling at the source 
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles
    • H04L67/303Terminal profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles
    • H04L67/306User profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/52Network services specially adapted for the location of the user terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/563Data redirection of data network streams
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/41Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/43Billing software details
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/44Augmented, consolidated or itemized billing statement or bill presentation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/47Fraud detection or prevention means
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/49Connection to several service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/51Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for resellers, retailers or service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/52Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for operator independent billing system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/53Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP using mediation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/55Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for hybrid networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/56Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for VoIP communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/63Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the content carried by the session initiation protocol [SIP] messages
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/745Customizing according to wishes of subscriber, e.g. friends or family
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80Rating or billing plans; Tariff determination aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82Criteria or parameters used for performing billing operations
    • H04M15/8207Time based data metric aspects, e.g. VoIP or circuit switched packet data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82Criteria or parameters used for performing billing operations
    • H04M15/8214Data or packet based
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82Criteria or parameters used for performing billing operations
    • H04M15/8292Charging for signaling or unsuccessful connection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/22Arrangements for supervision, monitoring or testing
    • H04M3/2218Call detail recording
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42229Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/46Arrangements for calling a number of substations in a predetermined sequence until an answer is obtained
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/46Arrangements for calling a number of substations in a predetermined sequence until an answer is obtained
    • H04M3/465Arrangements for simultaneously calling a number of substations until an answer is obtained
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/006Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0075Details of addressing, directories or routing tables
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/006Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0078Security; Fraud detection; Fraud prevention
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/12Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/12Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/128Details of addressing, directories or routing tables
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0029Provisions for intelligent networking
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/06Generation of reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/16Threshold monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2207/00Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
    • H04M2207/20Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place hybrid systems
    • H04M2207/203Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place hybrid systems composed of PSTN and data network, e.g. the Internet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0104Augmented, 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0108Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0148Fraud detection or prevention means
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0152General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0164Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0168On line or real-time flexible customization or negotiation according to wishes of subscriber
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0172Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0176Billing arrangements using internet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0188Network monitoring; statistics on usage on called/calling number
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20Technology dependant metering
    • H04M2215/2013Fixed data network, e.g. PDN, ATM, B-ISDN
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20Technology dependant metering
    • H04M2215/202VoIP; Packet switched telephony
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20Technology dependant metering
    • H04M2215/2046Hybrid network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/22Bandwidth or usage-sensitve billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/44Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/46Connection to several service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/54Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78Metric aspects
    • H04M2215/7813Time based data, e.g. VoIP or circuit switched packet data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78Metric aspects
    • H04M2215/782Data or packet based
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/006Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • H04W4/029Location-based management or tracking services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Definitions

  • the present invention relates generally to support systems for telecommunications service providers and, more particularly, to providing a connector from an integration platform to a billing unit.
  • Telecommunications service providers continually increase the number of services and products they offer to customers. As competition increases, service providers must provide an increased level of support for these services while keeping costs down.
  • a service provider may use a system integrator to develop solutions that tie together multi-vendor hardware systems.
  • the system integrator typically uses a commercial off the shelf (COTS) software package to integrate the various hardware systems.
  • COTS commercial off the shelf
  • COTS software to integrate multi-vendor hardware systems
  • the selected software is often incompatible with all of the existing hardware systems.
  • the service provider is often forced to replace legacy systems (i.e., existing systems) in order to maintain full functionality.
  • COTS software to integrate multi-vendor hardware systems
  • the selected software package often does not include pre-packaged modules that permit the software to communicate with various hardware platforms. This may cause the system integrator to exclude one or more hardware platforms from the support system.
  • OSS operational support system
  • the OSS includes a middleware core that may be customized to integrate various applications/platforms and to ensure that data from one application can be routed to the appropriate destination(s).
  • a method for communicating from a first system to a billing system includes receiving user-entered information at the first system and sending event information to a channel, where the event information is based on the user-entered information and the channel is subscribed to by a first connector associated with the billing system.
  • the method also includes receiving, by the first connector, the event information, transforming the event information to a format compatible with the billing system and publishing the event information to a channel subscribed to by a second connector associated with a database system.
  • the method further includes sending, by the database system, an indication that the database system received the event information and receiving the indication by the first connector.
  • the method also includes establishing, by the first connector, communications with the billing system and downloading the transformed event information to the billing system.
  • Another aspect of the present invention provides a computer-readable medium having stored 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 billing system.
  • the instructions also cause the processor to receive the data associated with at least one of adding, deleting and modifying information stored in the billing system, format the data based on a type associated with the received data and forward the data to an operational data storage system.
  • the instructions further cause the processor to receive an indication that the operational data storage system received the data, establish communications with the billing system in response to receiving the indication and download the formatted data to the billing system.
  • a further aspect of the present invention provides a software-based connector for communicating between an integration platform and a billing system using remote invocation over Internet inter-ORB protocol.
  • the connector includes a transformer module configured to receive input information associated with a request for information from the billing system, identify an opcode corresponding to the request and format the request to include the identified opcode.
  • the connector also includes a client module configured to establish communications with the billing system, transmit the formatted request to the billing system and receive information from the billing system in response to the request.
  • FIG. 1 is a block diagram of an exemplary system in which methods and systems consistent with the present invention may be implemented.
  • FIG. 2 illustrates an exemplary configuration of a user device of FIG. 1 in an implementation consistent with the present invention.
  • FIG. 3 illustrates an exemplary configuration of the operational support system (OSS) of FIG. 1 in an implementation consistent with the present invention.
  • FIG. 4 illustrates an exemplary configuration of the process management system of FIG. 3 in an implementation consistent with the present invention.
  • FIG. 5 illustrates an exemplary functional block diagram of the process management system of FIG. 3 in an implementation consistent with the present invention.
  • FIG. 6 illustrates an exemplary configuration of the voice portal of FIG. 3 in an implementation consistent with the present invention.
  • FIG. 7 illustrates an exemplary configuration of the web center of FIG. 3 in an implementation consistent with the present invention.
  • FIG. 8 illustrates an exemplary configuration of the Internet Protocol communications (IPCOM) unit of FIG. 3 in an implementation consistent with the present invention.
  • IPCOM Internet Protocol communications
  • FIG. 9 illustrates an exemplary configuration of the very high performance backbone network service (vBNS+) unit of FIG. 3 in an implementation consistent with the present invention.
  • FIG. 10 illustrates an exemplary functional block diagram associated with one of the connectors of FIG. 5 in an implementation consistent with the present invention.
  • FIGS. 11 and 12 are flow diagrams illustrating exemplary processing by the OSS in an implementation consistent with the present invention.
  • Systems and methods consistent with the present invention provide a connection from a support system to a billing unit using a flexible software based connector.
  • the connector may also ensure that data is properly routed to other portions of the support system before storing the data in the billing unit.
  • FIG. 1 illustrates an exemplary system 100 in which methods and systems consistent with the present invention may be implemented.
  • system 100 includes a network 110 that interconnects a group of user devices 120 and an operational support system (OSS) 130 .
  • OSS operational support system
  • a typical system may include more or fewer devices than illustrated in FIG. 1.
  • system 100 may include additional devices (not shown) that aid in the transfer, processing, and/or reception of data.
  • the network 110 may include, for example, the Internet, an intranet, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a public switched telephone network (PSTN), and/or some other similar type of network.
  • the network 110 may include any type of network or combination of networks that permits routing of information from a particular source to a particular destination.
  • the user devices 120 may include a type of computer system, such as a mainframe, minicomputer, or personal computer, a type of telephone system, such as a POTS telephone or a session initiation protocol (SIP) telephone, and/or some other similar type of device that is capable of transmitting and receiving information to/from the network 110 .
  • the user device 120 may connect to the network via any conventional technique, such as a wired, wireless, or optical connection.
  • FIG. 2 illustrates an exemplary configuration of a user device 120 of FIG. 1 in an implementation consistent with the present invention.
  • the user device 120 includes a bus 210 , a processor 220 , a memory 230 , a read only memory (ROM) 240 , a storage device 250 , an input device 260 , an output device 270 , and a communication interface 280 .
  • the bus 210 may include one or more conventional buses that permit communication among the components of the user device 120 .
  • the processor 220 may include any type of conventional processor or microprocessor that interprets and executes instructions.
  • the memory 230 may include a random access memory (RAM) or another type of dynamic storage device that stores information and instructions for execution by the processor 220 .
  • RAM random access memory
  • the memory 230 may also be used to store temporary variables or other intermediate information during execution of instructions by processor 220 .
  • the ROM 240 may include a conventional ROM device and/or another type of static storage device that stores static information and instructions for the processor 220 .
  • the storage device 250 may include a magnetic disk or optical disk and its corresponding drive and/or some other type of magnetic or optical recording medium and its corresponding drive for storing information and/or instructions.
  • the input device 260 may include any conventional mechanism that permits an operator to input information to the user device 120 , such as a keyboard, a mouse, a microphone, a pen, a biometric input device, such as voice recognition device, etc.
  • the output device 270 may include any conventional mechanism that outputs information to the operator, including a display, a printer, a speaker, etc.
  • the communication interface 280 may include any transceiver-like mechanism that enables the user device 120 to communicate with other devices and/or systems, such as OSS 130 .
  • the communication interface 280 may include a modem or an Ethernet interface to a network.
  • communication interface 280 may include other mechanisms for communicating via a data network.
  • the OSS 130 provides the infrastructure for integrating applications supporting traditional telephony services and applications supporting non-traditional products/services.
  • customers using, for example, user device 120 , may manage, configure, and provision services in real time, obtain real-time billing information, and generate reports using a rules-centric middleware core.
  • a customer may perform these functions through a single point of entry using an Internet accessible web interface.
  • FIG. 3 illustrates an exemplary configuration of the OSS 130 of FIG. 1 in an implementation consistent with the present invention.
  • the OSS 130 includes a process management system 310 , a network interface 320 , a group of integrated applications 330 , a group of traditional telephony systems 340 , a voice portal unit 350 , a web center unit 360 , an Internet Protocol communications (IPCOM) unit 370 , a very high performance backbone network service (vBNS+) unit 380 , and a group of non-integrated applications 390 .
  • IPCOM Internet Protocol communications
  • vBNS+ very high performance backbone network service
  • the OSS 130 may include other components (not shown) that aid in receiving, processing, and/or transmitting data.
  • the process management system 310 acts as the backbone to the OSS 130 by providing graphical process automation, data transformation, event management, and flexible connectors for interfacing with OSS 130 components.
  • the process management system 310 uses a Common Object Request Broker Architecture (CORBA) based publish-and-subscribe messaging middleware to integrate the different components of the OSS 130 .
  • CORBA Common Object Request Broker Architecture
  • Other techniques for integrating the different components of the OSS 130 may also be used, such as extensible markup language (XML) or Enterprise JavaBeans (EJB).
  • XML extensible markup language
  • EJB Enterprise JavaBeans
  • the process management system 310 may, for example, be implemented using Vitria Technology Inc.'s BusinessWare software system.
  • the network interface 320 also referred to as the web front end, provides a graphical user interface that allows users (e.g., customers, engineers, account teams, and the like) to access the components of the OSS 130 .
  • the network interface 320 may include commercial off the shelf (COTS) software or hardware packages, such as Siteminder by Netegrity Inc. and/or iplanet by Sun Microsystems Inc., custom software or hardware or a combination of custom software/hardware and COTS software/hardware.
  • COTS commercial off the shelf
  • the network interface 320 may, for example, allow customers to request a new service or terminate an existing service and monitor or change network or user settings/preferences.
  • the network interface 320 may also allow customers to obtain reports and billing information, perform account management and perform trouble reporting and tracking, all in a real time manner.
  • the network interface 320 may also allow engineers to submit transactions to control and configure network elements and services in a real time manner.
  • the network interface 320 may also allow account teams to create and cancel accounts, generate sub-accounts from master accounts, access current account data, and access historical account data.
  • the network interface 320 authenticates users and controls actions that authenticated users are allowed to execute in the OSS 130 .
  • the network interface 320 allows users access to the components of the OSS 130 via a single sign-on technique. This single sign-on eliminates the need for users to sign in (or authenticate themselves) in order to access different components of the OSS 130 .
  • the integrated applications 330 may include, for example, a data warehouse 331 , an operational data store (ODS) 332 , a lightweight directory access protocol (LDAP) based server 333 , an LDAP database 334 , a fault management unit 335 , a data collection unit 336 , a billing unit 337 and a reporting unit 338 .
  • the data warehouse 331 may include one or more separate databases for storing data.
  • the data warehouse 331 acts as a repository for service order, account, usage and performance data.
  • the data warehouse 331 may be implemented as a relational database management system (RDBMS) and may include a server (not shown) that controls access to the data warehouse 331 .
  • RDBMS relational database management system
  • the ODS 332 may also include one or more separate databases for storing data.
  • the ODS 332 temporarily stores data that is used in the course of fulfilling, for example, account creation, service order management, and network provisioning operations.
  • the ODS 332 also stores authentication and authorization data. This data defines user's roles and privileges.
  • the ODS 332 may be a RDBMS and may include a server (not shown) that controls access to the ODS 332 .
  • the LDAP server 333 may be a general directory server that controls access to the LDAP database 334 .
  • the LDAP database 334 may be an LDAP-based repository that stores information associated with users in a hierarchical, tree-like structure.
  • the LDAP database 334 may store attributes for a user that may include preferences associated with the following exemplary services: 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.
  • the LDAP database 334 may store this information as one or more directory entries for each user. Each directory entry may include an identifier associated with the user and a collection of attributes associated with the user.
  • Each of the attributes may include a type and one or more values that identify the user's settings associated with that type.
  • the LDAP server 333 and LDAB database 334 provide a system that enables the user's preferences regarding various services to be stored, searched, updated and retrieved in an efficient manner.
  • the LDAP server 333 and LDAP database 334 are shown as separate devices. It should be understood, however, that these two devices may both be part of the same directory server in implementations consistent with the present invention.
  • the fault management unit 335 monitors and manages the operation of the OSS 130 .
  • the fault management unit 335 may receive information from every device, computer and application in the OSS 130 via the process management system 310 . In situations where a fault has been detected, the fault management unit 335 may transmit a trouble ticket identifying the fault to the appropriate system administrator.
  • the data collection unit 336 collects usage and performance data for the products supported by the OSS 130 .
  • the data collection unit 336 utilizes a hierarchical architecture, having a centralized manager that defines and manages collection and data transformation. Individual, lower level gatherers interface with source targets.
  • the data collection unit 336 may aggregate the gathered data and provide the data to other end-user applications in a desired format. For example, data collection unit 336 may provide various records to billing unit 337 .
  • the billing unit 337 receives customer usage and performance data from the data collection unit 336 and generates bills for the customer.
  • the billing unit 337 may be configured with a variety of rating rules and plans and may provide mechanisms to manage and create rating plans.
  • the rating rules may include traditional telephony styled rating rules that include time-of-day, day-of-week, distance-based, flat rate, non-recurring and recurring on a definably regular basis, such as weekly, bi-weekly, monthly, etc.
  • the billing unit 337 may also provide bonus points, airline miles and other incentives as part of the rules-based rating and billing service.
  • the billing unit 337 may provide revenue and billing reports to authorized parties. The billing unit 337 may further allow customers to access previous invoices and view current charges not yet billed. In an exemplary implementation consistent with the present invention, the billing unit 337 may transfer rated events and summary records into other billing and revenue systems. For example, billing unit 337 may receive and transfer billing information or event information to a legacy billing system (i.e., an existing billing system) that generates the actual bill. In alternative implementations, billing unit 337 may provide hard copy bills and/or provide electronic bills to a customer. In this implementation, billing unit 337 may also be configured to perform electronic payment handling. In an exemplary implementation of the present invention, the billing unit 337 may be implemented using Infranet(I by Portal Software, Inc.
  • the OSS 130 keeps the billing unit 337 up to date in a real-time manner.
  • Authorized parties may also extract real-time data from the billing unit 337 , make changes to various services and request new services, as described in more detail below.
  • the reporting unit 338 may interact with various components of the OSS 130 , such as the data warehouse 331 , the data collection unit 336 and the billing unit 337 , to provide user (i.e., customers, engineers and account team members) with the ability to obtain reports based on real-time data.
  • the reports may include, for example, billing reports, reports regarding the usage and/or performance of the network, etc.
  • the traditional telephony systems 340 may include one or more components that are typically used in a telecommunications network.
  • the traditional telephony systems 340 include one or more legacy systems, such as an order entry system, provisioning system, billing system, and the like.
  • the voice portal unit 350 provides a variety of information services to subscribers. These services may include, for example, banking, brokerage, and financial services, travel and entertainment services, distribution and shipping services, insurance services, health and pharmaceutical services, manufacturing services, and the like.
  • the voice portal unit 350 may store subscriber profiles to determine a subscriber's device preference (e.g., a cellular telephone, a personal digital assistant (PDA), a paging device, and the like) and may also track a subscriber's access to the services provided for billing purposes.
  • a subscriber's device preference e.g., a cellular telephone, a personal digital assistant (PDA), a paging device, and the like
  • PDA personal digital assistant
  • the web center 360 acts as a virtual call center by queuing, routing and distributing communications from any first location to an appropriate agent at any second location.
  • the web center 360 allows agents to handle multiple mediums (e.g., inbound telephone calls, faxes, e-mails, voicemail, voice over Internet protocol (VoIP) transactions, etc.) via a single browser-based interface.
  • the web center 360 may be implemented using CallCenter@nywhere from Telephony@Work, Inc.
  • the IPCOM unit 370 may include one or more devices that provide VoIP services to subscribers.
  • the subscribers may make and receive calls via an IP communications network using, for example, session initiation protocol (SIP) telephones.
  • IP session initiation protocol
  • the IPCOM unit 370 may support the following services: 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.
  • Customers may set or change attributes associated with these features via the network interface 320 .
  • the vBNS+unit 380 provides the IP infrastructure for the IP communications network.
  • the vBNS+unit 380 may include a group of edge routers for routing packets in the network.
  • the non-integrated applications 390 may include, for example, a security unit, a trouble ticketing unit, and a fault manager.
  • the security unit may include one or more firewalls for securing the network interface 320 , telephone equipment (e.g., PBX, switch, redirect server, etc.) and network equipment.
  • the trouble ticketing unit manages the issuance and resolution of trouble tickets and the fault manager monitors the hardware components of the OSS 130 .
  • FIG. 4 illustrates an exemplary configuration of the process management system 310 of FIG. 3 in an implementation consistent with the present invention.
  • the process management system 310 includes a bus 410 , a processor 420 , a memory 430 , an input device 440 , an output device 450 , and a communication interface 460 .
  • the bus 410 permits communication among the components of the process management system 310 .
  • the processor 420 may include any type of conventional processor or microprocessor that interprets and executes instructions.
  • the memory 430 may include a RAM or another type of dynamic storage device that stores information and instructions for execution by the processor 420 ; a ROM or another type of static storage device that stores static information and instructions for use by the processor 420 ; and/or some type of magnetic or optical recording medium and its corresponding drive.
  • the input device 440 may include any conventional mechanism that permits an operator to input information to the process management system 310 , such as a keyboard, a mouse, a pen, voice recognition and/or biometric mechanisms, and the like.
  • the output device 450 may include any conventional mechanism that outputs information to the operator, including a display, a printer, a speaker, etc.
  • the communication interface 460 may include any transceiver-like mechanism that enables the process management system 310 to communicate with other devices and/or systems, such as the network interface 320 , integrated applications 330 , traditional telephony systems 340 , etc. via a wired, wireless, or optical connection.
  • process management system 310 may run a CORBA-based program to integrate various components of the OSS 130 .
  • execution of the sequences of instructions associated with the program contained in a computer-readable medium, such as memory 430 causes processor 420 to implement the functional operations described below.
  • processor 420 may be used in place of or in combination with software instructions to implement the present invention.
  • the present invention is not limited to any specific combination of hardware circuitry and software.
  • FIG. 5 illustrates an exemplary functional block diagram of the process management system 310 of FIG. 3 in an implementation consistent with the present invention.
  • the process management system 310 includes a process automator 510 , an analyzer 520 , a group of connectors 530 , a communicator 540 and a central engine 550 .
  • these elements are implemented as functional modules of a software program executed by processor 420 of the process management system 310 .
  • the process management system 310 may execute additional functional modules (not shown) that aid in the reception, processing, and/or transmission of data.
  • the processor automator 510 includes a modeling tool that allows event processing to be visually modeled by engineers and product development analysts. The process automator 510 can then execute these models to create an automated business process executed by the central engine 550 .
  • the analyzer 520 provides on-going and real-time monitoring of the components of the OSS 130 .
  • the analyzer 520 delivers reports, history, and trending on events processed through the central engine 550 .
  • the connectors 530 allow the components of the OSS 130 to interact and communicate with the process management system 310 .
  • the OSS components may communicate with the process management system 310 via standard messaging or through full publish/subscribe processing.
  • the communicator 540 enables the process management system 310 to communicate with various components of the 05 S 130 using transmission control protocol/Internet protocol (TCP/IP).
  • TCP/IP transmission control protocol/Internet protocol
  • the central engine 550 is the core of the software program and executes customized rules to enable the process management system 310 to integrate the various systems of the OSS 130 , as described in more detail below. It should be understood that the central engine 550 may be programmed to perform any rules-based processing based on the particular requirements associated with managing the OSS 130 .
  • FIG. 6 illustrates an exemplary configuration of the voice portal unit 350 of FIG. 3 in an implementation consistent with the present invention.
  • the voice portal unit 350 includes an extensible Program Management (XPM) unit 610 , one or more voice portal application servers 620 , and a customer directory database 630 .
  • the XPM unit 610 receives user profile information from the network interface 320 via the process management system 310 and stores this information for use by the voice portal application servers 620 .
  • the XPM unit 610 may also receive other information, such as information identifying the device(s) (e.g., PDA, cellular telephone, pager, computer, etc.) by which a user wishes to receive the information associated with a particular service(s) to which the user has subscribed.
  • the device(s) e.g., PDA, cellular telephone, pager, computer, etc.
  • the voice portal application servers 620 may include one or more servers that interact with the XPM unit 610 to provide, for example, banking, brokerage, and financial services, travel, entertainment, sports and weather services, distribution and shipping services, insurance services, health and pharmaceutical services, manufacturing services, and the like. Voice portal application servers 620 may also provide data collection unit 336 with information regarding what services are accessed and by whom. The data collection unit 336 may then pass this information to billing unit 337 for billing purposes.
  • the voice portal application servers 620 may be located at the OSS 130 or distributed throughout the network 110 .
  • the customer directories 630 may store information relating to the services provided by the voice portal application servers 620 . For example, the customer directories 630 may store stock quotes, current weather forecasts, real-time sports scores, etc.
  • FIG. 7 illustrates an exemplary configuration of the web center 360 of FIG. 3 in an implementation consistent with the present invention.
  • the web center 360 includes a communications server 710 and an agent information database 720 .
  • the communication server 710 queues, routes, and distributes communications from any first location to an appropriate agent at any second location.
  • the communications server 710 may determine the appropriate agent based on data stored in the agent information database 720 .
  • the agent information database 720 may store agent activity information, the particular skills of the agents, and the like.
  • the usage information may be transmitted to the data collection unit 336 and then to the billing unit 337 for billing. Users may, via the network interface 320 , provision new services, such as order a toll free number.
  • FIG. 8 illustrates an exemplary configuration of the IPCOM unit 370 of FIG. 3 in an implementation consistent with the present invention.
  • the IPCOM unit 370 includes a redirect server 810 , a redirect server database 812 , network server 820 , customer provided equipment (CPE) enterprise gateways/routers 830 and network gateways 840 .
  • the redirect server 810 executes an object request broker (ORB) that is CORBA compliant.
  • the redirect server 810 stores data in database 812 relating to call processing (e.g., information identifying the device by which the subscriber wishes to receive the call, network configuration information, etc.), subscriber profiles (e.g., a subscriber identifier) and network-supported features.
  • call processing e.g., information identifying the device by which the subscriber wishes to receive the call, network configuration information, etc.
  • subscriber profiles e.g., a subscriber identifier
  • the redirect server 810 may decide how to route calls based on information stored in redirect server database 812 .
  • the redirect server 810 and the redirect server database 812 are shown as separate devices. It should be understood that these devices may both be part of the same server in implementations consistent with the present invention.
  • the redirect server 810 forwards the routing information to the network server 820 .
  • the network server 820 also referred to as the proxy server or SIP server, processes the actual calls made over the IP communications network.
  • the network server 820 directs the calls to CPE enterprise gateways/routers 830 or network gateways 840 based on the type of call and the network-supported features to which a customer subscribes.
  • the network-supported features may include, for example, 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.
  • a subscriber may change attributes of these network-supported features using the network interface 320 .
  • the redirect server 810 may also communicate with the data collection unit 336 .
  • the CPE enterprise gateways/routers 830 may include one or more gateways for linking POTS telephone systems to the IP communications network.
  • the CPE enterprise gateways/routers 830 may, for example, connect to a customer's private branch exchange (PBX) and convert TDM voice data into VoIP packets and voice signaling into SIP messages.
  • PBX private branch exchange
  • the CPE enterprise gateways/routers 830 may also include one or more routers that receive information from a SIP phone over a network, such as a LAN or WAN.
  • the network gateways 840 may include one or more gateways for linking the IP communications network to the PSTN in a well known manner.
  • the CPE enterprise gateways/routers 830 and network gateways 840 track customer access and transmit this customer access data to the data collection unit 336 for billing purposes.
  • FIG. 9 illustrates an exemplary configuration of the vBNS+unit 380 of FIG. 3 in an implementation consistent with the present invention.
  • the vBNS+unit 380 includes a group of edge routers 910 that route packets to/from the vBNS+core network 920 .
  • the edge routers 910 may connect to the network server 820 , redirect server 810 , network gateways 830 , customer's CPE equipment, other routers in the IP communications network, directly to SIP telephones, etc.
  • the vBNS+core 920 may include one or more core routers for routing packets between edge routers.
  • the OSS 130 may provide a number of products and services to users, such as services associated with voice portal unit 350 , web center 360 , IPCOM unit 370 and vBNS+unit 380 . Each of these products has unique billing requirements.
  • the data collection unit 336 retrieves data from network elements associated with these products, normalizes the data records into a format recognized by billing unit 337 and forwards the data records to billing unit 337 .
  • the billing unit 337 may include a database that stores information associated with a customer's account (e.g., the customer's calling plan information, the services subscribed to by the customer, etc.). The billing unit 337 may also store rating information to rate the data records so that the customer is billed the appropriate amount for the services it receives. At various times, the customer, account personnel and engineering personnel may require access to the billing unit 337 .
  • the present invention is directed to systems and methods for enabling the process management system 310 to communicate with the billing unit 337 to support various parties requiring access to the billing unit 337 .
  • FIG. 10 is an exemplary functional block diagram illustrating one of the connectors 530 (FIG. 5) of the process management system 310 that enables the process management system 310 to communicate with the billing unit 337 .
  • connector 532 may be a software module (i.e., part of the software program) executed by process management system 310 .
  • the connector 532 may be a Java-based connector that enables the process management system 310 to communicate with the billing unit 337 .
  • the connector 532 may include a channel source 1010 , a transformer 1020 , a client 1030 and a channel target 1040 . These elements may represent functional processes implemented in software.
  • the connector 532 acts as a conversion point to drive data to and from the billing unit 337 , since the billing unit 337 is not capable of performing a publish/subscribe activity on its own without the connector 532 .
  • the connector 532 manages the semantics associated with managing event queues on a channel on behalf of the billing unit 337 .
  • the connector 532 communicates with the billing unit 337 to enable a user to retrieve information stored in the billing unit 337 , modify or delete information stored in the billing unit 337 and create new service identification information.
  • a customer or a member of an account team may wish to retrieve current charges associated with the customer's account.
  • the user may access the process management system 310 using network interface 320 .
  • the process management system 310 receives the request and invokes connector 532 to establish communications with the billing unit 337 and retrieve the desired information.
  • the connector 532 uses customized opcodes to retrieve the desired information, as described in more detail below. Using custom opcodes provides for the retrieval of data from the billing unit 337 in an efficient manner.
  • the connector 532 may also include logic that allows “event” information to be written to the billing unit 337 using a 2-phase commit procedure.
  • the event information may include the user-entered information received via the network interface 320 .
  • the process management system 310 ensures that data written to the billing unit 337 is consistent with data stored in other portions of the OSS 130 , as described in more detail below.
  • the channel source 1010 represents input data associated with user-entered event information.
  • the process management system 310 receives the request via the network interface 320 and processes the request.
  • the central engine 550 (FIG. 5) publishes an event on a channel, such as the channel corresponding to the channel source 1010 .
  • the transformer 1020 subscribes to the channel associated with the channel source 1010 and receives the event information.
  • the transformer 1020 may then identify the particular type of event received from the channel source 1010 . For example, transformer 1020 determines what service/product the event is associated with and whether the event is associated with a user requesting information or a user attempting to modify or store new information associated with a particular service/product. The transformer 1020 may then determine how to format the data associated with the received event. The transformer 1020 may also invoke client 1030 to establish communications with the billing unit 337 . The client 1030 may be used to transmit the re-formatted event information to the billing unit 337 .
  • the transformer 1020 may also publish the event to various channel targets 1040 subscribed to by other modules/external systems.
  • the transformer 1030 may publish event information to a channel subscribed to by a connector associated with the ODS 332 , represented by channel target 1040 .
  • the connector 532 may publish event information to channels associated with other modules/externals systems, based on the particular system requirements.
  • the billing unit 337 may include a database that stores information associated with customer's accounts and the services to which the customer subscribes.
  • the billing unit 337 may execute a billing unit process 1050 to facilitate the actual execution of the received event information from the connector 532 , as described in more detail below.
  • the billing unit 337 may also communicate with other systems via the process management system 310 before performing the desired operation associated with the received event. For example, the billing unit 337 may prepare a transaction for writing to its database. The billing unit 337 , however, may wait for a “go ahead” indication from the connector 532 before actually writing the data to its database. In this manner, the connector 532 may essentially perform a 2-phase commit process associated with a received event to ensure that the actual data written to the billing unit 337 is consistent with information in other databases of the OSS 130 .
  • FIG. 11 is a flow diagram, consistent with the present invention, illustrating exemplary processing associated with connector 532 .
  • Processing may begin when a user accesses the OSS 130 (act 1110 ).
  • the user may wish to change his/her particular plan associated with a particular service, such as select a plan with unlimited minutes for VoIP communications.
  • the user may access the OSS 130 with a conventional user device 120 via network 110 (FIG. 1).
  • the user may provide a user identification and/or password and network interface 320 may determine whether the user is authorized to access/modify various information stored in the OSS 130 .
  • GUI graphical user interface
  • the GUI may include a number of options associated with the user's account. These options may include selections associated with modifying the user's plan, selections associated with receiving billing information, etc.
  • the user wishes to change his VoIP plan.
  • the user selects “customer configuration” or a similar graphic/text input and transmits the selection to the OSS 130 (act 1130 ).
  • the OSS 130 receives the selection and downloads a customer configuration interface GUI to the user device 120 (act 1130 ).
  • the GUI may also include pre-stored information associated with that user.
  • the pre-stored information may indicate the user's plan information for making/receiving VoIP calls.
  • the user selects “modify VoIP plan” or a similarly labeled input on the GUI.
  • the user may then input the desired modification and transmit the information to the OSS 130 (act 1140 ).
  • the process management system 310 receives the user-entered information, also referred to as an “event,” via the network interface 320 (act 1150 ).
  • the central engine 550 may then publish the event on a channel (act 1150 ).
  • the central engine 550 publishes the event to a channel subscribed to by connector 532 , represented by channel source 1010 (FIG. 10).
  • the connector 532 receives the event information (act 1160 ).
  • the transformer 1020 extracts the event contents, identifies the event type based on the received information and converts the event information into an appropriate format based on the event type (act 1160 ).
  • the transformer 1020 may format the event information for the billing unit 337 .
  • the transformer 1020 may also publish the event information to other systems/units, represented by channel target 1040 (act 1160 ).
  • the transformer 1020 may publish the event to a channel target associated with the ODS 332 .
  • the ODS 332 essentially acts as the database of record for the OSS 130 .
  • transformer 1020 may also publish the event information to other channels, represented by channel target 1040 .
  • channel targets may be associated with other external systems/connectors that may be involved in storing or processing information associated with the user's profile, such as the user's VoIP plan.
  • a connector associated with the ODS 332 receives the event information, extracts the event contents, converts the event information into an appropriate format for the ODS 332 and downloads the event information to the ODS (act 1170 ).
  • ODS 332 may be an RDBMS.
  • one of connectors 530 that is designed to communicate with an RDBMS may be utilized to establish communications with ODS 332 .
  • the ODS 332 receives the event information and stores the event information. If the ODS 332 is unable to store the information or does not receive the information, the connector 532 may queue the event information. Assuming that the ODS 332 write operation is successful, the ODS 332 sends a signal back to the process management system 310 indicating that the event data has been stored (act 1170 ).
  • the transformer 1020 invokes the client 1030 to establish communications with the billing unit 337 (act 1180 ).
  • the client 1030 establishes the semantics associated with communicating with the billing unit 337 .
  • the client 1030 may communicate with the billing unit 337 via method calls using Java remote method invocation over Internet inter-ORB protocol (RMI over IIOP).
  • RMI over IIOP Java remote method invocation over Internet inter-ORB protocol
  • the client 1030 may communicate with the billing unit 337 using other techniques.
  • the connector 532 may queue the event, as described in more detail below with respect to FIG. 12.
  • the billing unit 337 receives the event information from client 1030 and initiates a billing unit process 1050 to update the user's plan information (act 1180 ).
  • the billing unit process 1050 then stores the user-entered event information in the billing unit's 337 database (act 1180 ).
  • This procedure enables the billing unit 337 to ensure that the event information will be implemented in all the proper systems/databases before the billing unit 337 commits the operation to its database, thereby maintaining consistency across the various systems in the OSS 130 .
  • the billing unit 337 may signal the ODS 332 , via process management system 310 , to write additional data to the ODS 332 .
  • the ODS 332 may store the order-related event information.
  • the billing unit 337 may then store the information in its database.
  • the billing unit 337 may create a new service identifier associated with the new service. In this case, the billing unit 337 passes the service identifier back to the ODS 332 , via the process management system 310 .
  • the ODS 332 receives the service identifier and completes the order record by storing the service identifier assigned to the service by the billing unit 337 .
  • the central engine 550 may publish the event to the channel target associated with ODS 332 at the same time that the event is published to the channel subscribed to by the connector 532 .
  • connector 532 may write the data to the billing unit 337 at the same time the data is being written to the ODS 332 . If the ODS 332 returns an error, i.e., the data was not successfully written to the ODS 332 , the connector 532 may signal the billing unit 337 to “roll back” the transaction.
  • the error may be data related (e.g., the user entered information regarding a request to modify calling plan information that is outside an accepted range) or equipment related (e.g., the ODS 332 is offline).
  • the connector 532 signals the billing unit process 1050 to return the billing unit's 337 database to the state it was in prior to receiving the event information. This ensures that the billing unit's 337 database and the ODS 332 remain consistent.
  • FIG. 12 is a flow diagram, consistent with the present invention, illustrating exemplary processing associated with establishing communications with billing unit 337 .
  • the client 1030 cannot establish a connection with the billing unit 337 at act 1180 (act 1210 ).
  • the billing unit 337 is offline, busy with another event, or generally unavailable. In this case, client 1030 queues the event (act 1220 ).
  • the client 1030 may also start a thread to check when the connection to the billing unit 337 can be made, i.e., determine when the billing unit 337 is available (act 1230 ). For example, the client 1030 may open a new thread that periodically “pings” the billing unit 337 to determine whether the billing unit 337 is available (act 1240 ). If the billing unit 337 is not available, the client 1030 may re-check the billing unit 337 every predetermined period of time. The predetermined period may be configurable. In addition, the client 1030 may repeat this process until a positive response is received or may ping the billing unit 337 a configurable number of times.
  • the client 1030 When the billing unit 337 is available, the client 1030 establishes the communication link to the billing unit 337 and downloads the queued event information to the billing unit 337 (act 1250 ). The billing unit 337 may then store the event information in its database (act 1250 ).
  • the client 1030 may provide an alarm message indicating that the billing unit 337 is unavailable (act 1260 ). This alarm may be sent to a device, such as fault management unit 335 .
  • the connector 532 may also provide information as to why the connection with the billing unit 337 cannot be established. For example, the connector 532 may indicate that the billing unit 337 is offline. The connector 532 may then send an error message to the user.
  • the connector 532 may also signal the ODS 332 , via process management system 310 to roll back the previous write operation (act 1270 ). In this manner, data across the OSS 130 remains consistent.
  • customers, account personnel and engineering personnel may wish to access the billing unit 337 to retrieve information.
  • a party may wish to retrieve master account information, retrieve all services performed for a particular master account, retrieve all current charges for a master account, retrieve detailed charges for a master account, or retrieve any other information associated with the customer's account.
  • the user may make the request for information via network interface 320 in a manner similar to that described with respect to acts 1110 to 1150 .
  • the connector 532 recognizes that the event is a request for information and does not publish the event to any other channel targets.
  • the transformer 1020 (FIG. 10) opens client 1030 , which establishes communications with billing unit 337 .
  • the billing unit process 1050 retrieves the desired information and the process management system 310 provides the requested information to the user.
  • an authorized user may request any type of information regarding a customer's account via network interface 320 .
  • the process management system 310 publishes these type of events to a channel subscribed to by connector 532 .
  • Connector 532 identifies the type of request, formats the request for billing unit 337 and retrieves the desired information.
  • the process management system 310 then returns the requested data to the authorized user.
  • the process management system 310 may use custom opcodes, as described previously.
  • the custom opcodes may be implemented in Java using RMI over IIOP.
  • the particular custom opcodes may be designed based on the service provider's business requirements so that the same opcodes can be used for any of the products/services in the OSS 130 .
  • the same opcode may be used to retrieve account information associated with services provided by voice portal unit 350 , web center 360 , IPCOM unit 370 and vBNS+unit 380 .
  • the programming associated with the customized opcodes may be minimized to take advantage of commonality associated with the various products/services of the OSS 130 .
  • the connector 532 uses the appropriate custom opcode identifying the request.
  • the billing unit 337 recognizes the opcode and returns the requested information on the customer's account.
  • Systems and methods consistent with the present invention provide a flexible connection between a support system and a billing unit 337 to allow a user to modify information regarding the services subscribed to by the user, request new services and request information from the billing unit 337 .
  • An advantage of the invention is that the connector may be easily customized to support new products/services.
  • Another advantage of the invention is that the connector is fault tolerant. For example, when the billing unit 337 is unavailable, the connector 532 includes provisions for retrying the connection. This results in a more flexible and reliable system.
  • a further advantage of the present invention is the system can be easily modified to support various vendors' equipment.
  • the connector 532 described above essentially uses a two-tiered approach to connect with the billing unit 337 .
  • the first tier deals with the semantics of the physical connection and protocol between the connector 532 and the target billing unit 337 .
  • the second tier described above in relation to the transformer process deals with transaction completion and fault tolerance. If the particular vendor associated with the billing unit 337 changes, only the first tier of the connector needs to be modified to support this vendor. Therefore, the connector 532 facilitates the integration of new systems, thereby reducing development time and costs.
  • the present invention has been described with a few examples with respect to requesting changes in service, requesting new services and requesting information stored in the billing unit 337 . It should be understood that the present invention may be used to support any number of requests associated with account management, order management, service management and bill presentation.
  • aspects of the present invention have been described as series of acts in relation to FIGS. 11 and 12. It should be understood that the order of these acts may vary in other implementations of the present invention. Moreover, non-dependent acts may be performed in parallel.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Probability & Statistics with Applications (AREA)
  • Technology Law (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Abstract

An operational support system includes an integration platform and a billing system. The integration platform receives user-entered information and generates an event based on the user-entered information. The integration platform publishes the event on a channel subscribed to by a connector associated with the billing system. The connector transforms the event information to a format compatible with the billing system and forwards the event to a channel that is associated with a data storage system. The connector establishes communication with the billing system and downloads the information to the billing system in response to a message indicating that the data storage system received the event information.

Description

    RELATED APPLICATIONS
  • This application claims priority under 35 U.S.C. §119(e) based on the following U.S. Provisional Applications: Serial Nos. 60/276,923, 60/276,953, 60/276,955, and 60/276,954 all filed on Mar. 20, 2001, the disclosures of which are incorporated herein by reference.[0001]
  • FIELD OF THE INVENTION
  • The present invention relates generally to support systems for telecommunications service providers and, more particularly, to providing a connector from an integration platform to a billing unit. [0002]
  • BACKGROUND OF THE INVENTION
  • Telecommunications service providers continually increase the number of services and products they offer to customers. As competition increases, service providers must provide an increased level of support for these services while keeping costs down. [0003]
  • In conventional support systems, a service provider may use a system integrator to develop solutions that tie together multi-vendor hardware systems. The system integrator typically uses a commercial off the shelf (COTS) software package to integrate the various hardware systems. [0004]
  • One problem with using COTS software to integrate multi-vendor hardware systems is that the selected software is often incompatible with all of the existing hardware systems. In this case, the service provider is often forced to replace legacy systems (i.e., existing systems) in order to maintain full functionality. [0005]
  • Another problem with using COTS software to integrate multi-vendor hardware systems is that the selected software package often does not include pre-packaged modules that permit the software to communicate with various hardware platforms. This may cause the system integrator to exclude one or more hardware platforms from the support system. [0006]
  • SUMMARY OF THE INVENTION
  • There exists a need for systems and methods that improve problems associated with providing a system to support various services and products that a telecommunication service provider offers. [0007]
  • These and other needs are met by the present invention where an operational support system (OSS) integrates various hardware and software platforms. The OSS includes a middleware core that may be customized to integrate various applications/platforms and to ensure that data from one application can be routed to the appropriate destination(s). [0008]
  • According to one aspect of the invention, a method for communicating from a first system to a billing system is provided. The method includes receiving user-entered information at the first system and sending event information to a channel, where the event information is based on the user-entered information and the channel is subscribed to by a first connector associated with the billing system. The method also includes receiving, by the first connector, the event information, transforming the event information to a format compatible with the billing system and publishing the event information to a channel subscribed to by a second connector associated with a database system. The method further includes sending, by the database system, an indication that the database system received the event information and receiving the indication by the first connector. The method also includes establishing, by the first connector, communications with the billing system and downloading the transformed event information to the billing system. [0009]
  • Another aspect of the present invention provides a computer-readable medium having stored 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 billing system. The instructions also cause the processor to receive the data associated with at least one of adding, deleting and modifying information stored in the billing system, format the data based on a type associated with the received data and forward the data to an operational data storage system. The instructions further cause the processor to receive an indication that the operational data storage system received the data, establish communications with the billing system in response to receiving the indication and download the formatted data to the billing system. [0010]
  • A further aspect of the present invention provides a software-based connector for communicating between an integration platform and a billing system using remote invocation over Internet inter-ORB protocol. The connector includes a transformer module configured to receive input information associated with a request for information from the billing system, identify an opcode corresponding to the request and format the request to include the identified opcode. The connector also includes a client module configured to establish communications with the billing system, transmit the formatted request to the billing system and receive information from the billing system in response to the request. [0011]
  • Other features and advantages of the present invention will become readily apparent to those skilled in this art from the following detailed description. The embodiments shown and described provide illustration of the best mode contemplated for carrying out the invention. The invention is capable of modifications in various obvious respects, all without departing from the invention. Accordingly, the drawings are to be regarded as illustrative in nature, and not as restrictive.[0012]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Reference is made to the attached drawings, wherein elements having the same reference number designation may represent like elements throughout. [0013]
  • FIG. 1 is a block diagram of an exemplary system in which methods and systems consistent with the present invention may be implemented. [0014]
  • FIG. 2 illustrates an exemplary configuration of a user device of FIG. 1 in an implementation consistent with the present invention. [0015]
  • FIG. 3 illustrates an exemplary configuration of the operational support system (OSS) of FIG. 1 in an implementation consistent with the present invention. [0016]
  • FIG. 4 illustrates an exemplary configuration of the process management system of FIG. 3 in an implementation consistent with the present invention. [0017]
  • FIG. 5 illustrates an exemplary functional block diagram of the process management system of FIG. 3 in an implementation consistent with the present invention. [0018]
  • FIG. 6 illustrates an exemplary configuration of the voice portal of FIG. 3 in an implementation consistent with the present invention. [0019]
  • FIG. 7 illustrates an exemplary configuration of the web center of FIG. 3 in an implementation consistent with the present invention. [0020]
  • FIG. 8 illustrates an exemplary configuration of the Internet Protocol communications (IPCOM) unit of FIG. 3 in an implementation consistent with the present invention. [0021]
  • FIG. 9 illustrates an exemplary configuration of the very high performance backbone network service (vBNS+) unit of FIG. 3 in an implementation consistent with the present invention. [0022]
  • FIG. 10 illustrates an exemplary functional block diagram associated with one of the connectors of FIG. 5 in an implementation consistent with the present invention. [0023]
  • FIGS. 11 and 12 are flow diagrams illustrating exemplary processing by the OSS in an implementation consistent with the present invention. [0024]
  • DETAILED DESCRIPTION
  • The following detailed description of implementations consistent with the present invention refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims and equivalents. [0025]
  • Systems and methods consistent with the present invention provide a connection from a support system to a billing unit using a flexible software based connector. The connector may also ensure that data is properly routed to other portions of the support system before storing the data in the billing unit. [0026]
  • EXEMPLARY SYSTEM
  • FIG. 1 illustrates an [0027] exemplary system 100 in which methods and systems consistent with the present invention may be implemented. In FIG. 1, system 100 includes a network 110 that interconnects a group of user devices 120 and an operational support system (OSS) 130. It will be appreciated that a typical system may include more or fewer devices than illustrated in FIG. 1. Moreover, system 100 may include additional devices (not shown) that aid in the transfer, processing, and/or reception of data.
  • The [0028] network 110 may include, for example, the Internet, an intranet, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a public switched telephone network (PSTN), and/or some other similar type of network. In fact, the network 110 may include any type of network or combination of networks that permits routing of information from a particular source to a particular destination.
  • The [0029] user devices 120 may include a type of computer system, such as a mainframe, minicomputer, or personal computer, a type of telephone system, such as a POTS telephone or a session initiation protocol (SIP) telephone, and/or some other similar type of device that is capable of transmitting and receiving information to/from the network 110. The user device 120 may connect to the network via any conventional technique, such as a wired, wireless, or optical connection.
  • FIG. 2 illustrates an exemplary configuration of a [0030] user device 120 of FIG. 1 in an implementation consistent with the present invention. In FIG. 2, the user device 120 includes a bus 210, a processor 220, a memory 230, a read only memory (ROM) 240, a storage device 250, an input device 260, an output device 270, and a communication interface 280. The bus 210 may include one or more conventional buses that permit communication among the components of the user device 120.
  • The [0031] processor 220 may include any type of conventional processor or microprocessor that interprets and executes instructions. The memory 230 may include a random access memory (RAM) or another type of dynamic storage device that stores information and instructions for execution by the processor 220. The memory 230 may also be used to store temporary variables or other intermediate information during execution of instructions by processor 220.
  • The [0032] ROM 240 may include a conventional ROM device and/or another type of static storage device that stores static information and instructions for the processor 220. The storage device 250 may include a magnetic disk or optical disk and its corresponding drive and/or some other type of magnetic or optical recording medium and its corresponding drive for storing information and/or instructions.
  • The [0033] input device 260 may include any conventional mechanism that permits an operator to input information to the user device 120, such as a keyboard, a mouse, a microphone, a pen, a biometric input device, such as voice recognition device, etc. The output device 270 may include any conventional mechanism that outputs information to the operator, including a display, a printer, a speaker, etc.
  • The [0034] communication interface 280 may include any transceiver-like mechanism that enables the user device 120 to communicate with other devices and/or systems, such as OSS 130. For example, the communication interface 280 may include a modem or an Ethernet interface to a network. Alternatively, communication interface 280 may include other mechanisms for communicating via a data network.
  • Returning to FIG. 1, the [0035] OSS 130 provides the infrastructure for integrating applications supporting traditional telephony services and applications supporting non-traditional products/services. Through OSS 130, customers, using, for example, user device 120, may manage, configure, and provision services in real time, obtain real-time billing information, and generate reports using a rules-centric middleware core. In one embodiment, a customer may perform these functions through a single point of entry using an Internet accessible web interface.
  • FIG. 3 illustrates an exemplary configuration of the [0036] OSS 130 of FIG. 1 in an implementation consistent with the present invention. As illustrated, the OSS 130 includes a process management system 310, a network interface 320, a group of integrated applications 330, a group of traditional telephony systems 340, a voice portal unit 350, a web center unit 360, an Internet Protocol communications (IPCOM) unit 370, a very high performance backbone network service (vBNS+) unit 380, and a group of non-integrated applications 390. It will be appreciated that the OSS 130 may include other components (not shown) that aid in receiving, processing, and/or transmitting data.
  • The [0037] process management system 310 acts as the backbone to the OSS 130 by providing graphical process automation, data transformation, event management, and flexible connectors for interfacing with OSS 130 components. In one implementation consistent with the present invention, the process management system 310 uses a Common Object Request Broker Architecture (CORBA) based publish-and-subscribe messaging middleware to integrate the different components of the OSS 130. Other techniques for integrating the different components of the OSS 130 may also be used, such as extensible markup language (XML) or Enterprise JavaBeans (EJB). The process management system 310 may, for example, be implemented using Vitria Technology Inc.'s BusinessWare software system.
  • The [0038] network interface 320, also referred to as the web front end, provides a graphical user interface that allows users (e.g., customers, engineers, account teams, and the like) to access the components of the OSS 130. The network interface 320 may include commercial off the shelf (COTS) software or hardware packages, such as Siteminder by Netegrity Inc. and/or iplanet by Sun Microsystems Inc., custom software or hardware or a combination of custom software/hardware and COTS software/hardware.
  • The [0039] network interface 320 may, for example, allow customers to request a new service or terminate an existing service and monitor or change network or user settings/preferences. The network interface 320 may also allow customers to obtain reports and billing information, perform account management and perform trouble reporting and tracking, all in a real time manner. The network interface 320 may also allow engineers to submit transactions to control and configure network elements and services in a real time manner. The network interface 320 may also allow account teams to create and cancel accounts, generate sub-accounts from master accounts, access current account data, and access historical account data.
  • The [0040] network interface 320 authenticates users and controls actions that authenticated users are allowed to execute in the OSS 130. In one implementation consistent with the present invention, the network interface 320 allows users access to the components of the OSS 130 via a single sign-on technique. This single sign-on eliminates the need for users to sign in (or authenticate themselves) in order to access different components of the OSS 130.
  • The integrated [0041] applications 330 may include, for example, a data warehouse 331, an operational data store (ODS) 332, a lightweight directory access protocol (LDAP) based server 333, an LDAP database 334, a fault management unit 335, a data collection unit 336, a billing unit 337 and a reporting unit 338. The data warehouse 331 may include one or more separate databases for storing data. The data warehouse 331 acts as a repository for service order, account, usage and performance data. In one implementation, the data warehouse 331 may be implemented as a relational database management system (RDBMS) and may include a server (not shown) that controls access to the data warehouse 331.
  • The [0042] ODS 332 may also include one or more separate databases for storing data. The ODS 332 temporarily stores data that is used in the course of fulfilling, for example, account creation, service order management, and network provisioning operations. The ODS 332 also stores authentication and authorization data. This data defines user's roles and privileges. Like the data warehouse 331, the ODS 332 may be a RDBMS and may include a server (not shown) that controls access to the ODS 332.
  • The [0043] LDAP server 333 may be a general directory server that controls access to the LDAP database 334. The LDAP database 334 may be an LDAP-based repository that stores information associated with users in a hierarchical, tree-like structure. For example, the LDAP database 334 may store attributes for a user that may include preferences associated with the following exemplary services: 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. The LDAP database 334 may store this information as one or more directory entries for each user. Each directory entry may include an identifier associated with the user and a collection of attributes associated with the user. Each of the attributes may include a type and one or more values that identify the user's settings associated with that type. In this manner, the LDAP server 333 and LDAB database 334 provide a system that enables the user's preferences regarding various services to be stored, searched, updated and retrieved in an efficient manner. The LDAP server 333 and LDAP database 334 are shown as separate devices. It should be understood, however, that these two devices may both be part of the same directory server in implementations consistent with the present invention.
  • The [0044] fault management unit 335 monitors and manages the operation of the OSS 130. The fault management unit 335 may receive information from every device, computer and application in the OSS 130 via the process management system 310. In situations where a fault has been detected, the fault management unit 335 may transmit a trouble ticket identifying the fault to the appropriate system administrator.
  • The [0045] data collection unit 336 collects usage and performance data for the products supported by the OSS 130. In one implementation, the data collection unit 336 utilizes a hierarchical architecture, having a centralized manager that defines and manages collection and data transformation. Individual, lower level gatherers interface with source targets. The data collection unit 336 may aggregate the gathered data and provide the data to other end-user applications in a desired format. For example, data collection unit 336 may provide various records to billing unit 337.
  • The [0046] billing unit 337 receives customer usage and performance data from the data collection unit 336 and generates bills for the customer. The billing unit 337 may be configured with a variety of rating rules and plans and may provide mechanisms to manage and create rating plans. The rating rules may include traditional telephony styled rating rules that include time-of-day, day-of-week, distance-based, flat rate, non-recurring and recurring on a definably regular basis, such as weekly, bi-weekly, monthly, etc. The billing unit 337 may also provide bonus points, airline miles and other incentives as part of the rules-based rating and billing service.
  • The [0047] billing unit 337 may provide revenue and billing reports to authorized parties. The billing unit 337 may further allow customers to access previous invoices and view current charges not yet billed. In an exemplary implementation consistent with the present invention, the billing unit 337 may transfer rated events and summary records into other billing and revenue systems. For example, billing unit 337 may receive and transfer billing information or event information to a legacy billing system (i.e., an existing billing system) that generates the actual bill. In alternative implementations, billing unit 337 may provide hard copy bills and/or provide electronic bills to a customer. In this implementation, billing unit 337 may also be configured to perform electronic payment handling. In an exemplary implementation of the present invention, the billing unit 337 may be implemented using Infranet(I by Portal Software, Inc.
  • As customer orders and accounts are created or modified through normal business functions, the [0048] OSS 130 keeps the billing unit 337 up to date in a real-time manner. Authorized parties may also extract real-time data from the billing unit 337, make changes to various services and request new services, as described in more detail below.
  • The [0049] reporting unit 338 may interact with various components of the OSS 130, such as the data warehouse 331, the data collection unit 336 and the billing unit 337, to provide user (i.e., customers, engineers and account team members) with the ability to obtain reports based on real-time data. The reports may include, for example, billing reports, reports regarding the usage and/or performance of the network, etc.
  • The [0050] traditional telephony systems 340 may include one or more components that are typically used in a telecommunications network. In one implementation, the traditional telephony systems 340 include one or more legacy systems, such as an order entry system, provisioning system, billing system, and the like.
  • The [0051] voice portal unit 350 provides a variety of information services to subscribers. These services may include, for example, banking, brokerage, and financial services, travel and entertainment services, distribution and shipping services, insurance services, health and pharmaceutical services, manufacturing services, and the like. The voice portal unit 350 may store subscriber profiles to determine a subscriber's device preference (e.g., a cellular telephone, a personal digital assistant (PDA), a paging device, and the like) and may also track a subscriber's access to the services provided for billing purposes.
  • The [0052] web center 360 acts as a virtual call center by queuing, routing and distributing communications from any first location to an appropriate agent at any second location. The web center 360 allows agents to handle multiple mediums (e.g., inbound telephone calls, faxes, e-mails, voicemail, voice over Internet protocol (VoIP) transactions, etc.) via a single browser-based interface. In one implementation, the web center 360 may be implemented using CallCenter@nywhere from Telephony@Work, Inc.
  • The [0053] IPCOM unit 370 may include one or more devices that provide VoIP services to subscribers. The subscribers may make and receive calls via an IP communications network using, for example, session initiation protocol (SIP) telephones. The IPCOM unit 370 may support the following services: 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. Customers may set or change attributes associated with these features via the network interface 320.
  • The vBNS+[0054] unit 380 provides the IP infrastructure for the IP communications network. The vBNS+unit 380 may include a group of edge routers for routing packets in the network. The non-integrated applications 390 may include, for example, a security unit, a trouble ticketing unit, and a fault manager. The security unit may include one or more firewalls for securing the network interface 320, telephone equipment (e.g., PBX, switch, redirect server, etc.) and network equipment. The trouble ticketing unit manages the issuance and resolution of trouble tickets and the fault manager monitors the hardware components of the OSS 130.
  • FIG. 4 illustrates an exemplary configuration of the [0055] process management system 310 of FIG. 3 in an implementation consistent with the present invention. As illustrated, the process management system 310 includes a bus 410, a processor 420, a memory 430, an input device 440, an output device 450, and a communication interface 460. The bus 410 permits communication among the components of the process management system 310.
  • The [0056] processor 420 may include any type of conventional processor or microprocessor that interprets and executes instructions. The memory 430 may include a RAM or another type of dynamic storage device that stores information and instructions for execution by the processor 420; a ROM or another type of static storage device that stores static information and instructions for use by the processor 420; and/or some type of magnetic or optical recording medium and its corresponding drive.
  • The [0057] input device 440 may include any conventional mechanism that permits an operator to input information to the process management system 310, such as a keyboard, a mouse, a pen, voice recognition and/or biometric mechanisms, and the like. The output device 450 may include any conventional mechanism that outputs information to the operator, including a display, a printer, a speaker, etc. The communication interface 460 may include any transceiver-like mechanism that enables the process management system 310 to communicate with other devices and/or systems, such as the network interface 320, integrated applications 330, traditional telephony systems 340, etc. via a wired, wireless, or optical connection.
  • As discussed previously, [0058] process management system 310 may run a CORBA-based program to integrate various components of the OSS 130. As such, execution of the sequences of instructions associated with the program contained in a computer-readable medium, such as memory 430, causes processor 420 to implement the functional operations described below. In alternative embodiments, hardwired circuitry may be used in place of or in combination with software instructions to implement the present invention. Thus, the present invention is not limited to any specific combination of hardware circuitry and software.
  • FIG. 5 illustrates an exemplary functional block diagram of the [0059] process management system 310 of FIG. 3 in an implementation consistent with the present invention. As illustrated, the process management system 310 includes a process automator 510, an analyzer 520, a group of connectors 530, a communicator 540 and a central engine 550. In an exemplary implementation of the present invention, these elements are implemented as functional modules of a software program executed by processor 420 of the process management system 310. It will be appreciated that the process management system 310 may execute additional functional modules (not shown) that aid in the reception, processing, and/or transmission of data.
  • The [0060] processor automator 510 includes a modeling tool that allows event processing to be visually modeled by engineers and product development analysts. The process automator 510 can then execute these models to create an automated business process executed by the central engine 550. The analyzer 520 provides on-going and real-time monitoring of the components of the OSS 130. The analyzer 520 delivers reports, history, and trending on events processed through the central engine 550. The connectors 530 allow the components of the OSS 130 to interact and communicate with the process management system 310. The OSS components may communicate with the process management system 310 via standard messaging or through full publish/subscribe processing. The communicator 540 enables the process management system 310 to communicate with various components of the 05 S 130 using transmission control protocol/Internet protocol (TCP/IP). The central engine 550 is the core of the software program and executes customized rules to enable the process management system 310 to integrate the various systems of the OSS 130, as described in more detail below. It should be understood that the central engine 550 may be programmed to perform any rules-based processing based on the particular requirements associated with managing the OSS 130.
  • FIG. 6 illustrates an exemplary configuration of the [0061] voice portal unit 350 of FIG. 3 in an implementation consistent with the present invention. As illustrated, the voice portal unit 350 includes an extensible Program Management (XPM) unit 610, one or more voice portal application servers 620, and a customer directory database 630. The XPM unit 610 receives user profile information from the network interface 320 via the process management system 310 and stores this information for use by the voice portal application servers 620. The XPM unit 610 may also receive other information, such as information identifying the device(s) (e.g., PDA, cellular telephone, pager, computer, etc.) by which a user wishes to receive the information associated with a particular service(s) to which the user has subscribed.
  • The voice [0062] portal application servers 620 may include one or more servers that interact with the XPM unit 610 to provide, for example, banking, brokerage, and financial services, travel, entertainment, sports and weather services, distribution and shipping services, insurance services, health and pharmaceutical services, manufacturing services, and the like. Voice portal application servers 620 may also provide data collection unit 336 with information regarding what services are accessed and by whom. The data collection unit 336 may then pass this information to billing unit 337 for billing purposes. The voice portal application servers 620 may be located at the OSS 130 or distributed throughout the network 110. The customer directories 630 may store information relating to the services provided by the voice portal application servers 620. For example, the customer directories 630 may store stock quotes, current weather forecasts, real-time sports scores, etc.
  • FIG. 7 illustrates an exemplary configuration of the [0063] web center 360 of FIG. 3 in an implementation consistent with the present invention. As illustrated, the web center 360 includes a communications server 710 and an agent information database 720. The communication server 710 queues, routes, and distributes communications from any first location to an appropriate agent at any second location. The communications server 710 may determine the appropriate agent based on data stored in the agent information database 720. The agent information database 720 may store agent activity information, the particular skills of the agents, and the like. Once a customer has utilized the services of the web center 360, the usage information may be transmitted to the data collection unit 336 and then to the billing unit 337 for billing. Users may, via the network interface 320, provision new services, such as order a toll free number.
  • FIG. 8 illustrates an exemplary configuration of the [0064] IPCOM unit 370 of FIG. 3 in an implementation consistent with the present invention. As illustrated, the IPCOM unit 370 includes a redirect server 810, a redirect server database 812, network server 820, customer provided equipment (CPE) enterprise gateways/routers 830 and network gateways 840. According to an exemplary implementation, the redirect server 810 executes an object request broker (ORB) that is CORBA compliant. The redirect server 810 stores data in database 812 relating to call processing (e.g., information identifying the device by which the subscriber wishes to receive the call, network configuration information, etc.), subscriber profiles (e.g., a subscriber identifier) and network-supported features. The redirect server 810 may decide how to route calls based on information stored in redirect server database 812. The redirect server 810 and the redirect server database 812 are shown as separate devices. It should be understood that these devices may both be part of the same server in implementations consistent with the present invention.
  • The [0065] redirect server 810 forwards the routing information to the network server 820. The network server 820, also referred to as the proxy server or SIP server, processes the actual calls made over the IP communications network. The network server 820 directs the calls to CPE enterprise gateways/routers 830 or network gateways 840 based on the type of call and the network-supported features to which a customer subscribes. The network-supported features may include, for example, 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. As described above, a subscriber may change attributes of these network-supported features using the network interface 320. The redirect server 810 may also communicate with the data collection unit 336.
  • The CPE enterprise gateways/[0066] routers 830 may include one or more gateways for linking POTS telephone systems to the IP communications network. The CPE enterprise gateways/routers 830 may, for example, connect to a customer's private branch exchange (PBX) and convert TDM voice data into VoIP packets and voice signaling into SIP messages. The CPE enterprise gateways/routers 830 may also include one or more routers that receive information from a SIP phone over a network, such as a LAN or WAN.
  • The [0067] network gateways 840 may include one or more gateways for linking the IP communications network to the PSTN in a well known manner. The CPE enterprise gateways/routers 830 and network gateways 840 track customer access and transmit this customer access data to the data collection unit 336 for billing purposes.
  • FIG. 9 illustrates an exemplary configuration of the vBNS+[0068] unit 380 of FIG. 3 in an implementation consistent with the present invention. As illustrated, the vBNS+unit 380 includes a group of edge routers 910 that route packets to/from the vBNS+core network 920. The edge routers 910 may connect to the network server 820, redirect server 810, network gateways 830, customer's CPE equipment, other routers in the IP communications network, directly to SIP telephones, etc. The vBNS+core 920 may include one or more core routers for routing packets between edge routers.
  • The foregoing description of the [0069] OSS 130 provides an overview of the components and operations of the OSS 130. A more detailed description of the present invention as embodied, for example, in the process management system 310, is provided below.
  • BILLING UNIT CONNECTOR
  • As described previously, the [0070] OSS 130 may provide a number of products and services to users, such as services associated with voice portal unit 350, web center 360, IPCOM unit 370 and vBNS+unit 380. Each of these products has unique billing requirements. The data collection unit 336, consistent with implementations of the present invention, retrieves data from network elements associated with these products, normalizes the data records into a format recognized by billing unit 337 and forwards the data records to billing unit 337.
  • The [0071] billing unit 337 may include a database that stores information associated with a customer's account (e.g., the customer's calling plan information, the services subscribed to by the customer, etc.). The billing unit 337 may also store rating information to rate the data records so that the customer is billed the appropriate amount for the services it receives. At various times, the customer, account personnel and engineering personnel may require access to the billing unit 337. The present invention is directed to systems and methods for enabling the process management system 310 to communicate with the billing unit 337 to support various parties requiring access to the billing unit 337.
  • FIG. 10 is an exemplary functional block diagram illustrating one of the connectors [0072] 530 (FIG. 5) of the process management system 310 that enables the process management system 310 to communicate with the billing unit 337. Referring to FIG. 10, connector 532 may be a software module (i.e., part of the software program) executed by process management system 310. The connector 532 may be a Java-based connector that enables the process management system 310 to communicate with the billing unit 337. The connector 532 may include a channel source 1010, a transformer 1020, a client 1030 and a channel target 1040. These elements may represent functional processes implemented in software.
  • The [0073] connector 532 acts as a conversion point to drive data to and from the billing unit 337, since the billing unit 337 is not capable of performing a publish/subscribe activity on its own without the connector 532. The connector 532 manages the semantics associated with managing event queues on a channel on behalf of the billing unit 337. According to an exemplary implementation of the invention, the connector 532 communicates with the billing unit 337 to enable a user to retrieve information stored in the billing unit 337, modify or delete information stored in the billing unit 337 and create new service identification information.
  • For example, a customer or a member of an account team may wish to retrieve current charges associated with the customer's account. In this case, the user may access the [0074] process management system 310 using network interface 320. The process management system 310 receives the request and invokes connector 532 to establish communications with the billing unit 337 and retrieve the desired information. In an exemplary implementation consistent with the present invention, the connector 532 uses customized opcodes to retrieve the desired information, as described in more detail below. Using custom opcodes provides for the retrieval of data from the billing unit 337 in an efficient manner.
  • The [0075] connector 532 may also include logic that allows “event” information to be written to the billing unit 337 using a 2-phase commit procedure. The event information may include the user-entered information received via the network interface 320. By using a 2-phase commit procedure, the process management system 310 ensures that data written to the billing unit 337 is consistent with data stored in other portions of the OSS 130, as described in more detail below.
  • Referring back to FIG. 10, the [0076] channel source 1010 represents input data associated with user-entered event information. For example, when a user in an accounting department accesses the OSS 130 to perform some transaction, e.g., retrieve master account information, retrieve services associated with a particular master account, retrieve current charges associated with the master account, retrieve detailed charge information associated with the master account, etc., the process management system 310 receives the request via the network interface 320 and processes the request. In an exemplary implementation consistent with the present invention, the central engine 550 (FIG. 5) publishes an event on a channel, such as the channel corresponding to the channel source 1010. The transformer 1020 subscribes to the channel associated with the channel source 1010 and receives the event information.
  • The [0077] transformer 1020 may then identify the particular type of event received from the channel source 1010. For example, transformer 1020 determines what service/product the event is associated with and whether the event is associated with a user requesting information or a user attempting to modify or store new information associated with a particular service/product. The transformer 1020 may then determine how to format the data associated with the received event. The transformer 1020 may also invoke client 1030 to establish communications with the billing unit 337. The client 1030 may be used to transmit the re-formatted event information to the billing unit 337.
  • In accordance with an exemplary implementation of the invention, the [0078] transformer 1020 may also publish the event to various channel targets 1040 subscribed to by other modules/external systems. For example, according to an exemplary implementation of the present invention, the transformer 1030 may publish event information to a channel subscribed to by a connector associated with the ODS 332, represented by channel target 1040. It should be understood that in other implementations of the invention, the connector 532 may publish event information to channels associated with other modules/externals systems, based on the particular system requirements.
  • As described previously, the [0079] billing unit 337 may include a database that stores information associated with customer's accounts and the services to which the customer subscribes. The billing unit 337 may execute a billing unit process 1050 to facilitate the actual execution of the received event information from the connector 532, as described in more detail below.
  • The [0080] billing unit 337 may also communicate with other systems via the process management system 310 before performing the desired operation associated with the received event. For example, the billing unit 337 may prepare a transaction for writing to its database. The billing unit 337, however, may wait for a “go ahead” indication from the connector 532 before actually writing the data to its database. In this manner, the connector 532 may essentially perform a 2-phase commit process associated with a received event to ensure that the actual data written to the billing unit 337 is consistent with information in other databases of the OSS 130.
  • FIG. 11 is a flow diagram, consistent with the present invention, illustrating exemplary processing associated with [0081] connector 532. Processing may begin when a user accesses the OSS 130 (act 1110). For example, the user may wish to change his/her particular plan associated with a particular service, such as select a plan with unlimited minutes for VoIP communications. In this case, the user may access the OSS 130 with a conventional user device 120 via network 110 (FIG. 1). The user may provide a user identification and/or password and network interface 320 may determine whether the user is authorized to access/modify various information stored in the OSS 130. Assuming that the user is authorized, the OSS 130 downloads a graphical user interface (GUI) to the user's particular user device 120 (act 1120). The GUI may include a number of options associated with the user's account. These options may include selections associated with modifying the user's plan, selections associated with receiving billing information, etc.
  • In an exemplary scenario, the user wishes to change his VoIP plan. In this case, the user selects “customer configuration” or a similar graphic/text input and transmits the selection to the OSS [0082] 130 (act 1130). The OSS 130 receives the selection and downloads a customer configuration interface GUI to the user device 120 (act 1130). The GUI may also include pre-stored information associated with that user. For example, the pre-stored information may indicate the user's plan information for making/receiving VoIP calls.
  • Assuming that the user wishes to change his VoIP plan, the user selects “modify VoIP plan” or a similarly labeled input on the GUI. The user may then input the desired modification and transmit the information to the OSS [0083] 130 (act 1140).
  • The [0084] process management system 310 receives the user-entered information, also referred to as an “event,” via the network interface 320 (act 1150). The central engine 550 may then publish the event on a channel (act 1150). In the example described above where the event is associated with updating the user's VoIP plan, the central engine 550 publishes the event to a channel subscribed to by connector 532, represented by channel source 1010 (FIG. 10).
  • The [0085] connector 532 receives the event information (act 1160). In an exemplary implementation consistent with the present invention, the transformer 1020 extracts the event contents, identifies the event type based on the received information and converts the event information into an appropriate format based on the event type (act 1160). For example, the transformer 1020 may format the event information for the billing unit 337. The transformer 1020 may also publish the event information to other systems/units, represented by channel target 1040 (act 1160).
  • In the exemplary scenario in which the event is associated with modifying the user's VoIP plan, the [0086] transformer 1020 may publish the event to a channel target associated with the ODS 332. The ODS 332 essentially acts as the database of record for the OSS 130. It should be understood that transformer 1020 may also publish the event information to other channels, represented by channel target 1040. These channel targets may be associated with other external systems/connectors that may be involved in storing or processing information associated with the user's profile, such as the user's VoIP plan.
  • After the transformer publishes the event information to [0087] channel target 1040, a connector associated with the ODS 332 receives the event information, extracts the event contents, converts the event information into an appropriate format for the ODS 332 and downloads the event information to the ODS (act 1170). For example, as described previously, ODS 332 may be an RDBMS. In this case, one of connectors 530 that is designed to communicate with an RDBMS may be utilized to establish communications with ODS 332.
  • The [0088] ODS 332 receives the event information and stores the event information. If the ODS 332 is unable to store the information or does not receive the information, the connector 532 may queue the event information. Assuming that the ODS 332 write operation is successful, the ODS 332 sends a signal back to the process management system 310 indicating that the event data has been stored (act 1170).
  • After the [0089] process management system 310 receives the acknowledgement from the ODS 332, the transformer 1020 invokes the client 1030 to establish communications with the billing unit 337 (act 1180). The client 1030 establishes the semantics associated with communicating with the billing unit 337. In an exemplary implementation consistent with the present invention, the client 1030 may communicate with the billing unit 337 via method calls using Java remote method invocation over Internet inter-ORB protocol (RMI over IIOP). In alternative implementations, the client 1030 may communicate with the billing unit 337 using other techniques. In the event that the client 1030 is unable to establish communications with the billing unit 337, the connector 532 may queue the event, as described in more detail below with respect to FIG. 12.
  • Assume that the [0090] client 1030 is able to establish communications with the billing unit 337. In this case, the billing unit 337 receives the event information from client 1030 and initiates a billing unit process 1050 to update the user's plan information (act 1180). The billing unit process 1050 then stores the user-entered event information in the billing unit's 337 database (act 1180).
  • This procedure enables the [0091] billing unit 337 to ensure that the event information will be implemented in all the proper systems/databases before the billing unit 337 commits the operation to its database, thereby maintaining consistency across the various systems in the OSS 130.
  • In some implementations of the present invention, after the [0092] billing unit 337 updates its database, the billing unit 337 may signal the ODS 332, via process management system 310, to write additional data to the ODS 332. For example, when the original event received at act 1150 is associated with order management, such as ordering a new service, the ODS 332 may store the order-related event information. The billing unit 337 may then store the information in its database. As part of the storing process, the billing unit 337 may create a new service identifier associated with the new service. In this case, the billing unit 337 passes the service identifier back to the ODS 332, via the process management system 310. The ODS 332 receives the service identifier and completes the order record by storing the service identifier assigned to the service by the billing unit 337.
  • The description above with respect to FIG. 11 illustrates a process in which the [0093] ODS 332 stores the event information followed by the billing unit 337 storing the event information. In alternative implementations, the central engine 550 may publish the event to the channel target associated with ODS 332 at the same time that the event is published to the channel subscribed to by the connector 532. In this case, connector 532 may write the data to the billing unit 337 at the same time the data is being written to the ODS 332. If the ODS 332 returns an error, i.e., the data was not successfully written to the ODS 332, the connector 532 may signal the billing unit 337 to “roll back” the transaction. For example, the error may be data related (e.g., the user entered information regarding a request to modify calling plan information that is outside an accepted range) or equipment related (e.g., the ODS 332 is offline). In either case, the connector 532 signals the billing unit process 1050 to return the billing unit's 337 database to the state it was in prior to receiving the event information. This ensures that the billing unit's 337 database and the ODS 332 remain consistent.
  • Implementations consistent with the present invention also provide a mechanism for establishing a connection between the [0094] connector 532 and the billing unit 337 after an initial attempt is unsuccessful. FIG. 12 is a flow diagram, consistent with the present invention, illustrating exemplary processing associated with establishing communications with billing unit 337. Assume that the client 1030 cannot establish a connection with the billing unit 337 at act 1180 (act 1210). For example, assume that the billing unit 337 is offline, busy with another event, or generally unavailable. In this case, client 1030 queues the event (act 1220).
  • The [0095] client 1030 may also start a thread to check when the connection to the billing unit 337 can be made, i.e., determine when the billing unit 337 is available (act 1230). For example, the client 1030 may open a new thread that periodically “pings” the billing unit 337 to determine whether the billing unit 337 is available (act 1240). If the billing unit 337 is not available, the client 1030 may re-check the billing unit 337 every predetermined period of time. The predetermined period may be configurable. In addition, the client 1030 may repeat this process until a positive response is received or may ping the billing unit 337 a configurable number of times.
  • When the [0096] billing unit 337 is available, the client 1030 establishes the communication link to the billing unit 337 and downloads the queued event information to the billing unit 337 (act 1250). The billing unit 337 may then store the event information in its database (act 1250).
  • If the [0097] billing unit 337 is still unavailable after a predetermined period of time or after a predetermined number of attempts, the client 1030 may provide an alarm message indicating that the billing unit 337 is unavailable (act 1260). This alarm may be sent to a device, such as fault management unit 335. In implementations consistent with the present invention, the connector 532 may also provide information as to why the connection with the billing unit 337 cannot be established. For example, the connector 532 may indicate that the billing unit 337 is offline. The connector 532 may then send an error message to the user.
  • The [0098] connector 532, in implementations consistent with the present invention, may also signal the ODS 332, via process management system 310 to roll back the previous write operation (act 1270). In this manner, data across the OSS 130 remains consistent.
  • As described previously, customers, account personnel and engineering personnel may wish to access the [0099] billing unit 337 to retrieve information. For example, a party may wish to retrieve master account information, retrieve all services performed for a particular master account, retrieve all current charges for a master account, retrieve detailed charges for a master account, or retrieve any other information associated with the customer's account. In these situations, the user may make the request for information via network interface 320 in a manner similar to that described with respect to acts 1110 to 1150. The connector 532, however, recognizes that the event is a request for information and does not publish the event to any other channel targets. The transformer 1020 (FIG. 10) opens client 1030, which establishes communications with billing unit 337. The billing unit process 1050 retrieves the desired information and the process management system 310 provides the requested information to the user.
  • In summary, an authorized user may request any type of information regarding a customer's account via [0100] network interface 320. The process management system 310 publishes these type of events to a channel subscribed to by connector 532. Connector 532 identifies the type of request, formats the request for billing unit 337 and retrieves the desired information. The process management system 310 then returns the requested data to the authorized user.
  • To facilitate retrieval of information from the [0101] billing unit 337, the process management system 310 may use custom opcodes, as described previously. The custom opcodes may be implemented in Java using RMI over IIOP. The particular custom opcodes may be designed based on the service provider's business requirements so that the same opcodes can be used for any of the products/services in the OSS 130. For example, the same opcode may be used to retrieve account information associated with services provided by voice portal unit 350, web center 360, IPCOM unit 370 and vBNS+unit 380. In this manner, the programming associated with the customized opcodes may be minimized to take advantage of commonality associated with the various products/services of the OSS 130. For example, when a particular request is made, the connector 532 uses the appropriate custom opcode identifying the request. The billing unit 337 recognizes the opcode and returns the requested information on the customer's account.
  • Systems and methods consistent with the present invention provide a flexible connection between a support system and a [0102] billing unit 337 to allow a user to modify information regarding the services subscribed to by the user, request new services and request information from the billing unit 337. An advantage of the invention is that the connector may be easily customized to support new products/services. Another advantage of the invention is that the connector is fault tolerant. For example, when the billing unit 337 is unavailable, the connector 532 includes provisions for retrying the connection. This results in a more flexible and reliable system.
  • A further advantage of the present invention is the system can be easily modified to support various vendors' equipment. For example, the [0103] connector 532 described above essentially uses a two-tiered approach to connect with the billing unit 337. The first tier deals with the semantics of the physical connection and protocol between the connector 532 and the target billing unit 337. The second tier described above in relation to the transformer process deals with transaction completion and fault tolerance. If the particular vendor associated with the billing unit 337 changes, only the first tier of the connector needs to be modified to support this vendor. Therefore, the connector 532 facilitates the integration of new systems, thereby reducing development time and costs.
  • In this disclosure, there is shown and described only the preferred embodiments of the invention, but, as aforementioned, it is to be understood that the invention is capable of use in various other combinations and environments and is capable of changes or modifications within the scope of the inventive concept as expressed herein. [0104]
  • For example, the present invention has been described with a few examples with respect to requesting changes in service, requesting new services and requesting information stored in the [0105] billing unit 337. It should be understood that the present invention may be used to support any number of requests associated with account management, order management, service management and bill presentation. In addition, aspects of the present invention have been described as series of acts in relation to FIGS. 11 and 12. It should be understood that the order of these acts may vary in other implementations of the present invention. Moreover, non-dependent acts may be performed in parallel.
  • No element, act or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. [0106]
  • The scope of the invention is defined by the claims and their equivalents. [0107]

Claims (27)

What is claimed is:
1. A method for conununicating from a first system to a billing system, 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 first connector associated with the billing system;
receiving, by the first connector, the event information;
transforming the event information to a format compatible with the billing system;
publishing the event information to a channel subscribed to by a second connector associated with a database system;
sending, by the database system, an indication that the database system received the event information;
receiving the indication by the first connector;
establishing, by the first connector, communications with the billing system; and
downloading the transformed event information to the billing system.
2. The method of claim 1, fuirther comprising:
writing the transformed event information to a database associated with the billing system.
3. The method of claim 2, further comprising:
sending order-related information, after writing the transformed event information, from the billing system to the first connector; and
forwarding the order-related information to the database system.
4. The method of claim 3, wherein the order-related information comprises a service identifier, the method further comprising:
storing the service identifier in the database system.
5. The method of claim 1, further comprising:
signaling the billing system to not download the transformed event information if the indication is not received by the first connector.
6. The method of claim 1, fturther comprising:
queuing the transformed event information if the first connector is unable to establish communications with the billing system; and
periodically attempting to establish communications with the billing system.
7. The method of claim 6, further comprising:
generating an alarm if communications with the billing system are not established after a predetermined period of time or after a predetermined number of attempts.
8. The method of claim 1, wherein the user-entered information comprises information associated with at least one of account management, order management, service management and bill presentation and the establishing communications with the billing system includes:
establishing communications using remote method invocation over Internet interORB protocol.
9. 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 billing system;
receive the data associated with at least one of adding, deleting and modifying information stored in the billing system;
format the data based on a type associated with the received data;
forward the data to an operational data storage system;
receive an indication that the operational data storage system received the data;
establish, in response to receiving the indication, communications with the billing system; and
download the formatted data to the billing system.
10. The computer-readable medium of claim 9, including further instructions for causing the processor to:
receive order-related information from the billing system; and
forward the order-related information to the operational data storage system.
11. The computer-readable medium of claim 10, wherein the order-related information comprises a service identifier.
12. The computer-readable medium of claim 9, including further instructions for causing the processor to:
queue the formatted data if the indication is not received.
13. The computer-readable medium of claim 9, including fu~rther instructions for causing the processor to:
queue the formatted data if communications with the billing system are not established; and
periodically attempt to establish communications with the billing system.
14. The computer-readable medium of claim 13, including further instructions for causing the processor to:
generate an alarm if communications with the billing system are not established after a predetermined number of attempts or after a predetermined period of time.
15. The computer-readable medium of claim 9, wherein the data associated with at least one of adding, deleting and modifying information stored in the billing system comprises information associated with at least one of account management, order management, service management and bill presentation and when establishing communications with the billing system, the instructions cause the processor to:
establish communications using remote method invocation over Internet interORB protocol.
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,
output event information associated with the input data to a channel subscribed to by a first connector associated with a billing system,
transform the data into an appropriate format for the billing system based on a type associated with the input data,
forward the data to an operational data storage system,
receive an indication that the operational data storage system received the data,
establish communications with the billing system, in response to receiving the indication, and
download the transformed data to the billing system.
17. The support system of claim 16, wherein the processor is further configured to:
receive order-related information from the billing system, and
forward the order-related information to the operational data storage system.
18. The support system of claim 17, wherein the order-related information comprises a service identifier associated with a service to which a user wishes to subscribe.
19. The support system of claim 16, wherein the processor is further configured to:
queue the event if communications with the billing system cannot be established, and
periodically attempt to establish communications with the billing system.
20. The support system of claim 19, wherein the processor is further configured to:
generate an alarm if communications with the billing system are not established after a predetermined period of time or after a predetermined number of attempts.
21. The support system of claim 16, wherein the user-entered information comprises information associated with at least one of account management, order management, service management and bill presentation and when establishing communications with the billing system, the processor is configured to:
establish communications using remote method invocation over Internet interORB protocol.
22. A software-based connector for communicating between an integration platform and a billing system using remote method invocation over Internet inter-ORB protocol (RMI over IIOP), the connector comprising:
a transformer module configured to:
receive input information associated with a request for information from the billing system,
identify an opcode corresponding to the request, and
format the request to include the identified opcode; and
a client module configured to:
establish communications with the billing system,
transmit the formatted request to the billing system, and
receive information from the billing system in response to the request.
23. The software-based connector of claim 22, wherein the transformer module is further configured to:
receive event information associated with at least one of a request to change a plan associated with a service or a request for a new service,
transform the event information into an appropriate format, and
output information associated with the received event 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 an operational data storage system and the client module is further configured to:
receive a message from the operational data storage system when the operational data storage system has received the information,
establish communications with the billing system in response to receiving the message, and
download the transformed event information to the billing system.
25. The software-based connector of claim 24, wherein the client module is further configured to:
queue the transformed event information if communications with the billing system cannot be established, and
periodically attempt to establish communications with the billing system.
26. The software-based connector of claim 22, wherein the received input information comprises at least one of a request for account information associated with a customer, a request for charge information associated with a customer and a request for service information associated with a customer.
27. The software-based connector of claim 23, wherein the event information comprises information associated with at least one of account management, order management, service management and bill presentation.
US10/097,866 2001-03-20 2002-03-15 Systems and methods for communicating from an integration platform to a billing unit Abandoned US20020138427A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/097,866 US20020138427A1 (en) 2001-03-20 2002-03-15 Systems and methods for communicating from an integration platform to a billing unit

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US27692301P 2001-03-20 2001-03-20
US27695501P 2001-03-20 2001-03-20
US27695401P 2001-03-20 2001-03-20
US27695301P 2001-03-20 2001-03-20
US10/097,866 US20020138427A1 (en) 2001-03-20 2002-03-15 Systems and methods for communicating from an integration platform to a billing unit

Publications (1)

Publication Number Publication Date
US20020138427A1 true US20020138427A1 (en) 2002-09-26

Family

ID=27501179

Family Applications (10)

Application Number Title Priority Date Filing Date
US10/097,866 Abandoned US20020138427A1 (en) 2001-03-20 2002-03-15 Systems and methods for communicating from an integration platform to a billing unit
US10/099,097 Active 2026-07-15 US7599351B2 (en) 2001-03-20 2002-03-15 Recursive query for communications network data
US10/097,971 Active 2025-02-14 US7289522B2 (en) 2001-03-20 2002-03-15 Shared dedicated access line (DAL) gateway routing discrimination
US10/097,869 Expired - Fee Related US8200577B2 (en) 2001-03-20 2002-03-15 Systems and methods for retrieving and modifying data records for rating and billing purposes
US10/101,199 Active 2029-08-16 US8761745B2 (en) 2001-03-20 2002-03-18 Call forwarding on screening
US10/103,279 Expired - Fee Related US7197560B2 (en) 2001-03-20 2002-03-20 Communications system with fraud monitoring
US10/667,278 Expired - Fee Related US7809860B2 (en) 2001-03-20 2003-09-22 System, method and apparatus that isolate virtual private network (VPN) and best effort traffic to resist denial of service attacks
US12/510,948 Expired - Lifetime US9124722B2 (en) 2001-03-20 2009-07-28 Recursive query for communications network data
US12/725,193 Expired - Lifetime US8543734B2 (en) 2001-03-20 2010-03-16 System, method and apparatus that isolate virtual private network (VPN) and best effort traffic to resist denial of service attacks
US13/490,734 Expired - Fee Related US8700528B2 (en) 2001-03-20 2012-06-07 Systems and methods for retrieving and modifying data records for rating and billing purposes

Family Applications After (9)

Application Number Title Priority Date Filing Date
US10/099,097 Active 2026-07-15 US7599351B2 (en) 2001-03-20 2002-03-15 Recursive query for communications network data
US10/097,971 Active 2025-02-14 US7289522B2 (en) 2001-03-20 2002-03-15 Shared dedicated access line (DAL) gateway routing discrimination
US10/097,869 Expired - Fee Related US8200577B2 (en) 2001-03-20 2002-03-15 Systems and methods for retrieving and modifying data records for rating and billing purposes
US10/101,199 Active 2029-08-16 US8761745B2 (en) 2001-03-20 2002-03-18 Call forwarding on screening
US10/103,279 Expired - Fee Related US7197560B2 (en) 2001-03-20 2002-03-20 Communications system with fraud monitoring
US10/667,278 Expired - Fee Related US7809860B2 (en) 2001-03-20 2003-09-22 System, method and apparatus that isolate virtual private network (VPN) and best effort traffic to resist denial of service attacks
US12/510,948 Expired - Lifetime US9124722B2 (en) 2001-03-20 2009-07-28 Recursive query for communications network data
US12/725,193 Expired - Lifetime US8543734B2 (en) 2001-03-20 2010-03-16 System, method and apparatus that isolate virtual private network (VPN) and best effort traffic to resist denial of service attacks
US13/490,734 Expired - Fee Related US8700528B2 (en) 2001-03-20 2012-06-07 Systems and methods for retrieving and modifying data records for rating and billing purposes

Country Status (8)

Country Link
US (10) US20020138427A1 (en)
EP (3) EP1374509A4 (en)
JP (3) JP2005518681A (en)
CN (1) CN1509412A (en)
BR (4) BR0208231A (en)
CA (2) CA2441344A1 (en)
MX (3) MXPA03008511A (en)
WO (1) WO2002075339A1 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030140029A1 (en) * 2002-01-18 2003-07-24 Adam Messinger System and method for performing commutative operations in data access systems
WO2003069434A2 (en) * 2002-02-11 2003-08-21 At & T Wireless Services, Inc. Centralized communications network charging methods and apparatus
US20030191773A1 (en) * 2002-04-09 2003-10-09 Vigilos, Inc. System and method for providing a fault-tolerant data warehouse environment
EP1427134A2 (en) * 2002-12-05 2004-06-09 BTS Holdings PLC System and method for management of communications resources
US20050261920A1 (en) * 2004-05-20 2005-11-24 Hewlett-Packard Development Company, L.P. Establishing services
EP1804420A1 (en) * 2005-12-29 2007-07-04 Société Française du Radiotéléphone-SFR Method and device for improving the operation of a billing chain by implementing a multi-level backup method
US20070201429A1 (en) * 2003-09-08 2007-08-30 Raffaela Brodt Method For Billing A Service In A Packet Data Network
US20090313059A1 (en) * 2008-06-12 2009-12-17 Verizon Business Network Services Inc. System and method for integrating issue tracking systems
US20180203754A1 (en) * 2017-01-17 2018-07-19 Bank Of America Corporation Individualized Channel Error Detection and Resolution
US11729588B1 (en) 2021-09-30 2023-08-15 T-Mobile Usa, Inc. Stateless charging and message handling

Families Citing this family (419)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7072303B2 (en) * 2000-12-11 2006-07-04 Acme Packet, Inc. System and method for assisting in controlling real-time transport protocol flow through multiple networks
US7028092B2 (en) * 2000-12-11 2006-04-11 Acme Packet, Inc. System and method for assisting in controlling real-time transport protocol flow through multiple networks via media flow routing
US7133923B2 (en) 2000-12-11 2006-11-07 Acme Packet, Inc. System and method for assisting in controlling real-time transport protocol flow through multiple networks via screening
US7002973B2 (en) * 2000-12-11 2006-02-21 Acme Packet Inc. System and method for assisting in controlling real-time transport protocol flow through multiple networks via use of a cluster of session routers
US7945592B2 (en) 2001-03-20 2011-05-17 Verizon Business Global Llc XML based transaction detail records
US20030115480A1 (en) * 2001-12-17 2003-06-19 Worldcom, Inc. System, method and apparatus that employ virtual private networks to resist IP QoS denial of service attacks
US20020138427A1 (en) * 2001-03-20 2002-09-26 Trivedi Prakash A. Systems and methods for communicating from an integration platform to a billing unit
US20020138296A1 (en) * 2001-03-20 2002-09-26 Holmes Ralph K. Systems and methods for collecting and rating contact center usage
US7406306B2 (en) * 2001-03-20 2008-07-29 Verizon Business Global Llc Method for billing in a telecommunications network
US8380840B2 (en) 2001-12-17 2013-02-19 Verizon Business Global Llc Method for recording events in an IP network
US7215643B2 (en) * 2003-07-29 2007-05-08 Level 3 Communications, Llc System and method for providing alternate routing in a network
US7339934B2 (en) * 2001-04-06 2008-03-04 Level 3 Communications, Llc Alternate routing of voice communication in a packet-based network
US7362707B2 (en) * 2001-07-23 2008-04-22 Acme Packet, Inc. System and method for determining flow quality statistics for real-time transport protocol data flows
US7031311B2 (en) * 2001-07-23 2006-04-18 Acme Packet, Inc. System and method for providing rapid rerouting of real-time multi-media flows
US8098651B1 (en) 2001-07-27 2012-01-17 Rockstar Bidco, LP Integrating multimedia capabilities with circuit-switched calls
US6888828B1 (en) * 2001-10-02 2005-05-03 Nokia Corporation System and method for providing at least one service obtained from a service network for a user in a packet switched communication network
US7882029B2 (en) * 2001-10-16 2011-02-01 Hewlett-Packard Development Company, L.P. Centralized billing credit system utilizing a predetermined unit of usage
US7206393B2 (en) * 2001-11-01 2007-04-17 Agilent Technologies, Inc. Apparatus and method for processing information from a telephone network
US20040162066A1 (en) * 2001-11-02 2004-08-19 Ravi Kuchibhotla Isolation and remediation of a communication device
US7460533B1 (en) * 2001-11-15 2008-12-02 3Com Corporation System and method for multi-casting announcements
US7937439B2 (en) 2001-12-27 2011-05-03 Utbk, Inc. Apparatus and method for scheduling live advice communication with a selected service provider
IL164067A0 (en) * 2002-03-27 2005-12-18 Ibm Methods, apparatus and products for wireless access points
US20030215080A1 (en) * 2002-05-17 2003-11-20 Wengrovitz Michael S. Presence-aware private branch exchange (PBX)
US9565275B2 (en) 2012-02-09 2017-02-07 Rockwell Automation Technologies, Inc. Transformation of industrial data into useful cloud information
FR2841072A1 (en) * 2002-06-14 2003-12-19 France Telecom System for consulting and updating DNS servers and LDAP directories, includes using protocol management unit for searching IP address of server hosting first database and transmitting request for reading and updating record to server
US20040028080A1 (en) * 2002-08-06 2004-02-12 Harish Samarasinghe Method of defining a SIP message body for communications between core network elements
US8509736B2 (en) 2002-08-08 2013-08-13 Global Tel*Link Corp. Telecommunication call management and monitoring system with voiceprint verification
US7333798B2 (en) 2002-08-08 2008-02-19 Value Added Communications, Inc. Telecommunication call management and monitoring system
US7254643B1 (en) * 2002-08-08 2007-08-07 At&T Corp. System and method for providing multi-media services to communication devices over a communications network
US7979297B1 (en) 2002-08-19 2011-07-12 Sprint Communications Company L.P. Order tracking and reporting tool
US7315518B1 (en) * 2002-09-05 2008-01-01 Art Technology Group, Inc. Method and apparatus for the prevention of unwanted calls in a callback system
US7463620B2 (en) * 2002-09-10 2008-12-09 3Com Corporation Architecture and method for controlling features and services in packet-based networks
US7646761B2 (en) * 2002-10-01 2010-01-12 Nortel Networks Limited Integrating multimedia capabilities with legacy networks
US7920546B2 (en) * 2002-10-01 2011-04-05 Nortel Networks Limited Automated attendant multimedia session
US7486944B2 (en) 2002-10-02 2009-02-03 The Bill Police Llc Method for managing wireless telecommunications bills
JP3948389B2 (en) 2002-10-24 2007-07-25 富士ゼロックス株式会社 Communication analyzer
JP3917067B2 (en) * 2002-12-06 2007-05-23 株式会社エヌ・ティ・ティ・ドコモ Web providing system, web providing method, terminal used for these, and terminal control program
US7180912B1 (en) 2003-01-06 2007-02-20 At&T Corp. System and method for providing a plurality of multi-media services using a number of media servers to form a preliminary interactive communication relationship with a calling communication device
US7768996B1 (en) * 2003-01-09 2010-08-03 Cisco Technology, Inc. Route re-query scheme in communication networks
US7283515B2 (en) * 2003-02-14 2007-10-16 Managed Inventions, Llc Internet telephony network and methods for using the same
US7319692B2 (en) * 2003-02-21 2008-01-15 Avaya Technology Corp. Subscriber mobility in telephony systems
US20050282559A1 (en) * 2003-02-25 2005-12-22 Boston Communications Group, Inc. Method and system for providing supervisory control over wireless phone data usage
MXPA05008994A (en) * 2003-02-25 2006-02-10 Boston Communications Group Inc Method and system for providing supervisory control over wireless phone usage.
US7508923B1 (en) * 2003-02-27 2009-03-24 At&T Corp. Call control element constructing a session initiation protocol (SIP) message including provisions for incorporating address related information of public switched telephone network (PSTN) based devices
US7411917B1 (en) * 2003-03-26 2008-08-12 Network Equipment Technologies, Inc. Method and system for providing registration-based SIP NAT traversal
US7283516B1 (en) * 2003-04-07 2007-10-16 At&T Corp. Session initiation protocol (SIP) messages incorporating address and/or routing information obtained from a contact header of a redirect message
US7480723B2 (en) * 2003-04-08 2009-01-20 3Com Corporation Method and system for providing directory based services
US20040230695A1 (en) * 2003-05-15 2004-11-18 Anschutz Thomas Arnold Methods, systems, and computer program products for processing traffic in a communication network based on registration of an access session and/or application flow and specifying a treatment for the access session and/or application flow traffic
US7783019B2 (en) * 2003-05-15 2010-08-24 Verizon Business Global Llc Method and apparatus for providing fraud detection using geographically differentiated connection duration thresholds
US7817791B2 (en) * 2003-05-15 2010-10-19 Verizon Business Global Llc Method and apparatus for providing fraud detection using hot or cold originating attributes
US7774842B2 (en) * 2003-05-15 2010-08-10 Verizon Business Global Llc Method and system for prioritizing cases for fraud detection
US7971237B2 (en) * 2003-05-15 2011-06-28 Verizon Business Global Llc Method and system for providing fraud detection for remote access services
US7808974B2 (en) * 2003-06-19 2010-10-05 At&T Intellectual Property I, L.P. Method and apparatus for Voice over Internet Protocol telephony using a virtual private network
US8139585B1 (en) * 2003-07-10 2012-03-20 Sprint Spectrum L.P. Method and system for controlling sessions from a subscriber terminal
US7412044B2 (en) * 2003-07-14 2008-08-12 Avaya Technology Corp. Instant messaging to and from PBX stations
US6845235B1 (en) * 2003-07-18 2005-01-18 Motorola, Inc. Method and apparatus in a wireless communication system for expediting a request for uplink resources
DE10335149A1 (en) * 2003-07-31 2005-03-03 Siemens Ag Method for reversing a Bearer Redirect for SIP / SIP-T subscribers
US7886009B2 (en) * 2003-08-22 2011-02-08 Utbk, Inc. Gate keeper
DE10344938A1 (en) * 2003-09-27 2005-04-21 Clariant Gmbh Surfactant compounds containing fatty alcohol alkoxylates
US20050071494A1 (en) * 2003-09-30 2005-03-31 Rundquist William A. Method and apparatus for providing fixed bandwidth communications over a local area network
US6977933B2 (en) * 2003-10-06 2005-12-20 Tekelec Methods and systems for providing session initiation protocol (SIP) trunk groups
US7280533B2 (en) * 2003-10-15 2007-10-09 Nokia Corporation System and method for presence-based routing of communication requests over a network
US7096043B1 (en) * 2003-10-24 2006-08-22 Nortel Networks Limited Call origination control
KR100600414B1 (en) * 2003-10-28 2006-07-13 (주)씨앤에스 테크놀로지 Method for offering service of multimedia post-office box
US7245609B2 (en) * 2003-10-31 2007-07-17 Agilent Technologies, Inc. Apparatus and method for voice over IP traffic separation and factor determination
US20050155036A1 (en) * 2003-12-19 2005-07-14 Nokia Corporation Application server addressing
US7680259B2 (en) * 2004-01-12 2010-03-16 At&T Intellectual Property, I,L.P. Rule-based intelligent call forwarding
US7734294B2 (en) * 2004-01-12 2010-06-08 At&T Intellectual Property, I,L.P. Intelligent interactive call handling
KR100602638B1 (en) * 2004-01-20 2006-07-19 삼성전자주식회사 The method for VoIP-UMS system access
US8015119B2 (en) 2004-01-21 2011-09-06 Google Inc. Methods and systems for the display and navigation of a social network
US7362698B2 (en) * 2004-01-22 2008-04-22 International Business Machines Corporation Method, system and service for achieving synchronous communication responsive to dynamic status
TW200539641A (en) * 2004-02-19 2005-12-01 Matsushita Electric Ind Co Ltd Connected communication terminal, connecting communication terminal, session management server and trigger server
CN1678005B (en) 2004-03-31 2010-10-13 国际商业机器公司 Apparatus, system and method for sharing a single physical address by multiple virtual telephones
US7408925B1 (en) 2004-03-31 2008-08-05 Avaya Technology Corp. Originator based directing and origination call processing features for external devices
US8908699B2 (en) * 2004-04-16 2014-12-09 Broadcom Corporation Providing automatic format conversion via an access gateway in a home
US8929524B2 (en) 2004-04-27 2015-01-06 Value-Added Communications, Inc. System and method for determining and associating tariff rates for institutional calls
US9014355B2 (en) 2004-04-27 2015-04-21 Value-Added Communications, Inc. Telecommunication revenue management system
US8200839B1 (en) * 2004-04-30 2012-06-12 Rockstar Bidco Lp Method and apparatus for restoring service label information
US11062412B2 (en) 2004-05-19 2021-07-13 Touchpay Holdings, Llc Machines and process for managing a service account
US8019875B1 (en) 2004-06-04 2011-09-13 Google Inc. Systems and methods for indicating a user state in a social network
US7760707B1 (en) * 2004-06-07 2010-07-20 Aol Inc. Voice over internet protocol application development framework
US9462122B1 (en) 2004-06-07 2016-10-04 Aol Inc. Selective call routing and blocking
US8832132B1 (en) 2004-06-22 2014-09-09 Google Inc. Personalizing search queries based on user membership in social network communities
US8621215B1 (en) 2004-06-30 2013-12-31 Google Inc. Methods and systems for creating monetary accounts for members in a social network
US8015019B1 (en) 2004-08-03 2011-09-06 Google Inc. Methods and systems for providing a document
CN1294728C (en) * 2004-08-05 2007-01-10 华为技术有限公司 Method and system for providing QoS assurance in edge router
US7983245B2 (en) * 2004-09-13 2011-07-19 Tekelec Methods and systems for converting an internet protocol (IP)-based message containing subscriber content to a public switched telephone network (PSTN)-based message including subscriber content
US7599347B2 (en) * 2004-09-16 2009-10-06 Research In Motion Limited System and method for allocating session initiation protocol (SIP) identifications (IDs) to user agents
US7497374B2 (en) * 2004-09-17 2009-03-03 Digital Envoy, Inc. Fraud risk advisor
US7543740B2 (en) * 2004-09-17 2009-06-09 Digital Envoy, Inc. Fraud analyst smart cookie
US20060064374A1 (en) * 2004-09-17 2006-03-23 David Helsper Fraud risk advisor
US20060062358A1 (en) * 2004-09-23 2006-03-23 Sbc Knowledge Ventures L.P. Method and apparatus for shared line FMFM sub-mailbox determination, dynamic out dialing and call path duplication in a telephone system
US8340261B2 (en) 2004-09-27 2012-12-25 At&T Intellectual Property Ii, L.P. Method and apparatus for ubiquitous access to dialing plans for enterprise networks
DE102004055494B4 (en) * 2004-11-17 2007-11-08 Siemens Ag Method for forwarding a call in one of the directly communicating communication network and communication component for a directly communicating communication network
US7742581B2 (en) 2004-11-24 2010-06-22 Value-Added Communications, Inc. Electronic messaging exchange
WO2007110679A2 (en) * 2004-12-13 2007-10-04 Radvision Ltd. Systems and methods for incorporating video into voice-only call centers
US7672443B2 (en) * 2004-12-17 2010-03-02 At&T Intellectual Property I, L.P. Virtual private network dialed number nature of address conversion
CN101084659B (en) * 2004-12-21 2010-10-13 三星电子株式会社 Method and system for providing private voice call service to mobile subscriber and wireless soft switch apparatus therefor
US8060405B1 (en) 2004-12-31 2011-11-15 Google Inc. Methods and systems for correlating connections between users and links between articles
US8194640B2 (en) * 2004-12-31 2012-06-05 Genband Us Llc Voice over IP (VoIP) network infrastructure components and method
US7716140B1 (en) 2004-12-31 2010-05-11 Google Inc. Methods and systems for controlling access to relationship information in a social network
US10402457B1 (en) 2004-12-31 2019-09-03 Google Llc Methods and systems for correlating connections between users and links between articles
WO2006074825A1 (en) * 2005-01-11 2006-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Facilitating early media in a communications system
US8351419B2 (en) 2005-01-19 2013-01-08 Qualcomm Iskoot, Inc. Local access to a mobile network
US8756328B2 (en) * 2005-01-19 2014-06-17 Qualcomm Connected Experiences, Inc. Caller-callee association of a plurality of networked devices with direct dial through thin client
US8856359B2 (en) * 2005-06-29 2014-10-07 Qualcomm Connected Experiences, Inc. Caller-callee association of a plurality of networked devices
US9876915B2 (en) 2005-01-28 2018-01-23 Value-Added Communications, Inc. Message exchange
US7783021B2 (en) 2005-01-28 2010-08-24 Value-Added Communications, Inc. Digital telecommunications call management and monitoring system
US9282188B2 (en) 2005-01-28 2016-03-08 Value-Added Communications, Inc. Voice message exchange
US7680060B2 (en) * 2005-03-08 2010-03-16 Cisco Technology, Inc. Transferring state information in a network
GB2424141B (en) 2005-03-08 2009-04-22 Praesidium Technologies Ltd Communication system with distributed risk management
WO2006098725A2 (en) * 2005-03-11 2006-09-21 Cluster Resources, Inc. System and method for enforcing future policies in a compute environment
US20060218282A1 (en) * 2005-03-23 2006-09-28 Nokia Corporation System and method for providing mobile assisted, fixed line video calls
US8538810B2 (en) * 2005-03-29 2013-09-17 Google Inc. Methods and systems for member-created advertisement in a member network
US8412780B2 (en) 2005-03-30 2013-04-02 Google Inc. Methods and systems for providing current email addresses and contact information for members within a social network
US7765305B2 (en) * 2005-04-07 2010-07-27 Microsoft Corporation Retry request overload protection
US7743411B2 (en) * 2005-04-14 2010-06-22 At&T Intellectual Property I, L.P. Method and apparatus for voice over internet protocol telephony using a virtual private network
US7436814B2 (en) * 2005-04-22 2008-10-14 Cisco Technology, Inc. Selecting transport addresses to route streams between endpoints
US8656458B2 (en) * 2005-08-25 2014-02-18 Guy Heffez Method and system for authenticating internet user identity
US9727867B2 (en) 2005-04-26 2017-08-08 Guy Hefetz Method for detecting misuse of identity in electronic transactions
US8640197B2 (en) * 2005-04-26 2014-01-28 Guy Heffez Methods for acquiring an internet user's consent to be located and for authenticating the identity of the user using location information
US7503489B2 (en) * 2005-04-26 2009-03-17 Bpriv, Llc Method and system for monitoring electronic purchases and cash-withdrawals
US11308477B2 (en) 2005-04-26 2022-04-19 Spriv Llc Method of reducing fraud in on-line transactions
US8590007B2 (en) * 2005-08-25 2013-11-19 Guy Heffez Method and system for authenticating internet user identity
US20090102712A1 (en) 2005-04-26 2009-04-23 Guy Heffez Method and system for monitoring electronic purchases and cash-withdrawals
US20060248588A1 (en) * 2005-04-28 2006-11-02 Netdevices, Inc. Defending Denial of Service Attacks in an Inter-networked Environment
US8018854B1 (en) * 2005-05-03 2011-09-13 Eastern Research Inc. Facility and equipment testing for packet networks
US20070291734A1 (en) * 2005-05-27 2007-12-20 Medhavi Bhatia Methods and Apparatus for Multistage Routing of Packets Using Call Templates
US7657624B2 (en) * 2005-06-22 2010-02-02 Hewlett-Packard Development Company, L.P. Network usage management system and method
US7610287B1 (en) 2005-06-28 2009-10-27 Google Inc. System and method for impromptu shared communication spaces
CN100525476C (en) * 2005-06-29 2009-08-05 华为技术有限公司 Content transmitting method in media gate control protocol calling
US7502320B2 (en) * 2005-07-06 2009-03-10 Cisco Technology, Inc. Method and apparatus for network-based admission control using path-coupled quality of service signaling
US20070008954A1 (en) * 2005-07-11 2007-01-11 Chao-Hung Wu Method for transmitting audiovisual data using a mobile conversion device
US8234498B2 (en) 2005-07-25 2012-07-31 Britti Michael A Screening using a personal identification code
US8418254B2 (en) 2005-07-25 2013-04-09 Transunion Rental Screening Solutions, Inc. Applicant screening
US8040875B2 (en) * 2005-07-30 2011-10-18 Alcatel Lucent Network support for caller ID verification
US12086803B2 (en) 2005-08-25 2024-09-10 Spriv Llc Method for authenticating internet users
US11818287B2 (en) 2017-10-19 2023-11-14 Spriv Llc Method and system for monitoring and validating electronic transactions
US20070070981A1 (en) * 2005-09-27 2007-03-29 Marian Croak Method and apparatus for dynamically establishing links between IP private branch exchanges
US8085757B2 (en) * 2005-11-07 2011-12-27 At&T Intellectual Property I, L.P. Caller-controlled routing to non-SIP/non-TEL URI destinations for an IMS-based ENUM query
US7606223B2 (en) * 2005-11-08 2009-10-20 Siemens Communications, Inc. Handling communications between stations in a digital telecommunications system
WO2007056838A1 (en) * 2005-11-21 2007-05-24 Bce Inc. Method, system and apparatus for announcing caller information over a television link
US20070118660A1 (en) * 2005-11-24 2007-05-24 Nokia Corporation Recording session contents in a network
GB2432993A (en) * 2005-12-01 2007-06-06 Marconi Comm Ltd Combating fraud in telecommunication systems
US9060047B2 (en) 2005-12-21 2015-06-16 Genband Us Llc Media stream management
US8244532B1 (en) 2005-12-23 2012-08-14 At&T Intellectual Property Ii, L.P. Systems, methods, and programs for detecting unauthorized use of text based communications services
US8649485B2 (en) * 2005-12-28 2014-02-11 Sap Ag System and method for automated connection triggered by availability status
US8077849B2 (en) * 2006-01-10 2011-12-13 Utbk, Inc. Systems and methods to block communication calls
US7881455B2 (en) * 2006-01-12 2011-02-01 At&T Intellectual Property I, L.P. Apparatus and method for finding a called party over a telecommunication network
US7529231B2 (en) * 2006-01-13 2009-05-05 At&T Intellectual Property L.L.P. Routing methods and systems using ENUM servers internal and external to a service provider network
US7697422B1 (en) 2006-01-17 2010-04-13 Marvell Israel (M.I.S.L.) Ltd. Quality of service marking techniques
US20070165605A1 (en) * 2006-01-17 2007-07-19 Samsung Electronics Co., Ltd. Apparatus and method for handling call features activated by POTS phones in an IP multimedia subsystem
US7945261B1 (en) * 2006-01-25 2011-05-17 Nextel Communications Inc. Systems and methods for provisioning and synchronizing wireless subscriber data
US9479604B2 (en) * 2006-01-30 2016-10-25 Qualcomm Incorporated System and method for dynamic phone book and network content links in a mobile device
US8144644B1 (en) 2006-02-07 2012-03-27 Sprint Spectrum L.P. Network-side setup of a packet-data communication session on behalf of a mobile station, followed by transfer of the communication session to the mobile station
CN101496387B (en) * 2006-03-06 2012-09-05 思科技术公司 System and method for access authentication in a mobile wireless network
KR101017693B1 (en) * 2006-03-06 2011-02-25 노키아 코포레이션 Aggregation of VCI routing tables
JP5105755B2 (en) * 2006-03-10 2012-12-26 サンデン株式会社 Connection device for communication equipment.
US20070234424A1 (en) * 2006-03-31 2007-10-04 Lucent Technologies, Inc. Design and evaluation of a fast and robust worm detection algorithm
JP2007282059A (en) * 2006-04-10 2007-10-25 Sony Corp Video-phone terminal device and method for displaying address
US20070237131A1 (en) * 2006-04-10 2007-10-11 Microsoft Corporation Voip client information
SE531400C2 (en) 2006-05-10 2009-03-24 Rebtel Networks Ab telephone Communication
US7890636B2 (en) * 2006-06-28 2011-02-15 Cisco Technology, Inc. Application integrated gateway
US9054909B2 (en) * 2006-06-30 2015-06-09 Microsoft Technology Licensing, Llc Forwarding calls in real time communications
US7809123B2 (en) 2006-08-02 2010-10-05 At&T Intellectual Property I, L.P. Method and system for determining independent authorization levels in a VPN
US8036366B2 (en) * 2006-08-04 2011-10-11 Microsoft Corporation Intelligent formatting of VoIP telephone numbers
US20080046440A1 (en) * 2006-08-16 2008-02-21 Estes Philip F Method And System For Enforcing User-Defined Relational Limitations In A Recursive Relational Database Table
US7881297B2 (en) * 2006-09-01 2011-02-01 Avaya Inc. Providing communications including an extended protocol header
NO325487B1 (en) * 2006-09-14 2008-05-13 Tandberg Telecom As Method and device for dynamic streaming / archiving configuration
US8160218B2 (en) * 2006-09-22 2012-04-17 Alcatel Lucent Event driven call generation
US20080080527A1 (en) * 2006-09-29 2008-04-03 Motorola, Inc. Method and apparatus for communication between session initiation protocol based networks and legacy networks
US8270588B2 (en) 2006-10-04 2012-09-18 Ronald Schwartz Method and system for incoming call management
US20080086700A1 (en) * 2006-10-06 2008-04-10 Rodriguez Robert A Systems and Methods for Isolating On-Screen Textual Data
US8571198B2 (en) 2006-10-10 2013-10-29 Cisco Technology, Inc. Handling redirect calls
US7706373B2 (en) * 2006-11-01 2010-04-27 Nuvoiz, Inc. Session initiation and maintenance while roaming
JP4410236B2 (en) * 2006-11-28 2010-02-03 株式会社東芝 Telephone system and call control method thereof
GB0624577D0 (en) * 2006-12-08 2007-01-17 Skype Ltd Communication Systems
US8451825B2 (en) 2007-02-22 2013-05-28 Utbk, Llc Systems and methods to confirm initiation of a callback
US20080201158A1 (en) 2007-02-15 2008-08-21 Johnson Mark D System and method for visitation management in a controlled-access environment
US8542802B2 (en) 2007-02-15 2013-09-24 Global Tel*Link Corporation System and method for three-way call detection
WO2008103743A1 (en) * 2007-02-20 2008-08-28 Macaluso Anthony G Automatic provisioning of abbreviated dialing codes
US8730970B2 (en) * 2007-02-23 2014-05-20 Tekelec Global, Inc. Methods systems, and computer program products for providing voicemail routing information in a network that provides customized voicemail services
US9055517B2 (en) * 2007-02-26 2015-06-09 Blackberry Limited System and method of user-directed dynamic domain selection
US7995562B2 (en) * 2007-02-26 2011-08-09 Research In Motion Limited System and method to trigger a mobile device in different domains based on unsuccessful initialization or handover
US8010093B2 (en) 2007-03-08 2011-08-30 Infineon Technologies Ag Communication network unit and method for exchanging capability information
US8983051B2 (en) * 2007-04-03 2015-03-17 William F. Barton Outgoing call classification and disposition
US20080247529A1 (en) * 2007-04-03 2008-10-09 Microsoft Corporation Incoming Call Classification And Disposition
US8131556B2 (en) 2007-04-03 2012-03-06 Microsoft Corporation Communications using different modalities
US20080259918A1 (en) * 2007-04-19 2008-10-23 Craig Elliott Walker Method and apparatus for managing telephone calls
US11354667B2 (en) 2007-05-29 2022-06-07 Spriv Llc Method for internet user authentication
AU2007354390B2 (en) * 2007-05-29 2010-03-11 Guy S. Heffez Method and system for authenticating internet user indentity
US20090003582A1 (en) * 2007-06-27 2009-01-01 Microsoft Corporation Optimized Replacement of Calls Using A Grid Parameter
JP5018329B2 (en) * 2007-08-10 2012-09-05 富士通株式会社 Program for controlling communication device and communication device
CN102016825A (en) 2007-08-17 2011-04-13 谷歌公司 Ranking social network objects
US20110010384A1 (en) * 2007-08-17 2011-01-13 Google Inc. Multi-community content sharing in online social networks
BRPI0721937A2 (en) * 2007-08-17 2014-03-18 Google Inc ONLINE COMMUNITY CREATION METHODS WITHIN ONLINE SOCIAL NETWORK AND COMPUTER PROGRAM PRODUCT
US9137377B2 (en) * 2007-08-22 2015-09-15 Citrix Systems, Inc. Systems and methods for at least partially releasing an appliance from a private branch exchange
US8315362B2 (en) * 2007-08-22 2012-11-20 Citrix Systems, Inc. Systems and methods for voicemail avoidance
US8750490B2 (en) * 2007-08-22 2014-06-10 Citrix Systems, Inc. Systems and methods for establishing a communication session among end-points
US9357061B2 (en) 2007-09-10 2016-05-31 Dsi-Iti, Llc System and method for the automatic distribution of inmate phone recordings
WO2009045212A1 (en) * 2007-10-03 2009-04-09 Art Technology Group, Inc. Method and apparatus for the prevention of unwanted calls in a callback system
US7920474B2 (en) * 2007-10-08 2011-04-05 Samsung Electronics Co., Ltd. System and method for context-based hierarchical adaptive round robin scheduling
US8503334B2 (en) 2007-12-14 2013-08-06 Level 3 Communications, Llc System and method for providing network services over shared virtual private network (VPN)
US20090187848A1 (en) * 2007-12-21 2009-07-23 Richard Leo Murtagh Methods and systems for identifying a process for analyzing data displayed by a window to a user of a computing device
JP4985435B2 (en) * 2008-01-30 2012-07-25 日本電気株式会社 Monitoring and analyzing apparatus, method, and program
US8694617B2 (en) * 2008-01-31 2014-04-08 Centurylink Intellectual Property Llc System and method for orders and troubles metric attribution identification and aggregation
US8339959B1 (en) 2008-05-20 2012-12-25 Juniper Networks, Inc. Streamlined packet forwarding using dynamic filters for routing and security in a shared forwarding plane
US20090319666A1 (en) * 2008-06-18 2009-12-24 Shih-Chang Liang Method and Apparatus for Session Initiated Protocol (SIP) Based Information Uploading from an Optical Network Terminal (ONT)
US8612614B2 (en) * 2008-07-17 2013-12-17 Citrix Systems, Inc. Method and system for establishing a dedicated session for a member of a common frame buffer group
US8538003B2 (en) * 2008-09-12 2013-09-17 Hartford Fire Insurance Company Method and apparatus for integrating call center and existing telephony infrastructure
US8955107B2 (en) * 2008-09-12 2015-02-10 Juniper Networks, Inc. Hierarchical application of security services within a computer network
GB2463494A (en) * 2008-09-15 2010-03-17 Data Connection Ltd Providing a single telephone dialling number for multiple telephony devices
US7885253B2 (en) * 2008-09-30 2011-02-08 Avaya Inc. Synchronization of session-initiation-protocol proxy databases
US8300644B2 (en) * 2008-09-30 2012-10-30 Avaya Inc. Coordination of user information across session initiation protocol-based proxy servers
US8310609B2 (en) * 2008-09-30 2012-11-13 Sony Corporation Liquid crystal device, electronic apparatus, and method of manufacturing liquid crystal device
US8040808B1 (en) 2008-10-20 2011-10-18 Juniper Networks, Inc. Service aware path selection with a network acceleration device
US8224954B2 (en) * 2008-10-20 2012-07-17 At&T Intellectual Property I, L.P. Protecting subscriber database data integrity in geographical redundant deployments
US8549616B2 (en) * 2008-10-31 2013-10-01 At&T Intellectual Property I, L.P. Methods and apparatus to dynamically control access from virtual private networks to network-based shared resources
US8121118B2 (en) * 2008-10-31 2012-02-21 At&T Intellectual Property I, L.P. Methods and apparatus to dynamically control connectivity within virtual private networks
US8903973B1 (en) * 2008-11-10 2014-12-02 Tanium Inc. Parallel distributed network management
US8374576B2 (en) 2008-12-04 2013-02-12 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for generating resource utilization alerts through communication terminals
US8218744B2 (en) * 2008-12-12 2012-07-10 At&T Intellectual Property I, L.P. Method for indicating the context of a call to a called party
US8385326B2 (en) * 2008-12-29 2013-02-26 Microsoft Corporation Handling early media in VoIP communication with multiple endpoints
WO2010083509A2 (en) * 2009-01-16 2010-07-22 Tekelec Methods, systems, and computer readable media for centralized routing and call instance code management for bearer independent call control (bicc) signaling messages
US12034863B2 (en) 2009-01-21 2024-07-09 Spriv Llc Methods of authenticating the identity of a computer
US9621714B2 (en) 2009-01-27 2017-04-11 Value-Added Communications, Inc. System and method for electronic notification in institutional communication
US8582560B2 (en) * 2009-01-30 2013-11-12 Level 3 Communications, Llc System and method for routing calls associated with private dialing plans
US9225838B2 (en) 2009-02-12 2015-12-29 Value-Added Communications, Inc. System and method for detecting three-way call circumvention attempts
JP2012520515A (en) * 2009-03-10 2012-09-06 アイエムエス ソフトウェア サービシズ リミテッド Address intelligence system and method
JP5177042B2 (en) * 2009-03-24 2013-04-03 富士通株式会社 Communication terminal, location information notification method
US8391884B2 (en) * 2009-03-26 2013-03-05 Andrew Llc System and method for managing created location contexts in a location server
CN101854268B (en) * 2009-04-04 2013-06-05 华为技术有限公司 Method, device and system of IP (Internet Protocol) network performance measurement as well as method, device and system of IP network service quality control
US8200821B2 (en) 2009-06-19 2012-06-12 Comcast Cable Communications, Llc System and method for improved in-browser notification
WO2011025689A1 (en) * 2009-08-25 2011-03-03 Bank Of America Corporation Integrated fraud platform
JP5216719B2 (en) * 2009-08-27 2013-06-19 京セラドキュメントソリューションズ株式会社 Information processing apparatus and control apparatus
US8599834B2 (en) * 2009-09-29 2013-12-03 Ipc Systems, Inc. Systems, methods, and computer program products for providing a manual ring-down communication line using session initiation protocol
US20110103564A1 (en) * 2009-10-30 2011-05-05 Mitel Networks Corporation System and method for communicating guest preferences to a telephony device
US10389761B2 (en) * 2009-11-17 2019-08-20 Time Warner Cable Enterprises Llc Internet protocol multimedia subsystem voice-video mail service over a home network
US8635683B2 (en) * 2009-12-04 2014-01-21 International Business Machines Corporation Method to improve fraud detection on conference calling systems by detecting re-use of conference moderator passwords
US20110135073A1 (en) * 2009-12-04 2011-06-09 Charles Steven Lingafelt Methods to improve fraud detection on conference calling systems by detection of conference moderator password utilization from a non-authorized device
US8494142B2 (en) * 2009-12-04 2013-07-23 International Business Machines Corporation Methods to improve fraud detection on conference calling systems based on observation of participants' call time durations
US8243904B2 (en) * 2009-12-04 2012-08-14 International Business Machines Corporation Methods to improve security of conference calls by observation of attendees' order and time of joining the call
US20110135081A1 (en) * 2009-12-04 2011-06-09 Charles Steven Lingafelt Methods to improve fraud detection on conference calling systems by detection of non-typical useage of moderator passcode
US8705513B2 (en) * 2009-12-15 2014-04-22 At&T Intellectual Property I, L.P. Methods and apparatus to communicatively couple virtual private networks to virtual machines within distributive computing networks
US8621366B1 (en) 2010-02-16 2013-12-31 Google Inc. Self-creation of comic strips in social networks and other communications
US11792314B2 (en) 2010-03-28 2023-10-17 Spriv Llc Methods for acquiring an internet user's consent to be located and for authenticating the location information
US8626849B2 (en) * 2010-04-27 2014-01-07 Blackberry Limited Apparatus and method for resolving a race condition between two session initiation protocol (SIP) end points
US20110286365A1 (en) * 2010-05-21 2011-11-24 Avaya Inc. Method for Connection Preservation
US8473557B2 (en) 2010-08-24 2013-06-25 At&T Intellectual Property I, L.P. Methods and apparatus to migrate virtual machines between distributive computing networks across a wide area network
US8606787B1 (en) 2010-09-15 2013-12-10 Google Inc. Social network node clustering system and method
KR101848111B1 (en) 2010-09-27 2018-04-11 구글 엘엘씨 System and method for generating a ghost profile for a social network
WO2012057745A1 (en) 2010-10-27 2012-05-03 Hewlett-Packard Development Company, L.P. Pattern detection
US9449302B1 (en) 2010-11-04 2016-09-20 Google Inc. Generating personalized websites and newsletters
US8359006B1 (en) * 2010-11-05 2013-01-22 Sprint Communications Company L.P. Using communications records to detect unauthorized use of telecommunication services
US8595167B1 (en) 2010-11-30 2013-11-26 Google Inc. Predicting likelihood of a successful connection between unconnected users within a social network using a learning network
US9038177B1 (en) * 2010-11-30 2015-05-19 Jpmorgan Chase Bank, N.A. Method and system for implementing multi-level data fusion
US8887070B1 (en) 2010-12-16 2014-11-11 Google Inc. Conference calls for social streams
US8732240B1 (en) 2010-12-18 2014-05-20 Google Inc. Scoring stream items with models based on user interests
US8826446B1 (en) 2011-01-19 2014-09-02 Google Inc. System and method for applying privacy settings to a plurality of applications
US8683557B1 (en) 2011-02-05 2014-03-25 Google Inc. Delegation as a mechanism to manage business activity by taking on a shared identity
US11978052B2 (en) 2011-03-28 2024-05-07 Spriv Llc Method for validating electronic transactions
US9002956B1 (en) 2011-03-30 2015-04-07 Google Inc. Self-regulating social news feed
US8694593B1 (en) 2011-03-31 2014-04-08 Google Inc. Tools for micro-communities
US8909711B1 (en) 2011-04-27 2014-12-09 Google Inc. System and method for generating privacy-enhanced aggregate statistics
US8818049B2 (en) 2011-05-18 2014-08-26 Google Inc. Retrieving contact information based on image recognition searches
US8538742B2 (en) 2011-05-20 2013-09-17 Google Inc. Feed translation for a social network
US8589407B2 (en) 2011-06-17 2013-11-19 Google Inc. Automated generation of suggestions for personalized reactions in a social network
US9148399B1 (en) 2011-06-21 2015-09-29 Google Inc. Automatic publication of a user's application installation events
US8959083B1 (en) 2011-06-26 2015-02-17 Google Inc. Searching using social context
US9146656B1 (en) 2011-06-27 2015-09-29 Google Inc. Notifications user interface
US9417759B1 (en) 2011-06-27 2016-08-16 Google Inc. Synchronizing data across multiple browser tabs or windows
US8832854B1 (en) 2011-06-30 2014-09-09 Google Inc. System and method for privacy setting differentiation detection
US8326769B1 (en) 2011-07-01 2012-12-04 Google Inc. Monetary transfer in a social network
US9900351B2 (en) * 2011-07-20 2018-02-20 Genband Us Llc Methods, systems, and computer readable media for providing legacy devices access to a session initiation protocol (SIP) based network
US8645484B2 (en) 2011-08-02 2014-02-04 Google Inc. Messaging service using different text messaging channels
US9317807B1 (en) 2011-08-03 2016-04-19 Google Inc. Various ways to automatically select sharing settings
US8782761B1 (en) 2011-08-08 2014-07-15 Google Inc. Generating authentication challenges based on preferences of a user's contacts
CA2787816C (en) 2011-08-22 2022-03-22 Google Inc. Share box for endorsements
US8375331B1 (en) 2011-08-23 2013-02-12 Google Inc. Social computing personas for protecting identity in online social interactions
US20130061153A1 (en) * 2011-09-07 2013-03-07 Avaya Inc. System and Method for Inserting a Control System Into a Conference
US8903909B1 (en) 2011-09-15 2014-12-02 Google Inc. Detecting and extending engagement with stream content
US8997240B1 (en) 2011-09-21 2015-03-31 Google Inc. Generating user authentication challenges based on social network activity information
US9037864B1 (en) 2011-09-21 2015-05-19 Google Inc. Generating authentication challenges based on social network activity information
US8867849B1 (en) 2011-10-05 2014-10-21 Google Inc. Suggesting profile images for a social network
US9871757B1 (en) 2011-10-07 2018-01-16 Google Llc Sharing user-generated content to external social networks
US8935422B1 (en) 2011-10-11 2015-01-13 Google Inc. Embedded streams user interface
US9177062B2 (en) 2012-10-31 2015-11-03 Google Inc. Sorting social profile search results based on computing personal similarity scores
US20130121212A1 (en) * 2011-11-15 2013-05-16 Arunabha Guha Method and apparatus for supporting location-aware services
CN103139824A (en) * 2011-11-25 2013-06-05 华为技术有限公司 Method and device for identifying very annoying people (VAP) in mobile communication network
US8754926B1 (en) 2011-11-29 2014-06-17 Google Inc. Managing nodes of a synchronous communication conference
US9043417B1 (en) 2011-12-13 2015-05-26 Google Inc. Detecting spam across a social network
US9043870B1 (en) 2011-12-16 2015-05-26 Google Inc. Automated sign up based on existing online identity
US9251535B1 (en) 2012-01-05 2016-02-02 Juniper Networks, Inc. Offload of data transfer statistics from a mobile access gateway
US8391136B1 (en) 2012-01-27 2013-03-05 Google Inc. Fallback messaging
US9497149B2 (en) * 2012-02-03 2016-11-15 Richard Kramer System and method for reducing unsolicited E-mails
US9477936B2 (en) 2012-02-09 2016-10-25 Rockwell Automation Technologies, Inc. Cloud-based operator interface for industrial automation
US9641609B2 (en) 2012-02-28 2017-05-02 Google Inc. Integrated messaging
US9524487B1 (en) * 2012-03-15 2016-12-20 Google Inc. System and methods for detecting temporal music trends from online services
US9385979B1 (en) 2012-03-23 2016-07-05 Google Inc. Customizing posts by activity type and client type
US8825658B1 (en) 2012-03-27 2014-09-02 Google Inc. Organizing indications of approval for collections
US8693648B1 (en) 2012-04-16 2014-04-08 Google Inc. Providing backstage support for online video communication broadcasts
US8463796B1 (en) 2012-05-25 2013-06-11 Google Inc. System and method for providing noted items
US8930392B1 (en) 2012-06-05 2015-01-06 Google Inc. Simulated annealing in recommendation systems
US9720495B1 (en) 2012-06-22 2017-08-01 Google Inc. Aggregating online activities
US8997072B1 (en) 2012-07-13 2015-03-31 Google Inc. Compressing dependency graphs in a social network
US9230287B2 (en) 2012-08-21 2016-01-05 Google Inc. Real-time notifications and sharing of photos among users of a social network
US9680959B2 (en) 2012-08-30 2017-06-13 Google Inc. Recommending content based on intersecting user interest profiles
US8977654B1 (en) 2012-09-21 2015-03-10 Google Inc. Assigning classes to users of an online community
US8856173B2 (en) 2012-10-04 2014-10-07 Google Inc. User engagement in a social network using indications of acknowledgement
US8959151B1 (en) * 2012-10-04 2015-02-17 Google Inc. Establishing per-page multi-party communication sessions
US9275420B1 (en) 2012-10-05 2016-03-01 Google Inc. Changing user profile impression
US9231939B1 (en) 2012-10-09 2016-01-05 Google Inc. Integrating business tools in a social networking environment
US9269081B1 (en) 2012-10-12 2016-02-23 Google Inc. Seeding user connections in a social network
US9299060B2 (en) 2012-10-12 2016-03-29 Google Inc. Automatically suggesting groups based on past user interaction
US9098819B1 (en) 2012-10-18 2015-08-04 Google Inc. Identifying social network accounts belonging to the same user
US9117197B1 (en) 2012-10-19 2015-08-25 Google Inc. Alert system for social network users
US8819851B1 (en) 2012-10-29 2014-08-26 Google Inc. Access control using social network associations
US8977617B1 (en) 2012-10-31 2015-03-10 Google Inc. Computing social influence scores for users
CN103812913B (en) * 2012-11-14 2017-11-10 新华三技术有限公司 A kind of remote access method and device based on Virtual Networking Computing
US11172470B1 (en) 2012-12-21 2021-11-09 Tanium Inc. System, security and network management using self-organizing communication orbits in distributed networks
CN103906146B (en) * 2012-12-27 2018-08-03 南京中兴新软件有限责任公司 A kind of method of QoS alignment between WLAN and packet-based core networks
CN103997479B (en) * 2013-02-17 2018-06-15 新华三技术有限公司 A kind of asymmetric services IP Proxy Methods and equipment
KR102054941B1 (en) * 2013-05-02 2020-01-22 한국전자통신연구원 Apparatus of setting active networking of smart devices for providing fusion service and method thereof
US9989958B2 (en) 2013-05-09 2018-06-05 Rockwell Automation Technologies, Inc. Using cloud-based data for virtualization of an industrial automation environment
US9786197B2 (en) 2013-05-09 2017-10-10 Rockwell Automation Technologies, Inc. Using cloud-based data to facilitate enhancing performance in connection with an industrial automation system
US9703902B2 (en) 2013-05-09 2017-07-11 Rockwell Automation Technologies, Inc. Using cloud-based data for industrial simulation
US9438648B2 (en) 2013-05-09 2016-09-06 Rockwell Automation Technologies, Inc. Industrial data analytics in a cloud platform
US10026049B2 (en) 2013-05-09 2018-07-17 Rockwell Automation Technologies, Inc. Risk assessment for industrial systems using big data
US9709978B2 (en) 2013-05-09 2017-07-18 Rockwell Automation Technologies, Inc. Using cloud-based data for virtualization of an industrial automation environment with information overlays
US9391889B1 (en) * 2013-08-19 2016-07-12 Sprint Spectrum L.P. Methods and systems for using DNS-dip to select codec for a communication session
US10063458B2 (en) * 2013-10-13 2018-08-28 Nicira, Inc. Asymmetric connection with external networks
US20150188956A1 (en) 2013-12-27 2015-07-02 T-Mobile Usa, Inc. Unified Communication Device
US10931721B2 (en) * 2013-12-27 2021-02-23 T-Mobile Usa, Inc. User account-based access to real-time communications
CN104869097A (en) * 2014-02-20 2015-08-26 杭州华三通信技术有限公司 Route limiting method based on virtual private network (VPN), and route limiting device based on VPN
US10873645B2 (en) 2014-03-24 2020-12-22 Tanium Inc. Software application updating in a local network
US10306000B1 (en) * 2014-03-31 2019-05-28 Ribbon Communications Operating Company, Inc. Methods and apparatus for generating, aggregating and/or distributing presence information
US10623285B1 (en) 2014-05-09 2020-04-14 Amazon Technologies, Inc. Multi-mode health monitoring service
US10313225B1 (en) 2014-05-09 2019-06-04 Amazon Technologies, Inc. Scalable routing service
US9813379B1 (en) 2014-05-09 2017-11-07 Amazon Technologies, Inc. Virtual private gateways using compute instances
US10044581B1 (en) 2015-09-29 2018-08-07 Amazon Technologies, Inc. Network traffic tracking using encapsulation protocol
EP3172880B1 (en) * 2014-07-25 2018-09-05 Telefonaktiebolaget LM Ericsson (publ) Method of and communications handling equipment for controlling communication session establishment in a multimedia communications network.
US9787499B2 (en) 2014-09-19 2017-10-10 Amazon Technologies, Inc. Private alias endpoints for isolated virtual networks
US10178008B2 (en) * 2014-11-14 2019-01-08 Bigleaf Networks, Inc. Circuit-aware load balancing with dynamic quality of service
US9781169B2 (en) * 2015-01-27 2017-10-03 Tevnos LLC Switch controller for separating multiple portions of call
US9735981B2 (en) 2015-03-03 2017-08-15 At&T Intellectual Property I, L.P. Facilitation of session initiation protocol trunking
US11042131B2 (en) 2015-03-16 2021-06-22 Rockwell Automation Technologies, Inc. Backup of an industrial automation plant in the cloud
US11513477B2 (en) 2015-03-16 2022-11-29 Rockwell Automation Technologies, Inc. Cloud-based industrial controller
US10496061B2 (en) 2015-03-16 2019-12-03 Rockwell Automation Technologies, Inc. Modeling of an industrial automation environment in the cloud
US11243505B2 (en) 2015-03-16 2022-02-08 Rockwell Automation Technologies, Inc. Cloud-based analytics for industrial automation
US11461208B1 (en) 2015-04-24 2022-10-04 Tanium Inc. Reliable map-reduce communications in a decentralized, self-organizing communication orbit of a distributed network
US10637766B2 (en) * 2015-04-27 2020-04-28 Telefonaktiebolaget Lm Ericsson (Publ) Resource provisioning in a virtualized network
EP3099046B1 (en) * 2015-05-25 2018-07-04 EXFO Oy Arrangement, computer program code and method for call data record processing
US10021196B1 (en) 2015-06-22 2018-07-10 Amazon Technologies, Inc. Private service endpoints in isolated virtual networks
US10033602B1 (en) 2015-09-29 2018-07-24 Amazon Technologies, Inc. Network health management using metrics from encapsulation protocol endpoints
EP3363189A1 (en) * 2015-10-14 2018-08-22 Pindrop Security, Inc. Call detail record analysis to identify fraudulent activity and fraud detection in interactive voice response systems
US11153383B2 (en) 2016-03-08 2021-10-19 Tanium Inc. Distributed data analysis for streaming data sources
US11886229B1 (en) 2016-03-08 2024-01-30 Tanium Inc. System and method for generating a global dictionary and performing similarity search queries in a network
US11609835B1 (en) 2016-03-08 2023-03-21 Tanium Inc. Evaluating machine and process performance in distributed system
US11372938B1 (en) 2016-03-08 2022-06-28 Tanium Inc. System and method for performing search requests in a network
US10572961B2 (en) 2016-03-15 2020-02-25 Global Tel*Link Corporation Detection and prevention of inmate to inmate message relay
US9942787B1 (en) 2016-03-22 2018-04-10 Amazon Technologies, Inc. Virtual private network connection quality analysis
WO2017176934A1 (en) 2016-04-05 2017-10-12 Joinesty, Inc. Apparatus and method for automated email and password creation and curation across multiple websites
US9609121B1 (en) 2016-04-07 2017-03-28 Global Tel*Link Corporation System and method for third party monitoring of voice and video calls
CN107302470B (en) * 2016-04-14 2020-04-14 中国移动通信有限公司研究院 Method and device for processing xDR data represented by external data
US10135974B1 (en) * 2016-06-23 2018-11-20 8X8, Inc. Client-specific control of shared telecommunications services
US20180063333A1 (en) * 2016-08-29 2018-03-01 T-Mobile Usa, Inc. Call classification and routing using enum queries
US10911263B2 (en) 2016-09-28 2021-02-02 Amazon Technologies, Inc. Programmatic interfaces for network health information
US10862777B2 (en) 2016-09-28 2020-12-08 Amazon Technologies, Inc. Visualization of network health information
US10243820B2 (en) 2016-09-28 2019-03-26 Amazon Technologies, Inc. Filtering network health information based on customer impact
US10917324B2 (en) 2016-09-28 2021-02-09 Amazon Technologies, Inc. Network health data aggregation service
US10735431B2 (en) 2016-11-02 2020-08-04 Global Tel*Link Corp. Control of internet browsing in a secure environment
US10708369B2 (en) 2016-11-02 2020-07-07 Global Tel*Link Corp. Control of internet browsing in a secure environment
US9729727B1 (en) * 2016-11-18 2017-08-08 Ibasis, Inc. Fraud detection on a communication network
US10560431B1 (en) 2016-12-05 2020-02-11 Amazon Technologies, Inc. Virtual private gateway for encrypted communication over dedicated physical link
US9990826B1 (en) 2016-12-07 2018-06-05 Global Tel*Link Corporation System for monitoring offender during correctional supervisory program
US20190207946A1 (en) * 2016-12-20 2019-07-04 Google Inc. Conditional provision of access by interactive assistant modules
US10742746B2 (en) 2016-12-21 2020-08-11 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10212071B2 (en) 2016-12-21 2019-02-19 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10027797B1 (en) 2017-05-10 2018-07-17 Global Tel*Link Corporation Alarm control for inmate call monitoring
US10749827B2 (en) 2017-05-11 2020-08-18 Global Tel*Link Corporation System and method for inmate notification and training in a controlled environment facility
US11436417B2 (en) 2017-05-15 2022-09-06 Google Llc Providing access to user-controlled resources by automated assistants
US10127227B1 (en) 2017-05-15 2018-11-13 Google Llc Providing access to user-controlled resources by automated assistants
US10225396B2 (en) 2017-05-18 2019-03-05 Global Tel*Link Corporation Third party monitoring of a activity within a monitoring platform
US10863025B2 (en) * 2017-05-25 2020-12-08 T-Mobile Usa, Inc. Efficient robocall/scam identification with verification function
US10860786B2 (en) 2017-06-01 2020-12-08 Global Tel*Link Corporation System and method for analyzing and investigating communication data from a controlled environment
US10104710B1 (en) 2017-06-19 2018-10-16 Global Tel*Link Corporation Dual mode transmission in a controlled environment
US9930088B1 (en) 2017-06-22 2018-03-27 Global Tel*Link Corporation Utilizing VoIP codec negotiation during a controlled environment call
GB2563947B (en) * 2017-06-30 2020-01-01 Resilient Plc Fraud Detection System
US9912821B1 (en) 2017-06-30 2018-03-06 Global Tel*Link Corporation Call processing system for modifying inmate communication limits
US10841755B2 (en) 2017-07-01 2020-11-17 Phoneic, Inc. Call routing using call forwarding options in telephony networks
US10333870B2 (en) 2017-07-06 2019-06-25 Global Tel*Link Corporation Presence-based communications in a controlled environment
US11140020B1 (en) 2018-03-01 2021-10-05 Amazon Technologies, Inc. Availability-enhancing gateways for network traffic in virtualized computing environments
CN110234105B (en) * 2018-03-06 2022-04-01 中国移动通信有限公司研究院 Method and device for detecting whether VLR verifies service rejection instruction
WO2019245131A1 (en) 2018-06-20 2019-12-26 주식회사 케이티 Apparatus and method for detecting illegal call
US11343355B1 (en) 2018-07-18 2022-05-24 Tanium Inc. Automated mapping of multi-tier applications in a distributed system
US10805459B1 (en) 2018-08-07 2020-10-13 First Orion Corp. Call screening service for communication devices
EP4418146A1 (en) 2018-08-07 2024-08-21 Google Llc Assembling and evaluating automated assistant responses for privacy concerns
US10700955B2 (en) * 2018-09-14 2020-06-30 The Nielsen Company (Us), Llc Methods apparatus and medium to exclude network communication traffic from media monitoring records
US10484532B1 (en) * 2018-10-23 2019-11-19 Capital One Services, Llc System and method detecting fraud using machine-learning and recorded voice clips
GB2608939B (en) 2018-12-28 2023-09-13 Resilient Plc Fraud detection system
US11470194B2 (en) 2019-08-19 2022-10-11 Pindrop Security, Inc. Caller verification via carrier metadata
US11095480B2 (en) 2019-08-30 2021-08-17 Vmware, Inc. Traffic optimization using distributed edge services
US10764434B1 (en) * 2019-09-26 2020-09-01 Joinesty, Inc. Phone alert for unauthorized call
US11831670B1 (en) 2019-11-18 2023-11-28 Tanium Inc. System and method for prioritizing distributed system risk remediations
US11356473B2 (en) * 2019-11-25 2022-06-07 Level 3 Communications, Llc Web service-based monitoring and detection of fraudulent or unauthorized use of calling service
CN111092893A (en) * 2019-12-22 2020-05-01 上海唐盛信息科技有限公司 Network security protection method based on XDR ticket data
US20230036110A1 (en) * 2020-01-23 2023-02-02 Nippon Telegraph And Telephone Corporation Optimization engine, optimization method, and program
TWI766290B (en) * 2020-06-03 2022-06-01 遠傳電信股份有限公司 Electronic device and method for detecting net phone hijacking
US11616755B2 (en) 2020-07-16 2023-03-28 Vmware, Inc. Facilitating distributed SNAT service
US11606294B2 (en) 2020-07-16 2023-03-14 Vmware, Inc. Host computer configured to facilitate distributed SNAT service
US11494746B1 (en) * 2020-07-21 2022-11-08 Amdocs Development Limited Machine learning system, method, and computer program for making payment related customer predictions using remotely sourced data
US11611613B2 (en) 2020-07-24 2023-03-21 Vmware, Inc. Policy-based forwarding to a load balancer of a load balancing cluster
US11902050B2 (en) 2020-07-28 2024-02-13 VMware LLC Method for providing distributed gateway service at host computer
US11451413B2 (en) 2020-07-28 2022-09-20 Vmware, Inc. Method for advertising availability of distributed gateway service and machines at host computer
US11563764B1 (en) 2020-08-24 2023-01-24 Tanium Inc. Risk scoring based on compliance verification test results in a local network
US11895034B1 (en) 2021-01-29 2024-02-06 Joinesty, Inc. Training and implementing a machine learning model to selectively restrict access to traffic
US11265296B1 (en) * 2021-05-11 2022-03-01 Roqos, Inc. System and method to create and implement virtual private networks over internet for multiple internet access types
US11962615B2 (en) 2021-07-23 2024-04-16 Bank Of America Corporation Information security system and method for denial-of-service detection
US20230126032A1 (en) * 2021-10-26 2023-04-27 Zoom Video Communications, Inc. Communication Forwarding Based On Content Analysis

Citations (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5608720A (en) * 1993-03-09 1997-03-04 Hubbell Incorporated Control system and operations system interface for a network element in an access system
US5758343A (en) * 1995-12-08 1998-05-26 Ncr Corporation Apparatus and method for integrating multiple delegate directory service agents
US5852812A (en) * 1995-08-23 1998-12-22 Microsoft Corporation Billing system for a network
US5877759A (en) * 1997-03-26 1999-03-02 Netscape Communications Corporation Interface for user/agent interaction
US5918213A (en) * 1995-12-22 1999-06-29 Mci Communications Corporation System and method for automated remote previewing and purchasing of music, video, software, and other multimedia products
US5999612A (en) * 1997-05-27 1999-12-07 International Business Machines Corporation Integrated telephony and data services over cable networks
US6008805A (en) * 1996-07-19 1999-12-28 Cisco Technology, Inc. Method and apparatus for providing multiple management interfaces to a network device
US6115741A (en) * 1996-03-14 2000-09-05 Domenikos; Steven D. Systems and methods for executing application programs from a memory device linked to a server
US6125391A (en) * 1998-10-16 2000-09-26 Commerce One, Inc. Market makers using documents for commerce in trading partner networks
US6145001A (en) * 1995-05-19 2000-11-07 Telogy Networks, Inc. Network management gateway
US6154743A (en) * 1998-06-16 2000-11-28 Cisco Technology, Inc. Technique for accessing heterogeneous directory services in an APPN environment
US6175656B1 (en) * 1999-03-25 2001-01-16 Sony Corporation Non-linear video sharpening filter
US6189033B1 (en) * 1998-07-16 2001-02-13 Hewlett-Packard Company Method and system for providing performance guarantees for a data service system of a data access network system
US6192405B1 (en) * 1998-01-23 2001-02-20 Novell, Inc. Method and apparatus for acquiring authorized access to resources in a distributed system
US6192418B1 (en) * 1997-06-25 2001-02-20 Unisys Corp. System and method for performing external procedure calls from a client program to a server program while both are operating in a heterogenous computer
US6195697B1 (en) * 1999-06-02 2001-02-27 Ac Properties B.V. System, method and article of manufacture for providing a customer interface in a hybrid network
US6208986B1 (en) * 1997-12-15 2001-03-27 International Business Machines Corporation Web interface and method for accessing and displaying directory information
US6247055B1 (en) * 1996-06-28 2001-06-12 International Business Machines Corporation System, method and program for enabling a client to reconnect to a same server in a network of computer systems after the server has moved to a different network address
US6282281B1 (en) * 1995-12-11 2001-08-28 Hewlett-Packard Company Method of providing telecommunications services
US20010032076A1 (en) * 1999-12-07 2001-10-18 Kursh Steven R. Computer accounting method using natural language speech recognition
US20010037379A1 (en) * 2000-03-31 2001-11-01 Noam Livnat System and method for secure storage of information and grant of controlled access to same
US20010037469A1 (en) * 1999-05-11 2001-11-01 Sun Microsystems, Inc. Method and apparatus for authenticating users
US20010049745A1 (en) * 2000-05-03 2001-12-06 Daniel Schoeffler Method of enabling transmission and reception of communication when current destination for recipient is unknown to sender
US6330560B1 (en) * 1999-09-10 2001-12-11 International Business Machines Corporation Multiple manager to multiple server IP locking mechanism in a directory-enabled network
US6334116B1 (en) * 1998-02-02 2001-12-25 Checkfree Corporation Technique for centrally tracking transactions in an electronic billing system
US6343332B1 (en) * 1997-10-20 2002-01-29 Fujitsu Limited Communication link information generating device, a three-tier client/server system, and a medium storing a communication link information generator program
US20020023232A1 (en) * 2000-08-10 2002-02-21 Shield Security Systems, L.L.C. Interactive key control system and method of managing access to secured locations
US6363411B1 (en) * 1998-08-05 2002-03-26 Mci Worldcom, Inc. Intelligent network
US20020062346A1 (en) * 2000-09-22 2002-05-23 Chen Joesph Shih-Chun Apparatus, method, and computer program to integrate applications and appliances over a network
US6418324B1 (en) * 1995-06-01 2002-07-09 Padcom, Incorporated Apparatus and method for transparent wireless communication between a remote device and host system
US20020123972A1 (en) * 2001-02-02 2002-09-05 Hodgson Robert B. Apparatus for and method of secure ATM debit card and credit card payment transactions via the internet
US6453356B1 (en) * 1998-04-15 2002-09-17 Adc Telecommunications, Inc. Data exchange system and method
US20020135611A1 (en) * 1999-03-04 2002-09-26 Trevor Deosaran Remote performance management to accelerate distributed processes
US20020138563A1 (en) * 2001-03-20 2002-09-26 Trivedi Prakash A. Systems and methods for communicating from an integration platform to a profile management server
US6460072B1 (en) * 1996-08-28 2002-10-01 Infospace, Inc. Method and system for tracking the purchase of a product and services over the internet
US6535855B1 (en) * 1997-12-09 2003-03-18 The Chase Manhattan Bank Push banking system and method
US20030058277A1 (en) * 1999-08-31 2003-03-27 Bowman-Amuah Michel K. A view configurer in a presentation services patterns enviroment
US6574661B1 (en) * 1997-09-26 2003-06-03 Mci Communications Corporation Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client
US20030172145A1 (en) * 2002-03-11 2003-09-11 Nguyen John V. System and method for designing, developing and implementing internet service provider architectures
US6681232B1 (en) * 2000-06-07 2004-01-20 Yipes Enterprise Services, Inc. Operations and provisioning systems for service level management in an extended-area data communications network
US6697806B1 (en) * 2000-04-24 2004-02-24 Sprint Communications Company, L.P. Access network authorization
US20040135805A1 (en) * 2003-01-10 2004-07-15 Gottsacker Neal F. Document composition system and method
US6801914B2 (en) * 1999-03-15 2004-10-05 Microsoft Corporation Persistent client-server database sessions
US6952836B1 (en) * 2000-09-26 2005-10-04 At&T Corp. Method and apparatus for managing the provisioning of client devices connected to an interactive TV network

Family Cites Families (133)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US2003A (en) * 1841-03-12 Improvement in horizontal windivhlls
US2002003A (en) * 1930-09-20 1935-05-21 Ig Farbenindustrie Ag Production of acetylene and carbon black
US4924500A (en) * 1989-05-17 1990-05-08 Northern Telecom Limited Carrier independent network services
US5577209A (en) * 1991-07-11 1996-11-19 Itt Corporation Apparatus and method for providing multi-level security for communication among computers and terminals on a network
TW225623B (en) * 1993-03-31 1994-06-21 American Telephone & Telegraph Real-time fraud monitoring system
US5950121A (en) * 1993-06-29 1999-09-07 Airtouch Communications, Inc. Method and apparatus for fraud control in cellular telephone systems
US5606604A (en) * 1993-12-13 1997-02-25 Lucent Technologies Inc. System and method for preventing fraud upon PBX through a remote maintenance or administration port
US5463681A (en) * 1993-12-29 1995-10-31 At&T Corp. Security system for terminating fraudulent telephone calls
US5627886A (en) * 1994-09-22 1997-05-06 Electronic Data Systems Corporation System and method for detecting fraudulent network usage patterns using real-time network monitoring
US5768354A (en) * 1995-02-02 1998-06-16 Mci Communications Corporation Fraud evaluation and reporting system and method thereof
EP0818103B1 (en) * 1995-03-30 2004-02-25 Azure Solutions Limited Detecting possible fraudulent communications usage
US5802320A (en) 1995-05-18 1998-09-01 Sun Microsystems, Inc. System for packet filtering of data packets at a computer network interface
WO1997024688A1 (en) 1995-12-29 1997-07-10 Tele-Communications, Inc. Method and aparatus for processing billing transactions
JP2000507765A (en) * 1996-03-29 2000-06-20 ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニー Fraud monitoring in telecommunications networks
US5768271A (en) 1996-04-12 1998-06-16 Alcatel Data Networks Inc. Virtual private network
US5842040A (en) * 1996-06-18 1998-11-24 Storage Technology Corporation Policy caching method and apparatus for use in a communication device based on contents of one data unit in a subset of related data units
US5918019A (en) * 1996-07-29 1999-06-29 Cisco Technology, Inc. Virtual dial-up protocol for network communication
US6064653A (en) * 1997-01-07 2000-05-16 Bell Atlantic Network Services, Inc. Internetwork gateway to gateway alternative communication
US5907803A (en) * 1997-01-14 1999-05-25 Telefonaktiebolaget L M Ericsson (Publ) User assisted fraud detection in a cellular communications system
US5953653A (en) * 1997-01-28 1999-09-14 Mediaone Group, Inc. Method and system for preventing mobile roaming fraud
US6600733B2 (en) * 1997-02-06 2003-07-29 Verizon Laboratories Inc. System for interconnecting packet-switched and circuit-switched voice communications
US6327352B1 (en) * 1997-02-24 2001-12-04 Ameritech Corporation System and method for real-time fraud detection within a telecommunications system
US6157648A (en) * 1997-03-06 2000-12-05 Bell Atlantic Network Services, Inc. Network session management
US6178505B1 (en) * 1997-03-10 2001-01-23 Internet Dynamics, Inc. Secure delivery of information in a network
US6047267A (en) * 1997-05-14 2000-04-04 Portal Software, Inc. Method and apparatus for tracking multiple payment resources and charging transactions to payment resources in on line transaction processing system
US6226748B1 (en) 1997-06-12 2001-05-01 Vpnet Technologies, Inc. Architecture for virtual private networks
US6173399B1 (en) * 1997-06-12 2001-01-09 Vpnet Technologies, Inc. Apparatus for implementing virtual private networks
US6035281A (en) 1997-06-16 2000-03-07 International Business Machines Corporation System and method of multiparty billing for Web access
US5995604A (en) * 1997-06-20 1999-11-30 Nortel Networks Corporation Method of preventing fraudulent toll calls by key system users
US6188753B1 (en) * 1997-06-30 2001-02-13 Sprint Communications Co. L.P. Method and apparatus for detection and prevention of calling card fraud
US6415167B1 (en) * 2000-05-02 2002-07-02 Instrumentation Metrics, Inc. Fiber optic probe placement guide
US6115673A (en) * 1997-08-14 2000-09-05 Instrumentation Metrics, Inc. Method and apparatus for generating basis sets for use in spectroscopic analysis
US6018575A (en) 1997-09-08 2000-01-25 Mci Worldcom Direct distance dialing (DDD) access to a communications services platform
WO1999029095A1 (en) 1997-12-03 1999-06-10 Telcordia Technologies, Inc. Intelligent data peripheral systems and methods
US6226364B1 (en) * 1997-12-08 2001-05-01 Bellsouth Intellectual Property Management Corporation Method and system for providing prepaid and credit-limited telephone services
US6339595B1 (en) * 1997-12-23 2002-01-15 Cisco Technology, Inc. Peer-model support for virtual private networks with potentially overlapping addresses
US6363079B1 (en) * 1997-12-31 2002-03-26 At&T Corp. Multifunction interface facility connecting wideband multiple access subscriber loops with various networks
US6079020A (en) * 1998-01-27 2000-06-20 Vpnet Technologies, Inc. Method and apparatus for managing a virtual private network
US6353614B1 (en) * 1998-03-05 2002-03-05 3Com Corporation Method and protocol for distributed network address translation
US6182226B1 (en) * 1998-03-18 2001-01-30 Secure Computing Corporation System and method for controlling interactions between networks
US6233313B1 (en) * 1998-03-26 2001-05-15 Bell Atlantic Network Services Call detail reporting for lawful surveillance
EP0948164A1 (en) * 1998-04-01 1999-10-06 Hewlett-Packard Company Generating telephony service detail records
IL134616A (en) * 1998-06-19 2004-05-12 Juniper Networks Inc Device for performing ip forwarding and atm switching
US6452915B1 (en) * 1998-07-10 2002-09-17 Malibu Networks, Inc. IP-flow classification in a wireless point to multi-point (PTMP) transmission system
US6862622B2 (en) * 1998-07-10 2005-03-01 Van Drebbel Mariner Llc Transmission control protocol/internet protocol (TCP/IP) packet-centric wireless point to multi-point (PTMP) transmission system architecture
US6680922B1 (en) * 1998-07-10 2004-01-20 Malibu Networks, Inc. Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system
US20020097725A1 (en) * 1998-07-27 2002-07-25 Nec Corporation Resource and protocol management for virtual private networks within multiprocessor ATM switches
US6580721B1 (en) * 1998-08-11 2003-06-17 Nortel Networks Limited Routing and rate control in a universal transfer mode network
US6134307A (en) * 1998-09-21 2000-10-17 Iridium Ip Llc Call conversion process for a business system for a global telecommunications network
US6157041A (en) * 1998-10-13 2000-12-05 Rio Grande Medical Technologies, Inc. Methods and apparatus for tailoring spectroscopic calibration models
US6912232B1 (en) * 1998-10-19 2005-06-28 At&T Corp. Virtual private network
US7236950B2 (en) * 1998-10-29 2007-06-26 Universal Card Services Corp. Method and system of combined billing of multiple accounts on a single statement
US6826616B2 (en) * 1998-10-30 2004-11-30 Science Applications International Corp. Method for establishing secure communication link between computers of virtual private network
US6502135B1 (en) * 1998-10-30 2002-12-31 Science Applications International Corporation Agile network protocol for secure communications with assured system availability
US6614781B1 (en) * 1998-11-20 2003-09-02 Level 3 Communications, Inc. Voice over data telecommunications network architecture
US6266525B1 (en) * 1998-12-17 2001-07-24 Lucent Technologies Inc. Method for detecting fraudulent use of a communications system
US6631258B1 (en) * 1998-12-31 2003-10-07 At&T Corp. Busy call forwarding in a wireless centrex services system
US6587683B1 (en) * 1998-12-31 2003-07-01 At&T Corp. Unconditional call forwarding in a wireless centrex services system
FI990088A (en) * 1999-01-18 2000-07-19 Nokia Networks Oy Implementation of call forwarding in a telecommunications network
US7307990B2 (en) * 1999-01-19 2007-12-11 Cisco Technology, Inc. Shared communications network employing virtual-private-network identifiers
US6280381B1 (en) * 1999-07-22 2001-08-28 Instrumentation Metrics, Inc. Intelligent system for noninvasive blood analyte prediction
US6873617B1 (en) * 1999-02-03 2005-03-29 Tekno Industries, Inc. Means for and methods of “in-progress” fraud, billing and maintenance in a SS#7 network of high speed data links
US6937597B1 (en) * 1999-02-26 2005-08-30 Lucent Technologies Inc. Signaling method for internet telephony
US6731642B1 (en) * 1999-05-03 2004-05-04 3Com Corporation Internet telephony using network address translation
US6564261B1 (en) * 1999-05-10 2003-05-13 Telefonaktiebolaget Lm Ericsson (Publ) Distributed system to intelligently establish sessions between anonymous users over various networks
JP4110671B2 (en) * 1999-05-27 2008-07-02 株式会社日立製作所 Data transfer device
US6453034B1 (en) * 1999-07-29 2002-09-17 Mci Worldcom, Inc. Method of and system for extending internet telephony over virtual private network direct access lines
US6614800B1 (en) * 1999-09-02 2003-09-02 International Business Machines Corporation Method and system for virtual private network administration channels
US6798772B2 (en) * 1999-09-07 2004-09-28 Nortel Network Limited Method for public access to private phone numbers and other telephonic peripherals using a caller access code
US6532088B1 (en) * 1999-09-10 2003-03-11 Alcatel System and method for packet level distributed routing in fiber optic rings
US6888842B1 (en) * 1999-10-05 2005-05-03 Nortel Networks Limited Scheduling and reservation for dynamic resource control systems
US6741688B1 (en) * 1999-10-28 2004-05-25 Cisco Technology, Inc. Method and apparatus for handling telephone calls
US6738910B1 (en) * 1999-10-28 2004-05-18 International Business Machines Corporation Manual virtual private network internet snoop avoider
US6473863B1 (en) * 1999-10-28 2002-10-29 International Business Machines Corporation Automatic virtual private network internet snoop avoider
US6366577B1 (en) * 1999-11-05 2002-04-02 Mci Worldcom, Inc. Method for providing IP telephony with QoS using end-to-end RSVP signaling
US6904276B1 (en) * 1999-12-17 2005-06-07 Mci, Inc. Apparatus and method for managing call billing records
US7154997B1 (en) * 1999-12-28 2006-12-26 Cingular Wireless Ii, Llc Subscription-based billing methods and systems for shared network modem pools
US6252952B1 (en) 1999-12-30 2001-06-26 At&T Corp Personal user network (closed user network) PUN/CUN
US6539483B1 (en) * 2000-01-12 2003-03-25 International Business Machines Corporation System and method for generation VPN network policies
GB0001040D0 (en) * 2000-01-17 2000-03-08 Nortel Networks Corp Communications network
JP2001237876A (en) * 2000-02-21 2001-08-31 Nec Corp Buildup method for ip virtual private network and the ip virtual private network
US7096495B1 (en) * 2000-03-31 2006-08-22 Intel Corporation Network session management
US7215637B1 (en) * 2000-04-17 2007-05-08 Juniper Networks, Inc. Systems and methods for processing packets
US6621793B2 (en) * 2000-05-22 2003-09-16 Telefonaktiebolaget Lm Ericsson (Publ) Application influenced policy
JP4099930B2 (en) * 2000-06-02 2008-06-11 株式会社日立製作所 Router device and VPN identification information setting method
US6611863B1 (en) * 2000-06-05 2003-08-26 Intel Corporation Automatic device assignment through programmable device discovery for policy based network management
EP2375643B1 (en) * 2000-06-16 2015-02-18 Fujitsu Limited Communication device having VPN accomodation function
US6765921B1 (en) * 2000-06-28 2004-07-20 Nortel Networks Limited Communications network
US6836895B2 (en) * 2000-06-29 2004-12-28 Howard Hamlin Hybrid electronic e-mail server system and method
US6779020B1 (en) * 2000-07-18 2004-08-17 Lucent Technologies Inc. Establishing communications between a calling server and a called server according to services subscribed by their respective calling and called parties
US6826147B1 (en) * 2000-07-25 2004-11-30 Nortel Networks Limited Method and apparatus for aggregate flow control in a differentiated services network
US7035248B2 (en) * 2000-08-10 2006-04-25 Alcatel Switch with emulation client
WO2002015481A2 (en) 2000-08-17 2002-02-21 Trendium, Inc. Methods, systems, and computer program products for managing a service provided by a network
US6405035B1 (en) * 2000-08-24 2002-06-11 Telefonaktiebolaget L.M. Ericsson System and method for forwarding messages to a subscriber device
US7007299B2 (en) * 2000-08-30 2006-02-28 Citibank, N.A. Method and system for internet hosting and security
US7315554B2 (en) * 2000-08-31 2008-01-01 Verizon Communications Inc. Simple peering in a transport network employing novel edge devices
US20020032793A1 (en) * 2000-09-08 2002-03-14 The Regents Of The University Of Michigan Method and system for reconstructing a path taken by undesirable network traffic through a computer network from a source of the traffic
US20020038339A1 (en) * 2000-09-08 2002-03-28 Wei Xu Systems and methods for packet distribution
US7272643B1 (en) * 2000-09-13 2007-09-18 Fortinet, Inc. System and method for managing and provisioning virtual routers
US6822940B1 (en) * 2000-09-29 2004-11-23 Cisco Technology, Inc. Method and apparatus for adapting enforcement of network quality of service policies based on feedback about network conditions
US20020042875A1 (en) * 2000-10-11 2002-04-11 Jayant Shukla Method and apparatus for end-to-end secure data communication
JP4183379B2 (en) * 2000-11-27 2008-11-19 富士通株式会社 Network and edge router
US6954790B2 (en) * 2000-12-05 2005-10-11 Interactive People Unplugged Ab Network-based mobile workgroup system
US20050088977A1 (en) * 2000-12-14 2005-04-28 Nortel Networks Limited Dynamic virtual private network (VPN) tunnel quality of service (QoS) treatment
US20020075901A1 (en) * 2000-12-19 2002-06-20 Bruce Perlmutter Bandwidth management for tunneling servers
US6914883B2 (en) * 2000-12-28 2005-07-05 Alcatel QoS monitoring system and method for a high-speed DiffServ-capable network element
US6775235B2 (en) * 2000-12-29 2004-08-10 Ragula Systems Tools and techniques for directing packets over disparate networks
KR100360274B1 (en) * 2000-12-30 2002-11-09 엘지전자 주식회사 Method for supporting general ip telephone system in nat based private network
US6822904B2 (en) 2001-01-03 2004-11-23 Micron Technology, Inc. Fast sensing scheme for floating-gate memory cells
US20020101868A1 (en) * 2001-01-30 2002-08-01 David Clear Vlan tunneling protocol
US7120682B1 (en) * 2001-03-08 2006-10-10 Cisco Technology, Inc. Virtual private networks for voice over networks applications
US20020138427A1 (en) * 2001-03-20 2002-09-26 Trivedi Prakash A. Systems and methods for communicating from an integration platform to a billing unit
US20020138296A1 (en) * 2001-03-20 2002-09-26 Holmes Ralph K. Systems and methods for collecting and rating contact center usage
US6778498B2 (en) * 2001-03-20 2004-08-17 Mci, Inc. Virtual private network (VPN)-aware customer premises equipment (CPE) edge router
US7068646B2 (en) * 2001-04-03 2006-06-27 Voxpath Networks, Inc. System and method for performing IP telephony including internal and external call sessions
IL151027A0 (en) * 2001-04-05 2003-04-10 Method for voice activated network access
US7356596B2 (en) * 2001-12-07 2008-04-08 Architecture Technology Corp. Protecting networks from access link flooding attacks
US7146428B2 (en) * 2001-12-12 2006-12-05 At&T Corp. Secure in-band signaling method for mobility management crossing firewalls
CN1615612A (en) * 2001-12-21 2005-05-11 查尔斯·S·缪尔黑德 System for supply chain management of virtual private network services
US7937439B2 (en) * 2001-12-27 2011-05-03 Utbk, Inc. Apparatus and method for scheduling live advice communication with a selected service provider
US7367045B2 (en) * 2002-03-16 2008-04-29 Trustedflow Systems, Inc. Trusted communications system
US20030200441A1 (en) * 2002-04-19 2003-10-23 International Business Machines Corporation Detecting randomness in computer network traffic
US20040034702A1 (en) * 2002-08-16 2004-02-19 Nortel Networks Limited Method and apparatus for exchanging intra-domain routing information between VPN sites
US7478427B2 (en) * 2003-05-05 2009-01-13 Alcatel-Lucent Usa Inc. Method and apparatus for providing adaptive VPN to enable different security levels in virtual private networks (VPNs)
US20040223497A1 (en) * 2003-05-08 2004-11-11 Onvoy Inc. Communications network with converged services
US20040266420A1 (en) * 2003-06-24 2004-12-30 Nokia Inc. System and method for secure mobile connectivity
US7305705B2 (en) * 2003-06-30 2007-12-04 Microsoft Corporation Reducing network configuration complexity with transparent virtual private networks
US7366181B2 (en) * 2003-09-06 2008-04-29 Fujitsu Limited Virtual private network (VPN) with channelized ethernet over sonet (EoS) interface and method
US8718262B2 (en) * 2007-03-30 2014-05-06 Mattersight Corporation Method and system for automatically routing a telephonic communication base on analytic attributes associated with prior telephonic communication
US8229090B2 (en) * 2007-04-17 2012-07-24 Verizon Patent And Licensing Inc. Voice portal communications
US8200189B2 (en) * 2008-06-19 2012-06-12 Verizon Patent And Licensing Inc. Voice portal to voice portal VoIP transfer
US8428243B2 (en) * 2008-12-19 2013-04-23 Verizon Patent And Licensing Inc. Method and system for trunk independent gateway transfer of calls
US20110246308A1 (en) * 2010-04-02 2011-10-06 Segall Timothy R Method and system for managing interactive communications campaigns with preference management

Patent Citations (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5608720A (en) * 1993-03-09 1997-03-04 Hubbell Incorporated Control system and operations system interface for a network element in an access system
US6145001A (en) * 1995-05-19 2000-11-07 Telogy Networks, Inc. Network management gateway
US6418324B1 (en) * 1995-06-01 2002-07-09 Padcom, Incorporated Apparatus and method for transparent wireless communication between a remote device and host system
US5852812A (en) * 1995-08-23 1998-12-22 Microsoft Corporation Billing system for a network
US5758343A (en) * 1995-12-08 1998-05-26 Ncr Corporation Apparatus and method for integrating multiple delegate directory service agents
US6282281B1 (en) * 1995-12-11 2001-08-28 Hewlett-Packard Company Method of providing telecommunications services
US5918213A (en) * 1995-12-22 1999-06-29 Mci Communications Corporation System and method for automated remote previewing and purchasing of music, video, software, and other multimedia products
US6115741A (en) * 1996-03-14 2000-09-05 Domenikos; Steven D. Systems and methods for executing application programs from a memory device linked to a server
US6247055B1 (en) * 1996-06-28 2001-06-12 International Business Machines Corporation System, method and program for enabling a client to reconnect to a same server in a network of computer systems after the server has moved to a different network address
US6008805A (en) * 1996-07-19 1999-12-28 Cisco Technology, Inc. Method and apparatus for providing multiple management interfaces to a network device
US6460072B1 (en) * 1996-08-28 2002-10-01 Infospace, Inc. Method and system for tracking the purchase of a product and services over the internet
US5877759A (en) * 1997-03-26 1999-03-02 Netscape Communications Corporation Interface for user/agent interaction
US5999612A (en) * 1997-05-27 1999-12-07 International Business Machines Corporation Integrated telephony and data services over cable networks
US6192418B1 (en) * 1997-06-25 2001-02-20 Unisys Corp. System and method for performing external procedure calls from a client program to a server program while both are operating in a heterogenous computer
US6574661B1 (en) * 1997-09-26 2003-06-03 Mci Communications Corporation Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client
US6343332B1 (en) * 1997-10-20 2002-01-29 Fujitsu Limited Communication link information generating device, a three-tier client/server system, and a medium storing a communication link information generator program
US6535855B1 (en) * 1997-12-09 2003-03-18 The Chase Manhattan Bank Push banking system and method
US6208986B1 (en) * 1997-12-15 2001-03-27 International Business Machines Corporation Web interface and method for accessing and displaying directory information
US6192405B1 (en) * 1998-01-23 2001-02-20 Novell, Inc. Method and apparatus for acquiring authorized access to resources in a distributed system
US6334116B1 (en) * 1998-02-02 2001-12-25 Checkfree Corporation Technique for centrally tracking transactions in an electronic billing system
US6453356B1 (en) * 1998-04-15 2002-09-17 Adc Telecommunications, Inc. Data exchange system and method
US6154743A (en) * 1998-06-16 2000-11-28 Cisco Technology, Inc. Technique for accessing heterogeneous directory services in an APPN environment
US6189033B1 (en) * 1998-07-16 2001-02-13 Hewlett-Packard Company Method and system for providing performance guarantees for a data service system of a data access network system
US6363411B1 (en) * 1998-08-05 2002-03-26 Mci Worldcom, Inc. Intelligent network
US6125391A (en) * 1998-10-16 2000-09-26 Commerce One, Inc. Market makers using documents for commerce in trading partner networks
US20020135611A1 (en) * 1999-03-04 2002-09-26 Trevor Deosaran Remote performance management to accelerate distributed processes
US6801914B2 (en) * 1999-03-15 2004-10-05 Microsoft Corporation Persistent client-server database sessions
US6175656B1 (en) * 1999-03-25 2001-01-16 Sony Corporation Non-linear video sharpening filter
US20010037469A1 (en) * 1999-05-11 2001-11-01 Sun Microsystems, Inc. Method and apparatus for authenticating users
US6195697B1 (en) * 1999-06-02 2001-02-27 Ac Properties B.V. System, method and article of manufacture for providing a customer interface in a hybrid network
US20030058277A1 (en) * 1999-08-31 2003-03-27 Bowman-Amuah Michel K. A view configurer in a presentation services patterns enviroment
US6330560B1 (en) * 1999-09-10 2001-12-11 International Business Machines Corporation Multiple manager to multiple server IP locking mechanism in a directory-enabled network
US20010032076A1 (en) * 1999-12-07 2001-10-18 Kursh Steven R. Computer accounting method using natural language speech recognition
US20010037379A1 (en) * 2000-03-31 2001-11-01 Noam Livnat System and method for secure storage of information and grant of controlled access to same
US6697806B1 (en) * 2000-04-24 2004-02-24 Sprint Communications Company, L.P. Access network authorization
US20010049745A1 (en) * 2000-05-03 2001-12-06 Daniel Schoeffler Method of enabling transmission and reception of communication when current destination for recipient is unknown to sender
US6681232B1 (en) * 2000-06-07 2004-01-20 Yipes Enterprise Services, Inc. Operations and provisioning systems for service level management in an extended-area data communications network
US20020023232A1 (en) * 2000-08-10 2002-02-21 Shield Security Systems, L.L.C. Interactive key control system and method of managing access to secured locations
US20020062346A1 (en) * 2000-09-22 2002-05-23 Chen Joesph Shih-Chun Apparatus, method, and computer program to integrate applications and appliances over a network
US6952836B1 (en) * 2000-09-26 2005-10-04 At&T Corp. Method and apparatus for managing the provisioning of client devices connected to an interactive TV network
US20020123972A1 (en) * 2001-02-02 2002-09-05 Hodgson Robert B. Apparatus for and method of secure ATM debit card and credit card payment transactions via the internet
US20020138563A1 (en) * 2001-03-20 2002-09-26 Trivedi Prakash A. Systems and methods for communicating from an integration platform to a profile management server
US20030172145A1 (en) * 2002-03-11 2003-09-11 Nguyen John V. System and method for designing, developing and implementing internet service provider architectures
US20040135805A1 (en) * 2003-01-10 2004-07-15 Gottsacker Neal F. Document composition system and method

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6898587B2 (en) * 2002-01-18 2005-05-24 Bea Systems, Inc. System and method for performing commutative operations in data access systems
US20030140029A1 (en) * 2002-01-18 2003-07-24 Adam Messinger System and method for performing commutative operations in data access systems
WO2003069434A2 (en) * 2002-02-11 2003-08-21 At & T Wireless Services, Inc. Centralized communications network charging methods and apparatus
US20030158812A1 (en) * 2002-02-11 2003-08-21 At&T Wireless Services, Inc. Centralized communications network charging methods and apparatus
US7515696B2 (en) 2002-02-11 2009-04-07 At&T Mobility Ii Llc Centralized communications network charging methods and apparatus
WO2003069434A3 (en) * 2002-02-11 2004-01-15 At & T Wireless Services Inc Centralized communications network charging methods and apparatus
US7254640B2 (en) * 2002-04-09 2007-08-07 Vigilos, Inc. System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure
USRE43933E1 (en) * 2002-04-09 2013-01-15 Hatoshi Investments Jp, Llc System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure
US20030191773A1 (en) * 2002-04-09 2003-10-09 Vigilos, Inc. System and method for providing a fault-tolerant data warehouse environment
US7318065B2 (en) 2002-05-23 2008-01-08 Bea Sytems, Inc. System and method for performing commutative operations in data access systems
GB2396074B (en) * 2002-12-05 2006-04-19 Bts Holdings Plc System and method for management of communications resources
EP1427134A3 (en) * 2002-12-05 2005-06-01 BTS Holdings PLC System and method for management of communications resources
EP1427134A2 (en) * 2002-12-05 2004-06-09 BTS Holdings PLC System and method for management of communications resources
US20070201429A1 (en) * 2003-09-08 2007-08-30 Raffaela Brodt Method For Billing A Service In A Packet Data Network
US20050261920A1 (en) * 2004-05-20 2005-11-24 Hewlett-Packard Development Company, L.P. Establishing services
US8799901B2 (en) * 2004-05-20 2014-08-05 Hewlett-Packard Development Company, L.P. Establishing new service as conversation by replacing variables in generic service in an order with variables from a decoupled method of legacy service
FR2895858A1 (en) * 2005-12-29 2007-07-06 Radiotelephone Sfr METHOD AND DEVICE FOR IMPROVING THE FUNCTIONING OF A TAXATION CHAIN BY SETTING UP A MULTI-LEVEL DEGRADE MODE
EP1804420A1 (en) * 2005-12-29 2007-07-04 Société Française du Radiotéléphone-SFR Method and device for improving the operation of a billing chain by implementing a multi-level backup method
US20090313059A1 (en) * 2008-06-12 2009-12-17 Verizon Business Network Services Inc. System and method for integrating issue tracking systems
US9031856B2 (en) * 2008-06-12 2015-05-12 Verizon Patent And Licensing Inc. System and method for integrating issue tracking systems
US20180203754A1 (en) * 2017-01-17 2018-07-19 Bank Of America Corporation Individualized Channel Error Detection and Resolution
US10761920B2 (en) * 2017-01-17 2020-09-01 Bank Of America Corporation Individualized channel error detection and resolution
US11729588B1 (en) 2021-09-30 2023-08-15 T-Mobile Usa, Inc. Stateless charging and message handling
US12041521B2 (en) 2021-09-30 2024-07-16 T-Mobile Usa, Inc. Stateless charging and message handling

Also Published As

Publication number Publication date
US7289522B2 (en) 2007-10-30
US20050066053A1 (en) 2005-03-24
US8700528B2 (en) 2014-04-15
MXPA03008507A (en) 2011-08-04
EP1374509A1 (en) 2004-01-02
US7197560B2 (en) 2007-03-27
WO2002075339A1 (en) 2002-09-26
EP1373912A1 (en) 2004-01-02
US7599351B2 (en) 2009-10-06
US9124722B2 (en) 2015-09-01
BR0208232A (en) 2004-06-22
US20020138378A1 (en) 2002-09-26
US20020136370A1 (en) 2002-09-26
US8761745B2 (en) 2014-06-24
JP2005518681A (en) 2005-06-23
BR0208168A (en) 2004-03-02
BR0208268A (en) 2004-07-06
EP1374508A1 (en) 2004-01-02
EP1374509A4 (en) 2005-02-02
CA2441281A1 (en) 2002-09-26
MXPA03008511A (en) 2005-09-15
US20090285204A1 (en) 2009-11-19
EP1374508A4 (en) 2005-02-02
CN1509412A (en) 2004-06-30
US8543734B2 (en) 2013-09-24
JP2004529549A (en) 2004-09-24
BR0208231A (en) 2004-03-02
JP2005505948A (en) 2005-02-24
US20100175125A1 (en) 2010-07-08
US8200577B2 (en) 2012-06-12
US20020137490A1 (en) 2002-09-26
CA2441344A1 (en) 2002-09-26
US20020188712A1 (en) 2002-12-12
US20020136206A1 (en) 2002-09-26
EP1373912A4 (en) 2005-02-16
US7809860B2 (en) 2010-10-05
US20120246043A1 (en) 2012-09-27
MXPA03008479A (en) 2010-10-11

Similar Documents

Publication Publication Date Title
US7054866B2 (en) Systems and methods for communicating from an integration platform to a provisioning server
US20020138427A1 (en) Systems and methods for communicating from an integration platform to a billing unit
WO2002076006A2 (en) Systems and methods for communicating from an integration platform to a billing unit
US8195738B2 (en) Systems and methods for communicating from an integration platform to a profile management server
US8660017B2 (en) Systems and methods for updating IP communication service attributes using an LDAP
US7039041B2 (en) Operational support system for telecommunication services
US20130223289A1 (en) Operational support system
US20020194504A1 (en) Systems and methods for accessing reporting services
US8417632B2 (en) Systems and methods for interfacing with a billing and account management unit
US7043480B2 (en) Systems and methods for communicating from an integration platform to a lightweight directory access protocol based database
US20020138296A1 (en) Systems and methods for collecting and rating contact center usage
US8341116B2 (en) Systems and methods for updating an LDAP

Legal Events

Date Code Title Description
AS Assignment

Owner name: WORLDCOM, INC., MISSISSIPPI

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TRIVEDI, PRAKASH A.;REEL/FRAME:012700/0041

Effective date: 20020314

AS Assignment

Owner name: MCI, INC., VIRGINIA

Free format text: CHANGE OF NAME;ASSIGNOR:WORLDCOM, INC.;REEL/FRAME:016672/0375

Effective date: 20040419

AS Assignment

Owner name: VERIZON BUSINESS GLOBAL LLC, VIRGINIA

Free format text: CHANGE OF NAME;ASSIGNOR:MCI, LLC;REEL/FRAME:019114/0361

Effective date: 20061120

Owner name: MCI, LLC, NEW JERSEY

Free format text: MERGER;ASSIGNOR:MCI, INC.;REEL/FRAME:019114/0315

Effective date: 20060109

AS Assignment

Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERIZON BUSINESS GLOBAL LLC;REEL/FRAME:032734/0502

Effective date: 20140409

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE PREVIOUSLY RECORDED AT REEL: 032734 FRAME: 0502. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:VERIZON BUSINESS GLOBAL LLC;REEL/FRAME:044626/0088

Effective date: 20140409