Non-fungible token management device, non-fungible token management method, and program

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

[Technical Field]

[0001] The present invention relates to technical fields such as systems that use NFTs to prove ownership of tangible objects such as goods. [Background technology]

[0002] In recent years, non-fungible tokens (NFTs) have become popular as a means of proving ownership of digital data. For example, as disclosed in Patent Document 1, NFTs can be issued in accordance with the Ethereum Request for Comments (ERC) 721 standard. The ownership history and transaction history of NFTs are recorded on a blockchain on a P2P network. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6973840 Summary of the Invention [Problem to be solved by the invention]

[0004] It is hoped that NFTs will be applied not only to digital data but also to ownership of tangible objects such as tradeable goods. For example, when applying NFTs to ownership of goods, it is envisioned that product identification information (product-specific information) may be printed on the product itself, a sticker printed with product identification information may be affixed to the product, or a certificate of authenticity containing product identification information may be provided in a form separate from the product, thereby certifying the product identification information as part of the NFT. However, product identification information provided by these means is easily copied or tampered with, making it possible to create counterfeit goods with the same product identification information, which poses the problem that even counterfeit goods may appear to be genuine on the NFT.

[0005] Therefore, the present invention has been made in consideration of the above problems, and aims to provide a non-fungible token management device, a non-fungible token management method, and a program that can efficiently reduce the risk of tampering with and copying of identification information of tangible objects such as products, and increase the convenience of proving ownership of the tangible objects. [Means for solving the problem]

[0006] In order to solve the above problem, the invention described in claim 1 is 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, the non-fungible token management device comprising: an issuance request receiving means that receives, from the provider terminal via the communication network, a non-fungible token issuance request including tangible object identification information read by the provider terminal from an IC tag embedded in the tangible object; Informing URL for accessing a web server that stores a management page dedicated to the tangible object identified by a URL including the tangible object identification information; a token issuing means for issuing a non-fungible token on a blockchain system based on the tangible item identification information so that the provider can prove ownership of the tangible item; a token management means for managing the issued non-fungible token by associating it with the tangible item identification information and the URL; and a write command sending means for sending a command to the provider terminal via the communication network to write the URL to the IC tag.

[0007] The invention of claim 2 is the non-fungible token management device of claim 1, wherein the non-fungible token management device is capable of communicating with a purchaser terminal of a purchaser who purchases the tangible item via the communication network, and includes a transfer request receiving means for receiving from the purchaser terminal via the communication network a non-fungible token transfer request including a new URL that includes an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag, the new URL being acquired from the IC tag by the purchaser terminal; and and comparing the authentication code acquired from the URL with an authentication code generated by the same cryptographic operation as that of the IC tag based on data obtained by removing the authentication code from the new URL, and determining whether they match. The system further comprises a validity determination means for determining whether the IC tag is valid or not, and a token transfer means for transferring the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system if the validity determination means determines that the IC tag is valid.

[0008] The invention described in 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, the non-fungible token being used to prove ownership of the tangible object. to Non-fungible tokens issued on a blockchain system 、 The aforementioned tangible Physical identification information and Identified by the tangible object identification information a token management means for managing a URL for accessing a web server storing a management page dedicated to the tangible object in association with the token; a transfer request receiving means for receiving, from the purchaser terminal via the communication network, a non-fungible token transfer request including a new URL that includes an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object, the new URL being obtained from the IC tag by the purchaser terminal; and and comparing the authentication code acquired from the URL with an authentication code generated by the same cryptographic operation as that of the IC tag based on data obtained by removing the authentication code from the new URL, and determining whether they match.The system is characterized by comprising a validity determination means for determining whether the IC tag is valid or not, and a token transfer means for transferring the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser on the blockchain system if the validity determination means determines that the IC tag is valid.

[0009] The invention described in claim 4 is a non-fungible token management device described in claim 2 or 3, wherein the new URL further includes a counter value that is incremented each time the new URL is read from the IC tag, and further comprises a counter value determination means for determining whether the counter value is normal, and 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 transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system.

[0010] The invention of claim 5 is the non-fungible token management device of claim 2 or 3, wherein the non-fungible token transfer request is the provider or prior purchaser The IC tag is determined to be valid by the validity determination means, and the non-fungible token transfer request is determined to be valid by the validity determination means. the provider or prior purchaser If it is determined that the intention is in accordance with the statement of intent, the token transfer means transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system.

[0011] The invention of claim 6 is the non-fungible token management device of claim 2 or 3, wherein the new URL further includes a counter value that is incremented every time the new URL is read from the IC tag, and the non-fungible token transfer request is transmitted to the counter value determination means. the provider or prior purchaserand an intention determination means for determining whether the IC tag conforms to the intention of the user, and when 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 intention determination means determines that the non-fungible token transfer request conforms to the intention of the user. the provider or prior purchaser If it is determined that the intention is in accordance with the statement of intent, the token transfer means transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system.

[0012] The invention described in claim 7 is a non-fungible token management device according to any one of claims 2 to 6, The new URL includes the original URL, The validity determination means is characterized in that it determines that the IC tag is valid if the authentication code included in the new URL matches the authentication code generated by cryptographic calculation based on the original URL included in the new URL.

[0013] The invention described in claim 8 is 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, the method comprising the steps of receiving, from the provider terminal via the communication network, a non-fungible token issuance request including tangible object identification information read by the provider terminal from an IC tag embedded in the tangible object; Informing URL for accessing a web server that stores a management page dedicated to the tangible object identified by a URL including the tangible object identification information; a step of generating a token based on the tangible object identification information, 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 by associating it with the tangible object identification information and the URL, and a step of transmitting an instruction to the provider terminal via the communication network to write the URL to the IC tag.

[0014] The invention described in claim 9 includes a computer that can communicate with a provider terminal of a provider that provides a tangible object to be traded via a communication network, an issuance request receiving means that receives from the provider terminal via the communication network a non-fungible token issuance request including tangible object identification information read by the provider terminal from an IC tag embedded in the tangible object, and a communication means for receiving the tangible object identification information included in the non-fungible token issuance request. Informing URL for accessing a web server that stores a management page dedicated to the tangible object identified by a URL including the tangible object identification information; a token issuing means for issuing a non-fungible token on a blockchain system based on the tangible item identification information so that the provider can prove ownership of the tangible item; a token management means for managing the issued non-fungible token by associating it with the tangible item identification information and the URL; and a write command sending means for sending a command to write the URL to the provider terminal via the communication network.

[0015] The invention described in claim 10 is a non-fungible token management method executed by a computer that can communicate with a purchaser terminal of a purchaser who purchases a tangible item to be traded via a communication network, To prove ownership of said tangible object to Non-fungible tokens issued on a blockchain system 、 The aforementioned tangible Physical identification information and Identified by the tangible object identification information a step of managing a URL for accessing a web server storing a management page dedicated to the tangible object in association with the URL; a step of receiving a non-fungible token transfer request from the purchaser terminal via the communication network, the non-fungible token transfer request including a new URL that includes an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object, the new URL being acquired from the IC tag by the purchaser terminal; and comparing the authentication code acquired from the URL with an authentication code generated by the same cryptographic operation as that of the IC tag based on data obtained by removing the authentication code from the new URL, and determining whether they match.The method is characterized by including a step of determining whether the IC tag is legitimate, and if the IC tag is determined to be legitimate, a step of transferring the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser on the blockchain system.

[0016] The invention described in claim 11 is a method for verifying ownership of a tangible object by using a computer that can communicate with a purchaser terminal of a purchaser who purchases the tangible object through a communication network. to Non-fungible tokens issued on a blockchain system 、 The aforementioned tangible Physical identification information and Identified by the tangible object identification information a token management means for managing a URL for accessing a web server storing a management page dedicated to the tangible object in association with the token; a transfer request receiving means for receiving, from the purchaser terminal via the communication network, a non-fungible token transfer request including a new URL that includes an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object, the new URL being obtained from the IC tag by the purchaser terminal; and and comparing the authentication code acquired from the URL with an authentication code generated by the same cryptographic operation as that of the IC tag based on data obtained by removing the authentication code from the new URL, and determining whether they match. The system is characterized by having a validity determination means for determining whether the IC tag is valid or not, and functioning as a token transfer means for transferring the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser on the blockchain system if the validity determination means determines that the IC tag is valid. [Effects of the Invention]

[0017] According to the present invention, it is possible to efficiently suppress the risk of tampering with and copying of identification information of a tangible object such as a product, and to increase the convenience of proving ownership of the tangible object. [Brief explanation of the drawings]

[0018] [Figure 1] A diagram showing an example of the general configuration of an NFT management system NS. [Figure 2] 1 is a diagram illustrating an example of a schematic configuration of an RF tag 1. FIG. [Figure 3] A diagram showing an example of the schematic configuration of an NFT management server 6. [Figure 4] This is a conceptual diagram showing an example of the flow of information exchange during the operations when issuing an NFT and when transferring an NFT. [Figure 5] This is a sequence diagram showing an example of the operation when issuing an NFT in the NFT management system NS. [Figure 6] This is a sequence diagram showing an example of operation when transferring an NFT in the NFT management system NS. DETAILED DESCRIPTION OF THE INVENTION

[0019] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Note that the embodiment described below is an embodiment in which the present invention is applied to an NFT management system. Furthermore, in the embodiment described below, a tangible object to be traded will be described using a commodity as an example.

[0020] [1. Overview of the NFT management system NS] First, the schematic configuration of the NFT management system NS according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a diagram showing an example of the schematic configuration of the NFT management system NS. As shown in Fig. 1, the NFT management system NS is configured to include RF (Radio Frequency Identifier) ​​tags 1 (there are multiple tags) manufactured by a tag manufacturer, a tag manufacturer terminal 2 used by the tag manufacturer, a product manufacturer terminal 3 (an example of a provider terminal) used by a product manufacturer, a product purchaser terminal 4 (an example of a purchaser terminal) used by a product purchaser, a tag authenticity determination server 5 operated by a tag authenticity determination service provider, and an NFT management server 6 (an example of a non-fungible token management device) operated by an NFT management service provider.

[0021] Here, the RF tag 1 is an IC (Integrated Circuit) tag with tamper resistance, cryptographic calculation function, and NFC (Near Field Communication) function, and is configured to store tag identification information (tag-specific information) for identifying the RF tag 1. The RF tag 1 is configured to be embedded in a product by a product manufacturer (an example of a provider of products). As a result, the tag identification information is used as product identification information (an example of tangible object identification information) for identifying the product. The tag manufacturer terminal 2 is a terminal (e.g., a smartphone, tablet, or personal computer) with an NFC function, and performs contactless communication (wireless communication) with the RF tag 1. As a result, the tag manufacturer terminal 2 can write the tag identification information to the RF tag 1.

[0022] The product manufacturer terminal 3 is a terminal (for example, a smartphone, tablet, or personal computer) with an NFC function, 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. The product manufacturer terminal 3 is also connectable to (communicable with) the NFT management server 6 via a communication network NW, and exchanges information with the NFT management server 6. The communication network NW is composed of, for example, the Internet, a mobile communication network, and its wireless base stations, etc.

[0023] The product purchaser terminal 4 is a terminal with an NFC function (for example, a smartphone, tablet, or personal computer) and performs contactless communication with the RF tag 1. This enables the product purchaser terminal 4 to read necessary information from the RF tag 1. The product purchaser terminal 4 is also connectable to the NFT management server 6 via the communication network NW, and exchanges information with the NFT management server 6.

[0024] The tag authenticity determination server 5 is composed of one or more server computers, is connected to the NFT management server 6 via a communication network NW, and is configured to determine the authenticity of the RF tags 1 embedded in the products (that is, determine whether they are legitimate (genuine) or not). Note that 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 authenticity determination server 5 is not necessary.

[0025] The NFT management server 6 is composed of one or more server computers and functions as a web server on the communication network NW. The NFT management server 6 is also connectable to the blockchain system BS via the communication network NW and manages NFTs associated with (linked to) product identification information for identifying products. Note that even if multiple copies of the same product are in stock, the product identification information differs for each product, and therefore the NFTs associated with the product identification information also differ. The blockchain system BS is based on a P2P network consisting of multiple nodes (computers) connected to the communication network NW and is built using distributed applications and smart contracts provided by, for example, Ethereum or Polygon.

[0026] NFTs are used to prove ownership of goods and are issued from a specific contract address in the blockchain system BS according to the ERC721 standard, for example. 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 private blockchains other than public blockchains, such as Ethereum and Polygon, may also be applied to the blockchain system BS.

[0027] The NFT management server 6 is also connectable to the commodity trading system SS via the communications network NW. The commodity trading system SS provides a marketplace and processes commodity transactions (buying and selling) conducted on an online commodity trading site or a brick-and-mortar store (e.g., a POS terminal). In particular, when a commodity identified (specified) by commodity identification information associated with an NFT is traded on a commodity trading site or a brick-and-mortar store, the NFT management server 6 can acquire transaction information related to the transaction from the commodity trading system SS. This transaction information includes the transaction date and time, commodity identification information of the traded commodity, the user ID of the commodity seller who sold the commodity, and the user ID of the commodity buyer who purchased the commodity. Here, the commodity seller includes not only the commodity manufacturer, but also the commodity buyer who purchased the commodity from the commodity manufacturer, and the commodity buyer who purchased the commodity from the commodity buyer (hereinafter, these commodity buyers are referred to as "prior commodity buyers"). The user ID is user identification information used to identify a user who has been issued an account as a member of the NFT management system NS.

[0028] FIG. 2 is a diagram illustrating an example of the schematic configuration of an RF tag 1. As illustrated in FIG. 2, the RF tag 1 includes an antenna 11, an I / O circuit 12, a random access memory (RAM) 13, a read-only memory (ROM) 14, a nonvolatile memory (NVM) 15, and a central processing unit (CPU) 16. The antenna 11 receives radio waves containing an RF signal (including a command) transmitted from the tag manufacturer terminal 2, the product manufacturer terminal 3, or the product purchaser terminal 4, and transmits radio waves containing an RF signal (including a response) transmitted from the I / O circuit 12. The I / O circuit 12 demodulates the RF signal from the antenna 11 and outputs the demodulated signal to the CPU 16, or modulates a signal from the CPU 16 and outputs the modulated RF signal to the antenna 11. A program is stored in the ROM 14 or the NVM 15. Examples of the NVM 15 include flash memory and electrically erasable programmable read-only memory.

[0029] Furthermore, tag identification information and an individual key are stored in advance in NVM 15 by the tag manufacturer (for example, stored during the manufacturing stage of the RF tag 1). Here, as described above, the tag identification information is used as product identification information that identifies a product when the product manufacturer embeds the RF tag 1 in the product. The individual key is generated by inputting the tag identification information and performing an encryption operation such as an AES (Advanced Encryption Standard) operation using a predetermined master key as an encryption key, and is assigned to the tag identification information. Then, after the product identification information is linked to a unique NFT, a uniform resource locator (URL) (hereinafter referred to as the "management page URL") for accessing an NFT management server 6 (web server) that stores a management page (web page) dedicated to the product identified by the product identification information is stored in NVM 15 by the product manufacturer terminal 3.

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

[0031] Such a read command may be an NDEF (NFC Data Exchange Format) read command. If the RF tag 1 is set to be read in NDEF format, the read URL can be sent to the product purchaser terminal 4, even if the product purchaser terminal 4 does not have a dedicated application installed. After the counter value reaches its 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 if authentication of the encryption key representing the authority of the tag administrator (corresponding to the product manufacturer in this embodiment) is successful.

[0032] FIG. 3 is a diagram showing an example of the schematic configuration of the NFT management server 6. As shown in FIG. 3, the NFT management server 6 includes a communication unit 61, a storage unit 62, and an information processing unit 63. The communication unit 61 has a function of connecting to a communication network NW. The storage unit 62 is formed, for example, from 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. Note that the user information database 621 and the NFT information database 622 may be provided in a database server not shown.

[0033] The user information database 621 is a database for registering information about users who have been issued accounts as members of the NFT management system NS. The user information database 621 registers, in association with each user, a user ID, password, email address, address, telephone number, a key pair of a public key and a private key used in the blockchain system BS, and an individual address on the blockchain system BS. Here, the key pair of a public key and a private key is issued individually to each user in the blockchain system BS in response to a request from the NFT management server 6, for example, when an account is issued. The individual address is generated in accordance with a predetermined algorithm based on the public key. An NFT can be associated with the individual address in the blockchain system BS.

[0034] The NFT information database 622 is a database for registering information about NFTs issued in the blockchain system BS. The NFT information database 622 registers, in association with each NFT, the NFT's contract address, the NFT's token ID, the individual address of the user who owns the NFT (i.e., the individual address linked to the NFT), product identification information, a management page URL, and transaction information (which may be absent). Here, the management page URL is the address (corresponding to an IP address) of the NFT management server 6 (web server) where the management page is stored, and is expressed, for example, by a domain, a path (directory), and URL parameters (which may include a host name) generated from the product identification information. 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.

[0035] The information processing unit 63 is configured to include RAM, ROM, a CPU, etc., and functions as an issuance request receiving means, a URL generating means, a token issuing means, a token management means, a write command sending means, a transfer request receiving means, a validity determining means, a counter value determining means, an intention expression determining means, and a token transfer means, etc., in accordance with the NFT management program stored in the memory unit 62, and performs various processes.

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

[0037] The information processing unit 63 then issues an NFT on the blockchain system BS based on the product identification information, which is used by the product manufacturer to prove ownership of the product, and manages the issued NFT by associating the product identification information and a management page URL with it. For example, the product identification information and management page URL are associated with the contract address and token ID of the issued NFT, and are managed by being registered in the NFT information database 622. The information processing unit 63 then transmits a command to the product manufacturer terminal 3 via the communication network NW to write the management page URL to the RF tag 1. As a result, the management page URL is written to the RF tag 1. This efficiently reduces the risk of tampering with and copying of product identification information, and improves the convenience of proving product ownership.

[0038] In addition, when transferring an NFT associated with the product identification information of a product sold from a product manufacturer (or a previous product purchaser) to a product purchaser, the information processing unit 63 receives an NFT transfer request from the product purchaser terminal 4 via the communication network NW, the NFT transfer request including a new URL that includes an authentication code generated by cryptographic calculation of the RF tag 1 based on at least the URL for the management page, and that is obtained by the product purchaser terminal 4 from the RF tag 1 (i.e., the RF tag 1 embedded in the product).

[0039] The information processing unit 63 then determines whether the RF tag 1 is authentic based on the new URL included in the received NFT transfer request, and if it determines that the RF tag 1 is authentic, transfers the NFT from the product manufacturer (or the previous product purchaser) to the product purchaser on the blockchain system BS. This makes it possible to transfer the NFT linked to the product identification information recorded in the RF tag 1, provided that the product identification information is reliable. Note that whether the RF tag 1 is authentic or not can be determined based on the authenticity determination result of the RF tag 1 by the tag authenticity determination server 5. This allows for the use of more reliable authenticity determination results.

[0040] The new URL may also 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 unit 63 further determines whether the counter value is normal. If the information processing unit 63 determines that the RF tag 1 is authentic and that the counter value is normal, it transfers the NFT from the product manufacturer (or the previous product purchaser) to the product purchaser on the blockchain system BS. This makes it possible to transfer the NFT linked to the product identification information recorded in the RF tag 1, provided that the product identification information is even more reliable.

[0041] The information processing unit 63 may also determine whether the NFT transfer request conforms to the expression of intent of the NFT transfer source (i.e., the product manufacturer or the previous product purchaser). In this case, if the information processing unit 63 determines that the RF tag 1 is valid and that the NFT transfer request conforms to the expression of intent of the NFT transfer source, it transfers the NFT from the product manufacturer (or the previous product purchaser) to the product purchaser on the blockchain system BS. Alternatively, if the information processing unit 63 determines that the RF tag 1 is valid, that the counter value is normal, and that the NFT transfer request conforms to the expression of intent of the NFT transfer source, it transfers the NFT from the product manufacturer (or the previous product purchaser) to the product purchaser on the blockchain system BS.

[0042] [2. Operation of the NFT Management System NS] Next, the operation of the NFT management system NS according to this embodiment will be explained separately for the operation when issuing an NFT and the operation when transferring an NFT. Note that Figure 4 is a conceptual diagram showing an example of the flow of information exchange during the operation when issuing an NFT and the operation when transferring an NFT.

[0043] (2.1 NFT issuance behavior) First, the operation of the NFT management system NS when issuing an NFT will be described with reference to Fig. 5. Fig. 5 is a sequence diagram showing an example of the operation of the NFT management system NS when issuing an NFT.

[0044] 5, before a series of RF tags 1 to be embedded in each of a plurality of products are delivered to a product manufacturer, the tag manufacturer terminal 2 generates a master key for cryptographic calculations in accordance with instructions from the tag manufacturer (step S1) and stores the master key for manufacturing the series of RF tags 1. The master key thus generated is sent by the tag manufacturer to a tag authenticity determination service provider by a predetermined means and recorded in the tag authenticity determination server 5. Next, the tag manufacturer terminal 2 generates unique tag identification information for each RF tag 1 in accordance with instructions from the tag manufacturer (step S2).

[0045] Next, in accordance with instructions from the tag manufacturer, the tag manufacturer terminal 2 receives tag identification information as input, performs cryptographic calculations using the master key as an encryption key, and generates an individual key (step S3), as shown in (a) of Fig. 4, and assigns the individual key to the tag identification information. Note that the subsequent processing is performed for each RF tag 1. Next, in accordance with instructions from the tag manufacturer, the tag manufacturer terminal 2 transmits a write command including the tag identification information and the individual key to the RF tag 1 by contactless communication (step S4).

[0046] 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 in response to the write command (step S5), as shown in (b) of Fig. 4, and transmits a response indicating successful completion to the tag manufacturer terminal 2. In this way, a series of RF tags 1 in which the tag identification information and the individual key are saved (recorded) are shipped from the tag manufacturer and delivered to the product manufacturer. Note that the tag identification information and the individual key are different for each RF tag 1.

[0047] Next, the series of RF tags 1 received by the product manufacturer are embedded one by one in each product during the manufacturing process of each product. Then, in accordance with instructions from the product manufacturer, the product manufacturer terminal 3 transmits a command to read tag identification information to the RF tags 1 by contactless communication (step S6).

[0048] Next, when the RF tag 1 receives a read command from the product manufacturer terminal 3, it reads tag identification information from the NVM 15 in response to the read command, as shown in (c) of Fig. 4, and transmits a response including the tag identification information 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, it transmits an NFT issuance request including the tag identification information as product identification information to the NFT management server 6 via the communication network NW, as shown in (d) of Fig. 4 (step S9). Note that the NFT issuance request may further include product features and image data.

[0049] Next, when the NFT management server 6 receives an NFT issuance request from the product manufacturer terminal 3, it generates a management page URL (including a domain, path, and product identification information) dedicated to the product identified by the product identification information in response to the NFT issuance request, based on the product identification information, as shown in (e) of Figure 4. Next, the NFT management server 6 sends an NFT issuance request including the product identification information (or management page URL) and the individual address of the product manufacturer to the blockchain system BS (any node) as shown in (f) of Figure 4 (step S11).

[0050] In response to this NFT issuance request, an NFT linked to the product identification information is issued from a specific contract address in the blockchain system BS (step S12). The issued NFT is then linked to the product manufacturer's individual address, thereby recording in the blockchain that the NFT is owned by the product manufacturer. Next, an NFT issuance completion notification including the NFT's contract address, token ID, and the product manufacturer's individual address is sent from the blockchain system BS to the NFT management server 6 (step S13).

[0051] 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 from the product identification information using a predetermined algorithm may be specified as the token ID, or a unique token ID may be issued at a specific contract address in the blockchain system BS.

[0052] Next, when the NFT management server 6 receives an NFT issuance completion notification from the blockchain system BS, it registers information about 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. Note that the NFT information database 622 may also register product features and image data.

[0053] Next, as shown in (g) of Fig. 4, the NFT management server 6 transmits a write command to the product manufacturer terminal 3 via the communication network NW to write the management page URL to the RF tag 1 (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).

[0054] Next, when the RF tag 1 receives the write command from the product manufacturer terminal 3, it writes the management page URL to the NVM 15 in response to the write command (step S17), as shown in Fig. 4(h), and transmits a response indicating successful completion to the product manufacturer terminal 3. In this way, each product embedded with an RF tag 1 storing product identification information, an individual key, and a management page URL is shipped by the product manufacturer and registered (listed) in the product trading system SS.

[0055] (2.2 NFT Transfer Operation) Next, the operation of the NFT management system NS when transferring an NFT will be described with reference to Fig. 6. Fig. 6 is a sequence diagram showing an example of the operation of the NFT management system NS when transferring an NFT. After a product with an embedded RF tag 1 is put up for sale, when a transaction for that product is concluded, for example, on a product trading site or in a brick-and-mortar store, transaction information regarding that transaction is sent from the product trading system SS to the NFT management server 6.

[0056] To begin the process of transferring the NFT, which serves as proof of ownership of the purchased product, from the product manufacturer (or previous product purchaser) to the purchaser, the product purchaser brings their product purchaser terminal 4 close to the embedded part of the RF tag 1 in the product, and the RF tag 1 is activated by the electromagnetic field from the product purchaser terminal 4, starting contactless communication between the product purchaser terminal 4 and the RF tag 1. The product purchaser terminal 4 then transmits the above-mentioned NDEF read command to the RF tag 1 via contactless communication (step S21).

[0057] Next, when the RF tag 1 receives an NDEF read command from the product purchaser terminal 4, it reads the individual key and the counter value of the counter from NVM 15 in response to the NDEF read command, and as shown in (i) of Figure 4, it inputs data containing the counter value as a dynamic element and performs an encryption operation such as an AES operation using the individual key as an encryption key to generate a session key (step S22).

[0058] Next, the RF tag 1 reads the management page URL from the NVM 15, and generates a data block by linking the counter value to the management page URL in the form of a URL parameter and further adding the generated random number to the counter value in the form of a URL parameter (step S23), as shown in (j) of Fig. 4. Note that a data block in which the counter value is linked to the management page URL in the form of a URL parameter (i.e., a data block not including a random number) may be generated.

[0059] 4(k), the RF tag 1 receives data including the generated data block as a dynamic element and executes cryptographic operations such as AES operations using the generated session key as an encryption key to generate an authentication code (step S24). Alternatively, the RF tag 1 may receive a management page URL as an input and execute the cryptographic operations using the generated session key as an encryption key to generate an authentication code.

[0060] Next, the RF tag 1 sends a response in NDEF format to the product purchaser terminal 4, including a new URL in which the generated authentication code is linked to the data block in the form of a URL parameter (step S25). In other words, the product purchaser terminal 4 reads from the RF tag 1 a new URL in which the counter value, random number, and authentication code are added as URL parameters to the management page URL.

[0061] Next, when the product purchaser terminal 4 receives a response including the new URL expressed in NDEF format from the RF tag 1, it launches a web browser and, according to the acquired URL, accesses the NFT management server 6 (web server) via the communication network NW and sends a page request (step S26), as shown in (l) of Figure 4. This page request is an HTTP (Hypertext Transfer Protocol) request and includes the new URL acquired from the RF tag 1.

[0062] Next, in response to a page request from the product purchaser terminal 4, the NFT management server 6 (web server) obtains information about the NFT associated with the product identification information in the new URL included in the page request (e.g., the NFT contract address, the NFT token ID, and the individual address of the product manufacturer that owns the NFT) from the NFT information database 622 (step S27).

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

[0064] Next, when the product purchaser terminal 4 receives the management page from the NFT management server 6 (web server), it displays the management page using a web browser (step S29). The management page thus displayed displays a menu for operating the NFT linked to the product identification information, and when the product purchaser selects NFT transfer (i.e., acquisition of ownership) from the menu, 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 (web server) via the web browser over the communication network NW (step S30).

[0065] Next, when the NFT management server 6 receives an NFT transfer request from the product purchaser terminal 4, it sends an authenticity determination request including the new URL included in the NFT transfer request to the tag authenticity determination server 5 via the communication network NW to determine whether the URL is sent by a legitimate RF tag 1 (step S31).

[0066] Next, upon receiving an authentication determination request from the NFT management server 6, the tag authenticity determination server 5 performs an authentication determination of the RF tag 1 based on the new URL included in the authentication determination request (step S32) and transmits the authentication determination result to the NFT management server 6 (step S33). In determining the authenticity of the RF tag 1 in step S32, as shown in (m) of FIG. 4, the tag authenticity determination server 5 receives as input the product identification information acquired from the new URL included in the authentication determination request, and generates an individual key by performing a cryptographic operation such as an AES operation using a master key received in advance from the tag manufacturer and recorded as the encryption key. Next, as shown in (n) of FIG. 4, the tag authenticity determination server 5 receives as input data including the counter value acquired from the new URL as a dynamic element, and performs a cryptographic operation using the generated individual key as the encryption key to generate a session key.

[0067] Next, as shown in (o) of Fig. 4, the tag authenticity determination server 5 receives as input the data obtained by excluding the authentication code from the new URL and performs cryptographic calculations using the generated session key as an encryption key to generate an authentication code. Next, as shown in (p) of Fig. 4, the tag authenticity determination server 5 compares the generated authentication code with the authentication code obtained from the new URL and determines whether they match (i.e., verifies the authentication code), thereby determining the authenticity of the RF tag 1. For example, if the authentication codes match, the authenticity determination result indicates that the RF tag 1 is authentic. On the other hand, if the authentication codes do not match, the authenticity determination result indicates that the RF tag 1 is fake.

[0068] Next, when the NFT management server 6 receives the authenticity determination result from the tag authenticity determination server 5, it determines whether the RF tag 1 is authentic based on the authenticity determination result (step S34). If the authenticity determination result indicates that the RF tag 1 is fake, it is determined that the RF tag 1 is not authentic (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 authentic, it is determined that the RF tag 1 is authentic (step S34: YES), and the process proceeds to step S35.

[0069] In step S35, the NFT management server 6 determines whether the counter value acquired from the new URL included in the NFT transfer request is normal. This 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 a counter value linked to the product identification information, and checks that the counter value is incremented each time a counter value is acquired. If the stored counter value and the acquired counter value are equal or greater than the acquired counter value, the counting is not normal, and the counter value is determined to be abnormal (step S35: NO), and processing proceeds to step S37. On the other hand, if the counter value is determined to be normal (step S35: YES), processing proceeds to step S36.

[0070] In step S36, the NFT management server 6 determines whether the NFT transfer request conforms to the NFT transfer source's expression of intent (i.e., whether it indicates an intention to relinquish ownership of the product) based on the transaction information acquired from the product trading system SS. For example, if transaction information is acquired that includes product identification information acquired from a new URL included in the NFT transfer request and the user ID included in the NFT transfer request as the user ID of the product purchaser, the NFT transfer request is determined to conform to the NFT transfer source's expression of intent (step S36: YES), and processing proceeds to step S39. Note that if the NFT transfer source is the product manufacturer, the NFT transfer request may be determined to conform to the NFT transfer source's expression of intent without being based on the transaction information, because unspecified product purchasers are assumed as the NFT transfer destination. On the other hand, if it is determined to not conform to the NFT transfer source's expression of intent (step S36: NO), processing proceeds to step S37.

[0071] In step S37, the NFT management server 6 sends a response indicating a denial of the NFT transfer request to the product purchaser terminal 4. When the product purchaser terminal 4 receives the response indicating a denial from the NFT management server 6 (web server), it displays information indicating a failure of the NFT transfer (failure to acquire ownership) on the management page using the web browser (step S38).

[0072] In step S39, the NFT management server 6 sends an NFT transfer request to the blockchain system BS (any node), as shown in (q) of FIG. 4. This NFT transfer request includes the NFT token ID (or contract address and token ID) linked to the product identification information obtained from the new URL, the NFT source address (e.g., the individual address of the product manufacturer or the previous product purchaser), and the NFT destination address (e.g., the individual address of the product purchaser). In other words, the NFT transfer request indicates that the NFT (NFT token ID) is to be transferred from the source address to the destination address.

[0073] In response to this NFT transfer request, the NFT is transferred from the product manufacturer (or the previous product purchaser) to the product purchaser on the blockchain system BS (step S40). This links the NFT related to the transfer to the product purchaser's individual address, thereby recording on the blockchain that the NFT is owned by the product purchaser. Next, an NFT transfer completion notice including the NFT's contract address, token ID, and the product purchaser's individual address is sent from the blockchain system BS to the NFT management server 6 (step S41).

[0074] 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 source address of the NFT (e.g., the individual address of the product manufacturer or the previous product purchaser) is updated to the destination address of the NFT (e.g., the individual address of the product purchaser).

[0075] Next, the NFT management server 6 (web server) obtains information about the transferred NFT (for example, the NFT contract address, the NFT token ID, and the updated individual address of the product purchaser) from the NFT information database 622 (step S43). Next, the NFT management server 6 (web server) transmits a management page containing information about the NFT (i.e., the updated management page) to the product purchaser terminal 4 via the communications network NW, along with a response indicating approval of the NFT transfer request (step S44). Note that the management page dedicated to the product may further include product features and image data.

[0076] Next, when the product purchaser terminal 4 receives the updated management page and a response indicating permission from the NFT management server 6 (web server), it displays the management page using a web browser and displays information on the management page indicating that the NFT transfer was successful (ownership acquisition was successful) (step S45).

[0077] As described above, according to the above embodiment, when the NFT management server 6 receives an NFT issuance request from the product manufacturer terminal 3 via the communication network NW, the request includes product identification information read by the product manufacturer terminal 3 from the RF tag 1 embedded in the product. Based on the product identification information, the NFT management server 6 generates a management page URL dedicated to the product identified by the product identification information, issues an NFT on the blockchain system BS based on the product identification information for the product manufacturer to prove ownership of the product, associates the product identification information and the management page URL with the issued NFT and manages it, and writes the management page URL to the RF tag 1. This allows the product-specific information and management page URL linked to the NFT to be efficiently recorded on the RF tag 1, efficiently reducing the risk of tampering with and copying the product identification information and increasing the convenience of proving ownership of the product.

[0078] Furthermore, according to the above embodiment, when the NFT management server 6 receives an NFT transfer request from the product purchaser terminal 4 via the communication network NW, the request includes a new URL that includes an authentication code generated by cryptographic calculation of the RF tag 1 based on at least the management page URL, and the new URL is obtained from the RF tag 1 by the product purchaser terminal 4, the NFT management server 6 determines whether the RF tag 1 is legitimate based on the new URL, and if it determines that the RF tag 1 is legitimate, it transfers the NFT from the product manufacturer (or the previous product purchaser) to the product purchaser on the blockchain system BS.This makes it possible to verify the reliability of the product identification information recorded in the RF tag 1 before the NFT transfer, and the NFT linked to the product identification information can be transferred on the condition that the product identification information is reliable, thereby improving the convenience of proving ownership of the product corresponding to the transferred NFT while maintaining the reduction in the risk of tampering and duplication of the product identification information. [Explanation of symbols]

[0079] 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 ROM 15 NVM 16 CPU 61 Communications Department 62 Memory section 63 Information Processing Department NW communication network NS NFT Management System

Claims

1. A non-fungible token management device capable of communicating with a provider terminal of a provider that provides a tangible item to be traded via a communication network, an issuance request receiving means for receiving, from the provider terminal via the communication network, a non-fungible token issuance request including tangible object identification information read by the provider terminal from the IC tag embedded in the tangible object; 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 included in the non-fungible token issuance request, the URL including the tangible object identification information; a token issuing means for issuing a non-fungible token on a blockchain system based on the tangible object identification information, the non-fungible token being used by the provider to prove ownership of the tangible object; a token management means for managing the issued non-fungible token in association with the tangible entity identification information and the URL; a write 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:

2. the non-fungible token management device is capable of communicating with a purchaser terminal of a purchaser who purchases the tangible item via the communication network; a transfer request receiving means for receiving, from the purchaser terminal via the communication network, a non-fungible token transfer request including a new URL that includes an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag, the new URL being obtained from the IC tag by the purchaser terminal; a legitimacy determination means for determining whether the IC tag is legitimate by comparing the authentication code obtained from the new URL included in the non-fungible token transfer request with an authentication code generated by the same cryptographic calculation as the cryptographic calculation of the IC tag based on data obtained by excluding the authentication code from the new URL, and determining whether they match; a token transfer means for transferring the non-fungible token from the provider or the previous purchaser to the purchaser on the blockchain system when the IC tag is determined to be valid by the validity determination means; 2. The non-fungible token management device of claim 1, further comprising:

3. A non-fungible token management device capable of communicating with a purchaser terminal of a purchaser who purchases a tangible item to be traded via a communication network, a token management means for managing a non-fungible token issued on a blockchain system to prove ownership of the tangible object by associating the non-fungible token with tangible object identification information of the tangible object and a URL for accessing a web server that stores a management page dedicated to the tangible object identified by the tangible object identification information; a transfer request receiving means for receiving, from the purchaser terminal via the communication network, a non-fungible token transfer request including a new URL obtained from the IC tag by the purchaser terminal, the new URL including an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object; a legitimacy determination means for determining whether the IC tag is legitimate by comparing the authentication code obtained from the new URL included in the non-fungible token transfer request with an authentication code generated by the same cryptographic calculation as the cryptographic calculation of the IC tag based on data obtained by excluding the authentication code from the new URL, and determining whether they match; a token transfer means 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 IC tag is determined to be valid by the validity determination means; A non-fungible token management device comprising:

4. the new URL further includes a counter value that is incremented every time the new URL is read from the IC tag; further comprising a counter value determination means for determining whether the counter value is normal; A non-fungible token management device as described in claim 2 or 3, characterized in that 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 transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system.

5. The method further includes: determining whether the non-fungible token transfer request conforms to the expression of intent of the provider or the previous purchaser; The non-fungible token management device described in claim 2 or 3, characterized in that when the validity determination means determines that the IC tag is valid and the expression of intention determination means determines that the non-fungible token transfer request conforms to the expression of intention of the provider or previous purchaser, the token transfer means transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system.

6. the new URL further includes a counter value that is incremented every time the new URL is read from the IC tag; a counter value determination means for determining whether the counter value is normal; An intention determination means for determining whether the non-fungible token transfer request conforms to the intention of the provider or the previous purchaser; Further provided with The non-fungible token management device of claim 2 or 3, characterized in that when 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 expression of intention determination means determines that the non-fungible token transfer request conforms to the expression of intention of the provider or previous purchaser, the token transfer means transfers the non-fungible token from the provider or previous purchaser to the purchaser on the blockchain system.

7. The new URL includes the original URL, A non-fungible token management device as described in any one of claims 2 to 6, characterized in that the validity determination means determines that the IC tag is valid when the authentication code contained in the new URL matches an authentication code generated by cryptographic calculation based on at least the original URL contained in the new URL.

8. A non-fungible token management method executed by a computer that can communicate with a provider terminal of a provider that provides a tangible item to be traded via a communication network, receiving, from the provider terminal via the communication network, a non-fungible token issuance request including tangible object identification information read by the provider terminal from an IC tag embedded in the tangible object; generating a URL for accessing a web server that stores a management page dedicated to the tangible object identified by the tangible object identification information included in the non-fungible token issuance request, the URL including the tangible object identification information; A step of issuing a non-fungible token on a blockchain system based on the tangible object identification information, for the provider to prove ownership of the tangible object; managing the issued non-fungible token in association with the tangible entity identification information and the URL; 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:

9. A computer that can communicate with a provider terminal of a provider that provides a tangible item to be traded via a communication network, an issuance request receiving means for receiving, from the provider terminal via the communication network, a non-fungible token issuance request including tangible object identification information read by the provider terminal from the IC tag embedded in the tangible object; 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 included in the non-fungible token issuance request, the URL including the tangible object identification information; a token issuing means for issuing a non-fungible token on a blockchain system based on the tangible object identification information, the non-fungible token being used by the provider to prove ownership of the tangible object; a token management means for managing the issued non-fungible token in association with the tangible entity identification information and the URL; A program that functions as a write command transmitting means that transmits a command to write the URL to the IC tag to the provider terminal via the communication network.

10. A non-fungible token management method executed by a computer that can communicate with a purchaser terminal of a purchaser who purchases a tangible item to be traded via a communication network, a step of associating and managing a non-fungible token issued on a blockchain system to prove ownership of the tangible object with tangible object identification information of the tangible object and a URL for accessing a web server that stores a management page dedicated to the tangible object identified by the tangible object identification information; receiving a non-fungible token transfer request from the purchaser terminal via the communication network, the non-fungible token transfer request including a new URL obtained from the IC tag by the purchaser terminal, the new URL including an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object; a step of determining whether the IC tag is authentic by comparing the authentication code obtained from the new URL included in the non-fungible token transfer request with an authentication code generated by the same cryptographic calculation as the cryptographic calculation of the IC tag based on data obtained by excluding the authentication code from the new URL and determining whether they match; If the IC tag is determined to be authentic, transferring the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser on the blockchain system; A non-fungible token management method comprising:

11. A computer that can communicate with a purchaser terminal of a purchaser who purchases a tangible item to be traded via a communication network, a token management means for managing a non-fungible token issued on a blockchain system to prove ownership of the tangible object by associating the non-fungible token with tangible object identification information of the tangible object and a URL for accessing a web server that stores a management page dedicated to the tangible object identified by the tangible object identification information; a transfer request receiving means for receiving, from the purchaser terminal via the communication network, a non-fungible token transfer request including a new URL obtained from the IC tag by the purchaser terminal, the new URL including an authentication code generated by cryptographic calculation of the IC tag based on at least the URL written in the IC tag embedded in the tangible object; a legitimacy determination means for determining whether the IC tag is legitimate by comparing the authentication code obtained from the new URL included in the non-fungible token transfer request with an authentication code generated by the same cryptographic calculation as the cryptographic calculation of the IC tag based on data obtained by excluding the authentication code from the new URL, and determining whether they match; A program characterized by functioning as a token transfer means on the blockchain system to transfer the non-fungible token from the provider or previous purchaser of the tangible object to the purchaser when the validity determination means determines that the IC tag is valid.

Images