Electric vehicle, energy supply device, and energy supply system

Abstract

An electric vehicle replenishes energy independently from each of a plurality of energy supply devices that supply energy. The electric vehicle includes a controller. The controller is configured to: maintain a plurality of vehicle control softwares associated with at least two control softwares of each of the plurality of energy supply devices, and select, when replenishing energy from any one of the plurality of energy supply devices, a vehicle control software associated with the control software of the any one energy supply device from among the plurality of vehicle control softwares.

Description

Technical Field

[0001] The present invention relates to an electrically-powered vehicle, an energy supply device, and an energy supply system. Background Art

[0002] There is known a technique in which a server provides a charging station information including information on the location, availability, and accessibility of a charging station to an electric vehicle. The charging station information includes compatibility between the charging station and the electric vehicle (e.g., plug type support) as availability (e.g., see Japanese Unexamined Patent Application Publication No. 2014-212690 (JP2014-212690A)). Summary of the Invention

[0003] Compatibility between an energy supply device including a charging station and an electrically-powered vehicle including an electric vehicle is not only hardware compatibility such as a plug type, but also software compatibility such as a program for controlling the energy supply device or the electric vehicle.

[0004] For an energy supply device installed in a place such as a public facility and a commercial facility, when the server regularly provides the latest software to the energy supply device via, for example, wired communication, the energy supply device can be updated to the latest state. When the server provides software for an electric vehicle that is compatible with the latest software to the electric vehicle via, for example, wireless communication, the electric vehicle can supply energy from the energy supply device updated to the latest state to supplement energy.

[0005] However, an energy supply device installed in a residence or the like where the usage frequency of an electric vehicle is high may obtain the latest software irregularly from the server by manual operation. When forgetting to obtain the latest software, the electric vehicle provided with the software for the electric vehicle and the energy supply device installed in a residence or the like may not support each other, and the electric vehicle may not be able to supplement energy from the energy supply device.

[0006] The present invention provides an electrically-powered vehicle, an energy supply device, and an energy supply system that avoid a situation where two software programs for separately controlling the supply and supplementation of energy do not support each other.

[0007] One aspect of the present invention relates to an electrically-powered vehicle. The electrically-powered vehicle independently supplements energy from each of a plurality of supply devices that supply energy. The electrically-powered vehicle includes a controller. The controller is configured to: hold a plurality of vehicle control software programs associated with at least two control software programs for each of the plurality of supply devices, and when supplementing energy from any one of the plurality of supply devices, select a vehicle control software program associated with the control software program of any one of the supply devices from among the plurality of vehicle control software programs.

[0008] In the above configuration, the controller can be configured to obtain and select vehicle control software associated with the control software of any one of the supply devices from a server capable of communicating with the electric vehicle when the controller does not hold the vehicle control software associated with the control software of any one of the supply devices.

[0009] In the above configuration, the electric vehicle may further include a secondary battery as a power source, and a plurality of supply devices may be configured to supply electric power as energy.

[0010] In the above configuration, the electric vehicle may further include a fuel cell as a power source, the fuel cell may use hydrogen as fuel, and a plurality of supply devices may be configured to supply hydrogen as energy.

[0011] Another aspect of the present invention relates to an energy supply device. The energy supply device supplies energy to a plurality of electric vehicles individually. The energy supply device includes a control unit. The control unit is configured to: hold a plurality of control software of the energy supply device associated with at least two vehicle control software of each of the plurality of electric vehicles, and when supplying energy to any one of the plurality of electric vehicles, select from the plurality of control software the control software associated with the vehicle control software of any one of the electric vehicles.

[0012] In the above configuration, the control unit can be configured to obtain and select from a server capable of communicating with the energy supply device the control software associated with the vehicle control software of any one of the electric vehicles when the control unit does not hold the control software associated with the vehicle control software of any one of the electric vehicles.

[0013] Another aspect of the present invention relates to an energy supply system. The energy supply system includes: a plurality of supply devices configured to supply energy, and electric vehicles configured to independently replenish energy from each of the plurality of supply devices. The electric vehicle includes a controller. The controller is configured to: hold a plurality of vehicle control software associated with at least two control software of each of the plurality of supply devices, and when replenishing energy from any one of the plurality of supply devices, select from the plurality of vehicle control software the vehicle control software associated with the control software of any one of the supply devices.

[0014] In the above configuration, the energy supply system may further include a server capable of communicating with the electric vehicle. The controller can be configured to obtain and select from the server the vehicle control software associated with the control software of any one of the supply devices when the controller does not hold the vehicle control software associated with the control software of any one of the supply devices.

[0015] According to an aspect of the present invention, it is possible to avoid a situation where two software for separately controlling the supply and replenishment of energy do not support each other. Description of the Drawings

[0016] The features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the drawings, in which like reference numerals denote like elements, and in which:

[0017] Figure 1 is a diagram schematically showing the overall configuration of an energy supply system;

[0018] Figure 2 is a diagram showing an example of the configuration of an electric vehicle;

[0019] Figure 3A is an example of a vehicle control software management table for an electric vehicle;

[0020] Figure 3B is an example of a first support table for an electric vehicle;

[0021] Figure 3C is an example of a second support table for an electric vehicle;

[0022] Figure 4 is an example of the hardware configuration of a vehicle management server;

[0023] Figure 5 is an example of the functional configuration of a vehicle management server;

[0024] Figure 6 is an example of a vehicle control software management table for a vehicle management server;

[0025] Figure 7 is an example of the functional configuration of a station management server;

[0026] Figure 8 is an example of a control software management table for a station management server;

[0027] Figure 9A is an example of the configuration of a first charging station;

[0028] Figure 9B is an example of the configuration of a second charging station;

[0029] Figure 10A is an example of a control software management table for a first charging station;

[0030] Figure 10B is an example of a first support table for a first charging station;

[0031] Figure 10C is an example of a second support table for a first charging station;

[0032] Figure 11A is an example of a control software management table for a second charging station;

[0033] Figure 11B is an example of the first support table of the second charging station;

[0034] Figure 11C is an example of the second support table of the second charging station;

[0035] Figure 12 is a processing sequence diagram (part 1) showing an example of the operation of the energy supply system according to the first embodiment;

[0036] Figure 13 is a processing sequence diagram (part 2) showing an example of the operation of the energy supply system according to the first embodiment;

[0037] Figure 14 is a processing sequence diagram (part 1) showing an example of the operation of the energy supply system according to the second embodiment; and

[0038] Figure 15 is a processing sequence diagram (part 2) showing an example of the operation of the energy supply system according to the second embodiment. DETAILED DESCRIPTION

[0039] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[0040] First Embodiment

[0041] The energy supply system ST includes an electric vehicle 100, a management server group 200, and a plurality of charging stations 300. The electric vehicle 100 is not equipped with an engine, but is equipped with a power storage device. The electric vehicle 100 is a power vehicle capable of traveling using a motor with the power stored in the power storage device. The electric vehicle 100 also includes a plug-in electric vehicle (plug-in EV). The electric vehicle 100 may be a hybrid vehicle equipped with an engine in addition to the motor, or may be a fuel cell vehicle equipped with a fuel cell using hydrogen as fuel instead of or in addition to the power storage device. The electric vehicle 100 may be a privately owned vehicle, or may be a company-owned vehicle owned by a company.

[0042] The management server group 200 is installed in a data center DC that provides cloud services. The management server group 200 includes various management servers, such as a vehicle management server 210 and a station management server 220. The charging stations 300 include a first charging station 310 and a second charging station 320. Although not shown in the figure, in addition to the first charging station 310 and the second charging station 320, the charging stations 300 include a plurality of first charging stations and a plurality of second charging stations. Each of the first charging station 310 and the second charging station 320 is an example of a supply device and an energy supply device.

[0043] The vehicle management server 210 and the station management server 220 are connected to each other via a wired communication network such as a Local Area Network (LAN). The vehicle management server 210 and the station management server 220 are connected to the communication network NW. The communication network NW is, for example, the Internet.

[0044] The cellular base station BS is connected to the communication network NW. When the electric vehicle 100 is included in the wireless communication area of the cellular base station BS, the cellular base station BS can communicate with the electric vehicle 100 via the wireless communication WL. The cellular base station BS can also be regarded as being able to communicate with the electric vehicle 100 by using Over-The-Air (OTA) technology. Therefore, the electric vehicle 100 communicates with the vehicle management server 210 and the like via the communication network NW, the cellular base station BS, and the wireless communication WL. For example, a communication standard for wide-area wireless communication such as Long Term Evolution (LTE) is used for the wireless communication WL.

[0045] The first charging station 310 and the second charging station 320 are connected to the communication network NW. The first charging station 310 is, for example, a fast charging station capable of supplying direct current power of several tens of kilowatts to several hundreds of kilowatts. The first charging station 310 is installed in a parking lot of a public facility or a commercial facility, for example. The first charging station 310 is connected to a 200-volt three-phase alternating current power supply 312 via a power system 311 different from the communication system W1.

[0046] On the other hand, the second charging station 320 is, for example, a standard charging station capable of supplying several kilowatts of direct current power. The second charging station 320 is installed in the residential garage of a person who owns the electric vehicle 100 or in the parking lot of a company that owns the electric vehicle 100. The second charging station 320 is connected to a 100-volt or 200-volt single-phase alternating current power supply 322 via a power system 321 different from the communication system W2.

[0047] The first charging station 310 and the second charging station 320 each supply power to the electric vehicle 100 as energy independently of each other. When, for example, the electric vehicle 100 is parked in the parking lot where the first charging station 310 is installed, the first charging station 310 supplies power to the electric vehicle 100. Alternatively, when the electric vehicle 100 is parked in the garage where the second charging station 320 is installed, the second charging station 320 supplies power to the electric vehicle 100. The electric vehicle 100 can be charged using the power independently supplied from each of the first charging station 310 and the second charging station 320.

[0048] A case where the electric vehicle 100 is charged using the power supplied from the first charging station 310 will be specifically described. When power is supplied from the first charging station 310 to the electric vehicle 100, a first connector provided at the distal end of a charging cable extending from the first charging station 310 is connected to a first inlet of the electric vehicle 100. When an instruction to perform external charging is issued in the electric vehicle 100 or the first charging station 310, power is supplied from the first charging station 310 to the electric vehicle 100 through the charging cable. Accordingly, the electric vehicle 100 can be replenished with power and charged from the first charging station 310. The case where power is supplied from the second charging station 320 to the electric vehicle 100 is substantially similar to that of the first charging station 310, and thus a detailed description thereof is omitted.

[0049] The vehicle management server 210 communicates with the electric vehicle 100 via the communication network NW, the cellular base station BS, and the wireless communication WL. The vehicle management server 210 receives various information from the electric vehicle 100, for example. The vehicle management server 210 transmits vehicle control software (specifically, a control program, firmware, etc.) for controlling the electric vehicle 100 to the electric vehicle 100. The vehicle control software includes replenishment control software for controlling operations related to the replenishment of power (i.e., charging).

[0050] The electric vehicle 100 receives a new version of the vehicle control software via the wireless communication WL, and updates the old version of the vehicle control software with the new version of the vehicle control software without deleting and while maintaining the old version of the vehicle control software. When the old version of the vehicle control software is updated with the new version of the vehicle control software, the functions of the old version of the vehicle control software are not exercised and are restricted. The functions of the new version of the vehicle control software are exercised. In this way, each time the electric vehicle 100 receives a new version of the vehicle control software, the electric vehicle 100 accumulates a plurality of different old versions of the vehicle control software and remains up-to-date by maintaining the new version of the vehicle control software.

[0051] On the other hand, the station management server 220 communicates with the first charging station 310 and the second charging station 320 via the communication network NW. The station management server 220 receives various information from the first charging station 310 and the second charging station 320. The station management server 220 transmits control software for controlling the first charging station 310 to the first charging station 310. Similarly, the station management server 220 transmits control software for controlling the second charging station 320 to the second charging station 320. The plurality of control software includes supply control software for controlling operations related to the supply of power.

[0052] Here, the communication between the station management server 220 and the first charging station 310 will be described. The station management server 220 sends the new version control software to the first charging station 310 in response to a periodic request from the first charging station 310 based on, for example, a set date and time. Accordingly, the first charging station 310 receives the new version control software. As in the case of the electric vehicle 100, when the first charging station 310 receives the new version control software, the first charging station 310 updates the old version control software with the new version control software without deleting and while maintaining the old version control software. When updating the old version control software with the new version control software, the functions of the old version control software are not demonstrated and are restricted. Then, the functions of the new version control software are demonstrated. In this way, each time the first charging station 310 receives the new version control software, the first charging station 310 accumulates multiple different old version control softwares and stays up-to-date by maintaining the new version control software.

[0053] Next, the communication between the station management server 220 and the second charging station 320 will be described. When a situation occurs, the station management server 220 sends the new version control software to the second charging station 320 in response to an aperiodic request from the second charging station 320. When, for example, a user using the second charging station 320 manually operates the second charging station 320 to issue an instruction to send the new version control software, the second charging station 320 makes a request for the new version control software to the station management server 220. When the periodic sending of the control software requires high communication costs, some users can set the sending based on manual operation for the second charging station 320 instead of setting dynamic periodic sending.

[0054] When the second charging station 320 makes a request for sending the new version control software, the station management server 220 sends the new version control software to the second charging station 320. Accordingly, the second charging station 320 receives the new version control software. As in the case of the first charging station 310, each time the second charging station 320 receives the new version control software, the second charging station 320 accumulates multiple different old version control softwares and stays up-to-date by maintaining the new version control software. In the case where, for example, the electric vehicle 100 is up-to-date, when the second charging station 320 is up-to-date, the second charging station 320 is compatible with the up-to-date electric vehicle 100, and thus the second charging station 320 can supply power to the electric vehicle 100. In other words, the electric vehicle 100 can replenish power from the second charging station 320. In other words, the electric vehicle 100 can be charged from the second charging station 320.

[0055] On the other hand, there is also a case where the second charging station 320 is not in the latest state due to the user's forgetfulness, incorrect operation, etc. Although described in detail later, in this case, the electric vehicle 100 selects any one of the old version vehicle control software that is compatible with the control software of the second charging station 320 from among multiple old version vehicle control software to ensure compatibility with the second charging station 320 that is not in the latest state. Therefore, even when the second charging station 320 is not in the latest state, the control software of the second charging station 320 is compatible with the vehicle control software of the electric vehicle 100. Therefore, the second charging station 320 can supply power to the electric vehicle 100, and the electric vehicle 100 can replenish power from the second charging station 320.

[0056] Having compatibility means that there is a support relationship between multiple software, and not having compatibility means that there is no support relationship between multiple software. For compatibility related to charging, when there is a support relationship between the control software and the vehicle control software, the output control, input control, and communication of power operate normally. Therefore, for example, the electric vehicle 100 can be charged at the fastest charging rate. The charging completion time until charging is completed can be calculated with high precision. In addition, the screen guidance of the electric vehicle 100, the first charging station 310, or the second charging station 320 that issues an external charging instruction can be displayed normally. Therefore, when there is no support relationship between the control software and the vehicle control software, for example, the charging rate may decrease, the accuracy of calculating the charging completion time may decrease, and the accuracy of displaying the screen guidance (e.g., image quality, etc.) may decrease.

[0057] Reference will be made to Figure 2Describe the configuration of the electric vehicle 100. The electric vehicle 100 includes a power storage device 110, a system main relay SMR, and a power control unit (PCU) 120. The electric vehicle 100 includes a motor generator (MG) 130, a power transmission gear 135, drive wheels 140, a first inlet 150, a second inlet 152, and a charging relay RY. The electric vehicle 100 includes an electronic control unit (ECU) 160, a data communication module (DCM) 170, a global positioning system (GPS) receiver 172, and a controller area network (CAN) communication unit 174. The ECU 160 includes a central processing unit (CPU), a random access memory (RAM), a read only memory (ROM), an input and output interface (I / F), and a non-volatile memory (NVM) 161.

[0058] The power storage device 110 is a power storage element configured to be rechargeable and dischargeable. The power storage device 110 is, for example, a secondary battery such as a lithium ion battery and a nickel metal hydride battery, a power storage element such as an electric double layer capacitor, etc. A lithium ion battery is a secondary battery that uses lithium as a carrier. The lithium ion battery can be a lithium ion battery with a liquid electrolyte or a all-solid-state battery with a solid electrolyte.

[0059] The power storage device 110 is charged by a first charging station 310 located outside the vehicle and connected to the first inlet 150 through a charging cable (external charging). The power storage device 110 can be charged by a second charging station 320 located outside the vehicle and connected to the second inlet 152 (see Figure 1 ) through a charging cable (external charging). The power storage device 110 supplies power to the MG 130 through the PCU 120 during driving. The power storage device 110 is charged using the power generated by the MG 130 through the PCU 120 during regenerative power generation of the MG 130 during vehicle braking.

[0060] The system main relay SMR is provided between the PCU 120 and a pair of power lines PL1 and NL1 connected to the power storage device 110. When the vehicle system is started by a start switch (not shown) or the like, the system main relay SMR is turned on by the ECU 160.

[0061] The PCU 120 is a drive unit that drives the MG 130 and is composed of a power conversion device such as a converter and an inverter. The PCU 120 is controlled by the ECU 160 and converts the DC power supplied from the power storage device 110 into AC power for driving the MG 130. The PCU 120 converts the AC power generated by the MG 130 into DC power and outputs the DC power to the power storage device 110.

[0062] The MG 130 is an AC rotating electric machine and is, for example, a three-phase AC synchronous motor in which permanent magnets are embedded in the rotor. The MG 130 is driven by the PCU 120 to generate a rotational driving force, and the driving force generated by the MG 130 is transmitted to the drive wheels 140 through the power transmission device 135. On the other hand, for example, during vehicle braking, the MG 130 operates as a generator and performs regenerative power generation. The power generated by the MG 130 is supplied to the power storage device 110 through the PCU 120.

[0063] The charging relay RY is provided between a pair of power lines DCL1 and DCL2 connected to the first inlet 150 and the second inlet 152 and a pair of power lines PL2 and NL2 connected to the pair of power lines PL1 and NL1. When performing external charging, the charging relay RY is turned on by the ECU 160.

[0064] The first inlet 150 receives power supplied from the first charging station 310 during external charging. During external charging, the first connector of the first charging station 310 is connected to the first inlet 150, and the DC power output from the first charging station 310 is supplied to the power storage device 110 through the first inlet 150, a pair of power lines DCL1, DCL2, the charging relay RY, a pair of power lines PL2, NL2, and a pair of power lines PL1, NL1.

[0065] The second inlet 152 receives power supplied from the second charging station 320 (see Figure 1 ) during external charging. During external charging, the second connector of the second charging station 320 is connected to the second inlet 152, and the DC power output from the second charging station 320 is supplied to the power storage device 110 through the second inlet 152, a pair of power lines DCL1, DCL2, the charging relay RY, a pair of power lines PL2, NL2, and a pair of power lines PL1, NL1.

[0066] The DCM 170 is for communicating with the vehicle management server 210 (seeFigure 1 ) The in-vehicle communication device for communication. The DCM 170 can perform two-way communication between the electric vehicle 100 (specifically, the ECU 160) and the vehicle management server 210 via the wireless communication WL, the cellular base station BS, and the communication network NW. The GPS receiver 172 determines the current position based on the radio waves from artificial satellites and outputs the determined position information to the ECU 160. The position information determined by the GPS receiver 172 is used for, for example, a navigation system (not shown).

[0067] The navigation system includes map information. The map information includes the position information of various facilities where the first charging station 310 is installed and the position information of the place where the second charging station 320 is installed. Therefore, the electric vehicle 100 can identify the model IDs of the multiple charging stations 300 based on the position information about the current position of the electric vehicle 100 and the position information about the facilities and the like. For example, when the first charging station 310 is included in the close-in range of the electric vehicle 100, the model ID indicating a quick charger can be identified. When the second charging station 320 is included in the close-in range of the electric vehicle 100, the model ID indicating a standard charger can be identified.

[0068] The CAN communication unit 174 performs CAN communication between the electric vehicle 100 (specifically, the ECU 160) and the first charging station 310 or the second charging station 320 during external charging. In this embodiment, an example of DC charging according to the CHAdeMO (registered trademark) mode is described, and the communication between the electric vehicle 100 and the first charging station 310 is also performed according to the CAN communication protocol adopted in CHAdeMO.

[0069] The charging mode that can be adopted in the electric vehicle 100 according to this embodiment is not limited to the CHAdeMO mode, and for example, the combined charging system (combo) mode mainly standardized in Europe and the United States can also be adopted. In addition, the communication between the electric vehicle 100 and the first charging station 310 or the second charging station 320 is not limited to the CAN communication adopted in the CHAdeMO mode, and can be performed via power line communication (PLC) or near-field communication.

[0070] While the electric vehicle 100 is in motion, the ECU 160 controls the driving of the MG 130 and the charging and discharging of the power storage device 110 by turning on the system main relay SMR and controlling the PCU 120. During external charging, the ECU 160 executes external charging by turning on the charging relay RY and sending a charging start request, a charging current command value, etc. to the first charging station 310 or the second charging station 320 through the CAN communication unit 174. The ECU 160 calculates the state of charge (SOC) of the power storage device 110. When the SOC reaches a predetermined upper limit value, the ECU 160 sends a charging stop request to the first charging station 310 or the second charging station 320 through the CAN communication unit 174 and turns off the charging relay RY. As for the method of calculating the SOC, various known methods can be used, such as the method using the OCV-SOC curve (map, etc.) representing the relationship between the open circuit voltage (OCV) and the SOC, the method using the integrated value of the charging and discharging current, and the method of remaining capacity / full charge capacity × 100.

[0071] The charging cable of the first charging station 310 has a first connector that can be connected to the first inlet 150 of the electric vehicle 100. In a state where the first connector is connected to the first inlet 150, DC power can be supplied from the first charging station 310 to the electric vehicle 100, and CAN communication can be performed between the first charging station 310 and the electric vehicle 100. The second charging station 320 is basically similar to the first charging station 310, so a detailed description is omitted.

[0072] In a state where the first connector of the first charging station 310 is connected to the first inlet 150, the data sent from the electric vehicle 100 to the first charging station 310 includes various charging data, for example, a charging start request, a charging stop request, a charging current command value, and a charging voltage upper limit. On the other hand, the data to be sent from the first charging station 310 to the electric vehicle 100 includes various output data, for example, maximum output information (such as available current value and available voltage value) and current output information (such as current output current value and current output voltage value). The second charging station 320 is basically similar to the first charging station 310.

[0073] Reference will be made to Figures 3A to 3C describe the details of the NVM 161. Initially, the NVM 161 stores the vehicle control software in the vehicle control software management table of the electric vehicle 100. Specifically, as Figure 3AAs shown, the NVM 161 stores the vehicle model ID, vehicle control software, version, release date, etc. in association with each other. The vehicle model ID is an identifier for identifying the model of the electric vehicle 100. Examples of the models of the electric vehicle 100 include plug-in EVs and hybrid vehicles. The version and release date are the version and available date of the vehicle control software, respectively. In the first embodiment, each of the version "V1" and version "V2" corresponds to an old version of the vehicle control software in the electric vehicle 100, and the version "V3" corresponds to a new version of the vehicle control software in the electric vehicle 100.

[0074] The NVM 161 stores compatibility data regarding the compatibility between the electric vehicle 100 and each of the first charging station 310 and the second charging station 320. Specifically, as Figure 3B and Figure 3C shown, the NVM 161 manages the compatibility data by using a first support table of the electric vehicle 100 and a plurality of second support tables. For example, before the NVM 161 stores the vehicle control software, this compatibility data is pre-stored in the NVM 161.

[0075] As Figure 3B shown, the first support table manages multiple combinations of the station model ID and the vehicle model ID as compatibility data. The station model ID is an identifier for identifying the model of the charging station 300. In the first embodiment, the station model ID "S1" is assigned to the first charging station 310, and the station model ID "S2" is assigned to the second charging station 320. The station model ID "S1" corresponds to a fast charger, and the station model ID "S2" corresponds to a standard charger. The combination of the station model ID and the vehicle model ID is uniquely identified by using the first support table.

[0076] As Figure 3C shown, each second support table manages the compatibility between the version of the control software of the first charging station 310 or the second charging station 320 assigned with the station model ID and the version of the vehicle control software of the electric vehicle 100 assigned with the vehicle model ID, as the compatibility data for each combination of the station model ID and the vehicle model ID. The compatibility "Yes" indicates that there is compatibility between the control software and the vehicle control software. The compatibility "No" indicates that there is no compatibility between the control software and the vehicle control software. Therefore, in Figure 3C , it indicates that there is no compatibility between the version "V2" of the control software of the second charging station 320 assigned with the station model ID "S2" and the versions "V1" and "V3" of the vehicle control software of the electric vehicle 100 assigned with the vehicle model ID "E1". By using the second support table, the compatibility between the version of the control software and the version of the vehicle control software can be uniquely identified.

[0077] will refer to Figure 4 Describe the hardware configuration of the vehicle management server 210. The station management server 220 basically has a hardware configuration similar to that of the vehicle management server 210, so its description is omitted. As Figure 4 shown, the vehicle management server 210 includes a CPU 210A serving as a processor, a RAM 210B and a ROM 210C serving as memories, and a network I / F 210D. When necessary, the vehicle management server 210 may include at least one of a hard disk drive (HDD) 210E, an input I / F 210F, an output I / F 210G, an input and output I / F 210H, and a drive device 210I. The CPU 210A, the RAM 210B, the ROM 210C, the network I / F 210D, the HDD 210E, the input I / F 210F, the output I / F 210G, the input and output I / F 210H, and the drive device 210I are connected to each other through an internal bus 210J.

[0078] An input device 710 is connected to the input I / F 210F. A keyboard or a mouse (not shown) is an example of the input device 710. A display device 720 is connected to the output I / F 210G. A liquid crystal display is an example of the display device 720. A semiconductor memory 730 is connected to the input and output I / F 210H. For example, a universal serial bus (USB) drive, a flash memory, etc. are examples of the semiconductor memory 730. The input and output I / F 210H reads out a program or data stored in the semiconductor memory 730. For example, each of the input I / F 210F and the input and output I / F 210H includes a USB port. The output I / F 210G includes, for example, a display port.

[0079] A portable recording medium 740 is inserted into the drive device 210I. For example, removable disks such as a compact disc (CD)-ROM and a digital versatile disc (DVD) are examples of the portable recording medium 740. The drive device 210I reads out a program or data stored in the portable recording medium 740. The network I / F 210D includes, for example, a LAN port. The network I / F 210D is connected to a communication network NW.

[0080] The programs stored in the ROM 210C or the HDD 210E are temporarily stored in the RAM 210B by the CPU 210A. The programs recorded on the portable recording medium 740 are temporarily stored in the RAM 210B by the CPU 210A. When the CPU 210A runs the stored programs, the CPU 210A implements various functions (described later) and executes various processes (described later). The programs only need to follow the process sequence diagram (described later).

[0081] Reference will be made to Figure 5 and Figure 6 describe the functional configuration of the vehicle management server 210. Figure 5 Show the main part of the functions of the vehicle management server 210.

[0082] As Figure 5 shown, the vehicle management server 210 includes a storage unit 211, a processing unit 212, an input unit 213, and a communication unit 214. The storage unit 211 is implemented by the RAM 210B, the HDD 210E, etc. The processing unit 212 is implemented by the CPU 210A. The input unit 213 is implemented by the input I / F 210F. The communication unit 214 is implemented by the network I / F 210D. Therefore, the storage unit 211, the processing unit 212, the input unit 213, and the communication unit 214 are connected to each other.

[0083] The storage unit 211 includes a vehicle control software (hereinafter referred to as SW) storage unit 215. The vehicle control SW storage unit 215 may be provided in another management server different from the vehicle management server 210. In this case, the vehicle management server 210 can access the other management server and refer to the details stored in the vehicle control SW storage unit 215.

[0084] The vehicle control SW storage unit 215 stores the vehicle control software in the vehicle control software management table of the vehicle management server 210. Specifically, as Figure 6 shown, the vehicle control SW storage unit 215 stores the vehicle model ID, the vehicle control software, the version, the release date, etc. in association with each other. Different from the vehicle control software management table of the electric vehicle 100, the vehicle control SW storage unit 215 stores the version "V4" of the vehicle control software "E1 control program" as the new version of the vehicle control software. In this way, depending on the moment when the vehicle management server 210 sends the vehicle control software to the electric vehicle 100, the vehicle control software management table of the electric vehicle 100 may be different from the vehicle control software management table of the vehicle management server 210.

[0085] The processing unit 212 includes a vehicle control SW management unit 217. The vehicle control SW management unit 217 accesses the vehicle control SW storage unit 215 and performs various processes. For example, when multiple vehicle control softwares are requested from the electric vehicle 100, the vehicle control SW management unit 217 sends the multiple vehicle control softwares to the electric vehicle 100. Details of the vehicle control SW management unit 217 will be described when the operation of the energy supply system ST is described.

[0086] Reference will be made to Figure 7 and Figure 8 describe the functional configuration of the station management server 220. Figure 7 Show the main part of the functions of the station management server 220.

[0087] As Figure 7 shown, the station management server 220 includes a storage unit 221, a processing unit 222, an input unit 223, and a communication unit 224. The storage unit 221 is implemented by the RAM 210B, HDD 210E, etc. The processing unit 222 is implemented by the CPU 210A. The input unit 223 is implemented by the input I / F 210F. The communication unit 224 is implemented by the network I / F 210D. Therefore, the storage unit 221, the processing unit 222, the input unit 223, and the communication unit 224 are connected to each other.

[0088] The storage unit 221 includes a station control SW storage unit 225. The station control SW storage unit 225 may be provided in another management server different from the station management server 220. In this case, the station management server 220 can access the other management server and refer to the details stored in the station control SW storage unit 225.

[0089] The station control SW storage unit 225 stores the control software for controlling the charging station 300 in the control software management table of the station management server 220. Specifically, as Figure 8 shown, the station control SW storage unit 225 stores the station model ID, control software, version, release date, etc. in association with each other. As in the case of the vehicle control software, each of the version "V1", version "V2", and version "V3" corresponds to an old version of the control software, and the version "V4" corresponds to a new version of the control software.

[0090] The processing unit 222 includes a station control SW management unit 227. The station control SW management unit 227 accesses the station control SW storage unit 225 and performs various processes. For example, when a plurality of control softwares are requested from the first charging station 310 to the station control SW management unit 227, the station control SW management unit 227 sends the plurality of control softwares associated with the station model ID of the first charging station 310 to the first charging station 310. When a plurality of control softwares are requested from the second charging station 320 to the station control SW management unit 227, the station control SW management unit 227 sends the plurality of control softwares associated with the station model ID of the second charging station 320 to the second charging station 320. Details of the station control SW management unit 227 will be described when the operation of the energy supply system ST is described.

[0091] Reference will be made to Figure 9A Describe the configuration of the first charging station 310. The first charging station 310 includes an AC-DC converter 315, a high-frequency inverter 316, a step-up transformer 317, a rectifier 318, and a first charging controller 319. The first charging controller 319 includes a CPU, a RAM, a ROM, an input and output I / F, and an NVM 319m. A three-phase AC power supply 312 is connected to the AC-DC converter 315 via a power system 311. One end of a pair of first power lines 313 is connected to the rectifier 318. One end of a first communication line 314 is connected to the first charging controller 319. A first connector C1 is connected to the other ends of the pair of first power lines 313 and the first communication line 314. The first connector C1 can be connected to the first inlet 150 of the electric vehicle 100. The pair of first power lines 313 and the first communication line 314 are part of a charging cable extending from the first charging station 310 and are included in the charging cable.

[0092] The AC-DC converter 315 receives the power supplied from the three-phase AC power supply 312 and converts the AC power into DC power. The high-frequency inverter 316 converts the DC power into high-frequency (rectangular wave) AC power to improve the step-up efficiency. The step-up transformer 317 steps up the high-frequency AC power. The rectifier 318 rectifies and smoothes the step-up AC power boosted from the high-frequency AC power, and outputs DC power via the first connector C1. The first charging controller 319 controls the operations of the AC-DC converter 315 and the high-frequency inverter 316 while exchanging information such as the current SOC of the power storage device 110 with the ECU 160 of the electric vehicle 100 (see Figure 2 )

[0093] Reference will be made to Figure 9BDescribe the configuration of the second charging station 320. The second charging station 320 includes a first filter 325, an AC-DC converter 326, a DC-DC converter 327, a second filter 328, and a second charging controller 329. The second charging controller 329 includes a CPU, a RAM, a ROM, an input and output I / F, and an NVM 329m. A single-phase AC power supply 322 is connected to the first filter 325 via a power system 321. One end of a pair of second power lines 323 is connected to the second filter 328. One end of a second communication line 324 is connected to the second charging controller 329. A second connector C2 is connected to the other ends of the pair of second power lines 323 and the second communication line 324. The second connector C2 can be connected to a second inlet 152 of the electric vehicle 100. The pair of second power lines 323 and the second communication line 324 are part of a charging cable extending from the second charging station 320 and are included in the charging cable.

[0094] The first filter 325 suppresses the inflow of noise from the single-phase AC power supply 322 and the outflow of noise to the single-phase AC power supply 322 while receiving the power supplied from the single-phase AC power supply 322. The AC-DC converter 326 converts the AC power received by the first filter 325 into DC power. The DC-DC converter 327 converts the DC power output from the AC-DC converter 326 into DC power with a different voltage. The second filter 328 smoothes the DC power and outputs the DC power via the second connector C2. The second charging controller 329 controls the operations of the AC-DC converter 326 and the DC-DC converter 327 while exchanging information such as the current SOC of the power storage device 110 with the ECU 160 of the electric vehicle 100 (see Figure 2 ).

[0095] Reference will be made to Figures 10A to 10C Describe the details of the NVM 319m included in the first charging controller 319. Initially, the NVM 319m stores the control software in the control software management table of the first charging station 310. Specifically, as Figure 10A shown, the NVM 319m stores the station model ID, control software, version, release date, etc. in association with each other.

[0096] The NVM 319m stores compatibility data regarding the compatibility between the electric vehicle 100 and the first charging station 310. Specifically, as Figure 10B and Figure 10C shown, the NVM 319m manages the compatibility data by using the first support table of the first charging station 310 and multiple second support tables. For example, before the NVM 319m stores the control software, this compatibility data is pre-stored in the NVM 319m.

[0097] As Figure 10B shown, a plurality of combinations of the first support table management station model ID and the vehicle model ID are used as compatibility data. The combination of the station model ID and the vehicle model ID is uniquely identified by using the first support table. As Figure 10C shown, each second support table manages the compatibility between the version of the control software of the first charging station 310 assigned with the station model ID and the version of the vehicle control software of the electric vehicle 100 assigned with the vehicle model ID, as the compatibility data for each combination of the station model ID and the vehicle model ID. By using the second support table, the compatibility between the version of the control software and the version of the vehicle control software can be uniquely identified.

[0098] Reference will be made to Figures 11A to 11C to describe the details of the NVM 329m included in the second charging controller 329. Initially, the NVM 329m stores the control software in the control software management table of the second charging station 320. Specifically, as Figure 11A shown, the NVM 329m stores the station model ID, the control software, the version, the release date, etc. in association with each other.

[0099] The NVM 329m stores the compatibility data regarding the compatibility between the electric vehicle 100 and the second charging station 320. Specifically, as Figure 11B and Figure 11C shown, the NVM 329m manages the compatibility data by using the first support table of the second charging station 320 and a plurality of second support tables. For example, before the NVM 329m stores the control software, this compatibility data is pre-stored in the NVM 329m.

[0100] As Figure 11B shown, a plurality of combinations of the first support table management station model ID and the vehicle model ID are used as compatibility data. The combination of the station model ID and the vehicle model ID is uniquely identified by using the first support table. As Figure 11C shown, each second support table manages the compatibility between the version of the control software of the second charging station 320 assigned with the station model ID and the version of the vehicle control software of the electric vehicle 100 assigned with the vehicle model ID, as the compatibility data for each combination of the station model ID and the vehicle model ID. By using the second support table, the compatibility between the version of the control software and the version of the vehicle control software can be uniquely identified.

[0101] Reference will be made to Figure 12 and Figure 13 to describe the operation of the energy supply system ST according to the first embodiment. In Figure 12 and Figure 13 , the continuity of the processing is represented by characters such as "A" and "B".

[0102] Initially, as Figure 12 shown, the ECU 160 of the electric vehicle 100 requests multiple vehicle control softwares from the vehicle management server 210 (step S1). The ECU 160 does not need to request multiple vehicle control softwares in a unified manner, but can request each vehicle control software among the multiple vehicle control softwares individually. For example, the ECU 160 requests multiple vehicle control softwares by sending information including the vehicle model ID and release date assigned to itself or the DCM 170 as the first transmission target condition to the vehicle management server 210. In this embodiment, the ECU 160 sends information including the vehicle model ID "E1" and the release date from "January 8, 2020" to "November 8, 2020" as the first transmission target condition.

[0103] When the vehicle control SW management unit 217 of the vehicle management server 210 is requested for multiple vehicle control softwares, the vehicle control SW management unit 217 sends the multiple vehicle control softwares to the electric vehicle 100 (step S2). When the above first transmission target condition is sent, the vehicle control SW management unit 217 accesses the vehicle control SW storage unit 215 and extracts the vehicle control softwares that meet the first transmission target condition from the vehicle control software management table of the vehicle management server 210 (see Figure 6 ). In this embodiment, the vehicle control SW management unit 217 extracts the vehicle control softwares of version "V1", version "V2", and version "V3" of the vehicle model ID "E1". The vehicle control SW management unit 217 sends the extracted vehicle control softwares to the electric vehicle 100.

[0104] When multiple vehicle control softwares are sent, the ECU 160 receives the multiple vehicle control softwares (step S3). When the ECU 160 receives the multiple vehicle control softwares, the ECU 160 stores and holds the multiple vehicle control softwares in the NVM 161 (step S4). Therefore, the NVM 161 stores multiple vehicle control softwares (see Figure 3A ). The NVM 161 can pre-store multiple vehicle control softwares without the ECU 160 performing the processes of step S1 and step S3.

[0105] After the ECU 160 stores and holds a plurality of vehicle control softwares, the electric vehicle 100 replenishes power from either the first charging station 310 or the second charging station 320. When the ECU 160 replenishes power, the ECU 160 checks the station model ID of the first charging station 310 or the second charging station 320 (step S5). For example, when the electric vehicle 100 is parked in a parking lot of a facility where the first charging station 310 is installed, the ECU 160 checks the station model ID of the first charging station 310 through wired communication via a charging cable. When the electric vehicle 100 is parked in a parking lot of a place where the second charging station 320 is installed, the ECU 160 checks the station model ID of the second charging station 320 through wired communication via a charging cable.

[0106] When the first charging controller 319 of the first charging station 310 is requested by the electric vehicle 100 to check the station model ID, the first charging controller 319 provides the electric vehicle 100 with a notification regarding the station model ID and the version of the control software (step S6). For example, the first charging controller 319 identifies the latest control software among a plurality of control softwares stored in the first charging controller 319 (more specifically, the NVM 319m), and provides a notification regarding the version of the identified control software together with the station model ID of the first charging controller 319. In the present embodiment, the first charging controller 319 provides a notification regarding the version "V2" of the control software together with the station model ID "S1" (see Figure 10A ).

[0107] On the other hand, when the second charging controller 329 of the second charging station 320 is requested by the electric vehicle 100 to check the station model ID, the second charging controller 329 provides the electric vehicle 100 with a notification regarding the station model ID and the version of the control software (step S7). For example, the second charging controller 329 identifies the latest control software among a plurality of control softwares stored in the second charging controller 329 (more specifically, the NVM329m), and provides a notification regarding the version of the identified control software together with the station model ID of the second charging controller 329. In the present embodiment, the second charging controller 329 provides a notification regarding the version "V2" of the control software together with the station model ID "S2" (see Figure 11A ).

[0108] The ECU 160 can check the model ID by using the distance on the map information based on the position information related to the current position of the electric vehicle 100 identified by the GPS receiver 172 and the position information related to the first charging station 310 or the second charging station 320. For example, when the second charging station 320 exists within a short distance range of the electric vehicle 100, the ECU 160 can check the model ID "S2".

[0109] When a notification regarding the station model ID and the version of the control software is provided, the ECU 160 determines whether there is vehicle control software associated with the first charging station 310 or the second charging station 320 (step S8), as Figure 12 shown. For example, when a notification of the version "V2" of the control software together with the station model ID "S2" is provided from the second charging station 320, the ECU 160 identifies the combination of the vehicle model ID "E1" and the station model ID "S2" based on the first support table of the electric vehicle 100 (see Figure 3B ). When the ECU 160 identifies this combination, the ECU 160 identifies the second management slip associated with the identified combination and checks the vehicle control software that is compatible with the version "V2" of the control software associated with the station model ID "S2" (see Figure 3C ). In other words, the ECU 160 checks the version of the vehicle control software associated with "Yes" in terms of compatibility based on the identified second management slip. In the present embodiment, "No" in terms of compatibility is associated with the versions "V1" and "V3" of the vehicle control software. On the other hand, "Yes" in terms of compatibility is associated with the version "V2" of the vehicle control software, and the NVM 161 stores the vehicle control software of the version "V2". Therefore, the ECU 160 determines that there is associated vehicle control software (step S8 is Yes).

[0110] When there is associated vehicle control software, the ECU 160 skips the processing of steps S9, S10, and S12 (described later) and selects the associated vehicle control software (step S13). In the present embodiment, the ECU 160 switches from the vehicle control software of the latest version "V3" to the vehicle control software of the version "V2" and selects this vehicle control software. Therefore, the vehicle control software of the electric vehicle 100 can ensure compatibility with the control software of the version "V2" of the second charging station 320.

[0111] On the other hand, when there is no associated vehicle control software in the processing of step S8 (No in step S8), the ECU 160 accesses the vehicle management server 210 and determines whether it is possible to obtain the associated vehicle control software from the vehicle management server 210 (step S9). For example, when in Figure 3C "No" in terms of compatibility is associated with the versions "V1", "V2", and "V3" of the vehicle model ID "E1" associated with the version "V2" of the station model ID "S2", and "Yes" in terms of compatibility is associated with the version "V4" (not shown), the NVM 161 may not store the vehicle control software of the version "V4". In this case, the ECU 160 determines that there is no associated vehicle control software and determines whether it is possible to obtain the associated vehicle control software from the vehicle management server 210.

[0112] When the vehicle management server 210 can obtain the associated vehicle control software because it has the associated vehicle control software (Yes in step S9), the ECU 160 requests the associated vehicle control software from the vehicle management server 210 (step S10). In the present embodiment, since the vehicle control SW storage unit 215 stores the vehicle model ID "E1" and the version "V4" (see Figure 6 ), the ECU 160 requests the associated vehicle control software from the vehicle management server 210.

[0113] When the associated vehicle control software is requested, the vehicle control SW management unit 217 sends the associated vehicle control software to the electric vehicle 100 (step S11). When the associated vehicle control software is sent, the ECU 160 receives and obtains the associated vehicle control software (step S12). When the ECU 160 obtains the associated vehicle control software, the ECU 160 stores and holds the associated vehicle control software in the NVM 161.

[0114] When the associated vehicle control software is held, in the process of step S13, the ECU 160 selects the associated vehicle control software. In other words, the ECU 160 switches from the vehicle control software of the latest version "V3" to the vehicle control software of the version "V4" and selects this vehicle control software. As described above, when the compatibility "Yes" is associated with the version "V4" of the vehicle model ID "E1" associated with the version "V2" of the station model ID "S2", the vehicle control software of the electric vehicle 100 can ensure compatibility with the control software of the version "V2" of the second charging station 320 by the ECU 160 selecting the vehicle control software of the version "V4".

[0115] When the vehicle management server 210 cannot obtain the associated vehicle control software because it does not have the associated vehicle control software (No in step S9), in the process of step S13, the ECU 160 selects the vehicle control software with a high possibility of charging. For example, when in Figure 3C the compatibility "No" is associated with the versions "V1", "V2", "V3", and "V4" (not shown) of the vehicle model ID "E1" associated with the version "V2" of the station model ID "S2", regardless of the station model ID "S2", the ECU 160 selects any version of the vehicle control software of the vehicle model ID "E1" associated with the compatibility "Yes". For example, in Figure 3CAmong them, the ECU 160 selects the vehicle control software of version "V1" of vehicle model ID "E1" associated with version "V1" of station model ID "S2". The NVM 161 stores the vehicle control software of version "V1" (see Figure 3A ), so the ECU 160 can select the vehicle control software.

[0116] As an example, the case where the notice of version "V2" of the control software together with the station model ID "S2" is provided from the second charging station 320 has been described. The case where the notice of version "V2" of the control software together with the station model ID "S1" is provided from the first charging station 310 is basically similar to that of the second charging station 320, so its description is omitted.

[0117] When the vehicle control software is selected in the process of step S13, the ECU 160 sends charging data such as a charging start request to the first charging station 310 or the second charging station 320 (step S14). When the electric vehicle 100 is parked in the parking lot of the facility where the first charging station 310 is installed, the ECU 160 sends the charging data to the first charging station 310 via the charging cable through wired communication. When the electric vehicle 100 is parked in the parking lot of the place where the second charging station 320 is installed, the ECU 160 sends the charging data to the second charging station 320 via the charging cable through wired communication.

[0118] When the charging data is sent to the first charging station 310, the first charging controller 319 receives the charging data (step S15). When the charging data is sent to the second charging station 320, the second charging controller 329 receives the charging data (step S16). When the first charging controller 319 receives the charging data, the first charging controller 319 sends output data such as maximum output information to the electric vehicle 100 (step S17). When the second charging controller 329 receives the charging data, output data is sent to the electric vehicle 100 (step S18).

[0119] When the output data is sent from the first charging station 310 or the second charging station 320, the ECU 160 receives the output data sent from the first charging station 310 or the second charging station 320 (step S19). When the ECU 160 receives the output data, the supply of power from the first charging station 310 or the second charging station 320 to the electric vehicle 100 starts. In other words, the charging of the electric vehicle 100 starts. Through the process of step S13, the ECU 160 selects the vehicle control software that is compatible with the control software of the first charging station 310 or the second charging station 320, so the situation where the control software and the vehicle control software do not support each other can be avoided.

[0120] Second Embodiment

[0121] Reference will be made to Figure 14 and Figure 15 to describe the operation of the energy supply system ST according to the second embodiment. In Figure 14 and Figure 15 , the continuation of processing is represented by characters such as the character "P" and the character "Q".

[0122] Initially, as Figure 14 shown, the first charging controller 319 of the first charging station 310 requests a plurality of control softwares from the station management server 220 (step S31). The second charging controller 329 of the second charging station 320 requests a plurality of control softwares from the station management server 220 (step S32). Each of the first charging controller 319 and the second charging controller 329 can make requests individually, rather than making a unified request for a plurality of control softwares.

[0123] For example, the first charging controller 319 requests a plurality of control softwares by sending information including the station model ID and release date assigned to the first charging controller 319 to the station management server 220 as the second transmission target condition. In the present embodiment, the first charging controller 319 sends information including the station model ID "S1" and the release date from "January 8, 2020" to "November 8, 2020" as the second transmission target condition. The second charging controller 329 is similar to the case of the first charging controller 319, and thus the description thereof is omitted.

[0124] When the station control SW management unit 227 of the station management server 220 is requested a plurality of control softwares, the station control SW management unit 227 sends a plurality of control softwares (step S33). When the second transmission target condition is sent from the first charging station 310, the station control SW management unit 227 accesses the station control SW storage unit 225 and extracts the control softwares that satisfy the second transmission target condition from the control software management table (see Figure 8 ) of the station management server 220. In the present embodiment, the station control SW management unit 227 extracts the control softwares of version "V1", version "V2", and version "V3" of the station model ID "S1". The station control SW management unit 227 sends the extracted plurality of control softwares to the first charging station 310. When the second transmission target condition is sent from the second charging station 320, as in the case where the second transmission target condition is sent from the first charging station 310, the station control SW management unit 227 sends the extracted plurality of control softwares to the second charging station 320.

[0125] When multiple control softwares are sent to the first charging station 310, the first charging controller 319 receives the multiple control softwares (step S34). When multiple control softwares are sent to the second charging station 320, the second charging controller 329 receives the multiple control softwares (step S35). When the first charging controller 319 receives the multiple control softwares, the first charging controller 319 stores and holds the multiple control softwares in the NVM 319m (step S36). Accordingly, the NVM 319m stores the multiple control softwares (see Figure 10A ).

[0126] When the second charging controller 329 receives the multiple control softwares, the second charging controller 329 stores and holds the multiple control softwares in the NVM 329m (step S37). Accordingly, the NVM 329m stores the multiple control softwares (see Figure 11A ). Alternatively, the NVM 319m may pre-store the multiple control softwares without the first charging controller 319 performing the processes of step S31 and step S34. The NVM 329m may pre-store the multiple control softwares without the second charging controller 329 performing the processes of step S32 and step S35.

[0127] After the first charging controller 319 and the second charging controller 329 store and hold the multiple control softwares, the first charging station 310 and the second charging station 320 supply power to the electric vehicle 100 independently of each other. When the first charging controller 319 supplies power, the first charging controller 319 checks the vehicle model ID of the electric vehicle 100 (step S38). When the second charging controller 329 supplies power, the second charging controller 329 checks the vehicle model ID of the electric vehicle 100 (step S39). For example, when the electric vehicle 100 is parked in the parking lot of the facility where the first charging station 310 is installed, the first charging controller 319 checks the vehicle model ID of the electric vehicle 100 through wired communication via the charging cable. When the electric vehicle 100 is parked in the parking lot of the place where the second charging station 320 is installed, the second charging controller 329 checks the vehicle model ID of the electric vehicle 100 through wired communication via the charging cable.

[0128] When the electric vehicle 100 is requested to check the vehicle model ID, the ECU 160 provides a notice regarding the vehicle model ID and the version of the control software (step S40). When, for example, the electric vehicle 100 is requested by the first charging controller 319 to check the vehicle model ID, the ECU 160 identifies the latest vehicle control software from among a plurality of vehicle control softwares stored in the ECU 160 (more specifically, the NVM 161). The ECU 160 provides a notice regarding the version of the identified vehicle control software together with the vehicle model ID of the electric vehicle 100 to the first charging station 310. In the present embodiment, the ECU 160 provides a notice regarding the version "V3" of the control software together with the vehicle model ID "E1" (see Figure 3A ). When the electric vehicle 100 is requested by the second charging controller 329 to check the vehicle model ID, as in the case where the electric vehicle 100 is requested by the first charging controller 319 to check the vehicle model ID, the ECU 160 provides a notice regarding the version of the vehicle control software together with the vehicle model ID of the electric vehicle 100 to the second charging station 320.

[0129] When providing the notice regarding the vehicle model ID and the version of the vehicle control software to the first charging station 310, as Figure 15 shown, the first charging controller 319 determines whether there is control software associated with the electric vehicle 100 (step S41). For example, when a notice regarding the version "V3" of the vehicle control software together with the vehicle model ID "E1" is provided from the electric vehicle 100, the first charging controller 319 identifies the combination of the station model ID "S1" and the vehicle model ID "E1" based on the first support table of the first charging controller 319 (see Figure 10B ). When the first charging controller 319 identifies this combination, the first charging controller 319 identifies the second management unit associated with the identified combination, and checks the control software that is compatible with the version "V3" of the vehicle control software associated with the vehicle model ID "E1" (see Figure 10C ). In other words, the first charging controller 319 checks the version of the control software associated with "Yes" in terms of compatibility based on the identified second management unit. In the present embodiment, "No" in terms of compatibility is associated with the version "V2" of the control software. On the other hand, "Yes" in terms of compatibility is associated with the version "V1" of the control software, and the NVM 161 stores the control software of version "V1". Therefore, the first charging controller 319 determines that there is associated control software (Yes in step S41).

[0130] When there is associated control software, the first charging controller 319 skips the processes of step S42, step S43, and step S45 (described later) and selects the associated control software (step S46). In the present embodiment, the first charging controller 319 switches the control software of the latest version "V2" to the control software of version "V1" and selects this control software. Therefore, the control software of version "V1" of the first charging station 310 can ensure compatibility with the vehicle control software of the electric vehicle 100.

[0131] On the other hand, when there is no associated control software (No in step S41), the first charging controller 319 accesses the station management server 220 and determines whether the associated control software can be obtained from the station management server 220 (step S42). For example, when in Figure 10C the compatibility "No" is associated with version "V1" and version "V2" of the station model ID "S1" associated with the vehicle model ID "E1" of version "V3", and the compatibility "Yes" is associated with version "V3" (not shown), the NVM 319m may not store the control software of version "V3". In this case, the first charging controller 319 determines that there is no associated control software and determines whether the associated control software can be obtained from the station management server 220.

[0132] When the associated control software can be obtained because the station management server 220 has the associated control software (Yes in step S42), the first charging controller 319 requests the associated control software from the station management server 220 (step S43). In the present embodiment, the station control SW storage unit 225 stores the control software including the station model ID "S1" and version "V3" (see Figure 8 ), so the first charging controller 319 requests the associated control software from the station management server 220.

[0133] When the associated control software is requested, the vehicle control SW management unit 217 sends the associated control software to the electric vehicle 100 (step S44). When the associated control software is sent, the first charging controller 319 receives and obtains the associated control software (step S45). When the first charging controller 319 obtains the associated control software, the first charging controller 319 stores and holds the associated control software in the NVM 319m.

[0134] When the associated control software is maintained, in the process of step S46, the first charging controller 319 selects the associated control software. In other words, the first charging controller 319 switches the control software of the latest version "V2" to the control software of version "V3", and selects this control software. As described above, when the compatibility "Yes" is associated with the version "V3" of the station model ID "S1" associated with the vehicle model ID "E1", the control software of version "V3" of the first charging station 310 can ensure compatibility with the vehicle control software of the electric vehicle 100 by the first charging controller 319 selecting the control software of version "V3".

[0135] When the associated control software cannot be obtained because the station management server 220 does not have the associated control software (No in step S42), in the process of step S46, the first charging controller 319 selects the control software with a high possibility of supply. For example, when Figure 10C the compatibility "No" is associated with versions "V1" and "V2" of the station model ID "S1" associated with the vehicle model ID "E1" of version "V3", the first charging controller 319 selects the control software of any version of the station model ID "S1" associated with the compatibility "Yes". For example, in Figure 10C the first charging controller 319 selects the control software of version "V2" of the station model ID "S1" associated with the vehicle model ID "E1" of version "V2". Since the NVM 319m stores the control software of version "V2" (see Figure 10A ), the first charging controller 319 can select the control software.

[0136] The case of the first charging station 310 has been described as an example, and the case of the second charging station 320 is basically similar to the case of the first charging station 310. Therefore, except for the process of step S47, various processes of the second charging station 320 corresponding to the processes of step S41, step S42, step S43, step S44, step S45, and step S46 in Figure 15 are omitted from the drawings, and their detailed descriptions are omitted.

[0137] When the control software is selected in the process of step S46, the ECU 160 of the electric vehicle 100 sends charging data such as a charging start request to the first charging station 310 or the second charging station 320 (step S48). When the charging data is sent to the first charging station 310, the first charging controller 319 receives the charging data (step S49). When the charging data is sent to the second charging station 320, the second charging controller 329 receives the charging data (step S50).

[0138] When the first charging controller 319 receives charging data, the first charging controller 319 transmits output data such as maximum output information to the electric vehicle 100 (step S51). When the second charging controller 329 receives charging data, the second charging controller 329 transmits output data to the electric vehicle 100 (step S52). When output data is transmitted from the first charging station 310 or the second charging station 320, the ECU 160 receives the output data transmitted from the first charging station 310 or the second charging station 320 (step S53).

[0139] When the ECU 160 receives the output data, the supply of power from the first charging station 310 or the second charging station 320 to the electric vehicle 100 is started. In other words, the charging of the electric vehicle 100 starts. Since the first charging controller 319 or the second charging controller 329 selects control software compatible with the vehicle control software through the process of step S46, it is possible to avoid a situation where the vehicle control software and the control software do not support each other.

[0140] Embodiments of the present invention have been described in detail; however, the present invention is not limited to the above specific embodiments. Various modifications or variations are applicable within the scope of the gist of the present invention described in the appended claims.

[0141] For example, in the first and second embodiments, the first charging station 310 and the second charging station 320 are described as examples of supply devices and energy supply devices. Alternatively, when the electric vehicle 100 is a fuel cell vehicle, a hydrogen station that supplies hydrogen as energy can be adopted instead of the charging station 300. Through such an embodiment, it is possible to avoid a situation where there is no compatibility between the control software for controlling hydrogen supply and the vehicle control software for controlling hydrogen replenishment.

[0142] In the first embodiment, the electric vehicle 100 receives a vehicle control program via wireless communication WL. Alternatively, the electric vehicle 100 can receive the vehicle control program via wired communication such as a first communication line 314 included in a charging cable extending from the first charging station 310, for example.

[0143] Regarding the above embodiments, the following supplementary explanations will be described.

[0144] Appendix 1

[0145] An energy supply method in which a plurality of supply devices independently supply energy to an electric vehicle for replenishing energy includes: a controller of the electric vehicle maintaining a plurality of vehicle control software associated with at least two control software of each of the plurality of supply devices, and when replenishing energy from any one of the plurality of supply devices, the controller selecting, from among the plurality of vehicle control software, the vehicle control software associated with the control software of any one supply device.

Claims

1. An electric vehicle that independently replenishes the energy from each of a plurality of energy supply devices that supply energy, the electric vehicle including a controller configured to: Maintain a plurality of vehicle control software of the electric vehicle associated with at least two control software of each of the plurality of energy supply devices, the plurality of vehicle control software having different versions from each other, the plurality of vehicle control software including replenishment control software for controlling operations related to the replenishment of energy, Store compatibility data regarding the compatibility between the electric vehicle and each of the plurality of energy supply devices, wherein a plurality of combinations of station models and vehicle models are used as the compatibility data, the station model being an identifier for identifying the model of the energy supply device, the vehicle model being an identifier for identifying the model of the electric vehicle, the compatibility indicating the compatibility between the version of the control software and the version of the vehicle control software, and When replenishing energy from any one of the plurality of energy supply devices, select, from among the plurality of vehicle control software, a compatible vehicle control software associated with the version of the control software of the any one energy supply device, Among them, The controller is configured to, when the controller does not maintain a compatible vehicle control software associated with the version of the control software of the any one energy supply device, obtain and select, from a server capable of communicating with the electric vehicle, a compatible vehicle control software associated with the version of the control software of the any one energy supply device, The controller is configured to, when it is not possible to obtain the associated vehicle control software because the server does not have the associated vehicle control software, select a vehicle control software with a high possibility of supply.

2. The electric vehicle according to claim 1, wherein: The electric vehicle includes a secondary battery as a power source; and The plurality of energy supply devices are configured to supply electric power as the energy.

3. The electric vehicle according to claim 1, wherein: The electric vehicle includes a fuel cell as a power source, and the fuel cell uses hydrogen as a fuel; and The plurality of energy supply devices are configured to supply hydrogen as the energy.

4. An energy supply device that supplies energy to a plurality of electric vehicles individually, the energy supply device including a control unit configured to: Maintain a plurality of control software of the energy supply device associated with at least two vehicle control software of each of the plurality of electric vehicles, the plurality of control software having different versions from each other, the plurality of control software including supply control software for controlling operations related to the supply of electric power, Store compatibility data regarding the compatibility between the electric vehicle and the energy supply device, wherein a plurality of combinations of station models and vehicle models are used as the compatibility data, the station model being an identifier for identifying the model of the energy supply device, the vehicle model being an identifier for identifying the model of the electric vehicle, the compatibility indicating the compatibility between the version of the control software and the version of the vehicle control software, and When supplying energy to any one of the plurality of electric vehicles, a compatible control software associated with the version of the vehicle control software of the any one electric vehicle is selected from among the plurality of control softwares. Among them, The control unit is configured to, when the control unit does not hold a compatible control software associated with the version of the vehicle control software of the any one electric vehicle, obtain and select a compatible control software associated with the vehicle control software of the any one electric vehicle from a server capable of communicating with the energy supply device. The control unit is configured to, when it is not possible to obtain the associated control software because the server does not have the associated control software, select a control software with a high likelihood of supply.

5. An energy supply system, comprising: A plurality of supply devices configured to supply energy; And An electric vehicle configured to independently replenish the energy from each of the plurality of supply devices, wherein: The electric vehicle includes a controller configured to: Hold a plurality of vehicle control softwares of the electric vehicle associated with at least two control softwares of each of the plurality of supply devices, the plurality of vehicle control softwares having different versions from each other, and the plurality of vehicle control softwares including a replenishment control software for controlling operations related to the replenishment of energy. Store compatibility data regarding the compatibility between the electric vehicle and each of the plurality of supply devices, wherein a plurality of combinations of station models and vehicle models are used as the compatibility data, the station model is an identifier for identifying the model of the supply device, the vehicle model is an identifier for identifying the model of the electric vehicle, and the compatibility indicates the compatibility between the version of the control software and the version of the vehicle control software. When replenishing energy from any one of the plurality of supply devices, select a compatible vehicle control software associated with the version of the control software of the any one supply device from among the plurality of vehicle control softwares. Wherein, the energy supply system further includes a server capable of communicating with the electric vehicle, wherein The controller is configured to, when the controller does not hold a compatible vehicle control software associated with the version of the control software of the any one supply device, obtain and select a compatible vehicle control software associated with the version of the control software of the any one supply device from the server. The controller is configured to, when it is not possible to obtain the associated vehicle control software because the server does not have the associated vehicle control software, select a vehicle control software with a high likelihood of supply.

Images