Unified multi-protocol intelligent terminal equipment management method and device

Abstract

The invention relates to the technical field of intelligent terminal equipment management, and particularly provides a unified multi-protocol intelligent terminal equipment management method and device, and the method comprises the steps: firstly, enabling a protocol access module to serve as message middleware to integrate an MQTT Broker and an STOMP Broker, and receiving data from equipment; then, the protocol adapter module is used for converting data from equipment into a format which can be processed by the message bus module from a used protocol so as to realize conversion between protocols and message routing, and finally, the service processing module is used for processing and storing the equipment data; wherein the message bus module provides message transmission between components or services. Compared with the prior art, the equipment management process can be simplified, the management efficiency is improved, the management cost is reduced, real-time data processing and analysis are supported, and the reliability and stability of the system are enhanced.

Description

Technical Field

[0001] This invention relates to the field of smart terminal device management technology, specifically providing a unified multi-protocol smart terminal device management method and apparatus. Background Technology

[0002] With the rapid development of Internet of Things (IoT) technology, the types and numbers of smart terminal devices have exploded, encompassing home broadband gateways (CPE), optical network terminals (ONT), and various IoT devices. These devices typically support multiple communication protocols, such as MQTT, WebSocket, and STOMP.

[0003] However, existing equipment management systems often only support one or a few communication protocols, resulting in complex equipment management and difficulty in unified monitoring and control. Summary of the Invention

[0004] This invention addresses the shortcomings of the prior art by providing a highly practical unified multi-protocol smart terminal device management method.

[0005] A further technical objective of this invention is to provide a reasonably designed, secure, and applicable unified multi-protocol smart terminal device management device.

[0006] The technical solution adopted by this invention to solve its technical problem is: A unified multi-protocol smart terminal device management method is proposed. First, the protocol access module, as a message middleware, integrates MQTT Broker and STOMP Broker to receive data from the device. Then, the data from the device enters the protocol adapter module to convert the data from the device into a format that the message bus module can process, realizing protocol conversion and message routing. Finally, the data enters the business processing module to process and store the device data. The message bus module provides a means for message passing between components or services.

[0007] Furthermore, the protocol access module is responsible for receiving and forwarding messages between the device and the management platform, performing bidirectional communication between the platform and the device, and forwarding messages received by the Broker to the management platform.

[0008] Furthermore, the protocol adapter module maps the topic or destination sent by the device to the subject of the message bus, and is responsible for data formatting and decoupling.

[0009] Furthermore, the message bus module provides message passing between components or services, including publishing, subscribing, requesting, responding, and queue groups. It adopts a topic-based message routing strategy and identifies the source of the message and the access controller through a hierarchical topic naming rule.

[0010] Furthermore, the business processing module performs device registration, parameter management, command issuance, data collection and analysis, and log management; The device registration is responsible for the registration and authentication of the devices; The parameter management is based on the TR-369 protocol and performs operations such as querying, setting, and updating device parameters; The command is issued to send various control commands to the device; The data acquisition and analysis process periodically collects, stores, and analyzes equipment status and performance indicators from the devices. The log management system records the device's operation logs and the management platform's operation logs.

[0011] Furthermore, the linking phase includes: (1) Agent (CPE) device management page configuration: On the Agent (CPE) device management page, enable the TR-369Agent function and complete the following configuration: Configure the connection information for the MQTT Broker; Set Endpoint ID and Topic; (2) The Agent (CPE) establishes a two-way TLS secure connection through the MQTT Broker; (3) The Agent initiates a connection to the Broker (Connect), and the Broker confirms the connection (Connect ACK).

[0012] Furthermore, the subscription phase includes: (1) The Agent subscribes to the topic used to receive Controller instructions (SUB usp / v1 / agent / {agent-endpoint-id}), and the Broker confirms the subscription is successful (SUB ACK). (2) The Controller subscribes to the topic (SUB usp / v1 / controller / +) used to receive information reported by the Agent, and the Broker confirms the subscription is successful (SUB ACK).

[0013] Further, device information requests include: (1) When the Agent (CPE) device is powered on and started, it will actively report the Boot event and the device's Endpoint ID (agent-endpoint-id) to the management platform, thereby informing the management platform that the device is online and in standby mode, ready to receive further instructions and conduct information interaction; (2) After receiving the Boot event and Endpoint ID reported by the Agent device, the management device will immediately start the device information acquisition process. The device registration in the business processing module will encapsulate a basic event for acquiring parameters. Subsequently, the event for acquiring parameters will be published to the message bus. (3) After receiving the parameter acquisition event, the message bus module converts the content of the parameter acquisition event into data that conforms to the MQTT message format through the protocol adapter module according to the protocol type and Controller ID, and encapsulates it into an MQTT message and submits it to the Controller; (4) The Controller sends a message to the Agent to retrieve information (PUB usp / v1 / agent / {agent-endpoint-id}). (5) The Agent queries the corresponding parameters and then publishes the parameter values ​​to the Controller's topic (PUB usp / v1 / controller / {agent-endpoint-id}). (6) After receiving the parameter value message reported by the Agent device, it will be parsed by the protocol adapter module to convert the MQTT protocol format data into an internal unified data format. Finally, the data parsed by the adapter is published to the message bus and eventually stored in the database.

[0014] Furthermore, when there is no actual message exchange between the device and the Broker, a heartbeat packet is sent to maintain the connection (PingREQ / PingRESP). When a user initiates an interaction, it includes: (1) Users send operation requests through web pages or APIs; (2) After receiving a user request, the business processing module encapsulates it into an operation event and publishes it to the message bus; (3) The message bus sends operation events to the protocol adapter module according to the protocol type and Controller ID; (4) The protocol adapter module converts the operation events into MQTT message format and submits them to the Controller; (5) The Controller sends the operation to the Agent (PUB usp / v1 / agent / {agent-endpoint-id}) via the MQTT Broker. After the Agent executes the operation, it returns the execution result (PUB usp / v1 / api / {unique-msg-id} / {agent-endpoint-id}). (6) The message bus receives the execution result message from the Agent, parses it through the protocol adapter, stores the result in the database, and feeds it back to the user through the Web page or API.

[0015] A unified multi-protocol smart terminal device management device includes: at least one memory and at least one processor; The at least one memory is used to store a machine-readable program; The at least one processor is used to call the machine-readable program to execute a unified multi-protocol smart terminal device management method.

[0016] Compared with the prior art, the unified multi-protocol smart terminal device management method and apparatus of the present invention have the following outstanding advantages: (1) By supporting multiple communication protocols such as MQTT, WebSocket and STOMP, this invention can be compatible with more smart terminal devices, greatly improving the system's compatibility and scalability, enabling different types of devices to be managed and controlled on the same platform, without the need to develop or configure different management systems for each device, thus reducing the complexity and cost of device management.

[0017] (2) By using message middleware to unify the interaction of different protocols, the model and interface are unified. This simplifies the equipment management process and significantly improves management efficiency. Managers can operate and monitor various devices through a unified interface, without having to switch between different systems, reducing the possibility of operational errors, and also facilitating centralized management and maintenance of equipment.

[0018] (3) This invention is based on a microservice architecture design, and the system has good scalability. When it is necessary to add new types of smart terminal devices or add new management functions, it can be easily extended and integrated without large-scale modification and reconstruction of the entire system. This flexible scalability can better adapt to the rapid changes in the smart terminal device market and the continuous updates of technology, ensuring that the system can continue to effectively meet the needs of users in the future.

[0019] (4) It supports real-time data acquisition, analysis, and log management, enabling timely acquisition of data such as the operating status and performance indicators of the equipment, and in-depth analysis of such data. This helps to quickly identify potential problems and faults in the equipment, and take preventive and handling measures in advance, thereby improving the reliability and stability of the system and reducing the risk of service interruption and data loss due to equipment failure. Attached Figure Description

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

[0021] Figure 1 This is a flowchart illustrating a unified multi-protocol smart terminal device management method. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present invention, the present invention will be further described in detail below with reference to specific embodiments. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] The following is a preferred embodiment: like Figure 1 As shown in this embodiment, a unified multi-protocol smart terminal device management method firstly integrates MQTT Broker and STOMP Broker as message middleware to receive data from the device. Then, the data from the device is converted from the protocol used by the device into a format that the message bus module can process, realizing the conversion between protocols and message routing. Finally, the data is processed and stored in the business processing module. The message bus module provides message passing between components or services.

[0024] The protocol access module, acting as a message middleware, is responsible for receiving and forwarding messages between devices and the management platform, enabling bidirectional communication between them. It integrates MQTT Broker, STOMP Broker, and other protocols to receive data from devices using different protocols. It also provides Controller creation and management functions, responsible for forwarding messages received by the Broker to the management platform.

[0025] The protocol adapter module converts data from devices from their specific protocols into a format that the message bus can process, enabling protocol conversion and message routing. The adapter maps the topics or destinations sent by the devices to the subjects on the message bus, handling data formatting and decoupling.

[0026] The message bus module facilitates message passing between components or services, supporting asynchronous message passing. It supports multiple message passing modes, including publish / subscribe, request / reply, and queue groups. It employs a subject-based message routing strategy, using hierarchical subject naming rules to accurately identify the message source and the access controller. This naming method not only helps clarify the message path but also facilitates subsequent message storage and display, enabling the system to more efficiently manage and process message streams from different protocols and controllers.

[0027] The business processing module processes and stores device data, while providing a unified API interface for device registration, parameter management, command issuance, data collection and analysis, and log management.

[0028] Device registration: New devices access the system through the protocol access module, and the device registration module in the business processing module is responsible for device registration and authentication.

[0029] Parameter Management: The parameter management module in the business processing module is based on the TR-369 protocol and supports querying, setting and updating of device parameters.

[0030] Command issuance: The command issuance module in the business processing module supports issuing various control commands to the device, such as restarting the device, upgrading firmware, and performing specific operations.

[0031] Data Acquisition and Analysis: The data acquisition module periodically collects data such as device status and performance indicators from the device, and then stores and analyzes the data.

[0032] Log Management: The log management module records the device's operation logs and the management platform's operation logs, facilitating troubleshooting and device maintenance.

[0033] The following is a specific implementation step that demonstrates the process of enabling interaction between a device and a smart terminal device via the MQTT protocol: Linking phase: (1) Agent (CPE) device management page configuration: On the Agent (CPE) device management page, enable the TR-369Agent function and complete the following configuration: MQTT Client Configuration: Configures the connection information for the MQTT Broker, including the Client ID, etc.

[0034] MQTT Controller Configuration: Set Endpoint ID and Topic.

[0035] (2) The Agent (CPE) establishes a two-way TLS secure connection through the MQTT Broker; (3) The Agent initiates a connection to the Broker (Connect), and the Broker confirms the connection (Connect ACK).

[0036] Subscription phase: (1) The Agent subscribes to the topic used to receive Controller instructions (SUB usp / v1 / agent / {agent-endpoint-id}), and the Broker confirms the subscription is successful (SUB ACK).

[0037] (2) The Controller subscribes to the topic (SUB usp / v1 / controller / +) used to receive information reported by the Agent, and the Broker confirms the subscription is successful (SUB ACK).

[0038] Device information request: (1) When the Agent (CPE) device is powered on and started, it will actively report the Boot event and the device's Endpoint ID (agent-endpoint-id) to the management platform, thereby informing the management platform that the device is online and in standby mode, ready to receive further instructions and conduct information interaction.

[0039] (2) After receiving the Boot event and Endpoint ID reported by the Agent device, the management device will immediately initiate the device information acquisition process. The device registration module or related modules in the business processing module will encapsulate a basic parameter acquisition event, which contains instructions to request basic information such as device status and parameters, as well as related parameter information. Subsequently, the parameter acquisition event is published to the message bus.

[0040] (3) After receiving the parameter acquisition event, the message bus module converts the content of the parameter acquisition event into data that conforms to the MQTT message format through the protocol adapter module according to the protocol type and Controller ID, and encapsulates it into an MQTT message and submits it to the Controller.

[0041] (4) The Controller sends a message to the Agent to retrieve information (PUB usp / v1 / agent / {agent-endpoint-id}).

[0042] (5) The Agent queries the corresponding parameters and then publishes the parameter values ​​to the Controller's topic (PUB usp / v1 / controller / {agent-endpoint-id}).

[0043] (6) After receiving the parameter value message reported by the Agent device, it will be parsed by the protocol adapter module to convert the MQTT protocol format data into an internally unified data format. Finally, the parsed data is published to the message bus and eventually stored in the database for subsequent device management and data analysis.

[0044] Survival mechanism: When there is no actual message exchange between the device and the broker, heartbeat packets are sent to maintain the connection (PingREQ / PingRESP).

[0045] User-initiated interaction: (1) Users send operation requests (such as modifying parameters or restarting the device) through Web pages or APIs.

[0046] (2) After receiving a user request, the business processing module encapsulates it into an operation event and publishes it to the message bus.

[0047] (3) The message bus module sends the operation event to the protocol adapter module according to the protocol type and Controller ID.

[0048] (4) The protocol adapter module converts the operation events into MQTT message format and submits them to the Controller.

[0049] (5) The Controller sends the operation to the Agent (PUB usp / v1 / agent / {agent-endpoint-id}) via the MQTT Broker. After the Agent executes the operation, it may return the execution result (PUB usp / v1 / api / {unique-msg-id} / {agent-endpoint-id}).

[0050] (6) The message bus module receives the execution result message from the Agent, parses it through the protocol adapter module, stores the result in the database, and feeds it back to the user through a web page or API.

[0051] Through the above modules and processes, unified management and control of various smart terminal devices can be achieved, improving management efficiency and system reliability.

[0052] Based on the above method, a unified multi-protocol smart terminal device management device in this embodiment includes: at least one memory and at least one processor; The at least one memory is used to store a machine-readable program; The at least one processor is used to call the machine-readable program to execute a unified multi-protocol smart terminal device management method.

[0053] The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can be a microprocessor or any conventional processor.

[0054] Memory is used to store computer programs and / or modules. The processor implements various functions of the electronic device by running or executing the computer programs and / or modules stored in the memory, and by accessing data stored in the memory. Memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, at least one application program required for a function, etc.; the data storage area can store data created based on the use of the terminal, etc. In addition, memory can also include high-speed random access memory, and can also include non-volatile memory, such as hard disks, RAM, plug-in hard disks, smart memory cards (SMC), secure digital cards (SD cards), flash memory cards, at least one disk storage device, flash memory devices, or other volatile solid-state storage devices.

[0055] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A unified multi-protocol smart terminal device management method, characterized in that, First, the protocol access module, acting as a message middleware, integrates MQTT Broker and STOMP Broker to receive data from the device. Then, it enters the protocol adapter module to convert the data from the device from the protocol it uses into a format that the message bus module can process, realizing protocol conversion and message routing. Finally, it enters the business processing module to process and store the device data. The message bus module provides a means for message passing between components or services.

2. The unified multi-protocol smart terminal device management method according to claim 1, characterized in that, The protocol access module is responsible for receiving and forwarding messages between the device and the management platform, performing bidirectional communication between the platform and the device, and forwarding messages received by the Broker to the management platform.

3. The unified multi-protocol smart terminal device management method according to claim 2, characterized in that, The protocol adapter module maps the topic or destination sent by the device to the subject of the message bus, and is responsible for data formatting and decoupling.

4. The unified multi-protocol smart terminal device management method according to claim 3, characterized in that, The message bus module provides message passing between components or services, including publishing, subscribing, requesting, responding, and queue groups. It adopts a topic-based message routing strategy and identifies the source of the message and the access controller through a hierarchical topic naming rule.

5. The unified multi-protocol smart terminal device management method according to claim 4, characterized in that, The business processing module performs device registration, parameter management, command issuance, data collection and analysis, and log management. The device registration is responsible for the registration and authentication of the devices; The parameter management is based on the TR-369 protocol and performs operations such as querying, setting, and updating device parameters; The command is issued to send various control commands to the device; The data acquisition and analysis process periodically collects, stores, and analyzes equipment status and performance indicators from the devices. The log management system records the device's operation logs and the management platform's operation logs.

6. The unified multi-protocol smart terminal device management method according to claim 5, characterized in that, The linking phase includes: (1) Agent (CPE) device management page configuration: On the Agent (CPE) device management page, enable the TR-369 Agent function and complete the following configuration: Configure the connection information for the MQTT Broker; Set Endpoint ID and Topic; (2) The Agent (CPE) establishes a two-way TLS secure connection through the MQTT Broker; (3) The Agent initiates a connection to the Broker (Connect), and the Broker confirms the connection (Connect ACK).

7. The unified multi-protocol smart terminal device management method according to claim 6, characterized in that, The subscription phase includes: (1) The Agent subscribes to the topic used to receive Controller instructions (SUB usp / v1 / agent / {agent-endpoint-id}), and the Broker confirms the subscription is successful (SUB ACK). (2) The Controller subscribes to the topic (SUB usp / v1 / controller / +) used to receive information reported by the Agent, and the Broker confirms the subscription is successful (SUB ACK).

8. The unified multi-protocol smart terminal device management method according to claim 7, characterized in that, Device information requests include: (1) When the Agent (CPE) device is powered on and started, it will actively report the Boot event and the device's Endpoint ID (agent-endpoint-id) to the management platform, thereby informing the management platform that the device is online and in standby mode, ready to receive further instructions and conduct information interaction; (2) After receiving the Boot event and Endpoint ID reported by the Agent device, the management device will immediately start the device information acquisition process. The device registration in the business processing module will encapsulate a basic event for acquiring parameters. Subsequently, the event for acquiring parameters will be published to the message bus. (3) After receiving the parameter acquisition event, the message bus module converts the content of the parameter acquisition event into data that conforms to the MQTT message format through the protocol adapter module according to the protocol type and Controller ID, and encapsulates it into an MQTT message and submits it to the Controller; (4) The Controller sends a message to the Agent to retrieve information (PUB usp / v1 / agent / {agent-endpoint-id}). (5) The Agent queries the corresponding parameters and then publishes the parameter values ​​to the Controller's topic (PUB usp / v1 / controller / {agent-endpoint-id}). (6) After receiving the parameter value message reported by the Agent device, it will be parsed by the protocol adapter module to convert the MQTT protocol format data into an internal unified data format. Finally, the data parsed by the adapter is published to the message bus and eventually stored in the database.

9. The unified multi-protocol smart terminal device management method according to claim 8, characterized in that, When there is no actual message exchange between the device and the Broker, a heartbeat packet is sent to maintain the connection (PingREQ / PingRESP). When a user initiates an interaction, it includes: (1) Users send operation requests through web pages or APIs; (2) After receiving a user request, the business processing module encapsulates it into an operation event and publishes it to the message bus; (3) The message bus sends operation events to the protocol adapter module according to the protocol type and Controller ID; (4) The protocol adapter module converts the operation events into MQTT message format and submits them to the Controller; (5) The Controller sends the operation to the Agent (PUB usp / v1 / agent / {agent-endpoint-id}) via the MQTT Broker. After the Agent executes the operation, it returns the execution result (PUB usp / v1 / api / {unique-msg-id} / {agent-endpoint-id}). (6) The message bus receives the execution result message from the Agent, parses it through the protocol adapter, stores the result in the database, and feeds it back to the user through the Web page or API.

10. A unified multi-protocol smart terminal device management device, characterized in that, include: At least one memory and at least one processor; The at least one memory is used to store a machine-readable program; The at least one processor is configured to invoke the machine-readable program to perform the method according to any one of claims 1 to 9.

Images