Battery charging device and battery management device
The integration of a battery charging device and a battery management device with a communication server allows for efficient battery management by analyzing individual battery states and predicting SOC and lifetime, addressing the challenges of battery aging and degradation in existing systems.
Patent Information
- Application Number
- JP2025008700
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-09-03
- Filing Date
- 2025-01-21
- Publication Date
- 2025-04-15
- Estimated Expiration
- 2042-08-30
AI Technical Summary
Existing battery management systems struggle to efficiently charge and manage multiple batteries, as they do not account for individual battery states, leading to potential issues with aging and degradation.
A battery charging device and a battery management device that communicate with a battery management server to obtain and analyze charging profiles for each battery, allowing for controlled charging based on individual battery states, predicting state of charge (SOC) and lifetime, and determining loanability.
The system enables efficient charging and management of batteries by tailoring charging profiles to individual battery states, predicting SOC and lifetime, and ensuring that only suitable batteries are loaned, thereby extending battery life and improving operational efficiency.
Smart Images

Figure 2025063255000001_ABST
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 the Korean patent application are incorporated herein by reference.
[0002] SUMMARY OF THE DISCLOSURE The embodiments disclosed herein relate to a battery charging system and a battery management system. [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, and the like. In addition, lithium-ion batteries can be manufactured to be small and lightweight, and are therefore used as power sources for mobile devices. Recently, the range of use has been 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 a means of transportation using a battery, there may be cases where the battery is replaced and used. There may be a charging station that charges and lends out such replaceable batteries, and a large number of replaceable batteries may be charged and lent out at the charging station. Since the degree of aging or degradation of a battery varies depending on the method of using the battery or the state of the battery, problems may occur when a large number of batteries are managed in the same way. Summary of the Invention [Problem to be solved by the invention]
[0005] One objective of the embodiments disclosed in this specification is to provide a battery charging apparatus that can be controlled to efficiently charge each battery based on the state of each battery.
[0006] Another object of the embodiments disclosed in this specification is to provide a battery management device that can efficiently utilize 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 state 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 can 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 predict a mileage and a probability of a breakdown based on the predicted SOC.
[0010] In an embodiment, the control unit may determine whether the at least one battery can be rented based on a travel distance and whether the at least one battery has a malfunction.
[0011] In one embodiment, the control unit can predict a life span of each of the at least one battery based on a charging profile of the at least one battery, and determine whether or not the at least one battery can be loaned based on the predicted life span.
[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 a status of the at least one battery to the battery management server based on 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, a 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 charging and battery status information when a device including the at least one battery is performing regenerative braking.
[0015] In an embodiment, the controller may obtain a charging 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 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 controller may receive a charging profile of the battery from the battery management server, and when the battery is connected to a charging device, transmit the charging profile 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, 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 mileage 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. Effect of the Invention
[0022] A battery charging apparatus according to an embodiment disclosed herein can control the charging of each battery efficiently 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 loan 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 the power limit or mileage based on the 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 description of the drawings]
[0027] [Figure 1] FIG. 1 illustrates a system including a battery charging device and a battery management device according to one embodiment disclosed herein. [Diagram 2] 1 is a block diagram illustrating a battery charging device according to one embodiment disclosed herein. [Diagram 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 regarding a battery according to one embodiment disclosed herein. [Diagram 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 disclosed in this specification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0028] Hereinafter, the embodiments disclosed in this specification will be described in detail with reference to the drawings. When attaching reference numerals to components in each drawing, it should be noted that the same components are assigned the same numerals as much as possible even if they are displayed in different drawings. In addition, when describing the embodiments disclosed in this specification, if it is determined that a detailed description of such known configurations or functions would hinder understanding of the embodiments disclosed in this specification, the detailed description will be omitted.
[0029] In describing the components of the embodiments disclosed herein, terms such as first, second, A, B, (a), (b) and the like may be used. Such terms are merely used to distinguish the components from other components, and do not limit the essence, order, or sequence of the components. In addition, 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 belong. Terms that are 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 an embodiment disclosed herein can communicate with a battery management server 10, a user terminal 20, and a battery management apparatus 200. In an 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 described below. In an embodiment, the battery management apparatus 200 shown in FIG. 1 may be substantially the same as the battery management apparatus 200 shown in FIG. 3 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 can 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 traveled using the battery, and the battery charging apparatus 100 can select a battery to be lent based on the inputted travel distance. For example, the battery charging apparatus 100 can predict a current SOC of at least one battery, can predict a possible travel distance based on the current SOC, and can lend a battery corresponding to the travel distance input by the user terminal 20. That is, the user terminal 20 can receive a battery corresponding to the travel distance from the battery charging apparatus 100, and can use the battery efficiently.
[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 charging profile of the battery from the battery management unit 200. In this case, the battery charging device 100 does not need to receive the charging profile of the battery from the battery management server 10, so charging can be performed quickly in terms of time. 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 an internal storage. In this case, even when the battery management unit 200 is subsequently connected to another charging device, it can perform efficient charging by transmitting the charging profile to the other charging device. In one embodiment, if the battery charging device 100 is 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 charging device 100 can be controlled to charge the battery based on the charging profile stored in the battery management unit 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 may transmit the charge and / or discharge state information of the battery to the battery management server 10. The battery management server 10 may generate a charge and / or discharge profile of the battery based on the received charge and / or discharge state information of the battery. For example, when the battery identification information is received together with the charge and / or discharge state information of the battery, the battery management server 10 may store and / or transmit the charge and / or discharge profile of the battery corresponding to the received battery identification information. The battery management device 200 may receive the charge and / or discharge profile of the battery from the battery management server 10 and may 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 the same as the battery charging device 100 of FIG.
[0039] The 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 may communicate with the battery management server 10 (see FIG. 1). The communication unit 110 may 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 may include 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 may communicate with an external electronic device 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 using the corresponding communication circuit. The various types of communication units 110 described above may be implemented in one chip or may be implemented in separate chips.
[0041] The control unit 120 may obtain status information of at least one battery connected to the battery charging apparatus 100. For example, the control unit 120 may obtain the status information of at least one battery from a 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 a voltage, a current, a temperature, and an insulation resistance of the battery. In addition, the battery status information may include parameters indicating the state of the battery, 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 charging state 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 charging speed, the remaining battery capacity, the charging current, the charging voltage, the charging time, and whether or not the battery is faulty, for each of the at least one battery being charged.
[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 charging profile of the battery based on the state information of the battery and the comparison information of the state of charge transmitted from the control unit 120.
[0044] The control unit 120 may receive a charging profile of each of at least one battery from the battery management server 10. For example, the charging profile of the battery may include at least one of the number of times the battery has been charged, the charging rate according to the charging voltage, the charging rate according to the charging current, the charging rate according to the charging time, the change in SOC according to the charging voltage, and the change in SOC according to the charging current. For another example, the charging profile of the battery may have a graph of the charging current, voltage, and time at which the battery can be efficiently charged. In one embodiment, the charging profile of the at least one battery may be generated based on at least one of the battery status information when the at least one battery is being charged and the battery status information when the 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 driven using a power source of 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. As 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. As 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, mileage, and failure of the device to which the battery is attached based on the predicted SOC. For example, the control unit 120 can predict the mileage based on data on average battery usage by the device using the battery and the predicted SOC of the battery. For another example, the control unit 120 can determine that the battery is broken when the battery is in at least one of an uncharged state, a state in which the remaining SOC is equal to or less than a critical value, and a state in which the battery is broken. In one embodiment, the control unit 120 can determine whether the battery is usable based on the mileage and failure of the battery.
[0048] The control unit 120 may determine whether or not at least one battery can be lent based on the predicted mileage and failure of the at least one battery. For example, when a battery lending request is received from a user, the control unit 120 may lend to the user a battery having 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 battery determined to be broken so that it is not lent. In one embodiment, the control unit 120 may manage the battery so that the user does not travel 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 when there is no battery that allows the user to travel 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 guide the user to move to another battery charging device and then replace the battery. In one embodiment, if there is no battery that can enable driving for a distance greater than the mileage 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 mileage 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, when 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 obtain status information of the battery etc. connected to the other battery charging device. The control unit 120 can guide the user to a battery charging device in which a battery corresponding to the mileage input by the user exists, based on the status information of the battery etc. connected to the other battery charging device.
[0050] The control unit 120 may predict the lifespan of at least one battery based on a charging profile of the at least one battery. For example, the control unit 120 may predict the lifespan of the battery based on at least one of the number of times the battery has been charged, the charging speed, 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 or not at least one battery can be lent based on the predicted lifespan. For example, the control unit 120 may control a battery that is predicted to have run out of life to not be lent any more. For another example, the control unit 120 may control a battery that has a lot of life left based on the predicted lifespan to be lent to a user who drives long distances, and may control a battery that does not have much life left to be lent to a user who drives short distances. In one embodiment, the control unit 120 may determine whether or not to lend a battery to a user by considering both the SOC and lifespan predicted based on the charging profile.
[0052] Each of the at least one battery connected to the battery charging device 100 may have its own identification information set therein. For example, each of the at least one battery may have an ID.
[0053] The control unit 120 may acquire a state 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 state information and correspond the acquired state information to the identification information of the battery. The control unit 120 may transmit the state of at least one battery corresponding to 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 state information corresponding to the battery identification information. In this case, the battery management server 10 may generate a charging profile of the battery based on the battery state information and correspond the generated charging profile to the battery identification information.
[0054] The control unit 120 may receive a charging profile of at least one battery from the battery management server 10 based on the identification information of each of the at least one battery. 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 may control the battery to be charged using the received charging profile.
[0055] The battery charging apparatus 100 according to an embodiment disclosed herein may acquire battery status information and transmit it to the battery management server 10, and may receive a battery charging profile from the battery management server 10. Based on the received charging profile, the battery charging apparatus 100 may efficiently charge the battery and may predict the SOC or life of the battery to determine whether to lend the battery to a user. In addition, the battery charging apparatus 100 may continuously update the battery charging profile by managing the battery charging profile based on the battery identification information, and may individually charge the battery based on the charging profile of each battery. That is, the battery charging apparatus 100 may individually manage, charge, and / or lend each connected battery.
[0056] 3 is a block diagram illustrating a battery management device according to one embodiment disclosed herein. In one embodiment, the battery management device 200 of FIG. 3 may be substantially identical to the battery management device 200 of FIG.
[0057] 3, a battery management device 200 according to an embodiment disclosed herein may be included in a battery 2000. The battery management device 200 may manage and / or control a state and / or operation of the battery 2000. For example, the battery management device 200 may manage and / or control a state and / or operation of a plurality of battery cells included in the battery 2000. The battery management device 200 may manage charging and / or discharging of the battery 2000.
[0058] Furthermore, the battery management device 200 can monitor the voltage, current, temperature, insulation resistance, and the like of the battery 2000. The battery management device 200 can calculate parameters indicating the state of the battery 2000, such as a state of charge (SOC) and a state of health (SOH), based on the measured values of the monitored voltage, current, temperature, and the like. In one embodiment, the battery 2000 managed by the battery management device 200 may 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, and the like.
[0059] The battery management unit 200 may include a communication unit 210 and a control unit 220.
[0060] The communication unit 210 may communicate with the battery management server 10 (see FIG. 1). The communication unit 210 may 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 may communicate with an external electronic device 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 using the corresponding communication circuit. The various types of communication units 210 described above may be implemented in one chip or in 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 a battery current, a voltage, a charge rate, a discharge rate, a SOC, and a SOH.
[0062] The control unit 220 can transmit the battery state information to the battery management server 10. For example, the control unit 220 can transmit the 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 discharge profile of the battery based on the battery state information while the battery 2000 is in use.
[0063] The control unit 220 can receive a discharge profile of the battery from the battery management server 10. For example, the discharge profile of the battery may include at least one of the number of times the battery 2000 is charged and discharged, the discharge rate according to the discharge voltage, the discharge rate according to the discharge current, the discharge rate according to the discharge time, the change in SOC according to the discharge voltage, and the change in SOC according to the discharge current. For another example, the discharge profile of the battery 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 can receive the charging profile of the battery from the battery management server 10. For example, the charging profile of the battery may include at least one of the number of times the battery 2000 is charged, the charging rate according to the charging voltage, the charging rate according to the charging current, the charging rate according to the charging time, the change amount of the SOC according to the charging voltage, and the change amount of the SOC according to the charging current. For another example, the charging profile of the battery may be in the form of a graph related to the charging current, voltage, and time at which the battery 2000 can be efficiently charged. In one embodiment, the charging profile of the battery may be generated based on at least one of the battery status information when the battery 2000 is being charged and the battery status information when the 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 the power source of the battery.
[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 charging state information of the battery 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 that 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 mileage 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 mileage and the 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 inform the user of the predicted mileage or power limit, and may prevent the battery 2000 from being used beyond the predicted mileage or power limit.
[0069] The control unit 220 may determine whether or not the battery 2000 needs to be charged or replaced based on the predicted mileage or power limit. For example, if the user intends to travel a distance greater than the predicted mileage based on the predicted mileage, the control unit 220 may determine that the battery 2000 needs to be charged or replaced, and may inform the user of the determined result. In another example, if the user intends to use the battery more than the predicted power limit of the battery 2000, for example, to increase the speed, the control unit 220 may determine that the user needs to charge or replace the battery 2000, and may inform the user of the determined 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 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 may associate the generated charging profile with the battery identification information.
[0072] The control unit 220 may receive a charging profile or a discharging profile of the battery from the battery management server 10 based on the identification information of the battery. For example, when the control unit 220 requests a charging profile or a discharging profile of the battery from the battery management server 10, the control unit 220 may transmit the identification information of the battery together, and the battery management server 10 may search for a charging profile or a discharging profile corresponding to the transmitted identification information of the battery and transmit the charging profile or the discharging profile to the control unit 220. Thus, the control unit 220 may receive a charging profile or a discharging profile corresponding to the transmitted identification information of the battery, and may control the battery to be efficiently charged or discharged using the received charging profile or the discharging 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. In addition, the devices 1 and 2 using batteries can transmit status information of the batteries being charged during regenerative braking to the battery management server 10.
[0076] The battery management server 10 can generate a charging profile and / or a 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 using the battery. Although not shown in Fig. 4, the battery management server 10 can transmit the generated charging and / or discharging profile to all the devices 1, 2, 3, 4, 5, 100 in which the battery is used and / or charged. For example, the battery management server 10 can transmit the charging and / or discharging profile to all the devices in which the battery is used and / or charged based on the 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 device included in the battery 3 and charge the battery 3 based on the received charging profile.
[0078] When there is a request to use the battery 4, the battery charging device 100 can provide the battery 4 to a user (or a device using the battery). In this case, the device 5 using the battery can receive a discharge profile from the battery management server 10 or a battery management device included in the battery 4, and can use the battery 4 based on the received discharge profile.
[0079] FIG. 5 is a block diagram showing 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 FIG. 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 memory 1020, RAM, DRAM, SRAM, etc. may be used. As the non-volatile memory 1020, ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. may be used. The examples of the memory 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 to transmit and receive data.
[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, a program for measuring the voltage of a battery cell and controlling switching, and various data, can be transmitted and received from a separately provided external server via the communication I / F 1040.
[0086] In this manner, 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 performing, for example, each function shown in FIG.
[0087] In one embodiment, the computing system 1000 may also be applied to the battery charging device 100 in Fig. 2. That is, the battery charging device 100 in 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 may be made by a person having ordinary knowledge in the technical field to which the embodiments disclosed in this specification pertain, 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 to 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 according to the following claims, and all technical ideas within the same range should be interpreted as being included in the scope of the present invention.
Claims
1. A communication unit that communicates with the battery management server; transmitting battery status information to the battery management server while the battery is in use; receiving a discharge profile of the battery from the battery management server; and a control unit that controls the battery so that it is used based on the discharge profile.
2. The control unit is receiving a charging profile of 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 coupled to the charging device.
3. The control unit is The battery management device according to claim 1 or 2, wherein when the battery is used for regenerative braking, the battery management device transmits charge state information of the battery to the battery management server.
4. The battery has identification information set thereon, The control unit is transmitting state information of the battery to the battery management server based on the identification information; The battery management device according to claim 1 , further comprising: a battery management server configured to receive the discharge profile or the charge profile from the battery management server based on the identification information.
5. The control unit is The battery management device according to claim 1 , further comprising: a predictor configured to predict at least one of a mileage and a power limit based on the discharge profile.
6. The control unit is The battery management device according to claim 5 , further comprising a step of determining whether the battery needs to be charged or replaced based on the predicted mileage 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