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

Abstract

According to one embodiment of the present invention, provided is a platooning starting apparatus of a vehicle, which comprises: a communication circuit configured to communicate with at least one external vehicle included in a platooning group with a vehicle; a filter configured to filter particulate matter generated by the vehicle; and a control unit electrically connected with the communication module. If regeneration of the filter is determined to be required during the platooning, at least one of movement operation of the vehicle or a regeneration operation of the filter based on information on an order of the vehicle in the platooning group can be controlled.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a software license management method based on a block chain, and a license management server using the same.

The present invention relates to a software license management method based on a block chain and a license management server using the method. More particularly, the present invention relates to a software license management method using a block chain, And sends the license issuance information including the license identification value to the software provider terminal to match and manage the license identification value with the software identification value, registers the license issuance information in the block chain database, And registering license state information corresponding to the license state information in the state database, and a license management server using the software chain management method.

Generally, software is difficult to create, but easy to copy. Creating good software applications can often take hundreds or thousands of hours, but unethical users with ordinary computers can sometimes copy the same work product in seconds.

Therefore, although the software developer adopts the technique for managing the license of the software, some hackers distribute the installation or execution software that disables the license to illegally install and use it.

In particular, there is no way to identify and sanction software licensed by a third party who is not authorized to do so.

SUMMARY OF THE INVENTION The present invention has been made to solve all the problems described above.

It is another object of the present invention to prevent unauthorized use of a software license arbitrarily.

The present invention is also directed to another purpose of enabling the issued software license to be verified by the authorized user and confirming that the authorized user is using the software license.

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

In order to accomplish the above object, a representative structure of the present invention is as follows.

According to an embodiment of the present invention, there is provided a method of managing a software license based on a block chain, the method comprising the steps of: (a) when a license issuance request transaction for software is obtained from a software provider terminal, The license issued smart contract is source code that is compiled into executable bytecode and can be executed on at least one computing device, and the identification value for the software Executing a predetermined procedure to issue and 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 allowing another device linked to the license management server to transfer the license issuance information to the software provider terminal, thereby allowing the software provider terminal to manage and match the license identification value with the software identification value, The license management server registers the issuance information in the block chain database or other devices connected to the license management server to register the license issuance information in the block chain database, Steps to register a sense of status information to the state database; Is provided.

According to an embodiment of the present invention, there is provided a method for managing a software license based on a block chain, the method comprising the steps of: (a) in response to a license issuance request for software from a software provider terminal, The license identification value corresponding to the software identification value is generated by the software license terminal and the license identification value corresponding to the software identification value is registered in the status database, Wherein the license activation request transaction comprises a software identification value, a license identification value, a public key generated by the software, and a license signature value signed with a private key generated by the software , The license management server verifies the validity of the license activation request transaction and, if valid, a license activated smart contract - the license activated smart contract is compiled into executable bytecode, Executing a predetermined procedure to activate a license of the software corresponding to the license identification value, the source code being executable on a computing device of the computer; 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 transaction, and activates the license when the verification is completed And transmits the license activation information including the activation code to the software provider terminal or to allow another device linked to the license management server to transfer the license activation information to the software provider terminal, To activate the license of the software corresponding to the license identification value using the license activation code, to register the license activation information in the block chain database, Updating the license status information corresponding to the license identification value registered in the status database with reference to the license activation information, by supporting another device connected to the server to register the license activation information in the block chain database; Is provided.

According to an embodiment of the present invention, there is provided a method for managing a software license based on a block chain, the method comprising the steps of: (a) in response to a license issuance request for software from a software provider terminal, The license identification value corresponding to the software identification value is registered in the status database, and the license identification value and the corresponding license status information are registered in the status database, and in response to the license activation request transaction for the software, Wherein the license activation information generating unit generates an activation code for activating the license by the TRAT, and updates the license status information of the status database with reference to the license activation information, When the license validation confirmation request transaction including the license identification value and the license activation code is generated by the software and transmitted through the software provider terminal, the license management server verifies whether or not the license validity confirmation request transaction is valid Wherein the license validation smart contract is source code compiled into executable bytecode and executable on at least one computing device, wherein the license validation confirmation smart contract is source code that is executable on at least one computing device, Executing a predetermined procedure to confirm the validity of the license; (b) the license management server checks the license identification value and the license activation code from the license status information registered in the status database in response to the license identification value by the license validation smart contract, Generates a license verification identification value and a nonce value corresponding to the license identification value, registers the license verification identification value and the nonce value in the license verification status information of the status database corresponding to the license identification value And generating a signature request transaction including the license verification identification value and the nonce value to be transmitted to the software through the software provider terminal; And (c) if a signature transaction is obtained via the software provider terminal, the signature transaction comprising the license verification identity from the software and the signature value that signed the nonce value with a private key, Verifies the signature value, registers the result information in the block chain database, and transmits the result information to the software server via the software provider terminal, if it is valid, and executes a signature verification smart contract corresponding to the signature transaction, To allow the software to be executed in the user terminal and to update license verification status information corresponding to the license verification identification value registered in the status database with reference to the result information; Is provided.

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

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

The present invention has the following effects.

The present invention has the effect of preventing the unauthorized use of the software arbitrarily by using the smart contract so that the authority regarding the license of the software is strictly controlled.

In other words, according to the present invention, the license of the once-issued software can be made by the author and confirmed by the authorized user.

Further, according to the present invention, the integrity of the license of the software is verified, so that there is an advantage that the forgery and falsification of the license is not ensured.

1 schematically shows a license management server for managing software licenses according to an embodiment of the present invention,
2 schematically illustrates a method for issuing a software license according to an embodiment of the present invention,
Figure 3 schematically illustrates a method for activating a software license in accordance with one embodiment of the present invention,
4 schematically illustrates a method for validating software licenses according to an embodiment of the present invention,
5 and 6 schematically illustrate the process of registering information related to document management in another block-chain database or a public-block-chain database according to an embodiment of the present invention.

The following detailed description of the invention refers to the accompanying drawings, which illustrate, 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 features, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in connection with an embodiment. It is also to be understood that the position or arrangement of the individual components within each disclosed embodiment may be varied without departing from the spirit and scope of the invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is to be limited only by the appended claims, along with the full scope of equivalents to which such claims are entitled, if properly explained. In the drawings, like reference numerals refer to the same or similar functions throughout the several views.

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 carry out the present invention.

FIG. 1 schematically illustrates a license management server for managing software licenses based on a block chain according to an embodiment of the present invention. The license management server 300 may include a communication unit 310 and a processor 320 have. The use of the same reference numerals is for convenience of explanation only and is 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 corresponding method, or may perform the corresponding method through the same server 300.

In addition, the license management server 300 may be composed of a plurality of servers each performing functions in relation to software license management. Also, the license management server 300 may be a server corresponding to each node of the block-chain database, or a server managing each node of the block-chain database. In addition, the license management server 300 can manage status information of the software license through communication with the status database. The block-chain database may be composed of a first block-chain database and a second block-chain database. In this case, the first block chain database may be a private block chain database, and the second block chain database may be a private block chain database or a public block chain database.

In particular, the license management server 300 typically includes a computing device (e.g., a computer processor, memory, storage, input and output devices, and other devices capable of including components of a conventional computing device; Electronic communication devices, electronic information storage systems such as Network Attached Storage (NAS) and Storage Area Networks (SAN)) and computer software (i. E., Instructions that cause a computing device to function in a particular manner) System performance.

The communication unit 310 of such a computing device can send and receive requests and responses to and from other interworking computing devices. As an example, such requests and responses can be made by the same TCP session, For example, as a UDP datagram.

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, and a data bus. It may further include a software configuration of an operating system and an application that performs 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 as follows.

When the software registrant requests the license issuance of the software registered by the software registrant to the software provider terminal 200 in which the software is registered and distributed through the registrant terminal, the software provider terminal 200 issues the license requested by the software registrant To the license management server 300 (S11). At this time, the license issuance request transaction may include a software identification value, which is information on the software to be issued a license, but is not limited thereto, and may include a public key of the software registrant, a signature value using the software registrant's private key, .

The communication unit 310 of the license management server 300 acquires a license issuance request transaction transmitted from the software provider terminal 200 and the processor 320 of the license management server 300 receives the license issuance request transaction The validity of the license issuing request transaction is verified (S12).

For example, the license management server 300 can confirm the validity of the format format for the acquired license issue request transaction. Also, the license management server 300 can confirm 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 signifies the software identification value for the software to be issued using the private key of the software registrant, the license management server 300 uses the public key of the software registrant to issue a license Checking the signature value of the request transaction to check the signed software identification value, checking whether the software identification value verified from the signature value matches the software identification value included in the license issuance request transaction, so that the license issuance request transaction is valid and the normal software It can be confirmed whether it is signed by the registrant.

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

At this time, the license-issued 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 issue a license to the software in response to the license issuing request transaction Lt; / RTI >

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

At this time, the license management server 300 may obtain the license identification value from the software provider terminal 200, or may refer to the acquired software identification value. That is, the software registrant can request the license issuance for the software by matching the specific license identification value with the software identification value. The license management server 300 can use the license identification value requested for issuance for the software, I can give you a sense.

The license management server 300 then registers the license issuance information in the block chain database 410 or the other device linked to the license management server 300 to register the license issuance information in the block chain database 410 (S15) and acquire and manage the transaction ID indicating the location on the block chain database 410 of the license issuance information registered in the block chain database 410 (S16).

In addition, the license management server 300 may register the license identification value and the corresponding license status information in the status database 420 (S17). At this time, the license status information may include at least one of a software identification value, registration time information of the license, license activation status information, license owner information, license activation code information, and license end time information, , And may further include rule information up to the end time after activation of the license.

The license management server 300 also transmits the license issuance information including the license identification value to the software provider terminal 200 or allows the other device linked to the license management server 300 to transmit the license issuance information to the software provider terminal 200 ) So that the software provider terminal 200 can manage the license identification value by matching with the software identification value.

The license management server 300 registers the license issuance information in the block chain database 410 (S16), the license status information is registered in the state database 420 (S17), and the license issuance information is software To the provider terminal 200, the operation S18 is sequentially described. However, this operation is merely an explanation of the operation and may be executed in different orders in actual operation.

In the above description, one license issuance is exemplarily described for the software. Alternatively, a certain number of license issuance requests may be issued to the corresponding software, and in this case, the license management server 300 determines the number The software provider terminal 200 issues a license issuance request transaction a number of times corresponding to the number requested to be issued by the software provider terminal 200 Or may be transferred 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.

2, the license management server 300 acquires the license identification value corresponding to the software identification value by the license issuance smart contract in response to the license issuance request for the software from the software provider terminal 200 A user who has obtained the license identification value from the software providing terminal 200 and the license identification information corresponding to the license identification value are registered in the state database 420, The software requests the user to input the license identification value in accordance with the predetermined operating conditions.

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, and stores the public key and the private key 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 generates 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 with a private key generated by the software, (S21) to the software provider server 200, the software provider server 200 transmits 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 And transmits a license activation request transaction including a license signature value to the license management server 300 (S22).

The communication unit 310 of the license management server 300 acquires the license activation request transaction transmitted from the software provider terminal 200 and the processor 320 of the license management server 300 receives the license activation request transaction The validity of the license activation request transaction is verified (S23). In one example, the license management server 300 can confirm the validity of the format format for the acquired license activation request transaction.

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

Wherein the license activated smart contract is source code compiled into executable bytecode and executable on at least one computing device and is operable to generate a predefined license to activate the license of the software corresponding to the license identification value in response to the license activation request transaction, Procedures to be performed.

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 signature value of the license activation request transaction signifies the license identification value to be activated by using the private key generated by the software, the license management server 300 can acquire The signature value of the license activation request transaction is checked using the generated public key to check the signed license identification value and whether or not the license identification value determined from the signature value matches the license identification value included in the license activation request transaction You can verify the public key and license signature value.

Thereafter, when the public key and the license signature value are verified, the license management server 300 generates an activation code for activating the license (S26), and transmits the license activation information including the activation code to the software provider terminal 200 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, activates the license of the software corresponding to the license identification value using the license activation code, It is possible to know information indicating that the license identification value corresponding to the software is activated.

The license management server 300 can also register the license activation information in the block chain database 410 or allow another device linked to the license management server 300 to register the license activation information in the block chain database 410 (S27).

Also, the license management server 300 can update the license status information corresponding to the license identification value registered in the status database 420 by referring to the license activation information (S28).

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

In particular, the license management server 300 can update the license activation status information corresponding to the license identification value in the status database 420 to " active status ". That is, the license activation status information indicates an activation status of the license, and may be indicated as " inactive status ", " active status ", "

The license management server 300 transmits the license activation information to the software provider terminal 200 (S29), the license activation information is registered in the block chain database 410 (S27), and the license activation information (S28) of updating the state database 420 are sequentially described with reference to FIG. 5, but this is merely an explanation of the operation and may be executed in different orders in actual operation.

Next, the validity of the license according to the embodiment of the present invention will be described with reference to FIG.

2 and 3, the license management server 300 responds to the software identification value by the license issuance smart contract in response to the license issuance request for the software from the software provider terminal 200 And registering the license identification value and the corresponding license status information in the status database 420. In response to the license activation request transaction for the software, the license activation smart transaction generates a license identification value When the user executes the software installed in the user terminal 110 in a state where the license status information of the status database 420 is updated with reference to the license activation information, Activate License (S51), the software provider server 200 sends a license validity confirmation request transaction including the license identification value and the license activation code to the license management server 200 (Step S52).

The communication unit 310 of the license management server 300 acquires the license validation request transaction transmitted from the software provider terminal 200 and the processor 320 of the license management server 300 acquires And validates the license validation request transaction (S53). For example, the license management server 300 can check whether the format of the acquired license validation request transaction is valid.

If it is determined that the verification result (S53) is valid, the license management server 300 executes the license validation confirmation 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 check the validity of the software license corresponding to the license identification value .

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

 Then, the license management server 300 generates a license verification identification value and a nonce value corresponding to the license identification value (S56), adds the license verification identification value to the license verification status information of the state database 420 corresponding to the license identification value (S57). The 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, S59).

The software of the user terminal 110 thus generates a signature transaction that includes a signature value that signifies the license verification identity and the nonce value with the private key in response to the signature request transaction and sends the generated signature transaction to the software provider terminal 200 To the license management server 300 (S60, S61).

When the signature transaction including the license verification identification value and the signature value from the software of the user terminal 110 is acquired through the software provider terminal 200, the license management server 300 confirms whether the signature transaction is valid, , The signature verification smart contract corresponding to the signature transaction is executed to verify the signature value (S62).

At this time, the license management server 300 obtains the public key from the license status information registered in the state database 420 by referring to the license identification value matched with the license verification identification value, and outputs the public key obtained from the state database 420 Verifies the nonce value from the signature value, confirms whether the nonce value registered in the license verification state information of the state database matches the nonce value and the license verification identification value confirmed from the signature value, Can be verified.

Thereafter, the license management server 300 registers the verification result information in the block chain database 410 (S63), and verifies the verification result information to the software provider terminal (S62) 200 to the software of the user terminal 110 so that the software is executed in the user terminal 110 (S65, S66).

Also, 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 by referring to the verification result information (S64).

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

2 to 4, the license management server 300 registers information related to software license management in a block chain database composed of one network. Alternatively, the block chain database may be registered in the first block chain database And the second database, the information may be registered in the first block chain database, and the block may be registered in the second block chain database using the merge tree.

For example, when the triggering condition for registering a predetermined hash value in the second block chain database is satisfied, the license management server 300 applies the hash function to the transaction registered in the first block chain database 410 A representative hash value or a representative hash value is processed by calculating a specific hash value and at least one neighbor hash value matched with the specific hash value to generate a representative hash value or a representative hash value And stores the processed value in the second block chain database or supports other devices to register the position information on the second block chain database of the value obtained by processing the representative hash value or the representative hash value registered in the second block chain database And acquire and manage the transaction ID indicating the transaction ID.

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

The hash function may be an MD4 function, an MD5 function, an SHA-0 function, a SHA-1 function, a SHA-224 function, A SHA-256 function, an SHA-384 function, a SHA-512 function, and a HAS-160 function. For example, Triple SHA256 would be possible.

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

That is, the license management server 300 can support a particular hash value to create or generate a merkle tree that is assigned to a particular leaf node, and if a predetermined condition is met, A representative hash value or a representative hash value generated by computing a hash value assigned to another leaf node may be registered or registered in the second block chain database.

More specifically, (x1) the license management server 300 supports to calculate or operate a hash value assigned to (i) a particular hash value and (ii) a sibling node of the node to which the particular hash value is assigned , And to assign or assign a hash value for the operation value to the parent node of the node. (x2) If the parent node is the root node of the merge tree, the hash value assigned to the parent node is the representative hash value. (x3). On the other hand, if the parent node is not the root node of the merge tree, the server 100 repeats (x1) to (x3) with the hash value assigned to the parent node as a specific hash value.

Then, the license management server 300 supports to register or register the hash value assigned to the root node of the merge tree as a representative hash value in the second block chain database. At this time, a value obtained by processing the representative hash value may be registered. For example, a result obtained by performing a hex operation on a representative hash value may be registered.

On the other hand, 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 of the same type as the first data structure, The first data structure and the second data structure may be connected in a chain form.

In particular, if the first data structure and the second data structure are merc trees as in the above example, the root value of the first data structure or the hash value of the root value may be assigned to the first leaf node of the second data structure .

Further, when the second data structure is generated, verification of the first data structure is performed, so that data integrity can be further ensured. Verification of the second data structure will be described later.

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

5 and 9 are diagrams illustrating examples of a merge tree generated according to an embodiment of the present invention.

FIG. 5 shows a merge tree having four leaf nodes. Since the illustrated merge tree is the first merge tree (tree_id = 0), it can be seen that a hash value (sha256digest (coinplug_unique_message)) of predetermined message data is assigned to the first leaf node h0. If there is a registration request for the record data, the license management server 300 generates a next leaf node of the last leaf node of the currently configured merge tree and allocates or assigns a value obtained by processing a specific hash value or a specific hash value Support. For example, if a new leaf node needs to be created in a state where value assignment from the merge tree to the h1 node as the second leaf node is completed, a h2 node, which is a next leaf node, is generated to process a specific hash value or a specific hash value One value (sha256digest (input2)) can be assigned. Also, the license management server 300 can support to calculate or calculate (i) a particular hash value assigned to the h2 node and (ii) the hash value assigned to the h3 node which is the sibling node of the h2 node. The hash value for the operation value is assigned to the h2 node and the parent node (h23 node) of the h3 node. Since the parent node (h23 node) is not the root node of the merge tree, the license management server 300 can repeat the above process with the hash value assigned to the h23 node as a specific hash value. That is, the hash value assigned to the h23 node is a specific hash value, and the hash value assigned to the h23 node and the hash value assigned to the h01 node are calculated and assigned to the h23 node and the parent node (h0123 node) of the h01 node have. At this time, since the h0123 node is the root node of the merge tree, the license management server 300 registers the value (hex (h {node_index})) obtained by processing the hash value assigned to the node h0123 in the second block chain database .

(Ii) a condition that a predetermined time elapses; (iii) a condition in which a transaction related to license management is generated for a predetermined number of times; A condition under which a block is created, and (iv) a condition for a service characteristic.

On the other hand, for example, when a plurality of license management transactions are acquired for the number of leaf nodes of a merge tree, a merge tree can be created, and the root value of the merge tree can be registered or registered in the second block chain database.

Also, the license management server 300 can generate the aforementioned root value of the merge tree in a predetermined time unit (condition (ii)). In this case, the license management server 300 may generate a merge tree using the input values up to that time and register or register the root value of the merge tree in the second block chain database.

In this case, although a predetermined time has elapsed, a value may not be assigned to a sibling node of a node to which a particular hash value of the merge tree is assigned. If the hash value is not assigned to the sibling node of the node to which the specific hash value is allocated even though the predetermined condition is satisfied, the license management server 300 supports to assign or assign a predetermined hash value to the sibling node, The route value of the merge tree can be calculated in one way. For example, the license management server 300 may support copying and assigning or assigning a particular hash value to a sibling node.

In addition, the license management server 100 may further include, when a block is generated in the first block chain database (the condition (iii)), the final block status information registered in the status database in the block header of the generated block May be recorded or recorded in the state database hash value.

For example, (i) only the hash values calculated from the random nonce, the random nonce signature value and the public key are generated from the merge tree assigned to the leaf nodes, the representative hash value being the representative hash value, (ii) After the license management information representative hash value, which is a representative hash value, is generated from the merge tree allocated to the leaf nodes, only the hash values calculated from the data, the public key, and the signature value are used to generate the representative information hash value and the license management information representative hash value The license management server 300 deletes the hash value of the state database hash value, the trader information representative hash value, and the license management information representative hash value, or the value obtained by processing them, into the block header of the generated block 2 block chain database.

In addition, the license management server 300 may further include hash values computed from (i) random nonce, random nonce signature value, and hash value computed from the public key, and (ii) license management data, public key, After the private representative hash value is generated from the merge tree assigned to the generated block, the private representative hash value is further recorded in the block header of the generated block, or the private database hash value and the private representative hash value, And register or register a value in the second block chain database.

The service characteristic includes information on the cost, information on time of the transaction registration related to the license management, area information on which the transaction registration service related to the license management is performed, transaction registration related to the license management It may be at least a part of the company type information that made the request. However, the present invention is not limited to the one described here, but includes various condition information in which a generally accepted differential service can be provided.

On the other hand, when a new merge tree generation is started and a predetermined condition is satisfied in a state in which there is no transaction related to license management, the license management server 300 judges that the predetermined message data is the first leaf node and the second leaf node, Tree, and can support registering or registering the root value of the merge tree or the processed value in the second block chain database. In this case, a merge tree with two leaf nodes may be created.

Meanwhile, as described above, the license management server 300 stores a specific hash value and at least one neighbor hash value in a predetermined first data structure, stores the second data structure in 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, if the first data structure and the second data structure are merc trees, the root value of the first data structure or the hash value of the root value may be assigned to the first leaf node of the second data structure.

6 is a diagram illustrating a merge 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 merge tree (tree_id = 0) of FIG. 5 is assigned to the first leaf node (h4 node) of the new merge tree (sha256digest (input4)). The present invention has an advantage of improving data integrity by enabling easy tracking even when data is modulated in the middle by connecting a plurality of data structures generated at the time of occurrence of a transaction.

In addition, the embodiments of the present invention described above can be implemented in the form of program instructions that can be executed through various computer components and recorded in a computer-readable recording medium. The computer-readable recording medium may include program commands, data files, data structures, and the like, alone or in combination. The program instructions recorded on the computer-readable recording medium may be those specially designed and constructed for the present invention or may be those known and used by 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 and DVDs, 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 machine language code such as those generated by a compiler, as well as 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 for performing the processing according to the present invention, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, Those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims.

Therefore, the spirit of the present invention should not be construed as being limited to the above-described embodiments, and all of the equivalents or equivalents of the claims, as well as the following claims, I will say.

110: user terminal,
200: software provider terminal,
300: license management server,
310: communication unit,
320: processor,
410: Block Chain Database
420: state database

Claims (24)

A method for managing software licenses based on block chaining,
(a) When a license issuance request transaction for software is obtained from a software provider terminal, the license management server checks whether the license issuance request transaction is valid, and if valid, issues a license issued smart contract - The source code 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 the license identification value corresponding to the software identification value by the license issuance smart contract, transmits the license issuance information including the license identification value to the software provider terminal Allowing another device connected to the license management server to transfer the license issuance information to the software provider terminal, thereby allowing the software provider terminal to manage and match the license identification value with the software identification value, Information to the block chain database, or to allow another device linked to the license management server to register the license issuance information in the block chain database, and the license identification value and the corresponding license Registering the state information in the state database;
≪ / RTI > The method according to claim 1,
Wherein the license status information includes at least one of the software identification value, the registration time information of the license, the activation status information of the license, the owner information of the license, the activation code information of the license, . ≪ / RTI > 3. The method of claim 2,
Wherein the license status information further includes rule information from activation to end time of the license. The method according to claim 1,
Wherein 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. A method for managing software licenses based on block chaining,
(a) a 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, The license activation request transaction for the software from the software provider terminal, wherein the license activation request transaction is registered in the state database with the software identification value, the license identification value, the public key generated by the software And a license signing value obtained by signing the license identification value with a private key generated by the software, the license management server determines whether the license activation request transaction is valid or not Wherein the license activation smart contract is source code compiled into executable bytecode and executable on at least one computing device, wherein the license activation smart contract is a license of the software corresponding to the license identification value The method comprising the steps of: 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 the verification is completed And transmitting the license activation information including the activation code to the software provider terminal or allowing another device coupled to the license management server to transmit the license activation information to the software provider terminal, Activate the license of the software corresponding to the license identification value using the license activation code, register the license activation information in the block chain database, 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;
≪ / RTI > 6. The method of claim 5,
In the step (b)
Wherein the license management server checks the license identification value from the license signature value using the public key, and if the license identification value identified from the license signature value and the license identification value included in the license activation request transaction are And verifying that the public key and the license signature value match. 6. The method of claim 5,
In the step (b)
Wherein the license management server registers at least one of the public key, the license activation code, and the end time information of the license in the status database with the license status information corresponding to the license identification value. 8. The method of claim 7,
Wherein the license management server updates license activation status information corresponding to the license identification value in the status database to an active status. 6. The method of claim 5,
Wherein the activation request transaction is a transaction in which the software provided by the software provider terminal with the license identification value is executed in the user terminal and the license identification value is input to the user terminal by the software, A key is generated and stored, and is generated using the public key and the private key. A method for managing software licenses based on block chaining,
(a) a 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 activating the license by the license activation smart contract in response to the license activation request transaction for the software, wherein the license activation information generation unit generates the activation code by referring to the license activation information, Wherein the software provided by the software provider terminal updates the license status information of the status database, and the license validity code including the license identification value and the license activation code A license validation confirmation transaction is generated and transmitted through the software provider terminal, the license management server verifies whether the license validation request transaction is valid, and if valid, a license validation confirmation smart contract - Wherein the TRIT is source code compiled into executable bytecode and executable on at least one computing device and configured to perform a predetermined procedure to validate the 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 status database in response to the license identification value by the license validation smart contract, Generates a license verification identification value and a nonce value corresponding to the license identification value, registers the license verification identification value and the nonce value in the license verification status information of the status database corresponding to the license identification value And generating a signature request transaction including the license verification identification value and the nonce value to be transmitted to the software through the software provider terminal; And
(c) if a signature transaction comprising the license verification identity from the software and the signature value that signed the nonce value with a private key is obtained through the software provider terminal, then the license management server determines whether the signature transaction is valid Verifies the signature value, registers the result information in a block chain database, and transmits the result information to the software through the software provider terminal, if it is valid, executes a signature verification smart contract corresponding to the signature transaction, The license verification status information corresponding to the license verification identification value registered in the status database by referring to the result information;
≪ / RTI > 11. The method of claim 10,
In the step (c)
Wherein the license management server obtains a public key from license state information registered in the state database in correspondence with the license identification value matched with the license verification identification value and extracts the nonce value from the signature value using the public key And verifies whether or not the nonce value registered in the license verification state information of the state database coincides with the nonce value and the license verification identification value confirmed from the signature value to verify the signature value. How to. 11. 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 the time information obtained by verifying the signature value in the license verification state information of the state database corresponding to the license verification identification value How to. A license management server for managing a software license based on a block chain,
A communication unit for acquiring a license issuance request transaction for software from a software provider terminal; And
(i) validating the validity of the license issuance request transaction obtained in the communication unit and, if valid, issuing a license-issued smart contract, the license-issued smart contract being compiled into executable bytecode and executed on at least one computing device And executing a predetermined procedure for issuing and issuing a license corresponding to a software identification value that is an identification value for the software, and (ii) a process for executing the license-issuing smart contract When the license identification value corresponding to the software identification value is generated by the license management server, the license issuance information including the license identification value is transmitted to the software provider terminal, To the software provider terminal, thereby allowing the software provider terminal to manage and match the license identification value with the software identification value, to register the license issuance information in the block chain database, or to register the license issuance information in the block chain database A processor for supporting another device to register the license issuance information in the block chain database, and for registering the license identification value and corresponding license status information in a state database;
To the license management server. 14. The method of claim 13,
Wherein the license status information includes at least one of the software identification value, the registration time information of the license, the activation status information of the license, the owner information of the license, the activation code information of the license, To the license management server. 15. The method of claim 14,
Wherein the license status information further includes rule information from the activation to the end time after activation of the license. 14. The method of claim 13,
Wherein the processor obtains the license identification value from the software provider terminal or refers to the software identification value to generate the license identification value. A license management server for managing a software license based on a block chain,
The license management server generates a license identification value corresponding to the software identification value by the license issuing smart contract in response to the license issuance request for the software from the software provider terminal, A license activation request transaction for the software from the software provider terminal, wherein the license activation request transaction registers the software identification value, the license identification value, the public key generated by the software, And a license signing value obtained by signing the license identification value with a private key generated by the software; And
(i) validating the validity of the license activation request transaction obtained at the communication unit, and if valid, a license activated smart contract, the license activated smart contract being compiled into executable bytecode and executed on at least one computing device And performing a predetermined procedure to activate a license of the software corresponding to the license identification value, and (ii) a process for executing the activation by the license activated smart contract, And generating an activation code for activating the license when the verification is completed, and transmitting the license activation information including the activation code to the software provider terminal Or allowing another device connected to the license management server to transmit the license activation information to the software provider terminal, thereby causing the software provider terminal to transmit the license activation code to the software corresponding to the license identification value using the license activation code The license activation information is registered in the block chain database or the other device linked to the license management server registers the license activation information in the block chain database, And updates the license status information corresponding to the license identification value with reference to the license activation information. 18. The method of claim 17,
The processor comprising:
In the (ii) process,
Wherein the public key is used to identify the license identification value from the license signature value, and if the license identification value identified from the license signature value matches the license identification value included in the license activation request transaction, Key and the license signature value. 18. The method of claim 17,
The processor comprising:
In the (ii) process,
And registers at least one of the public key, the license activation code, and the end time information of the license in the status database with the license status information corresponding to the license identification value. 20. The method of claim 19,
Wherein the processor updates license activation status information corresponding to the license identification value in the status database to an active status. 18. The method of claim 17,
Wherein the activation request transaction is a transaction in which the software provided by the software provider terminal with the license identification value is executed in the user terminal and the license identification value is input to the user terminal by the software, A key is generated and stored, and the generated license key is generated using the public key and the private key. A license management server for managing a software license based on a block chain,
The license management server generates a license identification value corresponding to the software identification value by the license issuing smart contract in response to the license issuance request for the software from the software provider terminal, And generates an activation code for activating the license by the license activation smart contract in response to the license activation request transaction for the software, The license identification information and the license activation code generated by the software provided by the software provider terminal and the license activation code, A communication unit for acquiring a validation confirmation request transaction through the software provider terminal; And
(i) validating the validity of the license validation request transaction obtained at the communication unit and validating the validity of the license validation smart contract, the license validation smart contract being compiled into executable bytecode, And executing a predetermined procedure to confirm the validity of the license of the software corresponding to the license identification value, (ii) a process of executing the license validation confirmation smart key The state of the license is confirmed by checking the license identification value and the license activation code from the license status information registered in the status database corresponding to the license identification value by the track, And generates the license verification identification value and the nonce value corresponding to the license verification value and the nonce value, registers the license verification identification value and the nonce value in the license verification state information of the state database corresponding to the license identification value, And (iii) a signature including a signature value obtained by signing the nonce value with the license verification identification value from the software and the private key, If the signature transaction is valid, executing a signature verification smart contract corresponding to the signature transaction if valid, and verifying the signature value, and transmitting the result information to the block chain database To register , And the result information is transmitted to the software through the software provider terminal, so that the software is executed in the user terminal, and a license verification status corresponding to the license verification identification value registered in the status database A processor for performing a process of updating information;
To the license management server. 23. The method of claim 22,
The processor comprising:
In the process (iii)
Acquiring a public key from license state information registered in the state database corresponding to the license identification value matched with the license verification identification value, verifying the nonce value from the signature value using the public key, And verifies whether or not the nonce value registered in the license verification state information of the state database coincides with the nonce value and the license verification identification value, which have been confirmed from the value of the license verification state information, to verify the signature value. 23. The method of claim 22,
The processor comprising:
In the process (iii)
And registers at least one of the signature value, the result information, and the time information obtained by verifying the signature value in the license verification state information of the state database corresponding to the license verification identification value.

Images