Battery management device, BMS data storage system, and BMS data storage method

Abstract

A battery management device according to an embodiment of the present invention may include a processor; and a memory for storing at least one instruction executed through the processor, the at least one instruction including an instruction for detecting an event requiring emergency storage of BMS data; an instruction for detecting an event requiring emergency storage of the BMS data, thereby requesting emergency storage of the BMS data from a first controller in a device including the battery; and an instruction for receiving a response to the request from the first controller and transmitting the BMS data to the first controller.

Description

[Technical Field]

[0001] This application claims the benefit of the filing date of Korean Patent Application No. 10-2022-0130536, filed with the Korean Intellectual Property Office on October 12, 2022, and all of the contents disclosed in the documents of that Korean patent application are incorporated herein by reference.

[0002] The present invention relates to a battery management device, a BMS data storage system, and a BMS data storage method, and more particularly to a battery management device, a BMS data storage system, and a BMS data storage method that can safely back up BMS data in the event of an emergency such as a fire. [Background technology]

[0003] Secondary batteries, which can be recharged and reused after use, are manufactured into battery modules or battery packs consisting of a number of battery cells connected in series according to the output capacity required by the device, and are used as power sources for various devices. Such batteries are used in a variety of fields, including small, cutting-edge electronic devices such as smartphones, as well as electric bicycles, electric vehicles, and energy storage systems (ESS).

[0004] A battery module or a battery pack is a structure in which a number of battery cells are combined, and if some of the battery cells experience overvoltage, overcurrent, overheating, etc., this can cause problems in the safety and operating efficiency of the battery module or the battery pack, so a means for detecting these is essential. For this reason, a battery module or a battery pack is equipped with a BMS (Battery Management System) that measures the voltage value of each battery cell and monitors and controls the voltage state of the battery cells based on the measured value.

[0005] Although the BMS stores information related to battery usage records and diagnostic occurrences in a storage device within the BMS, there is a risk that the stored records may be lost in an emergency such as a fire inside the vehicle. To solve this problem, attempts have been made to store information in real time using cloud services, but implementing such a function requires separate, expensive equipment, and if the equipment fails, it is difficult to check the recorded information. Summary of the Invention [Problem to be solved by the invention]

[0006] SUMMARY OF THE INVENTION In order to solve the above problems, an object of the present invention is to provide a battery management device.

[0007] Another object of the present invention to solve the above problems is to provide a system for storing BMS data related to the state of a battery.

[0008] Another object of the present invention to solve the above problems is to provide a method for storing BMS data related to the state of a battery. [Means for solving the problem]

[0009] To achieve the above object, a battery management device according to an embodiment of the present invention may include a processor; and a memory that stores at least one instruction executed by the processor.

[0010] The at least one instruction may include an instruction to detect an event requiring emergency storage of BMS data; an instruction to request emergency storage of the BMS data from a first controller in a device including the battery by detecting an event requiring emergency storage of the BMS data; and an instruction to receive a response to the request from the first controller and transmit the BMS data to the first controller.

[0011] The event requiring urgent storage of the BMS data may include a case where the temperature of the battery detected by the battery management device is equal to or higher than a threshold value.

[0012] The emergency storage request for the BMS data and the transmission of the BMS data can be performed through CAN (Controller Area Network) communication.

[0013] The frame used in the CAN communication can include an identifier field that identifies the sender and receiver of the frame, and one or more data fields.

[0014] The one or more data fields may include information indicating whether the corresponding frame is a message requesting emergency storage or a message responding to storage availability.

[0015] Identifiers that identify the sender and receiver of the frame are assigned uniquely to each of the battery management device, the first controller, and one or more second controllers under the control of the first controller, and the assignment information for each identifier can be pre-shared and stored by the battery management device, the first controller, and the second controller.

[0016] The BMS data transmitted to the first controller may be transferred to and stored in one controller selected from the first controller or one or more second controllers interlocked with the first controller.

[0017] A BMS data storage system according to another embodiment of the present invention is a system for storing battery status-related BMS (Battery Management System) data, and may include: a first controller located in a device including the battery; and a battery management device that detects an event requiring emergency storage of BMS data, requests the first controller to emergency store the BMS data, receives a response to the request from the first controller, and transmits the BMS data to the first controller.

[0018] In response to an emergency storage request for the BMS data, the first controller determines whether the communication path with the battery management device is normal, confirms whether the first controller has secured storage space to store the BMS data, sends a response message to the battery management device, receives the BMS data from the battery management device, and stores it in a storage device within the first controller.

[0019] Meanwhile, the BMS data storage system may further include one or more second controllers under the control of the first controller.

[0020] In response to an emergency storage request for the BMS data, the first controller can identify the safest controller among the second controllers for storing the BMS data, receive the BMS data from the battery management device, and transmit the BMS data to the safest second controller.

[0021] The safest controller may be determined based on one or more of the availability of space to store the BMS data, the location from the battery pack, and the temperature of the corresponding controller.

[0022] The emergency storage request for the BMS data and the transmission of the BMS data can be performed through CAN (Controller Area Network) communication.

[0023] The frame used in the CAN communication can include an identifier field that identifies the sender and receiver of the frame, and one or more data fields.

[0024] The one or more data fields may include information indicating whether the corresponding frame is a message requesting emergency storage or a message responding to storage availability.

[0025] Identifiers that identify the sender and receiver of the frame are assigned uniquely to each of the battery management device, the first controller, and one or more second controllers under the control of the first controller, and the assignment information for each identifier can be pre-shared and stored by the battery management device, the first controller, and the second controller.

[0026] The first controller may be a VCU (Vehicle Control Unit) that is a top-level controller that centrally controls one or more ECUs (Electronic Control Units) in the automobile that communicate with the BMS.

[0027] A BMS data storage method according to another embodiment of the present invention is a method for storing battery status-related BMS (Battery Management System) data, and includes the steps of: a battery management device detecting an event requiring emergency storage of BMS data; the battery management device detecting the event requiring emergency storage of the BMS data, and thereby requesting emergency storage of the BMS data from a first controller in a device including the battery; and the battery management device receiving a response to the request from the first controller and transmitting the BMS data to the first controller.

[0028] Here, the event requiring emergency storage of the BMS data may include a case where the temperature of the battery detected by the battery management device is equal to or higher than a threshold. According to an embodiment of the present invention, the BMS data storage method may further include, in response to a request for emergency storage of the BMS data, determining whether a communication path between the first controller and the battery management device is normal; confirming whether the first controller has secured storage space for storing the BMS data; and, if the communication path is normal and the first controller has secured the storage space, transmitting a response message to the battery management device.

[0029] The BMS data storage method may also further include a step in which the first controller receives the BMS data from the battery management device and stores the BMS data in a storage device within the first controller.

[0030] According to another embodiment of the present invention, the BMS data storage method may further include a step in which, in response to an emergency storage request for the BMS data, the first controller identifies the safest controller for storing the BMS data among a plurality of second controllers under the control of the first controller; a step in which the first controller receives the BMS data from the battery management device; and a step in which the first controller transmits the BMS data to the safest second controller.

[0031] The safest controller may be determined based on one or more of the availability of space to store the BMS data, the location from the battery pack, and the temperature of the corresponding controller.

[0032] The emergency storage request for the BMS data and the transmission of the BMS data can be performed through CAN (Controller Area Network) communication.

[0033] The frame used in the CAN communication can include an identifier field that identifies the sender and receiver of the frame, and one or more data fields.

[0034] The one or more data fields may include information indicating whether the corresponding frame is a message requesting emergency storage or a message responding to storage availability.

[0035] Identifiers that identify the sender and receiver of the frame are uniquely assigned to the battery management device, the first controller, and one or more second controllers under the control of the first controller, and assignment information for each identifier can be pre-shared and stored by the battery management device, the first controller, and the second controller. [Effects of the Invention]

[0036] According to the above-described embodiment of the present invention, if a fire occurs in a vehicle, the BMS data can be backed up to another safe location before the BMS is completely destroyed by the fire.

[0037] Even if the battery pack is completely burned down, the cause of the fire and other defects can be analyzed through the BMS data backed up in another location. [Brief explanation of the drawings]

[0038] [Figure 1] 1 shows the structure of a battery system to which the present invention can be applied. [Figure 2] 1 is a diagram conceptually showing a communication system between a plurality of ECUs in an automobile according to an embodiment of the present invention; [Figure 3] 1 illustrates an operational flow between components in a BMS data storage method according to an embodiment of the present invention. [Figure 4] 1 illustrates the structure of a CAN communication frame used in a BMS data storage method according to an embodiment of the present invention. [Figure 5]10 illustrates an operational flow between components in a BMS data storage method according to another embodiment of the present invention. [Figure 6] 1 is a block diagram of a battery management device according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0039] Since the present invention can be modified in various ways and can have various embodiments, specific embodiments will be illustrated in the drawings and described in detail in the detailed description. However, it is understood that this is not intended to limit the present invention to the specific embodiments, but rather to include all modifications, equivalents, or alternatives within the spirit and technical scope of the present invention. Like reference numerals are used to refer to like elements throughout the drawings.

[0040] Terms such as "first," "second," "A," and "B" may be used to describe various components, but the components should not be limited by these terms. These terms are used only to distinguish one component from another. For example, a first component may be termed a "second component," and similarly, a second component may be termed a "first component," without departing from the scope of the present invention. The term "and / or" includes a combination of multiple associated listed items or any of multiple associated listed items.

[0041] When a component is referred to as being "coupled" or "connected" to another component, it is understood that the component may be directly coupled or connected to the other component, but that there may be other components in between. Conversely, when a component is referred to as being "directly coupled" or "directly connected" to another component, it is understood that there are no other components in between.

[0042] The terms used in this application are merely used to describe specific embodiments and are not intended to limit the present invention. The singular expressions include the plural expressions unless the context clearly indicates otherwise. It should be understood that in this application, the terms "comprise" or "have" are intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and do not preclude the presence or additional possibility of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0043] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which this invention pertains. Terms as defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted as having an ideal or overly formal meaning unless expressly defined in this application.

[0044] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0045] FIG. 1 shows the structure of a battery system to which the present invention can be applied.

[0046] In FIG. 1, a battery pack or a battery module may be configured to include a plurality of battery cells connected in series. The battery cells or modules are connected to a load through positive and negative terminals to perform charge / discharge operations. The most commonly used battery cells are lithium-ion (Li-Ion) battery cells. Such a battery module or battery pack may be provided with a Battery Management System (BMS) 100.

[0047] A battery management system (BMS) monitors the current, voltage, and temperature of each battery pack under its control, calculates the SOC (Status of Charge) based on the monitoring results, and controls charging and discharging. Here, SOC (State of Charge) is the current charged state of the battery expressed as a percentage [%], and SOH (State of Health) is the current deterioration state of the battery expressed as a percentage [%].

[0048] In this way, the BMS monitors the battery cells, reads the cell voltages, and transmits the voltages to other systems connected to the battery. The BMS also balances the charges of the battery cells evenly to extend the life of the battery system. Here, the battery system is used as a concept including multiple batteries and a battery management device (BMS).

[0049] To perform these operations, the BMS 100 may include various components such as fuses, current sensing elements, thermistors, switches, and balancers, but in most cases, it also includes a microcontroller unit (MCU) or a battery monitoring integrated chip (BMIC) for interlocking and controlling these components. Here, the BMIC may be an IC-type component located inside the BMS that measures information such as the voltage, temperature, and current of the battery cell / module.

[0050] The BMS also monitors the battery cells, reads the cell voltages, and transmits the cell voltages to other systems connected to the battery. To this end, the BMS may include a communication module for communicating with other systems within the device that includes the battery system. The communication module of the BMS may communicate with other systems within the device using a Controller Area Network (CAN). In this case, components, modules, or systems within the BMS are connected to each other via a CAN bus.

[0051] Meanwhile, the BMS stores battery usage record-related information and diagnostic occurrence-related items in its internal storage device (e.g., EEPROM). However, since the BMS is located very close to the battery, there is a high possibility that it will be completely burned down along with the battery in an emergency such as a serious fire inside the vehicle. In this case, the storage device (e.g., EEPROM IC type) in the BMS will also be damaged, making the previously recorded information unusable.

[0052] FIG. 2 is a conceptual diagram showing a communication system between a plurality of ECUs in an automobile, which is one embodiment to which the present invention is applied.

[0053] The vehicle according to an embodiment of the present invention may be, for example, an electric vehicle, a hybrid vehicle, or a plug-in hybrid vehicle, and includes a battery pack including a battery and a BMS according to an embodiment of the present invention. The vehicle includes a four-wheeled vehicle and a two-wheeled vehicle, and operates by receiving power from the battery pack.

[0054] To operate such a vehicle, control operations are required, such as motor drive control, regenerative braking control, air conditioning load control, electrical load power (12V) supply control, etc. Referring to Figure 2, there are many ECUs (Electronic Control Units) inside the vehicle for these control operations.

[0055] Meanwhile, the BMS 100 is one of the control devices in a vehicle and can be considered a type of ECU. In addition, in this specification, the term "ECU" may be used as a concept including the VCU (vehicle control unit) 210, which is the highest-level controller that manages all operations and controls in the vehicle. The term "ECU 220" may also refer to one or more ECUs in a vehicle (or various devices or systems that use a battery) under the control of the VCU 210.

[0056] An ECU (Electronic Control Unit) can contain internal storage devices such as RAM (Random Access Memory) and ROM (Read Only Memory). The RAM in the ECU temporarily stores various signals generated while the vehicle is in operation, but the stored data gradually disappears over time and will be lost all at once if electricity is cut off. In contrast, the ROM in the ECU records control data necessary for the vehicle to operate, and the data stored there cannot be arbitrarily erased or modified.

[0057] When an ECU is applied to an electric vehicle (hybrid), it is also called an EPCU (Electric Power Control Unit), which controls the motor and the overall movement of the vehicle. The EPCU can be said to perform functions similar to those of an ECU (Electronic Control Unit) and a TCU (Transmission Control Unit).

[0058] Meanwhile, multiple ECUs contained within a vehicle can communicate with each other via a CAN bus. CAN communication (Controller Area Network) is a standard communication protocol designed for microcontrollers and devices to communicate with each other within a vehicle without a host computer. CAN communication is a non-host bus message-based network protocol mainly used for communication between controllers, and is mainly used in vehicles.

[0059] The communication method used by the CAN protocol is a multi-master communication method, and the CAN controllers (ECU, VCU, and BMS in Figure 2) that share the communication bus all act as masters, allowing each controller to use the CAN bus whenever they want.The CAN protocol also uses a message-oriented transmission protocol and is electrically differentiated using two twisted pair wires, making it resistant to electrical noise.

[0060] Referring to Figure 2, all nodes on the CAN bus are connected via a two-wire bus. Each signal line, CAN_H (High) and CAN_L (Low), has a different voltage. CAN communication uses half-duplex technology, transmitting one bit of data at a time through two complementary signals on the CAN_H and CAN_L bus wires. The CAN bus has two logic states, dominant and recessive, depending on the signal state. The dominant state represents a logic "0" and the recessive state represents a logic "1." In the recessive state, both the CAN_H and CAN_L bus pins are biased to the same level (e.g., 2.5V). In the dominant state, the CAN_H bus pin is biased to a high voltage potential (e.g., ~3.5V), and the CAN_L bus pin is biased to a low voltage potential (e.g., ~1.5V). If the voltage difference between the two signal lines is lower than a certain threshold, it is determined to be recessive, and if it is higher than another threshold, it is determined to be dominant, allowing communication between CAN nodes.

[0061] FIG. 3 shows the operational flow between each component in a BMS data storage method according to one embodiment of the present invention.

[0062] FIG. 3 shows a first embodiment of how the cooperative control between the components for BMS data storage according to the present invention is performed.

[0063] Referring to FIG. 3, in this embodiment, components involved in the BMS data storage method may be the BMS 100 and VCU 210 in the automobile. This embodiment is presented on the premise that the VCU is a safer ECU than the BMS, which is located closest to the battery and in a dangerous location in an emergency situation such as a fire. As shown in FIG. 2 above, communication between the BMS and VCU is performed using the CAN protocol. Therefore, message transmission between the BMS and VCU shown in FIG. 3 is performed using the CAN protocol.

[0064] The battery management system (BMS) 100 detects an event that requires urgent storage of BMS data (S310). Here, the event that requires urgent storage of BMS data includes a case where the battery temperature detected by the battery management system is equal to or higher than a threshold. The event that requires urgent storage of BMS data also includes all situations where an abnormality occurs in the storage device (or recording device) that stores the stored BMS data, and there is a risk of the corresponding record being lost.

[0065] The battery management device 100 detects an event that requires emergency storage of the BMS data and requests a first controller in the vehicle to urgently store the BMS data (S320). At this time, the first controller may be the VCU 210, which is a top-level controller that centrally controls a plurality of ECUs that communicate with the BMS.

[0066] The first controller that has received the data emergency storage request from the BMS checks whether it can receive and store the emergency storage data (S321). At this time, the first controller checks whether the CAN line, which is the communication path with the BMS, is normal, whether there is enough space to store the data that needs to be urgently stored, and so on, to determine whether it can store the emergency storage data.

[0067] If the first controller 210 determines that it has the capability to store the data requiring emergency storage, it transmits a response to the request from the BMS to the battery management unit 100 (S330). Upon receiving the response completion message, the battery management unit transmits the data requiring emergency storage to the first controller (S340).

[0068] The first controller receives and stores data that requires urgent storage. The number of data transmissions may be one or more. The number of data transmissions may be determined based on the amount of data that requires urgent storage and the amount of data that can be transmitted in one CAN frame. If multiple data transmissions are performed, the first controller transmits a reply message to the BMS for each data transmission (S350). When data storage is complete, the first controller 210 transmits a storage completion and end message to the battery management unit 100 (S350). Upon receiving the storage completion message, the battery management unit 100 ends the BMS data backup transmission procedure (S360).

[0069] FIG. 4 shows the structure of a CAN communication frame used in the BMS data storage method according to an embodiment of the present invention.

[0070] The CAN communication frame 40 shown in Fig. 4 may be a message frame exchanged between the BMS and the VCU. The CAN communication frame 40 shown in Fig. 4 may also be a message exchanged between the BMS, the VCU, and multiple ECUs. The CAN communication frame 40 according to the embodiment of the present invention may include an ID field 41 and data fields (Data 1 to Data 8) 42.

[0071] According to one embodiment of the present invention, if frame ID 41 is "Ox100", it indicates a message frame transmitted by the BMS to the VCU, and if frame ID 41 is "Ox101", it indicates a message frame transmitted by the VCU to the BMS.

[0072] In addition, the "DATA1" field of the data field can indicate whether the corresponding message frame is a message requesting emergency storage (e.g., "1") or a message responding to storage availability (e.g., "2"). The following "DATA2" field can indicate a transmission (Tx) sequence (0 to 255), and the "DATA3" to "DATA8" fields can indicate the payload data to be transmitted. In this case, the transmission period of the CAN communication frame can be 10 ms.

[0073] FIG. 5 shows the operational flow between components in a BMS data storage method according to another embodiment of the present invention.

[0074] FIG. 5 shows a second embodiment of how the cooperative control between the components for BMS data storage according to the present invention is performed.

[0075] 5, in this embodiment, the components involved in the BMS data storage method may be the BMS 100, the VCU 210, and one or more ECUs 220 in the automobile. Communication between the BMS, the VCU, and the ECUs is performed using the CAN protocol. Therefore, message transmission between the BMS, the VCU, and the ECUs is performed via the CAN protocol.

[0076] According to the embodiment shown in Fig. 5, the battery management system (BMS) 100 detects an event requiring urgent storage of BMS data (S510). Here, the event requiring urgent storage of BMS data includes a case where the temperature of the battery detected by the battery management system is equal to or higher than a threshold. The event requiring urgent storage of BMS data also includes all situations where an abnormality occurs in the storage device (or recording device) that stores the stored BMS data, and there is a risk of the corresponding record being lost.

[0077] The battery management device detects an event that requires emergency storage of the BMS data and requests a first controller in the vehicle to urgently store the BMS data (S520). At this time, the first controller may be a VCU, which is a top-level controller that centrally controls a plurality of ECUs that communicate with the BMS.

[0078] The first controller, upon receiving a data emergency storage request from the BMS, transmits the request to one or more second controllers under its control, requesting them to confirm whether backup is possible (S530). The one or more second controllers, upon receiving the backup availability confirmation request message from the first controller, confirm whether they can receive and store the emergency storage data (S531). At this time, the second controller determines whether it can store the emergency storage data by checking whether the CAN line, which is the communication path with the VCU, is normal and whether there is sufficient space to store the data that requires emergency storage. Here, the second controller may be one of all ECUs in the vehicle excluding the VCU, and communicates with the VCU via the CAN line.

[0079] That is, in the second embodiment, the first controller 210 acts as a simple gateway that transfers the BMS data received from the BMS 100 to the second controller 220 .

[0080] If the second controller determines that it has the capability to store data requiring emergency storage, it transmits a response to the backup possibility confirmation request to the first controller (S540). The first controller, having received a response completion message from one or more second controllers, determines a subject to perform data backup based on the received response completion message (S550). Here, the first controller can select the safest controller for storing BMS data from the plurality of second controllers that have responded that data storage is possible, and determine the corresponding controller as the backup subject.

[0081] In this case, the safest controller for storing BMS data may be selected as the ECU located farthest from the battery pack (including the battery and battery management device) or the ECU with the lowest temperature, or may be selected as the most suitable ECU considering both of these conditions. That is, the safest controller for storing BMS data may be determined based on one or more of whether space for storing BMS data is available, the position from the battery pack, and the temperature of the corresponding controller.

[0082] The first controller 210, having determined the backup subject, transmits a response completion message to the BMS 100 (S560). The first controller then receives BMS data from the BMS and transmits it to the ECU determined as the backup subject (S570, S571). The backup subject ECU 220 receives and stores the data requiring urgent storage. The number of data transmissions may be one or more, and the number of transmissions may be determined based on the amount of data requiring urgent storage and the amount of data that can be transmitted in one CAN frame. When multiple data transmissions are performed, the backup subject ECU transmits a response message to the BMS via the first controller after each transmission (S580, S581). Once data storage is complete, the backup subject ECU 220 transmits a storage completion and end message to the battery management unit 100 via the first controller (S580, S581). Upon receiving the storage completion message, the BMS ends the BMS data transmission procedure (S590).

[0083] Meanwhile, the CAN communication frame 40 exchanged between the BMS and VCU shown in Fig. 4 can also be applied to the embodiment shown in Fig. 5. In this case, the CAN communication frame 40 may be a message exchanged between the BMS, the VCU, and a plurality of ECUs. The CAN communication frame 40 according to the embodiment of the present invention can be configured to include an ID field 41 and data fields (data 1 to data 8 fields) 42.

[0084] According to this embodiment, a frame ID of "0x100" indicates a message frame transmitted from the BMS to the VCU, and a frame ID of "0x101" indicates a message frame transmitted from the VCU to the BMS. Furthermore, a frame ID of "0x102" or higher indicates a frame assigned to a different ECU and transmitted by the corresponding ECU. In this case, an ID for each ECU may be predetermined and pre-shared and stored (e.g., stored in the ROM of each device) among all nodes (i.e., the VCU, the BMS, and one or more ECUs) on the CAN bus.

[0085] In addition, the 'DATA1' field of the data field can indicate whether the corresponding message frame is a message requesting emergency storage (e.g., '1') or a message responding to storage availability (e.g., '2'). The following 'DATA2' field can indicate a transmission (Tx) sequence (0 to 255), and the 'DATA3' to 'DATA8' fields can indicate payload data to be transmitted.

[0086] Meanwhile, a BMS data storage system that executes the BMS data storage method shown in Figures 3 and 5 may include a first controller located in a device including a battery; and a battery management device that detects an event requiring emergency storage of BMS data, requests the first controller to emergency store the BMS data, receives a response to the request from the first controller, and transmits the BMS data to the first controller.

[0087] In response to the emergency storage request for the BMS data, the first controller determines whether the communication path with the battery management device is normal, confirms whether the first controller has secured storage space to store the BMS data, sends a response message to the battery management device, receives the BMS data from the battery management device, and stores it in a storage device within the first controller.

[0088] Meanwhile, the BMS data storage system may further include one or more second controllers under the control of the first controller.

[0089] In response to an emergency storage request for the BMS data, the first controller can identify which of the second controllers is the safest controller for storing the BMS data, receive the BMS data from the battery management device, and transmit the BMS data to the safest second controller.

[0090] The safest controller may be determined based on one or more of the availability of space to store the BMS data, the location from the battery pack, and the temperature of the corresponding controller.

[0091] The emergency storage request for the BMS data and the transmission of the BMS data can be performed through CAN (Controller Area Network) communication.

[0092] The frame used in the CAN communication can include an identifier field that identifies the sender and receiver of the frame, and one or more data fields.

[0093] The one or more data fields may include information indicating whether the corresponding frame is a message requesting emergency storage or a message responding to storage availability.

[0094] Identifiers that identify the sender and receiver of the frame are assigned uniquely to each of the battery management device, the first controller, and one or more second controllers under the control of the first controller, and the assignment information for each identifier can be pre-shared and stored by the battery management device, the first controller, and the second controller.

[0095] The first controller may be a VCU (Vehicle Control Unit) that is a top-level controller that centrally controls one or more ECUs (Electronic Control Units) in the automobile that communicate with the BMS.

[0096] FIG. 6 is a block diagram of a battery management device according to an embodiment of the present invention.

[0097] 6, a battery management device 100 according to an embodiment of the present invention may include a processor 110 and a memory 120 that stores at least one instruction executed by the processor. Here, the processor may be, for example, a microcontroller unit (MCU) or other types of controller.

[0098] The at least one instruction may include an instruction to detect an event requiring emergency storage of BMS data; an instruction to request emergency storage of the BMS data from a first controller in a device including the battery by detecting an event requiring emergency storage of the BMS data; and an instruction to receive a response to the request from the first controller and transmit the BMS data to the first controller.

[0099] The event requiring urgent storage of the BMS data may include a case where the temperature of the battery detected by the battery management device is equal to or higher than a threshold value.

[0100] The emergency storage request for the BMS data and the transmission of the BMS data can be performed through CAN (Controller Area Network) communication.

[0101] The frame used in the CAN communication can include an identifier field that identifies the sender and receiver of the frame, and one or more data fields.

[0102] The one or more data fields may include information indicating whether the corresponding frame is a message requesting emergency storage or a message responding to storage availability.

[0103] Identifiers that identify the sender and receiver of the frame are uniquely assigned to each of the battery management device, the first controller, and one or more second controllers under the control of the first controller, and the assignment information for each identifier can be pre-shared and stored by the battery management device, the first controller, and the second controller.

[0104] The BMS data transmitted to the first controller may be transferred to and stored in one controller selected from the first controller or one or more second controllers interlocked with the first controller.

[0105] Meanwhile, the battery management device 100 according to the present invention may further include a transceiver 130, an input interface 140, an output interface 150, a storage unit 160, etc. The components included in the battery management device 100 are connected to each other by a bus 570 to communicate with each other.

[0106] Furthermore, the memory 120 (or storage unit) may be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory may be composed of at least one of a read-only memory (ROM) and a random access memory (RAM), and may include an EEPROM (Electrically Erasable Programmable Read-only Memory). The memory 120 according to an embodiment of the present invention may store information related to battery usage records and diagnostic occurrence-related items.

[0107] The operations of the methods according to the embodiments of the present invention can be embodied as a computer-readable program or code on a computer-readable recording medium. The computer-readable recording medium includes all kinds of storage devices in which data that can be read by a computer system is stored. In addition, the computer-readable recording medium can be distributed among computer systems connected via a network, so that the computer-readable program or code can be stored and executed in a distributed manner.

[0108] Some aspects of the invention have been described in the context of an apparatus, but they may also be described in terms of a corresponding method, where a block or apparatus corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method may be described in terms of a corresponding block or item or feature of a corresponding apparatus. Some or all of the method steps may be performed by (or using) a hardware apparatus, such as a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, one or more of the most important method steps may be performed by such an apparatus.

[0109] Although the present invention has been described above with reference to preferred embodiments, those skilled in the art will understand that various modifications and variations of the present invention can be made without departing from the spirit and scope of the present invention as set forth in the following claims. [Explanation of symbols]

[0110] 100:BMS 210:VCU (Vehicle Control Unit) 220:ECU(Electronic Control Unit)

Claims

1. A battery management device for managing battery state-related BMS data, a processor; and a memory for storing at least one instruction to be executed by said processor; The at least one instruction: instructions to sense events requiring urgent storage of BMS data; instructions for causing a first controller in a device including the battery to request emergency storage of the BMS data by detecting an event requiring emergency storage of the BMS data; and a battery management device including instructions for receiving a response to the request from the first controller and transmitting the BMS data to the first controller;

2. The event requiring emergency storage of the BMS data is: The battery management device according to claim 1 , including a case where the temperature of the battery detected by the battery management device is equal to or higher than a threshold value.

3. The battery management device according to claim 1 , wherein the emergency storage request for the BMS data and the transmission of the BMS data are performed through CAN communication.

4. The frame used in the CAN communication is The battery management device according to claim 3 , further comprising an identifier field for identifying a sender and a receiver of the frame, and one or more data fields.

5. The one or more data fields are:

5. The battery management device according to claim 4, further comprising information indicating whether the frame is a message requesting emergency storage or a message responding as to whether storage is possible.

6. an identifier for identifying a transmitter and a receiver of the frame is uniquely assigned to each of the battery management device, the first controller, and one or more second controllers under the control of the first controller; The battery management device according to claim 4 , wherein the identifier-specific assignment information is shared and stored in advance by the battery management device, the first controller, and the second controller.

7. The BMS data transmitted to the first controller: The battery management device according to claim 1 , wherein the battery management device is transmitted to and stored in one controller selected from the first controller or one or more second controllers linked to the first controller.

8. 1. A system for storing battery status related BMS data, comprising: a first controller located within the device containing the battery; and A BMS data storage system including a battery management device that requests emergency storage of the BMS data from the first controller by detecting an event requiring emergency storage of the BMS data, receives a response to the request from the first controller, and transmits the BMS data to the first controller.

9. The first controller In response to an emergency storage request for the BMS data, 9. The BMS data storage system of claim 8, further comprising: determining whether a communication path with the battery management device is normal; confirming whether the first controller has secured storage space for storing the BMS data; transmitting a response message to the battery management device; receiving the BMS data from the battery management device; and storing the BMS data in a storage device within the first controller.

10. 9. The BMS data storage system of claim 8, further comprising one or more second controllers under the control of the first controller.

11. The first controller In response to an emergency storage request for the BMS data, The BMS data storage system of claim 10, further comprising: determining which of the second controllers is the safest controller for storing the BMS data; receiving the BMS data from the battery management device; and transmitting the BMS data to the safest second controller.

12. The most secure controller is The BMS data storage system according to claim 11 , wherein the determination is based on at least one of whether space for storing the BMS data is available, a position from a battery pack, and a temperature of the corresponding controller.

13. The BMS data storage system according to claim 10 , wherein the emergency storage request for the BMS data and the transmission of the BMS data are performed through CAN communication.

14. The frame used in the CAN communication is 14. The BMS data storage system of claim 13, including an identifier field that identifies a sending entity and a receiving entity of the frame, and one or more data fields.

15. The one or more data fields are:

15. The BMS data storage system according to claim 14, further comprising information indicating whether the frame is a message requesting emergency storage or a message responding to whether storage is possible.

16. an identifier for identifying a transmitter and a receiver of the frame is uniquely assigned to each of the battery management device, the first controller, and the second controller; The BMS data storage system according to claim 14 , wherein the identifier-specific assignment information is pre-shared and stored by the battery management device, the first controller, and the second controller.

17. 9. The BMS data storage system according to claim 8, wherein the first controller is a VCU, which is a top-level controller that centrally controls one or more ECUs in a vehicle that communicate with the BMS.

18. 1. A method for storing battery status related BMS data, comprising: The battery management device detects an event that requires urgent storage of BMS data; The battery management device detects an event that requires emergency storage of the BMS data, and requests a first controller in the device including the battery to emergency store the BMS data; and A BMS data storage method comprising the steps of: the battery management device receiving a response to the request from the first controller; and transmitting the BMS data to the first controller.

19. The event requiring emergency storage of the BMS data is: The BMS data storage method according to claim 18, including a case where the temperature of the battery detected by the battery management device is equal to or higher than a threshold value.

20. In response to an emergency storage request for the BMS data, a step of determining whether a communication path between the first controller and the battery management device is normal; Verifying whether the first controller has sufficient storage space to store the BMS data; and 20. The BMS data storage method of claim 18, further comprising the step of: when the communication path is normal and the first controller has reserved the storage space, the first controller sending a response message to the battery management device.

21. 20. The BMS data storage method according to claim 19, further comprising the step of the first controller receiving the BMS data from the battery management device and storing the BMS data in a storage device within the first controller.

22. In response to an emergency storage request for the BMS data, a step of the first controller identifying a safest controller for storing the BMS data among a plurality of second controllers under the control of the first controller; The first controller receives the BMS data from the battery management unit; and 20. The BMS data storage method of claim 18, further comprising the step of the first controller communicating the BMS data to the most secure second controller.

23. The most secure controller is The BMS data storage method according to claim 22, wherein the determination is based on one or more of whether space for storing the BMS data is available, a position from a battery pack, and a temperature of the corresponding controller.

24. The BMS data storage method according to claim 18, wherein the emergency storage request for the BMS data and the transmission of the BMS data are performed through CAN communication.

25. The frame used in the CAN communication is 25. The method of claim 24, further comprising an identifier field identifying a sending entity and a receiving entity of the frame and one or more data fields.

26. The BMS data storage method according to claim 25, wherein the one or more data fields include information indicating whether the frame is a message requesting emergency storage or a message responding to whether storage is possible.

27. an identifier for identifying a transmitter and a receiver of the frame is uniquely assigned to each of the battery management device, the first controller, and the second controller; The BMS data storage method according to claim 25, wherein the identifier-specific assignment information is shared and stored in advance by the battery management device, the first controller, and the second controller.

Images