JP2024015486A - Sold merchandise management system, sold merchandise management method, and program - Google Patents

Abstract

To suppress the occurrence of resale.SOLUTION: A sold merchandise management system 1 includes: an NFT relation database 13 which stores an NFT management table T2 storing a token ID of a NFT which identifies merchandise in association with a serial code of the merchandise; an application server 10 which receives input of the serial code of the merchandise from a user; and an NFT management server 12 which records transfer transaction in a block chain which indicates the transfer of the NFT stored in the NFT management table T2 in association with the serial code inputted to the application server 10, to the user who inputted the serial code.SELECTED DRAWING: Figure 3

Description

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

Conventionally, sales systems for selling real goods such as figurines have been known. Patent Document 1 discloses an example of such a sales system. According to the sales system disclosed in Patent Document 1, the product supply side can grasp the status of purchase applications in real time, and it is said that it becomes possible to secure appropriate product inventory.

Japanese Patent Application Publication No. 2002-163502

By the way, in recent years, with the rise of flea market apps, the buying and selling of products between individuals has become popular, and as a result, auctions (so-called resellers) and elaborate counterfeits (counterfeits) have become social issues. If left unchecked, the market could be destroyed, and a solution is urgently needed. Additionally, there was a need to improve the fact that traditional second-hand markets (secondary markets), including flea market apps, do not provide returns to the creators (manufacturers).

Therefore, one of the objects of the present invention is to provide a sold product management system, a sold product management method, and a program that can prevent the destruction of the market due to auctions and counterfeits, and realize returns to manufacturers from the second-hand market. Regarding.

The sold product management system according to the present invention includes an NFT relationship database that stores an NFT management table that stores an NFT token ID that identifies the product in association with the serial code of the product, and an NFT relationship database that stores the NFT token ID that identifies the product in association with the serial code of the product. recording on a blockchain a transfer transaction indicating the transfer of the NFT stored in the NFT management table in association with the accepting application server and the serial code input to the application server to the user who input the serial code; This is a sold product management system that includes an NFT management server for managing NFTs.

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

In the program according to the present invention, a user inputs the serial code of a product into a computer connected to an NFT relationship database that stores an NFT management table that stores an NFT token ID that identifies the product in association with the serial code of the product. and 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 inputs the serial code. This is a program to be executed.

According to the present invention, it becomes possible to track products after they have been sold by referring to the blockchain, and as a result, it becomes possible to psychologically suppress resale of products by consumers, and Since it becomes possible to give consumers an incentive to hold on to their products for a long time, it becomes possible to prevent the market from being destroyed by auctions and counterfeits. Furthermore, since it is possible to track sales and purchases on the second-hand market, it is also possible to return transaction fees and the like from the second-hand market to the manufacturer.

1 is a diagram showing the configuration of a system including a sold product management system 1 according to the present embodiment. 1 is a diagram showing an example of the hardware configuration of a sold product management system 1, a user terminal 2, and an operator terminal 3. FIG. 1 is a diagram showing the internal configuration of a sold product management system 1. FIG. 3 is a diagram showing a user table T1 stored in the 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 cooperation table T3 stored in the NFT relation database 13. (a) is a diagram showing an incentive table T4 stored in the NFT relation database 13, and (b) is a diagram showing an accomplished mission table T5 stored in the NFT relation database 13. 3 is a sequence diagram showing processing executed by the operator terminal 3 and each server in the sold product management system 1. FIG. 3 is a sequence diagram showing processing executed by the operator terminal 3 and each server in the sold product management system 1. FIG. 9 is a diagram showing transitions of screens displayed on the operator terminal 3 during the process shown in FIG. 8. FIG. 2 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold product management system 1. FIG. 2 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold product management system 1. FIG. 2 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold product management system 1. FIG. 13 is a diagram showing transitions of screens displayed on the user terminal 2 during the processing shown in FIGS. 10 to 12. FIG. 2 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold product management system 1. FIG. 2 is a sequence diagram showing processing executed by the user terminal 2 and each server in the sold product management system 1. FIG. 16 is a diagram showing transitions of screens displayed on the user terminal 2 during the processing shown in FIGS. 14 and 15. FIG.

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

FIG. 1 is a diagram showing the configuration of a system including a sold product management system 1 according to the present embodiment. The sold product management system 1 is a system that manages products (real goods) sold at a real shop such as the illustrated 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 give an overview of the process performed by the sold product management system 1, the sold product management system 1 first allocates a serial code to each product before sale, and creates an NFT (non-fungible) that includes the assigned serial code. Tokens) are recorded on 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 to the product in advance. The sold product management system 1 that receives this input stores the input serial code in association with the user ID of the input user, and transfers the transfer transaction indicating the transfer of ownership of the NFT to the blockchain network 4. to be recorded. This makes it possible to track products after they have been sold (i.e., check the history of the user who owns the product) by referring to the blockchain network 4, and as a result, it is possible to prevent consumers from reselling the product. This makes it possible to psychologically control this and also to give consumers an incentive to keep products for a long time, making it possible to prevent market destruction due to auctions and counterfeits. Furthermore, since it is possible to track sales and purchases on the second-hand market, it is also possible to return transaction fees and the like from the second-hand market to the manufacturer.

FIG. 2 is a diagram showing an example of the hardware configuration of the sold product management system 1, the user terminal 2, and the operator terminal 3. The sold product 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 product management system 1 is a high-performance computer that functions as a server. Further, the 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 smartphone. 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. It is a computer. However, when the computer 100 is configured by combining a plurality of computers as described above, each of the servers 10 and 12 shown in FIG. 3 may be distributed and implemented in a plurality of computers. The functions of each server 10, 12 are realized by the CPU 101 of each computer executing a program stored in each storage device 102. Furthermore, the programs executed by the CPU 101 of the user terminal 2 or the operator terminal 3 include browser software or a mobile application that has 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, and stores various programs for executing the operating system of the computer 100 and various applications, as well as a variety of programs for executing the operating system and various applications. A device that plays the role of storing data used by programs. Databases 11 and 13 shown in FIG. 3, which will be described later, are implemented in the storage device 102 of the sold product management system 1.

The input device 103 is a device that receives user input operations and supplies them 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 results of the CPU 101 to the user, and includes, for example, a display and a speaker. The 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 product management system 1, user terminal 2, and 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. It is configured like this.

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

Generally, there are three types of blockchain: 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, the explanation will be continued assuming that the blockchain network 4 is the Ethereum network.

Recording of transactions on the blockchain is performed by several computers (hereinafter referred to as "miners") connected to the blockchain network 4. Specifically, each block constituting the blockchain includes a block header and data (transaction data) indicating 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 Blockchain Network 4, in order to connect a new block to the blockchain, the hash value of that block must meet a predetermined condition (for example, a value starting with "000"). Rules are set. Therefore, a miner who wants to record a block in a blockchain performs work (mining) to find a nonce value using brute force so that the hash value of the block header of that block satisfies the above predetermined condition. As a result of this work, the miner who succeeds in discovering the nonce value first will connect 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 wish to record transactions on the blockchain must pay a fee called "gas" in virtual currency. Gas is paid as a reward to miners who successfully concatenate blocks.

FIG. 3 is a diagram showing the internal configuration of the sold product management system 1. As shown in the figure, the sold product management system 1 includes an application server 10, an application database 11, an NFT management server 12, and an NFT relationship 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.

Here, the method by which the user obtains the product serial code is not particularly limited. For example, the shop may hand out a piece of paper with the serial code written on it along with the product, or it may affix a sticker with the serial code written on the product. Furthermore, if a serial code is written in an 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. . Note that in the case of purchasing 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. The data stored in the application database 11 includes a user table T1. Details of the user table T1 will be explained in detail later with reference to FIG. 4.

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 the registration of the product before sale, issues a serial code, records the NFT issuance transaction including the assigned serial code on the blockchain network 4, and records the transaction of the recorded issuance transaction. A process is performed in which an ID (token ID) and a serial code are associated with each other and registered in the NFT relation database 13. Further, the NFT management server 12 associates the serial code accepted by the application database 11 with the user ID and registers it in the NFT relationship database 13, and also sends a transfer transaction indicating the transfer of ownership of the corresponding NFT to the blockchain network 4. Perform the processing to record.

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

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

The session ID is identification information for identifying the user who is communicating. Although "ID1", "ID2", etc. are written 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 the time of login, stores it in the user table T1 in association with the user ID of the logged-in user, and deletes it at the time of 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 product management system 1, and identifies the source 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. The NFT management table T2 is a table for storing detailed information on individual products, and as shown in the figure, it stores serial codes, product type IDs, product names, selling prices, thumbnail information, and NFT information. are configured to be stored in association with each other. The serial code is a code for identifying individual products, and is uniquely assigned to products handled by the sold product management system 1. The product type ID is a code for identifying the type of product, and is uniquely assigned to the type of product 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 type of product 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 a corresponding product. NFT is an NFT token ID that includes a corresponding serial code.

FIG. 5(b) is a diagram showing the NFT cooperation table T3 stored in the NFT relation database 13. The NFT linkage table T3 is a table for storing serial codes of products owned by individual users, and as shown in the figure, it is configured to store user IDs and serial codes in association with each other. .

FIG. 6(a) is a diagram showing an incentive table T4 stored in the NFT relationship database 13. Each record of the incentive table T4 indicates a mission to be accomplished by the user, and as shown in the figure, includes a mission ID, a mission name, conditions, and reward information indicating a reward. The mission ID is a code for identifying each mission, and is uniquely assigned to a mission handled by the sold product management system 1. The mission name is a character string given to each mission, and serves to help users understand the mission content. The conditions are conditions for accomplishing the mission, and include one or more product type IDs. The reward information is information indicating the reward given to the user who completes the mission. Specifically, as illustrated in FIG. 6A, it is preferable to use an image file, a method for obtaining a not-for-sale item (a character string indicating the method), etc. as the remuneration information.

FIG. 6(b) is a diagram showing an accomplished mission table T5 stored in the application database 11. The accomplished mission table T5 is a table for storing missions accomplished by individual users, and is configured to store user IDs and accomplished missions in association with each other, as shown in the figure. Zero or more mission IDs stored in the incentive table T4 are arranged in the accomplished mission.

Below, a sequence diagram of the processing executed by the operator terminal 3, user terminal 2, and each server in the sold product management system 1, and a diagram showing the transition of screens displayed on the operator terminal 3 and user terminal 2 are shown. The processing performed by the sold product management system 1 will be described in detail with reference to the following.

7 and 8 are sequence diagrams showing the processing executed by the operator terminal 3 and each server in the sold product management system 1, and FIG. 9 is a sequence diagram showing the processing executed by the operator terminal 3 in the processing shown in FIG. FIG. 3 is a diagram showing the transition of screens.

FIG. 7 shows a process for assigning a serial code to a product before sale. Specifically, first, a product registration request is sent 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. 5(a), 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 issuance transaction of the generated NFT on the blockchain network 4 with the wallet address of the sold product 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 blockchain network 4 sends the NFT token ID (transaction ID indicating the NFT issuance transaction) 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 it 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 thus obtained to the product (step S7), and completes the product registration. As mentioned above, specific methods for adding a serial code include writing the serial code on a piece of paper attached to the product, pasting a sticker with the serial code on the product, and attaching a sticker embedded in the product. One example is writing a serial code into an IC chip.

Next, FIG. 8 shows a process for the operator to confirm information on products registered in the NFT relationship database 13. Specifically, first, a list display request is sent 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 received this list display request refers to the NFT management table T2 in the NFT relationship database 13 (step S11), and information including the product type ID, product name, selling price, and thumbnail information (hereinafter referred to as " product information") (step S12). Then, a product list screen is generated based on the retrieved product information and sent back to the operator terminal 3 (step S13).

FIG. 9A is a diagram showing a product list screen W1 displayed on the display of the operator terminal 3. 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 an image and a product name of the product indicated by the corresponding product information. Although not shown, the selling price may also be displayed on each tile 20. This point also applies to tiles 23 and 28, which will be described later.

Return to FIG. 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). Upon receiving this product type ID, the NFT management server 12 extracts one or more corresponding serial codes from the NFT management table T2 (steps S16, S17), and then extracts one or more corresponding serial codes from the NFT management table T2 (steps S16, S17). The user ID is taken out from the NFT cooperation table T3 (steps S18, S19). Then, a product details screen is generated based on the retrieved serial code and user ID and sent back 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 details screen W2 includes an enlarged tile 20 of the selected product and an NFT list 21. The NFT list 21 is a list of serial codes and user IDs extracted in steps S17 and S19.

Return to FIG. 8. When the operator selects a serial code by tapping one of the lines in the NFT list 21 of the product details screen W2 (step S21), the selected serial code is transmitted from the operator terminal 3 to the NFT management server 12. (Step S22). Upon receiving this serial code, the NFT management server 12 first retrieves the corresponding NFT token ID from the NFT management table T2 (steps S23 and S24). Next, the NFT management server 12 inquires of the blockchain network 4 about the history of the user who owns the NFT corresponding to the retrieved token ID (step S25). In short, this process is a process of acquiring the history of users who have owned the corresponding NFT by collecting and referring to the corresponding transfer transactions (details will be described later).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 details screen based on the acquired possession user history and sends it back 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 details screen W3 includes an enlarged tile 20 of the corresponding product and a possession user history 22. The possessing user history 22 is a list of possessing user histories acquired in step S26. Each record in the owned user history 22 includes the event that caused the transfer (sales of new products, transfers between users, etc.), the amount of money (price) transferred due to the transfer, the user from whom the transfer was made, and the information about the transfer. Contains the previous user and the date on which the transfer occurred.

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

10 to 12 show the process for the user of the user terminal 2 to log into the sold product management system 1, and the process for registering the serial code of the purchased product in the sold product management system 1. ing. Specifically, a user who wishes to log in to the sold product 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 user ID and password shown in FIG.

The application server 10 that has received the login request determines whether the combination of user ID and password included therein exists in the user table T1. As a result, the application server 10 that determines that the login does not exist returns a login NG message to the user terminal 2 and ends the process. On the other hand, the application server 10 that has determined that the user exists gives a new session ID to the user and stores it in the user table T1 (step S31), and also sends it back to the user terminal 2 (step S32). This session ID is then placed in messages sent and received between the user terminal 2 and each server in the sold product management system 1, and is used to identify the sender and destination of the message. Ru.

Here, even when the operator terminal 3 accesses the sold product management system 1 in order to execute the processing explained with reference to FIGS. 7 and 8, the same login process as in the case of the user terminal 2 is required. You can also use it as 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 logging in as the user terminal 2 or the operator terminal 3. Preferably, 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 completed logging into the sold product management system 1 and wishes to register the serial code of the purchased product in the sold product management system 1 sends an NFT to the application server 10 by operating the user terminal 2. A cooperation request is sent (step S40). The application server 10 that has received this NFT collaboration request transmits a product information inquiry to the NFT management server 12 to inquire about information on all products to be registered (step S41). In response to this product information inquiry, the NFT management server 12 refers to the NFT management table and extracts the above-mentioned product information 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 received in this way and sends it back 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. 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 a product image and a product name indicated by the corresponding product information.

Return to FIG. 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 S46). S47). The application server 10 that has received this product type ID generates a code input screen for inputting the serial code and sends it back to the user terminal 2 (step S48).

FIG. 13(b) is a diagram showing a code input screen W5 displayed on the display of the user terminal 2. 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.

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

Upon receiving the combination of serial code and user ID, the NFT management server 12 first retrieves the corresponding NFT token ID from the NFT management table T2 (steps S52 and S53), and inquires of the blockchain network 4 about its current owner ( Step S54). In short, this process is a process of acquiring the user who currently owns the corresponding NFT by collecting and referencing the corresponding transfer transactions, and as a result of the inquiry, the NFT management server 12 determines the current owner. The indicated NFT ownership information is acquired (step S55).

The NFT management server 12 determines that the user indicated by the NFT ownership information acquired in step S55 matches the user indicated by the user ID stored in the NFT cooperation table T3 in association with the serial code received in step S51. It is determined whether or not (steps S56 to S58). As a result, if it is determined that they do not match, the NFT management server 12 sends an error notification to the user terminal 2 via the application server 10 (steps S59 and S60). In this case, the serial code input by the user in step S49 will not be registered in the sold product management system 1 as belonging to the user. By performing this process, it becomes possible to prevent double transfer from occurring, such as when the ownership of the NFT has been transferred in a place unrelated to the sold product management system 1.

On the other hand, if it is determined in step S58 that they match, the NFT management server 12 replaces the user ID stored in the NFT cooperation table T3 in association with the serial code received in step S51 with the user ID received in step S51. At the same time, a transfer transaction indicating that ownership of the corresponding NFT is transferred to the wallet address of the user indicated by the user ID is generated and recorded 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 sale as the transfer source user. Information indicating the completed product management system 1 (described as "user0" in FIG. 9(c)), information indicating the transfer destination user (the user indicated by the user ID received in step S51), and information indicating the transfer destination. Contains the 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 cooperation table T3 (steps S63, S64), and further retrieves the serial codes corresponding to the retrieved serial codes. One or more product type IDs are taken out from the NFT management table T2 (steps S65, S66).

Next, 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 completed by the corresponding user as an accomplished mission. It is taken out from table T5 (steps S69, S70). Then, by comparing these, it is determined that the mission that has been newly achieved this time (that is, the mission that the user's owned product satisfies the conditions for being stored in the incentive table T4 and that has not yet been achieved by the user) It is determined whether or not there is (step S71). As a result, the NFT management server 12 determines that there is no newly accomplished mission, and sends a completion notification back to the application server 10 (step S72), and ends the process. On the other hand, the NFT management server 12 that has determined that there is a newly accomplished mission retrieves information indicating the newly accomplished mission and its reward (hereinafter referred to as "newly accomplished mission information") from the incentive table T4 (step S73 , S74), and sends it back to the application server 10 together with a completion notification (step S75). The NFT management server 12 then updates the accomplished mission table T5 by adding the mission indicated by the new accomplished mission information to the accomplished missions of the corresponding user (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 sends it to the user terminal 2 (step S77).

FIG. 13(c) is a diagram showing a code input completion screen W6 displayed on the display of the user terminal 2. As shown in the figure, the code input completion screen W6 includes a text 26 indicating that the registration of the selected product has been completed, and new mission information 27 indicating the reward given to the user. The new accomplished mission information 27 is the newly accomplished 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 a process for the user of the user terminal 2 to check the list of products owned by the user 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 received this NFT confirmation request transmits the user ID of the user who sent the NFT confirmation request to the NFT management server 12 (step S81).

The NFT management server 12 that has received the user ID retrieves the corresponding serial code from the NFT cooperation table T3 (steps S82 and 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, 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 received in this way and sends it back 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. 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, and each tile 28 is displayed with corresponding product information. The product image and product name will be displayed. Note that if the user owns a plurality of products of the same type (products with the same product type ID), tiles 28 with the same contents will be displayed for the number of products.

Return to FIG. 14. When the user selects a product by tapping one of the tiles 28 on the owned 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. The code is transmitted (steps S89, S90).

The NFT management server 12 that 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). Next, the NFT management server 12 retrieves the mission ID associated with the retrieved product type ID (the mission ID in which the corresponding "condition" includes the product type ID) from the incentive table T4 (steps S93 and S94), and further, By referring to the accomplished mission table T5, among the mission IDs retrieved in step S94, those that have been accomplished by the corresponding user (achieved mission IDs) are acquired (steps S95, S96).

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

Thereafter, the NFT management server 12 transmits the mission ID (related mission ID) acquired in step S94, the mission ID (achieved mission ID) acquired in step S96, and the possession user history acquired in step S100 to the application server 12. (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 possession product details screen based on each piece of acquired information and sends it back to the user terminal 2 (step S102).

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

As explained above, according to the sold product management system 1 according to the present embodiment, it becomes possible to track the sold products by referring to the blockchain network 4, and as a result, the This makes it possible to psychologically discourage resale of products, and it also makes it possible to give consumers an incentive to keep products for a long time, thereby preventing the destruction of the market due to auctions and counterfeits. become. Furthermore, since it is possible to track sales and purchases on the second-hand market, it is also possible to return transaction fees and the like from the second-hand market to the manufacturer.

Furthermore, since we have prepared an NFT cooperation table T3 that stores user IDs and serial codes of products in association with each other, it becomes 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 records in the chain network 4 match, and the ticket 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 products owned by the user indicated by one or more serial codes stored in the NFT cooperation table T2 in association with the user ID of the user who input the serial code into the application server 10 is stored in the incentive table T4. The NFT management server 12 is configured to determine whether or not the conditions of each mission are met, and to send the reward information included in the missions determined to be satisfied to the user. , it becomes possible to actually provide incentives for holding products for a long time.

Although not described in this embodiment, the sold product management system 1 is preferably configured to be able to register a transfer transaction regarding the transfer (assignment) of a product between users. In this case, it is preferable to allow the user ID of the transfer source user and the transfer price to be input on the code input screen W5 shown in FIG. 13(b). By doing this, the NFT management server 12 records the event that caused the transfer (in this case, a transfer between users), the input transfer price, information indicating the transfer source user, and the transfer destination user. It becomes possible to generate a transfer transaction including information indicating the transfer and the date on which the transfer occurred and record it on the blockchain network 4 similarly to step S62 in FIG. 11.

Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments in any way, and the present invention may be implemented in various forms without departing from the gist thereof. 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 relationship database 20, 23, 28 Tile 21 NFT list 22, 30 Owned user history 24 Serial code Input field 25 Registration button 26 Text indicating that the registration of the selected product has been completed 27 New 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 Accomplished mission table W1 Product list screen W2 Product details screen W3 NFT details screen W4 Product selection screen W5 Code input screen W6 Code entry completion screen W7 Owned product list screen W8 Owned product details screen

Claims (8)

an NFT relationship 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;
an application server that accepts input of a product serial code from a user;
an NFT management server that records on a blockchain a transfer transaction indicating the transfer of an NFT stored in the NFT management table in association with the serial code input to the application server to the user who input the serial code; ,
Sold product management system including. The NFT management server records an NFT issuance transaction that specifies a product in the blockchain, obtains the transaction ID of the issuance transaction as the token ID, associates it with the serial code of the product, and stores it in the NFT management table. Perform the process of registering with
The sold product management system according to claim 1. The NFT relationship database further stores an NFT cooperation table that stores user IDs and product serial codes in association with each other,
The NFT management server performs a process of updating a user ID stored in the NFT cooperation table in association with the serial code input to the application server with the user ID of the user who input the serial code.
A sold product management system according to claim 1 or 2. The NFT management server records in the blockchain 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. determining whether or not the users are matched, and if it is determined that they match, performing a process of recording the transfer transaction on the blockchain;
The sold product 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 relationship database further stores an incentive table that stores a plurality of missions each including a condition based on the product type ID and reward information indicating a reward to be given to a user who satisfies the condition,
The NFT management server stores a corresponding condition in the NFT cooperation table in association with the user ID of the user who inputs the serial code in the application server, among the plurality of missions stored in the incentive table. It is determined whether there is a mission that is satisfied by one or more items owned by the user indicated by one or more stored serial codes, and if it is determined that there is a mission, the corresponding condition is fulfilled by one or more items owned by the user indicated by one or more stored serial codes. transmitting the reward information included in each of one or more missions fulfilled by the product to the user;
The sold product management system according to claim 3 or 4. The NFT relationship database further stores an accomplished mission table that stores accomplished missions in association with user IDs,
The NFT management server stores a mission as an accomplished mission in the accomplished mission table in association with the user ID of the user, among one or more missions whose corresponding conditions are satisfied by the one or more owned products. , do not send the remuneration information,
The sold product management system according to claim 5. A sold product management method executed by a computer connected to an NFT relationship 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, the method comprising:
a step in which the computer receives input of a product serial code from a user;
the computer 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 inputs the serial code;
Sold product management methods, including: A computer connected to an NFT relationship database that stores an NFT management table that stores an NFT token ID that identifies the product in association with the serial code of the product;
a step of accepting the input of the serial code of the product from the user;
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 has input the serial code;
A program to run.

Images