Multi-sensor data display method and device, equipment and medium

By introducing a front-end machine and MQTT Broker server in the multi-sensor data display system, the subscription/publishing function of the MQTT protocol is used to solve the complex data processing and bandwidth waste caused by WebSocket technology, and efficient and reliable multi-client data is achieved. Transmission reduces system complexity and cost.

CN118921384APending Publication Date: 2024-11-08STATE GRID BEIJING ELECTRIC POWER CO +2
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

The real-time display of existing multi-sensor data on different clients uses WebSocket technology, resulting in complex data processing and waste of bandwidth, increasing the load on servers and clients.

Method used

Using the front-end machine and the MQTT Broker server, the front-end machine acquires sensor data and transmits the data to the client through the MQTT Broker server according to the client's requirements, decouples the association between the sensor and the client, simplifies the data transmission logic, and uses the subscription of the MQTT protocol. /Publishing function implements data filtering and routing.

Benefits of technology

It reduces bandwidth consumption, simplifies data transmission logic, improves system reliability and maintainability, reduces development costs, and makes full use of the original concentrator and sensor hardware resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921384A_ABST
    Figure CN118921384A_ABST
Patent Text Reader

Abstract

The invention belongs to the technical field of power data display, and particularly discloses a multi-sensor data display method and device, equipment and a medium. A multi-sensor data display method comprises the following steps that a front-end processor is deployed, and the front-end processor obtains data of a plurality of sensors; the MQTT Broker server is deployed, and the MQTT Broker server obtains a demand instruction of the client side and sends the demand instruction of the client side to the front-end processor; and the front-end processor displays the sensor data required by the client on the client through the MQTT Broker server according to the requirement instruction. Data between the sensors and the clients are transmitted through the front-end processor and the MQTT Broker, association between the sensors and the clients is decoupled, the structure is simple, the bandwidth is low, the data are finally transmitted to the multiple clients in real time through the MQTT Broker, original concentrator and sensor software and hardware can be fully utilized, and cost is saved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of power data display, and specifically relates to a multi-sensor data display method, device, equipment and medium. Background Art

[0002] In IoT applications, it is often necessary to display the information received by multiple sensors to more than one client. This involves the problem of displaying different sensor information in real time on multiple clients. The current mainstream display is the Web client, and real-time push messages to Web clients mostly use WebSocket technology. For multiple clients, it is required to display different sensor data. It is necessary to send each client's personalized configuration parameters to the server to obtain the data required by the client. The server needs to design complex processing logic, which is a lot of work. If WebSocket does not send all data in a classified manner, it will inevitably cause great pressure on the network bandwidth and the client, wasting bandwidth and client resources, and the client's logic for filtering the data required by users will also become complicated. Summary of the invention

[0003] The purpose of the present invention is to provide a multi-sensor data display method, device, equipment and medium to solve the technical problem that the existing multi-sensor display often uses WebSocket when on different clients, resulting in complex data processing and bandwidth waste.

[0004] To achieve the above object, the present invention adopts the following technical solutions:

[0005] In a first aspect, the present invention provides a multi-sensor data display method, comprising the following steps:

[0006] Deploy a front-end machine, which acquires data from several sensors.

[0007] Deploy the MQTT Broker server, which obtains the client's demand instructions and sends the client's demand instructions to the front-end;

[0008] The front-end processor displays the sensor data required by the client on the client through the MQTT Broker server according to the demand instructions.

[0009] A further improvement of the present invention is that it also includes arranging a Web application server, wherein the Web application server is used to verify the user authority of the client.

[0010] A further improvement of the present invention is that it also includes a database, which is communicatively connected to the front-end processor and is used to store the subject matter in the demand instruction.

[0011] A further improvement of the present invention is that: the step of acquiring data from a plurality of sensors further includes a concentrator, the plurality of sensors are communicatively connected to the concentrator, and the concentrator is communicatively connected to the front-end processor.

[0012] A further improvement of the present invention is that the plurality of sensors and the concentrator communicate with each other using RS485 or MBUS.

[0013] A further improvement of the present invention is that the step of the front-end processor acquiring a plurality of sensor data comprises:

[0014] The front-end acquires the initial sensor data, determines whether there is a new sensor registration in the initial sensor data, and if there is a new sensor registration, creates an abstract entity of the new sensor and stores the abstract entity of the new sensor in the sensor abstract list;

[0015] When the front-end receives sensor data, if the corresponding abstract entity does not exist in the sensor abstract list, the data is discarded;

[0016] If an abstract entity exists, determine whether the abstract entity is bound to the client that needs to receive data. If the abstract entity is already bound to the client, publish the sensor data to the corresponding client. When multiple clients are bound to an abstract entity at the same time, publish the sensor data to multiple clients in turn.

[0017] A further improvement of the present invention is that: the step of deploying the MQTT Broker server, the MQTT Broker server obtaining the client's demand instruction, and sending the client's demand instruction to the front-end, and the front-end displaying the sensor data required by the client on the client through the MQTT Broker server according to the demand instruction, includes:

[0018] Get the MQTT Broker server parameters;

[0019] The front-end establishes an MQTT connection with the MQTT Broker server according to the MQTT Broker server parameters. If the connection fails, it will retry until it succeeds.

[0020] The MQTT Broker server obtains the client's request instructions;

[0021] The MQTT Broker server sends the demand instruction to the corresponding abstract entity in the front-end according to the subject of the demand instruction;

[0022] The corresponding abstract entity in the front-end obtains the corresponding sensor data according to the required instructions and uploads it to the M QTTBroker server;

[0023] The MQTT Broker server uploads the corresponding sensor data to the client.

[0024] In a second aspect, the present invention provides a multi-sensor data display device, comprising:

[0025] Client: used to generate demand instructions, send demand instructions to the MQTT Broker server, and display sensor data;

[0026] MQTT Broker server: used to send demand instructions to the front-end processor and upload sensor data sent by the front-end processor to the client;

[0027] Front-end processor: used to upload corresponding sensor data to the MQTT Broker server according to the required instructions.

[0028] In a third aspect, the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned multi-sensor data display method when executing the computer program.

[0029] In a fourth aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned multi-sensor data display method is implemented.

[0030] Compared with the prior art, the present invention has at least the following beneficial effects:

[0031] The present invention transmits data between sensors and clients through a front-end machine and an MQTT Broker, decouples the association between sensors and clients, has a simple structure, and has low bandwidth. Finally, data is transmitted to multiple clients in real time through an MQTT Broker, and the original concentrator and sensor hardware and software can be fully utilized, thus saving costs.

[0032] By constructing an abstraction of the physical sensor in the memory of the front-end machine, virtualizing the sensor, and connecting to the subscription / publishing function of MQTT, it is possible for the client to subscribe to the changes in the virtual sensor data in real time. When the front-end machine receives the physical sensor data, the corresponding virtual sensor publishes a data to the client, thus completing the real-time publishing of the sensor data to the client. Compared with the current use of interpreters or rule-based data forwarding, the program logic is easier to understand, reducing the complexity of the software and improving the reliability and maintainability of the software.

[0033] Simple and reliable: By using MQTT broker to filter and route subscription / publish topics, the message transmission development process between the front-end and the client is simplified. Using websocket requires developers to add code to implement the filtering and routing of sensor data required by the client, while using MQTT's built-in topic filtering and routing reduces development costs and increases reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0035] In the attached picture:

[0036] Figure 1 A flowchart of a multi-sensor data display method of the present invention;

[0037] Figure 2 It is a structural block diagram of a multi-sensor data display device of the present invention;

[0038] Figure 3 A schematic diagram of a front-end processor and a client in a multi-sensor data display method of the present invention. DETAILED DESCRIPTION

[0039] The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that the embodiments and features in the embodiments of the present invention can be combined with each other without conflict.

[0040] The following detailed description is an exemplary description, which is intended to provide further detailed description of the present invention. Unless otherwise specified, all technical terms used in the present invention have the same meaning as those generally understood by those skilled in the art to which the present invention belongs. The terms used in the present invention are only for describing specific embodiments, and are not intended to limit the exemplary embodiments according to the present invention.

[0041] Example 1

[0042] A multi-sensor data display method, such as Figure 1 As shown, the following steps are included:

[0043] Deploy a front-end machine, which acquires data from several sensors.

[0044] Deploy the MQTT Broker server, which obtains the client's demand instructions and sends the client's demand instructions to the front-end;

[0045] The front-end processor displays the sensor data required by the client on the client through the MQTT Broker server according to the demand instructions.

[0046] Specifically, it also includes: deploying Web application servers, which are used to verify the identity of users and manage user permissions. Processing business logic, including verifying user input, performing calculations, generating reports, and then sending them to the front-end for display. It interacts with the front-end server using TCP / IP. Some tasks that cannot be processed by the Web application server (such as users actively requesting real-time data) will be transferred to the front-end server for processing, and the front-end server will wait for the results to be returned before sending them to the client for display.

[0047] Specifically, it also includes a database, which is used to store the topic in the demand instruction. The topic in the demand instruction is the personalized configuration service for receiving sensor data by the client. The payload format of this topic is JSON format, and the content is {"client":clientId, "subscribeSenserId":SenserId, "SenserType":SenserType, "SenserDataType":SenserDataType}, which means that the client identified as clientId listens to the data of type SenserDat aType of the sensor with the SenserType identified as SenserId. The front-end will configure the association between the client and the abstract sensor entity and data type in the memory, and write the topic published by the client into the database. The front-end can then directly read the database to load the topic configuration previously published by the client to topic / client / config.

[0048] Specifically, the sensor data includes electricity meter data, gas meter data, heat meter data, etc.

[0049] Specifically, the step of obtaining data from a plurality of sensors further includes a concentrator, wherein the plurality of sensors are communicatively connected to the concentrator, and the concentrator is communicatively connected to the front-end processor;

[0050] Several sensors and the concentrator communicate using RS485 or MBUS, without the need for an MQTT protocol stack. The cost of data transmission between each sensor and the front-end processor is reduced by setting up a concentrator.

[0051] Specifically, MQTT Broker is an intermediary entity that is responsible for the communication between the front-end MQTT module and the client MQTT. MQTT Broker receives messages published by the front-end MQTT module, filters the messages according to the topic, and then distributes them to the client subscribers. By using MQTT Broker to implement the publish / subscribe communication model, the efficiency and scalability of the MQTT protocol can be significantly improved.

[0052] Specifically, the client is written using the front-end framework Vue, which can communicate with the Web application server through AJAX technology, allowing users to actively request sensor lists and data items, communicate with the MQTT Broker through MQTT, subscribe to data topics that users are interested in, and display changes in sensor data in real time.

[0053] Specifically, Figure 3 As shown, the steps of deploying a front-end processor and obtaining data from several sensors include:

[0054] The front-end acquires the initial sensor data, determines whether there is a new sensor registration in the initial sensor data, and if there is a new sensor registration, creates an abstract entity of the new sensor and stores the abstract entity of the new sensor in the sensor abstract list;

[0055] When the front-end receives sensor data, if the corresponding abstract entity does not exist in the sensor abstract list, the data is discarded;

[0056] If an abstract entity exists, determine whether the abstract entity is bound to the client that needs to receive data. If the abstract entity is already bound to the client, publish the sensor data to the corresponding client. When multiple clients are bound to an abstract entity at the same time, publish the sensor data to multiple clients in turn.

[0057] Specifically, deploying an MQTT Broker server, the MQTT Broker server obtains the client's demand instructions, and sends the client's demand instructions to the front-end. The front-end displays the sensor data required by the client on the client through the MQTT Broker server according to the demand instructions, including the following steps:

[0058] Get the MQTT Broker server parameters;

[0059] The front-end establishes an MQTT connection with the MQTT Broker server according to the MQTT Broker server parameters. If the connection fails, it will retry until it succeeds.

[0060] The MQTT Broker server obtains the client's request instructions;

[0061] The MQTT Broker server sends the demand instruction to the corresponding abstract entity in the front-end according to the subject of the demand instruction;

[0062] The corresponding abstract entity in the front-end obtains the corresponding sensor data according to the required instructions and uploads it to the M QTTBroker server;

[0063] The MQTT Broker server uploads the corresponding sensor data to the client.

[0064] The front-end receives sensor data from the concentrator. When the sensor data changes, it publishes the topic data to the MQTT Broker according to the topic configuration of to pic / client / config. The topic to pic / {clientId} / data is published. The {clientId} is the client ID, and the Payload content is {“Sens erId”:SenserId, “SenserType”:SenserType, “data”:{data content entity}}. The {clientId} in topic / {clientId} / data in the topic will be automatically routed by the MQTT Broker to the client identified as clientId. For example, if the data published as topic / 1 / data is published, it will be routed by the MQTT Broker to the client identified as 1.

[0065] Specifically, the workflow for deploying a Web application server is as follows:

[0066] Get the MQTT Broker server parameters;

[0067] Introduce Vue into the mqttjs library in the Web application server, and establish an MQTT connection with the MQTTBroker server according to the MQTT Broker server parameters. If the connection fails, retry until it succeeds.

[0068] The mqttjs library is an open source client library for the MQTT protocol. The client creates an MQTT connection and specifies the address and port number of the MQTTBroker to attempt a connection.

[0069] After the connection is successful, the client can publish the topic / client / config to the MQTT Broker according to user needs. After the front-end receives the topic published by the client, it will process it according to step 3 of the "Front-end Processing Flow".

[0070] The client subscribes to the topic topic / {clientId} / data, where {clientId} is its own ID. If client 1 wants to monitor its own events, the subscribed topic instance is topic / 1 / data. When the current machine publishes the data of the topic topic / {clientId} / data, it is automatically routed to the client after being filtered by the MQTT Broker. The client {clientId} will receive the message immediately. By reading the MQTT message queue, Vue will render the data in real time and present it to the client. If the user needs to request historical data, he can interact with the Web application server through AJAX to request data.

[0071] Example 2

[0072] A multi-sensor data display device, such as Figure 2 As shown, including:

[0073] Client: used to generate demand instructions, send demand instructions to the MQTT Broker server, and display sensor data;

[0074] MQTT Broker server: used to send demand instructions to the front-end processor and upload sensor data sent by the front-end processor to the client;

[0075] Front-end processor: used to upload corresponding sensor data to the MQTT Broker server according to the required instructions.

[0076] Specifically, it also includes: deploying Web application servers, which are used to verify the identity of users and manage user permissions. Processing business logic, including verifying user input, performing calculations, generating reports, and then sending them to the front-end for display. It interacts with the front-end server using TCP / IP. Some tasks that cannot be processed by the Web application server (such as users actively requesting real-time data) will be transferred to the front-end server for processing, and the front-end server will wait for the results to be returned before sending them to the client for display.

[0077] Specifically, it also includes a database, which is used to store the topic in the demand instruction. The topic in the demand instruction is the personalized configuration service for receiving sensor data by the client. The payload format of this topic is JSON format, and the content is {"client":clientId, "subscribeSenserId":SenserId, "SenserType":SenserType, "SenserDataType":SenserDataType}, which means that the client identified as clientId listens to the data of type SenserDat aType of the sensor with the SenserType identified as SenserId. The front-end will configure the association between the client and the abstract sensor entity and data type in the memory, and write the topic published by the client into the database. The front-end can then directly read the database to load the topic configuration previously published by the client to topic / client / config.

[0078] Specifically, the sensor data includes electricity meter data, gas meter data, heat meter data, etc.

[0079] Specifically, the step of obtaining data from a plurality of sensors further includes a concentrator, wherein the plurality of sensors are communicatively connected to the concentrator, and the concentrator is communicatively connected to the front-end processor;

[0080] Several sensors and the concentrator communicate using RS485 or MBUS, without the need for an MQTT protocol stack. The cost of data transmission between each sensor and the front-end processor is reduced by setting up a concentrator.

[0081] Specifically, MQTT Broker is an intermediary entity that is responsible for the communication between the front-end MQTT module and the client MQTT. MQTT Broker receives messages published by the front-end MQTT module, filters the messages according to the topic, and then distributes them to the client subscribers. By using MQTT Broker to implement the publish / subscribe communication model, the efficiency and scalability of the MQTT protocol can be significantly improved.

[0082] Specifically, the client is written using the front-end framework Vue, which can communicate with the Web application server through AJAX technology, allowing users to actively request sensor lists and data items, communicate with the MQTT Broker through MQTT, subscribe to data topics that users are interested in, and display changes in sensor data in real time.

[0083] Specifically, the steps of deploying a front-end machine and obtaining data from several sensors include:

[0084] The front-end acquires the sensor data and determines whether there is a new sensor registration in the sensor data. If there is a new sensor registration, an abstract entity of the new sensor is established and the abstract entity of the new sensor is stored in the sensor abstract list;

[0085] When the front-end receives sensor data, if the corresponding abstract entity does not exist in the sensor abstract list, the data is discarded;

[0086] If an abstract entity exists, determine whether the abstract entity is bound to the client that needs to receive data. If the abstract entity is already bound to the client, publish the sensor data to the corresponding client. When multiple clients are bound to an abstract entity at the same time, publish the sensor data to multiple clients in turn.

[0087] Specifically, deploying an MQTT Broker server, the MQTT Broker server obtains the client's demand instructions, and sends the client's demand instructions to the front-end. The front-end displays the sensor data required by the client on the client through the MQTT Broker server according to the demand instructions, including the following steps:

[0088] Get the MQTT Broker server parameters;

[0089] The front-end establishes an MQTT connection with the MQTT Broker server according to the MQTT Broker server parameters. If the connection fails, it will retry until it succeeds.

[0090] The MQTT Broker server obtains the client's request instructions;

[0091] The MQTT Broker server sends the demand instruction to the corresponding abstract entity in the front-end according to the subject of the demand instruction;

[0092] The corresponding abstract entity in the front-end obtains the corresponding sensor data according to the required instructions and uploads it to the M QTTBroker server;

[0093] The MQTT Broker server uploads the corresponding sensor data to the client.

[0094] The front-end receives sensor data from the concentrator. When the sensor data changes, it publishes the topic data to the MQTT Broker according to the topic configuration of to pic / client / config. The topic to pic / {clientId} / data is published. The {clientId} is the client ID, and the Payload content is {“Sens erId”:SenserId, “SenserType”:SenserType, “data”:{data content entity}}. The {clientId} in topic / {clientId} / data in the topic will be automatically routed by the MQTT Broker to the client identified as clientId. For example, if the data published as topic / 1 / data is published, it will be routed by the MQTT Broker to the client identified as 1.

[0095] Specifically, the workflow for deploying a Web application server is as follows:

[0096] Get the MQTT Broker server parameters;

[0097] Introduce Vue into the mqttjs library in the Web application server, and establish an MQTT connection with the MQTTBroker server according to the MQTT Broker server parameters. If the connection fails, retry until it succeeds.

[0098] The mqttjs library is an open source client library for the MQTT protocol. The client creates an MQTT connection and specifies the address and port number of the MQTTBroker to attempt a connection.

[0099] After the connection is successful, the client can publish the topic / client / config to the MQTT Broker according to user needs. After the front-end receives the topic published by the client, it will process it according to step 3 of the "Front-end Processing Flow".

[0100] The client subscribes to the topic topic / {clientId} / data, where {clientId} is its own ID. If client 1 wants to monitor its own events, the subscribed topic instance is topic / 1 / data. When the current machine publishes the data of the topic topic / {clientId} / data, it is automatically routed to the client after being filtered by the MQTT Broker. The client {clientId} will receive the message immediately. By reading the MQTT message queue, Vue will render the data in real time and present it to the client. If the user needs to request historical data, he can interact with the Web application server through AJAX to request data.

[0101] Example 3

[0102] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, a multi-sensor data display method of embodiment 1 is implemented.

[0103] Example 4

[0104] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, a multi-sensor data display method of embodiment 1 is implemented.

[0105] It is known from common technical knowledge that the present invention can be implemented by other embodiments that do not deviate from its spirit or essential features. Therefore, the above disclosed embodiments are only illustrative in all respects and are not exclusive. All changes within the scope of the present invention or within the scope equivalent to the present invention are included in the present invention.

[0106] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0107] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0108] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0109] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0110] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A multi-sensor data display method, It is characterized in that The following steps are involved: Deploy a front-end machine, which acquires data from several sensors. Deploy the MQTT Broker server, which obtains the client's demand instructions and sends the client's demand instructions to the front-end; The front-end processor displays the sensor data required by the client on the client through the MQTT Broker server according to the demand instructions.

2. A multi-sensor data display method according to claim 1, It is characterized in that The method also includes arranging a Web application server, wherein the Web application server is used to verify the user authority of the client.

3. A multi-sensor data display method according to claim 1, It is characterized in that The step of the front-end processor acquiring a plurality of sensor data comprises: The front-end acquires the initial sensor data, determines whether there is a new sensor registration in the initial sensor data, and if there is a new sensor registration, creates an abstract entity of the new sensor and stores the abstract entity of the new sensor in the sensor abstract list; When the front-end receives sensor data, if the corresponding abstract entity does not exist in the sensor abstract list, the data is discarded; If an abstract entity exists, determine whether the abstract entity is bound to the client that needs to receive data. If the abstract entity is already bound to the client, publish the sensor data to the corresponding client. When multiple clients are bound to an abstract entity at the same time, publish the sensor data to multiple clients in turn.

4. A multi-sensor data display method according to claim 1, It is characterized in that The steps of deploying the MQTT Broker server, the MQTT Broker server obtaining the client's demand instructions, and sending the client's demand instructions to the front-end processor, and the front-end processor displaying the sensor data required by the client on the client through the MQTT Broker server according to the demand instructions, include: Get the MQTT Broker server parameters; The front-end establishes an MQTT connection with the MQTT Broker server according to the MQTT Broker server parameters. If the connection fails, it will retry until it succeeds. The MQTT Broker server obtains the client's request instructions; The MQTT Broker server sends the demand instruction to the corresponding abstract entity in the front-end according to the subject of the demand instruction; The corresponding abstract entity in the front-end obtains the corresponding sensor data according to the required instructions and uploads it to the M QTTBroker server; The MQTT Broker server uploads the corresponding sensor data to the client.

5. A multi-sensor data display device, It is characterized in that include: Client: used to generate demand instructions, send demand instructions to the MQTT Broker server, and display sensor data; MQTT Broker server: used to send demand instructions to the front-end processor and upload sensor data sent by the front-end processor to the client; Front-end processor: used to upload corresponding sensor data to the MQTT Broker server according to the required instructions.

6. A multi-sensor data display method according to claim 5, It is characterized in that It also includes a database, which is communicatively connected to the front-end processor and is used to store the subject matter in the demand instruction.

7. A multi-sensor data display method according to claim 5, It is characterized in that The step of acquiring data from a plurality of sensors also includes a concentrator, the plurality of sensors are communicatively connected to the concentrator, and the concentrator is communicatively connected to the front-end processor.

8. A multi-sensor data display method according to claim 6, It is characterized in that The plurality of sensors and the concentrator communicate with each other via RS485 or MBUS.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, It is characterized in that When the processor executes the computer program, a multi-sensor data display method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program. It is characterized in that When the computer program is executed by a processor, a multi-sensor data display method according to any one of claims 1 to 7 is implemented.