Power management system and power management method

Abstract

To increase an opportunity to use a vehicle for exchange of power.SOLUTION: A VGI system is a system that exchanges power between a power system of a power company and a BEV, and comprises: a plurality of BEVs; an EVSE that includes a charging cable and a connector; and a management server that manages the exchange of power. The EVSE includes a specific EVSE that can use a specific vehicle for which use of the EVSE is permanently recognized among from the BEVs. The management server executes: processing of temporally permitting the user of the specific EVSE of a non-specific vehicle under a condition that power is exchanged with a power company by the specific EVSE using the non-specific vehicle that is different from the specific vehicle (S113); and processing of applying an incentive to a user of the non-specific vehicle or an administrator of the specific EVSE under the condition that the non-specific vehicle exchanges power with the power company (S124).SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present disclosure relates to a power management system and a power management method, and in particular to a power management system that exchanges power between a power supply and demand system of a power trading partner and a vehicle, and a power management method in a power management system that exchanges power between a power supply and demand system of a power trading partner and a vehicle. [Background technology]

[0002] In a conventional information provision system that provides information to occupants via an on-board device mounted on an electric vehicle, the on-board device has a notification means that predicts the congestion state of a candidate charging station, which is a charging station that can be reached based on the remaining battery power of the vehicle, at the time the vehicle arrives at the candidate charging station based on position information and remaining battery power of other electric vehicles that are present in the vicinity of the candidate charging station, and notifies the occupants of the congestion state of the candidate charging station (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-013893 Summary of the Invention [Problem to be solved by the invention]

[0004] When using electric vehicles as a power resource, it is conceivable that not only public charging stations but also charging stations for private use by individual businesses will be utilized.

[0005] This disclosure has been made to solve such problems, and its purpose is to provide a power management system and a power management method that can increase the opportunities for using vehicles to exchange power. [Means for solving the problem]

[0006] The power management system disclosed herein is a system for exchanging power between vehicles and an electric power supply and demand system of an electric power trading partner. The power management system includes a plurality of vehicles, a plurality of charging / discharging devices each including a cable through which electric power is exchanged with the vehicles and a connector for connecting the cable to the vehicle, and a server for managing the exchange of power. The charging / discharging devices include specific charging / discharging equipment that can be used by specific vehicles that are permanently authorized to use the charging / discharging equipment. The server executes processing to temporarily permit a non-specific vehicle, different from the specific vehicle, to use the specific charging / discharging equipment to exchange power with a trading partner, on the condition that the non-specific vehicle uses the specific charging / discharging equipment, and executes processing to grant an incentive to a user of the non-specific vehicle or an administrator of the specific charging / discharging equipment, on the condition that the non-specific vehicle has exchanged power with the trading partner.

[0007] With this configuration, even non-specified vehicles, which are different from specified vehicles that are permanently authorized to use specified charging / discharging facilities, can use the specified charging / discharging facilities to exchange power with the power supply and demand system of the power trading partner. As a result, it is possible to provide an energy management system that can increase the opportunities to use vehicles for energy exchange.

[0008] The server may provide an incentive to the manager depending on the size or performance of the specific charging / discharging equipment.

[0009] With this configuration, managers who provide specific charging / discharging equipment for use in vehicle power exchange can be motivated to provide larger-scale, higher-performance charging / discharging equipment.

[0010] In response to a request from a user of a non-specific vehicle to search for specific charging / discharging equipment, the server may search for specific charging / discharging equipment that meets the user's wishes and transmit the search results to the user.

[0011] According to this configuration, it is possible to notify a user of a non-specific vehicle of a specific charging / discharging facility that meets the user's desire, thereby improving user convenience.

[0012] The server may search for the specific charging / discharging facility on days when the specific vehicle does not use the facility. With this configuration, the specific charging / discharging facility can be provided to non-specific vehicles on days when the specific vehicle does not use the facility.

[0013] According to another aspect of the present disclosure, a power management method is a method for managing power in a power management system that exchanges power between vehicles and an power supply and demand system of an power trading partner. The power management system includes a plurality of vehicles, a plurality of charging / discharging devices each including a cable through which power is exchanged between the vehicles and a connector for connecting the cable to the vehicle, and a server that manages the exchange of power. The charging / discharging devices include a specific charging / discharging facility that can be used by a specific vehicle that is permanently authorized to use the charging / discharging facility. The power management method includes the steps of: executing a process by the server to temporarily permit a non-specific vehicle, different from the specific vehicle, to use the specific charging / discharging facility to exchange power with the trading partner, on the condition that the non-specific vehicle exchanges power using the specific charging / discharging facility; and executing a process by the server to grant an incentive to a user of the non-specific vehicle or an administrator of the specific charging / discharging facility, on the condition that the non-specific vehicle has exchanged power with the trading partner.

[0014] With this configuration, it is possible to provide a power management method that can increase opportunities to utilize vehicles for power exchange. [Effects of the Invention]

[0015] According to this disclosure, it is possible to provide a power management system and a power management method that can increase opportunities to utilize vehicles for power exchange. [Brief explanation of the drawings]

[0016] [Figure 1]1 is a diagram showing the configuration of a VGI system according to this embodiment. [Figure 2] This is a communication system diagram of the VGI system. [Figure 3] FIG. 1 is a diagram illustrating the configuration of a BEV. [Figure 4] 1 is a diagram showing an input device and a notification device mounted near the driver's seat of a BEV. [Figure 5] FIG. 1 is a diagram for explaining a BEV connected to a public EVSE. [Figure 6] FIG. 2 is a diagram for explaining an outline of a search for a parking lot equipped with an EVSE in the first embodiment. [Figure 7] 10 is a flowchart showing the flow of processing for searching for a parking lot having an EVSE that can participate in a VPP in the VGI system according to this embodiment. [Figure 8] FIG. 10 is a diagram for explaining an outline of a search for a parking lot equipped with an EVSE in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0017] [First embodiment] 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 designated by the same reference numerals, and description thereof will not be repeated.

[0018] In recent years, the power system, which relies on large-scale power plants (centralized energy resources) owned by electric power companies, has been reconsidered, and efforts are underway to build a system that utilizes the energy resources owned by individual consumers (hereinafter referred to as "DSR (Demand Side Resources)") in the power system.DSR functions as a distributed energy resource (hereinafter referred to as "DER (Distributed Energy Resources)").

[0019] VPPs (Virtual Power Plants) have been proposed as a mechanism for utilizing DSR in power systems. VPPs use advanced energy management technology that utilizes the Internet of Things (IoT) to bundle a large number of DERs (such as DSRs) and remotely and centrally control them, making them function as if they were a single power plant. In VPPs, the electric utility that bundles DERs and provides energy management services is called an "aggregator." For example, by collaborating with an aggregator, electric power companies can adjust the balance of supply and demand for electricity through demand response (DR).

[0020] In the VGI (Vehicle Grid Integration) system according to this embodiment, a vehicle equipped with a power storage device (more specifically, an electric vehicle (hereinafter referred to as a BEV (Battery Electric Vehicle)) and a plug-in hybrid vehicle (a plug-in hybrid electric vehicle (PHEV (Plug-in Hybrid Electric Vehicle) or other electric vehicle capable of external charging and discharging) are employed as a DSR for realizing a VPP.

[0021] 1 is a diagram showing the configuration of a VGI system according to this embodiment. Referring to Fig. 1, the VGI system 1 includes an electric power company E1, a higher-level aggregator E2, and a lower-level aggregator E3.

[0022] The electric power company E1 generates and supplies electric power. The electric power company E1 can make a profit by conducting transactions with consumers (e.g., individuals or companies) who use electric power. The electric power company E1 maintains and manages the server 10, the power plant 11, the power transmission and distribution equipment 12, and the smart meters 13A and 13B.

[0023] The power plant 11 includes a power generation device for generating electricity, and is configured to supply the power generated by the power generation device to the power transmission and distribution facility 12. The power generation method of the power plant 11 is arbitrary, and may be, for example, 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 is configured to transmit and distribute the power supplied from the power plant 11. The power plant 11 and the power transmission and distribution facility 12 form an electric power system (power grid).

[0024] Each of the smart meters 13A, 13B is configured to measure the amount of power consumption at predetermined time intervals (for example, every 30 minutes), store the measured amount of power consumption, and transmit it to the server 10. IEC (DLMS / COSEM) can be used as the communication protocol between the smart meters 13A, 13B and the server 10, for example. The smart meters 13A, 13B are configured to measure the amount of power consumption (for example, the amount of power used to charge the BEVs 50A, 50B) in the EVSEs 40A, 40B, which will be described later. The power company E1 corresponds to the management business operator of each of the EVSEs 40A and 40B.

[0025] Each business operator (hereinafter referred to as "parent AG") belonging to upper aggregator E2 manages multiple business operators (hereinafter referred to as "child AG") belonging to lower aggregator E3, and provides energy management services by aggregating the amount of electricity controlled by the child AGs within its jurisdiction. The parent AG can earn profits by trading with, for example, electric power company E1.

[0026] The server 10 is configured to manage information on multiple parent AGs (e.g., parent AGs registered in the server 10) within its jurisdiction. Each parent AG is assigned identification information (ID) for identifying the parent AG. The server 10 manages information for each parent AG, distinguishing it by the parent AG ID. A parent AG may procure electricity supply capacity not only from BEVs (electric vehicles) but also from resources other than BEVs (e.g., biomass). The upper aggregator E2 includes multiple servers (e.g., servers 20A to 20C) provided for each parent AG. Hereinafter, unless otherwise specified, each server included in the upper aggregator E2 will be referred to as a "server 20." While FIG. 1 shows three servers 20 (servers 20A to 20C), the number of servers 20 included in the upper aggregator E2 is arbitrary and may be 10 or more.

[0027] Each server 20 included in the upper aggregator E2 is configured to manage information on multiple child AGs (e.g., child AGs registered in the server 20) within its jurisdiction. Each business operator (child AG) belonging to the lower aggregator E3 controls the amount of power by requesting each consumer to reduce or increase their power demand using a DR signal (demand response signal). Identification information (ID) for identifying the child AG is assigned to each child AG. The server 20 manages information for each child AG by distinguishing it using the child AG's ID. The lower aggregator E3 includes multiple servers (e.g., servers 30A to 30C) provided for each child AG. Hereinafter, unless otherwise specified, each server included in the lower aggregator E3 will be referred to as a "server 30." The servers 30A to 30C shown in FIG. 1 are managed by a common server 20 (e.g., server 20B). The number of servers 30 managed by each server 20 included in the upper aggregator E2 is arbitrary and may be 10 or more.

[0028] In the VGI system 1 shown in FIG. 1, the consumers managed by the child AG (and thus the server 30) are BEVs (electric vehicles). The BEVs can receive power from EVSEs (vehicle power supply equipment). In this embodiment, the VGI system 1 includes both AC (alternating current) EVSEs and DC (direct current) EVSEs.

[0029] The EVSE 40A included in the VGI system 1 shown in FIG. 1 is a home EVSE (i.e., an EVSE installed in a home). Home EVSEs can be managed by a Home Energy Management System-Gateway (HEMS-GW). For example, the EVSE 40A is managed by a HEMS-GW 60. The EVSE 40B included in the VGI system 1 shown in FIG. 1 is a public EVSE. Public EVSEs are installed in public facilities, commercial facilities, accommodation facilities, parking lots (e.g., highway service areas), etc. as infrastructure for charging power storage devices installed in electric vehicles. Typical examples of public EVSEs include AC standard chargers and DC rapid chargers.

[0030] The VGI system 1 includes multiple EVSEs, BEVs, and HEMS-GWs (only one of each is shown in FIG. 1 ). The number of EVSEs, BEVs, and HEMS-GWs included in the VGI system 1 is independent and arbitrary, and may be 10 or more, or 100 or more. Hereinafter, unless otherwise specified, each EVSE, each BEV, and each HEMS-GW included in the VGI system 1 will be referred to as an “EVSE 40,” a “BEV 50,” and a “HEMS-GW 60,” respectively. Each BEV 50 included in the VGI system 1 may be a privately owned vehicle (hereinafter also referred to as a “POV vehicle”) or a vehicle managed by a MaaS (Mobility as a Service) operator (hereinafter also referred to as a “MaaS vehicle”). In this embodiment, the user of each BEV 50 included in the VGI system 1 has a contract with electric power company E1. This contract gives the user the right to receive compensation from the electric power company E1 when the user adjusts the electric power demand in response to a request from the electric power company E1. The electric power company E1 in this embodiment corresponds to an example of a "contracted business operator."

[0031] Each server 30 included in the lower aggregator E3 is configured to manage information on multiple BEVs 50 (for example, BEVs registered in the server 30) within its jurisdiction. Identification information (hereinafter also referred to as a "vehicle ID") for identifying the BEV 50 is assigned to each BEV 50. The server 30 manages information for each BEV 50 by distinguishing them by the vehicle ID. Furthermore, each server 30 included in the lower aggregator E3 is configured to be able to communicate with each HEMS-GW 60 (for example, a HEMS-GW registered in the server 30) within its jurisdiction.

[0032] The EVSE 40A is connected to the power grid of the power company E1 via a smart meter 13A. The amount of power used by the EVSE 40A is measured by the smart meter 13A and transmitted to the server 10. The EVSE 40B is connected to the power grid of the power company E1 via a smart meter 13B. The amount of power used by the EVSE 40B is measured by the smart meter 13B and transmitted to the server 10. Hereinafter, unless otherwise specified, each of the smart meters 13A and 13B included in the VGI system 1 will be referred to as a "smart meter 13."

[0033] A smart meter 13 is provided for each EVSE 40 included in the VGI system 1. Each EVSE 40 included in the VGI system 1 is managed by electric power company E1 and connected to the power grid provided by electric power company E1. Each EVSE 40 included in the VGI system 1 receives power from electric power company E1. In the VGI system 1, identification information (hereinafter also referred to as "facility ID") for identifying the EVSE 40 is assigned to each EVSE 40, and the server 10 manages the power consumption of each EVSE 40 by distinguishing them by the facility ID. The electric power company E1 monitors the amount of power used by each EVSE 40 included in the VGI system 1 (i.e., the amount of power supplied to consumers) using each smart meter 13, and provides power to consumers through each EVSE 40 included in the VGI system 1.

[0034] The multiple EVSEs 40 included in the VGI system 1 include charging equipment that does not support reverse power flow and charging equipment that supports reverse power flow (i.e., charging and discharging equipment). The charging and discharging equipment is configured to supply power received from the BEVs 50 to the power grid of the power company E1 (i.e., reverse power flow). The smart meter 13 provided in the charging and discharging equipment is configured to measure the amount of power that is reversely flowed in addition to the amount of power used.

[0035] The functions of each element constituting the VGI system 1 will be explained below using Figure 2. Figure 2 is a communication system diagram of the VGI system 1. In Figure 2, BEV 50A is electrically connected to EVSE 40A (home EVSE) via a charging cable. BEV 50B is electrically connected to EVSE 40B (public EVSE) via a charging cable. BEV 50C is running.

[0036] 2, in the VGI system 1, servers 10 and 20 are configured to be able to communicate with each other. Servers 20 and 30 are also configured to be able to communicate with each other. The communication method between servers 10 and 20 and the communication method between servers 20 and 30 are each independent and arbitrary, and may be, for example, a VPN (Virtual Private Network).

[0037] The server 30 is configured to be able to communicate with each of the BEVs 50 (i.e., BEVs 50A to 50C) and the HEMS-GW 60. The server 30 and the HEMS-GW 60 are configured to communicate with each other, for example, via the Internet. The server 30 and each of the BEVs 50 are configured to wirelessly communicate with each other, for example, via a mobile communication network (telematics).

[0038] The HEMS-GW 60 and the EVSE 40A are configured to communicate with each other via, for example, a local area network (LAN), which may be a wired LAN or a wireless LAN.

[0039] The EVSE 40A and the BEV 50A are configured to communicate with each other via a charging cable. The EVSE 40B and the BEV 50B are also configured to communicate with each other via a charging cable. The communication method between the EVSE 40A and the BEV 50A and the communication method between the EVSE 40B and the BEV 50B are each independent and arbitrary, and may be a controller area network (CAN) or a power line communication (PLC).

[0040] The VGI system 1 further includes a data center 70 and a mobile terminal 80 registered in the data center 70. The data center 70 includes, for example, a server (not shown) that manages information. In this embodiment, a smartphone equipped with a touch panel display is used as the mobile terminal 80. However, the present invention is not limited to this, and any mobile terminal can be used as the mobile terminal 80, including, for example, a tablet terminal, a portable game console, and a wearable device such as a smartwatch.

[0041] The data center 70 is configured to communicate with the server 30, for example, via the Internet. The data center 70 is configured to manage information on a plurality of registered mobile terminals 80. The information on the mobile terminal 80 includes information on the terminal itself (for example, the communication address of the mobile terminal 80) as well as information on the user who carries the mobile terminal 80 (for example, information indicating the electric utility with which the user has a contract and the vehicle ID of the BEV 50 belonging to the user). Identification information for identifying the mobile terminal 80 (hereinafter also referred to as a "terminal ID") is assigned to each mobile terminal 80, and the data center 70 manages the information for each mobile terminal 80 by distinguishing them by the terminal ID. The terminal ID also functions as information for identifying the user (user ID). Although only one mobile terminal 80 is illustrated in FIG. 2, a mobile terminal 80 is carried by each user.

[0042] Predetermined application software (hereinafter simply referred to as "app") is installed on the mobile terminal 80, and the mobile terminal 80 is configured to exchange information with each of the HEMS-GW 60 and the data center 70 through the app. The mobile terminal 80 is configured to wirelessly communicate with each of the HEMS-GW 60 and the data center 70 via, for example, the Internet.

[0043] The server 10 is configured to adjust the balance between supply and demand of electricity using DR (Demand Response). When the server 10 performs such an adjustment, it first transmits a signal requesting participation in DR (hereinafter also referred to as a "DR participation request") to each of the servers 20 included in the upper aggregator E2 (for example, servers 20A to 20C shown in FIG. 1). The DR participation request includes the area to be covered by the DR, the type of DR (for example, downward DR or upward DR), and the DR period.

[0044] The server 20 is configured to, upon receiving a DR participation request from the server 10, determine the DR possible amount (i.e., the amount of power that can be adjusted according to DR) and transmit it to the server 10. The server 20 can determine the DR possible amount, for example, based on the sum of the DR capacities (i.e., DR-compatible capacities) of each child AG within its jurisdiction. The server 20 can obtain the DR capacity of each child AG within its jurisdiction, for example, by inquiring of the server 30. The server 10 determines the DR amount for each parent AG (i.e., the amount of power adjustment to be requested from the parent AG) based on the DR possible amount received from each server 20 included in the upper aggregator E2, and transmits a signal instructing the server 20 of each parent AG to execute DR (hereinafter also referred to as a "first DR execution instruction"). The first DR execution instruction includes the area to be subject to the DR, the type of DR (e.g., downward DR or upward DR), the DR amount for the parent AG, and the DR period.

[0045] The server 30 is configured to sequentially acquire and store information indicating the status of each BEV 50 within its jurisdiction (for example, vehicle location, remaining battery charge, driving schedule, and driving conditions) from each BEV 50. By accumulating such data, the charge / discharge history and driving history of each BEV 50 within its jurisdiction are stored in the server 30. The server 30 is also configured to sequentially acquire and store information indicating the status of each EVSE 40 within its jurisdiction (for example, information indicating whether charging is in progress, charging schedule, and charging conditions) from each HEMS-GW 60 connected to each EVSE 40. By accumulating such data, the charging history and reverse power flow history of each EVSE 40 within its jurisdiction are stored in the server 30.

[0046] The user can transmit information indicating the user's status and schedule to the data center 70 by operating the mobile terminal 80. An example of the information indicating the user's status is information indicating whether the user is in a state where they can respond to DR. An example of the information indicating the user's schedule is the time when the POV vehicle departs from home, or the operation plan of the MaaS vehicle. The data center 70 is configured to store the above information received from the mobile terminal 80 separately for each terminal ID. The server 30 can acquire information about the user from the data center 70.

[0047] When the server 30 receives the above-mentioned inquiry from the server 20, the server 30 is configured to determine the DR capacity of the child AG corresponding to the server 30 based on the above-mentioned information on each of the BEVs 50, the EVSEs 40, and the user, and transmit the DR capacity to the server 20. When the server 20 receives the above-mentioned first DR execution instruction from the server 10, the server 20 determines the DR amount for each child AG (i.e., the amount of power to be requested to be adjusted by the child AG) based on the DR capacity received from each server 30 included in the lower aggregator E3, and transmits a signal instructing the server 30 of each child AG to execute DR (hereinafter also referred to as a "second DR execution instruction"). The second DR execution instruction includes the area to be subject to the DR, the type of DR (for example, downward DR or upward DR), the DR amount for the child AG, and the DR period.

[0048] When the server 30 receives the second DR execution instruction, it allocates a DR amount to each DR-capable BEV 50 among the BEVs 50 under its jurisdiction, creates a DR signal for each BEV 50, and transmits the DR signal to each BEV 50. The DR signal includes the type of DR (e.g., downward DR or upward DR), the DR amount for the BEV 50, and a DR period. The DR amount of the upward DR required of the BEV 50 during the DR period may be, for example, the charging power during the DR period, or the charging amount during the DR period (i.e., the time integral of the charging power). The DR amount of the downward DR required of the BEV 50 during the DR period may be, for example, the discharging amount during the DR period (i.e., the time integral of the discharging power), or a guard value (i.e., the upper limit of the charging power) that limits the charging power during the DR period.

[0049] When a user of each BEV50 included in the VGI system 1 receives the above-mentioned DR signal, the user can contribute to the adjustment of power demand by charging or discharging in accordance with the DR using charging equipment (i.e., any of the multiple EVSEs 40 included in the VGI system 1) managed by the contracted electric power company E1. The user who contributes to the adjustment of power demand then acquires the right to receive a reward (compensation for the contribution) from the electric power company E1 based on the contract with the electric power company E1.

[0050] 3 is a diagram showing the configuration of a BEV 50. Referring to FIG. 3, the BEV 50 includes a motor generator (hereinafter referred to as "MG (Motor Generator)") 51, a power transmission gear 52, a drive shaft 53, a power control unit (hereinafter referred to as "PCU (Power Control Unit)") 54, a high-voltage battery 110, a monitoring unit 120, a charger / discharger 150, an inlet 160, a communication device 180, an electronic control unit (hereinafter referred to as "ECU (Electronic Control Unit)") 200, a car navigation system (hereinafter also referred to as "NAVI system") 300, an input device 310, and a notification device 320. The ECU 200 is configured to perform charging control and discharging control of the high-voltage battery 110.

[0051] The high-voltage battery 110 is configured to store power for driving. The high-voltage battery 110 includes a secondary battery such as a lithium-ion battery or a nickel-metal hydride battery. The secondary battery may be a single cell or a battery pack. Alternatively, another power storage device such as an electric double layer capacitor may be used instead of the secondary battery.

[0052] The inlet 160 is configured to receive power supplied from outside the BEV 50. The inlet 160 can be connected to a connector 43 of a charging cable 42.

[0053] The charger / discharger 150 is located between the inlet 160 and the high-voltage battery 110. The charger / discharger 150 includes a relay that switches between connection and disconnection of a power path from the inlet 160 to the high-voltage battery 110, and a power conversion circuit (e.g., a bidirectional converter) (neither of which is shown). The relay and the power conversion circuit included in the charger / discharger 150 are each controlled by the ECU 200.

[0054] Connecting the EVSE 40, which is external to the BEV 50, to the inlet 160 via the charging cable 42 enables power to be exchanged between the EVSE 40 and the BEV 50. For example, it becomes possible to receive power from an external source of the BEV 50 and charge the high-voltage battery 110 of the BEV 50 (hereinafter also referred to as "external charging"). Power for external charging is supplied, for example, from the EVSE 40 to the inlet 160 via the charging cable 42. The charger / discharger 150 is configured to convert the power received by the inlet 160 into power suitable for charging the high-voltage battery 110 and output the converted power to the high-voltage battery 110. Connecting the EVSE 40 to the inlet 160 via the charging cable 42 also enables power to be supplied from the BEV 50 to the EVSE 40 via the charging cable 42 (and thus the high-voltage battery 110 to be discharged). Electric power for power supply to the outside of BEV 50 (hereinafter also referred to as "external power supply") is supplied from high-voltage battery 110 to charger / discharger 150. Charger / discharger 150 is configured to convert the power supplied from high-voltage battery 110 into power suitable for external power supply and output the converted power to inlet 160. When either external charging or external power supply is performed, the relay of charger / discharger 150 is closed (connected), and when neither external charging nor external power supply is performed, the relay of charger / discharger 150 is opened (disconnected).

[0055] Charger / discharger 150 and inlet 160 may be a charger / discharger and inlet compatible with an AC system or a charger / discharger and inlet compatible with a DC system. BEV 50 may be provided with multiple types of chargers / dischargers and inlets to be compatible with multiple systems (for example, both AC and DC systems).

[0056] The configuration of charger / discharger 150 is not limited to the above and can be changed as appropriate. Charger / discharger 150 may include at least one of a rectifier circuit, a power factor correction circuit, an isolation circuit (e.g., an isolation transformer), an inverter, and a filter circuit, for example.

[0057] The MG51 is, for example, a three-phase AC motor generator. The MG51 is driven by the PCU54 and configured to generate driving force for driving the BEV50. The PCU54 is configured to include, for example, a control device including a processor, an inverter, and a converter (none of which are shown). The control device of the PCU54 is configured to receive instructions (control signals) from the ECU200 and control the inverter and converter of the PCU54 in accordance with the instructions. The PCU54 further includes a system main relay (hereinafter referred to as "SMR (System Main Relay)") not shown. The SMR is configured to switch between connection and disconnection of a power path from the high-voltage battery 110 to the PCU54. The state (connection / disconnection) of the SMR is controlled by the ECU200. The SMR is closed (connected) when the vehicle is running.

[0058] The MG 51 is mechanically connected to the drive shaft 53 via a power transmission gear 52 that functions as a reducer. Drive wheels (not shown) of the BEV 50 are attached to both ends of the drive shaft 53 and are configured to rotate integrally with the drive shaft 53. The MG 51 is driven by power supplied from the high-voltage battery 110 via the inverter and converter of the PCU 54 and is in a power running state. In the power running state, the MG 51 rotates the drive shaft 53 (and thus the drive wheels of the BEV 50). The MG 51 is also configured to perform regenerative power generation and supply the generated power to the high-voltage battery 110. The drive system of the BEV 50 is arbitrary, and may be, for example, front-wheel drive or four-wheel drive. While FIG. 3 shows a configuration in which only one MG is provided, the number of MGs is not limited thereto, and a configuration in which multiple MGs (for example, two) are provided is also possible.

[0059] The monitoring unit 120 includes various sensors that detect the state of the high-voltage battery 110 (for example, temperature, current, and voltage), and outputs the detection results to the ECU 200. The ECU 200 can acquire the state of the high-voltage battery 110 (for example, temperature, current, voltage, SOC (State Of Charge), and internal resistance) based on the output of the monitoring unit 120 (i.e., the detected values ​​of the various sensors). The SOC indicates the remaining amount of power, and is, for example, the ratio of the current amount of power stored to the amount of power stored in a fully charged state, expressed as a percentage from 0 to 100%.

[0060] The communication device 180 includes a communication I / F (interface) for communicating with each of the server 30, the EVSE 40, and the mobile terminal 80. The communication device 180 is registered with the server 30. The communication device 180 may further include a communication I / F for communicating with each of the HEMS-GW 60 and the data center 70.

[0061] The ECU 200 includes a processor 210, a RAM (Random Access Memory) 220, and a storage device 230. The processor 210 may be, for example, a CPU (Central Processing Unit). The RAM 220 functions as a working memory that temporarily stores data processed by the processor 210. The storage device 230 is configured to be able to save stored information. The storage device 230 includes, for example, a ROM (Read Only Memory) and a rewritable non-volatile memory. The storage device 230 stores programs as well as information used by the programs (for example, maps, mathematical formulas, and various parameters). The ECU 200 is configured to communicate with devices outside the BEV 50 (for example, the server 30, the EVSE 40, and the mobile terminal 80) via the communication device 180. The ECU 200 may include any number of processors, and a processor may be provided for each predetermined control.

[0062] The navigation system 300 includes a control device 301, a touch panel display (hereinafter also referred to as "TPD") 302, a GPS (Global Positioning System) module 303, a storage device 304, operation buttons 305, and a speaker 306. The control device 301 includes a processor and RAM (neither of which are shown). The storage device 304 may be, for example, at least one of a hard disk drive and an SSD (Solid State Drive). The storage device 304 stores map information and a route search program. In this embodiment, a smart speaker (i.e., a speaker with an AI (artificial intelligence) assistant function that supports interactive voice operation) is used as the speaker 306. However, the present invention is not limited to this, and a general speaker that does not accept voice input may be used instead of a smart speaker.

[0063] The TPD 302 receives touch input from the user and displays maps and other information. The speaker 306 receives voice input from the user and outputs sounds (including voice). The operation button 305 also receives input from the user. The TPD 302, the speaker 306, and the operation button 305 all function as input devices and are configured to output signals corresponding to user input to the control device 301. Furthermore, the TPD 302 and the speaker 306 each function as an alarm device and are configured to provide an alarm to a user (e.g., a passenger of the BEV 50).

[0064] The GPS module 303 is configured to receive signals (hereinafter referred to as "GPS signals") from GPS satellites (not shown). The control device 301 is configured to identify the position of the BEV 50 using the GPS signals. The control device 301 is configured to control the TPD 302 to display the position of the BEV 50 in real time on a map displayed by the TPD 302. The control device 301 is configured to execute a route search program to perform a route search to find an optimal route (e.g., the shortest route) from the current position of the BEV 50 to a destination, and to display the optimal route found by the route search on a map displayed by the TPD 302. The user can set a destination in the control device 301 through the above-mentioned input devices (i.e., the TPD 302, the speaker 306, and the operation button 305).

[0065] The BEV 50 is equipped with an input device 310 in addition to the input device of the navigation system 300. The input device 310 is configured to accept input from a user and to output a signal corresponding to the input from the user to the ECU 200. Communication between the ECU 200 and the input device 310 may be wired or wireless. Examples of the input device 310 include various switches, various pointing devices, a keyboard, a smart speaker, and a touch panel.

[0066] The BEV 50 is equipped with a notification device 320 separate from the notification device of the NAVI system 300. The notification device 320 is configured to perform a predetermined notification process to a user (for example, an occupant of the BEV 50) when requested by the ECU 200. The notification device 320 may be any of a display device (for example, a touch panel display), a speaker (for example, a smart speaker), and a lamp (for example, an MIL (malfunction warning light)).

[0067] FIG. 4 is a diagram showing an input device and an alarm device mounted near the driver's seat of the BEV 50. Referring to FIG. 4, the BEV 50 includes operation buttons 311 and 312, a head-up display (hereinafter referred to as "HUD") 321, and a meter panel 322. The operation buttons 311 and 312 are included in the input device 310 (FIG. 3) described above. The operation button 311 is an operation button provided on the instrument panel of the BEV 50. The operation button 312 is an operation button provided on the steering wheel 502 of the BEV 50. The HUD 321 and the meter panel 322 are each included in the alarm device 320 (FIG. 3) described above. The HUD 321 is a display provided on the windshield 501 of the BEV 50. The meter panel 322 is located near the windshield 501 and is configured to display information about the BEV 50 (for example, remaining battery charge (SOC), driving speed, driving distance, average power consumption, and outside temperature). The instrument panel of the BEV 50 is also provided with a TPD 302 and operation buttons 305 of the navigation system 300 (FIG. 3). The main body of the navigation system 300 is disposed within the instrument panel.

[0068] FIG. 5 is a diagram illustrating a BEV 50B connected to a public EVSE 40B. Referring to FIG. 5, the BEV 50B is electrically connected to the EVSE 40B via a charging cable 42 while parked in a parking lot where the EVSE 40B is installed. The charging cable 42 has a connector 43 at its tip. When the connector 43 of the charging cable 42 connected to the EVSE 40B is connected to an inlet 160 of the BEV 50B, communication between the BEV 50B and the EVSE 40B becomes possible, and power can be supplied from a power source 41 (i.e., a power source provided external to the BEV 50B) provided in the EVSE 40B to the BEV 50B (and thus to the high-voltage battery 110). The power source 41 is connected to a power grid PG provided by a power company E1 (FIG. 1) via a smart meter 13B. The power source 41 is configured to supply power from the power grid PG to the BEV 50B via the charging cable 42. The amount of power used in the EVSE 40B is measured by a smart meter 13B.

[0069] The communication device 180 mounted on the BEV 50B is configured to communicate with the EVSE 40B via the charging cable 42. The communication device 180 is also configured to communicate wirelessly with the server 30, for example, via a mobile communication network. In this embodiment, the communication device 180 and the mobile terminal 80 are configured to communicate wirelessly with each other. The communication between the communication device 180 and the mobile terminal 80 may be short-range communication (for example, direct communication within the vehicle and its surroundings). In this embodiment, no communication is performed between the server 30 and the EVSE 40B, but the server 30 and the EVSE 40B may be configured to be able to communicate with each other. At least one of the communication device 180 and the mobile terminal 80 may be configured to receive the amount of power usage in the EVSE 40B from the smart meter 13B. At least one of the alarm device 320 and the mobile terminal 80 may be configured to display at least one of the measurement value of the smart meter 13B, the DR amount allocated to the BEV 50B, and the achievement rate of the DR amount while the high-voltage battery 110 is charging or discharging.

[0070] EVSE 40 includes specific EVSE 40 that can only be used by specific BEVs 50 that are permanently authorized to use the EVSE 40 (for example, this includes not only permanently permitted BEVs 50, but also BEVs 50 that have been authorized from the beginning and BEVs 50 of users of facilities that have parking lots in which the EVSE 40 is installed). When using BEVs 50 as a power resource, it is conceivable to use not only public EVSEs 40 that can be used by any BEVs 50, but also specific EVSEs 40 such as EVSEs 40 that are used privately by businesses, etc.

[0071] Therefore, the management server (for example, one of servers 10, 20, or 30) performs a process (for example, a process for direct permission, or a process for indirect permission by obtaining permission from the administrator of the specific EVSE40) to temporarily permit the non-specific BEV50 to use the specific EVSE40, on the condition that a non-specific BEV50 different from the specific BEV50 uses the specific EVSE40 to exchange electricity with the power company E1, and performs a process to grant an incentive to the user of the non-specific BEV50 or the administrator of the specific EVSE40, on the condition that the non-specific BEV50 has exchanged electricity with the power company E1.

[0072] As a result, even a non-specific BEV50 that is different from a specific BEV50 that is permanently authorized to use a specific EVSE40 can be used to exchange power with the power grid PG of the power company E1 in the specific EVSE40. As a result, it is possible to increase the opportunities to use the BEV50 for power exchange.

[0073] 6 is a diagram for explaining an outline of a search for a parking lot 44 equipped with an EVSE 40 in the first embodiment. First, the user 5 installs a specific app created by a business that provides a VPP service on the mobile terminal 80. By launching this specific app, the user 5 can search for a parking lot 44 that has a specific EVSE 40 that can only be used by a specific BEV 50 different from the BEV 50 of the user 5.

[0074] Such parking lots 44 are, for example, parking lots managed by a parking lot manager such as a company, individual, or real estate agent, or by a manager 45 such as a rental car company. In parking lots 44 managed by a company, for example, employees and related businesses are permitted to park, and since there are more vacant parking spaces on company holidays, unspecified BEVs 50 can also be parked there. In parking lots 44 managed by individuals or real estate agents, contracted users can park there, and unspecified BEVs 50 can park in vacant parking spaces when the number of contracted vehicles is less than the number of parking spaces. In parking lots 44 managed by rental car companies, rental cars managed by the company can be parked there, and unspecified BEVs 50 can park in vacant parking spaces depending on the rental car operation status.

[0075] The EVSE 40 of a searchable parking lot is prepared to be able to participate in a VPP managed by a management server, which is one of the servers 10, 20, and 30. A user 5 goes to the parking lot found in the search results, connects his / her BEV 50 to the EVSE 40, and participates in the specified VPP. In response, the user 5 is given an incentive, such as by being issued a coupon.

[0076] The management server also acquires the DR performance of the BEV 50 at the VPP from the EVSE 40 and transmits data related to VPP participation, such as the DR performance at the VPP, to a provider that provides the VPP service. The provider that provides the VPP service provides an incentive by awarding points to the user 5 according to the VPP participation status indicated by the data related to VPP participation. The user 5 can check the awarded points on the member point screen of the specific app.

[0077] The management server provides incentives, such as reducing the retail electricity contract fee, to the parking lot manager or the rental car company depending on the status of provision of the EVSE 40 to the VPP. Note that the business providing the VPP service may be the same business as the electric power company E1, the upper aggregator E2, or the lower aggregator E3.

[0078] 7 is a flowchart showing the process flow for searching for parking lots 44 that have EVSEs 40 that can participate in VPP in the VGI system 1 according to this embodiment. Referring to FIG. 7, the CPU of the mobile terminal 80 determines whether information such as the date and time of use and the area of ​​use for searching for parking lots 44 has been input from the touch panel display (step S811).

[0079] If it is determined that parking lot search information has been entered (YES in step S811), information such as the date and time of use and the area of ​​use to search for parking lots 44 that can participate in the VPP is sent to the management server (one of servers 10, 20, or 30) (step S812).

[0080] The CPU of the management server determines whether or not search information has been received from the mobile terminal 80 (step S111). If it determines that search information has been received (YES in step S111), the CPU of the management server searches for parking lots 44 that can participate in the VPP and meet the search criteria (step S112), and transmits the search results (including information permitting use of the parking lot) to the mobile terminal 80 (step S113).

[0081] If it is determined that the parking lot search information has not been input (NO in step S811), or after step S812, the CPU of the mobile terminal 80 determines whether or not search results have been received from the management server (step S813).If it is determined that search results have been received (YES in step S813), the CPU of the mobile terminal 80 displays information about the parking lots 44 that have EVSEs 40 that can participate in the VPP, as indicated in the search results, on the touch panel display (step S814).

[0082] If it is determined that search information has not been received (NO in step S111), or after step S113, the CPU of the management server determines whether it is the period (for example, every 5 minutes or every minute) for checking the participation of the BEV 50 in the VPP in the EVSE 40 in the parking lot 44 (step S121). If it is determined that it is the period (YES in step S121), the CPU of the management server checks the participation status of the BEV 50 in the VPP in the EVSE 40 in the parking lot 44 (step S122).

[0083] The CPU of the management server then determines whether the BEV 50 is participating in a VPP (step S123). If it is determined that the BEV 50 is participating in a VPP (YES in step S123), the CPU of the management server executes a process to request a business that provides a VPP service to grant an incentive to the user 5 of the BEV 50 (step S124). Note that the CPU of the management server may execute a process to directly grant an incentive to the user 5 of the BEV 50 as a process to grant an incentive to the user 5 of the BEV 50.

[0084] Next, the CPU of the management server executes a process to request the provider of the VPP service to notify the mobile terminal 80 of the user 5 that an incentive has been granted (step S125), as a process to notify the mobile terminal 80 of the user 5 that an incentive has been granted. Note that the CPU of the management server may also execute a process to directly notify the mobile terminal 80 of the user 5 that an incentive has been granted, as a process to notify the mobile terminal 80 of the user 5 that an incentive has been granted.

[0085] If it is determined that the search result has not been received (NO in step S813), or after step S814, the CPU of the mobile terminal 80 determines whether or not a notification that an incentive has been granted has been received (step S821). If it is determined that a notification has been received (YES in step S821), the CPU controls the touch panel display and speaker to notify that an incentive has been granted (step S822).

[0086] If it is determined that no notification has been received (NO in step S821), or after step S822, the CPU of the mobile terminal 80 determines whether an operation to confirm the granted incentive has been input on the touch panel display (step S831). If it is determined that a confirmation operation has been input (YES in step S831), the CPU of the mobile terminal 80 transmits information for confirming the granted incentive to the management server (step S832).

[0087] If it is determined that it is not the confirmation period (NO in step S121), if it is determined that the BEV 50 is not participating in the VPP (NO in step S123), or after step S125, the CPU of the management server determines whether or not information for confirming the granted incentive has been received from the mobile terminal 80 (step S131). If it is determined that the confirmation information has been received (YES in step S131), the CPU of the management server searches for the incentive granted to the user 5 of the mobile terminal 80 that sent the confirmation information (step S132), and sends the search result to the mobile terminal 80 (step S133).

[0088] If it is determined that the confirmation operation has not been input (NO in step S831), the CPU of the mobile terminal 80 determines whether or not the search result has been received from the management server (step S833). If it is determined that the search result has been received (YES in step S833), the CPU of the mobile terminal 80 displays the awarded incentive indicated in the search result on the touch panel display (step S834).

[0089] [Second embodiment] In the first embodiment, the parking lot 44 is a parking lot managed by an administrator 45. In return for the BEV 50 participating in the VPP, a coupon is given to the user 5 of the BEV 50 by the administrator.

[0090] FIG. 8 is a diagram illustrating an outline of a search for a parking lot 44 equipped with an EVSE 40 in the second embodiment. In the second embodiment, the parking lot 44 is managed by a manager 45, such as a hotel. The manager 45 allows customers to use the parking lot 44, for example, to shop at nearby stores 46A-46D, thereby receiving fees from the stores 46A-46D. The stores 46A-46D provide coupons to the users 5 of the BEVs 50 in exchange for the BEVs 50 participating in the VPP. The users 5 can use the coupons at the stores 46A-46D. The stores 46A-46D receive incentives, such as reduced electricity retail contract fees, from a management server (servers 10, 20, or 30) based on the VPP participation records of the users 5 who use the stores 46A-46D. This allows the manager 45 to increase the utilization rate of the parking lot. The stores 46A-46D can save on parking contract fees and avoid losing customers to suburban shopping complexes.

[0091] [Variations] (1) In the above-described embodiment, the electricity trading partner is the electric power company E1. However, the present invention is not limited to this, and the electricity trading partner may be a business other than a power generation business such as the electric power company E1, for example, a general electricity transmission and distribution business, a retail electricity business, or an electricity consumer such as a general business.

[0092] (2) In the above-described embodiment, the power supply and demand system of the power trading partner is the power grid PG. However, this is not limited to this, and the power supply and demand system of the power trading partner may be another system, for example, a power line system within a business premises.

[0093] (3) In the above-described embodiment, the electric vehicle is a BEV 50. However, the present invention is not limited to this. The electric vehicle may be a vehicle that is equipped with a power storage device and is capable of external charging and discharging. For example, the electric vehicle may be a PHEV or a plug-in fuel cell electric vehicle (FCEV).

[0094] (4) The above-described embodiments can be understood as disclosure of a power management system such as VGI system 1, as disclosure of a power management method in a power management system, as disclosure of server 10, 20, 30, EVSE 40 or BEV 50, or as disclosure of a power management method or power management program executed in server 10, 20, 30, EVSE 40 or BEV 50.

[0095] [summary] (1) As shown in Figures 1 and 2, the VGI system 1 is a system that exchanges power between the power grid PG of power company E1 and BEVs 50. As shown in Figures 1 and 2, the VGI system 1 includes multiple BEVs 50, an EVSE 40 including a charging cable 42 through which power is exchanged with the BEVs 50 and a connector 43 for connecting the charging cable 42 to the BEVs 50, and a management server (e.g., one of servers 10, 20, or 30) that manages the exchange of power. As shown in Figure 6, the EVSE 40 includes specific EVSEs 40 that can be used by specific vehicles that are permanently authorized to use the EVSE 40 (e.g., not only permanently permitted BEVs 50, but also BEVs 50 that are authorized from the beginning and BEVs 50 owned by users of facilities that have a parking lot in which the EVSE 40 is installed).

[0096] As shown in Figure 6, the management server performs a process (for example, step S113) to temporarily permit a non-specific vehicle, different from a specific vehicle, to use the specific EVSE 40, on the condition that the non-specific vehicle uses the specific EVSE 40 to exchange electricity with the electric power company E1 (this may be a process to directly permit the non-specific vehicle, or a process to indirectly permit the non-specific vehicle by obtaining permission from the administrator of the specific charging / discharging equipment), and performs a process to grant an incentive to the user 5 of the non-specific vehicle or the administrator of the specific EVSE 40, on the condition that the non-specific vehicle has exchanged electricity with the electric power company E1 (for example, step S124).

[0097] This allows even a non-specific vehicle, which is different from a specific vehicle that is permanently authorized to use a specific EVSE 40, to exchange power with the power grid PG of the power company E1 in the specific EVSE 40. As a result, it is possible to increase the opportunities to use vehicles for exchange of power.

[0098] (2) The management server may provide an incentive to the manager depending on the size or performance of a particular EVSE 40 .

[0099] This makes it possible to motivate the administrator who provides a specific EVSE 40 to be utilized for the exchange of electric power between vehicles to provide a larger-scale, higher-performance EVSE 40.

[0100] (3) As shown in FIG. 6, in response to a request from a user 5 of an unspecified vehicle to search for a specific EVSE 40, the management server searches for a specific EVSE 40 according to the user 5's wishes and transmits the search results to the user 5 (for example, steps S811 to S814, steps S111 to S113).

[0101] This makes it possible to notify the user 5 of an unspecified vehicle of a specific EVSE 40 that meets the desire of the user 5. As a result, convenience for the user 5 can be improved.

[0102] (4) The management server may search for a specific EVSE 40 on a day when a specific vehicle is not using the EVSE 40 (for example, a regular holiday for the operator of the parking lot where the charging / discharging equipment is installed).

[0103] This allows a specific EVSE 40 to be provided to a non-specific vehicle on days when the specific vehicle is not using the EVSE 40.

[0104] 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]

[0105] 1 VGI system, 5 user, 10, 20, 20A-20C, 30, 30A-30C server, 11 power plant, 12 power transmission and distribution equipment, 13, 13A, 13B smart meter, 40, 40A, 40B EVSE, 41 power supply, 42 charging cable, 43 connector, 44 parking lot, 45 administrator, 46A-46D store, 50, 50A-50C BEV, 51 MG, 52 power transmission gear, 53 drive shaft, 54 PCU, 60 HEMS-GW, 70 data center, 80 mobile terminal, 110 high-voltage battery, 120 monitoring unit, 150 charger / discharger, 160 inlet, 180 communication equipment, 200 ECU, 210 processor, 220 RAM, 230, 304 storage device, 300 NAVI system, 301 Control device, 302 TPD, 303 GPS module, 305, 311, 312 operation buttons, 306 speaker, 310 input device, 320 alarm device, 321 HUD, 322 meter panel, 501 windshield, 502 steering wheel, E1 power company, E2 upper aggregator, E3 lower aggregator, PG power system.

Claims

1. An electricity management system that exchanges electricity for a virtual power plant between an electricity supply and demand system of an electricity trading partner and a vehicle, A plurality of the vehicles; a plurality of charging / discharging devices each including a cable through which power is exchanged between the vehicle and the charging / discharging device and a connector for connecting the cable to the vehicle; A server that manages the exchange of power, The charging / discharging device includes specific charging / discharging equipment that can be used by specific vehicles that are permanently authorized to use the charging / discharging device among the vehicles, The server executes a process for temporarily permitting a non-specified vehicle different from the specified vehicle to use the specified charging / discharging facility on the condition that the non-specified vehicle uses the specified charging / discharging facility to exchange electricity with the business partner; An energy management system that executes a process to provide an incentive to a user of the non-specified vehicle or an administrator of the specified charging / discharging equipment, on the condition that the non-specified vehicle exchanges electricity with the business partner.

2. The power management system according to claim 1 , wherein the server provides the manager with an incentive according to a scale or performance of the specific charging / discharging facility.

3. The server 2. The power management system according to claim 1, wherein, in response to a request from a user of the non-specific vehicle to search for the specific charging / discharging facility, the specific charging / discharging facility according to the user's request is searched for, and the search results are transmitted to the user.

4. The energy management system according to claim 3 , wherein the server searches for the specific charging / discharging equipment on days when the specific vehicle does not use the equipment.

5. A power management method in a power management system that exchanges power for a virtual power plant between a power supply and demand system of a power trading partner and a vehicle, comprising: The power management system includes: A plurality of the vehicles; a plurality of charging / discharging devices each including a cable through which power is exchanged between the vehicle and the charging / discharging device and a connector for connecting the cable to the vehicle; A server that manages the exchange of power, The charging / discharging device includes specific charging / discharging equipment that can be used by specific vehicles that are permanently authorized to use the charging / discharging device among the vehicles, The power management method includes: a step in which the server executes a process for temporarily permitting a non-specified vehicle different from the specified vehicle to use the specified charging / discharging facility on the condition that the non-specified vehicle uses the specified charging / discharging facility to exchange electricity with the business partner; The power management method includes a step in which the server executes a process to provide an incentive to the user of the non-specified vehicle or the manager of the specified charging / discharging equipment, on the condition that the non-specified vehicle has exchanged power with the business partner.

Images