JP7574014B2 - Information system, information processing device, information processing method, and program - Google Patents

Description

The present invention relates to an information system that processes tokens in a blockchain.

Conventionally, there have been token trading support systems that allow token trading to be conducted smoothly and efficiently (see, for example, Patent Document 1).

In this token trading support system, the control unit of the trading support server acquires user authentication information from the accessed user terminal, performs user authentication, and when user authentication is complete, identifies all wallets held by the user, acquires balance information for each virtual currency and each token in each wallet, acquires trading price information for each virtual currency and each token from each exchange server, and outputs the balance information and trading price information to the user terminal.

JP 2020-53082 A

However, in conventional technology, when approval is given for processing of tokens in a blockchain that satisfies predetermined conditions, it is not possible to perform processing of the tokens corresponding to that approval.

As a result, it was not possible to perform appropriate recovery for certain processes, such as recovery processes when a user loses key information.

The information system of the first invention is an information system comprising a request terminal that transmits request information having a request identifier that identifies a request for processing related to a token, two or more approval devices that transmit approval information indicating approval of the request, and an information processing device, the request terminal comprises a terminal reception unit that receives the request information, and a terminal transmission unit that transmits the request information to the information processing device, the approval device comprises a first approval storage unit in which a private key is stored, a second approval storage unit in which request specific information that identifies the request to be approved is stored, an approval reception unit that receives an approval instruction that is an instruction to approve the request, and after the approval reception unit receives the approval instruction, signs information including the request specific information using the private key, This information system includes an approval acquisition unit that configures approval information and an approval transmission unit that transmits the approval information to an information processing device. The information processing device includes a request receiving unit that receives request information transmitted from a request terminal, an approval receiving unit that receives approval information transmitted from two or more approval devices, an approval determination unit that obtains request specific information using a request identifier contained in the request information received by the request receiving unit and determines whether the approval information corresponding to the request specific information and received by the approval receiving unit satisfies a predetermined condition, and a token processing unit that performs token processing related to the token, which is processing corresponding to the request identifier, when the approval determination unit determines that the predetermined condition is satisfied.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

In addition, the information system of the second invention is an information system in which the approval device includes a first terminal and a second terminal, the first terminal includes a first approval storage unit in which a private key is stored, and a first transmission unit that transmits the private key to the second terminal, and the second terminal includes a second approval storage unit in which request specific information that identifies the request to be approved is stored, an approval receiving unit that receives an approval instruction that is an instruction to approve the request, a second receiving unit that receives the private key from the first terminal, an approval acquisition unit that uses the private key to sign information including the request specific information and composes the approval information, and an approval transmission unit that transmits the approval information to the information processing device.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

In addition, the information system of the third invention is an information system according to the first invention, in which the approval device comprises a first terminal and a second terminal, the first terminal comprises a first approval storage unit in which a private key is stored, a first receiving unit that receives request specific information from the second terminal, an approval acquisition unit that uses the private key to sign information including the request specific information and composes the approval information, and an approval transmission unit that transmits the approval information to the information processing device, and the second terminal comprises a second approval storage unit in which request specific information that identifies the request to be approved is stored, an approval receiving unit that receives an approval instruction that is an instruction to approve the request, and a second transmission unit that transmits the request specific information to the first terminal after the approval receiving unit receives the approval instruction.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

The information system of the fourth invention is an information system according to any one of the first to third inventions, in which the information processing device further includes an inquiry sending unit that sends inquiry information to two or more approval devices after the request receiving unit receives the request information, the inquiry information inquiring whether or not to give approval corresponding to the request identified by the request identifier contained in the request information, the approval receiving unit receives the approval information after the inquiry sending unit sends the inquiry information, the approval device further includes an inquiry receiving unit that receives the inquiry information, and the request specific information is information corresponding to the inquiry information.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

The information system of the fifth invention is an information system in which, compared to any one of the first to third inventions, the communication between the information processing device and the request terminal, and the communication between the information processing device and each of two or more approval devices are communications using a closed network.

With this configuration, when approval is given for processing related to tokens in the blockchain that meets predetermined conditions, the processing related to the tokens corresponding to that approval can be carried out more safely.

The information system of the sixth invention is an information system according to any one of the first to fifth inventions, in which the token processing unit performs recovery processing in the event that key information required to use the token is lost.

With this configuration, if approval is given that meets predetermined conditions, recovery processing can be performed appropriately for a user who has lost their key.

The information system of the seventh invention is an information system in which the recovery process is a process of changing a user identifier that identifies a user who is the holder of a token corresponding to key information to another user identifier, as compared to the sixth invention.

With this configuration, if approval is given that meets predetermined conditions, the process of transferring the token of a user who has lost their key to another user can be carried out appropriately.

The information system of the eighth invention is an information system in which, compared to any one of the first to seventh inventions, the information processing device further includes a smart contract storage unit in which smart contract information describing predetermined conditions and the contents of token processing is stored, the approval determination unit determines whether the approval information received by the approval receiving unit satisfies the predetermined conditions described in the smart contract information, and the token processing unit performs token processing based on the contents of token processing described in the smart contract information.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

The information system of the ninth invention is an information system according to any one of the first to eighth inventions, in which the information processing device stores period information relating to the approval period, and the approval determination unit determines whether the approval information corresponding to the period information satisfies a predetermined condition.

With this configuration, when approval within a predetermined period of time satisfies the conditions for processing a token in the blockchain, processing can be performed for the token corresponding to that approval.

The information processing device of the tenth invention is an information processing device that includes a request receiving unit that receives request information having a request identifier that identifies a request for processing related to a token from a request terminal, an approval receiving unit that receives approval information transmitted from each of two or more approval devices, an approval determination unit that acquires request specific information using the request identifier contained in the request information received by the request receiving unit and determines whether the approval information corresponding to the request specific information and received by the approval receiving unit satisfies a predetermined condition, and a token processing unit that performs token processing related to the token, which is processing corresponding to the request identifier, when the approval determination unit determines that the request satisfies the predetermined condition.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

The approval terminal of the eleventh invention is an approval terminal that includes a second approval storage unit in which request specific information is stored that identifies the request to be approved, which is a request for processing related to a token, an approval receiving unit that receives an approval instruction that is an instruction to approve the request, a second receiving unit that receives a private key from the first terminal, an approval acquisition unit that uses the private key to sign information including the request specific information and composes the approval information, and an approval transmitting unit that transmits the approval information to the information processing device.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

The approval terminal of the twelfth invention is an approval terminal that includes a first approval storage unit in which a private key is stored, a first receiving unit that receives request specific information from the second terminal, which is a request for processing related to a token and identifies the request to be approved, an approval acquisition unit that uses the private key to sign information including the request specific information and composes the approval information, and an approval transmission unit that transmits the approval information to an information processing device.

With this configuration, when approval is given for processing related to a token in the blockchain that satisfies predetermined conditions, processing related to the token corresponding to that approval can be performed.

According to the information system of the present invention, when approval is given for processing related to a token in a blockchain that satisfies predetermined conditions, processing related to the token corresponding to the approval can be performed.

Conceptual diagram of information system A in embodiment 1. Block diagram of information system A A block diagram of an information processing device 3 constituting the information system A. A flowchart illustrating an example of the operation of the second terminal 22. A flowchart illustrating an example of the operation of the information processing device 3. The figure shows the request information management table. FIG. 2 is a diagram for explaining the operation outline of the information system A. Conceptual diagram of information system B in embodiment 2 Block diagram of information system B A flowchart illustrating an example of the operation of the first terminal 41. A flowchart illustrating an example of the operation of the second terminal 42. Overview of the computer system according to the above embodiment. Block diagram of the computer system

Embodiments of information systems and the like will be described below with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore may not be described again.

(Embodiment 1)
In this embodiment, an information system is described that includes an information processing device that receives approval information for a request from a request terminal in a blockchain and executes a process corresponding to the request when it is determined that the received two or more pieces of approval information satisfy a predetermined condition. Note that the approval information is information signed by each of two or more approval devices with a private key.
In addition, in this embodiment, the approval device has a first terminal in which the private key is stored, and a second terminal that receives the private key and transmits approval information. That is, in this embodiment, the approval device has two physically separated devices. In addition, it is preferable that the communication between the approval device and the information processing device is communication using a closed network. In addition, the closed network is, for example, an LTE closed network or a VPN. In addition, it is preferable that the process corresponding to the request is a recovery process for a user who has lost a key. In addition, the recovery process is, for example, a process for transferring a token to another user. In addition, it is preferable that the information processing device operates according to a smart contract.

In addition, in this embodiment, an information system is described that includes an information processing device that receives request information sent from a request terminal, then sends inquiry information requesting approval of the request information to one or more second terminals, receives approval information from each of the one or more second terminals, and executes processing corresponding to the request if it is determined that the approval information satisfies a predetermined condition.

In addition, in this embodiment, information regarding the approval period is managed, and an information system having an information processing device that uses approval information received within the approval period to determine whether or not it satisfies predetermined conditions is described.

Figure 1 is a conceptual diagram of an information system A in this embodiment. Information system A includes one or more request terminals 1, one or more approval devices 2, and an information processing device 3. The approval device 2 includes a first terminal 21 and a second terminal 22.

Figure 2 is a block diagram of information system A in this embodiment. Also, Figure 3 is a block diagram of information processing device 3 that constitutes information system A.

The request terminal 1 constituting the information system A includes a terminal storage unit 11, a terminal reception unit 12, a terminal processing unit 13, a terminal transmission unit 14, a terminal reception unit 15, and a terminal output unit 16.

The first terminal 21 includes a first approval storage unit 211, a first processing unit 212, and a first transmission unit 213.

The second terminal 22 includes a second approval storage unit 221, an approval acceptance unit 222, a second receiving unit 223, a second processing unit 224, and an approval transmission unit 225. The second receiving unit 223 includes an inquiry receiving unit 2231. The second processing unit 224 includes an approval acquisition unit 2241.

The information processing device 3 includes a storage unit 31, a receiving unit 32, a processing unit 33, and a transmitting unit 34. The storage unit 31 includes a smart contract storage unit 311. The receiving unit 32 includes a request receiving unit 321 and an approval receiving unit 322. The processing unit 33 includes an approval determination unit 331 and a token processing unit 332. The transmitting unit 34 includes an inquiry sending unit 341.

The terminal storage unit 11 constituting the request terminal 1 stores various types of information. Examples of the various types of information include request information, which will be described later.

The terminal reception unit 12 receives various types of information and instructions. Examples of the various types of information and instructions include request information and transmission instructions.

The request information is information related to a request for processing related to a token. The request information has, for example, a request identifier. The request identifier is information that identifies a request for processing related to a token. The request identifier is, for example, an ID or a character string indicating the content of the request. The request information includes, for example, a first user identifier and a second user identifier. The first user identifier is information that identifies a first user who is the owner of the token. The second user identifier is information that identifies a second user who is a user different from the first user. The first user identifier and the second user identifier are, for example, a user ID, a telephone number, an email address, etc. The first user identifier and the second user identifier are different information.

A transmission instruction is an instruction to transmit request information to the information processing device 3. A transmission instruction usually includes request information. Note that the request information may be transmitted upon receipt of the request information.

Here, acceptance is a concept that includes the acceptance of information entered from input devices such as a keyboard, mouse, or touch panel, the reception of information transmitted via a wired or wireless communication line, and the acceptance of information read from recording media such as optical disks, magnetic disks, and semiconductor memory.

The means for inputting the request information can be anything, such as a touch panel, keyboard, mouse, or menu screen.

The device processing unit 13 performs various types of processing. For example, various types of processing are processing for converting information and instructions accepted by the device accepting unit 12 into a structure for information and instructions to be transmitted. For example, various types of processing are processing for converting information received by the device receiving unit 15 into a data structure for output.

The device transmission unit 14 transmits the request information constructed by the device processing unit 13 to the information processing device 3. It can be said that the request information constructed by the device processing unit 13 is the request information accepted by the device acceptance unit 12.

The terminal receiving unit 15 receives information from the information processing device 3. Such information is, for example, information that the request information has been accepted, and the result of sending the request information. The result of sending the request information is, for example, whether or not the request corresponding to the request information has been approved. The result of sending the request information is, for example, information on the result if approved. Information on the result if approved is, for example, information that the owner of the token has changed, and information on the changed owner of the token.

The terminal output unit 16 outputs various information. The various information is information configured by the device processing unit 13. The various information is, for example, request information, information indicating that the request information has been accepted, the result of sending the request information, etc.

In this case, output is a concept that includes displaying on a display, projecting using a projector, printing on a printer, outputting sound, sending to an external device, storing on a recording medium, and passing on the processing results to other processing devices or other programs, etc.

The approval device 2 includes a first terminal 21 and a second terminal 22. The approval device 2 may be an integrated device having the functions of the first terminal 21 and the second terminal 22. In such a case, communication is not performed between the first terminal 21 and the second terminal 22.

The private key is stored in the first approval storage unit 211 that constitutes the first terminal 21. The process by which the private key is stored is not important.

The first processing unit 212 performs various processes. For example, various processes include reading the private key from the first approval storage unit 211.

The first transmission unit 213 transmits the private key read by the first processing unit 212 to the second terminal 22. The first transmission unit 213 may transmit the private key to the second terminal 22 autonomously, or may transmit the private key to the second terminal 22 in response to receiving an instruction from the second terminal 22. When the first transmission unit 213 autonomously transmits the private key to the second terminal 22, the frequency, time interval, etc. are not important.

The second approval storage unit 221 constituting the second terminal 22 stores various types of information. The various types of information are, for example, an approver identifier, request specific information, and a private key. The approver identifier is information that identifies a user who uses the approval device 2. It may also be said that the approver identifier is information that identifies an approver. The approver identifier may also be considered to be an example of a user identifier.

The storage of the request specific information etc. in the second approval storage unit 221 may be temporary storage. The request specific information in the second approval storage unit 221 is usually information transmitted from the information processing device 3. However, the request specific information in the second approval storage unit 221 may also be information accepted by the approval acceptance unit 222. The route for acquiring the request specific information is not important.

The request specific information is information that specifies the request to be approved. The request here is a request for processing related to a token. The object to be approved is processing related to a token, or the token. The request specific information is, for example, information that corresponds to the inquiry information described below. The request specific information may be a request identifier, information that corresponds to a request identifier, or request information.

The private key in the second approval storage unit 221 is information received from the first terminal 21.

The approval receiving unit 222 receives approval instructions, etc. Approval instructions, etc. include, for example, approval instructions and inquiry instructions.

An approval instruction is an instruction indicating approval of a request. The request here is a request for processing related to a token. An approval instruction for a request may be considered to be the same as an approval instruction for request-specific information. An approval instruction has, for example, a request identifier or request-specific information.

An inquiry instruction is an instruction to inquire whether there is a request requiring approval in the information processing device 3. An inquiry instruction usually has a user identifier that identifies the approver.

The means for inputting approval instructions, etc. may be anything, such as a touch panel, keyboard, mouse, or menu screen. The approval receiving unit 222 may be realized by a device driver for an input means such as a touch panel or keyboard, or control software for a menu screen, etc.

The second receiving unit 223 receives various types of information. Examples of the various types of information include a private key and inquiry information.

The second receiving unit 223 receives the private key from the first terminal 21. This reception is, for example, reception by short-range wireless communication. Examples of short-range wireless communication include Bluetooth (registered trademark) and NFC, but the communication method is not important.

The second receiving unit 223 may receive the private key in response to receiving an approval instruction. The second receiving unit 223 may receive the private key constantly, periodically, or continuously.

The inquiry receiving unit 2231 receives inquiry information. The inquiry receiving unit 2231 receives inquiry information from the information processing device 3. The inquiry information is information for inquiring whether or not to approve the request identified by the request identifier contained in the request information. The inquiry information usually has a request identifier or request specific information.

The communication means of the second receiving unit 223 and the inquiry receiving unit 2231 may be different from each other. For example, the communication of the second receiving unit 223 may be by short-range wireless communication, and the communication of the inquiry receiving unit 2231 may be by a closed network or the Internet.

The second processing unit 224 performs various types of processing. The various types of processing are, for example, processing performed by the approval acquisition unit 2241. The various types of processing are, for example, processing to create a data structure for transmitting instructions and the like accepted by the approval acceptance unit 222. The various types of processing are, for example, processing to create a data structure for outputting information received by the inquiry reception unit 2231. The various types of processing are, for example, processing to read out a user identifier stored in the second approval storage unit 221 and compose an inquiry instruction including the user identifier.

After the approval receiving unit 222 receives an approval instruction, the approval acquisition unit 2241 uses the received private key to sign information including the request specific information, and constructs the approval information. A signature is a so-called digital signature. The signature is a process of encrypting information including the request specific information using a private key, and obtaining the approval information. Note that the signature process is a publicly known technology, so a description thereof will be omitted here.

In addition, "after receiving an approval instruction" may be interpreted as meaning that the approval receiving unit 222 receives an approval instruction. In other words, the approval acquisition unit 2241 may configure the approval information in response to receiving an approval instruction.

Information that includes request-specific information typically includes an approver identifier, but may also include only the request-specific information.

The approval sending unit 225 sends the approval information acquired by the approval acquisition unit 2241 to the information processing device 3. The approval sending unit 225 may also send an inquiry instruction to the information processing device 3. Note that the approval information to be sent is usually encrypted.

The second output unit 226 outputs various information. For example, various information is request-specific information.

In this case, output is a concept that includes displaying on a display, projecting using a projector, printing on a printer, outputting sound, sending to an external device, storing on a recording medium, and passing on the processing results to other processing devices or other programs, etc.

Various types of information are stored in the storage unit 31 constituting the information processing device 3. Examples of the various types of information include smart contract information, key information, request information, period information, points for each user, tokens, and terminal identifiers, which are described below.

The key information is key information for decrypting the approval information. The key information is usually a private key. The key information in the storage unit 31 may correspond to the request information, or may be separate. The key information may be included in the smart contract information.

The period information is information about the approval period. The period information may correspond to the request information, or may be separate. The period information exists, for example, in the smart contract information.

User points are points that are awarded when the approver user approves. In other words, user points are usually used when there is a user-based weighting for approval.

Smart contract information is stored in the smart contract storage unit 311. Smart contract information is information in which a smart contract program is described. Smart contract information is usually a file in which a smart contract program is described. Smart contract information describes, for example, predetermined conditions and the contents of token processing. The predetermined conditions are conditions related to approval. The predetermined conditions are conditions for approval of a request. The predetermined conditions are, for example, conditions related to the strength of approval of a request. The predetermined conditions are, for example, information indicating the minimum number of approvals required for approval of a request, information specifying the ratio of the number of approvals required for approval of a request, and information indicating the minimum approval points required for approval of a request. The approval points are, for example, the sum of points stored in association with each approver. The smart contract information is, for example, associated with an owner identifier that identifies the owner. The owner is a person who has the authority to change the smart contract information. The owner identifier can be an ID, a name, or the like. Corresponding to an owner identifier may mean including an owner identifier, and the data structure of the smart contract information does not matter.

The token here refers to a token in a blockchain. A token is what is known as virtual currency. A token is usually associated with a user identifier. A user identifier is information that identifies the owner of the associated token. Note that the information processing device 3 may or may not manage the token.

The terminal identifier is information that identifies the approval device 2. It may also be said that the terminal identifier is information that identifies the second terminal 22. The terminal identifier may also be information that identifies the approver. Here, the approver may include candidates for approvers.

The receiving unit 32 receives various types of information. Examples of the various types of information include request information, approval information, and inquiry instructions.

The request receiving unit 321 receives request information sent from the request terminal 1. The request information has a request identifier that identifies a request for processing related to the token.

In response to the request receiving unit 321 receiving the request information, the inquiry sending unit 341 may send the inquiry information to two or more approval devices 2. In such a case, the device identifiers of the two or more approval devices 2 to which the inquiry information is sent are stored, for example, in the storage unit 31. The device identifiers of the two or more approval devices 2 to which the inquiry information is sent are included, for example, in the received request information. The device identifier of the approval device 2 may be any information for communicating with the approval device 2, such as the ID, IP address, or email address of the approval device 2.

The approval receiving unit 322 receives approval information transmitted from each of the two or more approval devices 2. The timing at which the approval receiving unit 322 receives the approval information from each of the two or more approval devices 2 does not matter. In addition, in the first embodiment, the transmission from the approval device 2 refers to the transmission from the second terminal 22. In the second embodiment, the transmission from the approval device 2 refers to the transmission from the first terminal 41.

The approval receiving unit 322 receives approval information, for example, after the inquiry sending unit 341 sends inquiry information. Here, receiving approval information after sending may also mean receiving approval information in response to the sending of inquiry information by the inquiry sending unit 341.

The processing unit 33 performs various types of processing. For example, various types of processing are performed by the approval determination unit 331 and the token processing unit 332.

The processing unit 33, for example, pairs the received approval information with the date and time of reception or the date and time of transmission and stores it in the storage unit 31. For example, when approval information is received, the processing unit 33 obtains the date and time from a clock (not shown), associates the date and time with the approval information, and stores it in the storage unit 31. For example, when approval information is received, the processing unit 33 pairs the approval information with the date and time of reception (information indicating the date and time transmitted from the request terminal 1) and stores it in the storage unit 31.

The processing unit 33, for example, composes inquiry information in response to receiving an inquiry instruction. That is, the processing unit 33, for example, obtains a request identifier that identifies a request corresponding to the approver identifier possessed by the inquiry instruction, and composes inquiry information having the request identifier. The processing unit 33 also, for example, obtains a request identifier that identifies a request that has not been approved by the approver identified by the approver identifier possessed by the inquiry instruction, and composes inquiry information having the request identifier.

The approval determination unit 331 uses the approval information received by the approval receiving unit 322 to determine whether or not to approve the request for the request information.

The approval determination unit 331, for example, acquires request specific information using a request identifier contained in the request information received by the request receiving unit 321, and determines whether the approval information corresponding to the request specific information and received by the approval receiving unit 322 satisfies a predetermined condition. The approval receiving unit 322 typically receives two or more pieces of approval information, but there may also be one piece. Needless to say, the approval information corresponding to the request specific information may also be approval information corresponding to the request identifier.

The predetermined conditions are, for example, information indicating the minimum number of approvals required for a request to be approved, information specifying the percentage of approvals required for a request to be approved, and information indicating the minimum approval points required for a request to be approved.

The approval determination unit 331, for example, determines whether one or more pieces of approval information received by the approval receiving unit 322 satisfy predetermined conditions described in the smart contract information.

The approval determination unit 331, for example, determines whether the approval information corresponding to the period information satisfies a predetermined condition. In such a case, the received approval information is stored in the storage unit 31 in a pair with the date and time of reception or the date and time of transmission.

The approval determination unit 331 typically decrypts the approval information using key information (typically a private key) stored in the storage unit 31, and obtains the request specific information from the decrypted information. The approval determination unit 331 then increments, for example, the variable "number of approvals" for the request identifier corresponding to the request specific information by 1. Note that the decrypted information may be the request specific information. Furthermore, the request specific information may be only the request identifier, or may include information other than the request identifier. Note that the initial value of the variable "number of approvals" is "0".

"Whether or not the approval information satisfies a predetermined condition" means, for example, "whether or not two or more pieces of request-specific information obtained from two or more pieces of approval information using the stored key satisfy a predetermined condition."

When the approval determination unit 331 determines that the predetermined conditions are met, the token processing unit 332 performs token processing corresponding to the request identifier. Token processing is processing related to tokens.

The token processing is preferably a process that uses blockchain technology to broadcast the transaction that has occurred to a blockchain platform.

Token processing is, for example, recovery processing. Recovery processing does not usually include processing in token transactions. Recovery processing is, for example, token transfer processing, key information notification processing, key information change processing, owner change processing, token lock processing, lock release processing, and fee change processing.

The token transfer process is a process of transferring the token of a user who has lost key information to another user. The token transfer process is, for example, a process of changing the user identifier that identifies the user who is the holder of the token corresponding to the key information to another user identifier. The token transfer process is, for example, a process of rewriting the user identifier associated with the token to another user identifier. Also, the token transfer process is, for example, a process of instructing a token management device (not shown) to rewrite the user identifier associated with a specific token to another user identifier.

The key information notification process is a process for notifying a user of key information that corresponds to a specific token and is necessary when using the token. The notification process may involve sending the key information using a communication means, printing mail with the key information printed on it, etc. The key information is usually stored in the storage unit 31 or an external device (not shown) in association with the token or user identifier.

The key information change process is, for example, a process of rewriting the key information corresponding to a specific token with new key information and notifying the user of the new key information.

The owner change process is a process that changes the owner identifier that is managed in accordance with the smart contract information.

The token lock process is a process that makes it impossible to perform processes on a token, such as transferring or deleting the token. The token lock process is, for example, a process of storing a flag indicating that the token is locked in association with the token. The token lock process is, for example, a process of deleting the "write" authority in the processing authority for the token.

The unlock process is a process for unlocking a token that has been locked by the token lock process. Examples of the unlock process include a process for deleting a flag indicating that the token is locked, a process for adding a flag indicating that the token is not locked, and a process for adding "write" authority to the processing authority for the token.

The fee change process is a process that changes the fee information that specifies the fee for processing a token. The fee information may be associated with a token or with a user. Examples of fee information include "X%" or "100 yen."

As described above, it is preferable for the token processing unit 332 to perform recovery processing in the event that key information required to use the token is lost.

The token processing unit 332 performs token processing, for example, based on the contents of token processing described in the smart contract information.

The transmission unit 34 transmits various types of information. Examples of various types of information include information indicating that request information has been received, information indicating that approval information has been received, and inquiry information.

After the request receiving unit 321 receives the request information, the inquiry sending unit 341 sends inquiry information to two or more approval devices 2 inquiring whether or not to approve the request identified by the request identifier contained in the request information. The inquiry sending unit 341 sends the inquiry information to the approval device 2 identified by the terminal identifier stored in the storage unit 31. Note that the transmission to the approval device 2 here is a transmission to the second terminal 22.

The inquiry sending unit 341 may send inquiry information in response to receiving an inquiry instruction. Note that the inquiry information is information configured by the processing unit 33. The inquiry information has a request identifier.

The terminal storage unit 11, the first approval storage unit 211, the second approval storage unit 221, the storage unit 31, and the smart contract storage unit 311 are preferably non-volatile recording media, but can also be realized using volatile recording media.

The process by which information is stored in the terminal storage unit 11, etc. is not important. For example, information may be stored in the terminal storage unit 11, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the terminal storage unit 11, etc., or information inputted via an input device may be stored in the terminal storage unit 11, etc.

The terminal reception unit 12 and the approval reception unit 222 can be realized by device drivers for input means such as a touch panel or keyboard, control software for a menu screen, etc.

The terminal processing unit 13, the first processing unit 212, the second processing unit 224, the approval acquisition unit 2241, the processing unit 33, the approval determination unit 331, and the token processing unit 332 can usually be realized by an MPU, memory, etc. The processing procedure of the terminal processing unit 13 is usually realized by software, and the software is recorded on a recording medium such as a ROM. However, it may also be realized by hardware (dedicated circuitry).

The terminal transmission unit 14, the first transmission unit 213, the approval transmission unit 225, the transmission unit 34, and the inquiry transmission unit 341 are typically realized by wireless or wired communication means, but may also be realized by broadcasting means.

The terminal receiving unit 15, the second receiving unit 223, the inquiry receiving unit 2231, the receiving unit 32, the request receiving unit 321, and the approval receiving unit 322 are typically realized by wireless or wired communication means, but may also be realized by means of receiving broadcasts.

The terminal output unit 16 may or may not include an output device such as a display or speaker. The terminal output unit 16 may be realized by driver software for an output device, or by a combination of driver software for an output device and an output device, etc.

Next, an example of the operation of information system A will be described. First, an example of the operation of request terminal 1 will be described.

The terminal reception unit 12 of the request terminal 1 receives request information from a user. Next, the terminal processing unit 13 converts the request information received by the terminal reception unit 12 into request information with a data structure to be transmitted. The terminal transmission unit 14 transmits the request information constructed by the device processing unit 13 to the information processing device 3.

In response to the transmission of the request information, the terminal receiving unit 15 receives information from the information processing device 3 indicating that the request information has been accepted. The terminal processing unit 13 converts the information received by the terminal receiving unit 15 into data with a structure to be output. The terminal output unit 16 outputs information indicating that the request information has been accepted.

Next, an example of the operation of the first terminal 21 will be described. The first processing unit 212 of the first terminal 21 reads out the private key from the first approval storage unit 211. Next, the first transmission unit 213 transmits the private key read out by the first processing unit 212 to the second terminal 22.

Next, an example of the operation of the second terminal 22 will be described using the flowchart in FIG.

(Step S401) The approval reception unit 222 determines whether or not an inquiry instruction has been received. If an inquiry instruction has been received, the process proceeds to step S402; if an inquiry instruction has not been received, the process proceeds to step S406.

(Step S402) The second processing unit 224 reads out the approver identifier stored in the second approval storage unit 221. The second processing unit 224 also composes an inquiry instruction that includes the approver identifier. The approval transmission unit 225 transmits the inquiry instruction to the information processing device 3.

(Step S403) In response to the transmission of the inquiry instruction, the inquiry receiving unit 2231 determines whether or not inquiry information has been received. If inquiry information has been received, the process proceeds to step S404; if inquiry information has not been received, the process returns to step S403.

(Step S404) The second processing unit 224 acquires the request specific information contained in the inquiry information received in step S403. The second processing unit 224 then temporarily stores the request specific information in at least the second approval storage unit 221.

(Step S405) The second output unit 226 outputs the request specific information acquired in step S404. Return to step S401.

(Step S406) The second receiving unit 223 determines whether or not a private key has been received from the first terminal 21. If a private key has been received, the process proceeds to step S407; if not, the process proceeds to step S408.

(Step S407) The second processing unit 224 temporarily stores the private key received in step S406 in the second approval storage unit 221. Return to step S401.

(Step S408) The approval receiving unit 222 determines whether or not the approval instruction input by the approver has been accepted. If the approval instruction has been accepted, the process proceeds to step S409. If the approval instruction has not been accepted, the process returns to step S401. Note that the approver normally checks the output request specific information and then inputs the approval instruction.

(Step S409) The approval acquisition unit 2241 acquires the private key and the approver identifier from the second approval storage unit 221. The approval acquisition unit 2241 also acquires the request identifier contained in the output request specific information.

(Step S410) The approval acquisition unit 2241 uses the private key acquired in step S409 to sign the information including the request identifier or request specific information and the approver identifier, thereby constructing approval information.

(Step S411) The approval sending unit 225 sends the approval information acquired in step S410 to the information processing device 3. Return to step S401.

In the flowchart of FIG. 4, the inquiry information may be received from the information processing device 3 by push-type communication.

In the flowchart in Figure 4, processing ends when the power is turned off or an interrupt occurs to end processing.

Next, an example of the operation of the information processing device 3 will be described using the flowchart in FIG.

(Step S501) The request receiving unit 321 determines whether or not request information sent from the request terminal 1 has been received. If request information has been received, the process proceeds to step S502; if request information has not been received, the process proceeds to step S505.

(Step S502) The processing unit 33 acquires a request identifier. Note that the method for acquiring the request identifier is not important. The processing unit 33 acquires the request identifier, for example, from the request information received in step S501. The processing unit 33 generates, for example, a unique request identifier. Note that the algorithm for generating the request identifier is not important. The algorithm for generating the request identifier is, for example, a process of adding "1" to the latest request identifier.

The request identifier included in the request information received in step S501 may be different from the request identifier acquired in step S502. The request information received in step S501 may not have a request identifier.

(Step S503) The processing unit 33 constructs request specific information using the request information received in step S501. It is preferable that the request specific information has the request identifier acquired in step S502. In addition, the request specific information may be associated with the request identifier.

(Step S504) The processing unit 33 stores the request specific information constructed in step S503 in the storage unit 31. Return to step S501.

(Step S505) The receiving unit 32 determines whether or not an inquiry instruction has been received from the second terminal 22. If an inquiry instruction has been received, the process proceeds to step S506; if an inquiry instruction has not been received, the process proceeds to step S508.

(Step S506) The processing unit 33 acquires request specific information corresponding to the inquiry instruction received in step S505 from the storage unit 31. Then, the processing unit 33 constructs inquiry information having the request specific information.

The request specific information corresponding to the inquiry instruction is, for example, the request specific information corresponding to the approver identifier contained in the inquiry instruction. Also, the request specific information corresponding to the inquiry instruction is, for example, one or more pieces of request specific information stored in the storage unit 31.

(Step S507) The transmission unit 34 transmits the inquiry information acquired in step S506 to the second terminal 22 that transmitted the inquiry instruction. Return to step S501.

(Step S508) The approval receiving unit 322 determines whether approval information has been received. If approval information has been received, the process proceeds to step S509. If approval information has not been received, the process proceeds to step S510. Note that it is preferable that the approval information be associated with an approver identifier that identifies the approver, who is the user of the second terminal 22.

(Step S509) The processing unit 33 stores the approval information received in step S508 in the storage unit 31. Return to step S501.

The processing unit 33 typically stores the approval information in the storage unit 31 in association with the approver identifier. The processing unit 33 typically stores the approval information in the storage unit 31 in association with the request information.

In addition, here, the processing unit 33 may use the key information to decrypt the approval information received in step S508, obtain the decrypted approval information, and store it in the storage unit 31.

(Step S510) The approval judgment unit 331 judges whether or not to make an approval judgment. If an approval judgment is to be made, proceed to step S511, and if an approval judgment is not to be made, return to step S501. Note that the approval judgment unit 331 judges to make an approval judgment, for example, each time approval information is received. Also, the approval judgment unit 331 judges to make an approval judgment, for example, when a predetermined period of time has elapsed since request information was received. Also, the approval judgment unit 331 judges to make an approval judgment, for example, when a period indicated by period information has elapsed since request information was received. Also, the approval judgment unit 331 judges to make an approval judgment, for example, periodically.

(Step S511) The approval decision unit 331 assigns 1 to counter i.

(Step S512) The approval determination unit 331 determines whether or not the i-th approval information for the request information to be approved is stored in the storage unit 31. If the i-th approval information is stored, the process proceeds to step S513, and if the i-th approval information is not stored, the process proceeds to step S517.

(Step S513) The approval determination unit 331 uses the private key included in the smart contract information in the smart contract storage unit 331 to decrypt the i-th approval information stored in the storage unit 31, and obtains the decrypted approval information.

(Step S514) The approval determination unit 331 determines whether the approval information acquired in step S513 is valid. If the information is valid, the process proceeds to step S515. If the information is invalid, the process proceeds to step S516.

(Step S515) The approval determination unit 331 adds 1 to the variable "approval count". Note that the initial value of the variable "approval count" is "0".

(Step S516) The approval decision unit 331 increments the counter i by 1. Return to step S512.

(Step S517) The approval judgment unit 331 judges whether or not the value of the variable "number of approvals" satisfies a predetermined condition. If the predetermined condition is satisfied, the process proceeds to step S518, and if the predetermined condition is not satisfied, the process returns to step S501. Note that the predetermined condition is, for example, that the value of the variable "number of approvals" is equal to or greater than a threshold value, and that "value of the variable "number of approvals" / total number of approvers" (proportion of approvers) is equal to or greater than a threshold value. The total number of approvers is stored, for example, in the storage unit 31.

(Step S518) The token processing unit 332 performs token processing corresponding to the request information. Return to step S501.

In the flowchart in Figure 5, processing ends when the power is turned off or an interrupt occurs to end processing.

The specific operation of information system A in this embodiment will be described below. A conceptual diagram of information system A is shown in FIG. 1. In this specific example, the communication between the request terminal 1 and the information processing device 3, and the communication between the approval device 2 and the information processing device 3 are communications using an LTE closed network. Also, in this specific example, the token processing is a token transfer processing.

Now, assume that the request information management table shown in FIG. 6 is stored in the storage unit 31. The request information management table is a table that manages requests. The request information management table can also be said to be a table that manages request-specific information.

The request information management table stores records having "ID", "request identifier", "user identifier", "other user identifier", "date and time information", "approval information", "approval yes/no", and "flag". "ID" is information for identifying a record. "Request identifier" is information for identifying a request, and is a character string consisting of "R" and a number. "User identifier" is the identifier of the original user who transfers the token. In other words, "user identifier" is the identifier of the user who holds the token before the transfer. "Other user identifier" is the identifier of the user to whom the token is transferred. In other words, "other user identifier" is the identifier of the user who holds the token after the transfer. "Date and time information" is the date on which the request information was received. "Approval information" is the identifier of the approver who approved the request. "Approval yes/no" is the result of the decision made by the approval decision unit 331 ("OK" or "NG"). "Flag" is information indicating whether the approval decision has been completed (value is "1") or not (value is "0").

The storage unit 31 also stores the deadline information "10 days." The deadline information "10 days" indicates that the approval decision unit 331 will decide whether to approve the request based on the approval information received within 10 days of receiving the request information.

The smart contract information in the smart contract storage unit 311 includes a predetermined condition: "Approval from all three approvers must be obtained" and a token process: "A process to rewrite the user identifier in the token that is paired with the user identifier contained in the request information to another user identifier."

The description of this process is, for example, "token = search (user identifier); rewrite (token.user identifier, other user identifier)." Note that "token = search (user identifier)" is a function that searches for a token that pairs with a user identifier. "rewrite (token.user identifier, other user identifier)" is a function that rewrites the user identifier that pairs with the searched token to another user identifier.

In this situation, it is assumed that the user of the request terminal 1 inputs request information having a user identifier "U512" and another user identifier "U908" into the request terminal 1. This request information is information indicating a request to perform a process to transfer tokens held by the user identified by the user identifier "U512" to the user identified by the other user identifier "U908".

Next, the terminal reception unit 12 of the request terminal 1 receives the request information. Next, the terminal processing unit 13 converts the request information received by the terminal reception unit 12 into request information with a data structure to be transmitted (for example, "Request U512, U908"). The terminal transmission unit 14 transmits the request information "Request U512, U908" constructed by the terminal processing unit 13 to the information processing device 3 via the LTE closed network.

Next, the request receiving unit 321 of the information processing device 3 receives the request information "Request U512, U908" sent from the request terminal 1. Next, the processing unit 33 obtains a new request identifier "R128". Note that the maximum value of the numerical portion of the request identifiers that exist up until now is "127", and the processing unit 33 adds "1" to this "127" to obtain "R128".

Next, the processing unit 33 uses the received request information, the acquired request identifier "R128", the initial value of the flag "0", etc. to construct the request specific information "Request identifier = R128, User identifier = U512, Other user identifier = U908, Date and time information = 2020/4/22, Flag = 0". It is assumed that the processing unit 33 has acquired "Date and time information = 2020/4/22" from a clock (not shown). It is to be noted that the date and time information here is a date, but may also include a time.

Next, the processing unit 33 stores the constructed request specific information in the request information management table of FIG. 6. Note that this record is the record with "ID=128". Also, at this stage, since approval from the approver has not been received, the attribute values of "approval information" and "approval possible" are NULL.

Let us also assume that approver A inputs an inquiry command into his/her first terminal 21 to inquire whether there are any requests that he/she needs to approve.

Then, the approval receiving unit 222 of the first terminal 21 receives the inquiry instruction. Next, the second processing unit 224 reads out the approver identifier "M01" stored in the second approval storage unit 221. The second processing unit 224 also composes an inquiry instruction "Inquiry M01" that includes the approver identifier. The approval sending unit 225 sends the inquiry instruction "Inquiry M01" to the information processing device 3.

Next, the receiving unit 32 of the information processing device 3 receives an inquiry instruction from the second terminal 22. The processing unit 33 then obtains from FIG. 6 the request specific information for "ID=128" that is paired with date and time information that does not exceed the deadline information of "10 days" from today, has a flag of "0" (approval decision has not been made), and has an approver identifier "M01" of the received inquiry instruction "Inquiry M01" that does not exist in the approval information. The obtained request specific information is "request identifier=R128, user identifier=U512, other user identifier=U908, flag=0".

Next, the sending unit 34 sends the inquiry information, which includes the request specific information "request identifier = R128, user identifier = U512, other user identifier = U908, flag = 0", to the second terminal 22 of approver A who sent the inquiry instruction.

Next, in response to the transmission of an inquiry instruction by the second terminal 22 of the approver A, the inquiry receiving unit 2231 of the second terminal 22 receives the inquiry information. Next, the second processing unit 224 acquires the request specific information contained in the received inquiry information. Then, the second processing unit 224 temporarily stores the request specific information in at least the second approval storage unit 221. In addition, the second output unit 226 outputs the acquired request specific information.

Let us say that approver A looks at the output request specific information and inputs an approval instruction to approve the request into the second terminal 22.

Next, the approval receiving unit 222 of the second terminal 22 receives the approval instruction. The approval acquisition unit 2241 reads out the private key stored in the second approval storage unit 221. Note that this private key is information received by the second receiving unit 223 from the first terminal 21.

Next, the approval acquisition unit 2241 reads the approver identifier "M01" from the second approval storage unit 221, and performs a signature process using the private key on the information having the approver identifier "M01" and the request specific information including "request identifier = R128, user identifier = U512, other user identifier = U908," thereby constructing approval information. Then, the approval transmission unit 225 transmits the acquired approval information to the information processing device 3.

Next, the approval receiving unit 322 of the information processing device 3 receives the approval information from the second terminal 22 via the LTE closed network.

Next, the processing unit 33 stores the received approval information in the storage unit 31. Note that here, the processing unit 33 may decrypt the received approval information using the private key of the storage unit 31, and store the decrypted approval information in the storage unit 31. In addition, the stored approval information is associated with "request identifier=R128".

Let us assume that the above process was performed not only by approver A, but also by approver B identified by approver identifier "M02" and approver C identified by approver identifier "M03". In other words, let us assume that the approval information of approver A, approver B, and approver C are stored in the storage unit 31 in association with the request identifier "R128".

The approval decision unit 331 also determines that it is time to make an approval decision for the request identified by the request identifier "R128".

For example, the approval determination unit 331 decrypts the approval information of approver A that is paired with the request identifier "R128" using the private key of the storage unit, and obtains the approval information including "M01". The approval determination unit 331 also adds the approver identifier "M01" to FIG. 6 as approval information that is paired with the request identifier "R128". Similarly, the approval determination unit 331 adds each of the approver identifiers "M02" and "M03" to FIG. 6 as approval information that is paired with the request identifier "R128". As a result, the approval information "M01, M02, M03" is stored in pairs with the request identifier "R128".

The approval determination unit 331 also determines that the approval information "M01, M02, M03" satisfies the predetermined condition "approval by all three approvers is obtained." The approval determination unit 331 then records the attribute value "approval possible or not = OK, flag = 1" in the request information management table of FIG. 6, pairing it with the request identifier "R128."

Next, the token processing unit 332 performs token processing corresponding to the request information. That is, the token processing unit 332 executes "token = search (U512); rewrite (token.U512,U908)" and performs a transfer process to transfer the token of the user identified by U512 to the token of another user identified by U908.

The operation of information system A will be outlined with reference to FIG. 7. In FIG. 7, the request terminal 1 and one or more sets of the first terminal 21 and the second terminal 22 logically belong to an issuer office. The issuer office is a logical office related to the emission of tokens.

In addition, each terminal in the issuer's office and the information processing device 3 communicate via an LTE closed network.

Then, request information regarding a request for processing related to the token is transmitted from the request terminal 1 to the information processing device 3 via the LTE closed network via a remote connection (701).

When the information processing device 3 receives the request information, an unsigned transaction (unapproved request specific information (e.g., the record with "ID=128" in FIG. 6) is stored in the transaction DB (702).

Next, when approver A inputs an inquiry instruction to the second terminal 22, the second terminal 22 transmits an instruction to verify the unsigned transaction to the information processing device 3 via the LTE closed network (703). Then, the unsigned transaction (unapproved request-specific information) is transmitted from the information processing device 3 to the second terminal 22 via the LTE closed network.

The second terminal 22 then receives and outputs the unsigned transaction.

Then, when approver A, who has confirmed the unsigned transaction, inputs an approval instruction to the second terminal 22, the second terminal 22 performs a signature using the private key received from the first terminal 21, and the encrypted approval information is transmitted from the second terminal 22 to the information processing device 3 via the LTE closed network (704).

Next, the information processing device 3 receives the approval information from the approver A, decrypts the approval information using the stored private key (705), and stores the decrypted approval information.

For example, if approver B also performs the same operation as approver A on his/her second terminal 22, the information processing device 3 etc. similarly stores the decrypted approval information from approver B.

When strong approval that satisfies a predetermined condition is obtained for a piece of request specific information, the information processing device 3 determines that approval has been obtained for the request corresponding to the piece of request specific information, and performs token processing corresponding to the piece of request specific information. In addition, the information processing device 3 broadcasts the transaction that occurs as a result of the token processing to the blockchain platform (706) (707).

For example, when a request to issue a token is input from the request terminal 1, the request is sent to the information processing device 3, and the information processing device 3 performs the process of issuing the token, and the process (transaction) of issuing the token is broadcast (707) to the blockchain platform (706).

In FIG. 7, the first terminal 21 and the second terminal 22 belong to a single logical organization, but it goes without saying that the first terminal 21 and the second terminal 22 may belong to different organizations or may be located in separate locations.

As described above, according to this embodiment, when approval is given for processing related to a token in a blockchain that satisfies predetermined conditions, processing related to the token corresponding to the approval can be performed.

Furthermore, according to this embodiment, when approval is given that satisfies predetermined conditions, recovery processing can be appropriately performed for a user who has lost their key.

Furthermore, according to this embodiment, when approval is given that satisfies predetermined conditions, the process of transferring the token of a user who has lost their key to another user can be carried out appropriately.

The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to the other embodiments in this specification.

The software for realizing the second terminal 22 in this embodiment is the following program. In other words, this program is a program for causing a computer that can access a second approval storage unit in which request specific information that specifies a request to be approved, which is a request for processing related to a token, to function as an approval receiving unit that receives an approval instruction that is an instruction to approve the request, a second receiving unit that receives a private key from the first terminal, an approval obtaining unit that uses the private key to sign information including the request specific information and composes approval information, and an approval transmitting unit that transmits the approval information to an information processing device.

The software for realizing the information processing device 3 in this embodiment is the following program. That is, this program causes a computer to function as a request receiving unit that receives request information having a request identifier that identifies a request for processing related to a token from a request terminal, an approval receiving unit that receives approval information transmitted from two or more approval devices, an approval determination unit that acquires request specific information using the request identifier contained in the request information received by the request receiving unit and determines whether the approval information corresponding to the request specific information and received by the approval receiving unit satisfies a predetermined condition, and a token processing unit that performs token processing related to the token, which is processing corresponding to the request identifier, when the approval determination unit determines that the predetermined condition is satisfied.

(Embodiment 2)
The present embodiment differs from the first embodiment in that communication with the information processing device 3 is performed by the first terminal, not the second terminal.

Figure 8 is a conceptual diagram of information system B in this embodiment. Information system B includes one or more request terminals 1, one or more approval devices 4, and an information processing device 3.

Figure 9 is a block diagram of information system B in this embodiment. The approval device 4 constituting information system B includes a first terminal 41 and a second terminal 42.

The first terminal 41 includes a first approval storage unit 211, a first receiving unit 411, a first processing unit 412, and an approval sending unit 225. The first processing unit 412 includes an approval acquisition unit 2241.

The second terminal 42 includes a second approval storage unit 221, an approval receiving unit 222, and a second transmitting unit 421.

The first receiving unit 411 constituting the first terminal 41 receives various information instructions from the second terminal 42 or the information processing device 3. The first receiving unit 411 receives, for example, an inquiry instruction from the second terminal 42. The first receiving unit 411 receives, for example, request specification information from the second terminal 42. The request specification information is information that specifies the request to be approved. The request is a request for processing related to a token. The first receiving unit 411 receives, for example, inquiry information from the information processing device 3.

The first receiving unit 411 is typically implemented as a wireless or wired communication means, but may also be implemented as a means for receiving broadcasts.

The first processing unit 412 performs various types of processing. For example, various types of processing are processing performed by the approval acquisition unit 2241.

The first processing unit 412 can usually be realized by an MPU, memory, etc. The processing procedure of the first processing unit 412 is usually realized by software, and the software is recorded on a recording medium such as a ROM. However, it may also be realized by hardware (dedicated circuitry).

The second transmission unit 421 constituting the second terminal 42 transmits the request specific information to the first terminal 41 after the approval receiving unit 222 receives the approval instruction.

The second transmitting unit 421 is typically implemented using a wireless or wired communication means, but may also be implemented using a broadcasting means.

Next, an example of the operation of information system B will be described. First, an example of the operation of first terminal 41 will be described using the flowchart in FIG. 10.

(Step S1001) The first receiving unit 411 determines whether or not an inquiry instruction has been received from the second terminal 42. If an inquiry instruction has been received, the process proceeds to step S1002; if an inquiry instruction has not been received, the process proceeds to step S1005.

(Step S1002) The first processing unit 412 reads out the approver identifier stored in the first approval storage unit 211. The first processing unit 412 also constructs an inquiry instruction that includes the approver identifier. The approval transmission unit 225 transmits the inquiry instruction to the information processing device 3.

(Step S1003) The first receiving unit 411 determines whether or not inquiry information has been received from the information processing device 3. If inquiry information has been received, the process proceeds to step S1006; if inquiry information has not been received, the process returns to step S1003.

(Step S1004) The approval sending unit 225 sends the inquiry information received in step S1003 to the second terminal 42. Return to step S1001.

(Step S1005) The first receiving unit 411 determines whether or not request specific information has been received from the second terminal 42. If request specific information has been received, the process proceeds to step S1006; if request specific information has not been received, the process returns to step S1001.

(Step S1006) The approval acquisition unit 2241 acquires the private key and the approver identifier from the first approval storage unit 211. The approval acquisition unit 2241 also acquires the request identifier contained in the request specific information received in step S1005.

(Step S1007) The approval acquisition unit 2241 uses the private key acquired in step S1006 to sign the information including the request identifier or request specific information and the approver identifier, thereby constructing approval information.

(Step S1008) The approval sending unit 225 sends the approval information acquired in step S1007 to the information processing device 3. Return to step S1001.

In the flowchart in Figure 10, processing ends when the power is turned off or an interrupt occurs to end processing.

Next, an example of the operation of the second terminal 42 will be explained using the flowchart in FIG. 11.

(Step S1101) The approval reception unit 222 determines whether or not an inquiry instruction has been received. If an inquiry instruction has been received, the process proceeds to step S1102; if an inquiry instruction has not been received, the process proceeds to step S1106.

(Step S1102) The second processing unit 224 constructs a query instruction for the data structure to be sent. The second transmission unit 421 sends the query instruction to the first terminal 41.

(Step S1103) In response to the transmission of the inquiry instruction, the inquiry receiving unit 2231 determines whether or not inquiry information has been received from the first terminal 41. If inquiry information has been received, the process proceeds to step S1104; if inquiry information has not been received, the process returns to step S1103.

(Step S1104) The second processing unit 224 acquires the request specific information contained in the inquiry information received in step S1103. The second processing unit 224 then temporarily stores the request specific information in at least the second approval storage unit 221.

(Step S1105) The second output unit 226 outputs the request specific information acquired in step S1104. Return to step S1101.

(Step S1106) The approval receiving unit 222 determines whether an approval instruction has been received. If an approval instruction has been received, the process proceeds to step S1107; if an approval instruction has not been received, the process returns to step S1101.

(Step S1107) The second terminal 42 configures request specific information in response to receiving the approval instruction in step S1106.

(Step S1108) The second transmission unit 421 transmits the request specific information constructed in step S1107 to the first terminal 41. Return to step S1101.

In the flowchart in Figure 11, processing ends when the power is turned off or an interrupt occurs to end processing.

As described above, according to this embodiment, when approval is given for processing related to a token in a blockchain that satisfies predetermined conditions, processing related to the token corresponding to the approval can be performed.

Furthermore, according to this embodiment, when approval is given that satisfies predetermined conditions, recovery processing can be appropriately performed for a user who has lost their key.

Furthermore, according to this embodiment, when approval is given that satisfies predetermined conditions, the process of transferring the token of a user who has lost their key to another user can be carried out appropriately.

The software that realizes the first terminal 41 in this embodiment is the following program. In other words, this program causes a computer that can access a first approval storage unit in which a private key is stored to function as a first receiving unit that receives request specific information from a second terminal, which is a request for processing related to a token and identifies the request to be approved, an approval acquiring unit that uses the private key to sign information including the request specific information and composes approval information, and an approval transmitting unit that transmits the approval information to an information processing device.

FIG. 12 shows the appearance of a computer that executes the programs described in this specification to realize the information systems and the like of the various embodiments described above. The above-mentioned embodiments can be realized by computer hardware and computer programs executed thereon. FIG. 12 is an overview of this computer system 300, and FIG. 13 is a block diagram of system 300.

In FIG. 12, computer system 300 includes computer 301, which includes a CD-ROM drive, keyboard 302, mouse 303, and monitor 304.

In FIG. 13, in addition to a CD-ROM drive 3012, computer 301 includes an MPU 3013, a bus 3014 connected to the CD-ROM drive 3012 etc., a ROM 3015 for storing programs such as a boot-up program, a RAM 3016 connected to the MPU 3013 for temporarily storing instructions for application programs and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card that provides connection to a LAN.

The program that causes computer system 300 to execute the functions of the information system of the above-mentioned embodiment may be stored on CD-ROM 3101, inserted into CD-ROM drive 3012, and then transferred to hard disk 3017. Alternatively, the program may be sent to computer 301 via a network (not shown) and stored on hard disk 3017. The program is loaded into RAM 3016 when executed. The program may be loaded directly from CD-ROM 3101 or the network.

The program does not necessarily have to include an operating system (OS) or third-party programs that cause computer 301 to execute functions such as the information system of the above-described embodiment. The program only needs to include instructions that call appropriate functions (modules) in a controlled manner to obtain the desired results. How computer system 300 operates is well known, and a detailed description will be omitted.

In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmission step (processing that is performed only by hardware).

The computer that executes the above program may be a single computer or multiple computers. In other words, it may perform centralized processing or distributed processing.

Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be realized physically by one medium.

In addition, in each of the above embodiments, each process may be realized by centralized processing by a single device, or may be realized by distributed processing by multiple devices.

The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these are also included within the scope of the present invention.

As described above, the information system of the present invention has the effect of being able to perform processing related to a token in a blockchain when approval that satisfies predetermined conditions is given for the processing related to the token, and is useful as a server device, etc. in the blockchain.

LIST OF SYMBOLS 1 Request terminal 2, 4 Approval device 3 Information processing device 11 Terminal storage unit 12 Terminal reception unit 13 Terminal processing unit 14 Terminal transmission unit 15 Terminal reception unit 16 Terminal output unit 21, 41 First terminal 22, 42 Second terminal 31 Storage unit 32 Reception unit 33 Processing unit 34 Transmission unit 211 First approval storage unit 212, 412 First processing unit 213 First transmission unit 221 Second approval storage unit 222 Approval reception unit 223 Second reception unit 224 Second processing unit 225 Approval transmission unit 226 Second output unit 311 Smart contract storage unit 321 Request reception unit 322 Approval reception unit 331 Approval determination unit 332 Token processing unit 341 Inquiry transmission unit 411 First reception unit 421 Second transmission unit 2231 Inquiry receiving unit 2241 Approval acquisition unit

Claims (12)

An information system comprising: two or more approval devices that transmit approval information indicating approval of a request for processing related to a token ; and an information processing device that receives request information from a request terminal that transmits request information having a request identifier that identifies the request ;
The approval device includes:
a first authorization storage unit in which a private key is stored;
a second approval storage unit in which request specification information for specifying a request to be approved is stored;
an approval receiving unit that receives an approval instruction which is an instruction for approving the request;
an approval acquisition unit that, after the approval acceptance unit accepts the approval instruction, signs information including the request specific information using the private key to configure approval information;
an approval transmitting unit that transmits the approval information to the information processing device;
The information processing device includes:
a request receiving unit that receives the request information transmitted from the request terminal;
an approval receiving unit that receives the approval information transmitted from each of the two or more approval devices;
an approval determination unit that acquires request specifying information by using a request identifier included in the request information received by the request receiving unit, and determines whether the approval information corresponding to the request specifying information and received by the approval receiving unit satisfies a predetermined condition;
a token processing unit that performs a token process related to the token , the token processing being a process corresponding to the request identifier when the approval determination unit determines that the predetermined condition is satisfied,
The predetermined condition is:
the number of approvals indicated by the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval ratio based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval points based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value,
The approval points are a sum of points stored in association with each approver for the approval device that has transmitted approval information indicating approval . The approval device includes a first terminal and a second terminal,
The first terminal,
a first authorization storage unit in which a private key is stored;
a first transmission unit that transmits the private key to the second terminal;
The second terminal,
a second approval storage unit in which request specification information for specifying a request to be approved is stored;
an approval receiving unit that receives an approval instruction which is an instruction for approving the request;
a second receiving unit that receives the private key from the first terminal;
an approval acquisition unit that uses the private key to sign information including the request specifying information and configures approval information;
2. The information system according to claim 1, further comprising an approval transmitting unit for transmitting the approval information to the information processing device. The approval device includes a first terminal and a second terminal,
The first terminal,
a first authorization storage unit in which the private key is stored;
a first receiving unit that receives the request specifying information from the second terminal;
an approval acquisition unit that uses the private key to sign information including the request specifying information and configures approval information;
an approval transmitting unit that transmits the approval information to the information processing device;
The second terminal,
a second approval storage unit in which request specification information for specifying a request to be approved is stored;
an approval receiving unit that receives an approval instruction which is an instruction for approving the request;
2. The information system according to claim 1, further comprising: a second transmitting unit configured to transmit the request specific information to the first terminal after the approval receiving unit has received the approval instruction. The information processing device includes:
The method further includes a query sending unit that sends query information to the two or more approval devices after the request receiving unit receives the request information, the query information inquiring whether or not to approve a request identified by a request identifier included in the request information,
The approval receiving unit is
receiving the approval information after the inquiry transmission unit transmits the inquiry information;
The approval device includes:
Further comprising an inquiry receiving unit that receives the inquiry information,
The information system according to claim 1 , wherein the request specific information is information corresponding to the inquiry information. The information system according to any one of claims 1 to 3, wherein the communication between the information processing device and the request terminal, and the communication between the information processing device and each of the two or more approval devices are communications using a closed network. The token processing unit:
6. The information system according to claim 1, further comprising a recovery process for recovering a lost key information required for using the token. The recovery process includes:
7. The information system according to claim 6, further comprising a process for changing a user identifier that identifies a user who is a holder of a token corresponding to the key information to another user identifier. The information processing device includes:
Further comprising a smart contract storage unit in which smart contract information describing the predetermined conditions and the contents of the token processing is stored,
The approval determination unit is
determining whether the approval information received by the approval receiving unit satisfies the predetermined condition described in the smart contract information;
The token processing unit:
The information system according to claim 1 , wherein the token processing is performed based on the content of the token processing described in the smart contract information. The information processing device stores period information relating to an approval period,
The approval determination unit is
The information system according to claim 1 , further comprising: determining whether or not the approval information corresponding to the period information satisfies a predetermined condition. a request receiving unit that receives request information having a request identifier that identifies a request for processing related to the token from a request terminal;
an approval receiving unit that receives approval information transmitted from each of the two or more approval devices;
an approval determination unit that acquires request specifying information by using a request identifier included in the request information received by the request receiving unit, and determines whether the approval information corresponding to the request specifying information and received by the approval receiving unit satisfies a predetermined condition;
a token processing unit that performs a token process related to the token , the token processing being a process corresponding to the request identifier when the approval determination unit determines that the predetermined condition is satisfied,
The predetermined condition is:
the number of approvals indicated by the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval ratio based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval points based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value,
The approval points are a total of points stored in association with each approver for the approval device that has transmitted approval information indicating approval . An information processing method implemented by a request receiving unit, an approval receiving unit, an approval determining unit, and a token processing unit,
a request receiving step in which the request receiving unit receives, from a request terminal, request information having a request identifier that identifies a request for processing related to a token;
an approval receiving step in which the approval receiving unit receives approval information transmitted from each of two or more approval devices;
an approval determination step in which the approval determination unit acquires request specific information using a request identifier included in the request information received in the request receiving step, and determines whether the approval information corresponds to the request specific information and whether the approval information received by the approval receiving unit satisfies a predetermined condition;
a token processing step in which the token processing unit performs a token processing related to the token, the token processing unit being a process corresponding to the request identifier when the approval determination unit determines that the predetermined condition is satisfied ,
The predetermined condition is:
the number of approvals indicated by the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval ratio based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval points based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value,
The information processing method , wherein the approval points are a sum of points stored in association with each approver for the approval device that has transmitted approval information indicating approval . Computer,
a request receiving unit that receives request information having a request identifier that identifies a request for processing related to the token from a request terminal;
an approval receiving unit that receives approval information transmitted from each of the two or more approval devices;
an approval determination unit that acquires request specifying information by using a request identifier included in the request information received by the request receiving unit, and determines whether the approval information corresponding to the request specifying information and received by the approval receiving unit satisfies a predetermined condition;
a program for causing the program to function as a token processing unit that performs a process corresponding to the request identifier and a token process related to the token when the approval determination unit determines that the predetermined condition is satisfied ,
The predetermined condition is:
the number of approvals indicated by the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval ratio based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value, or the approval points based on the approval information received by the approval receiving unit from each of the two or more approval devices is equal to or greater than a threshold value,
The approval points are a total of points stored in association with each approver for the approval device that has transmitted approval information indicating approval .

Images