Vehicle

Abstract

The invention provides a vehicle. The vehicle is configured so as to be able to execute external charging for charging a battery by means of a power device provided outside the vehicle. A vehicle includes a storage device and a control device. The storage device stores certificate data for allowing execution of external charging. The control device controls a communication sequence executed between the power equipment and the vehicle before the external charging starts. The certificate data has a valid period. The control device executes an update process for updating the certificate data when the expiration date at the start of the communication sequence expires, and temporarily stops the communication sequence when it is predicted that the update process is overtime.

Description

Technical Field

[0001] The present disclosure relates to vehicles. Background Art

[0002] Japanese Patent Publication No. 2022-61185 discloses a charging authentication device. The device includes an on-board processing unit and a vehicle-side authentication unit. The on-board processing unit is mounted on the vehicle and communicates with a charging device outside the vehicle. The charging device is used to charge the vehicle's rechargeable battery (for external charging). The vehicle-side authentication unit sends authentication information pre-issued to the user of the vehicle to a server device. The information includes an electronic certificate (certificate data) with a validity period. Summary of the invention

[0003] Before external charging starts, a communication sequence is usually performed to exchange various information between the vehicle and an electric power device outside the vehicle. When external charging starts in order to execute the communication sequence, the validity period of the certificate data must not have expired. When it is determined at the start of the communication sequence that the validity period of the certificate data has expired, it is necessary to access a server that manages the certificate data to update the certificate data (certificate data update process). However, when the update process takes time due to a decrease in communication speed, etc., the update process sometimes times out. As a result, the communication sequence ends halfway without being completed, and external charging cannot be started. Then, if the operation for starting external charging is performed again, the information that has been exchanged in the previous communication sequence from its start to its end may be exchanged again in this communication sequence. This is not preferred from the perspective of the efficiency of information transmission in the communication sequence.

[0004] The present disclosure has been made to solve the above-mentioned problems, and an object thereof is to provide a vehicle capable of improving the efficiency of information transmission in a communication sequence when the validity period of certificate data expires at the start of a communication sequence before external charging.

[0005] The vehicle disclosed in the present invention is configured to be capable of performing external charging, which charges an on-board power storage device through an electric power device provided outside the vehicle. The vehicle is provided with a storage device and a control device. The storage device stores certificate data for allowing the execution of external charging. The control device controls a communication sequence executed between the electric power device and the vehicle before the start of external charging. The certificate data has a validity period. When the validity period expires at the start of the communication sequence, the control device executes an update process for updating the certificate data, and when a timeout of the update process is predicted, the communication sequence is temporarily stopped.

[0006] By setting the above structure, the communication sequence is temporarily stopped before the update process times out. Thus, the update process is completed during the period when the communication sequence is temporarily stopped, thereby updating the validity period of the certificate data. As a result, the expiration of the validity period is eliminated. Therefore, the situation where the communication sequence ends midway due to the expiration of the validity period is avoided. Therefore, the efficiency of information transmission in the communication sequence can be improved.

[0007] According to the present disclosure, when the validity period of the certificate data expires at the start of the communication sequence before external charging, the efficiency of information transfer in the communication sequence can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, wherein like reference numerals represent like components.

[0009] Figure 1 It is a diagram schematically showing the overall configuration of the charging processing system according to the present embodiment.

[0010] Figure 2 This is a diagram for explaining the structure and function of the control device in detail.

[0011] Figure 3 The flowchart exemplifies a process performed in association with plug and charge (P&C).

[0012] Figure 4 This is a flowchart illustrating a process performed in association with P&C.

[0013] Figure 5 It is a flowchart illustrating a process executed by a high level communication (HLC)-electronic control unit (ECU) in a modified example. DETAILED DESCRIPTION

[0014] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The same or corresponding parts in the drawings are denoted by the same reference numerals and their description will not be repeated. The embodiments and their modifications may be appropriately combined with each other.

[0015] Figure 1 1 is a diagram schematically showing the overall configuration of a charging processing system 1 according to the present embodiment. Figure 1 The charging processing system 1 includes a vehicle 100 , a server 200 , an electric power device 300 , a certificate server 400 , and a portable terminal 500 .

[0016] The vehicle 100 is a battery electric vehicle (BEV) and includes a battery 105 , a storage device 110 , a data communication module (DCM) 120 , a human machine interface (HMI) device 130 , a socket 140 , and a control device 150 .

[0017] The battery 105 is a secondary battery such as a lithium-ion battery, and is an example of a power storage device mounted on the vehicle 100. The battery 105 stores power for driving the vehicle 100. The vehicle 100 is configured to be able to perform external charging of charging the battery 105 through the power equipment 300. In this example, the power supplied from the power equipment 300 to the vehicle 100 is direct current power. External charging using direct current power is also referred to as "DC charging".

[0018] In the present embodiment, external charging is DC charging, specifically, charging called plug and charge (P&C). After the power device 300 confirms that the vehicle 100 is a certified vehicle that has undergone a prescribed certification (described later), P&C is automatically performed. "Automatic execution" means that it is performed without a user operation for starting DC charging (for example, an operation of the charging start button 305 of the power device 300). That is, according to P&C, a communication sequence is automatically started in response to the connection (insertion) of the connector 301 of the power device 300 to the socket 140, and DC charging is automatically performed after the communication sequence is completed. Therefore, the user U basically only needs to insert the connector 301 into the socket 140 during P&C, and there is no need to present an electronic device such as an IC card for authentication. As a result, the convenience of the user U can be improved.

[0019] P&C is a service provided by a predetermined mobile operator and is performed based on a contract between the operator and the user U. Hereinafter, an example in which external charging is P&C will be mainly described.

[0020] The storage device 110 is a secure memory that stores certificate data 115. The certificate data 115 is used to allow the execution of P&C. The certificate data 115 proves through an electronic signature that the vehicle 100 is a certified vehicle that has undergone a prescribed certification. This certification is provided from the operator to the vehicle 100 when the user U has signed a contract with a mobile operator for utilizing a charging service based on P&C. In this example, the user U has signed the above-mentioned contract with the operator. The certificate data 115 includes validity period information 116. The validity period information 116 indicates the validity period of the certificate data 115. In this way, the certificate data 115 has a validity period. If the validity period expires, the above-mentioned certification becomes invalid and P&C cannot be executed. The certificate data 115 is used in the communication sequence performed between the vehicle 100 and the power device 300 before the start of P&C.

[0021] The communication sequence is a process of exchanging various information between the vehicle 100 and the power device 300 before the P&C starts. The information includes various information related to the vehicle 100 (vehicle information) and specification information of the power device 300 (device information). The vehicle information includes authentication information of the user U related to the charging service (such as credit card information) and identification information of the vehicle 100 (such as manufacturer information and identification number). The device information includes identification information of the power device 300 (such as manufacturer information and identification number).

[0022] The communication sequence is performed in order for the power supply device 300 to confirm that the vehicle 100 is an authorized vehicle, and in order for the vehicle 100 to confirm that the power device 300 is an authorized device. The authorized device is a power device that has received a prescribed authentication provided by the above-mentioned mobile operator. In order to start the P&C by executing the communication sequence, it is necessary that the validity period of the certificate data 115 has not expired. The communication sequence complies with a prescribed international communication standard. The communication standard is, for example, ISO 15118-20.

[0023] The DCM 120 is configured to wirelessly communicate with external devices of the vehicle 100. The external devices include the server 200. The HMI device 130 displays various screens. The screens include a notification screen for notifying the user U of the expiration date of the certificate data 115.

[0024] The socket 140 is configured to be connectable to the connector 301 of the power device 300. In the embodiment, the communication sequence is started in response to the connection of the connector 301 to the socket 140. The socket 140 is configured to receive the power supply supplied from the power device 300.

[0025] The control device 150 controls various devices of the vehicle 100 such as the DCM 120 and the HMI device 130. The control device 150 detects the connection (insertion) of the connector 301 to the socket 140 based on the level of the signal CPLT input from the power device 300 through the socket 140. Before the P&C starts, the control device 150 confirms that the power device 300 is an authenticated device in the communication sequence. The configuration and function of the control device 150 will be described in detail later.

[0026] The server 200 is configured to communicate with the vehicle 100. The server 200 is also configured to communicate with a portable terminal 500. The portable terminal 500 is, for example, a smartphone, and is owned by a user U of the vehicle 100. The portable terminal 500 includes a display for displaying various screens.

[0027] The power device 300 is provided outside the vehicle 100 and is connected to a commercial power source (not shown). The power device 300 includes a connector 301, a power cable 302, a power supply unit 303, a charge start button 305, a communication unit 307, and a control unit 309. The connector 301 is provided at the front end of the power cable 302. The power supply unit 303 is configured to convert AC power from a commercial power source into DC power and supply the converted power to the vehicle 100 through the power cable 302. The charge start button 305 can receive a user operation indicating the start of DC charging. The communication unit 307 is configured to wirelessly communicate with a certificate server 400 (described later). The communication unit 307 is also configured to execute a communication sequence with the vehicle 100. The control unit 309 controls the power supply unit 303 and the communication unit 307. Before the P&C starts, the control unit 309 confirms that the vehicle 100 is an authenticated vehicle in the communication sequence.

[0028] The certificate server 400 is operated by a mobile operator that provides a charging service based on P&C. The certificate server 400 can issue new certificate data when the validity period of the certificate data 115 expires. The certificate server 400 is configured to perform wireless communication with the power equipment 300.

[0029] Figure 2 Detailed description of the structure and function of the control device 150. Figure 2 , the control device 150 includes a vehicle ECU 155 , a charging control ECU 160 and an HLC-ECU 170 .

[0030] The vehicle ECU 155 comprehensively performs control of the vehicle 100. The vehicle ECU 155 controls the DCM 120, the HMI device 130, and the charging control ECU 160, for example.

[0031] The charging control ECU 160 includes a CPU 162 and a memory 164. The CPU 162 performs various calculation processes. The memory 164 includes a read-only memory (ROM) and a random access memory (RAM). The ROM stores a program executed by the CPU 162. When the connector 301 is connected to the socket 140, the charging control ECU 160 sends a startup instruction to the HLC-ECU 170. In the startup of the HLC-ECU 170, the HLC-ECU 170 manages the communication sequence by successively receiving information indicating the state of the communication sequence from the HLC-ECU 170, thereby sending a control instruction for controlling the HLC-ECU 170 to the HLC-ECU 170. During DC charging, the charging control ECU 160 sends information indicating the charging state of the battery 105 to the vehicle ECU 155. The information includes the SOC (State Of Charge) of the battery 105.

[0032] HLC-ECU 170 includes CPU 172 and memory 174. CPU 172 performs various calculations. Memory 174 includes ROM and RAM. ROM stores programs executed by CPU 172. HLC-ECU 170 communicates with power device 300 through HLC communication, thereby controlling the communication sequence before P&C or controlling the power supply after P&C starts.

[0033] The HLC-ECU 170 is configured to execute an update process for updating the certificate data 115 when the validity period of the certificate data 115 expires at the start of the communication sequence. The update process includes a process for updating (extending) the validity period of the certificate data 115 to a date and time later than the current date and time. The current date and time is the date and time when the update process is executed.

[0034] The update process includes a process of sending a certificate request signal to the power device 300 through HLC communication. The signal is a request signal for requesting the power device 300 to have the certificate server 400 issue new certificate data, obtain the issued certificate data, send an acquisition completion notification indicating that the acquisition of the certificate data is completed, and send the acquired certificate data to the vehicle 100. The update process also includes a process of receiving new certificate data from the power device 300, a process of deleting old certificate data whose validity period has expired, and a process of storing (installing) the new certificate data as the certificate data 115 in the storage device 110.

[0035] If the execution time of the update process exceeds a reference time, the update process times out. The reference time is determined based on the aforementioned communication standard, for example, 5 seconds.

[0036] When it is determined at the beginning of the communication sequence that the validity period of the certificate data 115 has expired, it is necessary to access the certificate server 400 and issue new certificate data to update the certificate data 115. However, the data size of the certificate data 115 is generally large. Sometimes the speed of the HLC communication between the vehicle 100 and the power device 300 decreases. Therefore, if both the update process of the certificate data 115 and the exchange of the above-mentioned vehicle information and device information are performed through HLC communication, the data volume of the HLC communication increases. In addition, there is also a case where the communication speed between the power device 300 and the certificate server 400 decreases. In such a case, the update process takes time. When the update process takes time and the update process times out, the certificate data 115 is not updated (new certificate data is not obtained), and the expiration of the validity period of the certificate data 115 is not eliminated. As a result, the communication sequence is not completed and ends halfway, and P&C cannot be started. Afterwards, although the charging start button 305 can be operated again, the information exchanged between the start and end of the previous communication sequence (part of the above-mentioned vehicle information and device information) may be exchanged again in this communication sequence. This is not preferable from the viewpoint of efficiency of information transfer in the communication sequence.

[0037] The control device 150 according to the embodiment has a structure for dealing with such a problem. Specifically, when the control device 150 determines that the validity period of the certificate data 115 has expired at the beginning of the communication sequence, it performs a process of temporarily stopping (sleeping) the communication sequence when a timeout of the update process is predicted. This process includes a process of sending a temporary stop request for temporarily stopping the communication sequence to the power device 300.

[0038] By setting such a structure, the power device 300 temporarily stops the communication sequence in response to the temporary stop request. As a result, the communication sequence is temporarily stopped before the update process times out. Due to the temporary stop of the communication sequence, the amount of data in the HLC communication is reduced, the data processing load of the control device 150 (HLC-ECU 170) is reduced, and the processing speed of the update process is improved. As a result, the update process is completed during the period when the communication sequence is temporarily stopped (before the timeout of the update process), whereby the validity period of the certificate data 115 is updated, and the expiration of the validity period is eliminated. Therefore, the situation where the communication sequence ends midway due to the expiration of the validity period is avoided. Therefore, the efficiency of information transmission in the communication sequence can be improved.

[0039] The control device 150 predicts (determines) whether the execution time of the update process exceeds the reference time (whether a timeout occurs) based on whether the update process is completed within a specified time shorter than the reference time from the start of the update process. The specified time is, for example, 3 seconds. In this example, if the update process is not completed within the above-mentioned specified time from the start of the update process, a timeout is predicted. If the update process is completed within the specified time from the start of the update process, it is determined that no timeout occurs (the update process is completed within the reference time).

[0040] If the update process is not completed within the specified time from the start of the update process, there is a possibility that the update process will be extended. In this case, the execution time of the communication sequence may exceed the reference time and time out due to the update process. As described above, according to the prediction process based on the specified time, it is possible to appropriately predict whether a timeout will occur.

[0041] Furthermore, whether the update process is completed is determined based on whether the HLC-ECU 170 has completed receiving the certificate data acquisition completion notification and new certificate data from the electric device 300 and storing the certificate data in the storage device 110 .

[0042] When the updating process of the certificate data 115 is completed after the temporary suspension of the communication sequence, the control device 150 performs a process of canceling the temporary suspension of the communication sequence and resuming the communication sequence, including a process of transmitting a restart request for resuming the communication sequence to the power device 300 .

[0043] By setting such a configuration, the communication sequence is restarted in a state where the validity period has expired and has been eliminated. As a result, the communication sequence can be completed before the P&C starts. As a result, even if the validity period of the certificate data 115 is determined to have expired at the start of the communication sequence, DC charging can be automatically started without reinserting the connector 301 into the socket 140 or pressing the charge start button 305.

[0044] Figure 3 and Figure 4 1 is a flowchart illustrating processing performed in association with P & C. This flowchart starts when connection of connector 301 to socket 140 is detected.

[0045] Reference Figure 3 , the charging control ECU 160 sends a start command to the HLC-ECU 170 (S105). The HLC-ECU 170 starts up in response to the command and starts a communication sequence with the power device 300 (S207). The HLC-ECU 170 confirms the validity period of the certificate data 115 based on the validity period information 116 when the communication sequence starts (S210).

[0046] HLC-ECU 170 determines whether the current date is before the expiration date (S215). If the current date is before the expiration date, that is, if the expiration date has not expired ("Yes" in S215), HLC-ECU 170 continues the communication sequence. After the communication sequence is completed, the processing of HLC-ECU 170 enters Figure 4 If the current date is later than the validity period, that is, if the validity period has expired (No in S215), HLC-ECU 170 notifies charging control ECU 160 of the expiration of the validity period of certificate data 115 (S220).

[0047] In response to the notification, the charging control ECU 160 instructs the HLC-ECU 170 to update the certificate data 115 (S125). In response to the instruction, the HLC-ECU 170 starts the update process of the certificate data 115 (S230). Specifically, the HLC-ECU 170 transmits a certificate request signal CR-RQ to the power device 300.

[0048] The HLC-ECU 170 determines whether a timeout of the update process is predicted (the execution time of the update process exceeds the reference time) (S235). Specifically, the HLC-ECU 170 determines whether the update process is completed within the prescribed time PT. If a timeout is not predicted, that is, if the update process is completed within the prescribed time PT (No in S235), the processing of the HLC-ECU 170 enters Figure 4 If a timeout is predicted, that is, if the update process is not completed within the prescribed time PT (Yes in S235), the process of HLC-ECU 170 enters Figure 4 S240.

[0049] Reference Figure 4 The HLC-ECU 170 transmits a temporary stop request TS-RQ requesting temporary stop of the communication sequence to the power device 300 ( S240 ).

[0050] The power device 300 responds to the temporary stop request TS-RQ and determines whether it can accept the temporary stop of the communication sequence (S342). In the case where the power device 300 cannot accept the temporary stop of the communication sequence, for example, assuming that the communication sequence does not meet the aforementioned communication standard (No in S342), the processing of the power device 300 ends. The power device 300 temporarily stops the communication sequence when it can accept the temporary stop of the communication sequence (Yes in S342). Then, the power device 300 notifies the HLC-ECU 170 of the acceptance of the temporary stop of the communication sequence (S345). Specifically, the power device 300 sends a temporary stop acceptance notification to the HLC-ECU 170. Then, the power device 300 causes the certificate server 400 to issue new certificate data, and sends the issued certificate data to the HLC-ECU 170 through HLC communication (S360).

[0051] The HLC-ECU 170 determines whether a temporary stop receiving notification is received within a specified period (for example, within 2 seconds) from S240 (S250). If the HLC-ECU 170 does not receive the notification within the specified period (No in S250), it notifies the charging control ECU 160 of the situation. In this case, the update process times out. In response to the notification from the HLC-ECU 170, the charging control ECU 160 sends a validity expiration notification indicating that the validity period of the certificate data 115 has expired to the vehicle ECU 155, whereby the notification is sent to the portable terminal 500 via the DCM 120 and the server 200 (S155). In response to the validity expiration notification, the portable terminal 500 displays a notification screen for notifying the user U of the expiration of the validity period of the certificate data 115 (S60). The screen may also be displayed as a screen notifying an error caused by the expiration of the validity period. The screen may also be displayed on the HMI device 130 of the vehicle 100.

[0052] When HLC-ECU 170 receives the temporary suspension notification within the predetermined period (Yes in S250), it receives the newly issued certificate data from power device 300 through HLC communication (S265). HLC-ECU 170 stores the newly issued certificate data as certificate data 115 in storage device 110 instead of the old certificate data, thereby completing the update process (S270).

[0053] The HLC-ECU 170 sends a validity period update notification to the charging control ECU 160 (S275). This notification indicates that the validity period of the certificate data 115 is updated due to the completion of the update process. The charging control ECU 160 sends the notification to the vehicle ECU 155, whereby the notification is sent to the portable terminal 500 via the DCM 120 and the server 200 (S185). In response to the validity period update notification, the portable terminal 500 displays a notification screen for notifying the user U of the update of the validity period of the certificate data 115 (S90). This screen may also be displayed on the HMI device 130 of the vehicle 100.

[0054] After S275, the HLC-ECU 170 transmits a restart request RS-RQ requesting to restart the communication sequence to the power device 300 (S292). The power device 300 restarts the communication sequence in response to the restart request RS-RQ (S394). Thereafter, the communication sequence is completed.

[0055] After the communication sequence is completed, the HLC-ECU 170 executes a process for starting P&C (external charging) (S297). This process includes a process of sending a power supply start instruction to instruct the start of power supply to the vehicle 100 to the power device 300 according to the instruction from the charging control ECU 160. The power device 300 starts power supply to the vehicle 100 in response to the power supply start instruction. Thus, P&C starts.

[0056] As described above, according to the embodiment, the control device 150 temporarily stops the communication sequence when predicting a timeout in the update process of the certificate data 115. This avoids the situation where the communication sequence ends midway due to the expiration of the validity period of the certificate data 115. Therefore, the efficiency of information transmission in the communication sequence can be improved.

[0057] When the validity period of the certificate data 115 expires, the control device 150 can send a notification to promote the update of the certificate data 115 to the portable terminal 500 through the DCM 120 and the server 200, but sometimes the user U does not notice the notification. The embodiment is effective when the user U notices such a notification when inserting the connector 301 into the socket 140 (immediately before starting P&C).

[0058] Modifications of the Embodiments

[0059] In the case where the update process is extended and times out despite the temporary stop of the communication sequence, there is a possibility that the communication associated with the update process is unstable. The communication is, for example, wireless communication between the power device 300 and the certificate server 400. In the case of unstable communication as described above, there is a high possibility that a timeout will occur during the retry of the update process, making it difficult to update the certificate data 115. In this case, it is preferred that the communication sequence be completely terminated.

[0060] The HLC-ECU 170 according to this modification executes a process for completely ending the communication sequence when the update process times out. This process includes a process for transmitting an end request for requesting the end of the communication sequence to the power device 300 .

[0061] By setting such a configuration, when the update process times out (for example, when the communication status is considered unstable), the communication sequence is completely terminated. This can avoid the situation where the communication sequence is temporarily stopped for a long time and wastes time.

[0062] Figure 5 2 is a flowchart illustrating the processing executed by HLC-ECU 170 in this modification. Figure 5 , S250, S155 processing and Figure 4 The processing shown is the same.

[0063] In the case where the update process times out (No in S250), the HLC-ECU 170 transmits an end request EN-RQ requesting the end of the communication sequence to the power device 300 (S252). In response to the end request EN-RQ, the power device 300 completely ends the communication sequence. After S252, the process proceeds to S155. In this case, the validity period expiration notification of S155 may include information for notifying the user U that it is difficult to update the certificate data 115 due to the unstable communication condition.

[0064] As described above, according to this modification, when the update process times out, the communication sequence is completely terminated, thereby preventing the communication sequence from being temporarily stopped for a long time and wasting time.

[0065] Other variations

[0066] As long as vehicle 100 can be externally charged, it may be another type of electric vehicle such as a plug-in hybrid electric vehicle (PHEV) that also includes an engine.

[0067] The power supplied by the power equipment 300 is DC power, but may also be AC ​​power. External charging using AC power is also referred to as "AC charging". When AC charging of the vehicle 100 is performed, the vehicle 100 includes a charging device (not shown). The charging device converts the AC power from the power equipment 300 into DC power for charging the battery 105, and supplies the converted power to the battery 105. In this way, external charging (P&C) is not limited to DC charging, but may also be AC ​​charging.

[0068] The control device 150 may also predict whether the update process will time out based on the data size of the certificate data 115 (certificate data before update). For example, if the data size is greater than a threshold, it is predicted that a timeout will occur. On the other hand, if the data size is less than the threshold, it is predicted that no timeout will occur (the update process will be completed within the reference time). Information indicating the data size is pre-stored in the storage device 110.

[0069] DCM 120 may be configured to perform wireless communication with certificate server 400. In this case, control device 150 may obtain new certificate data from certificate server 400 via DCM 120 by wireless communication instead of HLC communication, and execute update processing of certificate data 115 based on the obtained data.

[0070] The embodiments disclosed this time should be considered as illustrative in all aspects and not restrictive. The scope of the present invention is indicated by the claims rather than the above description, and is intended to include all modifications within the meaning and scope equivalent to the claims.

Claims

1. A vehicle capable of performing external charging, wherein the external charging charges an on-vehicle power storage device by an electric power device provided outside the vehicle, wherein: The vehicle has: a storage device storing certificate data for allowing execution of the external charging; and a control device that controls a communication sequence performed between the power device and the vehicle before the external charging starts, The certificate data has a validity period. The control means executes an update process for updating the certificate data when the validity period expires at the start of the communication sequence, The control device temporarily stops the communication sequence when predicting a timeout of the update process.

2. The vehicle according to claim 1, wherein: The control device restarts the communication sequence when the update process is completed after the temporary stop of the communication sequence.

3. The vehicle according to claim 1 or 2, wherein: If the execution time of the update process exceeds the reference time, the update process times out. The timeout is predicted when the update process is not completed within a predetermined time shorter than the reference time from the start of the update process.

4. The vehicle according to claim 3, wherein: The control device ends the communication sequence if the update process times out.

5. The vehicle according to claim 1, wherein: The vehicle includes an inlet configured to be connectable to the connector of the electric device and configured to receive electric power supplied from the electric device. The communication sequence begins in response to connection of the connector to the socket, In the communication sequence, the electric device confirms that the vehicle has received a predetermined authentication. The external charging includes plug-and-charge which is automatically performed after the electric power equipment confirms that the vehicle has accepted the authentication.

Images