Cloud hosting system and method for energy storage EMS system

Abstract

The invention provides an energy storage EMS system cloud hosting system and method, and the system comprises a monitoring center which is used for keeping heartbeat and basic information synchronization with a communication front-end processor and local energy storage equipment; the communication front-end processor and each local energy storage device are used for respectively initiating a cloud hosting request to the monitoring center when detecting that a preset hosting trigger condition is met; the monitoring center is used for initiating a trusteeship application and basic information to the cloud container trusteeship center after receiving a cloud trusteeship request; the cloud container trusteeship center is used for dynamically injecting the basic information corresponding to the local energy storage equipment into a cloud energy storage container corresponding to the local energy storage equipment to complete initialization of the cloud container trusteeship center, and a response result of trusteeship success is issued through the monitoring center; and the communication front-end processor is also used for disconnecting with the local energy storage equipment and connecting with the cloud energy storage system to carry out cloud hosting after a response result of successful hosting is issued.

Description

Technical Field

[0001] This invention relates to the field of user-side energy storage management systems, and more particularly to a cloud-hosted system and method for an energy storage EMS system. Background Technology

[0002] When deploying small to medium-sized user-side energy storage EMS systems, a dual-machine hot standby approach is typically used to avoid data loss due to local server failures. This solution requires each local energy storage system to be equipped with dual machines for backup, which is too costly. Other solutions, due to cost considerations, usually employ single-machine deployment, and in many cases, they do not connect to a cloud platform. The EMS system operates in standalone mode, and if the server fails, the energy storage EMS system will become inoperable. Even with a cloud platform, the data transmission path between the conventional cloud platform, local energy storage system, and communication front-end unit is similar to a cascaded, hierarchical reporting system. If any node fails, the energy storage EMS system will become inoperable, thus failing to prevent downtime and resulting in data loss.

[0003] Therefore, developing a low-cost cloud-hosted system and method for energy storage EMS systems to ensure data integrity and system reliability, and to avoid downtime due to malfunctions, is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] To address the aforementioned technical deficiencies, this invention proposes a cloud-hosted system for energy storage EMS systems. By constructing a dual-channel cloud-hosted triggering system, both the communication front-end and local energy storage devices can communicate and synchronize data with the monitoring center. Combined with the container provisioning function of the cloud container hosting center, cloud hosting can be achieved when any node experiences an anomaly and triggers the hosting rules. This realizes the cloud hosting function for energy storage systems in the event of a failure, ensuring no data loss and system availability.

[0005] This invention provides a cloud-hosted system for an energy storage EMS system, comprising: Communication front-end server, local energy storage equipment, monitoring center and cloud container hosting center; The monitoring center is used to keep synchronized with the basic information of local energy storage devices and to store the basic information, which includes: site information, site device topology, policy information and basic data. The communication front-end is used to initiate a cloud hosting request to the monitoring center when it detects an abnormal communication situation between itself and the local energy storage device that meets the preset hosting trigger conditions. When the local energy storage device detects an abnormality in its own operation that meets the preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center. The monitoring center is also connected to the cloud container hosting center for: receiving the cloud hosting request and sending a hosting application and the basic information to the cloud container hosting center. The cloud container hosting center is used to dynamically inject the basic information into the cloud energy storage container corresponding to the local energy storage device, and send the successful hosting response to the communication front-end or the local energy storage device through the monitoring center. The communication front-end is used to disconnect from the local energy storage device and connect to the cloud energy storage system for cloud hosting after the successful hosting response is sent.

[0006] Optionally, the monitoring center is also used to notify the cloud container hosting center of the fault clearance information by maintaining a heartbeat with the communication front-end or the local energy storage device when the fault is cleared, thereby terminating cloud hosting; the fault clearance information includes information on the clearance of its own abnormal operation or information on the clearance of communication abnormality.

[0007] Optionally, the cloud container hosting center is further configured to determine, upon receiving the cloud hosting request, whether there are any free cloud energy storage containers in the idle area of ​​the cloud container hosting center; If it is determined that there is a cloud-based energy storage container, then the monitoring center is used to: randomly select a cloud-based energy storage container from the idle area for hosting; otherwise, the monitoring center is used to dynamically create a cloud-based energy storage container in the idle area for hosting.

[0008] Optionally, the cloud container hosting center is used to dynamically inject the basic information corresponding to the local energy storage device into the cloud energy storage container when it receives a cloud hosting application, so as to complete the cloud initialization. At this time, the cloud energy storage container enters the running area; and is also used to: send out a response result of successful hosting.

[0009] The communication front-end is configured to: receive a successful hosting response from the monitoring center when a cloud hosting request is initiated by the communication front-end; and to: disconnect from the local energy storage device and connect to the cloud energy storage system upon receiving the successful hosting response. The local energy storage device is used to: receive a successful hosting response from the monitoring center when a cloud hosting request is initiated by the local energy storage system; and is also used to: After receiving a successful hosting response, a communication disconnection notification is sent to the communication front-end machine, instructing the communication front-end machine to disconnect from itself, and the communication front-end machine connects to the cloud container hosting center.

[0010] Optionally, the communication front-end unit is further configured to: when the fault is cleared, notify the monitoring center of the clearing of the communication anomaly by maintaining a heartbeat; and simultaneously, it is also configured to: restore the communication connection with the local energy storage device and disconnect the connection with the cloud energy storage system. The cloud container hosting center is also used to: release the cloud energy storage containers in the operating area to the idle area and release them from cloud hosting.

[0011] Optionally, the local energy storage device is further configured to: when the fault is cleared, notify the monitoring center of the clearance of its abnormal operation by maintaining a heartbeat; and simultaneously, send a communication connection notification to the communication front-end machine, instructing the communication front-end machine to restore the communication connection with the local energy storage device and disconnect the connection with the cloud energy storage system. The cloud container hosting center is also used to: release the cloud energy storage containers in the operating area to the idle area and release them from cloud hosting.

[0012] Optional, including: two or more sets of distributed local energy storage devices; Each group of local devices includes a local energy storage device and a communication front-end unit connected to it. Each group of local devices shares a single monitoring center and cloud container hosting center.

[0013] This invention also provides a cloud-based hosting method for an energy storage EMS system, applied to the aforementioned cloud-based hosting system for an energy storage EMS system, comprising: The monitoring center maintains a heartbeat with the communication front-end and the local energy storage device to synchronize the basic information of the local energy storage device; the monitoring center saves the basic information of each local energy storage device in real time; the basic information includes: site information, site device topology, policy information and basic data; The communication front-end unit detects communication anomalies; simultaneously, the local energy storage device detects its own operational anomalies. When the communication front-end device detects a communication anomaly between itself and the local energy storage device that meets the preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center; or, when the local energy storage device detects an operational anomaly that meets the preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center. After receiving the cloud hosting request, the monitoring center sends a hosting application and basic information associated with the local energy storage device to the cloud container hosting center. The cloud container hosting center dynamically injects the basic information of the local energy storage device into the cloud energy storage container corresponding to the local energy storage device, and completes the initialization of the cloud container hosting center. At this time, the successful hosting response will be sent to the local energy storage device or the communication front-end through the monitoring center. Upon receiving the successful hosting response, the communication front-end disconnects from the local energy storage device and connects to the cloud energy storage system for cloud hosting.

[0014] Optionally, when the fault is resolved, the monitoring center will notify the monitoring center of the fault resolution information by maintaining a heartbeat, so as to release the cloud hosting; the fault resolution information includes information on the resolution of its own abnormal operation or information on the resolution of communication abnormality.

[0015] Compared with existing technologies, the above technical solution has the following advantages: 1. This invention constructs a dual-channel cloud-hosted triggering system. Both the communication front-end and the local energy storage device can communicate and synchronize data with the monitoring center. Combined with the container provisioning function of the cloud container hosting center, cloud hosting can be realized when any node malfunctions and triggers the hosting rules. This realizes the cloud hosting function when the energy storage system fails, ensuring that data is not lost and system availability is maintained.

[0016] 2. Once the fault is resolved, the hosting is immediately terminated, releasing the cloud container hosting center to prepare for potential future faults and enabling local energy storage devices to dynamically share the same cloud container hosting center during a fault.

[0017] 3. The managed storage solution of this invention is particularly suitable for energy storage systems composed of distributed local energy storage devices. Any failed local energy storage device can share the cloud container hosting center. Compared with traditional dual-machine backup, it eliminates the need to set up dual-machine backups for each local energy storage device, greatly reducing system costs. Moreover, the more local energy storage devices are configured, the more the cost advantage of this solution becomes apparent.

[0018] 4. A hosting trigger mechanism is set up for both nodes. When the local energy storage device is running normally, the cloud hosting mechanism will not be triggered, and no 4G traffic will be generated for communication between the local and cloud nodes. 4G traffic charges will only be incurred when cloud hosting is successful. After the fault is resolved, communication with the cloud will be terminated accordingly to avoid unnecessary 4G traffic generated by simultaneous operation of the local energy storage device and the cloud, thus avoiding traffic waste.

[0019] 5. Upon receiving the hosting request, the cloud container hosting center randomly selects a cloud energy storage container from the idle area for hosting; otherwise, it dynamically creates a cloud energy storage container in the idle area for hosting. After hosting ends, excessive cloud energy storage containers in the idle area are deleted to ensure that there is no excessive redundancy in the idle area, while also ensuring cyclical activation. This achieves dynamic sharing of cloud containers. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the structure of a cloud-hosted energy storage EMS system according to an embodiment of the present invention; Figure 2 This is a flowchart illustrating a cloud-based hosting method for an energy storage EMS system according to an embodiment of the present invention. Figure 3 This is a schematic diagram of the hosting process of a cloud-based hosting system for an energy storage EMS system, as described in one embodiment of the present invention. Figure label: 1-Local energy storage equipment; 2-Communication front-end processor; 3-Monitoring Center; 4-Cloud container hosting center. Detailed Implementation

[0021] The advantages of the present invention will be further illustrated below with reference to the accompanying drawings and specific embodiments.

[0022] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appendix.

[0023] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “described,” and “the” as used in this disclosure and the appendices are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0024] In the description of this invention, it should be understood that the terms "inner" and "outer", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this invention.

[0025] In the description of this invention, unless otherwise specified and limited, it should be noted that the terms "installation", "connection" and "linking" should be interpreted broadly. For example, they can refer to mechanical or electrical connections, or internal connections between two components. They can be direct connections or indirect connections through an intermediate medium. Those skilled in the art can understand the specific meaning of the above terms according to the specific circumstances.

[0026] In the following description, suffixes such as "module," "part," or "unit" used to denote elements are merely for the purpose of illustrating the invention and have no specific meaning in themselves. Therefore, "module" and "part" may be used interchangeably.

[0027] Figure 1 A schematic diagram of a cloud-hosted energy storage EMS system according to an embodiment of the present invention is shown.

[0028] See Figure 1 The energy storage EMS system cloud hosting system includes: a communication front-end unit 2, a local energy storage device 1, a monitoring center 3, and a cloud container hosting center 4.

[0029] The monitoring center 3 is used to maintain a heartbeat with the communication front-end unit 2 and the local energy storage device 1 so that it can synchronize with the basic information of the local energy storage device 1; it is also used to store the basic information of the local energy storage device 1; the basic information includes: site information, site equipment topology, policy information and basic data; The communication front-end unit 2 is used to detect communication anomalies. When it detects that the communication anomaly between itself and the local energy storage device 1 meets the preset hosting trigger conditions, it sends a cloud hosting request to the monitoring center 3. The local energy storage device 1 is used to detect its own abnormal operation. When it detects that its own abnormal operation meets the preset hosting trigger conditions, it sends a cloud hosting request to the monitoring center 3. The monitoring center 3 is also connected to the cloud container hosting center 4; the monitoring center 3 is used to: after receiving the cloud hosting request, initiate a hosting application to the cloud container hosting center 4 and send basic information associated with the local energy storage device 1.

[0030] The cloud container hosting center 4 is used to dynamically inject the basic information of the corresponding local energy storage device 1 into the cloud energy storage container corresponding to the local energy storage device 1, completing the initialization of the cloud container hosting center 4. At this time, the successful hosting response result is sent to the communication front-end machine 2 or the local energy storage device 1 through the monitoring center 3. In this embodiment, the monitoring center 3 uniformly maintains the site information, device topology, policy information and basic data of the local energy storage system, and dynamically injects the above information into the corresponding cloud energy storage container when hosting in the cloud, so that the cloud system and the hosted local system are consistent in configuration and topology after startup, realizing the smooth replacement of the local energy storage system by the cloud energy storage. In a specific example, the cloud container hosting center 4 is a cloud Docker container hosting center; the cloud energy storage container is an energy storage EMS system container.

[0031] The communication front-end unit 2 is communicatively connected to the local energy storage device 1. The communication front-end unit 2 is also used to disconnect from the local energy storage device 1 and connect to the cloud energy storage system for cloud-based hosting after the successful hosting response is sent. In this embodiment, after successful hosting, by controlling the communication front-end unit 2 to disconnect from the local energy storage system and connect to the cloud energy storage system for hosting, automatic redirection of the control link is achieved, avoiding conflicts caused by parallel control between the cloud and local systems.

[0032] This invention provides a cloud-hosted energy storage EMS system, which constructs a dual-channel cloud-hosted triggering system. This system enables cloud-hosting in the event of a fault in the energy storage system, ensuring data integrity and system availability. By simultaneously monitoring the rules for triggering cloud-hosting on both the communication front-end unit 2 and the local energy storage EMS system, cloud-hosting can be initiated when communication between the communication front-end unit 2 and the local energy storage device 1 fails, or when the local energy storage device 1 experiences an operational malfunction. This avoids the problem of a single monitoring node failure preventing the hosting from triggering, thus improving the reliability and fault tolerance of the energy storage EMS system. When the local energy storage device 1 is operating normally, the cloud-hosting mechanism is not triggered, preventing the generation of 4G traffic for communication between the local and cloud systems. 4G traffic charges are only incurred when cloud-hosting is successful.

[0033] In a further preferred embodiment of the present invention, the cloud-hosted energy storage EMS system includes: two or more groups of distributed local energy storage devices 1. Each group of local devices includes a local energy storage device 1 and a communication front-end unit 2 connected to it; each group of local devices shares a monitoring center 3 and a cloud container hosting center 4.

[0034] This invention provides a cloud-hosted energy storage EMS system, which is particularly suitable when the energy storage system consists of distributed local energy storage devices 1. Failed local energy storage devices 1 can share a cloud-based container hosting center 4. Compared to traditional dual-machine backup, it eliminates the need for dual-machine backup for each local energy storage device 1, significantly reducing system costs. The more local energy storage devices 1 are configured, the more the cost advantage of this solution becomes apparent.

[0035] In one embodiment of the present invention, the preset hosting triggering conditions for communication anomalies of the communication front-end machine 2 include: the communication interruption time between the communication front-end machine 2 and the local energy storage device 1 exceeds a preset threshold, or the number of consecutive communication command failures exceeds a preset number; specifically, for example, if the communication disconnection time between the communication front-end machine 2 and the local energy storage system exceeds 10 seconds or the number of consecutive communication commands exceeds 5, a hosting request will be initiated to the monitoring center 3.

[0036] In one embodiment of the present invention, the preset hosting trigger conditions for the abnormal operation of the local energy storage device 1 include: abnormal server resources, abnormal network or system failure warning; specifically, such as insufficient server disk, network failure, etc.

[0037] In an optional embodiment of the present invention, the cloud container hosting center 4 is further configured to, when receiving the hosting request, determine whether there are any idle cloud energy storage containers in the idle area of ​​the cloud container hosting center 4; and to: when it is determined that there are cloud energy storage containers, randomly select a cloud energy storage container from the idle area for hosting; otherwise, dynamically create a cloud energy storage container in the idle area for hosting.

[0038] In a further embodiment of the present invention, the cloud container hosting center 4 is used to allocate a unique cloud energy storage container to the local energy storage device 1. The cloud container hosting center 4 can be divided into a space area and an operating area. It is used to dynamically inject the basic information corresponding to the local energy storage device 1 into the cloud energy storage container to complete cloud initialization. At this time, the cloud energy storage container enters the operating area. It is also used to issue a response result indicating successful hosting. Before receiving the hosting request, the cloud container hosting center 4 pre-starts an idle energy storage system container in the idle area. In this scheme, the cloud container hosting center 4 obtains the basic information of the local energy storage system in real time. When there is a cloud hosting request, the monitoring center 3 can randomly select a pre-started idle energy storage system container. Simultaneously, the cloud container hosting center 4 dynamically injects the basic information of the local energy storage system currently requesting hosting, as fed back by the monitoring center 3, into the uniquely corresponding container. Cloud hosting can be achieved immediately within seconds, ensuring the efficient availability of the energy storage EMS system.

[0039] In one optional embodiment of the present invention, the communication front-end 2 is configured to: receive a successful hosting response from the monitoring center 3 when a cloud hosting request is initiated by the communication front-end 2; and to: disconnect from the local energy storage device 1 and connect to the cloud energy storage system upon receiving the successful hosting response. Simultaneously, the local energy storage device 1 is configured to: receive a successful hosting response from the monitoring center 3 when a cloud hosting request is initiated by the communication front-end 2; and to: send a communication disconnection notification to the communication front-end 2 after receiving the successful hosting response, instructing the communication front-end 2 to disconnect from itself, and the communication front-end 2 to connect to the cloud container hosting center 4. In a further embodiment of the present invention, the monitoring center 3 is further configured to, upon fault resolution, maintain a heartbeat with the communication front-end 2 or the local energy storage device 1 to inform the cloud container hosting center 4 of the fault resolution information, thereby terminating cloud hosting; the fault resolution information includes information on the resolution of its own operational abnormality or information on the resolution of communication abnormality. In this solution, once the fault is resolved, the hosting is immediately terminated, releasing the cloud container hosting center 4 to prepare for possible future faults and enabling local energy storage device 1 to dynamically share the same cloud container hosting center 4 during a fault.

[0040] In a preferred embodiment of the present invention, the cloud container hosting center 4 is further configured to, upon completion of hosting, determine whether the number of containers in the current idle area is saturated. If not saturated, the cloud energy storage containers in the running area are released to the idle area; the cloud energy storage containers are destroyed, and excessive idle area cloud energy storage containers are deleted to ensure that there is no excessive redundancy in the idle area containers. Simultaneously, cyclical activation is ensured, enabling the reuse and dynamic creation of container resources. While ensuring that the same local energy storage EMS system corresponds to only one cloud EMS container, rapid response and elastic scaling of cloud hosting are achieved.

[0041] In a further embodiment of the present invention, when a local energy storage anomaly occurs due to a communication failure, the communication front-end unit 2 is used to notify the monitoring center 3 of the resolution of the communication anomaly by maintaining a heartbeat; simultaneously, it is also used to: restore the communication connection with the local energy storage device 1 and disconnect the connection with the cloud energy storage system. The cloud container hosting center 4 is also used to: release the cloud energy storage containers in the operating area to the idle area, release the cloud energy storage containers, and terminate cloud hosting.

[0042] In one embodiment, when a local energy storage malfunctions due to its own abnormal condition, after the malfunction is resolved through manual repair or other means, the local energy storage device 1 is further configured to: when the malfunction is resolved, notify the monitoring center 3 of the resolution of its own operational malfunction by maintaining a heartbeat; simultaneously, it is also configured to: send a communication connection notification to the communication front-end 2, instructing the communication front-end 2 to restore the communication connection with the local energy storage device 1 and disconnect the connection with the cloud energy storage system. The cloud container hosting center 4 is further configured to: release the cloud energy storage containers in the operating area to the idle area, release the cloud energy storage containers, and terminate cloud hosting.

[0043] In the two embodiments of the present invention described above, after the fault is cleared, communication with the cloud is correspondingly terminated to avoid unnecessary 4G traffic generated by the simultaneous operation of the local energy storage device 1 and the cloud, thus avoiding traffic waste.

[0044] Figure 2 A flowchart illustrating a cloud-based hosting method for an energy storage EMS system according to an embodiment of the present invention is shown, which is used in the cloud-based hosting system for the energy storage EMS system as described in any of the preceding claims of the present invention.

[0045] See Figure 2 The cloud-hosting method for the energy storage EMS system includes steps S1 to S5: S1: The monitoring center maintains a heartbeat with the communication front-end and the local energy storage device respectively, so as to synchronize the basic information of each local energy storage device; the monitoring center saves the basic information of the local energy storage device in real time; the basic information includes: site information, site equipment topology, policy information and basic data.

[0046] S2: The communication front-end device detects communication anomalies; simultaneously, the local energy storage device detects its own operational anomalies. When the communication front-end device detects a communication anomaly between itself and the local energy storage device that meets preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center; or, when the local energy storage device detects its own operational anomaly that meets preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center.

[0047] S3: After receiving the cloud hosting request, the monitoring center sends a hosting application and basic information associated with the local energy storage device to the cloud container hosting center.

[0048] S4: The cloud container hosting center dynamically injects the basic information of the local energy storage device into the cloud energy storage container corresponding to the local energy storage device, and completes the initialization of the cloud container hosting center. At this time, the successful hosting response will be sent to the local energy storage device or the communication front-end through the monitoring center.

[0049] S5: Upon receiving the successful hosting response, the communication front-end unit disconnects from the local energy storage device and connects to the cloud energy storage system for cloud hosting.

[0050] To ensure successful cloud hosting, cloud hosting initialization and specific cloud energy storage container configuration are required. Furthermore, due to differences in communication connection control after the hosting request is initiated by the communication front-end and local energy storage devices, more detailed handling methods are needed. Steps S4 and S5 are explained in detail below: In one optional implementation, in step S4, the cloud container hosting center dynamically injects the basic information of the corresponding local energy storage device into the cloud energy storage container corresponding to the local energy storage device, completing the initialization of the cloud container hosting center. At this time, the successful hosting response will be sent through the steps issued by the monitoring center, specifically including: S41: The cloud container hosting center assigns a unique cloud energy storage container to the local energy storage device.

[0051] In a further optional implementation, step S41, in which the cloud container hosting center allocates a unique cloud energy storage container to the local energy storage device, specifically includes: S411: After receiving the hosting application, the monitoring center determines whether there are any free cloud energy storage containers in the free area of ​​the cloud container hosting center.

[0052] S412: If there is a cloud energy storage container, a cloud energy storage container is randomly selected from the idle area for hosting; otherwise, the cloud container hosting center dynamically creates a cloud energy storage container in the idle area for hosting.

[0053] S42: Dynamically inject the basic information corresponding to the local energy storage device into the cloud energy storage container to complete the cloud initialization. At this time, the cloud energy storage container enters the operating area.

[0054] The S43 cloud container hosting center will send out the successful hosting response through the monitoring center.

[0055] In one optional implementation, step S5, the process of disconnecting the communication front-end from the local energy storage device and connecting it to the cloud energy storage system, specifically includes: S51: When a cloud hosting request is initiated by a communication front-end machine, the communication front-end machine disconnects from the local energy storage device and connects to the cloud energy storage system when it receives the successful hosting response.

[0056] S52: When the cloud hosting request is initiated by the communication front-end machine, after the local energy storage device receives the successful hosting response, it sends a communication disconnection notification to the communication front-end machine, instructing the communication front-end machine to disconnect from itself and connect to the cloud energy storage system.

[0057] Therefore, regardless of which node triggers the hosting, this invention enables the system to disconnect from the local energy storage system and connect to the cloud energy storage system after successful hosting by controlling the communication front-end machine. This achieves automatic redirection of the control link, avoids conflicts caused by parallel control between the cloud and local systems, and ensures the data integrity and business continuity of the energy storage system.

[0058] In a further embodiment, the cloud-hosted method for the energy storage EMS system also includes: Step S6: When the fault is cleared, the monitoring center notifies the monitoring center of the fault clearance information by maintaining a heartbeat, thereby canceling the cloud-hosted operation; the fault clearance information includes information on the clearance of its own abnormal operation or information on the clearance of communication abnormality.

[0059] In one embodiment, when a local energy storage failure occurs due to a communication anomaly, step S6 includes: steps S61 to S63.

[0060] Step S61: When the fault is cleared, the communication front-end machine notifies the cloud container hosting center of the clearing information of the communication abnormality through the monitoring center by maintaining a heartbeat.

[0061] Step S62: After receiving the communication anomaly resolution notification, the cloud container hosting center releases the cloud energy storage container in the operating area to the idle area, releases the cloud energy storage container, and terminates cloud hosting.

[0062] Step S63: The communication front-end unit restores the communication connection with the local energy storage device and disconnects the connection with the cloud energy storage system.

[0063] In another embodiment, when the local energy storage malfunctions due to an abnormal operation of the local energy storage device itself, step S6 includes: S61~S63: S61: When the fault is cleared, the local energy storage device notifies the cloud container hosting center of the information that its abnormal operation has been cleared by maintaining a heartbeat.

[0064] S62: The cloud container hosting center releases the cloud energy storage container in the operating area to the idle area, releases the cloud energy storage container, and terminates cloud hosting.

[0065] S63: The local energy storage system sends a communication connection notification to the communication front-end, instructing the communication front-end to restore the communication connection with the local energy storage device and disconnect the connection with the cloud energy storage system.

[0066] Figure 3 A schematic diagram illustrating the hosting process of a cloud-based hosting system for an energy storage EMS system, conforming to an embodiment of the present invention, is shown below. Figure 3 The specific embodiments described herein (the embodiments only depict the specific architecture and management process of "Local Energy Storage EMS System 1" in detail; "Local Energy Storage EMS System 1" refers to...) Figure 3 This is the first local energy storage system in China; other local systems are similar, dynamically sharing a monitoring center and a cloud container hosting center (details omitted). A detailed description of the dual-hosting route hosting process follows: The blue line in the diagram represents the process of cloud hosting triggered by the "communication front-end machine," while the black line represents the process of cloud hosting triggered by the "local energy storage EMS system." Both monitor simultaneously, enabling the cloud container hosting center to replace local energy storage devices in data acquisition and control of PCS, BMS, and other equipment. This bidirectional monitoring ensures that cloud hosting can be implemented in the event of a failure in the energy storage EMS system, guaranteeing no data loss and system availability. Simultaneously, both the "communication front-end machine" and the "local energy storage EMS system" maintain heartbeat and basic information synchronization with the monitoring center. Therefore, the monitoring center stores basic information for each distributed energy storage EMS system, including site information, site equipment topology, policy information, and basic data. This basic information is dynamically injected into the cloud container when it is created, ensuring that the initial configuration information and equipment topology of the cloud energy storage EMS system in the hosting center are completely identical to those of the locally hosted energy storage EMS system, thus achieving a smooth replacement of the cloud container hosting center. Only one container corresponds to the same local energy storage EMS system in the cloud container hosting center; there is a one-to-one relationship between them, ensuring uniqueness.

[0067] I. The process of cloud hosting being triggered by the "communication front-end machine" monitoring: A communication anomaly rule is configured on the communication front-end machine. When the communication front-end machine detects that the communication disconnection time between it and the local energy storage EMS system exceeds 10 seconds or that more than 5 consecutive communication commands are issued, it will initiate a hosting request to the monitoring center. After receiving the hosting request, the monitoring center sends the basic information of the local energy storage EMS system to the cloud-based Docker container hosting center and then initiates a hosting application. Upon receiving the application, the hosting center first checks if there are any idle containers in the idle area. If not, it dynamically creates a container for hosting; otherwise, it randomly selects a container from the idle area. The hosting center dynamically injects the basic information of the local energy storage EMS system sent by the monitoring center into the container, completing the initialization of the cloud-based EMS system. At this point, the container enters the running area, indicating that the container is ready to replace the local energy storage EMS system at any time. The successful hosting response is transmitted to the communication front-end machine through the monitoring center. The communication front-end machine then disconnects from the local energy storage EMS system and connects to the cloud-based energy storage EMS system, realizing cloud hosting and avoiding the unavailability of the local energy storage EMS system due to communication failures.

[0068] When the fault is cleared, the communication front-end unit notifies the monitoring center of the clearance information by maintaining a heartbeat; upon receiving the clearance information, the cloud container hosting center releases the cloud energy storage containers in the operating area to the idle area and terminates cloud hosting; the communication front-end unit restores communication connection with the local energy storage device and disconnects from the cloud energy storage system (deactivation process). Figure 3 (Not shown in the image).

[0069] II. The process of "Local Energy Storage EMS System" monitoring triggering cloud hosting: Rules for triggering cloud hosting are configured on the local energy storage EMS system. For example, server disk shortages and network failures can be configured in the rule table. When a fault alarm occurs, a hosting request is sent to the monitoring center. The process from initiating the hosting request to receiving a successful hosting response from the local energy storage EMS system is the same as that of the "communication front-end" mentioned above. The difference is that after receiving the successful hosting response, the local energy storage EMS system also notifies the communication front-end to disconnect from it and connect to the cloud energy storage EMS system to achieve cloud hosting.

[0070] When the fault is cleared, the local energy storage device maintains a heartbeat and notifies the cloud container hosting center of the cleared operational status. The cloud container hosting center then releases the cloud energy storage containers from the operating area to the idle area, releasing the cloud energy storage containers and terminating cloud hosting. The local energy storage system sends a communication connection notification to the communication front-end, instructing the communication front-end to restore the communication connection with the local energy storage device and disconnect from the cloud energy storage system (deactivation process). Figure 3 (Not shown in the image).

[0071] In summary, this invention provides a novel and effective managed storage solution that enables the management of energy storage systems in the event of failure, ensuring data integrity and system availability. It is particularly suitable for energy storage systems composed of distributed local energy storage devices. By dynamically sharing a single cloud-based managed system, it significantly reduces system costs compared to traditional local dual-machine backup solutions. Furthermore, the more local energy storage devices are configured, the more pronounced the cost advantages of this solution become.

[0072] This invention constructs a dual-channel cloud-hosted triggering system. Both the communication front-end and the local energy storage device can communicate and synchronize data with the monitoring center. Combined with the container provisioning function of the cloud container hosting center, cloud hosting can be realized when any node malfunctions and triggers the hosting rules. This realizes the cloud hosting function when the energy storage system fails, ensuring that data is not lost and system availability is maintained.

[0073] This invention provides an energy storage hosting solution for situations where local energy storage fails. When the local energy storage device is operating normally, the cloud hosting mechanism is not triggered. Furthermore, once the fault is resolved, the hosting is immediately terminated, releasing the cloud container hosting center to prepare for potential future failures. This allows local energy storage devices to dynamically share the same cloud container hosting center during a fault. It also avoids unnecessary 4G traffic generated by simultaneous operation of local energy storage devices and the cloud, thus preventing bandwidth waste.

[0074] The cloud-based container hosting center dynamically creates or deletes excessive cloud storage containers in idle areas, ensuring minimal redundancy and cyclic activation. This enables dynamic sharing of cloud containers.

[0075] It should be noted that the embodiments of the present invention have better implementability and are not intended to limit the present invention in any way. Any person skilled in the art may use the above-disclosed technical content to change or modify it into equivalent effective embodiments. However, any modifications or equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention shall still fall within the scope of the technical solution of the present invention.

Claims

1. A cloud-hosted system for an energy storage EMS system, characterized in that, include: Communication front-end server, local energy storage equipment, monitoring center and cloud container hosting center; The monitoring center is used to keep the basic information of the local energy storage devices synchronized. And save the basic information; the basic information includes: site information, site equipment topology, policy information and basic data; The communication front-end is used to initiate a cloud hosting request to the monitoring center when it detects an abnormal communication situation between itself and the local energy storage device that meets the preset hosting trigger conditions. When the local energy storage device detects an abnormality in its own operation that meets the preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center. The monitoring center is also connected to the cloud container hosting center for: receiving the cloud hosting request and sending a hosting application and the basic information to the cloud container hosting center. The cloud container hosting center is used to dynamically inject the basic information into the cloud energy storage container corresponding to the local energy storage device, and send the successful hosting response result to the communication front-end or the local energy storage device through the monitoring center. The communication front-end is used to disconnect from the local energy storage device and connect to the cloud energy storage system for cloud hosting after the successful hosting response is sent.

2. The cloud-hosted energy storage EMS system as described in claim 1, characterized in that, The monitoring center is also used to notify the cloud container hosting center of the fault clearance information by maintaining a heartbeat with the communication front-end or the local energy storage device when the fault is cleared, and to release the cloud hosting; the fault clearance information includes information on the clearance of its own abnormal operation or information on the clearance of communication abnormality.

3. The cloud-hosted energy storage EMS system as described in claim 2, characterized in that, The cloud container hosting center is also used to determine whether there are any free cloud energy storage containers in the idle area of ​​the cloud container hosting center after receiving the cloud hosting request. If it is determined that there is a cloud-based energy storage container, then the monitoring center is used to: randomly select a cloud-based energy storage container from the idle area for hosting; otherwise, the monitoring center is used to dynamically create a cloud-based energy storage container in the idle area for hosting.

4. The cloud-hosted energy storage EMS system as described in claim 3, characterized in that, The cloud container hosting center is used to dynamically inject the basic information corresponding to the local energy storage device into the cloud energy storage container when it receives a cloud hosting application, so as to complete the cloud initialization. At this time, the cloud energy storage container enters the running area; and is also used to issue a response result of successful hosting.

5. The cloud-hosted energy storage EMS system as described in claim 4, characterized in that, The communication front-end is configured to: receive a successful hosting response from the monitoring center when the cloud hosting request is initiated by the communication front-end; and to: disconnect from the local energy storage device and connect to the cloud energy storage system upon receiving the successful hosting response. The local energy storage device is used to: receive a successful hosting response from the monitoring center when a cloud hosting request is initiated by the local energy storage system; and is also used to: After receiving a successful hosting response, a communication disconnection notification is sent to the communication front-end machine, instructing the communication front-end machine to disconnect from itself, and the communication front-end machine connects to the cloud container hosting center.

6. The cloud-hosted energy storage EMS system as described in claim 5, characterized in that, The communication front-end unit is also used to: when the fault is cleared, notify the monitoring center of the clearing of the communication anomaly by maintaining a heartbeat; at the same time, it is also used to: restore the communication connection with the local energy storage device and disconnect the connection with the cloud energy storage system. The cloud container hosting center is also used to: release the cloud energy storage containers in the operating area to the idle area and release them from cloud hosting.

7. The cloud-hosted energy storage EMS system as described in claim 6, characterized in that, The local energy storage device is also used to: when the fault is cleared, notify the monitoring center of the clearing of its abnormal operation by maintaining a heartbeat; at the same time, it is also used to: send a communication connection notification to the communication front-end machine, instructing the communication front-end machine to restore the communication connection with the local energy storage device and disconnect the connection with the cloud energy storage system. The cloud container hosting center is also used to: release the cloud energy storage containers in the operating area to the idle area and release them from cloud hosting.

8. The cloud-hosted energy storage EMS system as described in claim 7, Its features are, Includes: two or more sets of distributed local energy storage devices; Each group of local devices includes a local energy storage device and a communication front-end unit connected to it. Each group of local devices shares a single monitoring center and cloud container hosting center.

9. A cloud-based hosting method for an energy storage EMS system, characterized in that, A cloud-hosted system for an energy storage EMS system as described in any one of claims 1-8, comprising: The monitoring center maintains a heartbeat with the communication front-end and the local energy storage device to synchronize the basic information of the local energy storage device; the monitoring center saves the basic information of each local energy storage device in real time; the basic information includes: site information, site device topology, policy information and basic data; The communication front-end unit detects communication anomalies; simultaneously, the local energy storage device detects its own operational anomalies. When the communication front-end device detects a communication anomaly between itself and the local energy storage device that meets the preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center; or, when the local energy storage device detects an operational anomaly that meets the preset hosting trigger conditions, it initiates a cloud hosting request to the monitoring center. After receiving the cloud hosting request, the monitoring center sends a hosting application and basic information associated with the local energy storage device to the cloud container hosting center. The cloud container hosting center dynamically injects the basic information of the local energy storage device into the cloud energy storage container corresponding to the local energy storage device, and completes the initialization of the cloud container hosting center. At this time, the successful hosting response will be sent to the local energy storage device or the communication front-end through the monitoring center. Upon receiving the successful hosting response, the communication front-end disconnects from the local energy storage device and connects to the cloud energy storage system for cloud hosting.

10. The cloud-based hosting method for an energy storage EMS system as described in claim 9, characterized in that, When the fault is resolved, the monitoring center will notify the monitoring center of the fault resolution information by maintaining a heartbeat, so as to release the cloud hosting; the fault resolution information includes information on the resolution of its own abnormal operation or information on the resolution of communication abnormality.

Images