JP2023107560A - Non-fungible token management apparatus, non-fungible token management method, and program - Google Patents

Abstract

To provide a non-fungible token management apparatus configured to efficiently suppress alteration of identification information of a tangible object, such as a commodity, and duplication risk, and improve the convenience for certifying ownership of the tangible object, a non-fungible token management method, and a program.SOLUTION: An NFT management server 6 is configured to: generate, on receipt of an NFT issuance request including commodity identification information read by a commodity producer terminal 3 from an RF tag 1 embedded in a commodity from the commodity producer terminal 3 through a communication network NW, a management page URL dedicated to the commodity identified by the commodity identification information, on the basis of the commodity identification information; issue an NFT for a commodity producer to certify ownership of the commodity on the basis of the commodity identification information, on a blockchain system BS; associate the issued NFT with the commodity identification information and the management page URL and manage it; and write the management page URL on the RF tag 1.SELECTED DRAWING: Figure 5

Description

The present invention relates to a technical field such as a system using NFT for proving ownership of tangible objects such as goods.

In recent years, NFTs (Non-Fungible Tokens) have become popular as a means of proving ownership of digital data. For example, as disclosed in Patent Document 1, NFTs can be issued according to the ERC (Ethereum Request for Comments) 721 standard, as an example. NFT ownership history and transaction history are recorded on the blockchain on the P2P network.

Japanese Patent No. 6973840

By the way, NFT is desired to be applied not only to digital data but also to property rights of tangible objects such as tradeable products. For example, when NFT is applied to product ownership, product identification information (product individual information) can be printed on the product itself, a sticker printed with product identification information can be attached to the product, or the product identification information can be written It is envisioned that the certificate will be provided in a form different from the product as a written appraisal, and that the product identification information will be certified as part of the NFT. However, the product identification information provided by these means can be easily duplicated or falsified, and counterfeit products with the same product identification information can be created. There is a problem that it looks like there is.

Therefore, the present invention has been made in view of the above problems, etc., and can efficiently suppress the risk of falsification and duplication of identification information of a tangible object such as a product, and enhance the convenience of proving the ownership of the tangible object. An object of the present invention is to provide a non-fungible token management device, a non-fungible token management method, and a program.

In order to solve the above problems, the invention according to claim 1 is a non-fungible token management device that can communicate with a provider terminal of a provider that provides a tangible object to be traded via a communication network, issuance request receiving means for receiving, from the provider terminal via the communication network, a non-fungible token issuance request containing the tangible object identification information read by the provider terminal from an IC tag embedded in the tangible object; URL generation means for generating, based on the tangible object identification information included in the non-fungible token issuance request, a URL for accessing a web server storing a management page dedicated to the tangible object identified by the tangible object identification information; Token issuing means for causing the provider to issue a non-fungible token on a blockchain system for proving ownership of the tangible object based on the tangible object identification information; token management means for managing the information and the URL in association with each other; and write command transmission means for transmitting a command to write the URL to the IC tag to the provider terminal via the communication network. Characterized by

The invention according to claim 2 is the non-fungible token management device according to claim 1, wherein the non-fungible token management device communicates with a purchaser terminal of a purchaser who purchases the tangible object via the communication network. A new URL which is communicable and includes an authentication code generated by cryptographic operation of the IC tag based on at least the URL written in the IC tag, and which is transmitted from the IC tag by the purchaser terminal transfer request receiving means for receiving a non-fungible token transfer request including the obtained new URL from the purchaser terminal via the communication network; and the new URL included in the non-fungible token transfer request. and a validity determination means for determining whether the IC tag is valid based on the above, and when the validity determination means determines that the IC tag is valid, the non-substitutable token transfer means for transferring a sex token from said provider or previous purchaser to said purchaser.

The invention according to claim 3 is a non-fungible token management device capable of communicating with a purchaser terminal of a purchaser who purchases a tangible object to be traded via a communication network, wherein the tangible object identification information of the tangible object access to a web server that stores the tangible object identification information and a dedicated management page for the tangible object in the non-fungible token issued on the blockchain system, which is a non-fungible token for proving the ownership of the tangible object. and a new URL containing an authentication code generated by a cryptographic operation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object. a transfer request receiving means for receiving a non-fungible token transfer request including the new URL acquired from the IC tag by the purchaser terminal from the purchaser terminal via the communication network; validity determination means for determining whether or not the IC tag is valid based on the new URL included in the fungibility token transfer request; and when the IC tag is determined to be valid by the validity determination means. and token transfer means for transferring the non-fungible token from the provider or previous purchaser of the tangible item to the purchaser on the blockchain system.

The invention according to claim 4 is the non-fungibility token management device according to claim 2 or 3, wherein the new URL includes a counter value that is incremented each time the new URL is read from the IC tag. further comprising counter value determination means for determining whether the counter value is normal, the validity determination means determining that the IC tag is valid, and the counter value When the determination means determines that the counter value is normal, the token transfer means transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system. It is characterized by

The invention according to claim 5 is the non-fungible token management device according to claim 2 or 3, wherein the non-fungible token transfer request conforms to the manifestation of intention of the non-fungible token transfer source. a manifestation of intention determination means for judging, wherein the validity judgment means judges that the IC tag is valid, and the non-fungibility token transfer request is determined by the manifestation of intention judgment means to be the non-fungibility token transfer source; wherein said token transfer means transfers said non-fungible token from said provider or previous purchaser to said purchaser on said blockchain system and

The invention according to claim 6 is the non-fungibility token management device according to claim 2 or 3, wherein the new URL has a counter value that is incremented each time the new URL is read from the IC tag. counter value determination means for determining whether the counter value is normal; declaration of intention determination means for determining the validity determination means determines that the IC tag is valid, and the counter value determination means determines that the counter value is normal, and , when the manifestation of intention determination means determines that the non-fungible token transfer request conforms to the manifestation of intention of the non-fungible token transfer source, the token transfer means performs the non-fungible token transfer on the blockchain system. The fungibility token is transferred from the provider or previous purchaser to the purchaser.

The invention according to claim 7 is the non-fungible token management device according to any one of claims 2 to 6, wherein the validity determination means comprises an authentication code included in the new URL and the new URL. The IC tag is determined to be valid when the authentication code generated by the cryptographic operation based on the original URL contained in the URL matches.

The invention according to claim 8 is a non-fungible token management method executed by a computer capable of communicating with a provider terminal of a provider who provides a tangible object to be traded via a communication network, wherein the tangible object receiving from the provider terminal via the communication network a non-fungible token issuance request containing tangible object identification information read by the provider terminal from the embedded IC tag; and issuing the non-fungible token. generating, based on the tangible object identification information included in the request, a URL for accessing a web server storing a management page dedicated to the tangible object identified by the tangible object identification information; a step in which a provider issues a non-fungible token for proving ownership of the tangible object on a blockchain system; and managing the tangible object identification information and the URL in association with the issued non-fungible token. and transmitting a command to write the URL to the IC tag to the provider terminal via the communication network.

According to the ninth aspect of the invention, a computer capable of communicating with a provider terminal of a provider who provides a tangible object to be traded through a communication network is read from an IC tag embedded in the tangible object by the provider terminal. an issuance request receiving means for receiving a non-fungible token issuance request including the issued tangible entity identification information from the provider terminal via the communication network; a URL generating means for generating a URL for accessing a web server that stores a management page dedicated to a tangible object identified by the tangible object identification information, based on the tangible object identification information; Token issuing means for issuing a non-fungible token for proving rights on a blockchain system; token management means for managing the issued non-fungible token in association with the tangible object identification information and the URL; It is characterized by functioning as writing command transmitting means for transmitting a command to write the URL to the IC tag to the provider terminal via the communication network.

According to a tenth aspect of the invention, there is provided a non-fungible token management method executed by a computer capable of communicating with a purchaser terminal of a purchaser who purchases a tangible object to be traded via a communication network, wherein the tangible object is The tangible object identification information and a management page dedicated to the tangible object are stored in a non-fungible token for proving ownership of the tangible object based on the tangible object identification information and issued on a blockchain system. a step of associating and managing a URL for accessing a web server; receiving from the purchaser terminal via the communication network a non-fungible token transfer request including the new URL obtained from the IC tag by the purchaser terminal; determining whether the IC tag is valid based on the new URL included in the fungibility token transfer request; and if the IC tag is determined to be valid, on the blockchain system transferring said non-fungible token from a provider or previous purchaser of said tangible object to said purchaser.

According to the eleventh aspect of the invention, a computer capable of communicating with a purchaser terminal of a purchaser who purchases a tangible object to be traded through a communication network determines ownership of the tangible object based on the tangible object identification information of the tangible object. A non-fungible token for certification and a non-fungible token issued on a blockchain system is associated with a URL for accessing a web server that stores the tangible object identification information and a management page dedicated to the tangible object. a token management means to manage; and a new URL including an authentication code generated by cryptographic operation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object, wherein the purchaser terminal a transfer request receiving means for receiving from said purchaser terminal via said communication network a non-fungible token transfer request including said new URL acquired from said IC tag by said non-fungible token transfer request included in said non-fungible token transfer request; a validity determination means for determining whether or not the IC tag is valid based on the new URL that is entered; and if the validity determination means determines that the IC tag is valid, the blockchain system It is characterized by functioning as a token transfer means for transferring the non-fungible token from the provider or previous purchaser of the tangible item to the purchaser.

ADVANTAGE OF THE INVENTION According to this invention, falsification and duplication risk of the identification information of a tangible thing, such as goods, can be suppressed efficiently, and the convenience which proves the ownership of the said tangible thing can be improved.

It is a figure which shows the outline|summary structure example of NFT management system NS. 1 is a diagram showing a schematic configuration example of an RF tag 1; FIG. 3 is a diagram showing an example of the schematic configuration of an NFT management server 6; FIG. FIG. 4 is a conceptual diagram showing an example of the flow of information exchange in the operation when issuing an NFT and the operation when transferring an NFT. FIG. 10 is a sequence diagram showing an example of operations when issuing an NFT in the NFT management system NS; FIG. 10 is a sequence diagram showing an example of operations at the time of NFT transfer in the NFT management system NS;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. The embodiments described below are embodiments in which the present invention is applied to an NFT management system. In addition, in the embodiments described below, commodities are used as examples of tangible objects to be traded.

[1. Outline configuration of NFT management system NS]
First, a schematic configuration of the NFT management system NS according to the present embodiment will be described with reference to FIG. 1 and the like. FIG. 1 is a diagram showing a schematic configuration example of the NFT management system NS. As shown in FIG. 1, the NFT management system NS includes RF (Radio Frequency Identifier) tags 1 (there are multiple) manufactured by tag manufacturers, tag manufacturer terminals 2 used by tag manufacturers, product manufacturers Product manufacturer terminal 3 used (an example of a provider terminal), product purchaser terminal 4 used by a product purchaser (an example of a purchaser terminal), tag authentication server operated by a tag authentication service provider 5, and an NFT management server 6 (an example of a non-fungible token management device) operated by an NFT management service provider.

Here, the RF tag 1 is an IC (Integrated Circuit) tag having tamper resistance, encryption operation function, and NFC (Near field communication) function, and tag identification information for identifying the RF tag 1 (tag individual information ) is saved. The RF tag 1 is embedded in the product by the product manufacturer (an example of a provider who provides the product). Thereby, the tag identification information is used as product identification information (an example of tangible object identification information) for identifying the product. The tag manufacturer's terminal 2 is a terminal having an NFC function (for example, a smart phone, a tablet, a personal computer, or the like), and performs contactless communication (wireless communication) with the RF tag 1 . This allows the tag manufacturer terminal 2 to write tag identification information to the RF tag 1 .

The product manufacturer terminal 3 is a terminal having an NFC function (for example, a smart phone, a tablet, a personal computer, or the like) and performs contactless communication with the RF tag 1 . This enables the product manufacturer terminal 3 to read necessary information such as tag identification information from the RF tag 1 embedded in the product. In addition, the product manufacturer terminal 3 is connectable (communicable) to the NFT management server 6 via the communication network NW, and exchanges information with the NFT management server 6 . Note that the communication network NW is composed of, for example, the Internet, a mobile communication network, its radio base stations, and the like.

The product purchaser terminal 4 is a terminal having an NFC function (for example, a smart phone, a tablet, a personal computer, or the like), and performs contactless communication with the RF tag 1 . As a result, the product purchaser terminal 4 can read necessary information from the RF tag 1 . In addition, the product purchaser terminal 4 can be connected to the NFT management server 6 via the communication network NW, and exchanges information with the NFT management server 6 .

The tag authenticity determination server 5 is composed of one or a plurality of server computers and is connected to the NFT management server 6 via the communication network NW. ) is determined). The authenticity determination function of the tag authenticity determination server 5 may be provided in the NFT management server 6 . In this case, the tag authentication server 5 becomes unnecessary.

The NFT management server 6 is composed of one or more server computers and functions as a web server on the communication network NW. In addition, the NFT management server 6 can be connected to the blockchain system BS via the communication network NW, and manages NFTs associated (linked) with product identification information for identifying products. Note that, even for the same product having a plurality of inventories, the product identification information differs for each product, so the NFT associated with the product identification information also differs. Blockchain system BS is based on a P2P network composed of a plurality of nodes (computers) connected to communication network NW, and is constructed by distributed applications and smart contracts provided by Ethereum, Polygon, etc., for example.

NFTs are used to prove ownership of goods and are issued from a specific contract address in the blockchain system BS, for example according to the ERC721 standard. A token ID (contract address and token ID) for identifying the NFT is associated with the NFT. The blockchain (distributed ledger) in the blockchain system BS records the owner and transaction history of the NFT. Note that a private blockchain other than a public blockchain such as Ethereum or Polygon may be applied to the blockchain system BS.

Also, the NFT management server 6 can be connected to the commodity trading system SS via the communication network NW. The product transaction system SS provides a marketplace and performs processing related to product transactions (buying and selling) performed at a product transaction site on the Internet or a physical store (for example, a POS terminal). In particular, when a product identified (specified) by product identification information associated with an NFT is traded at a product trading site or a physical store, the NFT management server 6 acquires transaction information related to the transaction from the product trading system SS. can do. Such transaction information includes the transaction date and time, product identification information of the traded product, the user ID of the product seller who sold the product, and the user ID of the product purchaser who purchased the product. Here, product sellers include not only product manufacturers, but also product purchasers who purchase products from product manufacturers, and product purchasers who purchase products from the product purchasers. The purchaser is hereinafter referred to as the "previous product purchaser"). Also, the user ID is user identification information for identifying a user who has been issued an account as a member using the NFT management system NS.

FIG. 2 is a diagram showing a schematic configuration example of the RF tag 1. As shown in FIG. As shown in FIG. 2, the RF tag 1 includes an antenna 11, an I/O circuit 12, a RAM (Random Access Memory) 13, a ROM (Read Only Memory) 14, a NVM (Nonvolatile Memory) 15, and a CPU (Central Processing Unit). ) 16. Antenna 11 receives radio waves having RF signals (including commands) transmitted from tag manufacturer terminal 2, product manufacturer terminal 3, or product purchaser terminal 4, and receives radio waves output from I/O circuit 12. It emits radio waves with RF signals (including responses). The I/O circuit 12 demodulates the RF signal from the antenna 11 and outputs the demodulated signal to the CPU 16 , modulates the signal from the CPU 16 and outputs the modulated RF signal to the antenna 11 . Programs are stored in the ROM 14 or NVM 15 . Examples of NVM 15 include flash memory and electrically erasable programmable read-only memory.

Tag identification information and individual keys are stored in the NVM 15 in advance by the tag manufacturer (for example, stored at the manufacturing stage of the RF tag 1). Here, as described above, the tag identification information is used as product identification information for identifying the product when the RF tag 1 is embedded in the product by the product manufacturer. The individual key is generated by inputting the tag identification information and performing cryptographic computation such as AES (Advanced Encryption Standard) computation using a predetermined master key as the cryptographic key, and is assigned to the tag identification information. Then, after the product identification information is associated with the unique NFT, the NVM 15 accesses the NFT management server 6 (web server) that stores the management page (web page) dedicated to the product identified by the product identification information. A URL (Uniform Resource Locator) (hereinafter referred to as a “management page URL”) for this purpose is stored by the product manufacturer terminal 3 .

The CPU 16 is included in the RF signal transmitted from the tag manufacturer terminal 2, the product manufacturer terminal 3, or the product purchaser terminal 4 according to the program stored in the ROM 14 or NVM 15, the antenna 11 and the I/O circuit 12 Reads information from the NVM 15, writes information to the NVM 15, and performs arithmetic processing according to a command (read command or write command) input via the . Note that the CPU 16 may generate random numbers using a random number generation algorithm. The NVM 15 may be provided with a counter controlled so as not to be decremented. In this case, the CPU 16 increments (adds) the counter value of the counter each time information is read from the NVM 15 in response to a URL read command from the product purchaser terminal 4 .

Such a read command may be an NDEF (NFC Data Exchange Format) read command. If the RF tag 1 is set to be read out in NDEF format, even if the product purchaser terminal 4 does not have a dedicated application installed, for example, the read URL can be responded to the product purchaser terminal 4. be able to. After the counter value reaches the maximum value, the CPU 16 fails to increment the counter value and responds with an error to the read command. Note that the counter value may be reset when the encryption key representing the authority of the tag manager (corresponding to the product manufacturer in this embodiment) is successfully authenticated.

FIG. 3 is a diagram showing a schematic configuration example of the NFT management server 6. As shown in FIG. As shown in FIG. 3, the NFT management server 6 includes a communication section 61, a storage section 62, an information processing section 63, and the like. The communication unit 61 has a function of connecting to the communication network NW. The storage unit 62 is composed of, for example, a hard disk drive or the like, and stores an operating system, an NFT management program (including the program of the present invention), and the like. In addition, a user information database (DB) 621, an NFT information database (DB) 622, and the like are constructed in the storage unit 62. FIG. Note that the user information database 621 and the NFT information database 622 may be provided in a database server (not shown).

The user information database 621 is a database for registering information on users who have been issued accounts as members using the NFT management system NS. The user information database 621 contains user IDs, passwords, e-mail addresses, addresses, telephone numbers, key pairs of public and private keys used in the blockchain system BS, individual addresses on the blockchain system BS, etc. for each user. It is associated and registered. Here, a key pair of a public key and a private key is issued individually for each user in the blockchain system BS in response to a request from the NFT management server 6, for example, when issuing an account. An individual address is generated according to a predetermined algorithm based on the public key. Individual addresses can be associated with NFTs in the blockchain system BS.

The NFT information database 622 is a database for registering information on NFTs issued in the blockchain system BS. The NFT information database 622 contains NFT contract addresses, NFT token IDs, individual addresses of users who own NFTs (that is, individual addresses linked to NFTs), product identification information, management page URLs, and transaction information ( may not exist) is associated with each NFT and registered. Here, the management page URL is the address (corresponding to the IP address) of the NFT management server 6 (web server) in which the management page is stored, and is generated from, for example, the domain, path (directory), and product identification information. represented by a specified URL parameter (which may include the hostname). The management page is composed of, for example, a structured document file such as an HTML (Hyper Text Markup Language) document or an XHTML document for describing information about the NFT.

The information processing unit 63 includes a RAM, a ROM, a CPU, etc., and operates according to the NFT management program stored in the storage unit 62. means, write command transmitting means, transfer request receiving means, validity judging means, counter value judging means, manifestation of intention judging means, token transfer means, etc., and executes various processes.

For example, when issuing an NFT to be associated with product identification information of a product manufactured by a product manufacturer, the information processing unit 63 reads from the RF tag 1 embedded in the product by the product manufacturer terminal 3. An NFT issuance request including the issued product identification information is received from the product manufacturer terminal 3 via the communication network NW. Then, based on the product identification information included in the received NFT issuance request, the information processing unit 63 generates a management page URL dedicated to the product identified by the product identification information.

Then, the information processing unit 63 causes the product manufacturer to issue an NFT on the blockchain system BS based on the product identification information to prove the ownership of the product, and the issued NFT includes the product identification information and the management page Manage by associating with the URL for use. For example, the contract address and token ID of the issued NFT are associated with the product identification information and the management page URL and registered in the NFT information database 622 for management. Then, the information processing section 63 transmits a command to write the management page URL to the RF tag 1 to the product manufacturer terminal 3 via the communication network NW. As a result, the management page URL is written in the RF tag 1 . Therefore, the risk of falsification and duplication of product identification information can be efficiently suppressed, and the convenience of proving the ownership of the product can be enhanced.

In addition, in the operation at the time of transfer of the NFT associated with the product identification information of the product sold from the product manufacturer (or previous product purchaser) to the product purchaser, the information processing unit 63 at least stores the management page URL A new URL containing an authentication code generated by the cryptographic operation of the RF tag 1 based on the acquired from the RF tag 1 (that is, the RF tag 1 embedded in the product) by the product purchaser terminal 4 An NFT transfer request including a new URL is received from the product purchaser terminal 4 via the communication network NW.

Then, the information processing unit 63 determines whether the RF tag 1 is valid based on the new URL included in the received NFT transfer request, and when it is determined that the RF tag 1 is valid, NFT is transferred from the product manufacturer (or previous product purchaser) to the product purchaser on the blockchain system BS. As a result, on the condition that the product identification information recorded in the RF tag 1 is reliable, the NFT linked to the product identification information can be transferred. Whether or not the RF tag 1 is legitimate may be determined based on the authentication result of the RF tag 1 by the tag authentication server 5 . This makes it possible to use a more reliable authenticity determination result.

The new URL may further include a counter value that is incremented each time the new URL is read from the RF tag 1. In this case, the information processing section 63 determines whether the counter value is normal. It is further determined whether or not there is. When the information processing unit 63 determines that the RF tag 1 is valid and that the counter value is normal, the information processing unit 63 assigns the NFT to the product manufacturer (or previous product purchase) on the blockchain system BS. person) to the product purchaser. As a result, on the condition that the product identification information recorded in the RF tag 1 is more reliable, the NFT linked to the product identification information can be transferred.

Further, the information processing section 63 may determine whether or not the NFT transfer request conforms to the declaration of intention of the NFT transfer source (that is, the product manufacturer or the previous product purchaser). In this case, when the information processing unit 63 determines that the RF tag 1 is valid and that the NFT transfer request conforms to the intention of the NFT transfer source, the NFT is transferred to the product on the blockchain system BS. transfer from the manufacturer (or previous purchaser of the goods) to the purchaser of the goods; Alternatively, when the information processing unit 63 determines that the RF tag 1 is valid, determines that the counter value is normal, and determines that the NFT transfer request conforms to the intention of the NFT transfer source, NFT is transferred from the product manufacturer (or previous product purchaser) to the product purchaser on the blockchain system BS.

[2. Operation of NFT management system NS]
Next, the operation of the NFT management system NS according to the present embodiment will be described separately for the operation when issuing an NFT and the operation when transferring an NFT. Note that FIG. 4 is a conceptual diagram showing an example of the flow of information exchange in the operation when issuing an NFT and the operation when transferring an NFT.

(2.1 Operation when issuing NFT)
First, with reference to FIG. 5, the operation of issuing an NFT in the NFT management system NS will be described. FIG. 5 is a sequence diagram showing an example of the operation when issuing an NFT in the NFT management system NS.

In FIG. 5, before a series of RF tags 1 to be embedded in each of a plurality of products is delivered to the product manufacturer, the tag manufacturer's terminal 2 operates as a master for cryptographic calculation according to instructions from the tag manufacturer. A key is generated (step S 1 ) and stored for manufacturing a series of RF tags 1 . The master key thus generated is sent from the tag manufacturer to the tag authentication service provider by a predetermined means and recorded in the tag authentication server 5 . Next, the tag manufacturer's terminal 2 generates unique tag identification information for each RF tag 1 according to instructions from the tag manufacturer (step S2).

Next, according to the instruction from the tag manufacturer, as shown in FIG. 4(a), the tag manufacturer's terminal 2 receives the tag identification information as input and performs cryptographic operations using the master key as the cryptographic key. A key is generated (step S3), and the individual key is assigned to the tag identification information. Note that the subsequent processing is performed for each RF tag 1 . Next, the tag manufacturer's terminal 2 transmits a write command including the tag identification information and the individual key to the RF tag 1 by non-contact communication according to the instruction from the tag manufacturer (step S4).

Next, when the RF tag 1 receives the write command from the tag manufacturer terminal 2, it writes the tag identification information and the individual key to the NVM 15 according to the write command (step S5), a response indicating normal termination is sent to the tag manufacturer's terminal 2; Thus, a series of RF tags 1 in which tag identification information and individual keys are stored (recorded) are shipped from the tag manufacturer and delivered to the product manufacturer. Note that the tag identification information and individual key are different for each RF tag 1 .

Then, a series of RF tags 1 received by the product manufacturer are embedded one by one in each product in the process of manufacturing each product. Then, according to the instruction from the product manufacturer, the product manufacturer terminal 3 transmits a tag identification information read command to the RF tag 1 by non-contact communication (step S6).

Next, when the RF tag 1 receives the read command from the product manufacturer terminal 3, it reads the tag identification information from the NVM 15 as shown in FIG. A response including the tag identification information is transmitted to the product manufacturer terminal 3 (step S8). Next, when the product manufacturer terminal 3 receives the tag identification information from the RF tag 1, as shown in (d) of FIG. to the NFT management server 6 (step S9). Note that the NFT issuance request may further include product features and image data.

Next, when the NFT management server 6 receives the NFT issuance request from the product manufacturer terminal 3, in response to the NFT issuance request, as shown in (e) of FIG. A management page URL (including domain, path, and product identification information) dedicated to the product identified by the identification information is generated (step S10). Next, as shown in (f) of FIG. 4, the NFT management server 6 sends an NFT issuance request containing the product identification information (or management page URL) and the individual address of the product manufacturer to the blockchain system BS (any node) (step S11).

With such an NFT issuance request, an NFT linked with product identification information is issued from a specific contract address in the blockchain system BS (step S12). By linking the issued NFT to the product manufacturer's individual address, it is recorded in the blockchain that the NFT is owned by the product manufacturer. Next, an NFT issuance completion notification including the contract address of the NFT, the token ID, and the individual address of the product manufacturer is sent from the blockchain system BS to the NFT management server 6 (step S13).

In addition, in the NFT issuance request, the product identification information of the product may be specified as the NFT token ID, or a data string generated by a predetermined algorithm from the product identification information may be specified as the token ID, Alternatively, a unique token ID may be issued at a specific contract address in the blockchain system BS.

Next, when the NFT management server 6 receives the NFT issuance completion notification from the blockchain system BS, it registers information on the issued NFT (step S14). For example, the contract address of the issued NFT, the token ID, the individual address of the product manufacturer, the product identification information, and the management page URL are associated and registered in the NFT information database 622 . The NFT information database 622 may further register product features and image data.

Next, as shown in (g) of FIG. 4, the NFT management server 6 transmits a write command for writing the management page URL to the RF tag 1 to the product manufacturer terminal 3 via the communication network NW (step S15). Next, upon receiving the write command from the NFT management server 6, the product manufacturer terminal 3 transmits a write command including the management page URL to the RF tag 1 by contactless communication in response to the write command (step S16 ).

Next, when the RF tag 1 receives a write command from the product manufacturer terminal 3, it writes the management page URL to the NVM 15 as shown in (h) of FIG. 4 according to the write command (step S17). , a response indicating normal termination is sent to the product manufacturer terminal 3 . In this way, each product embedded with the RF tag 1 storing the product identification information, individual key, and management page URL is shipped by the product manufacturer and registered (exhibited) in the product trading system SS.

(2.2 Operation at the time of transfer of NFT)
Next, with reference to FIG. 6, the operation at the time of NFT transfer in the NFT management system NS will be described. FIG. 6 is a sequence diagram showing an example of operations at the time of NFT transfer in the NFT management system NS. After the product in which the RF tag 1 is embedded is put up for sale, for example, when a transaction of the product is established at a product trading site or an actual store, transaction information regarding the transaction is transmitted from the product trading system SS to the NFT management server 6.

The product purchaser uses his/her own product purchaser terminal 4 to start the procedure for transferring the NFT for proving the ownership of the product received by purchase from the product manufacturer (or previous product purchaser) to himself/herself. near the embedding part of the RF tag 1 in the product, the RF tag 1 is activated by the electromagnetic field from the product purchaser terminal 4, and non-contact communication between the product purchaser terminal 4 and the RF tag 1 is started. . Then, the product purchaser terminal 4 transmits the above-described NDEF read command to the RF tag 1 by non-contact communication (step S21).

Next, when the RF tag 1 receives the NDEF read command from the product purchaser terminal 4, it reads the individual key and the counter value of the counter from the NVM 15 according to the NDEF read command, and Then, data including the counter value as a dynamic element is input, and a session key is generated by executing cryptographic computation such as AES computation using the individual key as the cryptographic key (step S22).

Next, the RF tag 1 reads out the management page URL from the NVM 15, and as shown in (j) of FIG. Furthermore, a data block is generated by adding the generated random numbers in the form of URL parameters (step S23). Note that a data block (that is, a data block containing no random numbers) may be generated in which the counter value is linked to the management page URL in the form of a URL parameter.

Next, as shown in (k) of FIG. 4, the RF tag 1 receives data including the generated data block as a dynamic element, and uses the generated session key as an encryption key to perform encryption such as AES calculation. An authentication code is generated by executing the calculation (step S24). Alternatively, the RF tag 1 may generate an authentication code by executing the cryptographic operation with the management page URL as an input and the generated session key as an encryption key.

Next, the RF tag 1 transmits a response including a new URL in which the generated authentication code is linked to the data block in the form of a URL parameter to the product purchaser terminal 4 in the form of NDEF (step S25). . That is, a new URL obtained by adding the counter value, random number, and authentication code as URL parameters to the management page URL is read from the RF tag 1 by the product purchaser terminal 4 .

Next, when the product purchaser terminal 4 receives a response including a new URL expressed in the NDEF format from the RF tag 1, the product purchaser terminal 4 activates the web browser, and according to the acquired URL, the terminal 4 of FIG. As shown, the NFT management server 6 (web server) is accessed via the communication network NW to send a page request (step S26). This page request is an HTTP (Hypertext Transfer Protocol) request and includes the new URL acquired from the RF tag 1 .

Next, the NFT management server 6 (web server), in response to the page request from the product purchaser terminal 4, information on the NFT associated with the product identification information in the new URL included in the page request (for example, NFT contract address, NFT token ID, individual address of product manufacturer owning NFT) are acquired from NFT information database 622 (step S27).

Next, the NFT management server 6 (web server) transmits a management page containing information about the NFT (management page dedicated to the product identified by the product identification information) to the product purchaser terminal 4 via the communication network NW. (Response) (step S28). Note that the product-dedicated management page may further include product features and image data.

Next, when the product purchaser terminal 4 receives the management page from the NFT management server 6 (web server), it displays the management page on the web browser (step S29). On the management page displayed in this way, a menu for operating the NFT linked to the product identification information is displayed, and the product purchaser selects NFT transfer (that is, acquisition of ownership) from the menu. Then, the product purchaser terminal 4 sends an NFT transfer request (HTTP request) including the new URL acquired from the RF tag 1 and the product purchaser's user ID to the NFT management server 6 via the communication network NW using a web browser. (web server) (step S30).

Next, when the NFT management server 6 receives the NFT transfer request from the product purchaser terminal 4, in order to determine that the new URL included in the NFT transfer request is transmitted by the valid RF tag 1, An authentication request including the URL is transmitted to the tag authentication server 5 via the communication network NW (step S31).

Next, when the tag authenticity determination server 5 receives the authentication request from the NFT management server 6, based on the new URL included in the authenticity determination request, the tag authentication server 5 executes the authentication determination of the RF tag 1 (step S32), The authentication result is transmitted to the NFT management server 6 (step S33). In the authenticity determination of the RF tag 1 in step S32, as shown in (m) of FIG. An individual key is generated by executing an encryption operation such as an AES operation using a master key previously received and recorded from a person as an encryption key. Next, as shown in (n) of FIG. 4, the tag authenticity determination server 5 receives data including the counter value obtained from the new URL as a dynamic element, and uses the generated individual key as an encryption key. Generate a session key by performing a cryptographic operation.

Next, as shown in (o) of FIG. 4, the tag authenticity determination server 5 receives the data obtained by removing the authentication code from the new URL, and executes cryptographic calculation using the generated session key as the cryptographic key. to generate an authorization code. Next, as shown in (p) of FIG. 4, the tag authenticity determination server 5 compares the generated authentication code with the authentication code acquired from the new URL to determine if they match (that is, authenticate verification of the code) to determine the authenticity of the RF tag 1. For example, if the authentication codes match, the authentication result indicates that the RF tag 1 is authentic. On the other hand, if the authentication codes do not match, the authentication result indicates that the RF tag 1 is counterfeit.

Next, when receiving the authentication result from the tag authentication server 5, the NFT management server 6 determines whether the RF tag 1 is valid based on the authentication result (step S34). If the authentication result indicates that the RF tag 1 is counterfeit, it is determined that the RF tag 1 is not legitimate (step S34: NO), and the process proceeds to step S37. On the other hand, if the authenticity determination result indicates that the RF tag 1 is true, it is determined that the RF tag 1 is valid (step S34: YES), and the process proceeds to step S35.

In step S35, the NFT management server 6 determines whether or not the counter value obtained from the new URL included in the NFT transfer request is normal. Such a counter value is incremented each time a new URL is read from the RF tag 1 . For example, the NFT management server 6 first stores the counter value in association with the product identification information, confirms that the counter value is incremented each time the counter value is acquired, and confirms that the stored counter value is If the value and the obtained counter value are equal or if the stored counter value is greater than the obtained counter value, it is determined that the counter value is not normal (step S35: NO ), and the process proceeds to step S37. On the other hand, if it is determined that the counter value is normal (step S35: YES), the process proceeds to step S36.

In step S36, the NFT management server 6 checks from the product trading system SS whether the NFT transfer request conforms to the intention of the NFT transfer source (that is, indicates the intention to abandon the ownership of the product). Determination is made based on the acquired transaction information. For example, if the product identification information obtained from the new URL included in the NFT transfer request and the transaction information that the user ID included in the NFT transfer request includes as the product purchaser's user ID are obtained, the NFT transfer It is determined that the request conforms to the intention of the NFT transfer source (step S36: YES), and the process proceeds to step S39. In addition, if the NFT transfer source is the product manufacturer, the NFT transfer destination is assumed to be an unspecified product purchaser. may be determined. On the other hand, if it is determined that the declaration of intention of the NFT transfer source is not followed (step S36: NO), the process proceeds to step S37.

In step S<b>37 , the NFT management server 6 transmits a response indicating refusal of the NFT transfer request to the product purchaser terminal 4 . When the product purchaser terminal 4 receives a response indicating refusal from the NFT management server 6 (web server), it displays information indicating NFT transfer failure (ownership acquisition failure) on the management page by the web browser (step S38 ).

In step S39, the NFT management server 6 transmits an NFT transfer request to the blockchain system BS (any node), as shown in (q) of FIG. Such an NFT transfer request includes the NFT token ID (or contract address and token ID) linked to the product identification information acquired from the new URL, the NFT sender address (for example, the product manufacturer or the previous product purchaser's individual address), and NFT destination address (for example, product purchaser's individual address). That is, the NFT transfer request indicates that the NFT (token ID of the NFT) is transferred from the source address to the destination address.

With such an NFT transfer request, the NFT is transferred from the product manufacturer (or previous product purchaser) to the product purchaser on the blockchain system BS (step S40). As a result, by linking the NFT related to the transfer to the individual address of the product purchaser, it is recorded in the blockchain that the NFT is owned by the product purchaser. Next, an NFT transfer completion notification including the contract address of the NFT, the token ID, and the individual address of the product purchaser is sent from the blockchain system BS to the NFT management server 6 (step S41).

Next, when the NFT management server 6 receives the NFT transfer completion notification from the blockchain system BS, it updates the individual address associated with the contract address and token ID of the transferred NFT in the NFT information database 622 ( step S42). That is, the NFT source address (for example, the individual address of the product manufacturer or previous product purchaser) is updated to the NFT destination address (for example, the individual address of the product purchaser).

Next, the NFT management server 6 (web server) acquires information on the transferred NFT (for example, NFT contract address, NFT token ID, individual address of the product purchaser after update) from the NFT information database 622 ( step S43). Next, the NFT management server 6 (web server) sends a management page (that is, an updated management page) containing information about the NFT to the product purchaser terminal via the communication network NW along with a response indicating permission for the NFT transfer request. 4 (step S44). Note that the product-dedicated management page may further include product features and image data.

Next, when the product purchaser terminal 4 receives the response indicating the updated management page and permission from the NFT management server 6 (web server), the web browser displays the management page, and the NFT transfer success (ownership acquisition information indicating success) is displayed on the management page (step S45).

As described above, according to the above embodiment, the NFT management server 6 transmits the NFT issuance request including the product identification information read by the product manufacturer terminal 3 from the RF tag 1 embedded in the product to the communication network. When received from the product manufacturer terminal 3 via the NW, based on the product identification information, a management page URL dedicated to the product identified by the product identification information is generated, and based on the product identification information, the product manufacturer issues an NFT to prove the ownership of the product on the blockchain system BS, manages the issued NFT by associating the product identification information and the management page URL, and sets the management page URL to the RF tag 1, the product-specific information and management page URL linked to the NFT can be efficiently recorded on the RF tag 1, and the risk of falsification and duplication of product identification information can be efficiently suppressed. , can increase the convenience of proving ownership of goods.

Furthermore, according to the above embodiment, the NFT management server 6 is a new URL containing an authentication code generated by cryptographic calculation of the RF tag 1 based on at least the management page URL, and the product purchaser terminal 4 When the NFT transfer request including the new URL acquired from the RF tag 1 is received from the product purchaser terminal 4 via the communication network NW, it is determined whether the RF tag 1 is valid based on the new URL. If it is determined that the RF tag 1 is valid, the NFT is transferred from the product manufacturer (or previous product purchaser) to the product purchaser on the blockchain system BS, so the RF It is possible to verify the reliability of the product identification information recorded in the tag 1 before NFT transfer, and transfer the NFT linked to the product identification information on the condition that the product identification information is reliable. It is possible to increase the convenience of proving the ownership of the product corresponding to the transferred NFT while maintaining the suppression of falsification and duplication risks of the product identification information.

1 RF tag 2 Tag manufacturer terminal 3 Product manufacturer terminal 4 Product purchaser terminal 5 Tag authentication server 6 NFT management server 11 Antenna 12 I/O circuit 13 RAM
14 ROMs
15NVM
16 CPUs
61 communication unit 62 storage unit 63 information processing unit NW communication network NS NFT management system

Claims (11)

A non-fungible token management device capable of communicating with a provider terminal of a provider that provides a tangible object to be traded via a communication network,
issuance request receiving means for receiving, from the provider terminal via the communication network, a non-fungible token issuance request containing the tangible object identification information read by the provider terminal from an IC tag embedded in the tangible object;
URL generation means for generating, based on the tangible object identification information included in the non-fungible token issuance request, a URL for accessing a web server storing a management page dedicated to the tangible object identified by the tangible object identification information;
token issuing means for issuing a non-fungible token on a blockchain system for the provider to prove ownership of the tangible object based on the tangible object identification information;
token management means for managing the issued non-fungible token in association with the tangible object identification information and the URL;
writing command transmitting means for transmitting a command to write the URL to the IC tag to the provider terminal via the communication network;
A non-fungible token management device comprising: The non-fungible token management device is capable of communicating with a purchaser terminal of a purchaser who purchases the tangible object via the communication network,
A new URL containing an authentication code generated by a cryptographic operation of the IC tag based on at least the URL written in the IC tag, the new URL obtained from the IC tag by the purchaser terminal. a transfer request receiving means for receiving a non-fungible token transfer request including from the purchaser terminal via the communication network;
validity determination means for determining whether or not the IC tag is valid based on the new URL included in the non-fungible token transfer request;
a token transfer means for transferring the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system when the validity determination means determines that the IC tag is valid; ,
2. The non-fungibility token management device of claim 1, further comprising: A non-fungible token management device capable of communicating with a purchaser terminal of a purchaser who purchases a tangible object to be traded via a communication network,
a non-fungible token for proving ownership of the tangible object based on the tangible object identification information of the tangible object and issued on a blockchain system; a token management means for managing in association with a URL for accessing a web server storing
A new URL including an authentication code generated by cryptographic computation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object, and obtained from the IC tag by the purchaser terminal. transfer request receiving means for receiving a non-fungible token transfer request including the new URL from the purchaser terminal via the communication network;
validity determination means for determining whether or not the IC tag is valid based on the new URL included in the non-fungible token transfer request;
Token transfer for transferring the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser on the blockchain system when the validity determination means determines that the IC tag is valid means and
A non-fungible token management device comprising: The new URL further includes a counter value that is incremented each time the new URL is read from the IC tag,
Further comprising counter value determination means for determining whether the counter value is normal,
When the validity determination means determines that the IC tag is valid and the counter value determination means determines that the counter value is normal, the token transfer means performs 4. The non-fungible token management device according to claim 2, wherein said non-fungible token is transferred from said provider or previous purchaser to said purchaser. further comprising manifestation of intention determination means for determining whether the non-fungible token transfer request conforms to the manifestation of intention of the non-fungible token transfer source;
The validity determination means determines that the IC tag is valid, and the declaration of intention determination means determines that the non-fungible token transfer request conforms to the declaration of intention of the non-fungible token transfer source. 4. The token transfer means according to claim 2 or 3, wherein the token transfer means transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system when A non-fungible token manager. The new URL further includes a counter value that is incremented each time the new URL is read from the IC tag,
counter value determination means for determining whether the counter value is normal;
manifestation of intention determination means for determining whether the non-fungible token transfer request conforms to the manifestation of intention of the non-fungible token transfer source;
further comprising
The validity determination means determines that the IC tag is valid, the counter value determination means determines that the counter value is normal, and the manifestation of intention determination means determines the non-fungible token transfer When it is determined that the request conforms to the manifestation of intention of the non-fungible token transfer source, the token transfer means transfers the non-fungible token from the provider or previous purchaser on the blockchain system. 4. The non-fungible token management device according to claim 2 or 3, wherein the token is transferred to the purchaser. The legitimacy determination means determines that the IC tag is 7. The non-fungibility token management device according to any one of claims 2 to 6, characterized in that it determines that the token is legitimate. A non-fungible token management method executed by a computer capable of communicating with a provider terminal of a provider that provides a tangible object to be traded via a communication network,
a step of receiving, from the provider terminal via the communication network, a non-fungible token issuance request containing the tangible object identification information read by the provider terminal from the IC tag embedded in the tangible object;
generating a URL for accessing a web server storing a management page dedicated to a tangible object identified by the tangible object identification information based on the tangible object identification information included in the non-fungible token issuance request;
a step of issuing a non-fungible token on a blockchain system for the provider to prove ownership of the tangible object based on the tangible object identification information;
a step of managing the issued non-fungible token in association with the tangible object identification information and the URL;
a step of transmitting a command to write the URL to the IC tag to the provider terminal via the communication network;
A non-fungible token management method, comprising: A computer that can communicate with a provider terminal of a provider that provides a tangible object to be traded via a communication network,
issuance request receiving means for receiving, from the provider terminal via the communication network, a non-fungible token issuance request containing the tangible object identification information read by the provider terminal from an IC tag embedded in the tangible object;
URL generation means for generating, based on the tangible object identification information included in the non-fungible token issuance request, a URL for accessing a web server storing a management page dedicated to the tangible object identified by the tangible object identification information;
token issuing means for issuing a non-fungible token on a blockchain system for the provider to prove ownership of the tangible object based on the tangible object identification information;
token management means for managing the issued non-fungible token in association with the tangible object identification information and the URL;
A program characterized by functioning as writing command transmitting means for transmitting a command to write the URL to the IC tag to the provider terminal via the communication network. A non-fungible token management method executed by a computer capable of communicating with a purchaser terminal of a purchaser who purchases a tangible object to be traded via a communication network,
a non-fungible token for proving ownership of the tangible object based on the tangible object identification information of the tangible object and issued on a blockchain system; a step of associating and managing a URL for accessing a web server storing
A new URL including an authentication code generated by cryptographic computation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object, and obtained from the IC tag by the purchaser terminal. receiving a non-fungibility token transfer request including the new URL from the purchaser terminal via the communication network;
determining whether the IC tag is valid based on the new URL included in the non-fungible token transfer request;
transferring the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser on the blockchain system when the IC tag is determined to be valid;
A non-fungible token management method, comprising: A computer that can communicate with a purchaser terminal of a purchaser who purchases a tangible object to be traded via a communication network,
a non-fungible token for proving ownership of the tangible object based on the tangible object identification information of the tangible object and issued on a blockchain system; a token management means for managing in association with a URL for accessing a web server storing
A new URL including an authentication code generated by cryptographic computation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object, and obtained from the IC tag by the purchaser terminal. transfer request receiving means for receiving a non-fungible token transfer request including the new URL from the purchaser terminal via the communication network;
validity determination means for determining whether or not the IC tag is valid based on the new URL included in the non-fungible token transfer request;
Token transfer for transferring the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser on the blockchain system when the validity determination means determines that the IC tag is valid A program characterized by functioning as a means.

Images