Information management system

Abstract

An information management system includes a data management device and a server. The data management device records, in a distributed book, management information including identification information of the power storage device, identification information of a user using the power storage device, and a hash value of use history information of the power storage device. The server is configured so as to be able to read the management information. The server is configured so as to be able to acquire the use history information from the data management device. The server is configured to transmit provision information based on the use history information in accordance with the transmission request. The provision information based on the use history information is information including at least one of the use history information and information generated based on the use history information.

Description

Technical Field

[0001] The present disclosure relates to an information management system for an electric storage device. Background Art

[0002] Japanese Patent Application No. 2010-540907 discloses a technique for replacing a battery mounted on a vehicle with another battery having a larger remaining amount of power when the remaining amount of power stored in the battery mounted on the vehicle is reduced. In the system described in Japanese Patent Application No. 2010-540907, the battery is replaced at a replacement station.

[0003] In the system described in the above-mentioned Japanese Patent Table 2010-540907, the battery removed from the vehicle is charged and provided to other vehicles at a replacement station. In this system, multiple power storage devices are used. In addition, one power storage device is used by multiple users in sequence. For example, a power storage device used by a user is provided to other users.

[0004] If the states of the multiple power storage devices circulating in the system can be understood, it is easy to provide power storage devices suitable for each user. Therefore, a technology for managing information related to each of the multiple power storage devices using a distributed ledger is considered. The information recorded in the distributed ledger is shared by multiple nodes. Therefore, the information recorded in the distributed ledger is difficult to be tampered with.

[0005] If the usage history information of each user's power storage device is provided to a service company (such as an insurance company), it is easy for the service company to provide services suitable for each user (such as insurance services). However, the usage history information of the power storage device used by the user is equivalent to the personal information of the user. If the user's personal information recorded in the distributed ledger is shared by multiple nodes, the interests of the user may be damaged. Summary of the invention

[0006] An object of the present disclosure is to protect the user's personal information regarding the use of a power storage device and to utilize it as necessary.

[0007] An information management system according to one aspect of the present disclosure includes a data management device and a server. The data management device is configured to record management information including identification information of a power storage device, identification information of a user who has used the power storage device, and a hash value of usage history information of the power storage device in a distributed ledger.

[0008] The server is configured to be able to read the management information.

[0009] The server is configured to be able to acquire the use history information from the data management device.

[0010] The server is configured to transmit the provided information based on the use history information in response to the transmission request.

[0011] The provided information based on the usage history information is information including at least one of the usage history information and information generated based on the usage history information.

[0012] According to the present disclosure, regarding the use of the power storage device, the user's personal information can be protected and used as needed. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Features, advantages and technical and industrial significance of this invention will become more apparent from the following detailed description of preferred embodiments of the invention with reference to the accompanying drawings, wherein like reference numerals denote like elements and wherein:

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

[0015] Figure 2 Yes means Figure 1 A diagram showing the structure of the information platform.

[0016] Figure 3 This is a diagram for explaining a process for recording management information in a distributed ledger in an information management system according to an embodiment of the present disclosure.

[0017] Figure 4 This is a diagram for explaining management information recorded in a distributed ledger in an information management system according to an embodiment of the present disclosure.

[0018] Figure 5 It is a diagram for explaining a process related to the information management method according to the embodiment of the present disclosure.

[0019] Figure 6 It means used for Figure 1 The flowchart of the process of obtaining the usage history information by the analysis server shown. DETAILED DESCRIPTION

[0020] The embodiments of the present 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 description will not be repeated.

[0021] Figure 1 This is a diagram showing an overview of the information management system according to this embodiment. Figure 1The information management system shown includes a management terminal 30, a plurality of vehicles 40, an information terminal 50, a data collection system 100A to 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 ESS150 (Energy Storage System), an information platform 200, and a warehouse 300. In this system, a plurality of power storage devices are circulated. Each power storage device is used in turn by a plurality of users. For example, a power storage device used by a certain user is provided to another user. In order to identify each power storage device circulated in the system, each power storage device is given inherent identification information (hereinafter referred to as "battery ID"). In addition, the owner and user of the power storage device are registered in the information platform 200 and given inherent identification information. In addition, the use place (vehicle 40, residence 140, ESS150) and the storage place (exchange station 130, warehouse 300) of the power storage device are registered in the information platform 200 and given inherent identification information.

[0022] Each of the plurality of vehicles 40 is equipped with a power storage device. In the vehicle 40, the power storage device functions as a driving battery. Each of the plurality of vehicles 40 uses the power output from the power storage device to travel. The power storage device may also be provided (rented) to a vehicle user (e.g., the owner of the vehicle body) through a rental service provided by an automobile manufacturer. The identification information of each vehicle (hereinafter referred to as "vehicle ID") may also be a vehicle identification number (VIN: Vehicle Identification Number).

[0023] The dealer 110 is equipped with a scan tool 111 and a dealer terminal 112 (for example, a computer). The scan tool 111 obtains information (including a vehicle ID and a battery ID) from a vehicle 40 that has visited the dealer 110 through wired communication. The information of the vehicle 40 obtained 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 by the vehicle ID.

[0024] The vehicle management device 120 includes a terminal (e.g., a computer) configured to wirelessly communicate with a vehicle 40 that is traveling or parked. The vehicle management device 120 obtains information (including vehicle IDs and battery IDs) from each of the plurality of vehicles 40 through wireless communication. The vehicle management device 120 manages the information of each vehicle by distinguishing them by vehicle ID.

[0025] The exchange station 130 is configured to store a replacement power storage device and to replace the power storage device mounted on the vehicle 40. Specifically, the exchange station 130 is configured to remove the power storage device from the vehicle 40 and to attach the replacement power storage device to the vehicle 40.

[0026] House 140 includes a solar power generation system and a mounted 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.

[0027] ESS150 is a stationary power storage system that is larger 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 excess power. The power storage device used in ESS150 has a larger capacity than the power storage device used in house 140.

[0028] The warehouse 300 is configured to store a plurality of power storage devices. The management terminal 30 manages information (in-stock information) of each power storage device stored in the warehouse 300. Power storage devices whose uses are not determined are stored in the warehouse 300. When the uses of the power storage devices are determined, the power storage devices are transported from the warehouse 300 to a use location (e.g., a residence 140 or an ESS 150) or another storage location (e.g., a replacement station 130).

[0029] The vehicle 40, the exchange station 130, the residence 140, the ESS 150, and the warehouse 300 are each equipped with a battery management system (BMS). The BMS has a detector (including various sensors) and a controller. The detector detects the state of the power storage device (such as temperature, current, and voltage). The controller records the detection result of the detector in a storage device in association with the detection time. However, the BMS at the storage location can also be omitted.

[0030] The data collection system 100A is configured to periodically collect information on vehicle-mounted power storage devices (information on each power storage device used in a plurality of vehicles 40) 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 on the power storage device of each vehicle obtained 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.

[0031] The data collection systems 100B, 100C, and 100D are configured to respectively collect information on the replacement power storage devices (information on each power storage device stored in the plurality of exchange stations 130), information on the residential power storage devices (information on each power storage device used in the plurality of residences 140), and information on the ESS power storage devices (information on each power storage device used in the plurality of ESSs 150), and to form the collected information into a database. The BMS in each of the exchange station 130, the residence 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.

[0032] The information platform 200 has nodes 10A, 10B, 10C, 10D, and 10E (e.g., computers) corresponding to the data collection systems 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. In the distributed ledger, all information from the start of the use of the distributed ledger to the present is recorded. Figure 2 It is a diagram showing the structure of the information platform 200.

[0033] like Figure 2 As shown, 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 includes, for example, a hard disk or a flash memory, and is configured to store information. The storage device 15 stores a distributed ledger. Figure 2 Only the structure of the node 10A is shown, but the other nodes 10B to 10E also have similar Figure 2 The node 10A shown has substantially the same structure.

[0034] The server 20 also holds 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 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 a distributed ledger. The storage device 25 also stores information (calculation information) used for information parsing.

[0035] The vehicle 40 is, for example, a battery electric vehicle (BEV). The vehicle 40 includes a battery 41 and an ECU (Electronic Control Unit) 42. As the battery 41, a known vehicle power storage device (e.g., a secondary battery) can be used. The ECU 42 is a control device having a processor and a storage device. The vehicle 40 also includes a wireless communication device (e.g., a data communication module (DCM)). The vehicle 40 may also include a camera for acquiring images of the surroundings of the vehicle 40, a driving recorder for recording images acquired by the camera, and an impact force sensor for detecting an impact force applied to the vehicle body (e.g., a body shell) of the vehicle 40.

[0036] The information terminal 50 of this embodiment is an external server including a processor and a storage device. The information terminal 50 provides insurance services using information (provided information) obtained from the information platform 200.

[0037] exist Figure 1 In the information management system shown, the node 10A and the data collection system 100A function as a "first data management device", the node 10B and the data collection system 100B function as a "second data management device", the node 10C and the data collection system 100C function as a "third data management device", the node 10D and the data collection system 100D function as a "fourth data management device", and the node 10E and the management terminal 30 function as a "fifth data management device". Hereinafter, when the first to fifth data management devices are not distinguished, they are simply referred to as "data management devices".

[0038] Figure 3 This is a diagram for explaining the process of recording management information in a distributed ledger by a data management device. In the following, each step in the flowchart is simply marked as "S". The process flow of S101 to S104 is executed by nodes 10A to 10E respectively. When the data management device obtains new battery information, it starts this process flow.

[0039] 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 was used (e.g., vehicle ID), and 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 (e.g., material composition information, specification information, insurance contract information, and performance evaluation information).

[0040] The usage history information of the power storage device indicates, for example, the state transition of the power storage device during a certain usage period. The usage history information of the power storage device may also include at least one of current data indicating the transition of the current of the power storage device (“current-time” graph), power storage amount data indicating the transition of the state of charge (SOC: State Of Charge) of the power storage device (“SOC-time” graph), and temperature data indicating the transition of the temperature of the power storage device (“temperature-time” graph). Information related to the usage of the power storage device, for example, Figure 3 As shown in the table in , the target power storage device is distinguished for each user. The target power storage device shown in the table is currently being used by user Y1 (first user) in vehicle A, and is rented to user Y1 from company X as the owner. In addition, the target power storage device was used by user Y2 (second user) in vehicle B before user Y1, and was used by user Y3 (third user) in vehicle C before user Y2. The battery information of the target power storage device includes first usage history information of the target power storage device used by user Y1, second usage history information of the target power storage device used by user Y2, and third usage history information of the target power storage device used by user Y3.

[0041] If the data management device obtains new battery information, the corresponding node adds the battery information to the distributed ledger through the following processing flow. However, the usage history information of the power storage device is recorded in the distributed ledger after being hashed, and the usage history information before being hashed is not recorded in the distributed ledger.

[0042] In S101, the data management device obtains a hash value of the usage history information by hashing the usage history information included in the new battery information using a hash function. In the following S102, the data management device generates an electronic signature by encrypting the hash value of the usage history information obtained in S101 using a key. The reliability of information protection is improved by the electronic signature. However, it is not necessary to generate an electronic signature.

[0043] Next, in S103, the data management device generates transaction data including management information, identification information of the data management device (recorder ID), and recording time. In this embodiment, the electronic signature (hash value of the encrypted usage history information) obtained in S102 and the above-mentioned battery information other than the usage history information are equivalent to the above-mentioned management information. In the following S104, the data management device records a new block including the hash value of the transaction data generated in S103 and the past transaction data (previous block) in the distributed ledger. Thus, the distributed ledger of each node of the DLN is updated. The various information contained in the new block is associated with each other.

[0044] Figure 4 This is a diagram used to explain the management information recorded in the distributed ledger. Figure 4 As shown, BLC data is composed of a plurality of blocks connected in a series. Figure 4 The blocks BD11 to BD13 in the table are newer as they go to the right. If they are arranged in order from the oldest block, they become blocks BD11, BD12, and BD13. BLC data represents the history of transactions. Figure 4 , the data management device generates transaction data corresponding to the data addition (transaction) (S103), and sends the generated transaction data to the DLN (S104). Afterwards, if the specified conditions are met, a new block BD13 is added to the existing blocks BD11 and BD12. For example, the new block BD13 is added to the BLC data through a related process called POW (Proof of Work). POW is a mechanism for multiple nodes to compete for the addition of a new block BD13. The node participating in the above POW that generates the new block BD13 first is rewarded. The anti-tampering nature of the BLC data is ensured by using a consensus algorithm that uses this mechanism.

[0045] Figure 5 This is a diagram for explaining the processing related to the information management method according to this embodiment. The ECU 42 of the vehicle 40 repeatedly executes the processing flow of S11 to S14.

[0046] In S11, the ECU 42 determines whether a traffic accident of the vehicle 40 is detected. The ECU 42 may also use at least one of the impact force detected by the impact force sensor and the image recorded by the driving recorder to determine whether a traffic accident of the vehicle 40 has occurred. If a traffic accident is detected (Yes in S11), the ECU 42 transmits an accident signal notifying that a traffic accident of the vehicle 40 has occurred to the information terminal 50 together with the vehicle ID of the vehicle 40 in the next S12. On the other hand, if a traffic accident is not detected (No in S11), S12 is skipped and the process proceeds to S13.

[0047] In S13, the ECU 42 determines whether the battery 41 mounted on the vehicle 40 has been replaced. The ECU 42 may read the identification information (battery ID) of the battery 41 and determine whether the battery 41 has been replaced based on whether the battery ID has changed. Alternatively, the ECU 42 may determine that the battery 41 has been replaced when receiving a signal notifying completion of battery replacement from the dealer 110 or the replacement station 130. When battery replacement is detected (Yes in S13), the ECU 42 transmits a replacement signal notifying that the battery 41 of the vehicle 40 has been replaced to the information terminal 50 together with the vehicle ID of the vehicle 40 in the next S14. On the other hand, when battery replacement is not detected (No in S13), S14 is skipped and the process returns to the initial step (S11).

[0048] When the information terminal 50 receives an accident signal or a replacement signal from the vehicle 40, the processing flow of S21 to S27 is started. The information terminal 50 specifies the target vehicle (vehicle 40) based on the vehicle ID. In S21, the information terminal 50 determines whether a traffic accident has occurred with the target vehicle. When the processing flow is started based on the accident signal, the information terminal 50 determines yes in S21 and causes the processing to proceed to S22. In addition, when the processing flow is started based on the replacement signal but a predetermined period (hereinafter referred to as "accident response period") has not passed since the receipt of the past accident signal, the information terminal 50 also causes the processing to proceed to S22 in the same manner. The accident response period can be set arbitrarily, and can be 1 day or 1 week. When the processing flow is started based on the replacement signal and the information terminal 50 has not received an accident signal for the target vehicle in the past, the information terminal 50 determines no in S21 and causes the processing to proceed to S23. In addition, when the processing flow is started based on the replacement signal and the accident response period has passed since the receipt of the past accident signal, the information terminal 50 also causes the processing to proceed to S23 in the same manner.

[0049] In any one of steps S22 and S23, the information terminal 50 requests the server 20 to send provision information (transmission request) based on the usage history information of the target power storage device mounted on the target vehicle. The information terminal 50 sends the signal for sending the request together with the vehicle ID of the target vehicle to the server 20. Among them, the signal sent in S22 (hereinafter referred to as the "first transmission request signal") indicates that a traffic accident has occurred with the target vehicle. The signal sent in S23 (hereinafter referred to as the "second transmission request signal") indicates that a traffic accident has not occurred with the target vehicle and the target power storage device has been removed from the target vehicle. If a transmission request is made to the server 20 through any of the processes in S22 and S23, the process enters S25. In S25, the information terminal 50 determines whether the provision information has been received from the server 20, and does not process during the period when the provision information has not been received.

[0050] If the server 20 receives the first or second transmission request signal from the information terminal 50, the processing flow of S31 to S34 is started. In S31, the server 20 determines whether a traffic accident involving the target vehicle has occurred. In a case where the processing flow is started based on the first transmission request signal, the server 20 determines yes in S31 and causes the processing to proceed to S32. In a case where the processing flow is started based on the second transmission request signal, the server 20 determines no in S31 and causes the processing to proceed to S33. In S32 and S33, the server 20 generates the provided information using at least one of the usage history information of the target power storage device used by the current user and the usage history information of the target power storage device used by past users. At this time, the server 20 generates the provided information, for example, by Figure 6 The series of processes shown is to obtain the usage history information of the target power storage device from the first data management device (node ​​10A).

[0051] Figure 6 2 is a flowchart showing a process for the server 20 to obtain the usage history information. Figure 3 The example of the power storage device used by users Y1 to Y3 shown in the table in will be described. The server 20 can obtain the battery information of the target power storage device based on the vehicle ID of the target vehicle by referring to the distributed ledger.

[0052] In S201, the server 20 requests the first data management device (node ​​10A) to send the usage history information of the target power storage device during the entire usage period. The server 20 can also specify the target power storage device by vehicle ID or battery ID. In response to the request from the server 20, the first data management device sends the usage history information of the target power storage device to the server 20 in the same format as BLC data (management information recorded in the distributed ledger). The usage history information of the target power storage device sent here is divided into blocks and consists of multiple blocks (refer to Figure 4 ).

[0053] In S202, the server 20 reads the transaction data corresponding to the above-mentioned usage history information in the distributed ledger. Then, the server 20 uses the key ( Figure 3 The electronic signature contained in the transaction data is decrypted using the public key corresponding to S102). The public key may also be pre-stored in the storage device 25. Alternatively, the server 20 may obtain the public key from a predetermined public key holder (e.g., the first data management device or the certification authority). If the above decryption is successful, the server 20 is able to obtain the hash value of the usage history information. The success of the decryption means that the recorder is correct. In addition, the server 20 is able to obtain battery information other than the usage history information from the transaction data.

[0054] In S203, the server 20 checks the legitimacy of the usage history information obtained from the first data management device. Specifically, the server 20 hashes the usage history information obtained in S201 using a hash function to obtain a hash value of the usage history information. Then, the server 20 checks the legitimacy of the data by comparing the hash value of the usage history information obtained by hashing with the hash value of the usage history information obtained from the distributed ledger in S202. The consistency of the hash values ​​of both parties means that the data is correct. The inconsistency of the hash values ​​of both parties means that the data is incorrect. The legitimacy of the data is checked for each block.

[0055] In S204, the server 20 determines whether the usage history information obtained from the first data management device is correct. In a case where the usage history information is determined to be incorrect through the check in S203 (No in S204), the server 20 specifies the incorrect portion (block) of the usage history information in S205, and requests the first data management device to send the correct usage history information. In response to the request from the server 20, the first data management device sends the usage history information stored in a location different from the usage history information sent in S201 to the server 20. The first data management device may also send backup data (for example, data stored in the data collection system 100A). Thereafter, the processing returns to S203. In S203, the server 20 checks the legitimacy of the usage history information obtained in S205. In a case where the usage history information is determined to be correct through the check in S203 (Yes in S204), the acquisition of the usage history information is completed. The server 20 in Figure 5 In each of S32 and S33, the provided information is generated using the usage history information.

[0056] Refer again Figure 5 In S32, the server 20 uses the usage history information (first usage history information) of the object power storage device used by the current user (user Y1) to generate provision information (hereinafter referred to as "provided information Z1") indicating the amount of value loss of the object power storage device caused by the traffic accident. For example, the difference in SOH (State of Health) before and after the accident corresponds to the amount of value loss caused by the traffic accident. Examples of SOH include capacity retention rate, full charge capacity, and the inverse of internal resistance. The server 20 may also use the first calculation formula pre-stored in the storage device 25 to calculate the amount of value loss of the object power storage device based on the first usage history information. There is a correlation between the state transition of the object power storage device accompanying the accident and the degree of degradation progress (degree of damage) of the object power storage device. The mathematical formula representing the correlation is equivalent to the above-mentioned first calculation formula.

[0057] In S33, the server 20 generates provision information (hereinafter referred to as "provided information Z2") indicating the amount of value loss of the target power storage device caused by aging degradation, using the usage history information of the target power storage device used by the current user and the usage history information of the target power storage device used by past users. In this embodiment, the usage history information related to all users is used. Specifically, regarding Figure 3 For the target power storage device shown, the server 20 generates provision information Z2 using the first usage history information related to the user Y1, the second usage history information related to the user Y2, and the third usage history information related to the user Y3. The provision information Z2 indicates the amount of value loss of each user. The server 20 may also use the second calculation formula pre-stored in the storage device 25 to calculate the amount of value loss of the target power storage device based on the first to third usage history information. There is a correlation between the state transition of the target power storage device accompanying the use of the target power storage device and the degree of degradation progress of the target power storage device. The mathematical formula representing the correlation is equivalent to the above-mentioned second calculation formula.

[0058] When the provided information Z1 or Z2 is generated by the process of S32 or S33, the server 20 transmits the generated provided information Z1 or Z2 to the information terminal 50 in S34. Thus, the process flow of S31 to S34 ends.

[0059] When there are usage histories related to a plurality of users for the target power storage device, the server 20 can provide the information terminal 50 with provision information (first provision information, second provision information, and third provision information) based on the usage history information of each user. The provision information Z1 includes only the first provision information among the first provision information based on the first usage history information, the second provision information based on the second usage history information, and the third provision information based on the third usage history information. In the case where a traffic accident of the target vehicle occurs, it is highly likely that the target power storage device has deteriorated mainly due to the traffic accident. Information related to the state of the target power storage device before and after the traffic accident is considered to be the first provision information. Therefore, the server 20 provides only the first provision information to the information terminal 50. On the other hand, the provision information Z2 includes the first to third provision information. In the case where the target power storage device has been removed from the target vehicle without a traffic accident, it is highly likely that the target power storage device cannot be used any more due to aging and degradation. The aging and degradation of the target power storage device is considered to be related not only to the first provision information but also to the second and third provision information (particularly the second provision information). Therefore, the server 20 provides the first to third provided information to the information terminal 50. According to the information management system of this embodiment, the personal information of past users is provided to the information terminal only when it is highly necessary. Thus, the personal information of past users can be protected and used at the same time.

[0060] If the information terminal 50 receives the provided information Z1 or Z2 from the server 20 (Yes in S25), the process proceeds to S26. In S26, the information terminal 50 calculates the insurance money using the provided information Z1 or Z2. In the next S27, the information terminal 50 generates information related to the reuse of the target power storage device removed from the target vehicle (hereinafter referred to as "reuse information"). If the process of S27 is executed, the process flow of S21 to S27 ends.

[0061] In detail, in the event of a traffic accident involving a target vehicle, the information terminal 50 receives the provided information Z1 from the server 20, and uses the provided information Z1 to calculate the insurance money for compensating the amount of value loss of the target power storage device caused by the traffic accident. The provided information Z1 indicates the amount of value loss of the target power storage device caused by the traffic accident. Therefore, the server 20 can calculate the insurance money corresponding to the amount of value loss of the target power storage device caused by the traffic accident. The calculated insurance money is paid from the insurance company to the current user. According to the information management system of this embodiment, it is easy to appropriately provide an insurance service for compensating the amount of value loss of the target power storage device caused by the traffic accident.

[0062] In the event of a traffic accident involving the target vehicle, the information terminal 50 generates reuse information in S27 indicating that the purpose for reusing the target power storage device has not yet been determined. Then, when the target power storage device has been removed from the target vehicle during the accident response period (S21), the information terminal 50 sends the above-mentioned reuse information to the server 20. The server 20 may also record the reuse information of the collected target power storage device in the distributed ledger. In this case, the target power storage device is transported to the warehouse 300 and inspected in the warehouse 300. The management terminal 30 determines the purpose for reuse based on the inspection result. The node 10E may also record the purpose of the target power storage device determined by the management terminal 30 in the distributed ledger.

[0063] In the case where a traffic accident of the target vehicle has not occurred and the target power storage device has been removed from the target vehicle, the information terminal 50 receives the provision information Z2 from the server 20, and uses the provision information Z2 to divide the value loss amount of the target power storage device caused by aging degradation into the value loss amount caused by the use of the current user (the user immediately before the replacement) and the value loss amount caused by the use of the past user. Then, the information terminal 50 calculates the insurance money for compensating the value loss amount caused by the use of the past user. The server 20 is capable of calculating the insurance money for compensating the value loss amount that is not the responsibility of the current user. The calculated insurance money is paid to the current user. According to the information management system of this embodiment, for the target power storage device used sequentially by multiple users, it is possible to easily and appropriately provide an insurance service for compensating for the value loss amount caused by aging degradation.

[0064] Furthermore, the information terminal 50 uses the above-mentioned provided information Z2 to infer the value of the target power storage device, and determines the purpose of reusing the target power storage device removed from the target vehicle based on the inferred value. The provided information Z2 includes not only information related to the current user's use of the target power storage device, but also information related to the use of the target power storage device by past users. Therefore, the information terminal 50 can infer the value of the target power storage device (remaining value after aging and degradation) with high accuracy. According to the information management system of this embodiment, it is easy to appropriately determine the purpose of reusing the target power storage device removed from the target vehicle. The information terminal 50 can also select one purpose from the options including the replacement station 130, the residence 140 and the ESS150. The information terminal 50 sends the reuse information indicating the determined purpose to the server 20. The server 20 can also record the reuse information of the received target power storage device in the distributed ledger. The target power storage device can also be transported to a place (a place of use or a place of storage) corresponding to the purpose indicated by the reuse information.

[0065] As described above, the information management system of this embodiment includes the first to fifth data management devices and the server 20. The first to fifth data management devices each record management information including identification information of the power storage device, identification information of the user who uses the power storage device, and a hash value of the usage history information of the power storage device in a distributed ledger. The server 20 is configured to read the management information. The server 20 is configured to obtain the usage history information from the first to fifth data management devices, respectively. For example, the server 20 can obtain the usage history information related to the vehicle-mounted power storage device from the first data management device. In response to the transmission request from the information terminal 50, the server 20 transmits the provided information based on the usage history information to the information terminal 50.

[0066] In the above-mentioned information management system, the server 20 can read the hash value of the usage history information of the power storage device from the management information (distributed ledger). In addition, the server 20 can obtain the unhashed usage history information from the data management device. The server 20 can hash the obtained usage history information and confirm whether the usage history information is correct based on whether the obtained hash value is consistent with the hash value read from the management information. Then, the server 20 can send the provision information based on the correct usage history information in response to a request from the outside. The management information contains the hash value of the usage history information, but does not contain the unhashed usage history information. Therefore, the usage history information (user's personal information) is protected. In this way, according to the above-mentioned information management system, the user's personal information can be protected and used as needed regarding the use of the power storage device.

[0067] In the information management system, execute Figure 3 , Figure 5 , Figure 6 Each process shown in the figure 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 circuit) instead of software.

[0068] Figure 5 It is not necessary for the provided information Z2 in S33 to include the first to third provided information. It is also possible to include only the first and second provided information related to the current user (user Y1) and the user immediately before (user Y2) in the provided information Z2. Figure 5 In S32 and S33 of the present invention, the server 20 generates provision information based on the usage history information. However, the present invention is not limited to this, and the server 20 may also send the usage history information itself as provision information to the information terminal 50. In addition, the server 20 may also send provision information including both the usage history information and information generated based on the usage history information to the information terminal 50. The usage history information is not limited to Figure 3The data shown may be information indicating the state of the power storage device in use.

[0069] The server 20 may also record the hash value of the calculation information (including the first and second calculation formulas) in the distributed ledger in a manner that can prove the calculation method of the value loss amount as needed. Figure 5 In S32 of the embodiment, the use history information of the target power storage device is used to generate the provision information indicating the SOH of the target power storage device immediately before the traffic accident, and the provision information Z1 is sent to the information terminal 50 instead. In addition, the target power storage device may be inspected in the warehouse 300 after the traffic accident. Then, the management terminal 30 may also obtain the SOH of the target power storage device after the traffic accident based on the inspection result and send it to the information terminal 50. The information terminal 50 may also calculate the insurance money corresponding to the value loss amount of the target power storage device caused by the traffic accident based on the SOH of the target power storage device before and after the accident.

[0070] The vehicle 40 is not limited to a BEV, and may be an electrified vehicle other than a BEV (for example, a plug-in hybrid electric vehicle). The vehicle 40 may be an automated guided vehicle (AGV) or an agricultural machine.

[0071] The embodiments disclosed this time should be considered in all aspects as illustrative rather than restrictive. The scope of the present invention is indicated by the claims rather than the description of the embodiments above, and is intended to include all modifications within the meaning and scope equivalent to the claims.

Claims

1. An information management system, wherein: have: a data management device that records management information including identification information of a power storage device, identification information of a user who has used the power storage device, and a hash value of usage history information of the power storage device in a distributed ledger; as well as a server configured to read the management information, The server is configured to obtain the usage history information from the data management device. The server is configured to send provided information based on the usage history information according to a sending request, The provided information based on the usage history information is information including at least one of the usage history information and information generated based on the usage history information.

2. The information management system according to claim 1, wherein: further comprising an information terminal that makes the transmission request to a target power storage device mounted on a vehicle currently being used by a first user, The server is configured to, when receiving the sending request from the information terminal and the target power storage device has been used by a second user before the first user, send to the information terminal at least one of first provision information based on first usage history information of the target power storage device used by the first user and second provision information based on second usage history information of the target power storage device used by the second user.

3. The information management system according to claim 2, wherein: The server is configured to transmit only the first provided information of the first provided information and the second provided information to the information terminal in response to the transmission request from the information terminal when a traffic accident involving the vehicle occurs, The server is configured to transmit the first provided information and the second provided information to the information terminal in response to the transmission request from the information terminal when a traffic accident involving the vehicle has not occurred and the target power storage device has been removed from the vehicle.

4. The information management system according to claim 3, wherein: The server is configured to: when a traffic accident involving the vehicle occurs, generate the first provision information indicating the amount of value loss of the target power storage device caused by the traffic accident in response to the transmission request from the information terminal, and transmit the generated first provision information to the information terminal; When a traffic accident involving the vehicle occurs, the information terminal calculates insurance money for compensating for the amount of value loss of the target power storage device caused by the traffic accident, using the first provided information received from the server.

5. The information management system according to claim 3 or 4, wherein: When a traffic accident involving the vehicle has not occurred and the target power storage device has been removed from the vehicle, the information terminal uses the first provided information and the second provided information to infer the value of the target power storage device, and determines the purpose of reusing the target power storage device removed from the vehicle based on the inferred value.

Images