Token issuance management system, information collection system, information provision system, electronic transaction execution system, non-fungible token issuance method, issuance-target asset-related information collection method, information provision method, and electronic commerce execution method

Abstract

The purpose of the present invention is to provide, for example, a token issuance system that is capable of providing assets existing in a real space as digital assets having high reliability, ease of handling, and transparency.　An electronic transaction network system S has a configuration that is capable of, while guaranteeing the existence of an asset having existence in a real space, converting the asset into a non-fungible token as an issuance-target asset and handling the asset as an equivalent asset on a network, the configuration being further capable of executing an electronic transaction of the issuance-target asset or providing information such as viewing of the issuance-target asset, by using a smart contract (transaction processing regulation information) in which predetermined processing and constraints are defined.

Description

Token issuance management system, information collection system, information provision system, electronic transaction execution system, non-fungible token issuance method, issuance target asset related information collection method, information provision method, and electronic commerce execution method

[0001] The present invention relates to a token issuance management system, an information collection system, an information provision system, an electronic transaction execution system, and the like.

[0002] In recent years, with the advancement of digital technology and the development of communication technology and networks, the circulation of digital content and crypto assets, which can be exchanged for legal tender and used to pay for goods and services to unspecified parties, has become common.

[0003] Furthermore, by utilizing blockchain technology as a mechanism for proving the uniqueness or ownership of these items and using non-fungible tokens (NFTs) to assign asset value, highly reliable distribution of digital content or crypto assets has been realized.

[0004] Meanwhile, in addition to the digital assets described above, network services have recently emerged that convert real assets that exist in the real world into NFTs, for example, as Real Word Assets (RWAs), and handle these NFT-converted real assets in the same way as digital content and crypto assets (for example, MOCA Inc., "Whisky NFT," [online], [searched April 23, 2024], Internet <https: / / whiskeynft.jp / >).

[0005] However, in the systems described in the above non-patent documents, the existence of physical assets is based on trust in the creator or manufacturer of the physical assets, and it is difficult to say that the existence and authenticity of the physical assets are reliably guaranteed when they are converted into NFTs or when they are circulated as NFTs.

[0006] The present invention has been made to solve the above-mentioned problems, and its purpose is to ensure the existence and authenticity of assets that exist in the real world when they are converted into NFTs or when those assets are circulated as NFTs, and as a result, to provide a token issuance system or the like that can provide those assets as digital assets that are highly reliable, easy to handle, and transparent.

[0007] The present invention has also been made to solve the above-mentioned problems, and its purpose is to provide an information collection system or the like that makes it unnecessary to register a large amount of information and constantly update the registered information when managing non-fungible tokens, and that can reduce processing speeds and approval delays that accompany the increase in the amount of data that must be stored due to distributed ledger technologies such as blockchain technology.

[0008] (1) In order to solve the above problem, a token issuance management system according to a first aspect of the present invention is a token issuance management system that issues non-fungible tokens to be used for electronic transactions on a network for assets held by a user, and includes: a receiving means that receives an instruction to issue the non-fungible token for a given asset, the instruction being transmitted from a terminal device of a user who wishes to issue the non-fungible token; an acquiring means that acquires, as issuance target asset related information, information on the issuance target asset for which the non-fungible token is to be issued, from the terminal device of the user who wishes to issue the non-fungible token or an information system operated by an administrator who manages the assets in real space; a token issuing means that issues a non-fungible token that embodies the issuance target asset based on the received issuance instruction and the acquired issuance target asset related information; and a token issuing system that issues the issued non-fungible token while ensuring tamper-resistance, which exhibits characteristics for preventing tampering by unauthorized persons. and provision means for providing information on ownership rights indicating that the registered non-fungible token is held by the desiring user to a terminal device of the desiring user as ownership rights information, wherein when the token issuing means acquires from the information system real-world management information indicating that the asset to be issued actually exists in real space and is managed so as to be tradable, the token issuing means issues the non-fungible token, which has a token ID for identifying the non-fungible token and token-related information on the non-fungible token, and which specifies at least one of processing when a transaction of the non-fungible token is executed and processing when provision of information related to the relevant asset to be issued is requested, and which is associated with transaction processing specification information stored in a given storage medium or given storage means.

[0009] (2) To solve the above problem, a non-fungible token issuance method according to a second aspect of the present invention is a method for issuing non-fungible tokens to be used for electronic transactions on a network for assets held by a user, the method comprising: receiving an instruction to issue a non-fungible token for a given asset, the instruction being transmitted from a terminal device of a user wishing to issue the non-fungible token; acquiring information on the target asset for issuance, for which the non-fungible token is to be issued, from the terminal device of the user wishing to issue the non-fungible token or from an information system operated by an administrator who manages the assets in real space, as target asset related information; issuing a non-fungible token that embodies the target asset for issuance based on the received issuance instruction and the acquired target asset related information; controlling a registration management database that registers the issued non-fungible token while ensuring non-tampering, which indicates a characteristic for preventing tampering by unauthorized persons; and acquiring information on ownership rights indicating that the registered non-fungible token is held by the user wishing to issue the non-fungible token. The information is provided as title information to the terminal device of the user desiring issuance, and when actual management information indicating that the asset to be issued actually exists in real space and is managed so as to be tradable is obtained from the information system, the system issues the non-fungible token, which has a token ID for identifying the non-fungible token and token-related information regarding the non-fungible token, and which specifies at least one of the processing when a transaction of the non-fungible token is executed and the processing when provision of information related to the relevant asset to be issued is requested, and which is associated with transaction processing specification information stored in a given storage medium or a given storage means.

[0010] (3) To solve the above problem, an information collection system according to a third aspect of the present invention is an information collection system that collects issuance target asset related information relating to an issuance target asset when electronic transactions on a network of the issuance target asset for which a non-fungible token is issued can be executed using a non-fungible token that embodies an asset held by a user, and the issuance target asset related information is registered in an information management database in association with a token ID for identifying the non-fungible token for each issuance target asset, or is updated and registered at a given timing after the issuance of the non-fungible token, and the information collection system includes: an acquisition means for acquiring a provision instruction transmitted from a terminal device of an information providing user who wishes to receive information on the issuance target asset, the instruction specifying the type of the issuance target asset related information to be collected from the information management database together with the token ID of the issuance target asset; and and a provision control means that executes a process to provide the collected issuance target asset related information to the relevant terminal device as a provision control process, wherein the collection means identifies the issuance target asset related information to be collected by referring to a token ID for identifying the non-fungible token and token-related information related to the non-fungible token, which are specified for the non-fungible token corresponding to the issuance target asset related information to be collected, and transaction processing specification information that specifies at least one of a process when a transaction of the non-fungible token is executed and a process when provision of the relevant issuance target asset related information is requested, and that is stored in a given storage medium or a given storage means.

[0011] (4) To solve the above-mentioned problem, a fourth aspect of the present invention provides an issuance target asset related information collection method for collecting issuance target asset related information when an electronic transaction on a network of an issuance target asset for which a non-fungible token is issued can be executed using a non-fungible token embodied in an asset held by a user, and the issuance target asset related information is collected. The issuance target asset related information is registered in an information management database for each issuance target asset in association with a token ID for identifying the non-fungible token, or is updated and registered at a given timing after the issuance of the non-fungible token, and a provision instruction is sent from a terminal device of an information providing user who wishes to be provided with information on the issuance target asset, and the type of the issuance target asset related information to be collected from the information management database together with the token ID of the issuance target asset is specified. and acquires a specified instruction, collects corresponding issuance target asset related information from information stored in the information management database based on the acquired token ID and the specified type of issuance target asset related information, and executes a process for providing the collected issuance target asset related information to a corresponding terminal device as a provision control process, and specifies the issuance target asset related information to be collected by referring to a token ID for identifying the non-fungible token and token related information related to the non-fungible token, which are specified for the non-fungible token corresponding to the issuance target asset related information to be collected, and transaction processing specification information which specifies at least one of a process when a transaction of the non-fungible token is executed and a process when provision of the corresponding issuance target asset related information is requested, and which is stored in a given storage medium or a given storage means.

[0012] (5) To solve the above problem, an information provision system according to a fifth aspect of the present invention is an information provision system that provides collected issuance target asset-related information related to an issuance target asset to an information providing user who requests it, when electronic transactions on a network of the issuance target asset for which a non-fungible token is issued can be executed using a non-fungible token embodied in an asset held by the user. In an information management database, the issuance target asset-related information is registered for each issuance target asset in association with a token ID for identifying the non-fungible token, or is updated and registered at a given timing after the issuance of the non-fungible token. The information provision system is configured to include: a reception processing means that receives a provision instruction transmitted from a terminal device of the information providing user together with the token ID of the issuance target asset; an identification means that identifies a type of the issuance target asset-related information to be collected from the information management database based on the accepted token ID; an acquisition means that acquires the issuance target asset-related information that has been identified and collected based on the identified type of the issuance target asset-related information and the accepted token ID; and a provision means that provides the acquired issuance target asset-related information to the terminal device of the information providing user.

[0013] (6) To solve the above problem, an information provision method according to a sixth aspect of the present invention is an information provision method for providing collected issuance asset-related information related to an issuance asset to an information providing user who wishes to provide the desired information, when electronic transactions on a network for the issuance asset for which a non-fungible token is issued can be executed using a non-fungible token embodied in an asset held by the user. The issuance asset-related information is registered in an information management database in association with a token ID for identifying the non-fungible token for each issuance asset, or is updated and registered at a given timing after the issuance of the non-fungible token. The information provision method is configured to accept a provision instruction sent from a terminal device of the information providing user together with the token ID of the non-fungible token embodied in the issuance asset, identify the type of issuance asset-related information to be collected from the information management database based on the accepted token ID, obtain the issuance asset-related information identified and collected based on the identified type of the issuance asset-related information and the accepted token ID, and provide the acquired issuance asset-related information to the terminal device of the information providing user.

[0014] (7) To solve the above-mentioned problems, the electronic transaction execution system according to a seventh aspect of the present invention is an electronic transaction execution system that uses a non-fungible token embodied in an asset held by a user to execute an electronic transaction on a network for an issuance target asset for which the non-fungible token is issued, as an electronic transaction, and that includes an information management database in which issuance target asset-related information for the issuance target asset for the corresponding non-fungible token is registered in association with a token ID for identifying the non-fungible token for each issuance target asset, or is updated and registered at a given timing after the issuance of the non-fungible token, and a transaction processing rule specification means that specifies a given process when executing the electronic transaction of the non-fungible token and specifies transaction processing rule information stored in a given storage medium or a given storage means; The electronic transaction system comprises a transaction execution means for executing the electronic transaction based on the specified transaction processing specification information, a registration control means for performing update registration in a database, a collection control means for controlling the collection of issuance target asset related information regarding the issuance target asset of the corresponding non-fungible token from the information management database based on the specified transaction processing specification information when executing the electronic transaction, and a provision means for providing the collected issuance target asset related information to a corresponding terminal device, wherein the collection control means is configured to identify the type of issuance target asset related information to be collected from the information management database based on the specified transaction processing specification information, and collect the corresponding issuance target asset related information from the information stored in the information management database based on the specified type of issuance target asset related information.

[0015] (8) To solve the above-mentioned problem, a seventh aspect of the present invention provides a method for executing an electronic commerce transaction, which uses a non-fungible token embodied in an asset held by a user to execute an electronic transaction on a network for an issuance target asset for which the non-fungible token is issued, as an electronic transaction, wherein an information management database stores issuance target asset-related information for the issuance target asset for the corresponding non-fungible token, in association with a token ID for identifying the non-fungible token, for each issuance target asset, or the information is updated and registered at a given timing after the issuance of the non-fungible token, and a given process for executing the electronic transaction of the non-fungible token is specified, and the transaction information is stored in a given storage medium or a given storage means. The electronic transaction control system is configured to identify processing specification information, and based on the identified transaction processing specification information, execute an update registration in a transaction execution means that executes the electronic transaction and a database, and when executing the electronic transaction, control the collection of issuance target asset related information regarding the issuance target asset of the relevant non-fungible token from the information management database based on the identified transaction processing specification information, provide the collected issuance target asset related information to the relevant terminal device, identify the type of issuance target asset related information to be collected from the information management database based on the identified transaction processing specification information, and collect the relevant issuance target asset related information from the information stored in the information management database based on the identified type of issuance target asset related information.

[0016] FIG. 1 is a system configuration diagram for each function for executing each process related to circulating NFTs in an electronic transaction network system according to an embodiment. FIG. 2 is a system configuration diagram in which a given function executed in an electronic transaction network system according to an embodiment is configured as a system based on multiple virtual machines. FIG. 3 is an example of a functional block diagram showing the configuration of a token issuing server device according to an embodiment. FIG. 4 is a functional block diagram showing an example of the configuration of a terminal device according to an embodiment. FIG. 5 is an example of a functional block diagram showing the configuration of an information providing server device according to an embodiment. FIG. 6 is an example of a functional block diagram showing the configuration of a transaction management server device according to an embodiment. FIG. 7 is a diagram for explaining NFT issuance control processing, which is part of the overall processing related to the issuance of NFTs embodied in assets to be issued, the provision of NFT-related information, and the trading of NFTs in an electronic transaction network system according to an embodiment. FIG. 8 is a diagram illustrating an NFT-related information collecting and providing process, which is part of the overall process related to the issuance of an NFT embodied in an asset to be issued, the provision of NFT-related information, and trading of the NFT in an electronic trading network system of an embodiment. FIG. 9 is a diagram illustrating an NFT-related information collecting and providing process, which is part of the overall process related to the issuance of an NFT embodied in an asset to be issued, the provision of NFT-related information, and trading of the NFT in an electronic trading network system of an embodiment. FIG. 10 is a diagram illustrating an example of image information (image information generated by control information) for allowing a user to view issuance-related information including token-related information acquired by the NFT-related information collecting and providing process in an embodiment. FIG. 11 is a flowchart illustrating the operation of an NFT issuance control process executed by a token issuing server device of an embodiment. FIG. 12 is a flowchart illustrating the operation of an NFT-related information collecting and providing process executed by an information providing server device of an embodiment. FIG. 13 is a flowchart illustrating the operation of an NFT-related information collecting and providing process executed by an information providing server device of an embodiment. FIG. 14 is a diagram for explaining an NFT transaction execution control process including an NFT-related information collection and provision process executed by a transaction management server device of one embodiment.15 and 16 are flowcharts illustrating the operation of an NFT transaction execution control process executed by an information transaction management server device according to an embodiment of the present invention.

[0017] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0018] (1) One embodiment of the present invention is a token issuance management system that issues non-fungible tokens used for electronic transactions on a network for assets held by a user, the system including: a receiving means that receives an instruction to issue the non-fungible token for a given asset, the instruction being transmitted from a terminal device of a user who wishes to issue the non-fungible token; an acquiring means that acquires, as issuance target asset related information, information on the issuance target asset for which the non-fungible token is to be issued, from the terminal device of the user who wishes to issue the non-fungible token or an information system operated by an administrator who manages the assets in real space; a token issuing means that issues a non-fungible token that embodies the issuance target asset based on the received issuance instruction and the acquired issuance target asset related information; and a registering means that registers the issued non-fungible token while ensuring non-tampering, which indicates a characteristic for preventing tampering by unauthorized persons. and provision means for providing information regarding ownership rights indicating that the registered non-fungible token is held by the issuing user to the terminal device of the issuing user as ownership rights information, wherein when the token issuing means acquires from the information system real-world management information indicating that the asset to be issued actually exists in real space and is managed so as to be tradable, the token issuing means issues the non-fungible token, which has a token ID for identifying the non-fungible token and token-related information regarding the non-fungible token, and which specifies at least one of processing when a transaction of the non-fungible token is executed and processing when provision of information related to the relevant asset to be issued is requested, and which is associated with transaction processing specification information stored in a given storage medium or a given storage means.

[0019] Note that one embodiment of the present invention may be realized by a non-fungible token issuing method instead of the above-described token issuance management system.

[0020] With this configuration, one embodiment of the present invention can ensure the existence of the assets to be issued, and if the assets are managed appropriately, can transform the assets to be issued into unique non-fungible tokens (i.e., non-fungible tokenization (so-called NFT)).This means that tangible assets such as physical objects or rights that can be traded in the real world, or intangible assets, can be treated as equivalent assets on the network.

[0021] In other words, one embodiment of the present invention can ensure the existence and authenticity of assets that exist in the real world when they are converted into NFTs or when the assets are circulated as NFTs, and therefore can provide the assets as digital assets that are highly reliable, easy to handle, and transparent.

[0022] Note that "asset" refers to assets that have a real existence in the real world (i.e., assets that are the subject of transactions), such as tangible assets, intangible assets, financial assets, real assets, and various rights.

[0023] "Non-fungible token" refers to data (tokens) such as crypto assets that are unique and non-fungible and are processed and stored in a decentralized manner while transaction records are encrypted using blockchain technology, and that function as the subject of transactions. However, "decentralized processing and storage" refers to, for example, the same (integrated) processing and the same (integrated) storage being executed in multiple systems or multiple storage media.

[0024] Furthermore, "accepting an instruction to issue a non-fungible token sent from a terminal device" includes not only cases where the instruction is sent directly, but also cases where the instruction is received via another device such as a server device.

[0025] The "information related to the asset to be issued" includes, for example, at least the following information: (A1) information indicating the type of the asset to be issued (including the type of physical or intangible object), the name of the asset, the price (including not only the current price but also various prices such as the reserve price and bid price in the case of an auction), or identification information of the asset to be issued, such as a model number or certification number (hereinafter referred to as "asset ID"); (A2) if the asset to be issued is composed of multiple tangible or intangible assets of the same type or different types, information on the number of such assets (if there are multiple types, the number of each type); and (A3) information on the attributes of the asset to be issued (if the asset to be issued is a physical object, information on the creator or manufacturer, the time or date of production of the asset to be issued, the place of production or the raw materials, etc.) (hereinafter also referred to as "basic information on the asset to be issued").

[0026] In particular, such asset-related information to be issued may be obtained from information that has been pre-registered in the information system, or may be obtained from information input by the relevant user (via a terminal device).

[0027] Furthermore, "information system operated by an administrator" refers to an information system operated by a public institution that manages the assets to be issued, as well as an information system operated by a business that preserves, certifies, or manages the value or status of the assets to be issued, such as an information system operated by a business that determines the authenticity (determines the genuineness) of the assets to be issued or stores them.

[0028] In addition to the above, "illegal person" refers to a person who does not have legitimate authority, and refers to a malicious third party such as an "impersonator."

[0029] Furthermore, "ensuring non-tamperability" refers to ensuring that recorded data cannot be tampered with, for example, by encrypting data or using blockchain technology that performs distributed registration.

[0030] The "administrator" includes, for example, if the asset is a physical object, a business operator who operates a business where the physical object is stored, such as a warehouse, and an administrator who manages intangible assets, such as a bank or securities company, and is a third party different from the user wishing to issue the asset.

[0031] Furthermore, "real-life management information" includes at least information indicating that movable property is stored in a designated location while maintaining a designated condition, such as a warehouse, or that the value of assets is preserved, such as real estate or rights being publicly verifiable and properly managed, such as by registration or enrollment.

[0032] Furthermore, "assets exist in the real world" means that even intangible assets such as rights can be traded in the real world through registration or other means.

[0033] In addition to the above, "token-related information" includes, for example, (B1) information for identifying the holder of the non-fungible token (i.e., the holder who holds the asset to be issued) (hereinafter referred to as "holder identification information"), and (B2) information on the location where the non-fungible token is electronically held (in a terminal device or in a database of an exchange, etc.), such as the address of the wallet that holds the non-fungible token (i.e., the wallet address). However, the token-related information does not need to include all of the information in (B1) and (B2) (i.e., it may only include some of the information).

[0034] In particular, when non-fungible tokens use a distributed ledger technology such as blockchain, which is difficult to tamper with, it is preferable that the "token-related information" basically be composed of a smaller amount of data, from the viewpoint that the tokens are distributedly registered in a chain using part of past data. Therefore, for token-related information that cannot be directly stored in non-fungible tokens, it is preferable to store an address for referencing the relevant information.

[0035] For example, "holder identification information" may include any one or a combination of the following: (C1) information on the holder's name (including the holder ID and nickname indicating the user ID), (C2) information on the holder's place of residence such as address and residence, (C3) information on the holder's attributes (age, generation, gender, nationality, etc.), and (C4) the holder's contact information (for example, email address, SNS (social network service) ID or telephone number).

[0036] Furthermore, "transaction processing specification information" refers to, for example, a program that is automatically executed in conjunction with a terminal device or the like when a transaction of a non-fungible token is executed.

[0037] In particular, the "transaction processing specification information" includes, for example, (D1) information (hereinafter also referred to as "application specification information") that specifies an application (for example, an application based on a smart contract that can be executed within a specific platform such as a De-Fi contract) that executes processing to determine whether or not a transaction can be executed based on transaction conditions that indicate the conditions under which a transaction of the issuance target asset is executed, and (D2) information (application specification information) that specifies an application (for example, an application based on a smart contract for linking with information or devices outside a specific platform such as an oracle contract) that executes processing to collect information to be provided to traders when a transaction of the issuance target asset is executed (i.e., hereinafter referred to as "issuance target asset related information").

[0038] Furthermore, "transaction processing specification information stored in a given storage medium or a given storage means" refers to information stored, for example, in a physically or electronically mobile storage medium (which may include the NFT itself), or in one or more databases existing on a network.

[0039] (2) In addition, in one embodiment of the present invention, the token issuing means is configured to issue the non-fungible token to which at least one of the following application specification information is associated as the transaction processing specification information: information specifying a transaction execution application for executing the transaction based on the transaction conditions for the transaction of the issuance target asset, and information specifying an information acquisition application for acquiring issuance target asset related information indicating information to be provided to the transaction target user when the issuance target asset is traded.

[0040] With this configuration, one embodiment of the present invention can automatically execute an application using a non-fungible token when a transaction of the asset to be issued is executed, thereby ensuring that the transaction is executed in accordance with the transaction conditions and providing the user of the transaction with the information they require when executing the transaction.

[0041] Therefore, one embodiment of the present invention simplifies user operations when trading for holders or those wishing to hold non-fungible tokens, and enables such transactions to be carried out reliably and safely.

[0042] It should be noted that the term "transaction target user" includes, for example, not only the transactor who executes the transaction, but also the transaction-seeking user who wishes to carry out the transaction.

[0043] Furthermore, the term "application" refers to, for example, an application such as a decentralized application (DApps) that automatically executes a given program (e.g., asset trading or provision of asset-related information) on a specific platform when given transaction conditions are met (i.e., an application based on a De-Fi contract and an oracle contract). However, the term "application" may also refer to an application that runs on multiple platforms.

[0044] For example, an "application" includes code for running a program on a platform and variables embedded in that code.

[0045] For example, the "transaction conditions" are conditions for determining whether or not a transaction can be carried out, such as (E1) the amount of the asset to be issued, (E2) the location in real space where the asset to be issued is located (location based on time), (E3) the storage condition of the asset to be issued in real space, and (E4) whether or not there is a certificate of authenticity or certification by a third party organization.

[0046] For example, the "information related to the asset to be issued" includes: (F1) basic information about the asset to be issued; (F2) information about the authenticity (genuineness) of the asset to be issued (hereinafter referred to as "genuineness information"); (F3) information about the actual location of the asset to be issued in real space (which may include the time when the asset was at that location) (hereinafter referred to as "location-related information"); and (F4) information about the storage of the asset to be issued (hereinafter referred to as "storage information").

[0047] In particular, the "information related to the asset to be issued" may include not only the above-mentioned various pieces of information at the time of the transaction, but also past information (i.e., history information).

[0048] For example, the authenticity information includes information indicating whether the asset to be issued is authentic, information on the appraiser of authenticity, such as the name of the appraiser who performed the appraisal, and information on the appraisal date and time when the appraisal was performed.

[0049] For example, the location-related information includes current location information indicating the current location of the asset to be issued (including the name of the area or building to identify the location), and information on the date and time when the current location information of the asset to be issued was obtained.

[0050] For example, the storage information includes information on the storage status (including the type of storage location) of the asset to be issued, information on the storage period of the asset to be issued, and the like.

[0051] (3) Furthermore, one embodiment of the present invention is configured such that the issuance target asset related information is registered in the information management database in association with a token ID for identifying the non-fungible token for each issuance target asset, or is updated and registered at a given timing after the issuance of the non-fungible token, and further includes an acquisition means for acquiring a provision instruction transmitted from a terminal device of an information providing user who wishes to receive information related to the issuance target asset, the instruction specifying the type of the issuance target asset related information to be collected from the information management database along with the token ID of the issuance target asset, and a collection means for collecting relevant issuance target asset related information from information stored in the information management database based on the acquired token ID and the specified type of issuance target asset related information, and the provision means provides the collected issuance target asset related information to the relevant terminal device.

[0052] With this configuration, one embodiment of the present invention can provide information related to the asset to be issued when a transaction of the non-fungible token is executed by a server device that issues the non-fungible token, and can also present the latest information related to the asset to be issued at the time of the transaction, thereby not only improving the trading environment for the non-fungible token, but also proving the authenticity of the non-fungible token.

[0053] Therefore, one embodiment of the present invention can also execute transactions of non-fungible tokens, and can therefore be executed with a simple configuration and can be easily managed.

[0054] Furthermore, one embodiment of the present invention can maintain the ease and transparency of handling assets that exist in the real world and are owned by a user based on digitalization, while ensuring the existence and authenticity of the assets when they are converted into NFTs or when they are circulated as NFTs, thereby ensuring their reliability as assets.

[0055] (4) Furthermore, one embodiment of the present invention has a configuration in which the registration control means encrypts the non-fungible token to ensure the non-tampering, and distributes and registers the encrypted non-fungible token in multiple registration management databases on the network.

[0056] With this configuration, one embodiment of the present invention can register transaction information for non-fungible tokens in multiple databases using a distributed ledger technology that is difficult to tamper with, such as a blockchain, thereby decentralizing and accurately preventing tampering of transaction information for non-fungible tokens by unauthorized parties.

[0057] Therefore, one embodiment of the present invention can ensure the reliability of transactions of non-fungible tokens and prevent tampering with the non-fungible tokens, thereby maintaining the ease and transparency of handling assets based on digitization, while ensuring the existence and authenticity of the assets when they are converted into NFTs or when they are circulated as NFTs, and ensuring the reliability of the assets.

[0058] Note that "encrypted non-fungible tokens are distributed across multiple registration management databases on the network" means that they are managed in a distributed manner, preventing tampering and using blockchain technology, for example, rather than in a centralized manner.

[0059] (5) In order to solve the above problem, one embodiment of the present invention is an information collection system that collects issuance target asset related information regarding an issuance target asset when electronic transactions on a network of the issuance target asset for which a non-fungible token is issued can be executed using a non-fungible token that embodies an asset held by a user, the issuance target asset related information being registered in an information management database in association with a token ID for identifying the non-fungible token for each issuance target asset, or being updated and registered at a given timing after the issuance of the non-fungible token, and an acquisition means for acquiring a provision instruction transmitted from a terminal device of an information providing user who wishes to receive information regarding the issuance target asset, the instruction specifying the type of the issuance target asset related information to be collected from the information management database together with the token ID of the issuance target asset; and and a provision control means that executes a process to provide the collected issuance target asset related information to the relevant terminal device as a provision control process, wherein the collection means identifies the issuance target asset related information to be collected by referring to a token ID for identifying the non-fungible token and token-related information related to the non-fungible token, which are specified for the non-fungible token corresponding to the issuance target asset related information to be collected, and transaction processing specification information that specifies at least one of a process when a transaction of the non-fungible token is executed and a process when provision of the relevant issuance target asset related information is requested, and that is stored in a given storage medium or a given storage means.

[0060] Note that one embodiment of the present invention may be realized by a method for collecting information related to assets to be issued, instead of the above-described information collection system.

[0061] With this configuration, one embodiment of the present invention allows users wishing to provide information to receive information on the issuance assets for which they wish to receive information, and also allows users to receive the latest information on the issuance assets at the time of information provision while also referencing information on non-fungible tokens.This not only makes it possible to provide accurate and ample information, but also improves the trading environment for issuance assets via non-fungible tokens and proves the authenticity and appropriate value of the non-fungible tokens.

[0062] Therefore, one embodiment of the present invention eliminates the need to register a large amount of information and constantly update registered information when managing non-fungible tokens, and can reduce processing speeds and approval delays that accompany the increased amount of data that must be stored using distributed ledger technologies such as blockchain technology.

[0063] It should be noted that the "provision instruction sent from the terminal device of the user desiring information provision" includes not only cases where it is sent directly from the terminal device, but also cases where it is sent via another device such as a server device.

[0064] Furthermore, the "provision control process" refers to a process of providing information to the terminal device of the relevant user directly or indirectly via another device.

[0065] (6) In addition, in one embodiment of the present invention, the transaction processing specification information includes at least one of application specification information: information specifying a transaction execution application for executing the transaction based on the transaction conditions for the transaction of the issuance target asset, and information specifying an information acquisition application for acquiring issuance target asset related information indicating information to be provided to the transaction target user when trading the issuance target asset; and the acquisition means is configured to acquire a provision instruction specifying the type of issuance target asset related information to be collected, which is specified based on the application specification information.

[0066] With this configuration, one embodiment of the present invention allows users wishing to receive information on assets to be issued according to the information acquisition application, and also allows users wishing to receive information on assets to be issued regarding the execution of transactions during the transaction execution application.

[0067] (7) Furthermore, in order to solve the above problem, the present invention provides an information provision system that provides collected issuance asset-related information about an issuance asset to a requesting information user when electronic transactions on a network for the issuance asset for which a non-fungible token is issued can be executed using a non-fungible token that embodies an asset held by the user. The issuance asset-related information is registered in an information management database for each issuance asset in association with a token ID for identifying the non-fungible token, or is updated and registered at a given timing after the issuance of the non-fungible token. The information provision system is configured to include: a reception processing means that receives a provision instruction sent from the terminal device of the information requesting user together with the token ID of the issuance asset; an identification means that identifies a type of the issuance asset-related information to be collected from the information management database based on the accepted token ID; an acquisition means that acquires the issuance asset-related information that has been identified and collected based on the identified type of the issuance asset-related information and the accepted token ID; and a provision means that provides the acquired issuance asset-related information to the terminal device of the information requesting user.

[0068] Note that one embodiment of the present invention may be realized by an information providing method instead of the above-described information providing system.

[0069] With this configuration, one embodiment of the present invention allows users wishing to provide information to receive information on the issuance assets for which they wish to receive information, and also allows users to receive the latest information on the issuance assets at the time of information provision while also referencing information on non-fungible tokens.This not only makes it possible to provide accurate and ample information, but also improves the trading environment for issuance assets via non-fungible tokens and proves the authenticity and appropriate value of the non-fungible tokens.

[0070] Therefore, one embodiment of the present invention eliminates the need to register a large amount of information and constantly update registered information when managing non-fungible tokens, and can reduce processing speeds and approval delays that accompany the increased amount of data that must be stored using distributed ledger technologies such as blockchain technology.

[0071] (8) Furthermore, one embodiment of the present invention is configured such that the acquisition means acquires token-related information regarding the non-fungible token based on the token ID of the non-fungible token that is the subject of the transaction, and the provision means generates control information to be recognized by the user who wishes to receive information based on the acquired token-related information and the collected information related to the asset to be issued, and provides the generated control information to the relevant terminal device.

[0072] With this configuration, one embodiment of the present invention allows the user to easily recognize the issuance target asset related information along with the token information, thereby improving convenience for the user.

[0073] The "control information" is, for example, information to be recognized by the user, and includes image control information used when an image is generated on the terminal device.

[0074] (9) To solve the above problem, one embodiment of the present invention is an electronic transaction execution system that uses a non-fungible token embodied in an asset held by a user to execute an electronic transaction on a network for an issuance target asset for which the non-fungible token is issued as an electronic transaction, wherein an information management database stores issuance target asset-related information for the issuance target asset for the corresponding non-fungible token in association with a token ID for identifying the non-fungible token for each issuance target asset, or the information is updated and registered at a given timing after the issuance of the non-fungible token, and a transaction processing rule specifying means for specifying a given process when executing the electronic transaction of the non-fungible token and for specifying transaction processing rule information stored in a given storage medium or a given storage means; and a transaction execution means for executing the electronic transaction and a registration control means for performing update registration in a database based on the specified transaction processing specification information; a collection control means for controlling the collection of issuance target asset related information regarding the issuance target asset of the relevant non-fungible token from the information management database based on the specified transaction processing specification information when executing the electronic transaction; and a provision means for providing the collected issuance target asset related information to a relevant terminal device, wherein the collection control means is configured to identify the type of issuance target asset related information to be collected from the information management database based on the specified transaction processing specification information, and collect the relevant issuance target asset related information from information stored in the information management database based on the identified type of issuance target asset related information.

[0075] Note that one embodiment of the present invention may be realized by an electronic transaction execution method instead of the above-described electronic transaction execution system.

[0076] With this configuration, one embodiment of the present invention allows access to information on the assets to be issued when trading non-fungible tokens, and also allows access to the latest information on the assets to be issued at the time of the transaction while also referencing the information on the non-fungible tokens. This not only makes it possible to provide accurate and ample information, but also improves the trading environment for assets to be issued via non-fungible tokens, and can prove the authenticity and appropriate value of the non-fungible tokens.

[0077] Therefore, one embodiment of the present invention eliminates the need to register a large amount of information and constantly update registered information when managing non-fungible tokens, and can reduce processing speeds and approval delays that accompany the increased amount of data that must be stored using distributed ledger technologies such as blockchain technology.

[0078] (10) Furthermore, one embodiment of the present invention further includes an acquisition means for acquiring token-related information regarding the non-fungible token based on the token ID of the non-fungible token that is the subject of the transaction, and a control information generation means for generating control information to be recognized by the target user of the transaction based on the acquired token-related information and the collected information related to the asset to be issued, and the provision means is configured to provide the generated control information to a corresponding terminal device.

[0079] With this configuration, one embodiment of the present invention can collect information related to the asset to be issued as well as information on the non-fungible tokens corresponding to that information, thereby allowing the user to easily recognize the information related to the asset to be issued along with the token information, thereby improving convenience for the user.

[0080] The embodiment described below is an embodiment in which the token issuance management system, information collection system, electronic trading system, etc. of the present application are applied to an electronic trading network system that uses non-fungible tokens (hereinafter referred to as "NFTs (Non Fungible Tokens)") to carry out electronic transactions on a network of assets held by users in real space.

[0081] Additionally, in the following description, unless otherwise specified, each process related to the issuance of an NFT and each process related to the transaction of that NFT will be described as the process of the token issuance server device 10 and the transaction management server device 40 (see FIGS. 1 and 2). However, when the process of the information provision server device 30 is executed, the process executed by DApps based on the De-Fi contract will be described as being executed by the NFT virtual machine M.

[0082] [1] Overview of the Electronic Transaction Network System First, the overview and system configuration of the electronic transaction network system S of this embodiment will be described with reference to FIGS.

[0083] 1 is a system configuration diagram for each function for executing each process related to circulating NFTs in the electronic transaction network system S of this embodiment. Also, FIG. 2 is a system configuration diagram in which a given function executed in the electronic transaction network system of this embodiment is configured as a system based on multiple virtual machines M. To avoid cluttering the diagrams, FIGS. 1 and 2 only show terminal devices 20 used by some users, some information-providing server devices 30, some databases (hereinafter also referred to as "DBs") 50 and 60, and the NFT virtual machine M.

[0084] That is, in an actual electronic transaction network system S, there are many more terminal devices 20, information-providing server devices 30, databases 50 and 60, and NFT virtual machines M than are shown in FIG. 1 or FIG.

[0085] (System Overview) As shown in Figures 1 and 2, the electronic trading network system S of this embodiment is a system that uses NFTs that embody assets held by users to carry out electronic trading (circulation) on a network of assets (hereinafter referred to as "issuance target assets") that are the subject of the issuance of NFTs, and manages such trading.

[0086] In particular, the electronic trading network system S is configured to ensure the existence of assets that have a real existence in the real world (i.e., assets that are the subject of trading), such as tangible assets, intangible assets, financial assets, real assets, and various rights, and, if managed appropriately, to turn such assets into unique non-fungible tokens (NFTs) as assets to be issued, and treat them as equivalent assets on the network.

[0087] Furthermore, the electronic transaction network system S is configured to be able to execute electronic transactions (e.g., electronic commerce) of assets that exist in the real world (RAW: Real World Assets) as assets to be issued, or to provide information such as the ability to view the assets to be issued, using smart contracts (transaction processing specification information) that specify predetermined processes and constraints, in order to circulate these assets on the network using NFTs.

[0088] The electronic trading network system S is a system for circulating NFTs as a financial service (De-Fi: Decentralized Finance) that is provided autonomously and automatically, and is configured to execute electronic transactions of the target assets in accordance with a De-Fi contract (hereinafter also referred to as an "RWA contract") as a smart contract, or to provide users with various information regarding NFTs (hereinafter referred to as "NFT-related information" or "token-related information"), including information related to the target assets, such as viewing or confirmation of the target assets.

[0089] The electronic trading network system S of this embodiment is configured to circulate NFTs with De-Fi contracts implemented on a platform (e.g., a blockchain platform) that is tamper-resistant and manages data in a distributed manner.

[0090] Specifically, the electronic trading network system S of this embodiment has a configuration in which each process, such as issuance and trading of NFTs, is executed in a distributed manner by a virtual machine M for executing De-Fi contracts (hereinafter referred to as an "NFT virtual machine").

[0091] That is, as shown in Figures 1 and 2, the electronic trading network system S of this embodiment is configured to execute various operations and transactions (transaction history) as an NFT virtual machine (also called a node) M on a tamper-resistant decentralized management platform (hereinafter referred to as the "NFT decentralized management platform") for circulating NFTs, and to execute processes specified in the De-Fi contract, such as the issuance and trading of NFTs.

[0092] The electronic trading network system S of this embodiment is configured to run DApps (Decentralized Applications) like a virtual machine (running on each node) based on a De-Fi contract, and to perform various processes such as issuing NFTs, providing information about NFTs, and trading the NFTs.

[0093] On the other hand, the electronic trading network system S of this embodiment has a configuration that introduces an oracle contract to incorporate the asset information to be issued, which is external information (so-called off-chain information) of the NFT decentralized management platform, into the De-Fi contract.

[0094] In other words, the electronic trading network system S of this embodiment is configured to execute each process in a virtual machine manner as a DApps that links De-Fi contracts based on on-chain information and oracle contracts that import off-chain information.

[0095] In addition, the DApps of this embodiment are used as a given program (e.g., trading assets or providing information about assets) when given transaction conditions are met on the NFT decentralized management form, but may also be an application that runs on multiple platforms.

[0096] In addition, the DApps of this embodiment are, in principle, applications that are executed automatically based on smart contracts and oracle contracts, but are also executed based on instructions from the terminal device 20 (including instructions from the user) as appropriate.

[0097] For example, the DApps of this embodiment are made up of code for executing a program on a platform and variables incorporated in the code.

[0098] Furthermore, although the DApps of this embodiment executes each process on the same NFT distributed management platform, it may also be compatible with multiple platforms.

[0099] (System Configuration) The electronic trading network system S of this embodiment includes a token issuance server device 10 that issues NFTs, terminal devices 20 (e.g., terminal devices 20A, 20B, 20C) on which various operations are performed by users, and an information-providing server device 30 (e.g., information-providing server devices 30A, 30B) that collects information related to the assets to be issued (hereinafter referred to as "information related to the assets to be issued") at given times, such as when NTF transactions are executed, and provides the information to the relevant users.

[0100] Furthermore, as shown in Figures 1 and 2, the electronic transaction network system S of this embodiment has, for example, a transaction management server device 40 that functions as an exchange for electronically trading NFTs and executes various processes for managing electronic transactions, multiple databases (hereinafter referred to as "token registration DBs") 50 in which NFTs and transaction processing specification information (i.e., De-Fi contracts) that specifies various processes and constraints when NFT transactions or information provision are executed are registered, and a database (hereinafter referred to as "asset information management DB") 60 in which information related to assets to be issued for each NFT is registered.

[0101] In particular, in the electronic transaction network system S of this embodiment, each function of the server device 10 for issuing tokens issued by NFTs and each function of the transaction management server device 40 that executes various processes for managing electronic transactions can be realized by one or more NFT virtual machines M formed on the FT distributed management platform, as shown in Figures 1 and 2.

[0102] The token issuing server device 10 of this embodiment is a server device that issues NFTs in association with assets held by a user who wishes to issue an NFT on an electronic trading network system S, which electronically circulates assets held by the user by using NFTs that embody the assets.

[0103] The token issuance server device 10 is configured to execute various processes related to the issuance of NFTs, for example, by using an NFT decentralized management platform.

[0104] In particular, the token issuance server device 10 is configured to work in conjunction with the terminal device 20 and the asset management server device 80 to execute an NFT issuance process that embodies assets held by the user (i.e., assets to be issued) and is used for electronic transactions on the network.

[0105] In addition, the token issuance server device 10 may be configured with one or more NFT virtual machines M as described above, or instead of the NFT virtual machine M, it may be configured with one (device, processor) or multiple (devices, processors).

[0106] The terminal device 20 is a communication terminal device that is used by a user and is configured by an information processing device such as a PC (personal computer), a tablet-type information communication terminal device, a smartphone, a mobile phone, or an HMD.

[0107] In addition, the terminal device 20 is a device that can be connected to the token issuing server device 10, the information providing server device 30, and the transaction management server device 40 via a network such as the Internet (WAN) or LAN, and is configured to exchange various types of data.

[0108] In particular, the terminal device 20 has a digital wallet (hereinafter simply referred to as "wallet") that is associated with the user's identification information (i.e., user ID) and stores NFTs held by the user.

[0109] In addition, when the terminal device 20 requests the issuance of a new NFT, it is configured to work in conjunction with the token issuance server device 10 and use a wallet to request the issuance of an NFT associated with the asset to be issued and to execute various processes related to the issuance.

[0110] Furthermore, when the terminal device 20 wishes to trade an NFT (i.e., an NFT registered in association with a wallet address) associated with its own wallet or another terminal device 20 (specifically, a wallet of another device), the terminal device 20 is configured to work in conjunction with the transaction management server device 40 and perform various processes related to NFT transactions.

[0111] Furthermore, when the terminal device 20 wishes to be provided with information regarding NFTs, it is configured to work in conjunction with the information providing server device 30 and the transaction management server device 40 to obtain information regarding the asset to be issued (i.e., NFT-related information) and perform various control processes such as display control for viewing or notification control for notifying.

[0112] The information-providing server device 30 is a server device that collects NFT-related information and performs a process of providing the information to the relevant user when a user requests information regarding NFTs, such as when an NFT transaction is executed (hereinafter referred to as the "NFT-related information collection and provision process").

[0113] Specifically, for example, when an NFT transaction is executed, or when a user simply requests the provision of NFT information, the information providing server device 30 is configured to link with the corresponding terminal device 20 and transaction management server device 40 and provide NFT-related information, including information related to the asset to be issued, to the user who requests it (hereinafter referred to as the "information-requesting user").

[0114] In particular, when an NFT transaction is executed or when a user requests the provision of NFT information, the information providing server device 30 is configured to refer to the De-Fi contract, work in conjunction with the terminal device 20 and the transaction management server device 40, search the asset information management DB 60 in which issuance target asset related information for each NFT is registered, and execute an information collection process to collect issuance target asset related information for the NFT for which information is to be provided.

[0115] In addition, the information-providing server device 30 may be configured with one or more NFT virtual machines M as described above, or may be configured with one or more devices or processors instead of the NFT virtual machines M.

[0116] The transaction management server device 40 is a server device that, for example, uses an NFT decentralized management platform, etc., and, while referencing De-Fi contracts, provides information about NFTs and performs various processes related to electronic transactions of NFTs (hereinafter referred to as "NFT transaction execution control processes").

[0117] In particular, the transaction management server device 40 has the unique ability to perform various processes related to electronic transactions of NFTs for users (hereinafter referred to as "registered users") registered in a network service that conducts NFT transactions (hereinafter referred to as "electronic transaction service").

[0118] In addition, the transaction management server device 40 has a wallet function for each user, and when an NFT transaction is executed (including cases where an NFT transaction is not executed but various information about the NFT is desired), it works in conjunction with the information provision server device 30 to obtain NFT-related information, including information related to the asset to be issued, and provides it to the relevant terminal device 20.

[0119] In addition, the transaction management server device 40 may be configured with one or more NFT virtual machines M as described above, or may be configured with one or more devices or processors instead of the NFT virtual machines M.

[0120] Each token registration DB50 is a database in which, for example, when a new NFT is issued or when an NFT transaction is executed, the corresponding NFT is encrypted using blockchain technology and registered in a distributed manner.

[0121] Each token registration DB50 may be composed of various databases (broadly speaking, storage devices, memories) such as a hard disk drive connectable to a network, or may be formed together with an information processing device connected to the network N, such as a PC (personal computer) or a server device.

[0122] Each asset information management DB 60 is linked to the asset management server device 80, and is a database in which information related to the asset to be issued is registered in correspondence with a token ID for identifying the NFT for each asset to be issued, or is updated and registered at a given time after the NFT is issued.

[0123] Each asset information management DB 60 may be composed of various databases (broadly speaking, storage devices, memories) such as hard disk drives that can be connected to a network, or may be formed together with an information processing device connected to the network N, such as a PC (personal computer) or a server device.

[0124] The asset management server device 80 is a server device that belongs to an information system operated by an administrator who manages the assets to be issued in the real world, and is a server device operated by an operator that preserves, certifies, or manages the value or status of the assets to be issued, such as an information system operated by an operator that determines the authenticity (determines the genuineness) or stores the assets to be issued, as well as a server device operated by a public institution that manages the assets to be issued.

[0125] Specifically, when a user who wishes to issue an NFT requests the issuance of an NFT corresponding to an asset they own, the asset management server device 80 is configured to register the asset as an asset to be issued, along with the transfer of management authority (including the transfer of ownership rights) to the administrator of the asset (i.e., the asset to be issued).

[0126] In particular, the asset management server device 80 is configured to work in conjunction with the terminal device 20 to obtain information necessary for managing the issuance target asset, such as information identifying the issuance target asset (hereinafter referred to as ``issuance target asset identification information'') when the issuance target asset is registered.

[0127] The asset management server device 80 is configured to work in conjunction with the token issuance server device 10 and the like, and to provide or register information necessary for issuing NFTs as asset existence management information, such as information identifying the asset to be issued and information indicating the management status of the asset to be issued, at the time of issuing an NFT.

[0128] In addition, the asset management server device 80 is configured to provide or register in the asset information management DB 60 information indicating that the value of assets is preserved, such as that movable property is stored in a designated location while maintaining a designated state, such as a warehouse, or that real estate or rights are publicly verifiable and properly managed through registration or other means (i.e., reality management information indicating that the asset to be issued actually exists in real space and is properly managed, hereinafter referred to as "asset reality management information").

[0129] In addition, the administrator in this embodiment includes, for example, if the asset to be issued is a physical object, a business operator who operates a business where the physical object is stored, such as a warehouse, and an administrator who manages intangible assets, such as a bank or securities company, and is a third party different from the user wishing to issue.

[0130] [2] Token Issuance Server Device Next, the token issuance server device 10 of this embodiment will be described with reference to Fig. 3. Fig. 3 is an example of a functional block diagram showing the configuration of the token issuance server device 10 of this embodiment.

[0131] Furthermore, part or all of the token issuance server device 10 of this embodiment may be realized by an NFT virtual machine M, as shown in Fig. 2. However, in the following embodiment, unless otherwise specified, the token issuance server device 10 will be described as being configured by hardware.

[0132] As shown in Fig. 3, the token issuance server device 10 of this embodiment includes a processing unit 100, a storage unit 170, an information storage medium 180, and a communication unit 196. Note that the token issuance server device 10 does not need to include all of the units shown in Fig. 3, and may have a configuration in which some of the units are omitted.

[0133] The storage unit 170 serves as a work area for the processing unit 100 and the like, and its functions can be realized by hardware such as RAM (VRAM).

[0134] Specifically, the memory unit 170 includes a main memory unit 171 used as a work area when executing various processes, an NFT issuance information memory unit 172 in which information necessary for issuing NFTs is stored, and an issuance target asset information memory unit 173 in which initial information regarding the issuance target asset (i.e., related to the issuance target asset) and an address indicating the location where the issuance target asset related information is registered (hereinafter also referred to as the "registration address") are stored.

[0135] In particular, the NFT issuance information storage unit 172 stores information required when issuing an NFT, such as a token ID (already issued) that associates the issuance target asset with the NFT. Note that the storage unit 170 of this embodiment may be configured to omit some of the components, such as the main storage unit 171, the NFT issuance information storage unit 172, and the issuance target asset information storage unit 173.

[0136] Furthermore, the issuance target asset information storage unit 173 may be formed separately from the token issuing server device 10, as long as it is connected via a network, or may be formed under the management of the information providing server device 30, the transaction management server device 40, or other server device not shown.

[0137] The information storage medium 180 is computer-readable and stores programs, data, and the like. That is, the information storage medium 180 stores programs for causing a computer to function as each unit of this embodiment (programs for causing a computer to execute the processing of each unit). The processing unit 100 can perform various processes of this embodiment based on data read from the programs (data) stored in the information storage medium 180.

[0138] For example, the information storage medium 180 is an optical disk (CD, DVD), a magneto-optical disk (MO), a magnetic disk, a hard disk, a flash memory such as a solid state drive, a magnetic tape, a memory (ROM), or a memory card.

[0139] The communication unit 196 performs various controls for communicating with the outside (for example, the terminal device 20 and the asset management server device 80), and its functions are composed of hardware such as various processors or communication ASICs, programs, etc.

[0140] The processing unit 100 performs various processes of this embodiment based on programs (data) stored in the storage unit 170 .

[0141] In addition, the processing unit 100 of this embodiment may read out programs and data stored in the information storage medium 180, temporarily store the read out programs and data in the memory unit 170, and perform processing based on the programs and data.

[0142] The processing unit 100 (processor) performs various processes using a main memory unit 171 in the memory unit 170 as a work area. The functions of the processing unit 100 can be realized by hardware such as various processors (CPU, DSP, etc.) or programs.

[0143] Specifically, the processing unit 100 includes a communication control unit 101 , an issuance target asset management unit 102 , a token issuance management unit 103 , a token registration management unit 104 , a timer management unit 110 , and an information providing unit 111 .

[0144] The communication control unit 101 establishes a communication line with the terminal device 20, the information-providing server device 30, and the like via the network, and communicates with them.

[0145] The issuance target asset management unit 102 works in conjunction with the communication control unit 101, and when it receives an instruction to issue an NFT for a given asset sent via the communication unit 196 from the terminal device 20 of the issuing user who wishes to issue an NFT, it identifies the asset and manages the status of the identified asset (i.e., the issuance target asset).

[0146] The token issuance management unit 103 issues an NFT that embodies the asset to be issued when the asset to be issued management unit 102 determines that the asset to be issued is in a tradable state based on the instructions of the user wishing to issue the asset.

[0147] The token registration management unit 104 encrypts the issued NFTs using distributed ledger technology such as blockchain technology and registers them in a distributed manner in multiple token registration DBs 50.

[0148] The timer management unit 110 has a function of measuring the current date and time and from a predetermined timing, and outputs the current time and the measurement result when the predetermined timing arrives.

[0149] The information providing unit 111 provides the relevant terminal device 20 with information that the NFT has been issued and registered in the token registration DB 50, as well as information on the access location (address) for accessing the registered NFT.

[0150] [3] Terminal Device Next, the terminal device 20 will be described with reference to Fig. 4. Fig. 4 is a functional block diagram showing an example of the configuration of the terminal device 20 of this embodiment.

[0151] 4, the terminal device 20 of this embodiment has a processing unit 200, a current position detection unit 250, an operation input unit 260 configured with a touch panel or the like, a storage unit 270, an information storage medium 280, a display unit 290 configured with a display element such as a liquid crystal panel, a communication unit 296, and a sound output unit 292. Note that the terminal device 20 does not need to include all of the units shown in FIG. 4, and may have a configuration in which some of them are omitted.

[0152] The current position detection unit 250 detects the current position of the terminal device 20 at each predetermined timing, and generates position information indicating the current position.

[0153] For example, the current position detection unit 250 detects the position of a GPS satellite (not shown) at predetermined intervals (for example, every 5 seconds) and detects satellite signals (GPS signals) transmitted from the GPS satellite.

[0154] Then, the current position detection unit 250 calculates (i.e., detects) the coordinate values ​​(e.g., latitude and longitude) of the current position of its own terminal device 20 based on the detected GPS signal, and provides the coordinate values ​​to the processing unit 200 as current position information.

[0155] In addition, the current position detection unit 250 may use Wi-Fi or mobile phone radio waves instead of or in addition to GPS signals to detect the coordinates of the current position or to correct the coordinates.

[0156] The operation input unit 260 is a device for inputting information input by the user, and outputs the user's input information to the processing unit 200 .

[0157] The operation input unit 260 of this embodiment includes a detection unit that detects input information (input signals) from the user, and is composed of, for example, a lever, buttons, a microphone, a touch panel display, a keyboard, a mouse, and the like.

[0158] The storage unit 270 serves as a work area for the processing unit 200 and the like, and its functions can be realized by hardware such as a RAM (VRAM).

[0159] The storage unit 270 of this embodiment includes a main storage unit 271 used as a work area, an image buffer 272 in which the final display image and the like are stored, and a user information storage unit 273 in which user information of the user who owns the terminal device 20 (hereinafter referred to as the "owner user") is stored. Note that some of these may be omitted.

[0160] The information storage medium 280 is computer-readable, and in addition to various applications and an OS (operating system), in this information storage medium 280, in particular, in this embodiment, various data including the user ID of the user corresponding to the terminal device 20 is stored.

[0161] That is, the information storage medium 280 stores applications for causing a computer to function as each unit of this embodiment (applications for causing a computer to execute the processing of each unit) and a user ID.

[0162] For example, the information storage medium 280 is an optical disk (CD, DVD), a magneto-optical disk (MO), a magnetic disk, a hard disk drive, a flash memory, a magnetic tape, a memory (ROM), a memory card, or the like.

[0163] The communication unit 296 performs various controls to communicate with the outside (for example, other terminal devices 20, token issuing server device 10, information providing server device 30, transaction management server device 40, and token registration DB 50), and its functions are composed of hardware such as various processors or communication ASICs, programs, etc.

[0164] The processing unit 200 can perform various processes of this embodiment by reading and executing the applications stored in the information storage medium 280. Note that the types of applications stored in the information storage medium 280 are arbitrary.

[0165] The processing unit 200 performs various processes of this embodiment based on the applications stored in the information storage medium 280. Note that the processing unit 200 of this embodiment may read out programs and data stored in the information storage medium 280, temporarily store the read out programs and data in the storage unit 270, and perform processing based on the programs and data.

[0166] The processing unit 200 (processor) performs various processes using the main memory in the memory unit 270 as a work area. The functions of the processing unit 200 can be realized by hardware such as various processors (CPU, DSP, etc.) or programs.

[0167] The processing unit 200 includes a communication control unit 210, a web browser 211, a current location management unit 212, a display control unit 213, an input reception processing unit 214, a wallet management unit 217, a timer management unit 218, a drawing unit 220, and a sound processing unit 230. Note that some of these units may be omitted.

[0168] The communication control unit 210 performs processing to send and receive data to and from the token issuing server device 10, the information providing server device 30, the transaction management server device 40, and the token registration DB 50.

[0169] In addition, the communication control unit 210 receives data transmitted from the token issuing server device 10, the information providing server device 30, the transaction management server device 40, and the token registration DB 50, and performs processes such as storing the received data in the memory unit 270, providing or registering given data, and controlling the transmission and reception of other data.

[0170] In addition, the communication control unit 210 may be configured to store and manage the destination information (IP address, port number) of the token issuing server device 10, the information providing server device 30, the transaction management server device 40, and the token registration DB 50 in the information storage medium 280.

[0171] The web browser 211 is an application program for viewing web pages (screens for issuing NFTs, screens for collected information related to assets to be issued and screens for provided token-related information), and downloads HTML files, image files, etc. from web servers (token issuing server device 10, information providing server device 30, transaction management server device 40 and token registration DB 50), analyzes the layout and controls the display.

[0172] In addition, the web browser 211 sends data to the web server (token issuing server device 10, information providing server device 30, and transaction management server device 40) using input forms (links, buttons, text boxes, etc.).

[0173] In addition, the terminal device 20 can display information from the web server (token issuing server device 10, information providing server device 30, and transaction management server device 40) specified by a URL via the Internet using the web browser 211.

[0174] For example, the terminal device 20 can display each content (data such as HTML) received from the token issuing server device 10, the information providing server device 30, and the transaction management server device 40 using the web browser 211.

[0175] The current location management unit 212 acquires current location information for each predetermined period from the current location detection unit 250 and stores it in the main storage unit 271 as history information.

[0176] The display control unit 213 performs processing for displaying on the display unit 290. For example, the display control unit 213 may use the web browser 211 for display.

[0177] The input reception processing unit 214 recognizes input information input by the user from the operation input unit 260, and executes various processes based on the recognized information.

[0178] The wallet management unit 217 works in conjunction with other terminal devices 20, the token issuance server device 10, the information provision server device 30, and the transaction management server device 40 to perform various processes related to the issuance or trading of NFTs.

[0179] In particular, when an NFT is issued and distributedly recorded on a specific platform such as a blockchain (i.e., when it is encrypted and distributedly registered on the token registration DB 50), the wallet management unit 217 is configured to store its address (network address) and to be able to access the user's NFT using that address.

[0180] The wallet management unit 217 has a unique wallet address and uses the wallet address and NFT to perform processing related to transactions (i.e., transactions) (specifically, signing and verifying transactions).

[0181] Specifically, the wallet management unit 217 generates a private key and a public key (which may be a wallet address) for the user, stores the private key, and provides the public key to the trading partner.

[0182] When executing an NFT transaction, the wallet management unit 217 uses the NFT (wallet address) to be traded, the private key, and the public key to perform processing to execute the NFT transaction after going through a given authentication process (signing and verifying the transaction) by the user.

[0183] The timer management unit 218 has a function of measuring the current date and time and from a predetermined timing, and outputs the current time and the measurement result when the predetermined timing arrives.

[0184] The drawing unit 220 performs drawing processing based on the various processes performed by the processing unit 200 , thereby generating an image, which is output to the display unit 290 by the display control unit 213 .

[0185] The sound processing unit 230 performs sound processing based on the results of various processes performed by the processing unit 200 , generates background music, sound effects, voices, etc., and outputs them to the sound output unit 292 .

[0186] [4] Information-Providing Server Device Next, the information-providing server device 30 will be described with reference to FIG. 5. Note that FIG. 5 is an example of a functional block diagram showing the configuration of the information-providing server device 30 according to the embodiment. Furthermore, part or all of the information-providing server device 30 according to the embodiment can be realized by an NFT virtual machine M, as shown in FIG. 2. However, in the following embodiment, unless otherwise specified, a case will be described in which part or all of the information-providing server device 30 is configured by hardware.

[0187] As shown in Fig. 5, the information-providing server device 30 of this embodiment includes a processing unit 300, a storage unit 370, an information storage medium 380, and a communication unit 396. Note that the information-providing server device 30 does not need to include all of the units shown in Fig. 5, and may have a configuration in which some of them are omitted.

[0188] The storage unit 370 has a main storage unit 371 and serves as a work area for the processing unit 300 and the like, and its function can be realized by hardware such as a RAM (VRAM).

[0189] The information storage medium 380 is computer-readable, and stores programs, data, and the like. That is, the information storage medium 380 stores programs for causing a computer to function as each unit of this embodiment (programs for causing a computer to execute the processing of each unit). The processing unit 300 can perform various processes of this embodiment based on data read from the programs (data) stored in the information storage medium 380.

[0190] For example, the information storage medium 380 is an optical disk (CD, DVD), a magneto-optical disk (MO), a magnetic disk, a hard disk, a flash memory such as a solid state drive, a magnetic tape, a memory (ROM), a memory card, or the like.

[0191] The communication unit 396 performs various controls for communication between the terminal device 20, the transaction management server device 40, the token registration DB 50, and the asset information management DB 60, and its functions are composed of hardware such as various processors or communication ASICs, programs, etc.

[0192] The processing unit 300 performs various processes of this embodiment based on programs (data) stored in the storage unit 370. Note that the processing unit 300 of this embodiment may read out programs and data stored in the information storage medium 380, temporarily store the read out programs and data in the storage unit 370, and perform processing based on the programs and data.

[0193] The processing unit 300 (processor) performs various processes using the main memory unit in the memory unit 370 as a work area. The functions of the processing unit 300 can be realized by hardware such as various processors (CPU, DSP, etc.) or by programs.

[0194] Specifically, the processing unit 300 includes a communication control unit 301 , an acquisition processing unit 302 , an information collection control unit 303 , a timer management unit 310 , and an information providing unit 311 .

[0195] The communication control unit 301 establishes communication lines with the terminal device 20, the transaction management server device 40, the asset information management DB 60, etc. via the network, and communicates with them.

[0196] The acquisition processing unit 302 acquires a provision instruction sent from the terminal device 20 of an information-requesting user who wishes to receive information regarding the asset to be issued, which instruction specifies the type of information related to the asset to be issued that should be collected from the asset information management DB 60 along with the token ID of the asset to be issued.

[0197] In particular, the acquisition processing unit 302 acquires a request to collect information on the NFT (hereinafter referred to as the "target NFT") from which information is to be collected, while referring to the corresponding De-Fi contract, and information on the target asset associated with the NFT (i.e., information related to the target asset).

[0198] The information collection control unit 303 collects issuance target asset related information from the asset information management DB 60 based on the token ID of the collection target NFT and the collection request received by the acquisition processing unit 302.

[0199] In addition, the information collection control unit 303 refers to the corresponding De-Fi contract based on the token ID of the NFT to be collected, and obtains information (i.e., token-related information) regarding the NFT to be collected that is registered in the token registration DB 50.

[0200] The timer management unit 310 has a function of measuring the current date and time and from a predetermined timing, and outputs the current time and the measurement result when the predetermined timing arrives.

[0201] The information providing unit 311 generates control information to be provided to users who wish to receive information based on the acquired NFT-related information and the collected information related to the assets to be issued, and provides the generated control information to the corresponding terminal device 20.

[0202] For example, the information providing unit 311 generates control information such as image control information that can be displayed on the terminal device 20, or notification control information that is notified to users who wish to receive information, and provides the generated control information to the terminal device 20 (including via the transaction management server device 40).

[0203] [5] Transaction Management Server Device Next, the transaction management server device 40 of this embodiment will be described using Figure 6. Note that Figure 6 is an example of a functional block diagram showing the configuration of the transaction management server device 40 of this embodiment. Furthermore, part or all of the transaction management server device 40 of this embodiment can be realized by an NFT virtual machine M, as shown in Figure 2. However, in the following embodiment, unless otherwise specified, the transaction management server device 40 will be described as being part or all configured by hardware.

[0204] As shown in Fig. 6, transaction management server device 40 of this embodiment includes a processing unit 400, a memory unit 470, an information storage medium 480, and a communication unit 496. Note that transaction management server device 40 does not need to include all of the units shown in Fig. 6, and may have a configuration in which some of them are omitted.

[0205] The storage unit 470 serves as a work area for the processing unit 400 and the like, and its function can be realized by hardware such as a RAM (VRAM).

[0206] Specifically, the memory unit 470 includes a main memory unit 471 used as a work area when executing various processes, and a registered user related information memory unit 472 in which information (hereinafter referred to as "registered user related information") relating to users registered with the electronic transaction service (hereinafter referred to as "registered users") is stored.

[0207] In particular, the registered user related information storage unit 472 may have information related to the wallet of each user. In other words, in this case, the registered user related information storage unit 472 may function as the wallet of each user. Note that the storage unit 470 of this embodiment may be configured to omit some of the components such as the main storage unit 471 and the registered user related information storage unit 472.

[0208] The information storage medium 480 is computer-readable and stores programs, data, and the like. That is, the information storage medium 480 stores programs for causing a computer to function as each unit of this embodiment (programs for causing a computer to execute the processing of each unit). The processing unit 400 can perform various processes of this embodiment based on data read from the programs (data) stored in the information storage medium 480.

[0209] For example, the information storage medium 480 is an optical disk (CD, DVD), a magneto-optical disk (MO), a magnetic disk, a hard disk, a flash memory such as a solid state drive, a magnetic tape, a memory (ROM), a memory card, or the like.

[0210] The communication unit 496 performs various controls to communicate with the outside (for example, the terminal device 20, the token issuing server device 10, the information providing server device 30, and the token registration DB 50), and its functions are composed of hardware such as various processors or communication ASICs, programs, etc.

[0211] The processing unit 400 performs various processes of this embodiment based on programs (data) stored in the storage unit 470. Note that the processing unit 400 of this embodiment may read out programs and data stored in the information storage medium 480, temporarily store the read out programs and data in the storage unit 470, and perform processing based on the programs and data.

[0212] The processing unit 400 (processor) performs various processes using a main memory unit 471 in the memory unit 470 as a work area. The functions of the processing unit 400 can be realized by hardware such as various processors (CPU, DSP, etc.) or programs.

[0213] Specifically, the processing unit 400 includes a communication control unit 401 , a transaction management control unit 402 , a registered user management control unit 403 , an approval processing unit 404 , an information collection control unit 405 , a timer management unit 410 , and an information provision unit 411 .

[0214] The communication control unit 401 establishes communication lines with the terminal device 20, the token issuing server device 10, the information providing server device 30, the token registration DB 50, and the like via the network, and communicates with them.

[0215] The transaction management control unit 402 works in conjunction with the terminal devices 20 of the NFT transaction destination and transaction source users (hereinafter collectively referred to as "transaction target users") to perform processing to manage transactions.

[0216] Specifically, the transaction management control unit 402, for example, manages NFTs from the source user, performs processing related to transactions with the destination user who wishes to transfer them, such as purchasing them (hereinafter referred to as "electronic transaction processing"), and performs various processes to make payment of the consideration when the transaction is completed.

[0217] In particular, when an electronic transaction of an NFT is executed, the transaction management control unit 402 identifies a De-Fi contract corresponding to the NFT that is the subject of the transaction, and executes the electronic transaction processing based on the identified De-Fi contract.

[0218] Then, the transaction management control unit 402 receives the results of the approval processing of the electronic transaction in the approval processing unit 404, and based on the received results, executes various processes after the transaction is completed or various processes related to the failure of the transaction.

[0219] The registered user management control unit 403 manages information on each registered user as a transaction target user. Specifically, the registered user management control unit 403 manages, for example, the registration and updating of information required when an NFT is transferred due to a sale or the like, and information required when purchasing the NFT, in the registered user related information storage unit 472.

[0220] When an electronic transaction of NFT is executed, the approval processing unit 404 executes approval processing to determine whether or not to approve the electronic transaction based on location information of the transaction source, the transaction destination, or both of the electronic transaction sources, the transaction destination, or both.

[0221] The information collection control unit 405 collects issuance target asset related information from the asset information management DB 60 based on the token ID of the target NFT and the collection request received by the transaction management control unit 402.

[0222] In addition, the information collection control unit 405 refers to the corresponding De-Fi contract based on the token ID of the NFT to be collected, and obtains information (i.e., token-related information) regarding the NFT to be collected that is registered in the token registration DB 50.

[0223] The timer management unit 410 has a function of measuring the current date and time and from a predetermined timing, and outputs the current time and the measurement result when the predetermined timing arrives.

[0224] The information providing unit 411 generates control information to be provided to users who wish to receive information based on the acquired NFT-related information and the collected information related to the asset to be issued.

[0225] For example, the information providing unit 311 provides various information when an electronic transaction is executed or when the electronic transaction is completed to the terminal device 20 of the transaction target user (the user from which the transaction originates or the user at the other end of the transaction).

[0226] [6] Method of this embodiment [6.1] NFT Next, we will explain NFTs circulating in the electronic transaction network system S, which is the premise of the method of this embodiment.

[0227] The NFT as a non-fungible token in this embodiment is data (token) that functions as the subject of various transactions such as electronic transactions within the NFT decentralized management platform, and is data that has non-fungible uniqueness and is used, for example, in cryptographic technology and distributed ledger technology such as blockchain technology, which processes and records transaction records in a decentralized manner.

[0228] Specifically, the NFT of this embodiment includes the following information: (A1) a token ID; (A2) information for identifying the holder of the NFT (i.e., the holder who holds the asset to be issued) (hereinafter referred to as "holder identification information"); and (A3) information on the location where the non-fungible token is electronically held (in the terminal device 20 or in the transaction management server device 40), such as the address of the wallet that holds the NFT (i.e., the wallet address, hereinafter also referred to as the "holder address").

[0229] In particular, the owner identification information includes, in addition to the owner address, information such as: (A2-1) the owner's name and title (including the owner ID and nickname indicating the user ID); (A2-2) information on the owner's place of residence, such as address and residence; (A2-3) information on the owner's attributes (age, generation, gender, nationality, etc.); and (A2-4) the owner's contact information (for example, email address, SNS (social network service) ID or telephone number).

[0230] In addition to the above, the token-related information of this embodiment may also specify information for identifying the asset to be issued (hereinafter referred to as "asset to be issued identification information"). The token-related information of this embodiment may not include all of the above (A1) to (A2).

[0231] Furthermore, the issuance target asset identification information may include information such as an image of the issuance target asset, such as an icon displayed on an image (hereinafter referred to as "image information"), and information regarding the price and payment of the NFT, such as payment history.

[0232] The token-related information, including the issuance target asset identification information, may all be specified in the NFT. Alternatively, the token-related information may be stored as metadata in association with a uniform resource identifier (URI) indicating a storage location (address) when stored in the token registration DB 50 or the like, and may be acquired by reading the information based on the URI.

[0233] [6.2] De-Fi Contract and Oracle Contract Next, we will explain the De-Fi Contract and Oracle Contract, which specify the constraints and processing details when circulating NFTs, which are the premise of the method of this embodiment.

[0234] (De-Fi Contract) The De-Fi contract of this embodiment is a program (transaction processing specification information) for constructing DApps that specifies various processes and restrictions for issuing NFTs, transactions (including, for example, contracts such as agreements on whether or not a transaction can be executed), providing various information such as tamper prevention and ownership rights, and managing and supporting NFTs in general, and that is automatically executed when a transaction or information provision is executed.

[0235] In other words, the De-Fi contract of this embodiment is a program for driving an NFT virtual machine M consisting of a terminal device 20, a transaction management server device 40, a token registration DB 50, or a combination of these, on an NFT decentralized management platform, for example, when an NFT transaction is executed or when NFT information provision is requested, and is a program for automatically executing transaction processing.

[0236] The De-Fi contracts of this embodiment are encrypted, distributed, and registered in each token registration DB 50, just like NFTs.

[0237] Specifically, the De-Fi contract of this embodiment specifies, as transaction processing specification information, the processing when an NFT transaction is executed on an NFT decentralized management platform that manages the distribution of NFTs that embody the assets to be issued (hereinafter also referred to as "transaction execution processing"), the processing when a request is made for information related to the assets to be issued that correspond to the relevant NFT (hereinafter referred to as "NFT-related information collection and provision processing"), or both.

[0238] For example, the De-Fi contract of this embodiment includes: (A1) information specifying an application that executes a process to determine whether or not a transaction can be executed based on transaction conditions indicating the conditions under which a transaction of the issuance target asset is executed (hereinafter also referred to as "application specification information"), and (A2) information specifying an application (e.g., an oracle contract) that executes a process to collect information to be provided to traders when a transaction of the issuance target asset is executed (hereinafter referred to as "information related to the issuance target asset") (i.e., application specification information).

[0239] For example, transaction conditions indicate conditions for determining whether or not a transaction can be carried out, such as the amount of the asset to be issued, the location in real space where the asset to be issued is located (location based on time), the storage condition of the asset to be issued in real space, and whether or not there is a certificate of authenticity or certification from a third-party institution.

[0240] (Oracle Contract) The oracle contract of this embodiment is a program that specifies various processes and constraints for linking with outside the NFT decentralized management platform when DApps are being executed based on the De-Fi contract.

[0241] In particular, the oracle contract of this embodiment specifies a process in which, based on instructions from DApps based on the De-Fi contract, the information providing server device 30 is queried for information related to the assets to be issued that correspond to the relevant NFT, and the necessary information is obtained from the asset information management DB 60 and provided to the DApps (i.e., the De-Fi contract).

[0242] [6.3] Information Related to the Asset to be Issued Next, we will explain the information related to the asset to be issued, which is information related to the asset to be issued corresponding to the NFT that is the premise of the method of this embodiment and is provided to users who wish to receive information and other users who are the target of transactions.

[0243] In this embodiment, the issuance target asset related information includes at least the following information (hereinafter referred to as "issue target asset basic information"). (A1) information indicating the type of the issuance target asset (including the type of physical or intangible asset), the asset name, price (including not only the current price but also various prices such as the reserve price and bid price in the case of an auction), or identification information of the issuance target asset such as a model number or certification number (hereinafter referred to as "asset ID"); (A2) if the issuance target asset is composed of multiple tangible or intangible assets of the same or different types, information on the number of such assets (if there are multiple types, the number of such assets for each type); and (A3) information on the attributes of the issuance target asset (if the issuance target asset is a physical asset, information on the manufacturer or manufacturer, the time or date of production of the issuance target asset, the time of production or location of production, raw materials, etc.). Note that the issuance target asset related information may also include issuance target asset identification information, as described above.

[0244] For example, the information related to the asset to be issued may include, in addition to the basic information on the asset to be issued, (B1) information related to the authenticity (genuineness) of the asset to be issued (hereinafter referred to as "genuineness information"), (B2) information related to the actual location of the asset to be issued in real space (which may include the time when the asset was at that location) (hereinafter referred to as "location-related information"), and (B3) information related to the storage of the asset to be issued (hereinafter referred to as "storage information").

[0245] For example, the authenticity information includes information indicating whether the asset to be issued is authentic, information regarding the appraiser of authenticity, such as the name of the appraiser who performed the appraisal, and information regarding the appraisal date and time when the appraisal was performed.

[0246] For example, the location-related information includes current location information indicating the current location of the asset to be issued (including the name of the area or building to identify the location), and information on the date and time when the current location information of the asset to be issued was obtained.

[0247] For example, the storage information includes information on the storage status of the asset to be issued (including the type of storage location), information on the storage period of the asset to be issued, etc. Note that the information related to the asset to be issued may include not only the above-mentioned various pieces of information at the time of the transaction, but also past information (i.e., history information).

[0248] In addition, among the issuance asset related information, basic information on the issuance target asset may be pre-registered in the issuance target asset information storage unit 173, or may be input via the terminal device 20 by the user who wishes to issue the NFT when the NFT is issued, or may be read from the terminal device 20.

[0249] [6.4] NFT Issuance Control Process Next, with reference to FIG. 7, an NFT issuance control process for issuing an NFT that embodies a user's assets, which is executed by the token issuing server device 10 as a method of this embodiment, will be described.

[0250] 7 is a diagram for explaining the NFT issuance control process for issuing an NFT embodied with a user's assets, which is executed by the token issuance server device 10 of this embodiment. In particular, FIG. 7 is a diagram for explaining the NFT issuance control process, which is part of the overall process related to the issuance of an NFT embodied with an asset to be issued in the electronic transaction network system S, the provision of information related to the NFT, and the transaction of the NFT.

[0251] (Outline of NFT issuance control process) The token issuance server device 10 of this embodiment is configured to issue unique NFTs that embody the assets to be issued, in order to treat tangible assets such as entities or rights that can be traded in the real world, or intangible assets, as equivalent assets on the network.

[0252] Specifically, as shown in FIG. 7 , the token issuance server device 10 of this embodiment performs the following NFT issuance control process: (A1) upon receiving an instruction to issue an NFT for a given asset (i.e., an issuance target asset) sent from the terminal device 20 of the issuing user who wishes to issue an NFT, (A2) acquires information on the issuance target asset for which an NFT is to be issued, as issuance target asset related information, from the terminal device 20 of the issuing user or the asset management server device 80 operated by a third party, (A3) executes a process (hereinafter referred to as the “token issuance process”) to issue an NFT that embodies the issuance target asset based on the received issuance instruction and the acquired issuance target asset related information, and (A4) executes a process (hereinafter referred to as the “registration control process”) to control the token registration DB 50 that registers the issued NFT while ensuring tamper-resistance, which exhibits characteristics to prevent tampering by unauthorized persons (i.e., persons without legitimate authority who are malicious third parties, such as “impersonators”). (A5) It is configured to execute a process (hereinafter referred to as "owner title information provision process") to provide the registered NFT to the terminal device 20 of the user wishing to issue it as information regarding the ownership rights indicating that the user wishing to issue it holds the registered NFT (hereinafter referred to as "owner title information", specifically, that the user is stored as the owner).

[0253] Then, as the token issuance process (A3), the token issuance server device 10 is configured to issue an NFT associated with a De-Fi contract stored in the token registration DB 50 when it acquires real-world management information indicating that the asset to be issued actually exists in real space and is managed so as to be tradable from an administrator (e.g., the asset management server device 80) who manages the asset to be issued in real space.

[0254] The De-Fi contract specifies: (B1) a token ID and token-related information; and (B2) at least one of the following processes: a process when a transaction of the NFT is executed and a process when a request is made for information on the issuance target asset associated with the NFT (i.e., information related to the issuance target asset).

[0255] The token issuance server device 10 of this embodiment has a configuration that allows it to issue NFTs that can be traded or provided as information by DApps executed by the NFT virtual machine M based on such a De-Fi contract. However, in this embodiment, as described above, each function of the token issuance server device 10 itself may be executed by DApps (i.e., the NFT virtual machine M) based on the De-Fi contract.

[0256] In addition, the token issuance server device 10 of this embodiment has a configuration in which, as a registration control process, the NFT is encrypted to ensure non-tampering, and the encrypted NFT is distributed and registered in multiple token registration DBs 50 on the network.

[0257] That is, the token issuing server device 10 of this embodiment has a configuration that uses a distributed ledger technology such as blockchain technology to perform distributed management while preventing tampering, rather than a centralized system.

[0258] With this configuration, the token issuance server device 10 of this embodiment can convert the assets to be issued into NFTs while ensuring the existence of the assets to be issued, as long as they are managed appropriately.Therefore, tangible assets such as physical objects or rights that can be traded in the real world, or intangible assets, can be treated as equivalent assets on the network.

[0259] In other words, the token issuance server device 10 of this embodiment can guarantee the existence and authenticity of assets that exist in the real world when they are converted into NFTs or when the assets are circulated as NFTs, and therefore can provide the assets as digital assets that are highly reliable, easy to handle, and transparent.

[0260] (Each process included in the NFT issuance control process) When the issuance target asset management unit 102 receives an instruction to issue an NFT sent from the terminal device 20 of the user wishing to issue the NFT, it works in conjunction with the terminal device 20 and, based on the issuance instruction, obtains the information necessary to issue the NFT, including information related to the asset to be issued.

[0261] For example, based on the received NFT issuance instruction, the issuance target asset management unit 102 obtains information such as: (C1) information about the user wishing to issue the NFT (information for registering the user as the issuer and original holder of the NFT); (C2) issuance target asset identification information for identifying the issuance target asset, such as the asset management server device 80 in which the issuance target asset is registered; (C3) information related to the NFT to be issued as an initial value; and (C4) issuance target asset related information as an initial value.

[0262] The token issuance management unit 103 executes a token issuance process to issue an NFT that embodies the asset to be issued, based on the received issuance instruction and the acquired information related to the asset to be issued.

[0263] In particular, the token issuance management unit 103 determines whether or not it has been able to obtain issuance target asset existence management information from the asset management server device 80, which is information regarding the management of the issuance target asset and indicates that the issuance target asset actually exists in real space.

[0264] Specifically, the token issuance management unit 103 queries the asset management server device 80 based on the acquired issuance target asset identification information, and in conjunction with the asset management server device 80, determines whether the asset can be issued as an NFT, such as whether the asset is registered and whether a corresponding NFT has yet to be issued.

[0265] For example, the token issuance management unit 103 acquires, as asset existence management information, the management status of the assets to be issued and information regarding the asset management server device 80 (contact information, manager, total number of assets to be issued, etc.).

[0266] In addition, the asset existence management information in this embodiment includes at least information indicating that the value of assets is preserved, such as that movable property is stored in a designated location while maintaining a designated condition, such as a warehouse, or that real estate or rights are publicly verifiable and properly managed, such as by registration or enrollment.

[0267] For this reason, the token issuance management unit 103 is able to use asset existence management information to determine that an asset actually exists in real space, even if it is an intangible asset such as a right, if it is shown to be in a state where it can be traded in real space through registration or other means.

[0268] When the token issuance management unit 103 determines that an NFT can be issued, it issues a new token ID and, based on the issued token ID and information such as issuance target asset identification information and issuance target asset related information, associates it with the corresponding De-Fi contract and executes a token issuance process to issue an NFT.

[0269] In other words, the token issuance management unit 103 issues an NFT that has a token ID and NFT-related information, is associated with a De-Fi contract, and specifies the processing to be performed when a transaction of the NFT is executed and the processing to be performed when information related to the asset to be issued is requested.

[0270] The token registration management unit 104 executes a registration control process in which the issued NFT is encrypted using blockchain technology (i.e., ensuring tamper-resistance, which is a characteristic for preventing tampering by unauthorized parties) and registered in each token registration DB 50 (in the case of an NFT virtual machine M, in the corresponding token registration DB 50).

[0271] The information providing unit 111 executes an owner title information providing process that provides information regarding ownership rights indicating that the registered NFT is held by the user wishing to issue the NFT to the terminal device 20 of the user wishing to issue the NFT as ownership rights information.

[0272] That is, the information providing unit 111 provides the terminal device 20 (specifically, the wallet) of the user desiring to issue information indicating that the issued NFT has been registered in the token registration DB 50. However, the information providing unit 111 may also register the information in association with the user desiring to register in the registered user related information storage unit 472 (that is, a database that functions as the wallet of the user desiring to register).

[0273] [6.5] NFT-related information collection and provision process Next, using Figures 8 to 10, we will explain the NFT-related information collection and provision process, which is a process executed by the information providing server device 30 as a method of this embodiment, and which collects and provides information about NFTs including information related to the assets to be issued (i.e., various types of NFT-related information).

[0274] 8 and 9 are diagrams for explaining the NFT-related information collecting and providing process executed by the information-providing server device 30 of this embodiment, which collects and provides information related to NFTs, including information related to assets to be issued. In particular, FIGS. 8 and 9 are diagrams for explaining the NFT-related information collecting and providing process, which is part of the overall process related to the issuance of NFTs embodied in assets to be issued, the provision of NFT-related information, and trading of NFTs in the electronic trading network system S of this embodiment. Also, FIG. 10 is a diagram showing an example of image information (an image generated in the terminal device 20 based on control information) for allowing a user to view the information related to assets to be issued, including token-related information acquired by the NFT-related information collecting and providing process in this embodiment.

[0275] (Overview of NFT-related information collection and provision process) The information provision server device 30 of this embodiment works in conjunction with an NFT virtual machine M composed of a transaction management server device 40, etc., and is configured to enable users wishing to receive information on issuance target assets for which they wish to receive information, and to enable users to receive the latest information on issuance target assets at the time of information provision, while also referring to information on non-fungible tokens.

[0276] The information-providing server device 30 is configured to collect issuance-target asset-related information regarding the issuance-target asset when electronic transactions can be carried out on the network for the issuance-target asset that is the subject of the issuance of the NFT using an NFT that embodies the asset held by the user (i.e., the issuance-target asset).

[0277] In particular, the information-providing server device 30 of this embodiment is configured to collect issuance target asset related information in conjunction with an asset information management DB 60 in which issuance target asset related information is registered for each issuance target asset in association with the token ID of the NFT in which the issuance target asset is embodied, or is updated and registered at a given time after the issuance of the NFT.

[0278] In addition, when executing the NFT-related information collection and provision process, the information providing server device 30 of this embodiment is configured to search for issuance target asset-related information stored in the asset information management DB 60 while working in conjunction with DApps executed based on a De-Fi contract including an Oracle contract.

[0279] Specifically, as shown in FIG. 8, the information providing server device 30 of this embodiment has the following configuration as an NFT-related information collection and provision process: (A1) upon receiving a provision instruction transmitted from the terminal device of an information-desiring user who wishes to receive information related to an issuance target asset, the instruction specifying the type of issuance target asset related information to be collected from the asset information management DB 60 along with the token ID of the issuance target asset; (A2) executing a process (hereinafter referred to as "information collection process") to collect the relevant issuance target asset related information from the information stored in the asset information management DB 60 based on the acquired token ID and the specified type of issuance target asset related information; and (A3) executing a process to provide the collected issuance target asset related information to the terminal device 20 of the relevant information-desiring user as an issuance target asset related information provision control process.

[0280] The information providing server device 30 of this embodiment is configured to identify the issuance target asset related information to be collected in conjunction with DApps based on the De-Fi contract stored in the token registration DB 50 as the collection information identification process (A1).

[0281] As described above, the De-Fi contract specifies: (B1) a token ID and token-related information; and (B2) at least one of the following processes: a process when a transaction of the NFT is executed and a process when a request is made for information on the issuance target asset associated with the NFT (i.e., information related to the issuance target asset).

[0282] The information-providing server device 30 of this embodiment is configured to execute each of the above processes in conjunction with DApps executed by an NFT virtual machine M based on such a De-Fi contract.

[0283] With this configuration, the information-providing server device 30 of this embodiment can not only provide accurate and ample information regarding NFTs and the assets to be issued, but also improve the trading environment for the assets to be issued via the NFTs, and can certify the authenticity of the NFTs and their appropriate value.

[0284] Therefore, the information-providing server device 30 of this embodiment eliminates the need to register accurate and large amounts of information when managing NFTs, and to constantly update the registered information, thereby reducing processing speed and approval delays that arise from the increased amount of data that must be stored due to distributed ledger technologies such as blockchain technology.

[0285] On the other hand, the NFT virtual machine M, which works in conjunction with the information-providing server device 30 and cooperates with the NFT-related information collection and provision process, is a virtual machine constructed by DApps that provides issuance-related information collected by the information-providing server device 30 to users who wish to receive information.

[0286] In particular, the NFT virtual machine M is configured to provide the collected information related to the assets to be issued to the users who wish to receive the information.

[0287] Furthermore, as described above, the NFT virtual machine M is configured to link with an asset information management DB 60 in which information related to the assets to be issued is registered in association with the previous token ID for each asset to be issued, or is updated and registered at a given time after the issuance of the non-fungible token.

[0288] Specifically, as shown in FIG. 9, the NFT virtual machine M has the following configuration: (C1) upon receiving a provision instruction sent from the terminal device 20 of a user wishing to receive information together with the token ID of the asset to be issued, (C2) based on the received token ID, identifies the type of information related to the asset to be issued that should be collected from the asset information management DB 60, (C3) acquires the information related to the asset to be issued that has been identified and collected based on the identified type of information related to the asset to be issued and the received token ID, and (C4) provides the acquired information related to the asset to be issued to the terminal device 20 of the user wishing to receive information.

[0289] With this configuration, the NFT virtual machine M can receive information on the issuance assets for which the user wishing to provide information wishes to receive information, and can also receive the latest information on the issuance assets at the time of information provision while also referencing the NFT information.This not only makes it possible to provide accurate and extensive information, but also improves the trading environment for issuance assets via NFTs and proves the authenticity and appropriate value of the non-fungible token.

[0290] Therefore, the NFT virtual machine M eliminates the need to register a large amount of information and constantly update the registered information when managing NFTs, and can reduce processing speeds and approval delays that arise from the increased amount of data that must be stored due to distributed ledger technologies such as blockchain technology.

[0291] (Processes included in the NFT-related information collection and provision process) When the acquisition processing unit 302 acquires an information collection instruction sent from the NFT virtual machine M to DApps executed based on the De-Fi contract, it acquires the NFT token ID embodied in the issuance target asset that is the subject of information collection provided together with the information collection instruction, and the type of issuance target asset information.

[0292] The information collection control unit 303 executes an information collection process to collect the relevant issuance target asset related information from the information stored in the asset information management DB 60 based on the acquired token ID and the type of issuance target asset related information.

[0293] At this time, the information collection control unit 303 may collect the relevant issuance target asset related information in cooperation with the asset management server device 80 and wait for the asset management server device 80 to collect and register the information.

[0294] The information providing unit 311 executes an issuance target asset related information providing control process for providing the collected issuance target asset related information to the NFT virtual machine M.

[0295] In particular, the information providing unit 311 executes control to provide the collected issuance target asset related information to the terminal device 20 of the user who desires to receive the information via the NFT virtual machine M.

[0296] Specifically, the information providing unit 311 provides the NFT virtual machine M with information necessary to generate image control information that can be displayed on the terminal device 20 of the user who desires to receive the information.

[0297] (Processing of the NFT virtual machine linked to the NFT-related information collection and provision process) When the NFT virtual machine M receives a request for information provision (hereinafter referred to as an "information provision request") from the terminal device 20 of an information-desiring user who wishes to receive information about a specific issuance target asset (i.e., issuance target asset related information) along with the token ID of the NFT corresponding to the issuance target asset that is the subject of the NFT-related information collection and provision process, the NFT virtual machine M identifies the issuance target asset related information to be acquired (i.e., the type of issuance target asset related information) that corresponds to the issuance target asset that is the subject of the information provision request (hereinafter referred to as the "specific issuance target asset") based on the token ID.

[0298] For example, the NFT virtual machine M identifies one or more of the following types of information related to the asset to be issued: current price, past price history, storage location or manager, storage status or registration status (if the asset to be issued is an intangible asset such as data), and authenticity determination results (certificate, etc.).

[0299] Then, the NFT virtual machine M, while referring to the oracle contract, provides the information-providing server device 30 with the token ID and the type of issuance target asset information, and sends an instruction (hereinafter referred to as an "information collection instruction") to execute the collection of specific issuance target asset information.

[0300] On the other hand, when the NFT virtual machine M acquires the issuance target asset related information collected by the information-providing server device 30, it acquires token related information based on the corresponding token ID.

[0301] That is, the NFT virtual machine M acquires token-related information about the NFT based on the token ID of the NFT that is the subject of the transaction, generates control information to be recognized by users who wish to receive information based on the acquired token-related information and the collected information related to the asset to be issued, and provides the generated control information to the relevant terminal device 20.

[0302] In particular, the NFT virtual machine M generates control information to be recognized by users who wish to receive information based on the acquired information related to the asset to be issued and the token related information and a specified format.

[0303] For example, the NFT virtual machine M generates image control information (i.e., information for imaging) that can be displayed by the terminal device 20 of the user wishing to receive information, as shown in Figure 10, and provides the generated control information to the corresponding terminal device 20.

[0304] Note that the control information of the NFT virtual machine M may be sound output control information for outputting sound instead of image control information.

[0305] [7] Operation in this embodiment [7.1] NFT issuance control process Next, the operation of the NFT issuance control process executed by the token issuance server device 10 of this embodiment will be described with reference to Fig. 11. Fig. 11 is a flowchart showing the operation of the NFT issuance control process executed by the token issuance server device 10 of this embodiment.

[0306] This operation is performed on the premise that the issuance target asset for which the NFT is to be issued has been transitioned in advance by the issuing user who wishes to issue an NFT to a state where it is managed by an asset manager, and that information on the issuance target asset (i.e., information related to the issuance target asset) has been newly registered in the asset management server device 80 operated by the business operator (third party) who is the asset manager.

[0307] Furthermore, this operation is realized by the token issuance server device 10, but can also be realized by the NFT virtual machine M. Note that the NFT issuance information storage unit 172 is assumed to store in advance the history of issued token IDs and the like.

[0308] First, when the issuance target asset management unit 102 receives an instruction to issue an NFT sent from the terminal device 20 of the user wishing to issue it (step S101), it works in conjunction with the terminal device 20 and, based on the issuance instruction, obtains the information necessary to issue the NFT, including information related to the issuance target asset (step S102).

[0309] Next, the token issuance management unit 103 queries the asset management server device 80 based on the issuance target asset identification information, and in conjunction with the asset management server device 80, determines whether the asset can be issued, based on whether the corresponding asset is registered and whether a corresponding NFT has yet to be issued (step S103).

[0310] At this time, if the token issuance management unit 103 determines that an NFT cannot be issued because the asset to be issued is not registered, for example (if it determines that the asset existence management information to be issued cannot be obtained), it terminates this operation, and if it determines that the NFT can be issued (if it determines that the asset existence management information to be issued has been obtained), it proceeds to processing in step S104.

[0311] Next, the token issuance management unit 103 issues a new token ID (step S104), and executes a token issuance process to issue an NFT while associating it with the corresponding De-Fi contract based on the issued token ID and the information identified in the processing of step S102, such as the issuance target asset identification information and issuance target asset related information (step S105).

[0312] Next, the token registration management unit 104 executes a registration control process to encrypt the issued NFT using blockchain technology (i.e., to ensure tamper-resistance, which is a characteristic that prevents tampering by unauthorized parties) and distribute and register it in each token registration DB 50 (step S106).

[0313] Finally, the information providing unit 111 executes an owner title information providing process to provide information regarding ownership rights indicating that the registered NFT is held by the user wishing to issue the NFT as ownership rights information to the terminal device 20 of the user wishing to issue the NFT (step S107), and then terminates this operation.

[0314] [7.2] NFT-related information collection and provision process Next, the operation of the NFT-related information collection and provision process executed by the information-providing server device 30 of this embodiment will be described with reference to Figures 12 and 13. Figures 12 and 13 are flowcharts showing the operation of the NFT-related information collection and provision process executed by the information-providing server device 30 of this embodiment.

[0315] This operation assumes that the information related to the asset to be issued in the target NFT stored in the asset information management DB 60 has been updated as appropriate.

[0316] This operation is executed in conjunction with an NFT virtual machine (i.e., node) M that executes DApps based on a De-Fi contract while referencing an oracle contract, and this operation will be described together with the operation of the NFT virtual machine M. However, the NFT-related information collection and provision process can also be realized by the NFT virtual machine M.

[0317] First, when the NFT virtual machine M receives a request for information provision (hereinafter referred to as an "information provision request") from the terminal device 20 of an information-requesting user who wishes to receive information about a specific issuance target asset (i.e., information related to the issuance target asset) along with the token ID for the target NFT (step S201), it identifies the issuance target asset that is the subject of the information provision request as a specific issuance target asset based on the token ID (step S202).

[0318] Next, the NFT virtual machine M starts executing the NFT-related information collection and provision process for the specific issuance target asset (step S203).

[0319] First, when the NFT virtual machine M starts executing the NFT-related information collection and provision process, it identifies the issuance target asset related information (i.e., the type of issuance target asset related information) to be obtained for the specific issuance target asset (step S204).

[0320] For example, the NFT virtual machine M identifies one or more of the following types of information related to the asset to be issued: current price, past price history, storage location or manager, storage status or registration status (if the asset to be issued is an intangible asset such as data), and authenticity determination results (certificate, etc.).

[0321] Next, the NFT virtual machine M, while referring to the oracle contract, provides the information-providing server device 30 with the token ID and the type of issuance target asset information, and sends an instruction (hereinafter referred to as an "information collection instruction") to execute collection of specific issuance target asset information (step S205), and waits to receive the collected issuance target asset related information.

[0322] Meanwhile, in the information-providing server device 30, when the acquisition processing unit 302 acquires an information collection instruction sent from the NFT virtual machine M (step S301), it acquires the NFT token ID embodied in the issuance target asset that is the subject of information collection provided together with the information collection instruction, and the type of issuance target asset information (step S302).

[0323] Next, the information collection control unit 303 executes an information collection process to collect the relevant issuance target asset related information from the information stored in the asset information management DB 60 based on the acquired token ID and the type of issuance target asset related information (step S303).

[0324] Next, the information providing unit 311 executes an issuance target asset related information providing process to provide the collected issuance target asset related information to the NFT virtual machine M of the corresponding information-receiving user (step S304), and terminates this operation in the information providing server device 30.

[0325] On the other hand, when the NFT virtual machine M acquires the issuance target asset related information collected by the information-providing server device 30 (step S206), it acquires token-related information based on the corresponding token ID (step S207).

[0326] Next, the NFT virtual machine M generates control information to be recognized by the user who wishes to receive information based on the acquired issuance target asset related information and token related information and a predetermined format (step S208).

[0327] Finally, the NFT virtual machine M provides the generated control information to the corresponding terminal device 20 (step S209), and ends this operation.

[0328] [8] Modifications [8.1] Modification 1 (NFT transaction execution control processing) [8.1.1] Overview of Modification 1 Next, using Figure 14, we will explain the NFT transaction execution control processing, including the NFT-related information collection and provision processing executed by the transaction management server device 40 of the above embodiment.

[0329] FIG. 14 is a diagram for explaining the NFT transaction execution control process, including the NFT-related information collection and provision process, executed by the transaction management server device 40 of this embodiment.

[0330] This modified example is basically an embodiment in which the NFT-related information collection and provision process executed by the above-mentioned information provision server device 30 is executed when the NFT transaction execution control process is executed, and other features are the same as those of the above-mentioned embodiment.

[0331] In the following description, unless otherwise specified, the transaction management server device 40 is used alone. However, as described above, the transaction management server device 40 of this modified example can also be implemented by the NFT virtual machine M.

[0332] [8.1.2] NFT Transaction Execution Control Processing Next, using Figure 14, we will explain the NFT transaction execution control processing for executing NFT transactions, including the NFT-related information collection and provision processing, which is executed by the transaction management server device 40 of this modified example.

[0333] 14 is a diagram for explaining the NFT transaction execution control process for executing NFT transactions, including the NFT-related information collection and provision process, which is executed by the transaction management server device 40 of this embodiment. In particular, FIG. 14 is a diagram for explaining the NFT transaction execution control process for executing NFT transactions, including the NFT-related information collection and provision process, which is part of the overall process related to the issuance of NFTs embodied in assets to be issued in the electronic transaction network system S, the provision of the NFT-related information, and the transaction of the NFT.

[0334] The transaction management server device 40 is configured to use NFTs that embody assets held by users (i.e., assets to be issued) to execute electronic transactions of the assets to be issued on a network.

[0335] In particular, the transaction management server device 40 has a configuration that executes NFT-related information collection and provision processing when executing an NFT transaction, similar to the information provision server device 30 in the above embodiment.

[0336] In addition, similar to the information-providing server device 30, the transaction management server device 40 of this embodiment has a configuration in which information related to assets to be issued is registered for each asset to be issued in association with the token ID of the NFT in which the asset to be issued is embodied, or is updated and registered at a given time after the issuance of the NFT, and collects information related to assets to be issued in conjunction with an asset information management DB 60.

[0337] Specifically, as shown in FIG. 14 , the transaction management server device 40 is configured to perform the following NFT-related information collection and provision processes: (A1) a process for executing an electronic transaction based on a De-Fi contract that specifies a given process for executing an NFT electronic transaction and that is stored in the token registration DB 50 (hereinafter referred to as the "electronic transaction process"); (A2) a process for updating and registering the non-fungible token in a registration management database based on the result of the transaction while ensuring tamper-resistance, which indicates a characteristic for preventing tampering by unauthorized parties (hereinafter referred to as the "NFT update registration process"); (A3) a control process for collecting issuance asset-related information regarding the issuance asset of the relevant NFT based on the identified De-Fi contract when executing an electronic transaction (hereinafter referred to as the "NFT-related information collection control process"); and (A4) a process for providing the collected issuance asset-related information to the relevant terminal device 20 (hereinafter referred to as the "issuance asset-related information provision process").

[0338] The transaction management server device 40 of this embodiment has a configuration as the NFT-related information collection control process (A4) as follows: (A3-1) based on the identified De-Fi contract, identify the type of issuance target asset related information to be collected from the asset information management DB 60; and (A3-2) based on the identified type of issuance target asset related information, collect the corresponding issuance target asset related information from the information stored in the asset information management DB 60.

[0339] The transaction management server device 40 of this embodiment has a configuration that allows it to execute various processes, such as transactions or information provision, using DApps executed by the NFT virtual machine M based on such a De-Fi contract. However, in this embodiment, as described above, each function of the transaction management server device 40 itself may be executed by DApps (i.e., the NFT virtual machine M) based on the De-Fi contract, or some of the functions may be executed by the DApps.

[0340] With this configuration, the transaction management server device 40 of this embodiment can receive information on the issuance target assets for which the transaction user executing the NFT transaction wishes to receive information, and can also provide the latest information on the issuance target assets at the time of the transaction while also referencing the NFT information.This not only makes it possible to provide accurate and extensive information, but also improves the trading environment for issuance target assets via non-fungible tokens and proves the authenticity and appropriate value of the non-fungible tokens.

[0341] Furthermore, the transaction management server device 40 of this embodiment eliminates the need to register a large amount of information and constantly update registered information when managing NFTs, and can reduce processing speeds and approval delays that arise from the increased amount of data that must be stored due to distributed ledger technologies such as blockchain technology.

[0342] [8.1.3] NFT Transaction Execution Control Processing Next, the operation of the NFT transaction execution control processing executed by the transaction management server device 40 of this embodiment will be described with reference to Figures 15 and 16. Figures 15 and 16 are flowcharts showing the operation of the NFT transaction execution control processing executed by the transaction management server device 40 of this embodiment.

[0343] This operation includes the operation of the NFT-related information collection and provision process, and the collection of NFT-related information in this operation is basically the same as the NFT-related information collection and provision process described above. Furthermore, in this operation, as with the NFT-related information collection and provision process, it is assumed that the issuance target asset-related information for the target NFT stored in the asset information management DB 60 is updated as appropriate. This operation is implemented by the transaction management server device 40, but can also be implemented by the NFT virtual machine M.

[0344] First, when the transaction management control unit 402 receives a transaction start instruction from a user who wishes to conduct a transaction (step S401), it works in conjunction with the corresponding terminal device 20 to identify the information necessary to execute the transaction, such as identifying the user who wishes to conduct a transaction based on the user ID and identifying the NFT to be traded based on the token ID (step S402).

[0345] Next, the transaction management control unit 402 determines whether to start executing the transaction based on the identified information, the De-Fi contract that identifies the processing for executing the transaction, including restrictions and regulations related to the transaction, and the user's operational instructions (step S403).

[0346] At this time, if the transaction management control unit 402 determines that an NFT transaction is to be executed, it proceeds to processing of step S403, and if it determines that an NFT transaction is not to be executed, it proceeds to processing of step S411.

[0347] Next, if it is determined that an NFT transaction is to be carried out, the approval processing unit 404 performs identity authentication of the user wishing to transact (step S404) and determines the result (step S405).

[0348] Next, if the personal authentication is successful, the transaction management control unit 402 executes processing related to the transaction (step S406) and terminates this operation, and if the personal authentication is not successful, the transaction management control unit 402 proceeds to the processing of step S403. However, if the personal authentication is not successful, the transaction management control unit 402 may terminate this operation.

[0349] On the other hand, if the transaction management control unit 402 determines not to execute an NFT transaction, it determines whether or not to execute an NFT-related information collection and provision process (step S411). At this time, if the transaction management control unit 402 determines to execute an NFT-related information collection and provision process, it proceeds to the process of step S412, and if it does not determine to execute an NFT-related information collection and provision process, it proceeds to the process of step S420.

[0350] Next, if the transaction management control unit 402 does not determine to execute the NFT-related information collection and provision process, it determines whether to terminate this operation (step S420), and if it determines to terminate this operation, it terminates this operation, and if it determines not to terminate this operation, it proceeds to processing in step S403.

[0351] On the other hand, if it is determined that the NFT-related information collection and provision process should be executed, the information collection control unit 405 identifies the issuance target asset that is the subject of the information provision request as a specific issuance target asset based on the token ID in the target NFT, and starts the NFT-related information collection and provision process for the specific issuance target asset (step S421).

[0352] Next, when the information collection control unit 405 starts executing the NFT-related information collection and provision process, it identifies the issuance target asset related information (i.e., the type of issuance target asset related information) to be obtained for the specific issuance target asset (step S422).

[0353] Next, the information collection control unit 405 executes an information collection process to collect the relevant issuance target asset related information from the information stored in the asset information management DB 60 based on the token ID and the type of issuance target asset related information (step S423).

[0354] Finally, the information providing unit 411 provides the generated control information to the corresponding terminal device 20 (step S424), and the process proceeds to step S403.

[0355] [8.2] Modification 2 (Modification of Token Issuance Server Device) Next, modification 2 of this embodiment will be described.

[0356] This modification is a modification in which the NFT-related information collection and provision process is executed in the token issuing server device 10 of the above embodiment, and other features are the same as those of the above embodiment.

[0357] That is, the token issuing server device 10 of this modified example has a configuration for executing the NFT-related information collection and provision process in addition to the above configuration.

[0358] Specifically, in addition to the above configuration, the token issuance server device 10 of this modified example has a configuration in which, (A1) upon receiving a provision instruction sent from the terminal device 20 of an information-desiring user who wishes to receive information on an asset to be issued, the instruction specifies the type of information related to the asset to be issued that should be collected from the asset information management DB 60 along with the token ID of the asset to be issued, and (A2) executes an information collection process to collect the relevant information related to the asset to be issued from the information stored in the asset information management DB 60 based on the acquired token ID and the specified type of information related to the asset to be issued.

[0359] The token issuing server device 10 is configured to execute an issuance target asset related information providing process that provides the collected issuance target asset related information to the terminal device 20 of the corresponding information-requesting user.

[0360] That is, the token issuance server device 10 may have the following configuration: (B1) assuming that issuance target asset related information is registered in the asset information management DB 60 in association with a token ID for each issuance target asset, or is updated and registered at a given timing after the issuance of an NFT; (B2) acquires a provision instruction sent from the terminal device 20 of an information-desiring user who wishes to be provided with issuance target asset related information, the instruction specifying the type of issuance target asset related information to be collected from the token registration DB 50 along with the token ID of the issuance target asset; (B3) collects the relevant issuance target asset related information from the information stored in the asset information management DB 60 based on the acquired token ID and the specified type of issuance target asset related information; and (B4) provides the collected issuance target asset related information to the relevant terminal device 20.

[0361] In this case, the token issuing server device 10 may be configured by an NFT virtual machine M, or may be configured by one or more server devices, or a combination of a server device and an NFT virtual machine M.

[0362] [9] Others One embodiment of the present invention is not limited to the above-described embodiment, and various modifications are possible. For example, terms cited in the description of the specification or drawings as broadly defined or synonymous can be replaced with broadly defined or synonymous terms in other descriptions of the specification or drawings.

[0363] An embodiment of the present invention includes a configuration that is substantially the same as the configuration described in the embodiment (for example, a configuration with the same function, method, and result, or a configuration with the same purpose and effect). An embodiment of the present invention also includes a configuration in which non-essential parts of the configuration described in the embodiment are replaced. An embodiment of the present invention also includes a configuration that achieves the same action and effect as the configuration described in the embodiment, or a configuration that can achieve the same purpose. An embodiment of the present invention also includes a configuration in which publicly known technology is added to the configuration described in the embodiment.

[0364] Although the embodiments of the present invention have been described in detail as above, it will be readily apparent to those skilled in the art that many modifications can be made without substantially departing from the novel features and effects of the present invention. Therefore, all such modifications are intended to be included within the scope of the present invention.

[0365] M: NFT virtual machine, S: electronic transaction network system, 10: token issuing server device, 20: terminal device, 30: information providing server device, 40: transaction management server device, 50: token registration DB, 60: asset information management DB, 80: asset management server device, 100: processing unit, 101: communication control unit, 102: issuance target asset management unit, 103: token issuance management unit, 104: token Registration management unit, 110: timer management unit, 111: information provision unit, 170: memory unit, 171: main memory unit, 172: NFT issuance information memory unit, 173: issuance target asset information memory unit, 180: information storage medium, 196: communication unit, 200: processing unit, 210: communication control unit, 211: web browser, 212: current location management unit, 213: display control unit, 214: input reception processing unit, 217: wallet management unit, 218: Timer management unit, 220: drawing unit, 230: sound processing unit, 250: current position detection unit, 260: operation input unit, 270: storage unit, 271: main storage unit, 272: image buffer, 273: owner user information storage unit, 280: information storage medium, 290: display unit, 292: sound output unit, 296: communication unit, 300: processing unit, 301: communication control unit, 302: acquisition processing unit, 303: information collection control unit, 310: timer management unit, 3 11: Information providing unit, 370: Memory unit, 380: Information storage medium, 396: Communication unit, 400: Processing unit, 401: Communication control unit, 402: Transaction management control unit, 403: Registered user management control unit, 404: Approval processing unit, 405: Information collection control unit, 410: Timer management unit, 411: Information providing unit, 470: Memory unit, 471: Main memory unit, 472: Registered user related information storage unit, 480: Information storage medium, 496: Communication unit

Claims

1. A token issuance management system that issues non-fungible tokens to be used for electronic transactions on a network for assets held by users, comprising: a receiving means for receiving an instruction to issue a non-fungible token for a given asset, the instruction being sent from a terminal device of a user wishing to issue the non-fungible token; an acquiring means for acquiring information on the target asset for which the non-fungible token is to be issued, as target asset related information, from the terminal device of the user wishing to issue the non-fungible token or from an information system operated by an administrator that manages the assets in real space; a token issuing means for issuing a non-fungible token that embodies the target asset based on the received issuance instruction and the acquired target asset related information; a registration control means for controlling a registration management database that registers the issued non-fungible token while ensuring tamper-resistance, which indicates a characteristic for preventing tampering by unauthorized persons; and a providing means for providing information on ownership title indicating that the registered non-fungible token is held by the user wishing to issue the non-fungible token, to the terminal device of the user wishing to issue the non-fungible token, as ownership title information, A token issuance management system characterized in that, when acquiring from the information system real-world management information indicating that the asset to be issued actually exists in real space and is managed so as to be tradable, the system issues the non-fungible token, which has a token ID for identifying the non-fungible token and token-related information regarding the non-fungible token, and which specifies at least one of processing when a transaction of the non-fungible token is executed and processing when provision of information related to the corresponding asset to be issued is requested, and which is associated with transaction processing specification information stored in a given storage medium or a given storage means.

2. A token issuance management system as described in claim 1, wherein the token issuing means issues the non-fungible token associated with at least one of the following application specification information as the transaction processing specification information: information specifying a transaction execution application for executing the transaction based on the transaction conditions for the transaction of the asset to be issued, and information specifying an information acquisition application for acquiring information related to the asset to be issued, which indicates information to be provided to the transaction target user when the asset to be issued is traded.

3. A token issuance management system as described in claim 1, wherein the issuance target asset related information is registered in an information management database in association with a token ID for identifying the non-fungible token for each of the issuance target assets, or is updated and registered at a given timing after the issuance of the non-fungible token; and further comprising: an acquisition means for acquiring a provision instruction transmitted from a terminal device of an information providing user who wishes to receive information related to the issuance target asset, the instruction specifying the type of the issuance target asset related information to be collected from the information management database along with the token ID of the issuance target asset; and a collection means for collecting relevant issuance target asset related information from information stored in the information management database based on the acquired token ID and the specified type of issuance target asset related information; and wherein the provision means provides the collected issuance target asset related information to the relevant terminal device.

4. A token issuance management system according to claim 1, wherein the registration control means encrypts the non-fungible token to ensure the non-tampering property, and distributes and registers the encrypted non-fungible token in a plurality of the registration management databases on the network.

5. A non-fungible token issuance method for issuing non-fungible tokens to be used for electronic transactions on a network for assets held by a user, comprising: receiving an instruction to issue a non-fungible token for a given asset, transmitted from a terminal device of a user wishing to issue the non-fungible token; obtaining information on the target asset for which the non-fungible token is to be issued, as target asset related information, from the terminal device of the user wishing to issue the non-fungible token or from an information system operated by an administrator who manages the asset in real space; issuing a non-fungible token that embodies the target asset based on the received issuance instruction and the obtained target asset related information; controlling a registration management database that registers the issued non-fungible token while ensuring tamper-resistance, which exhibits characteristics to prevent tampering by unauthorized parties; providing information on ownership rights indicating that the registered non-fungible token is held by the user wishing to issue the non-fungible token, to the terminal device of the user wishing to issue the non-fungible token, as ownership rights information; and when actual presence management information indicating that the target asset actually exists in real space and is managed so as to be tradable is obtained from the information system, A non-fungible token issuance method comprising: issuing a non-fungible token having a token ID for identifying the non-fungible token and token-related information relating to the non-fungible token, wherein at least one of processing when a transaction of the non-fungible token is executed and processing when provision of information related to the corresponding asset to be issued is requested is specified, and wherein the non-fungible token is associated with transaction processing specification information stored in a given storage medium or a given storage means.

6. An information collection system for collecting issuance asset related information relating to an issuance asset for which a non-fungible token is issued, when electronic transactions on a network for the issuance asset for which a non-fungible token is issued can be executed using a non-fungible token that embodies an asset held by a user, the issuance asset related information being registered in an information management database for each issuance asset in association with a token ID for identifying the non-fungible token, or being updated and registered at a given timing after the issuance of the non-fungible token, the information collection system comprising: acquisition means for acquiring a provision instruction transmitted from a terminal device of an information providing user who wishes to receive information on the issuance asset, the instruction specifying the type of issuance asset related information to be collected from the information management database along with the token ID of the issuance asset; collection means for collecting relevant issuance asset related information from information stored in the information management database based on the acquired token ID and the specified type of issuance asset related information; and provision control means for executing a process to provide the collected issuance asset related information to the relevant terminal device as a provision control process, the collection means An information collection system characterized by identifying the issuance target asset related information to be collected by referring to a token ID for identifying the non-fungible token and token related information related to the non-fungible token, which are specified for the non-fungible token corresponding to the issuance target asset related information to be collected, and transaction processing specification information that specifies at least one of the processing when a transaction of the non-fungible token is executed and the processing when provision of the corresponding issuance target asset related information is requested, and that is stored in a given storage medium or a given storage means.

7. An information collection system as described in claim 6, wherein the transaction processing specification information includes at least one of application specification information: information specifying a transaction execution application for executing the transaction based on the transaction conditions for the transaction of the issuance target asset, and information specifying an information acquisition application for acquiring issuance target asset related information indicating information to be provided to the transaction target user when the issuance target asset is traded; and the acquisition means acquires a provision instruction specifying the type of issuance target asset related information to be collected, which is specified based on the application specification information.

8. A method for collecting information related to an issuance target asset, when electronic transactions on a network for the issuance target asset for which a non-fungible token is issued can be executed using a non-fungible token that embodies an asset held by a user, comprising: registering the issuance target asset related information for each issuance target asset in an information management database in association with a token ID for identifying the non-fungible token, or updating and registering the information at a given timing after the issuance of the non-fungible token; acquiring a provision instruction transmitted from a terminal device of an information providing user who wishes to receive information related to the issuance target asset, the instruction specifying the type of the issuance target asset related information to be collected from the information management database along with the token ID of the issuance target asset; collecting the relevant issuance target asset related information from information stored in the information management database based on the acquired token ID and the specified type of issuance target asset related information; and executing a process to provide the collected issuance target asset related information to the relevant terminal device as a provision control process; A method for collecting information related to issuance assets, characterized in that the information related to issuance assets to be collected is identified by referring to a token ID for identifying the non-fungible token and token-related information related to the non-fungible token, which are specified for the non-fungible token corresponding to the information related to the issuance assets to be collected, and transaction processing specification information that specifies at least one of processing when a transaction of the non-fungible token is executed and processing when provision of the corresponding information related to the issuance assets is requested, and that is stored in a given storage medium or a given storage means.

9. An information provision system that provides collected issuance asset-related information regarding an issuance asset for which a non-fungible token is issued to a user who requests it, when electronic transactions on a network for the issuance asset for which a non-fungible token is issued can be carried out using a non-fungible token that embodies an asset held by the user, wherein the issuance asset-related information is registered in an information management database for each issuance asset in association with a token ID for identifying the non-fungible token, or is updated and registered at a given timing after the issuance of the non-fungible token, the information provision system comprising: a reception processing means that receives a provision instruction sent from a terminal device of the information requesting user together with the token ID of the issuance asset; a specification means that specifies the type of issuance asset-related information to be collected from the information management database based on the received token ID; an acquisition means that acquires the issuance asset-related information that has been specified and collected based on the specified type of issuance asset-related information and the received token ID; and a provision means that provides the acquired issuance asset-related information to the terminal device of the information requesting user.

10. An information provision system as set forth in claim 9, wherein the acquisition means acquires token-related information regarding the non-fungible token based on the token ID of the non-fungible token that is the subject of the transaction, and the provision means generates control information to be recognized by the user who wishes to receive information based on the acquired token-related information and the collected information related to the asset to be issued, and provides the generated control information to the relevant terminal device.

11. A method of providing collected asset-related information relating to an issuance target asset for which a non-fungible token is issued to an information-requesting user who wishes to provide the desired information, when electronic transactions on a network for the issuance target asset for which a non-fungible token is issued can be executed using a non-fungible token embodied in an asset held by the user, the method comprising: registering the asset-related information for each asset in an information management database in association with a token ID for identifying the non-fungible token, or updating and registering the information at a given time after the issuance of the non-fungible token; receiving a provision instruction sent from the terminal device of the information-requesting user together with the token ID of the non-fungible token embodied in the issuance target asset; identifying the type of asset-related information to be collected from the information management database based on the received token ID; acquiring the asset-related information identified and collected based on the identified type of asset-related information and the received token ID; and providing the acquired asset-related information to the terminal device of the information-requesting user.

12. An electronic transaction execution system that uses non-fungible tokens that embody assets held by users to execute electronic transactions on a network for assets for which non-fungible tokens are issued, as electronic transactions, wherein an information management database registers issuance target asset related information for the assets for which the non-fungible tokens are issued, in association with a token ID for identifying the non-fungible token for each of the assets, or updates and registers the information at a given timing after the issuance of the non-fungible token; transaction processing rule specification means that specifies a given process when executing the electronic transaction of the non-fungible token and specifies transaction processing rule information stored in a given storage medium or given storage means; transaction execution means that executes the electronic transaction and registration of update information in the database based on the specified transaction processing rule information; collection control means that, when executing the electronic transaction, controls the collection of issuance target asset related information for the assets for which the non-fungible tokens are issued from the information management database based on the specified transaction processing rule information; and provision means that provides the collected issuance target asset related information to a relevant terminal device. The electronic transaction execution system is characterized in that the collection control means identifies the type of issuance target asset related information to be collected from the information management database based on the identified transaction processing specification information, and collects the corresponding issuance target asset related information from the information stored in the information management database based on the identified type of issuance target asset related information.

13. An electronic transaction execution system as described in claim 12, further comprising: an acquisition means for acquiring token-related information regarding a non-fungible token based on the token ID of the non-fungible token that is the subject of the transaction; and a control information generation means for generating control information to be recognized by the target user of the transaction based on the acquired token-related information and the collected information related to the asset to be issued, wherein the provision means provides the generated control information to a corresponding terminal device.

14. A method for executing electronic commerce, using a non-fungible token embodied in an asset held by a user, to execute an electronic transaction on a network for an asset for which a non-fungible token is issued, as an electronic transaction, the method comprising: registering, in an information management database, asset-related information for the asset for which the non-fungible token is issued, in association with a token ID for identifying the non-fungible token for each asset, or updating and registering the information at a given timing after the issuance of the non-fungible token; identifying transaction processing specification information that specifies a given process for executing the electronic transaction of the non-fungible token and is stored in a given storage medium or given storage means; performing update registration in a transaction execution means and database that executes the electronic transaction based on the identified transaction processing specification information; controlling, when executing the electronic transaction, to collect asset-related information for the asset for which the non-fungible token is issued from the information management database based on the identified transaction processing specification information; and providing the collected asset-related information to a corresponding terminal device; A method for executing electronic commerce, characterized by: identifying a type of the issuance target asset related information to be collected from the information management database based on the identified transaction processing specification information; and collecting corresponding issuance target asset related information from information stored in the information management database based on the identified type of issuance target asset related information.

Images