BMS management apparatus and method

Abstract

A BMS management device according to an embodiment of the present invention is a device comprising a master BMS and a plurality of slave BMSs, wherein the BMS management device includes: the master BMS configured to transmit an NV value confirmation request to the plurality of slave BMSs and, when a response to the NV value confirmation request is received from the plurality of slave BMSs, transmit an equalization request to the plurality of slave BMSs depending on whether a source ID has been established;and the plurality of slave BMSs configured to, when the NV value confirmation request is received from the master BMS, transmit each NV value to the master BMS, establish a representative BMS and a destination BMS based on the plurality of NV values, establish the representative BMS or the slave BMS corresponding to the source ID as a source BMS according to the equalization request received from the master BMS, and update an NV value of the destination BMS based on an NV value of the source BMS.;

Description

BMS management apparatus and method Technology sector This disclosure relates to a BMS (Battery Management System) management apparatus and method, and more particularly to a BMS management apparatus and method capable of efficiently updating a plurality of slave BMSs. Background of the invention Recently, the demand for portable electronic products such as laptops, video cameras, and mobile phones has increased dramatically, and electric vehicles, energy storage batteries, robots, satellites, and similar technologies have been seriously developed. Consequently, high-performance batteries that allow for repeated charging and discharging are being actively researched. Commercially available batteries today include nickel-cadmium batteries, nickel-hydrogen batteries, nickel-zinc batteries, lithium batteries, and similar types. Among these, lithium batteries are particularly noteworthy because they exhibit almost no memory effect compared to nickel-based batteries and also have a very low self-charge rate and high energy density. In general, an energy storage system (ESS) comprises multiple battery racks as a single system unit, and each of these battery racks may include a battery management system (BMS). However, within this BMS, a system value (e.g., an NV value, or similar) is set manually by an operator. For example, when the BMS of a battery rack is replaced, the operator sets the system value of the replaced BMS to match the system value of the other BMSs. However, when the operator directly sets the BMS system value, there is a cost and risk of error, so a method is required that can handle this work at the system level through communication between BMS. The additional prior art is described in documents US 2016 / 359329 A1, US 2020 / 169466 A1 and US 2020 / 351349 A1. Explanation of the invention Technical problem This disclosure is designed to solve problems of the related technique and, therefore, this disclosure is intended to provide a BMS management apparatus and method capable of efficiently updating and synchronizing NV values ​​by a plurality of slave BMSs. These and other objects and advantages of this disclosure can be understood from the following detailed description and will become more apparent from the illustrative embodiments herein. It will also be readily understood that the objects and advantages of this disclosure can be achieved by the means shown in the appended claims. Technical solution A BMS management apparatus according to one aspect of this disclosure is a device according to claim 1. When an ID for any one of the plurality of slave BMSs is received from the outside, the master BMS can be configured to set the received ID as the source ID. The master BMS can be configured to send an initial standardization request that includes the source ID to the plurality of slave BMSs, when the source ID is established. The master BMS can be configured to send a second uniformization request that does not include the source ID to the plurality of slave BMSs, when the source ID is not set. The plurality of slave BMSs can be configured to establish a slave BMS that corresponds to the source ID as the source BMS, when the first uniformization request is received. The plurality of slave BMSs can be configured to establish the representative BMS as the origin BMS when the second uniformization request is received. After establishing the representative BMS and the target BMS, when the uniformization request is not received for a predetermined time, the plurality of slave BMSs can be configured to set the representative BMS as the source BMS. The plurality of slave BMSs can be configured to generate groups, including a main group and at least one secondary group according to the NV values ​​of the plurality of slave BMSs, where slave BMSs that have the same NV value are included in the same group; where the generation of the main group and the at least one secondary group is done according to the number of slave BMSs included in the groups, the main group being the group with the largest number of slave BMSs, setting any one of the plurality of slave BMSs included in the main group as the representative BMS, and setting a slave BMS included in the at least one secondary group as the target BMS. The plurality of slave BMSs can be configured to establish a slave BMS that has an ID that corresponds to a pre-set condition among the plurality of slave BMSs included in the main group as the representative BMS. The master BMS can be configured to store the NV value of the source BMS at a previous update time as a reference NV value, and when the plurality of NV values ​​received from the plurality of slave BMSs are sorted into groups of the same NV value, the master BMS can be configured to set the ID of any one of the plurality of slave BMSs that have the same NV value as the reference NV value as the source ID. The source BMS can be configured to receive an updated NV value from each target BMS if the NV value is updated, and send a uniformization completion notification or a uniformization failure notification to the master BMS depending on whether the updated NV value received from the target BMS is the same as the NV value from the source BMS. An energy storage system according to another aspect of this disclosure may comprise the BMS management apparatus according to another aspect of this disclosure. A BMS management method according to claim 11 provides another aspect of the present disclosure. Advantageous effects According to one aspect of this disclosure, there is an advantage that the plurality of slave BMSs can autonomously update the NV value not only when the source ID is specified by the master BMS but also when the source ID is not specified. The effects of this disclosure are not limited to those mentioned above, and those skilled in the art will clearly understand other effects not mentioned herein from the description in the claims. Brief description of the drawings The accompanying drawings illustrate a preferred embodiment of the present disclosure and, together with the foregoing disclosure, serve to provide further understanding of the technical features of the present disclosure and, therefore, the present disclosure is not to be construed as being limited to the drawing. FIG. 1 is a diagram schematically showing a BMS management apparatus according to an embodiment of the present disclosure. FIG. 2 is a diagram schematically showing an embodiment of the BMS management apparatus according to an embodiment of the present disclosure. FIG. 3 is a diagram that schematically shows another embodiment of the BMS management apparatus according to an embodiment of the present disclosure. FIG.4 is a diagram that schematically shows yet another embodiment of the BMS management apparatus in accordance with an embodiment of the present disclosure. Figures 5 to 8 are diagrams that schematically show an embodiment in which an NV value of a slave BMS is updated by the BMS management apparatus according to one embodiment of this disclosure. Figure 9 is a diagram that schematically shows a BMS management method according to another embodiment of this disclosure. Figure 10 is a diagram that schematically shows a stage in establishing the representative BMS and the target BMS in the BMS management method according to another embodiment of this disclosure. Figure 11 is a diagram that schematically shows a stage in establishing the source BMS in the BMS management method according to another embodiment of this disclosure. Preferred embodiment of the invention Terms that include ordinal numbers, such as "first," "second," and the like, may be used to distinguish one element from another among several elements, but they are not intended to limit the elements. Throughout this descriptive report, when a portion is referred to as "comprising" or "including" any element, it means that the portion may include other elements as well, without excluding other elements, unless specifically stated otherwise. Furthermore, throughout the descriptive memory, when a portion is referred to as being "connected" to another portion, it is not limited to the case where they are "directly connected", but also includes the case where they are "indirectly connected" with another element interposed in between. Hereafter in this document, the preferred embodiments of this disclosure will be described in detail with reference to the accompanying drawings. FIG. 1 is a diagram schematically showing a BMS 100 management apparatus according to an embodiment of the present disclosure. Referring to FIG.1, the BMS 100 management apparatus may include a master BMS 110 and a plurality of slave BMS 120. For example, the master BMS 110 can be a higher-ranking BMS than the slave BMS. The master BMS 110 can be configured to send a non-volatile value (NV) confirmation request to the plurality of slave BMS 120. For example, in the implementation of FIG. 1, the master BMS 110 can be connected to a plurality of slave BMS 120, respectively. The master BMS 110 can send an NV value confirmation request to each of a first slave BMS 120a, a second slave BMS 120b, a third slave BMS 120c, a fourth slave BMS 120d, and a fifth slave BMS 120e. When a response to the NV value confirmation request is received from the plurality of slave BMS 120, the master BMS 110 can be configured to send a uniformization request to the plurality of slave BMS 120 based on whether a source ID is set. For example, when the master BMS 110 receives all NV value confirmation requests from each of the plurality of slave BMS 120s, the master BMS 110 can send a uniformization request to the plurality of slave BMS 120s. In this case, the master BMS 110 can identically send either a first uniformization request or a second uniformization request to the plurality of slave BMS 120s, depending on whether the source ID is set. In other words, when the source ID is set, the master BMS 110 can be configured to send the first uniformization request, which includes the source ID, to the plurality of slave BMS 120. Conversely, when the source ID is not set, the master BMS 110 can be configured to send the second uniformization request, which does not include the source ID, to the plurality of slave BMS 120. In the implementation of FIG.1, the master BMS 110 can send the uniformization request to the plurality of slave BMS 120 when all NV value confirmation requests are received from the plurality of slave BMS 120. The plurality of slave BMS 120 can be configured to send each NV value to the master BMS 110 when the NV value confirmation request is received from the master BMS 110. Each of the plurality of slave BMS 120 can send its NV value to the master BMS 110 as a response to the NV value confirmation request. Preferably, the plurality of slave BMS 120 can generate a hash value for the NV value using the same hash function. Furthermore, the plurality of slave BMS 120 can send the generated hash value to the master BMS 110. For example, in the implementation of FIG.1, each of the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the fourth slave BMS 120d, and the fifth slave BMS 120e can send their NV value as a response to the NV value confirmation request. The plurality of slave BMS 120 can be configured to establish a representative BMS and a target BMS based on the plurality of NV values. When the plurality of slave BMS 120 receives an NV value confirmation request from the master BMS 110, the plurality of slave BMS 120 can establish a representative BMS and a target BMS based on the plurality of NV values. Preferably, the plurality of slave BMS 120 can establish the representative BMS and the target BMS after sending the NV value to the master BMS 110. For example, in the implementation shown in FIG. 1, each of the plurality of 120 slave BMSs can have an NV value. That is, the plurality of NV values ​​can be five. The plurality of 120 slave BMSs can designate any one of them as a representative BMS based on these five NV values. Furthermore, the plurality of 120 slave BMSs can designate the target BMS based on these five NV values. The specific details of designating the representative BMS and the target BMS by the plurality of 120 slave BMSs based on these NV values ​​will be described later. The plurality of slave BMS 120 can be configured to establish the representative BMS or a slave BMS that corresponds to the source ID as the source BMS according to the uniformization request received from the master BMS 110. Specifically, the plurality of slave BMS 120 can establish the representative BMS or the slave BMS that corresponds to the source ID as the source BMS depending on whether the source ID is included in the uniformization request received from the master BMS 110. In other words, the plurality of slave BMSs (120) can be configured to establish a slave BMS corresponding to the source ID as the source BMS when the first uniformization request is received. Conversely, the plurality of slave BMSs (120) can be configured to establish the representative BMS as the source BMS when the second uniformization request is received. The plurality of 120 slave BMSs can be configured to update the NV value of the target BMS according to the NV value of the source BMS. For example, in the implementation of FIG. 1, when the NV value of the first slave BMS 120a and the NV values ​​of the second through fourth slave BMSs 120b through 120d are equal, and the NV value of the fifth slave BMS 120e is different, the first slave BMS 120a is assumed to be set as the source BMS and the fifth slave BMS 120e as the target BMS. That is, the second slave BMS 120b, the third slave BMS 120c, and the fourth slave BMS 120d do not need to be set as the target BMS. The first slave BMS 120a can send its NV value to the fifth slave BMS 120e to update the NV value of the fifth slave BMS 120e to match the NV values ​​of the first through fourth slave BMSs 120a through 120d. The BMS 100 management apparatus according to an embodiment of the present disclosure has the advantage that the plurality of slave BMS 120 can autonomously update the NV value not only when the source ID is specified by the master BMS 110 but also when the source ID is not specified. For example, even if the source ID is missing from the uniformization request received from the master BMS 110 by the plurality of slave BMS 120 or is lost due to a communication failure, the plurality of slave BMS 120 can update the NV value normally by setting the source BMS itself. Meanwhile, the master BMS 110 and the plurality of slave BMS 120 may include a control unit and a storage unit. Meanwhile, the control unit may optionally include a processor, an application-specific integrated circuit (ASIC), another chipset, a logic circuit, a register, a communication modem, a data processing device, and similar components known in the art to execute the various control logics described in this disclosure. Furthermore, when the control logic is implemented in software, the control unit may be implemented as a set of program modules. The program module may then be stored in memory and executed by the control unit. The memory may be provided inside or outside the control unit and may be connected to the control unit by various well-known means. Furthermore, the storage unit can store data or programs necessary for the operation and function of each component of the master BMS 110 and the plurality of slave BMS 120, data generated during the process of performing the operation or function, or similar data. The type of storage unit is not particularly limited, provided it is a known information storage medium capable of recording, erasing, updating, and reading data. Examples of information storage media include RAM, flash memory, ROM, EEPROM, registers, and similar devices. Additionally, the storage unit can store program code that defines processes executable by the control unit. When an ID for any one of the plurality of slave BMS 120 is received from the outside, the master BMS 110 can be configured to set the received ID as the source ID. For example, the master BMS 110 can communicate with the outside world. The master BMS 110 can receive an ID for any one of the multiple slave BMS 120s from a server or similar device. Alternatively, the master BMS 110 can connect to an input device to receive an ID for any one of the multiple slave BMS 120s entered through the input device. In this case, the input device can be a device capable of outputting an input value through user manipulation, such as a keyboard, mouse, and / or touchscreen. FIG. 2 is a diagram schematically showing an embodiment of the BMS 100 management apparatus according to an embodiment of the present disclosure. Specifically, the implementation in FIG.2 is an implementation in which the master BMS 110 sets the source ID after receiving a response to the NV value from the plurality of slave BMS 120. In the implementation of FIG. 2, when the source ID is established, the master BMS 110 can send the first uniformization request that includes the source ID to the plurality of slave BMS 120. When the first uniformization request is received, the plurality of 120 slave BMSs can set the slave BMS that corresponds to the source ID as the source BMS. In other words, the plurality of slave BMS 120 can set the representative BMS and the target BMS in advance before receiving the first uniformization request from the master BMS 110. Furthermore, when the first uniformization request is received, the plurality of slave BMS 120 can set the source BMS according to the source ID regardless of the established representative BMS. The source BMS can update the NV value of the target BMS by sending its NV value to the target BMS. Subsequently, the source BMS can be configured to receive updates to the NV value and the updated NV value from each target BMS. Additionally, the source BMS can be configured to send a uniformization completion notification or a uniformization failure notification to the master BMS 110 depending on whether the updated NV value received from the target BMS matches its own NV value. That is, after the source BMS receives the updated NV value from the target BMS and judges whether the update completes successfully, the source BMS can send either a uniformization completion notification or a uniformization failure notification to the master BMS 110, depending on the outcome. Figure 3 is a diagram schematically illustrating another embodiment of the BMS 100 management apparatus, as described in this disclosure. Specifically, the implementation in FIG.3 is an implementation in which the master BMS 110 does not set the source ID, unlike the implementation in FIG.2. In the implementation of FIG.3, the master BMS 110 can send the second uniformization request that does not include the source ID to the plurality of slave BMS 120, when the source ID is not set. The plurality of 120 slave BMSs can establish the representative BMS as the origin BMS, when it receives the second uniformization request. In other words, the plurality of slave BMS 120 can set the representative BMS and the target BMS in advance before receiving the second uniformization request from the master BMS 110. In addition, the plurality of slave BMS 120 can set a pre-set representative BMS as the source BMS when receiving the second uniformization request that does not include the source ID from the master BMS 110. In this case, the slave BMS set as the source BMS can send declaration information to inform the remaining slave BMSs that it is selected as the source BMS. Subsequently, the source BMS can update the NV value of the target BMS by sending its NV value to the target BMS. In other words, the plurality of slave BMSs (120) can update the NV value of the target BMS by setting the source BMS itself, even when the source ID is not received from the master BMS (110). The source BMS can receive the updated NV value from the target BMS and judge whether the update completes normally, and then send a uniformization completion notification or a uniformization failure notification to the master BMS 110 according to the judgment result. FIG.4 is a diagram that schematically shows yet another embodiment of the BMS 100 management apparatus according to an embodiment of the present disclosure. Specifically, the embodiment of FIG. 4 is an embodiment in which the uniformization request is not received for a predetermined time after the plurality of slave BMS 120 sends a response to the NV value to the master BMS 110 and establishes the representative BMS and the target BMS, unlike the embodiment of FIGS.2 and 3. The plurality of 120 slave BMSs can be configured to set the representative BMS as the source BMS, when the uniformization request is not received for a predetermined time after setting the representative BMS and the target BMS. For example, when a system failure and / or communication failure occurs in the master BMS 110, the master BMS 110 may not be able to send a uniformization request to the plurality of slave BMS 120. Even in this case, since the NV value of the plurality of slave BMS 120 must be updated for the plurality of slave BMS 120 to operate normally, the plurality of slave BMS 120 can set a pre-set representative BMS as the source BMS. That is, the BMS 100 management apparatus according to an embodiment of the present disclosure has the advantage of updating the NV value of the plurality of slave BMS 120 even when the plurality of slave BMS 120 does not receive a uniformization request from the master BMS 110. Figures 5 to 8 are diagrams that schematically show an embodiment in which an NV value of a slave BMS is updated by the BMS management apparatus 100 in accordance with an embodiment of this disclosure. Specifically, the embodiment of Figure 5 is an embodiment for a plurality of slave BMS 120s in an initial stage. In the embodiment of Figure 5, in an initial stage, the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the fourth slave BMS 120d, and the fifth slave BMS 120e may be provided. The embodiment of Figure 6 is an embodiment in which the fourth slave BMS 120d is replaced by the sixth slave BMS 120f, and the fifth slave BMS 120e is replaced by the seventh slave BMS 120g of the plurality of slave BMS 120s in an initial stage. The NV values ​​of the first slave BMS 120a, the second slave BMS 120b, and the third slave BMS 120c can be A, the NV value of the sixth replaced slave BMS 120f can be B, and the NV value of the seventh replaced slave BMS 120g can be C. That is, the NV values ​​of the replaced slave BMS 120f, 120g can be different from the NV value of the existing slave BMS 120a, 120b, 120c. The embodiment in FIG.7 is an embodiment in which the plurality of 120 slave BMS units are grouped based on NV values. The plurality of 120 slave BMSs can be configured to group slave BMSs with the same NV value, creating a primary group and at least one secondary group based on the number of slave BMSs included. For example, in the implementation shown in Figure 7, the plurality of 120 slave BMSs can communicate with each other to check each other's NV value. Specifically, each of the plurality of 120 slave BMSs can send data, including its own ID and NV value, to the other slave BMSs. The plurality of 120 slave BMSs can then check the NV value of another slave BMS using the data received from that other slave BMS. Three slave BMS 120a, 120b, 120c can have the NV value of A, one slave BMS 120f can have the NV value of B, and one slave BMS 120g can have the NV value of C. Among the plurality of slave BMS 120, slave BMS that have the same NV value can generate a group.A first group G1 may include the first slave BMS 120a, the second slave BMS 120b, and the third slave BMS 120c. A second group G2 may include the sixth slave BMS 120f, and a third group G3 may include the seventh slave BMS 120g. Furthermore, the plurality of BMS slaves 120 can establish a group that has the largest number of BMS slaves as a primary group, and the remaining groups can be established as secondary groups. For example, in the implementation of FIG. 7, the first group G1, which includes the three slave BMS 120a, 120b, 120c, can be configured as a main group, and the second group G2 and the third group G3 can be configured as the secondary groups. The plurality of 120 slave BMSs can be configured to establish any one of the plurality of 120 slave BMSs included in the main group as the representative BMS. Specifically, the plurality of 120 slave BMSs can be configured to establish a slave BMS that has an ID that corresponds to a pre-set condition among the plurality of 120 slave BMSs included in the main group as the representative BMS. For example, the slave BMS with the lowest ID among the plurality of 120 slave BMSs included in the main group can be established as the representative BMS. In the embodiment of FIG. 7, the first slave BMS 120a can be established as the representative BMS. As another example, the slave BMS with the largest ID among the 120 slave BMSs included in the parent group can be designated as the representative BMS. In other words, since the 120 slave BMSs included in the parent group have the same NV value, any slave BMS within the parent group can be designated as the representative BMS. The plurality of 120 slave BMSs can be configured to set the slave BMS included in at least one subgroup as the target BMS. The NV values ​​of all slave BMSs included in the secondary group may differ from the NV values ​​of the plurality of 120 slave BMSs included in the primary group. Therefore, all slave BMSs included in the secondary group may be set as the target BMS. The implementation of FIG.8 is an implementation in which the NV values ​​of the sixth slave BMS 120f and the seventh slave BMS 120g, established as the target BMS, are updated. The source BMS can be determined based on whether the standardization request originates from the master BMS (110) and the type of standardization request received. Additionally, the source BMS can update all NV values ​​in the target BMSs by sending its own NV value to the target BMS. For example, in the implementation of FIG. 8, the first slave BMS 120a is assumed to be set as the source BMS. The first slave BMS 120a can send its NV value to the sixth slave BMS 120f and the seventh slave BMS 120g. The sixth slave BMS 120f and the seventh slave BMS 120g can receive the NV value from the first slave BMS 120a and update their NV values. Consequently, the NV values ​​of the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the sixth slave BMS 120f, and the seventh slave BMS 120g can all be unified as A. That is, the BMS 100 management apparatus according to an embodiment of the present disclosure has the advantage that the NV values ​​of the plurality of slave BMSs can synchronize themselves even if the NV values ​​of the slave BMSs are not individually set by the user. Meanwhile, it is assumed that, unlike the implementation in FIGS. 5 to 8, six slave BMSs are initially provided, and three slave BMSs are replaced. If the NV values ​​of the three replaced slave BMSs are all the same, given that all three slave BMSs have the same NV values, establishing a primary group and a secondary group may not be straightforward. If the group of the replaced slave BMS is set as the primary group, there may be an issue where the NV values ​​of the existing slave BMSs are updated to the NV value of the replaced slave BMS. To prevent this problem, the master BMS 110 can be configured to store the NV value from the source BMS at the previous update time as the reference NV value. Additionally, when multiple NV values ​​received from multiple slave BMS 120s are classified as having the same number, the master BMS 110 can be configured to use the ID of any one of the multiple slave BMS 120s that have the same NV value as the reference NV value among the multiple NV values, using it as the source ID. In other words, the master BMS 110 can store the reference NV value at the previous update time in advance, and then sort the NV value received from the multiple slave BMS 120s itself. As a result of the sorting, when the same number of slave BMSs are sorted, the master BMS 110 can set the ID of the slave BMS that has the same NV value as the reference NV value as the source ID. In this case, even if there is no input for the ID from outside, the master BMS 110 can directly set the source ID. Consequently, even if multiple groups containing the same number of slave BMSs are generated, the NV values ​​of the multiple slave BMS 120s can be updated normally based on the source ID set by the master BMS 110. The BMS 100 management apparatus, according to an embodiment of this disclosure, may be included in an energy storage system (ESS). In general, the energy storage system applied to a power plant driving a large-scale electrical grid, or to a building or factory that consumes a large amount of energy, includes a plurality of battery racks, each containing a plurality of battery modules. Furthermore, the plurality of such battery racks are configured to form a battery bank, and a plurality of battery banks are configured to form a section. For example, the master BMS 110 may be a bank battery management system (BBMS) corresponding to the battery bank, and each of the plurality of slave BMS 120 may be a rack battery management system (RBMS) corresponding to a corresponding battery rack. Therefore, when the slave BMSs are replaced for some of the plurality of battery racks, the NV values ​​of the replaced slave BMSs can be updated according to the BMS 100 management apparatus. FIG. 9 is a diagram that schematically shows a BMS management method according to another embodiment of the present disclosure. Preferably, each stage of the BMS management method can be carried out by the BMS management apparatus 100 which includes the master BMS 110 and the plurality of slave BMS 120. Hereafter in this document, for convenience of description, content that overlaps with the content described above will be omitted or briefly described. Referring to FIG.9, the BMS management method may include an NV value confirmation request stage (S100), an NV value submission stage (S200), a representative BMS and target BMS establishment stage (S300), a uniformization request submission stage (S400), a source BMS establishment stage (S500), and an NV value update stage (S600). The NV value confirmation request stage (S100) is a stage of sending an NV value confirmation request to the plurality of slave BMS 120, and can be performed by the master BMS 110. The NV value sending stage (S200) is a stage of sending each NV value to the master BMS 110 when the NV value confirmation request is received from the master BMS 110, and can be performed by the plurality of slave BMS 120. Each of the plurality of BMS slaves 120 can send its NV value to the BMS master 110 as a response to the NV value confirmation request. The representative BMS and target BMS establishment stage (S300) is a stage of establishing a representative BMS and a target BMS based on the plurality of NV values, and can be carried out by the plurality of slave BMS 120. The establishment stage of the representative BMS and the target BMS (S300) will be described in detail with reference to FIG. 10. FIG. 10 is a diagram that schematically shows the establishment stage of the representative BMS and the target BMS S300 in the BMS management method according to another embodiment of this disclosure. The stage of establishing the representative BMS and the target BMS (S300) may include stage S310, stage S320, stage S330 and stage S340. In stage S310, each of the plurality of 120 slave BMSs can check its NV value and the NV values ​​of the other slave BMSs. For example, in the implementation of FIG.7, each of the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the sixth slave BMS 120f, and the seventh slave BMS 120g can check all of its NV value and the NV values ​​of the other slave BMSs. In stage S320, among the plurality of slave BMS 120, slave BMSs with the same NV value can form a group. Furthermore, among the generated groups, one group containing the largest number of slave BMSs can be designated as the primary group, and the remaining groups can be designated as secondary groups. For example, in the implementation shown in FIG. 7, the first slave BMS 120a, the second slave BMS 120b, and the third slave BMS 120c, all sharing the same NV value of A, can be classified as the first group G1. The sixth slave BMS 120f, with an NV value of B, can be classified as the second group G2. The seventh slave BMS 120g, with an NV value of C, can be classified as the third group G3. Additionally, the first group G1, containing the largest number of slave BMSs, can be designated as the primary group, and the remaining groups (the second group G2 and the third group G3) can be designated as secondary groups. At stage S330, any one of the plurality of slave BMS 120 can be designated as the representative BMS. Specifically, any one of the plurality of slave BMS 120 belonging to the main group can be designated as the representative BMS. For example, in the implementation of FIG. 7, the first slave BMS 120a included in the first group G1, which is a main group, can be established as the representative BMS. In the S340 stage, at least one slave BMS belonging to the secondary group can be established as the target BMS. For example, in the implementation of FIG.7, the sixth slave BMS 120f included in the second group G2 and the seventh slave BMS 120g included in the third group G3 can be established as the target BMS. The standardization request sending stage (S400) is a stage of sending a standardization request to the plurality of slave BMS 120 based on whether the source ID is set when a response to the NV value confirmation request is received from the plurality of slave BMS 120, and can be performed by the master BMS 110. When the source ID is established, the master BMS 110 can send a first uniformization request that includes the source ID to the plurality of slave BMS 120. Conversely, when the source ID is not established, the master BMS 110 can send a second uniformization request that does not include the source ID to the plurality of slave BMS 120. The origin BMS establishment stage (S500) is a stage of establishing the representative BMS or a slave BMS corresponding to the origin ID as the origin BMS according to the uniformization request received from the master BMS 110, and can be carried out by a plurality of slave BMS 120. The source BMS establishment stage (S500) will be described in detail with reference to FIG.11. FIG.11 is a diagram that schematically shows an S500 source BMS establishment stage in the BMS management method according to another embodiment of this disclosure. In stage S510, the plurality of slave BMS 120 can judge whether the first uniformization request is received from the master BMS 110. If the plurality of slave BMS 120 receives the first uniformization request, stage S520 can be performed, and if not, stage S530 can be performed. In step S520, the plurality of slave BMSs (120) can set the slave BMS corresponding to the source ID included in the first uniformization request as the source BMS. That is, even if the representative BMS is set beforehand in step S330, when the source ID is received from the master BMS (110), the slave BMS corresponding to that source ID can be set as the source BMS. After that, the NV value update step (S600) can be performed. For example, in the implementation of FIG. 7, it is assumed that the source ID included in the first standardization request received by the plurality of slave BMSs 120 from the master BMS 110 is 2. In this case, the second slave BMS 120b, which has an ID corresponding to the source ID, can be set as the source BMS. That is, even if the representative BMS is set as the first slave BMS 120a in stage S330, the second slave BMS 120b, which corresponds to the source ID, can be set as the source BMS. In stage S530, the plurality of slave BMS 120 can judge whether the second uniformization request is received from the master BMS 110. If the plurality of slave BMS 120 receives the second uniformization request, stage S550 can be performed, and if not, stage S540 can be performed. In step S540, the plurality of slave BMSs 120 can determine whether a predetermined time has elapsed after the uniformization request (the first and second uniformization requests) has not been received from the master BMS 110 since the point in time when the representative BMS and the target BMS were established. If the predetermined time has elapsed, step S550 can be performed; otherwise, step S510 can be performed again. In other words, the plurality of slave BMSs (120) can wait for the uniformization request to be received for a predetermined time after the representative BMS and target BMS establishment stage (S300). However, if the uniformization request is not received within a predetermined time, stage S550 can be performed to update the NV values ​​of the plurality of slave BMSs (120) normally. Step S550 is a step to establish the representative BMS set in step S330 as the source BMS. That is, the plurality of slave BMSs 120 can set a representative BMS they themselves established as the source BMS even if the source BMS is not determined by the master BMS 110 (even if the first uniformization request including the source ID is not received). For example, in the implementation of FIG.7, the first slave BMS 120a set as the representative BMS can be set as the origin BMS. The NV value update stage (S600) is an NV value update stage of the target BMS according to the NV value of the source BMS, and can be performed by a plurality of 120 slave BMSs. The source BMS can send its NV value to the destination BMS. The destination BMS, upon receiving the NV value, can update its own NV value based on the received NV value. For example, in the implementation of FIG. 7, the first slave BMS 120a, set as the source BMS, can send the NV value from A to the sixth slave BMS 120f and the seventh slave BMS 120g, set as the target BMS. The sixth slave BMS 120f and the seventh slave BMS 120g can update their NV values ​​to the NV value received from A. Consequently, in the implementation of FIG. 8, the NV values ​​of the first slave BMS 120a, the sixth slave BMS 120f, and the seventh slave BMS 120g can all be the same. The embodiments described herein may not be implemented solely through a device and method, but may be implemented through a program that performs a function corresponding to the configuration of the embodiments described herein, or through a recording medium on which the program is recorded. The program or recording medium can be readily implemented by those skilled in the art from the foregoing description of the embodiments. Reference signs 100: BMS management device 110: Master BMS 120: plurality of slave BMS

Claims

1. A BMS management apparatus (100) comprising a master BMS (110) and a plurality of slave BMSs (120), wherein the master BMS (110) is configured to send a non-volatile value (NV) confirmation request to the plurality of slave BMSs, and to send a corresponding uniformization request if a source ID among the IDs of the plurality of slave BMSs is established in the plurality of slave BMSs to synchronize the NV values ​​of the plurality of slave BMSs, when a response to the NV value confirmation request is received from the plurality of slave BMSs; and the plurality of slave BMSs is configured to send each NV value to the master BMS when the NV value confirmation request is received from the master BMS, establishing a representative BMS and a target BMS among the plurality of slave BMSs based on the plurality of NV values.

1. Establishing the representative BMS or a slave BMS corresponding to the source ID as a source BMS, and updating an NV value of the target BMS so that it is identical to the NV value of the source BMS.

2. The BMS management apparatus according to claim 1, wherein when an ID is received for any one of the plurality of slave BMSs, the master BMS is configured to set the received ID as the source ID.

3. The BMS management apparatus according to claim 2, wherein the master BMS is configured to send a first uniformization request that includes the source ID to the plurality of slave BMSs when the source ID is set, and wherein the master BMS is configured to send a second uniformization request that does not include the source ID to the plurality of slave BMSs when the source ID is not set.

4. The BMS management apparatus according to claim 3,wherein the plurality of slave BMSs is configured to establish a slave BMS corresponding to the source ID as the source BMS upon receipt of the first standardization request, and wherein the plurality of slave BMSs is configured to establish the representative BMS as the source BMS upon receipt of the second standardization request.

5. The BMS management apparatus according to claim 1, wherein after establishing the representative BMS and the target BMS, when no standardization request is received for a predetermined time, the plurality of slave BMSs are configured to establish the representative BMS as the source BMS.

6. The BMS management apparatus according to claim 1, wherein the plurality of slave BMSs is configured to generate groups (G1, G2, G3), which include a primary group (G1) and at least one secondary group (G2, G3).G3) according to the NV values ​​of the plurality of slave BMSs, wherein slave BMSs having the same NV value are included in the same group; wherein the generation of the main group and the at least one secondary group is carried out according to the number of slave BMSs included in the groups, the main group being the group with the largest number of slave BMSs, establishing any one of the plurality of slave BMSs included in the main group as the representative BMS, and establishing a slave BMS included in the at least one secondary group as the target BMS.

7. The BMS management apparatus according to claim 6, wherein the plurality of slave BMSs is configured to establish a slave BMS having an ID that corresponds to a pre-established condition among the plurality of slave BMSs included in the main group as the representative BMS.

8. The BMS management apparatus according to claim 1,wherein the master BMS is configured to store the NV value of the source BMS at a previous update time as a reference NV value, and when the plurality of NV values ​​received from the plurality of slave BMSs are sorted into groups of the same NV value, the master BMS is configured to set the ID of any one of the plurality of slave BMSs that have the same NV value as the reference NV value as the source ID.

9. The BMS management apparatus according to claim 1, wherein the source BMS is configured to receive, if the NV value is updated, an updated NV value from the target BMS, and send a uniformization completion notification or a uniformization failure notification to the master BMS depending on whether the updated NV value received from the target BMS is the same as the NV value of the source BMS.

10. An energy storage system,comprising the BMS management apparatus according to any one of claims 1 to 9.

11. A BMS management method, which is carried out by the BMS management apparatus according to claim 1, comprising: a non-volatile value confirmation request step, NV,(S100) of sending an NV value confirmation request to the plurality of slave BMSs; an NV value sending stage (S200) of sending each NV value to the master BMS when the NV value confirmation request is received from the master BMS; a representative BMS and target BMS establishment stage (S300) of establishing a representative BMS and a target BMS among the plurality of slave BMSs based on the plurality of NV values; a uniformization request sending stage (S400) of sending a corresponding uniformization request if a source ID among the IDs of the plurality of slave BMSs is established in the plurality of slave BMSs to synchronize the NV values ​​of the plurality of slave BMSs,when a response to the NV value confirmation request is received from the plurality of slave BMSs; a source BMS establishment stage (S500) to establish the representative BMS or a slave BMS corresponding to the source ID as a source BMS in accordance with the uniformization request received from the master BMS; and an NV value update stage (S600) to update an NV value of the target BMS so that it is identical to the NV value of the source BMS.

Images