Methods for managing energy storage devices, and vehicles

Abstract

To provide a management method of a power storage device, which, when an accident occurs to a vehicle, accurately informs an owner of a power storage device included in the vehicle about the occurrence of the accident.SOLUTION: A management method of a power storage device includes steps of: determining whether an accident occurs to a vehicle including a vehicle body and a power storage device mounted on the vehicle body; determining whether an owner of the power storage device is an owner of the vehicle body when it is determined that the accident has occurred to the vehicle (S123); and informing a terminal of the owner of the power storage device about the occurrence of the accident of the vehicle including the power storage device when it is determined that the owner of the power storage device is a person other than the owner of the vehicle body (S125, S126).SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present disclosure relates to a method for managing a power storage device and a vehicle.

Background Art

[0002] In Japanese Unexamined Patent Application Publication No. 2022-064527 (Patent Document 1), when an impact sensor that detects the magnitude of an impact applied to a vehicle detects an impact of a predetermined value or more, an electronic control unit using an auxiliary battery as a driving power source controls only a battery cell preselected by a battery module to reduce its voltage. A technique is disclosed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In recent years, the electrification of vehicles has been promoted in various countries around the world, and technologies in four fields called "CASE" (connected, automated, shared, electrified) have attracted particular attention. A vehicle lease service (including a vehicle sharing service) that lends a vehicle to a user is also one of them. However, in Patent Document 1 mentioned above, sufficient consideration has not been given to the occurrence of an accident in a leased vehicle or an accident in a vehicle equipped with a leased power storage device. Specifically, according to the technique described in Patent Document 1, a vehicle user can know the occurrence of an accident, but it is difficult for the owner of the power storage device to know the occurrence of an accident when the power storage device has been leased.

[0005] The present disclosure has been made to solve the above problems, and an object thereof is to accurately notify the owner of a power storage device provided in a vehicle of the occurrence of a vehicle accident when the accident occurs. [Means for solving the problem]

[0006] In accordance with the form relating to the first aspect of this disclosure, the following method for managing an energy storage device is provided. (Paragraph 1) The method for managing the energy storage device includes determining whether an accident has occurred with respect to the vehicle equipped with the vehicle body and the energy storage device mounted on the vehicle body; determining whether the owner of the energy storage device is the owner of the vehicle body if it is determined that an accident has occurred with respect to the vehicle; and, if it is determined that the owner of the energy storage device is someone other than the owner of the vehicle body, sending a notification to the terminal of the owner of the energy storage device informing them of the accident that has occurred with respect to the vehicle equipped with the energy storage device.

[0007] In the management method described above, when an accident occurs involving a vehicle, it is determined whether the owner of the vehicle's energy storage device is the same as the vehicle's owner. If it is determined that the owner of the energy storage device is not the vehicle's owner, a notification is sent to the owner's terminal informing them of the accident involving the vehicle equipped with that energy storage device. When a vehicle accident occurs, the vehicle's user can become aware of the accident. Furthermore, this method makes it possible to notify the owner of the energy storage device of the accident if they are not the vehicle's owner.

[0008] The terminal of the owner of the above-mentioned energy storage device may be a stationary computer (e.g., a server) or a terminal carried by the owner of the energy storage device (e.g., a smartphone).

[0009] The method described in paragraph 1 above may have the configuration described in paragraph 2 or 3 below. (Paragraph 2) The method described in Paragraph 1 further has the following characteristics: The method for managing the energy storage device further includes notifying the terminal of the insurance company providing the insurance for the vehicle of the occurrence of an accident involving the vehicle when it is determined that the owner of the energy storage device is not the owner of the vehicle.

[0010] According to the method described above, it becomes possible to notify the insurance company that provides the vehicle's insurance of the occurrence of the accident.

[0011] (Paragraph 3) The method described in paragraph 1 or 2 further has the following characteristics: The method of managing the energy storage device further includes, when it is determined that the owner of the energy storage device is the owner of the vehicle, informing the vehicle user of information for which insurance services can be applied for damage to the vehicle caused by an accident.

[0012] According to the method described above, if an accident occurs involving a vehicle covered by insurance, the vehicle user will be notified of information regarding how to receive insurance coverage. This makes it easier for the vehicle user to receive insurance coverage.

[0013] Furthermore, the method described in any one of paragraphs 1 to 3 above may have the configuration described in paragraph 4 or 5 below.

[0014] (Article 4) The method described in any one of paragraphs 1 to 3 includes determining whether the owner of the energy storage device is the owner of the vehicle, based on the owner information of the vehicle body and the owner information of the energy storage device stored in the vehicle.

[0015] (Paragraph 5) The method described in any one of paragraphs 1 to 3 includes determining whether the owner of the energy storage device is the owner of the vehicle, based on lease information of the energy storage device stored in the vehicle.

[0016] Furthermore, the method described in paragraph 1 above may have the configuration described in any one of paragraphs 6 to 10 below.

[0017] (Paragraph 6) The method described in any one of paragraphs 1 to 5 further includes making a notification to the terminal of the owner of the energy storage device using the owner's contact information stored in the vehicle.

[0018] According to the above configuration, by using the contact information of the owner of the power storage device stored in the vehicle, the notification to the terminal of the owner of the power storage device described above can be suitably executed.

[0019] (Item 7) In the method according to any one of Items 1 to 6, the terminal of the owner of the power storage device is a server that provides a service of lending the power storage device to the owner of the vehicle body.

[0020] According to the above configuration, when an accident occurs to a vehicle equipped with a power storage device leased by a lease service, it becomes possible to give the above-mentioned notification to the server that provides the lease service.

[0021] (Item 8) The method according to any one of Items 1 to 7 includes, when it is determined that an accident has occurred to a vehicle, obtaining the degree of damage of the power storage device, and using the obtained degree of damage to determine whether to replace the power storage device mounted on the vehicle, and when the owner of the power storage device is other than the owner of the vehicle body and it is determined that the power storage device is to be replaced, sending a notification to the terminal of the owner of the power storage device to inform that the power storage device is to be replaced together with the occurrence of the vehicle accident.

[0022] According to the above configuration, the terminal of the owner of the power storage device is notified whether the power storage device is to be replaced. Thereby, the owner of the power storage device can recognize whether the power storage device is to be removed from the vehicle.

[0023] (Item 9) The method according to Item 8 further includes, when the terminal of the owner of the power storage device receives a notification informing that the power storage device is to be replaced, requesting an exchange station that exchanges the power storage device for the vehicle to secure a power storage device that can be exchanged with the power storage device.

[0024] According to the above system, when the replacement of the power storage device mounted on the vehicle becomes necessary, it becomes easier for the exchange station to prepare a replacement power storage device early.

[0025] Instead of the configuration of the ninth item above, the configuration of the tenth item shown below may be adopted. (Item 10) The method according to Item 8 further includes: a terminal of the owner of the power storage device that has received a notification informing of replacement of the power storage device determines whether the power storage device equipped in the vehicle is covered by an insurance service; and when it is determined that the power storage device equipped in the vehicle is covered by an insurance service, the terminal of the owner of the power storage device requests a replacement station that replaces the power storage device for the vehicle to secure a power storage device that can be exchanged with the power storage device equipped in the vehicle.

[0026] According to the form according to the second aspect of the present disclosure, a vehicle shown below is provided. (Item 11) The vehicle executes the method for managing the power storage device according to any one of Items 1 to 3. The vehicle includes a vehicle body, a power storage device mounted on the vehicle body, a storage device that stores owner information indicating the owner of the vehicle body and the owner of the power storage device, an impact force sensor that detects an impact force applied to the vehicle body, and a processor that executes a management method for the power storage device. The processor is configured to determine whether an accident has occurred for the vehicle based on the detection result by the impact force sensor. When it is determined that an accident has occurred for the vehicle, the processor is configured to determine whether the owner of the power storage device is the owner of the vehicle body based on the owner information read from the storage device.

[0027] According to the vehicle described above, the method for managing the power storage device described above is preferably executed. The vehicle equipped with the power storage device may be an electric vehicle (xEV) that uses electric power as all or part of the power source. Examples of xEVs include BEV (battery electric vehicle), HEV (hybrid vehicle), PHEV (plug-in hybrid vehicle), FCEV (fuel cell vehicle), and the like.

Effects of the Invention

[0028] According to the present disclosure, when a vehicle accident occurs, it becomes possible to accurately notify the owner of the power storage device equipped in the vehicle of the occurrence of the accident.

Brief Description of the Drawings

[0029] [Figure 1] This figure illustrates an overview of the management system for an energy storage device according to an embodiment of the present disclosure. [Figure 2] Figure 1 is a diagram illustrating the configuration of the vehicle shown. [Figure 3] This flowchart shows the control in the event of an accident in the management method of an energy storage device according to an embodiment of the present disclosure. [Figure 4] Figure 3 shows a flowchart illustrating the post-accident control processes performed by the vehicle involved in the accident. [Figure 5] This flowchart shows the battery replacement process performed by the vehicle and the exchange station terminal in the energy storage device management method according to an embodiment of the present disclosure. [Figure 6] This figure illustrates the configuration and operation of a switching station included in the management system according to an embodiment of the present disclosure. [Figure 7] This flowchart shows the reuse process performed by the exchange station in the management method according to the embodiment of the present disclosure. [Figure 8] This flowchart shows the processing related to the provision of insurance services performed by the insurance server in the management method according to the embodiment of this disclosure. [Figure 9] Figure 3 shows a flowchart illustrating a modified version of the process shown. [Figure 10] This figure shows a modified version of the system shown in Figure 1. [Modes for carrying out the invention]

[0030] Embodiments of this disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated.

[0031] Figure 1 is a diagram illustrating the overview of the energy storage device management system according to this embodiment. The management system shown in Figure 1 includes a dealer 100, a battery exchange station (hereinafter referred to as "BSta") 200, a management center 500, an insurance server 600, and insurance servers 700A, 700B, 700C, ...

[0032] The management center 500 is a server that provides a leasing service for energy storage devices for vehicles (e.g., 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 the leasing company. The insurance server 600 is a server that provides insurance services (hereinafter also referred to as "battery insurance") for damage to energy storage devices for vehicles (e.g., for xEVs). Battery insurance is a service that provides compensation for damage to energy storage devices installed in vehicles. The insurance server 600 manages information related to the insurance service. The insurance server 600 belongs to, for example, an insurance company. The automobile manufacturer may also act as the insurance company. The insurance server 600 may belong to an automobile manufacturer or to an insurance company that is not an automobile manufacturer. The insurance server 600 works in conjunction with the management center 500 to provide insurance services for damage to energy storage devices leased through the above-mentioned leasing service. Management Center 500 and Insurance Server 600 correspond to examples of the "First Server" and "Second Server" as described in this disclosure, respectively.

[0033] Furthermore, each of the insurance servers 700A, 700B, 700C, ... is a server that provides insurance services for damage to the vehicle body (hereinafter also referred to as "vehicle body insurance") or insurance services for damage to the entire vehicle (including the vehicle body and energy storage device) (hereinafter also referred to as "automobile insurance"). Both vehicle body insurance and automobile insurance are services that provide compensation for damage to the vehicle within the scope of coverage (vehicle body or the entire vehicle). Each of the insurance servers 700A, 700B, 700C, ... belongs to an insurance company that is not an automobile manufacturer, for example. Hereafter, unless otherwise distinguished, each of the insurance servers 700A, 700B, 700C, ... will be referred to as "insurance server 700". Each insurance server 700 manages information related to insurance services.

[0034] The above-mentioned lease service employs multiple lease methods, including partial leases and full leases. A partial lease is a lease method in which only the vehicle's energy storage device is leased. Users who lease an energy storage device under a partial lease method are responsible for providing the rest of the vehicle (the vehicle body) excluding the energy storage device. Users can install the energy storage device leased from the leasing company into the vehicle body they own. The xEV becomes drivable once the energy storage device is installed in the vehicle body. When the partial lease contract ends, the user returns only the energy storage device to the leasing company. On the other hand, a full lease is a lease method in which the entire vehicle (i.e., both the vehicle body and the energy storage device) is leased. When the full lease contract ends, the user returns not only the energy storage device but the entire vehicle to the leasing company.

[0035] Dealer 100 includes server 150. Automobile manufacturers sell or lease vehicles through dealer 100. However, automobile manufacturers may lease energy storage devices without going through dealer 100. Dealer 100 not only sells vehicles manufactured by automobile manufacturers but also provides the aforementioned leasing services. Server 150 manages information (vehicle information) about vehicles sold or leased by dealer 100, distinguishing them by vehicle ID. Server 150 then transmits the latest vehicle information to management center 500 in response to requests from management center 500 or whenever vehicle information is updated. Dealer 100 may, for example, lease the energy storage device 12A of vehicle 10A shown in Figure 1 to a user using a partial lease method. In this case, vehicle 10A corresponds to a partially leased vehicle (hereinafter sometimes referred to as "vehicle A"), and the vehicle body 11A of vehicle 10A becomes the property of the user. The energy storage device 12A of vehicle 10A is provided to the user through a lease and becomes the property of the automobile manufacturer. Alternatively, dealer 100 may lease vehicle 10B, as shown in Figure 1, to the user through a full lease arrangement. In this case, vehicle 10B corresponds to a fully leased vehicle (hereinafter sometimes referred to as "vehicle B"). The entirety of vehicle 10B (body 11B and energy storage device 12B) is provided to the user through a lease and becomes the property of the automobile manufacturer. Alternatively, dealer 100 may sell vehicle 10C, as shown in Figure 1, to the user. In this case, vehicle 10C corresponds to a vehicle for sale (hereinafter sometimes referred to as "vehicle C"). The entirety of vehicle 10C (body 11C and energy storage device 12C) is sold to the user and becomes the property of the user.

[0036] In this embodiment, the insurance premium is included in the lease fee (e.g., monthly lease fee) that Dealer 100 charges the vehicle user. Vehicles leased by Dealer 100 are covered by battery insurance provided by Insurance Server 600. That is, for each of vehicles A and B, insurance applies when the battery storage device installed in that vehicle is damaged. The insurance service provides compensation for damage to the battery storage device.

[0037] BSta200 is configured to replace energy storage devices for vehicles (e.g., xEVs). BSta200 includes a server 250. In this embodiment, a battery (more specifically, a secondary battery) is used as the energy storage device. However, the energy storage device can be any device capable of storing electricity; examples of energy storage devices include secondary batteries and large-capacity capacitors.

[0038] The energy storage device management system according to this embodiment includes a plurality of BSt200s. These BSt200s are installed at each location within the jurisdiction so as to establish a network of battery exchange locations that cover the entire area under the management system's jurisdiction. Each BSt200 may also function as a vehicle repair shop. Each BSt200 may be configured to perform vehicle body repairs. Furthermore, although Figure 1 shows only one dealer 100, the management system may include a plurality of dealers 100. These dealers 100s may be installed at each location within the jurisdiction so as to establish a network of sales / leasing locations that cover the entire area under the management system's jurisdiction. The dealers 100 and the BSt200s may be installed in the same location (or nearby).

[0039] The management center 500 comprises a processor 510, a storage device 520, and a communication module 530. The insurance server 600 comprises a processor 610, a storage device 620, and a communication module 630. Each of the processors 510 and 610 includes, for example, a CPU (Central Processing Unit). Each of the storage devices 520 and 620 is configured to store stored information. Each of the storage devices 520 and 620 may include an HD (hard disk) drive or an SSD (solid state drive). Each of the communication modules 530 and 630 is connected to a communication network NW, for example, by a wired connection. Figure 1 does not show the configuration of the insurance server 700, but the insurance server 700 has a hardware configuration similar to that of the insurance server 600.

[0040] Servers 150 and 250 are also connected to a communication network NW, for example, by wired connections. The management center 500, insurance servers 600 and 700, servers 150 and 250 are configured to communicate with each other via the communication network NW. The communication network NW is a wide-area network constructed, for example, by the internet and wireless base stations. The communication network NW may also include a mobile phone network.

[0041] In the following, the vehicle provided by Dealer 100 may be referred to as "Vehicle 10". Vehicle 10 in this embodiment is one of Vehicles A, B, or C shown in Figure 1. Figure 2 is a diagram illustrating the configuration of Vehicle 10.

[0042] Referring to Figure 2, the vehicle 10 comprises a vehicle body 11 and a battery 12 mounted on the vehicle body 11. The vehicle 10 is configured to run using the power of the battery 12. The vehicle 10 is, for example, a BEV without an internal combustion engine. As the battery 12, a known vehicle energy storage device (e.g., a liquid-type secondary battery or an all-solid-state secondary battery) can be used. Examples of vehicle secondary batteries include lithium-ion batteries and nickel-metal hydride batteries. Multiple secondary batteries may form a battery pack. The battery 12 corresponds to an example of a "energy storage device" according to this disclosure.

[0043] The vehicle body 11 includes an ECU 111, a battery ECU 112, a BMS (Battery Management System) 112a, a strain sensor 112b, a temperature control system 112c, 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, a drive recorder 117c, a position sensor 118a, an impact force sensor 118b, and a communication device 119. ECU stands for Electronic Control Unit. Power is supplied to the control systems, including each ECU mounted on the vehicle body 11, from an auxiliary battery (not shown).

[0044] The ECU 111 is a computer comprising a processor 111a and a storage device 111b. The storage device 111b stores programs executed by the processor 111a, as well as information used by those programs (e.g., maps, formulas, and various parameters). The storage device 111b also holds various information about 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 Figure 2, the battery ECU 112 is also a computer with a hardware configuration similar to that of the ECU 111. The ECU 111 and the battery ECU 112 are configured to communicate with each other. These ECUs are connected, for example, by a CAN (Controller Area Network).

[0045] The Battery Management System (BMS) 112a includes sensors for detecting the state of the battery 12 (e.g., temperature, current, voltage). The strain sensor 112b detects the degree of strain in the battery case of the battery 12. The greater the impact force applied to the battery 12, the greater the degree of strain in the battery case. The strain sensor 112b may also be a strain gauge or a displacement sensor. The detection results from the BMS 112a and the strain sensor 112b are output to the battery ECU 112.

[0046] The temperature control system 112c regulates the temperature of the battery 12. The temperature control system 112c may include at least one of a heater and a cooling device. The cooling method may be water-cooled. The temperature control system 112c is controlled by the battery ECU 112.

[0047] Vehicle 10 is configured to perform external charging (charging of the battery 12 with power from outside the vehicle). The inlet 113 is configured to allow the plug of an EVSE (Electric Vehicle Supply Equipment) (e.g., a connector for a charging cable) 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 the charging line on and off. In the example shown in Figure 2, the charging line including the inlet 113, charger 114, and charging relay 115b is connected between the SMR 115a and the PCU 116a. However, it is not limited to this, and the charging line may be connected between the battery 12 and the SMR 115a. Also, the configuration shown in Figure 2 may be modified to perform external power supply (power supply from the battery 12 to the outside of the vehicle). For example, the charger 114 shown in Figure 2 may be changed to a charger / discharger.

[0048] The SMR115a switches the connection / disconnection of the electrical circuit from the battery 12 to the PCU116a. When the vehicle 10 is running, the SMR115a is connected and the charging relay 115b is disconnected. When power is exchanged between the battery 12 and the inlet 113, both the SMR115a and the charging relay 115b are connected. The charger 114, SMR115a, and charging relay 115b are each controlled by the battery ECU 112. The battery ECU 112 receives control commands from the ECU 111.

[0049] The PCU116a drives the MG116b using power supplied from the battery 12. The PCU116a includes, for example, an inverter and a DC / DC converter. The PCU116a is controlled by the ECU111. The MG116b functions as the drive motor for the vehicle 10. The MG116b is driven by the PCU116a and rotates the drive wheels of the vehicle 10. The MG116b also performs regenerative power generation and outputs the generated power to the battery 12. The number of drive motors equipped in the vehicle 10 is arbitrary.

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

[0051] NAVI117b includes a touch panel display, a GPS (Global Positioning System) sensor, a processor, and a storage device for storing map information. The map information shows the location of each dealer 100 and each BSt 200. The map information may be updated sequentially by OTA (Over The Air). NAVI117b detects the location of vehicle 10 using the GPS sensor and displays the location of vehicle 10 in real time on a map based on the map information. NAVI117b refers to the map information and performs route searching to find the optimal route (e.g., the shortest route) from the vehicle 10's current location to its destination.

[0052] The drive recorder 117c includes a camera that acquires images of the area around the vehicle 10, a storage device that stores the images acquired by the camera, and an acceleration sensor (G sensor) that detects the acceleration of the vehicle 10. The drive recorder 117c continuously records images of the area around the vehicle 10. However, if the amount of video information recorded in the storage device exceeds the capacity of the storage device, the latest video is overwritten and the older video is erased. For this reason, among the images acquired by the drive recorder 117c, images that should be stored long-term (for example, accident data described later) are stored in the ECU 111 (storage device 111b).

[0053] The position sensor 118a detects the position of the vehicle 10. The impact force sensor 118b detects the impact force applied to the vehicle body 11 (e.g., the body shell). The impact force sensor 118b may be configured to detect the impact force using at least one of an acceleration sensor, a strain gauge, and a displacement sensor.

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

[0055] 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. The smartphone has a built-in computer and a speaker function. However, it is not limited to this, and any device that can be carried by the user of the vehicle 10 can be used as the mobile terminal 20. For example, a laptop, tablet, portable game console, wearable device (smartwatch, smart glasses, smart gloves, etc.), and electronic key can also be used as the mobile terminal 20.

[0056] The mobile terminal 20 has application software (hereinafter referred to as "mobile app") installed for using the services provided by the management center 500. The mobile app links the identification information (terminal ID) of the mobile terminal 20 with the identification information (vehicle ID) of the corresponding vehicle 10 and registers it with 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 also be configured to communicate with each of the insurance servers 600, 700, server 250, and server 150 (Figure 1).

[0057] In vehicle 10, the ECU 111 performs integrated control of the entire vehicle. The ECU 111 acquires detection results from various sensors mounted on vehicle 10 (including position sensor 118a and impact force sensor 118b). The ECU 111 also acquires information from the battery ECU 112, HMI 117a, NAVI 117b, drive recorder 117c, and communication device 119. The battery ECU 112 acquires the state of the battery 12 (e.g., temperature, current, voltage, SOC, and SOH) based on the output of the BMS 112a and outputs the obtained state of the battery 12 to the ECU 111. The vehicle information acquired by the ECU 111 is stored in the storage device 111b. In response to a request from the management center 500, or whenever the vehicle information is updated, vehicle 10 transmits the latest vehicle information along with its vehicle ID to the management center 500. The vehicle ID may be a VIN (Vehicle Identification Number).

[0058] The vehicle information held by vehicle 10 (storage device 111b) includes the battery information described below.

[0059] The battery information for vehicle 10 corresponds to information about the battery 12 as it is installed in 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).

[0060] The owner information in the battery information (battery owner information) indicates the battery owner (i.e., the owner of battery 12). More specifically, the battery owner information includes the battery owner's identification information and contact information. The battery owner's identification information includes information to identify the owner of battery 12 (e.g., name, company name, identification number, identification code, etc.). The battery owner's contact information includes information to contact the battery owner (e.g., the communication address of the battery owner's device).

[0061] In this embodiment, when a dealer 100 employee sells or leases vehicle 10, they write owner information (vehicle body owner information) for the vehicle body 11, owner information (battery owner information) for the vehicle battery 12, and insurance information regarding the vehicle insurance or automobile insurance that vehicle 10 has taken out to the storage device (not shown) of the server 150 and the storage device 111b of vehicle 10, respectively. The server 150 also transmits the above owner information and insurance information to the management center 500, and the management center 500 stores the above owner information and insurance information in the storage device 520. As a result, owner information and insurance information corresponding to the sales contract or lease contract are written to each storage device.

[0062] When a lease agreement is concluded between a leasing company (automobile manufacturer) and a user of vehicle 10 (vehicle user), lease information indicating the contents of the lease agreement may be further stored in the storage device 111b of vehicle 10 and the storage device 520 of the management center 500. The lease information indicates whether vehicle 10 corresponds to vehicle A or vehicle B. In this configuration, the absence of lease information in each storage device means that vehicle 10 is vehicle C.

[0063] Vehicle owner information includes identification information of the vehicle owner. Battery owner information includes identification information and contact information of the battery owner. Specifically, in vehicle A (partially leased vehicle), the identification information in the vehicle owner information and battery owner information indicates that the owner of the vehicle body 11 is the vehicle user, and the owner of the battery 12 is the automobile manufacturer. In vehicle B (fully leased vehicle), the identification information in the vehicle owner information and battery owner information indicates that the owners of the vehicle body 11 and battery 12 are the leasing company (automobile manufacturer). In both vehicles A and B, the contact information in the battery owner information indicates the communication address of the management center 500 as the contact information of the battery owner. The management center 500 corresponds to the terminal of the automobile manufacturer (owner of battery 12).

[0064] On the other hand, in vehicle C (sale vehicle), the identification information of the vehicle owner information and the battery owner information respectively indicates that the owners of the vehicle body 11 and the battery 12 are vehicle users. The contact information of the battery owner information indicates the communication address of the mobile terminal 20 as the contact information of the battery owner. The mobile terminal 20 corresponds to the terminal of the user of vehicle 10 (owner of battery 12).

[0065] Insurance information is information regarding the body insurance or auto insurance that vehicle 10 has taken out. Insurance information includes, for example, identification information and contact information of the insurer providing the body insurance or auto insurance that vehicle 10 has taken out. The insurer's identification information indicates, for example, the name of the insurer. The insurer's contact information indicates, for example, the communication address of the insurer's terminal (any of the insurance servers 700A, 700B, 700C, ...). Insurance information may further include information indicating at least one of the insurance coverage period and insurance coverage conditions with respect to the body insurance or auto insurance that vehicle 10 has taken out. With respect to vehicle A (partially leased vehicle), the vehicle user may enter into a body insurance contract with the insurer. With respect to vehicle B (fully leased vehicle), the leasing company may enter into a body insurance contract with the insurer. With respect to vehicle C (sale vehicle), the vehicle user may enter into an auto insurance contract with the insurer.

[0066] SOC (State of Charge) indicates the remaining charge and is equivalent to the ratio of the current charge to the charge when fully charged. SOH (State of Health) indicates the health or degree of degradation. Examples of SOH include capacity retention rate and internal resistance. A higher internal resistance of a storage device means that the storage device is more degraded. A lower capacity retention rate of a storage device means that the storage device is more degraded. The capacity retention rate of a storage device is equivalent to the ratio of the current capacity of the storage device to the capacity of the storage device in its initial state (undegraded state). The capacity of a storage device is equivalent to the amount of charge when fully charged.

[0067] Furthermore, when an accident occurs with vehicle 10, accident data showing the condition of vehicle 10 at that time is stored in the storage device 111b. The accident data may also include video footage showing the condition of vehicle 10 at the time the accident occurred. Such video footage is acquired, for example, by a drive recorder 117c and stored in the storage device 111b when an accident occurs with vehicle 10.

[0068] Referring again to Figure 1, the energy storage device management system according to this embodiment includes a plurality of dealers 100, a plurality of BSt 200s, and a plurality of vehicles 10. Furthermore, the management system includes a plurality of portable terminals 20 carried by the users of each vehicle 10. The management center 500 is configured to communicate with the servers 150 of the dealers 100 installed at each location and the servers 250 of the battery exchange stations (BSta 200) installed at each location. The management center 500 is also configured to communicate with each vehicle 10 sold or leased by any of the dealers 100, and the portable terminals 20 corresponding to each vehicle 10.

[0069] The management center 500 has pre-registered identification information (vehicle ID) for each vehicle 10 sold or leased by the dealer 100 at each location. The storage device 520 of the management center 500 stores information about each vehicle 10 (vehicle information), distinguishing it by its vehicle ID. For parameters in the vehicle information that change over time, the latest values ​​are successively transmitted from each vehicle 10 to the management center 500, and the management center 500 records the changes in these parameter values. To reduce the frequency of communication, each vehicle 10 may transmit data recorded over a certain period (for example, each parameter value recorded in conjunction with the time) to the management center 500 all at once when that period has elapsed. The management center 500 obtains the aforementioned battery information from each vehicle 10.

[0070] The vehicle information held by Management Center 500 includes, in addition to the battery information mentioned above, the usage pattern information and fee information described below.

[0071] The usage information indicates the usage pattern of vehicle 10. In this embodiment, the usage information indicates one of the usage patterns of vehicle A (partially leased vehicle), vehicle B (fully leased vehicle), or vehicle C (vehicle for sale). For example, when a dealer 100 sells or leases vehicle 10, it writes the usage information for vehicle 10 to the storage device (not shown) of the server 150. The server 150 then transmits the usage information along with the vehicle ID to the management center 500.

[0072] The fee information corresponds to information regarding lease fees paid by the vehicle user to the leasing company (automobile manufacturer). Lease fees correspond to the fees paid by the user for renting and using the vehicle or battery. In this embodiment, the lease fee includes the insurance premium for battery insurance. That is, the vehicle user who pays the lease fee has the right to receive the aforementioned battery insurance.

[0073] Figure 3 is a flowchart showing the control process in the event of an accident in the energy storage device management method according to this embodiment. Hereafter, each step in the flowchart will be simply referred to as "S".

[0074] For example, when the ECU 111 of vehicle 10 is started, the started ECU 111 begins the process S11 described below. The ECU 111 is started, for example, in response to the operation of the start switch of vehicle 10. Generally, the start switch is called a "power switch" or "ignition switch". However, the period during which processes S11 and S12 are executed is arbitrary. For example, the ECU 111 may execute these processes only while vehicle 10 is running. In the process shown in Figure 3, vehicle 10 that executes processes S11 and S12 is referred to as the "target vehicle".

[0075] Referring to Figure 3 in conjunction with Figures 1 and 2, in S11, the ECU 111 of the target vehicle determines whether or not an accident has occurred with respect to the target vehicle. For example, if the impact force detected by the impact force sensor 118b exceeds a predetermined threshold (hereinafter referred to as "Th1"), the ECU 111 determines that an accident has occurred with respect to the target vehicle. In this case, accident data showing the condition of the target vehicle before and after the accident (for example, video from the drive recorder 117c) is stored in the storage device 111b. On the other hand, if the impact force detected by the impact force sensor 118b is less than or equal to Th1, the ECU 111 determines that no accident has occurred with respect to the target vehicle. If it is determined that no accident has occurred (NO in S11), the process does not proceed to S12 or later, and the determination in S11 is repeated. Note that the acceleration sensor of the drive recorder 117c may be used for impact force detection instead of the impact force sensor 118b.

[0076] If an accident is determined to have occurred (YES in S11), the vehicle's ECU111 executes post-accident control in S12. Figure 4 is a flowchart detailing S12.

[0077] Referring to Figures 1 and 2, as well as Figure 4, in S121, the ECU 111 determines the degree of damage to the battery 12 installed in the target vehicle. In this embodiment, the ECU 111 determines the degree of damage to the battery 12 based on at least one of the following: the degree of physical damage to the battery 12 case (e.g., the degree of distortion of the battery case detected by the strain sensor 112b), the communication level of the system monitoring the battery 12 (e.g., communication instability, communication interruption, etc.), the degree of damage to the electrical components of the battery 12 (e.g., disconnection, busbar deformation, etc.), and the degree of damage to the environmental system of the battery 12 (e.g., control malfunction, failure, etc.). In this embodiment, the battery ECU 112 and the BMS 112a each function as a system monitoring the battery 12. The temperature control system 112c functions as the environmental system for the battery 12. The ECU 111 may score the degree of damage for each evaluation item related to the degree of damage to the battery 12, and the sum of the scores for each evaluation item may be treated as the degree of damage to the battery 12 (evaluation result). The evaluation items may be the four items mentioned above (case, communication level, electrical components, and environmental system).

[0078] The method for determining the degree of damage to battery 12 is not limited to the method described above, and any method can be used. For example, the ECU 111 may calculate the degree of damage to battery 12 due to the accident based on the changes in the characteristics of battery 12 before and after the accident (for example, the degree of decrease in capacity retention rate or the degree of increase in internal resistance).

[0079] Next, in S122, the ECU 111 (more specifically, the processor 111a) reads vehicle owner information and battery owner information related to the target vehicle, as well as insurance information related to the vehicle insurance or automobile insurance that the target vehicle has subscribed to, from the storage device 111b. Subsequently, in S123, the ECU 111 determines whether the owner of the battery 12 matches the owner of the vehicle body 11 based on the read vehicle owner information and battery owner information. In this embodiment, the owner of the vehicle body 11 corresponds to the user of the target vehicle. The ECU 111 identifies the owner of the vehicle body 11 based on the identification information of the vehicle owner, and identifies the owner of the battery 12 based on the identification information of the battery owner. In this way, the ECU 111 determines whether the owner of the battery 12 is the owner of the vehicle body 11 based on the owner information of the vehicle body 11 and the owner information of the battery 12 stored in the vehicle 10 (for example, the storage device 111b). However, the ECU 111 may determine whether the owner of the battery 12 is the owner of the vehicle body 11 based on the lease information of the battery 12 stored in the vehicle 10 (for example, the memory device 111b).

[0080] In this embodiment, if the target vehicle is vehicle C, the determination in S123 is YES, and if the target vehicle is vehicle A, the determination in S123 is NO. In this embodiment, the determination of NO in S123 means that the owner of the battery 12 is a leasing company (automobile manufacturer), that is, the battery 12 installed in the target vehicle is provided through a leasing service.

[0081] If the owner of battery 12 is not the owner of vehicle body 11 (NO in S123), ECU 111 determines in S124 whether or not to replace battery 12 installed in the vehicle using the degree of damage to battery 12 (S121). ECU 111 may also determine whether or not it is necessary to replace battery 12 based on the degree of damage. In this embodiment, ECU 111 determines to replace battery 12 if the degree of damage to battery 12 exceeds a predetermined threshold (hereinafter referred to as "Th2"). If the degree of damage to battery 12 is Th2 or less, ECU 111 determines not to replace battery 12.

[0082] If it is determined that the battery 12 should be replaced (YES in S124), the ECU 111, in S125, identifies the communication address of the management center 500 (the battery owner's terminal) based on the battery owner's contact information (S122), and notifies the management center 500 that the battery 12 should be replaced as soon as an accident occurs in the vehicle in question. Specifically, the ECU 111 sends a first accident notification signal to the management center 500 that includes the identification information of the vehicle involved in the accident (the vehicle ID of the vehicle in question), the location information of the accident site, a battery replacement flag (=1) indicating "replacement required," and the degree of damage to the battery 12 (S121).

[0083] On the other hand, if it is determined that the battery 12 will not be replaced (NO in S124), the ECU 111, in S126, identifies the communication address of the management center 500 (the battery owner's terminal) based on the battery owner's contact information (S122), and notifies the management center 500 that the battery 12 will not be replaced along with the occurrence of an accident involving the vehicle in question. Specifically, the ECU 111 sends a second accident notification signal to the management center 500 that includes the identification information of the vehicle involved in the accident (the vehicle ID of the vehicle in question), the location information of the accident site, a battery replacement flag indicating "no replacement" (=0), and the degree of damage to the battery 12 (S121).

[0084] When either process S125 or S126 above is executed, in the subsequent S127, the ECU 111 identifies the communication address of the insurance provider's terminal that provides the insurance (more specifically, body insurance or automobile insurance) to which the target vehicle is subscribed, based on the insurance information of the target vehicle (S122), and sends a notification to the insurance provider's terminal (any of the insurance servers 700A, 700B, 700C, ...) informing them of the accident involving the target vehicle. The ECU 111 may also send a signal to the insurance provider's terminal that includes identification information of the vehicle involved in the accident (the vehicle ID of the target vehicle), location information of the accident site, and information regarding the damage to the target vehicle (for example, the magnitude of the impact force applied to the vehicle body 11). Upon receiving notification of the accident from the target vehicle, the insurance server 700 may perform processing to provide insurance services (for example, notifying the insurance provider's representative).

[0085] The location information of the accident site mentioned above corresponds to the current location information of the target vehicle detected by, for example, the location sensor 118a. However, the location detection method can be changed as appropriate. The GPS sensor of NAVI 117b may be used for location detection instead of the location sensor 118a. In addition, when the ECU 111 of the target vehicle detects that an accident has occurred (YES in S11 of Figure 3), it may, if necessary, request the dispatch of emergency vehicles to deal with the accident (for example, at least one of an ambulance, fire truck, tow truck, and police vehicle).

[0086] If the owner of battery 12 is also the owner of vehicle body 11 (YES in S123), ECU 111, in S128, informs the user of the vehicle of information regarding the application of insurance services for damage to the vehicle caused by the accident. This makes it easier for the user of the vehicle to apply for insurance services.

[0087] Specifically, the ECU 111 identifies the communication address of the user terminal (e.g., mobile terminal 20) of the vehicle in question based on the battery owner's contact information (S122). The ECU 111 then transmits the location information of the accident site, the magnitude of the impact force applied to the vehicle body 11 (S11 in Figure 3), the degree of damage to the battery 12 (S121), and the insurance information of the vehicle in question (S122) to the mobile terminal 20, and requests the mobile terminal 20 to display information necessary to receive insurance services. In response to the request from the ECU 111 (S128), the mobile terminal 20 displays, for example, the information received from the ECU 111. Specifically, the mobile terminal 20 may display information indicating the location of the accident (e.g., a map of the surrounding area, street address, or landmark), information regarding the insurance policy the vehicle in question has (e.g., at least one of the following: the name of the insurance company, the contact information of the insurance company, the insurance coverage period, and the insurance coverage conditions), and information regarding the damage to the vehicle in question (e.g., at least one of the following: the magnitude of the impact force applied to the vehicle body 11 and the degree of damage to the battery 12).

[0088] The post-accident control shown in Figure 4 (S12 in Figure 3) is terminated when either process S127 or S128 is executed. If the owner of the battery 12 installed in the target vehicle is someone other than the owner of the vehicle body 11, a first accident notification signal (S125) or a second accident notification signal (S126) is transmitted from the target vehicle to the management center 500.

[0089] As described above, the method for managing the energy storage device according to this embodiment includes: determining whether an accident has occurred with respect to a vehicle equipped with the energy storage device (battery 12) (S11 in Figure 3); determining whether the owner of the energy storage device is the owner of the vehicle if an accident has been determined to have occurred with respect to the vehicle (S123 in Figure 4); sending a notification to the terminal of the owner of the energy storage device (management center 500) informing them of the accident with respect to the vehicle equipped with the energy storage device if it has been determined that the owner of the energy storage device is not the owner of the vehicle (S125, S126 in Figure 4); and sending a notification to the terminal of the insurance company that provides the insurance for the vehicle informing them of the accident with respect to the vehicle (S127 in Figure 4). With this method, if the owner of the energy storage device equipped in the vehicle in which the accident occurred is not the owner of the vehicle, it becomes possible to notify the owner of the energy storage device (for example, a leasing company) of the accident. It also becomes possible to notify the insurance company that provides the insurance for the vehicle in which the accident occurred of the accident.

[0090] Upon receiving the first or second accident notification signal described above, the management center 500 initiates the series of processes S21 to S25 described below. On the other hand, if the owner of the battery 12 installed in the vehicle in question matches the owner of the vehicle body 11, no notification is sent to the management center 500. In this case, the series of processes S21 to S25 by the management center 500 are not performed.

[0091] Referring again to Figure 3 along with Figures 1 and 2, in S21, the management center 500 decides whether or not to replace the battery 12 installed in the target vehicle. Specifically, if the management center 500 receives a first accident notification signal (notification of replacement) from the target vehicle, it decides to replace the battery 12, and if it receives a second accident notification signal (notification of no replacement) from the target vehicle, it decides not to replace the battery 12.

[0092] If it is determined that the battery 12 needs to be replaced (YES in S21), the management center 500, in S22, uses the location information included in the first accident notification signal to identify one or more BSt200s located around the vehicle in question. The one or more BSt200s located around the vehicle in question may be the single BSt200 closest to the vehicle in question, or it may be at least one BSt200 located within a predetermined distance from the vehicle in question.

[0093] Next, in S23, the management center 500 requests the server 250 of the BSt 200 identified in S22 to secure a replacement battery (energy storage device) that can be swapped with the battery 12 installed in the target vehicle. Specifically, the management center 500 extracts information about the target vehicle's battery 12 (e.g., battery ID and specifications) from the database stored in the storage device 520 based on the target vehicle's identification information (vehicle ID), and sends a signal containing the extracted battery information (hereinafter also referred to as the "battery request signal") to the server 250, thereby executing the above request to the server 250. Upon receiving this request, the server 250 checks whether there is a shortage of replacement batteries in stock as requested by the management center 500, and if there is a shortage of replacement batteries, it secures a replacement battery (energy storage device for the target vehicle) from a nearby warehouse or another BSt 200.

[0094] As described above, when the management center 500 receives a notification (first accident notification signal) indicating that the battery 12 (energy storage device) installed in the target vehicle needs to be replaced, it requests one or more replacement stations to secure an energy storage device that can be replaced with the battery 12 (S23). With this configuration, when the battery 12 installed in the target vehicle needs to be replaced, BSta 200 can quickly prepare a replacement energy storage device (i.e., an energy storage device compatible with the energy storage device installed in the target vehicle).

[0095] The management center 500, through the processing in S23 above, authorizes the BSta 200, which received the battery request signal, to replace the energy storage device (battery 12) of the target vehicle. The battery ID included in the battery request signal is registered with the server 250. This reserves the battery replacement in the server 250. The server 250 identifies the battery to be replaced based on the battery ID included in the battery request signal. If the battery replacement is not performed after a predetermined period has elapsed since the battery replacement was reserved, the reservation is canceled.

[0096] If it is determined that the battery 12 will not be replaced (NO in S21), the management center 500 determines in S24 whether the battery 12 installed in the vehicle is eligible for insurance service (battery insurance). Specifically, the management center 500 uses the second accident notification signal to determine whether the insurance coverage conditions are met. In this embodiment, if the degree of damage to the battery 12 installed in the vehicle (second accident notification signal) exceeds a predetermined threshold (hereinafter referred to as "Th3"), the insurance coverage conditions are met; otherwise, the insurance coverage conditions are not met. Th3 is a threshold that defines the scope of insurance coverage and may be predetermined in the insurance contract. If the degree of damage to the battery 12 does not exceed Th3, it means that the degree of damage has not reached the level required for insurance coverage. Th3 is smaller than Th2.

[0097] If the insurance coverage conditions are met, it is determined that the battery 12 is eligible for insurance service (battery insurance) (YES in S24), and the process proceeds to S25. In S25, the management center 500 requests the insurance server 600 to determine the insurance amount. Specifically, the management center 500 makes the above request to the insurance server 600 by sending a signal (hereinafter also referred to as the "first request signal") to the insurance server 600 that includes the identification information of the target vehicle (vehicle ID), the owner information of the battery 12 installed in the target vehicle (for example, the communication address of the management center 500), and damage information indicating the degree of damage to the battery 12 installed in the target vehicle. Once the process in S25 is executed, the series of processes from S21 to S25 by the management center 500 are completed.

[0098] If the insurance coverage conditions are not met, it is determined that the battery 12 is not eligible for insurance service (battery insurance) (NO in S24), and the series of processes S21 to S25 by the management center 500 are terminated without the execution of process S25. Similarly, if the process S23 described above is executed, the series of processes are terminated. However, if it is determined that the battery 12 should be replaced (YES in S21), the degree of damage to the battery 12 exceeds Th2 (see S124 in Figure 4), and therefore insurance service (battery insurance) is applied to the damage to the battery 12. In this embodiment, when the battery 12 is replaced, the server 250, not the management center 500, requests the insurance server 600 to determine the insurance amount (see Figure 7 described later).

[0099] After the accident, the vehicle involved in the accident (the vehicle that was involved in the accident) is either driven under its own power or towed to a BSta200 located near the accident site (for example, the BSta200 closest to the accident site). At the BSta200, the battery 12 installed in the vehicle is replaced. Figure 5 is a flowchart showing the battery replacement process performed by the vehicle 10 and the battery replacement station terminal (server 250).

[0100] Referring to Figures 1 and 2, as well as Figure 5, the series of processes S110 to S180 are executed by the ECU 111 of the target vehicle. The series of processes S210 to S270 are executed by the server 250. The server 250 is configured to communicate wirelessly with the target vehicle and obtains battery information from the target vehicle. The server 250 and the target vehicle may communicate via short-range communication, for example, using a wireless LAN (Local Area Network), or they may communicate via a communication network NW.

[0101] After arriving at BSt200, the target vehicle sends a signal requesting battery replacement (hereinafter also referred to as the "replacement request signal") to the server 250 at S110. Hereafter, the battery 12 in the target vehicle before replacement will be referred to as "battery B1". The replacement request signal includes identification information (battery ID) of battery B1 installed in the target vehicle. The target vehicle may perform a battery replacement request (S110) in response to instructions from the user.

[0102] Upon receiving a replacement request signal, the server 250 determines in S210 whether the predetermined replacement requirements are met for the target vehicle. Specifically, the server 250 determines whether the replacement requirements are met based on whether the battery ID received from the target vehicle matches the battery ID included in the battery request signal obtained from the management center 500 (S23 in Figure 3). In other words, if the battery ID of the target vehicle is registered (reserved), the replacement requirements are met; if the battery ID of the target vehicle is not registered (reserved), the replacement requirements are not met.

[0103] If the replacement requirements are met for the target vehicle (YES in S210), the server 250 sends a permission notification 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), the server 250 sends a disapproval notification to the target vehicle in S230, and then the series of processes from S210 to S270 ends. In this case, the battery will not be replaced.

[0104] The target vehicle sends a replacement request signal (S110) and then waits for a reply from the server 250. Upon receiving a reply from the server 250, the target vehicle determines in S120 whether or not battery replacement is permitted. If the target vehicle receives notification of permission (YES in S120), the process proceeds to S130. On the other hand, if the target vehicle receives notification of denial (NO in S120), the series of processes from S110 to S180 ends. In this case, battery replacement is not performed.

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

[0106] In the following, the battery 12 installed in the target vehicle as a result of the above battery replacement will be referred to as "Battery B2". Once the battery replacement is complete, the target vehicle performs an inspection of Battery B2 in S140. Subsequently, in S150, the target vehicle transmits the results of the inspection to the server 250. Subsequently, in S160, the target vehicle determines whether the battery replacement was successful or not based on the inspection results. The target vehicle determines that the battery replacement was successful if no abnormalities (e.g., poor connection or abnormal electrical performance) are found in the inspection, and that the battery replacement was unsuccessful if abnormalities are found in the inspection. Similarly, the server 250, upon receiving the results of the above inspection, also determines in S250 whether the battery replacement was successful or not based on the inspection results (no abnormalities / abnormalities found).

[0107] If the battery replacement is successful (YES in S160 and YES in S250), the target vehicle and server 250 each update their respective battery information in S170 and S260, and then the series of processes shown in Figure 5 ends. On the other hand, if the battery replacement fails (NO in S160 and NO in S250), the target vehicle and server 250 each execute predetermined error handling in S180 and S270. The error handling may include notifying the user of the target vehicle that the battery replacement failed. The error handling may also include notifying the management center 500 that the battery replacement failed. Furthermore, the error handling may include removing battery B2 installed in the target vehicle and attempting the battery replacement again. After the error handling is executed, the series of processes shown in Figure 5 ends. Note that the error handling can be set arbitrarily.

[0108] Figure 6 is a diagram illustrating the configuration and operation of the battery exchange station (BSta200) according to this embodiment.

[0109] Referring to Figures 1 and 2, as well as Figure 6, the BSta200 comprises a storage device 210, an inspection unit 220, and a server 250. The storage device 210 includes a storage unit (e.g., a hangar). The inspection unit 220 includes, for example, a charger / discharger, a measuring device, and a sorting device. The BSta200 also further comprises a transport device for transporting energy storage devices and a replacement device for replacing energy storage devices. The transport method may be a conveyor system or a system utilizing transport robots. Each of the transport device and the replacement device is controlled by the server 250.

[0110] Server 250 comprises a processor 251, a storage device 252, and a communication module 253. The storage device 252 stores information about each battery present in BSt200, distinguishing it by its battery identification information (battery ID). The battery information held by Server 250 includes, for example, specifications (e.g., initial capacity, charge performance, and discharge performance), status (e.g., pre-inspection / inspected (reusable / other use / disposal) / available), SOH, and SOC. Server 250 sequentially transmits the information it holds to the management center 500. The batteries present in BSt200 are owned by the automobile manufacturer. New batteries may be supplied to BSt200 from the automobile manufacturer's warehouse, and used batteries recovered from vehicles 10 may be stored in BSt200. Batteries may also be transported between multiple BSt200s.

[0111] After the target vehicle parks in a designated location within BSta200, it requests a battery replacement from the server 250 (S110 in Figure 5). In response to this request, the server 250 starts the control process for battery replacement (S240 in Figure 5). The server 250 replaces the target vehicle's battery using, for example, the following procedure.

[0112] Server 250 selects a battery (replacement battery) corresponding to battery B1 from among multiple batteries B3 housed in the storage compartment of the storage device 210. The selected battery B3 has the same specifications as battery B1 (e.g., initial capacity, charging performance, and discharging performance). However, the degree of degradation of battery B3 is less than that of battery B1. Also, the state of charge (SOC) of battery B3 is at or above a predetermined SOC value (e.g., 50%).

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

[0114] Figure 6 shows an example where the battery is removed and installed in different locations. The vehicle may be transported from the removal location to the installation location by a transport device (e.g., a conveyor-type transport device) not shown. However, it is not limited to this, and the battery may be removed and installed in the same location. The battery may be replaced (removed and installed) while the vehicle is stationary (e.g., parked).

[0115] In addition, BSt200 performs a reuse process for battery B4 removed from the target vehicle in parallel with the battery replacement process described above. When battery B4 is removed from the target vehicle, server 250 starts control for battery reuse. The reuse process is performed in a procedure such as that shown in Figure 7. Figure 7 is a flowchart of the process related to the control for reuse of the energy storage device performed by server 250. When battery 12 (battery B1) is removed from the target vehicle by the battery replacement control described above (S240 in Figure 5), server 250 starts a series of processes S241 to S245 described below.

[0116] Referring to Figure 7 as well as Figure 6, in S241, the transport device transports (recovers) the battery B4 removed from the target vehicle to the inspection unit 220. Subsequently, in S242, the inspection unit 220 performs an inspection of the recovered battery B4. The inspection is performed by the charger / discharger and measuring device of the inspection unit 220. Before the inspection, the battery B4 may be subjected to a state of health recovery process.

[0117] In the above inspection, the charger / discharger discharges battery B4 until it reaches, for example, a predetermined first SOC value (e.g., an SOC value indicating an empty charge state) or less, and then charges battery B4 until it reaches, for example, a predetermined second SOC value (e.g., an SOC value indicating a fully charged state) or more. The measuring device includes various sensors to measure the state of battery B4 (e.g., temperature, current, and voltage) during charging and / or discharging. The measuring device then detects the SOH of battery B4 from the measured data. The measuring device may further include a camera for visual inspection. The charger / discharger may also repeat charging and discharging of battery B4 until the measuring device obtains the necessary inspection data.

[0118] Once the above inspection is complete, server 250 requests insurance server 600 to determine the insurance payout in S243. Specifically, management center 500 executes the above request to insurance server 600 by sending a signal (hereinafter also referred to as the "second request signal") to insurance server 600 that includes identification information of the target vehicle (vehicle ID), owner information of battery B4 (e.g., management center 500's communication address), and battery inspection information indicating the results of the above inspection (S242). The battery inspection information includes, for example, at least one of the following regarding battery B4: appearance information (e.g., video data or presence or absence of scratches), charging characteristics (e.g., charging start-up characteristics and maximum charging power), discharge characteristics (e.g., discharge start-up characteristics and maximum discharge power), and SOH (e.g., capacity retention rate or internal resistance).

[0119] In the following step S244, the sorting device in the inspection unit 220 sorts the batteries B4 according to the results of the above inspection (S242) into one of the following categories: reuse as vehicle batteries, use for other purposes (non-vehicle uses), or disposal. An example of other uses is stationary use. The sorting device may also classify batteries B4 with significant external damage as unusable (for other purposes or disposal).

[0120] Batteries B4 selected for reuse are treated as batteries B3 as described above. After the above selection (S244), in S245, the transport device transports the batteries B3 to the storage device 210. The transported batteries B3 are filled into the storage device 210. This ensures that inspected and charged batteries B3 are set in the storage device 210. However, this is not limited to this, and the storage device 210 may be configured to charge the inspected batteries B3. Batteries B4 selected for "other uses" are shipped for other uses in S245. Batteries B4 selected for "disposal" are disposed of in S245. The disposal method is optional. During the disposal process, the batteries may be disassembled down to the material level, and recyclable materials (resources) may be recovered and reused (resource recycling). Once the process in S245 is executed, the reuse process for batteries B4 is completed.

[0121] Figure 8 is a flowchart showing the process related to the provision of insurance services executed by the insurance server 600 upon receiving an insurance claim determination request (S25 in Figure 3 or S243 in Figure 7).

[0122] Referring to Figure 8 along with Figures 1 and 2, when the insurance server 600 receives a first request signal (S25 in Figure 3) or a second request signal (S243 in Figure 7), it starts a series of processes from S31 to S38. In S31, the insurance server 600 communicates wirelessly with the target vehicle and obtains accident data from the target vehicle that shows the condition of the vehicle at the time of the accident. The insurance server 600 may also communicate with the target vehicle via the management center 500. The accident data includes, for example, video from the drive recorder 117c showing the condition of the target vehicle before and after the accident. In the subsequent S32, the insurance server 600 determines, based on the accident data, whether or not there is another vehicle involved in the accident. In the case of a single-vehicle accident (self-inflicted accident), it is determined in S32 to be NO (there is no other vehicle involved in the accident), and the process proceeds to S37, which will be described later.

[0123] If the other party's vehicle exists (YES in S32), the insurance server 600 identifies the server of the insurance provider that the other party's vehicle is insured with (the other party's insurance server) in S33 and provides accident data (S31) to the other party's insurance server. If the insurance server 600 cannot identify the other party's insurance server from the accident data, it may request information to identify the other party's insurance server from the user terminal of the vehicle in question (e.g., mobile terminal 20). Prior to providing (transmitting) the accident data, the insurance server 600 may notify the other party's insurance server to explain the circumstances.

[0124] As a result of the process in S33 above, accident data is shared between the insurance server 600 of the vehicle in question and the insurance server of the other party involved in the accident. Subsequently, these insurance servers perform an accident analysis based on the accident data (S34, S41), and based on the results of the accident analysis, the percentage of fault of both parties involved in the accident (the percentage of fault between the user of the vehicle in question and the other party involved in the accident) is determined (S35, S42). A higher percentage of fault indicates a greater degree of fault.

[0125] Next, in S36, the insurance server 600 determines the amount of compensation to be claimed based on the percentage of fault of both parties involved in the accident (S35), and requests the determined amount of compensation from the other party's insurance server. The insurance server 600 may lower the amount of compensation it requests from the other party's insurance server if the vehicle user's degree of fault in relation to the accident (battery degradation) is greater. The other party's insurance server receives the above compensation amount in S43.

[0126] Next, in S37, the insurance server 600 determines the amount of insurance payout to be made by the insurance service based on the degree of damage (first request signal) or battery inspection information (second request signal) related to the battery 12 installed in the vehicle in question (the vehicle involved in the accident). The insurance server 600 may fully compensate for the loss of the battery 12 with the insurance payout. There may be an upper limit on the amount of insurance payout (for example, an upper limit predetermined in the contract). Furthermore, if it is determined from the accident data that the user intentionally damaged the battery 12, the insurance server 600 may decide that the insurance does not apply (no insurance payout).

[0127] In the following S37, the insurance server 600 transmits a signal to the management center 500 indicating the vehicle ID of the vehicle in question and the insurance amount determined in S37. Note that if the vehicle in question is vehicle B (a fully leased vehicle), the loss of the vehicle body may be fully compensated by the insurance, or the leasing company (automobile manufacturer) may claim at least a portion of the loss from the vehicle user.

[0128] As described above, the energy storage device management method according to this embodiment includes the processes shown in Figures 3 to 5, 7, and 8. In this embodiment, the ECU 111 corresponds to an example of a "computer device" according to this disclosure. Each process is executed by one or more processors executing programs stored in one or more memories. However, these processes may be executed by dedicated hardware (electronic circuits) instead of software.

[0129] The vehicle 10 according to this embodiment includes a vehicle body 11, a battery 12 (energy storage device) mounted on the vehicle body 11, a storage device 111b that stores owner information indicating the owner of the battery 12, an impact force sensor 118b that detects the impact force applied to the vehicle body 11, and a processor 111a that executes the above-described management method (including S11, S12 in Figure 3 and the series of processes shown in Figure 4) with respect to the battery 12. The processor 111a determines whether or not an accident has occurred with respect to the vehicle based on the detection result by the impact force sensor 118b (S11 in Figure 3). If the processor 111a determines that an accident has occurred with respect to the vehicle 10, it determines whether or not the owner of the battery 12 is the owner of the vehicle body 11 based on the owner information read from the storage device 111b (S123 in Figure 4). With such a vehicle 10, it becomes possible to accurately determine whether or not the owner of the battery 12 is the owner of the vehicle body 11 when a vehicle accident occurs.

[0130] In the above embodiment, insurance payments for damage to the energy storage device are calculated for both vehicle A (partially leased vehicle) and vehicle B (fully leased vehicle) using a common processing flow (see Figure 8). However, the invention is not limited to this, and insurance payments may be calculated using different processing flows for vehicle A and vehicle B. For example, when the management center 500 receives a first or second accident notification signal, it may transmit information indicating the lease method (partial lease / fully lease) of the target vehicle (e.g., usage information) to the insurance server 600. When the insurance server 600 receives an insurance payment determination request, it may execute the processing flow shown in Figure 8 for vehicle A and execute a different processing flow (not shown) for vehicle B. With respect to vehicle B, the insurance server 600 may provide an insurance service that covers not only damage to the energy storage device but also damage to the vehicle body.

[0131] The processes shown in Figures 3 and 8 (S21-S25, S51-S53) may be executed by Server 150 (dealer terminal) instead of Management Center 500. The processing flows shown in Figures 3-5, 7, and 8 can be modified as appropriate. For example, the order of processing may be changed or unnecessary steps may be omitted depending on the purpose. Also, the content of any of the processes may be changed. For example, in the process shown in Figure 4, S127 may be omitted.

[0132] Figure 9 is a flowchart showing a modified version of the process shown in Figure 3. In the series of processes shown in Figure 9, the management center 500, upon receiving a notification that the battery 12 will be replaced (a replacement notification), determines in S22A, prior to S23, whether or not the battery 12 in the vehicle 10 is covered by insurance. If the battery 12 is covered by insurance, the management center 500 requests the BSta200 (a replacement station that replaces energy storage devices for vehicles) to secure an energy storage device that can be replaced with the battery 12 in the vehicle 10, through the process in S23 (see Figure 3) described above. On the other hand, if the battery 12 in the vehicle 10 is not covered by insurance, the management center 500 executes the process in S22B instead of the process in S23. In S22B, the management center 500 notifies the vehicle user that the battery 12 in the vehicle 10 is not insured. Furthermore, the management center 500 may notify the vehicle user in S22B of potential BSt200 (exchange stations) that have stock of the batteries 12 that the vehicle 10 is equipped with. Upon receiving the notification, the vehicle user can contact any of the BSt200 to inquire about the amount of the battery replacement fee and payment arrangements by operating the user terminal in the vehicle 10 (for example, the mobile terminal 20 or HMI 117a).

[0133] The functions of the management center 500 and the insurance server 600 may be implemented on a single server. Figure 10 shows a modified example of the system shown in Figure 1. Instead of the management center 500 and insurance server 600 shown in Figure 1, the management center 500A shown in Figure 10 may be used. Referring to Figure 10, when the management center 500A receives a first accident notification signal (S125 in Figure 4) or a second accident notification signal (S126 in Figure 4) from the target vehicle, it executes the process described in S21 (see Figure 3). If it is determined that S21 is YES, the management center 500A executes the processes described in S22 and S23 (see Figure 3), and then executes the processes described in S31 to S36 (see Figure 8). On the other hand, if it is determined that S21 is NO, the management center 500A executes the processes described in S31 to S36 (see Figure 8) without performing the processes described in S22 and S23 (see Figure 3). In this modified example, the management center 500A provides insurance services through battery replacement rather than insurance payments, and therefore does not perform the processes S37 and S38 shown in Figure 8.

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

[0135] In the above embodiment, only the battery is replaced, but the battery pack, including the battery and its accessories (e.g., BMS and strain sensor), may be replaced as a whole. The vehicle may be an xEV (electric vehicle) other than a BEV. The vehicle may be equipped with an internal combustion 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 contactless rechargeable. The vehicle may be configured to be autonomous, or may be equipped with flight capabilities. The vehicle may be an unmanned vehicle (e.g., a robotaxi, an automated guided vehicle, or agricultural machinery).

[0136] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims rather than by the description of the embodiments above, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of Symbols]

[0137] 10 Vehicles, 11 Bodywork, 12 Batteries, 20 Mobile Devices, 100 Dealers, 111 ECUs, 111a Processors, 111b Storage Devices, 112a BMS, 112b Strain Sensors, 112c Temperature Control Systems, 117a HMIs, 117b Navigation Systems, 117c Drive Recorders, 118a Position Sensors, 118b Impact Sensors, 150 Servers, 200 Battery Replacement Stations, 250 Servers, 500 Management Centers, 600, 700 Insurance Servers.

Claims

1. A vehicle comprising a vehicle body and an energy storage device mounted on the vehicle body, and the determination of whether or not an accident has occurred with respect to the said vehicle, If it is determined that an accident has occurred with respect to the vehicle, the vehicle will determine whether the owner of the energy storage device is the owner of the vehicle body, determine the degree of damage to the energy storage device, and then, using the obtained degree of damage, further determine whether or not to replace the energy storage device installed in the vehicle. If the owner of the aforementioned power storage device is other than the owner of the vehicle, and it is determined that the aforementioned power storage device should be replaced, the vehicle shall notify the terminal of the owner of the aforementioned power storage device that an accident has occurred involving the vehicle equipped with the power storage device and that the aforementioned power storage device will be replaced. A method for managing energy storage devices, including the management of such devices.

2. The method for managing a power storage device according to claim 1, further comprising the vehicle notifying the terminal of the insurance company providing the insurance for the vehicle of an accident that has occurred, if it is determined that the owner of the power storage device is other than the owner of the vehicle.

3. If it is determined that the owner of the energy storage device is the owner of the vehicle, the vehicle's user shall be informed of information that the vehicle may be covered by insurance services for damage to the vehicle caused by the accident. A method for managing an energy storage device according to claim 1, further comprising:

4. The method for managing a power storage device according to claim 1, wherein the vehicle determines whether the owner of the power storage device is the owner of the vehicle body, based on the owner information of the vehicle body and the owner information of the power storage device stored in the vehicle.

5. The method for managing a power storage device according to claim 1, wherein the vehicle determines whether the owner of the power storage device is the owner of the vehicle body, based on lease information of the power storage device stored in the vehicle.

6. The method for managing a power storage device according to claim 1, further comprising the vehicle making the notification to the terminal of the owner of the power storage device using the contact information of the owner of the power storage device stored in the vehicle.

7. The method for managing a power storage device according to claim 1, wherein the terminal of the owner of the power storage device is a server that provides a service for lending the power storage device to the owner of the vehicle.

8. The method for managing a battery storage device according to claim 1, further comprising: when the terminal of the owner of the battery storage device receives the notification that the battery storage device is to be replaced, requesting the replacement station that performs replacement of vehicle battery storage devices to reserve a battery storage device that can be replaced with the battery storage device.

9. The terminal of the owner of the energy storage device who has received the notification that the energy storage device will be replaced determines whether or not the energy storage device installed in the vehicle is covered by insurance. If it is determined that the energy storage device installed in the vehicle is covered by insurance, the terminal of the owner of the energy storage device requests the replacement station that performs replacements of vehicle energy storage devices to secure an energy storage device that can be replaced with the energy storage device installed in the vehicle, A method for managing an energy storage device according to claim 1, further comprising:

10. A vehicle body and The energy storage device mounted on the vehicle body, A storage device that stores owner information indicating the owner of the vehicle body and the owner of the energy storage device, An impact force sensor that detects the impact force applied to the vehicle body, Processor and A vehicle equipped with, The processor is configured to determine whether or not an accident has occurred with respect to the vehicle based on the detection results from the impact force sensor. The aforementioned processor, If it is determined that an accident has occurred with respect to the vehicle, the owner of the energy storage device is determined based on the owner information read from the storage device, and the degree of damage to the energy storage device is determined. Based on the obtained degree of damage, a further decision is made as to whether or not to replace the energy storage device. If the owner of the aforementioned power storage device is other than the owner of the vehicle, and it is determined that the power storage device should be replaced, a notification shall be sent to the terminal of the owner of the power storage device informing them that the power storage device will be replaced at the same time as the accident involving the vehicle occurs. A vehicle configured to perform the following actions.

Images