Transaction management system and transaction management method
In a transaction management system which is a distributed ledger system in which a business network is formed of a plurality of nodes, the node calculates an upper limit of the number of transactions that can be issued by each of a plurality of organizations according to a calculation rule shared among the nodes, and refuses to accept the transaction from an organization of the organizations of which the number of transactions in past exceeds the upper limit of the number of transactions.
1 . A transaction management system that is a distributed ledger system in which a business network is formed of a plurality of nodes,
each node calculates an upper limit of a number of transactions that can be issued by each of a plurality of organizations according to a calculation rule shared among the nodes, and refuses to accept a transaction from an organization of the organizations of which the number of transactions in past exceeds the upper limit of the number of transactions,
the transaction management system comprises a predetermined node that manages configuration information of an organization on a distributed ledger for the organization that can participate in the distributed ledger system, and
the plurality of nodes calculate the upper limit of the number of transactions for each organization by applying the configuration information obtained from the predetermined node as input to the calculation rule for the upper limit of the number of transactions.
2 . The transaction management system of claim 1 , wherein
each node,
recalculates the upper limit of the number of transactions for each of the plurality of organizations based on the calculation rule for the upper limit of the number of transactions when the configuration information obtained from the predetermined node is changed.
3 . The transaction management system of claim 1 , wherein
each node,
holds, in the calculation rule for the upper limit of the number of transactions, policy information for allocating the upper limit of the number of transactions for each of the plurality of organizations according to an attribute of the organization.
4 . The transaction management system of claim 1 , wherein
the nodes,
share a smart contract, which is logic describing a condition of a transaction to be carried out between organizations participating in the distributed ledger system, upon agreement between participants, and
in the calculation rule for the upper limit of the number of transactions, when a number of past transactions for each of the plurality of organizations is calculated, policy information is held that changes for each smart contract according to a difference in a processing load of the smart contract.
5 . The transaction management system of claim 4 , wherein
each node,
holds an endorsement policy, which is a consensus level when forming a transaction consensus among organizations participating in the distributed ledger system, for each smart contract.
6 . The transaction management system of claim 1 , wherein
each node,
specifies a transaction as a past transaction in each of the plurality of organizations based on a timestamp of the transaction stored in the distributed ledger and each piece of information of an organization to which a transaction executor belongs, and calculates a number of transactions as the number of past transactions.
7 . The transaction management system of claim 1 , further comprising:
a load balancer that allocates transactions from another application to the nodes, wherein
the load balancer holds a history of the transactions from the higher-level application as a log, and
when the number of past transactions for each of the plurality of organizations is calculated, each node specifies a transaction based on a timestamp of the transaction and each piece of information on an organization to which a transaction executor belongs, which are held in the log of the load balancer, and calculates a number of transactions as the number of past transactions.
8 . The transaction management system of claim 1 , wherein
the predetermined node,
is a gateway node that acts on behalf of each process of consensus building and approval of a transaction in response to a request from another application.
9 . The transaction management system of claim 1 , wherein
the configuration information includes a field for registering the name of each node which belongs to each organization and to which a transaction is to be transmitted by a gateway node and a field for registering an ID of each organization, respectively.
10 . A transaction management method, wherein
in a distributed ledger system in which a business network is formed of a plurality of nodes, the method comprising the steps of:
calculating, by each node, an upper limit of a number of transactions that can be issued by each of a plurality of organizations according to a calculation rule shared among the nodes, and refusing to accept a transaction from an organization of the organizations of which the number of transactions in past exceeds the upper limit of the number of transactions,
managing, by a predetermined node, configuration information of an organization on a distributed ledger for the organization that can participate in the distributed ledger system, and
calculating, by each node, the upper limit of the number of transactions for each organization by applying the configuration information obtained from the predetermined node as input to the calculation rule for the upper limit of the number of transactions.
11 . The transaction management method of claim 10 , wherein
the configuration information includes a field for registering the name of each node which belongs to each organization and to which a transaction is to be transmitted by a gateway node and a field for registering an ID of the organization, respectively.