Method and system for managing energy storage devices

Abstract

To accurately acquire a deterioration degree of a vehicle's power storage device by an impact when the vehicle receives the impact.SOLUTION: A management method for a power storage device includes: determining whether a vehicle body of a vehicle equipped with a power storage device receives an impact (S12); obtaining deterioration information indicating degree of deterioration of the power storage device on the bases of power storage device information indicating a state of the power storage device before and after the vehicle body receives the impact when it is determined that the vehicle body receives the impact (S13); and sending the deterioration information to a first server (S14).SELECTED DRAWING: Figure 3

Description

Technical Field

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

Background Art

[0002] Japanese Unexamined Patent Application Publication No. 2022-064527 (Patent Document 1) discloses a technique in which when an impact detection sensor that detects the magnitude of an impact applied to a vehicle detects an impact force of a predetermined value or more, an electronic control unit using an auxiliary battery as a drive power source controls only a preselected battery cell of a battery module to a low voltage.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Patent Document 1 does not disclose which part of the vehicle the impact detection sensor detects the impact force on. In paragraph

[0022] of Patent Document 1, it is described that when an impact force of a predetermined value or more is detected by the impact detection sensor, the lead battery becomes unusable. However, when the vehicle body is impacted, the in-vehicle battery does not necessarily become unusable. Even if a large impact force is applied to the vehicle body, the impact force transmitted to the in-vehicle battery may be small.

[0005] The present disclosure has been made to solve the above problems, and an object thereof is to accurately grasp the degree of deterioration of the power storage device of the vehicle due to an impact when the vehicle is impacted.

Means for Solving the Problems

[0006] According to an aspect according to the first aspect of the present disclosure, a method for managing a power storage device as shown below is provided. (Paragraph 1) The method for managing the energy storage device includes determining whether the vehicle body equipped with the energy storage device has been subjected to an impact, and, if it is determined that the vehicle body has been subjected to an impact, obtaining degradation information indicating the degree of degradation of the energy storage device based on energy storage device information indicating the state of the energy storage device before and after the impact, and transmitting the degradation information to the first server.

[0007] In the above management method, when it is determined that the vehicle body has been subjected to an impact, the degree of deterioration of the energy storage device is obtained based on the state of the energy storage device before and after the impact. By comparing the state of the energy storage device before the impact with the state of the energy storage device after the impact, it becomes possible to accurately determine how much the vehicle's energy storage device has deteriorated due to the impact.

[0008] The management method for the energy storage device described in paragraph 1 above may have the configuration described in any one of paragraphs 2 to 12 below.

[0009] (Section 2) In the method described in Section 1, the energy storage device information indicates the resistance value of the energy storage device, and degradation information of the energy storage device is obtained based on the increase in the resistance value.

[0010] (3) If the resistance value of the energy storage device cannot be detected in the method described in paragraph 2, it is determined that the energy storage device is degraded, and degradation information is sent to the first server.

[0011] (Article 4) In the method described in any one of paragraphs 1 to 3, the energy storage device information indicates the capacity of the energy storage device, and energy storage device degradation information is obtained based on the decrease in the energy storage device capacity.

[0012] (Article 5) In the method described in any one of paragraphs 1 to 4, the energy storage device information indicates the amount of deformation of the case of the energy storage device, and degradation information of the energy storage device is obtained based on the amount of deformation of the case.

[0013] (Item 6) In the method described in any one of Items 1 to 5, the energy storage device information indicates the value of an acceleration sensor attached to the energy storage device, and degradation information of the energy storage device is obtained based on the value of the acceleration sensor.

[0014] (Article 7) In the method described in any one of paragraphs 1 to 6, the vehicle stores owner information indicating the owner of the energy storage device and transmits degradation information to the first server based on the owner information.

[0015] (Clause 8) In the method described in any one of paragraphs 1 to 7, the vehicle stores contract information indicating the provider of the automobile insurance, and transmits accident information regarding the occurrence of an accident to a second server different from the first server based on the contract information.

[0016] (Clause 9) In the method described in any one of paragraphs 1 to 8, if the impact on the vehicle body is less than a predetermined value, deterioration information is not transmitted to the first server.

[0017] (Article 10) In the method described in any one of paragraphs 1 to 9, the vehicle shall, in the event of an accident, notify the emergency service center of the accident information and the deterioration information of the energy storage device based on the emergency service center contact information stored in the vehicle.

[0018] (Paragraph 11) The method described in any one of paragraphs 1 to 10 further includes, if the degree of deterioration of the energy storage after the vehicle body has been subjected to an impact exceeds a predetermined standard level, the first server requiring a replacement station that replaces the energy storage for the vehicle to have a replacement energy storage unit available.

[0019] (Article 12) The method described in any one of paragraphs 1 to 11 further includes: the vehicle transmitting situation data indicating the condition of the vehicle when the vehicle body is struck; the first server determining, based on deterioration information, whether the degree of deterioration of the energy storage device after the vehicle body is struck is greater than a predetermined amount than the degree of deterioration of the energy storage device before the vehicle body is struck, based on the situation data, whether the other party's vehicle is present; and, if the other party's vehicle is present, the first server calculating and sending a claim for damages to the server of the insurance company providing the insurance for the other party's vehicle, in proportion to the percentage of fault of both parties involved in the accident.

[0020] In accordance with the form relating to the second aspect of this disclosure, the following vehicles are provided: (Paragraph 13) The vehicle shall perform the energy storage device management method described in any one of paragraphs 1 to 10. The vehicle shall include a vehicle body, an energy storage device mounted on the vehicle body, a first sensor for detecting an impact force applied to the vehicle body, a second sensor for detecting at least one of the impact force applied to the energy storage device and the state of the energy storage device, and a control device for performing the management method described in any one of paragraphs 1 to 10 with respect to the energy storage device. The control device is configured to determine whether the vehicle body has been subjected to an impact based on the detection result of the first sensor while the vehicle is in motion. The control device is configured to record the detection result of the second sensor while the vehicle is in motion. If the control device determines that the vehicle body has been subjected to an impact, it is configured to acquire the degree of deterioration of the energy storage device before the vehicle body was subjected to an impact based on the detection result of the second sensor before the vehicle body was subjected to an impact, and to acquire the degree of deterioration of the energy storage device after the vehicle body was subjected to an impact based on the detection result of the second sensor after the vehicle body was subjected to an impact.

[0021] According to the above vehicle, the aforementioned method for managing the energy storage device can be suitably implemented. The vehicle equipped with the above energy 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.

[0022] According to the aspect of the third aspect of the present disclosure, the following server is provided. (Item 14) The server manages an energy storage device mounted on a vehicle. The server acquires impact force data of the vehicle from the vehicle, determines whether the vehicle has received an impact based on the impact force data of the vehicle acquired from the vehicle, acquires energy storage device information indicating the state of the energy storage device before and after the vehicle receives an impact from the vehicle, and determines the degree of deterioration of the energy storage device before and after the vehicle receives an impact based on the energy storage device information acquired from the vehicle. It is configured to execute.

[0023] According to the above server, the above-described method for managing the energy storage device is preferably executed.

Effect of the Invention

[0024] According to the present disclosure, when a vehicle receives an impact, it becomes possible to accurately grasp the degree to which the energy storage device of the vehicle has deteriorated due to the impact.

Brief Description of the Drawings

[0025] [Figure 1] It is a diagram for explaining the outline of an energy storage device management system according to Embodiment 1 of the present disclosure. [Figure 2] It is a diagram for explaining the configuration of the vehicle shown in FIG. 1. [Figure 3] It is a flowchart showing the processing executed during a period including when the vehicle is running in the energy storage device management method according to Embodiment 1 of the present disclosure. [Figure 4] It is a flowchart showing the processing related to the post-accident control executed by the vehicle in the control shown in FIG. 3. [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 Embodiment 1 of this disclosure. [Figure 6] This figure illustrates the configuration and operation of a switching station included in the management system of an energy storage device according to Embodiment 1 of the present disclosure. [Figure 7] This flowchart shows the process related to the provision of insurance services executed by the insurance server in the energy storage device management method according to Embodiment 1 of this disclosure. [Figure 8] This figure shows a modified version of the system shown in Figure 1. [Figure 9] Figure 3 shows a flowchart illustrating a modified version of the process shown. [Figure 10] This flowchart shows the processes performed in the energy storage device management method according to Embodiment 2 of this disclosure. [Figure 11] This is a flowchart showing the first example of the first process in Figure 10. [Figure 12] This is a flowchart showing a second example of the first process in Figure 10. [Figure 13] This is a flowchart showing the third example of the first process in Figure 10. [Figure 14] This is a flowchart showing the fourth example of the first process in Figure 10. [Figure 15] This is a flowchart showing the first example of the second process in Figure 10. [Figure 16] This is a flowchart showing a second example of the second process in Figure 10. [Figure 17] This is a flowchart showing a third example of the second process in Figure 10. [Modes for carrying out the invention]

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

[0027] [Embodiment 1] Figure 1 is a diagram illustrating the overview of the energy storage device management system according to Embodiment 1. 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, and an insurance server 600.

[0028] 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 related to the deterioration of energy storage devices for vehicles (e.g., for xEVs). This insurance service provides compensation for the deterioration of 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 related to the deterioration of 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.

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

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

[0031] In this embodiment, the insurance premium is included in the lease fee (e.g., monthly lease fee) that the dealer 100 charges the vehicle user. Vehicles leased by the dealer 100 are covered by insurance provided by the insurance server 600 (more specifically, insurance for the degradation of the energy storage device). That is, for each of vehicles A and B, insurance applies when the energy storage device installed in the vehicle degrades, for example, due to an accident. The insurance service provides compensation for the degradation of the energy storage device.

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

[0033] 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).

[0034] 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. Also, each of the servers 150 and 250 is connected to a communication network NW, for example, by a wired connection. The management center 500, the insurance server 600, server 150, and server 250 are configured to communicate with each other via the communication network NW. The communication network NW is, for example, a wide-area network constructed by the Internet and wireless base stations. The communication network NW may include a mobile phone network.

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

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

[0037] 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).

[0038] 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).

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

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

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

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

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

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

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

[0046] The drive recorder 117c includes a camera that acquires images of the area around the vehicle 10 (for example, images of the front and rear), 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 information in the images recorded in the storage device exceeds the capacity of the storage device, the newest images will be overwritten and the older images will be erased. For this reason, images acquired by the drive recorder 117c that should be stored long-term (for example, situational data described later) are stored in the ECU 111 (storage device 111b).

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

[0048] 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 the server 250 (Figure 1) and the mobile terminal 20, respectively. The ECU 111 is configured to communicate with the management center 500 (Figure 1), the server 250, and the mobile terminal 20, respectively, through the communication device 119. The ECU 111 may also communicate with the server 150 and the insurance server 600 (Figure 1), respectively, through the communication device 119.

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

[0050] 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, 250, and 150 (Figure 1).

[0051] 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).

[0052] The vehicle information held by the vehicle 10 (storage device 111b) includes location information, vehicle body information, and battery information as described below.

[0053] The location information of vehicle 10 includes location data detected by the location sensor 118a. Through the process of S11 in Figure 3, which will be described later, the location data of vehicle 10 while it is in motion is sequentially recorded in the storage device 111b, linked to the time. In other words, the location data stored in the storage device 111b shows the change in the position of vehicle 10 while it is in motion.

[0054] The vehicle body information of vehicle 10 indicates information about the vehicle body 11. The vehicle body information includes specifications (e.g., shape and dimensions of the body shell) and vehicle body data indicating the state of the vehicle body 11. The vehicle body data includes the impact force detected by the impact force sensor 118b. Through the processing of S11 in Figure 3, which will be described later, the vehicle body data (e.g., impact force on the vehicle body 11) while vehicle 10 is in motion is sequentially recorded in the storage device 111b, linked to the time. In other words, the vehicle body data stored in the storage device 111b indicates the changes in the state of the vehicle body 11 while vehicle 10 is in motion.

[0055] 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), and battery data indicating the state of battery 12. Furthermore, if the ECU 111 acquires battery degradation information through the process in S13 of Figure 3, which will be described later, the battery degradation information is also stored in the storage device 111b as battery information.

[0056] The owner information in the battery information indicates the battery owner (i.e., the owner of battery 12). More specifically, the 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).

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

[0058] The battery data includes the degree of strain of the battery case detected by the strain sensor 112b, the temperature, current, voltage, SOC (State of Charge), and SOH (State of Health) detected by the BMS 112a, communication data indicating the communication status of the battery ECU 112, and control data indicating the control status of the battery ECU 112. Through the process of S11 in Figure 3, which will be described later, the battery data while the vehicle 10 is running is sequentially recorded in the storage device 111b, linked to the time. In other words, the battery data stored in the storage device 111b shows the changes in the state of the battery 12 while the vehicle 10 is running.

[0059] Note that 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 the energy storage device means that the energy storage device is more degraded. A lower capacity retention rate of the energy storage device means that the energy storage device is more degraded. The capacity retention rate of the energy storage device is equivalent to the ratio of the current capacity of the energy storage device to the capacity of the energy storage device in its initial state (undegraded state). The capacity of the energy storage device is equivalent to the amount of charge when fully charged.

[0060] Furthermore, when the vehicle body 11 is subjected to an impact, situational data indicating the state of the vehicle 10 at that time is stored in the storage device 111b. The situational data may include video footage showing the state of the vehicle 10 when the vehicle body 11 is subjected to an impact. Such video footage is acquired, for example, by a drive recorder 117c and stored in the storage device 111b when the vehicle body 11 is subjected to an impact.

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

[0062] 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 (vehicle information) about each vehicle 10, distinguishing it by its vehicle ID.

[0063] The vehicle information held by the management center 500 includes the usage pattern information and fee information described below. Furthermore, when the management center 500 receives battery degradation information (S143 in Figure 4), which will be described later, from the vehicle 10, it links this information to the vehicle 10's identification information (vehicle ID) and stores it in the storage device 520.

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

[0065] 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, insurance is included in the lease fee. That is, the vehicle user who pays the lease fee has the right to receive the aforementioned insurance service.

[0066] Figure 3 is a flowchart showing the processes executed during the period including the time when the vehicle 10 is running, in the energy storage device management method according to this embodiment. Hereinafter, each step in the flowchart will be simply referred to as "S".

[0067] For example, when the ECU 111 of vehicle 10 is activated, the activated ECU 111 starts the series of processes S11 to S14 described below. The ECU 111 is activated, for example, in response to the operation of the activation switch of vehicle 10. Generally, the activation switch is called a "power switch" or "ignition switch". In the process shown in Figure 3, vehicle 10 that performs the series of processes S11 to S14 is referred to as the "target vehicle".

[0068] Referring to Figure 3 in conjunction with Figures 1 and 2, in S11, the ECU 111 records the aforementioned location data, vehicle body data, and battery data related to the target vehicle in the storage device 111b, linked to the time. The location data includes, for example, the detected value of the location sensor 118a. The vehicle body data includes, for example, the detected value of the impact force sensor 118b. The battery data includes, for example, the detected values ​​of the BMS 112a and strain sensor 112b, as well as the communication data and control data of the battery ECU 112.

[0069] In the following step S12, the ECU 111 determines whether or not the vehicle body 11 of the target vehicle has been subjected to an impact. For example, the ECU 111 determines that the vehicle body 11 has been subjected to an impact if the impact force detected by the impact force sensor 118b exceeds a predetermined threshold (hereinafter referred to as "Th1"). In this case (YES in S12), situational data showing the condition of the target vehicle before and after the impact (for example, video from the drive recorder 117c) is saved in the storage device 111b, and then the process proceeds to S13. 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 the vehicle body 11 has not been subjected to an impact. In this case (NO in S12), the process does not proceed to S12 or later, and the processes of S11 and S12 are 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.

[0070] In this embodiment, unless the vehicle body 11 is subjected to an impact, the processes S11 and S12 are repeated from the time the ECU 111 is activated until the ECU 111 is stopped. However, this is not limited to this, and the period during which the processes S11 and S12 are executed is arbitrary. For example, the ECU 111 may execute these processes only while the vehicle 10 is in motion.

[0071] In this embodiment, when it is determined that the vehicle body 11 has been subjected to an impact, the ECU 111 determines that an accident has occurred with respect to the vehicle. The ECU 111 may store contact information for emergency vehicles to be notified in the event of an accident in the storage device 111b. The ECU 111 may, if necessary, request the dispatch of emergency vehicles to deal with the accident (e.g., at least one of an ambulance, fire truck, tow truck, and police vehicle). Then, in the subsequent S13, the ECU 111 acquires battery degradation information indicating the degree of degradation of the battery 12 before and after the vehicle body 11 is subjected to an impact. Specifically, the battery degradation information indicates the degree of degradation of the battery 12 before the vehicle body 11 is subjected to an impact (e.g., immediately before) (hereinafter referred to as "degradation before the accident") and the degree of degradation of the battery 12 after the vehicle body 11 is subjected to an impact (e.g., immediately after) (hereinafter referred to as "degradation after the accident"). The ECU 111 refers to the data recorded in the memory device 111b in S11 to determine the degree of degradation before the accident based on the battery data before the vehicle body 11 was impacted, and to determine the degree of degradation after the accident based on the battery data after the vehicle body 11 was impacted.

[0072] In this embodiment, the ECU 111 determines the degree of degradation of the battery 12 based on at least one of the following: the internal resistance of the battery 12, the capacity retention rate of the battery 12, the degree of physical degradation of the battery 12 case (e.g., the degree of battery case distortion 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 degradation of the electrical components of the battery 12 (e.g., disconnection, busbar deformation, etc.), and the degree of degradation of 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 of the battery 12. The ECU 111 may score the degree of degradation for each evaluation item related to the degree of degradation of the battery 12 and treat the sum of the scores for each evaluation item as the degree of degradation of the battery 12 (evaluation result). The evaluation items may be the six items mentioned above (internal resistance, capacity retention rate, case, communication level, electrical components, and environmental system), or two to five items selected from the six items mentioned above, or even just one item (for example, internal resistance or capacity retention rate). Furthermore, the method for determining the degree of degradation of the battery 12 is not limited to the method described above, and any method can be used.

[0073] The ECU111 stores the battery degradation information acquired in S13 into the storage device 111b. Subsequently, the ECU111 of the target vehicle performs post-accident control in S14. Figure 4 is a flowchart detailing S14.

[0074] Referring to Figures 1 and 2, as well as Figure 4, in S141, the ECU 111 (more specifically, the processor 111a) reads owner information (including the battery owner's identification information and contact information) for the battery 12 of the target vehicle from the storage device 111b. Subsequently, in S142, the ECU 111 determines whether the owner of the battery 12 is the user of the target vehicle based on the battery owner's identification information that has been read. The ECU 111 identifies the owner of the battery 12 based on the battery owner's identification information.

[0075] In this embodiment, if the target vehicle is vehicle C, the determination in S142 is YES, and if the target vehicle is vehicle A or vehicle B, the determination in S142 is NO. In this embodiment, the determination of NO in S142 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.

[0076] If the owner of battery 12 is not the user of the vehicle in question (NO in S142), ECU 111 identifies the communication address of the management center 500 (the battery owner's terminal) based on the battery owner's contact information (S141) in S143, and notifies the management center 500 of the accident involving the vehicle in question. Specifically, ECU 111 sends an 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, and battery degradation information (S13 in Figure 3). The location information of the accident site corresponds, for example, to the current location information of the vehicle in question detected by 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.

[0077] If the owner of battery 12 is the user of the vehicle in question (YES in S142), ECU 111, in S144, notifies the user of the vehicle in question 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 in question to apply for insurance services.

[0078] 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 (S141). The ECU 111 then transmits the location information of the accident site, the magnitude of the impact force applied to the vehicle body 11 (S12 in Figure 3), and battery degradation information (S13 in Figure 3) to the mobile terminal 20, and requests the mobile terminal 20 to display information for applying insurance services. In response to the request from the ECU 111, the mobile terminal 20 displays, for example, information about the automobile insurance that the user has purchased, along with the information received from the ECU 111.

[0079] In this embodiment, when a user purchases a vehicle 10 from a dealer 100, they enroll the vehicle 10 in POV (Personally Owned Vehicle) insurance. If the insured vehicle 10 is damaged in an accident, the damage to the vehicle 10 is covered by the automobile insurance. The insurance provider and the contents of the insurance contract are determined arbitrarily by the user. When the user enrolls in the insurance (i.e., before an accident occurs), they register information about the insurance (e.g., the insurance provider's contact information, the insurance coverage period, and the insurance coverage conditions) in a mobile terminal 20. In response to a request from the ECU 111 (S144), 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 about the insurance (e.g., at least one of the insurance provider's contact information, the insurance coverage period, and the insurance coverage conditions), and information about the damage to the vehicle (e.g., the magnitude of the impact force applied to the vehicle body 11, and the degree of battery 12 degradation before and after the accident). Furthermore, the vehicle 10 (for example, the storage device 111b) may store contract information indicating the provider of the automobile insurance. Based on the contract information, the vehicle 10 may transmit accident information regarding the occurrence of an accident to the automobile insurance company's server (for example, the insurance server 600).

[0080] The post-accident control shown in Figure 4 (S14 in Figure 3) ends when either process S143 or S144 is executed.

[0081] As described above, the method for managing the energy storage device according to this embodiment includes determining whether the vehicle body 11 of the target vehicle equipped with the energy storage device has been subjected to an impact (S12 in Figure 3), and, if it is determined that the vehicle body 11 has been subjected to an impact, acquiring battery degradation information indicating the degree of degradation of the energy storage device before and after the impact (S13 in Figure 3). The battery degradation information makes it possible to accurately grasp to what extent the energy storage device of the target vehicle has deteriorated due to the impact.

[0082] Furthermore, the storage device 111b of the ECU 111 stores owner information indicating the owner of the energy storage device installed in the target vehicle. The ECU 111 is configured to use the owner information to determine whether the energy storage device installed in the target vehicle is provided through a lease service when it is determined that the vehicle body 11 has been subjected to an impact (S142 in Figure 4), and to transmit an accident notification signal including battery degradation information to the management center 500 if it is determined that the energy storage device is provided through a lease service (S143 in Figure 4). This makes it easier for the owner of the energy storage device (automobile manufacturer) to accurately understand the extent to which the energy storage device has deteriorated due to the impact.

[0083] If the owner of the battery 12 installed in the target vehicle is not the user of the target vehicle, an accident notification signal (S143) is transmitted from the target vehicle to the management center 500. Upon receiving the accident notification signal, the management center 500 stores various information contained in the accident notification signal in the storage device 520, and then starts the series of processes S21 to S25 described below. On the other hand, if the owner of the battery 12 installed in the target vehicle is the user of the target vehicle, 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 executed.

[0084] Referring again to Figure 3 along with Figures 1 and 2, in S21, the management center 500 determines whether the degree of deterioration of the battery 12 after the vehicle body 11 has been impacted exceeds a predetermined standard level. Specifically, the management center 500 uses the battery deterioration information (S13) included in the accident notification signal to determine whether the degree of deterioration after the accident exceeds a predetermined value (hereinafter referred to as "Th2"). In this embodiment, Th2 represents the predetermined standard level.

[0085] If the degree of deterioration after the accident exceeds Th2 (YES in S21), the management center 500, in S22, uses the location information included in the 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.

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

[0087] As described above, the management center 500 requests that one or more replacement stations secure a replacement energy storage device for the battery 12 if the degree of degradation of the battery 12 in the target vehicle after the vehicle body 11 has been subjected to an impact exceeds a predetermined standard level (S23). With this configuration, if the degree of degradation of the energy storage device installed in the target vehicle becomes significant, BSta 200 can more easily prepare a replacement energy storage device (i.e., an energy storage device compatible with the energy storage device installed in the target vehicle) at an early stage.

[0088] Once the processes in S22 and S23 described above are executed, the process proceeds to S24. On the other hand, if the degree of deterioration after the accident does not exceed Th2 (NO in S21), the processes in S22 and S23 are not executed, and the process proceeds to S24. In S24, the management center 500 determines whether or not the battery 12 of the vehicle in question has deteriorated due to the accident.

[0089] Specifically, the management center 500 determines that the battery 12 of the vehicle in question has deteriorated due to the accident (YES in S24) if it determines that the degree of deterioration after the accident has increased by a predetermined amount (hereinafter referred to as "Th3") or more compared to the degree of deterioration before the accident, based on the above battery deterioration information. Otherwise, it determines that the battery 12 of the vehicle in question has not deteriorated due to the accident (NO in S24). The management center 500 may also determine whether the battery 12 of the vehicle in question has deteriorated due to the accident based on whether the value obtained by subtracting the degree of deterioration before the accident from the degree of deterioration after the accident (hereinafter also referred to as "deterioration increase") is Th3 or greater. For example, in a configuration where the only evaluation item for the degree of deterioration of the battery 12 is the capacity retention rate, if the capacity retention rate before the accident is "90%" (deterioration rate is 10%) and the capacity retention rate after the accident is "70%" (deterioration rate is 30%), then the subtraction value of these two, 20% (=30%-10%), may be treated as the deterioration increase.

[0090] In this embodiment, if the deterioration increase is determined to be Th3 or greater (YES in S24), the management center 500 determines that the insurance service is applicable, and the process proceeds to S25. On the other hand, if the deterioration increase is determined to be less than Th3 (NO in S24), the management center 500 determines that the insurance service is not applicable, and the series of processes from S21 to S25 by the management center 500 are terminated.

[0091] In S25, the management center 500 requests the insurance server 600 to determine the insurance payout. Specifically, the management center 500 sends a signal (hereinafter also referred to as the "insurance application 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 the battery degradation information, thereby executing the above request to the insurance server 600. Once the process in S25 is executed, the series of processes from S21 to S25 by the management center 500 are completed.

[0092] As described above, in the energy storage device management system according to this embodiment, the management center 500 determines, based on battery degradation information, that the degree of degradation of the energy storage device after the vehicle body 11 has been subjected to an impact has increased by a predetermined amount or more compared to the degree of degradation of the energy storage device before the vehicle body 11 was subjected to an impact, and requests the insurance server 600 to make a decision on the insurance payment. This makes it easier for vehicle users to receive insurance services.

[0093] The vehicle involved in the accident will either drive under its own power or be towed to a BSt200 located near the accident site (for example, the BSt200 closest to the accident site). At the BSt200, the battery 12 installed in the vehicle will be replaced. Figure 5 is a flowchart showing the battery replacement process performed by the vehicle 10 and the battery replacement station terminal (server 250).

[0094] 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 acquires battery information from the target vehicle as needed. The server 250 and the target vehicle may communicate via short-range communication, for example, using a wireless LAN (Local Area Network), or via a communication network NW.

[0095] After arriving at BSt200, the target vehicle sends a signal requesting battery replacement (hereinafter also referred to as the "replacement request signal") to the BSt200 server 250 in 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) and battery degradation information for battery B1 installed in the target vehicle. The target vehicle may also perform a battery replacement request (S110) in response to instructions from the user.

[0096] Upon receiving the replacement request signal, the server 250 determines in S210 whether the post-accident degradation level indicated by the battery degradation information included in the replacement request signal exceeds Th2 (the same value as S21 in Figure 3). The post-accident degradation level corresponds to the current degradation level of battery B1 installed in the vehicle in question.

[0097] If the degree of deterioration after the accident exceeds Th2 (YES in S210), server 250 sends a permission notification to the vehicle in S220, and then the process proceeds to S240. On the other hand, if the degree of deterioration after the accident does not exceed Th2 (NO in S210), server 250 sends a disapproval notification to the vehicle in S230, and then the series of processes from S210 to S270 ends. In this case, the battery will not be replaced.

[0098] As described above, the BSt200 (replacement station) according to this embodiment is configured to allow the replacement of energy storage devices in vehicles equipped with such devices if their degree of deterioration exceeds Th2 (a predetermined standard level). With such a system, it becomes possible to replace energy storage devices that have deteriorated significantly due to impact using the BSt200. Furthermore, by not allowing the replacement of energy storage devices with a low degree of deterioration, the BSt200 is made more likely to replace energy storage devices at an appropriate frequency.

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

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

[0101] 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).

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

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

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

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

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

[0107] 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%).

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

[0109] 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, for example, in the following steps.

[0110] The transport device transports (recovers) battery B4 to the inspection unit 220. Subsequently, 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.

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

[0112] Once the above inspection is complete, the sorting device in the inspection unit 220 sorts the batteries B4 according to the inspection results 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 method of battery disposal 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). The sorting device may also classify batteries B4 with significant external damage as unusable (for other uses or disposal).

[0113] The inspected (reusable) battery B4 is treated as the aforementioned battery B3. After the inspection, the transport device transports the battery B3 to the storage device 210. The transported battery B3 is filled into the storage device 210. This ensures that the inspected and charged battery B3 is set in the storage device 210. However, this is not limited to this configuration, and the storage device 210 may also be configured to charge the inspected battery B3.

[0114] Figure 6 shows an example where battery removal and battery installation are performed 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 battery removal and battery installation may be performed in the same location. Battery replacement (removal and installation) may be performed while the vehicle is stationary (e.g., parked). Furthermore, it is not necessary for the battery before replacement and the battery after replacement to have the same specifications. The onboard battery may be replaced with a battery of different specifications. For example, the capacity of the onboard battery may be increased by replacing the battery.

[0115] Figure 7 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).

[0116] Referring to Figure 7 along with Figures 1 and 2, when the insurance server 600 receives an insurance application request signal (S25 in Figure 3), it starts a series of processes from S31 to S38. In S31, the insurance server 600 communicates wirelessly with the target vehicle and obtains situation data from the target vehicle that shows the condition of the vehicle when the vehicle body 11 was impacted. The insurance server 600 may also communicate with the target vehicle via the management center 500. The situation data includes, for example, video from the drive recorder 117c showing the condition of the target vehicle before and after the vehicle body 11 was impacted. In the subsequent S32, the insurance server 600 determines, based on the situation 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.

[0117] 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 situation data (S31) to the other party's insurance server. If the insurance server 600 cannot identify the other party's insurance server from the situation 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 situation data, the insurance server 600 may notify the other party's insurance server to explain the circumstances.

[0118] As a result of the process in S33 described above, situation 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 situation 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.

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

[0120] Next, in S37, the insurance server 600 determines the insurance payout to be made by the insurance service based on the battery degradation information included in the insurance application request signal. The insurance server 600 may, for example, increase the amount of insurance payout the greater the increase in degradation. The insurance server 600 may also fully compensate for the loss of 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 the situation data determines that the user intentionally degraded battery 12, the insurance server 600 may decide that insurance does not apply (no insurance payout).

[0121] In the following S38, the insurance server 600 sends 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.

[0122] As described above, the energy storage device management method according to Embodiment 1 includes the processes shown in Figures 3 to 5 and Figure 7. In Embodiment 1, 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.

[0123] The vehicle 10 according to Embodiment 1 includes a vehicle body 11, a battery 12 (energy storage device) mounted on the vehicle body 11, an impact force sensor 118b (first sensor) for detecting impact force applied to the vehicle body 11, a BMS 112a and a strain sensor 112b (second sensor) for detecting the state of the battery 12 and the impact force applied to the battery 12, and an ECU 111 for executing the above-described management method (including the series of processes shown in S11 to S14 in Figure 3 and in Figure 4) with respect to the battery 12. The ECU 111 determines whether the vehicle body 11 has been subjected to an impact based on the detection result from the impact force sensor 118b while the vehicle 10 is running (S12 in Figure 3). The ECU 111 records the detection results from the BMS 112a and the strain sensor 112b while the vehicle 10 is running (S11 in Figure 3). When the ECU 111 determines that the vehicle body 11 has been subjected to an impact, it acquires the degree of battery degradation before the vehicle body 11 was subjected to an impact, based on the detection results from the BMS 112a and strain sensor 112b respectively, and also acquires the degree of battery degradation after the vehicle body 11 was subjected to an impact, based on the detection results from the BMS 112a and strain sensor 112b respectively (S13 in Figure 3). With this configuration, when the vehicle body 11 of the vehicle 10 is subjected to an impact, it becomes possible to accurately determine how much the battery 12 of the vehicle 10 has been degraded as a result of that impact.

[0124] In the above embodiment 1, the insurance payout for the deterioration of the energy storage device is calculated for both vehicle A (partially leased vehicle) and vehicle B (fully leased vehicle) using a common processing flow (see Figure 7). However, the invention is not limited to this, and the insurance payout may be calculated using different processing flows for vehicle A and vehicle B. For example, the management center 500 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 payout determination request, it may execute the processing flow shown in Figure 7 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 the deterioration of the energy storage device but also damage to the vehicle body.

[0125] The processing flows shown in Figures 3-5 and 7 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 S143 of Figure 4, the target vehicle may send an accident notification signal including situation data to the management center 500. Then, in S25 of Figure 3, the management center 500 may send an insurance application request signal including situation data to the insurance server 600. In this configuration, S31 of Figure 7 may be omitted. Also, if it is determined that the vehicle body 11 of the target vehicle has been hit, the target vehicle may send battery degradation information to the insurance server 600. Also, the target vehicle may request the insurance server 600 to determine the insurance payment. In a system where the target vehicle involved in an accident contacts the insurance company, the notification from the management center 500 to the insurance server 600 (S24, S25 in Figure 3) may be omitted.

[0126] The functions of the management center 500 and the insurance server 600 may be implemented on a single server. Figure 8 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 8 may be used. Referring to Figure 8, when the management center 500A receives an accident notification signal (S143 in Figure 4) from the target vehicle, it executes the processes S21 to S24 (see Figure 3) described above. If it is determined to be YES in S24, the management center 500A executes the processes S31 to S36 (see Figure 7) described above without performing the process in S25 (Figure 3). However, since the management center 500A provides insurance services through battery replacement rather than insurance payments, it does not execute the processes S37 and S38 shown in Figure 7.

[0127] In the process shown in Figure 3 above, the vehicle 10 determines whether or not the vehicle body 11 has been hit. However, the system is not limited to this configuration, and the control center 500 may make the determination instead of the vehicle 10. Figure 9 is a flowchart showing a modified version of the process shown in Figure 3.

[0128] Referring to Figure 9 along with Figures 1 and 2, in this modified example, the ECU 111 of the target vehicle performs the processes S141, S142, and S143A instead of the processes S11 to S14 (Figure 3) described above. S141 and S142 are the same as S141 and S142 in Figure 4. If NO is determined in S142, the process proceeds to S143A. In S143A, the ECU 111 acquires the target vehicle's location data, body data, and battery data, and transmits a signal (hereinafter also referred to as the "vehicle management signal") containing the obtained data and the target vehicle's identification information to the management center 500. The location data, body data, and battery data are, for example, the same as the data recorded in S11 in Figure 3 described above.

[0129] When the process in S143A is executed, the process returns to the first step (S141). Therefore, in each of vehicles A and B, the process in S143A is repeatedly executed at a predetermined interval. In this modified example, if YES is determined in S142, the process in S143A is not executed. Therefore, in vehicle C, the process in S143A is not executed.

[0130] When the management center 500 receives the above-mentioned vehicle management signal, it starts the series of processes S11A to S13A and S21 to S25 described below.

[0131] In S11A, the management center 500 records the location data, vehicle body data, and battery data included in the vehicle management signal in the storage device 520, linking them to the time. In the subsequent S12A, the management center 500 determines whether or not the vehicle body 11 of the target vehicle has been subjected to an impact, based on the data included in the vehicle management signal. The determination method is arbitrary, but for example, it may be the same as in S12 (Figure 3) described above. If it is determined that the vehicle body 11 has not been subjected to an impact (NO in S12A), the series of processes by the management center 500 ends.

[0132] If it is determined that the vehicle body 11 has been subjected to an impact (YES in S12A), the management center 500 acquires battery degradation information in S13A, which indicates the degree of degradation of the battery 12 before and after the impact on the vehicle body 11. The method for determining the degree of degradation of the battery 12 is arbitrary, but it may be the same as in S13 (Figure 3) described above. Then, the process proceeds to S21-S25. These steps are the same as S21-S25 shown in Figure 3.

[0133] Even with the modified vehicle 10 and management center 500 described above, it is possible to accurately determine the extent to which the vehicle 10's battery 12 has deteriorated due to an impact when the vehicle body 11 of the vehicle 10 is subjected to an impact. In the case where the dealer 100 does not sell vehicles but only leases them, the processes S141 and S142 (Figures 4 and 9) may be omitted. The processes shown in Figures 3 and 9 (S21 to S25, S11A to S13A) may be executed by the server 150 (dealer terminal) instead of the management center 500.

[0134] [Embodiment 2] Embodiment 2 of this disclosure will be described below. Since Embodiment 2 has many parts in common with Embodiment 1, the differences will be mainly described, and the explanation of the common parts will be omitted. The system configuration of Embodiment 2 is basically the same as that of Embodiment 1. The management system of Embodiment 2 includes the elements shown in Figures 1 and 2. However, the impact force sensor 118b shown in Figure 2 includes a first acceleration sensor attached to the vehicle body 11 (body shell) and a second acceleration sensor attached to the battery case 12. Figure 10 is a flowchart showing the processes executed in the energy storage device management method of Embodiment 2.

[0135] Referring to Figure 10, in S301, the ECU 111 of the vehicle 10 shown in Figure 2 determines whether the impact received by the vehicle 10 is greater than or equal to a predetermined value. The ECU 111 determines whether the impact received by the vehicle 10 is greater than or equal to a predetermined value based on, for example, the output of the first acceleration sensor attached to the vehicle body 11. The determination in S301 is repeated until the vehicle 10 receives an impact of greater than or equal to the predetermined value. If the impact is less than the predetermined value, the vehicle 10 does not transmit the battery degradation information, which will be described later, to the management center 500 (first server). If the vehicle 10 receives an impact of greater than or equal to the predetermined value (YES in S301), the processes in S302 to S304, which will be described below, are executed. In S302, the ECU 111 executes the first process. The first process includes a series of processes shown in at least one of Figures 11 to 14. The ECU 111 obtains the state of the battery 12 (resistance value, capacity, etc.) based on, for example, the output of the BMS 112a shown in Figure 2. The BMS112a may treat the multiple batteries contained in the battery 12 as modules and acquire voltage and current values ​​for each module. The ECU111 also acquires the deformation amount (strain amount) of the battery case based on the output of the strain sensor 112b shown in Figure 2, for example. The ECU111 also acquires the acceleration of the battery 12 based on the output of a second acceleration sensor attached to the battery 12 case, for example.

[0136] Figure 11 is a flowchart showing a first example of the first process in Figure 10. Referring to Figure 11, in S311, the ECU 111 determines whether or not it can obtain the current resistance value of the battery 12 (battery resistance value). If the ECU 111 can obtain the current resistance value of the battery 12 (YES in S311), the ECU 111 obtains the resistance value of the battery 12 before and after the impact in S312, and in the subsequent S313, records the increase in the resistance value of the battery 12 before and after the impact as battery degradation information in the storage device 111b. On the other hand, if the ECU 111 cannot obtain the current resistance value of the battery 12 (NO in S311), the ECU 111 records battery degradation information indicating that the battery has deteriorated due to the accident in the storage device 111b in S314.

[0137] Figure 12 is a flowchart showing a second example of the first process in Figure 10. Referring to Figure 12, in S321, the ECU 111 determines whether or not it can obtain the current capacity of the battery 12. If the ECU 111 can obtain the current capacity of the battery 12 (YES in S321), the ECU 111 obtains the capacity of the battery 12 before and after the impact in S322, and in the following S323, records the amount of decrease in the capacity of the battery 12 before and after the impact as battery degradation information in the storage device 111b. On the other hand, if the ECU 111 cannot obtain the current capacity of the battery 12 (NO in S321), the ECU 111 records battery degradation information in the storage device 111b in S324, indicating that the battery has deteriorated due to the accident.

[0138] Figure 13 is a flowchart showing a third example of the first process in Figure 10. Referring to Figure 13, in S331, the ECU 111 determines whether or not it can obtain the current deformation amount of the battery case 12. If the ECU 111 can obtain the current deformation amount of the battery case 12 (YES in S331), the ECU 111 obtains the deformation amount of the battery case 12 before and after the impact in S332, and in the subsequent S333, records the deformation amount of the battery case 12 before and after the impact as battery degradation information in the storage device 111b. On the other hand, if the ECU 111 cannot obtain the current deformation amount of the battery case 12 (NO in S331), the ECU 111 records battery degradation information indicating that the battery has deteriorated due to the accident in the storage device 111b in S334.

[0139] Figure 14 is a flowchart of the fourth example of the first process in Figure 10. Referring to Figure 14, in S341, the ECU 111 acquires information (acceleration of battery 12) from the second acceleration sensor attached to the battery 12 case. Subsequently, in S342, the ECU 111 records the acceleration of battery 12 as battery degradation information in the storage device 111b.

[0140] In S303 of Figure 10, the ECU 111 transmits the battery degradation information acquired in S302 (for example, battery degradation information acquired in any of S313, S314 in Figure 11, S323, S324 in Figure 12, S333, S334 in Figure 13, or S342 in Figure 14) to the management center 500 (first server).

[0141] In step S304 of Figure 10, the ECU 111 requests the management center 500 (first server) to perform the second process. This completes the series of processes shown in Figure 10. The management center 500 then executes the second process in response to a request from the vehicle 10 (target vehicle). The second process includes a series of processes shown in at least one of Figures 15 to 17.

[0142] Figure 15 is a flowchart showing the first example of the second process in Figure 10. Referring to Figure 15, in S351, the management center 500 determines whether or not vehicle 10 (the target vehicle) is insured. If vehicle 10 is not insured (NO in S351), the series of processes shown in Figure 15 ends. On the other hand, if vehicle 10 is insured (YES in S351), the management center 500 notifies the automobile insurance company's server (for example, the insurance server 600 shown in Figure 2) of the accident in S352. In more detail, vehicle 10 may store contract information indicating the automobile insurance provider. The management center 500 may obtain the contract information from vehicle 10. In S352, the management center 500 may send accident information regarding the accident to the automobile insurance company's server (a second server different from the first server) based on the contract information.

[0143] In the following step S353, the management center 500 determines whether vehicle 10 (the target vehicle) is insured for battery 12, and whether there is another party involved in the accident involving vehicle 10. If vehicle 10 is insured for battery 12 and there is another party involved in the accident involving vehicle 10, the decision in S353 is YES; otherwise, the decision in S353 is NO. The management center 500 may also request and obtain information indicating whether there is another party involved in the accident from the automobile insurance company's server.

[0144] If the decision in S353 is YES, the management center 500 requests and obtains the percentage of fault between the vehicle owner and the other party from the automobile insurance company's server in S354. Subsequently, in S355, the management center 500 calculates the amount of compensation to be paid to the other party according to the percentage of fault and notifies the other party of the calculated amount of compensation. On the other hand, if the decision in S353 is NO, the processes in S354 and S355 are not executed.

[0145] Figure 16 is a flowchart showing a second example of the second process in Figure 10. Referring to Figure 16, in S361, the management center 500 determines whether the degradation of the battery 12 of the vehicle 10 (target vehicle) is above a predetermined value. The management center 500 makes the determination in S361 based on the aforementioned battery degradation information. If the degradation of the battery 12 is below the predetermined value (NO in S361), the series of processes shown in Figure 16 ends. On the other hand, if the degradation of the battery 12 is above the predetermined value (YES in S361), the management center 500 searches for a battery replacement station (BSta200) corresponding to the vehicle 10 (target vehicle) in S362 and notifies the vehicle user of one or more battery replacement stations (hereinafter referred to as "candidate stations") in which the battery 12 can be replaced. The vehicle user who receives the notification can select one of the candidate stations by operating the user terminal of the vehicle 10 (for example, the mobile terminal 20 or HMI117a).

[0146] In the following S363, the management center 500 determines whether or not vehicle 10 is insured for battery 12. If vehicle 10 is insured for battery 12 (YES in S363), the management center 500 reserves a replacement battery (the battery to be replaced for the deteriorated battery 12) at the battery replacement station (BSta200) selected by the vehicle user in S364. On the other hand, if vehicle 10 is not insured for battery 12 (NO in S363), the management center 500 notifies the vehicle user in S365 that vehicle 10 is not insured for battery 12. Upon receiving the notification, the vehicle user can contact one of the candidate stations to inquire about price and payment by operating the user terminal in vehicle 10 (e.g., mobile terminal 20 or HMI117a).

[0147] Figure 17 is a flowchart showing a third example of the second process in Figure 10. Referring to Figure 17, in S371, the management center 500 determines whether the impact received by the vehicle 10 is greater than or equal to a predetermined value. The management center 500 may also obtain impact-related data (for example, the detection value of the first acceleration sensor attached to the vehicle body 11) from the vehicle 10. If the impact received by the vehicle 10 is greater than or equal to a predetermined value (YES in S371), the management center 500, in S372, notifies the emergency service center server of accident occurrence information, location information, and battery degradation information based on the emergency service center contact information stored in the storage device 111b beforehand. In this way, when an accident occurs, the vehicle 10 notifies the emergency service center of accident information (for example, accident occurrence information) and battery 12 (energy storage device) degradation information based on the emergency service center contact information stored in the vehicle 10. On the other hand, if the impact received by the vehicle 10 is less than a predetermined value (NO in S371), the process in S372 is not executed, and the series of processes shown in Figure 17 ends.

[0148] The energy storage device management method according to Embodiment 2 described above (see Figures 10 to 17) also makes it possible to accurately determine the extent to which the energy storage device of the vehicle 10 has deteriorated due to an impact when the vehicle 10 is subjected to an impact.

[0149] In each of the above embodiments, the management center 500, insurance server 600, server 150, and server 250 are all on-premise servers. However, the functionality 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).

[0150] In each of the embodiments described above, only the battery is replaced, but the entire battery pack, including the battery and its accessories (e.g., at least one of the battery ECU, BMS, strain sensor, temperature control system, and SMR), may be replaced. The vehicle may be an xEV (electric vehicle) other than a BEV. The vehicle may be equipped with an internal combustion engine (e.g., a gasoline engine, biofuel engine, or hydrogen engine). The vehicle is not limited to a four-wheeled passenger car, but may be a bus or 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 have flight capabilities. The vehicle may be an unmanned vehicle (e.g., a robotaxi, an automated guided vehicle, or agricultural machinery).

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

[0152] 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 Insurance Servers.

Claims

1. To determine whether a vehicle equipped with an energy storage device has been subjected to an impact, If the vehicle can detect the resistance value of the energy storage device when the vehicle body is subjected to an impact, the vehicle shall acquire first degradation information indicating the degree of degradation of the energy storage device based on the increase in the resistance value of the energy storage device due to the impact, and shall transmit the first degradation information to the first server. If the vehicle body is subjected to an impact and the vehicle is unable to detect the resistance value of the energy storage device, the vehicle transmits second degradation information to the first server indicating that the energy storage device has deteriorated due to the accident. When the first deterioration information or the second deterioration information is transmitted from the vehicle to the first server, the first server performs at least one of the following: replacement-related processing related to the replacement of the energy storage device, insurance-related processing related to automobile insurance, and notification-related processing related to accident reporting. A method for managing energy storage devices, including the management of such devices.

2. The method for managing an energy storage device according to Claim 1, wherein the vehicle determines whether or not the vehicle body has been subjected to an impact based on whether or not an impact force exceeding a predetermined value is detected on the vehicle body by an acceleration sensor attached to the vehicle body.

3. The method for managing an energy storage device according to Claim 2, wherein the vehicle repeatedly performs the determination of whether or not the vehicle body has been subjected to an impact until an impact force of a predetermined value or greater is detected by the acceleration sensor.

4. The method for managing an energy storage device according to claim 2, wherein when the impact force on the vehicle body is less than the predetermined value, the vehicle does not transmit either the first degradation information or the second degradation information to the first server.

5. When the first deterioration information or the second deterioration information is transmitted from the vehicle to the first server, the first server executes the replacement-related processing, The aforementioned exchange-related processing is, Based on the first deterioration information or the second deterioration information, it is determined whether the degree of deterioration of the energy storage device after the vehicle body has been subjected to an impact exceeds a predetermined standard level. If it is determined that the degree of deterioration of the energy storage device exceeds the predetermined standard level, candidate information indicating one or more replacement stations where the energy storage device installed in the vehicle can be replaced will be notified to the vehicle user; if it is determined that the degree of deterioration of the energy storage device does not exceed the predetermined standard level, the candidate information will not be notified to the vehicle user. A method for managing an energy storage device according to claim 1, including the method described in claim 1.

6. The exchange-related processing is: After the candidate information is notified to the user of the vehicle, the user of the vehicle requests that one or more exchange stations select an exchange station to secure an exchange station that can be exchanged for the exchange station. A method for managing an energy storage device according to claim 5, further comprising:

7. When the first deterioration information or the second deterioration information is transmitted from the vehicle to the first server, the first server executes the insurance-related processing, The method for managing a power storage device according to claim 1, wherein the insurance-related processing includes transmitting accident information regarding the occurrence of an accident to a second server of the automobile insurance company to which the vehicle has a contract.

8. The insurance-related processing is: If the other party's vehicle is present in the accident, the percentage of fault of both parties involved in the accident is obtained from the aforementioned second server, To calculate the amount of compensation for damages in accordance with the aforementioned percentage of fault in the aforementioned accident, A method for managing an energy storage device according to claim 7, further comprising:

9. When the first deterioration information or the second deterioration information is transmitted from the vehicle to the first server, the first server executes the notification-related processing, The aforementioned notification-related processing is as follows: To obtain data on the impact force on the vehicle body from the vehicle, If the impact force on the vehicle body is greater than or equal to a predetermined value, accident information regarding the occurrence of the accident and the first deterioration information or the second deterioration information are notified to the third server of the emergency service center; if the impact force on the vehicle body is less than the predetermined value, the notification process to the third server is not performed. A method for managing an energy storage device according to claim 1, including the method described in claim 1.

10. A system including a vehicle and a server, The aforementioned vehicle comprises a vehicle body, an energy storage device, and an electronic control device. The aforementioned electronic control device Determine whether the aforementioned vehicle body has been subjected to an impact, If the vehicle can detect the resistance value of the energy storage device when the vehicle body is subjected to an impact, first degradation information indicating the degree of degradation of the energy storage device is obtained based on the increase in the resistance value of the energy storage device due to the impact, and the first degradation information is transmitted to the server. If the vehicle body is subjected to an impact and the vehicle is unable to detect the resistance value of the energy storage device, it is configured to transmit second degradation information to the server indicating that the energy storage device has deteriorated due to the accident. The server is configured to perform at least one of the following when it receives the first deterioration information or the second deterioration information from the vehicle: replacement-related processing related to the replacement of the energy storage device, insurance-related processing related to automobile insurance, and notification-related processing related to accident reporting.

11. The vehicle further comprises an acceleration sensor mounted on the vehicle body and a BMS (Battery Management System) for detecting the state of the energy storage device, The aforementioned electronic control device is Based on whether or not an impact force exceeding a predetermined value is detected on the vehicle body by the acceleration sensor, it is determined whether or not the vehicle body has been subjected to an impact. The determination of whether or not the vehicle body has been subjected to an impact is repeatedly performed until an impact force exceeding the predetermined value is detected by the acceleration sensor. Based on the output of the BMS, the resistance value of the energy storage device is obtained. The system according to claim 10, wherein when the impact force on the vehicle body is less than the predetermined value, neither the first deterioration information nor the second deterioration information is transmitted to the server.

12. The system further includes a plurality of exchange stations for exchanging vehicle energy storage devices, The server is configured to execute the replacement-related processing when it receives the first deterioration information or the second deterioration information from the vehicle. The aforementioned exchange-related processing is, Based on the first deterioration information or the second deterioration information, it is determined whether the degree of deterioration of the energy storage device after the vehicle body has been subjected to an impact exceeds a predetermined standard level. If it is determined that the degree of deterioration of the energy storage device exceeds the predetermined standard level, candidate information indicating one or more exchange stations from among the plurality of exchange stations capable of replacing the energy storage device installed in the vehicle will be notified to the vehicle user; if it is determined that the degree of deterioration of the energy storage device does not exceed the predetermined standard level, the candidate information will not be notified to the vehicle user. The system according to claim 10, including the following:

13. The exchange-related processing is: After the candidate information is notified to the user of the vehicle, the user of the vehicle requests that one or more exchange stations select an exchange station to secure an exchange station that can be exchanged for the exchange station. The system according to claim 12, further comprising:

14. The system according to claim 12, wherein each of the plurality of exchange stations is configured to allow the vehicle to replace the energy storage device when the degree of deterioration of the energy storage device mounted on the vehicle exceeds a predetermined standard level.

Images