Electric vehicle, control method for electric vehicle, and control device for electric vehicle

Abstract

The present application relates to an electric vehicle, a control method of an electric vehicle, and a control device of an electric vehicle. An ECU performs a process including: when an OTA request exists (Yes in S100), a step of acquiring an ECU of an OTA target (S102); when the target ECU is an ECU that operates in running (Yes in S104), when external charging is in progress (Yes in S106), a step of requesting execution of an update process to the target ECU (S108); when the target ECU is an ECU that operates in external charging (No in S104 and Yes in S110), when the electric vehicle is in running (Yes in S112), a step of requesting execution of an update process to the target ECU (S114).

Description

TECHNICAL FIELD

[0001] The present application relates to an update of control programs of a plurality of control devices mounted on an electric vehicle. BACKGROUND

[0002] A plurality of control devices that control the operation of various electric power equipment mounted on an electric vehicle are mounted on the electric vehicle. In a case where any one of the control programs of the plurality of control devices is updated, in addition to being implemented using data transmitted by wire, the update is sometimes performed using update information received by wireless communication from a server outside the electric vehicle, so-called OTA (Over The Air) technology. In the update of the control program using such OTA technology, it is required that the power supply to the control device that is the object of the update not be stopped.

[0003] For example, in Japanese Patent Application Publication No. 2013-151222, a technology is disclosed.

[0004] In this technology, in a case where it is determined that the power supply voltage of an auxiliary battery of a vehicle is a prescribed value or less, the power supply from the auxiliary battery to a power supply other than the device associated with the update of the charge control program is prohibited. SUMMARY

[0005] However, in a case where the update of the control programs of a plurality of control devices is required, when the update of the control programs is implemented in parallel in the plurality of control devices, the consumed power at the time of the update sometimes increases. Further, in a case where a long time is required for the update of the control programs, the period for the update sometimes cannot be secured, and the reduction of the charge amount of the auxiliary battery has to be suppressed.

[0006] An object of the present application is to provide an electric vehicle, a control method of an electric vehicle, and a control device of an electric vehicle that can suppress an increase in the consumed power at the time of the update of the control programs of a plurality of control devices mounted on the electric vehicle, and can secure the period for the update.

[0007] One embodiment of the present application is an electric vehicle including: an electrical storage device that is chargeable using a power supply external to the vehicle; a drive motor that drives the vehicle using electric power from the electrical storage device; a reception device that receives predetermined information from outside the vehicle; and a control system configured by a plurality of control devices including a first control device and a second control device. The first control device controls a device that is a control target in charging of the electrical storage device using the power supply external to the vehicle, using a first control program. The second control device controls a device that is a control target in running of the vehicle using the drive motor, using a second control program. The control system updates the first control program using update information of the first control program received by the reception device, during running. The control system updates the second control program using update information of the second control program received by the reception device, during charging.

[0008] In this way, by updating the first control program of the first control device during running and updating the second control program of the second control device during charging, a period for updating can be secured. Further, by performing the update of the first control program and the update of the second control program in different periods, as compared with a case where the first control program and the second control program are updated in parallel, an increase in consumed power at the time of updating can be suppressed.

[0009] In one embodiment, the plurality of control devices further includes a third control device that controls a device that is a control target in each of charging and running, using a third control program. The control system updates the third control program using update information of the third control program received by the reception device, during stop of the vehicle.

[0010] In this way, the third control program of the third control device that operates during charging and running is updated during stop of the vehicle, so a period for updating can be secured. Further, by performing the update of the third control program in a period different from the update of the first control program and the update of the second control program, as compared with a case where the first control program to the third control program are updated in parallel, an increase in consumed power at the time of updating can be suppressed.

[0011] In a further embodiment, the electric vehicle further includes an auxiliary battery that supplies electric power to the third control device. The control system charges the auxiliary battery during at least either of charging and running, when update information of the third control program is received by the reception device. The control system updates the third control program using the update information, when a state of charge of the auxiliary battery during stop is equal to or higher than a threshold value at which the update of the third control program is possible.

[0012] In this way, in the stop of the vehicle, the power of the auxiliary battery does not become insufficient, and the third control program can be updated.

[0013] Further, in a further embodiment, when the receiving device receives the update information of the first control program, in a case where the distance that can be traveled due to an increase in the amount of power consumption accompanying the update of the first control program becomes shorter than the distance to the destination of the vehicle, the control system does not update the first control program during travel.

[0014] In this way, when power is consumed accompanying the update of the first control program, the first control program is not updated during travel when the destination of the vehicle cannot be reached, and thus the vehicle can reach the destination.

[0015] Further, in a further embodiment, when the receiving device receives the update information of the second control program, in a case where the charging of the electric storage device cannot be completed by the departure time due to an increase in the amount of power consumption accompanying the update of the second control program, the control system does not update the second control program during charging.

[0016] In this way, when power is consumed accompanying the update of the second control program, the second control program is not updated during charging when the charging of the electric storage device cannot be completed by the departure time, and thus the charging of the electric storage device can be completed by the departure time.

[0017] Another aspect of the present application is a control method for an electric vehicle having: an electric storage device that can be charged using a power source external to the vehicle; a drive motor that drives the vehicle using power from the electric storage device; a receiving device that receives predetermined information from outside the vehicle; and a control system configured by a plurality of control devices including a first control device and a second control device. The first control device controls a device that is a control target during charging of the electric storage device using the external power source using a first control program. The second control device controls a device that is a control target during travel of the vehicle using the drive motor using a second control program. The control method includes: a step of updating the first control program using the update information using the receiving device in a case where the receiving device receives update information of the first control program; and a step of updating the second control program using the update information using the receiving device in a case where the receiving device receives update information of the second control program.

[0018] Another aspect of the application is a control device of an electric vehicle including: an electric storage device that is chargeable using a power supply external to the vehicle; a drive motor that drives the vehicle using electric power of the electric storage device; and a reception device that receives predetermined information from outside the vehicle. The control device is configured to be able to communicate with a first control device that controls a device that is a control target in charging of the electric storage device using the external power supply using a first control program, and a second control device that controls a device that is a control target in running of the vehicle using the drive motor using a second control program. The control device requests the first control device to update the first control program using update information in running when the update information is received using the reception device. The control device requests the second control device to update the second control program using update information in charging when the update information is received using the reception device.

[0019] The above and other objects, features, aspects and advantages of the present application will become more apparent from the following detailed description of the application when taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0020] Figure 1 is a diagram for explaining an example of a structure of a management server and a plurality of electric vehicles capable of communicating with the management server.

[0021] Figure 2 is a diagram that schematically shows an example of a structure of an electric vehicle of the embodiment.

[0022] Figure 3 is a flowchart showing an example of processing executed by an update ECU.

[0023] Figure 4 is a timing chart showing an example of an operation of the update ECU.

[0024] Figure 5 is a flowchart showing an example of processing executed by the update ECU in the modified example.

[0025] Figure 6 is a flowchart showing another example of processing executed by the update ECU in the modified example.

[0026] Figure 7 is a flowchart showing still another example of processing executed by the update ECU in the modified example. DETAILED DESCRIPTION

[0027] Hereinafter, an embodiment of the application will be described in detail with reference to the accompanying drawings. In addition, the same or corresponding portions will be denoted by the same reference symbols, and a description thereof will not be repeated.

[0028] Figure 1 is a diagram for explaining an example of a configuration of the management server 10 and a plurality of electric vehicles 1, 2, 3, 4 (hereinafter, referred to as "1 to 4") capable of communicating with the management server 10.

[0029] As shown in Figure 1 , the management server 10 is configured to be capable of mutually communicating with a plurality of electric vehicles including the electric vehicles 1 to 4 via a base station 7 provided on a communication network 6. In the management server 10, identification information for identifying the electric vehicles 1 to 4 is stored in advance. The identification information is inherent information set for each vehicle. In the management server 10, version information, revision information, and update history of each of various control programs of the electric vehicles 1 to 4 are also stored in association with the above-mentioned identification information. The management server 10 manages an update status of the various control programs used in the operation of the electric vehicles 1 to 4, and when a new version of a control program of at least any one of a plurality of control programs is prepared, requests an update of the control program to a target vehicle among the electric vehicles 1 to 4.

[0030] The management server 10 is a computer including a control device 11, a storage device 12, and a communication device 13. The control device 11, the storage device 12, and the communication device 13 are communicably connected to each other via a communication bus 14.

[0031] The storage device 12 stores a management list including the identification information of the electric vehicles 1 to 4, and the above-mentioned update status in association with the identification information. As the management list, other information (update date and time, update status of each control program, and the like) in association with the identification information can be further included. The communication device 13 realizes bidirectional communication between the control device 11 and the communication network 6.

[0032] The control device 11, not shown, is configured to include a CPU (Central Processing Unit), a memory (ROM (Read Only Memory) and RAM (Random Access Memory), and the like), and an input / output port or the like for inputting and outputting various signals. Various controls performed by the control device 11 are performed by software processing, that is, by the CPU reading out a program stored in the memory. The various controls based on the control device 11 can also be realized by a general-purpose server (not shown) executing a program stored in a storage medium. However, the various controls based on the control device 11 are not limited to software processing, and can be processed by a dedicated hardware (electronic circuit).

[0033] Further, the management server 10 described above is described taking the example of managing four electric vehicles 1 to 4, but the number of electric vehicles to be managed is not particularly limited to four, and can be three or less, or five or more.

[0034] Next, the detailed structure of the electric vehicle 1 of the present embodiment will be described. Further, the electric vehicles 2 to 4 have the same structure as the electric vehicle 1 in principle, and thus detailed description of these structures will not be repeated.

[0035] Figure 2 is a diagram schematically showing an example of the structure of the electric vehicle 1 of the present embodiment. Referring to Figure 2 , the electric vehicle 1 includes a power storage device 20, a system main relay (SMR) 21, a power control unit (PCU) 22, a DC / DC converter 40, an auxiliary battery 50, a motor generator (hereinafter, referred to as MG) 62, a power transmission gear 65, a drive wheel 66, and a control system 90.

[0036] The power storage device 20 is a direct current power source that can be recharged, and is configured to include, for example, a secondary battery such as a nickel-hydrogen battery or a lithium-ion battery with a liquid or solid electrolyte. As the power storage device 20, a double-layer capacitor or the like can also be used. The power storage device 20 supplies power for generating a travel driving force of the electric vehicle 1 to the PCU 22. Further, the power storage device 20 is charged by power generated by a regenerative operation of the MG 62, discharged by a driving operation of the MG 62, charged by power supplied from the outside of the vehicle, and discharged by supply of power to the outside of the vehicle.

[0037] The SMR 21 is electrically connected between the power storage device 20 and the PCU 22. The closing / opening of the SMR 21 is controlled according to an instruction from an HV-ECU (Electronic Control Unit) 100 of the control system 90.

[0038] The PCU 22 performs power conversion between the power storage device 20 and the MG 62 according to an instruction from the HV-ECU 100 of the control system 90. The PCU 22 is configured to include an inverter that receives power from the power storage device 20 to drive the MG 62, a converter that adjusts the level of a direct current voltage supplied to the inverter, and the like (none of which is shown).

[0039] The MG 62 is a three-phase alternating current rotating electric machine, and is, for example, a permanent magnet type synchronous electric machine provided with a rotor in which a permanent magnet is embedded. The MG 62 has both a function as an electric machine (motor) and a function as a generator (generator). The MG 62 is connected to the power storage device 20 via the PCU 22.

[0040] The MG 62 is driven by a converter included in the PCU 22, for example, at the time of running of the electric vehicle 1. The power of the MG 62 is transmitted to the drive wheels 66 via the power transmission gear 65. In addition, the MG 62 is driven by the drive wheels 66, for example, at the time of braking of the electric vehicle 1, and the MG 62 operates as a generator to perform regenerative braking. The electric power generated by the MG 62 is stored in the electric storage device 20 via the PCU 22.

[0041] The electric vehicle 1 has a charging relay 26, a charging device 27, and an inlet 28 as a structure for implementing charging using an external alternating-current power supply 15 outside the electric vehicle 1 (hereinafter, sometimes referred to as external charging). In the inlet 28, a connector 32 is connected. The connector 32 is connected to the charging station 53 via a cable 31. In the electric vehicle 1, the connector 32 is connected to the inlet 28 via the cable 31. The connector 32 is connected to the inlet 28 via the cable 31. Figure 2 In the electric vehicle 1, the state in which the connector 32 is attached to the inlet 28 is shown. The connector 32 is configured to be attached to and detached from the inlet 28, and in the case of performing external charging, the connector 32 is attached to the inlet 28, and in the case of driving the electric vehicle 1, the connector 32 is detached from the inlet 28. The alternating-current electric power from the alternating-current power supply 15 is supplied to the charging station 53, and by attaching the connector 32 to the inlet 28, a state in which the alternating-current electric power can be supplied from the charging station 53 to the electric vehicle 1 is achieved.

[0042] In the external charging of the electric storage device 20, electric power is supplied from the charging station 53 side via the cable 31, the connector 32, and the inlet 28. The electric power supplied from the charging station 53 side is converted into electric power that can perform charging of the electric storage device 20 (hereinafter, referred to as charging electric power) in the charging device 27, and the converted charging electric power is supplied to the electric storage device 20.

[0043] The charging relay 26 is electrically connected between the electric storage device 20 and the charging device 27. When the charging relay 26 is closed and the SMR 21 is closed, a state in which electric power transmission between the inlet 28 and the electric storage device 20 is possible is achieved.

[0044] The charging device 27 is electrically connected between the charging relay 26 and the inlet 28. The charging device 27 converts the electric power supplied from the charging station 53 (for example, alternating-current electric power of AC 100 V) into charging electric power (direct-current electric power) according to an instruction from the HV-ECU 100 of the control system 90.

[0045] The DC / DC converter 40 is electrically connected between the SMR 21 and the charging device 27. Therefore, when the SMR 21 is closed, a state in which electric power can be supplied from the electric storage device 20 to the DC / DC converter 40 is established. The DC / DC converter 40 steps down the high-voltage direct-current voltage of the electric storage device 20 to a low-voltage direct-current voltage according to an instruction from the battery ECU 130 of the control system 90. The stepped-down low-voltage direct-current voltage is supplied to an auxiliary equipment load (not shown) and to the auxiliary battery 50. Thereby, the auxiliary battery 50 is charged.

[0046] The auxiliary battery 50 is a secondary battery such as a lead storage battery, and is capable of charging and discharging at a low-voltage direct-current voltage (for example, electric power of about 12 V) at which the auxiliary load can operate. For example, a voltage sensor 52 for detecting the output voltage of the auxiliary battery 50 is provided on a power line connected between a terminal portion of the auxiliary battery 50 or the DC / DC converter 40. The voltage sensor 52 transmits a signal indicating the detected output voltage of the auxiliary battery 50 to the battery ECU 130.

[0047] In the present embodiment, the control system 90 includes a plurality of control devices. Specifically, the control system 90 includes an HV-ECU 100, a charging ECU 110, a battery ECU 130, an instrument ECU 140, and an update ECU 150.

[0048] The HV-ECU 100 is configured including a CPU 102, a memory 104, and an input / output port (not shown) for inputting and outputting various signals. The HV-ECU 100 controls the SMR 21 and the PCU 22 in the electric vehicle 1 so that the electric vehicle 1 becomes a desired running state. Various controls performed by the HV-ECU 100 are performed by software processing, that is, by the CPU 102 reading out a control program stored in the memory 104.

[0049] On the HV-ECU 100, a wheel speed sensor 67 is connected. The wheel speed sensor 67 detects the rotational speed (wheel speed) V of the drive wheel 66 and transmits a signal indicating the detected wheel speed V to the HV-ECU 100. The HV-ECU 100 uses the detected wheel speed V to calculate the speed (hereinafter, also referred to as vehicle speed) of the electric vehicle 1.

[0050] The charging ECU 110 is configured with a CPU 112, a memory 114, and an input / output port (not shown) for inputting and outputting various signals, and the like. The charging ECU 110 controls the charging relay 26 and the charging device 27 in the electric vehicle 1 to make the electric vehicle 1 in a stop state to be able to perform external charging using the charging station 53. Various controls performed by the charging ECU 110 are performed by software processing, that is, by the CPU 112 reading out a control program stored in the memory 114.

[0051] The battery ECU 130 is configured with a CPU 132, a memory 134, and an input / output port (not shown) for inputting and outputting various signals. The battery ECU 130 acquires information on the state of the electrical storage device 20, and uses the acquired information to calculate the SOC (State Of Charge) of the electrical storage device 20, and controls the DC / DC converter 40 to charge the auxiliary battery 50. Various processes performed by the battery ECU 130 are performed by software processing, that is, by the CPU 132 reading out a control program stored in the memory 134.

[0052] In the electrical storage device 20, for example, a voltage sensor 136, a current sensor 137, and a temperature sensor 138 are provided. In the battery ECU 130, the voltage sensor 136, the current sensor 137, and the temperature sensor 138 are connected.

[0053] The voltage sensor 136 detects the voltage VB of the electrical storage device 20, and transmits a signal indicating the detected voltage VB to the battery ECU 130. The current sensor 137 detects the current IB of the electrical storage device 20, and transmits a signal indicating the detected current IB to the battery ECU 130. Further, the temperature sensor 138 detects the temperature TB of the electrical storage device 20, and transmits a signal indicating the detected temperature TB to the battery ECU 130.

[0054] The battery ECU 130 calculates the SOC indicating the remaining capacity of the electrical storage device 20, for example, based on the detection results of the voltage sensor 136, the current sensor 137, and the temperature sensor 138. The SOC is a percentage indicating the proportion of the current charge amount with respect to the charge amount of the full charge state of the electrical storage device 20. Further, as a method of calculating the SOC, various known methods such as a method based on current value integration (coulomb counting), or a method based on estimation of open circuit voltage (OCV: Open Circuit Voltage), or the like can be employed.

[0055] Further, in the battery ECU 130, a voltage sensor 52 for detecting the voltage of the auxiliary battery 50 is connected. The voltage sensor 52 transmits a signal indicating the voltage of the auxiliary battery to the battery ECU 130.

[0056] The instrument ECU 140 is configured including a CPU 142, a memory 144, and an input / output port (not shown) for inputting and outputting various signals, and the like. The instrument ECU 140 performs display control of displaying prescribed information in a display device (for example, various instruments such as a speedometer, a distance meter, and the like, which are disposed at a position where a driver seated on a driver's seat can visually recognize, and a display device that displays a warning lamp) in a cabin of the electric vehicle 1. Various controls performed by the instrument ECU 140 are performed by software processing, that is, by the CPU 142 reading out a control program stored in the memory 144.

[0057] The update ECU 150 is configured including a CPU 152, a memory 154, a communication device 156, and an input / output port (not shown) for inputting and outputting various signals, and the like. The update ECU 150 transmits update information of a control program to at least any one of the HV-ECU 100, the charging ECU 110, the battery ECU 130, and the instrument ECU 140, and performs processing of requesting an update of the control program.

[0058] The communication device 156 is configured so as to be able to communicate with a device outside the electric vehicle 1. Specifically, the communication device 156 is configured so as to be able to communicate with the above-described management server 10 via a communication network 6 and a base station 7. The communication network 6 is configured by, for example, the Internet or the like. The base station 7 and the communication device 156 can be communicably connected through a portable telephone line (for example, 4G or 5G), or can also be connected through wireless communication such as Wifi.

[0059] The update ECU 150 performs processing of requesting execution of an update process, so as to cause the update process to be executed in each ECU. Various processes performed by the update ECU 150 are performed by software processing, that is, by the CPU 152 reading out a program stored in the memory 154. Various processes performed by the update ECU 150 are not limited to software processing, and can also be performed using a dedicated hardware (electronic circuit).

[0060] The update ECU 150, for example, when receiving, using the communication device 156, differential data for update from the management server 10 and information related to an ECU that is an update target, transmits information indicating a request for execution of an update process, and the differential data for update as update information to the ECU that is the update target. The ECU that is the update target, when receiving the update information from the update ECU 150, performs an update process of updating a control program stored in a memory using the differential data for update included in the received update information. In the execution of such an update process, it is required that power supply to the control system 90 is not stopped.

[0061] However, in a case where update of control programs of a plurality of control devices is required, when the update of the control programs is performed in parallel in the plurality of control devices, there is a case where consumed power at the time of the update increases. Further, in a case where the update of the control programs takes a long time, a period for the update cannot be secured, and the reduction of the charge amount of the auxiliary battery 50 cannot be suppressed while the update is performed.

[0062] Therefore, in the present embodiment, the control system 90 updates the first control program using the update information in the running in a case where the update information of the first control program of the ECU that operates in the external charging using the communication device 156 is received. Further, the control system 90 updates the second control program using the update information in the external charging in a case where the update information of the second control program of the ECU that operates in the running of the electric vehicle 1 using the MG 62 using the communication device 156 is received.

[0063] In this way, by updating the first control program in the running and updating the second control program in the external charging, a period for the update can be secured. Further, by performing the update of the first control program and the update of the second control program in different periods, compared to a case where the first control program and the second control program are updated in parallel, the increase of the consumed power at the time of the update can be suppressed.

[0064] In the present embodiment, the update ECU 150 that adopts the control system 90 becomes the main body and executes the process for updating the first control program and the second control program.

[0065] Hereinafter, an example of the process executed by the update ECU 150 will be described with reference to Figure 3 . Figure 3 is a flowchart showing an example of the process executed by the update ECU 150. The series of processes shown in the flowchart are repeatedly executed at each predetermined control cycle.

[0066] In step (hereinafter, the step will be described as S) 100, the update ECU 150 determines whether there is an OTA request. The update ECU 150 determines that there is an OTA request, for example, in a case where an indicator indicating that there is an OTA request is in an ON state. The update ECU 150 sets the indicator indicating that there is an OTA request to the ON state, for example, in a case where the update information for updating the control program of any one of the plurality of ECUs mounted on the electric vehicle 1 is received from the management server 10 using the communication device 156. In a case where it is determined that there is an OTA request (YES in S100), the process shifts to S 102.

[0067] In S102, the update ECU 150 acquires the ECU that is the target of the OTA request (hereinafter, sometimes referred to as the OTA target ECU). The management server 10 includes identification information for identifying the OTA target ECU in the update information in a case where the update information of the control program is transmitted. The update ECU 150 acquires the OTA target ECU using the identification information included in the update information received from the management server 10, for example.

[0068] In S104, the update ECU 150 determines whether the OTA target ECU is an ECU that acts in running. The ECU that acts in running includes the HV-ECU 100 and the meter ECU 140, for example. In a case where it is determined that the OTA target ECU is an ECU that acts in running (YES in S104), the process shifts to S106.

[0069] In S106, the update ECU 150 determines whether external charging is in progress. The update ECU 150 determines that external charging is in progress, for example, in a case where the connector 32 is mounted to the inlet 28, the charging device 27 is operating, or the charging power is supplied from the charging device 27 to the electric storage device 20. In a case where it is determined that external charging is in progress (YES in S106), the process shifts to S108.

[0070] In S108, the update ECU 150 requests the target ECU to execute the update process. That is, the update ECU 150 transmits the update information to the OTA target ECU among the HV-ECU 100 and the meter ECU 140, and requests execution of the update process of the control program. The OTA target ECU updates the control program stored in the memory of the OTA target ECU using the differential data included in the update information when the update information is received from the update ECU 150. In addition, as the update method of the control program, a publicly known method can be used, and detailed description will not be given here. The OTA target ECU transmits information indicating completion of the update process to the update ECU 150 when the update process is completed. The update ECU 150 sets the flag indicating that the OTA request exists to the OFF state when the information is received.

[0071] On the other hand, in a case where it is determined that the OTA target ECU is not an ECU that acts in running (NO in S104), the process shifts to S110.

[0072] In S110, the update ECU 150 determines whether the ECU targeted by the OTA is an ECU that operates in external charging. The ECU that operates in external charging includes, for example, the charging ECU 110. In a case where it is determined that the ECU targeted by the OTA is an ECU that operates in external charging (YES in S110), the process shifts to S112.

[0073] In S112, the update ECU 150 determines whether the electric vehicle 1 is in running. For example, the update ECU 150 determines that the electric vehicle 1 is in running in a case where the vehicle speed is higher than a threshold value. The threshold value is a predetermined value for determining whether the electric vehicle 1 is in running, and is adjusted through experiments or the like. In a case where it is determined that the electric vehicle 1 is in running (YES in S112), the process shifts to S114.

[0074] In S114, the update ECU 150 requests the targeted ECU to execute the update process. That is, the update ECU 150 transmits the update information to the charging ECU 110, and requests execution of the update process of the control program. The charging ECU 110 updates the control program stored in the memory 114 of the charging ECU 110 using the differential data included in the update information upon reception of the update information from the update ECU 150. The charging ECU 110 transmits information indicating completion of the update process to the update ECU 150 upon completion of the update process. The update ECU 150 sets the flag indicating the presence of the OTA request to the OFF state upon reception of the information.

[0075] On the other hand, in a case where it is determined that the ECU targeted by the OTA is not an ECU that operates in external charging (NO in S110), the process shifts to S116.

[0076] In S116, the update ECU 150 determines whether the electric vehicle 1 is in stopping. The update ECU 150 determines that the electric vehicle 1 is in stopping, for example, in a case where the vehicle speed is below a threshold value and the connector 32 is not connected to the inlet 28. In a case where it is determined that the electric vehicle 1 is in stopping (YES in S116), the process shifts to S118.

[0077] In S118, the update ECU 150 requests the object ECU to execute the update processing. The ECU of the OTA object in this case is an ECU that acts in both the running and the external charging, such as the battery ECU 130. That is, the update ECU 150 transmits the update information to the battery ECU 130, requesting execution of the update processing of the control program. The battery ECU 130, upon receiving the update information from the update ECU 150, updates the control program stored in the memory 134 of the battery ECU 130 using the differential data contained in the update information. The battery ECU 130, upon completion of the update processing, transmits information indicating completion of the update processing to the update ECU 150. The update ECU 150, upon receiving this information, sets the flag indicating the presence of the OTA request to the OFF state.

[0078] Further, in the case where it is determined that the OTA request is not present (NO in S100), it is determined that it is not in the external charging (NO in S106), it is determined that it is not in the running (NO in S112), and it is determined that it is not in the stop (NO in S116), the processing ends.

[0079] Reference Signs Figure 4 An example of the action of the update ECU 150 in the present embodiment based on the above structure and the flowchart will be described. Figure 4 is a timing chart indicating an example of the action of the update ECU 150. Figure 4 The vertical axis of indicates the operating state of the electric vehicle 1, the presence or absence of execution of the update processing of the HV-ECU 100, the presence or absence of execution of the update processing of the charging ECU 110, and the presence or absence of execution of the update processing of the battery ECU 130. Figure 4 The horizontal axis of indicates time. Further, Figure 4 LN1 of indicates a change in the operating state of the electric vehicle 1. Figure 4 LN2 in indicates a change in the presence or absence of execution of the update processing of the HV-ECU 100. Figure 4 LN3 (dotted line) of indicates the presence or absence of execution of the update processing of the charging ECU 110 in the case where the charging ECU 110 is the ECU of the OTA object. Figure 4 LN4 (dot-dash line) in indicates the presence or absence of execution of the update processing of the battery ECU 130 in the case where the battery ECU 130 is the ECU of the OTA object.

[0080] Suppose, for example, that the update information of the control program of the HV-ECU 100 is received at time T(0). In this case, the flag indicating the presence of the OTA request becomes the ON state, and thus it is determined that the OTA request is present (YES in S100).

[0081] When the identification information included in the update information is used to obtain the ECU that is the OTA target as HV-ECU 100 (S102), the ECU that is the OTA target, namely HV-ECU 100, is the ECU that is operating while driving (in S104), so it is determined whether it is in the process of external charging (S106).

[0082] Therefore, as Figure 4 As shown in LN1, before time T(5), the electric vehicle 1 is not in the external charging state, therefore the execution of the HV-ECU 100 update process is not requested. On the other hand, when the electric vehicle 1 is in the external charging state at time T(5) (yes in S106), the HV-ECU 100 is requested to execute the update process (S108). Therefore, as Figure 4 As shown in LN2, during the period from time T(5) to time T(6), an update process is performed in HV-ECU 100. When the update process ends at time T(6), the flag indicating the existence of an OTA request is set to OFF.

[0083] Next, suppose that, for example, the control program of the charging ECU 110 receives update information at time T(0). In this case, the flag indicating the existence of an OTA request becomes ON, so it is determined that an OTA request exists (yes in S100).

[0084] When the ECU to be OTA is obtained as the charging ECU 110 using the identification information included in the update information (S102), the ECU to be OTA, namely the charging ECU 110, is the ECU that is operating in external charging (no in S104 and yes in S110), so it is determined whether the electric vehicle 1 is in motion (S112).

[0085] Therefore, as Figure 4 As shown in LN1, before time T(2), the electric vehicle 1 is not in a driving state, so no update processing is requested from the charging ECU 110. On the other hand, when the electric vehicle 1 is in a driving state at time T(2) (S112 is yes), an update processing is requested from the charging ECU 110 (S114).

[0086] Therefore, as Figure 4 As shown by LN3 (dashed line), during the period from time T(2) to time T(3), an update process is performed in the charging ECU 110. At time T(3), when the update process is completed, the flag indicating the existence of an OTA request is set to OFF.

[0087] Next, suppose that, for example, update information of the control program of the battery ECU 130 is received at time T(0). In this case, the flag indicating the existence of an OTA request becomes ON, and therefore it is determined that an OTA request exists (yes in S100).

[0088] Using the identification information included in the update information, the ECU to be OTA is identified as battery ECU 130 (S102).

[0089] The battery ECU 130, which is the ECU to be OTA-targeted, is neither an ECU that operates during external charging nor an ECU that operates while driving (no in S104 and no in S110), therefore it is determined whether the electric vehicle 1 is stopped (S116).

[0090] Therefore, as Figure 5 As shown in LN1, when the time T(0) and the operating state is stopped (yes in S116), the battery ECU 130 is requested to perform an update process (S118).

[0091] Therefore, as Figure 5 As shown in LN4 (dotted line), an update process is performed in the battery ECU130 during the period from time T(0) to time T(1). When the update process is completed at time T(1), the flag indicating that an OTA request exists is set to OFF.

[0092] As described above, in the electric vehicle according to this embodiment, by updating the control program of the charging ECU 110, which operates during external charging, while driving, and updating the control programs of the HV-ECU 100 and the instrument ECU 140, which operate during driving, while external charging, the period for updating can be ensured. Furthermore, by performing updates to the control programs of the charging ECU 110 and the HV-ECU 100 and the instrument ECU 140 at different times, the increase in power consumption during updates can be suppressed compared to updating these control programs in parallel. Therefore, an electric vehicle, an electric vehicle control method, and an electric vehicle control device can be provided that can suppress the increase in power consumption during updates of the control programs of multiple control devices mounted on the electric vehicle, while simultaneously ensuring the update period.

[0093] Further, the control program of the battery ECU 130 that operates in the external charging and in the running is updated in the stop of the electric vehicle 1, and thus a period for the update can be secured. Further, by implementing the update of the control program of the battery ECU 130 in a period different from the update of the control program of the charging ECU 110 and the update of the control program of the HV-ECU 100, the instrument ECU 140, compared to the case where these control programs are updated in parallel, it is possible to suppress an increase in the consumption power at the time of the update.

[0094] Hereinafter, a modification example is described.

[0095] In the above-described embodiment, in the case where the ECU that is the target of the OTA is an ECU that operates in the charging, the case where the target ECU is requested to execute the update processing at the time of the running is described, but for example, the target ECU can be requested to execute the update processing not only at the time of the running but also at the time when the consumption power is increased due to the update processing but the electric vehicle 1 is also able to reach the destination.

[0096] Hereinafter, with reference to Figure 5 One example of the control processing executed by the update ECU 150 in the modification example is described. Figure 3 is a flowchart that shows one example of the processing executed by the update ECU 150 in the modification example. The series of processing shown in this flowchart is repeatedly executed in each predetermined control period.

[0097] Figure 6 The processing of S100, S102, S104, S106, S108, S110, S112, S114, S116, and S118 (hereinafter, described as "S100 to S118") described in the flowchart shown in FIG. 10 are the same processing contents as the processing of S100 to S118 described in the flowchart shown in FIG. 8, respectively, except for the following described cases. Therefore, the detailed description thereof is not repeated. Figure 6 The processing of S100 to S118 described in the flowchart shown in FIG. 10 is the same processing contents as the processing of S100 to S118 described in the flowchart shown in FIG. 8, respectively, except for the following described cases. Therefore, the detailed description thereof is not repeated.

[0098] In the case where it is determined that the electric vehicle 1 is running (Yes in S112), the processing is shifted to S200.

[0099] In S200, the update ECU 150 calculates a reduction amount of the EV travel distance based on the update processing. The EV travel distance indicates a travel distance of the electric vehicle 1 using the MG 62. For example, the update ECU 150 calculates the EV travel distance corresponding to the amount of power consumption in the period during which the update processing is implemented, as the reduction amount of the EV travel distance. The amount of power consumption based on the update processing may be a predetermined value, for example, or can be inferred from the update time according to the amount of data to be updated, and calculated using the inferred update time and the amount of power consumption per unit time. Further, the update ECU 150 calculates the EV travel distance calculated using the amount of power consumption per unit distance during electric travel using the MG 62 and the amount of power consumption based on the update processing, as the reduction amount of the EV travel distance.

[0100] In S202, the update ECU 150 determines whether the electric vehicle 1 can reach the destination. Specifically, the update ECU 150 determines that the electric vehicle 1 can reach the destination when the distance from the current location of the electric vehicle 1 to the destination is shorter than the travelable distance. For example, the travelable distance is calculated by subtracting the reduction amount of the EV travel distance based on the update processing from the travelable distance based on the current SOC. The update ECU 150 acquires the position information of the destination and the position information of the current location, for example, from a navigation system not shown. In a case where it is determined that the electric vehicle 1 can reach the destination (Yes in S202), the process proceeds to S114. Further, in a case where it is determined that the electric vehicle 1 cannot reach the destination (No in S202), the process ends.

[0101] Hereinafter, an example of the operation of the update ECU 150 in this modification based on the above flowchart will be described.

[0102] For example, assume a case where update information of the control program of the charging ECU 110 is received. In this case, the flag indicating the presence of the OTA request becomes ON, and thus it is determined that the OTA request is present (Yes in S100).

[0103] When the ECU to be updated as the OTA object is the charging ECU 110 using the identification information included in the update information (S102), the ECU to be updated as the OTA object, that is, the charging ECU 110, is an ECU that operates in external charging (No in S104 and Yes in S110), and thus it is determined whether the electric vehicle 1 is traveling (S112).

[0104] When the running state of the electric vehicle 1 is in running (S112 is Yes), the reduction amount of the EV running distance based on the update processing is calculated (S200), and it is judged whether the electric vehicle 1 can reach the destination considering the calculated reduction amount (S202). Then, in the case where it is judged that the electric vehicle 1 can reach the destination (Yes in S202), the update processing is requested to be executed to the charging ECU 110 as the target ECU (S114). Therefore, the update processing is executed in the charging ECU 110, and when the update processing is completed, the flag indicating that there is the OTA request is set to the OFF state.

[0105] In this way, when the power consumption amount increases due to the execution of the update processing of the control program of the charging ECU 110 and the electric vehicle 1 cannot reach the destination, the control program of the charging ECU 110 is not updated in running, and thus the electric vehicle 1 can reach the destination.

[0106] Further, in the above-described embodiment, in the case where the ECU as the target of the OTA is the ECU that operates in running, the case where the execution of the update processing of the target ECU is requested in charging is described, but for example, the execution of the update processing of the target ECU can be requested not only in charging but also when the charging of the electric storage device 20 can be completed before the departure time even if the consumed power increases due to the update processing.

[0107] Hereinafter, with reference to Figure 6 , an example of the control processing executed by the update ECU 150 in the modified example is described. Figure 3 is a flowchart showing another example of the processing executed by the update ECU 150 in the modified example. The series of processing shown in the flowchart is repeatedly executed in each predetermined control period.

[0108] Figure 7 The processing of S100 to S118 described in the flowchart shown in Figure 7 is the same processing content as that of S100 to S118 described in the flowchart shown in

[0109] In the case where it is judged that it is in external charging (Yes in S106), the processing is shifted to S300.

[0110] In S300, the update ECU 150 calculates an increase amount of the charging time based on the update processing. For example, the update ECU 150 calculates a time to charge an amount of electric power corresponding to the amount of power consumption in the period during which the update processing is implemented, as the increase amount of the charging time. The amount of power consumption based on the update processing is as described above, and thus a detailed description thereof will not be repeated. The update ECU 150 calculates the charging time calculated using the charging electric power per unit time and the amount of power consumption based on the update processing, as the increase amount of the charging time.

[0111] In S302, the update ECU 150 determines whether charging of the electric storage device 20 can be completed before the departure time. Specifically, the update ECU 150 calculates a charging time required until charging is completed, from the amount of electric power corresponding to the difference between the current SOC and the SOC at the time of completion of charging (for example, the SOC corresponding to the full charge state) and the charging electric power per unit time, and calculates a charging completion time from the current time as a starting point, by adding the increase amount to the calculated charging time. The update ECU 150 determines that charging of the electric storage device 20 can be completed before the departure time, in a case where the charging completion time is a time before the departure scheduled time. The update ECU 150 determines that charging of the electric storage device 20 cannot be completed before the departure time, in a case where the charging completion time is a time later than the departure scheduled time. The update ECU 150 can acquire information on the charging electric power from the charging station 53, for example, or can calculate the charging electric power from the voltage and the current of the electric storage device 20 in external charging. In a case where it is determined that charging of the electric storage device 20 can be completed before the departure time (Yes in S302), the process proceeds to S108. Further, in a case where it is determined that charging of the electric storage device 20 cannot be completed before the departure time (No in S302), the process ends.

[0112] Hereinafter, an example of the action of the update ECU 150 in this modification example based on the above flowchart will be described.

[0113] For example, assume a case where update information of the control program of the HV-ECU 100 is received. In this case, the flag indicating the presence of the OTA request becomes the ON state, and thus it is determined that the OTA request is present (Yes in S100).

[0114] When the ECU acquired as the OTA target using the identification information included in the update information is the HV-ECU 100 (S102), the ECU acquired as the OTA target, that is, the HV-ECU 100, is an ECU that operates in the traveling (Yes in S104), and thus it is determined whether it is in external charging (S106).

[0115] When it is in external charging (Yes in S106), an increase amount of the charging time based on the update processing is calculated (S300), it is judged whether the charging of the electric storage device 20 can be completed before the departure time of the electric vehicle 1 considering the calculated increase amount of the charging time (S302). Then, in a case where it is judged that the charging of the electric storage device 20 can be completed before the departure time (Yes in S302), the execution of the update processing is requested to the HV-ECU 100 as the target ECU (S108). Thus, the update processing is executed in the HV-ECU 100, and when the update processing is completed, the flag indicating that there is the OTA request is set to the OFF state.

[0116] In this way, when the power consumption amount increases due to the execution of the update processing of the control program of the HV-ECU 100 and the charging of the electric storage device 20 cannot be completed before the departure time, the control program of the HV-ECU 100 is not updated in the external charging, and thus the charging of the electric storage device 20 can be completed before the departure time.

[0117] Further, in the above-described embodiment, the case where the update processing of the target ECU is executed when the electric vehicle 1 is stopped, in a case where the ECU that is the target of the OTA is an ECU that operates in running and external charging has been described, but for example, the auxiliary battery 50 can be charged in advance in running and external charging of the electric vehicle 1, and in a case where the electric storage amount required for the execution of the update processing of the target ECU remains in the auxiliary battery 50 in the stop of the electric vehicle 1, the execution of the update processing is requested to the ECU that is the target of the update.

[0118] Hereinafter, an example of the control processing executed by the update ECU 150 in the modified example will be described with reference to ​ , an example of the processing executed by the update ECU 150 in the modified example. ​ is a flowchart showing another example of the processing executed by the update ECU 150 in the modified example.

[0119] In S400, the update ECU 150 judges whether there is an OTA request for an ECU that operates in running and external charging. As described above, the battery ECU 130 is included as the ECU that operates in running and external charging. Thus, the update ECU 150 judges that there is an OTA request for an ECU that operates in running and external charging in a case where there is an OTA request for the battery ECU 130. In a case where it is judged that there is an OTA request for an ECU that operates in running and external charging (Yes in S400), the processing shifts to S402.

[0120] In S402, the update ECU 150 determines whether the electric vehicle 1 is in running or in external charging. The method of determining whether the electric vehicle 1 is in running and the method of determining whether it is in external charging are as described above, and thus a detailed description thereof will not be repeated. When the electric vehicle 1 is in running or in external charging (YES in S402), the process shifts to S404.

[0121] In S404, the update ECU 150 charges the auxiliary battery 50. The update ECU 150 charges the auxiliary battery 50 via the battery ECU 130 using the DC / DC converter 40. The update ECU 150 controls the DC / DC converter 40 to charge the auxiliary battery 50 in a case where the charge amount of the auxiliary battery 50 is lower than a threshold value (for example, in a case where the voltage of the auxiliary battery 50 is lower than a threshold value). For example, the update ECU 150 sets the threshold value in such a manner that the value when there is an OTA request is higher than the value when there is no OTA request for the battery ECU 130.

[0122] Further, in a case where the electric vehicle 1 is neither in running nor in external charging (for example, when the electric vehicle 1 is in stop) (NO in S402), the process shifts to S406.

[0123] In S406, the update ECU 150 determines whether there is a charge amount of the auxiliary battery 50 required for the update process. For example, the update ECU 150 determines that there is a charge amount of the auxiliary battery 50 required for the update process when the voltage of the auxiliary battery 50 is higher than a threshold value. In a case where it is determined that there is a charge amount of the auxiliary battery 50 required for the update process (YES in S406), the process shifts to S408.

[0124] In S408, the update ECU 150 requests the battery ECU 130, which is the ECU of the OTA target, to perform the update process. The battery ECU 130 updates the control program stored in the memory 134 of the battery ECU 130 using the differential data included in the update information when the update information is received from the update ECU 150. The battery ECU 130 transmits information indicating the completion of the update process to the update ECU 150 when the update process is completed. The update ECU 150 sets the flag indicating the presence of the OTA request to the OFF state when the information is received.

[0125] In this way, by charging the auxiliary battery 50 in external charging or in running of the electric vehicle 1, it is possible to secure the electric power required for implementing the update process. Therefore, it is possible to implement the update of the control program in the battery ECU 130 in stop.

[0126] Further, in the above-described embodiment, a case where the update ECU 150 requests the execution of the update processing to the ECU of the OTA target is described, but the update processing is not limited to being executed in the control system 90, and in particular, the update processing is executed in the ECU of the OTA target according to the request of the update ECU 150, for example, the update ECU 150 can be enabled to execute the update processing of each ECU, or any one of the ECUs constituting the control system 90 can be enabled to execute the update processing of each ECU.

[0127] Further, in the above-described embodiment, a case where the update information of any one of the ECUs in the control system 90 is included in the update information received from the management server 10 is described, but for example, the update information of a plurality of ECUs can be included in the update information received from the management server 10. In this case, the control programs can be updated in the order of the priority set in advance for each ECU, or in the case where information specifying the update order is included in the update information, the control programs of each ECU can be updated in the specified update order.

[0128] Further, in the above-described embodiment, a case where the update ECU 150 requests the execution of the update processing to the ECU of the OTA target is described, but for example, the management server 10 can request the execution of the update processing to the ECU of the OTA target. The management server 10 can also communicate with the electric vehicle 1 to acquire information that is in running, is in external charging, or is in stopping, from the electric vehicle 1, and request the execution of the update processing to the ECU of the OTA target using the acquired information.

[0129] Further, the above-described modified examples can be implemented by appropriately combining all or a part thereof. Although the embodiments of the present application have been described, it should be considered that the disclosed embodiments are illustrative in all respects rather than restrictive. The scope of the present application is indicated by the claims, and includes all changes equivalent in meaning and range to the claims.

Claims

1. An electric vehicle having: an electric storage device that is chargeable using a power source outside the vehicle; a drive motor that drives the vehicle using electric power of the electric storage device; a reception device that receives predetermined information from outside the vehicle; a control system that is configured by a plurality of control devices including a first control device, a second control device, and a third control device; an auxiliary battery that supplies electric power to the third control device, the first control device controls a device that is a control target in charging of the electric storage device using the power source outside the vehicle using a first control program, the second control device controls a device that is a control target in running of the vehicle using the drive motor using a second control program, the third control device controls a device that is a control target in each of the charging and the running using a third control program, in the control system, in a case where update information of the first control program is received using the reception device, the first control program is updated using the update information in the running, in a case where update information of the second control program is received using the reception device, the second control program is updated using the update information in the charging, in a case where processing for updating the first control program and the second control program is performed, it is determined whether or not there is a request for updating a control program before it is determined whether or not it is in the charging and whether or not it is in the running, in a case where it is determined that there is a request for updating a control program and it is in the running, the first control program is updated, and in a case where it is determined that there is a request for updating a control program and it is in the charging, the second control program is updated, in a case where update information of the third control program is received using the reception device, the auxiliary battery is charged in at least either the charging or the running, and in a case where a charge amount of the auxiliary battery is equal to or more than a threshold value at which updating of the third control program is possible in a stop of the vehicle, the third control program is updated using the update information.

2. The electric vehicle according to claim 1, wherein in a case where a distance that can be traveled due to an increase in an amount of electric power consumed accompanying updating of the first control program is shorter than a distance to a destination of the vehicle when the update information of the first control program is received using the reception device, the control system does not update the first control program in the running.

3. The electric vehicle according to claim 1 or 2, wherein in a case where charging of the electric storage device cannot be completed until a departure time due to an increase in an amount of electric power consumed accompanying updating of the second control program when the update information of the second control program is received using the reception device, the control system does not update the second control program in the charging.

4. A control method of an electric vehicle having: an electric storage device that is chargeable using a power source outside the vehicle; a drive motor that drives the vehicle using electric power of the electric storage device; a reception device that receives predetermined information from outside the vehicle; a control system that is configured by a plurality of control devices including a first control device, a second control device, and a third control device; an auxiliary battery that supplies electric power to the third control device, the first control device controls a device that is a control target in charging of the electric storage device using the power source outside the vehicle using a first control program, the second control device controls a device that is a control target in running of the vehicle using the drive motor using a second control program, the third control device controls a device that is a control target in each of the charging and the running using a third control program, in the control system, in a case where update information of the first control program is received using the reception device, the first control program is updated using the update information in the running, in a case where update information of the second control program is received using the reception device, the second control program is updated using the update information in the charging, in a case where processing for updating the first control program and the second control program is performed, it is determined whether or not there is a request for updating a control program before it is determined whether or not it is in the charging and whether or not it is in the running, in a case where it is determined that there is a request for updating a control program and it is in the running, the first control program is updated, and in a case where it is determined that there is a request for updating a control program and it is in the charging, the second control program is updated, in a case where update information of the third control program is received using the reception device, the auxiliary battery is charged in at least either the charging or the running, and in a case where a charge amount of the auxiliary battery is equal to or more than a threshold value at which updating of the third control program is possible in a stop of the vehicle, the third control program is updated using the update information. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ an electrical storage device that is chargeable using a power source external to a vehicle; a drive motor that drives the vehicle using electric power from the electrical storage device; a reception device that receives predetermined information from outside the vehicle; a control system configured by a plurality of control devices including a first control device, a second control device, and a third control device; an auxiliary battery that supplies electric power to the third control device, the first control device controls a device that is a control target in charging of the electrical storage device using the external power source using a first control program, the second control device controls a device that is a control target in running of the vehicle using the drive motor using a second control program, the third control device controls a device that is a control target in each of the charging and the running using a third control program, the control method includes: a step of updating the first control program using update information of the first control program received by the reception device in the running; a step of updating the second control program using update information of the second control program received by the reception device in the charging; a step of, in performing processing for updating the first control program and the second control program, determining whether or not there is a request for updating a control program before determining whether or not it is in the charging and whether or not it is in the running, and in a case where it is determined that there is a request for updating a control program and it is in the running, performing updating of the first control program, and in a case where it is determined that there is a request for updating a control program and it is in the charging, performing updating of the second control program; a step of, in a case where update information of the third control program is received by the reception device, charging the auxiliary battery in at least either the charging or the running; a step of, in a case where the charge amount of the auxiliary battery is equal to or more than a threshold value at which updating of the third control program is possible in the stopping of the vehicle, updating the third control program using the update information.

5. A control device of an electric vehicle including: an electrical storage device that is chargeable using a power source external to a vehicle; a drive motor that drives the vehicle using electric power from the electrical storage device; a reception device that receives predetermined information from outside the vehicle; an auxiliary battery, the control device is configured to be able to communicate with a first control device, a second control device, and a third control device, the first control device controls a device that is a control target in charging of the electrical storage device using the external power source using a first control program, the second control device controls a device that is a control target in running of the vehicle using the drive motor using a second control program, The third control device controls, using a third control program, a device that is a control target of each of the charging and the traveling, In the control device, In a case where the receiving device receives update information of the first control program, the first control device is requested to update the first control program using the update information in the traveling, In a case where the receiving device receives update information of the second control program, the second control device is requested to update the second control program using the update information in the charging, In a case where the receiving device receives update information of the third control program, the auxiliary battery is charged in at least either of the charging and the traveling, In a case where the charge amount of the auxiliary battery in the stop of the vehicle is equal to or more than a threshold value at which the update of the third control program is possible, the third control program is requested to update the third control program using the update information. ​

Images