Charge control device, charge control method, and program

Abstract

To provide a charge control device, a method and a program in which a vehicle switches a charging standard when it is determined that a battery cannot be charged when connection processing by Plug and Charge (PnC) is selected.SOLUTION: A charge control device is provided in a vehicle loaded with a battery, and communicates with a charging facility outside the vehicle to control charge of the battery. The charge control device is communicably connected with the charging facility to transmit a control signal showing a charging system when the battery is charged to the charging facility when there is a charge start input, transmits a control signal for charging the battery to the charging facility after performing authentication processing of certificate information when the charging system shown by the transmitted control signal is the one using the certificate information, disconnects communication with the charging facility and transmits a control signal showing a charging system without depending on the certificate information to the charging facility on performing communication connection with the charging facility again when the charging system using the certification information cannot be used after transmitting the control signal showing the charging system using the certificate information to the charging facility.SELECTED DRAWING: Figure 6

Description

[Technical field]

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

[0002] ISO15118-2, a communication standard for rapid charging, stipulates that electric vehicles be charged at charging stations (also called charging equipment) via plug and charge (PnC). The following Patent Document 1 is an example of PnC. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-93078 A Summary of the Invention [Problem to be solved by the invention]

[0004] According to ISO15118-2, if charging by PnC becomes impossible after selecting charging by PnC, the electric vehicle cannot change the charging method. For the electric vehicle to switch the charging method by itself, it is assumed that the user will have to remove the plug (charging gun) connected to the electric vehicle and then reattach it in order to charge, which is inconvenient.

[0005] Therefore, an aspect of the disclosed embodiment is to enable the vehicle to switch the charging standard when it is determined that charging is not possible when a connection process based on PnC is selected. [Means for solving the problem]

[0006] One aspect of the disclosed embodiment is exemplified by a charging control device. The charging control device is provided in a vehicle equipped with a battery, and controls charging of the battery by communicating with a charging facility outside the vehicle. When a charging start input is received, the charging control device is provided with a controller that connects to the charging facility and transmits a control signal indicating a charging method to be used when charging, and transmits a control signal to the charging facility to make the charging facility charge the battery after performing authentication processing of the certificate information if the charging method indicated by the transmitted control signal is a charging method using certificate information. If the charging method using certificate information becomes unavailable after transmitting the control signal indicating the charging method using certificate information to the charging facility, the controller disconnects communication with the charging facility. Then, the controller reconnects to the charging facility and transmits a control signal indicating a charging method not based on the certificate information to the charging facility. Effect of the Invention

[0007] According to the communication procedure of the present charging control device, when the PnC connection process is selected and it is determined that charging is not possible, the vehicle can switch the charging standard. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a vehicle equipped with a charge control device according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration related to charging in a vehicle and a charging facility. [Diagram 3] FIG. 3 is a sequence diagram illustrating the processing of a vehicle and a charging facility according to a comparative example. [Figure 4] FIG. 4 is a diagram illustrating a procedure (1) when PnC cannot be executed by a vehicle and a charging facility according to a comparative example. [Diagram 5] FIG. 5 is a diagram illustrating a procedure (2) when PnC cannot be executed by a vehicle and a charging facility according to a comparative example. [Figure 6]FIG. 6 is a sequence diagram illustrating the process (1) in the first embodiment. [Figure 7] FIG. 7 is a sequence diagram illustrating the process (2) in the first embodiment. [Figure 8] FIG. 8 is a sequence diagram illustrating the process (3) in the first embodiment. [Figure 9] FIG. 9 is a sequence diagram illustrating the processing of a vehicle and a charging facility according to a comparative example. [Figure 10] FIG. 10 is a diagram illustrating an effect of the processing of the vehicle and the charging facility according to the first embodiment. [Figure 11] FIG. 11 is a sequence diagram illustrating a process in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] First embodiment (Configuration) A charge control device 10, a charge control method, and a program according to a first embodiment will be described with reference to Figs. 1 to 10. Fig. 1 is a diagram illustrating a configuration of a vehicle 1 equipped with a charge control device 10 according to this embodiment. Note that Fig. 1 also illustrates a charging facility 2 (Electric Vehicle Supply Equipment, EVSE 2) that supplies power to a battery 19 (see Fig. 2, also called a secondary battery or a storage battery) of the vehicle 1, and a server 5 that exchanges information with the vehicle 1. In addition, In the following embodiments, the charging control device 10 and the charging facility 2 may be collectively referred to as a system.

[0010] The vehicle 1 is called an electric vehicle, and can charge a battery 19 for driving. The vehicle 1 has a charging control device 10, and executes a charging process between the vehicle 1 and the charging facility 2. In the charging process, the charging control device 10 of the vehicle 1 communicates with the charging facility 2 by TLS (Transport Layer Security). In communication by TLS (hereinafter, referred to as TLS communication), the charging control device 10 and the charging facility 2 exchange random values ​​with each other to create an encryption key. After creating the encryption key, the charging control device 10 exchanges information with the charging facility 2 by encrypted communication, and executes charging by PnC as a first authentication procedure. Charging by PnC can be said to be an example of a first charging method. The procedure by such a first charging method is started, for example, when a plug 2B that supplies power from the charging facility 2 is connected to a power receiving unit of the vehicle 1.

[0011] In addition to the above-mentioned PnC procedure, when charging the vehicle 1, an external authentication procedure by presenting an EIM is also possible as a second authentication procedure. For this reason, the charging equipment 2 has an EIM reader 2A. The external authentication method is, for example, a method of charging and charging using billing information acquired from a credit card, a QR code (registered trademark), Radio Frequency Identification (RFID), or the like via the EIM reader 2A. Charging using the second authentication procedure can be said to be an example of the second charging method.

[0012] The charging control device 10 can be connected to the server 5 via a network N1. The network N1 can be, for example, a Long Term Evolution (LTE), a 5th Generation Mobile Communication System (5G), a 6th Generation Mobile Communication System (6G), and wired public networks such as the Internet.

[0013] The vehicle 1 may report the result of the charging process to the server 5, and the server 5 may accumulate the result of the charging process from the vehicle 1. The server 5 accumulates information from a large number of vehicles including the vehicle 1, thereby providing various information to a large number of users including the user of the vehicle 1, and sharing the information with these users. For example, the server 5 may inform users of information regarding the level of service in the charging facility 2, the safety of communications, etc. The server 5 may be, for example, an OEM (Original Equipment Manufacturer) server that exchanges information with the vehicle 1, a server that provides services to the vehicle 1, etc. The server is exemplified as any one of various information processing devices such as an e-Mobility Service Provider (eMSP) server and a Charge Point Operator (CPO) server.

[0014] FIG. 2 is a diagram illustrating an example of a hardware configuration related to charging in the vehicle 1 and the charging facility 2. The vehicle 1 and the charging facility 2 are connected by connecting a plug 2B (see FIG. 1) connected to the charging facility 2 to a power receiving unit of a charging circuit 18 that charges a battery 19 of the vehicle 1. Then, for example, the communication ICs 12 and 22 communicate with each other to perform TLS authentication and V2G (Vehicle to Grid) communication. The vehicle 1 and the charging facility 2 perform TLS authentication and V2G (Vehicle to Grid) communication. Mutual authentication is performed via 2G communication, and charging of the battery 19 of the vehicle 1 and billing for the charging are performed.

[0015] The vehicle 1 is equipped with a charging control device 10, a battery 19, and a charging circuit 18. The charging control device 10 is an in-vehicle control device for charging the battery 19 from a charging facility 2. The charging control device 10 has a charging control unit 11, a communication IC 12, a communication control unit 13, an in-vehicle control unit 14, and an in-vehicle display 144. The charging control unit 11, the communication IC 12, the communication control unit 13, the in-vehicle control unit 14, etc. are connected to each other via an in-vehicle network N3. The in-vehicle network N3 may be, for example, a controller area network (CAN), a CAN F, or the like. D (with Flexible Data Rate), LIN (Local Interconnect Network), FlexR ay, MOST (Media Oriented Systems Transport), etc. However, the charging control unit 11 and the communication IC 12 are integrated into an in-vehicle control device called an ECU (Electronic Control Unit). The connection may be made by a serial communication interface such as SPI (Serial Peripheral Interface) or I2C (Inter-Integrated Circuit) for transmitting and receiving data between ICs (Integrated Circuits) in the device.

[0016] The charging control unit 11 of the vehicle 1 includes a central processing unit (CPU) 111, a memory including a read only memory (ROM) 112, and an interface for an in-vehicle network N3. The charging control unit 11 or the CPU 111 executes processes related to PnC and controls charging of the battery 19 by a computer program executablely deployed in a memory including the ROM 112. The charging control unit 11 or the CPU 111 can be said to be an example of a controller. The ROM 112 is a rewritable ROM. The ROM 112 is, for example, an EEPROM (Electrically Erasable Programmable Read-Only Memory), a flash memory, or the like.

[0017] The charging control unit 11 communicates with an OEM server via, for example, the communication control unit 13, and acquires a user-specific Contract certificate issued by an e-Mobility Service Provider (eMSP). and stores it in the ROM 112. The eMSP is a mobility service provider for the vehicle 1.

[0018] Furthermore, the charging control unit 11 of the vehicle 1 is connected to the charging facility 2 via the communication ICs 12 and 22, and performs TLS authentication and V2G communication. Furthermore, the charging control unit 11 controls a charging circuit 18 that receives power supply from a power line PL connected to the charging facility 2, and charges a battery 19.

[0019] The communication IC 12 executes a communication protocol, for example, in accordance with the ISO15118 standard. The communication IC 12 communicates with the communication IC 22 on the charging equipment 2 side through a communication line CL using a communication procedure similar to power line communication (PLC (Power Line Communication)) technology. The communication line CL is, for example, called a control pilot signal (CPLT, Control Pilot) line. Note that the communication IC 12 may include signal lines other than the CPLT line. In addition, the communication IC 22 may be connected to the communication IC 22 via multiple signal lines or wirelessly.

[0020] The communication control unit 13 is, for example, a device called a TCU (Telematics Control Unit). The communication control unit 13 is a communication unit that performs bidirectional information communication with the outside of the vehicle 1 in response to requests from other control units, such as the charging control unit 11 and the in-vehicle control unit 14. The communication control unit 13 communicates with the server 5, for example, via the network N1.

[0021] The communication control unit 13 includes a CPU 131, a memory including a ROM 132, a wireless communication unit 133, and an interface for the in-vehicle network N3. The CPU 131 and the ROM 132 are similar to the CPU 111 and the ROM 112, and therefore their description will be omitted. The wireless communication unit 133 is, for example, a high-frequency circuit for 4G, 5G, or a subsequent wireless access network. The wireless communication unit 133 may also include a wireless communication circuit for Dedicated Short Range Communications (DSRC) or a receiving circuit for a Global Positioning System (GPS).

[0022] The in-vehicle control unit 14 is, for example, a control unit of a car navigation system. The in-vehicle control unit 14 has therein a CPU 141, a memory including a ROM 142, an interface for the in-vehicle network N3, and the like. The CPU 141 and the ROM 142 are similar to the CPU 111 and the ROM 112, and therefore their description will be omitted. The in-vehicle control unit 14 is connected to an output device such as an in-vehicle display 144 and a speaker, and provides the user, who is the driver of the vehicle 1, with navigation information, information related to charging, information related to maintenance of the vehicle 1, and the like, by using images and sounds, etc.

[0023] The charging circuit 18 is a drive circuit that supplies electric charge to the battery 19. The battery 19 receives power from the charging facility 2 via the charging circuit 18 and stores the power. The battery 19 supplies the stored power to a drive unit such as a motor of the vehicle 1.

[0024] The charging facility 2 has an facility control unit 21, a communication IC 22, a communication device 23, a display 24, and a power circuit 28. The facility control unit 21 has a CPU 211 and a memory 212. The CPU 211 executes processing as the facility control unit 21 using a computer program on the memory 212. The facility control unit 21 is connected to the vehicle 1, for example, via the communication IC 22, and executes processing related to PnC. In addition, the facility control unit 21 is connected to a network N2, for example, via the communication device 23, and communicates with a server 5, etc.

[0025] The network N2 is a public line such as the Internet, a backbone network, or a core network. The network N2 is connected to the network N1 including a wireless access network. However, the network N2 may be integrated with the network N1 and provided by the same telecommunications carrier.

[0026] Server 5 is called the OEM (Original Equipment Manufacturer) server, eMSP (e-Mobility Service Provider) server, and CPO (Charge Point Operator) server. The OEM server is an information processing device operated by a manufacturer or distributor (OEM) of the vehicle 1. The OEM server executes various processes including maintenance for the vehicle 1. For example, the OEM server obtains a user-specific Contract certificate associated with the vehicle 1 from the eMSP server, and installs the Contract certificate in the ROM 112 of the vehicle 1.

[0027] The eMSP server is an information processing device operated by a business operator (eMSP) that provides charging services to the vehicle 1. The user of the vehicle 1 enters into a contract with the business operator (eMSP), and the business operator (eMSP) issues a user-specific Contract certificate to the user of the vehicle 1 from the eMSP server. The CPO server is an information processing device operated by a business operator (CPO) that operates or manages the charging facility 2. In addition to operating the charging facility 2, the CPO server also handles maintenance and They may also provide processes or services to assist with repairs, customer support, billing and payment processing, and the like.

[0028] The equipment control unit 21 acquires a user-specific Contract certificate associated with the identification information of the vehicle 1 and the OEM Leaf certificate, etc. from the eMSP server via, for example, the CPO server, and stores the Contract certificate in the memory 212. Then, the equipment control unit 21 can provide the user-specific Contract certificate to the vehicle 1 having a valid OEM Leaf certificate. In this way, the vehicle 1 can acquire a Contract certificate not only from the OEM server, but also from the charging equipment 2. The power circuit 28 supplies power from the commercial power source 30 to the charging circuit 18 of the vehicle 1 via the power line PL.

[0029] (Comparative Example: Processing Procedure and Problems) Fig. 3 is a sequence diagram illustrating the processing of a vehicle 501 and a charging facility 502 according to a comparative example. The vehicle 501 and the charging facility 502 have components similar to those of the vehicle 1 and the charging facility 2 in Fig. 2. Therefore, in this comparative example (Figs. 3 to 5 and 9), the components of the vehicle 501 and the charging facility 502 will be described using the components of the vehicle 1 and the charging facility 2 in Fig. 2.

[0030] The process of the comparative example starts when a user inserts plug 2B of charging equipment 502 into a power receiving unit connected to charging circuit 18 of vehicle 501. When plug 2B is connected to the power receiving unit, first, communication IC 22 of charging equipment 502 transmits a CPLT signal with a preset duty ratio of 5% to communication IC 12 via communication line CL (S501).

[0031] Then, the charging control unit 11 of the vehicle 501 detects the duty ratio of the CPLT signal to be 5% via the communication IC 12. By detecting the duty ratio of the CPLT signal to be 5%, the charging control unit 11 recognizes that the charging equipment 502 is in an activated state and is capable of executing, for example, a SLAC (Signal Level Attenuation Characterization) sequence. The control unit 11 executes communication for establishing a data link with the equipment control unit 21 of the charging equipment 502 by the communication IC 12 in accordance with the SLAC sequence (S502). The SLAC sequence is defined in ISO15118-3. In the SLAC sequence, a request message is transmitted from the vehicle 1 to the charging equipment 2, and a procedure is performed to identify a connection partner based on a response signal or the like (response message) transmitted from the charging equipment 2 in response to the message, and to establish a data link. Here, in establishing the data link, for example, a physical address, exemplified by a media access control (MAC) address of the other party, or a network ID (NID) or the like is identified between the vehicle 1 and the charging equipment 2.

[0032] Note that, although a SLAC sequence is exemplified here, in this embodiment, charging by PnC is not limited to communication established by a SLAC sequence. For example, the communication IC 12 of the vehicle 501 may execute a connection process conforming to the ISO15118-2 standard with the communication IC 22 of the charging equipment 502. As a result of S502, a data link is established between the vehicle 501 and the charging equipment 502 (S503). By establishing the data link, the vehicle 501 (charging control unit 11, communication IC 12) and the charging equipment 502 (equipment control unit 21, communication IC 22) execute communication using a physical address exemplified by a MAC address or an NID, etc.

[0033] Next, the communication IC 12 of the vehicle 501 is UDP message SECCDiscoveryProtocol.Req for establishing a connection is sent to the charging equipment 50 The communication IC 22 of the charging facility 502 then transmits the UDP message SECCDiscoveryProtocol.Res to the communication IC 22 of the charging facility 502 (S504). Then, a TCP connection is established between the vehicle 501 and the charging facility 502 (S505 Through the TCP connection, the vehicle 501 and the charging facility 502 communicate with each other using logical addresses such as IP addresses. Furthermore, through the TCP connection, the vehicle 501 and the charging facility 502 can confirm and resend data transmitted and received between them.

[0034] Then, the vehicle 501, for example, designates PnC or EIM and transmits a PaymentServiceSelection.Req message to the charging facility 502 (S507). The payment service response replies to the vehicle 501 with a message PaymentServiceSelection.Res (S508). The process from S504 to S505 can be considered as an example of a process for establishing a communication connection with the charging facility 2. The process from S507 can be considered as an example of a process for transmitting a control signal indicating a charging method for charging to the charging facility 2. In addition, the fact that PnC is specified in the message PaymentServiceSelection.Req transmitted to the charging facility 502 indicates that the charging method indicated by the transmitted control signal is specified in the certificate information. This corresponds to an example of a charging method using the above.

[0035] If PnC is specified in S507, the vehicle 501 further sends the Contract certificate to the charging facility 2 by using the message Authorization.Req (S510). At this time, the Contract certificate is transmitted to the charging facility 2 together with the Contract certificate installed in the vehicle 1 in advance. The Contract certificate is signed with the vehicle 1's private key and sent to the charging facility 2. The charging facility 2 verifies the signature of the Contract certificate signed in the vehicle 1. If the signature verification is successful, the charging facility 2 responds with a message Authorization.Res (S511). The charging method is determined according to the request and the response from the charging facility 502. That is, thereafter, the vehicle 501 receives power supply from the charging facility 502 by PnC and charges the battery 19. When EIM is specified in S507, charging is performed together with billing based on the billing information by the EIM reader 2A. The processes of S501 and S502 are an example of a process for performing authentication processing of the certificate information. Therefore, the process of FIG. 3 can be said to exemplify a process for transmitting a control signal to the charging facility 2 to charge the battery 19 after performing authentication processing of the certificate information.

[0036] FIG. 4 is a diagram illustrating a procedure (1) in a case where PnC cannot be executed by a vehicle 501 and a charging facility 502 according to a comparative example. In the example of FIG. 4, the communication IC 12 of the vehicle 501 detects by the message PaymentServiceSelection.Req that the vehicle 1 (e.g., the charging control unit 11) cannot execute PnC before selecting PnC or EIM (S510). In this case, the charging control unit 11 of the vehicle 501 then selects EIM and transmits the message PaymentServiceSelection.Req from the communication IC 22 (S517), and the facility control unit 21 responds to the vehicle 501 with PaymentServiceSelection.Res by the communication IC 22 (S518). 8).

[0037] Thereafter, the vehicle 501 receives power supply from the charging facility 502 via the EIM, and charges the battery 19. The above procedure complies with the procedure stipulated in the ISO15118 standard.

[0038] FIG. 5 is a diagram illustrating a procedure (2) in a case where PnC cannot be executed between a vehicle 501 and a charging facility 502 according to a comparative example. In the example of FIG. 5, the charging control unit 11 of the vehicle 501 selects PnC and transmits a message PaymentServiceSelection.Req to the charging facility 502 (S527), and the charging facility 502 responds with a PaymentServiceSelection.Res to the vehicle 501 ( S528). However, thereafter, the vehicle 1 (for example, the charging control unit 11) detects that PnC cannot be executed (S529). Therefore, the process in Fig. 5 illustrates a case where the charging method using the certificate information becomes unavailable after a control signal indicating the charging method using the certificate information is transmitted to the charging equipment 2.

[0039] Here, vehicle 1 detects that it cannot execute PnC if the following events occur: It is assumed that this may occur.

[0040] (1) Certificate read failure; This is exemplified when the charging control unit 11 fails to read the Contract certificate or the like stored in the ROM 112. Also, this is exemplified when the equipment control unit 21 of the charging equipment 502 fails to read the Contract certificate or the like from the memory 212.

[0041] (2) Signature generation failure; Examples of failures include failure to encrypt a digest value or failure to read a private key used for encryption. For example, the message Authorization.Req in FIG. 3 includes signature data. This signature data is, for example, For example, the charging control unit 11 of the vehicle 1 calculates a digest value from certain data that is the basis of the signature data and encrypts it with a contract private key. Examples of signature generation failures include a case where the charging control unit 11 fails to encrypt the digest value when creating this signature data, or a case where the charging control unit 11 fails to read the private key used for encryption.

[0042] (3) Contract certificate installation failed; This is exemplified by a case where the charging control unit 11 (CPU 111) fails to communicate an installation message received from the server 5 when installing the contract certificate, and the contract certificate is not installed.

[0043] (4) Signature verification failed; Examples of such failures include failure to decrypt signature data and failure to verify the match of the decrypted digest value. As described above in (2), the signature data is obtained by calculating a digest value from certain data that is the basis of the signature data and encrypting it with a private key. This signature data is signature-verified with a public key corresponding to the private key. For example, this failure occurs when signature data signed by the charging control unit 11 of the vehicle 1 with a private key is handed over to the equipment control unit 21 of the charging equipment 2, and the equipment control unit 21 fails to verify the signature data with the corresponding public key. Similarly, this failure occurs when signature data signed by the equipment control unit 21 of the charging equipment 2 is handed over to the charging control unit 11 of the vehicle 1, and the charging control unit 11 fails to verify the signature data.

[0044] (5) Certificate chain verification failure; Basically, electronic certificates such as a Contract certificate exchanged between the vehicle 1 and the charging equipment 2 are digitally signed. An example of a certificate chain verification failure is when an electronically signed electronic certificate is handed over from the vehicle 1 to the charging equipment 2, and the charging equipment 2 fails to verify the handed over electronic certificate. Note that electronic certificates generally form a hierarchical certificate chain according to the hierarchy of the certification authorities that issue the electronic certificates. An electronic certificate issued by a lower-level certification authority is authenticated by an electronic certificate issued by a higher-level certification authority.

[0045] (7) Session key derivation failure; When the Contract certificate is installed from the charging facility 2 to the vehicle 1, the encrypted Contract private key is also transmitted from the charging facility 2 to the vehicle 1 together with the Contract certificate. The vehicle 1 generates a common key for decrypting the encrypted Contract private key, etc. An example of a session key derivation failure is a failure to generate the common key.

[0046] (8) Contract private key decryption failure As described above, the Contract private key, together with the Contract certificate, is encrypted with a common key and distributed to the vehicle 1 via the OEM or via the charging facility 2. Here, a case is illustrated in which the vehicle 1 is unable to decrypt the Contract private key and Contract certificate distributed to the vehicle 1.

[0047] (9)Failed to read Contract private key The Contract certificate is encrypted with a private key and stored in a secure area of ​​the ROM 112 of the vehicle 1. Examples of failures to read the Contract private key include a case where the charging control unit 11 of the vehicle 1 fails to read the private key or fails to decrypt the Contract certificate encrypted with the private key.

[0048] (10) Contract private key / public key pair verification failure An example would be when the obtained Contract private key and Contract public key are an invalid pair (not a match).

[0049] As shown in Figure 5, after vehicle 1 sends PaymentServiceSelection.Req, i.e., Pn There is no standard requirement for transitioning to charging by EIM when charging by PnC becomes impossible after selecting PnC charging. For example, in the procedure specified in the ISO15118 standard, charging of the vehicle 501 fails. That is, in the procedure specified in the ISO15118 standard, when charging by PnC becomes impossible after selecting PnC charging, the charging control unit 11 of the vehicle 501 cannot switch to another charging method. In this case, it is assumed that the user of the vehicle 501 will perform a procedure such as temporarily removing the plug 2B from the power receiving unit connected to the charging circuit 18 of the vehicle 501 and then reinserting it. This is because the charging process is reset when the plug 2B is reconnected.

[0050] That is, in the process of the comparative example, if charging by PnC is selected and then charging by PnC becomes impossible, the vehicle 501 cannot take the initiative to continue the charging process or change to another charging method for charging. As a result, there is a high possibility that user intervention will be required, such as with the plug 2B. Thus, the process of the comparative example is not desirable for users. In the following embodiment, a process for solving such problems of the comparative example will be described.

[0051] (Processing procedure of the embodiment) FIG. 6 is a sequence diagram illustrating the process (1) in the first embodiment. The process in FIG. 6 is started by a user attaching the plug 2B (see FIG. 1) of the charging facility 2 to a power receiving unit connected to the charging circuit 18 (see FIG. 2) of the vehicle 1, as in the processes in FIG. 3 to FIG. 5 of the comparative example. However, the trigger for starting the process in FIG. 6 is not limited to the plug 2B being connected to the charging circuit 18 of the vehicle 1. For example, when there is an operation input by the user to an operation unit such as a switch to instruct the start of charging, the charging control unit 11 may detect the operation input and start the process in FIG. 6. Such an operation input includes, for example, an operation in a facility where non-contact charging is performed without connection of the power line PL by the plug 2B or the like. In addition, the charging control unit 11 may start the process in FIG. 6 when it receives a start instruction signal from a control device of the vehicle 1 (including various ECUs and components of the charging control unit 11 itself) or the like, instead of an operation input from the user. For example, when the vehicle 1 charges the battery 19 by timer charging or the like, a start instruction signal is transmitted from the in-vehicle device (including the charging control unit 11 itself) or the charging equipment 2 side when the charging start time is reached. That is, the charging control unit 11 may start the process of FIG. 6 by receiving a control signal indicating the start of charging. Also, for example, when the vehicle 1 is in a charging waiting state at the charging equipment 2, a start instruction signal is transmitted from the charging equipment 2 or the like when it is the vehicle's turn to charge. The charging control unit 11 may start the process of FIG. 6 by receiving a control signal indicating the start of charging. Such a trigger for starting charging is similar in each embodiment from the second embodiment onwards. In FIG. 6, the process from the charging control unit 11 of the vehicle 1 selecting PnC (S527) to the process of detecting that the charging control unit 11 of the vehicle 1 cannot execute PnC (S529) is the same as that in FIG. 5. Therefore, the process of FIG. 6, like the process of FIG. 5, can be said to exemplify a case where the charging method using the certificate information becomes unavailable after a control signal indicating the charging method using the certificate information is transmitted to the charging equipment 2.

[0052] In the process of FIG. 6, when the charging control unit 11 of the vehicle 1 detects that PnC cannot be executed (S529), it disconnects the TCP (S0). The TCP is disconnected by specifying the IP address of the charging equipment 2 (communication IC 22) by a TCP reset or TCP clear command. Then, when the TCP is disconnected and the data link is established, the charging control unit 11 can execute switching of the charging method from TCP establishment by the following procedure. Note that information indicating whether the data link is established or not can be acquired by the charging control unit 11 executing a command (or system call) to inquire about the state of the communication IC 12 to the OS (Operating System). Then, whether the data link between the vehicle 1 (communication IC 12) and the charging equipment 2 (communication IC 22) is established or not is notified to the upper level, i.e., to the charging control unit 11 via the OS.

[0053] When a data link is established between the vehicle 1 and the charging facility 2, the charging control unit 11 of the vehicle 1 transmits a UDP message SECCDiscoveryProtocol.Req for establishing a TCP connection to the communication IC The charging equipment 2 then transmits the SECCDiscoveryProtocol.Res to the vehicle 1 via the communication IC 22 (S4). Then, the equipment control unit 21 of the charging equipment 2 returns SECCDiscoveryProtocol.Res to the vehicle 1 via the communication IC 22 (S5). Through the procedures of S4 and S5, a TCP connection is re-established between the communication IC 12 of the vehicle 1 and the communication IC 22 of the charging facility 2.

[0054] Then, vehicle 1 selects EIM and sends PaymentServiceSelection.Req to IC1 for communication. The charging facility 2 then transmits the PaymentServiceSelection.Res to the vehicle 1 via the communication IC 22 (S7). The charging facility 2 then returns PaymentServiceSelection.Res to the vehicle 1 via the communication IC 22 (S8). Charging communication is performed between the device and equipment 2 via EIM.

[0055] Fig. 7 is a sequence diagram illustrating process (2) in the first embodiment. The trigger for starting the process in Fig. 7 is the same as that in Fig. 6 of the first embodiment. In Fig. 7, the process from the vehicle 1 selecting PnC (S527), the charging equipment 2 responding to the vehicle 1 (S528), to the process of detecting that the vehicle 1 cannot execute PnC (S529) is the same as that in Fig. 5.

[0056] In the process of FIG. 7, when the charging control unit 11 of the vehicle 1 detects that PnC cannot be executed (S529), it disconnects the TCP (S0) and further disconnects the data link (S1). The data link is disconnected by specifying the communication IC 12 with a data link reset or data link clear command. Here, the data link is disconnected when the vehicle 1 and the charging facility 2 do not recognize each other. For example, the vehicle 1 and the charging facility 2 do not recognize each other's data link layer level addresses (MAC address, physical address), NID (Network ID), etc., or this information is cleared from the ROM 112, memory 212, etc. (see FIG. 2).

[0057] After the data link is disconnected, the charging control unit 11 of the vehicle 1 detects a PWM signal (e.g., a CPLT signal) transmitted from the communication IC 22 via the communication line CL connecting the communication IC 12 of the vehicle 1 and the communication IC 22 of the charging equipment 2. Then, the charging control unit 11 judges whether the duty ratio of the PWM signal transmitted by the communication IC 12 is 5% within the allowable error range. In the example of FIG. 7, the duty ratio of the PWM signal transmitted from the communication IC 22 is 5% within the allowable error range (S501A). By detecting the duty ratio of the CPLT signal of 5%, the charging control unit 11 recognizes that the charging equipment 2 is in an activated state and, for example, a SLAC sequence can be executed. Then, the charging control unit 11 executes communication of the SLAC sequence to establish a data link (S2). Note that, although the SLAC sequence is exemplified here, the charging by PnC is not limited to the SLAC sequence in this embodiment. For example, the communication IC 12 of the vehicle 1 may establish a data link with the communication IC 22 of the charging facility 2 according to a general data link layer communication procedure. As a result of step 2, a data link is established between the vehicle 1 and the charging equipment 2 (see FIG. 3). By establishing the data link, the vehicle 1 (charging control unit 11, communication IC 12) and the charging equipment 2 (equipment control unit 21, communication IC 22) execute communication using addresses (MAC address, physical address), NID (Network ID), etc. at the data link layer level.

[0058] Next, the communication IC 12 of the vehicle 1 transmits a UDP message SECCDiscoveryProtocol.Req for establishing a TCP connection to the communication IC 22 of the charging equipment 2 (S4). The communication IC 22 responds with a UDP message SECCDiscoveryProtocol.Res (S5). As a result of the above, a TCP connection is established between the vehicle 1 and the charging facility 2 (see FIG. 3).

[0059] The subsequent steps are the same as those in FIG. 6. That is, the vehicle 1, for example, specifies EIM and transmits a PaymentServiceSelection.Req message to the charging facility 2 (S7). The charging facility 2 responds with a message PaymentServiceSelection.Res to the vehicle 1 (S8). As described above, the charging method is determined based on the selection by the vehicle 1 and the response from the charging facility 2. That is, from then on, the vehicle 1 receives power supply from the charging facility 2 according to the EIM, and charges the battery 19.

[0060] Fig. 8 is a sequence diagram illustrating the process (3) in the first embodiment. The trigger for starting the process in Fig. 8 is the same as that in Fig. 6 of the first embodiment. In Fig. 8, the process from the process in which the vehicle 1 selects the PnC (S527) to the process in which the data link is disconnected (S1) is the same as that in Fig. 7.

[0061] The example of FIG. 8 is different from FIG. 7 in that the duty ratio of the PWM signal transmitted from the communication IC 22 is determined to be not 5% within the allowable error range. By detecting a duty ratio of the CPLT signal other than 5% (S501B), the charging control unit 11 recognizes that the charging equipment 2 is not in an activated state and cannot execute, for example, a SLAC sequence. Here, the activated state is also called a wake-up state, and refers to a state in which the charging equipment 2 including the communication IC 22 is capable of executing a charging process. In FIG. 8, "!=" is a symbol indicating inequality.

[0062] Therefore, the charging control unit 11 of the vehicle 1 performs a BCB toggle (charging station activation request) using the communication IC 12 to activate the charging equipment 2. Then, by activating the charging equipment 2, the charging control unit 11 of the vehicle 1 detects a duty ratio of 5% using the communication IC 12 (S501C) and then starts over from the SLAC sequence (S2). That is, when the vehicle 1 detects a duty ratio of 5%, it executes the processes from S2 to S8. The processes from S2 to S8 are the same as those in FIG. 7, and therefore their description will be omitted.

[0063] (Effects of the embodiment) Fig. 9 is a sequence diagram illustrating the processing of the vehicle 501 and the charging facility 502 according to a comparative example for comparison with the processing of the vehicle 1 and the charging facility 2 according to this embodiment. Fig. 10 is a diagram illustrating the effect of the processing of the vehicle 1 and the charging facility 2 according to this embodiment.

[0064] In the process of the comparative example as shown in FIG. 9, the vehicle 501 selects PnC once in the charging sequence (S527), and then detects that PnC cannot be continued (S529). At this time, the charging equipment 2 stops the process (S530). In this case, the charging equipment 2 can notify the vehicle 1 of the stop due to an abnormality on its own display 24, or on the vehicle 1's in-vehicle display 144 by notifying the vehicle 1 (S531). However, if this continues, it is expected that the charging equipment 2 will, for example, continue to stop the process.

[0065] Therefore, in order to execute the charging sequence again, the user disconnects the charging plug 2B from the power receiving unit of the vehicle 1, thereby disconnecting the circuits of the power line PL and the communication line CL (S532). Then, the user reconnects the plug 2B to the power receiving unit (S533). The user's manual operations in S532 and S533 make it possible to start charging again (S534), and the vehicle 1 and the charging facility 2 execute the charging process (S540).

[0066] On the other hand, as shown in FIG. 10, in the processing of this embodiment, similarly to FIG. 9, even if the charging equipment 2 stops processing (S530), the vehicle 1 executes the charging sequence (S1 to S8), so that the charging processing can be executed under the initiative of the vehicle 1 (S20) without manual operation by the user.

[0067] That is, in this embodiment, a charging control device 10 including a charging control unit 11 is exemplified. As in the comparative example of Fig. 3, the charging control unit 11 is provided in a vehicle 1 equipped with a battery 19, and performs authentication using certificate information (e.g., a Contract certificate) by communicating with the charging facility 2 (S10, S11, etc. in Fig. 3). After the authentication is successful, the charging control unit 11 transmits a control signal to the charging facility 2 via the communication IC 12 to cause the charging facility 2 to charge the battery 19 (Fig. 3).

[0068] However, in this embodiment, the charging control unit 11 transmits a control signal (PaymentServiceSelection.Req) to the charging facility 2 to charge the battery using the charging method (PnC) using the certificate information, and then transmits the control signal (PaymentServiceSelection.Req) to the charging facility 2 using the certificate information. This is effective when nC is not available. In such a case, the charging control unit 11 of the vehicle 1 disconnects communication with the charging facility 2. Disconnection of communication is exemplified by, for example, disconnection of TCP (S0) in FIG. 6, and disconnection of TCP (S0) and disconnection of data link (S1) in FIG. 7 and FIG. 8. Then, the charging control unit 11 reconnects communication with the charging facility 2. The process of reconnecting communication is exemplified by establishment of TCP (S4, S5) in FIG. 6, and establishment of data link (S2) and establishment of TCP (S4, S5) in FIG. 7 and FIG. 8. Then, the charging control unit 11 of the vehicle 1 transmits a control signal (PaymentServiceSelection.Req) to the charging facility 2 to charge using a charging method based on EIM that does not depend on certificate information (S7). In this manner, in this embodiment, The charging control unit 11 mounted on the vehicle 1 in the form of a payment service selection unit 11 first transmits a control signal (PaymentServiceSelection.Req) to the charging facility 2 to indicate that charging will be performed using a charging method (PnC) using certificate information. In other words, when PnC is not available, the vehicle 1 can switch the charging method from the charging method using the certificate information (PnC) to the charging method using EIM under the initiative of the vehicle 1.

[0069] Furthermore, as illustrated in FIG. 8, when the charging method using the certificate information is unavailable, the charging control unit 11 disconnects the TCP between the charging facility 2 and the vehicle 1 (S0). TCP is an example of a first communication procedure using logical addresses. The IP addresses given to the charging control unit 11 and the equipment control unit 21 used in TCP are an example of logical addresses. On the other hand, the MAC addresses corresponding to the IP addresses, which are an example of logical addresses, and which are uniquely set in the communication interfaces of the charging control unit 11 of the vehicle 1 and the equipment control unit 21 of the charging facility 2 can be considered as an example of physical addresses. This communication at the data link layer using physical addresses can be considered as a second communication procedure.

[0070] The charging control unit 11 disconnects the communication by TCP, which corresponds to the first communication procedure, between the TCP and the communication at the data link layer, and transmits a control signal for re-establishing TCP from the communication IC 12 to the charging equipment 2. After re-establishing TCP, the charging control unit 11 then transmits a control signal (PaymentServiceSelection.Req) from the communication IC 12 to the charging equipment 2 to the effect that charging will be performed using a charging method (EIM) that does not depend on certificate information. In this way, in this embodiment, Even after the vehicle 1 has once sent a control signal to the charging equipment 2 indicating that charging will be performed using PnC, the vehicle 1 can take the initiative to switch the charging method from a charging method using certificate information (PnC) to a charging method using EIM.

[0071] Furthermore, in this embodiment, after disconnecting the first communication procedure (communication procedure by TCP) and the second communication procedure (communication procedure at the data link layer), the charging control unit 11 determines whether the charging equipment 2 is in an activated state from the duty ratio of the CPLT signal on the communication line CL. Then, when the charging equipment 2 is in an activated state, the charging control unit 11 transmits a control signal (SLAC sequence signal) for establishing communication at the data link layer, which is an example of the second communication procedure, from the communication IC 12 to the charging equipment 2. Then, after establishing communication at the data link layer, the charging control unit 11 (or the communication IC 12) transmits a control signal for establishing TCP (UDP message SECCDiscoveryProtocol.Req) from the communication IC 12 to the charging equipment 2. Then, the charging control unit 1 After establishing the first communication procedure, the communication IC 1 (or the communication IC 12) transmits a control signal (PaymentServiceSelection.Req) to the communication IC 12 to indicate that charging is to be performed using a charging method (EIM) that does not depend on certificate information. C12 to the charging facility 2. In this way, in this embodiment, even after the vehicle 1 once transmits a control signal to the charging facility 2 to charge by PnC, the vehicle 1 can take the initiative in switching the charging method from the charging method using the certificate information (PnC) to the charging method using EIM. That is, when the vehicle 1 can determine that the charging facility 2 is in an activated state from the duty ratio of the CPLT signal on the communication line CL, it is sufficient to establish communication with the data link layer and TCP in that order.

[0072] Also, as illustrated in FIG. 8, if the charging equipment 2 is not in an activated state after disconnecting the first communication procedure and the second communication procedure, the charging control unit 11 transmits a start-up signal (BCB toggle) for activating the charging equipment 2 from the communication IC 12 to the charging equipment 2. Then, if the charging control unit 11 (or the communication IC 12) can confirm that the charging equipment 2 is in an activated state, it transmits a control signal (SLAC sequence signal) for establishing communication of the data link layer, which is the second communication procedure, to the charging equipment 2. Then, after establishing the second communication procedure, the charging control unit 11 (or the communication IC 12) transmits a control signal (SECCDiscoveryProtocol.Req) for establishing the first communication. Then, after establishing the first communication procedure, the charging control unit 11 transmits the certificate information In this embodiment, the vehicle 1 transmits a control signal (PaymentServiceSelection.Req) to the charging facility 2, the control signal indicating that the charging method is to be performed using the charging method (EIM) that does not depend on the information. However, even if the charging equipment 2 is no longer in an activated state (sleep state or hibernation state) after a control signal indicating PnC charging is once transmitted to the charging equipment 2, the vehicle 1 can switch the charging method. That is, in this embodiment, even in such a case, the vehicle 1 can take the initiative in switching the charging method from the charging method using the certificate information (PnC) to the charging method using EIM.

[0073] <Second embodiment> Hereinafter, the charge control device 10, the charge control method, and the program according to the second embodiment will be described with reference to Fig. 11. In the above embodiment, a process is exemplified in a case where the charging method using the certificate information (Contract certificate) is not available after the vehicle 1 transmits to the charging equipment 2 a notice of charging using the charging method (PnC) using the certificate information (Contract certificate, etc.). In such a case, the first embodiment exemplified a process in which the vehicle 1 takes the initiative to switch the charging method from the charging method using the certificate information (PnC) to the charging method using EIM. In the present embodiment, a process is exemplified in such a case where the user is first prompted to select whether or not to switch.

[0074] Fig. 11 is a sequence diagram illustrating the process in the second embodiment. In Fig. 11, the process from S527, S528, and S529 after the plug 2B is attached to the power receiving unit of the vehicle 1 is similar to that in Fig. 6 to Fig. 8 in the first embodiment, and therefore the description thereof will be omitted.

[0075] In the process of FIG. 11, when the charging control unit 11 of the vehicle 1 detects that the PnC cannot be executed (S529), the charging control unit 11 confirms with the user whether or not to execute charging by EIM (S0A). The confirmation to the user is, for example, displayed on the in-vehicle display 144 or output of sound from the in-vehicle speaker, or displayed on the display 24 of the charging facility 2 or output of sound from the speaker. The confirmation to the user is detected by the user's response to the in-vehicle control unit 14 via an input device, or the user's response to the charging facility 2 via an input device. Here, the input device is, for example, a push button, a touch panel on which a graphic object for input is formed, or the like. The confirmation to the user may be via a user device recognized by the charging facility 2 or the server 5, or the like. Here, the user device is, for example, a mobile information terminal, a mobile phone, a smartphone, or the like. The in-vehicle display 144, the display 24, the display device of the user device, or the like are examples of the display device.

[0076] When the user selects to charge using EIM (YES in S0A), the charge control unit 11 executes the process of S0 to S8 as in Fig. 6 of the first embodiment. However, the charge control unit 11 may execute the process of S0 to S8 in Fig. 7 or the process of S0 to S8 in Fig. 8. On the other hand, when the user selects not to charge using EIM (NO in S0A), the charge control unit 11 ends the process of Fig. 11.

[0077] As described above, in this embodiment, if PnC is not available after the vehicle 1 once transmits a control signal to the charging facility 2 to charge using the charging method using certificate information (PnC), the vehicle 1 first confirms the user's intention. Then, when the user selects to charge using EIM, the charging control unit 11 executes the same process as in the first embodiment. Therefore, in this embodiment, even if PnC is not available after a signal to charge using the charging method using certificate information (PnC) is once transmitted to the charging facility 2, the user's intention is prioritized, and flexible processing according to the user's intention is executed.

[0078] In this embodiment, the process (S0A) of confirming with the user whether or not to perform charging by EIM is not limited to the case of Fig. 11. For example, the process (S0A) of confirming with the user whether or not to perform charging by EIM may be executed after disconnection of TCP (S0) in Fig. 6, Fig. 7 or Fig. 8. Moreover, the process of S0A may be executed after disconnection of the data link (S1) in Fig. 7 or Fig. 8. This is because the user's intention may change.

[0079] 7, the charging control unit 11 may execute the process of S0A before the SLAC sequence (S2) after confirming that the charging equipment 2 is activated by the CPLT signal (after confirming that the duty ratio is 5%). This is because the user's intention may change depending on the status of the charging equipment 2. Furthermore, in the process of FIG. 8, the charging control unit 11 may execute the process of S0A after confirming that the charging equipment 2 is stopped or in sleep mode by the CPLT signal.

[0080] For example, the charging control unit 11 may execute a process (S0A) to confirm with the user before transmitting a BCB toggle (charging stand activation request) to the charging equipment 2 by the communication IC 12. This is because the user may want to determine whether or not it is necessary to activate the charging equipment 2. Also, for example, the charging control unit 11 may execute a process (S0A) to confirm with the user after transmitting a BCB toggle to the charging equipment 2 by the communication IC 12 and after the charging equipment 2 is activated. This is because the user's intention may change further.

[0081] Note that if the vehicle 1 once transmits to the charging facility 2 a notice that charging will be performed using the charging method using certificate information (PnC), and the charging method using certificate information is not available, the user may be able to select the charging method using EIM at any time. The charging control unit 11 may display to the user, for example, on the in-vehicle display 144 or the display 24 of the charging facility 2, that the charging method can be switched. Then, the charging control unit 11 may display to the user, for example, on a user interface of a user device recognized by the in-vehicle control unit 14, the charging facility 2, the server 5, etc. Therefore, it is sufficient to accept the user's intention. For example, even if the charging control unit 11 is already performing various V2G communication processes with the charging facility 2, the vehicle 1 may accept an input indicating the user's intention by priority processing or interrupt processing. By such processing, the system including the vehicle 1 and the charging facility 2 can flexibly provide charging processing to the user.

[0082] <Computer-readable recording medium> A program for causing a computer or other machine or device (hereinafter, referred to as a computer, etc.) to realize any of the above functions can be recorded on a recording medium readable by the computer, etc. Then, the computer, etc. can provide the function by reading and executing the program from the recording medium.

[0083] Here, a computer-readable recording medium refers to a recording medium that stores information such as data and programs through electrical, magnetic, optical, mechanical, or chemical action and can be read by a computer. Examples of such recording media that can be removed from a computer include flexible disks, magneto-optical disks, CD-ROMs, CD-R / Ws, DVDs, Blu-ray disks, DATs, 8mm tapes, and memory cards such as flash memory. Examples of recording media that are fixed to a computer include hard disks and ROMs (read-only memories). Furthermore, SSDs (Solid State Drives) are also recording media that can be removed from a computer, and can be read by a computer. The present invention can also be used as a recording medium fixed to a computer.

[0084] <Other> The above first and second embodiments include the following aspects (referred to as supplementary notes). (Appendix 1) A charging control device that is provided in a vehicle equipped with a battery and controls charging of the battery by communicating with a charging facility outside the vehicle, a controller that, when a charging start input is received, establishes a communication connection with the charging equipment, transmits a control signal to the charging equipment indicating a charging method for charging, and, when the charging method indicated by the transmitted control signal is a charging method using certificate information, performs authentication processing of the certificate information and then transmits a control signal to the charging equipment to charge the battery; The controller: If the charging method using the certificate information becomes unavailable after transmitting a control signal indicating the charging method using the certificate information to the charging equipment, the charging control device disconnects communication with the charging equipment, reconnects communication with the charging equipment, and then transmits a control signal indicating a charging method not based on the certificate information to the charging equipment. (Appendix 2) The charging control device according to claim 1, wherein, when a charging method using the certificate information is unavailable, the controller disconnects the first communication procedure among a first communication procedure using a logical address between the charging equipment and the vehicle and a second communication procedure using a physical address that corresponds to the logical address and is uniquely set in each communication interface of the charging equipment and the vehicle, transmits a control signal to re-establish the first communication procedure, and transmits a control signal to the charging equipment after re-establishing the first communication procedure to charge using a charging method not using the certificate information. (Appendix 3) The charging control device described in Appendix 2, wherein after disconnecting the first communication procedure and the second communication procedure, when the charging equipment is in an activated state, the controller transmits a control signal to the charging equipment to establish the second communication procedure, and after establishing the second communication procedure, transmits a control signal to the charging equipment to establish the first communication procedure, and after establishing the first communication procedure, transmits a control signal to the charging equipment to charge using a charging method not based on the certificate information. (Appendix 4) The charging control device according to Appendix 2 or 3, wherein the controller transmits a start-up signal to switch the charging equipment to the started state if the charging equipment is not in the started state after disconnecting the first communication procedure and the second communication procedure, transmits a control signal to the charging equipment to establish the second communication procedure if it is confirmed that the charging equipment is in the started state, transmits a control signal to the charging equipment to establish the first communication procedure after establishing the second communication procedure, and transmits a control signal to the charging equipment to charge using a charging method not based on the certificate information after establishing the first communication procedure. (Appendix 5) 5. The charging control device according to claim 1, wherein the controller transmits a control signal to the charging equipment to instruct charging to be performed using a charging method using the certificate information, and then transmits a control signal to a display device to inquire of a user about a charging method if the charging method using the certificate information is unavailable. (Appendix 6) 4. The charge control device according to claim 3, further comprising: a control signal for inquiring of a user about a charging method, the control signal being transmitted to a display device after the first communication procedure and the second communication procedure are disconnected. (Appendix 7) A charging control method that is provided in a vehicle equipped with a battery and controls charging of the battery by communicating with a charging facility outside the vehicle, comprising: when a charging start input is received, establishing a communication connection with the charging equipment and transmitting a control signal indicating a charging method for charging to the charging equipment, and when the charging method indicated by the transmitted control signal is a charging method using certificate information, performing authentication processing of the certificate information and then transmitting a control signal to the charging equipment to charge the battery; and if, after transmitting a control signal indicating a charging method using the certificate information to the charging equipment, the charging method using the certificate information becomes unavailable, disconnecting communication with the charging equipment, and reconnecting communication with the charging equipment, and then transmitting a control signal indicating a charging method not based on the certificate information to the charging equipment. (Appendix 8) A program for causing a computer to be provided in a vehicle equipped with a battery and to communicate with a charging facility outside the vehicle to control charging of the battery, when a charging start input is received, establishing a communication connection with the charging equipment and transmitting a control signal indicating a charging method for charging to the charging equipment, and when the charging method indicated by the transmitted control signal is a charging method using certificate information, performing authentication processing of the certificate information and then transmitting a control signal to the charging equipment to charge the battery; and if the charging method using the certificate information becomes unavailable after a control signal indicating a charging method using the certificate information is transmitted to the charging equipment, disconnecting communication with the charging equipment, reconnecting communication with the charging equipment, and then transmitting a control signal indicating a charging method not based on the certificate information to the charging equipment. [Explanation of symbols]

[0085] 1 vehicle 2 Charging equipment 5 Server 10. Charging control device 11 Charging control unit 12, 22 Communication IC 13 Communication control section 14 Vehicle control unit 21 Equipment Control Section 24 Display 111, 121, 131, 141 CPUs 112, 122, 132, 142 ROM 144 In-vehicle display 211 CPU 212 Memory

Claims

1. A charging control device that is provided in a vehicle equipped with a battery and controls charging of the battery by communicating with a charging facility outside the vehicle, a controller that, when a charging start input is received, establishes a communication connection with the charging equipment, transmits a control signal to the charging equipment indicating a charging method for charging, and, when the charging method indicated by the transmitted control signal is a charging method using certificate information, performs authentication processing of the certificate information and then transmits a control signal to the charging equipment to charge the battery; The controller: If the charging method using the certificate information becomes unavailable after transmitting a control signal indicating the charging method using the certificate information to the charging equipment, the charging control device disconnects communication with the charging equipment, reconnects communication with the charging equipment, and then transmits a control signal indicating a charging method not based on the certificate information to the charging equipment.

2. 2. The charging control device according to claim 1, wherein, when a charging method using the certificate information is unavailable, the controller disconnects the first communication procedure among a first communication procedure using a logical address between the charging equipment and the vehicle and a second communication procedure using a physical address that corresponds to the logical address and is uniquely set in each communication interface of the charging equipment and the vehicle, transmits a control signal to re-establish the first communication procedure, and transmits a control signal to the charging equipment after re-establishing the first communication procedure to charge using a charging method not using the certificate information.

3. 3. The charging control device according to claim 2, wherein, after disconnecting the first communication procedure and the second communication procedure, when the charging equipment is in an activated state, the controller transmits a control signal to the charging equipment to establish the second communication procedure, and after establishing the second communication procedure, transmits a control signal to the charging equipment to establish the first communication procedure, and after establishing the first communication procedure, transmits a control signal to the charging equipment to charge using a charging method not based on the certificate information.

4. 3. The charging control device according to claim 2, wherein the controller transmits a start-up signal to switch the charging equipment to the started state when the charging equipment is not in the started state after disconnecting the first communication procedure and the second communication procedure, and when it is confirmed that the charging equipment is in the started state, transmits a control signal to the charging equipment to establish the second communication procedure, transmits a control signal to the charging equipment to establish the first communication procedure after establishing the second communication procedure, and transmits a control signal to the charging equipment to charge using a charging method not based on the certificate information after establishing the first communication procedure.

5. 2. The charging control device according to claim 1, wherein the controller transmits a control signal to the charging equipment to instruct charging using a charging method using the certificate information, and then transmits a control signal to a display device to inquire of a user about a charging method if the charging method using the certificate information is unavailable.

6. 4. The charge control device according to claim 3, further comprising: a control signal for inquiring of a user about a charging method, the control signal being transmitted to a display device after the first communication procedure and the second communication procedure are disconnected.

7. A charging control method that is provided in a vehicle equipped with a battery and controls charging of the battery by communicating with a charging facility outside the vehicle, comprising: When a charging start input is received, the charging device communicates with the charging equipment and transmits a control signal indicating a charging method for charging to the charging equipment. If the charging method indicated by the transmitted control signal is a charging method using certificate information, the charging device performs authentication processing of the certificate information and then transmits the transmitting a control signal to cause the battery to be charged; and if, after transmitting a control signal indicating a charging method using the certificate information to the charging equipment, the charging method using the certificate information becomes unavailable, disconnecting communication with the charging equipment, and reconnecting communication with the charging equipment, and then transmitting a control signal indicating a charging method not based on the certificate information to the charging equipment.

8. A program for causing a computer to be provided in a vehicle equipped with a battery and to communicate with a charging facility outside the vehicle to control charging of the battery, when a charging start input is received, establishing a communication connection with the charging equipment and transmitting a control signal indicating a charging method for charging to the charging equipment, and when the charging method indicated by the transmitted control signal is a charging method using certificate information, performing authentication processing of the certificate information and then transmitting a control signal to the charging equipment to charge the battery; and if the charging method using the certificate information becomes unavailable after a control signal indicating a charging method using the certificate information is transmitted to the charging equipment, disconnecting communication with the charging equipment, reconnecting communication with the charging equipment, and then transmitting a control signal indicating a charging method not based on the certificate information to the charging equipment.

Images