KR101978185B1 - Method for managing license of software based on blockchain, and license management server using the same - Google Patents

Abstract

The present invention executes a license issuance smart contract in response to a license issuance request transaction to generate a license identification value corresponding to a software identification value, and transmits license issuance information including the license identification value to a software provider terminal for license identification. A blockchain-based software license management method for registering a license issuance information in a blockchain database, registering license issuance information in a blockchain database, and registering the license identification value and corresponding license status information in a state database, and using the same. A license management server.

Description

TECHNICAL FOR MANAGING LICENSE OF SOFTWARE BASED ON BLOCKCHAIN, AND LICENSE MANAGEMENT SERVER USING THE SAME}

The present invention relates to a blockchain-based software license management method and a license management server using the same, and more particularly, to identify a license corresponding to a software identification value by executing a license issuing smart contract in response to a license issuance request transaction. A value is generated, and license issuance information including the license identification value is transmitted to the software provider terminal so that the license identification value is managed by matching the software identification value, the license issuance information is registered in the blockchain database, and the license identification value and The present invention relates to a blockchain-based software license management method for registering license status information corresponding thereto in a state database and a license management server using the same.

In general, software is difficult to create, while copying is easy. Creating a good software application can often take hundreds or thousands of hours, but immoral users with regular computers can sometimes copy the same work product in seconds.

Therefore, the software developer applies a technique for managing the license of the software, but some hackers distribute illegally installed or executed software to enable illegal installation.

In particular, there is no way to verify and sanction the licensed software if it is used by a third party who is not authorized to license it.

The present invention aims to solve all the above-mentioned problems.

It is another object of the present invention to prevent an unauthorized person from using the software license arbitrarily.

It is another object of the present invention to make sure that the issued software license is made by an authorized user and used by an authorized user.

It is another object of the present invention to ensure that the integrity of the software license can be verified to ensure that the forgery of the license has not been made.

Representative configuration of the present invention for achieving the above object is as follows.

According to an embodiment of the present invention, in a method for managing a blockchain-based software license, (a) when a license issuance request transaction for software is obtained from a software provider terminal, a license management server requests the license issuance request transaction. Is valid by checking whether the license is valid, the license issuing smart contract is source code that can be compiled into executable bytecode and executed on at least one computing device, and is an identification value for the software. Executing a predetermined procedure to issue a license corresponding to the software identification value; And (b) when the license management server generates a license identification value corresponding to the software identification value by the license issuance smart contract, transmits license issuance information including the license identification value to the software provider terminal. Or by allowing another device linked to the license management server to transmit the license issuance information to the software provider terminal, allowing the software provider terminal to manage the license identification value by matching the software identification value, and the license Register the issuing information in the blockchain database or allow other devices linked to the license management server to register the license issuing information in the blockchain database. Steps to register a sense of status information to the state database; There is provided a method comprising a.

In addition, according to an embodiment of the present invention, in a method for managing a blockchain-based software license, (a) the license management server in response to a license issuance request for software from a software provider terminal, the license issuance smart contract Generates a license identification value corresponding to the software identification value by using a server, and registers the license identification value and corresponding license status information in a state database, and requests a license activation request transaction for the software from the software provider terminal. The license activation request transaction includes a license signature value by signing the software identification value, the license identification value, the public key generated by the software, and the license identification value with a private key generated by the software. Includes-if is obtained, the license management server checks whether the license activation request transaction is valid, and if so, a license activation smart contract-the license activation smart contract is compiled into executable bytecode and at least one Source code that can be executed on a computing device of the computer, and configured to perform a predetermined procedure to activate a license of the software corresponding to the license identification value; And (b) the license management server verifies the public key and the license signature value included in the activation request transaction by the license activation smart contract, and activates the license to activate the license when verification is completed. Generating the license activation information including the activation code to the software provider terminal or by supporting another device linked to the license management server to transmit the license activation information to the software provider terminal. Enable the license activation code to activate a license of the software corresponding to the license identification value, and register the license activation information in a blockchain database or manage the license. Supporting other devices linked to a server to register the license activation information in a blockchain database, and updating license status information corresponding to the license identification value registered in the state database with reference to the license activation information; Provided is a method comprising a.

In addition, according to an embodiment of the present invention, in a method for managing a blockchain-based software license, (a) the license management server in response to a license issuance request for software from a software provider terminal, the license issuance smart contract Generates a license identification value corresponding to the software identification value by registering the license identification value, registers the license identification value and corresponding license status information in a state database, and generates a license activation smart controller in response to a license activation request transaction for the software. Generates an activation code for activating the license by the contract, provided by the software provider terminal in the state of updating the license state information of the state database with reference to license activation information When a license validation request transaction including the license identification value and the license activation code is generated by the existing software and transmitted through the software provider terminal, the license management server checks whether the license validation request transaction is valid. License validation smart contract, wherein the license validation smart contract is source code that can be compiled into executable bytecode and executed on at least one computing device, and corresponds to the license identification value. Executing a predetermined procedure to verify validity of a license; (b) The license management server checks the license identification value and the license activation code from the license status information registered in the state database in correspondence with the license identification value by the license validation smart contract, and licenses the license. Confirm the status of the license identification value, generate a license verification identification value and a nonce value corresponding to the license identification value, and register the license verification identification value and the nonce value in license verification status information of the state database corresponding to the license identification value. Generating a signature request transaction including the license verification identification value and the nonce value and transmitting the signature request transaction to the software through the software provider terminal; And (c) if a signature transaction including the license verification identification value from the software and a signature value signing the nonce value with a private key is obtained through the software provider terminal, the license management server determines that the signature transaction is valid. Verify the signature value and execute a signature verification smart contract corresponding to the signature transaction, verifying the signature value and registering the result information in the blockchain database, and registering the result information through the software provider terminal. Updating the license verification status information corresponding to the license verification identification value registered in the status database with reference to the result information by causing the software to be executed in the user terminal by transferring the information to the license information; There is provided a method comprising a.

In addition, according to an embodiment of the present invention, there is provided a license management server for performing the above methods.

In addition to this, a computer readable recording medium for recording a computer program for executing the method of the present invention is further provided.

According to the present invention, the following effects are obtained.

The present invention has the effect that by using a smart contract (smart contract) is strictly managed rights related to the license of the software to prevent unauthorized use of the software.

In other words, according to the present invention, a license of a software issued once can be confirmed by an authorized user and used by an authorized user.

In addition, the present invention has the effect of ensuring that the forgery of the license is not made by verifying the integrity of the license of the software.

1 schematically illustrates a license management server for managing software licenses according to an embodiment of the present invention.
2 schematically illustrates a method of issuing a software license according to an embodiment of the present invention.
3 schematically illustrates a method of activating a software license according to an embodiment of the present invention,
4 schematically illustrates a method for checking the validity of a software license according to an embodiment of the present invention.
5 and 6 schematically illustrate a process of registering information related to document management in another blockchain database or a public blockchain database according to an embodiment of the present invention.

DETAILED DESCRIPTION The following detailed description of the invention refers to the accompanying drawings that show, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different but need not be mutually exclusive. For example, certain shapes, structures, and characteristics described herein may be embodied in other embodiments without departing from the spirit and scope of the invention with respect to one embodiment. In addition, it is to be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present invention, if properly described, is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. Like reference numerals in the drawings refer to the same or similar functions throughout the several aspects.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention.

FIG. 1 schematically illustrates a license management server managing a blockchain based software license according to an embodiment of the present invention, and the license management server 300 may include a communication unit 310 and a processor 320. have. The same reference numerals are used for the convenience of description and are not intended to mean that these individual devices are the same. In another embodiment of the present invention, the server may be configured differently to perform the method, or the method may be performed through the same server 300.

In addition, the license management server 300 may be composed of a plurality of servers each performing a function related to software license management. In addition, the license management server 300 may be a server corresponding to each node of the blockchain database, or may be a server managing each node of the blockchain database. In addition, the license management server 300 may manage state information of the software license through communication with the state database. The blockchain database may be composed of a first blockchain database and a second blockchain database. In this case, the first blockchain database may be configured as a private blockchain database, and the second blockchain database may be configured as a private blockchain database or a public blockchain database.

Specifically, license management server 300 is typically a computing device (eg, a device that may include components of a computer processor, memory, storage, input and output devices, other conventional computing devices; routers, switches, etc.). Electronic communication devices; electronic information storage systems such as network attached storage (NAS) and storage area network (SAN) and computer software (i.e., instructions that cause a computing device to function in a particular manner). It may be to achieve system performance.

The communication unit 310 of such a computing device may transmit and receive a request and a response with another computing device to be interlocked. For example, the request and response may be made by the same TCP session, but are not limited thereto. For example, it may be transmitted and received as a UDP datagram.

In addition, the processor 320 of the computing device may include a hardware configuration such as a micro processing unit (MPU) or a central processing unit (CPU), a cache memory, a data bus, and the like. In addition, the operating system may further include a software configuration of an application performing a specific purpose.

First, a method of issuing a software license according to an embodiment of the present invention will be described with reference to FIG. 2 through the license management server 300 of FIG. 1.

When the software registrant requests a license for the software registered by the software provider terminal 200 through which the corresponding software is registered and distributed, the software provider terminal 200 issues a license requested by the software registrant. The license issuance request transaction is transmitted to the license management server 300 (S11). In this case, the license issuance request transaction may include a software identification value, which is information about the software to be licensed, but is not limited thereto, and may include a signature value using a software registrant's public key and a software registrant's private key. Can be.

Then, the communication unit 310 of the license management server 300 obtains a license issuance request transaction transmitted from the software provider terminal 200, and the processor 320 of the license management server 300 is obtained from the communication unit 310. Validate the license issuance request transaction (S12).

For example, the license management server 300 may check whether the format format for the obtained license issuance request transaction is valid. In addition, the license management server 300 may check the validity of the license issuance request transaction by checking the signature value from the obtained license issuance request transaction. That is, when the signature value of the license issuance request transaction is a software identification value for the software to be issued using the private key of the software registrant, the license management server 300 issues a license using the public key of the software registrant. The signature value of the request transaction is checked to verify the signed software identification value, and the software identification value confirmed from the signature value matches the software identification value included in the license issuance transaction so that the license issuance transaction is valid and is valid. The signature can be verified by the registrant.

If it is determined that the verification result (S12) is valid, the license management server 300 executes a license issuing smart contract (S13).

At this time, the license issuance smart contract is a source code that can be compiled into executable byte code and executed on at least one computing device, and to perform a predetermined procedure to issue a license for the software in response to a license issuance request transaction. Can be configured.

Then, the license management server 300 generates a license identification value corresponding to a software identification value, which is an identification value for the software for which license issuance is requested, in response to the license issuance smart contract (S14).

In this case, the license management server 300 may obtain a license identification value from the software provider terminal 200 or generate the license identification value with reference to the acquired software identification value. That is, the software registrant may request issuance of a license for the software by matching a specific license identification value with the software identification value, and the license management server 300 uses the license identification value requested for the software to issue a license for the software. You can issue a sense.

The license management server 300 may register license issuance information in the blockchain database 410 or allow other devices linked to the license management server 300 to register license issuance information in the blockchain database 410. In operation S15, a transaction ID indicating a location on the blockchain database 410 of license issuance information registered in the blockchain database 410 may be obtained and managed (S16).

In addition, the license management server 300 may register a license identification value and license status information corresponding thereto in the state database 420 (S17). In this case, the license status information may include at least one of a software identification value, license registration time information, license activation status information, license owner information, license activation code information, and license end time information, but is not limited thereto. The rule information may further include rule information from the activation of the license until the end time.

In addition, the license management server 300 transmits the license issuance information including the license identification value to the software provider terminal 200 or causes another device linked to the license management server 300 to transmit the license issuance information to the software provider terminal 200. In this case, the software provider terminal 200 may manage the license identification value by matching the software identification value.

In the above, the license management server 300 registers license issuance information to the blockchain database 410 (S16), registers license state information to the state database 420 (S17), and license issuance information. Although the operation S18 of transmitting to the provider terminal 200 has been described in sequence, this is merely for the description of the operation and may be executed in a different order in actual operation.

In addition, the above has been described as an example of issuing one license for the software, but, alternatively, a specific number of licenses may be requested for the corresponding software, and in this case, the license management server 300 requests for issuance. Issuance of the requested number of licenses for the corresponding software that performs the license issuance smart contract as many times as the number of times, or the software provider terminal 200 issues a license issuance request transaction as many times as the requested number of issuance. It may be transmitted to the license management server 300.

Next, a method of activating a license according to an embodiment of the present invention will be described with reference to FIG. 3.

The license identification value corresponding to the software identification value by the license issuance smart contract by the license management server 300 in response to the license issuance request for the software from the software provider terminal 200 by the method described with reference to FIG. 2. The user who acquires the corresponding software and license identification value from the software providing terminal 200 while registering the license identification value and corresponding license status information in the state database 420 is generated. When the corresponding software is executed, the software requests the user to input a license identification value according to a preset operating condition.

When the license identification value is input by the user, the software generates a public key and a private key, which are key pairs for user authentication, to be stored in the user terminal 110. At this time, the public key and the private key may be a key pair for the corresponding software or a key pair for the user.

Thereafter, the software of the user terminal 110 receives a license activation request signal including a software identification value, a license identification value, a public key generated by the software, and a license signature value signed by the private identification key generated by the software. In step S21, the software provider server 200 signs the software identification value, the license identification value, the public key generated by the software, and the license identification value with the private key generated by the software. The license activation request transaction including the license signature value is transmitted to the license management server 300 (S22).

Then, the communication unit 310 of the license management server 300 obtains a license activation request transaction transmitted from the software provider terminal 200, and the processor 320 of the license management server 300 is obtained from the communication unit 310. Validate the license activation request transaction (S23). For example, the license management server 300 may check whether the format format for the obtained license activation request transaction is valid.

If it is determined that the verification result (S23) is valid, the license management server 300 executes a license activation smart contract (S24).

At this time, the license activation smart contract is source code that can be compiled into executable byte code and executed on at least one computing device, and is predetermined to activate a license of software corresponding to a license identification value in response to a license activation request transaction. It may be configured to perform a procedure.

Then, the license management server 300 verifies the public key and the license signature value included in the activation request transaction by the license activation smart contract (S25).

For example, when the license value of the license activation request transaction is a signature of a license identification value to be activated using a private key generated by the software, the license management server 300 is configured by the software. Check the signed license identification value by checking the signature value of the license activation request transaction using the generated public key, and check whether the license identification value verified from the signature value matches the license identification value included in the license activation request transaction. You can verify the public key and license signatures.

Thereafter, when the public key and the license signature value are verified, the license management server 300 generates an activation code for activating a license (S26), and receives license activation information including the activation code through the software provider terminal 200. It may be transmitted to the user terminal 110 (S29, S30). That is, the license management server 300 transmits the license activation information to the software provider terminal 200 to activate the license of the software corresponding to the license identification value using the license activation code, or the user terminal 110 or the like. This allows the user to know that the license identification corresponding to the software has been activated.

In addition, the license management server 300 may register the license activation information in the blockchain database 410 or support other devices linked to the license management server 300 to register the license activation information in the blockchain database 410. There is (S27).

In addition, the license management server 300 may update the license state information corresponding to the license identification value registered in the state database 420 with reference to the license activation information (S28).

That is, the license management server 300 may register at least one of a public key, a license activation code, and end time information of the license as license state information corresponding to a license identification value in the state database 420.

In particular, the license management server 300 may update the license activation state information corresponding to the license identification value in the state database 420 to an “active state”. That is, the license activation state information indicates the activation state of the license and may be represented as "inactive state", "active state", "suspended state", or the like depending on conditions.

In operation S29, the license management server 300 transmits the license activation information to the software provider terminal 200, registers the license activation information with the blockchain database 410, and license activation information. Although an operation S28 of updating the state database 420 is sequentially described with reference to FIG. 6, this is merely for explaining an operation and may be executed in a different order in actual operation.

Next, referring to FIG. 4, the validity of the license according to an embodiment of the present invention will be described.

By the method described with reference to FIGS. 2 and 3, the license management server 300 corresponds to the software identification value by the license issuing smart contract in response to a license issuance request for software from the software provider terminal 200. Generates a license identification value, registers the license identification value and corresponding license status information in the state database 420, and licenses the license by a license activation smart contract in response to a license activation request transaction for the software. Generates an activation code for activating, and when the user executes the software installed in the user terminal 110 with the license status information of the state database 420 updated with reference to the license activation information, the software generates a license identification value. License activation When the license validation request signal including the code is transmitted to the software provider terminal 200 (S51), the software provider server 200 performs a license validation request transaction including a license identification value and a license activation code. Give it to 300 (S52).

Then, the communication unit 310 of the license management server 300 obtains a license validation request transaction transmitted from the software provider terminal 200, and the processor 320 of the license management server 300 is obtained from the communication unit 310. The validity of the license validation request transaction is verified (S53). For example, the license management server 300 may check whether the format format for the obtained license validation request transaction is valid.

If it is determined that the verification result (S53) is valid, the license management server 300 executes a license validity verification smart contract (S54).

At this time, the license validation smart contract is source code that can be compiled into executable bytecode and executed on at least one computing device, and performs a predetermined procedure to validate the license of the software corresponding to the license identification value. It can be configured to.

Then, the license management server 300 checks the license identification value and the license activation code from the license status information registered in the state database 420 in response to the license identification value by the license validation smart contract to check the status of the license. Check (S55). That is, it checks whether a license has been issued and activated by referring to the license identification value.

 Then, the license management server 300 generates a license verification identification value and a nonce value corresponding to the license identification value (S56), and the license verification identification value and the license verification status information of the state database 420 corresponding to the license identification value. The nonce value is registered (S57), and a signature request transaction including the license verification identification value and the nonce value is generated and transmitted to the software of the user terminal 110 through the software provider terminal 200 (S58 and S59).

Accordingly, the software of the user terminal 110 generates a signature transaction including a license verification identification value and a signature value signed with a nonce value with a private key in response to the signature request transaction, and generates the generated signature transaction into the software provider terminal 200. In order to be transmitted to the license management server 300 through the (S60, S61).

When a signature transaction including a license verification identification value and a signature value from the software of the user terminal 110 is obtained through the software provider terminal 200, the license management server 300 checks whether the signature transaction is valid and then validates it. In operation S62, a signature verification smart contract corresponding to the signature transaction is executed to verify the signature value.

At this time, the license management server 300 obtains the public key from the license status information registered in the state database 420 with reference to the license identification value matching the license verification identification value, and obtains the public key obtained from the state database 420. The nonce value is checked from the signature value by using, and the nonce value confirmed from the signature value and the license verification identification value correspond to the nonce value registered in the license verification status information of the state database to match the signature value. Can be verified

Subsequently, when the verification result of the signature value (S62) is verified as the validity of the signature value, the license management server 300 registers the verification result information in the blockchain database 410 (S63), and verifies the verification result information on the software provider terminal (S63). The software is executed in the user terminal 110 by transferring the software to the user terminal 110 through the 200 (S65 and S66).

In addition, the license management server 300 may update the license verification status information corresponding to the license verification identification value registered in the status database 420 with reference to the verification result information (S64).

In this case, the license management server 300 may register at least one of a signature value, verification result information, and time information of verifying the signature value in the license verification status information of the state database 420 corresponding to the license verification identification value. .

In the method of FIGS. 2 to 4, the license management server 300 registers information related to software license management in a blockchain database composed of one network. However, the blockchain database is a first blockchain database. In the case of configuring a second database and a second database, information may be registered in the first blockchain database, and a block may be registered in the second blockchain database using Merkle Tree.

For example, if the triggering condition for registering a predetermined hash value in the second blockchain database is satisfied, the license management server 300 generates a license function by applying a hash function to a transaction registered in the first blockchain database 410. By calculating the hash value or at least one neighboring hash value matching the specific hash value, a representative hash value or a value obtained by processing the representative hash value is generated as a merkle root, and the generated hash value or the representative hash value, Register the processed value to the second blockchain database or allow other devices to register the location information on the second blockchain database of the representative hash value or the processed hash value registered in the second blockchain database. It can acquire and manage the transaction ID that indicates.

In this case, at least one of the neighbor hash values may be a hash value generated by applying a hash function to final state information of the state database 420 updated by all transactions included in the block.

In addition, the operation of a specific hash value and at least one neighboring hash value may be performed by various hash functions, and the hash function may be an MD4 function, an MD5 function, a SHA-0 function, a SHA-1 function, a SHA-224 function, It will be appreciated by those skilled in the art that the present invention may include, but is not limited to, an SHA-256 function, an SHA-384 function, an SHA-512 function, and an HAS-160 function. For example, Triple SHA256 would be possible.

In this case, the license management server 300 may store and manage a specific hash value and at least one neighbor hash value in a predetermined data structure. Here, the data structure may vary, for example, may be a merkle tree structure.

That is, the license management server 300 may support to generate or generate a merkle tree in which a specific hash value is assigned to a specific leaf node, and if a predetermined condition is satisfied, at least one matching the specific hash value. A representative hash value generated by calculating a hash value assigned to another leaf node or a processed value of the representative hash value may be registered or registered in the second blockchain database.

More specifically, (x1) the license management server 300 supports or calculates (i) a hash value assigned to a sibling node of a node to which (i) a specific hash value and (ii) a specific hash value is assigned. For example, it may support assigning or assigning a hash value for an operation value to a node's parent node. (x2) If the parent node is the root node of the Merkle tree, the hash value assigned to the parent node becomes the representative hash value. (x3) On the other hand, if the parent node is not the root node of the Merkle tree, the server 100 repeats (x1) to (x3) by using the hash value assigned to the parent node as a specific hash value.

In addition, the license management server 300 supports to register or register the hash value finally assigned to the root node of the Merkle tree as the representative hash value in the second blockchain database. At this time, a value obtained by processing the representative hash value may be registered. For example, a result value of performing a hex operation may be registered in the representative hash value.

Meanwhile, when the license management server 100 stores a specific hash value and at least one neighbor hash value in a predetermined first data structure, and then stores and manages a second data structure having the same form as the first data structure, The first data structure and the second data structure may be connected in a chain form.

In particular, when the first data structure and the second data structure are Merkle trees as in the above-described example, a root value of the first data structure or a hash value of the root value may be allocated to the first leaf node of the second data structure. .

In addition, when the second data structure is generated, data integrity may be more guaranteed by verifying the first data structure. The verification of the second data structure will be described later.

In addition, in the case of the first Merkle tree of at least one Merkle tree connected in a chain form, the first leaf node of the first Merkle tree may be assigned a hash value of a predetermined message data composed of text, numbers, or symbols or a processed value thereof. have. For example, a hash value of an input message initially given by the license management server 300 may be assigned when generating the merkle tree.

5 and 9 illustrate an example of a merkle tree generated according to an embodiment of the present invention.

5 shows a Merkle tree with four leaf nodes. Since the illustrated Merkle tree is the first Merkle tree (tree_id = 0), it can be seen that a hash value (sha256digest (coinplug_unique_message)) of predetermined message data is allocated to the h0 node which is the first leaf node. When there is a registration request for the historical data, the license management server 300 generates the next leaf node of the last leaf node of the Merkle tree currently being configured to assign or assign a specific hash value or a processed value of the specific hash value. Support. For example, when a new leaf node needs to be created while the value allocation is completed from the merkle tree of FIG. 5 to the second leaf node h1, the next leaf node h2 is created to process a specific hash value or a specific hash value. You can assign one value (sha256digest (input2)). In addition, the license management server 300 may support to calculate or calculate (i) a specific hash value assigned to the h2 node and (ii) a hash value assigned to the h3 node that is a sibling node of the h2 node. The hash value for the operation value is assigned to the parent node (h23 node) of node h2 and node h3. Since the parent node (h23 node) is not the root node of the Merkle tree, the license management server 300 may repeat the above process by using the hash value assigned to the h23 node as a specific hash value. That is, the hash value assigned to the h23 node is designated as a specific hash value, and the hash value assigned to the h23 node and the hash value assigned to the h01 node can be calculated and assigned to the parent node (h0123 node) of the h23 node and the h01 node. have. At this time, since the h0123 node is the root node of the Merkle tree, the license management server 300 registers or registers a value (hex (h {node_index})) of the hash value assigned to the h0123 node in the second blockchain database. Can support

Meanwhile, the above-described predetermined conditions, that is, triggering conditions, include (i) a condition in which transactions related to license management are generated by a predetermined number, (ii) a condition in which a predetermined time elapses, and (iii) a first blockchain database. It may include at least one of a condition that the block is generated, (iv) a condition for the service characteristic.

On the other hand, for example, when a plurality of license management transactions are acquired by the number of leaf nodes of the Merkle tree, the Merkle tree may be generated, and the root value of the Merkle tree may be supported or registered in the second blockchain database.

In addition, the license management server 300 may generate the root value of the aforementioned Merkle tree on a predetermined time basis (condition (ii) above). In this case, when a predetermined time elapses, the license management server 300 may generate a Merkle tree by using input values up to that point and register or register a root value of the Merkle tree in the second blockchain database.

In this case, however, a value may not be assigned to a sibling node of a node to which a specific hash value of the Merkle tree is assigned even after a predetermined time has elapsed. When the hash value is not assigned to the sibling node of the node to which the specific hash value is assigned even though the predetermined condition is satisfied as described above, the license management server 300 supports to assign or allocate the predetermined hash value to the sibling node. In one way, the root value of the Merkle tree can be calculated. For example, the license management server 300 may duplicate a specific hash value and assign or assign it to a sibling node.

In addition, when the block is generated in the first blockchain database (condition (iii) above), the license management server 100 registers the last license state information registered in the state database in the block header of the generated block. The state database hash value, which is a hash value for, can be recorded or supported to be recorded.

For example, (i) only the hash values computed from the random nonce, random nonce signature value, and public key are generated from the Merkle tree assigned to the leaf nodes. After only the hash values calculated from the data, public key and signature value are generated from the Merkle Tree assigned to the leaf nodes, the license management information representative hash value, which is the representative hash value, the trader information representative hash value and the license management information representative hash value. In the state further recorded in the block header of the generated block, the license management server 300 removes the state database hash value, the trader information representative hash value, the license management information representative hash value, or a hash value for the processed values thereof. 2 It can also be supported to register or register in the blockchain database.

In addition, the license management server 300 may include (i) hash values computed from random nonce, random nonce signature value and public key, and (ii) hash values computed from license management data, public key and signature value. After the private representative hash value is generated from the Merkle tree assigned to, the state database hash value and the private representative hash value, or these are processed while the private representative hash value is further recorded in the block header of the generated block. A value may be registered or supported to be registered in the second blockchain database.

The service characteristics include cost information provided by the user who requested transaction registration related to license management, time zone information for transaction registration related to license management, region information for transaction registration service related to license management, and transaction registration related to license management. It may be at least part of the type of company that made the request. However, the present invention is not limited to the above description and includes various condition information in which a generally accepted differential service can be provided.

On the other hand, when a new Merkle tree generation is started and a predetermined condition is satisfied in a state where there is no transaction related to license management, the license management server 300 determines whether the license message has been assigned to the first leaf node and the second leaf node. It is possible to support the creation or creation of the tree, and to register or register the root value of the Merkle tree or the processed value in the second blockchain database. In this case, a two leaf node Merkle tree may be created.

Meanwhile, as described above, the license management server 300 stores the specific hash value and the at least one neighbor hash value in a predetermined first data structure, and then stores and manages a second data structure having the same form as the first data structure. In this case, the first data structure and the second data structure may be connected in a chain form. In particular, when the first data structure and the second data structure are Merkle trees, a root value of the first data structure or a hash value of the root value may be assigned to the first leaf node of the second data structure.

6 illustrates a Merkle tree generated as a second data structure according to an embodiment of the present invention.

Referring to FIG. 6, it can be seen that the root value hex (h0123) of the merkle tree (tree_id = 0) of FIG. 5 is allocated to the first leaf node (h4 node) of the new merkle tree (sha256digest (input4)). The present invention has an advantage of improving data integrity by easily tracking even when data is tampered with by connecting a plurality of data structures generated when a transaction occurs.

In addition, the embodiments according to the present invention described above may be implemented in the form of program instructions that may be executed by various computer components, and may be recorded in a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on the computer-readable recording medium may be those specially designed and configured for the present invention, or may be known and available to those skilled in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs, DVDs, and magneto-optical media such as floptical disks. media), and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform the process according to the invention, and vice versa.

Although the present invention has been described by specific embodiments such as specific components and the like, but the embodiments and the drawings are provided to assist in a more general understanding of the present invention, the present invention is not limited to the above embodiments. For those skilled in the art, various modifications and variations can be made from these descriptions.

Accordingly, the spirit of the present invention should not be limited to the above-described embodiments, and all of the equivalents or equivalents of the claims, as well as the appended claims, fall within the scope of the spirit of the present invention. I will say.

110: user terminal,
200: software provider terminal,
300: license management server,
310: communication unit,
320: processor,
410: blockchain database
420: State database

Claims (24)

In the blockchain-based software license management method,
(a) If a license issuance request transaction for the software is obtained from the software provider terminal, the license management server checks whether the license issuance request transaction is valid and is valid, and if it is valid, a license issuing smart contract-the license issuing smart contract. Is source code that can be compiled into executable bytecode and executed on at least one computing device, and is configured to perform a predetermined procedure to issue a license corresponding to a software identification value that is an identification value for the software. Executing; And
(b) when the license management server generates a license identification value corresponding to the software identification value by the license issuance smart contract, transmits license issuance information including the license identification value to the software provider terminal; By supporting other devices linked to the license management server to transmit the license issuance information to the software provider terminal, the software provider terminal matches the license identification value with the software identification value, and issues the license. Register information in the blockchain database or allow other devices linked to the license management server to register the license issuance information in the blockchain database, and the license identification value and the corresponding license Registering the switch status information with the state database;
Method comprising a. The method of claim 1,
The license state information includes at least one of the software identification value, registration time information of the license, activation state information of the license, owner information of the license, activation code information of the license, and end time information of the license. Characterized in that. The method of claim 2,
The license status information further comprises rule information from the activation of the license until the end time. The method of claim 1,
And the license management server obtains the license identification value from the software provider terminal or generates the license identification value with reference to the software identification value. In the blockchain-based software license management method,
(a) The license management server generates a license identification value corresponding to a software identification value by a license issuing smart contract in response to a license issuance request for software from a software provider terminal, and corresponds to the license identification value and the license identification value. A license activation request transaction for the software from the software provider terminal, wherein the license activation information transaction is registered in the state database, wherein the license activation request transaction is the software identification value, the license identification value, and the public key generated by the software. And a license signature value in which the license identification value is signed with a private key generated by the software. If obtained, the license management server determines whether the license activation request transaction is valid. License Activation Smart Contract, if verified and valid, the License Activation Smart Contract is source code that can be compiled into executable bytecode and executed on at least one computing device, the license of the software corresponding to the license identification value. To perform a predetermined procedure to activate a; And
(b) the license management server verifies the public key and the license signature value included in the activation request transaction by the license activation smart contract, and generates an activation code for activating the license when verification is completed. The software provider terminal may be configured to transmit license activation information including the activation code to the software provider terminal or to allow another device interworking with the license management server to transmit the license activation information to the software provider terminal. The license activation code is used to activate a license of the software corresponding to the license identification value, and register the license activation information in a blockchain database or the license management document. Cause the other device to be linked to the updating to the license condition information corresponding to the license information and the activated support to register with the chain block the database, wherein the license identification value registered in the condition database, referring to the enabled license information;
Method comprising a. The method of claim 5,
In step (b),
The license management server checks the license identification value from the license signature value using the public key, and the license identification value confirmed from the license signature value and the license identification value included in the license activation request transaction are determined. Verifying the public key and the license signature value by verifying a match. The method of claim 5,
In step (b),
And the license management server registers at least one of the public key, the license activation code, and end time information of the license into the state database as license state information corresponding to the license identification value. The method of claim 7, wherein
The license management server, characterized in that for updating the license activation state information corresponding to the license identification value in the state database to an active state. The method of claim 5,
The activation request transaction is executed by the software provider terminal with the license identification value and the software is executed in the user terminal and the license identification value is inputted by the software to the public terminal and the private key corresponding thereto. The key is generated and stored, characterized in that generated using the public key and the private key. In the blockchain-based software license management method,
(a) The license management server generates a license identification value corresponding to a software identification value by a license issuing smart contract in response to a license issuance request for software from a software provider terminal, and corresponds to the license identification value and the license identification value. Register license status information to a state database, generate an activation code for activating the license by a license activation smart contract in response to a license activation request transaction for the software, and refer to the license activation information. License validity including the license identification value and the license activation code by the software provided from the software provider terminal in the state of updating the license state information of the state database. When a confirmation request transaction is generated and transmitted through the software provider terminal, the license management server checks whether the license validation request transaction is valid and valid, and if it is valid, a license validation smart contract-the license validation smart controller. A contract is source code that can be compiled into executable bytecode and executed on at least one computing device, and configured to perform a predetermined procedure to validate a license of the software corresponding to the license identification value. Executing;
(b) The license management server checks the license identification value and the license activation code from the license status information registered in the state database in correspondence with the license identification value by the license validation smart contract, and licenses the license. Confirm the status of the license identification value, generate a license verification identification value and a nonce value corresponding to the license identification value, and register the license verification identification value and the nonce value in license verification status information of the state database corresponding to the license identification value. Generating a signature request transaction including the license verification identification value and the nonce value and transmitting the signature request transaction to the software through the software provider terminal; And
(c) if a signature transaction including the license verification identification value from the software and a signature value signing the nonce value with a private key is obtained through the software provider terminal, the license management server determines whether the signature transaction is valid. If it is confirmed and valid, it executes a signature verification smart contract corresponding to the signature transaction, verifies the signature value and registers the result information in the blockchain database, and sends the result information to the software through the software provider terminal. Forwarding the software to be executed in a user terminal, and updating license verification status information corresponding to the license verification identification value registered in the status database with reference to the result information;
Method comprising a. The method of claim 10,
In the step (c),
The license management server obtains a public key from license state information registered in the state database in response to the license identification value matching the license verification identification value, and uses the public key to generate the nonce value from the signature value. Verify the signature value by verifying that the nonce value registered in the license verification state information of the state database corresponds to the nonce value identified from the signature value and the license verification identification value; How to. The method of claim 10,
In the step (c),
The license management server registers at least one of the signature value, the result information, and time information of verifying the signature value in the license verification status information of the state database corresponding to the license verification identification value. How to. A license management server that manages blockchain-based software licenses,
A communication unit for obtaining a license issuance request transaction for software from a software provider terminal; And
(i) if the license issuance request transaction obtained from the communication unit is valid and valid, a license issuance smart contract-the license issuance smart contract is compiled into executable bytecode and executed on at least one computing device; And source code, which is configured to perform a predetermined procedure for issuing a license corresponding to a software identification value that is an identification value for the software, and (ii) the license issuing smart contract. When a license identification value corresponding to the software identification value is generated by the third party, the license issuance information including the license identification value is transmitted to the software provider terminal or the other device linked to the license management server causes the license issuing information to be transmitted. To transmit the license identification value to the software identification value by managing the transmission to the software provider terminal, and register the license issuing information in a blockchain database or interworking with the license management server. A processor for allowing another device to register the license issuing information in a blockchain database and performing a process of registering the license identification value and corresponding license status information in a state database;
License management server comprising a. The method of claim 13,
The license state information includes at least one of the software identification value, registration time information of the license, activation state information of the license, owner information of the license, activation code information of the license, and end time information of the license. License management server, characterized in that. The method of claim 14,
The license status information further includes rule information from the activation of the license until the end time. The method of claim 13,
And the processor obtains the license identification value from the software provider terminal or generates the license identification value with reference to the software identification value. A license management server that manages blockchain-based software licenses,
The license management server generates a license identification value corresponding to a software identification value by a license issuing smart contract in response to a license issuance request for software from a software provider terminal, and the license identification value and corresponding license is generated. In a state in which state information is registered in a state database, a license activation request transaction for the software from the software provider terminal-the license activation request transaction includes the software identification value, the license identification value, a public key generated by the software, and A communication signature to obtain the license identification value, the license signature value being signed with a private key generated by the software; And
(i) if the license activation request transaction obtained from the communication unit is valid and valid, a license activation smart contract-the license activation smart contract is compiled into executable bytecode and executed on at least one computing device And source code that is capable of performing a predetermined procedure to activate a license of the software corresponding to the license identification value, and (ii) the activation by the license activation smart contract. The software provider terminal verifies the public key and the license signature value included in the request transaction, generates an activation code for activating the license when verification is completed, and receives license activation information including the activation code. The software provider terminal by using the license activation code to allow the other device linked to the license management server to transmit the license activation information to the software provider terminal. And activate the license of the license activation information in the blockchain database or register the license activation information in the blockchain database or allow other devices linked to the license management server to register the license activation information in the blockchain database. And updating the license status information corresponding to the license identification value with reference to the license activation information. The method of claim 17,
The processor,
In the above (ii) process,
Verifying the license identification value from the license signature value by using the public key, and verifying that the license identification value identified from the license signature value and the license identification value included in the license activation request transaction match. And verifying a key and the license signature value. The method of claim 17,
The processor,
In the above (ii) process,
And at least one of the public key, the license activation code, and end time information of the license as license status information corresponding to the license identification value, in the status database. The method of claim 19,
And the processor is configured to update license activation state information corresponding to the license identification value to the active state in the state database. The method of claim 17,
The activation request transaction is executed by the software provider terminal with the license identification value and the software is executed in the user terminal and the license identification value is inputted by the software to the public terminal and the private key corresponding thereto. The key is generated and stored, the license management server, characterized in that generated using the public key and the private key. A license management server that manages blockchain-based software licenses,
The license management server generates a license identification value corresponding to a software identification value by a license issuing smart contract in response to a license issuance request for software from a software provider terminal, and the license identification value and corresponding license is generated. Register status information in a status database, generate an activation code for activating the license by a license activation smart contract in response to a license activation request transaction for the software, and refer to the license activation information for the status database. A license including the license identification value and the license activation code generated by the software provided by the software provider terminal in the state of updating the license status information of A communication unit for acquiring a license validation request transaction through the software provider terminal; And
(i) if the license validation request transaction obtained from the communication unit is valid and valid, a license validation smart contract-the license validation smart contract is compiled into executable bytecode and at least one computing Source code executable on the device and configured to perform a predetermined procedure to validate the license of the software corresponding to the license identification value, (ii) the license validation smart controller Confirms the license identification value and the license activation code from the license status information registered in the state database in response to the license identification value, and confirms the license status. Generate a corresponding license verification identification value and a nonce value, register the license verification identification value and the nonce value in license verification status information of the state database corresponding to the license identification value, and register the license verification identification value and the nonce value. A process for generating a signature request transaction that includes a signature request transaction to be transmitted to the software through the software provider terminal, and (iii) a signature value that signs the nonce value with the license verification identification value and private key from the software. If a transaction is obtained through the software provider terminal, verify that the signature transaction is valid and, if valid, execute a signature verification smart contract corresponding to the signature transaction, verifying the signature value and returning the information to the blockchain database. Enroll in License verification status information corresponding to the license verification identification value registered in the status database by executing the software on the user terminal by transferring the result information to the software through the software provider terminal and referring to the result information. A processor for performing a process of updating a;
License management server comprising a. The method of claim 22,
The processor,
In the above (iii) process,
Obtain a public key from license status information registered in the state database in response to the license identification value matching the license verification identification value, verify the nonce value from the signature value using the public key, and sign the signature. And verifying the signature value by checking whether the nonce value identified from the value and the nonce value registered in the license verification state information of the state database correspond to the license verification identification value. The method of claim 22,
The processor,
In the above (iii) process,
And at least one of the signature value, the result information, and time information of verifying the signature value in the license verification status information of the state database corresponding to the license verification identification value.

Images