Method for predicting charging information of a battery of an electric vehicle

[0001] The present application claims priority to Korean Patent Application No. 10-2022-0091501, Jul. 25, 2022, the entire contents of which are incorporated herein for all purposes by this reference.

[0002] The present disclosure relates to a system and a method for predicting charging information of a battery of an electric vehicle.

[0003] A pure electric vehicle, a plug-in hybrid electric vehicle, and the like are vehicles that are driven partially or entirely by a motor and have recently received great attention in terms of environmental friendliness.

[0004] Such electric vehicles contain high-voltage batteries. The high-voltage battery stores energy for driving the motor and is configured to be rechargeable to provide the energy consumed by driving the vehicle.

[0005] Charging a battery of an electric vehicle may take place via a portable charger or at an electric vehicle (EV) charging station. When charging the battery, the user may check the amount of current charge, the remaining charging time, and the like, in a display unit of a vehicle, or in a mobile device configured to communicate with the vehicle.

[0006] The foregoing is intended merely to aid in understanding the background of the present disclosure. The foregoing is not intended to mean that the present disclosure falls within the purview of the related art that is already known to those having ordinary skill in the art.

[0007] Accordingly, the present disclosure has been made keeping in mind the above problems occurring in the related art. The present disclosure is intended to provide a system and a method, with improved convenience, for predicting charging information of a battery.

[0008] Objectives of the present disclosure are not limited to the objectives mentioned above. Other objectives not mentioned may be clearly understood by those of ordinary skill in the art to which the present disclosure belongs from the description below.

[0009] In order to achieve the above objectives as described above and to perform characteristic functions of the present disclosure to be described later, features of the present disclosure may be as follows.

[0010] The present disclosure may be a method for predicting charging information of a battery of an electric vehicle driven by energy stored in the battery, wherein the following steps are configured to be executed by a controller provided in the electric vehicle. The method includes: collecting a target moving distance from a start location to a target location of the electric vehicle; estimating required energy required for the battery to move the target moving distance; and obtaining required charging information of the battery based on estimated required energy.

[0011] According to the present disclosure, a predicted charging time of the battery is provided, calculated based on a driving distance to a target destination and by reflecting a driving habit of a driver and/or driving environment conditions. A system and a method for predicting charging information of a battery that can improve convenience when charging an electric vehicle are thereby provided.

[0012] Effects of the present disclosure are not limited to those described above. Other effects not mentioned should be clearly recognized by those having ordinary skill in the art from the following description.

[0019] Specific structural or functional descriptions presented in embodiments of the present disclosure are only exemplified for a purpose of describing embodiments according to a concept of the present disclosure. The embodiments according to the concept of the present disclosure may be implemented in various forms.

[0020] The descriptions should not be construed as being limited to the embodiments described herein and should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present disclosure.

[0021] In the present disclosure, terms such as “first” and/or “second” may be used to describe various components, but the components are not limited by the above terms.

[0022] The above terms are used only for the purpose of distinguishing one component from other components, i.e., for example, within the scope of the rights according to the concept of the present disclosure, the first component may be named as the second component, and similarly, the second component may also be referred to as the first component.

[0023] When a component is referred to as being “connected” or “coupled” to another component, it should be understood that it may be directly connected or coupled to another component, but other components may exist in between.

[0024] On the other hand, when an element is referred to as being “directly connected” or “directly coupled” to another element, it should be understood that no other element is present in between. Other expressions for describing the relationship between components, i.e., expressions, such as “between” and “immediately between” or “adjacent to” and “directly adjacent to,” should be interpreted similarly.

[0025] Like reference numerals refer to like elements throughout the specification.

[0026] On the other hand, the terms used herein are for the purpose of describing embodiments and are not intended to limit the present disclosure. In the present specification, a singular form also includes a plural form unless specifically stated in a phrase. When a component, device, element, unit, or the like of the present disclosure is described as having a purpose or performing an operation, function, or the like, the component, device, element, or unit should be considered herein as being “configured to” meet that purpose or perform that operation or function.

[0027] As used herein, “comprises” and/or “comprising” refers to a referenced component, step, action, and/or a component and does not exclude the presence or addition of one or more other components, steps, operations, and/or devices. This applies equally to similar terms such as “include” and “have” and variations thereof. The present disclosure is described in detail with reference to the accompanying drawings.

[0028] A predicted charging time of a battery may be determined based on a charging current and target charging amount. Since the battery is highly temperature-dependent, the driving distance that a vehicle may drive is different even with the same State of Charge (SoC). Therefore, in order to move the same distance, a required charging amount is inevitably different at a temperature below 32 degrees Fahrenheit and at a temperature above 32 degrees Fahrenheit. Even in the same SoC, a distance that the vehicle may be driven may vary depending on the driving tendency of a vehicle driver.

[0029] The predicted charging time of the battery calculated without considering the temperature, driving habits of a driver, and the like, may be inaccurate. Accordingly, an objective of the present disclosure is to provide a method for predicting charging information that may more accurately provide a prediction time of battery charging for a required distance to the vehicle driver by reflecting such conditions.

[0030] With reference to FIG. 1, the system for predicting charging information according to the present disclosure includes a controller 10. The controller 10 may be a battery management system (BMS) of an electric vehicle V or a separate controller provided for predicting charging information.

[0031] The controller 10 is communicatively connected to an input unit 20 and an output unit 30. In one embodiment, the input unit 20 and the output unit 30 may be a user interface provided in the vehicle V, such as a cluster of the vehicle V, and an Audio, Video, Navigation (AVN). The driver of the vehicle V may directly input a target driving distance, i.e., a target moving distance to a target location as the destination through the input unit 20, and the controller 10 is configured to receive same. The input unit 20 may include an electric charging port of the vehicle V. The controller 10 may also determine that charging is started when the charging gun is inserted into the electric charging port of the vehicle V.

[0032] The controller 10 is configured to communicate with a map information provision unit 40. In one embodiment, the map information provision unit 40 may be a navigation device mounted on the vehicle V. In one embodiment, the map information provision unit 40 may be a navigation device separate from the vehicle V but configured to communicate with the vehicle V. When the target location is input by the input unit 20, the map information provision unit 40 may generate a route to the target location and transfer the target moving distance to the target location to the controller 10 When there is a waypoint or a stop en route to the target location, the map information provision unit 40 may generate a route including the waypoint. The map information provision unit 40 may provide the controller 10 with a distance from the starting point to the waypoint, a distance from the waypoint to the target location, and a total distance from the starting position to the target location through the waypoint.

[0033] The controller 10 is configured to collect data from a data storage unit 50. In one embodiment, the data storage unit 50 may be included in the controller 10. In one embodiment, the data storage unit 50 is configured to be separate from the controller 10 but may be configured to be able to communicate with each other.

[0034] Various data may be stored in the data storage unit 50. In one embodiment, a driving record of a predetermined period may be stored in the data storage unit 50. For example, the predetermined period may be a period of months, years, or the like. The driving record for a period of time may be used to determine the driving habits of the driver. Based on the driving record for the predetermined period of time, the distance driven by the driver on average with respect to a unit change in the SoC in % (km/%) may be calculated. The energy E, e.g., in kilowatt-hour (kWh), consumed on average per the distance s when the unit change in the SoC in % is made may be calculated in kWh/km based on the driving record for the predetermined period. Alternatively, the energy E consumed for unit change in the state of charge (SoC in %) may be calculated in kWh/% based on the driving record for the predetermined period. Alternatively, the average use of current may be obtained based on the driving record of the predetermined period. An expected value of an average use of current in the future may be predicted according to the existing driving conditions through maps or formulas.

[0035] For example, by accumulating the currents of previous driving records, for example, a prior record collected from vehicle start (KEY ON) to vehicle stop (KEY OFF,) the average use of current per hour (Ampere-hour/hour) may be calculated. This calculation method is only an example, and the average use of current may be determined by other methods.

[0036] In one embodiment, the data storage unit 50 may store seasonal outdoor temperature information. For example, the outdoor temperature information may be an average temperature at a predetermined point in a year. Since temperature greatly affects the performance of the battery, the present disclosure is configured to determine a target SoC in consideration of the outdoor temperature information stored in the data storage unit 50.

[0037] The controller 10 is configured to perform a computation for obtaining a target moving distance. The controller 10 is configured to calculate the required energy necessary to move to a target location based on environmental conditions including a battery state and temperature driving characteristics of a driver, and the like.

[0038] The controller 10 includes a state of health (SoH) calculation unit 110 configured to calculate the SoH of the battery. The SoH of the battery is the ratio of a current maximum capacity to a rated capacity of the battery enabling the aging of the battery to be estimated. Alternatively, the SoH of the battery may be determined by comparing an initial SoH measured with respect to an initial battery state with the current SoH based on the factors that change according to the use of the battery. As a non-limiting example, the factors may include internal resistance, voltage, charging performance, and the like of the battery. For example, the SoH may be calculated through a value obtained by dividing an integrated current value by an amount of a change in the SoC. The amount of a change in the SoC may be estimated through mapping of the SoC-open circuit voltage (OCV). Calculation of the SoH is not performed only in the above-described manner and may be calculated through other methods.

[0039] The controller 10 includes a no-load energy calculation unit 210 configured to calculate the no-load energy of the battery. For example, the no-load energy of the battery may be obtained through a map or a lookup table provided for each SoC and temperature of the battery.

[0040] The controller 10 includes an energy change calculation unit 310 configured to calculate an energy change according to a preset factor that is a usage condition. The preset factors may include the SoC, temperature, average current, and expected temperature change, of the battery. The energy change for each factor may be stored in the data storage unit 50 in a form of a map, a lookup table, or the like. The controller 10 may retrieve necessary data from the data storage unit 50. In some embodiments, the energy change for each factor may be determined by an equation. As a non-limiting example, the expected temperature change may be determined based on the amount of change in the SoC, the temperature of the battery, the outside temperature, and the like. The predicted value determined using an experiment or a temperature model may be used.

[0041] In some embodiments, SoC, temperature, average usage current, SoH, no-load energy, terminal voltage, and the like, of the battery, are stored in the battery management system (BMS) of the vehicle V or may always be measured or calculated. The controller 10 may also acquire necessary battery information from the battery management system (BMS).

[0042] A method for predicting charging information of a battery according to the present disclosure is described with reference to FIG. 2.

[0043] Predicting charging information of a battery according to the present disclosure starts with requesting charging or starting charging in step S100. The charging request may be determined by the input of the driver through the input unit 20. For example, the charging may be determined to start in accordance with the charging gun being inserted into the electric charging port of the vehicle V.

[0044] The controller 10 is configured to collect target moving distances in order to calculate the predicted charging time required to reach an SoC required to move a target moving distance in S200.

[0045] As shown in FIG. 3, in some embodiments, the target moving distance may be directly input by the driver through the input unit 20. In some embodiments, the target moving distance may be determined by the driver inputting the target location through the input unit 20. When the driver inputs the target location, the map information provision unit 40 may generate a route to the target location and transfer a required target moving distance to the target location to the controller 10.

[0046] At step S201, the target moving distance is directly input by the driver through the input unit 20. The controller 10 determines whether the input target moving distance is greater than the attainable mileage or distance when the vehicle V is fully charged in S203. When it is determined that the input target moving distance is no greater than the attainable distance when the vehicle V is fully charged, the controller 10 sets a target moving distance input by the driver as a target moving distance in S205. When it is determined that the input target moving distance exceeds the attainable distance when the vehicle V is fully charged, the controller 10 sets the attainable distance when the vehicle V is fully charged as the target moving distance in S207. In some embodiments, the controller 10 may notify through the output unit 30 that charging is required at least one more time to move the target moving distance. When the target distance input by the driver is greater than the attainable distance when fully charged, the controller 10 carries out a computation hereafter to provide a predicted charging time required to charge the state of charge (SoC) until fully charged. The controller 10 sets the attainable distance on a full charge as the target moving distance. The attainable distance on a full charge means a maximum distance possible for the vehicle V to travel when the vehicle V is fully charged. The controller 10 may notify the driver through the output unit 30 of the fact that the moving distance to the target location is greater than the attainable distance on a full charge and that the charging time required until full charging is predicted and provided, accordingly.

[0047] When the driver inputs the target location instead of the target moving distance through the input unit 20, the process proceeds to step S202. When the target location is input by the input unit 20, the controller 10 causes the map information provision unit 40 to calculate the distance to the target location at S204. According to the present disclosure, in preparation for a case where the distance to the target location is greater than the distance that the vehicle V may be driven when fully charged, the controller 10 may determine whether the distance to the target location is greater than the distance that the vehicle V may be driven when fully charged. The controller 10 compares the distance to the target location calculated by the map information provision unit 40 and the distance to be able to drive when the vehicle V is fully charged at S206. When the distance to the target location calculated by the map information provision unit 40 is equal to or less than the distance to be able to drive when fully charged, the controller 10 sets the distance to the target location calculated by the map information provision unit 40 as the target moving distance at S208.

[0048] When the distance to the target location calculated by the map information provision unit 40 is greater than the distance to be able to drive when fully charged, the controller 10 causes the map information provision unit 40 to search for an electric vehicle charging station located on the route to the target location at S210. The controller 10 is configured to select the most suitable station, for example, an electric vehicle charging station located closest to the route and located at a certain distance from the starting position. The controller 10 instructs the map information provision unit 40 to generate a route that includes the waypoint including the selected charging station to the target location at S212. The map information provision unit 40 is configured to set the target moving distance for determining a predicted charging time as the distance to the selected electric vehicle charging station and transfer a set distance to the controller 10 at S214.

[0049] With reference again to FIG. 2, when the target moving distance is obtained as such, the controller 10 calculates the required energy for moving the target moving distance at S300 and calculates the target state of charge (SoC) that may satisfy the required energy in S400. The controller 10 calculates the predicted charging time required to obtain the calculated target state of charge (SoC) at S500 and provides the calculated predicted charging time to the driver through the output unit 30 at S600.

[0050] With reference again to FIG. 4, according to some embodiments of the present disclosure, the required energy for moving the target moving distance of step S300 may be calculated as shown in FIG. 4.

[0051] The controller 10 calculates an initial value of the required amount of a change in the SoC based on the set target moving distance at S301. The initial value of SoC change is determined based on the driving record of the driver. For example, assume that the driving distance per unit change in the SoC of the battery derived from the driving record of the driver and stored in the data storage unit 50 is 4 km, and the target moving distance is 300 km. Then the initial value of the required amount of a change in the SoC is 75%. For example, when the current state of charge (SoC) of the battery is 25%, the target state of charge (SoC) is 50% based on the initial value of SoC change of 75%.

[0052] According to some embodiments of the present disclosure, as indicated by the dotted line box A, the controller 10 is configured to estimate the required energy based on a calculation result performed for calculating the required energy by the SoH calculation unit 110, the no-load energy calculation unit 210, and the energy change calculation unit 310.

[0053] The controller 10 is configured to calculate an expected energy change according to a usage condition calculated from the energy change calculation unit 310 in S310. As described above, the expected energy change value according to the usage condition may be determined by a formula based on average use of current of the battery, the SoC, a temperature of the battery, an outside temperature, available energy of the battery, and the like. The formula may be stored in the data storage unit 50, and calculation may be performed by the controller 10.

[0054] The controller 10 subtracts the estimated terminal voltage and the currently measured terminal voltage, of the battery. Moreover, the controller 10 is configured to calculate an amount of correction proportional to the subtracted value in consideration of the temperature and the SoC at S312. The amount of correction may be obtained by multiplying a difference between the estimated terminal voltage and the currently measured terminal voltage by the battery capacity or available energy. In addition to the estimated terminal voltage, the electromotive force of the battery, internal resistance, polarization voltage, and the like, may be considered.

[0055] The no-load energy calculation unit 210 of the controller 10 is configured to calculate the no-load energy of the battery at S314. No-load energy may be determined by the battery management system (BMS) based on the temperature, the SoC, and the like.

[0056] The SoH calculation unit 110 of the controller 10 is configured to calculate the SoH during normal charging at S316.

[0057] The controller 10 is configured to calculate a required energy estimation value E1 at S318 based on the values calculated in steps S310 to S316. The controller 10 subtracts an expected energy change value according to the usage condition from the no-load energy calculated by the no-load energy calculation unit 210. The calculated amount of correction is added to the subtracted energy change value. The required energy estimation value E1 may be calculated by multiplying the SoH during normal charging calculated by the SoH calculation unit 110.

[0058] According to some embodiments of the present disclosure, the required energy may also be estimated based on a driving habit of a driver. According to some embodiments of the present disclosure, as indicated by a dotted line box B, the required energy may be calculated through the energy required per unit moving distance s stored in the data storage unit 50 in S320. For example, in light of a driving habit record of a driver stored in the data storage unit 50, assume that the driver consumes 0.2 kWh of energy E per one kilometer that is a unit moving distance s. Then an energy equivalent to 60 kWh is required when the target moving distance is 300 km. The energy calculated as described above may be estimated at S322 as a required energy estimation value E2.

[0059] According to some embodiments of the present disclosure, the required energy may be calculated at S330 based on the energy required for a unit change in the state of charge (SoC) calculated based on the driving record of the driver stored in the data storage unit 50. For example, in light of the record in the data storage unit 50, assume that the driver consumes 4 kWh of energy on average when the state of charge (SoC) is subjected to the unit change. Then it is determined that the state of charge (SoC) of 75% is required for the target moving distance of 300 km. Energy corresponding to the required amount of change in the SoC (ΔSoC) of 75% may be estimated at S332 as a required energy estimation value E3.

[0060] When estimating the required energy estimation values E1, E2, and E3, the initial value calculated at step S301 is used as the required amount of change in the SoC (ΔSoC). The initial value of the SoC may act as a temporary value for determining the target SoC. A required energy is estimated based on at least in part the initial value of the SoC. As explained below with reference to FIG. 5, the target state of charge reflecting the current actual state of charge of the battery may be obtained by being iteratively calculated by being compared with the actual state of charge of the battery.

[0061] According to some embodiments of the present disclosure, the maximum value among the required energy estimation values E1, E2, E3 may be selected by the controller 10 at S303. The required energy is selected as the maximum value in order to minimize the error in the predicted charging time that is provided as more energy than the estimated energy is consumed.

[0062] With reference again to FIG. 2, the controller 10 is configured to calculate the required state of charge required for the estimated required energy. The required state of charge may be provided as SoC (unit: %) at S400.

[0063] When the target SoC is calculated, the controller 10 calculates a predicted charging time for reaching the target SoC at S500.

[0064] The controller 10 may display the calculated predicted charging time on the output unit 30 and provide same to the driver in S600.

[0065] With reference again to FIG. 5, according to the present disclosure, in order to calculate the target state of charge of the battery, an initial value of SoC change is corrected through iterations. For example, the expected temperature change may be determined based on the calculated initial value of SoC change. Alternatively, for example, the initial value of SoC change is used as the required amount of change in the SoC when calculating the energy (box C in FIG. 4) required for a unit change in the state of charge calculated based on the driving record of the driver.

[0066] The controller 10 derives an attainable distance for the vehicle V to be able to drive with the currently available energy of the battery at S305. In some embodiments, the attainable distance with respect to available energy may be obtained through a map, a lookup table, or the like.

[0067] The controller 10 compares the target moving distance calculated at step S200 with the attainable distance with the calculated current available energy, at S307 and S309. The controller 10 is configured to calculate the amount of a change in the SoC (i.e., the target SoC) required to move the target moving distance based on the current SoC of the battery.

[0068] When there is no difference between the target moving distance and the calculated distance to be able to drive, the process proceeds to step S400. For example, in the above example, assume that the required driving distance is 100 km, and the distance to be able to drive is also 100 km. Then the target state of charge for the estimated energy selected at step S303 is calculated at step S400. It may be determined that the target state of charge corresponding to the estimated required energy determined based on the initial value of a change in the SoC is required to move the target moving distance.

[0069] When there is a difference between the target moving distance and the calculated distance to be able to drive, it is determined whether the difference value is positive or negative at S309. When the difference between the target moving distance and the calculated distance to be able to drive is greater than 0, −α% is subtracted from the initial value of SoC change, and the process proceeds to S311 next to step S301. A required actual state of charge may be calculated in consideration of the currently available energy of the vehicle V, i.e., the current distance to be able to drive.

[0070] When the difference between the target moving distance and the calculated distance to be able to drive is 0 or less, the controller 10 is configured to add α% to the initial value of SoC change value and move after step S301 to perform the following steps at S313. As a non-limiting example, α% may be 1%.

[0071] Calculations continue until the target moving distance and the calculated distance to be able to drive are the same. When the target moving distance and the calculated distance to be able to drive become the same, the required energy estimation value at that time is converted into the target state of charge (SoC) at S400. The predicted charging time for the target SoC is obtained and provided to the driver at S500 and S600.

[0072] As described above, the present disclosure may provide the predicted charging time required in accordance with an input of the target moving distance, thereby promoting the convenience of the electric vehicle driver. The controller and various units described herein may include one or more processors or may utilize the same processor, may include a storage or memory, i.e. a transitory and/or non-transitory memory and may be configured to perform the above described method steps, calculations, estimations, and the like.

[0073] The present disclosure may provide a predicted charging time in consideration of the driving habits by each individual driver, thereby providing more accurate and reliable results.

[0074] The concepts of the present disclosure described above is not limited by the above-described embodiments and the accompanying drawings. It should be clear to those who have ordinary skill in the technical field to which the present disclosure pertains that various substitutions, modifications, and changes are possible within the scope without departing from the technical spirit of the present disclosure.