Power storage device management method, vehicle control device, and vehicle

Abstract

To suppress over degrading of a power storage device.SOLUTION: A management method of a power storage device comprises: determining whether the electric power of requested charge or discharge exceeds a prescribed value when an energy management by electrical charge or discharge of the power storage device is requested from an aggregator (S22); executing the charge or discharge (S24) according to the request, if the requesting aggregator is a registered aggregator (in S23, YES) when the requested electric power exceeds the prescribed value; and not executing the charge or discharge (S24) according to the request, if the requesting aggregator is not the registered aggregator (in S23, NO) when the requested electric power exceeds the prescribed value.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a power storage device management method, a vehicle control device, and a vehicle. [Background technology]

[0002] Japanese Patent Publication No. 2020-177652 (Patent Document 1) discloses a technology in which a server that manages the rental fee paid by users for the rental of a battery for driving a vehicle collects the battery's full charge capacity from the vehicle and lowers the rental fee as the collected full charge capacity decreases. [Prior art documents] [Patent documents]

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

[0004] As the full charge capacity of an energy storage device decreases due to degradation, the value of the energy storage device also decreases. Therefore, in the technology described in Patent Document 1, the rental fee decreases as the full charge capacity decreases. However, with this technology, the rental fee becomes cheaper as the energy storage device deteriorates, so there is no incentive for users to use the energy storage device in a way that prevents it from deteriorating. If a rented energy storage device deteriorates too much, it becomes difficult for leasing companies to reuse the returned energy storage device for other purposes.

[0005] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to prevent excessive deterioration of a power storage device. [Means for solving the problem]

[0006] According to a first aspect of the present disclosure, there is provided a method for managing a power storage device, which includes, when an aggregator requests energy management by charging or discharging a power storage device, determining whether the requested charging or discharging power exceeds a predetermined value; if the requested power exceeds the predetermined value, charging or discharging the power storage device in accordance with the request if the requesting aggregator is a registered aggregator; and if the requested power exceeds the predetermined value, not charging or discharging the power storage device in accordance with the request if the requesting aggregator is not a registered aggregator.

[0007] In a method in which all aggregators are free to use energy storage devices to perform energy management, there is a possibility that the aggregators may cause excessive deterioration of the energy storage devices through energy management. In particular, rapid charging (charging of large amounts of power) and rapid discharging (discharging of large amounts of power) are likely to accelerate deterioration of the energy storage devices. Therefore, in the above method, if the charging power or discharging power for energy management exceeds a predetermined value, energy management is permitted only for known aggregators (i.e., registered aggregators). By limiting the entities that perform energy management involving rapid charging or rapid discharging to highly reliable aggregators, excessive deterioration of the energy storage devices is prevented.

[0008] According to a second aspect of the present disclosure, there is provided a vehicle control device including a processor and a storage device that stores a program that causes the processor to execute the power storage device management method, and identification information of the registered aggregator is stored in the storage device.

[0009] According to the vehicle control device, the above-mentioned management method is preferably executed. According to a third aspect of the present disclosure, there is provided a vehicle that executes the above-described method for managing a power storage device. The vehicle includes a vehicle body, a power storage device mounted on the vehicle body, and a control device that executes the method for managing the power storage device. The registered aggregator is registered in the control device.

[0010] According to the vehicle, the above-described management method can be suitably executed. The vehicle equipped with the power storage device may be an xEV (exhausted electric vehicle) that uses electricity as all or part of its power source. Examples of xEVs include BEVs (electric vehicles), HEVs (hybrid vehicles), PHEVs (plug-in hybrid vehicles), and FCEVs (fuel cell vehicles). [Effects of the Invention]

[0011] According to the present disclosure, it is possible to prevent the power storage device from deteriorating too much. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating an overview of a management system for a power storage device according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram for explaining the configuration of the vehicle shown in FIG. [Figure 3] 1 is a diagram illustrating a schematic configuration of an energy management system according to an embodiment of the present disclosure. [Figure 4] 5 is a flowchart showing control for causing a vehicle to perform energy management in a method for managing a power storage device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure will be described in detail with reference to the accompanying drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals and their description will not be repeated.

[0014] 1 is a diagram for explaining an overview of a management system for a power storage device according to this embodiment. The management system includes a dealer 100, a battery exchange station (hereinafter referred to as "BSta") 200, a management center 500, and an insurance server 600.

[0015] The management center 500 is a server that provides a leasing service for renting out power storage devices for vehicles. The management center 500 manages information related to the leasing service. The management center 500 belongs to, for example, an automobile manufacturer. In this embodiment, the automobile manufacturer also acts as a leasing business operator. The insurance server 600 is a server that provides an insurance service. The insurance service is, for example, a service that provides compensation for deterioration of a power storage device. The insurance server 600 cooperates with the management center 500 to provide an insurance service for the power storage device rented out through the above-mentioned leasing service.

[0016] Automobile manufacturers provide vehicles they manufacture to customers (vehicle users) through dealers 100. Dealer 100 includes server 150. Dealer 100 rents out power storage devices using a variety of leasing methods. Dealer 100 may, for example, rent out power storage device 12A of vehicle 10A (vehicle A) shown in FIG. 1 to a user using a partial leasing method. In vehicle A (partially leased vehicle), vehicle body 11A is owned by the user, and power storage device 12A is owned by the automobile manufacturer. Dealer 100 may also, for example, rent out vehicle 10B (vehicle B) shown in FIG. 1 to a user using a full leasing method. In vehicle B (fully leased vehicle), the entire vehicle (vehicle body 11B and power storage device 12B) is owned by the automobile manufacturer.

[0017] In this embodiment, the insurance premium is included in the lease fee (for example, monthly lease fee) charged by dealer 100 to the vehicle user. That is, each of vehicles A and B is covered by insurance provided by insurance server 600. When the power storage devices mounted on these vehicles deteriorate, the insurance applies. The insurance service allows the vehicle user to replace the power storage device free of charge, for example.

[0018] In this embodiment, a plurality of dealers 100 and a plurality of BSta 200 are installed to cover the entire area under the jurisdiction of the power storage device management system. The BSta 200 is configured to replace power storage devices for vehicles. The BSta 200 includes a server 250. Power storage devices rented by automobile manufacturers to vehicle users through the dealers 100 are returned by the vehicle users to the BSta 200. In this embodiment, secondary batteries are used as the power storage devices. However, the power storage devices may be any devices that can store electric power.

[0019] The management center 500 includes a processor 510, a storage device 520, and a communication module 530. The communication module 530 is connected to a communication network NW, for example, by wire. The management center 500, the insurance server 600, the server 150, and the server 250 are configured to be able to communicate with each other via the communication network NW. The communication network NW is, for example, a wide area network constructed by the Internet and wireless base stations.

[0020] Hereinafter, the vehicle provided by dealer 100 may be referred to as "vehicle 10." Vehicle 10 according to this embodiment is either vehicle A or B shown in FIG. 1. FIG. 2 is a diagram for explaining the configuration of vehicle 10.

[0021] Referring to FIG. 2, vehicle 10 includes a vehicle body 11 and a battery 12 mounted on vehicle body 11. Vehicle 10 may be a BEV without an internal combustion engine, or a PHEV with an internal combustion engine. A known vehicle power storage device (e.g., a lithium-ion secondary battery or a nickel-metal hydride secondary battery) can be used as battery 12. A plurality of secondary batteries may form a battery pack. Battery 12 corresponds to an example of a "power storage device" according to the present disclosure.

[0022] The vehicle body 11 includes an ECU 111, an inlet 112, a charge / discharge circuit 113, a BMS (Battery Management System) 114, and a communication device 115. The vehicle body 11 also includes an HMI (Human Machine Interface) and a position sensor (not shown). The position sensor may detect the position (e.g., longitude and latitude) of the vehicle 10 using a GPS (Global Positioning System). The BMS 114 includes various sensors for detecting the state of the battery 12 installed in the vehicle 10.

[0023] The ECU 111 is a computer including a processor 111a and a storage device 111b. The processor 111a includes, for example, a CPU (Central Processing Unit). The storage device 111b stores programs to be executed by the processor 111a. Note that ECU stands for Electronic Control Unit. The control system of the vehicle 10 (including the ECU 111) is supplied with power from an auxiliary battery (not shown).

[0024] The storage device 111b stores owner information relating to each of the vehicle body 11 and the battery 12. In this embodiment, when the dealer 100 provides the vehicle 10, the owner information relating to the vehicle 10 is written to each of the storage device of the server 150 and the storage device 111b of the vehicle 10. As a result, the owner information according to the lease contract is written to each storage device.

[0025] The owner information includes identification information of the owner and identification information of the owner's terminal. The owner identification information includes information for identifying the owner (for example, a corporate name, an identification number, etc.). The owner's terminal identification information includes information for identifying the owner's terminal (for example, an identification number, a communication address, etc.). For example, the owner information for vehicle A indicates that the owner of the vehicle body part is the vehicle user (the terminal is the mobile terminal 30) and that the owner of the power storage device is the leasing company (the terminal is the management center 500). The owner information for vehicle B indicates that the owner of each of the vehicle body part and the power storage device is the leasing company (the terminal is the management center 500).

[0026] As will be described in detail later, the management center 500 functions as an aggregator. The power storage devices (batteries 12) of the vehicles A and B are provided to the vehicles on a lease basis. The management center 500 is a terminal of the owner of each of the power storage devices of the vehicles A and B. In the vehicle 10 (vehicles A and B), identification information (AGID-A) of the management center 500 is stored in the storage device 111b as identification information indicating the terminal of the owner of the battery 12. This means that the management center 500 is registered in the ECU 111 (vehicle control device) of the vehicle 10. In this embodiment, the management center 500 corresponds to a registered aggregator.

[0027] The storage device 111b further stores information (hereinafter referred to as "BMS information") indicating the state of the battery 12 (e.g., temperature, current, voltage, SOC, and SOH) detected by the BMS 114. The SOC (State Of Charge) indicates the remaining amount of electricity stored. The SOH (State of Health) indicates the health or deterioration level of the electricity storage device. Examples of SOH include capacity maintenance rate and internal resistance. The higher the internal resistance, the greater the deterioration level of the electricity storage device. The lower the capacity maintenance rate, the greater the deterioration level of the electricity storage device. The capacity maintenance rate corresponds to the ratio of the current capacity to the capacity in the initial state. The capacity of the electricity storage device corresponds to the amount of electricity stored in a fully charged state.

[0028] EVSE stands for Electric Vehicle Supply Equipment. The main body of the EVSE 20 incorporates a control unit 21 and a circuit unit 22. The EVSE 20 further includes a charging cable 23 extending outward from the main body of the EVSE 20. The charging cable 23 is electrically connected to the circuit unit 22. The control unit 21 includes a processor and a storage device, and is configured to be able to communicate with the management center 500. The circuit unit 22 includes a circuit for supplying power to the vehicle 10 and a circuit for supplying power to the power grid PG (reverse power flow).

[0029] The inlet 112 is configured so that the connector 24 (tip) of the charging cable 23 can be attached and detached. The inlet 112 functions as a charging and discharging port. When the connector 24 of the charging cable 23 connected to the main body of the EVSE 20 is connected to the inlet 112 of the parked vehicle 10, the vehicle 10 is electrically connected to the EVSE 20 (plugged-in state). On the other hand, for example, when the vehicle 10 is traveling, the vehicle 10 is not electrically connected to the EVSE 20 (plugged-out state). The EVSE 20 further includes a connection detection circuit (not shown) that detects the state of the connector 24 (plugged-in state / plugged-out state).

[0030] The EVSE 20 and the electric power grid PG are electrically connected. Therefore, the vehicle 10 in the plugged-in state is electrically connected to the electric power grid PG. When the vehicle 10 in the plugged-in state performs external charging (charging the battery 12 with electric power from outside the vehicle), electric power supplied from the electric power grid PG is output to the connector 24 via the circuit unit 22 of the EVSE 20 and input to the inlet 112. Then, the charge / discharge circuit 113 generates charging power according to instructions from the ECU 111 using the electric power supplied from the inlet 112, and inputs the generated charging power to the battery 12. When the vehicle 10 in the plugged-in state performs external power feeding (discharging from the battery 12 to outside the vehicle), the charge / discharge circuit 113 generates feed power according to instructions from the ECU 111 using electric power discharged from the battery 12, and outputs the generated feed power to the inlet 112. Then, electric power output from the vehicle 10 is supplied (reverse power flow) to the electric power grid PG via the circuit unit 22 of the EVSE 20. The charge / discharge circuit 113 generates charging power and feeding power using a power conversion circuit (for example, at least one of a DC / DC conversion circuit and an AC / DC conversion circuit).

[0031] The communication device 115 includes a communication I / F (interface) for accessing the communication network NW via wireless communication. The communication device 115 may include a TCU (Telematics Control Unit) or a DCM (Data Communication Module) for performing wireless communication. The communication device 115 further includes a communication I / F for performing wireless communication with each of the server 250 and the mobile terminal 30. The ECU 111 is configured to communicate with each of the management center 500, the server 250, and the mobile terminal 30 via the communication device 115.

[0032] The mobile terminal 30 is carried and operated by the user (vehicle manager) of the vehicle 10. In this embodiment, a smartphone equipped with a touch panel display is used as the mobile terminal 30. The smartphone has a built-in computer and a speaker function. However, the mobile terminal 30 is not limited to this, and a portable game console, a wearable device, an electronic key, etc. can also be used as the mobile terminal 30. The identification information (terminal ID) of the mobile terminal 30 is linked to the identification information (vehicle ID) of the corresponding vehicle 10 and registered in the management center 500.

[0033] Fig. 3 is a diagram showing a schematic configuration of an energy management system according to this embodiment. Referring to Fig. 3 together with Figs. 1 and 2, a management center 500 functions as an aggregator and performs energy management of the power system PG in cooperation with the vehicle group 1 and the EVSE group 2. The power system PG is a power network constructed by power transmission and distribution facilities. A plurality of power plants and a plurality of power loads are connected to the power system PG. A server 700 manages information related to the power system PG (including supply and demand balance information).

[0034] The management center 500 is configured to be able to communicate with each of the vehicle group 1, the EVSE group 2, and the server 700 via the communication network NW. The vehicle group 1 includes a plurality of vehicles 10. The EVSE group 2 includes a plurality of EVSEs 20 that receive power from a power grid PG. The management center 500 can acquire information (SOC, charging power, discharging power, etc.) about the vehicles 10 and EVSEs 20 by performing wired communication with the vehicles 10 connected to the EVSEs 20 (vehicles 10 in a plugged-in state) via the EVSEs 20. The vehicles 10 may also transmit information to the management center 500 via wireless communication.

[0035] Identification information (vehicle ID) of each vehicle included in vehicle group 1 is registered in advance in management center 500. Storage device 520 (FIG. 1) of management center 500 stores information about each vehicle (vehicle information) distinguished by vehicle ID. The vehicle information in storage device 520 includes vehicle specifications, information indicating whether the vehicle is plugged in or not, information about the vehicle in the plugged in state (for example, the BMS information mentioned above), fee information, and incentive information.

[0036] The fee information corresponds to information about lease fees that vehicle users pay to automobile manufacturers. The lease fees correspond to fees that users pay to rent and use a vehicle or a power storage device. The fee information may indicate the unpaid amount of lease fees for each vehicle user.

[0037] The incentive information corresponds to information about incentives (e.g., points) that an automobile manufacturer pays to vehicle users who perform energy management in response to a request from the automobile manufacturer. The incentive information may indicate the amount of points saved for each vehicle user. The points may be convertible into money, goods, or rights.

[0038] The management center 500 causes the vehicle fleet 1 to perform energy management of the power grid PG in response to a request from, for example, the server 700. The vehicles 10 electrically connected to the EVSE 20 can function as DERs (Distributed Energy Resources) for a VPP (Virtual Power Plant). Specifically, in order to adjust the supply and demand balance of the power grid PG, the server 700 requests the aggregator to perform either a first energy management (e.g., a decrease in demand or an increase in supply) that reduces the ratio of power demand to power supply, or a second energy management (e.g., an increase in demand or a decrease in supply) that increases the ratio of power demand to power supply. Hereinafter, the request for the first or second energy management from the server 700 to the aggregator will also be referred to as a "VPP request." In this embodiment, not only the management center 500 but also the server 900 functions as an aggregator. The server 900 is connected to the communication network NW and accepts the VPP request from the server 700.

[0039] Upon receiving a VPP request, the aggregator requests the plugged-in vehicle 10 to manage the energy of the power grid PG by using a VPP command. The VPP command is a signal requesting energy management by charging or discharging a power storage device (e.g., the battery 12). The VPP command for the first energy management requests the vehicle 10 to externally supply (discharge) specified power. The VPP command for the second energy management requests the vehicle 10 to externally charge specified power. The VPP command may represent the discharging power as a positive (+) value and the charging power as a negative (-) value. The VPP command may request discharge power or charge power in real time. In this case, the VPP command indicates the instantaneous value of the requested power. The VPP command may also request discharge power or charge power according to a power pattern. In this case, the VPP command indicates the trend of the requested power over a certain period (power pattern) and requests the vehicle 10 to make the discharge power or charge power follow the specified power trend (power value at each time) over that period.

[0040] Hereinafter, the management center 500 may be referred to as "aggregator A" and the server 900 may be referred to as "aggregator B." When aggregator A or B sends a VPP command to a plugged-in vehicle 10 requesting energy management of the power grid PG, if the vehicle 10 complies with the request, the energy management requested by the aggregator is executed. Each of the multiple vehicles 10 included in the vehicle fleet 1 may receive VPP commands from both aggregators A and B.

[0041] Aggregator A manages battery 12 of vehicle 10 based on information acquired from vehicle 10 to prevent battery 12 from deteriorating too much (see S13 to S16 in FIG. 4, which will be described later). Aggregator A is registered with vehicle 10 (see FIG. 2). In contrast, aggregator B is not configured to acquire information about the state of battery 12 from vehicle 10, and does not manage battery 12 of vehicle 10. Aggregator B is not registered with vehicle 10.

[0042] 4 is a flowchart showing energy management control according to this embodiment. In the following, each step in the flowchart will be simply represented as "S."

[0043] The series of processes (S11 to S16) shown on the left side of Fig. 4 are repeatedly executed by the management center 500. These processes are executed for the vehicles 10 in the plugged-in state among the multiple vehicles 10 included in the vehicle group 1 shown in Fig. 3. When multiple vehicles 10 are in the plugged-in state, the management center 500 executes the series of processes (S11 to S16) shown in Fig. 4 for each vehicle. Hereinafter, the plugged-in vehicle 10 (vehicle A or vehicle B) that is the target of the process will be referred to as the "target vehicle."

[0044] 1 to 3 as well as FIG. 4, in S11, the management center 500 determines whether or not it has received a VPP request (a discharge request for the first energy management or a charge request for the second energy management) from the server 700. If the management center 500 has not received a VPP request (NO in S11), the process proceeds to S13. In this case, the management center 500 does not transmit a VPP command (energy management request) to the target vehicle.

[0045] On the other hand, if the management center 500 has received a VPP request (YES in S11), the management center 500 transmits a VPP command (discharge request or charge request) in response to the VPP request from the server 700 to the target vehicle in S12. At this time, the management center 500 transmits the identification information of aggregator A (AGID-A) along with the VPP command to the target vehicle. After the process of S12 is executed, the process returns to the first step (S11). While the server 700 is continuously transmitting VPP requests to the management center 500, S12 is repeated, and the transmission of VPP commands from the management center 500 to the target vehicle is continuously executed. Then, when the transmission of the VPP request by the server 700 is completed, a NO determination is made in S11, and the process proceeds to S13.

[0046] In S13, the management center 500 acquires BMS information (including SOH) indicating the current state of the battery 12 mounted on the target vehicle from the target vehicle. For example, when the management center 500 requests the target vehicle to transmit BMS information, the target vehicle updates the BMS information in response to this request and transmits the latest BMS information to the management center 500.

[0047] In S14, the management center 500 determines whether the deterioration level of the battery 12 installed in the target vehicle is greater than a predetermined value (hereinafter referred to as "Th1"). The deterioration level of the battery 12 is indicated by the SOH (for example, capacity maintenance rate or internal resistance). If the deterioration level of the battery 12 is greater than Th1 (YES in S14), the processing of S15 and S16 described below is executed. On the other hand, if the deterioration level of the battery 12 is equal to or less than Th1 (NO in S14), the processing skips S15 and S16 and returns to the initial S11.

[0048] In S15, the management center 500 sends a notification (replacement notification) to the target vehicle urging it to replace the battery 12. Subsequently, in S16, the management center 500 acquires the location information of the target vehicle from the target vehicle, and permits one or more BSta 200 present in the vicinity of the target vehicle (for example, one BSta 200 closest to the current location of the target vehicle, or at least one BSta 200 present within a predetermined distance from the current location of the target vehicle) to replace the battery 12 installed in the target vehicle. Specifically, the management center 500 transmits an exchange permission signal including identification information (vehicle ID) of the target vehicle to one or more BSta 200 present in the vicinity of the target vehicle. This exchange permission signal permits the BSta 200 to replace the battery of the target vehicle. The server 250 identifies the vehicle to be replaced based on the vehicle ID included in the received exchange permission signal. After the processing of S16 has been executed, the processing returns to the initial S11.

[0049] In the method for managing a power storage device according to this embodiment, the processes of S15 and S16 are executed when the degree of degradation of the battery 12 becomes large, which makes it easier to replace the battery early. Furthermore, if the degree of degradation of the battery 12 becomes larger than Th1 after energy management is executed by charging or discharging the battery 12, the processes of S15 and S16 are executed, thereby preventing the battery 12 from deteriorating too much.

[0050] 4 (S21 to S26) is repeatedly executed by the ECU 111 of the target vehicle (vehicle 10 in a plugged-in state). In S21, the ECU 111 of the target vehicle determines whether the target vehicle has received a VPP command from the aggregator. If the target vehicle has not received a VPP command (NO in S21), the process proceeds to S25.

[0051] When the target vehicle receives a VPP command (YES in S21), the ECU 111 determines in S22 whether the magnitude of the charging or discharging power requested by the VPP command exceeds a predetermined value (hereinafter referred to as "Th2"). Specifically, when the VPP command indicates an instantaneous value of the requested power, the ECU 111 determines whether the instantaneous value (absolute value) exceeds Th2. When the VPP command indicates a requested power pattern (transition of power over a certain period), the ECU 111 determines whether the maximum power value (absolute value) over that period exceeds Th2. However, the present invention is not limited to this, and the ECU 111 may determine whether the magnitude of the requested power exceeds Th2 based on an average power value (absolute value) instead of the maximum power value.

[0052] If the amount of power requested by the VPP command exceeds Th2 (YES in S22), the ECU 111 determines in S23 whether the aggregator that transmitted the VPP command is an aggregator registered with the target vehicle. The ECU 111 makes this determination based on, for example, whether the aggregator identification information (AGID) included in the VPP command received by the target vehicle matches the AGID (e.g., identification information indicating the owner of the battery 12 shown in FIG. 2) stored in the storage device 111b of the target vehicle. If the two AGIDs match, it means that the aggregator that transmitted the VPP command is registered with the target vehicle. On the other hand, if the two AGIDs do not match, it means that the aggregator is not registered with the target vehicle. Also, if the VPP command does not include an AGID, it means that the aggregator that transmitted the VPP command is not registered with the target vehicle.

[0053] If the aggregator that sent the VPP command is not registered with the target vehicle (NO in S23), the process proceeds to S25. In this case, the charging or discharging requested by the VPP command (S24) is not executed. In this embodiment, if the aggregator that sent the VPP command is aggregator B, the determination in S23 is NO.

[0054] If the aggregator that sent the VPP command is registered in the target vehicle (YES in S23), the process proceeds to S24. In this embodiment, if the aggregator that sent the VPP command is aggregator A, the determination in S23 is YES. Also, if the amount of power requested by the VPP command is equal to or less than Th2 (NO in S22), the process proceeds to S24. In this embodiment, if either "NO in S22" or "YES in S23" is true, the requirement for allowing the energy management requested by the aggregator in the target vehicle (hereinafter also referred to as "VPP requirement") is satisfied.

[0055] In S24, the ECU 111 controls the charge / discharge circuit 113 so that the battery 12 is externally charged or externally powered as requested by the VPP command. After S24 is executed, the process returns to S21. While the target vehicle continuously receives a VPP command that satisfies the VPP requirements, S24 is repeated, and the battery 12 is externally charged or externally powered in accordance with the VPP command. When the aggregator finishes transmitting the VPP command, a NO determination is made in S21, and the process proceeds to S25. After energy management is completed, the aggregator provides an incentive to the user of the target vehicle that performed energy management in accordance with the VPP command, based on the performance of the energy management.

[0056] In S25, the ECU 111 determines whether the target vehicle has received a replacement notification (S15) from the management center 500. If the target vehicle has received the replacement notification (YES in S25), in S26 the ECU 111 controls the user terminal (e.g., the mobile terminal 30) of the target vehicle so that the user terminal prompts the user by display or audio to replace the battery 12. Once the notification process to the user in S26 has been executed, the process returns to the first step (S21). Note that the user terminal is not limited to a mobile terminal and may be an in-vehicle HMI.

[0057] A user who is prompted to replace the battery 12 may drive the target vehicle to the BSta 200. When the target vehicle requests replacement of the battery 12, for example, by wireless communication, the server 250 of the BSta 200 determines whether battery replacement is permitted based on the identification information of the target vehicle. If the server 250 determines that battery replacement is permitted for the target vehicle, the BSta 200 performs the requested battery 12 replacement. The BSta 200 may perform battery replacement fully automatically. However, the BSta 200 will not perform a battery replacement that is not permitted. The automobile manufacturer may reuse the power storage device returned to the BSta 200 for purposes other than automobiles (such as stationary use).

[0058] As described above, the method for managing a power storage device according to this embodiment includes the processes shown in Fig. 4. ECU 111 includes processor 111a and storage device 111b that stores a program that causes processor 111a to execute the processes of S21 to S26 in Fig. 4. The method for managing a power storage device includes, when an aggregator requests energy management by charging or discharging the power storage device, determining whether the requested power for charging or discharging exceeds a predetermined value (Th2) (S22), and, when the requested power exceeds the predetermined value, if the aggregator that made the request is a registered aggregator (YES in S23), executing the requested charging or discharging of the power storage device (S24), and, when the requested power exceeds the predetermined value, if the aggregator that made the request is not a registered aggregator (NO in S23), not executing the requested charging or discharging of the power storage device (S24). In this method, when the vehicle 10 receives a request from an aggregator for energy management using rapid charging (charging of large power) or rapid discharging (discharging of large power), the ECU 111 (a control device for the power storage device) permits energy management only from known aggregators (i.e., a pre-registered aggregator A). By limiting the subject of energy management involving rapid charging or rapid discharging to highly reliable aggregators, excessive deterioration of the power storage device (battery 12) is suppressed.

[0059] In the method for managing a power storage device according to this embodiment, the registered aggregator is a terminal (management center 500) of a leasing company. This makes it easier for the leasing company (the owner of battery 12) to manage battery 12. For example, the management center 500 may determine a VPP command for vehicle 10 based on the degree of deterioration of battery 12 so as to prevent battery 12 from deteriorating too much.

[0060] The method for managing a power storage device according to this embodiment further includes, when the requested power level is below the predetermined value (Th2) (NO in S22), executing charging or discharging of the power storage device in accordance with the request (S24), regardless of whether the requesting aggregator is a registered aggregator. In this method, for energy management that is unlikely to cause degradation of the power storage device (energy management that does not involve rapid charging or rapid discharging), the ECU 111 (power storage device control device) of the vehicle 10 permits energy management without limiting the aggregator. This achieves both suppressing degradation of the power storage device and meeting energy management requests.

[0061] The processing flow shown in Fig. 4 can be modified as appropriate. For example, the order of processing can be changed or unnecessary steps can be omitted depending on the purpose. Furthermore, the content of any of the processing can be changed. For example, S13 to S16 and S25 and S26 can be omitted.

[0062] The configuration of the vehicle can be changed as appropriate. The vehicle may be configured to be capable of wireless charging. A vehicle performing wireless charging may be considered to be in a state equivalent to the "plugged-in state" described above when the alignment between the power transmission unit (e.g., a power transmission coil) on the power supply equipment side and the power receiving unit (e.g., a power receiving coil) on the vehicle side is completed. The vehicle may be configured to be capable of only one of external charging and external power feeding.

[0063] There may be only one type of leasing method (for example, a partial leasing method). In the above embodiment, only the battery is replaced, but the battery pack including the battery and its accessories may be replaced together. The power storage device used for energy management is not limited to an in-vehicle battery, and may be a stationary power storage device.

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

[0065] 10 vehicles, 11 vehicle bodies, 12 batteries, 20 EVSE, 30 mobile terminals, 100 dealers, 111 ECUs, 111a processors, 111b storage devices, 200 battery exchange stations, 500 management centers, 150, 250, 700, 900 servers, 600 insurance servers.

Claims

1. When a control device is requested by an aggregator to perform energy management by charging or discharging a storage device controlled by the control device, the control device determines whether the magnitude of the requested charging or discharging power exceeds a predetermined value; When the magnitude of the requested power exceeds the predetermined value, if the aggregator that made the request is an aggregator registered in the control device, the control device executes charging or discharging of the power storage device in accordance with the request; When the magnitude of the requested power exceeds the predetermined value, if the aggregator that made the request is not an aggregator registered in the control device, the control device does not execute charging or discharging of the power storage device in accordance with the request; A method for managing an electricity storage device, comprising:

2. the power storage device is provided to the vehicle through a lease, The method for managing a power storage device according to claim 1 , wherein the aggregator registered in the control device is a terminal of an owner of the power storage device.

3. When the magnitude of the requested power is below the predetermined value, the control device executes charging or discharging of the power storage device in accordance with the request, regardless of whether the aggregator that made the request is an aggregator registered in the control device; The method for managing a power storage device according to claim 1 , further comprising:

4. A vehicle control device that executes a management method for a power storage device mounted on a vehicle, The management method includes: When an aggregator requests energy management by charging or discharging the power storage device, determining whether the magnitude of the requested power for charging or discharging exceeds a predetermined value; When the magnitude of the requested power exceeds the predetermined value, if the aggregator that made the request is a registered aggregator, charging or discharging the power storage device in accordance with the request; When the magnitude of the requested power exceeds the predetermined value, if the aggregator that made the request is not the registered aggregator, not charging or discharging the power storage device in accordance with the request; Including, The vehicle control device, wherein the registered aggregator is registered in the vehicle control device.

5. A vehicle body, an electricity storage device mounted on the vehicle body; A vehicle including a control device that executes the method for managing the power storage device, The management method includes: When an aggregator requests energy management by charging or discharging the power storage device, determining whether the magnitude of the requested power for charging or discharging exceeds a predetermined value; When the magnitude of the requested power exceeds the predetermined value, if the aggregator that made the request is a registered aggregator, charging or discharging the power storage device in accordance with the request; When the magnitude of the requested power exceeds the predetermined value, if the aggregator that made the request is not the registered aggregator, not charging or discharging the power storage device in accordance with the request; Including, The registered aggregator is registered with the control device.

Images