Multi-level remote upgrading method, upgrading system, storage medium and energy storage system

Abstract

The invention provides a multi-level remote upgrading method and system, a storage medium and an energy storage system. The method comprises the following steps: acquiring an upgrading file, and executing corresponding upgrading work based on the acquired upgrading file and a current application architecture; wherein when the current application architecture is the first architecture, whether the battery control unit is upgraded or not is judged based on the upgrading file, and if yes, first upgrading work is executed; otherwise, executing second upgrading work; when the current application is the second architecture, judging whether the battery access unit is upgraded or not based on the upgrading file, and if yes, executing third upgrading work; if the battery access unit is not upgraded, whether the battery control unit is upgraded or not is judged based on the upgrading file, and if yes, first upgrading work is executed; otherwise, executing the second upgrading work. According to the method, the corresponding upgrading work can be automatically judged and executed, and meanwhile, manual upgrading confirmation caused by lack of links is avoided.

Description

Technical Field

[0001] The present application relates to the field of upgrade technology, and in particular to a multi-level remote upgrade method, an upgrade system, a storage medium, and an energy storage system. Background Art

[0002] In normal project development and debugging, the download program generally uses an external downloader or serial port to download and refresh the MCU program. This method is the most commonly used method in the project development stage. However, when the project development is completed and launched on the market, it is often necessary to upgrade the product. At this time, the product has been added with a shell or packaged, and generally no download interface is reserved outside.

[0003] If you need to update the product program, you may have to reopen the product shell, then update the program through the downloader, and then install the shell after the update is complete. This approach is obviously unrealistic.

[0004] Therefore, it is necessary to reserve some external communication interfaces for the product itself for upgrading; the application framework of the energy storage system is mostly a two-level or three-level architecture; however, during the upgrade process, different architectures may require manual processing due to the lack of a certain link. Summary of the invention

[0005] In order to solve the above-mentioned technical problems, the present application provides a multi-level remote upgrade method, an upgrade system, a storage medium and an energy storage system.

[0006] Specifically, the present application provides a multi-level remote upgrade method, comprising the following steps:

[0007] Obtain an upgrade file, and perform corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least a first architecture and a second architecture, and the upgrade work includes at least a first upgrade work, a second upgrade work, and a third upgrade work.

[0008] When the current application architecture is the first architecture, it is determined based on the upgrade file whether to upgrade the battery control unit. If so, the first upgrade operation is performed; otherwise, the second upgrade operation is performed.

[0009] When the current application is the second architecture, determine whether to upgrade the battery access unit based on the upgrade file. If so, execute the third upgrade work; if the battery access unit is not upgraded, determine whether to upgrade the battery control unit based on the upgrade file. If so, execute the first upgrade work; otherwise, execute the second upgrade work.

[0010] In the above technical solution, through multi-level upgrade logic, the system can automatically determine and execute the corresponding upgrade work, reducing the inconvenience and errors caused by the manual process; for example, when the product architecture changes, the system can adapt to the corresponding upgrade process and reduce the possibility of manual processing due to missing links.

[0011] Furthermore, obtaining the upgrade file includes:

[0012] In response to the upgrade request instruction from the external platform, the battery control unit or the battery access unit receives a request file issued based on a preset protocol, and parses the request file to obtain an upgrade file.

[0013] In the above technical solution, when the energy storage system is connected to an external platform, the external platform can send a request upgrade instruction, and the external platform can be a cloud server, a management system or other monitoring equipment; the battery control unit or the battery access unit is responsible for receiving the request file issued based on a preset protocol, and the preset protocol can ensure compatibility between different systems and platforms; after receiving the request file, the system will parse the request file to extract the specific information of the upgrade file.

[0014] Among them, through the request instructions of the external platform, the entire upgrade acquisition process can be fully automated, reducing human intervention and improving work efficiency; the use of preset protocols can adapt to a variety of network environments and management requirements, providing the system with greater flexibility; through an effective parsing mechanism, repeated downloads and transmission of redundant data are avoided, thereby saving bandwidth and storage resources.

[0015] Furthermore, the first upgrading work includes:

[0016] If the current architecture is the first architecture, the battery control unit upgrade command is directly obtained based on the upgrade file through the battery control unit.

[0017] If the current architecture is the second architecture, the battery access unit obtains a battery control unit upgrade command based on the upgrade file, and transmits the battery control unit upgrade command to the battery control unit through the first communication interface.

[0018] And, the battery control unit upgrade command is verified, so that when the verification passes, the upgrade program corresponding to the battery control unit is executed.

[0019] Wherein, the first communication interface is arranged between the battery access unit and the battery control unit.

[0020] In the above technical solution, different processing methods (first architecture and second architecture) are adopted for different architectures, so that the system can flexibly respond to various upgrade scenarios and ensure the scalability of the system; in the first architecture, the battery control unit can directly process the upgrade command, avoiding multiple transmissions of information between different units and simplifying the upgrade process; by verifying before executing the upgrade command, the legality and integrity of the upgrade command are ensured to prevent illegal operations or erroneous upgrades from affecting the system; the battery access unit and the battery control unit communicate through a standardized interface. This modular design facilitates system maintenance and expansion and reduces dependence on specific hardware.

[0021] Furthermore, the second upgrade work includes:

[0022] If the current architecture is the first architecture, the battery control unit obtains a battery management unit upgrade command based on the upgrade file.

[0023] If the current architecture is the second architecture, the battery access unit obtains a battery management unit upgrade command based on the upgrade file, and transmits the battery management unit upgrade command to the battery control unit through the first communication interface.

[0024] And, the battery management unit upgrade command is verified, and when the verification passes, the upgrade file is stored in a preset storage space, and the battery management unit upgrade command is transmitted to the battery management unit through the second communication interface to execute the upgrade program corresponding to the battery management unit.

[0025] Wherein, the second communication interface is arranged between the battery control unit and the battery management unit.

[0026] In the above technical solution, different application architectures (first architecture and second architecture) can be supported, and the most appropriate upgrade path is adopted for each architecture; the upgrade files are stored in the preset storage space to ensure the stability and reliability of data during the upgrade process, avoiding data loss or damage; the entire upgrade process is highly automated, reducing the risk of human intervention and operational errors. The system can make autonomous decisions and execute upgrade tasks, improving the reliability and maintainability of the system.

[0027] Furthermore, the third upgrade work includes:

[0028] A battery access unit upgrade command is obtained based on the upgrade file, and the battery access unit upgrade command is verified. When the verification passes, the upgrade file is verified. If the upgrade file verification passes, a target application is obtained based on the upgrade file, and a corresponding application is run with the target application.

[0029] In the above technical solution, by verifying the battery access unit upgrade command, the accuracy and security of the upgrade process are ensured to prevent the impact of illegal operations or erroneous upgrades on the system; by running the target application, the battery access unit obtains the latest functions and performance optimization.

[0030] Further, the executing the upgrade procedure includes:

[0031] Obtain the original application corresponding to the battery control unit or battery management unit, store the original application in a preset storage space, and verify the upgrade file. If the verification passes, obtain the target application based on the upgrade file and run the corresponding application with the target application.

[0032] In the above technical solution, the original application is stored in a preset storage space to ensure that a backup is available during the upgrade process, thereby improving the reliability and security of the system and avoiding data loss or system crash due to upgrade failure; by verifying the upgrade file, the integrity and correctness of the file are ensured to prevent illegal operations or erroneous files from affecting the system; by running the target application, the battery control unit or battery management unit obtains the latest functions and performance optimization.

[0033] Furthermore, it also includes:

[0034] When the battery control unit upgrade command, the battery access unit upgrade command or the battery management unit upgrade command fails to be verified, the upgrade work is ended.

[0035] When the upgrade file verification fails, the original application is extracted from the preset storage space, and the corresponding application is run with the original application.

[0036] In the above technical solution, by immediately ending the upgrade work, system failure or instability caused by erroneous upgrade commands or files is prevented; in the event of file verification failure, the system can automatically roll back to the stable state before the upgrade and continue to run using the original application. This fault-tolerant capability ensures that the system can still work normally when the upgrade fails.

[0037] Based on the same concept, the present application also provides a multi-level remote upgrade system, the upgrade system comprising:

[0038] Get module: Get the upgrade file.

[0039] Upgrade module: performs corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least a first architecture and a second architecture, and the upgrade work includes at least a first upgrade work, a second upgrade work and a third upgrade work.

[0040] In the above technical solution, each level in different architectures can be upgraded, and manual on-site upgrades are not required due to the lack of a certain link, which improves operation and maintenance efficiency and reduces operation and maintenance costs.

[0041] Based on the same concept, the present application also provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the multi-level remote upgrade method when running.

[0042] Based on the same concept, the present application also provides an energy storage system, wherein the energy storage system is configured with a multi-level remote upgrade system, and the upgrade system adopts the multi-level remote upgrade method to perform the upgrade work.

[0043] Compared with the prior art, the beneficial effects of this application are:

[0044] The present application first obtains the upgrade file, and performs the corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least the first architecture and the second architecture, and the upgrade work includes at least the first upgrade work, the second upgrade work and the third upgrade work; wherein, when the current application architecture is the first architecture, it is determined based on the upgrade file whether to upgrade the battery control unit, and if so, the first upgrade work is performed; otherwise, the second upgrade work is performed; when the current application is the second architecture, it is determined based on the upgrade file whether to upgrade the battery access unit, and if so, the third upgrade work is performed; if the battery access unit is not upgraded, it is determined based on the upgrade file whether to upgrade the battery control unit, and if so, the first upgrade work is performed; otherwise, the second upgrade work is performed. The present application can automatically determine and perform the corresponding upgrade work, reducing the inconvenience and errors caused by the manual process. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 This is a flow chart of the multi-level remote upgrade method described in this application.

[0046] Figure 2 This is a framework diagram of the multi-level remote upgrade system described in this application. DETAILED DESCRIPTION

[0047] The following is a further detailed description of a multi-level remote upgrade method, upgrade system, storage medium and energy storage system of the present application in conjunction with specific embodiments and drawings.

[0048] Embodiment 1:

[0049] See also Figure 1 The present application provides a multi-level remote upgrade method, comprising the following steps:

[0050] Obtain an upgrade file, and perform corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least a first architecture and a second architecture, and the upgrade work includes at least a first upgrade work, a second upgrade work, and a third upgrade work.

[0051] It should be noted that the first architecture is a two-level architecture, including at least a battery control unit and a battery management unit; the second architecture is a three-level architecture, including at least a battery access unit, a battery management unit and a battery control unit.

[0052] Among them, the battery control unit is mainly responsible for the overall control and coordination of the battery system; the battery management unit is mainly responsible for monitoring and managing the status of the battery pack, including voltage, temperature, current, etc., to ensure the safe and efficient operation of the battery; the battery access unit is mainly responsible for the access and management of the battery pack.

[0053] The first upgrade work corresponds to the battery control unit, the second upgrade work corresponds to the battery management unit, and the third upgrade work corresponds to the battery access unit.

[0054] When the current application architecture is the first architecture, it is determined based on the upgrade file whether to upgrade the battery control unit. If so, the first upgrade operation is performed; otherwise, the second upgrade operation is performed.

[0055] When the current application is the second architecture, determine whether to upgrade the battery access unit based on the upgrade file. If so, execute the third upgrade work; if the battery access unit is not upgraded, determine whether to upgrade the battery control unit based on the upgrade file. If so, execute the first upgrade work; otherwise, execute the second upgrade work.

[0056] Furthermore, obtaining the upgrade file includes:

[0057] In response to the upgrade request instruction from the external platform, the battery control unit or the battery access unit receives a request file issued based on a preset protocol, and parses the request file to obtain an upgrade file.

[0058] In some embodiments, the external platform detects that a new program version has been released, and sends a request upgrade instruction to the battery control unit or the battery access unit through an external communication interface (such as CAN, RS485, WIFI or a host computer, etc.). When the battery control unit or the battery access unit receives the request upgrade instruction, it receives the request file from the external platform through a preset protocol.

[0059] Among them, the preset protocol must correspond to the external communication interface, because the request file is obtained based on the external communication interface; if the external communication interface currently used is CAN, for example, the ISO 11898-1 protocol is used, which defines the high-speed CAN protocol; if RS485 is currently used, for example, the Modbus RTU protocol is used; if WIFI is currently used, for example, the IEEE 802.11n / ac / ax protocol is used, which supports higher transmission rates and better anti-interference capabilities; if the host computer is currently used, for example, serial communication (such as RS232) or LAN communication (such as TCP / IP) is used, flexible data formats and transmission methods are supported.

[0060] The request file is further parsed to obtain an upgrade file, which at least includes an upgrade command corresponding to the component currently requiring upgrade, a target application, and the like.

[0061] In the above technical solution, when the energy storage system is connected to an external platform, the external platform can send a request upgrade instruction, and the external platform can be a cloud server, a management system or other monitoring equipment; the battery control unit or the battery access unit is responsible for receiving the request file issued based on a preset protocol, and the preset protocol can ensure compatibility between different systems and platforms; after receiving the request file, the system will parse the request file to extract the specific information of the upgrade file.

[0062] Among them, through the request instructions of the external platform, the entire upgrade acquisition process can be fully automated, reducing human intervention and improving work efficiency; the use of preset protocols can adapt to a variety of network environments and management requirements, providing the system with greater flexibility; through an effective parsing mechanism, repeated downloads and transmission of redundant data are avoided, thereby saving bandwidth and storage resources.

[0063] Furthermore, the first upgrading work includes:

[0064] If the current architecture is the first architecture, the battery control unit upgrade command is directly obtained based on the upgrade file through the battery control unit.

[0065] In some embodiments, the battery control unit of the secondary architecture (i.e., the first architecture) can directly obtain the upgrade file, and then obtain the upgrade command corresponding to the component that currently needs to be upgraded based on the upgrade file, and determine whether the upgrade command is a battery control unit upgrade command. If so, it starts to execute the first upgrade work.

[0066] In other embodiments, if it is determined under the secondary architecture that the current upgrade command is not a battery control unit upgrade command, the second upgrade operation is performed.

[0067] If the current architecture is the second architecture, the battery access unit obtains a battery control unit upgrade command based on the upgrade file, and transmits the battery control unit upgrade command to the battery control unit through the first communication interface.

[0068] Wherein, the first communication interface is arranged between the battery access unit and the battery control unit; in some embodiments, the first communication interface is an internal CAN communication interface arranged between the battery access unit and the battery control unit.

[0069] In some embodiments, under the three-level architecture (i.e., the second architecture), the battery access unit is the medium for directly obtaining the upgrade file, and then obtains the upgrade command corresponding to the component that currently needs to be upgraded according to the upgrade file, and determines whether the upgrade command is a battery access unit upgrade command. If not, it further determines whether it is a battery control unit upgrade command based on the current upgrade command, and starts executing the first upgrade task.

[0070] In other embodiments, if the command initially obtained is a battery access unit upgrade command, the third upgrade operation is performed; and if further determination shows that the command is not a battery control unit upgrade command, the second upgrade operation is performed.

[0071] And, the battery control unit upgrade command is verified, so that when the verification passes, the upgrade program corresponding to the battery control unit is executed.

[0072] In some embodiments, at the beginning of executing the first upgrade work, the battery control unit upgrade command is verified; wherein, the verification can be performed through a checksum, a hash value, a version number and / or a command format.

[0073] Specifically: When the upgrade file is sent, the external platform will generate a checksum or hash value corresponding to each command. After receiving the upgrade command, it will calculate the checksum or hash value of the received upgrade command, and then compare the calculated checksum or hash value with the one in the request. If they are the same, the verification passes and the upgrade program continues; if they are different, the verification fails.

[0074] In the upgrade command, check whether the version number field exists and conforms to the expected format, and confirm whether the upgrade version number is newer than the current version number. The upgrade program is allowed to execute only when the version number is legal and valid.

[0075] If the command format is to be verified, the required fields included in the upgrade command structure (such as JSON or XML) need to be pre-defined; the received upgrade command is formatted and formatted to ensure that all required fields exist and are in the correct format. The upgrade program is allowed to execute only if the format verification passes.

[0076] It should be noted that, when verifying the upgrade command, those skilled in the art may select only one verification method, or may select several verification methods at the same time to verify in sequence, which is not limited here.

[0077] In the above technical solution, different processing methods (first architecture and second architecture) are adopted for different architectures, so that the system can flexibly respond to various upgrade scenarios and ensure the scalability of the system; in the first architecture, the battery control unit can directly process the upgrade command, avoiding multiple transmissions of information between different units and simplifying the upgrade process; by verifying before executing the upgrade command, the legality and integrity of the upgrade command are ensured to prevent illegal operations or erroneous upgrades from affecting the system; the battery access unit and the battery control unit communicate through a standardized interface. This modular design facilitates system maintenance and expansion and reduces dependence on specific hardware.

[0078] Furthermore, the second upgrade work includes:

[0079] If the current architecture is the first architecture, the battery control unit obtains a battery management unit upgrade command based on the upgrade file.

[0080] If the current architecture is the second architecture, the battery access unit obtains a battery management unit upgrade command based on the upgrade file, and transmits the battery management unit upgrade command to the battery control unit through the first communication interface.

[0081] And, the battery management unit upgrade command is verified, and when the verification passes, the upgrade file is stored in a preset storage space, and the battery management unit upgrade command is transmitted to the battery management unit through the second communication interface to execute the upgrade program corresponding to the battery management unit.

[0082] Wherein, the second communication interface is arranged between the battery control unit and the battery management unit; in some embodiments, the second communication interface is an internal CAN communication interface arranged between the battery control unit and the battery management unit.

[0083] In some embodiments, the battery management unit needs to interact with the battery control unit to obtain a battery management unit upgrade command.

[0084] It should be noted that, in some embodiments, the method for verifying the battery management unit upgrade command is the same as the battery control unit upgrade command, which will not be described in detail here.

[0085] In the above technical solution, different application architectures (first architecture and second architecture) can be supported, and the most appropriate upgrade path is adopted for each architecture; the upgrade files are stored in the preset storage space to ensure the stability and reliability of data during the upgrade process, avoiding data loss or damage; the entire upgrade process is highly automated, reducing the risk of human intervention and operational errors. The system can make autonomous decisions and execute upgrade tasks, improving the reliability and maintainability of the system.

[0086] Furthermore, the third upgrade work includes:

[0087] A battery access unit upgrade command is obtained based on the upgrade file, and the battery access unit upgrade command is verified. When the verification passes, the upgrade file is verified. If the upgrade file verification passes, a target application is obtained based on the upgrade file, and a corresponding application is run with the target application.

[0088] In some embodiments, the battery access unit can directly obtain the corresponding upgrade command based on the upgrade file without interacting with other unit components.

[0089] It should be noted that, in some embodiments, the method for verifying the battery access unit upgrade command is the same as the battery control unit upgrade command, which will not be described in detail here.

[0090] In the above technical solution, by verifying the battery access unit upgrade command, the accuracy and security of the upgrade process are ensured to prevent the impact of illegal operations or erroneous upgrades on the system; by running the target application, the battery access unit obtains the latest functions and performance optimization.

[0091] Further, the executing the upgrade procedure includes:

[0092] Obtain the original application corresponding to the battery control unit or battery management unit, store the original application in a preset storage space, and verify the upgrade file. If the verification passes, obtain the target application based on the upgrade file and run the corresponding application with the target application.

[0093] In some embodiments, the preset storage space is, for example, a designated FLASH space, for storing the original application in the first upgrade operation or the second upgrade operation.

[0094] Furthermore, no matter in the first upgrade work, the second upgrade work or the third upgrade work, the upgrade file needs to be verified.

[0095] Optionally, obtain the digital signature of the upgrade file from the external platform, and use the public key to verify the upgrade file and the signature; if the verification passes, further complete the upgrade work.

[0096] Optionally, the first several bytes of the upgrade file are read to perform format analysis, and the file content is verified block by block according to a predefined file format specification. If the verification passes, the upgrade work is further completed.

[0097] It should be noted that those skilled in the art may also select other upgrade file verification methods, and are not limited to the above two methods.

[0098] In the above technical solution, the original application is stored in a preset storage space to ensure that a backup is available during the upgrade process, thereby improving the reliability and security of the system and avoiding data loss or system crash due to upgrade failure; by verifying the upgrade file, the integrity and correctness of the file are ensured to prevent illegal operations or erroneous files from affecting the system; by running the target application, the battery control unit or battery management unit obtains the latest functions and performance optimization.

[0099] Furthermore, it also includes:

[0100] When the battery control unit upgrade command, the battery access unit upgrade command or the battery management unit upgrade command fails to be verified, the upgrade work is ended.

[0101] When the upgrade file verification fails, the original application is extracted from the preset storage space, and the corresponding application is run with the original application.

[0102] In the above technical solution, by immediately ending the upgrade work, system failure or instability caused by erroneous upgrade commands or files is prevented; in the event of file verification failure, the system can automatically roll back to the stable state before the upgrade and continue to run using the original application. This fault-tolerant capability ensures that the system can still work normally when the upgrade fails.

[0103] Embodiment 2:

[0104] See also Figure 2 The present application also provides an upgrade system using the multi-level remote upgrade method as described in Example 1, the upgrade system comprising:

[0105] Get module: Get the upgrade file.

[0106] Upgrade module: performs corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least a first architecture and a second architecture, and the upgrade work includes at least a first upgrade work, a second upgrade work and a third upgrade work.

[0107] When the current application architecture is the first architecture, it is determined based on the upgrade file whether to upgrade the battery control unit. If so, the first upgrade operation is performed; otherwise, the second upgrade operation is performed.

[0108] When the current application is the second architecture, determine whether to upgrade the battery access unit based on the upgrade file. If so, execute the third upgrade work; if the battery access unit is not upgraded, determine whether to upgrade the battery control unit based on the upgrade file. If so, execute the first upgrade work; otherwise, execute the second upgrade work.

[0109] In the above technical solution, each level in different architectures can be upgraded, and manual on-site upgrades are not required due to the lack of a certain link, which improves operation and maintenance efficiency and reduces operation and maintenance costs.

[0110] Embodiment three:

[0111] The present application also provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the multi-level remote upgrade method described in the first embodiment when running.

[0112] In some embodiments, the storage medium stores a number of computer programs to enable an energy storage system to execute all or part of the steps of the methods described in the various embodiments of the present application; the storage medium may include a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.

[0113] Embodiment 4:

[0114] The present application also provides an energy storage system, which is configured with a multi-level remote upgrade system, and the upgrade system uses the multi-level remote upgrade method described in Example 1 to perform upgrade work.

[0115] In summary, the present application provides a multi-level remote upgrade method, upgrade system, storage medium and energy storage system; first, obtain the upgrade file, and perform the corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least the first architecture and the second architecture, and the upgrade work includes at least the first upgrade work, the second upgrade work and the third upgrade work; wherein, when the current application architecture is the first architecture, determine whether to upgrade the battery control unit based on the upgrade file, and if so, perform the first upgrade work; otherwise, perform the second upgrade work; when the current application is the second architecture, determine whether to upgrade the battery access unit based on the upgrade file, and if so, perform the third upgrade work; if the battery access unit is not upgraded, determine whether to upgrade the battery control unit based on the upgrade file, and if so, perform the first upgrade work; otherwise, perform the second upgrade work. The present application can automatically determine and perform the corresponding upgrade work, reducing the inconvenience and errors caused by the manual process.

[0116] Although example embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above example embodiments are merely exemplary and are not intended to limit the scope of the present application to this. Those of ordinary skill in the art may make various changes and modifications therein without departing from the scope and spirit of the present application. All these changes and modifications are intended to be included within the scope of the present application as required by the appended claims.

[0117] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0118] Although the description of the present application is carried out in conjunction with the above specific embodiments, it is obvious that those skilled in the art can make many substitutions, modifications and changes based on the above content. Therefore, all such substitutions, improvements and changes are included in the spirit and scope of the appended claims.

Claims

1. A multi-level remote upgrade method, characterized in that: The following steps are involved: Obtain an upgrade file, and perform corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least a first architecture and a second architecture, and the upgrade work includes at least a first upgrade work, a second upgrade work, and a third upgrade work; Wherein, when the current application architecture is the first architecture, judging whether to upgrade the battery control unit based on the upgrade file, if so, executing the first upgrade work; otherwise, executing the second upgrade work; When the current application is the second architecture, determine whether to upgrade the battery access unit based on the upgrade file. If so, execute the third upgrade work; if the battery access unit is not upgraded, determine whether to upgrade the battery control unit based on the upgrade file. If so, execute the first upgrade work; otherwise, execute the second upgrade work.

2. The multi-level remote upgrade method according to claim 1, characterized in that: The obtaining of the upgrade file includes: In response to the upgrade request instruction from the external platform, the battery control unit or the battery access unit receives a request file issued based on a preset protocol, and parses the request file to obtain an upgrade file.

3. The multi-level remote upgrade method according to claim 2, characterized in that: The first upgrade work includes: If the current architecture is the first architecture, obtaining a battery control unit upgrade command directly based on the upgrade file through the battery control unit; If the current architecture is the second architecture, obtaining a battery control unit upgrade command based on the upgrade file through the battery access unit, and transmitting the battery control unit upgrade command to the battery control unit through the first communication interface; and verifying the battery control unit upgrade command, so that when the verification passes, executing the upgrade program corresponding to the battery control unit; Wherein, the first communication interface is arranged between the battery access unit and the battery control unit.

4. The multi-level remote upgrade method according to claim 3, characterized in that: The second upgrade work includes: If the current architecture is the first one, the battery control unit obtains a battery management unit upgrade command based on the upgrade file; if the current architecture is the second one, the battery access unit obtains a battery management unit upgrade command based on the upgrade file, and transmits the battery management unit upgrade command to the battery control unit through the first communication interface; and verifying the battery management unit upgrade command, so that when the verification passes, the upgrade file is stored in a preset storage space, and the battery management unit upgrade command is transmitted to the battery management unit through a second communication interface to execute the upgrade program corresponding to the battery management unit; Wherein, the second communication interface is arranged between the battery control unit and the battery management unit.

5. The multi-level remote upgrade method according to claim 2, characterized in that: The third upgrade work includes: A battery access unit upgrade command is obtained based on the upgrade file, and the battery access unit upgrade command is verified. When the verification passes, the upgrade file is verified. If the upgrade file verification passes, a target application is obtained based on the upgrade file, and a corresponding application is run with the target application.

6. The multi-level remote upgrade method according to claim 4, characterized in that: The execution upgrade procedure includes: Obtain the original application corresponding to the battery control unit or battery management unit, store the original application in a preset storage space, and verify the upgrade file. If the verification passes, obtain the target application based on the upgrade file and run the corresponding application with the target application.

7. The multi-level remote upgrade method according to claim 5 or 6, characterized in that: Also includes: When the battery control unit upgrade command, the battery access unit upgrade command or the battery management unit upgrade command fails to be verified, the upgrade work is terminated; When the upgrade file verification fails, the original application is extracted from the preset storage space, and the corresponding application is run with the original application.

8. An upgrade system using the multi-level remote upgrade method according to any one of claims 1 to 7, characterized in that: The upgrade system comprises: Get module: get the upgrade file; Upgrade module: performs corresponding upgrade work based on the upgrade file and the current application architecture; the application architecture includes at least a first architecture and a second architecture, and the upgrade work includes at least a first upgrade work, a second upgrade work and a third upgrade work.

9. A storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the multi-level remote upgrade method according to any one of claims 1 to 7 when running.

10. An energy storage system, characterized in that: The energy storage system is configured with a multi-level remote upgrade system, and the upgrade system uses the multi-level remote upgrade method according to any one of claims 1 to 7 to perform the upgrade work.

Images