XML based transaction detail records

• US 8,886,682 B2
• Filed: 04/13/2011
• Issued: 11/11/2014
• Est. Priority Date: 03/20/2001
• Status: Expired due to Fees

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Gallant, John Kenneth
• Primary Examiner(s): Jalil, Neveen Abel
• Assistant Examiner(s): Tamaru, Michael K
• Application Number:
  US13/085,876
• Publication Number:
  US 20120182987A1
• Time in Patent Office: 1,308 Days
• Field of Search: None
• US Class Current: 707/802
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 12/1446 inter-operator billing
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/612 : for unicast
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/14 : Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 : specially adapted for interworking of IP-based networks with other networks
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04M 15/00 : Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/43 : Billing software details
• CPC Class Codes: H04M 15/44 : Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/47 : Fraud detection or prevention means
• CPC Class Codes: H04M 15/49 : Connection to several service providers
• CPC Class Codes: H04M 15/51 : for resellers, retailers or service providers
• CPC Class Codes: H04M 15/52 : for operator independent billing system
• CPC Class Codes: H04M 15/53 : using mediation
• CPC Class Codes: H04M 15/55 : for hybrid networks
• CPC Class Codes: H04M 15/56 : for VoIP communications
• CPC Class Codes: H04M 15/58 : based on statistics of usage or network monitoring
• CPC Class Codes: H04M 15/63 : based on the content carried by the session initiation protocol [SIP] messages
• CPC Class Codes: H04M 15/745 : Customizing according to wishes of subscriber, e.g. friends or family
• CPC Class Codes: H04M 15/8292 : Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2215/0104 : Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
• CPC Class Codes: H04M 2215/0108 : Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
• CPC Class Codes: H04M 2215/0148 : Fraud detection or prevention means
• CPC Class Codes: H04M 2215/0168 : On line or real-time flexible customization or negotiation according to wishes of subscriber
• CPC Class Codes: H04M 2215/0172 : Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
• CPC Class Codes: H04M 2215/0176 : Billing arrangements using internet
• CPC Class Codes: H04M 2215/0188 : Network monitoring; statistics on usage on called/calling number
• CPC Class Codes: H04M 2215/202 : VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/2046 : Hybrid network
• CPC Class Codes: H04M 2215/22 : Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/44 : Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
• CPC Class Codes: H04M 2215/46 : Connection to several service providers
• CPC Class Codes: H04M 2215/54 : Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04M 3/2218 : Call detail recording
• CPC Class Codes: H04M 7/006 : Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: Y10S 707/922 : Communications
• CPC Class Codes: Y10S 707/944 : Business related

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.

Claims

1. A method comprising:

receiving, by a server device and from a plurality of servers, a plurality of first extensible markup language (XML) transaction detail files,

the plurality of first XML transaction detail files being associated with a plurality of telecommunications transactions conducted between a telecommunications apparatus and the plurality of servers during a particular time period,

the telecommunications apparatus including at least one of;

a telephone that is not session initiation protocol (SIP)-enabled, or a SIP-enabled device,

each of the plurality of first XML transaction detail files including a respective plurality of fields,

each of the plurality of first XML transaction detail files including at least one field, of the plurality of respective fields, that is not common to a field, of the plurality of respective fields, of at least one other first XML transaction detail file, of the plurality of first XML transaction detail files, and

each of the plurality of first XML transaction detail files including transaction data associated with a corresponding telecommunications transaction of the plurality of telecommunications transactions;

converting, by the server device, the plurality of first XML transaction detail files to include common fields to form a plurality of second XML transaction detail files;

determining, by the server device, billing information for the telecommunications apparatus based on the plurality of second XML transaction detail files; and

providing, by the server device, the determined billing information.

2. The method of claim 1, further comprising:

closing a first XML transaction detail file, of the plurality of first XML transaction detail files, when the particular time period expires; and

creating a third XML transaction detail file,

the third XML transaction detail file being active for another time period.

3. The method of claim 1, where a first XML transaction detail file, of the plurality of first XML transaction detail files, includes:

an XML declaration field,

the XML declaration field identifying the first XML transaction detail file as an XML file;

a server identification field,

the server identification field including an internet protocol (IP) address of the server device; and

a transaction detail field including the transaction data.

4. The method of claim 1, where a telecommunications transaction, of the plurality of telecommunication transactions, is associated with least one of:

a SIP-INVITE message,

a SIP-ACK message,

a SIP-OPTIONS message,

a SIP-BYE message,

a SIP-CANCEL message, or

a SIP-REGISTER message.

5. The method of claim 1, where a telecommunications transaction, of the plurality of telecommunication transactions, includes at least one of:

a billing transaction,

a monitoring transaction, or

a performance measurement transaction.

6. The method of claim 1, where, when the telecommunications apparatus includes the SIP-enabled device, the SIP-enabled device includes at least one of:

a SIP-enabled telephone, or

a SIP-enabled computer.

7. A non-transitory computer-readable medium to store instructions, the instructions comprising:

one or more instructions that, when executed by a processor in a server, cause the processor to;

receive, from a plurality of servers, a plurality of extensible markup language (XML) transaction detail files,

the plurality of XML transaction detail files being active for a particular period of time,

the plurality of XML transaction detail files being associated with a plurality of telecommunications transactions conducted between a telecommunications apparatus and the plurality of servers during the particular period of time,

the telecommunications apparatus including at least one of;

a telephone that is not session initiation protocol (SIP)-enabled, or

a SIP-enabled device.

each of the plurality of XML transaction detail files including a respective plurality of fields,

each of the plurality of XML transaction detail files including at least one field, of the plurality of respective fields, that is not common to a field, of the plurality of respective fields, of at least one other XML transaction detail file, of the plurality of XML transaction detail files, and

each of the plurality of XML transaction detail files including at least one transaction detail record,

the at least one transaction detail record including transaction data associated with one or more of the plurality of telecommunications transactions associated with a respective XML transaction detail file of the plurality of XML transaction detail files;

convert the plurality of XML transaction detail files to include common fields; and

provide the converted plurality of XML transaction detail files.

8. The computer readable medium of claim 7, where the instructions further comprise:

one or more instructions to close the plurality of XML transaction detail files when the particular period of time expires; and

one or more instructions to create another plurality of XML transaction detail files, the other XML transaction detail files being active for another particular period of time.

9. The computer readable medium of claim 7, where a XML transaction detail file, of the plurality of XML transaction detail files, comprises:

an XML declaration field,

the XML declaration field identifying the XML transaction detail file as an XML file;

a server identification field,

the server identification field including an internet protocol (IP) address of the server; and

a transaction detail section including the at least one transaction detail record associated with the XML transaction detail file.

10. The computer readable medium of claim 7, where a telecommunications transaction, of the plurality of telecommunications transactions, is associated with at least one of:

a SIP-INVITE message,

a SIP-ACK message,

a SIP-OPTIONS message,

a SIP-BYE message,

a SIP-CANCEL message, or

a SIP-REGISTER message.

11. The computer readable medium of claim 7, where a telecommunications transaction, of the plurality of telecommunications transactions, includes at least one of:

a billing transaction,

a monitoring transaction, or

a performance measurement transaction.

12. A device comprising:

a memory; and

a processor to;

store, in the memory, a plurality of extensible markup language (XML) transaction detail files,

the plurality of XML transaction detail files being associated with a plurality of telecommunications transactions conducted between a telecommunications apparatus and a plurality of servers,

each of the plurality of XML transaction detail files including a respective plurality of fields,

each of the plurality of XML transaction detail files including at least one field, of the plurality of respective fields, that is not common to a field, of the plurality of respective fields, of at least one other XML transaction detail file, of the plurality of XML transaction detail files

store at least one transaction detail record in each of the plurality of XML transaction detail files,

the at least one transaction detail record including transaction data associated with one or more of the plurality of telecommunications transactions, and

convert the plurality of XML transaction detail files to include common fields.

13. The device of claim 12, where the processor is further to:

close an XML transaction detail file, of the plurality of XML transaction detail files, when a first particular period of time expires; and

create another XML transaction detail file,

the other XML transaction detail file being active for a second particular period of time.

14. The device of claim 12, where an XML transaction detail file, of the plurality of XML transaction detail files, comprises:

an XML declaration field,

the XML declaration field identifying the XML transaction detail file as an XML file;

a server identification field,

the server identification field including an internet protocol (IP) address of the device; and

a transaction detail section including the at least one transaction detail record.

15. The device of claim 12, where a telecommunications transaction, of the plurality of telecommunications transactions, is associated with at least one of:

a SIP-INVITE message,

a SIP-ACK message,

a SIP-OPTIONS message,

a SIP-BYE message,

a SIP-CANCEL message, or

a SIP-REGISTER message.

16. The device of claim 12, where a telecommunications transaction, of the plurality of telecommunications transactions, includes at least one of:

a billing transaction,

a monitoring transaction, or

a performance measurement transaction.

17. The device of claim 12, where a server, of the plurality of servers, includes a re-direct server, and the telecommunications apparatus includes a proxy device.

18. The device of claim 12, where, when the telecommunications apparatus includes the SIP-enabled device, the SIP-enabled device includes at least one of:

a SIP-enabled telephone, or

a SIP-enabled computer.

19. The device of claim 12, where the telecommunications apparatus includes a gateway.

20. The device of claim 12, where the server includes at least one of:

a proxy server,

a conferencing server, or

a voice mail server.