Multi-protocol fusion soft bus communication data processing method

Abstract

This invention provides a multi-protocol fusion soft bus communication data processing method, relating to data processing technology, comprising: generating a device topology diagram based on a first location; loading corresponding protocol service components and orchestrating them onto the soft bus based on the protocol identifiers of the first devices; splitting the device topology diagram based on the same protocol identifiers of the first devices to obtain protocol sub-topology diagrams corresponding to each protocol identifier, and generating virtual protocol lines corresponding to the protocol sub-topology diagrams and connected to the soft bus; generating a protocol priority strategy based on the user terminal's positioning information of each virtual protocol line and the protocol sub-topology diagram; generating a device priority strategy based on the user terminal's partitioning information of each first device in the protocol sub-topology diagram; obtaining the communication level of each first device based on the protocol priority strategy and the device priority strategy; and updating the protocol service components according to the communication level.

Description

Technical Field

[0001] This invention relates to data processing technology, and more particularly to a multi-protocol fusion soft bus communication data processing method. Background Technology

[0002] In today's Industrial Internet of Things (IIoT) applications, factory and enterprise devices and systems need to communicate reliably and efficiently. To achieve this, it is often necessary to integrate multiple communication protocols within a single system. However, the increasing number of devices and systems leads to greater communication complexity and management difficulty, especially in environments requiring real-time processing and highly reliable data exchange.

[0003] Current multiprotocol communication systems typically use pre-configured static converters or gateways to bridge devices using different protocols. While this approach can address multiprotocol compatibility issues to some extent, it suffers from poor flexibility and scalability. Furthermore, statically configured systems struggle to adapt quickly to dynamic production demands, leading to uneven resource allocation and increased communication latency, ultimately impacting overall efficiency.

[0004] Therefore, it is crucial to dynamically adjust and optimize communication priorities in a multi-protocol environment to quickly and flexibly adapt to changing communication needs in different industrial scenarios. Summary of the Invention

[0005] This invention provides a multi-protocol fusion soft bus communication data processing method that can dynamically adjust and optimize communication priorities in a multi-protocol environment, so as to quickly and flexibly adapt to changing communication needs in different industrial scenarios.

[0006] A first aspect of this invention provides a multi-protocol fusion soft bus communication data processing method, comprising:

[0007] Obtain the first location of the first device, generate a device topology map based on the first location, and load the corresponding protocol service components and orchestrate them onto the soft bus based on the protocol identifier of the first device.

[0008] The device topology is split based on the same protocol identifier of the first device to obtain a protocol sub-topology corresponding to each protocol identifier, and a virtual protocol line corresponding to the protocol sub-topology and connected to the soft bus is generated.

[0009] Based on the user terminal's location information for each virtual protocol line and protocol sub-topology, a protocol priority strategy is generated; based on the user terminal's partitioning information for each first device in the protocol sub-topology, a device priority strategy is generated.

[0010] The communication level of each of the first devices is obtained based on the protocol priority policy and the device priority policy, and the protocol service component is updated according to the communication level.

[0011] Optionally, in one possible implementation of the first aspect, the step of loading the corresponding protocol service component and orchestrating it to the soft bus according to the protocol identifier of the first device includes:

[0012] The preset component library is traversed according to the protocol identifier of the first device to determine the protocol service component corresponding to the protocol identifier of the first device as the target service component.

[0013] The target service components are loaded and orchestrated onto the soft bus, and the preset component library corresponds one-to-one with the soft bus;

[0014] The step of splitting the device topology map based on the same protocol identifier of the first device to obtain protocol sub-topology maps corresponding to each protocol identifier includes:

[0015] The first devices with the same protocol identifier are grouped together to obtain a set of devices corresponding to each protocol identifier;

[0016] The first device outside the device set is identified as the split device, and the split device is deleted from the device topology graph to obtain the initial topology graph corresponding to the device set.

[0017] The initial topology graph is merged to obtain a protocol sub-topology graph.

[0018] Optionally, in one possible implementation of the first aspect, the merging process of the initial topology graph to obtain a protocol sub-topology graph includes:

[0019] The first square region is obtained based on the first position of each first device in the initial topology diagram;

[0020] Centered on the corresponding first square area, other first square areas closest to the first square area are determined as second square areas in each preset direction. The preset directions include vertical directions and horizontal directions. The vertical directions include upward directions and downward directions. The horizontal directions include left directions and right directions.

[0021] Obtain the distance information between the first square region and the second square region. When the distance information is greater than a preset distance, the corresponding second square region is regarded as the third square region.

[0022] The area between the first square region and the third square region is determined as the clipping region;

[0023] The clipped region is clipped to obtain the protocol sub-topology graph.

[0024] Optionally, in one possible implementation of the first aspect, determining the area between the first square region and the third square region as the clipping area includes:

[0025] Determine the relative orientation between the third square region and the first square region;

[0026] When the relative orientation is in the upper position, the upper edge line of the first square area is determined and extended to obtain the first trimming line, and the lower edge line of the third square area is determined and extended to obtain the second trimming line.

[0027] When the relative orientation relationship is downward, the lower edge line of the first square area is determined and extended to obtain the first cutting line, and the upper edge line of the third square area is determined and extended to obtain the second cutting line.

[0028] When the relative orientation is left, the left edge line of the first square area is determined and extended to obtain the first trimming line, and the right edge line of the third square area is determined and extended to obtain the second trimming line.

[0029] When the relative orientation is to the right, the right edge line of the first square area is determined and extended to obtain the first trimming line, and the left edge line of the third square area is determined and extended to obtain the second trimming line.

[0030] The area between the first and second cutting lines is taken as the cutting area.

[0031] Optionally, in one possible implementation of the first aspect, generating the virtual protocol line corresponding to the protocol sub-topology and connected to the soft bus includes:

[0032] Construct a horizontal virtual soft bus corresponding to the soft bus, and generate protocol level slots in sequence below the horizontal virtual soft bus according to the protocol priority level order, wherein the protocol level slots correspond one-to-one with the protocol priority.

[0033] Generate a virtual protocol line corresponding to the protocol sub-topology diagram, and connect the lower endpoint of the protocol sub-topology diagram to the virtual protocol line;

[0034] The step of generating a protocol priority strategy based on the user's location information of each virtual protocol line and protocol sub-topology includes:

[0035] Receive the location information of the upper end point of the virtual protocol line from the user terminal, and determine the protocol level slot with connection relationship as the target level slot based on the location information;

[0036] The protocol priority corresponding to the target level slot is obtained as the protocol priority strategy of the virtual protocol line.

[0037] The step of generating a device priority strategy based on the user's partitioning information of each first device in the protocol sub-topology diagram includes:

[0038] Based on the wiring trajectory of the first device in the protocol sub-topology diagram provided by the user terminal, multiple initial dividing lines are generated;

[0039] Based on the device priority configuration information of each dividing line by the user terminal, the pixel value of the initial dividing line is updated to obtain the dividing information, and the device priority corresponds one-to-one with the pixel value;

[0040] Based on the device priority of the partitioning information, a device priority strategy is generated for each of the first devices.

[0041] Optionally, in one possible implementation of the first aspect, obtaining the communication level of each of the first devices based on the protocol priority policy and the device priority policy, and updating the protocol service component according to the communication level, includes:

[0042] The protocol priority in the protocol priority strategy is used as the first priority of each first device, and the device priority in the device priority strategy is used as the second priority of each first device.

[0043] A first communication level of the first device is determined based on the first priority, and a second communication level of the first device is determined based on the second priority.

[0044] The communication level of each of the first devices is obtained based on the order of the first communication level and the second communication level, and the protocol service component is updated according to the communication level.

[0045] Optionally, in one possible implementation of the first aspect, it also includes:

[0046] An interactive plugin is pre-configured for each first device. The interactive plugin is used to count the first moment of the sent data packet and the second moment of the received data packet.

[0047] The interactive plugin generates a data interaction table, which contains data sending cells and data receiving cells.

[0048] When the interactive plugin determines that the first device has sent a data packet, it extracts the data tag and data time of the sent data packet and stores them in the sending cell. When the interactive plugin receives a data packet from the first device, it extracts the data tag and data time of the received data packet and stores them in the receiving cell.

[0049] After a preset time interval, the coordination plugin interacts with all the interaction plugins of the first device to extract the corresponding data interaction table, and generates the corresponding soft bus processing strategy based on the data interaction table, the first priority, and the second priority.

[0050] Optionally, in one possible implementation of the first aspect, after a preset time interval, the coordination plugin interacts with all interaction plugins of the first device to extract the corresponding data interaction table, and generates a corresponding soft bus processing strategy based on the data interaction table, the first priority, and the second priority, including:

[0051] The coordination plugin sorts all first devices based on the first priority to obtain the first sequence, and then sorts the first devices with the same first priority again based on the second priority to obtain the second sequence after two sortings.

[0052] The coordination plugin sequentially selects all the data interaction tables of the first devices in the second sequence as the master data interaction table, and determines the associated data interaction tables of other first devices based on the data tags in the sending and receiving cells respectively;

[0053] Based on the analysis of data times with the same data tags in the master data interaction table and the associated data interaction table, a soft bus delay coefficient and a corresponding soft bus processing strategy are generated.

[0054] Optionally, in one possible implementation of the first aspect, the step of analyzing data times based on the same data tags in the master data interaction table and the associated data interaction table to generate a soft bus delay coefficient and a corresponding soft bus processing strategy includes:

[0055] The data times with the same data labels extracted from the master data interaction table and the related data interaction table are calculated to obtain the difference time.

[0056] The comprehensive priority is calculated by multiplying the priority values ​​of the first priority and the second priority corresponding to the master data interaction table and the related data interaction table respectively. The first priority and the second priority of each master data interaction table and the related data interaction table correspond to preset priority values, and the priority is directly proportional to the priority value.

[0057] If the difference time is greater than or equal to the threshold time, the data delay sub-coefficient is obtained by comprehensive calculation based on the difference time, the comprehensive priority of the master data interaction table, and the comprehensive priority of the associated data interaction table.

[0058] All data delay sub-coefficients are aggregated to generate the soft bus delay coefficient, and the recommended data transmission volume corresponding to the soft bus processing strategy is determined based on the current data transmission volume of the soft bus.

[0059] If the difference time is greater than or equal to the threshold time, then a data delay sub-coefficient is calculated based on the difference time, the comprehensive priority of the master data interaction table, and the comprehensive priority of the associated data interaction table, including:

[0060] Alternatively, in one possible implementation of the first aspect, the data delay sub-coefficient is calculated using the following formula:

[0061] in, The first in the master data interaction table Data delay sub-coefficient for each data label, The first in the master data interaction table Data time for each data label For the first in the related data interaction table Data time for each data label For time normalization, The first priority of the first device corresponding to the main data interaction table. The second priority of the first device corresponding to the main data interaction table. Main interaction weight, The first priority of the first device corresponding to the associated data interaction table. The second priority of the first device corresponding to the associated data interaction table. For associated interaction weights, Priority normalized value;

[0062] After determining the data delay sub-coefficient, the corresponding first-order data in the master data interaction table and the associated data interaction table will be used to determine the delay sub-coefficient. Data tags are deleted and updated;

[0063] The calculation of the data delay sub-coefficient is stopped after determining that there are no data labels in any data interaction table within the second sequence;

[0064] The process of summarizing all data delay sub-coefficients to generate a soft bus delay coefficient, and determining the recommended data transmission volume corresponding to the soft bus processing strategy based on the current data transmission volume of the soft bus, includes:

[0065] The soft bus delay coefficient is calculated using the following formula.

[0066] in, This represents the delay factor for the soft bus. This represents the upper limit of the data delay sub-coefficient. It is a constant value. To recommend the amount of data to transfer, This represents the current data transfer volume of the soft bus. This is a preset value. Recommend weights for data transmission volume.

[0067] This invention proposes a soft bus communication data processing method based on multi-protocol fusion. By generating a device topology diagram and loading corresponding protocol service components according to protocol identifiers, the method enables interconnection between devices using different protocols on the same soft bus. This design not only significantly reduces reliance on hardware protocol converters but also improves the system's scalability and compatibility, allowing for the rapid integration of new devices and protocols without altering the system architecture.

[0068] This invention allows users to adjust the communication priorities of devices and protocols through a visual interface. Users can drag virtual protocol lines on the interface to intuitively adjust protocol priorities and quickly set device priorities by dividing the lines. By combining protocol and device priority strategies, the system can optimize the order of data transmission and resource allocation, improving communication efficiency and reliability.

[0069] This invention utilizes interactive and coordination plugins to collect and analyze data exchanges between devices in real time, dynamically generating soft bus processing strategies. Based on priority strategies and real-time data analysis, the system can automatically calculate and adjust the recommended data transmission volume of the soft bus, reducing communication latency and enhancing network adaptability and overall performance. This intelligent strategy generation mechanism ensures efficient system operation in various production scenarios and improves management efficiency. Attached Figure Description

[0070] Figure 1 This is a flowchart illustrating a multi-protocol fusion soft bus communication data processing method provided in an embodiment of the present invention;

[0071] Figure 2 This is a schematic diagram of a data interaction table provided in an embodiment of the present invention. Detailed Implementation

[0072] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0073] See Figure 1This is a flowchart illustrating a multi-protocol fusion soft bus communication data processing method provided in an embodiment of the present invention. Figure 1 The execution entity of the method shown can be a software and / or hardware device. The execution entity of this application can include, but is not limited to, at least one of the following: user equipment, network equipment, etc. User equipment can include, but is not limited to, computers, smartphones, personal digital assistants (PDAs), and the aforementioned electronic devices. Network equipment can include, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of computers or network servers. Cloud computing is a type of distributed computing, consisting of a super virtual computer composed of a group of loosely coupled computers. This embodiment does not limit this. Steps S1 to S4 are detailed as follows:

[0074] S1, obtain the first location of the first device, generate a device topology map based on the first location, and load the corresponding protocol service components to the soft bus according to the protocol identifier of the first device.

[0075] First, the necessity of this solution is explained. In practical applications, a factory may include hundreds or thousands of devices that need to be controlled, and a large number of these devices may communicate with one or more soft buses. However, under different production strategies, the communication priorities of corresponding protocols or devices may differ to meet the communication needs of users when performing production tasks. For example, the communication priority of data protocol A may need to be higher than that of data protocol B, and the communication priorities of different devices within data protocol A may also differ; therefore, configuration is required. This solution provides a visual adjustment strategy to allow users to quickly and efficiently adjust communication priorities, as detailed below.

[0076] This step requires obtaining the location information of the first device. This location can be a physical location, such as its position within the factory. Obtaining the device's location helps users make subsequent visualization adjustments based on that location. Using the obtained location information, the system generates a device topology map. This topology map shows the layout and connections of the devices within the factory, aiding in understanding the positional relationships between them.

[0077] Each device has its own protocol identifier, indicating the type of communication protocol it uses (e.g., TCP / IP, HTTP, Modbus, etc.). Based on this protocol identifier, the system loads the corresponding protocol service component from a pre-defined component library. These components are then orchestrated onto the soft bus, enabling devices using different protocols to communicate via the soft bus.

[0078] Based on the above embodiments, step S1 can be implemented in the following ways:

[0079] S11, based on the protocol identifier of the first device, the preset component library is traversed to determine the protocol service component corresponding to the protocol identifier of the first device as the target service component.

[0080] This system traverses an internal pre-defined component library containing service components for various protocols. Based on the protocol identifier of the first device, the system locates and identifies the corresponding protocol service component as the target service component. Once the target service component is found, the system loads and orchestrates it onto the soft bus. Because each component in the pre-defined component library corresponds one-to-one with the soft bus, the loaded component can correctly connect to the soft bus, enabling the device to communicate with other devices via the soft bus.

[0081] S11, Load the target service component into the soft bus, and the preset component library corresponds one-to-one with the soft bus.

[0082] This disclosure can identify the protocol identifiers of different devices and dynamically load the corresponding protocol service components. This enables devices with different communication protocols to interconnect on the same soft bus, solving the problem of direct communication between devices with different protocols in traditional systems. Due to the component-based design, when a new device is connected, only the corresponding protocol service component needs to be added to the component library, without changing the overall system architecture. This gives the system good scalability and compatibility with new protocols and new devices.

[0083] By generating device topology diagrams, the system can intuitively display the layout and connection relationships of devices, facilitating management by maintenance personnel. At the same time, the multi-protocol integration approach reduces reliance on hardware such as protocol converters, lowering hardware costs and maintenance complexity.

[0084] S2, based on the same protocol identifier of the first device, the device topology map is split to obtain a protocol sub-topology map corresponding to each protocol identifier, and a virtual protocol line corresponding to the protocol sub-topology map and connected to the soft bus is generated.

[0085] Based on the above embodiments, in order to better manage and adjust the communication priorities of devices with different protocols, the system needs to split the device topology diagram, generate protocol sub-topology diagrams corresponding to each protocol identifier, and connect them to virtual protocol lines on the soft bus.

[0086] Based on the above embodiments, the step of splitting the device topology map based on the same protocol identifier of the first device to obtain a protocol sub-topology map corresponding to each protocol identifier includes:

[0087] S21, classify the first devices with the same protocol identifier to obtain a set of devices corresponding to each protocol identifier.

[0088] First, all devices are categorized based on their protocol identifiers. Devices with the same protocol identifier are grouped into the same device set. This yields the device set corresponding to each protocol identifier, facilitating subsequent topology diagram splitting.

[0089] S22, determine the first device outside the device set as the split device, delete the split device in the device topology graph, and obtain the initial topology graph corresponding to the device set.

[0090] For each device set, the system treats devices not belonging to that set as split devices. By removing these split devices from the original device topology graph, an initial topology graph for the corresponding device set is obtained. The initial topology graph contains only devices with the same protocol identifier and their connections.

[0091] S23, the initial topology graph is merged to obtain the protocol sub-topology graph.

[0092] This disclosure takes into account that devices using the same data protocol may be geographically dispersed, resulting in numerous blank areas in the initial topology diagram. Therefore, this disclosure requires merging the initial topology diagram to reduce its size and form a clearer and more concise protocol sub-topology diagram. The protocol sub-topology diagram only includes devices using the same protocol.

[0093] The step of merging the initial topology graph to obtain a protocol sub-topology graph includes:

[0094] S231, A first square region is obtained based on the first position of each first device in the initial topology diagram;

[0095] This disclosure generates a first square region containing each device based on its location information. These square regions represent the device's location and occupied space in the initial topology map. Generating a first square region containing the device can be achieved by determining a rectangle that completely encloses the image of the first device. For example, it can be achieved by determining the top, bottom, left, and optimal positions of the first device image, then generating a top horizontal line, a bottom horizontal line, a left horizontal line, and a right horizontal line, which ultimately form a rectangle.

[0096] S232, taking the corresponding first square area as the center, determine other first square areas that are closest to the first square area in each preset direction as second square areas. The preset directions include vertical directions and horizontal directions. The vertical directions include upward directions and downward directions. The horizontal directions include left directions and right directions.

[0097] For each first square region, this solution will search for the other first square region that is closest to it in a preset orientation (including the four directions of up, down, left, and right), and designate it as the second square region. This process is used to determine the relative positional relationship between the devices.

[0098] S233, obtain the distance information between the first square region and the second square region, and when the distance information is greater than a preset distance, take the corresponding second square region as the third square region.

[0099] Calculate the distance between the first square region and the second square regions in each direction. If the distance is greater than a preset threshold (i.e., a preset distance), it is considered that there is an excessively large blank area between the two regions. In this case, the corresponding second square region is marked as a third square region and needs to be cropped.

[0100] S234, determine the area between the first square area and the third square area as the cutting area.

[0101] The space between the second square region (marked as the third square region) and the corresponding first square region is defined as the clipping region. These clipping regions contain the redundant blank areas that need to be removed from the initial topology graph.

[0102] S235, perform clipping processing on the clipped area to obtain the protocol sub-topology diagram.

[0103] The defined trimming region is trimmed, removing unnecessary blank areas. After trimming, the size of the topology graph can be reduced, ultimately resulting in a more compact and clearer protocol sub-topology graph.

[0104] The step of determining the area between the first square region and the third square region as the clipping area includes:

[0105] S2341, Determine the relative orientation between the third square region and the first square region.

[0106] Determine the position of the third rectangular region (i.e., the rectangular region farther from the first rectangular region) relative to the first rectangular region, whether it is above, below, to the left, or to the right. Based on the coordinates of the first and third rectangular regions (e.g., center point coordinates), calculate their relative positions on a two-dimensional plane (e.g., the X and Y axes). By comparing the difference between the X and Y axis coordinates, determine the orientation of the third rectangular region relative to the first rectangular region.

[0107] S2342, when the relative orientation is upward, determine the upper edge line of the first square region and extend it to obtain the first cutting line, and determine the lower edge line of the third square region and extend it to obtain the second cutting line.

[0108] When the third square region is above the first square region, determine the top edge of the first square region. Taking the top edge of the first square region as the starting point, extend it infinitely to the left and right (in the positive and negative directions of the X-axis) to form a horizontal first cutting line. Determine the bottom edge of the third square region. Taking the bottom edge of the third square region, extend it to the left and right in the same way to form another horizontal second cutting line. The area between the first and second cutting lines is the area to be cut (located between the two lines in the Y-axis direction).

[0109] S2343, when the relative orientation relationship is downward, determine the lower edge line of the first square region and extend it to obtain the first cutting line, and determine the upper edge line of the third square region and extend it to obtain the second cutting line.

[0110] When the third-shaped area is below the first square area, determine the bottom edge of the first square area and extend it left and right to form the first cutting line. Determine the top edge of the third-shaped area and extend it left and right to form the second cutting line. The area between the two cutting lines is the part that needs to be cut.

[0111] S2344, when the relative orientation is left, determine the left edge line of the first square region and extend it to obtain the first trimming line, and determine the right edge line of the third square region and extend it to obtain the second trimming line.

[0112] The third square area is located to the left of the first square area. Determine the left edge of the first square area by extending it upwards and downwards (in the positive and negative Y-axis directions) to form a vertical first cutting line. Determine the right edge of the third square area by extending it upwards and downwards to form a second cutting line. The area between the two cutting lines is the portion that needs to be cut.

[0113] S2345, when the relative orientation is right, determine the right edge line of the first square region and extend it to obtain the first trimming line, and determine the left edge line of the third square region and extend it to obtain the second trimming line.

[0114] The third square area is located to the right of the first square area. Determine the right edge of the first square area, and extend it upwards and downwards to form the first cutting line. Determine the left edge of the third square area, and extend it upwards and downwards to form the second cutting line. The area between the two cutting lines is the part that needs to be cut.

[0115] S2346, the area between the first cutting line and the second cutting line is taken as the cutting area.

[0116] Identify the specific areas that need to be clipped to remove redundant blank areas in the initial topology map. Based on the first and second clipping lines determined in the preceding steps, a rectangular area is formed between them. This rectangular area covers the blank space between the first square area and the third square area. Clip this area, removing or reducing the blank space. Reposition the first square area and the third square area to make them closer together in the new topology map, reducing unnecessary spacing.

[0117] The process of generating virtual protocol lines corresponding to the protocol sub-topology and connected to the soft bus includes:

[0118] S24. Construct a horizontal virtual soft bus corresponding to the soft bus, and generate protocol level slots in sequence below the horizontal virtual soft bus according to the protocol priority level order, wherein the protocol level slots correspond one-to-one with the protocol priority.

[0119] To visually represent the priority relationships between protocols and the connections between devices and the soft bus in the topology diagram, we need to construct horizontal virtual soft buses, protocol-level slots, and virtual protocol lines. This will make the topology diagram structure clearer and easier for users to understand and operate.

[0120] Construct a horizontal virtual soft bus. Create a horizontal line in the topology diagram to represent the soft bus, serving as the backbone for all protocol connections. Generate protocol-level slots. Below the horizontal virtual soft bus, generate multiple protocol-level slots in descending order of protocol priority, with each slot corresponding to a specific protocol priority. Construct multiple protocol-level slots from left to right in the space below the virtual soft bus. The protocol-level slots are arranged from left to right according to protocol priority, with the leftmost slot having the highest priority. Each slot can be distinguished using visual elements (such as borders or colors) and labeled with its corresponding protocol priority. For example, if there are three protocol priorities: high, medium, and low, then generate three protocol-level slots from left to right, corresponding to high, medium, and low priorities respectively.

[0121] S25, generate a virtual protocol line corresponding to the protocol sub-topology diagram, and connect the lower endpoint of the protocol sub-topology diagram to the virtual protocol line.

[0122] Create a virtual protocol line for each protocol sub-topology diagram, connecting the protocol sub-topology diagram and the protocol-level slot of the virtual soft bus, reflecting the connection relationship between the device and the soft bus.

[0123] For each protocol sub-topology, create a virtual protocol line perpendicular to the horizontal virtual soft bus. Connect the lower endpoint of the virtual protocol line to the corresponding protocol sub-topology. Connect the lower endpoint of the virtual protocol line to the center point of the upper edge of the corresponding protocol sub-topology. In this way, each protocol sub-topology establishes an indirect connection with the virtual soft bus through a virtual protocol line. For example, protocol sub-topology A is connected to the horizontal virtual soft bus through a virtual protocol line 1, and the lower endpoint of virtual protocol line 1 is connected to sub-topology A.

[0124] The step of generating a protocol priority strategy based on the user's location information of each virtual protocol line and protocol sub-topology includes:

[0125] S27, Receive the positioning information of the upper end of the virtual protocol line from the user terminal, and determine the protocol level slot with connection relationship as the target level slot based on the positioning information.

[0126] This disclosure allows users to adjust the connection between virtual protocol lines and protocol-level slots interactively (e.g., dragging), thereby determining the protocol priority strategy. This disclosure requires interactive functionality to monitor user actions on the virtual protocol lines in real time. When the user drags the upper endpoint of the virtual protocol line, its new position and connection status are recorded. Based on the connection status of the virtual protocol line and the protocol-level slot, the protocol priority strategy is determined.

[0127] This process determines which protocol level slot each virtual protocol line is currently connected to, thus identifying the protocol priority. It captures user dragging actions on the endpoints of virtual protocol lines, including the new coordinate positions. It then determines whether the endpoint of the virtual protocol line is within the range of a specific protocol level slot. If it is, the virtual protocol line is considered to have established a connection with that slot. The connected protocol level slot is then set as the target level slot for the virtual protocol line. For example, if a user drags the endpoint of a virtual protocol line into the "Medium Priority" slot, the target level slot for that virtual protocol line becomes "Medium Priority."

[0128] S28, obtain the protocol priority corresponding to the target level slot as the protocol priority strategy of the virtual protocol line.

[0129] Each virtual protocol line and its connected protocol sub-topology are assigned an explicit protocol priority policy. Each protocol level slot has a predefined protocol priority. The protocol priority of the virtual protocol line is obtained based on its target level slot. This obtained protocol priority is assigned to the virtual protocol line. The priority policy of the virtual protocol line is then passed to the protocol sub-topology it connects to. If the target level slot connected to the virtual protocol line is "high priority," then the protocol priority policy of that virtual protocol line and the protocol sub-topology below it is "high priority." This disclosure establishes an interactive mechanism that allows users to intuitively adjust protocol priority policies within the topology diagram. Virtual protocol lines connect the protocol sub-topology diagram to the virtual soft bus, and protocol level slots represent different priority levels. This design improves the readability and operability of the topology diagram, facilitating network management and optimization.

[0130] S3. Based on the user terminal's positioning information for each virtual protocol line and protocol sub-topology, generate a protocol priority strategy; based on the user terminal's partitioning information for each first device in the protocol sub-topology, generate a device priority strategy.

[0131] In network topology diagrams, to achieve more granular flow control and resource allocation, we need to set priority policies not only at the protocol level but also at the device level. By allowing users to partition devices in the protocol sub-topology diagram, we can generate device priority policies, thereby optimizing network performance.

[0132] The step of generating a device priority strategy based on the user's partitioning information of each first device in the protocol sub-topology diagram includes:

[0133] S31, generate multiple initial dividing lines based on the wiring trajectory of the first device in the protocol sub-topology diagram provided by the user terminal.

[0134] By analyzing the traces drawn by the user on the protocol sub-topology diagram, the system determines which devices the user wishes to group and assign different priorities to. The user draws a trace on the protocol sub-topology diagram using a mouse or touchscreen. This trace, from start to finish, passes through multiple devices the user wishes to group into the same priority group. The system captures the user-drawn trace and converts it into initial dividing lines. Each initial dividing line represents a device priority group. For example, if the user draws a curve from left to right on the protocol sub-topology diagram, passing through devices A, B, and C in sequence, the system recognizes this trace, generates an initial dividing line, and groups devices A, B, and C into one group.

[0135] S32, based on the device priority configuration information of each dividing line by the user terminal, the pixel value of the initial dividing line is updated to obtain the dividing information, and the device priority corresponds one-to-one with the pixel value.

[0136] The system assigns specific priorities to device priority groups, allowing users to specify a device priority for each dividing line (device group). Users select each initial dividing line on the interface and assign it a device priority, such as 1, 2, 3, etc., where priority 3 is greater than 1. The system maps each device priority to a unique pixel value (or color value). The pixel values ​​of the initial dividing lines are updated to reflect the corresponding device priorities. This pixel value update can be visually displayed on the interface; for example, different colors represent different priorities. For instance, if a user sets the previously generated initial dividing lines (containing devices A, B, and C) to "priority 3," the system updates the pixel values ​​of that dividing line to the specific color (e.g., red) representing "priority 3."

[0137] S33, Generate a device priority strategy for each of the first devices based on the device priority of the partitioning information.

[0138] Device priorities are applied to specific devices, and corresponding priority policies are generated for the devices included in a given boundary line based on the line's priority information. The system checks whether each device is included or covered by a boundary line. For devices included by a boundary line, the system assigns the boundary line's device priority to that device. The device is then associated with its priority policy and recorded in the system's configuration.

[0139] In other embodiments, for devices not included by any dividing line, the system may assign a default device priority or allow the user to configure it individually. For example, devices A, B, and C are assigned a "3-priority" policy. Device D, not included by any dividing line, is assigned a default "2-priority" policy by the system.

[0140] By drawing dividing lines directly on the topology map, users can easily prioritize multiple devices, enhancing the intuitiveness and efficiency of configuration. Users can flexibly adjust the position of the dividing lines and the devices they cover according to network requirements. Device priorities are represented using pixel values ​​(or color values), making it easy to visually display different priority groups on the interface. The system can indicate the current priority setting on devices or dividing lines using color or markers. Setting high priority for critical devices ensures the reliability and timeliness of their communication.

[0141] S4, based on the protocol priority policy and the device priority policy, the communication level of each of the first devices is obtained, and the protocol service component is updated according to the communication level.

[0142] In network systems, to optimize communication efficiency and resource allocation, it is necessary to comprehensively consider protocol priorities and device priorities to determine the overall communication level of each device. Then, based on these communication levels, the protocol service components are updated and adjusted accordingly.

[0143] The step of obtaining the communication level of each of the first devices based on the protocol priority policy and the device priority policy, and updating the protocol service component according to the communication level, includes:

[0144] S41, the protocol priority in the protocol priority strategy is used as the first priority of each first device, and the device priority in the device priority strategy is used as the second priority of each first device.

[0145] This disclosure assigns protocol priority and device priority to each first device separately to determine its communication level in subsequent steps. Protocol Priority (First Priority): A corresponding protocol priority is assigned to each first device according to a protocol priority policy. Protocol priorities may be based on different communication protocol types, such as TCP, UDP, HTTP, etc., and ranked according to their importance or urgency. Device Priority (Second Priority): A corresponding device priority is assigned to each first device according to a device priority policy. Device priorities may be adjusted by the user based on factors such as the device's importance, performance, and role.

[0146] S42, determine the first communication level of the first device according to the first priority, and determine the second communication level of the first device according to the second priority.

[0147] The first communication level refers to the level that needs to be prioritized. That is, when there is a conflict in the transmission order of data packets during communication, the protocol priority needs to be determined first. For example, if Device A has a high protocol priority and Device B has a medium protocol priority, then data from Device A will be transmitted first, followed by data from Device B.

[0148] The second communication level refers to the level that needs to make judgments after the protocol level. That is, when there is a conflict in the transmission order of data packets during communication, the protocol priority needs to be determined first. If the protocols are the same, then the device priority needs to be determined second. For example, if device A and device B both use protocol 1 to communicate, and device A has a priority of 1, while device B has a priority of 2, then data from device B will be transmitted first, followed by data from device A.

[0149] S43, based on the order of the first communication level and the second communication level, the communication level of each of the first devices is obtained, and the protocol service component is updated according to the communication level.

[0150] By comprehensively considering the importance of protocols and devices, the above approach ensures that critical protocols and devices are given priority. It achieves a comprehensive evaluation from protocol priority and device priority to communication level, and optimizes and updates protocol service components accordingly. This helps meet the communication needs of different devices and protocols.

[0151] Building upon the above embodiments, this disclosure introduces a data collection and analysis mechanism, which, combined with the previous prioritization strategy, forms a complete network optimization process. The collaboration between the interactive plugin and the coordination plugin enables real-time monitoring and dynamic optimization of network communication, improving system efficiency and reliability. The process also includes the following steps:

[0152] S5, each first device is pre-configured with an interaction plugin, which is used to count the first moment of the sent data packet and the second moment of the received data packet.

[0153] By pre-installing an interactive plugin on each first device, the time information of data packets sent and received by the device is recorded in real time, facilitating subsequent analysis and optimization. When the plugin detects that a device is sending a data packet, it records the timestamp of the sending. When the plugin detects that a device is receiving a data packet, it records the timestamp of the receiving.

[0154] S6, the interactive plugin generates a data interaction table, which contains data sending cells and data receiving cells.

[0155] See Figure 2 The collected transmitted and received data is organized into a structured format to facilitate subsequent data analysis and processing. The data interaction table is an information table recording the data sent and received by the device. Data transmission cells store information about the transmitted data packets, including data tags and transmission times. Data reception cells store information about the received data packets, including data tags and reception times. After detecting a transmission or reception event, the plugin stores the corresponding information in the appropriate cell.

[0156] S7, when the interactive plugin determines that the first device has sent a data packet, it extracts the data tag and data time of the sent data packet and stores them in the sending cell. When the interactive plugin receives a data packet from the first device, it extracts the data tag and data time of the received data packet and stores them in the receiving cell.

[0157] A data tag is an identifier used to uniquely identify a data packet; it can be the packet's sequence number, hash value, source / destination address, etc. When capturing a data packet, the plugin parses the packet header and extracts the data tag. It obtains an accurate timestamp using system time or Network Time Protocol (NTP). Send Event: Adds a row to the send cell, recording the data tag and send time. Receive Event: Adds a row to the receive cell, recording the data tag and receive time.

[0158] Example: Sending a data packet: Event: Device A sends data packet Packet1. Operation: The plugin extracts the data tag of Packet1: "Packet1". Gets the current timestamp: "2023-10-01 10:00:00". Records in the sent cell: Data tag: Packet1; Send time: 2023-10-01 10:00:00; Receiving a data packet: Event: Device A receives data packet Packet2. Operation: The plugin extracts the data tag of Packet2: "Packet2". Gets the current timestamp: "2023-10-01 10:00:05". Records in the received cell: Data tag: Packet2; Receive time: 2023-10-01 10:00:05.

[0159] S8, after a preset time interval, coordinates the interaction between the plugin and the interaction plugins of all first devices to extract the corresponding data interaction table, and generates the corresponding soft bus processing strategy based on the data interaction table, the first priority, and the second priority.

[0160] The system periodically collects communication data from all primary devices and, based on previously determined priorities, generates an optimized soft bus processing strategy to improve overall system performance. The coordination plugin, running on the central server or management node, is responsible for communicating with the interaction plugins of each device and collecting data. Every preset time interval (e.g., every 100 minutes), the coordination plugin sends a request to each primary device to obtain its data interaction table. The collected data interaction tables are then analyzed. Combining the previously determined first priority (protocol priority) and second priority (device priority), the actual performance of each device and protocol is evaluated, and further adjustments are made.

[0161] Wherein, after a preset time interval, the coordination plugin interacts with all the interaction plugins of the first device to extract the corresponding data interaction table, and generates a corresponding soft bus processing strategy based on the data interaction table, the first priority, and the second priority, including:

[0162] S81, the coordination plugin sorts all first devices once based on the first priority to obtain the first sequence, and then sorts the first devices with the same first priority again based on the second priority to obtain the second sequence after the two sortings.

[0163] In the previous steps, we collected data interaction tables on each first device through the interaction plugin. These tables record information about the data packets sent and received by the device. Now, in step S8, we need to generate corresponding soft bus processing strategies based on these data interaction tables and the previously determined first and second priorities to optimize the communication performance of the entire system.

[0164] This disclosure identifies which devices should be prioritized in the soft bus processing strategy by sorting the devices. The two-stage sorting ensures that device priority considers not only the importance of the protocol (first priority) but also the importance of the device itself (second priority). The sorting process involves first sorting according to the first priority of the protocol, and then sorting again according to the second priority of the device, resulting in a second sequence that includes all first-priority devices. In this second sequence, higher-priority devices are listed first, followed by lower-priority devices.

[0165] S82, the coordination plugin sequentially selects the data interaction tables of all first devices in the second sequence as the master data interaction table, and determines the associated data interaction tables of other first devices based on the data tags in the sending and receiving cells respectively.

[0166] This disclosure selects a device's interaction table as the master data interaction table, finds other devices (related devices) that have data interactions with that device, and then analyzes their communication together.

[0167] From the sorted second sequence, the interaction tables of devices are selected as master data interaction tables in descending order of priority. For each master data interaction table, the data labels in its sending and receiving cells are examined. Based on the same data labels, the corresponding data interaction tables in other first devices are found; these tables are the associated data interaction tables. Data interaction information between the master devices and associated devices is collected in preparation for subsequent analysis.

[0168] S83, based on the data time of the same data tag in the master data interaction table and the associated data interaction table, analyze the data time and generate the soft bus delay coefficient and the corresponding soft bus processing strategy.

[0169] By comparing the data timestamps of the same data tags between the master device and associated devices, performance metrics such as data transmission latency are calculated. A soft bus latency coefficient is generated: the latency coefficient between devices is calculated, providing a basis for optimizing the soft bus processing strategy. An optimization strategy is formulated: based on the analysis results, a corresponding soft bus processing strategy is generated to improve network performance.

[0170] The step of analyzing data times based on the same data tags in the master data interaction table and the associated data interaction table to generate a soft bus delay coefficient and a corresponding soft bus processing strategy includes:

[0171] S831, extract the data times with the same data labels in the master data interaction table and the related data interaction table, calculate the difference time.

[0172] Understandably, the data packet transmission delay is obtained by comparing the data timestamps of the same data tags between the master device and the associated device. Data records with the same data tags are found in the master data exchange table and the associated data exchange table. For each matching data tag, the send or receive time of the master device and the corresponding time of the associated device are extracted. If the master device sends and the associated device receives: the time difference equals the associated device's receive time minus the master device's send time; if the associated device sends and the master device receives, the time difference equals the master device's receive time minus the associated device's send time.

[0173] S832, calculates the comprehensive priority by multiplying the priority values ​​of the first priority and the second priority corresponding to the master data interaction table and the related data interaction table respectively. The first priority and the second priority of each master data interaction table and the related data interaction table correspond to preset priority values ​​respectively, and the priority is proportional to the priority value.

[0174] By comprehensively considering both the device's protocol priority and device priority, weights are assigned to subsequent calculations. Pre-set values ​​are assigned to each first and second priority level. Higher priority results in larger values.

[0175] For devices in the master data interaction table and related data interaction tables, calculate their overall priority separately. Overall priority = First priority value × Second priority value. For example, device B (related device), first priority: 3 (value 3), second priority: 5 (value 5), overall priority: 3 × 5 = 15.

[0176] S833, if the difference time is greater than or equal to the threshold time, then the data delay sub-coefficient is obtained by comprehensive calculation based on the difference time, the comprehensive priority of the master data interaction table, and the comprehensive priority of the associated data interaction table.

[0177] For data transmissions with significant delays, a delay sub-coefficient is calculated to reflect the combined impact of delay level and priority. A threshold is defined; the delay sub-coefficient is only calculated when the difference in time is greater than or equal to this threshold. For example, the threshold time is set to 5 seconds. For each calculated difference in time, it is determined whether it is greater than or equal to the threshold time.

[0178] S834 summarizes all data delay sub-coefficients to generate soft bus delay coefficients, and determines the recommended data transmission volume corresponding to the soft bus processing strategy based on the current data transmission volume of the soft bus.

[0179] The total delay coefficient is obtained by summing the delay sub-coefficients, reflecting the overall latency situation in the entire system. Based on the delay coefficient and the current data transmission volume, an optimization strategy is determined: providing a quantitative basis for the soft bus processing strategy and recommending a reasonable data transmission volume. All calculated data delay sub-coefficients are summed to obtain the soft bus delay coefficient. The current data transmission volume of the soft bus is statistically analyzed, such as the total data transmission volume per unit time. Based on the soft bus delay coefficient and the current data transmission volume, the recommended data transmission volume is calculated. Based on the calculation results, specific optimization measures are formulated, such as adjusting bandwidth allocation to improve the soft bus transmission throughput.

[0180] In the above embodiments, if the difference time is greater than or equal to the threshold time, a data delay sub-coefficient is obtained by comprehensive calculation based on the difference time, the comprehensive priority of the master data interaction table, and the comprehensive priority of the associated data interaction table, including:

[0181] The data delay sub-coefficient is calculated using the following formula.

[0182] in, The first in the master data interaction table Data delay sub-coefficient for each data label, The first in the master data interaction table Data time for each data label For the first in the related data interaction table Data time for each data label For time normalization, The first priority of the first device corresponding to the main data interaction table. The second priority of the first device corresponding to the main data interaction table. Main interaction weight, The first priority of the first device corresponding to the associated data interaction table. The second priority of the first device corresponding to the associated data interaction table. For associated interaction weights, Priority normalized value.

[0183] In the above formula, This represents the time difference; the larger the value, the larger the corresponding data delay sub-coefficient. This represents the priority calculation value corresponding to the master data interaction table. This represents the priority value calculated for the related data interaction table, and then through... and The overall priority is then calculated. The time normalization value, priority normalization value, main interaction weight, and related interaction weight can be preset by staff. The main interaction weight can be set to be greater than the related interaction weight.

[0184] After determining the data delay sub-coefficient, the corresponding first-order data in the master data interaction table and the associated data interaction table will be used to determine the delay sub-coefficient. Data tags are deleted and updated. Understandably, this solution will delete and update calculated data.

[0185] The calculation of the data delay sub-coefficient stops after determining that no data label exists in any data interaction table within the second sequence. It is understandable that this scheme requires calculation for all data labels.

[0186] The process of summarizing all data delay sub-coefficients to generate a soft bus delay coefficient, and determining the recommended data transmission volume corresponding to the soft bus processing strategy based on the current data transmission volume of the soft bus, includes:

[0187] The soft bus delay coefficient is calculated using the following formula.

[0188] in, This represents the delay factor for the soft bus. This represents the upper limit of the data delay sub-coefficient. It is a constant value. To recommend the amount of data to transfer, This represents the current data transfer volume of the soft bus. This is a preset value. Recommend weights for data transmission volume.

[0189] In the above formula, the soft bus latency coefficient is the sum of the data latency sub-coefficients of multiple data tags in the master data interaction table. It can be understood that the larger the soft bus latency coefficient, the greater the recommended data transmission volume is required. This allows for a larger data transmission volume on the soft bus, resulting in lower data transmission latency. The recommended weight for the data transmission volume can be preset by the staff.

[0190] The present invention also provides a readable storage medium storing a computer program, which, when executed by a processor, is used to implement the methods provided in the various embodiments described above.

[0191] The readable storage medium can be a computer storage medium or a communication medium. A communication medium includes any medium that facilitates the transfer of computer programs from one location to another. A computer storage medium can be any available medium accessible to a general-purpose or special-purpose computer. For example, a readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application-Specific Integrated Circuit (ASIC). Alternatively, the ASIC can be located in a user equipment. Of course, the processor and the readable storage medium can also exist as discrete components in a communication device. The readable storage medium can be a read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0192] The present invention also provides a program product including executable instructions stored in a readable storage medium. At least one processor of the device can read the executable instructions from the readable storage medium, and the at least one processor executes the executable instructions to cause the device to implement the methods provided in the various embodiments described above.

[0193] In the embodiments of the above-described device, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0194] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A multi-protocol converged soft bus communication data processing method, characterized in that, The method comprises the following steps: obtaining a first position of a first device, generating a device topology graph according to the first position, and loading a corresponding protocol service component according to the protocol identification of the first device to a soft bus; splitting the device topology graph based on the same protocol identification of the first device to obtain a protocol sub-topology graph corresponding to each protocol identification, and generating a virtual protocol line corresponding to the protocol sub-topology graph and connected to the soft bus; generating a protocol priority strategy according to the positioning information of each virtual protocol line and protocol sub-topology graph of the user terminal, and generating a device priority strategy according to the division information of each first device in the protocol sub-topology graph of the user terminal; obtaining the communication level of each first device based on the protocol priority strategy and the device priority strategy, and performing protocol update on the protocol service component according to the communication level.

2. The method of claim 1, wherein, The method comprises the following steps: traversing a preset component library according to the protocol identification of the first device to determine the protocol service component corresponding to the protocol identification of the first device as a target service component; loading the target service component to the soft bus, wherein the preset component library and the soft bus are one-to-one corresponding; The method comprises the following steps: classifying the first devices with the same protocol identification to obtain a device set corresponding to each protocol identification; determining the first devices outside the device set as split devices, deleting the split devices in the device topology graph to obtain an initial topology graph corresponding to the device set; performing merging processing on the initial topology graph to obtain a protocol sub-topology graph.

3. The method of claim 2, wherein, The method comprises the following steps: obtaining a first square area according to the first position of each first device in the initial topology graph; determining the other first square area closest to the first square area as a second square area in each preset direction with the first square area as the center, wherein the preset direction includes vertical direction and horizontal direction, the vertical direction includes upward direction and downward direction, and the horizontal direction includes left direction and right direction; obtaining distance information between the first square area and the second square area, and taking the corresponding second square area as a third square area when the distance information is greater than a preset distance; determining the area between the first square area and the third square area as a clipping area; performing clipping processing on the clipping area to obtain a protocol sub-topology graph.

4. The method of claim 3, wherein, The method comprises the following steps: determining the relative positional relationship between the third square area and the first square area; when the relative positional relationship is upward direction, determining the upper edge line of the first square area and performing extension processing to obtain a first clipping line, and determining the lower edge line of the third square area and performing extension processing to obtain a second clipping line; In the case that the relative position relationship is the lower position, a lower edge line of the first square region is determined and extended to obtain a first cutting line, and an upper edge line of the third square region is determined and extended to obtain a second cutting line; In the case that the relative position relationship is the left position, a left edge line of the first square region is determined and extended to obtain a first cutting line, and a right edge line of the third square region is determined and extended to obtain a second cutting line; In the case that the relative position relationship is the right position, a right edge line of the first square region is determined and extended to obtain a first cutting line, and a left edge line of the third square region is determined and extended to obtain a second cutting line; An area between the first cutting line and the second cutting line is taken as a cutting area.

5. The method of claim 1, wherein, The generating of the virtual protocol line corresponding to the protocol sub-topology graph and connected with the soft bus comprises: A horizontal virtual soft bus corresponding to the soft bus is constructed, and protocol level slots are generated in turn under the horizontal virtual soft bus according to the order of protocol priority levels, the protocol level slots corresponding to the protocol priority levels one by one; A virtual protocol line corresponding to the protocol sub-topology graph is generated, and the protocol sub-topology graph is connected with a lower end point of the virtual protocol line; The generating of the protocol priority strategy according to the positioning information of the user end to each virtual protocol line and protocol sub-topology graph comprises: Positioning information of the user end to an upper end point of the virtual protocol line is received, and a protocol level slot having a connection relationship is determined as a target level slot according to the positioning information; A protocol priority corresponding to the target level slot is taken as a protocol priority strategy of the virtual protocol line; The generating of the device priority strategy according to the division information of the user end to each first device in the protocol sub-topology graph comprises: A plurality of initial division lines are generated according to a stringing track of the corresponding first device in the protocol sub-topology graph by the user end; Pixel value updating is performed on the initial division lines to obtain division information based on device priority configuration information of each division line by the user end, the device priority corresponding to the pixel value one by one; Device priority strategies of each first device are generated according to the device priority of the division information.

6. The method of claim 5, wherein, The obtaining of the communication level of each first device based on the protocol priority strategy and the device priority strategy, and the protocol updating of the protocol service component according to the communication level comprises: A protocol priority in the protocol priority strategy is taken as a first priority of each first device, and a device priority in the device priority strategy is taken as a second priority of each first device; A first communication level of the first device is determined according to the first priority, and a second communication level of the first device is determined according to the second priority; A communication level of each first device is obtained based on the order of the first communication level and the second communication level, and the protocol service component is updated according to the communication level.

7. The method of claim 6, wherein, Further comprising: pre-configuring an interaction plug-in for each first device, the interaction plug-in being used to record a first time of sending a data packet and a second time of receiving a data packet; the interaction plug-in generating a data interaction table, the data interaction table having a data sending cell and a data receiving cell; the interaction plug-in storing a data tag and a data time of the sent data packet into the sending cell when judging that the first device sends a data packet, and storing a data tag and a data time of the received data packet into the receiving cell when receiving the data packet sent by the first device; after a preset time interval, the coordination plug-in interacts with the interaction plug-ins of all the first devices to extract corresponding data interaction tables, and generates a corresponding soft bus processing strategy based on the data interaction tables, the first priority and the second priority.

8. The method of claim 7, wherein after the preset time interval, the coordination plug-in interacts with the interaction plug-ins of all the first devices to extract corresponding data interaction tables, and generates a corresponding soft bus processing strategy based on the data interaction tables, the first priority and the second priority, including: the coordination plug-in sorts all the first devices based on the first priority to obtain a first sequence, and sorts the first devices with the same first priority again based on the second priority to obtain a second sequence after the twice sorting; the coordination plug-in selects the data interaction tables of all the first devices in the second sequence as main data interaction tables in turn, and determines associated data interaction tables of other first devices according to the data tags respectively in the sending cells and the receiving cells; based on the data times of the same data tags in the main data interaction tables and the associated data interaction tables, the soft bus delay coefficient and the corresponding soft bus processing strategy are generated.

9. The method of claim 8, wherein the based on the data times of the same data tags in the main data interaction tables and the associated data interaction tables, the soft bus delay coefficient and the corresponding soft bus processing strategy are generated, including: the data times of the same data tags in the main data interaction tables and the associated data interaction tables are extracted for calculation to obtain a difference time; a comprehensive priority is calculated by multiplying the priority values of the first priority and the second priority corresponding to the main data interaction table and the associated data interaction table respectively, the first priority and the second priority of each main data interaction table and associated data interaction table respectively corresponding to a preset priority value, the priority being directly proportional to the priority value; if the difference time is greater than or equal to a threshold time, a data delay sub-coefficient is obtained by comprehensive calculation based on the difference time, the comprehensive priority of the main data interaction table and the comprehensive priority of the associated data interaction table; all the data delay sub-coefficients are summarized to generate a soft bus delay coefficient, and a corresponding recommended data transmission amount in the soft bus processing strategy is determined based on a current data transmission amount of the soft bus.

10. The method of claim 9, wherein the if the difference time is greater than or equal to a threshold time, a data delay sub-coefficient is obtained by comprehensive calculation based on the difference time, the comprehensive priority of the main data interaction table and the comprehensive priority of the associated data interaction table, including: The data delay sub-coefficients are calculated by the following formula, wherein, is a data delay sub-coefficient of a data tag of the main data interaction table, is a data tag of the main data interaction table, is a data tag of the main data interaction table, is a data tag of the main data interaction table, is a data tag of the main data interaction table, is a data tag of the main data interaction table, is a time normalization value, is a first priority of the first device corresponding to the main data interaction table, is a second priority of the first device corresponding to the main data interaction table, is a main interaction weight, is a first priority of the first device corresponding to the main data interaction table, is a second priority of the first device corresponding to the main data interaction table, is an associated interaction weight, is a priority normalization value; After judging the data delay sub-coefficients, the first data tag corresponding to the main data interaction table and the associated data interaction table is deleted and updated. ​ The calculation of the data delay sub-coefficients is stopped after it is judged that there is no data tag in all data interaction tables in the second sequence; The soft bus delay coefficients are generated by summarizing all the data delay sub-coefficients, and the recommended data transmission amount corresponding to the soft bus processing strategy is determined based on the current data transmission amount of the soft bus, including: The soft bus delay coefficients are calculated by the following formula, wherein, is a soft bus delay coefficient, is an upper limit value of a data delay sub-coefficient, is a constant value, is a recommended data transmission amount, is a current data transmission amount of the soft bus, is a preset value, is a data transmission amount recommendation weight.

Images