Patent Application
20240152349
This application claims priority to and the benefit of Korean Patent Application No. 10-2021-0132752 filed in the Korean Intellectual Property Office on Oct. 6, 2021, the entire contents of which are incorporated herein by reference.
Embodiments disclosed herein relate to a firmware update system in a battery data management system and a method therefor.
An energy storage system (ESS) is a device that improves power use efficiency by storing generated electricity in a storage device such as a battery and supplying power when needed, and includes a battery that stores electricity and components for efficiently managing and controlling the battery. Among those components, a battery management system (BMS) uses each sensor connected to a battery module to measure battery state information such as temperature, current, voltage, etc., and by doing so, plays a role of calculating data on dangerous problems such as overcharge or over discharge occurring in charge and/or discharge of the battery to control the temperature, current, voltage, etc., according to the state of the battery, thereby allowing the battery to operate in a stable state.
The BMS may include hardware that manages an operation of the battery and software that controls the hardware. Thus, for a more stable operation, the software of the BMS needs to be updated. The BMS may include a battery module management apparatus that monitors the state of each battery module and a battery pack management apparatus that manages the battery module management apparatus. When the software of the BMS is updated, the software of the battery pack management apparatus is updated and the battery pack management apparatus transmits update information to each battery module management apparatus. Each battery module management apparatus transmits state data of each connected battery module, etc., to the battery pack management apparatus to maintain the stable state of the BMS to allow collection of the information.
The matters described as the background art are merely for improving the understanding of the background of the present disclosure, and should not be considered as acknowledging that they correspond to the prior art known to those of ordinary skill in the art.
When a battery management system is updated, firmware updated in a battery pack management apparatus is transmitted to one or more battery module management apparatuses. The one or more battery module management apparatuses may monitor a state of each connected battery module and transmit monitored battery data information to a battery pack management apparatus. However, when the firmware updated in the battery pack management apparatus is transmitted to the one or more battery module management apparatuses, the battery module management apparatus is not able to transmit monitored battery data information to the battery pack management apparatus, such that some battery data information may be lost. When the size of update information of the firmware embedded in the battery pack management apparatus is sufficiently large, the amount of battery data information lost without being collected may be huge, disrupting an operation of the battery management system.
When the battery management system is updated, the firmware updated in the battery pack management apparatus is transmitted to the one or more battery module management apparatuses, and when some battery module management apparatuses have poor communication with the battery pack management apparatus, i.e., the battery module management device may fail to receive the updated firmware in a communication shadow area in relation to the battery pack management apparatus.
A battery management system according to an embodiment disclosed herein includes at least one battery module, one or more battery module management apparatuses respectively connected to the at least one battery module, and a battery pack management apparatus having embedded therein firmware and configured to manage the one or more battery module management apparatuses, in which the battery pack management apparatus is further configured to divide the firmware to generate divided firmware packet information and transmit the divided firmware packet information to the one or more battery module management apparatuses, and the one or more battery module management apparatuses are further configured to monitor a state of the connected at least one battery module and transmit monitored battery data information to the battery pack management apparatus.
According to an embodiment, the battery pack management apparatus may be further configured to transmit a non-divided firmware to the one or more battery module management apparatuses when a firmware batch download command is input according to a scheme designated in the battery pack management apparatus.
According to an embodiment, the battery pack management apparatus may be further configured to store length information of the firmware packet information transmitted to the one or more battery module management apparatuses.
According to an embodiment, the one or more battery module management apparatuses may be further configured to transmit the monitored battery data information to at least some of the other battery module management apparatuses.
According to an embodiment, the one or more battery module management apparatuses may be further configured to encode the monitored battery data information and received divided firmware packet information together to generate encoding information and transmit the encoding information to at least some of the other battery module management apparatuses.
According to an embodiment, the one or more battery module management apparatuses may be further configured to identify the divided firmware packet information by using the battery data information and the encoding information received from another of the one or more battery module management apparatuses.
An operating method of a battery management system according to an embodiment disclosed herein includes dividing firmware embedded in a battery pack management apparatus to generate divided firmware packet information, transmitting, by the battery pack management apparatus, the divided firmware packet information to one or more battery module management apparatuses, and monitoring, by the one or more battery module management apparatuses, a state of a connected battery module and transmitting monitored battery data information to the battery pack management apparatus.
According to an embodiment, the operating method may further include transmitting a non-divided firmware to the one or more battery module management apparatuses when a firmware batch download command is input according to a scheme designated in the battery pack management apparatus.
According to an embodiment, the operating method may further include storing, by the battery pack management apparatus, length information of the divided firmware packet information transmitted to the one or more battery module management apparatuses.
According to an embodiment, the operating method may further include transmitting, by the one or more battery module management apparatuses, the monitored battery data information to at least some of the other battery module management apparatuses.
According to an embodiment, the operating method may further include encoding, by the one or more battery module management apparatuses, the monitored battery data information and received divided firmware packet information to generate encoding information and transmitting the encoding information to at least some of the other battery module management apparatuses.
According to an embodiment, the operating method may further include identifying, by the one or more battery module management apparatuses, the divided firmware packet information by using the battery data information and the encoding information received from another of the one or more battery module management apparatuses.
A battery management system according to an embodiment disclosed herein includes one or more battery modules, one or more battery module management apparatuses respectively connected to the one or more battery modules, a battery pack management apparatus having embedded therein firmware and configured to manage the one or more battery module management apparatuses, and a controller connected to the one or more battery module management apparatuses and the battery pack management apparatus, in which the controller is configured to, by controlling the battery pack management apparatus, divide the firmware to generate divided firmware packet information and transmit the divided firmware packet information to the one or more battery module management apparatuses and, by controlling the one or more battery module management apparatuses, monitor a state of the connected one or more battery modules and transmit monitored battery data information to the battery pack management apparatus.
According to an embodiment, the controller may be further configured to, by controlling the battery pack management apparatus, transmit a non-divided firmware to the one or more battery module management apparatuses when a firmware batch download command is input according to a scheme designated in the battery pack management apparatus.
According to an embodiment, the controller may be further configured to, by controlling the battery pack management apparatus, store length information of the divided firmware packet information transmitted to the one or more battery module management apparatuses.
According to an embodiment, the controller may be further configured to, by controlling the one or more battery module management apparatuses, transmit the monitored battery data information to at least some of the other battery module management apparatuses.
According to an embodiment, the controller may be further configured to, by controlling the one or more battery module management apparatuses, encode the monitored battery data information and the divided firmware packet information together to generate encoding information and transmit the encoding information to at least some of the other battery module management apparatuses.
According to an embodiment, the controller may be further configured to, by controlling the one or more battery module management apparatuses, identify the divided firmware packet information by using the battery data information and the encoding information received from another of the one or more battery module management apparatuses.
According to embodiments disclosed herein, a battery management system may be updated without a loss of battery data information even during driving or operation of a battery module.
According to embodiments disclosed herein, when the battery management system is updated, even if there is a battery module management apparatus having poor communication with the battery pack management apparatus, another battery module management apparatus having normal communication with the battery pack management apparatus directly or indirectly receives received firmware packet information to identify the firmware packet information, thereby normally updating the battery management system.
Moreover, various effects recognized directly or indirectly from the disclosure may be provided.
With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related components.
Hereinafter, various embodiments of the present disclosure will be disclosed with reference to the accompanying drawings. However, the description is not intended to limit the present disclosure to particular embodiments, and it should be construed as including various modifications, equivalents, and/or alternatives according to the embodiments of the present disclosure.
It should be appreciated that various embodiments of the present disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment. With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related elements. It is to be understood that a singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise.
As used herein, each of such phrases 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 of, or all possible combinations of the items enumerated together in a corresponding one of the phrases. Such terms as “1st”, “2nd”, “first”, “second”, “A”, “B”, “(a)”, or “(b)” may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order), unless mentioned otherwise.
Herein, it is to be understood that when an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “connected with”, “coupled with”, or “linked with”, or “coupled to” or “connected to” to another element (e.g., a second element), it means that the element may be connected with the other element directly (e.g., wiredly), wirelessly, or via a third element.
According to an embodiment, a method according to various embodiments of the disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store, or between two user devices directly. If distributed online, at least part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as memory of the manufacturer's server, a server of the application store, or a relay server.
According to various embodiments, each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities, and some of the multiple entities may be separately disposed in different components. According to various embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, according to various embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.
More specifically,
As shown in
The plurality of battery modules 110 may include at least one chargeable/dischargeable battery cells. In this case, the plurality of battery modules 110 may be connected in series or in parallel.
The sensor 14 may detect current flowing in the battery pack 10. A detected signal may be transmitted to the battery pack management apparatus 130.
The switching unit 16 may be connected in series to a (+) terminal side or a (−) terminal side of the battery module 110 to control the charging/discharging current flow of the battery module 110. For example, the switching unit 16 may use at least one relay, a magnetic contactor, etc., according to the specifications of the battery pack 10.
The battery pack management apparatus 130 may monitor the voltage, current, temperature, etc., of the battery pack 10 to perform control and management to prevent overcharging and over discharging, etc., and may include, for example, a rack battery management system (RBMS).
The battery pack management apparatus 130, which is an interface for receiving measurement values of various parameter values described above, may include a plurality of terminals and a circuit, etc., connected to the terminals to process received values. The battery pack management apparatus 130 may control on/off of the switching unit 16, e.g., a relay, a contactor, etc., and may be connected to the battery module 110 to monitor the state of each battery module 110.
The higher-level controller 20 may transmit a control signal for controlling the battery module 110 to the battery pack management apparatus 130. Thus, the battery pack management apparatus 130 may also be controlled in terms of an operation thereof based on a control signal applied from the higher-level controller 20. Also, the battery module 110 may be a component included in an energy storage system (ESS). In this case, the higher-level controller 20 may be a controller (a bank battery management system (BBMS)) of a battery bank including the plurality of packs 10 or an ESS controller for controlling the entire ESS including a plurality of banks. However, the battery pack 10 is not limited to such a purpose.
Referring to
According to an embodiment disclosed herein, when the battery management system 100 is updated, the firmware embedded in the battery pack management apparatus 130 may be updated. The battery pack management apparatus 130 may transmit the entire updated firmware or a part thereof to the one or more battery module management apparatuses 120 to update the battery module management apparatus 120. In an example, the battery pack management apparatus 130 may transmit information corresponding to the updated part to the one or more battery module management apparatuses 120 in the updated firmware. According to an embodiment disclosed herein, when the battery pack management apparatus 130 may batch the entire updated firmware or a part thereof to the battery module management apparatus 120. In another example, the battery pack management apparatus 130 may divide the firmware to be transmitted to generate firmware packet information, and transmit the divided firmware packet information to the battery module management apparatus 120 several times.
The one or more battery module management apparatuses 120 may be connected to each of the one or more battery modules 110 to monitor the state of the battery module 110. In an example, the state information of the battery module 110 monitored by the battery module management apparatus 120 may correspond to battery related information such as a temperature T, a voltage V, a current I, a state of charge (SoC), a state of health (SoH), a state of power (SoP), etc., of the battery. In an example, a battery module management apparatus #1121 may be connected to a battery module #1111 to monitor the state of the battery module #1111. In an example, a battery module management apparatuses #2122 may be connected to a battery module #2112 to monitor the state of the battery module #2112. In an example, a battery module management apparatuses #3123 may be connected to a battery module #3113 to monitor the state of the battery module #3113. In an example, a battery module management apparatuses #4124 may be connected to a battery module #4114 to monitor the state of the battery module #4114. According to an embodiment disclosed herein, the number of battery module management apparatus and battery modules is not limited to the number of those shown in the drawing, and the number may be changed by adding or excluding battery module management apparatuses and battery modules, etc. As such, even when the number of battery module management apparatuses included in the battery management system 100 changes, an operation according to an embodiment disclosed herein may be performed in the same manner.
According to an embodiment disclosed herein, when the battery module management apparatus 120 monitors each connected battery module 110, the battery module management apparatus 120 may transmit the monitored battery data information to the battery pack management apparatus 130. In an example, the battery module management apparatus 120 may further transmit battery data information obtained by monitoring each connected battery module to at least some of the other battery module management apparatuses 120. According to a detailed example of the present disclosure, the battery module management apparatus #1121 may transmit battery data information obtained by monitoring the battery module #1111 to the battery pack management apparatus 130. According to a detailed example of the present disclosure, the battery module management apparatus #1121 may further transmit battery data information obtained by monitoring the battery module #1111 to at least any one of the other battery pack management apparatuses #2122, #3123, and #4124. In an example, the battery module management apparatus #2122, #3123, or #4124 may operate in the same manner to the battery module management apparatus #1121 according to an embodiment disclosed herein.
Referring to
Operation S260 of transmitting, by the battery management system 100 according to an embodiment disclosed herein, the firmware embedded in the battery pack management apparatus 130 to the one or more battery module management apparatuses 120 may be performed when there is an input operation S200 or S250 of a firmware batch download command from a user to the battery management system 100.
Operation S200 may correspond to an operation in which the battery management system 100 receives, from the user, an input of whether to batch the updated firmware when the battery management system 100 according to an embodiment disclosed herein is converted from an off stage to an on stage or the firmware embedded in the battery pack management apparatus 130 is updated in the on stage. In an example, when the user inputs a batch download command of the updated firmware to the battery management system 100 through operation S200, the battery pack management apparatus 130 may transmit the entire updated firmware or a part thereof to the one or more battery module management apparatuses 120. In this case, in an example according to the present disclosure, when the battery pack management apparatus 130 transmits a part of the firmware to the one or more battery module management apparatuses 120, the transmitted part of the firmware may correspond to an updated part of the entire firmware configuration.
In operation S200 according to an embodiment disclosed herein, when it is determined that the battery management system 100 does not receive the batch download command of the firmware, the battery pack management apparatus 130 may divide the updated firmware to generate firmware packet information in operation S210. In an example, in operation S210, the battery pack management apparatus may divide the entire firmware having been updated or a part thereof to generate firmware packet information. In an example, when a part of the firmware having been updated is divided to generate firmware packet information, the part of the firmware may correspond to firmware information corresponding to the part updated from the existing firmware.
According to an embodiment disclosed herein, the battery pack management apparatus 130 may transmit the firmware packet information generated in operation S210 to the one or more battery module management apparatuses 120 several times, and the battery module management apparatus 120 may perform a communication operation related to data transmission and reception between the battery pack management apparatus and the one or more battery module management apparatuses by transmitting battery data information of a battery module monitored by the battery module management apparatus 120 to the battery pack management apparatus 130 or further transmitting the battery data information to the other battery module management apparatuses, in operation S220. A detailed description of operation S220 will be described in detail with reference to
After operation S220 is performed according to an embodiment disclosed herein, the battery management system 100 may further perform an operation of determining whether a signal for stopping data transmission exists from an internal or external source of the system, in operation S230. For example, the signal for stopping data transmission in operation S230 may correspond to a signal for conversion to the off stage of the battery management system 100, input from the user. In another example, the signal for stopping data transmission in operation S230 may correspond to a signal for indicating that divided pieces of firmware packet information are transmitted from the battery pack management apparatus 130 to the battery module management apparatus 120. In an example, when it is determined that the signal for stopping data transmission does not exist in the battery management system 100, the battery pack management apparatus and the one or more battery module management apparatuses may repeat operation S220.
According to an embodiment disclosed herein, when it is determined that the signal for stopping data transmission exists in the battery management system 100, the battery management system 100 may perform an operation of determining whether all of the divided pieces of the firmware packet information have been transmitted to the battery module management apparatus 120 from the battery pack management apparatus 130, in operation S240. When it is determined in operation S240 that some or all of the divided pieces of the firmware packet information have not been transmitted to the battery module management apparatus 120, the battery management system 100 may receive a command of whether to batch the updated firmware from the user, in operation S250. For example, when it is determined in operation S240 that all of the divided pieces of the firmware packet information have been transmitted to the battery module management apparatus 120, the battery management system 100 may terminate update of firmware or be converted to the off stage thereof to terminate the system.
In operation S250 according to an embodiment disclosed herein, when it is determined that the battery management system 100 receives the firmware batch download command from the user, the battery management system 100 may perform operation S260 of transmitting the firmware embedded in the battery pack management apparatus 130 to the one or more battery module management apparatuses 120. In an example, when it is determined in operation S250 that the firmware batch download command is not input, the battery pack management apparatus 130 may further store the length information of the transmitted firmware packet information, in operation S270. In another example, when it is determined in operation S250 that the firmware batch download command is not input, the battery module management apparatus 120 may further store the length information of the received firmware packet information, in operation S270. According to an embodiment disclosed herein, by further storing the length information of the transmitted or received firmware packet information in operation S270 even when the battery management system 100 is terminated without completion of transmission of the firmware packet information to the battery module management apparatus 120, the battery management system 100 may merely transmit existing firmware packet information that has not been transmitted, when resuming the operation thereof. In this case, an advantage may be that it is possible to prevent unnecessary repetition of transmission of the existing firmware packet information having been transmitted.
Operation S260 according to an embodiment disclosed herein may correspond to an operation of transmitting the entire firmware embedded in the battery pack management apparatus 130 or a part thereof to the one or more battery module management apparatuses 120. In an example, operation S260 may correspond to an operation of transmitting, by the battery pack management apparatus 130, the entire updated firmware. In an example, operation S260 may correspond to an operation of transmitting, by the battery pack management apparatus 130, firmware information (i.e., a part of the updated firmware) corresponding to an updated part of the existing firmware. In an example, operation S260 may correspond to an operation of batching the entire firmware including transmitted pieces of the firmware packet information or a part thereof or an operation of batching the other pieces of the firmware packet information not transmitted, after the battery pack management apparatus 130 transmits some of the divided pieces of the firmware packet information.
Referring to
In an example, an order of transmitting each piece of the firmware packet information to the one or more battery module management apparatuses 120 during repetition of operation S221 may be designated as sequential transmission according to an order in which the firmware packet information is sequentially divided. In an example, an order of transmitting each piece of the firmware packet information to the one or more battery module management apparatuses 120 during repetition of operation S221 may be designated as an order in which the firmware packet information is transmitted from largest to smallest or an order in which the firmware packet information is transmitted from smallest to largest, depending on a size. In an example, an order of transmitting each piece of the firmware packet information to the one or more battery module management apparatuses 120 during repetition of operation S221 may be designated as following a scheme arbitrarily designed by a user. According to an embodiment disclosed herein, a total of N divided pieces of the firmware packet information (N is equal to or greater than 2) may be indicated by P1, P2, P3, . . . , PN according to an order in which they are transmitted.
The operating method of the battery management system may include operation S222 of transmitting, by the one or more battery module management apparatuses 120, battery data information of each monitored battery module to the battery pack management apparatus 130 according to a designated order when the battery pack management apparatus 130 one piece of firmware packet information (e.g., Pm in which 1≤m≤N) among pieces of the firmware packet information (e.g., P1, P2, P3, . . . , PN) according to a designated order. In an example, battery data information obtained by monitoring, by the battery module management apparatus #1, 121, #2122, #3123, or #4124, the battery module #1111, #2112, #3113, or #4114 connected thereto, may be referred to as Dm1, Dm2, Dm3, or Dm4. The battery management system according to an embodiment disclosed herein may perform operation S222 at a point before the battery pack management apparatus 130 transmits second firmware packet information (e.g., Pm+1), after transmitting first firmware packet information (e.g., Pm), to the one or more battery module management apparatuses 120. In this case, the one or more battery module management apparatuses 120 may perform an operation of transmitting monitored battery data information (e.g., Dm1, Dm2, Dm3, or Dm4) to the battery pack management apparatus 130 even during transmission of the divided pieces of the firmware packet information, such that the amount of battery data information of each battery module 110, which may be lost during batch update of the battery management system 100, may be reduced.
The operating method of the battery management system may further include operation S223 of transmitting the battery data information (e.g., the data Dm1, Dm2, Dm3, or Dm4) obtained by monitoring, by the battery module management apparatus 120, each connected battery module 110, to at least some of the other battery module management apparatuses according to an embodiment disclosed herein. According to a detailed example of the present disclosure, the operating method may further include an operation of, by the battery module management apparatus #1121, transmitting battery data information (e.g., data Dm1) obtained by monitoring the battery module #1111 to at least any one of the other battery pack management apparatuses #2122, #3123, and #4124. As various examples of operation S223, the battery module management apparatus #2122, #3123, or #4124 may operate in the same manner to the battery module management apparatus #1121 according to an example disclosed herein to further perform an operation of transmitting the monitored battery data information (e.g., the data Dm2, Dm3, or Dm4) of the battery module #2112, #3113, or #4114 to at least some of the other battery module management apparatuses.
The operating method of the battery management system may further include operation S224 of collectively encoding the battery data information (e.g., the data Dm1, Dm2, Dm3, or Dm4) obtained by monitoring each connected battery module 110 in the battery module management apparatus 120 according to an embodiment disclosed herein and the firmware packet information (e.g., Pm) received by the battery module management apparatus 120 from the battery pack management apparatus 130 in a designated order according to an embodiment disclosed herein to generate encoding information. As a detailed example of operation S224, an operation may be further performed in which the battery module management apparatus #1121 encodes the battery data information (e.g., the data Dm1) of the monitored battery module #1 and the received firmware packet information (e.g., Pm) to generate encoding information Im1 when the divided firmware packet information (e.g., Pm) is transmitted to the one or more battery module management apparatuses 120 from the battery pack management apparatus 130. As a detailed example of operation S224, an operation may be further performed in which the battery module management apparatus #2122, #3123, or #4124 operates in the same manner to the battery module management apparatus #1121 according to an embodiment disclosed herein to generate each encoding information Im2, Im3, or Im4.
The operating method of the battery management system may further include operation S225 of transmitting the encoding information (e.g., Im1, Im2, Im3, or Im4) generated in the one or more battery module management apparatuses 120 to at least some of the other battery module management apparatuses. In operation S225, when the encoding information (e.g., Im1, Im2, Im3, or Im4) generated by the one or more battery management modules 120 is transmitted, the encoding information may be further transmitted to the battery pack management apparatus 130.
According to a detailed example of operation S225, the battery module management apparatus #1121 may transmit the encoding information (e.g., Im1) generated in operation S224 to at least some of the other battery pack management apparatuses #2122, #3123, and #4124. As a detailed example of operation S225, an operation may be further performed in which the battery module management apparatus #2122, #3123, or #4124 operates in the same manner to the battery module management apparatus #1121 according to an embodiment disclosed herein to transmit the generated encoding information (e.g., Im2, Im3, or Im4) to at least some of the other battery module management apparatuses.
The operating method of the battery management system may further include operation S226 of identifying, by the battery module management apparatus according to an example disclosed herein, firmware packet information using battery data information and encoding information transmitted from the other battery module management apparatuses. As a detailed example of operation S226, the battery module management apparatus #2122 may receive battery data information (e.g., Dm1, Dm3, and/or Dm4) of respectively monitored battery modules from the battery module management apparatuses #1121, #3123, and/or #4124 according to an embodiment disclosed herein, and receive the encoding information (e.g., Im1, Im3, and/or Im4) generated in the battery module management apparatuses #1121, #3123, and/or #4124 according to an embodiment disclosed herein. In an example, when the battery data information (e.g., Dm1) monitored and the encoding information (e.g., Im1) generated in the battery module management apparatus #1121 are transmitted to the battery module management apparatus #2122 according to an embodiment disclosed herein, the battery module management apparatus #2122 may compare the received battery data information (e.g., Dm1) with a result of decoding the encoding information (e.g., Im1) to identify the firmware packet information (e.g., Pm) transmitted from the battery pack management apparatus 130. According to an embodiment disclosed herein, even when the battery module management apparatus #2122 fails to normally receive the firmware packet information (e.g., Pm) transmitted from the battery pack management apparatus 130, the battery module management apparatus #2122 may identify the firmware packet information (e.g., Pm) by using the battery data information (e.g., Dm1) and the encoding information (e.g., Im1) received from the battery module management apparatus #1121, such that the battery management system 100 may normally perform updating. As such, even when the battery pack management apparatus 130 is in a poor communication state with a part of the battery module management apparatus 120, the battery management system 100 may normally perform updating.
Referring to
In an example, when the firmware embedded in the battery pack management apparatus 130 is divided into a total of N (N is a natural number equal to or greater than 2) pieces of firmware packet information, firmware packet information transmitted mth in a designated order according to an embodiment disclosed herein may be referred to as Pm (1≤m≤N). In an example, when the battery pack management apparatus 130 transmits the firmware packet information (e.g., Pm), the battery pack management apparatus 130 may receive each monitored battery module data (e.g., Dm1, Dm2, Dm3, or Dm4) from the one or more battery module management apparatuses 120 before transmitting firmware packet information (e.g., Pm+1) of the next order. In an example, Tm1, Tm2, Tm3, tm1, tm2, tm3, tm4, tm5, tm6, tm7, tm8, and tm9 described below may correspond to data values indicating time.
In an example, during a time from Tm1 to tm1, the battery pack management apparatus 130 may transmit the beacon signal B to the one or more battery module management apparatuses 120 and transmit the firmware packet information Pm. Each battery module management apparatus #1121, #2122, #3123, or #4124 may be in a state of receiving information transmitted from the battery pack management apparatus 130.
In an example, during a time from tm1 to tm2, the battery module management apparatus #1121 may transmit the beacon signal B and battery data information Dm1 obtained by monitoring the battery module #1111 to the battery pack management apparatus 130, and may further transmit the same information to at least some of the other battery module management apparatuses #2122, #3123, and #4124. In this case, the battery pack management apparatus 130 or the other module management apparatuses #2122, #3123, and #4124 may be in a state of receiving information transmitted from the battery module management apparatus #1121.
In an example, during a time from tm2 to tm3, the battery module management apparatus #2122 may transmit the beacon signal B and the battery data information Dm2 obtained by monitoring the battery module #2122 to the battery pack management apparatus 130, and may further transmit the same information to at least some of the other battery module management apparatuses #1121, #3123, and #4124. In this case, the battery pack management apparatus 130 or the other module management apparatuses #1121, #3123, and #4124 may be in a state of receiving information transmitted from the battery module management apparatus #2122.
In an example, during a time from tm3 to tm4, the battery module management apparatus #3123 may transmit the beacon signal B and battery data information Dm3 obtained by monitoring the battery module #3113 to the battery pack management apparatus 130, and may further transmit the same information to at least some of the other battery module management apparatuses #1121, #2122, and #4124. In this case, the battery pack management apparatus 130 or the other module management apparatuses #1121, #2122, and #4124 may be in a state of receiving information transmitted from the battery module management apparatus #3123.
In an example, during a time from tm5 to Tm2, the battery module management apparatus #4124 may transmit the beacon signal B and battery data information Dm4 obtained by monitoring the battery module #4114 to the battery pack management apparatus 130, and may further transmit the same information to at least some of the other battery module management apparatuses #1121, #2122, and #3123. In this case, the battery pack management apparatus 130 or the other module management apparatuses #1121, #2122, and #3123 may be in a state of receiving information transmitted from the battery module management apparatus #4124.
According to an embodiment disclosed herein, when the battery pack management apparatus 130 or any one of the one or more battery module management apparatuses 120 is in a state of transmitting data (e.g., Pm, Dm1, Dm2, Dm3, Dm4, etc.), the other apparatuses may be in a state of receiving transmitted data. According to an embodiment disclosed herein, an order in which the battery pack management apparatus 130 or any one of the one or more battery module management apparatuses 120 transmits the data (e.g., Pm, Dm1, Dm2, Dm3, Dm4, etc.) may be changed and designated at random. According to an embodiment disclosed herein, even when the number of battery module management apparatuses included in the battery management system 100 changes, an operation according to an embodiment disclosed herein may be performed in the same manner.
Referring to
In an example, the battery module management apparatus #1121 may encode the battery data information Dm1 obtained by monitoring the battery module #1111 and the firmware packet information (e.g., Pm) received from the battery pack management apparatus 130 together to generate the encoding information Im1. In an example, when the battery module management apparatus #1121 generates the encoding information Im1, the battery module management apparatus #1121 may transmit the encoding information Im1 to at least some of the other battery module management apparatuses #2122, #3123, and #4124 during a time from Tm2 to tm6. In this case, the other module management apparatuses #2122, #3123, and #4124 may be in a state of receiving information transmitted from the battery module management apparatus #1121.
In an example, the battery module management apparatus #2122 may encode the battery data information Dm2 obtained by monitoring the battery module #2112 and the firmware packet information (e.g., Pm) received from the battery pack management apparatus 130 together to generate the encoding information Im2. In an example, when the battery module management apparatus #2122 generates the encoding information Im2, the battery module management apparatus #2122 may transmit the encoding information Im2 to at least some of the other battery module management apparatuses #1121, #3123, and #4124 during a time from tm6 to tm7. In this case, the other module management apparatuses #1121, #3123, and #4124 may be in a state of receiving information transmitted from the battery module management apparatus #2122.
In an example, the battery module management apparatus #3123 may encode the battery data information Dm3 obtained by monitoring the battery module #3113 and the firmware packet information (e.g., Pm) received from the battery pack management apparatus 130 together to generate the encoding information Im3. In an example, when the battery module management apparatus #3123 generates the encoding information Im3, the battery module management apparatus #3123 may transmit the encoding information Im3 to at least some of the other battery module management apparatuses #1121, #2122, and #4124 during a time from tm7 to tm8. In this case, the other module management apparatuses #1121, #2122, and #4124 may be in a state of receiving information transmitted from the battery module management apparatus #3123.
In an example, the battery module management apparatus #4124 may encode the battery data information Dm4 obtained by monitoring the battery module #4114 and the firmware packet information (e.g., Pm) received from the battery pack management apparatus 130 together to generate the encoding information Im4. In an example, when the battery module management apparatus #4124 generates the encoding information Im4, the battery module management apparatus #4124 may transmit the encoding information Im4 to at least some of the other battery module management apparatuses #1121, #2122, and #3123 during a time from tm8 to Tm3. In this case, the other module management apparatuses #1121, #2122, and #3123 may be in a state of receiving information transmitted from the battery module management apparatus #4124.
When the one or more battery module management apparatuses receive the battery data information (e.g., Dm1, Dm2, Dm3, or Dm4) and the encoding information (e.g., Im1, Im2, Im3, or Im4) from the other battery module management apparatuses, the firmware packet information (e.g., Pm) may be identified using the received battery data information and encoding information. In an example, when the battery module management apparatus #2122 receives the battery data information (e.g., Dm2) and the encoding information (e.g., Im2) from the battery module management apparatus #1121, the received encoding information (e.g., Im2) may be decoded and decoding result data may be compared with the battery data information (e.g., Dm2) to identify the firmware packet information (e.g., Pm). In this case, even when the battery module management apparatus #2122 may not be able to normally perform data communication with the battery pack management apparatus 130 and thus may fail to directly receive firmware packet information, the firmware packet information may be identified by using the received battery data information and encoding information, thereby normally performing updating of the battery management system 100. In an example, the battery module management apparatus #1121, #3123, or #4124 may operate in the same manner to the battery module management apparatus #2122 according to an embodiment disclosed herein.
The controller 310 may be a hardware device such as a processor or a central processing unit (CPU) or a program implemented by the hardware device. The controller 310 may be connected to components of the battery management system to perform an overall function of the battery management system. In an embodiment, the controller 310 may control the battery module management apparatus 120 to monitor a state of each connected battery module and to transmit monitored battery data information to the battery pack management apparatus 130. In an embodiment, the controller may control the battery pack management apparatus 130 to divide the firmware embedded in the battery pack management apparatus to generate firmware packet information and to transmit the divided firmware packet information to each battery module management apparatus 120.
In an embodiment, the controller 310 may be further configured to, by controlling the battery pack management apparatus 130, transmit the non-divided firmware to the one or more battery module management apparatuses 120 when a firmware batch download command is input according to a scheme designated in the battery pack management apparatus. In this case, a description of
In an embodiment, the controller 310 may be further configured to, by controlling the battery pack management apparatus 130, transmit length information of the firmware packet information to the battery module management apparatus to be stored. In this case, a description of
In an embodiment, the controller 310 may be further configured to, by controlling the battery module management apparatus 120, transmit the monitored battery data information to at least some of the other battery module management apparatuses. In this case, a description of
In an embodiment, the controller 310 may be further configured to, by controlling the battery module management apparatus 120, encode the monitored battery data information together with the firmware packet information from the battery pack management apparatus 130 to generate encoding information, and to transmit the generated encoding information to at least some of the other battery module management apparatuses. In this case, a description of
In an embodiment, the controller 310 may be further configured to, by controlling the battery module management apparatus 120, identify the divided firmware packet information transmitted by the battery pack management apparatus 130 using the battery data information and the encoding information received from the other battery module management apparatuses. In this case, a description of
The controller 310 may control each component of the battery management system and to this end, the controller 310 may include a battery module management apparatus controller 320 and/or a battery pack management apparatus controller 330. Components included in the controller 310 may be implemented with individual devices (or programs) or as one integrated module.
Even though all components constituting an embodiment disclosed herein have been described above as being combined into one or operating in combination, the embodiments disclosed herein are not necessarily limited to the embodiments. That is, within the object scope of the embodiments disclosed herein, all the components may operate by being selectively combined into one or more.
Referring to
The MCU 32 may be a processor that executes various programs (e.g., a feature calculation program, a class classification and lifespan estimation program, etc.) stored in the memory 34, processes various data including voltage, current, etc., of a battery cell through these programs, and executes the above-described functions of the battery management apparatus shown in
The memory 34 may store various programs regarding feature calculation, class classification, and lifespan estimation of the battery cell. Moreover, the memory 34 may store various data such as a voltage, a current, feature data, etc., of each battery cell.
The memory 34 may be provided in plural, depending on a need. The memory 34 may be volatile memory or non-volatile memory. For the memory 34 as the volatile memory, random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), etc., may be used. For the memory 34 as the nonvolatile memory, read only memory (ROM), programmable ROM (PROM), electrically alterable ROM (EAROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), flash memory, etc., may be used. The above-listed examples of the memory 34 are merely examples and are not limited thereto.
The input/output I/F 36 may provide an interface for transmitting and receiving data by connecting an input device (not shown) such as a keyboard, a mouse, a touch panel, etc., and an output device such as a display (not shown), etc., to the MCU 32.
The communication I/F 38, which is a component capable of transmitting and receiving various data to and from a server, may be various devices capable of supporting wired or wireless communication. For example, a program for feature calculation, class classification, and lifespan estimation for a battery cell or various data, etc., may be transmitted and received to and from a separately provided external server through the communication I/F 38.
As such, a computer program according to an embodiment disclosed herein may be recorded in the memory 34 and processed by the MCU 32, thus being implemented as a module that performs functions shown in
Moreover, terms such as “include”, “constitute” or “have” described above may mean that the corresponding component may be inherent unless otherwise stated, and thus should be construed as further including other components rather than excluding other components. All terms including technical or scientific terms have the same meanings as those generally understood by those of ordinary skill in the art to which the embodiments disclosed herein pertain, unless defined otherwise. The terms used generally like terms defined in dictionaries should be interpreted as having meanings that are the same as the contextual meanings of the relevant technology and should not be interpreted as having ideal or excessively formal meanings unless they are clearly defined in the present document.
The above description is merely illustrative of the technical idea of the present disclosure, and various modifications and variations will be possible without departing from the essential characteristics of embodiments of the present disclosure by those of ordinary skill in the art to which the embodiments disclosed herein pertains. Therefore, the embodiments disclosed herein are intended for description rather than limitation of the technical spirit of the embodiments disclosed herein and the scope of the technical spirit of the present disclosure is not limited by these embodiments disclosed herein. The protection scope of the technical spirit disclosed herein should be interpreted by the following claims, and all technical spirits within the same range should be understood to be included in the range of the present document.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0132752 | Oct 2021 | KR | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2022/015026 | 10/6/2022 | WO |
