Electric vehicle, energy supply device and energy supply system

Abstract

An electric vehicle that replenishes energy independently from each of a plurality of supply devices that supply energy includes a controller. The controller is configured to, when vehicle control software of the electric vehicle associated with first control software of at least one first supply device of the plurality of supply devices is stored in a server capable of communicating with the electric vehicle, check a support relationship between the vehicle control software and second control software of a second supply device of the plurality of supply devices that is used by the electric vehicle at a higher frequency than the first supply device, and, when a support relationship does not exist, restrict reception of the vehicle control software via communication with the server or update of the vehicle control software of the electric vehicle based on receipt of the vehicle control software.

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] A technology is known in which a server provides charging station information including information about the location, availability, and accessibility of a charging station to an electric vehicle. The charging station information includes compatibility (e.g., plug type support) between the charging station and the electric vehicle as availability (e.g., see Japanese Unexamined Patent Application Publication No. 2014-212690 (JP2014-212690A)). Summary of the invention

[0003] The compatibility between energy supply equipment including a charging station and electric vehicles including electric vehicles is not only hardware compatibility such as a plug type but also software compatibility such as a program for controlling the energy supply equipment or the electric vehicle.

[0004] For energy supply devices installed in places such as public facilities and commercial facilities, when a server periodically 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 the electric vehicle that is compatible with the latest software to the electric vehicle via, for example, wireless communication, the electric vehicle can be supplied with energy from the energy supply device updated to the latest state to replenish energy.

[0005] However, the energy supply device installed in a residence or the like where the use frequency of the electric vehicle is high may obtain the latest software from the server irregularly by manual operation. When the latest software is forgotten to be obtained, the support relationship between the electric vehicle provided with the software for the electric vehicle and the energy supply device installed in the residence or the like will be lost, and the electric vehicle may not be able to replenish energy from the energy supply device.

[0006] The present invention provides an electric vehicle, an energy supply device, and an energy supply system that avoid the loss of a support relationship between two softwares that respectively control the supply and replenishment of energy.

[0007] One aspect of the present invention relates to an electric vehicle. The electric vehicle that replenishes energy independently from each of a plurality of supply devices that supply energy includes a controller. The controller is configured to, when vehicle control software of the electric vehicle associated with first control software of at least one first supply device of the plurality of supply devices is stored in a server capable of communicating with the electric vehicle, check a support relationship between the vehicle control software and second control software of a second supply device of the plurality of supply devices that is used by the electric vehicle at a higher frequency than the first supply device, and when there is no support relationship, restrict the reception of the vehicle control software via communication with the server or the update of the vehicle control software of the electric vehicle based on the reception of the vehicle control software.

[0008] In the above configuration, the controller may be configured to, when a support relationship exists, perform reception of the vehicle control software via communication with the server and update of the vehicle control software of the electric vehicle based on the reception of the vehicle control software.

[0009] In the above configuration, the electric vehicle may further include a secondary battery as a power source, and the 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, and the fuel cell may use hydrogen as fuel, and the plurality of supply devices may be configured to supply hydrogen as energy.

[0011] In the above configuration, the version of the first control software may be newer than the version of the second control software.

[0012] Another aspect of the present invention relates to an energy supply device. The energy supply device supplies energy to an electric vehicle. The energy supply device includes a control unit. The control unit is configured to, when second control software of the energy supply device that is configured to supply energy to the electric vehicle independently of the energy supply device and is used by the electric vehicle at a lower frequency than the energy supply device, which is updated than the first control software associated with the vehicle control software of the electric vehicle, is stored in a server capable of communicating with the energy supply device, check the support relationship between the second control software and the vehicle control software, and when there is no support relationship, limit the reception of the second control software or update the second control software of the energy supply device based on the reception of the second control software.

[0013] In the above configuration, the controller may be configured to: when a support relationship exists, perform reception of the second control software and update of the second control software of the energy supply device based on the reception of the second control software.

[0014] 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, an electric vehicle configured to independently replenish energy from each of the plurality of supply devices, and a server capable of communicating with the plurality of supply devices and the electric vehicle. The electric vehicle includes a controller. The controller is configured to, when vehicle control software of the electric vehicle associated with a first control software of at least one first supply device among the plurality of supply devices is stored in the server, check a support relationship between the vehicle control software and a second control software of a second supply device among the plurality of supply devices that is used by the electric vehicle at a higher frequency than the first supply device, and when a support relationship does not exist, limit the reception of the vehicle control software via communication with the server or the update of the vehicle control software of the electric vehicle based on the reception of the vehicle control software.

[0015] In the above configuration, the controller may be configured to, when a support relationship exists, perform reception of the vehicle control software via communication with the server and update of the vehicle control software of the electric vehicle based on the reception of the vehicle control software.

[0016] According to aspects of the present invention, it is possible to avoid the loss of a support relationship between two softwares that respectively control the supply and replenishment of energy. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, in which like numerals represent like elements, and in which:

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

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

[0020] Figure 3 is an example of the hardware configuration of a vehicle management server;

[0021] Figure 4 is an example of the functional configuration of the vehicle management server;

[0022] Figure 5 is an example of a vehicle control software management table;

[0023] Fig. 6A is an example of a first support table;

[0024] Figure 6B is an example of a second support table;

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

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

[0027] Fig.9A is an example of a configuration of a first charging station;

[0028] Fig. 9B is an example of a configuration of a second charging station;

[0029] Fig.10 is a process sequence diagram (Part 1) showing an example of the operation of the energy supply system according to the first embodiment;

[0030] Fig.11 is a process sequence diagram (Part 2) showing an example of the operation of the energy supply system according to the first embodiment;

[0031] Fig.12 is a process sequence diagram (Part 1) showing an example of the operation of the energy supply system according to the second embodiment; and

[0032] Fig.13 is a process sequence diagram (Part 2) showing an example of the operation of the energy supply system according to the second embodiment. DETAILED DESCRIPTION

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

[0034] First embodiment

[0035] 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 an electric vehicle that can travel using a motor using electricity 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 a 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.

[0036] 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 station 300 includes 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 station 300 includes a plurality of first charging stations and a plurality of second charging stations. Each charging station 300 is an example of a supply device. The first charging station 310 is an example of a first supply device and a different energy supply device. The second charging station 320 is an example of a second supply device and an energy supply device.

[0037] The vehicle management server 210 and the station management server 220 are connected to each other through 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 a communication network NW. The communication network NW is, for example, the Internet.

[0038] 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 the 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.

[0039] 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 DC power of tens of kilowatts to hundreds of kilowatts. The first charging station 310 is installed in a parking lot of, for example, a public facility or a commercial facility. The first charging station 310 is connected to a 200-volt three-phase AC power supply 312 via a power system 311 different from the communication system W1. On the other hand, the second charging station 320 is, for example, a standard charging station capable of supplying several kilowatts of DC power. The second charging station 320 is installed in a residential garage of a person who owns the electric vehicle 100, or in a 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 AC power supply 322 via a power system 321 different from the communication system W2. In this way, since the second charging station 320 is installed in a personal residential garage or a company parking lot, the frequency of use of the second charging station 320 is higher than the frequency of use of the first charging station 310 temporarily used in the middle of the driving route. The usage frequency may be the number of times used per hour, the number of times used per day, the number of times used per month, or the number of times used per year.

[0040] The first charging station 310 and the second charging station 320 each supply power as energy to the electric vehicle 100 independently of each other. When, for example, the electric vehicle 100 is parked in a 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 a 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 with power independently supplied from each of the first charging station 310 and the second charging station 320.

[0041] A case where the electric vehicle 100 is charged using the power supplied from the first charging station 310 will be described in detail. 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 via the charging cable. Therefore, the electric vehicle 100 is able to be supplemented 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, so a detailed description is omitted.

[0042] The vehicle management server 210 communicates with the electric vehicle 100 through 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 sends the vehicle control software (specifically, control program, firmware, etc.) for controlling the electric vehicle 100 to the electric vehicle 100. The vehicle control software includes a supplementary control software for controlling operations related to the replenishment (i.e., charging) of electric power. On the other hand, the station management server 220 communicates with the first charging station 310 and the second charging station 320 through 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 sends the control software for controlling the first charging station 310 to the first charging station 310. Similarly, the station management server 220 sends the control software for controlling the second charging station 320 to the second charging station 320. A plurality of control software includes a supply control software for controlling operations related to the supply of electric power.

[0043] Although described in detail later, the station management server 220 periodically sends a new version (specifically, the latest version) of the control software to the first charging station 310 in a unified manner. When the first charging station 310 receives the new version of the control software and updates it with the new version of the control software, the first charging station 310 is in the latest state. The vehicle management server 210 sends a new version of the vehicle control software that is compatible with the new version of the control software to the electric vehicle 100 in synchronization with the transmission of the new version of the control software of the station management server 220. The electric vehicle 100 receives the new version of the vehicle control software via the wireless communication WL and updates it with the new version of the vehicle control software. Therefore, the electric vehicle 100 is in the latest state.

[0044] On the other hand, the station management server 220 sends the new version control software to the second charging station 320 in response to a 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 regular transmission of the control software requires high communication costs, some users may set the transmission based on manual operation to the second charging station 320 without setting dynamic regular transmission. When the second charging station 320 makes a request for the transmission of the new version control software, the station management server 220 sends the new version control software to the second charging station 320. The second charging station 320 receives the new version control software and updates it with the new version control software. Therefore, the second charging station 320 is in the latest state. When the second charging station 320 is in the latest state, the second charging station 320 is compatible with the electric vehicle 100 in the latest state, so the electric vehicle 100 can replenish electricity from the second charging station 320. In other words, the electric vehicle 100 can be charged from the second charging station 320 .

[0045] 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 and input control of electricity and the communication operate normally. Therefore, for example, the electric vehicle 100 can be charged at the fastest charging rate. The charging completion time until the charging is completed can be calculated with high precision. In addition, the screen guidance of the electric vehicle 100 or the first charging station 310 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 be reduced, the accuracy of calculating the charging completion time may be reduced, and the accuracy of displaying the screen guidance may be reduced.

[0046] Reference Figure 2The configuration of the electric vehicle 100 is described. 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, a drive wheel 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), and an input and output interface (I / F).

[0047] The power storage device 110 is a power storage element configured to be chargeable 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 a double layer capacitor, etc. A lithium ion battery is a secondary battery using lithium as a carrier. The lithium ion battery may be a lithium ion battery in which the electrolyte is a liquid or may be an all-solid battery in which the electrolyte is a solid.

[0048] The power storage device 110 is charged by a first charging station 310 located outside the vehicle and connected to the first inlet 150 via a charging cable (external charging). The power storage device 110 is charged by a second charging station 320 located outside the vehicle and connected to the second inlet 152 via a charging cable (see Figure 1 ) charging (external charging). Power storage device 110 supplies electric power to MG 130 through PCU 120 during traveling. Power storage device 110 is charged with electric power generated by MG 130 through PCU 120 during regenerative power generation of MG 130 in vehicle braking.

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

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

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

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

[0053] 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, the pair of power lines DCL1, DCL2, the charging relay RY, the pair of power lines PL2, NL2, and the pair of power lines PL1, NL1.

[0054] The second inlet 152 receives the charge from the second charging station 320 (see Figure 1 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, the pair of power lines DCL1, DCL2, the charging relay RY, the pair of power lines PL2, NL2, and the pair of power lines PL1, NL1.

[0055] DCM 170 is used to communicate with vehicle management server 210 (see Figure 1) is an on-vehicle communication instrument for communicating with the ECU 160. The DCM 170 is capable of bidirectional communication between the electric vehicle 100 (specifically, the ECU 160) and the vehicle management server 210 through wireless communication WL, a cellular base station BS, and a communication network NW. The GPS receiver 172 determines the current position based on radio waves from an artificial satellite, and outputs the determined position information to the ECU 160. The position information determined by the GPS receiver 172 is used, for example, for a navigation system (not shown) or the like.

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

[0057] The charging mode that can be adopted in the electric vehicle 100 according to the present embodiment is not limited to the CHAdeMO mode, and for example, a combined charging system (combo) mode that is mainly standardized in Europe and the U.S. may 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 may be performed through power line communication (PLC) or near field communication.

[0058] When the electric vehicle 100 is traveling, 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 performs 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 (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 disconnects the charging relay RY. As for the method of calculating the SOC, various known methods can be used, such as a method using an OCV-SOC curve (mapping, etc.) representing the relationship between the open circuit voltage (OCV) and the SOC, a method using an integrated value of the charging and discharging current, and a method of remaining capacity / full charge capacity×100.

[0059] The charging cable of the first charging station 310 has a first connector connectable 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 substantially similar to the first charging station 310, and thus a detailed description is omitted.

[0060] In a state where the first connector of the first charging station 310 is connected to the first inlet 150, data transmitted from the electric vehicle 100 to the first charging station 310 includes, for example, a charge start request, a charge stop request, a charge current command value, a charge voltage upper limit, etc. Data to be transmitted from the first charging station 310 to the electric vehicle 100 includes, for example, maximum output information (such as an available current value and an available voltage value), current output information (such as a current output current value and a current output voltage value), etc. The second charging station 320 is substantially similar to the first charging station 310.

[0061] Will refer to Figure 3 The hardware configuration of the vehicle management server 210 is described. The station management server 220 basically has a hardware configuration similar to that of the vehicle management server 210, so its description is omitted. Figure 3 As shown, the vehicle management server 210 includes a CPU 210A used as a processor, a RAM 210B and a ROM 210C used as a memory, and a network I / F 210D. If 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.

[0062] The 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. The display device 720 is connected to the output I / F 210G. A liquid crystal display is an example of the display device 720. The 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, the input I / F 210F and the input and output I / F 210H each include a USB port. The output I / F 210G includes, for example, a display port.

[0063] The portable recording medium 740 is inserted into the drive device 210I. For example, a removable disk such as a Compact Disc (CD)-ROM and a Digital Versatile Disc (DVD) is an example 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 the communication network NW.

[0064] The program stored in the ROM 210C or the HDD 210E is temporarily stored in the RAM 210B by the CPU 210A. The program recorded on the portable recording medium 740 is temporarily stored in the RAM 210B by the CPU 210A. When the CPU 210A runs the stored program, the CPU 210A realizes various functions (described later) and performs various processes (described later). The program only needs to follow the process sequence diagram (described later).

[0065] Reference Figures 4 to 6B The functional configuration of the vehicle management server 210 is described. Figure 4 The main part of the function of the vehicle management server 210 is shown.

[0066] like Figure 4 As 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 a RAM 210B, a HDD 210E, etc. The processing unit 212 is implemented by a CPU 210A. The input unit 213 is implemented by an input I / F 210F. The communication unit 214 is implemented by a 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.

[0067] The storage unit 211 includes a vehicle control software (hereinafter, referred to as SW) storage unit 215 and a compatibility storage unit 216 as components. At least one of the vehicle control SW storage unit 215 and the compatibility storage unit 216 may be provided in another management server different from the vehicle management server 210. In this case, the vehicle management server 210 may access another management server and refer to the details stored in the vehicle control SW storage unit 215 and the compatibility storage unit 216.

[0068] The vehicle control SW storage unit 215 stores the vehicle control software in the vehicle control software management table. Figure 5 As shown, the vehicle control SW storage unit 215 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 electric vehicle 100. The version and release date are the version and availability date of the vehicle control software, respectively. In the first embodiment, the version "V1" corresponds to the old version of the vehicle control software, and the version "V2" corresponds to the new version of the vehicle control software.

[0069] The compatibility storage unit 216 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, Fig. 6A and Figure 6B As shown, the compatibility storage unit 216 manages the compatibility data by using a first support table and a plurality of second support tables.

[0070] like Fig. 6A As shown, the first support table manages multiple combinations of station model IDs and vehicle model IDs as compatibility data. The station model ID is an identifier for identifying 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 combination of the station model ID and the vehicle model ID is uniquely identified by using the first support table. A predetermined identifier is set for the station model ID of the charging station 300 with a high frequency of use of the electric vehicle 100. The predetermined identifier can be set manually or can be dynamically set by the vehicle control SW management unit 217 (described later) that calculates the frequency of use. For example, a predetermined identifier "#" is set for the combination of the station model ID "S2" and the vehicle model ID "E1". Therefore, the electric vehicle 100 assigned the vehicle model ID "E1" can uniquely identify the second charging station 320 with a high frequency of use. For another electric vehicle (not shown) different from the electric vehicle 100, a predetermined identifier is also set for the station model ID of the charging station 300 with a high frequency of use.

[0071] like Figure 6BAs shown, each second support table manages the compatibility between the version of the control software of the charging station 300 assigned the station model ID and the version of the vehicle control software of the electric vehicle 100 assigned the vehicle model ID, as compatibility data for each combination of the station model ID and the vehicle model ID. Compatibility "Yes" indicates that there is compatibility between the control software and the vehicle control software. Compatibility "No" indicates that there is no compatibility between the control software and the vehicle control software. Therefore, this indicates that there is no compatibility between the version "V2" of the control software of the second charging station 320 assigned the station model ID "S2" and the version "V1" of the vehicle control software of the electric vehicle 100 assigned the vehicle model ID "E1". Through 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.

[0072] The processing unit 212 includes a vehicle control SW management unit 217. The vehicle control SW management unit 217 selectively accesses the components of the storage unit 211 and performs various processes. For example, when the vehicle control SW management unit 217 receives a request to send a new version of vehicle control software from the electric vehicle 100, the vehicle control SW management unit 217 sends the new version of vehicle control software associated with the vehicle model ID of the electric vehicle 100 to the electric vehicle 100. The details of the vehicle control SW management unit 217 will be described when the operation of the energy supply system ST is described.

[0073] Will refer to Figure 7 and Figure 8 The functional configuration of the station management server 220 is described. Figure 7 The main part of the function of the station management server 220 is shown.

[0074] like Figure 7 As 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, the 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.

[0075] The storage unit 221 includes a station control SW storage unit 225 and a compatibility storage unit 226 as components. At least one of the station control SW storage unit 225 and the compatibility storage unit 226 may be provided in another management server different from the station management server 220. In this case, the station management server 220 may access another management server and refer to the details stored in the station control SW storage unit 225 and the compatibility storage unit 226.

[0076] The station control SW storage unit 225 stores the control software for controlling the charging station 300 in the control software management table. Figure 8 As shown, the station control SW storage unit 225 stores the station model ID, control software, version, release date, etc. in association with each other. The version and release date are the version and availability date of the control software, respectively. As in the case of vehicle control software, version "V1" corresponds to the old version of the control software, and version "V2" corresponds to the new version of the control software. The compatibility storage unit 226 stores compatibility data as well as the compatibility storage unit 216. Therefore, a detailed description of the compatibility storage unit 226 is omitted.

[0077] The processing unit 222 includes a station control SW management unit 227. The station control SW management unit 227 selectively accesses the components of the storage unit 221 and performs various processes. For example, when the station control SW management unit 227 receives a request to send a new version of the control software from the second charging station 320, the station control SW management unit 227 sends the new version of the control software associated with the station model ID of the second charging station 320 to the second charging station 320. When describing the operation of the energy supply system ST, the details of the station control SW management unit 227 will be described.

[0078] Reference Fig.9A The configuration of the first charging station 310 is described. 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, input and output I / F, etc. The three-phase AC power supply 312 is connected to the AC-DC converter 315 via the power system 311. One end of a pair of first power lines 313 is connected to the rectifier 318. One end of the first communication line 314 is connected to the first charging controller 319. The first connector C1 is connected to the other end of the pair of first power lines 313 and the other end of 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 the charging cable extending from the first charging station 310 and are included in the charging cable.

[0079] The AC-DC converter 315 receives power supplied from the three-phase AC power source 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 boosting efficiency. The step-up transformer 317 steps up the high-frequency AC power. The rectifier 318 rectifies and smoothes the boosted AC power boosted from the high-frequency AC power, and outputs the DC power via the first connector C1. The first charging controller 319 communicates with the ECU 160 (see FIG. 1 ) of the electric vehicle 100. Figure 2 ) 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.

[0080] Reference Fig. 9B The configuration of the second charging station 320 is described. 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, input and output I / F, etc. The single-phase AC power supply 322 is connected to the first filter 325 via the power system 321. One end of a pair of second power lines 323 is connected to the second filter 328. One end of the second communication line 324 is connected to the second charging controller 329. The second connector C2 is connected to the other end of the pair of second power lines 323 and the other end of the second communication line 324. The second connector C2 can be connected to the second inlet 152 of the electric vehicle 100. The pair of second power lines 323 and the second communication line 324 are part of the charging cable extending from the second charging station 320 and are included in the charging cable.

[0081] 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 having 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 communicates with the ECU 160 (see FIG. 16) of the electric vehicle 100. Figure 2 ) while exchanging information such as the current SOC of the power storage device 110, while controlling the operations of the AC-DC converter 326 and the DC-DC converter 327.

[0082] Reference Fig.10 and Fig.11 The operation of the energy supply system ST according to the first embodiment is described. Fig.10 and Fig.11 In the example, the character "A", the character "B", etc. represent the succession of processing.

[0083] Initially, as Fig.10 As shown, the station control SW management unit 227 of the station management server 220 waits until a new version of the control software for controlling the operation of the first charging station 310 is input (No in step S1). When the new version of the control software is input (Yes in step S1), the station control SW management unit 227 stores the new version of the control software in the station control SW storage unit 225 (step S2). Therefore, when, for example, a new version "V2" of the control software "S1 control program" for the first charging station 310 is input, the station control SW storage unit 225 stores the new version "V2" (see Figure 8 ).

[0084] When the station control SW management unit 227 stores the new version of the control software, the station control SW management unit 227 dynamically sends the new version to the first charging station 310 (step S3). After the new version of the control software is input, the station control SW management unit 227 may send the new version before storing the new version, or may send the new version after storing the new version. The station control SW management unit 227 may send the new version of the control software based on a predetermined set date and time, a set time, etc.

[0085] When the new version of the control software is transmitted, the first charging controller 319 of the first charging station 310 receives the new version of the control software (step S4). When the first charging controller 319 receives the new version of the control software, the first charging controller 319 updates the old version of the control software with the new version of the control software (step S5). When, for example, the old version "V1" of the control software "S1 control program" is installed in the first charging station 310, the first charging controller 319 updates the old version "V1" with the new version "V2" of the control software "S1 control program". Therefore, the first charging controller 319 is in the latest state.

[0086] On the other hand, the vehicle control SW management unit 217 of the vehicle management server 210 waits until a new version of the vehicle control software for controlling the operation of the electric vehicle 100 is input (No in step S6). When the new version of the vehicle control software is input (Yes in step S6), the vehicle control SW management unit 217 stores the new version of the vehicle control software in the vehicle control SW storage unit 215 (step S7). Therefore, when, for example, a new version "V2" of the vehicle control software "E1 control program" of the electric vehicle 100 is input, the vehicle control SW storage unit 215 stores the new version "V2" (see step S7). Figure 5 ).

[0087] Before or after the processing of step S6 and step S7, the ECU 160 of the electric vehicle 100 periodically checks for a new version of the vehicle control software through the DCM 170 and the vehicle control SW management unit 217 (step S8). The ECU 160 waits until the ECU 160 determines that there is a new version of the vehicle control software (no in step S9). When the ECU 160 determines that there is a new version of the vehicle control software (yes in step S9), the ECU 160 checks compatibility with the vehicle control SW management unit 217 (step S10). More specifically, the ECU 160 checks compatibility between the vehicle control software and the control software for controlling the second charging station 320. When the ECU 160 checks compatibility, the ECU 160 sends the vehicle model ID assigned to the ECU 160 or the DCM 170 to the vehicle control SW management unit 217.

[0088] When the vehicle control SW management unit 217 is requested from the ECU 160 to check compatibility, the vehicle control SW management unit 217 provides a notification about compatibility to the ECU 160 (step S11). More specifically, when the vehicle control SW management unit 217 is requested to check compatibility, the vehicle control SW management unit 217 accesses the first support table (see Fig. 6A ) and identifies the station model ID to which a predetermined identifier is set from among the station model IDs associated with the vehicle model ID sent when checking compatibility. In the present embodiment, the vehicle model ID "E1" is sent, so the vehicle control SW management unit 217 identifies the station model ID "S2" to which a predetermined identifier "#" is set from among the station model IDs "S1", "S2", ... When the vehicle control SW management unit 217 identifies the station model ID "S2", the vehicle control SW management unit 217 requests the station model ID "S2" and the current version of the control software installed in the second charging station 320 from the station control SW management unit 227. Therefore, the station control SW management unit 227 accesses the control software management table (see Figure 8 ), and provides notification of the control software associated with the station model ID and its current version to the vehicle control SW management unit 217. In the present embodiment, the station control SW management unit 227 provides notification of the control software "S2 control program" associated with the station model ID "S2" and its current version "V1" to the vehicle control SW management unit 217.

[0089] When the vehicle control SW management unit 217 receives the notification about the control software and its current version from the station control SW management unit 227, the vehicle control SW management unit 217 identifies the second support table associated with the combination of the vehicle model ID and the station model ID (see Figure 6B). When the vehicle control SW management unit 217 identifies the second support table, the vehicle control SW management unit 217 provides a notification about compatibility to the ECU 160 based on the identified second support table, the updated new version for the vehicle control software checked and determined by the ECU 160 in the processing of steps S8 and S9, and the current version of the notification provided from the station control SW management unit 227.

[0090] refer to Fig.11 , ECU 160 determines whether there is compatibility based on the notification from the vehicle control SW management unit 217 (step S12). When, for example, a notification of "No" regarding compatibility is provided, ECU 160 determines that there is no compatibility (No in step S12). In the present embodiment, the control software "S2 control program" associated with the station model ID "S2" is version "V1" at the current time point, and the vehicle control software "E1 control program" associated with the vehicle model ID "E1" is a new version "V2". Therefore, based on the second support table (see Figure 6B ), there is no compatibility between the two software. Therefore, a notification of "NO" regarding compatibility is provided, and the ECU 160 determines that there is no compatibility.

[0091] When there is no compatibility, the ECU 160 determines whether there is an alternative (step S13). When there is no compatibility, the ECU 160 may limit (e.g., cancel or stop) subsequent processing. When, for example, the ECU 160 updates the control software for the second charging station 320 as an alternative, the ECU 160 determines whether there is compatibility with the new version of the vehicle control software. In this case, the ECU 160 checks the alternative with the vehicle control SW management unit 217, and the vehicle control SW management unit 217 provides the ECU 160 with a notification of the presence or absence of the alternative based on the second support table. When there is no alternative (No in step S13), the ECU 160 ends the process.

[0092] On the other hand, when there is an alternative (Yes in step S13), the ECU 160 requests the vehicle control SW management unit 217 to send a new version of the control software for the second charging station 320 (step S14). When the vehicle control SW management unit 217 is requested to send a new version from the ECU 160, because the control software is managed by the station management server 220, the vehicle control SW management unit 217 requests the station control SW management unit 227 to send a new version (step S15). When another new version "V2" that is newer than the new version "V1" and associated with the station model ID "S2" is managed in the control software management table, compatibility is ensured based on the second support table. Therefore, the station control SW management unit 227 sends the new version of the control software for the second charging station 320 to the second charging controller 329 of the second charging station 320 (step S16).

[0093] When the second charging controller 329 receives the new version of the control software sent from the station control SW management unit 227 (step S17), the second charging controller 329 updates the control software based on the received new version of the control software (step S18). In other words, the second charging station 320 is forcibly updated by the station control SW management unit 227. Therefore, the second charging station 320 is in the latest state with compatibility with the electric vehicle 100.

[0094] On the other hand, when a notification of compatibility "Yes" is provided in the process of step S12, the ECU 160 determines that there is compatibility (Yes in step S12). When, for example, compatibility "Yes" is managed for a combination of version "V2" of the vehicle model ID "E1" and version "V1" of the station model ID "S2" in the second support table (see Figure 6B ), providing a notification of "yes" regarding compatibility. In this way, when there is compatibility or when the processing of step S14 is completed, ECU 160 requests the new version of the vehicle control software from the vehicle control SW management unit 217 (step S19). In other words, ECU 160 allows the reception of the new version of the vehicle control software and the update based on the received vehicle control software. Therefore, the vehicle control SW management unit 217 sends the new version of the vehicle control software to ECU 160 (step S20). In the present embodiment, the vehicle control SW management unit 217 sends the new version "V2" of the vehicle control software "E1 control program".

[0095] When the ECU 160 receives the new version of the vehicle control software transmitted from the vehicle control SW management unit 217 (step S21), the ECU 160 updates the old version of the vehicle control software with the new version based on the received new version of the vehicle control software (step S22). In other words, the ECU 160 performs the update. Therefore, the electric vehicle 100 is in the latest state with compatibility with both the first charging station 310 and the second charging station 320. As a result, the loss of compatibility between the control software for controlling the supply of electric power and the vehicle control software for controlling the replenishment of electric power can be avoided.

[0096] Second embodiment

[0097] Next, refer to Fig.12 and Fig.13 The operation of the energy supply system ST according to the second embodiment is described. Fig.12 and Fig.13 In the example, the character "P", the character "Q", etc. are used to represent the continuation of the processing.

[0098] Initially, as Fig.12 As shown, the station control SW management unit 227 of the station management server 220 waits until a new version of the control software for controlling the operation of the second charging station 320 is input (No in step S31). When the new version of the control software is input (Yes in step S31), the station control SW management unit 227 stores the new version of the control software in the station control SW storage unit 225 (step S32). Therefore, when, for example, a new version "V2" of the control software "S2 control program" for the second charging station 320 is input, the station control SW storage unit 225 stores the new version "V2".

[0099] On the other hand, before or after the processing of step S31 and step S32, the second charging controller 329 of the second charging station 320 periodically checks for a new version of the control software with the station control SW management unit 227 through the communication network NW (step S33). The second charging controller 329 waits until there is a new version of the control software (No in step S34). When the second charging controller 329 determines that there is a new version of the control software (Yes in step S34), the second charging controller 329 checks compatibility with the station control SW management unit 227 (step S35). More specifically, the second charging controller 329 checks compatibility between the vehicle control software and the control software for controlling the second charging station 320. When the second charging controller 329 checks compatibility, the second charging controller 329 sends the station model ID assigned to the second charging controller 329 to the station control SW management unit 227.

[0100] When the station control SW management unit 227 is requested from the second charge controller 329 to check compatibility, the station control SW management unit 227 provides a notification about the compatibility to the second charge controller 329 (step S36). More specifically, when the station control SW management unit 227 is requested to check compatibility, the station control SW management unit 227 accesses the first support table of the compatibility storage unit 226 managed similarly to the compatibility storage unit 216 (see Fig. 6A ), and identifies the vehicle model ID to which a predetermined identifier is set from among the vehicle model IDs associated with the station model ID sent when checking compatibility. In the present embodiment, the station model ID "S2" is sent, so the station control SW management unit 227 identifies the vehicle model ID "E1" to which a predetermined identifier "#" is set from among the vehicle model IDs "E1", "E2", ... When the station control SW management unit 227 identifies the vehicle model ID "E1", the station control SW management unit 227 requests the vehicle control software of the vehicle model ID "E1" and the current version thereof installed in the electric vehicle 100 from the vehicle control SW management unit 217. Therefore, the vehicle control SW management unit 217 accesses the vehicle control software management table (see Figure 5 ), and provides notification about the vehicle control software associated with the vehicle model ID and its current version to the station control SW management unit 227. For example, the vehicle control SW management unit 217 provides notification about the vehicle control software "E1 control program" associated with the vehicle model ID "E1" and its current version "V1" to the station control SW management unit 227.

[0101] When the station control SW management unit 227 receives the notification about the vehicle control software and its current version from the vehicle control SW management unit 217, the station control SW management unit 227 identifies the second support table of the compatibility storage unit 226 associated with the combination of the station model ID and the vehicle model ID (see Figure 6B ). When the station control SW management unit 227 identifies the second support table, the station control SW management unit 227 provides a notification about compatibility to the second charge controller 329 based on the identified second support table, the updated new version for control software checked and determined by the second charge controller 329 in the processing of step S33 and step S34, and the current version of which the notification is provided from the vehicle control SW management unit 217.

[0102] refer to Fig.13, the second charging controller 329 determines whether there is compatibility based on the notification from the station control SW management unit 227 (step S37). When, for example, a notification of "No" regarding compatibility is provided, the second charging controller 329 determines that there is no compatibility (No in step S37). For example, the vehicle control software "E1 control program" associated with the vehicle model ID "E1" is version "V1" at the current point in time, and the updated version of the control software "S2 control program" associated with the station model ID "S2" is version "V2". Therefore, based on the second support table (see Figure 6B ), there is no compatibility between the two software. Therefore, a notification of "No" about compatibility is provided, and the second charging controller 329 determines that there is no compatibility.

[0103] When there is no compatibility, the second charge controller 329 determines whether there is an alternative (step S38). When there is no compatibility, the second charge controller 329 may limit (e.g., cancel or stop) subsequent processing. When, for example, the second charge controller 329 updates the vehicle control software for the electric vehicle 100 as an alternative, the second charge controller 329 determines whether there is compatibility with the new version of the control software. In this case, the second charge controller 329 checks the alternative with the station control SW management unit 227, and the station control SW management unit 227 provides a notification of the presence or absence of the alternative to the second charge controller 329 based on the second support table. When there is no alternative (No in step S38), the second charge controller 329 ends the process.

[0104] On the other hand, when there is an alternative (Yes in step S38), the second charging controller 329 requests the station control SW management unit 227 to send a new version of the vehicle control software for the electric vehicle 100 (step S39). When the station control SW management unit 227 is requested to send a new version from the second charging controller 329, because the vehicle control software is managed by the vehicle management server 210, the station control SW management unit 227 requests the vehicle control SW management unit 217 to send a new version (step S40). When another new version "V2" that is newer than the new version "V1" and associated with the vehicle model ID "E1" is managed in the vehicle control software management table, compatibility is ensured based on the second support table. Therefore, the vehicle control SW management unit 217 sends the new version of the vehicle control software for the electric vehicle 100 to the ECU 160 of the electric vehicle 100 (step S41).

[0105] When ECU 160 receives the new version of the vehicle control software sent from vehicle control SW management unit 217 (step S42), ECU 160 updates the vehicle control software based on the received new version of the vehicle control software (step S43). In other words, electric vehicle 100 is forcibly updated by vehicle control SW management unit 217.

[0106] On the other hand, when a notification of compatibility "Yes" is provided in the process of step S37, the second charging controller 329 determines that there is compatibility (Yes in step S37). When, for example, compatibility "Yes" is managed for a combination of version "V2" of the station model ID "S2" and version "V1" of the vehicle model ID "E1" in the second support table (see Figure 6B ), providing a notification of "yes" about compatibility. In this way, when there is compatibility or when the processing of step S39 is completed, the second charge controller 329 requests the station control SW management unit 227 for a new version of the control software (step S44). In other words, the second charge controller 329 allows reception of a new version of the control software and an update based on the received control software. Therefore, the station control SW management unit 227 sends the new version of the control software to the second charge controller 329 (step S45). In the present embodiment, the station control SW management unit 227 sends a new version "V2" of the control software "S2 control program".

[0107] When the second charging controller 329 receives the new version of the control software transmitted from the station control SW management unit 227 (step S46), the second charging controller 329 updates the old version of the control software with the new version based on the received new version of the control software (step S47). In other words, the second charging controller 329 performs the update. Therefore, the second charging station 320 is in the latest state with compatibility with the electric vehicle 100. As a result, the loss of compatibility between the control software for controlling the power supply and the vehicle control software for controlling the power replenishment can be avoided.

[0108] The embodiments of the present invention are described in detail; however, the present invention is not limited to the above-mentioned specific embodiments. Various modifications or changes are applicable within the scope of the gist of the present invention described in the appended claims.

[0109] For example, in the above embodiment, the first charging station 310 is described as an example of a first supply device and a different energy supply device, and the second charging station 320 is described as an example of a second supply device and an energy supply device. Alternatively, when the electric vehicle 100 is a fuel cell vehicle, a hydrogen station that supplies hydrogen as energy may be used instead of the charging station 300. Through such an embodiment, the loss of compatibility between the control software for controlling the hydrogen supply and the vehicle control software for controlling the hydrogen replenishment can be avoided.

[0110] In the first embodiment, the electric vehicle 100 checks compatibility and limits or performs updates of vehicle control software, etc. Alternatively, the vehicle management server 210 may perform similar processing. In the first embodiment, the electric vehicle 100 receives the vehicle control program via wireless communication WL. Alternatively, the electric vehicle 100 may receive the vehicle control program via wired communication such as the second communication line 324 included in the charging cable extending from the second charging station 320, for example.

[0111] Regarding the above-described embodiment, the following supplementary remarks will be described.

[0112] Appendix 1

[0113] An energy supply method for supplying energy to an electric vehicle that independently replenishes energy from each of a plurality of supply devices includes: when vehicle control software of the electric vehicle associated with first control software of at least one first supply device among the plurality of supply devices is stored in a server capable of communicating with the electric vehicle, a controller of the electric vehicle checks a support relationship between the vehicle control software and second control software of a second supply device among the plurality of supply devices that is used by the electric vehicle at a higher frequency than the first supply device, and, when a support relationship does not exist, restricts reception of the vehicle control software via communication with the server or updating of the vehicle control software of the electric vehicle based on receipt of the vehicle control software.

Claims

1. An electric vehicle that independently replenishes energy from each of a plurality of supply devices that supply energy, the electric vehicle comprising a controller configured to: When vehicle control software of the electric vehicle associated with first control software of at least one first supply device among the plurality of supply devices is stored in a server capable of communicating with the electric vehicle, checking a support relationship between the vehicle control software and second control software of a second supply device among the plurality of supply devices that is used by the electric vehicle at a higher frequency than the first supply device, and When there is no support relationship, reception of the vehicle control software via communication with the server or update of the vehicle control software based on the electric vehicle after receiving the vehicle control software is restricted.

2. The electric vehicle according to claim 1, wherein: The controller is configured to, when the supporting relationship exists, perform reception of the vehicle control software via communication with the server and update of the vehicle control software of the electric vehicle based on the reception of the vehicle control software.

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

4. The electric vehicle according to claim 1 or 2, 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 supply devices are configured to supply hydrogen as the energy.

5. The electric vehicle according to any one of claims 1 to 4, wherein: The version of the first control software is newer than the version of the second control software.

6. An energy supply device for supplying energy to an electric vehicle, the energy supply device comprising a control unit, the control unit being configured to: When the second control software of the energy supply device is stored in a server capable of communicating with the energy supply device, a support relationship between the second control software and the vehicle control software of the electric vehicle is checked, wherein, the second control software is more recent than first control software of a different energy supply device associated with the vehicle control software, the different energy supply device being configured to supply the energy to the electric vehicle independently of the energy supply device and being used by the electric vehicle at a lower frequency than the energy supply device, and When there is no support relationship, reception of the second control software or updating of the second control software of the energy supply device based on reception of the second control software is restricted.

7. The energy supply device according to claim 6, wherein: The control unit is configured to, when the supporting relationship exists, perform reception of the second control software and update of the second control software of the energy supply device based on the reception of the second control software.

8. Energy supply system, including: a plurality of supply devices configured to supply energy; an electric vehicle configured to independently replenish said energy from each of said plurality of supply devices; as well as A server capable of communicating with the plurality of supply devices and the electric vehicle; wherein: The electric vehicle includes a controller configured to When vehicle control software of the electric vehicle associated with first control software of at least one first supply device among the plurality of supply devices is stored in the server, checking a support relationship between the vehicle control software and second control software of a second supply device among the plurality of supply devices that is used by the electric vehicle at a higher frequency than the first supply device, and When there is no support relationship, reception of the vehicle control software via communication with the server or update of the vehicle control software based on the electric vehicle after receiving the vehicle control software is restricted.

9. The energy supply system according to claim 8, wherein: The controller is configured to, when the supporting relationship exists, perform reception of the vehicle control software via communication with the server and update of the vehicle control software of the electric vehicle based on the reception of the vehicle control software.

Images