Display device, and energy management system

Abstract

To facilitate a user to carry out at least one of charging and discharging of a power storage device at appropriate timing.SOLUTION: A portable terminal 400 functioning as a display device includes: a first acquisition part 411 for acquiring a first schedule indicating a time band where a power storage device is planned to be charged or discharged; a second acquisition part 412 for acquiring a second schedule indicating a time band where a demand response requiring charging or discharging of the power storage device is planned; and a display part 420 for displaying a schedule screen. The display part 420 displays the first and second schedules simultaneously on the schedule screen in a mode in which they can be distinguished from each other.SELECTED DRAWING: Figure 14

Description

Technical Field

[0001] The present disclosure relates to a display device, an energy management system, and a schedule display method.

Background Art

[0002] An electric utility may request energy management from an administrator of a power storage device by means of DR (Demand Response). An example of energy management is power regulation of a power grid. For example, International Publication No. 2020 / 100288 (Patent Document 1) discloses a charging support system including a processor that generates vehicle charging plan data based on predicted power consumption of a vehicle calculated based on a future driving schedule of the vehicle and charging conditions set for a predicted parking location for demand response.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the charging support system described in Patent Document 1, the processor automatically generates vehicle charging plan data based on predicted power consumption of the vehicle and charging conditions set for a predicted parking location for demand response (more specifically, charging conditions set based on whether demand response is implemented at the predicted parking location). However, in Patent Document 1, improvement of a user interface for a vehicle user to determine charging conditions by himself / herself or to determine whether to participate in DR has not been sufficiently studied.

[0005] In addition, Patent Document 1 describes that power saving is required during DR implementation. However, DR is not only about requesting power saving. General DR is broadly classified into up-DR and down-DR. Up-DR is basically DR that requests an increase in demand. On the other hand, down-DR is DR that requests demand suppression or reverse power flow. A typical method of using DR is a method in which a power transmission and distribution utility generates either up-DR or down-DR according to the power supply and demand situation that varies moment by moment. Hereinafter, the DR generated in this way is also referred to as "normal DR". Furthermore, in recent years, when a retail electricity provider compares and weighs the cost of procuring power on its own and the cost of procuring power through DR and determines that DR has greater economic benefits, the provider may generate DR. Hereinafter, the DR generated in this way is also referred to as "economic DR".

[0006] The administrator of the energy storage device can participate in DR using the energy storage device. However, in Patent Document 1, the development of a user interface that promotes the administrator of the energy storage device to utilize the energy storage device has not been sufficiently considered. In Patent Document 1, it is not assumed that the administrator of the energy storage device himself / herself selects the DR to participate in from among multiple types of DR (for example, normal DR and economic DR).

[0007] In addition, the charging of the energy storage device may be executed by timer charging. Timer charging is charging according to a reserved charging schedule. Administrators of energy storage devices that routinely use timer charging tend to charge the energy storage device at a fixed time period all the time. On the other hand, since the time period when DR occurs is irregular, even if the schedule of timer charging is set according to the timing of DR once, the schedule of that timer charging does not necessarily match the timing of the next-occurring DR. For this reason, a user interface for checking whether the schedule of timer charging matches the timing of DR is required. Further improvement is desired for the user interface provided for the use of the administrator of the energy storage device in the implementation of DR using the energy storage device.

[0008] The present disclosure has been made to solve the above problems, and an object thereof is to make it easy for a user to execute at least one of charging and discharging of a power storage device at an appropriate timing.

Means for Solving the Problems

[0009] According to an aspect according to the first aspect of the present disclosure, a display device as shown below is provided.

[0010] (Item 1) The display device includes a first acquisition unit that acquires a first schedule indicating a time zone in which charging or discharging of a power storage device is scheduled, a second acquisition unit that acquires a second schedule indicating a time zone in which a demand response for requesting charging or discharging of the power storage device is scheduled, and a display unit that displays a schedule screen. The display unit simultaneously displays the first schedule and the second schedule on the schedule screen in a distinguishable manner.

[0011] According to the above display device, the first schedule and the second schedule are simultaneously displayed on the schedule screen in a distinguishable manner. The user can check whether the charging or discharging schedule matches the timing of the DR by looking at the schedule screen. If the charging or discharging schedule does not match the timing of the DR, the user can change the charging or discharging schedule according to the timing of the DR. That is, it becomes easier for the user to participate in the DR that the user wants to participate in. However, if the user does not want to participate in the DR, the user does not have to change the charging or discharging schedule. According to the above configuration, it becomes easier for the user to execute at least one of charging and discharging of the power storage device at an appropriate timing.

[0012] The display device according to Item 1 above may have the configuration according to any one of Items 2 to 7 shown below.

[0013] (2) The display device according to claim 1 further has the following features. The first acquisition unit acquires a first schedule (hereinafter also referred to as a "charging schedule") indicating a time period when charging of the power storage device is scheduled, and a first schedule (hereinafter also referred to as a "discharging schedule") indicating a time period when discharging of the power storage device is scheduled. The second acquisition unit acquires a second schedule (hereinafter also referred to as a "raising DR schedule") indicating a time period when a demand response for charging the power storage device is scheduled, and a second schedule (hereinafter also referred to as a "lowering DR schedule") indicating a time period when a demand response for discharging the power storage device is scheduled. The display unit simultaneously displays the charging schedule, the discharging schedule, the raising DR schedule, and the lowering DR schedule on the schedule screen in a distinguishable manner.

[0014] According to the above display device, the user can check, by looking at the schedule screen, whether the charging schedule matches the timing of raising DR and whether the discharging schedule matches the timing of lowering DR. Therefore, it becomes easier for the user to participate in the DR in which the user wants to participate. According to the above configuration, it becomes easier for the user to execute charging and discharging of the power storage device at appropriate timings.

[0015] (3) The display device according to claim 1 or 2 further has the following features. The display device further includes a first DR distinguishing unit that distinguishes between a demand response for a power transmission and distribution utility and a demand response for a retail electricity provider. The display unit is configured to display, on the schedule screen in a distinguishable manner from each other, a second schedule indicating a time period when a demand response for a power transmission and distribution utility is scheduled and a second schedule indicating a time period when a demand response for a retail electricity provider is scheduled.

[0016] According to the above display device, DR for power transmission and distribution operators (for example, normal DR) and DR for retail electricity providers (for example, economic DR) are displayed on the schedule screen in a manner that distinguishes them from each other. Therefore, it becomes easier for the user to participate in the DR they want to participate in. Based on the above DR information, the user can easily make a plan for at least one of charging and discharging so that at least one of charging and discharging of the energy storage device is executed at an appropriate timing.

[0017] The user of the display device may be a consumer or a retail electricity provider that has entered into a contract regarding power trading (for example, power purchase or power sale) with each of the above power transmission and distribution operators and retail electricity providers.

[0018] (Item 4) The display device according to any one of Items 1 to 3 further has the following features. The display device further includes a first information management unit that manages information indicating whether the demand response is determined. The display unit is configured to display, on the schedule screen, a second schedule indicating the time zone in which the determined demand response is scheduled and a second schedule indicating the time zone in which the undetermined demand response is scheduled in a manner that distinguishes them from each other.

[0019] According to the above display device, the determined DR and the undetermined DR are displayed on the schedule screen in a manner that distinguishes them from each other. Therefore, it becomes easier for the user to participate in the DR they want to participate in. For example, the schedule of the undetermined DR may be canceled. Therefore, the user may not want to change the charging or discharging schedule accordingly. Based on the above DR information, the user can easily make a plan for at least one of charging and discharging so that at least one of charging and discharging of the energy storage device is executed at an appropriate timing.

[0020] (Item 5) The display device according to any one of Items 1 to 4 further has the following features. The display device further includes a second information management unit that manages information regarding the supply and demand situation of an external power source that is adjusted for supply and demand by demand response, and a second DR discrimination unit that discriminates demand responses according to the degree of tightness of the power supply and demand of the external power source. The display unit is configured to display the second schedules of the respective demand responses discriminated by the second DR discrimination unit in a mutually discriminated manner on the schedule screen.

[0021] The higher the degree of tightness of the power supply and demand of the external power source, the higher the tendency for the necessity of DR. According to the above display device, a plurality of types of DRs discriminated according to the degree of tightness of the power supply and demand of the external power source are displayed on the schedule screen in a mutually discriminated manner. Therefore, when the necessity of DR is high, it becomes possible to prompt the user to actively participate in DR. Based on the supply and demand situation of the external power source, the user can easily make a plan for at least one of charging and discharging of the power storage device so that at least one of charging and discharging is executed at an appropriate timing.

[0022] (Item 6) The display device according to any one of Items 1 to 5 further has the following features. The display device further includes a change unit that changes the first schedule displayed on the schedule screen in response to a user operation on the schedule screen, and a transmission unit that transmits the first schedule changed by the change unit to a first control device capable of controlling at least one of charging and discharging of the power storage device.

[0023] According to the above display device, it becomes easier for the user to change the first schedule (charging or discharging schedule) in accordance with the second schedule (DR schedule). Then, by transmitting the changed first schedule to the first control device, it becomes easier for the first control device to control the charging or discharging of the power storage device based on the changed first schedule. The schedule screen may be a touch panel screen.

[0024] The first control device may be a control device mounted on a resource including the power storage device. The resource may be an automobile, or may be a vehicle other than an automobile (such as a railway vehicle, a ship, an airplane, etc.), an unmanned moving body, an electromechanical device (such as a lighting device, an air conditioning facility, etc.), or a stationary power storage system. The resource may include at least one of an inverter that performs AC (alternating current) / DC (direct current) conversion and a DC / DC converter that performs DC / DC conversion.

[0025] (Item 7) The display device according to any one of Items 1 to 6 further has the following features. The display unit is configured to display a first schedule and a second schedule set in the same time zone on the schedule screen in an overlapping manner. The display device further includes a switching unit that switches whether to permit a second control device capable of controlling at least one of charging and discharging of the power storage device to execute charging or discharging of the power storage device according to the second schedule displayed overlapping the first schedule in response to a user operation on the schedule screen.

[0026] As described above, by displaying the first schedule and the second schedule set in the same time zone in an overlapping manner, it becomes easier for the user to grasp the DRs that can be participated in. In addition, the user can easily switch whether to participate in the DR by operating the schedule screen. The second control device may be a server that performs remote control of at least one of charging and discharging of the power storage device based on receiving the above permission.

[0027] The display unit may display whether or not the first schedule and the second schedule overlap with each other in an identifiable manner for each of the first schedule and the second schedule. The display unit may display the overlapping part (overlapping portion) and the non-overlapping part (non-overlapping portion) in an identifiable manner by changing the display mode (for example, color or pattern) between the overlapping part and the non-overlapping part for each of the first schedule and the second schedule that partially overlap.

[0028] According to an aspect according to the second aspect of the present disclosure, an energy management system as shown below is provided.

[0029] (Item 8) The energy management system includes an energy management device that requests charging or discharging of a power storage device electrically connectable to an external power source by demand response, and the display device according to any one of Items 1 to 7.

[0030] According to the above energy management system, energy management by DR can be suitably executed. In addition, any of the above-described display devices makes it easier for the user to execute at least one of charging and discharging of the power storage device at an appropriate timing.

[0031] The external power source may be a commercial power source of a retail electricity business operator, or may be a power grid that supplies power to a predetermined area (for example, a microgrid or a large-scale power grid developed as infrastructure). The external power source may supply AC power or DC power.

[0032] The energy management system according to Item 8 above may have the configuration according to Item 9 or Item 10 shown below.

[0033] (Item 9) The energy management system according to Item 8 further has the following features. The external power source is a power grid. The power storage device is a power storage device mounted on a vehicle. The first acquisition unit of the display device is configured to acquire information regarding a first schedule from an input device that receives an input from a user. The second acquisition unit of the display device is configured to acquire information regarding a second schedule from a communication device that receives information from the outside. Each of these display device, input device, and communication device is mounted on a mobile terminal that manages vehicle information.

[0034] (Item 10) The energy management system according to Item 8 further has the following features. The external power source is a power grid. The power storage device is a power storage device mounted on the vehicle. The first acquisition unit of the display device is configured to acquire information regarding a first schedule from an input device that receives an input from a user. The second acquisition unit of the display device is configured to acquire information regarding a second schedule from a communication device that receives information from the outside. Each of these display device, input device, and communication device is mounted on the vehicle.

[0035] According to the first acquisition unit, it becomes possible for the user to input an arbitrary first schedule to the display device. Also, according to the second acquisition unit, it becomes possible to receive a second schedule from an external computer. For example, an appropriate schedule may be calculated by an external computer with high computing power (for example, a cloud server). The external computer may calculate the second schedule using at least one of the supply and demand situation of the power grid, weather information, and power price information. According to the energy management system described in Item 9 or 10 above, it is possible to suitably execute energy management of the power grid using the power storage device mounted on the vehicle. Also, the vehicle user (vehicle administrator) can easily execute at least one of charging and discharging of the power storage device at an appropriate timing using the display device.

[0036] The vehicle may be an electric vehicle. An electric vehicle is an automobile that uses electric power as all or part of the power source (hereinafter also referred to as "xEV"). xEVs include BEV (battery electric vehicle), PHEV (plug-in hybrid vehicle), FCEV (fuel cell vehicle), etc. The portable terminal may be a smartphone, laptop, tablet terminal, wearable device (for example, a smartwatch or smart glasses), or an electronic key.

[0037] According to an aspect according to the third aspect of the present disclosure, information regarding at least one of charging and discharging of the power storage device is set in the information terminal, charging or discharging of the power storage device is requested to the information terminal by demand response, and the information terminal that has received the request by demand response displays, on the same schedule screen, a first schedule indicating a time period in which charging or discharging of the power storage device is scheduled and a second schedule indicating a time period in which demand response is scheduled. A schedule display method is provided that includes this.

[0038] Also according to the above schedule display method, similar to the display device described above, it becomes easier for the user to execute at least one of charging and discharging of the power storage device at an appropriate timing.

[0039] The information terminal may be the portable terminal described above, may be a stationary computer, or may be a computer mounted on a moving body such as an automobile.

Effect of the Invention

[0040] According to the present disclosure, it becomes possible to make it easier for the user to execute at least one of charging and discharging of the power storage device at an appropriate timing.

Brief Description of the Drawings

[0041]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Embodiments for Carrying Out the Invention

[0042] 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 their description will not be repeated.

[0043] FIG. 1 is a diagram showing a schematic configuration of an energy management system according to an embodiment of the present disclosure. Referring to FIG. 1, the energy management system according to this embodiment includes a vehicle group 1, an EVSE group 2, a server 700, a power generation facility 800, a server 900, and a management device 1000. The management device 1000 includes servers 200 and 500. EVSE means Electric Vehicle Supply Equipment.

[0044] Each of the servers 200, 500, 700, and 900 is a computer having, for example, an HMI (Human Machine Interface) and a communication I / F (interface). Each computer includes a processor and a storage device. The storage device stores programs executed by the processor, as well as information used by the programs (for example, maps, mathematical formulas, and various parameters). The HMI includes an input device and a display device. The HMI may be a touch panel display.

[0045] The power grid PG is a power network constructed by power transmission and distribution facilities. A plurality of power plants (not shown) are connected to the power grid PG. The power grid PG receives power supply from those power plants. In this embodiment, the power transmission and distribution operator corresponds to the TSO (system operator) of the power grid PG (commercial power supply). The power grid PG supplies alternating current power (for example, single-phase or three-phase alternating current power). The server 700 corresponds to a computer belonging to the power transmission and distribution operator. The server 700 incorporates a medium supply system (system of the central power supply command center) and a simple command system.

[0046] Server 500 communicates periodically with each vehicle included in vehicle group 1. In this embodiment, each vehicle included in vehicle group 1 is an xEV and is configured to be operable as an adjustment force for power grid PG. Each vehicle included in vehicle group 1 is a privately-owned vehicle (POV). The user of the vehicle corresponds to the administrator who manages the vehicle. The number of vehicles included in vehicle group 1 may be 5 or more and less than 30, or 30 or more and less than 100, or 100 or more. Vehicle group 1 includes vehicle 100 having a configuration (see FIG. 2) described later. The configuration of vehicle 100 and other vehicles in vehicle group 1 may be the same or different.

[0047] EVSE group 2 includes a plurality of EVSEs that receive power supply from power grid PG. Server 200 communicates with each EVSE as necessary. EVSE group 2 includes EVSE 300 having a configuration (see FIG. 2) described later. EVSE group 2 may include multiple types of EVSEs (for example, normal chargers and rapid chargers). EVSE may include both public EVSEs (for example, EVSEs installed in commercial facilities, automobile dealerships, or highway parking areas) and non-public EVSEs (for example, home EVSEs). The number of EVSEs included in EVSE group 2 is arbitrary.

[0048] Management device 1000, server 700, server 900, each vehicle included in vehicle group 1, and each EVSE included in EVSE group 2 are configured to be able to communicate with each other via communication network NW. Servers 700 and 900 communicate with server 200 via communication network NW. In management device 1000, server 200 and server 500 are configured to be able to communicate with each other. Communication network NW is a wide-area network constructed by, for example, the Internet and wireless base stations. Each vehicle is configured to access communication network NW by wireless communication and be connected to communication network NW. Each EVSE is connected to communication network NW via, for example, a communication line. Note that the communication form is not limited to the above and can be changed as appropriate. For example, each EVSE may be connected to communication network NW by wireless communication.

[0049] The server 900 corresponds to a computer belonging to a retail electricity provider. The retail electricity provider procures electric power from the electricity market (for example, the spot market and the forward market opened and operated by a wholesale electricity exchange) and the power generation facility 800 (for example, a power generation facility belonging to a power generation company with which the retail electricity provider has entered into a contract), and sells the procured electric power to a plurality of consumers. The power grid PG is configured to supply electric power to other than the EVSE group 2 shown in FIG. 1. Specifically, the power grid PG is also electrically connected to a building (for example, a house, a factory, or a commercial facility) not shown in the figure. The retail electricity provider pays a transmission fee to the transmission and distribution company, and uses the power grid PG to provide electric power to each consumer. The power generation facility 800 may include at least one of a pumped-storage power plant, a solar power plant, a wind power plant, a hydroelectric power plant, a geothermal power plant, a biomass power plant, and a nuclear power plant.

[0050] FIG. 2 is a diagram showing the configurations of the vehicle 100 and the EVSE 300. Referring to FIGS. 1 and 2 together, the EVSE 300 is configured to receive power supply from the power grid PG and perform power supply. The EVSE 300 incorporates a power circuit 310 and includes a charging cable 320. The power circuit 310 is electrically connected to the power grid PG. The charging cable 320 has a connector 320a (plug) at its tip and includes a communication line and a power line inside. One electric wire may serve as both the communication line and the power line. The power circuit 310 converts the power supplied from the power grid PG into power suitable for power supply to the vehicle 100, and outputs the converted power to the charging cable 320. The EVSE 300 outputs the power for supplying to the vehicle 100 from the connector 320a.

[0051] Vehicle 100 is provided with an inlet 60 to which a connector 320a is detachable. The inlet 60 corresponds to a charging / discharging port that functions as both a charging port and a discharging port. When the connector 320a of the charging cable 320 connected to the main body of the EVSE 300 is connected to the inlet 60 of the parked vehicle 100, the vehicle 100 is electrically connected to the power grid PG via the EVSE 300 (hereinafter, also referred to as the "plug-in state"). On the other hand, for example, during the running of the vehicle 100, the vehicle 100 is in a state of not being electrically connected to each of the EVSE 300 and the power grid PG (hereinafter, also referred to as the "plug-out state"). Note that FIG. 2 shows only the inlet 60 corresponding to the power supply method of the EVSE 300, but the vehicle 100 may be provided with a plurality of inlets so as to be compatible with a plurality of power supply methods (for example, AC method and DC method).

[0052] The vehicle 100 further includes a battery 11, an SMR (System Main Relay) 12, an MG (Motor Generator) 20, a PCU (Power Control Unit) 22, and an electronic control unit (hereinafter, referred to as "ECU (Electronic Control Unit)") 150. The ECU 150 is configured to include a processor 151, a RAM (Random Access Memory) 152, and a storage device 153. The ECU 150 may be a computer. The storage device 153 is configured to be able to store the stored information. In addition to the program, information used in the program (for example, maps, mathematical formulas, and various parameters) is stored in the storage device 153. In this embodiment, by the processor 151 executing the program stored in the storage device 153, various controls in the ECU 150 (for example, charging control and discharging control of the battery 11) are executed.

[0053] The battery 11 stores the electric power for driving the vehicle 100. The vehicle 100 is configured to be able to run using the electric power stored in the battery 11. The vehicle 100 according to this embodiment is a battery electric vehicle (BEV) that does not include an engine (internal combustion engine). As the battery 11, a known vehicle power storage device (for example, a liquid secondary battery, an all-solid-state secondary battery, or a battery pack) can be adopted. Examples of vehicle secondary batteries include lithium-ion batteries and nickel-metal hydride batteries.

[0054] The vehicle 100 further includes a monitoring module 11a that monitors the state of the battery 11. The monitoring module 11a includes various sensors that detect the state of the battery 11 (for example, voltage, current, and temperature), and outputs the detection results to the ECU 150. In addition to the above sensor functions, the monitoring module 11a may be a battery management system (BMS) that further has a state of charge (SOC) estimation function, a state of health (SOH) estimation function, a cell voltage equalization function, a diagnosis function, and a communication function. The ECU 150 can acquire the state of the battery 11 (for example, temperature, current, voltage, SOC, and internal resistance) based on the output of the monitoring module 11a.

[0055] The vehicle 100 further includes a charger 61 and a charge and discharge relay 62. The charger 61 and the charge and discharge relay 62 are located between the inlet 60 and the battery 11. Each of the charger 61 and the charge and discharge relay 62 is controlled by the ECU 150. In this embodiment, a charge and discharge line including the inlet 60, the charger 61, and the charge and discharge relay 62 is connected between the SMR 12 and the PCU 22. However, it is not limited to this, and a charge and discharge line may be connected between the battery 11 and the SMR 12.

[0056] In this embodiment, the charger / discharger 61 functions as both a charging circuit and a discharging circuit. The charger / discharger 61 charges the battery 11 using the power input from outside the vehicle to the inlet 60. The charger / discharger 61 discharges the power of the battery 11 to the outside of the vehicle through the inlet 60. The charger / discharger 61 includes a power conversion circuit. The power conversion circuit includes, for example, a bidirectional inverter. The power conversion circuit may perform DC (direct current) / AC (alternating current) conversion bidirectionally. The charge / discharge relay 62 switches the connection / disconnection of the power path from the inlet 60 to the battery 11. The vehicle 100 further includes a monitoring module 61a that monitors the state of the charger / discharger 61. The monitoring module 61a includes various sensors (for example, a current sensor and a voltage sensor) that detect the state of the charger / discharger 61, and outputs the detection result to the ECU 150.

[0057] In the plug-in vehicle 100, external charging (that is, charging of the battery 11 with power from outside the vehicle) and external power supply (that is, power supply to the outside of the vehicle with the power of the battery 11) are possible. The vehicle 100 can perform power adjustment of the power system PG by external charging and external power supply. The power for external charging is supplied, for example, from the power system PG to the inlet 60 through the charging cable 320 of the EVSE 300. The charger / discharger 61 converts the power received by the inlet 60 (for example, alternating current power) into power suitable for charging the battery 11 (for example, direct current power), and outputs the converted power to the battery 11. The power for external power supply is supplied from the battery 11 to the charger / discharger 61. The charger / discharger 61 converts the direct current power supplied from the battery 11 into power suitable for external power supply (for example, alternating current power), and outputs the converted power to the inlet 60. The vehicle 100 is configured to be able to perform reverse power flow with respect to the power system PG. When either external charging or external power supply is executed, the charge / discharge relay 62 is in a closed state (connected state), and when neither external charging nor external power supply is executed, the charge / discharge relay 62 is in an open state (disconnected state).

[0058] MG20 is, for example, a three-phase AC motor generator. MG20 functions as a driving motor for vehicle 100. MG20 is driven by PCU22 to rotate the driving wheels of vehicle 100. Also, MG20 performs regenerative power generation and outputs the generated power to battery 11. Vehicle 100 further includes a motor sensor 21 that monitors the state of MG20. Motor sensor 21 includes various sensors (for example, a current sensor, a voltage sensor, and a temperature sensor) that detect the state of MG20, and outputs the detection results to ECU150. Note that the number of driving motors provided in vehicle 100 is arbitrary and may be one, two, or three or more. The driving motor may be an in-wheel motor.

[0059] PCU22 drives MG20 using the power supplied from battery 11. SMR12 switches the connection / disconnection of the power path from battery 11 to PCU22. PCU22 is configured to include, for example, an inverter and a converter. Each of SMR12 and PCU22 is controlled by ECU150. SMR12 is in a closed state (connected state) when vehicle 100 is running. Also, SMR12 is in a closed state when power is exchanged between battery 11 and inlet 60 (and thus outside the vehicle).

[0060] Vehicle 100 further includes an HMI81, a navigation system (hereinafter also referred to as "NAVI") 82, an air conditioner 83, and a communication device 90. Battery 11 supplies power directly or indirectly to these devices (auxiliary equipment). Battery 11 may supply power to the auxiliary equipment via an auxiliary battery (not shown).

[0061] HMI81 includes an input device and a display device. HMI81 may include a touch panel display. HMI81 may include a meter panel and / or a head-up display. HMI81 may include a smart speaker that accepts voice input.

[0062] NAVI82 is configured to include a touch panel display, a GPS (Global Positioning System) module, a processor, and a storage device (none of which are shown). The storage device stores map information. The touch panel display receives input from the user and displays maps and other information. The GPS module is configured to receive signals from GPS satellites (hereinafter referred to as "GPS signals") not shown. NAVI82 is configured to detect the position of the vehicle 100 using GPS signals and display the position of the vehicle 100 on the map in real time. NAVI82 performs route search to find the optimal route (for example, the shortest route) from the current position of the vehicle 100 to the destination with reference to the map information. NAVI82 may sequentially update the map information by OTA (Over The Air).

[0063] The air conditioner 83 includes an air conditioning fan, a filter, a temperature adjustment unit, a temperature sensor, and a control device. The temperature adjustment unit may include an evaporator, a heater core, and an air mix door. The temperature sensor detects the temperature inside the passenger compartment of the vehicle 100. In the air conditioner 83, the air blown by the air conditioning fan passes through the filter and is temperature-adjusted by the temperature adjustment unit. The air conditioner 83 blows out the temperature-adjusted air into the passenger compartment of the vehicle 100. The control device of the air conditioner 83 controls the air conditioning fan and the temperature adjustment unit so that the temperature inside the passenger compartment of the vehicle 100 detected by the temperature sensor reaches a predetermined target temperature. The target temperature is set by the ECU150. The ECU150 sends a control signal to the air conditioner 83. The operation / stop of the air conditioner 83 is switched by the ECU150.

[0064] The communication device 90 is configured to include various communication I / Fs. The ECU 150 communicates with devices external to the vehicle 100 through the communication device 90. The communication device 90 includes a wireless communication device (for example, DCM (Data Communication Module)) that can access the communication network NW. The wireless communication device may include a communication I / F compatible with 5G or 6G (the 5th or 6th generation mobile communication system). The vehicle 100 performs wireless communication with each of the servers 200 and 500, for example, in both the plugged-in state and the plugged-out state. In this embodiment, the vehicle 100 receives commands or notifications from each of the servers 200 and 500 by the above wireless communication device. However, the present invention is not limited to this, and the vehicle 100 may perform wired communication with at least one of the servers 200 and 500 via the EVSE 300 in the plugged-in state.

[0065] The mobile terminal 400 is a terminal carried and operated by the administrator (vehicle user) of the vehicle 100. The mobile terminal 400 is configured to manage information of the vehicle 100. In this embodiment, a smartphone equipped with a touch panel display is adopted as the mobile terminal 400. The mobile terminal 400 corresponds to an example of the "information terminal" according to the present disclosure. However, the mobile terminal 400 is not limited to a smartphone, and any terminal can be adopted.

[0066] The communication device 90 includes a communication I / F for directly communicating with the mobile terminal 400 existing within the vehicle or in the vicinity of the vehicle. The communication device 90 and the mobile terminal 400 may perform short-range communication such as wireless LAN (Local Area Network), NFC (Near Field Communication), or Bluetooth (registered trademark). However, any communication method can be adopted as the communication method between the vehicle 100 and the mobile terminal 400.

[0067] The mobile terminal 400 is registered in advance with the servers 200 and 500 and is configured to be capable of wireless communication with the servers 200 and 500. A predetermined application software (hereinafter referred to as "mobile app") is installed in the mobile terminal 400. The servers 200 and 500 perform a predetermined authentication before starting communication with the mobile terminal and communicate only with the mobile terminals that have succeeded in the authentication. Thereby, it is possible to suppress unauthorized communication by mobile terminals not registered in the servers 200 and 500. The user of the vehicle 100 can start communication with the servers 200 and 500 by inputting predetermined authentication information (information for succeeding in the above authentication) into the mobile terminal 400. Also, by registering the predetermined authentication information in the mobile app, the input of the above authentication information can be omitted. The mobile terminal 400 can exchange information with the servers 200 and 500 through the above mobile app.

[0068] In this embodiment, the mobile terminal 400 is provided with a position sensor. The position sensor may be a sensor using GPS. The mobile terminal 400 transmits information indicating the user's position (hereinafter also referred to as "user position information") to the server 500 periodically or in response to a request from the server 500.

[0069] The on (operation) / off (stop) of the vehicle system (the system that controls the vehicle 100) including the ECU 150 is switched by the user operating the start switch 70. The start switch 70 is installed, for example, in the passenger compartment of the vehicle 100. When the start switch 70 is turned on, the vehicle system is started. Also, when the vehicle system is operating and the start switch 70 is turned off, the vehicle system enters a stopped state. However, in the vehicle 100 while it is running, the off operation of the start switch 70 is prohibited. Generally, the start switch of a vehicle is referred to as a "power switch" or an "ignition switch", etc.

[0070] Referring again to FIG. 1, the server 200 corresponds to a computer belonging to an aggregator. An aggregator is an electric utility that bundles a plurality of distributed energy resources (hereinafter, also referred to as "DER (Distributed Energy Resources)") to provide an energy management service. Although details will be described later, the aggregator executes energy management using DER. Each vehicle included in the vehicle group 1 can function as a DER. The server 200 may cause these DERs (for example, each vehicle included in the vehicle group 1) to function as a VPP (virtual power plant) by remotely and integrally controlling a plurality of DERs. Note that the server 500 may belong to an aggregator or may belong to an automobile manufacturer.

[0071] In order to integrally control a plurality of DERs as a VPP, the server 200 may perform DR (demand response) on each DER. By DR, the DER is requested to adjust the power of the power grid PG. The server 200 is configured to be able to bid in a power market (for example, a supply-demand adjustment market). The supply-demand adjustment market is a market for the TSO (transmission and distribution utility) of the power grid PG to procure regulation power. The server 200 may cause a plurality of DERs (for example, each vehicle included in the vehicle group 1) to perform the power adjustment of the power grid PG requested from the server 700 or the power adjustment of the power grid PG won in the power market using DR. In this embodiment, the power adjustment of the power grid PG corresponds to an example of the "energy management" according to the present disclosure.

[0072] By participating in DR (power regulation), flexibility and redundancy can be imparted to the power grid PG. The administrator of the DER participating in DR permits remote control to the server 200. In a situation where remote control of the DER by the server 200 is permitted, the server 200 can remotely control the DER so that power regulation of the power grid PG (for example, charging promotion, charging suppression, discharging, power consumption promotion, or power consumption suppression) is performed by the DER. When it is predicted that an imbalance will occur in the power grid PG at the same time and in the same amount, the server 200 may control the DER to eliminate the imbalance. For example, when the server 200 remotely controls the vehicle 100, the ECU 150 controls the charger / discharger 61 according to a command from the server 200. However, even if the server 200 sends a command to the DER, if the preparation of the DER for power regulation is not completed, the DER cannot perform power regulation by remote control. Therefore, the administrator of the DER participating in DR is required to complete the preparation of the DER before the start of DR.

[0073] Note that the type of power regulation is arbitrary. The power regulation may be, for example, any one of supply-demand adjustment, power source stabilization, load following, and frequency adjustment. The DER may operate as an adjustment force or a reserve force of the power grid PG by remote control.

[0074] Before starting the above-described DR, the server 200 transmits a DR request signal to the terminals set for each vehicle included in the vehicle group 1. The DR request signal requests participation in DR (power regulation). The DR request signal includes the content of the requested energy management (for example, down DR or up DR) and the DR period (DR start time and DR end time). Up DR is basically a DR that requests an increase in demand. However, when the DER receiving the request is a power generation facility, up DR may request supply suppression to the DER. On the other hand, down DR is a DR that requests demand suppression or reverse power flow. Details of the DR request signal will be described later.

[0075] Server 500 holds information about each vehicle included in vehicle group 1 (hereinafter also referred to as "vehicle information"). The vehicle information is stored in the storage device of server 500 and is updated sequentially. Server 500 communicates with each vehicle included in vehicle group 1 periodically and sequentially receives vehicle information from each vehicle. Then, server 500 updates the vehicle information in the storage device based on the received latest vehicle information. The vehicle information is distinguished by vehicle ID (vehicle identification information).

[0076] The above vehicle information includes, for example, a charging location, specifications of the power supply equipment installed at the charging location (for example, information indicating the power supply capacity), user location information (the location of the vehicle user), vehicle location information, the SOC of the in-vehicle battery, the grid connection state (plugged-in state / plugged-out state), the state of the vehicle system (on / off), information set in the navigation system (for example, the driving route to the destination), data related to the movement of the vehicle (for example, data associating the vehicle's location and time regarding the vehicle's daily movement), and data related to the behavior of the vehicle user (for example, data associating the user's location and time regarding the user's daily behavior). Also, when the specifications differ for each vehicle, the specifications of each vehicle (for example, the specs regarding charging and discharging) may be registered in server 500 in advance.

[0077] The charging location of vehicle 100 shown in FIG. 2 may be the vehicle user's home (for example, the installation location of EVSE300). In this embodiment, during the driving of vehicle 100, each of the location of vehicle 100 and the SOC of battery 11 is sequentially transmitted from vehicle 100 to server 500 in real time. Also, at the timing when the plugged-in state and the plugged-out state of vehicle 100 are switched, the latest grid connection state is transmitted from vehicle 100 to server 500. Also, at the timing when the on / off of the vehicle system in vehicle 100 is switched, the latest state of the vehicle system is transmitted from vehicle 100 to server 500. Also, when a destination is set in NAVI82, the driving route searched by NAVI82 is transmitted from vehicle 100 to server 500.

[0078] Server 200 can obtain the above-mentioned vehicle information from server 500. Server 500 transmits vehicle information to server 200 in response to a request from server 200, for example. Also, server 500 may transmit vehicle information to server 200 periodically. At the start of power adjustment (DR start time), server 200 determines whether the preparation for power adjustment for each vehicle is completed based on the vehicle information of each vehicle received from server 500. Hereinafter, among the vehicle group 1, a vehicle for which the preparation for power adjustment is completed is also referred to as a "standby vehicle". When a vehicle satisfies a predetermined requirement (hereinafter, also referred to as a "standby requirement"), server 200 determines that the preparation for power adjustment for the vehicle is completed. The standby requirements according to this embodiment include that the vehicle is in a plugged-in state (first SBY requirement), the SOC of the in-vehicle battery is within a predetermined SOC range (second SBY requirement), and remote control by server 200 is permitted (third SBY requirement). In order for the standby requirements to be satisfied, all of the first to third SBY requirements must be satisfied.

[0079] Regarding the first SBY requirement, for example, when the connector 320a of the charging cable 320 connected to the main body of the EVSE 300 is connected to the inlet 60 of the vehicle 100, the vehicle 100 is in a plugged-in state (see FIG. 2). The plugged-in vehicle 100 is electrically connected to the power grid PG.

[0080] Regarding the second SBY requirement, the above-mentioned predetermined SOC range is set by server 200, for example. The predetermined SOC range is set to a range corresponding to the power adjustment of the power grid PG requested by DR. For example, in an up-DR that requests an increase in demand (for example, charging of the energy storage device), server 200 may lower the upper limit value of the above-mentioned predetermined SOC range, and in a down-DR that requests reverse power flow (for example, discharging of the energy storage device), server 200 may raise the lower limit value of the above-mentioned predetermined SOC range.

[0081] Regarding the 3rd SBY requirement, the ECU 150 (control device of the vehicle 100) shown in FIG. 2 permits remote control by the server 200 in a predetermined charging mode (permission mode). Although details will be described later, the permission mode in this embodiment includes a first charging mode (hereinafter also referred to as the "smart charging mode") and a second charging mode (hereinafter also referred to as the "entrusted charging mode"). When the smart charging mode or the entrusted charging mode is set in the ECU 150, remote charging control and remote discharging control of the battery 11 by the server 200 are permitted.

[0082] The server 200 determines whether each vehicle that has requested DR by a DR request signal in advance satisfies the above first to third SBY requirements at the DR start time. Then, the server 200 selects a vehicle for power adjustment from among the standby vehicles that satisfy the first to third SBY requirements, and transmits a command for remote control (hereinafter also referred to as a "VPP command") to the selected vehicle. The number of vehicles required for power adjustment is selected. The VPP command is, for example, a command for remote charging control or remote discharging control. The server 200 performs power adjustment of the power grid PG by causing the battery of the selected vehicle to be charged or discharged by remote control. Hereinafter, a vehicle that has performed power adjustment according to the VPP command is also referred to as a "VPP vehicle".

[0083] In the energy management system according to this embodiment, an incentive is given to the administrator of the DER as a price for energy management using the DER. For example, each user (administrator) of the vehicles included in the vehicle group 1 can conclude a contract with an aggregator in advance and receive a predetermined incentive when a predetermined requirement is satisfied. For example, when a vehicle performs power adjustment according to the VPP command, the second incentive requirement described later is satisfied, and an incentive is given from the aggregator to the vehicle user.

[0084] Server 200 is configured to manage incentives given to an administrator who manages each vehicle included in vehicle group 1. Each vehicle included in vehicle group 1 corresponds to a resource that can be electrically connected to power grid PG. Specifically, server 200 manages incentives for each vehicle (e.g., vehicle user) by distinguishing them with vehicle IDs. For example, the power (power flow / reverse power flow) exchanged between power grid PG and EVSE may be detected by a predetermined electricity meter (e.g., at least one of a smart meter installed at the power receiving point and an electricity meter built into EVSE) and transmitted to server 200. Server 200 may determine whether power adjustment according to the VPP command has been performed by the vehicle using the detection value by the above-mentioned predetermined electricity meter.

[0085] Server 200 holds data regarding incentives for users (administrators) of each vehicle included in vehicle group 1 (hereinafter, also referred to as "incentive data"). Server 200 updates the incentive data so as to give an incentive corresponding to the satisfied requirement to the vehicle user when the vehicle satisfies a predetermined requirement. Specifically, when the vehicle satisfies predetermined first and second incentive requirements, server 200 gives the first and second incentives to the vehicle user, respectively, and reflects the result in the incentive data.

[0086] Specifically, when the vehicle 100 shown in FIG. 2 is in the plugged-in state (i.e., when the inlet 60 is electrically connected to the power grid PG), the first incentive requirement is satisfied, and the first incentive is given to the user of the vehicle 100. That is, the first incentive is given to the user of the vehicle that satisfies the first SBY requirement.

[0087] When the plugged-in vehicle 100 performs charge and discharge of the battery 11 for power adjustment of the power grid PG, the second incentive requirement is satisfied, and the second incentive is given to the user of the vehicle 100. That is, the second incentive is given to the user of the VPP vehicle.

[0088] The server 200 may calculate the first and second incentives based on a predetermined incentive unit price. The unit price of each of the first and second incentives is arbitrarily determined by the contract. The incentive may be a general currency or a virtual currency. The incentive may also be points exchangeable for goods or services at a predetermined store.

[0089] The server 200 is configured to perform a movement prediction for each vehicle included in the vehicle group 1. The server 200 performs a movement prediction for each vehicle based on, for example, the vehicle information of each vehicle received from the server 500. The server 200 executes the prediction every time it receives new information from the server 500. The server 200 improves the prediction accuracy by performing the prediction based on the latest information.

[0090] The server 200 may obtain a driving plan from the information set in the navigation system. Examples of the driving plan include the departure location, the departure time from the departure location, the destination, the arrival time at the destination, and the driving route to the destination. The server 200 can predict the movement schedule of the vehicle (the future transition of the vehicle's position) from the driving plan of the vehicle. The server 200 may presume that the vehicle is in a parked state when the vehicle system switches from on to off. When the parked state of the vehicle continues for a predetermined time or longer, the server 200 may presume that the vehicle exists at the user's home or workplace. When the vehicle system switches from off to on, the server 200 may predict that the vehicle will depart after a predetermined time. The server 200 may predict the arrival time at the destination and the SOC at the time of arrival of the vehicle while tracking the position of the vehicle using the position information and SOC information of the vehicle. The server 200 may predict the movement schedule of the vehicle from the historical data related to the movement of the vehicle (for example, weather information, traffic jam information, and past position data managed separately by day of the week).

[0091] Server 200 may predict the user's action schedule (the future movement of the user's position) and predict the vehicle's movement schedule from the predicted user's action schedule. Server 200 may determine whether the user is on board the vehicle based on the position information of each of the vehicle and the user. Server 200 may predict the future behavior of the user while tracking the position of the user after getting off the vehicle using the user's position information. Server 200 may predict the user's action schedule from historical data related to the user's actions (for example, weather information, traffic jam information, and past position data managed separately by day of the week).

[0092] When the mobile app is launched on the mobile terminal 400, the mobile app requests user authentication (login). The user can log in by inputting predetermined authentication information into the mobile terminal 400. The mobile terminal 400 can obtain information (for example, incentive data) about the user who has logged in to the mobile app from the server 200. After logging in, the mobile terminal 400 displays screen A shown in FIG. 3.

[0093] FIG. 3 is a diagram for explaining screen A displayed on the touch panel display of the mobile terminal 400. Referring to FIG. 3 together with FIGS. 1 and 2, screen A includes first to fifth operation parts OP1 to OP5 and an information part IN. When the fifth operation part OP5 is operated, the mobile terminal 400 executes a screen update process so that the latest information is displayed on screen A. The mobile terminal 400 may request the latest information from at least one of the vehicle 100 and the server 200 when the fifth operation part OP5 is operated. Even when a predetermined time has elapsed without the fifth operation part OP5 being operated since the previous screen update, the mobile terminal 400 executes the above screen update process. The information part IN indicates the time (update date and time) when the screen was last updated.

[0094] The first to fourth operation units OP1 to OP4 receive a screen designation. The mobile terminal 400 performs screen switching according to an input from the user and displays the screen designated by the user. For example, when the second operation unit OP2 (charging setting button) is operated on screen A or screen C (FIG. 6) or screen D (FIG. 13) described later, the mobile terminal 400 displays screen B shown in FIG. 4 described later. Also, when the third operation unit OP3 (setting button) is operated on any of screens A, B, and D, the mobile terminal 400 displays screen C shown in FIG. 6. Further, when the fourth operation unit OP4 (charging history button) is operated on any of screens A to C, the mobile terminal 400 displays screen D shown in FIG. 13. And when the first operation unit OP1 (vehicle information button) is operated on any of screens B to D, the mobile terminal 400 displays screen A shown in FIG. 3.

[0095] Screen A is a screen for displaying information about the vehicle 100. Screen A further includes information units IN11 to IN15 and operation units OP11 and OP12.

[0096] The information unit IN11 indicates the current SOC of the battery 11 (for example, the detection value by the monitoring module 11a). The information unit IN12 indicates the charging state of the battery 11 (for example, any one of charging waiting / charging in progress / charging completed). The information unit IN13 indicates information regarding the next charge (for example, the charge end time and the SOC at the end of charging). When the next charge is not set, the mobile terminal 400 may cause the information unit IN13 to display a message indicating that the next charge is not set.

[0097] The operation unit OP11 receives an instruction to start external charging. The information unit IN14 indicates an explanation of the operation unit OP11 (for example, "Charge immediately"). The operation unit OP12 receives an instruction to stop external charging. The information unit IN15 indicates an explanation of the operation unit OP12 (for example, "Stop charging"). When the operation unit OP11 (toggle switch) is turned on by the user, the mobile terminal 400 requests the vehicle 100 (ECU150) to start external charging, and in response to this request, the ECU150 starts external charging of the battery 11. In this embodiment, charging of the battery 11 is executed according to the operation on the operation unit OP11. Then, when the user turns on the operation unit OP12 (toggle switch) during external charging of the battery 11, the mobile terminal 400 requests the vehicle 100 (ECU150) to end external charging, and in response to this request, the ECU150 stops external charging of the battery 11. Also, when the battery 11 reaches a fully charged state during external charging, the ECU150 stops external charging of the battery 11.

[0098] The presence or absence of the display of each of the operation units OP11 and OP12 may be controlled by the mobile terminal 400. When the vehicle 100 is not in a plugged-in state, the mobile terminal 400 may not display the operation units OP11 and OP12. When external charging is being executed, the mobile terminal 400 may not display the operation unit OP11. When external charging is not being executed, the mobile terminal 400 may not display the operation unit OP12. According to such a display mode, it becomes easier for the user to grasp the charging state of the battery 11. Each operation unit cannot be operated when it is not displayed. The mobile terminal 400 can prohibit the operation on the operation unit by making the operation unit non-displayed.

[0099] FIG. 4 is a diagram for explaining a screen B displayed on the touch panel display of the mobile terminal 400. The first to fifth operation units OP1 to OP5 and the information unit IN in the screen B shown in FIG. 4 are the same as those in the screen A (FIG. 3). Also, the screen update process in the screen B is the same as the screen update process in the screen A described above.

[0100] Referring to FIG. 4 together with FIGS. 1 to 3, screen B is a screen that displays information regarding the next charging timer setting in vehicle 100. Screen B further includes information sections IN21 to IN24 and operation sections OP21 to OP24.

[0101] Information section IN21 indicates information regarding the next charge (for example, the scheduled charge date and the scheduled departure time of vehicle 100). The scheduled departure time may be the same as the charge end time (FIG. 3). When the user touches the area of information section IN21 on screen B (touch panel screen), the mobile terminal 400 may perform a screen switch to a screen for changing the next charge schedule (for example, the screen shown in FIG. 9 described later).

[0102] Information section IN22 indicates the current target SOC. The target SOC may be the same as the SOC at the end of charging (FIG. 3). Information section IN23 indicates the current SOC of battery 11. Operation section OP22 accepts an input of the target SOC. When a target SOC lower than the current SOC of battery 11 indicated by information section IN23 is input by operation section OP22, the mobile terminal 400 may display a confirmation message such as "The target SOC is lower than the current SOC. Is this okay?" on the mobile terminal 400.

[0103] Operation section OP23 accepts an instruction on whether to set the smart charging mode for vehicle 100 (ECU150). Information section IN24 indicates the operation state (ON / OFF) of operation section OP23.

[0104] Operation section OP24 accepts an input indicating the determination of the change content. The inputs for each of operation sections OP22 and OP23 become valid when operation section OP24 is operated.

[0105] Specifically, the information section IN22 indicates the target SOC by means of an SOC bar with the left side being the low SOC side and the right side being the high SOC side. The current SOC of the battery 11 is indicated by the information section IN23 (indicator) provided for this SOC bar. After the user changes the target SOC by sliding the operation section OP22 (slider) left or right, the user can reflect the changed target SOC in the charge control by operating the operation section OP24. Also, after the user turns on or off the operation section OP23 (toggle switch), the user can set the smart charge mode in the ECU150 or cancel the smart charge mode set in the ECU150 by operating the operation section OP24. When the operation section OP24 is operated, the mobile terminal 400 requests the vehicle 100 (ECU150) to change the charge control conditions (more specifically, change to the conditions specified by the operation sections OP22 and OP23), and in response to this request, the ECU150 changes the charge control conditions of the battery 11.

[0106] Note that the mobile terminal 400 may display, in the screen B, an operation section for receiving an instruction on whether to set the leave-it-to-charge mode in the vehicle 100 (ECU150) instead of or in addition to the above-described operation section OP23.

[0107] When the operation section OP21 (schedule button) is operated on the screen B, the mobile terminal 400 displays a charge / discharge schedule screen shown in FIG. 5. FIG. 5 is a diagram for explaining the charge / discharge schedule screen displayed on the touch panel display of the mobile terminal 400. The first to fifth operation sections OP1 to OP5 and the information section IN in the charge / discharge schedule screen shown in FIG. 5 are the same as those in the screen A (FIG. 3). Also, the screen update process in the charge / discharge schedule screen is the same as the screen update process in the above-described screen A.

[0108] Referring to FIGS. 1 to 3 and FIG. 5, the charge and discharge schedule screen is a screen that displays the charge and discharge schedule of the vehicle 100 for a predetermined period. In the charge and discharge schedule screen shown in FIG. 5, the predetermined period is set as one week from today (May 22 to May 28), but the predetermined period can be set arbitrarily. The predetermined period may be variable according to the request from the user.

[0109] The charge and discharge schedule screen includes an information section T10, an operation section T20, charge schedules T11 to T17, a boost DR schedule T21 to T23, and a lower DR schedule T41, T42.

[0110] The information section T10 indicates the current time. Each of the charge schedules T11 to T17 indicates the time period when charging (external charging) of the battery 11 is scheduled. The upward arrow (for example, the arrow M1 attached to the charge schedule T12) attached to each of the charge schedules T11 to T17 indicates that each schedule is a charge schedule rather than a discharge schedule. However, the method of distinguishing between the charge schedule and the discharge schedule is not limited to the method of distinguishing by the direction of the arrow. The mobile terminal 400 may distinguish between the charge schedule and the discharge schedule by changing marks, images, colors, sizes, shapes, patterns, etc.

[0111] Each of the upward DR schedules T21 to T23 indicates the time period during which a DR (upward DR) requesting charging of the battery 11 is scheduled. More specifically, each of the upward DR schedules T21 and T22 indicates the time period during which a DR for the power transmission and distribution utility (for example, normal DR) is scheduled. The upward DR schedule T23 indicates the time period during which a DR for the retail electricity provider (for example, economic DR) is scheduled. The upward DR schedules T21, T22 and the upward DR schedule T23 are simultaneously displayed on the charge / discharge schedule screen in a distinguishable manner from each other. The mobile terminal 400 according to this embodiment displays the upward DR schedules T21, T22 and the upward DR schedule T23 in a distinguishable manner by changing their patterns, but the method of distinguishing them is arbitrary. The mobile terminal 400 may distinguish the DR schedule for the power transmission and distribution utility from the DR schedule for the retail electricity provider by changing the mark, image, color, size, shape, etc. for display.

[0112] Each of the downward DR schedules T41 and T42 indicates the time period during which a DR (downward DR) requesting discharge of the battery 11 is scheduled. More specifically, the downward DR schedule T41 indicates the time period during which a DR for the retail electricity provider (for example, economic DR) is scheduled. The downward DR schedule T42 indicates the time period during which a DR for the power transmission and distribution utility (for example, normal DR) is scheduled. The downward DR schedule T41 and the downward DR schedule T42 are simultaneously displayed on the charge / discharge schedule screen in a distinguishable manner from each other. The mobile terminal 400 according to this embodiment displays the downward DR schedule T41 and the downward DR schedule T42 in a distinguishable manner by changing their patterns, but the method of distinguishing them is arbitrary.

[0113] Among the upload DR schedules T21 to T23 and the download DR schedules T41 and T42, the upload DR schedule T22 corresponds to an undetermined DR schedule, and the schedules other than the upload DR schedule T22 correspond to determined DR schedules. A frame M2 is attached to the upload DR schedule T22. The mobile terminal 400 according to this embodiment displays the determined DR schedule and the undetermined DR schedule in a distinguishable manner by attaching a predetermined mark (frame M2) to the undetermined DR schedule. However, the method of distinguishing between them is arbitrary. The mobile terminal 400 may distinguish the determined DR schedule and the undetermined DR schedule by changing the display of marks, images, colors, sizes, shapes, etc.

[0114] Among the upload DR schedules T21 to T23 and the download DR schedules T41 and T42, the download DR schedule T42 corresponds to a DR (hereinafter also referred to as "high-demand DR") requested in a situation where the power supply and demand of the power system PG is highly strained, and the schedules other than the download DR schedule T42 correspond to DRs (hereinafter also referred to as "low-demand DRs") requested in a situation where the power supply and demand of the power system PG is less strained. A mark M3 is attached to the download DR schedule T42. The mobile terminal 400 according to this embodiment displays the schedules of multiple types of DRs requested in situations with different degrees of power supply and demand strain in a distinguishable manner by attaching a predetermined mark (mark M3) to the high-demand DR schedule. However, the method of distinguishing between them is arbitrary. The mobile terminal 400 may distinguish the schedules of multiple types of DRs requested in situations with different degrees of power supply and demand strain by changing the display of marks, images, colors, sizes, shapes, etc.

[0115] As described above, the mobile terminal 400 simultaneously displays the charging schedules T11 to T17, the upload DR schedules T21 to T23, and the download DR schedules T41 and T42 on the same screen (charge and discharge schedule screen). The method by which the mobile terminal 400 acquires each schedule will be described later (see FIG. 14).

[0116] The operation unit T20 receives an instruction to return the screen. When the operation unit T20 (the back button) is operated by the user, the mobile terminal 400 displays the aforementioned screen B.

[0117] FIG. 6 is a diagram for explaining a screen C displayed on the touch panel display of the mobile terminal 400. The first to fourth operation units OP1 to OP4 in the screen C shown in FIG. 6 are the same as those in the screen A (FIG. 3).

[0118] Referring to FIGS. 1 to 3 and FIG. 6, the screen C is a screen for setting the charge and discharge of the battery 11. The screen C further includes operation units OP31, OP34, and OP35. When the operation unit OP31 (charge timer setting button) is operated on the screen C, the mobile terminal 400 displays a charge timer setting screen shown in FIG. 7.

[0119] FIG. 7 is a diagram for explaining a charge timer setting screen displayed on the touch panel display of the mobile terminal 400. Referring to FIG. 7, the charge timer setting screen displays set charge schedules Sc1 to Sc5. The charge timer setting screen includes an operation unit OP310. The operation unit OP310 receives an addition of a charge schedule. When the operation unit OP310 (add button) is operated on the charge timer setting screen, the mobile terminal 400 displays a screen (schedule registration screen) for adding a charge schedule.

[0120] FIG. 8 is a diagram for explaining a schedule registration screen displayed on the touch panel display of the mobile terminal 400. Referring to FIG. 8, the schedule registration screen includes operation units OP320 to OP326. The operation units OP321, OP322, OP323, OP324, and OP325 respectively receive inputs of day of the week, charging end time, charging start time, target SOC, and pre-air conditioning temperature. The operation unit OP326 receives an input indicating that the input of the charging schedule is completed. After the user inputs the day of the week, charging end time, charging start time, target SOC, and pre-air conditioning temperature by the operation units OP321 to OP325 (drum roll), by operating the operation unit OP326 (registration button), the user can register the charging schedule for the day of the week specified by the operation unit OP321 in the mobile app. The charging schedule thus registered includes the charging end time, charging start time, target SOC, and pre-air conditioning temperature specified by the operation units OP322 to OP325. The user can simultaneously register the same charging schedule for a plurality of days of the week by selecting a plurality of days of the week by the operation unit OP321. However, it is not essential for the charging schedule to include the charging start time and the pre-air conditioning temperature. The charging schedule is established as long as at least the day of the week, the charging end time, and the target SOC are input. The registered charging schedule (set charging schedule) is added to the charging timer setting screen shown in FIG. 7.

[0121] When the operation unit OP326 (registration button) or the operation unit OP320 (back button) is operated by the user, the mobile terminal 400 displays the above-described charging timer setting screen (FIG. 7). When the user touches any of the areas of the charging schedules Sc1 to Sc5 on the charging timer setting screen (touch panel screen) shown in FIG. 7, the mobile terminal 400 displays a screen (schedule change screen) for changing or deleting the charging schedule (designated charging schedule) touched by the user.

[0122] FIG. 9 is a diagram for explaining a schedule change screen displayed on the touch panel display of the mobile terminal 400. Referring to FIG. 9, the schedule change screen includes operation units OP330 to OP337. The operation units OP331, OP332, OP333, OP334, and OP335 respectively accept input of day of the week, charge end time, charge start time, target SOC, and pre-air conditioning temperature. The operation unit OP336 accepts an input indicating that the change of the charging schedule has been completed. The operation unit OP337 accepts a deletion instruction for the charging schedule. After the user changes at least one of the day of the week, charge end time, charge start time, target SOC, and pre-air conditioning temperature of the specified charging schedule by the operation units OP331 to OP335 (drum roll), the user can change the charging schedule by operating the operation unit OP336 (change button). Also, when the operation unit OP337 (delete button) is operated, the specified charging schedule is deleted. The changed or deleted content is reflected on the charging timer setting screen shown in FIG. 7.

[0123] When the operation unit OP336 (change button), the operation unit OP337 (delete button), or the operation unit OP330 (back button) is operated by the user, the mobile terminal 400 displays the above-described charging timer setting screen (FIG. 7).

[0124] Referring to FIG. 7 again, the charging timer setting screen further includes operation units OP311 to OP315. The operation units OP311 to OP315 are provided for the charging schedules Sc1 to Sc5 and receive an instruction on whether to enable the corresponding charging schedule. When any one of the operation units OP311 to OP315 (toggle switches) is turned on, the corresponding charging schedule becomes effective. Then, the mobile terminal 400 requests the vehicle 100 (ECU150) to externally charge the battery 11 according to the enabled charging schedule. In response to this request, the enabled charging schedule is set in the ECU150. The switching between the enabled and disabled states of the charging schedule by the operation units OP311 to OP315 is reflected on the charge / discharge schedule screen shown in FIG. 5. Note that it is prohibited to simultaneously enable charging schedules with overlapping time zones.

[0125] The charging timer setting screen includes an operation unit OP316. When the operation unit OP316 (return button) is operated by the user, the mobile terminal 400 displays the aforementioned screen C (FIG. 6). When the operation unit OP34 (VPP setting button) is operated on the screen C shown in FIG. 6, the mobile terminal 400 displays the VPP setting screen shown in FIG. 10.

[0126] FIG. 10 is a diagram for explaining the VPP setting screen displayed on the touch panel display of the mobile terminal 400. Referring to FIG. 10, the VPP setting screen is a screen for setting the charging mode and the minimum SOC. The VPP setting screen includes operation units OP340 to OP343.

[0127] The operation unit OP341 receives an instruction on whether to set the smart charging mode in the vehicle 100 (ECU150). The operation unit OP342 receives an instruction on whether to set the let - it - charge mode in the vehicle 100 (ECU150). Note that the operation unit OP341 and the operation unit OP342 are interlocked with each other. When the operation unit OP341 (toggle switch) is turned on, the operation unit OP342 becomes off, and when the operation unit OP342 (toggle switch) is turned on, the operation unit OP341 becomes off.

[0128] One of three charging modes is set for the vehicle 100 (ECU 150) by the operation units OP341 and OP342. Specifically, when the operation unit OP341 is turned on, the smart charging mode is set for the ECU 150. When the operation unit OP342 is turned on, the leave-it-to-me charging mode is set for the ECU 150. When both the operation units OP341 and OP342 are in the OFF state, the third charging mode (hereinafter also referred to as the "normal charging mode") is set for the ECU 150. However, when none of the charging schedules set for the mobile terminal 400 are valid, the transition operation to the smart charging mode (for example, turning on the operation unit OP341) is prohibited.

[0129] The mobile terminal 400 transmits the charging mode set by the operation units OP341 and OP342, together with a valid charging schedule (see FIG. 7), to each of the vehicle 100 and the server 200. The vehicle 100 sets the charging mode received from the mobile terminal 400 for the ECU 150. The ECU 150 executes charging control of the battery 11 according to the set charging mode. The ECU 150 permits remote control of the battery 11 by the server 200 (for example, remote charging control and remote discharging control according to a VPP command) in each of the smart charging mode and the leave-it-to-me charging mode. On the other hand, the ECU 150 does not permit remote control of the battery 11 by the server 200 in the normal charging mode.

[0130] The operation unit OP343 receives an input of the minimum SOC. When the minimum SOC is input by the operation unit OP343 (drum roll), the mobile terminal 400 requests the vehicle 100 (ECU 150) to perform charge / discharge control according to the input minimum SOC, and in response to this request, the ECU 150 changes the conditions for charge / discharge control of the battery 11. The ECU 150 that has received the above request performs charge / discharge control (control of external charging and external power supply) of the battery 11 so that the SOC of the battery 11 does not fall below the minimum SOC.

[0131] FIG. 11 is a diagram for explaining three types of charge modes (normal charge mode, smart charge mode, and leave-it-to-me charge mode) that can be set for the vehicle 100. Hereinafter, an example will be described in which user requirements regarding charging are defined by the charge end time and the target SOC. However, this is not restrictive, and the user requirements may be defined by at least one of the charge start time (see FIGS. 8 and 9), the pre-air conditioning temperature (see FIGS. 8 and 9), and the minimum SOC (FIG. 10) in addition to or instead of the charge end time and the target SOC. When the user requirements include the charge start time, the ECU 150 may perform charge and discharge control of the battery 11 so that external charging of the battery 11 is started at that time. Further, when the user requirements include the pre-air conditioning temperature, the ECU 150 may control the air conditioner 83 so that the temperature inside the vehicle compartment of the vehicle 100 becomes the pre-air conditioning temperature at the charge end time. Further, when the user requirements include the minimum SOC, the ECU 150 may perform charge and discharge control of the battery 11 so that the SOC of the battery 11 does not fall below the minimum SOC. Further, when the vehicle 100 is in the plugged-in state with the SOC of the battery 11 being below the minimum SOC, the ECU 150 may immediately start external charging of the battery 11 and end the external charging when the SOC of the battery 11 reaches the minimum SOC.

[0132] Referring to FIG. 11, the mobile terminal 400 sets the charge mode selected by the user as described above for the vehicle 100 (ECU 150). The mobile terminal 400 transmits the charge mode set by the operation units OP341 and OP342 (FIG. 10) to the vehicle 100 together with the set schedule for the next charge. The charge mode and the charge schedule received by the vehicle 100 are set in the ECU 150. The ECU 150 performs charge control of the battery 11 according to the set charge mode.

[0133] At least one of the servers 200 and 500 receives, from the mobile terminal 400, information regarding the charge mode and the charge schedule of the vehicle 100 (battery 11) (for example, information defining the user requirements described later).

[0134] When the charging mode of the vehicle 100 is the normal charging mode, the mobile terminal 400 does not permit remote control by the server 200. The ECU 150 executes charging of the battery 11 in local control. In the vehicle 100 set to the normal charging mode, different charging controls are executed according to whether the next charging (timer charging) is reserved in the ECU 150. When at least one charging schedule is enabled on the charging timer setting screen (Fig. 7), the next charging (timer charging) is reserved in the ECU 150. The ECU 150 (ECU without timer setting) in which the normal charging mode is set and the next charging is not reserved executes immediate charging as shown by line L1. Immediate charging is external charging that starts immediately when the vehicle 100 is in the plugged-in state. The immediate charging according to this embodiment ends when the battery 11 is fully charged.

[0135] The ECU 150 (ECU with timer setting) in which the normal charging mode is set and the next charging is reserved executes the reserved next charging (specifically, charging of the battery 11 according to a valid charging schedule) as shown by line L2. In Fig. 11, the charging end time and the target SOC of the next charging reserved in the ECU 150 by the user are the coordinate values S A (end time A1 and target value A2) in the two-dimensional graph of time and SOC. The user requirements are defined by the coordinate values S A . The user requirements according to the coordinate values S A are that the SOC of the battery 11 is equal to or higher than the target value A2 at the end time A1. The ECU with timer setting executes charging in the period immediately before the end time A1. Charging is started so that the SOC of the battery 11 reaches the target value A2 at the end time A1. Thereby, the user requirements are satisfied. By executing charging immediately before the end time A1, the time during which the vehicle 100 is left in a state where the SOC of the battery 11 is high is shortened, and deterioration of the battery 11 is suppressed. The charge amount A3 indicates the amount of electric power input to the battery 11 by charging according to the coordinate values S A .

[0136] When the charging mode of the vehicle 100 is the smart charging mode, the mobile terminal 400 permits the server 200 to remotely control the vehicle 100. However, the mobile terminal 400 does not permit the server 200 to change the user requirements (coordinate value S A ). Specifically, by setting the smart charging mode in the vehicle 100 (ECU 150) by the mobile terminal 400, remote control of the battery 11 by the server 200 is permitted. The ECU 150 in which the smart charging mode is set permits the server 200 to smart charge the battery 11 during the smart charging period A4 from the time when the vehicle 100 returns home (at the time of plugging in) to the end time A1. In the smart charging of the battery 11 in the smart charging mode, as long as the user requirements according to the coordinate value S A are satisfied, the server 200 can freely charge and discharge the battery 11. The server 200 determines the charging schedule and the discharging schedule during the smart charging period A4 and transmits them to each of the vehicle 100 and the mobile terminal 400. The mobile terminal 400 reflects the received charging and discharging schedule on the charging and discharging schedule screen shown in FIG. 5. The SOC of the battery 11 increases by the amount of the charging amount A3 from the SOC at the time when the vehicle 100 returns home by smart charging.

[0137] The ECU 150 in which the entrusted charging mode is set permits the server 200 to set the user requirements and to smart charge the battery 11 according to the set user requirements. The server 200 can set the user requirements by using the result of the movement prediction of the vehicle 100 described above. The server 200 may perform the movement prediction of the vehicle 100 by using the learned model obtained by machine learning using AI (artificial intelligence). Until the learning is completed, the operation of shifting to the entrusted charging mode (for example, the ON operation of the operation unit OP342 shown in FIG. 10) may be prohibited. When the learning for movement prediction is completed, the mobile terminal 400 may pop-up display a summary explanation of the entrusted charging mode.

[0138] For the vehicle 100 with the entrusted charging mode set, the server 200 sets user requirements (charging end time and target SOC) using the result of the movement prediction of the vehicle 100. Specifically, the server 200 obtains the scheduled departure time and the amount of power consumed in the next use (for example, the amount of power required for the next driving) from the predicted movement schedule of the vehicle 100. Then, the server 200 sets the obtained scheduled departure time as the charging end time of the next charge, and sets the target SOC of the next charge so that the amount of power (an appropriate amount of power without excess or deficiency) that meets the next use is stored in the battery 11. In FIG. 11, the charging end time and the target SOC of the next charge set by the server 200 in the ECU 150 are shown as coordinate values S B (end time B1 and target value B2) in the two-dimensional graph of time and SOC. If user requirements (coordinate values S A ) have already been set, the server 200 changes the user requirements from the coordinate values S A to the coordinate values S B . The user requirements according to the coordinate values S B are that the SOC of the battery 11 is equal to or higher than the target value B2 at the end time B1.

[0139] By setting the entrusted charging mode in the vehicle 100 (ECU 150) by the mobile terminal 400, remote control of the battery 11 by the server 200 is permitted. The ECU 150 with the entrusted charging mode permitted the server 200 to perform smart charging of the battery 11 during the smart charging period B4 from the time when the vehicle 100 returns home (the plug-in time point) to the end time B1. In the smart charging of the battery 11 in the entrusted charging mode, as long as the user requirements according to the coordinate values S B are satisfied, the server 200 can freely charge and discharge the battery 11. The server 200 determines the charging schedule and the discharging schedule during the smart charging period B4, and transmits them to each of the vehicle 100 and the mobile terminal 400. The mobile terminal 400 reflects the received charge and discharge schedule on the charge and discharge schedule screen shown in FIG. 5. The SOC of the battery 11 increases by the amount of charge B3 from the SOC at the time when the vehicle 100 returns home (the plug-in time point) by smart charging.

[0140] When vehicle 100 is selected as a resource for DR, the mobile terminal 400 receives a DR request signal from the server 200. The server 200 can perform charge and discharge control of the battery 11 for energy management (power adjustment of the power grid PG) requested by DR during the smart charging period A4 or B4. During the smart charging period A4 or B4, the server 200 executes energy management (power adjustment of the power grid PG) by transmitting the aforementioned VPP command to the vehicle 100. When the vehicle 100 participates in DR, the charging mode of the vehicle 100 is in the smart charging mode or the leave-it-to-me charging mode, and the vehicle 100 charges or discharges the battery 11 according to the VPP command from the server 200. In this way, by remotely controlling the vehicle 100 by the server 200, the energy management requested by DR is executed.

[0141] Referring to FIG. 10 again, when the operation unit OP340 (return button) is operated by the user on the VPP setting screen, the mobile terminal 400 displays the aforementioned screen C (FIG. 6). When the operation unit OP35 (other settings button) is operated on the screen C shown in FIG. 6, the mobile terminal 400 displays the other settings screen shown in FIG. 12.

[0142] FIG. 12 is a diagram for explaining the other settings screen displayed on the touch panel display of the mobile terminal 400. Referring to FIG. 12, the other settings screen is a screen for setting related to the mobile application. The other settings screen includes operation units OP350 to OP352.

[0143] The operation unit OP351 receives an instruction on whether to enable automatic login (automatic sign-in). When the operation unit OP351 (toggle switch) is turned on, automatic login is enabled and user authentication at the next mobile app startup is omitted. The operation unit OP352 receives an instruction to log out (sign out) of the mobile app. When the operation unit OP352 (log out button) is operated, the mobile app is logged out. In the state where the mobile app is logged out, the mobile terminal 400 cannot acquire user information and vehicle information from the server 200.

[0144] In the other settings screen, when the user operates the operation unit OP350 (back button), the mobile terminal 400 displays the aforementioned screen C (Figure 6).

[0145] Figure 13 is a diagram for explaining a screen D displayed on the touch panel display of the mobile terminal 400. The first to fourth operation units OP1 to OP4 in screen D are the same as those in screen A (Figure 3).

[0146] Referring to Figure 13, screen D is a screen that displays data related to the charge and discharge (external charging and external power supply) of the battery 11. Screen D includes information units IN41, IN42 and operation units OP41 to OP46. The mobile terminal 400 displays the data specified by the user in the information unit IN41. Also, the mobile terminal 400 displays the type of data displayed in the information unit IN41 in the information unit IN42.

[0147] Specifically, the mobile terminal 400 displays the data specified by the operation units OP41 to OP46 in the information unit IN41. In the example shown in Figure 13, the data is displayed as a bar graph, but the display form of the information unit IN41 is not limited to a bar graph and can be changed as appropriate. For example, the data may be displayed as a line graph or in a table format. Also, the mobile terminal 400 may change the display form in response to a request from the user.

[0148] The operation units OP41 to OP43 receive an input of the type of data to be displayed on the information unit IN41. The type of data to be displayed is switched by the operation units OP41 to OP43. When the operation units OP41, OP42, and OP43 are operated, the VPP performance (i.e., the incentives obtained by the administrator of the vehicle 100), the electricity charge (yen), and the charging amount (kWh) are displayed on the information unit IN41, respectively. The operation units OP44 to OP46 receive an input of the data period to be displayed on the information unit IN41. The horizontal axis of the graph is switched by the operation units OP44 to OP46. When the operation units OP44, OP45, and OP46 are operated, the data for the most recent 1 month, the most recent 1 week, and the previous day are displayed on the information unit IN41, respectively.

[0149] The incentives are calculated by the server 200. The method of calculating the incentives is arbitrary. In this embodiment, the vehicle user can obtain the aforementioned first and second incentives. The unit price of the first incentive may be a unit price per hour for the time during which the vehicle 100 continues in the plugged state (for example, yen / hour). The server 200 may calculate the first incentive by multiplying the total time during which the vehicle 100 continues in the plugged state by the incentive unit price. The unit price of the second incentive may be a unit price per number of times of power adjustment, a unit price per amount of adjusted electric power (kWh), or a unit price per time of power adjustment. The server 200 may calculate each of the second incentives by multiplying the number of times, the total amount of electric power, or the total time during which the vehicle user performs power adjustment by the incentive unit price. The unit price of each incentive may be fixed or variable according to the situation. The server 200 may determine the unit price of each incentive based on the price in the power market. Different incentive unit prices may be set for each user according to the specifications of the resources owned by the user.

[0150] FIG. 14 is a diagram showing the configuration of the mobile terminal 400. Referring to FIG. 14, the mobile terminal 400 includes a processor 451, a storage device 452, an HMI (Human Machine Interface) 453, and a communication device 454. The processor 451 may be a CPU (Central Processing Unit). The storage device 452 stores, in addition to the programs executed by the processor 451, information used by the programs (for example, maps, mathematical formulas, and various parameters). The HMI 453 includes an input device and a display device. The HMI 453 is, for example, a touch panel display. The processor 451 performs wireless communication with a device external to the mobile terminal 400 through the communication device 454. The mobile terminal 400 according to this embodiment corresponds to an example of the "display device" according to the present disclosure. The charge / discharge schedule screen shown in FIG. 5 corresponds to an example of the "schedule screen" according to the present disclosure.

[0151] In this embodiment, the mobile terminal 400 includes a first acquisition unit 411, a second acquisition unit 412, a display unit 420, a first DR discrimination unit 431, a second DR discrimination unit 432, an information management unit 440, a change unit 461, a switching unit 462, and a transmission unit 470. The information management unit 440 functions as the "first information management unit" and the "second information management unit" according to the present disclosure. In this embodiment, the above-described units are realized by the processor 451 executing the programs stored in the storage device 452. However, the present invention is not limited to this, and the above-described units may be realized by hardware (electronic circuits) included in the mobile terminal 400.

[0152] When the charging mode of the vehicle 100 is the normal charging mode, the first acquisition unit 411 acquires information regarding the charging schedule of the battery 11 from the HMI 453 (an input device that receives inputs from the user). The first acquisition unit 411 receives an input of information regarding the charging schedule of the battery 11, for example, on the screens shown in FIGS. 7 to 9. Then, the first acquisition unit 411 determines the charging start time and the charging end time based on the information input by the user for the charging schedule enabled on the charging timer setting screen (FIG. 7). For example, when the charging end time and the target SOC are input by the user, the first acquisition unit 411 determines the charging start time so that the SOC of the battery 11 becomes equal to or higher than the target SOC at the charging end time. The determined charging start time and charging end time are reflected on the charge / discharge schedule screen shown in FIG. 5 (see, for example, the charging schedules T11 to T17 shown in FIG. 5).

[0153] When the charging mode of the vehicle 100 is the smart charging mode or the delegated charging mode, the first acquisition unit 411 acquires information regarding the charging schedule and the discharging schedule of the battery 11 from the communication device 454 that receives information from the outside. For example, the communication device 454 receives from the server 200 the charging start time and the charging end time regarding the charging schedule and the discharging start time and the discharging end time regarding the discharging schedule during the smart charging periods A4 or B4 shown in FIG. 11, and the first acquisition unit 411 acquires these pieces of information from the communication device 454. The charging schedule and the discharging schedule acquired by the first acquisition unit 411 are reflected on the charge / discharge schedule screen shown in FIG. 5.

[0154] The server 200 may perform DR on the vehicle group 1 in order to fulfill the energy management (contracted energy management) won in the power market. The server 200 may bid for the energy management for the power transmission and distribution operator in the supply-demand adjustment market (for example, the tertiary regulation power -2). The DR for executing such energy management for the power transmission and distribution operator corresponds to normal DR.

[0155] The aggregator (server 200) may enter into a contract (relative contract) to undertake economic DR with a retail electricity provider (server 900). The server 200 may implement economic DR on the vehicle group 1 to fulfill the energy management requested by the retail electricity provider (the energy management determined in the relative contract).

[0156] Note that the agreed fee (ΔkW) that may be generated by meeting the standby requirements during the DR period, the adjustment power quantity fee (kWh) that may be generated by performing power adjustment during the DR period, and the penalty fee that may be generated by not meeting the standby requirements during the DR period can be arbitrarily set by the contract.

[0157] The server 200 implements the above-mentioned agreed DR on the vehicle group 1 as the confirmed DR. The server 200 may implement unconfirmed DR on the vehicle group 1 in addition to or instead of the confirmed DR. The server 200 may implement, as unconfirmed DR, the DR that requests energy management during the time period scheduled for bidding on the vehicle group 1. The server 200 implements DR on the vehicle group 1 by transmitting a DR request signal to the terminal set for each vehicle included in the vehicle group 1 (for example, the mobile terminal 400 set for the vehicle 100).

[0158] The second acquisition unit 412 acquires information regarding the DR schedule from the communication device 454 that receives information from the outside. For example, the communication device 454 receives a DR request signal from the server 200, and the second acquisition unit 412 acquires from the communication device 454 the information regarding the DR schedule included in the DR request signal. The DR request signal further includes the first to third DR discrimination information described below in addition to the content of the energy management and the DR period described above. The information management unit 440 stores various information included in the DR request signal in the storage device 452, and manages various information regarding DR (including the first to third DR discrimination information) by distinguishing each DR request signal (that is, each DR received by the mobile terminal 400).

[0159] The DR request signal includes information indicating whether the requested DR is for a distribution and transmission utility or for a retail electricity provider (hereinafter also referred to as "first DR discrimination information"). Based on the first DR discrimination information, the first DR discrimination unit 431 classifies the requested DR into either a DR for a distribution and transmission utility or a DR for a retail electricity provider. The display unit 420 is configured to display the schedule of the DR for the distribution and transmission utility and the schedule of the DR for the retail electricity provider in a distinguishable manner on the charge and discharge schedule screen shown in FIG. 5.

[0160] The DR request signal includes information indicating the degree of tightness of the power supply and demand of the power grid PG during the DR period (hereinafter also referred to as "second DR discrimination information"). The second DR discrimination information corresponds to an example of "information on the supply and demand situation of an external power source whose supply and demand is adjusted by demand response" according to the present disclosure. The second DR discrimination information may indicate the degree of tightness of the power supply and demand as the ratio of the demand power to the power supply capacity. The higher the ratio of the demand power to the power supply capacity, the higher the degree of tightness of the power supply and demand tends to be. However, it is not limited to this, and the degree of tightness of the power supply and demand may be represented by the supply reserve capacity or the supply reserve rate (the ratio of the supply reserve capacity to the demand power). The smaller the supply reserve capacity or the supply reserve rate, the higher the degree of tightness of the power supply and demand tends to be.

[0161] The second DR discrimination unit 432 discriminates DR according to the degree of tightness of the power supply and demand of the power system PG. For example, the second DR discrimination unit 432 classifies DR scheduled during a time period when the degree of tightness of the power supply and demand of the power system PG exceeds a predetermined level as high-tightness DR, and classifies DR scheduled during a time period when the degree of tightness of the power supply and demand of the power system PG does not exceed a predetermined level as low-tightness DR. The display unit 420 displays the schedules of the respective demand responses (high-tightness DR, low-tightness DR) discriminated by the second DR discrimination unit 432 on the charge and discharge schedule screen shown in FIG. 5 in a mutually distinguishable manner. In the charge and discharge schedule screen shown in FIG. 5, the display unit 420 displays the schedule of the high-tightness DR (for example, the lower DR schedule T42) together with the mark M3, and displays the schedule of the low-tightness DR (for example, the lower DR schedule T41) without the mark M3.

[0162] The DR request signal includes information indicating whether the demand response is determined (hereinafter, also referred to as "third DR discrimination information"). The display unit 420 displays on the charge and discharge schedule screen shown in FIG. 5, in a mutually distinguishable manner, the schedule (for example, the raise DR schedules T21, T23) indicating the time period when the determined demand response is scheduled, and the schedule (for example, the raise DR schedule T22) indicating the time period when the undetermined demand response is scheduled.

[0163] Hereinafter, with reference to FIGS. 15 to 17 together with FIG. 14, various processes executed by the mobile terminal 400 in response to an input from the user will be described. The description will be made in chronological order in the order of FIGS. 15, 16, and 17. In the state of FIG. 15, it is assumed that the charging mode of the vehicle 100 is the normal charging mode.

[0164] FIG. 15 is a diagram for explaining an example of a process related to setting a discharge schedule that the mobile terminal 400 executes in response to an input from a user. Referring to FIGS. 14 and 15 together, in the charge / discharge schedule screen (touch panel screen), when the user touches the area where the lowering DR schedule T42 is displayed, the display unit 420 displays the screen D1. The screen D1 requests the user to input information indicating whether to set a discharge schedule corresponding to the lowering DR schedule T42. The screen D1 includes an operation unit OP101 (yes button) and an operation unit OP102 (no button). When the operation unit OP101 is operated by the user, the first acquisition unit 411 acquires a discharge schedule corresponding to the lowering DR schedule T42, and the discharge schedule acquired by the first acquisition unit 411 is set in the mobile terminal 400. Thus, in the example shown in FIG. 15, the first acquisition unit 411 acquires a discharge schedule based on a user operation on the HMI453. Then, the mobile terminal 400 reflects the set discharge schedule on the charge / discharge schedule screen and transmits it to the vehicle 100. The vehicle 100 sets the received discharge schedule in the ECU150. On the other hand, when the operation unit OP102 is operated by the user, the mobile terminal 400 does not set a discharge schedule.

[0165] FIG. 16 is a diagram showing an example of a charge / discharge schedule screen in which a discharge schedule is set by the method shown in FIG. 15. Referring to FIGS. 14 and 16 together, when the operation unit OP101 is operated on the screen D1 shown in FIG. 15, a discharge schedule is set corresponding to the lowering DR schedule T42. Then, the display unit 420 displays a discharge schedule T32 on the charge / discharge schedule screen. The discharge schedule T32 indicates the time period when the battery 11 is scheduled to discharge (external power supply). The downward arrow (arrow M4) attached to the discharge schedule T32 indicates that it is a discharge schedule rather than a charge schedule.

[0166] The display unit 420 indicates the charging start time, the charging end time, and the target SOC for each of the charging schedules T11 to T17. For example, regarding the charging schedule T12, the display unit 420 displays that the charging start time is around 1:00, the charging end time is 5:00, and the target SOC is 80%. Also, the display unit 420 indicates the discharge start time, the discharge end time, and the SOC at the end of discharge for the discharge schedule T32. Specifically, regarding the discharge schedule T32, the display unit 420 displays that the discharge start time is around 17:00, the discharge end time is around 21:00, and the SOC at the end of discharge is 30%.

[0167] The display unit 420 displays the charging schedules T11 to T17, the discharge schedule T32, the raise DR schedules T21 to T23, and the lower DR schedules T41 and T42 on the same time axis. The display unit 420 superimposes and displays the discharge schedule T32 (first schedule) and the lower DR schedule T42 (second schedule) set in the same time zone on the charge / discharge schedule screen. As shown in FIG. 16, the display unit 420 displays the discharge schedule T32 and the lower DR schedule T42 in a distinguishable manner.

[0168] When the discharge schedule T32 is set, the mobile terminal 400 updates the charging schedule T16 so that the user requirements (charging end time and target SOC) are met. Further, the display unit 420 displays the screen D2. The screen D2 requests the user to input information indicating whether to change the charging mode of the vehicle 100 to the smart charging mode. The screen D2 includes an operation unit OP201 (yes button) and an operation unit OP202 (no button). When the operation unit OP201 is operated by the user, the switching unit 462 changes the charging mode of the vehicle 100 to the smart charging mode. Then, the mobile terminal 400 transmits the changed charging mode (smart charging mode) to the vehicle 100. The vehicle 100 sets the received charging mode in the ECU 150. Thereby, the remote control of the battery 11 by the server 200 is permitted. The switching unit 462 permits the remote control of the battery 11 by the server 200 by setting the smart charging mode in the vehicle 100 (ECU 150). On the other hand, when the operation unit OP202 is operated by the user, the switching unit 462 does not change the charging mode. Thus, the switching unit 462 switches whether to permit the server 200 (second control device) to execute charging and discharging of the battery 11 according to the overlapping part (the lowering DR schedule T42 displayed overlapping the discharge schedule T32) of the discharge schedule T32 and the lowering DR schedule T42 in response to a user operation on the schedule screen.

[0169] The changing unit 461 changes the charging schedule and the discharging schedule displayed on the charge / discharge schedule screen according to a user operation on the charge / discharge schedule screen. For example, the user can move the charging schedule T16 to the position of the raising DR schedule T23 by a drag operation on the charge / discharge schedule screen. The changing unit 461 changes the charging schedule T16 to a charging schedule corresponding to the raising DR schedule T23 in response to such a drag operation.

[0170] FIG. 17 is a diagram showing an example of a charge / discharge schedule screen in which the charge schedule is changed by the method shown in FIG. 16. Referring to FIGS. 14 and 17 together, the transmission unit 470 transmits the charge schedule (charge schedule T16 corresponding to the increased DR schedule T23) changed by the change unit 461 to the ECU 150 (first control device). Thereby, the changed charge schedule is set in the ECU 150.

[0171] When the user touches any area of the charge schedules T11 to T17 on the charge / discharge schedule screen (touch panel screen), the mobile terminal 400 (change unit 461) may execute a screen switch to a screen for changing the charge schedule touched by the user (for example, the screen shown in FIG. 9).

[0172] As described above, the schedule display method according to the above embodiment (see FIG. 14) includes, for example, setting information regarding at least one of charging and discharging of the power storage device in the mobile terminal 400 (information terminal) by an input to the HMI 453 from the user (setting step), requesting the mobile terminal 400 to charge or discharge the power storage device by a DR request signal indicating information regarding demand response (requesting step), and the mobile terminal 400 that has received the DR request signal by the communication device 454 displaying, on the same schedule screen (for example, the charge / discharge schedule screen shown in FIG. 14), a first schedule indicating a time period during which charging or discharging of the power storage device is scheduled and a second schedule indicating a time period during which demand response is scheduled (displaying step).

[0173] According to the above method, the user can check, by looking at the schedule screen, whether the charging or discharging schedule matches the timing of DR. If the charging or discharging schedule does not match the timing of DR, the user can change the charging or discharging schedule according to the timing of DR. That is, it becomes easier for the user to participate in the DR that the user wants to participate in. However, if the user does not want to participate in that DR, the user does not have to change the charging or discharging schedule. According to the above method, it becomes easier for the user to execute at least one of charging and discharging of the power storage device at an appropriate timing.

[0174] The energy management system according to the above embodiment includes a server 200 (energy management device) that requests charging or discharging of a power storage device (for example, the battery 11 of the vehicle 100) electrically connectable to the power grid PG (external power source) by demand response, and a mobile terminal 400 that functions as a display device. In the mobile terminal 400 according to the above embodiment, the first acquisition unit 411 acquires a charging schedule (for example, charging schedules T11 to T17) indicating a time period in which charging of the power storage device is scheduled, and a discharging schedule (for example, discharging schedule T32) indicating a time period in which discharging of the power storage device is scheduled. The second acquisition unit 412 acquires a raise DR schedule (for example, raise DR schedules T21 to T23) indicating a time period in which a demand response for requesting charging of the power storage device is scheduled, and a lower DR schedule (for example, lower DR schedules T41, T42) indicating a time period in which a demand response for requesting discharging of the power storage device is scheduled. The display unit 420 simultaneously displays the charging schedule, the discharging schedule, the raise DR schedule, and the lower DR schedule on a schedule screen (for example, the charge / discharge schedule screen shown in FIG. 17) in a distinguishable manner.

[0175] According to the above configuration, the user can check, by looking at the schedule screen, whether the charging schedule matches the timing of the up-regulation DR and whether the discharging schedule matches the timing of the down-regulation DR. Therefore, it becomes easier for the user to participate in the DR they want to participate in. According to the above configuration, it becomes easier for the user to charge and discharge the power storage device at appropriate timings.

[0176] In the above embodiment, the charging schedule is established by specifying the day of the week, the charging end time, and the target SOC. However, it is not limited to this, and the essential requirements of the charging schedule can be changed as appropriate. For example, the charging schedule for the specified day may be established by specifying the date, the charging start time, and the charging end time.

[0177] The display form of the first schedule (charging schedule, discharging schedule) and the second schedule (DR schedule) is not limited to the form shown in FIG. 5, and can be changed as appropriate. For example, the display unit 420 of the mobile terminal 400 may display the schedule for each day as a bar graph. Also, the display unit 420 may display the required contribution amount with respect to the second schedule (DR schedule).

[0178] The display unit 420 of the mobile terminal 400 may be configured to display only one of the charging schedule and the discharging schedule. Also, the display unit 420 may display, for only one of the up-regulation DR and the down-regulation DR, the schedules of the normal DR and the economic DR separately. Furthermore, it is not essential for the display unit 420 to display the schedules of a plurality of types of DR (for example, normal DR and economic DR), and it may be configured to display only the schedule of one type of DR.

[0179] The power system PG (external power source) is not limited to a large-scale AC grid, and may be a microgrid or a DC (direct current) grid. Also, the configuration of the energy management system is not limited to the configuration shown in FIG. 1. The server 200 may communicate with the servers 700 and 900 via other servers. Another server (for example, a server of a higher aggregator) may be provided between the servers 700 and 900 and the server 200. Also, the server 200 may directly perform wireless communication with the vehicle group 1. The functions of the server 500 may be implemented in the server 200, and the server 500 may be omitted. In the above embodiment, on-premises servers (the servers 200 and 500 shown in FIG. 1) function as management computers. However, it is not limited to this, and the functions of the servers 200 and 500 (particularly, functions related to resource management) may be implemented on the cloud by cloud computing. The management device 1000 may belong to another electric utility (for example, a retail electric utility or a TSO) instead of an aggregator.

[0180] At least a part of the functions of the mobile terminal 400 (particularly, functions related to display) may be implemented in a terminal (for example, HMI81 or NAVI82) mounted on the vehicle 100 (resource). In such a form, HMI81 or NAVI82 functions as a display device (user interface). Alternatively, the mobile terminal 400 and HMI81 or NAVI82 may cooperate to function as a display device.

[0181] The configuration of the vehicle is not limited to the configuration described above (see Fig. 2). The vehicle may be provided with a charger (charging circuit) instead of a charge / discharge device. Also, the vehicle may be provided with a discharger (discharge circuit) instead of a charge / discharge device. The first control device (for example, the ECU 150 mounted on the vehicle 100) that locally controls the power storage device mounted on the vehicle may be configured to control only one of charging and discharging of the power storage device. The second control device (for example, a control device mounted on an external server such as the server 200) that remotely controls the power storage device mounted on the vehicle may be configured to control only one of charging and discharging of the power storage device. The power exchanged between the vehicle and the EVSE is not limited to AC power and may be DC power. The power conversion circuit (for example, an inverter) for charging or discharging the in-vehicle battery may be mounted on the EVSE instead of the vehicle. The vehicle may output the power discharged from the in-vehicle battery to an external power source via a discharge connector instead of the EVSE. An xEV other than a BEV (such as a PHEV, an FCEV, or a range extender EV) may be adopted as the vehicle (resource).

[0182] The vehicle may be configured to enable non-contact charging. The vehicle may be provided with a solar panel. The vehicle may be configured to enable autonomous driving or may be equipped with a flight function. The vehicle is not limited to a four-wheel passenger car and may be a bus or a truck. The vehicle may be a MaaS (Mobility as a Service) vehicle. A MaaS vehicle is a vehicle managed by a MaaS operator. The vehicle may be a vehicle capable of running without a driver (for example, a robot taxi, an automated guided vehicle (AGV), or an agricultural machine). The vehicle may be a small BEV without a driver or with one passenger (for example, a three-wheel BEV, a BEV for the last mile, or an electric scooter).

[0183] The resource equipped with the power storage device may be a moving body other than an automobile (such as a railway vehicle, a ship, an airplane, a drone, a walking robot, a robot cleaner, a space probe, etc.). The resource may be a stationary power storage device used indoors (such as a house or a factory) or outdoors.

[0184] Each of the above-described various modifications may be implemented in any combination.

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

Description of Reference Numerals

[0186] 1 Vehicle group, 2 EVSE group, 11 Battery, 20 MG, 60 Inlet, 61 Charger / discharger, 81 HMI, 82 NAVI, 83 Air conditioner, 90 Communication device, 100 Vehicle, 150 ECU, 200, 500, 700, 900 Server, 300 EVSE, 400 Portable terminal, 411 First acquisition unit, 412 Second acquisition unit, 420 Display unit, 431 First DR discrimination unit, 432 Second DR discrimination unit, 440 Information management unit, 461 Change unit, 462 Switching unit, 470 Transmission unit, 800 Power generation facility, 1000 Management device, PG Power system.

Claims

1. A first acquisition unit that acquires a first schedule indicating a time period in which charging or discharging of a power storage device is scheduled; A second acquisition unit that acquires a second schedule indicating a time period in which a demand response requesting charging or discharging of the power storage device is scheduled; A display unit that displays a schedule screen; A display device comprising: The display unit is configured to simultaneously display the first schedule and the second schedule on the schedule screen in a distinguishable manner; The display device further includes a first DR discrimination unit that discriminates between the demand response for the power transmission and distribution utility and the demand response for the retail electricity provider; The display unit displays, on the schedule screen, the second schedule indicating a time period in which the demand response for the power transmission and distribution utility is scheduled and the second schedule indicating a time period in which the demand response for the retail electricity provider is scheduled in a distinguishable manner from each other.

2. A first acquisition unit that acquires a first schedule indicating a time period in which charging or discharging of a power storage device is scheduled; A second acquisition unit that acquires a second schedule indicating a time period in which a demand response requesting charging or discharging of the power storage device is scheduled; A display unit that displays a schedule screen; A display device comprising: The display unit is configured to simultaneously display the first schedule and the second schedule on the schedule screen in a distinguishable manner; The display device further includes a first information management unit that manages information indicating whether the demand response is confirmed; The display unit displays, on the schedule screen, the second schedule indicating a time period in which the confirmed demand response is scheduled and the second schedule indicating a time period in which the unconfirmed demand response is scheduled in a distinguishable manner from each other.

3. A first acquisition unit that acquires a first schedule indicating a time period in which charging or discharging of a power storage device is scheduled; A second acquisition unit that acquires a second schedule indicating a time period in which a demand response requesting charging or discharging of the power storage device is scheduled; A display unit that displays a schedule screen; A display device comprising: The display unit is configured to simultaneously display the first schedule and the second schedule on the schedule screen in a distinguishable manner; When the display device is a second information management unit that manages information regarding the supply and demand situation of an external power supply adjusted by the demand response; a second DR discrimination unit that discriminates the demand response according to the degree of tightness of the power supply and demand of the external power supply; further includes The display unit is a display device that displays the second schedule of each demand response discriminated by the second DR discrimination unit on the schedule screen in a mutually discriminated manner.

4. A first acquisition unit that acquires a first schedule indicating a time period in which charging or discharging of a power storage device is scheduled; a second acquisition unit that acquires a second schedule indicating a time period in which a demand response requesting charging or discharging of the power storage device is scheduled; a display unit that displays a schedule screen; A display device comprising: The display unit is configured to simultaneously display the first schedule and the second schedule on the schedule screen in a distinguishable manner; The display unit is configured to display the first schedule and the second schedule set in the same time period on the schedule screen in an overlapping manner; When the display device is A switching unit that switches whether to permit a second control device capable of controlling at least one of charging and discharging of the power storage device to execute charging or discharging of the power storage device according to the second schedule displayed overlapping the first schedule in response to a user operation on the schedule screen further includes.

5. An energy management device that requests charging or discharging of a power storage device electrically connectable to an external power supply by a demand response; the display device according to any one of claims 1 to 4; An energy management system including.

6. The external power supply is a power grid; The power storage device is a power storage device mounted on a vehicle; The first acquisition unit is configured to acquire information regarding the first schedule from an input device that receives an input from a user; The second acquisition unit is configured to acquire information regarding the second schedule from a communication device that receives information from the outside; The energy management system according to claim 5, wherein each of the display device, the input device, and the communication device is mounted on a portable terminal that manages information of the vehicle.

7. The external power supply is a power grid; The energy storage device is an energy storage device mounted on a vehicle. The first acquisition unit is configured to acquire information regarding the first schedule from an input device that receives an input from a user. The second acquisition unit is configured to acquire information regarding the second schedule from a communication device that receives information from the outside. Each of the display device, the input device, and the communication device is mounted on the vehicle. The energy management system according to claim 5.

Images