Battery data management device and operation method thereof

Abstract

A battery data management device according to an embodiment disclosed in this document may include a controller that determines whether or not a battery has an abnormality based on battery data, determines an abnormality level of the battery based on the presence or absence of the abnormality of the battery, and divides and stores the battery data into a plurality of storages based on the abnormality level of the battery, and a memory including the plurality of storages and a temporary storage that temporarily stores the battery data.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] The embodiments disclosed in this document claim the benefit of priority based on Korean Patent Application No. 10-2022-0003019 filed on January 7, 2022, and all contents disclosed in the documents of the Korean patent application are incorporated by reference into this specification.

[0002] SUMMARY OF THE DISCLOSURE The embodiments disclosed herein relate to a battery data management apparatus and method of operation thereof. [Background technology]

[0003] An electric vehicle or an energy storage system (ESS) generates power by charging a number of batteries connected in series and / or parallel and driving a motor with the charged voltage. A battery may generate heat due to a chemical reaction that occurs during the process of charging and discharging electricity, and such heat may damage the performance and lifespan of the battery. Therefore, a battery management system (BMS) monitors battery data including the battery temperature, voltage, and current to diagnose the battery condition.

[0004] It is important that the storage storing such a large amount of battery data is efficiently managed according to the importance and use of the accumulated battery data. This is because a problem of delaying analysis of the cause of a battery abnormality may occur depending on the management method and form. Therefore, a battery data management device and method capable of efficiently managing the storage storing the battery data is required. Summary of the Invention [Problem to be solved by the invention]

[0005] One objective of the embodiments disclosed herein is to provide a battery data management device and an operating method thereof that can divide storage that stores battery data and efficiently manage the battery data.

[0006] 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 may be clearly understood by a person skilled in the art from the following description. [Means for solving the problem]

[0007] A battery data management device according to an embodiment disclosed in this document may include a controller that determines whether or not a battery has an abnormality based on battery data, determines an abnormality level of the battery based on the presence or absence of the abnormality of the battery, and divides and stores the battery data into a plurality of storages based on the abnormality level of the battery, and a memory including the plurality of storages and a temporary storage that temporarily stores the battery data.

[0008] According to one embodiment, the controller may store the battery data in one of the plurality of storages corresponding to an abnormality level of the battery.

[0009] According to one embodiment, the controller can store the battery data in one of the plurality of storage areas based on a priority of a plurality of storage areas in the one of the plurality of storage areas.

[0010] According to one embodiment, when the battery is diagnosed as being in an abnormal state, the controller may acquire battery data stored in the temporary storage at the time the battery is diagnosed as being in an abnormal state and battery data stored in the temporary storage after a certain period of time, and store the battery data in the plurality of storages in a divided manner.

[0011] According to an embodiment, the controller may determine whether the battery is at an abnormal level in descending order of risk of abnormality.

[0012] According to one embodiment, the memory can store the battery data in a circular queue in the temporary storage on a regular cycle.

[0013] According to one embodiment, the battery data may include at least one of the voltage, current, temperature, and diagnostic information for the battery.

[0014] An operating method of a battery data management device according to one embodiment disclosed in this document may include a step of temporarily storing battery data, a step of determining whether or not there is an abnormality in the battery based on the battery data, a step of determining an abnormality level of the battery based on the presence or absence of an abnormality in the battery, and a step of dividing and storing the battery data into a plurality of storages based on the abnormality level of the battery.

[0015] According to an embodiment, the step of determining an abnormality level of the battery based on the presence or absence of an abnormality in the battery may store the battery data in one of the plurality of storages corresponding to the abnormality level of the battery.

[0016] According to one embodiment, the step of dividing and storing the battery data into a plurality of storages based on the abnormality level of the battery may store the battery data in one of the plurality of storage areas based on a priority of a plurality of storage areas of one of the plurality of storage areas.

[0017] According to one embodiment, the step of temporarily storing the battery data may include, when the battery is diagnosed as being in an abnormal state, acquiring the battery data stored in the temporary storage at the time the battery is diagnosed as being in an abnormal state and the battery data stored in the temporary storage after a certain period of time, and storing the battery data separately in the plurality of storages.

[0018] According to an embodiment, the step of determining the abnormality level of the battery based on the presence or absence of an abnormality of the battery may determine whether the battery is at an abnormal level in descending order of risk of the abnormality level.

[0019] According to an embodiment, the step of temporarily storing the battery data may include storing the battery data in a circular queue of the temporary storage at a regular interval. Effect of the Invention

[0020] According to an embodiment of the battery data management device and an operating method thereof disclosed in this document, storage for storing battery data can be divided to efficiently manage the battery data. [Brief description of the drawings]

[0021] [Figure 1] 1 is a diagram illustrating a schematic configuration of a battery pack to which a battery data management device according to an embodiment disclosed herein is applied. [Diagram 2] FIG. 2 is a diagram illustrating the configuration of a battery data management device according to an embodiment disclosed in this document. [Diagram 3] 2 is a diagram for specifically explaining the overall operation of a battery data management device according to an embodiment disclosed in this document. [Figure 4] 11 is a diagram for specifically explaining the overall operation of a battery data management device according to another embodiment disclosed in the present document. [Diagram 5]1 is a flowchart illustrating a method of operation of a battery data management device according to one embodiment disclosed herein. [Figure 6] 1 is a block diagram showing a hardware configuration of a computing system for implementing an operating method of a battery data management device according to an embodiment disclosed herein; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] Some embodiments disclosed in this document will be described in detail below with reference to exemplary drawings. When attaching reference numerals to components in each drawing, attention should be paid to using the same numerals as much as possible for the same components even if they are displayed in different drawings. In addition, when describing the embodiments disclosed in this document, if a detailed description of related known configurations or functions is deemed to hinder understanding of the embodiments disclosed in this document, the detailed description will be omitted.

[0023] In describing the components of the embodiments disclosed in this document, terms such as first, second, A, B, (a), (b) and the like may be used. Such terms are intended to distinguish the components from other components, and do not limit the essence, order, or sequence of the components. In addition, unless otherwise defined, all terms used herein, including technical and 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 belong. Terms similar to those defined in commonly used dictionaries should be interpreted as meanings consistent with the meanings they have in the context of the relevant art, and should not be interpreted in an ideal and overly formal sense unless expressly defined in this document.

[0024] FIG. 1 illustrates a battery pack according to one embodiment disclosed herein.

[0025] Referring to FIG. 1 , a battery pack 1000 according to an embodiment disclosed herein may include a battery module 100, a battery management unit 200, and a relay 300.

[0026] The battery module 100 may include a number of battery cells 110, 120, 130, and 140. Although the number of battery cells is illustrated as four in FIG. 1, the number of battery cells is not limited thereto, and the battery module 100 may include n (n is a natural number equal to or greater than 2) battery cells.

[0027] The battery module 100 can supply power to a target device (not shown). To this end, the battery module 100 can be electrically connected to the target device. Here, the target device can include an electrical, electronic, or mechanical device that operates by receiving power from a battery pack 1000 including a plurality of battery cells 110, 120, 130, and 140, and for example, the target device can be, but is not limited to, an electric vehicle (EV).

[0028] The battery cells 110, 120, 130, 140 may be, but are not limited to, lithium ion (Li-ion) batteries, lithium ion polymer (Li-ion polymer) batteries, nickel cadmium (Ni-Cd) batteries, nickel metal hydride (Ni-MH) batteries, etc. Meanwhile, although FIG. 1 illustrates a case in which there is one battery module 100, according to an embodiment, the battery module 100 may be configured with a plurality of battery modules.

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

[0030] In addition, the battery management device 200 may monitor the voltage, current, temperature, etc. of the battery module 100 and / or each of the plurality of battery cells 110, 120, 130, 140 included in the battery module 100. In addition, sensors and various measurement modules (not shown) may be further installed in the battery module 100, a charge / discharge path, or any position of the battery module 100 for monitoring by the battery management device 200. The battery management device 200 may calculate parameters indicating the state of the battery module 100, such as a state of charge (SOC) or a state of health (SOH), based on the measured values ​​of the monitored voltage, current, temperature, etc.

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

[0032] The battery management unit 200 may calculate a cell balancing time for each of the battery cells 110, 120, 130, and 140. Here, the cell balancing time may be defined as a time required for balancing the battery cells. For example, the battery management unit 200 may calculate the cell balancing time based on a state of charge (SOC), a battery capacity, and a balancing efficiency for each of the battery cells 110, 120, 130, and 140.

[0033] The battery management unit 200 may include a battery data management unit 210.

[0034] The battery data management device 210 can acquire data of temperature and voltage measurements of a plurality of batteries, and SOC and SOH parameters derived therefrom. The battery data management device 210 can diagnose whether or not there is an abnormality in the battery based on the acquired data of the plurality of batteries. The battery data management device 210 can classify and store battery data based on whether or not there is an abnormality in the acquired data of the plurality of batteries.

[0035] The battery data management device 210 may transmit battery data acquired from a plurality of batteries to an external server and analyze and manage the battery data using the external server having abundant computing resources. In addition, the battery data management device 210 may precisely analyze abnormal phenomena of the battery through the external server and diagnose whether or not the battery is in an abnormal state in real time.

[0036] In addition, the battery data management device 210 may analyze and manage battery data acquired from a plurality of batteries using internal components with abundant computing resources, and may precisely analyze abnormal phenomena of the batteries through the internal components to diagnose whether or not the plurality of batteries are in an abnormal state.

[0037] FIG. 2 is a block diagram illustrating a configuration of a battery data management device according to an embodiment disclosed in this document.

[0038] Hereinafter, the configuration of the battery data management device 210 will be specifically described with reference to FIG.

[0039] First, referring to FIG. 2, a battery data management device 210 may include a memory 211 and a controller 212.

[0040] The memory 211 may include a temporary storage 10 capable of acquiring and temporarily storing battery data of the battery data management device, and a plurality of storages 20 capable of separately storing the battery data.

[0041] The temporary storage 10 may include a circular queue capable of storing battery data at a regular interval. A queue may be defined as a data structure that allocates continuous space and outputs data first. According to one embodiment, the circular queue may include five buffers. A buffer has a limited amount of data that can be stored, and thus data can be temporarily stored continuously. The temporary storage 10 may use the circular queue including five buffers to temporarily store battery data continuously.

[0042] The temporary storage 10 can temporarily store the battery data periodically at a specific time interval. According to one embodiment, the temporary storage 10 can update the battery data every second using a circular queue that includes five buffers.

[0043] The controller 212 may analyze the battery data based on a certain time interval. The controller 212 may analyze whether or not there is an abnormality in the battery based on the battery data stored in the temporary storage 10. Specifically, the controller 212 may analyze whether or not there is an abnormality in the battery based on the voltage, current, and temperature data of a plurality of batteries. Here, an abnormality may be defined as a deviation of a characteristic or parameter of the internal configuration of the system from a prescribed condition by more than an allowable deviation.

[0044] For example, the controller 212 can diagnose the battery as being in an abnormal state if the battery data stored in the temporary storage 10 from time (t-5) to time (t), including at least one of the battery voltage, current, temperature, and diagnostic information, deviates from the already stored conditions or pre-set conditions by more than an allowable deviation.

[0045] When the battery is diagnosed as being in an abnormal state based on the battery data stored in the temporary storage 10, the controller 212 may additionally acquire and store the stored battery data after a certain time has elapsed in the temporary storage 10. For example, when the battery is diagnosed as being in an abnormal state based on the battery data from time (t-5) to time (t) stored in the temporary storage 10, the controller 212 may additionally acquire battery data from time (t+1) to time (t+5) stored in the temporary storage 10 after 5 seconds have elapsed, and store the battery data generated for a total of 10 seconds.

[0046] For example, the controller 212 can store battery data for 5 seconds up to the time when the abnormality diagnosis occurs, and then store battery data after 5 seconds have elapsed, thereby storing a battery data history for 10 seconds before and after the time when the abnormality diagnosis occurs. Therefore, the controller 212 can check the transition of the battery data for 10 seconds before and after the time when the abnormality diagnosis occurs.

[0047] The controller 212 can determine the abnormality level of the battery based on the presence or absence of an abnormality in the battery. For example, the controller 212 can determine the presence or absence of an abnormality in the battery management unit 200 and determine the abnormality level of the abnormality that has occurred.

[0048] For example, the abnormality level may be determined based on the severity, exposure, and controllability of damage caused by malfunction of vehicle components through vehicle-level hazard analysis and risk assessment. For example, the abnormality level may be classified into four levels, such as Fault2, Fault1, Warning, and Alarm. The abnormality level may be defined as a standard in which Fault2 is the most dangerous level and Alarm is the least dangerous level. For example, if a short circuit occurs in a battery module control cable or battery module diagnostic cable of the BMS, causing an overvoltage or undervoltage in the battery cell to rise in temperature of the battery, which is expected to cause a risk of battery fire, the battery abnormality level may be Fault2.

[0049] The controller may classify and store battery data in the plurality of storages 20 based on the abnormality level of the battery. For example, the plurality of storages 20 may include a first storage 21, a second storage 22, a third storage 23, and a fourth storage 24. The first storage 21, the second storage 22, the third storage 23, and the fourth storage 24 may be physically or programmatically separated. For example, the first storage 21 may store battery data in which the abnormality level of the battery corresponds to Fault2. The second storage 22 may store battery data in which the abnormality level of the battery corresponds to Fault1. The third storage 23 may store battery data in which the abnormality level of the battery corresponds to Warning. The fourth storage 24 may store battery data in which the abnormality level of the battery corresponds to Alarm.

[0050] Here, each of the multiple storages 20 may include multiple storage areas. The controller 212 can store the battery data in any one of the multiple storage areas based on the priority order of the multiple storage areas of any one of the multiple storages 20. Specifically, the first storage 21 may include a first storage area (A1) and a second storage area (A2). The second storage 22 may include a third storage area (A3) and a fourth storage area (A4). The third storage 23 may include a fifth storage area (A5) and a sixth storage area (A6). The fourth storage 24 may include a seventh storage area (A7) and an eighth storage area (A8).

[0051] FIG. 3 is a diagram for specifically explaining the overall operation of a battery data management device according to an embodiment disclosed herein.

[0052] 3, the controller 212 may determine whether the battery is at an abnormal level in the order of increasing risk of the abnormal level. For example, the controller 212 may determine whether the battery is at an abnormal level in the order of Fault2 level, Fault1 level, Warning level, and Alarm level.

[0053] When the controller 212 determines the abnormality level of the battery, the controller 212 can classify and store the battery data in one of a plurality of storages corresponding to the abnormality level of the battery.

[0054] For example, when the battery abnormality level corresponds to Fault 2, the controller 212 can determine whether or not there is storage space in the first storage area (A1) of the first storage 21. When there is no storage space in the first storage area (A1) of the first storage 21, the controller 212 can store battery data in the second storage area (A2).

[0055] For example, when the battery abnormality level corresponds to Fault 1, the controller 212 can determine whether or not there is storage space in the third storage area (A3) of the second storage 22. When there is no storage space in the third storage area (A3) of the second storage 22, the controller 212 can store battery data in the fourth storage area (A4).

[0056] For example, when the battery abnormality level corresponds to Warning, the controller 212 can determine whether or not there is storage space in the fifth storage area (A5) of the third storage 23. When there is no storage space in the fifth storage area (A5) of the third storage 23, the controller 212 can store battery data in the sixth storage area (A6).

[0057] For example, when the battery abnormality level corresponds to Alarm, the controller 212 can determine whether or not there is storage space in the seventh storage area (A7) of the fourth storage 24. When there is no storage space in the seventh storage area (A7) of the fourth storage 24, the controller 212 can store battery data in the eighth storage area (A8).

[0058] Here, the first memory area (A1), the third memory area (A3), the fifth memory area (A5), and the seventh memory area (A7) can be defined as battery data storage spaces for checking the initial abnormality diagnosis occurrence history, and the second memory area (A2), the fourth memory area (A4), the sixth memory area (A6), and the eighth memory area (A8) can be defined as battery data storage spaces for checking the most recent abnormality diagnosis occurrence history.

[0059] FIG. 4 is a diagram for specifically explaining the overall operation of a battery data management device according to another embodiment disclosed herein.

[0060] 4, the controller 212 can assign count data to each abnormality level of the battery. When determining an abnormality level of the battery, the controller 212 can assign count data to the abnormality level. That is, when determining an abnormality level of the battery, the controller 212 can increase the count data for the abnormality level.

[0061] The controller 212 can store the battery data in a plurality of storage areas of one of the plurality of storages 20 based on the count data of the abnormal level that is increased when the abnormal level of the battery is determined.

[0062] For example, the controller 212 can store battery data in the first storage area (A1) when the battery corresponds to the abnormal level Fault2 and the count value of the Fault2 level is within 10. The controller 212 can store battery data in the second storage area (A2) when the battery corresponds to the abnormal level Fault2 and the count value of the Fault2 level is more than 10.

[0063] For example, when the battery corresponds to the abnormality level Fault1 and the count value of the Fault1 level is within 10, the controller 212 can store the battery data in the third storage area (A3). When the battery corresponds to the abnormality level Fault1 and the count value of the Fault1 level is greater than 10, the controller 212 can store the battery data in the fourth storage area (A4).

[0064] For example, when the battery reaches the abnormal level Warning and the count value of the Warning level is within 10, the controller 212 can store the battery data in the fifth memory area (A5). When the battery reaches the abnormal level Warning and the count value of the Warning level is greater than 10, the controller 212 can store the battery data in the sixth memory area (A6).

[0065] For example, when the battery reaches an abnormal level Alarm and the count value of the Alarm level is within 10, the controller 212 can store the battery data in the seventh memory area (A7). When the battery reaches an abnormal level Alarm and the count value of the Alarm level is greater than 10, the controller 212 can store the battery data in the eighth memory area (A8).

[0066] Here, the reference count value may be changed based on the size of the storage area, the size of the storage space, or the size of the memory 211.

[0067] As described above, according to an embodiment of the battery data management device 210 disclosed in this document, the battery data storage may be divided to efficiently manage the battery data in multiple storages.

[0068] The battery data management device 210 manages the battery data by classifying it according to the battery abnormality level, and separately manages battery data with a high level of importance, making it easy to trace the cause of the battery abnormality.

[0069] In addition, even if the storage area is divided according to abnormality level and abnormality diagnoses occur frequently, leaving no battery data storage area, the problem of battery data with an abnormality level that is not important occupying the storage area of ​​battery data corresponding to an abnormality level with a high degree of importance can be solved.

[0070] The battery data management device 210 has a structure that stores only battery data acquired for one second when a battery abnormality diagnosis occurs, and utilizes a circular queue data structure including multiple buffers to store and analyze battery data for several seconds before and after the occurrence of a battery abnormality diagnosis, thereby analyzing the trend of the battery data.

[0071] 5 is a flowchart illustrating an operation method of the battery data management device according to an embodiment disclosed in the present document. Hereinafter, the operation method of the battery data management device 210 will be described in detail with reference to FIGS.

[0072] The battery data management device 210 may be substantially the same as the battery data management device 210 described with reference to FIGS. 1 to 4, and therefore will be described briefly below to avoid duplication of description.

[0073] Referring to FIG. 5, an operating method of the battery data management device may include a step of storing battery data (S101), a step of determining whether or not there is a battery abnormality based on the battery data (S102), a step of determining a battery abnormality level based on the presence or absence of the battery abnormality (S103), and a step of dividing and storing the battery data into a plurality of storages based on the battery abnormality level (S104).

[0074] Steps S101 to S104 will be described in detail below.

[0075] In step S101, the temporary storage 10 of the memory 211 may include a circular queue capable of storing the battery data at a regular interval. In step S101, according to one embodiment, the circular queue may include five buffers. In step S101, the temporary storage 10 of the memory 211 may temporarily store the battery data using the circular queue including the five buffers.

[0076] In step S101, the temporary storage 10 of the memory 211 may temporarily store the battery data at a specific time interval. In step S101, according to one embodiment, the temporary storage 10 of the memory 211 may update the battery data every second using a circular queue including five buffers.

[0077] In step S102, the controller 212 may analyze the battery data based on a certain time interval. In step S102, the controller 212 may analyze whether or not there is an abnormality in the battery based on the battery data stored in the temporary storage 10 of the memory 211. In particular, in step S102, the controller 212 may analyze whether or not there is an abnormality in the battery based on the voltage, current, and temperature data of a plurality of batteries.

[0078] In step S102, for example, the controller 212 can diagnose the battery as being in an abnormal state if the battery data, including at least one of the battery voltage, current, temperature, and diagnostic information from time (t-5) to time (t) stored in the temporary storage 10, deviates from the already stored conditions or pre-set conditions by more than an allowable deviation.

[0079] In step S103, when the battery is diagnosed as being in an abnormal state based on the battery data stored in the temporary storage 10, the controller 212 may additionally acquire and store the battery data stored in the temporary storage 10 after a certain time has elapsed. For example, in step S103, when the battery is diagnosed as being in an abnormal state based on the battery data from time (t-5) to time (t) stored in the temporary storage 10, the controller 212 may additionally acquire battery data from time (t+1) to time (t+5) stored in the temporary storage 10 after 5 seconds have elapsed, and store the battery data generated for a total of 10 seconds.

[0080] In step S103, for example, the controller 212 stores battery data for 5 seconds before the occurrence of the abnormality diagnosis, and then stores battery data after 5 seconds have elapsed, thereby storing a battery data history for 10 seconds before and after the occurrence of the abnormality diagnosis. Thus, the controller 212 can check the transition of the battery data for 10 seconds before and after the occurrence of the abnormality diagnosis.

[0081] In step S103, when the battery is diagnosed as being in an abnormal state based on the battery data, the controller 212 may determine an abnormality level of the battery. For example, the controller 212 may determine whether an abnormality occurs in the battery management unit 200 and determine an abnormality level of the abnormality that occurs.

[0082] In step S103, the controller 212 may determine whether the battery is at an abnormal level in the order of increasing risk of the abnormal level. For example, the controller 212 may determine whether the battery is at an abnormal level in the order of whether the battery data is at a Fault2 level, whether the battery data is at a Fault1 level, whether the battery data is at a Warning level, and whether the battery data is at an Alarm level.

[0083] In step S103, the controller 212 can assign count data to each abnormality level of the battery. In step S103, the controller 212 can assign count data to the abnormality level when determining the abnormality level of the battery. In step S103, that is, when determining the abnormality level of the battery, the controller 212 can increase the count data of the abnormality level determination.

[0084] In step S104, the controller 212 may monitor abnormality detection information including the abnormality level of the battery, and classify and store the battery data corresponding to the abnormality level. Specifically, in step S104, the controller 212 may store the battery data in one of the plurality of storages 20 corresponding to the abnormality level of the battery.

[0085] In step S104, when the battery is diagnosed as being in an abnormal state, the controller 212 can acquire battery data stored in the multiple circular queues and battery data stored in the multiple circular queues after a certain period of time, and store the battery data in separate storages 20.

[0086] Here, each of the multiple storages 20 may include multiple storage areas. In step S104, the controller 212 may store the battery data in one of the multiple storage areas based on the priority order of the multiple storage areas of any one of the multiple storages 20. Specifically, the first storage 21 may include a first storage area (A1) and a second storage area (A2). The second storage 22 may include a third storage area (A3) and a fourth storage area (A4). The third storage 23 may include a fifth storage area (A5) and a sixth storage area (A6). The fourth storage 24 may include a seventh storage area (A7) and an eighth storage area (A8).

[0087] At step S104, for example, when the battery abnormality level corresponds to Fault 2, the controller 212 can determine whether or not there is storage space in the first storage area (A1) of the first storage 21. When there is no storage space in the first storage area (A1) of the first storage 21, the controller 212 can store the battery data in the second storage area (A2).

[0088] FIG. 5 is a block diagram illustrating a hardware configuration of a computing system for implementing an operating method of a battery data management device according to an embodiment disclosed herein.

[0089] Referring to FIG. 5, a computing system 400 according to one embodiment disclosed herein may include an MCU 410, a memory 420, an input / output I / F 430, and a communication I / F 440.

[0090] The MCU 410 may be a broker that executes various programs (e.g., a program for monitoring battery data) stored in the memory 420, processes various data, and performs the functions of the battery data management device 210 shown in FIG. 1 described above.

[0091] The memory 420 can store various programs related to the operation of the equipment control device 400. The memory 420 can also store operation data for the equipment control device 400.

[0092] A plurality of such memories 420 may be provided as necessary. The memories 420 may be volatile memories or non-volatile memories. The volatile memories 420 may be RAM, DRAM, SRAM, etc. The non-volatile memories 420 may be ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. The above-listed examples of the memories 420 are merely illustrative and are not limited to these examples.

[0093] The input / output I / F 430 can provide an interface that connects input devices (not shown) such as a keyboard, mouse, or touch panel, and output devices such as a display (not shown), to the MCU 410 to enable data transmission and reception.

[0094] The communication I / F 440 is configured to be capable of transmitting and receiving various data to and from a server, and may be any of various devices capable of supporting wired or wireless communication. For example, programs for resistance measurement and abnormality diagnosis, various data, and the like can be transmitted and received from a separately provided external server via the communication I / F 440.

[0095] The above description is merely an illustrative example of the technical ideas of the present disclosure, and various modifications and variations can be made by a person having ordinary knowledge in the technical field to which the present disclosure pertains without departing from the essential characteristics of the present invention.

[0096] Therefore, the embodiments disclosed in this disclosure are intended to explain, not to limit, the technical idea of ​​the disclosure, and such embodiments do not limit the scope of the technical idea of ​​the disclosure. The scope of protection of the disclosure should be interpreted according to the following claims, and all technical ideas within the scope equivalent thereto should be interpreted as being included in the scope of rights of the disclosure. [Explanation of symbols]

[0097] 10. Temporary Storage 20. Storage 21 First Storage 22 Second Storage 23 Third Storage 24 4th Storage 100 Battery Module 110 Battery Cell 120 Battery Cells 130 Battery Cells 140 Battery Cells 200 Battery Management Device 210 Battery data management device 211 Memory 212 Controller 300 Relay 400 Computing Systems 400 Facility control device 420 Memory 1000 Battery Pack A1 1st storage area A2 2nd storage area A3 3rd storage area A4 4th storage area A5 5th storage area A6 6th storage area A7 7th storage area A8 8th storage area

Claims

1. a controller that determines whether or not a battery is abnormal based on battery data, determines an abnormality level of the battery based on the abnormality level of the battery, and divides and stores the battery data into a plurality of storages based on the abnormality level of the battery; A battery data management device including: a memory including the plurality of storages and a temporary storage for temporarily storing the battery data.

2. The battery data management device according to claim 1 , wherein the controller stores the battery data in one of the plurality of storages corresponding to an abnormality level of the battery.

3. The battery data management device of claim 1, characterized in that the controller stores the battery data in one of the plurality of storage areas based on the priority of the plurality of storage areas of the one of the plurality of storage areas.

4. 2. The battery data management device of claim 1, wherein, when the battery is diagnosed as being in an abnormal state, the controller acquires the battery data stored in the temporary storage at the time when the battery is diagnosed as being in an abnormal state and the battery data stored in the temporary storage after a certain period of time, and stores the battery data in the plurality of storages in a divided manner.

5. The battery data management device according to claim 1 , wherein the controller determines whether the battery is at an abnormal level in descending order of risk of abnormality.

6. The battery data management device according to claim 1 , wherein the memory stores the battery data in a circular queue of the temporary storage at a regular interval.

7. The battery data management device according to claim 1 , wherein the battery data includes at least one of a voltage, a current, a temperature, and diagnostic information of the battery.

8. temporarily storing battery data; determining whether the battery is abnormal based on the battery data; determining an abnormality level of the battery based on whether or not there is an abnormality in the battery; and dividing and storing the battery data into a plurality of storages based on the abnormality level of the battery.

9. 9. The method of claim 8, wherein the step of determining an abnormality level of the battery based on the presence or absence of an abnormality of the battery comprises storing the battery data in one of the plurality of storages corresponding to the abnormality level of the battery.

10. 9. The method of claim 8, wherein the step of dividing and storing the battery data into a plurality of storages based on the abnormality level of the battery comprises storing the battery data in one of the plurality of storage areas based on a priority of the plurality of storage areas in one of the plurality of storage areas.

11. 9. The method of claim 8, wherein the step of temporarily storing the battery data includes, when the battery is diagnosed as being in an abnormal state, acquiring the battery data stored in the temporary storage at the time when the battery is diagnosed as being in an abnormal state and the battery data stored in the temporary storage after a certain period, and storing the battery data in the temporary storage separately in the plurality of storages.

12. 9. The method of claim 8, wherein the step of determining an abnormality level of the battery based on the presence or absence of an abnormality of the battery comprises determining whether the battery is at an abnormal level in order of increasing risk of the abnormality level.

13. 9. The method of claim 8, wherein the temporarily storing the battery data comprises storing the battery data in a circular queue of the temporary storage at a regular interval.

Images