Energy storage device communication method and system, and readable storage medium

Abstract

The invention provides an energy storage device communication method and system and a readable storage medium, and relates to the technical field of Internet of Things communication, and the method comprises the steps: collecting and processing interaction data of an energy storage device through a data generation module, and dividing the interaction data into key data of a change report attribute and general data of a frequency report attribute; a globally accessible structured data storage area is constructed in an equipment memory through a data pool module to serve as a data pool; and when the data pool receives the key data and the general data pushed by the data generation module and the key data is changed, the packet report logic is triggered in real time, and when the general data is changed, the changed general data in the data pool is uniformly subjected to packet report after a preset time. According to the technical scheme, communication flow and equipment power consumption are remarkably reduced by reducing redundant data reporting, and the data pool serves as a central hub, so that an acquisition module, a calculation module and a reporting module are mutually independent, and functions are easy to expand, modify and debug.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) communication technology, and more specifically, to a communication method and system for energy storage devices, and a readable storage medium. Background Technology

[0002] Energy storage device data is reported to the cloud platform via network and MQTT (Message Queuing Telemetry Transport) protocols. The data exchanged includes multiple types of data, such as photovoltaic module data (voltage, current, power, energy, etc.), energy storage module data (voltage, current, power, energy, SOC (State of Charge), SOH (State of Health), etc.), inverter module data, and IoT (Internet of Things) smart accessory data.

[0003] In existing technologies, data reporting by devices often employs a simple timed reporting mechanism, meaning data is sent to the cloud platform at fixed intervals regardless of changes. This approach has the following drawbacks: Existing energy storage devices commonly use timed reporting mechanisms, such as the aforementioned photovoltaic module data, energy storage module data, inverter module data, and IoT device data. Some key data, such as power data, SOC, SOH, operating status, and alarm information, require real-time interaction with the platform. Timed reporting mechanisms affect data display, charging and discharging control, and energy dispatching on the cloud platform and the application (APP), inevitably impacting user experience. While a change-based reporting mechanism could improve the real-time performance of data interaction for balcony photovoltaic systems, the cloud platform would need to handle massive amounts of redundant data. As more devices are deployed, the increased data interaction costs on the cloud platform will inevitably lead to processing pressure and maintenance costs. When the cloud platform cannot handle the workload, it will further affect the real-time performance of data interaction on the APP, also impacting user experience. Furthermore, the data acquisition, processing, and communication reporting modules of energy storage devices are typically tightly coupled. Modification or expansion of any module may affect the communication logic, resulting in poor system maintainability and scalability. The software modules are highly coupled, and any modification to new requirements involves multiple changes such as data acquisition, calculation logic, and packet assembly, affecting the stability of the software version. Summary of the Invention

[0004] To address or improve the technical problems of excessive redundant data in energy storage devices and poor system maintainability and scalability, one objective of this invention is to provide a communication method for energy storage devices.

[0005] Another object of the present invention is to provide a communication system for energy storage devices.

[0006] Another object of the present invention is to provide a communication system for energy storage devices.

[0007] Another object of the present invention is to provide a readable storage medium.

[0008] To achieve the above objectives, the first aspect of the present invention provides a communication method for energy storage devices, comprising: collecting and processing interactive data of the energy storage device through a data generation module, and dividing the interactive data into key data with change reporting attributes and general data with frequency reporting attributes; constructing a globally accessible structured data storage area as a data pool in the device memory through a data pool module; when the data pool receives key data and general data pushed from the data generation module, when the key data changes, triggering a packet reporting logic in real time, and when the general data changes, uniformly packetizing and reporting the changed general data in the data pool after a predetermined time.

[0009] This invention aims to provide a communication method for energy storage devices. First, a data generation module collects and processes the interaction data of the energy storage devices, dividing the interaction data into critical data with change-reporting attributes and general data with frequency-reporting attributes. Then, a data pool module constructs a globally accessible structured data storage area in the device's memory as a data pool. When the data pool receives critical and general data pushed from the data generation module, changes in critical data trigger real-time packet reporting logic, reporting the critical data to the cloud platform. Changes in general data are reported in packets within a predetermined time after which the changed general data in the data pool is uniformly packetized and reported. Based on a change reporting mechanism, data is reported to the platform immediately when it changes, improving real-time response. When general data changes, the changed general data in the data pool is packaged and reported uniformly after a predetermined time, which reduces redundant data reporting and communication pressure. The data pool achieves internal decoupling of the system, decoupling and isolating the data generation module and the communication package reporting module. Change reporting and timed change reporting are driven by the data pool, which in turn drives package reporting, greatly reducing network communication volume and lowering device power consumption. The data pool acts as a central hub, making the acquisition, calculation, and reporting modules independent of each other, which facilitates functional expansion, modification, and debugging.

[0010] In some technical solutions, optionally, when triggering the group packet reporting, the data pool uses a hash table to look up the cloud platform measurement point change or name corresponding to the changed data measurement point.

[0011] It should be noted that hash tables are used to represent mapping relationships.

[0012] In this technical solution, when packet reporting is triggered, the data pool uses a hash table to look up the cloud platform measurement point change or name corresponding to the changed data measurement point. Internally, while maintaining data mapping relationships, the data pool also supports hash lookups. When packet reporting is triggered, the hash table quickly looks up the cloud platform measurement point change or name corresponding to the changed data measurement point, achieving rapid packet assembly and message serialization. Specifically, general data includes a first data key and data value on the data pool side. The data pool contains a first mapping table, which contains the mapping relationship between the first data key on the data pool side and the second data key on the cloud platform side. In response to triggering the data pool timing, based on the first data key of the changed general data in the data pool, the first mapping table is looked up to obtain the second data key. Then, the second data key and data value are sent to the cloud platform, thereby significantly improving reporting efficiency, reducing processing latency, and enhancing the determinism and reliability of the communication process.

[0013] In some technical solutions, optionally, after a predetermined time, the general data that has changed in the data pool is packaged and reported in a unified manner, including: setting a timer, and when the timer expires, scanning all measurement points of general data in the data pool; adding the measurement points that have changed data to the reporting data packet for package reporting; and after successful reporting, clearing the change flag bits of all reported measurement points to zero.

[0014] In this technical solution, after a predetermined time, all general data that has changed in the data pool is packaged and reported. Specifically, a timer is first set. When the timer expires, all measurement points of general data in the data pool are scanned, and then the measurement points whose data has changed are added to the reporting data packet for packaging and reporting. After successful reporting, the change flag bits of all reported measurement points are cleared to zero. Specifically, once the second type of data in the data pool changes, the flag bit of the general data is set. In response to triggering the data pool timing, the general data with the flag bit set in the data pool is reported to the cloud platform, and the flag bits of the general data already reported in the data pool are reset. This mechanism is suitable for data that changes slowly and does not require extreme real-time performance, such as temperature and light intensity, minimizing the number of reports while ensuring data validity.

[0015] In some technical solutions, optionally, the data pool maintains the data, names, and attribute information of all measurement points and provides a unified data push and setting interface.

[0016] In this technical solution, the data pool module maintains information such as data, names, and attributes for all measurement points, and provides a unified data push and setting interface. The data generation module only needs to push data to the target measurement points and does not need to concern itself with the package details. Specifically, the data pool provides a set of standardized and well-defined application programming interfaces. All other modules, such as data producers and data consumers, must interact with the data pool through this set of interfaces, thereby achieving decoupling between modules, improving maintainability and scalability, and ensuring data consistency and reliability.

[0017] In some technical solutions, the key data may optionally include one or a combination of the following: battery power, inverter power, SOC, and operating status.

[0018] In this technical solution, key data can include battery power, inverter power, SOC (State of Charge), and operating status. These data are the core parameters for real-time control, safety protection, and optimized operation of the energy storage system. Battery power, the charging and discharging power, directly determines the amount of energy interaction between the system and the grid, and is the core of power control. Inverter power is the output / input power on the AC side of the inverter, and is crucial for grid connection control. SOC is the remaining battery capacity, the lifeline for energy management and preventing overcharging and over-discharging. Operating status refers to the device's operating mode, such as charging / discharging, standby, or fault, and is the basis for system logic control and state switching. Defining these parameters as key data means that any changes must be reported immediately. This allows the cloud or master station system to instantly detect sudden power fluctuations, SOC critical points, or abnormal device states (such as fault tripping), providing crucial time for quickly executing protection commands (such as emergency shutdown) or adjusting control strategies, directly impacting system safety and grid stability.

[0019] In some technical solutions, the general data may optionally include one or a combination of the following: device name, hardware and software version information, light intensity, and temperature.

[0020] In this technical solution, typical data includes equipment name, hardware / software version information, illumination, and temperature. These are parameters that change slowly and are used for system maintenance, environmental monitoring, and data analysis. Equipment name and version information are static identity and configuration data used for equipment management, asset management, and fault diagnosis. Illumination and temperature are slowly changing environmental parameters used to analyze power generation performance and assess the equipment's operating environment. Because these data are updated infrequently, a timed batch reporting mechanism can compress changes from dozens or even hundreds of measuring points into a few data packets, significantly reducing redundant data transmission.

[0021] In some technical solutions, the interactive data may optionally include one or a combination of the following: photovoltaic module data, energy storage module data, inverter module data, and IoT smart accessory data.

[0022] In this technical solution, the interactive data includes photovoltaic module data, energy storage module data, inverter module data, and IoT smart accessory data. Power generation data from photovoltaic arrays, energy storage data from battery systems, power conversion data from inverters, and IoT data from smart meters, environmental monitoring instruments, etc., can all be uniformly collected, classified, and reported.

[0023] A second aspect of the present invention provides a communication system for an energy storage device, comprising: an acquisition module, configured to acquire and process interactive data of the energy storage device through a data generation module, and divide the interactive data into key data with change reporting attributes and general data with frequency reporting attributes; a construction module, configured to construct a globally accessible structured data storage area as a data pool in the device memory through a data pool module; and a reporting module, configured to, when the data pool receives key data and general data pushed from the data generation module, trigger packet reporting logic in real time when the key data changes, and when the general data changes, uniformly packetize and report the changed general data in the data pool after a predetermined time.

[0024] This invention aims to provide a communication system for energy storage devices, including an acquisition module, a construction module, and a reporting module. The acquisition module collects and processes interactive data from the energy storage device through a data generation module, dividing the interactive data into critical data with changing reporting attributes and general data with frequency reporting attributes. The construction module constructs a globally accessible structured data storage area as a data pool in the device's memory through a data pool module. The reporting module, when the data pool receives critical and general data pushed from the data generation module, triggers packet reporting logic in real time when critical data changes, and after a predetermined time, packages and reports the changed general data in the data pool. Based on a change reporting mechanism, data is reported to the platform immediately when it changes, improving real-time response. When general data changes, the changed general data in the data pool is packaged and reported uniformly after a predetermined time, which reduces redundant data reporting and communication pressure. The data pool achieves internal decoupling of the system, decoupling and isolating the data generation module and the communication package reporting module. Change reporting and timed change reporting are driven by the data pool, which in turn drives package reporting, greatly reducing network communication volume and lowering device power consumption. The data pool acts as a central hub, making the acquisition, calculation, and reporting modules independent of each other, which facilitates functional expansion, modification, and debugging.

[0025] A third aspect of the present invention provides an energy storage device communication system, comprising: a memory and a processor, wherein the memory stores a program or instructions executable on the processor, and the processor executes the program or instructions to implement the steps of the energy storage device communication method in any of the above-described technical solutions. The energy storage device communication system possesses the beneficial effects of any of the above-described technical solutions, which will not be elaborated further here.

[0026] A fourth aspect of the present invention provides a readable storage medium storing a program or instructions, which, when executed by a processor, implement the steps of the energy storage device communication method described in any of the above-described technical solutions. The readable storage medium possesses the beneficial effects of any of the above-described technical solutions, which will not be elaborated further here.

[0027] Additional aspects and advantages of the technical solutions of the present invention will become apparent in the following description or may be learned by practice of the invention. Attached Figure Description

[0028] Figure 1 A flowchart illustrating the steps of an energy storage device communication method according to an embodiment of the present invention is shown.

[0029] Figure 2 A flowchart illustrating the steps of a communication method for an energy storage device according to another embodiment of the present invention is shown;

[0030] Figure 3 A flowchart illustrating the steps of an energy storage device communication method according to an embodiment of the present invention is shown.

[0031] Figure 4 A schematic block diagram of a communication system for an energy storage device according to an embodiment of the present invention is shown;

[0032] Figure 5 A schematic block diagram of a communication system for an energy storage device according to an embodiment of the present invention is shown.

[0033] Figure label:

[0034] 10: Energy storage device communication system; 110: Acquisition module; 120: Construction module; 130: Reporting module; 20: Energy storage device communication system; 300: Memory; 400: Processor. Detailed Implementation

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

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

[0037] Energy storage device data is reported to the cloud platform via network and MQTT protocols. The data exchanged includes various types of data, such as photovoltaic module data (voltage, current, power, energy, etc.), energy storage module data (voltage, current, power, energy, SOC, SOH, etc.), inverter module data, and IoT smart accessory data.

[0038] In existing technologies, data reporting by devices often employs a simple timed reporting mechanism, meaning data is sent to the cloud platform at fixed intervals regardless of changes. This approach has the following drawbacks: Existing energy storage devices commonly use timed reporting mechanisms, such as the aforementioned photovoltaic module data, energy storage module data, inverter module data, and IoT device data. Some key data, such as power data, SOC, SOH, operating status, and alarm information, require real-time interaction with the platform. Timed reporting mechanisms affect data display, charging and discharging control, and energy dispatching on the cloud platform and the APP, inevitably impacting user experience. While a change-based reporting mechanism could improve the real-time performance of data interaction for balcony photovoltaic systems, the cloud platform would need to handle massive amounts of redundant data. As more devices are deployed, the cost of data interaction on the cloud platform increases, inevitably leading to increased processing pressure and maintenance costs. When the cloud platform cannot handle the workload, it further affects the real-time performance of data interaction on the APP, also impacting user experience. Furthermore, the data acquisition, data processing, and communication reporting modules of energy storage devices are typically tightly coupled. Modification or expansion of any module may affect the communication logic, resulting in poor system maintainability and scalability. The software modules are highly coupled, and any modification to new requirements involves multiple changes such as data acquisition, calculation logic, and packet assembly, affecting the stability of the software version.

[0039] This invention aims to provide a communication method and system for energy storage devices, as well as a readable storage medium. It utilizes a change reporting mechanism for packet reporting, instantly reporting data changes to the platform to improve real-time response. When general data changes, the changed general data in the data pool is uniformly packetized and reported after a predetermined time, reducing redundant data reporting and communication pressure. The data pool achieves internal decoupling, isolating the data generation module and the communication packet reporting module. Change reporting and timed change reporting are driven by the data pool, which in turn drives packet reporting, significantly reducing network communication volume and lowering device power consumption. The data pool acts as a central hub, making the acquisition, calculation, and reporting modules independent and facilitating functional expansion, modification, and debugging.

[0040] The following reference Figures 1 to 5 This invention describes a communication method and system for energy storage devices, and a readable storage medium, according to some embodiments of the present invention.

[0041] In one embodiment of the present invention, such as Figure 1 As shown, the communication methods for energy storage devices include:

[0042] S102: Collect and process the interaction data of the energy storage device through the data generation module, and divide the interaction data into key data of change reporting attributes and general data of frequency reporting attributes;

[0043] S104: Construct a globally accessible structured data storage area as a data pool in the device memory through the data pool module;

[0044] S106: When the data pool receives key data and general data pushed from the data generation module, if the key data changes, the grouping and reporting logic is triggered in real time. If the general data changes, the changed general data in the data pool will be grouped and reported uniformly after a predetermined time.

[0045] This embodiment aims to provide a communication method for energy storage devices. First, a data generation module collects and processes the interaction data of the energy storage devices, dividing the interaction data into critical data with change-reporting attributes and general data with frequency-reporting attributes. Then, a data pool module constructs a globally accessible structured data storage area as a data pool in the device's memory. When the data pool receives critical and general data pushed from the data generation module, if the critical data changes, a packet reporting logic is triggered in real time to report the critical data to the cloud platform. If the general data changes, the changed general data in the data pool is packetized and reported uniformly after a predetermined time. Based on a change reporting mechanism, data is reported to the platform immediately when it changes, improving real-time response. When general data changes, the changed general data in the data pool is packaged and reported uniformly after a predetermined time, which reduces redundant data reporting and communication pressure. The data pool achieves internal decoupling of the system, decoupling and isolating the data generation module and the communication package reporting module. Change reporting and timed change reporting are driven by the data pool, which in turn drives package reporting, greatly reducing network communication volume and lowering device power consumption. The data pool acts as a central hub, making the acquisition, calculation, and reporting modules independent of each other, which facilitates functional expansion, modification, and debugging.

[0046] Among them, the energy storage device can be a balcony photovoltaic energy storage device.

[0047] Specifically, the interactive data content is categorized by attributes. Key data such as battery power, inverter power, SOC, and operating status are classified as change reporting attributes. When a device detects changes in these data, it assembles and reports them based on the change reporting mechanism, immediately reporting to the platform upon data change, thus improving real-time response. General data such as device name, hardware / software version information, illumination, and temperature are classified as frequency reporting attributes. When a device detects changes in these data, it does not report them immediately but waits for a timeout before reporting them all at once. This timed + change reporting mechanism reduces communication load. Furthermore, a data pool is used to decouple the system internally, isolating the data generation module and the communication packet reporting module. The data pool drives change reporting and timed + change reporting, which in turn drives packet reporting, significantly reducing network communication volume and lowering device power consumption.

[0048] In some embodiments, optionally, such as Figure 2 As shown, the communication method for energy storage devices also includes:

[0049] S202: When triggering the group packet reporting, the data pool uses a hash table to look up the cloud platform measurement point change or name corresponding to the changed data measurement point.

[0050] It should be noted that hash tables are used to represent mapping relationships.

[0051] In this embodiment, when packet reporting is triggered, the data pool uses a hash table to look up the cloud platform measurement point change or name corresponding to the changed data measurement point. Internally, while maintaining data mapping relationships, the data pool supports hash lookups. When packet reporting is triggered, the hash table quickly looks up the cloud platform measurement point change or name corresponding to the changed data measurement point, achieving rapid packet assembly and message serialization. Specifically, general data includes a first data key and a data value on the data pool side. The data pool contains a first correspondence table, which contains the correspondence between the first data key on the data pool side and the second data key on the cloud platform side. In response to triggering the data pool timing, based on the first data key of the changed general data in the data pool, the first correspondence table is looked up to obtain the second data key. Then, the second data key and data value are sent to the cloud platform, thereby significantly improving reporting efficiency, reducing processing latency, and enhancing the determinism and reliability of the communication process.

[0052] In some embodiments, optionally, such as Figure 3 As shown, when general data changes, the changed general data in the data pool will be packaged and reported together after a predetermined time, including:

[0053] S302: Set a timer. When the timer expires, scan all general data measurement points in the data pool.

[0054] S304: Add the measurement points whose data has changed to the reporting data packet for packet assembly and reporting;

[0055] S306: After successful reporting, clear the change flags of all reported measurement points to zero.

[0056] In this embodiment, after a predetermined time, all general data that has changed in the data pool is packaged and reported. Specifically, a timer is first set. When the timer expires, all measurement points of general data in the data pool are scanned, and then the measurement points whose data has changed are added to the reporting data packet for packaging and reporting. After successful reporting, the change flag bits of all reported measurement points are cleared to zero. It can be understood that once the second type of data in the data pool changes, the flag bits of the general data are set. In response to triggering the data pool timing, the general data with flag bits set in the data pool is reported to the cloud platform, and the flag bits of the general data already reported in the data pool are reset. This mechanism is suitable for data that changes slowly and does not require extreme real-time performance, such as temperature and light intensity, minimizing the number of reports while ensuring data validity.

[0057] Optionally, in some embodiments, the data pool module maintains information such as data, names, and attributes of all measurement points, and provides a unified data push interface and setting interface. The data generation module only needs to push data to the target measurement points and does not need to concern itself with the package details. Specifically, the data pool provides a set of standardized, well-defined application programming interfaces. All other modules, such as data producers and data consumers, must interact with the data pool through this set of interfaces, thereby achieving decoupling between modules, improving maintainability and scalability, and ensuring data consistency and reliability.

[0058] Specifically, the data pool is a globally accessible structured data storage area built in the device's memory. It serves as the data exchange hub between various modules within the system, acting as middleware to decouple the data generation and data packaging modules. The data generation module focuses solely on data collection, processing, and pushing to the data pool, which then triggers the data change reporting and timed change reporting packaging logic. The data pool module maintains information such as data, names, and attributes for all measurement points, providing a unified data push and setting interface. The data generation module only needs to push data to the target measurement points and does not need to concern itself with packaging details.

[0059] In some embodiments, the key data may optionally include battery power, inverter power, SOC (State of Charge), and operating status. These data are the core parameters for real-time control, safety protection, and optimized operation of the energy storage system. Battery power is the charging and discharging power, which directly determines the amount of energy interaction between the system and the grid and is the core of power control. Inverter power is the output / input power on the AC side of the inverter and is crucial for grid connection control. SOC is the remaining battery charge and is the lifeline for energy management and preventing overcharging and over-discharging. Operating status refers to the device's operating mode, such as charging / discharging, standby, or fault, and is the basis for system logic control and state switching. Defining these parameters as key data means that any changes in them must be reported immediately. This allows the cloud or master station system to instantly detect sudden power fluctuations, SOC critical points, or abnormal device states (such as fault tripping), providing golden time for quickly executing protection commands (such as emergency shutdown) or adjusting control strategies, directly impacting system safety and grid stability.

[0060] In some embodiments, the general data may optionally include device name, hardware / software version information, illumination, and temperature. These data are slowly changing parameters used for system maintenance, environmental monitoring, and data analysis. Device name and version information are static identity and configuration data used for device management, asset management, and fault diagnosis. Illumination and temperature are slowly changing environmental parameters used to analyze power generation performance and assess the equipment's operating environment. Because these data are updated infrequently, a timed batch reporting mechanism can compress changes from dozens or hundreds of measuring points into a few data packets, significantly reducing redundant data transmission.

[0061] In some embodiments, the interactive data may optionally include photovoltaic module data, energy storage module data, inverter module data, and IoT smart accessory data. Power generation data from photovoltaic arrays, energy storage data from battery systems, converter data from inverters, and IoT data from smart meters, environmental monitoring instruments, etc., can all be uniformly collected, classified, and reported.

[0062] In one embodiment of the present invention, a communication system 10 for an energy storage device is also provided. For example... Figure 4 As shown, Figure 4 A structural block diagram of an energy storage device communication system 10 according to an embodiment of the present invention is shown. Specifically, the energy storage device communication system 10 may include the following: an acquisition module 110, a construction module 120, and a reporting module 130.

[0063] The acquisition module 110 is used to collect and process the interaction data of the energy storage device through the data generation module, and divide the interaction data into key data of change reporting attributes and general data of frequency reporting attributes.

[0064] The construction module 120 is used to build a globally accessible structured data storage area as a data pool in the device memory through the data pool module;

[0065] The reporting module 130 is used to trigger the package reporting logic in real time when the key data changes when the data pool receives key data and general data pushed by the data generation module, and to package and report the general data that has changed in the data pool after a predetermined time when the general data changes.

[0066] The energy storage device communication system 10 provided in this embodiment of the invention includes an acquisition module 110, a construction module 120, and a reporting module 130. The acquisition module 110 collects and processes interactive data from the energy storage device through a data generation module, dividing the interactive data into key data with change reporting attributes and general data with frequency reporting attributes. The construction module 120 constructs a globally accessible structured data storage area as a data pool in the device's memory through a data pool module. The reporting module 130, when the data pool receives key data and general data pushed from the data generation module, triggers a packet reporting logic in real time when the key data changes, and after a predetermined time, uniformly packets and reports the changed general data in the data pool when the general data changes. Based on a change reporting mechanism, data is reported to the platform immediately when it changes, improving real-time response. When general data changes, the changed general data in the data pool is packaged and reported uniformly after a predetermined time, which reduces redundant data reporting and communication pressure. The data pool achieves internal decoupling of the system, decoupling and isolating the data generation module and the communication package reporting module. Change reporting and timed change reporting are driven by the data pool, which in turn drives package reporting, greatly reducing network communication volume and lowering device power consumption. The data pool acts as a central hub, making the acquisition, calculation, and reporting modules independent of each other, which facilitates functional expansion, modification, and debugging.

[0067] In one embodiment of the present invention, an energy storage device communication system 20 is also proposed. For example... Figure 5 As shown, Figure 5 A structural block diagram of an energy storage device communication system 20 provided in an embodiment of the present invention is shown. The energy storage device communication system 20 includes:

[0068] Memory 300, on which programs or instructions are stored;

[0069] The processor 400 executes the above-described program or instructions to implement the steps of the energy storage device communication method as described in any of the above embodiments.

[0070] The energy storage device communication system 20 provided in this embodiment includes a memory 300 and a processor 400. When the program or instructions in the memory 300 are executed by the processor 400, they implement the steps of the energy storage device communication method as described in any of the above embodiments. Therefore, the energy storage device communication system 20 has all the beneficial effects of the energy storage device communication method in any of the above embodiments, which will not be repeated here.

[0071] Specifically, the memory 300 and the processor 400 can be connected via a bus or other means. The processor 400 may include one or more processing units, such as a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or a field-programmable gate array (FPGA).

[0072] In one embodiment of the present invention, a readable storage medium is also provided. A program or instructions are stored thereon, which, when executed by a processor, implement the steps of the energy storage device communication method as described in any of the above embodiments.

[0073] The readable storage medium provided in this embodiment of the invention, when its stored program or instructions are executed by a processor, can implement the steps of the energy storage device communication method as described in any of the above embodiments. Therefore, the readable storage medium possesses all the beneficial effects of the energy storage device communication method in any of the above embodiments, which will not be elaborated further here.

[0074] Specifically, the aforementioned readable storage media can include any medium capable of storing or transmitting information. Examples of readable storage media include electronic circuits, semiconductor memory devices, read-only memory (ROM), random access memory (RAM), compact disc read-only memory (CD-ROM), flash memory, erasable ROM (EROM), magnetic tape, floppy disk, optical disk, hard disk, fiber optic media, radio frequency (RF) links, optical data storage devices, etc. Code segments can be downloaded via computer networks such as the Internet and intranets.

[0075] According to a specific embodiment of the present invention, the energy storage device communication method combines several modules such as change reporting, timed change reporting, and data pooling. Based on the application scenario of balcony photovoltaic equipment, key data is classified and reported according to a specific mechanism. The specific technical solution is as follows:

[0076] Data pool module:

[0077] The data pool is a globally accessible structured data storage area built in the device's memory. It serves as the data exchange hub between various modules within the system. As middleware, the data pool decouples the data generation and data packaging modules. The data generation module focuses only on data collection, processing, and then pushing the data to the data pool. The data pool then uniformly triggers the data change reporting and timed change reporting packaging logic.

[0078] The data pool module maintains information such as data, name, and attributes of all measurement points and provides a unified data push and setting interface. The data generation module only needs to push data to the target measurement points and does not need to pay attention to the package details.

[0079] Change reporting, scheduled change reporting:

[0080] The data pool module implements change reporting and timed change reporting functions. The data pool receives data pushes from other modules. When the data of the change reporting attribute measurement point changes, the group package reporting logic module is directly triggered.

[0081] Additionally, the reporting logic module maintains a timer. When the timer expires, it scans all measurement points in the data pool with timed reporting and changing attributes, adding those that have changed to the reporting data packet. After successful reporting, the change flags of all reported measurement points are cleared. This mechanism is suitable for data such as temperature and light intensity that change slowly and do not require extreme real-time performance, minimizing the number of reporting attempts while ensuring data validity.

[0082] While maintaining data mapping relationships, the data pool also supports hash lookups. When packet reporting is triggered, the hash table is used to quickly look up the cloud platform measurement point changes or names corresponding to the changed data measurement points, enabling rapid packet assembly and message serialization.

[0083] Example 1: Balcony Photovoltaic Energy Storage System Scenario:

[0084] In a typical balcony photovoltaic energy storage system scenario, there is a total of 12 kWh of energy storage modules (1 main unit (2 kWh) + 5 additional power supply units (5 × 2 kWh), 4 photovoltaic modules, an 800W grid-connected / 1500W off-grid inverter, a smart meter, 3 smart sockets, a meter data acquisition unit, and several loads, etc., representing a fully loaded multi-device application scenario. The implementation process of the solution using this invention is as follows:

[0085] Key data such as energy storage charging and discharging power, photovoltaic power, inverter power, IoT (Internet of Things) communication status and power, and SOC are set as change attribute measurement points; other data are set as frequency reporting attributes; all measurement point data content is initialized and entered into the pool, and each module collects and pushes it to the data pool to complete the packet reporting.

[0086] The cloud platform and APP can display key data in real time, improving user experience; at the same time, they can provide real-time and reliable data for the APP's dynamic electricity prices, energy dispatch, and energy planning strategies.

[0087] Example 2: Small-scale balcony photovoltaic system (simplified configuration scenario):

[0088] This embodiment is applicable to a small-scale photovoltaic system on a residential balcony, containing only basic components such as a single photovoltaic module, a small energy storage unit (e.g., a 1kWh battery), and a simple inverter. The system load is simple, for example, connecting only a smart socket and a few lighting devices. The implementation process is as follows:

[0089] Set photovoltaic power, battery SOC, and inverter operating status as change reporting attributes to ensure real-time performance; set equipment temperature and software / hardware version as timed + change reporting attributes to reduce reporting frequency.

[0090] The data pool module initializes all measurement points. The photovoltaic data acquisition module only needs to push data to the data pool and does not need to pay attention to the data package logic. When the photovoltaic power changes, the data pool immediately triggers a change report; after the timer expires, it scans for slowly changing data such as temperature and reports them uniformly.

[0091] In low-power mode, the amount of communication data is reduced, making it particularly suitable for battery-powered IoT devices and extending their battery life. The cloud platform can display key parameters in real time, improving the user's monitoring experience for small systems.

[0092] Example 3: Commercial building balcony photovoltaic system (multi-device collaborative scenario):

[0093] This embodiment targets a balcony photovoltaic system for commercial buildings (such as office buildings), involving multiple photovoltaic arrays, a large energy storage unit (e.g., 10 kWh), multiple inverters, and integrating smart meters, environmental sensors (e.g., light intensity and humidity sensors), and energy management software. The system needs to handle high-concurrency data and support remote scheduling.

[0094] Set the total photovoltaic power, energy storage SOH, inverter efficiency, and alarm information as change reporting attributes; set the environmental sensor readings and equipment logs as timed + change reporting attributes, and the timed period can be dynamically adjusted according to the network load (e.g., extended from the default 30 seconds to 60 seconds).

[0095] The data pool acts as a central hub, supporting hash lookups for rapid packet assembly. When multiple devices experience simultaneous data changes, the data pool prioritizes reporting critical data to avoid network congestion. The scheduled reporting module processes non-critical data during off-peak hours, reducing communication traffic and significantly alleviating pressure on the cloud platform, while supporting real-time access by multiple users. The decoupled module design facilitates the addition of new sensors or software upgrades without requiring modifications to communication logic, improving system scalability.

[0096] Example 4: Balcony photovoltaic system integrated with smart home (cross-platform interaction scenario):

[0097] This embodiment integrates the balcony photovoltaic system with a smart home platform (such as via Wi-Fi or Zigbee protocol), allowing the photovoltaic equipment to work collaboratively with home appliances (such as smart air conditioners and electric vehicle charging stations) to achieve optimized energy distribution.

[0098] Power generation and SOC are set as change reporting attributes; smart home data (such as charging pile power and air conditioner energy consumption) are also included in the data pool and classified according to real-time requirements—urgent data (such as fault alarms) adopt change reporting, and historical data (such as daily cumulative electricity consumption) adopts timed + change reporting.

[0099] The data pool has been expanded into a cross-platform data exchange interface, decoupling the photovoltaic data acquisition module from the home control module. When photovoltaic power generation is excessive, the data pool triggers a change report, and the cloud platform automatically dispatches energy to charging piles; periodic reports are also submitted to statistically analyze the energy efficiency of home appliances. Communication redundancy is reduced by 50%, device power consumption is lowered, and energy utilization is improved. Users can view the real-time linkage status of photovoltaic and home appliances through an app, enhancing the user experience.

[0100] Beneficial effects:

[0101] 1. Significantly reduces communication traffic and device power consumption: By reducing redundant data reporting, network bandwidth is saved, and the number of activations and duration of Wi-Fi modules are greatly reduced, making it particularly suitable for battery-powered IoT devices; at least 30% of redundant communication data is reduced.

[0102] 2. Module decoupling improves system maintainability: The data pool serves as the central hub, making the acquisition, calculation, and reporting modules independent of each other, which facilitates the expansion, modification, and debugging of functions.

[0103] 3. Flexible and configurable: Supports configuring different reporting strategies for data points with different characteristics, taking into account both real-time and low power consumption requirements.

[0104] 4. High reporting efficiency: The package assembly process utilizes hash lookup, which is highly efficient and has a fast response. The design of "pushing the data pool triggers reporting" makes the entire process seamless.

[0105] In this invention, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance; the term "multiple" refers to two or more unless otherwise explicitly defined. The terms "install," "connect," "link," and "fix" should be interpreted broadly. For example, "connect" can be a fixed connection, a detachable connection, or an integral connection; "link" can be a direct connection or an indirect connection through an intermediate medium. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0106] In the description of this invention, it should be understood that the terms "upper," "lower," "left," "right," "front," "rear," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or unit referred to must have a specific orientation or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention.

[0107] In the description of this specification, the terms "one embodiment," "some embodiments," "specific embodiment," etc., refer to a specific feature, structure, material, or characteristic described in connection with that embodiment or example, which is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0108] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A communication method for an energy storage device, characterized in that, include: The data generation module collects and processes the interaction data of the energy storage device, and divides the interaction data into key data of change reporting attributes and general data of frequency reporting attributes. The data pool module constructs a globally accessible structured data storage area in the device's memory as a data pool. When the data pool receives key data and general data pushed by the data generation module, if the key data changes, the packet reporting logic is triggered in real time. If the general data changes, the changed general data in the data pool is packetized and reported uniformly after a predetermined time.

2. The communication method for energy storage devices according to claim 1, characterized in that, Also includes: When a group packet is triggered to report, the data pool uses a hash table to look up the cloud platform measurement point change or name corresponding to the changed data measurement point.

3. The communication method for energy storage devices according to claim 1, characterized in that, When the general data changes, the changed general data in the data pool will be packaged and reported together after a predetermined time, including: Set a timer, and when the timer expires, scan all measurement points of general data in the data pool; Add the measurement points whose data has changed to the reporting data packet for packet assembly and reporting; After successful reporting, clear the change flags of all reported measurement points to zero.

4. The communication method for energy storage devices according to claim 1, characterized in that, The data pool maintains the data, names, and attribute information of all measurement points and provides a unified data push and setting interface.

5. The communication method for an energy storage device according to any one of claims 1 to 4, characterized in that, The key data includes one or a combination of the following: battery power, inverter power, SOC, and operating status.

6. The communication method for an energy storage device according to any one of claims 1 to 4, characterized in that, The general data includes one or a combination of the following: device name, software and hardware version information, light intensity, and temperature.

7. The communication method for an energy storage device according to any one of claims 1 to 4, characterized in that, The interactive data includes one or a combination of the following: photovoltaic module data, energy storage module data, inverter module data, and IoT smart accessory data.

8. A communication system for an energy storage device, characterized in that, include: The acquisition module is used to collect and process the interaction data of the energy storage device through the data generation module, and divide the interaction data into key data of change reporting attributes and general data of frequency reporting attributes. The building module is used to construct a globally accessible structured data storage area as a data pool in the device memory through the data pool module; The reporting module is used to trigger the packet reporting logic in real time when the key data changes, and to uniformly packetize and report the changed general data in the data pool after a predetermined time when the key data changes, and when the general data changes.

9. A communication system for an energy storage device, characterized in that, include: A memory and a processor, wherein the memory stores a program or instructions executable on the processor, and the processor, when executing the program or instructions, implements the steps of the energy storage device communication method as described in any one of claims 1 to 7.

10. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or the instructions are executed by the processor, they implement the steps of the energy storage device communication method as described in any one of claims 1 to 7.

Images