Information management system

Abstract

To protect personal information of a user in use of a power storage device and to utilize the personal information as necessary.SOLUTION: An information management system comprises: a data management device; and a server. The data management device records management information including identification information of a 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 into a distributed ledger. A server is configured to enable a reading of the management information. The server is configured to enable acquisition of the use history information from the data management device. The server is configured to transmit provision information based on the use history information in response to a 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 on the basis of the use history information.SELECTED DRAWING: Figure 3

Description

[Technical field]

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

[0002] JP 2010-540907 A (Patent Document 1) discloses a technology for replacing a battery mounted on a vehicle with another battery having a large remaining amount of stored power when the remaining amount of stored power of the battery mounted on the vehicle decreases. In the system described in Patent Document 1, the battery is replaced at an exchange station. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special table 2010-540907 publication Summary of the Invention [Problem to be solved by the invention]

[0004] In the system described in Patent Document 1, a battery removed from a vehicle is charged and provided to another vehicle at an exchange station. In such a system, a large number of power storage devices are used. Also, one power storage device is used successively by multiple users. For example, a power storage device used by one user may be provided to another user.

[0005] If it is possible to grasp the state of each of the multiple power storage devices circulating in the system, it becomes easier to provide each user with an appropriate power storage device. Therefore, it is conceivable to use a distributed ledger to manage information about each of the multiple power storage devices. Information recorded in the distributed ledger is shared by multiple nodes. For this reason, information recorded in the distributed ledger is less likely to be tampered with.

[0006] If the usage history information of the power storage device for each user is provided to a service provider (e.g., an insurance provider), the service provider can easily provide a service (e.g., an insurance service) suitable for each user. However, the usage history information of the power storage device by the user corresponds to the personal information of the user, and if the personal information of the user recorded in the distributed ledger is shared among multiple nodes, there is a risk that the user's interests will be damaged.

[0007] The present disclosure has been made to solve the above-mentioned problems, and has an object to protect personal information of a user regarding the use of a power storage device while utilizing the information as needed. [Means for solving the problem]

[0008] An information management system according to an embodiment 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. The server is configured to be able to read the management information. The server is configured to be able to acquire the usage history information from the data management device. The server is configured to transmit, in response to a transmission request, information provided based on the usage history information. The information provided 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. Effect of the Invention

[0009] According to the present disclosure, it is possible to protect personal information of a user regarding the use of a power storage device and utilize the information as needed. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an overview of an information 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]A figure for explaining the process of recording management information in a distributed ledger in an information management system according to an embodiment of the present disclosure. [Figure 4] A diagram for explaining management information recorded in a distributed ledger in an information management system according to an embodiment of the present disclosure. [Diagram 5] 1 is a diagram for explaining a process related to an information management method according to an embodiment of the present disclosure. [Figure 6] 4 is a flowchart showing a process for the analysis server shown in FIG. 1 to acquire usage history information. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] FIG. 1 is a diagram showing an overview of an information management system according to this embodiment. The information management system shown in FIG. 1 includes a management terminal 30, a plurality of vehicles 40, an information terminal 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 warehouse 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, warehouse 300) are also registered in the information platform 200 and given unique identification information.

[0013] Each of the multiple vehicles 40 is equipped with a power storage device. In the vehicle 40, the power storage device functions as a drive battery. Each of the multiple vehicles 40 runs using electric power output from the power storage device. The power storage device may be provided (rented) to a vehicle user (e.g., an owner of a vehicle body) through a leasing service provided by an automobile manufacturer. Identification information for each vehicle (hereinafter referred to as "vehicle ID") may be a VIN (Vehicle Identification Number).

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

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

[0016] 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 particular, the exchange station 130 is configured to remove the electric storage device from the vehicle 40 and attach the exchange electric storage device to the vehicle 40.

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

[0018] 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. The power system is a power grid constructed by power transmission and distribution equipment. Examples of the facility include a factory and a commercial facility. The ESS150 can also store surplus power. The energy storage device used in the ESS150 has a larger capacity than the energy storage device used in the home 140.

[0019] Warehouse 300 is configured to be able to store a plurality of power storage devices. Management terminal 30 manages information (inventory information) of each power storage device stored in warehouse 300. Power storage devices whose uses have not been determined are stored in warehouse 300. Then, once the use of the power storage device is determined, the power storage device is transported from warehouse 300 to the place of use (e.g., house 140 or ESS 150) or another storage location (e.g., exchange station 130).

[0020] Each of the vehicle 40, the exchange station 130, the house 140, the ESS 150, and the warehouse 300 includes a BMS (Battery Management System). The BMS includes a detector (including various sensors) that detects the state of the power storage device (for example, temperature, current, voltage), 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.

[0021] The data collection system 100A is configured to, for example, periodically collect information about on-board power storage devices (information about each power storage device used in the multiple vehicles 40) 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 about 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.

[0022] Data collection systems 100B, 100C, and 100D are configured to collect information on exchange power storage devices (information on each power storage device stored in multiple exchange stations 130), information on residential power storage devices (information on each power storage device used in multiple homes 140), and information on ESS power storage devices (information on each power storage device used in multiple ESSs 150), and to organize the collected information into a database. The BMS in each of exchange stations 130, homes 140, and 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.

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

[0024] 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 includes, for example, a hard disk or a flash memory, and is configured to be able to store information. The storage device 15 stores a distributed ledger. Although FIG. 2 shows only the configuration of the node 10A, the other nodes 10B to 10E basically have the same configuration as the node 10A shown in FIG. 2.

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

[0026] The vehicle 40 is, for example, a BEV (electric vehicle). The vehicle 40 includes a battery 41 and an ECU (Electronic Control Unit) 42. A known vehicle power storage device (for example, a secondary battery) can be used as the battery 41. The ECU 42 is a control device including a processor and a storage device. The vehicle 40 further includes a wireless communication device (for example, a DCM (Data Communication Module)). The vehicle 40 may include a camera that captures images of the surroundings of the vehicle 40, a drive recorder that records the images captured by the camera, and an impact force sensor that detects an impact force applied to a vehicle body (for example, a body shell) of the vehicle 40.

[0027] The information terminal 50 according to this embodiment is an external server including a processor and a storage device. The information terminal 50 uses information obtained from the information platform 200 (provided information) to provide insurance services.

[0028] 1, node 10A and data collection system 100A function as the "first data management device," node 10B and data collection system 100B function as the "second data management device," node 10C and data collection system 100C function as the "third data management device," node 10D and data collection system 100D function as the "fourth data management device," and node 10E and management terminal 30 function as the "fifth data management device." Hereinafter, when there is no need to distinguish between the first to fifth data management devices, they will be simply referred to as the "data management devices."

[0029] 3 is a diagram for explaining the process for the data management device to record management information in the distributed ledger. In the following, each step in the flowchart is simply denoted as "S". The process flow of S101 to S104 is executed by each of the nodes 10A to 10E. The data management device starts this process flow when it acquires new battery information.

[0030] 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), 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 related to the power storage device (e.g., material composition information, specification information, insurance contract information, and performance evaluation information).

[0031] The usage history information of the power storage device indicates, for example, a state transition of the power storage device during a certain usage period. The usage history information of the power storage device may include at least one of current data indicating a transition of the current of the power storage device ("current-time" graph), stored power amount data indicating a transition of the SOC (State Of Charge) of the power storage device ("SOC-time" graph), and temperature data indicating a transition of the temperature of the power storage device ("temperature-time" graph). Information on the usage of the power storage device is classified for each user, for example, as shown in the table in FIG. 3. The target power storage device shown in this table is currently being used by user Y1 (first user) in vehicle A, and is loaned to user Y1 by business operator X, which is the owner. In addition, the target power storage device was used in vehicle B by user Y2 (second user) before user Y1, and was further used in vehicle C by user Y3 (third user) before user Y2. The battery information of the target power storage device includes first usage history information of the target power storage device by user Y1, second usage history information of the target power storage device by user Y2, and third usage history information of the target power storage device by user Y3.

[0032] When the data management device acquires new battery information, the corresponding node adds the battery information to the distributed ledger by the process flow shown below. Note that the usage history information of the power storage device is hashed before being recorded in the distributed ledger, and the usage history information before hashing is not recorded in the distributed ledger.

[0033] In S101, the data management device uses a hash function to hash the usage history information included in the new battery information, thereby obtaining a hash value of the usage history information. In the following S102, the data management device uses a private key to encrypt the hash value of the usage history information obtained in S101, thereby generating a digital signature. The digital signature improves the reliability of information protection. However, generating a digital signature is not essential.

[0034] Next, in S103, the data management device generates transaction data including management information, identification information (recorder ID) of the data management device, and recording time. In this embodiment, the electronic signature (hash value of encrypted usage history information) acquired in S102 and the above-mentioned battery information excluding the usage history information correspond to the above-mentioned management information. In the following S104, the data management device records a new block including the transaction data generated in S103 and the hash value of past transaction data (previous block) in the distributed ledger. This updates the distributed ledger of each node of the DLN. Various pieces of information included in the new block are linked to each other.

[0035] FIG. 4 is a diagram for explaining management information recorded in a distributed ledger. As shown in FIG. 4, the BLC data is composed of a plurality of blocks connected together. In FIG. 4, blocks BD11 to BD13 are newer as they move to the right. If these are arranged in order from the oldest to the newest, they are blocks BD11, BD12, and BD13. The BLC data shows a transaction history. Referring to FIG. 4, the data management device generates transaction data corresponding to data addition (transaction) (S103), and transmits the generated transaction data to the DLN (S104). After that, when a predetermined requirement is satisfied, a new block BD13 is added to the existing blocks BD11 and BD12. For example, a new block BD13 is added to the BLC data by a mining process called POW (Proof of Work). POW is a mechanism in which a plurality of nodes compete to add a new block BD13. Nodes participating in POW are generally called miners. A reward is given to the miner who generates the new block BD13 the earliest. A consensus algorithm using this mechanism ensures that BLC data is tamper-resistant.

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

[0037] In S11, the ECU 42 determines whether or not a traffic accident involving the vehicle 40 has been detected. The ECU 42 may determine whether or not a traffic accident involving the vehicle 40 has occurred using at least one of the impact force detected by the impact force sensor and the video recorded by the drive recorder. If a traffic accident has been detected (YES in S11), the ECU 42 transmits an accident signal notifying the information terminal 50 of the occurrence of a traffic accident involving the vehicle 40 together with the vehicle ID of the vehicle 40 in the following S12. On the other hand, if a traffic accident has not been detected (NO in S11), S12 is skipped and the process proceeds to S13.

[0038] 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 a signal notifying completion of the battery replacement is received from the dealer 110 or the replacement station 130. If the battery replacement is detected (YES in S13), the ECU 42 transmits an 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 following S14. On the other hand, if the battery replacement is not detected (NO in S13), S14 is skipped and the process returns to the first step (S11).

[0039] When the information terminal 50 receives an accident signal or an exchange signal from the vehicle 40, the information terminal 50 starts the process flow of S21 to S27. The information terminal 50 identifies the target vehicle (vehicle 40) based on the vehicle ID. In S21, the information terminal 50 judges whether or not a traffic accident has occurred for the target vehicle. If this process flow is started based on an accident signal, the information terminal 50 judges YES in S21 and advances the process to S22. Also, if this process flow is started based on an exchange signal but a predetermined period (hereinafter referred to as an "accident handling period") has not elapsed since the reception of a past accident signal, the information terminal 50 similarly advances the process to S22. The accident handling period can be set arbitrarily, and may be one day or one week. If this process flow is started based on an exchange signal and the information terminal 50 has not received an accident signal for the target vehicle in the past, the information terminal 50 judges NO in S21 and advances the process to S23. Also, when this processing flow is started based on an exchange signal and an accident handling period has elapsed since receiving a past accident signal, the information terminal 50 similarly advances the processing to S23.

[0040] In both S22 and S23, the information terminal 50 requests the server 20 to transmit provision information based on the usage history information of the target power storage device mounted on the target vehicle (transmission request). The information terminal 50 transmits a signal for the transmission request to the server 20 together with the vehicle ID of the target vehicle. However, the signal transmitted in S22 (hereinafter referred to as the "first transmission request signal") indicates that a traffic accident has occurred in the target vehicle. The signal transmitted in S23 (hereinafter referred to as the "second transmission request signal") indicates that a traffic accident has not occurred in the target vehicle and that the target power storage device has been removed from the target vehicle. When a transmission request is made to the server 20 by the processing of either S22 or S23, the processing proceeds to S25. The information terminal 50 determines whether or not the provision information has been received from the server 20 in S25, and does not proceed with the processing while the provision information has not been received.

[0041] When the server 20 receives the first or second transmission request signal from the information terminal 50, the server 20 starts the process flow of S31 to S34. In S31, the server 20 judges whether or not a traffic accident of the target vehicle has occurred. If this process flow has been started based on the first transmission request signal, the server 20 judges YES in S31 and advances the process to S32. If this process flow has been started based on the second transmission request signal, the server 20 judges NO in S31 and advances the process to S33. In S32 and S33, the server 20 generates information to be provided using at least one of the use history information of the target power storage device by the current user and the use history information of the target power storage device by past users. At this time, the server 20 acquires the use history information of the target power storage device from the first data management device (node ​​10A) by, for example, a series of processes shown in FIG. 6.

[0042] Fig. 6 is a flowchart showing a process for server 20 to acquire usage history information. An example will be described below in which the target power storage device is a power storage device used by users Y1 to Y3 shown in the table in Fig. 3. Server 20 can acquire battery information of the target power storage device from the vehicle ID of the target vehicle by referring to the distributed ledger.

[0043] In S201, server 20 requests first data management device (node ​​10A) to transmit usage history information for the entire usage period of the target power storage device. Server 20 may specify the target power storage device by a vehicle ID or a battery ID. In response to the request from server 20, the first data management device transmits the usage history information of the target power storage device to server 20 in the same format as BLC data (management information recorded in a distributed ledger). The usage history information of the target power storage device transmitted here is divided into blocks and consists of a plurality of blocks (see FIG. 4).

[0044] In S202, the server 20 reads transaction data corresponding to the usage history information in the distributed ledger. Then, the server 20 decrypts the electronic signature included in the transaction data using a public key corresponding to the private key (S102 in FIG. 3). The public key may be stored in advance in the storage device 25. Alternatively, the server 20 may obtain the public key from a predetermined holder of the public key (e.g., the first data management device or a certification authority). If the server 20 succeeds in the decryption, it can obtain a hash value of the usage history information. Successful decryption means that the recorder is correct. The server 20 can also obtain battery information other than the usage history information from the transaction data.

[0045] In S203, the server 20 checks the validity of the usage history information acquired from the first data management device. Specifically, the server 20 uses a hash function to hash the usage history information acquired in S201 to obtain a hash value of the usage history information. The server 20 then checks the validity of the data by comparing the hash value of the usage history information acquired by hashing with the hash value of the usage history information acquired from the distributed ledger in S202. If the two hash values ​​match, it means that the data is correct. If the two hash values ​​do not match, it means that the data is incorrect. The validity of the data is checked for each block.

[0046] In S204, the server 20 judges whether the usage history information acquired from the first data management device is correct. If it is judged by the check in S203 that the usage history information is incorrect (NO in S204), the server 20 requests the first data management device to transmit the correct usage history information by specifying the incorrect part (block) of the usage history information in S205. In response to the request from the server 20, the first data management device transmits to the server 20 the usage history information stored in a different location from the usage history information transmitted in S201. The first data management device may transmit backup data (for example, data stored in the data collection system 100A). After that, the process returns to S203. In S203, the server 20 inspects the validity of the usage history information acquired in S205. If it is judged by the check in S203 that the usage history information is correct (YES in S204), the acquisition of the usage history information is completed. The server 20 generates the provision information using the usage history information in each of S32 and S33 of FIG. 5.

[0047] Referring again to FIG. 5, in S32, the server 20 generates provided information (hereinafter, referred to as "provided information Z1") indicating the value loss of the target power storage device due to a traffic accident, using usage history information (first usage history information) of the target power storage device by a current user (user Y1). For example, the difference between the SOH (State of Health) before and after the accident corresponds to the value loss due to the traffic accident. Examples of the SOH include a capacity maintenance rate, a full charge capacity, and the reciprocal of internal resistance. The server 20 may calculate the value loss of the target power storage device from the first usage history information using a first arithmetic expression stored in the storage device 25 in advance. There is a correlation between the state transition of the target power storage device due to the accident and the degree of deterioration progress (degree of damage) of the target power storage device. The mathematical expression expressing this correlation corresponds to the above-mentioned first arithmetic expression.

[0048] In S33, the server 20 generates provided information (hereinafter, referred to as "provided information Z2") indicating the value loss of the target power storage device caused by aging, using the usage history information of the target power storage device by the current user and the usage history information of the target power storage device by past users. In this embodiment, the usage history information of all users is used. Specifically, the server 20 generates the provided information Z2 using the first usage history information of the user Y1, the second usage history information of the user Y2, and the third usage history information of the user Y3 for the target power storage device shown in FIG. 3. The provided information Z2 indicates the value loss for each user. The server 20 may calculate the value loss of the target power storage device from the first to third usage history information using a second arithmetic expression stored in the storage device 25 in advance. There is a correlation between the state transition of the target power storage device caused by the use of the target power storage device and the degree of deterioration of the target power storage device. The mathematical expression expressing this correlation corresponds to the above-mentioned second arithmetic expression.

[0049] 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. This ends the process flow of S31 to S34.

[0050] When there are usage histories relating to a plurality of users for the target power storage device, the server 20 can provide the information terminal 50 with provided information (first provided information, second provided information, third provided information) based on the usage history information of each user. The provided information Z1 includes only the first provided information among the first provided information based on the first usage history information, the second provided information based on the second usage history information, and the third provided information based on the third usage history information. When 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 regarding the state of the target power storage device before and after the traffic accident is considered to be the first provided information. For this reason, the server 20 provides only the first provided information to the information terminal 50. On the other hand, the provided information Z2 includes the first to third provided information. When the target power storage device is removed from the target vehicle without a traffic accident occurring, it is highly likely that the target power storage device cannot be used continuously due to aging deterioration. It is considered that not only the first provided information but also the second and third provided information (particularly the second provided information) are related to the aging of the target power storage device. 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, personal information of past users is provided to the information terminal only when there is a high need for it. This makes it possible to both protect and use the personal information of past users.

[0051] When 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 following S27, the information terminal 50 generates information relating to the reuse of the target power storage device removed from the target vehicle (hereinafter referred to as "reuse information"). When the process of S27 is executed, the process flow of S21 to S27 ends.

[0052] In detail, when a traffic accident occurs for the target vehicle, the information terminal 50 receives the provided information Z1 from the server 20, and calculates the insurance money to compensate for the value loss of the target power storage device due to the traffic accident, using the provided information Z1. The provided information Z1 indicates the value loss of the target power storage device due to the traffic accident. Therefore, the server 20 can calculate the insurance money according to the value loss of the target power storage device due to the traffic accident. The calculated insurance money is paid to the current user by the insurance company. The information management system according to this embodiment makes it easier to appropriately provide insurance services to compensate for the value loss of the target power storage device due to the traffic accident.

[0053] If a traffic accident occurs with the target vehicle, the information terminal 50 generates reuse information indicating that the use for reuse of the target power storage device has not been determined in S27. Then, if the target power storage device is removed from the target vehicle within the accident response period (S21), the information terminal 50 transmits the reuse information to the server 20. The server 20 may record the received reuse information of the target power storage device in the distributed ledger. In this case, the target power storage device is transported to the warehouse 300 and inspected at the warehouse 300. The management terminal 30 determines the use for reuse based on the inspection results. The node 10E may record the use of the target power storage device determined by the management terminal 30 in the distributed ledger.

[0054] When no traffic accident of the target vehicle has occurred and the target power storage device has been removed from the target vehicle, the information terminal 50 receives the provided information Z2 from the server 20, and uses the provided information Z2 to separate the value loss of the target power storage device caused by deterioration over time into the value loss caused by use by the current user (the user immediately before replacement) and the value loss caused by use by past users. Then, the information terminal 50 calculates the insurance money to compensate for the value loss caused by use by the past users. The server 20 can calculate the insurance money to compensate for the value loss that is not the fault of the current user. The calculated insurance money is paid to the current user. According to the information management system of this embodiment, it becomes easier to appropriately provide insurance services to compensate for the value loss caused by deterioration over time for a target power storage device that has been used successively by multiple users.

[0055] Furthermore, the information terminal 50 uses the above-mentioned provided information Z2 to estimate the value of the target power storage device, and determines the use for reuse of the target power storage device removed from the target vehicle based on the estimated value. The provided information Z2 includes not only information on the use of the target power storage device by the current user, but also information on the use of the target power storage device by past users. Therefore, the information terminal 50 can estimate the value (residual value after aging) of the target power storage device with high accuracy. According to the information management system according to this embodiment, it becomes easier to appropriately determine the use for reuse of the target power storage device removed from the target vehicle. The information terminal 50 may select one use from options including the exchange station 130, the house 140, and the ESS 150. The information terminal 50 transmits reuse information indicating the determined use to the server 20. The server 20 may record the received reuse information of the target power storage device in the distributed ledger. The target power storage device may be transported to a location (a use location or a storage location) corresponding to the use indicated by the reuse information.

[0056] As described above, the information management system according to this embodiment includes the first to fifth data management devices and the server 20. Each of the first to fifth data management devices records management information including identification information of the power storage device, identification information of the user who used the power storage device, and a hash value of usage history information of the power storage device in a distributed ledger. The server 20 is configured to be able to read the management information. The server 20 is configured to be able to acquire the usage history information from each of the first to fifth data management devices. For example, the server 20 can acquire usage history information related to the in-vehicle power storage device from the first data management device. The server 20 transmits provision information based on the usage history information to the information terminal 50 in response to a transmission request from the information terminal 50.

[0057] In the above 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). The server 20 can also obtain unhashed usage history information from the data management device. The server 20 hashes the obtained usage history information, and can confirm whether the usage history information is correct based on whether the obtained hash value matches the hash value read from the management information. The server 20 can then transmit information to be provided based on the correct usage history information in response to an external request. The management information includes a hash value of the usage history information, but does not include unhashed usage history information. For this reason, the usage history information (user's personal information) is protected. In this way, according to the above information management system, it is possible to utilize the user's personal information as needed while protecting it with respect to the use of the power storage device.

[0058] In the information management system, each process shown in Figures 3, 5, and 6 is executed. Each process is executed by one or more processors executing programs stored in one or more memories. However, these processes may be executed by dedicated hardware (electronic circuits) instead of software.

[0059] It is not essential that the provided information Z2 in S33 of FIG. 5 includes the first to third provided information. Only the first and second provided information related to the current user (user Y1) and the immediately preceding user (user Y2) may be included in the provided information Z2. In S32 and S33 of FIG. 5, the server 20 generates the provided information based on the usage history information. However, this is not limited to this, and the server 20 may transmit the usage history information itself as the provided information to the information terminal 50. Furthermore, the server 20 may transmit to the information terminal 50 the provided information including both the usage history information and information generated based on the usage history information. The usage history information is not limited to the data shown in FIG. 3, and may be any information indicating the state of the power storage device in use.

[0060] The server 20 may record a hash value of the calculation information (including the first and second calculation expressions) in the distributed ledger so that the calculation method of the value loss can be verified as necessary. In S32 of FIG. 5, the server 20 may generate provided information indicating the SOH of the target power storage device immediately before the traffic accident using the usage history information of the target power storage device, and transmit the provided information to the information terminal 50 instead of the provided information Z1. The target power storage device may also be inspected in the warehouse 300 after the traffic accident. Then, the management terminal 30 may determine the SOH of the target power storage device after the traffic accident based on the inspection result, and transmit the SOH to the information terminal 50. The information terminal 50 may calculate an insurance payment according to the value loss of the target power storage device due to the traffic accident, based on the SOH of the target power storage device before and after the accident.

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

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

[0063] 10A, 10B, 10C, 10D, 10E nodes, 20 server, 30 management terminal, 40 vehicle, 41 battery, 42 ECU, 50 information terminal, 100A, 100B, 100C, 100D data collection system, 110 dealer, 120 vehicle management device, 130 exchange station, 140 house, 150 ESS, 200 information platform, 300 warehouse.

Claims

1. 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; a server configured to be able to read the management information; Equipped with the server is configured to be able to acquire the usage history information from the data management device; the server is configured to transmit provision information based on the usage history information in response to a transmission request; an information management system, wherein the provided information based on the usage history information includes at least one of the usage history information and information generated based on the usage history information.

2. the information management system further includes an information terminal that makes the transmission request for a target power storage device mounted in a vehicle currently being used by a first user; 2. The information management system of claim 1, wherein the server is configured to receive the transmission request from the information terminal, and when the target energy storage device is used by a second user before the first user, to transmit to the information terminal at least one of first provided information based on first usage history information of the target energy storage device by the first user and second provided information based on second usage history information of the target energy storage device by the second user.

3. the server is configured to transmit, in a case where a traffic accident involving the vehicle has occurred, 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; 3. The information management system of claim 2, wherein 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 no traffic accident has occurred involving the vehicle and the target power storage device has been removed from the vehicle.

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

5. 5. The information management system of claim 3 or 4, wherein the information terminal estimates a value of the target energy storage device using the first provided information and the second provided information when no traffic accident has occurred involving the vehicle and the target energy storage device has been removed from the vehicle, and determines a use for reusing the target energy storage device removed from the vehicle based on the estimated value.

Images