WO2023013279A1

WO2023013279A1 - Sold merchandise management system, sold merchandise management method, and program

Info

Publication number: WO2023013279A1
Application number: PCT/JP2022/025095
Authority: WO
Inventors: 太郎鵜川; 寛史大橋
Original assignee: 株式会社プレイシンク
Priority date: 2021-08-06
Filing date: 2022-06-23
Publication date: 2023-02-09
Also published as: JP7397534B2; JP2024015486A; JPWO2023013279A1

Abstract

[Problem] To suppress occurrence of reselling. [Solution] This sold merchandise management system 1 includes: an NFT relation database 13 for storing an NFT management table T2, which stores a token ID of an NFT that is associated with a serial code of a piece of merchandise, and identifies the merchandise; an application server 10 for receiving an input of a serial code of a piece of merchandise from a user; and an NFT management server 12 for recording, in a blockchain, a transfer transaction indicating the transfer, to the user who entered the serial code, of an NFT stored in the NFT management table T2 and associated with the serial code that has been input to the application server 10.

Description

Sold merchandise management system, sold merchandise management method, and program

The present invention relates to a sold merchandise management system, a sold merchandise management method, and a program.

Conventionally, a sales system that sells real goods such as figures is known. Patent Literature 1 discloses an example of such a sales system. According to the sales system of Patent Literature 1, it is said that the product supply side can grasp the status of purchase applications in real time, and can secure an appropriate product inventory.

JP-A-2002-163502

By the way, in recent years, due to the rise of flea market apps, the buying and selling of products between individuals has become popular, and along with this, auctions (so-called resellers) and elaborate counterfeits (counterfeiting) have become social problems. If left unattended, the market could be destroyed, and a solution is urgently needed. In addition, there was a need to improve the fact that there is no return to the producer (manufacturer) in the conventional second-hand market (secondary market) including flea market apps.

Accordingly, one of the objects of the present invention is to provide a sold merchandise management system, a sold merchandise management method, and a program capable of preventing destruction of the market by bidding and counterfeits, and realizing returns from the used market to manufacturers. Regarding.

The sold product management system according to the present invention includes an NFT relation database storing an NFT management table that stores NFT token IDs that specify the product in association with the serial code of the product, and an NFT relation database that stores the serial code of the product from the user. An application server that accepts and a transfer transaction indicating the transfer of the NFT stored in the NFT management table in association with the serial code entered in the application server to the user who entered the serial code is recorded in the blockchain. and a NFT management server that manages the sold merchandise.

A sold product management method according to the present invention is executed by a computer connected to an NFT relation database that stores an NFT management table that stores an NFT token ID that identifies a product in association with a product serial code. A product management method, wherein the computer receives an input of a product serial code from a user; and recording a transfer transaction on the blockchain indicating transfer to the user who entered the code.

A program according to the present invention inputs a product serial code from a user to a computer connected to an NFT relation database that stores an NFT management table that stores an NFT token ID that identifies the product in association with the product serial code. a step of receiving; and a step of recording, on a blockchain, a transfer transaction indicating transfer of the NFT stored in the NFT management table in association with the received serial code to the user who entered the serial code. It is a program to run.

According to the present invention, it becomes possible to track products after they have been sold by referring to the blockchain. Since it is also possible to give incentives to consumers to hold long-term stocks, it is possible to prevent market destruction due to auctions and counterfeits. In addition, since sales on the second-hand market can be tracked, it is also possible to return commissions, etc. for sales from the second-hand market to the producer.

1 is a diagram showing the configuration of a system including a sold merchandise management system 1 according to this embodiment; FIG. 1 is a diagram showing an example of hardware configurations of a sold merchandise management system 1, a user terminal 2, and an operator terminal 3; FIG. 1 is a diagram showing an internal configuration of a sold merchandise management system 1; FIG. 3 is a diagram showing a user table T1 stored in an application database 11; FIG. (a) is a diagram showing an NFT management table T2 stored in the NFT relation database 13, and (b) is a diagram showing an NFT linkage table T3 stored in the NFT relation database 13. FIG. (a) is a diagram showing an incentive table T4 stored in the NFT relation database 13, and (b) is a diagram showing an achievement mission table T5 stored in the NFT relation database 13. FIG. 3 is a sequence diagram showing processing executed by the operator terminal 3 and each server in the sold merchandise management system 1. FIG. 3 is a sequence diagram showing processing executed by the operator terminal 3 and each server in the sold merchandise management system 1; FIG. FIG. 9 is a diagram showing transition of screens displayed on the operator terminal 3 in the process shown in FIG. 8; 3 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold merchandise management system 1. FIG. 3 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold merchandise management system 1. FIG. 3 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold merchandise management system 1. FIG. FIG. 13 is a diagram showing transition of screens displayed on the user terminal 2 during the processing shown in FIGS. 10 to 12; FIG. 3 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold merchandise management system 1. FIG. 3 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold merchandise management system 1. FIG. FIG. 16 is a diagram showing transition of screens displayed on the user terminal 2 in the process shown in FIGS. 14 and 15; FIG.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a diagram showing the configuration of a system including a sold merchandise management system 1 according to this embodiment. A sold product management system 1 is a system for managing products (real goods) sold at a real shop such as a figure shop or an online shop such as an EC site. It is connected to a user terminal 2, an operator terminal 3, and a blockchain network 4 via a network 5, which is the Internet.

To explain the outline of the processing performed by the sold merchandise management system 1, the sold merchandise management system 1 first assigns a serial code to each merchandise before sale, and an NFT (non-fungibility code) containing the assigned serial code. token) is recorded in the blockchain network 4. A user who has purchased a product at a shop accesses the sold product management system 1 from the user terminal 2 and inputs the serial code assigned in advance to the product. The sold merchandise management system 1 that has received this input associates and stores the input serial code and the user ID of the input user, and transmits a transfer transaction indicating the transfer of ownership of the NFT to the blockchain network 4. to record. This makes it possible to track the product after sale by referring to the blockchain network 4 (that is, to check the history of the user who owns the product), and as a result, the resale of the product by the consumer becomes possible. Since it becomes possible to suppress psychologically and to give consumers an incentive to keep the product for a long time, it is possible to prevent the destruction of the market due to auctions and counterfeits. In addition, since sales on the second-hand market can be tracked, it is also possible to return commissions, etc. for sales from the second-hand market to the producer.

FIG. 2 is a diagram showing an example of the hardware configuration of the sold merchandise management system 1, the user terminal 2, and the operator terminal 3. The sold merchandise management system 1, the user terminal 2, and the operator terminal 3 can each be configured by a computer 100 having the illustrated configuration. In a typical example, the computer 100 that constitutes the sold merchandise management system 1 is a high-performance computer that functions as a server. A computer 100 constituting the user terminal 2 or the operator terminal 3 is a personal computer such as a personal computer, a tablet terminal, or a smart phone. Note that the computer 100 may be a computer configured by combining a plurality of computers.

As shown in FIG. 2, the computer 100 includes a CPU (Central Processing Unit) 101, a storage device 102, an input device 103, an output device 104, and a communication device 105.

The CPU 101 is a device that controls each part of the computer 100 and reads and executes various programs stored in the storage device 102 . Each of the

servers

10 and 12 shown in FIG. 3, which will be described later, is a virtual virtual machine realized by executing a program stored in the storage device 102 of the sold merchandise management system 1 by the CPU 101 of the sold merchandise management system 1. computer. However, when the computer 100 is configured by combining a plurality of computers as described above, the

servers

10 and 12 shown in FIG. , the functions of the

servers

10 and 12 are implemented by the CPU 101 of each computer executing programs stored in the respective storage devices 102 . Also, the programs executed by the CPU 101 of the user terminal 2 or operator terminal 3 include browser software or mobile applications that have a function of accessing other devices via the network 5 .

The storage device 102 includes a main storage device such as a DRAM (Dynamic Random Access Memory) and an auxiliary storage device such as a hard disk. A device that serves to store data used by the programs of

Databases

11 and 13 shown in FIG. 3 (to be described later) are installed in storage device 102 of sold merchandise management system 1 .

The input device 103 is a device that receives a user's input operation and supplies it to the CPU 101, and includes, for example, a keyboard, a mouse, and a touch panel. The output device 104 is a device that outputs the processing result of the CPU 101 to the user, and includes, for example, a display and a speaker. A communication device 105 is a device for communicating with an external device, and transmits and receives data according to instructions from the CPU 101 . The sold merchandise management system 1, the user terminal 2, and the operator terminal 3 each use this communication device 105 to communicate with other devices including the blockchain network 4 and network 5 shown in FIG. configured as follows.

Return to Figure 1. Blockchain network 4 is a network of multiple computers connected by peer-to-peer, transferring NFT ownership between wallet addresses assigned to each user (including sold merchandise management system 1) (transfer transaction), And it is configured to record the association (issue transaction) of the newly generated NFT with any wallet address in the blockchain.

Generally, there are three types of blockchains: public chains without a specific administrator, private chains managed by a single organization, and consortium chains managed by multiple organizations. Any of these may be used. In a typical example, the blockchain network 4 is either the Ethereum network, which is classified as a public chain, or the LINE blockchain, which is classified as a private chain. In the following description, the blockchain network 4 is assumed to be the Ethereum network.

　Transactions are recorded on the blockchain by several computers (hereinafter referred to as "miners") connected to the blockchain network 4. Specifically, each block that constitutes the blockchain includes a block header and data (transaction data) that indicates the specific contents of a transaction. Among these, the block header includes a Merkle root, which is data obtained by compressing the size of transaction data, a hash value of the previous block, and a nonce value, which is an arbitrary character string. In the blockchain network 4, in order to connect a new block to the blockchain, the hash value of that block must satisfy a predetermined condition (for example, a value starting with "000"). There are rules. Therefore, a miner who intends to record a block in the blockchain brute forcely finds a nonce value (mining) so that the hash value of the block header of that block satisfies the above-mentioned predetermined conditions. As a result of this work, the miner that succeeds in discovering the nonce value earliest will link that block to the blockchain, completing the recording of the transaction on the blockchain.

If the blockchain network 4 is the Ethereum network, those who want to record transactions on the blockchain must pay a fee called "gas" in virtual currency. Gas is paid out as a reward to miners who successfully concatenate blocks.

FIG. 3 is a diagram showing the internal configuration of the sold merchandise management system 1. As shown in FIG. As shown in the figure, the sold merchandise management system 1 includes an application server 10 , an application database 11 , an NFT management server 12 and an NFT relation database 13 .

The application server 10 is a server that functions as an interface with the user terminal 2 . A user who has purchased a product at a figure shop or the like shown in FIG. Enter the serial code of

Here, the method by which the user obtains the serial code of the product is not particularly limited. For example, the shop may hand over a piece of paper on which the serial code is written together with the product, or may attach a sticker on which the serial code is written to the product. Also, if the serial code is written in the IC chip embedded in the product, the user can obtain the serial code by reading the information in the IC chip using the user terminal 2. . In the case of purchase at an online shop, the serial code may be automatically entered on the server side when transitioning from the purchase screen to the serial code input screen.

The application database 11 is a database that stores various data used for processing performed by the application server 10. Data stored in the application database 11 includes a user table T1. Details of the user table T1 will be described later with reference to FIG.

The NFT management server 12 is a server that functions as an interface with the operator terminal 3 and the blockchain network 4. Specifically, the operator terminal 3 accepts registration of pre-sale products, issues a serial code, records the NFT issuance transaction including the assigned serial code in the blockchain network 4, and records the transaction of the issuance transaction. A process of registering the ID (token ID) and the serial code in the NFT relation database 13 in association with each other is performed. In addition, the NFT management server 12 associates the serial code received by the application database 11 with the user ID and registers it in the NFT relation database 13, and transmits a transfer transaction indicating the transfer of ownership of the corresponding NFT to the blockchain network 4 process to record to

The NFT relation database 13 is a database that stores various data used for processing performed by the NFT management server 12. Data stored in the NFT relation database 13 includes an NFT management table T2, an NFT cooperation table T3, an incentive table T4, and an achievement mission table T5. These details will be explained later in detail with reference to FIGS. 5 and 6. FIG.

FIG. 4 is a diagram showing the user table T1 stored in the application database 11. FIG. The user table T1 is a table for storing information on users of the sold merchandise management system 1, and as shown in the figure, is configured to store user IDs, passwords, and session IDs in association with each other. be. A user ID is identification information uniquely assigned to a user of the sold merchandise management system 1 . A password is used for authentication when a user logs into the application server 10 .

A session ID is identification information for identifying a user during communication. Although "ID1", "ID2", etc. are described in FIG. 4, the actual session ID is composed of a longer random character string. The application server 10 assigns a new session ID at login, stores it in the user table T1 in association with the user ID of the logged-in user, and deletes it at logout. While the user is logged in, this session ID is placed in messages sent and received between the user terminal 2 and each server in the sold merchandise management system 1, and identifies the sender and destination of the message. used for

FIG. 5(a) is a diagram showing the NFT management table T2 stored in the NFT relation database 13. FIG. The NFT management table T2 is a table for storing detailed information of each product, and as shown in the figure, serial code, product type ID, product name, sales price, thumbnail information, NFT are stored in association with each other. A serial code is a code for identifying each product, and is uniquely assigned to each product handled by the sold product management system 1 . The product type ID is a code for identifying the product type, and is uniquely assigned to the product type handled by the sold product management system 1 . The product name is a character string that allows humans to easily identify the type of the corresponding product, and is uniquely assigned to the product type handled by the sold product management system 1 . The sales price is the price at which a new product of the corresponding product is sold. Thumbnail information is information indicating an image file representing the corresponding product. NFT is the token ID of the NFT containing the corresponding serial code.

FIG. 5(b) is a diagram showing the NFT linkage table T3 stored in the NFT relation database 13. FIG. The NFT linkage table T3 is a table for storing serial codes of products owned by individual users. .

FIG. 6(a) is a diagram showing an incentive table T4 stored in the NFT relation database 13. FIG. Each record in the incentive table T4 indicates a mission to be accomplished by the user, and includes a mission ID, mission name, conditions, and remuneration information indicating remuneration, as shown in the figure. The mission ID is a code for identifying each mission, and is uniquely assigned to each mission handled by the sold merchandise management system 1. FIG. A mission name is a character string assigned to each mission, and plays a role in helping the user understand the mission content. The condition is a condition for mission achievement, and includes one or more product type IDs. Reward information is information indicating a reward given to a user who has accomplished a mission. Specifically, as illustrated in FIG. 6A, it is preferable to use (a character string indicating) an image file and a method of obtaining not-for-sale items as remuneration information.

FIG. 6(b) is a diagram showing an accomplished mission table T5 stored in the application database 11. FIG. The achieved mission table T5 is a table for storing missions achieved by individual users. Zero or more mission IDs stored in the incentive table T4 are arranged in the accomplished mission.

Sequence diagrams of processes executed by the operator terminal 3, the user terminal 2, and each server in the sold merchandise management system 1, and diagrams showing transitions of screens displayed on the operator terminal 3 and the user terminal 2 are shown below. The processing performed by the sold merchandise management system 1 will be described in detail with reference to FIG.

7 and 8 are sequence diagrams showing the processing executed by the operator terminal 3 and each server in the sold merchandise management system 1. FIG. 9 is a sequence diagram displayed on the operator terminal 3 during the processing shown in FIG. FIG. 10 is a diagram showing transition of screens to be displayed;

Fig. 7 shows the process for assigning serial codes to products before they are sold. Specifically, first, a product registration request is transmitted from the operator terminal 3 to the NFT management server 12 in response to an operation by the operator (step S1). This product registration request includes the product type ID, product name, sales price, and thumbnail information shown in FIG. 5A, and information indicating the number of products to be registered.

Upon receiving the product registration request, the NFT management server 12 issues a number of serial codes equal to the number of products to be registered (step S2). Then, the NFT management server 12 generates an NFT including the issued serial code, and records the issued transaction of the generated NFT in the blockchain network 4 with the wallet address of the sold merchandise management system 1 as the owner (step S3). . As a result, the newly generated NFT is associated with the wallet address of the sold product management system 1, and the NFT token ID (transaction ID indicating the NFT issuance transaction) is sent from the blockchain network 4 to the NFT management server 12. is returned (step S4). The NFT management server 12 that has acquired the token ID in this way associates the issued serial code with the corresponding product type ID, product name, sales price, thumbnail information, and token ID, and registers them in the NFT management table T2 ( step S5).

Next, the NFT management server 12 transmits the issued serial code to the operator terminal 3 (step S6). The operator adds the serial code acquired in this way to the product (step S7), and completes the registration of the product. Specific methods for adding a serial code include, as described above, writing the serial code on paper attached to the product, pasting a sticker with the serial code on the product, and embedding the serial code in the product. For example, a serial code is written in the IC chip.

Next, FIG. 8 shows the processing for the operator to confirm the information of the products registered in the NFT relation database 13. Specifically, first, a list display request is transmitted from the operator terminal 3 to the NFT management server 12 in response to an operation by the operator (step S10). The NFT management server 12 that has received this list display request refers to the NFT management table T2 in the NFT relation database 13 (step S11), and information including product type ID, product name, sales price, and thumbnail information (hereinafter " product information”) is taken out (step S12). Then, a product list screen is generated based on the extracted product information and returned to the operator terminal 3 (step S13).

FIG. 9(a) is a diagram showing a product list screen W1 displayed on the display of the operator terminal 3. FIG. As shown in the figure, the product list screen W1 is a screen that displays a list of a plurality of tiles 20 each representing a product. Each tile 20 displays the product image and product name indicated by the corresponding product information. Although not shown, each tile 20 may also display the selling price. This point also applies to

tiles

23 and 28, which will be described later.

Return to Figure 8. When the operator selects a product by tapping one of the tiles 20 on the product list screen W1 (step S14), the product type ID of the selected product is transmitted from the operator terminal 3 to the NFT management server 12 ( step S15). The NFT management server 12 that has received this product type ID retrieves one or more corresponding serial codes from the NFT management table T2 (steps S16, S17), and then one or more serial codes corresponding to the retrieved one or more serial codes. The user ID is taken out from the NFT linkage table T3 (steps S18, S19). Then, based on the retrieved serial code and user ID, a product detail screen is generated and returned to the operator terminal 3 (step S20).

FIG. 9(b) is a diagram showing a product details screen W2 displayed on the display of the operator terminal 3. As shown in the figure, the product detail screen W2 includes an enlarged tile 20 of the selected product and an NFT list 21. As shown in FIG. The NFT list 21 is a list of serial codes and user IDs extracted in steps S17 and S19.

Return to Figure 8. When the operator selects a serial code by tapping any line in the NFT list 21 of the product detail screen W2 (step S21), the selected serial code is transmitted from the operator terminal 3 to the NFT management server 12. (Step S22). The NFT management server 12 that has received this serial code first takes out the token ID of the corresponding NFT from the NFT management table T2 (steps S23 and S24). Subsequently, the NFT management server 12 inquires of the blockchain network 4 about the possession user history of the NFT corresponding to the extracted token ID (step S25). In short, this process is a process of acquiring the history of users who have possessed the corresponding NFT by collecting and referring to the corresponding transfer transactions (details will be described later), and as a result of the inquiry, the NFT The management server 12 acquires the possession user history (step S26). The NFT management server 12 generates an NFT detail screen based on the acquired possession user history, and returns it to the operator terminal 3 (step S27).

FIG. 9(c) is a diagram showing the NFT details screen W3 displayed on the display of the operator terminal 3. As shown in the figure, the NFT detail screen W3 includes an enlarged tile 20 of the corresponding product and a possession user history 22 . The possession user history 22 is a list of possession user histories acquired in step S26. Each record in the possessing user history 22 includes an event that caused the transfer (sale of a new product, transfer between users, etc.), the amount (price) of money transferred with the transfer, the user who transferred, and the transfer. It consists of the previous user and the date on which the transfer occurred.

10 to 12, 14, and 15 are sequence diagrams showing the processing executed by the user terminal 2 and each server in the sold merchandise management system 1. FIG. 13 is a diagram showing the transition of screens displayed on the user terminal 2 during the processes shown in FIGS. 10 to 12, and FIG. 2 is a diagram showing the transition of screens displayed in FIG.

10 to 12 show the processing for the user of the user terminal 2 to log in to the sold merchandise management system 1 and the processing for registering the serial code of the purchased merchandise in the sold merchandise management system 1. ing. Specifically, a user who attempts to log in to the sold merchandise management system 1 transmits a login request to the application server 10 by operating the user terminal 2 (step S30). This login request includes the combination of the user ID and password shown in FIG.

The application server 10 that has received the login request determines whether the combination of the user ID and password contained therein exists in the user table T1. As a result, the application server 10 that has determined that it does not exist returns a login NG to the user terminal 2 and terminates the process. On the other hand, the application server 10, which has determined to exist, assigns a new session ID to the user, holds it in the user table T1 (step S31), and returns it to the user terminal 2 (step S32). This session ID is then arranged in messages sent and received between the user terminal 2 and each server in the sold merchandise management system 1, and is used to identify the source and destination of the message. be.

Here, even when the operator terminal 3 accesses the sold merchandise management system 1 in order to execute the processing described with reference to FIGS. 7 and 8, the same login processing as in the user terminal 2 is required. may be In this case, it is preferable to provide an authority information column in the user table T1 so that it is possible to identify whether the user is logged in as the user terminal 2 or the operator terminal 3 . Then, it is preferable that the processing described with reference to FIGS. 7 and 8 can be executed only when logged in as the operator terminal 3 .

A user who has logged in to the sold merchandise management system 1 and intends to register the serial code of the purchased merchandise in the sold merchandise management system 1 operates the user terminal 2 to send an NFT to the application server 10. A cooperation request is transmitted (step S40). The application server 10 that has received this NFT cooperation request transmits a product information inquiry for inquiring information of all products to be registered to the NFT management server 12 (step S41). The NFT management server 12 refers to the NFT management table in response to this product information inquiry, and extracts the product information described above for each product type ID (step S43). Then, the retrieved product information is returned to the application server 10 (step S44). The application server 10 generates a product selection screen based on the product information thus received, and returns it to the user terminal 2 (step S45).

FIG. 13(a) is a diagram showing a product selection screen W4 displayed on the display of the user terminal 2. FIG. As shown in the figure, the product selection screen W4 is a screen that displays a list of a plurality of tiles 23 each representing a product. Each tile 23 displays the product image and product name indicated by the corresponding product information.

Return to Figure 10. When the user selects a product by tapping one of the tiles 23 on the product selection screen W4 (step S46), the product type ID of the selected product is transmitted from the user terminal 2 to the application server 10 (step S47). The application server 10 that has received this product type ID generates a code input screen for inputting the serial code and returns it to the user terminal 2 (step S48).

FIG. 13(b) is a diagram showing the code input screen W5 displayed on the display of the user terminal 2. FIG. As shown in the figure, the code input screen W5 includes an enlarged tile 23 of the selected product, a serial code input field 24, and a registration button 25. As shown in FIG.

Return to Figure 10. On the code input screen W5, the user inputs the serial code of the purchased product in the serial code input field 24 and presses the registration button 25 to input the serial code to the application server 10 (steps S49 and S50). The application server 10 transmits the serial code thus input to the NFT management server 12 together with the user ID of the user (step S51).

The NFT management server 12 that has received the combination of the serial code and the user ID first retrieves the token ID of the corresponding NFT from the NFT management table T2 (steps S52, S53), and inquires about its current owner to the blockchain network 4 ( step S54). In short, this process is a process of acquiring the user who currently possesses the corresponding NFT by gathering and referring to the corresponding transfer transaction, and as a result of the inquiry, the NFT management server 12 obtains the current owner. The indicated NFT ownership information is acquired (step S55).

The NFT management server 12 matches the user indicated by the NFT ownership information acquired in step S55 with the user indicated by the user ID stored in the NFT linkage table T3 in association with the serial code received in step S51. (steps S56 to S58). As a result, when it is determined that they do not match, the NFT management server 12 transmits an error notification to the user terminal 2 via the application server 10 (steps S59 and S60). In this case, the serial code entered by the user in step S49 is not registered in the sold merchandise management system 1 as that of the user. By performing this processing, it is possible to prevent double transfer from occurring when the ownership of the NFT is transferred in a place unrelated to the sold merchandise management system 1.

On the other hand, if it is determined that they match in step S58, the NFT management server 12 stores the user ID stored in the NFT linkage table T3 in association with the serial code received in step S51. (step S61), generate a transfer transaction indicating that the ownership of the corresponding NFT is transferred to the wallet address of the user indicated by the user ID, and record it in the blockchain network 4 (step S62). The transfer transaction generated and recorded in this way includes the event that caused the transfer (in this case, the sale of a new product), the sales price recorded in the NFT management table T2, and the sales as the transfer source user. Information indicating the finished product management system 1 (denoted as “user0” in FIG. 9C), information indicating the transfer destination user (the user indicated by the user ID received in step S51), and information indicating the transfer date of occurrence.

Next, the NFT management server 12 retrieves one or more serial codes stored in association with the user ID received in step S51 from the NFT linkage table T3 (steps S63, S64), One or more product type IDs are taken out from the NFT management table T2 (steps S65 and S66).

Subsequently, the NFT management server 12 retrieves the mission ID of the mission including the product type ID acquired in step S66 from the incentive table T4 (steps S67, S68), and retrieves the mission ID of the mission that has been achieved by the corresponding user. Take out from table T5 (steps S69, S70). Then, by comparing these, the mission newly achieved this time (that is, the mission that the user's possessed product satisfies the conditions for being stored in the incentive table T4 and has not yet been achieved by the user) (step S71). As a result, the NFT management server 12, which determines that there is no newly accomplished mission, returns a completion notification to the application server 10 (step S72), and ends the process. On the other hand, the NFT management server 12, which has determined that there is a newly achieved mission, retrieves information indicating the newly achieved mission and its reward (hereinafter referred to as "newly achieved mission information") from the incentive table T4 (step S73 , S74), and returns it to the application server 10 together with a completion notification (step S75). Then, the NFT management server 12 updates the achieved mission table T5 by adding the mission indicated by the new achieved mission information to the corresponding user's already achieved mission (step S76), and ends the process.

The application server 10 that has received the completion notification in step S72 or step S75 generates a code input completion screen and transmits it to the user terminal 2 (step S77).

FIG. 13(c) shows the code input completion screen W6 displayed on the display of the user terminal 2. FIG. As shown in the figure, the code input completion screen W6 includes a sentence 26 indicating that the registration of the selected product has been completed, and new achievement mission information 27 indicating the reward given to the user. The newly achieved mission information 27 is the newly achieved mission information received by the application server 10 in step S75 of FIG. 12, and includes a mission name, an image (or text) as a reward, and the like.

14 and 15 show the process for the user of the user terminal 2 to confirm the list of products owned by him/herself and their details. Specifically, the user first transmits an NFT confirmation request to the application server 10 by operating the user terminal 2 (step S80). The application server 10 that has received this NFT confirmation request transmits the user ID of the user who has transmitted the NFT confirmation request to the NFT management server 12 (step S81).

Upon receiving the user ID, the NFT management server 12 retrieves the corresponding serial code from the NFT linkage table T3 (steps S82, S83). Next, the NFT management server 12 retrieves the product information of the product corresponding to the retrieved serial code from the NFT management table T2 (steps S84 and S85), and transmits it to the application server 10 (step S86). The application server 10 generates a possessed product list screen based on the product information thus received, and returns it to the user terminal 2 (step S87).

FIG. 16(a) is a diagram showing a possessed product list screen W7 displayed on the display of the user terminal 2. FIG. As shown in the figure, the product selection screen W4 is a screen that displays a list of a plurality of tiles 28 indicating one or more products owned by the user. Each tile 28 is indicated by corresponding product information. The product image and product name to be displayed are displayed. If the user owns a plurality of products of the same type (products having the same product type ID), the same number of tiles 28 are displayed.

Return to Figure 14. When the user selects a product by tapping one of the tiles 28 on the possessed product list screen W7 (step S88), the serial number of the selected product is sent from the user terminal 2 to the NFT management server 12 via the application server 10. A code is transmitted (steps S89, S90).

The NFT management server 12 that has received the serial code in step S90 first refers to the NFT management table T2 and extracts the corresponding product type ID (steps S91 and S92). Subsequently, the NFT management server 12 takes out a mission ID related to the extracted product type ID (a mission ID whose product type ID is included in the corresponding "condition") from the incentive table T4 (steps S93, S94), and further, By referring to the achieved mission table T5, among the mission IDs extracted in step S94, those that have been achieved by the corresponding user (accomplished mission IDs) are obtained (steps S95 and S96).

Next, the NFT management server 12 refers to the NFT management table T2 again and retrieves the token ID of the NFT corresponding to the serial code received in step S90 (steps S97 and S98). Then, the block chain network 4 is inquired about the history of the user possessing the corresponding NFT (step S99). The details of this process are the same as in step S25 of FIG. 8, and as a result of the inquiry, the NFT management server 12 acquires the possession user history (step S100).

After that, the NFT management server 12 sends the mission ID (related mission ID) acquired in step S94, the mission ID (accomplished mission ID) acquired in step S96, and the possession user history acquired in step S100 to the application server 10 (step S101), and the process ends. On the other hand, the application server 10 that has acquired each piece of information in step S101 generates a possessed product detail screen based on each piece of information that has been acquired, and returns it to the user terminal 2 (step S102).

FIG. 16(b) is a diagram showing a possessed product detail screen W8 displayed on the display of the user terminal 2. FIG. As shown in the figure, the possession product detail screen W8 includes an enlarged tile 28 of the corresponding product, a mission column 29, and possession user history 22. FIG. The mission column 29 includes a list of mission names for each of one or more mission IDs related to the corresponding product, and "achieved" or "unachieved" is given to each of them. The possession user history 30 is the same as the possession user history 22 shown in FIG. 9(c).

As described above, according to the sold merchandise management system 1 according to the present embodiment, it becomes possible to track merchandise after it is sold by referring to the blockchain network 4. As a result, In addition to making it possible to psychologically suppress the resale of products, it is also possible to give incentives to consumers to keep products for a long time, so it is possible to prevent market destruction due to auctions and counterfeits. become. In addition, since sales on the second-hand market can be tracked, it is also possible to return commissions, etc. for sales from the second-hand market to the producer.

In addition, since the NFT linkage table T3 that stores the user ID and the serial code of the product in association is prepared, it is possible to confirm the current owner without referring to the blockchain network 4. Furthermore, when issuing a transfer transaction, the user indicated by the user ID stored in the NFT linkage table T3 in association with the serial code input to the application server 10 and the current owner of the NFT are blocked. Since it is determined whether or not the user recorded in the chain network 4 matches, and is issued only when it is determined that they match, it is possible to prevent the occurrence of double transfer.

In addition, one or more possessed products of the user indicated by one or more serial codes stored in the NFT linkage table T2 in association with the user ID of the user who entered the serial code into the application server 10 are stored in the incentive table T4. Since the NFT management server 12 is configured to determine whether the conditions of each mission are satisfied and to transmit to the user the reward information included in the mission determined to be satisfied, the user , it becomes possible to actually give an incentive to hold the product for a long time.

Although not described in this embodiment, the sold merchandise management system 1 is preferably configured so that transfer transactions can also be registered for the transfer (transfer) of merchandise between users. In this case, it is preferable that the user ID of the transfer source user and the transfer price can be input on the code input screen W5 shown in FIG. 13(b). By doing this, the NFT management server 12 can display the event that caused the transfer (in this case, the transfer between users), the input transfer price, the information indicating the transfer source user, and the transfer destination user and the date when the transfer occurred, and can be recorded in the blockchain network 4 in the same manner as in step S62 of FIG.

Although the preferred embodiments of the present invention have been described above, the present invention is by no means limited to such embodiments, and the present invention can be implemented in various forms without departing from the gist thereof. is of course.

1 Sold product management system 2 User terminal 3 Operator terminal 4 Blockchain network 5 Network 10 Application server 11 Application database 12 NFT management server 13

NFT relation database

20, 23, 28 Tile 21

NFT list

22, 30 Ownership user history 24 Serial code Input field 25 Registration button 26 Text indicating completion of registration of the selected product 27 New achievement mission information 29 Mission field 100 Computer 101 CPU
102 Storage device 103 Input device 104 Output device 105 Communication device T1 User table T2 NFT management table T3 NFT cooperation table T4 Incentive table T5 Achievement mission table W1 Product list screen W2 Product details screen W3 NFT details screen W4 Product selection screen W5 Code input screen W6 Code input completion screen W7 Possessed product list screen W8 Possessed product details screen

Claims

an NFT relation database that stores an NFT management table that stores the NFT token ID that identifies the product in association with the serial code of the product;
an application server that accepts input of product serial codes from users;
an NFT management server that records, in a blockchain, a transfer transaction indicating the transfer of the NFT stored in the NFT management table in association with the serial code entered in the application server to the user who entered the serial code; ,
Sold Merchandise Management System including.
The NFT management server acquires the transaction ID of the issuance transaction as the token ID by recording the NFT issuance transaction that specifies the product in the blockchain, associates it with the serial code of the product, and associates it with the NFT management table perform the process of registering with
The sold merchandise management system according to claim 1.
The NFT relation database further stores an NFT linkage table that stores the user ID and the serial code of the product in association with each other,
The NFT management server updates the user ID stored in the NFT linkage table in association with the serial code entered in the application server with the user ID of the user who entered the serial code.
The sold merchandise management system according to claim 1 or 2.
The NFT management server records the user indicated by the user ID stored in the NFT linkage table in association with the serial code input to the application server and the current owner of the NFT in the blockchain. determining whether or not the user to be transferred matches, and if it is determined that they match, performing processing to record the transfer transaction on the blockchain;
The sold merchandise management system according to claim 3.
The NFT management table also stores a product type ID that identifies the type of product in association with the serial code,
The NFT relation database further stores an incentive table that stores a plurality of missions each including conditions based on the product type ID and reward information indicating rewards given to users who satisfy the conditions,
The NFT management server associates the corresponding conditions with the user ID of the user who entered the serial code into the application server, among the plurality of missions stored in the incentive table, in the NFT cooperation table Determining whether or not there is a mission fulfilled by one or more possessed products of the user indicated by one or more stored serial codes, and if it is determined that there is a mission, the corresponding condition is the possession of the one or more transmitting to the user the reward information included in each of the one or more missions fulfilled by the product;
The sold merchandise management system according to claim 3 or 4.
The NFT relation database further stores an accomplished mission table that stores accomplished missions in association with user IDs,
The NFT management server stores one or more missions whose corresponding conditions are satisfied by the one or more possessed products as completed missions in the accomplished mission table in association with the user ID of the user. Regarding, do not send said compensation information,
The sold merchandise management system according to claim 5.
A sold product management method executed by a computer connected to an NFT relation database that stores an NFT management table that stores an NFT token ID that identifies a product in association with a serial code of the product,
a step in which the computer receives an input of a product serial code from a user;
A step in which the computer records a transfer transaction indicating transfer of the NFT stored in the NFT management table in association with the received serial code to the user who entered the serial code on the blockchain;
Sold goods management method including;
A computer connected to an NFT relation database that stores an NFT management table that stores the NFT token ID that identifies the product in association with the serial code of the product,
a step of receiving an input of a product serial code from a user;
A step of recording, on a blockchain, a transfer transaction indicating the transfer of the NFT stored in the NFT management table in association with the received serial code to the user who entered the serial code;
program to run the