Battery charging device and battery management device
The battery charging and management system addresses inefficiencies in battery management by using communication and control units to apply personalized profiles, ensuring efficient charging and usage based on battery state and condition, enhancing performance and longevity.
Patent Information
- Application Number
- JP2025008700
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-09-03
- Filing Date
- 2025-01-21
- Publication Date
- 2026-01-21
- Estimated Expiration
- 2042-08-30
AI Technical Summary
Existing battery management systems fail to efficiently manage and optimize charging and usage of batteries based on their individual states and conditions, leading to potential issues when multiple batteries are managed uniformly.
A battery charging device and management system that includes communication units to exchange data with a battery management server, allowing for the generation and application of personalized charging and discharge profiles based on battery identification, state of charge, health, and usage history, enabling predictive maintenance and efficient allocation.
Enables efficient charging and usage of batteries by predicting state of charge, lifespan, and determining rental suitability, thereby optimizing battery performance and extending their usable life.
Smart Images

Figure 0007804111000001 
Figure 0007804111000002 
Figure 0007804111000003
Abstract
Description
[Technical Field]
[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] The present invention claims the benefit of priority based on Korean Patent Application No. 10-2021-0117973, filed on September 3, 2021, and all contents disclosed in the documents of said Korean patent application are incorporated herein by reference.
[0002] SUMMARY OF THE INVENTION The embodiments disclosed herein relate to a battery charging device and a battery management device. [Background technology]
[0003] Recently, research and development into secondary batteries has been actively conducted. Here, secondary batteries are batteries that can be charged and discharged, and include conventional Ni / Cd batteries, Ni / MH batteries, and the latest lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of having a much higher energy density than conventional Ni / Cd batteries, Ni / MH batteries, etc. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form, and are used as power sources for mobile devices. Recently, their range of use has expanded to include power sources for electric vehicles, and they are attracting attention as a next-generation energy storage medium.
[0004] In the case of battery-powered transportation, there are cases where batteries are replaced and used. There are charging stations that charge and lend such replaceable batteries, and many replaceable batteries are charged and lent out at the charging stations. Since the degree of aging or deterioration of a battery varies depending on the method of using the battery and the battery condition, problems may arise when many batteries are managed in the same way. Summary of the Invention [Problem to be solved by the invention]
[0005] One object of the embodiments disclosed in this specification is to provide a battery charging device that can be controlled to efficiently charge each battery 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 the battery based on the battery's condition.
[0007] The technical problems of the embodiments disclosed in this specification are not limited to the technical problems 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 in this specification may include a communication unit that communicates with a battery management server, and a control unit that compares the charging states of at least one battery being charged, transmits 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 charging of the at least one battery based on the received charging profile of the at least one battery.
[0009] In one embodiment, the control unit may predict a State Of Charge (SOC) of each of the at least one battery based on a charging profile of the at least one battery, and may predict a mileage and a likelihood of a breakdown based on the predicted SOC.
[0010] In one embodiment, the control unit may determine whether the at least one battery can be rented based on a travelable distance of the at least one battery and whether the at least one battery has a malfunction.
[0011] In one embodiment, the control unit can predict the lifespan of each of the at least one battery based on a charging profile of the at least one battery, and determine whether the at least one battery can be loaned based on the predicted lifespan.
[0012] In one embodiment, each of the at least one batteries may have its own identification information set thereon.
[0013] In one embodiment, the control unit can transmit the status 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 receive a charging profile 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 for the at least one battery may be generated based on at least one of battery status information when the at least one battery is being charged and battery status information when a device including the at least one battery is performing regenerative braking.
[0015] In an embodiment, the control unit may obtain a charging profile of the at least one battery from a battery management unit included in the at least one battery.
[0016] A battery management device according to one embodiment disclosed in this specification 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 discharge profile of the battery from the battery management server, and controls the battery to be used based on the discharge profile.
[0017] In an embodiment, the control unit may receive a charging profile of the battery from the battery management server, and may transmit the charging profile to the charging device when the battery is connected to the charging device.
[0018] In one embodiment, the control unit may transmit charge state information of the battery to the battery management server when the battery is used for regenerative braking.
[0019] In one embodiment, the battery has identification information set thereon, and the control unit can transmit status information of the battery to the battery management server based on the identification information, and receive the discharge profile or charge profile from the battery management server based on the identification information.
[0020] In an embodiment, the control unit may predict at least one of a driving distance and a 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 driving range or power limit. [Effects of the Invention]
[0022] A battery charging apparatus according to an embodiment disclosed herein can control the efficient charging of each battery based on a charging profile corresponding to the state of each battery.
[0023] A battery charging device according to an embodiment disclosed in this specification can predict the SOC and lifespan of each battery based on the charging profile of each battery, and select a rental battery that meets the user's requirements.
[0024] A battery management device according to an embodiment disclosed herein can control the efficient use of the battery based on the discharge profile of the battery.
[0025] A battery management device according to an embodiment disclosed herein can predict a power limit or a driving range based on a charging or discharging profile of the battery, and can control to replace the battery.
[0026] In addition, various other effects may be provided that can be grasped directly or indirectly through this specification. [Brief explanation of the drawings]
[0027] [Figure 1] 1 illustrates a system including a battery charging device and a battery management device according to one embodiment disclosed herein. [Figure 2] 1 is a block diagram illustrating a battery charging device according to one embodiment disclosed herein. [Figure 3] 1 is a block diagram illustrating a battery management unit according to one embodiment disclosed herein. [Figure 4] FIG. 2 is a diagram illustrating a flow of communication of information about a battery according to one embodiment disclosed herein. [Figure 5] 1 is a block diagram illustrating a hardware configuration of a computing system that implements a method for controlling a battery management unit according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION
[0028] Hereinafter, the embodiments disclosed herein will be described in detail with reference to the accompanying drawings. When assigning reference numerals to components in each drawing, it should be noted that identical components are assigned the same numerals whenever possible, even if they appear in different drawings. Furthermore, when describing the embodiments disclosed herein, if a detailed description of known structures or functions is deemed to hinder understanding of the embodiments disclosed herein, the detailed description will be omitted.
[0029] In describing components of the embodiments disclosed herein, terms such as "first," "second," "A," "B," "(a)," and "(b)" may be used. These terms are merely used to distinguish one component from another and do not limit the nature, order, or sequence of the components. Furthermore, unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed herein pertain. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted as idealized or overly formal unless expressly defined in this application.
[0030] FIG. 1 is a diagram illustrating a system including a battery charging device according to one embodiment disclosed herein.
[0031] 1, a battery charging apparatus 100 according to one embodiment disclosed herein can communicate with a battery management server 10, a user terminal 20, and a battery management unit 200. In one embodiment, the battery charging apparatus 100 shown in FIG. 1 may be substantially the same as the battery charging apparatus 100 shown in FIG. 2, which will be described below. In one embodiment, the battery management unit 200 shown in FIG. 1 may be substantially the same as the battery management unit 200 shown in FIG. 3, which will be described below.
[0032] The battery charging apparatus 100 can transmit status information of at least one battery connected to the battery charging apparatus 100 to the battery management server 10. For example, the battery charging apparatus 100 can transmit information obtained by comparing charging data of at least one battery, etc. 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 apparatus 100 and transmit the generated charging profile to the battery charging apparatus 100. The battery charging apparatus 100 can control the at least one battery connected to the battery charging apparatus 100 to be efficiently charged based on the received charging profile.
[0033] The battery charging apparatus 100 can receive a request from the user terminal 20. For example, the user terminal 20 can make a request to the battery charging apparatus 100 to lend a battery. The user terminal 20 can input a distance to be traveled using the battery, and the battery charging apparatus 100 can select a battery to be lent based on the input travel distance. For example, the battery charging apparatus 100 can predict the current SOC of at least one battery, predict a possible travel distance based on the current SOC, and lend a battery corresponding to the travel distance input by the user terminal 20. In other words, the user terminal 20 can receive a battery corresponding to the travel distance from the battery charging apparatus 100, thereby efficiently using the battery.
[0034] The battery charging device 100 can communicate with a battery management unit 200 included in a battery connected to the battery charging device 100. For example, the battery charging device 100 can receive a battery charging profile from the battery management unit 200. In this case, the battery charging device 100 does not need to receive the battery charging profile from the battery management server 10, allowing for prompt charging. As another example, the battery charging device 100 can transmit the charging profile received from the battery management server 10 to the battery management unit 200, and the battery management unit 200 can store the received charging profile in its internal storage. In this case, even when the battery charging device 100 is subsequently connected to another charging device, the battery management unit 200 can transmit the charging profile to the other charging device, allowing for efficient charging. In one embodiment, if the battery charging device 100 is located in an area where communication with the battery management server 10 is unavailable, the battery charging device 100 may be unable to communicate with the battery management server 10. In this case, the battery charging device 100 can control the battery to be charged based on the charging profile stored in the battery management unit 200.
[0035] The battery management unit 200 can communicate with the battery management server 10 and the charging unit 100.
[0036] The battery management unit 200 can transmit battery charge and / or discharge state 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 state information. For example, when battery identification information is received along with the battery charge and / or discharge state information, the battery management server 10 can store and / or transmit the battery charge and / or discharge profile corresponding to the received battery identification information. The battery management unit 200 can receive the battery charge and / or discharge profile from the battery management server 10 and control the battery to be charged and / or discharged based on the received charge and / or discharge profile.
[0037] When a battery is connected to the charging device 100, the battery management unit 200 can transmit a charging profile to the charging device 100. The charging device 100 can charge the battery based on the received charging profile.
[0038] 2 is a block diagram illustrating a battery charging device according to one embodiment disclosed herein. The battery charging device 100 of FIG. 2 may be substantially identical to the battery charging device 100 of FIG.
[0039] A battery charging apparatus 100 according to an 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 FIG. 1). The communication unit 110 can also communicate with a battery management system 200 (BMS, see FIG. 1) included in each of 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 global navigation satellite system (GNSS) communication circuit) or a wired communication circuit (e.g., a local area network (LAN) communication circuit or a power line communication circuit), and can communicate with an external electronic device using the corresponding communication circuit via a short-range communication network such as Bluetooth®, WiFi Direct®, or Infrared Data Association (IrDA), or a long-range communication network such as a cellular network, the Internet, or a computer network. The various types of communication units 110 described above may be implemented on a single chip or on separate chips.
[0041] The control unit 120 may acquire status information of at least one battery connected to the battery charging apparatus 100. For example, the control unit 120 may acquire the status information of at least one battery from the battery management unit 200 included in each of the at least one battery. In one embodiment, the battery status information may include at least one of the voltage, current, temperature, and insulation resistance of the battery. The battery status information may also include parameters indicating the battery status, such as, but not limited to, a state of charge (SOC) and a state of health (SOH).
[0042] The control unit 120 may compare the state of charge of at least one battery being charged. For example, the control unit 120 may compare at least one of the charging speed, charging level, SOC, SOH, whether or not the battery is fully charged, the full charge speed, the remaining battery capacity, the charging current, the charging voltage, the charging time, and whether or not the battery is faulty.
[0043] The control unit 120 may transmit state information of at least one battery to the battery management server 10 via the communication unit 110. For example, the control unit 120 may transmit state information of at least one battery or comparison information regarding the state of charge of at least one battery to the battery management server 10 via the communication unit 110. In one embodiment, the battery management server 10 may generate a battery charging profile based on the battery state information and the state of charge comparison information transmitted from the control unit 120.
[0044] The control unit 120 may receive a charge profile for each of the at least one battery from the battery management server 10. For example, the charge profile for a battery may include at least one of the following: the number of times the battery has been charged; a charge rate depending on the charge voltage; a charge rate depending on the charge current; a charge rate depending on the charge time; a change in SOC depending on the charge voltage; and a change in SOC depending on the charge current. For example, the charge profile for a battery may have a graph of the charge current, voltage, and time required for efficient charging of the battery. In one embodiment, the charge profile for the at least one battery may be generated based on at least one of battery status information when the at least one battery is being charged and battery status information when a device including the at least one battery is performing regenerative braking. For example, the device including the at least one battery may include a car, a bicycle, a kick boat, a drone, an ESS, a motorcycle, a two-wheeled vehicle, a three-wheeled vehicle, and other devices that can be powered by a battery.
[0045] The control unit 120 may control the charging of the at least one battery based on the received charging profile of the at least one battery. For example, the control unit 120 may control the charging of each of the at least one battery based on the received charging profile of each of the at least one battery so that each of the batteries is efficiently charged.
[0046] The control unit 120 can predict the SOC of each of the at least one battery based on the charging profile of the at least one battery. For example, the control unit 120 can predict the SOC of the battery based on the charging voltage of the battery included in the charging profile. For another example, the control unit 120 can predict the SOC of the battery based on the charging current of the battery included in the charging profile. For another example, the control unit 120 can predict the SOC of the battery based on the remaining SOC, charging current, charging voltage, and charging time of the battery.
[0047] When the control unit 120 predicts the SOC of each battery, it can predict at least one of driving information, status information, management information, available driving distance, and whether or not the battery is faulty, of a device to which the battery is attached, based on the predicted SOC. For example, the control unit 120 can predict the available driving distance based on data on average battery usage by a device using the battery and the predicted SOC of the battery. In another example, the control unit 120 can determine that the battery is faulty when the battery is in at least one of an uncharged state, a state where the remaining SOC is below a critical value, and a state where the battery is faulty. In one embodiment, the control unit 120 can determine whether the battery is usable based on the available driving distance and whether or not the battery is faulty.
[0048] The control unit 120 may determine whether at least one battery can be lent based on the predicted mileage of at least one battery and whether it is faulty. For example, when a user requests the lending of a battery, the control unit 120 may lend to the user a battery with a remaining SOC equal to or greater than the mileage input by the user based on the mileage input by the user. For another example, the control unit 120 may manage the vehicle so that a battery determined to be faulty is not lent. In one embodiment, the control unit 120 may manage the vehicle so that the user does not drive beyond the predicted mileage of the battery by informing the user of the mileage of the battery. In one embodiment, the control unit 120 may inform the user that there is no battery available for lending if there is no battery that can drive beyond the mileage input by the user. In this case, the control unit 120 may lend another battery to the user, inform the user of the mileage of the lent battery, and advise the user to move to another battery charging device and then replace the battery. In one embodiment, if there is no battery that can be charged to enable driving for a distance greater than the distance input by the user, the control unit 120 can calculate the time required to charge the battery to enable driving for a distance greater than the distance input by the user, based on the battery that has been charged the most, and can inform the user of the calculated time.
[0049] In one embodiment, if there is no battery corresponding to the mileage input by the user, the control unit 120 can communicate with another battery charging device via the communication unit 110 and acquire status information of the battery connected to the other battery charging device. Based on the status information of the battery connected to the other battery charging device, the control unit 120 can guide the user to a battery charging device that has a battery corresponding to the mileage input by the user.
[0050] The control unit 120 may predict the lifespan of at least one battery based on the charging profile of the at least one battery. For example, the control unit 120 may predict the lifespan of a battery based on at least one of the number of times the battery has been charged, the charging rate, the charging voltage, and the charging current of the battery. For another example, the control unit 120 may determine that a battery whose number of times the battery has been charged is higher than a threshold value is aged.
[0051] The control unit 120 may determine whether to lend at least one battery based on the predicted lifespan. For example, the control unit 120 may control a battery whose lifespan is predicted to be exhausted so that it is not further lent. For another example, the control unit 120 may control a battery whose lifespan is long based on the predicted lifespan to be lent to a user who will travel long distances, and may control a battery whose lifespan is short based on the predicted lifespan to be lent to a user who will travel short distances. In one embodiment, the control unit 120 may determine whether to lend a battery to a user by taking into consideration both the SOC and lifespan predicted based on the charging profile.
[0052] Identification information may be set for each of the at least one battery connected to the battery charging device 100. For example, each of the at least one battery may have an ID.
[0053] The control unit 120 may acquire the status of at least one battery based on the identification information of each of the at least one battery. For example, the control unit 120 may acquire battery status information and associate the acquired status information with the battery identification information. The control unit 120 may transmit the status of at least one battery associated with the identification information of the at least one battery to the battery management server 10. For example, the battery management server 10 may store the battery status information in association with the battery identification information. In this case, the battery management server 10 may generate a battery charging profile based on the battery status information and associate the generated charging profile with the battery identification information.
[0054] The control unit 120 may receive a charging profile of at least one battery based on the identification information of each of the at least one battery from the battery management server 10. For example, when the control unit 120 requests a charging profile of a battery from the battery management server 10, the control unit 120 may transmit the identification information of the battery together, and the battery management server 10 may search for a charging profile corresponding to the transmitted identification information of the battery and transmit the charging profile to the control unit 120. Thus, the control unit 120 may receive a charging profile corresponding to the transmitted identification information of the battery and control the battery to be charged using the received charging profile.
[0055] A battery charging apparatus 100 according to an embodiment disclosed herein can acquire battery status information and transmit it to the 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 apparatus 100 can efficiently charge the battery and predict the battery's SOC or lifespan to determine whether to lend the battery to a user. Furthermore, the battery charging apparatus 100 can continuously update the battery charging profile by managing the battery's charging profile based on battery identification information, and can individually charge the battery based on the charging profile for each battery. That is, the battery charging apparatus 100 can individually manage, charge, and / or lend each connected battery.
[0056] 3 is a block diagram illustrating a battery management unit according to one embodiment disclosed herein. In one embodiment, the battery management unit 200 of FIG. 3 may be substantially identical to the battery management unit 200 of FIG.
[0057] 3 , a battery management unit 200 according to an embodiment disclosed herein may be included in a battery 2000. The battery management unit 200 may manage and / or control the state and / or operation of the battery 2000. For example, the battery management unit 200 may manage and / or control the state and / or operation of a plurality of battery cells included in the battery 2000. The battery management unit 200 may manage charging and / or discharging of the battery 2000.
[0058] Furthermore, the battery management unit 200 can monitor the voltage, current, temperature, insulation resistance, etc. of the battery 2000. The battery management unit 200 can calculate parameters indicating the state of the battery 2000, such as SOC (State Of Charge) and SOH (State Of Health), based on the measured values of the monitored voltage, current, temperature, etc. In one embodiment, the battery 2000 managed by the battery management unit 200 can include, but is not limited to, a lithium ion (Li-ion) battery, a lithium polymer (Li-ion polymer) battery, a nickel cadmium (Ni-Cd) battery, a nickel metal hydride (Ni-MH) battery, etc.
[0059] The battery management unit 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 FIG. 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 global navigation satellite system (GNSS) communication circuit) or a wired communication circuit (e.g., a local area network (LAN) communication circuit or a power line communication circuit), and can communicate with an external electronic device using the corresponding communication circuit via a short-range communication network such as Bluetooth, WiFi Direct, or Infrared Data Association (IrDA), or a long-range communication network such as a cellular network, the Internet, or a computer network. The various types of communication units 210 described above may be implemented on a single chip or on separate chips.
[0061] The control unit 220 may acquire battery status information. For example, the control unit 220 may acquire battery status information measured by a measurement unit (not shown). In one embodiment, the control unit 220 may acquire battery status information while the battery 2000 is being used (or discharged). In one embodiment, the control unit 220 may 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 battery current, voltage, charge rate, discharge rate, SOC, and SOH.
[0062] The control unit 220 can transmit battery state information to the battery management server 10. For example, the control unit 220 can transmit battery state information while the battery 2000 is in use to the battery management server 10 via the communication unit 210. The battery management server 10 can generate a battery discharge profile based on the battery state information while the battery 2000 is in use.
[0063] The control unit 220 may receive a battery discharge profile from the battery management server 10. For example, the battery discharge profile may include at least one of the number of charge / discharge cycles of the battery 2000, the discharge rate depending on the discharge voltage, the discharge rate depending on the discharge current, the discharge rate depending on the discharge time, the amount of change in SOC depending on the discharge voltage, and the amount of change in SOC depending on the discharge current. As another example, the battery discharge profile may be in the form of a graph of the discharge current, voltage, and time at which the battery 2000 can be efficiently discharged.
[0064] The control unit 220 may receive a battery charge profile from the battery management server 10. For example, the battery charge profile may include at least one of the number of times the battery 2000 has been charged, the charge rate depending on the charge voltage, the charge rate depending on the charge current, the charge rate depending on the charge time, the amount of change in SOC depending on the charge voltage, and the amount of change in SOC depending on the charge current. For example, the battery charge profile may be a graph of the charge current, voltage, and time that allow the battery 2000 to be efficiently charged. In one embodiment, the battery charge profile may be generated based on at least one of battery status information when the battery 2000 is being charged and battery status information when a device to which the battery is attached is performing regenerative braking. For example, the device including the battery may include an automobile, a bicycle, a kick boat, a drone, an ESS, a motorcycle, a two-wheeled vehicle, a three-wheeled vehicle, and other devices that can be driven using a battery as a power source.
[0065] The control unit 220 may control the battery 2000 to be used based on the discharge profile received from the battery management server 10. For example, when a device including a battery uses the battery 2000, the control unit 220 may determine at least one of a discharge current and a discharge voltage based on the received discharge profile, and may control the battery 2000 to be used based on the determined discharge current or discharge voltage.
[0066] When the battery 2000 is connected to a charging device, the control unit 220 may transmit a charging profile to the charging device. For example, the control unit 220 may transmit a charging profile received from the battery management server 10 to the charging device, thereby enabling the battery 2000 to be efficiently charged.
[0067] When the battery 2000 is used for regenerative braking, the control unit 220 can transmit battery charge state information to the battery management server 10 via the communication unit 210. For example, when a device including a battery performs regenerative braking, the battery 2000 is charged, so the control unit 220 can transmit state information of the battery being charged to the battery management server 10, and the battery management server 10 can generate or update a charging profile based on the transmitted information.
[0068] The control unit 220 may predict at least one of a driving distance and a power limit based on the discharge profile. For example, the control unit 220 may determine a voltage or current at which the battery 2000 is discharged based on the discharge profile, and may predict the driving distance and power limit based on the SOC of the battery and the determined discharge voltage and discharge current. In one embodiment, the control unit 220 may notify the user of the predicted driving distance or power limit and may prevent the battery 2000 from being used beyond the predicted driving distance 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 intends to drive a distance greater than the predicted mileage based on the predicted mileage, the control unit 220 can determine that the battery 2000 needs to be charged or replaced and notify the user of the determination result. In another example, if the user intends to use the battery beyond the predicted power limit of the battery 2000, for example, by increasing the speed, the control unit 220 can determine that the battery 2000 needs to be charged or replaced and notify the user of the determination result.
[0070] Identification information may be set for the battery 2000. For example, the battery 2000 may have an ID.
[0071] The control unit 220 may transmit battery status information to the battery management server 10 based on the battery identification information. For example, the battery management server 10 may store battery status information corresponding to each battery identification information. In this case, the battery management server 10 may generate a battery charging profile based on the battery status information and associate the generated charging profile with the battery identification information.
[0072] The control unit 220 may receive a battery charge profile or discharge profile from the battery management server 10 based on the identification information of the battery. For example, when the control unit 220 requests a battery charge profile or discharge profile from the battery management server 10, the control unit 220 may transmit the battery identification information together, and the battery management server 10 may search for a charge profile or discharge profile corresponding to the transmitted battery identification information and transmit the charge profile or discharge profile to the control unit 220. Thus, the control unit 220 may receive a charge profile or discharge profile corresponding to the transmitted battery identification information and may control the battery to be efficiently charged or discharged using the received charge profile or discharge profile.
[0073] FIG. 4 is a diagram illustrating a flow of transmitting information about a battery according to one embodiment disclosed herein.
[0074] The battery charging apparatus 100 can transmit status information of the battery being charged to the battery management server 10. For example, the battery charging apparatus 100 can compare status information of the battery being charged and transmit the information to the battery management server 10. Depending on the embodiment, the battery charging apparatus 100 can also generate a battery charging profile directly.
[0075] The devices 1 and 2 using batteries can transmit status information of the batteries in use to the battery management server 10. Furthermore, the devices 1 and 2 using batteries can transmit status information of the batteries being charged to the battery management server 10 when performing regenerative braking.
[0076] The battery management server 10 can generate a charging profile and / or discharging profile based on the received battery status information. The battery management server 10 can transmit the generated charging and / or discharging profile to the battery charging device 100 and / or the device 5 that uses the battery. Although not shown in FIG. 4 , the battery management server 10 can transmit the generated charging and / or discharging profile to all devices 1, 2, 3, 4, 5, 100 that use and / or charge the battery. For example, the battery management server 10 can transmit the charging and / or discharging profile to all devices that use and / or charge the battery based on identification information set in the battery.
[0077] The battery charging apparatus 100 can charge the connected battery based on the received battery charging profile. When the battery 3 is connected, the battery charging apparatus 100 can receive a charging profile from a battery management unit included in the battery 3 and charge the battery 3 based on the received charging profile.
[0078] The battery charging device 100 can provide the battery 4 to a user (or a device using the battery) when 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 a battery management device included in the battery 4 and use the battery 4 based on the received discharge profile.
[0079] FIG. 5 is a block diagram illustrating a hardware configuration of a computing system that implements a method for controlling a battery management unit according to an embodiment disclosed in this specification.
[0080] Referring to FIG. 5, a computing system 1000 according to one embodiment disclosed herein may include an MCU 1010, a memory 1020, an input / output I / F 1030, and a communication I / F 1040.
[0081] The MCU 1010 may be a processor that executes various programs (e.g., a battery cell voltage measurement program, a switching control program, etc.) stored in the memory 1020, 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 described above.
[0082] The memory 1020 can store various programs related to battery cell voltage measurement, switching control, etc. The memory 1020 can also store various data such as the voltage and internal resistance of the battery cell.
[0083] A plurality of such memories 1020 may be provided as necessary. The memories 1020 may be volatile memories or non-volatile memories. As the volatile memories 1020, RAM, DRAM, SRAM, etc. may be used. As the non-volatile memories 1020, ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. may be used. The examples of the memories 1020 listed above are merely illustrative and are not limited to these examples.
[0084] The input / output I / F 1030 can provide an interface that connects input devices (not shown) such as a keyboard, mouse, or touch panel and output devices such as a display (not shown) to the MCU 1010, enabling data to be sent and received.
[0085] The communication I / F 1040 is configured to be able to transmit and receive various data to and from a server, and may be any device capable of supporting wired or wireless communication. For example, programs and various data for measuring the voltage of the battery cells and controlling switching can be transmitted and received from a separately provided external server via the communication I / F 1040.
[0086] In this way, a computer program according to one embodiment disclosed in this specification may be recorded in memory 1020 and processed by MCU 1010 to be embodied as a module that performs, for example, each function shown in Figure 2.
[0087] In one embodiment, the computing system 1000 may also be applied to the battery charging device 100 of Fig. 2. That is, the battery charging device 100 of Fig. 2 may include an MCU 1010, a memory 1020, an input / output I / F 1030, and a communication I / F 1040.
[0088] The above description is merely an illustrative example of the technical ideas disclosed in this specification, and various modifications and variations are possible by a person having ordinary knowledge in the technical field to which the examples disclosed in this specification belong, without departing from the essential characteristics of the embodiments disclosed in this specification.
[0089] Therefore, the embodiments disclosed in this specification are intended to illustrate, not limit, the technical ideas disclosed in this specification, and such embodiments do not limit the scope of the technical ideas disclosed in this specification. The scope of protection of the technical ideas disclosed in this specification should be interpreted by the following claims, and all technical ideas within the equivalent range should be interpreted as being included in the scope of the present invention.
Claims
1. A battery management device included in a battery, a communication unit that communicates with the battery management server; transmitting status information of the battery to the battery management server while the battery is in use; receiving a discharge profile of the battery from the battery management server; a control unit that controls the battery so that it is used based on the discharge profile.
2. The control unit receiving a charging profile for the battery from the battery management server; The battery management device of claim 1 , further comprising: a charging device that transmits the charging profile to the charging device when the battery is connected to the charging device.
3. The control unit 3. The battery management device according to claim 1, wherein when the battery is used for regenerative braking, the battery management device transmits information about the state of charge of the battery to the battery management server.
4. The battery has identification information set thereon, The control unit transmitting state information of the battery to the battery management server based on the identification information; receiving the discharge profile from the battery management server based on the identification information; The battery management device according to claim 1 or 2, wherein the battery management device controls the battery so that it is used based on the discharge profile received from the battery management server based on the identification information.
5. The discharge profile includes at least one of a discharge rate according to the discharge voltage of the battery, a discharge rate according to the discharge current of the battery, a discharge rate according to the discharge time of the battery, a change in SOC according to the discharge voltage of the battery, and a change in SOC according to the discharge current of the battery, The control unit 3. The battery management device according to claim 1, further comprising: a predictor configured to predict at least one of a driving range of a device that can be driven using the power source of the battery and a power limit of the battery based on the discharge profile.
6. The control unit The battery management device according to claim 5 , wherein it is determined whether the battery needs to be charged or replaced based on the predicted driving range or power limit.
Citation Information
Patent Citations
Device for driving four wheels of vehicle
JP2002315106A
Charging system and charging method for battery
JP2013150428A
Battery replacement system for electric vehicle and program
JP2015015827A
Battery management system
JP2020005463A
Management device, battery, and management system
JP2021119555A