CN1992651A - Implementation method for detecting multicast performance of Ethernet - Google Patents

Abstract

The invention relates to a method for realizing network multicast performance detection. The present invention mainly includes: first, constructing and sending a multicast performance measurement request message containing identification information at the test initiation point; then, each node receiving the multicast performance measurement message sends the A performance measurement response message with identification information; finally, within a predetermined time, the test initiation point receives the performance measurement response message, and measures the multicast performance parameter according to the identification information in the received message. The present invention has little changes to the OAM frame format defined by Y.17ethoam, and in the implementation process of the present invention, the processing flow at the sending point and the receiving point is relatively simple, and the calculation method based on the original unicast performance measurement is adopted to perform Calculation method for multicast performance measurement. Therefore, the present invention can well realize P2MP multicast performance parameter measurement in Ethernet OAM, thereby assisting OAM to provide more comprehensive network performance evaluation.

Description

Realization Method of Detecting Ethernet Multicast Performance

technical field

The invention relates to the technical field of network communication, in particular to a multicast performance detection technology in Ethernet OAM (operation management and maintenance).

Background technique

With the development of network communication technology, Ethernet (Ethernet) technology gradually develops from local area network to metropolitan area network with its high cost performance advantage, and its port rate also develops from 10M to 10G. In the process of the development of Ethernet to the metropolitan area network, it is required that the Ethernet technology must meet the carrier-class network requirements. Among them, OAM is the basic requirement of carrier-class network for various technologies. The corresponding OAM mainly includes a network fault management mechanism and a network performance management mechanism.

Currently, fault/performance management mechanisms for the ETH network include:

Based on the ETH-CC (Ethernet Connectivity Check) continuity detection function, it is used to detect the connectivity between ETHMEPs;

Based on the ETH-LB (Ethernet Loopback) loopback function, it is used for connectivity detection between MEP (maintenance domain endpoint) and MIP (maintenance domain intermediate node)/MEP, as well as frame delay and frame delay jitter measurement in performance parameters ;

ETH-LT (Ethernet Link Tracking) function for fault location;

Alarm indication function based on ETH-AIS (Ethernet Alarm Indication Signal) and ETH-RDI (Ethernet Reverse Defect Indication), used for fault alarm forward/reverse suppression;

ETH-LM (Ethernet frame loss measurement) function, used to measure the frame loss rate in performance parameters;

ETH-DM (Ethernet Frame Delay Measurement) function for measuring delay in performance parameters.

In the Y.17ethoam (Y.17 Ethernet OAM) fault management function, the ETH-CC and ETH-LB functions can be implemented in multicast mode, but the multicast implementation of the ETH-LT function is difficult. Therefore, there is no Define multicast ETH-LT.

Moreover, in the Y.17ethoam performance management function, the definition and measurement of network performance parameters such as FLR (frame loss rate), FD (frame delay) and FDV (frame delay jitter) are all based on unicast point-to-point (Point to Point, P2P ), performance parameters and measurements for multicast are not yet available.

With the development of Ethernet technology, some types of Ethernet (such as IEEE 802.3) are inherently suitable for multicast, so that Ethernet-based multicast services will gradually be widely used in Ethernet. For this reason, it is necessary to carry out Measurement of Ethernet multicast performance parameters to measure the multicast performance of Ethernet.

In Draft4 (Draft 4) of MEF10-Ethernet Service Attribute (Metropolitan Ethernet Forum 10-Ethernet Service Attribute), the performance parameters between multiple points are defined, specifically expressed as a vector, and each element of the vector represents multiple A performance parameter between a pair of nodes in a peer group.

At present, there is another implementation method that uses a set of performance parameters of multiple unicast paths to represent performance parameters between multiple points.

For example, assuming that there are 3 nodes in the network, a, b and c, then the network performance parameters between multiple points in the multi-point network are expressed as vectors:

(1) {FLR(a, b), FLR(c, b), FLR(a, c)} represents the frame loss performance between multiple points of the network;

(2) {FD(a, b), FD(c, b), FD(a, c)} represents the frame delay performance between multiple points of the network;

(3) {FDV(a, b), FDV(c, b), FDV(a, c)} represents the frame delay variation performance between multiple points of the network.

Of course, when there are many nodes in the network, the elements of the vector will also increase greatly. At this time, it is impossible to save all the elements. As OAM, only the maximum value, minimum value and average value are needed, that is, therefore, the corresponding The network performance parameters of can be expressed as:

(1) FLR{Ma×(maximum value), Min(minimum value), Average(average value)}, frame loss parameter between multiple points;

(2) FD (Max, Min, Average), the frame delay parameter between multiple points;

(3) FDV (Max, Min, Average), frame variation parameters between multiple points.

In a word, there is already a definition of network performance parameters between multiple points at present, but the corresponding performance parameters between multiple points are defined based on multiple unicast performance parameters between two points. Therefore, based on this definition, the obtained The network performance parameters corresponding to the corresponding unicast network performance parameters.

However, since it is very difficult to collect the network performance parameter values between all two points on the OAM plane, it is actually impossible to detect and obtain the above-mentioned network performance parameters between multiple points based on the definition between single points on the OAM plane .

In addition, as shown in Figure 1, since the multicast path of P2MP is not necessarily the same as its various unicast paths; moreover, to complete the function of multicast communication in unicast communication, the communication traffic must be copied one by one in turn, while multicast communication However, because in the upstream of the multicast, only one copy of the traffic may be sent, and the traffic is only copied at the fork point, so that the multicast communication will relatively use less network resources. Therefore, the timeliness of multicast communication constructed directly using multicast communication and unicast communication using multiple unicast paths is also different. This makes it unsuitable for the specific environment of P2MP (point-to-multipoint) multicast communication to use the unicast network performance parameters of multiple point-to-multipoint unicast paths to measure the network communication performance of P2MP multicast communication.

Therefore, the definition and measurement of performance parameters of P2MP multicast communication must be realized based on multicast paths. However, there is no feasible method for detecting network performance parameters based on multicast at present.

Contents of the invention

The purpose of the present invention is to provide a method for detecting Ethernet multicast performance, thereby effectively detecting and determining the performance parameters of point-to-multipoint multicast networks in Ethernet, and assisting Ethernet OAM to provide comprehensive network performance evaluation.

The purpose of the present invention is achieved through the following technical solutions:

The invention provides a method for detecting network multicast performance, including:

A. Construct and send a multicast performance measurement request message containing identification information at the test initiation point;

B. Each node receiving the multicast performance measurement message sends a performance measurement response message including the identification information to the test initiation point respectively;

C. The test initiation point receives the performance measurement response message, and measures the multicast performance parameter according to the identification information in the received message.

Described step A comprises:

When implementing Ethernet operation management and OAM maintenance, a multicast request frame using a multicast media access control MAC address is constructed and sent at the test initiation point, and the request frame carries multicast performance measurement operation code information and corresponding Identification information.

Described step A comprises:

A1. When performing frame loss measurement, build a multicast request frame using a multicast MAC address at the test initiation point, and include the multicast frame loss measurement request opcode and forward frame counter value information in the request frame and identification information;

and / or,

A2. When performing frame delay measurement, build a multicast request frame using a multicast MAC address at the test initiation point, and include the multicast frame delay measurement request opcode, forward sending timestamp information and Identification information.

The identification information includes:

Transaction ID in the Ethernet OAM packet.

Described step B comprises:

B1. When performing frame loss measurement, construct a multicast response frame at the node receiving the multicast request, and include the identification information, the multicast frame loss measurement response opcode, and the forward sending frame counter in the request frame in the response frame value information and the forward receiving frame counter value information of the receiving node, and send the multicast response frame after delaying a predetermined random delay time;

and / or,

B2. When performing frame delay measurement, construct a multicast response frame at the node receiving the multicast request, and include the identification information, the multicast frame delay measurement response opcode, and the forward transmission time stamp in the request frame in the response frame information and send it.

Described step B2 specifically comprises:

When frame delay measurement is performed, a multicast response frame is constructed at the node receiving the multicast request, and the response frame includes the identification information, the multicast frame delay measurement response opcode, the forward sending timestamp information in the request frame, and The receiving node forwardly receives the time stamp information, and after delaying for a predetermined random delay time, writes the backward sending time stamp of the receiving node into the multicast response frame and sends it.

Described step C comprises:

Within a predetermined time, the test initiation point receives the performance measurement response message, and measures the multicast performance parameter according to the identification information in the received message.

Also include before described step C:

Before testing multicast request frames, initialize the frame loss value and/or frame delay value.

The frame loss value includes: the minimum frame loss value, the maximum frame loss value and/or the total frame loss value, and the value of the multicast group size;

and / or,

The frame delay value includes: the minimum frame delay value, the maximum frame delay value and/or the total frame delay value, and the value of the multicast group size.

Described step C specifically comprises:

C1. When performing frame loss measurement, the test initiation point calculates the frame loss according to the forward sending frame counter value and the forward receiving frame counter value in two multicast response frames of the same identification information received continuously within a predetermined time value, and update the minimum frame loss value, the maximum frame loss value and/or the total frame loss value and the value of the multicast group size according to the frame loss value;

and / or,

C2. When performing frame delay measurement, the test initiation point is within the predetermined time, according to the time of receiving the multicast response frame, as well as the forward sending time stamp information, forward receiving time stamp information and response time stamp information in the multicast response frame The frame delay value is calculated for the sending timestamp information, and the minimum frame delay value, the maximum frame delay value and/or the total frame delay value and the value of the multicast group size are updated according to the frame delay value.

Described step C1 comprises:

The frame loss value is equal to the difference in the Forward Sent Frame Counter values in two consecutively received Multicast Response frames of the same identification information minus the difference in the Forward Received Frame Counter values in two Multicast Response frames, and:

When the frame loss value is less than the minimum frame loss value, update the minimum frame loss value to the frame loss value;

and / or,

When the frame loss value is greater than the maximum frame loss value, update the maximum frame loss value to the frame loss value;

and / or,

The total frame loss value is equal to the sum of the current total frame loss value and the frame loss value, and the value of the multicast group size needs to be increased by one.

Described step C2 comprises:

The frame delay value is equal to the difference between the time of receiving the multicast response frame and the forward sending timestamp information minus the difference between the forward receiving timestamp information and the reverse sending timestamp information, and:

When the frame delay value is less than the minimum frame delay value, the frame delay value is used as the minimum frame delay value;

and / or,

When the frame delay value is greater than the maximum frame delay value, then use the frame delay value as the maximum frame delay value;

and / or,

The total frame delay value is equal to the sum of the current total frame delay value and the frame delay value, and one is added to the value of the multicast group size.

In the present invention, before performing the step C, it also includes:

C0. After the test initiating point receives the multicast response message, if the identification information in it is correct, step C is executed.

Described step C0 also includes:

Determine whether the identification information in the received multicast response message is correct according to the saved effective identification information.

It can be seen from the technical solutions provided by the present invention that the present invention defines multicast performance parameters in Ethernet OAM based on multicast paths, and provides a corresponding detection method for multicast performance parameters. The present invention does not make much change to the OAM frame format defined by Y.17ethoam. Specifically, only 4 message opcodes need to be added. For frame delay measurement, as long as the response frame brings back the forward receiving timestamp and the backward sending timestamp, the difference between the two The difference is sufficient to include random delays made by the receiving point.

Moreover, in the implementation process of the present invention, the processing flow at the sending point and the receiving point is relatively simple, and the calculation method adopted is a calculation method based on the original unicast performance measurement.

Therefore, the present invention can well realize P2MP multicast performance parameter measurement in Ethernet OAM, thereby assisting OAM to provide more comprehensive network performance evaluation.

Description of drawings

Figure 1a is a schematic diagram of a unicast packet transmission process;

Figure 1b is a schematic diagram of a multicast message transmission process;

Fig. 2 is a schematic diagram of the overall specific implementation process of the method of the present invention;

Fig. 3 is the specific implementation process 1 of the method described in the present invention;

Fig. 4 is the specific realization process 2 of the method described in the present invention.

Detailed ways

The core of the present invention is to define the P2MP multicast performance parameter in Ethernet based on the multicast path, and provide P2MP multicast performance measurement support in Ethernet OAM, so as to be the same as the unicast performance parameter, in the OAM plane from frame loss rate, frame delay , Frame delay variation to evaluate Ethernet P2MP multicast performance.

In order to facilitate the understanding of the present invention, specific implementations of the present invention will be described below.

The present invention first needs to define P2MP multicast performance parameters in the specific implementation process, so that the measurement of corresponding performance parameters can be carried out according to the defined content in the subsequent process;

Defining P2MP multicast performance parameters is also implemented from three aspects: frame loss, frame delay and frame delay variation. The P2MP multicast performance parameter is based on the performance parameter of the multicast path, that is, the destination address of the corresponding OAM must be a multicast address, and the size Z of the multicast group needs to be considered in the definition process, and at the same time, the measured Waiting time T. The corresponding performance parameters of each multicast path include: the Max (maximum), Min (minimum) and Average (average) values of each performance parameter. In the process of actually measuring each performance parameter, the corresponding Max, Min and any one or more of Average.

For the performance parameters of the multicast path, only the point-to-multipoint point-to-multicast group direction is meaningful, while the opposite direction is meaningless because it is essentially a unicast mode. However, during measurement, a two-way (two-way) method can usually be used for measurement, that is, measurement values in the opposite direction may be included in the calculation process, but this has no great impact on multicast performance evaluation.

The P2MP multicast performance parameter defined in the present invention is specifically as follows:

(1) P2MP-FLR, defined as (Max, Min, Average) _{Z, T} of each multicast path FLR of P2MP;

(2) P2MP-FD is defined as (Max, Min, Average) _{Z, T} of each multicast path FD of P2MP;

(3) P2MP-FDV is defined as (Max, Min, Average) _{Z, T} of each multicast path FDV of P2MP;

Among the above-mentioned performance parameters, the subscript Z represents the size of the multicast group, which specifically represents the size of the multicast group embodied in real-time measurement, i.e. the number of multicast paths. In the present invention, it is assumed that the size of the multicast group is unpredictable Therefore, for two-way measurement, the measurement initiation point sets the waiting time experience value T, if the reply message arrives within T time, the measurement is valid, and if the waiting time T is exceeded, the measurement reply message can still be received , an alarm is issued, which is specifically realized by using the TransactionID (transmission identification) in the OAM message.

If the OAM function is implemented in hardware, the calculation of Average may require division, which is very difficult for hardware. Therefore, it can be represented by {Max, Min, Total (sum of measured values)} _{Z, T} , where Total represents each The sum of the measured values of the performance parameters of the multicast path. This expression has basically the same meaning as the expression described above. At this time, the storage space of Total must be large enough, usually 64bit.

Based on the definitions of the above multicast performance parameters, the corresponding multicast performance parameter measurement process is as follows:

First, in the latest Y.17ethoam Draft, Nov., 2005, the defined Ethernet OAM general frame header format is shown in Table 1:

Table 1 0 1 2 3 OAM EtherType ME Level Version OpCode HdrLength OpCode Specific Fields ...

In the prior art, for unicast performance measurement, frame loss measurement and frame delay measurement operation codes are defined, specifically as follows:

LMM, frame loss measurement request opcode;

LMR, frame loss measurement response opcode;

DMM, frame delay measurement request opcode;

DMR, Frame Delay Measurement Request opcode.

Based on the operation code of the above-mentioned unicast performance measurement, the present invention sets the operation code of the multicast performance measurement, specifically as follows:

P2MP-LMM, P2MP Multicast Frame Loss Measurement Request opcode;

P2MP-LMR, P2MP Multicast Frame Loss Measurement Response opcode;

P2MP-DMM, P2MP multicast frame delay measurement request opcode;

P2MP-DMR, P2MP Multicast Frame Delay Measurement Response opcode.

The fields included in the measurement frame during multicast performance parameter measurement are as follows:

(1) For frame loss measurement

The unicast LMM frame must contain the TxFCf field, that is, the forward frame counter value, and the P2MP-LMM frame requires the same;

The unicast LMR frame must contain TxFCf, RxFCf and TxFCb fields, that is, the forward sending frame counter value, the forward receiving frame counter value and the backward frame sending counter value, where the TxFCf field is copied from the LMM frame, P2MP-LMM The frame requirements are the same, but only TxFCf, RxFCf are actually used.

(2) For frame delay measurement

The unicast DMM frame must contain the forward sending timestamp TxTimeStampf, and the P2MP-DMM frame requires the same;

The unicast DMR frame must contain the forward sending timestamp TxTimeStampf, which is copied from the DMM frame. For the P2MP-DMM frame, the DMR also needs the forward receiving timestamp RxTimeStampf and the backward sending timestamp TxTimeStampb, and the difference between TxTimeStampb and RxTimeStampf Must include random delays made by the receiving point.

In addition, compared with unicast performance measurement, the two-way measurement in P2MP multicast performance measurement faces two problems:

(1) The multi-point backflow is too large. Therefore, the measurement initiation point is required to send the measurement request message at a very low rate. According to Y.17ethoam, since each sent message is assigned a TransactionID, after the message is sent, the Transaction ID Retain for a period of time to associate reply messages. The retention time is actually the same as the packet sending rate. The retention time is configured according to experience, for example, the default is 5s;

(2) The multi-point backflow is too concentrated, which can be overcome by making the receiving point delay a random time before responding (that is, a random delay). The random delay has a certain range, and the range is also configurable. For example, the default is 1s.

Regardless of measuring frame loss or frame delay, generally speaking, multicast measurement follows roughly the same process, and the corresponding process is shown in Figure 2:

First, the sender sends a multicast measurement request frame, including the measurement operation code, message identification information, and parameter values at the sender’s sending time, such as the forward frame count value needed to measure frame loss, and the forward frame count needed to measure frame delay. Send timestamp to;

Secondly, after receiving the multicast measurement request frame, the receiving end responds, including measurement operation reply, message representation information, parameter values at the receiving end at the receiving end, and parameter values at the sending time of the reply, such as the preamble required for measuring frame loss. Forward receiving frame count value required for receiving, forward receiving timestamp and backward sending timestamp required for measuring frame delay, and the received parameter value is also copied into the reply message and returned, such as measurement frame Forward send frame count value required for loss, forward send timestamp required for measuring frame delay;

Finally, after receiving the reply message, the sender first verifies the validity of the message, mainly to verify whether the message ID is valid, then extracts the parameter value in the message, calculates the parameter value on the path, and finally uses the Calculate and update the multicast performance parameters, including: specific performance parameter values, the sum of the performance parameter values of the multicast group, and the multicast group size, maximum value and/or minimum value, wherein the performance parameter values include Frame loss value and frame delay value.

The difference between frame loss measurement and frame delay measurement is that the calculation formulas for calculating frame loss and frame delay on a single path are different after the sender receives the reply message, which will be described in detail in the following Corresponding explanations are made in the description of FIG. 3 and FIG. 4 .

The measurement process of each multicast performance parameter will be described in detail below with reference to FIG. 3 and FIG. 4 .

(1) P2MP Multicast Frame Loss Measurement (P2MP-LM)

In order to facilitate the description of the frame loss measurement process, the following assumptions are first made:

Assume that the sending interval of sending measurement messages at the sending end is time T, that is, the local Transaction ID retention time. When the time T is exceeded after sending the message, the saved Transaction ID will be deleted. Afterwards, if another transaction ID is received frame, it is considered illegal and an alarm can be issued;

Suppose the random delay range after the receiving point receives the multicast measurement frame, that is, the random delay is R;

Suppose the size of the multicast group measured this time is Z;

Assume that the accumulated frame loss of each multicast path is Total, the minimum frame loss is Min, and the maximum frame loss is Max.

Second, based on the above assumptions, the processing of the corresponding frame loss measurement is as follows:

(1) At the measurement initiation point, construct a P2MP-LM request frame, specifically need to use the multicast MAC address and P2MP-LMM operation code, assign a Transaction ID for the current frame, and fill in the current forward sending frame counter value into the request frame In the TxFCf field, other fields may not be concerned;

(2) The measurement initiation point sends the constructed request frame, and starts the Transaction ID retention timer with a timeout of T, and clears the Z, Total, Min, and Max values at the same time.

(3) At the receiving point, that is, after receiving the frame loss measurement request frame at a certain point in the multicast group, a P2MP-LMR response frame is constructed, specifically, the source MAC address is used as the destination address, and the local MAC address is used as the source Address, the response operation code is P2MP-LMR, copy the Transaction ID and TxRCf into the response frame, and fill in the local forward received frame counter value into the RxFCf field of the response frame, and don’t care about other fields;

(4) Make a random delay within the time R range, that is, send the response frame after the delay time R;

(5) The measurement initiation point calculates the frame loss on a certain path based on two P2MP-LMR frames, and overflow needs to be considered when subtracting the two counter values; assuming the counter values TxFCf1 and RxFCf1 of the previous response frame , the counter values of the currently received response frame are TxFCf2, RxFCf2, then the corresponding processing flow is shown in Figure 3, specifically:

Step 31: According to the Transaction ID value retained in the measurement initiation point, judge whether the Transaction ID in the received response frame is consistent, that is, whether the Transaction ID is valid, if yes, perform step 33, otherwise, perform step 32, and an alarm is generated;

Step 33: Calculate the frame loss value FL as (TxFCf2-TxFCf1)-(RxFCf2-RxFCf1);

Step 34: Calculate the total frame loss value Total as the current Total value plus the FL value, and add 1 to the Z value;

Step 35: judging whether the minimum value Min of the current frame loss is greater than the FD value, if yes, then make Min=FD, otherwise, perform step 36;

Step 36: Judging whether the current maximum frame loss Max is smaller than the FD value, if yes, set Max=FD, otherwise, the process ends.

Based on the processing process from step 31 to step 36 above, wait for the response frame of the same Transaction ID returned at the measurement initiation point for a period of time T, and perform the above processing, and obtain the multicast performance of frame loss when the time T is reached The value of the parameter.

(2) P2MP Multicast Frame Delay Measurement (P2MP-DM)

Similarly, in order to facilitate the description of the frame delay measurement process, the following assumptions are first made:

Assume that the sending interval of sending measurement messages at the sending end is time T, that is, the local Transaction ID retention time. When the time T is exceeded after sending the message, the saved Transaction ID will be deleted. Afterwards, if another transaction ID is received frame, it is considered illegal and an alarm can be issued;

Suppose the random delay range after the receiving point receives the multicast measurement frame, that is, the random delay is R;

Suppose the size of the multicast group measured this time is Z;

Assume that the accumulated frame loss of each multicast path is Total, the minimum frame loss is Min, and the maximum frame loss is Max.

Second, based on the above assumptions, the processing of the corresponding frame delay measurement is as follows:

(1) At the measurement initiation point, build a P2MP-DM request frame. Specifically, you need to use the multicast MAC address and the P2MP-DMM request operation code to assign a Transaction ID to the current frame, and fill in the current forward sending timestamp in the request frame. In the TxTimeStampf field, other fields may not be concerned;

(2) Send a request frame at the measurement initiation point, and start the Transaction ID retention timer, the timeout length is T, and clear the Z, Total, Min, and Max values at the same time.

(3) At the receiving point, that is, after a certain point in the multicast group receives the frame loss measurement request frame, it constructs a P2MP-DMR response frame. Specifically, the source MAC address is used as the destination address, and the local MAC address is used as the source Address, the response operation code is P2MP-DMR, copy the Transaction ID and TxTimeStampf into the response frame, and fill in the local forward receiving timestamp into the RxTimeStampf of the response frame;

(4) At the receiving point, do a random delay within the time R range, that is, after delaying for R time, fill in the backward sending timestamp into the TxTimeStampb field of the response frame and send the response frame immediately;

(5) After the measurement initiating point receives the response frame, set the receiving time as RxTimeb, then the corresponding processing flow is as shown in Figure 4, specifically including:

Step 41: Judging whether the Transaction ID in the received response frame is consistent according to the Transaction ID value retained in the measurement initiation point, that is, whether the Transaction ID is valid, if yes, then perform step 43, otherwise, perform step 42, and an alarm is generated;

Step 43: Calculate the frame delay time FD as RxTimeb-TxTimeStampf-(RxTimeStampf-TxTimeStampb);

Step 44: Calculate the total frame delay time Total as the current Total value plus the FD value, and add 1 to the Z value;

Step 45: judging whether the minimum value Min of the current frame delay time is greater than the FD value, if yes, then make Min=FD, otherwise, perform step 46;

Step 46: Judging whether the maximum value of the current frame delay time Max is smaller than the FD value, if yes, set Max=FD, otherwise, the process ends.

Based on the processing from step 41 to step 46 above, wait for the response frame of the same Transaction ID returned at the measurement initiation point for a period of time T, and perform the above processing, and obtain the multicast performance of frame delay when time T is reached The value of the parameter.

In summary, the implementation method of defining the multicast performance parameters in the Ethernet OAM based on the multicast path and then carrying out the detection of the Ethernet multicast performance parameters provided by the present invention has little change to the OAM frame format defined by Y.17ethoam , only need to add 4 message codes, for the frame delay measurement, as long as the response frame brings back the forward receiving timestamp and the backward sending timestamp, the difference between the two includes the random delay made by the receiving point. The processing flow of the sending point and the receiving point is not complicated, and is based on the calculation method of the original unicast performance measurement. Therefore, the invention can well realize the measurement of P2MP multicast performance parameters in the Ethernet OAM.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present invention can easily think of changes or Replacement should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (14)

1, a kind of implementation method that detects the network multicast performance is characterized in that, comprising:

A, initiate the some structure and send the multicast performance that comprises identification information to measure request message in test;

Each node of B, the described multicast performance measured message of reception is initiated point to test respectively and is sent the performance measurement response message that comprises described identification information;

C, test are initiated point and are received described performance measurement response message, and measure the multicast performance parameter according to the identification information that receives in the message.

2, the implementation method of detection network multicast performance according to claim 1 is characterized in that, described steps A comprises:

When realizing that ethernet operation administers and maintains OAM, initiate the some structure and send the multicast claim frame that adopts multicast media access control MAC address in test, carrying multicast performance measuring operation sign indicating number information and corresponding identification information in the described request frame.

3, the implementation method of detection network multicast performance according to claim 2 is characterized in that, described steps A comprises:

A1, when carrying out LOF and measure, initiate point in test and make up a multicast claim frame that adopts the multicast MAC Address, and in described claim frame, comprise the multicast LOF and measure request operation code, forward direction transmit frame Counter Value information and identification information;

And/or,

A2, when carrying out frame delay when measuring, initiate point in test and make up a multicast claim frame that adopts the multicast MAC Address, and comprise in described claim frame that the multicast frame delay is measured request operation code, the forward direction transmitting time is stabbed information and identification information.

4, the implementation method of detection network multicast performance according to claim 3 is characterized in that, described identification information comprises:

Transmission sign Transaction ID in the Ethernet OAM message.

5, the implementation method of detection network multicast performance according to claim 3 is characterized in that, described step B comprises:

B1, when carrying out LOF and measure, make up the multicast response frame at the node that receives the multicast request, in response frame, comprise described identification information, multicast LOF and measure the forward direction transmit frame Counter Value information in operation response sign indicating number, the claim frame and the forward direction received frame Counter Value information of receiving node, and after postponing predetermined random delay time, send this multicast response frame;

And/or,

B2, when carrying out frame delay when measuring, make up the multicast response frame at the node that receives the multicast request, in response frame, comprise described identification information, multicast frame delay and measure forward direction transmitting time in operation response sign indicating number, the claim frame and stab information and send.

6, the implementation method of detection network multicast performance according to claim 5 is characterized in that, described step B2 specifically comprises:

When carrying out the frame delay measurement, make up the multicast response frame at the node that receives the multicast request, in response frame, comprise the forward direction time of reception stamp information that the forward direction transmitting time in described identification information, multicast frame delay measurement operation response sign indicating number, the claim frame is stabbed information and receiving node, and after postponing predetermined random delay time, the back stamp to transmitting time of receiving node write in the multicast response frame, and send.

According to the implementation method of each described detection network multicast performance of claim 1 to 6, it is characterized in that 7, described step C comprises:

Within the predetermined time, test is initiated point and is received described performance measurement response message, and measures the multicast performance parameter according to the identification information that receives in the message.

8, the implementation method of detection network multicast performance according to claim 7 is characterized in that, also comprises before the described step C:

Before test multicast claim frame, initialization frame is lost value and/or frame delay value.

9, the implementation method of detection network multicast performance according to claim 8 is characterized in that, described LOF value comprises: minimum frame is lost value, largest frames is lost value and/or total LOF value, and the value of multicast group size;

And/or,

Described frame delay value comprises: minimum frame length of delay, largest frames length of delay and/or total frame delay value, and the value of multicast group size.

10, the implementation method of detection network multicast performance according to claim 9 is characterized in that, described step C specifically comprises:

C1, when carrying out LOF and measure, test is initiated point within the predetermined time, calculate the LOF value according to forward direction transmit frame Counter Value in two multicast response frames of the same identification information of continuous reception and forward direction received frame Counter Value, and upgrade minimum frame according to this LOF value and lose value, largest frames and lose value and/or the total LOF value and the value of multicast group size;

And/or,

C2, when carrying out frame delay when measuring, test is initiated point within the predetermined time, according to the time that receives the multicast response frame, and the forward direction transmitting time in the multicast response frame stab information, forward direction time of reception stab information and oppositely transmitting time stab information calculations frame delay value, and upgrade minimum frame length of delay, largest frames length of delay and/or the total frame delay value and the value of multicast group size according to this frame delay value.

11, the implementation method of detection network multicast performance according to claim 10 is characterized in that, described step C1 comprises:

The difference that the LOF value equals the forward direction transmit frame Counter Value in two multicast response frames of the same identification information that receives continuously deducts the difference of two forward direction received frame Counter Values in the multicast response frame, and:

When described LOF value is lost value less than minimum frame, minimum frame is lost value be updated to this LOF value;

And/or,

When described LOF value is lost value greater than largest frames, largest frames is lost value be updated to this LOF value;

And/or,

Total LOF value equal current total LOF value and described LOF value and, and the value of multicast group size need add one.

12, the implementation method of detection network multicast performance according to claim 10 is characterized in that, described step C2 comprises:

The frame delay value equals to receive the time of multicast response frame and the difference of forward direction transmitting time stamp information deducts the difference that the forward direction time of reception stabs information and reverse transmitting time stamp information, and:

When described frame delay value during less than the minimum frame length of delay, then with described frame delay value as the minimum frame length of delay;

And/or,

When described frame delay value during greater than the largest frames length of delay, then with described frame delay value as the largest frames length of delay;

And/or,

Total frame delay value equal current total frame delay value and described frame delay value and, and the value of multicast group size added one.

13, according to the implementation method of each described detection network multicast performance of claim 1 to 6, it is characterized in that, carry out described step C and also comprise before:

C0, test are initiated after point receives described multicast response message, when wherein identification information is correct identification information, and execution in step C then.

14, the implementation method of detection network multicast performance according to claim 13 is characterized in that, described step C0 also comprises:

Whether the identification information in the multicast response message of determining to receive according to the effective identification information of preserving is correct.

Images