Charging protocol management device and operation method thereof
The charging protocol management device optimizes battery charging by using a full cell-based map to adjust C-rates based on SOC and temperature, addressing inefficiencies and safety issues in high-capacity batteries.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- LG ENERGY SOLUTION LTD
- Filing Date
- 2025-10-20
- Publication Date
- 2026-06-25
AI Technical Summary
Existing charging protocols for high-capacity batteries do not accurately reflect the heat generation of actual battery cells, leading to inefficiencies and potential side effects such as heat generation and lithium deposition during charging.
A charging protocol management device that uses a charging map based on a full cell experiment to identify and adjust the C-rate in real-time based on battery State of Charge (SOC) and temperature, optimizing the charging process to minimize heat and lithium deposition.
The solution allows for real-time optimization of charging protocols, reducing charging time while minimizing heat and lithium deposition, thus enhancing the safety and efficiency of high-capacity battery charging.
Smart Images

Figure KR2025016597_25062026_PF_FP_ABST
Abstract
Description
Charging protocol management device and method of operation thereof
[0001] Cross-citation with related applications
[0002] The present invention claims the benefit of priority based on Korean Patent Application No. 10-2024-0188872 filed on December 17, 2024, and includes all contents disclosed in the document of said Korean patent application as part of this specification.
[0003] Technology field
[0004] The embodiments disclosed in this document relate to a charging protocol management device and a method of operating the same.
[0005] Recently, active research and development on secondary batteries has been underway. Here, the term "secondary battery" refers to a rechargeable battery, encompassing conventional Ni / Cd and Ni / MH batteries as well as the more recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of significantly higher energy density compared to conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form factor, making them suitable for use as power sources for mobile devices. Recently, their scope of application has expanded to include electric vehicles, drawing attention as a next-generation energy storage medium.
[0006] As the industrial sectors utilizing batteries expand, the demand for high-capacity batteries is also increasing. While increasing battery capacity offers the advantage of extended usage time, it also increases the charging time required. To address this charging time issue, using high current can shorten charging times, but this leads to side effects such as heat generation and lithium deposition. Consequently, active research is currently being conducted to design charging protocols that can charge high-capacity batteries in a short time while simultaneously minimizing these side effects.
[0007] A charging protocol can be designed using a charging map that includes the charging depth according to the battery temperature and SOC. Conventionally, to obtain a charging map, a 3-electrode cell was fabricated, and the charging map was obtained through charging experiments on the 3-electrode cell.
[0008] However, using a 3-electrode cell presents a problem in that it is difficult to reflect the amount of heat generated when the actual battery cell is charged. Accordingly, there is a problem in that a charging map generated based on the charging content of a 3-electrode cell and a charging protocol based thereon do not reflect the amount of heat generated by the actual battery cell.
[0009] The technical problems of the embodiments disclosed in this document are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by those skilled in the art from the description below.
[0010] A charging protocol management device according to one embodiment disclosed in this document may include: an interface for acquiring the SOC and temperature of a battery; and a controller for identifying a first C-rate corresponding to the SOC and the temperature, identifying charging information including a change in the SOC and a change in the temperature during the process of charging the battery based on the first C-rate, and determining whether to change the C-rate based on the result of determining whether the charging information corresponds to the first C-rate.
[0011] In one embodiment, the controller can identify the first C-rate based on a charging map including a reference C-rate according to a reference SOC for a reference battery maintaining a reference temperature.
[0012] In one embodiment, the reference SOC may correspond to the upper charging depth when charging the reference battery based on the reference C-rate.
[0013] In one embodiment, if the controller determines that the changed SOC and the changed temperature based on the charge map do not correspond to the first C-rate, it may identify a second C-rate corresponding to the changed SOC and the changed temperature and change the first C-rate to the second C-rate.
[0014] In one embodiment, the controller can generate a charging protocol for the battery based on whether the C-rate is changed.
[0015] A method of operation of a charging protocol management device according to an embodiment disclosed in this document may include: acquiring the SOC and temperature of a battery; identifying a first C-rate corresponding to the SOC and the temperature; identifying charging information including a change in the SOC and a change in the temperature during the process of charging the battery based on the first C-rate; determining whether the charging information corresponds to the first C-rate; and determining whether to change the C-rate based on the result of the determining operation.
[0016] In one embodiment, the operation of identifying the first C-rate may include the operation of identifying the first C-rate based on a charging map containing a reference C-rate according to a reference SOC for a reference battery maintaining a reference temperature.
[0017] In one embodiment, the reference SOC may correspond to the upper charging depth when charging the reference battery based on the reference C-rate.
[0018] In one embodiment, the operation of determining whether to change the C-rate may include, when it is determined based on the charging map that the changed SOC and the changed temperature do not correspond to the first C-rate, an operation of identifying a second C-rate corresponding to the changed SOC and the changed temperature, and an operation of changing the first C-rate to the second C-rate.
[0019] In one embodiment, the method of operation of the charging protocol management device may further include the operation of generating a charging protocol for the battery based on whether the C-rate is changed.
[0020] The charging protocol management device and the method of operation thereof according to the various embodiments disclosed in this document utilize a charging map obtained through a charging experiment using a full cell rather than a 3-electrode cell, so a charging map reflecting the heat generation of the actual battery cell can be used.
[0021] The charging protocol management device and the method of operation thereof according to the various embodiments disclosed in this document can identify changes in SOC and temperature during the process of charging a battery cell in real time, and can optimize the charging protocol according to the state of the battery by changing the C-rate based thereon.
[0022] The effects of the charging protocol management device and the method of operation thereof disclosed in this document are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art in accordance with the disclosure of this document.
[0023] FIG. 1 is a block diagram of a charging protocol management system according to one embodiment disclosed in this document.
[0024] FIG. 2 illustrates a battery pack according to one embodiment disclosed in this document.
[0025] FIG. 3 illustrates the SOC-internal resistance profile of a reference battery according to one embodiment disclosed in this document.
[0026] FIG. 4 illustrates a charge map generated based on the SOC-internal resistance profile of a reference battery according to one embodiment disclosed in this document.
[0027] FIG. 5 illustrates an SOC-voltage profile during the process of charging a battery based on a first charging protocol according to one embodiment disclosed in this document.
[0028] FIG. 6 illustrates an SOC-voltage profile during the process of charging a battery based on a second charging protocol according to one embodiment disclosed in this document.
[0029] FIG. 7 illustrates an SOC-voltage profile during the process of charging a battery based on a third charging protocol according to an embodiment disclosed in this document.
[0030] FIG. 8 illustrates the result of charging a battery based on the first to third charging protocols according to an embodiment disclosed in this document.
[0031] FIG. 9 is a flowchart of the operation method of a charging protocol management device according to one embodiment disclosed in this document.
[0032] FIG. 10 illustrates a computing system for executing operations of a charging protocol management device according to an embodiment disclosed in this document.
[0033] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components.
[0034] Hereinafter, embodiments of the present invention are described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments and should be understood to include various modifications, equivalents, and / or alternatives of the embodiments of the present invention.
[0035] The embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise.
[0036] In this document, each of the phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B, or C” may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” “first,” “second,” “A,” “B,” “(a),” or “(b)” may be used simply to distinguish a component from another component and, unless specifically stated otherwise, do not limit the components in any other aspect (e.g., importance or order).
[0037] In this document, where it is stated that any (e.g., 1) component is "connected," "coupled," or "joined" to another (e.g., 2) component, with or without the terms "functionally" or "communicationly," or where it is stated that the component is "coupled" or "connected," it means that the component may be connected to the other component directly (e.g., by wire or wirelessly) or indirectly (e.g., through a 3) component.
[0038] Methods according to the various embodiments disclosed in this document may be provided as part of a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory, CD-ROM) or distributed online (e.g., download or upload) through an application store or directly between two user devices. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.
[0039] According to the embodiments disclosed in this document, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to the embodiments disclosed in this document, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the components of the multiple components in the same or similar manner as those performed by the corresponding components among the multiple components prior to the integration. According to the embodiments disclosed in this document, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.
[0040] FIG. 1 is a block diagram of a charging protocol management system (1) according to one embodiment disclosed in this document.
[0041] Referring to FIG. 1, the charging protocol management system (1) may include a charging protocol management device (10), a charger / discharger (12), and battery units (120, 140, 160). Although FIG. 1 is illustrated as not including the charging protocol management device (10) in the charger / discharger (12), it is not limited thereto, and the charging protocol management device (10) may be included in the charger / discharger (12). Each of the battery units (120, 140, 160) in FIG. 1 may correspond to any one of a battery rack, a battery pack, and a battery module.
[0042] The charging protocol management device (10) may be connected to the charging / discharging device (12) via wired and / or wireless connections. In one embodiment, the connection between the charging protocol management device (10) and the charging / discharging device (12) may be a communication connection via a wired and / or wireless network. In one embodiment, the wired network may be based on a local area network (LAN) communication or power line communication. In one embodiment, the wireless network may be based on a short-range communication network (e.g., Bluetooth, WiFi (wireless fidelity), or IrDA (infrared data association)), or a long-range communication network (cellular network, 4G network, 5G network).
[0043] In one embodiment, the connection between the charging protocol management device (10) and the charger / discharger (12) may be a connection via a device-to-device communication method (e.g., bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).
[0044] The charger / discharger (12) can charge the battery units (120, 140, 160). During the process of charging the battery units (120, 140, 160), the charger / discharger (12) can obtain values (or information) related to the state of each of the battery units (120, 140, 160) and / or battery cells (121, 122, 123). In one embodiment, the values related to the state may include one or more values for the voltage, current, resistance, state of charge (SOC), state of health (SOH), or temperature, or a combination thereof, of each of the battery units (120, 140, 160). Each of the battery units (120, 140, 160) may include one or more battery cells (121, 122, 123). For example, the battery cells (121, 122, 123) included in the first battery unit (120) may be electrically connected to each other (series and / or parallel connection). According to an embodiment, the battery cells (121, 122, 123) may be included in the first battery unit (120) in an electrically separated state. In FIG. 1, for convenience of explanation, only the first battery cell (121) to the third battery cell (123) included in the first battery unit (120) have been described, but this is not limited thereto, and the second battery unit (140) and the third battery unit (160) may also include one or more battery cells.
[0045] In one embodiment, the charger / discharger (12) may obtain values (or information) related to the state of each of one or more battery cells (121, 122, 123). In one embodiment, the values related to the state may include one or more values for the voltage, current, resistance, state of charge (SOC), state of health (SOH), or temperature, or a combination thereof, of each of the battery cells (121, 122, 123). Hereinafter, the values related to the state may be referred to as 'state values'. Additionally, for convenience of explanation, the battery units (120, 140, 160) and each of the battery cells (121, 122, 123) will be referred to as batteries in the following description.
[0046] The charging protocol management device (10) can obtain a status value of the battery units (120, 140, 160). The charging protocol management device (10) can identify a first C-rate corresponding to the status value of the battery units (120, 140, 160). The charging protocol management device (10) can change the first C-rate if the status value obtained during the process of charging the battery units (120, 140, 160) based on the first C-rate does not correspond to the first C-rate. The charging protocol management device (10) can generate a charging protocol based on the change in the C-rate according to the status value included in the process until the charging of the battery units (120, 140, 160) is completed.
[0047] In one embodiment, the charging protocol management device (10) may be included in a BMS capable of diagnosing battery cells included in an electronic device, and operations performed by the charging protocol management device (10) may be performed in the BMS. In one embodiment, the charging protocol management device (10) may be included in a server or a charger / discharger capable of diagnosing battery cells outside the electronic device, and operations performed by the charging protocol management device (10) may be performed in an external server or charger / discharger.
[0048] Hereinafter, for the convenience of explanation, the operation performed by each of the components included in the charging protocol management device (10) to diagnose whether the first battery cell (121) is abnormal will be described.
[0049] The charging protocol management device (10) may include an interface (100) and a controller (102). According to an embodiment, the charging protocol management device (10) illustrated in FIG. 1 may further include at least one component (e.g., a display, an input device, or an output device) in addition to the components illustrated in FIG. 1.
[0050] The interface (100) can obtain the SOC and temperature of the first battery cell (121). The interface (100) can obtain the SOC and temperature before charging of the first battery cell (121) begins, as well as the SOC and temperature during the charging process of the first battery cell (121). According to various embodiments, the interface (100) may include various interface circuits for obtaining signals, information and / or data, such as sensors and communication circuits.
[0051] The controller (102) can identify a first C-rate corresponding to the SOC and temperature. The controller (102) can identify a first C-rate corresponding to the SOC and temperature before charging of the first battery cell (121).
[0052] In one embodiment, the controller (102) can identify a first C-rate corresponding to the SOC and temperature of the first battery cell (121) based on a charging map. Here, the charging map can be obtained through an interface (100) if stored in an external device, or it may be stored in a memory (not shown) included in a charging protocol management device (10). For a reference battery maintaining a reference temperature, a reference C-rate according to a reference SOC may be included. The reference battery may include a full cell having the same manufacturing specifications as the first battery cell (121) and may be charged while maintaining a reference temperature by a cooling device, etc. The reference SOC may refer to the SOC during the process of charging the reference battery at a reference temperature. Specific details regarding the charging map will be described later in FIGS. 3 and FIGS. 4.
[0053] The controller (102) can identify charging information including changes in the SOC and temperature of the first battery cell (121) during the process of charging the first battery cell (121) based on the first C-rate.
[0054] The controller (102) can determine whether the charging information corresponds to the first C-rate. For example, assuming the first C-rate corresponds to the C-rate when the SOC is 20% and the temperature is 25 degrees Celsius, if the SOC of the first battery cell (121) changes to 30% and the temperature changes to 30 degrees Celsius during the charging process, the controller (102) can determine that the charging information does not correspond to the first C-rate.
[0055] The controller (102) can determine whether to change the C-rate based on the result of determining whether the charging information corresponds to the first C-rate. If the controller (102) determines that the charging information corresponds to the first C-rate, it can generate a command to continue charging the first battery cell (121) while maintaining the first C-rate. If the controller (102) determines that the charging information does not correspond to the first C-rate, it can identify a second C-rate corresponding to the charging information.
[0056] If the controller (102) determines that the charging information and the first C-rate do not correspond, it may generate a command to change the first C-rate to the second C-rate. If the controller (102) determines that the charging information and the first C-rate do not correspond, it may control the charger / discharger (12) to change the first C-rate to the second C-rate.
[0057] The controller (102) can generate a charging protocol for the first battery cell (121) based on whether the C-rate changes. The controller (102) can generate a charging protocol for the first battery cell (121) based on charging information and changes in the C-rate during the charging process of the first battery cell (121).
[0058] In FIG. 1, only the content of the controller (102) changing the first C-rate to the second C-rate is described, but this is for convenience of explanation only and the embodiments of the present invention are not limited thereto. For example, the controller (102) may continuously change from the nth C-rate (n: natural number) to the (n+1)th C-rate based on the battery charging information, and may maintain the first C-rate when the battery charging information corresponds to the first C-rate.
[0059] FIG. 2 illustrates a battery pack according to one embodiment disclosed in this document.
[0060] Referring to FIG. 2, the battery pack (2) may be included in an electronic device. Here, the electronic device may be a mobile device (e.g., mobile phone, laptop computer, smartphone, smart pad), an electric vehicle (e.g., EV (electric vehicle), HEV (hybrid EV), PHEV (plug-in HEV), FCEV (fuel cell EV)), an energy storage system (ESS), or a battery swapping system (BSS).
[0061] The battery pack (2) may include a Battery Management System (BMS, 20) and battery units (120, 140, 160). The BMS (20) can diagnose the condition of the battery units (120, 140, 160) and the battery cells (121, 122, 123) included therein. For example, the BMS (20) can diagnose whether there is an abnormality during the charging process of the battery units (120, 140, 160) and / or battery cells (121, 122, 123) included in the battery pack (2), and can control the charging to stop if an abnormality is determined.
[0062] The BMS (20) may include a charging protocol management device (10). The BMS (20) can monitor whether the battery pack (2) is being charged based on a charging protocol generated by the charging protocol management device (10), and can control the charging to stop if it is not being charged based on the charging protocol.
[0063] In one embodiment, when the charging protocol management device (10) is located outside the BMS (20), the BMS (20) can receive a charging protocol generated by the charging protocol management device (10) from an external device or server.
[0064] In FIG. 2, the battery pack (2) is depicted as having three battery modules, but this is for convenience of explanation only, and the battery pack (2) may include one or more battery modules. Also, in FIG. 2, only the battery cells (121, 122, 123) included in the first battery unit (120) are depicted, but this is for convenience of explanation only, and the second battery unit (140) and the third battery unit (160) may also include multiple battery cells. Also, in FIG. 2, the multiple battery cells (121, 122, 123) included in the first battery unit (120) are depicted as having three, but this is not limited thereto, and each of the battery cells (121, 122, 123) may be configured to include n (n is a natural number greater than or equal to 2) battery cells. According to various embodiments, when the battery pack (2) has a Cell To Pack (CTP) structure, the battery pack (2) may be configured to include a plurality of battery cells (121, 122, 123) without distinction of battery units.
[0065] For convenience of explanation, battery cells, battery modules, battery packs, and battery units will be collectively referred to as batteries in the following description.
[0066] FIG. 3 illustrates an SOC-internal resistance profile of a reference battery according to an embodiment disclosed in this document. FIG. 4 illustrates a charge map generated based on the SOC-internal resistance profile of a reference battery according to an embodiment disclosed in this document. Hereinafter, the process of generating the charge map will be explained with reference to FIG. 3 and FIG. 4.
[0067] Referring to FIG. 3, the SOC-internal resistance profile (30) may include graphs showing the change in internal resistance according to the change in SOC during the process in which a reference battery is charged based on each of a plurality of C-rates (e.g., 0.5C, 1.0C, 2.0C, 3.0C). Based on the SOC-internal resistance profile (30), the upper charging depth for each of the plurality of C-rates can be determined.
[0068] Referring to FIG. 4, the charging map (40) may include a charging upper limit charging depth determined for each of a plurality of C-rates. Here, the determined charging upper limit charging depth may be a reference SOC. Referring to FIG. 3 and FIG. 4, the charging map (40) may be a lookup table that corresponds the charging upper limit charging depth for each C-rate determined based on the SOC-internal resistance profile (30) with the temperature (reference temperature) maintained during the charging process of the reference battery.
[0069] The charging protocol management device (10) can set the first C-rate to 2.7C to start charging the battery when the SOC and temperature before charging the battery are 25 degrees Celsius and the SOC is 30%.
[0070] The charging protocol management device (10) can identify a corresponding second C-rate when the battery's SOC becomes 35% and the temperature reaches 30 degrees Celsius after the battery has started charging at a first C-rate of 2.7C. For example, by referring to the charging map (40), the second C-rate may be 2.6C.
[0071] The charging protocol management device (10) can optimize an existing charging protocol into a new charging protocol. The charging protocol management device (10) can generate a new charging protocol by changing the C-rate to correspond to the charging information of the battery based on the charging map (40). Referring to FIG. 4, the first charging protocol (400) may be an optimal charging protocol when the temperature of the battery is maintained at 25 degrees Celsius. However, unlike a preliminary experiment in which a reference battery is charged using a cooling device to maintain a reference temperature, the temperature of the battery rises during the actual charging process. Therefore, the charging protocol management device (10) can optimize the first charging protocol (400) into a second charging protocol (410) or a third charging protocol (420). Here, the charging protocol management device (10) can generate a new charging protocol (third charging protocol) that optimizes the existing charging protocol (first charging protocol) based on the charging information of the battery by generating the third charging protocol (420).
[0072] FIG. 5 illustrates an SOC-voltage profile during the process of charging a battery based on a first charging protocol according to an embodiment disclosed in this document. FIG. 6 illustrates an SOC-voltage profile during the process of charging a battery based on a second charging protocol according to an embodiment disclosed in this document. FIG. 7 illustrates an SOC-voltage profile during the process of charging a battery based on a third charging protocol according to an embodiment disclosed in this document. FIG. 8 illustrates the result of charging a battery based on the first to third charging protocols according to an embodiment disclosed in this document.
[0073] Graphs (50) in FIG. 5 to Graph (70) in FIG. 7 may each be the result of charging a battery based on the first to third charging protocols described in FIG. 4. By referring to the graphs (50, 60, 70), changes in voltage (500, 600, 700) and temperature (502, 602, 702) when charging a battery based on the first to third charging protocols can be observed. By referring to the graphs (50, 60, 70), it can be observed that the maximum temperature is highest when charging a battery using the third charging protocol. Based on this, the charging protocol management device (10) can minimize lithium deposition by generating a third charging protocol that allows the battery to maintain a relatively high temperature.
[0074] Referring to the graph (80) of FIG. 8, changes in voltage (800, 810, 820) and temperature (802, 812, 822) when charging the battery based on the first to third charging protocols can be observed, and charging times (T1, T2, T3) according to each charging protocol can be observed. Referring to the graph (80), it can be observed that the charging time (T3) when charging the battery based on the third charging protocol is the shortest compared to the charging times (T1, T2) based on other charging protocols. Based on this, the charging protocol management device (10) can generate a charging protocol that shortens the charging time by changing the C-rate based on the battery's SOC and temperature.
[0075] Referring to FIGS. 5 to 8 together, the charging protocol management device (10) can minimize the occurrence of lithium precipitation and shorten the charging time by changing the C-rate based on the battery's SOC and temperature. In addition, the charging protocol management device (10) can generate a new charging protocol that reflects the changes in SOC and temperature that reflect the degradation, even if the changes in the battery's SOC and temperature differ from the existing ones as the battery degrades.
[0076] FIG. 9 is a flowchart of the operation method of a charging protocol management device according to one embodiment disclosed in this document.
[0077] Referring to FIG. 9, in operation 900, the charging protocol management device (10) can obtain the SOC and temperature of the battery. The charging protocol management device (10) can obtain the SOC and temperature of the battery. The charging protocol management device (10) can obtain the SOC and temperature before charging of the battery begins, as well as the SOC and temperature during the process of charging the battery.
[0078] In operation 910, the charging protocol management device (10) can identify a C-rate corresponding to the SOC and temperature of the battery. The charging protocol management device (10) can identify a first C-rate corresponding to the SOC and temperature of the battery before charging.
[0079] In one embodiment, a charging protocol management device (10) can identify a first C-rate corresponding to the SOC and temperature of the battery based on a charging map.
[0080] In operation 920, the charging protocol management device (10) can identify charging information including changes in SOC and temperature during the process of charging the battery based on the identified C-rate. The charging protocol management device (10) can identify charging information including changes in the battery's SOC and changes in temperature during the process of charging the battery based on the first C-rate.
[0081] In operation 930, the charging protocol management device (10) can determine whether the charging information corresponds to the identified C-rate. The charging protocol management device (10) can determine whether to change the C-rate based on the result of determining whether the charging information corresponds to the first C-rate. The charging protocol management device (10) returns to operation 920 if the charging information corresponds to the first C-rate (operation 930, YES), and performs operation 930 if the charging information does not correspond to the first C-rate (operation 930, NO).
[0082] In operation 940, the charging protocol management device (10) can determine whether charging has ended. Here, charging has ended may include the case where the battery's SOC reaches 100%. The charging protocol management device (10) can perform operation 950 if it is determined that charging has not ended (operation 940, NO), and perform operation 960 if it is determined that charging has ended (operation 940, YES).
[0083] In operation 950, the charging protocol management device (10) can newly identify a C-rate corresponding to the charging information and change the previously identified C-rate to the newly identified C-rate. If the charging protocol management device (10) determines that the charging information and the first C-rate do not correspond, it can generate a command to change the first C-rate to the second C-rate. If the charging protocol management device (10) determines that the charging information and the first C-rate do not correspond, it can control the charging / discharging device to change the first C-rate to the second C-rate.
[0084] In operation 960, the charging protocol management device (10) can generate a charging protocol. The charging protocol management device (10) can generate a charging protocol for the battery based on whether the C-rate changes. The charging protocol management device (10) can generate a charging protocol for the battery based on charging information and changes in the C-rate during the process of charging the battery.
[0085] FIG. 10 illustrates a computing system for executing operations of a charging protocol management device according to an embodiment disclosed in this document.
[0086] Referring to FIG. 10, a computing system (1000) according to one embodiment disclosed in this document may include an MCU (1010), a memory (1020), an input / output I / F (1030), and a communication I / F (1040).
[0087] The MCU (1010) may be a processor that executes various programs stored in memory (1020), processes various data from these programs, and performs the functions of the charging protocol management device (10) shown in the aforementioned FIGS. 1 to 9.
[0088] The memory (1020) can store various programs regarding the operation of the charging protocol management device (10). In addition, the memory (1020) can store operation data of the charging protocol management device (10) (e.g., charging map (40, see FIG. 4)).
[0089] These memories (1020) may be provided in multiple quantities as needed. The memories (1020) may be volatile memories or non-volatile memories. As volatile memories, the memory (1020) may use RAM, DRAM, SRAM, etc. As non-volatile memories, the memory (1020) may use ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. The memories (1020) listed above are merely examples and are not limited to these examples.
[0090] The input / output I / F (1030) can provide an interface that enables data transmission and reception between an input device (not shown), such as a keyboard, mouse, or touch panel, an output device (not shown), and an MCU (1010).
[0091] The communication I / F (1040) is configured to transmit and receive various data with a server and may be various devices capable of supporting wired or wireless communication. For example, through the communication I / F (1040), a program for diagnosing abnormalities or various data (e.g., status values) can be transmitted and received from a separately provided external server.
[0092] Terms such as "include," "compose," or "have" as used above, unless specifically stated otherwise, mean that the relevant component may be inherent; therefore, they should be interpreted as allowing for the inclusion of additional components rather than excluding them. All terms, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the embodiments disclosed in this document pertain, unless otherwise defined. Commonly used terms, such as those defined in advance, should be interpreted in accordance with their meaning in the context of the relevant technology and, unless explicitly defined in this document, should not be interpreted in an ideal or overly formal sense.
[0093] The foregoing description is merely an illustrative explanation of the technical concept disclosed in this document, and a person skilled in the art to which the embodiments disclosed in this document pertain can make various modifications and variations within the scope of the essential characteristics of the embodiments disclosed in this document. Accordingly, the embodiments disclosed in this document are intended to explain, not limit, the technical concept of the embodiments disclosed in this document, and the scope of the technical concept disclosed in this document is not limited by these embodiments. The scope of protection of the technical concept disclosed in this document shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of this document.
Claims
1. An interface for acquiring the battery's SOC and temperature; and Identifying a first C-rate corresponding to the above SOC and the above temperature, and Identifying charging information including changes in SOC and changes in temperature during the process of charging the battery based on the first C-rate, and A controller comprising a controller that determines whether to change the C-rate based on the result of determining whether the above charging information and the above first C-rate correspond. Charging protocol management device.
2. In Claim 1, The above controller is, Identifying the first C-rate based on a charging map including a reference C-rate according to a reference SOC for a reference battery maintaining a reference temperature, Charging protocol management device.
3. In Claim 2, The above reference SOC corresponds to the upper charging depth when charging the above reference battery based on the above reference C-rate, Charging protocol management device.
4. In Claim 2, The above controller is, If it is determined that the changed SOC and changed temperature based on the above charging map do not correspond to the first C-rate, a second C-rate corresponding to the changed SOC and changed temperature is identified, and Changing the above first C-rate to the above second C-rate, Charging protocol management device.
5. In Claim 1, The above controller is, Generating a charging protocol for the battery based on whether the above C-rate is changed, Charging protocol management device.
6. Operation to obtain the battery's SOC and temperature; An operation to identify a first C-rate corresponding to the above SOC and the above temperature; An operation of identifying charging information including a change in SOC and a change in temperature during the process in which the battery is charged based on the first C-rate; An operation to determine whether the above charging information and the above first C-rate correspond; and A method including an operation to determine whether to change the C-rate based on the result of the above-determined operation, Charging protocol management device.
7. In Claim 6, The operation of identifying the first C-rate above is, The operation of identifying the first C-rate based on a charging map including a reference C-rate according to a reference SOC for a reference battery maintaining a reference temperature, Method of operation of a charging protocol management device.
8. In Claim 7, The above reference SOC corresponds to the upper charging depth when charging the above reference battery based on the above reference C-rate, Method of operation of a charging protocol management device.
9. In Claim 7, The operation of determining whether to change the above C-rate is, An operation to identify a second C-rate corresponding to the changed SOC and the changed temperature when it is determined that the changed SOC and the changed temperature based on the charge map do not correspond to the first C-rate, and The operation of changing the first C-rate to the second C-rate, Method of operation of a charging protocol management device.
10. In Claim 6, Further including the operation of generating a charging protocol for the battery based on whether the above C-rate is changed, Method of operation of a charging protocol management device.