JP2023020688A - Information processing method, program, and information processing apparatus - Google Patents

Abstract

To provide an information processing method and the like that can present the amount of reduction in the emission of carbon dioxide through the use of a battery.SOLUTION: A computer acquires the amount of emission of CO2 (carbon dioxide) in manufacturing a vehicle in which an on-board battery is mounted. The computer calculates the difference between the acquired amount of emission of CO2 and the amount of emission of CO2 in manufacturing an engine vehicle in which an engine for a vehicle is mounted, and defines the difference as an initial value of the amount of lifecycle emission of CO2 for the on-board battery. The computer specifies the amount of reduction in the emission of CO2 based on use history data of the on-board battery, and updates the amount of lifecycle emission of CO2 for the on-board battery based on the specified amount of reduction in the emission of CO2.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to an information processing method, a program, and an information processing apparatus.

As hybrid vehicles (HEV: Hybrid Electric Vehicle) and electric vehicles (EV: Electric Vehicle) become widespread, it is becoming important to diagnose deterioration of secondary batteries (also simply referred to as "batteries") mounted in these vehicles. there is In particular, when these automobiles are sold as used cars, the degree of battery deterioration affects the price of the vehicle, so it is necessary to perform an appropriate deterioration diagnosis. Patent Document 1 discloses that when the battery is installed in an automobile that can be driven by a motor, the temperature of the battery is within a predetermined temperature threshold range, and the remaining capacity of the battery is within a predetermined capacity threshold range. A battery deterioration determination device for determining deterioration of a battery is disclosed.

JP 2019-152551 A

The device of Patent Document 1 determines the deterioration of the battery while it is installed in the vehicle, and can diagnose the deterioration of only a specific battery installed in the vehicle. In addition, the battery installed in the EV is evaluated according to the degradation diagnosis result and also evaluated according to the amount of carbon dioxide emission reduction. The amount of carbon dioxide emission suppression is, for example, when driving an EV, the difference in the amount of carbon dioxide emissions compared to a gasoline car (amount of suppression), and when using a battery, the amount of power used is the primary battery. There is the amount of carbon dioxide emissions required for the production of the primary battery when it is realized by However, since it is difficult to manage the amount of carbon dioxide emitted during battery manufacture and the amount of carbon dioxide emission reduction associated with the use of the battery, for example, the amount of carbon dioxide emitted and the amount of reduction It is difficult to calculate and present

SUMMARY OF THE INVENTION It is an object of the present invention to provide an information processing method and the like capable of presenting the amount of carbon dioxide emission reduction by using a battery.

The information processing method according to the present disclosure acquires CO2 (carbon dioxide) emissions when manufacturing a vehicle equipped with a vehicle battery, and compares the acquired CO2 emissions with the engine vehicle equipped with a vehicle engine. Calculating the difference from the CO2 emissions at the time of manufacture as an initial value for the life cycle CO2 emissions of the vehicle battery, and specifying the reduction amount of CO2 emissions based on the usage history data of the vehicle battery, The computer executes a process of updating the life cycle CO2 emission amount of the vehicle battery based on the specified reduction amount of CO2 emission amount.

According to the present disclosure, it is possible to present the amount of carbon dioxide emission reduction (life cycle CO2 emission amount) due to the use of the battery. As a result, the use of the battery can be promoted, and the utility value of the battery can be increased.

1 is a schematic diagram showing a configuration example of an information processing system; FIG. 3 is a schematic diagram showing a configuration example of a node device; FIG. 4 is a schematic diagram showing a configuration example of battery-related information stored in a node device; FIG. It is a block diagram which shows the structural example of a terminal device. It is a block diagram which shows the structural example of each apparatus. 3 is a block diagram showing a configuration example of a battery management server; FIG. 4 is a schematic diagram showing a configuration example of a DB stored in a battery management server; FIG. 4 is a schematic diagram showing a configuration example of a DB stored in a battery management server; FIG. It is a block diagram which shows the structural example of a diagnostic server. It is a schematic diagram which shows the structural example of diagnosis DB. 4 is a block diagram showing a configuration example of a battery authentication server; FIG. It is a schematic diagram which shows the structural example of score DB. It is a schematic diagram which shows the structural example of authentication DB. It is a schematic diagram which shows the structural example of material authentication DB. It is a block diagram which shows the structural example of an insurance provider server. 4 is a schematic diagram showing a configuration example of a DB stored in an insurance provider server; FIG. FIG. 4 is a schematic diagram showing an example of an input screen for battery information; It is a schematic diagram which shows the input screen example of vehicle information. 5 is a flow chart showing an example of a measurement data accumulation processing procedure by an in-vehicle measuring device; 4 is a flow chart showing an example of an authentication granting procedure based on a diagnostic result by a maintenance business; 4 is a flow chart showing an example of an authentication granting procedure based on a diagnostic result by a maintenance business; It is a schematic diagram which shows an example of a screen. FIG. 4 is a schematic diagram showing an example of an input screen for battery information; It is a flowchart which shows an example of the accumulation|storage process procedure of the measurement data by BMS, and diagnostic data. FIG. 4 is a schematic diagram showing an example of an input screen for recycling information; 4 is a flow chart showing an example of an authorization granting procedure for recycled materials. It is a schematic diagram which shows an example of a screen. 7 is a flowchart showing an example of a repair information registration processing procedure; It is a schematic diagram which shows an example of a screen. 9 is a flow chart showing an example of a browsing process procedure of authentication data; It is a schematic diagram which shows an example of a screen. FIG. 11 is a schematic diagram showing another example of an authentication history screen; 4 is a flowchart showing an example of a battery pack diagnostic processing procedure; It is a schematic diagram which shows an example of a screen. FIG. 11 is a flowchart showing another example of a battery pack diagnostic processing procedure; FIG. It is a schematic diagram which shows the structural example of advice DB. 4 is a flowchart showing an example of a battery pack diagnostic processing procedure; It is a schematic diagram which shows an example of a screen. It is a schematic diagram which shows the structural example of CO2 discharge|emission control amount DB. It is a schematic diagram which shows the modification of battery DB. It is a schematic diagram which shows the modification of battery DB for stationary. FIG. 10 is a flowchart showing an example of an authorization granting process procedure for a battery; FIG. It is a schematic diagram which shows an example of a screen. FIG. 11 is a flow chart showing a modified example of a procedure for granting authentication to a battery; FIG. It is a schematic diagram which shows the modification of material authentication DB. It is a flowchart which shows the modified example of the authentication provision process procedure with respect to a recycled material. 7 is a flowchart showing an example of battery information registration processing. FIG. 10 is a flowchart showing an example of a viewing processing procedure of authentication data for recycled materials; FIG. It is a schematic diagram which shows an example of a screen. It is a schematic diagram which shows an example of a screen.

The information processing method, program, and information processing apparatus of the present disclosure will be described in detail below based on the drawings showing the embodiments thereof. In the following embodiments, an information processing system that manages various types of information about a battery (vehicle battery) installed in an HEV or EV will be described. In the following, automobiles or vehicles are assumed to be HEVs and EVs. In the following embodiments, the manufactured vehicle-mounted battery is first installed in a new vehicle for use, and then installed in a used vehicle for use. The used car may be the same vehicle as the new car, or may be a different vehicle. In addition, when the battery deteriorates to the extent that it cannot be used as a vehicle battery, it is dismantled from the vehicle, reassembled into a stationary storage battery (hereinafter referred to as a stationary battery), reused, and finally discarded. When the degree of deterioration or the like of the battery for vehicle use and the battery for stationary use is diagnosed, if repair is possible, various repair processes are performed. Batteries are also stripped of recyclable materials when discarded and used in the manufacture of new batteries. A battery is called a battery pack and is composed of a plurality of battery modules, and each battery module is composed of a plurality of battery cells connected in series or in series and parallel. In the following embodiments, a battery pack may simply be called a battery, a battery module may simply be called a module, and a battery cell may simply be called a cell.

<Overview of the system>
FIG. 1 is a schematic diagram showing a configuration example of an information processing system. The information processing system of this embodiment uses a blockchain system, which is one of the distributed ledger technologies, to store and manage various types of battery-related information in a distributed manner. The blockchain system is a system that has a plurality of node devices 10 connected to a peer-to-peer (P2P) network 1 and that the plurality of node devices 10 distribute and share various types of battery-related information. Each node device 10 includes a terminal device 20 of a battery manufacturer, a terminal device 30 of an EV manufacturer, an in-vehicle measuring device 40 of a vehicle manager, a diagnostic device 50 of a maintenance/used car business, a diagnostic device 60 of a dismantling business, Diagnostic device 70 of reuse business, BMS 80 of stationary battery manager, diagnostic device 90 of recycling business, battery management server 110 of battery management business, diagnostic server 120 of diagnostic business, battery authentication server 130 of battery certification organization , an insurance provider server 140 of an insurance provider, etc. are connected. Maintenance/used car business operators, dismantling business operators, reuse business operators, and recycling business operators are separated for the sake of convenience, but any business operator may be integrated. In the information processing system of the present embodiment, the block chain system is not an essential configuration, and various information related to the battery is stored in each server 110, 120, 130, 140, and in response to a request from each device or each server. Each server 110, 120, 130, 140 may be configured to provide such information.

The terminal device 20 of the battery manufacturer is a terminal installed in the office or office of the battery manufacturer and used by the person in charge of the battery manufacturer. The EV maker's terminal device 30 is a terminal that is installed in an EV maker's office, office, or the like, and is used by a person in charge of the EV maker. The in-vehicle measuring device 40 is mounted on the vehicle and measures information related to charging such as the travel distance of the vehicle, the usage time (discharge time) of the battery installed in the vehicle, the charging time and the number of times of charging, and measures the travel distance and battery life. Acquire metering data, including charging data related to usage time and charging. The vehicle manager includes not only the owner of the vehicle but also a business operator who manages the vehicle, such as a vehicle leasing/sharing business operator. The diagnostic device 50 of the maintenance/used car business is prepared in the maintenance shop or office of the maintenance business or the used car business, and used by the person in charge of maintenance of the vehicle or the battery. The diagnostic device 60 of the dismantling business is prepared in the factory, office, etc. of the dismantling business and used by the person in charge of dismantling the battery from the vehicle. The diagnostic device 70 of the reuse business is prepared in the factory, office, etc. of the reuse business, and is used for reuse processing such as rearrangement of modules or cells of the vehicle battery, and incorporation of the vehicle battery dismantled from the vehicle into the stationary battery. It is the equipment used by the person in charge of The diagnostic device 90 of the recycling company is prepared in the factory, office, etc. of the recycling company and used by a person in charge of dismantling the battery and sorting the recyclable materials. The diagnostic devices 50, 60, 70, and 90 are, for example, handy-type diagnostic devices, and measure the current value, voltage value, etc. of a battery mounted on a vehicle delivered to each operator or a battery dismantled from the vehicle. Data is measured and an SOH (State of Health) indicating the degree of deterioration of the battery is estimated. The diagnostic devices 50, 60, 70, and 90 measure, for example, the current value, voltage value, temperature, and SOC (State of Charge) of the battery pack, and estimate the SOH of the battery pack. Further, the diagnostic equipment 50, 60, 70, 90 measures the current value, voltage value, temperature, and SOC of the battery module or battery cell disassembled from the battery pack on a module-by-module or cell-by-cell basis, and calculates the SOH. presume. A BMS (Battery Management System) 80 is attached to a battery reused as a stationary battery, measures data such as the current value, voltage value, temperature, and remaining battery capacity (SOC) of the stationary battery, and detects overcharge or overcharge. To control a battery module so as not to overdischarge. Note that the stationary battery manager may be an operator such as an electric power company, a power supply equipment company, or a telecommunications carrier, in addition to the owner of the stationary battery.

The battery management server 110 is installed, for example, at a business office, office, or the like of a battery management company that operates a marketplace for selling batteries. The battery management server 110 stores and manages battery information related to the vehicle battery, such as information on specifications and materials of the vehicle battery and information on the vehicle in which the battery is mounted, in the battery DB 112a (see FIG. 6). . In addition, when a battery pack, battery module, or battery cell used in an in-vehicle battery is incorporated into a new battery pack or battery module and reused, the battery management server 110 stores the battery information of the new battery in the battery DB 112a. Remember. Further, when the vehicle battery is removed from the vehicle and reused as a stationary battery, the battery management server 110 stores stationary battery information related to the stationary battery in the stationary battery DB 112b (see FIG. 6). managed by In addition, the battery management server 110 stores and manages measurement data of the vehicle-mounted battery measured by the vehicle-mounted measuring device 40 in the measurement DB 112c (see FIG. 6). Furthermore, the battery management server 110 performs processing for outputting and storing vehicle battery information, stationary battery information, and vehicle battery measurement data to the blockchain system.

The diagnosis server 120 is installed in the office, office, or the like of a diagnosis provider who diagnoses the degree of deterioration of the vehicle battery and the stationary battery. The diagnosis server 120 has a function of diagnosing the degree of deterioration of the vehicle battery and the stationary battery. The diagnosis server 120 stores the measurement data of the vehicle battery measured by the diagnostic devices 50, 60, and 70, and the diagnostic results of the diagnosis of the degree of deterioration of the vehicle battery by the diagnosis operator based on the measurement data in the diagnosis database 122a (see FIG. 9). ) is stored and managed. The diagnosis server 120 also stores and manages the measurement data of the stationary battery measured by the BMS 80 and the diagnostic device 90, and the diagnosis results of the diagnosis of the degree of deterioration of the stationary battery by the diagnosis operator based on the measurement data, in the diagnosis DB 122a. are doing.

The battery authentication server 130 is installed at a business office, office, or the like of a battery authentication organization that grants predetermined authentication (authorization) to batteries. The battery authentication server 130 has a function of calculating an evaluation score for the vehicle battery and the stationary battery according to a preset rule, and granting authentication to the vehicle battery and the stationary battery based on the calculated evaluation score. . The battery authentication server 130 receives the measurement data of the vehicle-mounted battery stored in the measurement DB 112c of the battery management server 110, and the diagnostic results (diagnosis data) for the vehicle-mounted battery and stationary battery stored in the diagnosis DB 122a of the diagnosis server 120. The authentication DB 132b (see FIG. 11) stores and manages authentication information related to authentication given to vehicle-mounted batteries and stationary batteries by a battery authentication organization based on the above. In addition, the battery authentication server 130 stores and manages authentication information related to predetermined authentication (recycle authentication) given to materials recycled from discarded batteries in the material authentication DB 132c (see FIG. 11).

The insurance company server 140 is installed at a business office, office, or the like of an insurance company that sells insurance products for batteries (vehicle batteries and stationary batteries). The insurance business server 140 stores and manages insurance information on insurance products in the insurance DB 142a (see FIG. 15), and stores policyholder information on policyholders in the policyholder DB 142b (see FIG. 15). managing.

Each server of the battery management server 110, the diagnostic server 120, the battery authentication server 130, and the insurance company server 140 is described as one device, but a plurality of servers may be provided and distributed processing may be performed. It may be realized by a plurality of virtual machines provided in the server, or may be realized by using a cloud server. Moreover, when there are multiple diagnostic companies, battery certification bodies, and insurance companies, multiple servers 120, 130, and 140 are provided. Furthermore, if there are multiple battery manufacturers, EV manufacturers, vehicle managers, maintenance/used car businesses, dismantling businesses, reuse businesses, stationary battery managers, and recycling businesses, the terminal devices 20 and 30, on-vehicle measurement A plurality of devices 40, diagnostic devices 50, 60, 70, 90, and BMS 80 are provided.

In the blockchain system of the present embodiment, information on processing executed in each server of battery management server 110, diagnosis server 120, battery authentication server 130, and insurance provider server 140, and information provided from each server are stored in a plurality of The node device 10 distributes and stores. Also, the blockchain system can provide each server 110 , 120 , 130 , 140 with information stored in the plurality of node devices 10 .

FIG. 2 is a schematic diagram showing a configuration example of the node device 10. As shown in FIG. The node device 10 can be configured by a computer or computer system. The node device 10 may be a business office or office of a battery manufacturer, an EV manufacturer, a vehicle manager, a stationary battery manager, a maintenance shop, a factory of a maintenance/used car business, a dismantling business, a reuse business, or a recycling business. Alternatively, it is installed in offices, etc., of battery management companies, diagnostic companies, battery certification organizations, insurance companies, etc. Note that the node device 10 includes terminal devices 20 and 30, an on-vehicle measuring device 40, diagnostic devices 50, 60, 70 and 90, a BMS 80, a battery management server 110, a diagnostic server 120, a battery authentication server 130, or an insurance company server 140. may function as The in-vehicle measuring equipment 40 , the diagnostic equipment 50 , 60 , 70 , 90 and the BMS 80 may be configured to communicate with a predetermined server or terminal device connected to the node device 10 . In this case, each device 40, 50, 60, 70, 80, 90 transmits and receives information to and from the node device 10 via a predetermined server or terminal device.

The node device 10 includes a communication unit 11 , an information generation unit 12 , an information recording unit 13 , an information reference unit 14 and a database 15 . The communication unit 11 has a function of communicating with other node devices 10 connected to the network 1 . The communication unit 11 also communicates with the terminal devices 20 and 30, the vehicle-mounted measuring device 40, the diagnostic devices 50, 60, 70, and 90, the BMS 80, the battery management server 110, the diagnostic server 120, the battery authentication server 130, and the insurance company server 140. communication function.

The database 15 can be composed of a rewritable non-volatile semiconductor memory, a hard disk, or the like. The database 15 records a node list 16 and battery related information 17 . The node list 16 registers IP addresses and electronic certificates of the node devices 10 properly registered in the blockchain system in association with identification information for identifying the node devices 10 . A public key and an electronic signature of each node device 10 are recorded in the electronic certificate. When the new node device 10 is properly registered, the registration is reflected in the node list 16 .

FIG. 3 is a schematic diagram showing a configuration example of the battery-related information 17 stored in the node device 10. As shown in FIG. The battery related information 17 comprises a plurality of blocks 170 as shown in FIG. A plurality of blocks 170 is information that is linked in a chain and has a so-called block chain structure. FIG. 3 shows an example in which the nth and n+1th blocks 170 are connected. Each block 170 includes a timestamp 171 , a hash value 172 of the immediately preceding block 170 and record information 173 . The time stamp 171 is information indicating the date and time when the block 170 was generated. Hash value 172 is a value generated from the previous block 170 based on a preset hash function. Recorded information 173 is the main part of the information registered in block 170 . The recorded information 173 includes, for example, a pack ID, a module ID, and a cell ID (identification information for identifying a battery) in association with the battery manufacturing, EV It includes battery information at each event such as mounting on a vehicle, maintenance, repair, dismantling from a vehicle, reuse as a stationary battery, disposal, etc. Specifically, the record information 173 includes battery measurement data, deterioration degree diagnosis data, battery authentication data, and the like in each event. The recorded information 173 may also include information such as battery sales transactions, usage history, and driving history of the vehicle in which the battery is mounted. The pack ID is identification information for identifying the battery pack, the module ID is identification information for identifying the battery module within the battery pack, and the cell ID is for identifying the battery cell within the battery module. identification information.

For example, an EV manufacturer, an EV dealer, or an EV vehicle manager (for example, an owner) associates battery IDs (pack ID, module ID, cell ID) with battery IDs (pack ID, module ID, cell ID) when the vehicle manager starts using the EV. , information on battery specifications, and information on vehicles are output to the blockchain system and stored. In this case, as shown in the lower left of FIG. 3, the recorded information 173 includes battery ID, battery specification information, vehicle ID, vehicle information, vehicle manager information, and the like. In addition, the in-vehicle measuring device 40 mounted on the vehicle periodically outputs and stores the travel distance of the vehicle, battery usage time, charging time and number of charging times in association with the battery ID to the blockchain system. . In this case, as shown in the lower right of FIG. 3, the record information 173 includes the ID of the battery, the travel distance, the battery usage time, the charging time, the number of times of charging, and the like. In this way, block 170 records various pieces of information about the battery from the time the battery is manufactured until it is recycled in association with the battery ID.

The information generation unit 12, through the communication unit 11, the terminal devices 20 and 30, the vehicle-mounted measuring device 40, the diagnostic devices 50, 60, 70 and 90, the BMS 80, the battery management server 110, the diagnostic server 120, the battery authentication server 130, and the information obtained from the insurance provider server 140 is used to generate a block 170 to be registered in the blockchain system. In addition to being stored in the record information 173 of the block 170 , the battery-related information as described above is also stored in each DB of the battery management server 110 , the diagnostic server 120 , and the battery authentication server 130 . A configuration in which only the value 172 is stored may be used. Even in such a configuration, it is possible to verify the presence or absence of falsification based on the hash value 172 .

The information recording unit 13 determines whether or not the block 170 newly generated by the other node device 10 satisfies the consensus rules set in advance in the blockchain system. The information recording unit 13 records blocks 170 that satisfy predetermined agreement rules in the blockchain system. In this case, the information recording unit 13 adds a new block to the end of the cascaded blocks 170 . In the blockchain system, the reliability of information exchanged between participants is guaranteed by a process of consensus building within the network formed by all participants, and fraud such as tampering is prevented by the entire system. This keeps the integrity of the blockchain. The consensus process may use consensus algorithms such as Proof of Work or Proof of Stake.

When the information reference unit 14 receives a request to refer to the stored content of the blockchain system from the battery management server 110, the diagnosis server 120, the battery authentication server 130, and the insurance provider server 140 via the communication unit 11, the request , and transmits the read recorded information 173 to the request source. When the contents of the record information 173 are stored in the DBs of the servers 110, 120, and 130, the information reference unit 14 reads each information from each DB and transmits the information to the request source. As a result, the information recorded in the blockchain system can be provided to each server 110, 120, 130.

<Device configuration>
FIG. 4 is a block diagram showing a configuration example of the terminal device 20. As shown in FIG. The terminal device 20 is a personal computer, a tablet terminal, a smart phone, or the like. The terminal device 20 includes a control section 21 that controls the entire terminal, a storage section 22, a communication section 23, an operation section 24, a display section 25, etc. These sections are interconnected via a bus. The control unit 21 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like. The CPU of the control unit 21 expands the control program 22P pre-stored in the ROM or the storage unit 22 into the RAM and executes it, thereby controlling the operation of the hardware described above and executing the processing to be performed by the terminal device 20. do. Note that the control unit 21 is configured to include a CPU, a ROM, and a RAM, but may be any arithmetic control device including one or more CPUs, a multi-core CPU, a GPU (Graphics Processing Unit), or the like.

The storage unit 22 is composed of a flash memory, a hard disk, an SSD (Solid State Drive), or the like. The storage unit 22 stores a control program 22P executed by the control unit 21, various data necessary for executing the control program 22P, and the like. Note that the program stored in the storage unit 22 may be written in the storage unit 22 at the manufacturing stage of the terminal device 20, for example, or may be provided by a non-temporary recording medium storing the program in a readable manner. . The recording medium is, for example, a CD-ROM, a USB memory, an SD (Secure Digital) memory, a portable memory such as a micro SD card. In this case, the control unit 21 can read various programs from the recording medium using a reading device (not shown) and install the read various programs in the storage unit 22 . Also, the programs stored in the storage unit 22 may be provided by communication via the communication unit 23 . In this case, the control unit 21 can acquire various programs through the communication unit 23 and install the acquired various programs in the storage unit 22 .

The communication unit 23 has a function of communicating with the node device 10 and a function of communicating with each device via the network 1 . The communication unit 23 also has a function of communicating with, for example, the battery management server 110 via the Internet or the like. When various types of information are received via the network 1, the communication unit 23 outputs the received information to the control unit 21, and the control unit 21 executes appropriate processing based on the information received via the communication unit 23. do. When information to be transmitted to a desired destination is input from the control unit 21 via the network 1 , the communication unit 23 transmits the input information to the destination via the network 1 .

The operation unit 24 has an input interface such as a keyboard or a mouse, receives operation input by the user using the terminal device 20 , and sends a control signal corresponding to the operation content to the control unit 21 . The display unit 25 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 21 . The operation unit 24 and the display unit 25 may be a touch panel integrally configured.

When the terminal device 20 receives input of battery information related to a battery manufactured by a battery manufacturer from the operation unit 24 , the terminal device 20 transmits the received battery information to the battery management server 110 via the communication unit 23 . The battery management server 110 stores the battery information acquired from the terminal device 20, for example, in the battery DB 112a, and further outputs it to the blockchain system to store it in the blockchain system. Battery information includes, for example, information on battery specifications, information on materials used, whether or not recycled materials are used, carbon dioxide (CO2) emissions generated during battery manufacturing, and information such as optimal operating methods. .

Since the terminal device 30 has the same configuration as the terminal device 20, the description of the configuration is omitted. The terminal device 30 transmits the received vehicle information to the battery management server 110 via a communication part, when the input of the vehicle information regarding EV which the EV maker manufactured is received from the operation part. The battery management server 110 stores the vehicle information acquired from the terminal device 30, for example, in the battery DB 112a, and further outputs it to the blockchain system to store it in the blockchain system. The vehicle information includes, for example, information related to a vehicle equipped with a battery.

FIG. 5 is a block diagram showing a configuration example of each device. 5A shows an in-vehicle measuring device 40, FIG. 5B shows a diagnostic device 50, and FIG. 5C shows a BMS 80, respectively. The in-vehicle measuring device 40 is installed in the vehicle and installed in the vehicle, for example, when a vehicle equipped with an in-vehicle battery is sold to a vehicle manager, or when an in-vehicle battery is installed in the vehicle at the manufacturing stage of the vehicle. battery. The in-vehicle measuring device 40 has a function of measuring the state of the battery mounted in the vehicle. The in-vehicle measuring device 40 includes a control unit 41 that controls the entire device, a storage unit 42, a communication unit 43, a measuring unit 44, and the like. The control unit 41, the storage unit 42, and the communication unit 43 have the same configurations as the control unit 21, the storage unit 22, and the communication unit 23 of the terminal device 20 shown in FIG. 4, so detailed description thereof will be omitted. The measurement unit 44 has a terminal for connecting a battery, and measures the usage time (discharge time), charging time, number of times of charging, and the like of the connected battery. The measurement unit 44 also measures the travel distance of the vehicle. The traveled distance may be obtained, for example, from a device mounted on the vehicle, or may be configured to be measured by the measuring unit 44 itself. The in-vehicle measurement device 40 performs measurement processing by the measurement unit 44 at regular timing such as every predetermined time or once a day, or at predetermined timing such as when the vehicle finishes running, and obtains measurement data. is transmitted to the battery management server 110 by the communication unit 43 . The battery management server 110 stores the measurement data acquired from the in-vehicle measurement device 40 in, for example, the measurement DB 112c, outputs the data to the blockchain system, and stores the data in the blockchain system. With the configuration described above, battery measurement data measured by the vehicle-mounted measurement device 40 is accumulated in the battery management server 110 and the blockchain system at a predetermined timing.

The diagnostic equipment 50 can be composed of a personal computer, a tablet terminal, a smart phone, or the like. The diagnostic device 50 has a function of diagnosing the state of the battery installed in the vehicle to be serviced transported to the maintenance business or used car business. The diagnostic device 50 includes a control section 51, a storage section 52, a communication section 53, an operation section 54, a display section 55, a diagnostic section 56, an RFID (Radio Frequency Identifier) reader 57, and the like. The control unit 51, the storage unit 52, the communication unit 53, the operation unit 54, and the display unit 55 are the same as the control unit 21, the storage unit 22, the communication unit 23, the operation unit 24, and the display unit 25 of the terminal device 20 shown in FIG. , detailed description is omitted.

The RFID reader 57 reads information stored in IC tags from IC tags within a communicable range. In the information processing system of this embodiment, for example, an IC tag storing a pack ID assigned to the battery pack is attached to the battery pack. Therefore, the diagnostic device 50 can acquire the pack ID of the battery pack to be diagnosed by reading the pack ID from the IC tag attached to the battery pack using the RFID reader 57 . The diagnostic device 50 does not need to be equipped with the RFID reader 57. For example, the pack ID is read from the IC tag using a terminal device (for example, a smartphone) having an RFID reader function, and the read pack ID is read by the operation unit 54. You can enter via Instead of the IC tag, a one-dimensional code or two-dimensional code generated from the pack ID of the battery pack may be printed or attached to the battery pack. In this case, the code reader can read the pack ID from the one-dimensional code or the two-dimensional code.

The diagnosis unit 56 has a terminal for connecting a battery to be diagnosed, measures the current value, voltage value, temperature, SOC, etc. of the connected battery pack, and can acquire measurement data. Further, the diagnostic unit 56 can estimate the degree of deterioration of the battery pack according to a predetermined diagnostic algorithm. The degree of deterioration is represented by, for example, SOH (State of Health), and SOH is a value indicating what percentage the battery capacity is when a new battery is taken as 100%. The diagnosis unit 56 estimates the SOH according to a diagnosis algorithm based on, for example, a discharge current integration method during complete charging and discharging. The diagnostic algorithm performs capacity measurement using full charge and discharge. After charging the battery to full charge (SOC is 100%), it is discharged until the SOC becomes 0%. The full charge capacity is obtained using the current integration method and divided by the initial full charge capacity to estimate the SOH. Further, the diagnosis unit 56 may estimate the SOH using a diagnosis method simpler than the above-described diagnosis method, such as a diagnosis algorithm based on a charge curve analysis method, a diagnosis algorithm based on a discharge curve analysis method, or the like. The diagnostic unit 56 estimates the SOH of the battery pack according to, for example, a diagnostic algorithm instructed by the diagnostic server 120 or a diagnostic algorithm specified via the operation unit 54 . When a battery module or battery cell disassembled from a battery pack is connected, the diagnostic unit 56 measures the current value, voltage value, temperature, SOC, etc. in units of modules or cells, and estimates SOH. In addition, in the case of a cell that can record the state of the cell (for example, time-series data such as current value, voltage value, temperature, etc.) in the memory installed in each cell, the diagnostic unit 56 The data may be read to estimate the cell's SOH. The measurement data obtained by the diagnosis unit 56 is used, for example, to generate a learning model for estimating the degree of deterioration (SOH) of the battery from the battery measurement data (current value, voltage value, temperature, time-series data such as SOC). The data can be used as learning data, and can be provided to businesses that analyze battery diagnostic methods.

The diagnostic device 50 transmits diagnostic data including battery measurement data (current value, voltage value, temperature, and SOC) measured by the diagnostic unit 56 and SOH to the diagnostic server 120 through the communication unit 53 . The diagnostic server 120 stores the diagnostic data acquired from the diagnostic device 50, for example, in the diagnostic DB 122a, and further outputs the diagnostic data to the blockchain system for storage in the blockchain system. Thereby, diagnostic data of the battery diagnosed by the diagnostic device 50 is accumulated in the diagnostic DB 122a and the blockchain system. Note that the SOH of the battery may be estimated by the diagnostic server 120. In this case, the diagnostic server 120 associates the measurement data acquired from the diagnostic device 50 with the estimated SOH, and stores them in the diagnostic DB 122a and the blockchain system. Memorize. The diagnostic server 120 can determine whether the battery can be repaired and regenerated based on the diagnostic data for the battery, and can specify the module or cell to be repaired. For example, if the SOH, which indicates the degree of deterioration, is equal to or less than a predetermined threshold value, repair and regeneration can be disabled. Here, the threshold value can be, for example, a value to the extent that the battery mounted on the vehicle cannot be used. The diagnosis server 120 may also consider the past diagnosis data accumulated in the diagnosis DB 122a to determine whether the battery can be repaired or regenerated. The diagnosis device 50 may determine whether the battery can be repaired or regenerated.

The maintenance/used car business operator can use the diagnostic device 50 to acquire battery information of a battery to be diagnosed and measurement data of the battery from the battery management server 110 (battery DB 112a, measurement DB 112c). In addition, when a vehicle is brought into a maintenance facility, the maintenance/used vehicle business operator can use the diagnostic equipment 50 to perform diagnostic processing of the degree of deterioration in units of packs, modules, or cells, and obtain diagnostic results. (Measurement data and SOH) are transmitted to the diagnosis server 120 and stored in the diagnosis DB 122a. If the battery can be repaired and regenerated, the maintenance/used car business operator performs repair processing, transmits repair information regarding the repaired module or cell to the diagnosis server 120, and stores the repair information in the diagnosis DB 122a. The repair process is, for example, a process of replacing or repairing some defective modules or cells in the battery. The diagnosis server 120 may store the repair information stored in the diagnosis DB 122a in the blockchain system. With the above-described configuration, when the vehicle is transported to a maintenance/used car business, the measurement data and SOH of the battery mounted on the vehicle are measured by the diagnostic device 50, and accumulated in the diagnostic server 120 and the blockchain system. be. In addition, when the maintenance/used car business operator repairs the battery, the measurement data and SOH of the battery after repair are measured again by the diagnostic device 50, and stored in the diagnostic server 120 and the blockchain system. do.

Diagnostic equipment 60 , 70 , 90 has the same configuration as diagnostic equipment 50 . The dismantling operator can use the diagnostic device 60 to acquire battery information of the battery to be diagnosed and measurement data of the battery from the battery management server 110 (battery DB 112a, measurement DB 112c). In addition, when the vehicle is brought into the factory, the dismantling operator uses the diagnostic device 60 to diagnose the degree of deterioration of the battery removed from the vehicle on a pack-by-pack, module-by-module or cell-by-cell basis. The results (measurement data and SOH) are transmitted to the diagnostic server 120 and stored in the diagnostic DB 122a. If the battery can be repaired and regenerated, the dismantling operator performs repair processing, transmits repair information regarding the repaired module or cell to the diagnosis server 120, and stores the repair information in the diagnosis DB 122a. In addition to replacing or repairing some defective modules or cells in the battery, dismantlers perform repair processing by collecting and repacking modules or cells judged to be non-defective to assemble battery packs. include. With the above-described configuration, when the vehicle is transported to the dismantling business, the measurement data and SOH of the battery removed from the vehicle are measured by the diagnostic device 60 and accumulated in the diagnostic server 120 and the blockchain system. Further, when the dismantling operator repairs the battery, the battery measurement data and SOH are measured again by the diagnostic device 60 and stored in the diagnostic server 120 and the blockchain system. Note that when a new battery pack is generated by repacking, the dismantling operator uses the diagnostic device 60 to transmit battery information regarding the new battery pack to the battery management server 110 and store it in the battery DB 112a.

Reuse businesses repair (replace or repair) on-vehicle batteries that have been removed from vehicles by dismantling businesses. repacking to assemble the cells, re-modularization to assemble the cells judged to be non-defective into a battery module, processing to incorporate modules judged to be non-defective into other battery packs, processing to incorporate cells judged to be non-defective into other battery modules etc., necessary processing is performed when the battery is reused. These processes are hereinafter collectively referred to as a repair process. Note that these repair processes may be performed not only by reuse businesses, but also by maintenance/used car businesses, dismantling businesses, or the like. In addition, the reuse business performs the repair process described above on the vehicle-mounted battery removed from the vehicle, and also performs the process of generating a stationary battery using the battery module after the repair process. When the vehicle battery is repaired as described above, the reuse business operator uses the diagnostic device 70 to diagnose the degree of deterioration of the repaired vehicle battery in units of packs, modules, or cells. Then, the diagnosis result (measurement data and SOH) is transmitted to the diagnosis server 120 and stored in the diagnosis DB 122a. As a result, the measurement data and SOH of the vehicle battery after repair are measured by the diagnostic device 70, output to the diagnostic server 120, and accumulated in the diagnostic DB 122a and the blockchain system. Note that when a new battery pack is generated by the repacking process, the reuse business uses the diagnostic device 70 to transmit battery information regarding the new battery pack to the battery management server 110 and store it in the battery DB 112a. In addition, when the reuse business operator generates the stationary battery, the diagnostic device 70 is used to transmit battery information (stationary battery information) regarding the stationary battery to the battery management server 110 and store it in the stationary battery DB 112b. . In addition, the reuse business operator uses the diagnostic device 70 to diagnose the degree of deterioration of the generated stationary battery in units of packs, modules, or cells, and diagnoses the diagnosis results (measurement data and SOH). It is transmitted to the server 120 and stored in the diagnosis DB 122a. With the above-described configuration, when a reuse business operator generates a stationary battery, stationary battery information is output to the battery management server 110 and stored in the stationary battery DB 112b. Also, measurement data and SOH of the stationary battery are measured by the diagnostic device 70, output to the diagnostic server 120, and accumulated in the diagnostic DB 122a and the blockchain system. It should be noted that the reuse business creates an ESS (Energy Storage System) by connecting the BMS 80 to the stationary battery when generating the stationary battery.

The BMS 80 is connected to a stationary battery pack, for example, by a reuse business. The BMS 80 has a function of diagnosing the state of the battery pack, and performs diagnostic processing while the stationary battery is in use. BMS80 has the control part 81, the memory|storage part 82, the communication part 83, and the diagnostic part 84 grade|etc.,. The control unit 81, the storage unit 82, and the communication unit 83 have the same configuration as the control unit 21, the storage unit 22, and the communication unit 23 of the terminal device 20 shown in FIG. Since it has the same configuration as the diagnosis unit 56 of the device 50, detailed description will be omitted. The BMS 80 performs processing for controlling the battery modules based on the measurement data obtained by the diagnosis unit 84 so that the stationary battery is not overcharged or overdischarged. The BMS 80 periodically executes diagnostic processing by the diagnostic unit 84 and transmits diagnostic data including the obtained measurement data and SOH to the diagnostic server 120 through the communication unit 83 . The diagnostic server 120 stores the diagnostic data acquired from the BMS 80, for example, in the diagnostic DB 122a, outputs the data to the blockchain system, and stores the diagnostic data in the blockchain system. With the configuration described above, diagnostic data of the stationary battery measured by the BMS 80 connected to the stationary battery is accumulated in the diagnosis server 120 and the blockchain system at a predetermined timing. Note that the SOH of the stationary battery may be estimated by the diagnosis server 120 .

The recycling operator uses diagnostic equipment 90 to diagnose the degree of deterioration of batteries to be discarded (vehicle batteries and stationary batteries) in units of packs, modules, or cells, and displays the diagnosis results ( The measurement data and SOH) are transmitted to the diagnosis server 120 and stored in the diagnosis DB 122a. As a result, when the battery is brought into the recycling company, the battery measurement data and diagnostic data including SOH are measured by the diagnostic device 90, output to the diagnostic server 120, and accumulated in the diagnostic DB 122a and the blockchain system. be. In addition, the diagnostic server 120 can determine whether the battery can be repaired and regenerated based on the diagnostic data for the battery. Here, for example, a value to the extent that the battery cannot be used as a stationary battery is set as a threshold value, and if the SOH is equal to or less than the threshold value, repair and regeneration can be disabled. Further, the diagnostic device 90 can measure, for example, the remaining capacity (SOC) of the battery to be discarded, and if there is remaining capacity, the battery can be completely discharged at a predetermined discharge current value. This can prevent electric shock when the battery is disassembled for disposal.

When the battery cannot be repaired and regenerated, the recycling business dismantles the battery and extracts recyclable materials by refining the battery to remove impurities. At this time, the recycling operator uses the diagnostic device 90 to acquire battery information of the battery to be discarded (for example, information on rare metal components contained in the discarded battery based on material information at the time of battery manufacture), and It is possible to acquire and check the information of the diagnosis result of the battery. Information on rare metal components can be acquired from, for example, the battery DB 112a and the stationary battery DB 112b. In addition, the recycling operator can use the diagnostic equipment 90 to check how to handle the battery, and perform refining or the like according to the components of the rare metals contained in the battery. At the time of recycling, waste batteries can be sorted according to rare metal components, and waste batteries with similar components can be collected and recycled. The diagnostic device 90 can transmit to the battery management server 110 the details of the recycling process according to the rare metal component contained in the discarded battery, and can store the recycling information indicating the details of the recycling process in the stationary battery DB 112b.

In the information processing system shown in FIG. , 60 , 70 , 90 and BMS 80 , terminal devices (for example, smartphones) having the same configuration as the terminal devices 20 and 30 are provided. Each user can access the battery authentication server 130 using a terminal device, and can transmit and receive information to and from the battery authentication server 130 . Note that each user can apply to the battery authentication server 130 for authentication of the battery pack using a terminal device, and when the battery authentication server 130 grants authentication, the authentication information can be sent to the battery authentication server 130 . 130.

FIG. 6 is a block diagram showing a configuration example of the battery management server 110. As shown in FIG. The battery management server 110 is a personal computer, a server computer, or the like. The battery management server 110 includes a control unit 111 that controls the entire server, a storage unit 112, a communication unit 113, an operation unit 114, a display unit 115, etc. These units are interconnected via a bus. The control unit 111 includes, for example, a CPU, ROM, and RAM. The CPU of the control unit 111 expands the control program 112P pre-stored in the ROM or the storage unit 112 into the RAM and executes it, thereby controlling the operation of the hardware described above and executing the processing to be performed by the battery management server 110. Execute. Note that the control unit 111 is configured to include a CPU, a ROM, and a RAM, but may be any arithmetic control device including one or more CPUs, a multi-core CPU, a GPU, or the like.

The storage unit 112 is composed of a flash memory, hard disk, SSD, or the like. The storage unit 112 stores a control program 112P executed by the control unit 111, various data necessary for executing the control program 112P, and the like. Note that the program stored in the storage unit 112 may be written in the storage unit 112 at the manufacturing stage of the battery management server 110, for example, and provided by the non-temporary recording medium 110M that stores the program in a readable manner. good too. In this case, the control unit 111 can read various programs from the recording medium 110M using a reading device (not shown) and install the read various programs in the storage unit 112 . Also, the programs stored in the storage unit 112 may be provided by communication via the communication unit 113 . In this case, the control unit 111 can acquire various programs through the communication unit 113 and install the acquired various programs in the storage unit 112 . The storage unit 112 also stores a battery DB (database) 112a, a stationary battery DB 112b, and a measurement DB 112c, which will be described later.

The communication unit 113 has a function of communicating with the node device 10 and a function of communicating with each device via the network 1 . The communication unit 113 also has a function of communicating with, for example, other servers 120, 130, and 140 via the Internet or the like. Operation unit 114 has an input interface such as a keyboard or a mouse, receives operation input from a user who uses battery management server 110 , and sends a control signal corresponding to the operation content to control unit 111 . The display unit 115 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 111 . The operation unit 114 and the display unit 115 may be a touch panel configured integrally. In the present embodiment, the battery management server 110 is configured to include an operation unit 114 and a display unit 115, but the operation unit 114 and the display unit 115 are not essential, and an externally connected computer accepts operations and displays them. The configuration may be such that the information to be displayed is output to an external display device.

The battery management server 110 stores the acquired battery information in the battery DB 112a when the battery information related to the battery manufactured by the battery manufacturer is acquired from the terminal device 20 . Further, when the EV manufacturer acquires vehicle information about a vehicle equipped with a battery from the terminal device 30, the battery management server 110 stores the acquired vehicle information in the battery DB 112a. Further, when the battery management server 110 acquires the stationary battery information about the stationary battery generated by the reuse business operator from the diagnostic device 70, the battery management server 110 stores the acquired stationary battery information in the stationary battery DB 112b. Furthermore, when the vehicle-mounted measuring device 40 acquires measurement data of the battery, the battery management server 110 stores the acquired measurement data in the measurement DB 112c. The battery management server 110 may output each information stored in the battery DB 112a, the stationary battery DB 112b, and the measurement DB 112c to the node device 10 and store the information in the blockchain system.

7 and 8 are schematic diagrams showing configuration examples of the DBs 112a to 112c stored in the battery management server 110. FIG. 7 shows the battery DB 112a, FIG. 8A shows the stationary battery DB 112b, and FIG. 8B shows the measurement DB 112c. The battery DB 112a stores battery information related to batteries, vehicle information related to vehicles in which the batteries are mounted, and the like. The battery DB 112a shown in FIG. 7 includes a pack ID column, a module ID column, a cell ID column, a specification information column, a material information column, a battery manufacturing CO2 emission column, a new car information column, a used car information column, and a dismantling date column. etc., and each piece of information is stored in association with identification information (pack ID) assigned to the battery pack. The module ID is identification information assigned to each of the battery modules that make up the battery pack, and the cell ID is identification information that is assigned to each of the battery cells that make up the battery module. The module ID is, for example, information obtained by adding an identification number for each battery module to the pack ID, and the cell ID is information obtained by adding, for example, an identification number for each battery cell to the module ID. Therefore, the cell ID is information that can be identified for each cell in all the batteries registered in the battery DB 112a. The specification information includes information on battery specifications, such as battery type, size, usage conditions, and optimum operating method. The material information includes information such as the types and amounts of materials used to manufacture the battery, and the types and amounts of recycled materials used when recycled materials are used. The amount of CO2 emissions during battery manufacturing is the amount of CO2 emitted during the manufacturing process of the battery, and the amount of emissions calculated by the battery manufacturer based on the manufacturing process of the battery is acquired from the terminal device 20 of the battery manufacturer and stored. be. The new car information is information about a vehicle (new car) in which the manufactured battery is mounted, and includes, for example, the date of manufacture of the vehicle (date when the battery is mounted), vehicle ID, manufacturer name, vehicle type, model year. , manager information, etc. are associated with each other and stored in the new car information string. The vehicle ID is identification information assigned to the vehicle, and the manager information includes information such as the name and contact information of the owner such as the purchaser of the vehicle (new vehicle). The used car information is information about a vehicle equipped with a battery, and the vehicle here is a vehicle sold as a used car. The used car information is stored in a used car information string in association with, for example, the date when the used car was sold, the vehicle ID, the name of the manufacturer, the vehicle type, the model year, the manager's information, and the like. The administrator information here includes information such as the name and contact information of the owner such as the purchaser of the vehicle (used vehicle). The new car information and used car information may include the vehicle number (manufacturer's serial number, etc.), vehicle usage status (eg, mileage, years of use, frequency of use, average daily mileage, etc.). The dismantling date is the date when the battery was removed from the vehicle. The battery removed from the vehicle is reassembled into another vehicle battery, a new vehicle battery, or a stationary battery for reuse. In this embodiment, the battery pack can be repaired by replacement in units of cells or modules. Alternatively, a module ID is issued, and the cell ID or module ID in the battery DB 112a is updated to a new cell ID or module ID. In this embodiment, when a cell or module is replaced, it is configured to be updated to a new cell ID or module ID. may be stored in the battery DB 112a in association with the repair information indicating that repair processing by replacement has been performed.

The stationary battery DB 112b stores battery information related to stationary batteries. The stationary battery DB 112b shown in FIG. 8A includes a stationary battery pack ID column, a module ID column, a cell ID column, an assembly date column, an ESS information column, a repair information column, a recycling information column, and the like. Each piece of information is stored in association with the identification information (pack ID of the stationary battery) assigned to the battery pack. The module ID is identification information of the battery modules that make up the battery pack, and the cell ID is identification information of the battery cells that make up the battery module. The module ID is, for example, information obtained by adding an identification number for each battery module to the pack ID, and the cell ID is the cell ID assigned to each battery cell in the battery before being reused. Note that when a battery module is incorporated into a stationary battery, the module ID of the battery module before reuse may be stored in the module ID column. The assembly date is the date when the stationary battery was produced. The ESS information is information about a stationary battery (ESS) in which the BMS 80 is mounted, and includes specification information of the battery, specification information of the BMS 80, and the like. The repair information includes information on repair processing performed on the stationary battery. The recycling information includes information on recycling processing performed on recyclable materials contained in the stationary battery when the stationary battery is discarded. The recycling information includes, for example, the date of completion of recycling, the recycling company, the recycled material and amount, and the recycling method. The stationary battery DB 112b may store stationary battery manager information such as the name and contact information of the owner of the stationary battery. When the stationary battery is also replaced in units of cells or modules, a new cell ID or module ID is issued to the replaced cell or module, and the cell ID or module ID of the stationary battery DB 112b is changed. It is updated with a new cell ID or module ID.

The measurement DB 112c stores battery measurement data measured by the vehicle-mounted measuring device 40 while the battery is mounted in the vehicle. The measurement DB 112c shown in FIG. 8B includes a pack ID string, a measurement data string, and the like, and stores the measurement data acquired from the vehicle-mounted measuring device 40 in association with the pack ID. The measurement data includes the date and time when the in-vehicle measuring device 40 executed the measurement processing, device information related to the in-vehicle measuring device 40, the vehicle mileage measured by the in-vehicle measuring device 40, the battery usage time, the charging time and the number of times of charging. The device information includes information for specifying the vehicle-mounted measuring device 40, attributes of the vehicle-mounted measuring device 40, attributes of the vehicle manager, and other information. The battery management server 110 stores and manages information about the battery while the battery is installed in the vehicle in the battery DB 112a, and stores information about the stationary battery after the battery is removed from the vehicle and replaced with the stationary battery. are stored and managed in the stationary battery DB 112b. In addition, the battery management server 110 stores and manages measurement data of the battery measured by the in-vehicle measuring device 40 while the battery is mounted in the vehicle in the measurement DB 112c.

FIG. 9 is a block diagram showing a configuration example of the diagnosis server 120. As shown in FIG. The diagnostic server 120 is a personal computer, a server computer, or the like. The diagnosis server 120 includes a control unit 121 that controls the entire server, a storage unit 122, a communication unit 123, a switching unit 124, a diagnosis unit 125, etc. These units are interconnected via a bus. Control unit 121, storage unit 122, and communication unit 123 have the same configurations as control unit 111, storage unit 112, and communication unit 113 of battery management server 110 shown in FIG. In addition to the control program 122P executed by the control unit 121, the storage unit 122 stores a diagnostic DB 122a.

The diagnostic unit 125 includes a first diagnostic algorithm 125a, a second diagnostic algorithm 125b, and a third diagnostic algorithm 125c. Although the example of FIG. 9 shows a configuration with three diagnostic algorithms, it may have four or more diagnostic algorithms. The first to third diagnostic algorithms 125a to 125c are diagnostic algorithms for estimating the SOH of the battery. For example, a diagnostic algorithm based on a discharge current integration method during full charge and discharge, a diagnostic algorithm based on a charge curve analysis method, and a discharge curve. Includes analytical diagnostic algorithms. In the charge curve analysis method, the voltage, current, and temperature of the battery being charged are first measured, these data are recorded as a charge curve, the initial values of the parameters representing the internal state of the battery are set, and regression calculation is performed. The parameters are estimated to calculate the state of the battery (for example, battery capacity). In the discharge curve analysis method, the discharge curve is characterized by differentiating the voltage, etc., and the change in capacity of each active material of the positive electrode and negative electrode of the battery is extracted, and the state of the battery (for example, battery capacity) is calculated. .

The first to third diagnostic algorithms 125a to 125c may include, in addition to the diagnostic algorithms described above, diagnostic algorithms using table lookup from internal resistance, model-based diagnostic algorithms, and the like. Diagnosis by table lookup from internal resistance is to acquire the relationship between SOH and internal resistance in advance and form a table, and to obtain SOH by table lookup from the measured internal resistance. Model-based diagnosis involves estimating SOH by associating specific parameters in a model used in SOC estimation with SOH and estimating the parameters. For example, the SOH can be obtained by expressing the full charge capacity of the battery by the capacity of the capacitor in the equivalent circuit model and estimating the capacity. Diagnostic algorithms are not limited to those described above. Further, the diagnostic algorithm may be prepared for each battery manufacturer, each EV manufacturer, and each battery type, for example.

The switching unit 124 selects battery information (for example, battery information stored in the battery DB 112a of the battery management server 110, stationary battery information stored in the stationary battery DB 112b) of a battery to be diagnosed (including a stationary battery). , or depending on the user's choice, selects the desired diagnostic algorithm. For example, when the information of the battery to be diagnosed is acquired from the diagnostic equipment 50, 60, 70, 90 or the BMS 80, the switching unit 124 acquires the battery information of the battery from the battery management server 110, and based on the battery information, Select a diagnostic algorithm to be used for diagnosing the state of health (SOH) of the battery. For example, when a diagnostic algorithm is set in advance for each battery manufacturer or battery type, the switching unit 124 selects a diagnostic algorithm according to the battery manufacturer or battery type of the battery to be diagnosed. The diagnostic unit 125 instructs the diagnostic equipment 50 , 60 , 70 , 90 or the BMS 80 to execute diagnostic processing according to the diagnostic algorithm selected by the switching unit 124 . In addition, the diagnostic unit 125 acquires measurement data of the battery measured by the diagnostic equipment 50, 60, 70, 90 or the BMS 80, and based on the acquired measurement data, the battery according to the diagnostic algorithm selected by the switching unit 124. You may diagnose the degree of deterioration of

When the diagnostic devices 50, 60, 70, 90 and the BMS 80 perform battery diagnostic processing (including stationary batteries), the diagnostic server 120 determines a diagnostic algorithm according to the battery to be diagnosed, and 60, 70, 90 and BMS 80. Further, the diagnostic server 120 acquires the results (diagnostic data) of diagnostic processing by the diagnostic devices 50, 60, 70, 90 and the BMS 80, stores them in the diagnostic DB 122a, and manages them. Further, the diagnostic server 120 performs comprehensive diagnostic processing on the battery based on the diagnostic results obtained from the diagnostic devices 50, 60, 70, 90 and the BMS 80, and determines whether each cell can be repaired or regenerated. It is stored and managed in the DB 122a. The diagnosis server 120 may output each information stored in the diagnosis DB 122a to the node device 10 and store the information in the blockchain system.

FIG. 10 is a schematic diagram showing a configuration example of the diagnosis DB 122a. The diagnostic DB 122a stores diagnostic data for vehicle batteries and stationary batteries. Hereinafter, vehicle batteries and stationary batteries are collectively referred to as batteries. The diagnostic DB 122a shown in FIG. 10 includes a pack ID column, a module ID column, a cell ID column, a first diagnostic data column, a second diagnostic data column, etc., and corresponds to battery IDs (pack ID, module ID, cell ID). The diagnostic processing result for the battery is stored with the name attached. Diagnostic data is stored in the diagnostic DB 122a for each diagnostic process performed using the diagnostic equipment 50, 60, 70, 90 or BMS80. Diagnostic data includes identification information (diagnostic ID) for identifying diagnostic data, execution date and time of diagnostic processing, events, diagnostic equipment 50, 60, 70, 90 or equipment information related to BMS 80, diagnostic equipment 50, 60, 70, 90 Alternatively, it includes battery measurement data (current value, voltage value, temperature, SOC, SOH) by the BMS 80, battery diagnosis results, repair information, and the like. The event is a cause for execution of diagnostic processing. For example, when diagnostic processing is performed by the diagnostic device 50 when servicing a vehicle delivered to a maintenance/used car business, "vehicle maintenance" is stored and the vehicle is serviced. When the diagnostic processing is performed by the diagnostic device 50 when the vehicle is sold as a used vehicle, "used vehicle installed" is stored. For example, when the vehicle is disassembled from the vehicle by the dismantling business and the diagnosis processing is performed by the diagnostic device 60, the event is stored as "dismantled from the vehicle", and the stationary battery is assembled by the reuse business and the diagnostic device is used. If the diagnostic processing by 70 is performed, "assembly" is stored. As for the event, "regular diagnosis" is stored when the BMS 80 performs diagnostic processing at a predetermined timing, and diagnostic processing is performed by the diagnostic device 90 on stationary batteries to be discarded carried in to a recycling company. "discard" is stored. As described above, events include vehicle maintenance, installation of used vehicles, dismantling from vehicles, assembly, periodic diagnosis, and disposal, as well as manufacture of batteries, installation on EVs (new vehicles), repairs, and the like. Equipment information is information for identifying diagnostic equipment 50, 60, 70, 90 or BMS 80, attributes of diagnostic equipment 50, 60, 70, 90 or BMS 80, attributes of each business operator or stationary battery manager, etc. including. The diagnostic result includes the diagnostic result for the battery determined by the diagnostic server 120 based on the measurement data by the diagnostic equipment 50, 60, 70, 90 or the BMS 80, for example, the diagnostic algorithm used for diagnosis, the SOH for the battery, and the diagnostic business It includes information that identifies the person (diagnostic institution). The repair information includes information (for example, module ID or cell ID) on the module or cell on which the repair process has been performed and information indicating the details of the repair process. The repair information is stored in the diagnosis DB 122a when, for example, a maintenance/used car business operator, a dismantling business operator, or a reuse business operator performs repair processing on the battery as a result of diagnostic processing on the battery. The diagnostic data stored in the diagnostic DB 122a includes measurement data and diagnostic results for the battery pack when measurement processing and diagnostic processing are performed on the battery pack, and when measurement processing and diagnostic processing are performed for each module. contains measurement data and diagnosis results for each module, and includes measurement data and diagnosis results for each cell when measurement processing and diagnosis processing are performed for each cell. The diagnosis DB 122a is configured to store the diagnosis results regarding the battery mounted on the vehicle and the stationary battery. It may be configured to be stored in another DB.

FIG. 11 is a block diagram showing a configuration example of the battery authentication server 130. As shown in FIG. Since the battery authentication server 130 has the same configuration as the battery management server 110 shown in FIG. 6, detailed description of the configuration is omitted. Storage unit 132 of battery authentication server 130 stores score DB 132a, authentication DB 132b, and material authentication DB 132c in addition to control program 132P executed by control unit 131. FIG.

The battery authentication server 130 accepts applications for authentication of batteries (including stationary batteries) from business operators via the terminal devices 20, 30 or the diagnostic devices 50, 60, 70, 90, or the like. When the battery authentication server 130 receives a battery authentication application, the battery information and stationary battery information registered in the battery DB 112a and the stationary battery DB 112b of the battery management server 110 and the stationary battery information registered in the diagnostic DB 122a of the diagnostic server 120 are stored. Authorization is granted to the battery based on the diagnostic data stored therein. At that time, the battery authentication server 130 calculates an evaluation score (evaluation level) for the battery based on the battery information and diagnostic data, and determines whether or not to grant authentication according to the calculated evaluation score. When the battery authentication server 130 grants authentication to the battery, the battery authentication server 130 stores authentication information (authentication data) related to the granted authentication in the authentication DB 132b. Also, the battery authentication server 130 gives recycling authentication to the recycled material extracted from the battery to be discarded. At that time, the battery authentication server 130 determines whether or not to give the recycling authentication to the battery based on the recycling process performed on the recycled material, the recycling company, and the like. Note that, when the battery authentication server 130 gives recycling authentication to a recycled material, the battery authentication server 130 stores authentication information (authentication data) related to the given recycling authentication in the material authentication DB 132c. The battery authentication server 130 may output each information stored in the authentication DB 132b and the material authentication DB 132c to the node device 10 and store the information in the blockchain system.

FIG. 12 is a schematic diagram showing a configuration example of the score DB 132a. The score DB 132a shown in FIG. 12 includes a score ID column, a determination content column, a score column, and the like, and is associated with identification information (score ID) for identifying the score, and the score and the determination condition (determination content) for each score. ) and The judgment content is a condition for adding each score. The diagnostic device 50, 60, 70, 90 or BMS 80 is a device that has received predetermined certification (certified device), the diagnostic algorithm used for the diagnostic processing for the battery is an algorithm that has received predetermined certification, including that the diagnostic business operator who performed the diagnostic processing for is a business operator that has received a predetermined authorization (authorized business operator). Further, the determination contents include contents related to the degree of deterioration of the battery (for example, SOH), vehicle travel distance, battery usage time, charging time, and the number of times of charging (charging data relating to the charging history of the battery). The battery authentication server 130 refers to the score DB 132a when granting authentication to a battery, and based on the battery information and diagnostic data of the battery and the judgment contents stored in the score DB 132a, the battery authentication server 130 Calculate the evaluation score. Battery authentication server 130 determines whether or not to grant authentication to the battery based on the calculated evaluation score. The contents stored in the score DB 132a may be changeable according to an operation on the battery authentication server 130. FIG. In this case, when a certified device, a certified algorithm, and a certified business operator newly appear, scores corresponding to them can be registered in the score DB 132a. Therefore, if the device, diagnostic algorithm, or business operator used for diagnosing the battery is newly certified and the scores corresponding to them are registered in the score DB 132a, the device, diagnostic algorithm, or business operator can be used. Then, the evaluation score for the battery for which diagnosis processing has been performed is updated, and an improvement in the evaluation of the battery can be expected. Note that, when the contents stored in the score DB 132a are updated, the battery authentication server 130 performs the evaluation score calculation processing again for each battery based on the updated score information, thereby performing the evaluation processing and It may be configured to perform authentication processing again.

FIG. 13 is a schematic diagram showing a configuration example of the authentication DB 132b. The authentication DB 132b stores authentication information (authentication data) relating to authentication given to batteries (including stationary batteries). The authentication DB 132b shown in FIG. 13 includes a pack ID column, a module ID column, a cell ID column, a first authentication data column, a second authentication data column, etc., and corresponds to battery IDs (pack ID, module ID, cell ID). The authorization grant result for the battery is stored with the name attached. The authentication data is stored in the authentication DB 132b for each authentication given to the battery based on the authentication application from each company. The authentication data includes identification information (authentication ID) for identifying the authentication data, the date and time when the authentication was granted, the event, the evaluation score for the battery at this time, the details of the authentication for the battery, and the like. The event is the reason for applying for certification. For example, when an EV manufacturer manufactures a vehicle and an application for certification is made for the battery installed in the vehicle, "installed in a new vehicle" is stored, and the event is used by maintenance and used vehicle operators. If the application for certification is made when servicing the brought-in vehicle, "vehicle maintenance" is stored, and if the application for certification is made when the vehicle is sold as a used vehicle, "used vehicle installed" is stored. be done. In addition, for example, when a dismantling business dismantles from a vehicle and an application for certification is made, the event is stored as "dismantling from a vehicle", and an application for certification is made when a stationary battery is assembled by a reuse business. If it is set, "Assemble" is stored. Also, as the event, "discard" is stored, for example, when an application for certification is made for a battery to be discarded brought into a recycling company. The evaluation score is a score calculated for the battery by the battery authentication server 130 based on the score DB 132a. The authentication content is the result of authentication given to the battery by the battery authentication server 130 based on the evaluation score, and includes whether or not authentication has been given, and the level and details of the given authentication. The authentication data stored in the authentication DB 132b includes authentication data for the battery pack when authentication processing is performed for the battery pack, and includes authentication data for each module when authentication processing is performed for each module, If authentication processing is performed on a cell-by-cell basis, it includes authentication data for each cell. The authentication DB 132b is configured to store authentication results relating to the vehicle-mounted battery and the stationary battery, but may be configured to store the authentication result of the vehicle-mounted battery and the authentication result of the stationary battery in separate DBs. .

FIG. 14 is a schematic diagram showing a configuration example of the material authentication DB 132c. The material authentication DB 132c stores authentication information (authentication data) relating to authentication (recycle authentication) given to recyclable materials (hereinafter referred to as recycled materials) extracted from batteries to be discarded. The material authentication DB 132c shown in FIG. 14 includes a material ID column, a recycled material column, a pack ID column, a module ID column, a recycling completion date column, a recycling company column, a recycling method column, an authentication date column, an authentication information column, and the like. It stores the authentication grant result for the material in association with the identification information (material ID) assigned to the recycled material. The recycled materials are rare metal components such as lithium, nickel, cobalt and manganese. The pack ID and module ID are the IDs of the battery pack and battery module before recycling. The recycling method can use a recycling process according to the recycled material (rare metal component). For example, it is possible to use a recycling system according to the ratio of components such as lithium, nickel, cobalt, manganese, etc., and the most common component. Also, a recycling method according to the type of battery may be used. The authentication information includes the level and content of recycling authentication given to the recycled material by the battery authentication server 130 .

FIG. 15 is a block diagram showing a configuration example of the insurance provider server 140. As shown in FIG. The insurance company server 140 has the same configuration as the battery management server 110 shown in FIG. 6, so a detailed description of the configuration is omitted. In addition to the control program 142P executed by the control unit 141, the storage unit 142 of the insurance provider server 140 stores an insurance DB 142a and a policyholder DB 142b.

The insurance company server 140 is a server of an insurance company that sells insurance products for in-vehicle batteries and stationary batteries. The insurance provider server 140 receives requests for information on insurance products contracted for batteries from the battery management server 110, the diagnostic server 120, or the battery authentication server 130, for example. When information on an insurance product is requested, the insurance business server 140 reads the policyholder information of the owner of the battery (insurance policyholder) from the policyholder DB 142b, and obtains information on the insurance product contracted by the policyholder. The insurance information is read from the insurance DB 142a and provided to the requesting server.

FIG. 16 is a schematic diagram showing a configuration example of the DBs 142a to 142b stored in the insurance carrier server 140. As shown in FIG. FIG. 16A shows the insurance DB 142a, and FIG. 16B shows the policyholder DB 142b. The insurance DB 142a shown in FIG. 16A includes an insurance ID column, an insurance product name column, a compensation content column, and the like. and the content of compensation by the insurance product. The contents of compensation include insurance premiums, compensation conditions, compensation targets, and the like. For example, if the battery subject to the contract deteriorates rapidly (such as when the SOH drops by 20% or more in one month), we will pay a benefit for the repair cost required to replace the defective cell, or The content is to pay a benefit for the repair cost required to replace the battery module. In this way, the compensation condition may be a condition related to the degree of deterioration of the battery, such as the mileage of the vehicle using the battery, charging data related to the charging history such as the battery usage time, charging time, and the number of times the battery is charged. It may be a condition related to measurement data.

The policyholder DB 142b stores information about policyholders who have contracted insurance products for batteries. The policyholder DB 142b shown in FIG. 16B includes an insurance contract ID column, a policyholder information column, a battery information column, a contract insurance ID column, a contract date column, a contract period column, etc., and includes identification information (insurance contract ID), information on the policyholder, information on the battery to be compensated, insurance ID of the contracted insurance product, contract date and contract period of the insurance product are stored in association with each other. The contractor information includes, for example, the contractor's name, age, sex, and contact information. The battery information includes identification information such as the pack ID, module ID, and cell ID of the battery pack, and information related to the battery such as the type, size, and conditions of use of the battery. The battery information may include, for example, the usage period (usage time) of the battery at the time of the insurance contract, charging time and number of charging times, SOH, information on the vehicle in which the battery is mounted or stationary battery, and the like. The contract period may be a predetermined period (for example, 5 years, 10 years, etc.), or may be a period until use of the battery subject to compensation is terminated.

<Battery-related information registration process>
A process of registering battery-related information about a battery in the battery management server 110 will be described. The battery-related information here is assumed to be battery information about the battery, vehicle information about the vehicle, and measurement data of the battery measured by the in-vehicle measuring device 40 .

A process of registering battery information about a battery in the battery DB 112a of the battery management server 110 when the battery is manufactured by a battery manufacturer will be described. FIG. 17 is a schematic diagram showing an example of an input screen for battery information. The screen shown in FIG. 17 is displayed on the display unit 25 when the terminal device 20 executes a predetermined application, for example. The input screen shown in FIG. 17 displays the number of battery modules used in the battery pack to be registered, the number of battery cells used in each battery module, specification information, material information, CO2 emissions during battery manufacturing, and the like. It has input fields for inputting each information. Each input column may be configured such that each information is directly input, or may be configured to be input by displaying a plurality of options and selecting an arbitrary one. The specification information includes information such as battery type, size, usage conditions, and optimal operating method. The material information includes information such as the types and amounts of materials used to manufacture the battery, and the types and amounts of recycled materials used when recycled materials are used. The specification information and material information may be entered in the specification information and material information input fields, respectively, or the file name of a file (for example, a text file) containing the specification information or material information may be entered. . The amount of CO2 emissions during battery manufacturing may be the amount of CO2 emissions for a battery pack to be registered, or may be the amount of CO2 emissions for one cell. As the CO2 emission amount for one cell, for example, a value obtained by dividing the CO2 emission amount for the battery pack by the number of cells included in the battery pack may be used. When each piece of information is input through the battery information input screen and the registration button is operated, the terminal device 20 transmits the input battery information to the battery management server 110 and stores it in the battery DB 112a. Thereby, when a battery is manufactured by a battery manufacturer, battery information about the battery is registered in the battery management server 110 . When the battery information received from the terminal device 20 is registered in the battery DB 112a, the battery management server 110 issues a battery ID to the battery pack, and stores the issued battery ID and battery information in the battery DB 112a. . The battery IDs used in this embodiment include pack IDs, module IDs, and cell IDs, where the respective IDs are the ID assigned to the battery pack, the ID assigned to the battery module, and the ID assigned to the battery cell. is. When the battery ID (pack ID, module ID, cell ID) is issued, the battery management server 110 transmits the issued battery ID to the terminal device 20 to notify the battery manufacturer. The battery management server 110 may output the battery information stored in the battery DB 112a to the node device 10 and instruct the node device 10 to store the battery information in the blockchain system. In this case, the node device 10 generates the block 170 using the battery information acquired from the battery management server 110, and stores the block 170 in the blockchain system when the generated block 170 satisfies a predetermined consensus rule.

Next, a process of registering vehicle information about an EV in the battery DB 112a of the battery management server 110 when an EV manufacturer manufactures an EV will be described. FIG. 18 is a schematic diagram showing an example of an input screen for vehicle information. The screen shown in FIG. 18 is displayed on the display unit when the terminal device 30 executes a predetermined application, for example. The input screen shown in FIG. 18 includes pack ID (vehicle battery pack ID), module ID, cell ID, date, manufacturer, vehicle type, model year, administrator (vehicle owner) name and contact information. It has an input column for inputting each information such as. Each input column may be configured such that each information is directly input, or may be configured to be input by displaying a plurality of options and selecting an arbitrary one. The pack ID, module ID, and cell ID are IDs issued by the battery management server 110 when the battery manufacturer registers battery information in the battery management server 110 . The date may be the date the battery is installed in the vehicle, or the date the vehicle information is registered in the battery DB 112a. When each information is input through the vehicle information input screen and the registration button is operated, the terminal device 30 transmits the input vehicle information to the battery management server 110 and stores it in the battery DB 112a as new vehicle information. Accordingly, when an EV is manufactured by an EV manufacturer (when a battery is installed in the EV), vehicle information regarding the EV is registered in the battery management server 110 . When the vehicle information received from the terminal device 30 is registered in the battery DB 112a, the battery management server 110 issues a vehicle ID to the vehicle, and stores the issued vehicle ID and vehicle information in the battery DB 112a. Also, the battery management server 110 may output the vehicle information stored in the battery DB 112a to the node device 10, and the node device 10 may store the vehicle information in the blockchain system. The vehicle information described above is registered in the battery DB 112a by the person in charge of the EV manufacturer using the terminal device 30, and is also registered in the battery DB 112a by the purchaser (vehicle manager) who purchased the EV using his/her own terminal device. may For example, the vehicle manager may register the vehicle information in the battery DB 112a and be issued a vehicle ID when the vehicle starts to be used.

Vehicles whose battery information and vehicle information are registered in the battery management server 110 by the battery manufacturer and the EV manufacturer as described above are purchased and used by purchasers (vehicle managers). For example, when an EV manufacturer sells a vehicle, the vehicle is equipped with the in-vehicle measuring device 40 and connected to the battery in the vehicle. At that time, the EV manufacturer attaches to the battery pack an IC tag that stores the pack ID assigned to the battery pack mounted on the vehicle. As a result, the pack ID can be read from the IC tag by the RFID reader. Note that the IC tag may store a module ID and a cell ID in addition to the pack ID.

Next, a process of accumulating measurement data acquired by the vehicle-mounted measurement device 40 in the measurement DB 112c of the battery management server 110 will be described. The in-vehicle measuring device 40 measures the travel distance of the vehicle, the usage time, the charging time, and the number of charging times of the connected battery pack at a predetermined timing, and obtains measurement data. FIG. 19 is a flow chart showing an example of a measurement data accumulation processing procedure by the vehicle-mounted measuring device 40. As shown in FIG. In FIG. 19 , the processing performed by the in-vehicle measuring device 40 is shown on the left side, and the processing performed by the battery management server 110 is shown on the right side.

The in-vehicle measuring device 40 is configured to perform measurement processing periodically or at a predetermined timing, and the control unit 41 determines whether or not it is time to perform the measurement processing (measurement timing) (S11 ). For example, when the measurement process is executed every predetermined time, the control unit 41 determines whether or not a predetermined time has passed since the most recent measurement process was executed. Further, for example, when the measurement process is executed once a day at a predetermined time, the control unit 41 determines whether or not the predetermined time has arrived. When determining that it is not the measurement timing (S11: NO), the control unit 41 waits until the measurement timing arrives. If it is determined that it is time to measure (S11: YES), the control unit 41 executes the measurement process (S12), and calculates the travel distance of the vehicle, the battery usage time, and the charging time from the most recent measurement process to this point. Measure the time and the number of charging times. The control unit 41 transmits the acquired measurement data to the battery management server 110 in association with the pack ID of the battery pack to be measured (S13). Note that the control unit 41 includes the date and time (measurement date and time) at this point in time and device information (for example, a device ID assigned to the device) that can identify the in-vehicle measuring device 40 and transmits the measurement data to the battery management server 110 . . The device information is stored in the storage unit 42 in advance, for example. The pack ID may be input via an operation unit (not shown) and stored in the storage unit 42 when the in-vehicle measuring device 40 is mounted on the vehicle, for example. function, the IC tag attached to the battery pack may be read.

When receiving the measurement data from the vehicle-mounted measuring device 40, the control unit 111 of the battery management server 110 stores the received measurement data in the measurement DB 112c (S14). Here, the control unit 111 stores the measurement data including the measurement date and time and the device information in the measurement DB 112c in association with the pack ID received from the vehicle-mounted measuring device 40 . Also, the control unit 111 stores the measurement data in the blockchain system (S15). Here, the control unit 111 associates the pack ID and the measurement data, outputs them to the node device 10, and instructs the node device 10 to store the measurement data in the blockchain system. The node device 10 generates a block 170 using the pack ID and the measurement data acquired from the battery management server 110, and records it in the blockchain system when the generated block 170 satisfies a predetermined consensus rule. As a result, the measurement data measured by the in-vehicle measurement device 40 is stored in the blockchain system in association with the pack ID (battery identification information). Note that the control unit 111 may be configured to store the measurement data only in the blockchain system without storing the measurement data in the measurement DB 112c. A configuration in which only the hash value 172 is stored in the block 170 may be used.

After the process of step S13, the controller 41 of the in-vehicle measuring device 40 returns to step S11, and repeats the measurement process and the transmission process of the measurement data each time the measurement timing arrives. The battery management server 110 stores the measurement data in the measurement DB 112c and the blockchain system each time it receives the measurement data from the vehicle-mounted measurement device 40 . As a result, battery measurement data measured by the in-vehicle measuring device 40 at predetermined timings is accumulated in the battery management server 110 and the blockchain system, so that the battery state can be traced.

<Authentication based on diagnosis processing by the maintenance company>
Next, a description will be given of a process in which a maintenance business uses diagnostic equipment 50 to perform battery pack diagnostic processing, and a battery certification body grants certification to the battery pack based on the obtained diagnostic results (diagnostic data). . 20 and 21 are flow charts showing an example of the procedure for granting authorization based on the diagnostic results of the maintenance business, and FIG. 22 is a schematic diagram showing an example of a screen. In FIG. 20, the processing performed by the diagnostic device 50 of the maintenance business is shown on the left, and the processing performed by the diagnostic server 120 is shown on the right. Each processing performed by the server 130 is shown.

When the vehicle is brought into the maintenance business for maintenance or inspection, the maintenance business connects the diagnostic device 50 to the battery pack mounted on the vehicle, and the diagnostic device 50 measures the battery pack. and perform diagnostic processing. The diagnostic device 50 has a connection interface that is connected to the battery pack, for example, by inserting it into the power supply port of the vehicle. The control unit 51 of the diagnostic device 50 acquires the pack ID of the connected battery pack (in-vehicle battery) to be diagnosed (S21). Here, the control unit 51 uses the RFID reader 57 to read the pack ID from the IC tag attached to the battery pack. The IC tag may store the module ID and the cell ID in addition to the pack ID. In this case, the control unit 51 reads the module ID and the cell ID from the IC tag in addition to the pack ID. In this embodiment, the battery information and vehicle information are registered in the battery DB 112a of the battery management server 110 in association with the pack ID. Each piece of information may be input to diagnostic equipment 50 via operation unit 54 .

The control unit 51 transmits the acquired pack ID to the diagnostic server 120 and requests presentation of a diagnostic algorithm used for diagnostic processing of the battery pack (S22). When the diagnostic device 50 requests presentation of a diagnostic algorithm, the control unit 121 of the diagnostic server 120 selects a diagnostic algorithm to be used for diagnosing the battery pack from the pre-registered diagnostic algorithms (S23). . For example, the control unit 121 acquires battery information and vehicle information related to the battery pack from the battery DB 112a of the battery management server 110 based on the pack ID received from the diagnostic device 50, and based on the battery information or vehicle information, determines which battery to use. Select the diagnostic algorithm to be used. In the diagnostic server 120, for example, diagnostic algorithms corresponding to battery manufacturers, diagnostic algorithms corresponding to EV manufacturers, and diagnostic algorithms corresponding to specifications or model numbers of battery packs are set in advance. The diagnostic algorithm to be used may be determined according to the battery pack or the vehicle in which the battery pack is installed.

The control unit 121 transmits and presents the selected diagnostic algorithm to the diagnostic device 50 (S24). The control unit 51 of the diagnostic device 50 performs measurement processing for measuring the current value, voltage value, temperature, and SOC of the battery by the diagnostic unit 56 (S25). Further, the control unit 51 performs diagnostic processing for estimating the degree of deterioration (SOH) of the battery by the diagnostic unit 56 (S26). Here, the control unit 51 performs diagnostic processing according to the diagnostic algorithm presented by the diagnostic server 120, and estimates the degree of deterioration (SOH) of the battery. The diagnostic algorithm may be designated by the maintenance business or the like. In this case, the diagnostic equipment 50 receives the designation of the diagnostic algorithm via the operation unit 54 and performs diagnostic processing according to the designated diagnostic algorithm. Further, when a battery module or a battery cell disassembled from the battery pack is connected, the diagnosis unit 56 performs measurement processing and diagnosis processing for each module or each cell.

The control unit 51 indicates the results of diagnostic processing (current value, voltage value, temperature, measurement data including SOC, and SOH) and the diagnostic algorithm used for the diagnostic processing in association with the pack ID of the battery to be diagnosed. diagnostic data including the information is transmitted to the diagnostic server 120 (S27). Note that the control unit 51 includes the date and time (diagnosis date and time) at this time, the event (the reason for executing diagnostic processing), device information (for example, the device ID assigned to the device) that can identify the diagnostic device 50, etc. in the diagnostic data. It may be sent to diagnostic server 120 . The event is input via the operation unit 54 by, for example, the maintenance business operator, and is set to "vehicle maintenance" here. The device information is stored in the storage unit 52 in advance, for example.

The control unit 121 of the diagnostic server 120 acquires the diagnostic data transmitted by the diagnostic device 50, and performs repair processing on the battery based on the acquired diagnostic data (current value, voltage value, temperature, SOC, SOH of the battery). is determined, and whether or not repair processing is possible is determined (S28). Then, the control unit 121 adds the determination result (whether or not repair processing is necessary and possible) in step S28 to the diagnostic data received from the diagnostic device 50, and stores the result in the diagnostic DB 122a (S29). Here, the control unit 121 associates the pack ID received from the diagnostic device 50 with the date and time of diagnosis, event, device information, measurement data, SOH, information on the diagnostic algorithm used for the SOH diagnosis, availability of repair processing, Diagnosis data including information on the diagnosis business (diagnosis agency) is stored in the diagnosis DB 122a. Note that the control unit 121 issues a diagnosis ID, assigns the diagnosis ID to diagnosis data, and stores the diagnosis data in the diagnosis DB 122a.

The control unit 121 stores the diagnostic data described above in the blockchain system (S30). Here, the control unit 121 outputs the pack ID and diagnostic data to the node device 10 in association with each other, instructs storage of the diagnostic data in the blockchain system, and is recorded in the blockchain system by the node device 10 . As a result, the diagnostic data including the battery measurement data measured when the diagnostic device 50 is connected to the battery pack to be diagnosed and the degree of deterioration of the battery diagnosed based on the measurement data are transmitted to the diagnostic server 120 and the block. Recorded in the chain system. Therefore, the state of the battery can be traced based on such diagnostic data. Note that the control unit 121 may be configured to store the diagnostic data only in the blockchain system without storing the diagnostic data in the diagnostic DB 122a. A configuration in which only the hash value 172 is stored in the block 170 may be used. Diagnostic processing based on measurement data may be performed by the diagnostic server 120 in addition to the configuration performed by the diagnostic equipment 50 . In this case, the diagnostic server 120 acquires measurement data from the diagnostic device 50, performs diagnostic processing based on the diagnostic algorithm selected in step S23, and acquires battery diagnostic data. Note that when the diagnostic device 50 performs measurement processing and diagnostic processing on a module-by-module or cell-by-cell basis, the control unit 121 determines the degree of deterioration of the entire battery pack based on the measurement data and diagnostic data for each module or cell. You may For example, the control unit 121 may calculate the degree of deterioration of the battery pack based on the SOH value of each cell and the variation in SOH. The degree of deterioration is indicated by, for example, the SOH for the battery or the remaining life of the battery (how many years it will take to reach the end of its life). For example, the control unit 121 may set the minimum value of the SOH of each cell as the SOH for the battery, or may set the average value of the SOH of each cell as the SOH for the battery. The diagnosis server 120 may also diagnose the degree of deterioration of the battery pack in consideration of past measurement data (for example, measurement data by the in-vehicle measurement device 40) of the battery to be diagnosed. In this case, the control unit 121 may acquire the measurement data of the battery pack to be diagnosed from the battery management server 110 or the blockchain system.

The control unit 121 of the diagnostic server 120 generates a diagnostic result screen displaying the diagnostic result and transmits it to the diagnostic device 50 (S31). FIG. 22A shows an example of a diagnosis result screen. The diagnosis result screen shown in FIG. 22A includes the pack ID, module ID, and cell ID of the battery pack to be diagnosed, and as diagnosis results, the date and time of diagnosis, the diagnosis algorithm used for diagnosis processing, the degree of deterioration of the battery (for example, SOH), the diagnosis It displays information on the business operator and information on defective cells that require repair processing. Note that the control unit 121 may calculate the transaction price of the battery pack from the diagnosis result, for example, and display the transaction price on the diagnosis result screen. For example, by registering in advance a calculation formula that defines the relationship between the degree of deterioration of the battery pack and the transaction price, the transaction price of the battery pack whose degree of deterioration has been diagnosed can be calculated.

The control unit 51 of the diagnostic device 50 receives the diagnostic result screen transmitted by the diagnostic server 120 and displays it on the display unit 55 (S32). The diagnosis result screen has an authentication application button for applying for authorization by the battery authentication organization to the battery pack to be diagnosed based on the displayed diagnosis result. The certification by the battery certification organization is based on the fact that the degree of deterioration (for example, SOH) of the battery pack to be diagnosed is equal to or greater than a predetermined value, and that the diagnosis processing that estimates the degree of deterioration has been performed in advance by a pre-certified authorized diagnostic business. It certifies that the diagnostic processing is in accordance with a certified regular diagnostic algorithm, and that the measurement data of the battery used for the diagnostic processing is data measured by a pre-certified measuring instrument. By receiving such certification, the reliability of the value of the battery pack is ensured in the marketplace for battery sales operated by the battery management business operator. You can increase the value of your vehicle.

The maintenance business operator confirms the diagnosis result displayed on the diagnosis result screen, and operates the certification application button if he or she wishes to receive certification from the battery certification body. The control unit 51 of the diagnostic device 50 determines whether or not the authentication application button has been operated on the diagnostic result screen being displayed (S33). end the processing of If it is determined that the authentication application button has been operated (S33: YES), the control unit 51 transmits, for example, the pack ID of the battery pack (battery pack to be authenticated) to the battery authentication server 130, and applies authentication for the battery pack. is transmitted (S34).

The control unit 131 (accepting unit) of the battery authentication server 130 accepts an application for authentication of the battery pack (in-vehicle battery) from the diagnostic device 50. When the application for authentication is accepted, the battery pack to be authenticated has been previously authenticated. Measured measurement data is acquired (S35). For example, the control unit 131 acquires measurement data stored in the measurement DB 112c of the battery management server 110 or the blockchain system. Further, the control unit 131 (acquisition unit) acquires diagnostic data (diagnostic information) for the battery pack to be authenticated (S36). For example, the control unit 131 acquires diagnostic data stored in the diagnostic DB 122a of the diagnostic server 120 or the blockchain system.

The control unit 131 (identifying unit) calculates (identifies) an evaluation score for the battery pack to be authenticated based on the acquired measurement data and diagnostic data (S37). Here, the control unit 131 calculates an evaluation score (evaluation level) for the battery pack to be authenticated according to the contents stored in the score DB 132a. Specifically, the control unit 131 extracts the determination contents registered in the score DB 132a that match the measurement data and diagnostic data of the battery pack, and adds the score corresponding to the extracted determination contents. Then, the evaluation score of the battery pack is calculated. For example, if the measuring device (for example, the in-vehicle measuring device 40) that measures the measurement data of the battery pack is a pre-certified device, 10 points are added to the evaluation score. Also, if the diagnostic device (for example, the diagnostic device 50) that has diagnosed the battery pack is a pre-certified device, 10 points are added to the evaluation score. Further, when the diagnostic algorithm used for diagnosing the battery pack (for example, estimating SOH) is a pre-certified algorithm, 10 points are added to the evaluation score. Furthermore, if the diagnostic company (diagnostic institution) that has diagnosed the battery pack is a pre-certified company (institution), 10 points are added to the evaluation score. In addition, the diagnosis result (e.g. SOH), vehicle mileage, battery pack usage time, charging time and number of times of charging (e.g. each information from new car registration to the present) match the judgment contents registered in the score DB 132a. If so, add the corresponding score to the evaluation score. In this way, by referring to the score DB 132a and calculating an evaluation score according to the measurement data and diagnostic data (diagnostic information) of the battery pack to be authenticated, the details of the measurement processing and diagnostic processing performed on the battery pack are calculated. An evaluation score corresponding to is calculated. In addition to the addition of the predetermined points as described above, the evaluation score is the addition of -100 points (subtraction of 100 points) or 0 if the diagnostic device that diagnosed the battery pack is not a pre-certified device, for example. may be calculated by performing multiplication of . According to such a configuration, when a predetermined condition (determination content) is met, the evaluation score can be set as a determination that authentication should not be granted, and it is possible to indicate that authentication is granted to the battery pack. can be avoided. For example, even if the degree of deterioration is good (the SOH is high), the reliability of the SOH is low if the diagnostic device that has diagnosed the SOH is not certified. In such a case, it is not preferable to give authentication to the battery, so the evaluation score may be calculated so as to be a value to the extent that authentication is not given. As a result, not only the diagnostic results (degree of deterioration) of the battery, but also the equipment and methods used in the diagnostic process are evaluated according to whether or not they are highly reliable, and certification is granted according to this evaluation. You can decide whether to

Note that the evaluation score for the battery pack may be calculated using a trained model generated by machine learning. For example, a learning model composed of a decision tree, a random forest, and an SVM (Support Vector Machine) is trained to output an evaluation score for a battery pack when battery pack measurement data and diagnostic data are input. can be used. In this case, the control unit 131 can input the measurement data acquired in step S35 and the diagnostic data acquired in step S36 to the trained model, and specify the evaluation score based on the output value from the trained model.

Based on the evaluation score calculated for the battery pack, control unit 131 determines whether to grant authentication to the battery pack (S38). For example, the control unit 131 determines to grant authentication when the evaluation score is equal to or greater than a predetermined value, and determines not to grant authentication when it is less than the predetermined value. Thereby, the control unit 131 (determination unit) of the battery authentication server 130 can determine whether or not to grant authentication according to the evaluation score calculated for the battery pack. In addition, the control unit 131 may give different levels of authentication depending on the evaluation score when giving authentication to the battery pack. For example, when the maximum evaluation score is 100, level 3 (high evaluation) certification is given to battery packs with an evaluation score of 90 or more, and level 3 (high evaluation) is given to battery packs with an evaluation score of 80 or more and less than 90. 2 (medium evaluation) certification is given, battery packs with 70 or more points and less than 80 points are given level 1 (low evaluation) certification, and battery packs with less than 70 points are not given certification. good too. Also, different levels of authentication may be granted depending on the content of the diagnostic process. For example, if the degree of deterioration (SOH, remaining life) of the battery is equal to or greater than a predetermined value, but the diagnostic device 50 that has diagnosed the degree of deterioration is a device that has not received predetermined certification, level 1 (low evaluation) certification is given. If the degree of deterioration of the battery is equal to or greater than a predetermined value and the diagnostic device 50 that has diagnosed the degree of deterioration is a device that has received predetermined certification, level 2 (medium evaluation) certification is given and the degree of deterioration is diagnosed. If the diagnostic device 50 is a device that has received a predetermined certification, and as a result of comprehensively evaluating the diagnostic results from a plurality of diagnostic methods, the degree of deterioration of the battery is a predetermined value or more, level 3 (high evaluation). It may be configured to give certification. In such a case, whether or not certification is granted based not only on the degree of deterioration of the battery, but also on whether the diagnostic equipment and diagnostic method (diagnostic algorithm) used to diagnose the degree of deterioration have received a predetermined certification. It is possible to determine whether or not or to switch the authentication level. In the present embodiment, authentication is granted for each battery pack, but authentication may be granted for each battery module, or may be granted for each battery cell.

When the control unit 131 determines not to grant the authentication (S38: NO), the series of processing ends. Note that the control unit 131 may transmit a message indicating that the authentication has not been granted to the diagnostic equipment 50 and notify the diagnostic business via the diagnostic equipment 50 .

If it is determined that authentication is to be granted (S38: YES), the control unit 131 (granting unit) grants authentication to the battery pack (S39). Here, the control unit 131 issues an authentication ID, and generates authentication data including the current date and time (authentication date and time), the event, the evaluation score calculated in step S37, authentication details, and the like. Then, the control unit 131 stores the generated authentication data in the authentication DB 132b in association with the pack ID of the battery pack to be authenticated (S40). The event is the reason for applying for certification. For example, if the application for certification is made when the battery is installed in a new vehicle, it is regarded as "installed in a new vehicle", and if the application for certification is made during maintenance or inspection of the vehicle It is called "vehicle maintenance". If the application for certification is made when the vehicle is sold as a used vehicle, it is classified as "installed in a used vehicle." It is said that The event may be, for example, information input by the maintenance business using the diagnostic device 50, or may be information preset according to the device that requested the authentication application.

The control unit 131 stores the authentication data described above in the blockchain system (S41). Here, the control unit 131 outputs the pack ID and the authentication data in association with each other to the node device 10, instructs storage of the authentication data in the blockchain system, and is recorded in the blockchain system by the node device 10. Accordingly, when the battery authentication server 130 grants authentication to the battery pack, information (authentication data) regarding authentication is recorded and managed in the battery authentication server 130 and the blockchain system. Here too, the control unit 131 may be configured to store the authentication data only in the blockchain system without storing the authentication data in the authentication DB 132b. A configuration in which only the hash value 172 is stored in the corresponding block 170 may be used.

The control unit 131 of the battery authentication server 130 generates an authentication result screen displaying the authentication result for the battery pack and transmits it to the diagnostic device 50 (S42). FIG. 22B shows an example of an authentication result screen. The authentication result screen shown in FIG. 22B displays the pack ID, module ID, and cell ID of the battery pack to which authentication has been granted, and as the authentication result, the date of authentication, information on the battery certification authority that granted authentication, and the authentication level. . The control unit 51 of the diagnostic device 50 receives the authentication result screen transmitted by the battery authentication server 130 and displays it on the display unit 55 (S43). As a result, the content of the authentication given to the battery pack by the battery authentication server 130 (battery authentication organization) is provided to the maintenance business operator.

The maintenance business operator can provide the vehicle manager with the diagnosis result screen provided from the diagnosis server 120 and the authentication result screen provided from the battery authentication server 130, so that the deterioration degree of the battery installed in the vehicle can be obtained. and the content of the authentication given to the battery can be provided to the vehicle manager. Therefore, by requesting maintenance of the vehicle from the maintenance business, the vehicle manager can grasp the degree of deterioration of the battery mounted on the vehicle and the content of authentication. According to the above-described processing, when the vehicle is serviced by the maintenance business, diagnostic processing is performed by the diagnostic device 50 and the diagnostic server 120, and authentication is performed by the battery authentication server 130 (battery authentication organization) according to the diagnostic result. is given. Further, the result of diagnostic processing (diagnostic data) and the result of authentication (authentication data) are accumulated in the diagnostic server 120 or the battery authentication server 130 and the blockchain system. Therefore, the accumulated diagnostic data and authentication data can be used for subsequent diagnostic processing and authorization processing, and the state of the battery can be traced.

In the processing described above, for example, the authentication granting processing executed by the battery authentication server 130 can be realized by a smart contract in a blockchain system. For example, a program is defined in the node device 10 to perform authentication grant processing based on diagnostic data on the condition that battery diagnostic data is registered, and the node device 10 executes the program to perform battery diagnostic processing. The authorization granting process is automatically executed when the diagnosis is made, and authorization is granted according to the diagnosis result.

<Authentication based on application for certification from vehicle manager>
In the information processing system of this embodiment, the authentication of the battery by the battery authentication server 130 can also be executed in response to a request (authentication application) from the vehicle manager. For example, when a vehicle manager is considering selling his/her vehicle, or wants to know the degree of deterioration of the battery installed in his/her vehicle or the authentication status, the vehicle manager applies to the battery authentication server 130 for authorization. do. It should be noted that if the battery authentication server 130 grants the authentication, the value of the vehicle and the selling price can be expected to improve. The vehicle manager can request authentication by transmitting an authentication application to the battery authentication server 130 using his own terminal device. When the vehicle manager applies for authentication using his/her own terminal device, the terminal device and the battery authentication server 130 can perform the same processing as steps S34 to S43 in FIG. In FIG. 21, the processing performed by the diagnostic device 50 is performed by the vehicle manager's terminal device.

The vehicle manager inputs the pack ID of the battery pack for which the authentication application is to be made to his/her own terminal device. For example, the vehicle manager may input the pack ID via the operation unit of the terminal device, and if the terminal device has an RFID reader function, the RFID reader reads the pack ID from the IC tag attached to the battery pack. may be read. The terminal device of the vehicle manager transmits the pack ID of the battery pack to the battery authentication server 130, and transmits an authentication application for the battery pack (S34).

The control unit 131 of the battery authentication server 130 performs the processes of steps S35 to S42 in FIG. It should be noted that if the vehicle in which the battery pack is mounted has not been serviced by the maintenance business, diagnostic data for the battery pack is not stored in the diagnostic DB 122 a of the diagnostic server 120 . Therefore, in this case, the control unit 131 calculates the evaluation score for the battery pack based only on the measurement data acquired in step S35. For example, an evaluation score is calculated based on whether or not the measuring device that measured the measurement data is a pre-certified device, vehicle mileage, battery pack usage time (discharge time), charging time, and number of charging times. . Note that if the vehicle has been serviced by a maintenance business, the evaluation score can be calculated based on the diagnostic data in addition to the measurement data for the battery pack, so a more accurate evaluation score can be obtained.

Then, the control unit 131 of the battery authentication server 130 generates an authentication result screen displaying the authentication result for the battery pack, and transmits it to the terminal device of the vehicle manager (S42). The authentication result screen transmitted by the authentication server 130 is received and displayed on the display unit (S43). As a result, even when a vehicle administrator applies for authentication of a battery pack, the battery authentication server 130 (battery authentication organization) grants authentication to the battery pack, and the content of the granted authentication is verified by the vehicle management. provided to the person Therefore, the vehicle manager can easily grasp the degree of deterioration of the battery pack installed in his/her own vehicle and the content of authentication without requesting an authorized dealer or the like. Also in the above-described process, when the battery authentication server 130 (battery authentication organization) grants authentication, the authentication result (authentication data) is accumulated in the battery authentication server 130 and the blockchain system.

<Authentication based on diagnostic processing by used car operators>
Next, a description will be given of a process in which a used car dealer performs battery diagnostic processing using the diagnostic device 50, and a battery certification body grants certification to the battery based on the obtained diagnostic results. For example, when a used vehicle is sold as a used vehicle, a used vehicle business operator connects a diagnostic device 50 to a battery installed in the vehicle (used vehicle), and performs battery measurement processing and diagnostic processing using the diagnostic device 50. to run. The diagnostic process and authentication grant process based on the diagnostic result at the used car dealer are the same as in FIGS. Incidentally, the diagnostic device 50 in FIGS. 20 and 21 is the diagnostic device of the used car dealer.

20 and 21, the used car dealer can acquire the diagnosis result provided by the diagnosis server 120 and the authentication result provided by the battery authentication server 130. FIG. Therefore, the used car dealer can grasp the degree of deterioration of the battery mounted in the vehicle and the authentication content at any timing. That is, even in the used car business, diagnostic processing is performed by the diagnostic device 50 and the diagnostic server 120, and authentication is granted to the battery by the battery authentication server 130 (battery authentication organization) according to the diagnostic result. Contents of certification are provided. Therefore, when a used car business operator registers a vehicle in a marketplace for used car sales, for example, by registering authentication information indicating the result of authentication by the battery authentication server 130 together with information about the vehicle and measurement data of the battery, , the value of the vehicle and the battery installed in the vehicle can be appealed. Moreover, since the authentication information can be used to explain that the sales price set for the vehicle is a proper price, it is possible to improve the value of the used vehicle.

Also, in the diagnostic processing and authentication granting processing at the used car business, the diagnostic processing results (diagnostic data) and the authentication results (authentication data) are accumulated in the diagnostic server 120 or the battery authentication server 130 and the blockchain system. be. Therefore, the accumulated diagnostic data and authentication data can be used for subsequent diagnostic processing and authorization processing, and the state of the battery can be traced. Even after the vehicle is sold as a used vehicle, the battery measurement processing by the vehicle-mounted measuring device 40 and the accumulation processing of the measurement data in the battery management server 110 (measurement DB 112c) are continued. Therefore, the measurement data measured by the vehicle-mounted measuring device 40 is sequentially accumulated in the measurement DB 112c of the battery management server 110, and can be used for subsequent diagnostic processing and authentication granting processing.

In the above-described processing as well, the authentication grant processing executed by the battery authentication server 130 can be realized by a smart contract in the blockchain system. In this case as well, by defining in the node device 10 a program in which authentication grant processing based on diagnostic data is performed on the condition that the diagnostic data of the battery is registered, the diagnostic processing of the battery can be performed by the used car dealer. The authorization granting process is automatically executed when the diagnosis is made, and the authorization can be granted according to the diagnosis result.

<Certification based on diagnostic processing by dismantling companies>
Next, a description will be given of a process in which a dismantling business performs battery diagnostic processing using diagnostic equipment 60, and a battery certification body grants certification to the battery based on the obtained diagnostic results. For example, when a vehicle to be scrapped is brought in, the dismantling business connects the diagnostic device 60 to the battery mounted in the vehicle, and executes the battery measurement processing and diagnostic processing by the diagnostic device 60 . Note that the dismantling business may, after dismantling the battery from the vehicle to be scrapped, connect the dismantled battery to the diagnostic device 60 and execute the battery measurement process and diagnostic process. The diagnosis processing by the dismantling company and the authorization granting processing based on the diagnosis result are the same as those in FIGS. 20 and 21, so the description is omitted. The diagnostic device 50 in FIGS. 20 and 21 is the diagnostic device 60 of the demolition company.

Through the processing shown in FIGS. 20 and 21 , the dismantling business is also provided with the diagnosis result from the diagnosis server 120 and the authentication result from the battery authentication server 130 . Therefore, the dismantling business operator can grasp the degree of deterioration of the battery removed from the vehicle and the content of authentication at any timing. That is, even in the dismantling business, diagnostic processing is performed by the diagnostic device 60 and the diagnostic server 120, and authentication is given to the battery by the battery authentication server 130 (battery authentication organization) according to the diagnostic result, and the given authentication content is provided. When a dismantler registers a battery dismantled from a vehicle, for example, in a marketplace for battery sales, the dismantling business operator registers the information on the battery and the usage history of the battery (information on the vehicle in which it was installed, etc.) by the battery authentication server 130. By registering the authentication information indicating the authentication result, the value of the battery to be sold can be appealed. Moreover, since the authentication information can be used to explain that the selling price set for the battery is a proper price, it is possible to improve the value of the used battery dismantled from the vehicle.

Also, in the diagnostic processing and authentication granting processing at the dismantling business, the diagnostic processing results (diagnostic data) and authentication results (authentication data) are accumulated in the diagnostic server 120 or the battery authentication server 130 and the blockchain system. . When the battery is dismantled from the vehicle, the dismantling operator uses the diagnostic device 60 or the terminal device to register the date of dismantling in the battery DB 112 a of the battery management server 110 . Specifically, the dismantling operator uses diagnostic equipment 60 or a terminal device to transmit the pack ID of the dismantled battery and the dismantling date to the battery management server 110, and associates the pack ID with the dismantling year. The date is stored in the battery DB 112a. Thereby, the battery management server 110 can manage that the battery mounted on the vehicle has been removed from the vehicle.

In the above-described process as well, the authentication granting process executed by the battery authentication server 130 can be realized by a smart contract in the blockchain system. In this case as well, when the dismantling business performs the battery diagnosis process, the authorization granting process is automatically executed, and the authorization can be granted according to the diagnosis result.

<Diagnostic processing at the reuse business>
Next, the processing performed by the reuse business will be described. A reuse business operator purchases a battery (used battery) from, for example, a marketplace for selling batteries, connects the purchased battery to a diagnostic device 70 , and executes battery diagnostic processing by the diagnostic device 70 . Based on the diagnostic results obtained, the reuse business operator shall replace or repair the module or cell unit, repack the non-defective modules together to assemble the battery pack, or re-modularize the non-defective cells to assemble the battery module. , repair processing (reuse of on-vehicle batteries) such as reuse by incorporating non-defective modules into other battery packs, and reuse by incorporating non-defective cells into other battery modules. In addition, the reuse business performs reuse processing for stationary batteries by rearranging battery packs or battery modules that cannot be used as on-vehicle batteries to construct stationary batteries. It should be noted that the reuse operator performs diagnostic processing again by the diagnostic device 70 on the vehicle battery after the repair processing or the built stationary battery, and applies for certification by the battery certification organization based on the diagnostic result.

The diagnostic processing at the reuse business is the same as steps S21 to S32 in FIG. Note that the diagnostic device 50 in FIG. 20 is the diagnostic device 70 of the reuse business. As a result, since the diagnosis result is provided from the diagnosis server 120 to the reuse business operator, it is possible to grasp the degree of deterioration of the reused battery pack. Reuse business operators check the state of deterioration of battery packs based on the diagnostic results, and if the battery pack cannot be used as a vehicle battery, disassemble it into modules and perform diagnostic processing on a module-by-module basis. Determine whether the module can be used as a vehicle battery. If the battery module cannot be used as an on-board battery, it is further disassembled into individual cells and subjected to diagnostic processing on a cell-by-cell basis to determine whether each battery cell can be used as an on-board battery. do. Based on the diagnostic results, the reuse business confirms the state of deterioration in units of packs, modules, or cells, and reuses packs, modules, and cells that can be used as batteries for vehicles. For example, a module that can be used as an in-vehicle battery is repacked to generate a new battery pack, a cell that can be used as an in-vehicle battery is re-modularized to generate a battery module, and a module or cell that can be used as an in-vehicle battery. is incorporated into another battery pack or battery module for reuse. In addition, the reuse business assembles stationary batteries using packs, modules, and cells that are not usable as batteries for vehicles, but are usable as batteries for stationary use, and reuses them as batteries for stationary use. At this time, the reuse operator connects the assembled stationary battery (battery pack) to the BMS 80 to generate a stationary battery (ESS). If, for example, an SOH of 70% or more is set as a condition for use as an on-vehicle battery, the reuse operator will determine whether the SOH of the battery pack, battery module, or battery cell is 70% or more. to determine whether it can be used as an automotive battery. In addition, if an SOH of 30% or more is set as a condition for the battery to be usable as a stationary battery, the reuse operator shall determine whether the SOH of the battery pack, battery module, or battery cell is 30% or more and less than 70%. Depending on whether the battery can be used as a stationary battery or not, it is determined whether the battery can be used.

When a new vehicle battery is generated, the reuse business operator registers battery information related to the new vehicle battery in the battery DB 112 a of the battery management server 110 . Further, when the reuse business operator generates the stationary battery, it registers the battery information regarding the stationary battery in the stationary battery DB 112 b of the battery management server 110 . FIG. 23 is a schematic diagram showing an example of an input screen for battery information. The screen shown in FIG. 23 may be displayed on the display unit when the diagnostic device 70 executes a predetermined application, or may be displayed on the display unit of the terminal device when the terminal device of the reuse operator executes a predetermined application. may be The input screen shown in FIG. 23 is a screen for inputting information on a battery pack when a new vehicle battery pack or stationary battery pack is generated. The input screen shown in FIG. 23 has check boxes for selecting whether the battery pack to be registered is a new vehicle battery or a stationary battery. In addition, the input screen shown in FIG. 23 includes, as the information of the vehicle battery, the module ID of the battery module repacked into the new vehicle battery, the cell ID of the battery cell of each battery module, the date of repacking, the battery cell It has an input column for inputting each information such as information on repair processing performed in the above. The input screen shown in FIG. 23 includes, as information on the stationary battery, the module ID of the battery module used in the battery pack of the stationary battery, the cell ID of the battery cell of each battery module, and the assembly date of the stationary battery. It has input fields for inputting information such as the date, information on stationary batteries (ESS information), and information on repair processing performed on battery cells and the like. Each input column may be configured such that each information is directly input, or may be configured to be input by displaying a plurality of options and selecting an arbitrary one. The ESS information includes information such as the type and size of the stationary battery, usage conditions, and optimal operating method. The ESS information may also include information on materials such as the types and amounts of materials used in manufacturing the battery and recycled materials. The repair information includes the ID of the battery module or battery cell that has been repaired by the reuse business operator, the contents of the repair process, and the like.

Diagnostic device 70 sends the input battery information to battery management server 110 when reusing the vehicle battery is selected on the battery information input screen, various information on the vehicle battery is entered, and the registration button is operated. It is transmitted and stored in the battery DB 112a. Further, when the reuse of the stationary battery is selected, each information of the stationary battery is input, and the registration button is operated, the diagnostic device 70 transmits the input battery information to the battery management server 110 to perform the stationary battery. stored in the battery DB 112b. As a result, when a new vehicle battery or stationary battery is constructed by a reuse business, battery information related to the new vehicle battery or stationary battery is registered in the battery management server 110 . The battery management server 110 issues a new pack ID for the battery pack when registering the battery information of the new vehicle battery or stationary battery received from the diagnostic device 70 in the battery DB 112a or the stationary battery DB 112b. Then, the battery information is associated with the issued pack ID and stored in the battery DB 112a or stationary battery DB 112b. The pack ID assigned to the stationary battery is issued when the stationary battery is constructed, but the pack ID of the in-vehicle battery before being incorporated into the stationary battery may be used. For the module ID and cell ID of the stationary battery, the ID of the vehicle-mounted battery before being incorporated into the stationary battery is used as it is. Thereby, each battery module and each battery cell in the battery pack used as the vehicle battery can be associated with each battery module and each battery cell in the reused stationary battery. Therefore, it is possible to easily grasp from which in-vehicle battery each battery module and each battery cell in the stationary battery is reused. The pack ID of the battery pack and the module ID of the battery module incorporated in this battery pack are registered in association with information on the period during which the battery module was incorporated in this battery pack. The module ID and the cell ID of the battery cell incorporated in this battery module may be registered in association with information on the period during which the battery cell was incorporated in this battery module. In this case, the correspondence between each battery pack, the battery modules of each battery pack, and the battery cells of each battery module can be managed.

When the battery management server 110 issues pack IDs for new vehicle-mounted batteries and stationary batteries, the battery management server 110 may transmit the issued pack IDs to the diagnostic device 70 to notify the reuse business. The battery management server 110 may output the battery information stored in the battery DB 112a or the stationary battery DB 112b to the node device 10, and the node device 10 may store the battery information in the blockchain system.

After generating a new vehicle-mounted battery or stationary battery, the reuse business connects the diagnostic device 70 to the generated vehicle-mounted battery or stationary battery, and the diagnostic device 70 performs measurement processing and diagnosis processing. The diagnostic process and the authentication grant process based on the diagnostic result here are the same as in FIGS. 20 and 21, and the diagnostic equipment 50 in FIGS.

20 and 21, the diagnostic server 120 provides the reuse operator with the diagnosis result for the new vehicle-mounted battery or the stationary battery, and the authentication result for the new vehicle-mounted battery or the stationary battery is the battery. It is provided by the authentication server 130 . Therefore, the reuse business operator can grasp the degree of deterioration and the content of authentication for the generated vehicle-mounted battery or stationary battery. That is, the diagnostic device 70 and the diagnostic server 120 perform diagnostic processing on a new vehicle battery or stationary battery, and the battery authentication server 130 (battery certification organization) certifies a new vehicle battery or stationary battery according to the diagnosis result. Authentication is given to the used battery, and the content of the given authentication is provided to the reuse operator. When registering a new vehicle-mounted battery or stationary battery, for example, in a marketplace for battery sales, a reuse business operator must submit information about the battery and usage history (information about the vehicle in which it was installed, etc.) to the battery authentication server. By registering the authentication information indicating the authentication result by 130, the value of the battery to be sold can be appealed. In addition, since it is possible to explain with the authentication information that the selling price set for the battery is an appropriate price, the value of the vehicle battery generated by repacking and the stationary battery generated from the vehicle battery is improved. It is possible to

Also, in the diagnostic processing and authentication granting processing at the reuse business, the diagnostic processing results (diagnostic data) and authentication results (authentication data) are accumulated in the diagnostic server 120 or the battery authentication server 130 and the blockchain system. . Therefore, it is possible to view and provide diagnostic data and authentication data for vehicle-mounted batteries and fixed-use batteries generated by reuse processing such as cell repair, remodularization, and repacking.

<Accumulation processing of diagnostic results by BMS 80>
A process of accumulating battery measurement data acquired by the BMS 80 and diagnosis data based on the measurement data in the diagnosis DB 122a of the diagnosis server 120 will be described. A BMS 80 is connected to the stationary battery, and the BMS 80 measures the current value, voltage value, temperature, and SOC of the connected battery at appropriate timing, and calculates the SOH of the battery based on the obtained measurement data. presume. The measurement data and diagnosis data (SOH) thus obtained are accumulated in the diagnosis DB 122a of the diagnosis server 120 and the blockchain system.

FIG. 24 is a flow chart showing an example of an accumulation processing procedure of measurement data and diagnosis data by the BMS 80. As shown in FIG. In FIG. 24 , the processing performed by the BMS 80 is shown on the left side, and the processing performed by the diagnosis server 120 is shown on the right side. The BMS 80 is configured to perform diagnostic processing periodically or at a predetermined timing, and the control unit 81 determines whether or not it is time to perform the diagnostic processing (diagnosis timing) (S51). For example, when the measurement process is executed every predetermined time, the control unit 81 determines whether or not a predetermined time has passed since the most recent diagnostic process was executed. Further, for example, when the diagnosis process is executed once a day at a predetermined time, the control unit 81 determines whether or not the predetermined time has arrived. If it is determined that it is not the diagnostic timing (S51: NO), the controller 81 waits until the diagnostic timing arrives.

When it is determined that it is time to diagnose (S51: YES), the control unit 81 of the BMS 80 and the control unit 121 of the diagnostic server 120 perform the same processes as steps S25 to S30 in FIG. Specifically, the control unit 81 of the BMS 80 performs measurement processing for measuring the current value, voltage value, temperature, and SOC of the battery by the diagnosis unit 84 (S52), and diagnosis processing for estimating the degree of deterioration (SOH) of the battery. (S53). The diagnostic algorithm used for diagnostic processing may be a diagnostic algorithm presented to the BMS 80 in advance from the diagnostic server 120, or may be a diagnostic algorithm designated by the stationary battery administrator.

The control unit 81 associates the pack ID of the battery to be diagnosed (here, the pack ID of the stationary battery) with the result of the diagnosis process (battery current value, voltage value, temperature, measured data including SOC, and The diagnostic data including the SOH of the battery) and the diagnostic algorithm used for diagnostic processing are transmitted to the diagnostic server 120 (S54). In addition, the control unit 81 includes the date and time (diagnosis date and time) at this time, the event (the reason for executing diagnostic processing), the device information (for example, the device ID assigned to the device) that can identify the BMS 80, etc. in the diagnostic data. 120. The event is input in advance by the stationary battery manager via an operation unit (not shown), and is herein referred to as "fixed battery periodic diagnosis".

The control unit 121 of the diagnostic server 120 acquires the diagnostic data transmitted by the BMS 80, and based on the acquired diagnostic data (current value, voltage value, temperature, SOC, SOH of the battery), issues a request for repair processing to the battery. It judges no, and judges whether repair processing is possible or not (S55). Then, the control unit 121 stores the diagnosis data received from the BMS 80 in the diagnosis DB 122a (S56) by adding the determination result (necessity and availability of repair processing) in step S55 to the diagnosis data received from the blockchain system. (S57). Again, the control unit 121 may be configured to store the diagnostic data only in the blockchain system without storing the diagnostic data in the diagnostic DB 122a. A configuration in which only the hash value 172 is stored in the corresponding block 170 may be used. After the process of step S54, the control unit 81 of the BMS 80 returns to step S51, executes the measurement process and the diagnosis process, and repeats the process of transmitting the obtained diagnosis data to the diagnosis server 120 each time the diagnosis timing arrives. The diagnosis server 120 determines whether or not repair processing is necessary and possible each time it receives diagnostic data from the BMS 80, and stores the determination result and diagnostic data in the diagnostic DB 122a and the blockchain system. As a result, the measurement data of the stationary battery measured by the BMS 80 at appropriate timing and the information on whether repair processing is possible are accumulated in the diagnosis server 120 and the blockchain system. Therefore, the state of the stationary battery can also be traced. The diagnosis processing by the BMS 80 is executed at appropriate timings, and the diagnosis results are accumulated, and the diagnosis server 120 does not need to notify the BMS 80 of the necessity of the repair processing and the determination result of the possibility. However, the diagnosis server 120 may be configured to transmit the necessity of repair processing and the determination result of the necessity of repair processing to the BMS 80 , and the necessity of repair processing may be sent to the terminal device of the stationary battery manager who is the owner of the BMS 80 . and the determination result of whether or not it is possible to transmit.

The stationary battery administrator can request (apply for authentication) that the stationary battery be authenticated by the battery authentication server 130 in the same manner as the vehicle administrator. For example, when the stationary battery manager wants to know the degree of deterioration or the authentication status of the stationary battery he/she uses, he/she applies to the battery authentication server 130 for authorization. The stationary battery administrator can request authentication by transmitting an authentication application to the battery authentication server 130 using his own terminal device. When the stationary battery manager applies for authentication using his own terminal device, the terminal device and the battery authentication server 130 can perform the same processing as steps S34 to S43 in FIG. In FIG. 21, the processing performed by diagnostic device 50 is performed by the terminal device of the stationary battery manager.

The stationary battery manager inputs the pack ID of the stationary battery to be authenticated to his terminal device. For example, the stationary battery manager may input the pack ID via the operation unit of the terminal device, and if the terminal device has an RFID reader function, the RFID reader will read the packet from the IC tag attached to the stationary battery. A pack ID may be read. The terminal device of the stationary battery manager transmits the pack ID of the stationary battery to the battery authentication server 130, and transmits an authentication application for the stationary battery (S34).

When the controller 131 of the battery authentication server 130 receives an authentication application for the stationary battery from the terminal device of the stationary battery manager, the controller 131 performs the processes of steps S35 to S42 in FIG. In step S35, the control unit 131 acquires measurement data from the measurement DB 112c of the battery management server 110 as the battery usage history during the period in which the stationary battery was installed in the vehicle and used. In step S36, in addition to the diagnostic data for the stationary battery, the control unit 131 causes the diagnostic server 120 to use the diagnostic data for the period in which the stationary battery was installed and used in the vehicle as the battery diagnosis history. Acquired from DB 122a. Then, in step S37, the control unit 131 calculates an evaluation score for the stationary battery based on the acquired measurement data and diagnosis data.

As a result, for the stationary battery, based on the measurement data and diagnostic data during the period when it was used as an in-vehicle battery before reuse and the measurement data and diagnostic data during the period when it was used as a stationary battery, An evaluation score is calculated for the stationary battery, and authentication is given according to the calculated evaluation score. Therefore, it is determined whether or not the stationary battery is to be authenticated based on the measurement data and diagnostic data from the time of manufacture to the present. Through the above-described process, when the stationary battery administrator applies for authentication of the stationary battery, the battery authentication server 130 (battery authentication organization) grants authentication to the stationary battery, and details of the granted authentication is provided to the stationary battery manager. Therefore, the stationary battery manager can easily grasp the degree of deterioration of his own stationary battery and the authentication details. Also in the above-described process, when the battery authentication server 130 (battery authentication organization) grants authentication, the authentication result (authentication data) is accumulated in the battery authentication server 130 and the blockchain system.

<Diagnostic processing by recycling companies>
Next, the processing performed by the recycling company will be described. For example, when a stationary battery is brought in to be discarded, the recycling company connects the diagnostic device 90 to the battery pack of the stationary battery, and executes diagnostic processing of the battery pack by the diagnostic device 90 . Based on the diagnostic results obtained, the recycling company confirms that the battery pack is worthless and decides to dispose of it.

Diagnosis processing at the recycling company is the same as steps S21 to S32 in FIG. The diagnostic device 50 in FIG. 20 is the diagnostic device 90 of the recycler. As a result, the diagnosis result is provided from the diagnosis server 120 to the recycling company, so that the degree of deterioration of the battery to be discarded can be grasped. The recycling business confirms the state of deterioration of the battery based on the diagnostic result, and decides whether or not to dispose of the battery. In addition, if, for example, an SOH of 30% or more is set as a condition for use as a stationary battery, the recycling operator should dispose of the battery depending on whether the SOH is less than 30%. or not. In addition, when the diagnostic processing is performed on a module-by-module or cell-by-cell basis, the recycling company determines whether or not to dispose of each module or cell. Also in the diagnostic processing at the recycling company, the diagnostic processing results (diagnostic data) are accumulated in the diagnostic server 120 and the blockchain system. Therefore, it is possible to accumulate measurement data during the period until the stationary battery is discarded.

Recycling companies carry out predetermined recycling processes on batteries that are determined to be discarded. First, the recycling company measures the remaining capacity of the battery using, for example, diagnostic equipment 90, and if there is remaining capacity, the battery is completely discharged at a predetermined discharge current value. This prevents electric shock when the battery is disassembled for disposal. Next, the recycling operator uses the diagnostic device 90 or a terminal device to obtain material information of the battery to be discarded from the battery DB 112a of the battery management server 110 or the blockchain system. Based on the acquired material information, the recycling operator determines the components of recyclable materials (hereinafter referred to as recycled materials) contained in the batteries to be discarded. The material information includes component information of the materials used in manufacturing the battery, and the recycling operator determines whether or not the battery contains recycled materials. Recycled materials are rare metal components such as lithium, nickel, cobalt and manganese.

When recycling companies identify the recycled materials contained in batteries, they dismantle the batteries to be discarded, separate the components, and then perform refining or other processes to remove impurities and convert them into high-quality recycled materials (rare metals). components) are extracted. After extracting the recycled material from the battery to be discarded, the recycling operator uses the diagnostic device 90 or a terminal device to register recycling information indicating the details of the recycling process in the stationary battery DB 112b of the battery management server 110. . FIG. 25 is a schematic diagram showing an example of an input screen for recycling information. The screen shown in FIG. 25 is displayed on the display unit when the diagnostic device 90 or the terminal device executes a predetermined application. The input screen shown in FIG. 25 has input fields for inputting information such as the pack ID of the disassembled battery (stationary battery in this case), recycling completion date, recycling company, recycling material, recycling method, and the like. Each input column may be configured such that each information is directly input, or may be configured to be input by displaying a plurality of options and selecting an arbitrary one.

When each information is input via the recycling information input screen and the registration button is operated, the diagnostic device 90 or the terminal device transmits the input pack ID and recycling information to the battery management server 110, and corresponds to the pack ID. and store the recycling information in the stationary battery DB 112b. As a result, when the recycling company performs the recycling process on the battery and extracts the recycling material from the battery, recycling information related to the recycling process is registered in the stationary battery DB 112 b of the battery management server 110 . The battery management server 110 may output the recycling information stored in the stationary battery DB 112b to the node device 10, and the node device 10 may store the recycling information in the blockchain system. In this way, by registering the recycling information indicating that the stationary battery has been recycled in the stationary battery DB 112b, it is possible to feed back the information to each company as necessary.

Through the above-described processing, information about the completed recycling process can be stored in the stationary battery DB 112b, and the battery management server 110 can manage the fact that the stationary battery has been discarded and recycled and the contents of the recycling process. Note that the recycling information stored in the stationary battery DB 112b includes, for example, the weight of the battery material name (e.g., steel, aluminum, copper, resin, LiNiO2, etc.), the recycling processing weight (recycling and waste amount), the recycling rate etc. may be included. This makes it possible to grasp the recycling rate of batteries, processing weight, etc. from a bird's-eye view.

Recycling businesses can obtain certification from battery certification organizations for recycled materials extracted from batteries. The certification here is that the recycled material is extracted from a waste battery and recycled, and the authorized recycling method (recycling process) authorized in advance by an authorized recycling operator authorized in advance is used. It is a recycling certification that proves that it has been done. A recycling company sells the extracted recycled materials, for example, on a marketplace for selling materials. Therefore, when registering recycled materials in the marketplace for selling materials, the recycling company registers authentication information from the battery authentication server 130 together with information about the recycled materials, so that the materials to be sold are recycled materials. I can appeal that. In addition, information on recycling processing (for example, recycling completion date, recycling company, etc.) may be registered in the material sales marketplace. can be disclosed.

The process of obtaining recycling certification from the battery certification organization for recycled materials will be described below. FIG. 26 is a flow chart showing an example of a procedure for providing authentication to recycled materials, and FIG. 27 is a schematic diagram showing an example of a screen. In FIG. 26, the processing performed by the diagnostic device 90 of the recycling company is shown on the left side, and the processing performed by the battery authentication server 130 is shown on the right side. It should be noted that the recycling business operator may use a terminal device instead of the diagnostic device 90 to apply for certification of the recycled material.

The control unit of the diagnostic equipment 90 displays an authentication application screen as shown in FIG. 27A on the display unit when the recycling operator performs a predetermined operation via the operation unit (S61). The certification application screen shown in FIG. 27A is used for inputting information such as a recycled material to be certified, a stationary battery pack ID and module ID from which the recycled material is extracted, a recycling completion date, a recycling company, a recycling method, and the like. It has an input field. Each input column may be configured such that each information is directly input, or may be configured to be input by displaying a plurality of options and selecting an arbitrary one.

When applying for certification of the recycled material by the battery certification organization, the recycling business operator inputs information in each entry field on the certification application screen and operates the certification application button. The control unit of the diagnostic device 90 determines whether or not the authentication application button has been operated on the authentication application screen being displayed (S62), and if the authentication application button has not been operated (S62: NO), a series of End the process. If it is determined that the authentication application button has been operated (S62: YES), the control unit transmits each information input on the authentication application screen to the battery authentication server 130, and transmits an authentication application for the recycled material (S63). .

When the control unit 131 of the battery authentication server 130 receives the authentication application for the recycled material from the diagnostic device 90, it acquires the recycling information on the recycled material input via the authentication application screen on the diagnostic device 90 (S64). Based on the obtained recycling information, the control unit 131 determines whether or not to give certification to the recycled material (S65). The control unit 131 determines that the recycled material is to be certified, for example, when the recycling process for the recycled material is a process according to a recycling method pre-approved by a pre-approved recycling operator. Note that the control unit 131 may calculate an evaluation score according to the recycling company, the recycling method, and the like, and determine whether or not to grant authentication according to the calculated evaluation score. In addition, the control unit 131 determines whether or not to give recycling authentication to the recycled material by considering whether or not the battery authentication server 130 has given authentication to the battery before the decomposition of the recycled material. You may Also, whether or not to grant certification to recycled materials may be specified using a trained model generated by machine learning. For example, it is possible to use a learning model composed of a decision tree or the like, which is learned to output information indicating whether or not to grant certification to the recycled material when information on recycling processing is input. can. In this case, the control unit 131 can input the recycling information acquired from the diagnostic device 90 to the learned model and specify whether or not to grant authentication based on the output value from the learned model.

When the control unit 131 determines not to grant the authentication (S65: NO), the series of processing ends. Note that the control unit 131 may transmit a message indicating that the recycling certification has not been granted to the diagnostic device 90 and notify the recycling operator via the diagnostic device 90 .

If it is determined that the certification is granted (S65: YES), the control unit 131 grants the certification to the recycled material (S66). Here, the control unit 131 generates authentication data including information on the recycled material acquired from the diagnostic device 90, the date at this time (authentication date), authentication information indicating the authentication result, and the like. It is stored in the material authentication DB 132c in association with the material ID issued to the recycled material (S67). Also, the control unit 131 causes the blockchain system to store the authentication data described above (S68). Here, the control unit 131 outputs the material ID and the authentication data in association with each other to the node device 10, instructs storage of the authentication data in the blockchain system, and is recorded in the blockchain system by the node device 10. As a result, when the battery authentication server 130 grants recycling authentication to the recycled material, information (authentication data) related to recycling authentication is recorded and managed in the battery authentication server 130 and the blockchain system.

The control unit 131 of the battery authentication server 130 generates an authentication result screen displaying the authentication result for the recycled material and transmits it to the diagnostic device 90 (S69). FIG. 27B shows an example of an authentication result screen. The authentication result screen shown in FIG. 27B includes the material ID and component of the recycled material to which the recycling certification has been assigned, the pack ID and module ID of the battery from which the recycled material has been extracted, and the authentication result as the date of authentication and the battery authentication to which the authentication has been assigned. View agency information and certification levels. It should be noted that the certification level can be determined according to the recycling business that performed the recycling process, the recycling method, or the like.

The control unit of the diagnostic device 90 receives the authentication result screen sent by the battery authentication server 130 and displays it on the display unit (S70). As a result, the content of the recycling certification given to the recycled material by the battery certification server 130 (battery certification organization) is provided to the recycling operator. When selling recycled materials to which recycling certification has been granted, for example, at a marketplace for material sales, the recycling business registers authentication information from the battery authentication server 130 together with information on the recycled materials, thereby enabling the sale of the materials. You can appeal that the material is a recycled material.

<Battery repair process>
In the information processing system of the present embodiment, the diagnostic server 120 measures the battery based on the battery measurement data measured by the diagnostic devices 50, 60, 70 and the BMS 80, and the SOH of the battery diagnosed based on the measurement data. to determine whether repair or regeneration is possible. When the diagnostic devices 50, 60, 70 and the BMS 80 perform measurement processing and diagnostic processing on a module-by-module or cell-by-cell basis, the diagnostic server 120 determines whether repair or regeneration is possible on a module-by-module or cell-by-cell basis. Alternatively, a process for specifying a cell is performed. For example, if the SOH is less than a predetermined threshold value, repair and regeneration can be disabled, and if the SOH is greater than or equal to the predetermined threshold value, repair and regeneration can be enabled. It should be noted that the threshold value here can be a value to the extent that the battery cannot be used as it is mounted on the vehicle when the battery is mounted on the vehicle, and the battery is used as a stationary battery. In this case, the value can be set to the extent that the battery cannot be used as a stationary battery.

The operator notified by the diagnostic server 120 of whether or not the battery can be repaired or regenerated repairs or replaces a part that can be repaired or regenerated (for example, a defective module or defective cell). Then, each company registers the repair information regarding the repair process performed on the battery in the diagnostic DB 122 a of the diagnostic server 120 . Note that when the reuse business operator replaces a defective module or defective cell when generating a stationary battery, repair information regarding the repair process is registered in the stationary battery DB 112b. As a result, information on battery repair processing performed by each business is stored as diagnostic data in the diagnostic DB 122a of the diagnostic server 120, and is stored in the stationary battery DB 112b of the battery management server 110 as repair information for the stationary battery. . The repair information stored in the diagnosis DB 122a and the stationary battery DB 112b may be stored in a blockchain system.

FIG. 28 is a flowchart showing an example of a repair information registration processing procedure, and FIG. 29 is a schematic diagram showing an example of a screen. In FIG. 28 , the processing performed by the battery management server 110 is shown on the left side, and the processing performed by the diagnostic devices 50 and 60 and the BMS 80 of each of the maintenance/used car business operators, dismantling business operators, and stationary battery managers is shown on the right side. 4 respectively show the processing performed by the diagnosis server 120 . When the control unit 121 of the diagnostic server 120 receives diagnostic data (battery measurement data and SOH) from the diagnostic equipment 50, 60 or the BMS 80, based on the received diagnostic data, the control unit 121 determines whether or not the battery needs to be repaired. It judges (S81). Then, the control unit 121 adds the judgment result (whether or not repair processing is necessary and possible) in step S81 to the received diagnostic data and stores it in the diagnostic DB 122a (S82), and stores the above-described diagnostic data in the blockchain system. (S83). The processing of steps S81 to S83 can be, for example, the processing of steps S28 to S30 in FIG. 20 and steps S55 to S57 in FIG. In step S81, the identification of the module or cell to be repaired is based on the results of diagnostic processing (SOH of each module or cell) performed by the diagnostic device 50, 60 and BMS 80 on a module-by-module or cell-by-cell basis. is executed.

The control unit 121 generates a diagnostic result screen displaying the diagnostic result and transmits it to the diagnostic equipment 50, 60 or BMS 80 (S84). The diagnosis result screen here has the configuration shown in FIG. In addition to the configuration shown in FIG. 22A, the diagnosis result screen shown in FIG. 29 is used for inputting each piece of information such as the operator who repaired the defective cell, the repair method, the cell to be repaired, and the cell ID after repair. It has an input column, a cell ID acquisition button for requesting acquisition of the cell ID of the new cell when the cell is replaced, and a repair completion button for notifying that the repair processing for the cell has been completed. Note that even if the diagnosis result screen is provided with input fields for the module to be repaired and the module ID after repair, and a module ID acquisition button for requesting acquisition of the module ID of a new module when the module is repaired on a per-module basis. good.

The control unit of the diagnostic equipment 50, 60 or BMS 80 receives the diagnostic result screen from the diagnostic server 120 and displays it on the display unit (S85). Therefore, each company confirms the diagnosis result of the degree of deterioration of the battery, and if the defective cell can be repaired, it is repaired. When the operator who performed the repair process replaces the defective cell with a new cell, on the diagnosis result screen, enter the cell ID of the defective cell in the input field of the cell to be repaired and press the Get Cell ID button. to operate. The control unit of the diagnostic equipment 50, 60 or BMS 80 determines whether or not the cell ID acquisition button has been operated on the diagnostic result screen (S86), and if it determines that the cell ID acquisition button has been operated (S86: YES ), the cell ID of the cell to be repaired is transmitted to the battery management server 110, and a request is issued for the cell ID of the new replaced cell (S87).

The control unit 111 of the battery management server 110 issues a new cell ID when a new cell ID is requested from the diagnostic equipment 50, 60 or the BMS 80 (S88). For example, the control unit 111 identifies the module ID of the battery module and the pack ID of the battery pack based on the cell ID of the cell to be repaired, and generates a new cell ID corresponding to the identified pack ID and module ID. issue. When issuing a new cell ID, the control unit 111 updates the cell ID (the cell ID of the repaired defective cell) stored in the battery DB 112a to the new cell ID (S89). Note that when the battery information is stored in the blockchain system, the control unit 111 updates the cell ID stored in the blockchain system to a new cell ID. The controller 111 then transmits the new cell ID to the diagnostic equipment 50, 60 or BMS 80 (S90).

When acquiring a new cell ID from the battery management server 110, the diagnostic device 50, 60 or the control unit of the BMS 80 displays the acquired cell ID in the post-repair cell ID input field on the diagnosis result screen (S91). Thereby, the cell ID of the repaired defective cell can be associated with the cell ID of the new cell after repair. When the control unit of diagnostic equipment 50, 60 or BMS 80 determines that the cell ID acquisition button has not been operated (S86: NO), the process proceeds to step S92.

The company that performed the repair process operates the repair completion button in a state in which information on the repair process (repair company, repair method, cell to be repaired, cell ID after repair) has been entered on the diagnosis result screen. The control unit of the diagnostic equipment 50, 60 or BMS 80 determines whether or not the repair completion button has been operated on the diagnosis result screen (S92), and if the repair completion button has not been operated (S92: NO), the series end the processing of When determining that the repair completion button has been operated (S92: YES), the control unit transmits the input repair information to the diagnosis server 120 (S93).

When the control unit 121 of the diagnostic server 120 acquires the repair information from the diagnostic equipment 50, 60 or the BMS 80, it stores the repair information in the diagnostic DB 122a (S94). Here, the control unit 121 stores the acquired repair information as repair information included in the diagnostic data stored in the diagnostic DB 122a in step S82. When the repair information includes the cell ID of the defective cell and the cell ID of the cell after replacement, the control unit 121 replaces the cell ID of the defective cell stored in the diagnosis DB 122a with the cell ID of the cell after replacement. keep it updated. Thereby, in the diagnosis DB 122a, the diagnosis result indicated by the diagnosis data can be associated with the repair information, and the information of the repaired cell can be grasped according to the diagnosis result. In addition, the control unit 121 outputs, for example, the battery ID (pack ID, module ID, and cell ID) and the repair information in association with each other to the node device 10, and the node device 10 records the repair information in the blockchain system ( S95). As a result, battery repair information repaired by each business is recorded and managed in the blockchain system.

A business operator who performed repair processing on the battery, for example, a maintenance/used car business operator and a dismantling business operator, after registering repair information related to the repair processing in the diagnostic DB 122a of the diagnostic server 120, applies diagnostic equipment 50 and 60 to the repaired battery. are connected, and the battery measurement processing and diagnosis processing by the diagnostic devices 50 and 60 are executed again. The diagnosis processing and the authorization granting processing based on the diagnosis result here are the same as in FIGS. 20 and 21 .

20 and 21, the diagnosis result of the repaired battery is provided from the diagnosis server 120, and the authentication result of the repaired battery is provided from the battery authentication server 130 to the operator who performed the repair process. be. Therefore, the company that performed the repair process can grasp the degree of deterioration of the repaired battery and the details of authentication. When the battery cell is repaired, the SOH of the cell is improved, so the evaluation score for the cell increases, and as a result, the evaluation score for the battery as a whole also increases. Therefore, the battery after repair can be properly certified based on the improved evaluation score. Also in the diagnosis processing and authorization granting processing for the battery after repair, the diagnosis processing result (diagnosis data) and the authentication result (authentication data) are accumulated in the diagnosis server 120 or the battery authentication server 130 and the blockchain system.

By the above-described processing, the diagnostic processing for the battery is performed by the diagnostic equipment 50, 60 or the BMS 80 and the diagnostic server 120, and when repair processing is performed on a portion that can be repaired and regenerated, the repair information regarding the repair processing is sent to the diagnostic server. 120 and the blockchain system. Therefore, by registering the repair information in advance, it becomes possible to carry out the diagnostic process in consideration of the repair information in the subsequent diagnostic process, and to obtain an appropriate diagnostic result. In addition, by performing the diagnosis process and the authorization process again for the repaired battery, it is possible to acquire and manage the latest diagnosis result and authentication result for the repaired battery. The replaced defective module or defective cell is transported to, for example, a recycling company, and recycled materials are extracted and recycled by the recycling company.

Similar repair processing can be performed by reuse businesses, and repair information can be registered when repair processing is performed. The reuse operator performs diagnostic processing on the used battery by the diagnostic device 70, performs repair processing of the battery based on the obtained diagnostic result, and regarding battery modules and battery cells that cannot be used as on-vehicle batteries, Perform processing to replace the battery with a stationary one. When the reuse business operator generates the stationary battery, it stores the repair information regarding the stationary battery in the stationary battery DB 112b. As a result, the repair information regarding the repair process performed when the stationary battery is generated is registered in the battery management server 110 and the blockchain system as the stationary battery repair information. Therefore, by registering the repair information in advance, it becomes possible to carry out a diagnosis process in consideration of the repair information in the subsequent diagnosis process, and obtain an appropriate diagnosis result. In addition, reuse business operators can acquire and manage the latest diagnostic results and certification results for batteries after repair by performing diagnostic processing and authorization processing again for automotive batteries and stationary batteries after repair. can do.

Recycling businesses can also carry out similar repairs. The recycler may, for example, remediate modules and cells that are rendered usable by remediation. In addition, the recycling company executes the diagnostic processing by the diagnostic device 90 for the modules and cells that have been repaired, and performs the diagnostic processing and the authorization processing again for the modules and cells after the repair. may obtain the latest diagnostic results and authentication results for each module and cell. When a module or cell is repaired, the recycling operator registers information on the module or cell, repair information, post-repair diagnostic results and authentication results in, for example, a marketplace for battery sales, and sells the information to the marketplace. May be sold through the Place.

<Authentication history browsing process>
In the information processing system of the present embodiment, as described above, when each event occurs in the battery, diagnostic processing and authentication grant processing based on the diagnostic results are performed on the battery, and diagnostic data and authentication data are accumulated. In the information processing system of this embodiment, the authentication data stored in the authentication DB 132b of the battery authentication server 130 or in the blockchain system can be viewed by each business operator using a terminal device.

FIG. 30 is a flow chart showing an example of an authentication data browsing process procedure, and FIG. 31 is a schematic diagram showing an example of a screen. In FIG. 30, the processing performed by the terminal device of each business is shown on the left side, and the processing performed by the battery authentication server 130 is shown on the right side. When the battery authentication server 130 grants authentication to the battery, it provides the authentication requester with an authentication result screen as shown in FIG. 31A, for example. Note that the process of granting authentication to the battery is, for example, the process of step S40 in FIG. The authentication result screen shown in FIG. 31A displays a QR code (registered trademark) in addition to the same configuration as in FIG. 22B. The QR code is, for example, a coded authentication ID (authentication code) assigned to authentication given to the battery. By reading the QR code, an authentication ID that can specify the authentication information of the battery can be obtained. . Note that the QR code may include the pack ID of the battery.

The terminal device of each business acquires an authentication ID by reading the pack ID of the battery whose authentication history is to be browsed or the QR code in the authentication result screen of FIG. 31A (S101). The battery pack ID may be input, for example, by each business operator from the operation unit of the terminal device, or if the terminal device has an RFID reader function, the RFID reader may read the ID from the IC tag attached to the battery pack. good. The terminal device of each business operator determines whether or not viewing of the authentication history has been requested via the operation unit (S102), and if it determines that viewing of the authentication history has not been requested (S102: NO). , ends the series of processes.

When the terminal device of each operator determines that viewing of the authentication history is requested (S102: YES), it transmits the pack ID or the authentication ID acquired in step S101 to the battery authentication server 130, and the pack ID or the authentication ID The history of authentication data for the corresponding battery is requested (S103).

When the control unit 131 of the battery authentication server 130 accepts a request for the history of authentication data (authentication history) for the corresponding battery by designating the pack ID or the authentication ID from the terminal device of one of the business operators, the pack Authentication data corresponding to the ID or authentication ID is extracted from the authentication DB 132b or the blockchain system (S104). When extracting from the blockchain system, the battery authentication server 130 requests any of the node devices 10 to view the authentication data corresponding to the pack ID. The node device 10 searches the block chain system using the requested pack ID as a key, extracts authentication data corresponding to the pack ID, and outputs the authentication data to the battery authentication server 130 .

Control unit 131 of battery authentication server 130 generates an authentication history screen based on the extracted authentication data (S105). FIG. 31B shows an example of an authentication history screen. The authentication history screen shown in FIG. 31B displays, for each certification given to the battery, the certification date, the event when the certification application was made, the evaluation score calculated for the battery, the certification details, and the like. In the example of FIG. 31B, as events, installation on a vehicle (new vehicle), vehicle maintenance, installation on a vehicle (used vehicle) (sold as a used vehicle), etc. are displayed. are presenting.

The control unit 131 of the battery authentication server 130 transmits the generated authentication history screen to the terminal device that requested viewing (S106). Thereby, the control unit 131 outputs the history information of the authentication given to the battery in response to the request received from the terminal device. Upon receiving the authentication history screen from the battery authentication server 130, the terminal device displays the authentication history screen on the display unit (S107). This makes it possible to present the user (each business operator) with the authentication given to the battery at each event. Therefore, each company can grasp the grant status of authentication for batteries to which pack IDs or authentication IDs have been assigned. Note that when the battery is dismantled from the vehicle and used as a stationary battery, the grant status of authentication for the stationary battery is extracted from the authentication DB 132b or the blockchain system and presented. Furthermore, when the battery is discarded and disassembled into recycled materials, the status of granting recycling certification to the disassembled recycled materials is extracted from the material certification DB 132c or the blockchain system and presented. This makes it possible to present a history of certifications (including recycling certifications) granted by the battery certification server 130 during the period from the manufacture of the battery to the disassembly and recycling of the battery, and to determine the value of the battery depending on the certification status. can be evaluated.

FIG. 32 is a schematic diagram showing another example of the authentication history screen. The authentication history screen shown in FIG. 31B shows the authentication history when the battery is installed in the vehicle (new vehicle and used vehicle) and used. FIG. 32 shows the authentication history when the battery is used as a stationary battery after being mounted on a vehicle. The authentication history screen shown in FIG. 32 shows, for each battery module constituting the stationary battery, the authentication given to each battery module, the date of authentication, the event when applying for authentication, and the evaluation of the battery calculated at the time of authentication. Displays the score, authentication details, etc. In the example of FIG. 32, as an event, in addition to mounting on a new car, vehicle maintenance, mounting on a used car (sold as a used car), reuse is displayed, and authentication is given when the battery is reassembled into a stationary battery. It also presents the contents of

Stationary batteries are constructed by disassembling and rearranging battery packs that have been used as automotive batteries, for example, into battery modules. . Therefore, the authentication history screen shown in FIG. 32 displays authentication information of authentication given to each battery module. The authentication history screen shown in FIG. 32 is provided to the terminal device of, for example, the reuse business operator, the stationary battery manager, or the recycling business operator by the battery authentication server 130 executing the process shown in FIG. Note that in step S104 in FIG. 30, the control unit 131 of the battery authentication server 130 determines from the pack ID for which the authentication history is requested (here, the pack ID of the stationary battery) the battery included in the battery pack with this pack ID. Identify the module ID of the module. The module ID of the battery module included in the stationary battery can be obtained from the stationary battery DB 112b of the battery management server 110, for example. Then, the control unit 131 extracts authentication data corresponding to the specified module ID from the authentication DB 132b or the blockchain system.

The control unit 131 of the battery authentication server 130 generates an authentication history screen based on the authentication data extracted in this way, and provides it to the terminal device of each business operator. As a result, in a stationary battery configured by rearranging a plurality of battery packs used as on-vehicle batteries, it is possible to present information on authentication given to each battery module to each business operator. Note that the authentication history screen may be configured to present authentication data for each battery module as in the example of FIG. It may be configured to

<Collaboration with insurance companies>
In the information processing system of this embodiment, an insurance product for guaranteeing the operation of the battery pack to be sold is sold. For example, an insurance product may be conceived that covers the cost of replacing the battery pack or repairing the battery cells when the battery pack deteriorates rapidly. Sudden deterioration of the battery pack can be judged, for example, when the SOH of the battery has decreased by a predetermined value or more in a predetermined period. For example, if the SOH drops by 20% or more in one month, it may be determined that rapid deterioration has occurred. In this embodiment, for example, when a battery pack is mounted on a vehicle (new vehicle) and sold, when it is sold as a used vehicle, and when it is sold as a stationary battery, each battery pack is subjected to Insurance policies may be possible. The diagnostic server 120 of the present embodiment is used by the maintenance/used car business operators, the dismantling business operators, the reuse business operators, and the stationary battery management business operators to diagnose the SOH of the battery by the diagnostic devices 50, 60, 70 and the BMS 80. In this case, it is determined whether or not the battery pack has deteriorated rapidly, and if the battery pack is covered by insurance, it is configured to notify each business operator and the insurance business operator.

FIG. 33 is a flowchart showing an example of a battery pack diagnosis processing procedure, and FIG. 34 is a schematic diagram showing an example of a screen. In FIG. 33, on the left side, diagnostic equipment 50, 60, 70 and BMS 80 of maintenance/used car companies, dismantling companies, reuse companies, and stationary battery managers perform processing, and a diagnostic server 120 in the center. The processing performed by the insurance provider server 140 is shown on the right side. When the control unit 121 of the diagnostic server 120 receives diagnostic data (battery measurement data and SOH) from the diagnostic equipment 50, 60, 70 or the BMS 80, based on the received diagnostic data, the control unit 121 determines whether or not the battery needs to be repaired. It is determined whether it is possible (S111). Then, the control unit 121 adds the determination result (whether or not repair processing is necessary and possible) in step S111 to the received diagnostic data, and stores it in the diagnostic DB 122a (S112), and stores the above-described diagnostic data in the blockchain system. (S113). The processing of steps S111 to S113 can be, for example, the processing of steps S28 to S30 in FIG. 20 and steps S55 to S57 in FIG.

The control unit 121 requests the insurance provider server 140 for insurance information regarding the insurance product contracted for the battery to be diagnosed (S114). For example, the control unit 121 transmits information on the pack ID of the battery to be diagnosed and the owner of the battery (for example, vehicle manager, stationary battery manager) to the insurance provider server 140 to request insurance information. When receiving a request for insurance information from the diagnostic server 120, the control unit 141 of the insurance provider server 140 reads the requested insurance information from the insurance DB 142a and the policyholder DB 142b, and sends the read insurance information to the requesting diagnostic server 120. (S115). For example, based on the pack ID received from the diagnostic server 120 or information on the owner of the battery, the control unit 141 identifies the insurance product contracted for the battery from the contents of the policyholder DB 142b. And the control part 141 reads the information regarding the specified insurance product from insurance DB142a and policyholder DB142b. The control unit 141 transmits insurance information including, for example, an insurance business operator, an insurance product name, an insurance contract ID, a policyholder's name, a battery to be compensated, and details of compensation to the diagnostic server 120 that is the source of the request.

The control unit 121 of the diagnostic server 120 determines whether or not the battery is covered by insurance based on the insurance information acquired from the insurance provider server 140 (S116). For example, when the compensation condition is set such that the SOH has decreased by a predetermined value or more in a predetermined period, the control unit 121 calculates the temporal change in SOH in the predetermined period, and sets the compensation condition based on the calculated temporal change. determine whether or not it is satisfied. Specifically, the control unit 121 (acquisition unit), in addition to the degree of deterioration (SOH) acquired from the diagnostic equipment 50, 60, 70 or the BMS 80, the past diagnostic data (degree of deterioration) from the diagnostic DB 122a or the blockchain system to get If there is no past diagnostic data, it may be determined that the vehicle is not subject to compensation. The control unit 121 calculates the difference between the past degree of deterioration (SOH) and the degree of deterioration (SOH) acquired from the diagnostic equipment 50, 60, 70 or the BMS 80, and acquires the temporal change of the SOH. Note that when the degree of decrease in SOH for a predetermined period is set as the compensation condition, the control unit 121 compares the SOH before the predetermined period and the current SOH (the SOH acquired from the diagnostic equipment 50, 60, 70 or the BMS 80). Calculate the difference between Then, the control unit 121 (determination unit) determines whether or not the calculated difference (temporal change) is equal to or greater than a predetermined value. If so, it is determined that it is not eligible for compensation.

In addition to conditions based on the degree of deterioration (SOH) of the battery, the compensation conditions include charging data related to the charging history such as battery usage time, charging time and number of charging times, and vehicle running if the battery is installed in the vehicle. The condition may be based on battery measurement data such as distance. Compensation conditions based on battery measurement data are, for example, when the SOH drops by a predetermined value or more when the traveled distance is less than a predetermined distance, and when the battery usage time or charging time is less than a predetermined time, the SOH is a predetermined value or more. This includes the case where the SOH has decreased by a predetermined value or more when the number of times the battery has been charged is less than a predetermined number of times. In the case of compensation conditions based on battery measurement data, the control unit 121 acquires the battery measurement data from, for example, the measurement DB 112c of the battery management server 110 or the blockchain system, and the compensation conditions are met based on the acquired measurement data. It is determined whether or not the battery is covered by insurance.

In addition, the compensation condition may be a condition based on whether or not the battery is certified, or a condition based on the level of certification given to the battery, and is based on the evaluation score calculated when the battery is authenticated. It can be a condition. For example, if the SOH of a battery that has been certified has decreased by a predetermined value or more, if the SOH of a battery that has been certified at a predetermined level or more has decreased by a predetermined value or more, the SOH of a battery that has an evaluation score of a predetermined value or more This includes conditions such as when the In the case of a compensation condition based on the authentication or evaluation score given to the battery in this way, the control unit 121 acquires the authentication data and evaluation score of the battery from, for example, the authentication DB 132b of the battery authentication server 130 or the blockchain system, Based on the obtained authentication data or evaluation score, it is determined whether or not the compensation conditions are met, and whether or not the battery is covered by insurance.

The compensation condition may be a condition combining a plurality of conditions based on the degree of deterioration (SOH) of the battery as described above, a condition based on the measurement data of the battery, a condition based on the certification given to the battery or an evaluation score for the battery. good. Also, the compensation conditions are not limited to the conditions described above. For example, a condition based on a discharge curve (discharge curve) that indicates the discharge characteristics of the battery can also be used. A discharge curve is data that indicates a change characteristic of a voltage value with respect to a discharge capacity. The conditions based on the discharge curve include, for example, the shape of the discharge curve (S-shaped curve) and the condition based on the average value of the voltage values when the remaining capacity is 40% to 60%. In the case of the compensation condition based on the discharge curve, the control unit 121 causes the diagnostic device 50, 60, 70, 90 or the BMS 80 to measure the discharge curve of the battery, acquires the measurement result, and the acquired discharge curve matches the compensation condition. decide whether to

If it is determined not to be compensated (S116: NO), the control unit 121 generates a diagnostic result screen as shown in FIG. 22A and transmits it to the diagnostic equipment 50, 60, 70 or BMS 80 (S119). Since the BMS 80 periodically performs diagnostic processing and accumulates diagnostic results, the diagnostic server 120 does not need to transmit the diagnostic result screen to the BMS 80, but the diagnostic server 120 sends the diagnostic result screen to the BMS 80 or It may be configured to transmit to the terminal device of the stationary battery manager. The control unit of the diagnostic equipment 50, 60, 70 displays the diagnostic result screen received from the diagnostic server 120 on the display unit (S120), and presents the diagnostic result to each company.

If it is determined that compensation is required (S116: YES), the control unit 121 generates a compensation notification screen as shown in FIG. 34 and transmits it to the diagnostic equipment 50, 60, 70 or BMS 80 (S117). Here too, the diagnostic server 120 may transmit the compensation notification screen to the BMS 80 or the terminal device of the stationary battery manager to notify the stationary battery manager. The compensation notification screen shown in FIG. 34 displays the insurance information provided from the insurance provider server 140 to the diagnosis server 120 in addition to the structure of the diagnosis result screen shown in FIG. 22A. Specifically, a message indicating that there is insurance for which benefits can be received, insurance business information, insurance product name, insurance contract ID, policyholder name, information on the battery to be compensated (for example, pack ID) , information on the content of compensation for benefits, etc. will be displayed. In addition to this information, the compensation notification screen may display information related to procedures necessary for receiving benefits. Therefore, the control unit 121 (output unit) can provide compensation information based on available insurance products to each business operator when the battery to be diagnosed is covered by insurance. The diagnosis server 120 provides compensation information for batteries mounted in vehicles (in-vehicle batteries), for example, to maintenance/used car operators and dismantling operators, and provides compensation information for stationary batteries to reuse operators. do.

The control unit of the diagnostic equipment 50, 60, 70 displays the compensation notification screen received from the diagnostic server 120 on the display unit (S118), and presents the diagnostic results and compensation information to each company. Therefore, each business operator can confirm the diagnosis result of the degree of deterioration of the battery, and can understand that it is possible to receive insurance benefits for the repair processing of the defective cell. As a result, each business operator, when repairing a defective cell, can claim the cost of the repair process from the insurance business operator without forgetting. In addition, if the content of compensation is, for example, the dispatch of a technician to repair a defective cell or the replacement of a new battery module or battery pack, each business operator may request the dispatch of a repair technician or replace the battery with a new battery as necessary. Insurance coverage can be obtained by requesting delivery of the module or battery pack.

The diagnostic server 120 is configured to transmit the compensation notification screen not only to the business operator that performed the diagnostic processing, but also to the terminal devices of the vehicle manager and stationary battery manager who are the owners (users) of the battery. may be In this case, the diagnosis server 120 can notify the vehicle manager and the stationary battery manager that there is insurance that allows them to receive benefits. Since the contact information of the vehicle manager and the stationary battery manager is registered in the insurance company server 140 as the information of the contractor, the insurance company server 140 responds to the request from the diagnosis server 120. , the vehicle administrator and the stationary battery administrator that there is insurance that allows payment of benefits.

When the diagnostic server 120 acquires battery measurement data and diagnostic data from the diagnostic equipment 50, 60, 70 or the BMS 80 through the above-described processing, whether or not the battery is subject to compensation by the contracted insurance product It is possible to determine whether or not, and notify each business operator or the user of the battery. In the above-described process, the control unit 121 of the diagnostic server 120, based on the battery measurement data and diagnostic data acquired from the diagnostic equipment 50, 60, 70 or the BMS 80, determines the operating status of the EV, the usage environment of the battery, and the charging It may be configured such that it is determined whether or not the implementation status of the above is in a predetermined situation, and if the battery is used in the predetermined situation, the battery is not subject to compensation. Predetermined situations include usage in which the deterioration of the battery progresses rapidly, charging in a charging method, etc. For example, when the battery is always being charged by rapid charging, the EV is operated with sudden acceleration and braking. Including cases where By adopting such a configuration, batteries used in usage and charging methods that rapidly degrade the batteries are excluded from the scope of compensation, and the insurance business operator's burden of benefits increases inadvertently. can be suppressed.

Modified examples of the insurance content will be described below. In the configuration described above, the content of the insurance is covered when the compensation conditions are satisfied, but the insurance is not limited to such insurance. For example, when a battery deteriorates rapidly, an insurance product is conceivable in which whether or not the battery should be compensated and the contents of compensation differ according to the certification given to the battery or the evaluation score of the battery. With such an insurance product, even if the degree of deterioration is the same, it is possible to provide more complete coverage as the certification given to the battery or the evaluation score calculated for the battery is higher. Therefore, it is necessary to provide appropriate compensation depending on how the battery is used and how it is diagnosed (for example, whether the battery is regularly diagnosed, whether the battery is diagnosed using an appropriate diagnostic method, etc.). becomes possible. The content of compensation here is, for example, if the SOH decreases by 20% or more in one month, and if the certification level is 2 or higher, the cost required for repairing the cell will be paid, and in one month If the SOH drops by 20% or more, and if the authentication level is 3 or higher, it is conceivable to pay the cost required for replacing the cell.

FIG. 35 is a flow chart showing another example of the battery pack diagnostic processing procedure. The process shown in FIG. 35 is obtained by adding steps S121 and S122 before step S116 to the process shown in FIG. 33, and adding step S123 between YES in step S116 and step S117. In the process shown in FIG. 35, when the control unit 121 of the diagnosis server 120 acquires the insurance information from the insurance provider server 140, when determining whether the battery is covered by insurance, the authentication data for the battery is It is determined whether or not it is necessary (S121). For example, if the compensation conditions included in the insurance information include certification given to the battery or conditions based on the evaluation score of the battery, it is determined that certification data is necessary. Compensation conditions that require authentication data include, for example, "when certification with a certification level of 2 or higher is granted," and "when an evaluation score is 80 points or higher." When determining that the authentication data for the battery is not required (S121: NO), the control unit 121 skips the process of step S122 and proceeds to the process of step S116. Here, the diagnosis server 120 and each device 50, 60, 70, 80 may perform the processing of steps S116 to S120 described with reference to FIG.

When determining that the authentication data for the battery is required (S121: YES), the control unit 121 acquires the authentication data corresponding to the battery from the authentication DB 132b or the blockchain system (S122). Here, the control unit 121 acquires the content of authentication given to the battery (whether or not authentication is given, the authentication level, etc.) and the evaluation score when the authentication is given. Based on the insurance information acquired from the insurance provider server 140, the SOH diagnosed by the diagnostic equipment 50, 60, 70 or the BMS 80, and the acquired authentication data, the control unit 121 determines whether the battery is covered by insurance. It is determined whether or not there is (S116). Here, too, the compensation conditions include, in addition to conditions based on the degree of deterioration (SOH) of the battery and conditions based on the certification given to the battery, charging data related to the charging history such as battery usage time, charging time and number of charging times, If the battery is installed in the vehicle, the conditions based on the measurement data of the battery such as the travel distance of the vehicle may be included.

If it is determined that the battery is subject to compensation (S116: YES), the control unit 121 identifies the content of compensation based on the insurance information acquired from the insurance provider server 140 (S123). For example, if the content of the insurance is ``If the certification level is 2 or higher, the costs required for repairing the cell will be paid, and if the certification level is 3 or higher, the cost for replacing the cell will be paid.'' If the contents of the compensation are "to pay the cost" and the battery has been granted authentication with an authentication level of 2, the control unit 121 specifies "repair of the cell" as the content of the compensation. Then, the control unit 121 generates a compensation notification screen for notifying the diagnosis result and compensation content, and transmits it to the diagnostic equipment 50, 60, 70 or BMS 80 (S117). The compensation notification screen here has the same configuration as that shown in FIG. The content will be according to

In the above-described process as well, when the diagnostic server 120 acquires battery measurement data and diagnostic data from the diagnostic equipment 50, 60, 70 or the BMS 80, is the battery subject to compensation by the insurance product contracted for the battery? It is possible to determine whether or not it is possible to notify each business operator or the user of the battery. Here, it is possible to present different compensation contents according to not only the degree of deterioration of the battery but also the certification details (certification level) given to the battery. becomes possible. Therefore, for example, when the battery deteriorates rapidly, the higher the authentication level given to the battery, the more substantial compensation can be provided. In the process shown in FIG. 35 as well, if the battery is used in a usage and charging method that rapidly deteriorates the battery, the battery may be excluded from compensation.

In the information processing system of the present embodiment, the content of compensation by the insurance product sold by the insurance business is not limited to payment of expenses required for repair processing of defective parts. For example, if the charging efficiency of the battery decreases as the battery deteriorates and the amount of charge in the battery increases, an insurance product with a compensation content that pays the electricity charge (electricity charge) required for the increased amount of charge can be considered. . With such an insurance product, it is possible to determine whether or not the battery is subject to compensation according to the degree of deterioration (SOH) of the battery, and to determine the content of compensation (for example, the upper limit of the power rate to be paid). In addition to the degree of deterioration of the battery, it is possible to determine whether or not the battery is subject to compensation according to the authentication content (authentication level) of the battery, and determine the content of compensation. Furthermore, the insurance premium of the insurance product may be set according to the authentication level of the battery to be compensated. Also, the insurance premium for continuing the insurance contract may be set according to the authentication level of the battery at the time of renewal of the contract. For example, the higher the authentication level, the larger the discount amount, and the amount obtained by subtracting the discount amount from the normal insurance premium may be used as the insurance premium. In addition, when purchasing a new insurance product when switching to a new car, by switching the battery covered by the insurance product for the contracted insurance product to the battery installed in the new car, the coverage content of the contracted insurance product can be changed. may be configured to inherit from In this case, if the policyholder maintains a high certification level by using the battery in an appropriate manner, it will be possible to continue the insurance contract with substantial coverage.

The insurance information managed by the insurance company is not limited to the structure provided from the diagnosis server 120 to each company when the diagnosis server 120 executes the battery diagnosis process. For example, insurance information may be provided to each business operator and user by accessing insurance business server 140 using a terminal device by each business operator and battery user. In this case, each business operator and user input the pack ID of the battery for which insurance information is to be viewed using a terminal device, and the content of the insurance product contracted for the battery with the input pack ID is sent to the insurance business server. Request to 140. The insurance business server 140 responds to requests from the terminal devices of each business operator and the user by outputting the insurance information of the insurance product contracted for the battery to each terminal device. can be provided to

<Provision of advice based on diagnosis results>
The information processing system of the present embodiment has a configuration for providing advice on how to use the battery, etc., in accordance with the diagnosis result, in addition to the result of diagnosis processing by the diagnosis server 120 . The diagnosis server 120 stores an advice DB 122b in the storage unit 122 in addition to the configuration shown in FIG.

FIG. 36 is a schematic diagram showing a configuration example of the advice DB 122b. The advice DB 122b stores advice to be provided to each business operator or battery user (vehicle manager and stationary battery manager) according to the battery diagnostic results. The advice DB 122b shown in FIG. 36 includes an advice ID column, an advice content column, a provision condition column, and the like, and provides advice content and each piece of advice in association with identification information (advice ID) for identifying advice. It stores the provision conditions that should be provided. The advice is, for example, content related to how to use the battery or the vehicle according to the degree of deterioration of the battery, and includes content related to the method of driving the vehicle, the parking environment of the vehicle, the charging method of the battery, and the like. The advice on how to drive the vehicle includes, for example, refraining from sudden start and sudden braking (sudden stop), and gently accelerating and braking. Parking environment advice may include, for example, using a covered or indoor parking lot to keep the vehicle out of direct sunlight. The advice regarding the charging method of the battery includes, for example, refraining from rapid charging and charging after the charging amount has decreased to a certain level (for example, the SOC is about 30%). Further, the advice may include contents related to the travel distance of the vehicle, battery usage time (discharge time), charging time, and the number of charging times. The conditions for provision can be, for example, conditions based on the SOH of the battery and conditions based on the residual value of the battery. As the remaining value of the battery, the remaining cruising distance, usable time, etc. calculated based on the SOC and SOH of each cell can be used.

FIG. 37 is a flowchart showing an example of a battery pack diagnosis processing procedure, and FIG. 38 is a schematic diagram showing an example of a screen. In FIG. 37 , the processing performed by diagnostic equipment 50, 60, 70 and BMS 80 of each business is shown on the left side, and the processing performed by the diagnostic server 120 is shown on the right side. When the control unit 121 of the diagnostic server 120 receives diagnostic data (battery measurement data and SOH) from the diagnostic equipment 50, 60, 70 or the BMS 80, based on the received diagnostic data, the control unit 121 determines whether or not the battery needs to be repaired. It is determined whether or not it is possible (S131). Then, the control unit 121 adds the judgment result (whether or not repair processing is necessary and possible) in step S131 to the received diagnostic data and stores it in the diagnostic DB 122a (S132), and stores the above-described diagnostic data in the blockchain system. (S133). The processing of steps S131 to S133 can be, for example, the processing of steps S28 to S30 in FIG. 20 and steps S55 to S57 in FIG.

Next, the control unit 121 acquires the past deterioration degree (SOH) from the diagnostic DB 122a or the blockchain system, and compares the past deterioration degree with the deterioration degree (SOH) acquired from the diagnostic equipment 50, 60, 70 or the BMS 80. A difference (change in SOH) is calculated (S134). Then, the control unit 121 identifies advice corresponding to the calculated change in the degree of deterioration from the advice DB 122b (S135). For example, the control unit 121 identifies a condition that matches the calculated deterioration degree change from the provision conditions stored in the advice DB 122b, and reads advice corresponding to the identified condition from the advice DB 122b. Further, the control unit 121 acquires the residual value of the battery based on the diagnostic data (SOC and SOH of the battery) obtained by diagnostic processing by the diagnostic equipment 50, 60, 70 or the BMS 80 (S136). The residual value includes, for example, the remaining cruising distance, the usable time of the battery, the remaining life of the battery (how many years it will take to reach the end of life), etc., and is based on the SOC and SOH of the battery, the current value and voltage value of the battery, etc. can be calculated by If the diagnostic equipment 50, 60, 70 and the BMS 80 have a function of calculating the residual value of the battery based on the measurement data and diagnostic data for the battery, the control unit 121 causes the diagnostic equipment 50, 60, 70 and the BMS 80 to The calculated residual value of the battery may be obtained.

The control unit 121 generates a diagnosis result screen that displays the battery diagnosis result and advice according to the diagnosis result, and transmits it to the diagnostic devices 50, 60, and 70 (S137). The diagnosis result screen here has the configuration shown in FIG. In addition to the configuration shown in FIG. 22A, the diagnosis result screen shown in FIG. 38 displays advice on battery usage and remaining value of the battery. The diagnostic server 120 may transmit the diagnostic result screen to the BMS 80 or the terminal device of the vehicle manager or the stationary battery manager. In this case, it is possible to provide the user of the battery with advice according to the diagnosis result of the battery.

The control unit of the diagnostic equipment 50, 60, 70 displays the diagnostic result screen received from the diagnostic server 120 on the display unit (S138), and presents the diagnostic result and advice on battery usage to each company. When the diagnosis processing for the battery is performed by the diagnosis equipment 50, 60, 70 or the BMS 80 and the diagnosis server 120 by the above-described processing, advice based on the diagnosis result and the residual value of the battery are provided in addition to the diagnosis result. can be done. Therefore, each company can confirm the diagnosis result of the degree of deterioration of the battery, and can receive advice on how to use the battery, for example, to extend the life of the battery. Advice according to the battery diagnosis result may be provided by each business operator and battery user requesting the diagnosis server 120 using a terminal device.

<Granting of eco-certification based on the amount of CO2 emission reduction>
In the information processing system of the present embodiment, the battery authentication server 130 performs authentication based on battery measurement data and diagnostic data, as well as authentication based on the amount of CO2 emissions reduced (suppressed amount) by using the battery (hereinafter referred to as (hereinafter referred to as eco-certification) is given to the battery. Eco-certification (ecology certification) proves that the battery to be diagnosed contributes to the reduction of CO2 emissions. In addition to the configuration shown in FIG. 11, the battery authentication server 130 stores a CO2 emission control amount DB 132d in the storage unit 122. FIG.

FIG. 39 is a schematic diagram showing a configuration example of the CO2 emission suppression amount DB 132d. The CO2 emission suppression amount DB 132d stores the CO2 emission amount suppressed by the use of the battery, that is, the CO2 emission suppression amount. The CO2 emission suppression amount DB 132d shown in FIG. 39 includes an event column and a CO2 emission suppression amount column, and stores the CO2 emission suppression amount in association with the event. The event is an event related to the use of the battery, and includes, for example, use of the battery mounted on the vehicle (driving of the vehicle), charging of the battery, use and charging of the stationary battery, and the like. The amount of CO2 emission control is, for example, the amount of CO2 emission control for the use of an in-vehicle battery per unit time such as 1 hour (driving of a vehicle), or the amount of CO2 emission control for the use of a battery per unit distance such as 100 km. It is possible to use the difference between the amount of CO2 emissions caused by driving a car (a vehicle equipped with a vehicle engine) and the amount of CO2 emissions caused by driving an EV. For example, the CO2 emission suppression amount is calculated using Equation 1 below. In addition, the amount of CO2 emission reduction for one charge of the on-board battery is the amount of CO2 emitted when procuring gasoline for refueling the engine vehicle, and the amount of electric power that is charged to the on-board battery in one charge. can be used as the difference from the amount of CO2 emitted when the electric power company generates power. For example, the CO2 emission control amount is calculated using Equation 2 below. In addition, for example, when the battery is configured to be charged with power generated by photovoltaic power generation, the amount of CO2 emission reduction for battery use or charging per unit time such as one hour is used or charged per unit time. It is possible to use the difference between the amount of CO2 emissions emitted when an electric power company generates the amount of electricity to be supplied and the amount of CO2 emissions emitted when electricity is generated by photovoltaic power generation. In addition to the usage time or the travel distance of the vehicle, the amount of discharge from the battery may also be used as the amount of battery usage. That is, the CO2 emission suppression amount may be set according to the amount of discharge from the battery. Note that the amount of discharge from the battery includes natural discharge and discharge due to use of the battery (running of the EV). Since the amount of discharge can be calculated from the transition of the amount of electricity stored in the battery, the difference obtained by subtracting the amount of natural discharge from the amount of discharge based on the transition of the amount of electricity stored can be used as the amount of discharge due to use of the battery.

(CO2 emission control amount for use of on-vehicle battery) = (CO2 emission amount due to EV driving) - (CO2 emission amount due to engine vehicle driving) (Equation 1)
(Amount of CO2 emission reduction for charging the vehicle battery) = (Amount of CO2 emission when the electric power company generates the electric power to be charged to the vehicle battery) - (CO2 emission when procuring gasoline for refueling the engine vehicle emissions) … (Formula 2)

FIG. 40 is a schematic diagram showing a modification of the battery DB 112a. The battery DB 112a here has, in addition to the structure shown in FIG. 7, a column of lifecycle CO2 emissions. A part of the battery DB 112a shown in FIG. 40 is omitted. The life cycle CO2 emissions column stores the CO2 emissions from the manufacturing stage of the battery. Specifically, the CO2 emissions from EVs compared with the CO2 emissions from engine vehicles are stored as life cycle CO2 emissions. More specifically, from the total of the CO2 emissions emitted when manufacturing the vehicle battery and the CO2 emissions emitted when manufacturing the vehicle (new EV) equipped with the vehicle battery, The difference obtained by subtracting the CO2 emissions emitted when manufacturing the engine vehicle is set as the initial value of the life cycle CO2 emissions of the battery (that is, the life cycle CO2 emissions of the battery at the time of EV manufacturing). Further, the life cycle CO2 emission amount of the battery is updated by adding the CO2 emission suppression amount corresponding to the event when each event registered in the CO2 emission suppression amount DB 132d shown in FIG. 39 occurs. be. The amount of CO2 emissions reduced for each event is the difference between the CO2 emissions associated with the use and charging of EVs and on-board batteries minus the CO2 emissions associated with the use and refueling of engine vehicles, and is usually a negative figure. becomes. Therefore, each time an event occurs, the amount of CO2 emission reduction corresponding to the event is added to reduce the value of the life cycle CO2 emission amount. means that is reduced. When the life cycle CO2 emission amount is 0 or less, it means that the CO2 emission is suppressed compared to the engine vehicle and contributes to the suppression of CO2 emission. In other words, the life cycle CO2 emissions are the maximum values at the time of manufacture of on-vehicle batteries and EVs, and decrease as the EV is used. indicates In the life cycle CO2 emission amount column of the battery DB 112a shown in FIG. 40, for example, the date of occurrence of each event and the life cycle CO2 emission amount updated at this point are associated and stored sequentially. The life cycle CO2 emissions are calculated and stored in the battery DB 112a, for example, when the battery authentication server 130 performs processing for giving eco-certification to the battery. Note that the control unit 131 (acquisition unit, setting unit) of the battery authentication server 130, when performing the authentication process, if the life cycle CO2 emissions are not registered in the battery DB 112a, The total CO2 emissions during manufacturing of the vehicle battery and the CO2 emissions during manufacturing of the vehicle minus the CO2 emissions during manufacturing of the engine vehicle is calculated as the life of the battery. The initial value of the cycle CO2 emission amount is set and stored in the battery DB 112a. The amount of CO2 emissions during manufacture of the vehicle and the amount of CO2 emissions during manufacture of the engine vehicle may be acquired, for example, from the terminal device 30 of the EV manufacturer, or may be acquired in advance and stored in the storage unit 132. . Further, the CO2 emission amount at the time of manufacture of the engine vehicle may be obtained in advance from the manufacturer of the engine vehicle and stored in the storage unit 132, for example. As shown in FIG. 40, by sequentially updating the life cycle CO2 emissions and storing them in the battery DB 112a, the most recent life cycle CO2 emissions can be used when calculating a new life cycle CO2 emissions. Since the latest lifecycle CO2 emissions can be calculated, efficient calculation processing can be executed.

FIG. 41 is a schematic diagram showing a modification of the stationary battery DB 112b. The stationary battery DB 112b here has, in addition to the configuration shown in FIG. 8A, a column of life cycle CO2 emissions during reuse and a column of life cycle CO2 emissions. The column of life cycle CO2 emissions during reuse stores the life cycle CO2 emissions for the stationary battery when the vehicle battery is reused as the stationary battery. For example, when a reuse business constructs a stationary battery, the stationary battery information about the stationary battery is registered in the stationary battery DB 112b. is registered in the stationary battery DB 112b. The life cycle CO2 emissions column stores the life cycle CO2 emissions updated by using stationary batteries. The life cycle CO2 emissions in the stationary battery DB 112b correspond to the event that occurred when the event registered in the CO2 emission control amount DB 132d shown in FIG. It is updated by adding the amount of CO2 emission control to be performed. The CO2 emissions reduction amount for events related to stationary batteries is, for example, the amount of CO2 emissions emitted when the amount of electricity used or charged per unit time is generated by solar power generation, and the amount of electricity generated by the electric power company. This is the difference obtained by subtracting the amount of CO2 emitted, and is usually a negative number. Therefore, the life cycle CO2 emission amount of the stationary battery is also reduced by adding the CO2 emission suppression amount corresponding to the event each time the event occurs. This means that the amount of CO2 emissions has been reduced, which means that we are contributing to the suppression of CO2 emissions. The life cycle CO2 emissions in the stationary battery DB 112b are calculated and stored in the stationary battery DB 112b, for example, when the battery authentication server 130 performs the process of granting eco-certification to the stationary battery.

FIG. 42 is a flow chart showing an example of the authentication granting procedure for the battery, and FIG. 43 is a schematic diagram showing an example of the screen. In FIG. 42, the processing performed by the diagnostic equipment 50, 60, 70 of each business is shown on the left side, and the processing performed by the battery authentication server 130 is shown on the right side. Maintenance/used car business operators, dismantling business operators, and reuse business operators may use terminal devices instead of the diagnostic devices 50, 60, and 70 to apply for battery certification. may use the terminal device to apply for certification of the battery.

The control unit 131 of the battery authentication server 130 determines whether or not an authentication application has been received from the diagnostic equipment 50, 60, 70 or the terminal device of each business (S141). : NO), perform other processing and wait. Note that the timing at which the control unit 131 accepts the authentication application is, for example, when the authentication application transmitted by the diagnostic device 50 in step S35 in FIG. 21 is accepted. When an authentication application is received from any device, the control unit 131 performs the following processes while performing the processes of steps S35 to S42 in FIG. Then, a process of giving eco-certification to the battery is performed.

If it is determined that an authentication application has been received from any device (S141: YES), the control unit 131 acquires battery information of the battery to be authenticated from the blockchain system or the battery DB 112a of the battery management server 110 (S142). In addition, the control unit 131 acquires measurement data measured in the past for the battery to be authenticated from the blockchain system or the measurement DB 112c (S143). Based on the measurement data for the battery, the control unit 131 calculates event information such as battery usage time, vehicle travel time or travel distance, battery charge count or charge amount (charging time), and the calculated event , the amount of CO2 emission reduction due to each event is calculated (S144). For example, when the total battery usage time is calculated, the control unit 131 acquires the CO2 emission suppression amount due to battery usage per unit time from the CO2 emission suppression amount DB 132d, and calculates the CO2 emission suppression amount due to battery usage per unit time. Based on the calculated total time, the amount of CO2 emission suppression for the total battery usage time is calculated. In addition, when the total travel time or travel distance of the vehicle is calculated, the control unit 131 acquires the amount of CO2 emission suppression due to vehicle travel per unit time or unit distance from the CO2 emission suppression amount DB 132d, and calculates the travel time or travel distance. You may calculate the amount of CO2 emission control with respect to the total of. In addition, it may be configured such that each user can select whether to calculate the amount of CO2 emission suppression based on the travel time or based on the travel distance. In addition, when the number of times the battery is charged is calculated, the control unit 131 may acquire the amount of CO2 emission suppression for one charge from the CO2 emission suppression amount DB 132d, and calculate the amount of CO2 emission suppression for the number of times the battery is charged. . Note that when the total charge amount of the battery is calculated, the control unit 131 obtains the CO2 emission control amount for the unit charge amount from the CO2 emission control amount DB 132d, and calculates the CO2 emission control amount for the total battery charge amount. may Thereby, the control unit 131 (identifying unit) can specify the amount of CO2 emission reduction (amount of reduction in CO2 emission) based on the data indicating the usage history of the battery, and the amount of CO2 emission suppression specified from the usage history of the battery. Life cycle CO2 emissions in the battery can be calculated based on. In addition, the control unit 131 identifies the most recent update date of the life cycle CO2 emissions stored in the battery DB 112a or the stationary battery DB 112b, and determines the amount of CO2 emission reduction due to an event that occurred during the period from the update date to the present. Calculate

Next, the control unit 131 extracts (acquires) the most recent life cycle CO2 emissions of the battery from the battery information acquired in step S142, and extracts (acquires) the acquired life cycle CO2 emissions and the CO2 emission suppression calculated in step S144. The latest life cycle CO2 emission amount of the battery is calculated (S145). Note that if the battery information does not include the most recent life cycle CO2 emissions, the control unit 131 extracts the CO2 emissions during battery manufacture from the battery information, and based on the extracted CO2 emissions during battery manufacture, Sets the initial value of the life cycle CO2 emissions of the vehicle. Specifically, the control unit 131 calculates the difference obtained by subtracting the CO2 emissions during manufacturing of the engine vehicle from the sum of the CO2 emissions during battery manufacturing and the CO2 emissions during vehicle manufacturing, and calculates the life cycle CO2 emissions. set to the initial value of Then, the control unit 131 calculates the latest lifecycle CO2 emission amount by adding the CO2 emission suppression amount calculated in step S144 to the set initial value. The control unit 131 (update unit) associates the date at this time with the calculated latest life cycle CO2 emissions in the battery DB 112a of the battery management server 110, and stores the life cycle CO2 emissions of the battery. update. Note that the control unit 131 may store the lifecycle CO2 emissions at this point in the blockchain system.

Based on the calculated life cycle CO2 emissions, the control unit 131 determines whether or not to give eco-certification to the battery (S146). For example, the control unit 131 determines to grant eco certification when the life cycle CO2 emission amount is less than a predetermined value, and determines not to grant eco certification when it is equal to or greater than the predetermined value. Thereby, the battery authentication server 130 can determine whether or not to grant the eco-certification according to the calculated lifecycle CO2 emissions of the battery. Note that the predetermined life cycle CO2 emission amount, which is the criterion for determining whether or not to grant the eco-certification, is a value at which it can be recognized that the CO2 emission is being suppressed. When giving the eco-certification to the battery, the control unit 131 may give different levels of eco-certification according to the lifecycle CO2 emissions. For example, batteries with lifecycle CO2 emissions equal to or greater than the first threshold are not given eco-certification, while batteries with lifecycle CO2 emissions less than the first threshold are given level 1 (low evaluation) certification. , giving level 2 (medium evaluation) certification to batteries whose life cycle CO2 emissions are less than the second threshold (second threshold < first threshold), and less than the third threshold (third threshold < second threshold) level 3 (high evaluation) certification may be given to the battery. In the present embodiment, the eco-certification is given for each battery pack, but the eco-certification may be given for each battery module or each battery cell.

When the control unit 131 determines not to give the eco-authentication (S146: NO), the series of processing ends. Note that the control unit 131 may transmit a message indicating that the eco-certification has not been granted to each device requesting authentication, and notify each business operator or battery user.

If it is determined that the eco certification is to be granted (S146: YES), the control unit 131 grants the eco certification to the battery (S147). Here, the control unit 131 issues an authentication ID, and generates authentication data including the date and time of authentication, the event, the authentication content indicating the eco-authentication, and the like. Then, the control unit 131 stores the generated authentication data in the authentication DB 132b in association with the pack ID of the battery to be authenticated (S148). The event here indicates the timing at which the application for certification is made, and includes "installation of new vehicle", "vehicle maintenance", "installation of used vehicle", "dismantling from vehicle", and the like.

The control unit 131 stores the authentication data described above in the blockchain system (S149). As a result, when the battery authentication server 130 grants eco-authentication to the battery, information (authentication data) related to the eco-authentication is recorded and managed in the battery authentication server 130 and the blockchain system. The control unit 131 generates an authentication result screen displaying the eco-authentication result for the battery, and transmits it to the device (diagnostic device 50, 60, 70, etc.) that requested authentication (S150). The authentication result screen here has the configuration shown in FIG. In addition to the configuration shown in FIG. 22B, the authentication result screen shown in FIG. 43 displays the date of eco-certification, information on the battery certification authority, certification level, etc., and notifies that the eco-certification has been granted. Each device (diagnostic device 50, 60, 70, etc.) requesting authentication receives the authentication result screen sent by the battery authentication server 130 and displays it on the display unit (S151). As a result, when the battery authentication server 130 (battery authentication organization) gives eco-certification to the battery, the content of the given eco-certification is provided to each business operator and user. Note that the screen shown in FIG. 43 notifies that the battery has been given certification based on the evaluation score and eco-certification.

Through the above-described processing, the battery is authenticated by the battery authentication server 130 (battery authentication organization) according to the diagnosis result (evaluation score) of the battery. Eco-certification is given according to the amount of life cycle CO2 emissions based on the standards. Therefore, the certification given to the battery makes it possible to determine whether or not the battery has been diagnosed by an appropriate diagnostic company using an appropriate diagnostic method. , the amount of CO2 emission reduction in the battery can be grasped. Such authentication results are accumulated in the battery authentication server 130 and the blockchain system, and each business operator can view the authentication results as necessary.

<Modified Example of Determination of Granting Authentication>
In the information processing system of the present embodiment, the battery authentication server 130, in addition to the evaluation score calculated based on the measurement data and diagnostic data of the battery, based on the amount of CO2 emission reduction by using the battery, It has a configuration that grants authentication to

FIG. 44 is a flow chart showing a modified example of the authorization granting procedure for the battery. In FIG. 44, the processing performed by diagnostic equipment 50, 60, and 70 of each business is shown on the left side, and the processing performed by the battery authentication server 130 is shown on the right side. Again, maintenance/used car business operators, dismantling business operators, and reuse business operators may use terminal devices instead of the diagnostic devices 50, 60, and 70 to apply for battery certification. A battery administrator may use a terminal device to apply for battery authentication.

The control unit 131 of the battery authentication server 130 performs the same processes as steps S141 to S143 in FIG. 42 (S161 to S163). The control unit 131 acquires diagnostic data that has been diagnosed in the past for the battery to be authenticated from the blockchain system or the diagnostic DB 122a of the diagnostic server 120 (S164). The control unit 131 calculates an evaluation score for the battery to be authenticated based on the acquired measurement data and diagnosis data (S165). The processing of step S165 is the same as that of step S37 in FIG.

Next, the control unit 131 performs the same processing as steps S144 to S145 in FIG. 42 (S166 to S167), and calculates the amount of CO2 emission reduction and lifecycle CO2 emission due to the use of the battery based on the battery usage history. calculate. Based on the evaluation score calculated in step S165 and the life cycle CO2 emission amount calculated in step S167, the control unit 131 determines whether or not to grant authentication to the battery (S168). For example, when the evaluation score is equal to or greater than a predetermined value and the life cycle CO2 emission amount is less than a predetermined value, the control unit 131 determines to grant authentication. Therefore, the battery authentication server 130 can determine whether or not to grant authentication according to the evaluation score and lifecycle CO2 emissions calculated for the battery. Here too, the battery authentication server 130 is not limited to a configuration that grants authentication for each battery pack, and may grant authentication for each battery module or each battery cell.

When the control unit 131 determines not to grant the authentication (S168: NO), the series of processing ends. If it is determined to grant authentication (S168: YES), the control unit 131 grants authentication to the battery (S169), authentication ID, authentication date and time, event, evaluation score, life cycle CO2 emissions, authentication details. Generates authentication data including Then, the control unit 131 stores the generated authentication data in the authentication DB 132b in association with the pack ID of the battery to be authenticated (S170), and stores the authentication data described above in the blockchain system (S171). Thereby, the battery authentication server 130 determines whether or not to grant authentication based on the evaluation score and the life cycle CO2 emission amount calculated for the battery, and if authentication is granted, information on authentication ( authentication data) is recorded and managed in the battery authentication server 130 and the blockchain system.

The control unit 131 generates an authentication result screen displaying the authentication result for the battery, and transmits it to the authentication requesting device (diagnostic device 50, 60, 70, etc.) (S172). 50, 60, 70, etc.) receives the authentication result screen sent by the battery authentication server 130 and displays it on the display unit (S173). The authentication result screen here has the same configuration as that shown in FIG. 22B. As a result, in the battery authentication server 130 (battery authentication organization), authentication is given to the battery according to the evaluation score based on the diagnosis result of the battery and the life cycle CO2 emission amount, and the content of the given authentication is applied to each business. provided to persons and users.

By the above-described processing, the result of diagnostic processing (evaluation score) by the diagnostic equipment 50, 60, 70 and the diagnostic server 120 of each business, and the amount of CO2 emission reduction due to the use of the battery, the battery authentication server 130 (battery authentication organization ) to grant authorization. Therefore, the certification given to the battery confirms that the battery has been diagnosed by an appropriate diagnostic company using an appropriate diagnostic method, and that the battery contributes to the reduction of CO2 emissions. can.

<Amount of CO2 emission reduction for recycled materials>
An information processing system that allocates a CO2 emission control amount to a recycled material dismantled from a battery to be discarded by a recycling business will be described. Here, when a recycling operator receives recycling certification from a battery certification organization for a recycled material, the battery certification server 130 grants the recycling certification to the recycled material, and at the same time is assigned.

FIG. 45 is a schematic diagram showing a modification of the material authentication DB 132c. The material authentication DB 132c here has, in addition to the configuration shown in FIG. 14, a column of life cycle CO2 emissions during recycling. The column of life cycle CO2 emissions at the time of recycling stores the life cycle CO2 emissions at the time when the recycled material is dismantled from the battery and recycled. For example, when a recycling operator requests the battery authentication server 130 for recycling certification for recycled materials, the battery authentication server 130 grants recycling certification to the recycled materials, and transmits authentication information (certification data) related to the granted recycling certification to the material. Register in the authentication DB 132c. At this time, the battery authentication server 130 calculates the life cycle CO2 emission amount of the recycled material at this time and registers it in the material authentication DB 132c. The life cycle CO2 emissions during recycling are calculated, for example, by multiplying the life cycle CO2 emissions of the battery before the recycled materials are dismantled by, for example, the ratio of the weight of the recycled materials to the weight of the battery.

FIG. 46 is a flow chart showing a modified example of the authorization granting procedure for recycled materials. The process shown in FIG. 46 is obtained by adding steps S181 to S184 between YES in step S65 and step S66 in the process shown in FIG. The control unit of the diagnostic device 90 of the recycling business and the control unit 131 of the battery authentication server 130 perform the processes of steps S61 to S65.

When the control unit 131 of the battery authentication server 130 determines that the recycling authentication is to be given (S65: YES), the battery information of the battery (battery before dismantling) in which the recycled material to be authenticated was used is transferred to the blockchain system, or , from the battery DB 112a or stationary battery DB 112b of the battery management server 110 (S181). In addition, the control unit 131 acquires the measurement data measured in the past for the battery using the recycled material to be certified from the blockchain system or the measurement DB 112c (S182). The control unit 131 calculates the CO2 emission suppression amount for the battery based on the acquired measurement data and the stored contents of the CO2 emission suppression amount DB 132d (S183). For example, the control unit 131 calculates the total usage time of the battery, and calculates the total usage time of the battery based on the amount of CO2 emission reduction due to battery usage per unit time stored in the CO2 emission suppression amount DB 132d. Calculate the amount of CO2 emission reduction. Note that the control unit 131 may calculate the amount of CO2 emission suppression according to the battery charging time and the number of times of charging, may calculate the total of these CO2 emission suppression amounts, or may calculate the CO2 emission suppression amount based on the battery usage history. Calculate the emission control amount. The control unit 131 calculates the CO2 emission suppression amount in the period from the most recent update date of the life cycle CO2 emission amount stored in the battery DB 112a or the stationary battery DB 112b to the present.

Next, the control unit 131 acquires the most recent life cycle CO2 emissions of the battery from the battery information acquired in step S181, and combines the acquired life cycle CO2 emissions with the CO2 emission suppression amount calculated in step S183. Based on this, the latest life cycle CO2 emission amount of the battery is calculated. Then, the control unit 131 calculates the life cycle CO2 emissions for the recycled material based on the calculated life cycle CO2 emissions (S184). Here, for example, the control unit 131 may calculate the life cycle CO2 emission amount for the recycled material by multiplying the life cycle CO2 emission amount by the battery by the ratio of the weight of the recycled material to the weight of the battery. . Since the battery DB 112a or the stationary battery DB 112b stores the life cycle CO2 emissions calculated in the past, the control unit 131 can store the most recently calculated life cycle CO2 emissions and the most recent calculation year/month. The latest life cycle CO2 emissions can be calculated based on the daily CO2 emissions reduction amount. When calculating the life cycle CO2 emission amount, the control unit 131 stores the calculated life cycle CO2 emission amount in the material authentication DB 132c as the life cycle CO2 emission amount at the time of recycling. Note that the control unit 131 may store the life cycle CO2 emission amount at this point in the blockchain system as the life cycle CO2 emission amount at the time of recycling.

Then, the control unit 131 gives recycling certification to the recycled material according to the life cycle CO2 emission amount (life cycle CO2 emission amount at the time of recycling) calculated for the recycled material (S66). Here, the control unit 131 generates authentication data including the authentication date and authentication information indicating the authentication result, etc., and stores the generated authentication data in the material authentication DB 132c in association with the material ID issued to the recycled material. (S67). Note that the control unit 131 may give the recycled material a recycling certification of a level corresponding to the life cycle CO2 emission amount calculated for the recycled material. In addition to the recycling certification, the control unit 131 may give eco certification to the recycling material according to the life cycle CO2 emission amount of the recycling material.

The control unit 131 of the battery authentication server 130 and the control unit of the diagnostic device 90 execute the processing of steps S67 to S70, and the information (authentication data) regarding the recycling authentication given to the recycled material by the battery authentication server 130 is transferred to the battery. It is recorded and managed in the authentication server 130 and blockchain system. Note that the authentication result screen transmitted from the battery authentication server 130 to the diagnostic device 90 has the same configuration as that shown in FIG. 27B. Through the above-described processing, when the battery authentication server 130 (battery authentication organization) grants recycling authentication to the recycled material, the life cycle CO2 emission amount of the recycled material is calculated and registered in the material authentication DB 132c. Note that the life cycle CO2 emissions of recycled materials can be obtained by multiplying the life cycle CO2 emissions of a battery that uses the recycled material by the ratio of the recycled material to the weight of the battery. , but not limited to. Life cycle CO2 emissions of recycled materials are calculated by dividing the CO2 emissions generated when batteries are manufactured using recycled materials, and the CO2 emissions generated when batteries are manufactured using natural materials without using recycled materials. It can be calculated by the difference from the CO2 emissions generated in Specifically, the life cycle CO2 emissions of recycled materials are calculated from the amount of CO2 emissions generated in the dissolution and deposition processes in the recycling process in which recycled materials are dismantled from batteries. After that, it can be calculated by subtracting the amount of CO2 emissions generated during refining and transportation. The amount of reduction in CO2 emissions calculated by comparison with the case of using natural materials in this way may be added to the lifecycle CO2 emissions of recycled materials.

By assigning the life cycle CO2 emissions at the time of recycling to recycled materials in this way, it can be used to calculate the life cycle CO2 emissions at the time of manufacture of new batteries manufactured using the recycled materials. That is, by using recycled materials when manufacturing a new battery, it is possible to add the amount of CO2 emission reduction due to the use of recycled materials from the amount of life cycle CO2 emissions when manufacturing the battery. Life cycle CO2 emissions can be reduced.

Next, when a new battery is manufactured and the battery information is registered in the battery DB 112a of the battery management server 110 and the blockchain system from the battery manufacturer's terminal device 20, the life cycle CO2 emissions at the time of battery manufacturing are used. Processing for setting an amount in consideration of the life cycle CO2 emission amount at the time of recycling of the recycled material is described. FIG. 47 is a flow chart showing an example of battery information registration processing.

The control unit 21 of the terminal device 20 displays, for example, a battery information input screen as shown in FIG. 17 on the display unit 25 by executing a predetermined application (S191). The person in charge of the battery manufacturer inputs each piece of information about the battery to be registered in each entry column of the battery information entry screen. In addition to the type and amount of materials used in the manufacture of the battery, the material information includes the type and amount of recycled materials used in the case where recycled materials are used, and the materials assigned to the recycled materials. Information such as ID is included.

The control unit 21 determines whether or not each piece of information has been input via the input screen and the registration button has been operated (S192). Continue to wait for input of information for each input field. When determining that the registration button has been operated (S192: YES), the control unit 21 transmits each piece of information (battery information) input via the input screen to the battery management server 110 (S193).

When the control unit 111 of the battery management server 110 acquires the battery information from the terminal device 20, if there is a recycled material in the material information included in the battery information, the control unit 111 of the battery management server 110 calculates the life cycle CO2 emission amount of the recycled material in the block chain. It is acquired from the system or the material authentication DB 132c of the battery authentication server 130 (S194). Lifecycle CO2 emissions for recycled materials are calculated by the above-described process and stored in the blockchain system or material authentication DB 132c. Therefore, the control unit 111 can acquire the life cycle CO2 emission amount of the recycled material based on the material ID acquired from the terminal device 20 . Next, based on the amount of CO2 emissions during battery manufacturing included in the battery information acquired from the terminal device 20 and the amount of life cycle CO2 emissions for recycled materials, the control unit 111 determines the life cycle CO2 emissions during manufacturing of the battery. The amount is calculated (S195). Here, the control unit 111 adds the CO2 emissions during the manufacture of the EV to the CO2 emissions during the manufacture of the battery acquired from the terminal device 20, and then subtracts the CO2 emissions during the manufacture of the engine vehicle to estimate the life of the battery. Calculate the initial value of the cycle CO2 emissions. The life cycle CO2 emissions calculated here indicate the life cycle CO2 emissions at the time of EV manufacturing of a battery manufactured without using recycled materials. Note that the CO2 emissions during the manufacture of an EV and the CO2 emissions during the manufacture of an engine vehicle may be obtained from a predetermined server or may be stored in the storage unit 112 in advance. Then, the control unit 111 adds the life cycle CO2 emissions from the recycled materials (equivalent to the amount of CO2 emission suppression) to the calculated life cycle CO2 emissions of the battery at the time of EV manufacturing, and adds the obtained amount to the battery. Life cycle CO2 emissions during EV manufacturing (batteries manufactured using recycled materials). By adding life cycle CO2 emissions from recycled materials (usually a negative number) to the life cycle CO2 emissions of batteries during EV production calculated based on CO2 emissions from EV production, recycled materials The life cycle CO2 emissions reduced by the CO2 emissions due to the use of can be made the life cycle CO2 emissions during manufacture appropriate for the battery.

Then, the control unit 111 stores the battery information obtained from the terminal device 20 and the life cycle CO2 emissions during manufacture of the battery calculated in step S195 in the battery DB 112a (S196). Here, the control unit 111 issues a pack ID for the battery pack to be registered, issues a module ID according to the number of modules acquired from the terminal device 20 and a cell ID according to the number of cells, And, in association with the cell ID, the specification information, material information and CO2 emissions during battery manufacture acquired from the terminal device 20, and the life cycle CO2 emissions during battery manufacture calculated in step S195 are stored in the battery DB 112a ( S196). The control unit 111 also stores the battery information in the blockchain system (S197).

When a new battery is manufactured using recycled materials through the process described above, the life cycle CO2 emissions at the time of manufacture of the battery are considered (specifically, added) to the life cycle CO2 emissions from recycled materials. can be emissions. Therefore, the life cycle CO2 emission amount at the time of manufacturing the battery can be set to a life cycle CO2 emission amount in which CO2 is suppressed by the amount of the recycled material. The life cycle CO2 emissions for recycled materials increase as the number of times the battery is used and the number of times the recycled material is used (recycled) increases. Therefore, the use of recycled materials with large lifecycle CO2 emissions is being considered, and the recycling of materials is promoted.

Even when battery modules or battery cells are reused for other vehicle batteries or stationary batteries, the life cycle CO2 emissions of the reused vehicle batteries or stationary batteries An emission amount that takes into consideration the amount of CO2 emission control can be used. For example, when a battery is manufactured by reusing battery modules or battery cells, the amount of CO2 emitted during the manufacture of the battery manufactured without reusing the battery modules or battery cells indicates whether the battery modules or battery cells are reused. The amount obtained by subtracting the amount of CO2 emissions during manufacture of the manufactured battery may be set as the amount of lifecycle CO2 emissions during reuse of the battery (reused battery). In this case, the life cycle CO2 emissions reduced by the CO2 emissions due to reuse of the battery module or battery cell can be used as the appropriate life cycle CO2 emissions during reuse of the battery. Note that when a stationary battery is manufactured by reusing battery modules or battery cells, when the battery information of the stationary battery is registered in the stationary battery DB 112b of the battery management server 110 and the blockchain system, as described above, , the calculated life cycle CO2 emission amount of the stationary battery during reuse is registered.

<Browse of certification history for recycled materials>
In the information processing system of the present embodiment, the authentication data for recycled materials accumulated in the material authentication DB 132c of the battery authentication server 130 or the blockchain system can be viewed by each business operator using a terminal device. In addition to the recycling certification, the certification data for the recycled material includes certification information of certification (certification based on the evaluation score corresponding to the diagnosis result) granted during the period when the recycled material was used as a battery.

FIG. 48 is a flow chart showing an example of a browsing process procedure of authentication data for recycled materials, and FIGS. 49 and 50 are schematic diagrams showing examples of screens. In FIG. 48, the processing performed by the terminal device of each business is shown on the left side, and the processing performed by the battery authentication server 130 is shown on the right side. A person in charge of each business, such as a person in charge of a battery manufacturer, executes a predetermined application using a terminal device, for example, to display a search screen for recycled materials as shown in FIG. 49A on the display unit. The search screen shown in FIG. 49A includes an input field for entering the type of recycled material to be searched for, and a check box for selecting one or both of the vehicle battery and the stationary battery as the final form in which the recycled material was used. It has a box and an entry field for entering a price range. Each company inputs information in each entry field and operates a search button to instruct execution of a search process for recycled materials.

When the search button on the search screen is operated, the control unit of the terminal device transmits the search information entered in each input field to the battery authentication server 130 (S201). When receiving the search information from the terminal device, the control unit 131 of the battery authentication server 130 searches for recycled materials based on the search information (S202). For example, the control unit 131 extracts a recycled material to be searched from materials registered in the material authentication DB 132c. Note that when the final usage form of each recycled material (the final form in which the recycled material was used as a battery) is registered in the material authentication DB 132c, the control unit 131 , to extract the recycled material to be searched and the material corresponding to the final usage form. Further, when the price of each recycled material is registered in the material authentication DB 132c, the control unit 131 extracts the material corresponding to the search target recycled material and price range from the materials registered in the material authentication DB 132c. do.

The control unit 131 generates a search result screen displaying information on recycled materials extracted from the materials registered in the material authentication DB 132c (S203), and transmits the generated search result screen to the terminal device that has made a viewing request. (S204). FIG. 49B shows an example of a search result screen, and the screen shown in FIG. 49B shows the search result of nickel as a recycled material. The control unit 131 reads the material ID, the recycling completion date, the recycling company, and the authentication information from the material authentication DB 132c for the recycled material extracted from the material authentication DB 132c, and generates the screen shown in FIG. 49B. The authentication information displayed on the search result screen may include, for example, whether or not recycling certification has been granted to the recycled material, the level of certification granted, and information on the certification organization that granted certification.

The terminal device receives the search result screen from the battery authentication server 130 and displays it on the display unit. The search result screen shown in FIG. 49B has check boxes for selecting each of the retrieved recycled materials. Manipulate. The terminal device of each business determines whether or not the selection button has been operated on the search result screen (S205), and if it determines that the selection button has not been operated (S205: NO), the series of processing ends. If it is determined that the selection button has been operated (S205: YES), the terminal device of each company transmits the material ID of the selected recycled material to the battery authentication server 130, and the material ID is assigned to the recycled material corresponding to the material ID. authentication history is requested (S206).

The control unit 131 of the battery authentication server 130 accepts a request for the authentication history of the recycled material corresponding to the material ID from the terminal device, and when the request for the authentication history is accepted, stores the authentication data corresponding to the material ID in the authentication DB 132b and the material. Extract from the authentication DB 132c or the blockchain system (S207). The control unit 131 identifies the pack ID and module ID corresponding to the material ID for which the authentication history is requested, for example, from the material authentication DB 132c, and extracts the authentication data corresponding to the identified pack ID and module ID from the authentication DB 132b. do. The control unit 131 also extracts authentication information corresponding to the material ID for which the authentication history is requested from the material authentication DB 132c. When extracting the authentication data from the blockchain system, the battery authentication server 130 requests any of the node devices 10 to browse the authentication data corresponding to the pack ID and the module ID. The node device 10 searches the block chain system using the requested pack ID and module ID as keys, extracts authentication data corresponding to the pack ID and module ID, and outputs the authentication data to the battery authentication server 130 . When extracting the authentication information from the blockchain system, the battery authentication server 130 requests any of the node devices 10 to view the authentication information corresponding to the material ID, and the node device 10 uses the requested material ID as a key. and extract the corresponding credentials.

Control unit 131 of battery authentication server 130 generates an authentication history screen based on the extracted authentication data (S208). FIG. 50 shows an example of an authentication history screen for recycled materials. The screen shown in FIG. 50 displays material IDs and material names of recycled materials, recycling business operators, recycling completion dates, recycling methods, and the like. In addition, the screen shown in FIG. 50 shows the date of certification, the event when applying for certification, and the The cell ID, the evaluation score calculated for the battery pack, the authentication details, etc. are displayed. In the example of FIG. 50, as events, installation on vehicles (new and used vehicles), vehicle maintenance, reuse (incorporation into other vehicle batteries or stationary batteries), periodic diagnosis of stationary batteries, recycling, etc. are displayed. and presents the details of the certification granted at each event. Note that the certification at the time of recycling is a recycling certification that certifies that the recycled material is a recycled material.

The control unit 131 of the battery authentication server 130 transmits the generated authentication history screen to the terminal device that requested viewing (S209). Thereby, the control unit 131 outputs the history information of the authentication given to the recycled material in response to the request received from the terminal device. Upon receiving the authentication history screen from the battery authentication server 130, the terminal device displays the authentication history screen on the display unit (S210). As a result, it is possible to present information on the recycling certification given to the recycled material and the history of the certification given to the battery before recycling to each company. Therefore, each company can grasp what kind of certification the recycled material has been granted. According to such a configuration, it is possible to present the history of authentication given by the battery authentication server 130 during the period from when the battery is manufactured until it is disassembled and recycled, and the battery and the recycled material can be displayed depending on the authentication status. value can be evaluated. Note that in addition to the battery certification and the recycling certification for the recycled material, an eco-certification based on the amount of CO2 emission reduction may be granted, and in this case, the certification history of the eco-certification is also presented.

In the information processing system of the present embodiment having the configuration described above, a battery manufactured as an in-vehicle battery is replaced (reused) with another in-vehicle battery or a stationary battery from the start of use, and discarded after extraction of recycled materials. In the period until, the measurement data of the battery measured at appropriate timing and the diagnostic data of the degree of deterioration of the battery are associated with the ID (pack ID, module ID, cell ID) that identifies the battery, and the block chain system recorded in Since information about such batteries is shared among business operators via the blockchain system, information on batteries manufactured by different battery manufacturers can also be shared among business operators. By accumulating various types of information about the battery in the blockchain system and performing diagnostic processing and authorization processing using the accumulated information, highly reliable processing can be executed. In addition, in this embodiment, since the operating state and deterioration state of the battery are managed in units of packs, modules, or cells, it is possible to trace the operating state and deterioration state in units of packs, modules, or cells. . In addition, since the recycled material extracted from the battery is managed by assigning a material ID, it is possible to trace the operating state and deterioration state of the battery before recycling with respect to the recycled material.

In the information processing system of this embodiment, the batteries to be diagnosed and authenticated may be batteries manufactured by a plurality of battery manufacturers, or batteries of a plurality of types such as lithium-ion batteries and nickel-metal hydride batteries. good. Therefore, in the information processing system of the present embodiment, diagnostic processing and authentication grant processing are performed on a plurality of types of batteries, and the respective diagnostic results and authentication results are accumulated. By aggregating the diagnostic results and authentication results accumulated in this way, it is possible to evaluate the battery for each battery manufacturer and for each battery type, for example. It is also possible to extract evaluations of batteries of arbitrary types from arbitrary battery manufacturers and present comprehensive evaluations.

In the present embodiment, an evaluation score for a battery pack to be authenticated is calculated according to the contents stored in the score DB 132a, and whether or not to grant authentication to the battery pack is determined based on the evaluation score. Note that the score DB 132a may store, for example, addition of -100 points (subtraction of 100 points) or multiplication by 0 when the diagnostic device that has diagnosed the battery is not a pre-certified device. In this case, when a predetermined condition (determination content) is met, it is possible to calculate an evaluation score that determines that authentication should not be granted, and to avoid granting authentication to the battery. Alternatively, when a predetermined condition is met, it may be determined that authentication should not be granted without calculating the evaluation score. Also in this case, it is possible to avoid granting authentication to the battery. Therefore, by registering situations in which authentication should not be granted (for example, when the diagnostic device is not pre-certified), it is possible to control not to grant authentication when the situation matches. can.

Further, in the present embodiment, the evaluation score for the battery to be authenticated is calculated according to the contents stored in the score DB 132a, while the stored battery information (battery information, measurement data, diagnostic data, authentication data, etc.) is used to evaluate the battery. It may be determined whether or not to grant authentication based on the evaluation score and credit. For example, based on the measurement data of the battery, it is determined whether or not the measurement device (for example, the vehicle-mounted measurement device 40) or the diagnostic device has been replaced. do. In addition, the date and time of measurement data accumulated in the measurement DB 112c of the battery management server 110 include the start date and time of the battery measurement process and the storage date and time of the measurement data in the measurement DB 112c, and these dates and times are substantially the same (the date and time If the difference is less than a predetermined time, it may be assumed that the measurement data has not been tampered with, and the reliability of the battery may be given a high value. On the other hand, if the difference between these dates and times is equal to or longer than the predetermined time, it may be determined that the measurement data may have been falsified, and the reliability of the battery may be set to a low value. Further, the reliability of the battery may be given a higher value as the number of times the battery is applied for authentication or the number of times the battery is authenticated is increased. Furthermore, if the evaluation score and certification level fluctuate significantly compared to the past evaluation score and certification level, for example, if they go up or down, the battery's credibility is set to a low value, and the evaluation score and certification level are kept constant. (normal deterioration), the reliability of the battery may be set to a high value. By determining whether or not to grant authentication based on the credibility calculated in this way and the evaluation score calculated by referring to the score DB 132a, not only the numerical values of the measurement data and diagnostic data but also the data itself It is possible to determine whether or not to grant authentication in consideration of credibility.

In this embodiment, the in-vehicle measuring device 40 stores measurement data such as the travel distance of the vehicle, the usage time of the battery mounted in the vehicle, the charging time and the number of times of charging, as well as the temperature and humidity around the battery. You may have the structure which measures the measurement data regarding a use environment. In addition, by accumulating measurement data related to the usage environment in the blockchain system together with measurement data such as vehicle mileage, battery usage time, charging time and number of charging times, the environment in which the battery was used can be traced. may have been Similarly, the diagnostic devices 50, 60, 70, 90 and the BMS 80 provide diagnostic data on the current value, voltage value, temperature, SOC, and SOH for each cell, as well as on the usage environment of the battery, such as temperature and humidity around the battery. It may be configured to measure measurement data. In this case as well, the environment in which the battery was used may be traced by accumulating measurement data relating to the usage environment together with diagnostic data in the blockchain system.

The embodiments disclosed this time are illustrative in all respects and should be considered not restrictive. The scope of the present invention is indicated by the scope of the claims rather than the above-described meaning, and is intended to include all modifications within the scope and meaning equivalent to the scope of the claims.

REFERENCE SIGNS LIST 10 node device 20 terminal device 30 terminal device 40 in-vehicle measuring device 50 diagnostic device 60 diagnostic device 70 diagnostic device 80 BMS
90 diagnostic device 110 battery management server 120 diagnostic server 121 control unit 130 battery authentication server 131 control unit 140 insurance provider server

The information processing method according to the present disclosure acquires CO2 (carbon dioxide) emissions when manufacturing a vehicle equipped with a vehicle battery, and compares the acquired CO2 emissions with the engine vehicle equipped with a vehicle engine. Calculate the difference from the CO2 emissions at the time of manufacture, set it as an initial value of the life cycle CO2 emissions of the vehicle battery, and associate it with the usage time of the vehicle battery or the mileage of the vehicle, The difference between the amount of CO2 emissions due to running and the amount of CO2 emissions due to running with an engine vehicle is stored in the storage unit as a reduction amount of CO2 emissions, and based on the usage history data of the vehicle-mounted battery , The amount of reduction in CO2 emissions corresponding to the usage time of the battery or the mileage of the vehicle equipped with the in-vehicle battery is specified from the storage unit , and the in-vehicle battery is calculated based on the specified reduction amount of CO2 emissions. The computer executes the process of updating the life cycle CO2 emissions of the battery.

Claims (9)

Acquisition of CO2 (carbon dioxide) emissions when manufacturing vehicles equipped with in-vehicle batteries,
Calculating the difference between the acquired CO2 emissions and the CO2 emissions at the time of manufacture of an engine vehicle equipped with a vehicle engine, and using it as an initial value for the life cycle CO2 emissions of the vehicle battery,
Identifying the reduction amount of CO2 emissions based on the usage history data of the in-vehicle battery,
An information processing method in which a computer executes a process of updating the life cycle CO2 emission amount of the vehicle battery based on the identified reduction amount of CO2 emission amount. The information processing method according to claim 1, wherein the computer executes a process of specifying a reduction amount of CO2 emissions based on the amount of charge or the amount of discharge of the vehicle battery. 2. The computer executes a process of giving an eco-certification indicating contribution to CO2 reduction to the vehicle battery when the life cycle CO2 emission amount of the vehicle battery is less than a predetermined value. Or the information processing method according to 2. Acquiring diagnostic information for the vehicle battery,
Identifying an evaluation level for the in-vehicle battery based on the acquired diagnostic information,
Based on the specified evaluation level, determine whether to authenticate the vehicle battery,
4. The information according to any one of claims 1 to 3, wherein the computer executes a process of giving certification based on the evaluation level and eco-certification based on the life cycle CO2 emissions to the vehicle battery. Processing method. Acquiring diagnostic information for the vehicle battery,
Identifying an evaluation level for the in-vehicle battery based on the acquired diagnostic information,
5. The information processing method according to any one of claims 1 to 4, wherein the computer executes a process of granting authentication to the in-vehicle battery according to the specified evaluation level and the life cycle CO2 emission amount. . Based on the life cycle CO2 emissions of the vehicle battery, specifying the amount of CO2 emission reduction corresponding to the recycled amount for materials to be recycled among the materials contained in the vehicle battery,
The amount of CO2 emissions during the manufacturing of a vehicle equipped with an on-board battery manufactured using the recycled material is calculated as the amount of CO2 emitted when a vehicle equipped with an on-board battery manufactured without using recycled materials is manufactured. 6. The information processing method according to any one of claims 1 to 5, wherein the computer executes a process of subtracting the specified CO2 emission control amount from the CO2 emission amount. 4. The information processing method according to claim 3, wherein the computer executes a process of giving a higher level of eco-certification to the in-vehicle battery as the life cycle CO2 emission amount decreases. Acquisition of CO2 (carbon dioxide) emissions when manufacturing vehicles equipped with in-vehicle batteries,
Calculating the difference between the acquired CO2 emissions and the CO2 emissions at the time of manufacture of an engine vehicle equipped with a vehicle engine, and using it as an initial value for the life cycle CO2 emissions of the vehicle battery,
Identifying the reduction amount of CO2 emissions based on the usage history data of the in-vehicle battery,
A program for causing a computer to execute a process of updating the life cycle CO2 emission amount of the vehicle battery based on the identified CO2 emission reduction amount. an acquisition unit that acquires CO2 (carbon dioxide) emissions when manufacturing a vehicle equipped with an in-vehicle battery;
a setting unit that calculates a difference between the obtained CO2 emission amount and the CO2 emission amount at the time of manufacture of the engine vehicle in which the vehicle engine is installed, and sets an initial value for the life cycle CO2 emission amount of the vehicle battery; ,
a specifying unit that specifies a reduction amount of CO2 emissions based on the usage history data of the in-vehicle battery;
An information processing apparatus comprising: an update unit that updates the life cycle CO2 emission amount of the vehicle battery based on the identified CO2 emission reduction amount.

Images