System and method for end-to-end communications tracing

• US 20050276388A1
• Filed: 07/09/2004
• Published: 12/15/2005
• Est. Priority Date: 06/15/2004
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Firestone, Scott S., Ethier, Randall P. J., Hammer, Michael P.
• Granted Patent: US 7,209,548 B2
• Time in Patent Office: Days
• US Class Current: 379/32.50
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04M 3/2254 in networks
• CPC Class Codes: H04M 3/2281 Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls
• CPC Class Codes: H04M 7/0084 Network monitoring; Error detection; Error recovery; Network testing
• CPC Class Codes: H04M 7/009 in systems involving PBX or KTS networks
• CPC Class Codes: H04Q 3/0025 Provisions for signalling
• CPC Class Codes: H04Q 3/0087 Network testing or monitoring arrangements

Abstract

A method for tracing communications includes receiving trace criteria from a first remote element and determining whether a call signaling message matches the trace criteria. The method includes attaching a trace tag to the call signaling message, if the call signaling message matches the trace criteria. The method further includes transmitting the call signaling message to a second remote element.

Claims

1. A method of tracing communications, comprising:

receiving a trace trigger request from a management node, the trace trigger request comprising a unique identifier, trace scope parameters, trace criteria, and report parameters;

receiving a call signaling message;

determining whether the call signaling message matches the trace criteria; and

attaching a trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag comprising the unique identifier.

2. The method of claim 1, wherein receiving the trace trigger request further comprises receiving the unique identifier, wherein the unique identifier comprises:

a requester domain name specifying a domain of the management node; and

a requester identifier specifying an address of the management node with the domain; and

further comprising transmitting a trace report to the management node based on the requester domain name and the requester identifier.

3. The method of claim 1, wherein receiving the trace trigger request further comprises receiving the unique identifier, wherein the unique identifier comprises:

a request identifier specifying trace parameters from which the trace trigger request was generated; and

a request time specifying a time at which the management node received the trace parameters; and

further comprising transmitting a trace report to the management node that includes the request identifier and the request time.

4. The method of claim 1, wherein receiving the trace trigger request further comprises receiving the trace trigger request at a tracing node, and wherein the unique identifier comprises a trace sequence number associated with the tracing node.

5. The method of claim 1, wherein attaching a trace tag to the call signaling message further comprises attaching a call identifier to the call signaling message, and wherein the call identifier uniquely identifies a call with which the call signaling message is associated.

6. The method of claim 1, wherein the trace criteria includes trace parameter criteria, the trace parameter criteria identifying a parameter and a parameter value, and wherein determining whether the call signaling message matches the trace criteria comprises determining whether the identified parameter of the call signaling message matches the identified parameter value.

7. The method of claim 1, wherein the trace criteria includes trace sub-parameter criteria, the trace sub-parameter criteria identifying a sub-parameter and a sub-parameter value, and wherein determining whether the call signaling message matches the trace criteria further comprises determining whether the identified sub-parameter of the call signaling message matches the identified sub-parameter value.

8. The method of claim 1, wherein the trace criteria includes a trace message type and wherein determining whether the call signaling message matches the trace criteria further comprises determining whether a message type of the call signaling message matches the trace message type.

9. The method of claim 1, wherein the trace criteria includes a trace protocol type and wherein determining whether the call signaling message matches the trace criteria further comprises determining whether a protocol type of the call signaling message matches the trace protocol type.

10. The method of claim 1, wherein the trace criteria further includes a trace event trigger that specifies a condition, and wherein determining whether the call signaling message matches the trace criteria further comprises:

determining whether the trace event trigger is satisfied; and

determining, if the trace event trigger is satisfied, whether the call signaling message matches the trace criteria.

11. The method of claim 1, wherein the trace criteria further includes a trace start time and a trace stop time, and wherein determining whether the call signaling message matches the trace criteria further comprises:

determining whether a current time is between the trace start time and the trace stop time; and

determining, if the current time is between the trace start time and the trace stop time, whether the call signaling message matches the trace criteria.

12. The method of claim 1, wherein attaching the trace tag further comprises:

initializing a trace call counter, and

attaching the trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag including the trace call counter.

13. The method of claim 1, wherein the trace trigger request further comprises trace scope parameters that identify a protocol stain;

and wherein attaching the trace tag further comprises attaching the trace tag to the call signaling message if the call signaling message matches the trace criteria and a protocol of the call signaling message matches the protocol stain.

14. The method of claim 1, wherein the trace scope parameters further identify a report protocol;

and

further comprising transmitting a report to a remote element if the call signaling message matches the trace criteria and the protocol of the call signaling message matches the report protocol.

15. The method of claim 1, wherein the trace trigger request further comprises a frequency indicator and wherein receiving a call signaling message comprises receiving a plurality of call signaling messages and wherein attaching the trace tag to the call signaling message further comprises attaching the trace tag to particular call signaling messages that match the trace criteria at a frequency determined based on the frequency indicator.

16. A device for tracing communications, comprising:

a management interface module operable to receive a trace trigger request from a management node, the trace trigger request comprising a unique identifier, trace scope parameters, trace criteria, and report parameters;

a call control module operable to receive a call signaling message;

a filter module operable to determine whether the call signaling message matches the trace criteria; and

a tagging module operable to attach a trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag comprising the unique identifier.

17. The device of claim 16, wherein the unique identifier comprises:

a requester domain name specifying a domain of the management node; and

a requestor identifier specifying an address of the management node with the domain; and

further comprising a reporting module operable to transmit, if the call signaling message matches the trace criteria, a trace report to the management node based on the requester domain name and the requester identifier.

18. The device of claim 16, wherein the unique identifier comprises:

a request identifier specifying trace parameters from which the trace trigger request was generated; and

a request time specifying a time at which the management node received the trace parameters; and

further comprising a reporting module operable to transmit a trace report to the management node that includes the request identifier and the request time.

19. The device of claim 16, wherein the management interface module is further operable to receive the trace trigger request that includes the unique identifier, wherein the unique identifier comprises a trace sequence number associated with the device.

20. The device of claim 16, wherein the tagging module is further operable to attach a trace tag to the call signaling message by attaching a call identifier to the call signaling message, and wherein the call identifier uniquely identifies a call with which the call signaling message is associated.

21. The device of claim 16, wherein the trace criteria includes trace parameter criteria, the trace parameter criteria identifying a parameter and a parameter value, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether the identified parameter of the call signaling message matches the identified parameter value.

22. The device of claim 16, wherein the trace criteria includes trace sub-parameter criteria, the trace sub-parameter criteria identifying a sub-parameter and a sub-parameter value, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether the identified sub-parameter of the call signaling message matches the identified sub-parameter value.

23. The device of claim 16, wherein the trace criteria includes a trace message type and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether a message type of the call signaling message matches the trace message type.

24. The device of claim 16, wherein the trace criteria includes a trace protocol type and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether a protocol type of the call signaling message matches the trace protocol type.

25. The device of claim 16, wherein the trace criteria further includes a trace event trigger that specifies a condition, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by:

determining whether the trace event trigger is satisfied; and

determining, if the trace event trigger is satisfied, whether the call signaling message matches the trace criteria.

26. The device of claim 16, wherein the trace criteria further includes a trace start time and a trace stop time, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by:

determining whether a current time is between the trace start time and the trace stop time; and

determining, if the current time is between the trace start time and the trace stop time, whether the call signaling message matches the trace criteria.

27. The device of claim 16, wherein the tagging module is further operable to attach the trace tag by:

initializing a trace call counter, and

attaching the trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag including the trace call counter.

28. The device of claim 16, wherein the trace trigger request further comprises trace scope parameters that identify a protocol stain;

and wherein the tagging module is further operable to attach the trace tag by attaching the trace tag to the call signaling message, if the call signaling message matches the trace criteria and a protocol of the call signaling message matches the protocol stain.

29. The device of claim 16, wherein the trace scope parameters further identify a report protocol, and wherein the tagging module is further operable to transmit a report to a remote element, if the call signaling message matches the trace criteria and the protocol of the call signaling message matches the report protocol.

30. The device of claim 16, wherein:

the trace trigger request further comprises a frequency indicator;

the call control module is operable to receive a call signaling message by receiving a plurality of call signaling messages; and

the tagging module is operable to attach the trace tag to the call signaling message by attaching the trace tag to particular call signaling messages that match the trace criteria at a frequency determined based on the frequency indicator.

31. A computer program stored on a computer readable medium, the computer program operable to:

receive a trace trigger request from a management node, the trace trigger request comprising a unique identifier, trace scope parameters, trace criteria, and report parameters;

receive a call signaling message;

determine whether the call signaling message matches the trace criteria; and

attach a trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag comprising the unique identifier.

32. The computer program of claim 31, wherein the computer program is further operable to receive the trace trigger request by receiving the unique identifier, wherein the unique identifier comprises:

a requester domain name specifying a domain of the management node; and

a requester identifier specifying an address of the management node with the domain; and

wherein the computer program is further operable to transmit, if the call signaling message matches the trace criteria, a trace report to the management node based on the requester domain name and the requester identifier.

33. The computer program of claim 31, wherein the computer program is further operable to receive the trace trigger request by receiving the unique identifier, wherein the unique identifier comprises:

a request identifier specifying trace parameters from which the trace trigger request was generated; and

a request time specifying a time at which the management node received the trace parameters; and

wherein the computer program is further operable to transmit a trace report to the management node that includes the request identifier and the request time.

34. The computer program of claim 31, wherein the computer program is further operable to receive the trace trigger request by receiving the trace trigger request at a tracing node and wherein the unique identifier comprises a trace sequence number associated with the tracing node.

35. The computer program of claim 31, wherein the computer program is further operable to attach a trace tag to the call signaling message by attaching a call identifier to the call signaling message, and wherein the call identifier uniquely identifies a call with which the call signaling message is associated.

36. The computer program of claim 31, wherein the trace criteria includes trace parameter criteria, the trace parameter criteria identifying a parameter and a parameter value, and wherein the computer program is further operable to determine whether the call signaling message matches the trace criteria by determining whether the identified parameter of the call signaling message matches the identified parameter value.

37. The computer program of claim 31, wherein the trace criteria includes trace sub-parameter criteria, the trace sub-parameter criteria identifying a sub-parameter and a sub-parameter value, and wherein the computer program is further operable to determine whether the call signaling message matches the trace criteria by determining whether the identified sub-parameter of the call signaling message matches the identified sub-parameter value.

38. The computer program of claim 31, wherein the trace criteria includes a trace message type and wherein the computer program is further operable to determine whether the call signaling message matches the trace criteria by determining whether a message type of the call signaling message matches the trace message type.

39. The computer program of claim 31, wherein the trace criteria includes a trace protocol type and wherein the computer program is further operable to determine whether the call signaling message matches the trace criteria by determining whether a protocol type of the call signaling message matches the trace protocol type.

40. The computer program of claim 31, wherein the trace criteria further includes a trace event trigger that specifies a condition, and wherein the computer program is further operable to determine whether the call signaling message matches the trace criteria by:

determining whether the trace event trigger is satisfied; and

determining, if the trace event trigger is satisfied, whether the call signaling message matches the trace criteria.

41. The computer program of claim 31, wherein the trace criteria further includes a trace start time and a trace stop time, and wherein the computer program is further operable to determine whether the call signaling message matches the trace criteria by:

determining whether a current time is between the trace start time and the trace stop time; and

determining, if the current time is between the trace start time and the trace stop time, whether the call signaling message matches the trace criteria.

42. The computer program of claim 31, wherein the computer program is further operable to attach the trace tag by:

initializing a trace call counter, and

attaching the trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag including the trace call counter.

43. The computer program of claim 31, wherein the trace trigger request further comprises trace scope parameters that identify a protocol stain;

and wherein the computer program is further operable to attach the trace tag by attaching the trace tag to the call signaling message, if the call signaling message matches the trace criteria and a protocol of the call signaling message matches the protocol stain.

44. The computer program of claim 31, wherein the trace scope parameters further identify a report protocol, and wherein the computer program is further operable to transmit a report to a remote element, if the call signaling message matches the trace criteria and the protocol of the call signaling message matches the report protocol.

45. The computer program of claim 31, wherein the trace trigger request further comprises a frequency indicator, and wherein the computer program is operable to:

receive a call signaling message by receiving a plurality of call signaling messages; and

attach the trace tag to the call signaling message by attaching the trace tag to particular call signaling messages that match the trace criteria at a frequency determined based on the frequency indicator.

46. A system for tracing communications, comprising:

a management node, operable to transmit trace trigger requests to one or more remote elements; and

a tracing node, comprising;

a management interface module operable to receive a trace trigger request from a management node, the trace trigger request comprising a unique identifier, trace scope parameters, trace criteria, and report parameters;

a call control module operable to receive a call signaling message;

a filter module operable to determine whether the call signaling message matches the trace criteria; and

a tagging module operable to attach a trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag comprising the unique identifier.

47. The system of claim 46, wherein the unique identifier comprises:

a requestor domain name specifying a domain of the management node; and

a requester identifier specifying an address of the management node with the domain; and

wherein the tracing node further comprises a reporting module operable to transmit, if the call signaling message matches the trace criteria, a trace report to the management node based on the requester domain name and the requestor identifier.

48. The system of claim 46, wherein the unique identifier comprises:

a request identifier specifying trace parameters from which the trace trigger request was generated; and

a request time specifying a time at which the management node received the trace parameters; and

wherein the tracing node further comprises a reporting module operable to transmit a trace report to the management node that includes the request identifier and the request time.

49. The system of claim 46, wherein the management interface module is further operable to receive the trace trigger request that includes the unique identifier, wherein the unique identifier comprises a trace sequence number associated with the device.

50. The system of claim 46, wherein the tagging module is further operable to attach a trace tag to the call signaling message by attaching a call identifier to the call signaling message, and wherein the call identifier uniquely identifies a call with which the call signaling message is associated.

51. The system of claim 46, wherein the trace criteria includes trace parameter criteria, the trace parameter criteria identifying a parameter and a parameter value, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether the identified parameter of the call signaling message matches the identified parameter value.

52. The system of claim 46, wherein the trace criteria includes trace sub-parameter criteria, the trace sub-parameter criteria identifying a sub-parameter and a sub-parameter value, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether the identified sub-parameter of the call signaling message matches the identified sub-parameter value.

53. The system of claim 46, wherein the trace criteria includes a trace message type and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether a message type of the call signaling message matches the trace message type.

54. The system of claim 46, wherein the trace criteria includes a trace protocol type and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by determining whether a protocol type of the call signaling message matches the trace protocol type.

55. The system of claim 46, wherein the trace criteria further includes a trace event trigger that specifies a condition, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by:

determining whether the trace event trigger is satisfied; and

determining, if the trace event trigger is satisfied, whether the call signaling message matches the trace criteria.

56. The system of claim 46, wherein the trace criteria further includes a trace start time and a trace stop time, and wherein the filter module is further operable to determine whether the call signaling message matches the trace criteria by:

determining whether a current time is between the trace start time and the trace stop time; and

determining, if the current time is between the trace start time and the trace stop time, whether the call signaling message matches the trace criteria.

57. The system of claim 46, wherein the tagging module is further operable to attach the trace tag by:

initializing a trace call counter, and

attaching the trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag including the trace call counter.

58. The system of claim 46, wherein the trace trigger request further comprises trace scope parameters that identify a protocol stain;

and wherein the tagging module is further operable to attach the trace tag by attaching the trace tag to the call signaling message, if the call signaling message matches the trace criteria and a protocol of the call signaling message matches the protocol stain.

59. The system of claim 46, wherein the trace scope parameters further identify a report protocol, and wherein the tagging module is further operable to transmit a report to a remote element, if the call signaling message matches the trace criteria and the protocol of the call signaling message matches the report protocol.

60. The system of claim 46, wherein:

the trace trigger request further comprises a frequency indicator;

the call control module is operable to receive a call signaling message by receiving a plurality of call signaling messages; and

the tagging module is operable to attach the trace tag to the call signaling message by attaching the trace tag to particular call signaling messages that match the trace criteria at a frequency determined based on the frequency indicator.

61. A system of tracing communications, comprising:

means for receiving a trace trigger request from a management node, the trace trigger request comprising a unique identifier, trace scope parameters, trace criteria, and report parameters;

means for receiving a call signaling message;

means for determining whether the call signaling message matches the trace criteria; and

means for attaching a trace tag to the call signaling message if the call signaling message matches the trace criteria, the trace tag comprising the unique identifier.