Vehicle charging system

Abstract

To improve usability when setting up timer charging.SOLUTION: In a vehicle charging system, an input device accepts an input operation regarding a scheduled departure time of a vehicle from a user of the vehicle, a setting unit sets a charging target SOC indicating a charging target of an SOC of a power storage device based on the scheduled departure time accepted by the input device, a charging control unit controls charging of the power storage device by a power supply facility such that the SOC of the power storage device becomes the charging target SOC by the scheduled departure time, and a storage device stores information on the actual departure time of the vehicle and information on a setting history of the charging target SOC in association with each other. The setting unit performs statistical processing on the information stored in the storage device to acquire a reference time that is an expected value of the departure time and a reference SOC that is an expected value of the charging target SOC. The setting unit sets the charging target SOC by changing the reference SOC according to a time difference between the scheduled departure time accepted by the input device and the reference time.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present disclosure relates to a charging system for a vehicle equipped with a power storage device.

Background Art

[0002] Japanese Unexamined Patent Application Publication No. 2022 - 146415 (Patent Document 1) discloses a charging control device that charges a battery mounted on a vehicle with power supplied from an external power source. Based on history information indicating the usage status and charging status of the battery, the charging control device determines the pattern of the charging cycle that most approximates the user's charging habit among multiple charging cycle patterns, and displays the charging completion SOC, charging start SOC, and allowable lower limit SOC on a display unit according to the determined charging cycle pattern. When the charging completion SOC is set to be lower according to the user's operation, the charging control device controls the battery to charge based on the set charging completion SOC.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the user's charging behavior, there is timer charging in which the scheduled departure time of the next vehicle is set and the battery is fully charged by the scheduled departure time. According to the above charging control device, the charging completion SOC in timer charging is displayed according to the pattern of the charging cycle determined from the user's charging habit of timer charging.

[0005] However, if a user wants to use timer charging that differs from their usual charging habits, for example, if the next scheduled departure time of the vehicle is different from the usual departure time, they cannot change the charging plan for timer charging. Also, while the battery usage may change along with the scheduled departure time of the vehicle, it is not possible to set the State of Charge (SOC) to accommodate changes in battery usage.

[0006] One possible solution is for users to set the charging completion SOC (State of Charge) along with the vehicle's scheduled departure time each time, but this would increase the user's workload. Furthermore, some users may find it difficult to set an appropriate charging completion SOC based on battery usage. As a result, there are concerns that this could reduce the usability when setting up timer charging.

[0007] This disclosure is made to solve the above-mentioned problems, and its purpose is to improve the usability when setting timer charging for vehicles equipped with energy storage devices. [Means for solving the problem]

[0008] A vehicle charging system according to one aspect of this disclosure comprises a vehicle equipped with a power storage device, a power supply facility configured to charge the power storage device from outside the vehicle, an input device, a setting unit, a charging control unit, and a storage device. The input device receives input from the vehicle user regarding the vehicle's scheduled departure time. The setting unit sets a target SOC (State of Charge) indicating the charging target for the power storage device's State of Charge (SOC) based on the scheduled departure time received by the input device. The charging control unit controls the charging of the power storage device by the power supply facility so that the SOC of the power storage device reaches the target SOC by the scheduled departure time. The storage device stores information relating to the actual departure time of the vehicle and information relating to the setting history of the target SOC. The setting unit obtains a reference time, which is an estimated value of the departure time, and a reference SOC, which is an estimated value of the target SOC, by statistically processing the information stored in the storage device. The setting unit sets the target SOC by changing the reference SOC according to the time difference between the scheduled departure time received by the input device and the reference time.

[0009] With the above configuration, the target State of Charge (SOC) for timer charging is automatically set in response to user input regarding the next scheduled departure time of the vehicle. This eliminates the need for the user to manually input the target SOC, thus reducing user effort. Furthermore, since the target SOC is set based on the scheduled departure time using a reference time and reference SOC derived from information on vehicle usage history and the history of setting the target SOC, the target SOC can be appropriately set in anticipation of the energy storage device's usage during the next trip. Therefore, usability when setting timer charging can be improved.

[0010] Preferably, if the time difference between the scheduled departure time and the reference time is less than or equal to a predetermined threshold, the setting unit sets the target charge SOC to the reference SOC. If the scheduled departure time coincides with the reference time, the setting unit determines that the target charge SOC also coincides with the reference SOC, thereby automatically setting the target charge SOC to an appropriate value that reflects the user's vehicle usage habits and timer charging habits.

[0011] Preferably, if the time difference between the scheduled departure time and the reference time is greater than a threshold, the setting unit (1) sets the target charge SOC to a value higher than the reference SOC when the scheduled departure time is earlier than the reference time, and (2) sets the target charge SOC to a value lower than the reference SOC when the scheduled departure time is later than the reference time. This allows the target charge SOC to be set to an appropriate value, taking into account the usage status of the energy storage device, even when the scheduled departure time deviates from the reference time.

[0012] Preferably, the setting unit obtains a reference time by statistically processing information on actual departure times on the same day of the week as the scheduled departure time. This makes it possible to obtain a reference time based on the user's vehicle usage habits.

[0013] Preferably, the setting unit obtains a reference SOC by statistically processing information regarding the setting history of the charging target SOC for the same day of the week or time slot as the scheduled departure time. This makes it possible to obtain a reference SOC based on the user's habit of performing timer charging.

[0014] Preferably, the vehicle charging system further includes a notification device that informs the user of the target state of charge (SOC) set by the setting unit. The input device is configured to receive user input for changing the target SOC. The setting unit changes the setting of the target SOC in accordance with the user input. This allows the user to appropriately change the target SOC according to the next vehicle driving plan. [Effects of the Invention]

[0015] According to this disclosure, it is possible to improve the usability when setting timer charging for vehicles equipped with energy storage devices. [Brief explanation of the drawing]

[0016] [Figure 1] This figure shows an example of the configuration of a vehicle to which a charging system according to the embodiment is applied. [Figure 2]It is a diagram showing a schematic configuration of a vehicle charging system according to an embodiment. [Figure 3] It is a diagram showing an example of a charging plan setting screen displayed on a touch panel display of a user terminal. [Figure 4] It is a flowchart showing an example of a process for setting a charging target SOC in timer charging. [Figure 5] It is a diagram for explaining information stored in a storage device of a server. [Figure 6] It is a flowchart showing another example of a process for setting a charging target SOC in timer charging.

Mode for Carrying Out the Invention

[0017] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and the description thereof will not be repeated.

[0018] <Configuration of Vehicle> FIG. 1 is a diagram showing a configuration example of a vehicle to which a vehicle charging system according to the present embodiment is applied. As shown in FIG. 1, the vehicle 50 includes a battery 130 that stores traveling power, an inlet 110, a charger / discharger 120, monitoring modules 121 and 131, a traveling drive unit 140, an ECU (Electronic Control Unit) 150, an HMI (Human Machine Interface) 160, a navigation system (hereinafter also referred to as "NAVI") 170, and a communication device 180.

[0019] The battery 130 is, for example, a secondary battery such as a lithium-ion battery or a nickel-metal hydride battery, or an electric double layer capacitor. The battery 130 corresponds to an example of a "power storage device". The vehicle 50 may be an electric vehicle that can travel using only the power stored in the battery 130, or a plug-in hybrid vehicle that can travel using both the power stored in the battery 130 and the output of an engine.

[0020] The monitoring module 131 monitors the state of the battery 130. The monitoring module 131 includes various sensors for detecting the state of the battery 130 (such as voltage, current, and temperature), and outputs the detection results to the ECU 150. The ECU 150 can obtain the state of the battery 130 (such as voltage, current, temperature, SOC (State Of Charge), and internal resistance) based on the output of the monitoring module 131.

[0021] The EVSE (Electric Vehicle Supply System) 40 is a vehicle power supply facility. The EVSE 40 includes a power supply circuit 41. A charging cable 42 is connected to the EVSE 40. The charging cable 42 has a connector 43 at its tip and has a power line inside.

[0022] The inlet 110 is configured such that the connector 43 of the charging cable 42 can be connected. When the connector 43 of the charging cable 42 is connected to the inlet 110, the vehicle 50 and the EVSE 40 are electrically connected, and it becomes possible to supply power from the EVSE 40 to the vehicle 50 through the charging cable 42. As a result, external charging (that is, charging of the battery 130 with power from outside the vehicle) becomes possible in the vehicle 50.

[0023] The charger / discharger 120 is disposed between the inlet 110 and the battery 130. The charger / discharger 120 includes a relay for switching the connection / disconnection of the power path from the inlet 110 to the battery 130, and a power converter (such as a bidirectional converter). The power converter converts the power received by the inlet 110 into power suitable for charging the battery 130 (that is, power for external charging) and outputs it to the battery 130. The relay and the power converter are controlled by the ECU 150.

[0024] The monitoring module 121 monitors the state of the charger / discharger 120. The monitoring module 121 includes various sensors for detecting the state of the charger / discharger 120 (such as the voltage and current input / output to the power converter), and outputs the detection results to the ECU 150.

[0025] The drive unit 140 includes a PCU (Power Control Unit) and an MG (Motor Generator), and uses the power stored in the battery 130 to drive the vehicle 50. The PCU includes a power converter, an SMR (System Main Relay), and a control device. The control device controls the power converter and relay according to instructions from the ECU 150. The MG is, for example, a three-phase AC motor generator, which is driven by the PCU to rotate the drive wheels W. The MG supplies regenerated power to the battery 130. The SMR switches the connection / disconnection of the power path from the battery 130 to the PCU.

[0026] The ECU 150 includes a processor 151, RAM (Random Access Memory) 152, a storage device 153, and a timer 154. The processor 151 is, for example, a CPU (Central Processing Unit). The RAM 152 functions as working memory for temporarily storing data processed by the processor 151. The timer 154 is configured to notify the processor 151 of the arrival of a set time.

[0027] The storage device 153 includes, for example, ROM (Read Only Memory) and non-volatile memory. The storage device 153 stores programs as well as information used by those programs. The processor 151 executes the programs stored in the storage device 153, thereby performing various controls by the ECU 150. These controls are not limited to software execution; they can also be performed using dedicated hardware.

[0028] The information stored in the storage device 153 includes information about the usage history of the vehicle 50, information about the execution history of external charging, and information about the usage plan of the vehicle 50. The usage history of the vehicle 50 includes the driving history of the vehicle 50 (e.g., the departure time, driving route, and driving time of the vehicle 50). The execution history of external charging includes the charging location, the specifications of the power supply equipment installed at the charging location, and the execution history of timer charging. Timer charging is performed by externally charging the battery 130 so that its State of Charge (SOC) reaches the target SOC by the scheduled departure time of the vehicle 50. In order to avoid a situation where the SOC of the battery 130 is low when the vehicle 50 departs, the processor 151 controls the charging of the battery 130 so that the SOC reaches the target SOC by the scheduled departure time. The execution history of timer charging includes the setting history of the target SOC.

[0029] The usage plan for vehicle 50 includes the driving plan for vehicle 50 (e.g., the scheduled departure time and route of vehicle 50) and the charging plan for battery 130 (e.g., the target state of charge).

[0030] The HMI160 includes an input device and a display device. The HMI160 may include a touch panel display. The HMI160 may include an instrument panel and / or a head-up display. The HMI160 may include a smart speaker that accepts voice input. The user can use the HMI160 to register the vehicle usage plan for the vehicle 50 described above in the storage device 153. The HMI160 corresponds to one embodiment of the "input device" and the "notification device".

[0031] NAVI170 includes a touch panel display, a GPS (Global Positioning System) module, a processor, and a storage device. The storage device stores map information. The touch panel display accepts user input and displays maps and other information. NAVI170 receives signals from GPS satellites and uses the received signals to detect the position of vehicle 50. NAVI170 refers to the map information and performs route searching to find the optimal route from the vehicle 50's current location to the destination. NAVI170 corresponds to one embodiment of the "input device" and "notification device".

[0032] The communication device 180 includes various communication interfaces. The ECU 150 communicates with external communication devices of the vehicle 50 through the communication device 180. External communication devices of the vehicle 50 include the EVSE 40, the server 30 (described later), and the user terminal 80. The ECU 150 transmits information stored in the storage device 153 (information regarding the usage history of the vehicle 50, information regarding the execution history of external charging, and information regarding the usage plan of the vehicle 50) to the server 30 through the communication device 180.

[0033] <Configuration of the vehicle's charging system> Figure 2 shows a schematic configuration of a vehicle charging system according to this embodiment. As shown in Figure 2, the vehicle charging system 1 comprises a server 30, an EVSE 40, a vehicle 50, and a user terminal 80.

[0034] The user terminal 80 corresponds to one embodiment of a "terminal device" carried by the user of the vehicle 50. In the example shown in Figure 2, the user terminal 80 is a smartphone, but any terminal device can be used. The user terminal 80 has predetermined application software (hereinafter simply referred to as "app") installed. The user terminal 80 can exchange various information with the server 30 and the communication device 180 installed in the vehicle 50 through the app. The user can operate the app, for example, through the touch panel display of the user terminal 80. The touch panel display of the user terminal 80 can also provide information to the user.

[0035] The server 30 is configured to communicate with both the vehicle 50 and the user terminal 80. The server 30 includes a control device 31, a storage device 32, and a communication device 33. The control device 31 includes a processor and performs predetermined information processing and controls the communication device 33.

[0036] The storage device 32 stores the program executed by the control device 31, and various information used by the program. This information includes information received from the vehicle 50's ECU 150 (information regarding the vehicle 50's usage history, information regarding the execution history of external charging, and information regarding the vehicle 50's usage plan).

[0037] The communication device 33 includes various communication interfaces. The control device 31 communicates with the user terminal 80 and the communication equipment 180 of the vehicle 50 through the communication device 33 and receives information. The server 30 updates the information in the storage device 32 based on the received information.

[0038] <Battery timer charging> Next, timer charging of the battery 130 will be described. In this embodiment, the user can set a charging plan for timer charging of the battery 130 by operating the user terminal 80, HMI 160, or NAVI 170. Below, an example of the user setting a charging plan by operating the user terminal 80 will be described.

[0039] Figure 3 shows an example of a charging plan setting screen displayed on the touch panel display of the user terminal 80. As shown in Figure 3, the setting screen includes an operation unit 200, a setting bar 210, display bars 212 and 214, and buttons 216 and 218.

[0040] The control unit 200 accepts user input regarding the next scheduled use of vehicle 50. The next scheduled use of vehicle 50 includes the scheduled departure date and time of vehicle 50. The user can set the scheduled departure date and time of vehicle 50 by operating the control unit 200.

[0041] Display bar 212 is displayed on setting bar 210 and shows the current SOC of battery 130 as the length of the bar. Display bar 214 is displayed on setting bar 210 and shows the set value of the target SOC for the next timer charge as the length of the bar.

[0042] In this embodiment, the charging target SOC is automatically set based on the next scheduled use of the vehicle 50 (scheduled departure date and scheduled departure time) received by the operation unit 200, and a display bar 214 showing the set value of the charging target SOC is displayed on the setting bar 210. This eliminates the need for the user to manually input the charging target SOC. The method for setting the charging target SOC will be explained in detail later.

[0043] Button 216 is a button that allows the user to change the charging target SOC setting displayed on the setting bar 210. After touching button 216, the user can change the charging target SOC by touching the right edge of the display bar 214 and sliding it left or right.

[0044] Button 218 is used to complete the settings for the vehicle 50's planned usage and target State of Charge (SOC). The user can confirm each setting by touching button 218.

[0045] (Setting the target State of Charge) Figure 4 is a flowchart showing an example of the process for setting the target State of Charge (SOC) in timer charging. The series of processes shown in the flowchart of Figure 4 are executed by the user terminal 80 and the server 30 when the user sets a charging plan using the user terminal 80. The server 30 corresponds to one embodiment of the "setting unit".

[0046] In the diagram, the processes executed by the user terminal 80 are shown on the left, and the processes executed by the server 30 are shown on the right. Each step is implemented by software processing by the processor in the user terminal 80 and the control device 31 of the server 30, but may also be implemented by electronic circuits (hardware) located in the user terminal 80 and the server 30.

[0047] In step 01 (hereinafter simply referred to as "S"), the user terminal 80 displays the charging plan setting screen (Figure 3) on the touch panel display in response to receiving a request from the user to set a charging plan. In certain situations, the user terminal 80 displays the charging plan setting screen (Figure 3) in response to the user launching a pre-installed application.

[0048] In S02, the user terminal 80 determines whether or not it has received user input regarding the next scheduled use of vehicle 50 (scheduled departure date and scheduled departure time). If user input regarding the next scheduled use of vehicle 50 has been received (resulting in a YES determination in S02), the user terminal 80 sends information regarding the next scheduled use of vehicle 50 (scheduled departure date and scheduled departure time) to the server 30 in S03.

[0049] In S11, the server 30 determines whether it has received information from the user terminal 80 regarding the next scheduled use of vehicle 50 (scheduled departure date and scheduled departure time). If it has received information regarding the next scheduled use of vehicle 50 (scheduled departure date and scheduled departure time) (YES determination in S11), the server 30 obtains the reference time and reference SOC in S12 based on the information stored in the storage device 32. The reference time is the expected departure time of vehicle 50. The reference SOC is the expected value of the target SOC for timer charging.

[0050] Figure 5 is a diagram illustrating the information stored in the storage device 32 of the server 30. The information stored in the storage device 32 includes information received from the vehicle 50's ECU 150 regarding the vehicle's driving history and timer charging execution history. As shown in Figure 5, the storage device 32 stores information regarding the actual departure time of the vehicle 50 and information regarding the setting history of the charging target SOC in association with each other.

[0051] Figure 5 shows the time period that includes the actual departure dates and departure times of vehicle 50. The length of each time period can be set arbitrarily. Figure 5 also shows the set value of the target State of Charge (SOC) for the most recent timer charge for each departure date. The period for which the vehicle 50's driving history and timer charge execution history are stored in the storage device 32 can be set to any length. In certain situations, the length of this period can be set considering that the usage patterns of vehicle 50 change in accordance with changes in the user's living environment (place of residence, climate, workplace, etc.).

[0052] Server 30 obtains a reference time by statistically processing the information shown in Figure 5. For example, Server 30 obtains a reference time by statistically processing the actual departure times on the same day of the week as the next scheduled departure date of vehicle 50. The reference time can be, for example, the time period that includes the average or mode of the actual departure times on the same day of the week as the scheduled departure date.

[0053] Furthermore, the server 30 obtains a reference SOC by statistically processing the information shown in Figure 5. In certain situations, the server 30 obtains a reference SOC by statistically processing the charging target SOC setting history for the same day of the week as the next scheduled departure date of the vehicle 50. The reference SOC can be, for example, the average or mode of the charging target SOC settings for the same day of the week.

[0054] In another scenario, the server 30 obtains a reference SOC by statistically processing the charging target SOC setting history for the same time period as the next scheduled departure time of the vehicle 50. The reference SOC can be, for example, the average or mode of the charging target SOC settings for the same time period.

[0055] Next, the server 30 compares the reference time obtained in S12 with the scheduled departure time of the next vehicle 50 and determines whether the scheduled departure time matches the reference time. For example, the server 30 calculates the time difference between the reference time and the scheduled departure time, and if the magnitude of this time difference is less than or equal to a predetermined threshold, it determines that the scheduled departure time matches the reference time. If the above time difference is greater than the threshold, the server 30 further determines whether the scheduled departure time is earlier or later than the reference time.

[0056] If the scheduled departure time is earlier than the reference time (when S13 determines YES), the server 30 sets the target SOC for the next timer charge to a value higher than the reference SOC in S14. In S14, the server 30 assumes that the vehicle 50 has traveled for a time equivalent to the time difference between the reference time and the scheduled departure time, and calculates the amount of power required for this travel. This amount of power can be calculated, for example, by calculating the distance the vehicle 50 can travel in the above time and using the calculated distance and the vehicle 50's energy consumption. The distance the vehicle 50 can travel can be calculated from the vehicle 50's travel history stored in the storage device 32, or from the vehicle 50's driving mode (vehicle speed). The server 30 sets the target SOC by adding the calculated amount of power to the reference SOC.

[0057] On the other hand, if the scheduled departure time is later than the reference time (when S15 determines YES), the server 30 sets the target SOC for the next timer charge at a value lower than the reference SOC in S16. In S16, in contrast to S14, the server 30 assumes that the vehicle 50 is not moving for a time equivalent to the time difference between the reference time and the scheduled departure time, and calculates the amount of power required for this movement. Then, the server 30 sets the target SOC by subtracting the calculated amount of power from the reference SOC.

[0058] If the scheduled departure time matches the reference time (when NO is determined in S15), the server 30 sets the target SOC for the next timer charge to the reference SOC in S17.

[0059] When the target SOC is set by any of S14, S16, or S17, the server 30 transmits the set target SOC to the user terminal 80 by S18. Furthermore, the server 30 transmits the set value of the target SOC to the vehicle 50's ECU 150 by S19, along with the next scheduled departure date and time of the vehicle 50. As a result, the vehicle 50's ECU 150 controls the charging of the battery 130 so that the SOC of the battery 130 reaches the target SOC by the scheduled departure time on the next scheduled departure date. The ECU 150 corresponds to one embodiment of the "charging control unit".

[0060] In S03, the user terminal 80 sends information regarding the next scheduled use of the vehicle 50 (scheduled departure date and scheduled departure time) to the server 30, and then in S04, it determines whether or not it has received the set value for the target charge SOC from the server 30. If the set value for the target charge SOC is received (YES determination in S04), the user terminal 80 displays a display bar 214 indicating the set value for the target charge SOC on the setting bar 210 of the charging plan setting screen (Figure 3) in S05.

[0061] As described above, according to the vehicle charging system of this embodiment, the target SOC for the next timer charge is automatically set in response to user input regarding the next planned use of the vehicle (departure date and planned departure time). This eliminates the need for the user to input the target SOC, thus reducing the user's workload. Furthermore, since the target SOC is set based on the planned departure time using a reference time and reference SOC derived from information on the vehicle's driving history and timer charge execution history, the target SOC can be appropriately set while reflecting the user's vehicle usage habits and timer charge execution habits, and anticipating the usage of the battery 130 during the next drive. Therefore, usability when setting timer charge can be improved.

[0062] <Other Embodiments> (1) In the embodiment described above, the charging target SOC for timer charging is automatically set according to the next scheduled use of the vehicle 50 (scheduled departure date and scheduled departure time) and displayed on the charging plan setting screen (Figure 3) of the user terminal 80. However, the user can change the set charging target SOC as appropriate by touching the button 216 on the charging plan setting screen.

[0063] Figure 6 is a flowchart showing another example of the process for setting the target State of Charge (SOC) in timer charging. The flowchart in Figure 6 is the same as the flowchart in Figure 4, with the addition of processes S06, S07, S20, and S21. Processes S1 to S17, which are executed by the server 30, are the same as in Figure 4 and are therefore omitted from the description.

[0064] When the user terminal 80 is in a state where the target charge SOC is displayed on the charging plan setting screen (Figure 3) by S05, it determines in S06 whether or not it has received a user operation to change the target charge SOC. If it has received a user operation to change the target charge SOC (when S06 is determined to be YES), the user terminal 80 sends the changed target charge SOC to the server 30 in S07.

[0065] After the server 30 transmits the target charge SOC to the user terminal 80 in S18, it determines in S20 whether or not it has received the set value of the target charge SOC from the user terminal 80. If the server 30 has received the set value of the target charge SOC from the user terminal 80 (when S20 determines YES), the server 30 changes the target charge SOC to the received target charge SOC in S21, using one of S14, S16, or S17. Then, in S19, the server 30 transmits the set value of the target charge SOC to the ECU 150 of the vehicle 50, associating it with the next scheduled departure date and time of the vehicle 50.

[0066] Furthermore, if the target SOC is changed in response to user operation, the information stored in the server 30's storage device 32 (see Figure 5) is updated. This allows the change in the target SOC to be reflected in the setting of the target SOC for subsequent timer charging.

[0067] (2) In the above-described embodiment, a configuration was described in which the server 30 sets the target SOC in response to user operations on the user terminal 80. However, a configuration in which the vehicle 50's ECU 150 or the user terminal 80 sets the target SOC is also possible. In this case, the ECU 150 or the user terminal 80 functions as a "setting unit".

[0068] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than by the description of the embodiments above, and all modifications within the meaning and scope equivalent to the claims are intended. [Explanation of Symbols]

[0069] 1 Charging system, 30 Server, 31 Control device, 32 Storage device, 33 Communication device, 40 EVSE, 50 Vehicle, 80 User terminal, 110 Inlet, 120 Charger / Discharger, 130 Battery, 140 Drive unit, 150 ECU, 180 Communication equipment.

Claims

1. Vehicles equipped with energy storage devices, A power supply system configured to charge the energy storage device from outside the vehicle, An input device that receives input from the user of the vehicle regarding the scheduled departure time of the vehicle, A setting unit sets a charging target SOC indicating the charging target of the SOC of the energy storage device based on the scheduled departure time received by the input device, A charge control unit controls the charging of the energy storage device by the power supply equipment so that the State of Charge (SOC) of the energy storage device becomes the target SOC by the scheduled departure time, The system includes a storage device that stores information relating to the actual departure time of the vehicle and information relating to the setting history of the charging target SOC, The aforementioned setting unit is, By statistically processing the information stored in the memory device, a reference time, which is the predicted value of the departure time, and a reference SOC, which is the predicted value of the charging target SOC, are obtained. A vehicle charging system that sets the target charging state of care (SOC) by changing the reference SOC according to the time difference between the scheduled departure time and the reference time received by the input device.

2. The vehicle charging system according to claim 1, wherein if the time difference between the scheduled departure time and the reference time is less than or equal to a predetermined threshold, the setting unit sets the target charging SOC to the reference SOC.

3. If the time difference between the scheduled departure time and the reference time is greater than the threshold, the setting unit will If the scheduled departure time is earlier than the reference time, the target SOC for charging is set to a value higher than the reference SOC. The vehicle charging system according to claim 2, wherein when the scheduled departure time is later than the reference time, the target SOC is set to a value lower than the reference SOC.

4. The vehicle charging system according to any one of claims 1 to 3, wherein the setting unit obtains the reference time by statistically processing information regarding actual departure times on the same day of the week as the scheduled departure time.

5. The vehicle charging system according to any one of claims 1 to 3, wherein the setting unit obtains the reference SOC by statistically processing information regarding the setting history of the charging target SOC on the same day of the week or time zone as the scheduled departure time.

6. The system further includes a notification device that notifies the user of the charging target SOC set by the setting unit, The input device is configured to receive user input for changing the target SOC for charging, The vehicle charging system according to any one of claims 1 to 3, wherein the setting unit changes the setting of the charging target SOC in accordance with the user input.

Images