Decentralized SLS monitoring for throughput in a differentiated service environment
A decentralized SLS monitoring structure ( 30 ) includes a measurement preparation and minimization module ( 32 ), measurement launching coordination module ( 34 ), measurement scheduler module ( 36 ) and measurement initialization and results module ( 38 ). The monitoring structure ( 30 ) prepares throughput tests to be performed on measurement engines ( 50 ), including a tapper ( 52 ) for splitting the data flow, packet collector ( 54 ) for time stamping packet headers, packet filter ( 56 ) for filtering packets according to a flow definition and packet recorder ( 58 ) for providing information to the measurement initialization and results module ( 38 ) for computing throughput.
1. A measurement engine configured for use in a decentralized service level specification (SLS) monitoring device, with the SLS monitoring device including measurement initialization and result module, said measurement engine comprising:
a tapper connected to an egress node and a packet collector, said tapper configured to receive a data stream with the data stream including data packets, said tapper further configured to copy the data stream and further configured to send the data stream to each of said egress node and said packet collector, said tapper further configured to determine if a received data packet from the received data stream is complete and to discard the received data packet if the determination is made that the data packet was not complete;
said packet collector configured to copy headers from the data packets from the received data stream, said packet collector further configured to add a time stamp to create at least one packet header record;
a packet filter connected to said packet collector, said packet collector further for passing said at least one packet header record to said packet filter, said packet filter for comparing said received at least one packet header record with predefined definitions; and
a flow recorder connected to said packet filter, said packet filter configured to send said at least one packet header record to said flow recorder if the comparison of said at least one packet header record with the predefined definitions is a match;
wherein the packet collector is configured to locate a beginning of each one of a plurality of link data frames of the data stream, to extract a packet therefrom thereby providing said data packets, and to place a copy of a header of each one of said data packets in a respective packet header record along with the time stamp and wherein the time stamp indicates a time that the packet was received by the packet collector;
wherein the packet header record includes an interface ID field indicating a physical interface that the measurement engine monitors, a link layer information field that provides information regarding a link layer protocol, a packet header field containing the copy of the packet header, and a time stamp field having the time stamp stored therein.
2. The measurement engine as recited in claim 1 , wherein the time stamp added by said packet collector indicating the time the data packed was received by said tapper.
3. The measurement engine as recited in claim 2 , wherein the data packet header includes at least one of an interface identification field, a link layer information field, a time stamp filed.
4. The measurement engine as recited in claim 1 , wherein the packet falter includes a flow filter profile used thereby to determine which ones of said data packets will be counted for a throughput measurement.
5. The measurement engine as recited in claim 4 , wherein the filter profile is used to match a header record of at least a portion of said data packets to an associated traffic flow.
6. The measurement engine as recited in claim 5 wherein, a filter profile description field of the filter profile specifies all attributes needed for matching one of said data packets to an associated traffic flow.