KR20210027011A - Peer node, method for processing information executed on peer node and blockchain platform system - Google Patents

Abstract

According to one embodiment of the present invention, an information processing method comprises the steps of: receiving a predetermined transaction from a client application of a blockchain platform; selecting any one contract server from a plurality of contract servers included in a contract executer node of the blockchain platform based on a contract corresponding to the transaction; and forwarding the transaction to the selected contract server.

Description

PEER NODE, METHOD FOR PROCESSING INFORMATION EXECUTED ON PEER NODE AND BLOCKCHAIN PLATFORM SYSTEM}

The present invention relates to a peer node, a processing method performed in the peer node, and a blockchain platform system.

Since the release of decentralized electronic money, various countries and companies around the world have been continuing research and efforts to apply blockchain, a core technology, to various industrial fields. In addition, there are also attempts to utilize this blockchain technology in all methods of storing and transmitting data as well as transaction information.

However, at the level of the current blockchain technology, it is not easy to run actual application services. Accordingly, as a way to improve the technical level, modifications or compromises to the above-described decentralization are being studied. As a result of these modifications or compromises, the amount of resources required for consensus has been reported to be reduced.

However, these achievements do not even solve the performance bottleneck for the execution of smart contracts.

Korean Patent Publication, No. 10-1924026 (registered on November 26, 2018)

The problem to be solved of the present invention includes providing a technology that allows a contract to be executed in any one of a plurality of contract servers (smart contract server).

However, the problem to be solved of the present invention is not limited to those mentioned above, and another problem to be solved that is not mentioned can be clearly understood by those of ordinary skill in the art to which the present invention belongs from the following description. will be.

An information processing method executed in a peer node constituting a blockchain platform according to an embodiment includes receiving a predetermined transaction from a client application of the blockchain platform, and based on a contract corresponding to the transaction. Thus, it includes selecting one of a plurality of contract servers included in the contract executer node of the blockchain platform, and transmitting the transaction to the selected contract server.

Further, in the selecting step, after extracting a hash value based on a contract corresponding to the transaction, one of the plurality of contract servers may be selected based on the extracted hash value.

In addition, a range of hash values is differently allocated to each of the plurality of contract servers, and the selecting step includes, among the plurality of contract servers, the range of the allocated hash value including the extracted hash value. You can choose the contract server.

In addition, each of the plurality of contract servers includes a plurality of configuration servers, and each of the plurality of configuration servers includes an execution unit executing a predetermined contract and a plurality of state databases related to the execution unit. I can.

A peer node according to an embodiment, upon receiving a predetermined transaction from a client application of the blockchain platform, based on a contract corresponding to the transaction, includes a plurality of contract executer nodes of the blockchain platform. And a selection unit for selecting any one of the contract servers, and a guarantee node for transmitting the transaction to the selected contract server through the communication unit.

The blockchain platform system according to an embodiment includes a contract executer node including a plurality of contract servers and a peer node, wherein the peer node transmits a predetermined transaction from a client application of the blockchain platform. Upon receipt, a selection unit for selecting one of the plurality of contract servers, based on a contract corresponding to the transaction, and a guarantee node for transmitting the transaction to the selected contract server through the communication unit.

According to one embodiment, the contract may be distributed and executed on a plurality of contract servers. Thus, the number of contracts that can be executed at the same time can be increased. In addition, when the number of contracts expected to be executed is large, the processing of such contracts can be smoothly performed by expanding the contract server such as Arm server.

1 is an exemplary configuration diagram of a blockchain platform system including a peer node according to an embodiment.
FIG. 2 is an exemplary configuration diagram of any one contract server among a plurality of contract servers shown in FIG. 1.
FIG. 3 is an exemplary configuration diagram of any one configuration server among a plurality of configuration servers shown in FIG. 2.
4 is an exemplary flowchart illustrating a process of processing a contract in a blockchain platform system according to an embodiment.
5 is a flowchart illustrating a process of selecting a contract server for executing or simulating a contract from among a plurality of smart contract servers.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only these embodiments make the disclosure of the present invention complete, and are common knowledge in the technical field to which the present invention pertains. It is provided to completely inform the scope of the invention to those who have, and the invention is only defined by the scope of the claims.

In describing the embodiments of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in an embodiment of the present invention, which may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout the present specification.

In the present specification, expressions in the singular include plural expressions unless the context clearly indicates otherwise. In the present application, terms such as'comprise' or'comprise' are intended to designate the existence of features, numbers, steps, actions, components, parts, or a combination thereof described in the specification, but one or more other It is to be understood that it does not preclude the presence or addition of features, numbers, steps, actions, components, parts, or combinations thereof.

Further, in an embodiment of the present invention, when a part is connected to another part, this includes not only a direct connection but also an indirect connection through another medium. In addition, the meaning that a part includes a certain component means that other components may be further included rather than excluding other components unless specifically stated to the contrary.

1 is an exemplary configuration diagram of a blockchain platform system 100 including a peer node 120 according to an embodiment.

As shown in FIG. 1, the blockchain platform system 100 according to an embodiment includes a proxy node 110, a peer node 120, a verification node 130, and a shared memory. memory) 140, instruction (Orderer) node 150, block storage (Block storage) 160, and may include a contract execution (Contract executer) node 170, the peer node 120 is endorser (Endorser) ) It may include a node 121, a delegate node 122, and a selection unit 123. At this time, the verification node 130 may include Q (however, Q is a natural number) number of cores 131, and the contract execution node 170 has N (however, N is a natural number) number of contract servers 171 Can include.

First, the proxy node 110 is a service that acts as an intermediary between the blockchain cores, that is, the peer node 120, the verification node 130, and the indication node 150, and the client application 10. Such a proxy node 110 may serve as a barrier against malicious access.

The peer node 120 includes an assurance node 121, a delegation node 22, and a selection unit 123.

Among these, the guarantee node 121 may check whether the guarantee policy has been observed with respect to the transaction proposal generated by the client application 10.

In addition, the assurance node 121 may delegate the validation of the user signature to the verification node 130 during the verification of compliance with the assurance policy.

If the validity of the user signature is confirmed by the verification node 130 and the transaction proposal is confirmed to comply with the assurance policy, the assurance node 121 may execute the corresponding transaction. Here, execution of such a transaction leads to execution of a contract, which will be described later.

On the other hand, the assurance node 121 may delegate the creation of the signature for the assurance node 121 to the verification node 130 during execution of the corresponding transaction, and for the assurance node 121 generated by the verification node 130 The signature may be included in the proposal response and transmitted to the client application 10 through the proxy node 110.

The delegation node 122 can check whether all transactions in the block transmitted from the indicating node 150 comply with each guarantee policy, and in the process of checking whether the transaction conforms to the guarantee policy, it is included in all transactions included in the block. The verification of the signature for the guaranteed node 121, which has been verified, can be delegated to the verification node 130, and the block chain of the block storage 160 so that all transactions contain blocks that are confirmed to comply with the assurance policy. Ledger can be updated.

The selection unit 123 selects any one contract server 171 from among the N contract servers 171 included in the contract execution node 170. In the selected contract server 171, a contract corresponding to the transaction received from the client application 10 may be executed.

At this time, let's look at the selection process of such a contract server 171. It is assumed that the ranges of the hash values are allocated to each of the N contract servers 171 differently from each other, that is, not overlapping each other. For example, contract server #1 (171) is assigned a hash value range from 0 to A, contract server #2 (171) is assigned a hash value range from A+1 to B, and contract server #3 ( 171) is assigned a range of hash values from B+1 to C.

On the premise of this, the selection unit 123 extracts a hash value based on a contract corresponding to the transaction received from the client application 10. It is assumed that the algorithm for extracting the hash value and the like employs a known technique.

In addition, the selection unit 123 selects any one contract server 171 from among the N contract servers 171. In the selection process, a contract server 171 having a hash value range including a hash value extracted by the selection unit 123 may be selected from among the N contract servers 171.

The indicating node 150 receives the transaction message generated by the client application 10, receives transactions occurring in all channels regardless of the contents included in the transaction message, and arranges them in chronological order to generate a block, and the generated block Is transmitted to the delegating node 121 of all peer nodes 120 of the channel.

The verification node 130 may be delegated to verify the validity of the user signature from the assurance node 121, and may verify the validity of the user signature. In addition, the verification node 130 may return a result of validating user signatures processed in parallel by the plurality of cores 131 to the assurance node 121.

In addition, the verification node 130 receives the signature generation task of the assurance node 121 from the assurance node 121 and returns the signature generation result processed in parallel by the plurality of cores 131 to the assurance node 121 You may.

In addition, the verification node 130 may receive verification of the signature of the assurance node 121 included in the transaction in the block generated by the instruction node 150 from the delegating node 122, and a plurality of cores 141 As a result, the signature verification result of the assurance node 121 processed in parallel may be returned to the delegating node 122.

When the shared memory 140 communicates between the assurance node 121 of the peer node 120 and the verification node 130, the delegation node 122 of the peer node 120 and the verification node 130 communicate with each other. It is a storage space that is shared with each other.

Meanwhile, in FIG. 2, an exemplary configuration diagram of any one of the N contract servers 171 shown in FIG. 1 is shown. 2, the contract server 171 includes M number of configuration servers 172. The configuration server 172 may be an Arm server, but is not limited thereto. That is, one contract server 171 may include a configuration server 172 such as M number of Arm servers.

In addition, each of the configuration servers 172 includes P contract execution units 173 (wherein P is a natural number). The configuration of each contract execution unit 173 is shown in FIG. 3. Referring to FIG. 3, the contract execution unit 173 includes an execution unit and a state DB (DataBase). In each execution unit, a contract specified in advance can be executed. In addition, data related to contracts are stored in the state DB associated with each of these execution units.

Here, each of the contract execution units 173 may be sharding or replicated, and rebalancing may be performed according to various algorithms. For example, when the resource required for execution of a specific contract is higher than the average or higher than a predefined amount, a specific contract may be sharded or replicated through sharding or replication.

That is, looking at with reference to Figures 1 to 3, the blockchain platform system 100 according to an embodiment includes a plurality of contract servers 171 such as a smart contract server, and each contract server 171 includes an Arm server A plurality of configuration servers 172 are included, and each configuration server 172 includes a plurality of contract execution units 173 consisting of an execution unit and a state DB. Here, each contract execution unit 173 may be set to execute only contracts previously designated.

Hereinafter, a transaction and contract processing process of the blockchain platform system 100 according to an embodiment of the present invention will be described with reference to FIGS. 1 to 4 and 5.

First, referring to FIG. 4, a general user or an authorized user accesses the proxy node 110 through the SDK (Software Development Kit) of the client application 10 and then calls a transaction to make various transaction proposals. It can be generated (S201). Here, the user's identity information may be inserted into the transaction proposal in the form of a signature. For example, after creating an account, a general user can create a transaction using the account's private key. Authorized users can create transactions through an identity certificate issued through a Certification Authority (CA).

The proxy node 110 is a service that acts as an intermediary between the client application 10 and the blockchain platform cores (for example, an instruction node, an assurance node, and a delegation node), and the client application 10 is a block chain through itself. It allows indirect access to platform cores and can act as a barrier against malicious access. The transaction generated by the client application 10 is transmitted to the assurance node 121 in the peer node 120 through the proxy node 110. At this time, the transaction proposal is transmitted to the guarantee nodes 121 included in each of the plurality of peer nodes 120 (S203).

Endorsing policy of a transaction is specified in the endorsing nodes 121, and these endorsing nodes 121 may execute the corresponding transaction after confirming whether the transaction proposal complies with the endorsing policy.

In the process of checking whether the transaction proposal complies with the guarantee policy, the guarantee node 121 can check whether the transaction proposal is properly filled in according to the format, can check whether the transaction has been submitted before, and can confirm the transaction proposal. You can check whether the client has the right to suggest.

The assurance policy specified in the assurance node 121 may include the validity of the user's signature. In this case, the assurance node 121 may delegate validation of the user signature to the verification node 130. Then, validation of the user signature may be delegated to the verification node 130 from the plurality of assurance nodes 121 (S205 ). Such a plurality of user signature validation tasks are processed in parallel by a plurality of cores 131 constituting the verification node 130 (S207), and the processing result is sent to the assurance node 121 of the peer node 120. It is returned (S209). Here, the communication between steps S205 and S209 may use the shared memory 140 that is jointly used by the peer node 120 and the verification node 130.

If the validity of the user signature has been verified by the verification node 130 and the transaction proposal has been confirmed to comply with the assurance policy (S211), the assurance node 121 may execute the corresponding transaction (S213). Looking at an example of S213 in more detail, the assurance node 121 can call a contract by a specific calculation, the called contract is simulated according to a predetermined parameter, and the result of the simulation (read/write set ) May be returned to the guarantee node 121.

At this time, the called contract can be executed or simulated in any one of the contract servers 171 of the plurality of contract servers 171 included in the contract execution node 170, any of these contract servers 171 It may be selected by the selection unit 123 of the peer node 120. Hereinafter, a process in which the selection unit 123 selects any one contract server 171 from among the plurality of contract servers 171 will be described in more detail with reference to FIG. 5.

5 is a flowchart illustrating a process of selecting a contract server 171 in which a contract is to be executed or simulated from among a plurality of contract servers 171 by the selection unit 123 of the peer node 120. However, since FIG. 5 is only an example, the spirit of the present invention is not limited to that illustrated in FIG. 5.

Referring to FIG. 5, the guarantee node 121 transmits the transaction proposal received from the proxy node 110 to the distribution unit 123 in step S203 (S2131).

Then, the distribution unit 123 selects any one contract server 171 from among the plurality of contract servers 171 (S2132). In the selection process, the hash value of the contract corresponding to the transaction proposal received in S2131 is selected by comparing the hash value range allocated to each of the plurality of contract servers 171, and this selection process uses the previously described one. I will do it.

Thereafter, the distribution unit 123 transmits a request for a contract to the contract server 171 selected in S2132 (S2133).

The contract server 171 receiving the request executes a contract according to the request (S2134). These runs are simulated by parameters.

The result of the transaction execution is transmitted from the server 171 to the assurance node 121 (response) (S2135).

See FIG. 4 again. Then, the peer node 120 may transmit the result of the transaction execution to the client application 10 as a proposal response through the proxy node 110. In this case, the proposal response may include a signature of the assurance node 121, and the assurance node 121 may delegate the signature generation to the verification node 130. Then, signature generation may be delegated to the verification node 130 from the plurality of assurance nodes 121 (S215). Such a plurality of signature generation tasks are processed in parallel by the plurality of cores 141 constituting the verification node 130 (S217), and the signature generated by the processing result is the assurance node of the peer node 120 ( 121), and the assurance node 121 may include the signature generated by the verification node 130 in the proposal response and transmit it to the client application 10 through the proxy node 110 (S219). S221, S223).

The client application 10 checks the signature of the assurance node 121 and then compares the proposal responses from each peer node 120. If you don't need an ordering service like a simple query, you can get the query result and terminate the process. In the case of updating the ledger, it may be reviewed whether a response to the proposal that complies with the guarantee policy is returned at the client level (S225).

When the proposal response satisfies the guarantee policy, the client application 10 transmits the transaction result value included in the proposal response to the indicating node 150 through the proxy node 110. For example, the client application 10 may include both a transaction proposal and a proposal response corresponding thereto in the transaction message and transmit it to the indicating node 150 through the proxy node 110 (S227 and S229). For example, the transaction message may include a simulation result (read/write set), a signature of the assurance node 121, and a channel ID (ID).

The indicating node 150 receives the transactions occurring in all channels regardless of the content included in the transaction message, arranges them in chronological order to generate a block (S231), and delegates the generated block to all peer nodes 120 of the channel. It is transmitted to the node 122 (S233).

Each delegating node 122 of peer nodes 120 verifies that all transactions in the block comply with their respective endorsement policies. Here, in the process of verifying compliance with the guarantee policy, the signature of the guarantee node 121 included in all transactions included in the block must be verified. However, since multiple transactions are included in one block and multiple signatures are included in each transaction, the number of signatures that must be verified during the process of verifying compliance with the assurance policy is very large. For example, if a blockchain platform with the goal of processing more than 500,000 transactions per second when it is necessary to verify 4 signatures per transaction, it is necessary to verify more than 2 million signatures per second. In the case of intensively allocating the computing and computing resources of (122), it is highly likely that computing and computing resources to be used for processing other data, such as database input/output, etc., are highly likely to be consumed, and this may lead to overall performance degradation. In order to prevent such performance degradation, the delegating node 122 may delegate the signature verification to the verification node 130 during the process of verifying whether the assurance policy is complied with. Then, signature verification may be delegated to the verification node 130 from the plurality of delegating nodes 122 (S235). Such a plurality of signature verification tasks are processed in parallel by a plurality of cores 141 constituting the verification node 130 (S237), and the processing result is returned to the delegating node 122 of the peer node 120. (S239). In this case, the delegating node 122 may tag a corresponding transaction with a result value (eg, valid/invalid) according to the process of checking whether the guarantee policy is complied with (S241).

Each delegation node 122 of the peer nodes 120 transfers the block confirmed to comply with the guarantee policy to the block storage 160 and adds the block generated in step S231 to the block chain ledger of the block storage 160 It can be renewed. When such a series of processes up to the blockchain update is completed, the delegation node 122 of the peer node 120 may transmit the result of the operation to the client application 10.

As described so far, according to one embodiment, the contract may be distributed and executed on a plurality of contract servers. Thus, the number of contracts that can be executed at the same time can be increased. In addition, if the number of contracts expected to be executed is large, the processing of these contracts can be smoothly performed by expanding the contract server such as Arm server.

Combinations of each step in each flowchart attached to the present invention may be performed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are the functions described in each step of the flowchart. Will create a means of doing things. These computer program instructions can also be stored on a computer-usable or computer-readable recording medium that can be directed to a computer or other programmable data processing equipment to implement a function in a specific manner, so that the computer-readable or computer-readable medium. It is also possible to produce an article of manufacture containing instruction means for performing the functions described in each step of the flow chart with instructions stored on the recording medium. Since computer program instructions can also be mounted on a computer or other programmable data processing equipment, a series of operating steps are performed on a computer or other programmable data processing equipment to create a computer-executable process to create a computer or other programmable data processing equipment. It is also possible for the instructions to perform the processing equipment to provide steps for executing the functions described in each step of the flowchart.

In addition, each step may represent a module, segment, or part of code that contains one or more executable instructions for executing the specified logical function(s). In addition, it should be noted that in some alternative embodiments, the functions mentioned in the steps may occur out of order. For example, two steps shown in succession may in fact be performed substantially simultaneously, or the steps may sometimes be performed in the reverse order depending on the corresponding function.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains will be able to make various modifications and variations without departing from the essential characteristics of the present invention. Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but to explain the technical idea, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

100: blockchain platform system 110: proxy node
120: peer node 121: endorsement node
122: delegate node 130: verification node
140: shared memory 150: indicating node
160: block storage
170: contract execution node

Claims (8)

As an information processing method executed in a peer node constituting a blockchain platform,
Receiving a predetermined transaction from the client application of the blockchain platform,
Selecting one of a plurality of contract servers included in a contract executer node of the blockchain platform based on a contract corresponding to the transaction,
Delivering the transaction to the selected contract server.
How to process information. The method of claim 1,
The selecting step,
After extracting a hash value based on a contract corresponding to the transaction, selecting any one of the plurality of contract servers based on the extracted hash value
How to process information. The method of claim 2,
Each of the plurality of contract servers has a range of hash values allocated differently from each other,
The selecting step,
Selecting a contract server in which the range of the allocated hash value includes the extracted hash value from among the plurality of contract servers
How to process information. The method of claim 1,
Each of the plurality of contract servers includes a plurality of configuration servers, and each of the plurality of configuration servers includes an execution unit executing a predetermined contract and a plurality of state databases related to the execution unit.
How to process information. As a computer-readable recording medium storing a computer program,
When the computer program is executed by a processor,
Including instructions for causing the processor to perform the method of any one of claims 1 to 4
Computer-readable recording medium. As a computer program stored in a computer-readable recording medium,
When the computer program is executed by a processor,
Including instructions for causing the processor to perform the method of any one of claims 1 to 4
Computer program. When a predetermined transaction is received from the client application of the blockchain platform, based on the contract corresponding to the transaction, any one of the plurality of contract servers included in the contract executer node of the blockchain platform is selected. With a selection section to choose from,
Including a guarantee node for transmitting the transaction to the selected contract server through the communication unit
Peer node. A contract executer node including a plurality of contract servers,
Including peer nodes,
The peer node,
When receiving a predetermined transaction from the client application of the blockchain platform, based on a contract corresponding to the transaction, a selection unit for selecting any one of the plurality of contract servers,
Including a guarantee node for transmitting the transaction to the selected contract server through the communication unit
Blockchain platform system.

Images