XML based transaction detail records

• US 20030009463A1
• Filed: 03/15/2002
• Published: 01/09/2003
• Est. Priority Date: 03/20/2001
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Gallant, John Kenneth
• Granted Patent: US 7,945,592 B2
• Time in Patent Office: Days
• US Class Current: 707/10
• 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 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 IP 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 SIP-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 SIP-device.

8. The method of claim 7, wherein the SIP-device is a telephone.

9. The method of claim 7, wherein the SIP-device is a computer.

10. The method of claim 5, wherein the telecommunications apparatus includes a gateway.

11. The method of claim 5, wherein the SIP-server is a proxy server.

12. The method of claim 5, wherein the SIP-server is a conferencing server.

13. The method of claim 5, wherein the SIP-server is a voice mail server.

14. The method of claim 5, wherein the telecommunications apparatus is a proxy server and the SIP-server is a redirect server.

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

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

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

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

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

20. The method of claim 1, wherein the telecommunications transaction includes a SIP-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.

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 IP address of a proxy server.

29. The data structure of claim 26, wherein the server identification field includes the IP address of a conferencing server.

30. The data structure of claim 26, wherein the server identification field includes the IP 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 SIP request that is either sent or received by the IP network server.

35. The data structure of claim 34, wherein the request section includes a received-from field indicating the IP address of the sender of the SIP-request.

36. The data structure of claim 34, wherein the request section includes a sent-to field indicating the IP address of the addressee of the SIP-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 SIP response that is either sent or received by the IP network server.

40. The data structure of claim 39, wherein the response section includes a received-from field indicating the IP address of the sender of the SIP-response.

41. The data structure of claim 39, wherein the response section includes a sent-to field indicating the IP address of the addressee of the SIP-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 IP 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 SIP 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 IP 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 SIP request that is received by the SIP redirect server from a SIP network server.

53. The data structure of claim 52, wherein the request section includes a received-from field indicating the IP address of an original sender of the SIP-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 SIP response that is received by the SIP redirect server from a SIP 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 SIP-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 SIP 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 a non 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.

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 IP 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.

70. A telecommunications network, comprising:

at least one telecommunications apparatus configured to perform a telecommunications transaction; and

at least one SIP-server coupled to the at least one telecommunications apparatus, the at least one SIP-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 SIP device.

72. The network of claim 71, wherein the SIP device includes a telephone.

73. The network of claim 71, wherein the SIP device includes a computer.

74. The network of claim 71, wherein the telecommunications apparatus includes a SIP proxy server and the at least one SIP-server includes a SIP 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 SIP-server includes a SIP proxy server.

80. The network of claim 71, wherein the at least one SIP-server includes a SIP conferencing server.

81. The network of claim 71, wherein the at least one SIP-server includes a SIP 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 IP 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 telecommunications transaction includes a SIP-ACK message.

87. The method of claim 82, wherein the telecommunications transaction includes a SIP-OPTIONS message.

88. The method of claim 82, wherein the telecommunications transaction includes a SIP-BYE message.

89. The method of claim 82, wherein the telecommunications transaction includes a SIP-CANCEL message.

90. The method of claim 82, wherein the telecommunications transaction includes a SIP-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.