Charging control device, charging control method, and charging control program

Abstract

To surely enable a charging of a battery mounted onto a vehicle.SOLUTION: A charging control device comprises: a controller that controls a charging to a battery mounted onto a vehicle from a charging facility; and a storage part that stores a Contract certificate that certificates a user of the vehicle, who uses the charging facility and an OEMProvisioning certificate that certificates the vehicle. The controller determines whether or not the Contract certificate has to be installed when performing a charging with a system for using the Contract certificate, and determines whether or not the OEMProvisioning certificate is invalid or not in the case where the Contract certificate has to be installed. If it is invalid, the controller transmits a control signal for performing the charging with the system without using the Contract certificate to the charging facility. If it is not invalid, the controller transmits the control signal for installing the Contract certificate to the charging facility.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a charge control device, a charge control method, and a charge control program. [Background technology]

[0002] In charging facilities, PnC (Plug and Charge) charging is known as a method for charging batteries mounted on vehicles such as electric vehicles (for example, Patent Document 1). PnC is a contract-based authentication mechanism for user authentication. For example, when a vehicle driver connects a charging cable of a charging facility to the vehicle, the system authenticates the user and starts charging. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2022-530886 Summary of the Invention [Problem to be solved by the invention]

[0004] When PnC charging is performed in a vehicle equipped with a battery, it is checked whether the Contract certificate on the vehicle side is valid. The Contract certificate is a certificate that authenticates the user of the vehicle. The Contract certificate is issued by a charging business operator that provides a charging service to a user of the vehicle for which the charging business operator provides a battery charging service. If the vehicle side has a valid Contract certificate, the battery of the vehicle is charged. On the other hand, if the vehicle side does not have a valid Contract certificate, an attempt is made to install the Contract certificate in the vehicle. When the Contract certificate is installed, it is confirmed whether the vehicle has a valid OEMProvisioning certificate. The OEMProvisioning certificate is a certificate that authenticates the vehicle. The OEMProvisioning certificate is issued by a manufacturer that manufactures the vehicle. Here, if the OEMProvisioning certificate of the vehicle is invalid, the process of installing the Contract certificate cannot be terminated after the process is started, and the user cannot charge the battery of the vehicle.

[0005] The technique disclosed herein aims to provide a technique that enables a battery mounted on a vehicle to be reliably charged. [Means for solving the problem]

[0006] In order to solve the above problems, the following measures are adopted. That is, a first aspect is a charging control device including a controller and a storage unit that controls charging from a charging facility to a battery mounted on a vehicle. The storage unit stores a Contract certificate that authenticates a user of the vehicle who uses the charging facility and an OEMProvisioning certificate that authenticates the vehicle. When charging is performed using a method that uses a Contract certificate that authenticates the user of the vehicle, the controller determines whether or not it is necessary to install the Contract certificate. When it is necessary to install the Contract certificate, the controller determines whether or not an OEMProvisioning certificate that authenticates the vehicle is invalid. When the OEMProvisioning certificate is invalid, the controller transmits a control signal to the charging facility to charge using a method that does not use the Contract certificate. When the OEMProvisioning certificate is not invalid, the controller transmits a control signal to the charging facility to install the Contract certificate. Effect of the Invention

[0007] According to the disclosed technique, it is possible to provide a technique that enables a battery mounted on a vehicle to be reliably charged. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a charging system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing device. [Diagram 3] FIG. 3 is a diagram illustrating an example of an operation flow of the charging control device 100 provided in the vehicle 10 of the embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a certificate chain. [Diagram 5] FIG. 5 is a diagram showing an example of an operation sequence for installing the Contract certificate in S104. [Figure 6]FIG. 6 is a diagram showing an example of an operation sequence by the EIM in S103 and S107. [Figure 7] FIG. 7 is a diagram showing an example of an operation sequence of the process by PnC in S106. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment will be described with reference to the drawings. The configurations of the embodiments are merely examples, and the configurations of the invention are not limited to the specific configurations of the disclosed embodiments. In implementing the invention, a specific configuration according to the embodiment may be appropriately adopted.

[0010] [Embodiment 1] (Configuration example) FIG. 1 is a diagram showing an example of the configuration of a charging system according to the present embodiment. The charging system 1 includes a vehicle 10 and a charging stand 20. The vehicle 10 includes a charging control device 100. Here, it is assumed that the vehicle 10 is parked near the charging stand 20, and that the vehicle 10 and the charging stand 20 are connected to each other so as to be able to communicate with each other. The vehicle 10 is parked near the charging stand 20 in order to charge a battery mounted on the vehicle 10. Here, it is assumed that the vehicle 10 and the charging stand 20 are connected by a charging cable used when charging the battery of the vehicle 10. The charging cable includes a communication line that enables communication between the vehicle 10 and the charging stand 20.

[0011] Here, the vehicle 10 attempts to charge at the charging station 20 using PnC. If charging using PnC is not possible, EIM (External Identification Means) is used. In EIM, the user (driver) of the vehicle 10 makes payment at the charging station 20 using cash, a credit card, or the like. In PnC, a contract certificate for a charging contract is installed in the vehicle 10, and when charging, the vehicle 10 and the charging station 20 communicate with each other to charge. PnC is an example of a method that uses a contract certificate. EIM is an example of a method that does not use a contract certificate.

[0012] The vehicle 10 is a vehicle such as an electric vehicle equipped with a battery. The battery is used as a source of energy when the vehicle 10 is driven. The battery can be charged by a charging station 20 or the like.

[0013] The charging control device 100 includes a controller 102, a storage unit 104, and a communication unit 106. The controller 102, the storage unit 104, and the communication unit 106 are connected to each other by a communication bus.

[0014] The controller 102 controls operations such as the charging process of the charging control device 100 at the charging stand 20. The controller 102 also determines the validity of various certificates.

[0015] The storage unit 104 stores programs, data, and the like used in the charging control device 100, expands a working area, and stores operation setting information, and the like. The storage unit 104 also stores various certificates used in the charging control device 100, information on whether or not a Contract certificate can be installed, and the like. The information stored in the storage unit 104 may be stored in a storage unit of an information processing device other than the charging control device 100, such as a server, another control device, or a user's mobile terminal. In this case, the charging control device 100 does not need to have the storage unit 104. The information processing device may be communicably connected to the charging control device 100 or the charging stand 20.

[0016] The communication unit 106 is a communication interface that communicates to exchange data with other information processing devices, etc., via a communication network, etc. The communication unit 106 is communicably connected to the charging stand 20, other information processing devices, etc. The communication unit 106 may have a wired communication function according to a well-known wired communication standard, or a wireless communication function according to a well-known wireless communication standard such as a wireless LAN (Local Area Network).

[0017] The charging stand 20 charges the battery of the vehicle 10 connected via a charging cable. The charging stand 20 includes a communication means and communicates with the vehicle 10 and other devices. The charging stand 20 authenticates the user of the vehicle 10 when charging the battery. The charging stand 20 also instructs the vehicle 10 to install a Contract certificate. The charging stand 20 supports charging by PnC and charging by EIM. The charging stand 20 is an example of charging equipment.

[0018] The charging control device 100 is a personal computer (PC), a smartphone, a mobile phone, a The charging station 20 can be realized by using a dedicated or general-purpose computer such as a bullet terminal, a car navigation device, or a PDA (Personal Digital Assistant), or an electronic device equipped with a computer. The charging station 20 can be realized by using a dedicated or general-purpose computer such as a PC or a workstation (WS), or an electronic device equipped with a computer.

[0019] FIG. 2 is a diagram showing an example of the hardware configuration of an information processing device. The information processing device shown in FIG. 2 has a typical computer configuration. The charging control device 100 and the charging stand 20 are realized by an information processing device 90 as shown in FIG. 2. The information processing device 90 in FIG. 2 has a processor 91, a memory 92, a storage unit 93, an input unit 94, an output unit 95, and a communication control unit 96. These are connected to each other by a bus. The memory 92 and the storage unit 93 are computer-readable recording media. The hardware configuration of the computer is not limited to the example shown in FIG. 2, and components may be omitted, replaced, or added as appropriate.

[0020] The information processing device 90 has a processor 91 which loads a program stored in a recording medium into a working area of ​​a memory 92 and executes it, and each component, etc. is controlled through the execution of the program, thereby realizing functions consistent with a specified purpose.

[0021] The processor 91 is, for example, a CPU (Central Processing Unit) or a DSP (Digital Signal Processor).

[0022] The memory 92 includes, for example, a random access memory (RAM) and a read only memory (ROM). The memory 92 is also called a main storage device.

[0023] The storage unit 93 is, for example, an EPROM (Erasable Programmable ROM) or a hard disk. The storage unit 93 is a removable media. The removable media may include a USB (Universal Serial Bus) memory or a disk recording medium such as a CD (Compact Disc) or a DVD (Digital Versatile Disc). The storage unit 93 is also called a secondary storage device.

[0024] The storage unit 93 stores various programs, various data, and various tables in a readable and writable recording medium. An operating system (OS), various programs, various tables, etc. are stored in the storage unit 93. Information stored in the storage unit 93 may be stored in the memory 92. Information stored in the memory 92 may be stored in the storage unit 93.

[0025] The operating system is software that mediates between software and hardware, manages memory space, manages files, and manages processes and tasks. The operating system includes a communication interface. The communication interface is a program that exchanges data with other external devices connected via the communication control unit 96. External devices include, for example, other computers and external storage devices.

[0026] The input unit 94 includes a keyboard, a pointing device, a wireless remote control, a touch panel, etc. The input unit 94 can also include an input device for video or images such as a camera, and an input device for audio such as a microphone.

[0027] The output unit 95 is a liquid crystal display (LCD), an electroluminescence (EL) panel, The output unit 95 may include a display device such as a display panel, a CRT (Cathode Ray Tube) display, a PDP (Plasma Display Panel), etc., and an output device such as a printer, etc. The output unit 95 may also include an audio output device such as a speaker.

[0028] The communication control unit 96 connects to other devices and controls communication between the information processing device 90 and the other devices. The communication control unit 96 is, for example, a LAN (Local Area Network) interface board, a wireless communication circuit for wireless communication, or a communication circuit for wired communication. The LAN interface board and the wireless communication circuit are connected to a network such as the Internet.

[0029] A computer that realizes the charging control device 100 realizes the functions of the controller 102 and the communication unit 106 by a processor loading a program stored in an auxiliary storage device into a main storage device and executing the program. Meanwhile, the storage unit 104 is provided in a storage area of ​​the main storage device or the auxiliary storage device. The series of processes can be executed by hardware or software.

[0030] (Example of operation) Fig. 3 is a diagram showing an example of an operation flow of the charge control device 100 provided in the vehicle 10 of this embodiment. Here, it is assumed that the vehicle 10 is parked near the charging stand 20 to charge the battery of the vehicle 10, and a charging cable of the charging stand 20 is connected to the vehicle 10. At this time, the charge control device 100 and the charging stand 20 are connected so as to be able to communicate with each other. The operation flow of Fig. 3 is started when the charge control device 100 and the charging stand 20 are able to communicate with each other. Here, it is assumed that the vehicle 10 is charged by PnC.

[0031] In S101, the controller 102 of the charging control device 100 judges whether or not a Contract certificate needs to be installed in the charging control device 100. The Contract certificate is a certificate issued by a charging business providing a charging service to a user of a vehicle for which the charging business provides a battery charging service. This is a certificate that authenticates a user of the vehicle 10 who uses the charging station 20. If the vehicle 10 (charging control device 100) has a valid Contract certificate (if a valid Contract certificate is installed in the vehicle 10), the vehicle 10 can be charged at the charging station 20.

[0032] When all of the following three conditions A1 to A3 are satisfied, the controller 102 determines that the Contract certificate needs to be installed in the charging control device 100. The Contract certificate is stored in the storage unit 104. (A1) There is no valid Contract Certificate. (A2) The vehicle 10 (the charging control device 100) permits installation of the Contract certificate. (A3) The charging station 20 is compatible with the installation of a Contract certificate.

[0033] The controller 102 determines that the condition A1 is satisfied when any of the following five conditions B1 to B5 is satisfied. Furthermore, the controller 102 determines that the condition A1 is satisfied when a Contract certificate is not stored in the storage unit 104. The controller 102 may determine the validity of the Contract certificate using the charging stand 20 or another device via the communication unit 106. (B1) The Contract Certificate or the certificate chain for that certificate has expired. (B2) The Contract Certificate or any element in the certificate chain of that certificate has a type violation or is missing a required element. (B3) There is no chain in the issuer / subject relationship (the relationship between the certificate issuer and the name of the subject of certification) of the Contract Certificate or the certificate chain of the relevant certificate. (B4) Failure to verify the signature of a Contract certificate or the certificate chain of that certificate. (B5) Failure to extract the public key of a Contract certificate or the certificate chain of that certificate.

[0034] The controller 102 determines the condition of A2 based on information on whether or not a Contract certificate can be installed that is stored in the storage unit 104. Information on whether or not a Contract certificate can be installed is stored in advance in the storage unit 104.

[0035] The controller 102 inquires of the charging stand 20 via the communication unit 106 as to whether or not the charging stand 20 supports installation of a Contract certificate, and determines the condition A3 based on the response from the charging stand 20. The charging stand 20 responds to the response from the charging control device 100 as to whether or not the charging stand 20 supports installation of a Contract certificate. If the charging stand 20 supports installation of a Contract certificate from the charging control device 100, the charging stand 20 can transmit information for installing the Contract certificate to the charging control device 100.

[0036] If the Contract certificate needs to be installed in the charging control device 100 (S101; YES), the process proceeds to S102. If the Contract certificate does not need to be installed in the charging control device 100 (S101; NO), the process proceeds to S105.

[0037] In S102, the controller 102 determines whether the OEM Provisioning certificate is invalid. The controller 102 determines whether the OEM Provisioning certificate is invalid based on any one of the following five conditions C1 to C5: If any one of the above conditions is satisfied, the controller 102 determines that the OEM Provisioning certificate is invalid. The controller 102 may determine the validity of the OEM Provisioning certificate using the charging stand 20 or another device via the communication unit 106. (C1) The OEM Provisioning certificate or its certificate chain has expired. (C2) The OEM Provisioning Certificate or any element of the certificate chain for that certificate has a type violation or is missing a required element. (C3) The issuer / subject relationship (the relationship between the certificate issuer and the name of the subject of certification) of the OEM Provisioning certificate or the certificate chain of the certificate is not chained. (C4) Failure to verify the signature of the OEM Provisioning certificate or the certificate chain of that certificate. (C5) Failure to extract the public key of an OEM Provisioning certificate or the certificate chain for that certificate.

[0038] If the OEMProvisioning certificate is invalid (S102; YES), the process proceeds to S103. If the OEMProvisioning certificate is not invalid (S102; NO), the process proceeds to S104.

[0039] FIG. 4 is a diagram showing an example of a certificate chain. FIG. 4 illustrates an example of the hierarchy of each certificate. FIG. 4 shows a certificate chain of V2G_ROOT_CA201, MO_SUB1_CA211, MO_SUB2_CA212, and CONTRACT_LEAF_CA213, and a certificate chain of V2G_ROOT_CA201, OEM_SUB1_CA221, OEM_SUB2_CA222, and OEM_LEAF_CA223. That is, at least Based on V2G_ROOT_CA201 issued by another certificate authority (not shown), The certificates are issued in the order of MO_SUB1_CA211, MO_SUB2_CA212, and CONTRACT_LEAF_CA213, which are the certification authorities of the two services. Note that CONTRACT_LEAF_CA213 is issued, for example, by a server at the center of a mobility service provider. Similarly, an intermediate certification authority, MO_SUB1_CA211, MO_SUB2_CA212, and CONTRACT_LEAF_CA213 are issued based on V2G_ROOT_CA201. The subordinate CAs are OEM_SUB1_CA221, OEM_SUB2_CA222, and OEM_LEAF_CA22. The certificates are issued in the order of 3. Note that the OEM_LEAF_CA223 is, for example, The OEM_LEAF_CA223 is issued by the computer system of the provider or distributor. The vehicle 10 acquires the certificate based on the user's V2G_ROOT_CA201. The certificate chain is authenticated from top to bottom. V2G_ROOT_CA201 is the V2G (Vehicle to Grid) root CA (Certificate Authority). MO (Mobility Operator) is a charging business that provides charging services. MO_SUB1_CA211 is a MOSub1 CA certificate. MO_SUB2_CA212 is a MOSub2 CA certificate. CONTRACT_LEAF_CA213 is a Contract certificate. OEM (Original Equipment Manufacturer) is a company that provides charging services. OEM_SUB1_CA221 is the OEMSub1 CA certificate. OEM_SUB2_CA222 is the OEMSub2 CA certificate. OEM_LEAF_CA223 is the OEMP V2G_ROOT_CA201, MO_SUB1_CA211, MO_SUB2_CA212, and CONTRACT_LEAF_CA213 are the certificate chain of the Contract certificate. V2G_ROOT_CA201, OEM_SUB1_CA221, OEM_SUB2_CA222, and OEM_LEAF_CA223 are a certificate chain of the OEMProvisioning certificate. The Contract certificate and the OEMProvisioning certificate may be stored in different storage units. For example, the Contract certificate may be stored in a storage unit of the user's mobile terminal, and the OEMProvisioning certificate may be stored in the storage unit 104 of the charging control device 100.

[0040] In S103, the controller 102 decides to switch the method to EIM and starts processing by EIM. The processing by EIM will be described later. Here, since it is confirmed that the OEM Provisioning certificate is invalid, the controller 1 02 decides to switch to EIM without attempting to install the Contract certificate.

[0041] In S104, the controller 102 decides to install the Contract certificate. The installation of the Contract certificate will be described later. Here, since it is confirmed that the OEMProvisioning certificate is valid, it is possible to avoid failure of the installation of the Contract certificate due to the OEMProvisioning certificate being invalid.

[0042] In S105, the controller 102 determines whether the Contract certificate is valid. The controller 102 determines that the Contract certificate is valid when all of the following five conditions D1 to D5 are satisfied. The controller 102 may determine the validity of the Contract certificate using the charging stand 20 or another device via the communication unit 106. (D1) The Contract Certificate or the certificate chain for that certificate has not expired. (D2) The elements of the Contract Certificate or the certificate chain of that certificate do not violate any type rules and have required elements. (D3) The issuer / subject relationship of the Contract Certificate or the certificate chain of the certificate in question is chained. (D4) The signature verification of the Contract certificate or the certificate chain of that certificate is successful. (D5) Successfully extract the public key of a Contract certificate or the certificate chain of that certificate.

[0043] If the Contract certificate is valid (S105; YES), the process proceeds to S106. If the Contract certificate is not valid (S105; NO), the process proceeds to S107.

[0044] In S106, the controller 102 decides to continue the processing by PnC. The processing by PnC will be described later.

[0045] In S107, the controller 102 determines to switch the method to EIM and starts charging by EIM. The process by EIM will be described later.

[0046] 5 is a diagram showing an example of an operation sequence for installing the Contract certificate in S104. The operation sequence in FIG.

[0047] In SQ101, the controller 102 of the charging control device 100 transmits a service payment selection request (ServicePaymentSelectionReq) indicating that the PnC method has been selected to the charging stand 20 via the communication unit 106. When the charging stand 20 receives the service payment selection request, it recognizes that the charging control device 100 has selected the PnC method.

[0048] In SQ102, the charging stand 20 transmits a service payment selection response (ServicePaymentSelectionRes) that is a response to the service payment selection request to the charging control device 100.

[0049] In SQ103, the controller 102 determines to use the PnC method.

[0050] In SQ104, the controller 102 of the charging control device 100 transmits a certificate installation request (CertificateInstallationReq) to the charging stand 20 via the communication unit 106, requesting the charging stand 20 to install a Contract certificate. At this time, the controller 102 includes the OEMProvisioning certificate, the OEMSub2CA certificate, and the OEMSub1CA certificate in the certificate installation request. This enables the vehicle 10 to be authenticated in the charging stand 20 (or another device connected to the charging stand 20). The certificate installation request requesting the installation of a Contract certificate is an example of a control signal to install a Contract certificate.

[0051] In SQ105, the charging stand 20 transmits to the charging control device 100 a certificate installation response (CertificateInstallationRes) that is a response to the certificate installation request.

[0052] In SQ106, the controller 102 installs the Contract certificate.

[0053] In SQ107, processing by PnC (message exchange by PnC) is performed between the charging control device 100 and the charging stand. After that, charging of the battery of the vehicle 10 is started.

[0054] 6 is a diagram showing an example of an operation sequence by the EIM in S103 and S107. The operation sequence in FIG.

[0055] In SQ201, the controller 102 of the charging control device 100 transmits a service payment selection request (ServicePaymentSelectionReq) indicating that the EIM method has been selected to the charging stand 20 via the communication unit 106. Upon receiving the service payment selection request, the charging stand 20 recognizes that the charging control device 100 has selected the EIM method. The service payment selection request indicating that the EIM method has been selected is an example of a control signal indicating that charging will be performed using a method that does not use a Contract certificate.

[0056] In SQ202, the charging stand 20 transmits a service payment selection response (ServicePaymentSelectionRes) that is a response to the service payment selection request to the charging control device 100.

[0057] In SQ203, the controller 102 determines to use the EIM method.

[0058] In SQ204, processing by EIM (message exchange by EIM) is performed between the charge control device 100 and the charging stand. After that, charging of the battery of the vehicle 10 is started.

[0059] 7 is a diagram showing an example of an operation sequence of the process by PnC in S 106. The operation sequence in FIG.

[0060] In SQ301, the controller 102 of the charging control device 100 transmits a service payment selection request (ServicePaymentSelectionReq) indicating that the PnC method has been selected to the charging stand 20 via the communication unit 106. The charging stand 20 When the charge control device 100 receives the service payment selection request, the charge control device 100 recognizes that the PnC method has been selected.

[0061] In SQ302, the charging stand 20 transmits a service payment selection response (ServicePaymentSelectionRes) that is a response to the service payment selection request to the charging control device 100.

[0062] In SQ303, the controller 102 determines to use the PnC method.

[0063] In SQ304, processing by PnC (message exchange by PnC) is performed between the charging control device 100 and the charging stand. After that, charging of the battery of the vehicle 10 is started.

[0064] (Actions and Effects of the Embodiments) The charging control device 100 of the vehicle 10 connected to the charging cable of the charging station 20 determines whether or not it is necessary to install a Contract certificate when performing processing by PnC. When it is determined that it is necessary to install a Contract certificate, the charging control device 100 determines whether or not an OEMProvisioning certificate is invalid. When it is determined that the OEMProvisioning certificate is invalid, the charging control device 100 decides to switch to EIM. When it is determined that the OEMProvisioning certificate is valid, the charging control device 100 installs the Contract certificate. According to the charging control device 100, it is possible to prevent a situation in which the installation of the Contract certificate fails and the battery of the vehicle 10 cannot be charged when the OEMProvisioning certificate or the certificate chain of the certificate is invalid.

[0065] The configurations of the above-described embodiments can be implemented in any combination possible.

[0066] The disclosed aspects may be realized by a program being executed by an information processing device. That is, the disclosed configuration may be specified as a program for causing an information processing device to execute the processes executed by each of the means in the above-mentioned aspects, or a recording medium readable by the information processing device on which the program is recorded. The disclosed configuration may also be specified by a method in which the information processing device executes the processes executed by each of the above-mentioned means. The disclosed configuration may also be specified as a system including an information processing device that executes the processes executed by each of the above-mentioned means. The information processing device is, for example, a computer. The computer may also be called a personal computer or a server. [Explanation of symbols]

[0067] 1: Charging system 10: Vehicle 20: Charging station 90: Information processing equipment 91: Processor 92: Memory 93: Storage section 94: Input section 95: Output section 96: Communication control section 100: Charging control device 102: Controller 104: Storage area 106: Communications Department 201 :V2G_ROOT_CA 211 :MO_SUB1_CA 212 :MO_SUB2_CA 213 :CONTRACT_LEAF_CA 221 : OEM_SUB1_CA 222 : OEM_SUB2_CA 223 :OEM_LEAF_CA

Claims

1. A charging control device including a controller and a storage unit for controlling charging from a charging facility to a battery mounted on a vehicle, the storage unit stores a Contract certificate for authenticating a user of the vehicle who uses the charging facility and an OEM Provisioning certificate for authenticating the vehicle; The controller: When charging is performed in a manner using the Contract certificate, determining whether the Contract certificate needs to be installed, and if the Contract certificate needs to be installed, determining whether the OEM Provisioning certificate is invalid; If the OEM Provisioning certificate is invalid, a control signal is sent to the charging equipment to charge the battery in a manner not using the Contract certificate; If the OEM Provisioning certificate is not invalid, sending a control signal to the charging equipment to install the Contract certificate; Charging control device.

2. The controller determines that the contract certificate needs to be installed when the contract certificate is invalid, the charging control device permits installation of the contract certificate, and the charging equipment supports installation of the contract certificate. The charge control device according to claim 1 .

3. A charging control device including a controller that controls charging from a charging facility to a battery mounted on a vehicle, The controller: When charging is performed in a manner using a contract certificate stored in a storage unit, determining whether or not the contract certificate needs to be installed, and if the contract certificate needs to be installed, determining whether or not an OEM Provisioning certificate stored in the storage unit is invalid; If the OEM Provisioning certificate is invalid, a control signal is sent to the charging equipment to charge the battery in a manner not using the Contract certificate; If the OEM Provisioning certificate is not invalid, sending a control signal to the charging equipment to install the Contract certificate; Charging control device.

4. The controller determines that the contract certificate needs to be installed when the contract certificate is invalid, the charging control device permits installation of the contract certificate, and the charging equipment supports installation of the contract certificate. The charge control device according to claim 3.

5. A charging control method in a charging control device including a controller that controls charging from a charging facility to a battery mounted in a vehicle, and a storage unit that stores a Contract certificate that authenticates a user of the vehicle who uses the charging facility and an OEM Provisioning certificate that authenticates the vehicle, the method comprising: The controller: When charging is performed in a manner using the Contract certificate, it is determined whether the Contract certificate needs to be installed, and if the Contract certificate needs to be installed, the OEM Provisioning certificate is invalid. Determine whether or not If the OEM Provisioning certificate is invalid, a control signal is sent to the charging equipment to charge the battery in a manner not using the Contract certificate; If the OEM Provisioning certificate is not invalid, sending a control signal to the charging equipment to install the Contract certificate; Charging control method.

6. The controller determines that the contract certificate needs to be installed when the contract certificate is invalid, the charging control device permits installation of the contract certificate, and the charging equipment supports installation of the contract certificate. The charge control method according to claim 5 .

7. A charging control program executed in a charging control device including a controller that controls charging from a charging facility to a battery mounted in a vehicle, and a storage unit that stores a Contract certificate that authenticates a user of the vehicle who uses the charging facility and an OEM Provisioning certificate that authenticates the vehicle, The controller, When charging is performed in a manner using the Contract certificate, determining whether the Contract certificate needs to be installed, and if the Contract certificate needs to be installed, determining whether the OEM Provisioning certificate is invalid; If the OEM Provisioning certificate is invalid, a control signal is sent to the charging equipment to charge the battery in a manner not using the Contract certificate; If the OEM Provisioning certificate is not invalid, sending a control signal to the charging equipment to install the Contract certificate; A charging control program that executes the above.

8. The controller, When the contract certificate is invalid, the charging control device permits installation of the contract certificate, and the charging equipment supports installation of the contract certificate, it is determined that the contract certificate needs to be installed. The charge control program according to claim 7, which causes the charge control program to execute the following:

Images