Battery charging device and battery management device

Abstract

To provide a battery management device that efficiently uses batteries based on their condition. [Solution] In the system, the battery charging device includes a communication unit that communicates with a battery management server, and a control unit that compares the charging status of at least one battery being charged, transmits the status information of the at least one battery to the battery management server, receives a charging profile of the at least one battery from the battery management server, and controls the charging of the at least one battery based on the received charging profile of the at least one battery.

Description

Technical Field

[0001] [Cross - reference to Related Applications] This invention claims the benefit of priority based on Korean Patent Application No. 10 - 2021 - 0117973, filed on September 3, 2021, and includes all the contents disclosed in the document of the Korean patent application as part of this specification.

[0002] The embodiments disclosed in this specification relate to a battery charging device and a battery management device.

Background Art

[0003] Recently, research and development on secondary batteries have been actively conducted. Here, a secondary battery is a battery that can be charged and discharged, meaning it includes all conventional Ni / Cd batteries, Ni / MH batteries, etc., and recent lithium - ion batteries. Among secondary batteries, lithium - ion batteries have the advantage of having a much higher energy density compared to conventional Ni / Cd batteries, Ni / MH batteries, etc. Also, since lithium - ion batteries can be manufactured in a small and lightweight form, they are used as a power source for mobile devices. Recently, their usage range has been extended to the power source of electric vehicles and they have attracted attention as a next - generation energy storage medium.

[0004] In the case of a mobile means using a battery, there may be a situation where the battery is exchanged for use. There may exist a charging station that charges and rents out such replaceable batteries, and a large number of replaceable batteries may be charged and rented out at the charging station. Since the degree of aging or degradation of the battery changes depending on the method of using the battery or the state of the battery, there may be a problem when managing a large number of batteries in the same way.

Summary of the Invention

Problems to be Solved by the Invention

[0005] One object of the embodiments disclosed herein is to provide a battery charging device that can control the charging of each battery to be efficient based on the state of each battery.

[0006] Another object of the embodiments disclosed herein is to provide a battery management device that can efficiently use a battery based on its state.

[0007] The technical problems of the embodiments disclosed herein are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description. [Means for solving the problem]

[0008] A battery charging device according to one embodiment disclosed herein may include a communication unit that communicates with a battery management server, and a control unit that compares the charge status of at least one battery being charged, transmits the status information of the at least one battery to the battery management server, receives a charge profile of the at least one battery from the battery management server, and controls the charging of the at least one battery based on the received charge profile of the at least one battery.

[0009] In one embodiment, the control unit can predict the State of Charge (SOC) of each of the at least one battery based on the charge profile of each battery, and predict the remaining driving range and failure probability based on the predicted SOC.

[0010] In one embodiment, the control unit can determine whether the at least one battery is available for loan based on the driving range and failure status of the at least one battery.

[0011] In one embodiment, the control unit can predict the lifespan of each of the at least one battery based on the charging profile of each battery, and determine whether or not the at least one battery is available for loan based on the predicted lifespan.

[0012] In one embodiment, each of the at least one batteries may have its own identification information set.

[0013] In one embodiment, the control unit can transmit the status of each of the at least one battery to the battery management server based on the identification information of each of the at least one battery, and can receive the charging profile of each of the at least one battery from the battery management server based on the identification information of each of the at least one battery.

[0014] In one embodiment, the charging profile of the at least one battery may be generated based on at least one of the following: battery state information when the at least one battery is being charged, and battery state information when the device containing the at least one battery is undergoing regenerative braking.

[0015] In one embodiment, the control unit can obtain the charge profile of the at least one battery from a battery management device included in the at least one battery.

[0016] A battery management device according to one embodiment disclosed herein may include a communication unit that communicates with a battery management server, and a control unit that transmits battery status information to the battery management server while the battery is in use, receives a battery discharge profile from the battery management server, and controls the battery to be used based on the discharge profile.

[0017] In one embodiment, the control unit can receive the battery's charge profile from the battery management server and, when the battery is connected to a charging device, transmit the charge profile to the charging device.

[0018] In one embodiment, the control unit can transmit battery charge status information to the battery management server when the battery is used for regenerative braking.

[0019] In one embodiment, the battery is assigned identification information, the control unit transmits the battery status information to the battery management server based on the identification information, and can receive the discharge profile or charge profile from the battery management server based on the identification information.

[0020] In one embodiment, the control unit can predict at least one of the driving distance and the power limit based on the discharge profile.

[0021] In one embodiment, the control unit can determine whether the battery needs to be charged or replaced based on the predicted mileage or power limit. [Effects of the Invention]

[0022] A battery charging device according to one embodiment disclosed herein can be controlled to efficiently charge each battery based on a charging profile corresponding to the state of each battery.

[0023] A battery charging device according to one embodiment disclosed herein can predict the State of Charge (SOC) and lifespan based on the charging profile of each battery and select a loaner battery that meets the user's requirements.

[0024] The battery management device according to an embodiment disclosed in this specification can be controlled to efficiently use the battery based on the discharge profile of the battery.

[0025] The battery management device according to an embodiment disclosed in this specification can predict the power limit or driving range based on the charging or discharging profile of the battery and can be controlled to replace the battery.

[0026] In addition, various effects directly or indirectly understood through this specification can be provided.

Brief Description of Drawings

[0027] [Figure 1] It is a diagram showing a system including a battery charging device and a battery management device according to an embodiment disclosed in this specification. [Figure 2] It is a block diagram showing a battery charging device according to an embodiment disclosed in this specification. [Figure 3] It is a block diagram showing a battery management device according to an embodiment disclosed in this specification. [Figure 4] It is a diagram showing the flow of information related to a battery according to an embodiment disclosed in this specification being transmitted. [Figure 5] It is a block diagram showing the hardware configuration of a computing system embodying a control method of a battery management device according to an embodiment disclosed in this specification.

Modes for Carrying Out the Invention

[0028] The embodiments disclosed herein will be described in detail below with reference to illustrative drawings. It should be noted that, in assigning reference numerals to the components in each drawing, the same component will be given the same reference numeral whenever possible, even if shown in other drawings. Furthermore, in describing the embodiments disclosed herein, if a specific description of such known configurations or functions is deemed to hinder understanding of the embodiments disclosed herein, such detailed description will be omitted.

[0029] In describing the components of the embodiments disclosed herein, terms such as First, Second, A, B, (a), (b), etc., may be used. Such terms are merely for distinguishing a component from other components and do not limit the nature, order, or sequence of the component. Furthermore, unless otherwise specifically defined, all terms used herein, including technical and scientific terms, have the same meaning as those generally understood by a person of ordinary skill in the art to which the embodiments disclosed herein belong. Terms identical to those defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art and not as ideally or excessively formal unless explicitly defined in this application.

[0030] Figure 1 shows a system that includes a battery charging device according to one embodiment disclosed herein.

[0031] Referring to Figure 1, a battery charging device 100 according to one embodiment disclosed herein can communicate with a battery management server 10, a user terminal 20, and a battery management device 200. In one embodiment, the battery charging device 100 shown in Figure 1 may be substantially identical to the battery charging device 100 shown in Figure 2, which will be described below. In one embodiment, the battery management device 200 shown in Figure 1 may be substantially identical to the battery management device 200 shown in Figure 3, which will be described below.

[0032] The battery charging device 100 can transmit status information of at least one battery connected to the battery charging device 100 to the battery management server 10. For example, the battery charging device 100 can transmit information comparing the charging data of at least one battery to the battery management server 10. The battery management server 10 can generate a charging profile based on the battery status information (or comparison information) received from the battery charging device 100 and transmit the generated charging profile to the battery charging device 100. Based on the received charging profile, the battery charging device 100 can control at least one battery connected to the battery charging device 100 to charge it efficiently.

[0033] The battery charging device 100 can receive requests from the user terminal 20. For example, the user terminal 20 can request the battery charging device 100 to lend a battery. The user terminal 20 can input the distance to be traveled using the battery, and the battery charging device 100 can select a battery to lend based on the input distance. For example, the battery charging device 100 can predict the current state of charge (SOC) of at least one battery, predict the remaining distance based on the current SOC, and lend a battery corresponding to the distance to be traveled input by the user terminal 20. In other words, the user terminal 20 can borrow a battery from the battery charging device 100 that corresponds to the distance to be traveled, and can use the battery efficiently.

[0034] The battery charger 100 can communicate with the battery management device 200 included in the battery connected to the battery charger 100. For example, the battery charger 100 can receive a battery charge profile from the battery management device 200. In this case, the battery charger 100 does not need to receive a battery charge profile from the battery management server 10, and can therefore charge the battery quickly. Alternatively, the battery charger 100 can transmit the charge profile received from the battery management server 10 to the battery management device 200, and the battery management device 200 can store the received charge profile in its internal storage. In this case, even if the battery management device 200 is subsequently connected to another charger, it can efficiently charge the battery by transmitting the charge profile to the other charger. In one embodiment, if the battery charger 100 is located in an area where communication is not possible, it may not be able to communicate with the battery management server 10. In this case, the battery charger 100 can be controlled to charge the battery based on the charge profile stored in the battery management device 200.

[0035] The battery management device 200 can communicate with the battery management server 10 and the charging device 100.

[0036] The battery management device 200 can transmit battery charge and / or discharge status information to the battery management server 10. The battery management server 10 can generate a battery charge and / or discharge profile based on the received battery charge and / or discharge status information. For example, if the battery management server 10 receives battery identification information along with the battery charge and / or discharge status information, it can store and / or transmit a battery charge and / or discharge profile corresponding to the received battery identification information. The battery management device 200 can receive the charge and / or discharge profile for the battery from the battery management server 10 and can control the battery so that it can be charged and / or discharged based on the received charge and / or discharge profile.

[0037] The battery management device 200 can transmit a charging profile to the charging device 100 when a battery is connected to the charging device 100. The charging device 100 can then charge the battery based on the received charging profile.

[0038] Figure 2 is a block diagram showing a battery charging device according to one embodiment disclosed herein. The battery charging device 100 in Figure 2 may be substantially identical to the battery charging device 100 in Figure 1.

[0039] A battery charging device 100 according to one embodiment disclosed herein may include a communication unit 110 and a control unit 120.

[0040] The communication unit 110 can communicate with the battery management server 10 (see Figure 1). The communication unit 110 can also communicate with the battery management device 200 (BMS, see Figure 1) included in at least one battery connected to the battery charging device 100. In one embodiment, the communication unit 110 includes a wireless communication circuit (e.g., a cellular communication circuit, a short-range wireless communication circuit, or a GNSS (global navigation satellite system) communication circuit) or a wired communication circuit (e.g., a LAN (local area network) communication circuit, or a power line communication circuit), and can communicate with external electronic devices via a short-range communication network such as Bluetooth®, WiFi Direct®, or IrDA (infrared data association), or a long-range communication network such as a cellular network, the Internet, or a computer network using the appropriate communication circuit. The various types of communication units 110 described above may be embodied in a single chip or each on separate chips.

[0041] The control unit 120 can acquire status information for at least one battery connected to the battery charging device 100. For example, the control unit 120 can acquire status information for at least one battery from a battery management device 200 included in each of the at least one battery. In one embodiment, the battery status information may include at least one of the following: battery voltage, current, temperature, and insulation resistance. The battery status information may also include, but is not limited to, parameters indicating the state of the battery, such as SOC (State of Charge) and SOH (State of Health).

[0042] The control unit 120 can compare the charge status of at least one battery being charged. For example, the control unit 120 can compare at least one of the following for each of the at least one batteries being charged: charge speed, charge level, state of charge (SOC), state of health (SOH), full charge feasibility, full charge speed, battery level, charge current, charge voltage, charge time, and failure feasibility.

[0043] The control unit 120 can transmit status information of at least one battery to the battery management server 10 via the communication unit 110. For example, the control unit 120 can transmit status information of at least one battery or comparison information regarding the charge state of at least one battery to the battery management server 10 via the communication unit 110. In one embodiment, the battery management server 10 can generate a battery charge profile based on the battery status information and charge state comparison information transmitted from the control unit 120.

[0044] The control unit 120 can receive a charge profile for at least one battery from the battery management server 10. For example, the battery charge profile may include at least one of the following: the number of battery charge cycles, the charging rate due to the charging voltage, the charging rate due to the charging current, the charging rate due to the charging time, the change in SOC due to the charging voltage, and the change in SOC due to the charging current. Alternatively, for example, the battery charge profile may have a graph relating to the charging current, voltage, and time at which the battery can be efficiently charged. In one embodiment, the charge profile for at least one battery may be generated based on at least one of the following: the state information of the battery when at least one battery is being charged, and the state information of the battery when the device containing at least one battery is undergoing regenerative braking. For example, the device containing at least one battery may include an automobile, bicycle, kick boat, drone, ESS, motorcycle, two-wheeled vehicle, three-wheeled vehicle, and other devices that can be driven using a battery power source.

[0045] The control unit 120 can control the charging of at least one battery based on the charging profile of at least one battery received. For example, the control unit 120 can control each battery to be charged efficiently based on the charging profile of each of the at least one battery received.

[0046] The control unit 120 can predict the State of Charge (SOC) of at least one battery based on the charging profile of at least one battery. For example, the control unit 120 can predict the SOC of a battery based on the charging voltage of the battery included in the charging profile. Alternatively, the control unit 120 can predict the SOC of a battery based on the charging current of the battery included in the charging profile. Furthermore, the control unit 120 can predict the SOC of a battery based on the remaining SOC of the battery, charging current, charging voltage, and charging time.

[0047] When the control unit 120 predicts the State of Charge (SOC) of each battery, it can predict at least one of the following based on the predicted SOC: drive information, status information, management information, driving range, and failure probability of the device to which the battery is installed. For example, the control unit 120 can predict the driving range based on data showing how the device using the battery typically uses the battery, and the predicted SOC of the battery. Alternatively, for example, the control unit 120 may determine that a battery is faulty if it is in at least one of the following states: the battery is not charged, the remaining SOC is below a critical value, or the battery is faulty. In one embodiment, the control unit 120 can determine whether a battery is usable based on its driving range and failure probability.

[0048] The control unit 120 can determine whether at least one battery is available for loan based on the predicted driving range and failure status of at least one battery. For example, if a user requests to borrow a battery, the control unit 120 can lend the user a battery with a remaining State of Charge (SOC) equal to or greater than the driving range entered by the user. Alternatively, the control unit 120 can manage so that batteries that are determined to be faulty are not loaned out. In one embodiment, the control unit 120 can manage so that the user does not drive beyond the predicted driving range of the battery by informing the user of the battery's driving range. In one embodiment, if there is no battery that can enable the user to drive beyond the driving range entered by the user, the control unit 120 can inform the user that there are no batteries available for loan. In this case, the control unit 120 can lend the user another battery, inform the user of the driving range of the loaned battery, and guide the user to move to another battery charging device and then replace the battery. In one embodiment, if there is no battery capable of enabling travel beyond the distance entered by the user, the control unit 120 can calculate the time required for a battery to be charged to enable travel beyond the distance entered by the user, based on the battery that has received the most charge, and can inform the user of the calculated time.

[0049] In one embodiment, if there is no battery corresponding to the mileage entered by the user, the control unit 120 can communicate with other battery charging devices via the communication unit 110 and obtain status information of batteries connected to other battery charging devices. Based on the status information of batteries connected to other battery charging devices, the control unit 120 can guide the user to a battery charging device that has a battery corresponding to the mileage entered by the user.

[0050] The control unit 120 can predict the lifespan of at least one battery based on the charging profile of at least one battery. For example, the control unit 120 can predict the lifespan of a battery based on at least one of the following: the number of charge cycles, the charging speed, the charging voltage, and the charging current. Alternatively, for example, the control unit 120 can determine that a battery is aged if the number of charge cycles exceeds a critical value.

[0051] The control unit 120 can determine whether at least one battery is available for loan based on its predicted lifespan. For example, if a battery is predicted to have reached the end of its lifespan, the control unit 120 can control it so that it is not loaned out any further. Alternatively, for example, the control unit 120 can control it so that batteries with a long lifespan remaining are loaned to users traveling long distances, and batteries with a short lifespan remaining are loaned to users traveling short distances. In one embodiment, the control unit 120 can consider all predicted SOC and lifespans based on the charge profile to decide whether or not to loan a battery to a user.

[0052] At least one battery connected to the battery charging device 100 may have its own identification information set. For example, each of the at least one battery may have an ID.

[0053] The control unit 120 can acquire the state of at least one battery based on the identification information of at least one battery. For example, the control unit 120 can acquire battery state information and associate the acquired state information with the battery identification information. The control unit 120 can transmit the state of at least one battery, which is associated with the identification information of at least one battery, to the battery management server 10. For example, the battery management server 10 can store the battery state information associated with each battery's identification information. In this case, the battery management server 10 can generate a battery charge profile based on the battery state information and associate the generated charge profile with the battery identification information.

[0054] The control unit 120 can receive a charge profile for at least one battery from the battery management server 10 based on the identification information of at least one battery. For example, when the control unit 120 requests a battery charge profile from the battery management server 10, it can also transmit the battery identification information, and the battery management server 10 can find the charge profile corresponding to the transmitted battery identification information and transmit it to the control unit 120. Therefore, the control unit 120 can receive the charge profile corresponding to the transmitted battery identification information and control the battery to charge using the received charge profile.

[0055] A battery charging device 100 according to one embodiment disclosed herein can acquire battery status information and transmit it to a battery management server 10, and can receive a battery charging profile from the battery management server 10. Based on the received charging profile, the battery charging device 100 can efficiently charge the battery, predict the battery's SOC or lifespan, and determine whether or not to lend the battery to the user. Furthermore, by managing the battery charging profile based on the battery identification information, the battery charging device 100 can continuously update the battery charging profile and charge batteries individually based on their respective charging profiles. In other words, the battery charging device 100 can individually manage, charge, and / or lend each connected battery.

[0056] Figure 3 is a block diagram showing a battery management device according to one embodiment disclosed herein. In one embodiment, the battery management device 200 in Figure 3 may be substantially identical to the battery management device 200 in Figure 1.

[0057] Referring to Figure 3, a battery management device 200 according to one embodiment disclosed herein may be included in the battery 2000. The battery management device 200 can manage and / or control the state and / or operation of the battery 2000. For example, the battery management device 200 can manage and / or control the state and / or operation of multiple battery cells included in the battery 2000. The battery management device 200 can manage the charging and / or discharging of the battery 2000.

[0058] Furthermore, the battery management device 200 can monitor the voltage, current, temperature, insulation resistance, etc., of the battery 2000. Based on the measured values ​​of the monitored voltage, current, temperature, etc., the battery management device 200 can calculate parameters indicating the state of the battery 2000, such as SOC (State of Charge) and SOH (State of Health). In one embodiment, the battery 2000 managed by the battery management device 200 may include, but is not limited to, lithium-ion (Li-ion) batteries, lithium polymer (Li-ion polymer) batteries, nickel-cadmium (Ni-Cd) batteries, nickel-metal hydride (Ni-MH) batteries, etc.

[0059] The battery management device 200 may include a communication unit 210 and a control unit 220.

[0060] The communication unit 210 can communicate with the battery management server 10 (see Figure 1). The communication unit 210 can communicate with the charging device 100. In one embodiment, the communication unit 210 includes a wireless communication circuit (e.g., a cellular communication circuit, a short-range wireless communication circuit, or a GNSS (global navigation satellite system) communication circuit) or a wired communication circuit (e.g., a LAN (local area network) communication circuit, or a power line communication circuit), and can communicate with an external electronic device via a short-range communication network such as Bluetooth, WiFi Direct, or IrDA (infrared data association), or a long-range communication network such as a cellular network, the Internet, or a computer network, using the appropriate communication circuit. The various types of communication units 210 described above may be embodied in a single chip or each may be embodied in a separate chip.

[0061] The control unit 220 can acquire battery status information. For example, the control unit 220 can acquire battery status information measured by a measuring unit (not shown). In one embodiment, the control unit 220 can acquire battery status information while the battery 2000 is being used (or discharged). In one embodiment, the control unit 220 can acquire battery status information while the battery 2000 is being charged. In one embodiment, the battery status information may include at least one of the following: battery current, voltage, charging rate, discharging rate, state of charge (SOC), and state of health (SOH).

[0062] The control unit 220 can transmit battery status information to the battery management server 10. For example, the control unit 220 can transmit battery status information to the battery management server 10 via the communication unit 210 while the battery 2000 is in use. The battery management server 10 can generate a battery discharge profile based on the battery status information while the battery 2000 is in use.

[0063] The control unit 220 can receive the battery discharge profile from the battery management server 10. For example, the battery discharge profile may include at least one of the following: the number of charge / discharge cycles of the battery 2000, the discharge rate due to the discharge voltage, the discharge rate due to the discharge current, the discharge rate due to the discharge time, the change in SOC due to the discharge voltage, and the change in SOC due to the discharge current. Alternatively, for example, the battery discharge profile may be a graph relating to the discharge current, voltage, and time at which the battery 2000 can be efficiently discharged.

[0064] The control unit 220 can receive a battery charge profile from the battery management server 10. For example, the battery charge profile may include at least one of the following: the number of charge cycles of the battery 2000, the charging speed due to the charging voltage, the charging speed due to the charging current, the charging speed due to the charging time, the change in SOC due to the charging voltage, and the change in SOC due to the charging current. Alternatively, for example, the battery charge profile may be a graph relating to the charging current, voltage, and time at which the battery 2000 can be efficiently charged. In one embodiment, the battery charge profile may be generated based on at least one of the following: battery state information when the battery 2000 is charging, and battery state information when the device to which the battery is installed is performing regenerative braking. For example, the device containing the battery may include automobiles, bicycles, kick boats, drones, ESSs, motorcycles, two-wheeled vehicles, three-wheeled vehicles, and other devices that can be driven using the battery's power supply.

[0065] The control unit 220 can control the use of battery 2000 based on the discharge profile received from the battery management server 10. For example, when a device containing a battery uses battery 2000, the control unit 220 can determine at least one of the discharge current and discharge voltage based on the received discharge profile, and can control the use of battery 2000 based on the determined discharge current or discharge voltage.

[0066] The control unit 220 can transmit a charging profile to the charging device when the battery 2000 is connected to the charging device. For example, the control unit 220 can enable the battery 2000 to be charged efficiently by transmitting the charging profile received from the battery management server 10 to the charging device.

[0067] When the battery 2000 is used for regenerative braking, the control unit 220 can transmit battery charge status information to the battery management server 10 via the communication unit 210. For example, when a device containing a battery performs regenerative braking, the battery 2000 is charged, so the control unit 220 can transmit the status information of the charging battery to the battery management server 10, and the battery management server 10 can generate or update a charge profile based on the transmitted information.

[0068] The control unit 220 can predict at least one of the driving range and power limit based on the discharge profile. For example, the control unit 220 can determine the voltage or current at which the battery 2000 is discharged based on the discharge profile, and can predict the driving range and power limit based on the battery's SOC and the determined discharge voltage and discharge current. In one embodiment, the control unit 220 can inform the user of the predicted driving range or power limit, thereby preventing the use of the battery 2000 beyond the predicted driving range or power limit.

[0069] The control unit 220 can determine whether the battery 2000 needs to be charged or replaced based on the predicted mileage or power limit. For example, if the user attempts to travel beyond the predicted mileage, the control unit 220 can determine that the battery 2000 needs to be charged or replaced and can inform the user of the result. Alternatively, if the user attempts to use the battery beyond the predicted power limit, for example, by increasing speed, the control unit 220 can determine that the battery 2000 needs to be replaced or charged and can inform the user of the result.

[0070] Battery 2000 may have identification information assigned to it. For example, Battery 2000 may have an ID.

[0071] The control unit 220 can transmit battery status information to the battery management server 10 based on the battery identification information. For example, the battery management server 10 can store battery status information corresponding to each battery identification information. In this case, the battery management server 10 can generate a battery charge profile based on the battery status information and associate the generated charge profile with the battery identification information.

[0072] The control unit 220 can receive a battery charge profile or discharge profile from the battery management server 10 based on the battery's identification information. For example, when the control unit 220 requests a battery charge profile or discharge profile from the battery management server 10, it can also transmit the battery's identification information. The battery management server 10 can then find the charge profile or discharge profile corresponding to the transmitted battery identification information and transmit it to the control unit 220. Therefore, the control unit 220 can receive the charge profile or discharge profile corresponding to the transmitted battery identification information and use the received charge profile or discharge profile to control the battery so that it is charged or discharged efficiently.

[0073] Figure 4 is a diagram showing the flow of information about a battery according to one embodiment disclosed herein.

[0074] The battery charging device 100 can transmit status information of the battery being charged to the battery management server 10. For example, the battery charging device 100 can compare the status information of the batteries being charged and transmit it to the battery management server 10. Depending on the embodiment, the battery charging device 100 can also directly generate a battery charging profile.

[0075] Devices 1 and 2, which use batteries, can transmit information about the state of the battery in use to the battery management server 10. Furthermore, when regenerative braking is performed, devices 1 and 2, which use batteries, can transmit information about the state of the battery being charged to the battery management server 10.

[0076] The battery management server 10 can generate a charge profile and / or discharge profile based on the received battery status information. The battery management server 10 can transmit the generated charge and / or discharge profile to the battery charging device 100 and / or the device 5 that uses the battery. Although not shown in Figure 4, the battery management server 10 can transmit the generated charge and / or discharge profile to all devices 1, 2, 3, 4, 5, and 100 on which the battery is used and / or charged. For example, the battery management server 10 can transmit the charge and / or discharge profile to all devices on which the battery is used and / or charged based on the identification information set for the battery.

[0077] The battery charger 100 can charge connected batteries based on the received battery charge profile. Furthermore, when battery 3 is connected, the battery charger 100 can receive a charge profile from the battery management device included in battery 3 and charge battery 3 based on the received charge profile.

[0078] The battery charging device 100 can provide the battery 4 to the user (or the device using the battery) if there is a request to use the battery 4. In this case, the device using the battery 5 can receive a discharge profile from the battery management server 10 or the battery management device included in the battery 4, and use the battery 4 based on the received discharge profile.

[0079] Figure 5 is a block diagram showing the hardware configuration of a computing system that embodies a control method for a battery management device according to one embodiment disclosed herein.

[0080] Referring to Figure 5, a computing system 1000 according to one embodiment disclosed herein may include an MCU 1010, a memory 1020, an input / output interface 1030, and a communication interface 1040.

[0081] The MCU1010 may be a processor that executes various programs stored in the memory 1020 (for example, a battery cell voltage measurement program, a switching control program, etc.), processes various data including the voltage and internal resistance of the battery cells through such programs, and performs the functions of the battery management device 200 shown in Figure 3 above.

[0082] Memory 1020 can store various programs related to battery cell voltage measurement and switching control. It can also store various data such as battery cell voltage and internal resistance.

[0083] Multiple such memory 1020s may be provided as needed. Memory 1020 may be volatile memory or non-volatile memory. As volatile memory, RAM, DRAM, SRAM, etc., may be used for memory 1020. As non-volatile memory, ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc., may be used for memory 1020. The examples of memory 1020 listed above are merely illustrative and are not limiting to these examples.

[0084] The input / output interface 1030 can provide an interface that connects input devices (not shown), such as keyboards, mice, and touch panels, and output devices (not shown), such as displays, with the MCU 1010, enabling data transmission and reception.

[0085] The communication interface 1040 is configured to send and receive various data with a server and may be various devices that support wired or wireless communication. For example, programs for measuring the voltage of battery cells and switching control, as well as various other data, can be sent and received from an external server separately provided via the communication interface 1040.

[0086] Thus, a computer program according to one embodiment disclosed herein may be recorded in memory 1020 and processed by MCU 1010 to be embodied as a module that performs, for example, the functions shown in Figure 2.

[0087] In one embodiment, the computing system 1000 can also be applied to the battery charging device 100 shown in Figure 2. That is, the battery charging device 100 shown in Figure 2 may include an MCU 1010, a memory 1020, an input / output interface 1030, and a communication interface 1040.

[0088] The above description is merely illustrative of the technical concept disclosed herein, and any person with ordinary skill in the art to which the embodiments disclosed herein belong can make various modifications and variations without departing from the essential characteristics of the embodiments disclosed herein.

[0089] Therefore, the embodiments disclosed herein are for illustrative purposes only, and not to limit, the technical concept disclosed herein, and such embodiments do not limit the scope of the technical concept disclosed herein. The scope of protection of the technical concept disclosed herein should be interpreted by the following claims, and all technical concepts within the same scope should be interpreted as being included within the scope of the present invention.

Claims

1. A battery management device included in the battery, The battery status information during its use is transmitted to the battery management server via the device using the battery. A battery management device including a control unit that controls the use of the battery based on the battery discharge profile received from the battery management server via the device using the battery.

2. The control unit, The battery management device according to claim 1, wherein when the battery is connected to a charging device, it transmits a charging profile to the charging device.

3. The control unit, The battery management device according to claim 1 or 2, wherein when the battery is used for regenerative braking, the device transmits the charge status information of the battery to the battery management server via the device using the battery.

4. The aforementioned battery has identification information set, The control unit, Based on the identification information, the battery status information is transmitted to the battery management server via the device using the battery. The battery management device according to claim 1 or 2, which receives the discharge profile or charge profile from the battery management server via the device using the battery based on the identification information.

5. The discharge profile includes at least one of the following: discharge rate due to the battery's discharge voltage, discharge rate due to the battery's discharge current, discharge rate due to the battery's discharge time, change in SOC due to the battery's discharge voltage, and change in SOC due to the battery's discharge current. The control unit, A battery management device according to claim 1 or 2, which predicts at least one of the driving range of the device while using the battery and the power limit of the battery, based on the discharge profile.

6. The control unit, The battery management device according to claim 5, which determines whether or not the battery needs to be charged or replaced based on the predicted driving range or the power limit.

7. The aforementioned battery has identification information set, The control unit, Based on the identification information, the battery status information is transmitted to the battery management server via the device using the battery. The device, while using the aforementioned battery, The battery management device according to claim 1 or 2, which uses the battery based on the discharge profile received from the battery management server based on the identification information.

Images