XML based transaction detail records

• US 7,945,592 B2
• Filed: 03/15/2002
• Issued: 05/17/2011
• Est. Priority Date: 03/20/2001
• Status: Expired due to Fees

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Gallant, John Kenneth
• Primary Examiner(s): Wassum; Luke S
• Application Number:
  US10/099,323
• Publication Number:
  US 20030009463A1
• Time in Patent Office: 3,350 Days
• Field of Search: 707/100, 707/102, 707/10, 707/101, 379/111, 379/455, 379/67.1, 379/112.1, 705/1, 709/203, 709/223, 709/224, 455/560
• 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:

creating, by a server device, an extensible markup language (XML) transaction detail file, where the XML transaction detail file is active for a predetermined period of time, where creating the XML transaction detail file includes;

detecting a telecommunications transaction,

analyzing the telecommunications transaction to determine that the telecommunications transaction is conducted between a telecommunications apparatus and a session initiation protocol server (SIP-server), and

generating the XML transaction detail file based on the telecommunications transaction; and

during the predetermined period of time, storing, via the server device, at least one transaction detail record in the XML transaction detail file in response to determining that the telecommunications transaction is conducted between the telecommunications apparatus and the SIP-server, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction,

where the telecommunications apparatus is a proxy server and the SIP-server is a redirect server,

where the XML transaction detail file is a first XML transaction detail file, and

where the redirect server forms a second XML transaction detail file that differs in format from the first XML transaction detail file.

2. The method of claim 1, further comprising:

closing the XML transaction detail file when the predetermined period of time expires;

creating a third XML transaction detail file, the third 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.

3. The method of claim 1, where the XML transaction detail file comprises:

an XML declaration field, the XML declaration field defining 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 device; and

a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored 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.

4. The method of claim 1, where the telecommunications transaction includes a SIP-INVITE message.

5. The method of claim 1, where the telecommunications transaction includes a SIP-ACK message.

6. The method of claim 1, where the telecommunications transaction includes a SIP-OPTIONS message.

7. The method of claim 1, where the telecommunications transaction includes a SIP-BYE message.

8. The method of claim 1, where the telecommunications transaction includes a SIP-CANCEL message.

9. The method of claim 1, where the telecommunications transaction includes a SIP-REGISTER message.

10. The method of claim 1, where the telecommunications transaction includes a billing transaction.

11. The method of claim 1, where the telecommunications transaction includes a monitoring transaction.

12. The method of claim 1, where the telecommunications transaction includes a performance measurement transaction.

13. A tangible computer-readable medium having stored thereon computer-executable instructions to cause a processor in a server to perform a method comprising:

creating an extensible markup language (XML) transaction detail file, the XML transaction detail file being active for a predetermined period of time, where creating the XML transaction detail file includes;

detecting a telecommunications transaction,

analyzing the telecommunications transaction to determine that the telecommunications transaction is conducted between a telecommunications apparatus and a session initiation protocol server (SIP-server), and

generating the XML transaction detail file based on to the telecommunications transaction; and

storing, during the predetermined period of time, at least one transaction detail record in the XML transaction detail file in response to determining that the telecommunications transaction is conducted between the telecommunications apparatus and the SIP-server, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction, where, after the predetermined period of time expires, no additional transaction detail record can be added to the XML transaction detail file,

where the telecommunications apparatus is a proxy server and the SIP-server is a redirect server,

where the XML transaction detail file is a first XML transaction detail file, and

where the redirect server forms a second XML transaction detail file that differs in format from the first XML transaction detail file.

14. The computer readable medium of claim 13, further comprising:

closing the XML transaction detail file when the predetermined period of time expires;

creating a third XML transaction detail file, the third 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.

15. The computer readable medium of claim 13, where the XML transaction detail file comprises:

an XML declaration field, the XML declaration field defining 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 at least one transaction detail record, the at least one transaction detail record being stored 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.

16. The computer readable medium of claim 13, where the telecommunications transaction includes a session initiation protocol server (SIP) INVITE message.

17. The computer readable medium of claim 13, where the telecommunications transaction includes a SIP-ACK message.

18. The computer readable medium of claim 13, where the telecommunications transaction includes a SIP-OPTIONS message.

19. The computer readable medium of claim 13, where the telecommunications transaction includes a SIP-BYE message.

20. The computer readable medium of claim 13, where the telecommunications transaction includes a SIP-CANCEL message.

21. The computer readable medium of claim 13, where the telecommunications transaction includes a SIP-REGISTER message.

22. The computer readable medium of claim 13, where the telecommunications transaction includes a billing transaction.

23. The computer readable medium of claim 13, where the telecommunications transaction includes a monitoring transaction.

24. The computer readable medium of claim 13, where the telecommunications transaction includes a performance measurement transaction.

25. A device comprising:

a processor to;

create an extensible markup language (XML) transaction detail file, where the XML transaction detail file is active for a predetermined period of time, where creating the XML transaction detail file includes;

detecting a telecommunications transaction,

analyzing the telecommunications transaction to determine that the telecommunications transaction is conducted between a telecommunications apparatus and a session initiation protocol server (SIP-server), and

generating the XML transaction detail file based on the telecommunications transaction; and

store, during the predetermined period of time, at least one transaction detail record in the XML transaction detail file in response to determining that the telecommunications transaction is conducted between the telecommunications apparatus and the SIP-server, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction,

where the telecommunications apparatus is a proxy server and the SIP-server is a redirect server,

where the XML transaction detail file is a first XML transaction detail file, and

where the redirect server forms a second XML transaction detail file that differs in format from the first XML transaction detail file.

26. The device of claim 25, where the processor is further to:

close the XML transaction detail file when the predetermined period of time expires;

create a third XML transaction detail file, the third XML transaction detail file being active for a second predetermined period of time; and

repeat the closing and the creating for a number of times, as directed by a network management system.

27. The device of claim 25, where the XML transaction detail file comprises:

an XML declaration field, the XML declaration field defining 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 device; and

a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored 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.

28. The device of claim 25, where the telecommunications transaction includes a SIP-INVITE message.

29. The device of claim 25, where the telecommunications transaction includes a SIP-ACK message.

30. The device of claim 25, where the telecommunications transaction includes a SIP-OPTIONS message.

31. The device of claim 25, where the telecommunications transaction includes a SIP-BYE message.

32. The device of claim 25, where the telecommunications transaction includes a SIP-CANCEL message.

33. The device of claim 25, where the telecommunications transaction includes a SIP-REGISTER message.

34. The device of claim 25, where the telecommunications transaction includes a billing transaction.

35. The device of claim 25, where the telecommunications transaction includes a monitoring transaction.

36. The device of claim 25, where the telecommunications transaction includes a performance measurement transaction.