Method for recording events in an IP network

• US 20030126257A1
• Filed: 12/17/2001
• Published: 07/03/2003
• Est. Priority Date: 12/17/2001
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: WorldCom, Inc. (Verizon Communications Inc.)
• Inventors: Vijay, Sharadha
• Granted Patent: US 8,380,840 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• 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 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 63/1416 Event detection, e.g. attack signature detection
• 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/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 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: 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/06 : Recording class or number of calling , i.e. A-party or called party , i.e. B-party
• CPC Class Codes: H04M 15/41 : Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• 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/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/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/8214 : Data or packet based
• 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/0164 : Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• 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/2013 : Fixed data network, e.g. PDN, ATM, B-ISDN
• CPC Class Codes: H04M 2215/2046 : Hybrid network
• CPC Class Codes: H04M 2215/22 : Bandwidth or usage-sensitve billing
• 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 2215/782 : Data or packet based
• 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

Abstract

The present invention relates to a method for capturing call events and other information in a platform independent way. The method includes generating call event records in response to a SIP call events. A call event file is created that includes all the call event records collected by a server over a predetermined period of time. The call event file is an XML document that includes generic, uniformly formatted records that can be read by any network device equipped with an XML parser. XML documents include embedded instructions that enable a receiving computer to decode the records without needing a special proprietary interface.

Claims

1. A method for capturing call event data in a telecommunications network, the method comprising:

creating an XML call event file including a server information section, at least one SIP message section, and at least one call event section;

generating at least one call event record in response to at least one event; and

storing the at least one call event record in either the at least one SIP message section, or the at least one call event section.

2. The method of claim 1, wherein the method is performed using a telecommunications network device.

3. The method of claim 2, wherein the telecommunications network device is a SIP server computer.

4. The method of claim 3, wherein the SIP server computer is a SIP proxy server.

5. The method of claim 3, wherein the SIP server computer is a SIP redirect server.

6. The method of claim 2, wherein the telecommunications network device is a network management system.

7. The method of claim 6, wherein the network management system includes a database.

8. The method of claim 6, wherein the network management system includes a LAN.

9. The method of claim 2, wherein the telecommunications network device is a SIP client device.

10. The method of claim 1, wherein the at least one event includes a SIP invite request.

11. The method of claim 1, wherein the at least one event includes a response to a SIP invite request.

12. The method of claim 1, wherein the at least one event includes a SIP redirection message.

13. The method of claim 1, wherein the at least one event includes a SIP proxying request.

14. The method of claim 1, wherein the at least one event includes a SIP proxying response message.

15. The method of claim 1, wherein the at least one event includes a SIP error message.

16. The method of claim 1, wherein the at least one event includes a network fault condition.

17. The method of claim 1, wherein the at least one event includes the transmission or reception of billing information.

18. The method of claim 1, wherein the at least one event is an event related to network monitoring.

19. The method of claim 1, wherein the XML document includes a server information tag that identifies an originating server.

20. The method of claim 1, wherein the XML document includes a SIP message section identifying whether the event is a SIP request or a SIP response.

21. The method of claim 20, wherein the SIP message section includes a service identifier field, the server identifier field uniquely identifying the service associated with the SIP message.

22. The method of claim 20, wherein the SIP message section includes a send/receive field that includes IP addresses associated with a caller and a callee.

23. The method of claim 20, wherein the SIP message section includes an other message content field that is used to accommodate any additional information.

24. The method of claim 1, wherein the XML document includes an event field identifying the event.

25. The method of claim 1, wherein the XML document includes a document type declaration section that provides information required by a receiving computer to properly decode the XML document.

26. A computer readable medium that can be used to direct a Session Initiation Protocol (SIP) server computer to function in a specified manner, the computer readable medium comprising:

a SIP application layer software module, the SIP application layer software module being executable by the SIP server computer to provide SIP functionality;

a call event record module coupled to the SIP application layer software module, the call event record module being configured to create at least one call event record in response to at least one event; and

an XML processor module coupled to the call event record module, the XML processor module being configured to create an XML call event file, the XML call event file including the at least one call event record.

27. The medium of claim 26, wherein the SIP server computer is configured as a SIP proxy server.

28. The medium of claim 26, wherein the SIP server computer is configured as a SIP redirect server.

29. The medium of claim 26, wherein the at least one event includes a SIP invite request.

30. The medium of claim 26, wherein the at least one event includes a response to a SIP invite request.

31. The medium of claim 26, wherein the at least one event includes a SIP redirection message.

32. The medium of claim 26, wherein the at least one event includes a SIP proxying request.

33. The medium of claim 26, wherein the at least one event includes a SIP proxying response message.

34. The medium of claim 26, wherein the at least one event includes an error message.

35. The medium of claim 26, wherein the at least one event includes a network fault condition.

36. The medium of claim 26, wherein the at least one event includes the transmission or reception of billing information.

37. The medium of claim 26, wherein the at least one event is an event related to network monitoring.

38. The medium of claim 26, wherein the XML document includes a server information tag that identifies an originating server.

39. The medium of claim 26, wherein the XML document includes a SIP message section identifying whether the event is a SIP request or a SIP response.

40. The medium of claim 39, wherein the SIP message section includes a service identifier field, the server identifier field uniquely identifying the service associated with the SIP message.

41. The medium of claim 39, wherein the SIP message section includes a send/receive field that includes IP addresses associated with a caller and a callee.

42. The medium of claim 39, wherein the SIP message section includes an other message content field that is used to accommodate any additional information.

43. The medium of claim 26, wherein the XML document includes an event field identifying the event.

44. The medium of claim 26, wherein the XML document includes a document type declaration section that provides information required by a receiving computer to properly decode the XML document.

45. A set of application program interfaces embodied on a computer readable medium for execution on a computer, the set of application program interfaces comprising:

a first interface that receives an event identifier and returns a call event record; and

a second interface that receives a set of call event records and returns a call event file, the call event file including the set of call event records, the call event file being written using the Extensible Markup Language (XML), whereby the call event file is an XML document.

46. The program interfaces of claim 45, wherein the at least one event includes a SIP invite request.

47. The program interfaces of claim 45, wherein the at least one event includes a response to a SIP invite request.

48. The program interfaces of claim 45, wherein the at least one event includes a SIP redirection message.

49. The program interfaces of claim 45, wherein the at least one event includes a SIP proxying request.

50. The program interfaces of claim 45, wherein the at least one event includes a SIP proxying response message.

51. The program interfaces of claim 45, wherein the at least one event includes a SIP error message.

52. The program interfaces of claim 45, wherein the at least one event includes a network fault condition.

53. The program interfaces of claim 45, wherein the at least one event includes the transmission or reception of billing information.

54. The program interfaces of claim 45, wherein the at least one event is an event related to network monitoring.

55. The program interfaces of claim 45, wherein the XML document includes a server information tag that identifies an originating server.

56. The program interfaces of claim 45, wherein the XML document includes a SIP message section identifying whether the event is a SIP request or a SIP response.

57. The program interfaces of claim 45, wherein the XML document includes an event field identifying the event.

58. The program interfaces of claim 45, wherein the XML document includes a document type declaration section that provides information required by a receiving computer to properly decode the XML document.

59. A set of application program interfaces embodied on a computer readable medium for execution on a Session Initiation Protocol (SIP) server computer in conjunction with a SIP application layer software module that provides SIP functionality, the set of application program interfaces comprising:

a first interface that receives a SIP event identifier and returns a call event record; and

a second interface that receives a set of call event records and returns a call event file, the call event file including the set of call event records, the call event file being written using the Extensible Markup Language (XML), whereby the call event file is an XML document.

60. A communications network for establishing a communications session between a first client and a second client, the communications network comprising:

at least one Session Initiation Protocol (SIP) server computer, the SIP server computer including a first call event record module configured to create a call event record corresponding to an event, and a first XML processor module configured to create a first XML call event file, the first XML call event file including the call event record; and

at least one network system coupled to the at least one SIP server computer, the at least one network system including a second XML processor module, whereby the at least one network system can read the first XML call event file.

61. The network of claim 60, wherein the at least one SIP server computer includes at least one SIP proxy server and at least one SIP redirect server.

62. The network of claim 61, wherein the at least one SIP proxy server includes a plurality of SIP proxy servers, at least one of the plurality of SIP proxy servers being manufactured by a different manufacturer.

63. The network of claim 61, wherein the at least one SIP redirect server includes a plurality of SIP redirect servers, at least one of the plurality of SIP redirect servers being manufactured by a different manufacturer.

64. The network of claim 61, wherein the at least one SIP proxy server and the at least one SIP redirect server are manufactured by different manufacturers.

65. The network of claim 60, wherein the at least one SIP server and the at least one network system are manufactured by different manufacturers.

66. The network of claim 60, wherein the at least one network system includes a second call event record module configured to create a call event record corresponding to an event, the second XML processor module configured to create a second XML call event file, the second XML call event file including at least one call event record.

67. The network of claim 66, wherein the first XML processor module is configured to can decode the second XML call event file.

68. The network of claim 67, wherein the first XML call event file includes a document type declaration section that provides information required by the second XML processor module to read the first XML call event file.

69. The network of claim 67, wherein the second XML call event file includes a document type declaration section that provides information required by the first XML processor module to read the second XML call event file.

70. The network of claim 66, wherein both the first XML call event file and the second XML call event file include a server information tag that identifies an originating server.

71. The network of claim 66, wherein both the first XML call event file and the second XML call event file include a SIP message section identifying whether the event is a SIP request or a SIP response.

72. The network of claim 66, wherein both the first XML call event file and the second XML call event file include an event field identifying the event.

73. A computer-readable medium having stored thereon a data structure formatted as an XML document file, the data structure comprising:

a server identifier section including information identifying the server that created the XML document file;

a SIP message type section; and

a SIP event section including information relating to a SIP message event.

74. The data structure of claim 73, wherein the server identifier section includes information identifying the vendor of the server.

75. The data structure of claim 73, wherein the server identifier section includes the operating system running on the server.

76. The data structure of claim 73, wherein the XML document is a call event record that includes a plurality of call event records.

78. The data structure of claim 73, wherein the SIP message section includes a send/receive field that includes IP addresses associated with a caller and a callee for each call event record.

79. The data structure of claim 73, wherein the SIP message section indicates whether a call event record relates to a SIP request or a SIP response.

80. The data structure of claim 73, wherein the SIP message section identifies the originator of each call event record contained in the XML document file.

81. The data structure of claim 73, wherein the SIP message section identifies the receiving party of a call event record pertaining to a SIP message.

82. The data structure of claim 73, wherein the SIP message section includes a time and date of each call event record contained in the XML document file.

83. The data structure of claim 73, where the SIP event section identifies the event recorded by each call event record contained in the XML document file.

84. The data structure of claim 73, wherein the XML document includes a document type declaration section that provides information required by a receiving computer to properly read the XML document.

77. The data structure of claim 77, wherein the SIP message section includes a service identifier field, the server identifier field uniquely identifying the service associated each call event record.

85. A computer readable medium having computer executable instructions for performing a method, the method comprising:

generating at least one call event record in response to at least one event; and

creating an XML call event file including the at least one call event record.