Method, device, system and storage medium for predicting rate of flow

Abstract

The application discloses a method, device and system for predicting the rate of traffic and a storage medium. The method comprises: obtaining configuration information of a test device; matching the configuration information with test device configuration information corresponding to a preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the input traffic rate and the output traffic rate of a to-be-tested device are inconsistent; and in response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, determining a predicted output traffic rate of the to-be-tested device according to the test device configuration information corresponding to the preset traffic scenario and traffic characteristic information corresponding to the preset traffic scenario.

Description

Technical Field

[0001] This application relates to the field of equipment testing technology, and in particular to a method, apparatus, system and storage medium for predicting flow rate. Background Technology

[0002] Current testing instruments only calculate the transmission rate of the instrument port and do not consider the potential for data traffic to escalate on the device under test (DUT). This means that scenarios exist where data traffic exceeds line speed on the DUT side. Currently, there is no effective solution to this problem. Summary of the Invention

[0003] To address the related technical problems, embodiments of this application provide a method, apparatus, system, and storage medium for predicting the rate of traffic flow.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a method for predicting the rate of traffic flow, including:

[0006] Obtain the configuration information of the test equipment;

[0007] The configuration information is matched with the test device configuration information corresponding to the preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the rate of input traffic and the rate of output traffic of the device under test are inconsistent.

[0008] When the configuration information matches the test device configuration information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario.

[0009] In the above scheme, determining the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario includes:

[0010] Based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario, determine the data frame length change information corresponding to the preset traffic scenario;

[0011] Based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined.

[0012] The method in the above scheme further includes:

[0013] Determine whether the predicted rate of the output flow of the device under test is greater than a preset threshold;

[0014] If the predicted rate of the output traffic of the device under test is greater than the preset threshold, the rate of the output traffic of the device under test is configured to the preset threshold.

[0015] The method in the above scheme further includes:

[0016] The rate at which the test device sends traffic to the device under test is determined based on the preset threshold.

[0017] In the above scheme, the preset traffic scenario includes at least one traffic scenario; the step of matching the configuration information with the test device configuration information corresponding to the preset traffic scenario includes:

[0018] The configuration information is matched with the test device configuration information corresponding to each of the at least one traffic scenario.

[0019] The method in the above scheme further includes:

[0020] If, in one of the at least one traffic scenario, the configuration information of the test device matches the configuration information, then it is determined that the test device being tested has a scenario where the rate of input traffic and the rate of output traffic are inconsistent.

[0021] If in none of the at least one traffic scenario the test device configuration information matches the configuration information, then it is determined that the device under test tested by the test device does not have a scenario where the input traffic rate and the output traffic rate are inconsistent.

[0022] In the above scheme, the response occurs after the configuration information matches the test device configuration information corresponding to the preset traffic scenario; the method further includes:

[0023] Determine whether the device under test being tested by the test equipment has a preset output flow rate;

[0024] If the device under test is not set to a preset output flow rate, the predicted output flow rate of the device under test is determined based on the test device configuration information corresponding to the preset flow scenario and the flow characteristic information corresponding to the preset flow scenario.

[0025] The method in the above scheme further includes:

[0026] If the device under test being tested by the test equipment has a preset output flow rate, the rate at which the test equipment sends flow to the device under test is determined according to the preset output flow rate.

[0027] In the above scheme, the preset traffic scenario includes at least one traffic scenario; the response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario includes:

[0028] When the configuration information matches the test device configuration information corresponding to the first traffic scenario in the at least one traffic scenario.

[0029] In the above scheme, determining the data frame length change information corresponding to the preset traffic scenario based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario includes:

[0030] The rate of the output traffic of the test device corresponding to the first traffic scenario is obtained based on the test device configuration information corresponding to the first traffic scenario.

[0031] Based on the rate of the output traffic of the test device corresponding to the first traffic scenario and the traffic characteristic information corresponding to the first traffic scenario, the tag length added to at least one data frame in the first traffic scenario is determined.

[0032] The data frame length variation information corresponding to the first traffic scenario is determined based on the tag length added to at least one data frame in the first traffic scenario.

[0033] In the above scheme, determining the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario includes:

[0034] The length of the tag added to the first data frame in the first traffic scenario is determined by using the data frame length change information corresponding to the first traffic scenario; the first data frame is any data frame among at least one data frame in the first scenario;

[0035] Based on the tag length added to the first data frame in the first traffic scenario and the rate of the output traffic of the test device corresponding to the first traffic scenario obtained from the test device configuration information corresponding to the first traffic scenario, the predicted rate of the output traffic of the device under test is predicted.

[0036] This application also provides a flow rate prediction device, comprising:

[0037] The acquisition unit is used to acquire configuration information of the test equipment;

[0038] A matching unit is used to match the configuration information with the test device configuration information corresponding to a preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the rate of input traffic and the rate of output traffic of the device under test are inconsistent.

[0039] The determining unit is configured to, in response to a match between the configuration information and the test device configuration information corresponding to the preset traffic scenario, determine the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario.

[0040] This application also provides a traffic rate prediction system, including: a processor and a memory for storing a computer program that can run on the processor.

[0041] When the processor runs the computer program, it executes the steps of any of the above methods.

[0042] This application also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of any of the above methods.

[0043] The traffic rate prediction method, apparatus, system, and storage medium provided in this application embodiment acquire configuration information of a test device; match the configuration information with test device configuration information corresponding to a preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the input traffic rate and output traffic rate of the device under test are inconsistent; in response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, determine the predicted traffic rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario. The solution of this application embodiment, by matching the configuration information with the preset traffic scenario... The corresponding test device configuration information is matched, wherein the preset traffic scenario is a known scenario in which the input traffic rate and output traffic rate of the device under test are inconsistent; in response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined according to the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario, thereby considering the problem of data traffic expansion in the device under test, that is, the existence of a data traffic exceeding the line speed scenario in the device under test, and thus predicting the traffic rate of the port of the device under test, thereby avoiding the occurrence of the traffic rate exceeding the line speed scenario of the port of the device under test. Attached Figure Description

[0044] Figure 1 This is a schematic diagram illustrating a scenario in this application where data traffic exceeds line speed on the device under test.

[0045] Figure 2 This is a schematic diagram illustrating a method for predicting the rate of traffic flow according to an embodiment of this application;

[0046] Figure 3 The diagram below illustrates an application scenario of the traffic rate prediction method of this application.

[0047] Figure 4 This is a schematic diagram illustrating a traffic escalation scenario for testing the L3VPN protocol in an embodiment of this application.

[0048] Figure 5 This is a schematic diagram illustrating a traffic escalation scenario during L2VPN protocol testing, as described in an embodiment of this application.

[0049] Figure 6 This is a schematic diagram illustrating a traffic expansion scenario tested using the Vxlan protocol in an embodiment of this application.

[0050] Figure 7 This is a schematic diagram illustrating a traffic expansion scenario during SRv6 protocol testing, as described in an embodiment of this application.

[0051] Figure 8 This is a schematic diagram illustrating the expected device-side transmission format and instrument-side transmission format in the embodiments of this application;

[0052] Figure 9 This is a schematic diagram of the flow rate prediction device according to an embodiment of this application;

[0053] Figure 10 This is a schematic diagram of the traffic rate prediction system structure according to an embodiment of this application. Detailed Implementation

[0054] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0055] In related technologies, network testing instruments and equipment only calculate the sending rate of traffic. However, when testing the characteristics of protocols such as Multi-Protocol Label Switching (MPLS), Virtual eXtensible Local Area Network (VxLAN), Segment Routing (SR), Segment Routing IPv6 (SRv6), and G-Segment Routing IPv6 (G-SRv6) based on the China Mobile IPv6 forwarding plane, the device under test adds specific tags to existing packets, causing frame structure expansion. This results in a discrepancy between the speed of the device under test's port and the speed of the testing instrument's sending port. When the speed at the testing instrument's sending end approaches line speed, the increased frame length can cause the device under test's receiving port to exceed line speed, leading to abnormal test results.

[0056] Furthermore, current testing instruments only calculate the transmission rate of the instrument port, without considering the potential for data traffic saturation on the network under test. This can lead to scenarios where data traffic exceeds line speed on the device under test, resulting in packet loss and failing to achieve the expected testing results. Figure 1 The test scenarios in Figure 1 This is a schematic diagram illustrating a scenario in this application where data traffic exceeds line speed on the device under test. Data traffic is sent from the CE to the PE. When the PE router processes certain protocol traffic, it adds protocol header information to the frames received at port A. This causes the frame length sent to port B to be longer than the received frame length. If the rate received by port A is line speed, port B needs to send at a rate exceeding line speed, resulting in packet loss at port B, which affects the device under test.

[0057] Based on this, in various embodiments of this application, the configuration information is matched with the test device configuration information corresponding to a preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the rate of input traffic and the rate of output traffic of the device under test are inconsistent; in response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, the predicted rate of output traffic of the device under test is determined according to the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario.

[0058] This application provides a method for predicting traffic flow rate, applied to a traffic flow rate prediction system, such as... Figure 2 As shown, Figure 2This is a schematic diagram of a method for predicting the rate of traffic flow according to an embodiment of this application. The method includes:

[0059] Step 201: Obtain the configuration information of the test equipment;

[0060] Step 202: Match the configuration information with the test device configuration information corresponding to the preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the input traffic rate and the output traffic rate of the device under test are inconsistent;

[0061] Step 203: In response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, determine the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario.

[0062] In step 201, the testing equipment can be any network testing instrument or device, without limitation. As an example, the testing equipment can be a test instrument. The device under test can be determined according to the actual situation, without limitation. As an example, the device under test can be an MPLS device, a device implementing the VXLAN protocol, a device implementing the SR protocol, a device implementing the SRv6 protocol, etc.; in practical applications, the device under test can also be called the device under test.

[0063] Here, obtaining the configuration information of the test device can be understood as reading relevant information from the test device's configuration; the relevant information can be determined according to the actual situation and is not limited here. As an example, the relevant information may include the type of device under test, the protocol types included in the test scenario, the test topology, etc.

[0064] In step 202, the preset traffic scenario can be determined according to the actual situation, and is not limited here. In practical applications, the preset traffic scenario can also be called a traffic expansion scenario, or simply a scenario library.

[0065] The preset traffic scenario can be one or more traffic scenarios; the test device configuration information corresponding to the preset traffic scenario can be understood as each traffic scenario in the preset traffic scenario having its own corresponding test device configuration information; the preset traffic scenario can be determined according to the actual situation and is not limited here. As an example, the preset traffic scenario can be an L3VPN scenario, an L2VPN scenario, a Vxlan scenario, or an SRV6 VPN scenario. In practical applications, the preset traffic scenario can also be called a traffic expansion scenario.

[0066] The preset traffic scenarios are known scenarios where the input and output traffic rates of the device under test are inconsistent. This can be understood as listing all traffic expansion scenarios and constructing a scenario library, which constitutes the preset traffic scenarios. The test device configuration information corresponding to the preset traffic scenarios can be understood as analyzing the characteristics of various traffic expansion scenarios, finding the unique combination of features for each traffic expansion scenario, and then configuring the test device according to the unique combination of features for each traffic expansion scenario. In practical applications, the test device configuration information corresponding to the preset traffic scenarios can be the relevant configuration information of the test device corresponding to each traffic scenario within the preset traffic scenarios; that is, it can be understood as reading relevant information from the test device configuration corresponding to each traffic scenario. The relevant information can be determined according to the actual situation and is not limited here. As an example, the relevant information may include the type of device under test, the protocol type included in the test scenario, the test topology, etc.

[0067] As an example, when one of the preset traffic scenarios is an L3VPN scenario, the characteristic information corresponding to the L3VPN scenario can be L3VPN binding flow, sent from CE to PE; the test device configuration information corresponding to the L3VPN scenario in the preset traffic scenario can be reading MP-IBGP / MP-EBPG Virtual Private Network (VPN) related configuration, reading Link State Protocol (Intermediate System-to-Intermediate System, ISIS) related configuration, reading binding flow configuration, protocol header type, and reading Label Distributed Protocol (Label Distributed Protocol) configuration. Protocol (LDP) related configuration; when one of the preset traffic scenarios is an L2VPN scenario, the characteristic information corresponding to the L2VPN scenario can be L2VPN binding flow, sent from CE to PE; the test device configuration information corresponding to the L2VPN scenario in the preset traffic scenario can be reading LDP protocol configuration, label layer number, reading binding flow configuration, and protocol type; when one of the preset traffic scenarios is a VxLAN scenario, the characteristic information corresponding to the VxLAN scenario can be VxLAN binding flow, sent from CE to PE; the test device configuration information corresponding to the VxLAN scenario in the preset traffic scenario can be reading VxLAN protocol configuration information, reading VxLAN VTEP configuration information, reading binding flow configuration, and protocol header type; when the preset traffic scenario is an SRV6 VPN scenario, the preset characteristic information matched by the configuration information can be SRv6-VPN binding flow, sent from CE to PE; the preset configuration information matched by the configuration information can be reading SRv6 protocol configuration information, reading SRV6VPN related information, reading binding flow configuration, and protocol header type.

[0068] The test device can transmit traffic at a rate through its sending port; the input traffic rate of the device under test can be understood as the traffic rate received by the receiving port of the device under test; the output traffic rate of the device under test can be understood as the traffic rate emitted by the sending port of the device under test. In practical applications, the device under test can also be referred to as the device being tested.

[0069] In this embodiment, the main consideration is that when the test device tests the protocol characteristics of the device under test, the device under test will add some specific tags on the existing messages, which will cause the frame structure to expand and result in the rate of the port of the device under test being inconsistent with the rate of the sending port of the test device.

[0070] In one embodiment, the preset traffic scenario includes at least one traffic scenario; matching the configuration information with the test device configuration information corresponding to the preset traffic scenario includes:

[0071] The configuration information is matched with the test device configuration information corresponding to each of the at least one traffic scenario.

[0072] It should be noted that the at least one traffic scenario can be determined based on actual circumstances and is not limited here. As an example, the at least one traffic scenario may include L3VPN, L2VPN, Vxlan, SRV6 VPN, etc.

[0073] The test equipment configuration information corresponding to each of the at least one traffic scenario can be understood as analyzing the characteristics of various traffic expansion scenarios, finding the unique combination of features for each traffic expansion scenario, and the configuration information of the test equipment corresponding to the unique combination of features for each traffic expansion scenario.

[0074] Matching the configuration information with the test device configuration information corresponding to each of the at least one traffic scenario can be understood as matching the configuration information with the test device configuration information corresponding to each of the at least one traffic scenario to obtain a matching result; the matching result can be understood as either there is a case in the at least one traffic scenario where the test device configuration information corresponding to one traffic scenario matches the configuration information, or there is a case in the at least one traffic scenario where the test device configuration information corresponding to one traffic scenario does not match the configuration information.

[0075] In one embodiment, the method further includes:

[0076] If, in one of the at least one traffic scenario, the configuration information of the test device matches the configuration information, then it is determined that the test device being tested has a scenario where the rate of input traffic and the rate of output traffic are inconsistent.

[0077] If in none of the at least one traffic scenario the test device configuration information matches the configuration information, then it is determined that the device under test tested by the test device does not have a scenario where the input traffic rate and the output traffic rate are inconsistent.

[0078] It should be noted that if the configuration information of the test device for one of the at least one traffic scenarios matches the configuration information, then determining that the test device has a scenario where the input traffic rate and output traffic rate are inconsistent can be understood as the configuration information of the test device being consistent with the configuration information of the test device for a certain traffic scenario in the at least one traffic scenario, and the test device is in a certain traffic scenario in the preset traffic scenario. In this traffic scenario, the test device will add some specific tags on the existing packets, which will cause the frame structure to expand, resulting in a scenario where the input traffic rate and output traffic rate of the test device are inconsistent. Alternatively, it can be understood as the rate of the transmission port of the test device being inconsistent with the rate of the transmission port of the test instrument, that is, the traffic rate configured on the test device port changes in the test device.

[0079] If, in any of the at least one traffic scenario, the test device configuration information does not match the configuration information corresponding to any traffic scenario, then determining that the device under test tested by the test device does not have a scenario where the input traffic rate and output traffic rate are inconsistent can be understood as follows: the test device configuration information does not match the configuration information corresponding to any of the preset traffic scenarios; the device under test is not in any of the preset traffic scenarios; and the device under test does not have any specific tags added to existing packets. That is, the device under test tested by the test device does not have a scenario where the input traffic rate and output traffic rate are inconsistent. Alternatively, it can be understood as not causing the rate of the device under test port to be inconsistent with the rate of the test instrument's sending port, that is, the first traffic rate configured on the test device port does not change in the device under test.

[0080] In step 203, when the configuration information matches the test device configuration information corresponding to the preset traffic scenario, it can be understood that the configuration information matches the test device configuration information corresponding to a certain traffic scenario in the preset traffic scenario; it can also be understood that the test device under test has a scenario where the input traffic rate and the output traffic rate are inconsistent.

[0081] The scenario where the input flow rate and output flow rate of the device under test (DUT) are inconsistent under the test can be understood as a change in the input flow rate of the DUT under the test. Specifically, this could mean that the input flow rate of the DUT under the test increases or decreases within the DUT, without being limited to a single scenario. As an example, a change in the input flow rate of the DUT under the test can mean that the input flow rate of the DUT under the test increases within the DUT. For instance, the input flow rate of the DUT under the test is linear velocity; this linear velocity becomes superlinear velocity after passing through the DUT; that is, the input flow rate of the DUT under the test increases within the DUT.

[0082] Based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test can be determined by using a preset algorithm based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario; wherein, the preset algorithm can be determined according to the actual situation and is not limited here.

[0083] In one embodiment, determining the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario includes:

[0084] Based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario, the data frame length change information corresponding to the preset traffic scenario is determined.

[0085] Based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined.

[0086] It should be noted that the data frame length variation information corresponding to the preset traffic scenario can be determined according to the actual situation, and is not limited here. As an example, the data frame length variation information corresponding to the preset traffic scenario includes at least the traffic scenario and the frame length variation parameters corresponding to the traffic scenario; the frame length variation parameters include at least the tag length (bytes) and the tag depth.

[0087] In practical applications, the data frame length variation information corresponding to the preset traffic scenarios can be stored in a preset data frame length variation list. This preset data frame length variation list corresponds to a preset traffic scenario library. Specifically, each traffic scenario corresponds to at least one data frame length variation. For ease of understanding, the following examples illustrate this: a traffic scenario can be L3VPN, with a label length of 4 and a label depth of 1-6; a traffic scenario can be L2VPN, with a label length of 4 and a label depth of 1-6; a traffic scenario can be VXLAN, with a label length of 50 or 54 and a label depth of 1; a traffic scenario can be SR, with a label length of 4 and a label depth of 2-6; a traffic scenario can be SRv6, with a label length of 16 and a label depth of 2-6; and a traffic scenario can be G-SRv6, with a label length of 16 and a label depth of 2-3.

[0088] Based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test can be determined by using a preset algorithm based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario; wherein, the preset algorithm can be determined according to the actual situation and is not limited here.

[0089] In one embodiment, the method further includes:

[0090] Determine whether the predicted rate of the output flow of the device under test is greater than a preset threshold;

[0091] If the predicted rate of the output traffic of the device under test is greater than the preset threshold, the rate of the output traffic of the device under test is configured to the preset threshold.

[0092] In this embodiment, the preset threshold can be determined according to the actual situation, and is not limited here. As an example, the preset threshold can be a line speed value; the line speed value can be understood as 100% transmission.

[0093] In practical applications, the flow rate can be calculated using the following formula (1):

[0094]

[0095] In equation (1), Rate is the flow rate, also known as the ratio, denoted as R; MediaSpeed ​​is the medium speed; PreambleSize is the preamble length; FrameSize is the frame length; FrameSize is the inter-frame interval; FrameSize is the minimum inter-frame interval; FrameSize is the frame length.

[0096] When the inter-frame interval is set to the minimum inter-frame interval, the transmission rate reaches the line speed. However, if the device under test has features such as MPLS, VXLAN, SR, or SRv6, the actual frame length will increase, leading to a situation where the transmission rate exceeds the line speed.

[0097] Determining whether the predicted rate of the output flow of the device under test is greater than a preset threshold can be done by determining whether the predicted rate of the output flow of the device under test is greater than the line speed.

[0098] When the predicted rate of the output flow of the device under test is greater than the preset threshold, configuring the rate of the output flow of the device under test to the preset threshold can be understood as configuring the rate of the output flow of the device under test to the line speed when the predicted rate of the output flow of the device under test is greater than the line speed (i.e., exceeding the line speed), thereby avoiding the output flow of the device under test exceeding the line speed.

[0099] In one embodiment, the method further includes:

[0100] The rate at which the test device sends traffic to the device under test is determined based on the preset threshold.

[0101] It should be noted that the preset threshold can be determined according to the actual situation, and is not limited here. As an example, the preset threshold can be a line speed value; the line speed value can be understood as 100% transmission.

[0102] The rate at which the test device sends traffic to the device under test can also be understood as the rate at which the device under test receives traffic.

[0103] Determining the rate at which the test device sends traffic to the device under test based on the preset threshold can be understood as configuring the rate at which the test device sends traffic to the device under test based on the line velocity value. Specifically, configuring the rate at which the test device sends traffic to the device under test based on the line velocity value can be achieved using a preset algorithm. The preset algorithm can be determined based on actual conditions.

[0104] In practical applications, the test device can be an instrument device, or simply an instrument. If the user does not select to configure the expected port rate on the device side, but selects to configure the instrument port transmission rate, the instrument will automatically calculate the expected port rate of the device under test and send a prompt message to the user. When the expected port rate of the device under test exceeds the line speed, an alarm message will be issued, prompting the user to modify the configuration information. The rate of the device under test port can be reduced by reducing the frame length, increasing the IFG, etc., or the expected rate of the device under test can be set to the line speed of the device under test port with one click.

[0105] In one embodiment, after responding to the configuration information matching the test device configuration information corresponding to the preset traffic scenario; the method further includes:

[0106] Determine whether the device under test being tested by the test equipment has a preset output flow rate;

[0107] If the device under test is not set to a preset output flow rate, the predicted output flow rate of the device under test is determined based on the test device configuration information corresponding to the preset flow scenario and the flow characteristic information corresponding to the preset flow scenario.

[0108] In this embodiment, the preset output flow rate needs to be set or configured by the user according to the actual situation. In practical applications, the user can choose to set or configure the preset output flow rate of the device under test tested by the test device; the user can also choose not to set or configure the preset output flow rate of the device under test tested by the test device. If the user chooses not to set or configure the preset output flow rate of the device under test tested by the test device, the predicted flow rate of the device under test is determined according to the test device configuration information corresponding to the preset flow scenario and the flow characteristic information corresponding to the preset flow scenario.

[0109] In one embodiment, the method further includes:

[0110] If the device under test being tested by the test equipment has a preset output flow rate, the rate at which the test equipment sends flow to the device under test is determined according to the preset output flow rate.

[0111] In this embodiment, if the user selects to set or configure a preset output traffic rate for the device under test (DUT) being tested by the test device, the rate at which the test device sends traffic to the DUT is determined based on the preset output traffic rate. As an example, determining the rate at which the test device sends traffic to the DUT based on the preset output traffic rate can be achieved using a preset algorithm; wherein the preset algorithm can be determined according to actual circumstances.

[0112] In one embodiment, the preset traffic scenario includes at least one traffic scenario; the step of responding to the configuration information matching the test device configuration information corresponding to the preset traffic scenario includes:

[0113] When the configuration information matches the test device configuration information corresponding to the first traffic scenario in the at least one traffic scenario.

[0114] It should be noted that the at least one traffic scenario can be determined based on actual circumstances and is not limited here. As an example, the at least one traffic scenario can be an L3VPN scenario, an L2VPN scenario, a Vxlan scenario, an SRV6VPN scenario, etc. In practical applications, the preset traffic scenario can also be referred to as a traffic expansion scenario.

[0115] When the configuration information matches the test device configuration information corresponding to the first traffic scenario in the at least one traffic scenario, it can be understood as when the configuration information matches the test device configuration information corresponding to a certain traffic scenario in the at least one traffic scenario.

[0116] In one embodiment, determining the data frame length change information corresponding to the preset traffic scenario based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario includes:

[0117] The rate of the output traffic of the test device corresponding to the first traffic scenario is obtained based on the test device configuration information corresponding to the first traffic scenario.

[0118] Based on the rate of the output traffic of the test device corresponding to the first traffic scenario and the traffic characteristic information corresponding to the first traffic scenario, the tag length added to at least one data frame in the first traffic scenario is determined.

[0119] The data frame length variation information corresponding to the first traffic scenario is determined based on the tag length added to at least one data frame in the first traffic scenario.

[0120] It should be noted that the first traffic scenario needs to be determined based on the actual situation and is not limited here. As an example, if the first traffic scenario is L3VPN, the label length can be 4, and the label depth can be 2, then the label length added in the L3VPN traffic scenario is 8; if the first traffic scenario is VXLAN, the label length can be 50, and the label depth can be 1, then the label length added in the VXLAN traffic scenario is 50; if the first traffic scenario is SRv6, the label length can be 16, and the label depth can be 3, then the label length added in the SRv6 traffic scenario is 48.

[0121] In one embodiment, determining the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario includes:

[0122] The length of the tag added to the first data frame in the first traffic scenario is determined by using the data frame length change information corresponding to the first traffic scenario; the first data frame is any data frame among at least one data frame in the first scenario;

[0123] Based on the tag length added to the first data frame in the first traffic scenario and the rate of the output traffic of the test device corresponding to the first traffic scenario obtained from the test device configuration information corresponding to the first traffic scenario, the predicted rate of the output traffic of the device under test is predicted.

[0124] It should be noted that, based on the tag length added to the first data frame in the first traffic scenario and the rate of the output traffic of the test device corresponding to the first traffic scenario obtained from the test device configuration information corresponding to the first traffic scenario, the predicted rate of the output traffic of the device under test can be predicted by using a preset algorithm based on the tag length added to the first data frame in the first traffic scenario and the rate of the output traffic of the test device corresponding to the first traffic scenario obtained from the test device configuration information corresponding to the first traffic scenario.

[0125] For ease of understanding, an example is provided here. The rate of the output traffic of the test device corresponding to the first traffic scenario can be denoted as OfferedRate, the tag length added to the first data frame in the first traffic scenario can be denoted as IncreSize, and the predicted rate of the output traffic of the device under test can be denoted as ExpectedRate. The preset algorithm can refer to the following formulas (2) and (3):

[0126]

[0127]

[0128] In equations (1) and (2), PreambleSize is the preamble length; FrameSize is the frame length; FrameSize is the minimum inter-frame interval; FrameSize is the frame length; IncreSize is the tag length added to the frame; R is the ratio; OfferedRate is the rate of the output traffic of the test device corresponding to the first traffic scenario; ExpectedRate is the predicted rate of the output traffic of the device under test; in practical applications, OfferedRate can also be called the sending rate of the test port; ExpectedRate can also be called the predicted rate of the port of the device under test.

[0129] The traffic rate prediction method provided in this application matches the configuration information with the test device configuration information corresponding to a preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the input traffic rate and output traffic rate of the device under test are inconsistent; in response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario, thereby taking into account the problem of data traffic expansion in the device under test, that is, the existence of a data traffic exceeding the line rate scenario in the device under test, and thus predicting the traffic rate of the port of the device under test, thereby avoiding the occurrence of the traffic rate exceeding the line rate scenario of the port of the device under test.

[0130] The present application will be further described in detail below with reference to application examples.

[0131] Application Example 1

[0132] In this application embodiment, the test equipment is used as the instrument; the device under test is used as the device under test; and a flow rate prediction method is used to predict the port rate of the device under test, thereby calculating the actual port rate of the device under test and avoiding situations where the port of the device under test exceeds its line speed. The main steps are as follows:

[0133] Step 1: Establish a scenario library. Based on the instrument protocol, traffic and other relevant configurations, determine the network topology and traffic model in the test scenario, infer whether there is a super-line-speed scenario, and obtain the length of traffic inflation for each frame.

[0134] Step 2: Based on information such as the instrument's transmission rate, the length of the traffic expansion, and the inter-frame interval, predict the port rate of the device under test.

[0135] Step 3: Provide configuration options. Users can directly configure the expected rate of the device-side port. The meter adjusts the meter's transmission rate by automatically modifying the GapSize to achieve the expected rate of the device-side port configured by the user.

[0136] Step 4: When the expected receiving rate exceeds the line speed, a warning message is issued, prompting the user to modify the instrument test-side configuration, reduce the instrument-side sending rate, and automatically calculate the frameSize, IFG and other configuration values ​​on the test instrument side when the device-side port rate is at the line speed.

[0137] To better understand, examples Figure 3 To understand, Figure 3 The diagram below illustrates an application scenario of the traffic rate prediction method described in this application; Figure 3 In this context, the testing equipment is used as the instrument, and the device under test is used as the device being tested.

[0138] Application Example 2

[0139] In this application example:

[0140] The process of calculating the rate can be referred to the above formula (1). The meaning of the parameters in formula (1) can be found in Table 1, which shows the meaning of the parameters in the rate calculation formula.

[0141] Table 1

[0142] MediaS Medium velocity dPreambl Preamble length SiFrameSi Frame length GapSize Inter-frame interval GapSize Minimum Inter-Frame

[0143] When the inter-frame interval is set to the minimum inter-frame interval, the transmission rate reaches the line speed. However, if the device under test has features such as MPLS, VXLAN, SR, or SRv6, the actual frame length will increase, leading to a situation where the transmission rate exceeds the line speed.

[0144] To address the above issues, a method for predicting the rate on the device under test is proposed, with detailed steps as follows:

[0145] (a) Create a traffic expansion scenario library. Before traffic is sent, compare the meter configuration with the configuration combination in the scenario library to determine whether a traffic expansion scenario will occur.

[0146] The method for establishing a traffic expansion scenario library is as follows:

[0147] ① Analyze the characteristics of various traffic expansion scenarios and find the unique combination of characteristics for a certain traffic expansion scenario.

[0148] ② Based on the unique combination of features corresponding to the scenario, relevant information is read from the instrument configuration, including the type of device under test, the protocol types included in the test scenario, the test topology, etc., to obtain the unique configuration combination corresponding to the scenario.

[0149] Examples of scenarios are shown in Table 2 below. Table 2 is a scenario library for traffic expansion.

[0150] Table 2

[0151]

[0152]

[0153] L3VPN protocol test traffic scalation scenario analysis, such as Figure 4 As shown, Figure 4 This is a schematic diagram of a traffic swell scenario during L3VPN protocol testing in an embodiment of this application. In this scenario, when testing the router's MPLS protocol, an L3VPN binding flow is sent. When the traffic is sent from the CE side to the PE, the DUT adds two layers of tags to the data frame after receiving it, resulting in traffic swell on the DUT port.

[0154] L2VPN protocol test traffic scalation scenario analysis, such as Figure 5 As shown, Figure 5 This is a schematic diagram of a traffic swell scenario during L2VPN protocol testing in an embodiment of this application. In this scenario, when testing the MPLS protocol of a router, an L2VPN binding flow is sent. When the traffic is sent from the CE to the PE side, the DUT receives the data frame and adds L2VPN public network and private network labels, resulting in traffic swell on the DUT port.

[0155] Analysis of Vxlan protocol test traffic expansion scenarios, such as Figure 6 As shown, Figure 6 This is a schematic diagram of a VxLAN protocol test traffic expansion scenario in an embodiment of this application. In this scenario, when testing the VxLAN protocol, the VTEP adds VxLAN protocol information to the data frame after receiving it, causing the VTEP port rate to expand.

[0156] SRv6 protocol test flow escalation scenario analysis, such as Figure 7 As shown, Figure 7 This is a schematic diagram of a traffic expansion scenario for testing the SRv6 protocol in an embodiment of this application. In this scenario, when testing the SRv6 protocol, an SRv6-VPN binding flow is sent. When traffic is sent from the CE to the PE side, the DUT adds an SRv6-VPN tag to the received data frame, resulting in traffic expansion on the DUT port.

[0157] (b) Establish a list of frame length increase values ​​under traffic expansion scenarios, corresponding to the traffic expansion scenario library. The implementation method is to predict the change in frame length on the device under test side under traffic expansion scenarios, compare it with the frame length of the test instrument's transmission port, and calculate the increase in frame length.

[0158] Different traffic expansion scenarios will result in different numbers of bytes added to the data frame. The following is a detailed analysis of each traffic expansion scenario:

[0159] When the device under test is an MPLS device, L2VPN and L3VPN add new protocol tags between layers 2 and 3 of the frame. The length of a first-level MPLS tag is 4 bytes. The tag depth is generally two or three levels.

[0160] Devices implementing the VXLAN protocol will add an 8-byte VXLAN header, an 8-byte UDP header, a 20-byte IP header, and a 13- or 18-byte Ethernet header to the Ethernet frame header. When the Ethernet header requires a VLAN tag, it will require 18 bytes.

[0161] Devices implementing the SR protocol add a tag stack to the frame, with each tag being 4 bytes long, and the number of bytes added is determined based on the depth of the tag stack.

[0162] Devices implementing the SRv6 protocol are similar to those implementing the SR protocol, except that the tag length is 16 bytes, and the depth is determined by the specific device.

[0163] G-SRv6 is based on SRv6, but by compressing the 128-bit SID to a length of 16 or 32 bits, the length of the added frame can be greatly reduced. The added first-level tag is also 128 bits, which contains multiple compressed G-SIDs, so the required tag depth is reduced.

[0164] Table 3 shows the additional tag length and depth of data frames for different traffic expansion scenarios.

[0165] Table 3

[0166] L3VPN 4 1-6 L2VPN 4 1-6 vxlan 50 / 54 1 SR 4 2-6 SRv6 16 2-6 G-SRv6 16 2-3 … … …

[0167] (c) In the scenario of traffic expansion, the test instrument provides the expected rate configuration function on the device under test. The user can directly configure the expected rate ExpectedRate on the device under test. The instrument automatically calculates the sending rate OfferedRate of the instrument port. The calculation method is as described in the above formulas (2) and (3).

[0168] Where IncreSize = the length of the tag added to the frame.

[0169] The ExpectedRate configuration function is implemented as follows: the meter adjusts the meter's sending rate OfferedRate by automatically modifying GapSize based on the frame size and expected rate configured by the user, so that the expected rate ExpectedRate can be achieved in traffic expansion scenarios.

[0170] For ease of understanding, an example is shown here. Figure 8 , Figure 8 This is a schematic diagram illustrating the expected device-side transmission format and instrument-side transmission format in embodiments of this application; Figure 8 In this context, IFG GAP = IncreSize; SFD represents the start bit of the data frame; and EFD represents the end bit of the data frame.

[0171] (d) If the user does not select to configure the expected port rate on the device side, but selects to configure the instrument port transmission rate, the instrument will automatically calculate the expected port rate of the device under test and send a prompt message to the user. When the expected port rate of the device under test exceeds the line speed, an alarm message will be issued to prompt the user to modify the configuration information. The user can reduce the port rate of the device under test by reducing the frame length, increasing the IFG, etc., or set the expected port rate of the device under test to the line speed of the device under test with one click.

[0172] In this embodiment, the instrument provides the user with the expected port rate information of the device under test based on the port transmission rate; a traffic expansion scenario library is established and mapped to the instrument configuration. Through the instrument configuration and the traffic scenario library, it is possible to determine whether there is a traffic expansion scenario; and through various means, scenarios that cause test abnormalities due to the device under test exceeding the line speed are prevented.

[0173] To implement the method of the embodiments of this application, the embodiments of this application also provide a flow rate prediction device, which is installed on the flow rate prediction system, such as... Figure 9 As shown, Figure 9 This is a schematic diagram of the flow rate prediction device according to an embodiment of this application; the device includes:

[0174] Acquisition unit 901 is used to acquire configuration information of the test equipment;

[0175] The matching unit 902 is used to match the configuration information with the test device configuration information corresponding to the preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the rate of input traffic and the rate of output traffic of the device under test are inconsistent.

[0176] The determining unit 903 is configured to, in response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, determine the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario.

[0177] In one embodiment, the determining unit 903 is further configured to determine the data frame length change information corresponding to the preset traffic scenario based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario; and to determine the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario.

[0178] In one embodiment, the matching unit 902 is further configured to determine whether the predicted rate of the output traffic of the device under test is greater than a preset threshold; if the predicted rate of the output traffic of the device under test is greater than the preset threshold, the rate of the output traffic of the device under test is configured to the preset threshold.

[0179] In one embodiment, the determining unit 903 is further configured to determine the rate at which the test device sends traffic to the device under test based on the preset threshold.

[0180] In one embodiment, the preset traffic scenario includes at least one traffic scenario; the matching unit 902 is further configured to match the configuration information with the test device configuration information corresponding to each traffic scenario in the at least one traffic scenario.

[0181] In one embodiment, the determining unit 903 is further configured to: if, in the at least one traffic scenario, there exists a test device configuration information corresponding to a traffic scenario that matches the configuration information, then determine that the device under test tested by the test device has a scenario where the input traffic rate and the output traffic rate are inconsistent; if, in the at least one traffic scenario, there does not exist a test device configuration information corresponding to a traffic scenario that matches the configuration information, then determine that the device under test tested by the test device does not have a scenario where the input traffic rate and the output traffic rate are inconsistent.

[0182] In one embodiment, after responding to the configuration information matching the test device configuration information corresponding to the preset traffic scenario, the matching unit 902 is further configured to determine whether the device under test being tested by the test device has a preset output traffic rate set; if the device under test being tested by the test device has not a preset output traffic rate set, the predicted output traffic rate of the device under test is determined based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario.

[0183] In one embodiment, the matching unit 902 is further configured to determine the rate at which the test device sends traffic to the device under test according to the preset output traffic rate when the device under test being tested by the test device has a preset output traffic rate.

[0184] In one embodiment, the preset traffic scenario includes at least one traffic scenario; the matching unit 902 is further configured to respond to when the configuration information matches the test device configuration information corresponding to the first traffic scenario in the at least one traffic scenario.

[0185] In one embodiment, the determining unit 903 is further configured to obtain the rate of the output traffic of the test device corresponding to the first traffic scenario based on the test device configuration information corresponding to the first traffic scenario; determine the tag length of at least one data frame added in the first traffic scenario based on the rate of the output traffic of the test device corresponding to the first traffic scenario and the traffic feature information corresponding to the first traffic scenario; and determine the data frame length change information corresponding to the first traffic scenario based on the tag length of at least one data frame added in the first traffic scenario.

[0186] In one embodiment, the determining unit 903 is further configured to determine the tag length added to the first data frame in the first traffic scenario using the data frame length change information corresponding to the first traffic scenario; the first data frame is any data frame among at least one data frame in the first scenario; and predict the predicted rate of the output traffic of the device under test based on the tag length added to the first data frame in the first traffic scenario and the rate of the output traffic of the test device corresponding to the first traffic scenario obtained from the test device configuration information corresponding to the first traffic scenario.

[0187] It should be noted that the flow rate prediction device provided in the above embodiments is only illustrated by the division of the above program modules during testing. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the flow rate prediction device and the flow rate prediction method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0188] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide a traffic rate prediction system, such as... Figure 10 As shown, Figure 10This is a schematic diagram of the traffic rate prediction system according to an embodiment of this application; the traffic rate prediction system 1000 includes: a processor 1001 and a memory 1003. Optionally, the electronic device 1000 may also include a communication interface 1002.

[0189] It is understood that memory 1003 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 803 described in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0190] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 1001. The processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 1001 or by instructions in the form of software. The processor 1001 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 1001 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the memory 1003. The processor 1001 reads the information in the memory 1003 and completes the steps of the aforementioned method in conjunction with its hardware.

[0191] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a memory 1003 storing a computer program, which can be executed by the processor 1002 of the flow rate prediction system 1000 to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0192] It should be noted that "first", "second", "third", "fourth", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0193] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0194] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method for predicting the rate of flow, characterized in that, include: Obtain the configuration information of the test equipment; The configuration information is matched with the test device configuration information corresponding to the preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the input traffic rate and the output traffic rate of the device under test are inconsistent, and the preset traffic scenario is a traffic expansion scenario. When the configuration information matches the test device configuration information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario. The step of determining the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario includes: Based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario, the data frame length change information corresponding to the preset traffic scenario is determined. Based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined. Determine whether the predicted rate of the output flow of the device under test is greater than a preset threshold; If the predicted rate of the output traffic of the device under test is greater than the preset threshold, the rate of the output traffic of the device under test is configured to the preset threshold.

2. The method according to claim 1, characterized in that, The method further includes: The rate at which the test device sends traffic to the device under test is determined based on the preset threshold.

3. The method according to claim 1, characterized in that, The preset traffic scenario includes at least one traffic scenario; the step of matching the configuration information with the test device configuration information corresponding to the preset traffic scenario includes: The configuration information is matched with the test device configuration information corresponding to each of the at least one traffic scenario.

4. The method according to claim 3, characterized in that, The method further includes: If, in one of the at least one traffic scenario, the configuration information of the test device matches the configuration information, then it is determined that the test device being tested has a scenario where the rate of input traffic and the rate of output traffic are inconsistent. If in none of the at least one traffic scenario the test device configuration information matches the configuration information, then it is determined that the device under test tested by the test device does not have a scenario where the input traffic rate and the output traffic rate are inconsistent.

5. The method according to claim 4, characterized in that, After the response occurs when the configuration information matches the test device configuration information corresponding to the preset traffic scenario; the method further includes: Determine whether the device under test being tested by the test equipment has a preset output flow rate; If the device under test is not set to a preset output flow rate, the predicted output flow rate of the device under test is determined based on the test device configuration information corresponding to the preset flow scenario and the flow characteristic information corresponding to the preset flow scenario.

6. The method according to claim 5, characterized in that, The method further includes: If the device under test being tested by the test equipment has a preset output flow rate, the rate at which the test equipment sends flow to the device under test is determined according to the preset output flow rate.

7. The method according to claim 1, characterized in that, The preset traffic scenario includes at least one traffic scenario; the response to the configuration information matching the test device configuration information corresponding to the preset traffic scenario includes: When the configuration information matches the test device configuration information corresponding to the first traffic scenario in the at least one traffic scenario.

8. The method according to claim 7, characterized in that, The step of determining the data frame length change information corresponding to the preset traffic scenario based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario includes: The rate of the output traffic of the test device corresponding to the first traffic scenario is obtained based on the test device configuration information corresponding to the first traffic scenario. Based on the rate of the output traffic of the test device corresponding to the first traffic scenario and the traffic characteristic information corresponding to the first traffic scenario, the tag length added to at least one data frame in the first traffic scenario is determined. The data frame length variation information corresponding to the first traffic scenario is determined based on the tag length added to at least one data frame in the first traffic scenario.

9. The method according to claim 8, characterized in that, The step of determining the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario includes: The length of the tag added to the first data frame in the first traffic scenario is determined by using the data frame length change information corresponding to the first traffic scenario; the first data frame is any data frame among at least one data frame in the first traffic scenario. Based on the tag length added to the first data frame in the first traffic scenario and the rate of the output traffic of the test device corresponding to the first traffic scenario obtained from the test device configuration information corresponding to the first traffic scenario, the predicted rate of the output traffic of the device under test is predicted.

10. A device for predicting the rate of flow, characterized in that, include: The acquisition unit is used to acquire configuration information of the test equipment; The matching unit is used to match the configuration information with the test device configuration information corresponding to the preset traffic scenario, wherein the preset traffic scenario is a known scenario in which the rate of input traffic and the rate of output traffic of the device under test are inconsistent, and the preset traffic scenario is a traffic expansion scenario. The determining unit is configured to, in response to a match between the configuration information and the test device configuration information corresponding to the preset traffic scenario, determine the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario; The step of determining the predicted rate of the output traffic of the device under test based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario includes: Based on the test device configuration information corresponding to the preset traffic scenario and the traffic characteristic information corresponding to the preset traffic scenario, the data frame length change information corresponding to the preset traffic scenario is determined. Based on the test device configuration information corresponding to the preset traffic scenario and the data frame length change information corresponding to the preset traffic scenario, the predicted rate of the output traffic of the device under test is determined. The matching unit is also used to determine whether the predicted rate of the output flow of the device under test is greater than a preset threshold. If the predicted rate of the output traffic of the device under test is greater than the preset threshold, the rate of the output traffic of the device under test is configured to the preset threshold.

11. A system for predicting the rate of flow, characterized in that, include: The processor and the memory used to store computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 9.

12. A computer storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

Images