Control device and control method

Abstract

To provide a control device capable of preventing power transmission between an electric vehicle and a power stand from failing due to incompatibility between a route certificate corresponding to the electric vehicle and the power stand.SOLUTION: A battery information server 100 (control device) includes a communication unit 130 that transmits root certificate information to an EVSE 20 when requesting a contract certificate from the EVSE 20 (power stand), and a processor 110. When the communication unit 130 receives an inconsistency notification indicating that the root certificate is inconsistent with the EVSE 20, the processor 110 changes the root certificate. The communication unit 130 transmits the information of the changed root certificate to the EVSE 20.SELECTED DRAWING: Figure 3

Description

Technical Field

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

Background Art

[0002] International Publication No. 2021 / 1158021 (Patent Document 1) discloses an electric vehicle capable of charging by the PnC method from a charging station. When a contract certificate is stored (installed) in the electric vehicle, the above PnC charging becomes possible.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, although not specified in Patent Document 1 above, in order to store (install) a contract certificate in an electric vehicle (vehicle), it is necessary to transmit route certificate information from the electric vehicle to the charging station. However, since the syntax pattern (rule) of the route certificate corresponding to the electric vehicle is not defined by the standard, the route certificate may not match between the electric vehicle and the charging station. In this case, the contract certificate cannot be installed in the electric vehicle, and charging by the PnC method between the electric vehicle and the charging station cannot be performed. For this reason, charging control (power transmission) by the PnC method may not be established between the electric vehicle and the charging stand.

[0005] The present disclosure has been made to solve the above problems, and an object thereof is to provide a control device and a control method capable of suppressing the failure of power transmission between an electric vehicle and a power stand due to the route certificate corresponding to the electric vehicle being inconsistent with the power stand.

Means for Solving the Problems

[0006] A control device according to a first aspect of the present disclosure is a control device for a vehicle that communicates with a power stand capable of power transmission including at least one of charging and discharging, and includes a communication unit that transmits information on a route certificate to the power stand in order to acquire (request) a contract certificate, and a processor. When the communication unit receives a non-conformity notification indicating that the route certificate does not conform to the power stand, the processor changes the route certificate. The communication unit transmits information on the changed route certificate to the power stand. Note that the route certificate refers to a certificate of the root CA (Certificate Authority), which is a certification authority of a digital certificate, created by self-signing.

[0007] As described above, when the communication unit of the control device according to the first aspect of the present disclosure receives a non-conformity notification indicating that the route certificate does not conform to the power stand, the control device changes the route certificate and transmits information on the changed route certificate to the power stand. As a result, even when the route certificate does not conform to the power stand, a contract certificate can be requested (re-requested) using the changed route certificate. Therefore, compared with the case where a contract certificate cannot be re-requested, it is possible to suppress the failure of power transmission with the power stand. Therefore, it is possible to suppress the failure of power transmission between the electric vehicle and the power stand due to the route certificate corresponding to the electric vehicle being inconsistent with the power stand.

[0008] In the control device according to the first aspect, preferably, when it is determined that the changed root certificate matches the power stand, the communication unit transmits the information of the changed root certificate to the power stand without transmitting the information of the root certificate before the change to the power stand during the next power transmission with the power stand. With this configuration, it is possible to omit the transmission of the information of the root certificate that does not match the power stand and transmit the information of the root certificate with a proven track record of success to the power stand. As a result, the time required until it is determined that the root certificate matches the power stand in the next power transmission can be shortened.

[0009] In this case, preferably, the control device includes a storage unit that stores a root certificate that matches the power stand in association with the power stand. When the communication unit receives a matching notification indicating that the changed root certificate matches the power stand, (i) the processor updates the information in the storage unit, and (ii) the communication unit, during the next power transmission with the power stand, transmits the information of the changed root certificate based on the updated information in the storage unit to the power stand without transmitting the information of the root certificate before the change to the power stand. With this configuration, unlike the case where the information of the root certificate and the power stand that match each other are stored in an external device, the above information can be acquired without using communication with the external device. As a result, the inoperability in the control device can be reduced.

[0010] In the control device according to the first aspect, preferably, the charging station is configured to be able to charge the vehicle based on each of the PnC (Plug and Charge) charging method and the EIM (External Identification Means) charging method. When executing charging based on the PnC charging method, the processor repeatedly changes the root certificate until the changed root certificate matches the charging station, and when the number of times of changing the root certificate reaches a predetermined number of times, switches the charging method from the PnC charging method to the EIM charging method. With this configuration, when the charging sequence based on the PnC charging method cannot be appropriately started even after changing the root certificate a predetermined number of times, it is possible to abandon the execution of the PnC charging method and shift to the charging sequence based on the EIM charging method. As a result, charging can be started more quickly compared to the case where the change of the root certificate is further continued.

[0011] The control method according to the second aspect of the present disclosure is a control method by a control device of a vehicle that communicates with a charging station capable of power transmission including at least one of charging and discharging, and includes a first transmission step of transmitting information on a root certificate to the charging station in order to acquire a contract certificate, a reception step of receiving an inconsistency notification indicating that the root certificate does not match the charging station after the first transmission step, a change step of changing the root certificate after the reception step, and a second transmission step of transmitting information on the root certificate changed in the change step to the charging station.

[0012] In the control method according to the second aspect of the present disclosure, as described above, when the communication unit receives an inconsistency notification indicating that the root certificate does not match the charging station, the root certificate is changed and information on the changed root certificate is transmitted to the charging station. Thereby, it is possible to provide a control method capable of suppressing the non-establishment of power transmission between the electric vehicle and the charging station due to the root certificate corresponding to the electric vehicle being inconsistent with the charging station.

Advantages of the Invention

[0013] According to the present disclosure, it is possible to suppress the failure of power transmission between an electric vehicle and a power stand due to the route certificate corresponding to the electric vehicle being inconsistent with the power stand.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Embodiments for Carrying Out the Invention

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

[0016] <Configuration of Charging System> FIG. 1 is a diagram showing the configuration of a charging system 200 according to the present embodiment. The charging system 200 includes an electric vehicle 10 equipped with an ECU 100 and an EVSE (Electric Vehicle Supply Equipment) 20. Note that the electric vehicle 10 and the EVSE 20 are examples of the "vehicle" and the "power stand" of the present disclosure, respectively. Also, the ECU 100 is an example of the "control device" of the present disclosure.

[0017] The electric vehicle 10 includes, for example, a PHEV (Plug-in Hybrid Electric Vehicle), a BEV (Battery Electric Vehicle), or an FCEV (Fuel Cell Electric Vehicle).

[0018] EVSE20 means vehicle power supply equipment. The electric vehicle 10 is configured to be electrically connectable to the EVSE20. The EVSE20 includes a cable 20b to which a connector 20a is attached. When the connector 20a is connected to an inlet (not shown) of the electric vehicle 10, power is supplied (charged) from the EVSE20 to the electric vehicle 10. Note that charging is an example of "power transmission" in the present disclosure.

[0019] The EVSE20 is configured to be able to charge an electric vehicle based on each of the PnC (Plug and Charge) charging method and the EIM (External Identification Means) charging method. The PnC charging method refers to a charging method in which, simply by connecting the connector 20a of the EVSE20 to the electric vehicle 10, processes such as billing authentication and charging are automatically executed. The EIM charging method refers to a charging method in which a user of the electric vehicle 10 makes a payment at the installation location of the EVSE20 or on the EVSE20 main body using cash, electronic money, or the like.

[0020] The electric vehicle 10 includes an ECU (Electric Control Unit) 100, a battery pack 1, a GPS (Global Positioning System) module 2, and a DCM (Data Communication Module) 3.

[0021] The battery pack 1 stores, for example, the power used for the running of the electric vehicle 10. It is possible to increase the power storage amount of the battery pack 1 by charging from the EVSE20.

[0022] The GPS module 2 receives GPS signals transmitted from three or more (preferably four or more) satellites above the electric vehicle 10 and measures the position of the electric vehicle 10 (the own vehicle). The position information of the electric vehicle 10 measured by the GPS module 2 is transmitted to the DCM3 by CAN communication or the like. Note that the GPS module 2 may be built into a car navigation device (not shown) or the like.

[0023] DCM3 is configured to be able to access an external communication server, the Internet, etc. Thus, the electric vehicle 10 can acquire various information from the outside through DCM3.

[0024] The ECU 100 transmits and receives information to and from the battery pack 1, the GPS module 2, DCM3, etc. through CAN communication by the communication unit 130 described later. Further, the ECU 100 is configured to control each of the above devices.

[0025] The ECU 100 includes a processor 110, a memory 120, and a communication unit 130. In the memory 120, in addition to the program executed by the processor 110, information used in the program (for example, maps, mathematical formulas, and various parameters) is stored. Note that the memory 120 is an example of the "storage unit" of the present disclosure.

[0026] The memory 120 stores the root certificate shown in FIG. 2. In the example shown in FIG. 2, three root certificates 1 to 3 are stored in the memory 120. Note that the root certificate refers to the certificate of the root CA, which is the certification authority of the digital certificate, created by self-signing.

[0027] The memory 120 stores the root certificate that matches the EVSE 20 in association with the EVSE 20. When it is determined that the root certificate matches the EVSE 20, the processor 110 stores (updates the information in the memory 120) the root certificate and the EVSE 20 in association with each other in the memory 120.

[0028] The communication unit 130 transmits the root certificate information to the EVSE 20 in order to obtain (request) a certificate of contract. When obtaining a certificate of contract via the EVSE 20, the processor 110 creates a list of root certificates based on the root certificate profile stored in the memory 120. For example, the processor 110 creates a list in which information is set in at least one of the items of "SerialNumber", "CommonName", "Country", "Organization", "Organization Unit", and "Domain Component" based on the root certificate profile. Then, the processor 110 transmits the created list to the EVSE 20 through the communication unit 130. Hereinafter, the pattern of the item in which information is set is referred to as a "syntax pattern".

[0029] When the connector 20a is connected to the electric vehicle 10, the communication unit 130 transmits and receives information to and from the EVSE 20 (communication unit 23 described later) through the cable 20b.

[0030] The EVSE 20 includes a processor 21, a memory 22, and a communication unit 23. In addition to the program executed by the processor 21, the memory 22 stores information used in the program (for example, maps, mathematical formulas, and various parameters).

[0031] Here, in order to store (install) a certificate of contract in an electric vehicle, it is necessary to transmit the root certificate information from the electric vehicle to the EVSE. However, since the syntax pattern (rule) of the root certificate corresponding to the electric vehicle is not defined by the standard, the root certificate may not match between the electric vehicle and the EVSE. In this case, the certificate of contract cannot be installed in the electric vehicle, and charging by the PnC method between the electric vehicle and the EVSE cannot be performed. For this reason, the charging control by the PnC charging method between the electric vehicle and the EVSE may not be established.

[0032] Therefore, in this embodiment, when the communication unit 130 receives an inconsistency notification indicating that the root certificate does not match the EVSE 20, the processor 110 changes the root certificate. Specifically, the processor 110 changes the root certificate by changing the items in which information is set in the root certificate. Then, the communication unit 130 transmits the information of the changed root certificate to the EVSE 20. Details will be described with reference to FIG. 3.

[0033] <Sequence Control of Charging System> FIG. 3 is a diagram showing sequence control (S2 to S19 described later) corresponding to the control method by the charging system 200. Each process of the electric vehicle 10 shown in FIG. 3 is executed by the ECU 100 (processor 110). Each process of the EVSE 20 is executed by the processor 21.

[0034] In step S1, the connector 20a of the EVSE 20 is connected to the electric vehicle 10. Thereby, the PnC charging of the electric vehicle 10 becomes possible.

[0035] In step S2, the electric vehicle 10 determines whether the EVSE 20 connected in step S1 is the first EVSE to be connected to the electric vehicle 10. The electric vehicle 10 makes the above determination based on, for example, the charging history information (position information where PnC charging was performed or ID information of the EVSE where PnC charging was performed, etc.) stored in the memory 120. If it is the first time to be connected to the EVSE 20 (Yes in S2), the process proceeds to step S3. If it has been connected to the EVSE 20 in the past (No in S2), the process proceeds to step S4. Note that being connected to the EVSE 20 in the past means that there is a record of PnC charging having been performed with the EVSE 20 in the past. Also, being connected to the EVSE 20 for the first time means that there is no record of performing PnC charging with the EVSE 20.

[0036] In step S3, the electric vehicle 10 creates a list based on the syntax patterns with many successful PnC charging records in the EVSEs installed in each region. The above performance information is stored, for example, in an external server (not shown) that can communicate with the DCM3.

[0037] In step S4, the electric vehicle 10 creates a list based on the syntax patterns with past successful PnC charging records in the EVSE 20. The above past performance information is stored in the memory 120 of the electric vehicle 10. Note that the above past performance information may be stored in an external server (not shown) that can communicate with the DCM3. If there are multiple syntax patterns with successful records, a syntax pattern may be randomly selected from the multiple syntax patterns with successful records, or the syntax pattern with the highest priority based on a predetermined condition (for example, in ascending order of the number of set items) may be selected.

[0038] In step S5, in order to obtain (request) a certificate of contract, the electric vehicle 10 transmits the information of the root certificate based on the list created in step S3 or S4 to the EVSE 20 through the communication unit 130. For example, it is assumed that the information of the root certificate based on the syntax pattern in which information is set in two items of "SerialNumber" and "CommonName" shown in FIG. 2 is transmitted to the EVSE 20.

[0039] In step S6, the EVSE 20 determines whether it has received the information of the root certificate transmitted from the electric vehicle 10 in step S5. If the information of the root certificate has been received (Yes in S6), the process proceeds to step S7. If the information of the root certificate has not been received (No in S6), the process of step S7 is repeated.

[0040] In step S7, the EVSE 20 determines whether the route certificate corresponding to the electric vehicle 10 matches the EVSE 20 (itself) based on the information received in step S6. If the route certificate matches the EVSE 20 (Yes in S7), the process proceeds to step S8. If the route certificate does not match the EVSE 20 (No in S7), the process proceeds to step S9.

[0041] In step S8, the EVSE 20 transmits a contract certificate issued by a PKI (Public Key Infrastructure) provider to the electric vehicle 10 through the communication unit 23.

[0042] In step S9, the EVSE 20 transmits to the electric vehicle 10 that the route certificate based on the information received in step S6 does not match the EVSE 20 through the communication unit 23.

[0043] In step S10, the electric vehicle 10 determines whether it has received the mismatch notification in step S9. If it has not received the mismatch notification (No in S10), the process proceeds to step S11. If it has received the mismatch notification (Yes in S10), the process proceeds to step S14.

[0044] In step S11, the electric vehicle 10 receives the contract certificate transmitted from the EVSE 20 in step S8.

[0045] In step S12, a set of a route certificate that matches each other and the EVSE 20 (the set of the route certificate in S5 and the EVSE 20) is recorded in the memory 120 (the information in the memory 120 is updated).

[0046] In step S13, the electric vehicle 10 starts a charging session (PnC session) based on the PnC charging method.

[0047] In step S14, the electric vehicle 10 determines whether the number of changes to the route certificate (syntax pattern) has reached 2. If the number of changes to the route certificate has reached 2 (Yes in S14), the process proceeds to step S15. If the number of changes to the route certificate is less than 2 (No in S14), the process proceeds to step S16.

[0048] In step S15, the electric vehicle 10 abandons PnC charging and starts a charging session (EIM session) based on the EIM charging method. Next, the process proceeds to step S17.

[0049] In step S16, the electric vehicle 10 changes the syntax pattern of the route certificate. For example, the electric vehicle 10 changes the syntax pattern by increasing the number of items for which information is set by one (for example, adding information to the item corresponding to "Country"). Note that the method of changing the syntax pattern is not limited to the above example. Next, the process returns to step S5. That is, in step S5, the changed syntax pattern of the route certificate is transmitted to the EVSE 20.

[0050] Suppose that in step S7 after the process returns to step S5, it is determined that the route certificate with the changed syntax pattern matches the EVSE 20. Thereafter, in step S11, the electric vehicle 10 receives the contract certificate of step S8 (corresponding to "receiving the consistency notification" of the present disclosure). In this case, the electric vehicle 10 (processor 110) updates the information in the memory 120 in step S12 so that the route certificate with the changed syntax pattern and the EVSE 20 are associated with each other. The electric vehicle 10 (communication unit 130) transmits, to the EVSE 20 during the next charging with the EVSE 20 (next step S4), the information of the route certificate after the change based on the updated information in the memory 120 without transmitting the information of the route certificate before the change to the EVSE 20.

[0051] In step S17, charging authentication is performed between the electric vehicle 10 and the EVSE 20. In step S18, charging between the electric vehicle 10 and the EVSE 20 is started. In step S19, the charging ends. In step S20, the connection state between the connector 20a of the EVSE 20 and the electric vehicle 10 is released.

[0052] As described above, in this embodiment, when the communication unit 130 receives an inconsistency notification indicating that the root certificate does not match the EVSE 20, the processor 110 changes the root certificate. The communication unit 130 transmits the information of the changed root certificate to the EVSE 20. Thereby, even when the root certificate does not match the EVSE 20, the root certificate can be changed and the connection for PnC charging can be attempted again. As a result, it is possible to suppress the PnC charging from ending without success (switching to EIM charging).

[0053] In the above embodiment, an example in which control for changing the root certificate is executed during charging control of the electric vehicle 10 is shown, but the present disclosure is not limited to this. Control for changing the root certificate may be performed during discharge control of the electric vehicle 10. Also, control for changing the root certificate may be performed both during charging control and discharge control of the electric vehicle 10.

[0054] In the above embodiment, an example is shown in which when it is determined that the changed root certificate matches the EVSE 20, in the next charging at the EVSE 20, the information of the root certificate before the change is not transmitted to the EVSE 20, and the information of the root certificate after the change is transmitted to the EVSE 20. However, the present disclosure is not limited to this. The electric vehicle may first transmit the root certificate before the change (default root certificate) to the EVSE 20 regardless of the determination in the previous charging.

[0055] In the above embodiment, an example is shown in which when the number of times of changing the root certificate reaches a predetermined number of times (2 times in the above embodiment), the EIM session is switched. However, the present disclosure is not limited to this. When the number of times of changing the root certificate reaches a predetermined number of times, the charging control itself may end.

[0056] In the above embodiment, an example in which the EIM session is switched when the number of times of changing the root certificate reaches 2 is shown, but the present disclosure is not limited thereto. The upper limit of the number of times of changing the root certificate may be other than 2 times. For example, the electric vehicle 10 may be able to change the root certificate until information is set in all items of the syntax pattern shown in FIG. 2. Specifically described. Assume that when the electric vehicle 10 changes the root certificate, it is possible to increase the items (see FIG. 2) in which information is set one by one. For example, the electric vehicle 10 changes the root certificate by setting information in "Country" from the state of FIG. 2. Therefore, the electric vehicle 10 can add information to each item of "Country", "Organization", "Organization Unit", and "Domain Component" from the state of FIG. 2, so it is possible to change the root certificate 4 times. Note that the method of changing the root certificate is not limited to the above example.

[0057] In the above embodiment, an example in which the EVSE 20 determines the consistency between the root certificate and the EVSE 20 is shown, but the present disclosure is not limited thereto. For example, the above determination may be made by an external server different from the EVSE 20. Further, the result of the above determination (inconsistency notification and consistency notification) may be transmitted from the external server to the electric vehicle 10.

[0058] In the above embodiment, an example in which it is determined whether it is the first time that the electric vehicle 10 and the EVSE 20 are connected after the connector 20a is connected is shown, but the present disclosure is not limited thereto. For example, whether it is the first time that the electric vehicle 10 and the EVSE 20 are connected may be determined in response to the EVSE 20 being searched by the car navigation or the electric vehicle 10 stopping near the EVSE 20.

[0059] In the above embodiment, an example was shown in which the information (list of syntax patterns) of the route certificate first transmitted to the EVSE 20 is adjusted according to whether it is the first connection between the electric vehicle 10 and the EVSE 20 (see S3 and S4 in FIG. 3). However, the present disclosure is not limited to this. Regardless of whether it is the first connection between the electric vehicle 10 and the EVSE 20, the information of the route certificate first transmitted to the EVSE 20 may be constant (for example, default route certificate information).

[0060] Note that the controls of the above embodiment and the various modifications described above may be executed in combination with each other.

[0061] The embodiments disclosed this time should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is indicated by the scope of claims rather than the description of the above embodiments, and it is intended that all modifications within the meaning and scope equivalent to the scope of claims be included.

Description of Reference Numerals

[0062] 10 Electric vehicle (vehicle), 20 EVSE (charging station), 100 ECU (control device), 110 Processor, 120 Memory (storage unit), 130 Communication unit.

Claims

1. A control device for a vehicle that communicates with a power stand capable of power transmission including at least one of charging and discharging, a communication unit that transmits information on a root certificate to the power stand in order to obtain a certificate of contract, and a processor, wherein when the communication unit receives a mismatch notification indicating that the root certificate does not match the power stand, the processor changes the root certificate, and the communication unit transmits information on the changed root certificate to the power stand. The control device.

2. When it is determined that the changed root certificate matches the power stand, the communication unit transmits information on the changed root certificate to the power stand without transmitting information on the root certificate before the change when performing the next power transmission with the power stand. The control device according to claim 1.

3. further comprising a storage unit that stores in association with the power stand the root certificate that matches the power stand, when the communication unit receives a match notification indicating that the changed root certificate matches the power stand, the processor updates the information in the storage unit, and the communication unit transmits information on the changed root certificate based on the updated information in the storage unit to the power stand without transmitting information on the root certificate before the change when performing the next power transmission with the power stand. The control device according to claim 2.

4. The power stand is configured to be able to charge the vehicle based on each of the PnC (Plug and Charge) charging method and the EIM (External Identification Means) charging method, the processor, when performing charging based on the PnC charging method, repeatedly changes the root certificate until the changed root certificate matches the power stand, and when the number of times of changing the root certificate reaches a predetermined number of times, switches the charging method from the PnC charging method to the EIM charging method. The control device according to any one of claims 1 to 3.

5. A control method by a control device for a vehicle that communicates with a power stand capable of power transmission including at least one of charging and discharging, a first transmission step of transmitting information on a root certificate to the power stand in order to obtain a certificate of contract, After the first transmission step, a receiving step of receiving an inconsistency notification indicating that the route certificate does not match the power stand; After the receiving step, a changing step of changing the route certificate; A second transmission step of transmitting information on the route certificate changed in the changing step to the power stand, a control method comprising.

Images