Distributed photovoltaic cross-network multi-source data management method and system

Abstract

The invention discloses a distributed photovoltaic cross-network multi-source data management method and system, and relates to the field of data management, and the method comprises the steps that a mobile terminal employs a cloud MQTT protocol to issue a control command to a communication server through an EMQX platform; the communication server converts the control command under the cloud MQTT protocol into a control command under an industrial communication protocol corresponding to the equipment side; the equipment end acquires equipment data according to the control command under the corresponding industrial communication protocol, and sends the equipment data to the communication server through the corresponding industrial communication protocol; the communication server converts the equipment data under the corresponding industrial communication protocol into equipment data under a cloud MQTT protocol, and sends the equipment data to a computing server through an EMQX platform; and the computing server performs statistics on the equipment data and then sends the equipment data to the data lake through the interface service. The data management of different devices is realized through the unified data format of the Internet of Things, the data management level is improved, and the maintenance cost is reduced.

Description

Technical Field

[0001] The present application relates to the field of data management, and in particular to a distributed photovoltaic cross-network multi-source data management method and system. Background Art

[0002] In modern energy management systems, there is a lack of unified data collection standards between various devices and systems, resulting in significant data silos. Current monitoring methods mostly rely on their own equipment platforms, which reduces the efficiency of data analysis and decision-making. Summary of the invention

[0003] The purpose of this application is to provide a distributed photovoltaic cross-network multi-source data management method and system, which can realize data management of different devices through a unified Internet of Things data format, improve data management level and reduce maintenance costs.

[0004] To achieve the above objectives, this application provides the following solutions:

[0005] In a first aspect, the present application provides a distributed photovoltaic cross-network multi-source data management method, comprising:

[0006] The mobile terminal uses the cloud MQTT protocol to send control commands to the communication server through the EMQX platform;

[0007] The communication server converts the control commands under the MQTT protocol on the cloud into the control commands under the corresponding industrial communication protocol on the device side;

[0008] The device side collects device data according to the control command under the corresponding industrial communication protocol, and sends the device data to the communication server through the corresponding industrial communication protocol;

[0009] The communication server converts the device data under the corresponding industrial communication protocol into the device data under the cloud MQTT protocol, and sends it to the computing server through the EMQX platform;

[0010] The computing server collects statistics on the device data and sends it to the data lake through the interface service.

[0011] In the second aspect, the present application provides a distributed photovoltaic cross-network multi-source data management system, including: a mobile terminal, an EMQX platform, a communication server, a device terminal and a computing server;

[0012] The mobile terminal is used to issue control commands using the cloud MQTT protocol; the EMQX platform is used to forward control commands under the cloud MQTT protocol to the communication server; the communication server is used to convert control commands under the cloud MQTT protocol into control commands under the industrial communication protocol corresponding to the device terminal; the device terminal is used to collect device data according to the control commands under the corresponding industrial communication protocol; the communication server is also used to convert device data under the corresponding industrial communication protocol into device data under the cloud MQTT protocol; the EMQX platform is also used to send device data under the cloud MQTT protocol to the computing server; the computing server is used to count the device data and send it to the data lake through the interface service.

[0013] According to the specific embodiments provided in this application, this application has the following technical effects:

[0014] (1) This application can collect device data from different devices through different industrial communication protocols to achieve efficient integration of device data.

[0015] (2) This application uses the EMQX platform as the MQTT server, establishes a unified data transmission protocol standard, and unifies the data format. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1 A schematic diagram of a distributed photovoltaic cross-network multi-source data management method provided in an embodiment of the present application;

[0018] Figure 2 Schematic diagram of the control command issuing process

[0019] Figure 3 This is a schematic diagram of the device data upload process;

[0020] Figure 4 A schematic diagram of a communication service control flow based on MQTT provided in one embodiment of the present application. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0022] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0023] In an exemplary embodiment, Figure 1-Figure 4 As shown, a distributed photovoltaic cross-network multi-source data management method is provided, including the following steps S1 to S5. Among them:

[0024] S1: The mobile terminal uses the cloud MQTT protocol to send control commands to the communication server through the EMQX platform. The control command modes include manual control, automatic control and timing control.

[0025] S2: The communication server converts the control commands under the cloud MQTT protocol into the control commands under the corresponding industrial communication protocol on the device side. The communication protocols include: Modbus communication protocol, 376.1 communication protocol, DL645 communication protocol and device MQTT protocol

[0026] S3: The device side collects device data according to the control command under the corresponding industrial communication protocol, and sends the device data to the communication server through the corresponding industrial communication protocol.

[0027] S4: The communication server converts the device data under the corresponding industrial communication protocol into the device data under the cloud MQTT protocol, and sends it to the computing server through the EMQX platform.

[0028] S5: The computing server collects statistics on the device data and sends it to the data lake through the interface service. The interface service sends the collected device data to the data lake using the IEC104 communication protocol.

[0029] This application establishes a unified communication protocol standard for the device side, EMQX platform, and mobile side based on the MQTT protocol. Figure 2-Figure 3As shown, the device data is uploaded to the communication server and the protocol is judged. If it is the device MQTT protocol, it is automatically forwarded to the EMQX platform. If it is a traditional industrial protocol (i.e. Modbus communication protocol, 376.1 communication protocol, DL645 communication protocol), the communication server performs protocol conversion and forwards it to the EMQX platform for uploading. The EMQX platform is an MQTT server, which has established a unified data transmission protocol standard, realized various tasks such as mobile terminal control commands, data processing and result transmission of computing services, equipment acquisition protocols, and data interface format definitions, and unified the structure of acquisition models, business models, and control models and data format conversion.

[0030] Figure 4 This is a control flow chart of the communication service based on MQTT, which is divided into five objects: mobile terminal, communication terminal, device layer, interface terminal, and data lake. The mobile terminal is responsible for issuing control commands and viewing data. The communication terminal receives the control command and converts the protocol, and sends the command to the device layer through the EMQX platform. It also receives the data returned by the device layer, performs protocol parsing, converts it into the cloud MQTT protocol format content, and sends it to the EMQX platform. The mobile terminal subscribes and displays the data, and the interface terminal subscribes to the data at the same time. The device layer is responsible for receiving and issuing control commands and returning data. After the interface receives the collected data from the EMQX platform, the computing service processes the collected data, packages the data through the IEC104 protocol, and sends it to the data lake.

[0031] The distributed photovoltaic cross-network multi-source data management method provided in this application realizes real-time display of data based on mobile terminal + MQTT. Specifically:

[0032] For the energy Internet of Things, there are a large number of devices connected, and the traditional grid configuration mode (professional engineers configure the device type and device parameters according to the actual situation on site) is no longer applicable. Instead, automatic collection is achieved by configuring collection templates and scanning QR codes (device generation, collection parameter generation).

[0033] To C: Each device is configured with the server IP address, port, IMEI / SN (registration package, heartbeat package) before leaving the factory. On-site customers establish the relationship between the collection module and the user by scanning the code.

[0034] To B: Establish collection templates for different device types, configure device type and device quantity on site, load the collection parameter template of the corresponding device, automate the configuration, and configure the collection module (can be scanned or manually configured).

[0035] The distributed photovoltaic cross-network multi-source data management method provided in this application implements control command issuance based on mobile terminal + MQTT. Specifically:

[0036] When a user initiates a control request on the mobile terminal, first, the mobile terminal constructs a control command and sends it to the EMQX platform as a message agent. The communication server acts as a communication bridge between the EMQX platform and the device. The communication server subscribes to the control commands of the EMQX platform. Once a new control command enters, the communication server quickly receives and parses the command. Then, the communication server constructs a command that conforms to device communication based on the parsing results and sends it to the target device. After receiving the command, the device performs the corresponding operation to realize the control request initiated by the user on the mobile terminal.

[0037] The control command delivery includes three modes: manual control, automatic control, and timed control. When using manual control to deliver control commands, after entering the control delivery value on the front-end page and clicking execute, the value is first transmitted to the back-end via the EMQX platform. The back-end constructs the corresponding control command based on the received data and delivers the command to the RTU (remote terminal unit). At this point, manual control is completed.

[0038] Automatic control strategy refers specifically to the remote control strategy in the control system, that is, through the set rules and algorithms, according to the equipment status, sensor data and other information, automatically determine and execute the corresponding remote control commands to achieve equipment control and adjustment. To achieve automatic control of the system, it is necessary to first collect data from the equipment and understand the implementation of the equipment to determine whether the equipment meets the conditions for triggering automatic control.

[0039] Timing control is a way to control a device or system by setting a preset time. It can automatically execute instructions according to the preset time, so that the device can be turned on or off accurately at the preset time, or achieve a specific function, such as controlling the heating time of a water heater.

[0040] Manual control commands are issued to control a system, device or process through manual operation or direct intervention by humans. In this system, the user turns on or off the control button in the mini-program interface. When the user triggers the control operation in the mini-program interface, the mini-program will construct a message object containing the control information and send the control message to the EMQX platform using the cloud MQTT protocol. After receiving the message, the EMQX platform forwards the message to the communication server. The communication server performs corresponding control operations according to the MQTT subscription rules, such as the generation and execution of device commands. When the device receives the command and executes it, it will generate an echo message and send it back to the mini-program interface to form feedback. The mini-program generates the control information and sends it as follows:

[0041] Device ID plays a role in uniquely identifying devices in the Internet of Things and device communication. In this system, deviceID is used as the unique identifier of the device to distinguish different devices in the device list. When the user enters the device interface from the device list interface, a life cycle hook function onLoad of a mini program page is first constructed to perform some initialization work when the page is loaded. First, the "cleanup" function is called to clean up the connection with MQTT and pass the various properties in the parameter option passed when the page is loaded to the current page. Then the open method is called to open the MQTT connection and pass some configuration parameters and callback functions. The open method is the initialization process for establishing communication between the mini program and the MQTT server, including setting heartbeat and timeout parameters, device-related information, initializing agent properties, parsing configuration parameters, and initializing device information and three-segment and five-segment formats. Among them, the three-segment format and the five-segment format are usually used to describe the naming method of device parameters. The three-segment format includes three parts: device type, device ID, and parameter ID. The five-segment format usually includes five parts: device ID, device type, parameter ID, site ID, and component ID. Compared with the three-segment format, the five-segment format can more comprehensively represent the information of a device and its parameters.

[0042] After successful initialization, the connection to the EMQX platform begins. In this system, first create an MQTT mobile terminal instance and connect to the specified EMQX platform address. After the connection is successful, register a message event handler to process the MQTT message received from the EMQX platform. When receiving a message, the handler will parse the message content, check whether it contains a valid uid, and then perform the corresponding operation according to the result in the message. If the result is "0", it means that the device is offline, the corresponding modal box will be displayed and commandFlag will be set to false; if the result is "1", it means that the control is successful, the timer will be reset to obtain data later, and the loading prompt and success prompt will be displayed according to the value of showToast.

[0043] When the user clicks the button for control in the mini program interface, the sendMessage method is triggered to send control commands to the device through the mobile terminal. This method accepts control-related parameters, builds a JSON object containing remote control ID, control type, value and other information, and publishes the control command through the cloud MQTT protocol. At the same time, it handles the success and failure of publishing, including setting a timer to wait for a response, hiding the loading prompt, and displaying an error prompt based on the conditions.

[0044] The distributed photovoltaic cross-network multi-source data management method provided in this application is based on MQTT to convert the communication protocol. Specifically:

[0045] In order to achieve coordination and regularity of control and data collection, this application has developed a flexible and highly extensible MQTT protocol standard based on the MQTT protocol. The protocol standard is: Topics are divided into two categories, cloud-side topics and device-side topics. The cloud can subscribe to device-side topics to obtain device data, and the device can subscribe to cloud-side topics to obtain control commands.

[0046] After the device establishes a connection with the cloud, the cloud initiates a data call to the device, and the device responds to the EMQX platform and sends operating data to the cloud, or the device uploads to the cloud at a fixed time. The cloud initiates a data call, and the Topic format is: / cloud / ${productIMEI} / ${SN} / rtStatusCall The device reports data, and the Topic format is: / edge / ${productIMEI} / ${SN} / rtStatus.

[0047] After the program, device and cloud are connected, according to the control process, the cloud receives the mini program control command and sends a collection command to the device; the device responds to the cloud control command, and then the cloud feeds back the control result to the mini program. The mini program sends a control command, and the Topic is: topictask; the cloud publishes the control command, and the Topic is: / cloud / ${productIMEI} / ${SN} / paramSet; the device feeds back the collection command delivery result, and the Topic format is: topic_commandResult_${rtuId}

[0048] The distributed photovoltaic cross-network multi-source data management method provided in this application is based on MQTT for data interaction between application service modules. Specifically:

[0049] The data generated by users is transmitted to the communication server via RS485, 3G / 4G, WIFI and LORA. The communication server receives and parses the raw data, extracts information such as device status and monitoring data. Subsequently, the communication server transmits the parsed data to the EMQX platform using the cloud MQTT protocol. The EMQX platform, as a message agent, publishes data through the cloud MQTT protocol and forwards it to the communication server that subscribes to the relevant topic. The communication server receives the data and analyzes it, and stores the processed data in the database. When the user initiates a data request through the mini-program interface, the mobile terminal directly communicates with the database through the API interface to obtain real-time or historical data. This process intuitively shows the process of data collection, transmission and display.

[0050] When the data acquisition service is started, the channel container group, thread queue, protocol queue, device queue, device corresponding data buffer and other data in the system are initialized. After the system is initialized, the task processing thread, data publishing thread and terminal communication thread in the thread queue will be started. The terminal channel thread will bind the port to monitor whether there is a device connection. When the terminal communication thread is started, it will keep listening to the port. When a device is connected, the device will first send a registration frame to identify the corresponding device, and then select the device protocol type. After knowing the protocol used by the device to establish communication, the server and the device can communicate using the corresponding protocol. When the server receives the message, it will parse it, store the parsed data, and encapsulate the data and send it to the EMQX platform.

[0051] The distributed photovoltaic cross-network multi-source data management method provided in this application is based on the IEC104 communication protocol to enter data into the lake. Specifically:

[0052] This application realizes the status monitoring and display of photovoltaic power generation equipment based on the Internet of Things, uploads it to the service center, and realizes the storage, calculation and query of monitoring data. The service center can monitor the status of photovoltaic power generation equipment in real time and alarm in real time for faults. Different users can view the monitoring data within their authority based on PC, tablet, and workstation terminals, and submit system fault information through terminal devices to exchange information and realize centralized operation and maintenance of photovoltaic power stations.

[0053] The basic data collection of the photovoltaic power station field equipment layer is realized through data collection. It supports full-duplex communication, with optional transmission rates of 300, 600, 1200, 2400, and 9600bps, and supports network RT; it can receive and process telemetry, telesignal, and electricity measurements in different formats, and process them into a unified format required by the system; it can receive synchronous / asynchronous channel signals; it has the functions of monitoring and diagnosing the communication process, and counting the channel downtime; it can close and open the specified channel online. It adopts a variety of communication methods to achieve seamless connection with each station mid-end and remote data center.

[0054] In an exemplary embodiment, a distributed photovoltaic cross-network multi-source data management system is provided, including: a mobile terminal, an EMQX platform, a communication server, a device terminal and a computing server.

[0055] The mobile terminal is used to issue control commands using the cloud MQTT protocol; the EMQX platform is used to forward control commands under the cloud MQTT protocol to the communication server; the communication server is used to convert control commands under the cloud MQTT protocol into control commands under the industrial communication protocol corresponding to the device terminal; the device terminal is used to collect device data according to the control commands under the corresponding industrial communication protocol; the communication server is also used to convert device data under the corresponding industrial communication protocol into device data under the cloud MQTT protocol; the EMQX platform is also used to send device data under the cloud MQTT protocol to the computing server; the computing server is used to count the device data and send it to the data lake through the interface service.

[0056] The communication server collects real-time equipment data including: 01001 inverter DC input total power, 01001 inverter grid-connected active power, 01001 inverter status (operating status / grid-connected), 01001 inverter status (normal shutdown), 01001 inverter status (communication interruption), 01001 inverter status (normal standby), 01001 inverter status (fault shutdown), 01001 inverter status (alarm operation), 01001 inverter status (derating operation), 001 box-type transformer high-voltage side load switch closed, 001 box-type transformer high-voltage side load switch open, 002 box-type transformer high-voltage side load switch closed, 002 box-type transformer high-voltage side load switch open, forward active power (total), reverse active power (total), wind speed, light radiation value, ambient temperature. The above data are forwarded to the interface service through EMQX, and the interface service enters the lake through 104 protocol data.

[0057] The communication server collects real-time equipment data and sends it to the computing service through EMQX. The cumulative data is obtained through the computing service: the number of operating units, the operating capacity, the number of faulty units, the fault capacity, the number of interrupted units, the interrupted capacity, the number of shut down units, the shut down capacity, the number of standby units, the standby capacity, the number of maintenance units, the active power of the station, the solar radiation of the day, the cumulative daily electricity, the cumulative monthly electricity, the cumulative annual electricity, and the data is entered into the lake through the computing service via the 104 protocol.

[0058] The distributed photovoltaic cross-network multi-source data management system provided by this application provides a complete remote monitoring solution based on the characteristics of distributed power stations and the management experience in the field of photovoltaic power generation. Photovoltaic power stations are monitored through sensor communication technology, and online centralized remote monitoring, message push, multi-terminal display, and intelligent operation and maintenance analysis are realized. It improves the operation and management efficiency of distributed power stations, improves the level of production and operation management, reduces equipment maintenance costs, and ensures investment returns. It solves the problems of scattered distributed photovoltaic asset sites, large differences in installed capacity, and diverse equipment types, realizes efficient photovoltaic site operation and management, and enters real-time data of thermal power, wind power, and photovoltaics into the data lake for visualization and operation and maintenance.

[0059] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0060] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0061] The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. The non-relational database may include a distributed database based on blockchain, etc., but is not limited thereto. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but is not limited thereto.

[0062] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0063] This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. At the same time, for those skilled in the art, according to the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A distributed photovoltaic cross-network multi-source data management method, characterized in that: include: The mobile terminal uses the cloud MQTT protocol to send control commands to the communication server through the EMQX platform; The communication server converts the control commands under the MQTT protocol on the cloud into the control commands under the corresponding industrial communication protocol on the device side; The device side collects device data according to the control command under the corresponding industrial communication protocol, and sends the device data to the communication server through the corresponding industrial communication protocol; The communication server converts the device data under the corresponding industrial communication protocol into the device data under the cloud MQTT protocol, and sends it to the computing server through the EMQX platform; The computing server collects statistics on the device data and sends it to the data lake through the interface service.

2. The distributed photovoltaic cross-network multi-source data management method according to claim 1 is characterized in that: The modes of the control command include manual control, automatic control and timing control.

3. The distributed photovoltaic cross-network multi-source data management method according to claim 1 is characterized in that: The industrial communication protocols include: Modbus communication protocol, 376.1 communication protocol, DL645 communication protocol and device MQTT protocol.

4. The distributed photovoltaic cross-network multi-source data management method according to claim 1 is characterized in that: Each device on the device side is configured with a server IP address, port and IMEI / SN when leaving the factory.

5. The distributed photovoltaic cross-network multi-source data management method according to claim 4 is characterized in that: Each of the devices uses deviceID as a unique identifier.

6. The distributed photovoltaic cross-network multi-source data management method according to claim 1 is characterized in that: The interface service sends the statistical device data to the data lake using the IEC104 communication protocol.

7. A distributed photovoltaic cross-network multi-source data management system, characterized in that: include: Mobile terminal, EMQX platform, communication server, device terminal and computing server; The mobile terminal is used to issue control commands using the cloud MQTT protocol; The EMQX platform is used to forward control commands under the cloud MQTT protocol to the communication server; The communication server is used to convert the control commands under the MQTT protocol on the cloud into control commands under the industrial communication protocol corresponding to the device end; The device end is used to collect device data according to the control commands under the corresponding industrial communication protocol; the communication server is also used to convert the device data under the corresponding industrial communication protocol into device data under the cloud MQTT protocol; the EMQX platform is also used to send the device data under the cloud MQTT protocol to the computing server; the computing server is used to count the device data and send it to the data lake through the interface service.

Images