Battery management system firmware update system and related method

Abstract

A battery management system according to one embodiment disclosed in this document includes one or more battery modules, one or more battery module management devices connected to each of the battery modules, and a battery pack management device having firmware embedded therein and managing the one or more battery module management devices, wherein the battery pack management device is configured to divide the firmware to generate firmware packet information and transmit the divided firmware packet information to the one or more battery module management devices, and the battery module management device is configured to monitor a status of the connected battery modules and transmit the monitored battery data information to the battery pack management device.

Description

[Technical field]

[0001] The present invention claims the benefit of priority based on Korean Patent Application No. 10-2021-0132752 filed on October 6, 2021, and all contents disclosed in the documents of the Korean patent application are incorporated as part of this specification.

[0002] The embodiments disclosed herein relate to a firmware update system and related method in such a battery management system. [Background technology]

[0003] An energy storage system (ESS) is a device that improves the efficiency of power usage by storing generated electricity in a storage device such as a battery and supplying it when power is needed. The ESS includes a battery that stores electricity and a configuration for efficiently managing and controlling the battery. Among them, a battery management system (BMS) measures battery status information such as temperature, current, and voltage using various sensors connected to a battery module, calculates various data, and thereby calculates data on dangerous problems such as overcharging and over-discharging that may occur when charging and / or discharging the battery, and controls the temperature, current, voltage, etc. according to the battery status to maintain the battery in a stable state.

[0004] The battery management system (BMS) may be composed of hardware that manages the operation of the battery and software that controls the hardware. Therefore, for more stable operation, it is necessary to update the software of the battery management system (BMS). The battery management system (BMS) may be composed of a battery module management device that monitors the state of each battery module, and a battery pack management device that manages the battery module management device. When the software of the battery management system (BMS) is updated, the software of the battery pack management device is updated, and the battery pack management device transmits update information to each battery module management device. In addition, each battery module management device transmits status data of the battery modules connected thereto to the battery pack management device so that the battery management system (BMS) can be maintained in a stable state, and the information can be collected.

[0005] The matters described above as the background art are intended only to enhance understanding of the background of the present invention, and should not be accepted as admitting that they constitute prior art known to those of ordinary skill in the art. Summary of the Invention [Problem to be solved by the invention]

[0006] When updating the battery management system, the battery pack management device transmits updated firmware to one or more battery module management devices. The one or more battery module management devices monitor the states of the battery modules connected thereto, and transmit the monitored battery data information to the battery pack management device. However, while the battery pack management device transmits the updated firmware to the one or more battery module management devices, the battery module management devices cannot transmit the monitored battery data information to the battery pack management device, so there is a possibility that some battery data information will be lost. If the size of the firmware update information stored in the battery pack management device is sufficiently large, the amount of battery data information that cannot be collected and is lost may be enormous, which may cause problems in the operation of the battery management system.

[0007] When updating the battery management system, the battery pack management device transmits the updated firmware to one or more battery module management devices. In this case, if some of the battery module management devices have poor communication with the battery pack management device, that is, if the battery module management device is in a communication shadow area with respect to the battery pack management device, a situation may occur in which the battery module management device is unable to receive the updated firmware. [Means for solving the problem]

[0008] A battery management system according to one embodiment disclosed in this document includes one or more battery modules, one or more battery module management devices connected to each of the battery modules, and a battery pack management device having firmware embedded therein and managing the one or more battery module management devices, wherein the battery pack management device is configured to divide the firmware to generate firmware packet information and transmit the divided firmware packet information to the one or more battery module management devices, and the battery module management device is configured to monitor a status of the connected battery modules and transmit the monitored battery data information to the battery pack management device.

[0009] In one embodiment, the battery pack management device may be further configured to transmit the undivided firmware to the one or more battery module management devices when a batch firmware download command is input according to a method specified in the battery pack management device.

[0010] According to an embodiment, the battery pack management device may be further configured to store length information of the firmware packet information sent to the battery module management device.

[0011] According to an embodiment, the battery module management device may be further configured to transmit the monitored battery data information to at least a portion of the remaining battery module management devices.

[0012] In one embodiment, the battery module management device may be configured to generate encoding information by encoding both the monitored battery data information and the received divided firmware packet information, and to transmit the encoding information to at least a portion of the remaining battery module management devices.

[0013] According to one embodiment, the battery module management device may be configured to verify the segmented firmware packet information using the battery data information and the encoding information received from another battery module management device.

[0014] An operating method of a battery management system according to one embodiment disclosed in this document may include an operation of dividing firmware built into a battery pack management device and generating divided firmware packet information, an operation of the battery pack management device transmitting the divided firmware packet information to one or more battery module management devices, and an operation of the one or more battery module management devices monitoring the status of the battery modules connected thereto and transmitting the monitored battery data information to the battery pack management device.

[0015] An operating method of a battery management system according to one embodiment may further include an operation of transmitting the undivided firmware to the one or more battery module management devices when a batch firmware download command is input in accordance with a specified method in the battery pack management device.

[0016] The method of operating a battery management system according to an embodiment may further include storing, by the battery pack management device, length information of the firmware packet information transmitted to the battery module management device.

[0017] The method of operating the battery management system according to an embodiment may further include an operation of the battery module management device transmitting the monitored battery data information to at least some of the remaining battery module management devices.

[0018] An operating method of a battery management system according to an embodiment may further include an operation of the battery module management device encoding the monitored battery data information and the received divided firmware packet information to generate encoding information, and an operation of transmitting the encoding information to at least a portion of the remaining battery module management devices.

[0019] An operating method of a battery management system according to an embodiment may further include an operation in which the battery module management device checks the divided firmware packet information using the battery data information and the encoding information received from another battery module management device.

[0020] A battery management system according to one embodiment disclosed in this document includes one or more battery modules, one or more battery module management devices connected to each of the battery modules, a battery pack management device having firmware built in and managing the one or more battery module management devices, and a control unit connected to the battery module management device and the battery pack management device, wherein the control unit can be configured to control the battery pack management device to divide the firmware to generate firmware packet information and to control the divided firmware packet information to be transmitted to the one or more battery module management devices, and to control the battery module management device to monitor a status of the connected battery modules and to transmit the monitored battery data information to the battery pack management device.

[0021] In one embodiment, the control unit may be further configured to control the battery pack management device to transmit the undivided firmware to the one or more battery module management devices when a batch firmware download command is input according to a method specified in the battery pack management device.

[0022] According to an embodiment, the controller may be further configured to control the battery pack management device to store length information of the firmware packet information transmitted to the battery module management device.

[0023] According to an embodiment, the control unit may be further configured to control the battery module management devices to transmit the monitored battery data information to at least a portion of the remaining battery module management devices.

[0024] In one embodiment, the control unit may be further configured to control the battery module management devices to generate encoding information by encoding both the monitored battery data information and the received divided firmware packet information, and to transmit the encoding information to at least a portion of the remaining battery module management devices.

[0025] In one embodiment, the control unit may be further configured to control the battery module management device to confirm the divided firmware packet information using the battery data information and the encoding information received from another battery module management device. Effect of the Invention

[0026] According to the embodiments disclosed herein, the battery management system can be updated without losing battery data information, even while the battery module is in operation.

[0027] According to the embodiments disclosed in this document, when updating a battery management system, even if there is a battery module management device that has poor communication with the battery pack management device, the update of the battery management system can proceed normally by directly or indirectly receiving firmware packet information received by another battery module management device that has normal communication with the battery pack management device and checking the firmware packet information. In addition, this document may provide a variety of other benefits that may be perceived directly or indirectly. [Brief description of the drawings]

[0028] [Figure 1] FIG. 1 is a block diagram showing the configuration of a typical battery pack including a battery management device according to an embodiment disclosed herein. [Diagram 2] 1 illustrates a battery management system according to one embodiment disclosed herein. [Diagram 3]1 is an operational flowchart illustrating an operation method of a battery management system according to an embodiment disclosed herein. [Figure 4] 1 is an operational flowchart illustrating an operation method of a battery management system according to an embodiment disclosed herein. [Diagram 5] FIG. 2 is a diagram illustrating the progress of data communication according to time in a battery management system according to an embodiment disclosed in this document. [Figure 6] FIG. 2 is a diagram illustrating the progress of data communication according to time in a battery management system according to an embodiment disclosed in this document. [Figure 7] FIG. 1 is a functional block diagram of a battery management system according to one embodiment disclosed herein. [Figure 8] 1 illustrates an operational flow chart for consuming battery energy according to one embodiment disclosed herein.In connection with the description of the drawings, the same or similar reference numerals may be used for the same or similar components. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] Various embodiments of the present invention will now be described with reference to the accompanying drawings, however, it should be understood that this is not intended to limit the present invention to the specific embodiments, but rather includes various modifications, equivalents, and / or alternatives of the embodiments of the present invention.

[0030] The various embodiments and terms used in this document are not intended to limit the technical features described in this document to a specific embodiment, but should be understood to include various modifications, equivalents, or alternatives of the embodiment. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the said item, unless the relevant context clearly indicates otherwise.

[0031] In this document, each phrase such as "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C" may include any one or all possible combinations of the items listed with that phrase. Terms such as "first," "second," "first," "second," "A," "B," "(a)," or "(b)" may be used merely to distinguish the element from other elements and do not limit the element in other respects (e.g., importance or order) unless specifically stated to the contrary.

[0032] In this document, when a (e.g., first) component is referred to as being "coupled," "coupled," or "connected" to another (e.g., second) component, with or without the terms "functionally" or "communicatively," or when a reference is made to "coupled" or "connected," this means that the component may be coupled to the other component directly (e.g., by wire), wirelessly, or through a third component.

[0033] According to an embodiment, the method according to the various embodiments disclosed herein may be provided in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read only memory (CD-ROM)) or distributed online (e.g., downloaded or uploaded) via an application store or directly between two user devices. In case of online distribution, at least a part of the computer program product may be at least temporarily stored or temporarily generated in a machine-readable storage medium such as a memory of a manufacturer's server, an application store server, or an intermediary server.

[0034] According to various embodiments, each of the components described above (e.g., modules or programs) may include one or more entities, and some of the entities may be located separately in other components. According to various embodiments, one or more of the components described above may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., modules or programs) may be integrated into one component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the multiple components before the integration. According to various embodiments, operations performed by modules, programs, or other components may be performed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be performed in a different order, omitted, or one or more other operations may be added.

[0035] FIG. 1 is a block diagram showing the configuration of a typical battery pack including a battery management device according to an embodiment disclosed herein. 1 is a schematic diagram of a battery control system 1 including a battery pack 10 according to an embodiment disclosed herein and a host controller 20 included in the host system. In this case, the battery pack 10 shown in FIG. 1 may correspond to a configuration of a battery management system 100 disclosed herein.

[0036] 1, the battery pack 10 may include a plurality of battery modules 110, a sensor 14, a switching unit 16, and a battery pack management device 130. In this case, the battery pack 10 may include a plurality of battery modules 110, sensors 14, switching units 16, and battery pack management devices 130.

[0037] Each of the battery modules 110 may include at least one small battery cell that is chargeable and dischargeable. In this case, the battery modules 110 may be connected in series or in parallel.

[0038] The sensor 14 can detect a current flowing through the battery pack 10. At this time, a detection signal can be transmitted to the battery pack management device 130. The switching unit 16 is connected in series to the (+) terminal side or the (-) terminal side of the battery module 110 and can control the flow of charge / discharge current of the battery module 110. For example, the switching unit 16 can use at least one relay, electromagnetic contactor, etc. depending on the specifications of the battery pack 10.

[0039] The battery pack management device 130 can monitor the voltage, current, temperature, etc. of the battery pack 10 and control and manage it to prevent overcharging and over-discharging, and can include, for example, an RBMS (Rack Battery Management System).

[0040] The battery pack management device 130 is an interface that receives input of measured values ​​of the various parameters described above, and may include a plurality of terminals, a circuit connected to these terminals and capable of processing the input values, etc. The battery pack management device 130 may also control the ON / OFF of the switching unit 16, for example, a relay or a contactor, and may be connected to the battery modules 110 to monitor the status of each battery module 110.

[0041] The upper controller 20 can transmit a control signal for controlling the battery module 110 to the battery pack management device 130. As a result, the operation of the battery pack management device 130 can be controlled based on the control signal applied from the upper controller 20. The battery module 110 may be included in an ESS (Energy Storage System). In this case, the upper controller 20 may be a controller of a battery bank (BBMS, Bank Battery Management System) including a plurality of battery packs 10, or an ESS controller that controls the entire ESS including a plurality of banks. However, the battery pack 10 is not limited to such an application.

[0042] FIG. 2 illustrates a battery management system according to one embodiment disclosed herein. Referring to FIG. 2, the battery management system 100 may include one or more battery modules 110, one or more battery module management devices 120 that manage the battery modules, and a battery pack management device 130 that manages the battery module management devices. According to an example disclosed in this document, the number of battery module management devices and battery modules is not limited to the number shown in the drawing, and the number may be changed by adding or removing battery module management devices and battery modules. As an example, the battery module 110 may correspond to a battery module for a vehicle. As an example, the battery pack management device 130 may include firmware (F / W). As an example, the firmware included in the battery pack management device 130 may correspond to firmware for a vehicle. As an example, data may be transmitted or received between the battery pack management device 130 and the battery module management device 120, and one or more battery module management devices 120 may transmit or receive data to each other. In this case, in order to transmit or receive data according to one example disclosed in this document, the battery pack management device 130 and one or more battery module management devices 120 may be connected to each other via wired or wireless communication, and the one or more battery module management devices 120 may also be connected to each other via wired or wireless communication.

[0043] According to an example disclosed herein, when the battery management system 100 is updated, the firmware built in the battery pack management device 130 may be updated. In this case, the battery pack management device 130 may transmit all or a part of the updated firmware to one or more battery module management devices 120 to update the battery module management devices 120. As an example, the battery pack management device 130 may transmit only information corresponding to an updated part of the updated firmware to one or more battery module management devices 120. According to an example disclosed herein, the battery pack management device 130 may transmit all or a part of the updated firmware to the battery module management device 120 in a lump. As another example, the battery pack management device 130 may generate firmware packet information by dividing the firmware to be transmitted, and transmit the divided firmware packet information to the battery module management device 120 several times.

[0044] One or more battery module management devices 120 may be connected to one or more battery modules 110, respectively, and monitor the status of the battery modules 110. For example, the status information of the battery module 110 monitored by the battery module management device 120 may correspond to battery-related information such as the battery temperature (T), voltage (V), current (I), state of charge (SOC), SOH (State Of Health), or SOP (State Of Power). For example, the battery module management device #1 (121) may be connected to the battery module #1 (111) and monitor the status of the battery module #1 (111). For example, the battery module management device #2 (122) may be connected to the battery module #2 (112) and monitor the status of the battery module #2 (112). For example, the battery module management device #3 (123) may be connected to the battery module #3 (113) and monitor the status of the battery module #3 (113). As an example, the battery module management device #4 (124) may be connected to the battery module #4 (114) and monitor the status of the battery module #4 (114). According to an example disclosed herein, the number of battery module management devices and battery modules is not limited to the number shown in the drawings, and the number may be changed by adding or removing battery module management devices and battery modules. Thus, even when the number of battery module management devices included in the battery management system 100 is changed, the operation according to the example disclosed herein can be performed in a similar manner.

[0045] According to an example disclosed herein, when the battery module management devices 120 monitor the battery modules 110 connected thereto, the battery module management devices 120 can transmit the monitored battery data information to the battery pack management device 130. As an example, the battery module management devices 120 can further transmit the battery data information of the battery modules connected thereto to at least some of the remaining battery module management devices 120. According to a specific example disclosed herein, the battery module management device #1 (121) can transmit the battery data information of the battery module #1 (111) to the battery pack management device 130. According to a specific example disclosed herein, the battery module management device #1 (121) can further transmit the battery data information of the battery module #1 (111) to at least one of the remaining battery module management devices #2 (122), #3 (123), and #4 (124). As an example, battery module management device #2 (122), #3 (123), or #4 (124) may operate in a manner similar to battery module management device #1 (121) according to an example disclosed herein.

[0046] 3 is a flowchart showing an operation method of a battery management system according to an embodiment disclosed in the present document. The operation of the flowchart shown below can be realized by the battery management system or a configuration (e.g., a control unit 310) included in the battery management system.

[0047] Referring to FIG. 3, according to one embodiment disclosed herein, the battery management system 100 can perform an operation of transmitting firmware built into the battery pack management device 130 to one or more battery module management devices 120 (S260), and according to other embodiments disclosed herein, can perform an operation of dividing the firmware built into the battery pack management device 130 to generate firmware packet information (S210), and an operation of communicating between the battery pack management device 130 and one or more battery module management devices 120, such as by transmitting and receiving data between the battery pack management device 130 and one or more battery module management devices 120 (S220).

[0048] According to one embodiment disclosed in this document, the operation (S260) of the battery management system 100 transmitting firmware embedded in the battery pack management device to one or more battery module management devices can be performed when there is an input operation (S200 or S250) of a batch firmware download command from the user to the battery management system 100.

[0049] The operation S200 may correspond to an operation in which the battery management system 100 according to an embodiment disclosed herein is changed from a non-operation (off) step to an operation (on) step, or in which firmware built in the battery pack management device 130 is updated in the operation (on) step, and the battery management system 100 receives an input from a user as to whether or not to collectively download the updated firmware. As an example, when a user inputs a command to collectively download the updated firmware to the battery management system 100 through the operation S200, the battery pack management device 130 may transmit the whole or a part of the updated firmware to one or more battery module management devices 120. In this case, as an example disclosed herein, when the battery pack management device 130 transmits only a part of the firmware to one or more battery module management devices 120, the transmitted part of the firmware may correspond to an updated part of the entire firmware configuration.

[0050] In the operation S200 according to an example disclosed herein, if the battery management system 100 determines that it has not received an input of a batch firmware download command, the battery pack management device 130 may divide the updated firmware to generate firmware packet information (S210). As an example, in the operation S210, the battery pack management device may divide all or a part of the firmware that has been updated to generate firmware packet information. As an example, when a part of the firmware that has been updated is divided to generate firmware packet information, the part of the firmware may correspond to firmware information corresponding to the part that has been updated from the existing firmware.

[0051] According to an example disclosed herein, the battery pack management device 130 can transmit firmware packet information generated by the operation of S210 to one or more battery module management devices 120 several times, and the battery module management devices 120 can transmit battery data information of the monitored battery modules to the battery pack management device 130 or further transmit it to the remaining battery module management devices, thereby performing a communication operation related to data transmission and reception between the battery pack management device and one or more battery module management devices (S220). A detailed description of the operation of S220 will be given later with reference to FIG. 4.

[0052] After performing the operation S220 according to an example disclosed herein, the battery management system 100 may further perform an operation of determining whether a data transmission interruption signal is present from inside or outside the system (S230). As an example, the data transmission interruption signal in the operation S230 may correspond to a conversion signal input from a user to a non-operational (off) step of the battery management system 100. As another example, the data transmission interruption signal in the operation S230 may correspond to a signal notifying that all of the divided firmware packet information has been transmitted from the battery pack management device 130 to the battery module management device 120. As an example, if the battery management system 100 determines that no data transmission interruption signal is present, the battery pack management device and one or more battery module management devices may repeat the operation S220.

[0053] According to an example disclosed herein, when the battery management system 100 determines that a data transmission interruption signal exists, the battery management system 100 may perform an operation of determining whether or not all of the divided firmware packet information has been transmitted from the battery pack management device 130 to the battery module management device 120 (S240). When it is determined in the operation of S240 that some or all of the divided firmware packet information has not been transmitted to the battery module management device 120, the battery management system 100 may receive an input of a command as to whether or not to download the updated firmware in a batch from the user (S250). As an example, when it is determined in the operation of S240 that all of the divided firmware packet information has been transmitted to the battery module management device 120, the battery management system 100 may end the firmware update progress or may convert to a non-operating (off) step to shut down the system.

[0054] In the operation S250 according to an example disclosed herein, if the battery management system 100 determines that a batch firmware download command has been input from the user, it may perform an operation (S260) of transmitting firmware stored in the battery pack management device 130 to one or more battery module management devices 120. As an example, if the operation S250 determines that a batch firmware download command has not been input, the battery pack management device 130 may further store length information of the transmitted firmware packet information (S270). As another example, if the operation S250 determines that a batch firmware download command has not been input, the battery module management device 120 may further store length information of the received firmware packet information (S270). According to an example disclosed herein, even if the battery management system 100 is terminated without completing transmission of firmware packet information to the battery module management device 120, by further storing length information of the transmitted or received firmware packet information (S270), it is possible to transmit only existing firmware packet information that has not been completely transmitted when the battery management system 100 starts operating again. At this time, it is advantageous in that firmware packet information that has already been transmitted can be prevented from being unnecessarily transmitted repeatedly.

[0055] The S260 operation according to an example disclosed herein may correspond to an operation of transmitting all or a part of the firmware built in the battery pack management device 130 to one or more battery module management devices 120. As an example, the S260 operation may correspond to an operation of the battery pack management device 130 transmitting all of the updated firmware. As an example, the S260 operation may correspond to an operation of the battery pack management device 130 transmitting firmware information corresponding to a part updated from the existing firmware (i.e., a part of the updated firmware). As an example, the S260 operation may correspond to an operation of collectively transmitting all or a part of the firmware including the transmitted firmware packet information after the battery pack management device 130 has transmitted a part of the divided firmware packet information, or an operation of collectively transmitting the remaining firmware packet information that has not been transmitted.

[0056] 4 is an operation flowchart showing an operation method of a battery management system according to an embodiment disclosed herein. The operation shown in FIG. 4 may correspond to a specific example of the operation S220 of FIG. 3. The battery management system may repeatedly perform the operation S220 according to an embodiment disclosed herein, and the operation shown in FIG. 4, which may correspond to a specific example of the operation S220, may also be repeatedly performed in a similar manner.

[0057] 4, the operating method of the battery management system may include an operation of the battery pack management device 130 dividing the updated firmware to generate firmware packet information (S210), and an operation of the battery pack management device 130 transmitting the firmware packet information generated by the operation of S210 to one or more battery module management devices 120 (S221). According to an example disclosed in this document, when the firmware to be transmitted by the battery pack management device is divided into a total of N pieces of firmware packet information (where N is a natural number of 2 or more), the battery pack management device 130 can transmit each piece of firmware packet information to one or more battery module management devices 120 N times (sequence) according to a specified sequence.

[0058] As an example, the order of transmitting each piece of firmware packet information to one or more battery module management devices 120 while the S221 operation is repeated may be specified to be sequentially transmitted according to the order in which the firmware packet information is divided. As an example, the order of transmitting each piece of firmware packet information to one or more battery module management devices 120 while the S221 operation is repeated may be specified to be transmitted in the order from largest to smallest according to the size of the firmware packet information, or from smallest to largest. As an example, the order of transmitting each piece of firmware packet information to one or more battery module management devices 120 while the S221 operation is repeated may be specified to be in accordance with a method arbitrarily specified by a user. According to an example disclosed in this document, firmware packet information divided into a total of N pieces (where N is 2 or more) may be divided into each piece of firmware packet information P1, P2, P3, ..., P4, ..., P5, ..., P6, ..., P7, ..., P8, ..., P9, ..., P10, ..., P11, ..., P12, ..., P13, ..., P14, ..., P15, ..., P16, ..., P17, ..., P18, ..., P19, ..., P20, ..., P21, ..., P22, ..., P23, ..., P24, ..., P25, ..., P26, ..., P27, ..., P28, ..., P29, ..., P30, ..., ..., P31, ..., ..., P32, ... ... N It can be referred to as:

[0059] According to an example disclosed in this document, the battery management system operates by: the battery pack management device 130 reads each firmware packet information (e.g., P1, P2, P3, ..., P N) firmware packet information (for example, P m , where 1≦m≦N) to one or more battery module management devices 120, the one or more battery module management devices 120 may include an operation of transmitting battery data information of the monitored battery modules to the battery pack management device 130 in a specified order (S222). As an example, the battery module management devices #1 (121), #2 (122), #3 (123), or #4 (124) may transmit each of the battery data information monitored for the battery modules #1 (111), #2 (112), #3 (113), or #4 (114) connected thereto, respectively, as D m 1, D m 2. D m 3, or D m In the battery management system according to an embodiment disclosed in this document, the battery pack management device 130 performs the operation S222 by transmitting the first firmware packet information (e.g., P m ), then the second firmware packet information (e.g., P m+1 In this case, while each divided firmware packet information is being transmitted, one or more battery module management devices 120 may monitor the battery data information (e.g., D m 1, D m 2. D m 3, or D m 4) to the battery pack management device 130, it can have an advantage in that it can reduce the amount of battery data information of each battery module 110 that may be lost while the battery management system 100 is updating collectively.

[0060] The operation method of the battery management system may be, according to an embodiment disclosed herein, a battery module management device 120 monitors each of the connected battery modules 110 to obtain battery data information (e.g., D m 1, D m 2. D m 3, or D mAccording to a specific example disclosed herein, the battery module management device #1 (121) may further include an operation of transmitting battery data information (e.g., D m The method may further include an operation of transmitting the battery data information (e.g., D1 data) of the monitored battery module #2 (112), #3 (123), or #4 (124) to at least one of the remaining battery module management devices, that is, battery module management devices #2 (122), #3 (123), or #4 (124). As various examples of the operation of S223, the battery module management devices #2 (122), #3 (123), or #4 (124) may each operate in a manner similar to the battery module management device #1 (121) according to an example disclosed herein, and each transmit battery data information (e.g., D1 data) of the monitored battery module #2 (112), #3 (113), or #4 (114). m 2. D m 3, or D m 4 data) to at least some of the remaining battery module management devices.

[0061] The operation method of the battery management system may be, according to an embodiment disclosed herein, a battery module management device 120 monitors each of the connected battery modules 110 to obtain battery data information (e.g., D m 1, D m 2. D m 3, or D m 4 data), and firmware packet information (e.g., P m As a specific example of the operation of S224, the battery pack management device 130 may transmit the divided firmware packet information (e.g., P m ) is transmitted, the battery module management device #1 (121) transmits the battery data information (e.g., D m1 data), and received firmware packet information (e.g., P m ) to encode the encoding information I m As various examples of the operation of S224, the battery module management device #2 (122), #3 (123), or #4 (124) may each operate in a similar manner to the battery module management device #1 (121) according to an example disclosed herein, and each encoding information I m 2. I m 3, or I m A further operation of generating 4 can be performed.

[0062] The method of operating the battery management system may include encoding information (e.g., I m 1, I m 2. I m 3, or I m In operation S225, the encoding information (e.g., I ... m 1, I m 2. I m 3, or I m In the case of transmitting 4), encoding information can be further transmitted to the battery pack management device 130.

[0063] As a specific example of the operation of S225, the battery module management device #1 (121) may store the encoding information (e.g., I m 1) to at least some of the remaining battery module management devices, battery module management devices #2 (122), #3 (123), and #4 (124). As various examples of the operation of S225, battery module management devices #2 (122), #3 (123), and #4 (124) each operate in a manner similar to battery module management device #1 (121) according to an example disclosed in this document, and each transmits the generated encoding information (e.g., Im 2. I m 3, or I m 4) may further be transmitted to at least some of the remaining battery module management devices.

[0064] The operating method of the battery management system may further include an operation of the battery module management device checking firmware packet information using the battery data information and encoding information transmitted from the other battery module management devices (S226) by the battery module management device. As a specific example of the operation of S226, the battery module management device #2 (122) may check firmware packet information by receiving battery data information (e.g., D m 1, D m 3, and / or D m 4) and can receive encoding information (e.g., I m 1, I m 3, and / or I m As an example, the battery module management device #1 (121) can receive the monitored battery data information (e.g., D m 1) and the generated encoding information (e.g., I m When the battery module management device #2 (122) receives the battery data information (e.g., D m 1) and encoding information (e.g., I m 1) is compared with the decoded information, and firmware packet information (e.g., P m According to an example disclosed in this document, the battery module management device #2 (122) can check firmware packet information (e.g., P mEven if the battery module management device #2 (122) cannot normally receive the battery data information (e.g., D m 1) and encoding information (e.g., I m 1) to obtain firmware packet information (e.g., P m ), the battery management system 100 can proceed with the update normally. In this way, even if the battery pack management device 130 is in a poor communication state with some of the battery module management devices 120, it is advantageous that the update of the battery management system 100 can proceed normally.

[0065] 5 is a diagram illustrating a process of data communication according to time in a battery management system according to an embodiment disclosed herein. FIG. 5 can be referred to in order to explain the S221, S222, and S223 operations shown in FIG. 4 according to an embodiment disclosed herein.

[0066] Referring to FIG. 5, the battery pack management unit 130 transmits divided firmware packet information to one or more battery module management units 120, and receives battery data information (e.g., D m 1, D m 2. D m 3, or D m In order to receive the firmware packet information or each battery data information, the battery pack management device 130 may transmit a beacon signal (B) to one or more battery management devices 120 or receive a beacon signal (B) from one or more battery module management devices 120. As an example, the beacon signal may correspond to an informational beacon signal indicating location information of the battery pack management device 130 or one or more battery module management devices 120. As an example, the beacon signal (B) may be transmitted before transmitting firmware packet information or each battery data information.

[0067] As an example, when the firmware stored in the battery module management device 120 is divided into a total of N pieces of firmware packet information (where N is a natural number equal to or greater than 2), the firmware packet information to be transmitted m-th is determined as P m (where 1≦m≦N). As an example, the battery pack management device 130 may receive firmware packet information (e.g., P m ), the next firmware packet information (for example, P m+1 ) from one or more battery module management devices 120, respectively, before transmitting the monitored battery module data (e.g., D m 1, D m 2. D m 3, or D m 4) can be received. As an example, m 1. T m 2. T m 3. T m 1, t m 2, t m 3. T m 4, t m 5, t m 6, T m 7, t m 8, and t m 9 may correspond to a data value indicating time.

[0068] As an example, T m 1~t m During the period of time, the battery pack module device 130 transmits a beacon signal (B) to one or more battery module management devices 120 and transmits firmware packet information (P m At this time, each battery module management device #1 (121), #2 (122), #3 (123), or #4 (124) can be in a state to receive information transmitted from the battery pack module device 130.

[0069] As an example, m 1~t mDuring the period of time 2, the battery module management device #1 (121) monitors the beacon signal (B) and the battery data information (D m The battery pack management device 130 may transmit information (information) transmitted from the battery module management device #1 (121) to the battery pack management device 130, and may further transmit the same information to at least some of the remaining battery module management devices #2 (122), #3 (123), and #4 (124). At this time, the battery pack management device 130 or the remaining battery module management devices #2 (122), #3 (123), and #4 (124) may be in a state to receive the information transmitted from the battery module management device #1 (121).

[0070] As an example, m 2~t m During the period of time 3, the battery module management device #2 (122) monitors the beacon signal (B) and the battery data information (D m 2) to the battery pack management device 130, and can further transmit the same information to at least some of the remaining battery module management devices #1 (121), #3 (123), and #4 (124). At this time, the battery pack management device 130 or the remaining battery module management devices #1 (121), #3 (123), and #4 (124) can be in a state to receive the information transmitted from the battery module management device #2 (122).

[0071] As an example, m 3~t m During the period of time 4, the battery module management device #3 (123) monitors the beacon signal (B) and the battery data information (D m3) to the battery pack management device 130, and the same information can be further transmitted to at least some of the remaining battery module management devices #1 (121), #2 (122), and #4 (124). At this time, the battery pack management device 130 or the remaining battery module management devices #1 (121), #2 (122), and #4 (124) can be in a state to receive the information transmitted from the battery module management device #3 (123).

[0072] As an example, m 5~T m During the period of time 2, the battery module management device #4 (124) monitors the beacon signal (B) and the battery data information (D m The battery pack management device 130 may transmit information (information) transmitted from the battery module management device #4 (124) to the battery pack management device 130, and may further transmit the same information to at least some of the remaining battery module management devices #1 (121), #2 (122), and #3 (123). At this time, the battery pack management device 130 or the remaining battery module management devices #1 (121), #2 (122), and #3 (123) may be in a state to receive the information transmitted from the battery module management device #4 (124).

[0073] According to one embodiment disclosed herein, the battery pack management device 130 or one or more battery module management devices 120 may store data (e.g., m , D m 1, D m 2. D m 3, or D m 4, the remaining devices can be in a state to receive the transmitted data. According to an example disclosed herein, the battery pack management device 130 or one or more battery module management devices 120 can receive data (e.g., P m , D m 1, D m 2. D m 3, or D mThe order of transmitting the battery module management devices (e.g., 4) may be changed or may be specified arbitrarily. Even if the number of battery module management devices included in the battery management system 100 is changed according to the example disclosed herein, the operation according to the example disclosed herein can be performed in a similar manner.

[0074] 6 is a diagram illustrating a process of data communication according to time in a battery management system according to an embodiment disclosed herein. FIG. 6 can be referred to in order to explain the operations S224, S225, and S226 shown in FIG. 4 according to an embodiment disclosed herein.

[0075] 6, one or more battery module management devices 120 each monitor battery data information of the battery modules 110 and firmware packet information (e.g., P m ) may be encoded together to generate encoding information, and each encoding information may be sent to at least a portion of the remaining battery module management devices. According to an example disclosed herein, the battery module management device 120 may further send its encoding information to the battery pack management device.

[0076] As an example, the battery module management device #1 (121) monitors the battery module #1 (111) and outputs battery data information (D m 1), and firmware packet information received from the battery pack management device 130 (e.g., P m ) are encoded together to obtain the encoding information (I m For example, the battery module management device #1 (121) can generate encoding information (I m If 1) is generated, T m 2~t m During the period of time 6, the battery module management device #1 (121) stores the encoding information (I m1) to at least some of the remaining battery module management devices #2 (122), #3 (123), and #4 (124). At this time, the remaining battery module management devices #2 (122), #3 (123), and #4 (124) can be in a state to receive the information transmitted from battery module management device #1 (121).

[0077] As an example, the battery module management device #2 (122) monitors the battery module #2 (112) and outputs battery data information (D m 2), and firmware packet information received from the battery pack management device 130 (e.g., P m ) are encoded together to obtain the encoding information (I m For example, the battery module management device #2 (122) can generate the encoding information (I m 2) If t m 6~t m During the period of time 7, the battery module management device #2 (121) stores the encoding information (I m 2) to at least some of the remaining battery module management devices #1 (121), #3 (123), and #4 (124). At this time, the remaining battery module management devices #1 (121), #3 (123), and #4 (124) can be in a state to receive the information transmitted from the battery module management device #2 (122).

[0078] As an example, the battery module management device #3 (123) monitors the battery module #3 (113) and outputs battery data information (D m 3), and firmware packet information received from the battery pack management device 130 (e.g., P m ) are encoded together to obtain the encoding information (I m For example, the battery module management device #2 (123) can generate the encoding information (I m 3) If t m 7~t mDuring the period of time 8, the battery module management device #3 (123) m 3) to at least some of the remaining battery module management devices #1 (121), #2 (122), and #4 (124). At this time, the remaining battery module management devices #1 (121), #2 (122), and #4 (124) can be in a state to receive information transmitted from battery module management device #3 (123).

[0079] As an example, the battery module management device #4 (124) monitors the battery module #4 (114) and outputs battery data information (D m 4), and firmware packet information received from the battery pack management device 130 (e.g., P m ) are encoded together to obtain the encoding information (I m For example, the battery module management device #4 (123) can generate the encoding information (I m 4) If t m 8~T m During the period of time 3, the battery module management device #4 (124) stores the encoding information (I m 4) to at least some of the remaining battery module management devices #1 (121), #2 (122), and #3 (123). At this time, the remaining battery module management devices #1 (121), #2 (122), and #3 (123) can be in a state to receive information transmitted from battery module management device #4 (124).

[0080] According to one embodiment disclosed herein, one or more battery module management devices may receive battery data information (e.g., D m 1, D m 2. D m 3, or D m 4) and encoding information (e.g., I m 1, I m 2. I m 3, or I m4), firmware packet information (e.g., P m As an example, the battery module management device #2 (122) can confirm the battery data information (e.g., D m 2) and encoding information (e.g., I m 2) is received, the received encoding information (e.g., I m 2) is decoded, and the decoded result data is converted into battery data information (e.g., D m 2) compared with firmware packet information (e.g., P m ) can be confirmed. In this case, even if the battery module management device #2 (122) is unable to perform normal data communication with the battery pack management device 130 and is unable to directly receive firmware packet information, the battery management system 100 can normally proceed with the update by confirming the firmware packet information using the received battery data information and encoding information. As an example, the battery module management device #1 (121), #3 (123), or #4 (124) can operate in a manner similar to the battery module management device #2 (122) according to an example disclosed in this document.

[0081] 7 is a functional block diagram of a battery management system according to an embodiment disclosed in this document. The configuration shown in FIG. 7 may be a hardware device or a program (or application) including an instruction word.

[0082] The control unit 310 may be a hardware device such as a processor or a central processing unit (CPU), or a program implemented by a hardware device. The control unit 310 is connected to each component of the battery management system to perform the overall function of the battery management system. In one embodiment, the control unit 310 may control the battery module management device 120 to monitor the state of each connected battery module and transmit the monitored battery data information to the battery pack management device 130. In one embodiment, the control unit may control the battery pack management device 130 to divide firmware built in the battery pack management device to generate firmware packet information and transmit the divided firmware packet information to each battery module management device 120.

[0083] In an embodiment, the control unit 310 may further configure the battery pack management device 130 to control the battery pack management device 130 to transmit the undivided firmware to one or more battery module management devices 120 when a command for batch firmware download according to a specified method is input to the battery pack management device. In this case, the description of FIGS. 2 to 4 may be referred to for the specified method of the command for batch firmware download.

[0084] In an embodiment, the control unit 310 may further control the battery pack management device 130 to store length information of the firmware packet information transmitted to the battery module management device. In this case, the description of FIG. 3 may be referred to for the operation of storing the length information.

[0085] In an embodiment, the control unit 310 may further configure the battery module management device 120 to transmit the monitored battery data information to at least some of the remaining battery module management devices. In this case, the description of FIGS. 2 to 5 may be referred to for the operation of transmitting the battery data information.

[0086] In an embodiment, the control unit 310 may be further configured to control the battery module management device 120 to generate encoding information by encoding both the battery data information monitored by the battery module management device 120 and the firmware packet information from the battery pack management device 130, and may be further configured to transmit the generated encoding information to at least some of the remaining battery module management devices. In this case, the description of FIGS. 2 to 6 may be referred to for the operation of generating and transmitting the encoding information.

[0087] In an embodiment, the control unit 310 may be further configured to control the battery module management device 120 to check the divided firmware packet information transmitted by the battery pack management device 130, using the battery data information and encoding information received from another battery module management device. In this case, the description of FIGS. 2 to 6 may be referred to for the operation of checking the firmware packet information using the received battery data information and encoding information.

[0088] The control unit 310 can control each component of the battery management system, and for this purpose, the control unit 310 can include a battery module management device control unit 320 and / or a battery pack management device control unit 330. The components included in the control unit 310 may be realized as separate devices (or programs) or as a single integrated module.

[0089] Although it has been described above that all components constituting the embodiments disclosed in this document are combined or operate in combination, the embodiments disclosed in this document are not necessarily limited to such embodiments. In other words, within the scope of the purpose of the embodiments disclosed in this document, all components may be selectively combined and operate in one or more combinations.

[0090] FIG. 8 illustrates an operational flow chart for consuming battery energy according to one embodiment disclosed herein. Referring to FIG. 8, a computing system 30 according to one embodiment disclosed in this document may include an MCU 32, a memory 34, an input / output I / F 36, and a communication I / F 38.

[0091] The MCU 32 may be a processor that executes various programs (e.g., characteristic value calculation programs, class classification and life estimation programs, etc.) stored in the memory 34, processes various data including the voltage, current, etc. of the battery cells via such programs, and performs the functions of the battery management device shown in Figures 2 to 7 described above.

[0092] The memory 34 can store various programs related to calculation of characteristic values ​​of the battery cells, classification, and life expectancy estimation, as well as various data such as the voltage, current, and characteristic value data of each battery cell.

[0093] A plurality of such memories 34 may be provided as necessary. The memories 34 may be volatile memories or nonvolatile memories. The memory 34 as a volatile memory may be a RAM, a DRAM, an SRAM, or the like. The memory 34 as a nonvolatile memory may be a ROM, a PROM, an EAROM, an EPROM, an EEPROM, a flash memory, or the like. The examples of the memory 34 listed above are merely illustrative and are not limited to these examples.

[0094] The input / output I / F 36 can provide an interface that connects input devices (not shown) such as a keyboard, mouse, or touch panel, and output devices such as a display (not shown), to the MCU 32 to transmit and receive data.

[0095] The communication I / F 38 is configured to be able to transmit and receive various data to and from a server, and may be any of various devices capable of supporting wired or wireless communication. For example, programs and various data for calculating characteristic values ​​of battery cells, classifying them, and estimating their life spans can be transmitted and received from a separately provided external server via the communication I / F 38.

[0096] In this manner, a computer program according to one embodiment disclosed in this document may be recorded in memory 34 and processed by MCU 32 to be realized, for example, as a module performing each function shown in FIG. 3 or FIG. 4.

[0097] In addition, the terms "comprise", "constitute", or "have" described above mean that the relevant element can be contained, unless otherwise specified, and should be interpreted as meaning that other elements may be included, rather than excluding other elements. All terms, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed in this document belong, unless otherwise defined. Commonly used terms, such as terms defined in a dictionary, should be interpreted as consistent with the contextual meaning of the relevant art, and should not be interpreted in an idealized or overly formal sense, unless expressly defined in this document.

[0098] The above description is merely an illustrative example of the technical ideas disclosed in this document, and a person having ordinary knowledge in the technical field to which the embodiments disclosed in this document belong can make various modifications and variations within the scope of the essential characteristics of the embodiments disclosed in this document. Therefore, the embodiments disclosed in this document are intended to explain, not to limit, the technical ideas of the embodiments disclosed in this document, and such embodiments do not limit the scope of the technical ideas disclosed in this document. The scope of protection of the technical ideas disclosed in this document should be interpreted according to the claims below, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of rights of this document.

Claims

1. A plurality of battery modules; a plurality of battery module management devices connected to the battery modules; a battery pack management device having firmware built therein and managing the plurality of battery module management devices, The battery pack management device includes: a firmware management device that performs firmware update on a battery module management information storage device according to a predetermined order; configured to transmit a second firmware packet information of the generated firmware packet information after transmitting a first firmware packet information of the generated firmware packet information; The battery module management device includes: configured to monitor a state of the connected battery module and transmit monitored battery data information to the battery pack management device; A battery management system configured to transmit the battery data information to the battery pack management device after the battery pack management device transmits the first firmware packet information and before the battery pack management device transmits the second firmware packet information.

2. A plurality of battery modules; a plurality of battery module management devices connected to the battery modules; a battery pack management device having firmware built therein and managing the plurality of battery module management devices, The battery pack management device includes: a firmware management device that manages the firmware by dividing the firmware into a plurality of firmware packets; The battery module management device includes: configured to monitor a state of the connected battery module and transmit monitored battery data information to the battery pack management device; The battery module management device includes: further configured to transmit the monitored battery data information to at least a portion of the remaining battery module management devices; The battery module management device includes: The battery management system is configured to encode both the monitored battery data information and the received divided firmware packet information to generate encoding information, and transmit the encoding information to at least a portion of the remaining battery module management devices.

3. The battery module management device comprises: The battery management system of claim 2 , configured to verify the divided firmware packet information using the battery data information and the encoding information received from another battery module management device.

4. 4. A battery management system as claimed in any one of claims 1 to 3, wherein the battery pack management device is further configured to transmit the undivided firmware to the plurality of battery module management devices when a batch firmware download command is input in accordance with a method specified in the battery pack management device.

5. The battery pack management device includes: The battery management system according to claim 1 , further configured to store length information of the firmware packet information transmitted to the battery module management device.

6. The battery module management device includes: The battery management system of claim 1 , further configured to transmit the monitored battery data information to at least a portion of the remaining battery module management devices.

7. 1. A method of operating a battery management system, comprising: An operation of dividing firmware stored in the battery pack management device and generating divided firmware packet information; an operation of transmitting the divided firmware packet information from the battery pack management device to a plurality of battery module management devices in a predetermined order; an operation of monitoring states of the battery modules connected to the plurality of battery module management devices and transmitting the monitored battery data information to the battery pack management device; Including, an operation of transmitting the divided firmware packet information by the battery pack management device to the plurality of battery module management devices in a predetermined order includes an operation of transmitting first firmware packet information of the divided firmware packet information and then transmitting second firmware packet information of the divided firmware packet information; An operation method for a battery management system, wherein the operation of the battery module management device transmitting the battery data information to the battery pack management device includes an operation of transmitting the battery data information to the battery pack management device after the battery pack management device transmits the first firmware packet information and before the battery pack management device transmits the second firmware packet information.

8. A method for operating a battery management system, comprising: An operation of dividing firmware stored in the battery pack management device and generating divided firmware packet information; an operation of transmitting the divided firmware packet information from a battery pack management device to a plurality of battery module management devices; an operation of monitoring states of the battery modules connected to the plurality of battery module management devices and transmitting the monitored battery data information to the battery pack management device; Including, The battery module management device may further include an operation of transmitting the monitored battery data information to at least a portion of the remaining battery module management devices; an operation of the battery module management device encoding the monitored battery data information and the received divided firmware packet information to generate encoding information; transmitting the encoding information to at least a portion of the remaining battery module management devices.

9. The operating method of a battery management system described in claim 8, further comprising an operation in which the battery module management device confirms the divided firmware packet information using the battery data information and the encoding information received from another battery module management device.

10. The method of operating a battery management system according to any one of claims 7 to 9, further comprising an operation of transmitting the undivided firmware to the plurality of battery module management devices when a batch firmware download command is input in accordance with a method specified in the battery pack management device.

11. The method of claim 7 , further comprising an operation of the battery pack management device storing length information of the firmware packet information transmitted to the battery module management device.

12. The method of claim 7 , further comprising an operation of the battery module management device transmitting the monitored battery data information to at least a part of the remaining battery module management devices.

13. A plurality of battery modules; a plurality of battery module management devices connected to the battery modules; a battery pack management device having firmware built therein and managing the plurality of battery module management devices; A battery management system including: a control unit connected to the battery module management device and the battery pack management device, The control unit is controlling the battery pack management device to divide the firmware to generate firmware packet information, and to transmit the divided firmware packet information to the plurality of battery module management devices in a predetermined order; controlling the battery pack management device to transmit first firmware packet information of the divided firmware packet information and then transmit second firmware packet information of the divided firmware packet information; Controlling the battery module management device to monitor the state of the connected battery modules and to transmit the monitored battery data information to the battery pack management device; A battery management system that controls the battery module management device so that after the battery pack management device transmits the first firmware packet information, and before the battery pack management device transmits the second firmware packet information, the battery data information is transmitted to the battery pack management device.

14. A plurality of battery modules; a plurality of battery module management devices connected to the battery modules; a battery pack management device having firmware built therein and managing the plurality of battery module management devices; A battery management system including: a control unit connected to the battery module management device and the battery pack management device, The control unit is Controlling the battery pack management device to divide the firmware to generate firmware packet information, and to transmit the divided firmware packet information to the plurality of battery module management devices; The battery module management device is configured to control the battery module management device to monitor the status of the connected battery modules and transmit the monitored battery data information to the battery pack management device; The control unit is further configured to control the battery module management device to transmit the monitored battery data information to at least a portion of the remaining battery module management devices; The control unit is The battery management system is further configured to control the battery module management devices to encode both the monitored battery data information and the received divided firmware packet information to generate encoding information, and to transmit the encoding information to at least a portion of the remaining battery module management devices.

15. The control unit: The battery management system of claim 14 , further configured to control the battery module management device to verify the divided firmware packet information using the battery data information and the encoding information received from another battery module management device.

16. The control unit is The battery management system according to any one of claims 13 to 15, further configured to control the battery pack management device to transmit the undivided firmware to the plurality of battery module management devices when a batch firmware download command is input in accordance with a method specified in the battery pack management device.

17. The control unit is The battery management system of claim 13 , further configured to control the battery pack management device to store length information of the firmware packet information sent to the battery module management device.

18. The control unit is The battery management system of claim 13 , further configured to control the battery module management devices to transmit the monitored battery data information to at least a portion of the remaining battery module management devices.

Images