Power Transfer System

Abstract

To provide a technique capable of performing a power transfer according to a scenario using a vehicle.SOLUTION: A power transfer system 1 includes: a vehicle 50; an EVSE 40 that performs a power transfer with the vehicle 50; and a server unit 30 that controls the power transfer between the EVSE 40 and the vehicle 50. The server unit 30 suggests recommended behaviors for a user of the vehicle 50 based on the time between when the vehicle 50 is scheduled to start power transfer and when the vehicle 50 is scheduled to arrive at the EVSE40 and the time between when the vehicle 50 is scheduled to complete the power transfer and when the vehicle 50 is scheduled to depart from the EVSE40.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a power transfer system for transferring power. [Background technology]

[0002] Conventional power supply systems that rely on power generation by electric power companies and other electric utility companies are being reconsidered, and a system known as a Virtual Power Plant (VPP) is being considered that uses advanced energy management technology that utilizes the Internet of Things (IoT) to bundle multiple distributed energy resources (hereinafter also referred to as "Distributed Energy Resources (DERs)") and remotely and comprehensively control these DERs to make them function as if they were a single power plant. JP 2021-87261 A (Patent Document 1) discloses a VPP system in which an EV (Electric Vehicle) server controls the exchange of power with EVs (DERs) based on an adjustment request from a VPP server. [Prior art documents] [Patent documents]

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

[0004] According to the VPP system disclosed in Patent Document 1, an EV server can estimate an appropriate amount of power adjustment possible according to a future power transfer scenario based on past data on power transfer. However, in vehicles such as EVs, there are cases where power transfer cannot be carried out as planned due to sudden changes in the user's plans or road conditions such as traffic congestion.

[0005] The present disclosure has been made to solve the above-mentioned problems, and an object of the present disclosure is to provide a technology that enables power to be exchanged according to a scenario using a vehicle. [Means for solving the problem]

[0006] According to an aspect of the present disclosure, there is provided an electric power transfer system including a vehicle, an electric power transfer facility that transfers electric power to and from the vehicle, and a server device that controls the transfer of electric power between the electric power transfer facility and the vehicle. The server device proposes recommended actions to a user of the vehicle based on the time between a scheduled start time of the vehicle and a scheduled time of the vehicle's arrival at the electric power transfer facility, and the time between a scheduled end time of the vehicle and a scheduled time of the vehicle's departure from the electric power transfer facility. [Effects of the Invention]

[0007] According to the present disclosure, even if the timing at which a vehicle arrives at or departs from the power transfer facility does not conform to the power transfer scenario, recommended actions can be suggested to the vehicle user, allowing the vehicle to transfer power according to the scenario. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of a configuration of an electric power transfer system according to an embodiment. [Figure 2] 1 is a diagram for explaining an overview of a VPP system to which an electric power transfer system according to an embodiment is applied. [Figure 3] FIG. 1 is a diagram for explaining an example of a scenario for power transfer. [Figure 4] FIG. 2 is a diagram for explaining a calculation model stored in a server device according to an embodiment. [Figure 5] 4 is a flowchart showing a procedure of a process executed in the power transfer system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0010] [Configuration of the power transfer system] Fig. 1 is a diagram illustrating an example of the configuration of an electric power transfer system 1 according to an embodiment. As shown in Fig. 1, the electric power transfer system 1 includes an electric power grid PG, a vehicle 50, a server device 30, an EMS (Energy Management System) 60, an EVSE (Electric Vehicle Supply Equipment) 40, a smart meter 13, and a user terminal 80, and realizes a VPP through energy management using the vehicle 50.

[0011] The power grid PG is a power network provided by an electric utility such as a power company. The power grid PG is electrically connected to a plurality of EVSEs 40, and supplies power to each EVSE 40 and receives power from each EVSE 40.

[0012] Vehicle 50 is, for example, a battery electric vehicle (BEV) or a plug-in hybrid electric vehicle (PHEV). Vehicle 50 may be a personally owned vehicle (POV) or a vehicle managed by a mobility as a service (MaaS) provider. Vehicle 50 includes a battery 130, an electronic control unit (ECU) 150, a communication device 180, an inlet 110, and a charger / discharger 120.

[0013] The battery 130 includes a secondary battery such as a lithium-ion battery or a nickel-metal hydride battery. The secondary battery may be, for example, a battery pack in which a plurality of lithium-ion batteries are electrically connected to one another. The vehicle 50 can run using the power stored in the battery 130. The amount of power stored in the battery 130 is also referred to as the SOC (State Of Charge).

[0014] The ECU 150 is a computer including a processor, random access memory (RAM), and a storage device. The processor may be, for example, a microcontroller, a central processing unit (CPU), or a microprocessing unit (MPU). The processor has the function of executing various processes by executing programs, but some or all of these functions may be implemented using dedicated hardware circuits such as an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA). The term "processor" is not limited to processors in the narrow sense that execute processes using stored programs, such as a CPU or MPU, but may also include hardwired circuits such as an ASIC or FPGA. Therefore, the term "processor" can also be interpreted as a processing circuitry whose processes are predefined by computer-readable code and / or hardwired circuits. The RAM is a volatile memory, such as a dynamic random access memory (DRAM) or a static random access memory (SRAM), that functions as a working memory for temporarily storing data to be processed by the processor. The storage device is a non-volatile memory such as a ROM (Read Only Memory) or a flash memory, and stores not only the program but also various data used in the program (for example, maps, formulas, and various parameters). Note that ECU 150 may be configured on one chip or multiple chips.

[0015] The communication device 180 includes various communication I / Fs (interfaces). The ECU 150 is configured to be able to communicate with the user terminal 80 via the communication device 180.

[0016] The inlet 110 is configured to be connectable to a connector 43 of the charging cable 42, and receives power supplied from outside the vehicle 50 and supplies power to outside the vehicle 50 via the charging cable 42. For example, the vehicle 50 is placed in a state where it can be charged or discharged when the connector 43 of the charging cable 42 connected to the EVSE 40 is connected (plugged in) to the inlet 110 of the vehicle 50.

[0017] Charger / discharger 120 is disposed between inlet 110 and battery 130. Charger / discharger 120 includes a relay that switches between connection and disconnection of a power path from inlet 110 to battery 130, and a power conversion circuit (for example, a bidirectional converter). Each of the relay and the power conversion circuit included in charger / discharger 120 is controlled by ECU 150.

[0018] When the vehicle 50 is in a chargeable / dischargeable state, it is possible to perform external charging (i.e., charging the battery 130 with power supplied from the EVSE 40) and external discharging (i.e., discharging from the vehicle 50 to the EVSE 40). Power for external charging is supplied from the EVSE 40 to the inlet 110 via the charging cable 42. The charger / discharger 120 converts the power received by the inlet 110 into power suitable for charging the battery 130 and outputs the converted power to the battery 130. Power for external discharging is supplied from the battery 130 to the charger / discharger 120. The charger / discharger 120 converts the power supplied from the battery 130 into power suitable for external discharging and outputs the converted power to the inlet 110. When performing either external charging or external discharging, the ECU 150 controls the relay of the charger / discharger 120 to a closed state (connected state), and when performing neither external charging nor external discharging, the ECU 150 controls the relay of the charger / discharger 120 to an open state (disconnected state).

[0019] The server device 30 includes a control device 31, a storage device 32, and a communication device 33, and realizes, for example, some or all of the functions as a cloud-based server device.

[0020] The control device 31 is a computer including a processor and RAM. The processor may be, for example, a microcontroller, a CPU, or an MPU. The processor has the function of executing various processes by executing programs, but some or all of these functions may be implemented using dedicated hardware circuits such as ASICs or FPGAs. The term "processor" is not limited to processors in the narrow sense that execute processes using stored programs, such as CPUs or MPUs, but may also include hardwired circuits such as ASICs or FPGAs. Therefore, the term "processor" can also be interpreted as a processing circuitry whose processes are predefined by computer-readable code and / or hardwired circuits. RAM is a volatile memory, such as DRAM or SRAM, that functions as a working memory for temporarily storing data to be processed by the processor.

[0021] The storage device 32 is a storage device such as a non-volatile memory such as a ROM or flash memory, an SSD (solid state drive) or an HDD (hard disk drive), and stores not only programs but also various data used in the programs (e.g., maps, formulas, and various parameters).

[0022] The communication device 33 includes various communication I / Fs (interfaces). The control device 31 is configured to be able to communicate with the user terminal 80 via the communication device 33. For communication between the communication device 33 and the user terminal 80, wireless communication such as Wi-Fi or Bluetooth (registered trademark) may be applied.

[0023] The EMS 60 communicates with the EVSE 40 in accordance with instructions from the server device 30. The EMS 60 is, for example, a Home Energy Management System (HEMS), a Factory Energy Management System (FEMS), or a Building Energy Management System (BEMS). The server device 30 communicates with the EVSE 40 via the EMS 60, without directly communicating with the EVSE 40.

[0024] EVSE 40 is an example of "power transfer equipment." EVSE 40 is, for example, an AC power supply equipment capable of supplying AC power, in which case charger / discharger 120 of vehicle 50 has a circuit corresponding to the AC power supply equipment. EVSE 40 may also be a DC power supply equipment capable of supplying DC power, in which case charger / discharger 120 of vehicle 50 may have a circuit corresponding to the DC power supply equipment. EVSE 40 includes non-public EVSEs (e.g., home EVSEs) that are available only to specific users, and public EVSEs that are available to an unspecified number of users. EVSE 40 includes a control unit 41, a power supply circuit 44, and a charging cable 42.

[0025] The control unit 41 controls the power supply circuit 44 to supply power to the battery 130 of the vehicle 50 via the charging cable 42 and to receive power from the battery 130 of the vehicle 50 .

[0026] A charging cable 42 is connected to the power supply circuit 44. The power supply circuit 44 supplies power to the battery 130 of the vehicle 50 and receives power from the battery 130 of the vehicle 50 via the charging cable 42 under the control of the control unit 41.

[0027] The charging cable 42 may be always connected to the main body of the EVSE 40, or may be detachable from the main body of the EVSE 40. The charging cable 42 has a connector 43 at the tip and includes a power line inside.

[0028] The smart meter 13 is assigned to each consumer (e.g., an individual or a business) that uses electricity, and measures the amount of power adjustment at the consumer every predetermined time (e.g., 30 minutes). For example, the smart meter 13 measures the amount of power supplied from the power grid PG to the EVSE 40 or the amount of power supplied from the EVSE 40 to the power grid PG. The smart meter 13 transmits a signal including information indicating the measured amount of power adjustment to the server device 30. Note that instead of the smart meter 13, a watt-hour meter mounted on the vehicle 50 or a watt-hour meter built into the EVSE 40 may be used.

[0029] The above-described EVSE 40 and EMS 60 are installed in one home or business (for example, a factory or commercial facility). The smart meter 13 measures the amount of power adjustment that is adjusted between the power grid PG and the home or business.

[0030] The user terminal 80 is an information terminal capable of communicating with each of the server device 30 and the vehicle 50 via a network, such as a desktop personal computer (PC), a laptop PC, a smartphone, a smart watch, a wearable device, or a tablet PC. The user terminal 80 may be a portable terminal that the user can carry with them, or may be an information terminal installed in the vehicle 50, such as a navigation system.

[0031] Although not shown, the navigation system includes a processor, a storage device, a touch panel display, and a GPS (Global Positioning System) module. The storage device stores map information. The touch panel display accepts input from a user and displays maps and other information. The GPS module receives GPS signals from GPS satellites. The navigation system can identify the location of the vehicle 50 using the GPS signals. Based on the input from the user, the navigation system can perform a route search to find a driving route (e.g., the shortest route) from the current location of the vehicle 50 to the destination, and display the driving route found by the route search on the map on the touch panel display.

[0032] Predetermined application software (hereinafter also simply referred to as "app") is installed on the user terminal 80. The user terminal 80 is used by the user of the vehicle 50, and exchanges information with the server device 30 through the app. For example, the user can participate in the VPP by exchanging information with the server device 30 using the VPP app installed on the user terminal 80.

[0033] [VPP system overview] Fig. 2 is a diagram illustrating an overview of a VPP system to which an electric power transfer system 1 according to an embodiment is applied. As shown in Fig. 2, the electric power transfer system 1 includes an electric power company E1, a higher-level aggregator E2, a lower-level aggregator E3, and a plurality of vehicles 50A, 50B, and 50C. Each of the plurality of vehicles 50A, 50B, and 50C corresponds to the vehicle 50 shown in Fig. 1. In the example of Fig. 2, the electric power transfer system 1 includes an EMS 60 and a smart meter 13 corresponding to the vehicle 50A, and also includes an EMS 60 and a smart meter 13 (not shown) for each of the other vehicles 50B and 50C.

[0034] The electric power company E1 is an electric utility such as a power generation company or a power transmission and distribution company. In the example of FIG. 2 , the electric power company E1 serves as both a power generation company and a power transmission and distribution company. The electric power company E1 includes a power plant 11, a power transmission and distribution facility 12, and a server device 10. The electric power company E1 constructs a power grid PG using the power plant 11 and the power transmission and distribution facility 12, and maintains and manages the power grid PG using the server device 10. The power plant 11 includes a power generation device for generating electricity, and supplies the power generated by the power generation device to the power transmission and distribution facility 12. The power plant 11 may use any known power generation method, such as thermal power generation, hydroelectric power generation, wind power generation, nuclear power generation, or solar power generation. The power transmission and distribution facility 12 includes transmission lines, substations, and distribution lines, and transmits and distributes the power supplied from the power plant 11.

[0035] An operator that aggregates DERs and performs energy management is also referred to as an "aggregator." For example, a power company E1 can adjust power in a power grid PG by working with an aggregator. The upper aggregator E2 includes multiple server devices (e.g., server devices 20A and 20B). The multiple server devices included in the upper aggregator E2 belong to different operators. The lower aggregator E3 includes multiple server devices (e.g., server devices 30A and 30B). The multiple server devices included in the lower aggregator E3 belong to different operators. Note that each server device included in the lower aggregator E3 shown in FIG. 2 corresponds to the server device 30 shown in FIG. 1. Hereinafter, unless otherwise distinguished, each server device included in the upper aggregator E2 will also be referred to as a "server device 20," and each server device included in the lower aggregator E3 will also be referred to as a "server device 30." The number of server devices 20 and the number of server devices 30 are independent of each other and can be set arbitrarily.

[0036] In the example of FIG. 2, one server device 10 requests energy management from multiple server devices 20 that are upper aggregators E2, and each server device 20 that receives a request from the server device 10 requests energy management from multiple server devices 30 that are lower aggregators E3. Furthermore, each server device 30 that receives a request from the server device 20 requests energy management from multiple DER users (e.g., users of vehicles 50). The electric power company E1 can use such a hierarchical structure (tree structure) to request energy management from many users. Note that the upper aggregator E2 and the lower aggregator E3 may be configured to function using the same server device.

[0037] A request from the electric power company E1 (server device 10) to the upper aggregator E2 (server device 20), a request from the upper aggregator E2 (server device 20) to the lower aggregator E3 (server device 30), and a request from the lower aggregator E3 (server device 30) to each user are also referred to as a DR (demand response) request. DR refers to changing the power demand pattern by controlling DERs to adjust the amount of power transferred. DR that actively uses power using DERs to increase power demand for each user is also referred to as "increasing DR." On the other hand, DR that reduces power demand for each user by saving or discharging power is also referred to as "decreasing DR."

[0038] The server device 30 performs energy management in its jurisdiction area. The area under the jurisdiction of the server device 30 may be a town (for example, a smart city), a factory, or a university campus. The lower aggregator E3 concludes energy management contracts with DER users in the jurisdiction area of ​​the server device 30. Users who have concluded such contracts can receive predetermined incentives from the lower aggregator E3 by performing energy management using DERs in accordance with a DR request from the lower aggregator E3. On the other hand, users who do not comply with the DR request despite agreeing to comply with the DR request from the lower aggregator E3 are subject to a predetermined penalty under the above-mentioned contract. DERs and DER users who are obligated to perform energy management under the contract are registered in the server device 30.

[0039] When the server device 30 receives a DR request from the server device 20, it selects a DER to respond to the DR request from among the DERs registered in the server device 30. The DER selected in this manner is also referred to as an "EMDER." After selecting an EMDER, the server device 30 transmits a command to the user of each EMDER. Based on the command received from the server device 30, the user of each EMDER performs energy management (for example, adjusting supply and demand in the power grid PG) in accordance with the DR request from the server device 30.

[0040] The amount of power adjustment for each EMDER (for example, charging power and / or discharging power in a predetermined period) is measured by the smart meter 13. The amount of power adjustment measured by the smart meter 13 is transmitted to the server device 10. In the example of FIG. 2, the server device 30 acquires the amount of power adjustment measured by the smart meter 13 via the server device 10, but the server device 30 may acquire the amount of power adjustment directly from the smart meter 13. The amount of power adjustment measured by the smart meter 13 may be used to calculate an incentive.

[0041] In the power transfer system 1 configured as described above, the server device 30 selects at least one vehicle to make a DR request from among the registered vehicles 50 in order to fulfill the power adjustment amount of power transfer in accordance with a request from the power company E1 (server device 10) or the upper aggregator E2 (server device 20), and transmits the DR request to the user terminal 80 of the user of the at least one selected vehicle 50. When the user who received the DR request accepts the DR request using the user terminal 80, the server device 30 schedules power transfer using the at least one selected vehicle 50 in a DR block time reserved for executing the power transfer (DR request). When the vehicle 50 arrives at a location where the EVSE 40 is installed during the DR block time and is ready to transfer power, the server device 30 can transmit a DR signal to the EMS 60 to cause the vehicle 50 of the user who accepted the DR request to exchange power with the EVSE 40 so as to fulfill the power adjustment amount of the DR request.

[0042] The term "power transfer" is a concept that includes at least one of supplying power from the power grid PG to the vehicle 50 by charging the battery 130 of the vehicle 50 using the EVSE 40, and supplying power from the vehicle 50 to the power grid PG by discharging the battery 130 of the vehicle 50 using the EVSE 40. For example, when the server device 30 requests an upward DR from the user of the vehicle 50, power transfer occurs in which power is supplied from the power grid PG to the vehicle 50 or the supplied power is increased. On the other hand, when the server device 30 requests a downward DR from the user of the vehicle 50, power transfer occurs in which the power supplied from the power grid PG to the vehicle 50 is decreased or, conversely, power is supplied from the vehicle 50 to the power grid PG.

[0043] [Example of a power transfer scenario] Fig. 3 is a diagram for explaining an example of a scenario for transferring power. In Fig. 3, a timing chart with time on the horizontal axis shows each event and also explains the time between each event.

[0044] 3 shows an example in which a vehicle 50 carrying a user returns to the user's home and arrives at the EVSE 40 installed at the home, and then the vehicle 50 exchanges power with the EVSE 40 during the DR block time, and then the vehicle 50 carrying the user again departs from the home (EVSE 40). For example, consider a situation in which the vehicle 50 returns home from an outside location, charges using the EVSE 40 at home, and the fully charged vehicle 50 departs from the home again.

[0045] The time between the start timing T1 at which the DR block reserved for executing power transfer (DR request) starts and the arrival timing T2 at which the vehicle 50 arrives at the EVSE 40 is indicated by the arrival time difference "Tarr." The time during which the vehicle 50 transfers power to and from the EVSE 40 is indicated by the power transfer time "Tdsoc." The time between the start timing T1 at which the DR block starts and the end timing T4 at which the DR block ends is indicated by the DR block time "Tdr." The time between the end timing T4 at which the DR block time Tdr ends and the departure timing T5 at which the vehicle 50 departs from the EVSE 40 is indicated by the departure time difference "Tdep." The time obtained by subtracting the power transfer time Tdsoc from the DR block time Tdr is indicated by the DR block remaining time "Tdr-Tdsoc."

[0046] The user of the vehicle 50 who has accepted the DR request is obligated to ensure the power transfer time Tdsoc within the DR block time Tdr. For example, when the arrival time difference Tarr is equal to or less than the remaining DR block time Tdr - Tdsoc, the server device 30 can ensure the power transfer time Tdsoc within the DR block time Tdr. Furthermore, the server device 30 fulfills the DR request by executing within the DR block the power transfer scheduled to be performed outside the DR block. That is, the server device 30 fulfills the DR request by replacing the amount of power transfer scheduled outside the DR block with the amount of power adjustment within the DR block. For example, the server device 30 fulfills the DR request by advancing the power transfer scheduled from the end of the DR block time Tdr until the vehicle 50 departs the EVSE 40 and executing it within the DR block. This fulfills the DR request by replacing the amount of power transfer scheduled from the end of the DR block time Tdr until the vehicle 50 departs the EVSE 40 with the amount of power adjustment within the DR block. Therefore, the server device 30 can satisfy the DR request when the departure time difference Tdep is equal to or greater than the power transfer time Tdsoc.

[0047] However, in a vehicle 50 such as an EV, power exchange may not be performed as scheduled due to various factors such as a sudden change in the user's plans or road conditions such as traffic congestion. In such cases, the server device 30 may not be able to satisfy the power exchange adjustment amount requested by the power company E1 or the upper aggregator E2.

[0048] For example, it is assumed that the vehicle 50 arrives at the EVSE 40 significantly later than scheduled. In such a case, if the arrival time difference Tarr becomes larger than the remaining DR block time Tdr-Tdsoc, the server device 30 cannot secure the power transfer time Tdsoc within the DR block time Tdr. Such user behavior may reduce the amount of power adjustment in power transfer.

[0049] Alternatively, it is assumed that the vehicle 50 departs from the EVSE 40 much earlier than planned. In such a case, if the departure time difference Tdep becomes less than the power transfer time Tdsoc, the server device 30 cannot secure the power transfer time Tdsoc within the DR block time Tdr. Such user behavior may reduce the amount of power adjustment in power transfer.

[0050] Therefore, in the electric power transfer system 1 according to the embodiment, the server device 30 is configured to propose recommended actions to the user of the vehicle 50 based on the arrival time difference Tarr between the start timing T1 when the vehicle 50 is scheduled to start electric power transfer (i.e., the start timing of the DR block) and the arrival timing T2 when the vehicle 50 is scheduled to arrive at the EVSE 40, and the departure time difference Tdep between the end timing T4 when the vehicle 50 is scheduled to end electric power transfer (i.e., the end timing of the DR block) and the departure timing T5 when the vehicle 50 is scheduled to depart from the EVSE 40. Hereinafter, the processing of the server device 30 in the electric power transfer system 1 according to the embodiment will be described.

[0051] [Calculation model] 4 is a diagram illustrating a calculation model stored in the server device 30 according to the embodiment. The server device 30 stores data corresponding to the calculation model shown in FIG. 4 in the storage device 32, and uses the calculation model to propose recommended actions to the user of the vehicle 50 based on the arrival time difference Tarr and the departure time difference Tdep.

[0052] 4, the calculation model is configured by a coordinate plane with the departure time difference Tdep on the horizontal axis and the arrival time difference Tarr on the vertical axis. By inputting input data into the calculation model, the server device 30 determines quadrants 1 to 4 corresponding to four regions divided by orthogonal coordinate axes on the coordinate plane, and outputs one quadrant from quadrants 1 to 4.

[0053] The input data includes DR block information related to the DR block time, user behavior information related to the user's behavior, charging rate information related to the charging rate of the vehicle 50, EVSE information related to the EVSE 40, and battery information related to the battery capacity of the vehicle 50.

[0054] The DR block information includes information regarding the scheduled start timing (scheduled start time) of the DR block and information regarding the scheduled end timing (scheduled end time) of the DR block. The server device 30 determines the DR block information after the user of the vehicle 50 accepts the DR request. The server device 30 can calculate the DR block time Tdr based on the DR block information.

[0055] The user behavior information includes information regarding the planned arrival timing (estimated arrival time) of the vehicle 50 at the EVSE 40 and information regarding the planned departure timing (estimated departure time) of the vehicle 50 from the EVSE 40. The server device 30 acquires current or past GPS information received by a navigation system installed in the vehicle 50 that has accepted the DR request, and calculates the user behavior information based on the GPS information. The server device 30 may also acquire traffic congestion information and calculate the user behavior information based on the traffic congestion information. The server device 30 can calculate the arrival timing of the vehicle 50 at the EVSE 40 and calculate the arrival time difference Tarr based on the user behavior information. The server device 30 can also calculate the departure timing of the vehicle 50 from the EVSE 40 and calculate the departure time difference Tdep based on the user behavior information.

[0056] The charging rate information includes information about the SOC when the vehicle 50 arrives at the EVSE 40 and information about the SOC when the vehicle 50 departs from the EVSE 40. The server device 30 calculates the charging rate information based on the SOC acquired from the vehicle 50 and the power adjustment amount in the power exchange requested for DR.

[0057] The EVSE information includes information related to the charging power [kW] or discharging power [kW] of the EVSE 40. The server device 30 acquires the EVSE information from the EVSE 40.

[0058] The battery information includes information regarding the capacity [kWh] at which the battery 130 of the vehicle 50 is fully charged. The server device 30 acquires the battery information from the vehicle 50. The server device 30 can calculate the power transfer time Tdsoc based on the charging rate information, the EVSE information, the battery information, and the like.

[0059] The server device 30 inputs input data into the calculation model, and thereby determines quadrants 1 to 4 corresponding to four regions divided by the orthogonal coordinate axes on the coordinate plane.

[0060] Specifically, in a coordinate plane corresponding to the calculation model, the server device 30 plots the time from the end timing T4 when the DR block ends to the departure timing T5 when the vehicle 50 departs from the EVSE 40 on the horizontal axis, and the time from the start timing T1 when the DR block starts to the arrival timing T2 when the vehicle 50 arrives at the EVSE 40 on the vertical axis. Furthermore, in the coordinate plane, the server device 30 draws a vertical axis perpendicular to the horizontal axis of the coordinate axes at a position corresponding to the power transfer time Tdsoc and a vertical axis corresponding to the DR block time Tdr. Furthermore, in the coordinate plane, the server device 30 draws a horizontal axis perpendicular to the vertical axis of the coordinate axes at a position corresponding to the DR block remaining time Tdr-Tdsoc and a horizontal axis corresponding to the DR block time Tdr. Furthermore, in the coordinate plane, the server device 30 draws a diagonal axis according to the linear function Tarr = Tdep + (Tdr-Tdsoc). The server device 30 can configure four regions, quadrants 1 to 4, on the coordinate plane corresponding to the calculation model using the multiple axes drawn as described above.

[0061] The server device 30 outputs one quadrant from quadrants 1 to 4. Specifically, when the departure time difference Tdep is equal to or greater than the power transfer time Tdsoc and the arrival time difference Tarr is greater than the DR block remaining time Tdr-Tdsoc, the server device 30 outputs quadrant 1 according to the calculation model.

[0062] That is, in this example, there is no problem because the power transfer time Tdsoc can be secured for the timing when the vehicle 50 departs from the EVSE 40 (departure timing T5 in Figure 3), but the power transfer time Tdsoc cannot be secured for the timing when the vehicle 50 arrives at the EVSE 40 (arrival timing T2 in Figure 3).

[0063] When the server device 30 outputs quadrant 1 using the calculation model, the server device 30 suggests to the user of the vehicle 50 that the timing at which the vehicle 50 arrives at the EVSE 40 be advanced. By making such a suggestion to the user, the server device 30 can advance the timing at which the vehicle 50 arrives at the EVSE 40 and make the arrival time difference Tarr equal to or less than the DR block remaining time Tdr-Tdsoc, thereby ensuring the power transfer time Tdsoc.

[0064] When the departure time difference Tdep is equal to or greater than the power transfer time Tdsoc and the arrival time difference Tarr is equal to or less than the DR block remaining time Tdr-Tdsoc, the server device 30 outputs quadrant 2 according to the calculation model.

[0065] That is, in this example, there is no problem at the timing when the vehicle 50 departs from the EVSE 40 (departure timing T5 in Figure 3) because the power transfer time Tdsoc can be secured, and there is also no problem at the timing when the vehicle 50 arrives at the EVSE 40 (arrival timing T2 in Figure 3) because the power transfer time Tdsoc can be secured.

[0066] When the server device 30 outputs quadrant 2 according to the calculation model, the server device 30 suggests to the user of the vehicle 50 that the amount of power adjustment in the power exchange be increased. For example, the server device 30 suggests to the user of the vehicle 50 that the target SOC in the power exchange be increased, or that the SOC be decreased at the start of the power exchange (or when the vehicle arrives at the EVSE 40). By making such suggestions to the user, the server device 30 can ensure that the free capacity of the battery 130 is sufficient for charging from the EVSE 40 during the power exchange, and can more reliably satisfy the amount of power adjustment in the power exchange in accordance with a request from the electric power company E1 (server device 10) or the upper aggregator E2 (server device 20).

[0067] When the departure time difference Tdep is less than the power transfer time Tdsoc and the arrival time difference Tarr is equal to or less than the DR block remaining time Tdr-Tdsoc, the server device 30 outputs quadrant 3 according to the calculation model.

[0068] In other words, in this example, the power transfer time Tdsoc cannot be secured for the timing when the vehicle 50 departs from the EVSE 40 (departure timing T5 in Figure 3), but there is no problem because the power transfer time Tdsoc can be secured for the timing when the vehicle 50 arrives at the EVSE 40 (arrival timing T2 in Figure 3).

[0069] When the server device 30 outputs quadrant 3 using the calculation model, the server device 30 proposes to the user of the vehicle 50 to delay the timing at which the vehicle 50 departs from the EVSE 40. By making such a proposal to the user, the server device 30 can delay the timing at which the vehicle 50 departs from the EVSE 40 to make the departure time difference Tdep equal to or greater than the power transfer time Tdsoc, thereby ensuring the power transfer time Tdsoc.

[0070] If the departure time difference Tdep is less than the power transfer time Tdsoc and the arrival time difference Tarr is greater than the DR block remaining time Tdr-Tdsoc, the server device 30 outputs quadrant 4 according to the calculation model.

[0071] In other words, in this example, the power transfer time Tdsoc cannot be secured when the vehicle 50 departs from the EVSE 40 (departure time T5 in Figure 3), and the power transfer time Tdsoc cannot be secured when the vehicle 50 arrives at the EVSE 40 (arrival time T2 in Figure 3).

[0072] When quadrant 4 is output by the calculation model, the server device 30 proposes to the user of the vehicle 50 that the timing at which the vehicle 50 departs from the EVSE 40 be delayed. By making such a proposal to the user, the server device 30 can delay the timing at which the vehicle 50 departs from the EVSE 40 to make the departure time difference Tdep equal to or greater than the power transfer time Tdsoc, thereby ensuring the power transfer time Tdsoc. Furthermore, after the server device 30 transitions from quadrant 4 to quadrant 1 by making such a proposal to the user, the server device 30 proposes to the user of the vehicle 50 that the timing at which the vehicle 50 arrives at the EVSE 40 be advanced as a proposal corresponding to quadrant 1. By making such a proposal to the user, the server device 30 can advance the timing at which the vehicle 50 arrives at the EVSE 40 to make the arrival time difference Tarr equal to or less than the DR block remaining time Tdr-Tdsoc, thereby ensuring the power transfer time Tdsoc.

[0073] Alternatively, when the server device 30 outputs quadrant 4 using the calculation model, the server device 30 proposes to the user of the vehicle 50 that the timing at which the vehicle 50 arrives at the EVSE 40 be advanced. By making such a proposal to the user, the server device 30 can advance the timing at which the vehicle 50 arrives at the EVSE 40 and make the arrival time difference Tarr equal to or less than the DR block remaining time Tdr-Tdsoc, thereby ensuring the power transfer time Tdsoc. Furthermore, after transitioning from quadrant 4 to quadrant 3 using such a proposal to the user, the server device 30 proposes to the user of the vehicle 50 that the timing at which the vehicle 50 departs from the EVSE 40 be delayed as a proposal corresponding to quadrant 3. By making such a proposal to the user, the server device 30 can delay the timing at which the vehicle 50 departs from the EVSE 40 and make the departure time difference Tdep equal to or greater than the power transfer time Tdsoc, thereby ensuring the power transfer time Tdsoc.

[0074] In addition, the server device 30 may suggest to the user that the vehicle 50 transition from quadrant 4 to quadrant 2 via quadrant 1 or quadrant 3, and then suggest to the user of the vehicle 50 that the amount of power adjustment in power exchange be increased as a suggestion corresponding to quadrant 2.

[0075] [Processing procedure executed in the power transfer system] Fig. 5 is a flowchart showing the procedure of processing executed in the electric power transfer system 1 according to the embodiment. Fig. 5 shows processing executed by the server device 30, processing executed by the user terminal 80, and processing executed by the EMS 60. Note that, hereinafter, step will be abbreviated as "S".

[0076] 5, the server device 30 determines whether or not a DR request has been received from the electric power company E1 or the upper aggregator E2 (S301). If a DR request has been received (YES in S301), the server device 30 determines a combination of vehicles 50 that will make the DR request in response to the DR request from the electric power company E1 or the upper aggregator E2 (S302).

[0077] The server device 30 transmits a DR request signal including information requesting DR to the user terminal 80 of the user of the determined vehicle 50 (S303). The DR request signal includes, for example, information indicating the start timing and end timing of the DR block, information indicating whether the DR is an up-DR or down-DR, and information indicating the charge power / discharge power per vehicle 50 requested by the DR.

[0078] Meanwhile, the user terminal 80 determines whether or not a DR request signal has been received from the server device 30 in the VPP application (S801). When the user terminal 80 receives the DR request signal from the server device 30 (YES in S801), the user terminal 80 displays a screen on the display for confirming whether or not to accept the DR request (S802). The screen for confirming whether or not to accept the DR request includes, for example, an icon image of a button for inputting the intention to accept.

[0079] If the user terminal 80 has not received a DR request signal from the server device 30 (NO in S801), or after S802, the user terminal 80 determines whether the DR request has been approved on a screen for confirming whether to approve the DR request (S803). If the DR request has been approved (YES in S803), the user terminal 80 transmits an approval signal including information indicating that the DR request has been approved to the server device 30 (S804).

[0080] Meanwhile, the server device 30 determines whether or not it has received an approval signal from the user terminal 80 (S304). If it has received an approval signal from the user terminal 80 (YES in S304), the server device 30 adds information about the user of the user terminal 80 that sent the approval signal, the vehicle 50, and the like to the DR request list (S305).

[0081] If the server device 30 has not received an approval signal from the user terminal 80 (NO in S304), or after S305, the server device 30 determines whether the timing has come to propose a recommended action to the user of the vehicle 50 (S306).

[0082] When the suggestion timing arrives (YES in S306), the server device 30 acquires input data (S307). The server device 30 inputs the input data into the calculation model (S308). The server device 30 uses the calculation model to output one quadrant based on the input data (S309). For example, as described with reference to FIG. 4, the server device 30 inputs the input data into the calculation model to determine quadrants 1 to 4 corresponding to four regions divided by orthogonal coordinate axes, and outputs one quadrant from quadrants 1 to 4. The server device 30 transmits a suggestion signal including information suggesting a recommended action to the user of the vehicle 50 based on the determined one quadrant to the user terminal 80 (S310).

[0083] Meanwhile, the user terminal 80 determines whether or not a proposal signal has been received from the server device 30 (S805). If the user terminal 80 receives a proposal signal from the server device 30 (YES in S805), the user terminal 80 displays a screen showing the action proposed by the server device 30 on the display (S806). This allows the user of the vehicle 50 to take action, such as arriving at the EVSE 40 earlier or departing from the EVSE 40 later, in accordance with the proposal from the server device 30 displayed on the user terminal 80.

[0084] The server device 30 may transmit a suggestion signal not only to the user terminal 80 but also to the navigation system of the vehicle 50. In this case, the user can take action such as advancing the timing of arriving at the EVSE 40 or delaying the timing of departing from the EVSE 40, in accordance with the suggestion from the server device 30 displayed on the display of the navigation system of the vehicle 50.

[0085] If the user terminal 80 has not received a proposal signal from the server device 30 (NO in S805), or after S806, the user terminal 80 returns the process to be executed to the calling upper process.

[0086] After S310, the server device 30 determines whether the timing to start the DR block has arrived and whether the DR request can be executed while the vehicle 50 is connected to the EVSE 40 (S311). If the DR request can be executed (YES in S311), the server device 30 transmits a DR signal including information for executing the DR request to the EMS 60 corresponding to the EVSE 40 to which the vehicle 50, which is ready to exchange power, is connected (S312).

[0087] If the server device 30 cannot execute the DR request (NO in S311), or after S312, the server device 30 returns the process to be executed to the calling upper process.

[0088] Meanwhile, the EMS 60 corresponding to the vehicle 50 that accepted the DR request determines whether or not it has received a DR signal from the server device 30 (S601). If the EMS 60 has received a DR signal from the server device 30 (YES in S601), the EMS 60 controls the EVSE 40 and the vehicle 50 to charge or discharge the battery 130 of the vehicle 50 in accordance with the DR signal (S602).

[0089] For example, when the DR request indicated by the DR signal is an upward DR, the EMS 60 transmits a signal to the EVSE 40 and the vehicle 50 to start charging the vehicle 50 according to the power adjustment amount indicated by the DR signal. As a result, charging of the vehicle 50 is started so as to satisfy the specified power adjustment amount.

[0090] Furthermore, when the DR request indicated by the DR signal is a downward DR, the EMS 60 transmits a signal to the EVSE 40 and the vehicle 50 to start discharging from the vehicle 50 in accordance with the power adjustment amount indicated by the DR signal. This causes discharging from the vehicle 50 to start so as to satisfy the specified power adjustment amount.

[0091] If the EMS 60 has not received a DR signal from the server device 30 (NO in S601), or after S602, the EMS 60 returns to the calling upper process.

[0092] In this way, the power transfer system 1 can propose recommended actions to the user of the vehicle 50 based on the arrival time difference Tarr between the planned start timing when the vehicle 50 starts power transfer and the planned arrival timing when the vehicle 50 arrives at the EVSE 40, and the departure time difference Tdep between the planned end timing when the vehicle 50 ends power transfer and the planned departure timing when the vehicle 50 departs from the EVSE 40. As a result, even if the timing when the vehicle 50 arrives at the EVSE 40 or the timing when the vehicle 50 departs from the EVSE 40 does not conform to the power transfer scenario, the power transfer system 1 can perform power transfer using the vehicle 50 according to the scenario by proposing recommended actions to the user of the vehicle 50.

[0093] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is defined by the claims, not by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0094] 1 Power transfer system, 10, 20, 20A, 20B, 30, 30A, 30B Server equipment, 11 Power plant, 12 Power transmission and distribution equipment, 13 Smart meter, 31 Control device, 32 Storage device, 33 Communication device, 41 Control unit, 42 Charging cable, 43 Connector, 44 Power supply circuit, 50, 50A, 50B, 50C Vehicle, 80 User terminal, 110 Inlet, 120 Charger / discharger, 130 Battery, 180 Communication equipment, E1 Power company, E2 Upper aggregator, E3 Lower aggregator, PG Power system.

Claims

1. A power transfer system for transferring power, Vehicles and an electric power transfer facility for transferring electric power between the vehicle and the electric power transfer facility; a server device that controls the power exchange between the power exchange facility and the vehicle so as to satisfy a power adjustment amount of the power exchange within a block time that has been secured in advance; a user terminal used by a user of the vehicle; the server device transmits to the user terminal a proposal signal including information suggesting to the user to adjust the arrival timing or the departure timing based on an arrival time difference between a start timing of the block time and an arrival time at which the vehicle is scheduled to arrive at the power transfer facility and a departure time difference between an end timing of the block time and a departure time at which the vehicle is scheduled to depart from the power transfer facility; The user terminal displays a screen showing the action proposed by the server device on a display based on the proposal signal.

2. The power transfer system described in claim 1, wherein the server device determines the information to be included in the proposed signal based on the arrival time difference, the departure time difference, the power transfer time required for the power transfer, and the remaining block time obtained by subtracting the power transfer time from the block time when the arrival time difference is the power transfer system.

3. The power transfer system described in Claim 2, wherein the server device includes information in the proposal signal suggesting to the user that the arrival timing be advanced if the departure time difference is greater than or equal to the power transfer time and the arrival time difference is greater than the remaining block time.

4. The power transfer system described in Claim 2, wherein the server device includes information in the proposal signal suggesting to the user that the departure timing be delayed if the departure time difference is less than the power transfer time and the arrival time difference is less than the remaining block time.

5. The power transfer system described in claim 2, wherein the server device includes information in the proposal signal suggesting to the user that the arrival time be advanced or the departure time be delayed when the departure time difference is less than the power transfer time and the arrival time difference is greater than the remaining block time.

Images