OTA remote upgrading system and method for energy storage system

Abstract

The invention discloses an OTA remote upgrading system and method for an energy storage system, belongs to the technical field of air upgrading of the energy storage system, and realizes non-sensitivity of an upgrading process and intelligent scheduling based on a load rate and an importance coefficient by integrating non-inductive upgrading, communication redundancy and edge calculation to avoid system overload and service interruption. The communication redundancy ensures that key data are not lost during upgrading, and the system reliability is improved; the data transmission quantity is reduced by differential upgrading and breakpoint resuming, and the upgrading efficiency is improved; and a whole-process security mechanism and version rollback guarantee the stability and security of the system.

Description

Technical Field

[0001] This invention belongs to the field of over-the-air (OTA) upgrade technology for energy storage systems, specifically relating to an OTA remote upgrade system and method for energy storage systems. Background Technology

[0002] With the rapid development of renewable energy, energy storage systems play a crucial role in microgrids and smart grids, balancing loads, improving energy efficiency, and ensuring system stability. Energy storage systems typically include an Energy Management System (EMS), a Power Conversion System (PCS), and a Battery Management System (BMS). These subsystems require firmware upgrades to fix vulnerabilities, optimize performance, or add new features. Traditional upgrade methods often require downtime, leading to system interruptions and impacting critical business operations. In existing technologies, Firmware Over-The-Air (FOTA) upgrades have been applied to energy storage systems. For example, CN120104156A discloses a seamless upgrade method for energy storage systems. This method obtains the energy storage load rate uploaded by the first energy storage system among multiple energy storage systems. Based on the first energy storage system's energy storage load rate and a preset importance coefficient, it determines the upgrade order of the first energy storage system and sends upgrade packages to it at the target download rate, enabling the first energy storage system to complete a seamless upgrade when the version switching conditions are met. However, the patent lacks consideration of factors such as the operating time and failure rate of the energy storage system when determining the upgrade sequence, resulting in insufficient rationality of the upgrade sequence.

[0003] CN114661316A discloses a method and system for upgrading software on an energy storage device. The method includes establishing a connection between the energy storage device and an OTA service platform and performing security verification. The OTA service platform interacts with a TSP platform to obtain the firmware version information of the energy storage device and performs information matching. Upon successful matching, a software upgrade package is generated and sent to the energy storage device. The energy storage device downloads the software upgrade package and determines whether to execute the software update based on the upgrade command. However, this patent lacks a mechanism for handling system anomalies during the software update process, resulting in insufficient reliability. Furthermore, challenges such as communication link failures, low upgrade package transmission efficiency, and data security issues may arise during the upgrade process.

[0004] In summary, existing firmware over-the-air (OTA) download technologies have the following shortcomings:

[0005] The upgrade order and timing lack intelligence and cannot be dynamically adjusted according to the real-time load status of the system, which can easily cause system overload or network congestion during high-load periods.

[0006] Insufficient communication link redundancy means that when the link between EMS and BMS or PCS is interrupted, the system cannot maintain critical data communication, which may lead to upgrade failure or system control failure.

[0007] Upgrade packages have low transmission efficiency, large upgrade packages consume a lot of bandwidth, and need to be retransmitted when the network is interrupted, which prolongs the upgrade time.

[0008] Inadequate security mechanisms mean that upgrade packages may be tampered with or accessed without authorization, and the lack of version rollback functionality affects system reliability. Summary of the Invention

[0009] To address the shortcomings of the existing technology, this application provides an OTA remote upgrade system and method for energy storage systems.

[0010] In the first aspect, this application proposes an OTA remote upgrade system for energy storage systems, including an FOTA platform for managing the upgrade process, including upgrade order decision-making, upgrade package delivery rate adjustment and parallel upgrade control.

[0011] Multiple energy storage systems, each including an energy management system, a power conversion system, and a battery management system, are connected by three communication links: the energy management system and the power conversion system form a first communication link, the energy management system and the battery management system form a second communication link, and the power conversion system and the battery management system form a third communication link;

[0012] The edge computing energy management unit is deployed in the microgrid system as a local OTA upgrade center, used to store encrypted firmware, process differential upgrade packages, and implement breakpoint resume.

[0013] The power conversion system and the battery management system are each equipped with a data register to store relevant data from other systems in order to achieve communication redundancy.

[0014] The energy storage system is configured to collect its own characteristic information, calculate the energy storage load rate, and upload it to the FOTA platform;

[0015] The FOTA platform is configured to determine the upgrade order based on the energy storage load rate and importance coefficient, and to dynamically adjust the upgrade package delivery rate according to the load rate.

[0016] The edge computing energy management unit is configured to collaborate with the FOTA platform to generate a complete upgrade package and transmit it to the energy storage system for version rollback and upgrade result feedback.

[0017] In some embodiments, the FOTA platform is further configured as follows:

[0018] By multiplying the energy storage load rate of the energy storage system by an importance coefficient, a priority score is obtained. The upgrade order is determined by sorting the scores, with those having lower scores being upgraded first.

[0019] Based on the comparison between the energy storage load rate and the load rate threshold, the target distribution rate of the upgrade package is dynamically adjusted: when the load rate is higher than the threshold, the rate is reduced by the difference and the first adjustment step; when the load rate is not higher than the threshold, the rate is increased by the second adjustment step.

[0020] In some embodiments, the energy storage system is configured as follows:

[0021] By collecting multi-dimensional feature information, including battery status, power fluctuation, environmental status, power consumption status and hardware resources, normalization processing and weighted summation are performed to calculate the energy storage load rate.

[0022] After receiving the upgrade package, the version switch is triggered only when the system is idle.

[0023] In some embodiments, the data register includes:

[0024] The first data register in the power conversion system is used to store relevant data from the battery management system in real time, including battery status, temperature, charge / discharge rate limits, and cycle count.

[0025] The second data register in the battery management system is used to store relevant data of the power conversion system in real time, including operating status, power information, voltage and current, and fault alarms.

[0026] Specifically, when the second communication link is interrupted, the energy management system sends a read request to the power conversion system through the first communication link to obtain the battery management system data in the first data register; when the first communication link is interrupted, the energy management system sends a read request to the battery management system through the second communication link to obtain the power conversion system data in the second data register.

[0027] In some embodiments, the edge computing power management unit is further configured to:

[0028] Using differential upgrade technology, generate differential upgrade packages that contain only version difference data, and then verify and deploy them;

[0029] It supports a breakpoint resume mechanism, which records the progress during the transmission process and resumes the transmission from the breakpoint after the network is interrupted.

[0030] The system performs security authentication, encrypted storage, and decryption verification on upgrade packages, maintains a version list and upgrade history, and supports version rollback.

[0031] Secondly, this application proposes an OTA (Over-The-Air) remote upgrade method for an energy storage system, the method comprising:

[0032] Upgrade preparation phase: The energy storage system collects its own characteristic information, calculates the energy storage load rate and uploads it to the FOTA platform; the FOTA platform determines the upgrade order based on the energy storage load rate and importance coefficient, and dynamically adjusts the upgrade package delivery rate according to the load rate;

[0033] Communication redundancy protection phase: During the upgrade process, when the communication link between the energy management system and the battery management system or power conversion system is interrupted, the energy management system accesses the data register through the backup link to obtain critical data and maintain communication;

[0034] Upgrade execution phase: The edge computing energy management unit receives the upgrade request, generates a differential upgrade package, and transmits it to the energy storage system through a breakpoint resume mechanism; the energy storage system completes the version switch in an idle state;

[0035] Post-upgrade processing stage: The edge computing energy management unit monitors the upgrade results, supports version rollback, and feeds back the results to the cloud or local server.

[0036] In some embodiments, calculating the energy storage load factor during the upgrade preparation phase includes:

[0037] Collect multi-dimensional feature information on battery status, power fluctuation, environmental status, power consumption status, and hardware resources;

[0038] The feature information is normalized and the energy storage load rate is obtained by weighted summation.

[0039] In some embodiments, the communication redundancy protection phase includes:

[0040] When the energy management system fails to communicate with the battery management system, the energy management system sends a read request to the power conversion system, and the power conversion system reports the battery management system data in the first data register to the energy management system.

[0041] When the energy management system fails to communicate with the power conversion system, the energy management system sends a read request to the battery management system, and the battery management system reports the power conversion system data in the second data register to the energy management system.

[0042] The energy management system periodically sends recovery requests to the faulty communication link, and switches back to the original communication link once communication is restored.

[0043] In some embodiments, the upgrade execution phase includes:

[0044] The edge computing power management unit performs security authentication on the upgrade request, and receives the differential upgrade package after successful authentication.

[0045] The edge computing power management unit generates a complete upgrade package based on the differential upgrade package and the current version, and verifies its integrity with the server.

[0046] The energy storage system's bootloader receives the upgrade package, decrypts and verifies it, writes the new version of the software to the storage area, updates the startup configuration, and copies it to the application area after restarting.

[0047] In some embodiments, the post-upgrade processing stage includes:

[0048] The subsystem will feed back the upgrade results to the edge computing energy management unit, which will then upload the results to the cloud or a local server.

[0049] If the upgrade fails, the edge computing energy management unit will trigger a version rollback, restoring to the previous stable version.

[0050] Thirdly, this application proposes an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method described above.

[0051] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described above.

[0052] The beneficial effects of this invention are:

[0053] This solution integrates seamless upgrades, communication redundancy, and edge computing to achieve a seamless upgrade process. Intelligent scheduling based on load rate and importance coefficient avoids system overload and business interruption. Communication redundancy ensures that critical data is not lost during the upgrade, improving system reliability. Differential upgrades and breakpoint resume reduce data transmission volume and improve upgrade efficiency. Full-process security mechanisms and version rollback ensure system stability and security. Attached Figure Description

[0054] Figure 1 This is a system principle block diagram of the present invention.

[0055] Figure 2 This is the overall flowchart of the present invention. Detailed Implementation

[0056] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein; rather, these embodiments are provided so that a more thorough understanding of the invention can be achieved and that the full scope of the invention can be conveyed to those skilled in the art.

[0057] Firstly, this application proposes an OTA (Over-The-Air) remote upgrade system for energy storage systems, such as... Figure 1 As shown, it includes an FOTA platform for managing the upgrade process, including upgrade order decision-making, upgrade package delivery rate adjustment, and parallel upgrade control;

[0058] Multiple energy storage systems, each including an energy management system, a power conversion system, and a battery management system, are connected by three communication links: the energy management system and the power conversion system form a first communication link, the energy management system and the battery management system form a second communication link, and the power conversion system and the battery management system form a third communication link;

[0059] The edge computing energy management unit is deployed in the microgrid system as a local OTA upgrade center, used to store encrypted firmware, process differential upgrade packages, and implement breakpoint resume.

[0060] The power conversion system and the battery management system are each equipped with a data register to store relevant data from other systems in order to achieve communication redundancy.

[0061] The energy storage system is configured to collect its own characteristic information, calculate the energy storage load rate, and upload it to the FOTA platform;

[0062] The FOTA platform is configured to determine the upgrade order based on the energy storage load rate and importance coefficient, and to dynamically adjust the upgrade package delivery rate according to the load rate.

[0063] The edge computing energy management unit is configured to collaborate with the FOTA platform to generate a complete upgrade package and transmit it to the energy storage system for version rollback and upgrade result feedback.

[0064] In some embodiments, the FOTA platform is further configured as follows:

[0065] By multiplying the energy storage load rate of the energy storage system by an importance coefficient, a priority score is obtained. The upgrade order is determined by sorting the scores, with those having lower scores being upgraded first.

[0066] Based on the comparison between the energy storage load rate and the load rate threshold, the target distribution rate of the upgrade package is dynamically adjusted: when the load rate is higher than the threshold, the rate is reduced by the difference and the first adjustment step; when the load rate is not higher than the threshold, the rate is increased by the second adjustment step.

[0067] In some embodiments, the energy storage system is configured as follows:

[0068] By collecting multi-dimensional feature information, including battery status, power fluctuation, environmental status, power consumption status and hardware resources, normalization processing and weighted summation are performed to calculate the energy storage load rate.

[0069] After receiving the upgrade package, the version switch is triggered only when the system is idle.

[0070] In some embodiments, the data register includes:

[0071] The first data register in the power conversion system is used to store relevant data from the battery management system in real time, including battery status, temperature, charge / discharge rate limits, and cycle count.

[0072] The second data register in the battery management system is used to store relevant data of the power conversion system in real time, including operating status, power information, voltage and current, and fault alarms.

[0073] Specifically, when the second communication link is interrupted, the energy management system sends a read request to the power conversion system through the first communication link to obtain the battery management system data in the first data register; when the first communication link is interrupted, the energy management system sends a read request to the battery management system through the second communication link to obtain the power conversion system data in the second data register.

[0074] In some embodiments, the edge computing power management unit is further configured to:

[0075] Using differential upgrade technology, generate differential upgrade packages that contain only version difference data, and then verify and deploy them;

[0076] It supports a breakpoint resume mechanism, which records the progress during the transmission process and resumes the transmission from the breakpoint after the network is interrupted.

[0077] The system performs security authentication, encrypted storage, and decryption verification on upgrade packages, maintains a version list and upgrade history, and supports version rollback.

[0078] Secondly, this application proposes an OTA (Over-The-Air) remote upgrade method for energy storage systems, such as... Figure 2 As shown, the method includes:

[0079] S100: Upgrade preparation phase: The energy storage system collects its own characteristic information, calculates the energy storage load rate and uploads it to the FOTA platform; the FOTA platform determines the upgrade order based on the energy storage load rate and importance coefficient, and dynamically adjusts the upgrade package delivery rate according to the load rate;

[0080] S200: Communication Redundancy Guarantee Phase: During the upgrade process, when the communication link between the energy management system and the battery management system or power conversion system is interrupted, the energy management system accesses the data register through the backup link to obtain critical data and maintain communication.

[0081] S300: Upgrade Execution Phase: The edge computing energy management unit receives the upgrade request, generates a differential upgrade package, and transmits it to the energy storage system through the breakpoint resume mechanism; the energy storage system completes the version switch in the idle state.

[0082] S400: Post-upgrade processing stage: The edge computing energy management unit monitors the upgrade results, supports version rollback, and feeds back the results to the cloud or local server.

[0083] In some embodiments, calculating the energy storage load factor during the upgrade preparation phase includes:

[0084] Collect multi-dimensional feature information on battery status, power fluctuation, environmental status, power consumption status, and hardware resources;

[0085] The feature information is normalized and the energy storage load rate is obtained by weighted summation.

[0086] In some embodiments, the communication redundancy protection phase includes:

[0087] When the energy management system fails to communicate with the battery management system, the energy management system sends a read request to the power conversion system, and the power conversion system reports the battery management system data in the first data register to the energy management system.

[0088] When the energy management system fails to communicate with the power conversion system, the energy management system sends a read request to the battery management system, and the battery management system reports the power conversion system data in the second data register to the energy management system.

[0089] The energy management system periodically sends recovery requests to the faulty communication link, and switches back to the original communication link once communication is restored.

[0090] In some embodiments, the upgrade execution phase includes:

[0091] The edge computing power management unit performs security authentication on the upgrade request, and receives the differential upgrade package after successful authentication.

[0092] The edge computing power management unit generates a complete upgrade package based on the differential upgrade package and the current version, and verifies its integrity with the server.

[0093] The energy storage system's bootloader receives the upgrade package, decrypts and verifies it, writes the new version of the software to the storage area, updates the startup configuration, and copies it to the application area after restarting.

[0094] In some embodiments, the post-upgrade processing stage includes:

[0095] The subsystem will feed back the upgrade results to the edge computing energy management unit, which will then upload the results to the cloud or a local server.

[0096] If the upgrade fails, the edge computing energy management unit will trigger a version rollback, restoring to the previous stable version.

[0097] Thirdly, this application proposes an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method described above.

[0098] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described above.

[0099] The upgrade process of this solution is divided into four stages: upgrade preparation, communication redundancy assurance, upgrade execution, and post-upgrade processing.

[0100] Upgrade preparation phase:

[0101] The energy storage system collects its own characteristic information in real time, including battery status (e.g., charge and health), power fluctuations (e.g., output power changes), environmental status (e.g., temperature and humidity), power consumption status (e.g., energy consumption level), and hardware resources (e.g., CPU utilization). This information is normalized and weighted to calculate the energy storage load rate. The weights are set according to the system configuration, such as a battery status weight of 0.3 and a power fluctuation weight of 0.2.

[0102] The energy storage system uploads its load factor to the FOTA (Firmware Over-The-Air) platform. The FOTA platform presets an importance coefficient for each system. Based on the system's role in the microgrid, systems supplying critical loads have a higher coefficient; the load factor is multiplied by the importance coefficient to obtain a priority score. Systems are then sorted by their scores to determine the upgrade order. For example, important systems with low load factors are upgraded first to avoid business disruption.

[0103] The FOTA platform dynamically adjusts the upgrade package delivery rate based on load factor: A load factor threshold is set; if the load factor exceeds the threshold, the rate is reduced by the difference (load factor - threshold) and a first adjustment step (e.g., a decrease of 10kbps per second); if the load factor is not higher than the threshold, the rate is increased by a second adjustment step (e.g., an increase of 5kbps per second). Simultaneously, the FOTA platform controls the number of parallel upgrades to avoid resource conflicts.

[0104] Communication redundancy guarantee phase:

[0105] During the upgrade process, if the second communication link is interrupted, the energy management system detects the fault and sends a read request to the power conversion system via the first communication link. The power conversion system retrieves data from the battery management system in the first data register, converts it into a format recognizable by the energy management system, and then reports it. Similarly, if the first communication link is interrupted, the energy management system sends a read request to the battery management system via the second communication link, and the battery management system retrieves data from the power conversion system in the second data register and reports it.

[0106] The energy management system periodically sends heartbeat packets to test the faulty link. Once it receives a successful response N times consecutively (e.g., 3 times), the energy management system automatically switches back to the original communication link and stops accessing the data register.

[0107] Upgrade Execution Phase:

[0108] The cloud or local server initiates an upgrade request to the edge computing power management unit, specifying the target version and verification file. The edge computing power management unit performs security authentication. After successful authentication, the server uses a differential algorithm to compare the current version with the target version and generates a differential upgrade package. The edge computing power management unit receives the differential package and supports resuming interrupted transmissions: if the network is interrupted, the transmission pauses and records the breakpoint; upon resumption, the transmission continues from the breakpoint.

[0109] The edge computing energy management unit generates a complete upgrade package based on the differential upgrade package and the current version of the subsystem, and interacts with the server to verify its integrity. Then, the edge computing energy management unit transmits the complete upgrade package to the target energy storage system.

[0110] The energy storage system's bootloader receives the upgrade package, decrypts it, and performs CRC verification. Upon successful verification, the bootloader writes the new software version to the update area of ​​the storage region, updates the startup configuration, and copies it to the application area after a system reboot to complete the switchover. The switchover is triggered only when the system is idle, ensuring zero interference.

[0111] Post-upgrade processing stage:

[0112] The subsystem feeds back the upgrade results to the edge computing power management unit. The edge computing power management unit records the upgrade history and the list of maintained versions. If the upgrade fails, the edge computing power management unit automatically triggers a rollback, restoring the system to the previous stable version.

[0113] The edge computing power management unit uploads the final results to the cloud or local server for remote monitoring and management. The entire process maximizes upgrade efficiency through system-level collaboration.

[0114] The invention will now be described in detail using a microgrid energy storage system in an industrial park as an example. This microgrid comprises multiple energy storage systems to provide power support for critical loads within the park, such as production lines and data centers. The system needs to complete firmware upgrades without system downtime, while ensuring communication reliability and upgrade efficiency.

[0115] System architecture and initial state:

[0116] FOTA platform: Deployed in the cloud, responsible for upgrade management, sequence decision-making, and rate adjustment.

[0117] Energy storage system: comprises three subsystems: Energy Management System (EMS), Power Conversion System (PCS), and Battery Management System (BMS). EMS is responsible for overall control, PCS handles charging and discharging, and BMS monitors battery status. These three are connected via three communication links:

[0118] First communication link: between EMS and PCS (Ethernet).

[0119] Second communication link: between EMS and BMS (CAN bus).

[0120] The third communication link is between the PCS and the BMS (CAN bus).

[0121] Data registers:

[0122] The first data register in the PCS stores BMS data in real time, including battery charge (SOC), temperature, charge / discharge rate limits, and cycle count.

[0123] The second data register in the BMS stores PCS data in real time, including operating status (start / stop), output power, voltage, current, and fault codes.

[0124] Edge computing energy management unit (EMU): Deployed locally in the campus, it serves as an OTA upgrade center, stores encrypted firmware (such as firmware version V1.0 of EMS, PCS, and BMS), and supports differential upgrades and breakpoint resume.

[0125] Initial state: The energy storage system is running on firmware version V1.0, and the EMU stores the V1.0 firmware and multiple version histories. The campus load is at a normal level, with some energy storage systems experiencing high loads (such as those supporting production lines).

[0126] Detailed upgrade process steps:

[0127] 1. Upgrade preparation phase:

[0128] Step 1.1: Feature information collection and load rate calculation; Each energy storage system (taking energy storage system A as an example) collects its own multi-dimensional feature information in real time and calculates the energy storage load rate through the local controller.

[0129] Collect feature information:

[0130] Battery status: including battery charge (SOC, range 0-1), health status (SOH, range 0-1), and internal resistance (unit: mΩ).

[0131] Power fluctuation: Standard deviation of current output power (based on the last 10 sampling points, in kW).

[0132] Environmental conditions: ambient temperature (°C), humidity (%).

[0133] Power consumption status: Total system power consumption (unit: kW).

[0134] Hardware resources: CPU utilization (range 0-1), memory utilization (range 0-1).

[0135] Normalization: Maps the original values ​​to the range [0,1], using the following formula:

[0136]

[0137] The minimum and maximum values ​​are set based on the system design specifications (e.g., minimum SOC 0, maximum SOC 1; minimum temperature -10°C, maximum temperature 50°C).

[0138] Weighted summation calculation of energy storage load factor: Energy storage load factor = ×SOC+ ×SOH+ ×Power fluctuations+ ×Temperature+ ×humidity+ ×Power Consumption+ ×CPU utilization+ × Memory usage

[0139] in, arrive For the weighting coefficients, satisfying The system importance is set according to the system's importance (in this embodiment, , , , , , , , (Emphasis on battery status and power consumption).

[0140] Calculation example: For energy storage system A, the SOC=0.8, SOH=0.9, power fluctuation=0.2, temperature=0.3, humidity=0.1, power consumption=0.6, CPU utilization=0.4, and memory utilization=0.3. Then the load factor=0.2×0.8+0.1×0.9+...=0.52, or 52%.

[0141] Upload load rate: Energy storage system A uploads the load rate to the FOTA platform in real time.

[0142] Step 1.2: Upgrade order decision; The FOTA platform collects the load rate and preset importance coefficient of all energy storage systems (energy storage systems A, B, and C).

[0143] Importance coefficient: Based on the role of the energy storage system in the park (for example, energy storage system A supports the production line, coefficient = 0.9; energy storage system B supports lighting, coefficient = 0.5; energy storage system C supports backup power, coefficient = 0.7).

[0144] Priority score calculation: Priority score = Energy storage load factor × Importance coefficient

[0145] Energy storage system A: Load factor 0.52, coefficient 0.9 → fraction = 0.468

[0146] Energy storage system B: Load factor 0.7, coefficient 0.5 → fraction = 0.35

[0147] Energy storage system C: Load factor 0.3, coefficient 0.7 → fraction = 0.21

[0148] Sorting: Sorted in ascending order of score (lower score takes precedence), the order is: Energy Storage System C (0.21), Energy Storage System B (0.35), Energy Storage System A (0.468). Energy Storage System C is prioritized for upgrade because of its low load and moderate importance.

[0149] Step 1.3: Dynamic distribution rate adjustment; The FOTA platform adjusts the distribution rate of the upgrade package (target version V2.0) according to the load rate.

[0150] Load rate threshold: set to 70% (based on system performance testing).

[0151] Rate adjustment formula:

[0152] If load rate > threshold: New rate = Current rate − (Load rate − threshold) × First adjustment step size

[0153] If the load rate is less than or equal to the threshold: New rate = Current rate + Second adjustment step size

[0154] Parameter explanation:

[0155] Current rate: Initial value 100kbps (based on network bandwidth).

[0156] First adjustment step size: 10kbps / % (the rate decreases by 10kbps for every 1% increase in load rate above the threshold).

[0157] Second adjustment step size: 5kbps (the rate increases linearly when the load rate is below the threshold).

[0158] Application Example: Energy storage system C has a load rate of 30% ≤ threshold, and its speed is adjusted to 100 + 5 = 105 kbps; energy storage system A has a load rate of 52% ≤ threshold, and its speed is adjusted to 100 + 5 = 105 kbps; energy storage system B has a load rate of 70% (equal to the threshold), and its speed remains unchanged. The FOTA platform simultaneously controls a parallel upgrade capacity of 2 (based on platform capabilities), prioritizing the upgrades of energy storage systems C and B.

[0159] 2. Communication redundancy assurance phase:

[0160] During the upgrade process, the second communication link (CAN bus) between the EMS and BMS of the energy storage system C was temporarily interrupted due to the transmission of the upgrade package.

[0161] Step 2.1: Detect communication failure: The EMS of energy storage system C timed out when attempting to read BMS data (failed 3 times in a row), indicating that the second communication link was interrupted;

[0162] Step 2.2: Activate the backup link:

[0163] EMS sends a read request to PCS via the first communication link (Ethernet) to request BMS data.

[0164] PCS retrieves BMS data (e.g., SOC=0.8, temperature=25°C) from the first data register and converts the data into JSON format that EMS can recognize.

[0165] The PCS reports the data to the EMS, which then continues to monitor the system status based on the data to ensure uninterrupted control during the upgrade process.

[0166] Step 2.3: Automatic Recovery Detection: The EMS sends a heartbeat packet to the second communication link every 5 seconds. After receiving three consecutive responses from the BMS, the EMS automatically switches back to the second communication link and stops accessing the PCS register.

[0167] 3. Upgrade Execution Phase:

[0168] Step 3.1: Upgrade Request and Security Authentication; The cloud server sends an upgrade request to the EMU, specifying the target version V2.0 (used to fix the BMS computing vulnerability) and a verification file (SHA-256 hash value). The EMU first performs security authentication:

[0169] Verify the digital signature (using the RSA-2048 algorithm) to ensure the request originates legitimately.

[0170] After successful authentication, the EMU confirms with the server.

[0171] Step 3.2: Differential upgrade package generation and transmission; The server generates a differential upgrade package using the bsdiff algorithm based on the current version V1.0 and the target version V2.0 of the energy storage system C.

[0172] Differential packet generation: Traverse the firmware files of V1.0 and V2.0, identify the difference data (only the changed parts), and package them into a PATCH file (the size is only 30% of the full packet).

[0173] Verification and Deployment: The server calculates the hash value of the PATCH, compares it with the verification file, and then deploys it to the EMU.

[0174] Resume download mechanism:

[0175] The EMU receives the PATCH file, and the transmission rate is adjusted by the FOTA platform (105kbps in this example).

[0176] The network suddenly stopped (e.g., due to fluctuations in the campus network), and transmission was paused. The EMU recorded the breakpoint (60% of the data had been transmitted).

[0177] Once the network is restored, the EMU resumes transmission from the point of interruption without having to start over.

[0178] Transmission strategy adjustment: Based on network conditions (such as latency and packet loss rate), EMU dynamically adjusts the segment size (default 1KB, reduced to 512B in severe cases) and the number of concurrent requests (default 2, reduced to 1 in severe cases).

[0179] Step 3.3: Generation and verification of the complete upgrade package; The EMU reconstructs the complete upgrade package (V2.0) based on the differential upgrade package and the current version V1.0 of the energy storage system C.

[0180] Reconstruction process: Apply the differential algorithm to merge in reverse and generate complete firmware.

[0181] Integrity verification: The EMU calculates the SHA-256 hash value of the complete packet and compares it with the server's verification file. If the verification passes, the EMU transmits the complete packet to the energy storage system C.

[0182] Step 3.4: Subsystem software update; The bootloader of energy storage system C (pre-installed in the BMS) undergoes an upgrade:

[0183] Reception and decryption: The bootloader receives the complete packet and decrypts it using the AES-256 algorithm (the key is pre-stored in a secure area).

[0184] Verification: Perform a CRC check to ensure data integrity.

[0185] Write and switch:

[0186] Write the new software to the update area (inactive area) of the storage region.

[0187] Update the startup configuration (e.g., modify the boot parameters to point to the update area).

[0188] System status check: Energy storage system C is in idle state (load rate <10% and no charging / discharging operation), triggering a restart. After restarting, the Bootloader copies the software from the update area to the app area (active area), completing the version switch to V2.0.

[0189] 4. Post-upgrade processing stage:

[0190] Step 4.1: Upgrade Result Feedback; The BMS of Energy Storage System C will send the upgrade result (success) back to the EMU. The EMU records the upgrade history (Energy Storage System C, V1.0→V2.0, timestamp).

[0191] Version Management: EMU maintains a version list (including V1.0 and V2.0) and stores rollback images (a complete backup of V1.0).

[0192] Step 4.2: Rollback Mechanism; If the energy storage system C upgrade fails (e.g., CRC check failure or startup timeout), the EMU automatically triggers a rollback:

[0193] After the bootloader detects a failure, it restores the app version to V1.0 from the update area.

[0194] The EMU updates the history and notifies the cloud. The system continues to run on V1.0 to ensure stability.

[0195] Step 4.3: Overall upgrade complete; the EMU uploads the upgrade results of energy storage system C to the cloud server. The FOTA platform continues to upgrade energy storage systems B and A in sequence, repeating the above process. Throughout the entire process, the park's microgrid experienced no downtime, and critical loads (such as production lines) were unaffected.

[0196] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0197] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0198] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0199] In the embodiments provided in this disclosure, it should be understood that the disclosed apparatus / computer devices and methods can be implemented in other ways. For example, the apparatus / computer device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. Multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0200] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0201] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0202] If integrated modules / units are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program may include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in a computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in a jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0203] The above are merely preferred embodiments of the present invention. It should be noted that any modifications and improvements made by those skilled in the art without departing from the present technical solution should also be considered to fall within the scope of protection claimed by the present solution.

Claims

1. An OTA (Over-The-Air) remote upgrade system for energy storage systems, characterized in that: This includes the FOTA platform, used to manage the upgrade process, including upgrade order decisions, upgrade package delivery rate adjustments, and parallel upgrade control; Multiple energy storage systems, each including an energy management system, a power conversion system, and a battery management system, are connected by three communication links: the energy management system and the power conversion system form a first communication link, the energy management system and the battery management system form a second communication link, and the power conversion system and the battery management system form a third communication link; The edge computing energy management unit is deployed in the microgrid system as a local OTA upgrade center, used to store encrypted firmware, process differential upgrade packages, and implement breakpoint resume. The power conversion system and the battery management system are each equipped with a data register to store relevant data from other systems in order to achieve communication redundancy. The energy storage system is configured to collect its own characteristic information, calculate the energy storage load rate, and upload it to the FOTA platform; The FOTA platform is configured to determine the upgrade order based on the energy storage load rate and importance coefficient, and to dynamically adjust the upgrade package delivery rate according to the load rate. The edge computing energy management unit is configured to collaborate with the FOTA platform to generate a complete upgrade package and transmit it to the energy storage system for version rollback and upgrade result feedback.

2. The system according to claim 1, characterized in that: The FOTA platform is further configured as follows: By multiplying the energy storage load rate of the energy storage system by an importance coefficient, a priority score is obtained. The upgrade order is determined by sorting the scores, with those having lower scores being upgraded first. Based on the comparison between the energy storage load rate and the load rate threshold, the target distribution rate of the upgrade package is dynamically adjusted: when the load rate is higher than the threshold, the rate is reduced by the difference and the first adjustment step; when the load rate is not higher than the threshold, the rate is increased by the second adjustment step.

3. The system according to claim 2, characterized in that: The energy storage system is configured as follows: By collecting multi-dimensional feature information, including battery status, power fluctuation, environmental status, power consumption status and hardware resources, normalization processing and weighted summation are performed to calculate the energy storage load rate. After receiving the upgrade package, the version switch is triggered only when the system is idle.

4. The system according to claim 3, characterized in that: The data register includes: The first data register in the power conversion system is used to store relevant data from the battery management system in real time, including battery status, temperature, charge / discharge rate limits, and cycle count. The second data register in the battery management system is used to store relevant data of the power conversion system in real time, including operating status, power information, voltage and current, and fault alarms. Specifically, when the second communication link is interrupted, the energy management system sends a read request to the power conversion system through the first communication link to obtain the battery management system data in the first data register; when the first communication link is interrupted, the energy management system sends a read request to the battery management system through the second communication link to obtain the power conversion system data in the second data register.

5. The system according to claim 4, characterized in that: The edge computing power management unit is further configured as follows: Using differential upgrade technology, generate differential upgrade packages that contain only version difference data, and then verify and deploy them; It supports a breakpoint resume mechanism, which records the progress during the transmission process and resumes the transmission from the breakpoint after the network is interrupted. The system performs security authentication, encrypted storage, and decryption verification on upgrade packages, maintains a version list and upgrade history, and supports version rollback.

6. An OTA remote upgrade method for an energy storage system, applied to the system as described in any one of claims 1-5, characterized in that: The method includes: Upgrade preparation phase: The energy storage system collects its own characteristic information, calculates the energy storage load rate and uploads it to the FOTA platform; the FOTA platform determines the upgrade order based on the energy storage load rate and importance coefficient, and dynamically adjusts the upgrade package delivery rate according to the load rate; Communication redundancy protection phase: During the upgrade process, when the communication link between the energy management system and the battery management system or power conversion system is interrupted, the energy management system accesses the data register through the backup link to obtain critical data and maintain communication; Upgrade execution phase: The edge computing energy management unit receives the upgrade request, generates a differential upgrade package, and transmits it to the energy storage system through a breakpoint resume mechanism; the energy storage system completes the version switch in an idle state; Post-upgrade processing stage: The edge computing energy management unit monitors the upgrade results, supports version rollback, and feeds back the results to the cloud or local server.

7. The method according to claim 6, characterized in that: During the upgrade preparation phase, calculating the energy storage load factor includes: Collect multi-dimensional feature information on battery status, power fluctuation, environmental status, power consumption status, and hardware resources; The feature information is normalized and the energy storage load rate is obtained by weighted summation.

8. The method according to claim 6, characterized in that: The communication redundancy guarantee phase includes: When the energy management system fails to communicate with the battery management system, the energy management system sends a read request to the power conversion system, and the power conversion system reports the battery management system data in the first data register to the energy management system. When the energy management system fails to communicate with the power conversion system, the energy management system sends a read request to the battery management system, and the battery management system reports the power conversion system data in the second data register to the energy management system. The energy management system periodically sends recovery requests to the faulty communication link, and switches back to the original communication link once communication is restored.

9. The method according to claim 6, characterized in that, The upgrade execution phase includes: The edge computing power management unit performs security authentication on the upgrade request, and receives the differential upgrade package after successful authentication. The edge computing power management unit generates a complete upgrade package based on the differential upgrade package and the current version, and verifies its integrity with the server. The energy storage system's bootloader receives the upgrade package, decrypts and verifies it, writes the new version of the software to the storage area, updates the startup configuration, and copies it to the application area after restarting.

10. The method according to claim 6, characterized in that, The post-upgrade processing stage includes: The subsystem will feed back the upgrade results to the edge computing energy management unit, which will then upload the results to the cloud or a local server. If the upgrade fails, the edge computing energy management unit will trigger a version rollback, restoring to the previous stable version.

Images