Battery management device and operation method thereof

Abstract

A battery management device according to one embodiment disclosed in the present document may comprise: a memory for storing at least one instruction; and at least one processor for executing the at least one instruction, wherein the at least one processor can identify a first reset count corresponding to a first operating state of the battery management device and, when the first reset count is greater than a reference reset count, diagnose the state of the battery management device on the basis of an operating time of one or more pieces of software executed after the first operating state.

Description

Battery management device and method of operation thereof

[0001] Cross-citation with related applications

[0002] The present invention claims the benefit of priority based on Korean Patent Application No. 10-2024-0132596 filed on September 30, 2024, and includes all contents disclosed in the document of said Korean patent application as part of this specification.

[0003] Technology field

[0004] The embodiments disclosed in this document relate to a battery management device and a method of operating the same.

[0005] Recently, active research and development on secondary batteries has been underway. Here, the term "secondary battery" refers to a rechargeable battery, encompassing conventional Ni / Cd and Ni / MH batteries as well as the more recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of significantly higher energy density compared to conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form factor, making them suitable for use as power sources for mobile devices. Recently, their scope of application has expanded to include electric vehicles, drawing attention as a next-generation energy storage medium.

[0006] As the industrial sectors utilizing batteries expand, Battery Management Systems (BMS) for diagnosing battery safety are also evolving. BMS can diagnose battery performance using various diagnostic algorithms and perform appropriate control based on the battery's condition. BMS can diagnose the presence of abnormal battery cells. Here, abnormalities can include all causes that may lead to ignition due to damage or aging of the battery itself.

[0007] Due to problems with the BMS hardware or software running inside the BMS, an infinite reset state may occur where the booting process to run the BMS repeats infinitely. If the BMS enters an infinite reset state, it consumes high current, which can cause the battery pack to enter a low voltage state.

[0008] However, conventionally, there was no technology to detect the infinite reset state of the BMS in advance and prevent the battery pack from falling into a low-voltage state.

[0009] The technical problems of the embodiments disclosed in this document are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by those skilled in the art from the description below.

[0010] A battery management device according to one embodiment disclosed in this document may include a memory for storing at least one instruction; and at least one processor for executing said at least one instruction, and said at least one processor may identify a first reset count corresponding to a first operating state of the battery management device and, when the first reset count is greater than a reference reset count, diagnose the state of the battery management device based on the operating time of one or more software executed after the first operating state.

[0011] In one embodiment, the processor can determine whether the operating time is less than a threshold time, and if the operating time is less than the threshold time, diagnose the state of the battery management device based on the result of determining whether the first reset count exceeds the threshold count.

[0012] In one embodiment, the processor can diagnose that the battery management device is in an infinite reset state when the first reset count exceeds the threshold count.

[0013] In one embodiment, the first operating state may include a boot state in which the battery management device is booting.

[0014] In one embodiment, the processor may generate a control signal that controls the operation state of the battery management device to switch to a second operation state when the battery management device is diagnosed as having an abnormality.

[0015] In one embodiment, the second operating state may include a sleep mode state.

[0016] In one embodiment, the threshold time may be set based on the normal operating time of the software.

[0017] A method of operation of a battery management device according to an embodiment disclosed in this document may include: an operation of identifying a first reset count corresponding to a first operating state of the battery management device; and an operation of diagnosing the state of the battery management device based on the operating time of one or more software executed after the first operating state when the first reset count is greater than a reference reset count.

[0018] In one embodiment, the diagnosing operation may include an operation of determining whether the operating time is less than a threshold time, and an operation of diagnosing the state of the battery management device based on the result of comparing whether the first reset count exceeds the threshold count when the operating time is less than the threshold time.

[0019] In one embodiment, the diagnosing operation may include diagnosing that the battery management device is in an infinite reset state when the first reset count exceeds the threshold count.

[0020] In one embodiment, the first operating state may include a boot state in which the battery management device is booting.

[0021] In one embodiment, the method of operating the battery management device may further include an operation of generating a control signal to control the operation state of the battery management device to switch to a second operation state when the battery management device is diagnosed as having an abnormality.

[0022] In one embodiment, the second operating state may include a sleep mode state.

[0023] In one embodiment, the threshold time may be set based on the normal operating time of the software.

[0024] A battery management device and a method of operation thereof according to various embodiments disclosed in this document can determine whether the BMS is in an infinite reset state based on the boot state of the BMS and the operating time of software executed after booting.

[0025] A battery management device and a method of operation thereof according to various embodiments disclosed in this document can prevent the battery pack from becoming low voltage by switching the operating state of the BMS to a sleep mode state when the BMS is diagnosed as being in an infinite reset state.

[0026] The effects of the battery management device and the method of operation thereof disclosed in this document are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art in accordance with the disclosure of this document.

[0027] FIG. 1 illustrates a battery pack according to one embodiment disclosed in this document.

[0028] FIG. 2 is a flowchart illustrating the operation method of a battery management device according to one embodiment disclosed in this document.

[0029] FIG. 3 is a flowchart illustrating the operation 230 included in FIG. 2.

[0030] FIG. 4 illustrates a computing system for executing operations of a battery management device according to an embodiment disclosed in this document.

[0031] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components.

[0032] Hereinafter, embodiments of the present invention are described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments and should be understood to include various modifications, equivalents, and / or alternatives of the embodiments of the present invention.

[0033] The embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. 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 said items unless the relevant context clearly indicates otherwise.

[0034] In this document, each of the phrases 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 of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” “first,” “second,” “A,” “B,” “(a),” or “(b)” may be used simply to distinguish a component from another component and, unless specifically stated otherwise, do not limit the components in any other aspect (e.g., importance or order).

[0035] In this document, where it is stated that any (e.g., 1) component is "connected," "coupled," or "joined" to another (e.g., 2) component, with or without the terms "functionally" or "communicationly," or where it is stated that the component is "coupled" or "connected," it means that the component may be connected to the other component directly (e.g., by wire or wirelessly) or indirectly (e.g., through a 3) component.

[0036] Methods according to the various embodiments disclosed in this document may be provided as part of a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory, CD-ROM) or distributed online (e.g., download or upload) through an application store or directly between two user devices. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0037] According to the embodiments disclosed in this document, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to the embodiments disclosed in this document, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the components of the multiple components in the same or similar manner as those performed by the corresponding components among the multiple components prior to the integration. According to the embodiments disclosed in this document, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0038] FIG. 1 illustrates a battery pack according to one embodiment disclosed in this document.

[0039] Referring to FIG. 1, the battery pack (1) may be included in an electronic device. Here, the electronic device may be a mobile device (e.g., mobile phone, laptop computer, smartphone, smart pad), an electric vehicle (e.g., EV (electric vehicle), HEV (hybrid EV), PHEV (plug-in HEV), FCEV (fuel cell EV)), an energy storage system (ESS), or a battery swapping system (BSS).

[0040] The battery pack (1) may include a battery management device (10) and battery units (120, 140, 160). Here, each of the battery units (120, 140, 160) may correspond to a battery module. Although the battery units are depicted as three in FIG. 1, this is for convenience of explanation only, and the battery pack (1) may include one or more battery units. Also, although only the battery cells (121, 122, 123) included in the first battery unit (120) are depicted in FIG. 1, this is for convenience of explanation only, and the second battery unit (140) and the third battery unit (160) may also include multiple battery cells. Additionally, although the plurality of battery cells (121, 122, 123) included in the first battery unit (120) in FIG. 1 are shown as being three, they are not limited thereto, and each of the battery cells (121, 122, 123) may be configured to include n (n is a natural number greater than or equal to 2) battery cells.

[0041] According to various embodiments, when the battery pack (1) has a Cell To Pack (CTP) structure, the battery pack (1) may be configured to include a plurality of battery cells (121, 122, 123) without distinction of battery units.

[0042] A battery management device (10) can obtain values ​​(or information) related to the state of battery units (120, 140, 160) and battery cells (121, 122, 123) included therein. In one embodiment, the values ​​related to the state may include one or more values ​​for the voltage, current, resistance, state of charge (SOC), state of health (SOH), or temperature, or a combination thereof, of each of the battery units (120, 140, 160). In one embodiment, the values ​​related to the state may include one or more values ​​for the voltage, current, resistance, state of charge (SOC), state of health (SOH), or temperature, or a combination thereof, of each of the battery cells (121, 122, 123). Hereinafter, the values ​​related to the state may be referred to as 'state values'.

[0043] A battery management device (10) may be booted to execute at least one program for diagnosing the status of each of the battery units (120, 140, 160) and / or battery cells (121, 122, 123). For example, if a battery pack (1) is included in an electric vehicle, when the electric vehicle is started, the battery management device (10) included in the battery pack (1) may start booting by executing booting software that drives itself. However, the battery management device (10) may be in an infinite reset state in which the booting process is continuously repeated by the hardware of the battery management device (10), the software executed in the battery management device (10), or an external device. Here, the infinite reset state may include cases where the booting process is continuously repeated more than a predetermined number of times, and cases where, after the booting process is completed, software for battery diagnosis (e.g., SOX calculation and software for cell voltage measurement) is not executed normally and the booting process proceeds again.

[0044] In one embodiment, the battery management device (10) may be included in a BMS capable of diagnosing battery cells included in an electronic device, and operations performed by the battery management device (10) may be performed in the BMS. In one embodiment, the battery management device (10) may be included in a server or a charger / discharger capable of diagnosing battery cells outside the electronic device, and operations performed by the battery management device (10) may be performed in an external server or charger / discharger.

[0045] Hereinafter, for the convenience of explanation, each component included in the battery management device (10) will be described as performing an operation to diagnose whether the battery management device (10) is abnormal.

[0046] The battery management device (10) may include a memory (100) and a processor (102). According to an embodiment, the battery management device (10) illustrated in FIG. 1 may further include at least one component (e.g., a sensor, a display, an input device, or an output device) in addition to the components illustrated in FIG. 1.

[0047] The memory (100) may include volatile memory and / or non-volatile memory. In one embodiment, the memory (100) may store at least one instruction for executing a processor (102). The instruction may cause the battery management device (10) to perform operations defined by the instruction when executed by the processor (102). In one embodiment, the memory (100) may include one or more software. Here, the one or more software may include software for booting the battery management device (10) and one or more software for battery diagnosis (e.g., SOX calculation and software for measuring cell voltage).

[0048] The processor (102) can execute at least one instruction stored in memory (100). In one embodiment, the battery management device (10) may correspond to a BMS, and the processor (102) may correspond to or be included in a Micro Control Unit (MCU) that performs hardware control and software operation of the BMS. The processor (102) can perform the following operations by executing at least one instruction stored in memory (100).

[0049] The processor (102) can identify a first reset count corresponding to a first operating state of the battery management device (10). Here, the first operating state may include a state in which the battery management device (10) is booting, and the first reset count may correspond to a count that identifies whether the first operating state is in progress for the nth (n: natural number) boot. For example, if the battery management device (10) repeats booting three times, the first reset count may be identified as 3.

[0050] In one embodiment, the first reset count may be identified by a watchdog timer (WDT: WatchDog Timer, not shown). The watchdog timer (not shown) may be a software timer capable of monitoring whether a specific device is operating normally and taking action thereon. The watchdog timer (not shown) may monitor an infinite reset state of the battery management device (10) due to a hardware and / or software error of the battery management device (10). Software that executes the watchdog timer (not shown) may be stored in memory (100), and a processor (102) may execute said software to identify whether the battery management device (10) is booted and rebooted, and identify the first reset count based on the number of times it has been rebooted.

[0051] In one embodiment, the reset count may be reset to 0 when booting is successfully completed, and in another embodiment, the reset count may have a value that accumulates whenever a reboot occurs regardless of whether booting is completed. The processor (102) can determine whether the battery management device (10) is in a repeating state by identifying the first reset count.

[0052] The processor (102) can diagnose the state of the battery management device (10) based on the operating time of one or more software executed after the first operating state when the first reset count is greater than the reference reset count. Here, the reference reset count can be arbitrarily set by a setter. For example, if the reference reset count is set to 1, the first reset count can be identified as 2 when the booting process of the battery management device (10) is performed 2 times. In this case, the processor (102) can determine that the first reset count has exceeded the reference reset count and can proceed with the following steps to determine whether there is an infinite reset.

[0053] In one embodiment, the processor (102) can determine whether the operating time is less than a threshold time. According to the embodiment, the operating time may be the time during which each of the software for battery diagnosis (e.g., SOX calculation, and voltage measurement) is executed, in addition to the time when the battery management device (10) boots up. Additionally, the threshold time may be set based on the time during which each of one or more software is operated normally. In one embodiment, the threshold time may be set by adding the init time for each of one or more software and the time during which the longer cycle of the main loop is repeated m times (m: natural number). In one embodiment, the threshold time may be set based on the cycle of the function (e.g., SOX calculation function) corresponding to the longest cycle among a plurality of functions that are repeated at regular intervals included in a specific software. For example, if the cycle of the SOX calculation function is 1 second, the threshold time may be set to 10 seconds, which is 10 times the cycle of the SOX calculation function. The processor (102) can determine whether one or more software stored in memory (100) is operating normally after the battery management device (10) has finished booting by comparing the operating time and threshold value. If the operating time of the software is less than the threshold time even though the battery management device (10) has finished booting normally, the processor (102) can diagnose that the battery management device (10) has been rebooted.

[0054] In one embodiment, the processor (102) can determine whether the first reset count exceeds the threshold count when the operating time is less than the threshold time. The processor (102) can diagnose the state of the battery management device (10) based on the result of determining whether the first reset count exceeds the threshold count when the operating time is less than the threshold time. The processor (102) can diagnose that the battery management device (10) is in an infinite reset state when the first reset count exceeds the threshold count. Here, the threshold count can be set by a setter to prevent the battery management device (10) from being misdiagnosed as being in an infinite reset state even though it is booting normally. For example, the threshold count can be set to 100, and when the first reset count exceeds the threshold count of 100, the processor (102) can diagnose that the battery management device (10) is in an infinite reset state.

[0055] The processor (102) can generate a control signal to control the operation state of the battery management device (10) to switch to a second operation state when the battery management device (10) is diagnosed as having a defect (e.g., diagnosed as being in an infinite reset state). Here, the second operation state may include a sleep mode state in which the battery management device (10) stops operating. By switching the operation state of the battery management device (10) to a sleep mode state when the battery management device (10) is diagnosed as having a defect, the processor (102) can prevent a low voltage state of the battery pack (1) that may occur due to the power of the battery pack (1) being consumed by the infinite reset state.

[0056] In one embodiment, the processor (102) may include a central processing unit, an application processor, a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor. In one embodiment, the processor (102) may execute software to control at least one other component (e.g., a hardware or software component) of the battery management device (10) connected to the processor (102) and may perform various data processing or operations.

[0057] FIG. 2 is a flowchart illustrating the operation method of a battery management device according to one embodiment disclosed in this document.

[0058] Referring to FIG. 2, in operation 200, the processor (102) can identify a first operating state of the battery management device (10). Here, the first operating state may include a state in which the battery management device (10) is booting.

[0059] In operation 210, the processor (102) can identify a first reset count (C1) corresponding to a first operating state. Here, the first reset count (C1) may correspond to a count that identifies whether the first operating state is the nth (n: natural number) boot state.

[0060] In operation 220, the processor (102) has a first reset count (C1) and a reference reset count (C R ) can be compared.

[0061] In operation 230, the processor (102) determines that the first reset count (C1) is a reference reset count (C R If ) exceeds (operation 220, C R The state of the battery management device can be diagnosed based on the operating time and threshold time during which at least one software is executed after the first operating state ≥C1).

[0062] In operation 240, the processor (102) determines that the first reset count (C1) is a reference reset count (C R If ) or less (operation 220, C1>C R ), the booting process of the battery management device (10) can be diagnosed as normal.

[0063] FIG. 3 is a flowchart illustrating the operation 230 included in FIG. 2.

[0064] Referring to FIG. 3, the operation 230 included in FIG. 2 may include operations 232 to 238.

[0065] In operation 232, the processor (102) operates for an operating time (T O ) is the critical time (T TH It can determine whether it is less than ). The processor (102) can determine whether the operating time (T) O ) is the critical time (T TH If ) or more (Operation 232, T O ≥T TH ), return to operation 240 and diagnose that the battery management device (10) is operating normally.

[0066] In operation 234, the processor (102) operates for an operating time (T O ) is the critical time (T TH If less than ) (Operation 232, T O <T TH ), the first reset count (C1) is the threshold count (C TH It can determine whether it exceeds ).

[0067] In operation 236, the processor (102) determines that the first reset count (C1) is a threshold count (C TH If ) exceeds (action 234, C1>C TH ), the battery management device (10) can be diagnosed as being in an infinite reset state.

[0068] According to an embodiment, the processor (102) can generate a control signal to switch the operating state of the battery management device (10) to a sleep mode state when the battery management device (10) is diagnosed as being in an infinite reset state.

[0069] In operation 238, the processor (102) determines that the first reset count (C1) is a threshold count (C TH If ) or less (C1≤C TH ), the first reset count can be updated by increasing the reset count. For example, if the first reset count is C1, the updated first reset count (C'1) can be (C1+1). After updating the first reset count, the processor (102) can return to operation 240 and diagnose that the battery management device (10) is operating normally.

[0070] FIG. 4 illustrates a computing system that executes the operations of a battery management device according to one embodiment disclosed in this document.

[0071] Referring to FIG. 4, a computing system (40) according to one embodiment disclosed in this document may include an MCU (400), memory (410), an input / output I / F (420) and a communication I / F (430).

[0072] The MCU (400) may be a processor that executes various programs (e.g., battery diagnostic programs) stored in memory (410), processes various data from these programs, and performs the functions of the battery management device (10) shown in FIGS. 1 to 3.

[0073] The memory (410) can store various programs regarding the operation of the battery management device (10). In addition, the memory (410) can store operation data of the battery management device (10).

[0074] These memories (410) may be provided in multiple quantities as needed. The memory (100) may be a volatile memory or a non-volatile memory. As a volatile memory, the memory (410) may use RAM, DRAM, SRAM, etc. As a non-volatile memory, the memory (410) may use ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. The memories (100) listed above are merely examples and are not limited to these examples.

[0075] The input / output I / F (420) can provide an interface that enables data transmission and reception between an input device (not shown), such as a keyboard, mouse, or touch panel, and an output device (not shown), such as a display, and the MCU (400).

[0076] The communication I / F (430) is configured to transmit and receive various data to and from a server and may be various devices capable of supporting wired or wireless communication. For example, through the communication I / F (430), a program for diagnosing abnormalities or various data (e.g., status values) can be transmitted and received from a separately provided external server.

[0077] Terms such as "include," "compose," or "have" as used above, unless specifically stated otherwise, mean that the relevant component may be inherent; therefore, they should be interpreted as allowing for the inclusion of additional components rather than excluding them. All terms, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the embodiments disclosed in this document pertain, unless otherwise defined. Commonly used terms, such as those defined in advance, should be interpreted in accordance with their meaning in the context of the relevant technology and, unless explicitly defined in this document, should not be interpreted in an ideal or overly formal sense.

[0078] The foregoing description is merely an illustrative explanation of the technical concept disclosed in this document, and a person skilled in the art to which the embodiments disclosed in this document pertain can make various modifications and variations within the scope of the essential characteristics of the embodiments disclosed in this document. Accordingly, the embodiments disclosed in this document are intended to explain, not limit, the technical concept of the embodiments disclosed in this document, and the scope of the technical concept disclosed in this document is not limited by these embodiments. The scope of protection of the technical concept disclosed in this document shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of this document.

Claims

1. In a battery management device, Memory for storing at least one instruction; and It includes at least one processor that executes the above at least one instruction, and The above-mentioned at least one processor is, Identifying a first reset count corresponding to a first operating state of the battery management device, and When the first reset count is greater than the reference reset count, diagnosing the state of the battery management device based on the operating time of one or more software executed after the first operating state. Battery management device.

2. In Claim 1, The above processor is, Determining whether the above operating time is less than the threshold time, and Diagnosing the state of the battery management device based on the result of determining whether the first reset count exceeds the threshold count when the above operating time is less than the above threshold time, Battery management device.

3. In Claim 2, The above processor is, If the first reset count exceeds the threshold count, the battery management device diagnoses that it is in an infinite reset state. Battery management device.

4. In Claim 1, The above first operating state includes a boot state in which the battery management device is booting. Battery management device.

5. In Claim 4, The above processor is, When the above battery management device is diagnosed as having a malfunction, a control signal is generated to control the operation state of the above battery management device to switch to a second operation state. Battery management device.

6. In Claim 5, The above second operating state includes a sleep mode state. Battery management device.

7. In Claim 1, The above threshold time is set based on the normal operating time of the software, Battery management device.

8. An operation to identify a first reset count corresponding to a first operating state of a battery management device; and The operation includes diagnosing the state of the battery management device based on the operating time of one or more software executed after the first operating state when the first reset count is greater than the reference reset count. Method of operation of a battery management device.

9. In Claim 8, The above-mentioned diagnostic operation is, An operation to determine whether the above operating time is less than a threshold time, and A method comprising diagnosing the state of the battery management device based on the result of comparing whether the first reset count exceeds the threshold count when the above operating time is less than the above threshold time. Method of operation of a battery management device.

10. In Claim 9, The above-mentioned diagnostic operation is, The operation includes diagnosing that the battery management device is in an infinite reset state when the first reset count exceeds the threshold count. Method of operation of a battery management device.

11. In Claim 8, The above first operating state includes a boot state in which the battery management device is booting. Method of operation of a battery management device.

12. In Claim 11, The operation further includes generating a control signal to control the operation state of the battery management device to switch to a second operation state when the battery management device is diagnosed as having an abnormality. Method of operation of a battery management device.

13. In Claim 12, The above second operating state includes a sleep mode state. Method of operation of a battery management device.

14. In Claim 8, The above threshold time is set based on the normal operating time of the software, Method of operation of a battery management device.

Images