XML based transaction detail records

• US 8,161,080 B2
• Filed: 12/31/2008
• Issued: 04/17/2012
• Est. Priority Date: 03/20/2001
• Status: Expired due to Term

• 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): LOVEL, KIMBERLY M
• Application Number:
  US12/347,819
• Publication Number:
  US 20090222457A1
• Time in Patent Office: 1,203 Days
• Field of Search: 707/802, 707/922, 707/999.101, 707/999.102, 707/999.107, 455/405, 455/406
• 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 computer-readable medium having stored thereon computer-executable instructions to cause a processor in a network device to perform a method comprising:

storing an extensible markup language (XML) transaction detail file, the XML transaction detail file comprising;

an XML declaration field, the XML declaration field including data 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 a first server generating the XML transaction detail file, and

a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the transaction detail section in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction;

enabling the XML transaction detail file to be active for a particular period of time; and

transmitting the XML transaction detail file to a second server,

where the at least one transaction detail record includes an authentication section, the authentication section including data indicating a time when an authentication was performed, a cause for the authentication, and a result of the authentication.

2. The computer-readable medium of claim 1, where the XML transaction detail file further comprises a time/date field including data indicating a time and date that the XML transaction detail file was opened.

3. The computer-readable medium of claim 1, where the first server comprises an internet protocol (IP) network server.

4. The computer-readable medium of claim 3, where the server identification field further includes an IP address of at least one of a proxy server, a conferencing server, or a voice mail server.

5. The computer-readable medium of claim 3,

where the at least one transaction detail record includes a plurality of transaction detail records,

where the telecommunication transaction comprises a plurality of telecommunication transactions, and

one of the plurality of transaction detail records includes a correlation identification field including data correlating the one of the plurality of transaction detail records to one of the plurality of telecommunication transactions.

6. The computer-readable medium of claim 3, where one of the at least one transaction detail record includes a request section including information related to a session initiation protocol (SIP) request that is either sent or received by the IP network server.

7. The computer-readable medium of claim 6, where the request section includes a received-from field including data indicating an IP address of at least one of a sender of the SIP request or an addressee of the SIP request.

8. The computer-readable medium of claim 6, where the request section includes a message field including data contained in the SIP request.

9. The computer-readable medium of claim 3, where the at least one transaction detail record includes a response section including information related to a SIP response that is either sent or received by the IP network server.

10. The computer-readable medium of claim 9, where the response section includes a received-from field including data indicating an IP address of at least one or a sender or an addressee of the SIP response.

11. The computer-readable medium of claim 9, where the response section includes a message field including data contained in the SIP response.

12. The computer-readable medium of claim 1, where one of the at least one transaction detail record includes a time/date field including data indicating when the one of the at least one transaction detail record was made.

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

storing an extensible markup language (XML) transaction detail file, the XML transaction detail file comprising;

an XML declaration field, the XML declaration field including data 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 a first server generating the XML transaction detail file, and

a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the transaction detail section in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction;

enabling the XML transaction detail file to be active for a particular period of time and

transmitting the XML transaction detail file to a second server,

where the first server comprises an internet protocol (IP) network server, and

where one of the at least one transaction detail record includes an event section including data recording at least one event that occurred at the IP network server, where the at least one event is unrelated to receiving or sending a message by the IP network server.

14. The computer-readable medium of claim 13, where the at least one event includes at least one of a timeout event or an error event.

15. A computer-readable medium having stored thereon computer-executable instructions to cause a processor in a network device to perform a comprising:

storing an extensible markup language (XML) transaction detail file, the XML transaction detail file comprising;

an XML declaration field, the XML declaration field including data 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 a first server generating the XML transaction detail file, and

a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the transaction detail section in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction;

enabling the XML transaction detail file to be active for a particular period of time and

transmitting the XML transaction detail file to a second server,

where the first server comprises a session initiation protocol (SIP) redirect server, and

where the at least one transaction detail record includes a features section that includes data related at least one feature executed by the SIP redirect server during the transaction.

16. The computer-readable medium of claim 15, where the server identification field includes an IP address of the SIP redirect server.

17. The computer-readable medium of claim 15,

where the at least one transaction detail record includes a plurality of transaction detail records,

where the telecommunication transaction comprises one or more telecommunication transaction, and

one of the plurality of the transaction detail records includes a correlation identification field including data correlating the one of the plurality of the transaction detail record to a corresponding one of the one or more telecommunication transaction.

18. The computer-readable medium of claim 15, where each one of the at least one transaction detail record includes a time/date field including data indicating when the one of the at least one transaction detail record was made.

19. The computer-readable medium of claim 15, where one of the at least one transaction detail record includes a request section including information related to a SIP request that is received by the SIP redirect server from a SIP network server.

20. The computer-readable medium of claim 19, where the request section includes a received-from field including data indicating an IP address of an original sender of the SIP request.

21. The computer-readable medium of claim 19, where the request section includes a message field including data contained in the SIP request.

22. The computer-readable medium of claim 15, where one of the at least one transaction detail record includes a response section including information about a SIP response that is received by the SIP redirect server from a SIP network server.

23. The computer-readable medium of claim 22, where the response section includes a sent-to field including data indicating an IP address of an addressee of the SIP response.

24. The computer-readable medium of claim 22, where the response section includes a message field including data associated with the response.

25. The computer-readable medium of claim 15, where the features section includes at least one recursive routing field that includes data related to a recursive call routing feature.

26. The computer-readable medium of claim 15, where the features section includes at least one originating call validation field, the at least one originating call validation field including data relating to a validation of a call originator and relating to the call originator.

27. The computer-readable medium of claim 15, where the features section includes a non-trusted terminating call field that includes data related to whether a non-trusted call was allowed during the telecommunications transaction.

28. The computer-readable medium of claim 15, where the features section includes at least one terminating call validation field, the at least one terminating call validation field including data relating to a validation of a subscriber being called and relating to the subscriber.

29. The computer-readable medium of claim 15, where the features section includes at least one originating call screening field including information indicating when a call screening feature is executed.

30. The computer-readable medium of claim 15, where the features section includes at least one terminating call screening field including information indicating when a terminating call screening feature is executed.

31. The computer-readable medium of claim 15, where the features section includes at least one call forwarding field including information indicating when at least one call forwarding feature is executed.

32. The computer-readable medium of claim 15, where the features section includes at least one find-me field including information indicating when a find-me feature is executed.

33. The computer-readable medium of claim 15, where the features section includes at least one registered address list field including information indicating to when a call is redirected to a list of registered addresses.

34. The computer-readable medium of claim 15, where the features section includes at least one default address field including information indicating when a call is redirected to a default address in a subscriber'"'"'s record.

35. A computer-readable medium having stored thereon computer-executable instructions to cause a processor in a network device to perform a method comprising:

storing an extensible markup language (XML) transaction detail file, the XML transaction detail file comprising;

an XML declaration field, the XML declaration field including data defining the XML transaction detail as an XML file,

a server identification field, the server identification field including an internet protocol (IP) address of a first server generating the XML transaction detail file, and

a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the transaction detail section in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunication transaction;

enabling the XML transaction detail file to be active for a particular period of time; and

transmitting the XML transaction detail file to a second server,

where each transaction detail record includes at least one directory access protocol (DAP) field including information associated with one or more DAP communication, and

where the first server comprises a session initiation protocol (SIP) redirect server.

36. A server device comprising:

a processor configured to;

generate an extensible markup language (XML) transaction detail file that is active for a particular period of time, where the XML transaction detail file comprises;

an XML declaration field including data 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;

receive transaction data related to a telecommunications transaction, the telecommunications transaction occurring during the particular period of time;

in response to receiving transaction data related to the telecommunications transaction, add at least one transaction detail record to the transaction detail section, the at least one transaction detail record including the transaction data corresponding to the telecommunications transaction, where each of the at least one transaction detail record includes an authentication section, the authentication section including data indicating a time when an authentication was performed, a reason for the authentication, and a result of the authentication; and

transmit the XML transaction detail file to another server device.

37. The server device of claim 36, where the XML transaction detail file further comprises a time/date field including data indicating when the XML transaction detail file was opened.

38. The server device of claim 36, where each of the at least one transaction detail record includes a time/date field including data indicating when the each of the at least one transaction detail record was made.

39. The server device of claim 36, where the server device comprises one of an internet protocol (IP) network server or a session initiation protocol (SIP) redirect server.

40. The server device of claim 36,

where the at least one transaction detail record includes a plurality of transaction detail records,

where the telecommunication transaction comprises a plurality of telecommunication transactions, and

where each one of the plurality of transaction detail records includes a correlation identification field including data correlating said one of the plurality of transaction detail records to one of the plurality of telecommunication transactions.

41. The server device of claim 36, where one of the at least one transaction detail record includes a session initiation protocol (SIP) message section including information related to a SIP message that is either sent or received by the server device, where the SIP message includes an SIP request or an SIP response.

42. The server device of claim 41, where the SIP message section includes a received-from field including data indicating an IP address of at least one of a sender or an addressee of the SIP message.

43. The server device of claim 41, where the SIP message section includes a content field including data contained the SIP message.

44. A server device comprising:

a processor configured to;

generate an extensible markup language (XML) transaction detail file that is active for a particular period of time, where the XML transaction detail file comprises;

an XML declaration field including data defining the XML transaction detail 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;

receive transaction data related to a telecommunications transaction, the telecommunications transaction occurring during the particular period of time;

in response to receiving the transaction data related to the telecommunications transaction, add at least one transaction detail record to the transaction detail section, the at least one transaction detail record including the transaction data corresponding to the telecommunications transaction, where one of the at least one transaction detail record includes an event section including data recording at least one event that occurred at the server device, where the at least one event is unrelated to receiving or sending a message by the server device; and

transmit the XML transaction detail file to another server device.

45. The server device of claim 44, where the at least one event includes at least one of a timeout event or an error event.