Battery management apparatus and battery management method

Abstract

The battery management device disclosed in this document includes a sensor unit for measuring the voltage and current of a plurality of battery cells, and a control unit for generating voltage deviation accumulation data by accumulating voltage deviations between the plurality of battery cells, determining the state of charge (SOC) of the plurality of battery cells based on the current, generating SOC deviation accumulation data by accumulating SOC deviations between the plurality of battery cells, and determining the cause of failure of the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data.

Description

Technology Field

[0001] The embodiments disclosed in this document relate to a battery management device and a battery management method for diagnosing battery status. Background Technology

[0002] 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 manner, making them suitable for use as power sources for mobile devices. Additionally, as their scope of application expands to include power sources for electric vehicles, lithium-ion batteries are garnering attention as a next-generation energy storage medium.

[0003] Since the occurrence of defective battery cells, such as open-circuit tabs or lithium deposition, can lead to safety issues during battery use, research is being conducted on algorithms for detecting defective battery cells. Conventionally, a method was used to diagnose battery abnormalities simply by analyzing deviations in voltage and State of Charge (SOC). However, conventional methods had problems such as delayed diagnosis due to high deviation thresholds to prevent overdiagnosis, and cost losses resulting from the need to replace all related parts because the cause of the battery abnormality could not be determined. The problem to be solved

[0004] According to one embodiment disclosed in this document, a battery management device and a battery management method are provided that facilitate the identification of the causes of deviations in voltage and State of Charge (SOC) by utilizing accumulated deviation data.

[0005] 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. means of solving the problem

[0006] A battery management device according to one embodiment includes a sensor unit for measuring the voltage and current of a plurality of battery cells, and a control unit for generating voltage deviation accumulation data by accumulating voltage deviations between the plurality of battery cells, determining the state of charge (SOC) of the plurality of battery cells based on the current, generating SOC deviation accumulation data by accumulating SOC deviations between the plurality of battery cells, and determining the cause of failure of the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data.

[0007] The control unit above can determine the time required for the increase of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determine the cause of the deviation corresponding to the time required for the increase as the cause of the defect of the plurality of battery cells.

[0008] The control unit can determine the number of occurrences of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determine the cause of the deviation corresponding to the number of occurrences of the deviation as the cause of defects of the plurality of battery cells.

[0009] The control unit can determine the maximum deviation of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determine the cause of the deviation corresponding to the maximum deviation as the cause of defect in the plurality of battery cells.

[0010] The control unit can determine the time required from the point of maximum deviation occurrence to the next point of maximum deviation occurrence based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determine the cause of deviation occurrence corresponding to the time required as the cause of defect in the plurality of battery cells.

[0011] The above control unit can determine the maximum deviation occurrence rate based on the above required time and determine the cause of deviation occurrence corresponding to the maximum deviation occurrence rate as the cause of defect in the plurality of battery cells.

[0012] The control unit above can reset the accumulated data based on the fact that the voltage deviation accumulated data and the SOC deviation accumulated data are included in the normal range.

[0013] The control unit above stores the maximum deviation up to the reset point based on the fact that the accumulated data has been reset, and can store the larger value by comparing the maximum deviation previously stored with the maximum deviation up to the reset point.

[0014] A battery management method according to one embodiment may include measuring the voltage and current of a plurality of battery cells, generating voltage deviation accumulation data by accumulating voltage deviations between the plurality of battery cells, determining the SOC of the plurality of battery cells based on the current, generating SOC deviation accumulation data by accumulating SOC deviations between the plurality of battery cells, and determining the cause of failure of the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data.

[0015] Determining the cause of failure of the plurality of battery cells above involves determining the time required for the increase of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determining the cause of the deviation corresponding to the time required for the increase as the cause of failure of the plurality of battery cells.

[0016] Determining the cause of defects in the plurality of battery cells above involves determining the number of occurrences of deviations in the voltage deviation and SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determining the cause of deviation occurrence corresponding to the number of occurrences of deviations as the cause of defects in the plurality of battery cells.

[0017] Determining the cause of defects in the plurality of battery cells above involves determining the maximum deviation of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determining the cause of deviation occurrence corresponding to the maximum deviation as the cause of defects in the plurality of battery cells.

[0018] Determining the cause of failure of the plurality of battery cells above involves determining the time required from the point of maximum deviation occurrence to the point of next maximum deviation occurrence based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determining the cause of deviation occurrence corresponding to the time required as the cause of failure of the plurality of battery cells.

[0019] Determining the cause of failure of the plurality of battery cells above involves determining the maximum deviation occurrence rate based on the time required above, and determining the cause of deviation occurrence corresponding to the maximum deviation occurrence rate as the cause of failure of the plurality of battery cells.

[0020] A battery management method according to one embodiment may further include resetting the accumulated data based on the fact that the voltage deviation accumulated data and the SOC deviation accumulated data are included in a normal range.

[0021] A battery management method according to one embodiment may further include storing the maximum deviation up to the reset point based on the fact that the accumulated data has been reset, and storing the larger value by comparing the maximum deviation previously stored with the maximum deviation up to the reset point. Effects of the invention

[0022] According to a battery management device of one embodiment, the cause of voltage or SOC (State Of Charge) deviation can be classified based on accumulated deviation data, so cost loss can be reduced by replacing only the causative part without replacing all parts related to the battery abnormality.

[0023] According to a battery management device of one embodiment, by analyzing the cause of voltage or SOC (State Of Charge) deviation and performing balancing without replacing parts, the deviation can be reduced, thereby reducing the time and cost required for cause analysis. Brief explanation of the drawing

[0024] FIG. 1 illustrates a block diagram showing a general battery system including a battery management device according to one embodiment. FIG. 2 illustrates a block diagram showing the configuration of a battery management device according to one embodiment. FIG. 3 schematically illustrates the types of data stored in memory in a battery management device according to one embodiment. FIG. 4 schematically illustrates the flow of a battery management device according to one embodiment determining the cause of a battery failure. FIG. 5 illustrates a change in the state of a battery management device according to one embodiment. FIG. 6 illustrates a value stored based on a state change in a battery management device according to one embodiment. FIGS. 7 to 10 illustrate a graph of deviation accumulation data obtained from a battery management device according to one embodiment. FIG. 11 illustrates a flowchart of a battery management method according to one embodiment. FIG. 12 continues to illustrate a flowchart of a battery management method according to one embodiment, following FIG. 11. Specific details for implementing the invention

[0025] Hereinafter, various embodiments disclosed in this document will be described in detail with reference to the attached drawings. In this document, the same reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted.

[0026] With respect to the various embodiments disclosed in this document, specific structural or functional descriptions are provided merely for the purpose of explaining the embodiments, and the various embodiments disclosed in this document may be implemented in various forms and should not be interpreted as being limited to the embodiments described in this document.

[0027] Expressions such as "first," "second," "first," or "second" used in various embodiments may modify various components regardless of order and / or importance and do not limit said components. For example, without departing from the scope of the embodiments disclosed herein, the first component may be named the second component, and similarly, the second component may be renamed the first component.

[0028] The terms used in this document are used merely to describe specific embodiments and are not intended to limit the scope of other embodiments. Singular expressions may include plural expressions unless the context clearly indicates otherwise.

[0029] All terms used herein, including technical or scientific terms, may have the same meaning as generally understood by those skilled in the art of the embodiments disclosed herein. Terms defined in commonly used dictionaries may be interpreted as having the same or similar meaning as they have in the context of the relevant technology, and are not to be interpreted in an ideal or overly formal sense unless explicitly defined in this document. In some cases, even terms defined in this document shall not be interpreted to exclude the embodiments disclosed herein.

[0030] FIG. 1 illustrates a block diagram showing the configuration of a general battery system including a battery management device according to various embodiments.

[0031] Specifically, FIG. 1 schematically illustrates a battery system (10) and a higher controller (20) included in a higher system according to an embodiment disclosed in this document.

[0032] As illustrated in FIG. 1, the battery system (10) may include a plurality of battery modules (12), a sensor unit (14), a switching unit (16), and a battery management device (1). At this time, the battery system (10) may be equipped with a plurality of battery modules (12), a sensor unit (14), a switching unit (16), and a battery management device (1).

[0033] A plurality of battery modules (12) may include at least one battery cell (13) capable of charging and discharging. The battery cell (13) may include a positive electrode, a positive electrode material, a negative electrode material, a separator, an electrolyte, a polymer, and a case. At this time, the plurality of battery modules (12) may be connected in series or in parallel.

[0034] The sensor unit (14) may include a current sensor (2), a voltage sensor (3), and a temperature sensor (not shown).

[0035] The current sensor (2) can detect the current used in the process of determining the SOC of the battery cell (13).

[0036] The current sensor (2) may include all configurations that generate a signal corresponding to the magnitude of the charging current, and the current sensor (2) may be installed on a charging / discharging path, which is a path through which the charging / discharging current flows from the battery.

[0037] The current sensor (2) can measure the battery current flowing through the battery, i.e., the charging current and the discharging current, and transmit the measurement results to the battery management device (1). According to one embodiment, the current sensor (2) can measure the battery current at a predetermined interval during a charging cycle in which the battery is charged with power from an external device or during a discharging cycle in which the battery is discharged, and transmit the measurement results to the battery management device (1).

[0038] A voltage sensor (3) can be configured to be connected in parallel to the battery to detect the battery voltage, which is the voltage across both ends of the battery, and to generate a voltage signal indicating the detected battery voltage.

[0039] A temperature sensor may be configured to measure the battery temperature and generate a temperature signal indicating the measured battery temperature. The temperature sensor may be placed within a case so as to measure a temperature close to the actual temperature of the battery. For example, the temperature sensor may be attached to the surface of at least one battery cell included in a cell group and may detect the surface temperature of the battery cell as the battery temperature.

[0040] The temperature sensor may be configured to measure an external temperature, which is the temperature at a predetermined location spaced apart from the battery, and to generate a temperature signal indicating the measured external temperature. The temperature sensor may be placed at a predetermined location outside the case where heat exchange between the battery and the atmosphere takes place. According to an embodiment, the temperature sensor may be implemented as one or more combinations of known temperature detection elements, such as a thermocouple, a thermistor, or a bimetal. It may detect the current flowing through the battery system (10). At this time, the detection signal may be transmitted to the battery management device (1).

[0041] In FIG. 1, the sensor unit (14) is connected between the positive electrode of the battery cell (13) and the switching unit (16), but the configurations and the connection relationships between the configurations shown in FIG. 1 are examples and are not limited thereto.

[0042] The switching unit (16) can be connected in series to the (+) terminal side or the (-) terminal side of the battery module (12) to control the charging and discharging current flow of the battery module (12). For example, depending on the specifications of the battery system (10), at least one relay, magnetic contactor, etc. may be used as the switching unit (16).

[0043] The battery management device (1) can monitor the voltage, current, and temperature of the battery system (10) to control and manage it to prevent overcharging and over-discharging, and may include, for example, a Battery Management System (BMS).

[0044] The battery management device (1) is an interface that receives values ​​of various measured parameters and may include a plurality of terminals and a circuit connected to these terminals to perform processing of the received values. Additionally, the battery management device (1) may control the ON / OFF of a switching unit (16), such as a relay or contactor, and may be connected to a battery module (12) to monitor the status of each battery module (12).

[0045] In addition, the battery management device (1) can receive temperature data, voltage data, and current data from the sensor unit (14) to obtain battery status information and diagnose the state of the battery.

[0046] The upper controller (20) can transmit a control signal to the battery management device (1) to control the battery module (12). Accordingly, the operation of the battery management device (1) can be controlled based on the control signal applied from the upper controller (20). Additionally, the battery module (12) may be a component included in an Energy Storage System (ESS). In this case, the upper controller (20) may be a controller (BBMS) of a battery bank including a plurality of battery systems (10) or an ESS controller that controls the entire ESS including a plurality of banks. However, the battery system (10) is not limited to such uses.

[0047] FIG. 2 illustrates a block diagram showing the configuration of a battery management device according to one embodiment.

[0048] Referring to FIG. 2, a battery management device (1) according to one embodiment includes a control unit (100) comprising at least one processor (110) and a memory (120) and a communication unit (200), and can diagnose the battery by communicating with an external device (4) through the communication unit (200).

[0049] According to an embodiment, an external device (4) communicating with a battery management device (1) may include a user terminal and a server device that transmits results diagnosed by the battery management device (1).

[0050] Specifically, when the external device (4) is a user terminal, the control unit (100) of the battery management device (1) can transmit the battery diagnosis result to the user terminal so that the user can check it. At this time, the user terminal may include a personal computer, terminal, portable telephone, smartphone, handheld device, wearable device, etc., but is not limited thereto.

[0051] Additionally, if the external device (4) is a server device, the server device can be implemented as various computing devices such as a workstation, cloud, data drive, or data station. The server device can be implemented as one or more server devices that are physically or logically separated based on functions, detailed configurations of functions, or data, and can transmit and receive data and process the transmitted and received data through communication between each server device.

[0052] A battery management device (1) according to one embodiment may refer to any electronic device including a processor (110) and a memory (120), and may be mounted on a vehicle and operated. Each component of the battery management device (1) will be described in detail below.

[0053] The communication unit (200) may include a wireless communication unit (210) and a wired communication unit (220) to communicate with an external device (4). The communication unit (200) may transmit and receive programs or various data for calculating characteristic values ​​of battery cells, class classification, and lifespan estimation from a separately provided external server.

[0054] The wireless communication unit (210) may include at least one of a short-range communication module and a long-range communication module.

[0055] A short-range communication module can communicate with an external device (4) adjacent to a battery management device (1) using a short-range communication method. Here, the short-range communication module can utilize one of the following communication methods: Bluetooth, Bluetooth Low Energy, infrared data association (IrDA), Zigbee, Wi-Fi, Wi-Fi Direct, Ultra Wideband (UWB), or near field communication (NFC).

[0056] The remote communication module may include a communication module that performs various types of remote communication and may include a mobile communication unit. The mobile communication unit can transmit and receive wireless signals with at least one of a base station, an external terminal, and an external device (4) on a mobile communication network. Additionally, the remote communication module can communicate with an external device (4) or other electronic devices, such as an external device (4), through a nearby access point (AP). The access point (AP) can connect a local network (LAN) to which the battery management device (1) is connected to a wide area network (WAN) to which a communication server is connected. Accordingly, the battery management device (1) can communicate with the external device (4) and the communication server through the wide area network (WAN).

[0057] The wired communication unit (220) can connect to a wired communication network and communicate with an external device (4) through the wired communication network. For example, the wired communication unit (220) can connect to a wired communication network via Ethernet (Ethernet, IEEE 802.3 technical standard) or connect to a wired communication network via CAN communication and transmit and receive data with external devices (4) through the wired communication network.

[0058] A battery management device (1) according to one embodiment may include an input / output interface (not shown). An interface may be provided to enable data transmission and reception between an input device (not shown), such as a keyboard, mouse, or touch panel, an output device (not shown), such as a display (not shown), and a processor (110).

[0059] The memory (120) can store various information required for the operation of the battery management device (1). Specifically, the memory (120) can store an operating system and programs required for the operation of the battery management device (1), or store data required for the operation of the battery management device (1).

[0060] Specifically, the memory (120) can store various programs regarding the calculation of characteristic values ​​of battery cells, class classification, and lifespan estimation. In addition, the memory (120) can store various data such as voltage, current, and characteristic value data of each battery cell.

[0061] Additionally, the memory (120) can store the SOC and SOH of the battery cell (13) estimated by the processor (110).

[0062] The memory (120) may include volatile memory (120), such as S-RAM (Static Random Access Memory, S-RAM) and D-RAM (Dynamic Random Access Memory), for temporarily storing data. Additionally, the memory (120) may include non-volatile memory (120), such as ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory).

[0063] The processor (110) outputs a control signal to control the battery management device (1) overall. The processor (110) may include one or more CPUs (central processing units) and GPUs (Graphics Processing Units). In this case, the processor (110) may be implemented as an array of multiple logic gates, or as a combination of a general-purpose microprocessor (110) and a memory (120) storing a program that can be executed on the microprocessor (110).

[0064] The aforementioned memory (120) and processor (110) may be included in the control unit (100), and the control unit (100) may control the aforementioned components to determine whether a defect has occurred in the battery cell.

[0065] Specifically, the control unit (100) can generate voltage deviation accumulation data by accumulating voltage deviations between voltages measured in a plurality of battery cells, and the control unit (100) can generate SOC deviation accumulation data by accumulating SOC (State Of Charge) deviations between a plurality of battery cells.

[0066] To this end, the control unit (100) can determine the SOC of a plurality of battery cells based on the current measured in a plurality of battery cells.

[0067] Additionally, the control unit (100) can determine the time required for the increase of voltage deviation and SOC deviation based on the voltage deviation accumulation data and SOC deviation accumulation data, and determine the cause of the deviation corresponding to the time required for the increase as the cause of defects in a plurality of battery cells.

[0068] The control unit (100) can determine the number of occurrences of voltage deviation and SOC deviation based on voltage deviation accumulation data and SOC deviation accumulation data, and determine the cause of deviation occurrence corresponding to the number of occurrences of deviation as the cause of defects in a plurality of battery cells.

[0069] The control unit (100) can determine the maximum deviation of the voltage deviation and SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determine the cause of the deviation corresponding to the maximum deviation as the cause of defects in a plurality of battery cells.

[0070] The control unit (100) determines the time required from the point of maximum deviation to the next point of maximum deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and can determine the cause of deviation corresponding to the time required as the cause of defects in a plurality of battery cells.

[0071] The control unit (100) determines the maximum deviation occurrence rate based on the time required, and can determine the cause of the deviation corresponding to the maximum deviation occurrence rate as the cause of defects in a plurality of battery cells. In this way, the control unit (100) can determine the cause of defects in battery cells by matching various factors with the cause of deviation occurrence.

[0072] Additionally, the control unit (100) can reset the accumulated data based on the fact that the voltage deviation accumulated data and the SOC deviation accumulated data are included in the normal range, and based on the fact that the accumulated data has been reset, the control unit (100) can store the maximum deviation up to the reset point, and can store the larger value by comparing the maximum deviation stored in advance with the maximum deviation up to the reset point. In this way, the control unit (100) can determine the cause of the deviation by continuously updating the maximum deviation.

[0073] As such, the battery management device according to one embodiment can diagnose whether a defect has occurred in a battery cell by utilizing accumulated voltage deviation data and accumulated SOC deviation data of the battery cell, thereby providing a significant effect of improving the reliability of the diagnosis.

[0074] FIG. 3 schematically illustrates the types of data stored in memory (120) in a battery management device according to one embodiment.

[0075] Referring to FIG. 3, the control unit (100) can receive current and voltage of a plurality of battery cells from the sensor unit (14). Subsequently, the processor (110) of the control unit (100) can calculate the SOC of the battery cells based on the received current, and the SOC calculation can utilize a current integration method or an OCV (Open Circuit Voltage) measurement method.

[0076] The processor (110) can generate deviation data (a) including voltage deviation data and SOC deviation data based on the received voltage and the calculated SOC. Additionally, the processor (110) can generate deviation accumulation data (b) including voltage deviation accumulation data and SOC deviation accumulation data, which is distinguished according to the battery usage mode.

[0077] Thus, a battery management device according to one embodiment can store both deviation data (a) and deviation accumulation data (b) in memory (120). That is, unlike conventional technology that stores only deviation data (a) in memory (120), deviation data (a) and deviation accumulation data (b) regarding deviation increase / decrease can be stored in a storage unit.

[0078] Accordingly, the processor (110) of the control unit (100) can derive the cause of the battery defect by utilizing the deviation accumulation data (b) according to the battery usage mode and matching the battery usage mode with the deviation accumulation trend. Subsequently, the control unit (100) can transmit the cause of the battery defect to an external device (4) including a user terminal and a server device.

[0079] FIG. 4 schematically illustrates the flow of a battery management device according to one embodiment determining the cause of a battery failure.

[0080] Referring to FIG. 4, a control unit (100) of a battery management device according to one embodiment can receive a battery voltage value and a current value at a specific point in time from a voltage sensor (3) and a current sensor (2), and can determine the SOC of a battery cell based on the current value.

[0081] Subsequently, the voltage deviation accumulation data generation unit (101) of the control unit (100) can generate voltage deviation accumulation data by accumulating the difference between the voltages of the battery cells. In addition, the SOC deviation accumulation data generation unit (102) of the control unit (100) can generate SOC deviation accumulation data by accumulating the difference between a preset reference SOC and the calculated SOC of the battery cells.

[0082] At this time, the voltage deviation (Vdev) can be determined by subtracting the minimum voltage (Vmin) from the maximum voltage (Vmax) among the battery cells, or by subtracting the minimum voltage (Vmin) from the median voltage (Vmedian) among the battery cells, as shown in the mathematical formula below.

[0083] In Figure 4, it is shown that the voltage deviation cumulative data is generated first and the SOC deviation cumulative data is generated later, but there are no restrictions on the order, and the SOC deviation cumulative data can be generated first and the voltage deviation cumulative data can be generated, or they can be generated simultaneously in parallel.

[0084] Subsequently, the deviation cause analysis unit (103) of the control unit (100) can determine the cause of the deviation based on the accumulated SOC deviation data and the accumulated voltage deviation data. Specifically, the control unit (100) can generate and visualize accumulated data according to the battery usage mode, and determine the cause of the deviation by interpreting the visualized graph. This is explained in detail below in FIG. 5.

[0085] The defect cause determination unit (104) of the control unit (100) can determine a defect cause corresponding to the determined defect cause. That is, when the defect cause is determined, the control unit (100) can match the defect cause with a pre-typed defect cause and transmit the defect cause to an external device (4).

[0086] For example, the control unit (100) can determine that the deviation is reduced through cell balancing when the deviation is reduced during battery charging in the accumulated SOC deviation data, and the control unit (100) can determine that there is no problem with the cell balancing function.

[0087] As another example, the control unit (100) may determine that the deviation is not reduced through cell balancing when the deviation is maintained constant during battery charging in the accumulated SOC deviation data, and the control unit (100) may determine that there is a problem with the cell balancing function.

[0088] Accordingly, the control unit (100) can determine the cause of the deviation as the failure to perform cell balancing operations, and can determine the cause of the type of defect as a failure of the cell balancing function.

[0089] Afterwards, the control unit (100) can transmit a signal or message regarding a cell balancing function failure to an external device (4), and the user can diagnose the battery based on the cell balancing function failure signal or message transmitted to the external device (4).

[0090] FIG. 5 illustrates a state change of a battery management device according to one embodiment, and FIG. 6 illustrates a value stored based on a state change of a battery management device according to one embodiment.

[0091] First, referring to FIG. 5, the state of the battery management device may change according to the battery usage mode, and the state of the battery management device may be divided into an initial state (a), a charging state (b), an operating state (c), and a stopped state (d). That is, the initial state (a) may mean a standby state as the state before the battery is used, the charging state (b) may mean a state where the battery is connected to a power source and is charging, the operating state (c) may mean a discharge state where the battery is being used, and the stopped state (d) may mean a state where the charging state (b) or the operating state (d) has ended.

[0092] For example, in the solid line portion of FIG. 5, the state of the battery management device according to the battery usage mode can change from an initial state (a) to an operating state (c), from the operating state (c) to a charging state (b), from the charging state (b) back to an operating state (c), from the operating state (c) to a stopped state (d), and from the stopped state (d) to an initial state (a) to form a cycle.

[0093] Next, referring to FIG. 6, the value stored in memory (120) can be determined according to the change in the state of the battery management device in FIG. 5.

[0094] First, in step (a) where the state of the battery management device changes from an initial state to an operating state, the control unit (100) can store the voltage deviation accumulation data (acc_Vdev_r), SOC deviation accumulation data (acc_SOCdev_r), and accumulation time data (Tr) as storage values ​​(e) in the memory (120).

[0095] At this time, if we examine the details of the stored value (f), the accumulated voltage deviation data (acc_Vdev_r) can be determined by adding the voltage deviation change amount (△Vdev_r) to the previous accumulated voltage deviation data (acc_Vdev_r) (acc_Vdev_r = acc_Vdev_r + △Vdev_r). Also, the accumulated SOC deviation data (acc_SOCdev_r) can be determined by adding the SOC deviation change amount (△SOCdev_r) to the previous accumulated SOC deviation data (acc_SOCdev_r) (acc_SOCdev_r = acc_SOCdev_r + △SOCdev_r). Additionally, the accumulated time data (Tr) can be determined by adding the accumulated time change amount (△Tr) to the previous accumulated time data (Tr) (Tr = Tr + △Tr).

[0096] Additionally, looking at the details of the delta (△) value (g), the change in voltage deviation (△Vdev_r) may represent the value obtained by subtracting the voltage deviation of the previous step, the termination state (Vdev_end), from the voltage deviation of the initial state (Vdev_init) (△Vdev_r = Vdev_init - Vdev_end). Also, the change in SOC deviation (△SOCdev_r) may represent the value obtained by subtracting the SOC deviation of the previous step, the termination state (SOCdev_end), from the SOC deviation of the initial state (SOCdev_init) (△SOCdev_r = SOCdev_init - SOCdev_end). Furthermore, the change in cumulative time (△Tr) may represent the value obtained by subtracting the cumulative time of the previous step, the termination state (Tend), from the cumulative time of the initial state (T_init) (△Tr = Tinit - Tend).

[0097] Next, in step (b) where the state of the battery management device changes from an operating state to a charging state, the control unit (100) can store the voltage deviation accumulation data (acc_Vdev_d), SOC deviation accumulation data (acc_SOCdev_d), and accumulation time data (Td) as storage values ​​(e) in the memory (120).

[0098] At this time, if we examine the details of the stored value (f), the accumulated voltage deviation data (acc_Vdev_d) can be determined by adding the change in voltage deviation (△Vdev_d) to the previous accumulated voltage deviation data (acc_Vdev_d) (acc_Vdev_d = acc_Vdev_d + △Vdev_d). Also, the accumulated SOC deviation data (acc_SOCdev_d) can be determined by adding the change in SOC deviation (△SOCdev_d) to the previous accumulated SOC deviation data (acc_SOCdev_d) (acc_SOCdev_d = acc_SOCdev_d + △SOCdev_d). Additionally, the accumulated time data (Td) can be determined by adding the change in accumulated time (△Td) to the previous accumulated time data (Td) (Td = Td + △Td).

[0099] Additionally, looking at the details of the delta (△) value (g), the change in voltage deviation (△Vdev_d) may refer to the value obtained by subtracting the voltage deviation of the previous stage, the initial state (Vdev_init), from the voltage deviation of the operating state (Vdev_d) (△Vdev_d = Vdev_d - Vdev_init). Also, the change in SOC deviation (△SOCdev_d) may refer to the value obtained by subtracting the SOC deviation of the previous stage, the initial state (SOCdev_init), from the SOC deviation of the operating state (SOCdev_d) (△SOCdev_d = SOCdev_d - SOCdev_init). Furthermore, the change in cumulative time (△Td) may refer to the value obtained by subtracting the cumulative time of the previous stage, the initial state (Tinit), from the cumulative time of the operating state (T_d) (△Td = Td - Tinit).

[0100] Next, in step (c) where the state of the battery management device changes from a charging state to an operating state, the control unit (100) can store the voltage deviation accumulation data (acc_Vdev_c), SOC deviation accumulation data (acc_SOCdev_c), and accumulation time data (Tc) as storage values ​​(e) in the memory (120).

[0101] At this time, if we examine the details of the stored value (f), the accumulated voltage deviation data (acc_Vdev_c) can be determined by adding the voltage deviation change amount (△Vdev_c) to the previous accumulated voltage deviation data (acc_Vdev_c) (acc_Vdev_c = acc_Vdev_c + △Vdev_c). Also, the accumulated SOC deviation data (acc_SOCdev_c) can be determined by adding the SOC deviation change amount (△SOCdev_c) to the previous accumulated SOC deviation data (acc_SOCdev_c) (acc_SOCdev_c = acc_SOCdev_c + △SOCdev_c). Additionally, the accumulated time data (Tc) can be determined by adding the accumulated time change amount (△Tc) to the previous accumulated time data (Tc) (Tc = Tc + △Tc).

[0102] Additionally, looking at the details of the delta (△) value (g), the change in voltage deviation (△Vdev_c) may refer to the value obtained by subtracting the voltage deviation of the previous operating state (Vdev_d) from the voltage deviation of the charging state (Vdev_c) (△Vdev_c = Vdev_c - Vdev_d). Also, the change in SOC deviation (△SOCdev_c) may refer to the value obtained by subtracting the SOC deviation of the previous operating state (SOCdev_d) from the SOC deviation of the charging state (SOCdev_c) (△SOCdev_c = SOCdev_c - SOCdev_d). Additionally, the change in cumulative time (△Tc) may refer to the value obtained by subtracting the cumulative time of the previous operating state (Td) from the cumulative time of the charging state (Tc) (△Tc = Tc - Td).

[0103] Next, in step (d), where the state of the battery management device changes from an operating state to a stopped state, the control unit (100) can store the voltage deviation accumulated data (acc_Vdev_d), SOC deviation accumulated data (acc_SOCdev_d), and accumulated time data (Td) as stored values ​​(e) in the memory (120). Additionally, in the stopped state, the voltage deviation (Vdev_end), SOC deviation (SOCdev_end), measurement time (Tend), voltage maximum deviation (Vdev_max), and SOC maximum deviation (SOCdev_max) can be stored along with the accumulated data. Accordingly, as described above, the control unit (100) can utilize not only the accumulated deviation data but also the unaccumulated deviation data to determine whether there is an abnormality in the battery cell.

[0104] At this time, if we examine the details of the stored value (f), the accumulated voltage deviation data (acc_Vdev_d) can be determined by adding the change in voltage deviation (△Vdev_d) to the previous accumulated voltage deviation data (acc_Vdev_d) (acc_Vdev_d = acc_Vdev_d + △Vdev_d). Also, the accumulated SOC deviation data (acc_SOCdev_d) can be determined by adding the change in SOC deviation (△SOCdev_d) to the previous accumulated SOC deviation data (acc_SOCdev_d) (acc_SOCdev_d = acc_SOCdev_d + △SOCdev_d). Additionally, the accumulated time data (Td) can be determined by adding the change in accumulated time (△Td) to the previous accumulated time data (Td) (Td = Td + △Td).

[0105] Additionally, looking at the details of the delta (△) value (g), the change in voltage deviation (△Vdev_d) may refer to the value obtained by subtracting the voltage deviation of the previous stage, the charging state (Vdev_c), from the voltage deviation of the stationary state (Vdev_end) (△Vdev_d = Vdev_end - Vdev_c). Also, the change in SOC deviation (△SOCdev_d) may refer to the value obtained by subtracting the SOC deviation of the previous stage, the charging state (SOCdev_c), from the SOC deviation of the stationary state (SOCdev_end) (△SOCdev_d = SOCdev_end - SOCdev_c). Additionally, the change in cumulative time (△Td) may refer to the value obtained by subtracting the cumulative time of the previous stage, the initial state (Tc), from the cumulative time of the operating state (Tend) (△Td = Tend - Tc).

[0106] The storage values ​​described above are exemplary and may vary depending on the charge / discharge cycle. Below, a process in which a battery management device according to one embodiment determines the cause of a defect based on the storage values ​​is described.

[0107] FIGS. 7 to 10 illustrate a graph of deviation accumulation data obtained from a battery management device according to one embodiment.

[0108] Referring to FIG. 7, the control unit (100) can generate and visualize accumulated data according to the battery usage mode and determine the cause of the deviation by interpreting the visualized graph. FIG. 7 (a) represents the total voltage deviation (V_dev), (b) represents the accumulated voltage deviation data in the charging mode (acc_Vdev_c), (c) represents the accumulated voltage deviation data in the operating mode (acc_Vdev_d), and (d) represents the accumulated voltage deviation data in the stop or idle mode (acc_Vdev_end).

[0109] In FIG. 7, it can be seen that the voltage deviation of the battery cell increases overall based on the increase in the total voltage deviation (a). In addition, since the battery management device according to one embodiment can acquire deviation accumulation data according to the battery usage mode, the cause of the deviation can be determined and the corresponding cause of the defect can be determined.

[0110] Additionally, the control unit (100) can determine the cause of the deviation corresponding to the voltage deviation accumulation data (b) in the charging mode, which accumulates with a positive deviation, and the voltage deviation accumulation data (c) in the operating mode, which accumulates with a negative deviation. Furthermore, the voltage deviation accumulation data (d) in the stop or idle mode accumulates with a positive deviation, which determines the cause of the deviation corresponding to the deviation.

[0111] Referring to FIG. 8, (a) of FIG. 8 represents the total voltage deviation (V_dev), (b) represents the accumulated voltage deviation data in charge / discharge mode (acc_Vdev_on), and (c) represents the accumulated voltage deviation data in idle mode (acc_Vdev_end).

[0112] In FIG. 7, the voltage deviation cumulative data of the charging mode and the operating mode had positive deviation and negative deviation, respectively, and in FIG. 8, the voltage deviation cumulative data (b) in the charging / discharging mode including the charging mode and the operating mode can be shown as having a positive deviation with a small slope, where the positive deviation and the negative deviation cancel each other out.

[0113] Accordingly, the control unit (100) can determine that the ratio affecting the increase in the total voltage deviation (a) is higher in the voltage deviation accumulation data (c) in the idle mode than in the voltage deviation accumulation data (b) in the charge / discharge mode. Subsequently, the control unit (100) can determine the cause of the deviation by determining the ratio affecting the increase in the total voltage deviation (a) and can determine the corresponding cause of the defect.

[0114] For example, assuming that the voltage deviation increase rate is 32 mV / day, the control unit (100) can determine that the deviation increase rate is similar to that of a low voltage state, determine the cause of the deviation to be low voltage, and select the corresponding cause of defect and transmit it to an external device (4).

[0115] Likewise, referring to FIGS. 9 and FIGS. 10, the control unit (100) can generate and visualize accumulated data according to the battery usage mode and determine the cause of deviation by interpreting the visualized graph. FIG. 9 (a) represents the total SOC deviation (SOC_dev), (b) represents the accumulated SOC deviation data in charging mode (acc_SOCdev_c), (c) represents the accumulated SOC deviation data in operating mode (acc_SOCdev_d), and (d) represents the accumulated SOC deviation data in stop or idle mode (acc_SOCdev_end).

[0116] In FIG. 9, it can be seen that the SOC deviation of the battery cell increases overall based on the increase in the total SOC deviation (a). In addition, since the battery management device according to one embodiment can acquire deviation accumulation data according to the battery usage mode, the cause of the deviation can be determined and the corresponding cause of the defect can be determined.

[0117] Additionally, the control unit (100) can determine the cause of the deviation corresponding to the accumulated SOC deviation data (b) in the charging mode, which has a negative deviation, and the accumulated SOC deviation data (c) in the operating mode, which has a positive deviation. Furthermore, the accumulated SOC deviation data (d) in the stop or idle mode has a positive deviation, which has been accumulated, which can determine the cause of the deviation corresponding to the deviation.

[0118] Referring to FIG. 10, (a) of FIG. 10 represents the total SOC deviation (SOC_dev), (b) represents the accumulated SOC deviation data in charge / discharge mode (acc_SOCdev_on), and (c) represents the accumulated SOC deviation data in idle mode (acc_SOCdev_end).

[0119] In FIG. 9, the accumulated SOC deviation data for the charging mode and the operating mode had negative deviation and positive deviation, respectively, and in FIG. 10, the accumulated SOC deviation data (b) in the charging / discharging mode including the charging mode and the operating mode can be displayed as a graph close to horizontal as the positive deviation and the negative deviation cancel each other out.

[0120] Accordingly, the control unit (100) can determine that the cause affecting the increase in the total SOC deviation (a) occurred in the idle mode. Additionally, for example, if the rate of increase in the SOC deviation is assumed to be 4.3% / day, the control unit (100) can determine that the rate of increase in the deviation is similar to the rate of increase in the deviation in the low voltage state, and can determine the cause of the deviation to be low voltage, and can select the corresponding cause of failure and transmit it to an external device (4).

[0121] As such, the battery management device according to one embodiment can utilize cumulative deviation data in addition to voltage and SOC deviations, thereby enabling a more detailed analysis of the cause of battery failure.

[0122] FIG. 11 illustrates a flowchart of a battery management method according to one embodiment, and FIG. 12 continues to illustrate a flowchart of a battery management method according to one embodiment following FIG. 11.

[0123] Referring to FIG. 11, the control unit (100) can receive the voltage and current of a plurality of battery cells from the sensor unit (14) (1100). Subsequently, the control unit (100) can generate voltage deviation accumulation data by accumulating the voltage deviations between the plurality of battery cells (1110).

[0124] Additionally, the control unit (100) can determine the SOC of a plurality of battery cells based on the current of the plurality of battery cells (1120). Subsequently, the control unit (100) can generate SOC deviation accumulation data by accumulating the deviation between the SOCs of the plurality of battery cells (1130).

[0125] At this time, the control unit (100) can determine the cause of defects in a plurality of battery cells based on voltage deviation accumulation data and SOC deviation accumulation data (1140). Specifically, the control unit (100) can determine the cause of defects in the battery cells using information obtained through each of the voltage deviation accumulation data and SOC deviation accumulation data, or can determine the cause of defects in the battery cells using information obtained by analyzing the voltage deviation accumulation data and SOC deviation accumulation data together.

[0126] Referring further to FIG. 12, the control unit (100) can determine whether the voltage deviation accumulation data and the SOC deviation accumulation data have entered a normal range (1200). That is, the control unit (100) can determine that the deviation has entered a normal range if the deviation displayed in the voltage deviation accumulation data and the SOC deviation accumulation data is reduced to within a reference range. The control unit (100) can determine whether the deviation accumulation data has entered a normal range and use this to identify the cause of the deviation.

[0127] For example, if the control unit (100) shows a deviation in the range where the voltage deviation data and the SOC deviation data are judged to be defective for an arbitrary first time period, and then enter the normal range after the first time period, the first time period can be used as a factor for analyzing the cause of the deviation.

[0128] At this time, the control unit (100) can increase the number of deviation occurrences (COUNTdev) when the voltage deviation accumulation data and the SOC deviation accumulation data enter a normal range. Additionally, when the voltage deviation accumulation data and the SOC deviation accumulation data enter a normal range, the control unit (100) can initialize the voltage deviation accumulation data, SOC deviation accumulation data, elapsed time accumulation data, final voltage deviation, final SOC deviation, final elapsed time, maximum voltage deviation, and maximum SOC deviation corresponding to the stored value (e) of FIG. 6.

[0129] However, the control unit (100) may exclude deviation fluctuations within the normal range based on the maximum deviation (Vdev_max, SOCdev_max) in the charge / discharge cycle according to the battery usage mode from the number of deviation occurrences.

[0130] When the control unit (100) determines that the voltage deviation accumulation data and the SOC deviation accumulation data have entered the normal range (e.g., 1200), it can temporarily store the maximum deviation of the current charge / discharge cycle (1210).

[0131] Subsequently, the control unit (100) can compare the maximum deviation stored in the previous charge / discharge cycle with the maximum deviation of the current cycle (1220). If the control unit (100) determines that the maximum deviation of the current cycle is greater than the maximum deviation stored in the previous charge / discharge cycle, it can update the stored maximum deviation to the maximum deviation of the current cycle (1230).

[0132] Accordingly, the control unit (100) can determine the cause of the defect in the battery cell based on the maximum value of the voltage and SOC deviation occurring in the battery cell by continuously updating the maximum deviation.

[0133] Additionally, the control unit (100) may grant the user the authority to initialize the deviation occurrence count (COUNT_dev) and maximum deviation (Vdev_max, SOCdev_max) data only when the user resolves the cause of the defect in the battery cell. Accordingly, the reliability of the deviation occurrence count (COUNT_dev) and maximum deviation (Vdev_max, SOCdev_max) data can be improved.

[0134] As such, the battery management device according to one embodiment utilizes accumulated voltage and SOC deviation data in addition to voltage and SOC deviation data, thereby having the effect of diagnosing the cause of battery failure in more detail.

[0135] Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium that stores instructions executable by a computer. The instructions may be stored in the form of program code and, when executed by a processor, may generate a program module to perform the operation of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.

[0136] Computer-readable recording media include all types of recording media that store instructions that can be decoded by a computer. Examples include ROM (read-only memory), RAM (random access memory), magnetic tape, magnetic disk, flash memory, optical data storage devices, etc.

[0137] Additionally, computer-readable recording media may be provided in the form of non-transitory storage media. Here, 'non-transitory storage media' simply means that it is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily. For example, 'non-transitory storage media' may include a buffer in which data is stored temporarily.

[0138] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in 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 recording medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., downloadable app) may be temporarily stored or temporarily created in a device-readable recording medium such as a manufacturer's server, an application store's server, or a relay server's memory (102).

[0139] In the foregoing, although all components constituting the embodiments disclosed in this document have been described as being combined or operating in combination, the embodiments disclosed in this document are not necessarily limited to such embodiments. That is, within the scope of the purposes of the embodiments disclosed in this document, all components may be selectively combined in one or more ways to operate.

[0140] Furthermore, terms such as "include," "compose," or "have" as described above, unless specifically stated otherwise, mean that the relevant component may be inherent; thus, 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 contextual meanings in the relevant technology and, unless explicitly defined in this document, should not be interpreted in an ideal or overly formal sense.

[0141] 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 such 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. Explanation of the symbols

[0142] 1: Battery Management Unit 2: Current sensor 3: Voltage sensor 4: External device 10: Battery System 12: Multiple battery modules 13: Battery cell 14: Sensor section 16: Switching section 20: Upper controller 100: Control unit 110: Processor 120: Memory 200: Communications Department 210: Wireless Communications Unit 220: Wired Communications Department

Claims

Claim 1 A battery management device comprising: a memory configured to store instructions; and a processor configured to execute said instructions, wherein the processor is configured to acquire battery data including voltage and current measured from a plurality of battery cells, generate voltage deviation accumulation data by accumulating voltage deviations between the plurality of battery cells according to a change in the operating state of the battery management device, determine the SOC of the plurality of battery cells based on the current, generate SOC deviation accumulation data by accumulating SOC deviations between the plurality of battery cells according to a change in the operating state of the battery management device, and determine the cause of failure of the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data. Claim 2 A battery management device according to claim 1, wherein the processor determines the time required for the increase of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determines the cause of the deviation occurrence corresponding to the time required for the increase as the cause of defect in the plurality of battery cells. Claim 3 A battery management device according to claim 1, wherein the processor determines the number of occurrences of deviations of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determines the cause of the deviation occurrence corresponding to the number of occurrences of deviations as the cause of defects of the plurality of battery cells. Claim 4 A battery management device according to claim 1, wherein the processor determines the maximum deviation of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determines the cause of the deviation corresponding to the maximum deviation as the cause of failure of the plurality of battery cells. Claim 5 A battery management device according to claim 1, wherein the processor determines the time required from the point of maximum deviation occurrence to the next point of maximum deviation occurrence based on the voltage deviation accumulation data and the SOC deviation accumulation data, and determines the cause of deviation occurrence corresponding to the time required as the cause of defect in the plurality of battery cells. Claim 6 A battery management device according to claim 5, wherein the processor determines a maximum deviation occurrence rate based on the required time and determines a cause of deviation occurrence corresponding to the maximum deviation occurrence rate as a cause of defect in the plurality of battery cells. Claim 7 A battery management device according to claim 1, wherein the processor resets the accumulated data based on the voltage deviation accumulated data and the SOC deviation accumulated data being included in a normal range. Claim 8 A battery management device according to claim 7, wherein the processor stores the maximum deviation up to the reset point based on the fact that the accumulated data has been reset, and stores the larger value by comparing the maximum deviation previously stored with the maximum deviation up to the reset point. Claim 9 A battery management method comprising: a step of obtaining voltage and current measured from a plurality of battery cells; a step of generating voltage deviation accumulation data by accumulating voltage deviations between the plurality of battery cells according to a change in the operating state of the battery management device; a step of determining the SOC of the plurality of battery cells based on the current; a step of generating SOC deviation accumulation data by accumulating SOC deviations between the plurality of battery cells according to a change in the operating state of the battery management device; and a step of determining the cause of failure of the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data. Claim 10 A battery management method according to claim 9, wherein the step of determining the cause of defects of the plurality of battery cells comprises: a step of determining the time required for the increase of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data; and a step of determining the cause of deviation occurrence corresponding to the time required for the increase as the cause of defects of the plurality of battery cells. Claim 11 A battery management method according to claim 9, wherein the step of determining the cause of defects of the plurality of battery cells comprises: a step of determining the number of occurrences of deviations of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data; and a step of determining the cause of deviation occurrence corresponding to the number of occurrences of deviations as the cause of defects of the plurality of battery cells. Claim 12 A battery management method according to claim 9, wherein the step of determining the cause of defects of the plurality of battery cells comprises: a step of determining the maximum deviation of the voltage deviation and the SOC deviation based on the voltage deviation accumulation data and the SOC deviation accumulation data; and a step of determining the cause of deviation occurrence corresponding to the maximum deviation as the cause of defects of the plurality of battery cells. Claim 13 A battery management method according to claim 9, wherein the step of determining the cause of failure of the plurality of battery cells comprises: a step of determining the time required from the point of maximum deviation occurrence to the next point of maximum deviation occurrence based on the voltage deviation accumulation data and the SOC deviation accumulation data; and a step of determining the cause of deviation occurrence corresponding to the time required as the cause of failure of the plurality of battery cells. Claim 14 A battery management method according to claim 13, wherein the step of determining the cause of defects of the plurality of battery cells comprises: a step of determining the maximum deviation occurrence rate based on the required time; and a step of determining the cause of deviation occurrence corresponding to the maximum deviation occurrence rate as the cause of defects of the plurality of battery cells. Claim 15 A battery management method according to claim 9, further comprising: a step of resetting the accumulated data based on the fact that the voltage deviation accumulated data and the SOC deviation accumulated data are included in a normal range; and a step of storing the maximum deviation up to the reset point based on the fact that the accumulated data has been reset, wherein the maximum deviation up to the reset point is compared with the maximum deviation previously stored and the maximum deviation up to the reset point and the larger value is stored. Claim 16 A computer-readable recording medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform the battery management method of any one of claims 9 to 15.

Images