CN105634937B

CN105634937B - A message processing method and device

Info

Publication number: CN105634937B
Application number: CN201511029103.1A
Authority: CN
Inventors: 刘炽彬; 周明; 张成龙
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2015-12-31
Filing date: 2015-12-31
Publication date: 2019-03-26
Anticipated expiration: 2035-12-31
Also published as: WO2017113771A1; CN105634937A

Abstract

The embodiments of the present application disclose a packet processing method and device. The method includes: the reflecting end device receives the bidirectional active measurement protocol TWAMP test message sent from the sending end device, and in the returned TWAMP test message, modifying the value of the Z bit in the TWAMP test message or modifying the new TWAMP test message The value of the S/R bit of the sender/reflector is used to distinguish whether the returned TWAMP test packet is a reflection packet. Thus, the loopback risk of the returned TWAMP test message between the misconfigured reflector device and the normally configured reflector device is effectively reduced, and network storms are avoided.

Description

Message processing method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a message processing method and device.

Background

Two-way Active Measurement Protocol (TWAMP) provides a method for measuring the performance of a round-trip Internet Protocol (IP) between any Two devices supporting the standard in a network, and a User Datagram Protocol (UDP) data packet is used as a Measurement probe frame to count the network bidirectional packet loss, time delay and jitter. The TWAMP follows IETF RFC5357 standard, when a user starts a statistical session, a TWAMP test message constructed and sent from a session sending end reaches a session reflection end through a service forwarding channel, the session reflection end is identified as a TWAMP test message of a specified session based on source IP address, destination IP address, source port number and destination port number matching, then the source IP address, the destination IP address, the source port number and the destination port number are exchanged, corresponding protocol content is added, the message time-to-live TTL is reset to 255, and the modified TWAMP test message is returned to the session sending end. As shown in fig. 1, in order to test the round-trip IP performance between the node a and the node C, the node a is used as a session sending end, the node C is a session reflection end configured normally, and during normal operation, the node a constructs and initiates a TWAMP test packet, and the TWAMP test packet is reflected and returned after matching identification of the node C. In some cases, due to a user's misoperation, the source IP address, the destination IP address, the source port number, and the destination port number of the node B may be configured incorrectly, which causes the node B to be configured as a reflection end incorrectly, the node C reflects the returned packet to the node B, and the node B reflects the packet, and resets the TTL to 255 according to the requirements of IETF RFC5357 standard when the packet is returned. The test message is reflected between the node B and the node C to form a ring, and a network storm is caused.

Disclosure of Invention

The application provides a TWAMP test message processing method and device. The method is used for reducing the problem that the service data is reflected into rings between network devices to cause network storms.

In a first aspect, a method for processing a TWAMP packet is provided, where the method includes:

the method comprises the steps that a TWAMP test message is received by a reflection end device;

and the reflecting end device returns the TWAMP test message to the sending end device if determining that the TWAMP test message is not the reflection message, wherein the returned TWAMP test message comprises an identifier indicating that the returned TWAMP test message is the reflection message.

The method further comprises the following steps: and when the TWAMP test message is determined to be a reflection message by the reflection end equipment, discarding the reflection message.

By the scheme, the reflection end equipment determines that the received TWAMP test message is not a reflection message, and adds the identifier that the returned TWAMP test message is the reflection message in the returned TWAMP message, so that when the reflection end equipment returns the TWAMP test message, if a certain equipment in a forwarding channel of the return message is wrongly configured as a reflection end due to artificial misoperation and the like, whether the received TWAMP test message is the reflection message can be distinguished through the identifier, and thus, a message loop formed by the TWAMP test message between the correctly configured reflection end equipment and the wrongly configured reflection end equipment can be timely and effectively avoided, repeated forwarding and copying of service data in a network are prevented, a network storm is prevented, and the reliability of the network is improved.

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

Optionally, the identifier is: z bit of value 1.

The Z bit is a field carried by the TWAMP test packet itself, and is a reserved bit in error evaluation, which is defined in ietf rfc5357 standard, when the sending end device sends the TWAMP test packet, the Z bit must be set to 0, and when the reflection end device receives the TWAMP test packet, the Z bit is not checked, and the value of the Z bit is not changed in the returned TWAM test packet. According to the technical scheme, when the TWAMP test message is received by the reflection end equipment, the value of a Z bit is checked, and when the Z bit is 0, the TWAMP test message is returned if the message is determined not to be the reflection message; and when the Z bit is 1, determining that the TWAMP test message is a reflection message, and discarding the TWAMP test message. Therefore, a message loop formed by the TWAMP test message between the correctly configured reflection end equipment and the incorrectly configured reflection end equipment can be effectively avoided in time, the repeated forwarding and copying of the service data in the network are prevented, the network storm is prevented, and the reliability of the network is improved.

Optionally, the value of the Z bit may be 1 to indicate that the TWAMP test packet carrying the Z bit is not reflected, and the value of the Z bit is 0 to indicate that the TWAMP test packet carrying the Z bit is reflected by the reflection end device.

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

Optionally, the determining that the TWAMP test packet is not a reflection packet includes: and the reflection end equipment determines that the S/R bit of the sending end/the reflection end in the TWAMP test message is 0, and determines that the TWAMP test message is not a reflection message.

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

When the sending terminal equipment generates the TWAMP test message, a sending terminal/reflection terminal S/R bit is added in the TWAMP test message. According to the technical scheme, when the TWAMP test message is received by the reflection end equipment, the value of the S/R bit is checked, when the S/R bit is 0, the message is determined not to be the reflection message, and the TWAMP test message is sent back; and when the S/R bit is 1, determining that the TWAMP test message is a reflection message, and discarding the TWAMP test message. Therefore, a message loop formed by the TWAMP test message between the correctly configured reflection end equipment and the incorrectly configured reflection end equipment can be effectively avoided in time, the repeated forwarding and copying of the service data in the network are prevented, the network storm is prevented, and the reliability of the network is improved.

Optionally, the value of the S/R bit may be set to be 1 to indicate that the TWAMP test packet carrying the S/R bit is not reflected, and the value of the S/R bit may be set to be 0 to indicate that the TWAMP test packet carrying the S/R bit is reflected by the reflection end device.

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

In a second aspect, the present application provides a TWAMP packet processing method, including: sending a TWAMP test message to a reflection end device by a sending end device;

and the sending end equipment receives the TWAMP test message returned by the reflecting end equipment, wherein the returned TWAMP test message comprises an identifier indicating that the returned TWAMP test message is a reflecting message.

Optionally, a value of a Z bit in the TWAMP test message sent by the sending-end device is 0, which indicates that the TWAMP test message is not a reflection message.

Optionally, the identifier in the returned TWAMP test message is: z bit of value 1.

Optionally, a value of a Z bit in the TWAMP test message sent by the sending-end device is 1, which indicates that the TWAMP test message is not a reflection message.

Optionally, the identifier in the returned TWAMP test message is: z bit of value 0.

Optionally, a value of an S/R bit in the TWAMP test message sent by the sending-end device is 0, which indicates that the TWAMP test message is not a reflection message.

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

Optionally, a value of an S/R bit in the TWAMP test message sent by the sending-end device is 1, which indicates that the TWAMP test message is not a reflection message.

Optionally, the identifier in the returned TWAMP test message is: S/R bits 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 effects as the technical solution of the first aspect.

In a third aspect, a message processing apparatus is provided for implementing the method of the first aspect. The device is located reflection end equipment side, the device includes: a receiving unit, a processing unit and a transmitting unit; wherein,

the receiving unit is used for receiving a TWAMP test message;

the processing unit is configured to: if the TWAMP test message is determined not to be a reflection message, generating a returned TWAMP test message, wherein the returned TWAMP test message comprises an identifier indicating that the returned TWAMP test message is the reflection message;

and the sending unit is used for sending the returned TWAMP test message.

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

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

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

Optionally, the identifier in the returned TWAMP test message is: z bits of value 0,.

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

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

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

Optionally, the S/R bit may also have multiple bits, and the processing unit is configured to determine whether the TWAMP test packet carrying the S/R bit is reflected by using another value.

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 implementing the method of the second aspect. The device is located the sending end equipment side, includes: a processing unit, a transmitting unit and a receiving unit; wherein,

the processing unit is used for generating 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 returned by the reflection end device, where the returned TWAMP test packet includes an identifier indicating that the returned TWAMP test packet is a reflection packet.

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

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

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

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

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

In a fifth aspect, a communication system is provided, which includes a sending end device and a reflecting end device, and is characterized in that: the reflecting end device comprises the apparatus of the third aspect, and the transmitting end device comprises the apparatus of the fourth aspect. The system is adapted to perform the method of the first aspect and the method of the second aspect.

In a sixth aspect, the present application provides a sending end device, including a memory and a processor, where the memory is used to store program instruction codes, and the processor is used to execute the instruction codes in the memory, so as to complete the method of the first aspect. The sending end device includes the apparatus of the third aspect.

In a seventh aspect, the present application provides a reflective end device, including a memory and a processor, where the memory is used for storing program instruction codes, and the processor is used for executing the instruction codes in the memory, thereby implementing the method of the second aspect. The reflective end device comprises the apparatus 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 and second aspects described above, including a program designed to perform the methods of the first and second aspects.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of TWAMP message reflection and looping in the prior art

Fig. 2 is a schematic view of an application scenario related to the message processing method provided in the present application;

fig. 3 is a schematic flowchart of a message processing method according to an embodiment of the present application;

fig. 4 is a schematic diagram of a format of a possible TWAMP test packet sent by a sending end device in an embodiment of the present application;

fig. 5 is a schematic flowchart of a message processing method according to another embodiment of the present application;

fig. 6 is a schematic diagram of a format of a possible TWAMP test packet sent by a sending end device in another embodiment of the present application;

fig. 7A is a schematic diagram of an execution main body of a message processing method according to an embodiment of the present application;

fig. 7B is a schematic diagram of another implementation main body of a message processing method according to an embodiment of the present application;

fig. 8A is a schematic diagram of a message processing apparatus according to an embodiment of the present application;

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

Detailed Description

The application scenario described in the embodiment of the present application is for more clearly illustrating the technical solution of the embodiment of the present application, and does not form a limitation on the technical solution provided in the embodiment of the present application, and it can be known by those skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of a network architecture and the appearance of a new service scenario.

The sending end device may be a router or a packet transport network device or a switch, and the reflecting end device may be a router or a packet transport network device or a switch.

Example 1

Fig. 2 is a schematic view of an application scenario related to a message processing method according to an embodiment of the present application, and as shown in fig. 2, a device a is a TWAMP test message sending end device, a device C is a TWAMP test message reflecting end device, and one or more intermediate devices, for example, an intermediate device B, are arranged between the device a and the device C. The destination IP address configured in the 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 the device a to the 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 TWAMP test packet reflected from device C back to device a carries a destination IP address of 2.2.2.2, a source IP address of 1.1.1.1, a destination port number of 2222, and a source port number of 1111. The device A sends a TWAMP test message to the device C, and the parameters of network bidirectional packet loss, time delay, jitter and the like are counted through testing the round-trip IP performance between the device A and the device C. The device B is an intermediate device in the TWAMP test packet transmission path, and due to human misoperation, the device B is configured as a reflection-end device, that is, the destination IP address configured in the device B 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.

Fig. 3 is a schematic diagram of a format of a possible TWAMP test packet sent by a sending-end device. As shown in fig. 3: in a TWAMP test message sent by sending end equipment, 13 th to 16 th bytes are source IP addresses (SIP), and occupy 32 bits in total; the 17 th byte to the 20 th byte is a destination IP address (DIP), and the total length of the destination IP address occupies 32 bits; bytes 21-22 are Source Port numbers (Source ports), which occupy 16 bits; bytes 23-24 are Destination Port numbers (Destination ports), accounting for 16 bits. Bytes 41-42 are Error Estimate (Error Estimate) bytes, the Error Estimate takes up a total of 16 bits, the Error Estimate bytes include: s bit (1bit), Z bit (1bit), Scale (6bit), Multiplier (8 bit). Wherein, the S bit indicates whether the clock generating the timestamp is synchronized to the identifier of Universal Time Coordinated (UTC), the S bit is 1 to indicate that the clock is synchronized with the external UTC, and the S bit is 0 to indicate that the clock is not synchronized with the external UTC. The Z bit is a reserved bit in error evaluation, and is defined in ietf rfc5357 standard, when the sending end device sends a TWAMP test packet, the Z bit must be set to 0, when the reflecting end device receives the TWAMP test packet, the Z bit is not verified, and when the sending end device receives the TWAMP test packet returned by the reflecting end device, the Z bit is also not verified. Scale is a power (Scale) in error assessment, 2^ Scale, used to assess error usage; multiplier is a Multiplier factor in error estimation, also used for estimating error usage. Starting at byte 43, there is a Padding byte (Padding) with either a pseudo random code or an all 0 code.

In this embodiment of the present application, when it is required to detect a round-trip IP performance between a sending end device (e.g., device a in fig. 1) and a reflecting end device (e.g., device C in fig. 1) in a network, the device a serves as the sending end device, constructs and sends a TWAMP test packet, and forwards the TWAMP test packet to the reflecting end device C through an intermediate device B. In the TWAMP test message sent by the sending-end device, the Z bit value is 0. The following describes the message processing method provided in the embodiment of the present application in detail with reference to fig. 4. The application is illustrated with the method applied to the scenario shown in fig. 2. The method comprises the following steps:

401: the sending terminal equipment generates and sends the TWAMP test message.

The device a, as a sending end device, generates and sends a TWAMP test packet, which is forwarded to the reflecting end device C via the intermediate device B. When the device A serves as the sending end device to send the TWAMP test message, the Z bit in the TWAMP test message is set to be 0, and the TWAMP test message is represented to be not a reflection message. And when receiving the TWAMP test message, the reflecting end device C returns the TWAMP test message to the sending end device a, where the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflected message. In particular, the flag may be a Z bit having a value of 1. The TWAMP test message is a User Datagram Protocol (UDP) message.

402: and the next hop equipment receives the TWAMP test message.

When the device a sends the TWAMP test packet to the device C, the device a forwards the TWAMP test packet to a next hop device, that is, the device B, through route query, and the device B receives the TWAMP test packet.

403: and the next-hop device respectively matches the destination IP address, the source IP address, the destination port number and the source port number of the TWAMP test message with the source IP address, the destination IP address, the source port number and the destination port number configured by the next-hop device, if the matching is successful, 404 is executed, if the matching is failed, the next-hop device continues to forward the destination IP address, and 402 and 403 are repeatedly executed.

When the TWAMP test packet sent by the device a reaches the device B, the device B receives the TWAMP test packet, and the device B first matches a destination IP address, a source IP address, a destination port number, and a source port number carried in the TWAMP test packet with a source IP address, a destination IP address, a source port number, and a destination port number configured by the device B itself. If the destination IP address, the source IP address, the destination port number, and the source port number carried in the TWAMP test packet are respectively consistent with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device B, it is determined that the matching is successful, and the device B determines that the received packet is the TWAMP test packet, and continues to execute 404. If the destination IP address, the source IP address, the destination port number, and the source port number carried in the TWAMP test packet are not consistent with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device B, it is considered that the matching fails, and the operation continues 402 and 403. Therefore, if the matching is successful, the device B returns the TWAMP test message to the sending end device a of the test message. And if the matching fails, continuing to forward the destination IP address to the next-hop equipment.

In this embodiment of the present application, a destination IP address, a source IP address, a destination port number, and a source port number carried in a TWAMP test packet are not consistent with a source IP address, a destination IP address, a source port number, and a destination port number configured by the device B, matching fails, and the device B continues to forward the TWAMP test packet to the destination IP address of the TWAMP test packet. When the TWAMP test packet reaches the device C, the device C matches the destination IP address, the source IP address, the destination port number, and the source port number carried in the TWAMP test packet with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device C, determines the destination IP address, the source IP address, the destination port number, and the source port number carried in the TWAMP test packet, and determines that the matching is successful if the destination IP address, the source port number, and the destination port number are consistent with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device C. The device C determines that the received message is a TWAMP test message, and determines that the device C is a reflection-side device corresponding to the transmission-side device a.

404: the reflection end device determines whether a Z bit in the received TWAMP test message is 0, if so, the execution 405 is executed, and if not, the TWAMP test message is discarded.

In the TWAMP test message sent by the sending-end device a, the Z bit is 0, and the TWAMP test message is forwarded to the reflecting-end device C through the intermediate device B. After receiving the TWAMP test message, the device C determines that the Z bit in the TWAMP test message is 0, determines that the TWAMP is not a reflection message, and then includes an identifier indicating that the returned TWAMP test message is a reflection message in the TWAMP test message, for example, the value of the Z bit in the TWAMP test message is set to 1, and the device C returns the TWAMP test message including the identifier to the sending-end device a.

The TWAMP test message returned by device C passes through device B again when returned to the sending end device a. Due to artificial misconfiguration, the destination IP address, the source IP address, the destination port number, and the source port number carried by the TWAMP test packet returned by the device C are consistent with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device B, so that the destination IP address, the source IP address, the destination port number, and the source port number carried by the TWAMP test packet returned by the device C are successfully matched with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device B. The device B determines that the TWAMP test message is received, and the device B determines whether the Z bit of the received TWAMP message is 0. Since the device C at the reflection end has set the value of the Z bit of the returned TWAMP test packet to 1, the device B determines that the value of the Z bit of the received TWAMP message is not 0, and then determines that the received TWAMP test packet is a reflection packet, and at this time, the device B discards the TWAMP test packet without performing reflection, thereby effectively avoiding forming a packet loop and reducing the risk of network storm.

405: and the reflecting end device sends the TWAMP test message back to the sending end device, wherein the sent TWAMP test message comprises an identifier indicating that the sent TWAMP test message is a reflecting message.

If the value of the Z bit of the TWAMP test packet received by the device C is 0, it indicates that the TWAMP test packet is not a reflection packet. 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-end device a, where the TWAMP test message that is sent back may further include other fields of the corresponding TWAMP protocol, such as a message sequence number, a timestamp, a time-to-live TTL, a source IP address, a destination IP address, a source port number, a destination port number, and the like.

In embodiment 1, the value of the Z bit may also be 1 to indicate that the TWAMP test packet carrying the Z bit is not reflected, and the value of the Z bit is 0 to indicate that the TWAMP test packet carrying the Z bit is reflected by the reflection end device.

Example 2

Fig. 5 is a schematic flowchart of a message processing method according to another embodiment of the present application, which is illustrated by applying the method to the scenario shown in fig. 2. The method comprises the following steps:

501: the sending terminal equipment generates and sends the TWAMP test message.

The device a, as a sending end device, generates and sends a TWAMP test packet, which is forwarded to the reflecting end device C via the intermediate device B. The format of the TWAMP test message is shown in fig. 6. Basically the same as the message format shown in fig. 3, except that: in the 43 th byte belonging to the stuff byte in the TWAMP test message, a sending end device/reflecting end device S/R bit is set. The S/R bit is set to 1bit and the other 7 bits are set to the reserved field Resv. The Resv field may be set to all 0 s, or may be set to other values to identify a specific packet type of the TWAMP test packet.

Alternatively, the S/R bit may have multiple bits, and other values are used to indicate whether the TWAMP test packet carrying the S/R bit is reflected. Further optionally, the S/R bit may be disposed at other positions of the stuff byte.

In the embodiment of the present application, it is illustrated that the TWAMP test packet is not a reflection packet by using the S/R bit of 0, and the TWAMP test packet is a reflection packet by using the S/R bit of 1. When the device A serves as the sending end device to send the TWAMP test message, the S/R bit in the TWAMP test message is set to be 0, and the TWAMP test message is represented to be not a reflection message. And when receiving the TWAMP test message, the reflecting end device C returns the TWAMP test message to the sending end device a, where the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflected message. In particular, the flag may be an S/R bit having a value of 1. The TWAMP test message is a User Datagram Protocol (UDP) message.

502: and the next hop equipment receives the TWAMP test message.

503: and the next-hop device respectively matches the destination IP address, the source IP address, the destination port number and the source port number of the TWAMP test message with the source IP address, the destination IP address, the source port number and the destination port number configured by the next-hop device, if the matching is successful, 504 is executed, if the matching is failed, the next-hop device continues to forward the destination IP address, and 502 and 503 are repeatedly executed.

The specific processes of steps 502-503 are the same as those of steps 402-403 in embodiment 1, and reference may be made to the description of embodiment 1, which is not repeated herein.

504: and the reflection end equipment determines whether the S/R bit in the received TWAMP test message is 0 or not, if so, 505 is executed, and if not, the TWAMP test message is discarded.

In the TWAMP test message sent by the sending-end device a, the S/R bit is 0, and the TWAMP test message is forwarded to the reflecting-end device C through the intermediate device B. After receiving the TWAMP test message, the device C determines that the S/R bit in the TWAMP test message is 0, determines that the TWAMP is not a reflection message, and then includes an identifier indicating that the returned TWAMP test message is a reflection message in the TWAMP test message, for example, the value of the S/R bit in the TWAMP test message is set to 1, and the device C returns the TWAMP test message including the identifier to the sending-end device a. The TWAMP test message returned by device C passes through device B again when returned to the sending end device a. Due to artificial misconfiguration, the destination IP address, the source IP address, the destination port number, and the source port number carried by the TWAMP test packet returned by the device C are consistent with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device B, so that the destination IP address, the source IP address, the destination port number, and the source port number carried by the TWAMP test packet returned by the device C are successfully matched with the source IP address, the destination IP address, the source port number, and the destination port number configured by the device B. Device B determines that a TWAMP test message is received. The device B determines whether the S/R bit of the received TWAMP test packet is 0. Since the device C at the reflection end has set the value of the S/R bit of the returned TWAMP test packet to 1, the device B determines that the value of the Z bit of the received TWAMP packet is not 0, and then determines that the received packet is a reflection packet, and at this time, the device B discards the TWAMP test packet without reflection, thereby effectively avoiding the formation of a packet loop and reducing the risk of network storm.

505. And the reflecting end device sends the TWAMP test message back to the sending end device, wherein the sent TWAMP test message comprises an identifier indicating that the sent TWAMP test message is a reflecting message.

If the value of the S/R bit of the test packet received by the device C is 0, it indicates that the test packet is not a reflection packet. The device C sets the value of the S/R bit in the received TWAMP test message to 1, and sends the TWAMP test message back to the sending-end device a, where the TWAMP test message that is sent back may also include other fields of the corresponding TWAMP protocol, such as message sequence number, timestamp, time-to-live TTL, source IP address, destination IP address, source port number, destination port number, and the like.

Example 3

Fig. 7A and 7B are schematic diagrams illustrating possible hardware structures of a transmitting end device and a reflecting end device for performing the methods provided in embodiments 1 and 2. The sending end device may be the sending end device 600 shown in fig. 7A and the reflecting end device may be the reflecting end device 700 shown in fig. 7B.

The transmitting end device 600 comprises a processor 601 and a network interface 602, said processor 601 communicating with the reflecting end device 700 via the network interface 602.

A processor 601, configured to generate a TWAMP test packet;

the network interface 602 is configured to send a TWAMP test packet, and further configured to receive a TWAMP test packet returned by the reflection-side device, where the returned TWAMP test packet includes an identifier indicating that the returned TWAMP packet is a reflection packet.

The processor 601 is further configured to set a Z bit in the TWAMP test message to 0, which is used to indicate that the TWAMP test message is not a reflection message; the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflection message. The flag may be a Z bit having a value of 1.

Optionally, the processor 601 is further configured to set a Z bit in the TWAMP test message to 1, which is used to indicate that the TWAMP test message is not a reflection message; the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflection message. The flag may be a Z bit having a value of 0.

Optionally, the processor 601 is further configured to set a sending end/reflection end S/R bit in the TWAMP test message to 0, where the sending end/reflection end S/R bit is used to indicate that the TWAMP test message is not a reflection message; the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflection message. The flag may be an S/R bit having a value of 1.

Optionally, the processor 601 is further configured to set a sending end/reflection end S/R bit in the TWAMP test message to 1, where the sending end/reflection end S/R bit is used to indicate that the TWAMP test message is not a reflection message; the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflection message. The flag may be an S/R bit having a value of 0.

The reflective end device 700 comprises a processor 701 and a network interface 702, wherein the processor 701 communicates with the transmitting end device 600 through the network interface 702.

A network interface 702, configured to receive the TWAMP test packet sent by the sending-end device.

The processor 701 is configured to generate a loopback TWAMP test packet if it is determined that the TWAMP test packet is not a reflection packet, where the loopback TWAMP test packet includes an identifier indicating that the loopback TWAMP test packet is a reflection packet.

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

The processor 701 is further configured to determine that a Z bit in the TWAMP test message sent by the sending-end device is 0, and then determine that the TWAMP is not a reflection message. The processor 701 is further configured to set a value of a reserved Z bit in the looped-back TWAMP test packet to 1, so as to indicate that the looped-back TWAMP test packet is a reflection packet.

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

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

Optionally, the processor 701 is further configured to determine that the TWAMP test packet is not a reflection packet if the S/R bit of the sending end/the reflection end is 0, and the processor 701 is further configured to set the S/R bit in the returned TWAMP test packet to 1, which is used to indicate that the returned TWAMP test packet is a reflection packet.

Optionally, the processor 701 is further configured to determine that the TWAMP test packet is not a reflection packet if the determined S/R bit of the sending end/the reflection end is 1; the processor 701 is further configured to set the S/R bit in the looped-back TWAMP test packet to 0, so as to indicate that the looped-back TWAMP test packet is a reflection packet.

In another embodiment, as shown in fig. 7A, the sender device 600 may include a processor 601, a network interface 602, a memory 603, and a bus 604. The processor 601, network interface 602, and memory 603 communicate over a bus 604. The processor 601 communicates with the reflector 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. The processor 701, network interface 702, and memory 703 communicate over a bus 704. The processor 701 communicates with the sender device 600 through the network interface 702.

Processor 601 and processor 701 may be one or more Central Processing Units (CPUs). When the processor 601 or the processor 701 is one 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 Fiber Distributed Data Interface (FDDI) Interface and Gigabit Ethernet (GE) Interface.

Memory 603 and memory 703 may be, but are not limited to, one or more of Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM), compact disc read only memory (CD-ROM), a hard disk, and the like. Memory 603 and memory 703 are used to store program codes.

The memory 603 stores program instruction codes, and the processor 601 is configured to execute the instruction codes in the memory 603 to implement 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 implement the methods in embodiment 1 and embodiment 2. Example 4:

fig. 8A shows a schematic diagram of a message processing apparatus 800. The method is used for executing the message processing methods provided by the embodiments 1 and 2. The message processing apparatus 800 is located at the sending-end device 600 side. The packet 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 packet.

A sending unit 802, configured to send the TWAMP packet.

A receiving unit 803, configured to receive a TWAMP test packet sent back by the reflection end device, where the sent back TWAMP test packet includes an identifier indicating that the TWAMP message is a reflection packet.

The units may be logically units, functional components generated after software codes stored in a memory are read by a CPU and executed in a specific implementation process, or may be implemented by hardware units.

The processing unit 801 is further configured to set a Z bit in the TWAMP test message to 0, which is used to indicate that the TWAMP test message is not a reflection message; the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflection message. The flag may be a Z bit having a value of 1.

Optionally, the processing unit 801 is further configured to set a Z bit in the TWAMP test message to 1, which is used to indicate that the TWAMP test message is not a reflection message; the returned TWAMP test message includes an identifier indicating that the returned TWAMP test message is a reflection message. The flag may be a Z bit having a value of 0.

Optionally, the processing unit 801 is further configured to set a sending end/reflection end S/R bit in the TWAMP test message to 0, where the sending end/reflection end S/R bit is used to indicate that the TWAMP test message is not a reflection message; the reflection end device is configured to set the S/R bit in the returned TWAMP test message to 1, and is configured to indicate that the returned TWAMP test message is a reflection message.

Optionally, the processing unit 801 is further configured to set a sending end/reflection end S/R bit in the TWAMP test message to 1, where the sending end/reflection end S/R bit is used to indicate that the TWAMP test message is not a reflection message; the reflection end device is configured to set the S/R bit in the returned TWAMP test message to 0, and is configured to indicate that the returned TWAMP test message is a reflection message.

The message processing apparatus 800 provided in fig. 8A may be integrated in the sending-end device 600 described in fig. 7A, and be applied to the scenario shown in fig. 2 to implement the function of the sending-end device. For example, the processing unit 801 may be implemented by the processor 601 of fig. 7A, and one or more of the transmitting unit 802 and the receiving unit 803 may be implemented by the network interface of fig. 7A. For other additional functions that the message processing apparatus 800 can implement and the interaction process with the reflection-side device, refer to the description of the methods in embodiment 1 and embodiment 2, and are not described herein again.

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

A receiving unit 901, configured to receive a TWAMP test packet.

A processing unit 902, configured to determine that the TWAMP test packet is not a reflection packet, generate a loopback TWAMP test packet, where the loopback TWAMP test packet includes an identifier indicating that the loopback TWAMP test packet is a reflection packet.

A sending unit 903, configured to send the looped back TWAMP test packet.

Optionally, the processing unit 902 is further configured to determine that the Z bit in the TWAMP test message is 0, and then determine that the TWAMP is not a reflection message. The processing unit 902 is further configured to set a value of a reserved Z bit in the looped-back TWAMP test message to 1, so as to indicate that the looped-back TWAMP test message is a reflection message.

Optionally, the processing unit 902 is further configured to determine that the Z bit in the TWAMP test message is 1, and then determine that the TWAMP is not a reflection message. The processing unit 902 is further configured to set a value of a reserved Z bit in the looped-back TWAMP test message to 0, so as to indicate that the looped-back TWAMP test message is a reflection message.

Optionally, the processing unit 902 is further configured to determine that the TWAMP test packet is not a reflection packet if the determined S/R bit of the sending end/reflection end is 0, and the processing unit 902 is further configured to set the S/R bit in the returned TWAMP test packet to 1, which is used to indicate that the returned TWAMP test packet is a reflection packet.

Optionally, the processing unit 902 is further configured to determine that the TWAMP test packet is not a reflection packet if the determined S/R bit of the sending end/reflection end is 1; the processing unit 902 is further configured to set the S/R bit in the looped-back TWAMP test message to 0, so as to indicate that the looped-back TWAMP test message is a reflection message.

The message processing apparatus 900 provided in fig. 8B may be integrated in the reflection-side device 700 described in fig. 6B, and be applied to the scenario shown in fig. 2 to implement the function of the reflection device. For example, the processing unit 902 may be implemented by the processor 701 of fig. 7B, and one or more of the receiving unit 901 and the transmitting unit 903 may be implemented by the network interface 702 of fig. 7B. For other additional functions that the message processing apparatus 900 can implement and the interaction process with the sending-end device, refer to the descriptions in embodiment 1 and embodiment 2, and are not described herein again.

The message processing apparatus provided in the present application is exemplified by only the division of the above functional modules, and in practical applications, the above functions may be allocated with different functional modules to complete as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above described functions.

Example 5

The application provides a communication system, which comprises sending end equipment and reflecting end equipment. The sending end device and the reflecting end device may be the sending end device and the reflecting end device provided in embodiment 3. The sending end device may include the message processing apparatus on the sending end device side provided in embodiment 4, and the reflection end device may include the message processing apparatus on the reflection end device side provided in embodiment 4. The sending end device and the reflecting end device are used for executing the methods described in the embodiments 1 and 2.

The communication system can also further comprise a control client device and a server, wherein after the control client device and the server interact control signaling messages to establish a control session, the control client device informs the server to establish a statistical session through the signaling messages. The signaling mainly refers to the negotiation and statistics of information such as IP addresses and UDP port numbers at two ends of the session, and after the negotiation at the two ends is successful, the establishment of the statistical session is successful. After the statistical session is started, the sending end equipment sends a test message, the test message carries information such as a timestamp and a sending serial number, the reflecting end equipment receives the test message and then responds, and the reflecting end equipment sends a response test message, wherein the response test message carries information such as the timestamp and the response serial number. And after receiving the response test message, the sending end equipment calculates an IP performance statistical result and sends the IP performance statistical result to the control client equipment, and the statistical data is uniformly maintained by the control client equipment and presented to the user. The establishment of the control session between the control client and the server and the establishment of the statistical session between the sending-end device and the sending-end device described in this embodiment are performed according to the prior art, and are not described herein again.

Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over 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 place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

All parts of the specification are described in a progressive mode, the same and similar parts of all embodiments can be referred to each other, and each embodiment is mainly introduced to be different from other embodiments. In particular, as to the apparatus and system embodiments, since they are substantially similar to the method embodiments, the description is relatively simple and reference may be made to the description of the method embodiments in relevant places.

Finally, it is to be noted that: the above description is only a preferred embodiment of the present disclosure, and is not intended to limit the scope of the present disclosure. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. To the extent that such modifications and variations of the present application fall within the scope of the claims and their equivalents, they are intended to be included within the scope of the present application.

Claims

1. A method for processing a TWAMP message of a two-way active measurement protocol is characterized by comprising the following steps:

2. The method of claim 1, wherein the determining that the TWAMP test packet is not a reflection packet comprises: and determining that the Z bit in the TWAMP test message is 0, and determining that the TWAMP test message is not a reflection message.

3. The method of claim 2, wherein the identification is: z bit of value 1.

4. The method of claim 1, wherein the determining that the TWAMP test packet is not a reflection packet comprises: and the reflection end equipment determines that the S/R bit of the sending end/the reflection end in the TWAMP test message is 0, and determines that the TWAMP test message is not a reflection message.

5. The method of claim 4, further comprising: the identification is as follows: S/R bits with a value of 1.

6. The method according to any one of claims 1-5, further comprising: and when the TWAMP test message is determined to be a reflection message by the reflection end equipment, discarding the reflection message.

7. A method for processing a TWAMP message of a bidirectional active measurement protocol is characterized by comprising the following steps:

sending a TWAMP test message to a reflection end device by a sending end device;

8. The method of claim 7, wherein: and the value of a Z bit in the TWAMP test message sent by the sending terminal equipment is 0, which indicates that the TWAMP test message is not a reflection message.

9. The method of claim 8, wherein the identification is: z bit of value 1.

10. The method of claim 7, wherein: and setting the S/R bit of the sending end/the reflection end in the TWAMP test message to be 0, and indicating that the TWAMP test message sent by the sending end equipment is not a reflection message.

11. The method of claim 10, wherein: the identification is as follows: S/R bits with a value of 1.

12. A bidirectional active measurement protocol TWAMP message processing apparatus is characterized in that the apparatus is located at a side of a reflection end device, and the apparatus comprises: a receiving unit, a processing unit and a transmitting unit; wherein,

the receiving unit is used for receiving a TWAMP test message;

and the sending unit is used for sending the returned TWAMP test message.

13. The apparatus of claim 12, wherein: the processing unit is configured to determine that the TWAMP is not a reflection packet if the Z bit in the TWAMP test packet is determined to be 0.

14. The apparatus of claim 13, wherein: the identification is as follows: z bit of value 1.

15. The apparatus of claim 12, wherein: the processing unit is configured to determine that a sending end/reflection end S/R bit in the TWAMP test message is 0, and determine that the TWAMP test message is not a reflection message.

16. The apparatus of claim 15, wherein: the identification is as follows: S/R bits with a value of 1.

17. The apparatus according to any one of claims 12-16, wherein: the processing unit is further configured to discard the reflection packet when determining that the TWAMP test packet is a reflection packet.

18. A two-way active measurement protocol TWAMP message processing device is characterized in that the device is positioned at a sending end device side and comprises a processing unit, a sending unit and a receiving unit; wherein,

the processing unit is used for generating a TWAMP test message;

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

19. The apparatus of claim 18, wherein: the processing unit is further configured to set a Z bit in the TWAMP test message sent by the sending unit to 0.

20. The apparatus of claim 19, wherein: the identification is as follows: z bit of value 1.

21. The apparatus of claim 18, wherein: the processing unit is further configured to set a sending end/reflection end S/R bit in the TWAMP test message sent by the sending unit to 0.

22. The apparatus of claim 21, wherein: the identification is as follows: S/R bits with a value of 1.

23. A communication system comprises a sending terminal device and a reflecting terminal device, and is characterized in that: the reflecting end device comprising the apparatus of any of claims 13-17 and the transmitting end device comprising the apparatus of any of claims 18-22.