WO2017113771A1

WO2017113771A1 - Packet processing method and device

Info

Publication number: WO2017113771A1
Application number: PCT/CN2016/091573
Authority: WO
Inventors: 刘炽彬; 周明; 张成龙
Original assignee: 华为技术有限公司
Priority date: 2015-12-31
Filing date: 2016-07-25
Publication date: 2017-07-06
Also published as: CN105634937B; CN105634937A

Abstract

Embodiments of the present application disclose a packet processing method and device. The method comprises: receiving by a reflector a TWAMP (Two-Way Active Measurement Protocol) test packet transmitted by a sender; modifying a value of a Z bit in the returned TWAMP test packet or modifying a value of a newly added sender/reflector (S/R) bit in the TWAMP test packet to determine whether the returned TWAMP test packet is a reflected packet, thereby reducing the risk of forming a reflection loop of the returned TWAMP test packet between a mistakenly configured reflector and a correctly configured reflector, avoiding network storm.

Description

Message processing method and device

This application claims priority to Chinese Patent Application No. 201511029103.1, entitled "Processing and Apparatus for Processing a Message", filed on December 31, 2015, the entire contents of which is incorporated herein by reference. In the application.

Technical field

The embodiments of the present invention relate to the field of communications technologies, and in particular, to a packet processing method and apparatus.

Background technique

The Two-way Active Measurement Protocol (TWAMP) provides a means of measuring the performance of the Internet Protocol (IP) between any two devices supporting this standard in the network. The User Datagram Protocol (UDP) data packet is used as a measurement probe frame to measure network bidirectional packet loss, delay, and jitter. TWAMP follows the IETF RFC5357 standard. After the user initiates the statistics session, the TWAMP test packet constructed and sent from the session sender passes through the service forwarding channel and arrives at the session reflector. The session reflector is based on the source IP address, destination IP address, and source port. The destination port number matches the TWAMP test packet identified as the specified session, and then exchanges the source IP address, destination IP address, source port number, and destination port number, and adds the corresponding protocol content to reset the packet lifetime TTL to 255. Then, the modified TWAMP test packet is sent back to the session sender. As shown in Figure 1, in order to test the round-trip IP performance between Node A and Node C, Node A acts as the session sender, and Node C is the normally configured session reflector. When working normally, Node A constructs and initiates the TWAMP test report. After the node C matches the identification, the reflection returns the TWAMP test message. In some cases, the source IP address, the destination IP address, the source port number, and the destination port number of the node B may be misconfigured due to the user's misoperation. As a result, the node B is misconfigured as a reflector and the node C reflects the reported packet. The text arrives at the node B, and the node B reflects the message. When the message is sent back, the TTL is reset to 255 according to the IETF RFC5357 standard. The test packet is reflected into a ring between Node B and Node C, causing a network storm.

Summary of the invention

The application provides a TWAMP test message processing method and apparatus. It is used to reduce the problem that business data is reflected in the loop between network devices, causing network storms.

In a first aspect, a method for processing a TWAMP message is provided, the method comprising:

The reflective device receives the TWAMP test message;

And the TWAMP test packet is sent back to the sending device, where the TWAMP test packet includes the TWAMP test packet indicating that the loopback is a reflected packet. Logo.

The method further includes: when the reflector device determines that the TWAMP test packet is a reflection packet, discarding the reflected packet.

The device of the present invention determines that the received TWAMP test packet is not a reflection packet, and adds the TWAMP test packet sent back to the TWAMP packet to be a reflection packet identifier. After the TWAMP test packet is sent back, if a device is misconfigured as a reflective terminal due to human error or the like in the forwarding channel of the loopback packet, the received TWAMP test packet can be distinguished by the above identifier. Whether the text is a reflection packet, so that the TWAMP test packet can be prevented from being formed into a packet loop between the correctly configured reflector device and the misconfigured reflector device in time, thereby preventing the service data from being repeatedly forwarded and replicated in the network. Network storms improve the reliability of the network.

Optionally, the determining that the TWAMP test message is not a reflection message comprises: determining that a Z bit in the TWAMP test message is 0, and determining that the TWAMP is not a reflection message.

Optionally, the identifier is: a Z bit with a value of 1.

The Z bit is a field carried by the TWAMP test message itself and is a reserved bit in the error evaluation. It is defined in the IETF RFC5357 standard. When the transmitting device sends a TWAMP test message, the Z bit must be set to 0, and the reflective device receives the location. When the TWAMP test message is described, the Z bit is not checked, and the value of the Z bit is not changed in the returned TWAM test message. Through the solution of the present application, when the reflective end device receives the TWAMP test packet, the value of the Z bit is verified, when the Z bit is If the message is 0, the TWAMP test message is sent back. If the Z bit is 1, the TWAMP test message is discarded. Therefore, the TWAMP test packet can be prevented from forming a packet loop between the properly configured reflector device and the misconfigured reflector device, preventing service data from being repeatedly forwarded and replicated in the network, causing network storms and improving network reliability. Sex.

Optionally, the Z bit value of 1 may be used to indicate that the TWAMP test packet carrying the Z bit is not reflected, and the Z bit value is 0 to indicate that the TWAMP test packet carrying the Z bit passes through the reflective device. Reflection.

Optionally, the Z bit may also have multiple bits, and other values are used to indicate whether the TWAMP test message carrying the Z bit is reflected.

Optionally, the determining that the TWAMP test packet is not a reflection packet includes: determining, by the reflector device, that the sender/reflection S/R bit in the TWAMP test packet is 0, determining the The TWAMP test message is not a reflection message.

Optionally, the identifier is: S/R bit with a value of 1.

When generating the TWAMP test packet, the sender device adds a sender/reflector S/R bit to the TWAMP test packet. With the solution of the present application, the reflective end device checks the value of the S/R bit when receiving the TWAMP test packet, and determines that the packet is not a reflected packet when the S/R bit is 0, and then sends back The TWAMP test message; when the S/R bit is 1, determining that the TWAMP test message is a reflection message, discarding the TWAMP test message. Therefore, the TWAMP test packet can be prevented from forming a packet loop between the properly configured reflector device and the misconfigured reflector device, preventing service data from being repeatedly forwarded and replicated in the network, causing network storms and improving network reliability. Sex.

Optionally, the S/R bit value of 1 may be used to indicate that the TWAMP test packet carrying the S/R bit is not reflected, and the S/R bit value is 0 to represent the TWAMP carrying the S/R bit. The test packet is reflected by the reflective device.

Optionally, the S/R bit may also have multiple bits, and other values are used to indicate that the S/R bit is carried. Whether the TWAMP test message is reflected.

In a second aspect, the present application provides a TWAMP packet processing method, where the method includes: the sending end device sends a TWAMP test packet to the reflective end device;

The sending end device receives the TWAMP test packet sent back by the reflective end device, and the TWAMP test packet sent back includes the identifier indicating that the returned TWAMP test packet is a reflected packet.

Optionally, the value of the Z bit in the TWAMP test packet sent by the sending end device is 0, indicating that the TWAMP test packet is not a reflection packet.

Optionally, the identifier in the returned TWAMP test packet is: a Z bit with a value of 1.

Optionally, the value of the Z bit in the TWAMP test packet sent by the sending end device is 1, indicating that the TWAMP test packet is not a reflection packet.

Optionally, the identifier in the returned TWAMP test packet is: a Z bit with a value of 0.

Optionally, the value of the S/R bit in the TWAMP test packet sent by the sending end device is 0, indicating that the TWAMP test packet is not a reflection packet.

Optionally, the identifier in the returned TWAMP test packet is: S/R bit with a value of 1.

Optionally, the value of the S/R bit in the TWAMP test packet sent by the sending end device is 1, indicating that the TWAMP test packet is not a reflection packet.

Optionally, the identifier in the returned TWAMP test packet is: S/R bit with a value of 0.

Optionally, the S/R bit may also have multiple bits, and other values are used to indicate whether the TWAMP test packet carrying the S/R bit is reflected.

The technical solution of the second aspect has the same technical effect as the technical solution of the first aspect.

In a third aspect, a message processing apparatus is provided for performing the method of the first aspect. The device is located on the side of the reflective device, and the device includes: a receiving unit, a processing unit, and a sending unit;

The receiving unit is configured to receive a TWAMP test packet;

The processing unit is configured to: determine that the TWAMP test packet is not a reflection packet, and generate The returned TWAMP test message, where the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflected message;

The sending unit is configured to send the returned TWAMP test packet.

The processing unit is further configured to: when the TWAMP test packet is a reflection packet, discard the TWAMP test packet.

Optionally, the processing unit is configured to determine that the Z bit in the TWAMP test packet is 0, and determine that the TWAMP is not a reflection message.

Optionally, the processing unit is configured to determine that the Z bit in the TWAMP test packet is 1, and determine that the TWAMP is not a reflection message.

Optionally, the Z bit may also have multiple bits, and the processing unit is configured to use other values to determine whether the TWAMP test message carrying the Z bit is reflected.

Optionally, the processing unit is configured to determine that the S/R bit in the TWAMP test packet is 0, and determine that the TWAMP is not a reflection message.

Optionally, the processing unit is configured to determine that the S/R bit in the TWAMP test packet is 1, and determine that the TWAMP is not a reflection message.

Optionally, the S/R bit may also have multiple bits, and the processing unit is configured to use other values to determine whether the TWAMP test message carrying the S/R bit is reflected.

The technical solution of the third aspect has the same technical effects as the technical solutions of the first aspect and the second aspect.

In a fourth aspect, a message processing apparatus is provided for performing the method of the second aspect. The device is located at the transmitting device side, and includes: a processing unit, a sending unit, and a receiving unit;

The processing unit is configured to generate a TWAMP test message;

The sending unit is configured to send the TWAMP test packet;

The receiving unit is configured to receive a TWAMP test packet sent back by the reflective device, where the returned TWAMP test packet includes an identifier indicating that the returned TWAMP test packet is a reflected packet.

Optionally, the processing unit is configured to set a Z bit in the sent TWAMP test message to 0, indicating that the TWAMP test message is not a reflection message.

Optionally, the processing unit is configured to: the value of the Z bit in the sent TWAMP test message is 1, indicating that the TWAMP test message is not a reflection message.

Optionally, the processing unit is configured to: set a value of S/R bit in the sent TWAMP test packet to 0, indicating that the TWAMP test packet is not a reflection message.

Optionally, the processing unit is configured to set a value of S/R bit in the sent TWAMP test packet to 1, indicating that the TWAMP test packet is not a reflection packet.

Optionally, the S/R bit may also have multiple bits, and other values are used to indicate whether the TWAMP test message carrying the S/R bit is reflected.

The technical solutions of the fourth aspect have the same technical effects as the technical solutions of the first to third aspects.

In a fifth aspect, a communication system is provided, including a transmitting end device and a reflective end device, wherein the reflective end device includes the apparatus according to the third aspect, and the transmitting end device includes the fourth aspect s installation. The system is for performing the method of the first aspect and the method of the second aspect.

In a sixth aspect, the application provides a sender device, including a memory and a processor, where The memory is for storing program instruction code, and the processor is configured to execute the instruction code in the memory to complete the method of the first aspect. The transmitting device includes the device described in the third aspect.

In a seventh aspect, the present application provides a reflective device, including a memory and a processor, wherein the memory is configured to store program instruction code, and the processor is configured to execute an instruction code in the memory, completing the second aspect. Methods. The reflective end device includes the device of the fourth aspect.

In an eighth aspect, the present application provides a computer readable storage medium for storing computer software instructions for performing the functions of the first aspect and the second aspect, comprising the method for performing the first aspect and the second aspect Designed program.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

FIG. 1 is a schematic diagram of reflection of a TWAMP message into a ring in the prior art.

2 is a schematic diagram of an application scenario involved in a packet processing method provided by the present application;

FIG. 3 is a schematic flowchart of a packet processing method according to an embodiment of the present disclosure;

4 is a schematic diagram of a format of a possible TWAMP test packet sent by a sender device according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of a packet processing method according to another embodiment of the present disclosure;

6 is a schematic diagram of a format of a possible TWAMP test packet sent by a sender device according to another embodiment of the present application;

FIG. 7A is a schematic diagram of an execution body of a packet processing method according to an embodiment of the present disclosure;

FIG. 7B is a schematic diagram of another execution body of a packet processing method according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a message processing apparatus according to an embodiment of the present disclosure;

FIG. 8B is a schematic diagram of another packet processing apparatus according to an embodiment of the present application.

detailed description

The application scenarios described in the embodiments of the present application are for the purpose of more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application. Those skilled in the art may understand that with the evolution of the network architecture and The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

The sender device involved in the present application may be a router or a packet transport network device or a switch. The reflector device involved in the present application may be a router or a packet transport network device or a switch.

Example 1

FIG. 2 is a schematic diagram of an application scenario involved in a packet processing method according to an embodiment of the present disclosure. As shown in FIG. 2, device A is a TWAMP test packet sending device, and device C is a TWAMP test packet reflection. End device, device A and device C have one or more intermediate devices, such as an intermediate device B. The destination IP address configured in device A is 1.1.1.1, the source IP address is 2.2.2.2, the destination port number is 1111, and the source port number is 2222. The destination IP address configured in device C is 2.2.2.2, the source IP address is 1.1.1.1, the destination port number is 2222, and the source port number is 1111. Therefore, the destination IP address carried by the TWAMP test packet sent from device A to device C is 1.1.1.1, the source IP address is 2.2.2.2, the destination port number is 1111, and the source port number is 2222. The destination IP address carried by the TWAMP test packet of device A is 2.2.2.2, the source IP address is 1.1.1.1, the destination port number is 2222, and the source port number is 1111. Device A sends a TWAMP test packet to device C. By testing the round-trip IP performance between device A and device C, parameters such as network bidirectional packet loss, delay, and jitter are counted. Device B is the intermediate device in the TWAMP test packet transmission path. Device B is configured as a reflector device because of human error. That is, the destination IP address configured in device B is 1.1.1.1, and the source IP address is 2.2.2.2. The destination port number is 1111 and the source port number is 2222.

FIG. 3 is a schematic diagram of a format of a possible TWAMP test packet sent by a sender device. As shown in Figure 3, in the TWAMP test packet sent by the sender device, the 13th to 16th bytes are the source. IP address (SIP), a total of 32 bits; the 17th-20th byte is the destination IP address (DIP), a total of 32 bits; the 21st-22th byte is the source port number (Source Port), a total of 16 bits; The 23-24 bytes are the destination port numbers, which occupy a total of 16 bits. The 41st-42th byte is an Error Estimate byte, which is 16 bits in total, and the error evaluation byte includes: S bit (1 bit), Z bit (1 bit), Scale (6 bit), multiplier (8bit). The S bit indicates whether the clock generating the time stamp is synchronized to the Universal Time Coordinated (UTC) flag. The S bit is 1 to indicate that the clock is synchronized with the external UTC, and S is 0 to indicate that the clock is not synchronized with the external UTC. The Z bit is a reserved bit in the error evaluation. It is defined in the IETF RFC5357 standard. When the transmitting device sends a TWAMP test message, the Z bit must be set to 0. When the reflective device receives the TWAMP test message, it does not for the Z bit. When the check is performed, the transmitting device does not check the Z bit when receiving the TWAMP test packet sent back by the reflective device. Scale is the power (scale) in the error evaluation, 2^scale, used to evaluate the error use; Multiplier is the multiplier factor in the error evaluation, also used to evaluate the error use. Starting from the 43rd byte, it is a padding (Padding), using a pseudo-random code or an all-zero code.

In the embodiment of the present application, when it is required to detect the round-trip IP performance between the transmitting device (such as device A in FIG. 1) and the reflective device (such as device C in FIG. 1) in the network, device A is used as the transmitting end. The device constructs and sends a TWAMP test message, which is forwarded to the reflective device C via the intermediate device B. In the TWAMP test packet sent by the sender device, the Z bit value is 0. The packet processing method provided by the embodiment of the present application is described in detail below with reference to FIG. This application is exemplified by applying the method to the scenario shown in FIG. 2. The method includes:

401: The sender device generates and sends a TWAMP test packet.

Device A acts as the sender device, generates and sends a TWAMP test message, and the TWAMP test message is forwarded to the reflective device C via the intermediate device B. When the device A sends the TWAMP test packet as the sender device, the Z bit in the TWAMP test packet is set to 0, indicating that the TWAMP test packet is not a reflection packet. When the transmitting device C receives the TWAMP test packet, it sends back the TWAMP test packet to the sending device A, and the returned device The TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflected message. Specifically, the identifier may be a Z bit having a value of one. The TWAMP test packet is a User Datagram Protocol UDP packet.

402: The next hop device receives the TWAMP test packet.

When the device A sends the TWAMP test packet to the device C, the device A forwards the TWAMP test packet to the next hop device, that is, the device B, and the device B receives the TWAMP test packet.

403: The next hop device sets the destination IP address, the source IP address, the destination port number, and the source port number of the TWAMP test packet with the source IP address, the destination IP address, and the source port number of the next hop device. The destination port number is matched. If the match is successful, 404 is performed. If the match fails, the destination IP address is forwarded to the next hop device, and 402-403 is repeatedly executed.

When the TWAMP test packet sent by the device A arrives at the device B, the device B receives the TWAMP test packet, and the device B firstly uses the destination IP address, the source IP address, and the destination port number carried in the TWAMP test packet. The source port number is matched with the source IP address, destination IP address, source port number, and destination port number configured by device B. If the destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet are the same as the source IP address, destination IP address, source port number, and destination port number configured on device B, the match is determined. If the device B determines that the received message is a TWAMP test message, the process continues to 404. If the destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet are inconsistent with the source IP address, destination IP address, source port number, and destination port number configured on device B, the match is considered to be unsuccessful. , continue to execute 402-403. Therefore, if the match is successful, device B returns the TWAMP test message to the sender device A of the test message. If the match fails, the forwarding to the destination IP address continues to the next hop device.

In the embodiment of the present application, the destination IP address, the source IP address, the destination port number, and the source port number carried in the TWAMP test packet, and the source IP address, the destination IP address, the source port number, and the destination port number configured by the device B. Inconsistent, matching failed, device B continues to test the TWAMP The destination IP address of the packet forwards the TWAMP test packet. When the TWAMP test packet arrives at device C, device C sets the destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet with the source IP address and destination IP address configured on device C. The source port number and the destination port number are matched to determine the destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet, and the source IP address, destination IP address, and source configured on device C. If the port number and the destination port number are the same, the connection is determined to be successful. The device C determines that the received message is a TWAMP test message, and determines that the device C is a reflective end device corresponding to the transmitting device A.

404: The reflector device determines whether the Z bit in the received TWAMP test packet is 0. If it is 0, it executes 405. If it is not 0, discards the TWAMP test packet.

In the TWAMP test packet sent by the sender device A, the Z bit is 0, and is forwarded to the reflective device C through the intermediate device B. After receiving the TWAMP test packet, the device C determines that the Z bit in the TWAMP test packet is 0, and determines that the TWAMP is not a reflection message, and includes a TWAMP test indicating the loopback in the TWAMP test message. The message is the identifier of the reflected message. For example, the value of the Z bit in the TWAMP test message is set to 1, and the device C sends back the TWAMP test message including the identifier to the sending device A.

The TWAMP test packet sent back by the device C passes through the device B again when it is sent back to the sender device A. The destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet sent by device C, and the source IP address, destination IP address, source port number, and destination configured on device B. The port number is the same. Therefore, the destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet sent by device C are the source IP address, destination IP address, and source port number configured on device B. The destination port number is successfully matched. Device B determines that a TWAMP test message is received, and device B determines whether the Z bit of the received TWAMP message is zero. Since the reflection end device C has set the value of the Z bit of the returned TWAMP test message to 1, therefore, the device B determines that the value of the Z bit of the received TWAMP message is not 0, and determines the received TWAMP test report. The text is a reflection message. At this time, device B The TWAMP test packet is discarded without reflection, thereby effectively avoiding the formation of a packet loop and reducing the risk of network storms.

405: The reflective end device sends back the TWAMP test packet to the sending end device, where the returned TWAMP test packet includes an identifier indicating that the returned TWAMP test packet is a reflected packet.

If the value of the Z bit of the TWAMP test message received by the device C is 0, it indicates that the TWAMP test message is not a reflection message. The device C sets the value of the Z bit in the received TWAMP test message to 1, and sends the TWAMP test message back to the sending device A. The returned TWAMP test message may further include a corresponding TWAMP protocol. Other fields, such as the number of packet sequences, timestamp, lifetime TTL, source IP address, destination IP address, source port number, destination port number, and so on.

In Embodiment 1, the Z bit value of 1 can also be used to indicate that the TWAMP test message carrying the Z bit is not reflected, and the Z bit value is 0 to indicate that the TWAMP test message carrying the Z bit is reflected. The reflection of the end device.

Example 2

FIG. 5 is a schematic flowchart of a packet processing method according to another embodiment of the present application. The application is applied to the scenario shown in FIG. 2 for example. The method includes:

501: The sender device generates and sends a TWAMP test packet.

Device A acts as the sender device, generates and sends a TWAMP test message, and the TWAMP test message is forwarded to the reflective device C via the intermediate device B. The format of the TWAMP test message is as shown in FIG. 6. The format of the message shown in Figure 3 is basically the same. The only difference is that in the 43th byte belonging to the padding byte in the TWAMP test message, a sender/reflector device S/R bit is set. The S/R bit is set to 1 bit, and the other 7 bits are set to the reserved field Resv. The Resv field can be set to all 0s, or can be set to other values for identifying the TWAMP test report. The specific message type of the text.

Optionally, the S/R bit may also have multiple bits, and other values are used to indicate whether the TWAMP test message carrying the S/R bit is reflected. Further optionally, the S/R bit may also be set at other locations of the padding byte.

In the embodiment of the present application, the S/R bit is 0 to indicate that the TWAMP test message is not a reflection message, and the S/R bit is 1 to indicate that the TWAMP test message is a reflection message. When the device A sends the TWAMP test packet as the sender device, the S/R bit in the TWAMP test packet is set to 0, indicating that the TWAMP test packet is not a reflection packet. When the TWAMP test packet is received, the TWAMP test packet is sent back to the sender device A, and the TWAMP test packet sent back includes the TWAMP test packet indicating that the loopback is a reflection report. The logo of the text. Specifically, the identifier may be an S/R bit having a value of one. The TWAMP test packet is a User Datagram Protocol UDP packet.

502: The next hop device receives the TWAMP test packet.

503: The next hop device sets the destination IP address, the source IP address, the destination port number, and the source port number of the TWAMP test packet with the source IP address, the destination IP address, and the source port number of the next hop device. The destination port number is matched. If the match is successful, perform 504. If the match fails, continue forwarding to the destination IP address to the next hop device and repeat 502-503.

The specific process of the steps 502-503 is the same as the steps 402-403 of the embodiment 1, and the description of the embodiment 1 is omitted, and details are not described herein again.

504: The reflector device determines whether the S/R bit in the received TWAMP test packet is 0. If it is 0, it executes 505. If it is not 0, the TWAMP test packet is discarded.

In the TWAMP test packet sent by the sending device A, the S/R bit is 0, and is forwarded to the reflective device C through the intermediate device B. After receiving the TWAMP test packet, the device C determines that the S/R bit in the TWAMP test packet is 0, and determines that the TWAMP is not a reflection packet, and includes, in the TWAMP test packet, the indication that the loopback is sent. The TWAMP test packet is an identifier of the reflected message, for example, the value of the S/R bit in the TWAMP test packet is set to 1, The device C sends back a TWAMP test message including the identifier to the sender device A. The TWAMP test packet sent back by the device C passes through the device B again when it is sent back to the sender device A. The destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet sent by device C, and the source IP address, destination IP address, source port number, and destination configured on device B. The port number is the same. Therefore, the destination IP address, source IP address, destination port number, and source port number carried in the TWAMP test packet sent by device C are the source IP address, destination IP address, and source port number configured on device B. The destination port number is successfully matched. Device B determines that it is receiving a TWAMP test message. Device B determines whether the S/R bit of the received TWAMP test message is zero. Since the reflection end device C has set the value of the S/R bit of the returned TWAMP test message to 1, the device B determines that the value of the Z bit of the received TWAMP message is not 0, and determines the received report. The packet is a reflection packet. At this time, the device B discards the TWAMP test packet without performing reflection, thereby effectively avoiding the formation of a packet loop and reducing the risk of network storms.

505. The reflective end device sends back the TWAMP test packet to the sending end device, where the returned TWAMP test packet includes an identifier indicating that the returned TWAMP test packet is a reflected packet.

If the value of the S/R bit of the test packet received by the device C is 0, the test packet is not a reflection packet. The device C sets the value of the S/R bit in the received TWAMP test packet to 1, and sends the TWAMP test packet to the sending device A. The returned TWAMP test packet may also include a corresponding Other fields of the TWAMP protocol, such as the number of packet sequences, timestamps, time-to-live TTL, source IP address, destination IP address, source port number, destination port number, and so on.

Example 3

7A and 7B show a transmitting end for performing the methods provided in Embodiment 1 and Embodiment 2 A schematic diagram of possible hardware structures of devices and reflector devices. The transmitting end device may be the transmitting end device 600 as shown in FIG. 7A, and the reflective end device may be the reflective end device 700 as shown in FIG. 7B.

The transmitting device 600 includes a processor 601 and a network interface 602 that communicates with the reflective device 700 via the network interface 602.

The processor 601 is configured to generate a TWAMP test packet.

The network interface 602 is configured to send a TWAMP test packet, and is further configured to receive a TWAMP test packet sent by the reflective device, where the returned TWAMP test packet includes an identifier indicating that the returned TWAMP packet is a reflected packet.

The processor 601 is further configured to set the Z bit in the TWAMP test message to 0, to indicate that the TWAMP test message is not a reflection message, and the returned TWAMP test message includes the indication of the loopback. The TWAMP test packet is the identifier of the reflected message. The identifier may be a Z bit having a value of one.

Optionally, the processor 601 is further configured to set a Z bit in the TWAMP test packet to 1 to indicate that the TWAMP test packet is not a reflection packet; and the returned TWAMP test packet includes an indication. The loopback TWAMP test packet is an identifier of the reflected packet. The identifier may be a Z bit having a value of zero.

Optionally, the processor 601 is further configured to set a sender/reflector S/R bit in the TWAMP test packet to 0, to indicate that the TWAMP test packet is not a reflection packet; The TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflected message. The identifier may be an S/R bit having a value of one.

Optionally, the processor 601 is further configured to set a sender/reflection S/R bit in the TWAMP test packet to 1 to indicate that the TWAMP test packet is not a reflection packet; The TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflected message. The identifier may be an S/R bit having a value of zero.

The reflective end device 700 includes a processor 701 and a network interface 702 that communicates with the transmitting device 600 via a network interface 702.

The network interface 702 is configured to receive the TWAMP test packet sent by the sender device.

The processor 701 is configured to determine that the TWAMP test packet is not a reflection packet, and generate a loopback TWAMP test packet, where the returned TWAMP test packet includes the TWAMP test packet indicating that the loopback is a reflection packet. Logo.

The network interface 702 is further configured to send the returned TWAMP test packet.

The processor 701 is further configured to determine that the Z bit in the TWAMP test packet sent by the sending end device is 0, and determine that the TWAMP is not a reflected message. The processor 701 is further configured to set a value of the reserved Z bit in the returned TWAMP test message to 1 to indicate that the returned TWAMP test message is a reflected message.

Optionally, the processor 701 is further configured to determine that a Z bit in the TWAMP test packet sent by the sending end device is 1, and determine that the TWAMP is not a reflection message. The processor 701 is further configured to set a value of the reserved Z bit in the returned TWAMP test message to 0, to indicate that the returned TWAMP test message is a reflected message.

Optionally, the processor 701 is further configured to determine that the sender/reflector S/R bit is 0, and then determine that the TWAMP test packet is not a reflection message, and the processor 701 is further configured to: The S/R bit in the TWAMP test packet sent back is set to 1, indicating that the TWAMP test packet sent back is a reflected message.

Optionally, the processor 701 is further configured to determine that the sender/reflector S/R bit is 1, and determine that the TWAMP test packet is not a reflection message; and the processor 701 is further configured to: The S/R bit in the loopback TWAMP test message is set to 0, and is used to indicate the loopback. The TWAMP test message is a reflection message.

In another embodiment, as shown in FIG. 7A, the transmitting device 600 can include a processor 601, a network interface 602, a memory 603, and a bus 604. Processor 601, network interface 602, and memory 603 communicate over bus 604. The processor 601 communicates with the reflective end device 700 via the network interface 602.

In another embodiment, as shown in FIG. 7B, the reflective end device may include a processor 701, a network interface 702, a memory 703, and a bus 704. Processor 701, network interface 702, and memory 703 communicate over bus 704. The processor 701 communicates with the source device 600 via the network interface 702.

The processor 601 and the processor 701 may be one or more central processing units (CPUs). In the case where the processor 601 or the processor 701 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

The network interface 602 and the network interface 702 may be wired interfaces, such as a Fiber Distributed Data Interface (FDDI), and a Gigabit Ethernet (GE) interface.

The memory 603 and the memory 703 may be, but not limited to, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM), a compact disk read only memory (CD-ROM), a hard disk, or the like. One or more. The memory 603 and the memory 703 are used to store program codes.

The memory 603 stores the program instruction code, and the processor 601 is configured to execute the instruction code in the memory 603 to complete the method in Embodiment 1 or Embodiment 2.

The memory 703 stores program instruction codes, and the processor 701 is configured to execute the instruction codes in the memory 703 to complete the methods in Embodiment 1 and Embodiment 2. Example 4:

FIG. 8A shows a schematic diagram of a message processing apparatus 800. Used to perform embodiment 1 and The packet processing method provided in the second embodiment. The message processing device 800 is located on the side of the transmitting device 600. The message processing apparatus 800 includes: a processing unit 801, a transmitting unit 802, and a receiving unit 803;

The processing unit 801 is configured to generate a TWAMP test message.

The sending unit 802 is configured to send the TWAMP message.

The receiving unit 803 is configured to receive a TWAMP test packet sent back by the reflective device, where the returned TWAMP test packet includes an identifier indicating that the TWAMP packet is a reflected packet.

Each of the above units may be a logical unit. In a specific implementation process, the CPU may read a functional component generated after the software code stored in the memory is run, or may be implemented by a hardware unit.

The processing unit 801 is further configured to set the Z bit in the TWAMP test message to 0, to indicate that the TWAMP test message is not a reflection message, and the returned TWAMP test message includes the indication of the loopback The TWAMP test message is the identifier of the reflected message. The identifier may be a Z bit having a value of one.

Optionally, the processing unit 801 is further configured to set a Z bit in the TWAMP test packet to 1 to indicate that the TWAMP test packet is not a reflection packet; and the loopback TWAMP test packet includes The TWAMP test message indicating the loopback is an identifier of the reflected message. The identifier may be a Z bit having a value of zero.

Optionally, the processing unit 801 is further configured to set a sender/reflection S/R bit in the TWAMP test packet to 0, to indicate that the TWAMP test packet is not a reflection packet; The reflector device is configured to set the S/R bit in the loopback TWAMP test packet to 1 to indicate that the loopback TWAMP test packet is a reflection packet.

Optionally, the processing unit 801 is further configured to set a sender/reflection S/R bit in the TWAMP test packet to 1 to indicate that the TWAMP test packet is not a reflection packet; The reflective end device is configured to set the S/R bit in the loopback TWAMP test message A value of 0 indicates that the TWAMP test message sent back is a reflection message.

The packet processing apparatus 800 provided in FIG. 8A can be integrated into the transmitting device 600 described in FIG. 7A and applied to the scenario shown in FIG. 2 to implement the function of the transmitting device. For example, processing unit 801 can be implemented with processor 601 of FIG. 7A, and one or more of transmitting unit 802 and receiving unit 803 can be implemented by the network interface of FIG. 7A. For other additional functions that can be implemented by the packet processing device 800 and the interaction process with the reflective device, refer to the description of the methods in Embodiment 1 and Embodiment 2, and details are not described herein again.

FIG. 8B shows a schematic diagram of another message processing apparatus 900. The message processing device 900 is located on the side of the transmitting device 700. The message processing apparatus 900 includes: a receiving unit 901, a processing unit 902, and a transmitting unit 903.

The receiving unit 901 is configured to receive a TWAMP test message.

The processing unit 902 is configured to: determine that the TWAMP test packet is not a reflection packet, and generate a TWAMP test packet that is sent back, where the returned TWAMP test packet includes a TWAMP test packet indicating that the loopback is a reflection packet. Logo.

The sending unit 903 is configured to send the returned TWAMP test packet.

Optionally, the processing unit 902 is further configured to determine that the Z bit in the TWAMP test packet is 0, and determine that the TWAMP is not a reflection message. The processing unit 902 is further configured to set a value of the reserved Z bit in the returned TWAMP test message to 1 to indicate that the returned TWAMP test message is a reflected message.

Optionally, the processing unit 902 is further configured to determine that the Z bit in the TWAMP test packet is 1, and determine that the TWAMP is not a reflection message. The processing unit 902 is further configured to The value of the reserved Z bit in the returned TWAMP test message is set to 0, and is used to indicate that the returned TWAMP test message is a reflected message.

Optionally, the processing unit 902 is further configured to determine that the sender/reflection S/R bit is 0, and then determine that the TWAMP test packet is not a reflection message, and the processing unit 902 is further configured to: The S/R bit in the TWAMP test packet sent back is set to 1, indicating that the TWAMP test packet sent back is a reflected message.

Optionally, the processing unit 902 is further configured to determine that the sender/reflector S/R bit is 1, and then determine that the TWAMP test packet is not a reflection message; and the processing unit 902 is further configured to: The S/R bit in the TWAMP test packet sent back is set to 0, and is used to indicate that the TWAMP test packet sent back is a reflected message.

The packet processing apparatus 900 provided in FIG. 8B can be integrated into the reflective end device 700 described in FIG. 6B and applied to the scenario shown in FIG. 2 to implement the function of the reflected device. For example, processing unit 902 can be implemented with processor 701 of FIG. 7B, and one or more of receiving unit 901 and transmitting unit 903 can be implemented by network interface 702 of FIG. 7B. Other additional functions that can be implemented by the message processing apparatus 900 and the interaction process with the source device are described in the descriptions of Embodiment 1 and Embodiment 2, and details are not described herein again.

The packet processing apparatus provided in the present application is exemplified by the division of the above functional modules. In actual applications, the functions may be assigned with different functional modules as needed, that is, the internal structure of the device is divided into different Functional modules to perform all or part of the functions described above.

Example 5

The application provides a communication system, including a sender device and a reflector device. The sending The end device and the reflective end device may be the transmitting end device and the reflective end device provided in Embodiment 3. The transmitting end device may include the packet processing device on the transmitting end device side provided in Embodiment 4, and the reflective end device may include the packet processing device on the reflective end device side provided in Embodiment 4. The transmitting device and the reflective device are configured to perform the methods described in Embodiment 1 and Embodiment 2.

The communication system may further include controlling the client device and the server, and after controlling the interaction control signaling message between the client device and the server to establish a control session, the control client device notifies the server to establish a statistical session by using a signaling message. The signaling is mainly to negotiate the IP address and UDP port number of both ends of the statistics session. After the two sides negotiate successfully, the statistical session is established successfully. After the statistics session is started, the sending device sends a test packet, and the test packet carries the information such as the timestamp and the sequence number. After receiving the test packet, the device responds, sends a response test packet, and responds to the test packet. Carry information such as time stamp, response serial number, and so on. After receiving the response test packet, the sending device calculates the IP performance statistics result and sends it to the controlling client device. The statistics are uniformly maintained by the controlling client device and presented to the user. The establishment of the control session between the control client and the server in the present embodiment, and the establishment of the statistical session between the sender device and the sender device are performed according to the prior art, and are not described herein again.

Those skilled in the art will appreciate that in one or more examples described above, the functions described herein can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in or transmitted as one or more instructions or code in a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

The various parts of the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, for apparatus and system embodiments, since it is substantially similar to the method embodiment, The description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

Finally, it should be noted that the above description is only a preferred embodiment of the technical solution of the present application, and is not intended to limit the scope of protection of the present application. It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the scope of the application. All such modifications, equivalents, improvements, etc., are intended to be included within the scope of the present application.

Claims

A method for processing a bidirectional active measurement protocol TWAMP message, characterized in that the method comprises:

The reflective device receives the TWAMP test message;

And the TWAMP test packet is sent back to the sending device, where the TWAMP test packet includes the TWAMP test packet indicating that the loopback is a reflected packet. Logo.
The method according to claim 1, wherein the determining that the TWAMP test message is not a reflection message comprises: determining that a Z bit in the TWAMP test message is 0, determining the TWAMP test report. The text is not a reflection message.
The method of claim 2 wherein said identification is a Z bit having a value of one.
The method according to claim 1, wherein the determining that the TWAMP test message is not a reflection message comprises: the reflector device determining a sender/reflection end S/ in the TWAMP test message. If the R bit is 0, it is determined that the TWAMP test message is not a reflection message.
The method according to claim 4, further comprising: said identifier being: an S/R bit having a value of one.
The method according to any one of claims 1 to 5, further comprising: when the reflection end device determines that the TWAMP test message is a reflection message, discarding the reflection message.
A TWAMP packet processing method for a bidirectional active measurement protocol, comprising:

The sending end device sends a TWAMP test packet to the reflective end device;

The sending end device receives the TWAMP test packet sent back by the reflective end device, and the TWAMP test packet sent back includes the identifier indicating that the returned TWAMP test packet is a reflected packet.
The method according to claim 7, wherein the value of the Z bit in the TWAMP test message sent by the sender device is 0, indicating that the TWAMP test message is not a reflection message.
The method of claim 8 wherein said identification is a Z bit having a value of one.
The method according to claim 7, wherein the S/R bit of the transmitting end/reflecting end in the TWAMP test message is set to 0, indicating that the TWAMP test message sent by the sending end device is not a reflection. Message.
The method of claim 10 wherein said identifier is an S/R bit having a value of one.
A two-way active measurement protocol TWAMP message processing device, wherein the device is located on a side of a reflective device, the device includes: a receiving unit, a processing unit, and a sending unit;

The receiving unit is configured to receive a TWAMP test packet;

The processing unit is configured to: determine that the TWAMP test packet is not a reflection packet, and generate a TWAMP test packet that is sent back, where the returned TWAMP test packet includes a TWAMP test packet indicating that the loopback is a reflection The identifier of the message;

The sending unit is configured to send the returned TWAMP test packet.
The apparatus according to claim 12, wherein the processing unit is configured to determine that the Z bit in the TWAMP test message is 0, and determine that the TWAMP is not a reflection message.
The apparatus of claim 13 wherein said identifier is a Z bit having a value of one.
The apparatus according to claim 12, wherein the processing unit is configured to determine that the sender/reflection S/R bit in the TWAMP test message is 0, and determine that the TWAMP test packet is not Reflected message.
The apparatus of claim 15 wherein said identifier is an S/R bit having a value of one.
The device according to any one of claims 12-16, wherein the processing unit is further configured to: when the TWAMP test message is a reflection message, discard the reflected message.
A two-way active measurement protocol TWAMP message processing device, wherein the device is located at a transmitting device side, and the device includes a processing unit, a transmitting unit, and a receiving unit;

The processing unit is configured to generate a TWAMP test message;

The sending unit is configured to send the TWAMP test packet;

The receiving unit is configured to receive a TWAMP test packet sent back by the reflective device, where the returned TWAMP test packet includes an identifier indicating that the returned TWAMP test packet is a reflected packet.
The apparatus according to claim 18, wherein said processing unit is further configured to set a Z bit in said TWAMP test message sent by said transmitting unit to zero.
The apparatus according to claim 19, wherein said identifier is: Z bits having a value of one.
The apparatus according to claim 18, wherein said processing unit is further configured to set a sender/reflector S/R bit in said TWAMP test message sent by said transmitting unit to zero.
The apparatus according to claim 21, wherein said identifier is an S/R bit having a value of one.
A communication system comprising a transmitting end device and a reflecting end device, characterized in that the reflecting end device comprises the device according to any one of claims 13-17, the transmitting end device comprising the claims 18-22 The device of any of the preceding claims.