A virtual power plant interaction method, communication architecture, electronic device and storage medium

Abstract

The application discloses a virtual power plant interaction method, a communication architecture, an electronic device and a storage medium, which are applied to a gateway of a virtual power plant communication architecture and include the following steps: a connection request is initiated to a virtual power plant cloud, and a connection state with the virtual power plant cloud is confirmed; when the connection is normal, identity authentication is sent to the virtual power plant cloud; when the identity authentication is passed, data transmission is initiated to the virtual power plant cloud, so that the virtual power plant cloud checks the data; and based on a checking result of the virtual power plant cloud on the data, it is judged whether data retransmission is needed to complete the data transmission. The technical scheme improves the security and reliability of virtual power plant communication.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of power systems, in particular to a virtual power plant interaction method, a communication architecture, an electronic device and a storage medium. BACKGROUND

[0002] A virtual power plant is a power coordination management system that can realize the aggregation and coordinated optimization of energy storage systems, controllable loads, electric vehicles and the like through advanced information communication technology and software systems, participate in power market and power grid operation as a special power plant, and provide management and auxiliary services for distribution networks and transmission networks.

[0003] The aggregation and regulation of massive flexible resources by using a virtual power plant is a key implementation path for urban energy internet. Traditional virtual power plants usually take one type of resource as a regulation element, and can realize general methods in terms of resource distribution, communication mode, adaptation protocol, access quantity, etc. However, due to the multiple types, large quantity, wide distribution and diverse protocols of the distributed resources aggregated by a flexible resource virtual power plant, it is difficult to meet the requirements of reliability and security by using general methods. SUMMARY

[0004] Therefore, the embodiments of the present application provide a virtual power plant interaction method, a communication architecture, an electronic device and a storage medium to improve the security and reliability of virtual power plant communication.

[0005] According to a first aspect, the embodiments of the present application provide a virtual power plant interaction method applied to a virtual power plant cloud of a virtual power plant communication architecture, comprising:

[0006] receiving a connection request initiated by a gateway and confirming a connection state with the gateway;

[0007] when the connection is normal, receiving identity authentication sent by the gateway;

[0008] when the identity authentication is passed, receiving data transmission initiated by the gateway and checking the data to obtain a checking result;

[0009] feeding back the checking result to the gateway and processing the data based on the checking result to complete the transmission of the data.

[0010] The virtual power plant interaction method provided by the embodiments of the present application is applied to a virtual power plant cloud of a virtual power plant communication architecture, receives data transmission after identity authentication of the gateway, checks the data, processes and saves the data based on the checking result, completes the data transmission process between the cloud and the gateway of the virtual power plant, and improves the security of virtual power plant data transmission.

[0011] In one embodiment, the method further comprises:

[0012] When the check result is a check success, the data is format-converted to obtain data in a target format.

[0013] The data in the target format is stored and backed up.

[0014] In one embodiment, the virtual power plant cloud applied to the virtual power plant communication architecture, the method further comprises:

[0015] Receiving a dispatching task of a power grid, and filtering virtual power generators and generating a dispatching plan based on the dispatching task;

[0016] Sending the dispatching plan to the gateway to obtain resource terminal participation results;

[0017] Confirming a final dispatching plan based on the resource terminal participation results, calculating predicted load data, and publishing the final dispatching plan to the gateway;

[0018] Receiving actual load data generated by at least one resource terminal after receiving and executing a dispatching decomposition task distributed by the gateway;

[0019] Settling the actual load data based on the predicted load data to obtain a settlement result, so as to complete the dispatching task of the power grid.

[0020] The virtual power plant interaction method provided in the embodiments of the present application takes the gateway as a relay, receives a dispatching task published by a power grid through a cloud, generates a dispatching plan according to the dispatching task, confirms resource terminals that can participate through the gateway, and distributes a final dispatching plan to enable the resource terminals that can participate to execute the dispatching task, thereby improving the efficiency of task execution.

[0021] In one embodiment, confirming a final dispatching plan based on the resource terminal participation results, calculating predicted load data, and publishing the final dispatching plan comprise:

[0022] When the resource terminal participation results meet the dispatching plan, the final dispatching plan is confirmed.

[0023] According to the final dispatching plan, predicted load data is calculated, and the final dispatching plan is published.

[0024] According to a second aspect, the embodiments of the present application provide a virtual power plant interaction method applied to a gateway of a virtual power plant communication architecture, and the method comprises:

[0025] Initiating a connection request to a virtual power plant cloud, and confirming a connection state with the virtual power plant cloud.

[0026] When the connection is normal, send an authentication message to the virtual power plant cloud;

[0027] When the authentication is successful, data transmission is initiated to the virtual power plant cloud so that the virtual power plant cloud can verify the data;

[0028] Based on the verification results of the data by the virtual power plant cloud, it is determined whether data retransmission is required to complete the data transmission.

[0029] In one implementation, confirming the connection status with the virtual power plant cloud includes:

[0030] When the gateway establishes a connection with the virtual power plant cloud, it sends a heartbeat connection detection to the virtual power plant cloud;

[0031] The connection status is confirmed based on the heartbeat detection results fed back from the virtual power plant cloud.

[0032] In one embodiment, the gateway applied to a virtual power plant communication architecture, the method further includes:

[0033] Receive scheduling plans generated by the virtual power plant cloud based on scheduling tasks;

[0034] According to the scheduling plan, the resource participation result is confirmed to at least one resource terminal, and the resource terminal participation result is fed back to the virtual power plant cloud.

[0035] The system receives the final scheduling plan confirmed by the virtual power plant based on the participation results, decomposes the final scheduling plan to obtain scheduling decomposition tasks, and assigns the scheduling decomposition tasks to at least one resource terminal to complete the execution of the scheduling tasks.

[0036] According to a third aspect, embodiments of the present invention provide a virtual power plant communication architecture, including:

[0037] At least one resource terminal;

[0038] A gateway, wherein the at least one resource terminal is connected to the gateway, and the gateway is used to execute the virtual power plant interaction method in the second aspect or any embodiment of the second aspect;

[0039] The cloud is connected to the gateway and is used to execute the virtual power plant interaction method in the first aspect or any embodiment of the first aspect.

[0040] According to a fourth aspect, an electronic device is provided, comprising a memory and a processor, which are in communication connection with each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the virtual power plant interaction method in the first aspect, the second aspect, any one of the implementation manners of the first aspect, or any one of the implementation manners of the second aspect.

[0041] According to a fifth aspect, a computer readable storage medium is provided, which stores computer instructions for performing the virtual power plant interaction method in the first aspect, the second aspect, any one of the implementation manners of the first aspect, or any one of the implementation manners of the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the drawings needed in the specific embodiments or prior art description will be briefly introduced as follows. Obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0043] Figure 1 is a flow chart of the virtual power plant interaction method according to an embodiment of the present application;

[0044] Figure 2 is a flow chart of the virtual power plant interaction method according to an embodiment of the present application;

[0045] Figure 3 is a structure diagram of the virtual power plant communication architecture according to an embodiment of the present application;

[0046] Figure 4 is an interaction diagram of the virtual power plant communication architecture according to an embodiment of the present application;

[0047] Figure 5 is an interaction diagram of the virtual power plant communication architecture according to an embodiment of the present application;

[0048] Figure 6 is a virtual power plant cloud interaction diagram according to an embodiment of the present application;

[0049] Figure 7 is a cloud edge data communication flow diagram of the virtual power plant according to an embodiment of the present application;

[0050] Figure 8 is a task scheduling flow diagram of the virtual power plant according to an embodiment of the present application;

[0051] Figure 9Fig. 1 is a structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0052] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0053] The virtual power plant cloud can be an aggregation and regulation platform of the virtual power plant, for example, a user end, and mainly realizes central control of a virtual power plant communication architecture; the gateway can be an "edge" in the virtual power plant communication architecture and mainly serves as a transfer between the resource terminal and the cloud; the resource terminal can be an "end" in the virtual power plant communication architecture and includes various source, load and storage resources with different response capabilities, and flexible resources include distributed photovoltaic, wind power, three-in-one supply, distributed energy storage, commercial buildings, residential buildings, electric vehicles, industrial parks and the like, and flexible resource terminals cover photovoltaic inverters, wind turbines, boilers, water pumps, air conditioners, water heaters, charging devices, production lines and the like.

[0054] According to the embodiments of the present application, a virtual power plant interaction method embodiment is provided. It should be noted that the steps shown in the flowchart of the drawings can be executed in a computer system such as a group of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0055] In the present embodiment, a virtual power plant interaction method is provided, which is applied to a cloud end of a virtual power plant communication architecture, Figure 1 Fig. 2 is a flowchart of a virtual power plant interaction method according to an embodiment of the present application, as shown in the figure, the flow includes the following steps: Figure 1

[0056] S11, receiving a connection request initiated by the gateway, and confirming the connection state with the gateway.

[0057] The virtual power plant cloud can be an aggregation and regulation platform of the virtual power plant, for example, a user end, and mainly realizes central control of a virtual power plant communication architecture; the gateway can be an "edge" in the virtual power plant communication architecture and mainly serves as a transfer between the resource terminal and the cloud; the resource terminal can be an "end" in the virtual power plant communication architecture and includes various source, load and storage resources with different response capabilities, and flexible resources include distributed photovoltaic, wind power, three-in-one supply, distributed energy storage, commercial buildings, residential buildings, electric vehicles, industrial parks and the like, and flexible resource terminals cover photovoltaic inverters, wind turbines, boilers, water pumps, air conditioners, water heaters, charging devices, production lines and the like.

[0058] ​A connection request is initiated by a gateway in a virtual power plant to a cloud, which can be a TCP (Transmission Control Protocol) request. When the gateway establishes a connection with the cloud, a heartbeat connection detection can be sent to the cloud. Based on the heartbeat detection result fed back by the virtual power plant cloud, the connection status between the gateway and the cloud is confirmed.

[0059] S12, when the connection is normal, identity authentication sent by the gateway is received.

[0060] When the connection is unsuccessful, the gateway initiates a connection request to the cloud again. When the connection is normal, the cloud receives the identity authentication sent by the gateway for identity authentication.

[0061] S13, when the identity authentication is passed, data transmission initiated by the gateway is received, and the data is checked to obtain a checking result.

[0062] S14, the checking result is fed back to the gateway, and the data is processed based on the checking result to complete the transmission of the data.

[0063] If the identity authentication is unsuccessful, the process ends and no subsequent operation is performed. If the identity authentication is passed, the gateway initiates data transmission to the cloud, and the cloud receives the data transmitted by the gateway. The data mainly includes energy data, which can include voltage, current, switch state, whether active, power angle, grid point information, etc. Different data can be transmitted according to different resource types.

[0064] After receiving the data, the cloud checks the received data. The gateway determines whether data retransmission is needed according to the data checking result of the cloud. The checking mechanism mainly checks whether there is byte loss or disorder in the transmitted data. When the cloud determines that there is loss or disorder in the transmitted data, no response information is sent to the sending end, i.e. the gateway. If the sending end cannot receive the response information after sending the data, it is considered to be an abnormal interruption, and data transmission is performed again. After data checking, if the checking is correct, the cloud parses the data according to the transmission protocol, converts the data into the required format, and saves and processes the data.

[0065] In one embodiment, when the checking result is checking success, the data is format-converted to obtain data in a target format; the data in the target format is stored and backed up.

[0066] After data checking, if the checking is correct, the cloud parses the data according to the transmission protocol, formats the data into the required data format, stores the processed data into a database, and additionally stores the data as an XML or JSON format backup.

[0067] The virtual power plant interaction method provided by the embodiment of the application is applied to a virtual power plant cloud of a virtual power plant communication architecture, data transmission is accepted after identity verification of a gateway, data is checked, the data is processed and saved based on the checking result, the data transmission process of the virtual power plant cloud and the gateway is completed, and the security of virtual power plant data transmission is improved.

[0068] A virtual power plant interaction method is provided in the embodiment, which is applied to a cloud of a virtual power plant communication architecture, Figure 2 The flowchart of the virtual power plant interaction method according to the embodiment of the application is shown in Figure 2 The flowchart includes the following steps:

[0069] S21, receiving a scheduling task of a power grid, and screening a virtual power generator and generating a scheduling plan based on the scheduling task.

[0070] The cloud, the edge and the end can be scheduled according to requirements. The cloud in the virtual power plant communication architecture receives a scheduling task instruction issued by the power grid, the scheduling task can be load adjustment of a power system, screens a virtual power generator participating according to a task scenario, a target and a state of a current resource terminal contained in the scheduling task, and generates a scheduling plan.

[0071] S22, sending the scheduling plan to the gateway to obtain a participation result of the resource terminal.

[0072] The cloud sends the scheduling plan to the gateway, the gateway notifies each resource terminal after receiving the scheduling plan, waits for feedback of the resource terminal, and obtains the participation result of the resource terminal. The feedback content of the resource terminal includes the participation result of the resource terminal, for example, whether to participate in the scheduling task.

[0073] S23, confirming a final scheduling plan based on the participation result of the resource terminal, calculating predicted load data and publishing the final scheduling plan to the gateway.

[0074] When the participation result of the resource terminal meets the scheduling plan, the final scheduling plan is confirmed. The predicted load data is calculated according to the final scheduling plan, and the final scheduling plan is published.

[0075] After the gateway receives the feedback result of the resource terminal, the feedback result is sent to the cloud. The cloud summarizes all feedback results and judges whether the feedback results meet the scheduling plan. If there is a resource terminal that cannot participate, the resources are re-screened and feedback information is obtained again after excluding the resources that do not participate.

[0076] For example, the dispatching task requires cutting 500 kW load, the aggregation regulation platform will first select a batch of resource terminals whose total adjustable load in the time period is greater than 500 kW, if all the resource terminals are willing to participate, the dispatching plan is met, which means that the resource terminals can be taken over and controlled by the cloud in the dispatching time. If there is a resource terminal that does not participate, resulting in the total amount cannot reach 500 kW, then a batch of resource terminals need to be selected again until the total amount of the resource terminals that agree to participate in the regulation is greater than 500 kW.

[0077] If the feedback result meets the dispatching plan, that is, all the resource terminals can participate, the cloud confirms the final dispatching plan, calculates the baseline according to the dispatching plan and saves the baseline data, wherein the baseline data can include the predicted load data. Then the cloud officially publishes the dispatching plan to the gateway, and the gateway receives the dispatching plan and notifies the participating resource terminals.

[0078] S24, receiving actual load data generated by at least one resource terminal after executing the dispatching decomposition task allocated by the gateway.

[0079] After the gateway receives the final dispatching plan published by the cloud, the task is decomposed to obtain a dispatching decomposition task, and the dispatching instruction corresponding to each dispatching decomposition task is issued to each resource terminal. After each resource terminal receives the dispatching instruction, it begins to execute the corresponding dispatching decomposition task.

[0080] There can be multiple participating resource terminals in the task scheduling process, and the cloud monitors the results of each resource terminal when executing the task, that is, the actual load data generated by the resource terminal.

[0081] S25, settling the actual load data based on the predicted load data to obtain a settlement result, so as to complete the dispatching task of the power grid.

[0082] The actual load data is compared with the predicted load data to obtain a settlement result. Each resource terminal will receive a subsidy income for responding to the dispatching instruction once. The income is obtained through the settlement result. After obtaining the calculation result, the cloud can send the settlement result to the gateway, the gateway performs settlement feedback and sends the feedback result to the cloud, and the cloud archives the feedback result and the dispatching data, thereby completing the dispatching task issued by the power grid.

[0083] The virtual power plant interaction method provided in the embodiment of the application takes the gateway as a transfer, receives the dispatching task published by the power grid through the cloud, generates a dispatching plan according to the dispatching task, confirms the participating resource terminals through the gateway, and issues the final dispatching plan to enable each resource terminal to execute the dispatching task, thereby improving the efficiency of task execution.

[0084] In the embodiment, a virtual power plant communication architecture is provided. Please refer to Figure 3 ,Figure 3 is a structural schematic diagram of a virtual power plant communication architecture according to an embodiment of the present application. As shown in the figure, the virtual power plant communication architecture comprises at least one resource terminal; a gateway, to which the at least one resource terminal is connected, the gateway being configured to execute a virtual power plant interaction method; and a cloud, connected to the gateway, the cloud being configured to execute the virtual power plant interaction method. Figure 3

[0085] As shown in the figure, the virtual power plant communication architecture comprises a cloud, an edge and a terminal, the aggregation and regulation platform serving as the "cloud", i.e. the "cloud", to realize central control; the Internet of Things aggregation gateway, i.e. the gateway, serving as the "edge" to realize the role of connecting the resource terminal and the aggregation and regulation platform; and the flexible resource terminal, i.e. the resource terminal, serving as the "terminal" to include various sources, loads and storage resources with different response capabilities, the flexible resource including distributed photovoltaic, wind power, combined heat and power, distributed energy storage, commercial buildings, residential buildings, electric vehicles and industrial parks, etc., the flexible resource terminal covering photovoltaic inverters, wind turbines, boilers, water pumps, air conditioners, water heaters, charging stations and production lines, etc. The interaction of the virtual power plant communication architecture is shown in the figure. Figure 4 Figure 5

[0086] The virtual power plant communication architecture involves a wide-area network layer, a regional autonomous layer and a local communication layer. The wide-area network layer realizes communication between the virtual power plant aggregation and regulation platform and the Internet of Things aggregation and control gateway, the feature of this layer being that the communication distance is generally more than 1 km, the communication system is various and public network / special network fusion bearing is involved. The wide-area network layer realizes data collection of the Internet of Things aggregation and control gateway through uplink communication, realizes dispatching instructions through downlink communication, realizes interaction through 4G / 5G and Ethernet, and uses IEC 60870-5-104, DL / T 1867-2018 and Q / GDW 1376.1 as the communication protocol.

[0087] The regional autonomous layer realizes communication between the Internet of Things aggregation and control gateways, the feature of this layer being that the communication distance is generally between 100 m and 1 km, and local area network communication technologies such as Lora and Ethernet are used to realize interaction, the downlink of the Internet of Things aggregation and control gateway involves various protocols such as MQTT, Modbus, Q / GDW 1376.1 and OPC, these protocols can be converted into an application layer protocol and an upper layer through a protocol conversion module in the gateway to shield the difference between the protocols.

[0088] ​​​The local communication layer realizes the communication between the edge aggregation control gateway and the flexible resource terminal, and the feature of this layer is that the communication distance is generally within 100 m. The uplink of the local communication layer realizes the communication of the data acquisition of the flexible resource terminal device, and the downlink realizes the communication of task analysis, strategy selection and control instruction issuing. The bus technology or the micro-power wireless technology, such as RS485, Ethernet, WiFi and the like, is adopted to realize the interaction, and the Modbus, OPC and BACnet are adopted as the communication protocol.

[0089] Inside the virtual power plant cloud, that is, inside the aggregation control platform, there are a communication module, a data storage and reading module, a calculation training module, a background data interface module and a front-end function module, as shown in Figure 6 The communication module realizes the cloud communication service, the data storage and reading module realizes the database service, the calculation training module realizes the application service, the background data interface module realizes the Web service, and the front-end function module realizes the virtual power plant client.

[0090] The communication module realizes the data communication between the aggregation control platform center server and the access flexible resource terminal, transmits and analyzes the data through a specific communication protocol, and mainly includes the reception and scheduling instruction issuing of data and instructions. The communication module mainly supports TCP and Http modes, and is developed by using the Netty framework. The communication module mainly includes resource data acquisition, power business docking and scheduling instruction issuing. The resource data acquisition is periodically sent by the Internet of Things aggregation control gateway to the communication module (such as once every 5 minutes), the data is packaged and sent according to the specified protocol (such as Q / GDW 1376.1 communication protocol) at the resource end, and the data is obtained after being analyzed by the server after being received. The power business docking includes the power company transaction business and the dispatching business, and the platform server will develop the data docking service according to the related business protocol (such as DL / T 1867-2018 specification), complete the task acceptance, data reporting and the like docking work with the power company. The scheduling instruction issuing is that the platform determines the scheduling plan, and issues the scheduling instruction to the participating resource. After receiving the instruction, the resource decomposes the instruction and operates the related equipment according to the time to complete the scheduling task. The Internet of Things aggregation control gateway will access the scheduling instruction service through a specific protocol (such as DL / T 1867-2018 specification) at a time, and feedback the connection state and obtain the scheduling task.

[0091] The data storage and reading module completes the data storage and data query calling functions. This module is developed by using JDBC and mybatis-plus, and completes the database operation and object relationship mapping. The service first completes the data storage operation after the basic verification of the resource data, and after the storage, the service will compress and backup the data in the xml or json file format. When the platform function accesses the data, the data reading service is uniformly operated.

[0092] The calculation training module mainly includes data verification calculation, load prediction calculation and regular display data calculation, adopts the XXL-JOB framework to perform task management and scheduling. The data verification calculation task verifies the collected data according to the abnormal data verification algorithm, and marks the abnormal data according to the verification result. The task is scheduled and executed when the data is collected and stored, and the calculation frequency is extremely high; the load prediction calculation is divided into automatic prediction calculation and manual calculation, and the platform will start the load prediction calculation task at the specified time every day according to the scheduling plan, calculate and store the prediction data. When the user needs (such as scheduling release, data correction, etc.), the calculation service can be manually called to calculate and correct the prediction data; the regular display data calculation arranges the collected data into regular data (such as 15-minute interval data) and display data according to the architecture and configuration requirements, so as to facilitate the architecture function call and improve the data query efficiency. The calculation task is generally executed at a frequency of 15 minutes or 1 hour.

[0093] The background data interface module provides json format data results for the front-end page by using WebApi, wherein the WebApi is developed by using the SpringBoot framework, and the request log and exception management are realized by using the SpringBoot framework aop. The WebApi security problem is controlled and managed by using Spring Security, and perfect and extensible identity verification and authorization are provided. The Spring Security realizes the identity verification of all webapi accesses through a filter.

[0094] The front-end function module is a page operated and used by a user, the user accesses a function page through a browser, the VUE framework is adopted for development, the page is built and rendered by using Html5+CSS, and the data communication with the back-end WebApi is realized by using AJAX. The front-end function module page is designed according to the function requirement and user interaction logic, and the virtual power plant resource data, analysis result, scheduling virtual power plant task flow and resource equipment are displayed through the function page.

[0095] The virtual power plant communication architecture can shield the protocol difference of the resource terminal through the protocol conversion module in the gateway, is conducive to the standardization in the interaction process, provides a basis for edge computing and power grid boundary protection, and the edge ordered control can effectively avoid the security hidden danger caused by the simultaneous investment and withdrawal of a large number of distributed resources to the power grid. In addition, management interfaces can be provided for each end user involved in the architecture, and the edge node serves as a portal for taking over and releasing resource control authority, and can provide autonomous operation boundaries for users in a period of time without participating in power grid interaction.

[0096] Please refer to Figure 7 , Figure 7 is a cloud-edge data communication flow diagram of the virtual power plant of the embodiment of the application, as described above, the virtual power plant includes a cloud and an edge, such as Figure 7As shown, the cloud and the edge in the virtual power plant communication architecture can transmit data.

[0097] The edge initiates a connection request to the cloud, which can be a TCP request. When the edge establishes a connection with the cloud, a heartbeat connection detection can be sent to the cloud. Based on the heartbeat detection result fed back by the cloud, the connection status between the edge and the cloud is confirmed. If the connection is unsuccessful, the edge initiates a connection request again. If the connection is successful, the edge sends identity authentication to the cloud, and the cloud performs identity authentication. If the identity authentication is unsuccessful, the process ends. If the identity authentication is passed, the edge initiates data transmission to the cloud, and the cloud receives the data transmitted by the edge. The data mainly includes energy data, which can include voltage, current, switch state, whether active, power angle, grid point information, etc. Different data can be transmitted according to different resource types.

[0098] After receiving the data, the cloud checks the received data. The edge determines whether data retransmission is needed according to the data checking result of the cloud. The checking mechanism mainly checks whether there is byte loss or disorder in the transmitted data. If the checking is unsuccessful, data retransmission is performed. If the checking is successful, the cloud processes the data, including parsing the data according to the transmission protocol, formatting the data into the required data format, storing the processed data into a database, and additionally saving the data as an XML or JSON format backup. After the data processing is completed, the data transmission process ends.

[0099] Please refer to Figure 8 , Figure 8 is a task scheduling process schematic diagram of the virtual power plant of the embodiment of the present application, as Figure 8 shown, the virtual power plant communication architecture can perform task scheduling.

[0100] The cloud in the virtual power plant communication architecture receives the scheduling task instructions issued by the power grid. The scheduling task can be load adjustment of the power system. According to the task scenario, target and current resource terminal state contained in the scheduling task, the participating virtual power generators are screened, the scheduling plan is generated and previewed. The scheduling plan is sent to the edge. After receiving the scheduling plan, the edge notifies each resource terminal and waits for the feedback of the resource terminal to obtain the participation result of the resource terminal. The feedback content of the resource terminal includes the resource participation result, such as whether to participate in the scheduling task. If not, the resource terminal ends the task process. According to the participation result of the resource terminal, the participation feedback is obtained and sent to the cloud. The cloud summarizes the participation and judges whether it is qualified, that is, whether it meets the scheduling plan. If it does not meet the scheduling plan, that is, there is a resource terminal that cannot participate, the resources are re-screened and feedback information is obtained again after excluding the non-participating resources.

[0101] If the participation result is qualified, i.e., all resource terminals can participate, the cloud confirms the scheduling task, performs baseline prediction calculation according to the scheduling task, and saves baseline data, wherein the baseline data can include predicted load data. Then the cloud publishes the scheduling plan to the edge, the edge receives the scheduling plan, parses the scheduling tasks contained in the scheduling plan, and sends the scheduling tasks to each resource terminal. Each resource terminal responds to the scheduling instruction and starts to execute the scheduling task.

[0102] During the task execution process, the cloud monitors the results of each resource terminal when executing the task, i.e., the actual load data generated by the resource terminal. Settlement is performed according to the actual load data, i.e., the actual load data is compared with the predicted load data to obtain a settlement result and publish the settlement result. The edge receives the published settlement result and performs settlement feedback, sends the settlement feedback to the cloud, the cloud views the feedback result, and archives the scheduling data and the feedback result, completing the task scheduling process.

[0103] Please refer to Figure 9 , Figure 9 is a structural schematic diagram of an electronic device provided by an embodiment of the application, as shown in Figure 9 , the electronic device can include at least one processor 601, such as a CPU (Central Processing Unit, central processor), at least one communication interface 603, a memory 604, and at least one communication bus 602. The communication bus 602 is used to realize the connection and communication between the components. The communication interface 603 can include a display screen (Display), a keyboard (Keyboard), and an optional communication interface 603, which can also include a standard wired interface and a wireless interface. The memory 604 can be a high-speed RAM memory (Random Access Memory, volatile random access memory), or a non-volatile memory, such as at least one disk memory. The memory 604 can also be at least one storage device located away from the aforementioned processor 601. The processor 601 can combine the communication architecture described in Figure 3 , the memory 604 stores an application program, and the processor 601 invokes the program code stored in the memory 604 to execute any of the above method steps.

[0104] The communication bus 602 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication bus 602 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation,Figure 9 Only one bus or type of bus might exist but implementations that have more than one bus or type of bus can use the terms to refer to the busses as collectively a "bus." As that is a tradeoff between performance, cost, and engineering effort, others will resonate with these design choices.

[0105] The memory 604 can include volatile memory (e.g., random access memory, RAM), non-volatile memory (e.g., flash memory, hard disk drive, or solid-state drive), or a combination of volatile and non-volatile memory. The memory 604 can be used to store data and / or code for use by the processor 601, for example.

[0106] The processor 601 can be a central processing unit (CPU), a network processor (NP), or both, for example.

[0107] The processor 601 can further include a hardware chip. The hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0108] Optionally, the memory 604 is further configured to store program instructions. The processor 601 can invoke the program instructions to implement the virtual power plant interaction method as shown in the embodiments of the present application.

[0109] The embodiment of the present application further provides a non-transitory computer storage medium, which stores computer executable instructions, and the computer executable instructions are used for executing the virtual power plant interaction method in any method embodiment described above. The storage medium can be a disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory, a Hard Disk Drive (HDD) or a Solid-State Drive (SSD), etc. The storage medium can also include a combination of the above-mentioned memories.

[0110] Although the embodiments of the present application are described in conjunction with the drawings, various modifications and changes can be made by those skilled in the art without departing from the spirit and scope of the present application, and such modifications and changes are intended to fall within the scope of the appended claims.

Claims

1. A virtual power plant interaction method, characterized by, The virtual power plant cloud applied to the virtual power plant communication architecture includes at least one resource terminal, a gateway and a virtual power plant cloud, the at least one resource terminal is connected with the gateway, the gateway is an Internet of Things aggregation gateway, the virtual power plant cloud is connected with the gateway, a protocol conversion module in the gateway is used for converting protocols into an application layer protocol and communicating with an upper layer, and the method comprises the following steps: A connection request initiated by the gateway is received, and a connection state with the gateway is confirmed, the connection state being determined based on a heartbeat detection result; When the connection is normal, identity authentication sent by the gateway is received; When the identity authentication is passed, data transmission initiated by the gateway is received, and the data is checked to obtain a checking result; The checking result is fed back to the gateway, and the data is processed based on the checking result to complete the transmission of the data; A scheduling task of a power grid is received, and a virtual generator is screened based on the scheduling task and a scheduling plan is generated; The scheduling plan is sent to the gateway to obtain a resource terminal participation result; The final scheduling plan is confirmed based on the resource terminal participation result, predicted load data is calculated, and the final scheduling plan is published to the gateway; Actual load data generated by at least one resource terminal after receiving and executing a scheduling decomposition task distributed by the gateway is received; The actual load data is settled based on the predicted load data to obtain a settlement result, so as to complete the scheduling task of the power grid.

2. The method of claim 1, wherein, The checking result is fed back to the gateway, and the data is processed based on the checking result to complete the transmission of the data, which comprises the following steps: When the checking result is a checking success, the data is format-converted to obtain data in a target format; The data in the target format is stored and backed up.

3. The method of claim 1, wherein, The final scheduling plan is confirmed based on the resource terminal participation result, predicted load data is calculated, and the final scheduling plan is published to the gateway, which comprises the following steps: When the resource terminal participation result meets the scheduling plan, the final scheduling plan is confirmed; Predicted load data is calculated according to the final scheduling plan, and the final scheduling plan is published.

4. A virtual power plant interaction method, characterized by, The gateway applied to the virtual power plant communication architecture includes at least one resource terminal, a gateway and a virtual power plant cloud, the at least one resource terminal is connected with the gateway, the gateway is an Internet of Things aggregation gateway, the virtual power plant cloud is connected with the gateway, a protocol conversion module in the gateway is used for converting protocols into an application layer protocol and communicating with an upper layer, and the method comprises the following steps: A connection request is initiated to the virtual power plant cloud, and a connection state with the virtual power plant cloud is confirmed, the connection state being determined based on a heartbeat detection result; When the connection is normal, identity authentication is sent to the virtual power plant cloud; When the identity authentication is passed, data transmission is initiated to the virtual power plant cloud, so that the virtual power plant cloud checks the data; Based on a checking result of the data by the virtual power plant cloud, it is judged whether data retransmission is needed to complete the transmission of the data; A scheduling plan generated by the virtual power plant cloud based on a scheduling task is received; According to the scheduling plan, a resource terminal participation result is confirmed for at least one resource terminal, and the resource terminal participation result is fed back to the virtual power plant cloud; A final scheduling plan confirmed by the virtual power plant based on the participation result is received, the final scheduling plan is decomposed to obtain a scheduling decomposition task, and the scheduling decomposition task is distributed to at least one resource terminal to complete execution of the scheduling task.

5. The method of claim 4, wherein, The confirmation includes a connection state with the virtual power plant cloud, and the connection state includes: When the gateway establishes a connection with the virtual power plant cloud, a heartbeat connection detection is sent to the virtual power plant cloud; Based on a heartbeat detection result fed back by the virtual power plant cloud, the connection state is confirmed.

6. A virtual power plant communication architecture, characterized by The system includes: At least one resource terminal; A gateway, the at least one resource terminal is connected with the gateway, and the gateway is used to execute the virtual power plant interaction method in any one of claims 4-5; A cloud, the cloud is connected with the gateway, and the cloud is used to execute the virtual power plant interaction method in any one of claims 1-3.

7. An electronic device, comprising: The system includes: A memory and a processor, the memory and the processor are connected with each other in communication, the memory stores computer instructions, and the processor executes the virtual power plant interaction method in any one of claims 1-5 by executing the computer instructions.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions are used to make a computer execute the virtual power plant interaction method in any one of claims 1-5.

Images