Coordination control system of quasi-distributed service

Abstract

The invention belongs to the technical field of micro-energy coordination control of a virtual power plant, and particularly relates to a quasi-distributed service coordination control system. Comprising a serial port and message mutual conversion service, a CAN and message mutual conversion service, a 4-20mA message conversion service, an information arrangement service, a control service, a system log service, a data cycle persistence service, a fault processing service, a data permanent persistence service, an adjustment algorithm service, a historical data query and display service, and a data and prediction data display service. Real-time data display service and equipment management service. According to the method, the disaster tolerance of the whole software system can be improved through fully distributed deployment and redundant services, resource limitation can be broken through the characteristics of remote cloud services, and infinite extension of computing power and storage theories is achieved. According to the method, functions can be decomposed into characteristics of a plurality of services, so that the flexibility of the system is improved, and the expansibility of the system is also improved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of micro energy coordination control of virtual power plant, and particularly relates to a coordination control system of quasi-distributed service. BACKGROUND

[0002] With the development and popularization of photovoltaic and wind power technologies, energy management of photovoltaic storage nuclear network is becoming more and more popular. How to take the first opportunity in the continuous development, that is, to facilitate the upgrading of functional modules without upgrading the whole system, to compatible hardware upgrade or local upgrade caused by hardware replacement and repair, has become a difficult problem for the development of the industry. In fact, the whole system can be expanded multiple times. The traditional method is to upgrade the whole system or restructure the software every time the system hardware is changed. The traditional method is also limited by a single framework.

[0003] The prior art as shown in Figure 1 is generally deployed in two parts, a local server part and a cloud service part. The local server part generally adopts a front-back BS architecture, all functions are integrated in one software program, and are decoupled in layers in the software program, cannot jump layers for communication and calling, and each module generally uses a function interface calling form, which belongs to marker coupling. Once a program has a bug, the whole system is prone to crash. The extensibility mainly relies on design patterns for control. System expansion can only be realized by restructuring the program, and part of the device maintenance can only be satisfied by pre-designing configurability. The cloud service part mainly functions as permanent storage and data analysis. The main functions of the system are realized through the local server, which belongs to centralized software.

[0004] In the traditional architecture, each module calls API, and the program is generally a whole. Once a module has a problem, the whole system can only be restarted. Therefore, once a module of the centralized software has a problem, the whole software crashes, and the system can only be upgraded or restructured as a whole. The centralized elasticity is poor, and can only be expanded by design patterns, In addition, the cloud server in the traditional architecture generally only has the functions of data storage and program OTA upgrade. There is a single embedded device / local server centralized binding: the computing power and function are limited by the resources of the embedded device / server itself.

[0005] The function deployment is fixed. Once a device has a problem, it can only be solved by restarting the device (or restoring factory settings).

[0006] The extensibility of the system has an upper limit, which is not only limited by resources but also limited by software architecture, Therefore, the technical personnel in the field have been continuously researching and developing. SUMMARY

[0007] In view of the deficiencies in the prior art, the application provides a coordination control system of quasi-distributed services. The purpose is to improve the system disaster tolerance, break the system resource limit by using the cloud service characteristics, improve the scalability by using the reverse link deployment, and achieve rapid system upgrade without the problem of longer maintenance and upgrade time as the system becomes larger.

[0008] The application adopts the technical solution of: A coordination control system of quasi-distributed services, comprising: The serial port and message interconversion service, the CAN and message interconversion service, and the 4-20 mA to message service are connected with the information arrangement service through MQTT protocol in a message publishing and subscribing mode. The information arrangement service is connected with the data cyclic persistence service, the fault processing module, the data persistence service adjustment service, the historical data query and display service, the data and predicted data display service, the real-time data display service, and the device management service on the broker embedded device through the API gateway in a message publishing and subscribing mode of Kafka distributed stream processing, and the broker is on the cloud. Control service: conversion from Kafka to custom MQTT protocol, one-way conversion. System log service: meets the needs of recording any service in the system, and supports custom MQTT and Kafka topics.

[0009] Further, the serial port and message interconversion service: service of bidirectional conversion between serial port protocol and custom MQTT protocol. The CAN and message interconversion service: service of bidirectional conversion between CAN application layer protocol and custom MQTT protocol. The 4-20 mA to message service: service of converting 4-20 mA current collection to custom MQTT protocol. The information arrangement service: mapping from custom MQTT protocol to Kafka, one-way conversion. The data cyclic persistence service: meets the needs of data storage of the perception layer, and is used for ensuring the integrity of data in transmission and supporting Kafka topics. The fault processing service: used for fault alarm of information data. The data permanent persistence service: meets the needs of permanent storage of system data. The adjustment algorithm service: used for meeting certain purpose control algorithm. The historical data query and display service: supports conditional query and display of historical data. The data and predicted data display service: supports comparison between actual data curve and adjustment algorithm predicted curve. The real-time data display service: all real-time data dynamic summary, customizable increase and decrease data; The device management service: support all device management in the system.

[0010] Further, the coordination control system of the distributed service, the dynamic deployment and system upgrade mode are as follows: data cycle persistence service, fault processing module, data persistence service adjustment service, historical data query and display service, data and prediction data display service, real-time data display service and device management service, API gateway is arranged on the embedded device or cloud service, and backup of each service is arranged on the cloud service, the missing service is replaced or restarted by the cloud service after timeout, and the system is upgraded by deploying new services in reverse order.

[0011] Further, the serial port protocol includes modbus protocol and modbus extension protocol.

[0012] Further, the fault processing service includes: information filtering processing, fault threshold access and fault information record persistence.

[0013] Further, the purpose includes but is not limited to peak clipping, power quality, optimization of system economy, user load prediction, power grid data prediction, photovoltaic data prediction and wind energy data prediction.

[0014] Further, the coordination control system of the quasi-distributed service further includes: an embedded device and a public interface redundancy of the service; The local server, i.e. private cloud server: used for improving disaster recovery and data security; The embedded device: physically connected with other devices in the energy system, including but not limited to BMS system, photovoltaic PCS, energy storage PCS, smart meter and charging device; used for completing the sensing layer and gateway of the energy management system, and realizing real-time encrypted communication with the local server or cloud server through wired network, wireless network, 4G mobile network; The public interface redundancy of the service: all services support MQTT topic and Kafka topic, and non-embedded devices prefer Kafka topic.

[0015] Further, the embedded device includes at least one or more in the whole system; the local server further includes public cloud server: used for completing permanent data storage and data analysis operation by using the advantage of strong resource expansion.

[0016] A computer device comprises a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, and the processor implements the operation steps of the coordination control system of the quasi-distributed service according to any one of the embodiments when executing the computer program.

[0017] A computer storage medium, on which a computer program is stored, and the computer program implements the operation steps of the coordination control system of the quasi-distributed service according to any one of the embodiments when executed by a processor.

[0018] The present application has the following advantages and benefits: The quasi-distributed architecture provided by the present application breaks through the limitations of existing monolithic resources, and enhances the scalability of the architecture. The redundancy mechanism of the present application fundamentally avoids problems in a single module, thereby preventing system crashes. The architecture of the present application can also be upgraded or restructured at the module level.

[0019] The communication between the various services of the system of the present application is all loosely coupled, and can be upgraded or replaced at any time. In addition, the services can be replaced by backup services when a service fails. Except for services related to resources, such as serial port and message conversion, other services can be deployed on any device, such as an embedded device, a local server, and a cloud service, and are usually deployed locally or near the ground in accordance with the principle of proximity. The present application can also undertake some services to reduce the resource pressure of the embedded device.

[0020] The quasi-distributed architecture provided by the present application can improve the disaster recovery of the entire software system through full-distributed deployment and redundant services, and can break through resource constraints through the characteristics of off-site cloud services to achieve theoretically unlimited expansion of computing power and storage. The present application can also improve the flexibility and scalability of the system by decomposing functions into multiple services.

[0021] The present application replaces the API direct call mode with the message publishing and subscribing mode, and divides the entire system according to the function chain, which plays a role in dividing the whole into parts, is more convenient for upgrading, and will not require more and more time for upgrading as the system becomes larger and larger and the data becomes more and more. BRIEF DESCRIPTION OF DRAWINGS

[0022] The above and / or additional aspects and advantages of the present application will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which: Figure 1 is a traditional system architecture diagram; Figure 2 is a service division diagram of the system of the present application. DETAILED DESCRIPTION

[0023] To better understand the above-mentioned objectives, features, and advantages of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments of the present invention and the features thereof can be combined with each other.

[0024] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and therefore the scope of protection of the invention is not limited to the specific embodiments disclosed below.

[0025] The following reference Figure 2 The technical solutions of some embodiments of the present invention are described below.

[0026] Example 1

[0027] This invention provides an embodiment of a quasi-distributed service coordination and control system. For example... Figure 2 As shown, Figure 2 This is the service partitioning diagram of the system of the present invention.

[0028] like Figure 2 As shown, the present invention includes the following services: serial port to message conversion service, CAN to message conversion service, 4 to 20mA to message conversion service, information organization service, control service, system log service, data cyclic persistence service, fault handling service, data permanent persistence service, adjustment algorithm service, historical data query and display service, data and predictive data display service, real-time data display service, and device management service.

[0029] Specifically, the serial port to message conversion service, CAN to message conversion service, and 4-to-20mA to message conversion service are connected to the information processing service via the MQTT protocol using a publish-subscribe message method, with the broker deployed on an embedded device. The information processing service, data loop persistence service, fault handling module, data persistence service adjustment service, historical data query and display service, data and predictive data display service, real-time data display service, and device management service are connected to the API gateway via a Kafka distributed stream processing message publish-subscribe message method, with the broker deployed on a cloud service.

[0030] Of these, the serial port to message conversion service, CAN to message conversion service, 4 to 20mA to message conversion service, information processing service, and data loop persistence service must be implemented on the embedded device. The data loop persistence service must be implemented on the cloud server. Other services can be implemented on the embedded device, distributed on the local server, or on the cloud server.

[0031] The serial port and message conversion service is a bidirectional conversion service between the serial port protocol and a custom MQTT protocol. The serial port protocol includes the Modbus protocol and Modbus extended protocols.

[0032] The CAN and Message Conversion Service is a service that converts between the CAN application layer protocol and a custom MQTT protocol in both directions.

[0033] The 4 to 20mA message conversion service is a service that collects and converts 4 to 20mA current using a custom MQTT protocol.

[0034] The information processing service involves a one-way conversion from a custom MQTT protocol to a Kafka mapping.

[0035] The control service: a one-way conversion from Kafka to a custom MQTT protocol.

[0036] The system log service meets the need for logging in any service within the system. It also supports custom MQTT and Kafka topics.

[0037] The data circular persistence service satisfies the data storage requirements of the perception layer, ensuring data integrity during transmission. Kafka topics are supported. The fault handling service is used for fault alarms of information data, including information filtering, fault threshold storage and retrieval, and persistent recording of fault information.

[0038] The data persistence service: satisfies the requirement for permanent storage of system data.

[0039] The regulation algorithm service is used to satisfy certain purposeful control algorithms, which include, but are not limited to, peak shaving and valley filling, power quality optimization, system economic optimization, user load forecasting, grid data forecasting, photovoltaic data forecasting, and wind energy data forecasting.

[0040] The historical data query and display service supports conditional query and display of historical data.

[0041] The data and prediction display service supports the comparison between actual data curves and adjustment algorithm-predicted curves.

[0042] The real-time data display service dynamically aggregates all real-time data, and allows for customized additions and subtractions of data.

[0043] The device management service supports the management of all devices within the system.

[0044] Example 2

[0045] The present invention provides another embodiment, which is a coordination and control system for quasi-distributed services.

[0046] This invention employs a novel approach for dynamic deployment and system upgrades. Services such as data persistence, fault handling, data persistence adjustment, historical data query and display, data and predictive data display, real-time data display, device management, and API gateways can be deployed on embedded devices or cloud services without requiring service-device binding. This means that these services do not need to be deployed on any fixed device; as long as a service (module) provides the service (function) and forms a complete service flow during system operation, the system can function. Even if some modules are missing, only the relevant functions are missing; it will not cause the entire system to crash or become paralyzed. Moreover, there are backups of each service on the cloud service, and missing services will be quickly replaced or restarted by the cloud service after a timeout. The system upgrade is achieved by deploying new services in reverse order to replace the original services.

[0047] In practice, the data sequence is: 4-20mA to message service, information processing service, and real-time data display service. To upgrade, the deployment order is: real-time data display service, information processing service, and then 4-20mA to message service. After deploying the 4-20mA to message service, the original 4-20mA to message service is stopped, thus completing the upgrade.

[0048] Example 3

[0049] This invention provides another embodiment, which is a coordination and control system for quasi-distributed services. Specifically, it includes the following components: Embedded devices: These provide the physical connection to other devices in the energy system, including but not limited to BMS systems, photovoltaic PCS, energy storage PCS, smart meters, and charging devices. Multiple devices can be connected if one is insufficient, primarily functioning as the sensing layer and gateway of the energy management system. They can communicate in real-time with local servers and cloud servers via wired networks, wireless networks, and 4G mobile networks.

[0050] Local server, also known as private cloud server: It is not a necessary device in this framework, but having a local server can improve disaster recovery and data security, and with a private cloud server, the public cloud service below can be eliminated.

[0051] Public cloud servers leverage their strong resource scalability to perform permanent data storage and data analysis. If certain services on embedded devices experience problems, backup services on the cloud server can also provide alternatives.

[0052] Redundancy of public service interfaces: All services support both MQTT and Kafka topics. For non-embedded devices, Kafka topics are prioritized; if data congestion occurs, MQTT topics are enabled.

[0053] Example 4

[0054] The present invention provides another embodiment, which is a coordination and control system for quasi-distributed services.

[0055] The services provided by this invention are not limited by device and can be embedded devices, local servers, and private / public clouds.

[0056] All services in this invention have a unified interface with MQTT and Kafka topic interfaces. Embedded devices prioritize MQTT topics, while other devices prioritize Kafka topics.

[0057] All services in this invention have primary and backup services, and the upstream service can choose between primary and backup to meet its needs. This ensures reliability. If the upstream service fails, the system can also autonomously restart itself to maintain reliability. If three consecutive restarts fail, the backup service will be activated to ensure basic system operation.

[0058] Some services of this invention must be deployed on specific types of devices. For example, hardware-related services must be deployed on embedded devices, but they can be deployed on multiple embedded devices, and the primary and backup services can be deployed separately on different devices to improve reliability. The hardware-related services include: serial port to message conversion service, CAN to message conversion service, and 4 to 20mA to message conversion service.

[0059] The services provided by this invention can be upgraded or reconfigured independently.

[0060] The rest is the same as in Examples 1-3.

[0061] Example 5

[0062] Based on the same inventive concept, embodiments of the present invention also provide a computer device, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor. When the processor executes the computer program, it implements the steps of a coordination and control system for a quasi-distributed service as described in embodiment 1 or 2.

[0063] Example 6

[0064] Based on the same inventive concept, embodiments of the present invention also provide a computer storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of any one of the coordination and control systems for a quasi-distributed service described in Embodiment 1 or 2.

[0065] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied 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.

[0066] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0067] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0068] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0069] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do 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 quasi-distributed service coordination and control system, characterized by: include: The serial port to message conversion service, CAN to message conversion service, and 4 to 20mA to message conversion service are connected to the information processing service via the MQTT protocol using a message publish-subscribe method. On the embedded broker device, there are information organization and data recycling persistence services, fault handling modules, data persistence service adjustment services, historical data query and display services, data and predictive data display services, real-time data display services, and device management services. The API gateway connects via Kafka distributed stream processing message publish-subscribe. The broker is on the cloud. Control service: One-way conversion from Kafka to a custom MQTT protocol; System Log Service: Meets the need for logging in any service within the system, and also supports custom MQTT and Kafka topics.

2. The coordination and control system for quasi-distributed services according to claim 1, characterized in that: The serial port and message conversion service is a bidirectional conversion service between the serial port protocol and the custom MQTT protocol. The CAN and message conversion service is a bidirectional conversion service between the CAN application layer protocol and the custom MQTT protocol. The 4 to 20mA message conversion service is a service that collects and converts 4 to 20mA current using a custom MQTT protocol. The information processing service involves a one-way conversion from a custom MQTT protocol to a Kafka mapping. The data circular persistence service satisfies the data storage needs of the perception layer, ensures data integrity during transmission, and supports Kafka topics; The fault handling service is used for fault alarms related to information data. The data persistence service: satisfies the requirement of permanent data storage in the system; The adjustment algorithm service is used to satisfy certain purposeful control algorithms; The historical data query and display service supports conditional query and display of historical data. The data and prediction display service supports the comparison between actual data curves and adjustment algorithm-predicted curves. The real-time data display service dynamically aggregates all real-time data and allows for customized additions and subtractions of data. The device management service supports the management of all devices within the system.

3. The coordination and control system for quasi-distributed services according to claim 1, characterized in that: The coordination and control system of the distributed service has the following dynamic deployment and system upgrade methods: data cyclic persistence service, fault handling module, data persistence service adjustment service, historical data query and display service, data and predictive data display service, real-time data display service and device management service, API gateway is deployed on embedded device or cloud service, and each service is backed up on the cloud service. Missing services are quickly replaced or restarted by cloud services after timeout. The system is upgraded by deploying new services in reverse order.

4. A quasi-distributed service coordination and control system according to claim 1, characterized in that: The serial port protocol includes the Modbus protocol and the Modbus extended protocol.

5. A quasi-distributed service coordination and control system according to claim 1, characterized in that: The fault handling service includes: information filtering, fault threshold storage and retrieval, and persistent recording of fault information.

6. A quasi-distributed service coordination and control system according to claim 1, characterized in that: The objectives include, but are not limited to, peak shaving and valley filling, power quality optimization, system economic optimization, user load forecasting, grid data forecasting, photovoltaic data forecasting, and wind energy data forecasting.

7. A quasi-distributed service coordination and control system according to claim 1, comprising a local server component and a cloud service component, characterized in that: Also includes: Redundant portions of the common interfaces between embedded devices and services; The local server, i.e., the private cloud server, is used to improve disaster recovery and data security. The embedded device: completes the actual physical connection with other devices in the energy system, including but not limited to BMS system, photovoltaic PCS, energy storage PCS, smart meter and charging device; Used to complete the work of the sensing layer and gateway of the energy management system, and communicates with the local server or cloud server in real time with encrypted communication via wired network, wireless network, 4G mobile network; The service has redundant public interfaces: all services support MQTT topics and Kafka topics, with Kafka topics being preferred for non-embedded devices.

8. A quasi-distributed service coordination and control system according to claim 7, characterized in that: The embedded device is included in at least one or more in the whole system; the local server also includes a public cloud server: used to complete permanent data storage and data analysis operations by taking advantage of the strong resource scalability.

9. A computer device, comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, When the processor executes the computer program, it implements the operational steps of the coordination and control system for a quasi-distributed service as described in any one of claims 1-8.

10. A computer storage medium, characterized in that: The computer storage medium contains a computer program, which, when executed by a processor, implements the operational steps of a quasi-distributed service coordination and control system as described in any one of claims 1-8.

Images