Battery management device and its operating method

JP7899968B2Active Publication Date: 2026-08-04LG ENERGY SOLUTION LTD
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
LG ENERGY SOLUTION LTD
Filing Date
2023-08-09
Publication Date
2026-08-04

AI Technical Summary

Benefits of technology

【0020】 本文書に開示される一実施形態に係る電池管理装置およびその動作方法によると、電池データのうち、閾値を超えた電池データの識別情報を記録し、閾値時間を流動的に変更して電池データ分析の効率性を向上させることができる。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007899968000001
    Figure 0007899968000001
  • Figure 0007899968000002
    Figure 0007899968000002
  • Figure 0007899968000003
    Figure 0007899968000003
Patent Text Reader

Abstract

A battery management device according to one embodiment disclosed herein may include a memory and a controller that determines whether battery data exceeds a threshold value and whether the duration of the battery data that exceeds the threshold value exceeds a threshold time, diagnoses the battery data based on the determination result, and records identification information of the battery data in the memory based on the determination result.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application claims the benefit of priority based on Korean Patent Application No. 10-2022-0115949, filed on September 14, 2022, and all the contents disclosed in the literature of the patent application are incorporated herein by reference in their entirety. The embodiments disclosed in this document relate to a battery management device and an operating method thereof.

Background Art

[0002] An electric vehicle receives electrical supply from the outside to charge a battery, and then obtains power by driving a motor with the voltage charged in the battery. The battery of an electric vehicle may generate heat due to a chemical reaction occurring during the charging and discharging of electricity, and such heat may damage the performance and lifespan of the battery. Therefore, a battery management device (BMS, Battery Management System) that monitors the temperature, voltage, and current of the battery is driven to diagnose and control the state of the battery.

[0003] However, even if there is battery data that continuously exceeds a threshold value among the battery data measured by the battery management device during the process of diagnosing the battery, if the duration exceeding the threshold value is less than the threshold time, there is a problem that the battery data cannot be diagnosed and is overlooked. Generally, the threshold time for diagnosing a battery is set to a fixed value, but in order to change the fixed threshold time, the software of the vehicle to which the battery is attached must be updated, which causes a problem of significant time and cost during the update process.

Summary of the Invention

Problems to be Solved by the Invention

[0004] An object of an embodiment disclosed in this document is to provide a battery data management device and an operating method thereof that can record identification information of battery data exceeding a threshold value among battery data, and improve the efficiency of battery data analysis by changing the threshold time dynamically.

[0005] The technical problems of the embodiments disclosed in this document are not limited to those mentioned above, and other technical problems not mentioned can be clearly understood by those skilled in the art from the following description. [Means for solving the problem]

[0006] A battery management device according to one embodiment disclosed in this document may include a memory and a controller that determines whether battery data exceeds a threshold and whether the duration of the battery data exceeding the threshold exceeds a threshold time, diagnoses the battery data based on the determination result, and records identification information of the battery data in the memory based on the determination result.

[0007] According to one embodiment, if the duration of battery data exceeding the threshold is less than the threshold time, the controller can accumulate identification information of the battery data exceeding the threshold and record it in the memory.

[0008] According to one embodiment, the controller can accumulate and record in the memory the duration of battery data exceeding the threshold and the number of times battery data exceeding the threshold occurs.

[0009] According to one embodiment, the controller can calculate the cumulative duration of battery data exceeding the threshold based on the cumulative duration of recorded battery data exceeding the threshold, and calculate the cumulative number of occurrences of battery data exceeding the threshold based on the cumulative number of occurrences of battery data exceeding the threshold.

[0010] According to one embodiment, the controller can determine whether the cumulative count is equal to or greater than a reference value, and can change the threshold time based on whether the cumulative count is equal to or greater than a reference value.

[0011] According to one embodiment, if the cumulative count is equal to or greater than a reference value, the controller can recalculate the threshold time by dividing the cumulative time by the cumulative count.

[0012] According to one embodiment, the controller can determine whether the duration of battery data exceeding the threshold exceeds the threshold time, based on the recalculated threshold time.

[0013] An operating method for a battery management device according to one embodiment disclosed herein includes the steps of: determining whether battery data exceeds a threshold; determining whether the duration of the battery data that exceeds the threshold exceeds a threshold time; diagnosing the battery data based on the determination; and recording identification information of the battery data based on the determination.

[0014] According to one embodiment, the step of recording the identification information of the battery data based on the result of the determination can be performed by accumulating and recording the identification information of the battery data that exceeded the threshold if the duration of the battery data that exceeded the threshold is less than the threshold time.

[0015] According to one embodiment, the step of recording the identification information of the battery data based on the result of the determination can be used to record the duration of the battery data that exceeded the threshold and the number of times the battery data that exceeded the threshold occurred.

[0016] According to one embodiment, the step of recording the identification information of the battery data based on the result of the determination can be used to calculate the cumulative time of the battery data that has exceeded the threshold based on the cumulative duration of the recorded battery data that has exceeded the threshold, and to calculate the cumulative number of times the battery data has exceeded the threshold based on the cumulative number of times the battery data that has exceeded the threshold has occurred.

[0017] According to one embodiment, the further step may include determining whether the cumulative number of times is equal to or greater than a reference value, and changing the threshold time based on whether the cumulative number of times is equal to or greater than a reference value.

[0018] According to one embodiment, the step of determining whether the cumulative count is equal to or greater than a reference value and changing the threshold time based on whether the cumulative count is equal to or greater than a reference value can be recalculated by dividing the cumulative time by the cumulative count if the cumulative count is equal to or greater than a reference value.

[0019] According to one embodiment, the step of determining whether the cumulative number of operations is equal to or greater than a reference value and changing the threshold time based on whether the cumulative number of operations is equal to or greater than a reference value can determine, based on the recalculated threshold time, whether the duration of battery data exceeding the threshold exceeds the threshold time. [Effects of the Invention]

[0020] According to the battery management device and its operating method as disclosed in this document, identification information of battery data that exceeds a threshold can be recorded, and the threshold time can be flexibly changed to improve the efficiency of battery data analysis. [Brief explanation of the drawing]

[0021] [Figure 1] This figure shows a battery pack according to one embodiment disclosed in this document. [Figure 2] This figure is intended to specifically illustrate the configuration of a battery management device according to one embodiment disclosed in this document. [Figure 3] This figure shows the operation method of a controller according to one embodiment disclosed in this document. [Figure 4] This is a flowchart showing the operation method of a battery management device according to one embodiment disclosed in this document. [Figure 5] This is a flowchart showing the operation method of a battery management device according to another embodiment disclosed in this document. [Figure 6] It is a block diagram showing the hardware configuration of a computing system that realizes an operation method of a battery management device according to an embodiment disclosed in this document.

Embodiments for Carrying Out the Invention

[0022] Hereinafter, some embodiments disclosed in this document will be described in detail with reference to exemplary drawings. It should be noted that when assigning reference numerals to the components of each drawing, the same components are assigned the same numerals as much as possible when displayed on other drawings. Also, when explaining the embodiments disclosed in this document, if a specific explanation of a related known configuration or function is determined to impede the understanding of the embodiments disclosed in this document, the detailed explanation thereof will be omitted.

[0023] When explaining the components of the embodiments disclosed in this document, terms such as first, second, A, B, (a), (b), etc. may be used. Such terms are only for distinguishing the components from other components, and the essence, order, or procedure of the components are not limited by such terms. Also, unless otherwise defined, all terms used here, including technical or scientific terms, have the same meaning as generally understood by those with ordinary knowledge in the technical field to which the embodiments disclosed in this document belong. Terms defined in a generally used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and should not be interpreted in an ideal or overly formal meaning unless clearly defined in this document.

[0024] FIG. 1 is a diagram showing a battery pack according to an embodiment disclosed in this document. Referring to FIG. 1, a battery pack 1000 according to an embodiment disclosed in this document can include a battery module 100, a battery management device 200, and a relay 300.

[0025] The battery module 100 can include multiple battery cells 110, 120, 130, and 140. Although Figure 1 shows a configuration with four battery cells, the battery module 100 is not limited to this configuration and can be composed of n (where n is a natural number greater than or equal to 2) battery cells.

[0026] The battery module 100 can supply power to a target device (not shown). For this purpose, the battery module 100 can be electrically connected to the target device. Here, the target device may include an electrical, electronic, or mechanical device that operates on power supplied from a battery pack 1000 including a plurality of battery cells 110, 120, 130, 140, for example, an electric vehicle (EV) or an energy storage system (ESS).

[0027] The multiple battery cells 110, 120, 130, and 140 are the basic units of a battery that can be used by charging and discharging electrical energy, and may be, but are not limited to, lithium-ion (Li-ion) batteries, lithium-ion polymer (Li-ion polymer) batteries, nickel-cadmium (Ni-Cd) batteries, nickel-metal hydride (Ni-MH) batteries, etc. On the other hand, although Figure 1 shows that there is one battery module 100, according to the embodiment, the battery module 100 may be composed of multiple units.

[0028] The Battery Management System (BMS) 200 can predict the State of Health (SOH) of multiple battery cells 110, 120, 130, and 140 based on their temperature and voltage data. The Battery Management System 200 can remove noise from the battery data of the multiple battery cells 110, 120, 130, and 140, and based on the noise-removed data, can predict the State of Health (SOH) of the multiple battery cells 110, 120, 130, and 140 at different battery temperatures and charge / discharge rates.

[0029] The battery management device 200 can manage and / or control the state and / or operation of the battery module 100. For example, the battery management device 200 can manage and / or control the state and / or operation of multiple battery cells 110, 120, 130, and 140 contained in the battery module 100. The battery management device 200 can manage the charging and / or discharging of the battery module 100.

[0030] Furthermore, the battery management device 200 can monitor the voltage, current, temperature, etc., of the battery module 100 and / or the multiple battery cells 110, 120, 130, and 140 contained within the battery module 100. In addition, for monitoring via the battery management device 200, sensors and various measuring modules (not shown) can be further provided at any location on the battery module 100, the charge / discharge path, or the battery module 100. Based on the measured values ​​of voltage, current, temperature, etc., the battery management device 200 can calculate parameters indicating the state of the battery module 100, such as SOC (State of Charge).

[0031] The battery management device 200 can control the operation of the relay 300. For example, the battery management device 200 can short-circuit the relay 300 to supply power to the target device. The battery management device 200 can also short-circuit the relay 300 when a charging device is connected to the battery pack 1000.

[0032] The battery management device 200 can calculate the cell balancing time for each of the multiple battery cells 110, 120, 130, and 140. Here, cell balancing time can be defined as the time required to balance the battery cells. For example, the battery management device 200 can calculate the cell balancing time for each of the multiple battery cells 110, 120, 130, and 140 based on their State of Charge (SOC), battery capacity, and balancing efficiency.

[0033] Multiple battery cells 110, 120, 130, and 140 can experience changes in various battery factors, such as decreased capacity and increased internal resistance, as their usage period or number of uses increases. The battery management device 200 can calculate the battery life based on data of various factors that change as the battery deteriorates. Specifically, the battery management device 200 can calculate the State of Health (SOH) of multiple battery cells 110, 120, 130, and 140 based on data of various factors that change as the multiple battery cells 110, 120, 130, and 140 deteriorate. SOH is an indicator that can show the health or lifespan of a battery in its current state relative to its initial state. The moment when SOH reaches 0% can be defined as the End of Life (EOL). Alternatively, the End of Life may be the point at which the battery capacity falls below the guaranteed capacity. For example, the battery management device 200 can calculate the State of Health (SOH) of multiple battery cells 110, 120, 130, and 140 based on at least one of the following factors: internal resistance, impedance, conductance, capacity, voltage, self-discharge current, charging performance, and charge / discharge cycles of the multiple battery cells 110, 120, 130, and 140, which change as the multiple battery cells 110, 120, 130, and 140 degrade.

[0034] Figure 2 is a diagram for specifically illustrating the configuration of a battery management device according to one embodiment disclosed in the document. The configuration of the battery management device 200 will be described in detail below with reference to Figure 2.

[0035] Referring to Figure 2, the battery management device 200 may include a memory 210 and a controller 220. The memory 210 can store battery data for multiple battery cells 110, 120, 130, and 140. According to the embodiment, the memory 210 can temporarily store data to adjust for time differences or data transmission speed differences that occur when transmitting data from one device to another. The memory 210 can temporarily store battery data for multiple battery cells 110, 120, 130, and 140 at specific time intervals. Here, the battery data may include battery voltage, current, temperature, SOC (State of Charge), SOH (State of Health), Power Limit, or related diagnostic information.

[0036] Memory 210 can record identification information for battery data that exceeds a threshold. Here, the identification information may include log data. Log data can be defined as data that records all event information that occurred during the execution of the operating system or software, chronologically. For example, the values ​​stored in the identification information may include battery communication raw data, the numerical value of the battery data, the measurement time of the battery data, and information about the battery that exceeded the threshold.

[0037] The controller 220 can analyze battery data from multiple battery cells 110, 120, 130, and 140. The controller 220 can determine whether the battery data from multiple battery cells 110, 120, 130, and 140 exceeds a threshold. Here, the threshold can be defined as a criterion that indicates an extreme result and can be judged as "abnormal." In other words, the threshold can be defined as a criterion that shows how much the data deviates from a particular statistical model. Specifically, the controller 220 can determine whether the battery data from multiple battery cells 110, 120, 130, and 140 exceeds a threshold, using a specific time interval as the period. For example, the controller 220 can determine whether the battery data from multiple battery cells 110, 120, 130, and 140 from (tN) time to (t-1) time exceeds a pre-set threshold.

[0038] The controller 220 can determine whether the duration (Mature Time) of battery data exceeding a threshold exceeds the threshold time. Here, the duration can be defined as the minimum battery failure maintenance time required to diagnose the battery based on the battery data. In other words, the controller 220 can determine whether the duration of battery data exceeding the threshold generated during a predetermined period of time exceeds the already set threshold time.

[0039] The controller 220 can diagnose a battery if the duration of battery data exceeding a threshold exceeds the threshold time. For example, the controller 220 can diagnose the first battery cell 110 if the duration of battery data exceeding a threshold is maintained for several seconds to tens of seconds. The controller 220 can also determine whether the duration of battery data exceeding a threshold exceeds the threshold time, using a specific time interval as a period.

[0040] For example, if the duration of battery data exceeding a threshold exceeds a threshold time, the controller 220 can diagnose the State of Charge (SOC), which is the battery capacity for predicting the remaining driving range of the battery pack 1000, and the State of Health (SOH), which is the aging life prediction for battery replacement. Here, the battery capacity for predicting the remaining driving range is the ratio of the remaining charge to the charged amount. The controller 220 senses the current, voltage, temperature, etc., of the battery pack 1000 to determine the current charge remaining in the battery pack 1000 and can predict the remaining driving range of the vehicle.

[0041] The controller 220 can diagnose a battery system failure if the duration of battery data exceeding a threshold exceeds the threshold time. For example, if the duration of battery data exceeding a threshold exceeds the threshold time, the controller 220 can detect various battery system failures such as overvoltage, undervoltage, battery cell failure, current sensor failure, temperature sensor failure, open circuit, short circuit, cooling fan failure, communication abnormality, or relay fusion, and send the failure detection information to other controllers.

[0042] The controller 220 can record battery data identification information in the memory 210 based on the result of its determination. According to the embodiment, if the duration of battery data exceeding a threshold is less than the threshold time, the controller 220 can accumulate and record the identification information of the battery data exceeding the threshold in the memory 210. Specifically, if the duration of battery data exceeding a threshold is less than the threshold time, the controller 220 can accumulate and record the duration of the battery data exceeding the threshold and the number of times the battery data exceeding the threshold occurred in the memory 210.

[0043] Figure 3 is a diagram showing the operation method of a controller according to one embodiment disclosed in this document. First, referring to Figure 3(a), the controller 220 can record identification information for battery data that has exceeded the threshold if the duration of the battery data that has exceeded the threshold is less than the threshold duration. For example, if the duration required for battery data to be diagnosed is 10 seconds, and the measured duration of battery data that has exceeded the threshold is 2 seconds, the controller 220 can record data such as the duration of the battery data that has exceeded the threshold (2 seconds) and the number of occurrences (6).

[0044] Referring to Figure 3(b), the controller 220 can accumulate and record the duration of battery data exceeding the threshold if the duration of the battery data exceeding the threshold is less than the threshold time. The controller 220 can also calculate the cumulative time of battery data exceeding the threshold based on the accumulated and recorded duration of the battery data exceeding the threshold. If the duration of battery data exceeding the threshold is less than the threshold time, the controller 220 can accumulate the duration of the battery data exceeding the threshold and record it in the memory 210 to calculate the cumulative time.

[0045] For example, if the duration required for battery data diagnosis is 10 seconds, and the measured duration of battery data exceeding the threshold is 2 seconds, the controller 220 can accumulate and record the 2 seconds of duration of the battery data exceeding the threshold.

[0046] Referring to Figure 3(c), the controller 220 can accumulate and record the number of times battery data exceeds the threshold if the duration of the battery data exceeding the threshold is less than the threshold time. The controller 220 can also calculate the cumulative number of times battery data exceeds the threshold based on the cumulatively recorded number of occurrences of battery data exceeding the threshold. Here, the number of occurrences can include, for example, the cycle of the battery management device. The cycle of the battery management device can include the operating cycle of the battery management device 200, such as Power ON / OFF and Ignition ON / OFF of the battery management device. The controller 220 can accumulate the number of occurrences of battery data in which battery data exceeding the threshold occurs and increase the occurrence count value.

[0047] For example, if the duration required for battery data diagnosis is 10 seconds, and the duration of measured battery data exceeding the threshold is 2 seconds, the controller 220 can accumulate and record the number of times battery data exceeding the threshold occurs.

[0048] The controller 220 can determine whether the cumulative count is above a certain threshold. If the cumulative count is above a certain threshold, the controller 220 can recalculate the threshold time by dividing the cumulative time by the cumulative count. Specifically, if the cumulative count is above a certain threshold, the controller 220 can change the battery diagnostic conditions by setting the value calculated by dividing the cumulative time by the cumulative count as the threshold time.

[0049] For example, if the cumulative number of cycles is greater than or equal to the baseline value of 5, the controller 220 can recalculate and change the threshold time. If the cumulative time is 10 seconds and the cumulative number of cycles is greater than or equal to the baseline value of 5, the controller 220 can recalculate the threshold time by dividing the cumulative time of 10 seconds by the cumulative number of cycles, which is 2 seconds. The controller 220 can then set the recalculated threshold time of 2 seconds and change the battery diagnostic conditions.

[0050] The controller 220 can determine, based on the recalculated threshold time, whether the duration of battery data exceeding the threshold time exceeds the threshold time. The controller 220 can diagnose battery data whose duration exceeds the threshold time. For example, after changing the battery diagnostic conditions by setting the threshold time to 2S, the controller 220 can diagnose the battery if the duration of battery data exceeding the threshold is 2S.

[0051] One objective of the embodiments disclosed herein is to provide a battery management device and its operating method that can prevent fires by determining whether or not the battery voltage data exceeds a threshold count value, thereby enabling early diagnosis of battery degradation and improving the efficiency and speed of battery diagnosis.

[0052] As described above, according to the battery data management device 200 according to one embodiment disclosed in this document, identification information of battery data that exceeds a threshold can be recorded, and the efficiency of battery data analysis can be improved by flexibly changing the threshold time.

[0053] Furthermore, the battery management device 200 can improve the accuracy of battery diagnosis and predict the occurrence of a diagnosis by analyzing the timing and trends at which the battery data duration exceeds a threshold count value.

[0054] Figure 4 is a flowchart showing the operation method of a battery management device according to one embodiment disclosed in this document. The operation method of the battery management device 200 will be described in detail below with reference to Figures 1 to 3.

[0055] Since the battery management device 200 is substantially the same as the battery management device 200 described with reference to Figures 1 to 3, a brief description will be given below to avoid repetition.

[0056] Referring to Figure 4, the operation method of the battery management device 200 may include the steps of: determining whether the battery data exceeds a threshold (S101); determining whether the duration of the battery data that has exceeded the threshold exceeds a threshold time (S102); diagnosing the battery data based on the determination result (S103); and recording identification information of the battery data based on the determination result (S104).

[0057] The following provides a detailed explanation of steps S101 through S104. In step S101, the controller 220 can analyze battery data from multiple battery cells 110, 120, 130, and 140. In step S101, the controller 220 can determine whether the battery data from multiple battery cells 110, 120, 130, and 140 exceeds a threshold. Here, the threshold can be defined as a criterion that indicates an extreme result and can be judged as "abnormal." In other words, the threshold can be defined as a criterion that shows how much the data contradicts a particular statistical model.

[0058] In step S101, the controller 220 can determine whether the battery data of multiple battery cells 110, 120, 130, and 140 exceeds a threshold, with a specific time interval as the period. In step S101, for example, the controller 220 can determine whether the battery data of multiple battery cells 110, 120, 130, and 140 from (tN) time to (t-1) time exceeds a previously set threshold.

[0059] In step S102, the controller 220 can determine whether the duration (Mature Time) of the battery data that exceeds the threshold exceeds the threshold time. Here, the duration can be defined as the minimum battery failure maintenance time required to diagnose the battery based on the battery data.

[0060] In step S102, the controller 220 can determine whether the duration of battery data exceeding the threshold, generated during a predetermined time period, exceeds the already set threshold time.

[0061] In step S103, the controller 220 can diagnose the battery if the duration of battery data exceeding a threshold exceeds a previously set threshold time. In step S103, for example, the controller 220 can diagnose the first battery cell 110 if the duration of battery data exceeding a threshold for the first battery cell 110, measured over a predetermined period of time, exceeds the threshold time.

[0062] In step S103, for example, the controller 220 can diagnose the first battery cell 110 if the duration of battery data exceeding a threshold is maintained for several seconds to tens of seconds. The controller 220 can also determine whether the duration of battery data exceeding a threshold exceeds a threshold time, using a specific time interval as a period.

[0063] In step S104, the controller 220 can record battery data identification information in the memory 210 based on the result of its determination. In step S104, according to the embodiment, if the duration of battery data exceeding the threshold is less than the threshold time, the controller 220 can accumulate identification information of the battery data exceeding the threshold and record it in the memory 210. Here, the identification information may include log data. Log data can be defined as data that records all event information that occurred during the execution of the operating system or software, on a time-by-time basis. For example, the values ​​stored in the identification information may include battery communication raw data, a numerical value of the battery data, the measurement time of the battery data, and information about the battery in which the threshold was exceeded.

[0064] In step S104, specifically, if the duration of battery data exceeding the threshold is less than the threshold time, the controller 220 can accumulate the duration of the battery data exceeding the threshold and the number of times the battery data exceeding the threshold occurred and record them in the memory 210.

[0065] In step S104, for example, if the duration required for battery data diagnosis is 10 seconds, and the measured duration of battery data exceeding the threshold is 2 seconds, the controller 220 can record data such as the duration of the battery data exceeding the threshold (2 seconds) and the number of occurrences (6).

[0066] In step S104, the controller 220 can accumulate and record the number of times battery data exceeds the threshold if the duration of the battery data exceeding the threshold is less than the threshold time.

[0067] In step S104, the controller 220 can also calculate the cumulative number of battery data occurrences that exceed the threshold based on the cumulatively recorded number of occurrences of battery data exceeding the threshold. In step S104, the controller 220 can increase the occurrence count value by accumulating the number of occurrences of battery data in which battery data exceeding the threshold occurred.

[0068] Figure 5 is a flowchart showing the operation method of a battery management device according to another embodiment disclosed in this document. Referring to Figure 5, the operation method of the battery management device 200 may include the steps of: determining whether the battery data exceeds a threshold (S201); determining whether the duration of the battery data that exceeds the threshold exceeds a threshold time (S202); diagnosing the battery data based on the determination result (S203); recording the cumulative time and cumulative count of the battery data based on the determination result (S204); and determining whether the cumulative count is equal to or greater than a standard value, and changing the threshold time based on whether the cumulative count is equal to or greater than a standard value (S205).

[0069] In step S201, the controller 220 can analyze the battery data of multiple battery cells 110, 120, 130, and 140. In step S201, the controller 220 can determine whether the battery data of multiple battery cells 110, 120, 130, and 140 exceeds a threshold.

[0070] In step S202, the controller 220 can determine whether the duration of battery data exceeding the threshold exceeds the threshold time. Here, the duration can be defined as the minimum battery failure maintenance time required to diagnose the battery based on the battery data.

[0071] In step S203, the controller 220 can diagnose the battery if the duration of battery data exceeding a threshold exceeds a previously set threshold time.

[0072] In step S204, the controller 220 can record battery data identification information in the memory 210 based on the result of its determination. In step S204, according to the embodiment, if the duration of battery data exceeding the threshold is less than the threshold time, the controller 220 can accumulate and record the battery data identification information exceeding the threshold in the memory 210.

[0073] In step S204, specifically, if the duration of battery data exceeding the threshold is less than the threshold time, the controller 220 can accumulate the duration of the battery data exceeding the threshold and the number of times the battery data exceeding the threshold occurred and record them in the memory 210.

[0074] In step S204, the controller 220 can calculate the cumulative time of battery data exceeding the threshold if the duration of battery data exceeding the threshold is less than the threshold time. If the duration of battery data exceeding the threshold is less than the threshold time, the controller 220 can accumulate the duration of battery data exceeding the threshold and record it in the memory 210 to calculate the cumulative time.

[0075] In step S205, the controller 220 can determine whether the cumulative count is above a certain threshold. In step S205, if the cumulative count is above a certain threshold, the controller 220 can recalculate the threshold time by dividing the cumulative time by the cumulative count. Specifically, in step S205, if the cumulative count is above a certain threshold, the controller 220 can change the battery diagnostic conditions by setting the value calculated by dividing the cumulative time by the cumulative count as the threshold time.

[0076] In step S205, for example, if the cumulative count is 5 or more, the controller 220 can recalculate and change the threshold time. In step S205, if the cumulative time is 10S and the cumulative count is 5 or more, the controller 220 can recalculate the threshold time as 2S, which is calculated by dividing the cumulative time of 10S by the cumulative count of 5 (Cycles).

[0077] In step S205, the controller 220 can change the battery diagnostic conditions by setting the recalculated 2S as the threshold time. In step S205, the controller 220 can determine, based on the recalculated threshold time, whether the duration of the battery data that exceeds the threshold time exceeds the threshold time.

[0078] In step S205, the controller 220 can diagnose battery data whose duration exceeds the threshold time. In step S205, for example, the controller 220 can change the battery diagnostic conditions by setting 2S as the threshold time, and then diagnose the battery if the duration of the battery data exceeding the threshold is 2S.

[0079] Figure 6 is a block diagram showing the hardware configuration of a computing system that implements the operation method of a battery management device according to one embodiment disclosed in this document.

[0080] Referring to Figure 6, the computing system 2000 according to one embodiment disclosed in this document may include an MCU 2100, a memory 2200, an input / output I / F 2300, and a communication I / F 2400.

[0081] The MCU2100 may be a processor that executes various programs (for example, a battery data diagnostic program) stored in the memory 2200, processes various data through such programs, and performs the functions of the battery management device 200 shown in Figure 1 above.

[0082] The memory 2200 can store various programs related to the operation of the battery management device 200. The memory 2200 can also store operation data for the equipment control device 200.

[0083] Multiple such memory 2200s may be provided as needed. The memory 2200 may be volatile or non-volatile. As volatile memory, RAM, DRAM, SRAM, etc., can be used. As non-volatile memory, ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc., can be used. The examples of memory 2200 listed above are merely illustrative and the system is not limited to these examples.

[0084] The I / O I / F 2300 can provide an interface that connects input devices (not shown), such as keyboards, mice, and touch panels, with output devices (not shown), such as displays, and the MCU 2100, enabling data transmission and reception.

[0085] The communication interface 2400 is configured to send and receive various data with the server and may be various devices that support wired or wireless communication. For example, programs for resistance measurement and anomaly diagnosis, as well as various data, can be sent and received from a separately provided external server via the communication interface 2400.

[0086] The above description is merely illustrative of the technical concept of this disclosure, and any person with ordinary skill in the art to which this disclosure belongs can make various modifications and variations without departing from the essential characteristics of this disclosure.

[0087] Therefore, the embodiments disclosed herein are for illustrative purposes only, and not to limit the technical concept of the disclosure, and such embodiments do not limit the scope of the technical concept of the disclosure. The scope of protection of this disclosure must be interpreted in accordance with the claims set forth below, and all technical concepts within an equivalent scope should be interpreted as being included in the scope of rights of this disclosure. [Explanation of Symbols]

[0088] 1000: Battery pack 100: Battery Module 110: First battery cell 120: Second battery cell 130: Third battery cell 140: Fourth battery cell 200:Battery management device 210: Memory 220: Controller 300: Relay 2000: Computing Systems 2100:MCU 2200: Memory 2300: Input / Output Interface 2400: Communication I / F

Claims

1. Memory and A controller that determines whether battery data exceeds a threshold and whether the duration of the battery data exceeding the threshold exceeds a threshold time, diagnoses the battery data based on the determination result, and records the identification information of the battery data in the memory based on the determination result, Includes, The controller is configured to record in the memory the duration and number of occurrences of battery data exceeding the threshold as identification information when the duration of battery data exceeding the threshold is less than the threshold time, and to adjust the threshold time based on the accumulated record of the identification information.

2. The battery management device according to Claim 1, wherein the controller changes the threshold time based on the cumulative recorded duration of the battery data exceeding the threshold when the duration of the battery data exceeding the threshold is less than the threshold time, and the cumulative recorded number of occurrences of the battery data exceeding the threshold when the duration of the battery data exceeding the threshold is less than the threshold time.

3. The battery management device according to claim 2, wherein the controller calculates the cumulative time of battery data exceeding the threshold based on the cumulatively recorded duration of battery data exceeding the threshold when the duration of battery data exceeding the threshold is less than the threshold time, and calculates the cumulative number of occurrences of battery data exceeding the threshold based on the cumulatively recorded number of occurrences of battery data exceeding the threshold when the duration of battery data exceeding the threshold is less than the threshold time.

4. The battery management device according to claim 3, wherein the controller determines whether the cumulative count is equal to or greater than a reference value, and changes the threshold time based on whether the cumulative count is equal to or greater than a reference value.

5. The battery management device according to claim 4, wherein the controller recalculates the threshold time by dividing the cumulative time by the cumulative number of times if the cumulative count is equal to or greater than a reference value.

6. The battery management device according to claim 5, wherein the controller determines, based on the recalculated threshold time, whether the duration of battery data exceeding the threshold time exceeds the threshold time.

7. A step to determine whether the battery data exceeds a threshold, The steps include determining whether the duration of battery data exceeding the threshold exceeds the threshold time, A step of diagnosing the battery data based on the result of the determination, A step of recording identification information of the battery data based on the result of the above determination, Includes, The step of recording the identification information of the battery data based on the result of the above determination is: A method for operating a battery management device, wherein if the duration of battery data exceeding the threshold is less than the threshold time, the duration and number of occurrences of the battery data exceeding the threshold are accumulated and recorded as identification information, and the threshold time is adjusted based on the accumulated record of the identification information.

8. The method for operating a battery management device according to claim 7, further comprising the step of changing the threshold time based on the cumulative recorded duration of the battery data exceeding the threshold when the duration of the battery data exceeding the threshold is less than the threshold time, and the cumulative recorded number of occurrences of the battery data exceeding the threshold when the duration of the battery data exceeding the threshold is less than the threshold time.

9. The step of recording the identification information of the battery data based on the result of the above determination is: A method for operating a battery management device according to claim 8, wherein, when the duration of battery data exceeding the threshold is less than the threshold time, the cumulative time of battery data exceeding the threshold is calculated based on the cumulative duration of battery data exceeding the threshold that has been recorded, and when the duration of battery data exceeding the threshold is less than the threshold time, the cumulative number of occurrences of battery data exceeding the threshold is calculated based on the cumulative number of occurrences of battery data exceeding the threshold that has been recorded.

10. The method for operating a battery management device according to claim 9, wherein the step of changing the threshold time includes determining whether the cumulative count is equal to or greater than a reference value, and changing the threshold time based on whether the cumulative count is equal to or greater than a reference value.

11. The step of determining whether the cumulative count is equal to or greater than a standard value, and changing the threshold time based on whether the cumulative count is equal to or greater than a standard value, The method for operating a battery management device according to claim 10, wherein if the cumulative count is equal to or greater than a standard value, the cumulative time is divided by the cumulative count to recalculate the threshold time.

12. The step of determining whether the cumulative count is equal to or greater than a standard value, and changing the threshold time based on whether the cumulative count is equal to or greater than a standard value, A method for operating a battery management device according to claim 11, wherein, based on the recalculated threshold time, it is determined whether the duration of battery data exceeding the threshold time exceeds the threshold time.