Distributed credential equipment control docking method and device

Abstract

The invention relates to the technical field of intelligent Internet of Things, and particularly provides a distributed credential equipment control docking method and device, and the method comprises the steps: enabling credential equipment to receive or transmit a control instruction through subscribing a specific theme or queue; internet of Things middleware is developed based on the go language, multi-architecture environment adaptation is achieved, and message transmission, routing and persistence are carried out; based on a standard Internet of Things protocol, data and a management instruction are transmitted through a message protocol, and Internet of Things equipment and intelligent agent equipment at an opposite end are managed, controlled and linked, so that message management and remote control of the equipment at the opposite end are realized. Compared with the prior art, data and management instructions can be transmitted through the message protocol, and the Internet of Things equipment and the intelligent agent equipment at the opposite end are managed, controlled and linked, so that message management and remote control of the equipment at the opposite end are realized.

Description

Technical Field

[0001] The present invention relates to the field of smart Internet of Things technology, and specifically provides a distributed information and innovation equipment control docking method and device. Background Art

[0002] In this technology, trusted devices act as publishers and consumers of messages, receiving or sending control commands by subscribing to specific topics or queues. These commands are encapsulated in a message body, containing key data such as device identification, operation type, and operation parameters. Message-based middleware is responsible for message delivery, routing, and persistence, ensuring reliable message transmission between devices.

[0003] It realizes efficient, reliable and flexible control docking between information and innovation equipment, and provides strong support for the centralized management and intelligent control of information and innovation equipment.

[0004] In the existing technology, there are differences between complex instruction sets and reduced instruction sets under the ARM architecture and X86 architecture of the Trusted Innovation. There is inconsistent device compatibility in communication protocols and standards for devices produced by different manufacturers. The edge devices are deployed in places with complex environments, resulting in poor network communication stability. The IoT edge devices are deployed in remote places and the number is large, making remote management and maintenance of the devices difficult. With the continuous deepening and expansion of IoT applications, and the increasing number of edge devices and data volume, there are problems with scale expansion and elastic expansion. Summary of the Invention

[0005] The present invention aims to address the deficiencies of the above-mentioned existing technologies and provides a highly practical distributed information and communication equipment control and docking method.

[0006] A further technical task of the present invention is to provide a distributed information and innovation equipment control docking device that is rationally designed, safe and applicable.

[0007] The technical solution adopted by the present invention to solve its technical problem is: A distributed ICT device control docking method, first, the ICT device receives or sends control instructions by subscribing to a specific topic or queue; Develop IoT middleware based on Go language to achieve multi-architecture environment adaptation and perform message delivery, routing, and persistence; Based on the standard IoT protocol, data and management instructions are transmitted through the message protocol, and the IoT devices and intelligent devices at the other end are managed and linked, thereby realizing message management and remote control of the devices at the other end.

[0008] Furthermore, based on the cross-compilation capability of the golang language in the trusted device, binary programs that run in the ARM environment can be compiled under the porwelshell in the windows environment.

[0009] Furthermore, the standard IoT protocol is the MQTT protocol, which is used to complete edge-to-cloud communication. It is suitable for the distributed information and innovation device control docking scenario in this article. The specific docking operation process is as follows: (1) Create a message broker on the cloud server; (2) The edge devices of the ICT industry act as message publishers and subscribers based on the IoT device middleware; (3) The IoT device middleware connects to the Broker via TCP or IP and communicates using the MQTT protocol.

[0010] Furthermore, message caching and will messages are added to the IoT device middleware, and shadow devices are added to the cloud platform. When the client is disconnected, the MQTT agent will automatically publish the will message to other subscribers who have subscribed to the relevant topics.

[0011] Furthermore, based on the will message, status notification, resource release and message delivery are performed; the status notification is that the client sets a will message to notify other subscribers of its online or offline status; The resource release is to release the occupied resources or perform cleanup operations when the client connection is abnormally disconnected in some scenarios; The messaging is a will message that carries information about the client, and when the client disconnects, the information is passed to other subscribers.

[0012] Furthermore, OTA upgrades are integrated into the IoT device middleware, which carries upgrade package information in the message queue, and integrates device updates, downloads update packages, verifies and installs, restarts, and applies updates through the IoT device middleware.

[0013] Furthermore, authentication and encryption technology is set up between end-to-end to access devices, ensure low latency in cloud-edge device communication, and continuously deepen and expand IoT applications. A distributed information and innovation equipment control and docking device, comprising: at least one memory and at least one processor; The at least one memory is configured to store a machine-readable program; The at least one processor is used to call the machine-readable program to execute a distributed information and communication equipment control docking method.

[0014] Compared with the prior art, the distributed information and innovation equipment control docking method and device of the present invention have the following outstanding beneficial effects: The present invention solves the differences between complex instruction sets and reduced instruction sets under the ARM architecture and X86 architecture, and the device compatibility problem of inconsistent communication protocols and standards among devices produced by different manufacturers.

[0015] It can also solve the problem of network communication stability caused by the deployment of edge devices in places with complex environments, simplify the remote management and maintenance of IoT edge devices, and solve the problems of scale expansion and elastic expansion as the number and amount of data of IoT applications continue to increase. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0017] Attachment Figure 1 This is an architectural diagram of a distributed ICT device control and docking method; Attachment Figure 2 It is a flowchart of adding OTA upgrade capability to the distributed information and innovation device control docking method. DETAILED DESCRIPTION

[0018] In order to enable those skilled in the art to better understand the solutions of the present invention, the present invention will be further described in detail below in conjunction with specific embodiments. Obviously, the embodiments described are only some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0019] A best embodiment is given below: like Figure 1 As shown, a distributed ICT device control docking method in this embodiment, first, the ICT device receives or sends control instructions by subscribing to a specific topic or queue; Develop IoT middleware based on Go language to achieve multi-architecture environment adaptation and perform message delivery, routing, and persistence; Based on the standard IoT protocol, data and management instructions are transmitted through the message protocol, and the IoT devices and intelligent devices at the other end are managed and linked, thereby realizing message management and remote control of the devices at the other end.

[0020] Trusted computing devices may use CPU architectures such as ARM, which differ from traditional X86 architectures. Since X86 and ARM respectively belong to the complex instruction set and reduced instruction set camps, machine instructions do not completely correspond one-to-one, leading to challenges in code porting and compilation. This is especially problematic when machine instruction optimization is directly written in assembly language.

[0021] In this case, based on the cross-compilation capability of the Golang language, we can compile a binary program that can run in the ARM environment under the porwelshell in the Windows environment through a set of codes.

[0022] The following is the compile amd environment: $env:CGO_ENABLED="0" $env:GOOS="linux" $env:GOARCH="amd64" go build The following is the arm compilation environment: $env:CGO_ENABLED="0" $env:GOOS="linux" $env:GOARCH="arm64" go build Based on cross-compilation, we solve the problem of instruction set differences in the trusted computing architecture by developing program code in a Windows environment and building binary programs for the ARM environment.

[0023] Through cross-compilation of the Go language, the IoT device middleware is compiled into software versions that are compatible with multiple architectures.

[0024] Due to the diversity and complexity of IoT devices, devices from different manufacturers often have inconsistent communication protocols and standards, leading to compatibility issues between devices. Communication between edge devices and the cloud must adhere to consistent protocols and standards to ensure accurate data transmission and stable system operation. However, in practice, compatibility issues may prevent edge devices from seamlessly connecting with cloud systems, impacting data transmission efficiency and overall system performance.

[0025] This article uses the MQTT protocol to achieve edge-to-cloud communication. MQTT (Message Queuing Telemetry Transport) is a publish / subscribe messaging protocol designed specifically for the Internet of Things (IoT). This article adds support for the MQTT protocol to IoT device middleware and develops device-specific publish / subscribe rules.

[0026] The MQTT protocol has features such as a publish / subscribe model (MQTT implements message delivery through the publish / subscribe model. Publishers send messages to specific topics, while subscribers subscribe to these topics to receive messages. This model supports one-to-many message publishing and receiving, effectively reducing network traffic and resource usage), lightweight (the MQTT protocol is designed to be very concise, taking up very little code and bandwidth, making it very suitable for resource-constrained devices such as sensors), low bandwidth consumption (due to its lightweight nature, MQTT has extremely low bandwidth consumption in message transmission between IoT devices), efficient resource utilization (MQTT decouples senders and receivers by adopting a publish-subscribe model, thereby effectively improving the overall efficiency of the system), and quality of service (QoS) (the MQTT protocol supports different levels of quality of service to ensure message reliability and consistency. QoS 0, 1, and 2 represent different reliability levels, allowing the appropriate quality of service to be selected according to needs to optimize the message delivery process). It is suitable for the distributed information and innovation device control docking scenario described in this article. The specific docking operation process is as follows: (1) Create a message broker on the cloud server. (2) The edge devices of the ICT industry act as message publishers and subscribers based on the IoT device middleware; (3) The IoT device middleware connects to the Broker via TCP / IP and communicates using the MQTT protocol.

[0027] IoT edge devices are usually deployed in places with complex environments, such as factories, oil fields, etc. The network environment in these places may be unstable and easily interfered by various factors, such as network congestion, equipment failure, etc. This may cause delays, interruptions or data loss in the communication between edge devices and the cloud, seriously affecting the real-time and reliability of the system. In this patent design, we added message cache and will message to the IoT device middleware (the will message is set when the client connects to the MQTT agent, and a shadow device is added to the cloud platform (the cloud caches the command status of the device). When the client is abnormally disconnected due to network failure, power failure or other reasons, the MQTT agent will automatically publish the will message to other subscribers who have subscribed to the relevant topic. This is mainly used to notify other clients that the client is offline, or to deliver some other information related to the client status). Based on the will message, we have implemented the following three capabilities: Status Notification: The client can set a will message to notify other subscribers of its online or offline status. This is very useful for scenarios that require real-time monitoring of the online / offline status of devices or applications.

[0028] Resource Release: In some scenarios, when a client connection is abnormally disconnected, it may be necessary to release occupied resources or perform cleanup operations. By setting a will message, the client can instruct the proxy to perform the corresponding resource release or cleanup operations when it disconnects.

[0029] Information delivery: Will messages can carry information about the client, such as the device's status, location, or other important data. When the client is disconnected, this information can be delivered to other subscribers to keep them informed of the client's status or other relevant information.

[0030] At the same time, the IoT device middleware is designed to retain important information based on the device's own storage, and then retransmit the information after network communication is restored. The rational configuration and utilization of MQTT will messages improves the system's reliability, flexibility, and information transmission efficiency.

[0031] like Figure 2 As shown, IoT edge devices are often deployed in remote locations and are numerous, posing challenges to their remote management and maintenance. Remote monitoring, fault diagnosis, and upgrades for edge devices are crucial communication issues. Furthermore, with the continuous advancement of IoT technology, edge device software and firmware require constant updates to fix vulnerabilities and add new features, placing an additional burden on remote management and maintenance. This paper integrates OTA upgrades (short for Over-the-Air Technology, a method for remotely updating device firmware or software using wireless communication) into IoT device middleware. This approach carries upgrade package information in message queues and integrates device capabilities such as checking for updates, downloading update packages, verifying and installing them, restarting them, and applying updates through the IoT device middleware.

[0032] As IoT applications continue to deepen and expand, the number of edge devices and the amount of data they generate will continue to grow. Achieving scalability and elasticity between edge devices and cloud systems is a key consideration in the communication process. This includes effectively managing and maintaining large-scale devices, ensuring device security and stability, and achieving inter-device collaboration and unified communication protocols. This design leverages the lightweight MQTT communication protocol and authenticated encryption between the server and client to support real-time access to millions of devices while ensuring low latency for cloud-edge device communication.

[0033] Based on the above method, a distributed information and innovation equipment control and docking device in this embodiment includes: at least one memory and at least one processor; The at least one memory is configured to store a machine-readable program; The at least one processor is used to call the machine-readable program to execute a distributed information and communication equipment control docking method.

[0034] The above-mentioned specific implementation methods are only specific cases of the present invention. The patent protection scope of the present invention includes but is not limited to the above-mentioned specific implementation methods. Any technical solutions that conform to the above-mentioned specific implementation methods of the present invention and any appropriate changes or substitutions made thereto by ordinary technicians in the relevant technical field shall fall within the patent protection scope of the present invention.

[0035] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. A distributed information and innovation equipment control docking method, characterized in that: First, the trusted device receives or sends control instructions by subscribing to specific topics or queues; Develop IoT middleware based on Go language to achieve multi-architecture environment adaptation and perform message delivery, routing, and persistence; Based on the standard IoT protocol, data and management instructions are transmitted through the message protocol, and the IoT devices and intelligent devices at the other end are managed and linked, thereby realizing message management and remote control of the devices at the other end.

2. A distributed information-based device control docking method according to claim 1, characterized in that: Based on the cross-compilation capability of the golang language in the trusted computing device, binary programs that run in the ARM environment can be compiled under the porwelshell in the windows environment.

3. A distributed information-based device control docking method according to claim 2, characterized in that: The standard IoT protocol is the MQTT protocol, which is used to complete edge-to-cloud communication. It is suitable for the distributed information and innovation device control docking scenario in this article. The specific docking operation process is as follows: (1) Create a message broker on the cloud server; (2) The edge devices of the ICT industry act as message publishers and subscribers based on the IoT device middleware; (3) The IoT device middleware connects to the Broker via TCP or IP and communicates using the MQTT protocol.

4. A distributed information-based device control docking method according to claim 3, characterized in that: Add message cache and will messages to the IoT device middleware, and add shadow devices to the cloud platform. When the client disconnects, the MQTT agent will automatically publish the will message to other subscribers who have subscribed to the relevant topic.

5. A distributed information-based device control docking method according to claim 4, characterized in that: Based on the will message, status notification, resource release and message delivery are performed; the status notification is that the client sets a will message to notify other subscribers of its online or offline status; The resource release is to release the occupied resources or perform cleanup operations when the client connection is abnormally disconnected in some scenarios; The messaging is a will message that carries information about the client, and when the client disconnects, the information is passed to other subscribers.

6. A distributed information technology equipment control docking method according to claim 5, characterized in that: OTA upgrades are integrated into the IoT device middleware, carrying upgrade package information in the message queue. The IoT device middleware integrates device updates, downloads update packages, verifies and installs, restarts, and applies updates.

7. A distributed information-based device control docking method according to claim 6, characterized in that: Authentication and encryption technology is set up between ends to access devices, ensure low latency in cloud-edge device communications, and continuously deepen and expand IoT applications.

8. A distributed information and innovation equipment control docking device, characterized in that: include: at least one memory and at least one processor; The at least one memory is configured to store a machine-readable program; The at least one processor is configured to call the machine-readable program to execute the method according to any one of claims 1 to 8.

Images