Authentication systems, vehicles, and terminals

The authentication system addresses unnecessary certificate renewal notifications by selectively sending alerts based on the request source, improving user experience by minimizing irrelevant notifications.

JP2026067653APending Publication Date: 2026-04-21TOYOTA JIDOSHA KK
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
TOYOTA JIDOSHA KK
Filing Date
2024-10-09
Publication Date
2026-04-21

AI Technical Summary

Technical Problem

Existing authentication systems frequently notify users about the expiration and renewal of digital certificates, leading to unnecessary notifications.

Method used

An authentication system that selectively sends notifications based on the source of the request for certificate information transmission, ensuring that notifications are only sent when requested by the user or vehicle, thereby suppressing unnecessary alerts.

Benefits of technology

This approach reduces unnecessary notifications to users by only sending notifications when they are relevant, enhancing user experience and reducing unwanted alerts.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026067653000001_ABST
    Figure 2026067653000001_ABST
Patent Text Reader

Abstract

Suppress unnecessary notifications to the user. [Solution] The server performs a process that includes the steps of sending certificate information (S102) when it is determined that there is a request to obtain a certificate (YES in S100), sending download progress information (S106) when it is determined that the requester is a terminal (YES in S104), sending write progress information (S110) when it is determined that the download is complete (YES in S108), and notifying the result (S114) when it is determined that the write is complete (YES in S112).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to an authentication system.

Background Art

[0002] Japanese Patent Application Publication No. 2022-527902 (Patent Document 1) discloses a charging station that verifies a vehicle digital signature received from a vehicle using a vehicle public key and enables power supply to the vehicle in response to successful verification.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Information about the above vehicle digital signature, etc. is stored in the control device of the vehicle via a communication network. However, such information has an expiration date and is written to the control device of the vehicle each time, so if the user is to be notified each time the progress of the writing changes, the user will receive such notifications frequently. Therefore, unnecessary notifications may be given to the user.

[0005] This disclosure has been made to solve the above-described problems, and an object thereof is to provide an authentication system, a vehicle, and a terminal that suppress unnecessary notifications to the user.

Means for Solving the Problems

[0006] An authentication system relating to one aspect of this disclosure comprises a server that transmits certificate information for a digital certificate used in the authentication process when using a power station that transmits power to a power storage device mounted on an electric vehicle, and a vehicle that includes a storage device that stores the certificate information received from the server. The server switches whether or not to send a notification regarding the writing of the certificate information while the certificate information is being written to the storage device, depending on the source of the request for transmission of the certificate information to the vehicle.

[0007] In this way, the source requesting the transmission of certificate information to the vehicle can switch whether or not a notification regarding the writing of certificate information is sent while the certificate information is being written to the storage device. This makes it possible to suppress unnecessary notifications for the user or to send notifications that the user requests.

[0008] In one embodiment, the authentication system further includes terminals to which notifications are sent. The server notifies the terminal when the terminal requests that certificate information be sent to the vehicle.

[0009] In this way, when the terminal requests that certificate information be sent to the vehicle, the certificate information is written according to the user's instructions. Therefore, while the certificate information is being written to the storage device, a notification regarding the writing of the certificate information is sent to the terminal, allowing the user to receive the necessary notifications.

[0010] In one further embodiment, the server does not notify the terminal when the vehicle requests that certificate information be sent to the vehicle.

[0011] In this way, if the vehicle requests the transmission of certificate information, the writing of the certificate information is not performed at the user's instruction. Therefore, by not sending a notification to the terminal regarding the writing of the certificate information, it is possible to suppress unnecessary notifications to the user.

[0012] In one further embodiment, the notification regarding the writing of certificate information includes information indicating the progress of the writing of certificate information.

[0013] In this way, if a notification is sent, the user can be made aware of the progress of writing the certificate information.

[0014] Vehicles relating to other aspects of this disclosure include an energy storage device, a storage device that stores certificate information for a digital certificate used in an authentication process when using a power station that transmits power to the energy storage device, a communication device configured to communicate with a terminal and a server that sends the digital certificate, and a control device that writes the certificate information to the storage device when it receives the certificate information from the server. When the terminal requests the server to send the certificate information, the control device notifies the terminal of the writing of the certificate information while it is writing the certificate information to the storage device, but when the request for the server to send the certificate information is made via the communication device, no notification is given while it is writing the certificate information to the storage device.

[0015] A terminal relating to another aspect of this disclosure comprises a communication device capable of communicating with a server and a vehicle, and a display device that displays predetermined information. The vehicle includes a power storage device and a storage device that stores certificate information for a digital certificate used in the authentication process when using a power station that transmits power to the power storage device. When the vehicle requests the server to transmit certificate information via the communication device, the vehicle further includes a control device that displays information on the display device regarding the writing of certificate information received from the server while the certificate information is being written to the storage device. The control device does not display information on the display device regarding the writing of certificate information when the vehicle requests the server to write certificate information. [Effects of the Invention]

[0016] According to this disclosure, it is possible to provide authentication systems, vehicles, and terminals that suppress unnecessary notifications to users. [Brief explanation of the drawing]

[0017] [Figure 1] This is a diagram showing an example of the overall configuration of the authentication system according to this embodiment. [Figure 2] This is a sequence diagram showing an example of a charging process between a vehicle, a power stand, and a server. [Figure 3] This is a flowchart showing an example of the processing executed by the server. [Figure 4] This is a sequence diagram showing an example of the operation of the authentication system according to this embodiment. [Figure 5] This is a sequence diagram showing another example of the operation of the authentication system according to this embodiment. MODE FOR CARRYING OUT THE INVENTION

[0018] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and the description thereof will not be repeated.

[0019] FIG. 1 is a diagram showing an example of the overall configuration of an authentication system 1 according to this embodiment. The authentication system 1 includes a vehicle 100, a power stand 300, a server 400, a terminal 500, and a certification authority 600.

[0020] The vehicle 100 will be described by taking, as an example, the case where it is a battery electric vehicle (BEV) without an engine. However, any electric vehicle having an electric motor as a drive source may be used. For example, it may be a hybrid vehicle (HEV) having an engine, or alternatively, a plug-in hybrid vehicle (PHEV). The vehicle 100 includes a power storage device 200 that stores power for running. The vehicle 100 is configured to be able to run by supplying the power stored in the power storage device 200 to an electric motor (rotary electric machine).

[0021] The power stand 300 is configured to enable power transmission with the power storage device 200 mounted on the vehicle 100. Specifically, the power stand 300 is configured to charge the power storage device 200 by the PnC (Plug and Charge) charging method. The PnC charging method refers to a charging method in which, simply by connecting the connector 301 of the power stand 300 to the inlet 160 of the vehicle 100, processes such as charging authentication and charging for using the power stand 300 are automatically executed.

[0022] The server 400 includes a control device 401, a storage device 402, and a communication device 403. The control device 401 is constituted by a processor such as a CPU (Central Processing Unit) and executes a program stored in the storage device 402 including a RAM (Random Access Memory) or the like. The communication device 403 is configured to be able to communicate with the communication device 140 of the vehicle 100 and the communication device 503 of the terminal 500 via a communication network (not shown).

[0023] Server 400 stores information about vehicle 100, terminal 500, and user information. Server 400 stores, for example, a digital certificate for vehicle 100 to use the power station 300. The digital certificate is an electronic certificate that includes, for example, public key information. The digital certificate includes, for example, a root certificate, an OEM (Original Equipment Manufacture) certificate, or a charging contract certificate. The root certificate is used in the authentication process during TLS communication with the power station 300. The charging contract certificate authenticates the vehicle contract and is used in the authentication process, particularly when using the power station 300. The OEM certificate is used by server 400 to encrypt the charging contract certificate, is also installed on vehicle 100, and is used in the authentication process. The charging contract certificate proves the contents of the contract concluded between the mobility operator (MO) providing the charging service and the user of vehicle 100. In this embodiment, the case where the digital certificate is a charging contract certificate will be described as an example.

[0024] The Certificate Authority 600, which includes servers belonging to the certification authority, issues digital certificates upon request, such as when an existing digital certificate expires or a new contract is concluded. The Certificate Authority 600 transmits the issued digital certificate to the Server 400.

[0025] Vehicle 100 includes a monitoring module 130 and a control unit (ECU: Electronic Control Unit) 150.

[0026] The monitoring module 130 includes various sensors to detect the state of the energy storage device 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 BMS (Battery Management System) that further has 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 energy storage device 200 (e.g., temperature, current, voltage, SOC, and internal resistance) based on the output of the monitoring module 130. The energy storage device 200 is charged (externally charged) or discharged (externally powered) by exchanging power with the power stand 300.

[0027] The ECU 150 is configured to control the charging and discharging of the energy storage device 200. The ECU 150 includes a processor 151 consisting of a CPU, RAM 152, a storage device 153, and a signal receiving unit 154.

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

[0029] The storage device 153 is configured to store stored information. The storage device 153 stores programs as well as information used by the programs (e.g., maps, formulas, and various parameters). The processor 151 executes the programs stored in the storage device 153, thereby performing various controls in the ECU 150. The storage device 153 also stores the aforementioned digital certificates. These digital certificates have expiration dates. The ECU 150 controls charging authenticated by the digital certificates. If a digital certificate has expired, a new digital certificate is downloaded and the old one is updated (replaced).

[0030] The signal receiving unit 154 receives predetermined signals from devices other than the ECU 150 mounted on the vehicle 100. 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.

[0031] 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.

[0032] The drive unit 110 is configured to drive the vehicle 100 using the power stored in the energy storage device 200. The drive unit 110 includes, for example, a Power Control Unit (PCU) composed of an inverter, a converter, and a relay, a Motor Generator (MG) composed of a three-phase AC rotating electric machine, and a System Main Relay (SMR) that switches the disconnection state of the power path between the energy storage device 200 and the PCU (none of which are shown).

[0033] The PCU and SMR are controlled by the ECU 150. The MG is driven by the PCU and configured to rotate the drive wheels W. The PCU drives the MG using power supplied from the energy storage device 200. The MG is also configured to perform regenerative power generation and supply the generated power to the energy storage device 200. The SMR is closed (connected) when the vehicle 100 is running.

[0034] The energy storage device 200 is composed of a secondary battery such as a nickel-metal hydride battery or a lithium-ion battery having a liquid or solid electrolyte. Alternatively, the energy storage device 200 may be composed of a capacitor or the like instead of a secondary battery.

[0035] The HMI device 120 includes an input device for receiving user input and a display device for displaying information to the user. The HMI device 120 may also include a touch panel display. The HMI device 120 displays information on the display device in response to control signals from the ECU 150.

[0036] The communication device 140 is configured to communicate with, for example, a terminal 500 (e.g., a smartphone) used by a user of the vehicle 100 and a server 400. The communication device 140 may also include a communication interface such as a Data Communication Module (DCM) that supports a predetermined communication format such as 5G (fifth-generation mobile communication system).

[0037] The inlet 160 is shaped to allow the connector 301 of the power stand 300 to be inserted. The connector 301 is located at the end of the cable 302 attached to the power stand 300. The vehicle 100 is electrically connected to the power stand 300 when the connector 301 is inserted into the inlet 160. This makes it possible to exchange power (charge and supply) between the power stand 300 and the vehicle 100.

[0038] Terminal 500 includes a control device 501, a storage device 502, a communication device 503, and a touch panel display 504. The control device 501 is composed of a processor such as a CPU and executes a program stored in the storage device 502, which includes RAM. The communication device 503 is configured to communicate with the communication device 140 of the vehicle 100 and the communication device 403 of the server 400. The touch panel display 504 includes an input device that accepts user input and a display device that displays information to the user. Terminal 500 is the user's terminal for vehicle 100. In server 400, terminal 500, vehicle 100, and user are stored in association. Specifically, server 400 stores, for example, identification information that identifies the user, identification information that identifies the vehicle 100, and identification information that identifies terminal 500 in association. Furthermore, server 400 stores in storage device 402 information about digital certificates stored in vehicle 100 in association with this identification information.

[0039] Figure 2 is a sequence diagram showing an example of the charging process between vehicle 100, power station 300, and server 400.

[0040] In step 10 (hereinafter referred to as step S), the charging process between the vehicle 100 and the power station 300 is initiated. For example, the charging process is initiated when the connector 301 is connected to the inlet 160.

[0041] In S20, a secure communication connection is established between the vehicle 100 and the power station 300.

[0042] In S30, various authentication processes are performed between the vehicle 100 and the power station 300 using a digital certificate stored in the vehicle 100. For example, processes such as identity verification, data verification, and authorization are performed.

[0043] In S40, settings are executed. For example, target settings and charge scheduling settings are performed.

[0044] In S50, charging takes place between the vehicle 100 and the power station 300. In S60, charging is completed.

[0045] As mentioned above, the digital certificates used in the charging process described above have an expiration date. Therefore, the digital certificate is renewed when its expiration date approaches. The renewal of the digital certificate is performed, for example, by replacing the data about the existing digital certificate stored in the storage device 153 of the vehicle 100 with data about the new digital certificate downloaded from the server 400. In this case, for example, the server 400 notifies the vehicle 100 or the terminal 500 of the update information about the digital certificate (information that a new digital certificate is available). In response to such a notification, the terminal 500, upon receiving user input, requests the server 400 to obtain the new digital certificate, or the vehicle 100 requests the server 400 to obtain the new digital certificate. The server 400 sends data about the digital certificate to the vehicle 100 in response to these requests, and the vehicle 100 stores the received data about the digital certificate in the storage device 153. The progress of obtaining such a digital certificate may be notified to the user in real time.

[0046] However, if the progress of obtaining such digital certificates is notified to the user in real time, the user will receive such notifications frequently. Therefore, for example, if the acquisition of a digital certificate is not initiated by the user, the user will receive unnecessary notifications if such notifications are sent frequently.

[0047] Therefore, in this embodiment, the server 400 switches whether or not to issue a notification regarding the writing of certificate information, which includes information about the digital certificate, while the certificate information is being written to the storage device 153 of the vehicle 100, depending on the source requesting the transmission of the certificate information to the vehicle 100.

[0048] This approach allows you to suppress unnecessary notifications for users and deliver notifications that users request.

[0049] More specifically, when terminal 500 requests that certificate information be sent to vehicle 100, server 400 notifies terminal 500 about the writing of certificate information. This allows for notifications that are requested by the user. Furthermore, when vehicle 100 requests that certificate information be sent to vehicle 100, server 400 does not notify terminal 500. In this case, since the writing of the digital certificate occurs without user intervention when vehicle 100 requests that certificate information be sent to vehicle 100, not notifying terminal 500 prevents unnecessary notifications from being sent to the user.

[0050] The following describes an example of processing performed by the server 400 (specifically, the control device 401), with reference to Figure 3. Figure 3 is a flowchart of an example of processing performed by the server 400. The series of processes shown in this flowchart are repeatedly executed at predetermined intervals.

[0051] In S100, the server 400 determines whether or not there is a request to obtain a digital certificate. The server 400 determines that there is a request to obtain a digital certificate if it receives a request signal from at least one of the vehicle 100 and terminal 500 requesting the transmission of a digital certificate to the vehicle 100.

[0052] When the server 400's managed digital certificate expires or a new digital certificate is issued by the certification authority 600, the server 400 sends certificate information to the vehicle 100 and the terminal 500 associated with the vehicle 100 indicating that a new digital certificate is available. For example, when the user receives notification that the certificate information has been received at terminal 500 and performs an operation to obtain the digital certificate for vehicle 100, a request signal is sent from terminal 500 to server 400. Alternatively, when vehicle 100 receives notification that the certificate information has been received, a request signal is sent from vehicle 100 to server 400. If it is determined that there is a request to obtain a digital certificate (YES in S100), the process moves to S102.

[0053] In S102, server 400 sends data (certificate information) about the digital certificate to vehicle 100. The process then moves to S104.

[0054] In S104, server 400 determines whether the requester of the acquisition request is terminal 500. If server 400 determines that the requester of the acquisition request is terminal 500 (YES in S104), processing is moved to S106.

[0055] In S106, the server 400 sends progress information on the download of digital certificate data to the vehicle 100 to the terminal 500. The terminal 500 uses the received progress information to display information on the touch panel display 504 about the percentage of the total amount of data of the new digital certificate to be downloaded to the vehicle 100 that has been downloaded (this information can be displayed as text or image information such as a bar graph showing the percentage as a percentage). Alternatively, the terminal 500 may display information on the percentage of the total amount of data that has not been downloaded on the touch panel display 504 instead of information on the percentage of the total amount of data of the new digital certificate that has been downloaded, or it may display information on the time until the download is completed using the transfer speed on the touch panel display 504. The process then moves to S108.

[0056] In S108, the server 400 determines whether the download is complete. The server 400 may determine that the download is complete, for example, if the amount of data of the digital certificate sent to the vehicle 100 matches the total amount of data. If it is determined that the download is complete (YES in S108), the process moves to S110.

[0057] In S110, the server 400 obtains progress information from the vehicle 100 regarding the writing of the digital certificate data to the storage device 153 and transmits it to the terminal 500. The terminal 500 uses the received writing progress information to display information on the touch panel display 504 about the percentage of the total amount of data of the new digital certificate to be written to the storage device 153 that has been written (this information can be displayed as text or image information such as a bar graph showing the percentage as a percentage). Alternatively, the terminal 500 may display information about the percentage of the total amount of data that has not been written on the touch panel display 504 instead of information about the percentage of the total amount of data of the new digital certificate that has been written, or it may display information about the time until the writing is completed using the writing speed on the touch panel display 504. The process then moves to S112.

[0058] In S112, the server 400 determines whether the write operation is complete. The server 400 may determine that the write operation is complete, for example, if it receives information from the vehicle 100 indicating that the write operation is complete. If it is determined that the write operation is complete (YES in S112), the process moves to S114.

[0059] In S114, server 400 notifies terminal 500 of the result by sending result information indicating that the writing is complete. If it is determined that there is no request to write the certificate (NO in S100), this process is terminated. If it is determined that the requester of the certificate writing request is not terminal 500 (NO in S104), the process is moved to S112. Furthermore, if it is determined that the download is not complete (NO in S108), the process returns to S108. Also, if it is determined that the writing is not complete (NO in S112), the process returns to S112.

[0060] An example of the operation of the authentication system 1 based on the above configuration and flowchart will be explained with reference to Figures 4 and 5. Figure 4 is a sequence diagram showing an example of the operation of the authentication system 1 according to this embodiment.

[0061] As shown in Figure 4 (A-1), when the server 400 obtains a new digital certificate issued by the certification authority 600, such as when the expiration date of a digital certificate it manages has passed, it sends certificate information indicating that a new digital certificate is available to both the vehicle 100 and the terminal 500. In the terminal 500, for example, an application is used to provide guidance (notification) about obtaining a new digital certificate in the vehicle 100.

[0062] As shown in Figure 4 (B-1), when a user requests to obtain a new digital certificate in response to a notification to the application on terminal 500, an operation is performed to instruct vehicle 100 to write the certificate, and the write instruction is sent to vehicle 100.

[0063] As shown in Figure 4 (C-1), when the IG is turned on in vehicle 100 by user operation or remote operation, it becomes possible to write the digital certificate. Therefore, if a writing instruction has been received from terminal 500, vehicle 100 will inquire with terminal 500 whether or not to proceed with the writing.

[0064] As shown in Figure 4 (B-2), when a user performs a write operation on terminal 500, a request is made to server 400 to send the data to vehicle 100. If a certificate acquisition request is made (YES in S100), new digital certificate data is sent to vehicle 100 (S102).

[0065] Since the requesting party is terminal 500 (YES in S104), download progress information is sent from server 400 to terminal 500 (S106). Then, once the download to vehicle 100 is complete (YES in S108), a request is made to write new digital certificate data, as shown in (A-2) of Figure 4.

[0066] As shown in Figure 4 (C-3), new digital certificate data is written to the vehicle 100 in response to a request from the server 400.

[0067] As shown in Figure 4 (A-3), the server 400 obtains write progress information from the vehicle 100 at predetermined intervals and transmits the write progress information to the terminal 500 (S110).

[0068] Therefore, as shown in Figure 4 (B-3), terminal 500 displays the received progress information on the touch panel display 504. As shown in Figure 4 (C-4), when the writing of the digital certificate is complete, a notification of completion (result notification) is sent to server 400. As shown in Figure 4 (A-4), when server 400 receives the result notification, it determines that the writing is complete (YES in S112) and sends the result information to terminal 500 (S114). As shown in Figure 4 (B-4), terminal 500 displays the received result information on the touch panel display 504.

[0069] Figure 5 is a sequence diagram showing another example of the operation of the authentication system 1 according to this embodiment.

[0070] As shown in Figure 5 (A-1), when the server 400 obtains a new digital certificate issued by the certification authority 600, such as when the expiration date of a digital certificate it manages has passed, it sends certificate information indicating that a new digital certificate is available to the vehicle 100 and the terminal 500, respectively.

[0071] As shown in (C-1) of Figure 5, when the vehicle 100 is ignited by user operation or remote operation, and no write instruction has been received from terminal 500, a request to send data to the vehicle is sent to server 400, as shown in (C-2) of Figure 5. If a certificate acquisition request is received (YES in S100), new digital certificate data is sent to vehicle 100 (S102).

[0072] Since the requesting party is vehicle 100 (NO in S104), the progress information of the digital certificate download is not sent from server 400 to terminal 500, and processing continues. When the download of the digital certificate data is completed in vehicle 100, information indicating this is sent to server 400. At this time, as shown in (A-2) of Figure 5, a request is made to write new digital certificate data.

[0073] As shown in (C-3) of Figure 5, new digital certificate data is written to the vehicle 100 in response to a request from the server 400.

[0074] As shown in Figure 5 (C-4), when the writing of the digital certificate is complete, a notification of completion (result notification) is sent to the server 400. As shown in Figure 5 (A-4), when the server 400 receives the result notification, it determines that the writing is complete (YES in S112) and sends the result information to the terminal 500 (S114). At this time, as shown in Figure 5 (B-4), the result may or may not be displayed on the touch panel display 504 of the terminal 500.

[0075] As described above, according to the authentication system 1 of this embodiment, when the terminal 500 requests that certificate information be sent to the vehicle 100, a notification regarding the writing of certificate information is sent to the terminal 500, so that notifications requested by the user can be made. Furthermore, when the vehicle 100 requests that certificate information be sent to the vehicle 100, no notification is sent to the terminal 500. When the vehicle 100 requests that certificate information be sent to the vehicle 100, the digital certificate is written without the user's initiative, so by not sending a notification to the terminal 500, it is possible to suppress unnecessary notifications to the user. Therefore, an authentication system, vehicle, and terminal that suppress unnecessary notifications to the user can be provided.

[0076] The following describes variations. In the above-described embodiment, the vehicle 100 was described as being turned on via remote or user operation. However, for example, the vehicle 100 may be configured to turn on the ignition only after the terminal has inquired about the possibility of turning on the ignition and the user has given permission.

[0077] Furthermore, in the above-described embodiment, it was explained that progress information is not displayed on the terminal 500 when the source of the write request is the vehicle 100. However, in this case, progress information may also not be displayed on the HMI device 120 of the vehicle 100.

[0078] Furthermore, although the above-described embodiment was explained as performing writing after the completion of downloading the new digital certificate data, the data download and writing may be performed in parallel.

[0079] Furthermore, the above-mentioned modifications may be implemented by combining all or part of them as appropriate. 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]

[0080] 1 Authentication system, 100 vehicles, 110 drive units, 120 HMI devices, 130 monitoring modules, 140, 403, 503 communication devices, 150 ECUs, 151 processors, 152 RAM, 153, 402, 502 memory devices, 154 signal receivers, 160 inlets, 200 energy storage devices, 300 power stands, 301 connectors, 302 cables, 400 servers, 401, 501 control devices, 500 terminals, 504 touch panel displays, 600 authentication authorities.

Claims

1. A server that transmits certificate information for a digital certificate used in the authentication process when using a power station that transmits power to a power storage device installed in an electric vehicle, The vehicle includes a storage device that stores the certificate information received from the server, The server is an authentication system that switches whether or not to issue a notification regarding the writing of the certificate information while the certificate information is being written to the storage device, depending on the source of the request for transmission of the certificate information to the vehicle.

2. The authentication system further comprises the terminals to which the notification is to be sent, The authentication system according to claim 1, wherein the server provides the notification to the terminal when the terminal requests that the certificate information be sent to the vehicle.

3. The authentication system according to claim 2, wherein the server does not make the notification to the terminal when the vehicle requests that the certificate information be sent to the vehicle.

4. The authentication system according to claim 1, wherein the notification regarding the writing of the certificate information includes information indicating the progress of the writing of the certificate information.

5. Energy storage device, A storage device that stores certificate information for a digital certificate used in the authentication process when using a power station that transmits power to the aforementioned energy storage device, A communication device configured to communicate with the terminal and the server that sent the digital certificate, The system includes a control device that writes the certificate information to the storage device when it receives the certificate information from the server, The control device is If the terminal requests the server to send the certificate information, the terminal will be notified of the writing of the certificate information while the certificate information is being written to the storage device. A vehicle in which, if a request to transmit the certificate information to the server is made via the communication device, the notification is not made while the certificate information is being written to the storage device.

6. A communication device capable of communicating with the server and the vehicle, It includes a display device that displays predetermined information, The vehicle includes an energy storage device and a storage device that stores certificate information for a digital certificate used in the authentication process when using a power station that transmits power to the energy storage device. When requesting the transmission of the certificate information from the server via the communication device, the control device further provides a device that displays information regarding the writing of the certificate information received from the server on the display device while the certificate information is being written to the storage device. The control device is a terminal that, when the vehicle requests the server to write the certificate information, does not display information regarding the writing of the certificate information on the display device.

Citation Information

Patent Citations

  • Electric Vehicle Charging Station System

    JP2022527902A