Energy storage device management method and management system, as well as computer equipment and vehicle

Abstract

To provide a management method of a power storage device, which, when an accident occurs to a vehicle, accurately informs an emergency vehicle dealing with the accident about a state of the vehicle having the accident (especially, a state of a power storage device included in the vehicle).SOLUTION: A management method of a power storage device includes steps of: determining whether an accident occurs to a vehicle including a power storage device (S11); acquiring a degree of damage of the power storage device when it is determined that the accident has occurred to the vehicle (S12); and transmitting an emergency signal indicating the acquired degree of the damage and a position of the vehicle having the accident to at least one of an emergency vehicle dealing with the accident and a management device for instructing the emergency vehicle on dispatch (S13).SELECTED DRAWING: Figure 3

Description

Technical Field

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] According to the above impact detection sensor, the occurrence of a vehicle accident can be detected. However, Patent Document 1 does not disclose which part of the vehicle the impact detection sensor detects an impact on. In paragraph

[0022] of Patent Document 1, it is described that when an impact greater than or equal to a predetermined value is detected by the impact detection sensor, the lead battery becomes unusable. However, when an impact force is applied to the vehicle body, the in-vehicle battery is not necessarily damaged. 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] Depending on the technology described in Patent Document 1 above, it is difficult to appropriately convey the state of a vehicle in which an accident has occurred to an emergency vehicle dealing with the accident when a vehicle accident occurs.

[0006] This disclosure was made to solve the above-mentioned problems, and its purpose is to appropriately communicate the condition of the vehicle involved in the accident (in particular, the condition of the vehicle's energy storage device) to emergency vehicles responding to the accident. [Means for solving the problem]

[0007] In accordance with the form relating to the first aspect of this disclosure, the following method for managing an energy storage device is provided. (Paragraph 1) The method for managing the energy storage device includes determining whether or not an accident has occurred with respect to a vehicle equipped with the energy storage device, determining the degree of damage to the energy storage device if it is determined that an accident has occurred with respect to the vehicle, and transmitting an emergency signal indicating the obtained degree of damage and the location of the vehicle involved in the accident to at least one of the emergency vehicle responding to the accident and the management device that instructs the emergency vehicle to dispatch.

[0008] In the above management method, when an accident occurs with a vehicle, the degree of damage to the vehicle's energy storage device is determined, and an emergency signal is sent to an emergency vehicle or its management device. Based on the received emergency signal, the emergency vehicle or its management device can recognize the location of the vehicle involved in the accident and the degree of damage to its energy storage device. When the management device receives an emergency signal, it may also convey the information indicated by the emergency signal to the emergency vehicle when instructing it to dispatch. In this way, the above method makes it possible to appropriately convey the condition of the vehicle involved in the accident (especially the condition of the vehicle's energy storage device) to the emergency vehicle responding to the accident.

[0009] Examples of emergency vehicles include ambulances, fire trucks, tow trucks, and police vehicles. Vehicles equipped with the above-mentioned energy storage devices may also be electric vehicles (xEVs) that use electricity as all or part of their power source. Examples of xEVs include battery electric vehicles (BEVs), hybrid electric vehicles (HEVs), plug-in hybrid electric vehicles (PHEVs), and fuel cell electric vehicles (FCEVs).

[0010] The management method for the energy storage device described in paragraph 1 above may have the configuration described in paragraph 2 or 3 below.

[0011] (Section 2) The method described in Section 1 further has the following characteristics: The emergency signal further indicates the type of energy storage device.

[0012] According to the method described above, emergency vehicles can recognize in advance the impact of different types of energy storage devices based on emergency signals, making it easier to appropriately address damage to energy storage devices at the accident scene.

[0013] (3) The method described in paragraph 1 or 2 further has the following characteristics: The emergency signal further indicates whether the type of vehicle involved in the accident is a BEV (electric vehicle), a PHEV (plug-in hybrid vehicle), a HEV (hybrid vehicle), or a FCEV (fuel cell vehicle).

[0014] According to the above method, emergency vehicles will be able to respond more appropriately to vehicle accidents depending on the type of vehicle.

[0015] In one form, a program is provided that causes a computer to execute the management method for the energy storage device described in any one of paragraphs 1 to 3. In another form, a computer device is provided that distributes the program.

[0016] In accordance with the form relating to the second aspect of this disclosure, the following computer device is provided. (Clause 4) The computer device comprises a processor and a storage device that stores a program that causes the processor to execute the energy storage device management method described in any one of paragraphs 1 to 3.

[0017] According to the computer device described above, the aforementioned method for managing the energy storage device can be suitably executed. In accordance with the third aspect of this disclosure, the following energy storage device management system is provided.

[0018] (Clause 5) The energy storage device management system includes a vehicle equipped with the computer device described in paragraph 4, and a first server that provides a leasing service for energy storage devices for vehicles. When it is determined that an accident has occurred with respect to the vehicle, the computer device determines whether the energy storage device installed in the vehicle is provided through a leasing service, and if it is determined that the energy storage device is provided through a leasing service, it transmits first damage information indicating the degree of damage to the first server.

[0019] According to the system described above, if an accident occurs involving a vehicle equipped with a battery storage device leased through a lease service, the vehicle (computer device) transmits first damage information to the first server providing the lease service. This allows the first server to recognize the degree of damage.

[0020] The energy storage device management system described in paragraph 5 above may have the configuration described in any one of paragraphs 6 to 8 below.

[0021] (Section 6) The management system described in Section 5 further has the following features: The management system further includes a plurality of exchange stations for replacing energy storage devices for vehicles. The first server uses the first damage information to determine whether or not to replace the energy storage device installed in the vehicle, and if it is determined that the energy storage device should be replaced, it requests one or more exchange stations to reserve an energy storage device that can be replaced with the energy storage device.

[0022] According to the system described above, if a vehicle's onboard energy storage device needs to be replaced, the replacement station will be able to quickly prepare a replacement energy storage device.

[0023] (Item 7) The management system according to Item 5 or 6 further has the following features. The management system further includes a second server that provides an insurance service regarding damage to a power storage device for a vehicle. When the first server receives first damage information, it determines whether the power storage device mounted on the vehicle is eligible for the insurance service. When it is determined that the power storage device is eligible for the insurance service, the first server transmits second damage information indicating the degree of damage to the second server. Note that the first damage information and the second damage information may be the same information or different information.

[0024] According to the above system, when an accident occurs to a vehicle equipped with a power storage device that is the target of the insurance service, the second damage information is transmitted from the first server to the second server that provides the insurance service. This makes it easier for the second server to provide an insurance service based on the degree of damage. Also, it becomes easier for the vehicle user to receive the insurance service. The insurance service is a service that compensates for damage to the power storage device mounted on the vehicle.

[0025] (Item 8) The management system according to Item 7 further has the following features. When the second server receives the second damage information, it acquires vehicle information indicating the situation when the accident occurred, determines the degree of fault of the user of the vehicle related to the accident using the acquired vehicle information, and determines the insurance money paid by the insurance service based on the degree of damage and the degree of fault. The second server is configured to perform the above operations.

[0026] According to the above system, it becomes easier to appropriately determine the insurance money based on the degree of damage to the power storage device and the degree of fault of the vehicle user related to the accident.

[0027] The second server may transmit the determined insurance money to at least one of the first server and the user terminal of the vehicle in which the accident occurred. The user terminal may be an in-vehicle terminal mounted on the vehicle or a mobile terminal carried by the user of the vehicle. The user terminal may be registered in advance with at least one of the first server and the second server in association with the vehicle.

[0028] In accordance with the form relating to the fourth aspect of this disclosure, the following vehicles are provided: (Article 9) A vehicle that performs the energy storage device management method described in any one of paragraphs 1 to 3 comprises a vehicle body, an energy storage device mounted on the vehicle body, a first sensor that detects an impact force applied to the vehicle body, a second sensor that detects at least one of the impact force applied to the energy storage device and the state of the energy storage device, a third sensor that detects the position of the vehicle, and a control device that performs the above management method with respect to the energy storage device. The control device is configured to determine whether or not an accident has occurred with respect to the vehicle based on the detection result of the first sensor. The control device is configured to determine the degree of damage to the energy storage device based on the detection result of the second sensor. If it is determined that an accident has occurred with respect to the vehicle, the control device is configured to obtain the position of the vehicle involved in the accident based on the detection result of the third sensor.

[0029] According to the above vehicle, the aforementioned method for managing the energy storage device can be suitably implemented. In accordance with the form relating to Aspect 5 of this disclosure, the following servers are provided:

[0030] (Article 10) The server that performs the energy storage device management method described in any one of paragraphs 1 to 3 is configured to determine whether or not an accident has occurred with respect to the vehicle based on impact force data of the vehicle body acquired from the vehicle, and to determine the degree of damage to the energy storage device based on data related to the energy storage device acquired from the vehicle.

[0031] According to the server mentioned above, the aforementioned method for managing the energy storage device can be suitably executed. [Effects of the Invention]

[0032] According to this disclosure, when a vehicle accident occurs, it becomes possible to appropriately communicate the condition of the vehicle involved in the accident (in particular, the condition of the vehicle's energy storage device) to emergency vehicles responding to the accident. [Brief explanation of the drawing]

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

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

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

[0036] 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 for damage to energy storage devices for vehicles (e.g., for xEVs). The insurance server 600 manages information related to the insurance service. The insurance server 600 belongs to, for example, an insurance company. The insurance server 600 works in conjunction with the management center 500 to provide insurance services for damage to energy storage devices leased through the above-mentioned leasing service. The management center 500 and the insurance server 600 correspond to examples of the "first server" and "second server" as described herein.

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

[0038] Dealer 100 includes server 150. Automobile manufacturers sell or lease vehicles 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 leases at least one of the vehicle body and energy storage device provided by the automobile manufacturer. For example, Dealer 100 may lease the energy storage device 12A of vehicle 10A shown in Figure 1 to a user using a partial lease scheme. 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.

[0039] 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 damage to the energy storage device). That is, for each of vehicles A and B, insurance applies when the energy storage device installed in that vehicle is damaged. The insurance service provides compensation for damage to the energy storage device. As will be described in detail later, the insurance server 600 determines the insurance amount to be paid by the insurance service and notifies the management center 500 of the determined insurance amount. The determined insurance amount is paid by the insurer to the leasing company. If the amount of loss due to damage to the energy storage device is greater than the insurance amount, the leasing company will bill the vehicle user for the difference. Since the above insurance is for leases, vehicle C is not covered by the above insurance. However, vehicle C may be covered by a different insurance.

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

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

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

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

[0044] 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 be able to run using the power stored in the battery 12. 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 an "energy storage device" according to this disclosure.

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

[0046] The ECU111 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 the 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. In this embodiment, the processor 111a executes the programs stored in the storage device 111b, thereby performing various vehicle controls by the ECU111. Although the configuration of the battery ECU112 is not shown in Figure 2, the battery ECU112 is also a computer with a hardware configuration similar to that of the ECU111. The ECU111 and the battery ECU112 are configured to communicate with each other. These ECUs are connected, for example, by a CAN (Controller Area Network).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0060] The vehicle information held by vehicle 10 (storage device 111b) includes vehicle type information, usage information, and battery information. Vehicle 10 transmits the latest vehicle information, along with its vehicle ID, to the management center 500 upon request from the management center 500, or whenever the vehicle information is updated. The vehicle ID may be a VIN (Vehicle Identification Number).

[0061] The vehicle type information indicates whether the vehicle 10 is a BEV (electric vehicle), PHEV (plug-in hybrid vehicle), HEV (hybrid vehicle), or FCEV (fuel cell vehicle). The usage information indicates the usage of the vehicle 10. In this embodiment, the usage information indicates one of the usage modes of vehicle A (partially leased vehicle), vehicle B (fully leased vehicle), or vehicle C (sale vehicle). For example, when a dealer 100 sells or leases vehicle 10, it writes the vehicle type information and usage information related to vehicle 10 to the storage device (not shown) of the server 150 and to the storage device 111b of vehicle 10, respectively.

[0062] The battery information held by vehicle 10 corresponds to information about the battery 12 as it is installed in vehicle 10. The battery information includes identification information (battery ID), specifications (e.g., constituent materials, initial capacity, charging performance, and discharging performance), SOC (State of Charge), and SOH (State of Health).

[0063] The battery information indicates the type of battery 12. The battery information includes, for example, the electrolyte material that makes up the battery 12. The battery information may also further include the electrode material that makes up the battery 12. The degree of influence of the materials differs depending on the constituent materials (especially the electrolyte material) of the energy storage device for vehicles. For example, batteries that use a solid electrolyte tend to be less affected by the electrolyte than batteries that use a liquid electrolyte. Batteries that use a water-based liquid electrolyte tend to be less affected by the electrolyte than batteries that use an organic liquid electrolyte.

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

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

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

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

[0068] The vehicle information held by the management center 500 includes vehicle type information, usage information, battery information, and fee information. The management center 500 obtains the aforementioned vehicle type information, usage information, and battery information from each vehicle 10.

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

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

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

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

[0073] If it is determined that an accident has occurred (YES in S11), the ECU 111 determines the degree of damage to the battery 12 installed in the vehicle in S12. In this embodiment, the ECU 111 determines the degree of damage to the battery 12 based on at least one of the following: the degree of physical damage to the battery 12 case (e.g., the degree of distortion of the battery case detected by the strain sensor 112b), the communication level of the system monitoring the battery 12 (e.g., communication instability, communication interruption, etc.), the degree of damage to the electrical components of the battery 12 (e.g., disconnection, busbar deformation, etc.), and the degree of damage to the environmental system of the battery 12 (e.g., control malfunction, failure, etc.). In this embodiment, the battery ECU 112 and the BMS 112a each function as a system monitoring the battery 12. The temperature control system 112c functions as the environmental system for the battery 12. The ECU 111 may score the degree of damage for each evaluation item related to the degree of damage to the battery 12, and the sum of the scores for each evaluation item may be treated as the degree of damage to the battery 12 (evaluation result). The evaluation items may be the four items mentioned above (case, communication level, electrical components, and environmental system).

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

[0075] In the subsequent S13, the ECU 111 of the target vehicle (the vehicle involved in the accident) acquires the current location of the target vehicle (location of the accident site) and transmits an emergency signal containing the acquired vehicle location information and battery damage information (S12) to one or more emergency vehicles 900. Specifically, the ECU 111 generates the emergency signal using, for example, the vehicle type information and battery information possessed by the target vehicle, the current location information of the target vehicle detected by the location sensor 118a, and the degree of damage to the battery 12 acquired in S12. Such an emergency signal indicates the type of the target vehicle, the location of the target vehicle, the degree of damage to the battery 12, and the type of battery 12. 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.

[0076] Emergency vehicle 900 is a vehicle that responds to an accident. Emergency vehicle 900 that receives the above emergency signal includes, for example, at least one (for example, all) of an ambulance, a fire truck, a tow truck, and a police vehicle. ECU 111 may not send an emergency signal to the tow truck if the damage to the battery 12 is minor enough that the target vehicle can run, but may send an emergency signal to the tow truck if the damage to the battery 12 is major enough that the target vehicle cannot run.

[0077] In this embodiment, the emergency signal is transmitted from the target vehicle to the emergency vehicle 900. As a result, the emergency vehicle 900 can recognize the location of the target vehicle (the vehicle involved in the accident) and the degree of damage to the battery 12 based on the received emergency signal. Thus, according to the processes S11 to S13 described above, when a vehicle accident occurs, it becomes possible to appropriately communicate the status of the target vehicle (in particular, the status of the battery 12 installed in the target vehicle) to the emergency vehicle 900 that will deal with the accident.

[0078] In this embodiment, the emergency signal indicates the type of battery 12 installed in the target vehicle. Specifically, the effect of the battery type 12 is indicated by the electrolyte material. For example, the effect of battery types 12 using organic liquid electrolytes, aqueous liquid electrolytes, and solid electrolytes may be evaluated in three stages, such as high, normal, and low. In this embodiment, by recognizing the effect of the battery type 12 in advance based on the emergency signal, the emergency vehicle 900 can more easily deal with battery damage at the accident scene. Note that the information indicating the type of energy storage device is not limited to the electrolyte material and is arbitrary. Also, the evaluation method is not limited to a three-stage evaluation, but may be a two-stage evaluation or a four-stage or higher evaluation.

[0079] In this embodiment, the emergency signal indicates the type of vehicle in question (BEV, PHEV, HEV, or FCEV). BEVs do not have an internal combustion engine, while PHEVs and HEVs each have an internal combustion engine. Also, BEVs and PHEVs each have an external charging function, while HEVs do not. The external charging function is a function that charges the battery storage device installed in the vehicle with power from outside the vehicle. The capacity of the battery storage device installed in the vehicle tends to be in the order of BEV, PHEV, and HEV, from largest to smallest. Due to these differences in characteristics, the way accidents are handled differs between BEVs, PHEVs, and HEVs. In addition, FCEVs are equipped with a device for storing fuel (e.g., hydrogen). Therefore, the way accidents are handled differs between FCEVs and other electric vehicles (BEV, PHEV, HEV). According to the above emergency signal, the emergency vehicle 900 can respond appropriately to vehicle accidents according to the type of vehicle in question.

[0080] In this embodiment, the ECU 111 of the target vehicle directly transmits an emergency signal to the emergency vehicle 900. However, the ECU 111 may transmit an emergency signal to a management device (not shown) that instructs the emergency vehicle 900 to dispatch, in addition to or instead of the emergency vehicle 900. For example, the ECU 111 may request the dispatch of a fire truck by transmitting an emergency signal to a server (management device) of a fire station that instructs fire trucks to dispatch. When the management device (e.g., server) instructs the emergency vehicle 900 to dispatch in response to the emergency signal, it may convey the information indicated by the emergency signal to the emergency vehicle 900. The management device may direct the emergency vehicle 900 to the accident scene based on the location information indicated by the emergency signal. Furthermore, the emergency vehicle 900 or its management device may notify workers (e.g., terminals carried by workers) of the equipment necessary to appropriately deal with the accident based on at least one of the type of battery 12 indicated by the emergency signal (or an evaluation value of the impact of that type) and the degree of damage to the battery 12.

[0081] In the following step S14, the ECU 111 determines whether the battery 12 installed in the target vehicle is provided through a lease service. The ECU 111 may, for example, use usage information to determine which of vehicles A to C (Figure 1) the target vehicle corresponds to. If the target vehicle is vehicle A or vehicle B, it is determined that the battery 12 of the target vehicle is provided through a lease service (YES in S14), and the process proceeds to S15.

[0082] In S15, the ECU 111 transmits a signal containing information for managing the battery 12 (hereinafter also referred to as the "first management signal") to the management center 500, along with the identification information (vehicle ID) of the target vehicle. The first management signal includes the current location information of the target vehicle detected by the position sensor 118a and damage information (first damage information) indicating the degree of damage to the battery 12 acquired in S12. If an accident occurs with a target vehicle equipped with a battery 12 leased through the lease service, the first damage information is transmitted from the target vehicle to the management center 500 through the processing in S15. This allows the management center 500 to recognize the degree of damage.

[0083] Once the process in S15 described above is executed, the process proceeds to S16. Also, if the target vehicle is vehicle C, it is determined that the battery 12 of the target vehicle is not provided by the lease service (NO in S14), and the process proceeds to S16 without executing the process in S15.

[0084] In S16, the ECU 111 notifies the vehicle user of the necessary actions to take after the accident. Specifically, the ECU 111 may control the user terminal of the vehicle in question (for example, at least one of the HMI 117a and the mobile terminal 20) so that it displays a predetermined procedure manual (for example, an accident response manual).

[0085] The ECU111 may determine the content of the procedure manual to be displayed on the user terminal based on at least one of the information indicating which of vehicles A to C (Figure 1) the target vehicle corresponds to (usage type information) and the degree of damage to the battery 12 acquired in S12. For example, if the degree of damage to the battery 12 is small enough that the target vehicle can be driven, the ECU111 may display on the user terminal that the target vehicle is drivable. On the other hand, if the degree of damage to the battery 12 is large enough that the target vehicle cannot be driven, the ECU111 may display on the user terminal that the target vehicle is not drivable. Also, if the target vehicle is vehicle C, the ECU111 may display on the user terminal the location of a repair shop other than BSta200. If the target vehicle is vehicle A or vehicle B, the ECU111 may display on the user terminal the location of one or more BSta200s (more specifically, battery replacement stations that also serve as vehicle repair shops) located around the target vehicle. One or more BSt200s located around the target vehicle may be the single BSt200 closest to the target vehicle, or at least one BSt200 located within a predetermined distance from the target vehicle's position. When the process in S16 is executed, the series of processes in S11 to S16 by the target vehicle are completed.

[0086] When the management center 500 receives the aforementioned first management signal and vehicle ID (S15), it starts the series of processes S21 to S25 described below. In S21, the management center 500 uses the first damage information included in the first management signal to determine whether or not to replace the battery 12 installed in the target vehicle. The management center 500 may also determine whether or not to replace the battery 12 based on the degree of damage. In this embodiment, the management center 500 determines to replace the battery 12 if the degree of damage to the battery 12 exceeds a predetermined threshold (hereinafter referred to as "Th2"). If the degree of damage to the battery 12 is Th2 or less, the management center 500 determines not to replace the battery 12.

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

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

[0089] As described above, the management center 500 uses the first damage information to determine whether or not to replace the battery 12 installed in the target vehicle (S21), and if it is determined that the battery 12 should be replaced, it requests one or more replacement stations to secure a power storage device that can be replaced with the battery 12 (S23). With this configuration, when it becomes necessary to replace the battery 12 installed in the target vehicle, BSta 200 can quickly prepare a replacement power storage device (i.e., a power storage device compatible with the power storage device installed in the target vehicle).

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

[0091] Once the process in S23 is executed, the process proceeds to S24. If it is determined that battery 12 does not need to be replaced (NO in S21), the process proceeds to S24 without executing processes S21 to S23.

[0092] In S24, the management center 500 determines whether the battery 12 installed in the target vehicle is eligible for insurance coverage. Specifically, based on the identification information (vehicle ID) of the target vehicle, the management center 500 extracts usage information of the target vehicle from the database stored in the storage device 520, and determines which of vehicles A to C (Figure 1) the target vehicle falls under based on the extracted usage information. If the target vehicle is vehicle A or vehicle B, and the degree of damage to the battery 12 installed in the target vehicle (first damage information) exceeds a predetermined threshold (hereinafter referred to as "Th3"), the insurance coverage conditions are met; otherwise, the insurance coverage conditions are not met. Th3 is a threshold that defines the scope of insurance coverage and may be predetermined in the insurance contract. If the degree of damage to the battery 12 does not exceed Th3, it means that the degree of damage has not reached the level required for insurance coverage.

[0093] If the insurance coverage conditions are met, it is determined that the battery 12 is eligible for insurance service (YES in S24), and the process proceeds to S25. In S25, the management center 500 sends a signal (hereinafter also referred to as the "second management signal") containing damage information (second damage information) indicating the degree of damage to the battery 12 installed in the target vehicle, along with the identification information of the target vehicle (vehicle ID), to the insurance server 600.

[0094] In this way, when the management center 500 receives the first management signal (first damage information), it determines whether the battery 12 installed in the target vehicle is eligible for insurance service (S24). If it determines that the battery 12 of the target vehicle is eligible for insurance service, it transmits a second management signal containing second damage information to the insurance server 600 (S25). With this configuration, when an accident occurs involving a vehicle equipped with an energy storage device that is eligible for insurance service, the management center 500 transmits the second damage information to the insurance server 600 that provides the insurance service. This makes it easier for the insurance server 600 to provide insurance service based on the degree of damage. It also makes it easier for vehicle users to receive insurance service.

[0095] Once the S25 process is executed, the series of processes S21 to S25 performed by the management center 500 is completed. If the aforementioned insurance coverage conditions are not met, it is determined that the battery 12 is not eligible for insurance service (NO in S24), and the series of processes S21 to S25 performed by the management center 500 is completed without the execution of the S25 process.

[0096] After the accident is handled by the emergency vehicle 900, the vehicle involved in the accident (the vehicle that was involved in the accident) is transported by either its own power or by a tow truck to a BSta200 located near the accident site (for example, the BSta200 closest to the accident site). At the BSta200, the battery 12 installed in the vehicle is replaced. Figure 4 is a flowchart showing the battery replacement process performed by the vehicle 10 and the battery replacement station terminal (server 250).

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

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

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

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

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

[0102] In S130 and S240, battery replacement is performed according to the procedure described later (see Figure 5). 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.

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

[0104] 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, after which the series of processes shown in Figure 4 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 4 ends. Note that the error handling can be set arbitrarily.

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

[0106] Referring to Figures 1 and 2, as well as Figure 5, 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.

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

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

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

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

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

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

[0113] In the above test, the charger / discharger discharges battery B4 until it falls below a predetermined first SOC value (e.g., an SOC value indicating an empty charge state), and then charges battery B4 until it rises above a predetermined second SOC value (e.g., an SOC value indicating a fully charged state). The measuring device includes various sensors to measure the state of battery B4 during charging (e.g., temperature, current, and voltage). 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.

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

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

[0116] Figure 5 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.

[0117] Figure 6 is a flowchart showing the process related to the provision of insurance services that the insurance server 600 executes after receiving the second management signal (S25 in Figure 3) from the management center 500.

[0118] Referring to Figure 6 in conjunction with Figures 1 and 2, when the insurance server 600 receives a second management signal (second damage information) and identification information of the target vehicle (vehicle ID) from the management center 500, it starts a series of processes from S31 to S37. In S31, the insurance server 600 communicates wirelessly with the target vehicle identified by the vehicle ID and obtains accident data from the target vehicle that shows the condition of the target vehicle at the time of the accident. The insurance server 600 may also communicate with the target vehicle via the management center 500. The accident data includes, for example, video from the drive recorder 117c showing the condition of the target vehicle before and after the accident. In the subsequent S32, the insurance server 600 determines, based on the accident data, whether or not there is another vehicle involved in the accident. In the case of a single-vehicle accident (self-inflicted accident), it is determined in S32 to be NO (there is no other vehicle involved in the accident), and the process proceeds to S36.

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

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

[0121] In S36, the insurance server 600 determines the insurance payout to be made by the insurance service based on the degree of damage to the battery 12 installed in the target vehicle (the vehicle involved in the accident) (second damage information) and the vehicle user's percentage of fault in the accident (S35). The insurance server 600 may also determine the insurance payout using a formula (for example, a formula in accordance with the insurance contract) that shows the relationship between the degree of battery damage, the percentage of fault in the accident, and the insurance payout.

[0122] In the case of a single-vehicle accident (self-inflicted accident), the insurance server 600 may determine the insurance payout in S36 based solely on the degree of damage to the battery 12. However, if the accident data indicates that the user intentionally damaged the battery 12, the insurance server 600 may decide that the insurance does not apply (no insurance payout).

[0123] In the following step S37, the insurance server 600 sends a signal (hereinafter also referred to as the "insurance signal") to the management center 500 indicating the vehicle ID of the target vehicle and the insurance amount determined in S36. This completes the series of processes from S31 to S37 by the insurance server 600, and the series of processes from S51 to S53 by the management center 500 begin.

[0124] In S51, the management center 500 calculates the amount of loss due to damage to the battery 12 based on battery information related to the target vehicle (e.g., specifications of battery 12) and the degree of damage to the battery 12 (first damage information) indicated by the first management signal (S15 in Figure 3). In the following S52, the management center 500 determines whether the amount of loss due to damage to the battery 12 (S51) is greater than the insurance amount indicated by the insurance signal. If the amount of loss due to damage to the battery 12 is greater than the insurance amount (YES in S52), the management center 500 notifies the user terminal of the target vehicle (e.g., mobile terminal 20) in S53 to claim the difference (= loss amount - insurance amount). On the other hand, if the amount of loss due to damage to the battery 12 is less than or equal to the insurance amount (NO in S52), the management center 500 does not make a claim to the vehicle user (S53).

[0125] As described above, the management method for the energy storage device according to this embodiment includes the processes shown in Figures 3, 4, and 6. In this embodiment, the ECU 111 functions as 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.

[0126] The vehicle 10 according to this embodiment performs a series of processes S11 to S16 shown in Figure 3. The vehicle 10 comprises a vehicle body 11, a battery 12 (energy storage device) mounted on the vehicle body 11, an impact force sensor 118b (first sensor), a BMS 112a and a strain sensor 112b (second sensor), a position sensor 118a (third sensor), and an ECU 111 (control device) that performs the above-described management method (including S11 to S16 in Figure 3) with respect to the battery 12. The ECU 111 determines whether or not an accident has occurred with respect to the vehicle 10 based on the detection result from the impact force sensor 118b (S11). The ECU 111 determines the degree of damage to the energy storage device based on the detection result from at least one of the BMS 112a and the strain sensor 112b (S12). When the ECU 111 determines that an accident has occurred with respect to vehicle 10, it acquires the location of the vehicle 10 involved in the accident based on the detection results from the position sensor 118a, and transmits an emergency signal containing the obtained vehicle location information and battery damage information to one or more emergency vehicles 900 (S13). With such a vehicle 10, it becomes possible to appropriately communicate the condition of the vehicle 10 involved in the accident (especially the condition of the battery 12) to the emergency vehicles 900 that are responding to the accident.

[0127] In the above embodiment, the insurance payout for damage to 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 Figures 3 and 6). 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, in S14 of Figure 3, the processing may be modified so that it is determined as "YES" if the target vehicle is vehicle A, and as "NO" if the target vehicle is vehicle B. In other words, the processing shown in Figure 6 may be executed only for vehicle A. The insurance server 600 may also provide an insurance service for vehicle B (fully leased vehicle) that covers not only damage to the energy storage device but also damage to the vehicle body.

[0128] The processes shown in Figures 3 and 6 (S21-S25, S51-S53) may be executed by the server 150 (dealer terminal) instead of the management center 500. The processing flows shown in Figures 3, 4, and 6 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 S15 of Figure 3, the target vehicle may send a first management signal containing accident data to the management center 500. Then, in S25 of Figure 3, the management center 500 may send a second management signal containing accident data to the insurance server 600. In this configuration, S31 in Figure 6 may be omitted. Furthermore, in a system where the vehicle user involved in an accident contacts the insurance company themselves, the notification from the management center 500 to the insurance server 600 (S24, S25 in Figure 3) may be omitted.

[0129] In the above embodiment, the vehicle 10 determines whether or not an accident has occurred. However, the system is not limited to this configuration, and the management center 500 may determine whether or not an accident has occurred for the vehicle 10 instead.

[0130] Figure 7 is a flowchart showing a modified version of the process shown in Figure 3. Referring to Figure 7 along with Figures 1 and 2, in this modified version, the ECU 111 of the target vehicle determines in S14 whether the battery 12 installed in the target vehicle is provided through a lease service, without executing the processes S11 to S13 (Figure 3) described above. If the battery 12 of the target vehicle is provided through a lease service (YES in S14), the ECU 111 acquires the latest vehicle information in S15A and transmits a signal containing the obtained vehicle information (hereinafter also referred to as the "vehicle management signal") to the management center 500 along with the identification information (vehicle ID) of the target vehicle. Specifically, the vehicle management signal includes the location information of the target vehicle, vehicle body data for determining whether an accident has occurred with respect to the target vehicle, and battery data for calculating the degree of damage to the battery 12 installed in the target vehicle. The location information of the target vehicle includes the location data of the target vehicle detected by the location sensor 118a. The vehicle body data includes the impact force data of the vehicle body 11 detected by the impact force sensor 118b. The battery data includes various data about the battery 12 detected by the BMS 112a and strain sensor 112b. When the process in S15A is executed, the process returns to the first step (S14). For this reason, in each of vehicles A and B, the process in S15A is repeatedly executed at a predetermined cycle. In this modified example, if NO is determined in S14, the process in S15A is not executed. For this reason, the process in S15A is not executed in vehicle C.

[0131] When the management center 500 receives the above-mentioned vehicle management signal and vehicle ID (S15A), it starts the series of processes S11A to S13A and S21 to S23 described below.

[0132] In S11A, the management center 500 determines whether or not an accident has occurred with respect to the target vehicle based on the vehicle data included in the vehicle management signal. The determination method is arbitrary, but for example, it may be the same as in S11 (Figure 3) described above. If it is determined that no accident has occurred (NO in S11A), the series of processes by the management center 500 ends.

[0133] If it is determined that an accident has occurred (YES in S11A), the management center 500 determines the degree of damage to the battery 12 installed in the target vehicle (the vehicle involved in the accident) in S12A, based on the battery data included in the vehicle management signal. The method for determining the degree of damage to the battery 12 is arbitrary, but it may be the same as in S12 (Figure 3) described above. In the following S13A, the management center 500 transmits an emergency signal to one or more emergency vehicles 900, which includes the type of target vehicle, the location of the target vehicle, the degree of damage to the battery 12 (S12A), and the type of battery 12 (or an evaluation value of the impact of that type). Based on the identification information (vehicle ID) of the target vehicle, the management center 500 can obtain information about the target vehicle from the database stored in the storage device 520. The location of the target vehicle is included in the vehicle management signal.

[0134] Then proceed to steps S21-S23. These steps are the same as those shown in Figure 3 (S21-S23). In this modified example, steps S24 and S25 (Figure 3) are omitted. However, this is not the only option; steps S24 and S25 may be included after S21-S23.

[0135] Even with the modified vehicle 10 and management center 500 described above, it is possible to appropriately communicate the condition of the vehicle 10 involved in the accident (especially the condition of the battery 12) to the emergency vehicle 900 that will respond to the accident. In the case where the dealer 100 does not sell vehicles but only leases them, the decision in S14 (Figures 3 and 7) may be omitted.

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

[0137] In the above embodiment, only the battery is replaced, but the battery pack, including the battery and its accessories (e.g., BMS and strain sensor), may be replaced as a whole. The vehicle is not limited to a four-wheeled passenger car, but may be a bus or truck, or a three-wheeled or five-wheeled or more xEV (electric vehicle). 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 (AGV), or agricultural machinery).

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

[0139] 10 Vehicles, 11 Body, 12 Battery, 20 Mobile devices, 100 Dealers, 111 ECU, 112a BMS, 112b Strain sensors, 112c Temperature control systems, 117a HMI, 117b NAVI, 117c Drive recorders, 118a Position sensors, 118b Impact force sensors, 150 Servers, 200 Battery replacement stations, 250 Servers, 500 Management centers, 600 Insurance servers, 900 Emergency vehicles.

Claims

1. A computer device determines whether or not an accident has occurred with respect to a vehicle equipped with an energy storage device, If it is determined that an accident has occurred with respect to the vehicle, the computer device will determine the degree of damage to the energy storage device. The computer device transmits an emergency signal indicating the obtained degree of damage and the location of the vehicle where the accident occurred to at least one of the emergency vehicle responding to the accident and the management device that instructs the emergency vehicle to dispatch. If it is determined that an accident has occurred with the aforementioned vehicle, the computer device will determine whether or not the energy storage device installed in the vehicle is provided through a lease service, If it is determined that the energy storage device is provided through the lease service, the computer device transmits damage information indicating the degree of damage to the server providing the lease service. 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 emergency signal further indicates the type of energy storage device.

3. The method for managing an energy storage device according to claim 1 or 2, wherein the emergency signal further indicates whether the type of vehicle involved in the accident is an electric vehicle, a plug-in hybrid vehicle, a hybrid vehicle, or a fuel cell vehicle.

4. A computer device comprising a processor and a storage device that stores a program causing the processor to execute the energy storage device management method described in claim 1.

5. A vehicle and The first server provides a leasing service for vehicle energy storage devices, A management system for an energy storage device, including The aforementioned vehicle is equipped with an energy storage device and a computer device, The aforementioned computer device, To determine whether or not an accident occurred with the aforementioned vehicle, If it is determined that an accident has occurred with respect to the said vehicle, the degree of damage to the said energy storage device of the said vehicle shall be determined, An emergency signal indicating the obtained degree of damage and the location of the vehicle where the accident occurred is transmitted to at least one of the emergency vehicle responding to the accident and the management device that instructs the emergency vehicle to dispatch. It is configured to perform, A management system for a power storage device, wherein the computer device determines, when it is determined that an accident has occurred with respect to the vehicle, whether or not the power storage device installed in the vehicle is provided through the lease service, and when it is determined that the power storage device is provided through the lease service, transmits first damage information indicating the degree of damage to the first server.

6. The management system further includes multiple exchange stations for replacing vehicle energy storage devices. The energy storage device management system according to claim 5, wherein the first server determines whether or not to replace the energy storage device installed in the vehicle using the first damage information, and if it is determined that the energy storage device should be replaced, it requests one or more of the replacement stations to secure an energy storage device that can be replaced with the energy storage device.

7. The management system further includes a second server that provides insurance services for damage to vehicle energy storage devices. The energy storage device management system according to claim 5 or 6, wherein the first server, upon receiving the first damage information, determines whether the energy storage device installed in the vehicle is eligible for the insurance service, and if it is determined that the energy storage device is eligible for the insurance service, transmits second damage information indicating the degree of damage to the second server.

8. When the second server receives the second damage information, To obtain accident data showing the circumstances at the time the aforementioned accident occurred, Using the acquired accident data, the degree of negligence of the vehicle user in relation to the accident is determined, Based on the degree of damage and the degree of negligence, the insurance payment to be made by the insurance service shall be determined, A management system for an energy storage device according to claim 7, configured to perform the following:

9. A vehicle body and, The energy storage device mounted on the vehicle body, A first sensor for detecting the impact force applied to the vehicle body, A second sensor that detects at least one of the impact force applied to the energy storage device and the state of the energy storage device, A third sensor for detecting the position of the vehicle, The computer device according to claim 4, Equipped with, The computer device is configured to determine whether or not an accident has occurred with respect to the vehicle based on the detection results from the first sensor. The computer device is configured to determine the degree of damage to the energy storage device based on the detection results from the second sensor. The computer device is configured to acquire the location of the vehicle involved in the accident based on the detection results from the third sensor when it is determined that an accident has occurred with respect to the vehicle.

Images