Remote maintenance system and method for edge internet-of-things proxy device based on internet of things

By designing a remote maintenance system for IoT in an edge IoT proxy device, using MQTT protocol and encrypted communication to achieve remote upgrade and fault management, the problems of inconvenient upgrade and maintenance and difficulty in recovery of edge IoT proxy devices in the prior art have been solved, and the problems of inconvenient upgrade and maintenance and difficulty in recovery of edge IoT proxy devices have been improved. The equipment's online rate and service life are as follows.

CN118972408APending Publication Date: 2024-11-15SICHUAN JINGNENG TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410962178.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-17
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The existing edge IoT proxy devices lack remote upgrade maintenance functions, resulting in high upgrade time and labor costs, and the inability to remote management and failure recovery in the event of a failure, reducing the online rate of the device.

Method used

A remote maintenance system based on the Internet of Things is designed, including sensors, aggregation nodes, edge IoT agent devices, security gateways, IoT management platform and operation inspection and control platform, and data transmission and instruction issuance is achieved through MQTT protocol and encrypted communication. , supports functions such as device management, container management, remote login and remote control, and uses the unified object model to automatically add and maintain equipment.

Benefits of technology

Remote upgrade and maintenance of edge IoT agent devices is realized, manpower and material resources are saved, equipment failure time is reduced, and equipment online rate and service life are improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118972408A_ABST
    Figure CN118972408A_ABST
Patent Text Reader

Abstract

The invention discloses an internet-of-things-based remote maintenance system and method for an edge internet-of-things proxy device, and is particularly suitable for an internet-of-things environment of a power system. The system realizes remote monitoring, maintenance and upgrading of equipment by integrating the sensor, the sink node, the edge Internet of Things agent device, the security gateway, the Internet of Things management platform, the operation and maintenance management and control platform and the service system, obviously improves the online rate and management efficiency of the equipment, and reduces the maintenance cost.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field related to the Internet of Things of power systems, and in particular to a remote maintenance system and method for an edge IoT proxy device based on the Internet of Things. Background Art

[0002] In the system architecture of cloud, pipe, edge and end, the edge IoT agent device, as an "edge" side device, carries out data collection and control for southbound and "end" side devices. It performs security authentication and data upload to the north through the "pipe". At the same time, it also receives query, management and control instructions from the "cloud". It is an important communication and management device for the power Internet of Things.

[0003] In the application of edge IoT agent devices in the power industry, the equipment is widely distributed, most of them are unattended, and require high reliability and low maintenance. At the same time, the construction cycle of substations in digital transformation is a long process that is implemented in stages and categories. There are many types of connected sensors and equipment, and the communication technologies and protocols are different. These problems lead to the need for system upgrades after the deployment of edge IoT agent devices to adapt to the access of new sensors and new equipment.

[0004] The current edge IoT proxy devices do not have the remote upgrade and maintenance function using security authentication, and require technicians to go on-site to upgrade the system and configure parameters, resulting in high time and labor costs for the upgrade. At the same time, when an edge IoT proxy device fails, the current management system lacks the necessary technical means to obtain the system status of the edge IoT proxy device, remotely manage and control the containers and hardware resources of the edge IoT proxy device, and remotely recover from the failure, resulting in the inability to repair the failure in time, reducing the online rate of the edge IoT proxy device. Summary of the invention

[0005] In view of the shortcomings of the existing system, the present invention discloses a remote maintenance system and method for edge IoT proxy devices based on the Internet of Things. The system solves the problem of inconvenient remote upgrade and maintenance of edge IoT proxy devices, aggregation nodes, and sensors, saves manpower and material resources, reduces equipment failure time, and increases equipment online rate and service life.

[0006] The system consists of sensors, aggregation nodes, edge IoT agent devices, security gateways, IoT management platforms, operation and inspection control platforms, and business systems.

[0007] The sensor communicates with the aggregation node or edge IoT agent through the field bus. The field bus can use RS485 bus, CAN bus, Ethernet, wireless LoRa and other communication methods;

[0008] The edge IoT proxy device collects the "end" data, performs edge computing, data filtering, adds time stamps, uses the MQTT protocol, performs protocol conversion and data encapsulation, and then publishes the message to the northbound channel through the encryption APP on the edge IoT device after message encryption;

[0009] The edge IoT proxy device runs a communication encryption and decryption APP, which is responsible for encrypting the forward communication data entering the designated port and restoring the reverse data received by the designated port through authentication, identification, decryption and other technical means;

[0010] The northbound channel of the edge IoT proxy device can use physical channels such as 4G\5G APN, Ethernet, and WIFI private network. After being transmitted to the security gateway, it is reversely decrypted and the message is uploaded to the IoT management platform. The IoT management platform is deployed with an MQTT server, which is responsible for receiving and pushing information.

[0011] The business system and the operation and inspection control platform subscribe to relevant topics, and the MQTT server pushes the relevant subject content to the business system and the operation and inspection control platform to realize the uploading of edge IoT agent data messages;

[0012] The business system and the operation and inspection control platform publish equipment management, container management, business interaction, application management, and device management messages to the IoT management platform. The edge IoT agent device subscribes to the relevant subject messages to achieve the control of the business system and the operation and inspection control platform over the edge IoT agent device and the "end" device.

[0013] The body format is: / topic version / edge device or direct device ID / message execution category / message action, and the corresponding command field is: {v1} / {edgeId} / {Topic Type} / {Topic Command};

[0014] The meaning of the message subscription instruction field is as follows: {v1}: indicates that the currently defined topic version is v1; {edgeId}: indicates the edge device or direct device ID that directly establishes an MQTT long connection with this system. This ID is unique within the device and channel-aware IoT management platform, that is, the edge IoT agent code; {Topic Type}: Topic category, mainly including device, container, app, service, and topo. Device indicates that the topic is a device message, service indicates a business message, app indicates an application message, container indicates a container message, and topo indicates a topology message; {TopicCommand}: indicates the action of the message, such as control, collected data, request, or response.

[0015] The operation and inspection control platform is responsible for the remote maintenance and management of the entire system, and has functions such as command issuance, command status query, historical command query, equipment status query, fault statistics, remote login, and remote control;

[0016] The edge IoT agent device has functions such as device management, data collection management, communication management, container management, application management, data management, security management, system maintenance, and log management. All of the above functions can be controlled by local operation or remote commands.

[0017] The system defines a unified object model, standardizes the description of terminal equipment types and parameter types, standardizes monitoring data parameter labels, parameter lengths, and parameter alignment methods, and the edge IoT agent device uploads data in accordance with the unified object model. The system can automatically parse and obtain device information for automatic addition and maintenance of equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Attached Figure 1 It is a diagram of the system composition of the present invention;

[0019] Attached Figure 2 It is the request message format;

[0020] Attached Figure 3 It is the reply message format; DETAILED DESCRIPTION

[0021] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention is further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. In addition, in the following description, the description of well-known structures and technologies is omitted to avoid unnecessary confusion of the concept of the present invention.

[0022] The technical solution of the present invention is described in detail below in conjunction with the accompanying drawings. According to one embodiment of the present invention, a remote maintenance system and method for an edge IoT proxy device based on the Internet of Things is provided. The system composition architecture diagram of the system is shown in FIG. Figure 1 As shown, it includes sensors, aggregation nodes, edge IoT agent devices, security gateways, IoT management platforms, operation and inspection control platforms, and business systems.

[0023] The request message for the edge IoT agent to interact with the IoT management platform is described in JSON format. The common request message fields are as follows: Figure 2 As shown, the response message is as follows Figure 3 shown.

[0024] Example 1, S11, after the edge IoT agent device is powered on, it sends a device access request to the IoT management platform. The edge device publishes Topic: / v1 / ${clientId} / device / request, where clientId is a 16-bit uuid used to connect to the message server to ensure uniqueness;

[0025] Example 1, S12, the request message format sent by the edge IoT agent is as follows Figure 2 , where the type field value is: EVENT_LINKUP (device access): the param field information includes dev (edge ​​device information), CPU (CPU information), mem (memory information), disk (disk information), os (operating system information), and links (other information).

[0026] Example 1, S13, the command information is encrypted by the edge IoT proxy pretending to be an encryption APP and then transmitted to the security gateway through the 4G APN channel. After being decrypted by the full gateway, it is transmitted to the IoT management platform;

[0027] Example 1, S14, IoT management platform; record and verify the edge device information, and send a device access response message to the edge device. The message format should be as follows: Figure 3 , the value of the message type field is: EVENT_LINKUP (device access), and the param field is edgeId (edge ​​device unique identifier);

[0028] Example 1, S15, the edge device publishes and subscribes to Topic: / v1 / ${clientId} / device / response. Get the unique edgeId assigned by the IoT management platform. The subsequent edge IoT agent publishes monitoring data, heartbeat data, and other data, using the unique edgeId.

[0029] Example 2, S21, such as Figure 1 First, the sensor uses the LoRa micro-power communication protocol to transmit the monitoring data to the nearest aggregation node on the 2.4GHz channel. The aggregation node sends the sensor data to the edge IoT agent device through the LoRa wireless low-power networking protocol on the 470.5MHz channel.

[0030] Example 2, S22 Further, the edge IoT proxy device first determines whether the data uploaded by the sensor is legal and valid. If it is valid data, it is prepared to publish Topic: / v1 / ${edgeId} / service / data. The sensor data is attached. Figure 2The message format is encapsulated, where the message type field value is: CMD_REPORTDATA (real-time data reporting), and the param field includes DeviceType (monitoring type code), LinkedDevice (monitored device identification), MfrsDeviceCode (manufacturer device identification), SinkNode (sink node identification), EdgeId (edge ​​agent code), ManufacturerCode (device manufacturer), FrameSN (frame sequence number), AcquisitionTime (monitoring time), Phase (monitoring phase difference), Isalarm (manufacturer self-diagnosis monitoring), MonitorData (monitoring data);

[0031] Example 2, S23, further, the message in step S22 is encrypted by the encryption APP and published to the security gateway through the 4G APN. After decryption, the security gateway publishes the data to the MQTT server of the IoT management platform; the business platform and the operation and inspection platform obtain the terminal sensor data perception by subscribing to Topic: / v1 / ${edgeId} / service / data;

[0032] Example 2, S24, further, after the data is successfully reported, the response subject returns the unique mark of the measurement point. Through this mark, the edge device will automatically report after a new message is generated. If no new message is generated, reporting is prohibited. The response message format is as shown in the attached Figure 2 , where the type field value is: CMD_REPORTDATA (real-time data reporting), and the param field includes DeviceCode (device measurement point code), FrameSN (frame sequence number), AcquisitionTime (monitoring time), Isalarm (manufacturer self-diagnosis monitoring), and MonitorData (monitoring data);

[0033] Example 2, S25, after receiving the data from the upper package, the operation and inspection platform responds to the access result. If the data can be stored, the response code is 200, otherwise it is 400. The command field is in the format as shown in the attached Figure 2 , where the type field is CMD_REPORTDATA (real-time data reporting), and the param field is defined as returning the reporting result description. If successful, it returns the device measurement point code. If unsuccessful, it returns the reason for failure, and the code code returns 200 or other error information.

[0034] Example 3, s31, the edge device subscribes to the message with the Topic: / v1 / ${edgeId} / device / command to obtain the device upgrade command information issued by the operation and inspection platform;

[0035] Example 3, s32, the operation and inspection platform issues an edge device upgrade instruction. The instruction format is as follows: Figure 2 , where the value of the type field is: CMD_SYS_UPGRADE (device upgrade command); param includes jobId (job ID), policy (command interval), version (upgraded version number), upgradeType (upgrade type code), and filePath (file path). The IoT platform pushes this information to the corresponding edgeId edge device;

[0036] Example 3, s33, after receiving the upgrade command, the edge device sends a message to the operation and inspection platform to obtain the file to be upgraded. If the file can be executed, it replies that the command has been received, with a reply code of 202. The edge device publishes a message Topic: / v1 / ${edgeId} / device / data. The command message format is shown in the attached Figure 2 , where the type field is CMD_SYS_GETUPGRADE, and param includes jobId (the ID assigned to this upgrade operation as a job task) and pieces (the current piece, starting from 1);

[0037] Example 3, s34, after the edge device completes the upgrade command, the edge device will actively report the execution result to the IoT management platform. The edge device publishes Topic: / v1 / ${edgeId} / device / data. The instruction format is attached. Figure 2 , where the type field value is: CMD_SYS_UPGRADE_RESULT (device upgrade result report), b) the param field includes jobId (ID assigned to the work task), result (100: installation successful 200: download failed 300: installation failed 400: upgrade program startup failed, info (description of installation failure, for example, download address is unavailable).

Claims

1. Claim 1: A remote maintenance system for edge IoT proxy devices based on the Internet of Things, the system comprising sensors, aggregation nodes, edge IoT proxy devices, security gateways, IoT management platforms, operation and inspection control platforms, and business systems.

2. Claim 2: According to the system of claim 1, the sensor communicates with the aggregation node or edge IoT agent device through a field bus, and the field bus can select RS485 bus, CAN bus, Ethernet, wireless LoRa and other communication methods.

3. Claim 3: The system according to claim 1 also includes an edge IoT proxy device that collects the "end" data, performs edge computing, data filtering, adds time stamps, uses the MQTT protocol, performs protocol conversion and data encapsulation, and then encrypts the message through the encryption APP on the edge IoT device and publishes the message to the northbound channel.

4. Claim 4: According to claim 3, the edge IoT proxy device runs a communication encryption and decryption APP, which is responsible for encrypting the message of the forward communication data entering the designated port, and restoring the message of the reverse data received by the designated port through authentication, identification, decryption and other technical means.

5. Claim 5: According to the system described in claim 1, the northbound channel of the edge IoT agent device can adopt physical channels such as 4G\5GAPN, Ethernet, WIFI private network, etc. After being transmitted to the security gateway, it is reversely decrypted and the message is uploaded to the IoT management platform. The IoT platform is deployed with an MQTT server, which is responsible for receiving and pushing information.

6. Claim 6: According to claim 5, the business system and the operation and maintenance management and control platform subscribe to relevant topics, and the MQTT server pushes the relevant main content to the business system and the operation and maintenance management and control platform to realize the uploading of edge IoT agent data messages.

7. Claim 7: According to claim 1, the business system and the operation and maintenance control platform publish equipment management, container management, business interaction, application management, and device management messages to the Internet of Things management platform, and the edge IoT agent device subscribes to relevant subject messages to achieve control of the edge IoT agent device and the "end" device by the business system and the operation and maintenance control platform.

8. Claim 8: According to the system described in claim 1, the edge IoT agent device has functions such as equipment management, data collection management, communication management, container management, application management, data management, security management, system maintenance, and log management. The above management functions can all be controlled by local operation or remote commands to achieve the normal operation of the edge agent.

9. Claim 9: According to the subscription message of claim 6, the body format is: / topic version / edge device or directly connected device ID / message execution category / message action, and the corresponding instruction field is: {v1} / {edgeId} / {Topic Type} / {TopicCommand}.

10. Claim 10: According to the main format of claim 6: the meaning of the message subscription instruction field is: {v1}: indicates that the currently defined topic version is v1; {edgeId}: indicates the edge device or direct device ID that directly establishes an MQTT long connection with this system, and the ID is unique within the device and channel-aware IoT management platform, that is, the edge IoT agent code; {Topic Type}: Topic categories, mainly including device, container, app, service, and topo. Device indicates that the topic is a device-type message, service indicates a business-type message, app indicates an application-type message, container indicates a container message, and topo indicates a topology-type message; {Topic Command}: indicates the action of the message such as control, collected data, request or response.