JP2017079518A - Charging control device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a charging control device that can restrain external charging tailored to an event without using a vehicle from being performed, and can achieve appropriate external charging.SOLUTION: A data center 300 comprises a communication module 310 and a controller 330. The communication module 310 obtains a schedule for users of an electric vehicle 100 from a scheduler capable of managing a time schedule for events to use the electric vehicle 100 and a time schedule for events not to use the electric vehicle 100. The controller 330 extracts the time schedule for the events to use the electric vehicle 100 from the obtained schedule for the users, and sets a charging time schedule according to the extracted time schedule.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a charge control device, and more particularly, to a charge control device for performing charging by a power supply external to a power storage device mounted on a vehicle (hereinafter also referred to as “external charging”).

  Japanese Patent Laying-Open No. 2014-011849 (Patent Document 1) discloses a charge / discharge control device that controls charge / discharge of a power storage device mounted on a vehicle. When the vehicle is parked, the charge / discharge control device estimates the parking time of the vehicle with reference to schedule information indicating the action schedule of the user who uses the vehicle. And this charging / discharging control apparatus calculates the electric energy which can be charged / discharged during parking of a vehicle, and transmits the information regarding the calculated electric energy to a user's portable terminal. Thus, the user can determine whether or not to charge / discharge the power storage device during parking after recognizing the amount of power that can be charged / discharged while the vehicle is parked.

JP, 2014-011849, A

  In the charge / discharge control device disclosed in Patent Document 1, the schedule information indicating the user's action schedule is dedicated information provided for estimating the parking time of the vehicle. The charge / discharge control device can perform various controls related to external charging of the power storage device mounted on the vehicle by referring to the schedule information.

  Further, instead of such schedule information, external charging can be performed by referring to information on a scheduler (for example, a scheduler on the web or a scheduler in a mobile terminal) used by a user for usual schedule management. It is conceivable to set a time schedule (hereinafter also referred to as “charging schedule”).

  However, in a general scheduler, not only the time schedule of events in which vehicles are used, but also the time schedule of events in which vehicles are not used can be registered. If external charging is performed for each event registered in the scheduler, external charging is performed even for an event in which the vehicle is not used. Since the power storage device mounted on the vehicle deteriorates when left for a long time in a high SOC (State Of Charge) state after charging, it is not preferable that external charging is performed for an event in which the vehicle is not used. .

  The present invention has been made to solve such a problem, and its purpose is to suppress external charging for an event not involving the use of a vehicle and realize appropriate external charging. It is providing the charge control apparatus which can do.

  A charging control device according to an aspect of the present invention performs charging by a power source outside a vehicle of a power storage device mounted on the vehicle. The charging control device includes an acquisition unit and a control device. An acquisition part acquires a vehicle user's schedule from the scheduler which can manage the time schedule of the event with use of a vehicle, and the time schedule of the event without use of a vehicle. The control device extracts a time schedule of an event that accompanies the use of the vehicle from the acquired user schedule, and sets a charging schedule according to the extracted time schedule.

  In this charging control apparatus, a time schedule of an event involving the use of a vehicle is extracted from the schedule of the vehicle user managed by the scheduler, and the charging schedule is set according to the extracted time schedule. Therefore, according to this charging control device, the possibility of external charging for an event involving the use of a vehicle can be increased, and the possibility of external charging for an event not involving the use of a vehicle can be performed. Can be lowered.

  According to the present invention, it is possible to provide a charge control device that can suppress external charging for an event that does not involve the use of a vehicle and can realize appropriate external charging. As a result, deterioration of the power storage device due to the power storage device being left in a high SOC state for a long time after charging can be suppressed.

It is a whole block diagram of an external charging system. It is a whole block diagram which shows the structure of an electric vehicle. It is the block diagram which showed the structure of the data center roughly. It is a figure which shows an example in case the time schedule of the event which arises on the go outside is registered into the scheduler. It is a figure which shows an example in case both the event which arises at home and the event which accompanies going out are registered into the scheduler. It is a flowchart which shows the production | generation procedure of a charging schedule in case the time schedule of the event which arises on the go outside is registered into the scheduler. It is a flowchart which shows the procedure of the learning process of commuting time. It is a flowchart which shows the production | generation procedure of a charging schedule in case the time schedule of both the event which arises at home, and the event with going out is registered into the scheduler. 4 is a flowchart showing a processing procedure for learning whether an event included in a time schedule is an event involving the use of electric vehicle 100. FIG.

  Hereinafter, embodiments of the present invention 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 description thereof will not be repeated.

[Embodiment 1]
(Configuration of external charging system)
1 is an overall configuration diagram of an external charging system to which an electric vehicle according to Embodiment 1 of the present invention is applied. Referring to FIG. 1, external charging system 1 includes an electric vehicle 100, a charging stand 200, a data center 300, and a smartphone 500.

  Electric vehicle 100 is connected to charging station 200 through charging cable 400. The charging stand 200 is a device that supplies electric power from the power source to the electric vehicle 100. The electric vehicle 100 stores the electric power supplied from the charging station 200 in a power storage device (described later) mounted on the vehicle. Electric vehicle 100 also has a function of automatically starting external charging according to a preset charging schedule. Hereinafter, external charging by such a function is also referred to as “timer charging”.

  The smartphone 500 is a communication device that can communicate with various devices. A user can access a scheduler managed on the Internet through the smartphone 500. The scheduler can manage the time schedule of events that involve the use of the electric vehicle 100 and the time schedule of events that do not involve the use of the electric vehicle 100. Here, the event is an item registered in the scheduler, and includes, for example, various actions of the user (for example, attendance at a meeting, pick-up of a child). The user can manage the daily schedule by accessing the scheduler through the smartphone 500.

  The data center 300 can perform various types of information processing. In the data center 300, the charging schedule is generated by referring to the user's schedule managed by the scheduler. In particular, the charging schedule is generated according to the time schedule of the event that involves using the electric vehicle 100 in the user's schedule. A procedure for generating a charging schedule in the data center 300 will be described in detail later.

  The electric vehicle 100 has a wireless communication function. The electric vehicle 100 receives a charging schedule from the data center 300 through the communication network. The timer charging according to the charging schedule automatically generated by the data center 300 or the like instead of the charging schedule set by the user is also referred to as “automatic timer charging” below. In the external charging system 1, the electric vehicle 100 can perform automatic timer charging according to the charging schedule received from the data center 300.

(Configuration of electric vehicle)
FIG. 2 is an overall block diagram showing the configuration of the electric vehicle 100. Electric vehicle 100 is, for example, an electric vehicle or a hybrid vehicle.

  Referring to FIG. 2, electrically powered vehicle 100 includes a charging inlet 110, a power storage device 120, a charger 130, a PCU (Power Control Unit) 140, a DCM (Data Communication Module) 150, and a GPS (Global Positioning System). ) Module 160 and ECU (Electronic Control Unit) 170.

  Charging connector 410 of charging cable 400 is connected to charging inlet 110. Then, electric power from a power source outside the vehicle is supplied to the electric vehicle 100 through the charging connector 410 and the charging inlet 110.

  The power storage device 120 is a power storage element configured to be chargeable / dischargeable. The power storage device 120 includes, for example, a secondary battery such as a lithium ion battery, a nickel metal hydride battery, or a lead storage battery, and a power storage element such as an electric double layer capacitor.

  The charger 130 converts an alternating current supplied from a power supply outside the vehicle through the charging inlet 110 into a direct current. Then, the charger 130 increases or decreases the voltage to a desired voltage and supplies the voltage to the power storage device 120. The charger 130 includes, for example, a rectifier circuit that converts an alternating current into a direct current and a converter that steps up or steps down the voltage. Charger 130 is not limited to such a configuration, and may be configured to supply DC power supplied from a power source outside the vehicle to power storage device 120, for example.

  PCU 140 includes an inverter, a motor connected to the inverter, and the like, and generates a traveling driving force of electric vehicle 100 using electric power supplied from power storage device 120.

  The DCM 150 is a communication device that can wirelessly communicate with the outside. The DCM 150 is, for example, a communication module compliant with a communication standard such as W-CDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), or a wireless LAN standard such as IEEE (Institute of Electrical and Electronic Engineers) 802.11. including.

  The GPS module 160 is a receiving device used in a satellite positioning system. The GPS module 160 calculates the current position of the electric vehicle 100 based on the received signal.

  The ECU 170 includes a CPU (Central Processing Unit) and a memory (not shown), and each device (the charger 130, the PCU 140, the ECU 130) of the electric vehicle 100 based on information stored in the memory and information from each sensor (not shown). The DCM 150 and the GPS module 160) are controlled. ECU 170 has a built-in timer and can recognize the current time.

  The main function realized by the ECU 170 is an automatic timer charging function. As described above, the automatic timer charging function is timer charging performed in accordance with a charging schedule automatically generated by the data center 300 or the like. When ECU 170 recognizes that the time indicated by the charging schedule received from data center 300 has arrived, it controls charger 130 to start external charging. Thereby, an automatic timer charging function is realized. When the charging connector 410 is connected to the charging inlet 110, the ECU 170 transmits a charging schedule generation instruction for automatic timer charging to the data center 300 through the DCM 150.

  The ECU 170 has a function of estimating the user's commuting time (required time). ECU 170 acquires a user's schedule from a scheduler managed on the Internet through DCM 150. The ECU 170 estimates the user's commuting time from the acquired user's schedule and the usage status of the user's electric vehicle 100. The ECU 170 also has a function of estimating the travel time for each event. The procedure for estimating the commuting time and travel time will be described in detail later. The ECU 170 transmits information regarding the estimated commuting time and travel time to the data center 300 through the DCM 150.

  The ECU 170 has a function of learning which event included in the user's schedule is an event that accompanies the use of the electric vehicle 100. The ECU 170 learns which event is an event involving the use of the electric vehicle 100 from the user schedule acquired through the DCM 150 and the position information of the electric vehicle 100 acquired through the GPS module 160. A learning procedure for an event involving the use of the electric vehicle 100 will be described in detail later. ECU 170 transmits the learning result to data center 300 through DCM 150.

(Data center configuration)
FIG. 3 is a block diagram schematically showing the configuration of the data center 300 shown in FIG. With reference to FIG. 3, the data center 300 includes a communication module 310, a storage device 320, and a controller 330.

  The communication module 310 is a communication module that can communicate with the electric vehicle 100 and the smartphone 500. The communication module 310 receives information on electricity charges for each time zone from a server (for example, managed by an electric power company). Moreover, the communication module 310 receives the schedule of the user of the electric vehicle 100 from the scheduler managed on the other server. In addition, the communication module 310 includes information on the estimated commuting time of the user in the electric vehicle 100 and information indicating which of the events included in the user's schedule is an event involving the use of the electric vehicle 100. Received from the electric vehicle 100. The communication module 310 outputs the received information to the controller 330.

  The storage device 320 stores various information collected from the Internet, a control program executed in the data center 300, and the like. For example, the storage device 320 stores information on the electricity rate for each time period received by the communication module 310, the user's schedule, and the like.

  The controller 330 generates a charging schedule in accordance with the information on the electricity rate for each time period, the user's schedule, and the like acquired through the communication module 310. The controller 330 transmits the generated charging schedule to the electric vehicle 100 through the communication module 310. The charging schedule generation processing procedure will be described in detail later.

(Description of automatic generation process of charging schedule)
In the data center 300 configured as described above, a charging schedule for the power storage device 120 mounted on the electric vehicle 100 is automatically generated. In generating the charging schedule, information on a scheduler (for example, a scheduler on the web) used by the user for usual schedule management is referred to.

  However, in a general scheduler, not only the time schedule of events in which the electric vehicle 100 is used, but also the time schedule of events in which the electric vehicle 100 is not used can be registered. If external charging is performed for each event registered in the scheduler, external charging is performed even for an event in which electric vehicle 100 is not used. Power storage device 120 mounted on electric vehicle 100 deteriorates when left for a long time in a high SOC state after charging. Therefore, it is not preferable that external charging is performed for an event in which electric vehicle 100 is not used. .

  Therefore, in the data center 300 according to the first embodiment, the controller 330 extracts the time schedule of the event accompanied by the use of the electric vehicle 100 from the user's schedule, and is mounted on the electric vehicle 100 according to the extracted time schedule. A charging schedule for power storage device 120 is set.

  This increases the possibility of external charging for an event involving the use of electric vehicle 100, and reduces the possibility of external charging for an event not involving use of electric vehicle 100. As a result, the deterioration of power storage device 120 due to the power storage device 120 being left in a high SOC state for a long time after charging can be suppressed.

(Explanation of charge schedule generation processing procedure according to how the scheduler is used)
What event time schedule is registered in the scheduler differs depending on the user. For example, one user manages a time schedule of events that occur in a place away from home (for example, a company) using a scheduler (such management is hereinafter also referred to as “outside place event management”), and another user takes home. Both events that occur in the event (events that do not involve the use of the electric vehicle 100) and events that involve going out (events that involve the use of the electric vehicle 100) are managed by the scheduler. Also referred to as “management”.) In data center 300 according to the first embodiment, a charging schedule is generated by different procedures depending on what event time schedule is registered in the scheduler by the user.

  FIG. 4 is a diagram illustrating an example of a case where the scheduler is used for going-out event management. Referring to FIG. 4, this scheduler manages a time schedule for each day of the user. In this example, at 9: 00-10: 00, 13: 00-13: 30, and 16: 30-17: 30, event A (internal meeting), event B (internal meeting), and event C (internal) Each meeting is registered.

  Since each registered event is an in-house meeting, there is a possibility that the user goes out of the office using the electric vehicle 100 between the first event (event A) and the last event (event C) of the day. Low. Therefore, the possibility that the electric vehicle 100 is used between the first event and the last event of the day is low. On the other hand, before the first event (event A), there is a high possibility that the electric vehicle 100 is used for going to work, and after the last event (event C), the electric vehicle 100 is used for returning home. There is a high possibility.

  Therefore, when the user uses the scheduler for away-site event management, the electric vehicle 100 is likely to be used before the first event and after the last event in the time schedule of the day. Therefore, in the data center 300, when the charging connector 410 is connected to the charging inlet 110 after returning home (after the last event), external charging is completed before the next sunrise shift (before the first event). A charging schedule is generated. Note that the user's commuting time (required time) is learned in the electric vehicle 100 based on the time when the charging connector 410 is removed from the charging inlet 110 and the user's schedule. The commuting time learning method will be described in detail later.

  FIG. 5 is a diagram illustrating an example in which the scheduler is used for general event management. Referring to FIG. 5, in this example, event A (children's pick-up) is registered at 9: 00-10: 00. It is assumed that the pick-up of the child involves the use of the electric vehicle 100. From 11:00 to 12:00, event B (lunch) is registered. It is assumed that lunch does not involve the use of the electric vehicle 100. From 15:00 to 16:30, event C (preparation for dinner) is registered. The preparation for dinner is accompanied by the use of the electric vehicle 100.

  In this case, whether or not the use of the electric vehicle 100 is involved is different for each registered event. Therefore, it is difficult to simply determine which event of the user's daily time schedule involves the use of the electric vehicle 100. In electrically powered vehicle 100 according to the first embodiment, ECU 170 is an event that accompanies the use of electrically powered vehicle 100 based on the position information of electrically powered vehicle 100 acquired through GPS module 160 and the user's schedule. To learn. A method of learning which event is an event involving the use of the electric vehicle 100 will be described in detail later.

  Therefore, when the scheduler is used for general event management, in the data center 300, external charging is performed for an event involving the use of the electric vehicle 100 learned by the electric vehicle 100 in the user's schedule. A charging schedule is generated so that is completed.

  Thus, in data center 300 according to the first embodiment, the charging schedule generation method is changed depending on what event time schedule is registered in the scheduler by the user. In the first embodiment, whether the scheduler is used for going-out event management or the scheduler is used for general event management is set in advance by the user. For example, the user notifies the data center 300 in advance which type of scheduler is used through the smartphone 500. The data center 300 determines a charging schedule generation method according to the setting contents from the user. Hereinafter, the procedure for generating the charging schedule will be described for each usage type of the scheduler by the user.

(Explanation of charging schedule automatic generation processing procedure)
FIG. 6 is a flowchart showing a charging schedule generation processing procedure when the scheduler is used for away-site event management. The process shown in this flowchart is executed by the controller 330 when an instruction for generating a charging schedule is received from the electric vehicle 100 through the communication module 310 when the scheduler is set for managing a destination event.

  With reference to FIG. 6, the controller 330 acquires a user's schedule from the scheduler managed on the internet through the communication module 310 (step S100). Thereafter, the controller 330 specifies the start time of the first event on the next day and the end time of the last event on the current day by referring to the acquired time schedule (step S110).

  Thereafter, the controller 330 reads information indicating the user's commuting time learned by the electric vehicle 100 from the storage device 320 (step S120). Information indicating the commuting time of the user is learned in the electric vehicle 100 and transmitted to the data center 300 every time it is updated. The commuting time learning method will be described in detail later.

  Thereafter, the controller 330 estimates the next sunrise departure scheduled time from the start time and commuting time of the first event of the next day, and further estimates the scheduled return time of the day from the end time and commuting time of the last event of the day ( Step S130). For example, the controller 330 estimates a time commuting from the start time of the first event the next day as a scheduled departure time of the next sunrise, and estimates a time when the commuting time has elapsed from the end time of the last event of the day as a scheduled return time of the day. To do.

  Thereafter, the controller 330 determines whether or not the current time has passed the estimated scheduled time to go home (step S140).

  If it is determined that the current time has passed the estimated return home time (YES in step S140), controller 330 is likely to have electric vehicle 100 at home. A charging schedule is generated that can complete external charging by a scheduled time and can reduce the electricity bill. Controller 330 transmits the generated charging schedule to electrically powered vehicle 100 through communication module 310 (step S150). Thereafter, the process proceeds to step S170.

  If it is determined that the estimated time to go home has not elapsed (NO in step S140), controller 330 transmits an instruction to immediately start external charging to electric vehicle 100 through communication module 310 (step S140). S160). If the estimated time to go home where the current time has not been estimated has passed, there is a high possibility that the electric vehicle 100 does not exist at home and the time during which the electric vehicle 100 is connected to the charging stand 200 is high. Because. Moreover, since the time connected to the charging stand 200 is short, there is almost no change in the electricity bill during connection, and it is difficult to obtain the advantage of timer charging. Thereafter, the process proceeds to step S170.

  As described above, in the data center 300 according to the first embodiment, the controller 330 extracts the time schedule of the event involving the use of the electric vehicle 100 (the time schedule of the first event of the day) from the user's schedule, In accordance with the extracted time schedule, a charging schedule (a charging schedule for completing external charging by the scheduled time of departure from the next sunrise) is set. Thereby, it can suppress that the external charge matched with the event which does not accompany the utilization of the electric vehicle 100 can be suppressed, and an appropriate external charge can be implement | achieved.

  FIG. 7 is a flowchart illustrating a procedure of commuting time learning processing. The process shown in this flowchart is executed by ECU 170 when charging connector 410 is removed from charging inlet 110 in electrically powered vehicle 100.

  Referring to FIG. 7, ECU 170 acquires time information when charging connector 410 is detached (step S200). Thereafter, ECU 170 acquires the user's schedule from the scheduler managed on the Internet through DCM 150 (step S210). Thereafter, the ECU 170 identifies the start time of the first event on the day by referring to the user's schedule (step S220).

  Thereafter, the ECU 170 performs a process of subtracting the time when the charging connector 410 is removed from the start time of the first event on the day, and estimates the calculated time as commuting time (step S230). Thereafter, ECU 170 stores the estimated commuting time in an internal memory (not shown) (step S240). ECU 170 updates the learned value of commuting time based on the estimated commuting time, and transmits the updated learned value to data center 300 through DCM 150 (step S250). For example, ECU 170 stores a history of estimated commuting time in an internal memory (not shown), and sets the average value of the stored history as a learned value for commuting time. Thereafter, the process proceeds to step S260.

  Thus, in electrically powered vehicle 100 according to the first embodiment, the user's commuting time is learned from the time when charging connector 410 is removed and the user's schedule, and the learning value updated each time the learning value is updated. Is transmitted to the data center 300. In the data center 300, as described above, the scheduled departure time of the next sunrise of the user is estimated using the commuting time, and a charging schedule that can complete external charging by the estimated next sunrise departure time is generated. .

  FIG. 8 is a flowchart showing a charging schedule generation processing procedure when the scheduler is used for general event management. The processing shown in this flowchart is executed by the controller 330 when receiving an instruction to generate a charging schedule from the electric vehicle 100 through the communication module 310 when the scheduler is set for general event management.

  With reference to FIG. 8, the controller 330 acquires a user's schedule from the scheduler managed on the internet through the communication module 310 (step S300). Thereafter, the controller 330 reads information for identifying an event associated with the use of the electric vehicle 100 (hereinafter also referred to as “vehicle use event information”) from the storage device 320 (step S310).

  The vehicle use event information is generated based on the learning result in the electric vehicle 100. The vehicle use event information is sequentially updated in the electric vehicle 100 and is transmitted to the data center 300 every time it is updated. The method for learning vehicle use event information will be described in detail later.

  Thereafter, the controller 330 specifies the start time and end time of an event that involves the use of the electric vehicle 100 among the events included in the user's schedule by referring to the vehicle use event information (step S320). When the user's schedule includes a plurality of events that involve the use of the electric vehicle 100, a plurality of pairs of start time and end time are specified.

  Thereafter, the controller 330 reads information indicating the travel time for each event learned by the electric vehicle 100 from the storage device 320 (step S330).

  The travel time for each event is learned from the time when the charging cable 400 is removed from the electric vehicle 100 and the start time of the event in the electric vehicle 100. For example, the time obtained by subtracting the time when the charging cable 400 was removed from the start time of the event is estimated as the travel time for the event. For each identical event, the travel time is estimated and the travel time learning value is updated. Each time the learning value is updated, the data center 300 receives the learning value from the electric vehicle 100. The received learning value (information indicating the movement time for each event) is stored in the storage device 320.

  In step S330, when the information indicating the travel time for each event is read, the controller 330 starts the scheduled start time and the scheduled home time from the start time and end time of the event that accompanies the use of the electric vehicle 100 and the travel time for each event. Is estimated (step S340). Specifically, the controller 330 estimates the time that is traveled back from the start time of the event involving the use of the electric vehicle 100 as the scheduled departure time, and the travel time has elapsed from the end time of the event involving the use of the electric vehicle 100. Estimate the time as the scheduled return time.

  Thereafter, the controller 330 determines whether or not the current time is a time between the estimated return home time and the next scheduled departure time (step S350).

  If it is determined that the current time is a time between the estimated scheduled return time and the next scheduled departure time (YES in step S350), controller 330 may have electric vehicle 100 at home. Since it is high, external charging can be completed by the estimated next scheduled departure time, and a charging schedule that can reduce the electricity bill is generated. Controller 330 transmits the generated charging schedule to electric vehicle 100 through communication module 310 (step S360). Thereafter, the process proceeds to step S380.

  If it is determined that the current time is not a time between the estimated scheduled return time and the next scheduled departure time (NO in step S350), controller 330 may not have electric vehicle 100 at home. Since it is high, an instruction to immediately start external charging is transmitted to the electric vehicle 100 through the communication module 310 (step S370).

  As described above, in the data center 300 according to the first embodiment, the controller 330 causes the time schedule of an event involving the use of the electric vehicle 100 from the user's schedule (in the electric vehicle 100 as an event involving the use of the electric vehicle 100). The time schedule of the learned event) is extracted, and a charging schedule (a charging schedule for completing external charging by the scheduled departure time for each event) is set according to the extracted time schedule. Thereby, it can suppress that the external charge matched with the event which does not accompany the utilization of the electric vehicle 100 can be suppressed, and an appropriate external charge can be implement | achieved.

  FIG. 9 is a flowchart showing a processing procedure for learning whether or not an event included in the user's schedule is an event involving the use of the electric vehicle 100. The process shown in this flowchart is executed by ECU 170 when the start time of an event included in the time schedule arrives in electrically powered vehicle 100 after the user's schedule is acquired.

  Referring to FIG. 9, ECU 170 refers to the output content of GPS module 160 to determine whether electric vehicle 100 is present at home (step S400). This determination process is continuously performed for a predetermined time. This is because the time when the use of the electric vehicle 100 is started may slightly deviate from the time schedule.

  If it is determined that electric vehicle 100 does not exist at home (NO in step S400), ECU 170 determines that there is a high possibility that the event for which the start time has arrived is an event involving the use of electric vehicle 100 ( Step S410). On the other hand, when it is determined that electric vehicle 100 is present at home (YES in step S400), ECU 170 determines that there is a high possibility that the event whose start time has arrived is an event that does not involve use of electric vehicle 100. (Step S420).

  Thereafter, ECU 170 updates the learning value based on the determination result regarding the event for which the start time has arrived, and transmits the updated learning value to data center 300 through DCM 150 (step S430). For example, when ECU 170 determines that events registered with the same event name in the scheduler are likely to be events accompanying the use of electric vehicle 100 at a ratio of a predetermined ratio or more, the ECU 170 uses the event name. A learning value indicating that the registered event is an event involving the use of the electric vehicle 100 is transmitted to the data center 300.

  Thus, in electrically powered vehicle 100 according to the first embodiment, it is learned whether each event included in the user's schedule is an event involving the use of electrically powered vehicle 100, and each time the learning value is updated. The updated learning value is transmitted to the data center 300. In the data center 300, an event involving the use of the electric vehicle 100 is specified based on the learning result, and a charging schedule is generated.

  As described above, in the data center 300 according to the first embodiment, the controller 330 extracts the time schedule of the event accompanied by the use of the electric vehicle 100 from the user's schedule and sets the charging schedule according to the extracted time schedule. To do. Thereby, it can suppress that the external charge matched with the event which does not accompany the utilization of the electric vehicle 100 can be suppressed, and an appropriate external charge can be implement | achieved.

[Other embodiments]
As described above, the first embodiment has been described as the embodiment of the present invention. However, the present invention is not necessarily limited to the first embodiment. Here, an example of another embodiment will be described.

  In the first embodiment, the charging schedule for automatic timer charging is generated in the data center 300. However, the charge schedule generation entity is not necessarily limited to this example. For example, in electric vehicle 100, a charging schedule for automatic timer charging may be generated. In this case, in electric powered vehicle 100, the time schedule of the event accompanied by the use of electric powered vehicle 100 is extracted from the user's schedule, and ECU 170 generates a charging schedule according to the extracted time schedule.

  In the first embodiment, the user's schedule is acquired from the scheduler managed on the Internet. However, the scheduler is not necessarily limited to this example. For example, the user's schedule may be acquired from a scheduler provided in the smartphone 500. In this case, when a charging schedule is generated in the data center 300, the data center 300 receives the user's schedule from the smartphone 500. In the data center 300, a charging schedule is generated based on the received time schedule. When the charging schedule is generated in the electric vehicle 100, the electric vehicle 100 receives the user's schedule from the smartphone 500. Electric vehicle 100 generates a charging schedule based on the received time schedule.

  In the first embodiment, the user himself / herself sets what event the user registers in the scheduler. Therefore, in the data center 300, it is determined what event is registered in the scheduler according to the setting contents of the user. However, the determination method of what event the user has registered in the scheduler is not limited to this. For example, in the data center 300 or the electric vehicle 100, the usage pattern of the scheduler by the user is learned, and it is automatically determined whether the user is the type used for the event management on the go or the general event management. You may do it.

  In the first embodiment, the user's commuting time and travel time are learned from the time when the charging connector 410 is removed from the charging inlet 110 and the user's schedule. However, the method of learning commuting time and travel time is not limited to this. For example, the ECU 170 may estimate the commuting time and travel time by learning the distance between two points from the current location (for example, home location) of the electric vehicle 100 and the event venue.

  Further, in the first embodiment, an event registered in the scheduler as an event having the same name as an event associated with the use of electric vehicle 100 is determined as an event involving the use of electric vehicle 100. . However, the method for determining whether or not the event involves the use of the electric vehicle 100 is not limited to this. For example, an event that is held at the same place as an event that involves the use of the electric vehicle 100 and a learned event may be determined as an event that involves the use of the electric vehicle 100, An event held on the same day and time as the learned event may be determined as an event involving the use of the electric vehicle 100.

  Further, in the first embodiment, when the scheduler is used for going-out event management, the controller 330 estimates the time commuting time retroactive from the start time of the first event of the next day as the next sunrise departure scheduled time, An example has been described in which the time when the commuting time has elapsed from the end time of the last event of the day is estimated as the scheduled return time of the day. However, the method for estimating the scheduled departure time and the scheduled return time is not limited to this. For example, a time that is a predetermined time earlier than the time that is commuting time from the start time of the first event the next day is estimated as the scheduled departure time for the next sunrise, and a time that is a predetermined time later than the time that the commuting time has elapsed from the end time of the last event of the day It may be estimated that the scheduled return time.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  DESCRIPTION OF SYMBOLS 1 External charging system, 100 Electric vehicle, 110 Charging inlet, 120 Power storage device, 130 Charger, 140 PCU, 150 DCM, 160 GPS module, 170 ECU, 200 Charging stand, 300 Data center, 310 Communication module, 320 Storage device, 330 controller, 400 charging cable, 410 charging connector, 500 smartphone.

Claims (1)

A charging control device for executing charging of a power storage device mounted on a vehicle by a power source outside the vehicle,
An acquisition unit for acquiring a schedule of a user of the vehicle from a scheduler capable of managing a time schedule of the event involving the use of the vehicle and a time schedule of the event not involving the use of the vehicle;
A charge control device comprising: a control device that extracts a time schedule of an event that accompanies use of the vehicle from the acquired user schedule and sets the time schedule of the charging according to the extracted time schedule.

Images