Electricity storage device management method and management system, computer device, and vehicle

Abstract

To provide a management method for a power storage device and a vehicle that, when the body of the vehicle including a lent power storage device is broken, facilitate an owner of the power storage device to recover the power storage device from the vehicle.SOLUTION: A management method for a power storage device includes: when detecting that the body of a vehicle including a lent power storage device is broken, determining whether the power storage device is in a controllable state (S151); when determining that the power storage device is in a controllable state, setting restrictions on the output of the power storage device (S152); and when detecting that the body of the vehicle is broken, transmitting, to a terminal of an owner of the power storage device, a recovery request signal for requesting recovery of the power storage device from the vehicle (S16).SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] Japanese Patent Application Laid-Open Publication No. 2020-135311 (Patent Document 1) discloses a technology for identifying a vehicle driver when a possibility of vehicle damage is detected based on information about the vehicle driver. This technology is applied to, for example, a vehicle sharing system. [Prior art documents] [Patent documents]

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

[0004] In recent years, countries around the world have been moving towards the electrification of vehicles, with particular attention being paid to technologies in the four areas known as "CASE" (connected, automated, shared, and electrified). Currently popular vehicle leasing services (including vehicle sharing services) involve the rental of entire vehicles. However, in the future, services that rent out vehicle energy storage devices alone, rather than entire vehicles, may become more common.

[0005] A user who receives the service can install the rented power storage device in the body of an electric vehicle owned by the user, thereby enabling the user to use the electric vehicle at low cost. However, if the body of such an electric vehicle is damaged, for example, in an accident, there is a possibility that the power storage device will be collected and disposed of along with the vehicle body. According to the technology described in Patent Document 1, when a vehicle is damaged, the driver of the vehicle can be identified, but the owner of the power storage device cannot be identified. The owner of the power storage device cannot know that the vehicle has been damaged. Therefore, when the vehicle body is damaged, it is difficult for the owner of the power storage device to collect the power storage device from the vehicle.

[0006] The present disclosure has been made to solve the above-mentioned problem, and its purpose is to make it easier for the owner of a rented power storage device to recover the power storage device from the vehicle when the body of the vehicle equipped with the rented power storage device is damaged. [Means for solving the problem]

[0007] According to an embodiment of a first aspect of the present disclosure, there is provided a method for managing a power storage device as follows. (Article 1) The method for managing the storage device includes, when it is detected that the body of a vehicle equipped with a rented storage device has been damaged, determining whether the storage device is in a controllable state, setting an output limit for the storage device on the vehicle when it is determined that the storage device is in a controllable state, and, when it is detected that the body of the vehicle has been damaged, transmitting a recovery request signal to a terminal of the owner of the storage device, requesting that the storage device be recovered from the vehicle.

[0008] In the above management method, when damage to the vehicle body (e.g., body shell) is detected, a request is made to a terminal of the owner of the power storage device to retrieve the power storage device from the vehicle. The above-mentioned retrieval request signal makes it easier for the owner of the power storage device to retrieve the power storage device from the vehicle. Furthermore, when the power storage device is in a controllable state, an output limit for the power storage device is set for the vehicle. By limiting the use of the power storage device in this way, it is possible to prevent the owner of the power storage device from installing another power storage device on a repaired vehicle body before retrieving the power storage device, thereby preventing the vehicle from being used fraudulently. This makes it easier for the owner of the power storage device to retrieve the power storage device from the vehicle.

[0009] The terminal of the owner of the power storage device may be a stationary computer (for example, a server) or a terminal carried by the owner of the power storage device (for example, a smartphone).

[0010] The management method described in the above item 1 may have the configuration described in any one of items 2 to 4 below.

[0011] (Item 2) The management method according to item 1 further includes the following feature: When the power storage device is collected by an owner of the power storage device from the vehicle on which the output limit has been set, the management method further includes canceling the output limit set on the vehicle.

[0012] According to the above method, after the owner of the power storage device collects the power storage device, the vehicle user can use the vehicle by mounting another power storage device on the repaired vehicle body.

[0013] (Item 3) The management method according to item 1 or 2 further has the following features. The management method further includes determining whether an accident has occurred with the vehicle, and determining whether the vehicle body has been damaged if it is determined that an accident has occurred with the vehicle. Determining whether the vehicle body has been damaged includes determining that the vehicle body has been damaged if the vehicle body has been damaged to the extent that it cannot continue traveling, and determining that the vehicle body has not been damaged if the vehicle body has not been damaged to the extent that it cannot continue traveling.

[0014] According to the above method, when the vehicle cannot continue traveling, a request is made to the terminal of the owner of the power storage device to retrieve the power storage device from the vehicle. This makes it easier for the owner of the power storage device to retrieve the power storage device from the vehicle. Note that the state in which traveling cannot continue includes a state in which traveling is not possible at all, as well as a state in which evacuation traveling is possible but normal traveling (traveling other than evacuation traveling) cannot be continued.

[0015] (Item 4) The management method according to item 3 further includes the following feature: when an accident occurs with a vehicle and it is determined that the vehicle body is not damaged, transmitting an exchange request signal to a terminal of an owner of the electric storage device, requesting permission to exchange the electric storage device mounted on the vehicle.

[0016] According to the above method, if the vehicle is able to continue traveling, the vehicle can continue traveling to a location where the power storage device can be replaced, and the owner of the power storage device can collect the power storage device from the vehicle by allowing the power storage device to be replaced at a predetermined location.

[0017] According to one aspect, there is provided a program for causing a computer to execute the method for managing a power storage device according to any one of aspects 1 to 4. In another aspect, there is provided a computer device for distributing the program.

[0018] According to an embodiment of a second aspect of the present disclosure, there is provided a computer device as follows. (Item 5) The computer device includes a processor and a storage device that stores a program that causes the processor to execute the method for managing a power storage device according to any one of items 1 to 4.

[0019] The above-described computer device can suitably execute the above-described method for managing the power storage device. According to an embodiment of a third aspect of the present disclosure, there is provided a management system for a power storage device as described below.

[0020] (Item 6) The management system for the power storage device includes a vehicle equipped with the computer device described in item 5, and a server that provides a leasing service for lending out a power storage device to the vehicle. A storage device of the computer device stores owner information indicating that the terminal of the owner of the power storage device mounted on the vehicle is the server. The computer device is configured to set an output limit for the power storage device on the vehicle and transmit a recovery request signal to the server when it detects that the vehicle body has been damaged and determines that the power storage device is in a controllable state.

[0021] According to the above configuration, if the body of a vehicle equipped with a power storage device rented out through a leasing service is damaged, the computer device installed in the vehicle can use the owner information stored in the storage device to request the server providing the leasing service to collect the power storage device.

[0022] The power storage device management system described in the above item 6 may have the configuration described in item 7 below.

[0023] (Item 7) The management system described in item 6 further includes a plurality of exchange stations that exchange electric storage devices for vehicles. The computer device is configured to transmit an exchange request signal to the server requesting permission to exchange the electric storage device mounted on the vehicle. When the server receives the exchange request signal, it requests the exchange station to secure an electric storage device that can be exchanged for the electric storage device.

[0024] According to the above system, when the power storage device mounted on the vehicle needs to be replaced, the exchange station can more easily prepare a replacement power storage device quickly.

[0025] According to an embodiment of a fourth aspect of the present disclosure, there is provided a vehicle as follows. (Item 8) The vehicle is configured to execute the method for managing an electricity storage device according to any one of Items 1 to 4. The vehicle includes a vehicle body, an electricity storage device mounted on the vehicle body, a detector that detects damage to the vehicle body, a first control device that executes the management method for the electricity storage device, and a second control device that controls the electricity storage device. The first control device is configured to determine whether the vehicle body is damaged based on a detection result by the detector. The second control device is configured to determine whether the electricity storage device is in a controllable state when it is determined that the vehicle body is damaged. The first control device is configured to set an output limit for the electricity storage device in the second control device when it is determined that the electricity storage device is in a controllable state.

[0026] According to the vehicle, the above-described method for managing the power storage device can be suitably carried out. 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]

[0027] According to the present disclosure, when the body of a vehicle equipped with a rented power storage device is damaged, it becomes possible for the owner of the power storage device to easily retrieve the power storage device from the vehicle. [Brief explanation of the drawings]

[0028] [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] 5 is a flowchart showing control executed by a vehicle when an accident occurs in a method for managing a power storage device according to an embodiment of the present disclosure. [Figure 4] 5 is a flowchart showing control executed by a server (a terminal of an owner of a power storage device) when an accident occurs in a power storage device management method according to an embodiment of the present disclosure. [Figure 5] 5 is a flowchart showing a process related to battery exchange executed by a vehicle and an exchange station terminal in a method for managing an electricity storage device according to an embodiment of the present disclosure. [Figure 6] 1 is a diagram illustrating a configuration and operation of an exchange station included in a management system for an electricity storage device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0029] 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.

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

[0031] The management center 500 is a server that provides a leasing service for renting out power storage devices for vehicles (for example, for xEVs). 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 for damage to power storage devices for vehicles (for example, for xEVs). This insurance service is a service that compensates for damage to power storage devices mounted on vehicles. The insurance server 600 manages information related to the insurance service. The insurance server 600 belongs to, for example, an insurance provider. The insurance server 600 cooperates with the management center 500 to provide an insurance service for damage to power storage devices rented out through the leasing service.

[0032] The above leasing service employs several types of leasing methods, including partial leasing and full leasing. The partial leasing method is a leasing method in which only the power storage device for a vehicle is rented out. A user who rents out a power storage device under the partial leasing method provides the rest of the vehicle (the body portion) excluding the power storage device. The user can install the power storage device rented from the leasing company in a vehicle body that the user owns. An xEV becomes capable of running when the power storage device is installed in the body. When the partial leasing contract expires, the user returns only the power storage device to the leasing company. On the other hand, the full leasing method is a leasing method in which the entire vehicle (i.e., both the body portion and the power storage device) is rented out. When the full leasing contract expires, the user returns not only the power storage device but also the entire vehicle to the leasing company.

[0033] The dealer 100 includes a server 150. Automobile manufacturers sell or lease vehicles through the dealer 100. The dealer 100 not only sells vehicles manufactured by the automobile manufacturers but also provides the leasing service described above. The server 150 manages information (vehicle information) related to the vehicles sold or leased by the dealer 100, distinguishing them by vehicle ID. The server 150 then transmits the latest vehicle information to the management center 500 in response to a request from the management center 500 or whenever the vehicle information is updated. The dealer 100 rents out at least one of a vehicle body and a power storage device provided by the automobile manufacturer. For example, the dealer 100 may rent out the power storage device 12A of the vehicle 10A shown in FIG. 1 to a user by a partial leasing system. In this case, the vehicle 10A corresponds to a partially leased vehicle (hereinafter, sometimes referred to as "vehicle A"), and the vehicle body 11A of the vehicle 10A becomes the property of the user. Then, power storage device 12A of vehicle 10A is provided to the user through leasing and becomes the property of the automobile manufacturer. Dealer 100 may also lend vehicle 10B shown in FIG. 1 to the user through a full leasing system, for example. In this case, vehicle 10B corresponds to a fully leased vehicle (hereinafter may be referred to as "vehicle B"). Then, the entire vehicle 10B (body 11B and power storage device 12B) is provided to the user through leasing and becomes the property of the automobile manufacturer. Dealer 100 may also sell vehicle 10C shown in FIG. 1 to the user, for example. In this case, vehicle 10C corresponds to a vehicle for sale (hereinafter may be referred to as "vehicle C"). Then, the entire vehicle 10C (body 11C and power storage device 12C) is sold to the user and becomes the property of the user.

[0034] In this embodiment, the insurance fee is included in the lease fee (for example, monthly lease fee) charged by the dealer 100 to the vehicle user. Vehicles leased by the dealer 100 are covered by insurance (more specifically, insurance for damage to the power storage device) provided by the insurance server 600. That is, for each of vehicles A and B, insurance is applied when the power storage device installed in the vehicle is damaged. The insurance service provides compensation for damage to the power storage device. Since the above insurance is for lease purposes, vehicle C is not covered by the above insurance. However, vehicle C may be covered by a different insurance.

[0035] The BSta 200 is configured to replace a power storage device for a vehicle (for example, for an xEV). The BSta 200 includes a server 250. In this embodiment, a battery (more specifically, a secondary battery) is used as the power storage device. However, the power storage device may be any device that can store electric power, and examples of the power storage device include a secondary battery and a large-capacity capacitor.

[0036] The power storage device management system according to this embodiment includes a plurality of BSta 200. These BSta 200 are installed at respective bases within the jurisdiction of the management system so as to establish a network of battery exchange bases covering the entire jurisdiction of the management system. Each BSta 200 may also function as a vehicle repair shop. Each BSta 200 may also be configured to repair vehicle bodies. Furthermore, although only one dealer 100 is shown in FIG. 1 , the management system may include a plurality of dealers 100. These dealers 100 may also be installed at respective bases within the jurisdiction of the management system so as to establish a network of sales / lease bases covering the entire jurisdiction of the management system. The dealer 100 and the BSta 200 may also be installed in the same location (or nearby).

[0037] The management center 500 includes a processor 510, a storage device 520, and a communication module 530. The insurance server 600 includes a processor 610, a storage device 620, and a communication module 630. Each of the processors 510, 610 includes, for example, a CPU (Central Processing Unit). Each of the storage devices 520, 620 is configured to be able to save stored information. Each of the storage devices 520, 620 may include an HD (Hard Disk) drive or an SSD (Solid State Drive). Each of the communication modules 530, 630 is connected to a communication network NW, for example, by a wire. Furthermore, each of the server 150 and the server 250 is also connected to the communication network NW, for example, by a 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. The communication network NW may include a mobile phone network.

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

[0039] Referring to FIG. 2, vehicle 10 includes a vehicle body 11 and a battery 12 mounted on vehicle body 11. Vehicle 10 is configured to be able to run using the power of battery 12. Vehicle 10 is, for example, a BEV that does not include an internal combustion engine. A known vehicle power storage device (for example, a liquid secondary battery or an all-solid-state secondary battery) can be used as battery 12. Examples of vehicle secondary batteries include lithium-ion batteries and nickel-metal hydride batteries. 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.

[0040] The vehicle body 11 includes an ECU 111, a battery ECU 112, a BMS (Battery Management System) 112a, a temperature control system 112b, an inlet 113, a charger 114, an SMR (System Main Relay) 115a, a charging relay 115b, a PCU (Power Control Unit) 116a, an MG (Motor Generator) 116b, an HMI (Human Machine Interface) 117a, a navigation system (hereinafter referred to as "NAVI") 117b, an accident detector 118a, a body damage detector 118b, and a communication device 119. Note that ECU stands for Electronic Control Unit. The control system including each ECU mounted on the vehicle body 11 is supplied with power from an auxiliary battery (not shown).

[0041] The ECU 111 is a computer including a processor 111a and a storage device 111b. The storage device 111b stores information used by the programs (for example, maps, formulas, and various parameters) in addition to the programs executed by the processor 111a. The storage device 111b also stores various types of information related to the vehicle 10. This information is updated according to the status of the vehicle 10. Although the configuration of the battery ECU 112 is not shown in FIG. 2, the battery ECU 112 is also a computer having a hardware configuration similar to that of the ECU 111. The ECU 111 and the battery ECU 112 are configured to be able to communicate with each other. These ECUs are connected by, for example, a CAN (Controller Area Network).

[0042] The BMS (Battery Management System) 112a includes sensors for detecting the state of the battery 12 (for example, temperature, current, and voltage). The detection results by the BMS 112a are output to the battery ECU 112. The temperature adjustment system 112b adjusts the temperature of the battery 12. The temperature adjustment system 112b may include at least one of a heater and a cooling device. The cooling method may be a water-cooling type. The temperature adjustment system 112b is controlled by the battery ECU 112.

[0043] The vehicle 10 is configured to be able to perform external charging (charging the battery 12 with power from outside the vehicle). The inlet 113 is configured to allow a plug (e.g., a connector of a charging cable) of EVSE (Electric Vehicle Supply Equipment) to be attached and detached. The charger 114 includes a power conversion circuit for external charging. The charger 114 may include at least one of a DC / DC conversion circuit and an AC / DC conversion circuit. The charging relay 115b switches between connection and disconnection of a charging line. In the example shown in FIG. 2, a charging line including the inlet 113, the charger 114, and the charging relay 115b is connected between the SMR 115a and the PCU 116a. However, this is not limited thereto, and a charging line may also be connected between the battery 12 and the SMR 115a. The configuration shown in FIG. 2 may also be modified to enable external power supply (power supply from the battery 12 to outside the vehicle). For example, the charger 114 shown in FIG. 2 may be replaced with a charger / discharger.

[0044] The SMR 115a switches between connection and disconnection of an electric path from the battery 12 to the PCU 116a. When the vehicle 10 is running, the SMR 115a is connected and the charging relay 115b is disconnected. When power is exchanged between the battery 12 and the inlet 113, both the SMR 115a and the charging relay 115b are connected. The charger 114, the SMR 115a, and the charging relay 115b are each controlled by the battery ECU 112. The battery ECU 112 receives control commands from the ECU 111.

[0045] The PCU 116a drives the MG 116b using power supplied from the battery 12. The PCU 116a includes, for example, an inverter and a DC / DC converter. The PCU 116a is controlled by the ECU 111. The MG 116b functions as a traction motor for the vehicle 10. The MG 116b is driven by the PCU 116a to rotate the drive wheels of the vehicle 10. The MG 116b also performs regenerative power generation and outputs the generated power to the battery 12. The vehicle 10 may be equipped with any number of traction motors.

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

[0047] The NAVI 117b includes a touch panel display, a GPS (Global Positioning System) sensor, a processor, and a storage device that stores map information. The map information indicates the locations of each dealer 100 and each BSta 200. The map information may be updated sequentially via OTA (Over The Air). The GPS sensor functions as a position sensor and detects the location of the vehicle 10. The NAVI 117b detects the location of the vehicle 10 using the GPS sensor and displays the location of the vehicle 10 in real time on a map based on the map information. The NAVI 117b refers to the map information and performs a route search to find an optimal route (e.g., the shortest route) from the current location of the vehicle 10 to the destination.

[0048] When the accident detector 118a detects an accident in the vehicle 10, it outputs an accident detection signal to the ECU 111. An example of an accident is a traffic accident (object collision) in which the traveling vehicle 10 hits another vehicle or an obstacle. When an accident occurs in the vehicle 10, the acceleration of the vehicle 10 changes suddenly. In this embodiment, when an acceleration sensor mounted on the vehicle 10 detects acceleration equal to or greater than a predetermined value, the accident detector 118a outputs the accident detection signal to the ECU 111. The accident detector 118a may use a drive recorder (not shown) mounted on the vehicle 10 for accident detection. For example, an accident in the vehicle 10 may be detected when an acceleration sensor (G sensor) of the drive recorder detects acceleration equal to or greater than a predetermined value.

[0049] However, the accident detection method is not limited to the above and is arbitrary. For example, the accident detector 118a may use an impact force sensor to output an accident detection signal to the ECU 111 when an impact force equal to or greater than a predetermined value is applied to the vehicle 10. Alternatively, the accident detector 118a may detect an accident in the vehicle 10 based on video of the surroundings of the vehicle 10 recorded by a drive recorder (for example, video from a camera capturing the surroundings of the vehicle 10). The accident detector 118a may include an image processing circuit for accident detection. Furthermore, the accident detector 118a may analyze acceleration data of the vehicle 10 and determine whether or not an accident has occurred in the vehicle 10 based on the analysis results.

[0050] When the body damage detector 118b detects that the vehicle body 11 (for example, the body shell) is damaged, it outputs a body damage signal to the ECU 111. When the body damage detector 118b according to this embodiment detects that the vehicle body 11 is damaged to the extent that the vehicle 10 cannot continue traveling, it outputs a body damage signal indicating that the vehicle body 11 is damaged to the ECU 111. In this embodiment, when the body damage detector 118b detects a break in the vehicle body wiring (wiring connected to the vehicle body 11) using a break detection circuit provided in the front part of the vehicle body 11, it outputs the body damage signal to the ECU 111.

[0051] However, the method of detecting body damage is not limited to the above and is arbitrary. For example, the body damage detector 118b may output a body damage signal to the ECU 111 when it detects a deformation (strain) amount equal to or greater than a predetermined value using a strain gauge provided in the front portion of the vehicle body 11. The predetermined value may be set to a value at which the vehicle 10 cannot continue traveling, for example. Each of the strain gauges and open circuit detection circuits for detecting body damage may be provided in at least one of the lateral portions (both side portions) and rear portion of the vehicle body 11 in addition to or instead of the front portion of the vehicle body 11.

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

[0053] The mobile terminal 20 is configured to be portable by the user. The mobile terminal 20 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 20. A smartphone has a built-in computer and a speaker function. However, the mobile terminal 20 is not limited to this, and any terminal that can be carried by the user of the vehicle 10 can be used as the mobile terminal 20. For example, a laptop, a tablet terminal, a portable game console, a wearable device (such as a smart watch, smart glasses, or smart gloves), or an electronic key can also be used as the mobile terminal 20. In this embodiment, the HMI 117a, the NAVI 117b, and the mobile terminal 20 can each function as a user terminal of the target vehicle.

[0054] Application software (hereinafter referred to as "mobile app") for using services provided by the management center 500 is installed on the mobile terminal 20. The mobile app associates the identification information (terminal ID) of the mobile terminal 20 with the identification information (vehicle ID) of the corresponding vehicle 10 and registers the information in the management center 500. The mobile terminal 20 can exchange information with the management center 500 through the mobile app. The mobile terminal 20 may be configured to be able to communicate with each of the insurance server 600, the server 250, and the server 150 (FIG. 1).

[0055] In the vehicle 10, the ECU 111 performs integrated control of the entire vehicle. The ECU 111 acquires detection results from various sensors (including an accident detector 118a and a body damage detector 118b) mounted on the vehicle 10. The ECU 111 also acquires information from each of the battery ECU 112, the HMI 117a, the NAVI 117b, and the communication device 119. The battery ECU 112 acquires the status of the battery 12 (e.g., temperature, current, voltage, SOC, and SOH) based on the output of the BMS 112a, and outputs the acquired status of the battery 12 to the ECU 111. The vehicle information acquired by the ECU 111 is stored in the storage device 111b. The vehicle 10 transmits the latest vehicle information together with its own vehicle ID to the management center 500 in response to a request from the management center 500 or whenever the vehicle information is updated. The vehicle ID may be a VIN (Vehicle Identification Number).

[0056] The vehicle information held by the vehicle 10 (storage device 111b) includes battery information, which will be described below.

[0057] The battery information of the vehicle 10 corresponds to information about the battery 12 in a state where it is installed in the vehicle 10. The battery information includes identification information (battery ID), owner information, specifications (e.g., initial capacity, charging performance, and discharging performance), SOC (State Of Charge), and SOH (State of Health).

[0058] The owner information in the battery information indicates the battery owner (i.e., the owner of the battery 12). More specifically, the owner information includes identification information and contact information of the battery owner. The identification information of the battery owner includes information for identifying the owner of the battery 12 (e.g., name, corporate name, identification number, identification symbol, etc.). The contact information of the battery owner includes information for contacting the battery owner (e.g., the communication address of the battery owner's terminal).

[0059] In this embodiment, when the dealer 100 sells or leases the vehicle 10, the dealer 100 writes owner information (including the identification information and contact information of the battery owner) regarding the battery 12 of the vehicle 10 to a storage device (not shown) of the server 150 and to the storage device 111b of the vehicle 10. As a result, the owner information according to the sales contract or lease contract is written to each storage device. Specifically, for each of vehicle A (partially leased vehicle) and vehicle B (fully leased vehicle), the identification information of the battery owner indicates that the owner of the battery 12 is the automobile manufacturer, and the contact information of the battery owner indicates the communication address of the management center 500. The management center 500 corresponds to the terminal of the automobile manufacturer (the owner of the battery 12). For vehicle C (vehicle for sale), the identification information of the battery owner indicates that the owner of the battery 12 is the vehicle user, and the contact information of the battery owner indicates the communication address of the mobile terminal 20.

[0060] SOC indicates the remaining amount of electricity stored, and corresponds to the ratio of the current amount of electricity stored to the amount of electricity stored in a fully charged state. SOH indicates the state of health or the degree of deterioration. Examples of SOH include capacity retention rate and internal resistance. The higher the internal resistance of the electricity storage device, the greater the degree of deterioration of the electricity storage device. The lower the capacity retention rate of the electricity storage device, the greater the degree of deterioration of the electricity storage device. The capacity retention rate of the electricity storage device corresponds to the ratio of the current capacity of the electricity storage device to the capacity of the electricity storage device in its initial state (undegraded state). The capacity of the electricity storage device corresponds to the amount of electricity stored in a fully charged state.

[0061] 1 again, the power storage device management system according to this embodiment includes a plurality of dealers 100, a plurality of BSta 200, and a plurality of vehicles 10. The management system further includes a plurality of mobile terminals 20 carried by users of the respective vehicles 10. A management center 500 is configured to be able to communicate with each of the servers 150 of the dealers 100 installed at each base and the servers 250 of the battery exchange stations (BSta 200) installed at each base. The management center 500 is also configured to be able to communicate with each vehicle 10 sold or leased by any of the dealers 100 and the mobile terminals 20 corresponding to each vehicle 10.

[0062] The management center 500 has pre-registered identification information (vehicle ID) of each vehicle 10 sold or leased by the dealer 100 at each base. The storage device 520 of the management center 500 stores information (vehicle information) about each vehicle 10, distinguishing them by vehicle ID. For parameters that vary over time among the vehicle information, the latest values ​​are sequentially transmitted from each vehicle 10 to the management center 500, and the management center 500 records the changes in these parameter values. In order to reduce the frequency of communication, each vehicle 10 may transmit data recorded over a certain period (for example, each parameter value recorded in association with a time) to the management center 500 all at once after that period has elapsed. The management center 500 acquires the above-mentioned battery information from each vehicle 10.

[0063] The vehicle information held by the management center 500 includes the above-mentioned battery information, as well as usage type information and fee information, which will be described below.

[0064] The usage mode information indicates the usage mode of the vehicle 10. In this embodiment, the usage mode information indicates one of the usage modes of vehicle A (partially leased vehicle), vehicle B (fully leased vehicle), and vehicle C (sold vehicle). For example, when selling or leasing the vehicle 10, the dealer 100 writes the usage mode information regarding the vehicle 10 into a storage device (not shown) of the server 150. Then, the server 150 transmits the usage mode information to the management center 500 together with the vehicle ID.

[0065] The fee information corresponds to information about the lease fee that the vehicle user pays to the leasing company (automobile manufacturer). The lease fee corresponds to the fee that the user pays to rent and use the vehicle or battery.

[0066] 3 is a flowchart showing control that is executed by vehicle 10 when an accident occurs in the method for managing an electricity storage device according to this embodiment. In the following, each step in the flowchart will be simply represented by "S".

[0067] For example, when the ECU 111 of the vehicle 10 is started, the started ECU 111 starts a series of processes shown in FIG. 3, which will be described below. The control system of the vehicle 10 (including the ECU 111) is started in response to, for example, the operation of a start switch of the vehicle 10. The start switch is generally called a "power switch" or an "ignition switch." However, the period during which the series of processes shown in FIG. 3 are executed is arbitrary. For example, the ECU 111 may execute these processes only while the vehicle 10 is traveling. Hereinafter, the vehicle 10 executing the series of processes shown in FIG. 3 will be referred to as a "target vehicle."

[0068] 1, 2, and FIG. 3, in S11, ECU 111 of the target vehicle determines whether an accident has occurred for the target vehicle based on whether an accident detection signal has been received from accident detector 118a. In this embodiment, if acceleration of the target vehicle equal to or greater than a predetermined value is detected, ECU 111 determines that an accident has occurred for the target vehicle. In this case (YES in S11), processing proceeds to S12. On the other hand, if acceleration of the target vehicle equal to or greater than a predetermined value is not detected, ECU 111 determines that no accident has occurred for the target vehicle. In this case (NO in S11), processing does not proceed to S12 or later, and the determination in S11 is repeated. However, the accident detection method is not limited to the above and is arbitrary.

[0069] In S12, the ECU 111 (more specifically, the processor 111a) reads owner information (including the identification information and contact information of the battery owner) regarding the battery 12 of the target vehicle from the storage device 111b. Subsequently, in S131, the ECU 111 determines whether the owner of the battery 12 is the user of the target vehicle based on the read battery owner identification information. The ECU 111 identifies the owner of the battery 12 based on the battery owner identification information.

[0070] In this embodiment, if the target vehicle is vehicle C, a YES determination is made in S131. Also, if the target vehicle is vehicle A or vehicle B, a NO determination is made in S131. If the target vehicle is vehicle A or vehicle B, the target vehicle is equipped with a power storage device rented from an automobile manufacturer. In this case, the owner information stored in storage device 111b indicates that the terminal of the owner of the power storage device installed in the target vehicle is management center 500. In this embodiment, a NO determination in S131 means that the owner of battery 12 is the leasing company (automobile manufacturer), that is, that battery 12 installed in the target vehicle is provided through a leasing service.

[0071] If the owner of the battery 12 is the user of the target vehicle (YES in S131), the ECU 111 notifies the vehicle user for post-accident response in S132. For example, the ECU 111 controls the user terminal (e.g., at least one of the HMI 117a and the mobile terminal 20) of the target vehicle so that the user terminal displays a predetermined procedure manual (e.g., an accident response manual). The user terminal may display contact information for an emergency vehicle (e.g., at least one of an ambulance, a fire engine, a tow truck, and a police vehicle) that will handle the accident.

[0072] If the owner of the battery 12 is other than the user of the target vehicle (NO in S131), the ECU 111 determines in S141 whether the body 11 of the target vehicle is damaged based on whether a body damage signal has been received from the body damage detector 118b. In this embodiment, the ECU 111 determines that the body 11 is damaged when a break in the body wiring (wiring connected to the body 11) of the target vehicle is detected. The detection of a break in the body wiring of the target vehicle means that the body 11 is damaged to the extent that the target vehicle cannot continue traveling. In this case (YES in S141), the process proceeds to S151. On the other hand, if a break in the body wiring of the target vehicle is not detected, the ECU 111 determines that the body 11 is not damaged (and therefore the target vehicle can continue traveling). In this case (NO in S141), the process proceeds to S142. However, the method of body damage detection is not limited to the above and is arbitrary.

[0073] In S142, the ECU 111 requests each of the user terminal (e.g., NAVI 117b) of the target vehicle and the management center 500 to replace the battery 12 installed in the target vehicle. Specifically, the ECU 111 identifies the communication address of the management center 500 (terminal of the battery owner) based on the contact information of the battery owner (S12), and transmits a signal (hereinafter referred to as an "exchange request signal") to the management center 500 notifying the target vehicle of an accident and requesting permission to replace the battery 12 at the nearest BSta 200. The exchange request signal according to this embodiment includes identification information of the vehicle in which the accident occurred (vehicle ID of the target vehicle) and location information of the location where the accident occurred. The location of the location where the accident occurred is detected, for example, by a GPS sensor of the NAVI 117b. The ECU 111 may request the dispatch of an emergency vehicle to deal with the accident, if necessary.

[0074] When the ECU 111 requests the NAVI 117b to replace the battery 12, the NAVI 117b searches for a route to the BSta 200 closest to the target vehicle as the destination, and displays a route from the current position of the target vehicle to the destination. Furthermore, the NAVI 117b displays a message urging the user to replace the battery 12.

[0075] In S151, the ECU 111 determines whether the battery 12 is in a controllable state in the target vehicle whose body 11 is damaged. Specifically, the ECU 111 determines whether the battery 12 is in a controllable state in cooperation with the battery ECU 112. The battery ECU 112 may determine whether the battery 12 is in a controllable state based on whether the detection signal from the BMS 112a is normal and whether the response of the battery control component to the control command is normal. The ECU 111 instructs the battery ECU 112 to make the above determination, and if the battery ECU 112 determines that the battery 12 is in a controllable state, the ECU 111 determines YES in S151. As a result, the process proceeds to S152. However, the method of diagnosing the state of the battery 12 is not limited to the above and is arbitrary.

[0076] In S152, an output limit of the battery 12 is set in the battery ECU 112. In this embodiment, the battery ECU 112 in which the output limit of the battery 12 has been set (i.e., the battery ECU 112 in the output limited state) instructs the ECU 111 to reduce the output of the battery 12 when the discharge power of the battery 12 exceeds a predetermined value (hereinafter referred to as "limit value U"). The limit value U is set, for example, to a level at which electric traveling other than evacuation traveling is prohibited. When the ECU 111 is instructed by the battery ECU 112 to reduce the output of the battery 12, the ECU 111 reduces the discharge power of the battery 12. Therefore, when the battery ECU 112 is in the output limited state, the control of the PCU 116a by the ECU 111 (and thus the electric traveling of the target vehicle) is limited. However, the output limit control is not limited to the above-described aspect. For example, the SMR 115a may be maintained in a cut-off state while the output of the battery 12 is being limited.

[0077] If the battery 12 is in a controllable state (YES in S151), the process proceeds to S16 via S152. In this case, the output of the battery 12 is limited by the above-mentioned process (S152). On the other hand, if the battery 12 is not in a controllable state (NO in S151), the process of S152 is not executed and the process proceeds to S16. In this case, the battery 12 is in an uncontrollable state.

[0078] In S16, the ECU 111 requests the management center 500 to collect the battery 12 installed in the target vehicle. Specifically, the ECU 111 identifies the communication address of the management center 500 (the battery owner's terminal) based on the battery owner's contact information (S12), and transmits a signal (hereinafter referred to as a "collection request signal") to the management center 500 notifying the management center 500 of the occurrence of an accident involving the target vehicle and requesting that the battery 12 be collected from the target vehicle. The collection request signal according to this embodiment includes identification information of the vehicle in which the accident occurred (the vehicle ID of the target vehicle) and location information of the location where the accident occurred. The location of the location where the accident occurred is detected, for example, by a GPS sensor of the NAVI 117b. The ECU 111 may request the dispatch of an emergency vehicle to deal with the accident, if necessary.

[0079] As described above, when the ECU 111 according to this embodiment detects that the vehicle body 11 equipped with the battery 12 rented out through the leasing service has been damaged and determines that the battery 12 is in a controllable state, it sets an output limit for the battery 12 in the vehicle 10 and transmits a collection request signal to the management center 500 (S152, S16). With the ECU 111 configured in this way, when the vehicle body 11 is damaged, it becomes possible to request the management center 500 that provides the leasing service to collect the battery 12.

[0080] After transmitting the collection request signal, the ECU 111 determines in S171 whether the battery 12 has been collected by the battery owner from the target vehicle. Specifically, the ECU 111 determines whether a collection completion signal (S25 in FIG. 4) described below has been received. While the ECU 111 has not received the collection completion signal (NO in S171), the determination in S171 is repeated. Then, when the ECU 111 receives the collection completion signal (YES in S171), the ECU 111 releases the output restriction (S152) set on the target vehicle (more specifically, the battery ECU 112) in S172. Note that when the battery 12 is in an uncontrollable state, the process of S172 is unnecessary and may be skipped.

[0081] As described above, the method for managing the power storage device according to this embodiment includes determining whether an accident has occurred with the target vehicle (S11), determining whether the body 11 of the target vehicle has been damaged if it is determined that an accident has occurred with the target vehicle equipped with the rented power storage device (battery 12) (S141), determining whether the body 11 of the target vehicle has been damaged to the extent that the target vehicle cannot continue traveling if it is detected that the body 11 has been damaged to the extent that the target vehicle cannot continue traveling (S151), determining whether the power storage device is in a controllable state if it is determined that the power storage device is in a controllable state, setting an output limit for the power storage device for the target vehicle (S152), and When it is detected that the vehicle body 11 has been damaged, transmitting a recovery request signal to the management center 500 (terminal of the owner of the power storage device) requesting that the power storage device be recovered from the target vehicle (S16); when the power storage device is recovered by the automobile manufacturer (owner of the power storage device) from the target vehicle for which an output limit has been set, releasing the output limit set for the target vehicle (S172); and when it is determined that an accident has occurred with the target vehicle and the vehicle body 11 is not damaged, transmitting an exchange request signal to the management center 500 requesting permission to replace the power storage device installed in the target vehicle (S142).

[0082] In the above method, when the target vehicle cannot continue traveling, the collection request signal is transmitted to the terminal of the owner of the power storage device. This makes it easier for the owner of the power storage device to collect the power storage device from the target vehicle. Furthermore, when the power storage device is in a controllable state, an output limit for the power storage device is set for the target vehicle, which prevents the owner of the power storage device from installing another power storage device on the repaired vehicle body 11 and using the target vehicle fraudulently before collecting the power storage device. On the other hand, after the owner of the power storage device collects the power storage device, the output limit for the power storage device is released, which enables the user of the target vehicle to install another power storage device on the repaired vehicle body 11 and use the target vehicle. Furthermore, when the target vehicle can continue traveling, the target vehicle can continue traveling to a location where the power storage device can be replaced, and the power storage device can be replaced. The owner of the power storage device can collect the power storage device from the target vehicle by permitting replacement of the power storage device at a predetermined location (for example, the nearest BSta 200).

[0083] Execution of any one of the processes of S132, S142, and S172 ends the post-accident control shown in FIG. 3. If the owner of the battery 12 installed in the target vehicle is other than the user of the target vehicle, a replacement request signal (S142) or a collection request signal (S16) is transmitted from the target vehicle to the management center 500. Each of the replacement request signal and the collection request signal corresponds to a notification of the occurrence of an accident. When the management center 500 receives notification of the occurrence of an accident from the target vehicle, it starts a series of processes shown in FIG. 4, which will be described below. On the other hand, if the owner of the battery 12 installed in the target vehicle is the user of the target vehicle, the management center 500 is not notified of the occurrence of the accident. In this case, the series of processes shown in FIG. 4 is not executed.

[0084] FIG. 4 is a flowchart showing control executed by the management center 500 when an accident occurs in the method for managing the power storage device according to this embodiment.

[0085] 1, 2, and 4, in S21, the management center 500 determines whether or not to collect the battery 12 installed in the target vehicle. Specifically, when the management center 500 receives a collection request signal (S16 in FIG. 3) from the target vehicle, it determines to collect the battery 12, and when the management center 500 receives a replacement request signal (S142 in FIG. 3) from the target vehicle, it determines not to collect the battery 12.

[0086] If it is determined that the battery 12 should be collected (YES in S21), the management center 500 determines in S22 whether the target vehicle is a partially leased vehicle. Specifically, the management center 500 acquires usage mode information of the target vehicle based on the identification information (vehicle ID) of the target vehicle included in the collection request signal, and determines whether the target vehicle is vehicle A or vehicle B based on the usage mode information. If the target vehicle is vehicle A (YES in S22), the management center 500 requests the collecting vehicle 910 to collect only the battery 12 (the battery 12 removed from the target vehicle) in S231. If the target vehicle is vehicle B (NO in S22), the management center 500 requests the tow truck 920 to collect the entire target vehicle (i.e., to collect the vehicle body 11 and battery 12 together without removing the battery 12 from the target vehicle) in S232.

[0087] In the next step S24, in response to the request in step S231 or S232, the management center 500 determines whether the recovery vehicle 910 or the tow truck 920 has completed recovery of the battery 12. The determination in step S24 is repeated until recovery of the battery 12 is completed.

[0088] When the recovery vehicle 910 and the tow truck 920 according to this embodiment receive a recovery request from the management center 500 (for example, when they receive a request signal indicating the location of the accident location), they head to the location where the target vehicle is parked (the location where the accident occurred). When the recovery vehicle 910 secures the battery 12 removed from the target vehicle (for example, when the battery 12 is loaded onto the recovery vehicle 910), it notifies the management center 500 that recovery is complete. When the tow truck 920 secures the target vehicle (for example, when the target vehicle is secured by the tow truck 920), it notifies the management center 500 that recovery is complete. Each of the recovery vehicle 910 and the tow truck 920 may transport the recovered battery 12 (the battery 12 alone or the target vehicle) to the BSta 200.

[0089] When the management center 500 receives the notification of the completion of collection, it determines that collection of the battery 12 is complete (YES in S24). As a result, the process proceeds to S25. In S25, the management center 500 transmits a collection completion signal to the target vehicle, indicating that the battery 12 has been collected from the target vehicle by the battery owner (automobile manufacturer). When the process of S25 is executed, the series of processes shown in FIG. 4 ends.

[0090] If it is determined in S21 that the battery 12 is to be collected, the battery 12 is collected from the target vehicle as described above. On the other hand, if it is determined that the battery 12 is not to be collected (NO in S21), the management center 500 permits the BSta 200 nearest to the target vehicle to exchange the battery by the processes of S26 and S27 described below.

[0091] In S26, the management center 500 uses the location information included in the replacement request signal to identify one BSta 200 that is closest to the location of the target vehicle. Subsequently, in S27, the management center 500 requests the server 250 of the BSta 200 identified in S26 to secure a power storage device (replacement battery) that can be replaced with the battery 12 installed in the target vehicle. Specifically, the management center 500 extracts information about the battery 12 of the target vehicle (e.g., battery ID and specifications) from a database stored in the storage device 520 based on the identification information (vehicle ID) of the target vehicle, and executes the above request to the server 250 by transmitting a signal including the extracted battery information (hereinafter also referred to as a "battery request signal") to the server 250. Upon receiving this request, the server 250 checks whether or not there is a shortage of the replacement battery requested by the management center 500, and if there is a shortage of replacement batteries, secures a replacement battery (power storage device for the target vehicle) from a nearby warehouse or another BSta 200.

[0092] As described above, when the management center 500 receives an exchange request signal from the target vehicle, it requests a predetermined exchange station (for example, the BSta 200 nearest to the target vehicle) to secure a power storage device that can be exchanged for the battery 12 (S27). According to this configuration, when it becomes necessary to exchange the battery 12 mounted on the target vehicle, it becomes easier for the BSta 200 to quickly prepare a replacement power storage device (i.e., a power storage device that is compatible with the power storage device mounted on the target vehicle).

[0093] By the processing of S27, the management center 500 permits the BStata 200 that has received the battery request signal to replace the power storage device (battery 12) of the target vehicle. The battery ID included in the battery request signal is registered in the server 250. As a result, a battery replacement is reserved in the server 250. The server 250 identifies the battery to be replaced based on the battery ID included in the battery request signal. Note that if the battery replacement is not performed even after a predetermined period has elapsed since the battery replacement was reserved, the reservation is canceled.

[0094] When the process of S27 is executed, the series of processes shown in Fig. 4 ends. The user of the target vehicle (the vehicle in which the accident occurred) that transmitted the exchange request signal in S142 of Fig. 3 drives the target vehicle according to the guidance by NAVI 117b (see S142 of Fig. 3) and arrives at BSta 200 that is closest to the accident site. Then, at BSta 200, the battery 12 installed in the target vehicle is exchanged. Fig. 5 is a flowchart showing the process related to battery exchange executed by the vehicle 10 and the battery exchange station terminal (server 250).

[0095] 1, 2, and FIG. 5, a series of processes from S110 to S180 are executed by ECU 111 of the target vehicle. A series of processes from S210 to S270 are executed by server 250. Server 250 is configured to be able to wirelessly communicate with the target vehicle and acquires battery information from the target vehicle. Server 250 and the target vehicle may communicate with each other over a short distance using a wireless LAN (Local Area Network), for example, or may communicate via a communication network NW.

[0096] After arriving at BSta 200, the target vehicle transmits a signal (hereinafter also referred to as a "request signal") requesting battery replacement to server 250 in S110. Hereinafter, the battery 12 before replacement provided in the target vehicle will be referred to as "battery B1." The request signal includes identification information (battery ID) of battery B1 installed in the target vehicle. The target vehicle may execute the battery replacement request (S110) in response to an instruction from a user.

[0097] Upon receiving the request signal, the server 250 determines in S210 whether or not predetermined replacement requirements are met for the target vehicle. Specifically, the server 250 determines whether or not the replacement requirements are met based on whether or not the battery ID received from the target vehicle matches the battery ID (S27 in FIG. 4) included in the battery request signal acquired from the management center 500. In other words, if the battery ID of the target vehicle is registered (reserved), the replacement requirements are met, and if the battery ID of the target vehicle is not registered (reserved), the replacement requirements are not met.

[0098] If the replacement requirements are met for the target vehicle (YES in S210), server 250 sends a permission notice to the target vehicle in S220, and then the process proceeds to S240. On the other hand, if the replacement requirements are not met for the target vehicle (NO in S210), server 250 sends a denial notice to the target vehicle in S230, and then the series of processes from S210 to S270 ends. In this case, battery replacement is not performed.

[0099] After transmitting the request signal (S110), the target vehicle waits for a reply from server 250. Then, upon receiving the reply from server 250, the target vehicle determines in S120 whether or not the battery replacement is permitted. If the target vehicle receives the above-mentioned notification of permission (YES in S120), the process proceeds to S130. On the other hand, if the target vehicle receives the above-mentioned notification of denial (NO in S120), the series of processes from S110 to S180 ends. In this case, the battery replacement is not performed.

[0100] In S130 and S240, the battery replacement is performed according to the procedure described below (see FIG. 6). The target vehicle and server 250 exchange information for the battery replacement. Server 250 may acquire information (e.g., specifications) about the battery installed in the target vehicle from the target vehicle.

[0101] Hereinafter, the battery 12 attached to the target vehicle by the battery replacement will be referred to as "battery B2." When the battery replacement is complete, the target vehicle inspects battery B2 in S140. Then, the target vehicle transmits the inspection results to server 250 in S150. Then, the target vehicle determines whether the battery replacement was successful or not based on the inspection results in S160. If the inspection does not reveal any abnormalities (e.g., poor connection or abnormal electrical performance), the target vehicle determines that the battery replacement was successful; if the inspection reveals any abnormalities, the target vehicle determines that the battery replacement was not successful. Similarly, upon receiving the inspection results, server 250 also determines whether the battery replacement was successful or not based on the inspection results (no abnormality / abnormality) in S250.

[0102] If the battery replacement is successful (YES in S160 and YES in S250), the target vehicle and server 250 each update their own battery information in S170 and S260, and then the series of processes shown in FIG. 5 ends. On the other hand, if the battery replacement is unsuccessful (NO in S160 and NO in S250), the target vehicle and server 250 each execute predetermined abnormality processing in S180 and S270. The abnormality processing may include processing to notify the user of the target vehicle that the battery replacement has failed. The abnormality processing may also include processing to notify the management center 500 that the battery replacement has failed. The abnormality processing may also include processing to temporarily remove battery B2 installed in the target vehicle from the target vehicle and then perform the battery replacement again. After the abnormality processing is executed, the series of processes shown in FIG. 5 ends. Note that the abnormality processing can be set arbitrarily.

[0103] FIG. 6 is a diagram for explaining the configuration and operation of the battery exchange station (BSta200) according to this embodiment.

[0104] 1 and 2 as well as FIG. 6, the BSta 200 includes a storage device 210, an inspection unit 220, and a server 250. The storage device 210 includes a storage unit (e.g., a storage facility). The inspection unit 220 includes, for example, a charger / discharger, a measuring device, and a sorting device. The BSta 200 also includes a transport device for transporting the power storage devices, and an exchange device for exchanging the power storage devices. The transport method may be a conveyor system or a system using a transport robot. The transport device and the exchange device are each controlled by the server 250.

[0105] The server 250 includes a processor 251, a storage device 252, and a communication module 253. The storage device 252 stores information about each battery present in the BSta 200, distinguishing it by battery identification information (battery ID). The battery information held by the server 250 includes, for example, specifications (e.g., initial capacity, charging performance, and discharging performance), status (e.g., pre-inspection / inspected (reuse / other use / disposal) / ready for supply), SOH, and SOC. The server 250 sequentially transmits the information it holds to the management center 500. The batteries present in the BSta 200 are the property of the automobile manufacturer. New batteries may be supplied to the BSta 200 from the automobile manufacturer's warehouse, or used batteries collected from vehicles 10 may be stored in the BSta 200. Batteries may also be transported between multiple BSta 200.

[0106] After parking the target vehicle in a predetermined position within BSta 200, the target vehicle requests server 250 to replace the battery (S110 in FIG. 5). In response to this request, server 250 starts control for battery replacement (S240 in FIG. 5). Server 250 replaces the battery of the target vehicle, for example, in the following procedure.

[0107] The server 250 selects a battery (replacement battery) corresponding to battery B1 from among the multiple batteries B3 housed in the storage unit of the storage device 210. The selected battery B3 has the same specifications (e.g., initial capacity, charging performance, and discharging performance) as battery B1. However, the degree of deterioration of battery B3 is less than that of battery B1. In addition, the SOC of battery B3 is equal to or greater than a predetermined SOC value (e.g., 50%).

[0108] Next, the replacement device removes battery B1 from the target vehicle. Hereinafter, the battery removed from the target vehicle will be referred to as "battery B4." Next, the transport device transports (supplies) battery B3 from storage device 210 to the replacement device. Next, the replacement device installs the supplied battery B3 in the target vehicle. This completes the battery replacement of the target vehicle.

[0109] In parallel with the battery replacement process, BSta 200 also executes a reuse process for battery B4 that has been removed from the target vehicle. When battery B4 is removed from the target vehicle, server 250 starts control for battery reuse. The reuse process is executed, for example, in the following procedure.

[0110] The transport device transports (collects) battery B4 to inspection unit 220. Subsequently, inspection unit 220 inspects the collected battery B4. The inspection is performed by a charger / discharger and a measuring device of inspection unit 220. Before the inspection, SOH recovery processing may be performed on battery B4.

[0111] In the above test, the charger / discharger discharges battery B4 until it reaches a predetermined first SOC value (e.g., an SOC value indicating a fully charged state) or less, and then charges battery B4 until it reaches a predetermined second SOC value (e.g., an SOC value indicating a fully charged state) or more. The measurement device includes various sensors and measures the state (e.g., temperature, current, and voltage) of battery B4 during charging and / or discharging. The measurement device then detects the SOH of battery B4 from the measured data. The measurement device may further include a camera for visual inspection. The charger / discharger may repeatedly charge and discharge battery B4 until the measurement device acquires the necessary test data.

[0112] Once the above inspection is complete, the sorting device of the inspection unit 220 sorts the battery B4 based on the inspection results into one of the following: reuse as a vehicle battery, use for other purposes (use other than for vehicles), or disposal. Examples of other uses include stationary use. The method of battery disposal is arbitrary. During the disposal process, the battery may be disassembled down to the material level, and recyclable materials (resources) may be recovered and reused (resource recycling). Note that the sorting device may classify batteries B4 with significant external damage as non-reusable (for other uses or disposal).

[0113] The inspected (reused) battery B4 is treated as the above-mentioned battery B3. After the above inspection, a transport device transports the battery B3 to the storage device 210. The transported battery B3 is loaded into the storage device 210. As a result, the inspected and charged battery B3 is set in the storage device 210. However, without being limited to this, the storage device 210 may be configured to charge the inspected battery B3.

[0114] FIG. 6 shows an example in which battery removal and battery installation are performed at different locations. The target vehicle may be transported from the removal position to the installation position by a transport device (e.g., a conveyor-type transport device) not shown. However, this is not limited to this, and battery removal and battery installation may also be performed at the same location. Battery replacement (removal and installation) may be performed while the target vehicle is stationary (e.g., parked). Furthermore, it is not necessary for the battery before replacement and the battery after replacement to have the same specifications. The on-board battery may be replaced with a battery of different specifications. For example, the capacity of the on-board battery may be increased by battery replacement.

[0115] As described above, the method for managing a power storage device according to this embodiment includes the processes shown in FIGS. 3 to 5. In this embodiment, ECU 111 corresponds to an example of a "computer device" according to the present disclosure. Each process is performed by one or more processors executing a program stored in one or more memories. However, these processes may also be performed by dedicated hardware (electronic circuits) rather than software.

[0116] Vehicle 10 according to this embodiment includes vehicle body 11, battery 12 (power storage device) mounted on vehicle body 11, a detector (body damage detector 118b) that detects damage to vehicle body 11, ECU 111 (first control device) that executes the above-described management method (for example, the processes shown in FIG. 3 ) for battery 12, and battery ECU 112 (second control device) that controls battery 12. When it is determined that vehicle body 11 is damaged, battery ECU 112 determines whether battery 12 is in a controllable state (S151 in FIG. 3 ). When it is determined that battery 12 is in a controllable state, ECU 111 sets an output limit for battery 12 in battery ECU 112 (S152 in FIG. 3 ). Vehicle 10 having this configuration makes it easier for the owner of a rented power storage device to retrieve the power storage device from vehicle 10 when vehicle body 11 of vehicle 10 equipped with the rented power storage device is damaged.

[0117] The series of processes shown in Fig. 4 may be executed by the server 150 (dealer terminal) instead of the management center 500. The process flows shown in Figs. 3 to 5 may be modified as appropriate. For example, the order of the processes may be changed or unnecessary steps may be omitted depending on the purpose. Furthermore, the content of any of the processes may be changed.

[0118] In this embodiment, the management center 500, the insurance server 600, the server 150, and the server 250 are all on-premise servers. However, this is not limiting, and the functions of each server may be implemented on the cloud by cloud computing. That is, these servers may be cloud servers. The location where the leasing service is provided is not limited to the dealer 100. For example, the management center 500 may provide the leasing service online (e.g., on the cloud). Also, only one type of leasing method (e.g., partial leasing method) may be used.

[0119] In the above embodiment, only the battery is replaced, but the battery pack including the battery and its accessories (e.g., the battery ECU, BMS, temperature control system, and SMR) may be replaced together. The battery ECU may keep the SMR disconnected while the output is limited. The battery ECU may connect the SMR when the output limit is released.

[0120] The vehicle may be an xEV (electric vehicle) other than a BEV. The vehicle may be equipped with an internal combustion engine (for example, a gasoline engine, a biofuel engine, or a hydrogen engine). The vehicle is not limited to a four-wheeled passenger car, but may be a bus or a truck, or an xEV (electric vehicle) with three or five or more wheels. The vehicle may be equipped with solar panels. The vehicle may be configured to be capable of wireless charging. The vehicle may be configured to be capable of autonomous driving or may have a flight function. The vehicle may be an unmanned vehicle (for example, a robotaxi, an automated guided vehicle, or agricultural machinery).

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

[0122] 10 vehicle, 11 vehicle body, 12 battery, 20 mobile terminal, 100 dealer, 111 ECU, 111a processor, 111b storage device, 112 battery ECU, 112a BMS, 112b temperature control system, 117a HMI, 117b NAVI, 118a accident detector, 118b body damage detector, 150 server, 200 battery exchange station, 250 server, 500 management center, 600 insurance server.

Claims

1. In a vehicle comprising a vehicle body, a computer device, a rented power storage device, and a disconnection detection circuit or strain gauge provided in at least one location on the front, side, and rear of the vehicle body, when the disconnection detection circuit or the strain gauge outputs a body damage signal to the computer device indicating that the vehicle body has been damaged to the extent that the vehicle cannot continue to run, the computer device determines whether the power storage device is in a controllable state, and transmits a recovery request signal to a terminal of the owner of the power storage device, requesting that the power storage device be recovered from the vehicle; When it is determined that the power storage device is in a controllable state, the computer device sets an output limit of the power storage device for the vehicle; A method for managing an electricity storage device, comprising:

2. when the power storage device is collected by an owner of the power storage device from the vehicle for which the output limit has been set, the computer device cancels the output limit set on the vehicle; The method for managing a power storage device according to claim 1 , further comprising:

3. The computer device determines whether an accident has occurred in the vehicle using an acceleration sensor or a drive recorder mounted on the vehicle; When it is determined that an accident has occurred in the vehicle and the computer device has not received the body damage signal, the computer device transmits an exchange request signal to the terminal of an owner of the power storage device, requesting permission to exchange the power storage device mounted on the vehicle; and The method for managing a power storage device according to claim 1 , further comprising:

4. In a vehicle comprising a vehicle body, a computer device, a rented power storage device, and a body damage detector provided in at least one location on the front, side, and rear of the vehicle body, when the body damage detector outputs a body damage signal to the computer device indicating that the vehicle body has been damaged to the extent that the vehicle cannot continue to run, the computer device determines whether the power storage device is in a controllable state and transmits a recovery request signal to a terminal of the owner of the power storage device, requesting that the power storage device be recovered from the vehicle; When it is determined that the power storage device is in a controllable state, the computer device sets an output limit of the power storage device for the vehicle; A method for managing an electricity storage device, comprising:

5. A computer device including a processor and a storage device that stores a program that causes the processor to execute a method for managing a power storage device, The method for managing the power storage device includes: In a vehicle including a vehicle body, the computer device, a rented power storage device, and a disconnection detection circuit or a strain gauge provided in at least one of a front portion, a side portion, and a rear portion of the vehicle body, when the disconnection detection circuit or the strain gauge outputs a body damage signal to the computer device indicating that the vehicle body has been damaged to the extent that the vehicle cannot continue traveling, the processor determines whether the power storage device is in a controllable state and transmits a recovery request signal to a terminal of an owner of the power storage device, requesting that the power storage device be recovered from the vehicle; When it is determined that the power storage device is in a controllable state, the processor sets an output limit of the power storage device for the vehicle; 2. A computer device comprising:

6. The vehicle is equipped with the computer device according to claim 5; a server that provides a leasing service for leasing the power storage device to the vehicle; A management system for a power storage device, comprising: the storage device of the computer device stores owner information indicating that the terminal of the owner of the power storage device mounted on the vehicle is the server, the computer device is configured to, when it receives the body damage signal from the open circuit detection circuit or the strain gauge and determines that the power storage device is in a controllable state, set an output limit for the power storage device in the vehicle and transmit the recovery request signal to the server.

7. The management system further includes a plurality of exchange stations that exchange electric storage devices for vehicles; the computer device is configured to transmit to the server an exchange request signal requesting permission to exchange the power storage device mounted on the vehicle; The power storage device management system according to claim 6 , wherein, when the server receives the exchange request signal, the server requests the exchange station to secure a power storage device that can be exchanged for the power storage device.

8. A vehicle body, The rented electricity storage device; a wire break detection circuit or a strain gauge provided in at least one of the front, side, and rear portions of the vehicle body; a first control device; a second control device that controls the power storage device; A vehicle comprising: The first control device determining whether the vehicle body has been damaged to the extent that the vehicle cannot continue traveling based on an output from the disconnection detection circuit or the strain gauge; when it is determined that the vehicle body has been damaged to the extent that the vehicle cannot continue traveling, a recovery request signal is transmitted to a terminal of an owner of the power storage device, requesting that the power storage device be recovered from the vehicle; the second control device is configured to determine whether the power storage device is in a controllable state when the first control device determines that the vehicle body is damaged to the extent that the vehicle cannot continue traveling, The vehicle, wherein the first control device is configured to set an output limit of the power storage device in the second control device when the second control device determines that the power storage device is in a controllable state.

Images