Battery management device and method, and battery system including the same

The battery management system efficiently updates control logic using a virtual machine, addressing the inefficiencies of conventional systems by enabling real-time updates without interrupting battery operations.

JP7859745B2Active Publication Date: 2026-05-15LG ENERGY SOLUTION LTD
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
LG ENERGY SOLUTION LTD
Filing Date
2023-07-18
Publication Date
2026-05-15

AI Technical Summary

Technical Problem

Conventional battery management systems require on-site visits and system interruptions for software updates, leading to inefficiencies and additional costs.

Method used

A battery management system that executes updated control logic using a virtual machine without interrupting battery charge/discharge monitoring, utilizing a memory and processor to execute instructions that manage control logic updates, including copying and parsing logic from external storage areas.

Benefits of technology

Enables efficient battery operation management by allowing real-time recognition and execution of updated control logic, reducing the need for system interruptions and on-site visits.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007859745000001
    Figure 0007859745000001
  • Figure 0007859745000002
    Figure 0007859745000002
  • Figure 0007859745000003
    Figure 0007859745000003
Patent Text Reader

Abstract

A battery management device, method, and battery system including the same according to an embodiment of the present invention can provide software capable of highly efficient battery operation management by recognizing and executing control logic updated from a control logic generation device by a virtual machine in real time, so that the updated control logic can be executed without interrupting the battery management system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application claims the benefit of the filing date of Korean Patent Application No. 10-2022-0146067, filed with the Korean Intellectual Property Office on November 4, 2022, and all of the contents disclosed in the document of the Korean patent application are incorporated herein.

[0002] The present invention relates to a battery management device and method, and a system including the same. More specifically, the present invention relates to a battery management device and method including a virtual machine for executing updated control logic without interrupting battery monitoring, and a system including the same.

Background Art

[0003] An Energy Storage System (ESS) is a system that connects renewable energy, a battery that stores power, and existing grid power. In recent years, with the spread of smart grids and renewable energy, and with the importance of improving the efficiency and stability of power grids, the demand for energy storage systems is increasing steadily for power supply and demand regulation and power quality improvement. Depending on the purpose of use, the output and capacity of the energy storage system vary. To configure a large-capacity energy storage system, multiple battery systems can be connected to each other.

[0004] For example, an energy storage system applied to a photovoltaic (PV) power generation system can include a battery section composed of a number of batteries, a battery management system for battery management, a power conversion system (PCS), an energy management system (EMS), a DC-DC converter, and the like.

[0005] Among these, the battery management system is the core component for managing batteries, and continuous system updates are required to efficiently manage batteries in operation at the site.

[0006] Therefore, conventional battery management systems required administrators to visit the site directly, interrupt the operation of the battery system while it was in use, and then perform the software update.

[0007] However, in this case, compensation for the interruption of the battery management system's use is always required, and on-site visits are necessary for software updates, resulting in time and material costs, which presents an inefficient challenge. [Overview of the project] [Problems that the invention aims to solve]

[0008] The objective of the present invention, which aims to solve the above-mentioned problems, is to provide a highly efficient battery management device.

[0009] Another objective of the present invention, in order to solve the above-mentioned problems, is to provide a highly efficient battery management method.

[0010] Another objective of the present invention, in order to solve the above-mentioned problems, is to provide a highly efficient battery system. [Means for solving the problem]

[0011] A battery management system (BMS) according to one embodiment of the present invention for achieving the above objective, which operates according to updated control logic without interrupting battery charge / discharge monitoring, includes memory and a processor that executes at least one instruction stored in memory, the at least one instruction including an instruction that controls a virtual machine that executes control logic pre-recorded in memory to execute the updated control logic.

[0012] Here, instructions that control the virtual machine to execute the updated control logic may include instructions to execute a loader to copy the updated control logic to memory if the updated control logic exists in an external storage area connected to the battery management device, and instructions to operate the virtual machine to parse and execute the updated control logic.

[0013] Furthermore, at least one instruction may further include an instruction to operate a loader to copy pre-recorded control logic from an external storage area and store it in memory, and an instruction to operate a virtual machine to execute the pre-recorded control logic.

[0014] Furthermore, at least one instruction may further include an instruction that, upon receiving a termination signal, stores the updated control logic in external storage and terminates the program.

[0015] On the other hand, the memory may include non-volatile memory for storing at least one processor instruction, and volatile memory for storing pre-recorded control logic and updated control logic.

[0016] In this case, the volatile memory may include a main memory for storing pre-recorded control logic and a backup memory for storing updated control logic.

[0017] On the other hand, at least one instruction may further include, if, before the termination signal is received, any newly updated control logic is stored in the external storage area after the updated control logic, an instruction to copy the newly updated control logic and store it in one of the partitioned areas of the backup memory in memory, and an instruction to operate the virtual machine to execute the newly updated control logic.

[0018] Furthermore, pre-recorded and updated control logic can be generated by a logic generator and compiled into a computer language compatible with the virtual machine.

[0019] On the other hand, the external storage area may include a non-volatile storage device that includes at least one of the following: a hard disk drive (HDD), flash memory, EEPROM, and a portable storage device.

[0020] Furthermore, the control logic generation device can be connected to the battery management device via a wireless or wired network, and the updated control logic can be transmitted to the battery management device.

[0021] A battery management method for a Battery Management System (BMS), comprising memory and a processor, which operates according to updated control logic without interrupting battery charge / discharge monitoring, according to another embodiment of the present invention for achieving the objective, includes the step of controlling a virtual machine that executes control logic pre-recorded in memory to execute the updated control logic.

[0022] Here, the steps of controlling the virtual machine to execute the updated control logic may include, if the updated control logic exists in an external storage area connected to the battery management device, running a loader to copy the updated control logic and store it in memory, and operating the virtual machine to parse and execute the updated control logic.

[0023] Furthermore, it can further include steps of operating a loader to copy control logic pre-recorded in an external storage area and storing it in a memory, and operating a virtual machine to execute the pre-recorded control logic.

[0024] In addition, the battery management method can further include a step of storing the updated control logic in an external storage area and ending when an end signal is received.

[0025] On the other hand, the memory can include a non-volatile memory that stores at least one instruction of a processor, and a volatile memory that stores pre-recorded control logic and updated control logic.

[0026] At this time, the volatile memory can include a main memory that stores pre-recorded control logic and a backup memory that stores updated control logic.

[0027] On the other hand, if new updated control logic is stored in the external storage area after the updated control logic before an end signal is received, the battery management method can further include steps of copying the newly updated control logic and storing it in any one of the divided areas of the backup memory in the memory, and operating the virtual machine to execute the newly updated control logic.

[0028] In addition, the pre-recorded control logic and the updated control logic can be generated from a control logic generator and compiled into a computer language compatible with the virtual machine.

[0029] On the one hand, the external memory area can be included in a non-volatile memory device including at least one of a hard disk drive (HDD), a flash memory, an EEPROM, and a removable memory device.

[0030] In addition, the control logic generation device can be connected to the battery management device via a wireless or wired network to transmit the updated control logic to the battery management device.

[0031] A battery management system according to another embodiment of the present invention for achieving the object, which operates according to the updated control logic without interrupting the charge / discharge monitoring of the battery, includes a control logic generation device (Logic generator) that generates and compiles the updated control logic, a memory, and a processor, and a battery management device that controls a virtual machine that executes the control logic pre-recorded in the memory to execute the updated control logic.

[0032] Here, if there is updated control logic in the external memory area connected to the battery management device, the battery management device can execute a loader to copy the updated control logic and store it in the memory, and parse the updated control logic to operate the virtual machine to execute it.

[0033] In addition, the battery management device can further include operating a loader to copy the control logic pre-recorded in the external memory area and store it in the memory, and operating the virtual machine to execute the pre-recorded control logic.

[0034] In addition, the battery management device can further include storing the updated control logic in the external memory area and ending when receiving an end signal.

[0035] On the other hand, the battery management device may further include, if, before the termination signal is received, any newly updated control logic stored in the external storage area after the updated control logic has been stored, copying the newly updated control logic and storing it in one of the partitioned areas of the backup memory in memory, and then instructing the virtual machine to execute the newly updated control logic.

[0036] At this time, the control logic generation device can compile the pre-recorded control logic and the updated control logic into a computer language compatible with the virtual machine.

[0037] On the other hand, the external storage area may include a non-volatile storage device that includes at least one of the following: a hard disk drive (HDD), flash memory, EEPROM, and a portable storage device.

[0038] Furthermore, the control logic generation device can be connected to the battery management device via a wireless or wired network, and the updated control logic can be transmitted to the battery management device. [Effects of the Invention]

[0039] The battery management device and method according to an embodiment of the present invention, and the battery system including the same, can provide software that enables highly efficient battery operation management by allowing the updated control logic to be executed without interrupting the battery management system, through the real-time recognition and execution of the control logic updated from the control logic generation device by a virtual machine. [Brief explanation of the drawing]

[0040] [Figure 1] This is a conceptual diagram of a conventional battery system. [Figure 2]This is a block diagram of an energy storage system to which embodiments of the present invention can be applied. [Figure 3] This is a conceptual diagram of a battery system according to an embodiment of the present invention. [Figure 4] This is a block diagram of a battery management device according to an embodiment of the present invention. [Figure 5] This is a block diagram of the memory in a battery management device according to an embodiment of the present invention. [Figure 6] This is a flowchart illustrating a battery management method according to an embodiment of the present invention. [Figure 7] This flowchart illustrates a battery management method according to an embodiment of the present invention, specifically the case where there is a newly updated control logic after the updated control logic. [Modes for carrying out the invention]

[0041] The present invention can be modified in various ways and may have many different embodiments. Therefore, specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this should not be understood as limiting the present invention to specific embodiments, but rather as including all modifications, equivalents, or substitutes that fall within the spirit and technical scope of the present invention. Similar reference numerals are used for similar components in the description of each drawing.

[0042] Terms such as First, Second, A, B, etc., may be used to describe various components, but the components should not be limited by such terms. The terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the First component may be named the Second component, and similarly, the Second component may be named the First component. The term "and / or" includes a combination of multiple related items or one of multiple related items.

[0043] When it is stated that one component is "linked" or "connected" to another component, it should be understood that this may mean that it is directly linked or connected to that other component, but that there may also be another component in between. Conversely, when it is stated that one component is "directly linked" or "directly connected" to another component, it should be understood that there is no other component in between.

[0044] The terms used in this application are used solely to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless they are clearly different in context. In this application, terms such as “includes” or “having” are intended to specify the existence of features, figures, steps, actions, components, parts, or combinations thereof described in the specification, and should not be understood to preemptively exclude the existence or possibility of adding one or more other features, figures, steps, actions, components, parts, or combinations thereof.

[0045] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as those generally 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 the meaning consistent with their meaning in the context of the relevant art, and not as ideal or overly formal unless explicitly defined herein.

[0046] Figure 1 is a conceptual diagram of a conventional battery system.

[0047] Referring to Figure 1, typical battery systems applied to energy storage systems require continuous system updates to efficiently manage batteries in operation at the site.

[0048] Therefore, conventionally, in order to update the software of the battery management device within the battery system, administrators would visit the site in person, interrupt the operation of the battery system while it was running, and perform the software update on the battery management device.

[0049] To explain in more detail, previous battery management system updates involved software updates using compiled image files, which always required interrupting the use of the battery system in order to apply the compiled image files to the software.

[0050] Therefore, in order to update the software of the conventional battery management device, the battery system that was already in operation was interrupted, the existing compiled executable files remaining in memory were deleted, and the initialization of the battery management device proceeded.

[0051] Subsequently, the battery management device was switched to update mode, the loader copied the updated compiled image from the external storage device into memory and stored it, the battery management device was initialized, and the updated compiled image was applied to the software program to perform the update. For example, the external storage device may be a portable storage device.

[0052] Thus, conventional battery systems had the disadvantage of being inefficient because they required interrupting the operation of the battery system to apply the updated compiled image to the software program, necessitating compensation for the interruption of use, and requiring on-site visits for software updates, resulting in time and material costs.

[0053] Therefore, the battery system according to the embodiment of the present invention can acquire control logic that has been updated in real time and reflect the updated control logic in the system without interrupting the system by a virtual machine.

[0054] Figure 2 is a block diagram of an energy storage system to which embodiments of the present invention can be applied.

[0055] Referring to Figure 2, batteries that play a role in storing electricity in an energy storage system can typically be implemented in a form where a number of battery modules constitute a battery rack, and a number of battery racks constitute a battery bank. Here, depending on the device or system in which the batteries are used, a battery rack may also be called a battery pack. For example, batteries #1, #2, ..., #N shown in Figure 1 may be in the form of a battery pack or a battery rack.

[0056] In this case, each battery may be equipped with a Battery Management System (BMS) 1000.

[0057] A battery management system 1000 (BMS) to which embodiments of the present invention can be applied can monitor the current, voltage, and temperature of each battery pack (or rack) managed by the machine, calculate the State of Charge (SOC) based on the monitoring results, and control charging and discharging.

[0058] On the other hand, each battery section, which consists of numerous batteries and peripheral circuits and devices, can be equipped with a Battery Section Controller (BSC). This allows the BSC2000 to monitor and control the voltage, current, temperature, circuit breakers, and other control targets within the battery section. The BSC2000 also calculates the output of each DC-DC converter based on the monitored battery status information and transmits this information to the DC-DC converters.

[0059] Furthermore, the Power Conversion System (PCS) 4000 provided for each battery section controls the charging and discharging of the batteries by controlling the power supplied from the outside and the power supplied from the battery section to the outside, and may include a DC / AC inverter.

[0060] Furthermore, the output of the DC-DC converter 5000 can be connected to the PCS4000, which in turn can be connected to the grid 600 and load 7000. The PCS4000 normally operates in constant power mode. The Power Management System (PMS) 3000 connected to the PCS4000 is the highest-level control unit that determines and controls the output of the PCS4000 based on the monitoring and control results of the BMS1000 or BSC2000.

[0061] In the energy storage system shown in Figure 2, battery #1 is connected to DC-DC converter #1, battery #2 is connected to DC-DC converter #2, and battery #N is connected to DC-DC converter #N. The output of the DC-DC converter 5000 corresponding to each battery is connected to the PCS4000 via the DC link section.

[0062] A DC-DC converter may be a bidirectional converter, and when conversion is performed from the battery to the load, the input of the DC-DC converter can be connected to the battery (battery unit, battery rack, or battery pack), and the output of the DC-DC converter can be connected to the load. Examples of DC-DC converters include various types of converters such as full-bridge converters, half-bridge converters, and flyback converters.

[0063] A DC-DC converter may be a bidirectional converter, and when conversion is performed from the battery to the load, the input of the DC-DC converter can be connected to the battery (battery unit, battery rack, or battery pack), and the output of the DC-DC converter can be connected to the load. Examples of DC-DC converters include various types of converters such as full-bridge converters, half-bridge converters, and flyback converters.

[0064] On the other hand, communication between the BMS1000, BSC2000, PMS3000, and PCS4000 can be performed using CAN (Controller Area Network) or Ethernet (shown by dotted lines in Figure 2).

[0065] Hereinafter, preferred embodiments of a battery system applicable to an energy storage system (ESS) will be described in detail with reference to the accompanying drawings.

[0066] Figure 3 is a conceptual diagram of a battery system according to an embodiment of the present invention.

[0067] Referring to Figure 3, the battery system 1000 may be applied to an energy storage system (ESS) as described above. This allows the battery system 1000 to manage the state of the battery while it is in operation at the site.

[0068] According to the embodiment, the battery system 1000 can perform continuous system updates to efficiently manage batteries in operation at the site.

[0069] More specifically, the battery system 1000 may include a control logic generation device 1100 and a battery management device 1300. Furthermore, the battery system 1000 may further include an external storage device 1500.

[0070] The Logic Generator 1100 can generate control logic for application to the software of the Battery Management Device 1300 (described later) for software updates of at least one battery system applied to an Energy Storage System (ESS). According to one embodiment, the Logic Generator 1100 may be a dual-source supplier PC with the Battery Management Device 1300 (described later).

[0071] Here, the control logic is program logic for managing the state of the battery and may include at least one program logic that requires continuous updates for efficient management of the battery state, such as battery charge / discharge control, cell balancing, or state monitoring. However, the control logic may also be provided modularly, without limitation, on a program logic-by-program logic basis.

[0072] For example, if the control logic is modularized and provided separately for each program logic, the virtual machines within the battery management device 1300, described later, can also be provided individually for each module. This allows the modularized control logic and virtual machines to operate identically to the functions of the control logic and virtual machines described later.

[0073] The control logic generation device 1100 may include a compiler. This allows the control logic generation device 1100 to perform compiler operations and compile the generated control logic into a computer language compatible with the virtual machine (VM) in the battery management device 1300, which will be described later. This allows the interpreter of the virtual machine (VM) in the battery management device 1300, which will be described later, to execute the updated control logic generated from the control logic generation device 1100. However, without limiting what has been disclosed, the compilation of the updated control logic can also be performed by the external storage device 1500, which will be described later.

[0074] The battery management device 1300 can obtain the updated control logic generated from the control logic generation device 1100.

[0075] According to one embodiment, the battery management device 1300 can be connected to the control logic generation device 1100 via a wired or wireless network. This allows the battery management device 1300 to receive updated control logic from the control logic generation device 1100 via network communication.

[0076] According to another embodiment, the battery management device 1300 can acquire updated control logic using an external storage device 1500, which will be described later.

[0077] More specifically, the external storage device 1500 can be physically connected to the control logic generation device 1100 and the battery management device 1300 via ports. In other words, the external storage device 1500 can be physically connected to the control logic generation device 1100 and download the updated control logic generated from the control logic generation device 1100. Subsequently, the external storage device 1500 can be physically connected to the battery management device 1300, and if the battery management device 1300 recognizes the external storage device 1500, the battery management device 1300 can execute a loader to copy the updated control logic stored in the external storage device 1500 and temporarily store it in its own memory. Here, the loader may be a bootloader.

[0078] The battery management device 1300 may include a virtual machine (VM). This allows the battery management device 1300 to execute control logic stored in memory by having the virtual machine (VM) run by a processor described later.

[0079] According to one embodiment, the battery management device 1300 can execute control logic pre-recorded in at least one memory area during initial operation.

[0080] Subsequently, when the battery management device 1300 obtains the updated control logic, the loader stores the updated control logic in a backup memory area within the memory, and the virtual machine (VM) is operated to execute the updated control logic. For example, the virtual machine (VM) can run an interpreter to parse and execute the updated control logic. Here, as described above, the updated control logic is compiled from the control logic generation device 1100 into a computer language compatible with the interpreter in the virtual machine (VM) and provided, making it possible to drive it with the interpreter.

[0081] As described above, the external storage device 1500 may be a storage device that stores at least one piece of data. According to the embodiment, the external storage device 1500 may be a non-volatile storage device provided in the form of physical hardware. For example, the external storage device 1500 can be provided in the form of at least one of the following: a hard disk drive (HDD), flash memory, EEPROM, or portable storage device.

[0082] This allows the external storage device 1500 to temporarily store the updated control logic generated by the control logic generation device 1100 and transmit it to the battery management device 1300.

[0083] Furthermore, the external storage device 1500 can store control logic executed by the virtual machine (VM) before the battery management device 1300 terminates. Here, the control logic executed by the virtual machine (VM) can be copied by the loader when the battery management device 1300 is restarted and run in the main memory within the memory. The battery management method by which the battery management device operates will be explained in more detail in Figure 6 below.

[0084] Figure 4 is a block diagram of a battery management device according to an embodiment of the present invention.

[0085] Referring to Figure 4, the battery management device 1300 can include a memory 100, a processor 200, a transceiver 300, an input interface device 400, an output interface device 500, and a storage device 600, respectively. Here, the processor 200 may be a control unit for a battery pack and battery rack according to an embodiment of the present invention (for example, the MCU, microcontroller unit in Figure 2).

[0086] According to this embodiment, the components 100, 200, 300, 400, 500, and 600 included in the battery management device 1100 are connected by a bus 700 and can communicate with each other.

[0087] Of the components 100, 200, 300, 400, 500, and 600 of the battery management device 1300, the memory 100 and the storage device 600 can be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 100 can be composed of at least one of a read-only memory (ROM) and a random access memory (RAM). The memory 100 will be explained in more detail in Figure 5 below.

[0088] The processor 200 may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which a method according to the embodiment of the present invention is performed.

[0089] As described above, the processor 200 can execute at least one program command stored in the non-volatile memory within the memory 1100.

[0090] Figure 5 is a block diagram of the memory in the battery management device according to an embodiment of the present invention.

[0091] Referring to Figure 5, the memory 100 can include a non-volatile memory 110 and a volatile memory 150.

[0092] The non-volatile memory 110 can permanently store at least one piece of data, regardless of the program operation of the battery management device.

[0093] According to one embodiment, the non-volatile memory 110 may include at least one instruction executed by the processor 200 to control the operation of the wireless communication module. For example, the non-volatile memory 110 may be provided as read-only memory (ROM), as described above.

[0094] At least one instruction within the battery management device includes an instruction that controls a virtual machine, which is configured to execute control logic pre-recorded in memory, to execute updated control logic.

[0095] Here, instructions that control the virtual machine to execute the updated control logic may include instructions that, if the updated control logic exists in the external storage area connected to the battery management device, execute a loader to copy the updated control logic and store it in memory, and instructions that cause the virtual machine to parse and execute the updated control logic.

[0096] Furthermore, at least one instruction may further include an instruction to operate a loader to copy pre-recorded control logic from an external storage area and store it in memory, and an instruction to operate a virtual machine to execute the pre-recorded control logic.

[0097] Furthermore, at least one instruction may further include an instruction that, upon receiving a termination signal, stores the updated control logic in external storage and terminates the program.

[0098] On the other hand, the memory may include non-volatile memory for storing at least one processor instruction, and volatile memory for storing pre-recorded control logic and updated control logic.

[0099] In this case, the volatile memory may include a main memory for storing pre-recorded control logic and a backup memory for storing updated control logic.

[0100] On the other hand, at least one instruction may further include, if, before the termination signal is received, any newly updated control logic is stored in the external storage area after the updated control logic, an instruction to copy the newly updated control logic and store it in one of the partitioned areas of the backup memory in memory, and an instruction to operate the virtual machine to execute the newly updated control logic.

[0101] Furthermore, pre-recorded and updated control logic can be generated by a logic generator and compiled into a computer language compatible with the virtual machine.

[0102] On the other hand, the external storage area may include a non-volatile storage device that includes at least one of the following: a hard disk drive (HDD), flash memory, EEPROM, and a portable storage device.

[0103] Furthermore, the control logic generation device can be connected to the battery management device via a wireless or wired network, and the updated control logic can be transmitted to the battery management device.

[0104] On the other hand, the volatile memory 150 can temporarily store pre-recorded control logic and updated control logic.

[0105] According to one embodiment, the volatile memory 150 may include a main memory 151 and a backup memory 155.

[0106] The main memory 151 can temporarily store pre-recorded control logic. More specifically, the main memory 151 may be a space for storing pre-recorded control logic copied from an external storage area by the loader during the initial operation of the battery management device 1300. This allows the battery management device 1300 to execute the control logic pre-recorded in the main memory 151 by a virtual machine (VM) during its initial operation due to initialization. Here, the control logic pre-recorded in the main memory 151 may be the most recently updated control logic executed before the initialization of the battery management device 1300, as described above.

[0107] The backup memory 155 can temporarily store newly updated control logic. More specifically, the backup memory 155 can store updated control logic obtained from the control logic generator 1100 by the loader.

[0108] The backup memory 155 can store at least one updated control logic obtained from the control logic generator 1100 until the end signal of the battery management device 1300 is received, in other words, until the initialization of the battery management device 1300 is performed.

[0109] According to one embodiment, the backup memory 155 can be provided with areas divided to correspond to the number of updated control logics, or it can be provided with a number of areas pre-configured by the user, taking into account the memory capacity. This allows the updated control logics to be sequentially stored in the divided areas of the backup memory 155, even if multiple updated control logics are provided from the control logic generation device 1100 before the battery management device 1300 is initialized. Therefore, the battery management device 1300 according to an embodiment of the present invention can update the software of the battery management device without interrupting the battery system by sequentially storing newly updated control logics in the backup memory 155, regardless of whether initialization is performed or not, and by having the interpreter of the virtual machine (VM) execute the corresponding control logic each time a newly updated control logic is stored.

[0110] The battery management device and method, as well as a battery system including the same, according to embodiments of the present invention have been described above. Below, the battery management method using the processor operation of the battery management device will be described in more detail.

[0111] Figure 6 is a flowchart illustrating a battery management method according to an embodiment of the present invention.

[0112] Referring to Figure 6, the battery management device 1300 can be initially executed by the operation of the processor 200 (S1000).

[0113] The battery management device 1300 can execute a loader. This allows the battery management device 1300 to copy control logic previously recorded in an external storage area and temporarily store it in the main memory 151 using the loader.

[0114] Subsequently, the battery management device 1300 can run a virtual machine (VM). This allows the VM's interpreter to manage the battery by parsing and executing (S2000) the control logic stored in the main memory 151. Here, the control logic may be the most recently updated control logic executed immediately before the initial execution of the battery management device 1300. In other words, the battery management device 1300 can operate with the latest software applied during its initial execution.

[0115] Subsequently, the battery management device 1300 can check the external storage area connected to the battery management device 1300 to confirm whether the updated control logic exists. Here, the external storage area may be a non-volatile storage medium.

[0116] According to one embodiment, the battery management device 1300 can verify whether updated control logic exists in the external storage device 1500, which is physically connected by a port. For example, the external storage device 1500 can be provided in the form of physical hardware such as a hard disk drive (HDD), flash memory, EEPROM, or portable storage device.

[0117] In another embodiment, the battery management device 1300 can verify whether updated control logic exists on an external server or cloud storage connected via a wired or wireless network.

[0118] If updated control logic exists, the battery management device 1300 can execute a loader to store the updated control logic in the backup memory 155 (S3000).

[0119] Subsequently, the virtual machine (VM) in the battery management device 1300 can execute an interpreter to parse and run the updated control logic stored in the backup memory 155 (S4000).

[0120] Subsequently, when the battery management device 1300 receives a termination signal from an external source (S8000), it can store the updated control logic being executed by the virtual machine (VM) in an external storage area (S9000) and terminate the update operation.

[0121] Figure 7 is a flowchart illustrating a battery management method according to an embodiment of the present invention, in which there is a newly updated control logic after the updated control logic.

[0122] Referring to Figure 7, if, after the execution of the updated control logic and before an end signal is received from an external source, the battery management device 1300 can execute a loader to copy the newly updated control logic and store it in an area of ​​the partitioned backup memory 155 that does not contain the currently running control logic (S6000).

[0123] This allows the interpreter of the virtual machine in the battery management device 1300 to parse and execute the newly updated control logic stored in the partitioned backup memory 155 (S7000).

[0124] Subsequently, as shown in Figure 6, when the battery management device 1300 receives a termination signal from an external source (S8000), it can store the updated control logic being executed by the virtual machine (VM) in the external storage area (S9000) and terminate the update operation.

[0125] Referring again to Figure 6, the battery management device 1300 according to the embodiment of the present invention is not limited to what is described therein, and during the execution of the updated control logic by the virtual machine (VM) in the S4000 step, the updated control logic can be stored in an external storage area during the idle time that occurs with each battery diagnostic cycle.

[0126] More specifically, control logic executed by a virtual machine (VM) can generally perform battery diagnostics at a pre-configured interval. In other words, battery diagnostics can be completed within the pre-configured interval. For example, if the pre-configured interval is 1 second, the battery diagnostic period may be 0.4 seconds. In other words, an idle period of 0.6 seconds can occur.

[0127] Therefore, the battery management device 1300 according to an embodiment of the present invention can utilize idle time to store the updated control logic in an external storage area.

[0128] For example, the battery management device 1300 can store the updated control logic in an external storage area during the idle time allocated for each battery diagnostic cycle.

[0129] According to one embodiment, if the battery management device 1300 has finished storing the updated control logic in the external storage area before receiving an termination signal from the outside, it can terminate by omitting the S9000 step.

[0130] According to another embodiment, if the battery management device 1300 has not finished storing the updated control logic in the external storage area until a termination signal is received from the outside, it can complete the storage of the remaining capacity that could not be stored in step S9000.

[0131] On the other hand, if, during the process of storing the updated control logic due to idle time, a newly updated control logic is recognized, as in S5000, the battery management device 1300 can delete the updated control logic that was previously recorded in the external storage area for each idle time.

[0132] After the deletion of the updated control logic is complete, the battery management device 1300 can store the newly updated control logic in the external storage area.

[0133] For example, the battery management device 1300 can store newly updated control logic in an external storage area during the idle time allocated for each battery diagnostic cycle.

[0134] According to one embodiment, if the battery management device 1300 has finished storing the newly updated control logic in the external storage area before receiving an termination signal from the outside, it can terminate by omitting the S9000 step.

[0135] According to another embodiment, if the battery management device 1300 has not finished storing the newly updated control logic in the external storage area until a termination signal is received from the outside, it can complete the storage of the remaining capacity that could not be stored in step S9000.

[0136] Therefore, in the battery management device according to the embodiment of the present invention, the storage time can be shortened by first storing the updated control logic during the idle time that occurs with each battery diagnostic cycle, and then quickly updating the updated control logic to an external storage area when a termination signal is received from an external source.

[0137] The battery management device and method, as well as a battery system including the same, according to embodiments of the present invention, have been described above.

[0138] The battery management device and method according to an embodiment of the present invention, and the battery system including the same, can provide software that enables highly efficient battery operation management by allowing the updated control logic to be executed without interrupting the battery management system, through the real-time recognition and execution of the control logic updated from the control logic generation device by a virtual machine.

[0139] The operation of the method according to the embodiment of the present invention can be embodied as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices on which data that can be read by a computer system is stored. Furthermore, computer-readable recording media can be distributed across networked computer systems, and computer-readable programs or code can be stored and executed in a distributed manner.

[0140] Furthermore, computer-readable recording media can include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions can include not only machine code, such as that produced by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

[0141] Some aspects of the present invention have been described in the context of apparatus, but they can also be described by corresponding methods, where 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 be described by corresponding blocks or items or features of corresponding apparatus. Some or all of the method steps can be carried out by (or using) hardware devices 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 carried out by such devices.

[0142] While preferred embodiments of the present invention have been described above with reference to the present invention, those skilled in the art will understand that the present invention can be modified and altered in various ways without departing from the spirit and scope of the invention as set forth in the following claims. [Explanation of Symbols]

[0143] 1000: Battery System 1100: Control logic generator 1300:Battery management device 1500: External storage device 100: Memory 110: Non-volatile memory 150: Volatile memory 151: Main memory 155: Backup memory 200: Processor 300: Transceiver 400: Input Interface Device 500: Output Interface Device 600: Storage device 700: Bus

Claims

1. A battery management system (BMS), memory, and Includes a processor that executes at least one instruction stored in the memory, The at least one instruction is, A battery management device that includes an instruction to control a virtual machine of the battery management device, which is executing control logic pre-recorded in the memory, to execute updated control logic, without stopping the operation of the battery management device.

2. Instructions that control the virtual machine to execute the updated control logic include: If the updated control logic exists in the external storage area connected to the battery management device, an instruction is given to execute the loader to copy the updated control logic and store it in the memory, and The battery management device according to claim 1, comprising an instruction to operate the virtual machine to parsing and execute the updated control logic.

3. The at least one instruction is, An instruction to operate the loader to copy the control logic previously recorded in the external storage area and store it in the memory, and The battery management device according to claim 1, further comprising instructions for operating the virtual machine to execute the pre-recorded control logic.

4. The at least one instruction is, The battery management device according to claim 1, further comprising an instruction to store the updated control logic in an external storage area and terminate upon receiving a termination signal.

5. The aforementioned memory is A non-volatile memory for storing at least one instruction of the processor, and The battery management device according to claim 2, further comprising a volatile memory for storing the pre-recorded control logic and the updated control logic.

6. The volatile memory is The main memory for storing the previously recorded control logic, and The battery management device according to claim 5, further comprising a backup memory for storing the updated control logic.

7. The at least one instruction is, If, before the termination signal is received, the external storage area stores control logic that has been updated since the previously updated control logic, An instruction to copy the newly updated control logic and store it in one of the partitioned areas of the backup memory in the memory, and The battery management device according to claim 4, further comprising an instruction to operate the virtual machine to execute the newly updated control logic.

8. The previously recorded control logic and the updated control logic are The battery management device according to claim 2, which is generated from a logic generator and compiled into a computer language compatible with the virtual machine.

9. The aforementioned external storage area is The battery management device according to claim 2, which is included in a non-volatile storage device that includes at least one of a hard disk drive (HDD), flash memory, EEPROM, and a mobile storage device.

10. The control logic generation device is The battery management device according to claim 8, which is connected to the battery management device via a wireless or wired network and transmits the updated control logic to the battery management device.

11. A battery management method for a battery management system (BMS) including memory and a processor, A battery management method comprising the step of controlling a virtual machine of the battery management device, which is executing control logic pre-recorded in the memory, to execute updated control logic, without stopping the operation of the battery management device.

12. The step of controlling the virtual machine to execute the updated control logic is: If the updated control logic exists in the external storage area connected to the battery management device, the loader is executed to copy the updated control logic and store it in the memory, and The battery management method according to claim 11, further comprising the step of operating the virtual machine to parsing and execute the updated control logic.

13. The steps include operating a loader to copy the control logic previously recorded in the external storage area and storing it in the memory, and The battery management method according to claim 11, further comprising the step of operating the virtual machine to execute the pre-recorded control logic.

14. The battery management method according to claim 11, further comprising the step of storing the updated control logic in an external storage area and terminating when a termination signal is received.

15. The aforementioned memory is A non-volatile memory for storing at least one instruction of the processor, and The battery management method according to claim 12, further comprising a volatile memory for storing the pre-recorded control logic and the updated control logic.

16. The volatile memory is The main memory that stores the previously recorded control logic, The battery management method according to claim 15, further comprising a backup memory for storing the updated control logic.

17. If, before the termination signal is received, the external storage area stores control logic that has been updated since the previously updated control logic, The steps include: copying the newly updated control logic and storing it in one of the partitioned areas of the backup memory within the memory; The battery management method according to claim 14, further comprising the step of operating the virtual machine to execute the newly updated control logic.

18. The previously recorded control logic and the updated control logic are The battery management method according to claim 12, wherein the control logic is generated from a logic generator and compiled into a computer language compatible with the virtual machine.

19. The aforementioned external storage area is The battery management method according to claim 12, which is included in a non-volatile storage device that includes at least one of a hard disk drive (HDD), flash memory, EEPROM, and a portable storage device.

20. The control logic generation device is The battery management method according to claim 18, wherein the battery management device is connected to the battery management device via a wireless or wired network and the updated control logic is transmitted to the battery management device.

21. A battery management system, A logic generator that generates and compiles updated control logic, and A battery system comprising a battery management device including memory and a processor, the battery management device controlling a virtual machine of the battery management device, which is executing control logic pre-recorded in the memory, to execute the updated control logic without stopping the operation of the battery management device.

22. The aforementioned battery management device, If the updated control logic exists in the external storage area connected to the battery management device, the loader is executed to copy the updated control logic and store it in the memory. The battery system according to claim 21, wherein the virtual machine is operated to parsing and execute the updated control logic.

23. The aforementioned battery management device, The loader is operated to copy the control logic previously recorded in the external storage area and store it in the memory. The battery system according to claim 21, further comprising operating the virtual machine to execute the pre-recorded control logic.

24. The aforementioned battery management device, The battery system according to claim 21, further comprising storing the updated control logic in an external storage area and terminating upon receiving a termination signal.

25. The aforementioned battery management device, If, before the termination signal is received, the external storage area stores control logic that has been updated since the previously updated control logic, The newly updated control logic is copied and stored in one of the partitioned areas of the backup memory within the memory. The battery system according to claim 24, further comprising operating the virtual machine to execute the newly updated control logic.

26. The control logic generation device is The battery system according to claim 22, wherein the pre-recorded control logic and the updated control logic are compiled into a computer language compatible with the virtual machine.

27. The aforementioned external storage area is The battery system according to claim 24, which is included in a non-volatile storage device that includes at least one of a hard disk drive (HDD), flash memory, EEPROM, and a portable storage device.

28. The control logic generation device is The battery system according to claim 21, which is connected to the battery management device via a wireless or wired network and transmits the updated control logic to the battery management device.

29. A computer program that, when executed on the processor of the battery management device, causes the battery management device to execute the battery management method described in any one of claims 11 to 20.