Battery management device, BMS data storage system, and BMS data storage method
Emergency data backup in the battery management system is achieved through CAN communication, which solves the problem of BMS data storage equipment being damaged in a fire and ensures the safe storage and analysis of data.
Patent Information
- Application Number
- CN202380031729.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-10-12
- Filing Date
- 2023-09-21
- Publication Date
- 2024-11-15
AI Technical Summary
In emergencies such as fires, the data storage devices within the battery management system (BMS) are easily damaged, leading to the loss of recorded information, and existing technologies make it difficult to achieve secure backup.
Through Controller Area Network (CAN) communication, the battery management device detects an emergency and requests the vehicle control unit (VCU) to back up data, selects the safest storage location, and transmits BMS data to ensure the safe storage of data in the event of a fire.
Even if a fire occurs in a vehicle, the BMS data can be safely backed up to another location to avoid data loss and facilitate subsequent analysis of the cause of the fire.
Smart Images

Figure CN118973858A_ABST
Abstract
Description
Technical Field
[0001] This application claims priority to and the benefit of Korean Patent Application No. 10-2022-0130536 filed in the Korean Intellectual Property Office on October 12, 2022, the entire contents of which are incorporated herein by reference.
[0002] The present invention relates to a battery management device, a battery management system (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 an emergency such as a fire. Background Art
[0003] Secondary batteries that can be recharged and reused are manufactured as battery modules or packs by connecting multiple battery cells in series based on the required output capacity, thereby serving as power sources for various applications. These batteries are used in small high-tech electronic devices such as smartphones and in various fields including electric bicycles, electric vehicles, and energy storage systems (ESS).
[0004] A battery module or pack including a plurality of battery cells faces safety and operating efficiency issues when some cells encounter overvoltage, overcurrent or overheating, thus requiring detection means. Therefore, the battery module or battery pack is equipped with a battery management system (BMS) that measures the voltage value of each battery cell and monitors and controls the voltage state of the battery cell based on the measured value.
[0005] The battery management system stores information related to battery usage records and items related to the occurrence of diagnostics in a storage device within the battery management system, however, in the event of an emergency such as a fire in a vehicle, the stored records may be lost. To address this issue, attempts are being made to use cloud services to save information in real time, however, separate expensive equipment is required to implement this function, and in the event of a device failure, the recorded information cannot be ensured. Summary of the invention
[0006] Technical issues
[0007] In order to solve one or more problems in the prior art, an embodiment of the present disclosure provides a battery management device.
[0008] To solve one or more problems of the prior art, embodiments of the present disclosure also provide a system for storing battery management system (BMS) data related to a state of a battery.
[0009] To solve one or more problems of the prior art, embodiments of the present disclosure also provide a method for storing battery management system (BMS) data related to a state of a battery.
[0010] Technical Solution
[0011] To achieve the purpose of the present disclosure, a battery management device for managing battery management system (BMS) data related to a state of a battery may include at least one processor and a memory configured to store at least one instruction executed by the at least one processor.
[0012] The at least one instruction may include: an instruction to detect at least one event requiring emergency storage of BMS data; an instruction to request emergency storage of BMS data to a first controller in a device including a battery when an event requiring emergency storage of BMS data is detected; and an instruction to receive a response to the request for emergency storage of BMS data from the first controller and transmit the BMS data to the first controller.
[0013] The at least one event requiring urgent storage of the BMS data may include an event in which a temperature of the battery detected by the battery management device is equal to or greater than a threshold value.
[0014] The request for emergency storage of BMS data and the transmission of BMS data may be performed via controller area network (CAN) communication.
[0015] At least one frame used for CAN communication may include a field specifying identifiers of a sender and a receiver of the frame and one or more data fields.
[0016] One or more data fields may include information indicating whether the frame is a message requesting emergency storage or a message responding whether emergency storage is possible.
[0017] Identifiers of the sender and receiver of a designated frame can be uniquely assigned to each of: a battery management device, a first controller, and one or more second controllers under the control of the first controller, and the assignment information of each identifier can be pre-shared and pre-stored by the battery management device, the first controller, and one or more second controllers.
[0018] The BMS data transmitted to the first controller is transmitted to and stored in the first controller or a selected one of the one or more second controllers interoperating with the first controller.
[0019] According to another embodiment of the present disclosure, a system for storing battery management system (BMS) data related to the status of a battery may include: a first controller, which is located in a device containing a battery; and a battery management device, which is configured to: request the first controller in the device containing the battery to urgently store the BMS data when an event requiring urgent storage of the BMS data is detected, receive a response to the request for urgent storage of the BMS data from the first controller, and transmit the BMS data to the first controller.
[0020] The first controller can be configured to: determine whether the communication path between the battery management device and the first controller is normal in response to a request for emergency storage of BMS data; check whether the first controller ensures storage space to store BMS data and sends a response message to the battery management device; and receive BMS data from the battery management device and store the BMS data in a storage device within the first controller.
[0021] Meanwhile, the BMS data storage system may further include one or more second controllers under the control of the first controller.
[0022] The first controller may also be configured to: in response to a request for emergency storage of the BMS data, determine which of the second controllers is safest to store the BMS data; receive the BMS data from the battery management device; and transmit the BMS data to the safest second controller.
[0023] The safest second controller may be determined based on one or more of availability of space to store BMS data, location from the battery, and temperature of the corresponding controller.
[0024] The request for emergency storage of BMS data and the transmission of BMS data may be performed via controller area network (CAN) communication.
[0025] At least one frame used for CAN communication may include a field specifying identifiers of a sender and a receiver of the frame and one or more data fields.
[0026] One or more data fields may include information indicating whether the frame is a message requesting emergency storage or a message responding whether emergency storage is possible.
[0027] Identifiers of the sender and receiver of a designated frame can be uniquely assigned to each of: a battery management device, a first controller, and one or more second controllers under the control of the first controller, and the assignment information of each identifier can be pre-shared and pre-stored by the battery management device, the first controller, and one or more second controllers.
[0028] The first controller may be a vehicle control unit (VCU), which is a top-level controller that centrally controls one or more electronic control units (ECUs) that communicate with the battery management device.
[0029] According to another embodiment of the present disclosure, a method for storing battery management system (BMS) data related to the state of a battery may include: detecting, by a battery management device, at least one event requiring emergency storage of BMS data; upon detecting the event requiring emergency storage of BMS data, requesting, by the battery management device, a first controller in a device including a battery to urgently store the BMS data; and receiving, by the battery management device, a response to the request for emergency storage of the BMS data from the first controller and transmitting the BMS data to the first controller.
[0030] At least one event requiring emergency storage of BMS data may include an event in which the temperature of the battery detected by the battery management device is equal to or greater than a threshold. According to one embodiment of the present invention, the method may also include: in response to a request for emergency storage of BMS data, determining by the first controller whether a communication path between the battery management device and the first controller is normal; checking whether the first controller ensures storage space to store BMS data; and sending a response message by the first controller to the battery management device if the communication path between the battery management device and the first controller is normal and the first controller has storage space to store BMS data.
[0031] The method may further include: receiving, by the first controller, BMS data from the battery management device; and storing, by the first controller, the BMS data in a storage device within the first controller.
[0032] According to another embodiment of the present invention, the method may further include: in response to a request for emergency storage of BMS data, determining by the first controller which of the second controllers stores the BMS data most safely; receiving by the first controller the BMS data from the battery management device; and transmitting by the first controller the BMS data to the safest second controller.
[0033] The safest second controller is determined based on one or more of availability of space to store BMS data, location from the battery, and temperature of the corresponding controller.
[0034] The request for emergency storage of BMS data and the transmission of BMS data may be performed via controller area network (CAN) communication.
[0035] At least one frame used for CAN communication may include a field specifying identifiers of a sender and a receiver of the frame and one or more data fields.
[0036] One or more data fields may include information indicating whether the frame is a message requesting emergency storage or a message responding whether emergency storage is possible.
[0037] Identifiers of the sender and receiver of a designated frame can be uniquely assigned to each of: a battery management device, a first controller, and one or more second controllers under the control of the first controller, and the assignment information of each identifier can be pre-shared and pre-stored by the battery management device, the first controller, and one or more second controllers.
[0038] Beneficial effects
[0039] According to the embodiments of the present invention as described above, even if a fire occurs in a vehicle, the BMS data can be backed up to another safe location before the battery management device is completely destroyed by the fire.
[0040] In addition, even if the battery pack burns out, the causes of the fire and other defects can be analyzed through the BMS data backed up in another safe location. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] Figure 1 The structure of a battery system to which the present invention can be applied is shown.
[0042] Figure 2 is a diagram conceptually showing a communication method between a plurality of ECUs in an automobile, which is one of the embodiments to which the present invention is applied.
[0043] Figure 3 The flowchart of operations between components in the BMS data storage method according to an embodiment of the present invention is shown.
[0044] Figure 4 The structure of a CAN communication frame used in the BMS data storage method according to an embodiment of the present invention is shown.
[0045] Figure 5 A flowchart of operations between components in a BMS data storage method according to another embodiment of the present invention is shown.
[0046] Figure 6 is a block diagram of a battery management device according to an embodiment of the present invention.
[0047] 100: BMS 210: VCU (Vehicle Control Unit)
[0048] 220: ECU (Electronic Control Unit) DETAILED DESCRIPTION
[0049] The present invention can be modified in various forms and have various embodiments, and its specific embodiments are shown in the accompanying drawings by way of example and will be described in detail below. However, it should be understood that it is not intended to limit the present invention to specific embodiments, on the contrary, the present invention will cover all modifications, equivalents and substitutions that fall within the spirit and technical scope of the present invention. Throughout the description of the drawings, the same reference numerals refer to the same elements.
[0050] It will be understood that although various elements may be described herein using terms such as first, second, A, B, etc., these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the present invention. As used herein, the term "and / or" includes any one of a combination of a plurality of associated listed items or a plurality of associated listed items.
[0051] It will be understood that when an element is referred to as being "coupled" or "connected" to another element, it can be directly coupled or connected to the other element, or intervening elements may be present. Conversely, when an element is referred to as being "directly coupled" or "directly connected" to another element, there are no intervening elements.
[0052] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the present invention. As used herein, unless the context clearly indicates otherwise, the singular forms "one", "an" and "the" are also intended to include plural forms. It will be further understood that the terms "include", "comprise", "cover", "contain" and / or "have" specify the existence of stated features, integers, steps, operations, constituent elements, parts and / or combinations thereof when used herein, but do not exclude the existence or addition of one or more other features, integers, steps, operations, constituent elements, parts and / or combinations thereof.
[0053] Unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by those skilled in the art to which the present invention belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.
[0054] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.
[0055] Figure 1 The structure of a battery system to which the present invention can be applied is shown.
[0056] Figure 1A battery pack or battery module in a battery pack may include a plurality of battery cells connected in series. The battery pack or battery module may be connected to a load through positive and negative terminals and perform a charge / discharge operation. The most commonly used battery cell is a lithium-ion (Li-Ion) battery cell. A battery management system (BMS) may be installed for each of the battery pack or battery module.
[0057] The battery management system (BMS) may monitor the current, voltage, and temperature of each battery pack for management, calculate the state of charge (SOC) based on the monitoring results, and control charging and discharging. Here, SOC refers to the current state of charge of the battery, expressed in percentage points [%). Meanwhile, the state of health (SOH) may be an indicator of the current state of the degree of battery aging, expressed in percentage points [%).
[0058] Therefore, the BMS can monitor the battery cells, read the cell voltage, and transmit the cell voltage to other systems connected to the battery. In addition, the BMS can evenly balance the charging of the battery cells to extend the life of the battery system. Here, the battery system is used as a concept including a plurality of batteries and a battery management system (BMS).
[0059] To perform such operations, the BMS may include various components such as fuses, current sensing elements, thermistors, switches, and balancers, and in most cases also includes an MCU (microcontroller unit) or BMIC (battery monitoring integrated chip) to interface with and control these components. Here, the BMIC may be located inside the BMS and may be an IC-type component that measures information such as voltage, temperature, and current of a battery cell / group.
[0060] In addition, the battery management system can monitor the battery cells, read the cell voltages, and transmit them to other systems connected to the battery. To this end, the BMS may include a communication module for communicating with other systems in the device including the battery system. The communication module of the BMS may communicate with other systems using a controller area network (CAN). Here, the components, modules, or systems in the BMS may be connected to each other via a CAN bus.
[0061] Meanwhile, the battery management system (BMS) stores information related to battery usage records and items related to diagnostic occurrences in a storage device (e.g., EEPROM) within the BMS. However, the BMS, which is located very close to the battery, is likely to burn out along with the battery in an emergency such as a serious fire in a vehicle. Here, a problem arises that the storage device (e.g., in the form of an EEPROM IC) within the BMS may also be damaged, rendering the recorded information unusable.
[0062] Figure 2This is a diagram conceptually showing a communication method between a plurality of ECUs in a car, which is one of the embodiments to which the present invention is applied.
[0063] The vehicle according to the embodiment of the present invention may be, for example, an electric vehicle, a hybrid vehicle, or a plug-in hybrid vehicle, and may include a battery pack including a battery according to the embodiment of the present invention and a battery management system (BMS). The vehicle may include a four-wheel vehicle and a two-wheel vehicle, and operates by receiving power from the battery pack.
[0064] For the operation of the vehicle, control operations such as motor drive control, regenerative braking control, air conditioning load control, and electric load power (12V) supply control are required. Figure 2 , a car may include several electronic control units (ECUs) for these control operations.
[0065] Meanwhile, the BMS 100 is one of the control devices in the vehicle and can be understood as a type of ECU. In addition, in this specification, ECU can be used as a concept including a vehicle control unit (VCU) 210, which is the highest-level controller that manages all operations and controls in the vehicle. The ECU 220 can also refer to one or more ECUs (or various devices or systems using batteries) in the vehicle under the control of the VCU 210.
[0066] The ECU may include a random access memory (RAM) and a read-only memory (ROM) as internal storage devices. The RAM within the ECU can temporarily store various signals that occur while the vehicle is running. The stored data gradually disappears over time and is lost when power is not supplied. On the other hand, the ROM within the ECU records the control data necessary for the vehicle to move, and the data stored in the ROM will not be arbitrarily erased or modified.
[0067] When ECU is applied to electric vehicles (hybrid vehicles), it is also called EPCU (Electric Power Control Unit), which is a device that controls the overall movement of the vehicle as well as controls the electric motor in the vehicle. EPCU can be understood as having similar functions to ECU and transmission control unit (TCU).
[0068] Meanwhile, multiple ECUs contained in a car can communicate with each other through the Controller Area Network (CAN) bus. Controller Area Network (CAN) communication is a standard communication specification designed to allow microcontrollers or devices to communicate with each other in a vehicle without a host computer. CAN communication is a non-host bus message-based network protocol mainly used for communication between several controllers, and is mainly used in vehicles.
[0069] The communication method used by the CAN protocol is a multi-master communication method, and all CAN controllers ( Figure 2 The ECU, VCU, and BMS in the vehicle are used as the master device, and each controller can use the CAN bus whenever it needs to. The CAN protocol also uses a message-oriented transmission protocol and is electrically differentiated using two twisted pairs, making it immune to electrical noise.
[0070] refer to Figure 2 , all nodes on the CAN bus are connected through a two-wire bus, and each signal line consists of CAN_H (high) and CAN_L (low) with different voltages. CAN communication uses a half-duplex method, which transmits data one bit at a time through two complementary signals on the CAN_H and CAN_L bus lines. The CAN bus has two logical states, dominant and recessive, depending on the signal state. The dominant state can represent a logic '0', while the recessive state can represent 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), while the CAN_L bus pin is biased to a low voltage potential (e.g., ~1.5V). Communication between CAN nodes is achieved in the following manner: if the voltage difference between the two signal lines is below a certain threshold, the voltage difference is determined to be recessive, and if the voltage difference is greater than another threshold, the voltage difference is determined to be dominant.
[0071] Figure 3 The flowchart of operations between components in the BMS data storage method according to an embodiment of the present invention is shown.
[0072] Figure 3 A first embodiment showing how cooperative control is performed between components for a BMS data storage method according to an embodiment of the present invention is shown.
[0073] refer to Figure 3 In this embodiment, the components involved in the BMS data storage method may be a battery management system (BMS) 100 and a vehicle control unit (VCU) 210 in a vehicle. This embodiment is presented under the assumption that the VCU is a safer ECU than the BMS located in a dangerous location closer to the battery in an emergency such as a fire. As previously Figure 2 As shown in , the CAN protocol can be used to perform communication between the BMS and the VCU. Figure 3 The message transmission between the BMS and the VCU shown in FIG. 1 may be performed via the CAN protocol.
[0074] The battery management device (BMS) 100 may detect an event requiring urgent storage of BMS data (S310). Here, the event requiring urgent storage of BMS data may include an event that the temperature of the battery detected by the battery management device is higher than a threshold value. In addition, the event requiring urgent storage of BMS data may also include any situation where there is a risk of loss of data records due to a problem in a storage device (or recording device) storing BMS data.
[0075] When the battery management device 100 detects an event that requires urgent storage of BMS data, the battery management device 100 may request the first controller in the vehicle to urgently store BMS data (S320). Here, the first controller may be the VCU 210, which is the uppermost controller that centrally controls multiple ECUs that communicate with the battery management device 100.
[0076] The first controller having received the data emergency storage request from the battery management device 100 may check whether the first controller can receive and store the emergency storage data (S321). More specifically, the first controller may determine whether the first controller can store the emergency storage data by checking whether the CAN line as the communication path with the battery management device is normal and whether a space capable of storing the data that needs to be urgently stored is ensured.
[0077] If the first controller 210 determines that the first controller itself has the ability to store the data that needs to be urgently stored, the first controller may transmit a response completion message to the BMS request to the battery management device 100 (S330). The battery management device 100 that receives the response completion message may transmit the data that needs to be urgently stored to the first controller (S340).
[0078] The first controller may receive and store data that requires emergency storage. Here, the number of data transmissions may be one or two or more times, and the number of data transmissions may be determined based on the amount of data that requires emergency storage and the amount of data that can be transmitted via one CAN frame. When multiple data transmissions occur, the first controller may deliver a reply message to the BMS for each data transmission (S350). When the data storage is completed, the first controller 210 may transmit a storage completion and end message to the battery management device 100 (S350). Upon receiving the storage completion message, the battery management device 100 may end the backup transmission process of the BMS data (S360).
[0079] Figure 4 The structure of a CAN communication frame used in the BMS data storage method according to an embodiment of the present invention is shown.
[0080] Figure 4The CAN communication frame 40 shown in FIG. 4 may be a message frame exchanged between a battery management system (BMS) and a vehicle control unit (VCU). Figure 4 The CAN communication frame 40 shown in FIG. 4 may also be a message exchanged between a BMS, a VCU, and a plurality of electronic control units (ECUs). The CAN communication frame 40 according to an embodiment of the present invention may be configured to include an ID field 41 and a data field (data 1 to data 8) 42.
[0081] According to an embodiment of the present invention, the frame ID 41 having “Ox100” may indicate a message frame transmitted from the BMS to the VCU, and the frame ID 41 having “Ox101” may indicate a message frame transmitted from the VCU to the BMS.
[0082] In addition, among the data fields, the "DATA1" field may indicate whether the corresponding message frame is a message requesting urgent storage (e.g., indicated as "1") or a message regarding whether a response can be stored (e.g., indicated as "2"). The subsequent "DATA2" field may indicate a transmission (Tx) sequence (0 to 255), and the "DATA3" to "DATA8" fields may indicate the transmitted payload data. Here, the transmission period of the CAN communication frame may be 10ms.
[0083] Figure 5 A flowchart of operations between components in a BMS data storage method according to another embodiment of the present invention is shown.
[0084] Figure 5 A second embodiment showing how to perform coordinated control between several components for BMS data storage according to the present invention is depicted.
[0085] refer to Figure 5 , the components involved in the BMS data storage method in this embodiment may be a battery management device (BMS) 100, a vehicle control unit (VCU) 210, and one or more electronic control units (ECUs) 220 in a vehicle. Communication may be performed between the BMS, the VCU, and the ECU using the CAN protocol. Therefore, messages between the BMS, the VCU, and the ECU may be transmitted via the CAN protocol.
[0086] according to Figure 5 In the embodiment shown in FIG. 5 , a battery management device (BMS) 100 may detect an event requiring urgent storage of BMS data (S510). Here, the event requiring urgent storage of BMS data may include an event in which the temperature of a battery detected by the battery management device exceeds a threshold value. The event requiring urgent storage of BMS data may also include any situation in which there is a risk of loss of data records due to a problem in a storage device (or recording device) storing BMS data.
[0087] When the battery management device detects an event requiring emergency storage of BMS data, the battery management device 100 may request the first controller in the vehicle to urgently store BMS data (S520). Here, the first controller may be the VCU 210, which is the highest controller that centrally controls multiple ECUs that communicate with the BMS.
[0088] The first controller that has received a data emergency storage request from a battery management system (BMS) may forward the data emergency storage request to one or more second controllers under the control of the first controller, and request the one or more second controllers to check whether backup storage is possible (S530). One or more second controllers that have received a request message for confirming the availability of backup storage from the first controller may check whether the second controller itself can receive and store emergency storage data (S531). Here, the second controller may determine whether the second controller itself can store emergency storage data by checking whether the CAN line, which is a communication path with the VCU, is normal and whether space for storing data that needs to be urgently stored is ensured. Here, the second controller may be one of all ECUs in the vehicle except the VCU, and may communicate with the VCU via the CAN line.
[0089] In other words, in this embodiment, the first controller 210 may function as a simple gateway that transmits the BMS data received from the battery management device 100 to the second controller 220 .
[0090] If the second controller determines that the second controller itself has the ability to store data that needs to be stored urgently, the second controller may transmit a response to the request to confirm whether backup storage is possible to the first controller (S540). The first controller that has received a response completion message from one or more second controllers may determine the entity that will perform data backup storage based on the received response completion message (S550). Here, the first controller may select the safest controller for storing BMS data among the multiple second controllers that respond that backup data storage can be performed, and confirm the selected controller as the backup storage subject.
[0091] Here, the safest controller for storing BMS data may be selected as the ECU located farthest from the battery pack (including the battery and the battery management device) or the ECU with the lowest temperature, or the most suitable controller when considering these two conditions. In other words, the safest controller for storing BMS data may be determined based on one or more of the availability of space for storing BMS data, the location from the battery pack, and the temperature of the corresponding controller.
[0092] In the case where the first controller 210 confirms the subject that performs the backup storage, the first controller 210 may transmit a response completion message to the battery management device (BMS) 100 (S560). Thereafter, the first controller that receives the BMS data from the battery management device may transmit the BMS data to the ECU confirmed as the backup storage subject (S570, S571). The ECU 220 as the backup subject may receive and store the data that needs to be urgently stored. Here, the number of data transmission and delivery may be 1 time, or 2 times or more, and the number of transmission and delivery may be determined based on the amount of data that needs to be urgently stored and the amount of data that can be transmitted via one CAN frame. In the case of performing multiple data transmissions, the backup subject ECU may transmit a reply message to the battery management device through the first controller when each transmission is completed (S580, S581). When the data storage is completed, the backup subject ECU 220 may transmit a storage completion and end message to the battery management device 100 through the first controller (S580, S581). The battery management device that has received the storage completion and end message may end the BMS data transmission process (S590).
[0093] At the same time, even in Figure 5 In the case of the embodiment shown in Figure 4 40 is a CAN communication frame 40 exchanged between a BMS and a VCU shown in FIG. Here, the CAN communication frame 40 may be a message exchanged between a BMS, a VCU, and a plurality of ECUs. The CAN communication frame 40 according to an embodiment of the present invention may be configured to include an ID field 41 and a data field (data 1 to data 8 fields) 42.
[0094] According to the present embodiment, when the frame ID is "Ox100", it may represent a message frame transmitted from the BMS to the VCU. In addition, when the frame ID 41 is "Ox101", it may represent a message frame transmitted from the VCU to the BMS. In addition, in the case of a frame ID of "Ox102" or higher, it may be assigned to a different ECU to indicate that the frame is transmitted by the corresponding ECU. Here, the ID of each ECU may be predetermined and pre-shared by all nodes on the CAN bus (ie, VCU, BMS, and one or more ECUs), and stored in each node (e.g., in the ROM of each device).
[0095] In addition, among the data fields, the "DATA1" field may indicate whether the message frame is a message requesting emergency storage (e.g., marked as "1") or a message responding whether emergency storage is possible (e.g., marked as "2"). The subsequent "DATA2" field may indicate a transmission (Tx) sequence (0 to 255), and the "DATA3" to "DATA8" fields may indicate payload data transmission.
[0096] At the same time, it is configured to execute Figure 3 and Figure 5 The BMS data storage system of the BMS data storage method shown in the figure may include: a first controller, which is located in a device containing a battery; and a battery management device, which is configured to: upon detecting an event requiring urgent storage of BMS data, request the first controller to urgently store the BMS data, receive a response to the request for urgent storage of the BMS data from the first controller, and transmit the BMS data to the first controller.
[0097] The first controller can be configured to: determine whether the communication path between the battery management device and the first controller is normal in response to a request for emergency storage of BMS data; check whether the first controller ensures storage space to store BMS data and sends a response message to the battery management device; and receive BMS data from the battery management device and store the BMS data in a storage device within the first controller.
[0098] Meanwhile, the BMS data storage system may further include one or more second controllers under the control of the first controller.
[0099] The first controller may also be configured to: in response to a request for emergency storage of the BMS data, determine which of the second controllers is safest to store the BMS data; receive the BMS data from the battery management device; and transmit the BMS data to the safest second controller.
[0100] The safest second controller may be determined based on one or more of availability of space to store BMS data, location from the battery pack, and temperature of the corresponding controller.
[0101] The request for emergency storage of BMS data and the transmission of BMS data may be performed via controller area network (CAN) communication.
[0102] At least one frame used for CAN communication may include a field specifying identifiers of a sender and a receiver of the frame and one or more data fields.
[0103] One or more data fields may include information indicating whether the frame is a message requesting emergency storage or a message responding whether emergency storage is possible.
[0104] Identifiers of the sender and receiver of a designated frame can be uniquely assigned to each of: a battery management device, a first controller, and one or more second controllers under the control of the first controller, and the assignment information of each identifier can be pre-shared and pre-stored by the battery management device, the first controller, and one or more second controllers.
[0105] The first controller may be a vehicle control unit (VCU), which is a top-level controller that centrally controls one or more electronic control units (ECUs) that communicate with the battery management device.
[0106] Figure 6 is a block diagram of a battery management device according to an embodiment of the present invention.
[0107] refer to Figure 6 The battery management device 100 according to an embodiment of the present invention may include a processor 110 and a memory 120 storing at least one instruction executed by the processor. Here, the processor may be, for example, a microcontroller unit (MCU) or another type of controller.
[0108] At least one instruction may include: an instruction to detect at least one event requiring emergency storage of BMS data; an instruction to request emergency storage of BMS data to a first controller in a device including a battery when an event requiring emergency storage of BMS data is detected; and an instruction to receive a response to the request for emergency storage of BMS data from the first controller and transmit the BMS data to the first controller.
[0109] The at least one event requiring urgent storage of the BMS data may include an event in which a temperature of the battery detected by the battery management device is equal to or greater than a threshold value.
[0110] The request for emergency storage of BMS data and the transmission of BMS data may be performed via controller area network (CAN) communication.
[0111] At least one frame used for CAN communication may include a field specifying identifiers of a sender and a receiver of the frame and one or more data fields.
[0112] One or more data fields may include information indicating whether the frame is a message requesting emergency storage or a message responding whether emergency storage is possible.
[0113] Identifiers of the sender and receiver of a designated frame can be uniquely assigned to each of: a battery management device, a first controller, and one or more second controllers under the control of the first controller, and the assignment information of each identifier can be pre-shared and pre-stored by the battery management device, the first controller, and one or more second controllers.
[0114] The BMS data transmitted to the first controller is transmitted to and stored in the first controller or a selected one of the one or more second controllers interoperating with the first controller.
[0115] Meanwhile, the battery management apparatus 100 according to the embodiment of the present invention may further include an input interface device 140 , an output interface device 150 , a storage device 160 , etc. The respective components included in the battery management apparatus 100 may be connected through a bus 170 and may communicate with each other.
[0116] In addition, the memory 120 (or storage unit) may include at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory may include at least one of a read-only memory (ROM) and a random access memory (RAM), and may include an electrically erasable programmable read-only memory (EEPROM). The memory 120 according to an embodiment of the present invention may store information related to battery usage records and items related to diagnostic occurrences.
[0117] The operation of the method according to an embodiment of the present invention can be implemented as a computer-readable program or code on a computer-readable recording medium. The computer-readable recording medium includes all types of recording devices having data readable by a computer system stored therein. In addition, the computer-readable recording medium can be distributed in a network-connected computer system, thereby storing and executing a computer-readable program or code in a distributed manner.
[0118] Although some aspects of the present invention have been described in the context of an apparatus, it can also be represented by a description according to a corresponding method, wherein a block or apparatus corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method can also represent features of a corresponding block or item or a corresponding apparatus. Some or all of the method steps can be performed by (or using) a hardware device such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, one or more of the most important method steps can be performed by such an apparatus.
[0119] In the foregoing, the present invention has been described with reference to exemplary embodiments thereof, but those skilled in the art will appreciate that various modifications and changes may be made to the present invention within the scope without departing from the spirit and area of the invention described in the appended claims.
Claims
1. A battery management device for managing battery management system (BMS) data related to a state of a battery, the device comprising: at least one processor; as well as a memory configured to store at least one instruction executed by the at least one processor, The at least one instruction includes: Instructions for detecting at least one event requiring urgent storage of BMS data; requesting a first controller in a device including the battery to urgently store the BMS data when an event requiring urgent storage of the BMS data is detected; and A response to the request to urgently store the BMS data and an instruction to transmit the BMS data to the first controller are received from the first controller.
2. The device according to claim 1, wherein: The at least one event requiring urgent storage of BMS data includes an event in which a temperature of the battery detected by the battery management device is equal to or greater than a threshold value.
3. The device according to claim 1, wherein: The request for emergency storage of the BMS data and the transmission of the BMS data are performed through controller area network (CAN) communication.
4. The device according to claim 3, wherein: At least one frame used for the CAN communication includes a field specifying identifiers of a sender and a receiver of the frame and one or more data fields.
5. The device according to claim 4, wherein: The one or more data fields include information indicating whether the frame is a message requesting emergency storage or a message responding whether the emergency storage can be performed.
6. The device according to claim 4, wherein: The identifiers specifying 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 of each identifier is pre-shared and pre-stored by the battery management device, the first controller, and the one or more second controllers.
7. The device according to claim 1, wherein: The BMS data transmitted to the first controller is transmitted to and stored in the first controller or a selected one of the one or more second controllers interoperating with the first controller.
8. A system for storing battery management system (BMS) data related to a state of a battery, the system comprising: a first controller located within a device containing the battery; as well as A battery management device, wherein the battery management device is configured to: upon detecting an event requiring urgent storage of the BMS data, request the first controller to urgently store the BMS data, receive a response to the request for urgent storage of the BMS data from the first controller, and transmit the BMS data to the first controller.
9. The system according to claim 8, wherein: The first controller is configured to: In response to the request for emergency storage of the BMS data, determining whether a communication path between the battery management device and the first controller is normal; checking whether the first controller ensures storage space to store the BMS data and sends a response message to the battery management device; and The BMS data is received from the battery management device and stored in a storage device within the first controller.
10. The system according to claim 8, further comprising: One or more second controllers under the control of the first controller.
11. The system according to claim 10, wherein: The first controller is further configured to: In response to the request for emergency storage of the BMS data, determining which of the second controllers stores the BMS data most securely; receiving the BMS data from the battery management device; and The BMS data is transmitted to the safest second controller.
12. The system according to claim 11, wherein: The safest second controller is determined based on one or more of availability of space to store the BMS data, location from the battery, and temperature of a corresponding controller.
13. The system according to claim 10, wherein: The request for emergency storage of the BMS data and the transmission of the BMS data are performed through controller area network (CAN) communication.
14. The system according to claim 13, wherein: At least one frame used for the CAN communication includes a field specifying an identifier of a sender and a receiver of the frame and one or more data fields.
15. The system of claim 14, wherein: The one or more data fields include information indicating whether the frame is a message requesting emergency storage or a message responding whether the emergency storage can be performed.
16. The system of claim 14, wherein: The identifiers specifying 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, and The assignment information of each identifier is pre-shared and pre-stored by the battery management device, the first controller, and the one or more second controllers.
17. The system of claim 8, wherein: The first controller is a vehicle control unit (VCU), which is a top-level controller that centrally controls one or more electronic control units (ECUs) that communicate with the battery management device.
18. A method for storing battery management system (BMS) data related to a state of a battery, the method comprising: detecting, by the battery management device, at least one event requiring urgent storage of BMS data; When an event requiring urgent storage of the BMS data is detected, the battery management device requests a first controller in a device including the battery to urgently store the BMS data; as well as A response to the request to urgently store the BMS data is received by the battery management device from the first controller and the BMS data is transmitted to the first controller.
19. The method according to claim 18, wherein: The at least one event requiring urgent storage of BMS data includes an event in which a temperature of the battery detected by the battery management device is equal to or greater than a threshold value.
20. The method of claim 18, further comprising: In response to the request for emergency storage of the BMS data, Determining, by the first controller, whether a communication path between the battery management device and the first controller is normal; checking whether the first controller ensures storage space to store the BMS data; as well as In a case where the communication path between the battery management device and the first controller is normal and the first controller has a storage space to store the BMS data, the first controller sends a response message to the battery management device.
21. The method of claim 19, further comprising: Receiving, by the first controller, the BMS data from the battery management device; as well as The BMS data is stored by the first controller in a storage device within the first controller.
22. The method of claim 18, further comprising: In response to the request for emergency storage of the BMS data, determining, by the first controller, which of the second controllers under the control of the first controller stores the BMS data most safely; Receiving, by the first controller, the BMS data from the battery management device; The first controller transmits the BMS data to the safest second controller.
23. The method according to claim 22, wherein: The safest second controller is determined based on one or more of availability of space to store the BMS data, location from the battery, and temperature of a corresponding controller.
24. The method according to claim 18, wherein: The request for emergency storage of the BMS data and the transmission of the BMS data are performed through controller area network (CAN) communication.
25. The method according to claim 24, wherein: At least one frame used for the CAN communication includes a field specifying identifiers of a sender and a receiver of the frame and one or more data fields.
26. The 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 whether the emergency storage can be performed.
27. The method according to claim 25, wherein: The identifiers specifying 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, and The assignment information of each identifier is pre-shared and pre-stored by the battery management device, the first controller, and the one or more second controllers.
Citation Information
Cited By
Battery cell data acquisition method and apparatus, battery management system, storage medium and program product
WO2026188706A1
