JP2020030454A - Information processing system, information processing apparatus, information processing method and information processing program - Google Patents

Abstract

To provide a license management system capable of improving an independence and a stability of a service.SOLUTION: A provider terminal apparatus 20 performs an encryption processing on an input application, outputs an encrypted application, gives a license based on a request from a user terminal apparatus 10, and transmits license information to a block-chain network. The user terminal apparatus 10 inquires to the block-chain network when starting the encrypted application, performs license authentication processing that confirms whether or not a valid license exists, and decrypts the encrypted application to make it possible to run when the valid license is confirmed.SELECTED DRAWING: Figure 2

Description

  The present invention relates to an information processing system, and more particularly to a system that manages licenses of software and the like using a block chain.

Conventionally, when using application software (hereinafter simply referred to as an application) or digital contents such as music and electronic books (hereinafter simply referred to as contents), it is determined whether or not the user has a valid license. This was determined by a so-called client-server system.
In a conventional method, a client device transmits a permission request to a server device when executing or using an application or content. The server device that has received the permission request verifies the permission request and transmits the permission information to the client device. The client device can execute the application or the content in response to receiving the license information.
The permission request transmitted by the client device is, for example, a pair of identification information (user ID) for specifying the client device or the user and a license code. The server device receiving such identification information refers to the authentication database, and if the corresponding pair is registered in the database, transmits the permission information to the client device.
Alternatively, in the system disclosed in Patent Document 1, a user terminal (client device) includes a key generation unit, a permission request unit, and a content use unit. The key generation unit generates a first key pair and a second key pair. The permission request unit transmits a permission request including the public encryption key of the second key pair by electronically signing it with the secret encryption key of the first key pair.
On the other hand, the right holder terminal (server device) includes a key management unit, a license verification unit, and a license issuing unit. The key management unit stores the third key pair and the content decryption key. The permission verification unit verifies the permission request received from the user terminal. The license issuing unit encrypts the content decryption key using the public encryption key of the second key pair included in the license request, and converts the license information including the encrypted content decryption key with the secret encryption key of the third key pair. Send a digital signature.
The content use unit of the user terminal that has received the license information acquires a content decryption key from the license information using the secret decryption key of the second key pair, and uses the content.

JP-A-2017-050763

Conventionally, license authentication (cloud authentication) based on a client-server system has the following problems. That is, when the server device and the right holder terminal are inactive due to a failure or maintenance, license authentication cannot be performed. Furthermore, if the entity that granted the license terminates the service and terminates the operation of the server device or the right holder terminal, authentication can no longer be performed, and the use of applications and contents becomes impossible. .
The present invention has been made in view of the above problems, and has as its object to provide a system capable of executing license authentication of an application or content stably and continuously.

The present invention has been made to solve the above-mentioned problem, and can be realized by the following modes.
A first embodiment includes a first device and a second device, wherein the first device performs an encryption process on input data and outputs encrypted data. A license granting unit that grants a license related to the data to a user of the second device, and sends license information related to the license grant to a blockchain network. The apparatus includes: a license authentication processing unit that performs authentication based on the license information recorded on a block chain when using the encrypted data; and a decryption process that performs decryption processing on the encrypted data when the authentication is successful. And an information processing system comprising:
In a second mode, an encryption processing unit that performs encryption processing of input data and outputs encrypted data, and a license for the data is provided to a user of another apparatus, and the license is provided. And a license assignment processing unit for sending license information related to the assignment to the blockchain network.
A third mode is a license authentication processing unit that performs authentication based on license information stored on a block chain when using encrypted data, and a decryption process on the encrypted data when the authentication is successful. And a decoding processing unit that performs the decoding.
According to a fourth aspect, an encryption processing unit that performs encryption processing on data to generate encrypted data, and a code for inquiring a blockchain network about license information of the encrypted data when using the encrypted data, An information processing apparatus comprising: an adding unit that adds the encrypted data at the time of encryption processing.
A fifth aspect is an information processing method executed by a computer, which performs an encryption process on data, generates encrypted data, and uses license information of the encrypted data in a block chain when the encrypted data is used. An information processing method for adding a code for inquiring a network to the encrypted data at the time of the encryption processing.
In a sixth mode, a code for performing encryption processing on data, generating encrypted data, and inquiring a blockchain network for license information of the encrypted data when using the encrypted data, An information processing program for causing a computer to execute a process of adding to encrypted data is characterized.

  With the configuration described above, according to the present invention, it is possible to realize a system capable of stably and continuously executing license authentication of applications and contents.

It is a schematic diagram showing a system configuration of the present embodiment. FIG. 1 is a diagram illustrating an outline of a license management system according to an embodiment. FIG. 2 is a diagram illustrating a functional configuration of a user terminal device that executes an application in the embodiment. FIG. 2 is a diagram illustrating a functional configuration of a provider terminal device that provides an application in the embodiment. FIG. 9 is a diagram illustrating an encryption application generated by an encryption tool. It is a flowchart explaining the application encryption processing which a provider terminal device performs. 9 is a flowchart illustrating an application startup process executed by the user terminal device. 8 is a flowchart illustrating a license authentication process in FIG. 7. It is a flowchart explaining the license granting process which a provider terminal device performs. It is a flowchart explaining the license transfer process which a user terminal device performs.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a schematic diagram illustrating a system configuration of the present embodiment.
FIG. 1A is a schematic diagram illustrating a network configuration according to the system of the present embodiment.
In the system 1 according to the present embodiment, a user terminal device 10 used by a user of an application and a provider terminal device 20 used by a provider (developer) of the application are interconnected via the Internet. ing.
Furthermore, a number of miner devices 30 used by miners who participate in a mining operation by participating in a blockchain network are connected to the Internet.

A blockchain network x is configured by a number of minor devices 30x (30x-1, 30x-2,...), And a blockchain network y is configured by a number of minor devices 30y (30y-1, 30y-2,...). Have been.
These blockchain networks are P2P (Peer to Peer) networks. The blockchain network x is a network of virtual currency X, and the blockchain network y is a network of virtual currency Y.

  There are many things on the blockchain, including those used for cryptocurrencies. As virtual currencies, besides typical bitcoin, what is called altcoin is known. As typical altcoins, Ethereum and Monacoin (registered trademark) are known.

On the Internet, there are a blockchain network for operating and functioning bitcoin, and a blockchain network for operating and functioning various altcoins.
Many minor devices 30 are connected to each block chain network to perform proof of work (PoW). Some other blockchain networks employ proof of stake (PoS) and proof of consensus (PoC) as consensus algorithms.

  In each case, the blockchain network is a P2P network without centralized servers. In the blockchain, the same transaction information is stored in the storage of each of the minor devices belonging to the blockchain network, the server device, and the storage of the pool server. That's why blockchains are called decentralized ledgers.

FIG. 1B is a diagram illustrating a block chain of a device belonging to a block chain network.
The outline of the block chain will be described with reference to FIG.
The block chain is established by connecting sequentially generated transaction information and the like in block units.

That is, in the blockchain technology, data whose contents are to be guaranteed, such as transaction records and contracts, are handled in units of blocks. A block chain is obtained by connecting blocks in a predetermined manner and storing them. A hash function is used to generate the block chain, and the hash function is a function for obtaining a fixed-length hash value for arbitrary-length arbitrary data.
Hash functions have the characteristic of being one-way, and it is easy to obtain a hash value from arbitrary data.On the contrary, it is said that it is practically impossible to restore the original data from the hash value. You.

  When connecting a new block to the block chain, the minor device applies a hash function to the hash value of the immediately preceding block, data of the current block, and original data using an arbitrary Nonce. . Then, the minor device searches for a Nonce value such that the upper several bits of the hash value of the original data become 0. The data of the current block is data called a Merkle route that combines transaction data of a new block to be connected. Nonce is, for example, a 32-bit fixed-length value. For example, SHA-256 that calculates a 256-bit hash value using arbitrary data is used as the hash function. When SHA-256 is applied, the probability that the upper 10 bits of the hash value become 0 is 1/1024.

Since it is difficult to restore the original data from the hash value, the miner device applies a hash function to the original data while changing the value of Nonce, and the determined number of 0s is arranged in the upper few bits of the hash value. Search for Nonce. The minor device that has found the correct Nonce sends the correct Nonce to the blockchain network. Then, the block is connected to the block chain by another minor device included in the block chain network approving that the received Nonce is correct.
The consensus algorithm for approving the above blocks is called proof of work.
By performing the approval work by the proof of work, each block of the block chain includes, as shown in FIG. 1B, the data of the block, the hash value of the immediately preceding block, and the searched Nonce value. Including.

In such a block chain, since each block has the hash value of the immediately preceding block, it is possible to confirm the validity of all blocks by sequentially tracing from the leading (oldest) block. I can do it.
If an attempt is made to alter a block in the middle, it is necessary to recalculate the Nonce of all blocks after that block. However, since the above round robin has to be performed for all blocks, the calculation is impossible.
With these features, the reliability of the blockchain is ensured.

In the field of virtual currency using a blockchain, “to remit virtual currency to a user” is a convenient expression.
In Bitcoin, virtual currency remittance is the process of unlocking unused transaction output, including the amount of Bitcoin, that is locked to the user's address and locking it to the address of the remittee user. . In Bitcoin, unused transaction output is also called UTXO (Unsent Transaction Output). In the following description, transaction output is also simply referred to as output.
A UTXO is an output that is not connected to another transaction in a transaction, and includes a ScriptPubKey describing the address of the owner. The owner's address is the owner's public key or public key hash. In the following description, it is assumed that the owner address is a public key hash.

That is, in remittance of the virtual currency, the UTXO locked by the ScriptPubKey including the owner's public key hash (address) is unlocked by an electronic signature generated using the owner's private key. Then, the unlocked UTXO is connected to a transaction newly created by the owner. In the transfer of the virtual currency, the UTXO of the newly created transaction is locked by the ScriptPubKey including the public key hash of the next owner.
The owner sends the newly created transaction to the blockchain network. Then, the minor device approves the transaction, and the block including the newly created transaction is incorporated in the blockchain, whereby the remittance of the virtual currency (transfer of ownership of UTXO) is completed.

Therefore, in remittance of virtual currency, no value information is exchanged between the user terminal devices as data. Therefore, information indicating the balance of the virtual currency is not stored in the terminal device.
The wallet software installed in the terminal device presents the user with the virtual currency balance possessed by the user by searching the blockchain network for the UTXO linked to the user address.

FIG. 2 is a diagram illustrating an outline of the license management system according to the present embodiment.
The processing will be outlined according to the steps (1) to (7) in the figure.
(1) The provider terminal device 20 provides the application to the user terminal device 10 by any means. This application is distributed as an encrypted application. The user terminal device 10 can be executed by decrypting the encrypted application on condition that the existence of a valid license for the user is confirmed.

(2) The user terminal device 10 requests the provider terminal device 20 to grant a license to use the encrypted application. In this grant request, the user's virtual currency wallet address is transmitted.
The user who uses the application can be specified by the wallet address of the virtual currency.
The application license is granted so that a user having a specific wallet address can use the application.

Preferably, the terminal unique information of the user terminal device 10 is transmitted to the provider terminal device 20 together with the user's wallet address. Depending on the terminal unique information, the user terminal device 10 can be uniquely specified. The terminal unique information is, for example, hardware unique information such as a CPUID and a DISKID. The CPUID is identification information uniquely given to the CPU at the time of manufacture. DISKID is identification information uniquely given to a hard disk at the time of manufacture.
When the terminal-specific information is transmitted, the license is provided so that the user having the specific wallet address can execute the application only on the specific user terminal device.
It is possible to prevent a user having a license from simultaneously starting an application on a plurality of terminal devices and from reusing a license among a plurality of users.

(3) The provider terminal device 20 that has received the license grant request from the user terminal device creates the wallet address and terminal unique information of the user included in the grant request and each application included in the provider terminal device 20. A license token as the license information is created based on the obtained Ethereum wallet address (public key).
With the wallet address of each application, the target application can be specified at the time of license grant and authentication.

In the present embodiment, the wallet address of the virtual currency is preferably a wallet address of Ethereum.
In the present embodiment, license information of an application (information indicating whether a specific user has a license of an application) is recorded on a block chain. Then, when the application is executed on the user terminal device 10, the license authentication is performed based on the license information recorded on the block chain.
This mechanism can be basically realized by using other block chains (virtual currencies), for example, bit coins and mona coins. However, Ethereum has a smart contract mechanism that other blockchain systems do not have.
The smart contract is realized by distributed processing performed by a virtual machine (EVM: Ethereum Virtual Machine) executed in each node configuring the blockchain network.
Smart contracts can automate various contracts and sales on the blockchain.

In the case of the present embodiment, in the smart contract, registration (deployment) of license information in the token format described later in the blockchain and license authentication using the license information are automatically performed by processing completed on the blockchain network. It can be carried out.
The license information is stored not in a specific server but in a memory area of a blockchain, and authentication using the license information is also performed by distributed processing by each node, not the specific server.
That is, by using Ethereum sometimes instead of another blockchain system, it is not necessary to separately prepare a server device that performs license authentication using license information recorded on the blockchain.
In the present embodiment, description will be made on the assumption that an Ethereum is used as a block chain system used to grant a license of an application to a user and register license information related to the grant.
(4) The provider terminal device 20 deploys the created license token to the smart contract. As a result, the fact that the application license has been granted to the user is registered in the blockchain, and the license grant is completed.

(5) When the encryption application is activated, the user terminal device 10 executes the decryption code embedded in the encryption application.
The decryption code makes an inquiry to a smart contract executed on the blockchain network for license authentication as a decryption condition.
This inquiry is a search for the blockchain using the user's Ethereum wallet address and the Ethereum wallet address for each application included in the encryption application as queries.
Depending on the Ethereum wallet address for each application, the application to be licensed can be specified.

(6) As a response to the query, the smart contract returns the presence or absence of a license or terminal-specific information to the user terminal device 10.
As described in (2) to (4) above, the license token generated based on the user's Ethereum wallet address, terminal-specific information, and the Ethereum wallet address for each application is recorded on the blockchain. .
In response to the inquiry, the smart contract specifies the license token from the token list by the wallet address included in the query.
Then, the smart contract returns the terminal unique information included in the specified license token to the user terminal device 10. Alternatively, it returns the normal license presence / absence to the user terminal device 10 simply based on the presence / absence of the license token.
(7) The decryption code executed in the user terminal device 10 is provided on condition that the terminal unique information returned from the block chain (smart contract) matches the actual terminal unique information of the user terminal device 10. Decrypts the encrypted application and executes the application.

This embodiment will be described in more detail. The user activates the downloaded encrypted application on his / her user terminal device 10.
If there is no Ethereum wallet in the user terminal device 10, the user terminal device 10 automatically creates an Ethereum wallet.
In the present embodiment, since license authentication is performed using the user's Ethereum wallet address, it is a major premise that an Ethereum wallet has been created. Therefore, when the Ethereum wallet does not exist, the license of the encryption application is not granted.
The user terminal device 10 provides the provider terminal device 20 with the Ethereum wallet address and the terminal unique information of the user terminal device 10 as a license grant request. Such information can be transmitted using e-mail or other communication means.

The provider terminal device 20 grants a license to the Ethereum wallet address and the terminal unique information received from the user terminal device 10.
Granting a license is, specifically, calling the API of the smart contract and adding a token to the received Ethereum wallet address.
Since the token includes the terminal-specific information of the user terminal device 10, node lock can be performed. That is, the node lock permits execution of the encryption application only in a specific terminal device specified by the terminal unique information. When it is desired to restrict simultaneous activation of an application on a plurality of terminal devices, it is preferable to include terminal-specific information in the token. However, terminal-specific information is not necessarily required for granting a license.
The user terminal device 10 may transmit only the Ethereum wallet address to the provider terminal device 20 as a license grant request.
In this case, the terminal information is not included in the license information (token), and the node lock cannot be performed. However, there is no restriction on the hardware that can execute the application, so that the license transfer described later becomes easier. .

上記のコードにおいては、ＰＣ（利用者端末装置１０）の端末固有情報と、アプリケーションごとのイーサリアムウォレットアドレスと、購入者（利用者）のイーサリアムウォレットアドレスと、をトークンに組み込み、トークンリストにマッピングすることが行われている。
これにより、特定のアプリケーションソフトウェアに関する利用者のライセンスがブロックチェーンネットワークに記録されたことになる。
スマートコントラクトが使用できないブロックチェーンを使用する場合は、ＯＰ＿ＲＥＴＵＲＮにＰＣの固有ノード情報を記載した、提供者の秘密鍵で署名したトランザクションを購入者のアドレスに送信することによって、ブロックチェーンに書き込む。 The application provider describes the token using a language such as Solidity or the like, and creates and publishes a transaction for deploying the token to the blockchain.
The provider terminal device 20 writes a token indicating that the user specified by the wallet address has a license using the smart contract.
The entity of the token is stored in a memory area on the smart contract.
The token is described, for example, as follows.

In the above code, the terminal-specific information of the PC (user terminal device 10), the Ethereum wallet address for each application, and the Ethereum wallet address of the purchaser (user) are incorporated into the token, and are included in the token list. Mapping has been done.
As a result, the user's license for the specific application software is recorded on the blockchain network.
When a block chain that cannot be used by a smart contract is used, a transaction signed with the private key of the provider, in which the unique node information of the PC is written in OP_RETURN, is transmitted to the address of the purchaser, thereby writing the transaction into the block chain.

When the encryption application is activated, if an Ethereum wallet is found in the user terminal device 10, the decryption DLL (decryption code) included in the encryption application determines whether a valid license is granted to the blockchain network. Inquire.
Even if an Ethereum wallet exists, it is a matter of course that an encryption application license is not always given to the address. Thus, the decryption DLL makes an inquiry to the blockchain network as license authentication.
This inquiry is performed by searching the blockchain network using the Ethereum wallet address for each application and the Ethereum wallet address of the user as a query (search key).
The search result is returned, for example, as terminal-specific information corresponding to the query.
The decryption DLL compares the returned terminal-specific information with the actual terminal-specific information, and if they match, determines that the license is correctly granted.
If the terminal-specific information is not transmitted when the license is granted, the inquiry result returned by the smart contract is only the presence or absence of a normal license.
As a result of confirming the existence of the normal license, the decryption DLL decrypts the encrypted application using the common key included in the application and makes it executable.

In the license authentication, it is difficult for the user terminal device 10 to hold the data (full nodes) of all the block chains, even in consideration of the capacity of the recording medium.
Therefore, it is desirable to make an inquiry to a full node running on an arbitrary server.
The user can select the full node to be connected when starting the encryption application.
Further, in order to prevent double use of the license, the full node of the connection destination may be limited when the application is encrypted in the provider terminal device 20. That is, a list of addresses (connection destination URLs) of full nodes that can be used by the application is designated at the time of encryption. That is, a list of connection destination URLs is included in the encryption application.

Once the license token is deployed on the blockchain by the provider terminal device 20, the license of the user is executed as a function of the smart contract without the intervention of the provider terminal device 20 anymore.
Therefore, even if the operation of the provider terminal device 20 ends or stops due to the application provider ending the service or the occurrence of a failure, the user terminal device 10 is recorded on the blockchain. License token is available. Accordingly, the user terminal 10 can execute the license authentication and execute the encryption application even when the operation of the provider terminal device 20 ends or stops.
In the conventional client-server authentication, unless the server device operates, license authentication cannot be performed, and applications and contents cannot be used.
However, the above-mentioned problem can be avoided by managing the information necessary for the license on the blockchain and automatically performing the license authentication on the blockchain.
In addition, since it is not necessary to keep the authentication server device operating at all times, it can be said that the service management side is very advantageous in terms of cost and operation.

Hereinafter, the configuration of the present embodiment for realizing the above processing will be described in detail.
3A and 3B are diagrams illustrating a functional configuration of the user terminal device, where FIG. 3A is a diagram illustrating a functional configuration using hardware, and FIG. 3B is a block diagram illustrating a functional configuration using software.
The user terminal device 10 is, for example, a computer device shown in FIG.
The user terminal device 10 includes a CPU (Central Processing Unit) 41 and a RAM (Random Access Memory) 42. Furthermore, the user terminal device 10 includes a drive device 43, a recording medium 44, a ROM (Read Only Memory) not shown, and a network I / F 45.
The CPU 41 executes a general-purpose operating system that controls the entire apparatus, and executes a program that implements the functions of the user terminal device 10. Various programs, temporary data, and variables are developed in the RAM 42 for processing by the CPU 41.

The drive device 43 is a device that performs at least one of reading and writing of information stored in the recording medium 44. The recording medium 44 stores information written by the drive device 43. The recording medium 44 is, for example, at least one of a storage medium of a type such as a hard disk, an SSD (Solid State Drive), a CD (Compact Disc), a DVD (Digital Versatile Disc), and a Blu-ray disc. Further, for example, the user terminal device 10 includes a drive device 43 corresponding to the type of the recording medium 44 in the user terminal device 10.
At least one of the recording medium 44 and the ROM stores programs and data. The network I / F 45 connects the user terminal device 10 to a network.
Further, the user terminal device 10 includes an input device 46 such as a mouse and a keyboard, and a display device 47 such as a liquid crystal display.

Further, as shown in FIG. 3B, the CPU 41 executes a license request processing unit 50, a license authentication processing unit 51, a decryption processing unit 52, and a license transfer processing unit 53 as processing units.
The license request processing unit 50 is a processing unit that performs a process of requesting the provider terminal device 20 to give an initial license to an application provided by the provider terminal device 20.
The license authentication processing unit 51 and the decryption processing unit 52 are a part of the encryption application provided from the provider terminal device 20, and are executed by activating the encryption application downloaded to the recording medium 44.
The license authentication processing unit 51 is a processing unit that makes an inquiry to a blockchain network at the time of activation of an encryption application, and performs license authentication for checking whether a valid license exists. It can be said that the inquiry to the blockchain network is a request for license authentication to the blockchain network.
The decryption processing unit 52 is a processing unit that decrypts and executes the encrypted application on condition that a valid license is confirmed by the processing by the license authentication processing unit 51.
The license transfer processing unit 53 is a processing unit that performs processing related to the smart contract, and performs processing for creating and transmitting a transaction for transferring the license token to another user.

4A and 4B are diagrams illustrating a functional configuration of the provider terminal device, where FIG. 4A is a diagram illustrating a functional configuration by hardware, and FIG. 4B is a block diagram illustrating a functional configuration by software.
The provider terminal device 20 is, for example, a computer device illustrated in FIG.
The provider terminal device 20 includes a CPU 61 and a RAM 62. Further, the provider terminal device 20 includes a drive device 63, a recording medium 64, a ROM (not shown), and a network I / F 65.
The CPU 61 executes a general-purpose operating system that controls the entire apparatus and executes a program that implements the functions of the provider terminal device 20. The RAM 62 stores various programs, temporary data, and variables for processing by the CPU 61.

The drive device 63 is a device that performs at least one of reading and writing of information stored in the recording medium 64. The recording medium 64 stores information written by the drive device 63. The recording medium 64 is, for example, at least one of storage media of a type such as a hard disk, an SSD, a CD, a DVD, and a Blu-ray disc. Further, for example, the provider terminal device 20 includes a drive device 63 corresponding to the type of the recording medium 64 in the provider terminal device 20.
At least one of the recording medium 64 and the ROM stores programs and data. The network I / F 65 connects the provider terminal device 20 to a network.
Further, the provider terminal device 20 includes an input device 66 such as a mouse and a keyboard, and a display device 67 such as a liquid crystal display.

Further, as shown in FIG. 4B, the CPU 61 executes an encryption processing unit (encryption tool) 71 and a license grant processing unit 72 as processing units.
The encryption processing unit 71 is an encryption tool that receives an input of binary data of an application from an application provider, performs an encryption process, and outputs an encrypted application.
The provider creates one Ethereum wallet for one application, and the encrypted application includes an Ethereum wallet address for each application.
The target application is specified at the time of license grant or authentication by the Ethereum wallet address created for each application.
When a blockchain system other than Ethereum is used, it is possible to specify a blockchain to be inquired for authentication by a wallet address.

The license grant processing unit 72 calls a smart contract API in response to a license grant request from the user terminal device 10, generates a license token, and registers (deploys) it in a blockchain (smart contract). It is. The license token is license information for performing license authentication by a smart contract.
In the system according to the present embodiment, the provider terminal device 20 holds a license token of an application on a blockchain.

FIG. 5 is a diagram illustrating an encryption application generated by the encryption tool of the provider terminal device.
As described above, the encryption tool is installed in the provider terminal device 20.
The encryption tool has an encryption code for encrypting application data before encryption.

In this embodiment, since the application is distributed after being encrypted, it is possible to prevent cracking due to rewriting or analysis performed on the binary data.
In addition, AES (Advanced Encryption Standard) is typically used as a common key encryption method, but other common key encryption methods may be used.
The encryption application can be suitably downloaded from any website or store application.

As shown in FIG. 5A, the provider terminal device 20 uses an encryption tool to encrypt data of the pre-encryption application using a predetermined common key, and outputs the data of the encrypted application.
The encryption tool is provided with a decryption dynamic link library (DLL) including a program for querying the blockchain, a wallet address of the application, and a common key for decryption. The decryption DLL has, as its body, a decryption code for decrypting the encrypted data.
The encrypted application after encryption is output together with the decryption DLL.
The common key used for encrypting the application may be input from outside the encryption tool, or may be a key included in the decryption DLL.

  As shown in FIG. 5B, the pre-encryption application stored in the recording medium 64 of the provider terminal device 20 includes a pre-encryption program, resources, and entry points. The entry point points to the beginning of the program.

FIG. 5C shows a data configuration of the encryption application. The encryption application has a configuration in which a stub program is added to the configuration of the pre-encryption application in FIG.
Unlike before encryption, the entry point points to the start of the stub program, and the stub program points to the start of the program after encryption.

When the encryption application downloaded to the user terminal device 10 is executed, a stub program is first executed. The stub program calls the DLL for decryption and causes a process for decrypting the encrypted program to be performed. This process includes a process of inquiring the blockchain about the presence or absence of a license.
That is, the decryption DLL includes a program corresponding to the functions of the license authentication processing unit 51 and the decryption processing unit 52 described above.
The main body of the recovery DLL functions as the decryption processing unit 52 when executed by the user terminal device 10. Further, the program that queries the block chain included in the decryption DLL functions as a part of the license authentication processing unit 51 when executed by the user terminal device 10.
The encryption tool automatically inserts (adds) a program for inquiring the blockchain into the encryption application by hooking an arbitrary application and injecting the decryption DLL when the encryption application is executed. The program that inquires the block chain is a program that causes the CPU 41 to function as the license authentication processing unit 51.
Only the program body in FIG. 5B is encrypted in the encryption application. The encrypted program body is a program after encryption in the encryption application in FIG.
The decryption DLL is inserted into the post-encryption application as a code separate from the post-encryption program, like the entry point, the resource, and the stub program.
The decryption DLL may be added as a file separate from the executable binary of the encryption application, or may be included in the executable binary.

FIG. 6 is a flowchart illustrating an application encryption process performed by the provider terminal device.
In step S51, the CPU 61 (the encryption processing unit 71) receives an input of binary data of an application to be encrypted.
As described above, the execution file of the application includes the entry point, the program body, and the resources.
In step S52, the CPU 61 (the encryption processing unit 71) encrypts the program body of the input application data using a predetermined common key, and generates an encryption program.

In step S53, the CPU 61 (the encryption processing unit 71) inserts a decryption DLL and a stub program into an encryption application including an entry point, an encryption program, and resources.
As described above, the DLL for decryption includes an inquiry program to the blockchain for license authentication, an Ethereum wallet address for each application, and a common key for decryption.
In step S54, the CPU 61 (the encryption processing unit 71) outputs data of an “encryption application” including an entry point, an encryption program, a resource, and a DLL for decryption.

FIG. 7 is a flowchart illustrating an application startup process executed by the user terminal device.
In step S101, the CPU 41 determines whether or not an application startup operation by a mouse double-click operation or the like has been performed.
If it is determined that the application has not been started (No in step 101), the CPU 41 ends the process.
If it is determined that the operation for starting the application has been performed (Yes in step S101), the CPU 41 starts the processing for starting the encrypted application in step S102.

In step S103, the CPU 41 (license request processing unit 50) determines whether or not the user terminal device 10 has a user's Ethereum wallet.
If it is determined that the Ethereum wallet does not exist in the user terminal device 10 (No in step S103), the CPU 41 (license request processing unit 50) newly creates an Ethereum wallet in step S107. Then, in step S108, the CPU 41 (license request processing unit 50) transmits the Ethereum wallet address and the terminal unique information of the user terminal device 10 to the provider terminal device 20 to issue a license grant request. Do.

If it is determined that a wallet is present (Yes in step S103), the CPU 41 (license authentication processing unit 51) performs the license authentication processing described in FIG. 8 in step S104.
In step S105, the CPU 41 determines whether or not the license authentication in step S104 has been successful, that is, whether or not the encryption program has been decrypted and whether or not the encryption has been released.
If it is determined that the encryption has been released (Yes in step S105), the CPU 41 starts the application in step S106 and ends the processing.
If it is determined that the encryption has not been decrypted (No in step S105), the CPU 41 cannot start the application and ends the processing as it is.

FIG. 8 is a flowchart illustrating the license authentication process of FIG.
In step S111, the license authentication processing unit 51 inquires of the blockchain network whether there is a valid license. At this time, the license authentication processing unit 51 transmits the wallet address of each application and the wallet address of the user to the blockchain network.
In step S112, the license authentication processing unit 51 determines whether or not an inquiry result (terminal specific information, presence or absence of a normal license) has been received from the blockchain network.
When it is determined that the inquiry result has not been received (No in step S112), the license authentication processing unit 51 repeats the process of step 112 and waits for reception of the inquiry result.

If it is determined that the inquiry result has been received (Yes in step S112), the license authentication processing unit 51 determines in step S113 whether the terminal unique information of the inquiry result matches the actual terminal unique information, and determines whether the inquiry result is normal. It is determined whether or not it indicates the presence of a license.
If it is determined that the terminal unique information of the inquiry result matches the actual terminal unique information or that the inquiry result indicates that a normal license exists (Yes in step S113), the license authentication processing unit 51 determines in step S114 The application is decrypted using the key, and the process ends.
If it is determined that the terminal unique information of the inquiry result does not match the actual terminal unique information or that the inquiry result does not indicate the presence of a normal license (No in step S113), the license authentication processing unit 51 ends the processing as it is. And does not decrypt the application.

FIG. 9 is a flowchart illustrating a license granting process executed by the terminal device of the application provider (developer).
In step S201, the CPU 61 (license grant processing unit 72) determines whether or not the user has received the Ethereum wallet address of the user and the terminal unique information of the user terminal device 10 as the license grant request. As described above, the terminal unique information of the user terminal device 10 is not essential for the license grant request.
If it is determined that the license grant request has been received (Yes in step S201), the CPU 61 (license grant processing unit 72) calls the smart contract API (smart contract processing unit) in step S202, and in step S203, the user The license token is assigned to the wallet address, and the license assignment process ends.

A license transfer procedure in the system according to the present embodiment will be described.
A user having a license can transfer a license token to another user by performing authentication using the private key of his or her own wallet.
That is, the user can execute a smart contract for transferring a license to an arbitrary wallet.
The execution of a smart contract in Ethereum requires a fee called gas, but it is also possible to automatically grant Ethereum to the user's wallet so that the user does not need to purchase Ethereum. It is possible.
For example, prior to the license transfer, one user transmits a transfer notification indicating that the license is transferred to another user to the provider terminal device 20.
This transfer notification includes at least the wallet address of the transfer source user and the wallet address of the transfer destination user.
In this case, the user terminal device 10 includes a transfer notification transmitting unit that transmits a transfer notification, in addition to the processing unit in FIG. The transfer notification transmitting unit is, for example, e-mail client software capable of transmitting an e-mail. Then, the transfer notification is transmitted to the provider terminal device 20 by the transfer notification transmitting unit.
The provider terminal device 20 that has received the transfer notification performs the remittance of Ethereum to the transfer source wallet address described in the transfer notification.
In this case, the provider terminal device 20 creates a transfer notification receiving unit for receiving a transfer notification and a transaction for adding virtual currency (Ethereum) to the user's wallet, in addition to the processing unit of FIG. , And a remittance unit that performs a process of making the information public.
When the transfer notification is sent by e-mail, the transfer notification receiving unit is also e-mail client software capable of receiving the e-mail.
The license transfer processing unit 53 shown in FIG. 3B checks the wallet of the transfer source user, and checks whether or not the Ethereum from the provider terminal device 20 has been received.
Upon confirming the payment, the license transfer processing unit 53 executes a license transfer process described below.
The transmission of the transfer notification from the provider terminal device 20 may be performed after executing the smart contract for transferring the license.

FIG. 10 is a flowchart illustrating a license transfer process executed by the user terminal device of the application.
In step S301, the CPU 41 (license transfer processing unit 53) creates a transfer transaction for transferring the license token to the transfer destination user's wallet.
The transfer transaction includes at least an electronic signature based on the secret key of the wallet of the transfer source user who uses the user terminal device, and a wallet address of the transfer destination user.
In step S302, the CPU 41 (license transfer processing unit 53) discloses the transfer transaction created in step S301 to the blockchain network.
Thereby, the smart contract for transferring the token is executed on the blockchain, and the transfer of the license is realized.
Note that the remittance of Ethereum for the fee associated with the license transfer is not performed based on the transfer notification transmitted by the user terminal device 10, but the provider terminal device 20 monitors the blockchain and the license transfer is performed. It may be performed in response to the fact that the provider terminal device 20 discovers the fact.
In this case, the provider terminal device 20 includes, in addition to the processing unit of FIG. 4B, a blockchain monitoring unit that constantly monitors the blockchain, and a process of creating and publishing a transaction for providing a user with virtual currency (Ethereum). A remittance unit that performs
When the blockchain monitoring unit monitoring the blockchain finds a transfer transaction for license transfer, the remittance unit performs a process of remitting Ethereum to the wallet of the user who published the transfer transaction.

Note that, in the system 1 of the present embodiment, such a process of monitoring the blockchain and automatically assigning the Ethereum is not performed by the provider terminal device 20 but by a server device provided separately from these terminal devices. May go.
The server device includes at least a CPU and a RAM as a control unit, and is connected to the Internet via a network I / F.
The CPU of the server device executes a blockchain monitoring unit that constantly monitors the blockchain, and a remittance unit that performs a process of creating and publishing a transaction for granting a virtual currency (Ethereum) to a user.
When the blockchain monitoring unit monitoring the blockchain finds a transfer transaction for license transfer, the remittance unit performs a process of remitting Ethereum to the wallet of the user who published the transfer transaction.

With the configuration described above, according to the system of the present embodiment, the provider of the application terminates or stops the operation of the provider terminal device 20 due to termination of the service or occurrence of a failure. Even in this case, the user terminal device 10 can always execute the license authentication using the license token recorded on the blockchain and execute the encryption application.
The service provider also does not need to operate the authentication server (license server) at all times, so that a system that is advantageous in terms of cost and operation can be provided.

In the above description, information on licenses is recorded on the blockchain using the smart contract mechanism of Ethereum, and the license authentication function in the application is completed on the blockchain (completely serverless). At).
On the other hand, the license information is recorded on the blockchain, but a search server for searching the blockchain and inquiring about the presence or absence of the license may be separately provided.
A similar mechanism can also be realized by using a blockchain as a storage for storing license information and performing license authentication by a separately provided server device by using a blockchain protocol other than Ethereum described above.
In this case, the license authentication processing unit 51 included in the decryption DLL makes an inquiry to the search server when executing the encryption application. That is, the application transmits the wallet address of the application and the wallet address of the user to the search server.
The search server performs a process of searching the memory area of the block chain based on these pieces of information and returning the presence or absence of the license to the license authentication processing unit 51.

In the above description, the license grant and authentication are limited to application software, but the present invention is not limited to this.
The same can be applied to contents such as electronic books, moving images, and music.
For example, the provider encrypts and distributes the content data. The browsing software executed on the terminal device used by the user who has obtained the encrypted content data performs authentication by querying the blockchain network each time the content is displayed.
If the authentication is successful, the viewing software decrypts the encrypted content data and displays it. With this configuration, even if the provider of the digital content terminates the service or the operation of the provider terminal device 20 is terminated or stopped due to a failure, the user terminal device 10 can display the digital content by performing license authentication using the license token recorded on the block chain.

1 system, 10 user terminal device, 20 provider terminal device, 30 minor device, 41 CPU, 42 RAM, 43 drive device, 44 recording medium, 45 network I / F, 46 input device, 47 display device, 51 license authentication Processing unit, 52 decryption processing unit, 53 license transfer processing unit, 61 CPU, 62 RAM, 63 drive device, 64 recording medium, 65 network I / F, 66 input device, 67 display device, 71 encryption processing unit (encryption Tools), 72 License grant processing unit, 73 Smart contract processing unit

Claims (12)

Comprising a first device and a second device,
The first device comprises:
An encryption processing unit that performs encryption processing of input data and outputs encrypted data;
A license grant processing unit that grants a license related to the data to a user of the second device, and sends license information related to the grant of the license to a blockchain network.
The second device comprises:
When using the encrypted data, a license authentication processing unit that performs authentication based on the license information recorded on the blockchain,
A decryption processing unit that performs decryption processing on the encrypted data when the authentication is successful,
An information processing system comprising: The information processing system according to claim 1,
The information processing system according to claim 1, wherein the encrypted data includes a first virtual currency wallet address created for identifying the encrypted data. The information processing system according to claim 1 or 2,
The information processing apparatus according to claim 1, wherein the license granting unit sends license information based on a second virtual currency wallet address of the user and the first virtual currency wallet address to the blockchain network. system. The information processing system according to claim 1 or 2,
The license grant processing unit is configured to convert license information based on a second virtual currency wallet address of the user, the first virtual currency wallet address, and unique information of the second device into the block chain. An information processing system for transmitting to a network. The information processing system according to any one of claims 1 to 4,
The license authentication processing unit makes an inquiry to an external device that stores a block chain at the time of the authentication,
The information processing system according to claim 1, wherein the encryption processing unit includes a connection destination list of an external device that can be used by the license authentication processing unit in the encrypted data when encrypting the data. The information processing system according to any one of claims 1 to 5,
The second device includes a license transfer processing unit that transfers the license by exposing transfer information for transferring the license from the user to another user on the blockchain network. Information processing system. The information processing system according to claim 6,
The second device further includes a transfer notification transmission processing unit that transmits a transfer notification notifying that the license transfer is performed to the first device,
The information processing system according to claim 1, wherein the first device further includes a remittance unit that performs a process of remitting virtual currency to the user based on the transfer notification. An encryption processing unit that performs encryption processing of input data and outputs encrypted data;
A license grant processing unit for granting a license related to the data to a user of another device, and sending out license information related to the grant of the license to a blockchain network. apparatus. A license authentication processing unit that performs authentication based on license information stored on the blockchain when using the encrypted data;
A decryption processing unit that performs decryption processing on the encrypted data when the authentication is successful,
An information processing apparatus comprising: An encryption processing unit that performs encryption processing on data and generates encrypted data;
An adding unit that adds a code for inquiring the blockchain network of the license information of the encrypted data when using the encrypted data to the encrypted data at the time of the encryption processing;
An information processing apparatus comprising: An information processing method executed by a computer, comprising:
Performs encryption processing on the data, generates encrypted data,
An information processing method, wherein a code for inquiring a blockchain network about license information of the encrypted data when using the encrypted data is added to the encrypted data at the time of the encryption processing. Performs encryption processing on the data, generates encrypted data,
An information processing program for causing a computer to execute a process of adding a code for inquiring a blockchain network about license information of the encrypted data to the encrypted data at the time of using the encrypted data at the time of the encryption process.

Images