Moving body and management system

Abstract

The invention relates to a mobile body and a management system. The moving body includes a power storage device and a control device. When the first power storage device is mounted on the moving body as a power storage device, the control device stores identification information of the first power storage device. When the first power storage device is replaced with the second power storage device and the identification information of the first power storage device stored in the control device is rewritten with the identification information of the second power storage device, the control device transmits a first signal to the outside of the moving body, the first signal notifying that the power storage device has been replaced.

Description

Technical Field

[0001] The present disclosure relates to a mobile object and a management system. Background Art

[0002] Japanese Patent Application Laid-Open No. 2017-189032 discloses a technology for determining whether first vehicle model information held by a vehicle control unit and second vehicle model information held by a battery control unit match each other when an auxiliary battery that supplies power to a vehicle control unit and a battery control unit is removed.

[0003] For example, an electric vehicle such as a battery electric vehicle is equipped with a power storage device (e.g., a driving battery) for driving. Generally speaking, the power storage device for driving is large-capacity and expensive. Even if such a large-capacity power storage device fails, it will not be replaced immediately, but repaired when it can be repaired. However, in the case where the vehicle manager entrusts the repair of the power storage device mounted on the vehicle to a repair merchant, the repair merchant may replace the power storage device against the intention of the vehicle manager. Summary of the invention

[0004] The present disclosure has been made to solve the above-mentioned problem, and an object of the present disclosure is to notify the outside of a moving body that a power storage device mounted on the moving body has been replaced.

[0005] A mobile body according to one embodiment of the present disclosure includes a power storage device and a control device. When a first power storage device is mounted on the mobile body as the power storage device, the control device stores identification information of the first power storage device. The control device is configured to send a first signal to the outside of the mobile body notifying that the power storage device has been replaced when the first power storage device is replaced with a second power storage device and the identification information of the first power storage device stored in the control device is rewritten with the identification information of the second power storage device.

[0006] According to the present disclosure, it is possible to notify the outside of the moving body that the power storage device mounted on the moving body has been replaced. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Hereinafter, features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described with reference to the accompanying drawings, wherein like reference numerals denote like elements, and wherein:

[0008] Figure 1 This is a diagram showing an overview of a management system according to an embodiment of the present disclosure.

[0009] Figure 2 Yes means Figure 1 A diagram showing the composition of the information platform.

[0010] Figure 3 It is a diagram showing the configuration of a moving object according to an embodiment of the present disclosure.

[0011] Figure 4 Detailed description of the invention The invention is a flowchart showing a management method according to an embodiment of the present disclosure.

[0012] Figure 5 This is a flowchart showing a process of report control executed by a mobile object according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0013] The embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The same or corresponding parts in the drawings are denoted by the same reference numerals, and their description will not be repeated.

[0014] Figure 1 This is a diagram showing an overview of the management system according to this embodiment. Figure 1 The management system shown includes a management terminal 30, a plurality of vehicles 40, a server 50, a data collection system 100A to a data collection system 100D, a plurality of dealers 110, a plurality of vehicle management devices 120, a plurality of exchange stations 130, a plurality of residences 140, a plurality of energy storage systems (ESS: Energy Storage System) 150, an information platform 200, and a repair shop 300. A plurality of power storage devices circulate in the system. Each power storage device is used in sequence by a plurality of users. For example, a power storage device used by a certain user can be provided to another user. Inherent identification information (hereinafter referred to as "battery ID") is given to each power storage device in such a manner that each power storage device circulating in the system can be identified. In addition, the owner and user of the power storage device are registered in the information platform 200 and are given inherent identification information. In addition, the use location (vehicle 40, residence 140, ESS150) and the storage location (exchange station 130, repair shop 300) of the power storage device are also registered in the information platform 200 and are given inherent identification information.

[0015] Each of the plurality of vehicles 40 is equipped with a power storage device. The identification information of each vehicle (hereinafter referred to as "vehicle ID") may be a vehicle identification number (VIN: Vehicle Identification Number). The configuration of the vehicle 40 will be described in detail later (see Figure 3 ).

[0016] The dealer 110 is equipped with a scan tool 111 and a dealer terminal 112 (for example, a computer). The scan tool 111 acquires information (including a vehicle ID and a battery ID) from a vehicle 40 that visits the dealer 110 through wired communication. The information of the vehicle 40 acquired by the scan tool 111 is sent to the dealer terminal 112. The dealer terminal 112 manages the information of each vehicle by distinguishing it with the vehicle ID.

[0017] The vehicle management device 120 includes a terminal (e.g., a computer) configured to wirelessly communicate with a moving or parked vehicle 40. The vehicle management device 120 obtains information (including a vehicle ID and a battery ID) from each of the plurality of vehicles 40 through wireless communication. The vehicle management device 120 distinguishes and manages the information of each vehicle using the vehicle ID.

[0018] The exchange station 130 is configured to store a replacement power storage device and to replace a power storage device mounted on the vehicle 40. Specifically, at the exchange station 130, a power storage device is removed from the vehicle 40 and another power storage device (replacement power storage device) is mounted on the vehicle 40.

[0019] House 140 includes a solar power generation system and a stationary power storage system (house power storage system). The power storage system is configured to supply power to house 140. In addition, the power storage system can also store the power generated by the solar power generation system.

[0020] ESS150 is a stationary power storage system that is larger in scale than a residential power storage system. ESS150 functions as a power source for a power system or a facility. A power system is a power grid constructed by power transmission and distribution equipment. Examples of facilities include factories and commercial facilities. ESS150 can also store surplus power.

[0021] The repair shop 300 is configured to repair the power storage device. A failed power storage device is sent to the repair shop 300 and repaired at the repair shop 300. In the case where a power storage device mounted on the vehicle 40 fails, the manager (user) of the vehicle 40 stores the vehicle 40 at the repair shop 300. In the repair shop 300, the power storage device is repaired while being mounted on the vehicle 40. In addition, the repair shop 300 is configured to store a plurality of power storage devices and also functions as a warehouse. The management terminal 30 is provided in the repair shop 300 to manage the information (inventory information) of each power storage device stored in the repair shop 300.

[0022] The vehicle 40, the exchange station 130, the residence 140, the ESS 150 and the repair shop 300 are each equipped with a battery management system (BMS). The BMS includes: a detector for detecting the state of the power storage device; and a controller for recording the detection result obtained by the detector in a storage device in association with the detection time. However, the BMS at the storage location may be omitted.

[0023] The data collection system 100A is configured to periodically collect information related to the vehicle-mounted power storage device from a plurality of dealers 110 (dealer terminals 112) and a plurality of vehicle management devices 120, and to form the collected information into a database. The information of the power storage device of each vehicle acquired by the BMS of each vehicle is transmitted to the scan tool 111 or the vehicle management device 120 through wired communication or wireless communication.

[0024] The data collection system 100B, the data collection system 100C, and the data collection system 100D are configured to respectively collect information on the replacement power storage device, the information on the house power storage device, and the information on the ESS power storage device, and to form the collected information into a database. The BMS in each of the replacement station 130, the house 140, and the ESS 150 transmits the information on the power storage device to the corresponding data collection system in response to a request from the corresponding data collection system or periodically.

[0025] The information platform 200 has nodes 10A, 10B, 10C, 10D, and 10E (for example, computers) corresponding to the data collection system 100A, 100B, 100C, 100D, and the management terminal 30, respectively. The information platform 200 also has a server 20. These nodes and the server 20 form a distributed ledger network (hereinafter referred to as "DLN"). However, the number of nodes can be changed appropriately. The information platform 200 uses, for example, a distributed ledger technology that utilizes a blockchain (hereinafter referred to as "BLC") to manage the information of each power storage device circulating in the system. The distributed ledger records all information from the start of the use of the distributed ledger to the present. Figure 2 It is a diagram showing the structure of the information platform 200.

[0026] Reference Figure 2 Node 10A includes a processor 11, a random access memory (RAM) 12, a human machine interface (HMI) 13, a communication device 14, and a storage device 15, which are connected to a bus 19. The storage device 15 stores a distributed ledger. Figure 2Only the configuration of node 10A is shown in FIG. 1 , but the other nodes 10B to 10E also have the same configuration as described above. Figure 2 The node 10A shown has the same configuration.

[0027] The server 20 also has a distributed ledger and functions as a node of the DLN. The information recorded in the distributed ledger is shared by all nodes of the DLN. In addition, the server 20 also functions as a parsing server that parses the information added to the distributed ledger by nodes 10A to 10E. The server 20 includes a processor 21, a RAM 22, an HMI 23, a communication device 24, and a storage device 25, which are connected to a bus 29. The storage device 25 stores a distributed ledger. The storage device 25 also stores information (calculation information) used for information parsing.

[0028] The distributed ledger of each node of the DLN records information related to each power storage device circulating in the system (hereinafter referred to as "battery information"). The battery information includes the identification information of the power storage device (battery ID), the identification information of the owner of the power storage device (owner ID), the identification information of the user who uses the power storage device (user ID), the identification information of the place where the power storage device is used (for example, vehicle ID), the technical specification information of the power storage device, and the usage history information of the power storage device. However, the battery information is not limited to this information, and may further include other information related to the power storage device (for example, material composition information, insurance contract information, performance evaluation information, and control program).

[0029] When the data collection system 100A, the data collection system 100B, the data collection system 100C, the data collection system 100D or the management terminal 30 obtains new battery information, the corresponding node records the new block containing the battery information in the distributed ledger. Specifically, the corresponding node generates transaction data containing the battery information, the identification information of the node (recorder ID) and the recording time. Then, the node records the new block containing the hash value of the generated transaction data and the past transaction data (previous block) in the distributed ledger. As a result, the distributed ledgers of each node of the DLN are updated. The various information contained in the new block is associated with each other.

[0030] The vehicle 40 is configured to be able to wirelessly communicate with the server 50 and the mobile terminal 80, respectively. The server 50 of the present embodiment is an external server having a processor and a storage device. The server 50 uses the information obtained from the information platform 200 (for example, the degree of battery degradation) to provide a prescribed service (for example, an insurance service). The mobile terminal 80 is a terminal that can be carried by a user of the vehicle 40. In the present embodiment, a smartphone with a touch panel display is used as the mobile terminal 80. The smartphone has a built-in computer and has a speaker function. However, it is not limited to this, and wearable devices, electronic keys, etc. can also be used as the mobile terminal 80.

[0031] The vehicle 40 is, for example, a plug-in hybrid electric vehicle (PHEV). The vehicle 40 includes a battery pack BP. Figure 3 4 is a diagram showing the structure of a vehicle 40. Figure 3 The battery pack BP includes a battery 41, a detector 41a, and a battery ECU 41b. A well-known vehicle power storage device (such as a secondary battery) can be used as the battery 41. The detector 41a includes various sensors for detecting the state of the battery 41 (for example, temperature, current, and voltage). The detector 41a may also include a strain sensor for detecting the degree of strain of the battery casing. The battery ECU 41b is a controller having a processor and a storage device. The storage device of the battery ECU 41b pre-stores the identification information (battery ID) of the battery 41. In addition, the battery electronic control unit (ECU: Electronic Control Unit) 41b records the detection results obtained by the detector 41a in the storage device in sequence by associating them with the detection time.

[0032] The vehicle 40 further includes a temperature control system 42 for adjusting the temperature of the battery 41. The temperature control system 42 includes at least one of a heating device and a cooling device. The temperature control system 42 can adjust the temperature of the battery 41 by circulating a heat medium (e.g., water, antifreeze, or gas) that performs heat exchange with the battery 41. The temperature control system 42 is controlled by, for example, the battery ECU 41b.

[0033] The vehicle 40 further includes an inlet 43a, a charger 43b, a charging relay 43c, a system main relay (SMR: System Main Relay) 43d, a vehicle drive device 44, a fuel tank 44a, a drive wheel 44b, a vehicle ECU 45, an HMI 46, and a communication device 47. The inlet 43a, the charger 43b, the charging relay 43c, and the SMR 43d are arranged on a charging line that guides power from outside the vehicle to the battery 41. In addition, the SMR 43d switches the connection / disconnection of the circuit connecting the vehicle drive device 44 to the battery 41. The charger 43b, the charging relay 43c, and the SMR 43d are controlled by, for example, the battery ECU 41b, respectively. The vehicle ECU 45 includes a processor 45a and a storage device 45b. The vehicle ECU 45 exchanges information with each of the battery ECU 41b, the HMI 46, and the communication device 47. The vehicle ECU 45 stores the battery ID received from the battery ECU 41b in the storage device 45b. In addition, the storage device 45b stores authentication information for user authentication in advance. The HMI 46 includes an input device and a display device. The HMI 46 may also include a touch panel display. The communication device 47 communicates with the outside of the vehicle. The communication device 47 includes a wireless communicator.

[0034] The vehicle drive device 44 is, for example, a drive device of a series-parallel hybrid mode. The vehicle drive device 44 includes a plurality of motor generators (MGs), a power control unit (PCU), a power distribution mechanism, and an internal combustion engine (engine). The PCU includes a power conversion circuit (e.g., an inverter) that functions as a drive circuit for each MG. The battery 41 is electrically connected to each MG via the PCU. The plurality of MGs include, for example, an MG1 for engine starting and power generation and an MG2 for driving and regenerative braking. The internal combustion engine generates torque using fuel (e.g., gasoline, light oil, or hydrogen) supplied from a fuel tank 44a. MG2 generates torque using electricity supplied from the battery 41. MG1 is configured to generate electricity using the torque output by the internal combustion engine or MG2. The power distribution mechanism includes planetary gears that are respectively connected to MG1, MG2, the internal combustion engine, and the drive wheel 44b. The torque generated by the internal combustion engine or MG2 is transmitted to the drive wheel 44b via the power distribution mechanism. Figure 3 Only one drive wheel 44b is shown, but the number of drive wheels is arbitrary. The drive mode can be any one of front-wheel drive, rear-wheel drive, and four-wheel drive. The vehicle drive device 44 (PCU, internal combustion engine, etc.) is controlled by the vehicle ECU 45. The vehicle ECU 45 functions as an engine ECU that controls the internal combustion engine.

[0035] The structure of the vehicle drive device 44 is not limited to the above description and can be changed appropriately. The number of MGs is not limited to two and is arbitrary, and can also be one. The vehicle drive device 44 can also be a series hybrid drive device. The internal combustion engine can also be dedicated to power generation. The vehicle 40 can also be a BEV (battery electric vehicle) or a range extender EV (Range Extender EV).

[0036] The user of the vehicle 40 can input instructions or requests to the vehicle ECU 45 through the HMI 46. The storage device 45b stores a replacement signal flag in advance. The replacement signal flag indicates the replacement signal ( Figure 4 ) is permitted. When the replacement signal flag is enabled, the replacement signal is permitted. When the replacement signal flag is disabled, the replacement signal is prohibited. HMI46 accepts input for requesting permission to send the replacement signal (permission request) and input for requesting prohibition of the replacement signal (prohibition request). When HMI46 receives a permission request or a prohibition request, it starts Figure 3 Hereinafter, each step in the flowchart is simply referred to as "S". The process flow of S101 to S103 is executed by the vehicle ECU 45 (control device).

[0037] In S101, the vehicle ECU 45 requests the authentication information related to the user authentication from the administrator (user) of the vehicle 40. The vehicle ECU 45 may also request the authentication information related to the user authentication from the mobile terminal 80. The user may input the authentication information to the mobile terminal 80 according to the request. In the following S102, the vehicle ECU 45 compares the authentication information received from the user (mobile terminal 80) with the authentication information pre-registered in the storage device 45b, thereby judging whether the user authentication is successful or not. As examples of authentication information, user ID, authentication code, and biometric information (e.g., fingerprint or facial information) are cited. In the case of successful user authentication ("Yes" in S102), in S103, the vehicle ECU 45 changes the replacement signal flag to enable or disable according to the permission request or prohibition request from the administrator (user) of the vehicle 40. On the other hand, in the case of failed user authentication ("No" in S102), the replacement signal flag is not changed, and the processing flow ends. As described above, the vehicle ECU 45 is configured to perform the following processes: authenticating the manager of the vehicle 40 (S101, S102); and switching the permission / prohibition of the transmission of the replacement signal according to the request from the manager of the vehicle 40 (S103). According to such a configuration, the vehicle manager can permit the transmission of the replacement signal only when necessary. For example, the vehicle manager can also permit the transmission of the replacement signal before requesting the repair of the power storage device.

[0038] Furthermore, an electrified vehicle (xEV) such as a PHEV is equipped with a power storage device (e.g., battery 41) for driving. Generally speaking, a power storage device for driving is large-capacity and expensive. Even if such a large-capacity power storage device fails, it will not be replaced immediately, but will be repaired if it can be repaired, and replaced only when it deteriorates to the point where it cannot be repaired. However, in the case where the vehicle manager entrusts the repair of the power storage device mounted on the vehicle to a repair merchant, the repair merchant may replace the power storage device against the intention of the vehicle manager.

[0039] Therefore, in this embodiment, the user of the vehicle 40 leaves the vehicle 40 with the replacement signal flag turned on at the repair shop 300. Then, the user of the vehicle 40 entrusts the repair of the battery 41 to the repair shop 300. In the repair shop 300, the vehicle 40 repeatedly performs the following steps. Figure 4 The processing flow shown in FIG. 1 can also be started when the vehicle system is restarted when the power supply of the vehicle system is disconnected. Figure 4 Hereinafter, the battery pack BP and the battery 41 included in the vehicle 40 at the time when the vehicle 40 is stored in the repair shop 300 are referred to as “battery pack BP1 ” and “battery B1 ”, respectively.

[0040] Figure 4 1 is a flowchart showing the processing of the management method according to the present embodiment. The processing flow of S11 to S15 is executed by the vehicle ECU 45 (control device).

[0041] Reference Figure 4 In S11, the vehicle ECU 45 determines whether the replacement signal flag in the storage device 45b is enabled. When the replacement signal flag becomes enabled ("Yes" in S11), in S12, the vehicle ECU 45 determines whether the battery pack BP1 (including the battery B1) has been replaced. The vehicle ECU 45 may also determine whether the battery pack BP1 has been replaced based on the communication status (for example, interruption and restart) with the battery ECU 41b. Alternatively, the vehicle ECU 45 may also determine whether the battery pack BP1 has been replaced based on information from the battery ECU 41b (for example, the detection result obtained by the detector 41a).

[0042] When the vehicle ECU 45 senses the replacement of the battery pack BP1 ("Yes" in S12), the vehicle ECU 45 determines in S13 whether the battery has been replaced and the battery ID has been rewritten. Hereinafter, the battery pack BP and the battery 41 installed in the vehicle 40 instead of the battery pack BP1 and the battery B1 by replacing the battery pack are referred to as "battery pack BP2" and "battery B2", respectively. The battery B1 and the battery B2 are respectively equivalent to an example of the "first power storage device" and the "second power storage device" of the present disclosure.

[0043] Usually, corresponding to the replacement of the battery pack, the subscriber identity module (SIM) information stored in the vehicle ECU45 (storage device 45b) is rewritten. Hereinafter, such rewriting of SIM information is also referred to as "ECU rewriting". The SIM information includes the battery ID. Specifically, when the battery pack BP1 is replaced with the battery pack BP2, the battery ECU41b of the battery pack BP2 sends the identification information of the battery B2 to the vehicle ECU45, and the identification information of the battery B1 stored in the storage device 45b is rewritten with the identification information of the battery B2. However, ECU rewriting may not always be successful, and ECU rewriting may sometimes fail for some reason. In S13, the vehicle ECU45 determines whether the ECU rewrite is successful.

[0044] When the battery ID stored in the storage device 45b is rewritten as the identification information of the battery B2 ("Yes" in S13), in S14, the vehicle ECU 45 sends a first replacement signal to the server 50 and the mobile terminal 80, respectively. The first replacement signal includes the identification information of the vehicle 40, the identification information of the battery B1, and the identification information of the battery B2. When the battery ID stored in the storage device 45b is not rewritten as the identification information of the battery B2 ("No" in S13), in S15, the vehicle ECU 45 sends a second replacement signal to the server 50 and the mobile terminal 80, respectively. The second replacement signal includes the identification information of the vehicle 40 and the identification information of the battery B1. The first replacement signal and the second replacement signal are signals that notify that the power storage device mounted on the vehicle 40 has been replaced. The first replacement signal and the second replacement signal are respectively equivalent to an example of the "first signal" and the "third signal" of the present disclosure.

[0045] The mobile terminal 80 is carried by the manager (user) of the vehicle 40. When receiving the first replacement signal or the second replacement signal, the mobile terminal 80 reports to the user that the power storage device mounted on the vehicle 40 has been replaced. The mobile terminal 80 may also display a message notifying that the power storage device has been replaced. Through such a report, the vehicle manager can know that the power storage device of the vehicle 40 stored in the repair shop 300 has been replaced against the vehicle manager's intention.

[0046] It should be noted that when the replacement signal flag is turned off (No in S11), the processing after S12 is not executed. In this case, even if the battery B1 is replaced with another battery, the vehicle 40 does not send a replacement signal (the first replacement signal and the second replacement signal). The vehicle user turns off the replacement signal flag, thereby freely performing battery replacement.

[0047] When receiving the first replacement signal or the second replacement signal, the server 50 starts the processing flow of S21 to S26 described below. In S21, the server 50 requests the server 20 for the degree of degradation of the battery B1. The server 50 sends the identification information of the vehicle 40 and the identification information of the battery B1 to the server 20. The battery B1 is equivalent to the power storage device removed from the vehicle 40 by the battery replacement in the repair shop 300. The server 20 estimates the current degree of degradation of the battery B1 (equivalent to the degree of degradation at the time of replacement) based on the usage history information of the battery B1 recorded in the distributed ledger (database) according to the request from the server 50 (S21), and sends the estimated degree of degradation to the server 50.

[0048] The usage history information of the battery B1 includes data indicating the state of the battery B1 during the use of the battery B1 (for example, the detection result obtained by the detector 41a). The server 20 uses such data to estimate the degree of degradation of the battery B1. The usage history information may also include at least one of current data, voltage data, power storage data, temperature data, communication data, shell strain degree, and the degree of degradation of accessories. The server 20 may also calculate the degree of degradation of the battery B1 based on at least one of the internal resistance of the battery B1, the capacity retention rate of the battery B1, the degree of physical degradation (strain degree) of the shell of the battery B1, the communication level related to the system that monitors the battery B1 (communication instability, communication interruption, etc.), the degree of degradation of the electrical components of the battery B1 (disconnection, deformation of the busbar, etc.), and the degree of degradation of the environmental components of the battery B1 (poor control, failure, etc.). In this embodiment, the detector 41a and the battery ECU 41b each function as a system that monitors the battery B1. The components corresponding to the temperature control system 42 (temperature control components in the battery pack BP1) function as environmental components of the battery B1. The server 20 may also score the degree of degradation according to each evaluation item related to the degree of degradation of the battery B1, and treat the total value of the score of each of these evaluation items as the degree of degradation of the battery B1 (evaluation result). The evaluation items may be the above-mentioned six items (internal resistance, capacity retention rate, housing, communication level, electrical components, and environmental components), or two or more and less than five items selected from the above-mentioned six items, or one item (for example, internal resistance or capacity retention rate). It should be noted that the method for determining the degree of degradation of the battery B1 is not limited to the above-mentioned method, and any method may be used.

[0049] In the next S22, the server 50 uses the degree of deterioration of the battery B1 obtained from the server 20 to determine whether the battery B1 needs to be replaced. In detail, when the degree of deterioration of the battery B1 is greater than a prescribed reference value, the server 50 determines that the battery B1 needs to be replaced, and when the degree of deterioration of the battery B1 is less than or equal to the above-mentioned prescribed reference value, the server 50 determines that the battery B1 does not need to be replaced. Alternatively, in a method of evaluating the degree of deterioration of the battery B1 using multiple items (for example, the aforementioned six items), the server 50 determines that the battery B1 needs to be replaced even if the degree of deterioration of the battery B1 exceeds the prescribed reference value in one item. The server 50 can easily make an appropriate judgment on whether the replacement of the power storage device is necessary by using the degree of deterioration of the battery B1 as described above.

[0050] If it is determined that the battery B1 does not need to be replaced ("No" in S22), in S23, the server 50 sends a first request signal to the management terminal 30. The first request signal is a signal requesting that the battery B2 mounted on the vehicle 40 be restored to the battery B1. The first request signal includes the identification information of the vehicle 40 and the identification information of the battery B1. When the management terminal 30 receives the first request signal, for example, Figure 4 As shown, the identification information of the vehicle 40 and the identification information of the battery B1 are displayed, and a message urging the restoration of the power storage device of the vehicle 40 to the battery B1 is displayed. By such control, when an unnecessary power storage device is replaced, the repair shop can be urged to restore the power storage device of the vehicle 40 to its original state. The first request signal is an example of the "second signal" of the present disclosure.

[0051] When it is determined that battery B1 needs to be replaced ("Yes" in S22), in S24, the server 50 determines whether a second replacement signal (S15) is received from the vehicle 40. When the server 50 receives the second replacement signal ("Yes" in S24), in S25, the server 50 sends a second request signal to the management terminal 30. The second request signal is a signal requesting rewriting of the battery ID (identification information of the power storage device) stored in the vehicle ECU 45. The second request signal includes identification information of the vehicle 40 and identification information of the battery B1. When the second request signal is received, the management terminal 30, for example, Figure 4 As shown, the identification information of the vehicle 40 is displayed, and a message urging the battery ID to be rewritten in coordination with the power storage device (battery B2) mounted on the vehicle 40 is displayed. According to such control, in a case where the identification information of the power storage device is not rewritten despite the required replacement of the power storage device, it is possible to request the repair business to rewrite the identification information of the power storage device. The repair business can use a scan tool to rewrite the ECU. The control device of the vehicle 40 (vehicle ECU45) can easily correctly identify the power storage device mounted on the vehicle 40 based on the identification information of the power storage device. The second request signal is equivalent to an example of the "fourth signal" of the present disclosure.

[0052] On the other hand, when the server 50 receives the first replacement signal (No in S24), in S26, the server 50 requests the server 20 for information related to the power storage device (battery B2) mounted on the vehicle 40. The server 50 sends the identification information of the vehicle 40 and the identification information of the battery B2 to the server 20. The server 20 sends the information related to the battery B2 (for example, the technical specification information of the battery B2 and the control program suitable for the battery B2) to the server 50 in accordance with the request from the server 50. Then, the server 50 sends the information acquired from the server 20 to the vehicle 40.

[0053] When any one of the processes in S23, S25, and S26 is executed, the processing flow of S21 to S26 ends. It should be noted that, in the case where the repair shop restores battery B2 to battery B1 according to the request of S23, it is judged as "yes" in S12, and a replacement signal (first replacement signal or second replacement signal) is sent from the vehicle 40 to the server 50 again. Alternatively, when the replacement signal is received, the server 50 starts the processing flow of S21 to S26. However, in S22, it is determined that the battery needs to be replaced. S21 can also be skipped. In S25, a request is made to rewrite the ECU in coordination with battery B1. In addition, in S26, information related to battery B1 is requested.

[0054] In S23 and S25, the server 50 may send the first request signal and the second request signal to the vehicle 40 instead of or in addition to the management terminal 30. For example, when the vehicle 40 receives the first request signal or the second request signal in the repair shop 300, the vehicle ECU 45 may start the following steps: Figure 5 The processing flow of S31 to S35 is shown. Figure 5 4 is a flowchart showing the process of the notification control executed by the vehicle 40 .

[0055] Reference Figure 5 In S31, the vehicle ECU 45 limits the use of the battery 41. For example, the vehicle ECU 45 sets an output limit for the battery 41 on the battery ECU 41b. As a result, the battery ECU 41b is in an output limit state. When the discharge power of the battery 41 exceeds a specified value (hereinafter referred to as "limit value U"), the battery ECU 41b in the output limit state instructs the vehicle ECU 45 that the output of the battery 41 is reduced. The limit value U is set, for example, to a degree at which electric driving other than slow driving is prohibited. However, the restriction control is not limited to the above scheme. For example, during the period of restriction on the use of the battery 41, the SMR 43d may be maintained in a cut-off state.

[0056] In the next S32, the vehicle ECU 45 causes the HMI 46 to perform a report process for urging the operation according to the first request signal or the second request signal. When the vehicle 40 receives the first request signal, the HMI 46 displays, for example, a screen Sc1. The screen Sc1 includes a message urging the battery replacement requested by the first request signal. When the vehicle 40 receives the second request signal, the HMI 46 displays, for example, a screen Sc2. The screen Sc2 includes a message urging the ECU rewrite requested by the second request signal.

[0057] In the next S33, the vehicle ECU 45 determines whether the operation according to the first request signal or the second request signal received by the vehicle 40 has been completed. While the operation is not completed ("No" in S33), S31 to S33 are repeated. On the other hand, when it is determined that the operation is completed ("Yes" in S33), in S34, the vehicle ECU 45 releases the usage restriction of S31. Next, in S35, the vehicle ECU 45 requests the server 20 for information related to the power storage device (battery B2) mounted on the vehicle 40. The vehicle ECU 45 sends the identification information of the vehicle 40 and the identification information of the battery B2. The server 20 sends information related to the battery B2 (technical specification information, control program, etc.) to the vehicle 40 in response to the request from the vehicle 40.

[0058] As described above, the control device (vehicle ECU 45) of the vehicle 40 of the present embodiment stores the identification information (battery ID) of the first power storage device when the first power storage device is mounted on the vehicle 40 as the power storage device of the vehicle 40. Figure 3 Then, when the first power storage device is replaced by the second power storage device and the identification information of the first power storage device stored in the control device is rewritten as the identification information of the second power storage device, the control device (vehicle ECU 45) sends a first replacement signal (first signal) to the outside of the vehicle to notify that the power storage device has been replaced ( Figure 4 Such a vehicle can notify the outside of the vehicle that the power storage device has been replaced.

[0059] The management method of this embodiment includes Figure 3 to Figure 5 Each process shown. Each process is executed by one or more processors executing a program stored in one or more memories. However, these processes can also be executed by dedicated hardware (electronic circuits) instead of software. Server 20 can also be used instead of server 50 to execute Figure 4 The process flow of S21 to S26 is shown.

[0060] The vehicle 40 is an example of a "mobile body" in the present disclosure. The mobile body may also be a means of transportation other than a car (railway vehicle, agricultural machinery, construction machinery, ship, airplane, amphibious machine, etc.) or an unmanned mobile body (unmanned transport vehicle, walking robot, drone, robot cleaner, etc.).

[0061] The embodiments disclosed this time should be considered in all respects as illustrative and non-restrictive. The scope of the present invention is indicated not by the description of the above embodiments but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

Claims

1. A mobile body comprising a power storage device and a control device, wherein: When a first power storage device is mounted on the mobile body as the power storage device, the control device stores identification information of the first power storage device. The control device is configured to, when the first power storage device is replaced with a second power storage device and identification information of the first power storage device stored in the control device is rewritten with identification information of the second power storage device, send a first signal to the outside of the moving body notifying that the power storage device has been replaced.

2. The moving object according to claim 1, wherein: The control device is configured to perform the following processing: authenticating the manager of the mobile object; and Permission / prohibition of transmission of the first signal is switched according to a request from the manager.

3. A management system comprising the mobile object and the mobile terminal according to claim 1 or 2, wherein: When receiving the first signal, the mobile terminal reports that the power storage device has been replaced.

4. The management system according to claim 3, wherein: The management system also has: a database storing usage history information of the power storage device acquired from the mobile object; as well as server, The server is configured to perform the following processing upon receiving the first signal: acquiring a degree of degradation of the first power storage device estimated based on the usage history information; using the degree of degradation to determine whether replacement of the first power storage device is necessary; as well as When it is determined that the first power storage device does not need to be replaced, a second signal requesting that the second power storage device mounted on the mobile body be restored to the first power storage device is transmitted.

5. The management system according to claim 4, wherein: The control device is configured to, when the first power storage device is replaced with the second power storage device and the identification information of the first power storage device stored in the control device is not rewritten with the identification information of the second power storage device, send a third signal notifying that the power storage device has been replaced, The server is configured to perform the following processing when receiving the third signal: acquiring a degree of degradation of the first power storage device estimated based on the usage history information; using the degree of degradation to determine whether replacement of the first power storage device is necessary; as well as When it is determined that the first power storage device needs to be replaced, a fourth signal is transmitted to request rewriting of identification information of the power storage device stored in the control device.

Images