Smart contract blockchain abstraction API
US-10871948-B1 · Dec 22, 2020 · US
US11514443B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11514443-B2 |
| Application number | US-201816632935-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 9, 2018 |
| Priority date | Jul 26, 2017 |
| Publication date | Nov 29, 2022 |
| Grant date | Nov 29, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Operation management with consistent policies and timings between nodes even in a situation where there are a plurality of administrators in the distributed ledger system is realized. In an operation management system 10 for a distributed ledger system 6 comprising a plurality of nodes, each of at least two or more predetermined nodes in the plurality of nodes manages an operation smart contract 372 for operation management of the distributed ledger system with a distributed ledger 37 , when at least one node in the two or more predetermined nodes receives a transaction, the node which has received the transaction judges whether or not a type of the transaction is the operation smart contract 372 , and, based on the judgment result, executes the operation smart contract 372.
Opening claim text (preview).
The invention claimed is: 1. A system operations management method of a distributed ledger system comprising a plurality of nodes, each node including a memory coupled to a processor, the method comprising the steps of: managing, by each of at least two or more predetermined nodes in the plurality of nodes, a system operations smart contract for executing system operations to the distributed ledger system itself or to nodes themselves comprising the distributed ledger system, the system operations smart contract holding at least any one of an identifier identifying a type of a system operation and procedure information for executing the system operation corresponding to the type of the system operation; when at least one node in the two or more predetermined nodes receives a transaction of the system operations smart contract, executing, by the node which has received the transaction, the system operations smart contract; and in response to the execution of the system operations smart contract, executing, by either of the node or a system operations execution program associated with the node, the system operations execution program stored on a memory on a node, a system operation work according to at least any one of the identifier identifying the type of the system operation held in the system operations smart contract and the procedure information of the system operation for a node being a target of the system operation. 2. The system operations management method according to claim 1 , wherein the system operations smart contract holds a data structure managing an execution history of the operation work for the identifier identifying the type of the operation, and wherein the system operations smart contract includes an acceptance phase of an operation work and a confirmation phase of completion of the execution, and, as an internal processing of the system operations smart contract, includes an individual registration step registering each completion of the execution in each node in the execution history in the confirmation phase of completion of the execution and a completion judgement step judging the completion of the entire operation work by confirming the registration status referring to the registration of the completion of the execution including those at the other nodes in the execution history. 3. The system operations management method according to claim 2 , wherein the node which has received the transaction in the distributed ledger system executes the operational smart contract and makes the transaction in the confirmation phase of the execution completion include an evidence of completion or information associated with the evidence of the completion, and as an internal processing of the system operations smart contract, the node which has received the transaction in the distributed ledger system registers an evidence of completion at each of the nodes at the individual registration step as the execution history or as information linked with the execution history, and utilizes the evidence of the completion to the completion judgement of the entirety of the operation work as a condition for the judgement of the completion at the completion judgement step. 4. The system operations management method according to claim 3 , wherein the system operations smart contract further holds recovery procedure information corresponding to an identifier identifying a type of an operation, when the node which has received the transaction in the distributed ledger system has failed to complete execution in the confirmation phase of the execution completion as a result of execution of the system operations smart contract, a predetermined recovery or re-execution process according to the recovery procedure information in the system operations smart contract may be performed. 5. The system operations management method according to claim 1 , wherein the system operations smart contract holds a data structure for managing an execution history of at least any one of registration of an operation work and execution of an operation work for each identifier identifying a type of an operation, and wherein the system operations smart contract includes an approval phase in at least one of registration and execution of a smart contract, and includes, as an internal processing of the system operations smart contract, an individual registration step registering each completion of the execution in each node in the execution history in the confirmation phase of completion of the execution and a completion judgement step judging the completion of the entire operation work by confirming the registration status referring to the registration of the completion of the execution including those at the other nodes in the execution history. 6. The system operations management method according to claim 1 , wherein a node which is not in charge of executing a business smart contract for business among the two or more predetermined nodes participates in a network and executes the system operations smart contract as a participant of a business network constituted by the distributed ledger system or a node participating in consensus formation of the system operations smart contract. 7. The system operations management method according to claim 1 , wherein the node that has received the transaction in the distributed ledger system issues a deployment transaction for adding/updating the system operations smart contract and an operation execution transaction for executing the operation work defined by the system operations smart contract with respect to the system operations smart contract, and verifies correctness of the system operations execution program to be used for the operation work at the time of issuing at least one of the deployment transaction and the operation execution transaction by calculating a hash value of the system operations execution program and judging based on whether or not the hush value matches a hush value calculated in advance and held as an internal variable of the system operations smart contract or a hush value related to the system operations execution program on the other node. 8. The system operations management method according to claim 1 , wherein a node which has executed the system operations smart contract in the two or more predetermined nodes issues an event related to the operation work including an identifier identifying at least the content of the operation indicating that the system operations smart contract has been executed at the time of execution of the system operations smart contract, and the system operations execution program which is held by the two or more predetermined nodes or associated with the node executes the operation work according to at least the content identified by the identifier in response to the event. 9. The system operations management method according to claim 1 , wherein, as at least a part of the operation procedure information, at least any one of one or more operation command string, a program to be called, a source code describing operation content, and information of the node to be operated is embedded in the event, and the system operations execution program executes the operation work according to the embedded procedure information. 10. The system operations management method according to claim 1 , wherein the plurality of nodes in the distributed ledger system manage a smart contract for operation management of a distributed processing system different from the distributed ledger system by a distributed ledger, execute the smart contract, and perform operation management of the distributed processing node in the distributed processing system. 11. A system operation
involving key management · CPC title
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling · CPC title
Transaction verification · CPC title
Keeping log of transactions for guaranteeing non-repudiation of a transaction · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.