Multi-terminal information equipment collaborative debugging and operation method

Abstract

The present application relates to the technical field of cloud edge collaboration and device operation and maintenance, and specifically discloses a multi-terminal informationization device collaborative debugging and operation and maintenance method. The technical scheme of the present application configures a protocol adaptation interface for terminal devices of different communication protocol types to complete bidirectional data format conversion, and acquires real-time running state data with time stamps based on time synchronization parameters to construct a device state label. After determining a target terminal device set in combination with a cloud debugging task, a collaborative state view is constructed according to a unified time sequence reference. When responding to a debugging operation instruction, a sending time stamp is recorded and compared with feedback running state data in terms of time sequence, thereby solving the problems of information silos caused by non-uniform heterogeneous terminal protocols, lack of collaborative scheduling of multi-terminal operation and maintenance, non-synchronized state data time, and delayed fault location, and improving the real-time performance, consistency and diagnostic accuracy of multi-terminal collaborative debugging and operation and maintenance.

Description

Technical Field

[0001] This invention relates to the field of cloud-edge collaboration and equipment operation and maintenance technology, and in particular to a method for collaborative debugging and operation and maintenance of multi-terminal information equipment. Background Technology

[0002] With the rapid development of information technology, information systems in various scenarios have gradually upgraded from single-terminal architectures to multi-terminal collaborative architectures, encompassing terminal devices, network devices, servers, and various sensors and actuators, forming a complex collaborative system with multiple terminals, protocols, and scenarios. In smart parks, monitoring terminals, environmental sensors, access control terminals, and smart lighting terminals need to operate collaboratively; in industrial production scenarios, PLC terminals, industrial control computers, data acquisition terminals, and display terminals need to work together. The collaborative debugging and maintenance of multi-terminal information devices is a core link in ensuring the stable and efficient operation of the entire information system. Its key lies in achieving unified monitoring of the status of multiple terminal devices, rapid fault location, collaborative debugging and linkage, and full lifecycle maintenance management.

[0003] However, current debugging and maintenance of multi-terminal information devices mainly rely on traditional operation and maintenance models, supplemented by some scattered operation and maintenance tools to complete the debugging, troubleshooting, and daily maintenance of terminal devices. In this model, the operation and maintenance of multiple terminals are independent, lacking a unified collaborative scheduling mechanism, resulting in low overall operation and maintenance efficiency. The communication protocols used by heterogeneous terminal devices are inconsistent, making adaptation difficult and easily creating information silos. The low level of intelligence and excessive reliance on manual operation not only increases the probability of errors but also causes significant delays in data synchronization, making it difficult to guarantee consistency in debugging and maintenance. Furthermore, the scattered storage of operation and maintenance data and the lack of a full lifecycle management mechanism further increase operation and maintenance costs. In weak network or offline scenarios, the existing solutions lack adaptability and emergency response capabilities, making it difficult to meet the actual needs of multi-terminal collaborative operation and maintenance in complex scenarios. Summary of the Invention

[0004] To address the aforementioned technical problems, this invention provides a method for collaborative debugging and maintenance of multi-terminal information technology devices. The technical solution of this method is as follows: Based on the communication protocol types and data interaction format standards of multiple terminal devices, a corresponding protocol adaptation interface is configured for each terminal device. A communication connection is established with the corresponding terminal device through each protocol adaptation interface. Each protocol adaptation interface is used to perform bidirectional data format conversion between each terminal device and the edge collaboration node. After establishing the communication connection, a status acquisition command carrying time synchronization parameters is sent to each terminal device, and real-time operating status data carrying acquisition timestamps is received from each terminal device in response to the status acquisition command. Based on the device type of each terminal device, status features are extracted from the real-time operating status data of each terminal device to generate a device status label for each terminal device. Obtain debugging task information issued by the cloud scheduling center, and determine the target terminal device set to participate in collaborative debugging from the multiple terminal devices based on the debugging task information; Based on the device status tag of each target terminal device in the target terminal device set and the real-time operating status data carrying the collection timestamp, a collaborative status view of the target terminal device set is constructed according to a unified time series benchmark. The collaborative status view is used to aggregate and display the real-time operating status data of each target terminal device on the same time axis. In response to a debugging operation command for any target terminal device in the set of target terminal devices, a debugging control signal is generated according to the debugging operation command, the debugging control signal is sent to any target terminal device through the protocol adaptation interface, and the sending timestamp of the debugging control signal is recorded. The system obtains feedback operation status data carrying feedback acquisition timestamps returned by each target terminal device in the target terminal device set after executing the debugging control signal. Based on the sending timestamp and the feedback acquisition timestamp, the system compares the feedback operation status data with the historical operation status data within the corresponding time interval in the collaborative status view, and generates collaborative diagnostic analysis results based on the comparison results.

[0005] The technical solution of this invention configures protocol adaptation interfaces for terminal devices with different communication protocol types to complete bidirectional data format conversion, and collects real-time operating status data with timestamps based on time synchronization parameters to construct device status tags. After determining the target terminal device set in conjunction with cloud debugging tasks, a collaborative status view is constructed according to a unified time series benchmark. When responding to debugging operation commands, the sending timestamp is recorded and compared with the feedback operating status data in a time series. This solves the problems of information silos caused by inconsistent protocols of heterogeneous terminals, lack of collaborative scheduling in multi-terminal operation and maintenance, asynchronous status data time, and delay in fault location, and improves the real-time performance, consistency, and diagnostic accuracy of multi-terminal collaborative debugging and maintenance.

[0006] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0007] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0008] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This is a flowchart illustrating an embodiment of a collaborative debugging and maintenance method for multi-terminal information devices according to the present invention. Detailed Implementation

[0009] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0010] Figure 1 This diagram illustrates a flowchart of an embodiment of a collaborative debugging and maintenance method for multi-terminal information devices provided by the present invention, executed by a control terminal. Figure 1 As shown, the collaborative debugging and maintenance method for multi-terminal information devices includes the following steps: S1. Based on the communication protocol types and data interaction format standards of multiple terminal devices, configure corresponding protocol adaptation interfaces for each terminal device, establish communication connections with the corresponding terminal devices through each protocol adaptation interface, and perform bidirectional data format conversion between each terminal device and the edge collaborative node.

[0011] Among them, terminal equipment refers to hardware entities deployed on the field side in an information system for performing information collection, data processing or physical execution functions; for example, in a certain information application site, there are equipment A, equipment B, equipment C and equipment D deployed, where equipment A is a lighting control device, equipment B is an environmental sensing device, equipment C is an access control device and equipment D is a video surveillance device.

[0012] The communication protocol type refers to the category of communication rules and standards followed when the terminal device exchanges data with external devices. For example, device A follows the Modbus protocol for data communication, device B follows the BACnet protocol, device C follows the HTTP protocol, and device D follows the MQTT protocol. The data interaction format standard refers to the specifications of the data organization and encoding format used by the terminal device when transmitting data. For example, device A uses JSON format to organize status data, device B uses XML format to organize sensor data, and device C uses Protocol Buffers format to organize authentication data.

[0013] The protocol adaptation interface refers to a software logic unit deployed on the edge collaboration node, used to adapt to terminal devices with different communication protocol types and data interaction format standards, enabling the edge collaboration node to interact with the terminal devices. For example, the edge collaboration node configures a Modbus protocol adaptation interface for device A, which can handle the Modbus protocol data frame structure, enabling the edge collaboration node to exchange data with device A. The communication connection refers to the logical link established between the edge collaboration node and the terminal device for data transmission. For example, the edge collaboration node establishes a communication connection with device A via Ethernet, device A sends data to the edge collaboration node over this connection, and the edge collaboration node issues control commands to device A over this connection.

[0014] In this context, an edge collaboration node refers to a computing device deployed at the network edge of an information system. It possesses data processing and protocol conversion capabilities and is used for unified access and collaborative management of terminal devices. For example, an edge collaboration node is deployed in a low-voltage equipment room at an information application site. This node connects to devices A, B, C, and D via a local area network and is responsible for the unified management and debugging of these four terminal devices. Bidirectional data format conversion refers to the process by which the edge collaboration node converts uplink data from the terminal devices from their original data format to a unified data format recognizable by the edge collaboration node through a protocol adaptation interface, and converts downlink control data from the edge collaboration node from the unified data format to the original data format corresponding to the terminal devices. For example, after receiving uplink data in Modbus protocol format from device A, the edge collaboration node converts this uplink data to a unified data format recognizable within the edge collaboration node. When sending downlink control data to device A, the edge collaboration node converts the downlink control data from the unified data format to the Modbus protocol format.

[0015] S2. After establishing the communication connection, a status acquisition command carrying time synchronization parameters is sent to each terminal device, and real-time operating status data carrying acquisition timestamps is received from each terminal device in response to the status acquisition command. Based on the device type of each terminal device, status features are extracted from the real-time operating status data of each terminal device to generate a device status label for each terminal device.

[0016] The time synchronization parameter refers to the time information sent by the edge collaboration node to the terminal device, instructing the terminal device to synchronize its local clock with the reference clock of the edge collaboration node. For example, the edge collaboration node sends a time synchronization parameter containing the current reference clock value to device A, and device A calibrates its local clock to match the reference clock of the edge collaboration node based on the time synchronization parameter. The status acquisition instruction refers to the instruction message sent by the edge collaboration node to the terminal device, instructing the terminal device to collect and report real-time operating status data according to a specified collection frequency and a specified list of data items. For example, the edge collaboration node sends a status acquisition instruction to device A, instructing device A to collect the current lighting power, lamp temperature, and operating mode every 10 seconds and report the data to the edge collaboration node.

[0017] Among them, real-time operating status data refers to the time-series data that the terminal device collects during operation according to the status collection instruction, reflecting the current working status of the terminal device; for example, the real-time operating status data reported by device A according to the status collection instruction is: collection timestamp is 14:30:15 on June 1, 2026, lighting power is 45W, lamp temperature is 38℃, and working mode is automatic dimming mode.

[0018] Here, "device type" refers to the category of terminal devices based on their functional attributes and application scenarios. For example, device A is a lighting control device, device B is an environmental sensing device, device C is an access control device, and device D is a video surveillance device. "Device status label" refers to the tagging information generated by the edge collaboration node based on the real-time operating status data and device type of the terminal device. This tagging information is used to characterize the terminal device's operating status level classification. For example, the edge collaboration node determines that device A's operating status level is normal based on the real-time operating status data of device A, and generates a status label for device A as "Normal - Lighting Control Device." This status label includes device type information and operating status level information.

[0019] S3. Obtain debugging task information issued by the cloud scheduling center, and determine the target terminal device set to participate in collaborative debugging from the multiple terminal devices based on the debugging task information.

[0020] Among them, the cloud dispatch center refers to a central management platform deployed on a cloud server, which is used to coordinate and manage the distribution of debugging tasks, configuration of operation and maintenance strategies, and global status monitoring of information systems. For example, a cloud dispatch center is deployed in the cloud, which is responsible for distributing terminal device debugging tasks to edge collaborative nodes in the information application site and receiving collaborative diagnostic analysis results reported by edge collaborative nodes.

[0021] The debugging task information refers to the debugging task description data issued by the cloud scheduling center, which includes a list of terminal device identifiers to be debugged, a debugging operation type identifier, debugging parameter configuration, and a debugging execution time window. For example, the cloud scheduling center issues a debugging task information to the edge collaborative node. The debugging task information includes a list of terminal device identifiers to be debugged, which records the device identifiers of device A and device D. It includes the debugging operation type identifier as parameter calibration, the debugging parameter configuration as a lighting power target value of 50W, and the debugging execution time window as from 14:30:00 to 14:35:00 on June 1, 2026.

[0022] The target terminal device set refers to the set of terminal devices that need to participate in this collaborative debugging, selected by the edge collaboration node from multiple connected terminal devices according to the list of terminal device identifiers to be debugged in the debugging task information. For example, the edge collaboration node selects device A and device D from multiple connected terminal devices according to the list of terminal device identifiers to be debugged in the debugging task information issued by the cloud scheduling center, and combines device A and device D into the target terminal device set.

[0023] S4. Based on the device status tag of each target terminal device in the target terminal device set and the real-time operating status data carrying the collection timestamp, construct a collaborative status view of the target terminal device set according to a unified time series benchmark. The collaborative status view is used to aggregate and display the real-time operating status data of each target terminal device on the same time axis.

[0024] The collaborative status view refers to a visual view in which the edge collaborative nodes aggregate and display the real-time operating status data of each target terminal device in the target terminal device set on the same time axis according to a unified time series reference. For example, after receiving the real-time operating status data of device A and device D, the edge collaborative nodes display the lighting power data curve of device A and the video bitrate data curve of device D in parallel on the same time axis according to a unified time series reference.

[0025] S5. In response to a debugging operation command for any target terminal device in the set of target terminal devices, generate a debugging control signal according to the debugging operation command, send the debugging control signal to any target terminal device through the protocol adaptation interface, and record the sending timestamp of the debugging control signal.

[0026] The debugging operation command refers to the operation command executed by the maintenance personnel on any one of the target terminal devices in the set of target terminal devices in the collaborative status view. This operation command includes the debugging action type and debugging action parameters. For example, the maintenance personnel initiate a debugging operation command for device A in the collaborative status view. The debugging operation command includes the debugging action type as lighting power adjustment and the debugging action parameter as a power setting value of 55W. The debugging control signal refers to the control message generated by the edge collaborative node based on the debugging operation command, conforming to the data interaction format standard and communication protocol type corresponding to the target terminal device. For example, the edge collaborative node generates a debugging control signal conforming to the Modbus protocol and JSON format based on the debugging operation command initiated by the maintenance personnel for device A. This debugging control signal includes a control command with a power setting value of 55W.

[0027] The sending timestamp refers to the time stamp recorded when the edge collaboration node sends the debugging control signal to the target terminal device. For example, the edge collaboration node sends the debugging control signal to device A at 14:32:10 on June 1, 2026, and records the sending timestamp as 14:32:10 on June 1, 2026.

[0028] S6. Obtain the feedback operation status data returned by each target terminal device in the target terminal device set after executing the debugging control signal, carrying the feedback acquisition timestamp. Based on the sending timestamp and the feedback acquisition timestamp, compare the feedback operation status data with the historical operation status data in the corresponding time interval in the collaborative status view, and generate collaborative diagnostic analysis results based on the comparison results.

[0029] The feedback operation status data refers to the operation status data that the target terminal device re-collects and reports according to the acquisition parameter configuration information in the status acquisition instruction after executing the debugging control signal. This operation status data carries a feedback acquisition timestamp. For example, after receiving the debugging control signal and performing lighting power adjustment, device A re-collects operation status data according to the acquisition frequency parameters and reports the feedback operation status data to the edge collaboration node. The feedback operation status data includes a lighting power value of 55W, a lamp temperature of 39℃, and carries a feedback acquisition timestamp of 14:32:25 on June 1, 2026.

[0030] The collaborative diagnostic analysis result refers to the diagnostic conclusion generated by the edge collaborative node based on the comparison between the feedback operating status data of each target terminal device and the historical operating status data within the corresponding time interval in the collaborative status view. This conclusion is used to determine the degree of change and consistency of the status of each target terminal device before and after the debugging operation is executed. For example, the edge collaborative node compares the lighting power value of 55W in the feedback operating status data of device A after executing the debugging control signal with the lighting power value of 45W in the corresponding time interval in the historical operating status data of the collaborative status view, and generates a collaborative diagnostic analysis result. This collaborative diagnostic analysis result indicates that the lighting power of device A has been successfully adjusted to the target value.

[0031] The technical solution of this embodiment configures protocol adaptation interfaces for terminal devices with different communication protocol types to complete bidirectional data format conversion, and collects real-time operating status data with timestamps based on time synchronization parameters to construct device status tags. After determining the target terminal device set in conjunction with cloud debugging tasks, a collaborative status view is constructed according to a unified time series benchmark. When responding to debugging operation commands, the sending timestamp is recorded and compared with the feedback operating status data in time series. This solves the problems of information silos caused by inconsistent protocols of heterogeneous terminals, lack of collaborative scheduling in multi-terminal operation and maintenance, asynchronous status data time, and delay in fault location, and improves the real-time performance, consistency, and diagnostic accuracy of multi-terminal collaborative debugging and maintenance.

[0032] In one alternative approach, the communication protocol type includes at least one of Modbus, BACnet, OPC UA, MQTT, and HTTP protocols, and the data interaction format standard includes at least one of JSON, XML, and Protocol Buffers formats. The bidirectional data format conversion performed by the protocol adaptation interface between each terminal device and the edge collaboration node includes: converting the uplink data sent by each terminal device from the original data format corresponding to the terminal device to a unified data format recognizable by the edge collaboration node, and converting the downlink control data sent by the edge collaboration node from the unified data format to the original data format corresponding to each terminal device.

[0033] The Modbus protocol refers to a master-slave based serial communication protocol that uses a request-response method for data exchange, used for communication between controllers and terminal devices in industrial automation. For example, device A uses the Modbus protocol to communicate with an edge collaboration node. The edge collaboration node, acting as the master, sends a data read request to device A, which acts as the slave. Device A responds to this request by returning a response message containing lighting power data. The BACnet protocol refers to a communication protocol designed for building automation and HVAC control systems, used to achieve data exchange and collaborative control between building devices. For example, device B uses the BACnet protocol to report temperature and humidity data to an edge collaboration node, and the edge collaboration node reads the current temperature and humidity values ​​of device B through the BACnet protocol. The OPC UA protocol refers to a platform-independent communication protocol for industrial automation, using a service-oriented architecture to achieve secure data exchange between devices from different manufacturers. For example, an industrial control computer uses the OPC UA protocol to establish a communication connection with an edge collaboration node, and the edge collaboration node reads the operating status data of the industrial control computer through the OPC UA protocol. MQTT protocol refers to a message transmission protocol based on a publish-subscribe model, employing a client-broker architecture, used for data communication in scenarios with limited network bandwidth or device resources. For example, device D uses the MQTT protocol to publish video stream status messages to a topic subscribed to by an edge collaboration node. The edge collaboration node, acting as a broker, receives the video stream status messages and obtains the operating status of device D. HTTP protocol refers to an application-layer hypertext transfer protocol based on a request-response model, employing a client-server architecture, used for data transmission between distributed information systems. For example, device C uses the HTTP protocol to send a POST request to an edge collaboration node. The message body of the POST request contains the current status data of device C, and the edge collaboration node responds to the POST request by returning an acknowledgment message.

[0034] JSON format refers to a key-value pair-based data exchange format that organizes data using curly braces to represent objects and square brackets to represent arrays. For example, the real-time operating status data reported by device A is organized in JSON format as {“device_id”:“A”,“power”:45,“temperature”:38,“mode”:“auto”}. XML format refers to an Extensible Markup Language (XML) format that uses angle brackets to describe the hierarchical structure and semantic information of data. For example, the real-time operating status data reported by device B is organized in XML format as follows: <data><device_id>B< / device_id> <temperature> 23.5< / temperature> <humidity> 60< / humidity> < / data>Protocol Buffers format refers to a binary encoding format that serializes data using a predefined message structure description file, and uses field numbers and data types for data compression encoding. For example, the real-time operating status data reported by device C is serialized using Protocol Buffers format according to a predefined access control status message structure before transmission.

[0035] Uplink data refers to data sent from the terminal device to the edge collaboration node, including real-time operating status data, event notification data, and status change reports. For example, the uplink data sent by device A to the edge collaboration node includes the current lighting power value of 45W, lamp temperature of 38℃, and the operating mode of automatic dimming. Downlink control data refers to control command data sent from the edge collaboration node to the terminal device, including parameter configuration commands, action execution commands, and status query commands. For example, the downlink control data sent by the edge collaboration node to device A includes a control command with a power setting of 55W, instructing device A to adjust the lighting power to 55W.

[0036] In the above-mentioned optional methods, the bidirectional data format conversion between heterogeneous terminal devices and edge collaborative nodes is further completed through the protocol adaptation interface. Uplink data is converted from the original terminal format to a unified format, and downlink control data is restored from the unified format to the original terminal format, thus breaking down the barriers between different communication protocols and data formats.

[0037] In one alternative approach, the steps of establishing a communication connection with the corresponding terminal device through each protocol adapter interface include: A connection handshake request is sent to the corresponding terminal device through each protocol adapter interface. A handshake confirmation message is received from the terminal device in response to the connection handshake request. A communication link is established with the terminal device based on the handshake confirmation message. Authentication credential information is sent to the corresponding terminal device through each protocol adapter interface. After the authentication credential information is verified by the terminal device, the communication link is maintained in a continuous connection state.

[0038] The connection handshake request refers to an initialization request message sent by the protocol adaptation interface to the terminal device to initiate the establishment of a communication connection. This initialization request message includes protocol version information and connection parameters. For example, the Modbus protocol adaptation interface on the edge collaboration node sends a connection handshake request to device A. This connection handshake request includes the Modbus protocol version number 2.0 and the communication baud rate parameter 9600. The handshake confirmation message refers to a response message returned by the terminal device to the protocol adaptation interface in response to the connection handshake request. This response message confirms the establishment of the communication connection. This response message includes the terminal device identifier and the supported connection parameters. For example, device A, in response to the connection handshake request sent by the Modbus protocol adaptation interface, returns a handshake confirmation message to the Modbus protocol adaptation interface. This handshake confirmation message includes the device identifier of device A as A and the supported communication baud rate of 9600.

[0039] The authentication credential information refers to the authentication credential data sent by the protocol adapter interface to the terminal device, used to prove that the edge collaboration node has legitimate access rights. This authentication credential data includes a username, password, or digital certificate. For example, the Modbus protocol adapter interface sends authentication credential information to device A, which includes the username "admin" and an encrypted password hash value. The persistent connection state refers to the long-term communication link maintained between the protocol adapter interface and the terminal device. In the persistent connection state, the protocol adapter interface and the terminal device can exchange data at any time without re-establishing a connection. For example, the communication link between the Modbus protocol adapter interface and device A remains in a persistent connection state. Even when there is no data transmission, the communication link remains open, and the edge collaboration node can send control commands to device A at any time through this communication link.

[0040] In the above-mentioned optional methods, a communication link is further constructed by handshake request and confirmation message when establishing a communication connection, and authentication is completed with the help of authentication credentials. After successful authentication, the communication link is maintained in a continuous connection state to ensure the reliability and security of the data transmission link.

[0041] In one alternative approach, the status acquisition instruction includes time synchronization parameters and acquisition parameter configuration information. The time synchronization parameters are used to instruct each terminal device to synchronize and calibrate its local clock with the reference clock of the edge collaboration node. The acquisition parameter configuration information includes acquisition frequency parameters and a list of acquisition data items, which are used to instruct each terminal device to acquire and report operational status data according to the acquisition frequency parameters and the list of acquisition data items.

[0042] The acquisition parameter configuration information refers to the configuration information contained in the status acquisition command, which instructs the terminal device on how to acquire and report operating status data. This configuration information includes acquisition frequency parameters and a list of acquisition data items. For example, the acquisition parameter configuration information contained in the status acquisition command sent by the edge collaborative node is an acquisition frequency of 10 seconds and a list of acquisition data items: lighting power, lamp temperature, and working mode.

[0043] The local clock refers to a timer maintained internally by the terminal device to record local time. This local clock is used to mark the collection time of the operational status data collected by the terminal device. For example, the local clock maintained internally by device A is calibrated to 14:30:00 on June 1, 2026 after receiving the time synchronization parameter. All subsequent operational status data collected by device A will be marked with the collection timestamp using this local clock. The reference clock refers to a standard clock source maintained internally by the edge collaboration node, used as a time reference to provide a unified time synchronization reference to each terminal device. For example, the reference clock maintained internally by the edge collaboration node is 14:30:00 on June 1, 2026. The edge collaboration node sends this reference clock value as a time synchronization parameter to device A.

[0044] The acquisition frequency parameter refers to the time interval specified in the status acquisition command, used to control the time interval for the terminal device to collect and report operational status data. For example, if the acquisition frequency parameter specified in the status acquisition command sent by the edge collaboration node is 10 seconds, device A will collect operational status data every 10 seconds and report it to the edge collaboration node. The data item list refers to the list of items specified in the status acquisition command, used to indicate the specific operational status parameters that the terminal device needs to collect. For example, if the data item list in the status acquisition command sent by the edge collaboration node includes three items—lighting power, lamp temperature, and operating mode—device A will only collect operational status data for these three items according to the data item list.

[0045] In the above-mentioned optional methods, time synchronization parameters and acquisition parameter configuration information are further embedded in the status acquisition command, instructing each terminal device to synchronize and calibrate its local clock with the reference clock of the edge collaborative node, and to acquire and report the operating status data according to the preset acquisition frequency and data item list.

[0046] In one alternative approach, the step of generating a device status tag for each terminal device includes: Based on the device type of each terminal device, a list of features to be extracted corresponding to the device type is determined. Status feature values ​​are extracted from the real-time operating status data of each terminal device according to the list of features to be extracted. The extracted status feature values ​​are compared with a preset multi-level status threshold range corresponding to the device type. Based on the comparison result, the operating status level of each terminal device is determined, and a device status label is generated for each terminal device based on the operating status level.

[0047] The "list of features to be extracted" refers to a list of items obtained by the edge collaboration node from a preset configuration based on the device type of the terminal device. This list indicates the status feature values ​​to be extracted from the real-time operating status data. For example, based on the device type of device A (lighting control device), the edge collaboration node obtains a list of features to be extracted from the preset configuration that includes three items: power deviation rate, temperature change rate, and mode switching frequency. The status feature value refers to a quantitative value extracted by the edge collaboration node from the real-time operating status data of the terminal device according to the list of features to be extracted. This quantitative value characterizes the operating status of the terminal device. For example, the status feature values ​​extracted by the edge collaboration node from the real-time operating status data of device A are: power deviation rate of 2%, temperature change rate of 1.5°C per minute, and mode switching frequency of 2 times every 10 minutes.

[0048] The multi-level state threshold range refers to a preset set of continuous numerical ranges corresponding to each device type. This set of continuous numerical ranges is divided by multiple thresholds, and each threshold range corresponds to an operating state level. For example, the preset multi-level state threshold range for lighting control equipment includes a power deviation rate range of 0% to 5% for the normal state, a power deviation rate range of 5% to 10% for the warning state, and a power deviation rate range greater than 10% for the fault state. The operating state level refers to the level classification determined by the edge collaboration node after comparing the extracted state feature values ​​with the multi-level state threshold range. This level classification is used to characterize the current operating health of the terminal device. For example, if the power deviation rate of device A is 2%, which falls within the power deviation rate range of 0% to 5% corresponding to the normal state, the edge collaboration node determines that the operating state level of device A is normal.

[0049] In the above-mentioned optional methods, the list of features to be extracted is further determined according to the type of terminal device, the status feature values ​​are extracted from the real-time operating status data, and compared with the corresponding multi-level status threshold range. The operating status level is determined according to the comparison results, and a device status label that can intuitively reflect the health status of the device is generated.

[0050] In one alternative approach, the step of determining the target set of terminal devices participating in collaborative debugging from the plurality of terminal devices based on the debugging task information includes: Extract the list of terminal device identifiers to be debugged, the debug operation type identifier, the debug parameter configuration, and the debug execution time window from the debug task information. Select terminal devices whose device identifiers belong to the list of terminal device identifiers to be debugged from the multiple terminal devices, and form a target terminal device set for collaborative debugging from the selected terminal devices.

[0051] The "Pending Debugging Terminal Device Identifier List" refers to a list of unique identifiers for all terminal devices required to participate in this collaborative debugging, as specified by the cloud dispatch center, contained in the debugging task information. For example, the "Pending Debugging Terminal Device Identifier List" in the debugging task information issued by the cloud dispatch center includes two device identifiers, A and D, corresponding to device A and device D, respectively. The "Debugging Operation Type Identifier" refers to an identifier contained in the debugging task information, used to indicate the type of operation to be performed in this collaborative debugging. For example, if the debugging operation type identifier in the debugging task information issued by the cloud dispatch center is "Parameter Calibration," this parameter calibration identifier indicates that a terminal device parameter calibration operation needs to be performed in this collaborative debugging.

[0052] The debugging parameter configuration refers to the configuration information included in the debugging task information, which indicates the target parameter value or specific action parameters that the target terminal device needs to adjust to during this collaborative debugging. For example, the debugging parameter configuration in the debugging task information issued by the cloud dispatch center is a lighting power target value of 50W, indicating that device A needs to adjust the lighting power to 50W. The debugging execution time window refers to the time period information included in the debugging task information, which indicates the effective execution time period of this collaborative debugging. For example, the debugging execution time window in the debugging task information issued by the cloud dispatch center is from 14:30:00 to 14:35:00 on June 1, 2026, and the edge collaborative node performs this collaborative debugging operation within this debugging execution time window.

[0053] In the above-mentioned optional methods, the list of terminal device identifiers to be debugged, the debug operation type identifier, the debug parameter configuration, and the debug execution time window are further parsed from the debug task information. Terminal devices with matching identifiers are selected from all terminal devices to form a set of target terminal devices participating in collaborative debugging.

[0054] In one alternative approach, the step of constructing a collaborative state view of the target terminal device set according to a unified timing reference includes: The collection timestamp is extracted from the real-time operating status data of each target terminal device. Using the collection timestamp as the time axis positioning basis, the real-time operating status data of each target terminal device is mapped to the time axis under the unified time series reference according to the collection timestamp. The real-time operating status data is arranged in parallel between each target terminal device according to the time alignment method. The corresponding status identifier is marked on each real-time operating status data in the parallel arrangement according to the device status label of each target terminal device.

[0055] Among them, the status identifier refers to the graphic or color mark that the edge collaboration node marks on the real-time operating status data of each target terminal device in the collaboration status view, which is used to intuitively display the operating status level of the terminal device; for example, the edge collaboration node marks the lighting power data curve of device A in the collaboration status view with a green status identifier, which is used to intuitively display that the operating status level of device A is normal.

[0056] In the above-mentioned optional methods, the real-time operating status data of each target terminal device is further mapped to the time axis under a unified time reference by using the collection timestamp as the time axis positioning basis. The data is arranged in parallel according to the time alignment method and the status identifiers corresponding to the device status labels are superimposed to form a multi-terminal collaborative status view.

[0057] In one alternative approach, the step of generating a debug control signal based on the debug operation instruction includes: In response to a debugging operation command for any target terminal device in the set of target terminal devices, a debugging action type and debugging action parameters are extracted from the debugging operation command. A debugging control signal conforming to the data interaction format standard corresponding to any target terminal device is generated according to the debugging action type and the debugging action parameters. The debugging control signal is then sent to any target terminal device through the protocol adaptation interface corresponding to any target terminal device.

[0058] The debugging action type refers to the category information contained in the debugging operation instruction, which indicates the type of operation action that the edge collaborative node performs on the target terminal device. For example, the debugging action type contained in the debugging operation instruction for device A initiated by the maintenance personnel is "lighting power adjustment," and this lighting power adjustment category information indicates that the edge collaborative node performs the operation of adjusting the lighting power. The debugging action parameter refers to the numerical value or configuration information contained in the debugging operation instruction, which indicates the specific parameters that the edge collaborative node uses when performing the debugging action. For example, the debugging action parameter contained in the debugging operation instruction for device A initiated by the maintenance personnel is a power setting value of 55W, and this power setting value of 55W indicates that the edge collaborative node adjusts the lighting power of device A to 55W.

[0059] In the above-mentioned optional methods, the debugging action type and debugging action parameters are further extracted from the debugging operation instructions to generate debugging control signals that conform to the corresponding data format standards of the target terminal device. These signals are then accurately sent to the target terminal device through the protocol adaptation interface to ensure that heterogeneous terminals correctly identify and execute the control instructions.

[0060] In one optional approach, the step of comparing the feedback operational status data with historical operational status data within the corresponding time interval in the collaborative status view includes: The feedback status parameter values ​​of each target terminal device at multiple feedback sampling times after the execution of the debugging control signal are extracted from the feedback operation status data. The historical status parameter values ​​of each target terminal device at multiple historical sampling times before the transmission timestamp are extracted from the collaborative status view. The status parameter change vector and historical status change vector of each target terminal device are calculated based on the feedback status parameter values ​​and the historical status parameter values. The state difference degree of each target terminal device before and after the execution of the debugging control signal is calculated according to the following formula:

[0061] in, Indicates the first The degree of state difference of each target terminal device before and after the execution of the debugging control signal. Indicates by the first The first vector is composed of multiple feedback status parameter values ​​of a target terminal device. Indicates by the first The second vector is composed of multiple historical state parameter values ​​of a target terminal device. Indicates the first The inverse matrix of the covariance matrix between the state parameters of each target terminal device, wherein the covariance matrix is ​​formed by the first... The system constructs a system based on the historical state parameter values ​​of a target terminal device from multiple historical sampling times prior to the transmission timestamp, wherein the number of state parameters involved in the construction is less than the total number of historical sampling times. This represents the total number of parameters involved in the state comparison. Indicates the parameter number. Indicates the first The time decay weighting coefficient of each parameter Indicates the first The first target terminal device The time interval between the feedback sampling time and the sending timestamp of each parameter. This indicates the length of the debugging execution time window. Indicates the first The first target terminal device The parameters are the feedback change rate vectors between the feedback sampling time and the previous feedback sampling time. Indicates the first The first target terminal device The parameters are a vector of historical change rates between the historical sampling time and the previous historical sampling time. This represents the preset regularization constant.

[0062] It should be noted that the above formula consists of three metric terms with different physical meanings. The first term is the squared Mahalanobis distance term, which uses the inverse of the covariance matrix to decorrelate and normalize the difference vector between the first vector composed of feedback state parameter values ​​and the second vector composed of historical state parameter values. This eliminates the interference of dimensional differences and linear correlations between the state parameters on the difference measurement results, thereby accurately reflecting the degree of change in the state amplitude of the target terminal device before and after the execution of the debugging control signal. The second term is the time decay penalty term, which is calculated by dividing the time interval between the feedback sampling time of each parameter and the transmission timestamp by the length of the debugging execution time window. The first term is a normalization process. After squaring the normalized result, it is multiplied by the time decay weight coefficient of the corresponding parameter to penalize the contribution of data points whose feedback sampling time is far from the transmission timestamp in the difference calculation. This makes the difference more focused on reflecting the changes in feedback data in the short term after the execution of the debugging control signal. The third term is the change direction consistency term. By calculating the cosine similarity between the feedback change rate vector and the historical change rate vector, and subtracting the cosine similarity by a constant 1, the inconsistency of the state change trend of the target terminal device before and after the execution of the debugging control signal is penalized. This allows the difference to reflect the differences in both the magnitude and direction of the state value change at the same time.

[0063] The above formula quantifies the state changes of the target terminal device before and after the execution of the debugging control signal into a comprehensive state difference value. This value takes into account three dimensions: state amplitude difference, feedback timeliness, and consistency of change direction, providing a quantitative data basis for the generation of subsequent collaborative diagnostic analysis results.

[0064] In the above-mentioned optional methods, multi-dimensional information such as feedback state parameter values, historical state parameter values, time decay weight, and change rate direction are further integrated, and the state difference degree of each terminal device before and after the execution of the debugging control signal is calculated according to the state difference degree formula, so as to quantitatively evaluate the impact of a single debugging operation on the device state.

[0065] In one alternative approach, the step of generating collaborative diagnostic analysis results based on the comparison results includes: The state difference degree of each target terminal device is arranged into a difference degree sequence according to the order of each target terminal device in the collaborative state view. The state change direction identifier of each target terminal device after the execution of the debugging control signal is determined according to the feedback state parameter value of each target terminal device. The comprehensive diagnostic index of the target terminal device set is calculated according to the following formula:

[0066] in, This represents a comprehensive diagnostic index for the target set of terminal devices. This represents the total number of target terminal devices in the target terminal device set. and Both represent the serial number of the target terminal device. Indicates the first The device priority weight coefficient of each target terminal device Indicates the first The saturation adjustment coefficient for the difference of each target terminal device Indicates the first The state difference degree of each target terminal device. Indicates the first The state difference degree of each target terminal device. Indicates the first The target terminal device and the first Device association weighting coefficients between target terminal devices Indicates the first The target terminal device and the first The arrangement distance of the target terminal devices in the collaborative status view This represents the preset distance normalization constant. Indicates the first The response consistency penalty weighting coefficient for each target terminal device Indicates the first The target terminal device is identified by the direction of the state change after the debugging control signal is executed. This indicates the state change direction identifier that represents the largest proportion in the target terminal device set. For indicator functions, when and The value is 1 when they are not equal, and when they are equal. and When they are equal, the value is 0.

[0067] It should be noted that the above formula consists of three parts with different diagnostic functions. The first part is a nonlinear saturation transformation term for the single-device difference degree. By multiplying the state difference degree of each target terminal device by the difference degree saturation adjustment coefficient, taking the negative exponent, and then subtracting the exponent result from the constant 1, the state difference degree is mapped to the saturation range between 0 and 1, avoiding excessive influence of extreme state difference degree values ​​of individual target terminal devices on the comprehensive diagnostic index. The second part is a difference degree comparison term between paired devices. By traversing all possible device pairs in the target terminal device set, the absolute value of the difference in state difference degree between each pair of devices is calculated, multiplied by the device association weight coefficient, and then multiplied by... A distance factor, which decays exponentially based on the ratio of the arrangement distance of the devices in the collaborative state view to a preset distance normalization constant, penalizes the inconsistency in the state differences between highly correlated device pairs, thereby reflecting the degree of coordination misalignment between devices; the third item is the group response consistency penalty item. First, the state change direction identifier with the largest proportion in the target terminal device set is determined as the dominant direction. Then, the target terminal devices whose state change direction identifier is inconsistent with the dominant direction are marked by an indicator function. The marking result is multiplied by the response consistency penalty weight coefficient and the average value is taken to penalize abnormal terminal devices whose response direction deviates from the mainstream trend of the group after the debugging control signal is executed.

[0068] The above formula integrates the state differences of each target terminal device in the target terminal device set and the response consistency among each target terminal device into a comprehensive diagnostic index. This index reflects three levels: the degree of state change of a single device, the degree of coordination disorder among multiple devices, and the degree of consistency of group response. It provides a quantitative basis for operation and maintenance personnel to judge the overall effect of this collaborative debugging and identify abnormal devices.

[0069] In the above-mentioned optional methods, the state differences of each terminal device are further arranged into a difference sequence according to the order in the collaborative state view. Combined with multiple factors such as device priority weight, inter-device association weight, and response consistency, a comprehensive diagnostic index of the target terminal device set is calculated to evaluate the operating status after collaborative debugging from an overall perspective.

[0070] In one alternative approach, before sending the status acquisition command carrying time synchronization parameters to each terminal device, the method further includes: Obtain the current network communication quality parameters between each terminal device and the edge collaboration node, and determine the data reporting mode corresponding to each terminal device based on the current network communication quality parameters. The data reporting modes include real-time online reporting mode and local cache reporting mode. When the current network communication quality parameter is greater than or equal to the preset network quality threshold, the data reporting mode of each terminal device is determined to be the real-time online reporting mode. According to the real-time online reporting mode, each terminal device immediately reports to the edge collaboration node after collecting real-time operating status data. When the current network communication quality parameters are less than the preset network quality threshold, the data reporting mode of each terminal device is determined to be the local cache reporting mode. According to the local cache reporting mode, each terminal device stores the collected real-time operating status data with the collection timestamp in the local cache of the terminal device, and calculates the local cache data reporting trigger judgment value of each terminal device according to the following formula:

[0071] in, Indicates the first The local cache data reporting of each terminal device triggers the judgment value. Indicates the first The current network communication quality parameters of each terminal device at the current moment. This indicates the preset network quality threshold. Indicates the first The amount of cached data already stored in the local cache of each terminal device. Indicates the first The maximum storage capacity of the local cache of each terminal device; when When greater than or equal to 1, the instruction is the first Each terminal device attempts to report real-time operating status data with collection timestamps stored in its local cache to the edge collaboration node, and deletes the reported real-time operating status data from the local cache after successful reporting.

[0072] In the aforementioned optional methods, a dynamic determination mechanism for data reporting modes based on current network communication quality parameters is further introduced before the status acquisition phase. This allows terminal devices to adopt a real-time online reporting mode when network quality is good to ensure data timeliness, and automatically switch to a local cache reporting mode when network quality deteriorates to avoid data loss. The local cache data reporting trigger determination value comprehensively weighs the current network quality and local cache usage. When the network quality recovers to a level sufficient to complete data transmission and the local cache backlog reaches a level that requires reporting, the cached data is automatically retransmitted. This avoids the ineffective occupation of network resources and waste of terminal power consumption caused by frequent reporting attempts in weak network scenarios, and ensures that the operating status data is not lost in weak network or offline scenarios. After the network recovers, the local cached data can be automatically retransmitted to the edge collaboration node, thereby ensuring the integrity and continuity of subsequent collaborative status view construction and historical operating status data comparison. This effectively improves the adaptability and data integrity assurance capability of multi-terminal information equipment collaborative debugging and maintenance methods in weak network and offline scenarios.

[0073] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for collaborative debugging and maintenance of multi-terminal information technology equipment, characterized in that, include: Based on the communication protocol types and data interaction format standards of multiple terminal devices, a corresponding protocol adaptation interface is configured for each terminal device. A communication connection is established with the corresponding terminal device through each protocol adaptation interface. Each protocol adaptation interface is used to perform bidirectional data format conversion between each terminal device and the edge collaboration node. After establishing the communication connection, a status acquisition command carrying time synchronization parameters is sent to each terminal device, and real-time operating status data carrying acquisition timestamps is received from each terminal device in response to the status acquisition command. Based on the device type of each terminal device, status features are extracted from the real-time operating status data of each terminal device to generate a device status label for each terminal device. Obtain debugging task information issued by the cloud scheduling center, and determine the target terminal device set to participate in collaborative debugging from the multiple terminal devices based on the debugging task information; Based on the device status tag of each target terminal device in the target terminal device set and the real-time operating status data carrying the collection timestamp, a collaborative status view of the target terminal device set is constructed according to a unified time series benchmark. The collaborative status view is used to aggregate and display the real-time operating status data of each target terminal device on the same time axis. In response to a debugging operation command for any target terminal device in the set of target terminal devices, a debugging control signal is generated according to the debugging operation command, the debugging control signal is sent to any target terminal device through the protocol adaptation interface, and the sending timestamp of the debugging control signal is recorded. The system obtains feedback operation status data carrying feedback acquisition timestamps returned by each target terminal device in the target terminal device set after executing the debugging control signal. Based on the sending timestamp and the feedback acquisition timestamp, the system compares the feedback operation status data with the historical operation status data within the corresponding time interval in the collaborative status view, and generates collaborative diagnostic analysis results based on the comparison results.

2. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 1, characterized in that, The communication protocol type includes at least one of Modbus protocol, BACnet protocol, OPC UA protocol, MQTT protocol and HTTP protocol. The data interaction format standard includes at least one of JSON format, XML format and Protocol Buffers format. The bidirectional data format conversion performed by the protocol adaptation interface between each terminal device and the edge collaboration node includes: converting the uplink data sent by each terminal device from the original data format corresponding to the terminal device to a unified data format recognizable by the edge collaboration node, and converting the downlink control data sent by the edge collaboration node from the unified data format to the original data format corresponding to each terminal device.

3. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 2, characterized in that, The steps for establishing a communication connection with the corresponding terminal device through each protocol adapter interface include: A connection handshake request is sent to the corresponding terminal device through each protocol adapter interface. A handshake confirmation message is received from the terminal device in response to the connection handshake request. A communication link is established with the terminal device based on the handshake confirmation message. Authentication credential information is sent to the corresponding terminal device through each protocol adapter interface. After the authentication credential information is verified by the terminal device, the communication link is maintained in a continuous connection state.

4. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 1, characterized in that, The status acquisition instruction includes time synchronization parameters and acquisition parameter configuration information. The time synchronization parameters are used to instruct each terminal device to synchronize and calibrate its local clock with the reference clock of the edge collaboration node. The acquisition parameter configuration information includes acquisition frequency parameters and a list of acquisition data items, which are used to instruct each terminal device to acquire and report operating status data according to the acquisition frequency parameters and the list of acquisition data items.

5. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 4, characterized in that, The steps for generating a device status tag for each terminal device include: Based on the device type of each terminal device, a list of features to be extracted corresponding to the device type is determined. Status feature values ​​are extracted from the real-time operating status data of each terminal device according to the list of features to be extracted. The extracted status feature values ​​are compared with a preset multi-level status threshold range corresponding to the device type. Based on the comparison result, the operating status level of each terminal device is determined, and a device status label is generated for each terminal device based on the operating status level.

6. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 5, characterized in that, The step of determining the set of target terminal devices to participate in collaborative debugging from the plurality of terminal devices based on the debugging task information includes: Extract the list of terminal device identifiers to be debugged, the debug operation type identifier, the debug parameter configuration, and the debug execution time window from the debug task information. Select terminal devices whose device identifiers belong to the list of terminal device identifiers to be debugged from the multiple terminal devices, and form a target terminal device set for collaborative debugging from the selected terminal devices.

7. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 6, characterized in that, The steps of constructing a collaborative state view of the target terminal device set according to a unified timing reference include: The collection timestamp is extracted from the real-time operating status data of each target terminal device. Using the collection timestamp as the time axis positioning basis, the real-time operating status data of each target terminal device is mapped to the time axis under the unified time series reference according to the collection timestamp. The real-time operating status data is arranged in parallel between each target terminal device according to the time alignment method. The corresponding status identifier is marked on each real-time operating status data in the parallel arrangement according to the device status label of each target terminal device.

8. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 7, characterized in that, The step of generating debugging control signals according to the debugging operation instructions includes: In response to a debugging operation command for any target terminal device in the set of target terminal devices, a debugging action type and debugging action parameters are extracted from the debugging operation command. A debugging control signal conforming to the data interaction format standard corresponding to any target terminal device is generated according to the debugging action type and the debugging action parameters. The debugging control signal is then sent to any target terminal device through the protocol adaptation interface corresponding to any target terminal device.

9. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 8, characterized in that, The step of comparing the feedback operation status data with the historical operation status data within the corresponding time interval in the collaborative status view includes: The feedback status parameter values ​​of each target terminal device at multiple feedback sampling times after the execution of the debugging control signal are extracted from the feedback operation status data. The historical status parameter values ​​of each target terminal device at multiple historical sampling times before the transmission timestamp are extracted from the collaborative status view. The status parameter change vector and historical status change vector of each target terminal device are calculated based on the feedback status parameter values ​​and the historical status parameter values. The state difference degree of each target terminal device before and after the execution of the debugging control signal is calculated according to the following formula: ； in, Indicates the first The degree of state difference of each target terminal device before and after the execution of the debugging control signal. Indicates by the first The first vector is composed of multiple feedback status parameter values ​​of a target terminal device. Indicates by the first The second vector is composed of multiple historical state parameter values ​​of a target terminal device. Indicates the first The inverse matrix of the covariance matrix between the state parameters of each target terminal device, wherein the covariance matrix is ​​formed by the first... The system constructs a system based on the historical state parameter values ​​of a target terminal device from multiple historical sampling times prior to the transmission timestamp, wherein the number of state parameters involved in the construction is less than the total number of historical sampling times. This represents the total number of parameters involved in the state comparison. Indicates the parameter number. Indicates the first The time decay weighting coefficient of each parameter Indicates the first The first target terminal device The time interval between the feedback sampling time and the sending timestamp of each parameter. This indicates the length of the debugging execution time window. Indicates the first The first target terminal device The parameters are the feedback change rate vectors between the feedback sampling time and the previous feedback sampling time. Indicates the first The first target terminal device The parameters are a vector of historical change rates between the historical sampling time and the previous historical sampling time. This represents the preset regularization constant.

10. The method for collaborative debugging and maintenance of multi-terminal information equipment according to claim 9, characterized in that, The steps for generating collaborative diagnostic analysis results based on the comparison results include: The state difference degree of each target terminal device is arranged into a difference degree sequence according to the order of each target terminal device in the collaborative state view. The state change direction identifier of each target terminal device after the execution of the debugging control signal is determined according to the feedback state parameter value of each target terminal device. The comprehensive diagnostic index of the target terminal device set is calculated according to the following formula: in, This represents a comprehensive diagnostic index for the target set of terminal devices. This represents the total number of target terminal devices in the target terminal device set. and Both represent the serial number of the target terminal device. Indicates the first The device priority weight coefficient of each target terminal device Indicates the first The saturation adjustment coefficient for the difference in the target terminal devices Indicates the first The state difference degree of each target terminal device. Indicates the first The state difference degree of each target terminal device. Indicates the first The target terminal device and the first Device association weighting coefficients between target terminal devices Indicates the first The target terminal device and the first The arrangement distance of the target terminal devices in the collaborative status view This represents the preset distance normalization constant. Indicates the first The response consistency penalty weighting coefficient for each target terminal device Indicates the first The target terminal device is identified by the direction of the state change after the debugging control signal is executed. This indicates the state change direction identifier that represents the largest proportion of the target terminal device set. For indicator functions, when and The value is 1 when they are not equal, and when... and When they are equal, the value is 0.

Images