Power management devices and power management methods

Abstract

The server (100) of the present invention manages the power supply and demand between at least one vehicle connected to the power grid and the power grid, which can be used as a power regulation resource for the power grid. The at least one vehicle is an FCEV (11). Furthermore, the server (100) includes: an acquisition unit (111) that acquires the operating plan of the FCEV (11) and information on the remaining amount of hydrogen that the FCEV (11) can use; and a determination unit (112) that determines whether the FCEV (11) can respond to the demand response request based on the acquired operating plan and the remaining hydrogen information.

Description

Technical Field

[0001] This invention relates to a power management device and a power management method, and more particularly, to a power management device and a power management method for managing the power supply and demand between at least one vehicle connected to the power grid and capable of being used as a power regulation resource of the power grid. Background Technology

[0002] A demand response (hereinafter referred to as "DR") is known as a mechanism for regulating the supply and demand of electricity by requesting electricity from electricity consumers based on requests from electricity companies.

[0003] For example, Japanese Patent Application Publication No. 2020-17030 discloses a DR operation server that manages the power supply and demand of each demander based on DR requests from power companies.

[0004] As environmentally friendly vehicles, fuel cell vehicles (hereinafter referred to as "FCEVs") are attracting attention. FCEVs use electricity generated through the chemical reaction of hydrogen filled in a hydrogen tank with oxygen from the atmosphere to power their operation. Since the fuel cell (FC) is a power generation device, FCEVs can be connected to the power grid when not in use and thus serve as a power regulation resource for the grid. With the increasing number of such FCEVs, it is desirable to utilize them as a power regulation resource that can participate in the DR (Dynamic Energy Regulation) system. Summary of the Invention

[0005] The present invention was made to solve the above-mentioned problems, and its purpose is to provide a power management device and power management method that enables FCEV to be effectively utilized as a power regulation resource in response to DR requests.

[0006] The power management device of the present invention manages the power supply and demand between at least one vehicle connected to the power grid and the power grid, which can be used as a power regulation resource for the power grid. The at least one vehicle includes an FCEV (Fuel Cell Electric Vehicle). Furthermore, the power management device includes: an acquisition unit that acquires information on the FCEV's operating plan and the remaining amount of hydrogen available to the FCEV; and a determination unit that, based on the acquired operating plan and the remaining hydrogen information, determines whether the FCEV can meet the demand (DR).

[0007] Furthermore, the power management method of the present invention is a method for managing the power supply and demand between at least one vehicle connected to the power grid and the power grid, which can be used as a power regulation resource for the power grid. The at least one vehicle includes an FCEV (Fuel Cell Electric Vehicle). Moreover, the power management method includes: a step of obtaining information on the FCEV's operating plan and the remaining hydrogen available to the FCEV; and a step of determining, based on the obtained operating plan and the remaining hydrogen information, whether the FCEV can respond to a DR (Dynamic Discharge) request.

[0008] Based on the aforementioned power management device and method, and considering the FCEV's operating plan and remaining hydrogen information, it can be determined whether the FCEV can handle the DR request. Therefore, the state of the FCEV after the operating plan is finalized can be predicted with high accuracy, enabling a high-precision assessment of the FCEV's ability to handle the DR request. Thus, for example, for a vehicle group with a determined operating plan for FCEVs, an optimal DR plan for the entire vehicle group can be generated based on the operating plans and remaining hydrogen information of each FCEV.

[0009] When the demand response (DR) request is a demand suppression request (reducing DR) that requests to suppress electricity demand (including power supply to the grid), the judgment unit determines whether the FCEV can cope with the demand response request based on the FCEV's operating plan and hydrogen remaining information.

[0010] Furthermore, if the DR request is a demand increase request for increased electricity demand (increase DR), the judgment department determines that the FCEV is unable to handle the DR request.

[0011] FCEVs are power regulation resources that utilize FC (Power Controller) generation. Therefore, they are effective in suppressing demand (including supplying power to the grid), but unsuitable for demand surges. Based on the above structure, FCEVs can be appropriately and effectively used as power regulation resources according to DR (Demand Response) requests.

[0012] The judgment unit can also determine whether an FCEV can meet a DR request based on the price of hydrogen available to the FCEV.

[0013] The price of hydrogen varies depending on the type of electricity used in hydrogen production, etc. Therefore, by incorporating the price of hydrogen into the judgment of whether a DR request can be met, the cost of hydrogen can also be taken into account when determining whether an FCEV can meet a DR request.

[0014] The hydrogen remaining information refers to the remaining hydrogen level in the hydrogen tank installed in the FCEV.

[0015] In addition, the hydrogen surplus information may also include information on the hydrogen storage capacity of the hydrogen stations used by FCEVs.

[0016] By including information on hydrogen storage capacity at hydrogen stations in the hydrogen surplus information, it is possible to determine whether FCEVs can cope with DR requests, taking into account the condition of the infrastructure.

[0017] At least one vehicle is an electric vehicle (hereinafter referred to as "BEV" or "Battery Electric Vehicle") that is selectively connected to the power grid and can be used as a power regulation resource. Then, in the case of a DR request that increases demand, the acquisition unit also acquires the BEV's operating plan and the SOC (State of Charge) information of the battery storage device installed in the BEV. The determination unit determines whether the BEV can respond to the DR request based on the BEV's operating plan and SOC information.

[0018] Battery Electric Vehicles (BEVs) are energy-storing power regulation resources that store electricity in energy storage devices, thus effectively responding to increased demand requests. Based on the above structure, by predicting the BEV's status after the operation plan in response to DR (Demand Responsibility) requests due to increased power demand, it is possible to determine with high accuracy whether the BEV can handle the DR request.

[0019] When the DR request is a demand suppression request, the acquisition unit also acquires the BEV's operating plan and BEV's SOC information. The determination unit calculates a first margin time representing the time from the scheduled end time of the FCEV's operating plan to the start time of power supply based on the DR request, and calculates a second margin time representing the time from the scheduled end time of the BEV's operating plan to the start time of power supply. Based on the first margin time and the second margin time, the priority order of the FCEVs and BEVs participating in the DR request is determined. Here, the weight of the second margin time relative to the priority order is larger than the weight of the first margin time relative to the priority order.

[0020] Typically, the number of hydrogen stations for FCEVs is less than the number of charging stations for BEVs. Therefore, during the period from the end of the operating schedule to the start of power supply, FCEVs face a higher risk of not being able to replenish energy compared to BEVs, given that FCEVs are replenishing hydrogen at hydrogen stations while BEVs are charging their batteries at charging stations. According to the above structure, since the weight of the second margin time relative to priority is larger than that of the first margin time relative to priority, for example, when the first and second margin times are the same, BEVs, which have a lower risk, are given a higher priority than FCEVs. Therefore, the response probability to DR requests can be improved.

[0021] The above and other objects, features, aspects and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings. Attached Figure Description

[0022] Figure 1 This is a diagram illustrating an example of the overall structure of a power system to which a power management device based on an embodiment of the present invention is applied.

[0023] Figure 2 It means Figure 1 The diagram shows an example of the structure of server 100.

[0024] Figure 3 This is a diagram illustrating a structural example of an FCEV.

[0025] Figure 4 This is a diagram illustrating a structural example of a BEV.

[0026] Figure 5 This is a flowchart illustrating an example of the steps involved in the DR process for FCEV.

[0027] Figure 6 This is a flowchart illustrating an example of the DR processing steps for FCEVs and BEVs in Implementation Method 2.

[0028] Figure 7 This is a flowchart illustrating an example of the DR processing steps for FCEVs and BEVs in Implementation Method 3. Detailed Implementation

[0029] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Furthermore, the same or corresponding symbols used to denote the same parts in the drawings will not be described again.

[0030] [Implementation Method 1] Reference Figure 1 This describes the overall structure of a power system using a power management device based on an embodiment of the present invention. Power system 1 includes a power system PG, a microgrid MG, servers 100 and 200, a DER (Distributed Energy Resource) group 500, and receiving transformer equipment 501.

[0031] A microgrid (MG) is a power grid that supplies electricity to a city as a whole, including DER Group 500. The power lines used in a microgrid (MG) to network DER Group 500 can also be self-operated power lines.

[0032] The power system PG is a power grid constructed from power plants and transmission and distribution equipment (not shown). In this implementation, the power company acts as both a power generation enterprise and a transmission and distribution enterprise. The power company is equivalent to a typical transmission and distribution enterprise, responsible for the maintenance and management of the power system PG (commercial power system).

[0033] The receiving transformer 501 is located at the linkage point (power receiving point) of the microgrid MG, receives AC power from the power system PG, steps down the received power, and supplies it to the microgrid MG. The receiving transformer 501 comprises switching devices (e.g., sectionalizing switches, circuit breakers, disconnectors, and load switches) on the high-voltage side (primary side), a transformer, protective relays, measuring equipment, and control devices.

[0034] Server 100 is a power management device that manages the power supply and demand between the microgrid MG and DER group 500. Server 100 is equivalent to a so-called CEMS (Community EMS (Energy Management System)) server and is the manager of the microgrid MG. Server 200 is a computer that manages the power supply and demand of the power system PG. Server 200 belongs to the power company.

[0035] Server 100 is configured to communicate with both server 200 and DER group 500. The communication protocol can be OpenADR. Server 100 manages multiple DERs included in DER group 500. Server 100 executes DR to DER group 500 when requesting supply and demand regulation of the power system PG from server 200. Server 100 can also execute DR to DER group 500 based on requests from the supply and demand regulation market, or for the purpose of implementing supply and demand regulation of the microgrid MG.

[0036] Multiple DERs included in DER group 500 are electrically connected to the microgrid MG. DER group 500 may include, for example, at least one FCEV11, at least one BEV12, residential unit 30, commercial facility 40, factory 50, ESS (Energy Storage System) 60, FCS (Fuel Cell System) 71, generator 80, and natural variable power source 90. These all function as DERs.

[0037] FCEV11 and BEV12 function as DERs when electrically connected to the EVSE (Electric Vehicle Supply Equipment) 20, which is connected to the microgrid MG. For example, the connector of the power cable installed in the EVSE 20 is connected to the inlet of FCEV11 or BEV12, thereby electrically connecting FCEV11 or BEV12 to the microgrid MG via the EVSE 20.

[0038] In addition, Figure 1In this diagram, only one FCEV11 and one BEV12 are shown, but the number of FCEV11 and BEV12 vehicles included in DER group 500 is arbitrary. FCEV11 and BEV12 can be MaaS (Mobility as a Service) vehicles or privately owned vehicles (POVs). MaaS vehicles are vehicles managed by MaaS companies. Furthermore, the number of EVSE20 connecting FCEV11 and BEV12, as well as the respective numbers of residential 30, commercial facilities 40, factories 50, ESS60, FCS71, generators 80, and natural variable power sources 90, are also arbitrary.

[0039] EVSE20 is a public power interface device that can be used by vehicle users after completing the prescribed authentication. EVSE20 converts the power output from the FCEV11 or BEV12 connected to it into AC power (system power) and outputs it to the microgrid MG. Furthermore, EVSE20 converts the AC power received from the microgrid MG into DC power and outputs it to the BEV12 connected to it. AC / DC power conversion devices may also be included in the FCEV11 or BEV12. In addition, EVSE20 is configured to communicate with server 100. Server 100, through the aforementioned authentication, can identify the user using EVSE20.

[0040] Residence 30 includes various household electrical appliances (e.g., lighting fixtures, air conditioning equipment, cooking appliances, information equipment, televisions, refrigerators, and washing machines). Additionally, residence 30 may also have at least one of the following: a power supply unit (e.g., a household electric electric system), a natural variable power source (e.g., solar panels mounted on the roof), an energy storage system (ESS), a fuel cell system (FCS), or a combined heat and power system (e.g., a water heater or heat pump water heater that uses heat generated during home power generation). In the case of residence 30 having a household electric electric system, FCEV11 and BEV12 can also function as a DER (Demand Provider) by being electrically connected to the household electric electric system of residence 30.

[0041] Energy supply and demand in residence 30 are managed, for example, by a HEMS (Home EMS) system (not shown). Residence 30 is configured to communicate with server 100. In this embodiment, residence 30 communicates with server 100 via HEMS.

[0042] Commercial facility 40 includes, for example, office buildings and shops. Examples of shops include department stores, shopping malls, supermarkets, or convenience stores. The energy supply and demand of the various facilities included in commercial facility 40 are managed, for example, by a BEMS (Building EMS) not shown. The BEMS can manage the energy supply and demand for each facility individually, or it can aggregate and manage the energy supply and demand of multiple facilities. Commercial facility 40 is configured to communicate with server 100. In this embodiment, commercial facility 40 communicates with server 100 via BEMS.

[0043] Factory 50 may be, for example, an automobile manufacturing plant or other types of factory. Factory 50 may include, for example, production lines and a centralized heat source for air conditioning. Furthermore, factory 50 may also have at least one of the following: a natural variable power source (e.g., solar or wind power generation equipment), a generator (e.g., a gas turbine generator or a diesel generator), or a combined heat and power (CHP) system. Energy supply and demand in factory 50 are managed, for example, by a Factory EMS (not shown). Factory 50 is configured to communicate with server 100. In this embodiment, factory 50 communicates with server 100 via a FEMS.

[0044] The ESS60 is a stationary energy storage device capable of charging and discharging a microgrid MG. Examples of suitable energy storage devices for the ESS60 include lithium-ion batteries, lead-acid batteries, nickel-metal hydride batteries, redox flow batteries, and NAS (sodium-sulfur) batteries. Surplus electricity generated by the natural variable power source 90 can also be stored in the ESS60.

[0045] FCS71 includes a fuel cell that generates electricity through the chemical reaction of hydrogen and oxygen. FCS71 is connected to a hydrogen tank 72, which is connected to a hydrogen generation device 73. FCS71 is configured to generate electricity using hydrogen supplied from the hydrogen tank 72 and to supply the generated electricity to the microgrid MG. The hydrogen generation device 73 generates hydrogen and supplies the generated hydrogen to the hydrogen tank 72.

[0046] The hydrogen generation device 73 can generate hydrogen using electricity supplied from the microgrid MG, or it can generate hydrogen using surplus electricity generated by the natural variable power source 90. The server 100 can also control the hydrogen generation device 73 to ensure that the remaining hydrogen level in the hydrogen tank 72 is not lower than a predetermined value. Furthermore, any method can be used as the hydrogen generation method, such as known methods like by-product hydrogen generation, water splitting, fossil fuel modification, biomass modification, or the IS (iodine / sulfur) process.

[0047] Generator 80 is a stationary generator that uses fossil fuels to generate electricity. Generator 80 can be, for example, a gas turbine generator or a diesel generator. Generator 80 can be used as an emergency power source.

[0048] The variable power source 90 generates electricity that varies according to weather conditions and outputs the generated power to the microgrid MG. The electricity generated by the variable power source 90 is equivalent to variable renewable energy (VRE). The variable power source 90 includes, for example, solar power generation equipment and wind power generation equipment.

[0049] Server 100 includes a processor 110, a storage device 120, and a communication device 130. The processor 110 may be a CPU (Central Processing Unit). The storage device 120 is configured to store various types of information. In addition to the program executed by the processor 110, the storage device 120 also stores information used in the program (e.g., mappings, mathematical formulas, various parameters, etc.). The communication device 130 includes various communication I / Fs. Server 100 is configured to communicate with the outside world via the communication device 130.

[0050] Server 100 controls DER group 500, which is connected to the microgrid MG, enabling DER group 500 to function as a VPP (Virtual Power Plant). Specifically, server 100 uses IoT energy management technology to remotely and comprehensively control DER group 500, thereby making it function like a power plant. Each DER included in DER group 500 functions as a power regulation resource for the power grid.

[0051] In this implementation method 1, server 100 implements DR to DER group 500. Generally speaking, server 200, for example, when requesting supply and demand adjustment from server 100, knows the capacity that DER group 500 can handle. Then, based on the capacity that can handle, server 100 generates an implementation schedule representing each DER participating in the DR and sends a DR request to each DER.

[0052] As mentioned above, FCEV11 and BEV12 are included in DER Group 500. FCEVs and BEVs are gaining attention as environmentally friendly vehicles, and there is a desire to effectively utilize the increasing number of FCEVs and BEVs in recent years as electric regulation resources for DR.

[0053] In this embodiment 1, a method for effectively using FCEV11 as a power regulation resource for DR is shown. Specifically, server 100 obtains the operating plan of FCEV11 and information on the amount of hydrogen remaining that FCEV11 can use, and determines whether FCEV11 can handle DR requests based on the obtained operating plan and hydrogen remaining information.

[0054] Therefore, by predicting the state of FCEV11 after the operation plan is completed, it is possible to determine with high accuracy whether FCEV11 can cope with the DR request. Thus, for example, for a vehicle group (such as multiple FC buses) with a determined operation plan for FCEV11, an optimal DR plan for the vehicle group as a whole can be generated based on the operation plan of each FCEV11 and the remaining hydrogen information.

[0055] Reference Figure 1 and Figure 2 This describes the structure of server 100. Server 100 includes an acquisition unit 111, a judgment unit 112, a charge / discharge control unit 114, a resource control unit 115, an information management unit 117, a storage device 120, and a communication device 130. For example, through... Figure 1 The processor 110 shown and the program in the storage device 120 executed by the processor 110 implement the above-described components. However, this is not a limitation; these components may also be implemented by dedicated hardware (electronic circuitry).

[0056] Server 100 is configured to communicate with each DER including FCEV11 and BEV12 via communication device 130 (DERs other than FCEV11 and BEV12 are not shown).

[0057] Information management unit 117 is configured to manage information on each user registered in server 100 (hereinafter referred to as "user information"), information on each vehicle (FCEV11 or BEV12) registered in server 100 (hereinafter referred to as "vehicle information"), and information on each fixed DER registered in server 100 (hereinafter referred to as "resource information"). User information, vehicle information, and resource information are stored in storage device 120 separately for each user, each vehicle, and each DER using identification information (ID).

[0058] The FCEV11, registered in server 100, is connected to EVSE20, thereby enabling it to supply power generated by the onboard FC system to the microgrid MG according to a DR request from server 100. Furthermore, the BEV12, also registered in server 100, is connected to EVSE20, thereby enabling it to accept power supplied from the microgrid MG to charge the onboard battery according to a DR request from server 100, and to supply the power stored in the battery to the microgrid MG.

[0059] Vehicle information includes vehicle specifications, vehicle location, remaining energy level, and vehicle operation plan. Vehicle specifications, for example, include the hydrogen tank capacity and electrical power output of an FCEV11, and the battery capacity and charging / discharging power output of a BEV12. Remaining energy level includes, for example, the remaining hydrogen in the hydrogen tank of an FCEV11, and the state of charge (SOC) of the battery in a BEV12. Vehicle location and remaining energy level are detected by various sensors mounted on each vehicle and transmitted from each vehicle to server 100. Acquisition unit 111 obtains the location and remaining energy level from each vehicle via communication device 130 and stores it as vehicle information in storage device 120, associating it with each vehicle's identification information (ID).

[0060] The operation plan specifies the operating routes and operating times for the vehicles (FCEV11, BEV12). During the operating time, the vehicles leave EVSE20 and operate according to the operation plan. Therefore, the vehicles cannot function as DERs during the operating time, but can function as DERs by connecting to EVSE20 outside the operation plan. In this embodiment 1, the vehicles are, for example, route buses, shared taxis, etc., and an operation plan is pre-formulated for each vehicle. The operation plan is obtained by the acquisition unit 111, for example via the communication device 130 to an external operation management server (not shown).

[0061] Server 100 registers EVSE20, residential 30, commercial facility 40, factory 50, ESS60, FCS71, generator 80, and natural variable power source 90 as fixed DERs. Resource information includes the status and specifications of each fixed DER (e.g., maximum output, capacity, responsiveness, etc.). The status of EVSE20 includes whether or not a vehicle is connected. Furthermore, the status of EVSE20 connected to FCEV11 includes the status of that FCEV11 (e.g., ECU operation / stop status, power supply, etc.). Additionally, the status of EVSE20 connected to BEV12 includes the status of that BEV12 (e.g., ECU operation / stop status, charging power / power supply, etc.).

[0062] In the respective states of residential building 30, commercial facility 40, and factory 50, electricity consumption is included. In the state of ESS60, the operating / stop status of the control system, SOC, and charging / discharging power are included. In the respective states of FCS71 and generator 80, the operating / stop status of the control system, generated power, and surplus generating capacity are included. The state of FCS71 also includes the remaining hydrogen in hydrogen tank 72. The state of natural variable power source 90 includes generated power. This resource information is acquired by acquisition unit 111 via communication device 130 and stored in storage device 120.

[0063] The user information includes the communication address of the user's portable terminal, the vehicle ID of the vehicle belonging to the user, the resource ID of the fixed DER belonging to the user, electricity costs (including charging costs), and incentive information (such as the amount of incentives received).

[0064] Each user registered on server 100 enters into a contract with the administrator of the microgrid MG (hereinafter referred to as the "MG administrator") to use the electricity supplied by the microgrid MG. According to this contract, the user (demander) who uses the electricity supplied from the microgrid MG is obligated to pay the stipulated electricity fees to the MG administrator.

[0065] Based on the DR request from the MG manager, DER users implementing power regulation in the microgrid MG are entitled to receive incentives predetermined in the contract from the MG manager. The Information Management Department 117 manages and grants incentives to DER users implementing power regulation in the microgrid MG. Incentives can be in regular currency or virtual currency usable only within the city.

[0066] Information Management Department 117 calculates the incentive amount for each user based on the stipulated incentive unit price. The incentive unit price is arbitrarily determined by the contract. The incentive unit price can be a unit price relative to the number of power adjustments, a unit price relative to the amount of electricity adjusted, or a unit price relative to the time during which power adjustments are implemented.

[0067] The determination unit 112 determines whether the FCEV11 participating in the DR and connected to the EVSE20 is capable of responding to the DR request. Specifically, when the DR request is a demand suppression request (sometimes also called "reduced DR," hereinafter referred to as "reduced DR"), the determination unit 112 determines whether the FCEV11 is capable of responding to the reduced DR based on the FCEV11's operating plan and remaining hydrogen quantity stored in the storage device 120. Furthermore, reduced DR is not limited to demand suppression but also includes power supply to the grid. That is, if the FCEV11 can supply power to the grid via the EVSE20, it is determined that the FCEV11 is capable of responding to the reduced DR.

[0068] For example, if the predetermined time period for reducing the DR (Demand Reduction) coincides with the operating time of the FCEV11, the determination unit 112 determines that the FCEV11 is unable to respond to the DR request. Alternatively, if the remaining hydrogen level is below a predetermined threshold, it is also determined that the FCEV11 is unable to respond to the DR request. Furthermore, the remaining hydrogen level includes not only the remaining hydrogen level in the FCEV11's hydrogen tank but also the remaining hydrogen level in the hydrogen station used by the FCEV11 (e.g., a hydrogen station located in the area where the FCEV11 operates). Even if the remaining hydrogen level in the FCEV11's hydrogen tank decreases, the DR request can be responded to as long as hydrogen can be replenished in the hydrogen station before the DR response time. On the other hand, if the remaining hydrogen levels in both the FCEV11's hydrogen tank and the hydrogen station decrease, hydrogen cannot be replenished in the hydrogen station, and the DR request cannot be responded to. Additionally, information on the remaining hydrogen level of the hydrogen station used by the FCEV11 is obtained from that hydrogen station via the acquisition unit 111.

[0069] Furthermore, when the determination unit 112 determines that the DR request is a demand increase request for increased electricity demand (sometimes also called "increased DR", hereinafter referred to as "increased DR"), the FCEV11 is unable to handle the DR request. The FCEV11 is a power regulation resource for a power generation type that uses FC, so it is effective in reducing DR, but not suitable for increasing DR. Therefore, in this embodiment 1, the determination is made as described above.

[0070] The charge / discharge control unit 114 generates a power supply schedule for the FCEV11 connected to the EVSE20 based on the DR request, and outputs commands to the FCEV11 to indicate the start / end of power supply and the amount of power supplied, according to the power supply schedule. Furthermore, the charge / discharge control unit 114 generates a charge / discharge schedule for the BEV12 connected to the EVSE20 based on the DR request, and outputs commands to the BEV12 to indicate the start / end of charge / discharge and the amount of charge / discharge, according to the charge / discharge schedule.

[0071] Resource Control Unit 115 selects a DER based on the DR request and according to a prescribed priority order. Before selecting a DER, Resource Control Unit 115 may also remove DERs unsuitable for power regulation from the candidate selection. For example, Resource Control Unit 115 may remove DERs that were not in standby mode during the DR request period. Users of DERs that have implemented power regulation are able to receive incentives from the MG manager.

[0072] Reference Figure 3This describes the structure of FCEV11. FCEV11 includes a hydrogen tank 312, an FC system (FCS) 314, a relay 316, a power supply port 318, an inlet 320, a battery 322, an ECU (Electronic Control Unit) 324, and a communication device 326.

[0073] Hydrogen tank 312 stores hydrogen supplied to FC system 314. Hydrogen tank 312 is, for example, a lightweight and high-strength high-pressure tank containing a carbon fiber reinforced plastic layer, capable of storing hydrogen at tens of MPa.

[0074] The FC system 314 includes an FC stack and a converter (neither shown). The FC system 314 generates electricity by an electrochemical reaction between hydrogen supplied from the hydrogen tank 312 and oxygen (air) taken from the outside in the FC stack, and outputs DC power boosted by the converter.

[0075] Relay 316 is controlled to be in the conducting state by ECU 324 when power is supplied from FCEV11 to the microgrid MG via EVSE20. An inlet 320 is provided at power supply port 318. By connecting the connector (not shown) of the power cable provided in EVSE20 to inlet 320, FCEV11 is electrically connected to EVSE20, enabling power to be supplied from FCEV11 to the microgrid MG via EVSE20.

[0076] The battery 322 is connected to the power line between the FC system 314 and the relay 316, and is able to store the power generated by the FC system 314 and the regenerative power generated by the drive motor (not shown) when the vehicle is braking.

[0077] The ECU324 comprises a processor (CPU, etc.), memory (ROM (Read Only Memory) and RAM (Random Access Memory)), input / output buffers, etc. (none are shown in the diagram). The processor loads and executes programs stored in the ROM in the RAM, etc. The programs stored in the ROM describe the various control processes executed by the ECU324.

[0078] Communication device 326 includes various communication I / Fs. ECU 324 can communicate with server 100 via communication device 326. Communication device 326 may include a DCM (Data Communication Module) or a communication I / F corresponding to 5G (Fifth Generation Mobile Communication System).

[0079] Then, ECU 324 obtains the remaining hydrogen level in hydrogen tank 312 via a sensor (not shown) and transmits it to server 100 via communication device 326. Additionally, ECU 324 uses GPS (not shown) to obtain the location information of FCEV 11 and transmits it to server 100 via communication device 326. The transmission of remaining hydrogen level and location information to server 100 is performed periodically, for example, at a predetermined interval.

[0080] Furthermore, when the EVSE20's connector is connected to the inlet 320, and the ECU 324 receives a power-on command from the server 100 via the communication device 326, it activates the relay 316 and the FC system 314. As a result, power generated by the FC system 314 is output to the EVSE20. Conversely, when the ECU 324 receives a power-off command via the communication device 326, it stops the operation of the FC system 314 and deactivates the relay 316.

[0081] Reference Figure 4 This describes the structure of the BEV12. The BEV12 has a charging port 330, an inlet 332, a relay 334, a battery 336, an ECU 338, and a communication device 340.

[0082] An inlet 332 is provided at the charging port 330. By connecting the connector (not shown) of the power cable provided in the EVSE20 to the inlet 332, the BEV12 is electrically connected to the EVSE20, enabling the battery 336 to be charged through the EVSE20 and the power stored in the battery 336 to be supplied to the microgrid MG via the EVSE20.

[0083] When charging the BEV12 based on EVSE20 or supplying power from BEV12 to EVSE20 is implemented, relay 334 is controlled to be in an on state by ECU 338. Battery 336 is charged through EVSE20 electrically connected to inlet 332. Furthermore, the power stored in battery 336 can be output to EVSE20 electrically connected to inlet 332. Additionally, battery 336 can store regenerative power generated by the drive motor (not shown) during vehicle braking.

[0084] The ECU338 includes a processor (CPU, etc.), memory (ROM and RAM), input / output buffers, etc. (none of which are shown). The processor loads and executes programs stored in the ROM in the RAM, etc. The programs stored in the ROM describe the various control processes executed by the ECU338.

[0085] The communication device 340 includes various communication I / Fs. The ECU 338 can communicate with the server 100 via the communication device 340. The communication device 340 may include a DCM or communication I / Fs corresponding to 5G.

[0086] Then, ECU 338 calculates the SOC of battery 336 based on the voltage and current of battery 336 obtained by sensors (not shown), and sends it to server 100 via communication device 340. Furthermore, ECU 338 uses GPS (not shown) to obtain the location information of BEV 12 and sends it to server 100 via communication device 340. The transmission of SOC and location information to server 100 is performed periodically, for example, at a predetermined interval.

[0087] Furthermore, when the ECU 338 is connected to the connector of the EVSE 20 and the inlet 332, it activates the relay 334 to conduct when it receives a charging start or power supply start command from the server 100 via the communication device 340. Thus, upon receiving a charging start command, the ECU 338 charges the battery 336 via the EVSE 20, and upon receiving a power supply start command, it outputs the power stored in the battery 336 to the EVSE 20. Conversely, when the ECU 338 receives a charging stop or power supply stop command via the communication device 340, it deactivates the relay 334 to the off state.

[0088] Next, refer to Figure 5 This flowchart describes the steps of DR processing for FCEV11 based on server 100. The processing shown in this flowchart is performed on FCEV11 participating in DR, and hereinafter, the FCEV11 being processed will be referred to as "object FCEV".

[0089] First, server 100 determines whether the DR request for DER group 500 is to lower the DR (step S10). If the DR request is not to lower the DR, that is, to raise the DR (no in step S10), server 100 determines that object FCEV cannot handle the DR request (step S28). Then, the process is transferred to end.

[0090] In step S10, when it is determined that the DR request for DER group 500 is to reduce the DR (yes in step S10), server 100 obtains the operation plan of object FCEV (step S12). The operation plan of object FCEV is obtained, for example, from an external operation management server that manages the operation of FCEV11 and BEV12.

[0091] Further, server 100 obtains the hydrogen remaining amount information of the target FCEV (step S14). The hydrogen remaining amount information includes the hydrogen remaining amount of the hydrogen tank 312 of the target FCEV and is obtained from the target FCEV. In addition, if the hydrogen remaining amount information includes the hydrogen remaining amount of the hydrogen station used by the target FCEV, the hydrogen remaining amount information is also obtained from that hydrogen station.

[0092] Then, based on the obtained operating plan and hydrogen remaining information of the target FCEV, server 100 determines whether the target FCEV can handle the DR request (reduce DR) (step S16). For example, if the time period of the DR request overlaps with the operating time of the target FCEV, it is determined that the target FCEV cannot handle the DR request. Or, for example, if the hydrogen remaining is below a specified threshold, it is also determined that the target FCEV cannot handle the DR request.

[0093] If it is determined in step S16 that the target FCEV cannot handle the DR request (no in step S16), the process proceeds to step S28. On the other hand, if it is determined in step S16 that the target FCEV can handle the DR request (DR reduction) (yes in step S16), the server 100 generates a power supply plan for the target FCEV based on the DR request (step S18). The power supply plan refers to the start time of power supply to the target FCEV, the end time of power supply, and the amount of power supplied.

[0094] When a power supply plan is generated, server 100 sends the generated power supply plan to the target FCEV. Then, when the power supply start time of the target FCEV arrives (yes in step S20), server 100 sends a power supply execution command to the target FCEV (step S22). Then, when the power supply end time of the target FCEV arrives (yes in step S24), server 100 sends a power supply end command to the target FCEV (step S26).

[0095] Furthermore, while the above analysis considers the target FCEV's operational plan and remaining hydrogen supply to determine its ability to meet DR (Reduction of DR) requests, other information can also be considered. For example, the price information of hydrogen available to the target FCEV can be obtained, and this price information can be taken into account when determining whether the target FCEV can meet DR requests (reduce DR). Since the price of hydrogen at hydrogen stations varies depending on the type of electricity used to produce hydrogen, incorporating the price of hydrogen into the determination of its ability to meet DR requests allows for a more comprehensive assessment of the target FCEV's capacity to meet DR requests, taking into account the cost of hydrogen.

[0096] As described above, according to Embodiment 1, based on the operating plan and hydrogen remaining information of each FCEV11, it is determined whether the FCEV11 can cope with the DR request (reduce DR). Therefore, the state of the FCEV11 after the operating plan is completed can be predicted, and the ability of the FCEV11 to cope with the DR request can be determined with high accuracy. Thus, for example, for a vehicle group of FCEVs with a determined operating plan, based on the operating plan and hydrogen remaining information of each FCEV11, an optimal DR plan for the entire vehicle group can be generated.

[0097] Furthermore, in this embodiment 1, when the DR request is to increase DR, it is determined that FCEV11 cannot handle the DR request. FCEV11 is a power regulation resource for power generation using FC, and therefore it is effective in reducing DR (including power supply to the grid), but not suitable for increasing DR. According to this embodiment 1, with the above structure, FCEV11 can be appropriately and effectively utilized as a power regulation resource according to the DR request.

[0098] Furthermore, when the price of hydrogen varies depending on the type of electricity used in hydrogen production, as described above, in determining whether FCEV11 can meet DR requests, by incorporating the price of hydrogen that FCEV11 can use, the cost of hydrogen can be taken into account when determining whether FCEV11 can meet DR requests.

[0099] Furthermore, by including information on the hydrogen storage capacity of the hydrogen stations used by the FCEV11 in the hydrogen surplus information of the FCEV11, it is possible to determine whether the FCEV11 can cope with DR requests, taking into account the condition of the infrastructure.

[0100] [Embodiment 2] As a power generation-type regulation resource, FCEV11 is not suitable for increasing DR (Demand Increase Request). In Embodiment 1, when the DR request is to increase DR, FCEV11 is determined to be unable to respond to the DR request. On the other hand, BEV12 is a storage-type regulation resource and effectively functions to increase DR. Therefore, in Embodiment 2, when a user has both FCEV11 and BEV12 (for example, when a bus or taxi operating company has both FCEV11 and BEV12), when the DR request is to increase DR, it is determined whether BEV12 can handle the DR request. Thus, even when the DR request is to increase DR, the DR request can still be handled.

[0101] The overall structure of the power system and the structure of the server 100 based on implementation method 2 Figure 1 , 2 The implementation method shown is the same as Implementation Method 1.

[0102] Reference Figure 6The steps of DR processing for FCEV11 and BEV12 in Implementation Method 2 will be described. The processing shown in this flowchart is also performed on FCEV11 and BEV12 participating in DR. Hereinafter, BEV12, which is the object of processing, will be referred to as "object BEV".

[0103] The processes from step S110 to step S128 are respectively related to Figure 5 The processes from step S10 to step S28 in the flowchart of Embodiment 1 shown are the same.

[0104] In this flowchart, if it is determined in step S110 that the DR request is to improve the DR (no in step S110), and it is determined that the object FCEV cannot handle the DR request (step S128), the server 100 obtains the operation plan of the object BEV (step S130). The operation plan of the object BEV is obtained, for example, from an external operation management server that manages the operation of FCEV11 and BEV12.

[0105] Further, server 100 obtains the SOC information of the object BEV (step S132). The SOC information is obtained from the object BEV. Then, server 100 determines whether the object BEV can handle the DR request (improve DR) based on the obtained object BEV's runtime plan and SOC information (step S134). For example, if the time period of the DR request overlaps with the object BEV's runtime, it is determined that the object BEV cannot handle the DR request. Or, for example, if the SOC is lower than a predetermined threshold, it is also determined that the object BEV cannot handle the DR request.

[0106] If it is determined in step S134 that the object BEV cannot handle the DR request (No in step S134), no subsequent series of processes are executed, and the process is transferred to end.

[0107] On the other hand, when it is determined in step S134 that the target BEV can handle the DR request (yes in step S134), the server 100 generates a charging plan for the target BEV based on the DR request (step S136). The charging plan refers to the charging start time, charging end time, and amount of charging power for the target BEV.

[0108] When a charging plan is generated, server 100 sends the generated charging plan to the target BEV. Then, when the charging start time of the target BEV arrives (yes in step S138), server 100 sends a charging execution command to the target BEV (step S140). Then, when the charging end time of the target BEV arrives (yes in step S142), server 100 sends a charging end command to the target BEV (step S144).

[0109] As described above, according to this embodiment 2, when the DR request is to increase DR, the FCEV11, which is a power regulation resource for power generation, cannot cope with it. However, it is determined whether the BEV12, which is a power regulation resource for energy storage, can cope with the DR request. Therefore, when the DR request is to increase DR, it can also cope with the DR request.

[0110] [Implementation Method 3] BEV12 can also supply power to the microgrid MG via EVSE20, so if the SOC of battery 336 becomes high enough, it will also effectively reduce DR. Therefore, FCEV11 and BEV12 will conflict when the DR request is to reduce DR.

[0111] FCEV11, as a power generation-type power regulation resource, has a higher power supply capacity compared to BEV12, which is an energy storage-type power regulation resource. Therefore, in reducing conflicts between FCEV11 and BEV12 in DR (Dynamic Energy Management), FCEV11 usually has a higher priority than BEV12. However, generally, there are fewer hydrogen stations for FCEVs than charging stations for BEVs. Therefore, during the period from the end of the operation plan to the start of power supply, if FCEV11 is replenishing hydrogen to hydrogen tank 312 at a hydrogen station while BEV12 is charging battery 336 at a charging station, FCEV11 is at a higher risk of not being able to replenish energy compared to BEV12.

[0112] Therefore, in this embodiment 3, when the DR request is to reduce DR, the priority order of FCEV11 and BEV12 for the DR request is determined considering the risks described above. Specifically, the time (margin time) from the predetermined end time of the operation plan to the start time of power supply based on the DR request (reduced DR) is calculated for both FCEV11 and BEV12. Then, the priority order of FCEV11 and BEV12 is determined based on the margin time of FCEV11 and the margin time of BEV12, and the weight of the margin time of BEV12 relative to the priority order is made greater than the weight of the margin time of FCEV11. Thus, for example, if the margin time of FCEV11 is the same as the margin time of BEV12, BEV12, which has a lower risk of not being able to replenish energy, becomes higher in priority than FCEV11. As a result, the response probability to the DR request (reduced DR) can be improved.

[0113] The overall structure of the power system and the structure of the server 100 according to Embodiment 3 are also similar. Figure 1 , 2 The implementation method shown is the same as Implementation Method 1.

[0114] Reference Figure 7This flowchart illustrates the steps of the DR processing for FCEV11 and BEV12 in Implementation 3. The processing shown in this flowchart is also performed for FCEV11 and BEV12 participating in DR.

[0115] Similar to embodiments 1 and 2, when the server 100 determines that the DR request for DER group 500 is to reduce DR (yes in step S210), it obtains the operation plan of the target FCEV (step S212) and further obtains the hydrogen remaining information of the target FCEV (step S214).

[0116] Then, server 100 calculates the time from the scheduled end time of the obtained object FCEV's operating plan to the start time of power supply based on the DR request (reducing DR) (hereinafter referred to as "first margin time"). (Step S216)

[0117] Similar to the object FCEV, for the object BEV, the server 100 also obtains the operation plan of the object BEV (step S218) and further obtains the SOC information of the object BEV (step S220). Then, the server 100 calculates the time from the predetermined end time of the obtained operation plan of the object BEV to the power supply start time based on the DR request (hereinafter referred to as the "second margin time") (step S222).

[0118] Next, server 100 determines the priority order of object FCEV and object BEV for the DR request (DR reduction) based on the first margin time of object FCEV calculated in step S216 and the second margin time of object BEV calculated in step S222 (step S224). Here, when determining the priority order, server 100 gives a greater weight to the second margin time than the first margin time. For example, if the first margin time and the second margin time are the same, the weight is determined in such a way that the object BEV has a higher priority than the object FCEV.

[0119] Then, if the target FCEV has a higher priority than the target BEV (yes in step S226), the server 100 generates a power supply plan for the target FCEV based on the DR request (step S228). The processes from step S228 to step S236 are respectively related to... Figure 5 Steps S18 to S26 of the flowchart of Embodiment 1 shown below Figure 6 The processing of steps S118 to S126 is the same, so it will not be described again.

[0120] On the other hand, if the target BEV has a higher priority than the target FCEV (no in step S226), the server 100 generates a power supply plan for the target BEV based on the DR request (step S244). The processes from step S244 to step S252 are respectively related to... Figure 6 The processes of steps S136 to S144 in the flowchart of Embodiment 2 shown are the same, so they will not be described again.

[0121] Returning to step S210, if the DR request is to improve the DR (which was not the case in step S210), server 100 obtains the running plan of object BEV (step S238) and further obtains the SOC information of object BEV (step S240). The processing from step S238 to step S252 is respectively related to... Figure 6 The processes from steps S130 to S144 in the flowchart shown are the same, so they will not be described again.

[0122] As described above, in this embodiment 3, when the DR request is to reduce DR, the priority order of FCEV11 and BEV12 participating in the DR request is determined based on the first margin time for FCEV11 and the second margin time for BEV12. This improves the response probability to the DR request.

[0123] The embodiments of the present invention have been described above; however, these embodiments are considered illustrative rather than limiting in all respects. The scope of the present invention is defined by the claims and is intended to include all modifications within the meaning and scope equivalent to the claims.

Claims

1. A power management device that manages power supply and demand between at least one vehicle electrically connected to a power grid and capable of being used as a power adjustment resource of the power grid and the power grid, the at least one vehicle being a fuel cell vehicle, the power management device having: an acquisition unit that acquires information of a travel plan of the fuel cell vehicle and a hydrogen remaining amount available to the fuel cell vehicle; a determination unit that determines whether the fuel cell vehicle can cope with a demand response request based on the acquired travel plan and hydrogen remaining amount information, the at least one vehicle further including an electric vehicle that is selectively electrically connected to the power grid and capable of being used as the power adjustment resource, in a case where the demand response request is a demand suppression request that requests suppression of power demand, the acquisition unit further acquires information of a travel plan of the electric vehicle and a SOC of a power storage device mounted on the electric vehicle, in the determination unit, a first margin time indicating a time from an end scheduled time of the travel plan of the fuel cell vehicle to a power supply start time based on the demand response request is calculated, a second margin time indicating a time from an end scheduled time of the travel plan of the electric vehicle to the power supply start time is calculated, a priority order of the fuel cell vehicle and the electric vehicle participating in the demand response request is determined based on the first margin time and the second margin time, the weight of the second margin time with respect to the priority order is larger than the weight of the first margin time with respect to the priority order.

2. The power management device according to claim 1, wherein the determination unit determines whether the fuel cell vehicle can cope with the demand response request based on the travel plan and the hydrogen remaining amount information in a case where the demand response request is the demand suppression request.

3. The power management device according to claim 2, wherein the determination unit determines that the fuel cell vehicle cannot cope with the demand response request in a case where the demand response request is a demand increase request that requests an increase in power demand.

4. The power management device according to any one of claims 1 to 3, wherein the determination unit determines whether the fuel cell vehicle can cope with the demand response request based on a price of hydrogen available to the fuel cell vehicle.

5. The power management device according to any one of claims 1 to 3, wherein the hydrogen remaining amount information is a hydrogen remaining amount of a hydrogen tank mounted on the fuel cell vehicle.

6. The power management device according to claim 5, wherein the hydrogen remaining amount information further includes information of a hydrogen storage amount of a hydrogen station used by the fuel cell vehicle.

7. The power management device according to claim 3, wherein in a case where the demand response request is the demand increase request, the acquisition unit further acquires information of a travel plan of the electric vehicle and a SOC of a power storage device mounted on the electric vehicle, The judging section judges whether the electric vehicle can cope with the demand response request based on the operation plan of the electric vehicle and the information of the SOC.

8. A power management method of managing power supply and demand between at least one vehicle and a power grid, the at least one vehicle being electrically connected to the power grid and being able to be used as a power adjustment resource of the power grid, the at least one vehicle including a fuel cell vehicle, The power management method has: a step of acquiring an operation plan of the fuel cell vehicle and information of a hydrogen remaining amount that the fuel cell vehicle can use; a step of judging whether the fuel cell vehicle can cope with a demand response request based on the acquired operation plan and hydrogen remaining amount information, The at least one vehicle also includes an electric vehicle that is selectively electrically connected to the power grid and is able to be used as the power adjustment resource, In a case where the demand response request is a demand suppression request that requests suppression of power demand, the power management method also has: a step of acquiring an operation plan of the electric vehicle and information of a SOC of a power storage device mounted on the electric vehicle; a step of calculating a first margin time that indicates a time from a scheduled end time of the operation plan of the fuel cell vehicle to a power supply start time based on the demand response request; a step of calculating a second margin time that indicates a time from a scheduled end time of the operation plan of the electric vehicle to the power supply start time; and a step of determining a priority order of the fuel cell vehicle and the electric vehicle that participate in the demand response request based on the first margin time and the second margin time, The second margin time has a larger weight with respect to the priority order than the first margin time has with respect to the priority order.

Images