EFFICIENT PERFORMANCE MONITORING USING IPv6 CAPABILITIES

• US 20080159287A1
• Filed: 12/29/2006
• Published: 07/03/2008
• Est. Priority Date: 12/29/2006
• Status: Abandoned Application

• Current Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Nagarajan, Ramesh, Rege, Kiran M., Parekh, Shyam P.
• Application Number:
  US11/617,837
• Publication Number:
  US 20080159287A1
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

The present invention provides a method for obtaining and reporting performance information on node-to-node data transfers, i.e., network hops, based on integrated capabilities in Internet Protocol version 6 (IPv6), specifically extension headers. The performance of a (real-time) data flow is monitored between a source-destination pair by inserting specific information in an extension header of select data packets in the data flow. By initiating an extension header at a source client, and updating the extension header at any intermediate nodes along the source-destination path, a destination node can produce a detailed set of statistics relating to the current performance level of select nodes in a network based upon the reported data in the extension header. Additionally, data flow performance can be monitored on any desired network path or segment independent of particular flows on those paths.

Claims

1. A method of monitoring and recording performance levels of a data network, the method comprising the steps of:

(1) initiating a data flow at a source node;

(2) forwarding said data flow through said network from said source node to said destination node;

(3) recording statistical information at said destination node, said information relating to a current performance level of said network.

2. The method of claim 1, wherein said step (1) further comprises including an extension header in a packet of said data flow, said extension header specifying performance information to be collected at each node in said network.

3. The method of claim 2, wherein step (2) further comprises updating said extension header at any intermediate node along a route between said source node and said destination node, said updating including adding said performance information as specified by said extension header.

4. The method of claim 3, wherein said step (3) comprises recording at said destination node said performance information for each intermediate node.

5. The method of claim 4, wherein said performance information comprises data from which can be derived end-to-end packet delay, per-hop packet delay, packets received, consecutive packet loss, total packet loss, and packet jitter.

6. The method of claim 5, wherein said data flow is initiated as a test flow and contains no payload.

7. The method of claim 2, wherein said extension header is a hop-by-hop extension header as defined by Internet Protocol version 6.

8. A method for monitoring performance levels of individual nodes on a source-destination path in a data network, the method comprising the steps of:

(1) initiating at a source node a data flow to be delivered to a destination node, said data flow periodically including a packet with an extension header for reporting performance information;

(2) forwarding packets associated with said data flow to said destination node through said data network;

(3) determining at said destination node statistical information relating to a current performance level of said network.

9. The method of claim 8, wherein said extension header specifies performance information to be collected at each node in said network.

10. The method of claim 9, wherein step (2) further comprises updating said extension header at any intermediate node along a route between said source node and said destination node, said updating including adding said performance information corresponding to said intermediate node as specified by said extension header.

11. The method of claim 10, wherein step (3) comprises recording at said destination node said performance information for each intermediate node.

12. The method of claim 11, where said recorded performance information is distributed to at least one other node in said data network.

13. The method of claim 11, wherein said performance information comprises data from which can be derived end-to-end packet delay, per-hop packet delay, packets received, consecutive packet loss, total packet loss, and packet jitter.

14. The method of claim 13, wherein said data flow is initiated as a test flow and contains no payload.

15. The method of claim 8, wherein said extension header is a hop-by-hop extension header as defined by Internet Protocol version 6.

16. A data structure embodied on a computer readable medium, said data structure comprising a hop-by-hop extension header as defined by Internet Protocol version 6, said extension header comprising:

an option type field for reporting a type of said extension header;

an option length field for reporting the length of said extension header;

a sequence number field for indicating a position of a packet in a data flow;

a number of node reports field for indicating a number of nodes in a network that have contributed data to said extension header;

a number metrics field for indicating a number of pieces of data to be reported in said extension header;

a node position field for indicating a position of reporting node in said network;

identifier fields for indicating the types of data to be reported in said extension header; and

data fields for reporting actual data corresponding to said identifier fields.

17. The data structure of claim 16, wherein said identifier fields comprise:

a node address field for indicating a physical address of a reporting node;

a timestamp field for indicating a time when a reporting node processes said data packet;

a packet count field for indicating a total number of packets received at a reporting node;

a total packet loss field for indicating a total number of packets lost at each reporting node;

a consecutive packet loss field for indicating a consecutive number of packets lost at each reporting node; and

a per hop jitter field for indicating the delay jitter at each reporting node.

18. The data structure of claim 17, wherein there is at least one data field corresponding to each identifier field, said data field containing the physical value of the statistic indicated by said identifier field.