vehicle

Abstract

To improve efficiency of information transmission in a communication sequence when an expiration date of certificate data has expired at a start of the communication sequence before external charging.SOLUTION: A vehicle 100 is configured to be capable of performing external charging for charging a battery 105 by power facilities 300 provided outside the vehicle 100. The vehicle 100 includes a storage device 110 and a control device 150. The storage device 110 stores certificate data 115 for permitting execution of external charging. The control device 150 controls a communication sequence performed between the power facilities 300 and the vehicle 100 before external charging is started. The certificate data 115 has an expiration date. The control device 130 executes update processing for updating the certificate data 115 when the expiration date has expired at the start of the communication sequence, and temporarily stops the communication sequence when time-out of the update processing is predicted.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] This disclosure relates to vehicles.

Background Art

[0002] Patent Document 1 (Japanese Patent Application Laid-Open No. 2022-61185) discloses a charging authentication device. This device includes an in-vehicle processing unit and a vehicle-side authentication unit. The in-vehicle processing unit is mounted on the vehicle and communicates with charging equipment outside the vehicle. The charging equipment is used to charge the vehicle's rechargeable battery (to perform external charging). The vehicle-side authentication unit transmits authentication information pre-issued to the user of the vehicle to a server device. This information includes an electronic certificate (certificate data) having an expiration date.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Before initiating external charging, a communication sequence is generally executed to exchange various information between the vehicle and external power equipment. To execute the communication sequence and begin external charging, the certificate data must not have expired. If the certificate data is found to have expired at the start of the communication sequence, it is necessary to access a server managing the certificate data and update it (certificate data update process). However, if the update process takes time due to factors such as a decrease in communication speed, the update process may time out. As a result, the communication sequence may not be completed and may terminate prematurely, preventing the start of external charging. If the operation to start external charging is then attempted again, information that was already exchanged between the start and termination of the previous communication sequence may be exchanged again in the current communication sequence. This is undesirable from the standpoint of information transmission efficiency in the communication sequence.

[0005] This disclosure was made to solve the above-mentioned problems, and its purpose is to provide a vehicle capable of improving the efficiency of information transmission in a communication sequence when the certificate data has expired at the start of the communication sequence before external charging. [Means for solving the problem]

[0006] The vehicle of this disclosure is configured to perform external charging, which charges an on-board energy storage device using power equipment located outside the vehicle. The vehicle comprises a storage device and a control device. The storage device stores certificate data for authorizing the execution of external charging. The control device controls a communication sequence performed between the power equipment and the vehicle before the start of external charging. The certificate data has an expiration date. The control device performs an update process to update the certificate data if it has expired at the start of the communication sequence, and suspends the communication sequence if a timeout of the update process is anticipated.

[0007] With the above configuration, the communication sequence is paused before the update process times out. This allows the update process to complete while the communication sequence is paused, thereby updating the expiration date of the certificate data. As a result, the expiration date is resolved. Therefore, situations where the communication sequence is terminated prematurely due to expiration are avoided. Thus, the efficiency of information transmission in the communication sequence can be improved. [Effects of the Invention]

[0008] According to this disclosure, if the certificate data has expired at the start of the communication sequence before external charging, the efficiency of information transmission in the communication sequence can be improved. [Brief explanation of the drawing]

[0009] [Figure 1] This diagram schematically shows the overall configuration of the charging process system according to this embodiment. [Figure 2] This diagram provides a detailed explanation of the configuration and functions of the control device. [Figure 3] This flowchart illustrates the processes performed in relation to P&C (Plug and Charge). [Figure 4] This flowchart illustrates the processes performed in relation to P&C (Point and Control). [Figure 5] This flowchart illustrates the processing performed by the HLC (High Level Communication)-ECU (Electronic Control Unit) in a modified example. [Modes for carrying out the invention]

[0010] Embodiments of this disclosure will be described in detail below with reference to the drawings. The same or corresponding parts in the drawings will be denoted by the same reference numerals and their descriptions will not be repeated. Each of the embodiments and its modifications may be combined with one another as appropriate.

[0011] Figure 1 is a schematic diagram showing the overall configuration of the charging processing system 1 according to this embodiment. Referring to Figure 1, the charging processing system 1 comprises a vehicle 100, a server 200, power equipment 300, a certificate server 400, and a mobile terminal 500.

[0012] Vehicle 100 is an electric vehicle (BEV: Battery Electric Vehicle). Vehicle 100 includes a battery 105, a storage device 110, a DCM (Data Communication Module) 120, an HMI (Human Machine Interface) device 130, an inlet 140, and a control device 150.

[0013] Battery 105 is a secondary battery such as a lithium-ion battery, and is an example of an energy storage device installed in vehicle 100. Battery 105 stores the power for driving vehicle 100. Vehicle 100 is configured to allow external charging of battery 105 by power equipment 300. In this example, the power supplied from power equipment 300 to vehicle 100 is DC power. External charging using DC power is also referred to as "DC charging".

[0014] In this embodiment, external charging is DC charging, specifically a type of charging called plug-and-charge (P&C). P&C is performed automatically after the power equipment 300 confirms that the vehicle 100 is a certified vehicle (described later) that has received a predetermined certification. "Performed automatically" means that it is performed without any user operation to start DC charging (for example, operation on the charging start button 305 of the power equipment 300). In other words, with P&C, a communication sequence is automatically started in response to the connection (insertion) of the connector 301 of the power equipment 300 to the inlet 140, and DC charging is automatically performed after the completion of the communication sequence. Therefore, when using P&C, the user U basically only needs to insert the connector 301 into the inlet 140 and does not 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.

[0015] P&C (Platform & Charge) is a service provided by a designated mobility provider and is performed based on a contract between that provider and the user U. The following explanation primarily focuses on examples where external charging is a form of P&C.

[0016] The storage device 110 is a secure memory that stores certificate data 115. The certificate data 115 is used to authorize the execution of P&C. The certificate data 115 electronically certifies that the vehicle 100 is a certified vehicle that has received a predetermined certification. This certification is given to the vehicle 100 by a mobility provider when user U has a contract with that provider to use the charging service via P&C. In this example, user U has the above contract with this provider. The certificate data 115 includes expiration date information 116. The expiration date information 116 indicates the expiration date of the certificate data 115. Thus, the certificate data 115 has an expiration date. When the expiration date passes, the above certification becomes invalid and P&C cannot be executed. The certificate data 115 is used in a communication sequence performed between the vehicle 100 and the power equipment 300 before the start of P&C.

[0017] The communication sequence is a process in which various information is exchanged between the vehicle 100 and the power equipment 300 before the start of P&C. This information includes various information about the vehicle 100 (vehicle information) and specifications information of the power equipment 300 (equipment information). The vehicle information includes authentication information of user U regarding the charging service (e.g., credit card information) and identification information of the vehicle 100 (e.g., manufacturer information and identification number). The equipment information includes identification information of the power equipment 300 (e.g., manufacturer information and identification number).

[0018] The communication sequence is executed for the power facility 300 to confirm that the vehicle 100 is an authenticated vehicle, and for the vehicle 100 to confirm that the power facility 300 is an authentication facility. The authentication facility refers to a power facility that has received a predetermined authentication given by the above mobility provider. To start P&C by executing the communication sequence, it is necessary that the expiration date of the certificate data 115 has not passed. This communication sequence complies with a predetermined international communication standard. This communication standard is, for example, ISO15118-20.

[0019] The DCM120 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. This screen includes a notification screen for notifying the user U to that effect when the expiration date of the certificate data 115 has passed.

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

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

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

[0023] The power equipment 300 is located outside the vehicle 100 and is connected to a commercial power source (not shown). The power equipment 300 includes a connector 301, a power cable 302, a power supply unit 303, a charging start button 305, a communication unit 307, and a control unit 309. The connector 301 is located at the end of the power cable 302. The power supply unit 303 is configured to convert AC power from the commercial power source to DC power and supply the converted power to the vehicle 100 through the power cable 302. The charging start button 305 can receive user input to initiate DC charging. The communication unit 307 is configured to communicate wirelessly with the 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 start of P&C, the control unit 309 verifies in the communication sequence that the vehicle 100 is an authenticated vehicle.

[0024] The certificate server 400 is operated by a mobility provider that offers P&C (Power & Charge) charging services. The certificate server 400 can issue new certificate data separately if the certificate data 115 has expired. The certificate server 400 is configured to communicate wirelessly with the power equipment 300.

[0025] Figure 2 is a diagram illustrating the configuration and function of the control device 150 in detail. Referring to Figure 2, the control device 150 includes a vehicle ECU 155, a charge control ECU 160, and an HLC-ECU 170.

[0026] The vehicle ECU 155 comprehensively controls the vehicle 100. For example, the vehicle ECU 155 controls the DCM 120, the HMI device 130, and the charge control ECU 160.

[0027] The charge control ECU 160 includes a CPU 162 and a memory 164. The CPU 162 performs various arithmetic operations. The memory 164 includes ROM (Read Only Memory) and RAM (Random Access Memory). The ROM stores the program executed by the CPU 162. When the connector 301 is connected to the inlet 140, the charge control ECU 160 sends a start command to the HLC-ECU 170. While the HLC-ECU 170 is starting up, the charge control ECU 160 manages the communication sequence by sequentially receiving information indicating the status of the communication sequence from the HLC-ECU 170, and thereby sends control commands to the HLC-ECU 170 to control the HLC-ECU 170. During DC charging, the charge control ECU 160 sends information indicating the charge status of the battery 105 to the vehicle ECU 155. This information includes the SOC (States of Charge) of the battery 105.

[0028] The HLC-ECU170 includes a CPU172 and a memory174. The CPU172 performs various arithmetic operations. The memory174 includes ROM and RAM. The ROM stores programs executed by the CPU172. The HLC-ECU170 communicates with the power equipment 300 via HLC communication, thereby controlling the communication sequence before P&C and controlling the power supply after P&C has started.

[0029] The HLC-ECU170 is configured to perform an update process to update certificate data 115 if its expiration date has passed at the start of a communication sequence. This update process includes updating (extending) the expiration date of certificate data 115 to a date later than the current date and time. The current date and time is the date and time on which the update process is executed.

[0030] The update process includes sending a certificate request signal to the power equipment 300 via HLC communication. This signal is a request signal that asks the power equipment 300 to issue new certificate data to the certificate server 400, to acquire the issued certificate data, to send an acquisition completion notification to the vehicle 100 indicating that the acquisition of the certificate data is complete, and to transmit the acquired certificate data to the vehicle 100. The update process further includes receiving new certificate data from the power equipment 300, deleting the old, expired certificate data, and storing (installing) the new certificate data as certificate data 115 in the storage device 110.

[0031] If the execution time of the update process exceeds the specified time limit, the update process will time out. This time limit is determined based on the aforementioned communication standard and is, for example, 5 seconds.

[0032] If it is discovered at the start of the communication sequence that the certificate data 115 has expired, it is necessary to access the certificate server 400 to issue new certificate data and update the certificate data 115. However, the data size of the certificate data 115 is generally large. The speed of HLC communication between the vehicle 100 and the power equipment 300 may also decrease. Therefore, if both the certificate data 115 update process and the exchange of vehicle information and equipment information mentioned above are performed by HLC communication, the amount of data in the HLC communication increases. In addition, the communication speed between the power equipment 300 and the certificate server 400 may also decrease. In such cases, the update process takes time. If the update process takes time and times out, the certificate data 115 will not be updated (new certificate data will not be obtained), and the expiration of the certificate data 115 will not be resolved. As a result, the communication sequence will not be completed and will terminate prematurely, and P&C cannot be started. Subsequently, the charging start button 305 may be operated again, but information that was exchanged between the start and termination of the previous communication sequence (some of the vehicle information and equipment information mentioned above) may be exchanged again in the current communication sequence. This is undesirable from the standpoint of information transmission efficiency in communication sequences.

[0033] The control device 150 according to the embodiment has a configuration to address such problems. Specifically, if the control device 150 finds that the certificate data 115 has expired at the start of the communication sequence, it performs a process to pause (sleep) the communication sequence when a timeout of the update process is expected. This process includes sending a pause request to the power equipment 300 to pause the communication sequence.

[0034] With this configuration, the power equipment 300 pauses the communication sequence in response to a pause request. As a result, the communication sequence is paused before the update process times out. Due to the pause in the communication sequence, the amount of data in the HLC communication is reduced, the data processing load on 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 while the communication sequence is paused (before the update process times out), thereby updating the expiration date of the certificate data 115 and resolving the expiration. Therefore, the situation in which the communication sequence is terminated midway due to expiration is avoided. Thus, the efficiency of information transmission in the communication sequence can be improved.

[0035] Whether the execution time of the update process exceeds the standard time (whether a timeout is triggered) is predicted (determined) by the control device 150 based on whether the update process is completed within a predetermined time shorter than the standard time from the start of the update process. The predetermined time is, for example, 3 seconds. In this example, if the update process is not completed within the predetermined time from the start of the update process, a timeout is predicted. If the update process is completed within the predetermined time from the start of the update process, it is determined that a timeout will not be triggered (the update process was completed within the standard time).

[0036] If the update process is not completed within a predetermined time from the start of the update process, it is possible that the update process is taking too long. In this case, the execution time of the communication sequence may exceed the standard time due to the update process, potentially causing a timeout. As described above, the prediction process based on the predetermined time can appropriately predict whether or not a timeout will occur.

[0037] Whether or not the update process is complete is determined by whether or not the HLC-ECU170 has received a notification from the power equipment 300 that the certificate data acquisition is complete and the new certificate data has been received, and has completed the process of storing this certificate data in the storage device 110.

[0038] The control device 150, after the suspension of the communication sequence has been completed and the update process of the certificate data 115 has been completed, executes a process to resume the communication sequence by releasing the suspension. This process includes sending a resume request to the power equipment 300 to resume the communication sequence.

[0039] With this configuration, the communication sequence is restarted with the expiration date resolved. This allows the communication sequence to be completed before the start of P&C. As a result, even if it is discovered that the certificate data 115 has expired at the start of the communication sequence, DC charging can be automatically started without any user operation such as reinserting the connector 301 into the inlet 140 or pressing the charging start button 305.

[0040] Figures 3 and 4 are flowcharts illustrating the processes performed in relation to P&C. This flowchart begins when the connection of connector 301 to inlet 140 is detected.

[0041] Referring to Figure 3, the charge control ECU 160 sends a start command to the HLC-ECU 170 (S105). The HLC-ECU 170 starts up in response to this command and begins a communication sequence with the power equipment 300 (S207). At the start of the communication sequence, the HLC-ECU 170 checks the expiration date of the certificate data 115 based on the expiration date information 116 (S210).

[0042] The HLC-ECU170 determines whether the current date and time is before the expiration date (S215). If the current date and time is before the expiration date, i.e., the expiration date has not passed (YES in S215), the HLC-ECU170 continues the communication sequence. After the completion of the communication sequence, the HLC-ECU170 proceeds to S297 in Figure 4. If the current date and time is after the expiration date, i.e., the expiration date has passed (NO in S215), the HLC-ECU170 notifies the charge control ECU160 that the certificate data 115 has expired (S220). In response to this notification, the charge control ECU 160 instructs the HLC-ECU 170 to update the certificate data 115 (S125). In response to this instruction, the HLC-ECU 170 starts the process of updating the certificate data 115 (S230). Specifically, the HLC-ECU 170 sends a certificate request signal CR-RQ to the power equipment 300.

[0043] The HLC-ECU170 determines whether a timeout for the update process (when the execution time of the update process exceeds the standard time) is expected (S235). Specifically, the HLC-ECU170 determines whether the update process was completed within a predetermined time PT. If a timeout is not expected, i.e., the update process was completed within the predetermined time PT (NO in S235), the HLC-ECU170 proceeds to S297 in Figure 4. If a timeout is expected, i.e., the update process was not completed within the predetermined time PT (YES in S235), the HLC-ECU170 proceeds to S240 in Figure 4.

[0044] Referring to Figure 4, the HLC-ECU170 sends a pause request TS-RQ to the power equipment 300 requesting a pause in the communication sequence (S240).

[0045] The power equipment 300 responds to the pause request TS-RQ to determine whether it can accept the pause of the communication sequence (S342). If the power equipment 300 cannot accept the pause of the communication sequence, for example, if the communication sequence does not conform to the aforementioned communication standard (NO in S342), the processing of the power equipment 300 ends. If the power equipment 300 can accept the pause of the communication sequence (YES in S342), it pauses the communication sequence. Then, the power equipment 300 notifies the HLC-ECU170 of its acceptance of the pause of the communication sequence (S345). Specifically, the power equipment 300 sends a pause acceptance notification to the HLC-ECU170. Subsequently, the power equipment 300 has the certificate server 400 issue new certificate data and sends the issued certificate data to the HLC-ECU170 via HLC communication (S360).

[0046] The HLC-ECU170 determines whether it has received a temporary pause acceptance notification from S240 within a predetermined period (for example, within 2 seconds) (S250). If the HLC-ECU170 has not received this notification within the predetermined period (NO in S250), it notifies the charge control ECU160 of this fact. In this case, the update process times out. In response to the notification from the HLC-ECU170, the charge control ECU160 sends an expiration notification to the vehicle ECU155 indicating that the certificate data 115 has expired, and this notification is then sent to the mobile terminal 500 via the DCM120 and server 200 (S155). In response to the expiration notification, the mobile terminal 500 displays a notification screen to inform user U that the certificate data 115 has expired (S60). This screen may be displayed to inform that an error caused by the expiration has occurred. This screen may be displayed on the HMI device 130 of the vehicle 100.

[0047] If the HLC-ECU170 receives a notification of acceptance of temporary suspension within a predetermined period (YES in S250), it receives newly issued certificate data from the power equipment 300 via HLC communication (S265). The HLC-ECU170 stores this certificate data as certificate data 115 in the storage device 110, replacing the old certificate data, and thereby completes the update process (S270).

[0048] The HLC-ECU170 sends an expiration date renewal notification to the charge control ECU160 (S275). This notification indicates that the expiration date of the certificate data 115 has been renewed due to the completion of the renewal process. The charge control ECU160 sends this notification to the vehicle ECU155, which then transmits the notification to the mobile terminal 500 via the DCM120 and server 200 (S185). In response to the expiration date renewal notification, the mobile terminal 500 displays a notification screen to inform user U of the renewal of the expiration date of the certificate data 115 (S90). This screen may also be displayed on the HMI device 130 of the vehicle 100.

[0049] After S275, the HLC-ECU170 sends a restart request RS-RQ to the power equipment 300 requesting the resumption of the communication sequence (S292). The power equipment 300 responds to the restart request RS-RQ and resumes the communication sequence (S394). The communication sequence is then completed.

[0050] After the communication sequence is completed, the HLC-ECU170 performs a process to start P&C (external charging) (S297). This process includes sending a power supply start command to the power equipment 300 in accordance with the command from the charging control ECU160, which commands the start of power supply to the vehicle 100. In response to the power supply start command, the power equipment 300 starts supplying power to the vehicle 100. This starts P&C.

[0051] As described above, according to this embodiment, the control device 150 temporarily suspends the communication sequence when a timeout is predicted for the certificate data 115 update process. This prevents the communication sequence from being terminated prematurely due to the expiration of the certificate data 115. Therefore, the efficiency of information transmission in the communication sequence can be improved.

[0052] If the certificate data 115 has expired, the control device 150 may send a notification to the mobile terminal 500 via the DCM 120 and server 200 prompting the renewal of the certificate data 115, but user U may not notice this notification. The embodiment is effective when user U does not notice such a notification when inserting the connector 301 into the inlet 140 (immediately before the start of P&C).

[0053] [Modified examples of the embodiment] If the update process takes too long and times out despite the communication sequence being paused, it is possible that the communication related to the update process is unstable. This communication is, for example, wireless communication between the power equipment 300 and the certificate server 400. If the communication is unstable as described above, it is highly likely that a timeout will occur when retrying the update process, making it difficult to update the certificate data 115. In this case, it is preferable that the communication sequence be completed completely.

[0054] In this modified version, the HLC-ECU170 performs a process to completely terminate the communication sequence if the update process times out. This process includes sending a termination request to the power equipment 300 requesting the termination of the communication sequence.

[0055] With this configuration, if the update process times out (for example, if the communication status is considered unstable), the communication sequence will terminate completely. This prevents situations where the communication sequence is paused for an extended period, resulting in wasted time.

[0056] Figure 5 is a flowchart illustrating the processes performed by the HLC-ECU170 in this modified example. Referring to Figure 5, the processes S250 and S155 are the same as those shown in Figure 4.

[0057] If the update process times out (NO in S250), the HLC-ECU170 sends a termination request EN-RQ to the power equipment 300 requesting the termination of the communication sequence (S252). The power equipment 300 responds to the termination request EN-RQ and completely terminates the communication sequence. After S252, the process proceeds to S155. In this case, the expiration notification in S155 may include information to inform user U that updating the certificate data 115 is difficult due to unstable communication conditions.

[0058] As described above, with this modified version, if the update process times out, the communication sequence is completely terminated. This avoids a situation where the communication sequence is paused for an extended period, resulting in wasted time.

[0059] [Other variations] Vehicle 100 may also be other types of electric vehicles, such as a plug-in hybrid electric vehicle (PHEV), which may include an engine, as long as external charging is possible.

[0060] The power supplied by the power equipment 300 is assumed to be DC power, but it may also be AC ​​power. External charging using AC power is also referred to as "AC charging". When AC charging is performed on the vehicle 100, the vehicle 100 includes a charging device (not shown). This 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. Thus, external charging (P&C) is not limited to DC charging, but may also be AC ​​charging.

[0061] The control device 150 may predict whether or not a timeout will occur during the update process based on the data size of the certificate data 115 (certificate data before update). For example, if this data size is greater than or equal to a threshold, a timeout is predicted to occur. On the other hand, if this data size is less than the threshold, a timeout is predicted not to occur (the update process will be completed within the standard time). This information indicating the data size is stored in advance in the storage device 110.

[0062] The DCM120 may be configured to communicate wirelessly with the certificate server 400. In this case, the control device 150 may obtain new certificate data from the certificate server 400 via wireless communication through the DCM120 instead of HLC communication, and perform an update process for the certificate data 115 based on the obtained data. [Industrial applicability]

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

[0064] 1 charging system, 100 vehicles, 105 batteries, 110 storage devices, 115 certificate data, 150 control devices, 300 power equipment, 400 certificate servers, 500 mobile terminals.

Claims

1. A vehicle capable of external charging, which charges an on-board energy storage device using power equipment installed outside the vehicle, A storage device that stores certificate data for permitting the execution of the aforementioned external charging, The system includes a control device that controls a communication sequence performed between the power equipment and the vehicle before the start of the external charging, The aforementioned certificate data has an expiration date. The control device is If the expiration date has expired at the start of the aforementioned communication sequence, an update process is executed to update the certificate data. If a timeout is predicted for the update process, the communication sequence is temporarily suspended. A vehicle that resumes the communication sequence after the update process is completed following a temporary suspension of the communication sequence.

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

3. The vehicle according to claim 2, wherein the control device terminates the communication sequence when the update process times out.

4. It comprises an inlet configured to be connectable to a connector of the aforementioned power equipment and configured to receive power supplied from the aforementioned power equipment, The communication sequence is initiated in response to the connection of the connector to the inlet. In the aforementioned communication sequence, the power equipment confirms that the vehicle has received the prescribed certification. The vehicle according to claim 1, wherein the external charging includes plug-and-charge, which is performed automatically after the power equipment has confirmed that the vehicle is certified.

Images