A method for managing battery data and a battery management system that provides such a method.

Abstract

The present invention relates to a battery data management method and a battery system that provides the method. The battery management system of the present invention includes a plurality of slave BMSs that each collect and store battery data including status information of a battery module at a predetermined storage period, and a master BMS that receives the battery data and identification data including identification information of the slave BMS from each of the plurality of slave BMSs at the storage period, and maps and stores the battery data and the identification data.

Description

[Technical Field]

[0001] [Cross-reference to Related Applications] This application claims the benefit of priority based on Korean Patent Application No. 10-2023-0060584 filed on May 10, 2023, and all contents disclosed in the document of said Korean patent application are incorporated as a part of the present specification.

[0002] The present invention relates to a battery data management method and a battery management system providing the method. [Background Art]

[0003] Since batteries used in automobiles and the like are also commodities, battery manufacturers or sales companies provide after-service (A / S) for batteries sold during the warranty period. After-service (A / S) is a service that provides consumers with services such as repair, installation and inspection for sold commodities at a special price or the like.

[0004] A sales company provides after-service (A / S) based on warranty data such as cumulative count of battery charge / discharge cycles and cumulative discharged energy. For example, the sales company can determine the period until the cumulative count of charge / discharge cycles reaches 1,000 times as the warranty period.

[0005] Quality assurance data is battery data that forms the basis for determining the application of after-sales service (A / S), and can be collected and / or calculated by a slave battery management system (Slave BMS) electrically connected to the battery. For example, if a battery system includes multiple battery modules, multiple slave BMSs, each electrically connected to one of the battery modules, can collect and / or calculate multiple quality assurance data corresponding to each of the battery modules. The collected quality assurance data can be stored in the storage unit of the slave BMS.

[0006] On the other hand, if a battery module becomes defective or reaches the end of its lifespan, the battery pack, consisting of the battery module and slave BMSs, can be replaced with a new battery pack. Alternatively, only the Master Battery Management System (Master BMS), which controls multiple slave BMSs, can be replaced. In this case, an update to the quality assurance data reflecting the current status is required.

[0007] Previously, updating quality assurance data by transferring it to the master BMS involved cumbersome tasks such as connecting a PC communication cable and running programs for data transfer. [Overview of the project] [Problems that the invention aims to solve]

[0008] The present invention aims to provide a battery data management method that can efficiently store and manage battery data, and a battery management system that provides this method. [Means for solving the problem]

[0009] A battery management system according to one embodiment of the present invention includes a plurality of slave BMSs that each collect and store battery data including status information of a battery module at predetermined storage cycles, and a master BMS that receives the battery data and identification data including identification information of the slave BMS from each of the plurality of slave BMSs at each storage cycle, maps the battery data and the identification data, and stores it.

[0010] The battery data may include at least one of the following: the total number of charge / discharge cycles of the battery module and the total energy discharged by the battery module.

[0011] When the master BMS receives a request signal for the battery data from an external system, it can transmit the stored battery data to the external system.

[0012] When the master BMS receives a signal requesting the transmission of battery data, it requests and receives the identification data from each of the plurality of slave BMSs. If the received identification data matches the stored identification data, the master BMS can transmit the stored battery data to the external system.

[0013] If the received identification data and the stored identification data do not match, the master BMS can request and receive the battery data from the slave BMS corresponding to the mismatched identification data, and update the stored battery data with the received battery data.

[0014] The master BMS can transmit battery data stored in the master BMS after the update to the external system.

[0015] The master BMS receives power from the power source and, upon waking up, requests and receives the identification data from each of the plurality of slave BMSs, requests and receives the battery data from at least one slave BMS whose received identification data does not match the previously stored identification data, and can update the stored battery data with the received battery data.

[0016] Another embodiment of the present invention provides a battery data management method in which a master BMS manages battery data collected by each of a plurality of slave BMSs electrically connected to a plurality of battery modules at predetermined storage cycles and stored in each of the plurality of slave BMSs, the method comprising: receiving a battery data request signal including battery module status information from an external system; and transmitting to the external system the battery data received from each of the plurality of slave BMSs at each storage cycle, mapped to identification data including identification information of the slave BMS, and stored.

[0017] The battery data may include at least one of the following: the total number of charge / discharge cycles of the battery module and the total energy discharged by the battery module.

[0018] The battery data management method further includes, after receiving a battery data request signal, a step of requesting and receiving the identification data from each of the plurality of slave BMSs, and a step of determining whether the received identification data matches the identification data stored in the master BMS, and if the result of the determination matches, the battery data stored in the master BMS can be transmitted to the external system.

[0019] The battery data management method further includes, after the step of determining whether the received identification data matches pre-stored identification data, if they do not match as a result of the determination, the step of requesting and receiving the battery data from at least one slave BMS corresponding to the mismatched identification data, and the step of updating the stored battery data with the received battery data, and the step of transmitting to an external system, after the update step, the battery data stored in the master BMS can be transmitted to the external system.

[0020] A battery data management method according to another embodiment of the present invention is a method for a master BMS to manage battery data collected by each of a plurality of slave BMSs electrically connected to a plurality of battery modules at predetermined storage cycles and stored in each of the plurality of slave BMSs, the method comprising: receiving power from a power source and waking up; requesting and receiving identification data including identification information of the slave BMS from each of the plurality of slave BMSs; determining whether the received identification data matches the identification data stored in the master BMS; if they do not match as a result of the determination, requesting and receiving the battery data from at least one slave BMS corresponding to the mismatched identification data; and updating the battery data stored in the master BMS with the received battery data.

[0021] The battery data may be mapped to the identification data and stored in the master BMS.

[0022] The battery data may include at least one of the total number of charge / discharge cycles of the battery module and the total energy discharged by the battery module. [Effects of the Invention]

[0023] According to the present invention, when a Slave BMS or a Master BMS is replaced, warranty data can be updated to the latest state without executing a program for connecting a PC communication cable and transferring battery data. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] [Figure 1] Figure 1 is a diagram illustrating a battery system according to one embodiment. [Figure 2] Figure 2 is a block diagram illustrating the configuration of the slave BMS of Figure 1. [Figure 3] Figure 3 is a block diagram illustrating the configuration of the master BMS of Figure 1. [Figure 4] Figure 4 is a conceptual diagram illustrating a state where battery data is stored in a plurality of slave BMSs and a master BMS according to one embodiment. [Figure 5] Figure 5 is a conceptual diagram illustrating a method for updating battery data when the master BMS is replaced according to one embodiment. [Figure 6] Figure 6 is a conceptual diagram illustrating a method for updating battery data when a first slave BMS is replaced according to one embodiment. [Figure 7] Figure 7 is a flowchart illustrating a method in which battery data collected by a slave BMS is stored in a master BMS according to another embodiment. [Figure 8] Figure 8 is a flowchart illustrating a method for updating battery data stored in a master BMS according to another embodiment. [Figure 9] Figure 9 is a flowchart illustrating a method in which a master BMS transmits battery data to an external system according to another embodiment. DESCRIPTION OF EMBODIMENTS

[0025] The embodiments disclosed herein will be described in detail below with reference to the accompanying drawings, but identical or similar components will be assigned the same or similar drawing numbers, and redundant descriptions thereof will be omitted. The suffixes “module” and / or “part” used for components in the following description are assigned or used interchangeably solely for the ease of specification preparation and do not have any distinguishing meaning or role in themselves. Furthermore, in describing the embodiments disclosed herein, if it is determined that a specific description of related prior art may obscure the gist of the embodiments disclosed herein, such detailed description will be omitted. In addition, the accompanying drawings are provided solely to facilitate understanding of the embodiments disclosed herein, and it should be understood that the accompanying drawings do not limit the technical idea disclosed herein and include any modifications, equivalents or substitutions that fall within the idea and scope of the present invention.

[0026] Terms including ordinal numbers, such as "first," "second," etc., can be used to describe a variety of components, but the components are not limited by such terms. These terms are used solely for the purpose of distinguishing one component from others.

[0027] When it is stated that one component is “linked” or “connected” to another component, it should be understood that it may be directly linked or connected to the other component, but there may also be other components 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 are no other components in between.

[0028] In this application, terms such as “includes” or “having” are intended to specify the existence of features, figures, steps, operations, components, parts, or combinations thereof described in the specification, and should be understood not to pre-exist to exclude the existence or possibility of adding one or more other embodiments, figures, steps, operations, components, parts, or combinations thereof.

[0029] Figure 1 is a diagram illustrating a battery system according to one embodiment, Figure 2 is a block diagram illustrating the configuration of the slave BMS in Figure 1, Figure 3 is a block diagram illustrating the configuration of the master BMS in Figure 1, and Figure 4 is a conceptual diagram illustrating a state in which battery data is stored in multiple slave BMSs and master BMSs according to one embodiment.

[0030] Referring to Figure 1, the battery system 1 includes a battery 10, a relay 20, and a battery management system (BMS) 30.

[0031] Battery 10 may include multiple battery modules B_M, each containing multiple battery cells electrically connected in series and parallel. In one embodiment, the battery cells may be rechargeable secondary batteries. Figure 1 shows, but is not limited to, battery 10 containing three battery modules B_M, each containing three battery cells connected in series. Battery 10 may include multiple battery modules B_M, each containing various numbers of battery cells connected in series and parallel. Each of the multiple battery cells may be electrically connected to a slave BMS (hereinafter referred to as "S_BMS") through wiring.

[0032] In Figure 1, the battery 10 includes multiple battery cells (Cell1-Celln) connected in series and is connected between the two output terminals OUT1 and OUT2 of the battery system 1, with a relay 20 connected between the positive terminal of the battery system 1 and the first output terminal OUT1. The configuration and the connections between the configurations shown in Figure 1 are examples, and the present invention is not limited thereto.

[0033] Relay 20 controls the electrical connection between the battery system 1 and the external device. When relay 20 is turned on, the battery system 1 and the external device are electrically connected for charging or discharging, and when relay 20 is turned off, the battery system 1 and the external device are electrically separated. In this case, the external device may be a charger in a charging cycle where power is supplied to charge the battery 10, or a load in a discharge cycle where the battery 10 discharges power to the external device.

[0034] The battery management system 30 may include multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and a master BMS (MA_BMS).

[0035] In Figure 1, multiple battery modules (B_M1, B_M2, B_M3) are shown to constitute a battery 10, and multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and a master BMS (MA_BMS) are shown to constitute a battery management system 30, but this is not limited to this. For example, a battery module B_M and a slave BMS (S_BMS) can constitute a single battery module assembly. In this case, if a battery module B_M needs to be replaced due to aging or other reasons, the entire battery module assembly may be replaced instead of just the battery module B_M. Also, although three slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) are shown in Figure 1, this is not limited to this. The battery management system 30 may include various numbers of slave BMSs.

[0036] Hereafter, when referring to a specific slave BMS (S_BMS_1, S_BMS_2, S_BMS_3) among multiple slave BMSs, the drawing code "k" will be used, and the communication unit, storage unit, and control unit included in that slave BMS (S_BMS_k) will be referred to as "S_k_1, S_k_2, S_k_3," respectively. In addition, when referring to a battery module electrically connected to a specific slave BMS (S_BMS_k), the drawing code "B_Mk" will be used, and the battery data collected by the specific slave BMS (S_BMS_k) and the ID of the slave BMS (S_BMS_k) will be referred to as "W_data_k" and "ID_k," respectively.

[0037] The slave BMS (S_BMS_k) can monitor the battery module B_Mk and collect battery data, including information about the status of the battery module B_Mk. In one embodiment, the battery data may include information such as the cell voltage, cell current, and cell temperature of each of the battery cells. In another embodiment, the battery data may further include warranty data, which serves as the basis for the warranty period, which is the period during which maintenance and repair of the battery module B_Mk is guaranteed.

[0038] For example, a battery module B_Mk may be configured by the manufacturer to be eligible for free repairs until it reaches 4000 charge / discharge cycles or a cumulative discharge energy of 200 MWh. In this case, the charge / discharge cycles and cumulative discharge energy can correspond to the quality assurance data.

[0039] Referring to Figure 2, the slave BMS (S_BMS_k) may include a communication unit S_k_1, a storage unit S_k_2, and a control unit S_k_3.

[0040] The communication unit S_k_1 can communicate with the master BMS (MA_BMS) using the CAN communication method to transmit battery data or receive various signals. For example, the communication unit S_k_1 can transmit battery data stored in the storage unit S_k_2 and identification data including the identification information ID_k of the slave BMS (S_BMS_k) to the master BMS (MA_BMS) under the control of the control unit S_k_3. Another example is that the communication unit S_k_1 can receive a request signal for battery data or a request signal for the identification information ID_k from the master BMS (MA_BMS).

[0041] The storage unit S_k_2 may store battery data collected by the control unit S_k_3 at predetermined intervals. The storage unit S_k_2 may also store identification data, including the identification information ID_k of the slave BMS (S_BMS_k). For example, the identification data may be generated when the battery module assembly is manufactured and stored in the storage unit S_k_2.

[0042] The control unit S_k_3 can monitor the slave BMS (S_BMS_k), collect battery data, and store it in the storage unit S_k_2. Depending on the embodiment, the control unit S_k_3 can transmit the battery data and / or identification information ID_k stored in the storage unit S_k_2 to the master BMS (MA_BMS) via the communication unit S_k_1 in response to a request from the master BMS (MA_BMS).

[0043] The master BMS (MA_BMS) can control multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) in general. Depending on the embodiment, the master BMS (MA_BMS) can store battery data collected by each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and transmit the stored battery data to an external system (e.g., an automotive system) upon request. In other words, the battery data may be stored not only in the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) but also in the master BMS (MA_BMS). In this case, the external system may include an automotive system on which the battery system 1 is installed, an energy storage system (ESS), etc.

[0044] Referring to Figure 3, the master BMS (MA_BMS) may include the master communication unit MA_1, the master storage unit MA_2, and the master control unit MA_3.

[0045] The master communication unit MA_1 can communicate with multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and external systems. For example, the master communication unit MA_1 can receive a request signal for battery data transmitted from an external system. Another example is that the master communication unit MA_1 can receive battery data and / or multiple identification data, including the identification information ID_k of each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3), from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3).

[0046] The master storage unit MA_2 may store battery data transmitted from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and multiple identification data including the identification information ID_k of each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). Depending on the embodiment, the master storage unit MA_2 may store battery data and identification data corresponding to each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) mapped to each other.

[0047] The master control unit MA_3 can integrate and manage battery data collected by each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). Depending on the embodiment, the master control unit MA_3 can manage the battery data stored in each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and the multiple battery data stored in the master storage unit MA_2 so that their states are identical.

[0048] For example, referring to Figure 4, the first slave BMS (S_BMS_1) may store the first battery data W_data_1, the second slave BMS (S_BMS_2) may store the second battery data W_data_2, and the third slave BMS (S_BMS_3) may store the third battery data W_data_3. Depending on the embodiment, the master BMS (MA_BMS) may store the first battery data W_data_1 mapped to first identification data including first identification information ID_1. The master BMS (MA_BMS) may store the second battery data W_data_2 mapped to second identification data including second identification information ID_2. The master BMS (MA_BMS) may store the third battery data W_data_3 mapped to third identification data including third identification information ID_3. In this case, the identification information for the first slave BMS (S_BMS_1), the second slave BMS (S_BMS_2), and the third slave BMS (S_BMS_3) are the first identification information ID_1, the second identification information ID_2, and the third identification information ID_3, respectively.

[0049] The following section will explain in detail how the master control unit MA_3 manages battery data, referring to Figures 5 and 6.

[0050] Figure 5 is a conceptual diagram illustrating a method for updating battery data when the master BMS is replaced according to one embodiment, and Figure 6 is a conceptual diagram illustrating a method for updating battery data when the first slave BMS is replaced according to one embodiment.

[0051] Referring to Figures 1 and 5, let's assume, for example, that the master BMS (MA_BMS) is replaced with a new master BMS (MA_BMS*) due to a failure or degradation of its functionality. In this case, the new master BMS (MA_BMS*) may not have the identification data for each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) stored in it. Also, the battery data stored for each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) in the new master BMS (MA_BMS*) may be set to its initial value (0).

[0052] The new master BMS (MA_BMS*) can request battery data and identification data from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). The new master BMS (MA_BMS*) can map the battery data and identification data received from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and store it in the master storage unit MA_2*.

[0053] Specifically, the new master BMS (MA_BMS*) can request and receive the first battery data W_data_1 and the first identification data ID_1 from the first slave BMS (S_BMS_1), map the first battery data W_data_1 and the first identification data ID_1, and store them in the master storage unit MA_2*. Furthermore, the new master BMS (MA_BMS*) can request and receive the second battery data W_data_2 and the second identification data ID_2 from the second slave BMS (S_BMS_1), map the second battery data W_data_2 and the second identification data ID_2, and store them in the master storage unit MA_2*. Finally, the new master BMS (MA_BMS*) can request and receive the third battery data W_data_3 and the third identification data ID_3 from the third slave BMS (S_BMS_3), map the third battery data W_data_3 and the third identification data ID_3, and store them in the master storage unit MA_2*. For example, referring to Figure 5, we can assume that the first battery data W_data_1, the second battery data W_data_2, and the third battery data W_data_3 are 10, 8, and 5, respectively.

[0054] The master storage unit MA_2* can be updated with multiple battery data sets, each mapped to a different identification number (ID_1, ID_2, ID_3) with an initial value (0). This allows multiple battery data sets reflecting the current status of each of the slave BMS units (S_BMS_1, S_BMS_2, S_BMS_3) to be stored in the new master BMS (MA_BMS*) without the need for cumbersome tasks such as connecting a PC communication cable or running a data transfer program.

[0055] Referring to Figures 1 and 6, for example, if the first battery module B_M1 is replaced due to failure, degradation, or other reasons, it is assumed that the first slave BMS (S_BMS_1), which is electrically connected to the first battery module B_M1, will also be replaced along with the first battery module B_M1. Furthermore, it is assumed that the first battery data W_data_1 before replacement is 10, and the new first battery data W_data_1* is 0. In other words, since the new first battery module B_M1* has no operational history, the battery data stored in the new first slave BMS (S_BMS_1*) may be set to the initial value (0).

[0056] The master BMS (MA_BMS) can update the first battery data W_data_1 and identification data ID_1 of the first slave BMS (S_BMS_1) before replacement to the new first battery data W_data_1* and new first identification data ID_1* of the new first slave BMS (S_BMS_1*).

[0057] Specifically, the master BMS (MA_BMS) requests and receives new first battery data W_data_1* and new first identification data ID_1* from the new first slave BMS (S_BMS_1*). The master BMS (MA_BMS) can then map the new first battery data W_data_1* and new first identification data ID_1* and store them in the master storage unit MA_2.

[0058] Figure 7 is a flowchart illustrating how, in another embodiment, battery data collected by a slave BMS is stored in a master BMS.

[0059] Referring to Figure 7, first, the master BMS (MA_BMS) determines whether or not the battery data storage cycle set according to a predetermined criterion has arrived (S110).

[0060] The storage cycle can correspond to the period during which the slave BMS (S_BMS_k) collects battery data, including the status information of the battery module B_Mk. For example, the storage cycle can correspond to the point when the charge and discharge cycles of battery 10 are completed. However, it is not limited to this, and the master BMS (MA_BMS) may set the storage cycle according to a variety of criteria.

[0061] If the judgment indicates that the storage cycle has not yet arrived (S110; No), the master BMS (MA_BMS) continues to count the time.

[0062] If the determination is made and the storage cycle has arrived (S110; Yes), the master BMS (MA_BMS) requests and receives battery data W_data_k and identification data ID_k from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) (S120).

[0063] For each storage cycle, each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) collects and stores battery data. Then, upon request from the master BMS (MA_BMS), each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) can transmit the collected battery data W_data_k and identification data ID_k to the master BMS (MA_BMS).

[0064] Depending on the embodiment, the battery data may include at least one of the total number of charge / discharge cycles of the battery module B_Mk and the total energy discharged by the battery module B_Mk. For example, when the charge and discharge cycles of battery 10 are completed, each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) can count the cycles and transmit the total number of cycles to the master BMS (MA_BMS). Another example is when the discharge cycle of battery 10 is completed, each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) can calculate the total energy discharged by the battery module B_Mk and transmit the total energy value to the master BMS (MA_BMS).

[0065] Next, the master BMS (MA_BMS) maps the battery data W_data_k and identification data ID_k corresponding to each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and stores them in the master storage unit MA_2 (S130).

[0066] Figure 8 is a flowchart illustrating how battery data stored in the master BMS is updated according to another embodiment.

[0067] Referring to Figure 8, first, the master BMS (MA_BMS) receives power from the power supply and wakes up, then requests and receives identification data ID_k from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) (S210, S220).

[0068] Next, the master BMS (MA_BMS) determines whether the identification data received from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) matches the identification data previously stored in the master storage unit MA_2 (S230).

[0069] For example, if the master BMS (MA_BMS) or at least one of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3), specifically slave BMS (S_BMS_k), is replaced, the state of the battery data W_data_k of the slave BMS (S_BMS_k) stored in the master storage unit MA_2 may differ from the state of the battery data W_data_k stored in the slave BMS (S_BMS_k). The master BMS (MA_BMS) can determine whether the identification data ID_k matches each time it wakes up, and can check the real-time state of the battery module B_Mk installed in the battery 10.

[0070] If the judgment result is a match (S230; YES), the master BMS (MA_BMS) terminates without taking any further action.

[0071] If the result of the judgment is not a match (S230; NO), the master BMS (MA_BMS) requests and receives the battery data W_data_k from at least one slave BMS (S_BMS_k) whose identification data ID_k does not match (S240).

[0072] For example, referring to Figure 6, among the first to third slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3), the slave BMS (S_BMS_k) whose identification data ID_k does not match is assumed to be the first slave BMS (S_BMS_1). Then, the master BMS (MA_BMS) can request the new first battery data W_data_1* and the new first identification data ID_1* from the new first slave BMS (S_BMS_1*).

[0073] Next, the master BMS (MA_BMS) updates the master storage unit MA_2 with the received battery data from the stored battery data (S250).

[0074] For example, referring to Figure 6, the master BMS (MA_BMS) can update the master storage unit MA_2 by deleting the first battery data W_data_1 that was previously stored in the master storage unit MA_2 and saving the new first battery data W_data_1*. At this time, the master BMS (MA_BMS) can map the new first battery data W_data_1* to the new first identification data ID_1* and save it in the master storage unit MA_2.

[0075] Figure 9 is a flowchart illustrating how a master BMS transmits battery data to an external system in another embodiment.

[0076] Referring to Figure 9, first, the master BMS (MA_BMS) receives a request signal for battery data from an external system (S310).

[0077] The external system (not shown) may be a higher-level system on which the battery system 1 is mounted. For example, the external system may include a vehicle system, an Energy Storage System (ESS), an electric motorcycle, or any other system on which the battery 10 and a battery management system (BMS) are mounted. The battery data request signal may be a signal in which the external system requests battery data from the battery system.

[0078] The battery data may include information such as the cell voltage, cell current, and cell temperature of each of the multiple battery cells. Depending on the embodiment, the battery data may further include warranty data that serves as the basis for the warranty period, which is the period during which maintenance and repair of the battery module B_Mk is guaranteed.

[0079] Next, the master BMS (MA_BMS) requests and receives identification data from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) (S320).

[0080] The identification data may include the identification information ID_k of the slave BMS (S_BMS_k). The identification information ID_k may be generated when the battery module assembly is manufactured and stored in the storage unit S_k_2 of the slave BMS (S_BMS_k). For example, the identification data of multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) may each contain different identification information ID_k.

[0081] Next, the master BMS (MA_BMS) determines whether the identification data previously stored in the master storage unit MA_2 matches the received identification data (S330).

[0082] Next, if the previously stored identification data matches the received identification data (S330; Yes), the master BMS (MA_BMS) transmits the battery data previously stored in the master storage unit MA_2 to the external system (S360).

[0083] Next, if the previously stored identification data does not match the received identification data (S330; No), the master BMS (MA_BMS) requests and receives battery data from the slave BMS corresponding to the mismatched identification data (S340).

[0084] Next, the master BMS (MA_BMS) updates the battery data previously stored in the master storage unit MA_2 with the received battery data (S350).

[0085] Next, the master BMS (MA_BMS) transmits the battery data stored in the master storage unit MA_2 after the update to an external system (S360).

[0086] At predetermined storage intervals, the slave BMS (S_BMS_k) can store the collected battery data in its storage unit S_k_2 and transmit it to the master BMS (MA_BMS). For example, at predetermined intervals, battery data collected by each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) may be stored simultaneously in the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and the master BMS (MA_BMS).

[0087] For example, if the master BMS (MA_BMS) or at least one of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3), specifically slave BMS (S_BMS_k), is replaced, the state of the battery data W_data_k of the slave BMS (S_BMS_k) stored in the master storage unit MA_2 may differ from the state of the battery data W_data_k stored in the slave BMS (S_BMS_k). Depending on the embodiment, the master BMS (MA_BMS) can determine whether the identification data matches each time it receives a battery data request signal. Then, the master BMS (MA_BMS) can transmit battery data containing accurate information about the current state of the multiple battery modules (B_M1, B_M2, B_M3) included in the battery 10 to an external system.

[0088] Although embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements made by persons with ordinary skill in the art to which the present invention belongs also fall within the scope of the present invention.

Claims

1. Multiple slave BMSs each collect and store battery data, including battery module status information, at predetermined storage intervals, A master BMS receives identification data, which includes the battery data and identification information of the slave BMS, from each of the plurality of slave BMSs at each of the storage cycles, maps the battery data and the identification data, and stores them. Includes, The aforementioned master BMS is When a request signal for the battery data is received from an external system, the stored battery data is transmitted to the external system. The aforementioned master BMS is A battery management system that, upon receiving a battery data transmission request signal, requests and receives the identification data from each of the plurality of slave BMSs, and when the received identification data matches the stored identification data, transmits the stored battery data to the external system.

2. The aforementioned master BMS is The battery management system according to claim 1, wherein if the received identification data and the stored identification data do not match, the system requests and receives the battery data from the slave BMS corresponding to the mismatched identification data, and updates the stored battery data with the received battery data.

3. The aforementioned master BMS is The battery management system according to claim 2, wherein battery data stored in the master BMS after the update is transmitted to the external system.

4. A battery management system, Multiple slave BMSs each collect and store battery data, including battery module status information, at predetermined storage intervals, A master BMS receives identification data, which includes the battery data and identification information of the slave BMS, from each of the plurality of slave BMSs at each of the storage cycles, maps the battery data and the identification data, and stores them. Includes, The aforementioned master BMS is A battery management system that, upon receiving power from a power source and waking up, requests and receives the identification data from each of the plurality of slave BMSs, requests and receives the battery data from at least one slave BMS whose received identification data does not match the previously stored identification data, and updates the stored battery data with the received battery data.

5. The battery data is The battery management system according to claim 1 or 4, comprising information on at least one of the total number of charge / discharge cycles of the battery module and the total energy discharged by the battery module.

6. A method by which a master BMS manages battery data collected by each of several slave BMSs electrically connected to multiple battery modules at predetermined storage cycles, and stored in each of the multiple slave BMSs, The steps include receiving a request signal for battery data, which includes status information of the battery module, from an external system, The steps include: transmitting battery data received from each of the plurality of slave BMSs at each storage cycle, mapped to identification data including identification information of the slave BMS, and stored to the external system; Includes, After the step of receiving the battery data request signal, The method further includes the steps of requesting and receiving the identification data from each of the plurality of slave BMSs, and determining whether the received identification data matches the identification data stored in the master BMS. The step of transmitting to the external system is: A battery data management method that, if the result of the above determination is correct, transmits the battery data stored in the master BMS to the external system.

7. The aforementioned battery data is The battery data management method according to claim 6, comprising information on at least one of the total number of charge / discharge cycles of the battery module and the total energy discharged by the battery module.

8. In the step of determining whether the received identification data matches the previously stored identification data, If the result of the above determination does not match, the further steps include requesting and receiving the battery data from at least one slave BMS corresponding to the mismatched identification data, and updating the stored battery data with the received battery data. The step of transmitting to the external system is: The battery data management method according to claim 6, wherein, after the update step, the battery data stored in the master BMS is transmitted to the external system.

9. A method by which a master BMS manages battery data collected by each of several slave BMSs electrically connected to multiple battery modules at predetermined storage cycles, and stored in each of the multiple slave BMSs, The steps include receiving power from the power source and waking up, The steps include requesting and receiving identification data containing the identification information of the slave BMS from each of the aforementioned plurality of slave BMSs, The steps include determining whether the received identification data matches the identification data stored in the master BMS, If the result of the above determination does not match, the battery data is requested from and received from at least one slave BMS corresponding to the mismatched identification data. The steps include updating the battery data stored in the master BMS with the received battery data, Battery data management methods, including those mentioned above.

10. The aforementioned battery data is The battery data management method according to claim 9, wherein the data is mapped to the identification data and stored in the master BMS.

11. The aforementioned battery data is The battery data management method according to claim 9, comprising at least one of the total number of charge / discharge cycles of the battery module and the total energy discharged by the battery module.

Images