WO2022180752A1 - 制御システム、制御プログラム、制御方法、および制御装置 - Google Patents
制御システム、制御プログラム、制御方法、および制御装置 Download PDFInfo
- Publication number
- WO2022180752A1 WO2022180752A1 PCT/JP2021/007214 JP2021007214W WO2022180752A1 WO 2022180752 A1 WO2022180752 A1 WO 2022180752A1 JP 2021007214 W JP2021007214 W JP 2021007214W WO 2022180752 A1 WO2022180752 A1 WO 2022180752A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- transaction information
- blockchain
- information
- transaction
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 28
- 230000010365 information processing Effects 0.000 claims abstract description 71
- 238000012545 processing Methods 0.000 claims description 47
- 230000003213 activating effect Effects 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 12
- 238000010586 diagram Methods 0.000 description 24
- 230000004913 activation Effects 0.000 description 14
- 238000012544 monitoring process Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 238000012546 transfer Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 239000004065 semiconductor Substances 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000000151 deposition Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/24—Credit schemes, i.e. "pay after"
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/407—Cancellation of a transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/06—Asset management; Financial planning or analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3297—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving time stamps, e.g. generation of time stamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
Definitions
- the present invention relates to control systems, control programs, control methods, and control devices.
- blockchain that realizes a distributed ledger that manages transaction information by linking blocks that record transaction information.
- blockchain is used in decentralized financial systems. At this time, if it is desired to reserve the operation of recording the transaction information on the blockchain so that the transaction information indicating the transaction details such as payment of money or transfer of rights is recorded on the blockchain after the specified time has passed.
- At least a predetermined node among a plurality of nodes forming a distributed ledger system executes an operation smart contract for operation management based on whether the received transaction type is an operation smart contract.
- the present invention aims to make it possible to reserve the operation of recording transaction information in the blockchain.
- a plurality of nodes forming a first blockchain network, one or more nodes forming a second blockchain network, said first blockchain network and said second wherein each node of the plurality of nodes manages a first blockchain that records a scheduled time point for validating transaction information; Based on the recorded contents of the first blockchain managed by the self-node, identifying the transaction information that has passed the scheduled time, recording the identified result in the first blockchain managed by the self-node, and the information a processing device that transmits transaction information identified by a node that satisfies a predetermined condition among the plurality of nodes to each of the one or more nodes based on the recorded content of the first blockchain; Each node of the one or more nodes manages a second blockchain that records validated transaction information, generates a block that includes the received transaction information, and manages the second block chain in its own node.
- a control system is proposed to add to the blockchain.
- FIG. 1 is an explanatory diagram of an example of a control method according to an embodiment.
- FIG. 2 is an explanatory diagram showing an example of the control system 110.
- FIG. 3 is a block diagram showing a hardware configuration example of the information processing apparatus 100.
- FIG. 4 is a block diagram showing a hardware configuration example of the first node 101.
- FIG. 5 is an explanatory diagram showing an example of the contents of the schedule transaction management information 500.
- FIG. FIG. 6 is a block diagram showing a hardware configuration example of the second node 102.
- FIG. 7 is a block diagram showing a functional configuration example of the control system 110.
- FIG. FIG. 3 is a block diagram showing a hardware configuration example of the information processing apparatus 100.
- FIG. 4 is a block diagram showing a hardware configuration example of the first node 101.
- FIG. 5 is an explanatory diagram showing an example of the contents of the schedule transaction management information 500.
- FIG. 6 is a block diagram showing a hardware configuration example of the second no
- FIG. 8 is an explanatory diagram (Part 1) showing an example of the operation of the control system 110.
- FIG. 9 is an explanatory diagram (part 2) showing an example of the operation of the control system 110.
- FIG. 10 is an explanatory diagram (part 3) showing an example of the operation of the control system 110.
- FIG. 11 is an explanatory diagram (part 4) showing an example of the operation of the control system 110.
- FIG. 12 is an explanatory diagram (part 1) showing a specific example of the operation of the control system 110.
- FIG. FIG. 13 is an explanatory diagram (part 2) showing a specific example of the operation of the control system 110.
- FIG. FIG. 10 is an explanatory diagram (part 3) showing an example of the operation of the control system 110.
- FIG. 11 is an explanatory diagram (part 4) showing an example of the operation of the control system 110.
- FIG. 12 is an explanatory diagram (part 1) showing a specific example of the operation of the control system 110.
- FIG. FIG. 13 is
- FIG. 14 is an explanatory diagram (part 3) showing a specific example of the operation of the control system 110.
- FIG. 15 is an explanatory diagram (part 4) showing a specific example of the operation of the control system 110.
- FIG. 16 is a flow chart showing an example of the overall processing procedure.
- FIG. 1 is an explanatory diagram of an example of a control method according to an embodiment.
- the information processing device 100 is a computer capable of cooperating with a blockchain network and capable of reserving an operation of recording transaction information in a blockchain.
- blockchain may be referred to as "BC (Block Chain)".
- the BC network manages BC.
- a BC network is formed by one or more nodes.
- the BC is managed by each node included in the BC network storing and monitoring the same BC.
- BC is a list that serves as a distributed ledger that manages transaction information by linking blocks in which transaction information is registered. Examples of BC networks include public, consortium, and private BC networks.
- Transaction information is, for example, called transaction (Tx: Transaction) information.
- Tx Transaction
- BC implements a distributed ledger technology that makes it difficult to falsify transaction information registered in blocks.
- BC can be used, for example, in a decentralized financial system and used for credit management.
- credit management it is desirable to determine a transaction schedule so that transactions such as payment of money or transfer of rights are performed at predetermined times.
- the transfer of rights is, for example, redemption of investment or dividend payment. For this reason, it is desirable to make it possible to reserve the operation of recording the transaction information in the BC so that the transaction information indicating the content of the transaction is recorded in the BC after a specified time has passed.
- a method called Ethereum Alarm Clock can be considered.
- Reference 1 below can be referred to.
- This method has the problem that the timer is held in the external device that performs the timer processing, resulting in an increase in the processing load.
- a control system 110 including a plurality of first nodes 101 forming a first BC network, one or more second nodes 102 forming a second BC network, and an information processing device 100 exist.
- the information processing device 100 can cooperate with a first BC network and a second BC network.
- Each first node 101 manages a first BC that records a scheduled point in time for validating transaction information.
- the scheduled point in time is the scheduled point in time at which transaction information relating to a certain transaction will be validated in response to the execution of the transaction.
- Each first node 101 identifies transaction information whose scheduled time has passed, based on the recorded contents of the first BC managed by the own node.
- Each first node 101 records information indicating transaction information for which the specified scheduled time has passed in the first BC managed by the own node.
- Information indicating transaction information is, for example, the transaction information itself.
- Each first node 101 distributes the recorded contents of the first BC managed by the own node to the information processing device 100 . Processing of each first node 101 is implemented by, for example, a smart contract. In the following description, the smart contract may be referred to as "SC (Smart Contract)".
- the information processing apparatus 100 acquires the recorded content of the first BC.
- the information processing apparatus 100 performs consensus building based on the recorded contents of the first BC, and selects transaction information specified by the first node 101 that satisfies a predetermined condition.
- the predetermined condition is, for example, the number of first nodes 101 .
- the predetermined condition may be, for example, a condition regarding attributes of the first node 101 .
- the information processing apparatus 100 performs consensus building based on the recorded contents of the first BC, and selects transaction information commonly specified by a predetermined number or more of the first nodes 101 .
- the information processing device 100 transmits information indicating the selected transaction information to each of the second nodes 102 .
- Each second node 102 manages a second BC that records validated transaction information. Each second node 102 receives information indicating transaction information from the information processing device 100 . Each second node 102 generates a block containing information indicating the received transaction information and adds it to the second BC managed by the own node.
- the control system 110 can make it possible to reserve the operation of recording the transaction information in the second BC.
- the information processing device 100 intervenes between a first BC network and a second BC network, and presents transaction information to the second BC based on the scheduled time recorded in the first BC.
- the timing at which information is recorded can be controlled. Therefore, the information processing device 100 can cooperate with the first BC network and make it possible to reserve the operation of recording the transaction information in the second BC.
- the information processing device 100 can select transaction information specified by the first node 101 that satisfies a predetermined condition and record it in the second BC.
- the information processing apparatus 100 can select, for example, transaction information specified by a predetermined number or more of the first nodes 101 to be recorded in the second BC. Therefore, the information processing apparatus 100 can prevent the transaction information erroneously specified by any of the first nodes 101 from being recorded in the second BC, thereby improving security. be able to.
- information indicating transaction information may be identification information for identifying transaction information.
- the information indicating the transaction information may be feature values obtained from the transaction information.
- information indicating transaction information may be a hash value obtained from the transaction information.
- control system 110 (Example of control system 110) Next, an example of a control system 110 to which the information processing apparatus 100, the first BC network 201, and the second BC network 202 shown in FIG. 1 are applied will be described with reference to FIG.
- FIG. 2 is an explanatory diagram showing an example of the control system 110.
- the control system 110 includes an information processing device 100 , a first BC network 201 , a second BC network 202 and a client device 203 .
- a first BC network 201 is formed by a plurality of first nodes 101 .
- a second BC network 202 is formed by one or more second nodes 102 .
- the information processing device 100 and the first BC network 201 are connected via a wired or wireless network 210.
- the network 210 is, for example, a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, or the like.
- the information processing device 100 and the second BC network 202 are connected via the network 210 .
- the first BC network 201 and the client device 203 are connected via the network 210 .
- the information processing device 100 is a computer that can cooperate with the first BC network 201 and the second BC network 202 .
- the information processing apparatus 100 acquires the recorded content of the first BC 211 that records the scheduled time point for validating the transaction information.
- the scheduled point in time is the scheduled point in time at which transaction information relating to a certain transaction will be validated in response to the execution of the transaction.
- the information processing apparatus 100 performs consensus building based on the recorded contents of the first BC 211 and selects transaction information specified by the first node 101 that satisfies a predetermined condition.
- the information processing device 100 transmits information indicating the selected transaction information to each of the second nodes 102 .
- the information processing apparatus 100 is, for example, a server or a PC (Personal Computer).
- the first node 101 is a computer that manages the first BC 211.
- the first node 101 receives from the client device 203 the information indicating the transaction information and the scheduled time for validating the transaction information, and records it in the first BC 211 .
- Information indicating transaction information is, for example, the transaction information itself.
- the first node 101 identifies transaction information whose scheduled time has passed, based on the recorded contents of the first BC 211 managed by the own node.
- the first node 101 records, in the first BC 211, information indicating transaction information for which the identified scheduled time has passed.
- the processing of the first node 101 is realized by smart contract, for example.
- the first node 101 is, for example, a server or a PC.
- the second node 102 is a computer that manages the second BC 212 that records validated transaction information.
- the second node 102 receives information indicating transaction information from the information processing device 100 .
- the second node 102 records the information indicating the received transaction information in the second BC 212 managed by the own node.
- the second node 102 for example, generates a block containing information indicating the received transaction information, and adds it to the second BC 212 managed by its own node.
- the processing of the second node 102 is realized by smart contracts, for example.
- the second node 102 is, for example, a server or PC.
- the client device 203 is a computer used by a certain trader.
- the client device 203 transmits, to each first node 101, information indicating transaction information related to a certain transaction and a scheduled time point for validating the transaction information, based on an operation input by the executor.
- the client device 203 is, for example, a PC, tablet terminal, smart phone, wearable terminal, or the like.
- Control system 110 is applied, for example, to a decentralized financial system.
- the information processing device 100 may be one of the first nodes 101 in some cases.
- FIG. 3 is a block diagram showing a hardware configuration example of the information processing apparatus 100.
- the information processing apparatus 100 has a CPU (Central Processing Unit) 301 , a memory 302 , a network I/F (Interface) 303 , a recording medium I/F 304 and a recording medium 305 . Also, each component is connected by a bus 300 .
- the CPU 301 controls the entire information processing apparatus 100 .
- the memory 302 has, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), a flash ROM, and the like. Specifically, for example, a flash ROM or ROM stores various programs, and a RAM is used as a work area for the CPU 301 .
- a program stored in the memory 302 causes the CPU 301 to execute coded processing by being loaded into the CPU 301 .
- the network I/F 303 is connected to the network 210 through a communication line, and is connected to other computers via the network 210.
- a network I/F 303 serves as an internal interface with the network 210 and controls input/output of data from other computers.
- Network I/F 303 is, for example, a modem or a LAN adapter.
- the recording medium I/F 304 controls reading/writing of data from/to the recording medium 305 under the control of the CPU 301 .
- the recording medium I/F 304 is, for example, a disk drive, SSD (Solid State Drive), USB (Universal Serial Bus) port, or the like.
- a recording medium 305 is a nonvolatile memory that stores data written under control of the recording medium I/F 304 .
- the recording medium 305 is, for example, a disk, a semiconductor memory, a USB memory, or the like.
- the recording medium 305 may be removable from the information processing apparatus 100 .
- the information processing apparatus 100 may have, for example, a keyboard, mouse, display, printer, scanner, microphone, speaker, etc., in addition to the components described above. Further, the information processing apparatus 100 may have a plurality of recording medium I/Fs 304 and recording media 305 . Further, the information processing apparatus 100 may not have the recording medium I/F 304 and the recording medium 305 .
- FIG. 4 is a block diagram showing a hardware configuration example of the first node 101.
- the first node 101 has a CPU 401 , a memory 402 , a network I/F 403 , a recording medium I/F 404 and a recording medium 405 . Also, each component is connected by a bus 400 .
- the CPU 401 controls the entire first node 101 .
- the memory 402 has, for example, ROM, RAM and flash ROM. Specifically, for example, a flash ROM or ROM stores various programs, and a RAM is used as a work area for the CPU 401 .
- the program stored in the memory 402 causes the CPU 401 to execute coded processing by being loaded into the CPU 401 .
- the memory 402 specifically stores the smart contract 410 .
- the smart contract 410 manages the first BC 211 that records the scheduled time to activate the transaction information.
- the smart contract 410 receives from the client device 203 and records in the first BC 211 the information indicating the transaction information and the scheduled time to activate the transaction information.
- the smart contract 410 identifies transaction information whose scheduled time has passed based on the recorded contents of the first BC 211 managed by its own node, and records the identified result in the first BC 211 .
- the network I/F 403 is connected to the network 210 through a communication line, and is connected to other computers via the network 210.
- a network I/F 403 serves as an internal interface with the network 210 and controls input/output of data from other computers.
- Network I/F 403 is, for example, a modem or a LAN adapter.
- the recording medium I/F 404 controls reading/writing of data from/to the recording medium 405 under the control of the CPU 401 .
- a recording medium I/F 404 is, for example, a disk drive, an SSD, a USB port, or the like.
- a recording medium 405 is a nonvolatile memory that stores data written under the control of the recording medium I/F 404 .
- the recording medium 405 stores, for example, the first BC 211 .
- the first BC 211 stores, for example, schedule transaction management information 500, which will be described later with reference to FIG.
- the recording medium 405 is, for example, a disk, a semiconductor memory, a USB memory, or the like.
- the recording medium 405 may be removable from the first node 101 .
- the first node 101 may have, for example, a keyboard, mouse, display, printer, scanner, microphone, speaker, and the like. Also, the first node 101 may have a plurality of recording medium I/Fs 404 and recording media 405 . Also, the first node 101 may not have the recording medium I/F 404 and the recording medium 405 .
- Scheduled transaction management information 500 is implemented by, for example, a storage area such as memory 402 or recording medium 405 of information processing apparatus 100 shown in FIG.
- FIG. 5 is an explanatory diagram showing an example of the contents of the schedule transaction management information 500.
- the schedule transaction management information 500 has fields for an escrow transaction ref, schedule transaction details, schedule time, whether execution can be canceled, and schedule execution conditions.
- a scheduled trade is a trade that is scheduled to execute.
- the escrow transaction ref field contains identification information that identifies the escrow transaction referenced in the schedule transaction.
- An escrow transaction is, for example, a transaction in which money handled in a schedule transaction is deposited with a third party in advance.
- the content of the schedule transaction to be executed with reference to the content of the escrow transaction is set in the content of schedule transaction field.
- the content of the schedule transaction indicates, for example, the content of the transaction for sending money, and specifically indicates the amount to be transferred and the destination to which the money for the transfer amount is to be sent.
- the scheduled time for executing the above schedule transaction is set in the Schedule Time field.
- Information indicating whether or not execution of the schedule transaction can be canceled is set in the execution cancelability field.
- a condition for executing the schedule transaction is set in the schedule execution condition field. The condition is, for example, that a predetermined number or more of the first nodes 101 determine that the scheduled time has passed. The above conditions may be different for each scheduled transaction.
- FIG. 6 is a block diagram showing a hardware configuration example of the second node 102.
- the second node 102 has a CPU 601 , memory 602 , network I/F 603 , recording medium I/F 604 and recording medium 605 . Also, each component is connected by a bus 600 .
- the CPU 601 controls the entire second node 102 .
- the memory 602 has, for example, ROM, RAM and flash ROM. Specifically, for example, a flash ROM or ROM stores various programs, and a RAM is used as a work area for the CPU 601 .
- a program stored in the memory 602 causes the CPU 601 to execute coded processing by being loaded into the CPU 601 .
- the memory 602 specifically stores a smart contract 610.
- Smart contract 610 manages a second BC 212 that records validated transaction information.
- the smart contract 610 receives information indicating transaction information from the information processing device 100 .
- the smart contract 610 generates a block containing information indicating the received transaction information and adds it to the second BC 212 managed by its own node.
- the network I/F 603 is connected to the network 210 through a communication line, and is connected to other computers via the network 210.
- a network I/F 603 serves as an internal interface with the network 210 and controls input/output of data from other computers.
- the network I/F 603 is, for example, a modem or LAN adapter.
- a recording medium I/F 604 controls reading/writing of data from/to the recording medium 605 under the control of the CPU 601 .
- a recording medium I/F 604 is, for example, a disk drive, an SSD, a USB port, or the like.
- a recording medium 605 is a nonvolatile memory that stores data written under control of the recording medium I/F 604 .
- the recording medium 605 stores, for example, the second BC 212 .
- the recording medium 605 is, for example, a disk, semiconductor memory, USB memory, or the like.
- the recording medium 605 may be removable from the second node 102 .
- the second node 102 may have, for example, a keyboard, mouse, display, printer, scanner, microphone, speaker, and the like. Also, the second node 102 may have a plurality of recording medium I/Fs 604 and recording media 605 . Also, the second node 102 may not have the recording medium I/F 604 and the recording medium 605 .
- FIG. 7 is a block diagram showing a functional configuration example of the control system 110.
- a control system 110 includes a plurality of first nodes 101 forming a first BC network 201, one or more second nodes 102 forming a second BC network 202, an information processing device 100 including.
- the first node 101 includes a first storage unit 700 , a first acquisition unit 701 , a first recording unit 702 , an identification unit 703 and a first output unit 704 .
- the first storage unit 700 is implemented by, for example, a storage area such as the memory 402 or the recording medium 405 shown in FIG. Although a case where the first storage unit 700 is included in the first node 101 will be described below, the present invention is not limited to this.
- the first storage unit 700 may be included in a device different from the first node 101 and the storage contents of the first storage unit 700 may be referenced from the first node 101 .
- the first acquisition unit 701 to first output unit 704 function as an example of a control unit. Specifically, the first acquisition unit 701 to the first output unit 704, for example, cause 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.
- the network I/F 403 implements that function.
- the processing result of each functional unit is stored in a storage area such as the memory 402 or recording medium 405 shown in FIG. 4, for example.
- the first storage unit 700 stores various information that is referred to or updated in the processing of each functional unit.
- the first storage unit 700 stores a first BC 211 that records a scheduled point in time for validating transaction information.
- Transaction information is, for example, information indicating the content of a certain transaction.
- Transactions are, for example, deposits or remittances.
- Activation is, for example, activating transaction information.
- Validation corresponds to, for example, executing a transaction indicated by the transaction information.
- the scheduled time is represented, for example, by the time format.
- a scheduled point in time is represented, for example, by an addition point in time at which a given block is added to the first BC 211 .
- the predetermined block is, for example, the Nth block from the top of the first BC 211 .
- the additional time points are represented by the block number N, for example.
- the first BC 211 is formed, for example, by concatenating blocks that record scheduled time points for validating transaction information. Specifically, the first BC 211 is formed by linking blocks that record information indicating transaction information and a scheduled time point for validating the transaction information in association with each other. The block may, for example, also record information indicating transaction information past the scheduled time.
- a predetermined condition is, for example, a predetermined number of nodes. The predetermined condition may be variable for each transaction information. The predetermined condition may include a node's long participation time in the BC network. The predetermined condition may include that the reliability of the node is high.
- the first storage unit 700 also stores a smart contract that records the scheduled time of transaction information in the first BC 211.
- the first storage unit 700 also stores a smart contract that specifies transaction information whose scheduled time has passed.
- the first acquisition unit 701 acquires various types of information used for processing of each functional unit.
- the first acquisition unit 701 stores the acquired various information in the first storage unit 700 or outputs the information to each functional unit. Further, the first acquisition unit 701 may output various information stored in the first storage unit 700 to each functional unit.
- the first acquisition unit 701 acquires various types of information, for example, based on user's operation input.
- the first acquisition unit 701 may receive various types of information from a device different from the first node 101, for example.
- the first acquisition unit 701 accepts a recording request to record the scheduled point in time for validating any transaction information.
- the record request includes, for example, information indicating any transaction information to be validated and the scheduled time at which the transaction information is validated.
- the first acquisition unit 701 accepts the recording request by, for example, receiving the recording request from the client device 203 .
- the first acquisition unit 701 acquires a cancellation request for canceling the scheduled point in time for validating any transaction information.
- the cancellation request includes, for example, information indicating any transaction information that cancels the scheduled time.
- the first acquisition unit 701 accepts a cancellation request by, for example, receiving the cancellation request from the client device 203 .
- the first acquisition unit 701 may accept a start trigger for starting processing of any of the functional units.
- the start trigger is, for example, that there is a predetermined operation input by the user.
- the start trigger may be, for example, reception of predetermined information from another computer.
- the start trigger may be, for example, the output of predetermined information by any of the functional units.
- the first acquisition unit 701 accepts, for example, reception of a recording request or cancellation request as a start trigger for starting the processing of the first recording unit 702 .
- the first acquisition unit 701 receives, for example, that the first recording unit 702 has updated the first BC 211 as a start trigger for starting the processing of the identification unit 703 .
- the first acquisition unit 701 receives, for example, the occurrence of a predetermined signal that occurs periodically as a start trigger for starting the processing of the identification unit 703 .
- the first recording unit 702 manages the first BC 211. For example, when receiving a recording request, the first recording unit 702 records the scheduled time point for validating any transaction information in the first BC 211 . Specifically, the first recording unit 702 generates a block containing information indicating any transaction information to be validated and correspondence information associated with the scheduled time point at which the transaction information is to be validated, Add to the first BC 211 . Generation may be performed by a computer other than the first node 101 by requesting that computer. Thereby, the first recording unit 702 can appropriately update the first BC 211 and manage the first BC 211 .
- the first recording unit 702 when a cancellation request is received, the first recording unit 702 records cancellation information indicating that the scheduled time for activating any transaction information is to be canceled in the first BC 211 . Specifically, the first recording unit 702 generates a block including cancellation information indicating cancellation of the scheduled time to validate any transaction information, and adds it to the first BC 211 . As a result, the first recording unit 702 can cancel the scheduled time of activation of the transaction information without deleting the scheduled time of activation of the transaction information itself from the first BC 211, thereby improving convenience. can be planned.
- the first recording unit 702 For example, if the first recording unit 702 does not receive a recording request for a certain period of time, it records the scheduled time point for activating the dummy transaction information in the first BC 211 . Specifically, the first recording unit 702 generates a block including the scheduled time point for validating the dummy transaction information, and adds it to the first BC 211 . As a result, the first recording unit 702 can generate a start trigger for starting the processing of the specifying unit 703 without receiving a recording request.
- the identifying unit 703 identifies transaction information whose scheduled time has passed based on the recorded contents of the first BC 211 .
- the processing of the identifying unit 703 is implemented using, for example, a smart contract. For example, each time a certain number of new blocks are added to the first BC 211 , the identifying unit 703 identifies transaction information whose scheduled time has passed, based on the recorded contents of the first BC 211 .
- the certain number is, for example, 1 or a number of 2 or more. As a result, if the constant number is 1, the specifying unit 703 can suppress a delay from a certain scheduled time until it is determined that the scheduled time has passed.
- the identification unit 703 can reduce the amount of processing if the fixed number is 2 or more.
- the identifying unit 703 identifies, for example, based on the recorded contents of the first BC 211, transaction information whose scheduled time has passed, other than any transaction information whose scheduled time has been cancelled. Specifically, each time a certain number of new blocks are added to the first BC 211, the identifying unit 703 detects any transaction information whose scheduled time point has been canceled based on the recorded contents of the first BC 211. Other than that, the transaction information whose scheduled time has passed is specified. As a result, the identification unit 703 can exclude any transaction information whose scheduled time has been cancelled, and can appropriately identify transaction information whose scheduled time has passed.
- the specifying unit 703 records the specified result in the first BC 211.
- the identifying unit 703 records information indicating the transaction information identified by the identifying unit 703 in the first BC 211, for example. Accordingly, the identifying unit 703 can allow the information processing apparatus 100 to refer to information indicating transaction information identified by the first node 101 that satisfies a predetermined condition.
- the first output unit 704 outputs the processing result of at least one of the functional units.
- the output format is, for example, display on a display, print output to 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 recording medium 405. This enables the first output unit 704 to notify the user of the processing result of at least one of the functional units, thereby improving the convenience of the first node 101 .
- the first output unit 704 outputs the recorded contents of the first BC 211, for example. Specifically, the first output unit 704 transmits the recorded content of the first BC 211 to the information processing apparatus 100 . This allows the first output unit 704 to allow the information processing apparatus 100 to grasp the content recorded in the first BC 211 .
- the second node 102 includes a second storage unit 710 , a second acquisition unit 711 , a second recording unit 712 and a second output unit 713 .
- the second storage unit 710 is implemented by, for example, a storage area such as the memory 602 or recording medium 605 shown in FIG. Although a case where the second storage unit 710 is included in the second node 102 will be described below, the present invention is not limited to this.
- the second storage unit 710 may be included in a device different from the second node 102 and the storage contents of the second storage unit 710 may be referenced from the second node 102 .
- the second acquisition unit 711 to second output unit 713 function as an example of a control unit. Specifically, for example, the second acquisition unit 711 to the second output unit 713 cause the CPU 601 to execute a program stored in a storage area such as the memory 602 or the recording medium 605 shown in FIG. 6, or The network I/F 603 realizes that function. The processing result of each functional unit is stored in a storage area such as the memory 602 or recording medium 605 shown in FIG. 6, for example.
- the second storage unit 710 stores various information that is referred to or updated in the processing of each functional unit.
- the second storage unit 710 stores a second BC 212 that records validated transaction information.
- the second BC 212 is formed, for example, by concatenating blocks that record validated transaction information.
- the second storage unit 710 also stores a smart contract that records activated transaction information in the second BC 212 .
- the second acquisition unit 711 acquires various information used for processing of each functional unit.
- the second acquisition unit 711 stores the acquired various information in the second storage unit 710 or outputs the acquired information to each functional unit. Further, the second acquisition unit 711 may output various information stored in the second storage unit 710 to each functional unit.
- the second acquisition unit 711 acquires various types of information, for example, based on the user's operation input.
- the second acquisition unit 711 may receive various types of information from a device other than the second node 102, for example.
- the second acquisition unit 711 receives, for example, validated transaction information from the information processing device 100 .
- the second acquisition unit 711 may receive, for example, information indicating activated transaction information from the information processing device 100 .
- the second acquisition unit 711 may accept a start trigger to start processing of any of the functional units.
- the start trigger is, for example, that there is a predetermined operation input by the user.
- the start trigger may be, for example, reception of predetermined information from another computer.
- the start trigger may be, for example, the output of predetermined information by any of the functional units.
- the second acquisition unit 711 receives, for example, the reception of validated transaction information as a start trigger for starting the processing of the second recording unit 712 .
- the second acquisition unit 711 receives, for example, reception of information indicating activated transaction information as a start trigger for starting the processing of the second recording unit 712 .
- the second recording unit 712 manages the second BC 212 that records validated transaction information.
- the 2nd recording part 712 produces
- the second recording unit 712 for example, generates a block containing information indicating the received transaction information and adds it to the second BC 212 .
- the second recording unit 712 acquires the transaction information based on the information indicating the received transaction information, generates a block including the acquired transaction information, and adds the block to the second BC 212 . Thereby, the second recording unit 712 can appropriately update the second BC 212 .
- the second output unit 713 outputs the processing result of at least one of the functional units.
- the output format is, for example, display on a display, print output to a printer, transmission to an external device via the network I/F 603, or storage in a storage area such as the memory 602 or recording medium 605. Thereby, the second output unit 713 can notify the user of the processing result of at least one of the functional units, and the convenience of the second node 102 can be improved.
- the second output unit 713 outputs the recorded content of the second BC 212, for example.
- the information processing apparatus 100 includes a third storage section 720 , a third acquisition section 721 , a selection section 722 and a third output section 723 .
- the third storage unit 720 is implemented by, for example, a storage area such as the memory 602 or recording medium 605 shown in FIG. Although a case where the third storage unit 720 is included in the information processing apparatus 100 will be described below, the present invention is not limited to this.
- the third storage unit 720 may be included in a device different from the information processing device 100 , and the information stored in the third storage unit 720 may be referenced from the information processing device 100 .
- the third acquisition unit 721 to third output unit 723 function as an example of a control unit. Specifically, for example, the third acquisition unit 721 to the third output unit 723 cause the CPU 601 to execute a program stored in a storage area such as the memory 602 or the recording medium 605 shown in FIG. 6, or The network I/F 603 realizes that function. The processing result of each functional unit is stored in a storage area such as the memory 602 or recording medium 605 shown in FIG. 6, for example.
- the third storage unit 720 stores various information that is referred to or updated in the processing of each functional unit.
- the third storage unit 720 stores the recorded contents of the first BC 211 .
- the third storage unit 720 stores, for example, the recorded contents of the first BC 211 in which information indicating transaction information specified by the first node 101 is recorded.
- the third acquisition unit 721 acquires various information used for processing of each functional unit.
- the third acquisition unit 721 stores the acquired various information in the third storage unit 720 or outputs the information to each functional unit. Further, the third acquisition unit 721 may output various information stored in the third storage unit 720 to each functional unit.
- the third acquisition unit 721 acquires various types of information, for example, based on user's operation input.
- the third acquisition unit 721 may receive various types of information from a device different from the information processing device 100, for example.
- the third acquisition unit 721 acquires the recorded content of the first BC 211, for example. Specifically, the third acquisition unit 721 receives the recorded content of the first BC 211 from each first node 101 .
- the third acquisition unit 721 may accept a start trigger for starting processing of any functional unit.
- the start trigger is, for example, that there is a predetermined operation input by the user.
- the start trigger may be, for example, reception of predetermined information from another computer.
- the start trigger may be, for example, the output of predetermined information by any of the functional units.
- the third acquisition unit 721 receives, for example, acquisition of the recorded content of the first BC 211 as a start trigger for starting the processing of the selection unit 722 .
- the selection unit 722 performs consensus building based on the recorded contents of the first BC 211, and selects the transaction information specified by the first node 101 that satisfies a predetermined condition among the plurality of first nodes 101. For example, the selection unit 722 forms a consensus based on the recorded contents of the first BC 211, and selects a transaction that is commonly specified by a predetermined number or more of the first nodes 101 among the plurality of first nodes 101. Select information. As a result, the selection unit 722 is non-centralized and can select transaction information whose scheduled time has passed, thereby improving security.
- the specifying unit 703 specifically selects the transaction information specified by the first node 101 having a predetermined attribute among the plurality of first nodes 101 based on the recorded contents of the first BC 211. You may Further, the identifying unit 703 specifically, based on the recorded contents of the first BC 211, the transaction information identified by the first node 101 that satisfies a predetermined condition among the plurality of first nodes 101 is Furthermore, it may be determined whether or not conditions for execution are satisfied. Then, the identifying unit 703 may select transaction information that satisfies execution conditions.
- the third output unit 723 outputs the processing result of at least one of the functional units.
- the output format is, for example, display on a display, print output to a printer, transmission to an external device via the network I/F 603, or storage in a storage area such as the memory 602 or recording medium 605. Thereby, the third output unit 723 can notify the user of the processing result of at least one of the functional units, and the convenience of the information processing apparatus 100 can be improved.
- the third output unit 723 transmits information indicating the transaction information selected by the selection unit 722 to each second node 102 . This allows the third output unit 723 to update the second BC 212 .
- FIG. 8 to 11 are explanatory diagrams showing an example of the operation of the control system 110.
- FIG. 8-1) the client device 203 transmits escrow transaction information related to an escrow transaction for depositing funds to the transaction execution BC network based on the user's operation input.
- the client device 203 for example, transmits escrow transaction information related to an escrow transaction in which funds are deposited to each recording node 802 forming the transaction execution BC network.
- Each record node 802 creates a block containing the received escrow transaction information and adds it to the transaction execution BC 820 at a predetermined timing.
- Any recording node 802 transmits the escrow transaction information recorded in the block added to the transaction execution BC 820 to the schedule management BC network.
- Any recording node 802 may, for example, send escrow transaction information recorded in blocks added to the transaction execution BC 820 to respective approval nodes 801 forming the schedule management BC network.
- Any recording node 802 distributes the escrow transaction information from the approval node 801 to other approval nodes 801 by transmitting the escrow transaction information to any approval node 801 forming the schedule management BC network, for example. You may let
- the client device 203 requests registration of the scheduled time for validating the scheduled transaction information indicating the details of the scheduled transaction to be executed with reference to the details of the escrow transaction. Send to network.
- the registration request includes, for example, the scheduled transaction information and the scheduled time for activation of the scheduled transaction information.
- the registration request may, for example, further include identification information identifying the escrow transaction information.
- the registration request specifically includes schedule transaction management information 500 .
- the client device 203 transmits a registration request to each approval node 801 forming the schedule management BC network.
- the client device 203 may, for example, transmit the registration request to any of the approval nodes 801 forming the schedule management BC network, thereby distributing the registration request from the approval node 801 to other approval nodes 801. good.
- Each approval node 801 generates, at a predetermined timing, a block containing schedule transaction information corresponding to the received registration request and the scheduled time for validating the schedule transaction information, and records it in the schedule management BC 810.
- Each approval node 801, for example, at a predetermined timing generates a block containing the schedule transaction management information 500 corresponding to the received registration request, and records it in the schedule management BC810. This allows each approval node 801 to store the plan 800 for activating each schedule transaction information as a local database. Next, the description of FIG. 9 will be described.
- the client device 203 transmits a cancellation request for canceling the scheduled time for validating the schedule transaction information to the schedule management BC network based on the user's operation input.
- the cancellation request includes, for example, identification information identifying the scheduled transaction information whose scheduled time is to be canceled.
- the client device 203 transmits a cancellation request to each approval node 801 forming the schedule management BC network.
- the client device 203 may, for example, transmit the cancellation request to any of the approval nodes 801 forming the schedule management BC network, thereby distributing the cancellation request from the approval node 801 to other approval nodes 801. good.
- Each approval node 801 generates, at a predetermined timing, a block containing identification information identifying schedule transaction information whose scheduled time is to be canceled, corresponding to the received cancellation request, and records it in the schedule management BC 810. As a result, each approval node 801 can cancel the scheduled time for validating the scheduled transaction information without deleting the scheduled time itself from the schedule management BC 810, thereby improving convenience.
- FIG. 10 the description of FIG. 10 will be described.
- each approval node 801 generates a block containing dummy transaction information and records it in the schedule management BC 810 when it does not receive a registration request for a certain period of time.
- each approval node 801 can generate a trigger for determining whether or not there is any scheduled transaction information that has passed the scheduled time, and can identify the scheduled transaction information that has passed the scheduled time at an appropriate timing. can be made possible.
- FIG. 11 will be described.
- each approval node 801 refers to the recorded contents of the schedule management BC 810 each time a block is generated a certain number of times to identify schedule transaction information whose scheduled time has passed. The fixed number of times is, for example, one time.
- Each approval node 801 generates approval information indicating approval for activating the specified schedule transaction information because the scheduled time for validating the specified schedule transaction information has passed, and records it in the schedule management BC 810. .
- Approval information includes, for example, a signature indicating approval for activating schedule transaction information. Approval corresponds to approval to execute the scheduled transaction associated with the scheduled transaction information.
- Authorization information includes, for example, the specified scheduled transaction information and a signature indicating authorization to validate the scheduled transaction information.
- Each approval node 801 determines whether or not the scheduled time for activating each schedule transaction information recorded in the generated block has passed. Also, each approval node 801 determines whether or not the scheduled time for activating each scheduled transaction information recorded in other blocks before the generated block has passed. Each approval node 801, for example, identifies scheduled transaction information whose scheduled time has passed, based on the determination result. Each approval node 801, for example, generates approval information based on the specified result and records it in the schedule management BC810.
- the information processing device 100 receives the schedule management BC 810 from each approval node 801 .
- the information processing apparatus 100 builds a consensus based on the received approval information recorded in the schedule management BC 810, and selects schedule transaction information whose activation is approved by a certain number of approval nodes 801 or more. .
- the selected schedule transaction information is transmitted to the recording node 802, and the funds corresponding to the predetermined remittance amount deposited by the escrow transaction specified by the escrow transaction ref included in the schedule transaction information are transferred to the set destination. You will realize a schedule transaction that will be sent to. In addition, when the scheduled time to be activated is canceled and the schedule transaction information is not selected, the schedule transaction for transmitting the funds of the prescribed remittance amount deposited by the escrow transaction to the set destination is not executed. At this time, the deposit by escrow transaction may also be canceled.
- the information processing device 100 transmits the selected schedule transaction information to the transaction execution BC network.
- the information processing apparatus 100 for example, transmits the selected scheduled transaction information to each recording node 802 forming the transaction execution BC network.
- Each recording node 802 generates a block containing the received schedule trade information and adds it to the trade execution BC 820 at predetermined times. This allows the control system 110 to schedule the act of activating the scheduled trade information.
- control system 110 (Specific example of operation of control system 110) Next, a specific example of the operation of the control system 110 will be described with reference to FIGS. 12 to 15. FIG.
- FIG. 12 to 15 are explanatory diagrams showing specific examples of the operation of the control system 110.
- the approval node 801 has reception means 1201 , recording means 1202 and determination means 1203 .
- the information processing apparatus 100 has issuing means 1204 .
- the approval node 801 stores a schedule management BC 810. Also, the approval node 801 stores a schedule management ledger for managing scheduled times for validating schedule transaction information based on the schedule management BC 810 .
- the schedule management ledger is stored, for example, as a local database.
- the schedule management ledger shows, for example, schedule transaction information to be activated at each scheduled time in association with each scheduled time.
- the schedule management ledger may identifiably indicate activated schedule transaction information.
- the approval node 801 generates blocks to be added to the schedule management BC 810 every 10 minutes.
- Accepting means 1201 accepts a registration request including a scheduled time for validating the scheduled transaction information.
- the registration request includes schedule transaction management information 500 .
- the receiving means 1201 includes the schedule transaction management information 500 included in each registration request received during the last 10 minutes in the block to be added to the schedule management BC 810 each time a block is generated.
- the determining means 1203 identifies schedule transaction information whose scheduled time has passed based on the schedule management ledger each time a block is generated.
- the determining means 1203 generates approval information including a signature indicating approval for activating the specified schedule transaction information, and generates an activation transaction list including the specified schedule transaction information and the generated approval information in association with each other. do.
- the determination means 1203 includes the generated activation transaction list in the block added to the schedule management BC810. Approval node 801 adds the generated block to schedule management BC 810 .
- the recording means 1202 updates the schedule management ledger based on the recorded contents of the schedule management BC 810 each time a block is generated.
- the recording means 1202 identifies schedule transaction information that has not yet been validated based on the schedule transaction management information 500 recorded in the block added to the schedule management BC810.
- the recording unit 1202 associates the identified scheduled transaction information that has not yet been validated with the scheduled time for activating the scheduled transaction information, and registers them in the schedule management ledger.
- the approval node 801 transmits the activation transaction list recorded in the block added to the schedule management BC 810 to the information processing device 100 .
- Issuing means 1204 receives the activation transaction list recorded in the block added to schedule management BC810.
- the issuing means 1204 builds a consensus based on the received activation transaction list, and selects scheduled transaction information that has passed the scheduled time and is commonly identified by a predetermined number or more of approval nodes 801 .
- the issuing means 1204 transmits the selected scheduled transaction information to each record node 802 forming the transaction execution BC network. For example, the issuing means 1204 may further determine whether or not the schedule execution condition corresponding to the selected schedule transaction information is satisfied. Then, the issuing means 1204 transmits the selected scheduled transaction information to each of the record nodes 802 forming the transaction execution BC network, for example, when the conditions for schedule execution are satisfied.
- Each record node 802 records the received schedule transaction information in the transaction execution BC 820. This allows the control system 110 to make it possible to reserve the operation of recording the schedule transaction information in the transaction execution BC 820, thereby improving convenience. Next, the description of FIG. 13 will be described.
- receiving means 1201 receives a cancellation request for canceling the scheduled time for validating the scheduled transaction information.
- the cancellation request includes schedule cancellation information that identifiably indicates the scheduled transaction information to be canceled.
- the receiving unit 1201 includes schedule cancellation information included in each cancellation request received during the last 10 minutes in the block to be added to the schedule management BC 810 each time a block is generated.
- the recording means 1202 updates the schedule management ledger based on the recorded contents of the schedule management BC 810 each time a block is generated.
- the recording means 1202 acquires the schedule transaction management information 500 recorded in the block added to the schedule management BC810. Based on the acquired scheduled transaction management information 500, the recording means 1202 associates the scheduled transaction information that has not yet been validated with the scheduled time for activating the scheduled transaction information, and registers them in the schedule management ledger.
- the recording means 1202 acquires the schedule cancellation information recorded in the block added to the schedule management BC810. Recording means 1202 cancels the scheduled time registered in the schedule management ledger based on the schedule cancellation information. As a result, the control system 110 can cancel the scheduled time after the fact, thereby improving convenience. Next, the description of FIG. 14 will be described.
- the receiving means 1201 includes dummy transaction management information in the block to be added to the schedule management BC 810 if no registration request has been received in the last 10 minutes when the block is generated.
- the control system 110 can execute the processing of the recording means 1202 and the determination means 1203 without receiving a registration request.
- the client device 203 transmits the schedule transaction management information 500 to each approval node 801 forming the schedule management BC network.
- Approval node 801 uses transaction monitoring SC 1501 to add a block including schedule transaction management information 500 to schedule management BC 810 .
- the approval node 801 uses the transaction monitoring SC 1501 to update the schedule management ledger based on the blocks added to the schedule management BC 810 .
- the approval node 801 uses the schedule monitoring SC 1502 to identify schedule transaction information whose scheduled time has passed based on the schedule management ledger.
- the approval node 801 uses the schedule monitoring SC 1502 to generate approval information by associating a scheduled transaction ID that identifies scheduled transaction information whose scheduled time has passed with a signature indicating approval for activating the scheduled transaction information. do.
- the approval node 801 uses the schedule monitoring SC 1502 to record the generated approval information in the schedule management BC 810 .
- the information processing apparatus 100 uses the schedule transaction execution SC 1503 to acquire the recorded contents of the schedule management BC 810.
- the information processing apparatus 100 uses the scheduled transaction execution SC 1503 to select scheduled transaction information that has passed the scheduled time determined to be appropriate through consensus building.
- the information processing apparatus 100 uses the scheduled transaction execution SC 1503, for example, to process the scheduled transaction information that has passed the scheduled time and that has been approved for activation by a certain number or more of the approval nodes 801 as appropriate for consensus building. I judge.
- the information processing apparatus 100 uses the scheduled transaction execution SC 1503 to transmit the selected scheduled transaction information to each recording node 802 forming the transaction execution BC network.
- the scheduled transaction information includes, for example, the contents of the scheduled transaction for remittance from the deposit account to the destination and a signature for transaction approval. This allows the control system 110 to enable scheduling of recording schedule trade information to the trade execution BC 820 .
- the overall processing 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.
- FIG. 16 is a flowchart showing an example of the overall processing procedure.
- the approval node 801 receives data (step S1601).
- Approval node 801 determines whether the received data is transaction request data requesting recording of the scheduled time of activation of the scheduled transaction information (step S1602).
- step S1602 if it is not transaction request data (step S1602: No), the approval node 801 proceeds to the process of step S1604. On the other hand, if it is transaction request data (step S1602: Yes), the approval node 801 proceeds to the process of step S1603.
- the approval node 801 replies whether or not to approve the transaction, which indicates whether to approve the schedule transaction (step S1603). If the approval node 801 approves the schedule transaction, it records the schedule transaction information in the schedule management BC 810 . The approval node 801 then returns to the process of step S1601.
- step S1604 the approval node 801 determines whether the received data is block data (step S1604). Here, if it is not block data (step S1604: No), the approval node 801 proceeds to the process of step S1608. On the other hand, if it is block data (step S1604: Yes), the approval node 801 proceeds to the process of step S1605.
- step S1605 the approval node 801 updates the internal state based on the schedule transaction information in the block data (step S1605).
- the internal state is the schedule management ledger.
- step S1606 determines whether or not the block number is to be executed. Here, if it is not an execution target (step S1606: No), the approval node 801 returns to the process of step S1601. On the other hand, if it is to be executed (step S1606: Yes), the approval node 801 proceeds to the process of step S1607.
- the approval node 801 updates the activation transaction list and distributes it by P2P (step S1607).
- the approval node 801 causes the information processing apparatus 100 to identify scheduled transaction information approved to be activated by a predetermined number or more of the approval nodes 801 from the distributed activation transaction list.
- the approval node 801 then returns to the process of step S1601.
- step S1608 the approval node 801 discards the received data (step S1608).
- the approval node 801 then returns to the process of step S1601. This allows the approval node 801 to be able to schedule the action of validating the scheduled transaction information.
- each first node 101 can manage the first BC that records the scheduled time of transaction information validation.
- the transaction information that has passed the scheduled time is specified, and the specified result is managed by the first node managed by the own node.
- BC can be recorded.
- the information processing apparatus 100 based on the recorded content of the first BC, the transaction information specified by the first node 101 that satisfies a predetermined condition among the plurality of first nodes 101 is transferred to each second can be sent to the node 102 of
- Each second node 102 may manage a second BC that records validated transaction information.
- Each second node 102 can generate a block containing the received transaction information and add it to the second BC managed by the own node. This allows the control system 110 to be able to schedule the act of recording the transaction information to the second BC.
- the transaction information commonly specified by a predetermined number or more of the plurality of first nodes 101 is stored in each of the second It can be sent to node 102 .
- the control system 110 can record the transaction information in the second BC when a consensus is formed on the transaction information after the scheduled time, thereby improving security.
- Each first node 101 can accept a cancellation request that cancels the scheduled time to activate any transaction information. According to each first node 101, when receiving a cancellation request, it generates a block containing cancellation information indicating that the scheduled time for activating any transaction information is to be cancelled, and manages the first node 101 in its own node. can be added to the BC of According to each first node 101, based on the recorded contents of the first BC managed by the own node, other than any transaction information, transaction information whose scheduled time has passed is specified, and the specified result is It can be recorded in the first BC managed by its own node. As a result, the control system 110 can cancel the scheduled time without deleting the scheduled time itself from the first BC, thereby improving convenience.
- each first node 101 upon receiving a recording request to record a scheduled time to validate any transaction information, generate a block containing a scheduled time to validate any transaction information, It can be added to the first BC managed by its own node. This allows the control system 110 to update the first BC to the latest state.
- each first node 101 each time a certain number of new blocks are added to the first BC managed by its own node, based on the recorded contents of the first BC managed by its own node, Transaction information that has passed the scheduled time can be identified.
- Each first node 101 can record the specified result in the first BC managed by the own node. As a result, the control system 110 can identify transaction information that has passed the scheduled time appropriately at a predetermined timing.
- the fixed number can be a number of 2 or more.
- the control system 110 can reduce the amount of processing.
- each first node 101 if no recording request is received for a certain period of time, a block containing a scheduled time point for activating dummy transaction information is generated and added to the first BC managed by its own node. can do.
- This allows the control system 110 to update the first BC without receiving a recording request. As such, the control system 110 can enable consensus building for outdated transaction information.
- Each first node 101 may have a smart contract specifying transaction information specified by the first node 101 that satisfies a predetermined condition.
- Each of the first nodes 101 can identify the transaction information past the scheduled point in time based on the recorded contents of the first BC managed by the node using the smart contract. According to each first node 101, if the transaction information is transaction information specified by the first node 101 that satisfies a predetermined condition, the first BC that manages the transaction information at its own node. can be recorded in As a result, the control system 110 can easily implement various processes using smart contracts.
- the scheduled point in time can be expressed as the point in time of adding a given block to the first BC.
- the control system 110 can express the scheduled point in time other than the time, and can improve the convenience.
- control method described in the present embodiment can be realized by executing a prepared program on a computer such as a PC or workstation.
- the control program described in the present embodiment is recorded in a computer-readable recording medium and executed by being read from the recording medium by a computer.
- Recording media include a hard disk, flexible disk, CD (Compact Disc)-ROM, MO (Magneto Optical disc), DVD (Digital Versatile Disc), and the like.
- the control program described in this embodiment may be distributed via a network such as the Internet.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Computer Security & Cryptography (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Human Resources & Organizations (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
図1は、実施の形態にかかる制御方法の一実施例を示す説明図である。情報処理装置100は、ブロックチェーンネットワークと連携可能な、取引情報をブロックチェーンに記録する動作を予約可能にするためのコンピュータである。以下の説明では、ブロックチェーンを「BC(Block Chain)」と表記する場合がある。
次に、図2を用いて、図1に示した情報処理装置100と、第1のBCネットワーク201と、第2のBCネットワーク202とを適用した、制御システム110の一例について説明する。
次に、図3を用いて、情報処理装置100のハードウェア構成例について説明する。
次に、図4を用いて、第1のノード101のハードウェア構成例について説明する。
次に、図5を用いて、スケジュール取引管理情報500の記憶内容の一例について説明する。スケジュール取引管理情報500は、例えば、図4に示した情報処理装置100のメモリ402や記録媒体405などの記憶領域により実現される。
次に、図6を用いて、第2のノード102のハードウェア構成例について説明する。
次に、図7を用いて、制御システム110の機能的構成例について説明する。
次に、図8~図11を用いて、制御システム110の動作の一例について説明する。
次に、図12~図15を用いて、制御システム110の動作の具体例について説明する。
次に、図16を用いて、承認ノード801が実行する、全体処理手順の一例について説明する。全体処理は、例えば、図4に示したCPU401と、メモリ402や記録媒体405などの記憶領域と、ネットワークI/F403とによって実現される。
101 第1のノード
102 第2のノード
110 制御システム
201 第1のBCネットワーク
202 第2のBCネットワーク
203 クライアント装置
210 ネットワーク
211 第1のBC
212 第2のBC
300,400,600 バス
301,401,601 CPU
302,402,602 メモリ
303,403,603 ネットワークI/F
304,404,604 記録媒体I/F
305,405,605 記録媒体
410,610 スマートコントラクト
500 スケジュール取引管理情報
700 第1記憶部
701 第1取得部
702 第1記録部
703 特定部
704 第1出力部
710 第2記憶部
711 第2取得部
712 第2記録部
713 第2出力部
720 第3記憶部
721 第3取得部
722 選択部
723 第3出力部
800 計画
801 承認ノード
802 記録ノード
810 スケジュール管理BC
820 取引実行BC
1201 受付手段
1202 記録手段
1203 判定手段
1204 発行手段
1501 取引監視SC
1502 スケジュール監視SC
1503 スケジュール取引実行SC
Claims (12)
- 第1のブロックチェーンネットワークを形成する複数のノードと、
第2のブロックチェーンネットワークを形成する1以上のノードと、
前記第1のブロックチェーンネットワーク、および、前記第2のブロックチェーンネットワークと連携可能な情報処理装置とを含む制御システムであって、
前記複数のノードのそれぞれのノードは、
取引情報を有効化する予定時点を記録する第1のブロックチェーンを管理し、
自ノードで管理する前記第1のブロックチェーンの記録内容に基づいて、予定時点が経過した取引情報を特定し、特定した結果を自ノードで管理する前記第1のブロックチェーンに記録し、
前記情報処理装置は、
前記第1のブロックチェーンの記録内容に基づいて、前記複数のノードのうち所定の条件を満たすノードによって特定された取引情報を、前記1以上のノードのそれぞれのノードに送信し、
前記1以上のノードのそれぞれのノードは、
有効化された取引情報を記録する第2のブロックチェーンを管理し、
受信した前記取引情報を含むブロックを生成し、自ノードで管理する前記第2のブロックチェーンに追加する、
ことを特徴とする制御システム。 - 前記所定の条件は、ノードの所定の数であり、
前記情報処理装置は、
前記第1のブロックチェーンの記録内容に基づいて、前記複数のノードのうち前記所定の数以上のノードによって共通して特定された取引情報を、前記1以上のノードのそれぞれのノードに送信する、ことを特徴とする請求項1に記載の制御システム。 - 前記複数のノードのそれぞれのノードは、
いずれかの取引情報を有効化する予定時点を取り消す取消要求を受け付けた場合、前記いずれかの取引情報を有効化する予定時点を取り消すことを示す取消情報を含むブロックを生成し、自ノードで管理する前記第1のブロックチェーンに追加し、
自ノードで管理する前記第1のブロックチェーンの記録内容に基づいて、前記いずれかの取引情報以外で、予定時点が経過した取引情報を特定し、特定した結果を自ノードで管理する前記第1のブロックチェーンに記録する、ことを特徴とする請求項1または2に記載の制御システム。 - 前記複数のノードのそれぞれのノードは、
いずれかの取引情報を有効化する予定時点を記録する記録要求を受け付けた場合、前記いずれかの取引情報を有効化する予定時点を含むブロックを生成し、自ノードで管理する前記第1のブロックチェーンに追加する、ことを特徴とする請求項1~3のいずれか一つに記載の制御システム。 - 前記複数のノードのそれぞれのノードは、
自ノードで管理する前記第1のブロックチェーンに新たなブロックが一定の数分追加される都度、自ノードで管理する前記第1のブロックチェーンの記録内容に基づいて、予定時点が経過した取引情報を特定し、特定した結果を自ノードで管理する前記第1のブロックチェーンに記録する、ことを特徴とする請求項4に記載の制御システム。 - 前記一定の数は2以上の数である、ことを特徴とする請求項5に記載の制御システム。
- 前記複数のノードのそれぞれのノードは、
一定の期間に前記記録要求を受け付けない場合、ダミーの取引情報を有効化する予定時点を含むブロックを生成し、自ノードで管理する前記第1のブロックチェーンに追加する、ことを特徴とする請求項5または6に記載の制御システム。 - 前記複数のノードのそれぞれのノードは、
前記所定の条件を満たすノードによって特定された取引情報を特定するスマートコントラクトを有し、前記スマートコントラクトを利用して、自ノードで管理する前記第1のブロックチェーンの記録内容に基づいて、予定時点が経過した取引情報を特定し、当該取引情報が、前記所定の条件を満たすノードによって特定された取引情報であれば、当該取引情報を、自ノードで管理する前記第1のブロックチェーンに記録する、ことを特徴とする請求項1~7のいずれか一つに記載の制御システム。 - 前記予定時点は、前記第1のブロックチェーンに所定のブロックが追加された追加時点を示す、ことを特徴とする請求項1~8のいずれか一つに記載の制御システム。
- 第1のブロックチェーンネットワークを形成するノードに、
取引情報を有効化する予定時点を記録する第1のブロックチェーンを管理し、
自ノードで管理する前記第1のブロックチェーンの記録内容に基づいて、予定時点が経過した取引情報を特定し、
前記第1のブロックチェーンの記録内容に基づいて、前記第1のブロックチェーンネットワークを形成する複数のノードのうち所定の条件を満たすノードによって特定された取引情報を、有効化された取引情報を記録する第2のブロックチェーンを管理するノードに送信する情報処理装置が参照可能に、特定した結果を自ノードで管理する前記第1のブロックチェーンに記録する、
処理を実行させることを特徴とする制御プログラム。 - 第1のブロックチェーンネットワークを形成するノードが、
取引情報を有効化する予定時点を記録する第1のブロックチェーンを管理し、
自ノードで管理する前記第1のブロックチェーンの記録内容に基づいて、予定時点が経過した取引情報を特定し、
前記第1のブロックチェーンの記録内容に基づいて、前記第1のブロックチェーンネットワークを形成する複数のノードのうち所定の条件を満たすノードによって特定された取引情報を、有効化された取引情報を記録する第2のブロックチェーンを管理するノードに送信する情報処理装置が参照可能に、特定した結果を自ノードで管理する前記第1のブロックチェーンに記録する、
処理を実行することを特徴とする制御方法。 - 第1のブロックチェーンネットワークを形成する制御装置であって、
取引情報を有効化する予定時点を記録する第1のブロックチェーンを管理し、
自ノードで管理する前記第1のブロックチェーンの記録内容に基づいて、予定時点が経過した取引情報を特定し、
前記第1のブロックチェーンの記録内容に基づいて、前記第1のブロックチェーンネットワークを形成する複数のノードのうち所定の条件を満たすノードによって特定された取引情報を、有効化された取引情報を記録する第2のブロックチェーンを管理するノードに送信する情報処理装置が参照可能に、特定した結果を自ノードで管理する前記第1のブロックチェーンに記録する、
制御部を有することを特徴とする制御装置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/007214 WO2022180752A1 (ja) | 2021-02-25 | 2021-02-25 | 制御システム、制御プログラム、制御方法、および制御装置 |
JP2023501929A JPWO2022180752A1 (ja) | 2021-02-25 | 2021-02-25 | |
US18/355,797 US20230360037A1 (en) | 2021-02-25 | 2023-07-20 | Control system, storage medium, and control method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/007214 WO2022180752A1 (ja) | 2021-02-25 | 2021-02-25 | 制御システム、制御プログラム、制御方法、および制御装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/355,797 Continuation US20230360037A1 (en) | 2021-02-25 | 2023-07-20 | Control system, storage medium, and control method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022180752A1 true WO2022180752A1 (ja) | 2022-09-01 |
Family
ID=83048879
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/007214 WO2022180752A1 (ja) | 2021-02-25 | 2021-02-25 | 制御システム、制御プログラム、制御方法、および制御装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20230360037A1 (ja) |
JP (1) | JPWO2022180752A1 (ja) |
WO (1) | WO2022180752A1 (ja) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019028525A (ja) | 2017-07-26 | 2019-02-21 | 株式会社日立製作所 | 運用管理方法、運用管理システム、および、運用管理プログラム |
US20190205884A1 (en) * | 2017-12-28 | 2019-07-04 | International Business Machines Corporation | Converting processes into multiple blockchain smart contracts |
JP2020126577A (ja) * | 2018-05-11 | 2020-08-20 | 株式会社Maxele | 価値交換媒体の単位交換価値を制御するためのシステム、プログラム、情報処理装置、及び方法 |
JP2020134997A (ja) * | 2019-02-13 | 2020-08-31 | ログトレ株式会社 | 突合システム、突合装置、突合システム用の方法及び、突合システム用のプログラム |
-
2021
- 2021-02-25 JP JP2023501929A patent/JPWO2022180752A1/ja not_active Withdrawn
- 2021-02-25 WO PCT/JP2021/007214 patent/WO2022180752A1/ja active Application Filing
-
2023
- 2023-07-20 US US18/355,797 patent/US20230360037A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019028525A (ja) | 2017-07-26 | 2019-02-21 | 株式会社日立製作所 | 運用管理方法、運用管理システム、および、運用管理プログラム |
US20190205884A1 (en) * | 2017-12-28 | 2019-07-04 | International Business Machines Corporation | Converting processes into multiple blockchain smart contracts |
JP2020126577A (ja) * | 2018-05-11 | 2020-08-20 | 株式会社Maxele | 価値交換媒体の単位交換価値を制御するためのシステム、プログラム、情報処理装置、及び方法 |
JP2020134997A (ja) * | 2019-02-13 | 2020-08-31 | ログトレ株式会社 | 突合システム、突合装置、突合システム用の方法及び、突合システム用のプログラム |
Non-Patent Citations (1)
Title |
---|
ETHEREUM ALARM CLOCK, 16 February 2021 (2021-02-16), Retrieved from the Internet <URL:https://www.ethereum-alarm-clock.com> |
Also Published As
Publication number | Publication date |
---|---|
JPWO2022180752A1 (ja) | 2022-09-01 |
US20230360037A1 (en) | 2023-11-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11531981B2 (en) | Digital contracts in blockchain environments | |
JP7108611B2 (ja) | 電子手形管理方法及び装置並びに記憶媒体 | |
TWI829626B (zh) | 用於指定電子通訊之接收者的基於區塊鏈之方法及系統 | |
CN110620810B (zh) | 在区块链上的连续资产转移的非链接所有权 | |
CN112381646A (zh) | 基于区块链的隐私交易及其应用方法和装置 | |
CN113435994A (zh) | 基于区块链的金融借贷多方共享交易元数据信息的方法、装置及系统 | |
CN111727428A (zh) | 基于区块链的房间库存管理系统 | |
US11151122B2 (en) | Distributed ledger data linkage management | |
EP3696766A1 (en) | Program, system and method for determining credit worthiness of a user | |
KR20190138614A (ko) | 신뢰가 없는 네트워크에서 데이터 전달을 증명하는 방법 및 장치 | |
CN110009320B (zh) | 资源转换方法、装置、系统、存储介质和计算机设备 | |
WO2022180752A1 (ja) | 制御システム、制御プログラム、制御方法、および制御装置 | |
KR102123487B1 (ko) | 암호화폐 교환을 위한 트랜잭션을 매칭하는 전자 장치 및 방법 | |
US20070027835A1 (en) | Systems and methods for processing data in a Web services environment | |
WO2023204954A1 (en) | Offline cryptocurrency transactions | |
JPWO2022180752A5 (ja) | ||
KR20200078069A (ko) | 블록체인 네트워크와 금융 시스템의 연동을 위한 검증 장치 및 방법 | |
CN112150157B (zh) | 通过区块链发行应收凭证的方法及装置 | |
JP2023106055A (ja) | エビデンス管理方法、エビデンス管理システム及びノード | |
CN110852891A (zh) | 基于轧差的数据处理方法、装置以及可读存储介质 | |
US20230267459A1 (en) | Method and device for stake-based token management on a blockchain system | |
KR20190136617A (ko) | 용도 지정형 암호 화폐의 거래 정보 처리 시스템 | |
KR20190136487A (ko) | 용도 지정형 암호 화폐의 거래 정보 처리 방법 및 그 장치 | |
KR102475662B1 (ko) | 분산원장 기반의 블록체인을 이용한 포인트 관리 방법 및 시스템 | |
KR102131548B1 (ko) | 전자지갑 생성 방법 및 이를 이용한 암호화폐 거래 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21927854 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2023501929 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021927854 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021927854 Country of ref document: EP Effective date: 20230925 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21927854 Country of ref document: EP Kind code of ref document: A1 |