Non-transitory computer-readable storage medium, information processing apparatus, and

Abstract

To provide a computer program, an information processing device, and a control method thereof for suitably paying a fee when using a service in a blockchain network.SOLUTION: The computer program causes a computer to receive, in a blockchain network, a transaction related to a token including use information of a service and execute processing requested by the received transaction. The computer program also causes the computer to determine whether to add a block to the blockchain in response to the performed operation. The computer program further causes the computer to set, when a block is added, a first wallet owned by the information processing apparatus or a second wallet owned by an issuer of the transaction as a payer of a fee for adding the block.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a computer program, an information processing device, and a control method thereof. [Background technology]

[0002] Patent Document 1 proposes an NFT management system that issues non-fungible tokens (NFTs) containing service usage information and grants them to service users for services provided to information processing devices owned by users. In this system, service usage information is rewritten by the service users. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2024-12690 Summary of the Invention [Problem to be solved by the invention]

[0004] The above-mentioned conventional technology has the following problems. When rewriting service usage information of a block on a blockchain using an NFT, the service user must pay a fee to generate the block using their wallet. In other words, the service user must pay a fee for adding a block every time they rewrite the service usage information. This means that service users have to pay a fee every time they use the service, which can lead to a problem where they refrain from using the service.

[0005] The present invention has been made in consideration of at least one of the above-mentioned problems, and provides a mechanism for suitably paying fees when using services in a blockchain network. [Means for solving the problem]

[0006] The present invention is characterized in that, for example, a computer of an information processing device that executes a smart contract functions as a receiving means for receiving transactions related to tokens including service usage information in a blockchain network, an execution means for executing processing requested by the received transaction, a determination means for determining whether to add a block to the blockchain based on the executed processing, and a setting means for setting a first wallet owned by the information processing device or a second wallet owned by the issuer of the transaction as the source of payment for the fee for adding the block when the block is to be added. [Effects of the Invention]

[0007] According to the present invention, fees for using services on a blockchain network can be paid in an appropriate manner. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating a system configuration according to an embodiment. [Figure 2] 1 is a flowchart illustrating the processing of a smart contract according to an embodiment. [Figure 3] Flowchart of NFT issuance process of smart contract according to one embodiment [Figure 4] 1 is a flowchart illustrating an NFT purchase process of a smart contract according to an embodiment. [Figure 5] 1 is a flowchart illustrating a service information notification process of a smart contract according to an embodiment. [Figure 6] Flowchart for service termination notification processing of a smart contract according to an embodiment [Figure 7] 1 is a block diagram illustrating an image forming apparatus according to an embodiment. [Figure 8] A sequence diagram from NFT issuance to NFT service termination notification according to one embodiment. [Figure 9]Flowchart for NFT service information processing of an image forming apparatus according to an embodiment [Figure 10] Block diagram of a node (information processing device) according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention claimed. Although multiple features are described in the embodiments, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0010] <System configuration> An embodiment of the present invention will be described below. An example of the configuration of a service providing system according to this embodiment will be described with reference to FIG. 1. This system includes a blockchain 100, an NFT development server 101, an information processing device (MFP 104), a service providing server 102 that provides services to the MFP 104, and a marketplace server 103 that sells NFTs. Solid lines with arrows in FIG. 1 indicate transactions. Dotted lines indicate references, instructions, notifications, etc., via HTTP.

[0011] Blockchain 100 is a system consisting of an unspecified number of information processing devices arranged as nodes, and is also called a distributed management ledger. Each node shares historical information on transaction data in blocks. Transaction data is stored in a data structure on the chain, inheriting the contents of the previous transaction data as a hash. Transaction data (transactions) recorded on blockchain 100 have the following characteristics: they cannot be tampered with, there is no loss, and the owner can be identified.

[0012] The NFT development server 101 is a server of a company that develops contract blocks (smart contracts 105) for non-fungible tokens (NFTs). NFTs are digital data containing owner information, and are associated with smart contracts and stored on the blockchain as blocks on the blockchain (NFT blocks). NFTs have features such as anti-counterfeiting and proof of ownership. In this embodiment, NFTs are linked to the number of printable sheets on a printing device such as the MFP 104. Note that this embodiment will be described using non-fungible tokens (NFTs) as an example of transactions related to tokens containing service usage information on a blockchain network. However, this is not intended to limit the scope of the present invention, and other tokens different from NFTs may also be used.

[0013] The smart contract 105 is a program that is automatically executed when triggered by a transaction received from the blockchain or outside the blockchain. The smart contract 105 is executed by any node (information processing device) that makes up the blockchain 100, and the execution results are shared among all nodes. The smart contract 105 of the present invention executes processes such as issuing NFTs, rewriting (purchasing) NFT owner information, notifying NFT service information, and notifying the termination of NFT services.

[0014] The service providing server 102 is a server of a company that sells NFTs that provide services. The services provided use an image forming device (MFP 104) and correspond to various service formats using the MFP, such as printing services, rental services, and maintenance services. Furthermore, the present invention is applicable to any service (email, web, content provision, games, etc.) provided via a network using the MFP as an information processing device. The service providing server 102 issues NFTs according to the type of service using the MFP and sends an NFT sales instruction 130 to the marketplace server 103 to sell the issued NFTs.

[0015] The marketplace server 103 is a web server that displays, in a web browser, a purchase page for the NFTs 151 and 152 sold on the marketplace. When the purchase process for the NFTs 151 and 152 is executed in the information processing device or MFP 104, an NFT purchase notification 131 is sent to the service providing server 102.

[0016] (Deploying NFTs) Next, we will explain how to deploy NFTs. The NFT development server 101 is a server of a company that develops smart contracts that can issue and sell NFTs to provide NFT services. The NFT development server 101 deploys (places) the smart contract 105 on the blockchain 100 by sending a deployment 110 transaction to the blockchain 100. A contract address 164 is assigned to the smart contract 105 when it is deployed, and transactions are sent to the smart contract 105 by specifying the contract address 164.

[0017] The NFT development server 101 provides the service provider server 102 with the authority to issue NFTs using the smart contract 105, rewrite (purchase) the owner, and update NFT information, thereby enabling the provision of services using NFTs. In the present invention, the smart contract 105 operates to accept transaction processing from the address (public key) of the wallet 162 owned by the service provider server 102. The smart contract 105 also generates a wallet 161 and sets the wallet address of the wallet 161 in the smart contract 105 to generate transactions to the smart contract 105 and to pay the fees required for adding NFT blocks. The wallet 161 manages the payment of fees when adding transactions related to issued NFTs to the blockchain 100. The fees described here are paid to the node that performed the calculation as compensation for the computational work expended in verifying blocks when adding them to the blockchain 100 and adding the verified blocks to the end of the blocks.

[0018] The smart contract 105 stores wallet address information in association with the NFT as an internal variable, and sends it in a response when the NFT is issued so that the wallet 161 can be managed by the service provider server 102. A wallet is a program that holds a pair of public and private keys required for signing when adding a block to the blockchain 100, and manages tokens (virtual currency, NFT) used in the blockchain 100. It also holds account information for accessing the blockchain 100, and also performs approval processes for processing on the blockchain 100 through the wallet. The fee required to add a block to the blockchain 100 is the verification of the added block, which is performed by each node that makes up the blockchain 100, and virtual currency (tokens) paid to the node that added the block as a reward for adding the block.

[0019] (Issuance of NFTs) Next, we will explain how to issue NFTs. The service providing server 102 issues NFTs and allows the marketplace server 103 to sell the issued NFTs. The service providing server 102 also monitors the service information of the NFT services owned by users and carries out procedures for terminating the services.

[0020] More specifically, the service providing server 102 first sends an issue 111 transaction to issue NFT151 and NFT152 to the smart contract 105. The issue 111 includes the service name (NFT151, NFT152), service information 170, metadata, etc. Upon receiving the issue 111, the smart contract 105 generates an NFT block 141 for NFT151 and an NFT block 140 for NFT152 in the blockchain 100 through the issues 112 and 113 transactions. The address of the wallet 162 of the service providing server 102 is set for the owner of NFT151 and NFT152.

[0021] The issued NFTs 151, 152 are each assigned a unique ID (token ID), and the NFTs can be referenced and processed by sending a transaction to the URI indicated by the contract address and token ID of the smart contract 105. The service providing server 102 also sells the issued NFTs by setting a selling price for the NFTs 151, 152 and sending an NFT selling instruction 130 to the marketplace server 103.

[0022] (Purchase NFTs) Next, we will explain how to purchase an NFT. When purchasing an NFT service, the MFP 104 selects an NFT 151 on the marketplace server 103 and purchases the NFT by sending an NFT purchase instruction 132 to the marketplace server 103, which includes the wallet address of a wallet 163. Upon receiving the NFT purchase instruction 132, the marketplace server 103 sends an NFT purchase notification 131, which includes the wallet address of the wallet 163, to the service providing server 102. After receiving the NFT purchase notification 131, the service providing server 102 sends a purchase 114 transaction to the smart contract 105 to change the owner information of the NFT 151 to the wallet 163 of the MFP 104 that purchased it.

[0023] After receiving the purchase 114, the smart contract 105 makes payment for the NFT purchase with the tokens held in wallet 163, sending a portion of the tokens to wallet 161 as total fee 117 and the remainder to wallet 162. The smart contract 105 also changes the owner of the NFT 151 in the purchase 115 transaction from wallet 162 to the wallet address of wallet 163, and adds the NFT block 142 to the blockchain 100. Thus, according to this embodiment, when the purchase 114 transaction is received by the smart contract 105, a transfer of tokens is performed.

[0024] (NFT service launch) Next, the start of the NFT service will be described. After the MFP 104 purchases the NFT 151, the NFT service using the NFT 151 begins when the block 142 of the NFT 151 is added to the blockchain 100. The service providing server 102 can confirm the service start date based on the NFT block 142 of the NFT 151. After the NFT service begins, the MFP 104 may install apps, data, and the like required for the MFP 104 from the metadata of the NFT 151.

[0025] (Service Information Notification) Next, we will explain the service information notification. When the MFP 104 executes a service provided by the NFT 151, it sends a service information notification 118 to the smart contract 105. For example, if the provided service is a printing service, the MFP 104 executes the printing function and then sends the number of sheets actually printed to the smart contract 105 via the service information notification 118.

[0026] Here, the smart contract 105 sets the wallet 161 as the payer of the fee when the transaction of the service information notification 118 is generated. When the smart contract 105 receives the service information notification 118 from the MFP 104, it rewrites the service information 170 stored in the NFT 151 with the service information notification 119 and adds the NFT block 143 to the blockchain 100. The smart contract 105 also sets the wallet 161 as the payer of the fee when the transaction of the service information notification 119 is generated.

[0027] The token balance of the wallet 161 holds the total fee tokens for the service information notifications 118 and 119 at the time of purchasing an NFT, and the fee for one service information notification can be paid from the wallet 161. Here, due to fluctuations in fees, etc., it is possible that the token balance of the wallet 161 will become zero. In this case, the smart contract 105 may move the tokens from the wallet 162 of the service providing server 102 to the wallet 161, or change the wallet of the payment source to the wallet 162 of the service providing server 102.

[0028] (Service Monitoring) Next, service monitoring will be explained. The service providing server 102 checks changes in the service information 716 of the MFP 104 by sending a monitoring 123 transaction to the smart contract 105. When the smart contract 105 receives the monitoring 123, it acquires the service information 170 of the issued NFT, sets the service information 170 in the response to the monitoring 123, and sends it to the service providing server 102.

[0029] (Service Termination Notice) Next, the service termination notification will be described. When the service of the NFT 151 provided to the MFP 104 is terminated, the MFP 104 sends a service termination notification 121 to the smart contract 105. Upon receiving the service termination notification 121, the smart contract 105 generates an NFT block 144 through a service termination notification 122 transaction and terminates the service. The NFT block 144 indicates that the owner of the NFT 151 has changed to the wallet 162 of the service providing server 102, thereby terminating the service provided by the NFT 151. Upon receiving the response to the service termination notification 121, the MFP 104 stops the service notification function currently operating on the MFP 104. Furthermore, the service providing server 102 monitors the NFT 151 sold via the smart contract 105 and determines the termination of the MFP 104's service from the NFT block 144.

[0030] If there are tokens remaining in the wallet 161 when the service for the NFT 151 ends, the smart contract 105 may be configured to send the remaining tokens to the wallet 163 of the MFP 104. Alternatively, if there are tokens remaining in the wallet 161 when the service end notification is issued, the smart contract 105 may be configured to send the remaining tokens to the wallet 162 of the service providing server 102.

[0031] As described above, an overview of a service information management system using NFTs has been explained using the system configuration diagram in FIG. 1. In this way, the present invention makes it possible to build a system that can provide various services using the MFP 104 by using the NFT 151 and smart contract 105. Furthermore, by using the NFT, the service providing server 102 can manage a series of operations on the blockchain, from installing service information and apps on the MFP 104 to monitoring service information and terminating the service. Furthermore, the present invention can provide a service system that is tamper-proof, has easy history verification (traceability), and guarantees authenticity (identification of the owner), which are characteristics of the blockchain.

[0032] <Node (information processing device) configuration> An example of the hardware configuration of an information processing device 1000, which is an example of a node according to this embodiment, will be described with reference to Fig. 10. The information processing device 1000 includes a CPU 1001, a ROM 1002, a RAM 1003, a communication unit 1004, and an HDD 1005.

[0033] The CPU 1001 performs processing by executing programs such as smart contract 105 stored in the ROM 1002 and HDD 1005. The ROM 1002 stores the programs. The RAM 1003 is used as a temporary storage area such as the main memory and work area of ​​the CPU 1001. In addition to the programs, the HDD 1005 stores various information related to the blockchain, such as NFTs, wallets, contract addresses, and service information.

[0034] Data can be exchanged with other nodes and various devices such as the NFT development server 101, the service provider server 102, the marketplace server 103, and the MFP 104 via the communication unit 1004. The communication unit 1004 may perform wired communication using Ethernet (registered trademark), or may perform wireless communication such as Wi-Fi.

[0035] <Smart Contract 105 Processing Procedure> The processing procedure of the smart contract 105 according to this embodiment will be described with reference to FIGS. 2 to 6. The smart contract 105 has an address on the blockchain 100, and when a transaction is sent to this address, it executes the processing described in the transaction. The smart contract 105 according to this embodiment processes issuance, purchase, service information notification, and service termination notification. The transaction contents also describe the token ID, owner, fee payer, token payer, and token payee. The token ID is an ID assigned to an NFT issued by the smart contract 105. Wallet addresses are described for the owner, fee payer, token payer, and token payee.

[0036] 2 is a flowchart showing the processing procedures for issuing, purchasing, notifying service information, notifying service termination, and monitoring services of NFTs by the smart contract 105 according to this embodiment. The processing described below is realized, for example, by the CPU 1001 of the information processing device 1000 that executes the program of the smart contract 105 reading a program stored in the ROM 1002 or HDD 1005 into the RAM 1003 and executing it. Note that in the following explanation, the number following "S" indicates the step number of the processing in the flowchart or sequence.

[0037] In S201, the smart contract 105 receives a transaction sent to the smart contract 105, for example, from the service provider server 102 or the MFP 104. After receiving the transaction, the smart contract 105 analyzes the content of the processing requested by the transaction and executes each processing according to the analysis results. In S202, the smart contract 105 determines whether the processing requested in the received transaction is an issuance, and if it is an issuance (YES), it transitions to S203, and if it is not an issuance (NO), it transitions to S210.

[0038] In S203, the smart contract 105 executes the NFT issuance process. Here, the smart contract 105 sets the wallet 162 of the service providing server 102 as the payment source for the fee for adding the NFT block and transaction block to the blockchain 100. Next, in S204, the smart contract 105 determines whether or not to add the block to the blockchain 100, and if it is to be added (YES), it transitions to S205, and if it is not to be added (NO), it transitions to S209.

[0039] In S205, the smart contract 105 adds the NFT block and transaction generated in S203, S212, S214, and S216 to the blockchain 100. At this time, the smart contract 105 sets the service company's wallet 162 as the payment source for the fee for adding the NFT block and transaction block to the blockchain 100 if S203 (NFT issuance processing) has been passed. If S212 (NFT purchase processing) has been passed, the smart contract 105 sets the wallet 163 of the service user who purchased the NFT. Here, wallets 162 and 163 correspond to the second wallet owned by the transaction issuer. If S214 (NFT service information notification processing) and S216 (NFT service termination notification processing) have been passed, the smart contract 105 sets the wallet 161 set in the smart contract 105. The wallet 161 corresponds to the first wallet owned by the node (information processing device) executing the smart contract 105. Here, by setting this in the wallet 161 of the smart contract 105, the service user will no longer need to pay from the MFP 104 for the blockchain usage fee when processing the NFT service information notification and NFT service termination notification.

[0040] In S206, the smart contract 105 determines the verification and approval result of the added block in the blockchain 100, and if the block addition is approved (YES), it transitions to S207, and if it is not approved (NO), it transitions to S208. In S207, the smart contract 105 sends a transaction success response to the transaction sender and returns the process to S201. The address information of the NFT block generated if the transaction is successful is linked to the NFT token ID and stored in the smart contract 105.

[0041] On the other hand, in S208, the smart contract 105 sends a transaction failure response to the transaction sender and returns the process to S201. Also, if it is determined in S204 that a block will not be added, in S209 the smart contract 105 sends the transaction responses generated in each process to the transaction sender and returns the process to S201.

[0042] If it is determined in S202 that the transaction is not an issuance, then in S210 the smart contract 105 determines whether the received transaction contains a token ID, and if it does (YES), it transitions to S211, and if it does not (NO), it transitions to S208. In S211, the smart contract 105 determines whether the received transaction is a purchase, and if it is a purchase (YES), it transitions to S212, and if it is not a purchase (NO), it transitions to S213. In S212, the smart contract 105 executes an NFT purchase process and transitions to S204. Here, the smart contract 105 sets the wallet 3 of the service user (MFP 104) as the source of payment for the fee for adding an NFT block and transaction block to the blockchain 100.

[0043] If it is determined in S211 that the transaction is not a purchase, then in S213 the smart contract 105 determines whether the received transaction processing is a service information notification. Here, if it is a service information notification (YES), the process transitions to S214, and if it is not a service information notification (NO), the process transitions to S215. In S214, the smart contract 105 executes NFT service information notification processing and transitions to S204. Here, the smart contract 105 sets wallet 1 set in the smart contract 105 as the payment source for the fee for adding an NFT block and transaction block to the blockchain 100.

[0044] If it is determined in S213 that the notification is not a service information notification, then in S215 the smart contract 105 determines whether the processing of the received transaction is a service termination notification. Here, if it is a service termination notification (YES), the process transitions to S216, and if it is not a service termination notification (NO), the process transitions to S217. In S216, the smart contract 105 executes NFT service termination notification processing and transitions to S204. Here, the smart contract 105 sets wallet 1 set in the smart contract 105 as the payment source for the fee for adding an NFT block and a transaction block to the blockchain 100.

[0045] If it is determined in S215 that the transaction is not a service termination notification, then in S217 the smart contract 105 determines whether the processing of the received transaction is service monitoring. Here, if the answer is service monitoring (YES), the process transitions to S218, and if the answer is not service monitoring (NO), the process transitions to S208. In S218, the smart contract 105 generates a service monitoring response, and if the address of the sender of the transaction is a service provider (service provider server), the smart contract 105 sets the service information 170 set in the NFT in the response. On the other hand, if the sender address is not a service provider, the smart contract 105 sets the response to indicate that service information cannot be obtained. In this case, no NFT block or transaction block is added to the blockchain 100, so no fee is paid. After that, the process transitions to S204.

[0046] As described above, the smart contract 105's processing related to issuance, purchase, service information notification, service termination notification, and service monitoring in the NFT service has been explained. In this way, the smart contract 105 can execute general processing such as issuance and purchase using NFTs, as well as processing related to the services provided, such as service information notification, service termination notification, and service monitoring. Furthermore, by increasing the number of decision branches in S211, 213, 215, and 217, the smart contract 105 can accommodate a variety of services. Furthermore, at each branch, it is possible to individually set a wallet that will be used as the payment source for fees corresponding to the processing executed.

[0047] <NFT Issuance Process> Referring to FIG. 3, the detailed processing procedure of the NFT issuance process (S203) by the smart contract 105 according to this embodiment will be described. The processes described below are realized, for example, by the CPU 1001 of the information processing apparatus 1000 that executes the program of the smart contract 105 reading the program stored in the ROM 1002 or the HDD 1005 into the RAM 1003 and executing it. For NFT issuance, in order to generate an NFT block, the content set in the NFT block is set.

[0048] In S301, the smart contract 105 sets the NFT name and the owner of the NFT. In the case of issuance 112 in FIG. 1, NFT151 is set as the NFT name and wallet 162 is set as the owner of the NFT. Subsequently, in S302, the smart contract 105 sets the service type of the NFT in the NFT block. Depending on the service type set in S302, the information notified from the NFT to the smart contract 105 is changed.

[0049] In S303, the smart contract 105 obtains the number of payment times of the fee for the block added to the blockchain 100 for NFT service information notification. For example, in the case of a printing service, the smart contract 105 sets the number of blocks generated on the blockchain based on the number of printed sheets provided by the NFT. Subsequently, in S304, the smart contract 105 multiplies the number of payment times of the block addition fee by the block addition fee to obtain the total fee required for block addition. In S305, the smart contract 105 sets the token (amount) for NFT sales. The sales token amount is set as the token amount as an NFT for providing the service and the total token amount (total amount) obtained by combining the total fee obtained in S304.

[0050] In S306, the smart contract 105 sets the wallet 161 prepared by the NFT development company as the payment source for the fee. In S307, the smart contract 105 sets the payment destination at the time of NFT purchase to the wallet of the service provider company. In S308, the smart contract 105 sets the payment source of the tokens required for NFT issuance to the wallet of the service provider company. In S309, the smart contract 105 generates the token ID of the NFT. The token ID is generated as an ID unique to all issued NFTs. In S310, the smart contract 105 generates an NFT block. The payment source for the fee for block addition is set to the wallet of the service provider company.

[0051] <NFT Purchase Process> Referring to FIG. 4, the detailed processing procedure of the NFT purchase process (S212) by the smart contract 105 according to the present embodiment will be described. The processing described below is realized, for example, by the CPU 1001 of the information processing apparatus 1000 that executes the program of the smart contract 105 reading the program stored in the ROM 1002 or the HDD 1005 into the RAM 1003 and executing it.

[0052] In S401, the smart contract 105 acquires the token balance of the purchaser's wallet. In S402, the smart contract 105 determines whether the token balance of the purchaser's wallet is greater than the token amount required for purchase. If it is greater (YES), it transitions to S403; if it is less (NO), it transitions to S404. In S404, the smart contract 105 generates a purchase failure response including insufficient balance information and ends the processing of this flowchart.

[0053] Meanwhile, in S403, the smart contract 105 generates a transaction to send tokens in an amount equal to the purchase price of the NFT minus the total fee to the service provider's wallet. Next, in S405, the smart contract 105 generates a transaction to send tokens equivalent to the total fee to the smart contract 105's wallet (wallet 161). In S406, it is determined whether the transactions generated in S403 and S405 above have been approved by the blockchain; if approved (YES), the process transitions to S407; if not approved (NO), the process transitions to S408. In S408, the smart contract 105 generates a purchase failure response in the blockchain 100, and ends the processing of this flowchart.

[0054] At S407, the smart contract 105 sets the service start date as information in the NFT block and the service end date based on the service content. By setting the service end date at the time of purchase, it becomes possible to automatically terminate the service from the smart contract 105. At S409, the smart contract 105 sets the owner of the NFT to the wallet address of the purchaser.

[0055] In S410, the smart contract 105 generates an NFT block with a changed owner. The payment source for the fee for adding the NFT block to the blockchain is set to the wallet (wallet 163) of the MFP 104 (service user).

[0056] <Service information notification processing> A detailed processing procedure of the NFT service information notification process (S214) by the smart contract 105 according to this embodiment will be described with reference to Figure 5. To generate an NFT block, the NFT service information notification adds an NFT block in which the service information 170 held in the NFT has been modified to the blockchain 100. The processing described below is realized, for example, by the CPU 1001 of the information processing device 1000 that executes the program of the smart contract 105 reading the program stored in the ROM 1002 or HDD 1005 into the RAM 1003 and executing it.

[0057] In S501, the smart contract 105 generates an NFT block for changing the NFT service information 170. Next, in S502, the smart contract 105 obtains the service information 716 of the MFP 104 from the service information notification 118 transaction received from the MFP 104 in S201, and writes it to the service information 170 of the NFT block generated in S501. Here, the smart contract 105 may accept payment of tokens for extending the service through the service information notification transaction. In this case, the NFT service can be extended by extending the NFT service termination notification date. In S503, the smart contract 105 sets the smart contract 105's wallet 161 as the payment source for the fee for adding the NFT block, and ends the processing of this flowchart.

[0058] <Service termination notification processing> Referring to FIG. 6, the detailed processing procedure of the NFT service termination notification process (S216) by the smart contract 105 according to the present embodiment will be described. The NFT service termination notification generates an NFT block for which the service termination notification has been made. Therefore, the service state held in the NFT is changed to the termination state, and the NFT block is added to the blockchain 100. The processing described below is realized, for example, when the CPU 1001 of the information processing apparatus 1000 that executes the program of the smart contract 105 reads out the programs stored in the ROM 1002 and the HDD 1005 and executes them in the RAM 1003.

[0059] In S601, the smart contract 105 checks the service state of the NFT and checks whether the termination conditions are met based on the service termination notification date, service information, etc. In S602, the smart contract 105 determines whether the service termination conditions are met. If they are met (YES), the process proceeds to S603; if not (NO), the process proceeds to S604. In S604, the smart contract 105 generates a failure response for the NFT service termination notification transaction and ends the processing of this flowchart.

[0060] On the other hand, in S603, the smart contract 105 generates an NFT block for the NFT service termination notification. Subsequently, in S605, the smart contract 105 changes the owner of the generated NFT block from the wallet of the MFP 104 to the wallet of the service provider company. Further, in S606, the smart contract 105 sets the service termination notification information in the generated NFT block and ends the processing of this flowchart. Here, the payment source of the fee for adding the NFT block is set to the wallet 161 of the smart contract 105.

[0061] <Hardware Configuration of MFP> An example of the hardware configuration of a controller unit 700 of the MFP 104 according to this embodiment and a device built into the MFP will be described with reference to Fig. 7. By purchasing an NFT sold on the marketplace server 103, it becomes possible to use the services provided by the MFP 104.

[0062] The MFP 104 includes a controller unit 700, an operation panel 709, a print engine 713, and a scanner 715. The controller unit 700 includes a CPU 702, a RAM 703, a ROM 704, and a storage device 705, each of which is directly connected to a system bus 701. The controller unit 700 also includes a network I / F 706, a display controller 707, a processing I / F 708, a print controller 712, and a scan controller 714, and is also connected to external devices via each of these units. These components are connected to the system bus 701 and can communicate with each other.

[0063] The CPU 702 is a central processing unit that controls the overall operation of the controller unit 700. The RAM 703 is a volatile memory. The ROM 704 is a non-volatile memory that stores a startup program for the CPU 702. The storage device 705 is a storage device (e.g., a hard disk drive: HDD) with a larger capacity than the RAM 703. The storage device 705 stores a control program for the MFP executed by the CPU 702. The storage device 705 may be replaced with another storage device that has the same functions as a hard disk drive, such as a solid state drive (SSD). The storage device 705 also has a wallet 163 for the MFP 104 that accesses the blockchain 100, and holds address information on the blockchain 100, virtual currency (tokens), private keys, public keys, and NFT information. The NFT information includes the name of the NFT owned by the MFP, the NFT token (contract address and token ID), the token URI, a description of the NFT, etc. The storage device 705 also stores an NFT service program for setting the wallet used to generate a transaction to the wallet 161 of the smart contract 105 when using the NFT service. After the NFT service starts, the NFT service program is deployed to the RAM 703 and executed by the CPU 702.

[0064] At startup, such as when the power is turned on, the CPU 702 executes a startup program stored in the ROM 704. This startup program reads a control program stored in the storage device 705, expands it on the RAM 703, and is executed. After executing the startup program, the CPU 702 subsequently executes the control program expanded on the RAM 703 to perform control. The CPU 702 also stores data used when executing the control program in the RAM 703 and reads and writes it. The storage device 705 can further store various settings required when executing the control program, image data read by the scanner 715, and service information 716 to be managed by the NFT 151, which are read and written by the CPU 702.

[0065] The CPU 702 communicates with nodes (information processing devices) of the blockchain 100 via the network I / F 706, the smart contract 105, and the marketplace server 103 on the Internet via a gateway. The MFP 104 also stores in its ROM 704 a control program for transmitting transactions of a service information notification 118 for notifying the smart contract 105 of service information 716 and a service termination notification 121 for terminating the service.

[0066] The display controller 707 controls the screen display of the touch panel on the connected operation panel 709 in response to instructions from the CPU 702. The processing I / F 708 inputs and outputs processing signals. The processing I / F 708 is connected to the processing panel 509, and when the touch panel is pressed, the CPU 702 acquires the coordinates of the touch on the touch panel via the processing I / F 708. The print controller 712 transmits control commands and image data to the connected print engine 713 in response to instructions from the CPU 702. The print engine 713 prints the received image data on a sheet in accordance with the control commands received from the print controller 712. A detailed description of the print engine 713 is not the focus of this embodiment, so further description will be omitted.

[0067] In response to instructions from the CPU 702, the scan controller 714 transmits control commands to the connected scanner 715 and writes image data received from the scanner 715 to the RAM 703. The scanner 715 reads an original document placed on a platen glass (not shown) provided in the MFP 104 or an original document placed in the ADF using an optical unit in accordance with the control command received from the scan controller 714. The original document read by the scanner 715 is stored in the RAM 703 as image data, and the image data is converted by the CPU 702 into a PDF / JPEG / TIFF file format in accordance with the file format setting and saved in the storage device 705.

[0068] <sequence> 8, a sequence from the start of service for an MFP that issues and purchases an NFT to notification of service termination in the service providing system according to this embodiment will be described. Here, the sequence between the blockchain 100, smart contract 105, MFP 104, service providing server 102, and marketplace server 103 is shown.

[0069] In S801, the service providing server 102 sends an issuance 111 to the smart contract 105 to issue the NFT 151. In S802, the smart contract 105 requests approval from the blockchain 100 to add the NFT block of the NFT 151 by issuance 112. When the blockchain 100 approves the block of the NFT 151, it sets the owner of the NFT 151 in the wallet 162 and adds it to the blockchain 100. The payment source for adding the NFT block and transaction by issuance 112 is the wallet 162 of the service providing server 102.

[0070] In S803, the smart contract 105 confirms that the NFT block 141, which sets the owner of the NFT 151 to the wallet 162, has been added to the blockchain 100. In S804, the smart contract 105 sends a response to the issuance 111 to the service providing server 102 indicating that the NFT block 141 for the NFT 151 has been generated. In S805, the service providing server 102 sends an NFT selling instruction 130 to the marketplace server 103, and sells the NFT 151 on the marketplace server 103.

[0071] Next, in S806, the MFP 104 sends a purchase instruction 132 for the NFT 151 using the wallet 163 to the marketplace server 103. In S807, the marketplace server 103 sends an NFT purchase notification 131 including the wallet address of the wallet 163 to the service providing server 102, notifying the service providing server 102 of the purchase of the NFT 151. In S808, the service providing server 102 sends a purchase 114 to the smart contract 105 to change the owner of the NFT 151 to the wallet 163, and starts the purchase process for the NFT 151.

[0072] In S809, the smart contract 105 requests approval to add the NFT block of NFT 151 to the blockchain 100, and waits for the NFT block of NFT 151 to be added to the blockchain 100. The wallet 163 that instructed the purchase is set as the payment source for the fee for adding the NFT block and the purchase transaction to the blockchain. In S810, the smart contract 105 confirms that the NFT block 142 of NFT 151, whose owner has been changed to wallet 163, has been added to the blockchain 100. In S811, the smart contract 105 notifies the service providing server 102, as a response to the purchase 114, that the NFT 151 has been purchased by the MFP 104. In S812, the MFP 104 references the NFT block 142 of NFT 151 and confirms the owner of NFT 151. Furthermore, in S813, the MFP 104 confirms that the owner of NFT 151 is wallet 163, and starts the NFT service. The MFP 104 obtains information for the NFT service from the NFT block 142 of the NFT 151, and performs operations such as obtaining necessary information and installing applications.

[0073] The following steps S814 to S820 are a sequence during the provision of the NFT service, in which the NFT service information notification 118 and monitoring 123 are repeatedly executed. In S814, the MFP 104 sends the NFT service information notification 118 to the smart contract 105 at the timing of notifying the NFT service information 716. In S815, the smart contract 105 requests approval of the NFT block 142 in which the service information 170 of the NFT 151 has been updated by the service information notification 119 from the blockchain 100. The wallet 161 of the smart contract 105 is set as the payer of the fee for adding the NFT block in which the service information 170 of the NFT 151 has been updated. The fee is paid to the node that added the NFT block to the blockchain 100 as a reward for the computation. In S816, the smart contract 105 confirms that the NFT block 142 in which the service information 170 has been updated has been added to the blockchain 100. In S817, the smart contract 105 sends a response of the service information notification 118 to the MFP 104.

[0074] In S818, the service providing server 102 sends monitoring 123 to the smart contract 105 to monitor the service information 170 of the NFT 151. In S819, the smart contract 105 references the NFT block 143 in the blockchain and acquires the service information 170 included in the NFT block 143. In S820, the smart contract 105 transmits the service information 170 acquired in S819 to the service providing server 102 as a response to the monitoring 123.

[0075] At S821, the MFP 104 sends a service termination notice 121 to the smart contract 105 at the timing when the service of the NFT 151 ends. At S822, the smart contract 105 requests the blockchain 100 to approve the block 144 in which the owner of the NFT 151 is changed to the wallet 162 by sending a service termination notice 122 to the blockchain 100. The payer of the fee for adding the NFT block due to the service termination notice 122 of the NFT 151 is set to the wallet 161 of the smart contract 105. At S823, the smart contract 105 confirms that the NFT block 144 with the owner updated to the wallet 162 due to the service termination notice 121 has been added to the blockchain 100. At S824, the smart contract 105 sends a response to the service termination notice 121 to the MFP 104.

[0076] As described above, referring to FIG. 8, the sequence of the service information notification system when the smart contract 105 provides services to the MFP 104 has been described. In this way, the service provider server 102 can monitor the service information 716 of the MFP of the service user by using the smart contract 105, and can automatically start and end the provided services. Also, by moving the owner of the NFT 151 to the wallet 163 of the MFP 104, the service start date can be set. Also, the smart contract 105 determines the service termination notice date on the service start date, and the MFP 104 can determine the service termination notice date by acquiring the service information of the NFT 151. In this way, the service provision system using NFTs can flexibly construct various processes by using smart contracts.

[0077] <MFP's NFT Service Information Notification Processing Flow> The processing procedure for NFT service information notification of the MFP 104 according to this embodiment will be described with reference to Figure 9. The processing described below is realized, for example, by the CPU 702 reading a program stored in the ROM 704 or storage device 705 into the RAM 703 and executing it. This flowchart starts when the function for NFT service information notification is enabled.

[0078] In S901, the CPU 702 acquires wallet information stored in the storage device 705 of the MFP 104. The wallet information includes a control program for communicating with the blockchain 100, account information, and private key and public key information required when adding a block. When accessing a block in the blockchain 100, the wallet uses the wallet program to access one of the nodes that make up the blockchain 100, sends a transaction, and receives the response, thereby enabling communication with the blockchain. The wallet also stores authentication information and performs authentication processing when accessing the blockchain 100.

[0079] In S902, the CPU 702 obtains the NFT information stored in the storage device 705. The NFT information is saved at the time of purchase, and the functions to be activated and the service information 170 to be notified to the blockchain 100 are determined from the service information 170 provided by the NFT. In S903, the CPU 702 determines whether or not a wallet exists from the wallet information read from the storage device 705, and if a wallet exists (YES), the process transitions to S904, and if not (NO), the process transitions to S905. In S905, the CPU 702 displays on the operation panel 709 that there is no wallet information and that the blockchain is not connected, and ends the processing of this flowchart.

[0080] In S904, the CPU 702 accesses the blockchain 100 and reads the NFT block from the read NFT information. If the owner of the NFT is the wallet address of the wallet read in S901, the NFT service functions, it determines that a valid NFT exists (YES), and the process transitions to S907. On the other hand, if it determines that a valid NFT does not exist (NO), the process transitions to S906. In S906, the CPU 702 displays on the operation panel 709 that there are no available NFTs, and ends the processing of this flowchart.

[0081] Meanwhile, in S907, the CPU 702 acquires NFT information from the blockchain 100 and confirms the owner of the NFT. In S908, the CPU 702 confirms whether the wallet address of the NFT owner acquired in S907 is the same as that of the CPU 702's own device, and if they are the same (YES), the process proceeds to S909; if not, the process of this flowchart ends.

[0082] In S909, the CPU 702 acquires the service information 716 to be notified to the notification destination of the NFT service information notification. In S910, the CPU 702 transitions to S911 if there is service information 716 to notify the smart contract 105 (YES), and transitions to S912 if there is no service information 716 (NO). In S911, the CPU 702 sends a service information notification to the smart contract 105 and returns the process to S909.

[0083] In S912, the CPU 702 determines whether the service termination notification conditions, such as the end date of the NFT service, have been met, and if the service termination notification conditions have been met (YES), the process transitions to S913, and if the service termination notification conditions have not been met (NO), the process transitions to S909. In S913, the CPU 702 sends a service termination notification to the smart contract 105, and ends the processing of this flowchart.

[0084] As described above, the flowchart of the NFT service information notification process of the MFP 104 has been described with reference to Fig. 9. In this way, by notifying the smart contract 105 of the service information notification 118 and the service end notification 121 from the MFP 104, the NFT service can be implemented by the MFP 104. For example, in the case of a print count service, the print count service of the MFP 104 can be realized by notifying the number of prints by the service information notification 118 and, when the upper limit of the print count service is reached, by notifying the service end notification 121. Furthermore, in the case of a consumables delivery service by the MFP 104, by notifying the smart contract 105 of the service information notification 118 when the consumables of the MFP 104 are running low, the service provider can manage the delivery of the consumables by monitoring 123.

[0085] As described above, the computer program according to this embodiment causes a computer of an information processing device (node) that executes a smart contract to function as follows. Specifically, the computer program causes the computer to receive a transaction related to a token containing service usage information in a blockchain network and execute the processing requested by the received transaction. The computer program also causes the computer to determine whether to add a block to the blockchain based on the executed processing. When adding a block, the computer program also sets a first wallet owned by the information processing device or a second wallet owned by the transaction issuer as the payment source for the fee for adding the block. This allows for the convenient payment of fees when using a service on a blockchain network. Thus, the smart contract of the present invention allows users of a printing device to pay the fee and service usage fee incurred each time they use a service when purchasing an NFT in a lump sum. The fee paid in advance is transferred to the smart contract wallet (first wallet), and the fee is paid from that wallet each time the service is used. Therefore, service users only need to pay a predetermined fee when purchasing an NFT, eliminating the need to pay fees each time they use the service. This reduces the user's resistance to using the service.

[0086] <Modification> The present invention is not limited to the above-described embodiment, and various modifications are possible. In the above-described embodiment, an example has been described in which a non-fungible token (NFT) is used as the token. However, other tokens may be used depending on the form of service provision. For example, any token that can be owned or whose value can be transferred can be applied to the present invention.

[0087] In the above embodiment, a portion of the fee paid when purchasing an NFT is pooled in a smart contract wallet, and the fee paid for each use of the service is paid from the smart contract wallet. Here, after printing the printable number of sheets granted by purchasing an NFT, there may be a surplus in the pooled balance (amount of tokens). In such cases, the surplus may be returned to the printable number of sheets. On the other hand, if the pooled balance is insufficient, the balance may be replenished from the wallet of the service provider, for example.

[0088] Additionally, a portion of the fee paid when purchasing an NFT may be pooled in the service provider's wallet. In this case, the service provider can offer a service that increases the number of printable sheets when the wallet balance is high. Furthermore, the pooled balance may be used as a temporary charge when the number of printable sheets is insufficient.

[0089] The disclosure of this specification includes the following computer program, information processing device, and control method thereof. (Item 1) A computer that is an information processing device that executes smart contracts, A receiving means for receiving a transaction related to a token including service usage information in a blockchain network; an execution means for executing a process requested by the received transaction; A determination means for determining whether or not to add a block to the blockchain according to the executed process; a setting means for setting a first wallet owned by the information processing device or a second wallet owned by the issuer of the transaction as a payment source for a fee for adding the block when the block is added; A computer program characterized by causing the computer to function as follows. (Item 2) The computer program described in item 1, characterized in that, when the processing requested by the received transaction is a token issuance process, the execution means sets the total amount including the total fee based on the number of times blocks are added and the fee for notifying service usage information to be performed when using the service, and the fee for using the service, as the fee for purchasing the token, and further sets the payment destination of the total fee to the first wallet and the payment destination of the fee for using the service to the second wallet owned by the issuer of the transaction. (Item 3) Item 3. The computer program according to item 2, wherein the setting means sets the second wallet owned by the issuer of the transaction as the payer of a fee for adding a block in association with the issuance process when the processing requested by the received transaction is a token issuance process. (Item 4) The computer program described in item 3, characterized in that, when the processing requested by the received transaction is a token purchase process, the execution means transmits the total fee from the purchaser's wallet to the first wallet and transmits the fee for using the service to the second wallet owned by the issuer of the transaction that requested the issuance process. (Item 5) The computer program according to any one of items 1 to 4, characterized in that, when the processing requested by the received transaction is a token purchase processing, the setting means sets the second wallet owned by the issuer of the transaction as the payment source for the fee for adding the block. (Item 6) The computer program according to any one of items 1 to 5, characterized in that the setting means sets the first wallet owned by the information processing device as the payment source for the fee for adding the block when the processing requested by the received transaction is a processing to notify service usage information. (Item 7) The computer program according to any one of items 1 to 6, characterized in that the setting means sets the first wallet owned by the information processing device as the payment source for the fee for adding the block when the processing requested by the received transaction is a processing to terminate the use of a service. (Item 8) The computer program according to any one of items 1 to 7, characterized in that the determination means determines not to add the block if the processing requested by the received transaction is a processing to monitor service information. (Item 9) 9. The computer program of any one of items 1 to 8, wherein the first wallet is specified when the smart contract is placed on a blockchain. (Item 10) 10. The computer program according to any one of items 1 to 9, wherein the service is a service provided by a printing device. (Item 11) Item 11. The computer program according to item 10, wherein the token is linked to the number of printable sheets in the printing device. (Item 12) 12. The computer program according to any one of items 1 to 11, wherein the token is a non-fungible token. (Item 13) An information processing device that executes a smart contract, A receiving means for receiving a transaction related to a non-fungible token including service usage information in a blockchain network; an execution means for executing a process requested by the received transaction; A determination means for determining whether or not to add a block to the blockchain according to the executed process; a setting means for setting a first wallet owned by the information processing device or a second wallet owned by the issuer of the transaction as a payment source for a fee for adding the block when the block is added; An information processing device comprising: (Item 14) A control method for an information processing device that executes a smart contract, comprising: a receiving step in which a receiving means receives a transaction related to a token including service usage information in a blockchain network; an execution step in which an execution means executes the processing requested by the received transaction; a determination step in which a determination means determines whether or not to add a block to the blockchain according to the executed process; a setting step in which, when adding the block, the setting means sets a first wallet owned by the information processing device or a second wallet owned by the issuer of the transaction as a payment source for a fee for adding the block; 10. A method for controlling an information processing device, comprising:

[0090] <Other embodiments> The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program.The present invention can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.

[0091] The invention is not limited to the above-described embodiments, and various changes and modifications can be made without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]

[0092] 100: Blockchain, 151: NFT (Non-Fungible Token), 105: Smart Contract, 104: MFP (Multi Function Peripheral), 161: Smart Contract Wallet, 162: Service Provider Wallet, 163: MFP Wallet, 103: Marketplace, 716: MFP Service Information, 170: NFT Service Information

Claims

1. A computer that is an information processing device that executes smart contracts, A receiving means for receiving a transaction related to a token including service usage information in a blockchain network; an execution means for executing a process requested by the received transaction; A determination means for determining whether or not to add a block to the blockchain according to the executed process; a setting means for setting a first wallet owned by the information processing device or a second wallet owned by the issuer of the transaction as a payment source for a fee for adding the block when the block is added; A computer program characterized by causing the computer to function as follows.

2. The computer program of claim 1, wherein the execution means, when the processing requested by the received transaction is a token issuance process, sets a total amount including a total fee based on the number of times blocks are added and a fee for notifying service usage information to be performed when the service is used, and a fee for using the service, as the fee for purchasing the token, and further sets the payment destination of the total fee to the first wallet and the payment destination of the fee for using the service to the second wallet owned by the issuer of the transaction.

3. 3. The computer program according to claim 2, wherein the setting means sets the second wallet owned by the issuer of the transaction as a payer of a fee for adding a block in association with the issuance process when the process requested by the received transaction is a token issuance process.

4. The computer program according to claim 3, wherein the execution means, when the processing requested by the received transaction is a token purchase process, transmits the total fee from the purchaser's wallet to the first wallet and transmits the fee for using the service to the second wallet owned by the issuer of the transaction that requested the issuance process.

5. 5. The computer program according to claim 4, wherein the setting means sets the second wallet owned by the issuer of the transaction as a payment source for a fee for adding the block when the processing requested by the received transaction is a token purchase processing.

6. The computer program according to any one of claims 1 to 5, characterized in that the setting means sets the first wallet owned by the information processing device as the payment source for the fee for adding the block when the processing requested by the received transaction is a processing to notify service usage information.

7. The computer program according to claim 6, characterized in that the setting means sets the first wallet owned by the information processing device as the payment source for the fee for adding the block when the processing requested by the received transaction is a processing to terminate the use of a service.

8. 8. The computer program according to claim 7, wherein the determining means determines not to add the block if the process requested by the received transaction is a process for monitoring service information.

9. 7. The computer program of claim 6, wherein the first wallet is specified when the smart contract is placed on a blockchain.

10. 7. The computer program according to claim 6, wherein the service is a service provided by a printing device.

11. 11. The computer program product according to claim 10, wherein the token is linked to the number of printable sheets in the printing device.

12. 8. The computer program product of claim 7, wherein the token is a non-fungible token.

13. An information processing device that executes a smart contract, A receiving means for receiving a transaction related to a token including service usage information in a blockchain network; an execution means for executing a process requested by the received transaction; A determination means for determining whether or not to add a block to the blockchain according to the executed process; a setting means for setting a first wallet owned by the information processing device or a second wallet owned by the issuer of the transaction as a payment source for a fee for adding the block when the block is added; An information processing device comprising:

14. A control method for an information processing device that executes a smart contract, comprising: a receiving step in which a receiving means receives a transaction related to a token including service usage information in a blockchain network; an execution step in which an execution means executes the processing requested by the received transaction; a determination step in which a determination means determines whether or not to add a block to the blockchain according to the executed process; a setting step in which, when adding the block, the setting means sets a first wallet owned by the information processing device or a second wallet owned by the issuer of the transaction as a payment source for a fee for adding the block; 10. A method for controlling an information processing device, comprising:

Images