Server, power management system and energy management method

Abstract

The present disclosure relates to a server, a power management system, and an energy management method. The energy management method includes: determining whether charging power compression control is executed in a battery (130) during charging (S22 and S23); and when it is determined that charging power compression control is executed in the battery during charging (S22 and S23: Yes), performing a process for compensating for a reduction in charging power caused by the charging power compression control (S24 and S25).

Description

Technical Field

[0001] The present disclosure relates to a server, a power management system, and an energy management method. Background Art

[0002] Japanese Patent Application Publication No. 2018-161018 discloses an aggregation system for energy management using DR (demand response). Upon receiving DR control instructions from a server, the hybrid power conversion device in this aggregation system activates controlled objects in descending order of response speed. The aggregation system is an example of a power management system. Summary of the Invention

[0003] When the battery currently being charged (the first battery) reaches full charge, charging is started with another battery (the second battery) instead of the first battery, ensuring sufficient charging power for a long period of time. For example, the server determines whether the first battery is fully charged based on its SOC (State of Charge) and sends a charge start command to the second battery when the first battery is fully charged, thereby charging the first and second batteries sequentially. The server can manage energy through battery charging in this manner.

[0004] However, a server may not always be able to obtain the battery's SOC. For example, there are only a limited number of servers that can obtain information from a vehicle. Generally speaking, a server that cannot communicate with the vehicle cannot obtain the SOC of the battery installed in the vehicle.

[0005] As a method for the server to charge multiple batteries sequentially, a method in which the server sends a charge start instruction to the battery according to a predetermined charging plan can also be considered. In this method, when the charging end timing (timing) of the first battery indicated by the charging plan is reached, the server sends a charge start instruction to the second battery. Even if the above-mentioned server does not know the charging status of the first battery, it can determine the charging end timing of the first battery by referring to the charging plan. However, the charging of the first battery is not necessarily carried out according to the charging plan. In the case where the charging of the first battery is completed earlier than the end timing indicated by the charging plan, a charging interruption may occur between the end of charging of the first battery and the start of charging of the second battery. Moreover, during the charging interruption, energy management based on charging becomes impossible.

[0006] The present disclosure is made to solve the above-mentioned problem, and its purpose is to grasp the charging status of the battery without relying on the SOC of the battery and to perform appropriate energy management according to the charging status of the battery.

[0007] A server according to a first aspect of the present disclosure includes a control device for sequentially charging a plurality of batteries. The control device is configured to determine that charging of a target battery is nearing completion when charging power compression (reduction) control is executed on the target battery during charging.

[0008] The inventors of this application developed the above-mentioned server by focusing on the situation where charging power compression control is performed near the end of battery charging. Charging power compression control reduces the charging power near the end of charging, allowing charging to proceed at a low power level until charging is complete. An example of charging power compression control is to reduce the charging current when the battery is nearing full charge, and continue charging at a low current until the battery voltage reaches the upper limit voltage. This type of control is also known as forced charging control.

[0009] According to the above-mentioned server, it is possible to easily and accurately detect that the charging of the target battery is nearing completion. The server can determine whether charging power compression control is being performed on the target battery based on the charging power of the target battery being charged. Therefore, the above-mentioned server can determine whether the charging of the target battery is nearing completion without relying on the SOC of the target battery being charged. After detecting that the charging of the target battery is nearing completion, the server can perform predetermined processing before the charging of the target battery is completed. Before the charging of the target battery is completed, the server can, for example, compensate for the reduction in charging power caused by the charging power compression control, or instruct the next battery to be charged after the target battery to start charging or prepare for charging. In this way, the above-mentioned server can grasp the charging status of the battery without relying on the SOC of the battery, and perform appropriate energy management according to the charging status of the battery.

[0010] The control device may also be configured to determine that charging power compression control has been initiated for the target battery when the charging power of the target battery decreases below a first reference value during charging. With this configuration, the server can easily and accurately detect the initiation of charging power compression control for the target battery.

[0011] The control device may also be configured to determine that charging of the target battery has ended when the charging power of the target battery falls below a second reference value that is lower than the first reference value after charging power compression control has begun. With this configuration, the server can easily and accurately detect the completion of charging of the target battery. Upon detecting the completion of charging of the target battery, the server may also change the target battery and begin charging control for the new target battery.

[0012] The server may further include a storage device for storing a charging schedule indicating the order in which the multiple batteries are to be charged. The multiple batteries may include a target battery and a subsequent battery, which is designated in the charging schedule to start charging after the target battery. The control device may also be configured to sequentially transmit a charge start command to each of the multiple batteries for power grid energy management.

[0013] With the above configuration, when charging of the target battery is complete or near completion, charging of the next battery is started instead of the target battery, ensuring sufficient charging power for a long period of time. The next battery can also replace the charged target battery and become the new target battery. The target battery and the next battery can each be a stationary battery or an on-board battery (battery pack).

[0014] The control device described above may also be configured to charge a charging resource connected to the power grid when it determines that charging of the target battery is nearing completion, thereby compensating for the reduction in charging power caused by charging power compression control. In this configuration, the reduction in charging power caused by charging power compression control of the target battery is compensated by the charging resource connected to the power grid. This facilitates ensuring a constant charging power.

[0015] Charging resources are configured to store electricity. The method of storing electricity (i.e., charging method) is arbitrary. Charging resources can store electricity (electrical energy) as is, or convert it into other energy sources (e.g., liquid fuel or gas fuel as an energy source) for storage.

[0016] The control device may be configured to execute a process for increasing the reserve capacity of the power grid when it is determined that the reserve capacity (reserve amount) of the power grid is insufficient when charging of the target battery is nearly completed.

[0017] When the server switches charging from the target battery to the next battery, the charging power may decrease due to charging power compression control or charging interruption. The server can also use reserve power to compensate for this decrease in charging power. However, if the reserve power is insufficient, it is difficult to compensate for the decrease in charging power with reserve power. In this regard, when charging of the target battery is nearing completion and the power grid's reserve power is insufficient, the server executes a process to increase the power grid's reserve power. This prevents insufficient reserve power.

[0018] An example of a process for increasing the reserve capacity of the power grid is to encourage users of charging resources to participate in energy management. The server can also encourage users of vehicles not connected to the power grid to connect their vehicles to the grid. The server can also implement DR (demand response) to increase the reserve capacity of the power grid.

[0019] In the server described above, the target battery may be a secondary battery mounted on a first vehicle, and the next battery may be a secondary battery mounted on a second vehicle. The control device may be configured to determine whether charging power compression control is being executed on the target battery being charged with power supplied from the power grid, using a detection value of a power meter that detects power supplied from the power grid to the target battery.

[0020] The above-mentioned server can use the secondary battery mounted on the vehicle for energy management. The secondary battery mounted on the vehicle can also store electricity for driving in the vehicle. The vehicle can also be an electric vehicle. An electric vehicle is a vehicle configured to use electricity supplied from the secondary battery mounted on the vehicle to travel. In addition to BEV (Battery Electric Vehicle, pure electric vehicle) and PHEV (Plug-in Hybrid Electric Vehicle), electric vehicles also include FCEV (Fuel Cell Electric Vehicle), range extender (Range Extender) BEV, etc. The above-mentioned power meter can be an electricity meter (such as a smart meter) that measures the amount of electricity consumed by the building, or a power meter built into EVSE (Electric Vehicle Supply Equipment), or a CT (Current Transformer) sensor provided on the outside of EVSE.

[0021] A second aspect of the present disclosure relates to a power management system including a server that sequentially charges multiple batteries. The server is configured to sequentially transmit a charge start command to each of the multiple batteries. The multiple batteries include a first target battery and a second target battery whose charging starts after the first target battery. The server is configured to transmit a charge start command to the second target battery when charging power compression control starts for the first target battery during charging.

[0022] When charging power compression control is initiated for the first battery during charging, the server transmits a command to start charging the second battery. Specifically, the command to start charging the second battery is transmitted before charging of the first battery is completed. Therefore, in the power management system, charging interruptions are less likely to occur between the completion of charging of the first battery and the start of charging of the second battery. The first and second batteries can each be either stationary or on-board batteries.

[0023] In the above-described power management system, the first target battery may be a secondary battery mounted on the first vehicle, and the second target battery may be a secondary battery mounted on the second vehicle. The first vehicle may include a first control device that initiates a predetermined first charge control for the first target battery based on a charge start command from a server. The second vehicle may include a second control device that initiates a predetermined second charge control for the second target battery based on a charge start command from the server.

[0024] In the above-described power management system, the charging control of the battery mounted on the vehicle is performed by the control device mounted on the vehicle. Therefore, the processing load of the server involved in the charging control is reduced.

[0025] The server can also be configured to transmit the charge start command to a power supply device connected to the vehicle or to an energy management system that manages the power supply device. Such a server can instruct the first and second target batteries to start charging via the EVSE or EMS (Energy Management System). For example, the EVSE body or charging cable can include communication functionality, allowing the server to transmit the charge start command to the EVSE (body or charging cable).

[0026] The server may also be configured to directly transmit a charge start command to a vehicle via wireless communication and obtain the charging power of the battery mounted on the vehicle from a smart meter. With this configuration, it is possible to directly instruct the first and second vehicles, respectively, to start charging the first and second target batteries. Furthermore, the server can obtain the charging power of the battery mounted on the vehicle from the smart meter.

[0027] The charging control executed by the control device mounted on the vehicle may be any of the following three charging controls. For example, the first control device may have any of the following configurations (a) to (c).

[0028] (a) The first control device may be configured to, during a predetermined first charging control, execute charging control of the first target battery in the order of a first constant power charging, a constant voltage charging that reduces the charging power, and a second constant power charging that has a power lower than the first constant power charging. Furthermore, the constant voltage charging and the second constant power charging may be executed as the aforementioned charging power compression control.

[0029] (b) The first control device may be configured to, during a predetermined first charging control, execute charging control of the first target battery in the order of constant current charging and constant voltage charging. Furthermore, the first control device may be configured to initiate the charging power compression control when the constant current charging is switched to the constant voltage charging.

[0030] (c) The first control device may be configured to, during a predetermined first charging control, execute charging control of the first target battery in the order of a first constant power charging and a second constant power charging having a lower power than the first constant power charging. Furthermore, the first control device may be configured to initiate the charging power compression control when transitioning from the first constant power charging to the second constant power charging.

[0031] The energy management method involved in the third aspect of the present disclosure is an energy management method for performing energy management by charging a battery, comprising: determining whether charging power compression control has been performed on the battery during charging; and when it is determined that charging power compression control has been performed on the battery during charging, performing processing for compensating for the reduction in charging power caused by the charging power compression control.

[0032] According to the above energy management method, it is possible to grasp the battery charge status without relying on the battery SOC, and perform appropriate energy management according to the battery charge status.

[0033] The foregoing and other objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 It is a diagram showing the configuration of a vehicle according to an embodiment of the present disclosure.

[0035] Figure 2 It is a diagram showing the configuration of a server according to an embodiment of the present disclosure.

[0036] Figure 3 This is a diagram showing a schematic configuration of a power management system according to an embodiment of the present disclosure.

[0037] Figure 4This is a diagram for explaining charging control (CP1 period, CV period, CP2 period) executed by the vehicle control device according to the embodiment of the present disclosure.

[0038] Figure 5 This is a flowchart showing charging control executed by a vehicle control device according to an embodiment of the present disclosure.

[0039] Figure 6 Yes Figure 4 FIG. 1 is a diagram showing a modified example of the transition of charging power.

[0040] Figure 7 It is a diagram showing a first modified example of charging control executed by the vehicle control device.

[0041] Figure 8 It is a diagram showing a second modified example of charging control executed by the vehicle control device.

[0042] Figure 9 This is a diagram showing an example of a charging schedule.

[0043] Figure 10 It means according to Figure 9 A diagram of multiple vehicles preparing for charging according to the charging schedule shown.

[0044] Figure 11 This is a diagram showing an example of energy management performed by a server according to an embodiment of the present disclosure.

[0045] Figure 12 This is a flowchart showing a process related to energy management executed by a control device of a server according to an embodiment of the present disclosure.

[0046] Figure 13 Yes Figure 12 A flowchart showing details of the processing involved in resource selection is shown.

[0047] Figure 14 Yes Figure 12 Flowchart of a modified example of the processing shown.

[0048] Figure 15 Yes Figure 2 FIG. 1 is a diagram showing a first variation of the communication method of the server shown.

[0049] Figure 16 Yes Figure 2 FIG. 2 is a diagram showing a second variant of the communication method of the server shown. DETAILED DESCRIPTION

[0050] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the accompanying drawings, identical or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated. Hereinafter, the energy management system (EMS) will be referred to as "EMS." Furthermore, the electronic control unit (ECU) installed in a vehicle will be referred to as "ECU."

[0051] Figure 1 1 is a diagram showing the structure of a vehicle 50 according to this embodiment. Figure 1 The vehicle 50 includes a battery 130 that stores electric power for traveling. The vehicle 50 is configured to be able to travel using the electric power stored in the battery 130. The vehicle 50 according to this embodiment is a BEV (Battery Electric Vehicle) that does not include an engine (internal combustion engine).

[0052] Battery 130 is composed of a secondary battery such as a lithium-ion battery or a nickel-metal hydride battery. In this embodiment, a battery pack comprising multiple lithium-ion batteries is used as the secondary battery. A battery pack is composed of multiple secondary batteries (commonly referred to as "cells") electrically connected to each other. Battery 130 in this embodiment is an example of a "battery" as used in this disclosure.

[0053] Vehicle 50 includes ECU 150 . ECU 150 is configured to control charging and discharging of battery 130 . ECU 150 is also configured to control communication with the outside of vehicle 50 .

[0054] Vehicle 50 also includes a monitoring module 131 that monitors the status of battery 130. Monitoring module 131 includes various sensors that detect the status of battery 130 (e.g., voltage, current, and temperature) and outputs the detection results to ECU 150. Monitoring module 131 may also be a BMS (Battery Management System) that, in addition to the aforementioned sensor functions, also has SOC (State of Charge) estimation functions, SOH (State of Health) estimation functions, cell voltage equalization functions, diagnostic functions, and communication functions. ECU 150 can obtain the status of battery 130 (e.g., temperature, current, voltage, SOC, and internal resistance) based on the output of monitoring module 131.

[0055] EVSE (Electric Vehicle Supply Equipment) 40 includes a power supply circuit 41 and a charging cable 42. The power supply circuit 41 is built into the main body of the EVSE 40. The charging cable 42 is connected to the main body of the EVSE 40. The charging cable 42 can be permanently connected to the main body of the EVSE 40 or can be detachable from the main body of the EVSE 40. The charging cable 42 has a connector 43 at its tip and contains a power line.

[0056] The vehicle 50 is provided with an inlet 110 for contact charging and a charger / discharger 120. The inlet 110 is configured to receive power supplied from outside the vehicle 50. The inlet 110 is configured to be connected to a connector 43 of a charging cable 42. By connecting (plugging) the connector 43 of the charging cable 42 connected to the main body of the EVSE 40 to the inlet 110 of the vehicle 50, the vehicle 50 becomes chargeable (i.e., a state in which it can receive power from the EVSE 40). In addition, Figure 1 4 shows only the inlet 110 and the charger / discharger 120 corresponding to the power supply method of the EVSE 40 , but the vehicle 50 may include a plurality of inlets so as to be compatible with a plurality of power supply methods (eg, AC method and DC method).

[0057] The charger and discharger 120 is located between the inlet 110 and the battery 130. The charger and discharger 120 includes a relay and a power conversion circuit (both not shown), and the relay switches the connection / disconnection of the power path from the inlet 110 to the battery 130. The power conversion circuit may also include a bidirectional converter. The relay and the power conversion circuit included in the charger and discharger 120 are respectively controlled by the ECU 150. The vehicle 50 also has a monitoring module 121 for monitoring the status of the charger and discharger 120. The monitoring module 121 includes various sensors that detect the status of the charger and discharger 120 and outputs the detection results to the ECU 150. In this embodiment, the monitoring module 121 is configured to detect the voltage and current input to the above-mentioned power conversion circuit, and the voltage and current output from the above-mentioned power conversion circuit. The monitoring module 121 is configured to be able to detect the charging power of the battery 130.

[0058] In a chargeable state, vehicle 50 can perform external charging (i.e., charging battery 130 using power supplied from EVSE 40) and external power supply (i.e., power supply from vehicle 50 to EVSE 40). Power for external charging is supplied from EVSE 40 to inlet 110 via charging cable 42, for example. Charger / discharger 120 is configured to convert power received by inlet 110 into power suitable for charging battery 130 and output the converted power to battery 130. Power for external power supply is supplied from battery 130 to charger / discharger 120. Charger / discharger 120 is configured to convert power supplied from battery 130 into power suitable for external power supply and output the converted power to inlet 110. When either external charging or external power supply is being performed, the relay of charger / discharger 120 is closed (connected). When neither external charging nor external power supply is being performed, the relay of charger / discharger 120 is open (disconnected).

[0059] ECU150 is composed of a processor 151, a RAM (Random Access Memory) 152, a storage device 153 and a timer 154. ECU150 can also be a computer. Processor 151 can also be a CPU (Central Processing Unit). RAM152 functions as a working memory for temporarily storing data processed by processor 151. Storage device 153 is configured to be able to save stored information. Storage device 153 includes, for example, ROM (Read Only Memory) and a rewritable non-volatile memory. In addition to programs, storage device 153 also stores information used in the program (for example, mapping, formulas and various parameters). In this embodiment, various controls in ECU150 are executed by executing the program stored in storage device 153 by processor 151. However, various controls in ECU150 are not limited to being executed by software, but can also be executed by dedicated hardware (electronic circuit). In addition, the number of processors provided by ECU150 is arbitrary, and processors can also be prepared according to predetermined control.

[0060] Timer 154 is configured to notify processor 151 of the arrival of a set time. When the time set in timer 154 arrives, a signal notifying processor 151 is sent from timer 154 to this effect. In this embodiment, a timing circuit is used as timer 154. However, timer 154 may also be implemented by software rather than hardware (timing circuit). ECU 150 can also obtain the current time using a real-time clock (RTC) circuit (not shown) built into ECU 150.

[0061] The vehicle 50 further includes a travel drive unit 140, an input device 161, an instrument panel 162, a navigation system (hereinafter referred to as "NAVI") 170, a communication device 180, and drive wheels W. The driving method of the vehicle 50 is not limited to Figure 1 Front-wheel drive is shown; rear-wheel drive or four-wheel drive is also possible.

[0062] The travel drive unit 140 is configured to include a PCU (Power Control Unit) and an MG (Motor Generator) (not shown), and uses the power stored in the battery 130 to drive the vehicle 50. The PCU is configured to include, for example, an inverter, a converter, and a relay (hereinafter referred to as "SMR (System Main Relay)") (all not shown). The PCU is controlled by the ECU 150. The MG is, for example, a three-phase AC motor generator. The MG is configured to be driven by the PCU to rotate the drive wheel W. The PCU uses the power supplied from the battery 130 to drive the MG. In addition, the MG is configured to perform regenerative power generation and supply the generated power to the battery 130. The SMR is configured to switch the connection / disconnection of the power path from the battery 130 to the MG. The SMR is in a closed state (connected state) when the vehicle 50 is traveling.

[0063] Input device 161 is a device that accepts input from the user. The user operates input device 161 and outputs signals corresponding to the user's operation to ECU 150. Examples of input device 161 include various switches, various pointing devices, keyboards, and touch panels. Input device 161 may also include a smart speaker that accepts voice input.

[0064] Instrument panel 162 is configured to display information related to vehicle 50. For example, instrument panel 162 displays various information related to vehicle 50 measured by various sensors installed in vehicle 50. The information displayed on instrument panel 162 may include at least one of the outside temperature, the speed of vehicle 50, the state of charge (SOC) of battery 130, average power consumption (distance per kilowatt), and the distance traveled by vehicle 50. Instrument panel 162 is controlled by ECU 150. ECU 150 may also cause instrument panel 162 to display a message or warning light for the user when predetermined conditions are met.

[0065] NAVI170 includes a processor, a storage device, a touch panel display, and a GPS (Global Positioning System) module (all not shown). The storage device stores map information. The touch panel display accepts input from the user and displays a map and other information. The GPS module is configured to receive signals from GPS satellites (hereinafter referred to as "GPS signals"). NAVI170 can determine the position of the vehicle 50 using the GPS signals. NAVI170 is configured to perform a path search for finding a driving route (for example, the shortest route) from the current position of the vehicle 50 to the destination based on input from the user, and display the driving route found by the path search on a map.

[0066] The communication device 180 includes various communication I / Fs (interfaces). The ECU 150 is configured to communicate with the EMS 61 (described later) via the communication device 180. Figure 3 ) to communicate. In addition, ECU150 is configured to communicate with the server 30B ( Figure 3 ) for wireless communication.

[0067] Figure 2 : is a diagram showing the configuration of a server according to this embodiment. Figure 2 The power management system 1 includes a power grid PG, a server 30A, an EVSE 40, a vehicle 50, and a mobile terminal 80. The server 30A according to this embodiment corresponds to an example of the "server" according to the present disclosure.

[0068] The vehicle 50 has Figure 1 The configuration shown in FIG. In this embodiment, an AC power supply device that provides alternating current (AC) power is used as EVSE 40. The charger / discharger 120 includes circuitry corresponding to an AC power supply device. However, this configuration is not limiting; EVSE 40 may also be a DC power supply device that provides direct current (DC) power. The charger / discharger 120 may also include circuitry corresponding to a DC power supply device.

[0069] The portable terminal 80 corresponds to a terminal carried by a user of the vehicle 50. In this embodiment, a smartphone with a touch panel display is used as the portable terminal 80. However, the portable terminal 80 is not limited thereto and any portable terminal may be used as the portable terminal 80, including a tablet terminal, a wearable device (e.g., a smartwatch), an electronic key, or a service tool.

[0070] The power grid PG is a power system provided by a power company (e.g., a utility company). The power grid PG is electrically connected to multiple EVSEs (including EVSE 40), supplying AC power to each EVSE. The power supply circuit 41 built into the EVSE 40 converts the power supplied from the power grid PG into power suitable for external charging. The power supply circuit 41 may also include a sensor for detecting charging power.

[0071] In vehicle 50 in a chargeable state, the relay of charger / discharger 120 is closed, electrically connecting battery 130 to power grid PG. External charging of battery 130 is performed by supplying power from power grid PG to battery 130 via power supply circuit 41, charging cable 42, and charger / discharger 120.

[0072] The server 30A does not communicate directly with the vehicle 50. In other words, the server 30A does not communicate wirelessly with the vehicle 50. The server 30A communicates with the vehicle 50 via the EMS 61. The EMS 61 communicates with the vehicle 50 via the EVSE 40 in accordance with instructions from the server 30A. The communication device 180 mounted on the vehicle 50 is configured to communicate with the EVSE 40 via the charging cable 42. The communication method between the EVSE 40 and the vehicle 50 is arbitrary, and for example, it can be CAN (Controller Area Network) or PLC (Power Line Communication). The standard related to the communication between the EVSE 40 and the vehicle 50 can be either ISO / IEC 15118 or IEC 61851.

[0073] In this embodiment, the communication device 180 and the portable terminal 80 are configured to communicate with each other wirelessly. The communication between the communication device 180 and the portable terminal 80 may be short-range communication (for example, direct communication within the vehicle and its surroundings) such as Bluetooth (registered trademark).

[0074] Server 30A is configured to communicate with portable terminal 80. Predetermined application software (hereinafter referred to as "application") is installed in portable terminal 80. Portable terminal 80 is carried by the user of vehicle 50 and can exchange information with server 30A via the application. The user can operate the application, for example, using the touch panel display of portable terminal 80. By operating the application, the user can, for example, send the scheduled departure time of vehicle 50 to server 30A.

[0075] The server 30A includes a control device 31, a storage device 32, a communication device 33, and an input device 34. The control device 31 may also be a computer. The control device 31 is configured to include a processor and a storage device, perform predetermined information processing, and control the communication device 33. The storage device 32 is configured to store various types of information. The communication device 33 includes various communication interfaces (I / Fs). The control device 31 is configured to communicate with the outside through the communication device 33. The input device 34 is a device that receives input from the user. The input device 34 outputs the input from the user to the control device 31.

[0076] Figure 3 This is a diagram showing the schematic structure of the power management system 1 involved in this embodiment. In this embodiment, the power management system 1 functions as a VPP (virtual power plant). VPP is a mechanism that centrally manages many distributed energy resources (hereinafter also referred to as "DER (Distributed Energy Resources)") based on advanced energy management technology using IoT (Internet of Things) and functions just like a power plant by remotely / integratedly controlling these DERs. In the power management system 1, by using electric vehicles (for example, Figure 1 VPP is achieved by energy management of the vehicle 50 shown.

[0077] The power management system 1 is a VGI (Vehicle Grid Integration) system. The power management system 1 includes a plurality of electric vehicles and a plurality of EVSE (in Figure 3 Only one is shown in each figure). The number of electric vehicles and EVSEs included in the power management system 1 is arbitrary and can be more than 10 or more than 100. The power management system 1 can also include at least one of POV and MaaS vehicles. POV is a vehicle owned by an individual. MaaS vehicles are vehicles managed by MaaS (Mobility as a Service) companies. The power management system 1 can also include at least one of a non-public EVSE (for example, a household EVSE) that can only be used by specific users and a public EVSE that can be used by many unspecified users. Figure 2 The portable terminal 80 shown is carried by each vehicle user. Figure 3 Server 30A in Figure 2 The same as server 30A in.

[0078] and Figure 2 Refer to it together Figure 3 , the power management system 1 includes an electric power company E1, an upper aggregator E2 connected to the electric power company E1, and a lower aggregator E3 connected to consumers.

[0079] The power company E1 is a power generation company and a power transmission and distribution company. The power company E1 builds a power grid (i.e., Figure 2 The power grid PG is shown in FIG. 1 , and is maintained and managed by a server 10. A power plant 11 is configured to include a power generation device for generating electricity, and the electricity generated by the power generation device is supplied to a power transmission and distribution facility 12. The power generation method of the power plant 11 is arbitrary. The power generation method of the power plant 11 can be any of thermal power generation, hydroelectric power generation, wind power generation, nuclear power generation, and solar power generation. The power transmission and distribution facility 12 is configured to include transmission lines, substations, and distribution lines, and transmits and distributes the electricity supplied from the power plant 11. Smart meters 13 and 14 are each configured to measure electricity usage at predetermined intervals (e.g., every 30 minutes), store the measured electricity usage, and transmit it to the server 10. A smart meter is assigned to each consumer (e.g., an individual or a company) who uses electricity. The server 10 obtains each consumer's electricity usage from each consumer's smart meter. The power company E1 can also collect electricity charges corresponding to the electricity usage from each consumer. In this embodiment, the electric power company corresponds to the manager of the power grid PG.

[0080] The power company that provides energy management services by centrally managing DERs is called an "aggregator". For example, the power company E1 can adjust the power of the power grid PG by cooperating with the aggregator. The upper aggregator E2 includes multiple servers (for example, servers 20A and 20B). Each server included in the upper aggregator E2 belongs to a different company. The lower aggregator E3 includes multiple servers (for example, servers 30A and 30B). Each server included in the lower aggregator E3 belongs to a different company. Hereinafter, except for the case of distinction, each server included in the upper aggregator E2 will be referred to as "server 20", and each server included in the lower aggregator E3 will be referred to as "server 30". The number of servers 20 and servers 30 is arbitrary, and can be more than 5 or more than 30.

[0081] In this embodiment, a single server 10 requests energy management from multiple servers 20. Each server 20, receiving the request from server 10, then requests energy management from multiple servers 30. Furthermore, each server 30, receiving the request from server 20, requests energy management from multiple DER users. Using this hierarchical (tree) structure, electric power company E1 can request energy management from numerous consumers (e.g., vehicle users). Requests can also be made through DR (demand response).

[0082] Upon receiving an energy management request from server 20, server 30 selects a DER from the DERs registered with server 30 to respond to the request. The DER thus selected is hereinafter referred to as an "EMDER." EMDERs can include either on-vehicle batteries (e.g., battery 130) or stationary batteries (e.g., ESS 70, described below).

[0083] Server 30 manages energy within its jurisdiction. The area under server 30's jurisdiction can be a neighborhood (e.g., a smart city), a factory, or even a university campus. An aggregator enters into energy management contracts with DER users within the server's jurisdiction. Contracting users can receive predetermined incentives by having their DERs perform energy management in accordance with requests from the aggregator. Furthermore, users who agree to comply with requests but fail to do so are subject to predetermined penalties based on the contract. DERs and their users, who are contractually obligated to perform energy management, are registered on server 30.

[0084] After selecting the EMDERs, the server 30 sends a command to each EMDER, and based on the command, performs energy management (for example, supply and demand adjustment of the power grid PG) in accordance with the request from the server 20 .

[0085] The server 30 measures the power adjustment amount of each EMDER (for example, the charging power amount and / or the discharging power amount in a predetermined period) using a predetermined power meter. The power adjustment amount can also be used to estimate the incentive. The predetermined power meter can be either a smart meter 13 or 14 or a power meter installed in a vehicle (for example, Figure 1 The monitoring module 121 shown in FIG. 1 is shown. The location of the watt-hour meter is arbitrary. The watt-hour meter may be built into the EVSE 40. The watt-hour meter may also be installed on a portable charging cable.

[0086] In this embodiment, the server 30 is configured to receive the detection values ​​of the smart meters 13 and 14 from the server 10. However, the present invention is not limited thereto, and the server 30 may be configured to obtain the detection values ​​of the smart meters 13 and 14 directly (not via the server 10).

[0087] The smart meter 13 is configured to measure Figure 2 The power grid PG (i.e., the power grid constructed by the power plant 11 and the power transmission and distribution equipment 12) shown is the amount of electricity supplied to the EVSE 40. In this embodiment, the EVSE 40 and the EMS 61 are installed in a single residence. The EMS 61 is, for example, a HEMS (Home EMS). The smart meter 13 measures the amount of electricity supplied from the power grid PG to the residence (i.e., the amount of electricity used in the home).

[0088] The smart meter 14 is configured to measure Figure 2 The power grid PG shown here supplies the amount of electricity to the ESS (Energy Storage System) 70. The ESS 70 is a stationary battery capable of charging and discharging with respect to the power grid PG. The ESS 70 can also be a lithium-ion battery, a lead-acid battery, a nickel-metal hydride battery, a redox flow battery, or a sodium-sulfur (NAS) battery.

[0089] Server 30A communicates with ESS 70 via EMS 62. In this embodiment, EMS 62 and ESS 70 are installed at a single commercial site (e.g., a factory or commercial facility). EMS 62 is, for example, a FEMS (Factory EMS) or a BEMS (Building EMS). Smart meter 14 measures the amount of electricity supplied from power grid PG to the commercial site (i.e., the amount of electricity used within the commercial site).

[0090] Upon receiving an energy management request from server 20, server 30A transmits a charge start command to vehicle 50 via EMS 61 and EVSE 40, thereby performing energy management by charging battery 130. Server 30A may also be a server belonging to a housing company or a motor manufacturer. Alternatively, server 30A may be a server belonging to a different automobile manufacturer than the automobile manufacturer that manufactured vehicle 50.

[0091] Meanwhile, server 30B is configured to wirelessly communicate with vehicle 50. Upon receiving an energy management request from server 20, server 30B directly transmits a charge start command to vehicle 50 via wireless communication to charge battery 130. While battery 130 is charging, server 30B obtains the battery 130 charge status (including SOC) from vehicle 50. Server 30B may also be a server owned by the automobile manufacturer that manufactured vehicle 50.

[0092] In the power management system 1 described above, server 30B can obtain the charge status (including SOC) of battery 130 from vehicle 50. On the other hand, server 30A cannot obtain the charge status of battery 130 from vehicle 50. As will be described in detail later, server 30A is configured to grasp the charge status of battery 130 independently of the SOC of battery 130.

[0093] The ECU 150 of the vehicle 50 is configured to perform CP1 charging (first constant power charging) until the battery 130 is nearly fully charged. However, when the battery 130 is nearly fully charged and the voltage of the battery 130 exceeds the fully charged OCV (Open Circuit Voltage), it becomes difficult to store electricity in the battery 130 at high charging power. Therefore, when the battery 130 is nearly fully charged, the ECU 150 is configured to perform CV charging (constant voltage charging) while reducing the charging power, and then perform CP2 charging (second constant power charging) at a lower charging power to bring the battery 130 close to a fully charged state. Hereinafter, the periods during which CP1 charging, CV charging, and CP2 charging are performed will be referred to as "CP1 period," "CV period," and "CP2 period," respectively. The charging powers during CP1 charging and CP2 charging may also be denoted as "P31" and "P32," respectively. P32 is a power value lower than P31. During the CV period, the charging voltage is constant and the charging power gradually decreases from P31 to P32. The CV charging and CP2 charging according to this embodiment correspond to an example of the "charging power compression control" according to the present disclosure.

[0094] Figure 4 This is a diagram for explaining the CP1 period, the CV period, and the CP2 period. Figure 4 In FIG. 1 , line L1 shows the change in charging power of battery 130. Line L2 shows the change in voltage (battery voltage) of battery 130. Line L3 shows the change in SOC of battery 130. t11 to t13 each represent a timing.

[0095] and Figure 1 Refer to it together Figure 4 In this time chart, the period before t11 corresponds to the CP1 period. At t11, when the SOC of battery 130 (line L3) reaches threshold value Y1, the CP1 period transitions to the CV period. In this embodiment, the SOC of battery 130 reaches threshold value Y1 when the voltage of battery 130 (line L2) reaches the fully charged OCV.

[0096] The period from t11 to t12 corresponds to the CV period. Figure 4In the example shown, during the CV period, the charging power decreases at a constant rate. At t12, when the charging power of battery 130 (line L1) reaches P32, the CV period transitions to the CP2 period. Subsequently, at t13, charging ends when the SOC of battery 130 (line L3) reaches threshold Y2 (e.g., 100%), which is greater than threshold Y1. In this embodiment, the SOC of battery 130 reaches threshold Y2 when the voltage of battery 130 (line L2) reaches the CCV (Closed Circuit Voltage) for full charge.

[0097] Figure 5 1 is a flowchart showing charging control executed by ECU 150 of vehicle 50. The processing shown in this flowchart is started by ECU 150 when vehicle 50 receives a charge start command from the outside, for example.

[0098] and Figure 1 and Figure 4 Refer to it together Figure 5 In step (hereinafter simply referred to as "S") 11, ECU150 performs CP1 charging of the battery 130. The period immediately after the vehicle 50 receives the charge start instruction is equivalent to the CP1 period. Therefore, CP1 charging is performed at the charging power P31. Next, in S12, ECU150 determines whether the SOC of the battery 130 is above the threshold value Y1. For example, ECU150 can obtain the SOC of the battery 130 based on the output of the monitoring module 131. During the CP1 period, CP1 charging (S11) continues to be executed, and the SOC of the battery 130 increases. Moreover, when the SOC of the battery 130 becomes above the threshold value Y1 (S12: Yes), in S13, ECU150 ends the CP1 period and transitions to the CV period.

[0099] In S14, the ECU 150 performs CV charging of the battery 130. Next, in S15, the ECU 150 determines whether the charging power of the battery 130 is P32 or less. The ECU 150 can obtain the charging power of the battery 130 based on, for example, the output of the monitoring module 131. During the CV period, CV charging (S14) continues, and the charging power of the battery 130 decreases. If the charging power falls below P32 (S15: Yes), in S16, the ECU 150 ends the CV period and transitions to the CP2 period.

[0100] In S17, the ECU 150 performs CP2 charging of the battery 130. Next, in S18, the ECU 150 determines whether the SOC of the battery 130 is greater than the threshold value Y2. During the CP2 period, the CP2 charging (S17) is continuously performed, and the SOC of the battery 130 increases. Then, when the SOC of the battery 130 becomes greater than the threshold value Y2 (S18: Yes), in S19, the ECU 150 ends the charging of the battery 130 and ends the Figure 5 As a result, the charging power of the battery 130 becomes 0 watts (W).

[0101] The change of charging power during charging is not limited to Figure 4 The example is shown by line L1 in FIG. Figure 6 Yes Figure 4 FIG. 1 is a diagram showing a modified example of the change in charging power. Figure 6 As shown by line L10 , the charging power reduction pattern during the CV period may be a pattern in which the charging power is reduced in steps.

[0102] In this embodiment, the ECU 150 controls the charging of the battery 130 in the order of CP1 charging, CV charging, and CP2 charging. However, the present invention is not limited to this, and the control scheme may be modified as appropriate.

[0103] Figure 7 1 is a diagram showing a first modification of the charging control executed by ECU 150 in vehicle 50. Figure 7 In FIG, line L20, line L21, and line L22 represent charging power, charging voltage, and charging current, respectively. Figure 7 In this modification, ECU150 performs charging control of battery 130 in the order of CC charging (constant current charging) and CV charging (constant voltage charging). The period before t21 corresponds to the CC period in which CC charging is performed. The period from t21 to t22 corresponds to the CV period in which CV charging is performed. For example, at t21, when the SOC of battery 130 becomes greater than threshold value Y1, ECU150 ends the CC period and transitions to the CV period. ECU150 starts charging power compression control when transitioning from the CC period to the CV period. The CV charging involved in this modification is equivalent to an example of "charging power compression control" involved in the present disclosure. Moreover, at t22, when the SOC of battery 130 becomes greater than threshold value Y2, charging of battery 130 ends.

[0104] Figure 8 1 is a diagram showing a second modification of the charging control executed by the ECU 150 in the vehicle 50. Figure 8As shown by line L30 in , in this modification, ECU150 performs charging control of battery 130 in the order of CP1 charging (first constant power charging) and CP2 charging (second constant power charging) with lower power than CP1 charging. The period before t31 is equivalent to CP1 period. The period from t31 to t32 is equivalent to CP2 period. For example, at t31, when the SOC of battery 130 becomes greater than threshold value Y1, ECU150 ends CP1 period and transitions to CP2 period. ECU150 starts charging power compression control when transitioning from CP1 period to CP2 period. The CP2 charging involved in this modification is equivalent to an example of "charging power compression control" involved in the present disclosure. Moreover, at t32, when the SOC of battery 130 becomes greater than threshold value Y2, charging of battery 130 is terminated.

[0105] In addition, about Figure 4 and Figures 6 to 8 X1 and X2 in will be explained later.

[0106] The server 30A according to this embodiment is configured to sequentially charge the storage batteries (batteries) mounted on each of a plurality of vehicles. The order in which the storage batteries mounted on each of the plurality of vehicles are charged is indicated by a charging schedule stored in the server 30A. Figure 9 This is a diagram showing an example of a charging schedule. Figure 10 It means according to Figure 9 A diagram of multiple vehicles preparing for charging according to the charging schedule shown. Figure 9 Vehicles A to H in the Figure 10 The vehicles 50A to 50H are shown. Figure 10 As shown, vehicles 50A to 50H are equipped with batteries 130A to 130H, respectively. Vehicles 50A to 50H are configured to be connectable to EVSEs 40A to 40H, respectively. Each of EVSEs 40A to 40H is electrically connected to a power grid PG and receives power from the power grid PG. Figure 1 and Figure 2 The illustrated vehicle 50 and EVSE 40 have the same configuration. Hereinafter, except for the case where they are described separately, each of the vehicles 50A to 50H will be referred to as a "vehicle 50," and each of the EVSEs 40A to 40H will be referred to as an "EVSE 40." Figure 2 The EMS 61 shown is provided for each EVSE 40 .

[0107] and Figure 2 Refer to it together Figure 9, the charging schedule determines that two batteries are charged at the same time. For example, the server 30A creates a charging schedule when receiving a charging request from the server 20 (upper aggregator E2). Each battery included in the charging schedule is equivalent to the aforementioned EMDER. Figure 9 In the example shown, each of batteries 130A to 130H corresponds to an EMDER. The generated charging schedule is stored in storage device 32. When generating the charging schedule, server 30A may select batteries (EMDERs) based on the scheduled departure times of each vehicle 50 and determine the charging order and charging start timing. After generating the charging schedule, server 30A may also provide a predetermined notification to the portable terminal 80 carried by the user of each vehicle included in the charging schedule.

[0108] exist Figure 9 In the example shown, server 30A creates a charging schedule that divides the charging power requested by upper-level aggregator E2 into charging power P1 and charging power P2. The first battery ensures charging power P1, while the second battery ensures charging power P2. The requested charging power is ensured by charging both batteries (the first and second batteries) simultaneously. The requested charging power is the sum of charging power P1 and charging power P2.

[0109] exist Figure 9 In the charging schedule shown, batteries 130A, 130C, 130E, and 130G each correspond to a first battery, and batteries 130B, 130D, 130F, and 130H each correspond to a second battery. Figure 9 In the figure, t0 to t5 each represent a timing. At t0, charging of batteries 130A and 130B begins. Then, at t1, charging of battery 130A ends, and charging of battery 130C begins. After t1, charging is sequentially handed over (charging ends and charging begins) at timings t2, t3, t4, and t5. Specifically, at t2, charging of battery 130B ends, and charging of battery 130D begins. At t3, charging of battery 130C ends, and charging of battery 130E begins. At t4, charging of battery 130D ends, and charging of battery 130F begins. Then, at t5, charging of batteries 130E and 130F ends, and charging of batteries 130G and 130H begins.

[0110] and Figure 9 Refer to it together Figure 10 In order to catch up with the charging start timing indicated in the charging schedule, the vehicle user connects the vehicle to the EVSE when the SOC of the vehicle battery is within a predetermined range (hereinafter referred to as the "start range"). The vehicle can also start driving after the charging is completed by disconnecting from the EVSE. Figure 10In the example shown, charging of battery 130F ends earlier than the charging end time indicated in the charging schedule, and vehicle 50F is disconnected from EVSE 40F. For example, if the SOC of battery 130F at the start of charging is higher than the aforementioned starting range, charging of battery 130F may end earlier than scheduled. If vehicle 50F is disconnected midway, the charging power guaranteed by server 30A may no longer meet the charging power requested by upper aggregator E2.

[0111] Figure 11 : is a diagram showing an example of energy management performed by the server 30A. Figure 2 Refer to it together Figure 11 The server 30A involved in this embodiment is configured to be able to detect the disengagement of the vehicle 50F. As will be described in detail later, the control device 31 of the server 30A determines whether the charging of the battery 130F is nearing completion based on whether the charging power compression control is being executed on the battery 130F during the charging period. That is, the control device 31 determines that the charging of the battery 130F is nearing completion when the charging power compression control is being executed on the battery 130F during the charging period. If the charging of the battery 130F is completed earlier than scheduled, the control device 31 can detect that the charging of the battery 130F is about to be completed before the charging of the battery 130F is completed. Therefore, the server 30A can quickly compensate for the reduction in charging power caused by the disengagement of the vehicle 50F. As a result, insufficient charging power is less likely to occur.

[0112] The server 30A involved in this embodiment compensates for the shortfall in the required charging power with a backup resource or the next battery. In the case where the target battery is the battery 130F, the battery 130H, which is determined in the charging schedule to start charging after the battery 130F, corresponds to the next battery. The backup resource is a resource that is connected to the power grid PG and has no charging schedule determined among the charging resources that can be controlled by the server 30A. In other words, the battery that is scheduled to be charged according to the charging schedule does not belong to the backup resource. However, due to the Figure 10 When the vehicle 50F shown is separated, Figure 9 Since charging of the storage batteries 130A to 130D scheduled in the shown charging schedule has already been completed, the storage batteries 130A to 130D can serve as backup resources.

[0113] Figure 12 This is a flowchart showing the processing related to energy management executed by the control device 31 of the server 30A. The processing shown in this flowchart starts when the target battery is determined. For example, the control device 31 starts the processing based on the target battery by setting the storage battery 130A and 130B as the target battery at the same time. Figure 9When the battery 130A is set as the target battery, the battery 130A is executed. Figure 12 In addition, when the battery 130B is set as the target battery, the battery 130B is executed. Figure 12 When the storage batteries 130A and 130B are simultaneously set as target batteries, the processing for each storage battery is executed in parallel and progresses simultaneously.

[0114] and Figure 2 Refer to it together Figure 12 In S21, the control device 31 sends a charge start instruction for the target battery. In this embodiment, the charge start instruction for the target battery is sent from the server 30A to the EMS 61. The EMS 61 instructs the EVSE 40 connected to the vehicle 50 equipped with the target battery to start charging the target battery according to the instruction from the server 30A. Therefore, when the control device 31 sends the charge start instruction for the target battery, according to Figure 5 The process shown starts charging the target battery. The target battery is charged with power supplied from the power grid PG.

[0115] In S22, the control device 31 determines whether the charging power of the target battery being charged is decreasing. The control device 31 can determine whether the charging power of the target battery is decreasing using the detection value of the smart meter 13, for example. The smart meter 13 detects the power supplied from the power grid PG to the target battery. The smart meter 13 involved in this embodiment is equivalent to an example of the "power meter" involved in the present disclosure. The control device 31 may also determine whether the charging power of the target battery is decreasing based on whether the decrease in the charging power of the target battery per unit time is greater than a predetermined value. The determination of S22 is repeated until the charging power of the target battery decreases. Then, when the charging power of the target battery decreases (S22: Yes), the process enters S23.

[0116] In S23, the control device 31 determines whether the charging power of the target battery during charging is lower than a predetermined first reference value (hereinafter referred to as "X1"). The first reference value (X1) corresponds to Figure 4 as well as Figures 6 to 8 In this embodiment, X1 is set to a value slightly lower than P31. X1 may be set within a range of 0.6 to 0.9 times P31, for example, a value obtained by multiplying P31 by 0.7.

[0117] In S23, the control device 31 uses, for example, the detection value from the smart meter 13 to determine whether the charging power of the target battery is less than X1. The determinations in S22 and S23 are repeated until the charging power of the target battery falls below X1. If the charging power of the target battery decreases during charging and falls below X1 (both S22 and S23 are "YES"), the process proceeds to S24.

[0118] When the charging power of the target battery during charging decreases below X1, the control device 31 determines that charging power compression control has been initiated for the target battery during charging. The initiation of charging power compression control for the target battery during charging indicates that charging of the target battery is nearing completion. The control device 31 in this embodiment detects that charging of the target battery is nearing completion by detecting the execution of charging power compression control for the target battery. If the determination in S23 is "YES," the control device 31 executes processing in S24 and S25 to compensate for the reduction in charging power caused by charging power compression control.

[0119] Figure 13 Yes Figure 12 The details of S24 are shown in the flowchart. Figure 2 Refer to it together Figure 13 In S31, the control device 31 determines whether the reserve capacity of the power grid PG is insufficient. The control device 31 may also determine whether the reserve capacity of the power grid PG is insufficient based on whether the remaining charge capacity of the reserve resource is less than a predetermined value.

[0120] If the reserve capacity of the power grid PG is not insufficient (S31: No), in S32, the control device 31 selects reserve resources for the above compensation. For example, the reserve resources include the ESS 70 ( Figure 3 ). Although Figure 3 Only one ESS 70 is shown in FIG. 1 , but the power grid PG is connected to multiple ESSs 70. The power grid PG has many backup resources. In S32 , the control device 31 selects the backup resources required for the above compensation from the many backup resources. The backup resources of the power grid PG may also include storage batteries 130A to 130H ( Figure 10 Since the on-board battery is not always connected to the power grid PG, the on-board battery may be selected in priority over the ESS in S32. The control device 31 may also notify the user of the selected backup resource of this fact.

[0121] If the reserve capacity of the power grid PG is insufficient (S31: YES), in S33, the control device 31 executes a process to increase the reserve capacity of the power grid PG. The control device 31 may also notify the mobile terminal 80 of the user of an electric vehicle not connected to the power grid PG, urging the user to connect the electric vehicle to the power grid PG. Furthermore, the control device 31 may implement DR (demand response) to increase reserve resources.

[0122] After the process of S33 , in S34 , the control device 31 selects a spare resource for the above-mentioned compensation.

[0123] When the prepared resource is selected through the above S32 or S34, Figure 13 The series of processing shown is completed and the processing enters Figure 12 S25. Re- Figure 2 Refer to it together Figure 12 In S25, the control device 31 performs charging using the backup resource selected in S32 or S34. The control device 31 performs charging control (remote control) of the backup resource so that the charging power secured by the server 30A becomes the charging power required by the upper aggregator E2 (see Figure 11 By charging the backup resource, the reduction in charging power caused by the charging power compression control is compensated. Thus, when the control device 31 determines that charging of the target battery is nearing completion (S22 and S23: YES), it charges the backup resource (the charging resource connected to the power grid PG) to compensate for the reduction in charging power caused by the charging power compression control.

[0124] In S26, the control device 31 determines whether the charging power of the target battery being charged is lower than a predetermined second reference value (hereinafter referred to as "X2"). X2 is a power value lower than X1. The second reference value (X2) is equivalent to Figure 4 and Figures 6 to 8 In this embodiment, X2 is set to around 0 W. X2 may also be set within a range of 0 W to 500 W, for example, 100 W.

[0125] In S26, the control device 31 uses, for example, the detection value from the smart meter 13 to determine whether the charging power of the target battery is less than X2. The processes of S24 to S26 are repeated until the charging power of the target battery falls below X2. Through the processes of S24 and S25, the reduction in charging power caused by the charging power compression control executed on the target battery is compensated by charging the backup resource. If the charging power of the target battery under charging power compression control falls below X2 (S26: Yes), the process proceeds to S27.

[0126] When the charging power of the target battery is lower than X2 after the charging power compression control is started (S26: Yes), the control device 31 determines that the charging of the target battery is completed. When the judgment in S26 is "Yes", in S27, the control device 31 refers to the charging schedule stored in the storage device 32 ( Figure 9 ) to determine whether there is a next battery. If there is no next battery (i.e., "No" is determined in S27), it means that the energy management based on the charging schedule is completed. When "No" is determined in S27, Figure 12 The series of processes shown ends.

[0127] On the other hand, if the determination in S27 is "YES," in S28, control device 31 performs processing to compensate for the reduction in charging power resulting from the completion of charging of the target battery. Specifically, in S28, control device 31 selects a backup resource and uses the selected backup resource to perform charging. The processing in S28 is similar to the processing in S24 and S25 described above.

[0128] In S29, control device 31 determines whether charging preparation for the next battery is complete. If vehicle 50 is ready for charging, control device 31 determines that charging preparation for battery 130 mounted on vehicle 50 is complete. If charging preparation for the next battery is not complete (S29: No), the process returns to S28. The processes of S28 and S29 are repeated until charging preparation for the next battery is complete. Through the process of S28, the reduction in charging power caused by the completion of charging of the target battery is compensated by charging the backup resource.

[0129] If the charging preparation of the next battery is completed (S29: Yes), in S30, the control device 31 sets the next battery as a new target battery. Figure 12 That is, the process of S30 is executed, thereby the target battery is Figure 12 The series of processing shown in FIG. 1 is completed, and the process starts anew for the next battery (new target battery). Figure 12 A series of processing shown.

[0130] exist Figure 10 In the example shown, the battery 130A of the vehicle 50A (first vehicle) is used as the target battery. Figure 12 In the case of the series of processes shown, when the charging of the battery 130A is nearly completed, the charging power compression control ( Figure 5 S14), the charging power is lower than X1 (refer to Figure 4), it is determined as "yes" in S23. Then, through the processing of S24 and S25, the reduction in charging power caused by the charging power compression control is compensated by charging the reserve resources. After that, when the charging of the battery 130A is completed, it is determined as "yes" in S26, and in S29, it is determined whether the charging preparation of the battery 130B (next battery) of the vehicle 50B (second vehicle) is completed. Since the vehicle 50B has been connected to the power grid PG before the charging of the battery 130A is completed, when the charging of the battery 130A is completed, it is determined as "yes" in S29, and in S30, the battery 130B is set as the new target battery. Then, the battery 130B is set as the target battery. Figure 12 A series of processing shown.

[0131] On the other hand, when the battery 130F of the vehicle 50F (first vehicle) is used as the target battery, Figure 12 In the case of the series of processing shown, the charging of the battery 130F is completed earlier than the charging end timing indicated by the charging schedule. Therefore, the vehicle 50H (the second vehicle) has not yet been connected to the power grid PG when the charging of the battery 130F is completed. Therefore, it is determined as "No" in S29, and until the vehicle 50H is connected to the power grid PG, the reduction in charging power caused by the completion of charging of the battery 130F is compensated by charging of the backup resources (S28). Then, when the vehicle 50H is connected to the power grid PG (S29: Yes), the battery 130H (the next battery) is set as the new target battery in S30, and the battery 130H is charged to the backup resources. Figure 12 The series of processes shown starts.

[0132] As described above, the server 30A according to this embodiment includes a control device 31 for sequentially charging a plurality of batteries (e.g., storage batteries 130A to 130H). The control device 31 is configured to sequentially send a charge start command to each of the plurality of batteries for energy management of the power grid PG. Furthermore, the control device 31 is configured to, when charging power compression control is executed on the target battery during charging ( Figure 12 S22 and S23: Yes), it is determined that the charging of the target battery is nearly completed. After detecting that the charging of the target battery is nearly completed, the server 30A can perform a predetermined process before the charging of the target battery is completed. For example, before the charging of the target battery is completed, the server 30A compensates for the reduction in charging power caused by the charging power compression control ( Figure 12 The server 30A according to this embodiment can grasp the battery charge status without relying on the battery SOC and perform appropriate energy management according to the battery charge status.

[0133] The energy management method according to the embodiment includes: determining whether charging power compression control ( Figure 12 and in the case where it is determined that the charging power compression control is executed in the battery during charging (S22 and S23: Yes), a process for compensating for the reduction in charging power caused by the charging power compression control is executed ( Figure 12 According to the energy management method of this embodiment, it is possible to grasp the battery charging status without relying on the battery SOC, and perform appropriate energy management according to the battery charging status.

[0134] In the above embodiment, the control device 31 of the server 30A uses the detection value of the smart meter 13 to determine whether charging power compression control is being executed on the target battery during charging. However, the present invention is not limited to this. The control device 31 of the server 30A may also use the detection value of the power meter built into the EVSE 40 or the detection value of the CT sensor installed outside the EVSE 40 to determine whether charging power compression control is being executed on the target battery during charging.

[0135] The control device 31 of the server 30A may also be configured to execute Figure 14 The treatment shown is instead Figure 12 The processing shown. Figure 14 Yes Figure 12 Flowchart of a modified example of the process shown. Figure 14 In the process shown, S24A and S25A are used instead of Figure 12 S24 and S25, and omit Figure 12 In this modification, the charging schedule is not used. For example, when the server 30A receives a charging request from the server 20 (upper aggregator E2), it selects the first target battery and executes the charging schedule for the first target battery. Figure 14 The server 30A selects the first target battery from the spare resources of the power grid PG. Figure 14 The series of processing shown in FIG. 1 is used to charge the first target battery and thereby perform energy management of the power grid PG. Figure 12 The difference in the processing shown is the center, and the processing involved in this modification example ( Figure 14 ) for explanation.

[0136] and Figure 2 Refer to it together Figure 14 In S21, the control device 31 of the server 30A sends a charge start instruction to the first target battery. The first target battery may also be Figure 1The vehicle 50 shown has a first vehicle battery 130 of the same configuration. The first vehicle ECU 150 (first control device) starts a predetermined first charging control for the first target battery based on a charge start instruction from the server 30A. The predetermined first charging control is, for example, Figure 4 and Figure 5 However, the first charging control may also be Figure 7 or Figure 8 Controls shown.

[0137] When charging power compression control is started for the first target battery during charging, it is determined as "yes" in S22 and S23, and the process enters S24A. In S24A, the control device 31 selects a second target battery (a new target battery) from the spare resources of the power grid PG. The second target battery is equivalent to the battery that starts charging next to the first target battery in relay charging (that is, the battery that takes over charging from the first target battery). Then, in S25A, the control device 31 performs the second target battery. Figure 14 The series of processing shown. Processing related to charging of the first target battery ( Figure 14 ) and the processing related to charging of the second target battery ( Figure 14 ) are executed in parallel and advanced simultaneously.

[0138] In the process of charging the first target battery, after the process of S25A, the control device 31 determines in S26 whether the charging power of the first target battery is lower than X2. While the charging power of the first target battery is not lower than X2 (S26: No), the control device 31 determines that the charging of the first target battery is continuing. Furthermore, when the charging power is lower than X2 (S26: Yes), the control device 31 determines that the charging of the first target battery is completed. When the judgment in S26 is "Yes", the process of charging the first target battery ( Figure 14 )Finish.

[0139] The process related to charging the second target battery starts before the charging of the first target battery is completed. In S21, the control device 31 sends a charge start instruction for the second target battery. The second target battery may also be Figure 1 The vehicle 50 shown has a second vehicle battery 130 of the same configuration. The ECU 150 (second control device) of the second vehicle can also be activated upon receiving a charge start instruction for the second target battery. The ECU 150 of the second vehicle starts a predetermined second charge control for the second target battery based on the charge start instruction from the server 30A. The predetermined second charge control is, for example, Figure 4 and Figure 5 However, the second charging control may also be Figure 7 or Figure 8 Controls shown.

[0140] Immediately after charging of the second target battery begins, charging is performed on both the first target battery and the second target battery. To ensure that the sum of the charging power for the first target battery and the charging power for the second target battery does not exceed the charging power requested by the upper aggregator E2, the control device 31 may instruct the charging power to be gradually increased in the charge start instruction for the second target battery.

[0141] If charging power compression control is subsequently initiated for the second target battery during charging, a "Yes" determination is made in S22 and S23, and the process proceeds to S24A. The process from S24A onward is identical to that for charging the first target battery. That is, even in the process for charging the second target battery, a new target battery (the third target battery) is selected in S24A.

[0142] The server 30A according to the above-described variation is configured to transmit a charge start command to the second battery when charging power compression control begins for the first battery during charging (S22 and S23: Yes). This configuration reduces the likelihood of charging interruptions by transmitting the charge start command to the second battery before charging of the first battery is completed. The power management system including the server 30A according to the above-described variation is an example of the "power management system" described in the present disclosure.

[0143] In the above-described embodiment and modification, the server 30A is configured to send a charge start instruction ( Figure 2 However, the present invention is not limited thereto. The server may also send the charging start instruction to the EVSE, or may send the instruction directly to the vehicle (not via the EMS and EVSE).

[0144] Figure 15 Yes Figure 2 FIG. 1 is a diagram showing a first variation of the communication method of the server shown. Figure 15 , the server 30C is configured to send the charging start instruction directly to the EVSE 40. The server 30C has a communication device 33C for communicating with the EVSE 40. In addition, the EVSE 40 has a communication device (not shown) for communicating with the server 30C. The communication device of the EVSE 40 can be mounted on the main body of the EVSE 40 or can be set on the charging cable 42. The communication method between the server 30C and the EVSE 40 can be wired or wireless. For example, the server 30C Figure 12 or Figure 14In S21, a command to start charging the target battery (storage battery 130) is sent to the EVSE 40 connected to the vehicle 50 equipped with the target battery. Following the command from the server 30C, the EVSE 40 instructs the vehicle 50 to start charging the target battery. The server 30C obtains the charging power of the target battery mounted on the vehicle 50 from the smart meter 13. Furthermore, the EVSE 40 may be configured to communicate with an EVSE management cloud. The communication protocol between the EVSE 40 and the EVSE management cloud may be OCPP (Open Charge Point Protocol).

[0145] Figure 16 Yes Figure 2 FIG2 is a diagram showing a second variation of the communication method of the server shown in FIG2. Figure 16 The server 30D is configured to directly send a charge start instruction to the vehicle 50 via wireless communication. The server 30D includes a communication device 33D for wireless communication with the vehicle 50. In addition, the communication device 180 of the vehicle 50 includes a communication interface for communicating with the server 30D. The communication device 180 may also include a DCM (Data Communication Module). The server 30D is, for example, Figure 12 or Figure 14 In S21, when a vehicle 50 equipped with a target battery (storage battery 130) is connected to the EVSE 40, a charge start command for the target battery is directly transmitted to the vehicle 50. The ECU 150 of the vehicle 50 begins the predetermined charge control for the target battery in accordance with the charge start command from the server 30D. The server 30D obtains the charging power of the target battery mounted on the vehicle 50 from the smart meter 13.

[0146] In the above-described embodiment and variations, when the charging power of the target battery during charging decreases and falls below a first reference value (X1), the server determines that charging power compression control has begun for the target battery during charging. However, the method for determining whether charging power compression control is being executed for the target battery is not limited to the above method. For example, the server may determine whether charging power compression control is being executed based on the charging power decrease pattern (behavior when charging power decreases). The server may also learn the behavior of charging power when charging power compression control is being executed. In addition, the server may determine whether charging power compression control is being executed based on the behavior of at least one of the charging current and charging voltage. The server may also learn the behavior of at least one of the charging current and charging voltage when charging power compression control is being executed. The server may also use a learned model obtained through machine learning using AI (artificial intelligence) to determine whether charging power compression control is being executed. Learning may also be performed for each battery (each vehicle). According to this method, even when the charging power is unstable, false detection of charging power compression control due to fluctuations in charging power is less likely to occur.

[0147] The above embodiments and various modifications may also be implemented in any combination. For example, the control device 31 may accept input from the user so that the user can use any control mode. Alternatively, the control device 31 may be configured so that the user can select Figure 12 The control shown (1st control mode) and Figure 14 Any of the controls shown (second control mode).

[0148] Power companies can also be divided into multiple divisions based on their business operations. Power generation companies and power transmission and distribution companies can also be separate companies. An aggregator can also play the role of both a top-tier aggregator and a bottom-tier aggregator. Servers can also receive energy management requests from the power market.

[0149] The plurality of vehicles that sequentially charge the batteries in a relay manner do not necessarily have to have the same configuration. A plurality of vehicles of different models can also sequentially charge the batteries in a relay manner.

[0150] The vehicle is not limited to Figure 1 The configuration shown. For example, the vehicle may be configured to be capable of only external charging and external power supply. The vehicle may also be configured to be capable of contactless charging. The vehicle is not limited to a passenger car, but may also be a bus or a truck. The vehicle is not limited to a BEV, but may also be a PHEV. The vehicle may also be configured to be capable of automatic driving and may also have a flight function. The vehicle may also be a vehicle that can be unmanned (for example, an unmanned guided vehicle (AGV) or agricultural machinery).

[0151] While the embodiments of the present invention have been described, the embodiments disclosed herein are to be construed as illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

Claims

1. A server (30A, 30C, 30D) including a control device (31) for sequentially charging a plurality of batteries (130A to 130H). The control device is configured to determine that charging of the target battery (130) is nearing completion when charging power compression control is executed in the target battery (130) during charging. The control device determines that the charging power compression control is started in the target battery during charging when the charging power of the target battery during charging decreases and falls below a first reference value (X1). The control device determines that charging of the target battery is completed when the charging power of the target battery falls below a second reference value (X2) lower than the first reference value after the charging power compression control is started. The server further includes a storage device (32) for storing a charging schedule indicating the charging order of the plurality of batteries. The plurality of batteries include the target battery and a next battery determined in the charging schedule to start charging next to the target battery, The control device is configured to sequentially send a charge start command to each of the plurality of batteries for energy management of a power grid (PG). When the control device determines that charging of the target battery is nearing completion, the control device charges the charging resource (70, 130) connected to the power grid so as to compensate for a reduction in charging power caused by the charging power compression control. The server compensates for a shortage of the required charging power with a backup resource, wherein the backup resource is a resource connected to the power grid and not scheduled to be charged, among the charging resources controllable by the server, and the plurality of batteries scheduled to be charged according to the charging schedule do not belong to the backup resource. The control device executes a process for increasing the reserve capacity of the power grid when it is determined that the charge of the target battery is nearing completion and the reserve capacity of the power grid is insufficient, wherein: The control device notifies a portable terminal carried by a user of an electric vehicle that is not connected to the power grid to urge the user to connect the electric vehicle to the power grid or to perform demand response to increase reserve resources.

2. The server according to claim 1, The target battery is a secondary battery (130A to 130F) mounted on a first vehicle (50A to 50F). The next battery is a secondary battery (130C to 130H) mounted on the second vehicle (50C to 50H). The control device is configured to determine whether the charging power compression control is being executed on the target battery being charged with power supplied from the power grid, using a detection value of a power meter that detects power supplied from the power grid to the target battery.

3. A power management system comprising a server (30A, 30C, 30D) that sequentially charges a plurality of batteries (130A to 130H). The server is configured to sequentially send a charge start instruction to each of the plurality of batteries. The plurality of batteries include a first target battery (130A to 130F) and a second target battery (130C to 130H) to be charged next to the first target battery. The server is configured to transmit a charge start instruction to the second target battery when charging power compression control is started in the first target battery during charging. When the charging power of the first target battery during charging decreases and falls below a first reference value (X1), it is determined that the charging power compression control is started in the first target battery during charging. The server determines that charging of the target battery is completed when the charging power of the first target battery falls below a second reference value (X2) lower than the first reference value after the charging power compression control is started. The server further includes a storage device (32) for storing a charging schedule indicating the charging order of the plurality of batteries. The plurality of batteries include the target battery and a next battery determined in the charging schedule to start charging next to the target battery, The server is configured to sequentially send a charge start instruction to each of the plurality of batteries for energy management of a power grid (PG). When the server determines that charging of the first target battery is nearing completion, the server charges the charging resource (70, 130) connected to the power grid so as to compensate for a reduction in charging power caused by the charging power compression control. The server compensates for a shortage of the required charging power with a backup resource, wherein the backup resource is a resource connected to the power grid and not scheduled to be charged, among the charging resources controllable by the server, and the plurality of batteries scheduled to be charged according to the charging schedule do not belong to the backup resource. When the server determines that the reserve capacity of the power grid is insufficient because charging of the first target battery is nearly completed, the server executes a process for increasing the reserve capacity of the power grid, wherein: The control device notifies a portable terminal carried by a user of an electric vehicle that is not connected to the power grid to urge the user to connect the electric vehicle to the power grid or to perform demand response to increase reserve resources.

4. The power management system according to claim 3, The first target battery is a secondary battery mounted on a first vehicle (50A to 50F). The second target battery is a secondary battery mounted on a second vehicle (50C to 50H). The first vehicle includes a first control device (150) which starts a predetermined first charging control for the first target battery based on a charging start instruction from the server. The second vehicle includes a second control device (150) that starts a predetermined second charging control for the second target battery based on a charging start instruction from the server.

5. The power management system according to claim 4, The server sends the charging start instruction to a power supply device (40) connected to a vehicle (50) or an energy management system that manages the power supply device.

6. The power management system according to claim 4, The server directly sends the charging start instruction to the vehicle (50) via wireless communication, and obtains the charging power of the battery (130) mounted on the vehicle from the smart meter (13).

7. The power management system according to any one of claims 4 to 6, The first control device performs charging control of the first target battery in the predetermined first charging control in the order of a first constant power charging, a constant voltage charging for decreasing the charging power, and a second constant power charging for a power lower than the first constant power charging. The constant voltage charging and the second constant power charging correspond to the charging power compression control.

8. The power management system according to any one of claims 4 to 6, The first control device executes charging control of the first target battery in the order of constant current charging and constant voltage charging in the predetermined first charging control. The first control device starts the charging power compression control when the constant current charging is switched to the constant voltage charging.

9. The power management system according to any one of claims 4 to 6, The first control device performs charging control of the first target battery in the predetermined first charging control in the order of a first constant power charging and a second constant power charging having a power lower than that of the first constant power charging. The first control device starts the charging power compression control when the charging mode changes from the first constant power charging to the second constant power charging.

10. An energy management method executed by a server, wherein the energy management method is performed by charging a plurality of batteries (130), comprising: determining whether charging power compression control is being executed in the battery during charging; When it is determined that the charging power compression control is being executed on the battery during the charging, executing a process for compensating for a reduction in charging power caused by the charging power compression control; as well as When the charging power of the battery during charging decreases and falls below a first reference value (X1), it is determined that the charging power compression control is started in the battery during charging. When the charging power of the battery falls below a second reference value (X2) lower than the first reference value after the charging power compression control is started, it is determined that charging of the battery is completed. The server includes a storage device (32) for storing a charging schedule indicating the charging order of the plurality of batteries. The plurality of batteries include the battery and a next battery determined in the charging schedule to start charging next to the battery, sequentially sending a charge start instruction to each of the plurality of batteries for energy management of a power grid (PG), When it is determined that charging of the battery is nearing completion, charging resources (70, 130) connected to the power grid are charged so as to compensate for a reduction in charging power caused by the charging power compression control. a backup resource that is connected to the power grid and for which no charging schedule is determined among the charging resources controllable by the server and that compensates for a shortage of the required charging power, wherein the plurality of batteries for which charging schedules are determined by the charging schedule do not belong to the backup resource; When it is determined that the reserve capacity of the power grid is insufficient due to the near completion of charging of the battery, a process for increasing the reserve capacity of the power grid is executed, wherein a notification is sent to a portable terminal carried by a user of an electric vehicle that is not connected to the power grid to urge the user to connect the electric vehicle to the power grid, or a demand response is executed to increase the reserve capacity.

Images