Network testing method and device, network equipment and computer readable storage medium
By setting a fixed UDP port number in a TWAMP Light session and determining the target session using the session ID, the TWAMP Light network testing method in the prior art solves the problems of UDP port number conflict and low data forwarding performance when handling multiple sessions, and realizes more efficient network testing.
Patent Information
- Application Number
- CN202411644876.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-18
- Publication Date
- 2025-02-25
- Estimated Expiration
- 2044-11-18
AI Technical Summary
When the existing TWAMP Light network testing method handles multiple sessions, there are problems such as UDP port number conflict and low data forwarding performance, resulting in inaccurate test results.
By setting a fixed UDP port number in a TWAMP Light session and using the session ID to determine the target session of the test response message from multiple sessions, the matching time is reduced and the UDP port resource usage is reduced.
It improves the data forwarding performance of network tests, reduces conflicts in UDP port numbers, and ensures the normal transmission and reception of test packets and the accuracy of test results.
Smart Images

Figure CN119520345A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a network testing method, apparatus, network equipment and computer-readable storage medium. Background Art
[0002] With the rapid development of computer network technology, more and more services are carried in the network, and voice, video, games and other services have higher and higher requirements for network packet loss and latency. Based on this, network managers need to test the network to understand the network packet loss and latency in a timely manner, so as to adjust and optimize the network according to the test results to meet network service needs.
[0003] Currently, network testing of devices can be performed using TWAMP (Two-Way Active Measurement Protocol). TWAMP can be used to measure network performance parameters between any two devices in the network, providing a basis for network quality analysis. TWAMP Light is a lightweight architecture of the TWAMP protocol that simplifies the control protocol for establishing performance measurement sessions. Therefore, TWAMP Light technology can be used for network testing.
[0004] In the prior art, the TWAMP Light test includes a source test device and a destination test device. When using the TWAMP Light technology for network testing, a test session is configured on the source test device (the basic parameters of the test session are the IP quadruple, i.e., source IP address, destination IP address, UDP source port number, and UDP destination port number). The destination test device also needs to be configured with the same test session as the source device (i.e., the same IP quadruple) to perform network testing by sending and receiving test messages.
[0005] Specifically, the source device may send a test request message to the destination device. After receiving the test request message, the destination device generates a test response message and returns it to the source device. The source device calculates the network performance parameters based on the test response message.
[0006] However, this method also has certain problems. Since there may be multiple sessions in the device to be tested, the device to be tested needs to match the IP four-tuple information of the test response message with the IP four-tuple information of each session after receiving the test response message, so as to determine the corresponding session. Since there is a lot of IP four-tuple information, if there are a large number of sessions in the device to be tested, this method will take a long time, thus affecting the overall data forwarding performance of the test.
[0007] In addition, since each session corresponds to different IP quadruple information, a different UDP port number needs to be configured for each session, which will aggravate the conflict of UDP port numbers and cause abnormal sending and receiving of test messages, thereby causing inaccurate test results. Summary of the invention
[0008] In view of this, the purpose of the present application is to provide a network testing method, apparatus, network equipment and computer-readable storage medium to improve the overall data forwarding performance of the test, while reducing the occupancy of UDP port resources, alleviating conflicts in UDP port numbers, thereby ensuring the normal sending and receiving of test messages and improving the accuracy of test results.
[0009] In order to achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:
[0010] In a first aspect, the present application provides a network testing method, which is applied to a first network device, wherein the first network device is communicatively connected to a second network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the first network device and the second network device, the method comprising:
[0011] Obtaining a test response message sent by the second network device; the test response message is a reply message corresponding to a test request message sent by the first network device to the second network device for any of the sessions;
[0012] When it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, obtaining a session ID from the test response message;
[0013] A target session corresponding to the test response message is determined from the multiple sessions according to the session ID, and a test result corresponding to the target session is determined according to the timestamp information corresponding to the test response message.
[0014] In an optional implementation manner, after acquiring the test response message sent by the second network device, the method further includes:
[0015] Obtain UDP port setting information, and determine whether the UDP port number of the TWAMP Light-based session is set to a fixed port number according to a preset identifier in the UDP port setting information;
[0016] The step of obtaining the session ID from the test response message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number includes:
[0017] In the case where it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, determining whether the UDP port number of the test response message matches the fixed port number;
[0018] If the UDP port number of the test response message matches the fixed port number, the session ID is obtained from the test response message.
[0019] In an optional embodiment, the method further comprises:
[0020] If it is determined that the UDP port number of the TWAMP Light-based session is not set to a fixed port number, then based on the IP quadruple information of each of the sessions and the IP quadruple information of the test response message, when it is determined that there is a corresponding session of the test response message among the multiple sessions, a format check is performed on the test response message, and if the test response message passes the check, the test result of the corresponding session is determined according to the timestamp information corresponding to the test response message.
[0021] In an optional implementation manner, the step of obtaining a session ID from the test response message includes:
[0022] Performing format verification on the test response message, and if the test response message passes the verification, obtaining the session ID from a padding field of the test response message;
[0023] The step of determining a target session corresponding to the test response message from the plurality of sessions according to the session ID, and determining a test result corresponding to the target session according to the timestamp information corresponding to the test response message, comprises:
[0024] Determine a target session corresponding to the test response message from the plurality of sessions according to the session ID, and determine whether the IP information of the test response message matches the IP information corresponding to the target session;
[0025] If the IP information of the test response message matches the IP information corresponding to the target session, the test result corresponding to the target session is determined according to the timestamp information corresponding to the test response message.
[0026] In an optional implementation manner, determining the test result corresponding to the target session according to the timestamp information corresponding to the test response message includes:
[0027] Obtain a receiving timestamp of the test response message, and obtain a sending timestamp of the test response message, a sending timestamp and a receiving timestamp of a test request message corresponding to the test response message from the test response message;
[0028] The test result corresponding to the target session is determined according to the sending timestamp and receiving timestamp of the test response message and the sending timestamp and receiving timestamp of the test request message.
[0029] In an optional implementation manner, before the step of obtaining the test response message sent by the second network device, the method further includes:
[0030] Determine a session to be processed, and construct a test request message corresponding to the session to be processed according to a preset communication protocol;
[0031] In the case where it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, adding the session ID corresponding to the to-be-processed session to the padding field of the test request message;
[0032] The current time is added to the test request message as a sending timestamp of the test request message, and the test request message is sent to the second network device according to the IP four-tuple information corresponding to the session to be processed.
[0033] In an optional implementation manner, before the step of acquiring the test response message sent by the second network device, the method further includes:
[0034] The UDP port of the session based on TWAMP Light is configured and saved as UDP port setting information, wherein the UDP port setting information includes a preset identifier indicating whether the UDP port number of the session based on TWAMP Light is set to a fixed port number.
[0035] In a second aspect, the present application provides a network testing method, which is applied to a second network device, wherein the second network device is communicatively connected to a first network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the second network device and the first network device, the method comprising:
[0036] Obtaining a test request message sent by the first network device for any of the sessions;
[0037] When it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, obtaining a session ID from the test request message;
[0038] A test response message corresponding to the test request message is generated according to the session ID, and the test response message is sent to the first network device.
[0039] In an optional implementation manner, the step of generating a test response message corresponding to the test request message according to the session ID, and sending the test response message to the first network device includes:
[0040] When it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, obtaining a session ID from the test request message;
[0041] In the case that it is determined according to the session ID that there is a target session corresponding to the test request message among the multiple sessions, the current time is used as the sending timestamp of the test response message, and a test response message is generated according to the sending timestamp of the test response message, the receiving timestamp of the test request message, the sending timestamp of the test response message and the session ID of the target session;
[0042] The test response message is sent to the first network device after performing header encapsulation according to the IP quadruple information of the target session.
[0043] In a third aspect, the present application provides a network testing device, which is applied to a first network device, wherein the first network device is communicatively connected to a second network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the first network device and the second network device, and the device includes:
[0044] An acquisition module, used to acquire a test response message sent by the second network device; the test response message is a reply message corresponding to a test request message sent by the first network device to the second network device for any of the sessions;
[0045] The acquisition module is further configured to acquire the session ID from the test response message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number;
[0046] The test module is used to determine the target session corresponding to the test response message from the multiple sessions according to the session ID, and determine the test result corresponding to the target session according to the timestamp information corresponding to the test response message.
[0047] In a fourth aspect, the present application provides a network testing device, which is applied to a second network device, the second network device is communicatively connected to a first network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the second network device and the first network device, the device comprising:
[0048] A receiving module, used to obtain a test request message sent by the first network device for any of the sessions;
[0049] The processing module obtains a session ID from the test request message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number; and generates a test response message corresponding to the test request message according to the session ID;
[0050] A sending module is used to send the test response message to the first network device.
[0051] In a fifth aspect, the present application provides a network device, comprising a processor and a memory, wherein the memory stores a computer program that can be executed by the processor, and the processor can execute the computer program to implement the method described in any one of the aforementioned implementations.
[0052] In a sixth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method described in any one of the aforementioned embodiments is implemented.
[0053] The network testing method, apparatus, network device, and computer-readable storage medium provided in the embodiments of the present application are such that the first network device can obtain the test response message sent by the second network device, and obtain the session ID from the test response message when determining that the UDP port number of the session based on TWAMP Light is set to a fixed port number, thereby determining the target session corresponding to the test response message from multiple sessions according to the session ID, and determining the test result corresponding to the target session according to the timestamp information corresponding to the test response message. In this method, the session based on TWAMP Light can be set to a fixed UDP port number, thereby reducing the occupation of UDP port resources, alleviating the conflict of UDP port numbers, thereby ensuring the normal sending and receiving of test messages, and improving the accuracy of test results; in addition, the method can determine the target session corresponding to the test response message from multiple sessions only through the session ID, thereby reducing the matching time and improving the overall data forwarding performance of the test.
[0054] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0055] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0056] Figure 1 A block schematic diagram of a communication system is shown;
[0057] Figure 2 A block diagram of a network device provided in an embodiment of the present application is shown;
[0058] Figure 3 A schematic diagram of a flow chart of a network testing method provided in an embodiment of the present application is shown;
[0059] Figure 4 A schematic diagram showing the format of a test request message is shown;
[0060] Figure 5 Another schematic diagram of a network testing method provided in an embodiment of the present application is shown;
[0061] Figure 6 A schematic diagram showing the format of a test response message is shown;
[0062] Figure 7 A functional module diagram of a network testing device provided in an embodiment of the present application is shown;
[0063] Figure 8 Another functional module diagram of the network testing device provided in an embodiment of the present application is shown.
[0064] Icons: 10 - first network device; 20 - second network device; 100 - memory; 110 - processor; 120 - communication module; 200 - acquisition module; 210 - test module; 300 - receiving module; 310 - processing module; 320 - sending module. DETAILED DESCRIPTION
[0065] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.
[0066] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.
[0067] It should be noted that relational terms such as the terms "" and "" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprises a..." do not exclude the existence of other identical elements in the process, method, article or device that includes the elements.
[0068] Figure 1 For a block diagram of the communication system, see Figure 1 The communication system includes a first network device 10 and a second network device 20, and the first network device 10 and the second network device 20 are communicatively connected.
[0069] Optionally, multiple sessions based on the lightweight two-way active measurement protocol TWAMP Light are created between the first network device and the second network device. That is, the first network device and the second network device are both provided with corresponding sessions, which can be used to perform network testing between the first network device and the second network device.
[0070] In this embodiment, each session may be provided with a session ID. It can be understood that the session ID can uniquely represent a session.
[0071] Optionally, the first network device refers to a device that initiates a network test for any session, and the second network device refers to a device that responds to the network test.
[0072] In this embodiment, any network device can be used as a first network device to perform a network test, and can also be used as a second network device to perform a network test.
[0073] Furthermore, Figure 2 For a block diagram of a network device provided in an embodiment of the present application, please refer to Figure 2The network device includes a memory 100, a processor 110 and a communication module 120. The memory 100, the processor 110 and the communication module 120 are electrically connected to each other directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses or signal lines.
[0074] The memory 100 is used to store computer programs or data that can be executed by the processor. The memory 100 can be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM), etc.
[0075] The processor 110 is used to read / write data or computer programs stored in the memory, and execute the computer program to implement the network testing method provided in the embodiment of the present application.
[0076] The communication module 120 is used to establish a communication connection between the network device and other communication terminals through the network, and to send and receive data through the network.
[0077] It can be understood that the network device can be Figure 1 The first network device in the Figure 2 It should be understood that Figure 2 The structure shown is only a schematic diagram of the structure of the network device. The network device may also include Figure 2 More or fewer components as shown, or with Figure 2 Different configurations are shown. Figure 2 Each component shown in the figure can be implemented by hardware, software or a combination thereof.
[0078] Next, the above Figure 1 The first network device in the example is the execution subject, and the network testing method provided in the embodiment of the present application is introduced exemplarily in combination with the flowchart. Specifically, Figure 3 A flowchart of a network testing method provided in an embodiment of the present application is shown in FIG. Figure 3 , the method comprising:
[0079] Step S20: Obtain a test response message sent by the second network device.
[0080] Optionally, the test response message is a reply message corresponding to a test request message sent by the first network device to the second network device for any session.
[0081] In this embodiment, the first network device can first generate a corresponding test request message for any session and send the message to the corresponding second network device. The second network device can then generate a test response message corresponding to the test request message and send the test response message to the first network device.
[0082] Step S21, when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, a session ID is obtained from the test response message.
[0083] In this embodiment, in order not to modify the existing protocol standard message format and simplify the protocol processing process, when the UDP port numbers of the TWAMP Light-based sessions in the network device are all set to fixed port numbers, the test response message information will carry the session ID.
[0084] It can be understood that the UDP port number of the TWAMP Light-based session is a fixed port number, which means that no matter whether it is the first network device or the second network device, the UDP source port in the IP quadruple of all configured TWAMP Light sessions is a fixed preset port number (such as 1001), and the UDP destination port is also a fixed preset port number (such as 1002). Regardless of which network device a TWAMP Light session is established with, the same fixed UDP source port and the same fixed UDP destination port number are used, and they are the same on all devices.
[0085] Step S22, determining a target session corresponding to the test response message from multiple sessions according to the session ID, and determining a test result corresponding to the target session according to the timestamp information corresponding to the test response message.
[0086] Optionally, the first network device may determine the target session corresponding to the test response message from multiple sessions according to the session ID by means of ID matching.
[0087] It can be understood that compared with the prior art method that requires matching the IP quadruple information with the IP quadruple information of each session to determine the corresponding session, matching only through the session ID parameter can significantly reduce the time consumption, thereby improving the overall data forwarding performance of the test.
[0088] Optionally, the test result may include network performance parameters between the first network device and the second network device, such as two-way delay, jitter, packet loss rate, etc.
[0089] In the network testing method provided in the embodiment of the present application, the first network device can obtain the test response message sent by the second network device, and obtain the session ID from the test response message when determining that the UDP port number of the session based on TWAMP Light is set to a fixed port number, thereby determining the target session corresponding to the test response message from multiple sessions according to the session ID, and determining the test result corresponding to the target session according to the timestamp information corresponding to the test response message. In this method, the session based on TWAMP Light can be set to a fixed UDP port number, thereby reducing the occupation of UDP port resources, alleviating the conflict of UDP port numbers, thereby ensuring the normal sending and receiving of test messages, and improving the accuracy of test results; in addition, the method can determine the target session corresponding to the test response message from multiple sessions only through the session ID, thereby reducing the matching time and improving the overall data forwarding performance of the test.
[0090] Optionally, before performing the network test, it is necessary to first arrange the network test environment in the first network device and the second network device, that is, configure relevant parameters and generate a TWAMP Light-based session.
[0091] In a possible implementation, in order to facilitate the generation of a session and the execution of a subsequent network test process, the first network device and the second network device may first configure UDP port setting information.
[0092] In this embodiment, the UDP port of the TWAMP Light session may be configured and saved as UDP port setting information.
[0093] Optionally, the UDP port setting information may include a preset identifier indicating whether the UDP port number of the TWAMP Light-based session is set to a fixed port number.
[0094] It can be understood that the fixed UDP port number here means that both the UDP source port number and the UDP destination port number are fixed.
[0095] Optionally, the UDP port setting information may further include a preset UDP port number. It is understandable that the preset UDP port number refers to a fixed port number based on a TWAMP Light session.
[0096] In one possible implementation, if the UDP port number of the TWAMP Light-based session is set to a fixed port number, the preset flag may be 1; if the UDP port number of the TWAMP Light-based session is not set to a fixed port number, the preset flag may be 0.
[0097] The embodiment of the present application can configure the UDP port of the TWAMP Light-based session, thereby setting whether the UDP port number of the session is a fixed port number, thereby improving the application flexibility of the TWAMP Light-based session to adapt to the interconnection between devices from different manufacturers.
[0098] Optionally, after configuring the UDP port of the TWAMP Light-based session, the first network device and the second network device may generate a TWAMP Light-based session.
[0099] In this embodiment, the first network device and the second network device may first create a session based on TWAMP Light, and generate a session ID corresponding to the session according to preset rules, and then obtain the UDP port setting information. If the preset identifier in the UDP port setting information represents that the UDP port number of the session is set to a fixed port number, the IP quadruple information is configured for the session according to the preset IP information and the preset UDP port number.
[0100] It can be understood that the first network device and the second network device can create multiple sessions according to actual test requirements.
[0101] Optionally, the preset rule can be set according to actual application conditions, such as randomly generated, or generated in sequence according to a certain rule.
[0102] It should be noted that, for a session corresponding to a network test, the session ID in the first network device and the session ID in the second network device should be consistent.
[0103] Optionally, after generating the session ID, if the preset identifier in the UDP port setting information represents that the UDP port number of the session is set to a fixed port number, the first network device and the second network device may set the preset UDP port number as the UDP port information in the IP quadruple information of the session.
[0104] It can be understood that the preset UDP port number includes a preset UDP source port number and a preset UDP destination port number.
[0105] Optionally, the preset IP information includes source IP information and destination IP information, wherein the source IP information refers to the IP information of the first network device, and the destination IP information refers to the IP information of the second network device.
[0106] It can be understood that for a network test, the IP information in the session of the first network device matches the IP information in the session of the second network device, and the UDP port number in the session of the first network device matches the UDP port number in the session of the second network device.
[0107] Specifically, for a session, the source IP information and UDP source port number contained therein are the IP information and UDP port number of the first network device, and the destination IP information and UDP destination port number are the IP information and UDP port number of the second network device.
[0108] For example, if the source IP information in the session of the first network device is x and the destination IP information is y, then the source IP information in the session of the second network device is also x, and the destination IP information is y; if the UDP source port number in the session of the first network device is m and the UDP destination port number is n, then the UDP source port number in the session of the second network device is m and the UDP destination port number is n.
[0109] Optionally, if the preset identifier indicates that the UDP port number fixing function is not enabled, the first network device and the second network device may allocate UDP information to the session according to a preset allocation rule to generate IP quadruple information for the session.
[0110] Optionally, after a session ID and IP quadruple information are generated for the created session, it can be determined that the session is generated.
[0111] In this embodiment, in order to manage multiple sessions, a session list may also be set in the first network device and the second network device. On this basis, the first network device and the second network device may add the session and the session ID corresponding to the session to the session list after generating the session.
[0112] Optionally, as the first network device, a pending session to be started may be determined from the session list according to actual needs.
[0113] In a possible implementation, the corresponding sessions may be started in sequence according to the arrangement order, or the pending sessions to be started may be determined according to the priority.
[0114] Optionally, after determining the pending session to be started, the first network device may read preset start parameters to configure the sending parameters of the session.
[0115] Optionally, the sending parameters include a time interval for sending a test request message, a duration or a number of test request messages sent, a timeout period for waiting for a test response message, etc.
[0116] It is understandable that for a network test, the first network device may send multiple test request messages, thereby obtaining multiple test response messages to calculate the test result.
[0117] In this embodiment, after configuring the sending parameters of the session, the first network device may configure the session to be in the start state, and then generate a corresponding test request message according to the sending parameters for sending.
[0118] Next, a possible implementation method is provided for how to generate and send a test request message.
[0119] Specifically, the first network device can first determine the session to be processed, construct a test request message corresponding to the session to be processed according to the preset communication protocol, and when determining that the UDP port number of the TWAMP Light-based session is set to a fixed port number, add the session ID corresponding to the session to be processed to the fill field of the test request message.
[0120] Optionally, the first network device may determine whether the UDP port number of the TWAMPLight-based session is set to a fixed port number according to a preset identifier in the UDP port setting information.
[0121] Optionally, if the UDP port number of the session is set to a fixed port number, the first network device may add a session ID corresponding to the session to be processed to the test request message.
[0122] In this embodiment, since the message protocol is not modified and the padding field of the test request message is random padding data, the first network device can add the session ID to the padding field of the test request message, for example, to the first two bytes of the padding field.
[0123] Optionally, to facilitate subsequent determination of the test results, the first network device may also add the current time as the sending timestamp of the test request message to the test request message, and then send the test request message to the second network device according to the IP quadruple information corresponding to the session to be processed.
[0124] In this embodiment, if the UDP port number of the session is not set to a fixed port number, the session ID is not added to the test request message, but the current time is added to the test request message as the sending time of the test request message.
[0125] In one example, Figure 4 For a diagram of the test request message format, see Figure 4The test request message may include four fields, namely Sequence Number, Timestamp, Error Estimate, and Packet Padding, where Sequence Number is the message sending sequence number, Timestamp is the timestamp when the message is sent, ErrorEstimate is the estimated error, and Packet Padding is the padding field.
[0126] In this example, the first network device can generate a Sequence Number, Error Estimate, and Packet Padding according to a preset communication protocol, and fill these fields into a test request message. After that, when it is determined that the UDP port number of the session is set to a fixed port number, the session ID corresponding to the session to be processed is added to the first two bytes of PacketPadding, and then the current time is used as the sending time and filled into the Timestamp field of the test request message.
[0127] In this example, if the UDP port number of the session is not set to a fixed port number, the current time is directly used as the sending time and filled in the Timestamp field of the test request message.
[0128] In this example, the first network device may encapsulate the test request message with a UDP and IP header according to the IP quadruple information of the session to be processed, and then send the test request message to the second network device.
[0129] Optionally, the second network device may process the test request message accordingly after receiving it, generate a test response message corresponding to the test request message, and send the test response message to the first network device.
[0130] Optionally, for the first network device, after receiving the test response message sent by the second network device, it needs to first obtain the UDP port setting information, and determine whether the UDP port number of the TWAMPLight-based session is set to a fixed port number according to the preset identifier in the UDP port setting information.
[0131] In this embodiment, if the UDP port number of the session is set to a fixed port number, the first network device can determine whether the UDP port number of the test response message matches the fixed port number. If it matches, the session ID is obtained from the test response message for subsequent operations.
[0132] It can be understood that if the UDP port number of the TWAMP Light-based session is set to a fixed port number, the UDP port number of the test response message returned by the second network device based on the test request message should match the fixed preset UDP port number.
[0133] In this embodiment, if the UDP port number of the session based on TWAMP Light is a fixed port number, but the UDP port number of the message does not match the preset UDP port number, the test response message may have a sending error problem. Therefore, the first network device can send the message to the system packet receiving module for processing.
[0134] Optionally, if the UDP port number of the TWAMP Light-based session is not set to a fixed port number, the first network device needs to determine whether there is a corresponding session for the test response message among multiple sessions based on the IP quadruple information of each session and the IP quadruple information of the test response message.
[0135] In this embodiment, the first network device can perform format verification on the test response message when it is determined that there is a corresponding session for the test response message in multiple sessions, and when the test response message passes the verification, determine the test result of the corresponding session according to the timestamp information corresponding to the test response message. Optionally, if there is no corresponding session for the test response message in multiple sessions, the first network device can send the test response message to the system packet receiving module for processing.
[0136] Optionally, the first network device may verify the field format of the test response message. For example, if the MBZ field in the test response message must be 0, the first network device may verify the field format by determining the value of the field.
[0137] Optionally, if the test response message fails the verification, it may indicate that an error may occur during the generation or sending of the test response message, and thus the test response message may be discarded.
[0138] In this embodiment, when the UDP port numbers of multiple sessions are set to fixed port numbers, the first network device also needs to verify the message format of the test response message first, and then obtain the session ID if the verification passes.
[0139] Specifically, the first network device may perform a format check on the test response message, and if the test response message passes the check, obtain the session ID from a padding field of the test response message.
[0140] Optionally, the first network device may verify the field format of the test response message. For example, if the MBZ field in the corresponding message must be 0, the first network device may verify the field format by determining the value of the field.
[0141] Optionally, if the test response message fails the verification, it may indicate that an error may occur during the generation or sending of the test response message, and thus the test response message may be discarded.
[0142] Optionally, the first network device can obtain the session ID when the test response message passes the verification, and determine the target session corresponding to the test response message from multiple sessions based on the session ID, and determine whether the IP information of the test response message matches the IP information corresponding to the target session.
[0143] It can be understood that if the IP information of the test response message matches the IP information corresponding to the target session, the first network device can determine the test result corresponding to the target session according to the timestamp information corresponding to the test response message.
[0144] Optionally, considering that a session may be deleted by mistake, the first network device may not be able to find the target session corresponding to the test response message from multiple sessions according to the session ID. In this case, the test response message may be discarded.
[0145] Furthermore, considering that there may be a problem of incorrect determination of the target session, the first network device also needs to determine whether the IP information of the test response message matches the IP information corresponding to the target session after acquiring the target session.
[0146] It can be understood that if the IP information of the test response message does not match the IP information corresponding to the target session, the test response message is discarded.
[0147] Optionally, the timestamp information corresponding to the test response message may include a reception time when the first network device receives the test response message, and the timestamp information recorded in the test response message.
[0148] Next, a possible implementation method is provided for determining the test result corresponding to the target session according to the timestamp information corresponding to the test response message.
[0149] Specifically, the first network device can obtain the receiving timestamp of the test response message, and obtain the sending timestamp of the test response message, the sending timestamp and the receiving timestamp of the test request message corresponding to the test response message from the test response message, and then determine the test result corresponding to the target session based on the sending timestamp and the receiving timestamp of the test response message and the sending timestamp and the receiving timestamp of the test request message.
[0150] Optionally, the reception timestamp of the test response message refers to the time when the first network device determines that the received message is a test response message.
[0151] In this embodiment, the first network device can calculate performance parameters such as two-way delay, jitter, packet loss rate, etc. between the first network device and the second network device based on the sending timestamp and receiving timestamp of the test response message and the sending timestamp and receiving timestamp of the test request message.
[0152] Next, the above Figure 1 The second network device in the embodiment is the execution subject, and the network testing method provided in the embodiment of the present application is introduced exemplarily in combination with the flowchart. Specifically, Figure 5 For another flowchart of the network testing method provided in the embodiment of the present application, please refer to Figure 5 , the method comprising:
[0153] Step S30: Acquire a test request message sent by the first network device for any session.
[0154] Step S31, when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, obtain a session ID from the test request message; and generate a test response message corresponding to the test request message.
[0155] Step S32: Send the test response message to the first network device.
[0156] In this embodiment, after the second network device sends the test response message to the first network device, the first network device can obtain the session ID from the test response message when determining that the UDP port number of the TWAMP Light-based session is set to a fixed port number, determine the target session corresponding to the test response message from multiple sessions based on the session ID, and determine the test result corresponding to the target session based on the timestamp information corresponding to the test response message.
[0157] Optionally, after receiving the test request message sent by the first network device, the second network device may first obtain UDP port setting information, and determine whether the UDP port number of the TWAMP Light-based session is set to a fixed port number according to a preset identifier in the UDP port setting information.
[0158] In this embodiment, if the UDP port number of the TWAMP Light-based session is set to a fixed port number, the second network device can obtain the session ID from the test request message if the UDP port number of the test request message matches the preset UDP port number in the UDP port setting information.
[0159] It can be understood that if the UDP port number of the test request message does not match the preset UDP port number in the UDP port setting information, the second network device can send the test request message to the system packet receiving module for processing.
[0160] In this embodiment, if the UDP port number of the TWAMP Light-based session is not set to a fixed port number, the second network device can determine whether there is a corresponding session for the test request message in multiple sessions based on the IP quadruple information of each session and the IP quadruple information of the test request message.
[0161] It is understandable that if there is no corresponding session of the test request message in multiple sessions, the second network device can send the test request message to the system packet receiving module for processing. Optionally, if the UDP port number of the test request message matches the preset UDP port number in the UDP port setting information, the second network device can generate its corresponding test response message and send it to the first network device.
[0162] Specifically, in this case, the second network device may perform a format check on the test request message, and construct a test response message if the test request message passes the format check.
[0163] Optionally, before obtaining the session ID, the second network device also needs to verify the message format of the test request message. The specific verification method is consistent with the verification method of the test response message by the first network device, and this application will not go into details.
[0164] It can be understood that the second network device can obtain the session ID from the test request message when the message format verification passes.
[0165] In a possible implementation manner, the second network device may obtain the session ID from a padding field of the test request message.
[0166] In a possible implementation, the session ID is located in the first two bytes of the padding field in the test request message, and the second network device can obtain the first two bytes of the padding field and use them as the session ID.
[0167] Optionally, if the test request message fails the verification, the test request message may be discarded.
[0168] In this embodiment, the second network device can also use the current time as the sending timestamp of the test response message when it is determined based on the session ID that there is a target session corresponding to the test request message among multiple sessions, and generate a test response message based on the sending timestamp of the test response message, the receiving timestamp of the test request message, the sending timestamp of the test response message and the session ID of the target session.
[0169] Optionally, after acquiring the session ID, the second network device may first determine whether a corresponding session exists among the multiple sessions according to the session ID, and if so, determine whether the IP information of the test request message matches the IP information of the session.
[0170] In this embodiment, if the IP information of the test request message matches the IP information of the session corresponding to the test request message, it can be determined that the session is the target session corresponding to the test request message. At this time, the second network device can first construct a test response message corresponding to the test request message according to the preset communication protocol and the test request message.
[0171] Optionally, if there is no session corresponding to the test request message among multiple sessions, or the IP information of the test request message does not match the IP information of the session corresponding to the test request message, it can be determined that the target session corresponding to the test request message cannot be obtained, so the second network device can discard the test request message.
[0172] Optionally, when constructing a test response message corresponding to the test request message, the second network device may copy some information in the test request message to the test response message, and generate other field information according to the protocol specification.
[0173] In this embodiment, the second network device can also use the current time as the sending timestamp of the test response message, add the receiving timestamp of the test request message, the sending timestamp of the test response message and the session ID of the target session to the test response message, and send the test response message to the first network device after performing header encapsulation according to the IP quadruple information of the target session.
[0174] In one example, Figure 6 This is a diagram of the format of the TWAMP Light test response message. Figure 6 The test response message may include the following fields: Sequence Number, Timestamp, Error Estimate, MBZ, Receive Timestamp, Sender Sequence Number, Sender Timestamp, Sender ErrorEstimate, Sender TTL, and Packet Padding.
[0175] Among them, Sequence Number is the message sending sequence number, Timestamp is the timestamp when the test response message is sent, Error Estimate is the error estimate, MBZ is Must be zero, and its value must be 0, ReceiveTimestamp is the timestamp when the test request message is received, Sender Sequence Number is the sequence number of the test request message, and its value is copied from the Sequence Number field in the corresponding test request message, Sender Timestamp is the timestamp in the test request message, and its value is copied from the Timestamp field in the corresponding test request message, SenderError Estimate is the error estimate in the test request message, and its value is copied from the Error Estimate field in the corresponding test request message, Sender TTL is the TTL in the test request message, and its value is copied from the TTL field in the IP header of the corresponding test request message, and Packet Padding is the padding field of the message, which is randomly filled with data.
[0176] In this example, when constructing a test response message, the second network device can first fill in the corresponding values for the Sequence Number field, Error Estimate field, MBZ field, and Packet Padding field of the test response message according to the protocol specification, and fill in the Receive Timestamp field as the receiving time of the test request message when the received message is determined to be a test request message, and copy the Sequence Number field, Timestamp field, and Error Estimate field in the test request message and fill them in the Sender Sequence Number field, Sender Timestamp field, and Sender Error Estimate field respectively, and copy the TTL field in the IP header of the test request message and fill it in the Sender TTL field.
[0177] In this example, if it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, the second network device may write the session ID of the target session into the first two bytes of the padding field of the test response message.
[0178] It can be understood that if the UDP port number of the TWAMP Light-based session is not set to a fixed port number, the session ID is not added to the test response message.
[0179] In this example, the second network device can also fill in the Timestamp field with the current time as the sending time of the test response message, and then encapsulate the UDP and IP header of the test response message according to the IP quadruple information of the target session and send the test response message to the corresponding first network device, so that the first network device can process the test response message to obtain the corresponding test result.
[0180] In order to execute the corresponding steps in the above embodiments and various possible methods, a method for implementing a network testing device is provided below. Optionally, the network testing device may adopt the above Figure 2 The device structure of the network device shown.
[0181] For further information, see Figure 7 , Figure 7 A functional module diagram of a network testing device applied to a first network device provided in an embodiment of the present application. It should be noted that the basic principle and technical effects of the network testing device provided in this embodiment are the same as those of the above-mentioned embodiments. For the sake of brief description, for parts not mentioned in this embodiment, reference can be made to the corresponding contents in the above-mentioned embodiments. The network testing device includes: an acquisition module 200 and a test module 210.
[0182] The acquisition module 200 is used to acquire a test response message sent by the second network device; the test response message is a reply message corresponding to a test request message sent by the first network device to the second network device for any session.
[0183] It can be understood that the acquisition module 200 can also be used to execute the above step S20.
[0184] The acquisition module 200 is further configured to acquire the session ID from the test response message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number.
[0185] It can be understood that the acquisition module 200 can also be used to execute the above step S21.
[0186] The test module 210 is used to determine the target session corresponding to the test response message from multiple sessions according to the session ID, and determine the test result corresponding to the target session according to the timestamp information corresponding to the test response message.
[0187] It can be understood that the test module 210 can also be used to execute the above step S22.
[0188] Optionally, the acquisition module 200 is further configured to acquire UDP port setting information, and determine whether the UDP port number of the TWAMP Light-based session is set to a fixed port number according to a preset identifier in the UDP port setting information.
[0189] Optionally, the acquisition module 200 is also used to determine whether the UDP port number of the test response message matches the fixed port number when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number; if the UDP port number of the test response message matches the fixed port number, the session ID is obtained from the test response message.
[0190] Optionally, the test module 210 is also used to, if it is determined that the UDP port number of the TWAMP Light-based session is not set to a fixed port number, then, based on the IP quadruple information of each session and the IP quadruple information of the test response message, determine that there is a corresponding session for the test response message in multiple sessions, perform format verification on the test response message, and if the test response message passes the verification, determine the test result of the corresponding session according to the timestamp information corresponding to the test response message.
[0191] Optionally, the acquisition module 200 is further configured to perform format verification on the test response message, and if the test response message passes the verification, obtain the session ID from a padding field of the test response message.
[0192] Optionally, the test module 210 is also used to determine the target session corresponding to the test response message from multiple sessions based on the session ID, and determine whether the IP information of the test response message matches the IP information corresponding to the target session; if the IP information of the test response message matches the IP information corresponding to the target session, the test result corresponding to the target session is determined based on the timestamp information corresponding to the test response message.
[0193] Optionally, the test module 210 is also used to obtain the receiving timestamp of the test response message, and obtain the sending timestamp of the test response message, and the sending timestamp and receiving timestamp of the test request message corresponding to the test response message from the test response message; determine the test result corresponding to the target session according to the sending timestamp and receiving timestamp of the test response message, and the sending timestamp and receiving timestamp of the test request message.
[0194] Optionally, the network testing device further includes a sending module.
[0195] The sending module is used to determine the session to be processed, and construct a test request message corresponding to the session to be processed according to a preset communication protocol; when it is determined that the UDP port number of the session based on TWAMP Light is set to a fixed port number, the session ID corresponding to the session to be processed is added to the fill field of the test request message; the current time is added to the test request message as the sending timestamp of the test request message, and the test request message is sent to the second network device according to the IP quadruple information corresponding to the session to be processed.
[0196] Optionally, Figure 8 A functional module diagram of a network testing device applied to a second network device provided in an embodiment of the present application is shown in FIG. Figure 8 The network testing device includes: a receiving module 300, a processing module 310 and a sending module 320.
[0197] The receiving module 300 is used to obtain a test request message sent by the first network device for any session.
[0198] It can be understood that the receiving module 300 can also be used to execute the above step S30.
[0199] The processing module 310 is used to obtain a session ID from the test request message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number; and generate a test response message corresponding to the test request message according to the session ID.
[0200] It can be understood that the processing module 310 can also be used to execute the above step S31.
[0201] The sending module 320 is used to send the test response message to the first network device.
[0202] It can be understood that the sending module 320 can also be used to execute the above step S32.
[0203] Optionally, the sending module 320 is also used to, when it is determined based on the session ID that there is a target session corresponding to the test request message among multiple sessions, use the current time as the sending timestamp of the test response message, and generate a test response message based on the sending timestamp of the test response message, the receiving timestamp of the test request message, the sending timestamp of the test response message and the session ID of the target session; and send the test response message to the first network device after performing header encapsulation based on the IP quadruple information of the target session.
[0204] Optionally, the above modules can be stored in the form of software or firmware. Figure 2The memory shown in FIG. 1 or the operating system (OS) of the network device may be fixed therein and may be Figure 2 Meanwhile, the data and program codes required for executing the above modules can be stored in the memory.
[0205] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the network testing method provided in the embodiment of the present application can be implemented.
[0206] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.
[0207] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
[0208] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.
[0209] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims
1. A network testing method, characterized in that: Applied to a first network device, the first network device is communicatively connected with a second network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the first network device and the second network device, the method comprising: Obtaining a test response message sent by the second network device; the test response message is a reply message corresponding to a test request message sent by the first network device to the second network device for any of the sessions; When it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, obtaining a session ID from the test response message; A target session corresponding to the test response message is determined from the multiple sessions according to the session ID, and a test result corresponding to the target session is determined according to the timestamp information corresponding to the test response message.
2. The method according to claim 1, characterized in that After acquiring the test response message sent by the second network device, the method further includes: Obtain UDP port setting information, and determine whether the UDP port number of the TWAMPLight-based session is set to a fixed port number according to a preset identifier in the UDP port setting information; The step of obtaining the session ID from the test response message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number includes: In the case where it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, determining whether the UDP port number of the test response message matches the fixed port number; If the UDP port number of the test response message matches the fixed port number, the session ID is obtained from the test response message.
3. The method according to claim 2, characterized in that The method further comprises: If it is determined that the UDP port number of the TWAMP Light-based session is not set to a fixed port number, then based on the IP quadruple information of each of the sessions and the IP quadruple information of the test response message, when it is determined that there is a corresponding session of the test response message among the multiple sessions, a format check is performed on the test response message, and if the test response message passes the check, the test result of the corresponding session is determined according to the timestamp information corresponding to the test response message.
4. The method according to claim 1, characterized in that: The step of obtaining the session ID from the test response message comprises: Performing format verification on the test response message, and obtaining the session ID from a padding field of the test response message if the test response message passes the verification; The step of determining a target session corresponding to the test response message from the plurality of sessions according to the session ID, and determining a test result corresponding to the target session according to the timestamp information corresponding to the test response message, comprises: Determine a target session corresponding to the test response message from the plurality of sessions according to the session ID, and determine whether the IP information of the test response message matches the IP information corresponding to the target session; If the IP information of the test response message matches the IP information corresponding to the target session, the test result corresponding to the target session is determined according to the timestamp information corresponding to the test response message.
5. The method according to claim 1, characterized in that The determining the test result corresponding to the target session according to the timestamp information corresponding to the test response message includes: Obtain a receiving timestamp of the test response message, and obtain a sending timestamp of the test response message, a sending timestamp and a receiving timestamp of a test request message corresponding to the test response message from the test response message; The test result corresponding to the target session is determined according to the sending timestamp and receiving timestamp of the test response message and the sending timestamp and receiving timestamp of the test request message.
6. The method according to any one of claims 1 to 5, characterized in that: Before the step of obtaining the test response message sent by the second network device, the method further includes: Determine a session to be processed, and construct a test request message corresponding to the session to be processed according to a preset communication protocol; In the case where it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, adding the session ID corresponding to the to-be-processed session to the padding field of the test request message; The current time is added to the test request message as a sending timestamp of the test request message, and the test request message is sent to the second network device according to the IP four-tuple information corresponding to the session to be processed.
7. The method according to claim 1, characterized in that Before the step of acquiring the test response message sent by the second network device, the method further includes: The UDP port of the session based on TWAMP Light is configured and saved as UDP port setting information, wherein the UDP port setting information includes a preset identifier indicating whether the UDP port number of the session based on TWAMP Light is set to a fixed port number.
8. A network testing method, characterized in that: Applied to a second network device, the second network device is communicatively connected to a first network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the second network device and the first network device, the method comprising: Obtaining a test request message sent by the first network device for any of the sessions; When it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number, obtaining a session ID from the test request message; A test response message corresponding to the test request message is generated according to the session ID, and the test response message is sent to the first network device.
9. The method according to claim 8, characterized in that The step of generating a test response message corresponding to the test request message according to the session ID, and sending the test response message to the first network device includes: In the case that it is determined according to the session ID that there is a target session corresponding to the test request message among the multiple sessions, the current time is used as the sending timestamp of the test response message, and a test response message is generated according to the sending timestamp of the test response message, the receiving timestamp of the test request message, the sending timestamp of the test response message and the session ID of the target session; The test response message is sent to the first network device after performing header encapsulation according to the IP quadruple information of the target session.
10. A network testing device, characterized in that: Applied to a first network device, the first network device is communicatively connected with a second network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the first network device and the second network device, the apparatus comprising: An acquisition module, used for acquiring a test response message sent by the second network device; the test response message is a reply message corresponding to a test request message sent by the first network device to the second network device for any of the sessions; The acquisition module is further configured to acquire the session ID from the test response message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number; The test module is used to determine the target session corresponding to the test response message from the multiple sessions according to the session ID, and determine the test result corresponding to the target session according to the timestamp information corresponding to the test response message.
11. A network testing device, characterized in that: Applied to a second network device, the second network device is communicatively connected to a first network device, and a plurality of sessions based on a lightweight bidirectional active measurement protocol TWAMP Light are established between the second network device and the first network device, the apparatus comprising: A receiving module, used to obtain a test request message sent by the first network device for any of the sessions; The processing module obtains a session ID from the test request message when it is determined that the UDP port number of the TWAMP Light-based session is set to a fixed port number; and generates a test response message corresponding to the test request message according to the session ID; A sending module is used to send the test response message to the first network device.
12. A network device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program executable by the processor, and the processor can execute the computer program to implement the method described in any one of claims 1 to 7, or the method described in any one of claims 8 to 9.
13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method described in any one of claims 1 to 7 or any one of claims 8 to 9 is implemented.
Citation Information
Patent Citations
Network performance measuring method, apparatus and system
CN106603333A
TWAMP session negotiation method, client, and server
CN107979619A
Network quality measurement method and device for bundled link, equipment and medium
CN112714036A
Selecting and monitoring a plurality of services key performance indicators using twamp
EP3099015A1
Acceleration of node configuration for twamp with a large number of test sessions
US20190280931A1
Cited By
Message forwarding method and device, multi-core processor, network equipment and storage medium
CN120935243A