Multi-device interconnection method and control system

Abstract

The invention designs a multi-device interconnection control system and a method thereof, and relates to the technical field of Internet of Things platforms, the system is based on a B / S architecture, comprises a device management end and an application server end, can collect and uniformly manage terminal device information, and can realize multi-device interconnection control through a configuration database, a controller format file, a configuration report and a software library. The system realizes equipment identification, software version control and configuration parameter management, comprises the following technologies: establishing a TLS / SSL encryption channel, performing identity verification by using a pre-shared key and an OAuth 2.0 authorization framework, supporting various PnP protocols and plug-in processing, adopting a digital twin technology, monitoring equipment states by a heartbeat mechanism and the like, and further provides a RESTFulAPI interface and a remote firmware upgrading function. And external system access request routing and protocol conversion are realized through the API gateway. According to the technical scheme, the challenge of multi-device interconnection in the prior art is effectively solved.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things platforms, and more specifically, to a multi-device interconnection method and a control system. Background Art

[0002] With the rapid development of Internet of Things (IoT) technology, more and more devices are connected to the network, forming a huge and complex IoT ecosystem. These devices are widely used in many fields such as smart home, industrial automation, smart medical care, smart transportation, etc., such as smart home appliances, lighting systems, and security equipment in smart homes; sensors, controllers, and robots in industry; remote monitoring equipment and smart diagnostic instruments in the medical field, etc. However, there are significant differences in communication protocols and data formats between devices produced by different manufacturers. Taking smart home as an example, some smart devices use Wi-Fi protocol, while others may use Bluetooth, Zigbee or Z-Wave protocols; in industrial environments, devices from different manufacturers may follow different protocols such as Modbus, OPC UA, Profibus, etc., and the data formats are also different. This diversity makes it impossible for devices to communicate directly and exchange data, forming a data island phenomenon.

[0003] This brings many severe challenges to the development and deployment of IoT applications. In order to make different devices work together, developers need to develop specific adapters for each device type. This not only requires an in-depth understanding of the communication details and data structures of various devices, but also requires the writing of a large amount of complex conversion code, which leads to a sharp increase in development workload. As the number of device types increases, the complexity of the system increases significantly, and the difficulty and cost of maintenance also increase accordingly. Whenever a new device is added or an existing device is upgraded, the adapter may need to be modified or even rewritten on a large scale. At the same time, due to the lack of a unified data exchange standard, device data is difficult to share and analyze. In actual applications, data is scattered across various devices or subsystems and cannot be effectively integrated for correlation analysis and in-depth mining.

[0004] The existing technology has problems such as diverse equipment protocols from different manufacturers, difficulty in interoperability, the formation of data islands, difficulty in development, and poor scalability. Summary of the invention

[0005] In order to overcome the problems in the prior art such as diverse equipment protocols from different manufacturers, difficulty in intercommunication, formation of data islands, difficulty in development, and poor scalability, the present invention designs a multi-device interconnection method and control system that can effectively solve the above technical problems.

[0006] In order to solve the above technical problems, the technical solution of the present invention is as follows:

[0007] Multi-device interconnection control system, including:

[0008] Configuration database, used to collect information of all connected terminal devices, identify the terminal devices and determine the software versions and configuration parameters required by them;

[0009] Controller format file, used to define the specific format and specification of different terminal device information, to ensure that the system can correctly parse and process the information from different terminal devices;

[0010] Configuration report, generated by the system to inform the terminal device of the current software version, configuration parameters and whether there is an available update;

[0011] A software library, used to store the software version and configuration parameters, which are encrypted and sent to the terminal device for updating or configuration;

[0012] The terminal device is used to read its own device information and send it to the system. The system determines whether there is an available software update or configuration modification based on the configuration database and the configuration report, and extracts the corresponding software version or configuration parameters from the software library, encrypts them and sends them to the terminal device for updating or configuration.

[0013] Preferably, the system is based on a B / S architecture, including a device management end and an application service end;

[0014] The device management terminal includes a device access module, a security access module, a device docking module, a device configuration module, a device reset module, a device batch operation module, a device status monitoring module, a device system module and an alarm management module, which are used to collect all the terminal device information;

[0015] The application server includes a data management module, a rule engine module, an API integration module and an application plug-in module, wherein the rule engine module includes a linkage engine, a permission engine and a log engine, which are used to process and apply the terminal device information collected by the device management end.

[0016] Preferably, the terminal device information collected by the device management end includes at least the access device type, model, unique identifier, hardware version, software version and communication protocol.

[0017] Preferably, the application server processes the terminal device information in a manner including rule engine linkage control and generation of alarm information, and the applications include data visualization, remote control and report generation.

[0018] The multi-device interconnection method comprises the following steps:

[0019] Terminal device access and lifecycle management, including secure access, data modeling, status monitoring, and remote operation;

[0020] The application server subscribes to the terminal device data topic through MQTT Broker and collects the data reported by the terminal device in real time;

[0021] The application server generates control instructions based on user operations and triggers from the rule engine;

[0022] The system is equipped with an API gateway as an entry point to route access requests from external systems to the terminal devices.

[0023] Preferably, the terminal device access and lifecycle management, including secure access, data modeling, status monitoring and remote operation, further includes:

[0024] Establishing a TLS / SSL encrypted channel to authenticate the terminal device;

[0025] Use pre-shared keys for initial authentication and use the OAuth 2.0 authorization framework to issue access tokens for subsequent communication authentication;

[0026] The system supports multiple PnP protocols to automatically discover and identify newly connected different terminal devices, and implements plug-in processing. For the terminal devices that do not support the PnP protocol, manual configuration options are provided;

[0027] Using digital twin technology to create a virtual digital copy for each of the terminal devices, and storing the metadata of the terminal devices;

[0028] A heartbeat mechanism is used to monitor the health status of the terminal device, and real-time data is pushed, triggering an alarm mechanism to asynchronously notify relevant personnel through Webhook or message queue;

[0029] A RESTful API interface is provided to allow remote configuration of the terminal device parameters and remote firmware upgrades.

[0030] Preferably, the application server subscribes to the terminal device data topic through MQTT Broker, and real-time collection of data reported by the terminal device further includes:

[0031] Use gzip or Snappy algorithm to compress data, AES or TLS / SSL algorithm to encrypt data, and use QoS mechanism to achieve data transmission;

[0032] Use edge computing to preprocess data, including data cleaning, conversion, standardization, and feature extraction;

[0033] Select a time series database to store data, and use a CEP engine to process the terminal device data stream in real time;

[0034] Use domain-specific languages ​​or graphical interfaces to define rules, and the rule engine supports complex event processing functions;

[0035] The terminal device linkage controls the newly connected terminal device and issues an alarm through the alarm management module.

[0036] Preferably, the application server generates control instructions according to user operations and triggering of the rule engine, further comprising:

[0037] The system converts the control instruction into a communication protocol format supported by the target terminal device, and uses a message queue to asynchronously transmit the instruction to the device management end, and the terminal device feeds back the control instruction execution result to the application service end;

[0038] The system uses a confirmation mechanism to set a control instruction execution timeout, and performs corresponding processing if no response is received from the terminal device.

[0039] The system is equipped with an API gateway as an entry point, and routing external system access requests to the terminal device further includes:

[0040] The API gateway verifies the legitimacy of the API request and uses the access token standard protocol for identity authentication and authorization;

[0041] The API gateway provides multiple protection mechanisms, including current limiting, circuit breaking, data verification and Web application firewall, and undertakes the function of communication protocol conversion.

[0042] An electronic device comprises a processor, a memory and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the above-mentioned multi-device interconnection method when executed by the processor.

[0043] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the multi-device interconnection method described above.

[0044] Compared with the prior art, the beneficial effects of the present invention are as follows: the multi-device interconnection method and control system of the present invention realizes efficient and unified management and control of diversified terminal devices by integrating key modules such as configuration database, device format file, configuration report, software library and encryption software package. The system can cross the boundaries of different manufacturers and protocols and provide a compatible access platform for various types of devices, thereby significantly simplifying the complex process of device management. In terms of interoperability, it can identify and integrate devices with multiple communication protocols and data formats, effectively eliminating the data island phenomenon, promoting the free flow and sharing of information, and enhancing security. The system establishes a TLS / SSL encryption channel and uses pre-shared keys and OAuth 2.0 authorization framework ensures the security of device access and data transmission. The reliability is reflected in the system's continuous monitoring of device information and heartbeat mechanism, as well as real-time alarm response to abnormal conditions. It can flexibly add or update management modules to adapt to new device types and communication protocols. In addition, the present invention reduces the maintenance cost of equipment through automated software updates and configuration parameter management. The improvement in development efficiency is due to the RESTful API interface and remote firmware upgrade capabilities provided by the system, which enables developers to quickly respond to market changes and accelerate product iterations. The application of digital twin technology further optimizes the simulation, analysis and prediction of equipment, and improves the level of intelligent equipment management. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only exemplary, and for ordinary technicians in this field, other implementation drawings can be derived based on the provided drawings without paying any creative work.

[0046] Figure 1 This is a schematic diagram of the platform application server of the present invention;

[0047] Figure 2 This is a schematic diagram of the device management terminal of the platform of the present invention;

[0048] Figure 3 This is a step-by-step diagram of the method for interconnecting multiple devices. DETAILED DESCRIPTION

[0049] The drawings are for illustrative purposes only and should not be construed as limiting the present patent;

[0050] In order to better illustrate the present embodiment, some parts in the drawings may be omitted, enlarged or reduced, and do not represent the size of the actual product;

[0051] It is understandable to those skilled in the art that some well-known structures and their descriptions may be omitted in the drawings.

[0052] The technical solution of the present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0053] Example

[0054] Multi-device interconnection control system, including:

[0055] Configuration database, used to collect information of all connected terminal devices, identify the terminal devices and determine the software versions and configuration parameters required by them;

[0056] Controller format file, used to define the specific format and specification of different terminal device information, to ensure that the system can correctly parse and process the information from different terminal devices;

[0057] Configuration report, generated by the system to inform the terminal device of the current software version, configuration parameters and whether there is an available update;

[0058] A software library, used to store the software version and configuration parameters, which are encrypted and sent to the terminal device for updating or configuration;

[0059] The terminal device is used to read its own device information and send it to the system. The system determines whether there is an available software update or configuration modification based on the configuration database and the configuration report, and extracts the corresponding software version or configuration parameters from the software library, encrypts them and sends them to the terminal device for updating or configuration.

[0060] The system is based on B / S architecture, including a device management end and an application service end;

[0061] B / S architecture (Browser / Server Architecture) is a common software system architecture model, widely used in modern network applications. Under this architecture, the user interface is mainly implemented through a web browser, while the application logic and data processing are handled by the server.

[0062] The device management terminal includes a device access module, a security access module, a device docking module, a device configuration module, a device reset module, a device batch operation module, a device status monitoring module, a device system module and an alarm management module, which are used to collect all the terminal device information;

[0063] The application server includes a data management module, a rule engine module, an API integration module and an application plug-in module, wherein the rule engine module includes a linkage engine, a permission engine and a log engine, which are used to process and apply the terminal device information collected by the device management end.

[0064] The terminal device information collected by the device management end includes at least the access device type, model, unique identifier, hardware version, software version and communication protocol.

[0065] The application server processes the terminal device information in a manner including rule engine linkage control and generation of alarm information, and the applications include data visualization, remote control and report generation.

[0066] The multi-device interconnection method comprises the following steps:

[0067] Terminal device access and lifecycle management, including secure access, data modeling, status monitoring, and remote operation;

[0068] The application server subscribes to the terminal device data topic through MQTT Broker and collects the data reported by the terminal device in real time;

[0069] MQTT (Message Queuing Telemetry Transport) Broker is a key component in the MQTT system. As a message proxy server, it is responsible for receiving, processing and distributing messages. MQTT is a lightweight, low-bandwidth communication protocol that is widely used in Internet of Things (IoT) scenarios to achieve communication and data transmission between devices.

[0070] The application server generates control instructions based on user operations and triggers from the rule engine;

[0071] The system is equipped with an API gateway as an entry point to route access requests from external systems to the terminal devices.

[0072] The terminal device access and lifecycle management, including secure access, data modeling, status monitoring and remote operation, further includes:

[0073] Establishing a TLS / SSL encrypted channel to authenticate the terminal device;

[0074] Use a pre-shared key (PSK) for initial authentication and use the OAuth 2.0 authorization framework to issue an access token for authentication of subsequent communications;

[0075] The system supports multiple PnP protocols to automatically discover and identify newly connected different terminal devices, and implements plug-in processing. For the terminal devices that do not support the PnP protocol, manual configuration options are provided;

[0076] Using digital twin technology to create a virtual digital copy for each of the terminal devices, and storing the metadata of the terminal devices;

[0077] A heartbeat mechanism is used to monitor the health status of the terminal device, and real-time data is pushed, triggering an alarm mechanism to asynchronously notify relevant personnel through Webhook or message queue;

[0078] Webhook is a callback mechanism that allows one application to send HTTP POST requests to another application to pass information. This mechanism is often used for real-time updates and notifications. When an event or action occurs on the server, the Webhook can be triggered immediately and notified to the client or another system.

[0079] A RESTful API interface is provided to allow remote configuration of terminal device parameters and remote firmware upgrade (OTA).

[0080] The application server subscribes to the terminal device data topic through the MQTT Broker, and real-time collection of data reported by the terminal device further includes:

[0081] Use gzip or Snappy algorithm to compress data, AES or TLS / SSL algorithm to encrypt data, and use QoS mechanism to achieve data transmission;

[0082] Use edge computing to preprocess data, including data cleaning, conversion, standardization, and feature extraction;

[0083] Select a time series database to store data, and use a CEP engine to process the terminal device data stream in real time;

[0084] CEP is the abbreviation of Complex Event Processing, which is a computing paradigm used to analyze and process event streams in real time in order to detect, correlate and respond to complex event patterns. The core idea of ​​CEP is to identify meaningful event patterns and trends from large amounts of event data, thereby achieving real-time decision-making and automated response.

[0085] Use domain-specific language (DSL) or graphical interface to define rules, and the rule engine supports complex event processing functions;

[0086] The terminal device linkage controls the newly connected terminal device and issues an alarm through the alarm management module.

[0087] The application server generates control instructions according to user operations and triggering of the rule engine, further comprising:

[0088] The system converts the control instruction into a communication protocol format supported by the target terminal device, and uses a message queue to asynchronously transmit the instruction to the device management end, and the terminal device feeds back the control instruction execution result to the application service end;

[0089] The system uses a confirmation mechanism to set a control instruction execution timeout, and performs corresponding processing if no response is received from the terminal device.

[0090] The system is equipped with an API gateway as an entry point, and routing external system access requests to the terminal device further includes:

[0091] The API gateway verifies the legitimacy of the API request and uses the access token standard protocol for identity authentication and authorization;

[0092] The API gateway provides multiple protection mechanisms, including current limiting, circuit breaking, data verification and Web application firewall, and undertakes the function of communication protocol conversion.

[0093] An electronic device comprises a processor, a memory and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the above-mentioned multi-device interconnection method when executed by the processor.

[0094] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the multi-device interconnection method described above.

[0095] In the specific implementation, the lighting controller is used as an example, see Figure 1 and Figure 2 The present invention discloses a multi-device interconnection control system, which is based on a B / S architecture and communicates with various terminal devices. The system includes a device management end and an application service end. The device management end includes a device access module, a security access module, a device docking module, a device configuration module, a device reset module, a device batch operation module, a device status monitoring module, a device system module and an alarm management module.

[0096] The device access module is used to manage and control the process of terminal devices accessing the system, ensuring that the terminal devices can be connected to the system safely and effectively.

[0097] The secure access module ensures that all connected terminal devices comply with security standards to prevent unauthorized access and data leakage.

[0098] The device docking module is used for connection and communication between different terminal devices to ensure that they can work together.

[0099] The device configuration module is used to manage and distribute the configuration parameters of terminal devices, including software versions and network settings.

[0100] The device reset module provides terminal device reset functions, including normal reset (unbinding) and factory reset (unbinding and clearing data) to restore the terminal device to its initial state.

[0101] The device batch operation module allows users to perform batch operations on multiple terminal devices, such as batch binding, configuration adjustment, etc., to improve management efficiency.

[0102] The device status monitoring module monitors the operating status of terminal devices in real time, and promptly detects and responds to terminal device failures or performance issues.

[0103] The device system module manages the system-level information of the terminal device, such as the operating system version, system log, etc., to ensure the normal operation of the terminal device system.

[0104] The alarm management module provides management functions such as alarm viewing, confirmation, and processing, including integrated management, alarm event management, notification strategy management, alarm collaborative processing, and alarm processing analysis.

[0105] The application server includes a data management module, a rule engine module, an API integration module and an application plug-in module. The rule engine module includes a linkage engine, a permission engine and a log engine. The device management end is used to maintain the information of all access terminal devices. The terminal device information includes at least the device type, model, unique identifier, hardware version, software version and communication protocol, and can also be related parameters such as device status, performance indicators and energy consumption data.

[0106] The data management module is used for data entry, storage, query, modification, deletion and other operations to help enterprises manage and utilize data.

[0107] The rule engine module includes a linkage engine, a permission engine and a log engine, which are used to process and apply the terminal device information collected by the terminal device management end.

[0108] The API integration module centrally manages the authentication configuration of third-party APIs and the request configuration of API interfaces, allowing authorized applications to directly call configured APIs to obtain or push data.

[0109] The application plug-in module provides additional functional extensions, allowing users to add or develop new application plug-ins as needed to enhance the functionality of the system.

[0110] The application server is used to process and apply the data collected by the device management end. The processing methods include linkage control of the rule engine and generation of alarm information. The applications include data visualization, remote control, report generation, etc.

[0111] See also Figure 3 , this embodiment provides a device interconnection method, comprising the following steps:

[0112] Lighting controller access and lifecycle management, including secure access, data modeling, status monitoring and remote operation

[0113] Furthermore, before the light controller is connected to the system, a secure TLS / SSL encrypted channel is first established to ensure the confidentiality and integrity of all communications and prevent man-in-the-middle attacks. The light controller needs to be authenticated first. When it is first connected, a pre-shared key (PSK) is used for identity authentication. PSK is a secret key negotiated in advance between the light controller and the system, stored in the secure storage area of ​​the light controller, and measures are taken to prevent leakage. After the identity is verified by PSK, the system will use the OAuth 2.0 authorization framework to issue an access token (Access Token), and subsequent communications use the access token for authentication instead of PSK to improve security. The browser verifies the SSL / TLS certificate provided by the server. According to the selected RSA key exchange algorithm, the browser generates a random number as the pre-master key (PMS), encrypts the PMS with the public key in the server certificate and sends it to the server. The server uses the private key to decrypt the PMS. Both parties use PMS, random numbers and the HMAC-SHA256 pseudo-random function to generate a master key, and derive the data key for symmetric encryption and the key for message authentication code (MAC) verification. The server private key is securely stored on the server side and has never been transmitted over the network; its public key is included in the server certificate signed by the certificate authority (CA). In the future, the communication through the TLS / SSL channel will use the generated key for symmetric encryption and MAC verification to ensure data confidentiality and integrity. For other different types of terminal devices, the system supports multiple PnP protocols, such as UPnP, SSDP, etc., and automatically discovers and identifies newly connected devices. The system implements plug-in processing. The core system provides a common interface that allows various plug-ins to interact with it. Each plug-in is responsible for processing a specific type of device or service. For example, one plug-in processes Zigbee protocol devices, another plug-in processes MQTT protocol sensor data, and another plug-in processes cloud service connections. For terminal devices that do not support PnP, the system provides a manual configuration option, and users can manually enter device information.

[0114] Furthermore, after the lighting controller is connected to the system, digital twin technology is used to create a virtual digital copy for each terminal device through a universal table. The digital twin model established by the system will contain the static attributes of the lighting controller, such as device type, manufacturer, model, IP, communication protocol and dynamic attributes, such as operating status, sensor data, which enables the system to simulate, analyze and predict terminal devices, optimize terminal device management and control strategies. The system stores rich device metadata, including terminal device type, manufacturer, model, firmware version, communication protocol, IP address, sensor list, supported command list, etc. These metadata will be used for terminal device management, data processing, rule engine configuration and command issuance. The metadata is stored in a relational database and provides an API interface for other modules to access.

[0115] Furthermore, after the lighting controller is connected to the system and data modeling is completed, a heartbeat mechanism is also adopted. The terminal device periodically sends a heartbeat packet to the system to indicate its online status. The system judges the health status of the device based on the frequency of the heartbeat packet. If the heartbeat packet is not received for a long time, the device is considered to be offline and an alarm is triggered. After ensuring that the device is online, real-time data is pushed. The device pushes real-time data to the system, such as sensor data, operating parameters, etc. The system monitors the data in real time and triggers alarms based on preset thresholds. After obtaining real-time data, when the lighting controller is in an abnormal state, such as offline, parameter exceeding the limit, etc., the system triggers the alarm mechanism and notifies relevant personnel through Webhook or message queue. The message queue implements asynchronous notification to avoid blocking the system.

[0116] Furthermore, after ensuring the safe and stable operation of the lighting controller, the system provides a RESTful API interface, allowing users to remotely configure terminal device parameters, such as modifying the light controller name, setting the light controller sensor sampling frequency, etc. The system supports remote firmware upgrades (OTA) for the lighting controller. Users can upload new firmware through the system and remotely send it to the terminal device for upgrade. OTA upgrades can improve the reliability and security of the lighting controller and reduce maintenance costs. It provides remote restart and factory reset functions to facilitate user terminal device maintenance and troubleshooting.

[0117] Data modeling: The application server subscribes to the terminal device data topic through the MQTT Broker and collects the data reported by the terminal device in real time.

[0118] Furthermore, after ensuring the access of the lighting controller and the stable operation of the terminal equipment, it also includes data collection. The application server subscribes to the terminal equipment data topic through the MQTT Broker, and collects the data reported by the lighting controller in real time. The QoS mechanism ensures the reliable transmission of data. Data compression uses algorithms such as gzip or Snappy to reduce data transmission and bandwidth occupancy. Data encryption uses encryption algorithms such as AES or TLS / SSL to ensure data transmission security. Edge computing capabilities can pre-process data and reduce the amount of data transmitted to the cloud.

[0119] The data preprocessing process includes steps such as data cleaning, conversion, standardization and feature extraction. Data cleaning is used to remove invalid data and noise data. Data conversion converts data of different formats into a unified format through the developer's specific extraction. Data standardization converts data into a unified dimension and range. Feature extraction developer cloud will extract the characteristics of terminal devices from the original data. These characteristics, such as terminal device type, manufacturer, model, etc., will be used for model training and rule matching. The system uses a time series database. The time series database uses label indexing and columnar storage to optimize the writing and query performance of time series data. The database supports data aggregation, downsampling and interpolation, which facilitates data analysis and visualization. It uses the distributed database architecture TimescaleDB to support data storage and processing. It uses the CEP engine and real-time Processing terminal device data streams, rule definitions use domain-specific languages ​​(DSL) or graphical interfaces to simplify rule creation and management. The rule engine supports complex event processing functions such as event pattern matching, time windows, and sliding windows. The dynamic loading and hot update mechanisms of rules allow rules to be updated without restarting the system. The system terminal devices are linked to control, and the lighting controller can link and control the lights that have been connected to the lighting controller so that the lights can be turned on or off at the same time. The system has an alarm management module that supports a multi-level alarm mechanism and performs graded processing according to the severity of the alarm. The alarm information includes the alarm type, time, device information, alarm content, etc. Alarm notifications support multiple channels, such as email, SMS, Webhook, mobile push notifications, etc. Alarm history records are used to track and analyze alarm events.

[0120] Command issuance and control: The application server generates control instructions based on user operations and triggers of the rule engine.

[0121] Furthermore, after ensuring the safe and stable operation of the lighting controller, a series of operations can be performed on the lighting controller, including: command generation, the application server generates control instructions based on the terminal device information recorded in the database according to user operations and the triggering of the rule engine, such as IP, communication protocol, device type, etc. The instructions contain the target device ID, command type and parameters. The system can support multiple command types, such as switch control, parameter setting, data query, etc., in which the system will convert the control instructions into the communication protocol format supported by the target lighting controller, such as Modbus, OPC UA, MQTT, etc., so that the system can control different types of light controllers without having to worry about the details of the underlying communication protocol. This information is transmitted asynchronously using message queues to improve system reliability and scalability. Message queues can buffer instructions, avoid system overload, and ensure reliable delivery of instructions. Next, the light controller management end receives the control instructions and sends the instructions to the target terminal device according to the light controller communication protocol and IP address. The system supports two-way communication of the device. The terminal device can feed back the instruction execution results to the application server to achieve closed-loop control. The system can use a confirmation mechanism to ensure that the control instructions are correctly received and executed by the light controller. The light controller can send an ACK message to confirm the receipt and execution of the instruction. The system also sets a command execution timeout. If no response is received from the terminal device within the specified time, the command execution is considered to have failed, and corresponding processing is performed and retries are performed. If multiple retries are still unsuccessful, an alarm operation is performed.

[0122] API Integration: The system is equipped with an API gateway as an entry point to route access requests from external systems to the terminal devices.

[0123] Furthermore, after the stability and accuracy of the interaction between the system and the terminal devices, the stability of external API requests is required. The system is equipped with an API gateway. The API gateway serves as the unified entrance to the system. All external systems must pass through the API gateway to access the device. It acts as a reverse proxy and middleware, providing several core functions. The API gateway routes requests to the back-end application server cluster based on the request path and parameters. It can achieve load balancing, distribute traffic to different servers, and improve the throughput and availability of the system. The API gateway is responsible for verifying the legitimacy of the API request and ensuring that only authorized users or systems can access protected resources. The system uses standard protocols such as JWT for identity authentication and authorization. The API gateway also provides the system with a variety of protection mechanisms, including current limiting, fuses, data verification, Web application firewalls, etc. The API gateway will also undertake protocol conversion functions, such as converting HTTP requests into MQTT messages to achieve communication between the system and the lighting controller.

[0124] The same or similar reference numerals correspond to the same or similar components;

[0125] The terms used in the drawings to describe positional relationships are only used for illustrative purposes and should not be construed as limiting this patent;

[0126] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not limitations on the implementation methods of the present invention. For ordinary technicians in the relevant field, other different forms of changes or modifications can be made on the basis of the above description. It is not necessary and impossible to list all the implementation methods here. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the claims of the present invention.

Claims

1. A multi-device interconnection control system, characterized in that: include: Configuration database, used to collect information of all connected terminal devices, identify the terminal devices and determine the software versions and configuration parameters required by them; Controller format file, used to define the specific format and specification of different terminal device information, to ensure that the system can correctly parse and process the information from different terminal devices; Configuration report, generated by the system to inform the terminal device of the current software version, configuration parameters and whether there is an available update; A software library, used to store the software version and configuration parameters, which are encrypted and sent to the terminal device for updating or configuration; The terminal device is used to read its own device information and send it to the system. The system determines whether there is an available software update or configuration modification based on the configuration database and the configuration report, and extracts the corresponding software version or configuration parameters from the software library, encrypts them and sends them to the terminal device for updating or configuration.

2. The multi-device interconnection control system according to claim 1, characterized in that: The system is based on B / S architecture, including a device management end and an application service end; The device management terminal includes a device access module, a security access module, a device docking module, a device configuration module, a device reset module, a device batch operation module, a device status monitoring module, a device system module and an alarm management module, which are used to collect all the terminal device information; The application server includes a data management module, a rule engine module, an API integration module and an application plug-in module, wherein the rule engine module includes a linkage engine, a permission engine and a log engine, which are used to process and apply the terminal device information collected by the device management end.

3. The multi-device interconnection control system according to claim 2, characterized in that: The terminal device information collected by the device management end includes at least the access device type, model, unique identifier, hardware version, software version and communication protocol.

4. The multi-device interconnection control system according to claim 2, characterized in that: The application server processes the terminal device information in a manner including rule engine linkage control and generation of alarm information, and the applications include data visualization, remote control and report generation.

5. A multi-device interconnection method, characterized in that: The multi-device interconnection control system according to any one of claims 1 to 4 is characterized in that it comprises the following steps: Terminal device access and lifecycle management, including secure access, data modeling, status monitoring, and remote operation; The application server subscribes to the terminal device data topic through MQTT Broker and collects the data reported by the terminal device in real time; The application server generates control instructions based on user operations and triggers from the rule engine; The system is equipped with an API gateway as an entry point to route access requests from external systems to the terminal devices.

6. The multi-device interconnection method according to claim 5, characterized in that: The terminal device access and lifecycle management, including secure access, data modeling, status monitoring and remote operation, further includes: Establishing a TLS / SSL encrypted channel to authenticate the terminal device; Use pre-shared keys for initial authentication and use the OAuth 2.0 authorization framework to issue access tokens for subsequent communication authentication; The system supports multiple PnP protocols to automatically discover and identify newly connected different terminal devices, and implements plug-in processing. For the terminal devices that do not support the PnP protocol, manual configuration options are provided; Using digital twin technology to create a virtual digital copy for each of the terminal devices, and storing the metadata of the terminal devices; A heartbeat mechanism is used to monitor the health status of the terminal device, and real-time data is pushed, triggering an alarm mechanism to asynchronously notify relevant personnel through Webhook or message queue; A RESTful API interface is provided to allow remote configuration of the terminal device parameters and remote firmware upgrades.

7. The multi-device interconnection method according to claim 5, characterized in that: The application server subscribes to the terminal device data topic through MQTT Broker, and real-time collection of data reported by the terminal device further includes: Use gzip or Snappy algorithm to compress data, AES or TLS / SSL algorithm to encrypt data, and use QoS mechanism to achieve data transmission; Use edge computing to preprocess data, including data cleaning, conversion, standardization, and feature extraction; Select a time series database to store data, and use a CEP engine to process the terminal device data stream in real time; Use domain-specific languages ​​or graphical interfaces to define rules, and the rule engine supports complex event processing functions; The terminal device linkage controls the newly connected terminal device and issues an alarm through the alarm management module.

8. The multi-device interconnection method according to claim 5, characterized in that: The application server generates control instructions according to user operations and triggering of the rule engine, further comprising: The system converts the control instruction into a communication protocol format supported by the target terminal device, and uses a message queue to asynchronously transmit the instruction to the device management end, and the terminal device feeds back the control instruction execution result to the application service end; The system uses a confirmation mechanism to set a control instruction execution timeout, and performs corresponding processing if no response is received from the terminal device. The system is equipped with an API gateway as an entry point, and routing external system access requests to the terminal device further includes: The API gateway verifies the legitimacy of the API request and uses the access token standard protocol for identity authentication and authorization; The API gateway provides multiple protection mechanisms, including current limiting, circuit breaking, data verification and Web application firewall, and undertakes the function of communication protocol conversion.

9. An electronic device, characterized in that: The method comprises a processor, a memory and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the multi-device interconnection method according to any one of claims 5 to 8 when executed by the processor.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the multi-device interconnection method according to any one of claims 5 to 8 are implemented.

Images