WO2002075605A9 - Xml based transaction detail records - Google Patents

Xml based transaction detail records

Info

Publication number
WO2002075605A9
WO2002075605A9 PCT/US2002/008578 US0208578W WO02075605A9 WO 2002075605 A9 WO2002075605 A9 WO 2002075605A9 US 0208578 W US0208578 W US 0208578W WO 02075605 A9 WO02075605 A9 WO 02075605A9
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
sep
data structure
telecommunications
server
Prior art date
Application number
PCT/US2002/008578
Other languages
French (fr)
Other versions
WO2002075605A1 (en
Inventor
John K Gallant
Kathleen A Mcmurry
Joseph W Pizzimenti
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 EP02721497A priority Critical patent/EP1381975A1/en
Priority to BR0208230-6A priority patent/BR0208230A/en
Priority to CA002441323A priority patent/CA2441323A1/en
Priority to MXPA03008508A priority patent/MXPA03008508A/en
Priority to JP2002574541A priority patent/JP2004532547A/en
Publication of WO2002075605A1 publication Critical patent/WO2002075605A1/en
Publication of WO2002075605A9 publication Critical patent/WO2002075605A9/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1442—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
    • H04L12/1446—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level inter-operator billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4523—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using lightweight directory access protocol [LDAP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4535—Network 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4557—Directories for hybrid networks, e.g. including telephone numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/762—Media network packet handling at the source 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/564—Enhancement of application control based on intercepted application data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H04L69/085—Protocols for interworking; Protocol conversion specially adapted for interworking of IP-based networks with other networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/43—Billing software details
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/44—Augmented, consolidated or itemized billing statement or bill presentation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/47—Fraud detection or prevention means
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/49—Connection to several service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/51—Arrangements 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/52—Arrangements 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/53—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP using mediation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/55—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for hybrid networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/56—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for VoIP communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58—Arrangements 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/63—Arrangements 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/745—Customizing according to wishes of subscriber, e.g. friends or family
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8292—Charging for signaling or unsuccessful connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/2218—Call detail recording
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0104—Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0108—Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0148—Fraud detection or prevention means
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0168—On line or real-time flexible customization or negotiation according to wishes of subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0172—Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0176—Billing arrangements using internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0188—Network monitoring; statistics on usage on called/calling number
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/202—VoIP; Packet switched telephony
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/2046—Hybrid network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/22—Bandwidth or usage-sensitve billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/44—Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/46—Connection to several service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/54—Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/912—Applications of a database
    • Y10S707/922—Communications
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/912—Applications of a database
    • Y10S707/944—Business related

Definitions

  • the present invention relates to telecommunications, and is more particularly related to recording transaction data in a telecommunications network.
  • IP(Internet Protocol) telephony which is also referred to as Voice-over-IP (VoIP)
  • VoIP Voice-over-IP
  • IP telephony over the Internet is often offered at minimal, or no cost to the users.
  • IP telephony has found significant success, particularly in the long distance market.
  • IP telephony Users also have turned to IP telephony as a matter of convenience. Both voice and data services are often accessible through a single piece of equipment, e.g., the personal computer. Furthermore, traditional DTMF (Dual-Tone Multi-Frequency) phones can enjoy the benefits of VoIP technology through the use of network adapters. The continual integration of voice and data services further fuels this demand for IP telephony applications.
  • DTMF Dual-Tone Multi-Frequency
  • IP Telephony must be interoperable with the Public Switched Telephone Network (PSTN) and have a comparable Quality of Service (QoS). Therefore, to ensure the highest success rate with the customers, the service providers need to build a network that provides call quality, service reliability, and security that is at minimum, on par with the PSTN. It is essential that IP Telephony solutions meet customer demands of high-quality, ease of use, superior customer service, and lower cost. Since the public Internet can only provide "best- efforts" service, managed IP networks are required to support VoIP traffic with the call quality, service reliability, and security that users are accustomed to.
  • SIP Session Initiation Protocol
  • SEP is an application-layer signaling protocol that has been developed to create, modify, and terminate sessions with one or more users. These sessions include Internet telephone calls, multi-media conferences, and multi-media distribution.
  • SIP functionality is typically resident on application servers. Sip servers are configured to provide telephony services, and process call event information. Because vendors have developed their own custom SEP application programs, call events and telephony services are processed by each vendor's application server in a proprietary way. Unfortunately, when a network includes network elements provided by a multiplicity of vendors, it becomes necessary to accommodate a variety of proprietary interfaces that enable the devices to transmit and receive network transaction data.
  • transaction data may include call event information, billing information, monitoring information, error data, fraud prevention data, timeout data and any other data that must be tracked by the network.
  • the system and method will be extensible, providing embedded information that will enable a receiving computer to read the generic, uniformly formatted records without needing to accommodate any proprietary interface.
  • the present invention relates to a platform independent method for capturing transaction data and other information in a uniform manner.
  • the method and system of the present invention is extensible, producing generic, umformly formatted records that can be read by a receiving computer without needing a special proprietary interface.
  • One aspect of the present invention is a method for recording transactions in a telecommunications network.
  • the method includes creating an XML transaction detail file.
  • At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction.
  • the at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.
  • the present invention includes a computer-readable medium having stored thereon a data structure for recording transactions in a telecommunications network.
  • the data structure includes: an XML declaration field, the XML declaration field defining the data structure as an XML file; a server identification field, the server identification field including an address of a server generating the XML file; and a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the data structure in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
  • the present invention includes a telecommunications network.
  • the network includes at least one telecommunications apparatus configured to perform a telecommunications transaction.
  • At least one S P-server is coupled to the at least one telecommunications apparatus.
  • the at least one SP-server is configured to create an XML transaction detail file, process the telecommunications transaction, and store at least one transaction detail record in the XML transaction detail file.
  • the at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.
  • the present invention includes a computer-readable medium having stored thereon computer-executable instructions for performing a method for recording transactions in a telecommunications network.
  • the method includes creating an XML transaction detail file.
  • the XML transaction detail file is active for a predetermined period of time.
  • At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction.
  • the at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.
  • FIG. 1 is a block diagram of an EP telecommunications network in accordance with one embodiment of the present invention.
  • FIG. 2 is a chart showing a method for managing telecommunications transactions in accordance with another embodiment of the present invention.
  • An exemplary embodiment of the network of the present invention is shown in Figure 1 , and is designated generally throughout by reference numeral 10.
  • the present invention includes a method for recording transactions in a telecommunications network.
  • the method includes creating an XML transaction detail file.
  • At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction.
  • the at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.
  • the present invention provides a platform independent method for capturing transaction data and other information in a uniform manner.
  • the system and method of the present invention is extensible, providing embedded information in generic, uniformly formatted transaction detail records that can be read by a receiving computer without needing a special proprietary interface.
  • Telecommunications network 10 includes IP network 100, coupled to the Public Switched Telephone Network (PSTN) 20, Internet 30, a customer PBX 40, SEP phones 50, and SIP-clients 52.
  • EP network 100 includes IP network backbone 120.
  • Backbone 120 is coupled to a number of SEP elements that support voice services, including SEP proxy server 102, redirect server (RS) 104, SEP conferencing server 106, voice mail server 108, Operational Support Systems (OSS) 110, Dedicated Access Line (DAL) gateway 112, network gateway 114, ENCP gateway 116, and enterprise gateway 118.
  • Network backbone 120 is also directly coupled to Internet 30, SEP phones 50, and SEP Clients 52.
  • SEP Session Initiation Protocol
  • EP Internet Protocol
  • P network 100 may be of any suitable type, but there is shown by way of 'example a network having a layered architecture.
  • the layered nature of the architecture provides protocol separation and independence, whereby one protocol can be exchanged or modified without affecting the other higher layer or lower layer protocols. It is advantageous that the development of these protocols can occur concurrently and independently.
  • the foundation of the layered architecture is the Internet Protocol (EP) layer.
  • the EP layer provides a connectionless data delivery service that operates on a "best effort" basis; that is, no guarantees of packet delivery are made.
  • a TCP (Transmission Control Protocol) layer is disposed above the EP layer.
  • the TCP layer provides a connection-oriented protocol that ensures reliable delivery of the IP packets, in part, by performing sequencing functions. This sequencing function reorders any EP packets that arrive out of sequence.
  • the UDP User Datagram Protocol
  • the User Datagram Protocol provides a connectionless service that utilizes the IP protocol to send a data unit, known as a datagram. Unlike TCP, UDP does not provide sequencing of packets. It relies on the higher layer protocols to sort the arriving packets.
  • UDP is preferable over TCP when the data units are small, which saves processing time because of the nii imal reassembly time.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • SEP Session Initiation Protocol
  • SEP is an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants.
  • SEP is also a client-server protocol wherein servers respond to requests generated by clients.
  • a detailed discussion of SEP and its call control services are described in IETF RFC 2543 and EETF Internet Draft "SIP Call Control Services", June 17, 1999. ' Those of ordinary skill in the art will recognize that application-layer protocols other than SEP ' may be employed, including the H.323 protocol.
  • SDP Session Description Protocol
  • EP network backbone 120 may be of any suitable type, but there is shown by way of example a network that includes a nationwide high speed network that operates at 622MB/sec (OC-12).
  • Backbone 104 employs advanced packet switching technology commonly known as the Asynchronous Transfer Mode (ATM).
  • Backbone 120 also utilizes a fiber-optic transmission technology referred to as the Synchronous Optical Network (SONET).
  • SONET Synchronous Optical Network
  • the combination of ATM and SONET enables high speed, high capacity voice, data, and video signals to be combined and transmitted on demand.
  • the high speed of backbone 120 is achieved by connecting Internet Protocol through the ATM switching matrix, and running this combination on the SONET network.
  • INCP 116 is an Intelligent Network Control Point that is accessed by RS 104 to obtain dial plan information for existing private network customers.
  • INCP 116 is an additional database that may be. queried by RS 104 to route specific private calls.
  • INCP 116 may also be accessed by SPS 102.
  • PSTN 160 is, by way of example, a circuit switched network employing Signaling System No. 7 (SS7).
  • Plain-Old-Telephone-Service (POTS) telephone 22 maybe any suitable telephone set currently in use or on the market.
  • Enterprise gateway 118 may be of any suitable type. In the example depicted in
  • enterprise gateway 118 is coupled to PBX 40.
  • PBX 40 includes trunks or lines for PBX phones 42.
  • Enterprise gateway 118 provides the interface between packet switched EP network 100 and the signaling employed by PBX 40.
  • enterprise gateway 118 may use Integrated Digital Services Network (ISDN), Circuit Associated Signaling (CAS), or other PBX interfaces (e.g., European Telecommunications Standards Institute (ETSI) PRE R2) to interface with PBX 40.
  • ISDN Integrated Digital Services Network
  • CAS Circuit Associated Signaling
  • ETSI European Telecommunications Standards Institute
  • DAL gateway 112 is a system configured to support private traffic between EP locations and non-EP locations. DAL gateway 112 may be optionally employed in network 100.
  • Network gateway 114 is an SS7 (Signaling System 7)/C7-to-SEP Gateway. This provides users with the ability to place calls between locations within EP network 100 and locations within PSTN 20.
  • network gateway 114 is configured to provide access to a voice switch (not shown), such as a Class 3 switch for domestic call processing, or a Class 5 switch for long-haul and/or international connections.
  • SEP phones 50, and SEP-client devices 52 may be of any suitable type provided that they conform to the standards promulgated in EETF 2543.
  • SEP phones 50 have a 10-key dial pad similar to traditional phones.
  • SEP URLs which include PSTN 20 numbers, can be entered using the keypad or retrieved from a speed dial directory. To place a call, digits are entered using the dial pad. The entered digits are-collected by the phone. When the "Dial" button is pressed, the call is initiated.
  • SEP phones 50 ring similar to traditional phones when receiving an incoming call.
  • SEP phones 50 may take the form of standalone devices - e.g., a SEP phone may be configured to function and appear like a Plain Old Telephone Service (POTS) telephone set.
  • POTS Plain Old Telephone Service
  • SEP client 52 is a software client that runs, for example, on a personal computer (PC) or laptop. From a signaling perspective, SIP-devices 50 and 52 are very similar, if
  • Each type of server in network 100 has a critical role in recording and managing the various transactions supported by network 100.
  • SPS SEP-proxy server
  • SPS 102 functions as both a server and a client for the purpose of making requests on behalf of other clients.
  • SPS 102 may service a request directly or pass it on to another server.
  • SPS 102 may also rewrite a message before forwarding it.
  • SPS 102 is configured to create a transaction detail file in XML format to record transaction data processed by SPS 102.
  • the transaction detail file is populated with transaction detail records(TDR).
  • Each TDR records a transaction such as a SEP call-event (INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER, etc.), or any of the other events described above, such as errors, or timeouts.
  • SPS 102 includes an XML processor module that is called by
  • SPS 102 application software to create the XML transaction detail file.
  • the XML processor module may also be called upon to read XML documents, e.g., to provide access to the content and structure of an XML file.
  • the format of the XML transaction detail file is shown in detail in Table I.
  • Table 1 SIP Service Transaction Detail File Structure-Network Server
  • a response contains the information about any SIP record Response that is either sent or received by the NS.
  • IP Address that the Response message was received from if the Response was received at the NS where AA, BB, CC, DD can be digits 0 through 255 and port can be a number 1024 through 65535.
  • TCP Connection to TUA AA.BB.CC.DD:EE "lost" - where AA.BB.CC.DD is the IP address and EE is the port number of the TUA
  • TCP Connection to TUA AA.BB.CC.DD:EE "could not be established” - where AA.BB.CC.DD is the IP address and EE is the port number of the TUA
  • RS Timeout for AA.BB.CC.DD. ⁇ E - where AA.BB.CC.DD is the IP Address and EE is the port number of the RS that timed out
  • TDR Data End ⁇ /tdr_record> Multiple Tdr Delimiter Records may
  • Voice mail server (VMS) 108 is a SEP -server that provides voice mail services. Users of the EP network 100 are provided with the capability to integrate voicemail services based upon SEP . Calls are routed to the voice mail system 108 by SPS 102 and RS 104 for certain calls, such as those that indicate a Busy or Ring No Answer condition. Calls to voice mail can also occur as a Find-Me/Follow-Me termination option, or as an Unconditional Call Forward option selected by the user. Calls by the user to log in and retrieve messages are routed to VMS 108 as a SEP endpoint. A voice mail address can be entered for any destination address in RS 104.
  • the Call Forwarding Unconditional address or Find-Me address, etc. can be the SEP URL of a voice mail account.
  • SEP enabled VMS 108 supports all alphanumeric SEP URLs, Headers, Request, Methods and Status codes (e.g., per IETF RFC 2543).
  • VMS 108 supports SUBSCRIBE, NOTIFY, and Message Waiting Indicator (MWI) messages.
  • VMS 108 may restrict access to the system through a variety of ways. Access may be secured through private access code. The access code may be supplied in the SEP INVITE message or through DTMF. VMS 108 may reject messages based on the EP address of the originating server.
  • VMS 108 may reject the message.
  • VMS 108 is also configured to create a transaction detail file in XML format to thereby record transaction data corresponding to all network transactions processed by VMS 108. Because the format of the VMS XML transaction detail file is very similar, to the SPS 102 XML transaction detail file, it will not be repeated here.
  • SEP conferencing server (SCS) 106 is a centralized SEP-conference server configured to provide audio conferencing capabilities.
  • SCS 106 support G.711
  • SCS 106 may specify two modes of operation. Under a Reserved mode, the users are required to reserve a bridge ahead of time.
  • An Instant Conferencing mode refers to the ability to set-up a conference as needed without any need for advance reservation, allowing ad-hoc set-up of conferences as well permitting client based conferences to migrate to a bridge. Conference access is secured through an access code. Participants joining the bridge can send their access code via the SEP Invite message. POTS telephone users can enter through DTMF depending on the support for DTMF at the gateway. An audible tone may be played to announce each participant as they join the bridge.
  • the system supports a coordinator /operator initiated conference, wherein the operator dials-out to each of the conference participants and brings them into the conference.
  • the conference operator can enter and announce the name of the participants into the conference.
  • the conference coordinator can notify the participants of the time and date for the call.
  • the operators may be able to put parties On and Off Hold. Music On Hold is supported, whereby the parties on Hold are provided with music.
  • SCS 106 also permits private conferencing (i.e., sub-conferencing), wherein designated conference callers may confer privately within a conference call and then be returned to the main call. Calls from PSTN 20 may be forwarded to SCS 106 by network gateway 114. From the perspective of SCS 106, a SIP originated call is not processed differently than a non-SEP call because network gateway 114 ' is able to translate the called number to the conference URL. However, SCS 106 is able to validate the caller by prompting for passwords and validating the password entered as DTMF digits. As an alternate to password collection through DTMF, SCS 106 may support authentication using SEP.
  • SEP Secure Element
  • the SEP INVITE message carries additional user parameters, such as username/password combination that may be used by SCS 106 to validate the user.
  • conferencing system 106 supports web based provisioning by the users.
  • SCS 106 interfaces with the OSS 110 for provisioning, alarming and reporting.
  • the provisioning and reporting interface of the OSS 110 assists with a number of conferencing functionalities, such as the capability to Setup, Modify and Delete conferences.
  • the administrator or moderator of the conference is able to specify the number of attendees to a conference, as well as specify duration of the conference, date and time-by-time zone, and name of reserved conference.
  • SCS 106 is configured to create a transaction detail file in XML format to thereby record transaction data corresponding to all the above described transactions processed by conferencing server 106. Because the format of the SCS 106 XML transaction detail file is similar to the SPS 102 XML transaction detail file, it will not 'be repeated.
  • RS 104 is a SIP redirect server that conforms with SEP standards detailed per IETF RFC 2543. RS 104 accepts SEP messages, maps the address into one or more new addresses, and returns these addresses to the client, which could be SPS 102. RS 104 does not initiate its own SEP requests, and RS 104 does not accept calls. RS 104 is essentially, a location server wherein information about possible terminating locations can be obtained. RS 104 also serves as a repository for end user information enabling address validation, feature status, and real-time subscriber feature configuration. RS 104 may also be used to store configuration information.
  • RS 104 is also configured to create a transaction detail file in XML format to thereby record transaction data corresponding to all SEP transactions, timeouts and errors processed by RS 104.
  • the transaction detail file includes transaction detail records used to record network transactions processed by RS 104.
  • RS 104 includes an XML processor module that is called by RS 104 application software module to create the XML transaction detail file.
  • the XML processor module may also be called to read an XML file. Because RS 104 has a different function in the management of network 100, its XML transaction detail file is substantially different than the SPS XML transaction detail file.
  • the format of the RS XML transaction detail file is shown in detail in Table II.
  • OSS 110 is also a critical system for managing network 100.
  • OSS 110 supports the establishment, provisioning, data collection, and billing of the services of the system 100.
  • OSS 110 is a distributed computing system that includes customer management, account management, billing, network facilities provisioning, and network data collection functionality. All of the XML transaction detail files generated by the above described servers SPS 102, RS 104, SCS 106, and VMS 108, are transmitted to OSS 110 using the XML transaction detail files described above.
  • the XML transaction detail files are used by OSS .110 for a variety of network functions including, but not limited to, network management, billing, and record keeping.
  • the present invention provides a platform independent method for capturing transaction data in a uniform manner.
  • the present invention is extensible, providing embedded information that will enable any receiving computer to read the generic, uniformly formatted XML files without needing any proprietary interface.
  • the OSS computing system is based on technology provided by SUN Microsystems, the databases employed by the computing system are based on technology provided by ORACLE.
  • OSS 110 provides and controls access to customer accounts. Users may utilize a web page to monitor service, login to their account, and manage certain elements permitted by user profiles.
  • the account management system allows network personnel to establish, maintain, or deactivate customer accounts.
  • customer information is viewed via a web interface.
  • the billing system processes customer event records, the customer pricing plan data, adjustments, taxation and other data in the preparation of customer invoices.
  • the network facilities provisioning system provides the information required by network engineers to ensure that the appropriate hardware and software is in place to provide service. This may involve the creation of a customer profile, and the reconfiguration of SPS 102, RS 104, or other network elements. Network provisioning may also require the placement of hardware plug-in devices used in backbone 120.
  • a process management/work flow system serves as the core of OSS 110.
  • the software is a Common Object Request Broker Architecture (CORBA) based publish- and-subscribe messaging middleware that provides graphical process automation, data transformation, event management and flexible connectors to transact with interfacing applications.
  • This middleware architecture software fulfills the function of integrating all OSS 110 components and may provide hooks to non-OSS components using designated standard interfaces.
  • a chart showing a method for recording telecommunications transaction data in accordance with the present invention is disclosed. The method described herein is equally applicable to SPS 102, RS 104, . SCS 106, and VMS 108.
  • the XML detail file is created.
  • XML detail file will have the form depicted in Table Ef, otherwise, the XML detail file will be of the form, or similar to the form, shown in Table I.
  • Each XML file is active for a predetermined period of time.
  • the server initializes a timer to track elapsed time. For example, OSS 110 may direct each server to keep each XML detail file active for one day, or one hour, as the case may be.
  • the server analyzes the transaction and performs an appropriate action.
  • SPS 102 may receive an ENVETE message from SEP-phone 50, requesting a session with a user at POTS telephone 22.
  • SPS 102 may perform and coordinate a plurality of transactions required to set up the session between SEP phone 50 and POTS telephone 22. In doing so, SPS 102 creates a transaction detail record (TDR) for each transaction in the call set-up process.
  • TDR transaction detail record
  • the TDRs are written into the XML file.
  • no records are written into the file. In this case, only the header information in the XML file is transmitted to OSS 110.
  • the server transmits the XML file to OSS 110. After the XML file is transmitted, a new file is created and the process repeats. If the timer has not elapsed, the server waits for additional transactions to process. En step 216, the server may suspend operations for any number of reasons. For example, if the server requires maintenance and is off-line, it is unnecessary to continue to monitor and record network transactions.
  • XML transaction detail files in accordance with the present invention can be employed for any events occurring within network 10. Calls placed between all or any combinations of SEP- phones, enterprise gateways, network gateways, DAL gateways, INCP gateways, SEP- voice ail servers, and SIP conferencing servers may employ the present mvention. Those of ordinary skill in the art will also recognize that the present invention can be employed using any suitable type of transport network. Further, the present invention is applicable to any type of session that may be established including, but not limited to, telephony, video, audio, instant messaging, and etc. It is also contemplated that the present invention may be employed for billing, monitoring, management, or for any of a wide variety of services performed by the network.

Abstract

The present invention is directed to a method for managing transactions in a telecommunications network. The method includes creating an XML transaction detail file. At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction. The at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.

Description

XMLBASED TRANSACTIONDETAILRECORDS
The present invention relates to telecommunications, and is more particularly related to recording transaction data in a telecommunications network. There are many factors driving the move toward converged networks such as deregulation, new sources of competition, substantial growth of the Internet, and the growth and importance of data in customers' enterprise networks. The popularity and convenience of the Internet has resulted in the reinvention of traditional telephony services. IP(Internet Protocol) telephony, which is also referred to as Voice-over-IP (VoIP), involves the conversion of voice information into data packets that are subsequently transmitted over an EP network. IP telephony over the Internet is often offered at minimal, or no cost to the users. Thus, IP telephony has found significant success, particularly in the long distance market. Users also have turned to IP telephony as a matter of convenience. Both voice and data services are often accessible through a single piece of equipment, e.g., the personal computer. Furthermore, traditional DTMF (Dual-Tone Multi-Frequency) phones can enjoy the benefits of VoIP technology through the use of network adapters. The continual integration of voice and data services further fuels this demand for IP telephony applications.
The primary incentives for customers to adopt a converged solution are cost and the promise of new and expanded capabilities. However, if IP telephony is to be fully accepted in the marketplace, VoIP must be interoperable with the Public Switched Telephone Network (PSTN) and have a comparable Quality of Service (QoS). Therefore, to ensure the highest success rate with the customers, the service providers need to build a network that provides call quality, service reliability, and security that is at minimum, on par with the PSTN. It is essential that IP Telephony solutions meet customer demands of high-quality, ease of use, superior customer service, and lower cost. Since the public Internet can only provide "best- efforts" service, managed IP networks are required to support VoIP traffic with the call quality, service reliability, and security that users are accustomed to.
One approach that is being considered in providing VoIP with the call quality, service reliability, and security that users are accustomed to, involves the Session Initiation Protocol (SIP). SEP is an application-layer signaling protocol that has been developed to create, modify, and terminate sessions with one or more users. These sessions include Internet telephone calls, multi-media conferences, and multi-media distribution. SIP functionality is typically resident on application servers. Sip servers are configured to provide telephony services, and process call event information. Because vendors have developed their own custom SEP application programs, call events and telephony services are processed by each vendor's application server in a proprietary way. Unfortunately, when a network includes network elements provided by a multiplicity of vendors, it becomes necessary to accommodate a variety of proprietary interfaces that enable the devices to transmit and receive network transaction data. By way of example, transaction data may include call event information, billing information, monitoring information, error data, fraud prevention data, timeout data and any other data that must be tracked by the network.
What is needed is a platform independent method for capturing transaction data in a uniform manner. Preferably, the system and method will be extensible, providing embedded information that will enable a receiving computer to read the generic, uniformly formatted records without needing to accommodate any proprietary interface.
The present invention relates to a platform independent method for capturing transaction data and other information in a uniform manner. The method and system of the present invention is extensible, producing generic, umformly formatted records that can be read by a receiving computer without needing a special proprietary interface.
One aspect of the present invention is a method for recording transactions in a telecommunications network. The method includes creating an XML transaction detail file. At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction. The at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.
In another aspect, the present invention includes a computer-readable medium having stored thereon a data structure for recording transactions in a telecommunications network. The data structure includes: an XML declaration field, the XML declaration field defining the data structure as an XML file; a server identification field, the server identification field including an address of a server generating the XML file; and a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the data structure in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction. In another aspect, the present invention includes a telecommunications network. The network includes at least one telecommunications apparatus configured to perform a telecommunications transaction. At least one S P-server is coupled to the at least one telecommunications apparatus. The at least one SP-server is configured to create an XML transaction detail file, process the telecommunications transaction, and store at least one transaction detail record in the XML transaction detail file. The at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.
In another aspect, the present invention includes a computer-readable medium having stored thereon computer-executable instructions for performing a method for recording transactions in a telecommunications network. The method includes creating an XML transaction detail file. The XML transaction detail file is active for a predetermined period of time. At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction. The at least one transaction detail record includes transaction data corresponding to the telecommunications transaction. Additional features and advantages of the invention will be set forth in the detailed description which follows, and in part will be readily apparent to those skilled in the art from that description or recognized by practicing the invention as described herein, including the detailed description which follows, the claims, as well as the appended drawings.
It is to be understood that both the foregoing general description and the following detailed description are merely exemplary of the invention, and are intended to provide an overview or framework for understanding the nature and character of the invention as it is claimed. The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The drawings illustrate various embodiments of the invention, and together with the description serve to explain the principles and operation of the invention.
Figure 1 is a block diagram of an EP telecommunications network in accordance with one embodiment of the present invention; and
Figure 2 is a chart showing a method for managing telecommunications transactions in accordance with another embodiment of the present invention. Reference will now be made in detail to the present exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. An exemplary embodiment of the network of the present invention is shown in Figure 1 , and is designated generally throughout by reference numeral 10.
In accordance with the invention, the present invention includes a method for recording transactions in a telecommunications network. The method includes creating an XML transaction detail file. At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction. The at least one transaction detail record includes transaction data corresponding to the telecommunications transaction. The present invention provides a platform independent method for capturing transaction data and other information in a uniform manner. The system and method of the present invention is extensible, providing embedded information in generic, uniformly formatted transaction detail records that can be read by a receiving computer without needing a special proprietary interface.
As embodied herein, and depicted in Figure 1, a block diagram of an EP telecommunications network 10 in accordance with one embodiment of the present invention is disclosed. Telecommunications network 10 includes IP network 100, coupled to the Public Switched Telephone Network (PSTN) 20, Internet 30, a customer PBX 40, SEP phones 50, and SIP-clients 52. EP network 100 includes IP network backbone 120. Backbone 120 is coupled to a number of SEP elements that support voice services, including SEP proxy server 102, redirect server (RS) 104, SEP conferencing server 106, voice mail server 108, Operational Support Systems (OSS) 110, Dedicated Access Line (DAL) gateway 112, network gateway 114, ENCP gateway 116, and enterprise gateway 118. Network backbone 120 is also directly coupled to Internet 30, SEP phones 50, and SEP Clients 52. Although the present invention is discussed with respect to the Session Initiation Protocol (SEP) and an Internet Protocol (EP)-based network, those of ordinary skill in the art will recognize that the present invention is equally applicable to other telecommunication networks and protocols. P network 100 may be of any suitable type, but there is shown by way of 'example a network having a layered architecture. The layered nature of the architecture provides protocol separation and independence, whereby one protocol can be exchanged or modified without affecting the other higher layer or lower layer protocols. It is advantageous that the development of these protocols can occur concurrently and independently. The foundation of the layered architecture is the Internet Protocol (EP) layer. The EP layer provides a connectionless data delivery service that operates on a "best effort" basis; that is, no guarantees of packet delivery are made. A TCP (Transmission Control Protocol) layer is disposed above the EP layer. The TCP layer provides a connection-oriented protocol that ensures reliable delivery of the IP packets, in part, by performing sequencing functions. This sequencing function reorders any EP packets that arrive out of sequence. In another embodiment, the UDP (User Datagram Protocol) is employed instead of TCP. The User Datagram Protocol provides a connectionless service that utilizes the IP protocol to send a data unit, known as a datagram. Unlike TCP, UDP does not provide sequencing of packets. It relies on the higher layer protocols to sort the arriving packets. UDP is preferable over TCP when the data units are small, which saves processing time because of the nii imal reassembly time. One of ordinary skill in the art will recognize that embodiments of the present invention can be practiced using either TCP or UDP, as well as other equivalent protocols.
A telephony application layer is disposed over the TCP layer. In one embodiment, the Session Initiation Protocol (SEP) is employed. SEP is an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. SEP is also a client-server protocol wherein servers respond to requests generated by clients. A detailed discussion of SEP and its call control services are described in IETF RFC 2543 and EETF Internet Draft "SIP Call Control Services", June 17, 1999. ' Those of ordinary skill in the art will recognize that application-layer protocols other than SEP ' may be employed, including the H.323 protocol.
Finally, the Session Description Protocol (SDP) is disposed above SEP in the layered architecture. SDP provides information about media streams in the multimedia sessions, permitting the recipients of the session description to participate in the session.
EP network backbone 120 may be of any suitable type, but there is shown by way of example a network that includes a nationwide high speed network that operates at 622MB/sec (OC-12). Backbone 104 employs advanced packet switching technology commonly known as the Asynchronous Transfer Mode (ATM). Backbone 120 also utilizes a fiber-optic transmission technology referred to as the Synchronous Optical Network (SONET). The combination of ATM and SONET enables high speed, high capacity voice, data, and video signals to be combined and transmitted on demand. The high speed of backbone 120 is achieved by connecting Internet Protocol through the ATM switching matrix, and running this combination on the SONET network.
INCP 116 is an Intelligent Network Control Point that is accessed by RS 104 to obtain dial plan information for existing private network customers. INCP 116 is an additional database that may be. queried by RS 104 to route specific private calls. INCP 116 may also be accessed by SPS 102.
PSTN 160 is, by way of example, a circuit switched network employing Signaling System No. 7 (SS7). Plain-Old-Telephone-Service (POTS) telephone 22 maybe any suitable telephone set currently in use or on the market. Enterprise gateway 118 may be of any suitable type. In the example depicted in
Figure 1, enterprise gateway 118 is coupled to PBX 40. Those of ordinary skill in the art will recognize that enterprise gateway 118 may also couple network 100 to other enterprise networks, such as LANs and or WANs. Referring back to Figure 1, PBX 40 includes trunks or lines for PBX phones 42. Enterprise gateway 118 provides the interface between packet switched EP network 100 and the signaling employed by PBX 40. For example, enterprise gateway 118 may use Integrated Digital Services Network (ISDN), Circuit Associated Signaling (CAS), or other PBX interfaces (e.g., European Telecommunications Standards Institute (ETSI) PRE R2) to interface with PBX 40.
DAL gateway 112 is a system configured to support private traffic between EP locations and non-EP locations. DAL gateway 112 may be optionally employed in network 100.
Network gateway 114 is an SS7 (Signaling System 7)/C7-to-SEP Gateway. This provides users with the ability to place calls between locations within EP network 100 and locations within PSTN 20. For example, network gateway 114 is configured to provide access to a voice switch (not shown), such as a Class 3 switch for domestic call processing, or a Class 5 switch for long-haul and/or international connections.
SEP phones 50, and SEP-client devices 52, may be of any suitable type provided that they conform to the standards promulgated in EETF 2543. SEP phones 50 have a 10-key dial pad similar to traditional phones. SEP URLs, which include PSTN 20 numbers, can be entered using the keypad or retrieved from a speed dial directory. To place a call, digits are entered using the dial pad. The entered digits are-collected by the phone. When the "Dial" button is pressed, the call is initiated. SEP phones 50 ring similar to traditional phones when receiving an incoming call. SEP phones 50 may take the form of standalone devices - e.g., a SEP phone may be configured to function and appear like a Plain Old Telephone Service (POTS) telephone set. On the other hand, SEP client 52 is a software client that runs, for example, on a personal computer (PC) or laptop. From a signaling perspective, SIP-devices 50 and 52 are very similar, if not identical, in some cases.
At this point, the various SEP-servers disposed in network 100 will be described in more detail. Each type of server in network 100 has a critical role in recording and managing the various transactions supported by network 100.
Referring back to Figure 1, SEP-proxy server (SPS) conforms with SEP standards detailed per EETF RFC 2543. SPS 102 functions as both a server and a client for the purpose of making requests on behalf of other clients. SPS 102 may service a request directly or pass it on to another server. SPS 102 may also rewrite a message before forwarding it. SPS 102 is configured to create a transaction detail file in XML format to record transaction data processed by SPS 102. The transaction detail file is populated with transaction detail records(TDR). Each TDR records a transaction such as a SEP call-event (INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER, etc.), or any of the other events described above, such as errors, or timeouts. SPS 102 includes an XML processor module that is called by
SPS 102 application software to create the XML transaction detail file. The XML processor module may also be called upon to read XML documents, e.g., to provide access to the content and structure of an XML file. The format of the XML transaction detail file is shown in detail in Table I. Table 1 SIP Service Transaction Detail File Structure-Network Server
Figure imgf000009_0001
Figure imgf000010_0001
Figure imgf000011_0001
Authentication <auth_res>text</auth_res> One per Result Authentication
This is a text field that indicates the results of authentication if it was performed. If authentication was not performed, this field will not be present.
The possible values are as follows:
"Pass-Trusted Entity"
"Pass-Authenticated"
"Pass-Non Trusted User"
"Fail-Entity Disabled"
"Fail-System Failure"
"Challenge-User information not found"
"Challenge-Authentication information mismatch"
"Challenge-No local Pending Challenge or Auth Cache Record"
"Challenge-Expired Pending Challenge"
"Challenge-Expired Auth Cache"
Authentication </auth> Optional field - if - End Delimiter present, one per Tdr
Used to define the end of the Authentication fields withing Record a Tdr Record.
Response <response> Optional field - if present one per Tdr
A response contains the information about any SIP record Response that is either sent or received by the NS. NOTE: Responses received from the RS or AUS are not recorded.
Received-from <received-from>AA.BB.CC.DD : port</received-from> One Received-from
(e.g. 166.23.44.157 : 5060) element per
Response
The IP Address that the Response message was received from if the Response was received at the NS, where AA, BB, CC, DD can be digits 0 through 255 and port can be a number 1024 through 65535.
Figure imgf000013_0001
Event <event>text</event>
Used to record events other than messages that caused actions at the NS during a transaction.
The possible values are as follows:
"TCP Connection to OUA lost"
"TCP Connection to TUA" AA.BB.CC.DD:EE "lost" - where AA.BB.CC.DD is the IP address and EE is the port number of the TUA
"TCP Connection to TUA" AA.BB.CC.DD:EE "could not be established" - where AA.BB.CC.DD is the IP address and EE is the port number of the TUA
"RS Timeout" for AA.BB.CC.DD.ΕE - where AA.BB.CC.DD is the IP Address and EE is the port number of the RS that timed out
"UA Invite Timeout for TUA" AA.BB.CC.DD:EE - where AA.BB.CCDD is the IP Address and EE is the port number of the TUA
"UA Non-Invite Timeout for TUA" AA.BB.CC.DD:EE - where AA.BB.CC.DD is the IP Address and EE is the port number of the TUA
"ACK Timeout"
"Txn Clear Timeout"
"Expires Timeout"
"AuS Timeout" for AA.BB.CC.DD'ΕE - where AA.BB.CC.DD is the IP Address and EE is the port number of the AUS that timed out
"Ring Timeout for TUA" AA.BB.CC.DD :EE - where AA.BB.CC.DD is the IP Address and EE is the port number of the TUA
"487 Timeout for TUA" AA.BB.CC.DD :EE - where AA.BB.CC.DD is the IP Address and EE is the port number of the TUA
TDR Data End </tdr_record> Multiple Tdr Delimiter Records may
Used to define the end of the TDR Record fields within a be in one TDR TDR File file (or none if timer period expires with no events processed)
Figure imgf000015_0001
Voice mail server (VMS) 108 is a SEP -server that provides voice mail services. Users of the EP network 100 are provided with the capability to integrate voicemail services based upon SEP . Calls are routed to the voice mail system 108 by SPS 102 and RS 104 for certain calls, such as those that indicate a Busy or Ring No Answer condition. Calls to voice mail can also occur as a Find-Me/Follow-Me termination option, or as an Unconditional Call Forward option selected by the user. Calls by the user to log in and retrieve messages are routed to VMS 108 as a SEP endpoint. A voice mail address can be entered for any destination address in RS 104. For instance, the Call Forwarding Unconditional address or Find-Me address, etc., can be the SEP URL of a voice mail account. SEP enabled VMS 108 supports all alphanumeric SEP URLs, Headers, Request, Methods and Status codes (e.g., per IETF RFC 2543). VMS 108 supports SUBSCRIBE, NOTIFY, and Message Waiting Indicator (MWI) messages. VMS 108 may restrict access to the system through a variety of ways. Access may be secured through private access code. The access code may be supplied in the SEP INVITE message or through DTMF. VMS 108 may reject messages based on the EP address of the originating server. In other words, if the me"ssage is coming from a server that is not trusted, then VMS 108 may reject the message. VMS 108 is also configured to create a transaction detail file in XML format to thereby record transaction data corresponding to all network transactions processed by VMS 108. Because the format of the VMS XML transaction detail file is very similar, to the SPS 102 XML transaction detail file, it will not be repeated here.
SEP conferencing server (SCS) 106 is a centralized SEP-conference server configured to provide audio conferencing capabilities. SCS 106 support G.711
(RTP/AVT 0), as well as other codecs. SCS 106 may specify two modes of operation. Under a Reserved mode, the users are required to reserve a bridge ahead of time. An Instant Conferencing mode refers to the ability to set-up a conference as needed without any need for advance reservation, allowing ad-hoc set-up of conferences as well permitting client based conferences to migrate to a bridge. Conference access is secured through an access code. Participants joining the bridge can send their access code via the SEP Invite message. POTS telephone users can enter through DTMF depending on the support for DTMF at the gateway. An audible tone may be played to announce each participant as they join the bridge. The system supports a coordinator /operator initiated conference, wherein the operator dials-out to each of the conference participants and brings them into the conference. The conference operator can enter and announce the name of the participants into the conference. The conference coordinator can notify the participants of the time and date for the call. The operators may be able to put parties On and Off Hold. Music On Hold is supported, whereby the parties on Hold are provided with music.
SCS 106 also permits private conferencing (i.e., sub-conferencing), wherein designated conference callers may confer privately within a conference call and then be returned to the main call. Calls from PSTN 20 may be forwarded to SCS 106 by network gateway 114. From the perspective of SCS 106, a SIP originated call is not processed differently than a non-SEP call because network gateway 114'is able to translate the called number to the conference URL. However, SCS 106 is able to validate the caller by prompting for passwords and validating the password entered as DTMF digits. As an alternate to password collection through DTMF, SCS 106 may support authentication using SEP. In this scenario, the SEP INVITE message carries additional user parameters, such as username/password combination that may be used by SCS 106 to validate the user. Further, conferencing system 106 supports web based provisioning by the users. SCS 106 interfaces with the OSS 110 for provisioning, alarming and reporting. The provisioning and reporting interface of the OSS 110 assists with a number of conferencing functionalities, such as the capability to Setup, Modify and Delete conferences. The administrator or moderator of the conference is able to specify the number of attendees to a conference, as well as specify duration of the conference, date and time-by-time zone, and name of reserved conference.
SCS 106 is configured to create a transaction detail file in XML format to thereby record transaction data corresponding to all the above described transactions processed by conferencing server 106. Because the format of the SCS 106 XML transaction detail file is similar to the SPS 102 XML transaction detail file, it will not 'be repeated.
RS 104 is a SIP redirect server that conforms with SEP standards detailed per IETF RFC 2543. RS 104 accepts SEP messages, maps the address into one or more new addresses, and returns these addresses to the client, which could be SPS 102. RS 104 does not initiate its own SEP requests, and RS 104 does not accept calls. RS 104 is essentially, a location server wherein information about possible terminating locations can be obtained. RS 104 also serves as a repository for end user information enabling address validation, feature status, and real-time subscriber feature configuration. RS 104 may also be used to store configuration information.
RS 104 is also configured to create a transaction detail file in XML format to thereby record transaction data corresponding to all SEP transactions, timeouts and errors processed by RS 104. The transaction detail file includes transaction detail records used to record network transactions processed by RS 104. RS 104 includes an XML processor module that is called by RS 104 application software module to create the XML transaction detail file. The XML processor module may also be called to read an XML file. Because RS 104 has a different function in the management of network 100, its XML transaction detail file is substantially different than the SPS XML transaction detail file. The format of the RS XML transaction detail file is shown in detail in Table II.
Table II SIP Services Transaction Detail File Structure - Redirect Server
Figure imgf000017_0001
Figure imgf000018_0001
Figure imgf000019_0001
Figure imgf000020_0001
Figure imgf000021_0001
Figure imgf000022_0001
Figure imgf000023_0001
Figure imgf000024_0001
Figure imgf000025_0001
Figure imgf000026_0001
Figure imgf000027_0001
Figure imgf000028_0001
Figure imgf000029_0001
Figure imgf000030_0001
Figure imgf000031_0001
Figure imgf000032_0001
Referring back to Figure 1, OSS 110 is also a critical system for managing network 100. OSS 110 supports the establishment, provisioning, data collection, and billing of the services of the system 100. OSS 110 is a distributed computing system that includes customer management, account management, billing, network facilities provisioning, and network data collection functionality. All of the XML transaction detail files generated by the above described servers SPS 102, RS 104, SCS 106, and VMS 108, are transmitted to OSS 110 using the XML transaction detail files described above. The XML transaction detail files are used by OSS .110 for a variety of network functions including, but not limited to, network management, billing, and record keeping. Thus, the present invention provides a platform independent method for capturing transaction data in a uniform manner. The present invention is extensible, providing embedded information that will enable any receiving computer to read the generic, uniformly formatted XML files without needing any proprietary interface. In one embodiment, the OSS computing system is based on technology provided by SUN Microsystems, the databases employed by the computing system are based on technology provided by ORACLE. OSS 110 provides and controls access to customer accounts. Users may utilize a web page to monitor service, login to their account, and manage certain elements permitted by user profiles. The account management system allows network personnel to establish, maintain, or deactivate customer accounts. In one embodiment, customer information is viewed via a web interface. The billing system processes customer event records, the customer pricing plan data, adjustments, taxation and other data in the preparation of customer invoices. The network facilities provisioning system provides the information required by network engineers to ensure that the appropriate hardware and software is in place to provide service. This may involve the creation of a customer profile, and the reconfiguration of SPS 102, RS 104, or other network elements. Network provisioning may also require the placement of hardware plug-in devices used in backbone 120.
A process management/work flow system serves as the core of OSS 110. The software is a Common Object Request Broker Architecture (CORBA) based publish- and-subscribe messaging middleware that provides graphical process automation, data transformation, event management and flexible connectors to transact with interfacing applications. This middleware architecture software fulfills the function of integrating all OSS 110 components and may provide hooks to non-OSS components using designated standard interfaces. As embodied herein, and depicted in Figure 2, a chart showing a method for recording telecommunications transaction data in accordance with the present invention is disclosed. The method described herein is equally applicable to SPS 102, RS 104, . SCS 106, and VMS 108. In step 200, the XML detail file is created. If the file is being created in RS 104, XML detail file will have the form depicted in Table Ef, otherwise, the XML detail file will be of the form, or similar to the form, shown in Table I. Each XML file is active for a predetermined period of time. Thus, once the XML file is created, the server initializes a timer to track elapsed time. For example, OSS 110 may direct each server to keep each XML detail file active for one day, or one hour, as the case may be. In step 204, if a transaction is detected, the server analyzes the transaction and performs an appropriate action. For example, SPS 102 (See Figure 1) may receive an ENVETE message from SEP-phone 50, requesting a session with a user at POTS telephone 22. In processing the INVITE message, SPS 102 may perform and coordinate a plurality of transactions required to set up the session between SEP phone 50 and POTS telephone 22. In doing so, SPS 102 creates a transaction detail record (TDR) for each transaction in the call set-up process. In step 210, the TDRs are written into the XML file. On the other hand, if there are no transactions generated in the predetermined time period, no records are written into the file. In this case, only the header information in the XML file is transmitted to OSS 110.
Once the timer has elapsed, the server transmits the XML file to OSS 110. After the XML file is transmitted, a new file is created and the process repeats. If the timer has not elapsed, the server waits for additional transactions to process. En step 216, the server may suspend operations for any number of reasons. For example, if the server requires maintenance and is off-line, it is unnecessary to continue to monitor and record network transactions.
Those of ordinary skill in the art will recognize that the use of XML transaction detail files in accordance with the present invention can be employed for any events occurring within network 10. Calls placed between all or any combinations of SEP- phones, enterprise gateways, network gateways, DAL gateways, INCP gateways, SEP- voice ail servers, and SIP conferencing servers may employ the present mvention. Those of ordinary skill in the art will also recognize that the present invention can be employed using any suitable type of transport network. Further, the present invention is applicable to any type of session that may be established including, but not limited to, telephony, video, audio, instant messaging, and etc. It is also contemplated that the present invention may be employed for billing, monitoring, management, or for any of a wide variety of services performed by the network. It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Claims

What is claimed is:
1. A method for recording transactions in a telecommunications network, the method comprising: creating an XML transaction detail file; and storing at least one transaction detail record in the XML transaction detail file in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
2. The method of claim 1, wherein the XML transaction detail file is active for a predetermined period of time.
3. The method of claim 2, further comprising: closing the XML transaction detail file when the predetermined period of time expires; creating a second XML transaction detail file, the second XML transaction detail file being active for a second predetermined period of time; and repeating the steps of closing and creating for a number of times as directed by a network management system.
4. The method of claim 1, wherein the XML transaction detail file comprises: an XML declaration field, the XML declaration field defining the data structure as an XML file; a server identification field, the server identification field including an EP address of a server generating the XML file; and a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the data structure in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
5. The method of claim 1, wherein the telecommunications transaction is conducted between a telecommunications apparatus and a SEP-server.
6. The method of claim 5, wherein the telecommunications apparatus includes a telephone.
7. The method of claim 5, wherein the telecommunications apparatus includes a SEP- device.
8. The method of claim 7, wherem the SIP-device is a telephone.
9. The method of claim 7, wherein the SEP-device is a computer.
10. The method of claim 5, wherem the telecommunications apparatus includes a gateway.
11. The method of claim 5, wherein the SEP-server is a proxy server.
12. The method of claim 5, wherein the SEP-server is a conferencing server.
13. The method of claim 5, wherein the SEP-server is a voice mail server.
14. The method of claim 5, wherein the telecommunications apparatus is a proxy server and the SEP-server is a redirect server.
15. The method of claim 1, wherein the telecommunications transaction includes a SEP- fNVITE message.
16. The method of claim 1, wherein the telecommunications transaction includes a SEP-ACK message.
17. The method of claim 1, wherein the telecommunications transaction includes a SEP- OPTIONS message.
18. The method of claim 1, wherein the telecommunications transaction includes a SEP- BYE message.
19. The method of claim 1, wherein the telecommunications transaction includes a SEP- CANCEL message.
20. The method of claim 1, wherein the telecommunications transaction includes a SEP- REGISTER message.
21. The method of claim 1 , wherein the telecommunications transaction includes a billing transaction.
22. The method of claim 1, wherein the telecommunications transaction includes a monitoring transaction.
23. The method of claim 1 , wherein the telecommunications transaction includes a performance measurement transaction.
24. A computer-readable medium having stored thereon a data structure for recording transactions in a telecommunications network, the data structure comprising: an XML declaration field, the XML declaration field defining the data structure as an XML file; a server identification field, the server identification field including an EP address of a server generating the XML fjle; and a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the data structure in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
25. The data structure of claim 24, further comprising a time/date field for indicating the time and date that the XML file was opened.
26. The data structure of claim 24, wherein the data structure is an XML transaction detail file created by an IP network server.
27. The data structure of claim 26, wherein the XML transaction detail file is active for a predetermined period of time.
28. The data structure of claim 26, wherein the server identification field includes the EP address of a proxy server.
29. The data structure of claim 26, wherein the server identification field includes the EP address of a conferencing server.
30. The data structure of claim 26, wherein the server identification field includes the EP address of a voice mail server.
31. The data structure of claim 26, wherein the at least one transaction detail record includes a plurality of transaction detail records.
32. The data structure of claim 31, wherein the at least one transaction detail record includes a correlation identification field for correlating each transaction detail record of the plurality of transaction detail records corresponding to a particular transaction.
33. The data structure of claim 26, wherein each transaction detail record includes a time/date field indicating when the transaction detail record was made.
34. The data structure of claim 26, wherein each transaction detail record includes a request section including information about any SEP request that is either sent or received by the EP network server.
35. The data structure of claim 34, wherein the request section includes a received-from field indicating the EP address of the sender of the SEP-request.
36. The data structure of claim 34, wherein the request section includes a sent-to field indicating the EP address of the addressee of the SEP-request.
37. The data structure of claim 34, wherein the request section includes a message field having all data associated with the request.
38. The data structure of claim 26, wherein each transaction detail record includes an authentication section, the authentication section indicates whether an authentication was performed, why the authentication was performed, and the result of the authentication.
39. The data structure of claim 26, wherein each transaction detail record includes a response section including information about any SEP response that is either sent or received by the EP network server.
40. The data structure of claim 39, wherein the response section includes a received- from field indicating the EP address of the sender of the SEP- response.
41. The data structure of claim 39, wherein the response section includes a sent-to field indicating the EP address of the addressee of the SEP- response.
42. The data structure of claim 39, wherein the response section includes a message field having all data associated with the response.
43. The data structure of claim 26, wherein each transaction detail record includes an event section for recording at least one event, other than messages, that occurred at the
EP network server.
44. The data structure of claim 43, wherein the at least one event includes a timeout event.
45. The data structure of claim 43, wherein the at least one event includes an error event.
46. The data structure of claim 24, wherein the data structure is an XML transaction detail file created by a SEP redirect server.
47. The data structure of claim 46, wherein the XML transaction detail file is active for a predetermined period of time.
48. The data structure of claim 46, wherein the server identification field includes the EP address of a redirect server.
49. The data structure of claim 46, wherein the at least one transaction detail record includes a plurality of transaction detail records.
50. The data structure of claim 49, wherein the at least one transaction detail record includes a correlation identification field for correlating each transaction detail record of the plurality of transaction detail records corresponding to a particular transaction.
51. The data structure of claim 46, wherein each transaction detail record includes a time/date field indicating when the transaction detail record was made.
52. The data structure of claim 46, wherein each transaction detail record includes a request section including information about any SEP request that is received by the SP redirect server from a SEP network server.
53. The data structure of claim 52, wherein the request section includes a received-from field indicating the EP address of an original sender of the SEP-request.
54. The data structure of claim 52, wherein the request section includes a message field having all data associated with the request.
55. The data structure of claim 46, wherein each transaction detail record includes a response section including information about any SEP response that is received by the SEP redirect server from a SEP network server.
56. The data structure of claim 55, wherein the response section includes a sent-to field indicating the IP address of the addressee of the SEP- response.
57. The data structure of claim 55, wherein the response section includes a message field having all data associated with the response.
58. The data structure of claim 46, wherein each transaction detail record includes a features section that records at least one feature executed by the SEP redirect server during the transaction.
59. The data structure of claim 58, wherein the features section includes at least one recursive routing field.
60. The data structure of claim 58, wherein the features section includes at least one originating call validation field, the at least one originating call validation field including data relating to the validation of a call originator, and data relating to the call originator.
61. The data structure of claim 58, wherein the features section includes anon trusted terminating call field for recording whether a non-trusted call was allowed.
62. The data structure of claim 58, wherein the features section includes at least one terminating call validation field, the at least one terminating call validation field including data relating to the validation of a subscriber being called, and data relating to the subscriber.
63. The data structure of claim 58, wherein the features section includes at least one originating call screening field for recording information when a call screening feature is executed.
64. The data structure of claim 58, wherein the features section includes at least one terminating call screening field for recording information when a terminating call screening feature is executed.
65. The data structure of claim 58, wherein the features section includes at least one call forwarding field for recording information when at least one call forwarding feature is executed.
66. The data structure of claim 58, wherein the features section includes at least one find-me field for recording information when a find-me feature is executed.
67. The data structure of claim 58, wherein the features section includes at least one registered address list field for recording information when a call is redirected to a list of registered addresses.
68. The data structure of claim 58, wherein the features section includes at least one default address field for recording information when the call is redirected to a default address in a subscriber's record.
69. The data structure of claim 46, wherein each transaction detail record includes at least one directory access protocol (DAP) field.
70. A telecommunications network, comprising: at least one telecommunications apparatus configured to perform a telecommunications transaction; and at least one SEP-server coupled to the at least one telecommunications apparatus, the at least one SEP-server being configured to create an XML transaction detail file, process the telecommunications transaction, and store at least one transaction detail record in the XML transaction detail file, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
71. The network of claim 70, wherein the telecommunications apparatus includes a SEP device.
72. The network of claim 71, wherein the SEP- device includes a telephone.
73. The network of claim 71 , wherein the SEP device includes a computer.
74. The network of claim 71, wherein the telecommunications apparatus includes a SEP proxy server and the at least one SEP-server includes a SEP redirect server.
75. The network of claim 71 , wherein the telecommunications apparatus includes a PBX.
76. The network of claim 71, wherein the telecommunications apparatus includes an enterprise gateway.
77. The network of claim 71, wherein the telecommunications apparatus includes a network gateway.
78. The network of claim 71, wherein the telecommunications apparatus includes a telephone.
79. The network of claim 71, wherein the at least one SEP-server includes a SEP proxy server.
80. The network of claim 71 , wherein the at least one SEP-server includes a SEP conferencing server.
81. The network of claim 71, wherein the at least one SEP-server includes a SEP voice mail server.
82. A computer-readable medium having stored thereon computer-executable instructions for performing a method for recording transactions in a telecommunications network, the method comprising: creating an XML transaction detail file, the XML transaction detail file being active for a predetermined period of time; storing at least one transaction detail record in the XML transaction detail file in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
83. The method of claim 82, further comprising: closing the XML transaction detail file when the predetermined period of time expires; creating a second XML transaction detail file, the second XML transaction detail file being active for a second predetermined period of time; and repeating the steps of closing and creating for a number of times as directed by a network management system.
84. The method of claim 82, wherein the XML transaction detail file comprises: an XML declaration field, the XML declaration field defining the data structure as an XML file; a server identification field, the server identification field including an EP address of a server generating the XML file; and a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the data structure in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
85. The method of claim 82, wherein the telecommunications transaction includes a SIP-INVITE message.
86. The method of claim 82, wherein the telecommumcations transaction includes a SEP-ACK message.
87. The method of claim 82, wherein the telecommunications transaction includes a SEP-OPTIONS message.
88. The method of claim 82, wherein the telecommunications transaction includes a SEP-BYE message.
89. The method of claim 82, wherein the telecommumcations transaction includes a SEP-CANCEL message.
90. The method of claim 82, wherein the telecommumcations transaction includes a SEP-REGISTER message.
91. The method of claim 82, wherein the telecommunications transaction includes a billing transaction.
92. The method of claim 82, wherein the telecommunications transaction includes a monitoring transaction.
93. The method of claim 82, wherein the telecommunications transaction includes a performance measurement transaction.
PCT/US2002/008578 2001-03-20 2002-03-20 Xml based transaction detail records WO2002075605A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP02721497A EP1381975A1 (en) 2001-03-20 2002-03-20 Xml based transaction detail records
BR0208230-6A BR0208230A (en) 2001-03-20 2002-03-20 Xml-based transaction detail records
CA002441323A CA2441323A1 (en) 2001-03-20 2002-03-20 Xml based transaction detail records
MXPA03008508A MXPA03008508A (en) 2001-03-20 2002-03-20 Xml based transaction detail records.
JP2002574541A JP2004532547A (en) 2001-03-20 2002-03-20 Processing detail record based on XML

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US27695401P 2001-03-20 2001-03-20
US27695501P 2001-03-20 2001-03-20
US27695301P 2001-03-20 2001-03-20
US27692301P 2001-03-20 2001-03-20
US60/276,953 2001-03-20
US60/276,954 2001-03-20
US60/276,923 2001-03-20
US60/276,955 2001-03-20
US10/099,323 US7945592B2 (en) 2001-03-20 2002-03-15 XML based transaction detail records
US10/099,323 2002-03-15

Publications (2)

Publication Number Publication Date
WO2002075605A1 WO2002075605A1 (en) 2002-09-26
WO2002075605A9 true WO2002075605A9 (en) 2003-01-23

Family

ID=27536934

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/008578 WO2002075605A1 (en) 2001-03-20 2002-03-20 Xml based transaction detail records

Country Status (8)

Country Link
US (3) US7945592B2 (en)
EP (1) EP1381975A1 (en)
JP (1) JP2004532547A (en)
CN (1) CN1509448A (en)
BR (1) BR0208230A (en)
CA (1) CA2441323A1 (en)
MX (1) MXPA03008508A (en)
WO (1) WO2002075605A1 (en)

Families Citing this family (88)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7243370B2 (en) * 2001-06-14 2007-07-10 Microsoft Corporation Method and system for integrating security mechanisms into session initiation protocol request messages for client-proxy authentication
GB0124261D0 (en) * 2001-10-09 2001-11-28 Nokia Corp Event related communications
US7240366B2 (en) 2002-05-17 2007-07-03 Microsoft Corporation End-to-end authentication of session initiation protocol messages using certificates
US6952697B1 (en) * 2002-06-21 2005-10-04 Trust Licensing, Llc Media validation system
US20040017791A1 (en) * 2002-07-23 2004-01-29 Pramodkumar Patel Network controlled call forwarding
US7084423B2 (en) 2002-08-12 2006-08-01 Acorn Technologies, Inc. Method for depinning the Fermi level of a semiconductor at an electrical junction and devices incorporating such junctions
US6833556B2 (en) 2002-08-12 2004-12-21 Acorn Technologies, Inc. Insulated gate field effect transistor having passivated schottky barriers to the channel
FR2848053B1 (en) 2002-11-29 2005-04-01 Streamwide METHOD FOR PROCESSING AUDIO DATA ON A NETWORK AND DEVICE FOR IMPLEMENTING SAID METHOD
KR100514196B1 (en) * 2003-02-14 2005-09-13 삼성전자주식회사 System and method for Controlling network address translation and session
KR100547115B1 (en) * 2003-05-23 2006-01-26 삼성전자주식회사 The method for transferring and recieving data between client and server by RDT message which extends SIP protocol, recording medium, system, user agent client, and user agent server thereof
JP2005159431A (en) * 2003-11-20 2005-06-16 Nec Infrontia Corp Signaling method, and server and gateway terminal
US8442227B1 (en) 2004-02-23 2013-05-14 Rockstar Consortium Us Lp Providing additional information with session requests
US20100299736A1 (en) * 2004-09-01 2010-11-25 Nortel Networks Limited Automated session admission
US7650347B2 (en) * 2004-10-01 2010-01-19 Computer Associates Think, Inc. System and method for job scheduling and distributing job scheduling
US8171474B2 (en) * 2004-10-01 2012-05-01 Serguei Mankovski System and method for managing, scheduling, controlling and monitoring execution of jobs by a job scheduler utilizing a publish/subscription interface
US10750327B2 (en) 2004-11-23 2020-08-18 Kodiak Networks Inc Method for multiplexing media streams to optimize network resource usage for push-to-talk-over-cellular service
US9913300B2 (en) 2011-12-14 2018-03-06 Kodiak Networks, Inc. Push-to-talk-over-cellular (PoC)
US10057105B2 (en) 2004-11-23 2018-08-21 Kodiak Networks, Inc. Architecture framework to realize push-to-X services using cloudbased storage services
US8498660B2 (en) * 2009-03-30 2013-07-30 Kodiak Networks, Inc. Enhanced group calling features for connected portfolio services in a wireless communications network
US8670760B2 (en) * 2008-01-24 2014-03-11 Kodiak Networks, Inc. Converged mobile-web communications solution
US9088876B2 (en) 2012-02-01 2015-07-21 Kodiak Networks, Inc. WiFi interworking solutions for push-to-talk-over-cellular (PoC)
US9485787B2 (en) 2005-05-24 2016-11-01 Kodiak Networks, Inc. Method to achieve a fully acknowledged mode communication (FAMC) in push-to-talk-over-cellular (PoC)
US9137646B2 (en) 2004-11-23 2015-09-15 Kodiak Networks, Inc. Method and framework to detect service users in an insufficient wireless radio coverage network and to improve a service delivery experience by guaranteed presence
US10111055B2 (en) 2004-11-23 2018-10-23 Kodiak Networks, Inc. Optimized methods for large group calling using unicast and multicast transport bearer for PoC
US10178513B2 (en) 2004-11-23 2019-01-08 Kodiak Networks, Inc. Relay-mode and direct-mode operations for push-to-talk-over-cellular (PoC) using WiFi-technologies
US10116691B2 (en) 2004-11-23 2018-10-30 Kodiak Networks, Inc. VoIP denial-of-service protection mechanisms from attack
US10367863B2 (en) 2004-11-23 2019-07-30 Kodiak Networks Inc. Method for providing dynamic quality of service for push-to-talk service
US7895158B2 (en) * 2004-12-27 2011-02-22 Solace Systems Inc. Data logging in content routed networks
US20070118503A1 (en) * 2005-11-22 2007-05-24 Connelly Stephen P Methods and systems for providing data to a database
US8689317B2 (en) * 2005-12-19 2014-04-01 Level 3 Communications, Llc Providing SIP signaling data for third party surveillance
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
US8699384B2 (en) * 2006-03-15 2014-04-15 American Teleconferencing Services, Ltd. VOIP conferencing
US9118507B2 (en) * 2006-06-07 2015-08-25 Cisco Technology, Inc. Techniques for message waiting indication support across different protocols
WO2009018578A2 (en) * 2007-08-02 2009-02-05 Tekelec Methods, systems, and computer readable media for collecting data from network traffic traversing high speed internet protocol (ip) communication links
KR100919219B1 (en) * 2007-10-10 2009-09-28 주식회사 스파이어테크놀로지 Method and apparatus for providing signaling message mapping/tracing service in wcdma circuit switched network
EP2204037A1 (en) * 2007-10-25 2010-07-07 Kodiak Networks, Inc. Connected portfolio services for a wireless communications network
WO2010048217A1 (en) * 2008-10-20 2010-04-29 Kodiak Networks, Inc. Hybrid push-to-talk for mobile phone networks
US8266477B2 (en) * 2009-01-09 2012-09-11 Ca, Inc. System and method for modifying execution of scripts for a job scheduler using deontic logic
WO2010082803A2 (en) * 2009-01-19 2010-07-22 Lg Electronics Inc. Method for delivering message based on cpm service and server thereof
US8391884B2 (en) * 2009-03-26 2013-03-05 Andrew Llc System and method for managing created location contexts in a location server
US9185226B2 (en) * 2009-08-13 2015-11-10 Verizon Patent And Licensing Inc. Voicemail server monitoring/reporting via aggregated data
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
US8982735B2 (en) * 2010-02-25 2015-03-17 Genesys Telecommunications Laboratories, Inc. Proxy media service for digital telephony
US20110218841A1 (en) * 2010-03-05 2011-09-08 International Business Machines Corporation Back office process monitoring and analysis
US9992032B2 (en) * 2011-05-09 2018-06-05 Samsung Electronics Co., Ltd Method and system for managing telephony services in a universal plug and play home network environment
US8954542B2 (en) * 2011-06-14 2015-02-10 Avaya Inc. Method and system for transmitting and receiving configuration and registration information for session initiation protocol devices
US9131385B2 (en) 2012-06-13 2015-09-08 All Purpose Networks LLC Wireless network based sensor data collection, processing, storage, and distribution
US9084155B2 (en) 2012-06-13 2015-07-14 All Purpose Networks LLC Optimized broadband wireless network performance through base station application server
US9107094B2 (en) 2012-06-13 2015-08-11 All Purpose Networks LLC Methods and systems of an all purpose broadband network
US9125064B2 (en) 2012-06-13 2015-09-01 All Purpose Networks LLC Efficient reduction of inter-cell interference using RF agile beam forming techniques
US9031511B2 (en) 2012-06-13 2015-05-12 All Purpose Networks LLC Operational constraints in LTE FDD systems using RF agile beam forming techniques
US9179392B2 (en) 2012-06-13 2015-11-03 All Purpose Networks LLC Efficient delivery of real-time asynchronous services over a wireless network
US9084143B2 (en) 2012-06-13 2015-07-14 All Purpose Networks LLC Network migration queuing service in a wireless network
US9503927B2 (en) 2012-06-13 2016-11-22 All Purpose Networks LLC Multiple-use wireless network
US9144082B2 (en) 2012-06-13 2015-09-22 All Purpose Networks LLC Locating and tracking user equipment in the RF beam areas of an LTE wireless system employing agile beam forming techniques
US9179354B2 (en) 2012-06-13 2015-11-03 All Purpose Networks LLC Efficient delivery of real-time synchronous services over a wireless network
US9219541B2 (en) 2012-06-13 2015-12-22 All Purpose Networks LLC Baseband data transmission and reception in an LTE wireless base station employing periodically scanning RF beam forming techniques
US9137675B2 (en) 2012-06-13 2015-09-15 All Purpose Networks LLC Operational constraints in LTE TDD systems using RF agile beam forming techniques
US9094803B2 (en) * 2012-06-13 2015-07-28 All Purpose Networks LLC Wireless network based sensor data collection, processing, storage, and distribution
US8565689B1 (en) 2012-06-13 2013-10-22 All Purpose Networks LLC Optimized broadband wireless network performance through base station application server
US9125123B2 (en) 2012-06-13 2015-09-01 All Purpose Networks LLC Efficient delivery of real-time asynchronous services over a wireless network
US9144075B2 (en) 2012-06-13 2015-09-22 All Purpose Networks LLC Baseband data transmission and reception in an LTE wireless base station employing periodically scanning RF beam forming techniques
US9179352B2 (en) 2012-06-13 2015-11-03 All Purpose Networks LLC Efficient delivery of real-time synchronous services over a wireless network
US9882950B2 (en) 2012-06-13 2018-01-30 All Purpose Networks LLC Methods and systems of an all purpose broadband network
US8874506B2 (en) * 2012-09-10 2014-10-28 Oracle International Corporation Preventing database replication conflicts in a distributed environment
MX350027B (en) 2013-07-23 2017-08-23 Kodiak Networks Inc EFFECTIVE PRESENCE FOR PUSH-TO-TALK-OVER-CELLULAR (PoC) NETWORKS.
US9485132B2 (en) * 2014-05-08 2016-11-01 Dell Products, Lp Automated SAN network topological diagram and point-to-point cabling creation for customers environments
US9742818B2 (en) * 2014-12-10 2017-08-22 Oracle International Corporation Pushing events to web pages used for interaction with applications
US10362074B2 (en) 2015-02-03 2019-07-23 Kodiak Networks, Inc Session management and notification mechanisms for push-to-talk (PTT)
EP3292485B1 (en) 2015-05-07 2021-02-17 Kodiak Networks, Inc. System and method for data synchronization
US10110342B2 (en) 2015-10-06 2018-10-23 Kodiak Networks Inc. System and method for tuning PTT over LTE according to QoS parameters
EP3360353A4 (en) 2015-10-06 2019-09-11 Kodiak Networks, Inc. Ptt network with radio condition aware media packet aggregation scheme
GB2561722B (en) 2015-10-23 2021-10-20 Kodiak Networks Inc System and method for content messaging
WO2017185032A1 (en) 2016-04-22 2017-10-26 Kodiak Networks, Inc. System and method for push-to-talk (ptt) key one-touch calling
US9620611B1 (en) 2016-06-17 2017-04-11 Acorn Technology, Inc. MIS contact structure with metal oxide conductor
US10555370B2 (en) 2016-09-28 2020-02-04 Kodiak Networks, Inc. System and method for push-to-talk (PTT) in high latency networks
US10170627B2 (en) 2016-11-18 2019-01-01 Acorn Technologies, Inc. Nanowire transistor with source and drain induced by electrical contacts with negative schottky barrier height
US10257669B2 (en) 2016-12-01 2019-04-09 Kodiak Networks, Inc. PTX data analytic engine notifying group list of detected risk event
US10630529B2 (en) 2016-12-29 2020-04-21 Kodiak Networks, Inc. System and method for push-to-talk (PTT) in mobile edge computing (MEC)
US10341823B2 (en) 2016-12-30 2019-07-02 Kodiak Networks Inc. System and method for direct mode push to talk communication protocols
US11822133B2 (en) 2017-07-14 2023-11-21 Senko Advanced Components, Inc. Ultra-small form factor optical connector and adapter
US10281669B2 (en) 2017-07-14 2019-05-07 Senko Advance Components, Inc. Ultra-small form factor optical connectors
US10827019B2 (en) 2018-01-08 2020-11-03 All Purpose Networks, Inc. Publish-subscribe broker network overlay system
WO2019135830A1 (en) 2018-01-08 2019-07-11 All Purpose Networks, Inc. Internet of things system with efficient and secure communications network
CN111033339B (en) 2018-03-28 2023-09-19 扇港元器件股份有限公司 Optical fiber connector
CN112088327A (en) 2018-07-15 2020-12-15 扇港元器件股份有限公司 Ultra-small optical connector and adapter
US11467354B2 (en) 2019-07-23 2022-10-11 Senko Advanced Components, Inc. Ultra-small form factor receptacle for receiving a fiber optic connector opposing a ferrule assembly
US10986555B1 (en) * 2019-09-25 2021-04-20 Dsbm, Llc Analog and digital communication system for interfacing plain old telephone service devices with a network

Family Cites Families (67)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4979207A (en) * 1990-02-01 1990-12-18 Motorola, Inc. Method of processing cellular telephone call detail data for billing multi-line customers for cellular telephone services
US5579379A (en) 1992-03-05 1996-11-26 Bell Atlantic Network Services, Inc. Personal communications service having a calling party pays capability
US5565316A (en) * 1992-10-09 1996-10-15 Educational Testing Service System and method for computer based testing
US5590181A (en) * 1993-10-15 1996-12-31 Link Usa Corporation Call-processing system and method
US7215663B1 (en) * 1996-01-16 2007-05-08 C2 Global Technologies, Inc. Private IP communication network architecture
EP0890255B1 (en) 1996-03-29 2004-08-04 Azure Solutions Limited Fraud monitoring in a telecommunications network
US5812668A (en) * 1996-06-17 1998-09-22 Verifone, Inc. System, method and article of manufacture for verifying the operation of a remote transaction clearance system utilizing a multichannel, extensible, flexible architecture
US5867495A (en) 1996-11-18 1999-02-02 Mci Communications Corporations System, method and article of manufacture for communications utilizing calling, plans in a hybrid network
US6335927B1 (en) * 1996-11-18 2002-01-01 Mci Communications Corporation System and method for providing requested quality of service in a hybrid network
US6122359A (en) 1997-09-04 2000-09-19 Lucent Technologies Inc. System for coordinating calls between an adjunct device and a switching system
USH1897H (en) 1997-09-26 2000-10-03 Dsc/Celcore, Inc. Merged operations and maintenance center and method for operation
US6233248B1 (en) 1997-10-14 2001-05-15 Itt Manufacturing Enterprises, Inc. User data protocol for internet data communications
GB2344265B (en) * 1997-11-20 2003-07-16 Xacct Technologies Inc Network accounting and billing system and method
US6119106A (en) * 1997-11-26 2000-09-12 Mersky; Randy Method and apparatus for facilitating customer payments to creditors from a remote site
US6396916B2 (en) 1997-12-10 2002-05-28 Mci Communications Corporation Clip-on fraud prevention method and apparatus
US6151624A (en) 1998-02-03 2000-11-21 Realnames Corporation Navigating network resources based on metadata
US6311186B1 (en) * 1998-02-20 2001-10-30 Priority Call Management, Inc. Telecommunications switching system utilizing a channelized database access mechanism
US6466971B1 (en) * 1998-05-07 2002-10-15 Samsung Electronics Co., Ltd. Method and system for device to device command and control in a network
GB2340344A (en) 1998-07-29 2000-02-16 Nokia Mobile Phones Ltd Bilateral Data Transfer Verification for Programming a Cellular Phone
US6870845B1 (en) * 1998-08-04 2005-03-22 At&T Corp. Method for providing privacy by network address translation
US7206397B1 (en) * 1998-08-04 2007-04-17 At&T Corp. Method for allocating network resources
US6282193B1 (en) 1998-08-21 2001-08-28 Sonus Networks Apparatus and method for a remote access server
US6134307A (en) * 1998-09-21 2000-10-17 Iridium Ip Llc Call conversion process for a business system for a global telecommunications network
US6614781B1 (en) * 1998-11-20 2003-09-02 Level 3 Communications, Inc. Voice over data telecommunications network architecture
US7058704B1 (en) * 1998-12-01 2006-06-06 Network Appliance, Inc.. Method and apparatus for implementing a service-level agreement
US20010012346A1 (en) * 1999-01-29 2001-08-09 Alex Terry Interactive billing system utilizing a thin web client interface
WO2000052916A1 (en) 1999-03-05 2000-09-08 Gric Communications, Inc. Method and system for internet telephony using gateway
US6631186B1 (en) * 1999-04-09 2003-10-07 Sbc Technology Resources, Inc. System and method for implementing and accessing call forwarding services
US6377939B1 (en) 1999-05-04 2002-04-23 Metratech Pipelined method and apparatus for processing communication metering data
US20020124100A1 (en) * 1999-05-20 2002-09-05 Jeffrey B Adams Method and apparatus for access to, and delivery of, multimedia information
US6751652B1 (en) 1999-06-29 2004-06-15 Transnexus, Inc. Intelligent end user devices for clearinghouse services in an internet telephony system
IL130893A (en) * 1999-07-12 2003-12-10 Ectel Ltd Method and system for creating integrated call detail records (cdr) databases in management systems of telecommunications networks
US6366655B1 (en) 1999-08-23 2002-04-02 Ameritech Corporation Method and system for service control point billing
US6490564B1 (en) * 1999-09-03 2002-12-03 Cisco Technology, Inc. Arrangement for defining and processing voice enabled web applications using extensible markup language documents
US6952800B1 (en) * 1999-09-03 2005-10-04 Cisco Technology, Inc. Arrangement for controlling and logging voice enabled web applications using extensible markup language documents
US6615236B2 (en) * 1999-11-08 2003-09-02 Worldcom, Inc. SIP-based feature control
US6499054B1 (en) 1999-12-02 2002-12-24 Senvid, Inc. Control and observation of physical devices, equipment and processes by multiple users over computer networks
US20010027420A1 (en) * 1999-12-21 2001-10-04 Miroslav Boublik Method and apparatus for capturing transaction data
US6577718B1 (en) 1999-12-22 2003-06-10 At&T Corp. Method for call forwarding without hairpinning and with split billing
US20010040886A1 (en) * 2000-01-07 2001-11-15 Ray Jimenez Methods and apparatus for forwarding audio content using an audio web retrieval telephone system
WO2001058110A2 (en) 2000-02-03 2001-08-09 Apion Telecoms Limited A network gateway-based billing method
US6714992B1 (en) * 2000-02-25 2004-03-30 Navic Systems, Inc. Method and system for embedded network device installation
US20010032197A1 (en) * 2000-02-25 2001-10-18 Gautam Chandra System and process for transactional infrastructure for energy distribution
US6907032B2 (en) 2000-03-06 2005-06-14 Goremote Internet Communications, Inc. Method for selecting terminating gateways for an internet telephone call using a tree search
US6980526B2 (en) * 2000-03-24 2005-12-27 Margalla Communications, Inc. Multiple subscriber videoconferencing system
US6976090B2 (en) * 2000-04-20 2005-12-13 Actona Technologies Ltd. Differentiated content and application delivery via internet
US8699472B2 (en) 2000-05-24 2014-04-15 Nokia Corporation Common charging identifier for communication networks
US20010051962A1 (en) * 2000-06-08 2001-12-13 Robert Plotkin Presentation customization
US6631185B1 (en) * 2000-06-22 2003-10-07 Micron Technology Inc. Method and apparatus for comparing communication service plans based on usage statistics
US6768722B1 (en) * 2000-06-23 2004-07-27 At&T Corp. Systems and methods for managing multiple communications
US6895438B1 (en) * 2000-09-06 2005-05-17 Paul C. Ulrich Telecommunication-based time-management system and method
EP1319281B1 (en) * 2000-09-11 2007-05-09 TransNexus, Inc. Clearinghouse server for internet telephony and multimedia communications
EP1202528A3 (en) 2000-10-31 2004-01-28 Alcatel USA Sourcing, L.P. Browser-based monitoring system and method for IP-based services
AU2001215191A1 (en) * 2000-11-06 2002-05-15 Nokia Networks Oy A method for billing a subscriber for data transmitted in a signaling message
US20020095339A1 (en) * 2000-11-28 2002-07-18 Galloway Richard L. Methods for enhancing broadcast media advertising
US20030079223A1 (en) * 2000-11-28 2003-04-24 Galloway Richard L. Methods for enhancing broadcast media advertising
US6870817B2 (en) * 2000-12-20 2005-03-22 Nortel Networks Limited Method and apparatus for monitoring calls over a session initiation protocol network
US6865681B2 (en) * 2000-12-29 2005-03-08 Nokia Mobile Phones Ltd. VoIP terminal security module, SIP stack with security manager, system and security methods
US20020103898A1 (en) * 2001-01-31 2002-08-01 Moyer Stanley L. System and method for using session initiation protocol (SIP) to communicate with networked appliances
US7136467B2 (en) * 2001-03-02 2006-11-14 Symphony Service Corp Customer-oriented telecommunications data aggregation and analysis method and object oriented system
US6937563B2 (en) * 2001-03-08 2005-08-30 Nortel Networks Limited Homing and controlling IP telephones
US20020160810A1 (en) * 2001-03-14 2002-10-31 Telefonaktiebolaget Lm Ericsson (Publ) Intelligent network service control point and method of implementing user services utilizing call processing language scripts
US7289522B2 (en) * 2001-03-20 2007-10-30 Verizon Business Global Llc Shared dedicated access line (DAL) gateway routing discrimination
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
US20020150221A1 (en) * 2001-04-12 2002-10-17 Carson Douglas John Generating call detail records
EP1536622A1 (en) * 2003-11-28 2005-06-01 Koninklijke KPN N.V. Call detail record for internet call waiting

Also Published As

Publication number Publication date
CN1509448A (en) 2004-06-30
EP1381975A1 (en) 2004-01-21
US20090222457A1 (en) 2009-09-03
US20030009463A1 (en) 2003-01-09
US7945592B2 (en) 2011-05-17
WO2002075605A1 (en) 2002-09-26
BR0208230A (en) 2004-03-23
MXPA03008508A (en) 2004-06-30
JP2004532547A (en) 2004-10-21
US20120182987A1 (en) 2012-07-19
US8886682B2 (en) 2014-11-11
US8161080B2 (en) 2012-04-17
CA2441323A1 (en) 2002-09-26

Similar Documents

Publication Publication Date Title
US8161080B2 (en) XML based transaction detail records
AU725933B2 (en) A communication system architecture
AU738963B2 (en) A system, method and article of manufacture for switched telephony communication
US6335927B1 (en) System and method for providing requested quality of service in a hybrid network
US7145898B1 (en) System, method and article of manufacture for selecting a gateway of a hybrid communication system architecture
US6754181B1 (en) System and method for a directory service supporting a hybrid communication system architecture
US5999525A (en) Method for video telephony over a hybrid network
US5867494A (en) System, method and article of manufacture with integrated video conferencing billing in a communication system architecture
US20090285204A1 (en) Recursive query for communications network data
EP1652359B1 (en) Method and system for suppressing early media in a communications network
US6731625B1 (en) System, method and article of manufacture for a call back architecture in a hybrid network with support for internet telephony
US8576992B2 (en) Mixed protocol multi-media provider system incorporating a session initiation protocol (SIP) based media server adapted to operate using SIP messages which encapsulate GR-1129 advanced intelligence network based information
WO1998034391A9 (en) A communication system architecture
Lu et al. Toward the PSTN/Internet Inter-Networking--Pre-PINT Implementations
AU2002252424A1 (en) XML based transaction detail records
Lung et al. Network Working Group J. Haluska Internet Draft Telcordia Intended Status: Informational R. Ahern Expires: May 15, 2009 AT&T Customer Information Services
Lu et al. RFC2458: Toward the PSTN/Internet Inter-Networking--Pre-PINT Implementations
Krishnaswamy et al. Toward the PSTN/Internet Inter-Networking--Pre-PINT Implementations
Conroy et al. Netowrk Working Group H. Lu Request for Comments: 2458 Editor Category: Informational M. Krishnaswamy Lucent Technologies
AU6259298A (en) A communication system architecture

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: C2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

COP Corrected version of pamphlet

Free format text: PAGES 1/2-2/2, DRAWINGS, REPLACED BY NEW PAGES 1/2-2/2; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

WWE Wipo information: entry into national phase

Ref document number: 2002252424

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2002721497

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2002574541

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2441323

Country of ref document: CA

Ref document number: PA/a/2003/008508

Country of ref document: MX

Ref document number: 1199/KOLNP/2003

Country of ref document: IN

Ref document number: 01198/KOLNP/2003

Country of ref document: IN

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 028102533

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2002721497

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWW Wipo information: withdrawn in national office

Ref document number: 2002721497

Country of ref document: EP