System and method for upgrading battery firmware by using charging cabinet

Abstract

The embodiment of the invention provides a system and a method for upgrading battery firmware by using a charging cabinet. The system comprises a main controller and a plurality of cell controllers, the main controller is in communication connection with the battery management platform and the grid controllers; each grid controller corresponds to one or more grids of the battery charging cabinet, and each grid controller comprises a memory for storing a plurality of reference battery firmware; in response to establishment of connection between the target battery and the target cell, the first cell controller corresponding to the target cell is used for acquiring current version information of firmware of the target battery and sending the current version information to the main controller; the main controller is used for sending the current version information to the battery management platform and sending the target version information to the first cell controller after receiving the target version information sent by the battery management platform; and the first cell controller is used for determining reference version information corresponding to a plurality of reference battery firmware, and performing firmware updating on the target battery based on the target version information and the reference version information.

Description

Technical Field

[0001] This specification relates to the field of charging technology, and particularly to a system and method for upgrading battery firmware using a charging cabinet. Background Art

[0002] With the popularization of the awareness of energy conservation and environmental protection, new energy electric vehicles are becoming more and more popular. The battery is the core component of an electric vehicle, and its firmware needs to be continuously updated or upgraded. Existing methods usually rely on a cloud platform (such as a remote server, etc.) to store and maintain the battery firmware of different manufacturers. When the battery is placed in the charging cabinet, the charging cabinet reports the version information of the battery to the cloud, and the cloud determines whether an upgrade is needed. When an upgrade is needed, the cloud platform sends the latest version of the battery firmware to the charging cabinet through the network to update or upgrade the version of the battery firmware. The long transmission link easily leads to a long upgrade time and a poor experience. At the same time, each large file transmission occupies a large amount of bandwidth and requires more traffic costs.

[0003] Therefore, a system and method for upgrading battery firmware using a charging cabinet are provided, which can improve the firmware upgrade efficiency of battery devices and reduce the consumption of network resources and upgrade costs. Summary of the Invention

[0004] One embodiment of this specification provides a system for upgrading battery firmware using a charging cabinet, including a main controller and multiple compartment controllers. Among them, the main controller is communicatively connected to a battery management platform and the multiple compartment controllers; each of the compartment controllers corresponds to one or more compartments of the battery charging cabinet, and each of the compartment controllers includes a memory for storing multiple reference battery firmwares; in response to a target battery establishing a connection with a target compartment in the battery charging cabinet, the first compartment controller corresponding to the target compartment is configured to obtain the current version information of the firmware of the target battery and send the current version information to the main controller; the main controller is configured to send the current version information to the battery management platform, receive the target version information sent by the battery management platform, and send the target version information to the first compartment controller; the first compartment controller is further configured to determine the reference version information corresponding to the multiple reference battery firmwares stored on the first compartment controller, and based on the target version information and the reference version information, update the firmware of the target battery.

[0005] One embodiment of this specification provides a method for upgrading battery firmware using a charging cabinet, which is applied to the system for upgrading battery firmware using a charging cabinet as described above, including: obtaining the current version information of a target battery through a first compartment controller corresponding to a target compartment, and sending the current version information to a main controller; sending the current version information to a battery management platform through the main controller, receiving the target version information sent by the battery management platform, and sending the target version information to the first compartment controller; determining the reference version information corresponding to a plurality of reference battery firmware stored on the first compartment controller through the first compartment controller, and performing firmware update on the target battery based on the target version information and the reference version information.

[0006] One embodiment of this specification provides a computer-readable storage medium storing instructions that, when executed by a processor of a main controller and / or a compartment controller, cause the processor to execute the method for upgrading battery firmware using a charging cabinet as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] This specification will be further described by way of exemplary embodiments, which will be described in detail through the drawings. These embodiments are not restrictive. In these embodiments, the same numbers represent the same structures, where:

[0008] Figure 1 is a schematic diagram of an application scenario of a management system of a battery charging cabinet according to some embodiments of this specification;

[0009] Figure 2 is an exemplary schematic diagram of a battery charging cabinet device according to some embodiments of this specification;

[0010] Figure 3 is an exemplary schematic diagram of a controller according to some embodiments of this specification;

[0011] Figure 4 is an exemplary flowchart of a management method of a battery charging cabinet according to some embodiments of this specification;

[0012] Figure 5 is an exemplary flowchart of a method for a first compartment controller to store target battery firmware according to some embodiments of this specification;

[0013] Figure 6 is an exemplary flowchart of a method for a first compartment controller to obtain target battery firmware according to some embodiments of this specification;

[0014] Figure 7It is an exemplary flowchart of a method for obtaining a target battery firmware by another first cell controller shown in some embodiments of this specification. Detailed implementation manners

[0015] To more clearly illustrate the technical solutions of the embodiments of this specification, the accompanying drawings required for the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some examples or embodiments of this specification. For those of ordinary skill in the art, without creative efforts, this specification can also be applied to other similar scenarios based on these drawings. Unless obvious from the language context or otherwise stated, the same reference numerals in the drawings represent the same structure or operation.

[0016] It should be understood that the "system", "device", "unit" and / or "module" used herein is a way to distinguish different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the said words can be replaced by other expressions.

[0017] Unless the context clearly indicates an exception, words such as "a", "an", "one" and / or "the" are not specifically singular and may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0018] Flowcharts are used in this specification to illustrate the operations performed by the systems according to the embodiments of this specification. It should be understood that the operations before or after may not necessarily be executed precisely in sequence. On the contrary, the steps can be processed in reverse order or simultaneously. At the same time, other operations can also be added to these processes, or one or several operations can be removed from these processes.

[0019] Figure 1 It is a schematic diagram of an application scenario of a management system for a battery charging cabinet shown in some embodiments of this specification.

[0020] As Figure 1 shown, the application scenario 100 of the management system for the battery charging cabinet (hereinafter referred to as the management system) may include an electric device 110, a charging cabinet 120, a network 130, and a battery management platform 140.

[0021] The electric device 110 refers to a device that uses a battery as an energy source. For example, the electric device 110 may include devices that require charging / replacing the battery, such as two-wheeled electric vehicles, electric vehicles with detachable batteries, and smartphones. The electric device 110 may include a built-in battery management program / application for monitoring the operation of the battery (such as remaining battery level, available battery life, etc.). Consumer users (such as the owners, renters, or users of the electric device 110) can charge / replace the battery of the electric device 110 through the battery charging cabinet 120 to meet the battery's endurance requirements.

[0022] The electric device 110 may include electric devices of multiple different brands (or manufacturers) (such as electric device 110-1... electric device 110-n, etc.). The batteries of electric devices 110 of different brands may correspond to different battery firmware. In some embodiments, when the battery of the electric device 110 is connected to the battery charging cabinet 120 for charging, the charging cabinet 120 may upgrade or update the battery firmware of the battery. For more information about battery firmware and its update, see Figure 4 and its description.

[0023] The battery charging cabinet 120 refers to a self-service charging device for charging batteries. In some embodiments, the management user (such as the charging cabinet operator) may deploy multiple battery charging cabinets 120 within a certain geographical area (such as residential areas, shopping malls, etc.) according to the needs of consumer users (such as the users of the electric device 110) (such as the frequency of charging), such as Figure 1 the battery charging cabinets 120-1, battery charging cabinets 120-2... battery charging cabinets 120-n, etc. as shown.

[0024] In some embodiments, the battery charging cabinet 120 may be connected to a network (such as network 130) and send data and / or instructions to one or more components in the application scenario 100 through the network, and / or receive data and / or instructions from one or more components in the application scenario 100. For example, the battery charging cabinet 120 may receive data and / or instructions (such as the latest version of the battery firmware of the electric device 110) from the battery management platform 140 through the network 130; it may also send information and / or instructions (such as a request for detecting the upgrade of the battery firmware) to the battery management platform 140 through the network 130.

[0025] In some embodiments, the battery charging cabinet 120 (such as the battery charging cabinet 120-1, etc.) may include a plurality of compartments (or panes), and each compartment corresponds to a charging circuit for charging one battery. In some embodiments, the battery charging cabinet 120 may include a main controller and a plurality of compartment controllers. The main controller is communicatively connected to the battery management platform 140 and the plurality of compartment controllers. Each compartment controller corresponds to one or more compartments and is used to manage or control one or more compartments. For more information about the battery charging cabinet 120 and its compartment controllers, see Figure 2 and its description.

[0026] The network 130 may include any suitable network that facilitates the exchange of information and / or data for the application scenario 100. In some embodiments, one or more components of the application scenario 100 (e.g., the battery charging cabinet 120, the server 140) may transmit information and / or data to one or more other components of the application scenario 100 via the network 130. For example, the battery management platform 140 may obtain the current version information of the battery firmware of the electric device 110 from the battery charging cabinet 120 via the network 130; it may also send the latest version information of the battery firmware of the electric device 110 and / or the latest version of the battery firmware to the battery charging cabinet 120 via the network 130. In some embodiments, the network 130 may be a wireless network (such as a wireless local area network (WLAN)). In some embodiments, the network may be of various topologies such as point-to-point, shared, centralized, etc., or a combination of multiple topologies.

[0027] The battery management platform 140 can be used to store and manage the battery firmware of multiple different electric devices 110. For example, it may include battery firmware of multiple versions (such as the latest version, historical versions) from different manufacturers or brands. In some embodiments, the battery management platform 140 can process the data and / or information obtained from the charging cabinet 120. For example, it can obtain a version upgrade detection request for the battery firmware of the battery charging cabinet 120 via the network 130 to determine whether the battery firmware of the target battery needs to be updated or upgraded; it can also send feedback information of the version upgrade detection request (such as whether an upgrade is required, target version information, and / or target battery firmware, etc.) via the network 130. For relevant content about the target battery and version upgrade detection, see Figure 4 and its description.

[0028] In some embodiments, the battery management platform 140 may be in the form of an Internet of Things platform or a cloud platform, which may be configured as a single server or a group of servers. The group of servers may be centralized or distributed. In some embodiments, the battery management platform 140 may be local or remote. The battery management platform 140 may be connected to the battery charging cabinet 120 via the network 130 to obtain information and / or data (such as an upgrade detection request for battery firmware, etc.). In some embodiments, the battery management platform 140 may be implemented on a cloud platform. By way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an internal cloud, a multi-layer cloud, etc. or any combination thereof.

[0029] The above description is for illustrative purposes only, and actual application scenarios can vary in various ways.

[0030] It should be noted that the application scenario 100 is provided only for illustrative purposes and is not intended to limit the scope of the present application. Those of ordinary skill in the art can make various modifications or changes based on the description of this specification. For example, the application scenario 100 may also include a display device or a terminal device for displaying information such as the upgrade progress of battery firmware. However, these changes and modifications will not depart from the scope of the present application.

[0031] Figure 2 is an exemplary schematic diagram of a battery charging cabinet shown in some embodiments of this specification.

[0032] As Figure 2 shown, the battery charging cabinet 120 may include a main controller 210, a compartment controller 220, and a first bus 230.

[0033] The main controller 210 may be used to manage the compartment controller 220. In some embodiments, the main controller 210 may summarize relevant information of one or more compartment controllers 220. For example, it may store relevant information about the storage space of each compartment controller 220 (such as remaining capacity), status information (such as whether it is performing a charging process on the battery, etc.), reference version information of the reference firmware, etc.

[0034] In some embodiments, the main controller 210 is communicatively connected to the battery management platform 140, and it may perform data communication with the battery management platform 140 via a network (such as the network 130). For example, the main controller 210 may obtain relevant data of the battery firmware (such as the battery firmware file, the latest version information of the battery firmware, etc.) from the battery management platform 140. The main controller 210 may perform data communication with the compartment controller 220 via the first bus 230. In some embodiments, the main controller 210 may be implemented based on the controller 300. For more information about the controller 300, see Figure 3 and its description.

[0035] The cell compartment controller 220 can be used to manage and / or control the battery connected to the cell compartment. For example, the cell compartment controller 220 can perform charging management on the battery and can also perform firmware update management on the battery, etc. In some embodiments, the cell compartment controller 220 can include one or more cell compartment controllers, such as Figure 2 As shown, the cell compartment controller 220 includes cell compartment controller 220-1, cell compartment controller 220-2... cell compartment controller 220-n. In some embodiments, each cell compartment controller can be used to correspond to one or more cell compartments, that is, each cell compartment controller can manage and / or control one or more cell compartments.

[0036] Among them, the cell compartment can be in the form of a window pane. For example, the battery charging cabinet 120 can include multiple rows and columns of cell compartments, and each cell compartment corresponds to a cell compartment controller 220. A user (such as the user of the electric device 110) can establish a charging connection between the battery and the battery charging cabinet 120 through the cell compartment, so as to charge the battery. In some embodiments, the cell compartment can be provided with various interfaces (such as a serial interface, an I / O interface, etc.) to adapt to the connection and charging of different types of batteries. In some embodiments, the cell compartment can also include, but is not limited to, components such as a compartment door, a signal indicator light, a label (such as No. 1, No. 2), etc.

[0037] In some embodiments, the cell compartment controller 220 can be implemented based on the controller 300.

[0038] The first bus 230 can refer to the link for data communication between the cell compartment controllers 220 and between the cell compartment controllers 220 and the main controller 210. The first bus 230 can realize the transmission of data, signals, program instructions, etc. between each cell compartment controller 220 and the main controller 210. Exemplarily, the cell compartment controller 220-1 can send battery-related information (such as battery basic information, battery firmware information, etc.) to the main controller 210 through the first bus 230; the main controller 210 can also send the latest battery firmware version information corresponding to the battery to the cell compartment controller 220-1 through the first bus 230.

[0039] In some embodiments, the first bus 230 can be, but is not limited to, a Controller Area Network (CAN) bus, a Serial Peripheral Interface (SPI) bus, a Universal Serial Bus (USB), etc.

[0040] In some embodiments, the battery charging cabinet 120 further includes a third bus 240. The third bus 240 can be used to communicatively connect each compartment controller 220 and the battery device 250. Among them, the battery device 250 can be batteries from different manufacturers (or different types) (such as battery device 1, battery device 2... battery device n). When a certain battery device 250 (such as battery device 1) is connected to the target compartment of the battery charging cabinet 120, the corresponding compartment controller 220 of the target compartment (such as compartment controller 220-1) can obtain battery-related information of the battery device 250 (such as basic battery information, battery firmware information, etc.) through the third bus 240. Among them, the third bus 240 includes but is not limited to a controller area network bus, a serial peripheral interface bus, a universal serial bus, etc.

[0041] In some embodiments, the battery charging cabinet 120 may further include other components (not shown in the figure). For example, it may include a display for presenting data or providing feedback. Exemplarily, the display can be used to display operation-related information. The operation-related information includes but is not limited to information such as currently available compartments, usage guides for the charging cabinet, advertisements, etc.

[0042] It should be noted that the above description of the battery charging cabinet 120 and its components is only for convenience of description and does not limit this specification to the scope of the illustrated embodiments. For example, the battery charging cabinet 120 may further include components such as a speaker. Such variations are all within the protection scope of this specification.

[0043] Figure 3 is an exemplary schematic diagram of a controller according to some embodiments of this specification.

[0044] As Figure 3 shown, the controller 300 may include a processor 310, a memory 320, a communication unit 330, an input unit 340, an output unit 350, and a second bus 360.

[0045] In some embodiments, the controller 300 can be disposed in a battery charging cabinet (such as the battery charging cabinet 120) to implement a main controller (such as the main controller 210) and / or one or more compartment controllers (such as the compartment controller 220).

[0046] In some embodiments, the processor 310 may process data and / or information obtained from other components of the controller 300, such as the memory 320, the communication unit 330, etc. For example, the processor 310 may obtain relevant information about the reference battery firmware from the memory 320 and store the target battery firmware in the storage space of the memory 320. As another example, the processor 310 may control the communication unit 330 via the second bus 360 to send a firmware update request to other controllers 300, such as the main controller 210 or other cell controllers 220.

[0047] In some embodiments, the processor 310 may include a microcontroller, a microprocessor, a central processing unit (CPU), a digital signal processor (DSP), a programmable logic device, and any circuit and processor capable of executing one or more functions, etc., or any combination thereof. It should be noted that the processor 310 may execute computer instructions (program code) and implement the methods or processes of some embodiments of this specification.

[0048] The memory 320 may store data and / or instructions. In some embodiments, the memory 320 may store data obtained from the processor 310, the communication unit 330, the input unit 340, and / or the output unit 350. For example, the memory 320 may store one or more battery firmwares, etc. In some embodiments, the memory 320 may store the data and / or instructions for the processor 310 to execute the exemplary methods described in this specification. For example, the memory 320 may store the instructions for the processor 310 to execute the methods shown in each flowchart.

[0049] In some embodiments, the memory 320 may include a mass storage device, a removable storage device, a volatile read-write memory, a read-only memory (ROM), etc., or any combination thereof. In some embodiments, the memory 320 may be a part of the processor 310.

[0050] The communication unit 330 is used for sending and receiving data. For example, the communication unit 330 may interact with the external (such as other cell controllers, the main controller, the battery management platform, etc.) via a network (such as network 130).

[0051] The input unit 340 may be used for data acquisition or sensing. It may be various types of sensors. In some embodiments, the input unit 340 may acquire relevant information about the battery connected to the cell (such as the model, the battery firmware version, etc.).

[0052] The output unit 350 includes various execution units. For example, the output unit 350 may include control devices (such as switching devices) for the compartment door of the cell, which are used to control the opening or closing of the compartment door of the cell.

[0053] The second bus 360 can be used as a link for data communication between controller components (such as the processor 310, the memory 320, the communication unit 330, the input unit 340, and / or the output unit 350) in the controller 300. It can enable the transmission of data, signals, program instructions, etc. between the controller components. Exemplarily, the processor 310 can obtain the reference version information of the reference firmware from the memory 320 through the second bus 360; for another example, the processor 310 can send signals and / or program instructions through the second bus 360 to control the output unit 350 to perform the operation of closing the bin door.

[0054] In some embodiments, the second bus 360 can include, but is not limited to, a CAN bus, an SPI bus, a universal serial bus, etc.

[0055] Figure 4 It is an exemplary flowchart of the management method of the battery charging cabinet shown in some embodiments of this specification.

[0056] In some embodiments, the process 400 can be executed by the management system. The process 400 includes the following steps.

[0057] Step 410, obtain the current version information of the firmware of the target battery through the first bay controller corresponding to the target bay, and send the current version information to the main controller.

[0058] The target battery refers to the battery placed in the charging cabinet for charging. The target bay refers to the bay in the charging cabinet where the target battery is placed, and it is connected to the target battery. For the relevant content of the bay, see Figure 2 and its description.

[0059] The first bay controller refers to the bay controller corresponding to the target bay. Among them, the correspondence between one or more bay controllers in the charging cabinet and multiple bays can be preset. For example, it can be determined based on a preset bay mapping relationship table. In some embodiments, the bay mapping relationship table can be stored in the storage device of the charging cabinet (such as the memory of the main controller), and it can include information such as the identification of the bay (such as a label) and the identification of the bay controller (such as a Mac address). When the user establishes a connection between the target battery and the target bay, the management system (such as the main controller of the charging cabinet) can determine the bay controller corresponding to the target bay (i.e., the first bay controller) through the bay mapping relationship table.

[0060] After the target battery is connected to the target cell, the first cell controller can obtain information related to the target battery (hereinafter referred to as battery-related information). The battery-related information may include basic information of the target battery (such as the brand, model, material, battery capacity, etc.), power information (such as the current power, remaining power, etc.). The battery-related information may also include battery firmware information. The battery firmware information may include the current version information of the battery firmware, the time of the last upgrade or update, etc.

[0061] Battery firmware may refer to software or programs that support the use of the battery. It can be used to control or manage the battery. For example, the battery firmware can control the charging and discharging processes of the battery, and can also be used to monitor operating parameters such as the power and temperature of the battery.

[0062] The battery firmware can be provided by suppliers (such as battery manufacturers, manufacturers of electric devices). For different batteries, their battery firmware can be different. In some embodiments, the battery firmware can be stored in the storage device of the management system (such as the storage device of the battery management platform, the memory of the main controller, the cell controller) in the form of a file, and it can be in various forms such as program files (such as upgrade files), compressed packages, etc.

[0063] Suppliers can upgrade or update the battery firmware according to actual needs (such as function addition, performance improvement, program code optimization, or program fault repair), so as to generate a new version of the battery firmware. The new version of the battery firmware can be used to upgrade or update the user's current battery firmware (that is, the battery firmware corresponding to the battery in the user's electric device), so that the user's battery can operate in the best state.

[0064] The version information includes various information related to the battery firmware version. For example, it may include the version number (such as 2.0, 3.1), release time (such as date, timestamp, etc.), release manufacturer (such as manufacturer A), battery type (such as brand, model), etc. The current version information refers to the information related to the current firmware version of the target battery. It can be understood that when a new version of the battery firmware is released, there are differences in version information (such as differences in version number, release time, etc.) between the current version of the battery firmware and the latest version of the battery firmware.

[0065] In some embodiments, the first cell controller can obtain the battery-related information of the target battery through the input unit, and send the current version information in the battery-related information to the main controller through the first bus. For the relevant content of the input unit, the first bus and the main controller, see Figure 3 and its description.

[0066] Step 420: Through the main controller, send the current version information to the battery management platform, receive the target version information sent by the battery management platform, and send the target version information to the first cell controller.

[0067] The target version information refers to the information related to the latest firmware version of the target battery. Similar to the current version information, the target version information may include the version number, release time, release manufacturer, battery type, etc. The firmware corresponding to the latest firmware version of the target battery can also be referred to as the target battery firmware.

[0068] In some embodiments, the main controller can send the current version information of the target battery to the battery management platform (such as the battery management platform 140) through a network (such as the network 130). After receiving the current version information, the battery management platform can perform version upgrade detection processing based on the current version information to determine whether the target battery needs to be firmware updated.

[0069] In some embodiments, the battery management platform can first obtain the battery firmware information of the firmware pool. The firmware pool refers to a collection of battery firmwares of multiple different manufacturers and / or battery firmwares of different types of batteries stored in the battery management platform (such as its storage device). Further, based on the current version information of the target battery and the battery firmware information in the firmware pool, it can be determined whether the target battery needs to be firmware updated (i.e., whether the current version is the latest version). For example, the latest version of the battery firmware released by the release manufacturer of the target battery or the latest version of the battery firmware of the same battery type as the target battery can be determined in the firmware pool; and the version information corresponding to the latest version of the battery firmware is compared and analyzed with the current version information to determine whether firmware update is required.

[0070] In some embodiments, the version comparison and analysis may include, but are not limited to, one or a combination of version number comparison, release time comparison, etc. For example, if the version number of the current version is lower than the version number of the latest version, and / or the release time of the current version is before the release time of the latest version, it means that the current version is not the latest version, that is, the battery firmware needs to be updated.

[0071] When it is determined that the battery firmware needs to be updated, the latest version of the battery firmware determined from the firmware pool is the target battery firmware, and its version information is the target version information. The battery management platform can send the target version information to the main controller through the network; when it is determined that the battery firmware does not need to be updated, the battery management platform can feedback an indication of not needing to update to the main controller (such as 0 indicating no update).

[0072] Step 430: Through the first cell controller, determine the reference version information corresponding to multiple reference battery firmware stored on the first cell controller, and based on the target version information and the reference version information, perform firmware update on the target battery.

[0073] The reference battery firmware refers to the set of battery firmware stored in the memory of the first cell controller, which may include battery firmware from different manufacturers and / or different versions. For example, the reference battery firmware may include Firmware A (such as the battery firmware corresponding to the battery of Manufacturer A), Firmware B (such as the battery firmware corresponding to the battery of Manufacturer B), Firmware C, etc.

[0074] In some embodiments, the reference battery firmware can be pre-configured. For example, the operator of the charging cabinet can pre-store the battery firmware of multiple different manufacturers in the memory of one or more cell controllers (such as the first cell controller) when the charging cabinet is put into use.

[0075] In some embodiments, the reference battery firmware can be obtained from the battery management platform (such as Battery Management Platform 140) or other cell controllers (such as the second cell controller) during the use of the charging cabinet. For the relevant content of the second cell controller, please refer to the following description.

[0076] The reference version information includes the version information corresponding to each battery firmware in the reference battery firmware. For example, the version number, release time, release manufacturer, battery type (such as brand, model), etc. of Firmware A.

[0077] In some embodiments, the first cell controller can implement firmware update based on the following steps.

[0078] Step 431: Based on the reference version information, determine whether the reference battery firmware stored in the first cell controller contains the target battery firmware that matches the target version information.

[0079] In some embodiments, the first cell controller can perform version comparison and analysis on the target version information and the reference version information to determine whether the reference battery firmware contains the target battery firmware (i.e., the latest version of the firmware corresponding to the target battery).

[0080] In response to the inclusion of the target battery firmware that matches the target version information, the first cell controller can execute the following Step 432 to perform firmware update on the target battery.

[0081] Step 432: Perform firmware update on the target battery based on the target battery firmware.

[0082] Firmware update refers to the process of updating the current firmware of the target battery to the latest version of the battery firmware. It can include, but is not limited to, various update methods such as full update (complete replacement or overwrite) of the current battery firmware with the target battery firmware, differential update (only updating the different parts), etc.

[0083] In some embodiments, the target version information may further include first verification information. The first cell controller may determine second verification information corresponding to the target battery firmware, and based on the first verification information and the second verification information, determine a verification result; in response to the verification result meeting the verification condition, perform firmware update on the target battery based on the target battery firmware.

[0084] The first verification information may include an original identity or signature representing the target battery firmware. It may be generated by the battery management platform when the target battery firmware is uploaded to the battery management platform, or it may be provided by a vendor (such as the release manufacturer) when the target battery firmware is released. In some embodiments, the first verification information may be an MD5 (Message-Digest Algorithm 5) value, which may be obtained by the battery management platform or the vendor after processing the target battery firmware using the MD5 algorithm.

[0085] It should be noted that the first verification information can be used to verify the consistency between the target battery firmware stored in the first cell controller and the original target battery firmware. It can also be generated in various ways according to actual needs. For example, it can also be a verification code generated according to a preset coding rule, or data (such as text, string) generated based on a preset encryption algorithm, etc.

[0086] The second verification information may represent the identity information of the target battery firmware in the first cell controller. In some embodiments, the first cell controller may process the target battery firmware stored in the first cell controller through the MD5 algorithm to obtain the second verification information.

[0087] In some embodiments, the first cell controller may compare the second verification information with the first verification information to determine the verification result. The verification condition may be that the second verification information is the same as the first verification information. It can be understood that when the second verification information is the same as the first verification information, it means that the target battery firmware in the first cell controller is consistent with the original / real target battery firmware. At this time, the first cell controller may perform firmware update on the target battery based on the target battery firmware.

[0088] If the verification result does not meet the verification condition, indicating that the target battery firmware in the first cell controller is unreliable (such as being tampered with, implanted with a virus, data missing, etc.), the first cell controller may execute steps 433 to 434 to achieve firmware update of the target battery.

[0089] In some embodiments of the present specification, the target battery firmware in the first cell controller is verified through the first verification information and the second verification information, avoiding the failure of the upgrade caused by the inconsistency between the target battery firmware and the original / true target battery firmware, thereby improving the accuracy and security of the firmware update.

[0090] In response to the non-existence of the target battery firmware that matches the target version information, the first cell controller may perform the following steps 433 to 434 to complete the firmware update of the target battery.

[0091] Step 433, obtain the target battery firmware from the main controller or the second cell controller. The second cell controller may be other cell controllers except the first cell controller, and it stores the target battery firmware.

[0092] In some embodiments, the first cell controller may send a firmware update request to other cell controllers, and the firmware update request includes the target version information. When a target battery firmware is stored in another cell controller, this cell controller may serve as the second cell controller and send the target battery firmware to the cell controller. If no target battery firmware is received from any other cell controller, the first cell controller may send a firmware update request to the main controller or the battery management platform to obtain the target battery firmware. For more descriptions of the foregoing embodiments, reference can be made to Figure 6 , which will not be elaborated here.

[0093] In some embodiments, the first cell controller may send a firmware update request to the main controller, and the firmware update request includes the target version information. The main controller may respond to the firmware update request. When the target battery firmware is stored in its memory, it may send the target battery firmware to the first cell controller. Or, in some embodiments, the main controller may also obtain the upgrade scheduling information, and based on the target version information and the upgrade scheduling information, determine the second cell controller that contains the target battery firmware from other cell controllers, and then send the relevant information of the second cell controller to the first cell controller, so that the first cell controller can obtain the target battery firmware from the second cell controller. For more descriptions of the foregoing embodiments, reference can be made to Figure 7 , which will not be elaborated here.

[0094] Step 434, store the target battery firmware as the reference battery firmware in the memory of the first cell controller.

[0095] After receiving the target battery firmware, the first cell controller may store it in the memory and, based on step 432, perform the firmware update of the target battery based on the target battery firmware.

[0096] In some embodiments of this specification, the target battery firmware can be preferentially obtained from the main controller or the second cell port controller instead of the battery management platform in the cloud, making full use of the local resources of the charging cabinet device, reducing the consumption of network resources, and at the same time, improving the efficiency of obtaining the target battery firmware, making the firmware update of the target battery faster and more effective.

[0097] In some embodiments, after the firmware of the target battery is updated, the first cell port controller can also determine the historical usage information of each reference battery firmware in the first cell port controller and update the historical usage information of each reference battery firmware.

[0098] The historical usage information can reflect the usage situation of each reference firmware in the first cell port controller being used for firmware update. The historical usage information corresponding to the reference battery firmware can include information such as the historical usage times, historical usage rate, historical usage proportion, most recent usage time, storage duration, etc.

[0099] In some embodiments, the first cell port controller can update the historical usage information of the reference battery firmware corresponding to the target battery firmware. For example, increment its historical usage times by 1; calculate the usage frequency (such as an average of n times per week, m times per month, etc.) in a preset time period (such as every week, every month, etc.) to update the historical usage rate; update the most recent usage time based on the moment when the firmware update is completed.

[0100] The first cell port controller can also update the storage duration of each reference battery firmware based on the moment when the current firmware update is completed. The storage duration can be the difference between the moment when the current firmware update is completed and the time when it was initially stored in the first cell port controller. The first cell port controller can also update its historical usage proportion based on the current historical usage times of each reference battery firmware. The historical usage proportion refers to the ratio of the historical usage times of the reference battery firmware to the total historical usage times of all reference battery firmware in the first cell port memory.

[0101] In some embodiments, the historical usage information can also include the estimated usage probability of each reference firmware. The estimated usage probability can reflect the possibility of the reference battery firmware being used for firmware update in the future. It can be in the form of a numerical value, and the larger the value, the higher its future usage probability and the greater the probability of being retained in the memory.

[0102] In some embodiments, the estimated usage probability can be comprehensively evaluated and determined based on various historical usage information. For example, the historical usage times, historical usage rate, most recent usage time, and storage duration can have different preset weight coefficients. By way of example only, the weight coefficients for the historical usage rate, most recent usage time, historical usage times, and storage duration can be set to decrease in sequence. The first cell controller can calculate the estimated usage probability of each reference firmware battery based on the historical usage information and the preset weight coefficients using algorithms such as weighted summation.

[0103] In some embodiments of the present specification, by updating the historical usage information of the reference battery firmware, a data basis is provided for the subsequent scheduling of the storage space of the first cell controller. At the same time, by estimating the usage probability, the future usage possibility of each reference battery firmware can be more accurately evaluated, so that when the storage space is tight, the reference firmware battery with a low usage probability can be more accurately removed, improving the utilization rate of the storage space and the update efficiency of the firmware.

[0104] In some embodiments, the first cell controller can also perform storage space scheduling on the memory based on the historical usage information. For more details, see Figure 5 and its description.

[0105] Figure 5 is an exemplary flowchart of a method for the first cell controller to store the target battery firmware according to some embodiments of the present specification.

[0106] In some embodiments, process 500 can be executed by a management system. As Figure 5 shown, process 500 includes the following steps.

[0107] Step 510, determine whether the storage space of the memory of the first cell controller meets the preset storage conditions.

[0108] The preset storage conditions can be determined according to the actual situation of the memory of the first cell controller. For example, it can include that the remaining storage space of the memory is greater than a preset space warning value. Among them, the space warning value can be in the form of a ratio of the remaining space to the total space (such as 10%) or a preset space threshold (such as 20M). In some embodiments, the preset storage conditions can be dynamically adjusted according to the size of the target battery firmware. For example, it can include that the remaining storage space is greater than the capacity requirement of the target battery firmware.

[0109] In response to the storage space meeting the preset storage conditions, step 521 can be executed. In response to the storage space not meeting the preset storage conditions, steps 522 and 523 can be executed.

[0110] Step 521, store the obtained target battery firmware in the memory of the first cell controller.

[0111] Step 522, delete at least one reference battery firmware in the first cell port controller.

[0112] In some embodiments, in response to not meeting the preset storage conditions, the first cell port controller may perform storage space scheduling processing. The storage space scheduling processing may include: obtaining the historical usage information of each reference battery firmware, and determining at least one reference battery firmware to be deleted based on the historical usage information.

[0113] In some embodiments, the reference battery firmware to be deleted needs to meet at least one of the following preset deletion conditions: being the historical version firmware of the target battery firmware (abbreviated as condition 1), having a historical usage rate less than the usage rate threshold (abbreviated as condition 2), having a historical usage frequency less than the usage frequency threshold (abbreviated as condition 3). The preset deletion may also include other conditions, for example, the storage duration is greater than the storage duration threshold (abbreviated as condition 4). In some embodiments, the above preset deletion conditions may be configured with priorities. For example, the priorities of condition 1, condition 4, condition 3, and condition 2 may decrease in sequence. The higher the priority, the more preferentially the reference battery firmware that meets the condition is deleted.

[0114] The historical version firmware is the firmware applicable to the target battery and earlier than the release of the target battery firmware. It can be understood that the firmware should be updated with the latest version, and the historical version firmware can be preferentially deleted. The usage rate threshold, the usage frequency threshold, and the storage duration threshold may be preset.

[0115] In some embodiments, the first cell port controller may also determine the target reference firmware based on the estimated usage probability of each reference battery firmware. The reference battery firmware with a lower estimated usage probability is more preferentially deleted. It can be understood that when one or more deletion conditions cannot determine the reference battery firmware to be deleted, the relative usage probability sizes among the reference firmwares can be considered for decision-making to further determine the reference battery firmware to be deleted. For the relevant content regarding the estimated usage probability, see Figure 4 and its description.

[0116] Step 523, store the obtained target battery firmware in the memory of the first cell port controller.

[0117] In some embodiments, the first cell port controller may store the target battery firmware in the memory of the first cell port controller, and this target battery firmware will become the reference battery firmware in the first port controller for firmware update of other batteries.

[0118] In some embodiments of this specification, scheduling the storage space of the first cell port controller based on the historical usage information of the reference battery firmware can improve the utilization efficiency of the storage space and avoid overly frequent and repeated storage and deletion operations of the reference firmware.

[0119] Figure 6 It is an exemplary flowchart of a method for a first cell controller to obtain a target battery firmware according to some embodiments of this specification.

[0120] In some embodiments, process 600 may be executed by a management system. As Figure 6 shown, process 600 includes the following steps.

[0121] Step 610, send a firmware update request including target version information to other cell controllers except the first cell controller among multiple cell controllers.

[0122] In some embodiments, the first cell controller may use various methods to send a firmware update request to multiple other cell controllers via the first bus to implement local firmware search. Local firmware search refers to the process in which the first cell controller requests and obtains the target battery firmware from other cell controllers or the main controller in this charging cabinet.

[0123] In some embodiments, the firmware update request includes a broadcast message sent by the first cell controller. The first cell controller may use the broadcast message mechanism to send a firmware update request to multiple other cell controllers simultaneously to implement local firmware search. The broadcast message may include target version information, relevant information of the broadcast source (i.e., the first cell controller) (such as identity identifiers such as Mac address, IP address, etc.).

[0124] After receiving the firmware update request, other cell controllers may determine the reference version information corresponding to multiple reference battery firmwares on their memories based on a method similar to step 430; and determine whether the reference battery firmware in their memories contains the target battery firmware that matches the target version information based on a method similar to step 431.

[0125] When one or more other cell controllers determine that they contain the target battery firmware pool, these cell controllers will send feedback information to the first cell controller. If only one other cell controller sends feedback information to the first cell controller, this cell controller is the second cell controller. If multiple other cell controllers send feedback information to the first cell controller, the second cell controller may be any one of them. For example, the second cell controller may be the cell controller that sends feedback information to the first cell controller first.

[0126] In some embodiments of this specification, through the broadcast message, the first cell controller can interact with multiple other cell controllers simultaneously. Compared with the method of polling multiple other cell controllers one by one, the efficiency of the first cell controller obtaining the target battery firmware from multiple other cell controllers is improved.

[0127] In some embodiments, the first cell controller may send firmware update requests to other cell controllers one by one, and stop sending firmware update information after receiving feedback information from a certain cell controller (i.e., the second cell controller).

[0128] After sending the firmware update request, the first cell controller may execute step 621 or 622 to obtain the target battery firmware.

[0129] Step 621: Determine the second cell controller from other cell controllers, and receive the target battery firmware from the second cell controller.

[0130] As described above, when a target battery firmware is stored in another cell controller, one of the cell controllers may be determined as the second cell controller. The second cell controller may send the target battery firmware to the first cell controller via the first bus.

[0131] In some embodiments, after receiving the target battery firmware, the first cell controller may also store the target battery firmware based on the method shown Figure 5 therein.

[0132] Step 622: In response to not receiving the target battery firmware from any other cell controller, send a firmware update request to the main controller, and receive the target battery firmware from the main controller.

[0133] In some embodiments, in response to not receiving the target battery firmware from any other cell controller, the first cell controller may send a firmware update request to the main controller. The main controller may obtain the target version information in the firmware update request, and it may determine whether the target battery firmware is included in its memory based on methods similar to step 430 and step 431.

[0134] When the target battery firmware is included, the main controller may send the target battery to the first cell controller via the first bus.

[0135] When the target battery firmware is not included, the main controller may obtain the target battery firmware matching the target version information from the battery management platform via the network and send it to the first cell controller.

[0136] In some embodiments of this specification, the first cell controller preferentially searches for and obtains the target battery firmware from other cell controllers to utilize the local storage resources. Compared with the traditional method of obtaining the target battery firmware from a remote server via the network, the method disclosed in this specification can reduce network bandwidth resources and can provide the battery firmware update service for users more quickly and efficiently.

[0137] Figure 7It is an exemplary flowchart of a method for another first cell port controller to obtain target battery firmware according to some embodiments of this specification.

[0138] Step 701, the first cell port controller sends a firmware update request to the main controller, and the firmware update request includes target version information.

[0139] In some embodiments, the first cell port controller can send a firmware update request to the main controller via the first bus.

[0140] Step 702, the main controller sends relevant information of the second cell port controller to the first cell port controller.

[0141] The relevant information of the second cell port controller may include unique identification information such as Mac address, device number, etc.

[0142] In some embodiments, after receiving the firmware update request from the first cell port controller, the main controller can obtain upgrade scheduling information and determine the second cell port controller based on the upgrade scheduling information. The upgrade scheduling information may include reference version information corresponding to the reference battery firmware on other cell port controllers. In some embodiments, the main controller can execute the method described in step 431, and based on the reference version information of other cell port controllers, determine whether the reference battery firmware stored in each other cell port controller contains the target battery firmware that matches the target version information.

[0143] When only one other cell port controller contains the target battery firmware, the main controller can directly use it as the second cell port controller. When multiple other cell port controllers contain the target battery firmware, the main controller can randomly select one of them as the second cell port controller, or can select one other cell port controller as the second cell port controller based on the status information of these cell port controllers. For example, the status information may include maintenance status (such as normal status, fault maintenance status, etc.), charging status (such as charging the battery, idle status, etc.), operating status (such as temperature), etc. The main controller can use the other cell port controller with a normal operating status and an idle charging status as the second cell port controller.

[0144] Step 703, the first cell port controller sends a firmware update request to the second cell port controller.

[0145] In some embodiments, after receiving the relevant information of the second cell port controller sent by the main controller, the first cell port controller can send a firmware update request to the second cell port controller via the first bus to obtain the target battery firmware.

[0146] Step 704, the second cell port controller sends the target battery firmware to the first cell port controller.

[0147] In some embodiments, after receiving the firmware update request from the first cell port controller, the second cell port controller may obtain the target battery firmware from multiple reference firmwares based on the target version information and the reference version information of the reference battery firmware, and send the target battery firmware to the first cell port controller.

[0148] In some embodiments, after receiving the target battery firmware sent by the second cell port controller, the first cell port controller may complete the firmware update operation for the target battery based on the target battery firmware by executing step 432.

[0149] In some embodiments of this specification, through the scheduling of the main controller, a unique second cell port controller can be determined for the first cell port controller, avoiding the problem that multiple other cell port controllers send the target battery firmware to the first cell port controller simultaneously, thereby avoiding unnecessary information interaction and the transmission of firmware files. At the same time, upgrade scheduling information is introduced, and the second cell port controller is determined by combining the status information of each other cell port controller, making the overall load of the charging cabinet more balanced and ensuring the normal operation of the charging cabinet and its multiple cell port controllers.

[0150] It should be noted that the above description of the process is only for illustration and example, and does not limit the scope of application of this specification. Those skilled in the art can make various corrections and changes to the process under the guidance of this specification. However, these corrections and changes are still within the scope of this specification.

[0151] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only an example and does not constitute a limitation of this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements, and corrections to this specification. Such modifications, improvements, and corrections are proposed in this specification, so such modifications, improvements, and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0152] At the same time, this specification uses specific terms to describe the embodiments of this specification. Such as "one embodiment", "an embodiment", and / or "some embodiments" mean a certain feature, structure, or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that the "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more at different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this specification can be appropriately combined.

[0153] In addition, unless explicitly stated in the claims, the order of the processing elements and sequences, the use of numerical and alphabetical characters, or the use of other names described in this specification are not used to limit the order of the processes and methods in this specification. Although some currently useful embodiments of the invention are discussed through various examples in the above disclosure, it should be understood that such details are for illustrative purposes only. The appended claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that conform to the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only through software solutions, such as installing the described system on existing servers or mobile devices.

[0154] Similarly, it should be noted that, in order to simplify the presentation of the disclosure in this specification and thus help the understanding of one or more embodiments of the invention, in the foregoing description of the embodiments of this specification, sometimes multiple features are grouped into one embodiment, drawing, or description thereof. However, this method of disclosure does not mean that the features required by the subject matter of this specification are more than those mentioned in the claims. In fact, the features of the embodiments are fewer than all the features of the individual embodiments disclosed above.

[0155] In some embodiments, numbers are used to describe the components and the quantity of attributes. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximate" or "substantially" in some examples. Unless otherwise stated, "about", "approximate" or "substantially" indicate that the said numbers allow a variation of ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, and such approximate values may vary according to the characteristics required by individual embodiments. In some embodiments, the numerical parameters should consider the specified significant digits and adopt the method of retaining the general number of digits. Although the numerical ranges and parameters used in some embodiments of this specification to confirm the breadth of their scope are approximate values, in specific embodiments, such numerical settings are made as precise as possible within the feasible range.

[0156] For each patent, patent application, patent application publication, and other materials cited in this specification, such as articles, books, specifications, publications, documents, etc., their entire contents are hereby incorporated into this specification by reference. This excludes the application history documents that are inconsistent with or conflict with the content of this specification, and also excludes the documents (currently or subsequently appended to this specification) that limit the broadest scope of the claims of this specification. It should be noted that if there are inconsistencies or conflicts between the descriptions, definitions, and / or uses of terms in the supplementary materials of this specification and the content described in this specification, the descriptions, definitions, and / or uses of terms in this specification shall prevail.

[0157] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of this specification. Therefore, by way of example and not limitation, alternative configurations of the embodiments of this specification may be regarded as consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly presented and described in this specification.

Claims

1. A system for upgrading battery firmware using a charging cabinet, characterized in that, It includes a main controller and multiple cell controllers, where: The main controller is communicatively connected to a battery management platform and the multiple cell controllers; Each of the cell controllers corresponds to one or more cells of the battery charging cabinet, and each of the cell controllers includes a memory for storing multiple reference battery firmware; In response to a target battery establishing a connection with a target cell in the battery charging cabinet, The first cell controller corresponding to the target cell is configured to obtain the current version information of the firmware of the target battery and send the current version information to the main controller; The main controller is configured to send the current version information to the battery management platform, receive the target version information sent by the battery management platform, and send the target version information to the first cell controller; The first cell controller is further configured to determine the reference version information corresponding to the multiple reference battery firmware stored on the first cell controller, and based on the target version information and the reference version information, perform firmware update on the target battery.

2. The system according to claim 1, characterized in that, The performing firmware update on the target battery based on the target version information and the reference version information includes: Based on the reference version information, determining whether the reference battery firmware stored on the first cell controller includes a target battery firmware that matches the target version information; In response to determining that the target battery firmware is included, performing firmware update on the target battery based on the target battery firmware; In response to determining that the target battery firmware is not included, obtaining the target battery firmware from the main controller or a second cell controller, storing the target battery firmware as a reference battery firmware in the memory of the first cell controller, and performing firmware update on the target battery based on the target battery firmware.

3. The system according to claim 2, characterized in that, The target version information further includes first verification information, The performing firmware update on the target battery based on the target battery firmware includes: Determining second verification information corresponding to the target battery firmware; Based on the first verification information and the second verification information, determining a verification result; In response to the verification result meeting the verification condition, performing firmware update on the target battery based on the target battery firmware.

4. The system according to claim 2, characterized in that, The storing the target battery firmware as a reference battery firmware in the memory of the first cell controller includes: Determining whether the storage space of the memory of the first cell controller meets a preset storage condition; In response to determining that the storage space meets the preset storage condition, storing the obtained target battery firmware in the memory of the first cell controller; or In response to determining that the storage space does not meet the preset storage condition, deleting at least one reference battery firmware in the first cell controller and storing the obtained target battery firmware in the memory of the first cell controller.

5. The system according to claim 4, characterized in that, The at least one reference battery firmware to be deleted meets at least one of the following preset deletion conditions: It is a historical version firmware of the target battery firmware; The historical usage rate is less than the usage rate threshold; The historical usage times are less than the usage times threshold.

6. The system according to claim 2, characterized in that, The first cell controller is further configured to: After performing a firmware update on the target battery, Determine the historical usage information of each of the reference battery firmwares in the first cell controller; Update the historical usage information of each of the reference battery firmwares.

7. The system according to claim 2, characterized in that, Obtaining the target battery firmware from the master controller or the second cell controller includes: Sending a firmware update request to other cell controllers in the plurality of cell controllers except the first cell controller, the firmware update request including the target version information; Determining the second cell controller from the other cell controllers and receiving the target battery firmware from the second cell controller; or In response to not receiving the target battery firmware from any other cell controller, sending the firmware update request to the master controller and receiving the target battery firmware from the master controller.

8. The system according to claim 2, wherein Obtaining the target battery firmware from the master controller or the second cell controller further includes: Sending a firmware update request to the master controller, the firmware update request including the target version information; In response to the firmware update request, the master controller is configured to: Obtain upgrade scheduling information, the upgrade scheduling information including the reference version information corresponding to the reference battery firmwares on other cell controllers in the plurality of cell controllers except the first cell controller; Based on the target version information and the upgrade scheduling information, determine the second cell controller including the target battery firmware; Send the relevant information of the second cell controller to the first cell controller so that the first cell controller can obtain the target battery firmware from the second cell controller.

9. A method for upgrading battery firmware using a charging cabinet, wherein Applied to the system as claimed in claim 1, including: Obtaining the current version information of the target battery through the first cell controller corresponding to the target cell and sending the current version information to the master controller; Through the master controller, sending the current version information to the battery management platform, receiving the target version information sent by the battery management platform, and sending the target version information to the first cell controller; Through the first cell controller, determining the reference version information corresponding to the plurality of reference battery firmwares stored on the first cell controller, and performing a firmware update on the target battery based on the target version information and the reference version information.

10. A computer-readable storage medium, wherein Stores instructions that, when executed by the processors of the master controller and / or the cell controllers, cause the processors to execute the method as claimed in claim 9.

Images