Synchronous distributed collaborative network heartbeat packet strength real-time management system and method

Abstract

The invention discloses a synchronous distributed collaborative network heartbeat packet strength real-time management system and method. The system comprises a heterogeneous interconnection module, a stepping management module and a stepping period monitoring module. The heterogeneous interconnection module is used for receiving a scheduling frame during data downlink and sending the scheduling frame to the stepping management module and the stepping period monitoring module; the stepping information extraction module is used for receiving data frames, extracting stepping information and sending the stepping information to the stepping management module and the stepping period monitoring module; the stepping management module is used for analyzing the number of network stepping cycles and clearing a historical stepping offset value of a historical stepping cycle; the controller is also used for adjusting the current stepping offset value of the current stepping period according to the stepping information and the equipment timer; the step period monitoring module is used for adding one to the count when the scheduling frame is received each time; the counting is reset when the stepping information in the data frame is received; and when the count is greater than or equal to the preset timeout number, determining that the module sending the data is offline. The method can meet the requirements of a strong real-time and high-certainty system.

Description

Technical Field

[0001] This invention belongs to the field of communications, specifically relating to a real-time management system and method for heartbeat packet strength in a synchronous distributed cooperative network. Background Technology

[0002] Heartbeat packets are a core technology in the communications field used for connection keep-alive, status detection, and anomaly warning. Their function is to verify link connectivity between software modules and confirm that the software is functioning normally. They play an irreplaceable role in many fields such as internet services, industrial control, automotive electronics, aerospace, and the Internet of Things. Typically, heartbeat packets are applied in scenarios with low real-time requirements (second-level), primarily targeting the TCP / IP protocol (Transmission Control Protocol / Internet Protocol), using a local clock for timing, and often only enabling one-to-one heartbeat monitoring.

[0003] Modern complex digital systems involve a large amount of hardware and software. The interconnections between these hardware and software are extremely complex, and the amount of system data has also increased dramatically. This application scenario poses a significant challenge to the system's real-time performance and determinism. In high real-time scenarios, traditional heartbeat management mechanisms are ill-suited to one-to-many and many-to-one requirements; heartbeats relying on local clocks add extra requirements for device synchronization. Furthermore, in high real-time scenarios, the heartbeat cycle time is significantly shortened, and as the system scales up, the competition for network bandwidth becomes substantial. These mechanisms are unable to meet the rigid requirements of high real-time systems for "timing consistency, determinism, and low overhead." Summary of the Invention

[0004] To address the aforementioned problems in the prior art, this invention provides a real-time management system and method for a synchronous distributed collaborative network heartbeat packet strength.

[0005] The technical problem to be solved by this invention is achieved through the following technical solution: In a first aspect, the present invention provides a real-time management system for heartbeat packet strength in a synchronous distributed collaborative network, the system comprising: a heterogeneous interconnection module, a step management module, and a step cycle monitoring module; The heterogeneous interconnection module is used to receive scheduling frames sent by the synchronous distributed cooperative network during data downlink, and send the scheduling frames to the step management module and the step cycle monitoring module; it is also used to receive data frames sent by the synchronous distributed cooperative network, extract step information from the data frames, and send the step information to the step cycle monitoring module. The step management module is used to parse the number of network step cycles in the received scheduling frame and clear the historical step offset value of the historical step cycle; it is also used to adjust the current step offset value of the current step cycle according to the device timer. The step cycle monitoring module is used to increment the count by one each time the scheduling frame is received; and to reset the count to zero when step information in the data frame is received; and to determine that the data sending module is offline when the count is greater than or equal to a preset timeout number.

[0006] Optionally, the system further includes: a software / algorithm encapsulation module; The software / algorithm encapsulation module is used to send the data to be uploaded to the heterogeneous interconnect module during data uplink. Optionally, the heterogeneous interconnection module is further configured to acquire the step offset value of the step management module when the data is uplinked; and to frame the data to be uplinked based on the step offset value and the data to be uplinked, and send the framed data to be uplinked to the synchronous distributed cooperative network to complete the data uplink.

[0007] Optionally, the heterogeneous interconnection module may also send the business data to the algorithm / software encapsulation module; The software / algorithm encapsulation module is also used to process the business data.

[0008] Optionally, the software / algorithm encapsulation module is further configured to encapsulate the algorithm provided by the user to obtain an encapsulated module, and use the encapsulated module as the module for sending data.

[0009] Optionally, the scheduling frames and data frames issued by the synchronous distributed cooperative network are obtained based on the encapsulated module.

[0010] Optionally, the step offset value is generated by a device timer.

[0011] Optionally, the system further includes: a synchronous distributed cooperative soft bus module; The synchronous distributed collaborative soft bus module is used to control the start and stop of the heterogeneous interconnection module, the step management module, the step cycle monitoring module, and the software / algorithm encapsulation module.

[0012] Secondly, the present invention provides a real-time management method for heartbeat packet strength in a synchronous distributed cooperative network, applied to the real-time management system for heartbeat packet strength in a synchronous distributed cooperative network described in the first aspect, wherein the system includes: a heterogeneous interconnection module, a step management module, and a step cycle monitoring module; the method includes: During data downlink, the heterogeneous interconnection module receives the scheduling frame issued by the synchronous distributed cooperative network and sends the scheduling frame to the step management module and the step cycle monitoring module. The heterogeneous interconnection module receives data frames sent by the synchronous distributed collaborative network, extracts step information and service data from the data frames, and sends the step information to the step cycle monitoring module. The step management module parses the number of network step cycles in the received scheduling frame and clears the historical step offset value of the historical step cycle to zero. The step management module adjusts the current step offset value of the current step cycle according to the device timer; The step cycle monitoring module increments the counter by one each time it receives the scheduling frame, and resets the counter to zero when it receives step information in the data frame. When the count is greater than or equal to a preset timeout number, the module that sends data is determined to be offline.

[0013] The technical solutions provided by the embodiments of the present invention may include the following beneficial effects: In the above technical solution, this invention deeply integrates heartbeat management with communication through a synchronous distributed collaborative network, reducing fault detection latency and solving the millisecond-level lag problem of traditional heartbeat packets. This meets the requirements of highly real-time and deterministic systems. Furthermore, it eliminates the need for precise alignment with local device clocks; the global clock is provided uniformly by the synchronous distributed collaborative network, eliminating the need for extensive cross-device time synchronization operations. The heartbeat packet is integrated into the data frame, consuming no additional bandwidth and eliminating the need for repeated heartbeat mechanism establishment, significantly improving system scalability. The heartbeat packet management logic only involves the step cycle timeout number and the step cycle timeout duration. When migrating the system software to other devices, the heartbeat packet management logic does not need to be modified. It supports both a heartbeat management mechanism "based solely on the step cycle number" and a hybrid judgment mode "combining the step cycle number and step offset value," allowing for flexible adaptation to different business scenarios through configuration of the timeout number and timeout duration.

[0014] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the structure of a synchronous distributed collaborative network heartbeat packet strength real-time management system provided in an embodiment of the present invention; Figure 2 This is a schematic diagram of the configuration of a scheduling frame provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of a data frame configuration provided in an embodiment of the present invention; Figure 4This is a schematic diagram of the operation of a synchronous distributed collaborative network heartbeat packet strength real-time management system provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of heartbeat packet management based on step cycle in a single device with multiple software applications, provided by an embodiment of the present invention. Figure 6 This is a flowchart of a real-time management method for heartbeat packet strength in a synchronous distributed collaborative network provided by an embodiment of the present invention. Detailed Implementation

[0016] To facilitate understanding of the present invention, a brief description of the prior art and the inventive concept of the present invention will be provided first.

[0017] Existing technologies typically rely on heartbeat packets provided by software. Data is transmitted via non-real-time protocols such as TCP / IP, and connection status is determined based on a preset system time. This is suitable for systems with low real-time requirements. For example, one invention patent proposes a heartbeat packet detection method, device, equipment, and storage medium. This invention patent uses heartbeat packets sent by the client as its core. The server passively parses the heartbeat packets to obtain the sending cycle and stores the heartbeat packet information (reception time, client identity) in a time-priority queue. It generates detection notifications based on the heartbeat cycle and polls the queue using a single thread or a small number of threads to determine whether a heartbeat packet has been received before the next detection time, thereby determining the connection status. Another invention proposes a heartbeat packet communication method, testing system, terminal equipment, and storage medium. This invention patent uses a host computer to autonomously generate heartbeat packets, carrying identification codes for each node in the path (host computer, intermediate communication nodes, and device under test). A mechanism of "sending → appending identifiers → receiving verification" is used to determine the link status, thereby locating link problems.

[0018] It's clear that existing technologies all rely on precise alignment of the device's local clock with a reference clock. For example, suppose device A needs to detect the heartbeat of device B. If device A's local clock is 12:00, then device B's local clock must be precisely aligned to 12:00. This not only requires extensive time synchronization to ensure minimal clock deviation between A and B, but also leads to a linear increase in resource consumption as the system scales up, especially in one-to-many scenarios involving system synchronization issues, resulting in increased development resource consumption.

[0019] Specifically, existing technologies rely on client heartbeat cycles or timeout periods, requiring additional retransmissions for verification (causing millisecond-level delays in deterministic systems), resulting in inherent latency and making fault detection cycles difficult to adapt to deterministic systems. Furthermore, using client heartbeat cycles or local clocks as a benchmark makes it difficult to achieve a unified time reference among multiple clients / nodes, potentially leading to deviations in heartbeat packet reception and judgment under strong real-time conditions. In one-to-many communication scenarios, multiple queues or multi-threaded polling are needed to repeatedly establish the heartbeat management mechanism. As the number of nodes increases, thread / bandwidth resource consumption grows linearly, and the complex interconnections make unified management difficult. Therefore, this invention proposes a synchronous distributed collaborative network heartbeat packet strong real-time management system to solve these technical problems.

[0020] Synchronous distributed cooperative networks / buses are a type of strongly real-time, deterministic network. Their characteristic is that the entire system operates based on a pre-defined stepping cycle. The system's global clock is generated by a single device, and all devices connected to the synchronous distributed cooperative network share a single global clock based on "stepping clock + number of stepping cycles + step offset value," without needing to synchronize the absolute time of all local clocks within the system. The data frame header of a synchronous distributed cooperative network contains the number of stepping cycles and the step offset. Combined with the synchronous distributed cooperative soft bus (a software component), other computer software can read these values ​​and perform time conversion based on the pre-defined stepping cycle.

[0021] The heartbeat management method based on the step cycle of a synchronous distributed cooperative network uses the number of step cycles and the step offset carried in the data frames of the synchronous distributed cooperative network to manage heartbeat packets. The heartbeat packets are generated by the network itself, not by software, and are directly included in the communication. Relying on a globally unified scheduling clock, the heartbeat is deeply bound to business data and node coordination timing, fundamentally solving the core shortcomings of traditional methods. Under this mechanism, the software can inherently manage heartbeat packets when receiving data, eliminating the need for an additional independent heartbeat packet management mechanism. In one-to-many scenarios, the system overhead is lower, and real-time performance can reach the microsecond level.

[0022] Figure 1 This is a schematic diagram of the structure of a synchronous distributed collaborative network heartbeat packet strength real-time management system provided in an embodiment of the present invention, as shown below. Figure 1 As shown, the system includes: a heterogeneous interconnection module, a step management module, and a step cycle monitoring module; The heterogeneous interconnection module is used to receive scheduling frames sent by the synchronous distributed cooperative network during downlink data transmission, and send the scheduling frames to the step management module and the step cycle monitoring module; it is also used to receive data frames sent by the synchronous distributed cooperative network, extract step information from the data frames, and send the step information to the step cycle monitoring module. The step management module is used to parse the network step cycle number in the received scheduling frame and clear the historical step offset value of the historical step cycle; it is also used to adjust the current step offset value of the current step cycle according to the device timer. The step cycle monitoring module is used to increment the counter by one each time a scheduling frame is received; and to reset the counter to zero when step information is received in a data frame; it is also used to determine that the data sending module is offline when the counter is greater than or equal to a preset timeout number.

[0023] It is understood that this invention implements the heartbeat packet function based on the monitoring of the step cycle count. Since the step cycle count itself is generated and provided to all devices / software modules by a synchronous distributed cooperative network, it is unified across the entire network. Furthermore, once communication is established, the step cycle count carried in the synchronous distributed cooperative network data frame itself implements the heartbeat packet function and can be used across modules. In addition, the step cycle is implemented by a single global clock of the synchronous distributed cooperative network, independent of the device's local clock; the step offset value is generated by the device timer (soft bus / device's own clock), and the count is reset each cycle. Its accuracy depends only on the device's clock source, thus eliminating the need for multiple time synchronizations across devices.

[0024] For example, in a communication scenario, data receiving module B needs to receive data generated by data sending module A. If no data is received from A for several cycles, it can be determined that A is offline. In a one-to-many situation, the data frame sent by A is unique and is synchronously fanned out to multiple modules. Other modules only need to monitor the number of steps in the frame to implement a heartbeat management mechanism, without each module needing to establish a bidirectional heartbeat packet management mechanism with A. For example, when data receiving modules B1, B2, and B3 are started, A only sends data to the synchronous distributed cooperative network. The synchronous distributed cooperative network fans out the same data to each device. B1, B2, and B3 can directly monitor the number of steps and implement a heartbeat management mechanism without needing to establish three links from A to B1, A to B2, and A to B3, and thus three sets of heartbeat packet management mechanisms.

[0025] The system also includes: a software / algorithm encapsulation module; The software / algorithm encapsulation module is used to send the data to be uploaded to the heterogeneous interconnect module during data uplink. The heterogeneous interconnect module is also used to obtain the step offset value of the step management module when data is uplinked; it is also used to frame the data according to the step offset value and the data to be uplinked, and send the framed data to be uplinked to the synchronous distributed cooperative network to complete the data uplink.

[0026] Optionally, the heterogeneous interconnect module may also send business data to the algorithm / software encapsulation module; The software / algorithm encapsulation module is also used for processing business data.

[0027] Understandably, in the data uplink process, the heterogeneous interconnect module provides data to the synchronous distributed collaborative network, where network hardware performs unified framing. The software / algorithm encapsulation module sends the data to be uplinked to the heterogeneous interconnect module; the heterogeneous interconnect module obtains the step offset value from the step management module; the heterogeneous interconnect module integrates key information such as the data to be uplinked and the step offset value to perform framing; the heterogeneous interconnect module sends the framed data to be uplinked to the synchronous distributed collaborative network, where the network globally manages the number of step cycles for the data frame. Furthermore, business data is sent to the corresponding algorithm / software encapsulation module, where the encapsulated module decides how to process it to achieve the path service from business data to the user algorithm.

[0028] Optionally, the software / algorithm encapsulation module is also used to encapsulate the algorithm provided by the user to obtain the encapsulated module, and use the encapsulated module as the module for sending data.

[0029] Specifically, the software / algorithm encapsulation module encapsulates the user-provided algorithm through an internal synchronous distributed collaborative network unified encapsulation module, resulting in the encapsulated module.

[0030] Optionally, the data frames distributed by the synchronous distributed collaborative network are obtained from the encapsulated modules.

[0031] Understandably, during development, users encapsulate algorithms using algorithm libraries / software encapsulation modules and set the number of monitoring steps in the class template. The default timeout is two steps, but users can set a preset timeout number based on the specific needs of the algorithm to monitor the offline status of the encapsulated module.

[0032] Optionally, the system also includes: a synchronous distributed cooperative soft bus module; The synchronous distributed collaborative soft bus module is used to control the start and stop of the heterogeneous interconnection module, step management module, step cycle monitoring module, and software / algorithm encapsulation module.

[0033] When the system is working normally, the synchronous distributed cooperative soft bus enables the start and stop of each software module, receives synchronous distributed cooperative network scheduling frames and data frames, manages the time (network step cycle, number of step cycles and step offset value) provided by the synchronous distributed cooperative network, generates step offset value based on the device clock, and realizes synchronous distributed cooperative network data transmission and reception based on the data provided by the software modules.

[0034] When a software module sends data, it notifies the soft bus stepping management module. Upon receiving the notification, the soft bus stepping management module provides the heterogeneous interconnect module with the step offset value generated by the device timer. After obtaining the key information, the heterogeneous interconnect module frames and uploads the data to the synchronous distributed cooperative network. The synchronous distributed cooperative network itself manages the number of stepping cycles for the uplink data.

[0035] Downlink data transmission includes data frames and scheduling frames. Upon receiving a scheduling frame, the heterogeneous interconnect module notifies the step management module. The latter updates the current network step count based on the step count contained in the scheduling frame and resets its own clock count (step offset value) to zero before restarting the count. For received data frames, the heterogeneous interconnect module extracts the step offset value and step count and provides them to the step management module. Subsequently, it notifies the algorithm / software encapsulation module to read the data. During data reception, the step cycle monitoring module continuously obtains the current network step count and step offset value. According to the usage strategy, it detects the step count, offset value, or the offset time generated by restoring both using the formula (offset time = step count × step count + offset value). Upon receiving data, the step cycle monitoring count restarts from zero, incrementing by one each time the network step count is updated. When this value is greater than or equal to the set step cycle timeout, the step cycle monitoring module considers the software module sending data to be offline. This process is entirely completed locally without the need for additional heartbeat packets.

[0036] In one implementation, the heartbeat packet implementation uses only the network's step count and does not detect offset values. In strong real-time mode, a step count of 20 microseconds to one millisecond is used. Figure 2 This is a schematic diagram of the configuration of a scheduling frame provided in an embodiment of the present invention, such as... Figure 2 As shown, time-triggered scheduling frames are unified to a single global clock in the synchronous distributed cooperative network. Each scheduling frame contains a step count and a step offset value as a "system heartbeat." The synchronous distributed cooperative network scheduling frame must contain at least the StepBeat step count and the StepOffset step offset value, where the step offset value is in microseconds. The StepTime step count is the network step count, also in microseconds, representing the synchronous distributed cooperative network's operating cycle. Figure 3 This is a schematic diagram of a data frame configuration provided in an embodiment of the present invention, such as... Figure 3 As shown, the synchronous distributed cooperative network data frame includes the StepBeat step cycle number and the StepOffset step offset value, where the step offset value is in microseconds. In the heartbeat packet-strength real-time management mechanism, the step cycle number and step offset value are extracted from the data frame protocol.

[0037] In one implementation, Figure 4 This is a schematic diagram of the operation of a synchronous distributed collaborative network heartbeat packet strength real-time management system provided in an embodiment of the present invention, as shown below. Figure 4As shown, at the beginning of each synchronous distributed collaborative network stepping cycle, the network sends a scheduling frame. The heterogeneous interconnection module receives the scheduling frame, obtains the network stepping cycle count, and provides it to the stepping management module. The stepping management module then provides the network stepping cycle count to all stepping monitoring modules. When the heterogeneous interconnection module receives a data frame, it reads the data frame's stepping cycle and provides it to the stepping management module. Subsequently, the stepping management module provides the data frame's stepping cycle to the stepping monitoring module, which stores the latest data frame's stepping cycle. The stepping monitoring module receives the network stepping cycle and the data frame's stepping cycle. During each network stepping cycle update, it compares the stored data frame's stepping cycle with the previous network stepping cycle. If they are the same, the stepping cycle monitoring count is reset to zero. If the data frame's stepping cycle is less than the network stepping cycle, the stepping cycle monitoring count is incremented by one, and the stepping cycle monitoring count is compared with the stepping timeout count. If the stepping cycle monitoring count is greater than or equal to the stepping cycle monitoring count, the stepping monitoring module notifies the synchronous distributed collaborative network unified encapsulation module. This enables autonomous monitoring of heartbeat packets.

[0038] In one implementation, Figure 5 This is a schematic diagram illustrating heartbeat packet management based on step-cycle in a single device with multiple software implementations, as provided in an embodiment of the present invention. Figure 5 As shown, in a single device with multiple software components, the step management module autonomously provides the data frame stepping period and network stepping period to each software / algorithm encapsulation module. Each software / algorithm encapsulation module only needs to register one stepping period monitoring number to autonomously monitor heartbeat packets. In a many-to-one scenario, multiple stepping monitoring modules can be established within a single encapsulation module to monitor the status of multiple sets of data sending software modules, thereby achieving heartbeat packet management.

[0039] Figure 6 This is a flowchart of a real-time management method for heartbeat packet strength in a synchronous distributed collaborative network provided by an embodiment of the present invention, such as... Figure 6 As shown, this method is applied to a real-time management system for heartbeat packet strength in a synchronous distributed cooperative network. The system includes: a heterogeneous interconnection module, a step management module, and a step cycle monitoring module. The method includes: S601. When data is downlinked, the heterogeneous interconnection module receives the scheduling frame sent by the synchronous distributed cooperative network and sends the scheduling frame to the step management module and the step cycle monitoring module. S602, the heterogeneous interconnection module receives data frames sent by the synchronous distributed cooperative network, extracts step information from the data frames, and sends the step information to the step cycle monitoring module; S603. The step management module parses the number of network step cycles in the received scheduling frame and clears the historical step offset value of the historical step cycle. S604. The step management module adjusts the current step offset value of the current step cycle according to the device timer. S605 The step cycle monitoring module increments the counter by one each time a scheduling frame is received; and resets the counter to zero when step information is received in a data frame. S606. When the count is greater than or equal to the preset timeout number, the module that sends data is determined to be offline.

[0040] In the above technical solution, this invention deeply integrates heartbeat management with communication through a synchronous distributed collaborative network, reducing fault detection latency and solving the millisecond-level lag problem of traditional heartbeat packets. This meets the requirements of highly real-time and deterministic systems. Furthermore, it eliminates the need for precise alignment with local device clocks; the global clock is provided uniformly by the synchronous distributed collaborative network, eliminating the need for extensive cross-device time synchronization operations. The heartbeat packet is integrated into the data frame, consuming no additional bandwidth and eliminating the need for repeated heartbeat mechanism establishment, significantly improving system scalability. The heartbeat packet management logic only involves the step cycle timeout number and the step cycle timeout duration. When migrating the system software to other devices, the heartbeat packet management logic does not need to be modified. It supports both a heartbeat management mechanism "based solely on the step cycle number" and a hybrid judgment mode "combining the step cycle number and step offset value," allowing for flexible adaptation to different business scenarios through configuration of the timeout number and timeout duration.

[0041] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described in this specification.

[0042] Although the invention has been described herein in conjunction with various embodiments, those skilled in the art will understand and implement other variations of the disclosed embodiments by reviewing the accompanying drawings and the disclosure in carrying out the claimed invention. In the description of the invention, the word "comprising" does not exclude other components or steps, "a" or "an" does not exclude a plurality, and "a plurality" means two or more, unless otherwise explicitly specified. Furthermore, while different embodiments may describe certain measures, this does not mean that these measures cannot be combined to produce good results.

[0043] The above description, in conjunction with specific preferred embodiments, provides a further detailed explanation of the present invention. It should not be construed that the specific implementation of the present invention is limited to these descriptions. For those skilled in the art, various simple deductions or substitutions can be made without departing from the concept of the present invention, and all such modifications and substitutions should be considered within the scope of protection of the present invention.

Claims

1. A real-time management system for heartbeat packet strength in a synchronous distributed collaborative network, characterized in that, The system includes: a heterogeneous interconnection module, a step management module, and a step cycle monitoring module; The heterogeneous interconnection module is used to receive scheduling frames sent by the synchronous distributed cooperative network during data downlink, and send the scheduling frames to the step management module and the step cycle monitoring module; it is also used to receive data frames sent by the synchronous distributed cooperative network, extract step information from the data frames, and send the step information to the step cycle monitoring module. The step management module is used to parse the number of network step cycles in the received scheduling frame and clear the historical step offset value of the historical step cycle; it is also used to adjust the current step offset value of the current step cycle according to the device timer. The step cycle monitoring module is used to increment the count by one each time the scheduling frame is received; and to reset the count to zero when step information in the data frame is received; and to determine that the data sending module is offline when the count is greater than or equal to a preset timeout number.

2. The synchronous distributed collaborative network heartbeat packet strength real-time management system according to claim 1, characterized in that, The system also includes: a software / algorithm encapsulation module; The software / algorithm encapsulation module is used to send the data to be uploaded to the heterogeneous interconnect module when data is being uploaded.

3. The synchronous distributed collaborative network heartbeat packet strength real-time management system according to claim 2, characterized in that, The heterogeneous interconnection module is also used to obtain the step offset value of the step management module when the data is uplinked; it is also used to frame the data according to the step offset value and the data to be uplinked, and send the framed data to be uplinked to the synchronous distributed cooperative network to complete the data uplink.

4. The synchronous distributed collaborative network heartbeat packet strength real-time management system according to claim 3, characterized in that, The heterogeneous interconnection module is also used to send the business data to the algorithm / software encapsulation module; The software / algorithm encapsulation module is also used to process the business data.

5. The real-time management system for heartbeat packet strength in a synchronous distributed collaborative network according to claim 1, characterized in that, The software / algorithm encapsulation module is also used to encapsulate the algorithm provided by the user to obtain an encapsulated module, and to use the encapsulated module as the module for sending data.

6. The real-time management system for heartbeat packet strength in a synchronous distributed collaborative network according to claim 5, characterized in that, The data frames issued by the synchronous distributed collaborative network are obtained based on the encapsulated modules.

7. The synchronous distributed cooperative network heartbeat packet strength real-time management system according to claim 2, characterized in that, The system also includes: a synchronous distributed collaborative soft bus module; The synchronous distributed collaborative soft bus module is used to control the start and stop of the heterogeneous interconnection module, the step management module, the step cycle monitoring module, and the software / algorithm encapsulation module.

8. A real-time management method for strong heartbeat packets in a synchronous distributed cooperative network, characterized in that, The method is applied to the synchronous distributed cooperative network heartbeat packet strength real-time management system according to claims 1-7, wherein the system comprises: a heterogeneous interconnection module, a step management module, and a step cycle monitoring module; the method comprises: During data downlink, the heterogeneous interconnection module receives the scheduling frame issued by the synchronous distributed cooperative network and sends the scheduling frame to the step management module and the step cycle monitoring module. The heterogeneous interconnection module receives data frames sent by the synchronous distributed cooperative network, extracts step information from the data frames, and sends the step information to the step cycle monitoring module. The step management module parses the number of network step cycles in the received scheduling frame and clears the historical step offset value of the historical step cycle to zero. The step management module adjusts the current step offset value of the current step cycle according to the device timer; The step cycle monitoring module increments the counter by one each time it receives the scheduling frame, and resets the counter to zero when it receives step information in the data frame. When the count is greater than or equal to a preset timeout number, the module that sends data is determined to be offline.

Images