WO2023233727A1

WO2023233727A1 - Insurance claim system, insurance claim method, and insurance claim program

Info

Publication number: WO2023233727A1
Application number: PCT/JP2023/005746
Authority: WO
Inventors: 佑樹近藤; 敬志大島; 訓大島
Original assignee: 株式会社日立製作所
Priority date: 2022-06-01
Filing date: 2023-02-17
Publication date: 2023-12-07
Also published as: JP2023177173A

Abstract

When a terminal device submits an insurance claim, an insurance claim evaluation device requests submission of proof of account ownership after receiving the insurance claim. The terminal device issues a proof of account ownership token via an account management device. The token is transferred from an account of an insured individual to an account of an insurance company. The insurance claim evaluation device verifies the proof of account ownership of the account that is an object of insurance of the insured person, determines whether an insurance settlement is possible on the basis of a payment device transaction history, and calculates a loss and insurance proceeds.

Description

Claims Systems, Claims Methods, and Claims Programs

The present invention relates to an insurance claim system, an insurance claim method, and an insurance claim program that perform electronic payment.

Due to technological innovation and the progress of cashless payments in the financial sector, central banks and financial institutions around the world are working on research and development of digital currencies.

Digital currency is currency that has been digitized by a computer system and is managed, stored, and exchanged over the Internet. Digital currencies include central bank digital currencies, which are legal tender issued as central bank debt, electronic money issued by private companies, and crypto assets that utilize blockchain algorithms.

Digital currency is expected to serve as a new payment infrastructure that supports the digitalization of economic activities. The spread of mobile devices and the cloud has created new points of contact and combinations between various economic entities, goods, and services. Economic activities in virtual spaces such as e-commerce and the sharing economy are expanding. In addition, connections with economic activities in real space are also emerging, such as with carbon footprints. Digital currency is responsible for the flow of money in these economic zones.

Various models have been proposed as operational forms of digital currency systems. For example, a model in which the issuer of digital currency manages the system centrally, a model in which the system is managed in a decentralized manner by a consortium made up of multiple companies that issue and distribute digital currency, and a model in which the system is managed in a decentralized manner by an unspecified number of companies and individuals. There are known models in which systems are managed in a decentralized manner.

Digital currency users, such as consumers and businesses, access the digital currency system using applications installed on PCs and mobile devices. Digital currencies utilize blockchain technology, so when making a payment, the transaction is electronically signed using the user's private key.

In order for digital currency to be accepted by society as a new payment method, it is necessary to ensure not only convenience but also safety. First, it is necessary to prevent cyber accidents and fraudulent transactions by improving system quality and implementing security measures. However, as long as it is a system, it is not possible to predict and deal with all problems in advance. Therefore, as a follow-up measure, cyber insurance is also required to compensate for damage caused by cyber accidents and fraudulent transactions in digital currency systems.

For example, Patent Document 1 is known as a technology for calculating premium rates for insurance products regarding cyber insurance for digital currency. This system expresses the relationship between digital currency and users in a tree structure, simulates how the damage will be propagated in the event of a cyber attack on digital currency, and calculates the risk based on the sum of the damages. Evaluate and calculate insurance premium rates.

US20210256623

Although the above-mentioned Patent Document 1 calculates the premium rate of insurance products, there is no mention of assessing insurance claims and paying insurance claims. An insured person insures various types of digital currencies that he or she owns, sets a guarantee period and guarantee amount, and concludes an insurance contract. Coverage often covers vulnerability attacks and hacking of digital currency system programs, but if the insured loses the private key of the digital currency, insurance claims will not be paid.

If a loss occurs due to a digital currency cyber accident, the insured will submit an insurance claim and evidence. The evidence is that the private key of the digital currency is currently being safely managed, that is, proof of ownership of the account. The insurance company analyzes the insured's claim information and transaction history collected from the digital currency system and confirms that the cyber incident occurred during the policy period and that the insured still owns the private key of the digital currency. If we are able to verify that this is the case, we will determine that the reason for payment is met and pay the insurance claim.

When building a system to assess insurance claims and pay insurance claims, it is also possible to run it on a public blockchain in which an unspecified number of companies and individuals participate. Since the insured person controls the private key of the digital currency, the insured person can submit proof of account ownership, and the insured person can also refer to the transaction history of the digital currency system, so the insurance company can make an assessment. You can directly refer to the evidence used to confirm the validity of the assessment results.

However, since the target is a form in which an unspecified number of companies and individuals operate a digital currency system on a public blockchain in a decentralized manner, a specific group of approved organizations operates a digital currency system on a private blockchain. There was a problem in that it was not compatible with a form of distributed management of the system.

When operating a digital currency system using a private blockchain, there is an information asymmetry between the insured using cyber insurance and the insurance company.

In this type of operation, users access the digital currency system via custody, so they cannot directly access evidence such as proof of digital currency account ownership or transaction history. Safely managing the private keys of digital currencies requires a high degree of expertise. In order to reduce this burden, the insured entrusts the management of the private key and account to a custodian such as a bank. Since the insured does not have direct access to the digital currency system, the insured cannot provide proof of account ownership to the insurance company. Furthermore, since it is not possible to check the transaction history used by the insurance company for assessment, it is not possible to judge the validity of the assessment results.

Furthermore, although Custody has the business function of making digital currency payments, it does not have the business function of making digital currency insurance claims.

On the other hand, insurance companies can collect transaction history as participating organizations in the digital currency system, but cannot access the custody system. Therefore, it is not possible to verify whether the insured's private key is being managed safely, that is, the proof of ownership of the account.

In other words, in the insurance claims process for cyber insurance for digital currencies, there is a problem that the insured and the insurance company cannot trust each other in the process of collecting and verifying evidence. As a result, the validity of insurance assessment evidence cannot be guaranteed.

The present invention has been made in view of the above-mentioned problems. When an insured person outsources digital currency account management to a custody company, the present invention ensures that the validity of the evidence of insurance assessment is guaranteed, and that digital currency The purpose is to provide technology that can assess insurance claims for cyber insurance.

An insurance claim system according to the present invention includes a terminal device, an account management device, a payment device, and an insurance claim adjustment device, each device having a processor and a memory, The processor of the terminal device executes a first program to output insurance claim information related to the digital currency insurance claim procedure input by the user to the insurance claim adjustment device, and the processor of the insurance claim adjustment device executes a first program. , execute a second program to prove that the user identified by the account identification information for identifying the user's account included in the insurance claim information owns the account as an insured person. requesting the terminal device to submit an account ownership certificate for the purpose of the transaction, the processor of the terminal device executes the first program and outputs a request to issue the account ownership certificate to the account management device; The processor of the account management device executes a third program to collect insurance contract identification information for identifying an insurance contract of the digital currency, the account identification information, and the digital currency included in the insurance claim information. The processor of the payment device outputs to the payment device a request for issuance of a token for proof of ownership of the account whose owner is the insured person, which is generated using the digital currency identification information for identification, and the processor of the payment device Execute the program to add the token that received the issuance request to a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token. , outputs the added result to the account management device as a token issuance transaction result, and the processor of the account management device executes the third program to output the added result to the token issuance transaction result. A transfer request indicating that the owner of the token is the insurance company is output to the payment device, and the processor of the payment device executes the fourth program to register the owner of the token added to the first table. to the insurance company, and outputs the updated result to the account management device as a token transfer transaction result, and the processor of the account management device executes the third program to transfer the token from the payment device. Upon receiving the transfer transaction result, outputting completion of issuance of the account ownership certificate to the terminal device, the processor of the terminal device executes the first program, and based on the completion of issuance of the account ownership certificate, The processor of the insurance claim adjusting device outputs the completion of submission of the account ownership certificate to the insurance claim adjusting device, and the processor of the insurance claim adjusting device executes a fifth program to manage insurance contract information identified by the insurance contract identification information. 2 and a third table that manages accident information regarding the digital currency identified by the currency identification information, an insurance claim is assessed based on the insurance claim information. Configured as a billing system.

According to the present invention, when an insured entrusts digital currency account management work to a custody company, it is possible to assess insurance claims for digital currency cyber insurance while ensuring the validity of insurance assessment evidence. I can do it.

The details of at least one implementation of the subject matter disclosed herein are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the disclosed subject matter will be apparent from the following disclosure, drawings, and claims.

FIG. 1 is a block diagram illustrating an example of a device configuration of an insurance claim system according to the present embodiment. FIG. 2 is a block diagram illustrating an example of a terminal device according to the present embodiment. FIG. 1 is a block diagram illustrating an example of an account management device according to the present embodiment. FIG. 1 is a block diagram showing an example of a payment device according to the present embodiment. FIG. 1 is a block diagram illustrating an example of an insurance claim adjustment device according to the present embodiment. FIG. 2 is a diagram illustrating the present embodiment and illustrating an example of a wallet table. It is a figure which shows a present Example and shows an example of a digital currency transaction history table. FIG. 2 is a diagram illustrating an example of an account ownership proof token management table according to the present embodiment. FIG. 2 is a diagram illustrating an example of an account ownership proof token transaction history table according to the present embodiment. It is a figure which shows a present Example and shows an example of an insurance contract table. It is a figure which shows a present Example and shows an example of a billing table. It is a figure which shows a present Example and shows an example of an accident information table. FIG. 2 is a sequence diagram illustrating an example of a processing flow between devices of an insurance claim system according to the present embodiment. 1 is a flowchart illustrating an example of an insurance claim program executed by a terminal device according to the present embodiment. 1 is a flowchart illustrating an example of a certificate issuing program executed by an account management device according to the present embodiment. 2 is a flowchart illustrating an example of an account ownership proof token program executed by a payment device according to the present embodiment. 1 is a flowchart illustrating an example of a claim management program executed by the insurance claim adjustment device according to the present embodiment. 2 is a flowchart illustrating an example of an evidence collection program executed by the insurance claim adjustment device according to the present embodiment. 1 is a flowchart illustrating an example of a loss assessment program executed by an insurance claim assessment device according to the present embodiment.

Hereinafter, embodiments of the present invention will be described based on the accompanying drawings. The embodiments described below do not limit the claimed invention, and all of the elements and combinations thereof described in the embodiments are essential to the solution of the invention. is not limited.

That is, the following description and drawings are examples for explaining the present invention, and are omitted and simplified as appropriate to clarify the explanation. The present invention can also be implemented in various other forms. Unless specifically limited, each component may be singular or plural.

The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

In the following description, various information may be explained using expressions such as "database", "table", and "list", but various information may be expressed using data structures other than these. "XX table", "XX list", etc. are sometimes referred to as "XX information" to indicate that they do not depend on the data structure. When describing identification information, when expressions such as "identification information", "identifier", "name", "ID", and "number" are used, these expressions can be replaced with each other.

If there are multiple components having the same or similar functions, the same reference numerals may be given different suffixes for explanation. However, if there is no need to distinguish between these multiple components, the subscripts may be omitted in the description.

In addition, in the following explanation, processing performed by executing a program may be explained, but the program is executed by a processor (for example, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit)). The processor may be the main body of the processing in order to perform the processing using appropriate storage resources (for example, memory) and/or interface devices (for example, communication ports). Similarly, the subject of processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing the program is a dedicated dedicated circuit that performs specific processing (for example, FPGA (FIELD -PROGRAMMABLE GATE ARRAY) and ASIC (APPLICATION SPECIFIC INTEGRATED CIR). CUIT) may be included .

A program may be installed on a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server includes a processor and a storage resource for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Furthermore, in the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

FIG. 1 is a block diagram illustrating an example of the device configuration of an insurance claims system, which is an assessment system that receives and assesses insurance claims, according to an embodiment of the present invention. In the insurance claim system of this embodiment, in the insurance claim business of cyber insurance for digital currency, when a terminal device submits an insurance claim, after the insurance claim adjustment device accepts the insurance claim, the insured who is the subject of insurance Request submission of proof of account ownership, which is proof of ownership of an account. The terminal device issues an account ownership proof token via the account management device, and transfers the token from the insured's account to the insurance company's account. The insurance claim adjustment device verifies the account ownership certificate, determines whether insurance claims can be paid based on the transaction history of the settlement device, and calculates damages and insurance claims.

The insurance claim system 100 is accessed by a terminal device 200 used by a user making an insurance claim, an account management device 300 owned by the custodian, and companies and organizations that are approved after a predetermined screening process, such as financial institutions such as banks and insurance companies. a payment system 4000 and an insurance claims adjustment device 500. The payment system 4000 includes one or more payment devices 400 owned by companies or organizations that are members of the payment system.

<Terminal device>
FIG. 2 is a block diagram showing an example of the terminal device 200. The terminal device 200 is a computer that includes a memory 201 , a calculation device 202 , an input device 203 , an output device 204 , a communication device 205 , and a storage device 206 .
The storage device 206 stores an insurance claim program 1400 that performs insurance claim processing.

The input device 203 is composed of, for example, a keyboard, a mouse, or a touch panel. The output device 204 includes, for example, a display. The communication device 205 is connected to a network and communicates with other computers.

Insurance claim program 1400 is loaded into memory 201 and executed by computing device 202 .
The arithmetic device 202 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing according to a program of each functional unit. For example, the computing device 202 functions as an insurance claim unit by executing processing according to the insurance claim program 1400. Furthermore, the arithmetic unit 202 also operates as a functional unit that provides functions for each of the plurality of processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

<Account management device>
FIG. 3 is a block diagram showing an example of the account management device 300. The account management device 300 is a computer that includes a memory 301, an arithmetic device 302, an input device 303, an output device 304, a communication device 305, and a storage device 306.

The storage device 306 stores a wallet table 600 that manages the insured's private key, and a certificate issuing program 1500 that issues and transfers account ownership proof tokens.

The input device 303 is composed of, for example, a keyboard, a mouse, or a touch panel. The output device 304 includes, for example, a display. A communication device 305 is connected to a network and communicates with other computers.

The certificate issuing program 1500 is loaded into the memory 301 and executed by the arithmetic unit 302.
The arithmetic device 302 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing according to a program of each functional unit. For example, the computing device 302 functions as a certificate issuing unit by executing processing according to the certificate issuing program 1500. Furthermore, the arithmetic unit 302 also operates as a functional unit that provides functions for each of the plurality of processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

<Payment device>
FIG. 4 is a block diagram showing an example of the payment device 400. The payment device 400 is a computer that includes a memory 401 , a calculation device 402 , an input device 403 , an output device 404 , a communication device 405 , and a storage device 406 .

The storage device 406 includes a digital currency transaction history table 700 that records the transaction history of digital currency, an account ownership proof token management table 800 that manages the state of account ownership proof tokens, and an account ownership table that records the transaction history of account ownership proof tokens. A proof token transaction history table 900, a digital currency program 407 that trades digital currency, and an account ownership proof token program 1600 that trades account ownership proof tokens are stored. There are many types of digital currency programs 407, each of which is stored as one program.

The input device 403 is composed of, for example, a keyboard, a mouse, or a touch panel. The output device 404 includes, for example, a display. A communication device 405 is connected to a network and communicates with other computers.

The digital currency program 407 and the account ownership proof token program 1600 are loaded into the memory 401 and executed by the computing device 402.
The arithmetic device 402 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing according to a program of each functional unit. For example, the computing device 402 functions as a digital currency unit by executing processing according to the digital currency program 407. The same applies to other programs. Furthermore, the arithmetic unit 402 also operates as a functional unit that provides functions for each of the plurality of processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

<Insurance claim assessment device>
FIG. 5 is a block diagram illustrating an example of an insurance claim adjustment device 500. The insurance claim adjustment device 500 is a computer including a memory 501, a calculation device 502, an input device 503, an output device 504, a communication device 505, and a storage device 506.

The storage device 506 includes an insurance contract table 1000 for managing insurance contract information, a claims table 1100 for managing insurance claim status, an accident information table 1200 for recording cyber accident information, and a claim management table for controlling insurance claim assessment processing. A program 1700, an evidence collection program 1800 that collects evidence for claim assessment, and a loss assessment program 1900 that determines the applicability of insurance claim payment reasons and calculates insurance claims are stored.

The input device 503 is composed of, for example, a keyboard, a mouse, or a touch panel. The output device 504 includes, for example, a display. A communication device 505 is connected to a network and communicates with other computers.

Claim management program 1700, evidence collection program 1800, and damage assessment program 1900 are loaded into memory 501 and executed by computing device 502.
The arithmetic device 502 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing according to a program of each functional unit. For example, the computing device 502 functions as a billing management unit by executing processing according to the billing management program 1700. The same applies to other programs. Furthermore, the arithmetic unit 502 also operates as a functional unit that provides functions for each of the plurality of processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

<Data>
FIG. 6 is a diagram showing an example of a wallet table 600. Wallet table 600 is managed by account management device 300.
The wallet table 600 includes an account ID 601, a private key 602, a validity state 603, and a timestamp 604 in one entry.

A unique identifier indicating the insured person's digital currency account is stored in the account ID 601. The private key 602 stores a private key for electronically signing transactions of the payment device 400. A flag indicating whether the account ID 601 is valid or invalid is stored in the valid state 603. The time stamp 604 stores the update time of the wallet record.

FIG. 7 is a diagram showing an example of a digital currency transaction history table 700. Digital currency transaction history table 700 is managed by payment device 400.
The digital currency transaction history table 700 includes a transaction ID 701, a currency ID 702, a transmission source 703, a transmission destination 704, a transaction amount 705, and a time stamp 706 in one entry.

A unique identifier is stored in the transaction ID 701 for each digital currency transaction result. The currency ID 702 stores an identifier indicating the type of digital currency. The sender 703 stores the ID of the account that sent the digital currency. The destination 704 stores the ID of the account that received the digital currency. The transaction amount 705 stores the amount of digital currency transferred in this transaction. The timestamp 706 stores the transaction execution time.

FIG. 8 is a diagram showing an example of an account ownership proof token management table 800. Account ownership proof token management table 800 is managed by payment device 400.
The account ownership proof token management table 800 includes a token ID 801, a token value 802, and an owner 803 in one entry.
The token ID 801 stores a unique identifier of the token. A token value is stored in the token value 802. Owner 803 stores the account ID of the token owner.

FIG. 9 is a diagram showing an example of an account ownership proof token transaction history table 900. The account ownership proof token transaction history table 900 is managed by the payment device 400.
The account ownership proof token transaction history table 900 includes a transaction ID 901, a token ID 902, a token value 903, a sender 904, a sender 905, a signature 906, and a time stamp 907 in one entry.

A unique identifier is stored in the transaction ID 901 for each account ownership proof token transaction result. The token ID 902 stores the ID of the traded token. The token value 903 stores the value of the traded token. The sender 904 stores the ID of the account that sent the token. The destination 905 stores the ID of the account that received the token. The signature 906 stores the electronic signature of the account that executed this transaction. The timestamp 907 stores the transaction execution time.

FIG. 10 is a diagram showing an example of an insurance contract table 1000. The insurance contract table 1000 is managed by the insurance claim adjustment device 500.
The insurance contract table 1000 includes an insurance contract ID 1001, an account ID 1002, a currency ID 1003, an insurance start date 1004, an insurance end date 1005, a coverage rate 1006, and a maximum amount 1007 in one entry.

The unique identifier of the insurance contract is stored in the insurance contract ID 1001. The account ID 1002 stores the account ID of the insured person who has concluded this insurance contract. The currency ID 1003 stores the currency ID of the digital currency to be insured. The insurance start date 1004 stores the application start date of this insurance contract. The insurance end date 1005 stores the application end date of this insurance contract. The coverage rate 1006 stores the rate at which damages are compensated for under this insurance contract. The upper limit amount 1007 stores the upper limit amount of damage compensated under this insurance contract.

FIG. 11 is a diagram showing an example of the billing table 1100. Claim table 1100 is managed by insurance claim adjustment device 500.

The billing table 1100 includes a billing ID 1101, an insurance contract ID 1102, an account ID 1103, a currency ID 1104, a verification code 1105, a verification code timestamp 1106, an account ownership certificate 1107, a payment possibility 1108, an insurance money 1109, A status 1110 is included in one entry.

A unique identifier of an insurance claim is stored in the claim ID 1101. The insurance contract ID 1102 stores an insurance contract ID that is the subject of an insurance claim. The account ID 1103 stores an account ID for which an insurance claim is made. The currency ID 1104 stores a currency ID for which an insurance claim is made. The verification code 1105 stores random numbers used for verification of insurance assessment. The verification code time stamp 1106 stores the verification code issuance time. The account ownership certificate 1107 stores the determination result of the account ownership certificate. The payment possibility 1108 stores the assessment result of insurance claim payability. The insurance money 1109 stores the amount of insurance money to be paid. The status 1110 stores the progress status of insurance assessment.

FIG. 12 is a diagram showing an example of an accident information table 1200. Accident information table 1200 is managed by insurance claim adjustment device 500.
The accident information table 1200 includes an incident ID 1201, a currency ID 1202, an accident content 1203, a cause 1204, a countermeasure 1205, an accident occurrence date 1206, and a countermeasure completion date 1207 in one entry.

Incident ID 1201 stores a unique identifier of a cyber accident related to digital currency. The currency ID 1202 stores the currency ID of the digital currency in which the cyber accident occurred. Accident details 1203 stores accident summary information. The cause 1204 stores the cause of the accident. The countermeasure 1205 stores contents of countermeasures for the accident. The accident occurrence date 1206 stores the date and time when the accident occurred. The countermeasure completion date 1207 stores the date and time when countermeasures for the accident were completed.

<Processing>
In the following explanation, a case will be explained in which an insurance claim assessment is performed for insurance contract ID "P01" as an example, but the present invention is not limited to this.

FIG. 13 is a sequence diagram showing an example of processing performed by the insurance claim system 100.

The terminal device 200 transmits the insurance claim to the insurance claim adjustment device 500 (S1301).
The insurance claim assessment device 500 accepts the insurance claim and transmits a request for submission of account ownership proof to the terminal device 200 (S1302).
The terminal device 200 transmits a request for issuing an account ownership certificate to the account management device 300 (S1303).

The account management device 300 transmits a token issuance request for proof of account ownership to the payment device 400 (S1304).

The payment device 400 executes token issuance processing (S1305) and sends the token transaction result to the account management device 300 (S1306).

The account management device 300 transmits a token transfer request for proof of account ownership to the payment device 400 (S1307).

The payment device 400 executes the token transfer process (S1308) and sends the token transaction result to the account management device 300 (S1309).

The account management device 300 transmits the completion of issuance of the account ownership certificate to the terminal device 200 (S1310).

The terminal device 200 transmits the completion of submission of account ownership proof to the insurance claim adjustment device 500 (S1311).

The insurance claim assessment device 500 determines whether an insurance claim can be paid, calculates the damage and insurance money (S1312), and transmits the assessment result to the terminal device 200 (S1313).

FIG. 14 is a flowchart illustrating an example of an insurance claim program 1400.
In the following explanation, the insurance claim program 1400 will be described as the main body of processing, but the calculation device 202 may also be the main body of processing.

The insurance claim program 1400 displays an insurance claim form on the output device (S1401).
Next, the insurance claim program 1400 receives user input using the input device and generates insurance claim information (S1402). The insurance claim information includes an insurance contract ID, an account ID, and a currency ID as information related to insurance claim procedures. For example, insurance claim information is a message {insurance contract ID: P01, account ID: user01, currency ID: PU085}.
Next, the insurance claim program 1400 transmits the insurance claim to the insurance claim adjustment device 500 (S1403).
Next, the insurance claim program 1400 receives a request to submit account ownership proof from the insurance claim adjustment device 500 (S1404).
Next, the insurance claim program 1400 transmits a request to issue an account ownership certificate to the account management device 300 (S1405).
Next, the insurance claim program 1400 receives the completion of issuance of the account ownership certificate from the account management device 300 (S1406).
Next, the insurance claim program 1400 transmits the completion of submission of account ownership proof to the insurance claim adjustment device 500 (S1407).
Next, the insurance claim program 1400 receives the assessment result from the insurance claim assessment device (S1408).

FIG. 15 is a flowchart showing an example of the certificate issuing program 1500.
In the following description, the certificate issuing program 1500 will be described as the main body of processing, but the computing device 302 may also be the main body of processing.

The certificate issuance program 1500 receives an account ownership certificate issuance request from the terminal device 200 (S1501). For example, the issuance request is a message {insurance contract ID: P01, currency ID: PU085, insured account ID: user01, insurance company account ID: insurance01, verification code: h8ex3h}.

The certificate issuance program 1500 extracts the insurance contract ID, currency ID, insured person account ID, insurance company account ID, and verification code from the issuance request message (S1502).

The certificate issuing program 1500 inputs the insurance contract ID, insured account ID, currency ID, and verification code into a hash function to generate a hash value (S1503).

The certificate issuing program 1500 transmits a token transaction request to the payment device 400 in order to perform a token issuing transaction (S1504). A token transaction request is issued to the request category, the token ID is the insurance contract ID, the token value is the hash value generated in the previous step, the sender is the custody account ID, the destination is the insured account ID, and the signature is the custody private key. It has the information that it is an electronic signature. For example, the token transaction request is a message {request classification: issued, token ID: P01, token value: xjfi9j3424la890d, sender: Bank02, sender: user01, signature: sig-bank02}.

The certificate issuing program 1500 receives the token transaction result from the payment device 400 (S1505).

The certificate issuing program 1500 transmits a token transaction request to the payment device 400 in order to perform a token transfer transaction (S1506). The token transaction request is transferred to the request category, has the following information: the token ID is the insurance contract ID, the sender is the insured's account ID, the destination is the insurance company account ID, and the signature is an electronic signature using the insured's private key. . For example, a token transaction request is a message {request classification: transfer, token ID: P01, sender: user01, sender: insurance01, signature: sig-user01}.
The certificate issuing program 1500 receives the token transaction result from the payment device 400 (S1507).
The certificate issuing program 1500 transmits the completion of issuing the account ownership certificate to the terminal device 200 (S1508).

FIG. 16 is a flowchart showing an example of an account ownership proof token program 1600.
In the following description, the account ownership proof token program 1600 will be described as the main body of processing, but the processing unit 402 may also be the main body of processing.

The account ownership proof token program 1600 receives a token transaction request from the account management device 300 (S1601).

The account ownership proof token program 1600 refers to the request category of the token transaction request message and determines the details of the requested transaction (S1602). In the case of issuance, the process advances to S1603. In the case of relocation, the process advances to S1610.

The account ownership proof token program 1600 extracts the token ID, token value, sender, destination, and signature from the token transaction request (S1603). For example, the following values are extracted from the token transaction request: token ID: P01, token value: xjfi9j3424la890d, sender: bank02, sender: user01, and signature: sig-bank02.

The account ownership proof token program 1600 searches the account ownership proof token management table 800 using the token ID as a key (S1604).

The account ownership proof token program 1600 determines whether a record with the same token ID exists in order to prevent double requests for account ownership proof (S1605). If Yes, the issuance transaction is interrupted due to double billing and the process proceeds to S1614. If No, the process advances to S1606 for a new request.

The account ownership proof token program 1600 adds a record to the account ownership proof token management table 800 (S1606). Data items of the record are token ID, token value, and owner. The values extracted from the token transaction request are set in the token ID and token value. Set the value of the destination of the token transaction request to the owner. For example, the account ownership proof token management record has information such as token ID: P01, token value: xjfi9j3424la890d, and owner: user01.

The account ownership proof token program 1600 adds a record to the account ownership proof token transaction history table 900 (S1607). The data items of the record are transaction ID, token ID, token value, sender, sender, signature, and timestamp. The transaction ID is set to a value that uniquely identifies the transaction. The values extracted from the token transaction request are set in the token ID, token value, sender, destination, and signature. The timestamp is set to the time the transaction was executed. For example, the account ownership proof token transaction history record is transaction ID: x2nd8hapo, token ID: P01, token value: xjfi9j3424la890d, sender: Bank02, sender: user01, signature: sig-bank02, timestamp: 2022/02/11 It has the information 14:23:01.

The account ownership proof token program 1600 sets the status of the token transaction result to success (S1608).

The account ownership proof token program 1600 sends the token transaction result to the account management device 300 (S1609).

The account ownership proof token program 1600 extracts the token ID, sender, sender, and signature from the token transaction request (S1610). For example, the following values are extracted from the token transaction request: token ID: P01, sender: user01, sender: insurance01, and signature: sig-user01.

The account ownership proof token program 1600 searches the account ownership proof token management table 800 using the token ID as a key (S1611).

The account ownership proof token program 1600 determines whether a record with the same token ID exists in order to prevent a non-existing account ownership proof from being submitted to an insurance company (S1612). If Yes, the process advances to S1613 because account ownership proof exists. If No, the account ownership signature does not exist, so the transfer transaction is interrupted and the process advances to S1614.

The account ownership proof token program 1600 updates the owner of the account ownership proof token management table 800 (S1613). Set the value of the destination of the token transaction request to the owner. For example, the account ownership proof token management record has information such as token ID: P01, token value: xjfi9j3424la890d, and owner: insurance01.

If the account ownership proof token program 1600 interrupts the issuance transaction or transfer transaction, it sets the status of the token transaction result to failure (S1614).

FIG. 17 is a flowchart illustrating an example of the billing management program 1700.
In the following description, the billing management program 1700 will be described as the main body of processing, but the computing device 502 may also be the main body of processing.

The claim management program 1700 receives an insurance claim from the terminal device 200 (S1701). The insurance claim information includes an insurance contract ID, an account ID, and a currency ID as information related to insurance claim procedures. For example, insurance claim information is a message {insurance contract ID: P01, account ID: user01, currency ID: PU085}.

The billing management program 1700 adds insurance billing information to the billing table 1100 (S1702). The request ID is set to a value that uniquely identifies the request. The insurance contract ID, account ID, and currency ID are set to values extracted from the insurance claim. The status is set to a value of billing accepted. For other data items, leave them blank at this point. For example, the billing record has information such as billing ID: C101, insurance contract ID: P01, account ID: user01, currency ID: PU085, and status: billing acceptance.

The billing management program 1700 executes the evidence collection program 1800 (S1703).
The claim management program 1700 executes the damage assessment program 1900 (S1704).
The billing management program 1700 acquires the record after the completion of the assessment from the billing table 1100 (S1705).
The billing management program 1700 notifies the terminal device 200 of the assessment result (S1706).

FIG. 18 is a flowchart illustrating an example of the evidence collection program 1800.
In the following description, the evidence collection program 1800 will be described as the main body of processing, but the computing device 502 may also be the main body of processing.

The evidence collection program 1800 receives an evidence collection request from the billing management program 1700 (S1801). The evidence collection request includes a request ID. For example, the evidence collection request is a message {request ID: C101}.

The evidence collection program 1800 extracts the request ID from the evidence collection request message (S1802). For example, the billing ID is C101.

The evidence collection program 1800 searches the billing table using the billing ID and obtains the billing record (S1803).

The evidence collection program 1800 generates a random number of verification code for the request (S1804). The verification code is used to verify that proof of account ownership has been issued for the insured digital currency. There are various types of digital currencies, so which digital currency is suitable for cyber incidents depends on the situation. Additionally, a single cyber incident may affect multiple digital currencies. Therefore, when making an insurance claim, the insured person selects the digital currency that has suffered damage and makes an insurance claim. If proof of account ownership for a digital currency that is not covered by insurance is submitted, the claims adjuster must deny the claim. A verification code is issued for the reasons mentioned above. The assessment method using the verification code will be described in the flowchart of the damage assessment program 1900.

The evidence collection program 1800 adds the verification code and verification code time stamp to the billing table 1100 (S1805). Set the random number generated in the previous step to the verification code. The verification code timestamp is set to the time when the verification code was generated. For example, the billing record is billing ID: C101, insurance contract ID: P01, account ID: user01, currency ID: PU085, verification code: h8ex3h, verification code timestamp: 2022/02/11 14:21:50, status: It has information such as billing reception.

The evidence collection program 1800 transmits a request to submit account ownership proof to the terminal device 200 (S1806). The request for submission of account ownership proof includes an insurance contract ID, a currency ID, an insured account ID, an insurance company account ID, and a verification code. For example, the request to submit proof of account ownership is a message {insurance contract ID: P01, currency ID: PU085, insured account ID: user01, insurance company account ID: insurance01, verification code: h8ex3h}.

The evidence collection program 1800 receives an account ownership certificate submission completion notification from the terminal device 200 (S1807).

The evidence collection program 1800 updates the status of the claim table to awaiting assessment (S1808).

FIG. 19 is a flowchart illustrating an example of the damage assessment program 1900.
In the following description, the damage assessment program 1900 will be described as the main body of processing, but the arithmetic device 502 may also be the main body of processing.

The damage assessment program 1900 receives a damage assessment request from the claim management program 1700 (S1901). The claim ID is included in the damage assessment request. For example, the damage assessment request is a message {Claim ID: C101}.

The damage assessment program 1900 extracts the claim ID from the damage assessment request message (S1902). For example, the billing ID is C101.

The damage assessment program 1900 searches the claim table 1100 using the claim ID and obtains a claim record (S1903).

The loss assessment program 1900 extracts the insurance contract ID, account ID, currency ID, verification code, and verification code time stamp from the claim record (S1904). For example, the following information is extracted: billing ID: C101, insurance contract ID: P01, account ID: user01, currency ID: PU085, verification code: h8ex3h, verification code timestamp: 2022/02/11 14:21:50.

The loss assessment program 1900 searches the insurance contract table 1000 using the insurance contract ID and obtains the insurance contract record (S1905).

The loss assessment program 1900 extracts the account ID, currency ID, insurance start date, and insurance end date from the insurance contract record (S1906). For example, the following information is extracted: insurance contract ID: P01, account ID: user01, currency ID: PU085, insurance start date: 2022/01/01, insurance end date: 2022/03/31.
The loss assessment program 1900 compares the account ID in the claim record with the account ID in the contract record in order to verify whether the account ID for which the insurance claim was made is the account ID to be insured (S1907).

The damage assessment program 1900 determines whether the account IDs match (S1908). If Yes, the process advances to S1909. If No, the request details do not match the insurance contract, so the assessment process is interrupted and the process advances to S1937.

The loss assessment program 1900 compares the currency ID of the claim record with the currency ID of the contract record in order to verify whether the currency ID of the insurance claim is the currency ID of the insurance target (S1909).

The damage assessment program 1900 determines whether the currency IDs match (S1910). If Yes, the process advances to S1911. If No, the request details do not match the insurance contract, so the assessment process is interrupted and the process advances to S1937.

The loss assessment program 1900 extracts records that match the condition "Currency ID=Currency ID AND Accident occurrence date>=Insurance start date AND Accident occurrence date<=Insurance end date" from the accident information table 1200 (S1911). For example, the search is performed using the following conditions: currency ID=PU085 AND date of accident >=2022/01/01 AND date of accident <=2022/03/31.

The loss assessment program 1900 determines whether there is an accident information record that meets the conditions of the step above in order to verify whether the occurrence of a cyber accident has been reported during the insurance period for the digital currency to be insured (S1912 ). If Yes, a cyber accident has occurred, so the process advances to S1913 to continue the assessment process. In the case of No, since no cyber accident has occurred, the assessment process is interrupted and the process proceeds to S1937.

In order to confirm the issuance history of the account ownership signature token, the loss assessment program 1900 retrieves the following information from the account ownership proof token transaction history table 900 of the payment device 400: “Token ID = Insurance contract ID AND Sender = Custody account ID AND Destination = Victim. Records matching the condition "insurer account ID" are extracted (S1913). For example, the search is performed using the following conditions: token ID=P01 AND source=Bank02 AND destination=user01.

The damage assessment program 1900 determines whether an account ownership proof token transaction history record exists (S1914). If Yes, the process advances to S1915 to continue the assessment process. If No, the assessment process is interrupted and the process advances to S1926.

The damage assessment program 1900 extracts the signature and time stamp from the account ownership proof token transaction history record (S1915). For example, signature: sig-bank02, timestamp: 2022/02/11 14:23:01.

In order to verify that the account ownership proof token was issued to the custodian, the damage assessment program 1900 determines whether the signature extracted in the step above is the custodian's signature (S1916). If Yes, the process advances to S1917 to continue the assessment process. If No, the assessment process is interrupted and the process advances to S1926.

The damage assessment program 1900 compares the verification code timestamp of the billing record with the timestamp of the account ownership certificate token transaction record in order to prevent the reuse of account ownership certificates issued in the past (S1917). One of the conditions for payment of insurance claims is that at the time of the insurance claim, the insured must be the account holder of the insured digital currency and the private key must be kept securely. If you resubmit the proof of account ownership issued in the past, you will not be able to confirm the current account management status. Therefore, it is necessary to verify that the account ownership proof token was issued after the insurance claim.

The damage assessment program 1900 determines whether the verification code timestamp of the billing record is earlier than the timestamp of the account ownership proof token transaction record (S1918). If Yes, the process advances to S1919 to continue the assessment process. If No, the assessment process is interrupted and the process advances to S1926.

In order to confirm the transfer history of the account ownership signature token, the loss adjustment program 1900 retrieves the following information from the account ownership proof token transaction history table 900 of the payment device 400: “Token ID = Insurance contract ID AND Sender = Insured account ID AND Destination =Insurance company account ID" is extracted (S1919). For example, the search is performed using the following conditions: token ID=P01 AND source=user01 AND destination=insurance01.

The damage assessment program 1900 determines whether an account ownership proof token transaction history record exists (S1920). If Yes, the process advances to S1915 to continue the assessment process. If No, the assessment process is interrupted and the process advances to S1926.

The damage assessment program 1900 extracts the token value and signature from the account ownership proof token transaction history record (S1921). For example, token value: xjfi9j3424la890d, signature: sig-user01.

The loss adjustment program 1900 determines whether the signature extracted in the previous step is the insured's signature in order to verify that the insured's keys are securely managed and ready for digital currency transactions. to judge. (S1922). If Yes, the process advances to S1923 to continue the assessment process. If No, the assessment process is interrupted and the process advances to S1926.

The loss assessment program 1900 inputs the insurance contract ID, insured account ID, currency ID, and verification code obtained from the claim record into a hash function to generate a hash value (S1923).

The loss adjustment program 1900 verifies that the account ownership certificate was issued for the insured digital currency by verifying that the hash value generated in the previous step matches the token value obtained from the account ownership token transaction history record. It is determined whether to do so (S1924). If Yes, the process advances to S1925 to continue the assessment process. If No, the assessment process is interrupted and the process advances to S1926. The hash value compared in this step is a unique value for the combination of account ID and digital currency ID. If it is an account ID or proof of account ownership for digital currency that is not covered by insurance, the token value will be different and will not match the hash value. This verifies that proof of account ownership has been issued for the insured digital currency.

The damage assessment program 1900 updates the account ownership certificate in the billing table to OK (S1925).
The damage assessment program 1900 updates the account ownership certificate in the billing table to NG (S1926).
The damage assessment program 1900 extracts the accident occurrence date and countermeasure completion date from the accident information record (S1927). For example, information such as accident occurrence date: 2022/02/07 and countermeasure completion date: 2022/02/09 is extracted.

The loss assessment program 1900 uses the digital currency transaction history table 700 of the payment device 400 to collect information on digital currency transactions made to the insured's account between the occurrence of the cyber accident and the completion of countermeasures. Records that match the condition "Currency ID=Currency ID AND (Sender=Account ID OR Destination=Account ID) AND Time stamp>=Date of accident Time stamp<=Date of countermeasure completion" are extracted (S1928). For example, the search is performed using the following conditions: currency ID=PU085 AND (sender=user01 OR destination=user01) AND timestamp>=2022/02/07 timestamp<=2022/02/09.

The damage assessment program 1900 extracts the transaction amount from the transaction history record group acquired in the above step and totals the fluctuation amount (S1929). The amount of change is the amount of digital currency that changed between the occurrence of a cyber accident and the completion of countermeasures against the digital currency that was carried out on the insured's account. If this total value is negative, that amount is considered as the amount of damage, and the amount of damage is considered as the damage caused by the cyber accident. If the total value is positive or zero, it is determined that there was no damage due to the cyber accident.

The damage assessment program 1900 determines whether the amount of change compiled in the above step is positive or negative (S1930). If the value is negative, the process advances to S1931. If the value is plus or zero, the assessment process is interrupted and the process advances to S1937.

The loss assessment program 1900 extracts the coverage rate and upper limit amount from the insurance contract record (S1931). For example, the information is that the coverage rate is 80 and the upper limit is 1000.

The loss assessment program 1900 calculates insurance money by multiplying the amount of change compiled from the digital currency transaction history by the coverage rate (S1933). For example, if the variable amount is 1000, the insurance amount will be 800 by multiplying by 80% of the coverage rate.

The loss assessment program 1900 determines whether the insurance money calculated in the step above exceeds the upper limit (S1934). If Yes, the process advances to S1935 to correct the insurance money. If No, the insurance money is finalized, so the process advances to S1936.

The loss assessment program 1900 changes the insurance money to the upper limit amount (S1935). For example, if the calculated insurance money is 1500 and the upper limit is 1000, the insurance money is changed to 1000, which is the upper limit.

The loss assessment program 1900 records the calculated insurance money in the insurance money in the claim table 1100, and updates the payability to OK (S1936).

The damage assessment program 1900 updates the payment possibility in the billing table 1100 to “no” (S1937).

The damage assessment program 1900 updates the status of the claim table to completed (S1938).

As described above, in this embodiment, as described using FIG. , each device has a processor and a memory, and the processor of the terminal device 200 executes a first program (insurance claim program 1400) to obtain insurance information regarding insurance claim procedures for digital currency input by the user. The claim information is output to the insurance claim adjustment device 500, and the processor of the insurance claim adjustment device 500 executes a second program (claim management program 1700) to obtain information about the user included in the insurance claim information. The terminal device 200 is requested to submit an account ownership certificate to prove that the user identified by the account ID for identifying the account owns the account as an insured person. The processor executes the first program and outputs the account ownership certificate issuance request to the account management device 300, and the processor of the account management device 300 executes the third program (certificate issuance program 1500). ) is generated using the insurance contract ID for identifying the insurance contract of the digital currency, the account ID, and the currency ID for identifying the digital currency, which are included in the insurance claim information. A request for issuance of the account ownership proof token whose owner is the insured person is output to the payment device 400, and the processor 400 of the payment device executes a fourth program (account ownership proof token program 1600). The token that received the issuance request is added to a first table (account ownership proof token management table 900) that associates the token ID for identifying the token, the value of the token, and the owner of the token. and outputs the added result to the account management device 300 as the token issuance transaction result, and the processor of the account management device 300 executes the third program to add the result to the token issuance transaction result. , a transfer request indicating that the owner of the added token is the insurance company is output to the payment device 400, and the processor of the payment device 400 executes the fourth program to add the token to the first table. update the owner of the token to the insurance company, output the updated result to the account management device 300 as a token transfer transaction result, and the processor of the account management device 300 executes the third program. Then, upon receiving the token transfer transaction result from the payment device 400, outputs completion of issuance of the account ownership certificate to the terminal device 200, and the processor of the terminal device 200 executes the first program. , based on the completion of issuance of the account ownership certificate, outputs completion of submission of the account ownership certificate to the insurance claim adjustment device 500, and the processor of the insurance claim adjustment device 500 executes a fifth program (damage adjustment program 1900). a second table (insurance contract table 1000) that executes and manages insurance contract information identified by the above-mentioned insurance contract ID, and a third table that manages accident information regarding the digital currency identified by the above-mentioned currency ID. (Accident Information Table 1200) is used to assess the insurance claim based on the insurance claim information.

In other words, this embodiment includes a terminal device 200 having a processor and memory, an account management device 300 having a processor and memory, a payment device 400 having a processor and memory, and an insurance claim adjustment device 500 having a processor and memory. In the insurance claim system 100, when the terminal device 200 submits an insurance claim, the insurance claim adjustment device 500 requests the submission of account ownership proof after accepting the insurance claim, and the terminal device 200 receives the insurance claim from the account management device. 300 and transfers the token from the insured's account to the insurance company's account; the insurance claims adjuster 500 verifies the insured's proof of ownership of the insured account; Based on the transaction history of the payment device 400, it is determined whether insurance claims can be paid or not, and damages and insurance claims are calculated.

This creates a situation where the insured and the insurance company do not trust each other when the insured entrusts digital currency account management to a custodian. In situations where information asymmetry exists, the custody account management device mediates the collection of evidence, complementing the relationship of mutual trust and making it possible to assess insurance claims for digital currency cyber insurance. Furthermore, the scope of cyber insurance applicable to digital currencies will be expanded, contributing to the protection of consumers who use digital currencies.

Further, as explained using S1605 of FIG. 16, etc., the processor of the payment device 400 executes the fourth program to generate a token for identifying the token having the same ID as the insurance contract ID. The above-mentioned correspondence is performed using the ID, and the above-mentioned token is added to the above-mentioned first table. As a result, the token ID of the account ownership proof token will be the same ID as the insurance contract ID, and if the token ID and insurance contract ID overlap at the time of a token issuance request, the issuance request will be rejected to eliminate the duplicate token ID. As a result, double requests for account ownership proof for one insurance contract can be prevented.

Furthermore, as described using FIGS. 1503, S1504, and S1607 of FIG. 16, the processor of the account management device 300 executes the third program to enter the insurance contract ID, account ID, and currency ID. In addition, a verification code for verifying the assessment of the insurance claim generated by the insurance claim assessment device 500 is input to a hash function to generate a hash value, and the generated hash value is used as the value of the token. The processor of the payment device 400 executes the fourth program, associates the token with each issued transaction, and outputs the token for proof of account ownership to the payment device 400. (account ownership proof token transaction history table 900). This makes it possible to centrally manage the transaction history of account ownership proof tokens using hash values as token values throughout the system.

Further, as explained using S1923 of FIG. 19, etc., the processor of the insurance claim adjustment device 500 executes the fifth program to determine the insurance claim information when receiving the insurance claim information from the terminal device 200. Input the contract ID, the account ID, the currency ID, and the verification code into a hash function to generate a hash value, and whether the generated hash value matches the token value recorded in the fourth table. Determine whether This makes it possible to verify that the account ownership proof token has been issued for the digital currency to be insured. In other words, the custody embeds a unique hash value for each insured item generated from insurance contract information and a verification code (random number) into the account ownership proof token, and the insurance company uses the hash value it generated itself and the hash value extracted from the token. Compare with the value. By verifying that the hash values do not match when the account ID and currency ID are different, it is possible to reject proof of account ownership for digital currencies that are not covered by insurance.

In addition, as explained using steps S1915-1917 in FIG. 19, the processor of the account management device 300 executes the third program to generate information generated by the insurance claim adjustment device 500 when making the insurance claim. The processor of the account management device 300 executes the third program to generate the token ID for identifying the token, the value of the token, and the issuer. The timestamp of the time when the transaction was executed is recorded in a fifth table (account ownership proof token transaction history table 900) similar to the fourth table in association with each of the above-mentioned issuance transactions of the above-mentioned token, and the above-mentioned payment is made. The processor of the device 400 executes the fifth program to assess the insurance claim based on the insurance claim information if the timestamp of the verification code is earlier than the timestamp of the time when the issuance transaction was executed. I do. This makes it possible to verify that the timestamp of the verification code issued at the time of accepting an insurance claim is earlier than the timestamp of the account ownership proof token, and prevent the reuse of account ownership proof tokens issued in the past.

Traditionally, two-tier digital currency systems have adopted private blockchains, and because users deposit their private keys for managing their digital currency accounts in the custody of banks or other institutions, users (i.e., insured persons) themselves have to prove account ownership. There was an issue with not being able to submit it to the insurance company. As explained above, according to this embodiment, when an insurance claim is received from an insured in order to resolve the issue, the custodian issues an account ownership proof token and transfers the token from the insured's account to the insurance company. By transferring the information to the company, the insured's ownership of the insured account is verified, and based on the transaction history of the digital currency system, it is determined whether insurance claims can be paid or not, and damages and insurance proceeds are calculated. This makes it possible to ensure the validity of the account ownership certificate submitted by the insured through custody. Additionally, various types of digital tokens can be issued, and the transaction history of those tokens is recorded in a ledger and shared among stakeholders. Therefore, it will be possible to track the changes in token ownership.

As described above, in the digital currency insurance claims system of this embodiment, even if there is information asymmetry between the insured and the insurance company, insurance assessment can be performed based on valid evidence. can. In the above embodiment, the case where the contract ID is P101, the account ID is 101, and the currency ID is PU085 is used as an example of bill assessment, but the present invention is not limited to this. There are various billing assessments, such as when the contract ID, account ID, and currency ID are different.

Furthermore, although information is stored in a table as an example in this embodiment, the information is not limited to a table and may be stored as schema-less data.

The present invention is not limited to the above-described embodiments as they are, and in the implementation stage, the components may be modified and embodied without departing from the gist thereof, or multiple components disclosed in the above-described embodiments may be embodied. These can be implemented in appropriate combinations.

200 Terminal device 300 Account management device 400 Payment device 500 Insurance claim adjustment device 600 Wallet table 700 Digital currency transaction history table 800 Account ownership proof token management table 900 Account ownership proof token transaction history table 1000 Insurance contract table 1100 Claim table 1200 Accident information table 1400 Insurance Claim Program 1500 Certificate Issuance Program 1600 Account Ownership Proof Token Program 1700 Claim Management Program 1800 Evidence Collection Program 1900 Loss Adjustment Program

Claims

An insurance claim system comprising a terminal device, an account management device, a payment device, and an insurance claim adjustment device,
Each device has a processor and a memory;
The processor of the terminal device executes a first program and outputs insurance claim information regarding the digital currency insurance claim procedure input by the user to the insurance claim adjustment device;
The processor of the insurance claim adjustment device executes a second program to enable a user identified by account identification information for identifying the user's account included in the insurance claim information to establish an account as an insured person. requesting the terminal device to submit proof of account ownership to prove ownership;
The processor of the terminal device executes the first program and outputs a request for issuing the account ownership certificate to the account management device;
The processor of the account management device executes a third program to collect insurance contract identification information for identifying an insurance contract of the digital currency, the account identification information, and the digital currency included in the insurance claim information. outputting to the payment device a request for issuance of a token proving ownership of the account whose owner is the insured person, which is generated using digital currency identification information for identification;
The processor of the payment device executes a fourth program and stores the issued information in a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token. Adding the requested token, outputting the added result to the account management device as a token issuance transaction result,
The processor of the account management device executes the third program and outputs a transfer request to the payment device for the token issuance transaction result in which the owner of the added token is an insurance company;
The processor of the payment device executes the fourth program to update the owner of the token added to the first table to the insurance company, and updates the updated result as the token transfer transaction result. Output to account management device,
When the processor of the account management device executes the third program and receives the token transfer transaction result from the payment device, the processor outputs the completion of issuance of the account ownership certificate to the terminal device;
The processor of the terminal device executes the first program and outputs the completion of submission of the account ownership certificate to the insurance claim adjustment device based on the completion of issuance of the account ownership certificate,
The processor of the insurance claim adjustment device executes a fifth program to create a second table for managing insurance contract information identified by the insurance contract identification information, and a second table for managing insurance contract information identified by the currency identification information. assessing an insurance claim based on the insurance claim information using a third table for managing accident information;
An insurance claim system characterized by:
The insurance claim system according to claim 1,
The processor of the payment device executes the fourth program to perform the association using account ownership proof token identification information for identifying the token having the same identification information as the insurance contract identification information, adding the token to the first table;
An insurance claim system characterized by:
The insurance claim system according to claim 1,
The processor of the account management device executes the third program, and in addition to the insurance contract identification information, the account identification information, and the digital currency identification information, the processor of the account management device also executes the third program to obtain the insurance contract identification information, the account identification information, and the digital currency identification information. Inputting a verification code for verifying the assessment of the claim into a hash function to generate a hash value, outputting the account ownership proof token to the payment device with the generated hash value as the value of the token,
The processor of the payment device executes the fourth program to associate the token with each issued transaction and record it in a fourth table.
An insurance claim system characterized by:
The insurance claim system according to claim 3,
The processor of the insurance claim adjustment device executes the fifth program to obtain the insurance contract identification information, the account identification information, the digital currency identification information, and the verification upon receiving the insurance claim information from the terminal device. inputting the code into a hash function to generate a hash value, and determining whether the generated hash value matches the token value recorded in the fourth table;
An insurance claim system characterized by:
The insurance claim system according to claim 1,
The processor of the account management device executes the third program to output a timestamp of the verification code generated in the insurance claim adjustment device at the time of the insurance claim,
The processor of the account management device executes the third program to obtain the token identification information for identifying the token, the value of the token, and the timestamp of the time when the issuance transaction was executed. Recording in a fifth table in association with each of the issuance transactions of the token,
The processor of the payment device executes the fifth program, and if the timestamp of the verification code is earlier than the timestamp of the time when the issuance transaction was executed, the processor of the payment device executes the fifth program to process the insurance claim based on the insurance claim information if the timestamp of the verification code is earlier than the timestamp of the time when the issuing transaction was executed. carry out an assessment,
An insurance claim system characterized by:
An insurance claim method performed in an insurance claim system having a terminal device, an account management device, a payment device, and an insurance claim adjustment device, each having a processor and a memory,
The terminal device outputs insurance claim information related to the digital currency insurance claim procedure input by the user to the insurance claim adjustment device,
The insurance claim adjustment device generates an account for proving that the user identified by the account identification information for identifying the user's account included in the insurance claim information owns the account as an insured person. requesting the terminal device to submit proof of ownership;
The terminal device outputs a request for issuing the account ownership certificate to the account management device,
The account management device uses insurance contract identification information for identifying the insurance contract of the digital currency, the account identification information, and digital currency identification information for identifying the digital currency, which are included in the insurance claim information. outputting a request for issuance of a token proving ownership of the account whose owner is the insured person to the payment device;
The payment device adds the token that received the issuance request to a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token, and outputting the added result to the account management device as a token issuance transaction result;
The account management device outputs a transfer request to the payment device that specifies that the owner of the added token is an insurance company in response to the token issuance transaction result;
The payment device updates the owner of the token added to the first table to the insurance company, and outputs the updated result to the account management device as a token transfer transaction result,
When the account management device receives the token transfer transaction result from the payment device, the account management device outputs the completion of issuance of the account ownership certificate to the terminal device,
The terminal device outputs the completion of submission of the account ownership certificate to the insurance claim adjustment device based on the completion of issuance of the account ownership certificate,
The insurance claim adjustment device includes a second table that manages insurance contract information identified by the insurance contract identification information, and a third table that manages accident information regarding digital currency identified by the currency identification information. using the insurance claim information to assess the insurance claim based on the insurance claim information;
An insurance claim method characterized by:
The insurance claim method according to claim 6,
The payment device performs the association using account ownership proof token identification information for identifying the token having the same identification information as the insurance contract identification information, and adds the token to the first table.
An insurance claim method characterized by:
The insurance claim method according to claim 6,
In addition to the insurance contract identification information, the account identification information, and the digital currency identification information, the account management device further includes a verification code for verifying the assessment of the insurance claim generated by the insurance claim assessment device. , generate a hash value by inputting it to a hash function, and output the account ownership proof token to the payment device with the generated hash value as the value of the token;
The payment device records the token in a fourth table in association with each issued transaction.
An insurance claim method characterized by:
9. The insurance claim method according to claim 8,
The insurance claim adjustment device inputs the insurance contract identification information, the account identification information, the digital currency identification information, and the verification code when receiving the insurance claim information from the terminal device into a hash function to generate a hash value. generating and determining whether the generated hash value matches the token value recorded in the fourth table;
An insurance claim method characterized by:
The insurance claim method according to claim 6,
The account management device outputs a timestamp of the verification code generated in the insurance claim adjustment device at the time of the insurance claim,
The account management device associates token identification information for identifying the token, the value of the token, and a timestamp of the time when the issuance transaction was executed for each of the issuance transactions of the token, and Record it in the table of 5,
The payment device assesses the insurance claim based on the insurance claim information when the timestamp of the verification code is earlier than the timestamp of the time when the issuing transaction was executed.
An insurance claim method characterized by:
A computer having a processor and memory,
A process of outputting insurance claim information related to the digital currency insurance claim procedure input by the user;
requesting submission of proof of account ownership to prove that the user identified by the account identification information for identifying the user's account included in the insurance claim information owns the account as an insured person; processing and
a process of outputting a request for issuance of the account ownership certificate;
The insurance contract identification information for identifying the insurance contract of the digital currency, the account identification information, and the digital currency identification information for identifying the digital currency included in the insurance claim information. a process of outputting a request for issuance of a token proving ownership of the account whose owner is the insurer;
The token that received the issuance request is added to a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token, and the added result is added to the first table. Processing to output as issue transaction results,
a process of outputting a transfer request that makes the owner of the added token an insurance company in response to the token issuance transaction result;
a process of updating the owner of the token added to the first table to the insurance company and outputting the updated result as a token transfer transaction result;
Upon receiving the token transfer transaction result, a process of outputting completion of issuance of the account ownership certificate;
a process of outputting completion of submission of the account ownership certificate based on completion of issuance of the account ownership certificate;
The insurance claim is made using a second table that manages insurance contract information identified by the insurance contract identification information and a third table that manages accident information regarding the digital currency identified by the currency identification information. the process of making an informed insurance claim assessment;
An insurance claim program characterized by causing execution of.