Moving body, management system

Abstract

To provide a moving body capable of notifying the outside of the moving body that the power storage unit installed in the moving body has been replaced.SOLUTION: The moving body includes a power storage unit and a control unit. The control unit is configured so as to, when a first power storage unit is installed in the moving body as the power storage unit, store a piece of identification information of the first power storage unit. The control unit is also configured so as to, when the first power storage unit is replaced with a second power storage unit and when the identification information of the first power storage unit stored in the control unit is rewritten to that of the second power storage unit, transmit a first signal to the outside of the moving body to inform that the power storage unit has been replaced (S14).SELECTED DRAWING: Figure 4

Description

[Technical field]

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

[0002] Japanese Patent Publication No. 2017-189032 (Patent Document 1) 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 are consistent when an auxiliary battery that supplies power to a vehicle control unit and a battery control unit is detached. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-189032 A Summary of the Invention [Problem to be solved by the invention]

[0004] For example, an electrically powered vehicle such as an electric car includes a power storage device (e.g., a drive battery) for driving. In general, the power storage device for driving has a large capacity and is expensive. Such a large capacity power storage device is not immediately replaced even if it breaks down, but is repaired if possible. However, when a vehicle manager requests a repairer to repair the power storage device mounted on the vehicle, it is possible that the repairer will replace the power storage device against the intention of the vehicle manager.

[0005] The present disclosure has been made to solve the above-mentioned problems, and has an object to notify the outside of a mobile body that a power storage device mounted on the mobile body has been replaced. [Means for solving the problem]

[0006] A mobile body according to an embodiment of the present disclosure includes a power storage device and a control device. The control device stores identification information of a first power storage device when the first power storage device is mounted on the mobile body as a power storage device. The control device is configured to transmit a first signal indicating that the power storage device has been replaced to an outside of the mobile body 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 to the identification information of the second power storage device. Effect of the Invention

[0007] According to the present disclosure, it becomes possible to notify the outside of the mobile body that a power storage device mounted on the mobile body has been replaced. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an overview of a management system according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram showing a configuration of the information platform shown in FIG. [Diagram 3] 1 is a diagram illustrating a configuration of a moving body according to an embodiment of the present disclosure. [Figure 4] 1 is a flowchart illustrating a management method according to an embodiment of the present disclosure. [Diagram 5] 5 is a flowchart showing a process related to notification control executed by a moving object according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure will now be described in detail with reference to the accompanying drawings, in which the same or corresponding parts are designated by the same reference characters and will not be described repeatedly.

[0010] FIG. 1 is a diagram showing an overview of a management system according to this embodiment. The management system shown in FIG. 1 includes a management terminal 30, a plurality of vehicles 40, a server 50, data collection systems 100A to 100D, a plurality of dealers 110, a plurality of vehicle management devices 120, a plurality of exchange stations 130, a plurality of homes 140, a plurality of ESSs (Energy Storage Systems) 150, an information platform 200, and a repair shop 300. In this system, a plurality of power storage devices are distributed. Each power storage device is used sequentially by a plurality of users. For example, a power storage device used by a user may be provided to another user. Each power storage device is given unique identification information (hereinafter referred to as a "battery ID") so that each power storage device distributed in the system can be identified. In addition, owners and users of the power storage devices are registered in the information platform 200 and given unique identification information. In addition, the locations where the power storage devices are used (vehicle 40, house 140, ESS 150) and the locations where they are stored (exchange station 130, repair shop 300) are also registered in the information platform 200 and given unique identification information.

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

[0012] Dealer 110 includes scan tool 111 and dealer terminal 112 (e.g., a computer). Scan tool 111 acquires information (including a vehicle ID and a battery ID) from vehicles 40 that visit dealer 110 via wired communication. The information on vehicles 40 acquired by scan tool 111 is transmitted to dealer terminal 112. Dealer terminal 112 manages information for each vehicle by distinguishing them by vehicle ID.

[0013] The vehicle management device 120 includes a terminal (e.g., a computer) configured to be able to wirelessly communicate with a traveling or parked vehicle 40. The vehicle management device 120 acquires information (including a vehicle ID and a battery ID) from each of the multiple vehicles 40 via wireless communication. The vehicle management device 120 manages information about each vehicle by distinguishing them by their vehicle IDs.

[0014] The exchange station 130 is configured to store an exchange electric storage device and to exchange the electric storage device mounted on the vehicle 40. In detail, the exchange station 130 removes the electric storage device from the vehicle 40 and attaches another electric storage device (exchange electric storage device) to the vehicle 40.

[0015] The house 140 includes a solar power generation system and a stationary power storage system (home power storage system). The power storage system is configured to be capable of supplying power to the house 140. The power storage system can also store power generated by the solar power generation system.

[0016] The ESS150 is a stationary energy storage system that is larger than a residential energy storage system. The 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. The ESS150 can also store surplus electricity.

[0017] The repair factory 300 is configured to repair the power storage device. A broken power storage device is sent to the repair factory 300 and repaired at the repair factory 300. When a power storage device mounted on a vehicle 40 breaks down, a manager (user) of the vehicle 40 leaves the vehicle 40 at the repair factory 300. At the repair factory 300, the power storage device is repaired while still attached to the vehicle 40. The repair factory 300 is also configured to be able to store a plurality of power storage devices, and also functions as a warehouse. The management terminal 30 is installed in the repair factory 300, and manages information (inventory information) of each power storage device stored at the repair factory 300.

[0018] Each of the vehicle 40, the exchange station 130, the house 140, the ESS 150, and the repair shop 300 includes a BMS (Battery Management System). The BMS includes a detector that detects the state of the power storage device, and a controller that records the detection result by the detector in a storage device in association with the detection time. However, the BMS at the storage location may be omitted.

[0019] The data collection system 100A is configured to, for example, periodically collect information on the in-vehicle power storage device from each of the multiple dealers 110 (dealer terminals 112) and multiple vehicle management devices 120, and to organize the collected information into a database. The information on 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, respectively, by wired communication or wireless communication.

[0020] The data collection systems 100B, 100C, and 100D are configured to collect information on an exchange power storage device, information on a residential power storage device, and information on an ESS power storage device, respectively, and to organize the collected information into a database. The BMS in each of the exchange station 130, the home 140, and the ESS 150 transmits 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.

[0021] The information platform 200 includes nodes 10A, 10B, 10C, 10D, and 10E (e.g., computers) corresponding to the data collection systems 100A, 100B, 100C, and 100D, and the management terminal 30, respectively. The information platform 200 further includes 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 as appropriate. The information platform 200 manages information of each power storage device circulating within the system using a distributed ledger technology that uses, for example, a block chain (hereinafter, referred to as "BLC"). All information from the start of operation of the distributed ledger to the present is recorded in the distributed ledger. FIG. 2 is a diagram showing the configuration of the information platform 200.

[0022] 2, the node 10A includes a processor 11, a RAM (Random Access Memory) 12, an HMI (Human Machine Interface) 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. Although only the configuration of the node 10A is shown in FIG. 2, the other nodes 10B to 10E basically have the same configuration as the node 10A shown in FIG. 2.

[0023] The server 20 also holds a distributed ledger and functions as a node of the DLN. Information recorded in the distributed ledger is shared by all nodes of the DLN. The server 20 also functions as an analysis server that analyzes information added to the distributed ledger by the 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 the distributed ledger. The storage device 25 further stores information for information analysis (computation information).

[0024] The distributed ledger of each node of the DLN records information about each power storage device (hereinafter referred to as "battery information") circulating within the system. The battery information includes identification information of the power storage device (battery ID), identification information of the owner of the power storage device (owner ID), identification information of the user who used the power storage device (user ID), identification information of the place where the power storage device is used (e.g., vehicle ID), specification information of the power storage device, and usage history information of the power storage device. However, the battery information is not limited to these pieces of information, and may further include other information about the power storage device (e.g., material composition information, insurance contract information, performance evaluation information, and a control program).

[0025] When the data collection system 100A, 100B, 100C, 100D, or the management terminal 30 acquires new battery information, the corresponding node records a new block including the battery information in the distributed ledger. Specifically, the corresponding node generates transaction data including the battery information, the identification information (recorder ID) of the node, and the recording time. Next, the node records a new block including the generated transaction data and a hash value of past transaction data (previous block) in the distributed ledger. This updates the distributed ledger of each node in the DLN. Various pieces of information included in the new block are linked to each other.

[0026] The vehicle 40 is configured to be able to wirelessly communicate with each of the server 50 and the mobile terminal 80. The server 50 according to this embodiment is an external server equipped with a processor and a storage device. The server 50 provides a predetermined service (e.g., insurance service) using information (e.g., the degree of battery deterioration) obtained from the information platform 200. The mobile terminal 80 is a terminal that can be carried by the user of the vehicle 40. In this embodiment, a smartphone equipped with a touch panel display is adopted as the mobile terminal 80. The smartphone has a built-in computer and a speaker function. However, the present invention is not limited to this, and a wearable device, an electronic key, and the like can also be adopted as the mobile terminal 80.

[0027] The vehicle 40 is, for example, a PHEV (plug-in hybrid vehicle). The vehicle 40 includes a battery pack BP. FIG. 3 is a diagram showing a configuration of the vehicle 40. Referring to FIG. 3, the battery pack BP includes a battery 41, a detector 41a, and a battery ECU 41b. A known vehicle power storage device (for example, a secondary battery) can be adopted as the battery 41. The detector 41a includes various sensors that detect the state (for example, temperature, current, and voltage) of the battery 41. The detector 41a may include a distortion sensor that detects the degree of distortion of the battery case. The battery ECU 41b is a controller that includes a processor and a storage device. The storage device of the battery ECU 41b stores in advance identification information (battery ID) of the battery 41. The battery ECU 41b also sequentially records the detection results by the detector 41a in the storage device in association with the detection time. The ECU stands for Electronic Control Unit.

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

[0029] The vehicle 40 further includes an inlet 43a, a charger 43b, a charging relay 43c, an SMR (System Main Relay) 43d, a vehicle drive device 44, a fuel tank 44a, drive wheels 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 electric power from outside the vehicle to the battery 41. The SMR 43d also switches between connection and disconnection of an electric path connecting the vehicle drive device 44 and the battery 41. Each of the charger 43b, the charging relay 43c, and the SMR 43d is controlled by, for example, the battery ECU 41b. 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. The storage device 45b also stores authentication information for user authentication in advance. The HMI 46 includes an input device and a display device. The HMI 46 may include a touch panel display. The communication device 47 communicates with the outside of the vehicle. The communication device 47 includes a wireless communication device.

[0030] The vehicle drive device 44 is, for example, a series-parallel hybrid type drive device. The vehicle drive device 44 includes a plurality of MGs (Motor Generators), a PCU (Power Control Unit), a power split mechanism, and an internal combustion engine (engine). The PCU includes a power conversion circuit (for example, an inverter) and 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 start and power generation, and an MG2 for drive and regenerative braking. The internal combustion engine generates torque using fuel (for example, gasoline, diesel, or hydrogen) supplied from a fuel tank 44a. The MG2 generates torque using electric power supplied from the battery 41. The MG1 is configured to be able to generate electricity using the torque output by the internal combustion engine or the MG2. The power split mechanism includes planetary gears and is connected to each of the MG1, MG2, the internal combustion engine, and the drive wheels 44b. The torque generated by the internal combustion engine or the MG2 is transmitted to the drive wheels 44b via the power split mechanism. 3 shows only one drive wheel 44b, the number of drive wheels is arbitrary. The drive system may be any 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.

[0031] The configuration of the vehicle drive device 44 is not limited to the above and can be changed as appropriate. The number of MGs is not limited to two and is arbitrary, and may be one. The vehicle drive device 44 may be a series hybrid drive device. The internal combustion engine may be dedicated to power generation. The vehicle 40 may be a BEV (electric vehicle) or a range extender EV.

[0032] A user of the vehicle 40 can input an instruction or request to the vehicle ECU 45 through the HMI 46. The storage device 45b prestores an exchange signal flag. The exchange signal flag is a parameter indicating whether or not the transmission of an exchange signal (FIG. 4) described later is permitted. When the exchange signal flag is ON, it means that the transmission of the exchange signal is permitted. When the exchange signal flag is OFF, it means that the transmission of the exchange signal is prohibited. The HMI 46 accepts an input (permission request) for requesting permission to transmit the exchange signal and an input (prohibition request) for requesting prohibition of the transmission of the exchange signal. When the HMI 46 receives the permission request or the prohibition request, the process flow shown in FIG. 3 is started. In the following, each step in the flowchart is simply denoted as "S". The process flow of S101 to S103 is executed by the vehicle ECU 45 (control device).

[0033] In S101, the vehicle ECU 45 requests authentication information related to user authentication from the administrator (user) of the vehicle 40. The vehicle ECU 45 may request the mobile terminal 80. In response to this request, the user may input the authentication information to the mobile terminal 80. In the following S102, the vehicle ECU 45 determines whether the user authentication is successful by collating the authentication information received from the user (mobile terminal 80) with authentication information previously registered in the storage device 45b. Examples of the authentication information include a user ID, an authentication code, and biometric information (e.g., fingerprint or face information). If the user authentication is successful (YES in S102), the vehicle ECU 45 changes the exchange signal flag to ON or OFF in S103 in response to a permission request or a prohibition request from the administrator (user) of the vehicle 40. On the other hand, if the user authentication is unsuccessful (NO in S102), the exchange signal flag is not changed and the process flow ends. As described above, the vehicle ECU 45 is configured to authenticate the manager of the vehicle 40 (S101, S102) and to switch between permission and prohibition of transmission of the replacement signal in response to a request from the manager of the vehicle 40 (S103). This configuration allows the vehicle manager to permit transmission of the replacement signal only when necessary. The vehicle manager may permit transmission of the replacement signal, for example, before requesting repair of the power storage device.

[0034] Incidentally, an electric vehicle (xEV) such as a PHEV includes a power storage device (for example, a battery 41) for driving. In general, a power storage device for driving has a large capacity and is expensive. Such a large-capacity power storage device is not immediately replaced even if it breaks down, but is repaired if possible, and is replaced if the deterioration has progressed to the point where it cannot be repaired. However, when a vehicle manager requests a repairer to repair a power storage device mounted on a vehicle, it may happen that the repairer replaces the power storage device against the intention of the vehicle manager.

[0035] Therefore, in this embodiment, the user of the vehicle 40 leaves the vehicle 40 with the replacement signal flag set to ON at the repair factory 300. Then, the user of the vehicle 40 requests the repair factory 300 to repair the battery 41. At the repair factory 300, the vehicle 40 repeatedly executes the process flow shown in FIG. 4 described below. If the power supply of the vehicle system is turned off, the process flow shown in FIG. 4 may be started when the vehicle system is restarted. Hereinafter, the battery pack BP and the battery 41 included in the vehicle 40 at the time when the vehicle 40 is left at the repair factory 300 will be referred to as the "battery pack BP1" and the "battery B1", respectively.

[0036] 4 is a flowchart showing the process of the management method according to this embodiment. The process flow of S11 to S15 is executed by the vehicle ECU 45 (control device).

[0037] 4, in S11, the vehicle ECU 45 determines whether or not a replacement signal flag in the storage device 45b is ON. If the replacement signal flag is ON (YES in S11), the vehicle ECU 45 determines whether or not the battery pack BP1 (including the battery B1) has been replaced in S12. The vehicle ECU 45 may determine whether or not the battery pack BP1 has been replaced based on the state of communication with the battery ECU 41b (e.g., interruption and resumption). Alternatively, the vehicle ECU 45 may determine whether or not the battery pack BP1 has been replaced based on information from the battery ECU 41b (e.g., the detection result by the detector 41a).

[0038] When the vehicle ECU 45 detects the replacement of the battery pack BP1 (YES in S12), the vehicle ECU 45 determines in S13 whether or not the battery ID has been rewritten together with the battery replacement. Hereinafter, the battery pack BP and the battery 41 installed in the vehicle 40 in place of the battery pack BP1 and the battery B1 due to the battery pack replacement will be referred to as "battery pack BP2" and "battery B2", respectively. The batteries B1 and B2 correspond to examples of the "first power storage device" and the "second power storage device" according to the present disclosure, respectively.

[0039] Usually, when the battery pack is replaced, SIM (Subscriber Identify Module) information stored in the vehicle ECU 45 (storage device 45b) is rewritten. Hereinafter, such rewriting of SIM information is also referred to as "ECU rewriting." The SIM information includes a battery ID. Specifically, when the battery pack BP1 is replaced with the battery pack BP2, the battery ECU 41b of the battery pack BP2 transmits the identification information of the battery B2 to the vehicle ECU 45, and the identification information of the battery B1 stored in the storage device 45b is rewritten to the identification information of the battery B2. However, the ECU rewriting is not always successful, and the ECU rewriting may fail due to some cause. In S13, the vehicle ECU 45 determines whether the ECU rewriting was successful or not.

[0040] When the battery ID stored in the storage device 45b has been rewritten to the identification information of battery B2 (YES in S13), the vehicle ECU 45 transmits a first exchange signal to each of the server 50 and the mobile terminal 80 in S14. The first exchange signal includes the identification information of the vehicle 40, the identification information of battery B1, and the identification information of battery B2. When the battery ID stored in the storage device 45b has not been rewritten to the identification information of battery B2 (NO in S13), the vehicle ECU 45 transmits a second exchange signal to each of the server 50 and the mobile terminal 80 in S15. The second exchange signal includes the identification information of the vehicle 40 and the identification information of battery B1. Each of the first and second exchange signals is a signal that notifies that the power storage device mounted on the vehicle 40 has been replaced. The first exchange signal and the second exchange signal are examples of the "first signal" and the "third signal" according to the present disclosure, respectively.

[0041] The mobile terminal 80 is carried by the manager (user) of the vehicle 40. When the mobile terminal 80 receives the first or second replacement signal, it notifies the user that the power storage device mounted on the vehicle 40 has been replaced. The mobile terminal 80 may display a message notifying that the power storage device has been replaced. The vehicle manager can learn from this notification that the power storage device of the vehicle 40 left at the repair shop 300 has been replaced against the intention of the vehicle manager.

[0042] When the replacement signal flag is OFF (NO in S11), the processes in S12 and after are not executed. In this case, even if battery B1 is replaced with another battery, vehicle 40 does not transmit a replacement signal (first and second replacement signals). By turning OFF the replacement signal flag, the vehicle user can freely replace the battery.

[0043] When the server 50 receives the first or second replacement signal, it starts the process flow of S21 to S26 described below. In S21, the server 50 requests the server 20 for the deterioration degree of battery B1. The server 50 transmits identification information of the vehicle 40 and identification information of battery B1 to the server 20. Battery B1 corresponds to a power storage device removed from the vehicle 40 due to battery replacement at the repair factory 300. In response to the request from the server 50 (S21), the server 20 estimates the current deterioration degree of battery B1 (corresponding to the deterioration degree at the time of replacement) based on the usage history information of battery B1 recorded in a distributed ledger (database), and transmits the estimated deterioration degree to the server 50.

[0044] The use history information of the battery B1 includes data indicating the state of the battery B1 during the use period of the battery B1 (for example, a detection result by the detector 41a). The server 20 estimates the deterioration degree of the battery B1 using such data. The use history information may include at least one of current data, voltage data, stored power data, temperature data, communication data, a case distortion degree, and a deterioration degree of an accessory. The server 20 may obtain the deterioration degree of the battery B1 based on at least one of the internal resistance of the battery B1, the capacity maintenance rate of the battery B1, the physical deterioration degree (distortion degree) of the case of the battery B1, the communication level (communication instability, communication interruption, etc.) regarding the system monitoring the battery B1, the deterioration degree of the electric parts of the battery B1 (disconnection, deformation of the bus bar, etc.), and the deterioration degree of the environmental parts of the battery B1 (control malfunction, failure, etc.). In this embodiment, each of the detector 41a and the battery ECU 41b functions as a system monitoring the battery B1. The parts corresponding to the temperature adjustment system 42 (the temperature adjustment parts in the battery pack BP1) function as the environmental parts of the battery B1. The server 20 may score the degree of deterioration for each evaluation item related to the deterioration degree of the battery B1, and may treat the total value of the points for each evaluation item as the deterioration degree (evaluation result) of the battery B1. The evaluation items may be the above-mentioned six items (internal resistance, capacity maintenance rate, case, communication level, electrical parts, and environmental parts), or may be two or more and five or less items selected from the above-mentioned six items, or may be one item (for example, internal resistance or capacity maintenance rate). Note that the method of determining the deterioration degree of the battery B1 is not limited to the above-mentioned method, and any method may be adopted.

[0045] In the next S22, the server 50 uses the deterioration degree of the battery B1 acquired from the server 20 to determine whether or not the battery B1 needed to be replaced. In particular, the server 50 determines that the battery B1 needed to be replaced if the deterioration degree of the battery B1 is greater than a predetermined reference value, and determines that the battery B1 needed to be replaced if the deterioration degree of the battery B1 is less than the above-mentioned predetermined reference value. In a form in which the deterioration degree of the battery B1 is evaluated based on a plurality of items (for example, the above-mentioned six items), the server 50 may determine that the battery B1 needed to be replaced if the deterioration degree of the battery B1 in even one item exceeds a predetermined reference value. By using the deterioration degree of the battery B1 as described above, the server 50 can easily appropriately determine whether or not the power storage device needs to be replaced.

[0046] When it is determined that the replacement of battery B1 was unnecessary (NO in S22), server 50 transmits a first request signal to management terminal 30 in S23. The first request signal is a signal requesting that battery B2 mounted on vehicle 40 be returned to battery B1. The first request signal includes identification information of vehicle 40 and identification information of battery B1. When management terminal 30 receives the first request signal, it displays the identification information of vehicle 40 and the identification information of battery B1, as shown in FIG. 4, for example, and displays a message urging the user to return the power storage device of vehicle 40 to battery B1. By such control, when an unnecessary replacement of a power storage device has been performed, it is possible to urge the repairer to return the power storage device of vehicle 40 to its original state. The first request signal corresponds to an example of a "second signal" according to the present disclosure.

[0047] When it is determined that the battery B1 needs to be replaced (YES in S22), the server 50 determines in S24 whether or not a second replacement signal (S15) has been received from the vehicle 40. When the server 50 receives the second replacement signal (YES in S24), the server 50 transmits a second request signal to the management terminal 30 in S25. 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 the identification information of the vehicle 40 and the identification information of the battery B1. When the management terminal 30 receives the second request signal, it displays the identification information of the vehicle 40 as shown in FIG. 4, for example, and displays a message prompting the user to rewrite the battery ID to match the power storage device (battery B2) attached to the vehicle 40. According to this control, when the identification information of the power storage device has not been rewritten despite the necessary replacement of the power storage device, it is possible to request the repairer to rewrite the identification information of the power storage device. The repairer may use a scan tool to rewrite the ECU. Based on the identification information of the power storage device, the control device (vehicle ECU 45) of vehicle 40 can easily correctly recognize the power storage device mounted on vehicle 40. The second request signal corresponds to an example of a "fourth signal" according to the present disclosure.

[0048] On the other hand, when the server 50 receives the first exchange signal (NO in S24), the server 50 requests information about the power storage device (battery B2) attached to the vehicle 40 from the server 20 in S26. The server 50 transmits identification information of the vehicle 40 and identification information of battery B2 to the server 20. In response to the request from the server 50, the server 20 transmits information about battery B2 (e.g., specification information of battery B2 and a control program suitable for battery B2) to the server 50. Then, the server 50 transmits the information obtained from the server 20 to the vehicle 40.

[0049] When any one of the processes of S23, S25, and S26 is executed, the process flow of S21 to S26 ends. If the repairer returns battery B2 to battery B1 in response to the request of S23, YES may be determined in S12, and a replacement signal (first or second replacement signal) may be transmitted again from vehicle 40 to server 50. When server 50 receives the replacement signal, it may start the process flow of S21 to S26. However, in S22, it is determined that battery replacement was necessary. S21 may be skipped. In S25, a request is made to rewrite the ECU in accordance with battery B1. In addition, in S26, information on battery B1 is requested.

[0050] The server 50 may transmit a first request signal and a second request signal to the vehicle 40 in S23 and S25, respectively, instead of or in addition to the management terminal 30. For example, when the vehicle 40 receives the first or second request signal at the repair shop 300, the vehicle ECU 45 may start a process flow of S31 to S35 shown in Fig. 5, which will be described below. Fig. 5 is a flowchart showing the process related to the notification control executed by the vehicle 40.

[0051] With reference to FIG. 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 in the battery ECU 41b. This causes the battery ECU 41b to enter an output limited state. When the discharge power of the battery 41 exceeds a predetermined value (hereinafter, referred to as "limit value U"), the battery ECU 41b in the output limited state instructs the vehicle ECU 45 to reduce the output of the battery 41. The limit value U is set to a level at which electric traveling other than slow driving is prohibited, for example. However, the limit control is not limited to the above mode. For example, the SMR 43d may be maintained in a cut-off state while the use of the battery 41 is being restricted.

[0052] In the next S32, the vehicle ECU 45 causes the HMI 46 to execute a notification process that prompts the user to perform an operation in accordance with the first or 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 that prompts the user to replace the battery 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 that prompts the user to rewrite the ECU requested by the second request signal.

[0053] In the next S33, the vehicle ECU 45 determines whether the work according to the first or second request signal received by the vehicle 40 has been completed. While the work is not completed (NO in S33), S31 to S33 are repeated. On the other hand, when it is determined that the work is completed (YES in S33), the vehicle ECU 45 releases the usage restriction of S31 in S34. Next, in S35, the vehicle ECU 45 requests information about the power storage device (battery B2) attached to the vehicle 40 from the server 20. The vehicle ECU 45 transmits identification information of the vehicle 40 and identification information of battery B2. In response to the request from the vehicle 40, the server 20 transmits information about battery B2 (such as specification information and a control program) to the vehicle 40.

[0054] As described above, the control device (vehicle ECU 45) of vehicle 40 according to this embodiment stores identification information (battery ID) of the first power storage device when the first power storage device is mounted on vehicle 40 as the power storage device of vehicle 40 (FIG. 3). Then, 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 to the identification information of the second power storage device, the control device (vehicle ECU 45) transmits a first replacement signal (first signal) to the outside of the vehicle notifying that the power storage device has been replaced (S14 in FIG. 4). Such a vehicle can notify the outside of the vehicle that the power storage device has been replaced.

[0055] The management method according to this embodiment includes each process shown in Fig. 3 to Fig. 5. Each process is performed by one or more processors executing a program stored in one or more memories. However, these processes may be performed by dedicated hardware (electronic circuitry) instead of software. Server 20 may execute the process flow of S21 to S26 shown in Fig. 4 instead of server 50.

[0056] The vehicle 40 corresponds to an example of a "moving body" according to the present disclosure. The moving body may be a vehicle other than an automobile (railroad vehicle, agricultural machinery, construction machinery, ship, airplane, amphibious aircraft, etc.), or an unmanned moving body (automated guided vehicle, walking robot, drone, robot cleaner, etc.).

[0057] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0058] 30 management terminal, 40 vehicle, 41 battery, 41b battery ECU, 44 vehicle drive unit, 45 vehicle ECU, 80 mobile terminal, 200 information platform, 300 repair shop.

Claims

1. A mobile body including a power storage device and a control device, the control device stores identification information of a first power storage device when the first power storage device is mounted on the moving body as the power storage device, A mobile body, wherein the control device is configured to transmit a first signal to an outside of the mobile body when the first storage device is replaced with a second storage device and the identification information of the first storage device stored in the control device is rewritten to the identification information of the second storage device.

2. The control device includes: authenticating an administrator of the mobile entity; switching between permission and prohibition of transmission of the first signal in response to a request from the administrator; The mobile body according to claim 1 , configured to execute the following:

3. A management system comprising the moving body according to claim 1 or 2 and a mobile terminal, When the mobile terminal receives the first signal, the mobile terminal notifies that the power storage device has been replaced.

4. The management system includes: a database that stores usage history information of the power storage device acquired from the mobile object; A server; Further equipped with When the server receives the first signal, acquiring a deterioration degree of the first power storage device estimated based on the usage history information; and determining whether or not replacement of the first power storage device was necessary using the degree of deterioration; transmitting a second signal requesting that the second power storage device mounted on the moving body be returned to the first power storage device when it is determined that replacement of the first power storage device is not necessary; The management system of claim 3 , configured to execute the following:

5. the control device is configured to transmit a third signal notifying that the power storage device has been replaced when the first power storage device is replaced with the second power storage device and identification information of the first power storage device stored in the control device has not been rewritten to identification information of the second power storage device; When the server receives the third signal, acquiring a deterioration degree of the first power storage device estimated based on the usage history information; and determining whether or not replacement of the first power storage device was necessary using the degree of deterioration; transmitting a fourth signal requesting rewriting of identification information of the power storage device stored in the control device when it is determined that replacement of the first power storage device is necessary; The management system of claim 4 , configured to execute the following:

Images