Charging control device, vehicle, and charging control method

Abstract

To provide a charging control device capable of inhibiting a time required for completing charging of a vehicle from being prolonged.SOLUTION: A charging control device 150 includes: a signal reception unit 154 (an acquisition unit) for acquiring charging schedule information on a scheduled timing of charging; and a processor 151 (a signal output unit) for outputting a request signal for updating a digital certificate when a period of validity of the digital certificate expires by the scheduled timing of the charging.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present disclosure relates to a charging control device, a vehicle, and a charging control method.

Background Art

[0002] Japanese Patent No. 4353197 (Patent Document 1) discloses a vehicle charged by a charging device. The charging device reads an ID code from a transponder key of the vehicle's immobilizer system and transmits the read ID code to the vehicle. Then, authentication is performed in the vehicle, and if the authentication result is normal, the supply of charging power is permitted.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, when the expiration date of the transponder key has passed during charging, it is necessary to update the transponder key. In this case, time is required to update the transponder key during charging, and the time required to complete charging becomes long.

[0005] The present disclosure has been made to solve the above problems, and an object thereof is to provide a charging control device, a vehicle, and a charging control method capable of suppressing an increase in the time required to complete charging of a vehicle.

Means for Solving the Problems

[0006] The charging control device according to the first aspect of this disclosure is a charging control device for a vehicle that controls charging authenticated by a digital certificate, and comprises: an acquisition unit that acquires charging schedule information relating to the scheduled time of charging; and a signal output unit that outputs a request signal to renew the digital certificate if the digital certificate has expired at the scheduled time of charging.

[0007] In the charging control device according to the first aspect of this disclosure, as described above, if the digital certificate has expired at the scheduled time of charging, a request signal to renew the digital certificate is output. This allows the digital certificate to be renewed by the scheduled time of charging. As a result, it becomes unnecessary to renew the digital certificate when charging starts. This helps to suppress the time required to complete charging of the vehicle.

[0008] In the charging control device relating to the first aspect described above, preferably, the acquisition unit acquires charging schedule information from at least one of an input terminal provided on the vehicle and a user terminal used by the vehicle's user. With this configuration, information on the scheduled timing of charging can be easily obtained based on the charging schedule information from at least one of the vehicle's input terminal and the user's user terminal.

[0009] In the charging control device relating to the first aspect described above, preferably, the charging is a type of charging in which the vehicle user is authenticated in response to the connection of a charging connector to the vehicle. With this configuration, it is possible to suppress the time required to complete charging when the vehicle user is authenticated in response to the connection of a charging connector to the vehicle.

[0010] In the charging control device relating to the first aspect described above, preferably, the signal output unit outputs a request signal to activate a button for initiating the renewal of a digital certificate, which is displayed on at least one of the input terminal provided in the vehicle and the user terminal used by the vehicle's user. With this configuration, the user can easily perform the operation to renew the digital certificate (the operation of selecting the button).

[0011] In the charging control device relating to the first aspect described above, preferably, the signal output unit outputs a request signal when the vehicle's battery SOC is below a predetermined threshold and the digital certificate has expired. Here, when the vehicle's battery SOC is below a predetermined threshold, charging is performed relatively quickly compared to when the battery SOC is above a predetermined threshold. Therefore, outputting a request signal when the vehicle's battery SOC is below a predetermined threshold and the digital certificate has expired is particularly effective in that it ensures the digital certificate is updated before charging begins.

[0012] In the charging control device relating to the first aspect described above, preferably, the signal output unit outputs a request signal when the charging frequency based on the charging history data is higher than a predetermined threshold and the digital certificate has expired. Here, during periods when the charging frequency is higher than a predetermined threshold, there is a higher probability that charging will be performed compared to periods when the charging frequency is below the predetermined threshold. Therefore, outputting a request signal when the charging frequency is higher than a predetermined threshold and the digital certificate has expired is particularly effective in ensuring that the digital certificate is updated when charging is started.

[0013] In the charging control device relating to the first aspect described above, preferably, the signal output unit outputs a request signal when the amount of power required to reach the vehicle's destination is higher than the remaining power of the vehicle's battery, and the digital certificate has expired. Here, when the required power is higher than the remaining power of the battery, charging is performed relatively quickly compared to when the remaining power is less than or equal to the required power. Therefore, outputting a request signal when the required power is higher than the remaining power of the vehicle's battery, and the digital certificate has expired, is particularly effective in ensuring that the digital certificate is updated before charging begins.

[0014] In the charging control device relating to the first aspect described above, preferably, the signal output unit outputs a request signal when the charging connector is connected to the vehicle. With this configuration, the digital certificate can be updated while the charging connector is connected to the vehicle.

[0015] The vehicle relating to the second aspect of this disclosure is a vehicle whose charging is authenticated by a digital certificate, and comprises a battery to which power is supplied by charging, and a storage unit for storing the digital certificate. If the digital certificate has expired at the scheduled time of charging, the digital certificate is renewed.

[0016] In the vehicle relating to the second aspect of this disclosure, as described above, if the digital certificate has expired at the scheduled time for charging, the digital certificate is renewed. This makes it possible to provide a vehicle that can suppress the time required to complete charging of the vehicle.

[0017] A charging control method relating to the third aspect of this disclosure is a charging control method by a vehicle charging control device that controls charging authenticated by a digital certificate, comprising the steps of: acquiring charging schedule information relating to the scheduled time of charging; and outputting a request signal to renew the digital certificate if the digital certificate has expired at the scheduled time of charging.

[0018] In the charging control method according to the third aspect of the present disclosure, as described above, when the expiration date of the digital certificate has expired at the scheduled charging time, a request signal for updating the digital certificate is output. Thereby, it is possible to provide a charging control method capable of suppressing an increase in the time required until the charging of the vehicle is completed.

Advantages of the Invention

[0019] According to the present disclosure, it is possible to suppress an increase in the time required until the charging of the vehicle is completed.

Brief Description of the Drawings

[0020] [Figure 1] It is a diagram showing the configuration of a vehicle and a charging stand according to an embodiment. [Figure 2] It is a diagram showing an example of a fee system included in a digital certificate. [Figure 3] It is a diagram showing a charging sequence according to an embodiment. [Figure 4] It is a sequence diagram showing control for updating a digital certificate according to an embodiment. [Figure 5] It is a diagram showing an update button for updating a digital certificate. [Figure 6] It is a diagram showing details of step S100 in FIG. 4. [Figure 7] It is the first diagram showing a flow for transmitting a request signal for requesting a digital certificate. [Figure 8] It is the second diagram showing a flow for transmitting a request signal for requesting a digital certificate. [Figure 9] It is the third diagram showing a flow for transmitting a request signal for requesting a digital certificate. [Figure 10] It is a sequence diagram showing control for updating a digital certificate according to a modification example of an embodiment.

Modes for Carrying Out the Invention

[0021] The embodiments of this disclosure will be described in detail below with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated.

[0022] Figure 1 is a schematic diagram showing the overall configuration of the charging system 1 according to this embodiment. The charging system 1 comprises an electric vehicle 100, a charging station 300, and a server 400.

[0023] Server 400 stores information about the electric vehicle 100. For example, Server 400 stores a digital certificate for the electric vehicle 100. Here, the digital certificate may be, for example, an OEM (Original Equipment Manufacture) certificate or a charging contract certificate. The charging contract certificate certifies the contents of the contract concluded between the mobility operator (MO) that provides the charging service and the user of the electric vehicle 100. In this embodiment, the case where the digital certificate is a charging contract certificate is described, but it may also be an OEM certificate or the like.

[0024] The electric vehicle 100 includes a battery 200 for storing power for driving. The electric vehicle 100 is configured to be able to drive using the power stored in the battery 200. In this embodiment, the electric vehicle 100 is an electric vehicle (BEV) without an engine (internal combustion engine), but it may also be a hybrid vehicle (HEV) or a plug-in hybrid vehicle (PHEV) equipped with an engine. Note that the electric vehicle 100 is an example of a "vehicle" in this disclosure.

[0025] The electric vehicle 100 includes an electronic control unit (ECU) 150. The ECU 150 is configured to control the charging and discharging of the battery 200. The ECU 150 includes a processor 151, a random access memory (RAM) 152, a storage device 153, and a signal receiving unit 154. The processor 151 and the signal receiving unit 154 are examples of the "signal output unit" and "signal acquisition unit" as defined in this disclosure, respectively. The ECU 150 is also an example of the "charging control device" as defined in this disclosure. The storage device 153 is also an example of the "storage unit" as defined in this disclosure.

[0026] The ECU150 may be a computer. The processor 151 may be a CPU (Central Processing Unit).

[0027] RAM152 functions as working memory to temporarily store data processed by processor 151.

[0028] The storage device 153 is configured to store the stored information. In addition to the program, the storage device 153 stores information used by the program (for example, maps, formulas, and various parameters). When the processor 151 executes the program stored in the storage device 153, various controls in the ECU 150 are performed.

[0029] Here, the storage device 153 stores a digital certificate (see Figure 2). In the example shown in Figure 2, the digital certificate contains information about the charging fee, which is determined by the time and the amount of charging power. Specifically, the digital certificate contains information indicating that from 0:00 AM to 1:00 AM, the maximum amount of charging power is 15 kW and the charging fee is 0.25 EUR / kWh. The digital certificate also contains information indicating that from 1:00 AM to 2:00 AM, the charging fee is 0.30 EUR / kWh for charging power up to 10 kW, 0.20 EUR / kWh for charging power from 10 kW to 20 kWh, and 0.10 EUR / kWh for charging power from 20 kW to 30 kWh.

[0030] Furthermore, the digital certificate includes identification information associated with the fee structure shown in Figure 2. This identification information includes, for example, the vehicle information (VIN) of the electric vehicle 100, the personal information of the user of the electric vehicle 100, and card information used for paying the charging fee.

[0031] Furthermore, digital certificates have an expiration date. The ECU150 controls charging authenticated by the digital certificate. If the digital certificate has expired, it needs to be renewed.

[0032] Referring again to Figure 1, the signal receiving unit 154 receives predetermined signals from other devices of the ECU 150. For example, the signal receiving unit 154 receives predetermined signals (information) from the HMI device 120 or the communication device 140, which will be described later.

[0033] The monitoring module 130 includes various sensors to detect the state of the battery 200 (e.g., voltage, current, and temperature) and outputs the detection results to the ECU 150. In addition to the above sensor functions, the monitoring module 130 may also be a Battery Management System (BMS) that further includes a State of Charge (SOC) estimation function, a State of Health (SOH) estimation function, a cell voltage equalization function, a diagnostic function, and a communication function. The ECU 150 can acquire the state of the battery 200 (e.g., temperature, current, voltage, SOC, and internal resistance) based on the output of the monitoring module 130. The battery 200 is charged (externally charged) by power supplied from the charging station 300.

[0034] The electric vehicle 100 further comprises a drive unit 110, an HMI (Human Machine Interface) device 120, a communication device 140, an inlet 160, and drive wheels W.

[0035] The drive unit 110 includes a PCU (Power Control Unit) and an MG (Motor Generator) (not shown), and is configured to drive the electric vehicle 100 using the power stored in the battery 200.

[0036] The PCU consists of components such as an inverter, a converter, and a relay (hereinafter referred to as "SMR (System Main Relay)"). The PCU is controlled by the ECU150.

[0037] The MG is, for example, a three-phase AC motor generator. The MG is driven by the PCU and configured to rotate the drive wheel W. The PCU drives the MG using power supplied from the battery 200. The MG is also configured to perform regenerative power generation and supply the generated power back to the battery 200.

[0038] The SMR is configured to switch between connecting and disconnecting the power path from battery 200 to PCU. The SMR is closed (connected) when the electric vehicle 100 is running.

[0039] The HMI device 120 includes an input device and a display device. The HMI device 120 may also include a touch panel display. The HMI device 120 is an example of an "input terminal" as described herein.

[0040] The communication device 140 communicates with a mobile terminal 500 (e.g., a smartphone) used by a user of an electric vehicle 100. The communication device 140 may include a Data Communication Module (DCM) or a 5G (fifth-generation mobile communication system) compatible communication interface. The mobile terminal 500 is an example of a "user terminal" in this disclosure.

[0041] The inlet 160 is configured to allow insertion of the charging connector 301 of the charging station 300. The charging connector 301 is located at the end of the charging cable 302 attached to the charging station 300. The electric vehicle 100 is electrically connected to the charging station 300 by inserting the charging connector 301 into the inlet 160. This enables the exchange of power between the charging station 300 and the electric vehicle 100.

[0042] <Charging Sequence> Figure 3 is a sequence diagram showing the charging process between the electric vehicle 100, the charging station 300, and the server 400.

[0043] In step S10, the charging process between the electric vehicle 100 and the charging station 300 is initiated.

[0044] In step S20, a secure communication connection is established between the electric vehicle 100 and the charging station 300. Specifically, UDP (User Datagram Protocol), TCP (Transmission Control Protocol), and TLS (Transport Layer Security) are used to establish the communication connection.

[0045] In step S30, various authentication processes are performed between the electric vehicle 100 and the charging station 300. For example, processes such as identity verification, data verification, and authorization are performed.

[0046] In step S40, settings are performed. For example, target settings and charge scheduling settings are performed.

[0047] In step S50, charging takes place between the electric vehicle 100 and the charging station 300. In step S60, charging is completed.

[0048] If the digital certificate has expired, it will need to be renewed. In this case, time will be required to renew the digital certificate during charging, which will increase the overall charging time.

[0049] Therefore, in this embodiment, the processor 151 of the ECU 150 outputs a request signal to renew the digital certificate if the digital certificate has expired by the scheduled time of charging. This makes it possible to more reliably renew the digital certificate by the scheduled time of charging. Specifically, the processor 151 determines whether a later scheduled time of charging is before the expiration date of the digital certificate. If the processor 151 determines that the scheduled time of charging is before the expiration date of the digital certificate, it outputs (generates) the request signal by the scheduled time of charging.

[0050] <Digital Certificate Renewal> Refer to Figures 4 to 6 to explain the sequence control for renewing digital certificates.

[0051] In step S100, the ECU 150 (processor 151) determines whether or not there is a charging schedule (plan) for the electric vehicle 100. If there is a charging schedule (Yes in S100), the process proceeds to step S110. If there is no charging schedule (No in S100), the process proceeds to step S160. Details of step S100 will be described later.

[0052] In step S110, the ECU 150 (processor 151) determines whether the digital certificate has expired at the scheduled charging time based on the charging schedule information obtained in step S100. If the digital certificate has expired at the scheduled charging time (Yes in S110), the process proceeds to step S120. If the digital certificate has not expired at the scheduled charging time (No in S110), the process proceeds to step S160.

[0053] In step S120, the ECU 150 (processor 151) determines whether the charging performed with the charging station 300 is PnC charging (charging in which user authentication is performed in response to the charging connector being connected to the vehicle). If PnC charging is performed (Yes in S120), the process proceeds to step S130. If PnC charging is not performed (No in S120), the process proceeds to step S160.

[0054] In step S130, the ECU 150 (processor 151) generates a request signal (AuthorizationSetupReq) requesting a digital certificate. The process then proceeds to step S140.

[0055] In step S140, the ECU 150 (processor 151) determines whether the charging connector 301 is connected to the inlet 160 of the electric vehicle 100 and whether a communication connection has been established (see step S20 in Figure 3). If a communication connection has been established (Yes in S140), the process proceeds to step S150. If a communication connection has not been established (No in S140), the process in step S140 is repeated. Note that the processes from steps S100 to S140 can basically be executed before plugging in, but the process in step S140 is determined to be Yes after plugging in.

[0056] In step S150, the ECU 150 sends the request signal generated in step S130 to the server 400. The request signal is sent to the charging station 300 through the connection terminal 161 of the inlet 160 (see Figure 1), the charging connector 301, and the charging cable 302. The charging station 300 then sends the received request signal to the server 400. Next, the processing in the electric vehicle 100 proceeds to step S160.

[0057] The request signal transmitted in step S150 is a signal to activate the update button 121 (see Figure 5) for initiating the digital certificate update. The update button 121 is displayed, for example, on the display screen 122 of the HMI device 120. Alternatively, the update button 121 may be displayed on the mobile terminal 500. Furthermore, the update button 121 may be displayed on both the mobile terminal 500 and the HMI device 120. Note that the update button 121 is just one example of a "button" in this disclosure.

[0058] In step S200, the server 400 determines whether or not it has received a request signal for a digital certificate. If it has received a request signal (Yes in S200), the process proceeds to step S210. If it has not received a request signal (No in S200), the process proceeds to step S220.

[0059] In step S210, the server 400 sends a response signal (AuthorizationRes) to the electric vehicle 100 for sending a digital certificate in response to the request signal. Specifically, the response signal is sent to the electric vehicle 100 via the charging station 300, similar to the request signal.

[0060] In step S220, the server 400 transmits a digital certificate to the electric vehicle 100. This transmission is a periodic transmission performed at predetermined intervals. Note that the timing of the execution of step S220 is not limited to the example shown in Figure 4.

[0061] In step S160, the ECU 150 (processor 151) determines whether the digital certificate transmitted from the server 400 in step S210 (or S220) has been received by the signal receiving unit 154. If the digital certificate has been received (Yes in S160), the process proceeds to step S170. If the digital certificate has not been received (No in S160), the process in step S160 is repeated.

[0062] In step S170, the ECU 150 (processor 151) activates the update button 121 (see Figure 5) for updating the digital certificate. At this time, the ECU 150 may also notify the HMI device 120 or the mobile terminal 500 via an application that the update button 121 has been activated.

[0063] In step S180, the ECU 150 (processor 151) determines whether the update button 121 has been selected (touched). If the update button 121 is selected (Yes in S180), the process proceeds to step S190. If the update button 121 is not selected (No in S180), the process in step S180 is repeated.

[0064] In step S190, the ECU 150 (processor 151) performs the digital certificate update process. However, if the auxiliary voltage of the electric vehicle 100 drops below a predetermined value, the update process may be stopped.

[0065] In this embodiment, the processing from step S150 onward is performed in the authentication step of step S30. Alternatively, the processing from step S150 onward may be performed in the setting step of step S40.

[0066] <Checking the charging schedule> As shown in Figure 6, the process in step S100 includes the process in step S101 and the process in step S102.

[0067] In step S101, the ECU 150 (processor 151) determines whether charging schedule information is set in the HMI device 120 or the mobile terminal 500. If charging schedule information is set (Yes in S101), the process proceeds to step S101. If charging schedule information is not set (No in S101), the process proceeds to step S160.

[0068] Specifically, the ECU 150 (processor 151) sends a signal to the HMI device 120 and the mobile terminal 500 to inquire whether or not charging schedule information has been set. Note that the signal inquiring whether or not charging schedule information has been set may be sent to either the HMI device 120 or the mobile terminal 500.

[0069] Furthermore, the HMI device 120 and the mobile terminal 500 (app) may allow users to set whether or not to charge using a charging station 300 that supports PnC charging. Users may also be able to set the desired charging station 300 and the charging time (and arrival and departure times).

[0070] In step S102, the ECU 150 (processor 151) acquires information on the charging schedule (scheduled charging time) set in the HMI device 120 or the mobile terminal 500. Specifically, the ECU 150 (processor 151) transmits a request signal for requesting the charging schedule information to the terminal that has responded that the charging schedule information is set.

[0071] <Request for Digital Certificate Based on SOC> Next, referring to FIG. 7, a method of transmitting a request signal for a digital certificate to the server 400 based on the SOC (State Of Charge) of the battery 200 will be described. Note that the processing in FIG. 7 is executed at a predetermined cycle.

[0072] In step S300, the ECU 150 (processor 151) determines whether the SOC of the battery 200 has become equal to or less than a predetermined threshold (for example, 20%). If the SOC is equal to or less than the predetermined threshold (Yes in S300), the process proceeds to step S310. If the SOC is higher than the predetermined threshold (No in S300), the process proceeds to step S160 (see FIG. 4).

[0073] In step S310, the ECU 150 (processor 151) determines whether the expiration date of the digital certificate has expired. If the expiration date of the digital certificate has expired (Yes in S310), the process proceeds to step S120 (see FIG. 4). If the expiration date of the digital certificate has not expired (No in S310), the process proceeds to step S160.

[0074] <Request for Digital Certificate Based on Charging History> Next, referring to FIG. 8, a method of transmitting a request signal for a digital certificate to the server 400 based on the charging history of the battery 200 will be described. Note that the processing in FIG. 8 is executed at a predetermined cycle.

[0075] In step S400, the ECU 150 (processor 151) determines whether the current time period is a time period in which the charging frequency based on past charging history is above a predetermined threshold. If the charging frequency is above the predetermined threshold (Yes in S400), the process proceeds to step S310. If the charging frequency is below the predetermined threshold (No in S400), the process proceeds to step S160. For example, the ECU 150 may determine that a time period in which charging has been performed 10 or more times within the past 30 days is a time period in which the charging frequency is above the predetermined threshold. Note that the charging history data may be obtained from, for example, the server 400.

[0076] Since the process in step S310 is the same as in Figure 7, a repeated explanation will not be provided.

[0077] <Request for a digital certificate based on remaining energy> Next, referring to Figure 9, we will explain how to send a digital certificate request signal to the server 400 based on the remaining power of the battery 200. Note that the process in Figure 9 is performed at predetermined intervals.

[0078] In step S500, the ECU 150 (processor 151) determines whether the remaining power of the battery 200 is less than the amount of power required for the electric vehicle 100 to reach its destination. If the remaining power is less than the required power (Yes in S500), the process proceeds to step S310. If the remaining power is equal to or greater than the required power (No in S500), the process proceeds to step S160. The remaining power may be calculated by the ECU 150 based on the State of Charge (SOC) of the battery 200 and the power capacity of the battery 200. The required power may also be calculated by the ECU 150 based on the distance between the destination set in the HMI device 120, etc., and the current location.

[0079] Since the process in step S310 is the same as in Figure 7, a repeated explanation will not be provided.

[0080] As described above, in this embodiment, the ECU 150 (processor 151) outputs a request signal to renew the digital certificate if the digital certificate has expired at the scheduled time for charging. This allows the process of renewing the digital certificate to be started prior to the scheduled time for charging. As a result, it is possible to suppress the increase in the time required to complete the charging of the electric vehicle 100.

[0081] Furthermore, the process of generating the digital certificate request signal can be completed before plugging in. As a result, charging can be started more quickly compared to when the above process is performed after plugging in.

[0082] In the above embodiment, an example was shown in which a request signal for a digital certificate is transmitted to the server 400 while the charging connector 301 is inserted into the inlet 160, but the disclosure is not limited thereto. The request signal may also be transmitted to the server 400 via the communication device 140 while the charging connector 301 is not inserted into the inlet 160. In this case, the digital certificate may be updated while the charging connector 301 is not inserted into the inlet 160. For example, even while the electric vehicle 100 is running, the update may be performed if an auxiliary power supply is provided for the electric vehicle 100.

[0083] Specifically, control may be performed according to the sequence shown in Figure 10. The sequence shown in Figure 10 omits step S140 of the sequence shown in Figure 4, and all processes up to step S190 are performed before plugging in. As a result, the digital certificate update is already completed when the electric vehicle 100 is connected to the charging station 300 (when it is plugged in), which further reduces the time required for the electric vehicle 100 to be fully charged.

[0084] The above embodiment shows an example in which the digital certificate is updated in response to the selection of the activated update button 121, but the disclosure is not limited thereto. For example, the digital certificate may be automatically updated in response to its installation in the electric vehicle 100.

[0085] In the above embodiment, an example was shown in which a request signal for a digital certificate is sent to the server 400 when the SOC is below a threshold and the digital certificate has expired, but the disclosure is not limited thereto. For example, the request signal may be sent to the server 400 when it is determined that the digital certificate will expire within a predetermined time (for example, within 2 hours) of the time when the SOC falls below the threshold.

[0086] In the above embodiment, an example was shown in which a request signal for a digital certificate is sent to the server 400 when the charging frequency is above a threshold during the current time period, but the disclosure is not limited thereto. The request signal may also be sent to the server 400 when it is determined that the charging frequency will be above a threshold during a time period later than the current time period, and the digital certificate will expire during that later time period (a time before that later time period).

[0087] In the above embodiment, an example was shown in which a request signal for a digital certificate is sent to the server 400 when the remaining power of the battery 200 is less than the power required to reach the destination and the digital certificate has expired, but the disclosure is not limited thereto. For example, the request signal may be sent to the server 400 when it is determined that the digital certificate will expire within a predetermined time (for example, within 2 hours) of the time when the remaining power becomes less than the required power.

[0088] The above embodiment shows an example in which the transmission of a digital certificate request signal is determined based on whether or not there is a charging schedule, but the disclosure is not limited thereto. The transmission of the request signal may also be determined based on whether or not the scheduled charging time falls within a predetermined period.

[0089] In the above embodiment, an example was shown in which the update button 121 is activated after the digital certificate is received, but the disclosure is not limited thereto. For example, the update button 121 may be activated at the timing when the digital certificate request signal is generated, or the update button 121 may be selected before the digital certificate is received. In this case, the digital certificate update starts when the digital certificate is installed in the electric vehicle 100.

[0090] Furthermore, the configurations (processes) of the above embodiments and each of the above modified examples may be combined with each other.

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

[0092] 100 Electric vehicle (vehicle), 120 HMI device (input terminal), 121 Update button (button), 150 ECU (charging control unit), 151 Processor (signal output unit), 153 Storage device (storage unit), 154 Signal receiving unit (acquisition unit), 200 Battery, 301 Charging connector, 500 Mobile terminal (user terminal).

Claims

1. A vehicle charging control device that controls charging performed using power supplied from a charging facility and authenticated by a digital certificate, An acquisition unit that acquires charging schedule information regarding the planned timing of the aforementioned charging, A charging control device comprising: a signal output unit that outputs a request signal to renew the digital certificate before a communication connection is established between the vehicle and the charging equipment if the digital certificate has expired at the scheduled time of charging.

2. The charging control device according to claim 1, wherein the acquisition unit acquires the charging schedule information from at least one of an input terminal provided on the vehicle and a user terminal used by the user of the vehicle.

3. The charging control device according to claim 1 or 2, wherein the charging is a charging in which the user of the vehicle is authenticated in response to the connection of a charging connector to the vehicle.

4. The charging control device according to claim 1 or 2, wherein the signal output unit outputs the request signal to activate a button for initiating the renewal of the digital certificate, which is displayed on at least one of the input terminal provided in the vehicle and the user terminal used by the user of the vehicle.

5. The charging control device according to claim 1 or 2, wherein the signal output unit outputs the request signal when the State of Charge (SOC) of the vehicle's battery is below a predetermined threshold and the digital certificate has expired.

6. The charging control device according to claim 1 or 2, wherein the signal output unit outputs the request signal when the frequency of charging based on the charging history data is higher than a predetermined threshold during a period of time, and the digital certificate has expired.

7. The charging control device according to claim 1 or 2, wherein the signal output unit outputs the request signal when the amount of power required for the vehicle to reach its destination is higher than the remaining power of the vehicle's battery, and the digital certificate has expired.

8. The charging control device according to claim 1 or 2, wherein the signal output unit outputs the request signal when the charging connector is connected to the vehicle.

9. A vehicle capable of performing charging using power supplied from a charging facility and authenticated by a digital certificate, A battery to which power is supplied by the aforementioned charging, The system comprises a storage unit for storing the aforementioned digital certificate, A vehicle in which, if the digital certificate has expired at the scheduled time of charging, the renewal of the digital certificate is initiated before a communication connection is established with the charging equipment.

10. A charging control method by a vehicle charging control device that controls charging performed using power supplied from a charging facility and authenticated by a digital certificate, A step of obtaining charging schedule information regarding the planned timing of the aforementioned charging, A charging control method comprising the step of outputting a request signal to renew the digital certificate before a communication connection is established between the vehicle and the charging equipment, if the digital certificate has expired at the scheduled time of charging.

11. A vehicle charging control device that controls charging authenticated by a digital certificate, An acquisition unit that acquires charging schedule information regarding the planned timing of the aforementioned charging, The system includes a signal output unit that outputs a request signal to renew the digital certificate if the digital certificate has expired at the scheduled time of charging, The signal output unit outputs the request signal when the charging frequency based on the charging history data is higher than a predetermined threshold during a certain period of time, and the digital certificate has expired.

Images