Battery management device and battery management method

Abstract

A battery management device disclosed in the present document comprises: a sensor unit for measuring the voltage and current of a plurality of battery cells; and a control unit for generating accumulated voltage deviation data in which deviations between the voltages of the plurality of battery cells are accumulated, determining the SOC of the plurality of battery cells on the basis of the currents, generating accumulated SOC deviation data in which deviations between the SOC of the plurality of battery cells are accumulated, and determining the cause of failure of the plurality of battery cells on the basis of the accumulated voltage deviation data and the accumulated SOC deviation data.

Description

Battery management device and battery management method

[0001] Cross-citation with related applications

[0002] This application claims the benefit of priority from Republic of Korea Patent Application No. 10-2023-0121004, filed September 12, 2023, the entire contents of which are incorporated herein by reference.

[0003] Technology field

[0004] The embodiments disclosed in this document relate to a battery management device and a battery management method for diagnosing a battery condition.

[0005] Recently, active research and development is being conducted on secondary batteries. The term "secondary battery" refers to a rechargeable battery, encompassing both conventional Ni / Cd and Ni / MH batteries, as well as more recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of a much higher energy density than conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form, making them suitable for use as power sources for mobile devices. Furthermore, lithium-ion batteries are attracting attention as a next-generation energy storage medium, as their use is expanding to include power sources for electric vehicles.

[0006] Defective battery cells, such as tab breaks or lithium deposition, can pose safety risks when used in these batteries, and research is underway on faulty battery cell detection algorithms. Conventional methods simply diagnose battery abnormalities based on voltage and SOC (State of Charge) deviations. However, these methods require high deviation thresholds to prevent overdiagnosis, delaying diagnosis. Furthermore, because the cause of the battery abnormality cannot be determined, all related components must be replaced, resulting in significant cost losses.

[0007] According to one embodiment disclosed in this document, a battery management device and a battery management method are provided that can easily identify the cause of voltage and SOC (State Of Charge) deviations by utilizing accumulated deviation data.

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

[0009] A battery management device according to one embodiment includes a sensor unit that measures voltage and current of a plurality of battery cells, a control unit that generates voltage deviation accumulation data by accumulating deviations between voltages of the plurality of battery cells, determines SOC of the plurality of battery cells based on the current, generates SOC deviation accumulation data by accumulating deviations between SOCs of the plurality of battery cells, and determines a cause of failure of the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data.

[0010] The control unit can determine the time required for an increase in 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 increase time as a cause of a defect in the plurality of battery cells.

[0011] The control unit may 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 a cause of a defect in the plurality of battery cells.

[0012] The control unit may 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 a defect in the plurality of battery cells.

[0013] The control unit may determine the time required from the time of occurrence of the maximum deviation to the time of occurrence of the next maximum 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 as the cause of a defect in the plurality of battery cells.

[0014] The control unit can determine the maximum deviation occurrence rate based on the required time, and determine the cause of deviation corresponding to the maximum deviation occurrence rate as a cause of defects in the plurality of battery cells.

[0015] The control unit can reset the accumulated data based on whether the voltage deviation accumulated data and the SOC deviation accumulated data fall within a normal range.

[0016] The above control unit stores the maximum deviation up to the reset point based on the fact that the accumulated data has been reset, and can compare the maximum deviation stored in advance with the maximum deviation up to the reset point and store a larger value.

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

[0018] Determining the cause of a defect in the plurality of battery cells may include determining the time required for an increase in 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 a deviation corresponding to the time required for the increase as the cause of a defect in the plurality of battery cells.

[0019] Determining the cause of a defect in the plurality of battery cells may include determining 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 determining the cause of the deviation corresponding to the number of occurrences of the deviation as the cause of a defect in the plurality of battery cells.

[0020] Determining the cause of a defect in the plurality of battery cells may include 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 the deviation corresponding to the maximum deviation as the cause of a defect in the plurality of battery cells.

[0021] Determining the cause of a defect in the plurality of battery cells may include determining the time required from the time of occurrence of the maximum deviation to the time of occurrence of the next maximum 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 as the cause of the defect in the plurality of battery cells.

[0022] Determining the cause of a defect in the plurality of battery cells may include determining the maximum deviation occurrence rate based on the required time, and determining the cause of a defect corresponding to the maximum deviation occurrence rate as the cause of a defect in the plurality of battery cells.

[0023] A battery management method according to one embodiment may further include resetting the accumulated data based on whether the voltage deviation accumulated data and the SOC deviation accumulated data fall within a normal range.

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

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

[0026] According to a battery management device according to one embodiment, the cause of voltage or SOC (State Of Charge) deviation can be analyzed and balancing can be performed without replacing parts to reduce the deviation, thereby reducing the time and cost required for cause analysis.

[0027] FIG. 1 illustrates a block diagram of a typical battery system including a battery management device according to one embodiment.

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

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

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

[0031] FIG. 5 illustrates state changes of a battery management device according to one embodiment.

[0032] FIG. 6 illustrates values ​​stored based on state changes in a battery management device according to one embodiment.

[0033] FIGS. 7 to 10 illustrate graphs of accumulated deviation data obtained from a battery management device according to one embodiment.

[0034] FIG. 11 illustrates a flowchart of a battery management method according to one embodiment.

[0035] FIG. 12 continues the flowchart of a battery management method according to one embodiment of FIG. 11.

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

[0037] With respect to the various embodiments disclosed in this document, specific structural and functional descriptions are merely illustrative 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 construed as being limited to the embodiments described in this document.

[0038] The expressions "first," "second," "first," or "second" used in various embodiments may describe various components, regardless of order and / or importance, and do not limit the components. For example, without departing from the scope of the embodiments disclosed herein, a first component may be renamed a second component, and similarly, a second component may also be renamed a first component.

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

[0040] All terms used herein, including technical or scientific terms, have the same meaning as commonly understood by those of ordinary skill in the art of the embodiments disclosed herein. Terms defined in commonly used dictionaries may be interpreted as having the same or similar meaning in the context of the relevant technology, and unless explicitly defined herein, they shall not be interpreted in an idealized or overly formal sense. In some cases, even if a term is defined herein, it cannot be interpreted to exclude the embodiments disclosed herein.

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

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

[0043] 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), sensor units (14), switching units (16), and battery management devices (1).

[0044] A plurality of battery modules (12) may include at least one rechargeable battery cell (13). The battery cell (13) may include a cathode, a cathode material, a cathode material, a separator, an electrolyte, a polymer, and a case. In this case, the plurality of battery modules (12) may be connected in series or in parallel.

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

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

[0047] The current sensor (2) may include any configuration that generates a signal corresponding to the size 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 in the battery.

[0048] The current sensor (2) can measure the battery current flowing in 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 cycle during a charging cycle in which the battery is charged with power from an external device or a discharging cycle in which the battery is discharged, and transmit the measurement results to the battery management device (1).

[0049] The voltage sensor (3) can be configured to be connected in parallel to the battery, detect the battery voltage, which is the voltage across both terminals of the battery, and generate a voltage signal representing the detected battery voltage.

[0050] The temperature sensor may be configured to measure the battery temperature and generate a temperature signal representing the measured battery temperature. The temperature sensor may be positioned within the 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 the cell group and may detect the surface temperature of the battery cell as the battery temperature.

[0051] The temperature sensor may be configured to measure the external temperature, which is the temperature at a predetermined location away from the battery, and generate a temperature signal representing the measured external temperature. The temperature sensor may be positioned at a predetermined location outside the case where heat exchange between the battery and the atmosphere occurs. According to an embodiment, the temperature sensor may be implemented using one or a combination of two or more known temperature detection elements, such as a thermocouple, a thermistor, or a bimetal. The current flowing in the battery system (10) may be detected. At this time, the detection signal may be transmitted to the battery management device (1).

[0052] 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 connection relationships between the configurations shown in Fig. 1 are only examples and are not limited thereto.

[0053] The switching unit (16) is connected in series to the (+) terminal side or the (-) terminal side of the battery module (12) to control the charge / discharge current flow of the battery module (12). For example, the switching unit (16) may use at least one relay, magnetic contactor, etc. depending on the specifications of the battery system (10).

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

[0055] The battery management device (1) is an interface for receiving values ​​measured from various parameters, and may include a plurality of terminals and a circuit connected to these terminals to process the values ​​received. In addition, the battery management device (1) may control the ON / OFF of a switching unit (16), for example, a relay or a contactor, and may be connected to a battery module (12) to monitor the status of each battery module (12).

[0056] 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 status of the battery.

[0057] The upper controller (20) can transmit a control signal for controlling the battery module (12) to the battery management device (1). Accordingly, the battery management device (1) can be controlled for operation based on the control signal received from the upper controller (20). In addition, the battery module (12) may be a component included in an ESS (Energy Storage System). 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 this purpose.

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

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

[0060] 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 transmit results diagnosed by the battery management device (1).

[0061] 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 results to the user terminal so that the user can check them. At this time, the user terminal may include, but is not limited to, a personal computer, a terminal, a portable telephone, a smart phone, a handheld device, a wearable device, etc.

[0062] In addition, when the external device (4) is a server device, the server device may be implemented as various computing devices such as a workstation, a cloud, a data drive, a data station, etc. The server device may be implemented as one or more server devices that are physically or logically separated based on function, detailed configuration of function, or data, etc., and may transmit and receive data and process the transmitted and received data through communication between each server device.

[0063] 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.

[0064] 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 for calculating characteristic values ​​of battery cells, class classification, and lifespan estimation, as well as various data, from a separately provided external server.

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

[0066] The short-range communication module can communicate with an external device (4) adjacent to the 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).

[0067] 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 may transmit and receive a wireless signal with at least one of a base station, an external terminal, and an external device (4) on a mobile communication network. In addition, the remote communication module may communicate with an external device (4) or an external device (4) such as another electronic device through a surrounding access point (AP). The access point (AP) may connect a local area 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) may be connected to the communication server through the wide area network (WAN) with the external device (4) and communicate with each other.

[0068] 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 through Ethernet (IEEE 802.3 technology standard) or connect to a wired communication network through CAN communication, and transmit and receive data with external devices (4) through the wired communication network.

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

[0070] The memory (120) can store various information necessary for operating the battery management device (1). Specifically, the memory (120) can store an operating system and a program necessary for operating the battery management device (1), or store data necessary for operating the battery management device (1).

[0071] Specifically, the memory (120) can store various programs related to calculating characteristic values ​​of battery cells, classifying classes, and estimating lifespan. In addition, the memory (120) can store various data such as voltage, current, and characteristic value data of each battery cell.

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

[0073] The memory (120) may include volatile memory (120) such as Static Random Access Memory (S-RAM) and Dynamic Random Access Memory (D-RAM) for temporarily storing data. In addition, the memory (120) may include nonvolatile memory (120) such as Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM), and Electrically Erasable Programmable Read Only Memory (EEPROM) for long-term storage of data.

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

[0075] 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.

[0076] Specifically, the control unit (100) can generate voltage deviation accumulation data that accumulates deviations between voltages measured in a plurality of battery cells, and the control unit (100) can generate SOC deviation accumulation data that accumulates deviations between SOCs (State Of Charges) of a plurality of battery cells.

[0077] To this end, the control unit (100) can determine the SOC of multiple battery cells based on the current measured from the multiple battery cells.

[0078] In addition, the control unit (100) can determine the time required for increasing 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 time required for increasing the time as the cause of a defect in a plurality of battery cells.

[0079] The control unit (100) can determine the number of occurrences of 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 number of occurrences of the deviation as the cause of a defect in a plurality of battery cells.

[0080] 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 a defect in a plurality of battery cells.

[0081] The control unit (100) can determine the time required from the time of occurrence of the maximum deviation to the time of occurrence of the next maximum 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 as the cause of a defect in a plurality of battery cells.

[0082] The control unit (100) can determine the maximum deviation occurrence rate based on the required time, and determine the deviation occurrence cause corresponding to the maximum deviation occurrence rate as the cause of defects in multiple 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.

[0083] In addition, the control unit (100) can reset the accumulated data based on whether the voltage deviation accumulated data and the SOC deviation accumulated data fall within a normal range, and the control unit (100) can store the maximum deviation up to the reset point based on the reset of the accumulated data, but can compare the maximum deviation up to the reset point with the maximum deviation that was previously stored and store the larger value. In this way, the control unit (100) can continuously update the maximum deviation to determine the cause of the deviation.

[0084] In this way, the battery management device according to one embodiment can diagnose whether a defect has occurred in a battery cell by utilizing the accumulated voltage deviation data and the accumulated SOC deviation data of the battery cell, and thus has a significant effect of improving the reliability of the diagnosis.

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

[0086] Referring to FIG. 3, the control unit (100) can receive current and voltage of a plurality of battery cells from the sensor unit (14). Thereafter, 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 the current integration method or the OCV (Open Circuit Voltage) measurement method.

[0087] 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. In addition, the processor (110) can generate deviation accumulation data (b) including voltage deviation accumulation data and SOC deviation accumulation data, which are distinguished according to the battery usage mode.

[0088] In this way, the battery management device according to one embodiment can store both deviation data (a) and deviation accumulation data (b) in the memory (120). That is, unlike the conventional technology that stores only deviation data (a) in the memory (120), the battery management device can store deviation data (a) and deviation accumulation data (b) for deviation increase / decrease in the storage unit.

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

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

[0091] 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 determine an SOC of a battery cell based on the current value.

[0092] Thereafter, 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 the preset reference SOC and the calculated SOC of the battery cell.

[0093] 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.

[0094] In Fig. 4, voltage deviation cumulative data is generated first and SOC deviation cumulative data is generated later, but there is no restriction on the order, and SOC deviation cumulative data may be generated first and then voltage deviation cumulative data, or they may be generated simultaneously and in parallel.

[0095] Thereafter, the deviation occurrence cause analysis unit (103) of the control unit (100) can determine the cause of the deviation occurrence based on the SOC deviation accumulation data and the voltage deviation accumulation data. Specifically, the control unit (100) can generate and visualize the accumulated data according to the battery usage mode, and interpret the visualized graph to determine the cause of the deviation occurrence. This will be described in detail in FIG. 5 and below.

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

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

[0098] For another example, if the deviation remains constant during battery charging in the SOC deviation accumulation data, the control unit (100) may determine that the deviation cannot be reduced through cell balancing, and the control unit (100) may determine that there is a problem with the cell balancing function.

[0099] Accordingly, the control unit (100) can determine the cause of the deviation as non-performance of the cell balancing operation, and can determine the cause of the typified defect as a failure of the cell balancing function.

[0100] Thereafter, 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).

[0101] 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 in a battery management device according to one embodiment.

[0102] First, referring to FIG. 5, the state of the battery management device can change depending on the battery usage mode, and the states of the battery management device can be divided into an initial state (a), a charging state (b), an operating state (c), and a stationary state (d). That is, the initial state (a) may mean a standby state before the battery is used, the charging state (b) may mean a state in which the battery is connected to a power source and being charged, the operating state (c) may mean a state in which the battery is being discharged and used, and the stationary state (d) may mean a state in which the charging state (b) or the operating state (d) is terminated.

[0103] For example, as shown in the solid line portion of Fig. 5, the state of the battery management device according to the battery usage mode can change from the initial state (a) to the operating state (c), can change from the operating state (c) to the charging state (b), can change from the charging state (b) back to the operating state (c), can change from the operating state (c) to the stationary state (d), and can change from the stationary state (d) to the initial state (a) to form one cycle.

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

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

[0106] At this time, if we look at the storage value details (f), the voltage deviation cumulative data (acc_Vdev_r) can be determined as a value obtained by adding the voltage deviation change amount (△Vdev_r) to the previous voltage deviation cumulative data (acc_Vdev_r) (acc_Vdev_r = acc_Vdev_r + △Vdev_r). In addition, the SOC deviation cumulative data (acc_SOCdev_r) can be determined as a value obtained by adding the SOC deviation change amount (△SOCdev_r) to the previous SOC deviation cumulative data (acc_SOCdev_r) (acc_SOCdev_r = acc_SOCdev_r + △SOCdev_r). In addition, the accumulated time data (Tr) can be determined as a value obtained by adding the accumulated time change amount (△Tr) to the previous accumulated time data (Tr) (Tr = Tr + △Tr).

[0107] In addition, if we look at the delta (△) value details (g), the voltage deviation change amount (△Vdev_r) can mean the value obtained by subtracting the voltage deviation (Vdev_end) of the previous stage, which is the end state, from the voltage deviation (Vdev_init) of the initial state (△Vdev_r = Vdev_init - Vdev_end). In addition, the SOC deviation change amount (△SOCdev_r) can mean the value obtained by subtracting the SOC deviation (SOCdev_end) of the previous stage, which is the end state, from the SOC deviation (SOCdev_init) of the initial state (△SOCdev_r = SOCdev_init - SOCdev_end). In addition, the accumulated time change amount (△Tr) can mean the value obtained by subtracting the accumulated time (Tend) of the previous stage, which is the end state, from the accumulated time (T_init) of the initial state (△Tr = Tinit - Tend).

[0108] 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 voltage deviation accumulation data (acc_Vdev_d), SOC deviation accumulation data (acc_SOCdev_d) and accumulated time data (Td) as storage values ​​(e) in the memory (120).

[0109] At this time, if we look at the storage value details (f), the voltage deviation cumulative data (acc_Vdev_d) can be determined as a value obtained by adding the voltage deviation change amount (△Vdev_d) to the previous voltage deviation cumulative data (acc_Vdev_d) (acc_Vdev_d = acc_Vdev_d + △Vdev_d). In addition, the SOC deviation cumulative data (acc_SOCdev_d) can be determined as a value obtained by adding the SOC deviation change amount (△SOCdev_d) to the previous SOC deviation cumulative data (acc_SOCdev_d) (acc_SOCdev_d = acc_SOCdev_d + △SOCdev_d). In addition, the cumulative time data (Td) can be determined as a value obtained by adding the cumulative time change amount (△Td) to the previous cumulative time data (Td) (Td = Td + △Td).

[0110] In addition, if we look at the delta (△) value details (g), the voltage deviation change amount (△Vdev_d) can mean the value obtained by subtracting the voltage deviation (Vdev_init) of the initial state, which is the previous step, from the voltage deviation (Vdev_d) of the operating state (△Vdev_d) (△Vdev_d = Vdev_d - Vdev_init). In addition, the SOC deviation change amount (△SOCdev_d) can mean the value obtained by subtracting the SOC deviation (SOCdev_init) of the initial state, which is the previous step, from the SOC deviation (SOCdev_d) of the operating state (△SOCdev_d = SOCdev_d - SOCdev_init). In addition, the accumulated time change amount (△Td) can mean the value obtained by subtracting the accumulated time (Tinit) of the initial state, which is the previous step, from the accumulated time (T_d) of the operating state (△Td = Td - Tinit).

[0111] 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 voltage deviation accumulation data (acc_Vdev_c), SOC deviation accumulation data (acc_SOCdev_c), and accumulated time data (Tc) in the memory (120) as storage values ​​(e).

[0112] At this time, if we look at the storage value details (f), the voltage deviation cumulative data (acc_Vdev_c) can be determined as a value obtained by adding the voltage deviation change amount (△Vdev_c) to the previous voltage deviation cumulative data (acc_Vdev_c) (acc_Vdev_c = acc_Vdev_c + △Vdev_c). In addition, the SOC deviation cumulative data (acc_SOCdev_c) can be determined as a value obtained by adding the SOC deviation change amount (△SOCdev_c) to the previous SOC deviation cumulative data (acc_SOCdev_c) (acc_SOCdev_c = acc_SOCdev_c + △SOCdev_c). In addition, the cumulative time data (Tc) can be determined as a value obtained by adding the cumulative time change amount (△Tc) to the previous cumulative time data (Tc) (Tc = Tc + △Tc).

[0113] In addition, if we look at the delta (△) value details (g), the voltage deviation change amount (△Vdev_c) can mean the value obtained by subtracting the voltage deviation (Vdev_d) of the operating state, which is the previous stage, from the voltage deviation (Vdev_c) of the charging state (△Vdev_c = Vdev_c - Vdev_d). In addition, the SOC deviation change amount (△SOCdev_c) can mean the value obtained by subtracting the SOC deviation (SOCdev_d) of the operating state, which is the previous stage, from the SOC deviation (SOCdev_c) of the charging state (△SOCdev_c = SOCdev_c - SOCdev_d). In addition, the accumulated time change amount (△Tc) can mean the value obtained by subtracting the accumulated time (Td) of the operating state, which is the previous stage, from the accumulated time (Tc) of the charging state (△Tc = Tc- Td).

[0114] Next, in step (d) where the state of the battery management device changes from an operating state to a stationary state, the control unit (100) can store voltage deviation accumulation data (acc_Vdev_d), SOC deviation accumulation data (acc_SOCdev_d), and accumulated time data (Td) as storage values ​​(e) in the memory (120). In addition, in the stationary step, the voltage deviation (Vdev_end), SOC deviation (SOCdev_end), measurement time (Tend), maximum voltage deviation (Vdev_max), and maximum SOC deviation (SOCdev_max) can be stored together with the accumulated data. Accordingly, as described above, the control unit (100) can utilize not only the accumulated deviation data but also the non-accumulated deviation data to determine whether a battery cell is abnormal.

[0115] At this time, if we look at the storage value details (f), the voltage deviation cumulative data (acc_Vdev_d) can be determined as a value obtained by adding the voltage deviation change amount (△Vdev_d) to the previous voltage deviation cumulative data (acc_Vdev_d) (acc_Vdev_d = acc_Vdev_d + △Vdev_d). In addition, the SOC deviation cumulative data (acc_SOCdev_d) can be determined as a value obtained by adding the SOC deviation change amount (△SOCdev_d) to the previous SOC deviation cumulative data (acc_SOCdev_d) (acc_SOCdev_d = acc_SOCdev_d + △SOCdev_d). In addition, the cumulative time data (Td) can be determined as a value obtained by adding the cumulative time change amount (△Td) to the previous cumulative time data (Td) (Td = Td + △Td).

[0116] In addition, if we look at the details of the delta (△) value (g), the voltage deviation change amount (△Vdev_d) can mean the value obtained by subtracting the voltage deviation (Vdev_c) of the previous stage, which is the charging state, from the voltage deviation (Vdev_end) of the stationary state (△Vdev_d = Vdev_end - Vdev_c). In addition, the SOC deviation change amount (△SOCdev_d) can mean the value obtained by subtracting the SOC deviation (SOCdev_c) of the previous stage, which is the charging state, from the SOC deviation (SOCdev_end) of the stationary state (△SOCdev_d = SOCdev_end - SOCdev_c). In addition, the accumulated time change amount (△Td) can mean the value obtained by subtracting the accumulated time (Tc) of the initial state, which is the previous stage, from the accumulated time (Tend) of the operating state (△Td = Tend - Tc).

[0117] The storage values ​​described above are exemplary and may vary depending on the charge / discharge cycle. Below, a process for determining the cause of a failure based on the storage values ​​by a battery management device according to one embodiment is described.

[0118] FIGS. 7 to 10 illustrate graphs of accumulated deviation data obtained from a battery management device according to one embodiment.

[0119] 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 deviation by interpreting the visualized graph. (a) of FIG. 7 may refer to the total voltage deviation (V_dev), (b) may refer to the voltage deviation accumulation data (acc_Vdev_c) in the charging mode, (c) may refer to the voltage deviation accumulation data (acc_Vdev_d) in the operating mode, and (d) may refer to the voltage deviation accumulation data (acc_Vdev_end) in the stop or idle mode.

[0120] In Fig. 7, it can be confirmed that the voltage deviation of the battery cells increases overall based on the increase in the total voltage deviation (a). In addition, the battery management device according to one embodiment can acquire accumulated deviation data according to the battery usage mode, thereby determining the cause of the deviation and the corresponding cause of the failure.

[0121] In addition, the control unit (100) can determine the cause of the corresponding deviation since the voltage deviation accumulation data (b) in the charging mode has a positive deviation and is accumulated, and the voltage deviation accumulation data (c) in the operating mode has a negative deviation and is accumulated. In addition, the voltage deviation accumulation data (d) in the stop or idle mode has a positive deviation and is accumulated, and thus the cause of the corresponding deviation can be determined.

[0122] Referring to FIG. 8 together, (a) of FIG. 8 may mean total voltage deviation (V_dev), (b) may mean voltage deviation accumulation data (acc_Vdev_on) in charge / discharge mode, and (c) may mean voltage deviation accumulation data (acc_Vdev_end) in idle mode.

[0123] In Fig. 7, the voltage deviation accumulation data of the charging mode and the operating mode have positive and negative deviations, respectively, and in Fig. 8, the voltage deviation accumulation data (b) in the charge / discharge mode including the charging mode and the operating mode can be displayed as having a positive deviation with a small slope because the positive and negative deviations are offset.

[0124] 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. Thereafter, 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.

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

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

[0127] In Fig. 9, it can be confirmed that the SOC deviation of the battery cells 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, it can determine the cause of the deviation and the corresponding cause of the failure.

[0128] In addition, the control unit (100) can determine the cause of the corresponding deviation since the SOC deviation accumulation data (b) in the charging mode has a negative deviation and is accumulated, and the SOC deviation accumulation data (c) in the operating mode has a positive deviation and is accumulated. In addition, the SOC deviation accumulation data (d) in the stop or idle mode has a positive deviation and is accumulated, so the cause of the corresponding deviation can be determined.

[0129] Referring to FIG. 10 together, (a) of FIG. 10 may mean total SOC deviation (SOC_dev), (b) may mean SOC deviation accumulation data (acc_SOCdev_on) in charge / discharge mode, and (c) may mean SOC deviation accumulation data (acc_SOCdev_end) in idle mode.

[0130] In Fig. 9, the SOC deviation accumulation data of the charging mode and the operating mode have negative and positive deviations, respectively, and in Fig. 10, the SOC deviation accumulation data (b) in the charge / discharge mode including the charging mode and the operating mode can be displayed as a graph close to horizontal because the positive and negative deviations are offset.

[0131] Accordingly, the control unit (100) can determine that the cause affecting the increase in the total SOC deviation (a) occurred in the idle mode. In addition, for example, assuming that the SOC deviation increase rate is 4.3% / day, the control unit (100) can determine that the cause of the deviation is low voltage by determining that it is similar to the deviation increase rate in the low voltage state, and can select a corresponding defective cause and transmit it to the external device (4).

[0132] In this way, the battery management device according to one embodiment can utilize accumulated deviation data in addition to voltage and SOC deviations, thereby enabling more detailed analysis of the cause of battery failure.

[0133] FIG. 11 illustrates a flowchart of a battery management method according to one embodiment, and FIG. 12 continues the flowchart of the battery management method according to one embodiment from FIG. 11.

[0134] Referring to FIG. 11, the control unit (100) can receive voltages and currents of multiple battery cells from the sensor unit (14) (1100). Thereafter, the control unit (100) can generate voltage deviation accumulation data that accumulates voltage deviations of multiple battery cells (1110).

[0135] Additionally, the control unit (100) can determine the SOC of the plurality of battery cells based on the current of the plurality of battery cells (1120). Thereafter, the control unit (100) can generate SOC deviation accumulation data that accumulates the deviation between the SOCs of the plurality of battery cells (1130).

[0136] At this time, the control unit (100) can determine the cause of failure of multiple battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data (1140). Specifically, the control unit (100) can determine the cause of failure of the battery cells using information that can be obtained through each of the voltage deviation accumulation data and the SOC deviation accumulation data, or can determine the cause of failure of the battery cells using information that can be obtained by analyzing the voltage deviation accumulation data and the SOC deviation accumulation data together.

[0137] Continuing with reference to FIG. 12, the control unit (100) can determine whether the voltage deviation cumulative data and the SOC deviation cumulative data have entered the normal range (1200). That is, the control unit (100) can determine that the voltage deviation cumulative data and the SOC deviation cumulative data have entered the normal range if the deviations indicated in the voltage deviation cumulative data and the SOC deviation cumulative data have decreased to within the reference range. The control unit (100) can determine whether the deviation cumulative data has entered the normal range and use this to identify the cause of the deviation.

[0138] For example, if the voltage deviation cumulative data and the SOC deviation cumulative data show a deviation in a range that is judged to be a battery defect for a certain first time period, and then enter a normal range after the first time period, the control unit (100) can utilize the first time period as a factor for analyzing the cause of the deviation.

[0139] At this time, the control unit (100) can increase the number of deviation occurrences (COUNTdev) when the voltage deviation cumulative data and the SOC deviation cumulative data enter the normal range. In addition, the control unit (100) can initialize the voltage deviation cumulative data, SOC deviation cumulative data, elapsed time cumulative data, final voltage deviation, final SOC deviation, final elapsed time, maximum voltage deviation, and maximum SOC deviation corresponding to the storage value (e) of FIG. 6 when the voltage deviation cumulative data and the SOC deviation cumulative data enter the normal range.

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

[0141] If the control unit (100) determines that the voltage deviation cumulative data and the SOC deviation cumulative data have entered a normal range (example of 1200), it can temporarily store the maximum deviation of the current charge / discharge cycle (1210).

[0142] Thereafter, 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, the control unit (100) can update the stored maximum deviation to the maximum deviation of the current cycle (1230).

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

[0144] Additionally, the control unit (100) may grant the user the authority to initialize the number of deviation occurrences (COUNT_dev) and maximum deviation (Vdev_max, SOCdev_max) data only when the user has resolved the cause of a battery cell failure. Accordingly, the reliability of the number of deviation occurrences (COUNT_dev) and maximum deviation (Vdev_max, SOCdev_max) data may be improved.

[0145] In this way, the battery management device according to one embodiment utilizes voltage and SOC deviation cumulative data in addition to voltage and SOC deviation data, so it has the effect of diagnosing the cause of battery failure in more detail.

[0146] Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium storing computer-executable instructions. The instructions may be stored in the form of program code, and when executed by a processor, may generate program modules to perform the operations of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.

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

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

[0149] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable recording medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via 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 at least temporarily stored or temporarily generated on a machine-readable recording medium, such as a memory (102) of a manufacturer's server, an application store's server, or a relay server.

[0150] Although all components constituting the embodiments disclosed in this document have been described as being combined or operating in combination as one, the embodiments disclosed in this document are not necessarily limited to such embodiments. That is, within the scope of the purpose of the embodiments disclosed in this document, all of the components may be selectively combined and operated one or more times.

[0151] Furthermore, terms such as "include," "comprise," or "have" described above, unless specifically stated otherwise, imply that the corresponding component may be present, and therefore should be interpreted to include other components rather than excluding other components. All terms, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed in this document pertain, unless otherwise defined. Commonly used terms, such as terms defined in dictionaries, should be interpreted to be consistent with the contextual meaning of the relevant technology, and shall not be interpreted in an idealized or overly formal sense, unless explicitly defined in this document.

[0152] The above description is merely an illustrative description of the technical idea disclosed in this document, and those skilled in the art to which the embodiments disclosed in this document pertain may make various modifications and variations without departing from the essential characteristics of the embodiments disclosed in this document. Therefore, the embodiments disclosed in this document are not intended to limit the technical idea of ​​the embodiments disclosed in this document, but to explain it, and the scope of the technical idea disclosed in this document is not limited by these embodiments. The scope of protection of the technical idea disclosed in this document should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of rights of this document.

Claims

1. A sensor unit that measures the voltage and current of multiple battery cells; and Generate voltage deviation accumulation data by accumulating voltage deviations of the plurality of battery cells, Determine the SOC of the plurality of battery cells based on the current, and generate SOC deviation accumulation data by accumulating the deviation between the SOCs of the plurality of battery cells, A battery management device comprising a control unit that determines the cause of a defect in the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data.

2. In claim 1, The above control unit, A battery management device that determines the time required for an increase in 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 time required for the increase as a cause of a defect in the plurality of battery cells.

3. In claim 1, The above control unit, A battery management device that determines 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 determines the cause of the deviation corresponding to the number of occurrences of the deviation as a cause of a defect in the plurality of battery cells.

4. In claim 1, The above control unit, A battery management device that 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 a cause of a defect in the plurality of battery cells.

5. In claim 1, The above control unit, A battery management device that determines the time required from the time of occurrence of the maximum deviation to the time of occurrence of the next maximum deviation based on the above voltage deviation accumulation data and the above SOC deviation accumulation data, and determines the cause of the deviation corresponding to the time required as the cause of a defect in the plurality of battery cells.

6. In claim 6, The above control unit, A battery management device that determines the maximum deviation occurrence rate based on the above-mentioned time, and determines the cause of deviation corresponding to the maximum deviation occurrence rate as a cause of defects in the plurality of battery cells.

7. In claim 1, The above control unit, A battery management device that resets the accumulated data based on the voltage deviation accumulated data and the SOC deviation accumulated data being within a normal range.

8. In claim 7, The above control unit, A battery management device that stores the maximum deviation up to the reset point based on the above accumulated data being reset, and compares the maximum deviation stored in advance with the maximum deviation up to the reset point and stores the larger value.

9. Measure the voltage and current of multiple battery cells; Generate voltage deviation accumulation data by accumulating voltage deviations of the plurality of battery cells; Determine the SOC of the plurality of battery cells based on the current; Generate SOC deviation accumulation data by accumulating the deviation between the SOCs of the plurality of battery cells; A battery management method comprising: determining a cause of failure of the plurality of battery cells based on the voltage deviation accumulation data and the SOC deviation accumulation data.

10. In claim 9, Determining the cause of failure of the above multiple battery cells is as follows: A battery management method for determining the time required for an increase in 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 a cause of a defect in the plurality of battery cells.

11. In claim 9, Determining the cause of failure of the above multiple battery cells is as follows: A battery management method for determining 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 determining the cause of the deviation corresponding to the number of occurrences of the deviation as a cause of a defect in the plurality of battery cells.

12. In claim 9, Determining the cause of failure of the above multiple battery cells is as follows: A battery management method for 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 the deviation corresponding to the maximum deviation as a cause of a defect in the plurality of battery cells.

13. In claim 9, Determining the cause of failure of the above multiple battery cells is as follows: A battery management method for determining the time required from the time of occurrence of the maximum deviation to the time of occurrence of the next maximum deviation based on the above voltage deviation accumulation data and the above SOC deviation accumulation data, and determining the cause of the deviation corresponding to the time required as a cause of a defect in the plurality of battery cells.

14. In claim 9, Determining the cause of failure of the above multiple battery cells is as follows: A battery management method for determining the maximum deviation occurrence rate based on the above-mentioned time, and determining the cause of deviation corresponding to the maximum deviation occurrence rate as a cause of defect in the plurality of battery cells.

15. In claim 9, A battery management method further comprising: resetting the accumulated data based on the voltage deviation accumulated data and the SOC deviation accumulated data being within a normal range.

16. In claim 15, A battery management method further comprising: storing the maximum deviation up to the reset point based on the above accumulated data being reset, comparing the maximum deviation stored in advance with the maximum deviation up to the reset point and storing the larger value;

Images