Information processing device, information processing method, and information processing program

The information processing device manages blockchain tokens to prevent attacks and optimize transaction processing, addressing system vulnerabilities and efficiency issues in multi-blockchain systems.

JP2024162800AInactive Publication Date: 2024-11-21FUJITSU LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023078706
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-11
Publication Date
2024-11-21
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Conventional systems linking multiple blockchains face challenges in preventing attacks by control devices and suffer increased processing time and load due to signature verification processes.

Method used

An information processing device that manages tokens for blockchain accounts, determines token validity, and generates transactions with or without signatures based on token existence, reducing the need for new token issuance and signature verification.

Benefits of technology

This approach effectively prevents attacks on the system by controlling transaction generation and verification, reducing processing time and load, thereby enhancing system reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024162800000001_ABST
    Figure 2024162800000001_ABST
Patent Text Reader

Abstract

To easily prevent attacks against a system.SOLUTION: A creation device 101 specifies an account of a signer 1 to which a token is to be issued when receiving a Tx creation request. The creation device 101 creates Tx for the specified account of the signer 1. The creation device 101 determines whether a valid token corresponding to the specified account of the signer 1 exists. The creation device 101 transmits, when determining that the valid token exists, the created Tx to a cooperation engine 241. The creation device 101 affixes, when determining that the valid token does not exist, a signature to the created Tx. The creation device 101 controls a cooperation destination BC 231 to issue a new valid token corresponding to the specified account of the signer 1. The creation device 101 transmits the created Tx to the cooperation engine 241.SELECTED DRAWING: Figure 6
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing method, and an information processing program. [Background technology]

[0002] Conventionally, there are systems that link multiple blockchains. For example, the above-mentioned system is realized by a control device that links multiple linking blockchains using a linking blockchain. Here, in order to deal with system failures, multiple control devices are sometimes prepared for redundancy.

[0003] Prior art includes, for example, a technique for transmitting a digital signature generated using a receiving address. Another example is a technique for generating a login token. Another example is a technique for verifying a digital signature corresponding to a query request using a public key. Another example is a technique for transmitting signature value request information including a verification confirmation value to a user terminal when a user certificate is registered in a blockchain. Another example is a technique for attaching a signature to a transaction value and transmitting it. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2022-166123 A [Patent Document 2] US Patent Application Publication No. 2020-0127832 [Patent Document 3] US Patent Application Publication No. 2020-0019980 [Patent Document 4] JP 2019-185774 A [Patent Document 5] Patent Publication No. 2022-003547 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the conventional technology, it is difficult to prevent attacks on the system by any of the multiple control devices. For example, one of the control devices may tamper with a transaction to be sent to a linked blockchain. In response to this, if an attempt is made to prevent tampering, there is a problem that the time required to send a transaction to a linked blockchain increases.

[0006] In one aspect, the present invention aims to make it easier to prevent attacks against a system. [Means for solving the problem]

[0007] According to one embodiment, an information processing device, an information processing method, and an information processing program are proposed that receive a processing request from a coordination unit that coordinates blockchains to generate a transaction for a target account in a target blockchain, determine whether or not a valid existing token for the target account in the target blockchain exists based on management information indicating the existence or absence of a valid token for each of one or more accounts in the target blockchain and the received processing request, and if it is determined that the existing token does not exist, generate a first transaction for the target account in the target blockchain to which a signature for the target account is attached, control the target blockchain to issue a valid new token for the target account in the target blockchain, update the management information, and return the generated first transaction to the coordination unit, and if it is determined that the existing token exists, generate a second transaction for the target account in the target blockchain and return the generated second transaction to the coordination unit. Effect of the Invention

[0008] According to one aspect, it becomes possible to facilitate prevention of attacks against a system. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of an information processing method according to an embodiment. [Diagram 2] FIG. 2 is an explanatory diagram illustrating an example of a cooperative processing system 200. As shown in FIG. [Diagram 3] FIG. 3 is an explanatory diagram showing an application example of the cooperative processing system 200. As shown in FIG. [Figure 4] FIG. 4 is a block diagram showing an example of a hardware configuration of the information processing device 100. As shown in FIG. [Diagram 5] FIG. 5 is a block diagram showing an example of a functional configuration of the information processing device 100. As shown in FIG. [Figure 6] FIG. 6 is an explanatory diagram showing a first operation example of the information processing device 100. As shown in FIG. [Figure 7] FIG. 7 is an explanatory diagram (part 1) showing a second operation example of the information processing device 100. In FIG. [Figure 8] FIG. 8 is an explanatory diagram (part 2) showing a second operation example of the information processing device 100. In FIG. [Figure 9] FIG. 9 is an explanatory diagram (part 1) showing a specific example of the information processing device 100. [Figure 10] FIG. 10 is an explanatory diagram (part 2) showing a specific example of the information processing device 100. [Figure 11] FIG. 11 is an explanatory diagram (part 1) showing an embodiment of the information processing device 100. As shown in FIG. [Figure 12] FIG. 12 is an explanatory diagram (part 2) showing an embodiment of the information processing device 100. In FIG. [Figure 13] FIG. 13 is a flowchart (part 1) illustrating an example of an overall processing procedure. [Figure 14] FIG. 14 is a flowchart (part 2) illustrating an example of the overall processing procedure. [Figure 15] FIG. 15 is a sequence diagram of an example of a procedure of the initial creation process (part 1). [Figure 16]FIG. 16 is a sequence diagram illustrating an example of the initial creation process procedure (part 2). [Figure 17] FIG. 17 is a sequence diagram of an example of the initial creation process (part 3). [Figure 18] FIG. 18 is a sequence diagram of an example of a re-creation process procedure (part 1). [Figure 19] FIG. 19 is a sequence diagram of an example of a re-creation process (part 2). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an information processing device, an information processing method, and an information processing program according to embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0011] (An example of an information processing method according to an embodiment) 1 is an explanatory diagram showing an example of an information processing method according to an embodiment. The information processing device 100 is a computer for easily preventing attacks on a federation processing system that links multiple federation destination blockchains, thereby making it easier to improve the reliability of the federation processing system. The information processing device 100 is, for example, a server or a PC (Personal Computer).

[0012] Here, the linked blockchain is a management system that manages the distributed ledger. The linked blockchain includes multiple nodes. Each node of the linked blockchain stores and monitors the same distributed ledger, thereby managing the distributed ledger. The BC is a list that manages transactions by linking blocks in which transactions are registered.

[0013] Collaboration is the process of having each of multiple partner blockchains execute a transaction according to rules. A transaction is information about a transaction. Executing a transaction is the process of verifying and sharing a transaction in the partner blockchain.

[0014] The above-mentioned federation processing system includes, for example, a control device called a federation engine that links the linked blockchains, and a federation blockchain that has a smart contract that specifies the rules of the federation. The federation engine uses the smart contract to link the linked blockchains by having one of the linked blockchains execute the transaction every time it generates a transaction according to the rules of the federation. A specific example of the above-mentioned federation processing system will be described later with reference to, for example, FIG. 2 and FIG. 3.

[0015] Here, in order to deal with the occurrence of failures in the above-mentioned federation processing system, multiple federation engines may be prepared for redundancy. For example, a different federation engine may be prepared for each node of the federation destination blockchain for redundancy. The multiple federation engines may each be managed by a different management entity.

[0016] In this case, there is a risk that one of the multiple collaboration engines will launch an attack on the collaboration processing system. For example, one of the collaboration engines may tamper with a transaction to be sent to a collaboration destination blockchain. For example, one of the collaboration engines may cause a collaboration destination blockchain to execute a transaction that does not comply with the collaboration rules. For example, one of the collaboration engines may fraudulently execute a process that is originally the responsibility of another collaboration engine.

[0017] However, conventionally, it is difficult to prevent attacks on the collaboration processing system by any of the collaboration engines. For example, a method of preventing attacks can be considered by providing a signature device that affixes a signature to a transaction outside the collaboration engine. Specifically, in this method, the collaboration engine first transmits the transaction to the signature device, obtains the signed transaction, and transmits it to the collaboration destination blockchain. Specifically, in this method, the collaboration destination blockchain verifies the validity of the signature affixed to the transaction before executing the transaction.

[0018] This method has the problem of increasing the time required for the collaboration engine to send a transaction to the collaboration partner blockchain after generating the transaction, and also of increasing the processing load on the collaboration engine.

[0019] Therefore, in this embodiment, an information processing method that can easily prevent attacks on a federated processing system that links multiple blockchains will be described. In the following description, a blockchain may be written as "BC (Block Chain)". In the following description, a transaction may be written as "Tx (Transaction)".

[0020] In FIG. 1, there is a collaboration unit 110. The collaboration unit 110 corresponds to, for example, a collaboration engine. In addition, there is a target BC 120. The target BC 120 manages Tx for the target account by using a distributed ledger. The collaboration unit 110 transmits a processing request to the information processing device 100, requesting that a Tx for the target account be generated in the target BC 120. The processing request includes, for example, an identifier that identifies the target BC 120. The processing request includes, for example, an identifier that identifies the target account.

[0021] The information processing device 100 stores management information 130. The management information 130 indicates the presence or absence of a valid token for each of one or more accounts in the target BC 120. The one or more accounts include, for example, the target account. The management information 130 includes, for example, correspondence information that associates an identifier for identifying each account with an identifier for identifying a valid token for the account.

[0022] (1-1) The information processing device 100 receives a processing request from the collaboration unit 110.

[0023] (1-2) The information processing device 100 determines whether or not a valid existing token for the target account in the target BC 120 exists based on the management information 130 and the received processing request. The information processing device 100 identifies the target BC 120 based on, for example, the received processing request. The information processing device 100 identifies the target account based on, for example, the received processing request. The information processing device 100 determines whether or not a valid existing token for the identified target account in the identified target BC 120 exists based on, for example, the management information 130.

[0024] This allows the information processing device 100 to determine whether the collaboration unit 110 is in a situation where it can transmit Tx to the target BC 120 without issuing a new valid token, and therefore to determine whether it is possible to avoid issuing a new valid token.

[0025] (1-3) When the information processing device 100 determines that an existing token does not exist, it generates a signature for the target account. The information processing device 100 generates a first Tx for the target account in the target BC 120 to which the generated signature is attached. The information processing device 100 controls the target BC 120 to store a valid new token for the target account in the target BC 120. The information processing device 100 controls the target BC 120 to issue, for example, a valid new token for the target account in the target BC 120. The information processing device 100 updates the management information 130. The information processing device 100 returns the generated first Tx to the collaboration unit 110.

[0026] Thereby, the information processing device 100 can make it possible to verify the validity of the first Tx in the target BC 120 by attaching a signature to the first Tx. The information processing device 100 can make it impossible for the collaboration unit to generate a signature, which can facilitate the prevention of attacks by the collaboration unit 110. The information processing device 100 can leave a token in the target BC 120, which can facilitate the collaboration unit 110 to transmit Tx to the target BC 120 thereafter.

[0027] (1-4) When the information processing device 100 determines that an existing token exists, it generates a second Tx for the target account in the target BC 120. The information processing device 100 returns the generated second Tx to the link unit 110.

[0028] This allows the information processing device 100 to omit the process of generating a signature for the target account and the process of controlling the target BC 120 to store a valid new token. Therefore, the information processing device 100 can reduce the processing load imposed when preventing an attack by the cooperation unit 110, and can reduce the time required for the cooperation unit 110 to transmit the second Tx to the target BC 120. The information processing device 100 can enable the cooperation unit 110 to transmit the second Tx to the target BC 120.

[0029] (1-5) The collaboration unit 110 receives the first Tx to which a signature is attached or the second Tx to which no signature is attached from the information processing device 100. The collaboration unit 110 transmits the first Tx to which a signature is attached or the second Tx to which no signature is attached to the target BC 120. In this way, the collaboration unit 110 can cause the target BC 120 to execute the first Tx to which a signature is attached or the second Tx to which no signature is attached.

[0030] (1-6) The target BC 120 receives the first Tx to which a signature is attached or the second Tx to which no signature is attached from the link unit 110. When the target BC 120 receives the first Tx to which a signature is attached or the second Tx to which no signature is attached, the target BC 120 determines whether or not a valid token exists in the target BC 120. When the target BC 120 receives the first Tx to which a signature is attached, it verifies the validity of the signature.

[0031] When the target BC 120 receives the first Tx with a signature, if the signature is valid and a valid token exists in the target BC 120, it executes the first Tx. When the target BC 120 receives the first Tx with a signature, if the signature is not valid, it discards the first Tx without executing it. When the target BC 120 receives the first Tx with a signature, if a valid token does not exist in the target BC 120, it discards the first Tx without executing it.

[0032] When the target BC 120 receives the second Tx without a signature, if a valid token exists in the target BC 120, the target BC 120 executes the second Tx. When the target BC 120 receives the second Tx without a signature, if a valid token does not exist in the target BC 120, the target BC 120 discards the second Tx without executing it. This allows the target BC 120 to execute Tx appropriately.

[0033] Here, the case where the linking unit 110 transmits the first Tx to which a signature is added to the target BC 120 has been described, but the present invention is not limited to this. For example, the linking unit 110 may transmit the first Tx to which no signature is added to the target BC 120. In this case, when the target BC 120 receives the first Tx to which no signature is added, if a valid token exists in the target BC 120, the target BC 120 executes the first Tx. When the target BC 120 receives the first Tx to which no signature is added, if a valid token does not exist in the target BC 120, the target BC 120 discards the first Tx without executing it.

[0034] Here, the case where the information processing device 100 stores the management information 130 has been described, but the present invention is not limited to this. For example, the information processing device 100 may communicate with another computer that stores the management information 130. In this case, for example, the information processing device 100 determines whether or not a valid existing token related to the target account in the target BC 120 exists by communicating with the other computer that stores the management information 130.

[0035] Here, the case where the information processing device 100 controls the target BC 120 to issue a valid new token related to the target account has been described, but the present invention is not limited to this. For example, the information processing device 100 may issue a valid new token related to the target account. In this case, for example, the information processing device 100 controls the target BC 120 to store the valid new token related to the target account in the target BC 120 by transmitting the valid new token related to the target account to the target BC 120.

[0036] (An example of the collaborative processing system 200) Next, an example of a cooperative processing system 200 to which the information processing device 100 shown in FIG. 1 is applied will be described with reference to FIG.

[0037] Fig. 2 is an explanatory diagram showing an example of a cooperation processing system 200. In Fig. 2, the cooperation processing system 200 includes one or more information processing devices 100, one or more client devices 210, one or more cooperation control devices 240, one or more cooperation BCs 220, and a plurality of cooperation destination BCs 230. The cooperation BC 220 includes one or more cooperation BC nodes 250. The cooperation destination BC 230 includes one or more cooperation destination BC nodes 260.

[0038] In the cooperative processing system 200, the information processing devices 100 are connected to each other via a wired or wireless network 201. The network 201 is, for example, a local area network (LAN), a wide area network (WAN), the Internet, etc. In the cooperative processing system 200, the information processing devices 100 and the cooperative control device 240 are connected to each other via the wired or wireless network 201.

[0039] In the cooperative processing system 200, the information processing device 100 and the cooperative BC 220 are connected via a wired or wireless network 201. In the cooperative processing system 200, the information processing device 100 and the cooperative BC 230 are connected via a wired or wireless network 201. In the cooperative processing system 200, the information processing device 100 and the client device 210 are connected via the wired or wireless network 201.

[0040] In the cooperation processing system 200, the cooperation control device 240 and the cooperation BC 220 are connected via a wired or wireless network 201. In the cooperation processing system 200, the cooperation control device 240 and the cooperation destination BC 230 are connected via a wired or wireless network 201.

[0041] The client device 210 is a computer that transmits a collaboration execution request to the collaboration control device 240, requesting the start of a series of processes that collaborate with multiple collaboration destination BCs 230. The client device 210 generates a collaboration execution request based on, for example, a user's operational input, and transmits it to the collaboration control device 240. The collaboration execution request includes, for example, a collaboration execution ID that identifies the collaboration execution request. The collaboration execution request includes, for example, parameters that define the content of a series of processes related to the collaboration. The client device 210 is, for example, a PC, a tablet terminal, or a smartphone.

[0042] The cooperation control device 240 is a computer for cooperation between multiple cooperation destination BCs 230. The cooperation control device 240 receives a cooperation execution request from the client device 210. Based on the cooperation execution request, the cooperation control device 240 transmits a cooperation start Tx, which requests the start of a series of processes for cooperation between multiple cooperation destination BCs 230, to the cooperation BC node 250 included in the cooperation BC 220.

[0043] The cooperation control device 240 receives a processing request for executing a first process among a series of processes from the cooperation BC node 250. The processing request indicates, for example, the cooperation destination BC 230 to be the target of the first process and the target account to be the target of the first process in the target cooperation destination BC 230.

[0044] The cooperation control device 240 executes the initial process using the target cooperation destination BC 230. For example, the cooperation control device 240 completes the initial process by causing the target cooperation destination BC 230 to record the Tx related to the initial process. Specifically, the cooperation control device 240 transmits a Tx creation request requesting the creation of a Tx related to the initial process to the information processing device 100. The Tx creation request indicates, for example, the target cooperation destination BC 230 related to the initial process and the target account related to the initial process in the target cooperation destination BC 230.

[0045] The cooperation control device 240 specifically receives Tx for the initial processing from the information processing device 100. Specifically, the cooperation control device 240 transmits the received Tx to the target cooperation destination BC node 260 and causes it to be recorded in the target cooperation destination BC 230. After causing the target cooperation destination BC 230 to record the Tx for the initial processing, the cooperation control device 240 generates an execution completion Tx indicating that the initial processing has been completed, transmits this to the cooperation BC node 250, and causes it to be recorded in the cooperation BC 220.

[0046] The cooperation control device 240 receives a processing request for executing the next process among a series of processes from the cooperation BC node 250. The processing request indicates, for example, the cooperation destination BC 230 to be the target of the next process and the target account in the cooperation destination BC 230 to be the target of the next process.

[0047] The cooperation control device 240 executes the next process by using the target cooperation destination BC 230. For example, the cooperation control device 240 completes the next process by causing the target cooperation destination BC 230 to record the Tx related to the next process. Specifically, the cooperation control device 240 transmits a Tx creation request requesting the creation of a Tx related to the next process to the information processing device 100. The Tx creation request indicates, for example, the target cooperation destination BC 230 related to the next process and the target account related to the next process in the target cooperation destination BC 230.

[0048] The cooperation control device 240 specifically receives Tx for the next process from the information processing device 100. The cooperation control device 240 specifically transmits the received Tx to the target cooperation destination BC node 260 and causes it to be recorded in the target cooperation destination BC 230. When the cooperation control device 240 causes the target cooperation destination BC 230 to record the Tx for the next process, it generates an execution completion Tx indicating that the next process has been completed, transmits it to the cooperation BC node 250, and causes it to be recorded in the cooperation BC 220. The cooperation control device 240 is, for example, a server or a PC.

[0049] The association BC node 250 is a computer that forms the association BC 220 and manages the distributed ledger. The association BC node 250 is equipped with logic called a smart contract, for example.

[0050] The cooperation BC node 250 receives the cooperation start Tx from the cooperation control device 240. Upon receiving the cooperation start Tx, the cooperation BC node 250 transmits a processing request to the cooperation control device 240, requesting execution of the first process of a series of processes, by the smart contract. The cooperation BC node 250 records the received cooperation start Tx in the cooperation BC 220.

[0051] The cooperation BC node 250 receives the execution completion Tx from the cooperation control device 240. Upon receiving the execution completion Tx, the cooperation BC node 250 transmits a processing request to the cooperation control device 240, which requests execution of the next process of the currently completed process among the series of processes by the smart contract. The cooperation BC node 250 records the received execution completion Tx in the cooperation BC 220. The cooperation BC node 250 is, for example, a server or a PC.

[0052] The information processing device 100 is a computer having a function of creating Tx. The information processing device 100 has a token ID cache. The token ID cache stores a token ID for identifying a valid token corresponding to each of one or more accounts in the linked BC 230. The token ID cache includes, for example, correspondence information that associates a public key ID for identifying an account with a token ID for identifying a valid token corresponding to the account.

[0053] The information processing device 100 receives, for example, a Tx creation request requesting creation of a Tx related to any one of a series of processes from the cooperation control device 240. The information processing device 100 identifies a target cooperation destination BC 230 related to any one of the processes based on the received Tx creation request, and identifies a target account in the target cooperation destination BC 230. The information processing device 100 refers to the token ID cache and determines whether or not a valid token corresponding to the target account in the target cooperation destination BC 230 exists.

[0054] If no valid token exists, the information processing device 100 creates a Tx for any one of the series of processes in response to the Tx creation request. The information processing device 100 generates a signature corresponding to the target account and assigns it to the created Tx. The information processing device 100 controls the linked BC node 260 to issue a valid new token. For example, the information processing device 100 transmits an issuance request requesting the issuance of a valid new token to the linked BC node 260. The information processing device 100 receives a token ID that identifies the transmitted valid new token from the linked BC node 260. The information processing device 100 updates the stored contents of the token ID cache based on the received token ID. The information processing device 100 transmits the Tx to which the signature corresponding to the target account has been assigned to the linked control device 240.

[0055] When a valid token exists, the information processing device 100 generates a Tx relating to any one of a series of processes in response to the Tx generation request, and transmits the Tx to the cooperation control device 240. The information processing device 100 is, for example, a server or a PC.

[0056] The linked BC node 260 is a computer that forms the linked BC 230 and manages the distributed ledger. The linked BC node 260 is equipped with logic called a smart contract, for example. The linked BC node 260 issues a valid new token under the control of the information processing device 100. The linked BC node 260 records the issued valid new token in the linked BC 220 by the smart contract. The linked BC node 260 issues a token ID that identifies the valid new token by the smart contract, and transmits it to the information processing device 100.

[0057] The linked BC node 260 receives Tx from the linked control device 240. If a signature is attached to Tx, the linked BC node 260 verifies the validity of the signature by a smart contract. The linked BC node 260 determines whether or not a valid token corresponding to the target account related to Tx exists by a smart contract. The linked BC node 260 may determine whether or not a valid token corresponding to the target account related to Tx exists without having a smart contract.

[0058] When a signature is attached to Tx, if the signature is valid according to the smart contract and a valid token exists, the linked BC node 260 records Tx in the linked BC 220. When a signature is attached to Tx, if the signature is invalid according to the smart contract or a valid token does not exist, the linked BC node 260 discards Tx without recording it in the linked BC 230.

[0059] If a signature is not attached to Tx, and if a valid token exists according to the smart contract, the associated BC node 260 records Tx in the associated BC 230. The associated BC node 260 is, for example, a server or a PC.

[0060] Here, a case has been described in which one information processing device 100 has a function of generating Tx and a function of controlling the linked BC node 260 to issue a token, but this is not limiting. For example, there may be a first information processing device 100 having a function of generating Tx and a second information processing device 100 having a function of controlling the linked BC node 260 to issue a token. In this case, the first information processing device 100 transmits the Tx to which the signature has been added to the second information processing device 100. The second information processing device 100 verifies the validity of the signature, and controls the linked BC node 260 to issue a token if the signature is valid.

[0061] (Application example of the cooperative processing system 200) Next, an application example of the cooperative processing system 200 shown in FIG. 2 will be described with reference to FIG.

[0062] Fig. 3 is an explanatory diagram showing an application example of the link processing system 200. In Fig. 3, the link processing system 200 can be applied to, for example, a service for buying and selling securities. In the example of Fig. 3, there are a securities management BC 310 which is a linked BC 230 that manages securities, and an account management BC 320 which is a linked BC 230 that manages accounts.

[0063] The Securities Management BC 310 records Alice's securities account 311 and Bob's securities account 312. The Account Management BC 320 records Alice's financial account 321 and Bob's financial account 322.

[0064] The collaboration BC 220 has a smart contract 301 and collaboration rules 302. The collaboration rules 302 represent, for example, a process 1 in the account management BC 320 for transferring C from a financial account of A to a financial account of B, and a process 2 in the securities management BC 310 for transferring D from a securities account of B to a securities account of A, which is executed next to the process 1. A, B, C, and D are parameters.

[0065] The cooperation control device 240, for example, specifies A=Alice, B=Bob, C=10ETH, and D=Asset0 to the cooperation BC 220. The cooperation control device 240, in accordance with the control of the cooperation BC 220, causes the account management BC 320 to record Tx relating to process 1 for transferring 10ETH from Alice's financial account to Bob's financial account. The Tx relating to process 1 is generated by, for example, the information processing device 100.

[0066] The cooperation control device 240, under the control of the cooperation BC 220, causes the securities management BC 310 to record Tx relating to process 2 for transferring Asset0 from Bob's securities account to Alice's securities account. Tx relating to process 2 is generated by the information processing device 100, for example.

[0067] The coordination control device 240 monitors blocks added to the distributed ledger in each of the coordination destination BCs 230. In this way, the coordination processing system 200 can realize a service for buying and selling securities. The coordination processing system 200 can leave a trail of each process in a series of processes.

[0068] (Example of hardware configuration of information processing device 100) Next, an example of the hardware configuration of the information processing device 100 will be described with reference to FIG.

[0069] Fig. 4 is a block diagram showing an example of a hardware configuration of the information processing device 100. In Fig. 4, the information processing device 100 has a CPU (Central Processing Unit) 401, a memory 402, a network I / F (Interface) 403, a recording medium I / F 404, and a recording medium 405. In addition, each component is connected to each other via a bus 400.

[0070] Here, the CPU 401 is responsible for the overall control of the information processing device 100. The memory 402 has, for example, a read only memory (ROM), a random access memory (RAM), and a flash ROM. Specifically, for example, the flash ROM and the ROM store various programs, and the RAM is used as a work area for the CPU 401. The programs stored in the memory 402 are loaded into the CPU 401, causing the CPU 401 to execute the coded processes.

[0071] The network I / F 403 is connected to the network 201 through a communication line, and is connected to other computers via the network 201. The network I / F 403 manages an internal interface with the network 201, and controls input and output of data from other computers. The network I / F 403 is, for example, a modem or a LAN adapter.

[0072] The recording medium I / F 404 controls reading / writing data from / to the recording medium 405 under the control of the CPU 401. The recording medium I / F 404 is, for example, a disk drive, a solid state drive (SSD), a universal serial bus (USB) port, etc. The recording medium 405 is a non-volatile memory that stores data written under the control of the recording medium I / F 404. The recording medium 405 is, for example, a disk, a semiconductor memory, a USB memory, etc. The recording medium 405 may be detachable from the information processing device 100.

[0073] In addition to the above-mentioned components, the information processing device 100 may have, for example, a keyboard, a mouse, a display, a printer, a scanner, a microphone, a speaker, etc. Furthermore, the information processing device 100 may have a plurality of recording medium I / Fs 404 and recording media 405. Furthermore, the information processing device 100 may not have the recording medium I / Fs 404 and the recording media 405.

[0074] (Example of Hardware Configuration of Client Device 210) Specifically, an example of the hardware configuration of the client device 210 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 4, and therefore a description thereof will be omitted.

[0075] (Example of Hardware Configuration of Cooperation Control Device 240) A specific example of the hardware configuration of the cooperation control device 240 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 4, and therefore a description thereof will be omitted.

[0076] (Example of hardware configuration for BC node 250 for collaboration) Specifically, an example of the hardware configuration of the cooperation BC node 250 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 4, and therefore a description thereof will be omitted.

[0077] (Example of hardware configuration of the linked BC node 260) Specifically, an example of the hardware configuration of the cooperation destination BC node 260 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 4, and therefore a description thereof will be omitted.

[0078] (Example of functional configuration of information processing device 100) Next, an example of a functional configuration of the information processing device 100 will be described with reference to FIG.

[0079] Fig. 5 is a block diagram showing an example of a functional configuration of the information processing device 100. In the example of Fig. 5, specifically, an example of a functional configuration of each of the information processing devices 100 in a case where the first information processing device 100 and the second information processing device 100 cooperate with each other will be described.

[0080] The first information processing device 100 includes a first storage unit 500, a first acquisition unit 501, a first determination unit 502, a creation unit 503, an update unit 504, and a first output unit 505. The second information processing device 100 includes a second storage unit 510, a second acquisition unit 511, a second determination unit 512, an issue unit 513, and a second output unit 514.

[0081] The first storage unit 500 is realized by, for example, a storage area such as the memory 402 or the recording medium 405 shown in Fig. 4. In the following, a case where the first storage unit 500 is included in the information processing device 100 will be described, but this is not limiting. For example, the first storage unit 500 may be included in a device different from the information processing device 100, and the stored contents of the first storage unit 500 may be accessible from the information processing device 100.

[0082] The first acquisition unit 501 to the first output unit 505 function as an example of a control unit. Specifically, the first acquisition unit 501 to the first output unit 505 realize their functions by, for example, causing the CPU 401 to execute a program stored in a storage area such as the memory 402 or the recording medium 405 shown in Fig. 4, or by the network I / F 403. The processing results of each functional unit are stored in, for example, a storage area such as the memory 402 or the recording medium 405 shown in Fig. 4.

[0083] The first storage unit 500 stores various information that is referred to or updated in the processing of each functional unit. The first storage unit 500 stores, for example, management information. The management information indicates, for example, the presence or absence of a valid token for each of one or more accounts in the target BC. Specifically, the management information includes correspondence information that associates an identifier that identifies each account with an identifier that identifies a valid token for the account.

[0084] A condition for making a token valid may be set. The management information may include, for example, correspondence information that associates an identifier for identifying each account, an identifier for identifying a token related to the account, and a condition for making the token valid. The condition for making a token valid may be, for example, any timing after the token is issued, or the number of times that a Tx corresponding to an account related to the token is recorded in the linked BC 230 after the token is issued. The management information is updated by, for example, the update unit 504.

[0085] The first acquisition unit 501 acquires various information used in the processing of each functional unit. The first acquisition unit 501 stores the acquired various information in the first storage unit 500 or outputs it to each functional unit. The first acquisition unit 501 may also output the various information stored in the first storage unit 500 to each functional unit. The first acquisition unit 501 acquires various information based on, for example, an operation input by a user. The first acquisition unit 501 may receive various information from, for example, a device different from the information processing device 100.

[0086] The first acquisition unit 501 receives, for example, a processing request for generating a Tx for a target account in a target BC from a linking unit that links BCs. The linking unit exists, for example, in another computer different from the first information processing device 100 and the second information processing device 100. Specifically, the linking unit is the linking control device 240. The linking unit has a function of transmitting the received Tx to the target BC. The target BC has a function of executing the Tx if a valid token exists when the Tx is received.

[0087] The processing request indicates, for example, a target BC and a target account in the target BC. Specifically, the processing request includes an identifier for identifying the target BC and an identifier for identifying the target account. The identifier for identifying the target account is, for example, a public key ID corresponding to the target account.

[0088] The first acquisition unit 501 may receive a start trigger for starting processing of any of the functional units. The start trigger may be, for example, a predetermined operation input by a user. The start trigger may be, for example, reception of predetermined information from another computer. The start trigger may be, for example, output of predetermined information by any of the functional units. The first acquisition unit 501 receives, for example, reception of a processing request as a start trigger for starting processing by the first determination unit 502, the creation unit 503, and the update unit 504.

[0089] The first determination unit 502 determines whether or not a valid existing token exists for the target account in the target BC based on the management information and the received processing request. The first determination unit 502 identifies the target BC and the target account, for example, based on the received processing request. The first determination unit 502 determines whether or not a valid existing token exists for the identified target account in the identified target BC, for example, based on the management information. This allows the first determination unit 502 to determine whether or not the linking unit is in a state in which Tx can be transmitted to the target BC, and to determine whether or not it is not necessary to issue a valid new token.

[0090] The first determination unit 502 may determine whether or not a condition for a token related to the identified target account in the identified target BC to be valid is satisfied, if there is such a condition based on, for example, management information. For example, when the first determination unit 502 determines that the condition is satisfied, the first determination unit 502 determines that a valid existing token related to the identified target account in the identified target BC exists. For example, when the first determination unit 502 determines that the condition is not satisfied, the first determination unit 502 determines that a valid existing token related to the identified target account in the identified target BC does not exist. Thereby, the first determination unit 502 can determine whether or not the linking unit is in a state in which Tx can be transmitted to the target BC, and can determine whether or not it is not necessary to issue a valid new token.

[0091] If the first determination unit 502 determines that no existing token exists, the creation unit 503 generates a signature for the target account. The signature is electronic. The creation unit 503 generates a signature for the target account, for example, by using a private key corresponding to the target account. The creation unit 503 generates a first Tx for the target account in the target BC to which the generated signature is attached. This allows the creation unit 503 to generate a Tx that the link unit transmits to the target BC. The creation unit 503 can guarantee the reliability of the Tx and the reliability of the token by the signature.

[0092] When the first determination unit 502 determines that an existing token exists, the creation unit 503 generates a second Tx for the target account in the target BC. This allows the creation unit 503 to generate a Tx to be sent by the linking unit to the target BC. This allows the creation unit 503 to enable the linking unit to appropriately control multiple linked BCs 230.

[0093] When it is determined that there is no existing token, the update unit 504 controls the target BC to store a valid new token related to the target account in the target BC. The update unit 504 controls the target BC to store the new token, for example, via the second information processing device 100.

[0094] The update unit 504 transmits an issuance request to the second information processing device 100, which includes, for example, the first Tx to which the signature generated by the creation unit 503 is added, and requests the issuance of a valid new token for the target account in the target BC. The issuance request indicates, for example, the target BC and the target account in the target BC. Specifically, the issuance request includes an identifier for identifying the target BC and an identifier for identifying the target account. The identifier for identifying the target account is, for example, a public key ID corresponding to the target account. This allows the update unit 504 to store a valid new token in the target BC, and allows the target BC to accept the first Tx or the second Tx generated by the creation unit 503.

[0095] The update unit 504 updates the management information when the target BC is controlled to store a valid new token related to the target account in the target BC. The update unit 504 receives an identifier for identifying the new token from the target BC as a result of controlling the target BC to store a new token, for example, via the second information processing device 100. The update unit 504 updates the management information based on, for example, the identifier for identifying the received new token. Thereby, the update unit 504 can appropriately determine the presence or absence of a valid token related to the target account in the target BC without communicating with the target BC thereafter.

[0096] The first output unit 505 outputs the processing result of at least one of the functional units. The output format is, for example, display on a display, printout on a printer, transmission to an external device via the network I / F 403, or storage in a storage area such as the memory 402 or the recording medium 405. In this way, the first output unit 505 can notify the user of the processing result of at least one of the functional units, thereby improving the convenience of the information processing device 100.

[0097] The first output unit 505 returns the first Tx generated by the creation unit 503 to the coordination unit. This enables the first output unit 505 to transmit the first Tx generated by the creation unit 503 to the target BC from the coordination unit. The first output unit 505 enables the coordination unit to appropriately control multiple coordination destination BCs 230, and enables the coordination unit to appropriately execute a series of processes.

[0098] The first output unit 505 returns the second Tx generated by the creation unit 503 to the coordination unit. This enables the first output unit 505 to transmit the first Tx generated by the creation unit 503 to the target BC from the coordination unit. The first output unit 505 enables the coordination unit to appropriately control multiple coordination destination BCs 230, and enables the coordination unit to appropriately execute a series of processes.

[0099] The linking unit transmits, for example, the received first Tx or the received second Tx to the target BC. The target BC executes the first Tx or the second Tx if a valid token exists when receiving the first Tx or the second Tx.

[0100] The second storage unit 510 is realized by, for example, a storage area such as the memory 402 or the recording medium 405 shown in Fig. 4. In the following, a case where the second storage unit 510 is included in the information processing device 100 will be described, but this is not limiting. For example, the second storage unit 510 may be included in a device different from the information processing device 100, and the stored contents of the second storage unit 510 may be accessible from the information processing device 100.

[0101] The second acquisition unit 511 to the second output unit 514 function as an example of a control unit. Specifically, the second acquisition unit 511 to the second output unit 514 realize their functions by, for example, causing the CPU 401 to execute a program stored in a storage area such as the memory 402 or the recording medium 405 shown in Fig. 4, or by the network I / F 403. The processing result of each functional unit is stored in, for example, a storage area such as the memory 402 or the recording medium 405 shown in Fig. 4.

[0102] The second storage unit 510 stores various information that is referred to or updated in the processing of each functional unit. The second storage unit 510 stores, for example, a public key corresponding to each of one or more accounts in the target BC. The public key is acquired by, for example, the second acquisition unit 511.

[0103] The second acquisition unit 511 acquires various information used in the processing of each functional unit. The second acquisition unit 511 stores the acquired various information in the second storage unit 510 or outputs it to each functional unit. The second acquisition unit 511 may also output the various information stored in the second storage unit 510 to each functional unit. The second acquisition unit 511 acquires various information based on, for example, an operation input by a user. The second acquisition unit 511 may receive various information from, for example, a device different from the information processing device 100.

[0104] The second acquisition unit 511 receives, for example, an issuance request from the first information processing device 100, requesting the issuance of a valid new token related to a target account in a target BC. The issuance request includes, for example, a first Tx to which a signature is attached. The issuance request indicates, for example, the target BC and the target account in the target BC. Specifically, the processing request includes an identifier for identifying the target BC and an identifier for identifying the target account. The identifier for identifying the target account is, for example, a public key ID corresponding to the target account.

[0105] The second acquisition unit 511 acquires, for example, a public key corresponding to a target account in a target BC. Specifically, the second acquisition unit 511 communicates with the association BC 220 based on a public key ID corresponding to the target account, and acquires the public key corresponding to the target account in the target BC by receiving it from the association BC 220.

[0106] The second acquisition unit 511 may receive a start trigger for starting processing of any of the functional units. The start trigger may be, for example, a predetermined operational input by a user. The start trigger may be, for example, reception of predetermined information from another computer. The start trigger may be, for example, output of predetermined information by any of the functional units. The second acquisition unit 511 receives, for example, reception of an issuance request as a start trigger for starting processing of the second determination unit 512 and the issuance unit 513.

[0107] The second determination unit 512 verifies the validity of the signature added to the first Tx. For example, the second determination unit 512 verifies the validity of the signature added to the first Tx based on a public key corresponding to the target account. This allows the second determination unit 512 to determine whether or not a new token may be issued. The second determination unit 512 can easily prevent a situation in which a new token is issued illegally.

[0108] The issuing unit 513 controls the target BC to issue a valid new token when the second judging unit 512 judges that the signature is valid. For example, when the second judging unit 512 judges that the signature is valid, the issuing unit 513 transmits an issuing request to the target BC to request that a valid new token be issued. This allows the issuing unit 513 to issue, in the target BC, a token to be recorded in the target BC. The issuing unit 513 can easily prevent a situation in which a valid new token is issued fraudulently.

[0109] The second output unit 514 outputs the processing result of at least one of the functional units. The output format is, for example, display on a display, printout on a printer, transmission to an external device via the network I / F 403, or storage in a storage area such as the memory 402 or the recording medium 405. In this way, the second output unit 514 can notify the user of the processing result of at least one of the functional units, thereby improving the convenience of the information processing device 100.

[0110] The second output unit 514 transmits, for example, a result of controlling the target BC so that the issuing unit 513 issues a valid new token to the first information processing device 100. This allows the first information processing device 100 to understand that the second output unit 514 has controlled the target BC so that the valid new token is issued.

[0111] The target BC may store an account that is permitted to be a target for issuing a token. The target BC issues a new token if the target account is an account that is permitted to be a target for issuing a token. The target BC issues a new token in response to the issuance request, for example, if the target account is an account that is permitted to be a target for issuing a token. The target BC does not need to issue a new token if the target account is not an account that is permitted to be a target for issuing a token.

[0112] The target BC may store the information processing device 100 that is permitted to be a source that issues a token. The target BC issues a new token when the second information processing device 100 is the information processing device 100 that is permitted to be a source that issues a token. The target BC issues a new token in response to the issuance request when, for example, the second information processing device 100 is the information processing device 100 that is permitted to be a source that issues a token. The target BC does not need to issue a new token when the second information processing device 100 is not the information processing device 100 that is permitted to be a source that issues a token.

[0113] The target BC does not need to issue a new token if the issuer of the token and the target to which the token is issued are the same.

[0114] Here, the case where the first information processing device 100 and the second information processing device 100 cooperate with each other has been described, but the present invention is not limited to this. For example, one information processing device 100 may have a function of generating Tx and a function of controlling a target BC to issue a token. Specifically, the first information processing device 100 may include a second acquisition unit 511, an issuing unit 513, and a second output unit 514.

[0115] (First operation example of information processing device 100) Next, a first operation example of the information processing device 100 will be described with reference to Fig. 6. The first operation example corresponds to a case where a single information processing device 100 controls the generation of Tx and the issuance of a token. In the following description, the single information processing device 100 that controls the generation of Tx and the issuance of a token may be referred to as a "creation device 101".

[0116] Fig. 6 is an explanatory diagram showing a first operation example of the information processing device 100. In Fig. 6, the cooperation control device 240 has a cooperation engine 241. In addition, there is a cooperation destination BC-A. In the following description, the cooperation destination BC-A may be written as "cooperation destination BC 231".

[0117] The associated BC 231 manages the account of signer1. The associated BC 231 also manages the account of the account of the creating device 101. The associated BC 231 also records the account of signer1 as an account permitted to be a target for issuing tokens. The associated BC 231 also records the account of the creating device 101 as an account permitted to be an issuer of tokens.

[0118] The creating device 101 has a cache file that records information indicating the presence or absence of a valid token corresponding to each of one or more accounts in the linked BC 231. The cache file includes, for example, correspondence information that associates a public key ID that identifies an account with a token ID that identifies a valid token corresponding to the account.

[0119] The token may have, for example, a condition set for it to become valid. The condition for it to become valid is, for example, a condition related to a period, the number of times Tx has been executed in the associated BC 231, or the data amount of Tx executed in the associated BC 231. The correspondence information may include, for example, the condition set in the token.

[0120] (6-1) The collaboration engine 241 transmits a Tx creation request to the creating device 101. Upon receiving the Tx creation request, the creating device 101 identifies the collaboration destination BC 231 and identifies the account of signer1 to which a token is to be issued. The creating device 101 identifies the public key ID corresponding to the identified account of signer1.

[0121] (6-2) The creating device 101 generates Tx for the identified account of signer 1. The creating device 101 determines whether or not a valid token corresponding to the identified account of signer 1 exists.

[0122] For example, if a token ID corresponding to the identified public key ID does not exist in the cache file, the creation device 101 determines that a valid token does not exist corresponding to the identified account of signer 1. For example, if a token ID corresponding to the identified public key ID exists in the cache file, the creation device 101 determines that a valid token exists corresponding to the identified account of signer 1.

[0123] For example, when a token ID corresponding to the identified public key ID exists in the cache file and a condition set in the token exists, the creating device 101 may determine whether the condition is satisfied. For example, when the creating device 101 determines that the condition is not satisfied, the creating device 101 determines that a valid token corresponding to the identified account of signer1 does not exist. For example, when the creating device 101 determines that the condition is satisfied, the creating device 101 determines that a valid token corresponding to the identified account of signer1 exists.

[0124] Here, when the creating device 101 determines that a valid token exists, it skips the processes (6-3) to (6-5) described below, and transmits the generated Tx to the collaboration engine 241. As a result, when the creating device 101 determines that a valid token exists, it is possible to reduce the time required from receiving a Tx creation request to transmitting the generated Tx to the collaboration engine 241. As a result, the creating device 101 can reduce the time required from the collaboration engine 241 sending a Tx creation request to transmitting the Tx to the collaboration destination BC 231.

[0125] (6-3) If the creating device 101 determines that a valid token does not exist, it generates a signature for the generated Tx based on a private key corresponding to the account of the identified signer 1. The creating device 101 attaches the generated signature to the generated Tx.

[0126] (6-4) The creating device 101 controls the associated BC 231 to issue a valid new token corresponding to the identified account of signer 1. The creating device 101 transmits, for example, an issuance request to the associated BC 231 to request that a new token be issued in association with the identified account of signer 1. The issuance request may include, for example, the account of signer 1.

[0127] In response to the issuance request, the associated BC 231 issues a new token associated with signer1's account. The associated BC 231 assigns a token ID to the token associated with signer1's account. The associated BC 231 records the token associated with signer1's account, to which the token ID has been assigned, in the distributed ledger. The associated BC 231 transmits the token ID assigned to the token associated with signer1's account to the creating device 101.

[0128] At this time, the associated BC 231 may determine whether to issue a token and record it in the distributed ledger based on the account permitted to be a target for issuing tokens and the account permitted to be a source for issuing tokens. In the example of Fig. 6, the associated BC 231 issues a token and records it in the distributed ledger because the account of signer1 is permitted to be a target for issuing tokens and the account of the creating device 101 is permitted to be a source for issuing tokens.

[0129] (6-5) The creating device 101 receives the token ID assigned to the token associated with the account of signer1 from the associated BC 231. The creating device 101 updates the cache file based on the received token ID. This allows the creating device 101 to appropriately determine whether or not there is a valid token corresponding to the account of signer1 thereafter. Thereafter, the creating device 101 transmits the generated Tx to the association engine 241.

[0130] (6-6) The collaboration engine 241 receives Tx from the creating device 101. The collaboration engine 241 transmits the received Tx to the collaboration destination BC 231, thereby causing the collaboration destination BC 231 to execute the received Tx. Tx does not need to be signed.

[0131] (6-7) The associated BC 231 receives Tx from the associated engine 241. The associated BC 231 determines whether or not a valid token corresponding to the account of signer1 corresponding to the received Tx exists. If the associated BC 231 determines that a valid token does not exist, it discards the received Tx without executing it. If the associated BC 231 determines that a valid token exists, it executes the received Tx, thereby recording the received Tx in the distributed ledger.

[0132] This allows the creating device 101 to make it impossible for the collaboration engine 241 alone to generate a signature and a token, making it easier to prevent attacks on the collaboration processing system 200 by the collaboration engine 241. By recording the token in the collaboration destination BC 231, the creating device 101 can make it possible to omit the process of generating a signature when subsequently generating a Tx. This allows the creating device 101 to reduce the time required from when the collaboration engine 241 transmits a Tx creation request until when it transmits the Tx to the collaboration destination BC 231.

[0133] (Second operation example of information processing device 100) Next, a second operation example of the information processing device 100 will be described with reference to Figs. 7 and 8. The second operation example corresponds to a case where a first information processing device 100 that generates Tx and a second information processing device 100 that controls the issuance of a token work together. In the following description, the first information processing device 100 that generates Tx may be referred to as a "creation device 101". Also, in the following description, the second information processing device 100 that controls the issuance of a token may be referred to as a "verification device 102".

[0134] 7 and 8 are explanatory diagrams showing a second operation example of the information processing device 100. In Fig. 7, the cooperation control device 240 has a cooperation engine 241. In addition, there is a cooperation destination BC-A. In the following description, the cooperation destination BC-A may be written as "cooperation destination BC 231."

[0135] The associated BC 231 manages the account of signer1. The associated BC 231 also manages the account of the verification device 102. The associated BC 231 also records the account of signer1 as an account permitted to be a target for issuing tokens. The associated BC 231 also records the account of the verification device 102 as an account permitted to be an issuer of tokens.

[0136] The creating device 101 has a cache file that records information indicating the presence or absence of a valid token corresponding to each of one or more accounts in the linked BC 231. The cache file includes, for example, correspondence information that associates a public key ID that identifies an account with a token ID that identifies a valid token corresponding to the account.

[0137] The token may have, for example, a condition set for it to become valid. The condition for it to become valid is, for example, a condition related to a period, the number of times Tx has been executed in the associated BC 231, or the data amount of Tx executed in the associated BC 231. The correspondence information may include, for example, the condition set in the token.

[0138] (7-1) The collaboration engine 241 transmits a Tx creation request to the creating device 101. Upon receiving the Tx creation request, the creating device 101 identifies the collaboration destination BC 231 and identifies the account of signer1 to which a token is to be issued. The creating device 101 identifies the public key ID corresponding to the identified account of signer1.

[0139] (7-2) The creating device 101 generates Tx for the identified account of signer 1. The creating device 101 determines whether or not a valid token corresponding to the identified account of signer 1 exists.

[0140] For example, if a token ID corresponding to the identified public key ID does not exist in the cache file, the creation device 101 determines that a valid token does not exist corresponding to the identified account of signer 1. For example, if a token ID corresponding to the identified public key ID exists in the cache file, the creation device 101 determines that a valid token exists corresponding to the identified account of signer 1.

[0141] For example, when a token ID corresponding to the identified public key ID exists in the cache file and a condition set in the token exists, the creating device 101 may determine whether the condition is satisfied. For example, when the creating device 101 determines that the condition is not satisfied, the creating device 101 determines that a valid token corresponding to the identified account of signer1 does not exist. For example, when the creating device 101 determines that the condition is satisfied, the creating device 101 determines that a valid token corresponding to the identified account of signer1 exists.

[0142] Here, when the creating device 101 determines that a valid token exists, it skips the processes (7-3) to (7-7) described below, and transmits the generated Tx to the collaboration engine 241. As a result, when the creating device 101 determines that a valid token exists, it is possible to reduce the time required from receiving a Tx creation request to transmitting the generated Tx to the collaboration engine 241. As a result, the creating device 101 can reduce the time required from the collaboration engine 241 sending a Tx creation request to transmitting the Tx to the collaboration destination BC 231.

[0143] (7-3) If the creating device 101 determines that a valid token does not exist, it generates a signature for the generated Tx based on a private key corresponding to the account of the identified signer 1. The creating device 101 attaches the generated signature to the generated Tx.

[0144] (7-4) The creation device 101 generates a signature verification request including the signed Tx, and transmits it to the verification device 102.

[0145] (7-5) Based on the signature verification request, the verification device 102 identifies the associated BC 231 and identifies the account of signer1 to which a token is to be issued. The verification device 102 identifies a public key ID corresponding to the identified account of signer1. Based on the identified public key ID, the verification device 102 obtains a public key corresponding to the account of signer1. Based on the public key ID, the verification device 102 verifies the validity of the signature attached to the received Tx.

[0146] (7-6) If the verification device 102 determines that the signature is not valid, it decides not to issue a token. If the verification device 102 determines that the signature is valid, it controls the associated BC 231 to issue a valid new token corresponding to the identified account of signer1. The verification device 102 transmits, for example, an issuance request to the associated BC 231 requesting that a new token be issued in association with the identified account of signer1. The issuance request may include, for example, the account of signer1.

[0147] In response to the issuance request, the associated BC 231 issues a new token associated with signer1's account. The associated BC 231 assigns a token ID to the token associated with signer1's account. The associated BC 231 records the token associated with signer1's account, to which the token ID has been assigned, in the distributed ledger. The associated BC 231 transmits the token ID assigned to the token associated with signer1's account to the verification device 102. The verification device 102 transmits the received token ID to the creation device 101.

[0148] At this time, the associated BC 231 may determine whether to issue a token and record it in the distributed ledger based on the account permitted to be a target for issuing tokens and the account permitted to be a source for issuing tokens. In the example of Fig. 7, the associated BC 231 issues a token and records it in the distributed ledger because the signer1 account is permitted to be a target for issuing tokens and the verification device 102 account is permitted to be a source for issuing tokens.

[0149] (7-7) The creating device 101 receives the token ID assigned to the token associated with the account of signer1 from the verification device 102. The creating device 101 updates the cache file based on the received token ID. This allows the creating device 101 to appropriately determine thereafter whether or not there is a valid token corresponding to the account of signer1. Thereafter, the creating device 101 transmits the generated Tx to the collaboration engine 241.

[0150] (7-8) The collaboration engine 241 receives Tx from the creating device 101. The collaboration engine 241 transmits the received Tx to the collaboration destination BC 231, thereby causing the collaboration destination BC 231 to execute the received Tx. Tx does not need to be signed.

[0151] (7-9) The associated BC 231 receives Tx from the associated engine 241. The associated BC 231 determines whether or not a valid token corresponding to the account of signer1 corresponding to the received Tx exists. If the associated BC 231 determines that a valid token does not exist, it discards the received Tx without executing it. If the associated BC 231 determines that a valid token exists, it executes the received Tx, thereby recording the received Tx in the distributed ledger.

[0152] This allows the creating device 101 to make it impossible for the collaboration engine 241 alone to generate a signature and a token, making it easier to prevent attacks on the collaboration processing system 200 by the collaboration engine 241. By recording the token in the collaboration destination BC 231, the creating device 101 can make it possible to omit the process of generating a signature when subsequently generating a Tx. This allows the creating device 101 to reduce the time required from when the collaboration engine 241 transmits a Tx creation request until when it transmits the Tx to the collaboration destination BC 231. Next, we move on to the explanation of FIG. 8.

[0153] As shown in Fig. 8, there may be cases where an information processing device 100 is provided for each of the collaboration engines 241, 242 possessed by different collaboration control devices 240. The information processing device 100 corresponding to the collaboration engine 241 operates, for example, as the creation device 101 shown in Fig. 7. The information processing device 100 corresponding to the collaboration engine 241 may also operate, for example, as the verification device 102 shown in Fig. 7. The information processing device 100 corresponding to the collaboration engine 242 operates, for example, as the verification device 102 shown in Fig. 7. The information processing device 100 corresponding to the collaboration engine 242 may also operate, for example, as the creation device 101 shown in Fig. 7.

[0154] A collaboration BC node 250 may be associated with each of the collaboration engines 241, 242. For example, there is a collaboration BC node 251 corresponding to the collaboration engine 241. There is a collaboration BC node 252 corresponding to the collaboration engine 242. A collaboration destination BC node 260 may be associated with each of the collaboration engines 241, 242. For example, there is a collaboration destination BC node 261 corresponding to the collaboration engine 241. There is a collaboration destination BC node 262 corresponding to the collaboration engine 242.

[0155] (Specific example of information processing device 100) Next, a specific example of the information processing device 100 will be described with reference to FIGS.

[0156] 9 and 10 are explanatory diagrams showing a specific example of an information processing device 100. In the example of Fig. 9, similarly to Fig. 8, there is a creation device 101 corresponding to the collaboration engine 241. There is also a verification device 102. There is also a collaboration BC node 251 corresponding to the collaboration engine 241. There is also a collaboration BC node 252 corresponding to the collaboration engine 242. There is also a collaboration destination BC-A. In the following description, the collaboration destination BC-A may be referred to as "collaboration destination BC 231."

[0157] 9, the associating BC node 252 stores a public key corresponding to each of one or more accounts in the associated BC 231 in association with a public key ID that identifies the public key. The associated BC 231 manages the account of signer1. The associated BC 231 also manages the account of signer2. The account of signer2 corresponds to the verification device 102.

[0158] The creating device 101 has a cache file that records information indicating the presence or absence of a valid token corresponding to each of one or more accounts in the linked BC 231. The cache file includes, for example, correspondence information that associates a public key ID that identifies an account with a token ID that identifies a valid token corresponding to the account.

[0159] The token may have, for example, a condition set for it to become valid. The condition for it to become valid is, for example, a condition related to a period, the number of times Tx has been executed in the associated BC 231, or the data amount of Tx executed in the associated BC 231. The correspondence information may include, for example, the condition set in the token.

[0160] The collaboration engine 241 receives a collaboration execution request from the client device 210, which requests starting a series of processes that collaborate with multiple collaboration destination BCs 230 including the collaboration destination BC 231. The collaboration execution request includes, for example, a collaboration execution ID that identifies the entire series of processes to be collaborated, and collaboration execution parameters.

[0161] The linkage execution parameters are, for example, parameters that define the content of each process in the series of processes. Specifically, the linkage execution parameters may include an identifier that identifies the linkage destination BC 230 that is the target of any process in the series of processes. Specifically, the linkage execution parameters may include an identifier that identifies an account in the linkage destination BC 230 that is the target of any process in the series of processes.

[0162] Based on the received collaboration execution request, the collaboration control device 240 transmits a collaboration start Tx, which requests the start of a series of processes for collaborating multiple collaboration destination BCs 230, to the collaboration BC node 251 included in the collaboration BC 220. The collaboration start Tx includes, for example, collaboration execution parameters. The collaboration BC node 251 records the received collaboration start Tx in the distributed ledger.

[0163] The cooperation BC node 251 transmits a processing request requesting execution of one of a series of processes based on the cooperation start Tx in accordance with the cooperation rules to the cooperation engine 241. The cooperation BC node 251 transmits the processing request to each information processing device 100.

[0164] The processing request includes, for example, a linkage execution ID that identifies the entire series of linked processes. The processing request includes, for example, a process ID that identifies a specific process to be executed this time among the series of processes. The processing request includes, for example, a processing parameter that specifies the content of the specific process to be executed this time among the series of processes.

[0165] The processing parameters specifically include an identifier for identifying one or more accounts handled in the specific processing in the linked BC 230. The processing parameters specifically include an identifier for identifying one or more data handled in the specific processing in the linked BC 230. If the specific processing is to transfer specific data from a first account to a second account, the processing parameters specifically include an identifier for identifying the first account, an identifier for identifying the second account, and an identifier for identifying the specific data.

[0166] The processing request includes, for example, information specifying the information processing device 100 operating as the creation device 101 that generates Tx and assigns a signature. The processing request includes, for example, an identifier that identifies an account for which a signature is to be generated. Specifically, the processing request includes an identifier that identifies signer1 as the account for which a signature is to be generated. The processing request includes, for example, information specifying the information processing device 100 operating as the verification device 102 that verifies the signature and controls the issuance of a token. The processing request includes, for example, information specifying a collaboration engine that executes the specific process. The signature server 1 of the processing request indicates, for example, the creation device 101. The signature server 2 of the processing request indicates, for example, the verification device 102.

[0167] (9-1) The collaboration engine 241 receives a processing request from the collaboration BC node 251. The collaboration engine 241 transmits a Tx creation request to the creating device 101. The Tx creation request includes, for example, a collaboration execution ID that identifies the entire series of processes to be coordinated, and a process ID that identifies a specific process to be executed this time among the series of processes.

[0168] The creating device 101 receives a processing request from the association BC node 251. The creating device 101 receives a Tx creation request from the association engine 241. Upon receiving the Tx creation request, the creating device 101 identifies the association destination BC 231 based on the received processing request, and identifies the account of signer1 to which a token is to be issued. The creating device 101 identifies the public key ID corresponding to the identified account of signer1.

[0169] (9-2) The creating device 101 generates Tx for the identified account of signer 1. Tx may include, for example, a public key ID corresponding to the account of signer 1. In addition, the creating device 101 determines whether or not a valid token corresponding to the identified account of signer 1 exists.

[0170] For example, if a token ID corresponding to the identified public key ID does not exist in the cache file, the creation device 101 determines that a valid token does not exist corresponding to the identified account of signer 1. For example, if a token ID corresponding to the identified public key ID exists in the cache file, the creation device 101 determines that a valid token exists corresponding to the identified account of signer 1.

[0171] For example, when a token ID corresponding to the identified public key ID exists in the cache file and a condition set in the token exists, the creating device 101 may determine whether the condition is satisfied. For example, when the creating device 101 determines that the condition is not satisfied, the creating device 101 determines that a valid token corresponding to the identified account of signer1 does not exist. For example, when the creating device 101 determines that the condition is satisfied, the creating device 101 determines that a valid token corresponding to the identified account of signer1 exists.

[0172] Here, when the creating device 101 determines that a valid token exists, it omits the processes (9-3) to (9-7) described below, and transmits the generated Tx to the collaboration engine 241. As a result, when the creating device 101 determines that a valid token exists, it is possible to reduce the time required from receiving a Tx creation request to transmitting the generated Tx to the collaboration engine 241. As a result, the creating device 101 can reduce the time required from the collaboration engine 241 sending a Tx creation request to transmitting the Tx to the collaboration destination BC 231.

[0173] (9-3) If the creating device 101 determines that a valid token does not exist, it generates a signature for the generated Tx based on a private key corresponding to the account of the identified signer 1. The creating device 101 attaches the generated signature to the generated Tx.

[0174] (9-4) The creation device 101 generates a signature verification request including the signed Tx and the public key ID corresponding to the identified account of signer 1. The creation device 101 transmits the generated signature verification request to the verification device 102.

[0175] (9-5) Based on the signature verification request, the verification device 102 identifies the associated BC 231 and identifies the account of signer 1 to which a token is to be issued. Based on the signature verification request, the verification device 102 identifies the public key ID corresponding to the identified account of signer 1.

[0176] Based on the identified public key ID, the verification device 102 inquires of the associating BC node 252 about the public key corresponding to the identified account of signer1. As a result of the inquiry, the verification device 102 receives the public key corresponding to the account of signer1 from the associating BC node 252. Based on the received public key corresponding to the account of signer1, the verification device 102 verifies the validity of the signature attached to the received Tx.

[0177] (9-6) If the verification device 102 determines that the signature is not valid, it decides not to issue a token. If the verification device 102 determines that the signature is valid, it controls the associated BC 231 to issue a valid new token corresponding to the identified account of signer1. The verification device 102 transmits an issuance request to the associated BC 231, requesting that a valid new token be issued in association with the identified account of signer1. Now, we move on to the explanation of FIG. 10.

[0178] 10, the linked BC 231 records accounts that are permitted to be targets or sources of token issuance. For example, the linked BC 231 records the account of signer1 and the account of signer2 as accounts that are permitted to be targets or sources of token issuance.

[0179] Based on the account that is permitted to be the target or source of token issuance, the associated BC 231 issues a token associated with the signer1 account in response to the issuance request and determines whether to record it in the distributed ledger.

[0180] 10, the linked BC 231 is permitted to issue a token to or from the account of signer1 and the account of signer2, and therefore issues a token associated with the account of signer1 in response to an issuance request and records the token in the distributed ledger. Here, the linked BC 231 does not need to issue a token if, for example, the account to which the token is to be issued matches the account that is to be the issuer of the token.

[0181] The associated BC 231 assigns a token ID to the token associated with the account of signer 1. The token ID is, for example, token A. The associated BC 231 assigns the token ID to the token associated with the account of signer 1.

[0182] A token includes, for example, conditions for becoming valid. The conditions include, for example, an expiration date, an upper limit on the number of Tx executions, and an upper limit on data size. The expiration date indicates, for example, that the token is valid until the expiration date. The upper limit on the number of Tx executions indicates, for example, that the token is valid until the number of times Tx has been executed for an account for which the token is issued exceeds the upper limit on the number of Tx executions. The upper limit on data size indicates, for example, that the token is valid until the cumulative sum of the data sizes of Txs executed in the past for an account for which the token is issued exceeds the upper limit on data size.

[0183] The associated BC 231 records the token associated with the account of signer1 to which the token ID has been assigned in the distributed ledger. The associated BC 231 transmits the token ID assigned to the token associated with the account of signer1 to the verification device 102. The verification device 102 transmits the received token ID to the creation device 101. Now, we return to the description of FIG. 9.

[0184] In Fig. 9, (9-7) the creating device 101 receives the token ID assigned to the token associated with the account of signer1 from the verification device 102. The creating device 101 updates the cache file based on the received token ID. This allows the creating device 101 to appropriately determine thereafter whether or not there is a valid token corresponding to the account of signer1. Thereafter, the creating device 101 transmits the generated Tx to the collaboration engine 241. Now, we move on to the explanation of Fig. 10.

[0185] 10, (10-1) the collaboration engine 241 receives Tx from the creating device 101. The collaboration engine 241 transmits the received Tx to the collaboration destination BC 231, thereby causing the collaboration destination BC 231 to execute the received Tx. Tx does not need to be signed. Tx includes, for example, a public key ID corresponding to the account of signer1.

[0186] (10-2) The linked BC 231 records, in association with an account, the number of times Tx has been executed in the past for that account and the cumulative sum of the data sizes of Tx executed in the past for that account. The linked BC 231 records the cumulative number of Tx executions and the cumulative data size, in association with, for example, the public key ID corresponding to the account of signer1. The cumulative number of Tx executions indicates the number of times Tx has been executed in the past for that account. The cumulative data size indicates the cumulative sum of the data sizes of Tx executed in the past for the account.

[0187] The cooperation destination BC 231 receives Tx from the cooperation engine 241. Based on the received Tx, the cooperation destination BC 231 acquires a public key ID corresponding to the account of signer 1. Based on the acquired public key ID, the cooperation destination BC 231 determines whether or not a valid token corresponding to the account of signer 1 corresponding to the received Tx exists.

[0188] The associated BC 231 acquires the expiration date, the cumulative Tx execution count, and the cumulative data size based on the acquired public key ID, for example. The associated BC 231 determines whether or not a valid token corresponding to the signer1 account exists based on the acquired expiration date, the cumulative Tx execution count, and the cumulative data size, for example.

[0189] If the associated BC 231 determines that a valid token does not exist, it discards the received Tx without executing it. If the associated BC 231 determines that a valid token exists, it executes the received Tx and records the received Tx in the distributed ledger.

[0190] This allows the creating device 101 to make it impossible for the collaboration engine 241 alone to generate a signature and a token, making it easier to prevent attacks on the collaboration processing system 200 by the collaboration engine 241. By recording the token in the collaboration destination BC 231, the creating device 101 can make it possible to omit the process of generating a signature when subsequently generating a Tx. This allows the creating device 101 to reduce the time required from when the collaboration engine 241 transmits a Tx creation request until when it transmits the Tx to the collaboration destination BC 231.

[0191] (Example of information processing device 100) Next, an embodiment of the information processing device 100 will be described with reference to FIG. 11 and FIG.

[0192] 11 and 12 are explanatory diagrams showing an embodiment of the information processing device 100. In Fig. 11, the client device 210 has a client application 1100. The client application 1100 has a request transmission / reception unit 1101.

[0193] The collaboration control device 240 has a collaboration engine 1110. The collaboration engine 1110 includes a collaboration execution module 1111, a collaboration BC communication unit 1112, a collaboration destination BC communication unit 1113, and a creating device communication unit 1114. The collaboration BC communication unit 1112 includes a collaboration BCTx execution monitoring module 1115. The collaboration destination BC communication unit 1113 includes a collaboration destination BCTx execution monitoring module 1116. The creating device communication unit 1114 includes a Tx creation request module 1117.

[0194] The cooperation BC node 1120 which serves as a peer, which is a component of the consortium type BC, includes a BC cooperation control module 1121, cooperation rule management 1122, allocation order management 1123, and public key management 1124. The cooperation rule management 1122, the allocation order management 1123, and the public key management 1124 are recorded in a distributed ledger 1125. The cooperation BC node 1130 which serves as an orderer, which is a component of the consortium type BC, includes a block creation unit 1131. Next, we move on to the explanation of FIG. 12.

[0195] 12, the associated BC node 1200 includes a Tx execution reference unit 1201, a Tx execution control unit 1202, and a distributed ledger 1203. The Tx execution reference unit 1201 includes a Tx execution module 1204. The Tx execution control unit 1202 includes a validity verification module 1205, a token management module 1206, an accumulation module 1207, and a restriction module 1208.

[0196] The creation device 1210 includes a Tx creation unit 1211 and a signature verification unit 1212. The Tx creation unit 1211 includes a Tx creation module 1213, a cache module 1214, and a signature key management 1215. The signature verification unit 1212 is similar to, for example, a signature verification unit 1222 described below. The verification device 1220 includes a Tx creation unit 1221 and a signature verification unit 1222. The Tx creation unit 1221 is similar to the Tx creation unit 1211. The signature verification unit 1222 includes a verification module 1223 and an issuing module 1224.

[0197] (11-1) The request transmission / reception unit 1101 transmits a collaboration execution request to the collaboration execution module 1111. The collaboration execution module 1111 assigns a collaboration execution ID to the collaboration execution request. The collaboration execution module 1111 transmits the collaboration execution request with the collaboration execution ID assigned to the collaboration BCTx execution monitoring module 1115.

[0198] (11-2) The cooperation BCTx execution monitoring module 1115 transmits a cooperation start Tx to the cooperation BC node 1120 and the cooperation BC node 1130 based on the cooperation execution request, thereby causing the cooperation BC 220 to execute the cooperation start Tx.

[0199] (11-3) The block creation unit 1131 of the associating BC node 1130 generates a block that records the association start Tx, and distributes it to the associating BC node 1120. The associating BC node 1120 records the distributed block in the distributed ledger 1125.

[0200] The BC cooperation control module 1121 refers to the cooperation rule management 1122 in response to the cooperation start Tx of the block, and transmits a processing request to the cooperation BC communication unit 1112. The cooperation BC communication unit 1112 transmits the processing request to the Tx creation request module 1117 via the cooperation execution module 1111.

[0201] (11-4) The Tx creation request module 1117 identifies the creating device 1210 based on the processing request. The Tx creation request module 1117 generates a Tx creation request based on the processing request. The Tx creation request module 1117 transmits the generated Tx creation request to the creating device 1210. The Tx creation request includes a public key ID corresponding to the target account.

[0202] The Tx creation module 1213 acquires a public key ID corresponding to the target account based on the Tx creation request. The Tx creation module 1213, in cooperation with the cache module 1214, determines whether or not a valid token corresponding to the acquired public key ID exists in the signature key management 1215. If a valid token corresponding to the acquired public key ID exists, the Tx creation module 1213 generates a Tx for the target account in the linked BC 230 and transmits it to the Tx creation request module 1117.

[0203] (11-5) If there is no valid token corresponding to the acquired public key ID, the Tx creation module 1213 generates a Tx for the target account in the linked BC 230. The Tx creation module 1213 generates a signature for the generated Tx based on the private key corresponding to the target account. The Tx creation module 1213 transmits the Tx with the generated signature to the cache module 1214 together with the acquired public key ID.

[0204] (11-6) The cache module 1214 identifies the verification device 1220 based on the processing request. The cache module 1214 transmits the Tx with the signature and the public key ID to the verification module 1223 of the identified verification device 1220.

[0205] (11-7) The verification module 1223 receives the Tx to which the signature has been added and the public key ID. The verification module 1223 executes the BC cooperation control module 1121 of the cooperation BC node 1120 based on the public key ID, and acquires the public key indicated by the public key ID. The verification module 1223 verifies the validity of the signature added to the received Tx based on the acquired public key. If the signature is not valid, the verification module 1223 discards Tx, and transmits the verification result to the cache module 1214.

[0206] (11-8) If the signature is valid, the verification module 1223 transmits the verification result to the issuance module 1224. The issuance module 1224 executes the token management module 1206 of the associated BC node 1200, and controls the associated BC node 1200 to issue a token for the target account. The token includes, for example, an expiration date, an upper limit on the number of Tx executions, or an upper limit on data size.

[0207] At this time, the restriction module 1208 may determine whether or not the pair of the target account and the verification device 1220 is a pair that can issue a token, and may control whether or not to issue a token in the token management module 1206. At this time, the accumulation module 1207 initializes the number of Tx executions and the accumulated sum of data sizes. There may be cases where the token management module 1206 determines whether or not the pair of the target account and the verification device 1220 is a pair that can issue a token, and decides whether or not to issue a token.

[0208] The token management module 1206 assigns a token ID to the issued token. The token management module 1206 transmits the token ID to the verification module 1223 via the issuance module 1224. The verification module 1223 transmits the token ID to the cache module 1214.

[0209] (11-9) The cache module 1214 receives the token ID. The cache module 1214 updates the signature key management 1215 based on the received token ID. The cache module 1214 records correspondence information that associates the received token ID with the acquired public key ID in the signature key management 1215. In response to the correspondence information being recorded in the signature key management 1215, the Tx creation module 1213 transmits the generated Tx to the Tx creation request module 1117 together with the public key ID.

[0210] (11-10) The Tx creation request module 1117 receives the Tx together with the public key ID. The Tx creation request module 1117 transmits the received Tx together with the public key ID to the collaboration destination BCTx execution monitoring module 1116. The collaboration destination BCTx execution monitoring module 1116 transmits the received Tx together with the public key ID to the Tx execution module 1204.

[0211] (11-11) The Tx execution module 1204 receives the Tx together with the public key ID. The Tx execution module 1204 transmits the public key ID to the validity verification module 1205. The validity verification module 1205 identifies the target account based on the public key ID. The validity verification module 1205 verifies whether a valid token corresponding to the target account exists based on the public key ID.

[0212] The validity verification module 1205 receives, for example, the number of Tx executions and the cumulative sum of data size from the accumulation module 1207 via the token management module 1206. The validity verification module 1205 verifies whether or not a valid token corresponding to the target account exists based on, for example, the number of Tx executions and the cumulative sum of data size. The validity verification module 1205 transmits the verification result to the Tx execution module 1204 and the token management module 1206.

[0213] If a valid token exists, the Tx execution module 1204 executes the Tx. If a valid token exists, the token management module 1206 controls the accumulation module 1207 to update the number of Tx executions and the cumulative sum of data sizes. If a valid token does not exist, the Tx execution module 1204 discards the Tx without executing it.

[0214] (Overall processing procedure) Next, an example of an overall processing procedure executed by the cooperative processing system 200 will be described with reference to FIGS.

[0215] 13 and 14 are flowcharts showing an example of an overall processing procedure. In Fig. 13, the client application 1100 transmits a collaboration execution request to the collaboration BCTx execution monitoring module 1115 of the collaboration engine (step S1301).

[0216] In the collaboration engine 1110, when the collaboration BCTx execution monitoring module 1115 receives a collaboration execution request, it transmits a collaboration start Tx to the collaboration BC node 1130, thereby causing the collaboration BC 220 to execute the collaboration start Tx (step S1302). The collaboration engine 1110 acquires a processing request from the collaboration BC node 1120 (step S1303). In the collaboration engine 1110, when the Tx creation request module 1117 receives the processing request, it transmits a Tx creation request to the creation device 1210 (step S1304).

[0217] In the creating device 1210, when the Tx creating module 1213 receives a Tx creation request, it checks whether a valid token exists for the target account (step S1305). As a result of the check, the Tx creating module 1213 determines whether a valid token exists in the signature key management 1215 (step S1306). If a valid token exists (step S1306: Yes), the creating device 1210 proceeds to processing of step S1307. On the other hand, if a valid token does not exist (step S1306: No), the creating device 1210 proceeds to processing of step S1308.

[0218] In step S1307, in the creating device 1210, the Tx creating module 1213 creates a Tx and transmits it to the collaboration engine 1110 (step S1307). Upon receiving the Tx, the collaboration engine 1110 proceeds to the process of step S1404 in FIG.

[0219] In step S1308, in the creation device 1210, the Tx creation module 1213 generates a Tx and attaches a signature for the target account (step S1308). In the creation device 1210, the cache module 1214 transmits a verification request including the Tx with the signature to the verification device 1220 (step S1309).

[0220] In the verification device 1220, when the verification module 1223 receives the verification request, it obtains the public key corresponding to the target account and verifies the signature added to Tx (step S1310). Next, the verification module 1223 proceeds to step S1401 in FIG.

[0221] 14, the verification module 1223 judges whether the signature is valid or not (step S1401). If the signature is not valid (step S1401: No), the verification device 1220 proceeds to the process of step S1409. On the other hand, if the signature is valid (step S1401: Yes), the verification device 1220 proceeds to the process of step S1402.

[0222] In step S1402, in the verification device 1220, the issuing module 1224 controls the token management module 1206 to issue a token, and obtains a token ID from the token management module 1206 (step S1402). In the verification device 1220, the verification module 1223 obtains the token ID from the issuing module 1224, and transmits it to the creation device 1210.

[0223] In the creating device 1210, the cache module 1214 stores the token ID in the signature key management 1215 (step S1403). In the creating device 1210, the Tx creating module 1213 transmits Tx to the collaboration engine 1110 (step S1404).

[0224] In the collaboration engine 1110, the Tx creation request module 1117 transmits a Tx execution request to the collaboration destination BC node 1200 based on the received Tx (step S1405).

[0225] In the destination BC node 1200, the Tx execution module 1204 verifies the validity of the token via the validity verification module 1205 (step S1406). The validity verification module 1205 determines whether the token is valid or not (step S1407). If the token is valid (step S1407: Yes), the Tx execution module 1204 proceeds to processing of step S1408. On the other hand, if the token is not valid (step S1407: No), the Tx execution module 1204 proceeds to processing of step S1409.

[0226] In step S1408, in the collaboration destination BC 230, the Tx execution module 1204 executes Tx (step S1408). Then, the collaboration processing system 200 ends the overall processing. In step S1409, the Tx creation module 1213 or the Tx execution module 1204 transmits an error notification to the collaboration engine 1110 (step S1409). Then, the collaboration processing system 200 ends the overall processing.

[0227] (Initial creation process) Next, an example of an initial creation process procedure executed by the collaboration processing system 200 will be described with reference to FIGS.

[0228] 15 to 17 are sequence diagrams showing an example of an initial creation process procedure. In Fig. 15, the client application 1100 transmits an integration execution request requesting the execution of a series of integrated processes to the integration execution module 1111 (step S1501).

[0229] The cooperation execution module 1111 receives the cooperation execution request and transmits it to the cooperation BCTx execution monitoring module 1115 (step S1502). Upon receiving the cooperation execution request, the cooperation BCTx execution monitoring module 1115 generates a cooperation start Tx and controls the cooperation BC nodes 1120 and 1130 so that the cooperation BC nodes 1120 and 1130 execute it (step S1503).

[0230] The cooperation BC nodes 1120 and 1130 execute the received cooperation start Tx (step S1504). When the cooperation BC node 1120 executes the cooperation start Tx, it generates a cooperation execution ID and transmits it to the cooperation BCTx execution monitoring module 1115 (step S1505).

[0231] The collaboration BCTx execution monitoring module 1115 receives the collaboration execution ID and transmits it to the collaboration execution module 1111 (step S1506). The collaboration execution module 1111 receives the collaboration execution ID and transmits it to the client application 1100 (step S1507).

[0232] When the cooperation start Tx is executed, the cooperation BC node 1120 transmits a processing request requesting the execution of any one of a series of processes to the cooperation BCTx execution monitoring module 1115 (step S1508).

[0233] The collaboration BCTx execution monitoring module 1115 receives the processing request and transmits it to the collaboration execution module 1111 (step S1509). The collaboration execution module 1111 receives the processing request and transmits it to the collaboration destination BCTx execution monitoring module 1116 (step S1510). Upon receiving the processing request, the collaboration destination BCTx execution monitoring module 1116 transmits a Tx creation request to the Tx creation module 1213, requesting the creation of a Tx related to any of the processing (step S1511).

[0234] When the Tx creation module 1213 receives the Tx creation request, it transmits a confirmation request to the cache module 1214 to request confirmation of the presence or absence of a valid token (step S1512). The cache module 1214 transmits the received confirmation result to the Tx creation module 1213 (step S1513).

[0235] The Tx creation module 1213 generates a Tx based on the confirmation result and attaches a signature to it (step S1514). The Tx creation module 1213 generates a verification request to verify the validity of the signature and transmits it to the verification module 1223 (step S1515).

[0236] The verification module 1223 inquires of the associating BC node 1120 about the public key based on the public key ID (step S1516). The verification module 1223 receives the public key from the associating BC node 1120 (step S1517). The verification module 1223 verifies the validity of the signature (step S1518). Next, the description will proceed to FIG. 16.

[0237] 16, it is assumed that the verification module 1223 determines that the signature is not valid. The verification module 1223 generates a verification error and transmits it to the Tx creation module 1213 (step S1601). The Tx creation module 1213 transmits the received verification error to the cooperation destination BCTx execution monitoring module 1116 (step S1602).

[0238] The collaboration destination BCTx execution monitoring module 1116 transmits the received verification error to the collaboration BCTx execution monitoring module 1115 (step S1603). Upon receiving the verification error, the collaboration BCTx execution monitoring module 1115 generates an execution completion Tx and transmits it to the collaboration BC nodes 1120, 1130 (step S1604). The collaboration BC nodes 1120, 1130 receive the collaboration completion Tx and execute the collaboration completion Tx. The collaboration processing system 200 then terminates the initial creation process. Next, we move on to the explanation of FIG. 17.

[0239] 17, it is assumed that the verification module 1223 determines that the signature is valid. The verification module 1223 generates an issuance request for requesting the issuance of a token, and transmits the request to the issuance module 1224 (step S1701). The issuance module 1224 controls the token management module 1206 to issue a token (step S1702).

[0240] The token management module 1206 issues a token, generates a token ID corresponding to the issued token, and transmits it to the issuing module 1224 (step S1703).

[0241] The issuing module 1224 receives the token ID and transmits it to the verification module 1223 (step S1704). The verification module 1223 receives the token ID and transmits it to the Tx creation module 1213 (step S1705).

[0242] The Tx creation module 1213 records the token ID in the signature key management 1215 (step S1706). The Tx creation module 1213 generates a Tx and transmits it to the cooperation destination BCTx execution monitoring module 1116 (step S1707).

[0243] Upon receiving the Tx, the cooperation destination BCTx execution monitoring module 1116 generates a Tx execution request and transmits it to the Tx execution module 1204 (step S1708).

[0244] The Tx execution module 1204 updates accumulated values ​​such as the number of Tx executions and the accumulated sum of data sizes (step S1709). The Tx execution module 1204 queries the token management module 1206 about the conditions under which a token is valid based on the public key ID (step S1710). The Tx execution module 1204 receives the conditions under which a token is valid from the token management module 1206 (step S1711). The Tx execution module 1204 determines whether or not a valid token exists based on the conditions under which a token is valid (step S1712).

[0245] Here, if a valid token exists (step S1712: Yes), the Tx execution module 1204 executes the received Tx (step S1713). The Tx execution module 1204 generates a Tx execution result and transmits it to the collaboration destination BCTx execution monitoring module 1116 (step S1714). The collaboration destination BCTx execution monitoring module 1116 receives the Tx execution result and transmits it to the collaboration BCTx execution monitoring module 1115 (step S1715). The collaboration BCTx execution monitoring module 1115 proceeds to the processing of step S1718.

[0246] On the other hand, if a valid token does not exist (step S1712: No), the Tx execution module 1204 generates a Tx execution result indicating a token invalid error and transmits it to the collaboration destination BCTx execution monitoring module 1116 (step S1716). The collaboration destination BCTx execution monitoring module 1116 receives the Tx execution result and transmits it to the collaboration BCTx execution monitoring module 1115 (step S1717). The collaboration BCTx execution monitoring module 1115 proceeds to the process of step S1718.

[0247] In step S1718, the cooperation BCTx execution monitoring module 1115 transmits the Tx execution result to the cooperation BC nodes 1120 and 1130, thereby causing the cooperation BC 220 to execute it (step S1718). The cooperation BC nodes 1120 and 1130 execute the Tx execution result (step S1719). Then, the cooperation processing system 200 ends the initial creation process.

[0248] (Re-creation process procedure) Next, an example of a procedure of a re-creation process executed by the information processing device 100 will be described with reference to Fig. 18 and Fig. 19. The re-creation process is realized by, for example, the CPU 401, storage areas such as the memory 402 and the recording medium 405, and the network I / F 403 shown in Fig. 4.

[0249] 18 and 19 are sequence diagrams showing an example of a re-creation process procedure. In Fig. 18, the client application 1100 transmits an collaboration execution request for requesting the execution of a series of collaborative processes to the collaboration execution module 1111 (step S1801).

[0250] The cooperation execution module 1111 receives the cooperation execution request and transmits it to the cooperation BCTx execution monitoring module 1115 (step S1802). Upon receiving the cooperation execution request, the cooperation BCTx execution monitoring module 1115 generates a cooperation start Tx and controls the cooperation BC nodes 1120 and 1130 so that the cooperation BC nodes 1120 and 1130 execute it (step S1803).

[0251] The cooperation BC nodes 1120 and 1130 execute the received cooperation start Tx (step S1804). When the cooperation BC node 1120 executes the cooperation start Tx, it generates a cooperation execution ID and transmits it to the cooperation BCTx execution monitoring module 1115 (step S1805).

[0252] The collaboration BCTx execution monitoring module 1115 receives the collaboration execution ID and transmits it to the collaboration execution module 1111 (step S1806). The collaboration execution module 1111 receives the collaboration execution ID and transmits it to the client application 1100 (step S1807).

[0253] When the cooperation start Tx is executed, the cooperation BC node 1120 transmits a processing request requesting the execution of any one of a series of processes to the cooperation BCTx execution monitoring module 1115 (step S1808).

[0254] The collaboration BCTx execution monitoring module 1115 receives the processing request and transmits it to the collaboration execution module 1111 (step S1809). The collaboration execution module 1111 receives the processing request and transmits it to the collaboration destination BCTx execution monitoring module 1116 (step S1810). Upon receiving the processing request, the collaboration destination BCTx execution monitoring module 1116 transmits a Tx creation request to the Tx creation module 1213, requesting the creation of a Tx related to any of the processing (step S1811).

[0255] When the Tx creation module 1213 receives the Tx creation request, it transmits a confirmation request to the cache module 1214 to request confirmation of the presence or absence of a valid token (step S1812). The cache module 1214 transmits the received confirmation result to the Tx creation module 1213 (step S1813).

[0256] The Tx creation module 1213 creates a Tx based on the confirmation result (step S1814). The Tx creation module 1213 transmits the created Tx to the cooperation destination BCTx execution monitoring module 1116 (step S1815).

[0257] When the cooperation destination BCTx execution monitoring module 1116 receives the Tx, it generates a Tx execution request and transmits it to the Tx execution module 1204 (step S1816). Next, the description will move to FIG.

[0258] The Tx execution module 1204 updates accumulated values ​​such as the number of Tx executions and the accumulated sum of data sizes (step S1901). The Tx execution module 1204 queries the token management module 1206 about the conditions under which a token is valid based on the public key ID (step S1902). The Tx execution module 1204 receives the conditions under which a token is valid from the token management module 1206 (step S1903). The Tx execution module 1204 determines whether or not a valid token exists based on the conditions under which a token is valid (step S1904).

[0259] Here, if a valid token exists (step S1904: Yes), the Tx execution module 1204 executes the received Tx (step S1905). The Tx execution module 1204 generates a Tx execution result and transmits it to the collaboration destination BCTx execution monitoring module 1116 (step S1906). The collaboration destination BCTx execution monitoring module 1116 receives the Tx execution result and transmits it to the collaboration BCTx execution monitoring module 1115 (step S1907). The collaboration BCTx execution monitoring module 1115 proceeds to the processing of step S1910.

[0260] On the other hand, if a valid token does not exist (step S1904: No), the Tx execution module 1204 generates a Tx execution result indicating a token invalid error and transmits it to the collaboration destination BCTx execution monitoring module 1116 (step S1908). The collaboration destination BCTx execution monitoring module 1116 receives the Tx execution result and transmits it to the collaboration BCTx execution monitoring module 1115 (step S1909). The collaboration BCTx execution monitoring module 1115 proceeds to the process of step S1910.

[0261] In step S1910, the cooperation BCTx execution monitoring module 1115 transmits the Tx execution result to the cooperation BC nodes 1120 and 1130, thereby causing the cooperation BC 220 to execute it (step S1910). The cooperation BC nodes 1120 and 1130 execute the Tx execution result (step S1911). Then, the cooperation processing system 200 ends the initial creation process.

[0262] As described above, the information processing device 100 can receive a processing request from a linking unit that links BCs to generate a Tx for a target account in a target BC. The information processing device 100 can determine whether or not a valid existing token for a target account in a target BC exists based on management information and the received processing request. When it is determined that an existing token does not exist, the information processing device 100 can generate a first Tx for a target account in a target BC to which a signature for the target account is added. The information processing device 100 can control a target BC to store a valid new token for a target account in a target BC, update management information, and return the generated first Tx to the linking unit. When it is determined that an existing token exists, the information processing device 100 can generate a second Tx for a target account in a target BC and return the generated second Tx to the linking unit. This makes it easier for the information processing device 100 to prevent an attack on a target BC by the linking unit.

[0263] According to the information processing device 100, when it is determined that an existing token does not exist, the information processing device 100 can control the target BC to store a new token via the verification unit and update the management information. This allows the information processing device 100 to verify the validity of the signature with the verification unit, making it easier to prevent attacks on the target BC by the cooperation unit.

[0264] According to the information processing device 100, when it is determined that no existing token exists, the target BC is controlled via the verification unit to store a new token, and as a result, an identifier for identifying the new token can be received from the target BC. According to the information processing device 100, it is possible to update the management information based on the identifier for identifying the received new token. This allows the information processing device 100 to appropriately update the management information.

[0265] According to the information processing device 100, when it is determined that an existing token does not exist, the target BC is controlled to store a new token via the verification unit, and as a result, an identifier for identifying the new token with a valid condition set can be received from the target BC. This allows the information processing device 100 to appropriately update the management information.

[0266] According to the information processing device 100, it is possible to communicate with a linking unit that transmits the received first Tx or the received second Tx to a target BC. According to the information processing device 100, when the first Tx or the second Tx is received, if a valid token exists, it is possible to communicate with a target BC that executes the first Tx or the second Tx. In this way, the information processing device 100 can make the first Tx or the second Tx executable by the target BC.

[0267] According to the information processing device 100, if the target account is not an account that is permitted to issue a token, the information processing device 100 can communicate with the target BC that does not store a new token. This allows the information processing device 100 to control the target BC with improved security.

[0268] According to the information processing device 100, it is possible to communicate with a linking unit that exists in another computer different from the information processing device 100. According to the information processing device 100, it is possible to communicate with a verification unit that exists outside. This allows the information processing device 100 to increase the number of trust points, making it easier to prevent attacks on the target BC by other computers.

[0269] The information processing method described in this embodiment can be realized by executing a prepared program on a computer such as a PC or a workstation. The information processing program described in this embodiment is recorded on a computer-readable recording medium, and is executed by being read from the recording medium by the computer. The recording medium may be a hard disk, a flexible disk, a CD (Compact Disc)-ROM, an MO (Magneto Optical disc), a DVD (Digital Versatile Disc), or the like. The information processing program described in this embodiment may also be distributed via a network such as the Internet.

[0270] The following supplementary notes are further disclosed regarding the above-described embodiment.

[0271] (Supplementary Note 1) Receive a processing request from a linking unit that links blockchains, requesting that a transaction be generated for a target account in a target blockchain; Determine whether or not there is a valid existing token for the target account in the target blockchain based on management information indicating the presence or absence of a valid token for each of the one or more accounts in the target blockchain and the received processing request; If it is determined that the existing token does not exist, generate a first transaction for the target account in the target blockchain, the first transaction being accompanied by a signature for the target account, control the target blockchain to issue a valid new token for the target account in the target blockchain, update the management information, and return the generated first transaction to the coordinating unit; If it is determined that the existing token exists, generate a second transaction for the target account in the target blockchain, and return the generated second transaction to the coordination unit. An information processing device comprising a control unit.

[0272] (Additional Note 2) The control unit is The information processing device described in Appendix 1, characterized in that when it is determined that the existing token does not exist, the information processing device generates the first transaction, controls the target blockchain to store the new token via a verification unit that controls the target blockchain to issue the new token if the signature is valid, updates the management information, and returns the generated first transaction to the collaboration unit.

[0273] (Supplementary Note 3) The management information is correspondence information that associates an identifier for identifying each of the accounts with an identifier for identifying a valid token related to the account, The control unit is The information processing device described in Appendix 2, characterized in that it updates the management information based on an identifier that identifies the new token received from the target blockchain.

[0274] (Additional Note 4) The control unit is The information processing device according to claim 1, characterized in that it controls the target blockchain to issue a new token that sets valid conditions for the target account in the target blockchain.

[0275] (Supplementary Note 5) The linking unit transmits the received first transaction or the received second transaction to the target blockchain; The information processing device according to any one of appendices 1 to 4, characterized in that when the target blockchain receives the first transaction or the second transaction, if a valid token is present, the target blockchain executes the first transaction or the second transaction.

[0276] (Appendix 6) An information processing device as described in any one of Appendices 2 to 4, characterized in that the target blockchain issues the new token if the target account is an account that is authorized to issue tokens, and does not issue the new token if the target account is not an account that is authorized to issue tokens.

[0277] (Supplementary Note 7) The link unit is present in another computer different from the information processing device, 5. The information processing device according to claim 2, wherein the verification unit is present externally.

[0278] (Appendix 8) Receive a processing request from a linking unit that links blockchains, requesting that a transaction be generated for a target account in a target blockchain; Determine whether or not there is a valid existing token for the target account in the target blockchain based on management information indicating the presence or absence of a valid token for each of the one or more accounts in the target blockchain and the received processing request; If it is determined that the existing token does not exist, generate a first transaction for the target account in the target blockchain, the first transaction being accompanied by a signature for the target account, control the target blockchain to issue a valid new token for the target account in the target blockchain, update the management information, and return the generated first transaction to the coordinating unit; If it is determined that the existing token exists, generate a second transaction for the target account in the target blockchain, and return the generated second transaction to the coordination unit. An information processing method characterized in that the processing is executed by a computer.

[0279] (Appendix 9) Receive a processing request from a linking unit that links blockchains, requesting that a transaction be generated for a target account in a target blockchain; Determine whether or not there is a valid existing token for the target account in the target blockchain based on management information indicating the presence or absence of a valid token for each of the one or more accounts in the target blockchain and the received processing request; If it is determined that the existing token does not exist, generate a first transaction for the target account in the target blockchain, the first transaction being accompanied by a signature for the target account, control the target blockchain to issue a valid new token for the target account in the target blockchain, update the management information, and return the generated first transaction to the coordinating unit; If it is determined that the existing token exists, generate a second transaction for the target account in the target blockchain, and return the generated second transaction to the coordination unit. An information processing program that causes a computer to execute a process. [Explanation of symbols]

[0280] 100 Information processing device 101,1210 Creation device 102,1220 Verification device 110 Collaboration Department 120 B.C. 130 Management information 200 Collaborative Processing System 201 Network 210 Client device 220 Linked BC 230,231 Partner BC 240 Linked Control Device 241,242,1110 Collaboration Engine 250, 251, 252, 1120, 1130 BC nodes for cooperation 260, 261, 262, 1200 Collaborating BC node 301 Smart Contract 302 Rules 310 Securities Management BC 311,312 Securities account 320 Account Management BC 321,322 Financial Accounts 400 Bus 401 CPU 402 Memory 403 Network Interface 404 Recording media I / F 405 Recording media 500 1st memory section 501 First Acquisition Department 502 1st Judgment Department 503 Creation Department 504 Update Department 505 First Output Section 510 2nd memory section 511 Second Acquisition Department 512 Second Judgment Department 513 Publishing Department 514 Second output section 1100 Client Applications 1101 Request transmission / reception unit 1111 Collaboration Execution Module 1112 BC Communication Department for Collaboration 1113 Partner BC Communications Department 1114 Creation device communication unit 1115 BCTx execution monitoring module for collaboration 1116 Partner BCTx Execution Monitoring Module 1117 Tx creation request module 1121 BC Linkage Control Module 1122 Linkage Rule Management 1123 Allocation Order Management 1124 Public Key Management 1125,1203 Distributed Ledgers 1131 Block Creation Department 1201 Tx Execution Reference Section 1202 Tx execution control unit 1204 Tx Execution Module 1205 Validity Verification Module 1206 Token Management Module 1207 Accumulation Module 1208 Restriction Module 1211,1221 Tx creation department 1212,1222 Signature Verification Unit 1213 Tx Creation Module 1214 Cache Module 1215 Signing key management 1223 Verification Module 1224 Issue Module

Claims

1. Receive a processing request from a linking unit that links between blockchains, the processing request requesting generation of a transaction for a target account in a target blockchain; Determine whether or not there is a valid existing token for the target account in the target blockchain based on management information indicating the presence or absence of a valid token for each of the one or more accounts in the target blockchain and the received processing request; If it is determined that the existing token does not exist, generate a first transaction for the target account in the target blockchain, the first transaction being accompanied by a signature for the target account, control the target blockchain to issue a valid new token for the target account in the target blockchain, update the management information, and return the generated first transaction to the coordinating unit; If it is determined that the existing token exists, a second transaction is generated for the target account in the target blockchain, and the generated second transaction is returned to the link unit. An information processing device comprising a control unit.

2. The control unit is The information processing device according to claim 1, characterized in that, when it is determined that the existing token does not exist, the information processing device generates the first transaction, controls the target blockchain to store the new token via a verification unit that controls the target blockchain to issue the new token if the signature is valid, updates the management information, and returns the generated first transaction to the collaboration unit.

3. The management information is correspondence information that associates an identifier for identifying each of the accounts with an identifier for identifying a valid token related to the account, The control unit is The information processing device according to claim 2 , further comprising: updating the management information based on an identifier that identifies the new token received from the target blockchain.

4. The control unit is The information processing device according to claim 1, further comprising: controlling the target blockchain to issue a new token that sets a validity condition for the target account in the target blockchain.

5. Receive a processing request from a linking unit that links between blockchains, the processing request requesting generation of a transaction for a target account in a target blockchain; Determine whether or not there is a valid existing token for the target account in the target blockchain based on management information indicating the presence or absence of a valid token for each of the one or more accounts in the target blockchain and the received processing request; If it is determined that the existing token does not exist, generate a first transaction for the target account in the target blockchain, the first transaction being accompanied by a signature for the target account, control the target blockchain to issue a valid new token for the target account in the target blockchain, update the management information, and return the generated first transaction to the coordinating unit; If it is determined that the existing token exists, a second transaction is generated for the target account in the target blockchain, and the generated second transaction is returned to the link unit. An information processing method characterized in that the processing is executed by a computer.

6. Receive a processing request from a linking unit that links between blockchains, the processing request requesting generation of a transaction for a target account in a target blockchain; Determine whether or not there is a valid existing token for the target account in the target blockchain based on management information indicating the presence or absence of a valid token for each of the one or more accounts in the target blockchain and the received processing request; If it is determined that the existing token does not exist, generate a first transaction for the target account in the target blockchain, the first transaction being accompanied by a signature for the target account, control the target blockchain to issue a valid new token for the target account in the target blockchain, update the management information, and return the generated first transaction to the coordinating unit; If it is determined that the existing token exists, a second transaction is generated for the target account in the target blockchain, and the generated second transaction is returned to the link unit. An information processing program that causes a computer to execute a process.

Citation Information

Patent Citations

  • Integrated log-in method for block chain infrastructure, terminal, and server using the same

    JP2019185774A

  • Method and system for providing validated, auditable, and immutable inputs to smart contract

    JP2022003547A

  • Method and system for transaction processing with full cryptographic auditing capabilities

    JP2022166123A

  • Method and system for referral fraud prevention via blockchain

    US20200019980A1

  • Blockchain id connect

    US20200127832A1