Traffic execution management method, device, electronic device and storage medium
By configuring traffic templates to automatically issue and parse, the high threshold problem of manually inputting command lines in SRIO chip test is solved, low threshold traffic execution management and performance testing is realized, and stability debugging and function are supported in high-density networking environments. Performance test.
Patent Information
- Application Number
- CN202410796677.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-06-20
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2044-06-20
AI Technical Summary
The existing SRIO chip testing method requires users to manually enter the command line, which has a high threshold and poor flexibility, making it difficult to reduce the difficulty of use.
By configuring the device ID in the configurable traffic template, distribute the configuration traffic template to the corresponding endpoint device, analyze and configure the traffic, count and send the traffic execution results, and support user interface display and management.
It realizes low-threshold operation of SRIO traffic execution management, simplifies the testing process, and supports test verification and performance testing in high-density networking environments.
Smart Images

Figure CN118368196B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to the field of chip testing technology, and in particular to a flow execution management method, device, electronic device, and storage medium. Background Art
[0002] The SRIO (Serial RapidIO) chip is a high-performance, low-latency, high-bandwidth serial communication chip based on RapidIO interconnect technology. It is widely used in key areas such as data centers, communication equipment, wireless base stations, radars, and avionics.
[0003] Most existing tests for SRIO chips require users to convert the test plan into command lines, then manually enter the command lines to send and receive packets, and then obtain the traffic execution status of the SRIO chip to evaluate its performance. Due to the need to manually enter commands, the existing traffic generation methods have a high threshold for use and poor flexibility.
[0004] Therefore, how to provide an SRIO traffic execution management method with a low usage threshold is a technical problem that technical personnel in this field urgently need to solve. Summary of the invention
[0005] The embodiments of the present disclosure provide a flow execution management method, an apparatus, an electronic device, and a storage medium.
[0006] In a first aspect, an embodiment of the present disclosure provides a traffic execution management method, which is applied to an interactive device, and the method includes:
[0007] According to the device ID in the configuration flow template, the configuration flow template is issued to the corresponding endpoint device, the configuration flow template includes a data flow execution management strategy, the data flow execution management strategy includes the device type and device ID of the endpoint device to which the configuration flow template needs to be issued, and the endpoint device has an embedded SRIO chip;
[0008] Receive the traffic execution result, the traffic execution result is obtained by the endpoint device parsing the parameters of the received configuration traffic template, and then issuing the traffic configuration according to the parameters of the configuration traffic template, and then obtaining and sending the statistics of the traffic sent and received by the current device.
[0009] In some possible implementations, the method further includes:
[0010] The flow execution result is sent to a user interface so that the user interface displays the flow execution result.
[0011] In some possible implementations, the sending the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template includes:
[0012] In response to receiving the start instruction, issuing the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template; and
[0013] After sending the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template, the method further includes:
[0014] In response to receiving a stop instruction and the execution status of the endpoint device being in execution, a stop data packet is sent to the endpoint device so that the endpoint device stops generating the traffic execution result.
[0015] In some possible implementations, sending the flow execution result to a user interface so that the user interface displays the flow execution result includes:
[0016] In response to receiving the refresh instruction, the current traffic execution result is sent to the user interface so that the user interface displays the current traffic execution result.
[0017] In some possible implementations, the method further includes:
[0018] In response to receiving the query instruction, obtaining endpoint device information in the SRIO network;
[0019] The endpoint device information in the SRIO network is sent to a user interface so that the user interface displays the endpoint device information in the SRIO network.
[0020] In some possible implementations, obtaining endpoint device information in the SRIO network includes:
[0021] Send endpoint device information query instructions to the network management system;
[0022] Receive endpoint device information in the SRIO network sent by the network management system.
[0023] In some possible implementations, the creation of the configuration traffic template is based on the following template creation operations:
[0024] In response to receiving a new creation instruction of a traffic configuration template, acquiring template information;
[0025] Generate a template ID based on the template information;
[0026] Saving the template information and the template ID;
[0027] The template ID is sent to a user interface so that the user interface displays the template ID.
[0028] In some possible implementations, the configured traffic template includes configured traffic information, and the configuration of the traffic information is created according to the following traffic information creation operation:
[0029] In response to receiving a flow information creation instruction, obtaining configuration flow information;
[0030] Verifying the legitimacy of the configuration flow information;
[0031] In response to a result of the verification being a failure, sending a traffic configuration creation failure reminder to a user interface so that the user interface displays the traffic configuration creation failure reminder;
[0032] In response to a successful result of the verification, generating a flow ID according to the configured flow information;
[0033] Saving the configuration flow information and the flow ID;
[0034] sending the stream ID to the user interface so that the user interface displays the stream ID;
[0035] The configuration flow information is encapsulated into an Ethernet message and saved.
[0036] In some possible implementations, the deletion of the configured flow information is based on the following flow information deletion operation:
[0037] In response to receiving the configuration flow information deletion instruction, obtaining the flow ID to be deleted;
[0038] Determine whether there is a configuration traffic template in the execution state among all configuration traffic templates;
[0039] If yes, sending a flow deletion failure reminder to the user interface so that the user interface displays the flow deletion failure reminder;
[0040] If not, deleting the storage information of the flow corresponding to the flow ID to be deleted;
[0041] Sending a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
[0042] In some possible implementations, the deletion of the configured traffic template is based on the following template deletion operation:
[0043] In response to receiving the configuration traffic template deletion instruction, obtaining the template ID to be deleted;
[0044] Determine whether there is a configuration traffic template in the execution state among all configuration traffic templates;
[0045] If yes, sending a template deletion failure reminder to the user interface so that the user interface displays the template deletion failure reminder;
[0046] If not, delete the template and storage information of all flow IDs corresponding to the template ID;
[0047] Sending a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
[0048] In some possible implementations, the method further includes:
[0049] In response to receiving the clear instruction, a data clear message is sent to the endpoint device, so that the endpoint device clears the global statistical data after receiving the data clear message.
[0050] In a second aspect, an embodiment of the present disclosure provides a traffic execution management device, which is applied to an interactive device, and includes:
[0051] A template delivery module, used to deliver the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template, wherein the configured traffic template includes a data traffic execution management strategy, and the data traffic execution management strategy includes a device type and a device ID of the endpoint device to which the configured traffic template needs to be delivered, and the endpoint device has an embedded SRIO chip;
[0052] The result receiving module is used to receive the flow execution result. The flow execution result is obtained by the endpoint device parsing the parameters of the received configuration flow template, and then issuing the flow configuration according to the parameters of the configuration flow template, and then obtaining and sending the statistics of the flow sent and received by the current device.
[0053] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation manner in the first aspect.
[0054] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by one or more processors, implements the method described in any implementation manner in the first aspect.
[0055] In order to lower the threshold of SRIO traffic execution management, the traffic execution management method, device, electronic device and storage medium provided by the embodiments of the present disclosure first send the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template, the configured traffic template includes a data traffic execution management policy, the data traffic execution management policy includes the device type and device ID of the endpoint device to which the configured traffic template needs to be sent, and the endpoint device has an embedded SRIO chip; then, receive the traffic execution result, the traffic execution result is obtained by the endpoint device parsing the parameters of the received configured traffic template, and then according to the parameters of the configured traffic template, the traffic configuration is sent, and then the traffic sent and received by the current device is statistically obtained and sent. In this way, by configuring the traffic template, the traffic configuration policy of the test plan is sent with one click, which effectively lowers the use threshold of traffic execution management. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] Other features, objects and advantages of the present disclosure will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings. The drawings are only for the purpose of illustrating specific embodiments and are not to be considered as limiting the present disclosure. In the drawings:
[0057] Figure 1 is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;
[0058] Figure 2A is a flow chart of an embodiment of a flow execution management method according to the present disclosure;
[0059] Figure 2B is a flow chart of a template creation operation according to an embodiment of the traffic execution management method disclosed herein;
[0060] Figure 2C is a flow chart of a new operation of flow information according to an embodiment of the flow execution management method disclosed in the present invention;
[0061] Figure 2D is a flow chart of flow information deletion operation according to an embodiment of the flow execution management method disclosed herein;
[0062] Figure 2E is a flow chart of template deletion operation according to an embodiment of the traffic execution management method disclosed herein;
[0063] Figure 3 is a flow chart of another embodiment of the flow execution management method according to the present disclosure;
[0064] Figure 4 is a structural diagram of an embodiment of a flow execution management device according to the present disclosure;
[0065] Figure 5 It is a structural diagram of a computer system of an electronic device suitable for implementing an embodiment of the present disclosure. DETAILED DESCRIPTION
[0066] The present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the relevant invention are shown in the accompanying drawings.
[0067] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0068] SRIO (Serial RapidIO) is an advanced high-speed interconnect technology developed for embedded systems. It is based on high reliability, high performance and packet switching and is widely used in key areas such as data centers, communication equipment, wireless base stations, radars, and avionics. The SRIO protocol consists of three layers: the physical layer, the transport layer, and the logical layer. Each layer is responsible for the electrical characteristics and link control, packet switching and routing addressing mechanism, and the definition of the overall protocol and packet format.
[0069] The construction of SRIO network depends on endpoint devices and switching devices, supporting two connection modes: endpoint device to endpoint device and endpoint device to switching device to endpoint device. Endpoint devices are responsible for sending and receiving data, while switching devices focus on data transmission between ports and do not involve data packet parsing. The network is characterized by low latency, high bandwidth (supporting data transmission rates of 1.25 Gbps to 25 Gbps) and excellent reliability.
[0070] In addition, the SRIO network has the advantages of a small number of pins, support for direct memory access (DMA) transmission, scalable complex topology and multi-point transmission. The optional transmission rates include 1.25 Gbps, 2.5 Gbps, 3.125 Gbps and 5 Gbps, which can meet the needs of different applications. The network is mainly used to efficiently transmit data and control information between microprocessors, DSPs, communication and network processors, system memory and peripheral devices. Through switching devices, the SRIO network can build an intercommunication data network connecting different platforms such as CPUs, DSPs and FPGAs to achieve distributed processing or sharing of data.
[0071] In order to fully test the business processing capabilities of SRIO chips, a comprehensive SRIO network ecosystem needs to be built, which needs to be compatible with a variety of networking environments and device types to ensure accurate simulation of actual application scenarios. At the same time, devices embedded with the chips to be verified can be deployed at the endpoints of the network, so that users can independently set traffic execution management policies and view traffic transmission and reception, thereby verifying the performance of SRIO chips.
[0072] Figure 1 An exemplary system architecture 100 is shown to which embodiments of the traffic execution management method, apparatus, electronic device, and storage medium of the present disclosure can be applied.
[0073] like Figure 1 As shown, the system architecture 100 may include an interactive device 101, an endpoint device 102, and a network 104. The network 104 is used to provide a medium for a communication link between the interactive device 101 and the endpoint device 102. When the number of endpoint devices 102 is too large, multiple endpoint devices 102 may be connected to a switching device to form an SRIO network, and then the switching device interacts with the network 104. Optionally, a network management system 103 and a network 105 may also be included. The network 105 is used to provide a medium for a communication link between the interactive device 101 and the network management system 103.
[0074] The media providing the communication link may include various connection types, such as wired including Ethernet, wireless communication links including PCIe (Peripheral Component Interconnect Express) and I2C (Inter-Integrated Circuit), or fiber optic cables, etc.
[0075] The user can interact with the interactive device 101 through the user interface, and the interactive device 101 interacts with the endpoint device 102 and the network management system 103 through the networks 104 and 105 respectively to receive or send messages, etc. Various communication client applications can be installed on the interactive device 101, such as traffic execution management applications, voice recognition applications, short video social applications, audio and video conferencing applications, video live broadcast applications, document editing applications, input method applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.
[0076] The interactive device 101 can be hardware or software. Preferably, it can be hardware that includes Windows 10 and above operating systems and can run software. When the interactive device 101 is hardware, it can be various electronic devices with a display screen, including but not limited to laptops and desktop computers. When the interactive device 101 is software, it can be installed in the interactive devices listed above. It can be implemented as multiple software or software modules (for example, used to provide traffic execution management services), or it can be implemented as a single software or software module. As an example, the software can be a copy-and-use software that can only be run one at a time, and no specific limitation is made here.
[0077] In some cases, the traffic execution management method provided by the present disclosure may be executed by the interactive device 101 , and accordingly, the traffic execution management apparatus may be disposed in the interactive device 101 .
[0078] The endpoint device 102 can be a device with a SRIO chip to be verified, such as a board with a T2080 or PRB0400 chip. It should be noted that the T2080 is one of the mid-to-high-end chips in the PowerPC T series, with a built-in E6500 high-performance CPU core and a computing power of 4 cores and 8 threads. The T2080 also has 8 groups of 10Gb and 8 groups of 8Gb Serdes Lanes. Serdes can be flexibly configured as SRIO, PCIE, XFI, SGMII and other interfaces to meet diverse communication needs. PRB0400 is a bridge chip that can realize conversion between RapidIO Gen2 and PCIeGen2 protocols. PRB0400 not only provides RapidIO to PCIe protocol conversion and bridging functions, but also provides solutions for mainstream CPUs to access RapidIO networks, demonstrating high application value.
[0079] The network management system 103 can be hardware or software. Preferably, it can be hardware that includes Windows 10 and above operating systems and can run software. When the network management system 103 is hardware, it can be various electronic devices with display screens, including but not limited to laptops and desktop computers, etc. When the network management system 103 is software, it can be installed in the interactive devices listed above. It can be implemented as multiple software or software modules (for example, for providing management services for endpoint device information in SRIO networks), or it can be implemented as a single software or software module. As an example, the software can be a copy-and-use software that can only be run one at a time, and no specific limitation is made here.
[0080] It should be understood that Figure 1The number of interactive devices, networks, endpoint devices, and network management systems in the embodiment is only illustrative. Any number of interactive devices, networks, endpoint devices, and network management systems may be provided according to implementation requirements.
[0081] Continue to refer Figure 2A , which shows a process 200 of an embodiment of a flow execution management method according to the present disclosure, the flow execution management method comprises the following steps:
[0082] Step 201: Send the configuration traffic template to the corresponding endpoint device according to the device ID in the configuration traffic template.
[0083] A template can be considered as a preset task mode, which comprehensively tests the processing capabilities of endpoint devices by simulating actual usage scenarios. The execution results of the template usually include key indicators such as processing time and number of sent and received packets. These data can help users gain a deeper understanding of the performance of endpoint devices in different task scenarios.
[0084] The configuration traffic template is a custom traffic template that can be pre-configured by the user. The user only needs to enter the parameters to be set to automatically generate the configuration traffic template, which greatly reduces the user's usage threshold. At the same time, through the pre-set configuration traffic template, the SRIO environment can be deployed with one-click software, which is easy to operate.
[0085] The configuration traffic template includes data traffic execution management policies, such as device type, device ID, traffic type, traffic distribution policy, traffic priority, etc. Among them, the device type and device ID reflect the device type and device ID of the endpoint device to which the configuration traffic template needs to be delivered.
[0086] Therefore, the interactive device can send the configured traffic template to the corresponding endpoint device according to the device type and device ID in the configured traffic template, so that the endpoint device generates traffic according to the configured traffic template.
[0087] Step 202, receiving the flow execution result.
[0088] The traffic execution result is generated and sent by the endpoint device according to the configured traffic template. Optionally, the endpoint device may be a device embedded with an SRIO chip, or may be other devices embedded with a chip having SRIO protocol functions, which is not limited here.
[0089] After receiving the configured traffic template, the endpoint device will parse the parameters of the configured traffic template, and then issue the traffic configuration according to the parameters of the configured traffic template, and then count the traffic sent and received by the current device, and finally send the traffic statistics results (i.e., traffic execution results) to the interactive device.
[0090] The traffic execution results not only cover the statistics of sent and received packets, but also include the execution results of the template. The statistics of sent and received packets can intuitively reflect the efficiency and stability of the SRIO chip during data transmission. For example, by comparing the number of sent and received packets, it can be preliminarily determined whether there is packet loss during data transmission. At the same time, the size of the packet, the transmission speed, etc. are also important indicators for evaluating chip performance. The execution results of the template more reflect the performance of the SRIO chip when processing specific tasks. The interactive device receives these traffic execution results and can use them as a basis for evaluating the performance of the SRIO chip.
[0091] As a possible implementation, after step 202, the method further includes: step 203, sending the flow execution result to the user interface so that the user interface displays the flow execution result.
[0092] The user interface can be a WebUI (Web User Interface) interface on or connected to an interactive device, or a desktop application interface, or other interfaces with interactive functions, which are not limited here. The design of the user interface can fully consider user experience and ease of use. For example, the statistics of sent and received packets and the template execution results can be intuitively displayed in the form of charts, curves, etc. These traffic execution results are sent to the user interface so that the user interface can display the traffic execution results.
[0093] As a possible implementation, each configured traffic template may include multiple flows, and the traffic execution result may include traffic data corresponding to multiple flows, which has a large amount of data and requires large storage resources. Considering that both the switching device and the endpoint device are devices with SRIO chips, most of their memories use volatile memories. Although they can be used to temporarily store running programs and currently used data, when the power is disconnected, the data may be lost because it does not have the ability to store data for a long time.
[0094] Therefore, the interactive device can use the database to store the configuration flow template, flow execution results and other contents. The database runs in non-volatile memory such as hard disk drive (HDD), solid state drive (SSD), flash memory and erasable and programmable memory (EEPROM), and can still keep the data after power failure. These storage devices are designed for long-term data storage, and can maintain the integrity of the data even in the absence of power. At the same time, it is convenient for users or applications to efficiently access and process flow execution results with large amounts of data.
[0095] As a possible implementation method, the user can control the above steps through the user interface, improve the degree of freedom of adjusting the networking environment, and adjust the traffic execution management strategy in real time. At least the following four control situations are included:
[0096] First, users can start and stop the delivery of the corresponding configured traffic template through the user interface, as follows:
[0097] On the one hand, the above step 201 may include: step 2011, in response to receiving the start instruction, sending the configuration traffic template to the corresponding endpoint device according to the device ID in the configuration traffic template.
[0098] The above step 201 is triggered by the corresponding start instruction. The issuance of the start instruction can be controlled by the user through the user interface. For example, a "start" button is set on the user interface for each configuration traffic template. The user first selects the configuration traffic template to be tested, and then clicks the "start" button corresponding to the selected traffic configuration template to trigger the issuance of the start instruction. In response to receiving the start instruction, the interactive device triggers the execution of the above step 201, that is, the user can start the test execution of the configuration traffic template through the user interface. In this way, an interconnected environment that is closer to the user's usage scenario is provided, further improving the user experience and enhancing the stickiness of users using the self-developed SRIO chip.
[0099] In addition, the startup instructions can also be issued through a pre-set automated program, thus reducing user involvement and automating chip testing.
[0100] On the other hand, after the above step 201 starts to execute, the traffic execution management method provided by the above embodiment further includes: step 204, in response to receiving a stop instruction and the execution status of the endpoint device is executing, sending a stop data packet to the endpoint device.
[0101] The interactive device can receive a stop command at any time, but since the endpoint device cannot be controlled to stop after execution is completed, the interactive device will send a data packet to the endpoint device to control the endpoint device to stop executing the traffic template configuration when the endpoint device is running.
[0102] The stop command can be issued by the user through the user interface control. For example, a "Stop" button is set on the user interface for each configuration traffic template. The user first selects the configuration traffic template that he wants to stop testing, and then clicks the "Stop" button corresponding to the selected traffic configuration template to trigger the issuance of the stop command. In response to receiving the stop command, the interactive device sends a stop data packet to the endpoint device, so that the endpoint device stops executing the configuration traffic template after receiving the stop data packet, that is, the user can stop the execution of the configuration traffic template test through the user interface. In this way, an interconnected environment that is closer to the user's usage scenarios is provided, the user experience is continuously improved, and the user's dependence on the self-developed SRIO chip is enhanced to meet the actual needs of the user.
[0103] In addition, the stop instruction can also be automatically issued when the preset stop condition is met, thus reducing user participation and automating chip testing.
[0104] It should be noted that once the endpoint device completes traffic generation, it will automatically report it to the interactive device.
[0105] Second, the user can control the display of the traffic execution results through the user interface. Specifically, the above step 203 may include: step 2031, in response to receiving a refresh instruction, sending the current traffic execution result to the user interface so that the user interface displays the current traffic execution result.
[0106] The above step 203 is triggered by the corresponding refresh instruction. The issuance of the refresh instruction can be controlled by the user through the user interface. For example, a "refresh" button is set on the user interface. The user clicks and selects the "refresh" button to trigger the issuance of the refresh instruction. In response to receiving the refresh instruction, the interactive device executes the above step 203.
[0107] Since endpoint devices may periodically send traffic execution results, interactive devices can only save traffic execution results sent by endpoint devices. Therefore, users can refresh the user interface to obtain the most recently updated and saved traffic execution results of the interactive device. There may be a certain delay between this result and the traffic execution result generated in real time by the endpoint device.
[0108] In addition, the refresh instruction can also be issued through a preset automation program, for example, a refresh instruction is issued once every preset period. In this way, even if the user does not actively trigger the refresh instruction, the method can automatically execute step 203 to meet the test requirements.
[0109] Third, the user can query all device information in the current SRIO network through the user interface. Specifically, the above method also includes the following steps 205 to 206:
[0110] Step 205: in response to receiving the query instruction, obtaining endpoint device information in the SRIO network.
[0111] The sending of the query instruction can be controlled by the user through the user interface. For example, a "query" button is set on the user interface. The user clicks and selects the "query" button to trigger the sending of the query instruction. In response to receiving the query instruction, the interactive device obtains the device information in the SRIO network.
[0112] In addition, query instructions can also be issued through a pre-set automated program, thus reducing user involvement and automating chip testing.
[0113] The endpoint device information includes the device type, device ID, capability, online status, etc. of the endpoint device. All the device information in the SRIO network is stored in the database. When obtaining the endpoint device information in the SRIO network, the endpoint device information in the SRIO network can be queried in the database.
[0114] If the database does not have the device information in the SRIO network, the device information is obtained from the network management system. After the device information in the SRIO network is obtained from the network management system, the query result is stored in the database for subsequent query use.
[0115] It should be noted that the network management system can obtain the current online status of the SRIO endpoint device and send it to the interactive device. Secondly, when the device information of the SRIO endpoint device changes, the network management system will actively push a message to the interactive device. In response to receiving the push message, the interactive device updates the database based on the push message. Furthermore, the network management system can poll the status of endpoint devices in the SRIO network. If an endpoint device in the SRIO network is offline or in an abnormal state, the network management system can output a disconnection reminder so that the administrator can physically restore the endpoint device in the SRIO network.
[0116] Step 206: Send the endpoint device information in the SRIO network to the user interface so that the user interface displays the endpoint device information in the SRIO network.
[0117] In this way, through the above steps 205 to 206, the user can obtain the device information in the SRIO network in real time, which is convenient for the user to set the configuration flow template and is conducive to improving the test efficiency.
[0118] Fourth, the user can set the configuration flow template through the user interface to customize the SRIO flow service. Before executing the above flow execution management method, operations such as creating and deleting the configuration flow template and the configuration flow information therein can be completed first.
[0119] Specifically, the creation of a traffic configuration template may include the following: Figure 2B The template creation operations from step A1 to step A3 shown are:
[0120] Step A1: In response to receiving a new creation instruction of a traffic configuration template, template information is obtained.
[0121] When a user wants to create a new template, the interactive device will first receive the instruction to create a new template. This instruction can come from the user's direct operation, such as clicking the Create a New Traffic Template button in the user interface. After receiving the instruction, the interactive device will enter the standby state, pop up the New Traffic Template Information page, and prepare to receive the template information entered by the user.
[0122] The template information includes the name and description of the template. The template name is a short identifier of the template, which helps users to quickly identify and manage the template; while the template description provides information about the purpose and characteristics of the template. Optionally, the template description information can adopt a combination strategy of maintenance write-maintenance read multicast serial interleaved traffic packet (Nwrite-NwriteR-Nread-Doorbell-Message). Taking the flow information as the unit, obtain each parameter that needs to be set entered on the user interface, and set the group id (parallel execution when the group id is the same, serial execution in ascending order when the group id is different), source device id, destination device id, number of repeated executions, loop interval, etc.
[0123] Step A2: Generate a template ID based on the template information.
[0124] The interactive device will generate a unique template ID based on the template information. This ID is the unique identifier of the template, which helps the interactive device to quickly identify and manage the template in subsequent operations.
[0125] Step A3: Save the template information and template ID.
[0126] The interactive device saves the template information and template ID to the database to ensure the security and integrity of the user information. For example, the template information is stored in the StreamModel table of the database.
[0127] Step A4: Send the template ID to the user interface so that the user interface displays the template ID.
[0128] After the template information entered by the user is saved and the template ID is generated, it is sent to the user interface for the user to view and use. In this way, the user can start, stop, and perform other operations on the template according to the template ID. At this point, the traffic configuration template is successfully created.
[0129] Optionally, the user interface may correspond to a status display area for each configured traffic template. After a new traffic configuration template is created, the interactive device sends the status of the configured traffic template as "not started" to the user interface, and then displays the status of the configured traffic template as "not started" in the status display area of the user interface.
[0130] So far, steps A1 to A4 have realized the creation of a new configuration traffic template.
[0131] After creating a new configuration traffic template, users can create or modify the configuration traffic information in the configuration traffic template through the user interface. Figure 2C The flow information creation operation of steps B1 to B7 shown is implemented as follows:
[0132] Step B1, in response to receiving a flow information creation instruction, obtaining configuration flow information.
[0133] When a user clicks on any configured traffic template in the user interface, the issuance of a new traffic information instruction for the configured traffic template can be triggered. When the interactive device receives the new traffic information instruction for the configured traffic template, a new traffic information page will pop up immediately, waiting to receive the configured traffic information entered by the user in the user interface. The configured traffic information may include group id, source device id, destination device id, number of repetitions, loop interval, etc.
[0134] Step B2: Verify the legality of the configuration flow information.
[0135] When creating or modifying configuration flow information, the interactive device will perform a series of legitimacy checks. The purpose of this step is to ensure the correctness and applicability of the configuration flow information to prevent the failure of flow generation due to configuration errors. The legitimacy check can include determining whether the packet type matches the packet sending capability corresponding to the device ID, and checking whether the flow parameters are within the range supported by the device.
[0136] Step B3: In response to the verification result being a failure, a reminder of a new flow configuration failure is sent to the user interface so that the user interface displays the reminder of a new flow configuration failure.
[0137] If the result of the legality check is a failure, the interactive device will send a reminder to the user interface that the new traffic configuration has failed. This reminder can be a text prompt, a pop-up warning, or other forms of feedback, so that the user can promptly know the reason for the configuration failure and take appropriate measures to correct it. After receiving this reminder, the user interface will display it to the user so that the user can understand the reason for the configuration failure and make adjustments accordingly.
[0138] Step B4: In response to the verification result being successful, a flow ID is generated according to the configuration flow information.
[0139] In order to achieve effective traffic execution management and monitoring, each flow needs to have a unique identifier, namely flow ID. These flow IDs not only help to distinguish and track various data flows in the network, but also provide the basis for subsequent traffic analysis, optimization and control.
[0140] The generation of flow IDs usually adopts the self-incrementing ID method. Self-incrementing ID means that each time a new flow ID is generated, its value will automatically increase by a certain amount to ensure the uniqueness of each flow ID. Specifically, the flow ID is automatically generated based on the previously assigned flow ID, usually by adding a certain value to the last assigned flow ID. In this way, as time goes by and the traffic continues to increase, the flow ID will continue to increase. The advantage of using self-incrementing ID as the flow ID is its simplicity and ease of management. Since each flow ID is automatically generated according to certain rules, no human intervention or management is required. In addition, the generation method of self-incrementing ID also ensures the uniqueness of the flow ID and avoids confusion and errors caused by duplicate IDs.
[0141] Step B5, save the configuration flow information and flow ID.
[0142] After the flow ID is generated, these configured traffic information and flow ID can be saved to the corresponding database for efficient processing when the traffic configuration is quickly retrieved and loaded when needed.
[0143] Step B6: Send the stream ID to the user interface so that the user interface displays the stream ID.
[0144] The generated flow ID is sent to the user interface so that the user can understand the identification information of each flow of the configured traffic information. After receiving the flow ID, the user interface can display it to the user or use it for subsequent traffic monitoring, statistics and analysis operations.
[0145] Step B7: encapsulate the configuration flow information into an Ethernet message and save it.
[0146] Ethernet message is a data packet format transmitted in Ethernet. Ethernet message contains frame header, frame data and frame trailer, wherein the frame header contains information such as source MAC address, destination MAC address, protocol type, etc., the frame data contains the actual data content, and the frame trailer is used for data checksum. Encapsulating the configuration flow information into Ethernet message and saving it ensures that the data packet can be correctly sent and processed, thereby ensuring the efficient operation and security of the network.
[0147] At this point, the above steps B1 to B7 complete the creation of the configuration flow information.
[0148] Optionally, after creating a new configuration flow information, the user can delete the newly created configuration flow information, as follows: Figure 2C The flow information deletion operation from step C1 to step C3 shown is as follows:
[0149] Step C1: in response to receiving a configuration flow information deletion instruction, obtaining a flow ID to be deleted.
[0150] When the user selects "Delete configured traffic information" in the user interface, a configuration traffic information deletion instruction can be triggered. After receiving the configuration traffic information deletion instruction, the interactive device can obtain the flow ID corresponding to the configuration traffic information that the user needs to delete, that is, the flow ID to be deleted.
[0151] Step C2: Determine whether there is a configuration traffic template in the execution state of being executed among all the configuration traffic templates.
[0152] All configured traffic templates include all newly created configured traffic templates. It is determined whether there are any configured traffic templates in the execution state in all configured traffic templates, ensuring that the running process will not be affected before trying to delete the flow. This step is implemented by checking the status of the traffic template. If any flow is found to be using any configured traffic template, the flow cannot be deleted immediately.
[0153] Step C3: If yes, sending a flow deletion failure reminder to the user interface so that the user interface displays the flow deletion failure reminder.
[0154] If the result is yes, that is, there is an executing flow that is using the template, we cannot delete the flow directly. A flow deletion failure reminder is sent to the user interface to inform the user that the deletion operation failed and explain the reason for the failure, that is, there is an executing flow for the corresponding configured traffic template. This helps users understand and handle this error situation.
[0155] Step C4: If not, delete the storage information corresponding to the stream ID to be deleted.
[0156] As mentioned above, the configured flow information will be saved to the specified storage medium. After receiving the configuration flow information deletion instruction, all storage information corresponding to the flow ID needs to be deleted in the storage medium, including but not limited to the stream table, ethstream table, StreamState table, EthStreamState table, etc.
[0157] Step C5: Send a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
[0158] Sending deletion result reminders to users can not only enhance user satisfaction, but also ensure data security and system reliability.
[0159] At this point, steps C1 to C3 can delete the newly created configuration flow information.
[0160] When the configuration traffic template ends or at other times, the generated configuration traffic template can be deleted. The template deletion operation in steps D1 to D5 is as follows:
[0161] Step D1, in response to receiving a configuration traffic template deletion instruction, obtain the template ID to be deleted.
[0162] When the user selects "Delete configuration traffic template" in the user interface, the configuration traffic template deletion instruction can be triggered. After the interactive device receives the configuration traffic template deletion instruction, it can obtain the template ID corresponding to the configuration traffic template that the user needs to delete, that is, the template ID to be deleted.
[0163] Step D2, determining whether there is a configuration traffic template in the execution state of being executed among all the configuration traffic templates.
[0164] All configured traffic templates include all newly created configured traffic templates. It is determined whether there are any configured traffic templates in the execution state in all configured traffic templates to ensure that the running process will not be affected before trying to delete the flow. This step is implemented by checking the status of the traffic template. If any flow is found to be using any configured traffic template, the template cannot be deleted immediately.
[0165] Step D3: If yes, send a template deletion failure reminder to the user interface.
[0166] If the result is yes, that is, there is an ongoing flow using the template, we cannot delete the template directly. A template deletion failure reminder is sent to the user interface to inform the user that the deletion operation failed and explain the reason for the failure, that is, there is an ongoing flow. This helps users understand and handle this error situation.
[0167] Step D4: If not, delete the storage information of the template and all flow IDs corresponding to the template ID.
[0168] If the result of the judgment is no, that is, no flow in execution uses the template, the template corresponding to the template ID and the storage information of all flow IDs are deleted, including but not limited to the stream table, ethstream table, StreamState table, EthStreamState table, etc. This means that the template and its related flow information are completely removed.
[0169] Step D5, sending a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
[0170] Send a deletion result reminder to the user interface to tell the user the result of the template deletion operation, whether it was successful or failed. If the deletion is successful, the reminder can include the deleted template ID. If the deletion fails, the reminder can include the reason for the failure and the solution.
[0171] So far, steps D1 to D5 have realized the deletion of the configured traffic template.
[0172] Through the above settings of the configuration traffic template, users can independently set test business policies, write traffic policies planned to be executed during the test, and flexibly test the performance of various SRIO chips.
[0173] As a possible implementation, before step 201, the method further includes: step 207, initializing global data and environment parameters.
[0174] In multi-threaded programming, initializing global data and environment parameters is one of the key steps to ensure stable program operation. Global data refers to data that can be accessed anywhere in the program, while environment parameters refer to various parameters provided by the operating system to the process, such as environment variables. In a multi-threaded environment, since multiple threads may access and modify global data at the same time, global data must be properly initialized to avoid data competition and inconsistency problems. At the same time, the initialization of environment parameters is also a prerequisite for ensuring that the program can run correctly.
[0175] Initialize global data, which includes allocating memory space for global variables and setting their initial values. For some global data, special initialization operations may be required, such as clearing, setting default values, etc. In addition, it is also necessary to initialize some environmental parameters according to the needs of the program, such as direct memory access (DMA) parameters, statistical switches, etc. The settings of these parameters will directly affect the operation mode and performance of the program.
[0176] Optionally, the initialization process can be repeated until the thread is successfully started, ensuring that the user already has a data table before use, otherwise the data cannot be stored and the system cannot run. The data table already has basic data, such as device information data. If not, the template cannot be created. Secondly, the initialization of environmental parameters can provide a good environment for the operation of the program and ensure that the program can interact with the operating system correctly. If these initialization operations are not performed before the thread is started, it may cause the program to run unstably or even crash. Therefore, initialization operations need to be performed before the thread is started.
[0177] As a possible implementation, before step 201, the method further includes: step 208, in response to receiving a clear instruction, sending a data clear message to the endpoint device, so that the endpoint device clears the global statistical data after receiving the data clear message.
[0178] The endpoint device will query the traffic execution status (including counting information) when the timer expires or the traffic execution ends. When the traffic execution status changes, the traffic execution status will be sent to the interactive device so that the interactive device can update the database. In order to prevent the last packet sending and receiving count from interfering with the current packet sending and receiving statistics, when performing a new round of test services corresponding to the configuration traffic template, it is necessary to clear the global data previously generated by the endpoint device (including traffic execution status, etc.).
[0179] In summary, the traffic execution management method provided by the above embodiments of the present disclosure can achieve at least the following beneficial effects:
[0180] (1) No need to enter command lines, which lowers the threshold for using packet sending and receiving operations.
[0181] (2) Through pre-set configuration traffic templates, the SRIO environment can be managed with one-click software, which is easy to operate.
[0182] (3) Support various test verifications of the physical layer, protocol layer, and application layer of SRIO chips in high-density networking environments. Through the construction of the SRIO environment, users are provided with debugging and performance testing methods for SRIO protocol interconnection, network management interoperability, and stability under high traffic pressure.
[0183] (4) It can access any SRIO network topology and support any network and adapt to extended SRIO endpoint devices.
[0184] (5) Users can customize any traffic service strategy.
[0185] Continue to see Figure 3 , which shows a process 300 of another embodiment of the flow execution management method according to the present disclosure, the flow execution management method comprises the following steps:
[0186] Step 301: in response to receiving a query instruction, sending endpoint device information in the SRIO network to a user interface.
[0187] The user can enter the URL in the browser to enter the user interface (such as the homepage of the SRIO traffic generation management tool) and interact with the interactive device. The user clicks the query button, and the interactive device responds to receiving the query instruction and executes the process of step 205 to step 206 of the above embodiment to send the endpoint device information in the SRIO network to the user interface.
[0188] For example, the current SRIO network includes 11 endpoint devices, and users can view detailed information of all endpoint devices: device IP, endpoint ID, device type, endpoint operating status, operating rate, width, SRIO traffic types supported by the device, and traffic configuration associated with the device.
[0189] Step 302: In response to receiving a clear instruction, a data clear message is sent to the endpoint device, so that the endpoint device clears the global statistical data after receiving the message.
[0190] Step 303: In response to receiving the start instruction, the configured traffic template is issued to the corresponding endpoint device according to the device ID in the configured traffic template.
[0191] The user can select the configuration flow template to be started and click the start button to execute the flow template. In response to receiving the start instruction, the interactive device sends the configuration flow template to the corresponding endpoint device according to the device ID in the configuration flow template.
[0192] It should be noted that the configuration of the traffic template will correspond to the execution status, including but not limited to "not started", "in execution", "completed", "stopped", and "abnormal". After the user clicks the start button, the execution status of the configuration traffic template will be updated from "not started" to "in execution"; when the configuration traffic template is executed, the execution status will be updated to "completed"; if the traffic package is abnormal, the execution status will be updated to "abnormal". When the user clicks to enter the configuration traffic template, the specific execution status of each type of flow can be viewed.
[0193] For example, configure the traffic template to set the number of loops to 10 times, and the user can view the execution status of the template and flow in real time.
[0194] When the user clicks the start button (i.e. the interactive device responds to receiving the start instruction), it is necessary to first determine whether the execution status of the currently configured traffic template is "executing". If so, send a startup failure reminder such as "the current template is being executed and cannot be started" to the user interface. If not, execute the subsequent steps.
[0195] The database is queried to see whether the current running status of the corresponding device is "online". If not, a startup failure reminder such as "the current device is not online and cannot be started" is sent to the user interface. If not, the subsequent steps are executed.
[0196] According to the device type and device ID in the configured traffic template, the corresponding data packet is read from the database (for example, the EthStreamState table) into the memory.
[0197] Traverse all endpoint devices and connect to the current interactive device. If the connection is not successful within the connection time, send a connection failure reminder such as "failed to connect to the interactive device, please try again" to the user interface, and set the Ethernet packet flag corresponding to the EthStreamState table in the database to 1. If the connection is successful, execute the subsequent steps.
[0198] Traverse all flows of the configured traffic template and send corresponding data packets to the corresponding endpoint devices. In response to receiving response messages from all sent endpoint devices, send a "start" message data packet to all sent endpoint devices. In response to receiving response messages from all sent endpoint devices, store the data packet corresponding to the configured traffic template in the database (for example, the EthStreamState table). Update the status of the corresponding flow in the database StreamState table to "executing", update the status of the corresponding template in the database StreamModel table to "executing", and update the execution status of the current configured traffic template in the user interface to "executing".
[0199] Optionally, during this process, the user can click the "Stop" button at any time, and the interactive device responds to receiving the stop instruction and sends a stop instruction to the endpoint device. In response to receiving the stop instruction, the interactive device determines whether the execution status of the configured traffic template is "executing". If not, a stop failure reminder such as "the template is not in execution and cannot be stopped" is sent to the user interface. If so, execute the subsequent steps.
[0200] Traverse all flows in the configured traffic template and determine whether there is a stop message packet in its EthStreamState table. If not, combine the Streamld and the field with the running status of "stop" into a data packet message, store it in the EthStreamState table, and then execute the subsequent steps. If yes, execute the subsequent steps.
[0201] The EthStreamState table is read into the memory, and the endpoint devices corresponding to the configured traffic template are traversed. If the connection is not successful within the connection time, a connection failure reminder such as "failed to connect to the interactive device, please try again" is sent to the user interface, and the Ethernet packet flag corresponding to the EthStreamState table in the database is set to 1. If the connection is successful, execute the subsequent steps.
[0202] Send a stop data packet to each connected endpoint device in turn, update the status of the corresponding flow in the database StreamState table to "stopped", and send the execution status of the corresponding flow to the user interface as "stopped". When the execution status of all flows of the configured traffic template is "stopped", update the execution status of the configured traffic template to "stopped" to the user interface.
[0203] Step 304: Receive the traffic execution result generated and sent by the endpoint device according to the configured traffic template.
[0204] Step 305: Send the flow execution result to the user interface so that the user interface displays the flow execution result.
[0205] For example, the specific calculation formula for the result corresponding to the traffic configuration template is:
[0206] Source device tx=12*11+12*11+4097*11*11+4097*11*12+4097*11*12+12*11+16*12=1577933, that is:
[0207] Maintenance write: 12 (number of endpoint devices 11 + source device self-count 1) * 11 (10 cycles + source device self-count 1)
[0208] Maintenance read: 12 (number of endpoint devices 11 + source device self-count 1) * 11 (10 cycles + source device self-count 1)
[0209] Nwrite: 4097 (maximum data length 4096 + 1M) * 11 (number of endpoint destination devices 10 + source device self-count 1) * 11 (loop 10 times + source device self-count 1)
[0210] NwriteR: 4097 (maximum data length 4096 + 1M) * 11 (number of endpoint destination devices 10 + source device self-count 1) * 12 (10 cycles + source device self-count 1 + source device response count 1)
[0211] Nread: 4097 (maximum data length 4096 + 1M) * 11 (number of endpoint destination devices 10 + source device self-count 1) * 12 (10 cycles + source device self-count 1 + source device response count 1)
[0212] Doorbell: 12 (11 endpoint devices + 1 source device self-count) * 11 (10 cycles + 1 source device self-count)
[0213] Message: 16 (maximum data length 16M) * 12 (10 cycles + source device self-count 1 + source device response count 1)
[0214] Source device rx=12*11+12*11+4097*11*10+4097*11*12+4097*11*12+12*11+16*12=1532866, that is:
[0215] Maintenance write: 12 (number of endpoint devices 11 + source device self-count 1) * 11 (10 cycles + source device self-count 1)
[0216] Maintenance read: 12 (number of endpoint devices 11 + source device self-count 1) * 11 (10 cycles + source device self-count 1)
[0217] Nwrite: 4097 (maximum data length 4096 + 1M) * 11 (number of endpoint destination devices 10 + source device self-count 1) * 10 (loop 10 times)
[0218] NwriteR: 4097 (maximum data length 4096 + 1M) * 11 (number of endpoint destination devices 10 + source device self-count 1) * 12 (10 cycles + source device self-count 1 + source device response count 1)
[0219] Nread: 4097 (maximum data length 4096 + 1M) * 11 (number of endpoint destination devices 10 + source device self-count 1) * 12 (10 cycles + source device self-count 1 + source device response count 1)
[0220] Doorbell: 12 (11 endpoint devices + 1 source device self-count) * 11 (10 cycles + 1 source device self-count)
[0221] Message: 16 (maximum data length 16M) * 12 (10 cycles + source device self-count 1 + source device response count 1)
[0222] Destination device tx=1*11+1*11+0+4097*11+4097*11+1*11+16*11=90343, that is:
[0223] Maintenance write: 1 (number of endpoint single destination devices 1) * 11 (10 cycles + destination device self-count 1)
[0224] Maintenance read: 1 (number of endpoint single destination devices 1) * 11 (10 cycles + destination device self-count 1)
[0225] Nwrite: 0
[0226] NwriteR: 4097 (maximum data length 4096 + 1M) * 11 (10 cycles + destination device response count 1)
[0227] Nread: 4097 (maximum data length 4096 + 1M) * 11 (10 cycles + target device response count 1)
[0228] Doorbell: 1 (number of endpoint single destination devices 1) * 11 (10 cycles + destination device self-count 1)
[0229] Message: 16 (maximum data length 16M) * 11 (10 cycles + destination device self-count 1)
[0230] Destination device rx=1*11+1*11+0+4097*11+4097*11+1*11+16*11=135410, that is:
[0231] Maintenance write: 1 (number of endpoint single destination devices 1) * 11 (10 cycles + destination device self-count 1)
[0232] Maintenance read: 1 (number of endpoint single destination devices 1) * 11 (10 cycles + destination device self-count 1)
[0233] Nwrite: 4097 (maximum data length 4096 + 1M) * 11 (10 cycles + destination device response count 1)
[0234] NwriteR: 4097 (maximum data length 4096 + 1M) * 11 (10 cycles + destination device response count 1)
[0235] Nread: 4097 (maximum data length 4096 + 1M) * 11 (10 cycles + target device response count 1)
[0236] Doorbell: 1 (number of endpoint single destination devices 1) * 11 (10 cycles + destination device self-count 1)
[0237] Message: 16 (maximum data length 16M) * 11 (10 cycles + destination device self-count 1)
[0238] If the template execution status is finally displayed as: Execution completed, and in the statistics page, the number of packets sent and received by each endpoint device are: the number of packets sent by the source device is 1577933, the number of packets received is 1532866, the number of packets sent by the destination device is 90343, and the number of packets received is 135410, then the test is considered to have passed.
[0239] Through the above embodiments, users can customize any traffic service strategy through the user interface, which is easy to operate and can support one-click deployment of the system without a high threshold, and can implement traffic execution management of the SRIO chip.
[0240] Further references Figure 4 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a flow execution management device, and the device embodiment is Figure 2A Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices (including interactive devices).
[0241] like Figure 4 As shown, the traffic execution management device 400 of this embodiment includes: a template issuing module 401 and a result receiving module 402.
[0242] Among them, the template sending module 401 is used to send the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template, the configured traffic template includes a data traffic execution management strategy, the data traffic execution management strategy includes the device type and device ID of the endpoint device to which the configured traffic template needs to be sent, and the endpoint device has an embedded SRIO chip;
[0243] The result receiving module 402 is used to receive the flow execution result. The flow execution result is obtained by the endpoint device parsing the parameters of the received configuration flow template, and then issuing the flow configuration according to the parameters of the configuration flow template, and then obtaining and sending the statistics of the flow sent and received by the current device.
[0244] In this embodiment, the specific processing of the flow execution management device 400 and the technical effects thereof can be referred to in Figure 2A The relevant descriptions of step 201 and step 202 in the corresponding embodiment are not repeated here.
[0245] In some optional implementations, the device 400 further includes:
[0246] The result sending module 403 is used to send the flow execution result to the user interface so that the user interface displays the flow execution result.
[0247] In some optional implementations, the template sending module 401 includes:
[0248] The template start-up and delivery unit 4011 is used to deliver the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template in response to receiving the start-up instruction; and
[0249] The device 400 further includes:
[0250] The template stopping execution unit 404 is configured to send a stop data packet to the endpoint device in response to receiving a stop instruction and the execution status of the endpoint device is in execution, so that the endpoint device stops generating the traffic execution result.
[0251] In some optional implementations, the result sending module 403 includes:
[0252] The refresh result unit 4031 is used to send the current flow execution result to the user interface in response to receiving a refresh instruction, so that the user interface displays the current flow execution result.
[0253] In some optional implementations, the device 400 further includes:
[0254] The query acquisition module 405 is used to obtain the endpoint device information in the SRIO network in response to receiving the query instruction;
[0255] The query display module 406 is used to send the endpoint device information in the SRIO network to the user interface so that the user interface displays the endpoint device information in the SRIO network.
[0256] In some optional implementations, the query acquisition module 405 includes:
[0257] The query issuing unit 4051 is used to send an endpoint device information query instruction to the network management system;
[0258] The query receiving unit 4052 is used to receive the endpoint device information in the SRIO network sent by the network management system.
[0259] In some optional implementations, the creation of the configuration traffic template is based on the following template creation operations:
[0260] In response to receiving a new creation instruction of a traffic configuration template, acquiring template information;
[0261] Generate a template ID based on the template information;
[0262] Saving the template information and the template ID;
[0263] The template ID is sent to a user interface so that the user interface displays the template ID.
[0264] In some optional implementations, the configured traffic template includes configured traffic information, and the creation of the configured traffic information is based on the following traffic information creation operation:
[0265] In response to receiving a flow information creation instruction, obtaining configuration flow information;
[0266] Verifying the legitimacy of the configuration flow information;
[0267] In response to a result of the verification being a failure, sending a traffic configuration creation failure reminder to a user interface so that the user interface displays the traffic configuration creation failure reminder;
[0268] In response to a successful result of the verification, generating a flow ID according to the configured flow information;
[0269] Saving the configuration flow information and the flow ID;
[0270] sending the stream ID to the user interface so that the user interface displays the stream ID;
[0271] The configuration flow information is encapsulated into an Ethernet message and saved.
[0272] In some optional implementations, the deletion of the configured flow information is based on the following flow information deletion operation:
[0273] In response to receiving the configuration flow information deletion instruction, obtaining the flow ID to be deleted;
[0274] Determine whether there is a configuration traffic template in the execution state among all configuration traffic templates;
[0275] If yes, sending a flow deletion failure reminder to the user interface so that the user interface displays the flow deletion failure reminder;
[0276] If not, deleting the storage information of the flow corresponding to the flow ID to be deleted;
[0277] Sending a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
[0278] In some optional implementations, the configuration traffic template is deleted according to the following template deletion operation:
[0279] In response to receiving the configuration traffic template deletion instruction, obtaining the template ID to be deleted;
[0280] Determine whether there is a configuration traffic template in the execution state among all configuration traffic templates;
[0281] If yes, sending a template deletion failure reminder to the user interface so that the user interface displays the template deletion failure reminder;
[0282] If not, delete the template and storage information of all flow IDs corresponding to the template ID;
[0283] Sending a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
[0284] In some optional implementations, the device 400 further includes:
[0285] The clearing module 407 is configured to send a data clearing message to the endpoint device in response to receiving a clearing instruction, so that the endpoint device clears the global statistical data after receiving the data clearing message.
[0286] It should be noted that the implementation details and technical effects of each module and unit in the traffic execution management device provided in the embodiments of the present disclosure can be referred to the description of other embodiments in the present disclosure, and will not be repeated here.
[0287] Reference below Figure 5 , which shows a schematic diagram of the structure of a computer system 500 suitable for implementing the electronic device of the present disclosure. Figure 5 The computer system 500 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0288] like Figure 5 As shown, the computer system 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 to a random access memory (RAM) 503. Various programs and data required for the operation of the computer system 500 are also stored in the RAM 503. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.
[0289] Typically, the following devices may be connected to the I / O interface 505: input devices 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, etc.; output devices 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 508 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 509. The communication devices 509 may allow the computer system 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 The computer system 500 of an electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.
[0290] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.
[0291] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.
[0292] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.
[0293] The computer readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device implements the following Figure 2AThe illustrated embodiment and its optional implementations illustrate a method for traffic execution management.
[0294] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Python, C++, and conventional procedural programming languages such as C or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0295] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession 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 square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0296] The units or modules involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit or module does not limit the unit itself in some cases. For example, the result receiving module may also be described as "for sending the configured traffic template to the corresponding endpoint device according to the device ID in the configured traffic template".
[0297] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.
Claims
1. A flow execution management method, It is characterized in that The method is applied to an interactive device, comprising: In response to receiving the start instruction, according to the device ID in the configuration traffic template, the configuration traffic template is issued to the corresponding endpoint device, the configuration traffic template includes a data traffic execution management strategy, the data traffic execution management strategy includes the device type and device ID of the endpoint device to which the configuration traffic template needs to be issued, and the endpoint device has an embedded SRIO chip; In response to receiving a stop instruction and the execution state of the endpoint device being in execution, sending a stop data packet to the endpoint device so that the endpoint device stops generating traffic execution results; The traffic execution result is received, and the endpoint device parses the parameters of the received configuration traffic template, and then issues the traffic configuration according to the parameters of the configuration traffic template, and then obtains and sends the statistics of the traffic sent and received by the current device.
2. The method according to claim 1, It is characterized in that The method further comprises: The flow execution result is sent to a user interface so that the user interface displays the flow execution result.
3. The method according to claim 2, It is characterized in that The sending the flow execution result to a user interface so that the user interface displays the flow execution result includes: In response to receiving the refresh instruction, the current traffic execution result is sent to the user interface so that the user interface displays the current traffic execution result.
4. The method according to claim 1, It is characterized in that The method further comprises: In response to receiving the query instruction, obtaining endpoint device information in the SRIO network; The endpoint device information in the SRIO network is sent to a user interface so that the user interface displays the endpoint device information in the SRIO network.
5. The method according to claim 4, It is characterized in that The obtaining of endpoint device information in the SRIO network includes: Send endpoint device information query instructions to the network management system; Receive endpoint device information in the SRIO network sent by the network management system.
6. The method according to claim 1, It is characterized in that The configuration flow template is created based on the following template creation operations: In response to receiving a new creation instruction of a traffic configuration template, acquiring template information; Generate a template ID based on the template information; Saving the template information and the template ID; The template ID is sent to a user interface so that the user interface displays the template ID.
7. The method according to claim 6, It is characterized in that The configuration flow template includes configuration flow information, and the configuration flow information is created according to the following flow information creation operation: In response to receiving a flow information creation instruction, obtaining configuration flow information; Verifying the legitimacy of the configuration flow information; In response to a result of the verification being a failure, sending a traffic configuration creation failure reminder to a user interface so that the user interface displays the traffic configuration creation failure reminder; In response to a successful result of the verification, generating a flow ID according to the configured flow information; Saving the configuration flow information and the flow ID; sending the stream ID to the user interface so that the user interface displays the stream ID; The configuration flow information is encapsulated into an Ethernet message and saved.
8. The method according to claim 7, It is characterized in that The configuration flow information is deleted according to the following flow information deletion operation: In response to receiving the configuration flow information deletion instruction, obtaining the flow ID to be deleted; Determine whether there is a configuration traffic template in the execution state among all configuration traffic templates; If yes, sending a flow deletion failure reminder to the user interface so that the user interface displays the flow deletion failure reminder; If not, deleting the storage information of the flow corresponding to the flow ID to be deleted; Sending a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
9. The method according to claim 7, It is characterized in that The configuration traffic template is deleted according to the following template deletion operations: In response to receiving the configuration traffic template deletion instruction, obtaining the template ID to be deleted; Determine whether there is a configuration traffic template in the execution state among all configuration traffic templates; If yes, sending a template deletion failure reminder to the user interface so that the user interface displays the template deletion failure reminder; If not, delete the template and storage information of all flow IDs corresponding to the template ID; Sending a deletion result reminder to the user interface so that the user interface displays the deletion result reminder.
10. The method according to claim 1, It is characterized in that The method further comprises: In response to receiving the clear instruction, a data clear message is sent to the endpoint device, so that the endpoint device clears the global statistical data after receiving the data clear message.
11. A flow execution management device, It is characterized in that The device is applied to an interactive device, comprising: A template startup issuing unit, configured to issue the configured traffic template to the corresponding endpoint device in response to receiving the startup instruction according to the device ID in the configured traffic template, wherein the configured traffic template includes a data traffic execution management strategy, and the data traffic execution management strategy includes a device type and a device ID of the endpoint device to which the configured traffic template needs to be issued, and the endpoint device has an embedded SRIO chip; A template stop execution unit, configured to, in response to receiving a stop instruction and the execution state of the endpoint device being in execution, send a stop data packet to the endpoint device so that the endpoint device stops generating a traffic execution result; The result receiving module is used to receive the traffic execution result. The traffic execution result is obtained by the endpoint device parsing the parameters of the received configuration traffic template, and then issuing the traffic configuration according to the parameters of the configuration traffic template, and then obtaining and sending the statistics of the traffic sent and received by the current device.
12. An electronic device, It is characterized in that include: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the method according to any one of claims 1 to 10.
13. A computer-readable storage medium, It is characterized in that A computer program is stored thereon, wherein when the computer program is executed by one or more processors, the method according to any one of claims 1 to 10 is implemented.
