Vehicle control device, server, and vehicle control method

Abstract

The invention discloses a vehicle control apparatus, a server, and a vehicle control method. A vehicle control device obtains a unique ID of a charger based on a vehicle in which a battery is charged using the charger, identifies vehicle data including at least a time at which charging of the battery is started, an SOC of the battery at the start of charging of the battery, a capacity of the battery, a time at the end of charging of the battery, or an SOC of the battery at the end of charging of the battery, calculating an actual charging speed including a speed at which the charger actually charges the battery based on the vehicle data, and providing information about charging speed data to a user, at least one of the actual charging speed or the unique ID of the charger is included using at least one of a display of the vehicle or an audio device of the vehicle.

Description

[0001] Application

[0002] This application claims the benefit of priority from Korean Patent Application No. 10-2024-0041285, filed on March 26, 2024, in the Korean Intellectual Property Office, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to a vehicle control device, a server, and a vehicle control method, and more particularly, to a technology for charging a vehicle battery. Background Art

[0004] Recently, there has been an increasing popularity of vehicles that allow users to directly charge their batteries. For example, in the case of electric vehicles or plug-in hybrid vehicles, users are able to directly charge the vehicle's battery.

[0005] In order for the user to charge the vehicle battery, the user accesses various information related to battery charging. For example, the user can obtain information related to the charger for the vehicle battery via various media such as the vehicle's navigation system, mobile applications, Internet websites, etc.

[0006] Specifically, the user can receive information about the charging speed of each charger via the above medium. For example, the user can receive information about whether the charger supports ultra-fast charging mode, fast charging mode, or slow charging mode based on the charging speed of each charger.

[0007] In the past, users may have received information about charging speeds included in the charger's specifications, rather than the actual charging speed of the vehicle battery. Consequently, there has been a problem in that the charging speed information provided to the user often differs from the actual charging speed of the vehicle battery due to factors such as weather conditions and aging of the charger.

[0008] Therefore, there is a need for technology that can provide information about the speed at which each charger is actually charging the vehicle. Summary of the Invention

[0009] The present disclosure has been made to solve the above-mentioned problems occurring in the prior art while keeping the advantages achieved by the prior art intact.

[0010] One aspect of the present disclosure provides a vehicle control device, a server, and a vehicle control method, which collect information about the actual charging speed of a vehicle battery by each charger and provide a user with information about the accurate charging speed of each charger based on the collected information.

[0011] An aspect of the present disclosure provides a vehicle control device, a server, and a vehicle control method that allow a user to more accurately estimate the time required to charge a vehicle battery using a corresponding charger by providing the user with information about the speed at which the vehicle battery is actually charged for each charger.

[0012] One aspect of the present disclosure provides a vehicle control device, a server, and a vehicle control method that collect information about the actual charging speed of a vehicle's battery for each charger and provide a user with information reflecting changes in the charging speed according to the age of the charger, season, weather, etc.

[0013] An aspect of the present disclosure provides a vehicle control device, a server, and a vehicle control method that determine performance of a charger by continuously updating information on a speed at which a battery of a vehicle is actually charged for each charger.

[0014] The technical problems to be solved by the present disclosure are not limited to the above-mentioned problems, and any other technical problems not mentioned herein will be clearly understood by those skilled in the art to which the present disclosure belongs from the following description.

[0015] According to one aspect of the present disclosure, a vehicle control device includes: a first memory storing program instructions; and a first processor executing the program instructions, and the first processor can obtain a unique ID of the charger based on a vehicle using the charger to charge a battery, identify vehicle data including at least one of the time when charging of the battery starts, the SOC (state of charge) of the battery when charging of the battery starts, the capacity of the battery, the time when charging of the battery ends, or the SOC of the battery when charging of the battery ends, or any combination thereof, calculate an actual charging speed based on the vehicle data, the actual charging speed including the speed at which the charger actually charges the battery, and use at least one of a display of the vehicle or an audio device of the vehicle, or any combination thereof, to provide a user with information about the charging speed data, the charging speed data including at least one of the actual charging speed or the unique ID of the charger, or any combination thereof.

[0016] According to an embodiment, the first processor may calculate at least one of a maximum value of the actual charging speed calculated for the cycle, a minimum value of the actual charging speed calculated for the cycle, or an average value of the actual charging speed calculated for the cycle, or any combination thereof, based on the actual charging speed calculated for each cycle between the charging start time and the charging end time of the battery.

[0017] According to an embodiment, the first processor may recognize that the actual charging speed for each cycle was not calculated due to any of the following reasons: charging the battery while the vehicle's engine was off, battery charging was abnormally terminated, charging speed data was not transmitted to the server due to a communication failure, or any combination thereof. The processor may calculate an average of the actual charging speeds over the entire charging time by multiplying the difference between the battery SOC at the end of charging and the battery SOC at the start of charging by the battery capacity, and dividing the result by the total charging time from the start to the end of charging. According to an embodiment, the first processor may obtain a unique ID for the charger from map data used to guide the vehicle's route.

[0018] According to an embodiment, the first processor may send charging speed data to the server, receive charging speed data for each charger, the charging speed data including data matching the actual charging speed, the unique ID of the charger, the date on which the server receives the charging speed data, and the time when the server receives the charging speed data, and provide information about the charger-specific charging speed data to the user using at least one of a display of the vehicle, an audio device of the vehicle, or any combination thereof.

[0019] According to one aspect of the present disclosure, a server includes: a second memory storing second program instructions; and a second processor executing the second program instructions, and the second processor can receive charging speed data from a vehicle, the charging speed data including at least one of an actual charging speed at which a battery of the vehicle is actually charged by a charger, or a unique ID of the charger, or any combination thereof, and generate charger-specific charging speed data including data matching the actual charging speed, the unique ID of the charger, a date when the charging speed data is received, and a time when the charging speed data is received.

[0020] According to an embodiment, the second processor may match external factor information including at least one of season, weather, outside temperature, vehicle type, vehicle age, or charger age, or any combination thereof, with the charger-specific charging speed data.

[0021] According to an embodiment, the second processor may provide information related to the charger-specific charging speed data to the user via at least one of the vehicle's navigation system, a mobile application, or a webpage, or any combination thereof.

[0022] According to an embodiment, the second processor may receive charging speed data from the vehicle, the charging speed data including an actual charging speed calculated for a cycle, a maximum value of the actual charging speed calculated for a cycle, a minimum value of the actual charging speed calculated for a cycle, an average value of the actual charging speed calculated for a cycle, and an average value of the actual charging speed for the entire charging time elapsed from the start time of charging of the battery to the end time of charging of the battery.

[0023] According to an embodiment, the average of the actual charging speed throughout the charging time may be calculated as a value obtained by multiplying a difference between the SOC of the battery at the end of charging of the battery and the SOC of the battery at the start of charging of the battery by the capacity of the battery and dividing it by the entire charging time.

[0024] According to an embodiment, the second processor may identify the entire charging time elapsed from the time charging of the battery starts to the time charging of the battery ends, and receive charger output data from the charger, the charger output data including at least one of a unique ID of the charger, a maximum value of an output speed at which the charger outputs power during the entire charging time, a minimum value of an output speed at which the charger outputs power during the entire charging time, or an average value of an output speed at which the charger outputs power during the entire charging time, or any combination thereof.

[0025] According to an embodiment, the second processor may compare the charger output data with the charging speed data to determine the performance of the charger.

[0026] According to one aspect of the present disclosure, a vehicle control method includes: a vehicle control device identifying that a vehicle is charging a battery using a charger; the vehicle control device identifying vehicle data, the vehicle data including the time when charging of the battery starts, the SOC (state of charge) of the battery when charging of the battery starts, the capacity of the battery, the time when charging of the battery ends, or the SOC of the battery when charging of the battery ends, or any combination thereof; the vehicle control device calculating an actual charging speed based on the vehicle data, the actual charging speed including the speed at which the battery is actually charged by the charger; and the vehicle control device using at least one of a display of the vehicle, an audio device of the vehicle, or any combination thereof to provide a user with information about the charging speed data, the charging speed data including at least one of the actual charging speed, the unique ID of the charger, or any combination thereof.

[0027] According to an embodiment, calculating by the vehicle control device an actual charging speed including a speed at which the battery is actually charged by the charger based on vehicle data may include: calculating by the vehicle control device at least one of a maximum value of the actual charging speed calculated for the cycle, a minimum value of the actual charging speed calculated for the cycle, or an average value of the actual charging speed calculated for the cycle, or any combination thereof, based on calculating the actual charging speed for each cycle between the moment when charging of the battery starts and the moment when charging of the battery ends.

[0028] According to an embodiment, calculating by the vehicle control device an actual charging speed including a speed at which the battery is actually charged by the charger based on vehicle data may include: calculating by the vehicle control device an average of the actual charging speeds over the entire charging time by dividing a value obtained by multiplying a difference between the SOC of the battery at the end of charging of the battery and the SOC of the battery at the start of charging of the battery by the entire charging time from the start of charging of the battery to the end of charging of the battery based on recognizing that the battery is charged when the engine of the vehicle is turned off, charging of the battery is abnormally terminated, or charging speed data is not transmitted to the server due to a communication failure, or any combination thereof.

[0029] According to an embodiment, the vehicle control method may further include: sending the charging speed data to a server by the vehicle control device; receiving the charging speed data from the vehicle by the server; and generating charger-specific charging speed data by the server, the charger-specific charging speed data including data matching the actual charging speed, the unique ID of the charger, the date of receiving the charging speed data, and the time of receiving the charging speed data.

[0030] According to an embodiment, generating, by the server, charger-specific charging speed data including data matching the actual charging speed, the unique ID of the charger, the date on which the charging speed data is received, and the time at which the charging speed data is received includes: matching, by the server, external factor information including at least one of season, weather, external temperature, vehicle type, vehicle age, or charger age, or any combination thereof, with the charger-specific charging speed data.

[0031] According to an embodiment, the vehicle control method may further include providing, by the server, information related to the charger-specific charging speed data to the user via at least one of a navigation system of the vehicle, a mobile application, or a webpage, or any combination thereof.

[0032] According to an embodiment, the vehicle control method may further include: receiving, by a server, charger output data from a charger, the charger output data including at least one of a unique ID of the charger, a maximum value of an output speed of power output by the charger during the entire charging time elapsed from the start of charging of the battery to the end of charging of the battery, a minimum value of an output speed of power output by the charger during the entire charging time, or an average value of the output speed of power output by the charger during the entire charging time, or any combination thereof.

[0033] According to an embodiment, the vehicle control method may further include comparing, by the server, the charger output data with the charging speed data to determine the performance of the charger. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings:

[0035] Figure 1 is a block diagram illustrating a vehicle control device according to an embodiment of the present disclosure;

[0036] Figure 2 is a block diagram of a server according to an embodiment of the present disclosure;

[0037] Figure 3 is a diagram illustrating an example in which a vehicle control device, a server, a charger, and a user transmit and receive data among each other according to an embodiment of the present disclosure;

[0038] Figure 4 is a diagram for describing an example in which a vehicle control device according to an embodiment of the present disclosure transmits data on a charging speed of each charger to a server;

[0039] Figure 5 is a diagram for describing an example in which the vehicle control device according to the embodiment of the present disclosure calculates a charging speed in a case where charging of a vehicle battery ends abnormally;

[0040] Figure 6 is a diagram for describing an example in which a server receives data on an output speed calculated for each charging session of the charger from a charger according to an embodiment of the present disclosure;

[0041] Figure 7 is a flowchart for describing a vehicle control device, a server, or a vehicle control method according to an embodiment of the present disclosure; and

[0042] Figure 8 is a diagram illustrating a computing system related to a vehicle control device, a server, or a vehicle control method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0043] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to the exemplary drawings. Furthermore, when reference numerals are assigned to components in each drawing, identical or equivalent components shown in other drawings will also be assigned the same reference numerals. Furthermore, when describing embodiments of the present disclosure, detailed descriptions of well-known features or functions will be omitted to avoid unnecessarily obscuring the main purpose of the present disclosure.

[0044] When describing components according to embodiments of the present disclosure, terms such as first, second, "A," "B," (a), (b), etc. may be used. These terms are intended only to distinguish one component from another and do not limit the nature, order, or sequence of the components. In addition, expressions such as "at least one of A, B, or C, or any combination thereof" may include A, B, or C, or a combination thereof, such as AB or ABC, etc.

[0045] Unless otherwise defined, all terms (including technical or scientific terms) used herein have the same meaning as commonly understood by those skilled in the art to which the present disclosure belongs. Terms defined in commonly used dictionaries should be interpreted as having the same meaning as the contextual meaning in the relevant art and should not be interpreted as having an ideal or overly formal meaning unless explicitly defined as having an ideal or overly formal meaning in this application.

[0046] In the following, reference will be made to Figures 1 to 8 The embodiments of the present disclosure are described in detail.

[0047] Figure 1 is a block diagram illustrating a vehicle control device according to an embodiment of the present disclosure.

[0048] Reference Figure 1 The vehicle control device 100 according to an embodiment of the present disclosure may be implemented inside a vehicle. In this case, the vehicle control device 100 may be integrated with an internal control unit of the vehicle, or may be implemented as a separate device and connected to the control unit of the vehicle via a separate connection device.

[0049] According to an embodiment, the vehicle control device 100 may include a first processor 110 and a first memory 120 . Figure 1 The configuration of the vehicle control device 100 shown in FIG is exemplary, and the embodiments of the present invention are not limited thereto. For example, the vehicle control device 100 may further include Figure 1 Parts not shown in FIG.

[0050] Depending on the embodiment, the first memory 120 may store commands or data. For example, the first memory 120 may include one instruction or two or more instructions that, when executed by the first processor 110, cause the vehicle control device 100 to perform various operations.

[0051] According to an embodiment, the first memory 120 may be implemented as a single chipset with the first processor 110 and may store various information associated with the vehicle control device 100. For example, the first memory 120 may store information about an operation history of the first processor 110.

[0052] Depending on the embodiment, the first memory 120 may include a non-volatile memory (read-only memory: ROM) and a volatile memory (random access memory: RAM). For example, the first memory 120 may store the time when battery charging starts, the battery's SOC (State of Charge) at the time of battery charging start, the battery's capacity, the time when battery charging ends, the battery's SOC at the time of battery charging end, and the like.

[0053] According to one embodiment, the first processor 110 may obtain a unique ID of the charger based on the vehicle using the charger to charge the battery.

[0054] According to an embodiment, the vehicle related to the vehicle control device 100 may include an electric vehicle. The electric vehicle may generate driving force by storing electric energy using a battery pack and supplying the electric energy to a motor.

[0055] According to an embodiment, the vehicle associated with vehicle control device 100 may include a hybrid vehicle. A hybrid vehicle may include an engine, an electric motor, an engine clutch that selectively connects the engine and the electric motor, a transmission, a differential gear device, or a battery. Furthermore, a hybrid vehicle may include a hybrid starter and generator (HSG) that starts the engine or generates power using the output of the engine. The HSG may be referred to as an integrated starter and generator (ISG).

[0056] According to an embodiment, the vehicle control device 100 can control the vehicle based on a control mode including any one of an electric vehicle mode using the power of an electric motor, an engine mode using the power of an engine, a hybrid electric vehicle mode using the power of the engine as a main power source and the power of the electric motor as an auxiliary power source, or a regenerative braking mode (in which, when the vehicle travels (or operates) by braking or kinetic energy, the battery is charged by recovering braking and kinetic energy through the drive of the motor), or any combination thereof.

[0057] A user can use a charger to charge the vehicle's battery. A charger is a machine used to charge the vehicle's battery and can be installed at a charging station or parking lot. For example, multiple chargers may be installed at a charging station, and a user can use any of the multiple chargers to charge the vehicle's battery.

[0058] According to an embodiment, the charger may be identified via a unique ID. For example, the unique ID of the charger may include a serial number consisting of numbers, letters, special symbols, etc.

[0059] According to an embodiment, if the battery of the vehicle starts to be charged by the charger, the first processor 110 may obtain the unique ID of the charger. The first processor 110 can receive data about the unique ID of the charger from the charger in a wired or wireless manner.

[0060] According to an embodiment, the first processor 110 may obtain the unique ID of the charger from map data for guiding a path of the vehicle.

[0061] For example, the first processor 110 may receive map data or navigation information from an external server. The map data may include various geographic information used in vehicle navigation systems or autonomous driving technologies. For example, the map data may include at least one of road network information, traffic information, terrain information, surrounding facility information, lane instructions, intersection information, or any combination thereof. Specifically, the map data may include information about locations useful to the user, such as gas stations, charging stations, chargers, residences, major tourist attractions, and restaurants.

[0062] For example, the first processor 110 may obtain the unique ID of the charger from information about the charging station or charger included in the map data.

[0063] According to an embodiment, the first processor 110 may identify vehicle data including the time when charging of the battery starts, the SOC (state of charge) of the battery when charging of the battery starts, the capacity of the battery, the time when charging of the battery ends, or the SOC of the battery when charging of the battery ends, or any combination thereof.

[0064] The time to start charging the battery may include the date and time when charging the battery of the vehicle starts, and the time to end charging the battery may include the date and time when charging the battery of the vehicle ends.

[0065] The capacity of a battery can refer to the amount of electrical energy available until the battery is discharged and no current flows. For example, the capacity of a battery can be expressed in units such as kWh (kilowatt-hours) or GWh (gigawatt-hours). As a specific example, if the battery capacity is 80 kWh, then 80 kW of power can be consumed in one hour.

[0066] The battery's state of charge (SOC) may refer to the remaining capacity of a vehicle's battery. For example, the battery's SOC (State of Charge) may be expressed as a percentage, obtained by dividing the battery's available capacity by the battery's total capacity. For example, a fully charged battery's SOC may be expressed as 100%.

[0067] The SOC (State of Charge) of the battery at the start of charging of the battery may indicate the remaining capacity of the battery at the start of charging of the vehicle, and the SOC (State of Charge) of the battery at the end of charging of the battery may indicate the remaining capacity of the battery at the end of charging of the vehicle.

[0068] Depending on the embodiment, the first processor 110 may identify data regarding the time when battery charging starts, the battery's SOC (State of Charge) at the start of charging, the battery's capacity, the time when battery charging ends, or the battery's SOC at the end of battery charging as "vehicle data." For example, the first processor 110 may store the identified vehicle data in the first memory 120.

[0069] According to an embodiment, the first processor 110 may calculate an actual charging speed including a speed at which the battery is actually charged by the charger based on the vehicle data. For example, the first processor 110 may calculate a speed at which the battery of the vehicle is actually charged, regardless of a speed at which the charger outputs power.

[0070] According to an embodiment, the first processor 110 may identify information about charging speed data including at least one of an actual charging speed, a unique ID of a charger, or any combination thereof. In addition, the first processor 110 may provide the user with information about the charging speed data using at least one of a display of the vehicle, an audio device of the vehicle, or any combination thereof.

[0071] The first processor 110 may display information about the charging speed data on the display of the vehicle. For example, the first processor 110 may display the actual charging speed of the battery of the vehicle or the current SOC of the battery on the display of the vehicle.

[0072] As another example, the first processor 110 may display on the vehicle's display both the speed at which the charger outputs power and the speed at which the vehicle's battery is actually charged. Thus, the user can determine the performance and charging efficiency of the charger.

[0073] In addition, the first processor 110 can notify the user of information about the charging speed data via an audio device. For example, at each preset battery SOC or preset charging time, the user can be notified by voice of the actual charging speed of the vehicle's battery or the current SOC of the battery.

[0074] According to an embodiment, the first processor 110 may calculate an actual charging speed for each cycle between when charging of the battery starts and when charging of the battery ends.

[0075] Depending on the implementation, the cycle may include a preset time interval. Specifically, the cycle may be set to identify a change in charging speed. The cycle may be set to reflect a user's pattern. Alternatively, the cycle may be set to a time interval directly input by the user. For example, the cycle may be set in minutes. As a specific example, the cycle may be set to 1 minute.

[0076] According to an embodiment, the first processor 110 may continuously calculate the actual charging speed for each cycle during a time period from when charging of the battery starts to when charging of the battery ends.

[0077] For example, when the battery of the vehicle is being charged, the first processor 110 may continuously calculate the actual charging speed of each cycle. As a specific example, if the battery of the vehicle has been charged for 30 minutes and the cycle is 1 minute, the actual charging speed may be calculated 29 times.

[0078] According to an embodiment, the first processor 110 may calculate a maximum value among the actual charging speeds calculated for the cycles, a minimum value among the actual charging speeds calculated for the cycles, and an average value of the actual charging speeds calculated for the cycles.

[0079] Depending on the embodiment, while the vehicle's battery is being charged, the actual charging speed may continuously vary. For example, the first processor 110 may identify the actual charging speeds that vary while the vehicle's battery is being charged, and calculate the fastest of the actual charging speeds as a maximum value. Furthermore, the first processor 110 may identify the slowest of the actual charging speeds as a minimum value.

[0080] According to an embodiment, the first processor 110 may identify actual charging speeds that vary while the vehicle battery is being charged, and calculate an average of the identified actual charging speeds. For example, if the actual charging speeds calculated for cycles while the vehicle battery is being charged are 30 kW, 35 kW, 40 kW, and 55 kW, the average of the actual charging speeds may be calculated to be 40 kW.

[0081] According to an embodiment, the first processor 110 may provide the user with a maximum value of the actual charging speeds calculated for the cycles, a minimum value of the actual charging speeds calculated for the cycles, and an average value of the actual charging speeds calculated for the cycles.

[0082] According to an embodiment, if the first processor 110 fails to calculate the actual charging speed for each cycle, if the battery is charged while the engine of the vehicle is turned off, if charging of the battery ends abnormally, or if the charging speed data is not transmitted to the server due to a communication failure, the first processor 110 may calculate an average of the actual charging speeds for the entire charging time.

[0083] For example, the first processor 110 may calculate an average of the actual charging speed over the entire charging time by dividing a value obtained by multiplying a difference between the SOC of the battery at the end of charging of the battery and the SOC of the battery at the start of charging of the battery by the capacity of the battery by the entire charging time elapsed from the start of charging of the battery to the end of charging of the battery.

[0084] As a specific example, if the SOC of the battery when charging starts is 30%, the SOC of the battery when charging ends is 100%, the total charging time from the start of charging of the battery to the end of charging of the battery is 10 hours, and the capacity of the battery of the vehicle is 60 kWh, the first processor 110 can calculate the average of the actual charging speeds as follows.

[0085] First processor 110 may calculate the difference between the battery SOC (100%) at the end of charging and the battery SOC (30%) at the start of charging as 70%, calculate the vehicle battery capacity of "42 kWh" by multiplying "0.7" (corresponding to 70%) by "60 kWh", and calculate the total charging time of "4.2 kWh" by dividing "42 kWh" by "10 hours". Therefore, first processor 110 may calculate "4.2 kWh" as the average of the actual charging speeds over the entire charging time. That is, in the above example, the average of the actual charging speeds over the entire charging time may also be calculated as 4.2 kWh.

[0086] For example, due to internal or external factors of the vehicle control device, the first processor 110 may not be able to identify the actual charging speed calculated for each cycle. In this case, the first processor 110 may calculate the average of the actual charging speeds of the entire charging time as described above and identify the average as the actual charging speed.

[0087] For example, if the battery is charged while the vehicle's engine is turned off, the first processor 110 may not be able to calculate the charging speed for each cycle. In this case, the first processor 110 may calculate the average of the actual charging speeds for the entire charging time as described above and identify the average as the actual charging speed.

[0088] For example, if the battery charge ends abnormally, the charging speed may not be calculated for each cycle, or the collection of the calculated charging speed may be unstable. In this case, the first processor 110 can calculate the average of the actual charging speeds of the entire charging time as described above and identify the average as the actual charging speed.

[0089] For example, due to a communication failure, the first processor 110 may be unable to transmit the charging speed data to the server. In this case, the first processor 110 may calculate the average of the actual charging speeds for the entire charging time as described above and identify the average as the actual charging speed. In addition, the first processor 110 may transmit the calculated average of the actual charging speeds for the entire charging time to the server.

[0090] According to an embodiment, the first processor 110 may transmit the charging speed data to the server. As described above, the charging speed data may include the actual charging speed and the unique ID of the charger.

[0091] According to an embodiment, the first processor 110 may transmit or receive data to or from the server via a communication circuit. For example, the vehicle and the server may each include a communication circuit, and the vehicle and the server may exchange data with each other via their respective communication circuits.

[0092] For example, the communication circuitry may include circuitry for wireless internet access. For example, the communication circuitry may connect to a wireless communication network of a wireless communication provider and utilize wireless communications such as 3G, LTE (Long Term Evolution), LTE-A (Long Term Evolution Advanced), or 5G (fifth generation mobile communications). Furthermore, the communication circuitry may be mounted on the telematics unit and may include an RF (radio frequency) antenna and a communication control module.

[0093] According to an embodiment, if the server receives the charging speed data from the first processor 110, the server may identify the date and time at which the server received the charging speed data. For example, the server may match the charger-specific charging speed data with the date and time at which the charging speed data was received, and store the charger-specific charging speed data associated with the date and time at which the charging speed data was received in a database.

[0094] For another example, the first processor 110 may transmit the charging speed data to the server while also transmitting information about the vehicle. The information about the vehicle may include the type of vehicle, the age of the vehicle, etc. For example, the server may match the actual charging speed included in the charging speed data with the information about the vehicle, and store the actual charging speed included in the charging speed data in a database in association with the information about the vehicle. In other words, the actual charging speed may be different depending on the type of vehicle or the age of the vehicle, even if the actual charging speed is calculated from the same charger. Therefore, the server may store the charging speed data containing the actual charging speed that matches the information about the vehicle in the database.

[0095] According to one embodiment, the server may identify data matching the actual charging speed, the unique ID of the charger, the date the server receives the charging speed data, and the time at which the server receives the charging speed data as charger-specific charging speed data.

[0096] For example, the server can collect charging speed data for each charger by matching the charging speed data received from the vehicle with the unique ID of the charger used by the vehicle. The server can identify the data collected per charger as charger-specific charging speed data and store it in a database.

[0097] According to an embodiment, the first processor 110 may receive charger-specific charging speed data including data matching the actual charging speed, the unique ID of the charger, the date on which the server receives the charging speed data, and the time at which the server receives the charging speed data.

[0098] According to an embodiment, the first processor 110 may provide the user with information regarding the charger-specific charging speed data received from the server using at least one of a display of the vehicle, or an audio device of the vehicle, or any combination thereof.

[0099] First processor 110 can provide the user with information regarding charging speed data for chargers located along the vehicle's route. For example, first processor 110 can display information regarding the actual charging speed of the charger on an indicator associated with the charger located along the route displayed on the display. Furthermore, if the vehicle approaches a charger located along the route within a predetermined distance, first processor 110 can provide information regarding the actual charging speed of the charger via an audio device.

[0100] According to an embodiment, a user may select a charger that meets the user's needs in consideration of a speed at which a vehicle is actually charged by using information on charger-specific charging speed data from the vehicle.

[0101] Figure 2 is a block diagram of a server according to an embodiment of the present disclosure.

[0102] refer to Figure 2 , the server 200 according to an embodiment of the present disclosure may include a second processor 210 and a second memory 220 . Figure 2 The configuration of the server 200 shown in FIG is illustrative, and the embodiments of the present disclosure are not limited thereto. For example, the server 200 may further include Figure 2 Components not shown.

[0103] Depending on the embodiment, the second memory 220 may store commands or data. For example, the second memory 220 may include one instruction or two or more instructions that, when executed by the second processor 210, cause the server 200 to perform various operations. For example, the second memory 220 may be used as a server database.

[0104] According to an embodiment, the second memory 220 may be implemented as a single chipset with the second processor 210 and may store various information associated with the server 200. For example, the second memory 220 may store information about an operation history of the second processor 210.

[0105] According to an embodiment, the second memory 220 may include a non-volatile memory (read only memory: ROM) and a volatile memory (random access memory: RAM). For example, the actual charging speed, the unique ID of the charger, etc. may be stored in the second memory 220.

[0106] Hereinafter, according to the embodiment Figure 2 The charging speed data of the server 200 and the charger-specific charging speed data may correspond to Figure 1 The charging speed data of the vehicle control device 100 and the charger-specific charging speed data described in .

[0107] According to an embodiment, the second processor 210 may receive charging speed data from the vehicle, which includes at least one of an actual charging speed at which the battery of the vehicle is actually charged by the charger, or a unique ID of the charger, or any combination thereof.

[0108] According to an embodiment, the second processor 210 may generate charger-specific charging speed data including data matching a unique ID of the charger, a date on which the charging speed data is received, and a time at which the charging speed data is received.

[0109] For example, if the second processor 210 receives charging speed data from a vehicle, the second processor 210 may identify the date when the second processor 210 receives the charging speed data and the time when the second processor 210 receives the charging speed data. The second processor 210 may generate charger-specific charging speed data that matches the date and time when the charging speed data is received, and may store the charger-specific charging speed data in a database.

[0110] According to an embodiment, the second processor 210 may match external factor information including at least one of season, weather, outside temperature, vehicle type, vehicle age, or charger age, or any combination thereof, with the charger-specific charging speed data.

[0111] Depending on the embodiment, the actual charging speed included in the charger-specific charging speed data may be affected by season, weather, outside temperature, vehicle type, vehicle age, or charger age.

[0112] For example, if the temperature is low, the activity of lithium ions in the electrolyte of the vehicle's battery decreases, which can reduce the charging speed. Therefore, if the battery is charged in cold weather, the actual charging speed of the vehicle's battery may be slower than when the battery is charged in hot weather. Similarly, in the winter, if the temperature is low, the actual charging speed of the battery may be slower than the actual charging speed in the summer when the temperature is high.

[0113] For example, the speed at which a vehicle's battery can actually charge may vary depending on the vehicle's type or age. The acceptable charging speed can vary depending on the vehicle's type. Specifically, even when charging the battery using the same charger, the actual charging speed may differ between vehicles capable of fast charging and those that are not. Furthermore, even when the vehicles are of the same type, recent model-year vehicles may be capable of fast charging, while older model-year vehicles may not be able to charge quickly. Therefore, even when charging the battery using the same charger, the actual charging speed may vary depending on the vehicle's age.

[0114] For example, the actual charging speed of a vehicle's battery may vary depending on the age of the charger. The older the charger, the lower the output speed due to the aging of the charger. Therefore, if the battery is charged by the same charger, the actual charging speed of the vehicle's battery may be slower if the battery is charged by an older model charger.

[0115] According to an embodiment, the second processor 210 may match the external factor information (season, weather, external temperature, vehicle type, vehicle age, charger age) with the charger-specific charging speed data and store it in a database.

[0116] According to an embodiment, the second processor 210 may provide the user with information related to charger-specific charging speed data matched with the above-mentioned external factor information (season, weather, outside temperature, vehicle type, vehicle age, charger age).

[0117] According to an embodiment, the second processor 210 may provide the user with information related to the charger-specific charging speed data via at least one of the vehicle's navigation system, a mobile application, or a webpage, or any combination thereof.

[0118] For example, the second processor 210 may provide the user with information corresponding to the type of vehicle owned by the user, the age of the vehicle, or the season, weather, and external temperature when the user identifies the information related to the charging speed data of each charger, among the information related to the charger-specific charging speed data.

[0119] For example, the second processor 210 may display information related to the charger-specific charging speed data on the vehicle's navigation system. Furthermore, the second processor 210 may provide information related to the charger-specific charging speed data to a mobile application or a webpage. Thus, the user can identify the charging speed of each charger through the vehicle's navigation system, mobile application, or webpage.

[0120] According to an embodiment, the second processor 210 may receive charging speed data from the vehicle, the charging speed data including data regarding an actual charging speed calculated for each cycle.

[0121] For example, the charging speed data received by the second processor 210 from the vehicle may include a maximum value of the actual charging speeds calculated for the cycle, a minimum value of the actual charging speeds calculated for the cycle, an average value of the actual charging speeds calculated for the cycle, and an average value of the actual charging speeds for the entire charging time elapsed from the start time of charging of the battery to the end time of charging of the battery.

[0122] According to an embodiment, the charging speed data received by the second processor 210 from the vehicle can be understood as the charging speed data received by the second processor 210 from the vehicle. Figure 1 The first processor 110 of the vehicle control device 100 described above calculates the charging speed data.

[0123] For example, the average of the actual charging speed for the entire charging time may be calculated as a value obtained by multiplying the difference between the SOC of the battery when charging of the battery ends and the SOC of the battery when charging starts by the capacity of the battery and dividing it by the entire charging time.

[0124] For example, if the second processor 210 fails to calculate the actual charging speed for each cycle, if the battery is charged while the vehicle engine is turned off, if charging of the battery is abnormally terminated, or if charging speed data is not transmitted to the server due to a communication failure, the second processor 210 may receive an average of the actual charging speed over the entire charging time from the vehicle.

[0125] According to an embodiment, the second processor 210 may identify the entire charging time taken from the charging start time of the battery to the charging end time of the battery.

[0126] According to an embodiment, the second processor 210 may receive data related to the power output by the charger from the charger. For example, each of the charger and the server may include a communication circuit, and the charger may receive data from the server via the communication circuit.

[0127] According to an embodiment, the second processor 210 may receive charger output data from the charger, the charger output data including at least one of a unique ID of the charger, a maximum value among output speeds at which the charger outputs power during the entire charging time, a minimum value among output speeds at which the charger outputs power during the entire charging time, or an average value of output speeds at which the charger outputs power during the entire charging time, or any combination thereof.

[0128] For example, the output speed at which the charger outputs power may be measured without regard to the speed at which the vehicle's battery is actually charged via the charger. Therefore, the output speed received from the charger and the speed at which the vehicle's battery is actually charged may be different.

[0129] According to an embodiment, the second processor 210 may match the output speed received from the charger in the charger output data with the unique ID of the charger, and store the output speed received from the charger in association with the unique ID of the charger.

[0130] According to an embodiment, the second processor 210 may match the charger output data received from the charger with the charging speed data received from the vehicle. For example, the second processor 210 may match the charger output data received from the charger with the charging speed data received from the vehicle based on the date and time when the vehicle's battery is charged.

[0131] Depending on the embodiment, the second processor 210 may determine the performance of the charger by comparing the charger output data with the charging speed data. For example, if the difference between the output speed included in the charger output data and the actual charging speed of the battery included in the charging speed data exceeds a threshold, it may be determined that the performance of the charger has deteriorated. Furthermore, the second processor 210 may determine when to replace the charger based on the extent to which the performance of the charger has deteriorated.

[0132] According to an embodiment, the second processor 210 may provide the user with information related to the performance of the charger.

[0133] According to an embodiment, the user may select a charger that meets the user's needs using information regarding charger-specific charging speed data provided by the server 200 via the vehicle's navigation system, a mobile application, or a webpage.

[0134] Figure 3 is a diagram illustrating an example in which a vehicle control device, a server, a charger, and a user transmit and receive data among each other according to an embodiment of the present disclosure.

[0135] According to an embodiment, a user 340 may charge a battery of a vehicle 310 using a charger 330. The charger 330 may provide electrical energy to the battery of the vehicle 310. The battery of the vehicle 310 may be charged by the charger 330.

[0136] Depending on the embodiment, vehicle 310 may obtain a charger ID. The charger ID may include a unique ID that identifies charger 330. For example, vehicle 310 may obtain the charger ID from map data. In another example, vehicle 310 may receive data associated with the charger ID from charger 330.

[0137] According to an embodiment, the vehicle 310 may calculate the speed (actual charging speed) at which the charger 330 actually charges the battery. The vehicle 310 may transmit charging speed data 311 including the actual charging speed and the charger ID to the server 320 .

[0138] According to an embodiment, the server 320 may receive charging speed data 311 including at least one of an actual charging speed or a charger ID or any combination thereof from the vehicle 310 .

[0139] According to an embodiment, the server 320 may generate the charger specific charging speed data 321 including data matching the charger ID, the date on which the charging speed data 311 is received, and the time at which the charging speed data 311 is received.

[0140] In addition, according to an embodiment, the server 320 may match external factor information to the charger-specific charging speed data 321. The external factor information may include season, weather, outside temperature, type of vehicle, age of the vehicle, or age of the charger.

[0141] According to an embodiment, the server 320 may receive charger output data 331 related to power output by the charger 330 from the charger 330 .

[0142] For example, the charger output data 331 may include the ID of the charger, the maximum value of the output speed of the charger outputting power during the entire charging time, the minimum value of the output speed of the charger outputting power during the entire charging time, and the average value of the output speed of the charger outputting power during the entire charging time.

[0143] According to an embodiment, the server 320 may store the output speed of the charger of the charger output data 331 together with the charger ID of the corresponding charger 330 , and store the output speed of the charger in a database in association with the charger ID of the corresponding charger 330 .

[0144] According to an embodiment, the server 320 may provide information on the charger-specific charging speed data 321 to the user 340 .

[0145] For example, server 320 may provide information regarding charger-specific charging speed data 321 to user 340 via at least one of a navigation system of vehicle 310 , a mobile application, or a webpage, or any combination thereof.

[0146] refer to Figure 3 According to an embodiment, user 340 may be provided with information regarding the actual charging speed of each charger, allowing user 340 to more accurately estimate the time required to charge the battery of vehicle 310 .

[0147] Figure 4 is a diagram for describing an example in which the vehicle control device according to the embodiment of the present disclosure transmits data on the charging speed of each charger to a server.

[0148] According to an embodiment, the first vehicle 411 may charge the battery of the vehicle using a charger “M” 431 , and the second vehicle 412 may charge the battery of the vehicle using a charger “N” 432 .

[0149] According to an embodiment, first vehicle 411 may identify charging speed 441 that changes over time. For example, the actual charging speed of the battery of first vehicle 411 may gradually increase from the time charging begins. Alternatively, the actual charging speed of the battery of first vehicle 411 may gradually decrease as charging nears the end of charging.

[0150] Depending on the embodiment, the first vehicle 411 may calculate charging speed data 442 associated with the actual charging speed of the battery (actual charging speed). For example, the charging speed data 442 may include the unique ID of the charger "M" 431, the maximum actual charging speed, the minimum actual charging speed, or the average actual charging speed.

[0151] For example, the first vehicle 411 may calculate the actual charging speed on a cycle-by-cycle basis. The first vehicle 411 may recognize the actual charging speed that varies when the battery of the vehicle is charged, and may calculate the maximum actual charging speed, the minimum actual charging speed, or the average actual charging speed based on the corresponding actual charging speed.

[0152] According to an embodiment, the first vehicle 411 may transmit the calculated charging speed data 442 to the server 420 .

[0153] Depending on the embodiment, second vehicle 412 may identify a charging speed 451 that changes over time. For example, the actual charging speed of the battery of second vehicle 412 may gradually increase over time from the start of charging. Alternatively, the actual charging speed of the battery of second vehicle 412 may gradually decrease as charging approaches the end of charging.

[0154] Depending on the embodiment, the second vehicle 412 may calculate charging speed data 452 associated with the actual charging speed of the battery (actual charging speed). For example, the charging speed data 452 may include the unique ID of the charger "N" 432, the maximum actual charging speed, the minimum actual charging speed, or the average actual charging speed.

[0155] For example, the second vehicle 412 may calculate the actual charging speed for each cycle. The second vehicle 412 may recognize that the actual charging speed varies when the battery of the vehicle is charged, and may calculate a maximum value, a minimum value, or an average value of the actual charging speed based on the corresponding actual charging speed.

[0156] According to an embodiment, the second vehicle 412 may transmit the calculated charging speed data 442 to the server 420 .

[0157] According to an embodiment, server 420 may distinguish between charging speed data 442 associated with charger "M" 431 received from first vehicle 411 and charging speed data 452 associated with charger "N" 432 received from second vehicle 412, and store them in a database. For example, charger-specific charging speed data 442 associated with charger "M" 431 and charging speed data 452 associated with charger "N" 432 may be used to collect charger-specific charging speed data.

[0158] If the first vehicle 411 and the second vehicle 412 are the same vehicle as an embodiment, then Figure 4 In other words, if the same vehicle charges the battery using a charger “M” 431 and a charger “N” 432 that are different from each other, the above example may be applicable.

[0159] Figure 5 is a diagram for describing an example in which the vehicle control device according to the embodiment of the present disclosure calculates a charging speed when charging of a battery of a vehicle ends abnormally.

[0160] According to the embodiment Figure 5 An example of a vehicle 510 charging a battery of the vehicle 510 using a charger "L" 530 may be shown. The vehicle 510 may calculate the actual charging speed of the battery through a vehicle control device.

[0161] According to the embodiment Figure 5 An example of a charging speed graph 551 is included if charging of the battery ends abnormally. Figure 5 An example of table 552 is included, which shows information for calculating the average of the actual charging speed over the entire charging time in the case of abnormal end of charging.

[0162] According to the embodiment, Figure 5 The charging speed graph 551 included in may indicate a time point “P” at which charging of the battery of the vehicle 510 is started, a time point “Q” at which charging of the battery of the vehicle 510 is abnormally ended, and a time point “R” at which charging of the battery of the vehicle 510 is ended.

[0163] For example, reference Figure 5 In the charging speed graph 551 included in the vehicle 510, the charging speed may not be calculated after the charging of the battery of the vehicle 510 has stopped. In this case, the vehicle control device may not be able to calculate the actual charging speed of each cycle.

[0164] According to an embodiment, if the vehicle control device fails to calculate the actual charging speed for each cycle, the vehicle control device may identify an average value of the actual charging speeds for the entire charging time as the actual charging speed.

[0165] For example, the vehicle control device can calculate the average of the actual charging speed during the entire charging time by dividing the value obtained by multiplying the difference between the SOC of the battery at the end of charging of the battery and the SOC of the battery at the start of charging of the battery by the capacity of the battery by the entire charging time elapsed from the start of charging of the battery to the end of charging of the battery.

[0166] As a specific example, refer to Figure 5 According to Table 552 included in the table, if the SOC of the battery at the start of battery charging is 50%, the SOC of the battery at the end of battery charging is 80%, the total charging time consumed from the start of battery charging to the end of battery charging is 0.5 hours, and the capacity of the battery of the vehicle is 60 kWh, the vehicle control device can calculate the average of the actual charging speeds as follows.

[0167] The vehicle control device of vehicle 510 may calculate the difference between the SOC of the battery at the end of battery charging (80%) and the SOC of the battery at the start of battery charging (50%) as 30%, calculate "18 kWh" by multiplying "0.3" corresponding to 30% by the capacity of the battery of the vehicle "60 kWh", and calculate "36 kWh" by dividing "18 kWh" by the entire charging time "0.5 hours".

[0168] Therefore, the vehicle control device can calculate "36 kWh" as the average of the actual charging speed during the entire charging time. Figure 5 In the example shown, the average actual charging rate over the entire charging time can be calculated to be 36 kWh.

[0169] According to an embodiment, the vehicle control device may transmit charging speed data including the calculated average of the actual charging speeds to the server. If the charging speed data is received, the server may collect the charging speed data for each charging station and store the charging speed data in a database.

[0170] refer to Figure 5 According to an embodiment, if the vehicle control device fails to calculate the actual charging speed calculated for each cycle due to internal factors or external factors, the vehicle control device may calculate an average of the actual charging speeds of the entire charging time as the actual charging speed.

[0171] Figure 6 is a diagram for describing an example in which a server receives data on an output speed calculated for each charging session of the charger from a charger according to an embodiment of the present disclosure.

[0172] According to the embodiment, Figure 6An embodiment may be shown where the vehicle is charging its battery using charger “L” 630 .

[0173] According to an embodiment, the charger "L" 630 may distinguish data generated from the start time to the end time of charging of the battery in units of charging sessions. Figure 6 As shown, if the battery is charged three times, the charger “L” 630 may distinguish the charging sessions into a first charging session 640 , a second charging session 650 , and a third charging session 660 .

[0174] According to the embodiment, Figure 6 A first charging session 640, a second charging session 650, and a third charging session 660 are shown for charger "L" 630. For example, first charging session 640, second charging session 650, and third charging session 660 may each be used to charge the battery of a different vehicle, or may be used to charge the battery of the same vehicle three times.

[0175] According to an embodiment, the charger 'L' 630 may identify a speed (output speed) at which the charger 'L' 630 outputs power to the battery of the vehicle. The charger 'L' 630 may identify the output speed for each charging session.

[0176] Figure 6 An output speed graph 641 for a first charging session 640, an output speed graph 651 for a second charging session 650, and an output speed graph 661 for a third charging session 660 are shown according to one embodiment. Figure 6 , even if the battery of the same vehicle is charged three times, the output speed may be calculated differently.

[0177] Depending on the embodiment, charger "L" 630 may calculate output data for each charging session. For example, the maximum output speed, the minimum output speed, or the average output speed may be calculated. Thus, the maximum output speed, the minimum output speed, or the average output speed may be calculated differently for each charging session.

[0178] Depending on the embodiment, the output data 642 of the first charging session, the output data 652 of the second charging session, and the output data 662 of the third charging session may include different data.

[0179] For example, the maximum output speed of the first charging session 640 may be calculated as 50 kW, and the average output speed of the first charging session 640 may be calculated as 39.83 kW. The maximum output speed of the second charging session 650 may be 35 kW, and the average output speed of the second charging session 650 may be 27.33 kW. The maximum output speed of the third charging session 660 may be 50 kW, and the average output speed of the third charging session 660 may be 36 kW.

[0180] Depending on the embodiment, charger “L” 630 may transmit at least one of output data 642 of the first charging session, output data 652 of the second charging session, or output data 662 of the third charging session, or any combination thereof, to server 620 .

[0181] According to an embodiment, the server 620 may store the output data 642 of the first charging session, the output data 652 of the second charging session, or the output data 662 of the third charging session in a database.

[0182] According to an embodiment, the server 620 may match the charging speed data received from the vehicle with the charger output data including the output data 642 of the first charging session, the output data 652 of the second charging session, or the output data 662 of the third charging session.

[0183] For example, the server 620 may compare the charger output data with the charging speed data to determine the performance of the charger. For example, if the difference between the output speed included in the charger output data and the actual charging speed of the battery included in the charging speed data exceeds a threshold, it may be determined that the performance of the charger has deteriorated.

[0184] Figure 7 It is a flowchart for describing a vehicle control device, a server, or a vehicle control method according to an embodiment of the present disclosure.

[0185] In the following, Figure 1 The vehicle control device 100 or Figure 2 The server 200 can execute Figure 7 In addition, Figure 7 In the description of the vehicle control device, the operation described as being performed by the vehicle control device can be understood as being performed by Figure 1 The first processor 110 of the vehicle control device 100 is controlled, and the operation described as being performed by the server can be understood as being performed by Figure 2 The second processor 210 of the server 200 is controlled.

[0186] According to an embodiment, the vehicle control device may recognize that the vehicle is charging a battery using a charger ( S710 ).

[0187] According to an embodiment, the vehicle control device may identify vehicle data (S720). The vehicle data may include the time when battery charging starts, the SOC (State of Charge) of the battery when charging starts, the capacity of the battery, the time when battery charging ends, the SOC of the battery when charging ends, or any combination thereof.

[0188] According to an embodiment, the vehicle control device may calculate an actual charging speed including a speed at which a battery is actually charged by a charger based on the vehicle data ( S730 ).

[0189] According to an embodiment, the vehicle control device may provide the user with information about charging speed data, including at least one of the actual charging speed or the unique ID of the charger, or any combination thereof, using at least one of a display of the vehicle or an audio device of the vehicle, or any combination thereof ( S740 ).

[0190] According to an embodiment, the vehicle control device may transmit the charging speed data to the server.

[0191] According to an embodiment, the server may receive the charging speed data transmitted by the vehicle and generate charger-specific charging speed data. According to an embodiment, the charger-specific charging speed data may include data matching the actual charging speed, the unique ID of the charger, the date the charging speed data was received, and the time the charging speed data was received.

[0192] Depending on the embodiment, charger output data may be received from the charger. For example, charger output data 331 may include at least one of the following: a unique ID of the charger, a maximum value of the output speed of the charger output power during the entire charging time from the start to the end of charging the battery, a minimum value of the output speed of the charger output power during the entire charging time, an average value of the output speed of the charger output power during the entire charging time, or any combination thereof.

[0193] According to an embodiment, the server may determine the performance of the charger by comparing the charger output data and the charging speed data.

[0194] According to an embodiment, the server may provide information related to the charger-specific charging speed data to the user via at least one of a navigation system, a vehicle, a mobile application, or a web page, or any combination thereof.

[0195] Figure 8 is a diagram illustrating a computing system related to a vehicle control device, a server, or a vehicle control method according to an embodiment of the present disclosure.

[0196] refer to Figure 8 , the computing system 1000 may include at least one processor 1100 , a memory 1300 , a user interface input device 1400 , a user interface output device 1500 , a storage device 1600 , and a network interface 1700 connected to each other via a bus 1200 .

[0197] The processor 1100 may be a central processing unit (CPU) or a semiconductor device that processes instructions stored in the memory 1300 and / or the storage device 1600. The memory 1300 and the storage device 1600 may include various types of volatile or non-volatile storage media. For example, the memory 1300 may include a ROM (read-only memory) 1310 and a RAM (random access memory) 1320.

[0198] Thus, the operations of the methods or algorithms described in conjunction with the embodiments disclosed herein may be directly embodied in hardware or software modules, or a combination thereof, executed by the processor 1100. The software modules may reside on a storage medium (i.e., the memory 1300 and / or the storage device 1600) such as RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, removable disks, and CD-ROMs.

[0199] An exemplary storage medium may be coupled to processor 1100, and processor 1100 may read information from the storage medium and may record information in the storage medium. Alternatively, the storage medium may be integrated with processor 1100. The processor and storage medium may reside in an application-specific integrated circuit (ASIC). The ASIC may reside in a user terminal. In another embodiment, the processor and storage medium may reside in the user terminal as separate components.

[0200] The above description is merely an illustration of the technical concept of the present disclosure, and those skilled in the art to which the present disclosure pertains may make various modifications and changes without departing from the essential characteristics of the present disclosure.

[0201] Therefore, the embodiments disclosed in this disclosure are not intended to limit the technical concept of the present disclosure, but are used to describe the present disclosure, and the scope of the technical concept of the present disclosure is not limited by the embodiments. The scope of protection of the present disclosure should be interpreted by the appended claims, and all technical concepts within the scope equivalent to the claims should be interpreted as included within the scope of the present disclosure.

[0202] The present technology may collect information about the speed at which the vehicle battery is actually charged by each charger, and provide the user with information about the accurate charging speed of each charger based on the collected information.

[0203] The present technology may allow a user to more accurately estimate the time required to charge a vehicle battery using a corresponding charger by providing the user with information about how fast the vehicle battery is actually charged for each charger.

[0204] The present technology can collect information about the speed at which each charger actually charges the vehicle's battery, and provide the user with information reflecting changes in charging speed according to the age of the charger, season, weather, etc.

[0205] The present technology can determine the performance of the chargers by continuously updating information about how fast the vehicle's battery is actually charged for each charger.

[0206] Although the present disclosure has been described above with reference to exemplary embodiments and the accompanying drawings, the present disclosure is not limited thereto, but various modifications and changes may be made by those skilled in the art to which the present disclosure pertains without departing from the spirit and scope of the present disclosure as claimed in the appended claims.

Claims

1. A vehicle control device, comprising: Memory, which stores computer-executable instructions; as well as at least one processor configured to access the memory and execute the instructions, wherein the instructions include: Based on the vehicle using the charger to charge the battery, obtaining a unique identifier of the charger; identifying vehicle data, the vehicle data comprising at least one of the following: a time when charging of the battery begins, a state of charge of the battery when charging of the battery begins, a capacity of the battery, a time when charging of the battery ends, and a state of charge of the battery when charging of the battery ends; calculating an actual charging speed based on the vehicle data, wherein the actual charging speed includes a speed at which the battery is actually charged by the charger; and Information regarding charging speed data including at least one of the actual charging speed or the unique identifier of the charger is provided to a user using at least one of a display of the vehicle or an audio device of the vehicle.

2. The vehicle control device according to claim 1, wherein: The instructions include: calculating, based on calculating an actual charging speed for each cycle between a charging start time and a charging end time of the battery, at least one of the following: a maximum value of the actual charging speed calculated for the cycle, a minimum value of the actual charging speed calculated for the cycle, and an average value of the actual charging speed calculated for the cycle.

3. The vehicle control device according to claim 1, wherein: The instructions include: based on identifying that the actual charging speed of each cycle is not calculated, the battery is charged when the engine of the vehicle is turned off, the charging of the battery is abnormally ended, the charging speed data is not transmitted to the server due to a communication failure, or any combination of the above, calculating the average of the actual charging speed during the entire charging time by multiplying the difference between the state of charge of the battery at the end of charging of the battery and the state of charge of the battery at the start of charging of the battery by the capacity of the battery and dividing the value obtained by the entire charging time spent from the start of charging of the battery to the end of charging of the battery.

4. The vehicle control device according to claim 1, wherein: The instructions include obtaining the unique identifier of the charger from map data of a route used to guide the vehicle.

5. The vehicle control device according to claim 1, wherein: The instructions include: Sending the charging speed data to a server; receiving charging speed data for each charger, the charging speed data including data matching the actual charging speed, a unique identifier of the charger, a date when the server receives the charging speed data, and a time when the server receives the charging speed data; and Information regarding charger-specific charging speed data is provided to the user using at least one of a display of the vehicle or an audio device of the vehicle.

6. A server comprising: Memory, which stores computer-executable instructions; as well as at least one processor configured to access the memory and execute the instructions, wherein the instructions include: receiving charging speed data from a vehicle, the charging speed data comprising at least one of an actual charging speed and a unique identifier of the charger, wherein the actual charging speed comprises a speed at which a battery of the vehicle is actually charged by the charger; and Charger-specific charging speed data is generated, the charger-specific charging speed data including data matching an actual charging speed, a unique identifier of the charger, a date when the charging speed data is received, and a time when the charging speed data is received.

7. The server according to claim 6, wherein: The instruction includes matching external factor information with the charger-specific charging speed data, wherein the external factor information includes at least one of season, weather, external temperature, vehicle type, vehicle age, and charger age.

8. The server according to claim 7, wherein: The instructions include providing information related to the charger-specific charging speed data to a user via at least one of a navigation system of the vehicle, a mobile application, or a webpage.

9. The server according to claim 6, wherein: The instructions include receiving the charging speed data from the vehicle, the charging speed data including an actual charging speed calculated for a cycle, a maximum value of the actual charging speed calculated for a cycle, a minimum value of the actual charging speed calculated for a cycle, an average value of the actual charging speed calculated for a cycle, and an average value of the actual charging speed for an entire charging time elapsed from a start time of charging of the battery to a finish time of charging of the battery.

10. The server according to claim 9, wherein: The average of the actual charging speed of the entire charging time is calculated as: a value obtained by multiplying the difference between the state of charge of the battery at the end of charging of the battery and the state of charge of the battery at the start of charging of the battery by the capacity of the battery and dividing it by the entire charging time.

11. The server according to claim 6, wherein: The instructions include: identifying a total charging time elapsed from when charging of the battery begins to when charging of the battery ends; and Charger output data is received from the charger, the charger output data including at least one of a unique identifier of the charger, a maximum value of an output speed at which the charger outputs power during an entire charging time, a minimum value of an output speed at which the charger outputs power during an entire charging time, and an average value of an output speed at which the charger outputs power during an entire charging time.

12. The server according to claim 11, wherein: The instructions include comparing the charger output data to the charging speed data to determine performance of the charger.

13. A vehicle control method comprising: The vehicle control device recognizes that the vehicle uses a charger to charge the battery; identifying, by the vehicle control device, vehicle data, the vehicle data including at least one of the following: a time when charging of the battery starts, a state of charge of the battery when charging of the battery starts, a capacity of the battery, a time when charging of the battery ends, and a state of charge of the battery when charging of the battery ends; calculating, by the vehicle control device, an actual charging speed based on the vehicle data, wherein the actual charging speed includes a speed at which the battery is actually charged by the charger; as well as Information regarding charging speed data including at least one of the actual charging speed or a unique identifier of the charger is provided to a user by the vehicle control device using at least one of a display of the vehicle, an audio device of the vehicle.

14. The vehicle control method according to claim 13, wherein: Calculating the actual charging speed includes: The vehicle control device calculates the actual charging speed based on each cycle between the start time of charging of the battery and the end time of charging of the battery, and calculates at least one of the following items: the maximum value of the actual charging speed calculated for the cycle, the minimum value of the actual charging speed calculated for the cycle, and the average value of the actual charging speed calculated for the cycle.

15. The vehicle control method according to claim 13, wherein: Calculating the actual charging speed includes: The vehicle control device calculates an average of the actual charging speeds over the entire charging time by multiplying a value obtained by multiplying a difference between the state of charge of the battery at the end of charging of the battery and the state of charge of the battery at the start of charging of the battery by the capacity of the battery, dividing the value by the entire charging time elapsed from the start of charging of the battery to the end of charging of the battery, based on recognition that the actual charging speed for each cycle is not calculated, the battery is charged when the engine of the vehicle is turned off, charging of the battery is abnormally terminated, charging speed data is not transmitted to the server due to a communication failure, or any combination of the foregoing.

16. The vehicle control method according to claim 13, further comprising: The vehicle control device sends the charging speed data to a server; receiving, by the server, the charging speed data from the vehicle; as well as Charger-specific charging speed data is generated by the server, the charger-specific charging speed data including data matching the actual charging speed, a unique identifier of the charger, a date when the charging speed data is received, and a time when the charging speed data is received.

17. The vehicle control method according to claim 16, wherein: Generating the charger-specific charging speed data includes: matching external factor information with the charger-specific charging speed data by the server, wherein the external factor information includes at least one of season, weather, external temperature, vehicle type, vehicle age, and charger age.

18. The vehicle control method according to claim 17, further comprising: Information related to the charger-specific charging speed data is provided by the server to a user via at least one of a navigation system of the vehicle, a mobile application, or a webpage.

19. The vehicle control method according to claim 13, further comprising: The server receives charger output data from the charger, the charger output data including at least one of the following: a unique identifier of the charger, a maximum value of an output speed of the charger outputting power during an entire charging time from when charging of the battery starts to when charging of the battery ends, a minimum value of an output speed of the charger outputting power during the entire charging time, and an average value of an output speed of the charger outputting power during the entire charging time.

20. The vehicle control method according to claim 19, further comprising: The charger output data is compared with the charging speed data by a server to determine the performance of the charger.

Images