Control methods, IoT devices, and programs

Abstract

In this control method for an IoT appliance, the IoT appliance and a user using the IoT appliance each have a digital account, and the method includes: acquiring first payment transaction data for the user using the IoT appliance to utilize a token to pay a usage fee for the IoT appliance (S1); identifying the digital account of the IoT appliance associated with an identifier allocated uniquely to hardware of the IoT appliance, from the acquired first payment transaction data (S2); and deducting the token from the digital account of the user and adding the same to the digital account of the IoT appliance, to transfer the usage fee for the IoT appliance to the digital account of the IoT appliance, on the basis of the acquired first payment transaction data (S3).

Description

Technical Field

[0001] The present disclosure relates to a method for controlling an IoT device, an IoT device, and a program.

Background Art

[0002] For example, in Patent Document 1, a technique is disclosed in which claims or payments can be made based on authenticated information on a blockchain exchanged between an ADEPT WASHER, which is an IoT (Internet of Things)-compatible washing machine, and a retailer.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the technique of Patent Document 1 is a technique in the case where a washing machine is owned by one or more fixed owners such as a coin laundry. Therefore, it cannot be applied when an IoT device such as a washing machine is shared and payment is desired each time it is used, or when profits such as usage fees are distributed to a plurality of replaceable owners.

[0005] The present disclosure has been made in view of the above circumstances, and an object thereof is to provide a method for controlling an IoT device that can manage income such as usage fees by the IoT device itself.

Means for Solving the Problems

[0006] To achieve the above objective, the control method of the present disclosure is a control method for an IoT device, wherein the IoT device and the user using the IoT device each have a digital account, and the user using the IoT device obtains first payment transaction data for paying the usage fee of the IoT device with tokens, identifies the digital account of the IoT device associated with an identifier uniquely assigned to the hardware of the IoT device from the obtained first payment transaction data, and transfers the usage fee of the IoT device to the digital account of the IoT device by deducting the tokens from the user's digital account and adding them to the digital account of the IoT device based on the obtained first payment transaction data. Furthermore, if the IoT device is owned by one or more owners, and the token is deposited into the digital account of the IoT device, the one or more owners of the IoT device are identified, and the amount to be allocated to the identified one or more owners is determined by referring to information that associates the identifier with the one or more owners of the IoT device and allocation information indicating the allocation to the one or more owners, and the token deposited into the digital account of the IoT device is allocated to the digital account of the identified one or more owners according to the determined allocation amount. .

[0007] These comprehensive or specific embodiments may be implemented as a system, method, integrated circuit, computer program, or recording medium such as a computer-readable CD-ROM, or as any combination of a system, method, integrated circuit, computer program, and recording medium. [Effects of the Invention]

[0008] According to this disclosure, it is possible to realize a control method for IoT devices that allows the IoT devices themselves to manage revenue such as usage fees. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is a diagram showing an example of the overall configuration of the system according to the embodiment. [Figure 2] Figure 2 shows an example of the configuration of an IoT device according to the embodiment. [Figure 3] Figure 3 shows an example of the configuration of a terminal according to the embodiment. [Figure 4] Figure 4 shows an example of the configuration of a BC node according to the embodiment. [Figure 5] Figure 5 is a flowchart showing an example of a method for controlling IoT devices using the system according to the embodiment. [Figure 6] Figure 6 is a sequence diagram showing the digital account opening process according to the embodiment. [Figure 7] Figure 7 is another sequence diagram showing the digital account opening process according to the embodiment. [Figure 8] Figure 8 is a sequence diagram showing the payment processing for usage fees according to the embodiment. [Figure 9] Figure 9 is a sequence diagram showing an example of the detailed processing of step S208 shown in Figure 8. [Figure 10] Figure 10 shows an example of a table for managing IoT devices, owners, and allocations according to the embodiment. [Figure 11] Figure 11 is a sequence diagram showing another example of the process from step S208 onwards, as shown in Figure 8. [Figure 12] Figure 12 is a sequence diagram showing the log data purchase fee payment process according to the embodiment. [Figure 13] Figure 13 is a sequence diagram showing another example of the detailed processing of step S310 shown in Figure 12. [Figure 14] Figure 14 is a diagram illustrating that different types of IoT devices according to the embodiment can be used to make payments using different tokens. [Figure 15] Figure 15 is a sequence diagram showing a modified example of the payment processing for usage fees according to the embodiment. [Figure 16] Figure 16 is a sequence diagram showing a modified example of the payment processing for usage fees according to the embodiment. [Figure 17] Figure 17 shows another example of the overall configuration of the system according to the embodiment. [Figure 18] Figure 18 is a sequence diagram showing an example of the payment process for maintenance costs according to the embodiment. [Figure 19] Figure 19 is a sequence diagram showing another example of the payment processing for maintenance costs according to the embodiment. [Figure 20] Figure 20 is a sequence diagram showing yet another example of the payment processing for maintenance costs according to the embodiment. [Figure 21]FIG. 21 is a sequence diagram showing a modification example of the withdrawal process of maintenance fees according to the embodiment. [Figure 22] FIG. 22 is a sequence diagram showing a modification example of the withdrawal process of maintenance fees according to the embodiment. [Figure 23] FIG. 23 is a sequence diagram of the withdrawal process of maintenance fees according to other modification examples.

MODE FOR CARRYING OUT THE INVENTION

[0010] The control method of one embodiment of the present disclosure is a control method for IoT devices. Both the IoT device and the user who uses the IoT device have digital accounts. The user who uses the IoT device obtains first payment transaction data for paying the usage fee of the IoT device with tokens. From the obtained first payment transaction data, the digital account of the IoT device associated with the identifier uniquely assigned to the hardware of the IoT device is specified. Based on the obtained first payment transaction data, the tokens are reduced from the user's digital account and added to the digital account of the IoT device, thereby transferring the usage fee of the IoT device to the digital account of the IoT device.

[0011] In this way, by giving the IoT device a digital account and transferring the usage fee, which is the usage fee of the IoT device, to the digital account of the IoT device, the IoT device itself can manage income such as usage fees. As a result, it is possible to shift from the conventional form of purchasing and using IoT devices to a new form in which multiple users share and use IoT devices and pay fees each time they are used.

[0012] The first payment transaction data may include the address of the user's digital account indicating the payment source, the address of the IoT device's digital account indicating the payment destination, and the token indicating the usage fee of the IoT device.

[0013] Thus, the first payment transaction data includes the digital account of the user using the IoT device, the digital account of the IoT device, and the amount of tokens representing the usage fee. This makes it easy to transfer the usage fee for the IoT device used by the user from the user's digital account to the IoT device's digital account using tokens.

[0014] Furthermore, the identifier may include at least one of the following: the model number, part number, serial number, and license plate number of the IoT device.

[0015] This allows for the use of digital accounts linked to identifiers that cannot be easily changed, thus enabling more reliable identification of the digital accounts of IoT devices. Consequently, IoT devices can more reliably manage revenue such as usage fees.

[0016] Furthermore, a user who has purchased log data from the IoT device may obtain a second payment transaction data to pay the purchase price of the log data in tokens to the digital account of the IoT device, identify the digital account of the IoT device associated with an identifier uniquely assigned to the hardware of the IoT device from the obtained second payment transaction data, and transfer the purchase price of the log data to the digital account of the IoT device by deducting the tokens from the user's digital account and adding them to the digital account of the IoT device based on the obtained second payment transaction data.

[0017] In this way, by having the purchase price of the log data purchased from the IoT device transferred to the IoT device's digital account, the IoT device itself can manage its own income, including the purchase price of the log data.

[0018] Furthermore, a third payment transaction data may be obtained for paying the maintenance costs of the IoT device with tokens, a digital account to which the maintenance costs are to be paid may be identified from the obtained third payment transaction data, and the maintenance costs may be transferred to the digital account of the payee by deducting the tokens from the digital account of the IoT device and adding them to the digital account of the payee based on the obtained third payment transaction data.

[0019] In this way, by having IoT devices pay their maintenance costs from their digital accounts, the IoT devices themselves can manage their own expenses and income.

[0020] Furthermore, if the IoT device is owned by one or more owners and the token is deposited into the digital account of the IoT device, the one or more owners of the IoT device may be identified, and the amount to be allocated to the identified one or more owners may be determined by referring to a table that associates the identifier with the one or more owners of the IoT device and allocation information indicating the allocation to the one or more owners, and the token deposited into the digital account of the IoT device may be allocated to the digital account of the identified one or more owners according to the determined allocation amount.

[0021] In this way, the revenue deposited into the digital account of the IoT device is distributed to the owner, who is one or more owners. This allows for a shift from the traditional model of purchasing and using IoT devices to a new model where IoT devices are owned by multiple users who can switch between them, and the profits generated from the IoT devices are distributed among the multiple users who own the IoT devices.

[0022] Furthermore, the address of the digital account may be a blockchain address, and the digital account may be managed on a blockchain.

[0023] This means that the digital accounts of IoT devices will be managed on the blockchain, allowing the IoT devices themselves to manage their revenue, such as usage fees, using digital accounts that are traceable and tamper-proof.

[0024] Furthermore, the control method may also involve storing the acquired payment transaction data on the blockchain to activate a smart contract managed on the blockchain, causing the smart contract to transfer the tokens from the user's digital account to the IoT device's digital account.

[0025] In this way, smart contracts can be used to automatically transfer income from IoT devices to digital accounts.

[0026] Furthermore, the smart contract may also distribute the tokens deposited into the IoT device's digital account to the digital accounts of one or more identified owners.

[0027] In this way, smart contracts can be used to automatically distribute the profits generated by IoT devices to one or more owners of those IoT devices.

[0028] Furthermore, the control method may also store the acquired third payment transaction data on the blockchain, thereby activating a smart contract managed on the blockchain, and the smart contract may transfer the maintenance fee from the IoT device's digital account to the recipient's digital account.

[0029] In this way, smart contracts can be used to automatically pay for the maintenance costs of IoT devices from the devices' digital accounts.

[0030] Furthermore, a first terminal, distinct from the IoT device, may acquire a hardware-unique identifier assigned to the IoT device, determine the address of the IoT device's digital account, and output information linking the identifier and the address to a database for storage. For example, the first terminal may be a terminal owned by the manufacturer that produced the IoT device.

[0031] In this way, IoT devices can have digital accounts using network-accessible addresses. This allows IoT devices to manage their own revenue, such as usage fees.

[0032] Furthermore, the system may calculate the maintenance costs of the IoT device, generate a fourth transaction data to request that the IoT device take over the payment of the maintenance costs if the balance in the IoT device's digital account is less than the calculated maintenance costs, transmit the generated fourth transaction data to one or more other IoT devices different from the IoT device, and if the balance in the digital account of the first IoT device among the one or more other IoT devices is greater than the calculated maintenance costs, obtain the third payment transaction data and transfer the maintenance costs from the first IoT device's digital account to the digital account of the recipient of the maintenance costs. Here, for example, the maintenance costs include at least one of the following: electricity costs corresponding to the power consumed to operate the IoT device, maintenance costs for the IoT device, consumable parts costs for the IoT device, and travel expenses for the user performing maintenance on the IoT device.

[0033] In this way, if an IoT device's digital account balance is insufficient to cover expenses such as maintenance costs, other IoT devices can make the payments on its behalf. This allows IoT devices to manage their own expenses and income without the need for a user.

[0034] Furthermore, the maintenance costs of the IoT device may be calculated, and if the balance in the IoT device's digital account is less than the calculated maintenance costs, credit information including the IoT device's log information or the balance information of the IoT device's digital account may be transmitted to one or more other IoT devices different from the IoT device, a loan token equivalent to the maintenance costs may be obtained from the first IoT device among the one or more other IoT devices that has decided to cover the maintenance costs, the third payment transaction data may be obtained, the digital account to which the maintenance costs will be paid may be identified from the obtained third payment transaction data, and the loan token may be transferred from the IoT device's digital account to the recipient's digital account based on the obtained third payment transaction data and the loan token. Here, for example, the loan token may include at least one of the following: loan amount, interest, or loan term.

[0035] In this way, if an IoT device's digital account balance is insufficient to cover expenses such as maintenance costs, it can borrow from other IoT devices to make payments, and then repay the loan when its balance increases later. This allows IoT devices to manage their own expenses and income without the need for a user.

[0036] Furthermore, if the balance of the IoT device's digital account exceeds the maintenance cost, the loan token may be used to identify the first IoT device's digital account, and a token equivalent to the loan token may be transferred from the IoT device's digital account to the first IoT device's digital account.

[0037] In this way, electricity usage fees can be earned as income. This allows the electricity usage fees, which are the income deposited into the digital account of the IoT device, to be distributed among the owner, who is one or more owners.

[0038] Furthermore, the IoT device is a solar power generation facility that transmits electricity generated using solar cells, and the user utilizes the solar power generation facility to use electricity, and the usage fee for the IoT device may be an electricity usage fee.

[0039] An IoT device in one embodiment of the present disclosure has a digital account for both the IoT device and the user using the IoT device, and includes a communication unit that acquires first payment transaction data for the user using the IoT device to pay the usage fee for the IoT device with tokens, an identification unit that identifies the digital account of the IoT device associated with an identifier uniquely assigned to the hardware of the IoT device from the acquired first payment transaction data, and a writing unit that, based on the acquired first payment transaction data, deducts the tokens from the user's digital account and adds them to the digital account of the IoT device, thereby transferring the usage fee for the IoT device to the digital account of the IoT device.

[0040] The embodiments will be described below with reference to the drawings. Note that the embodiments described below are all specific examples of the present disclosure. Therefore, the numerical values, shapes, materials, components, arrangement and connection configurations of components, steps, and the order of steps shown in the following embodiments are examples of the present disclosure and are not intended to limit the present disclosure. Furthermore, among the components in the following embodiments, those not described in the independent claims representing an implementation of one aspect of the present disclosure will be described as arbitrary components. The implementations of the present disclosure are not limited to the current independent claims and may also be expressed by other independent claims.

[0041] (Embodiment) The embodiments will be described below with reference to the drawings.

[0042] [1 Overall Structure] This disclosure describes a system 100 that allows IoT devices and other devices to have digital accounts for digital currency on a distributed network such as a blockchain, and to send and receive digital currency.

[0043] Figure 1 shows an example of the overall configuration of the system 100 according to this embodiment. In this embodiment, as shown in Figure 1, the main characters are, for example, an IoT device 10, a user 20, and a manufacturer of the IoT device 30. The distributed network 50 shown in Figure 1 is, for example, a blockchain network and is described as being composed of multiple BC nodes 51, each having a distributed ledger, but is not limited to this. The distributed network 50 may also be composed of a database and multiple nodes.

[0044] [1.1 IoT devices 10] The IoT device 10 is, for example, a home appliance such as a washing machine, as shown in Figure 1, but is not limited to this. The IoT device 10 may also be a computer or other device installed in a space such as a shared room.

[0045] Furthermore, the IoT device 10 is connected to a distributed network 50 and can communicate with multiple BC nodes 51, and can also communicate with user terminals 20 and manufacturer terminals 30 that are connected to the distributed network 50.

[0046] Furthermore, the IoT device 10 has its own digital account 11 on the distributed network 50. The IoT device 10 manages its own income, etc., using the digital account 11. Here, the digital account 11 is an address determined and assigned to an identifier uniquely assigned to the hardware of the IoT device 10. Information linking the identifier of the IoT device 10 to the address assigned to it is stored in a database. In this embodiment, the digital account 11 is a blockchain account, and the identifier of the IoT device 10 and the address assigned to it are blockchain addresses. The database is a distributed ledger of each of the multiple BC nodes 51. The digital account 11 is like a passbook for the IoT device 10, stored on the distributed ledger, and records deposits or withdrawals of digital currency that constitute the income or expenses of the IoT device 10.

[0047] Figure 2 shows an example of the configuration of the IoT device 10 according to this embodiment.

[0048] The IoT device 10 comprises a processor, a memory containing a program that causes the processor to perform predetermined processing, and a communication interface, etc. In other words, the IoT device 10 is realized when the processor uses the memory to execute a predetermined program.

[0049] In this embodiment, the IoT device 10 is installed inside or integrally with the casing of a home appliance or the like. As shown in Figure 2, the IoT device 10 comprises a communication unit 101, a processing unit 102, and a distributed ledger storage unit 103. Each component will be described below.

[0050] The communication unit 101 communicates with multiple BC nodes 51, and also communicates with user terminals 20 and manufacturer terminals 30 connected to the distributed network 50.

[0051] In this embodiment, the communication unit 101 transmits and retrieves transaction data. The communication unit 101 also notifies the calculated usage fee or maintenance fee (which may be called maintenance cost).

[0052] The processing unit 102 calculates usage fees when the IoT device 10 is used by a user, and calculates maintenance costs if maintenance or other upkeep costs are incurred for the IoT device 10. Furthermore, if the IoT device 10 has multiple owners and a lump sum payment is made to the digital account 11, the processing unit 102 calculates the allocation amount.

[0053] Furthermore, the processing unit 102 is also an example of an identification unit and a writing unit. The processing unit 102 generates transaction data and executes a consensus algorithm for the transaction data with multiple BC nodes 51, etc. The processing unit 102 also performs the process of writing the transaction data that has gone through the consensus algorithm to the distributed ledger. The processing unit 102 may also execute smart contracts that are written to the distributed ledger and are running in memory. For example, by executing a payment smart contract, the income deposited into the digital account 11 of the IoT device 10 can be distributed to one or more owners. More specifically, the payment smart contract can identify one or more owners of the IoT device 10 when the IoT device 10 is owned by one or more owners and tokens have been deposited into the digital account 11 of the IoT device 10. The payment smart contract can also determine the amount to be allocated to the identified one or more owners by referring to a table that associates identifiers with one or more owners of the IoT device 10 and allocation information indicating the allocation to those one or more owners. The payment smart contract can then distribute the tokens deposited into the digital account 11 of the IoT device 10 to the digital accounts of one or more specified owners according to the determined distribution amount.

[0054] In this embodiment, when the processing unit 102 calculates the usage fee, it generates payment transaction data including the digital account of the payment recipient, the digital account of the payment source, and a token indicating the fee.

[0055] Furthermore, the processing unit 102 may generate log data such as the usage history of the IoT device 10.

[0056] Furthermore, in the distributed network 50, the processing unit 102 may perform deposits or withdrawals to or from the digital account 11 by deducting or adding the relevant tokens from the digital account 11.

[0057] The distributed ledger storage unit 103 retrieves the latest distributed ledger from, for example, the BC node 51 and stores it in its storage device. The distributed ledger storage unit 103 also stores a distributed ledger with the same contents as the distributed ledger of, for example, the BC node 51. This distributed ledger contains records of deposits and withdrawals from the digital account 11.

[0058] In this way, the IoT device 10 can have a digital account 11, and the IoT device 10 can manage its own income and other transactions using its own digital account 11. In other words, the IoT device 10 can earn digital currency and distribute the earned currency to its owner without needing an administrator. This allows for a shift from the conventional model of purchasing and using the IoT device 10 to a new model where the IoT device 10 is shared and used by multiple users, with a fee paid each time it is used.

[0059] [1.2 User 20] User 20 is, for example, a user who has a digital account 21 and uses IoT device 10. User 20 uses terminal 22 to pay usage fees for IoT device 10 from digital account 21 to the digital account 11 of IoT device 10. User 20 may be both a user and the owner of IoT device 10, or an owner who does not use IoT device 10. If user 20 is the owner of IoT device 10, the digital account 21 will receive a distribution of income such as usage fees earned from the use of IoT device 10.

[0060] Here, terminal 22 is a terminal having a display unit and an input unit, such as a smartphone, tablet, or personal computer.

[0061] Figure 3 shows an example of the configuration of terminal 22 according to this embodiment.

[0062] Terminal 22 is connected to the distributed network 50 and can communicate with multiple BC nodes 51, and can also communicate with IoT devices 10 and terminals of manufacturer 30 that are connected to the distributed network 50. Terminal 22 has a digital account 21 of user 20 on the distributed network 50. Terminal 22 comprises a processor, a memory storing a program that causes the processor to execute predetermined processing, and a communication interface, etc. In other words, terminal 22 is realized by the processor executing a predetermined program using the memory.

[0063] As shown in Figure 3, terminal 22 comprises a communication unit 221, a processing unit 222, and a distributed ledger storage unit 223. Each component will be described below.

[0064] The communication unit 221 communicates with multiple BC nodes 51 and with IoT devices 10 and manufacturer terminals 30 connected to the distributed network 50. In this embodiment, the communication unit 221 transmits and retrieves transaction data. The communication unit 101 may also retrieve usage fees.

[0065] The processing unit 222 generates transaction data and executes a consensus algorithm for the transaction data with multiple BC nodes 51, etc. The processing unit 222 also writes the transaction data, after it has gone through the consensus algorithm, to the distributed ledger. The processing unit 222 can execute smart contracts that are written to the distributed ledger and running in memory.

[0066] In this embodiment, when the processing unit 222 obtains the usage fee for the IoT device 10, it generates payment transaction data that includes the digital account 11 of the IoT device 10 to which the usage fee is to be paid, the digital account 21 of the user 20 making the payment, and a token indicating the usage fee. If the processing unit 222 only knows the identifier of the IoT device 10 to which the payment is to be made, it may include the identifier of the IoT device 10 to which the payment is to be made in the payment transaction data instead of the digital account 11. Alternatively, the processing unit 222 may include the digital account 11 in the payment transaction data by referring to the correspondence between identifiers included in a table recorded in the distributed network 50 and the addresses of digital accounts and obtaining the address indicating the digital account.

[0067] If user 20 is the owner, the processing unit 222 signs the transaction data obtained through user 20's actions. If user 20 is a user of IoT device 10, the processing unit 222 can also determine the type of token to be paid as a usage fee.

[0068] Furthermore, if the smart contract is not to be run on the decentralized network 50, the processing unit 222 will subtract or add the corresponding tokens from the digital account 21.

[0069] The distributed ledger storage unit 223 retrieves the latest distributed ledger from, for example, BC node 51 and stores it in the storage device. The distributed ledger storage unit 223 stores a distributed ledger with the same contents as the distributed ledger of BC node 51. This distributed ledger contains the deposits and withdrawals of digital accounts 21.

[0070] [1.3 Manufacturer 30] Manufacturer 30 is, for example, a company that has a digital account 31 and manufactured IoT devices 10.

[0071] The terminal is, for example, a personal computer and is owned by the manufacturer 30 that manufactured the IoT device 10. The manufacturer 30 uses the terminal to manage the digital account 31. The manufacturer 30 is also a platform provider that uses the terminal to assign identifiers to the manufactured IoT devices 10 and to assign the digital account 11 of the IoT device 10 to those identifiers. The identifier includes at least one of the IoT device 10's model number, part number, serial number, and license plate, and can uniquely identify the IoT device 10.

[0072] Note that the configuration of terminal 30 is the same as that of terminal 22, so the explanation will be omitted.

[0073] [1.4 BC Node 51] Multiple BC nodes 51 constitute a distributed network 50, as shown in Figure 1. Each of the multiple BC nodes 51 is an authentication server with a distributed ledger. Since the multiple BC nodes 51 have a similar configuration, the following explanation will use one BC node 51 as an example.

[0074] Figure 4 shows an example of the configuration of the BC node 51 according to this embodiment.

[0075] BC node 51 is connected to the distributed network 50 and can communicate with other BC nodes 51, as well as with IoT devices 10, user terminals 22, and manufacturer terminals 30 that are also connected to the distributed network 50.

[0076] The BC node 51 comprises a processor, memory containing a program that causes the processor to perform predetermined processing, and a communication interface, etc. In other words, the BC node 51 is realized when the processor uses memory to execute a predetermined program.

[0077] In this embodiment, the BC node 51 includes a communication unit 510, a processing unit 511, and a distributed ledger storage unit 512, as shown in Figure 4. Each component will be described below.

[0078] The communication unit 510 communicates with multiple BC nodes 51, and also communicates with IoT devices 10, user terminals 22, and manufacturer terminals 30 connected to the distributed network 50. In this embodiment, the communication unit 510 transmits and retrieves transaction data.

[0079] The processing unit 511 generates transaction data and executes a consensus algorithm for the transaction data with multiple BC nodes 51, etc. The processing unit 511 also writes the transaction data, after it has gone through the consensus algorithm, to the distributed ledger. Furthermore, the processing unit 511 can execute smart contracts that are written to the distributed ledger and running in memory.

[0080] The distributed ledger storage unit 512 stores a distributed ledger with the same contents as the distributed ledger of the other BC node 51, for example, by obtaining the latest block from another BC node 51 and storing it in the storage device. This distributed ledger contains the deposits and withdrawals of the digital account 21.

[0081] [2. Operation of System 100] Next, we will describe an example of the operation of system 100 configured as described above.

[0082] [2.1 Control Methods for IoT Devices 10] The above-described system 100 uses the example of a distributed network 50 such as a blockchain, but it is not limited to this. The distributed network 50 is not limited to a blockchain; it may be a network that implements a distributed ledger, or a regular network equipped with a database. Below, we will describe the control method of the IoT device 10 as an example of the operation of system 100.

[0083] Figure 5 is a flowchart illustrating an example of a control method for an IoT device 10 by a system 100 according to this embodiment. Assume that the IoT device 10 and the user 20 using the IoT device 10 each have digital accounts 11 and 21, respectively. In this case, first, assume that after the user 20 uses the IoT device 10, the IoT device 10 notifies the user of the usage fee. The user 20 uses their terminal 22 to generate payment transaction data for paying the notified usage fee and sends it to the system 100. This payment transaction data includes the address of the user 20's digital account 21 indicating the payer, the address of the IoT device 10's digital account 11 indicating the recipient, and a token indicating the usage fee for the IoT device 10. The payment transaction data is an example of the first payment transaction data. Furthermore, the system 100 here is a computer that manages the digital account 11 of the IoT device 10 and the user 20's digital account 21, which are established on a distributed network 50. This computer may be the terminals 22 of the IoT device 10 and user 20.

[0084] The system 100 then obtains payment transaction data (S1). More specifically, the system 100 obtains payment transaction data for a user of the IoT device 10 to pay the usage fee for the IoT device 10 using a token.

[0085] Next, the system 100 identifies the digital account of the IoT device 10, which is associated with an identifier uniquely assigned to the hardware of the IoT device 10, from the payment transaction data obtained in step S1 (S2). More specifically, the system 100 identifies the digital account of the IoT device 10, which is associated with an identifier uniquely assigned to the hardware of the IoT device 10, from the address indicating the payee included in the payment transaction data obtained in step S1. The identifier includes at least one of the IoT device 10's model number, part number, serial number, and license plate number.

[0086] Next, system 100 pays the usage fee for IoT device 10 using tokens from user 20's digital account 21 to IoT device 10's digital account (S3). More specifically, system 100 deducts the tokens from user 20's digital account 21 and adds them to IoT device 10's digital account 11 based on the payment transaction data obtained in step S1. In this way, system 100 transfers the usage fee for IoT device 10 from user 20's digital account 21 to IoT device 10's digital account 11.

[0087] The following describes a specific example of how System 100 operates when the distributed network 50 is a blockchain network.

[0088] [2.2 Digital Account Opening Process] Figure 6 is a sequence diagram showing the digital account opening process according to this embodiment. The example shown in Figure 6 describes the process when a digital account 11 for an IoT device 10 is opened by the manufacturer 30. In Figure 6, multiple BC nodes 51 are represented as BC nodes 1 to 3, and it is explained that the IoT device 10 and the terminal of the manufacturer 30 are also participating as nodes in the distributed network 50, which is a blockchain.

[0089] First, let's assume that the IoT device 10 is manufactured by manufacturer 30 and that manufacturing is complete (S100). Here, the IoT device 10 is, for example, a home appliance such as a refrigerator or washing machine, and manufacturer 30 is, for example, a company that manufactures and sells home appliances. Also, manufacturer 30 may be a platform provider that builds and manages a distributed network 50.

[0090] Next, the manufacturer 30 uses a terminal to assign a device-specific identifier to the IoT device 10 whose manufacturing was completed in step S100 (S101). The manufacturer 30 assigns an identifier to the IoT device 10 that includes at least one of the model number, part number, serial number, and license plate number of the IoT device 10, and that can uniquely identify the hardware of the IoT device 10.

[0091] Next, the manufacturer 30 uses a terminal to determine the address of the digital account 11 for the device-specific identifier assigned in step S101 (S102). In this embodiment, the manufacturer 30 determines the blockchain address of the digital account 11 of the IoT device 10.

[0092] Next, the manufacturer 30 uses a terminal to generate account opening transaction data, which is transaction data for opening a digital account 11 for the IoT device 10 (S103). The account opening transaction data includes the identifier of the IoT device 10 and the blockchain address of the digital account 11 for the IoT device 10.

[0093] Next, the manufacturer 30 uses a terminal to transmit the account opening transaction data generated in step S103 to the IoT device 10 and BC nodes 1-3 (S104).

[0094] Next, when IoT device 10 and BC nodes 1-3 obtain account opening transaction data from manufacturer 30's terminal (S105), manufacturer 30's terminal, IoT device 10, and BC nodes 1-3 execute a consensus algorithm (S106).

[0095] In this way, the manufacturer's terminal 30, the IoT device 10, and BC nodes 1-3 execute a consensus algorithm to generate a block containing account opening transaction data and record it in the distributed ledger.

[0096] In this way, a block containing account opening transaction data is recorded in a distributed ledger on the distributed network 50, and a digital account 11 for the IoT device 10 is opened.

[0097] If the distributed network 50 is not a blockchain network, in step S103, the manufacturer 30 can use a terminal to generate information associating the identifier of the IoT device 10 with the address of the IoT device 10. Then, in step S104, the manufacturer 30 can have the terminal send the generated information to a database on the distributed network 50 and store the generated information in the database. This allows the IoT device 10 to have a digital account using an address accessible on the network.

[0098] In this way, system 100 can enable IoT devices 10 to have a digital account 11 using an address accessible on the distributed network 50. This allows IoT devices 10 to manage their own revenue, such as usage fees. Furthermore, because the digital account 11 of IoT devices 10 is managed on the blockchain, IoT devices 10 can manage their own revenue, such as usage fees, using a digital account 11 that is traceable and tamper-proof.

[0099] In the above explanation, it was assumed that manufacturer 30 used a terminal to assign an identifier to IoT device 10 and determine the address of IoT device 10's digital account 11, but this is not the only way. Any of BC nodes 1 to 3 may assign an identifier to IoT device 10 and determine the address of IoT device 10's digital account 11. This will be explained below using Figure 7.

[0100] Figure 7 is another sequence diagram showing the digital account opening process according to this embodiment.

[0101] First, let's assume that IoT device 10 was manufactured by manufacturer 30 and that manufacturing has been completed (S110).

[0102] Next, manufacturer 30 confirms the identifier of the IoT device 10 whose manufacturing was completed in step S101 and transmits it to BC node 1 using manufacturer 30's terminal (S111). More specifically, manufacturer 30 transmits the model number, part number, serial number, and identifiers that can uniquely identify the hardware of IoT device 10, such as a license plate number, to BC node 1 as the identifier of IoT device 10. Note that this information may be transmitted to other BC nodes 2 and 3, not just BC node 1.

[0103] Next, when BC node 1 obtains the identifier transmitted from the manufacturer's terminal 30 (S112), it assigns the identifier to the IoT device 10 whose manufacturing was completed in step S110 (S113).

[0104] Next, BC node 1 determines the address of the digital account 11 for the identifier assigned in step S113 (S114). In this embodiment, BC node 1 determines the blockchain address of the digital account 11 of the IoT device 10.

[0105] Next, BC node 1 generates account opening transaction data, which is transaction data for opening a digital account 11 for IoT device 10 (S115). As described above, the account opening transaction data includes the identifier of IoT device 10 and the blockchain address of the digital account 11 for IoT device 10.

[0106] Next, BC node 1 sends the account opening transaction data generated in step S115 to the terminal of maker 30 and to the other BC nodes 2 and 3 (S116).

[0107] Next, when the manufacturer's terminal 30 obtains account opening transaction data from BC node 1 (S117), it transmits the obtained account opening transaction data to the IoT device 10 (S118).

[0108] Next, IoT device 10 and BC nodes 2 and 3 acquire account opening transaction data (S119), and IoT device 10, manufacturer 30's terminal, and BC nodes 1 to 3 execute the consensus algorithm (S120).

[0109] In this way, a block containing account opening transaction data is recorded in a distributed ledger on the distributed network 50, and a digital account 11 for the IoT device 10 is opened.

[0110] [2.3 Processing of Payment of Usage Fees] Figure 8 is a sequence diagram showing the payment processing for usage fees according to this embodiment. The example shown in Figure 8 describes the process when the usage fee for the IoT device 10 used by user 20 is deposited into the digital account 11 of the IoT device 10. In Figure 8, as in Figures 6 and 7, multiple BC nodes 51 are represented as BC nodes 1 to 3, and it is explained that the IoT device 10 and the user 20's terminal 22 are also participating as nodes in the distributed network 50, which is a blockchain.

[0111] First, let's assume that user 20 uses IoT device 10 (S200). Here, IoT device 10 is, for example, a home appliance such as a refrigerator or washing machine, and user 20 may be a user of a shared room who uses the IoT device 10, or a user who uses the IoT device 10 on a pay-per-use basis.

[0112] Next, the IoT device 10 calculates the usage fee for user 20 (S201). The IoT device 10 can calculate the usage fee according to user 20's usage pattern by referring to a price list it holds internally or a price list via the network.

[0113] Next, the IoT device 10 notifies the user 20's terminal 22 of the usage fee calculated in step S201 (S202).

[0114] Next, user 20's terminal 22 obtains the usage fee notified by IoT device 10 (S203) and generates usage fee payment transaction data, which is transaction data for paying the usage fee of IoT device 10 (S204). The usage fee payment transaction data is an example of the first payment transaction data. The usage fee payment transaction data includes the address of user 20's digital account 21, which indicates the source of payment, the address of IoT device 10's digital account 11, which indicates the recipient of payment, and a token (token amount) indicating the usage fee of IoT device 10.

[0115] Next, user 20's terminal 22 sends the payment transaction data for the usage fee generated in step S204 to IoT device 10 and BC nodes 1-3 (S205).

[0116] Next, IoT device 10 and BC nodes 1-3 obtain payment transaction data for usage fees from user 20's terminal 22 (S206), and then IoT device 10, user 20's terminal 22, and BC nodes 1-3 execute a consensus algorithm (S207).

[0117] In this way, the IoT device 10, the user 20's terminal 22, and BC nodes 1-3 execute a consensus algorithm to generate a block containing payment transaction data for usage fees and record it in a distributed ledger.

[0118] Next, the IoT device 10, the user 20's terminal 22, and BC nodes 1-3 execute the payment smart contract recorded in the distributed ledger (S208). More specifically, in step S207, the payment transaction data generated in step S204 is recorded in the distributed ledger, i.e., stored in the blockchain, thereby enabling the operation of the smart contract managed by the blockchain. The payment smart contract executed in step S208 is programmed to execute the payment (deposit) of usage fees from the digital account of the payer to the digital account of the payee. This payment smart contract is made executable in working memory by being recorded in the distributed ledger. By executing the payment smart contract, tokens representing usage fees can be transferred from the user 20's digital account 21 to the IoT device 10's digital account 11. In this way, the system 100 can automatically transfer income in tokens to the IoT device 10's digital account 11 by utilizing the payment smart contract.

[0119] In the example shown in Figure 8, it is explained that user 20's terminal 22 generated the payment transaction data for the usage fee, but this is not limited to this. IoT device 10 may also generate the payment transaction data for the usage fee calculated in step S201. More specifically, without performing the notification process in step S202 and the acquisition process in step S203, IoT device 10 can generate the payment transaction data for the usage fee calculated in S201 in steps S204 to S205 and send it to BC nodes 1 to 3 and user 20's terminal 22.

[0120] Figure 9 is a sequence diagram showing an example of the detailed processing of step S208 shown in Figure 8.

[0121] In step S208, the payment smart contract transfers the usage fee in tokens from the user 20's digital account 21 to the IoT device 10's digital account 11 (S2081). In this embodiment, the payment smart contract deposits the usage fee in tokens into the IoT device 10's digital account 11 according to the blockchain addresses indicating the payer and payee and the amount of tokens indicating the usage fee, which are included in the payment transaction data generated in step S204.

[0122] Next, the payment smart contract identifies the owner of IoT device 10 (S2082) and calculates the allocation amount (S2083). For example, the payment smart contract may identify the owner of IoT device 10 and the allocation amount by referring to a table as shown in Figure 10, using the address of the IoT device 10's digital account included in the payment transaction data generated in step S204.

[0123] Figure 10 is an example of a table for managing the IoT device 10, its owners, and allocation according to this embodiment. The table in Figure 10 includes the correspondence between the identifier of the IoT device 10 and the address of its digital account, and if there are two owners for the IoT device 10, it includes the identifier of each owner's terminal and the address of their digital account. The table in Figure 10 also includes the allocation ratio between the two owners of the IoT device 10.

[0124] Using the example shown in Figure 10, the payment smart contract identifies the digital account addresses of the two owners of IoT device 10 and, given the 50% allocation rate, calculates the allocation amount to be half of the usage fee received in S2081.

[0125] Next, the payment smart contract distributes the usage fee from the IoT device 10's digital account 11 to the owner's digital account (S2084). In the example shown in Figure 10, the payment smart contract distributes half of the usage fee from the IoT device 10's digital account 11 to each of the two owners' digital accounts and deposits the funds.

[0126] In this way, the payment smart contract can distribute the tokens deposited into the digital account 11 of the IoT device 10 to the digital accounts of one or more identified owners. This allows for a shift from the conventional model of buying and using the IoT device 10 to a new model in which the IoT device 10 is owned by multiple interchangeable users, and the profits earned by the IoT device 10 are distributed among the multiple users who own the IoT device 10.

[0127] In the example shown in Figure 9, a single payment smart contract is used to transfer tokens for the usage fee to the digital account 11 of the IoT device 10 and to distribute the allocated amount to the owner's digital account. However, this is not the only way. The smart contract that transfers tokens for the usage fee to the digital account 11 of the IoT device 10 and the smart contract that distributes the allocated amount to the owner's digital account may be separate smart contracts. This will be explained using Figure 11.

[0128] Figure 11 is a sequence diagram showing another example of the processing from step S208 onwards, as shown in Figure 8. In Figure 11, it is assumed that the IoT device 10 and the owner's terminal are also participating as nodes in the distributed network 50, which is a blockchain. The configuration of the owner's terminal is the same as that of terminal 22.

[0129] In step S208, the payment smart contract transfers the usage fee in tokens from the user 20's digital account 21 to the IoT device 10's digital account 11 (S2081). In this embodiment, the payment smart contract deposits the usage fee in tokens into the IoT device 10's digital account 11 according to the blockchain addresses indicating the payer and payee and the amount of tokens indicating the usage fee, which are included in the payment transaction data generated in step S204.

[0130] Next, the payment smart contract identifies the owner of IoT device 10 (S2082). For example, the payment smart contract identifies the owner of IoT device 10 by referring to a table as shown in Figure 10, using the address of the IoT device 10's digital account included in the payment transaction data generated in step S204.

[0131] Next, the IoT device 10 calculates the allocation amount of the usage fees deposited into the digital account 11 (S209). By referring to a table like the one shown in Figure 10, the IoT device 10 can calculate that half of the usage fees deposited into the digital account 11 is the allocation amount.

[0132] Next, the IoT device 10 generates allocation transaction data (S210), which is transaction data for distributing the allocation amount calculated in step S209 to the owner. The allocation transaction data includes the address of the IoT device 10's digital account 11, which indicates the allocation source (payer), the address of the owner's digital account, which indicates the allocation recipient (payee), and a token indicating the allocation amount.

[0133] Next, IoT device 10 sends the distribution transaction data generated in step S210 to the owner's terminal and BC nodes 1-3 (S211).

[0134] Next, the owner's terminal and BC nodes 1-3 obtain the allocation transaction data from IoT device 10 (S212), and then IoT device 10, the owner's terminal, and BC nodes 1-3 execute the consensus algorithm (S215).

[0135] In this way, the IoT device 10, the owner's terminal, and BC nodes 1-3 execute a consensus algorithm to generate blocks containing allocation transaction data and record them in a distributed ledger.

[0136] Next, the IoT device 10, the owner's terminal, and BC nodes 1-3 execute the distribution smart contract recorded in the distributed ledger (S216). More specifically, in step S216, the distribution transaction data generated in step S210 is recorded in the distributed ledger, i.e., stored in the blockchain, thereby enabling the operation of the smart contract managed by the blockchain. The distribution smart contract executed in step S216 is programmed to pay (deposit) the allocated amount of usage fees from the source digital account to the destination digital account. This distribution smart contract is made executable in working memory by being recorded in the distributed ledger. By operating the distribution smart contract, the tokens, which are the usage fees deposited into the IoT device 10's digital account 11, can be distributed to the digital accounts of one or more identified owners (S2161). In this way, the system 100 can automatically distribute the profits obtained by the IoT device 10 by utilizing the distribution smart contract. In other words, by using a distribution smart contract, system 100 can automatically distribute the income deposited into the digital account 11 of the IoT device 10 to the owner.

[0137] In the above explanation, it was stated that IoT device 10 calculates the allocation amount and generates allocation transaction data, but this is not the only way. IoT device 10 may request any of BC nodes 1 to 3 to calculate the allocation amount and generate allocation transaction data. Alternatively, the calculation request may be made by generating request transaction data for the calculation request, which includes the address of IoT device 10's digital account and the amount of tokens indicating the usage fee.

[0138] [2.4 Log Data Purchase Payment Processing] Figure 12 is a sequence diagram showing the log data purchase fee payment process according to this embodiment. The example shown in Figure 12 describes the process when the log data of IoT device 10 is purchased by a buyer and the log data purchase fee is paid into the digital account 11 of IoT device 10. In Figure 12, multiple BC nodes 51 are represented as BC node 1, and it is explained that IoT device 10, the owner's terminal, and the buyer's terminal are all participating as nodes in a distributed network 50 which is a blockchain. The owner's terminal and the buyer's terminal have the same configuration as terminal 22. Note that Figure 12 describes the log data purchase fee payment process when the log data of IoT device 10 is purchased by a buyer as the payment process for the log data of IoT device 10, but it is not limited to this. The payment process for the log data of IoT device 10 may also be a payment process for viewing the log data of IoT device 10, a payment process for usage fees, or a payment process for secondary use of the log data of IoT device 10.

[0139] First, assume that IoT device 10 periodically registers log data with the data management server. That is, IoT device 10 generates log data transaction data, which is transaction data containing log data (S301), and sends it to the data management server (S302). Next, the data management server retrieves the log data transaction data (S303) and stores the log data of IoT device 10 contained in the log data transaction data in a storage device for storing log data. The data management server is located outside the distributed network 50 and is accessible from IoT device 10 and the buyer's terminal via the network.

[0140] If there is a buyer who wants to purchase the log data of IoT device 10, the buyer will use a terminal to purchase the log data of IoT device 10 from the data management server (S304). The data management server will then sell the log data of IoT device 10 to the buyer (send the log data) and notify the buyer of the log data purchase price, thus conducting a log data transaction (S305).

[0141] Next, the buyer uses a terminal to generate payment transaction data for the purchase of log data (S306). The payment transaction data for the purchase is an example of the second payment transaction data, and is transaction data for a user who has purchased log data from IoT device 10 to pay the purchase price of the log data in tokens to the digital account of IoT device 10. The payment transaction data for the purchase includes the address of the buyer's digital account, which indicates the payer (buyer), the address of the digital account 11 of IoT device 10, which indicates the recipient of the payment, and the amount of tokens indicating the purchase price of the log data from IoT device 10.

[0142] Next, the buyer uses their terminal to send the payment transaction data for the purchase price generated in step S304 to the IoT device 10, the owner's terminal, and the BC node 1 (S307).

[0143] Next, IoT device 10, the owner's terminal, and BC node 1 obtain payment transaction data for the purchase price from the buyer's terminal (S308), and then IoT device 10, the owner's terminal, the buyer's terminal, and BC node 1 execute a consensus algorithm (S309).

[0144] In this way, the IoT device 10, the owner's terminal, the buyer's terminal, and BC node 1 execute a consensus algorithm to generate a block containing payment transaction data for the purchase price and record it in a distributed ledger.

[0145] Next, the IoT device 10, the owner's terminal, the buyer's terminal, and BC node 1 execute the payment smart contract recorded in the distributed ledger (S310). More specifically, in step S309, the payment transaction data generated in step S306 is recorded in the distributed ledger, i.e., stored in the blockchain, thereby enabling the operation of the smart contract managed by the blockchain. The payment smart contract executed in step S310 is programmed to execute the payment (deposit) of the usage fee from the digital account of the payer to the digital account of the payee. This payment smart contract is made executable in working memory by being recorded in the distributed ledger. By executing this payment smart contract, the digital account 11 of the IoT device 10 is identified from the payment transaction data, the tokens representing the purchase price are deducted from the buyer's digital account, and added to the digital account 11 of the IoT device 10. In this way, by executing the payment smart contract, the purchase price of the log data can be transferred in tokens to the digital account of the IoT device 10. Therefore, the IoT device 10 itself can manage its own revenue, including the cost of purchasing log data.

[0146] Furthermore, the payment smart contract executed in step S310 may not only transfer the purchase price of the log data to the digital account of the IoT device 10, but may also allocate the allocated amount to the owner.

[0147] Figure 13 is a sequence diagram showing another example of the detailed processing of step S310 shown in Figure 12.

[0148] In step S310, the payment smart contract transfers the purchase price of the log data in tokens from the buyer's digital account to the IoT device 10's digital account 11 (S3101). In this embodiment, the payment smart contract deposits the purchase price in tokens into the IoT device 10's digital account 11 according to the payer, payee, and purchase price of the log data included in the payment transaction data generated in step S306.

[0149] Next, the payment smart contract identifies the owner of the IoT device 10 (S3102) and calculates the allocation amount (3103). For example, the payment smart contract can calculate the owner of the IoT device 10 and the allocation amount by referring to a table like the one shown in Figure 10, using the address of the digital account 11 of the IoT device 10 included in the payment transaction data generated in step S306.

[0150] Next, the payment smart contract distributes the purchase price of the log data from the IoT device 10's digital account 11 to the owner's digital account (S3104). In the example shown in Figure 10, the payment smart contract distributes half of the purchase price of the log data from the IoT device 10's digital account 11 to each of the two owners' digital accounts and deposits the funds.

[0151] In this way, the payment smart contract can distribute the tokens deposited into the digital account 11 of the IoT device 10 to the digital accounts of one or more identified owners.

[0152] [2.5 Variations of Payment Processing] In the above explanation, it was assumed that the tokens deposited into the digital account 11 of the IoT device 10 and the tokens in the digital account of the person paying the usage fees and purchase fees are the same, but this is not the only explanation.

[0153] Figure 14 is a diagram illustrating that different types of IoT devices 10 according to this embodiment can be used to make payments using different tokens.

[0154] In the example shown in Figure 14, IoT device 10, which is a washing machine, and IoT device 10A, which is a refrigerator, belong to different distributed networks 50 and 50A. Furthermore, the example in Figure 14 shows that when user 20 uses IoT device 10 (the washing machine), payment to their digital account 11 must be made using washing machine tokens. Similarly, when user 20 uses IoT device 10A (the refrigerator), payment to their digital account 11 must be made using refrigerator tokens. Washing machine tokens and refrigerator tokens are different tokens.

[0155] Figure 15 is a sequence diagram showing a modified example of the usage fee payment process according to this embodiment. The example shown in Figure 15 describes the process when the usage fee for IoT device 10A, which is a refrigerator used by user 20, is deposited into the digital account 11 of IoT device 10A in refrigerator tokens. In Figure 15, multiple BC nodes 51 are represented as a first group of BC nodes that can be treated as tokens that can only be deposited into the digital account as refrigerator tokens, and it is explained that the IoT device 10A, which is a refrigerator, and user 20's terminal 22 are also participating as nodes in the distributed network 50, which is a blockchain. Furthermore, the tokens in user 20's digital account 21 are described as base tokens and are different from refrigerator tokens.

[0156] First, let's assume that user 20 uses IoT device 10A, which is a refrigerator (S400).

[0157] The IoT device 10A, which is a refrigerator, then calculates the usage fee for user 20 using the refrigerator token (S401). The IoT device 10A refers to a price list it holds internally or a price list via the network and calculates the usage fee according to user 20's usage.

[0158] Next, the IoT device 10A notifies the user 20's terminal 22 of the usage fee calculated in step S401 (S402). In the example shown in Figure 15, the IoT device 10A notifies the user 20's terminal 22 of the usage fee calculated in step S401 and token information indicating that the token used to pay the usage fee is a refrigerator token.

[0159] Next, user 20's terminal 22 obtains information about the usage fee notified by IoT device 10A (S403) and determines the payment token, which is the token used to pay the usage fee for IoT device 10A (S404). In the example shown in Figure 15, terminal 22 determines that the payment token is a refrigerator token.

[0160] Next, user 20's terminal 22 converts the payment tokens in user 20's digital account 21 into refrigerator tokens (S405). Specifically, user 20's terminal 22 generates exchange transaction data requesting an intermediary server (not shown) to exchange the payment tokens in user 20's digital account 21, and sends it to the intermediary server. Here, the exchange transaction data includes the amount of base tokens equivalent to the usage fee and information requesting the exchange of base tokens for refrigerator tokens. When the intermediary server receives the exchange transaction data, it generates post-exchange transaction data including the amount of refrigerator tokens obtained by exchanging the base tokens equivalent to the usage fee, and sends it to user 20's terminal 22. In this way, the exchange, i.e., the conversion of base tokens to refrigerator tokens, can be performed. The intermediary server may belong to the distributed network 50A to which the IoT device 10A, which is a refrigerator, belongs, or it may belong to a different distributed network 50 from distributed network 50A.

[0161] Next, user 20's terminal 22 generates payment transaction data for usage fees, which is transaction data for paying the usage fee for IoT device 10A (S406). The payment transaction data for usage fees is an example of the first payment transaction data. The payment transaction data for usage fees includes the address of user 20's digital account 21, which indicates the source of payment, the address of IoT device 10A's digital account 11, which indicates the recipient of payment, and a refrigerator token, which indicates the usage fee for IoT device 10A.

[0162] Next, user 20's terminal 22 transmits the payment transaction data for the usage fee generated in step 406 to the IoT device 10A and the first BC node group (S407).

[0163] Next, when IoT device 10A and the first BC node group obtain payment transaction data for usage fees from user 20's terminal 22 (S408), IoT device 10A, user 20's terminal 22, and the first BC node group execute a consensus algorithm (S409).

[0164] In this way, the IoT device 10A, the user 20's terminal 22, and the first BC node group execute a consensus algorithm to generate a block containing payment transaction data for usage fees and record it in the distributed ledger.

[0165] Next, the IoT device 10A, the user 20's terminal 22, and the first BC node group execute the payment smart contract recorded in the distributed ledger (S410). More specifically, the payment transaction data generated in step S406 is recorded in the distributed ledger, i.e., stored in the blockchain, thereby activating the smart contract managed by the blockchain. Then, by activating the payment smart contract, refrigerator tokens representing the usage fee are transferred from the user 20's digital account 21 to the IoT device 10A's digital account (S4101). In this way, the system 100 can automatically transfer income to the IoT device 10A's digital account 11 by utilizing the payment smart contract.

[0166] In the example shown in Figure 15, it is explained that user 20's terminal 22 generates the payment transaction data for the usage fee, but this is not the only option. IoT device 10A may generate the payment transaction data for the usage fee calculated in step S406. More specifically, instead of performing the processes in steps S402 to S407 described above, IoT device 10A may generate the payment transaction data for the usage fee calculated in S401 in steps S402 to S407 and send it to the first BC node group and user 20's terminal 22.

[0167] Furthermore, while step S405 described above as using an intermediary server to exchange base tokens for refrigerator tokens, the explanation is not limited to this. Refrigerator tokens and washing machine tokens may also be implemented using colored coins. In this case, for example, IoT device 10, which is a washing machine, and IoT device 10A, which is a refrigerator, may belong to the same distributed network 50. Specifically, in step S405, user 20's terminal 22 generates exchange transaction data requesting the exchange of tokens equivalent to the payment tokens in user 20's digital account 21, and sends it to the first BC node group or IoT device 10A. Here, the exchange transaction data includes the amount of base tokens equivalent to the usage fee and the address of an exchange smart contract that can exchange the amount of base tokens for refrigerator tokens. The payment smart contract is programmed to allow the usage fee to be paid after the amount of base tokens equivalent to the usage fee has been exchanged for refrigerator tokens. When the first BC node group obtains the exchange transaction data, it executes the exchange smart contract to generate post-exchange transaction data that includes the amount of refrigerator tokens exchanged for the amount of base tokens equivalent to the usage fee, and sends it to the user 20's terminal 22. In this way, the exchange, i.e., the conversion of base tokens to refrigerator tokens, can be achieved.

[0168] Figure 16 is a sequence diagram showing a modified example of the payment processing for usage fees according to this embodiment. In the example shown in Figure 16, the processing is shown when the usage fee for the IoT device 10, which is a washing machine used by user 20, is deposited into the digital account 11 of the IoT device 10 in washing machine tokens. In Figure 16, as in Figure 15, multiple BC nodes 51 are represented as a second group of BC nodes that can be treated as tokens that can only be deposited into the digital account as washing machine tokens, and it is explained that the IoT device 10, which is a washing machine, and the terminal 22 of user 20 are also participating as nodes in the distributed network 50, which is a blockchain. Furthermore, the tokens in user 20's digital account 21 are base tokens and are different from washing machine tokens.

[0169] Steps S400A to S410A and S4104A are the same as steps S400 to S410 and S4104 explained in Figure 15, so their explanation is omitted.

[0170] As shown in Figure 14, it was explained that if user 20 uses IoT device 10, which is a washing machine, the usage fee must be paid with a washing machine token, and if user 20 uses IoT device 10A, which is a refrigerator, the usage fee must be paid with a refrigerator token. However, this is not limited to this. Even if each appliance, such as a refrigerator or a washing machine, belongs to a different distributed network, payment may be made with the same base token. Alternatively, each appliance, such as a refrigerator or a washing machine, may belong to a different distributed network, and payment may be required using a different token for each type. Furthermore, the token in the digital account from which payment is made may be a token corresponding to one of the appliances. In such cases, the usage fee may be paid by converting the token corresponding to one of the appliances using a table showing the conversion rate of tokens for each type of appliance relative to the base token.

[0171] [2.6 Processing of maintenance fee payments] Next, we will explain the expense processing when the maintenance costs of IoT device 10 are paid from the IoT device 10's digital account 11. The maintenance costs of IoT device 10 include electricity costs corresponding to the power consumed to operate IoT device 10, maintenance costs for IoT device 10, consumable parts costs for IoT device 10, and travel expenses for the user performing maintenance on IoT device 10.

[0172] Figure 17 shows another example of the overall configuration of system 100A according to this embodiment. In the following description, as shown in Figure 17, the main characters are, for example, IoT device 10, user 20, maintenance company 40 that performs maintenance on IoT device 10, and power company 45 that supplies power to IoT device 10. The maintenance company 40 is described as having a digital account 41 on the distributed network 50, and the power company 45 is described as having a digital account 46 on the distributed network 50. Elements similar to those in Figure 1 are denoted by the same reference numerals, and detailed explanations are omitted.

[0173] Figure 18 is a sequence diagram showing an example of the payment processing for maintenance costs according to this embodiment. The example shown in Figure 18 describes the process when maintenance costs for IoT device 10, such as electricity bills, are paid from the digital account 11 of IoT device 10. In Figure 18, multiple BC nodes 51 are represented as BC node 1, BC node 2, and it is explained that IoT device 10, the owner's terminal, and the power company's terminal 45 are also participating as nodes in the distributed network 50, which is a blockchain. The configuration of the owner's terminal and the power company's terminal 45 is the same as the configuration of terminal 22.

[0174] First, let's assume that IoT device 10 calculates maintenance costs such as electricity charges (S500). IoT device 10 calculates maintenance costs by referring to an electricity rate table obtained from the power company 45 via the network. Alternatively, IoT device 10 may obtain maintenance costs such as electricity charges from the power company 45 via the network.

[0175] Next, the IoT device 10 generates payment transaction data to pay for the maintenance costs of the IoT device 10, such as electricity bills (S501). This payment transaction data is an example of a third payment transaction data for paying the maintenance costs of the IoT device 10 with tokens. This payment transaction data includes the address of the IoT device 10's digital account 11, which indicates the source of payment, the address of the power company 45's digital account 46, which indicates the recipient of payment, and the amount of tokens representing the maintenance costs of the IoT device 10.

[0176] Next, the IoT device 10 sends the maintenance fee payment transaction data generated in step S501 to the owner's terminal (S503).

[0177] Next, the owner's terminal obtains the payment transaction data for maintenance fees (S504) and signs the payment transaction data (S505).

[0178] Next, the owner's terminal transmits the payment transaction data signed in step S505 to the IoT device 10, the power company's terminal 45, and BC nodes 1 and 2 (S506).

[0179] Next, when the IoT device 10, the power company's terminal 45, and BC nodes 1 and 2 obtain the payment transaction data from the owner's terminal (S507), the IoT device 10, the owner's terminal, the power company's terminal 45, and BC nodes 1 and 2 execute the consensus algorithm (S508).

[0180] In this way, the IoT device 10, the owner's terminal, the power company's terminal 45, and BC nodes 1 and 2 execute a consensus algorithm to generate a block containing maintenance fee payment transaction data and record it in a distributed ledger.

[0181] Next, the IoT device 10, the owner's terminal, the power company 45's terminal, and BC nodes 1 and 2 execute a payment smart contract recorded in the distributed ledger (S509). More specifically, in step S509, the payment transaction data is recorded in the distributed ledger, i.e., stored on the blockchain, thereby enabling the operation of the payment smart contract managed by the blockchain. By operating the payment smart contract, tokens representing maintenance fees can be transferred from the IoT device 10's digital account 11 to the power company 45's digital account 46 (S5091). More specifically, by operating the payment smart contract, the digital account 46 to which the maintenance fees are to be paid is identified from the payment transaction data, and based on the payment transaction data, tokens are deducted from the IoT device 10's digital account 11 and added to the recipient digital account 46. This allows the maintenance fees to be automatically transferred from the IoT device 10's digital account 11 to the power company 45's digital account 46. Thus, the IoT device 10 can manage its own expenses and income.

[0182] In the example shown in Figure 18, it is explained that the IoT device 10 calculated the electricity cost as a maintenance cost, but this is not the only example. The terminal of the power company 45 may also calculate the electricity cost as a maintenance cost. This will be explained below using Figure 19.

[0183] Figure 19 is a sequence diagram showing another example of the payment processing for maintenance costs according to this embodiment.

[0184] First, the IoT device 10 calculates power information such as the amount of power consumed when the IoT device 10 is used and transmits it to the terminal of the power company 45 (S600).

[0185] Next, the terminal of the power company 45 obtains power information from the IoT device 10 (S601) and calculates the electricity cost of the IoT device 10 as a maintenance cost (S602).

[0186] Next, the power company's terminal 45 sends the electricity bill calculated in step S602 to the IoT device 10 (S603).

[0187] Next, when the IoT device 10 obtains an electricity bill from the power company 45's terminal (S604), it generates payment transaction data to pay the electricity bill as maintenance costs for the IoT device 10 (S605). This payment transaction data is an example of a third payment transaction data for paying the maintenance costs of the IoT device 10 with tokens.

[0188] The following steps S606 to S612 and S6121 are the same as steps S503 to S509 and S5091 described above, so their explanation will be omitted.

[0189] In this way, by paying the maintenance costs of the IoT device 10 from the IoT device 10's digital account 11, the IoT device 10 can manage its own expenses and income.

[0190] In the example shown in Figure 19, it is explained that the IoT device 10 generates payment transaction data for maintenance costs, which are electricity charges, but this is not the only example. The power company's terminal 45 may generate payment transaction data for maintenance costs, which are electricity charges, and send it to the owner's terminal.

[0191] Figure 20 is a sequence diagram showing yet another example of the payment processing for maintenance costs according to this embodiment. The example shown in Figure 20 describes the process when maintenance costs for the IoT device 10, such as repair costs, are paid from the digital account 11 of the IoT device 10. In Figure 20, multiple BC nodes 51 are represented as BC node 1, BC node 2, and the IoT device 10, the owner's terminal, and the maintenance company 40's terminal are also assumed to be participating as nodes in the distributed network 50, which is a blockchain. The owner's terminal and the maintenance company 40's terminal have the same configuration as terminal 22.

[0192] First, if IoT device 10 detects a malfunction (S700), it notifies the maintenance company 40's terminal that the malfunction has occurred.

[0193] Next, when the terminal of the maintenance company 40 receives a notification from the IoT device 10 that the IoT device 10 has malfunctioned (S701), it repairs the IoT device 10 by dispatching a repair person (S702).

[0194] When the IoT device 10 is repaired in step S702, the terminal of the maintenance company 40 calculates the repair cost of the IoT device 10 as a maintenance cost and sends an invoice for the calculated repair cost to the IoT device 10 (S703).

[0195] Next, when IoT device 10 receives a repair invoice from the maintenance company 40's terminal (S704), it generates payment transaction data to pay the repair cost as maintenance cost for IoT device 10 (S705). This payment transaction data is an example of a third payment transaction data for paying IoT device 10's maintenance cost with tokens. This payment transaction data includes the address of IoT device 10's digital account 11, which indicates the payer, the address of maintenance company 40's digital account 41, which indicates the payee, and tokens representing the maintenance cost for IoT device 10.

[0196] Next, the IoT device 10 sends the maintenance fee payment transaction data generated in step S705 to the owner's terminal (S706).

[0197] Steps S707 to S712 are the same as steps S504 to S509 described above, so their explanation will be omitted.

[0198] In step S712, the payment transaction data is recorded in a distributed ledger, i.e., stored on the blockchain, thereby activating a payment smart contract managed on the blockchain. By activating the payment smart contract, tokens representing repair costs, which are maintenance fees, are transferred from the digital account 11 of the IoT device 10 to the digital account 41 of the maintenance company 40 (S7121).

[0199] In this way, by paying the maintenance costs of the IoT device 10 from the IoT device 10's digital account 11, the IoT device 10 can manage its own expenses and income.

[0200] In the example shown in Figure 20, it is explained that IoT device 10 generates payment transaction data for maintenance costs, which are repair costs, but this is not the only example. The terminal of maintenance company 40 may generate payment transaction data for maintenance costs, which are repair costs, and send it to the owner's terminal.

[0201] In this way, by operating smart contracts managed on the blockchain, maintenance fees can be automatically transferred to the digital accounts of payment recipients, such as the digital account 11 of the IoT device 10, via the smart contract.

[0202] [2.7 Variations of the processing of disbursements for maintenance costs] The above describes how IoT device 10 handles maintenance costs, but this is not the only way. It is also conceivable that the manufacturer 30 of IoT device 10 acts as a platform provider, selling IoT device 10 including electricity costs and paying the maintenance costs.

[0203] Figure 21 is a sequence diagram showing a modified example of the payment processing for maintenance costs according to this embodiment.

[0204] The example shown in Figure 21 describes the process when maintenance costs for IoT devices 10, such as electricity bills, are withdrawn from the manufacturer's 30 digital account 31. In Figure 21, multiple BC nodes 51 are represented as BC node 1, and it is explained that the IoT device 10, the owner's terminal, the manufacturer's 30 terminal, and the power company's terminal are all participating as nodes in the distributed network 50, which is a blockchain.

[0205] First, the IoT device 10 calculates power information such as the amount of power used and transmits it to the manufacturer's terminal 30 (S800).

[0206] Next, the manufacturer's terminal 30 obtains power information from the IoT device 10 (S801) and calculates the electricity cost of the IoT device 10 as a maintenance cost (S802).

[0207] Next, the manufacturer's terminal 30 generates payment transaction data to pay for the electricity bill as maintenance costs for the IoT device 10 (S803). This payment transaction data is an example of a third payment transaction data for paying the maintenance costs of the IoT device 10 with tokens. This payment transaction data includes the address of the manufacturer's digital account 31, which indicates the source of payment, the address of the power company's digital account 46, which indicates the recipient of payment, and tokens representing the maintenance costs of the IoT device 10.

[0208] Next, the manufacturer's terminal 30 sends the maintenance fee payment transaction data generated in step S803 to the owner's terminal (S804).

[0209] Steps S805 to S810 are the same as steps S504 to S509 described above, so their explanation will be omitted.

[0210] In step S810, the payment transaction data is recorded in a distributed ledger, i.e., stored on the blockchain, thereby activating a payment smart contract managed on the blockchain. By activating the payment smart contract, tokens representing the electricity bill, which is the maintenance cost of the IoT device 10, are transferred from the manufacturer's 30 digital account 31 to the power company's 45 digital account 46 (S8101).

[0211] Figure 22 is a sequence diagram showing a modified example of the payment processing for maintenance costs according to this embodiment.

[0212] The example shown in Figure 22 describes the process in which only the fees incurred when manufacturer 30 pays the maintenance costs of IoT device 10 are withdrawn from IoT device 10's digital account 11. In Figure 22, as in Figure 21, multiple BC nodes 51 are represented as BC node 1, and it is explained that IoT device 10, the owner's terminal, manufacturer 30's terminal, and the power company's terminal are all participating as nodes in the distributed network 50, which is a blockchain.

[0213] First, let's assume that when Manufacturer 30's terminal pays electricity as maintenance costs in the process shown in Figure 21, it calculates the fee for paying the electricity (S900) and sends it to IoT device 10. Manufacturer 30's terminal can calculate the fee by referring to a table showing the fees for the electricity charges it possesses.

[0214] Next, when IoT device 10 receives a fee invoice from manufacturer 30's terminal (S902), it generates payment transaction data to pay the fee as maintenance cost for IoT device 10 (S903). This payment transaction data is an example of a third payment transaction data for paying IoT device 10's maintenance cost with tokens. This payment transaction data includes the address of IoT device 10's digital account 11, which indicates the payer, the address of manufacturer 30's digital account 31, which indicates the recipient, and tokens representing the fee.

[0215] Next, the IoT device 10 sends the payment transaction data for the maintenance fee generated in step S903 to the owner's terminal (S904).

[0216] Steps S905 to S910 are the same as steps S504 to S509 described above, so their explanation will be omitted.

[0217] In step S910, the payment transaction data is recorded in a distributed ledger, i.e., stored on the blockchain, thereby activating a payment smart contract managed on the blockchain. Activating the payment smart contract causes tokens representing the maintenance fee for the IoT device 10 to be transferred from the IoT device 10's digital account 11 to the manufacturer 30's digital account 31 (S9101).

[0218] [2.8 Effects of the Embodiment] According to this embodiment, the IoT device 10 can have a digital account 11 using a network-accessible address. This enables a control method for the IoT device 10 that allows the IoT device 10 to manage its own revenue, such as usage fees.

[0219] Furthermore, by giving IoT device 10 a digital account 11, usage fees for IoT device 10 can be transferred to IoT device 10's digital account 11, and maintenance costs for IoT device 10 can be paid from IoT device 10's digital account. In addition, purchase fees for IoT device 10's log data can also be transferred to IoT device 10's digital account 11. This allows IoT device 10 to manage its own income, such as usage fees. Therefore, it is possible to shift from the conventional model of purchasing and using IoT device 10 to a new model where IoT device 10 is shared and used by multiple users, with fees paid each time it is used.

[0220] Furthermore, IoT device 10 may distribute the income deposited into its digital account 11 to one or more owners. This allows for a shift from the conventional model of purchasing and using IoT devices to a new model in which IoT devices are owned by multiple interchangeable users, and the profits generated by the IoT devices are distributed among the multiple users who own them.

[0221] Alternatively, the digital account 11 of the IoT device 10 may be managed on the blockchain. This allows the IoT device 10 to manage its own revenue, such as usage fees, using a digital account 11 that is traceable and tamper-proof.

[0222] Furthermore, by using smart contracts, revenue such as usage fees and log data purchase fees can be automatically transferred to the IoT device 10's digital account 11, and profits earned from the IoT device can be automatically distributed to one or more owners of the IoT device.

[0223] [3 Other variations] Although this disclosure has been described based on the embodiments described above, it goes without saying that this disclosure is not limited to the embodiments described above. The following cases are also included in this disclosure.

[0224] (1) In the above embodiment, when IoT device 10 incurs maintenance costs, it withdraws the maintenance costs from its own digital account 11. However, there may be cases where there are not enough funds remaining in its own digital account 11 to pay the maintenance costs. In this case, IoT device 10 may have another IoT device 10 pay the maintenance costs on its behalf and repay it at a later date. In this way, if an IoT device does not have enough funds in its digital account to incur expenses such as maintenance costs, it can have another IoT device pay them on its behalf. This allows the IoT device to manage its own expenses and income without the need for a user. This will be explained below using Figure 23.

[0225] Figure 23 is a sequence diagram of the payment processing for maintenance costs related to other variations. The example shown in Figure 23 explains the process when, for example, the maintenance costs of IoT device 10, such as electricity bills, are covered by other IoT devices 10. In Figure 23, multiple BC nodes 51 are represented as BC node 1, and it is explained that IoT devices 10 such as washing machines, refrigerators, and microwave ovens, as well as the owner's terminal, are participating as nodes in the distributed network 50, which is a blockchain.

[0226] First, let's assume that the washing machine, which is IoT device 10, calculates its own maintenance costs, such as electricity bills (S550). In other words, IoT device 10 calculates its own maintenance costs.

[0227] Next, the washing machine checks whether the maintenance cost calculated in step S550 is greater than the balance in its digital account 11 (S551).

[0228] In step S551, if the maintenance cost calculated in step S550 is greater than the balance in its own digital account 11 (YES in S551), it sends a notification to the other IoT devices 10, namely the refrigerator and microwave oven, requesting them to cover the maintenance cost, i.e., a notification that it wants to borrow money (S552). Here, the washing machine, which is IoT device 10, may generate a fourth transaction data to request that someone cover the maintenance cost if the balance in its own digital account 11 is less than the calculated maintenance cost. In this case, the washing machine, which is IoT device 10, only needs to send the generated transaction data to one or more other IoT devices 10 that are different from IoT device 10.

[0229] Next, when the other IoT devices 10, namely the refrigerator and microwave oven, receive the notification (S553), they refer to their own digital accounts 11 to check if they can pay the maintenance costs for the washing machine (S554). The following explanation assumes that the refrigerator, another IoT device 10, will cover the maintenance costs.

[0230] In step S554, if the maintenance fee notified in step S552 can be paid (YES in S554), payment transaction data is generated to pay the maintenance fee on behalf of the user (S555). If payment cannot be made (NO in S554), the process is terminated. This payment transaction data is an example of a fourth payment transaction data for paying the maintenance fee on behalf of the user. This payment transaction data includes the address of the digital account 11 of another IoT device 10 indicating the source of the payment, the address of the digital account 46 of the power company 45 indicating the recipient of the payment, and a token indicating the maintenance fee of the IoT device 10.

[0231] Next, the other IoT device 10, the refrigerator, sends the maintenance cost payment transaction data generated in step S555 to the owner's terminal (S556).

[0232] Steps S557 to S563 are the same as steps S504 to S508 described above, so their explanation will be omitted.

[0233] Furthermore, in step S551, if the maintenance cost calculated in step S550 is less than or equal to the balance in the IoT device's digital account 11 (No in S551), then the process in step S501, as explained in Figure 18, should be performed. In other words, if the balance in the IoT device 10's digital account 11 is greater than the calculated maintenance cost, payment transaction data should be generated to transfer the maintenance cost from the IoT device 10's digital account to the recipient's digital account.

[0234] (2) If the digital account 11 of IoT device 10 does not have enough balance to pay the maintenance fee, IoT device 10 may have another IoT device 10 cover the maintenance fee, as explained in (1) above, but this is not the only option. IoT device 10 may also borrow tokens for the maintenance fee from another IoT device 10 to pay the maintenance fee and repay it at a later date.

[0235] More specifically, IoT device 10 identifies its own maintenance costs and assumes that the balance in IoT device 10's digital account 11 is less than the calculated maintenance costs. In this case, IoT device 10 may transmit credit information, including IoT device 10's log information or the balance information of IoT device 10's digital account 11, to one or more other IoT devices. IoT device 10 may then obtain loan tokens equivalent to the maintenance costs from one of the other IoT devices 10 that has decided to cover the maintenance costs. Here, the loan tokens include at least one of the following: loan amount, interest, or loan term. When BC node 51 etc. obtains payment transaction data generated by IoT device 10, it instructs the payment smart contract to identify the digital account to which the maintenance costs will be paid from the obtained payment transaction data. This allows BC node 51 etc. to instruct the payment smart contract to transfer loan tokens from IoT device 10's digital account to the recipient's digital account based on the payment transaction data and the loan tokens.

[0236] Subsequently, when the balance in its own digital account 11 exceeds the maintenance fee, IoT device 10 identifies the digital account of the first IoT device 10 from the loan token. Then, IoT device 10 can transfer tokens equivalent to the loan token from its own digital account 11 to the digital account of the first IoT device.

[0237] In this way, if the balance in the digital account 11 of the IoT device 10 is insufficient to cover expenses such as maintenance costs, it can borrow from other IoT devices 10 to make payments, and then repay the loan when its balance increases later. This allows the IoT device 10 to manage its own expenses and income without the need for a user.

[0238] (3) In the above description, IoT device 10 is explained as a home appliance such as a washing machine or a computer installed in a space such as a shared room, but it is not limited to these. IoT device 10 may also be a solar power generation facility that transmits electricity generated using solar panels or solar cells.

[0239] In this case, the IoT device 10 can generate income by selling the electricity it produces using solar panels. In other words, the user 20 can use electricity by utilizing the solar power generation equipment, which is the IoT device 10, and the usage fee for the IoT device 10 may be considered an electricity usage fee. This allows the payment processing described above to be applied.

[0240] Furthermore, the income from IoT device 10, the solar power generation equipment, can also include the money invested in installing the solar panels.

[0241] (4) As explained above, payment for usage fees etc. will be made with a token, but this token may also be an NFT (Non-Fungible Token).

[0242] (5) Furthermore, although the digital account of the IoT device 10 has been described as a digital account associated with a real IoT device 10, it is not limited to this. The digital account of the IoT device 10 may also be a digital account associated within the metaverse (virtual space), and the real IoT device 10, the virtual IoT device associated with it, and the digital account may be a set. This means that, for example, if a virtual washing machine associated with a real shared washing machine in a shared house is located in a shared house metaverse (virtual space) that mimics the shared house, the income and expenses related to that virtual washing machine can also be managed with a digital account shared with the real shared washing machine.

[0243] Examples of expenses related to virtual washing machines include metaverse server usage fees and costs for changing the appearance of the virtual washing machine. Examples of revenue related to virtual washing machines include advance payments for future reservations of real washing machines made through the virtual washing machine, and advertising revenue displayed on the virtual washing machine.

[0244] (6) The above describes a case in which tokens, which are usage fees deposited into the digital account 11 of the IoT device 10, are distributed to the digital accounts of one or more owners using a distribution smart contract or the like. However, the method is not limited to this. A distribution smart contract or the like may be used to distribute tokens, which are usage fees deposited into the digital account 11 of the IoT device 10, to (one or more) distributors (owner's agents) approved by the owner. Alternatively, for example, the owner or owner's agent may issue distribution rights NFTs and circulate them on the market, and distribution may be made to the person who holds those NFTs at that time.

[0245] (7) Specifically, each device in the above embodiment is a computer system consisting of a microprocessor, ROM, RAM, hard disk unit, display unit, keyboard, mouse, etc. A computer program is recorded in the RAM or hard disk unit. Each device achieves its function by operating the microprocessor in accordance with the computer program. Here, the computer program is composed of a combination of multiple instruction codes that indicate commands to the computer in order to achieve a predetermined function.

[0246] (8) In the above embodiments, each device may have some or all of its constituent components made up of a single system LSI (Large Scale Integration). The system LSI is a multi-functional LSI manufactured by integrating multiple components onto a single chip, and specifically, it is a computer system comprising a microprocessor, ROM, RAM, etc. A computer program is recorded in the RAM. The system LSI achieves its function by operating the microprocessor in accordance with the computer program.

[0247] Furthermore, each component of the above-mentioned device may be individually integrated into a single chip, or some or all of the components may be integrated into a single chip.

[0248] Furthermore, while we refer to it as a system LSI here, depending on the degree of integration, it may also be called an IC, LSI, super LSI, or ultra LSI. Also, the method of integrated circuit implementation is not limited to LSIs; it may be implemented using dedicated circuits or general-purpose processors. After LSI manufacturing, FPGAs (Field Programmable Gate Arrays) that can be programmed, or reconfigurable processors that allow for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used.

[0249] Furthermore, if advancements in semiconductor technology or related technologies lead to the emergence of integrated circuit technologies that replace LSIs, then naturally, these technologies can be used to integrate functional blocks. The application of biotechnology, for example, is a possible possibility.

[0250] (9) Some or all of the components constituting each of the above devices may consist of a removable IC card or a standalone module. The IC card or module is a computer system consisting of a microprocessor, ROM, RAM, etc. The IC card or module may include the above-mentioned multi-functional LSI. The microprocessor operates according to a computer program, thereby enabling the IC card or module to perform its function. The IC card or module may be tamper-resistant.

[0251] (10) The present disclosure may be the methods described above. Alternatively, it may be a computer program that implements these methods using a computer, or a digital signal consisting of the computer program.

[0252] Furthermore, the computer program or the digital signal may be recorded on a computer-readable recording medium, such as a flexible disk, hard disk, CD-ROM, MO, DVD, DVD-ROM, DVD-RAM, BD (Blu-ray® Disc), semiconductor memory, etc. Alternatively, the digital signal may be recorded on one of these recording media.

[0253] Furthermore, this disclosure may also describe transmitting the computer program or digital signal via telecommunications lines, wireless or wired communication lines, networks such as the Internet, data broadcasting, etc.

[0254] Furthermore, the present disclosure may also provide a computer system comprising a microprocessor and memory, wherein the memory stores the computer program, and the microprocessor operates in accordance with the computer program.

[0255] Furthermore, the program or digital signal may be implemented by another independent computer system by recording and transferring it on the recording medium, or by transferring the program or digital signal via the network or the like.

[0256] (11) The above embodiments and the above modified examples may be combined. [Industrial applicability]

[0257] This disclosure can be used for control methods, IoT devices, and programs to realize earning-based shared home appliances, etc., by giving home appliances or IoT devices installed in a space a digital account and enabling them to send and receive digital currency. [Explanation of symbols]

[0258] 10, 10A IoT equipment 11, 21, 31, 41, 46 Digital Accounts 20 users 22 terminals 30 Manufacturers 40 Maintenance Companies 45 Power companies 50, 50A distributed network 51 BCnode 100, 100A system 101, 221, 510 Communications Department 102, 222, 511 Processing Unit 103, 223, 512 Distributed ledger storage unit

Claims

1. A method for controlling IoT devices, Both the IoT device and the user utilizing the IoT device have a digital account. A user using the IoT device obtains first payment transaction data for paying the usage fee of the IoT device with a token. From the acquired first payment transaction data, the digital account of the IoT device, which is associated with an identifier uniquely assigned to the hardware of the IoT device, is identified. Based on the acquired first payment transaction data, the token is deducted from the user's digital account and added to the IoT device's digital account, thereby transferring the IoT device usage fee to the IoT device's digital account. The aforementioned IoT device is owned by one or more owners, When the token is deposited into the digital account of the IoT device, Furthermore, the one or more owners of the IoT device are identified, By referring to information that associates the identifier, one or more owners of the IoT device, and allocation information indicating the allocation to the one or more owners, the amount allocated to the identified one or more owners is determined. The tokens deposited into the digital account of the IoT device are distributed to the digital accounts of the one or more specified owners according to the determined distribution amount. Control method.

2. The first payment transaction data is, The system includes the address of the user's digital account indicating the payment source, the address of the IoT device's digital account indicating the payment recipient, and the token indicating the usage fee for the IoT device. The control method according to claim 1.

3. The aforementioned identifier is, The IoT device includes at least one of the following: model number, part number, serial number, and license plate number. The control method according to claim 1.

4. Furthermore, the user who purchased the log data of the IoT device obtains a second payment transaction data to pay the purchase price of the log data to the IoT device's digital account using a token. From the acquired second payment transaction data, the digital account of the IoT device, which is associated with an identifier uniquely assigned to the hardware of the IoT device, is identified. Based on the acquired second payment transaction data, the token is deducted from the user's digital account and added to the IoT device's digital account, thereby transferring the purchase fee for the log data to the IoT device's digital account. The control method according to claim 1.

5. Furthermore, a third payment transaction data is obtained for paying the maintenance costs of the IoT device with a token. From the acquired third payment transaction data, the digital account to which the maintenance fee is paid is identified, Based on the acquired third payment transaction data, the maintenance fee is transferred to the digital account of the payee by deducting the token from the digital account of the IoT device and adding it to the digital account of the payee. The control method according to claim 1.

6. The information relating the identifier, one or more owners of the IoT device, and allocation information indicating the distribution to the one or more owners is a table, and the amount of the allocation to the identified one or more owners is determined by referring to the table. The control method according to any one of claims 1 to 5.

7. The address of the aforementioned digital account is a blockchain address, The aforementioned digital account is managed on a blockchain. The control method according to any one of claims 1 to 5.

8. The control method described above is By storing the acquired first payment transaction data on the blockchain, the smart contract managed on the blockchain is activated. The smart contract is instructed to transfer the token from the user's digital account to the IoT device's digital account. The control method according to claim 7.

9. moreover, The smart contract distributes the tokens deposited into the IoT device's digital account to the digital accounts of one or more identified owners. The control method according to claim 8.

10. The control method described above is By storing the acquired third payment transaction data on the blockchain, the smart contract managed on the blockchain is activated. The smart contract transfers the maintenance fee from the IoT device's digital account to the payee's digital account. The control method according to claim 5.

11. Furthermore, a first terminal different from the aforementioned IoT device, Obtain the identifier uniquely assigned to the hardware of the IoT device, Determine the address of the digital account of the aforementioned IoT device, The information relating the identifier and the address is output to and stored in a database. The control method according to any one of claims 1 to 5.

12. The first terminal is a terminal owned by the manufacturer that produced the IoT device. The control method according to claim 11.

13. The maintenance costs of the aforementioned IoT devices are calculated, If the balance of the IoT device's digital account is less than the calculated maintenance fee, generate a fourth transaction data to request that the maintenance fee be paid by the IoT device, and transmit the generated fourth transaction data to one or more other IoT devices different from the IoT device. If the balance of the digital account of the first IoT device among the one or more other IoT devices is greater than the calculated maintenance fee, the third payment transaction data is obtained, and the maintenance fee is transferred from the digital account of the first IoT device to the digital account of the recipient of the maintenance fee. The control method according to claim 5.

14. The aforementioned maintenance costs are, This includes at least one of the following: electricity costs corresponding to the power consumed to operate the IoT device, maintenance costs for the IoT device, costs for consumable parts for the IoT device, and travel expenses for the user performing maintenance on the IoT device. The control method according to claim 13.

15. The maintenance costs of the aforementioned IoT devices are calculated, If the balance of the IoT device's digital account is less than the calculated maintenance cost, credit information including the IoT device's log information or the balance information of the IoT device's digital account is transmitted to one or more other IoT devices different from the IoT device. From the first IoT device, which has been decided to cover the maintenance costs among the one or more other IoT devices mentioned above, a loan token equivalent to the maintenance costs is obtained. Obtain the third payment transaction data, From the acquired third payment transaction data, the digital account to which the maintenance fee is paid is identified, Based on the acquired third payment transaction data and the loan token, the loan token is transferred from the IoT device's digital account to the recipient's digital account. The control method according to claim 5.

16. The aforementioned loan token is This includes at least one of the following pieces of information: loan amount, interest rate, or loan term. The control method according to claim 15.

17. If the balance of the digital account of the IoT device exceeds the maintenance fee, From the aforementioned loan token, the digital account of the first IoT device is identified. Transfer tokens equivalent to the loan tokens from the digital account of the IoT device to the digital account of the first IoT device. The control method according to claim 15.

18. The aforementioned IoT device is a solar power generation facility that transmits electricity generated using solar cells. The aforementioned user utilizes solar power generation equipment to utilize electricity, The usage fee for the aforementioned IoT device is the electricity usage fee. The control method according to claim 6.

19. Both the IoT device and the user utilizing the IoT device have a digital account. A communication unit that obtains first payment transaction data for a user using the IoT device to pay the usage fee for the IoT device using a token, An identification unit identifies the digital account of the IoT device, which is associated with an identifier uniquely assigned to the hardware of the IoT device, from the acquired first payment transaction data, The system includes a writing unit that, based on the acquired first payment transaction data, deducts the token from the user's digital account and adds it to the IoT device's digital account, thereby transferring the usage fee for the IoT device to the IoT device's digital account, The aforementioned IoT device is owned by one or more owners, When the token is deposited into the digital account of the IoT device, The specified unit further identifies the one or more owners of the IoT device, The identification unit refers to information that associates the identifier, one or more owners of the IoT device, and allocation information indicating the allocation to the one or more owners, and determines the amount to be allocated to the identified one or more owners. The writing unit distributes the tokens deposited into the IoT device's digital account to the digital accounts of the one or more specified owners according to the determined distribution amount. IoT equipment.

20. A program that causes a computer to execute a control method for IoT devices, Both the IoT device and the user utilizing the IoT device have a digital account. A user using the IoT device obtains first payment transaction data for paying the usage fee of the IoT device with a token. From the acquired first payment transaction data, the digital account of the IoT device, which is associated with an identifier uniquely assigned to the hardware of the IoT device, is identified. Based on the acquired first payment transaction data, the token is deducted from the user's digital account and added to the IoT device's digital account, thereby transferring the IoT device usage fee to the IoT device's digital account. The aforementioned IoT device is owned by one or more owners, When the token is deposited into the digital account of the IoT device, Furthermore, the one or more owners of the IoT device are identified, By referring to information that associates the identifier, one or more owners of the IoT device, and allocation information indicating the allocation to the one or more owners, the amount allocated to the identified one or more owners is determined. The tokens deposited into the digital account of the IoT device are to be distributed to the digital accounts of one or more specified owners according to the determined distribution amount. A program that is executed by a computer.

Images