WO2021101012A1

WO2021101012A1 - Battery management system and control method thereof

Info

Publication number: WO2021101012A1
Application number: PCT/KR2020/009469
Authority: WO
Inventors: 권정현; 박찬하
Original assignee: 주식회사 엘지에너지솔루션
Priority date: 2019-11-19
Filing date: 2020-07-17
Publication date: 2021-05-27
Also published as: JP2022532516A; JP7206553B2; CN113950669A; KR20210061138A; US20220237029A1; EP3961392A4; EP3961392A1

Abstract

A battery management system according to the present disclosure corresponds to a system for performing an individually configured task by each of multiple battery management systems, and transmitting a result of the performed task to a master battery management system via wireless communication. The battery management system comprises: a task information storage unit including a list of tasks performed by multiple battery management systems, a performance time of each task included in the list of tasks, a performance period and work priorities, and communication priorities between the multiple battery management systems; a schedule determination unit for determining a work schedule on the basis of data stored in the task information storage unit; and a priority change unit for adjusting work priorities of a task on the basis of the work schedule determined by the schedule determination unit, wherein the schedule determination unit adjusts the work schedule according the adjusted work priorities. The present disclosure enables effective use of limited resources by providing the battery management system.

Description

Battery management system and control method thereof

Mutual citation with related applications

The present invention claims the benefit of priority based on Korean Patent Application No. 10-2019-0148979 filed on November 19, 2019, and includes all the contents disclosed in the documents of the Korean patent application as part of this specification.

Technical field

Embodiments of the present invention relate to a battery management system and a control method thereof.

Along with the generalization of portable electronic devices such as smartphones and tablets, research and development on secondary batteries capable of charging and discharging are being actively conducted with the spread of electric vehicles and energy storage devices. Among secondary batteries, lithium-ion batteries in particular have the advantage of having a much higher energy density compared to conventional Ni/Cd batteries and Ni/MH batteries.In addition, lithium-ion batteries can be manufactured in a small size and light weight, so they can be used as power sources for mobile devices. do. In addition, lithium-ion batteries are attracting attention as a next-generation energy storage medium as the range of use of lithium-ion batteries has been expanded as a power source for electric vehicles.

A secondary battery such as a lithium-ion battery is in the form of a battery module including a cell module in which a plurality of battery cells are connected in series and/or parallel, and a battery management system (BMS) that controls the charging and discharging of the cell module. Is used. In addition, a plurality of battery modules may be used as a combined battery pack according to an output specification required by an object to which the battery is mounted. In addition, a battery management system for managing the entire battery pack may be additionally provided as a master battery management system.

A battery system composed of a plurality of battery modules may include a master battery management system and a plurality of slave battery management systems. The master battery management system may control and manage the operation of a plurality of slave battery management systems, and may communicate with an upper system. The master battery management system and the plurality of slave battery management systems wirelessly transmit and receive signals. Therefore, a lot of research is also needed to efficiently and stably perform wireless communication between battery management systems.

The present invention has been made in view of such a situation, and an object of the present invention is to provide a method in which each battery management system can efficiently use limited resources in a battery system in which a plurality of battery management systems communicate wirelessly.

In order to solve the above technical problem, according to an aspect of the embodiments of the present disclosure, each of a plurality of battery management systems performs individually set tasks, and the performed task result is transmitted to the master battery management system through wireless communication. As a battery management system in a transmitting system, a task list performed by each of a plurality of battery management systems, execution time, execution cycle and task priority of each task included in the task list, and between a plurality of battery management systems Task information storage unit including the communication priority of the; A schedule determination unit that determines a work schedule based on data stored in the task information storage unit; And a priority change unit that adjusts the work priority of the task based on the work schedule determined by the schedule determination unit, wherein the schedule determination unit provides a battery management system that adjusts the work schedule according to the adjusted work priority. .

In order to solve the above technical problem, according to another aspect of the embodiments of the present disclosure, a task list performed by each of a plurality of battery management systems, execution time of each task included in the task list, execution cycle and task priority Storing the priority and communication priority between the plurality of battery management systems; Determining a work schedule based on the stored data; Adjusting the task priority of the task based on the determined task schedule; And adjusting the work schedule according to the adjusted work priority.

According to the battery management system and a control method thereof as described above, it is possible to efficiently use limited resources. In addition, tasks that have not been previously performed can be performed without changing hardware such as a microcomputer.

1 is a block diagram schematically showing a battery system according to an embodiment of the present invention.

2 is a block diagram of a battery pack including a battery management system according to an embodiment of the present invention.

3 is a functional block diagram showing the configuration of a battery management system according to an embodiment of the present invention.

4 is a functional block diagram illustrating a task scheduler in a battery management system according to an embodiment of the present invention.

5 is a flowchart showing the operation of the battery management system according to an embodiment of the present invention.

6 is a diagram illustrating a task time table according to an embodiment of the present invention.

7 is a diagram illustrating a communication priority table according to an embodiment of the present invention.

8 is a flowchart illustrating a task scheduling operation of the battery management system according to an embodiment of the present invention.

9 is a timing diagram illustrating an operation sequence of a task according to FIGS. 6 and 7.

10 is a timing diagram illustrating an operation sequence of a task whose priority has been changed by the battery management system according to an embodiment of the present invention.

11 is a diagram illustrating a task time table according to another embodiment of the present invention.

12 is a diagram illustrating a communication priority table according to another embodiment of the present invention.

13 is a timing diagram illustrating an operation sequence of a task according to FIGS. 11 and 12.

14 is a flowchart illustrating a method of changing a priority according to an embodiment of the present invention.

15 is a flowchart illustrating an example of a method of changing a priority according to an embodiment of the present invention.

16 is a timing diagram illustrating an operation sequence of a task whose priority has been changed by the priority change method according to FIG. 15.

17 is a flowchart illustrating another example of a method of changing a priority according to an embodiment of the present invention.

18 is a timing diagram illustrating an operation sequence of a task whose priority has been changed by the priority change method according to FIG. 17.

19 is a diagram illustrating a task time table according to another embodiment.

20 is a timing diagram illustrating an operation sequence of a task according to FIGS. 19 and 12.

21 is a flowchart illustrating a method of changing a priority according to another embodiment of the present invention.

22 is a flowchart illustrating an example of a method of changing the priority order in FIG. 21.

FIG. 23 is a timing diagram illustrating an operation sequence of a task whose priority has been changed by the priority change method according to FIG. 22.

24 is a hardware configuration diagram of a battery management system according to an embodiment of the present invention.

Hereinafter, various embodiments of the present invention will be described in detail with reference to the accompanying drawings. In this document, the same reference numerals are used for the same components in the drawings, and duplicate descriptions of the same components are omitted.

For the various embodiments of the present invention disclosed in this document, specific structural or functional descriptions have been exemplified only for the purpose of describing the embodiments of the present invention, and various embodiments of the present invention may be implemented in various forms. And should not be construed as being limited to the embodiments described in this document.

Expressions such as "first", "second", "first", or "second" used in various embodiments may modify various elements regardless of their order and/or importance, and the corresponding elements Not limited. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may be renamed to a first component.

Terms used in this document are only used to describe a specific embodiment, and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions unless the context clearly indicates otherwise.

Referring to FIG. 1, the battery system according to the present invention includes a cell module 12 including a plurality of battery cells, a battery management system (hereinafter referred to as'BMS') 14, and a switching unit 16. It may include a battery module 10 including a and a master BMS 20 for controlling and managing the battery module 10.

The cell module 12 includes one or more battery cells capable of being charged and discharged. The battery cell may be a lithium ion (Li-ion) battery, a lithium ion polymer (Li-ion polymer) battery, a nickel cadmium (Ni-Cd) battery, a nickel hydrogen (Ni-MH) battery, and the like, but is not limited thereto.

The BMS 14 may control the operation of the switching unit 16 to control charging and discharging of the cell module 12. In addition, the BMS 14 may monitor the voltage, current, temperature, etc. of each battery cell included in the cell module 12 and/or the cell module 12. In addition, for monitoring by the BMS 14, a sensor or various measurement modules, not shown, may be additionally installed at an arbitrary location such as the cell module 12, the charge/discharge path, or the cell module 12. The BMS 14 may calculate a parameter indicating the state of the cell module 12, for example, SOC or SOH, based on measured values such as voltage, current, and temperature monitored.

The BMS 14 controls and manages the overall operation of the battery module 10. To this end, the BMS 14 may include various configurations such as a microcomputer as a controller that executes a program and controls the overall operation of the BMS 14, an input/output device such as a sensor or a measuring means, and other peripheral circuits.

The BMS 14 is capable of wireless communication with the master BMS 20, and can transmit various monitored measured values such as voltage, current, and temperature, or calculated values such as SOC or SOH, to the master BMS 20. In particular, the BMS 14 according to the present invention determines a work schedule, which is an execution order of tasks to be performed in consideration of various conditions. In this case, various conditions may include priority and execution time of tasks, communication time required to transmit data to the master BMS 20 or other BMS, communication priority between other BMSs, and the like. Determination of the work schedule and its change will be discussed in detail below.

The switching unit 16 is a semiconductor switching device for controlling current flow for charging or discharging of the cell module 12, and, for example, at least one MOSFET may be used.

The battery module 10 may be provided in the form of a plurality of battery packs 1 according to the specifications of the device to be mounted. In addition, the battery pack 1 may include a master BMS 20 that controls and manages the battery module 10. The master BMS 20 may receive various data from the BMS 14 included in each battery module 10. The master BMS 20 may transmit a signal for controlling them to the BMS 14 included in each battery module 10.

In addition, the master BMS 20 may not have a battery module 10 separately managed. Alternatively, the master BMS 20 may be one of the BMSs 14 included in the plurality of battery modules 10, respectively, serving as a master communication device.

Meanwhile, the master BMS 20 may be communicatively connected with an external host controller 2. That is, the master BMS 20 of the battery pack 1 transmits various data on the battery pack 1 to the host controller 2, and a control signal related to the operation of the battery pack 1 from the host controller 2 Can be received. The host controller 2 may be a vehicle controller for controlling the operation of the vehicle when the battery pack 1 is mounted on the electric vehicle.

Referring to FIG. 2, a plurality of battery modules 10-1 to 10-N, where N is an integer greater than or equal to 1, and a master BMS 20 for controlling and managing them are included in the battery pack 1. Each of the plurality of battery modules 10-1 to 10-N includes a corresponding BMS 14-1 to 14-N.

The master BMS 20 and each of the BMSs 14-1 to 14-N communicate wirelessly with each other.

The master BMS 20 is a battery module controller and may be responsible for communication with the host controller 2. However, in the case of a small system without a host controller, the master BMS 20 may be operated in an independent form without a host controller.

The master BMS 20 performs various tasks that the BMS needs to perform by using various information that can be obtained from sensors such as the current voltage, temperature, and humidity of the battery pack 1 or the battery module 10. Various tasks may include an operation of acquiring various types of information from a sensor.

BMS(14-1~14-N) is a cell module controller that performs voltage measurement, module voltage measurement, temperature measurement, humidity measurement, resistance measurement, etc. for the cell module 12. It converts the information provided from the sensor by measurement to fit the battery system and transmits it to the master BMS 20, which is an upper control circuit.

In addition, the BMS 14-1 to 14-N may perform the corresponding operation according to a command for performing various operations such as cell balancing transmitted from the master BMS 20 or the host controller 2.

As described above, the communication nodes 14-1 to 14-N and the master BMS 20, which are communication nodes wirelessly connected in the system, share a task table with each other, and some tasks may be performed by synchronizing time. However, when the task is synchronized and executed in this way, IDLE time occurs in individual nodes due to reasons such as waiting for communication. Eventually, each node, BMS (14-1 to 14-N) and master BMS (20), cannot efficiently utilize their own resources, and there is a possibility that the work efficiency is lower than when the execution time of tasks is not synchronized. . In addition, if the execution times of the tasks are not synchronized, all tasks that could be processed may not be processed within a predetermined period.

Hereinafter, embodiments of the present invention capable of reconsidering work efficiency by adding a work scheduler to the BMS 14-1 to 14-N and the master BMS 20 will be described in order to solve the above problems. Specifically, a plurality of BMSs (14-1 to 14-N) and each of the master BMS 20 perform individually set tasks, and transmit the result of the performed task to the master BMS 20 through wireless communication. The configuration and operation of the BMS 14-1 to 14-N and the master BMS 20 will be described.

When designing a wireless network protocol, the tasks of a system using that protocol are already defined. In addition, due to the nature of the embedded system, all tasks that are set must be performed within a set time and must not exceed the set maximum time.

In addition, the operation method of the microprocessor (MCU, etc.) takes a sequential operation method according to the priority between tasks. If this order is determined at design time, it is not modified in Runtime. And in the final determined work schedule, an idle time occurs. Due to the performance of the microprocessor, when tasks are sequentially performed without synchronization of tasks, all tasks can be performed within a predetermined time. However, when performing tasks by synchronization, there are cases in which all tasks cannot be performed within a predetermined time.

Embodiments of the present invention have been made in view of this situation.

3, the BMS 100 according to this embodiment includes a communication unit 110, a storage unit 120, a schedule determination unit 130, a priority change unit 140, a task execution unit 150, and synchronization. A unit 160 and an error calculation unit 170 may be included. Here, the BMS 100 may be a slave node BMS 14 or a master node master BMS 20. Hereinafter, both the slave BMS 14 and the master BMS 20 are collectively referred to as the BMS 100.

The communication unit 110 transmits and receives data and various signals to and from other BMS 100. That is, the communication unit 110 performs a function for communication with other slave BMS 14 and master BMS 20. The communication unit 110 may use various protocols such as wireless CAN communication, WIFI, Bluetooth, Zigbee, and other slave BMS 14 and master BMS 20.

The communication unit 110 transmits the task list to be performed by itself to the other slave BMS 14 and the master BMS 20, the execution time of each task included in the task list, the execution period, and the task priority, and the task time table between them. You can share. In addition, the communication unit 110 may share a communication priority table indicating communication priorities between the other slave BMS 14 and the master BMS 20. That is, the communication unit 110 may transmit data related to the task time table and the communication priority table to the other BMS 100. Likewise, the communication unit 110 may receive data on a task time table and a communication priority table from another BMS 100.

In addition, the communication unit 110 may transmit the result of the task performed by itself to the master BMS 20 or the like. In this case, when the priority of the task and the task schedule according to the task priority change by the priority changer 140 when performing the task, the change may be transmitted to another BMS 100 to share the change. Likewise, the communication unit 110 may receive a change in the priority of the task and the task schedule from the other BMS (100).

The communication unit 110 may transmit signals and data in a multicast or broadcast method. For example, the communication unit 110 may transmit the work schedule adjusted by the schedule determination unit 130 to another BMS 100 in a multicast or broadcast manner.

The communication unit 110 may perform communication for sharing a task time table and a communication priority table when a certain condition is satisfied. For example, when a system of a device equipped with the battery pack 1 wakes up, communication for sharing a task time table and a communication priority table may be performed. If the device in which the battery pack 1 is mounted is an electric vehicle, the above condition may be the case of starting the engine. Alternatively, the communication unit 110 may periodically perform communication for sharing the task time table and the communication priority table.

Additionally, the communication unit 110 may receive a task execution start signal and a completion signal for synchronization when performing a task with other BMSs 100.

The storage unit 120 stores various programs required for the operation of the BMS 100 and various data generated during the operation of the BMS 100. The storage unit 120 stores a task time table including a task list performed by each of the plurality of BMSs 100 in the battery pack 1, an execution time of each task included in the task list, an execution cycle, and a task priority. I can. The storage unit 120 may store a communication priority table indicating communication priorities between a plurality of BMSs 100 in the battery pack 1. Additionally, the storage unit 120 may set tasks to be performed in synchronization with the other BMS 100 in the task list. In addition, the storage unit 120, when receiving the adjusted work schedule from the other BMS 100 through the communication unit 110, may update the stored contents such as the task time table and the communication priority table with the adjusted work schedule. . That is, the storage unit 120 functions as a task information storage unit.

The schedule determination unit 130 determines a work schedule based on data stored in the storage unit 120. Specifically, the schedule determination unit 130 determines a work schedule based on the contents of the task time table and the communication priority table, which are data stored in the task information storage unit. The schedule determination unit 130 also determines a work schedule in consideration of setting information on tasks to be performed in synchronization with the other BMS 100.

The task schedule means that each task is executed in what order, and when each task to be executed starts and when it ends.

The schedule determination unit 130 adjusts the work schedule based on the adjusted priority when the priority change occurs in some tasks by the priority change unit 140.

The priority change unit 140 adjusts the work priority of the task based on the work schedule determined by the schedule determination unit 130.

As an example, if there is a subordinate task that can be performed during the waiting time among the work schedule determined by the schedule determination unit 130, the priority change unit 140 determines the task priority of the subordinate task immediately before the waiting time. The priority of the task to be performed is adjusted next. The waiting time may mean a period after a specific task is performed and before the result of the corresponding task is transmitted to the other BMS 100. The waiting time may mean a period in which the processor utilization rate of the corresponding BMS 100 is less than or equal to a reference value.

The priority change unit 140 compares the length of the waiting time among the work schedules determined by the schedule determination unit 130 with execution times of tasks performed after the waiting time. The priority changer 140 may perform a comparison of the waiting time and the execution time for tasks stored in the task queue 125 to be described later. Alternatively, the priority changer 140 may compare the waiting time and the execution time based on tasks included in the entire determined work schedule.

In addition, the priority changing unit 140 adjusts the priority so that a task having an execution time shorter than the length of the waiting time as a result of the comparison is executed during the waiting time. At this time, as an example, when there are a plurality of tasks having an execution period shorter than the length of the waiting time, the priority changer 140 may adjust the priority of the task having the highest priority among the corresponding tasks. . Alternatively, as another example, when there are a plurality of tasks having an execution period shorter than the length of the waiting time, the priority changer 140 may adjust the priority of a task having the longest execution period among the corresponding tasks.

In this way, when the priority of the task and the task schedule are adjusted by the priority change unit 140, the communication unit 110 can transmit the change to another BMS 100 to share the change. have.

The task execution unit 150 performs tasks to be performed by itself according to the task schedule determined by the schedule determination unit 130. When a task to be performed in synchronization with another BMS 100 is included, the task execution unit 150 performs the task synchronously. For example, for synchronization, the task execution unit 150 performs each task according to the start time calculated by the synchronization unit 160 in relation to the execution start time of each task. Accordingly, it is possible to synchronize the business execution time with the other BMS 100 performing the same task.

The synchronization unit 160 calculates the execution start time of a specific task by using a specific task execution start signal, a completion signal, and a task time table received from the communication unit 110. In addition, the synchronization unit 160 synchronizes the task execution time between each BMS 100 through the calculated execution start time.

The error calculation unit 170 calculates an error using a reception time of a start signal or a completion signal of a specific task received from the communication unit 110 and a task time table. For example, an error is calculated by using the difference between the start signal reception time and the completion signal reception time of a specific task and the execution time of a specific task on the task time table, and provides the error to the synchronization unit 160. When calculating the execution time of the first task, the synchronization unit 160 may reflect the calculated error.

By determining a task schedule with the above configuration and performing an operation of changing the priority of a task on the determined task schedule, the BMS 100 can efficiently utilize its own resources.

Hereinafter, a function of determining a work schedule and adjusting priorities will be described in more detail.

4 is a functional block diagram illustrating a task scheduler 200 in a battery management system according to an embodiment of the present invention.

The task scheduler 200 refers to a function of determining a task schedule and adjusting priorities. The task scheduler 200 may include a task time table 121, a communication priority table 123, a task queue 125, and a priority change unit 140.

In the task time table 121, as described above, a list of tasks to be performed by each BMS 100 as a communication node, their order, and execution time and (if necessary) communication time of each task, and execution The cycle is saved.

The communication priority table 123 stores communication priorities between the BMSs 100 performing the corresponding task in relation to a task requiring communication. The communication priority may be information allocated by the master BMS 20 when each node first joins the wireless communication network.

Based on the task time table 121 and the communication priority table 123, the task scheduler knows in advance a list of tasks to be performed by each BMS 100 as a communication node, their order, and execution timing. At this time, the priority and order of execution of the task are determined, and the execution time is almost constant. In addition, tasks generally have a structure that is repeatedly performed at a specific time (period).

The task queue 125 identifies a task to be performed based on the work schedule determined by the schedule determination unit 130 by using information held by the work scheduler. Then, the tasks to be performed are sequentially called and stored in the task queue 125.

As described above, the priority change unit 140 may adjust the priority of the task according to a predetermined criterion. The priority change unit 140 may adjust the priority itself recorded in the task time table. Alternatively, the priority changer 140 may change the order of tasks in the task queue 125 by adjusting the priority of tasks among tasks included in the task queue 125 based on the determined task schedule. That is, among tasks excluding a task having the highest priority (a task currently being executed) among tasks included in the task queue 125, the priority of a task having an execution time shorter than the waiting time may be changed. When the execution of the task whose priority has been changed is completed, the priority change unit 140 may change the priority of the task to the original priority again.

Referring to FIG. 5, first, the BMS 100 shares a task time table and a communication priority table with other BMSs (S10). That is, data necessary for creating a task time table and a communication priority table are transmitted and received to another BMS 100 through the communication unit 110.

The BMS 100 updates the task time table and the communication priority table by including the task time table and the communication priority table received from another BMS (S11). That is, the BMS 100 generates a final task time table 121 and a communication priority table 123 in consideration of both data of itself and other BMSs. That is, in the storage unit 120 of the BMS 100, a list of tasks performed by each of the plurality of BMSs 100, the execution time of each task included in the task list, execution period and task priority, and a plurality of BMSs ( Communication priorities between 100) may be stored in the form of a task time table 121 and a communication priority table 123.

Then, a work schedule is determined based on the updated tables (S12). That is, the work schedule is determined based on the data stored in the storage unit 120.

6 and 7 illustrate a task time table 121 and a communication priority table 123 according to an embodiment of the present invention stored in the storage unit 120 based on the method described with reference to FIG. 5.

In this example, a master BMS 20 as a master node and BMS 14-1 to 14-3 as slave nodes are included as communication nodes in a wireless communication network. In addition, the task time table 121 may include a task list of each node, a priority among tasks included in the task list, execution time and communication time of each task, and the like. In addition, the total execution time, which is the sum of the work execution time and the total communication time, and the period of each task may be included. The communication priority table 123 may include, for each task, communication priority between the BMSs 100 performing the corresponding task in relation to a task requiring communication.

6, the master BMS 20 performs tasks A, B, and C, and BMS#1 14-1 performs tasks A, B, and E. BMS#2 (14-2) performs tasks A, B, and D, and BMS#3 (14-3) performs tasks A, E, and F.

And according to FIG. 7, for task A, communication priority is given in the order of BMS#1 -> BMS#2 -> BMS#3 -> master BMS. For task B, communication priority is given in the order of BMS#1 -> BMS#2 -> Master BMS.

Referring to FIG. 8, when the task time table 121 and the communication priority table 123 are generated and stored as described in FIG. 5, a task schedule is determined by the schedule determination unit 130. Further, the tasks to be performed are sequentially stored in the task queue 125 based on the determined work schedule (S20).

After that, it is determined whether all the tasks stored in the task queue 125 can be processed within a predetermined time, that is, a period (S21). If all tasks can be processed within a predetermined time (Yes in S21), the tasks are processed in the order of the task queue (S23). That is, according to the determined work schedule, tasks are processed without changing the priority.

On the other hand, if all tasks cannot be processed within a predetermined time (No in S21), the priority is changed (S22). After that, the order of the task queue is changed based on the changed priority, and the tasks are processed in order according to the order of the changed task queue (S23).

That is, if tasks satisfy a predetermined condition based on the determined work schedule, the task priority of the task is adjusted, and the task schedule is adjusted according to the adjusted task priority.

9 is a timing diagram illustrating an operation sequence of a task based on the task time table 121 and the communication priority table 123 according to FIGS. 6 and 7. 9 may be a schematic diagram of a state of a task queue while including a communication time and a waiting period between tasks.

Referring to FIG. 9, A to F indicate a period in which each task is performed. 1 to 3 denote a communication period in which each node transmits data to the master BMS 20, and Chinese character'up' denotes a communication period in which the master BMS 20 transmits data to the host controller 2. Hatching marks indicate waiting time.

The master BMS 20 performs task A in synchronization with other nodes for 0 to 30 ms. Thereafter, for 30 to 45 ms, data such as result information for task A are sequentially received from BMS#1 (14-1) to BMS#3. In addition, finally, the master BMS 20 transmits the data for task A to the host controller for 45 to 50 ms. Likewise, the master BMS 20 sequentially performs execution and communication for task B, and is in a standby state for 80 to 100 ms after task C is executed.

BMS#1(14-1) performs task A in synchronization with other nodes for 0~30ms. After that, data such as result information for task A is transmitted to the master BMS 20 for 30 to 35 ms. It enters the standby state for 35~50ms, and executes Task B in synchronization for 50~60ms again. After task B is performed, data such as result information for task C is transmitted to the master BMS 20 for 60 to 65 ms. Finally, task E is executed for 65~85ms, and it is in a standby state for the rest of the period.

BMS#2(14-2) performs task A in synchronization with other nodes for 0~30ms. After that, it becomes a standby state for 30~35ms, and data such as result information for task A is transmitted to the master BMS 20 for 35~40ms. It becomes the standby state again for 40~50ms, and executes task B synchronously for 50~60ms. After task B is executed, it becomes a standby state for 60~65ms, and data such as result information for task C is transmitted to the master BMS 20 for 65~70ms. Finally, Task D is executed for 70~75ms, and it is in a standby state for the rest of the period.

Finally, BMS#3(14-3) also performs task A in synchronization with other nodes for 0~30ms. After that, it becomes a standby state for 30~40ms, and data such as result information for task A is transmitted to the master BMS 20 for 40~45ms. Since BMS#3(14-3) does not include task B, it executes task E for 45~65ms, and then executes task F for 65~80ms. Finally, it is in a standby state for the rest of the period, 80~100ms.

As can be seen in FIG. 9, in the case of the task schedule based on the task time table 121 and the communication priority table 123 according to FIGS. 6 and 7, there is no problem in performing all schedules within a period of 100 ms, which is a predetermined period. .

However, if necessary, it may be desirable to change the priority of tasks for efficient operation of a microprocessor or the like. 10 is a timing diagram illustrating an operation sequence of a task whose priority has been changed by the battery management system according to an embodiment of the present invention.

As can be seen from the task time table 121 and the communication priority table 123 of FIGS. 6 and 7, the task D of BMS#2 14-2 does not need to be performed in synchronization with other nodes. In addition, BMS#2 (14-2) has a waiting time between 30 and 35 ms, as can be seen in FIG. 9. Accordingly, as can be seen from the timing diagram of BMS#2 14-2 of FIG. 10, the priority may be adjusted to precede the priority of task B so that task D can be performed at a waiting time between 30 and 35 ms. . To this end, the priority of task D in the task queue may be temporarily adjusted to precede the priority of task B, and the priority may be readjusted back to its original state after completion of the tasks. Alternatively, the table itself may be updated so that the priority of task D is prior to the priority of task B in the task time table 121.

11 and 12 are diagrams illustrating a task time table 121 and a communication priority table 123 according to another embodiment of the present invention. In this embodiment, all nodes include both task A and task B, and are set to perform them in synchronization.

11, the master BMS 20 performs tasks A, B, and C, and BMS#1 14-1 performs tasks A, B, F, G, and H. BMS#2 (14-2) and BMS#3 (14-3) perform tasks A, B, D, and E, respectively.

And, according to FIG. 12, for both tasks A and B, communication priority is given in the order of BMS#1 -> BMS#2 -> BMS#3 -> master BMS.

Hereinafter, a method of adjusting a task priority and a task schedule based on the tables of FIGS. 11 and 12 will be described.

Referring to FIG. 13, it can be seen that BMS#1 (14-1) and BMS#3 (14-3) do not complete all tasks within a predetermined period (for example, a period of 100 ms). That is, task H and task E exceed 100ms and are terminated. This is a situation in which an error has occurred in the battery system, and conventionally, some tasks have to be removed to solve this problem. Alternatively, in order to solve this problem, the task time table 121 and the communication priority table 123 had to be completely modified.

However, in the embodiments of the present invention, the above problem can be solved in the following manner.

14 is a flowchart illustrating a method of changing a priority according to an embodiment of the present invention. This operation corresponds to the detailed operation of the priority change described in S22 of FIG. 8.

Referring to FIG. 14, first, a waiting time on a determined work schedule is calculated (S100). This may be a portion indicated by hatching in FIG. 13. Then, the waiting time and the execution time of the tasks in the task queue are compared (S101).

For example, as can be seen in FIG. 13, in the case of BMS#1(14-1), there is no need to perform synchronously among tasks that are 15ms, which is a waiting time of 35 to 50ms, and tasks after the waiting time. Compare the execution times of tasks F, G and H. In the case of BMS#3(14-3), a task D that does not need to be executed synchronously among the waiting time of 10ms between 40~50ms, 5ms between 55~60ms, 10ms between 70~80ms and tasks after the waiting time. And the running times of E are compared.

Among the compared task execution times, it is determined whether there is a task less than the waiting time (S102), and if it is determined that there is a task less than the waiting time, the priority of the corresponding task is changed (S103).

That is, if there is a subordinate task that can be executed during the waiting time among the determined work schedule, the task priority of the subordinate task can be adjusted to the next priority of the task executed immediately before the waiting time.

On the other hand, if it is determined that there is no task less than the waiting time, it is determined that recovery of the error is impossible, and an error is notified to the host controller 2 or the like (S104).

15 is a flowchart illustrating an example of a method of changing a priority according to an embodiment of the present invention. This operation corresponds to the detailed operation of the priority change described in S103 of FIG. 15. 16 is a timing diagram illustrating an operation sequence of a task whose priority has been changed by the priority change method according to FIG. 15.

Referring to FIG. 15, first, it is determined whether there are a plurality of tasks having an execution time shorter than the length of the waiting time (S200). If there are a plurality of tasks having an execution period shorter than the length of the waiting time (Yes in S200), the priority of the task with the highest priority among the tasks is adjusted.

As shown in FIG. 16, the BMS#1 (14-1) has a shorter execution time than the 15ms long waiting time for tasks F, G, and H for 45 to 60ms. And task F has the highest priority. Therefore, first, adjust the priority so that task F can be executed in the waiting time of 45~50ms. After that, the waiting time of 10ms length for 50~60ms remains, and since task H has 10ms execution time, the priority is adjusted so that task H can be executed during the waiting time. In addition, with the adjustment of the task priorities, Task G can perform the task for a period of time between 75 and 90 ms with a schedule that is 5 ms ahead of the previous one.

Likewise, in BMS#3(14-3), task priority is first adjusted so that task D with high priority can be executed during waiting time of 40~50ms, and task E will be executed during waiting time of 70~80ms. Task priorities are adjusted to ensure that.

In addition, BMS#2 (14-2) can process all tasks within a predetermined time, but can adjust the task priority of task D for efficient operation of the microprocessor. However, in the case of Task E, only the work schedule is adjusted. That is, in the case of task E, the task priority is not adjusted, only the start and end timings are adjusted.

On the other hand, if there is one task with an execution period shorter than the length of the waiting time (No in S200), the priority of the task can be adjusted.

17 is a flowchart illustrating another example of a method of changing a priority according to an embodiment of the present invention. This operation corresponds to another detailed operation of the priority change described in S103 of FIG. 15. 18 is a timing diagram illustrating an operation sequence of a task whose priority has been changed by the priority change method according to FIG. 17.

Referring to FIG. 17, S300 and S302 are the same as S200 and S202 of FIG. 15.

On the other hand, when there are a plurality of tasks having an execution period shorter than the length of the waiting time, in the present embodiment, the priority of the task having the longest execution period among the corresponding tasks is adjusted (S201).

As shown in FIG. 18, the BMS#1 (14-1) has an execution time shorter than the 15ms long waiting time for tasks F, G, and H for 45 to 60ms. And task G has the longest execution time. Therefore, first, adjust the priority so that task G can be executed in the waiting time of 45~50ms. After that, the waiting time for 80~95ms, which is the time that the original task G executes the task, remains, and the task schedule is adjusted so that the task H can be executed for 80~90ms. However, in the case of Task H, task priorities are not adjusted, only start and end timings are adjusted.

In the case of BMS#2 (14-2) and BMS#3 (14-3), task D and task E after the waiting time have the same execution time, so the task priority and schedule are Is adjusted.

As described above, by making it possible to arbitrarily adjust the priority among tasks performed after that during the waiting time, it is possible to process tasks that were not possible to process all of the tasks within a predetermined period in the past, thus enabling efficient hardware operation. do.

19 is a diagram illustrating a task time table according to another embodiment.

19, the master BMS 20 performs tasks A, B, and C, and BMS#1 14-1 performs tasks A, B, F, and G. BMS#2 (14-2) and BMS#3 (14-3) perform tasks A, B, D, and E, respectively. In this embodiment, the communication priority is as shown in FIG. 12.

Referring to FIG. 20, it can be seen that BMS#1 (14-1) and BMS#3 (14-3) do not complete all tasks within a predetermined period (for example, a period of 100 ms). That is, task G and task E exceed 100 ms and are terminated. This is a situation in which an error has occurred in the battery system, and conventionally, some tasks have to be removed to solve this problem. Alternatively, in order to solve this problem, the task time table 121 and the communication priority table 123 had to be completely modified.

However, in the embodiments of the present invention, the above problem can be solved in a manner different from the method described above, as follows.

21 is a flowchart illustrating a method of changing a priority according to another embodiment of the present invention. This operation corresponds to another detailed operation of the priority change described in S22 of FIG. 8.

Referring to FIG. 21, the operations of S400 to S403 are the same as the operations of S100 to S103 of FIG. 14. That is, if all tasks can be processed within a period, the task is executed according to the determined work schedule. In addition, if all tasks cannot be processed within a period, and if there is a task having an execution time shorter than the waiting time, the priority of the task is adjusted so that all tasks can be processed within the period.

On the other hand, if there is no task having an execution time shorter than the waiting time (No in S402), it is determined whether the task can be divided (S404),

Referring to FIG. 22, since a task having an execution time shorter than the waiting time is not included in the task queue, another method must be devised to process the tasks within a period. To this end, it is determined whether there is a task that can be divided and executed among the tasks included in the task queue (S500).

If there is a task that can be divided and executed (Yes in S500), the task is divided into a plurality of subtasks. In this case, the execution period of the at least one sub-task is set to be less than or equal to the waiting time (S501).

After that, the priority of the divided subtasks is changed to have an execution time less than the waiting time (S502). Therefore, by performing the subtask during the waiting time, all tasks can be processed within a predetermined period.

On the other hand, if there are no tasks that can be divided and executed among the tasks included in the task queue, all tasks cannot be processed within a predetermined time, and an error is notified to the host controller 2 or the like (S503).

As shown in Fig. 23, the BMS#1 (14-1) is executed after the waiting time, and it is possible to divide the task F among tasks F and G that do not need to be executed synchronously. This task F can be divided into two subtasks f1 and f2. In the present embodiment, both f1 and f2 have an execution time less than or equal to the waiting time, but only at least one subtask may have an execution time less than or equal to the waiting time. In this case, at least one subtask may be divided to have an execution time of the same length as the waiting time. In other words, the subtask f1 is divided to have an execution time of 15ms so that it can be executed during 45~60ms, which is the waiting time of BMS#1 (14-1). And for the remainder, a subtask f2 with an execution time of 5ms is created. The priority of subtask f1 is adjusted so that it can be executed before task B, so the task is executed during the waiting time of 45~60ms. As a result, tasks having a length exceeding the predetermined time can be performed during the waiting time, so that all tasks can be performed within the predetermined time.

Referring to FIG. 24, the BMS 400 may include a controller (MCU) 410, a memory 420, an input/output interface 430, and a communication interface 440.

The MCU 410 controls processing and each configuration of various operations and operations in the BMS 400.

The memory 420 stores an operating system program and a program for performing the functions of the BMS 400. The memory 420 may include volatile memory and nonvolatile memory. For example, the memory 420 may be at least one of various storage media such as a semiconductor memory such as RAM, ROM, and flash memory, a magnetic disk, and an optical disk.

The input/output interface 430 performs input/output of various input signals and output signals. For example, the MCU 410 may output a control signal for a switching operation of the switching element through the input/output interface 430.

The communication interface 440 is a component capable of communicating with the outside through wired and/or wireless.

The MCU 410 executes a program stored in the memory 420 so that the schedule determination unit 130, the priority change unit 140, the task execution unit 150, the synchronization unit 160, and the error calculation unit 170 You will be able to implement a module that performs a function.

In addition, the MCU 410 may perform the function of the communication unit 110 in cooperation with the communication interface 440.

In the above, it has been described that all components constituting an embodiment of the present invention are combined into one or operated in combination, but the present invention is not necessarily limited to this embodiment. That is, within the scope of the object of the present invention, all the constituent elements may be selectively combined and operated in one or more.

In addition, terms such as "include", "consist of", or "have" described above mean that the corresponding component may be present unless otherwise stated, excluding other components. It should not be construed as being able to include other components. All terms including technical or scientific terms may be interpreted as having the same meaning as commonly understood by one of ordinary skill in the art, unless otherwise defined. Terms generally used, such as terms defined in the dictionary, should be interpreted as being consistent with the meaning of the context of the related technology, and are not interpreted as ideal or excessively formal meanings unless explicitly defined in the present invention.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains will be able to make various modifications and variations without departing from the essential characteristics of the present invention. Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but to explain the technical idea, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

Claims

As the battery management system in a system in which each of a plurality of battery management systems performs individually set tasks and transmits a result of the performed task to a master battery management system through wireless communication,

A task including a list of tasks performed by each of the plurality of battery management systems, execution time, execution cycle and task priority of each task included in the task list, and communication priority between the plurality of battery management systems An information storage unit;

A schedule determination unit that determines a work schedule based on data stored in the task information storage unit; And

Including; a priority change unit for adjusting the work priority of the task based on the work schedule determined by the schedule determination unit,

The schedule determination unit is a battery management system that adjusts a work schedule according to the adjusted work priority.
The method according to claim 1,

The priority change unit,

A battery management system that adjusts the task priority of the subordinate task to the next priority of the task executed immediately before the waiting time when there is a subordinate task that can be executed during the waiting time among the work schedule determined by the schedule determination unit .
The method according to claim 2,

The priority change unit,

A battery management system that compares the length of a waiting time among the work schedules determined by the schedule determination unit with execution times of tasks performed after the waiting time.
The method of claim 3,

The priority change unit,

As a result of the comparison, a battery management system for adjusting a priority so that a task having an execution time shorter than the length of the waiting time is executed during the waiting time.
The method of claim 4,

The priority change unit,

When there are a plurality of tasks having an execution period shorter than the length of the waiting time, the battery management system adjusts the priority of the task having the highest priority among the corresponding tasks.
The method of claim 4,

The priority change unit,

When there are a plurality of tasks having an execution period shorter than the length of the waiting time, the battery management system adjusts the priority of a task having the longest execution period among the corresponding tasks.
The method according to claim 1,

The task information storage unit is a battery management system in which tasks to be performed in synchronization with another battery management system in the task list are set.
The method of claim 7,

The schedule determination unit determines the work schedule in consideration of the tasks to be performed synchronously.
The method of claim 7,

A battery management system that synchronously performs tasks commonly performed by a plurality of battery management systems among the task list.
The method according to claim 2,

The waiting time is a period after the specific task is performed and before transmitting the result of the task to another battery management system.
The method according to claim 1,

A battery management system further comprising a communication unit capable of communicating with the master battery management system or another battery management system.
The method of claim 11,

When the priority of the task is adjusted by the priority change unit,

A battery management system for transmitting the work schedule adjusted by the schedule determination unit to another battery management system through the communication unit.
The method of claim 11,

When receiving the adjusted work schedule from the master battery management system or the other battery management system through the communication unit,

A battery management system for updating storage contents of the task information storage unit according to the adjusted work schedule.
The method of claim 11,

The communication unit transmits the work schedule adjusted by the schedule determination unit in a multicast or broadcast method to another battery management system.
The method according to claim 1,

Further comprising a task queue for storing the called tasks based on the work schedule determined by the schedule determination unit,

The priority change unit changes the priority of a task having an execution time shorter than a waiting time, among tasks excluding a task having a highest priority among tasks included in the task queue.
The method of claim 15,

The priority change unit changes the priority of the task to the original priority when the task whose priority has been changed is completed.
Storing a list of tasks performed by each of the plurality of battery management systems, an execution time, execution period, and task priority of each task included in the task list, and a communication priority between the plurality of battery management systems;

Determining a work schedule based on the stored data;

Adjusting a task priority of a task based on the determined task schedule; And

The control method of a battery management system comprising; adjusting a work schedule according to the adjusted work priority.
The method of claim 17,

Adjusting the task priority of the task,

If there is a lower priority task that can be executed during the waiting time among the determined work schedule, the task priority of the lower priority task is adjusted to be next to the priority of the task executed immediately before the waiting time. Control method.
The method of claim 18,

When there are a plurality of tasks having an execution period shorter than the length of the waiting time, the priority of the task having the highest priority among the corresponding tasks is adjusted.
The method of claim 18,

When there are a plurality of tasks having an execution period shorter than the length of the waiting time, the priority of a task having the longest execution period among the corresponding tasks is adjusted.