A multi-user power monitoring system based on MQTT

Abstract

The present invention proposes a multi-user power monitoring system based on MQTT. Based on the message publishing and subscribing mode of MQTT, it integrates application programs to implement a multi-user power monitoring system. By constructing a request / response mechanism and combining with a local caching strategy, it solves the problems of data storage and interaction; uses the MQTT communication system to integrate with enterprise WeChat, mini-programs, APPs, etc. to solve the network configuration problem; adopts the DES symmetric encryption algorithm for data encryption and topic traffic control to ensure data security; integrates functions such as data query, message reception and instruction issuance on the enterprise WeChat platform to improve the user experience. The present invention effectively solves the problems existing in the existing power monitoring system in aspects such as data storage, network configuration, data communication and security, and function integration, and significantly improves the security, convenience and user experience of the system.

Description

Technical Field

[0001] The present invention relates to the field of power monitoring, and particularly to a multi-user power monitoring system based on MQTT. Background Art

[0002] In the current development process of power monitoring systems, a series of key problems need to be urgently solved, which seriously restrict the performance, security and user experience of the systems.

[0003] I. Difficulty in data storage: Traditional power monitoring systems highly rely on MQTT and databases of cloud servers to store data. This not only significantly increases the costs of enterprises in server leasing, maintenance and data storage, but also brings serious data management risks. Once the cloud server fails, suffers from a cyber attack or experiences a data leakage incident, the power monitoring data of users will face the great risks of being lost or illegally obtained, seriously threatening the stable operation of the power system and the privacy security of user data. In addition, the way of storing the power data of each tenant of each power monitoring system on the server side does not conform to the data asset management security regulations, causing potential security risks to the power data assets of tenants. Each power customer hopes that the power monitoring data can preferably be stored in the database of the enterprise's local system.

[0004] II. Dilemma in network configuration: If the power monitoring data is stored in the server of the enterprise user's power monitoring system, the existing power monitoring systems require users to equip their own public IP addresses, domain names and separate application programs to provide data query, SMS reminder and instruction issuance. However, for many small enterprises or users, obtaining public IP addresses, domain names and application program management and maintenance requires cumbersome application procedures and additional cost expenditures, which undoubtedly greatly increases the usage threshold. At the same time, maintaining the application program accounts separately also requires certain human and time costs, seriously restricting the wide popularization and promotion of power monitoring systems. For a conventional frp mode network pass-through solution, power customers also need to apply for a cloud server, with complex configuration and certain security risks, which is not conducive to the realization of compliance functions of various query applications of the application program.

[0005] III. Data communication and security hazards: When using MQTT for data communication, there are many disadvantages. The broadcast message transmission mode of MQTT makes the data extremely easy to be eavesdropped by others, especially the sensitive data of power monitoring. Once illegally obtained, it is very likely to be used for malicious attacks or damage to the power system. In addition, as the number of users and devices accessing the system continues to climb, the data traffic will increase sharply, which may cause network congestion and seriously affect the real-time performance and stability of data transmission. Moreover, it is difficult to achieve effective security isolation for the data of different power companies during the transmission and storage processes.

[0006] IV. Insufficient function integration: Traditional power monitoring systems often implement functions such as power monitoring data query, application short message reception, and instruction issuance separately, lacking effective integration. This results in users having to frequently switch between different systems or platforms during use, with cumbersome operations, seriously reducing work efficiency. In addition, data interaction and collaboration between different functions are difficult, unable to meet users' needs for convenient and efficient management of power monitoring systems. Summary of the Invention

[0007] The present invention aims to propose a multi-user power monitoring system based on MQTT to effectively solve the problems existing in existing power monitoring systems in aspects such as data storage, network configuration, data communication and security, and function integration, significantly improving the security, convenience, and user experience of the system. The technical solutions provided by the present invention are as follows:

[0008] A multi-user power monitoring system based on MQTT includes the following modules:

[0009] Data interaction module: The user side initiates a query request, sends the query conditions and user ID to the operation and maintenance company server through WebSocket; the operation and maintenance company server finds the site to which the device belongs according to the query conditions and user ID, packages and publishes the query conditions and user ID to the [ / elec / device / get / {StationID}] topic of the cloud MQTT server; the user power monitoring system listens to the relevant topics of the site to which the device belongs subscribed to by the cloud MQTT server, obtains data according to the query conditions and user ID, and publishes the data to the [ / elec / device / get_reply / {StationID}] topic of the cloud MQTT server; after the operation and maintenance company server monitors this topic, it returns the data to the user side for display through WebSocket;

[0010] Network communication module: The user power monitoring system acts as an MQTT client, creates and subscribes to specific MQTT topics based on the user ID; the operation and maintenance company realizes the conversion between operation requests and MQTT messages through the application program; the user side connects to the Internet through the internal network configuration and port mapping of the operation and maintenance company server, without the need for a public network IP and domain name;

[0011] Security and traffic control module: Encrypts MQTT communication data, sets up a password authentication mechanism; sets the data of different user sides as different MQTT topics to control the number of concurrent requests;

[0012] Function implementation module: Includes a data query unit, a short message alarm unit, and an instruction issuance unit, specifically:

[0013] Data query unit: Design a data query interface in the application program, and display the query results from the data interaction module in pages and perform data statistical analysis;

[0014] SMS alarm unit: The MQTT server pushes important real-time data change information to the operation and maintenance company's server through the [ / elec / device / alarm / {StationID}] topic, and then the operation and maintenance company's server sends SMS messages to notify the user side;

[0015] Instruction issuing unit: Design an instruction issuing interface, check the legality of the instructions, and record the instruction execution information.

[0016] Preferably, the user power monitoring system includes a server or a workstation, and the user power monitoring system sets up a local cache for storing historical data; the operation and maintenance company's server sets up a local temporary cache for temporarily storing data frequently queried recently.

[0017] Preferably, in the data interaction module, text data is directly returned, and picture data is returned using Base64 encoding.

[0018] Preferably, in the network communication module, the MQTT client regularly sends heartbeat packets to the server to maintain the connection.

[0019] Preferably, in the security and traffic control module, SSL / TLS encryption protocol is used for encryption.

[0020] Preferably, in the data query unit, data statistical analysis includes calculating the average value, maximum value, minimum value and standard deviation, and presenting them in the form of charts or tables.

[0021] Preferably, in the SMS alarm unit, the SMS message includes device warning information and maintenance notice, and the application program sets up a message reminder mechanism.

[0022] Preferably, in the instruction issuing unit, after the user inputs an instruction at the user side, the application program checks the legality of the instruction. After the check passes, the instruction is converted into a WebSocket message together with the user ID and sent to the server of the operation and maintenance company. After receiving the message, the server of the operation and maintenance company performs a secondary verification. After the secondary verification passes, the instruction is sent to the topic

/ elec / device / set / {UserID} / {StationID}

/ sys / thing / node / property / set / {UserID} / {GetwayID}

/ sys / thing / node / property / set_reply / {UserID} / {GetwayID}

/ elec / device / set_reply / {UserID} / {StationID}

[0023] Preferably, in the instruction issuing unit, the instruction legality check includes instruction format, instruction content, and instruction permissions.

[0024] Preferably, in the instruction issuing unit, during the instruction issuing process, information such as the instruction sending time, instruction content, receiving device, execution result, and execution time is recorded.

[0025] Compared with the prior art, the beneficial effects achieved by the present invention are as follows:

[0026] First, it does not rely on the cloud database to store data, effectively reducing the data management cost and risk, and at the same time ensuring the privacy and security of user data. Users can flexibly manage their historical data through the local cache mechanism, avoiding data loss or leakage caused by cloud server problems; the server side does not need to save the data of each power monitoring system workstation, reducing the storage pressure on the power operation and maintenance company, and more effectively ensuring the data security of each power company.

[0027] II. Users do not need to own a public IP address, domain name, and separate application programs, which reduces the usage threshold and cost. As an intermediate bridge, the operation and maintenance company's server enables user devices to communicate with the system as long as they can connect to the Internet. This facilitates the use by small enterprises and users and realizes rich query applications without complex network passthrough modes, improving the simplicity and security of network configuration.

[0028] III. By adopting encryption and password authentication mechanisms, it effectively prevents data from being eavesdropped and ensures the security of data communication. Through topic differentiation and traffic control, it avoids the problem of excessive traffic and ensures the real-time and stable transmission of power monitoring data. Combined with local data storage, it comprehensively guarantees the data security of each power company.

[0029] IV. Functions such as power monitoring data query, application program short message reception, and instruction issuance are integrated on the application program platform, meeting the personalized needs of different users and improving the usage efficiency and convenience of the system. Users can complete various operations of the power monitoring system without switching between multiple systems. At the same time, based on the design of user ID and independent MQTT topics, it further improves the accuracy and efficiency of function implementation. Through data statistical analysis and visual display, it is convenient for users to quickly understand the operation status of equipment and make scientific decisions. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation to the present invention. In the drawings:

[0031] Figure 1 is the data interaction flowchart of the data interaction module of the present invention;

[0032] Figure 2 is the data interaction flowchart of the short message alarm unit of the present invention;

[0033] Figure 3 is the data interaction flowchart of the instruction issuance unit of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0034] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0035] To make the above objects, features, and effects of the present invention more obvious and understandable, the present invention will be further described in detail below with reference to the drawings and specific embodiments.

[0036] Embodiment 1: A multi-user power monitoring system based on MQTT, comprising the following modules:

[0037] Data interaction module: As shown in Figure 1 , the client initiates a query request, and sends the query conditions and user ID to the operation and maintenance company server through WebSocket; the operation and maintenance company server finds the station to which the device belongs according to the query conditions and user ID, and packages and publishes the query conditions and user ID to the [ / elec / device / get / {StationID}] topic of the cloud MQTT server; the user power monitoring system includes a server or a workstation, the user power monitoring system listens to the relevant topics subscribed to by the device's affiliated station on the cloud MQTT server, obtains data according to the query conditions and user ID, and publishes the data to the [ / elec / device / get_reply / {StationID}] topic of the cloud MQTT server; after the operation and maintenance company server monitors this topic, it returns the data to the client for display through WebSocket. For text data, it is directly returned, and for picture data, it is returned using Base64 encoding.

[0038] In view of not relying on cloud database storage, the user power monitoring system sets up a local cache to store historical data; the operation and maintenance company server sets up a local temporary cache to temporarily store data that is frequently queried recently. In this way, the server side does not need to save the database data of each power monitoring system workstation, and the data of each power company is retained locally, which ensures data security from the storage source and at the same time reduces the pressure on the operation and maintenance company server to store user data.

[0039] Network communication module: The user power monitoring system acts as an MQTT client, creates and subscribes to specific MQTT topics based on the user ID, such as:

[0040] [ / elec / device / get / {UserID} / {StationID}]

[0041] [ / elec / device / get_reply / {UserID} / {StationID}] is used for data query and reception,

[0042] [ / elec / device / set / {UserID} / {StationID}]

[0043] [ / elec / device / set_reply / {UserID} / {StationID}] is used for receiving instructions, etc. The MQTT client periodically sends heartbeat packets to the server to maintain the connection.

[0044] The operation and maintenance company realizes the conversion between operation requests and MQTT messages through an application program. The user's power monitoring system server or workstation only needs to have the ability to connect to the Internet. The operation and maintenance company's server acts as an intermediate bridge and is responsible for communicating with the user's equipment. The user's equipment does not require a public IP address and domain name. The operation and maintenance company's server establishes a connection with the user's equipment through internal network configuration and port mapping and other methods.

[0045] Security and traffic control module: Encrypts the MQTT communication data. For example, it uses the SSL / TLS encryption protocol and the DES symmetric encryption algorithm to encrypt the data to prevent data eavesdropping, ensure that the data is not stolen or tampered with during transmission, protect the privacy of users and the security of the power system, and regularly updates the encryption key to improve encryption security.

[0046] Set up a user authentication mechanism on the MQTT server side. When the user's equipment connects to the MQTT server, it needs to provide the correct username and password. Only the equipment that passes the authentication can communicate with the server, preventing illegal equipment from accessing the system.

[0047] Allocate an independent MQTT topic for each user terminal to ensure that the data traffic of different user terminals is isolated from each other. Regularly check the usage of topics, clean up invalid or abnormal topics, and optimize the topic management strategy. Through the setting of topics, achieve precise management and control of different user data, and improve the security and stability of the system.

[0048] Control the traffic at the same time by setting the concurrent connection number and message processing rate of the MQTT server. Avoid network congestion caused by excessive traffic, ensure the real-time and reliability of data transmission. According to the system operation situation, dynamically adjust the traffic control parameters, optimize the system performance, and use traffic shaping, queue management and other technologies to classify different types of traffic to ensure the priority transmission of critical business traffic.

[0049] Function implementation module: Includes a data query unit, a short message alarm unit and an instruction issuing unit. Specifically:

[0050] Data Query Unit: In the application, a data query interface is designed. After the user inputs query conditions (such as site name, monitoring device name, variable name, time range, etc.), the application first performs format verification on the user input content to ensure it conforms to the system's preset query rules. After passing the verification, the user ID and query conditions are encapsulated into a WebSocket message and sent to the server of the operation and maintenance company. After receiving the message, the server of the operation and maintenance company determines the corresponding data request source based on the query conditions and user ID in the message. Subsequently, in the mapping table of user ID, site ID, and MQTT topic maintained locally by the server, it accurately locates the topic subscribed by the client (i.e., the user's power monitoring system) responsible for processing the user's power monitoring data, sends it to the corresponding [ / elec / device / get / {UserID} / {StationID}] topic of the MQTT server, and forwards the request message to this client. After receiving the request, the server or workstation of the user's power monitoring system filters the data in the local cache or real-time monitoring data according to the query conditions. If the query conditions involve a time range, such as querying power data within the past 24 hours, the device will traverse the relevant time period data stored locally. If it involves data types, such as only querying voltage data, the device will filter out the data that meets this type. After the filtering is completed, the device returns the data to the MQTT server in the form of an MQTT message through the [ / elec / device / get_reply / {UserID} / {StationID}] topic. After the server of the operation and maintenance company monitors this topic, it forwards the data to the application through WebSocket. After receiving the data, the application displays the query results in pages, with a fixed number of data entries displayed on each page for easy user browsing. At the same time, the application performs statistical analysis on the data, such as calculating the average value, maximum value, minimum value, standard deviation, etc. of the data, and presents it intuitively to the user in the form of charts (bar charts, line charts, pie charts, etc.) or tables, facilitating the user to view and process the data.

[0051] SMS Alarm Unit: As Figure 2 shown, the operation and maintenance company can send short messages to the corresponding accounts based on the user ID for different user terminals through the message interface of the application, such as device warning messages (such as too high device temperature, abnormal current, etc.), maintenance notifications (regular maintenance reminders, fault repair notifications), etc. The MQTT server pushes important real-time data change information to the server of the operation and maintenance company through the [ / elec / device / alarm / {StationID}] topic, and then the server of the operation and maintenance company sends a short message notification to the user terminal. To ensure that users receive important information in a timely manner, the application can set a message reminder mechanism, such as sound reminder, vibration reminder, pop-up reminder, etc., and mark the unread messages for easy user viewing.

[0052] Instruction Sending Unit: As Figure 3 shown, design an instruction sending interface. After the user inputs an instruction at the user end, the application checks the legality of the instruction. After passing the check, the instruction is converted into a WebSocket message together with the user ID and sent to the operation and maintenance company's server. After receiving the message, the operation and maintenance company's server performs secondary verification. After passing the secondary verification, the instruction is sent to the [ / elec / device / set / {UserID} / {StationID}] topic of the MQTT server. After the user's power monitoring system subscribes to this topic and receives the instruction, it parses the content and determines whether it can issue an instruction to the device according to the user's permissions. If the permission passes, the instruction is reassembled into a new JSON string according to the configuration information of the device and the variable (such as the corresponding variable code and the corresponding instruction code) and sent to the [ / sys / thing / node / property / set / {UserID} / {GetwayID}] topic of the local MQTT server. After the gateway subscribes to this topic and obtains the instruction, the instruction is written into the device through the Modbus RTU / TCP or Siemens S7 protocol, and the execution result is fed back to the local MQTT server in the form of an MQTT message through the [ / sys / thing / node / property / set_reply / {UserID} / {GetwayID}] topic. After the user's power monitoring system subscribes to this topic and receives the feedback information, the feedback information is reassembled into a new JSON string and sent to the [ / elec / device / set_reply / {UserID} / {StationID}] topic of the cloud MQTT server. Finally, the operation and maintenance server listens and subscribes to this topic and forwards it to the user end through WebSocket for the operation and maintenance personnel to confirm the instruction execution status. During the instruction sending process, information such as the instruction sending time, instruction content, receiving device, execution result, and execution time is recorded for subsequent traceability and management.

[0053] Embodiment 2: This embodiment provides a specific system construction and deployment mode:

[0054] The operation and maintenance company deploys high-performance servers, installs the environment and tools required for MQTT Broker and enterprise WeChat application deployment, such as development language environment, database management system, etc. Configure the network parameters of the server to ensure network stability, and set strict security policies, such as firewall rules, access permission control, etc. Set up a mapping relationship table between user ID, site ID and MQTT topic in the MQTT server to facilitate fast and accurate message forwarding. At the same time, to improve the reliability and scalability of the system, a distributed cluster architecture can be used to deploy the servers to achieve load balancing and failover.

[0055] Install the MQTT client software on the user power monitoring system server or workstation to ensure that the device can be stably connected to the Internet. Make necessary configurations for the device so that it can automatically connect to the MQTT server according to the preset user ID at startup and subscribe to the corresponding topics. Conduct comprehensive tests after the configuration is completed, including network connection tests, data transmission tests, function tests, etc., to ensure normal communication between it and the operation and maintenance company's server.

[0056] The user side uses WeCom to interact with the operation and maintenance company's server. The operation and maintenance company develops corresponding application programs using the interfaces of WeCom. Users operate through this application program in WeCom, and the application program converts the user's operation requests (carrying the user ID) into MQTT messages and sends them to the corresponding user topics of the MQTT server. The MQTT server then forwards the requests to the corresponding user power monitoring system server or workstation. This embodiment abandons the network passthrough mode similar to the frp mode and realizes the smooth operation of various query applications in WeCom through a unique integration method of MQTT and WeCom, reducing the complexity and risks of network configuration.

[0057] The above are only the preferred embodiments of the present invention and are not used to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions recorded in the foregoing embodiments or perform equivalent replacements for some of the technical features. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A multi-user power monitoring system based on MQTT, characterized in that, It includes the following modules: Data interaction module: The user side initiates a query request and sends the query conditions and user ID to the server of the operation and maintenance company through WebSocket; The server of the operation and maintenance company finds the site to which the device belongs according to the query conditions and user ID, packages and publishes the query conditions and user ID to the [ / elec / device / get / {StationID}] topic of the cloud MQTT server; The user power monitoring system listens to the relevant topics of the site to which the device belongs subscribed by the cloud MQTT server, obtains data according to the query conditions and user ID, and publishes the data to the [ / elec / device / get_reply / {StationID}] topic of the cloud MQTT server; After the server of the operation and maintenance company monitors this topic, it returns the data to the user side for display through WebSocket; Network communication module: The user power monitoring system acts as an MQTT client, creates and subscribes to specific MQTT topics based on the user ID; The server of the operation and maintenance company realizes the conversion between query requests or instructions and MQTT messages through the application program; The user side connects to the Internet through the internal network configuration and port mapping of the server of the operation and maintenance company without a public IP and domain name; Security and traffic control module: Encrypts the MQTT communication data and sets up a password authentication mechanism; Sets different MQTT topics for the data of different user sides and controls the number of concurrent requests; Function implementation module: It includes a data query unit, a short message alarm unit and an instruction issuing unit. Specifically: Data query unit: Designs a data query interface in the application program, and displays the query results from the data interaction module in pages and conducts data statistical analysis; Short message alarm unit: The MQTT server pushes important real-time data change information to the server of the operation and maintenance company through the [ / elec / device / alarm / {StationID}] topic, and then the server of the operation and maintenance company sends a short message to notify the user side; Instruction issuing unit: Designs an instruction issuing interface, checks the legality of the instructions, and records the instruction execution information.

2. The multi-user power monitoring system based on MQTT according to claim 1, characterized in that, The user power monitoring system includes a server or workstation. The user power monitoring system sets up a local cache to store historical data; The server of the operation and maintenance company sets up a local temporary cache to temporarily store the data frequently queried recently.

3. A multi-user power monitoring system based on MQTT according to claim 2, characterized in that, In the data interaction module, text data is directly returned, and image data is returned using Base64 encoding.

4. A multi-user power monitoring system based on MQTT according to claim 2, characterized in that, In the network communication module, the MQTT client periodically sends heartbeat packets to the cloud MQTT server to maintain the connection.

5. A multi-user power monitoring system based on MQTT according to claim 1, characterized in that, In the security and traffic control module, SSL / TLS encryption protocol is used for encryption.

6. A multi-user power monitoring system based on MQTT according to any one of claims 1-5, characterized in that, In the data query unit, data statistical analysis includes calculating the average value, maximum value, minimum value and standard deviation, and presenting them in the form of charts or tables.

7. A multi-user power monitoring system based on MQTT according to any one of claims 1-5, characterized in that, In the short message alarm unit, the short message includes device warning information and maintenance notice, and the application program sets up a message reminder mechanism.

8. A multi-user power monitoring system based on MQTT according to any one of claims 1-5, characterized in that, In the instruction issuing unit, after the user inputs an instruction, the application checks the legality of the instruction. After the check passes, the instruction is converted into a WebSocket message together with the user ID and sent to the server of the operation and maintenance company. After receiving the message, the server of the operation and maintenance company conducts a secondary verification. After the secondary verification passes, the instruction is sent to the topic 【 / elec / device / set / {UserID} / {StationID}】 corresponding to the MQTT server. After the user power monitoring system subscribes to this topic and receives the instruction, it parses the content and determines whether it can issue an instruction to the device according to the user's permissions. If the permission passes, the instruction is reassembled into a new JSON string according to the variable code and instruction code corresponding to the device and sent to the topic 【 / sys / thing / node / property / set / {UserID} / {GetwayID}】 of the local MQTT server. After the gateway subscribes to this topic and obtains the instruction, the instruction is written into the device through the Modbus RTU / TCP or Siemens S7 protocol, and the execution result is fed back to the local MQTT server in the form of an MQTT message through the topic 【 / sys / thing / node / property / set_reply / {UserID} / {GetwayID}】. After the user power monitoring system subscribes to this topic and receives the feedback information, the feedback information is reassembled into a new JSON string and sent to the topic 【 / elec / device / set_reply / {UserID} / {StationID}】 of the cloud MQTT server. Finally, the server of the operation and maintenance company listens and subscribes to this topic and forwards it to the user side through WebSocket.

9. The multi-user power monitoring system based on MQTT according to claim 8, characterized in that, In the instruction issuing unit, the instruction legality check includes instruction format, instruction content, and instruction permissions.

10. A multi-user power monitoring system based on MQTT according to claim 8, characterized in that, In the instruction issuing unit, during the instruction issuing process, information such as the instruction sending time, instruction content, receiving device, execution result, and execution time is recorded.

Images