WO2024085737A1

WO2024085737A1 - Item verification server, item verification method and computer program for verifying acqusition of item with non-fungible token

Info

Publication number: WO2024085737A1
Application number: PCT/KR2023/016481
Authority: WO
Inventors: 오재헌; 서현철
Original assignee: 주식회사 딜라이트엑스
Priority date: 2022-10-21
Filing date: 2023-10-23
Publication date: 2024-04-25

Abstract

In the present invention, a non-fungible token corresponding to an item can be acquired online through detection of the item. In addition, licensing data including a non-fungible token that proves the scarcity of an item of user from among items produced in large quantities can be acquired. Moreover, digital content corresponding to the item can be activated in a user terminal possessing the non-fungible token.

Description

Product verification server, product verification method, and computer program that verifies the acquisition of the product with a non-fungible token

Embodiments of the present disclosure relate to a product verification server, a product verification method, and a computer program, and are characterized by generating and managing the distribution of physical goods in various ways, such as purchase, re-trade, and second-hand trade, using digital usage rights data. It relates to a product verification server, product verification method, and computer program.

Blockchain, also called a public transaction ledger, is a technology that uses decentralized algorithms to prevent hacking that may occur due to centralized servers during transactions. While existing financial companies store transaction records on a centralized server, blockchain sends transaction details to all users participating in the transaction and compares them for each transaction to prevent data falsification. Blockchain is applied to Bitcoin, a representative online virtual currency. Bitcoin transparently records transaction details in a ledger that anyone can view, and multiple computers using Bitcoin verify these records to prevent hacking.

Blockchain is not a technology that is simply applied to Bitcoin. It is a technology that can reduce enormous costs associated with database maintenance and security by applying it to storing various data.

This ‘blockchain’ technology allows anyone who receives a transaction transmitted through the network to create a block, but the block of the node that created the block the fastest is adopted. Additionally, if multiple blocks are created at a similar point in time, the chain is divided into several branches, which are later organized and synchronized by deleting all but the longest chain.

The above-mentioned background technology is technical information that the inventor possessed for deriving the present invention or acquired in the process of deriving the present invention, and cannot necessarily be said to be known art disclosed to the general public before filing the application for the present invention.

The purpose of the embodiments disclosed in this specification is to present a product verification server and a product verification method that enable non-fungible tokens corresponding to the product to be acquired online through detection of a physical product offline.

In addition, the embodiments disclosed in this specification are aimed at presenting a product verification server and a product verification method for obtaining usage rights data including a non-fungible token that proves the scarcity of a user's product among mass-produced products. there is.

Additionally, the embodiments disclosed in this specification are aimed at presenting a product verification server and a product verification method that activate digital content corresponding to the product in a user terminal holding a non-fungible token.

Additionally, the embodiments disclosed in this specification are intended to present a product verification server and a product verification method that move usage rights data including a non-fungible token according to the ownership of the product.

Additionally, the embodiments disclosed in this specification are aimed at presenting a product verification server and a product verification method that calculate the sales quantity of a product using distribution information of non-fungible tokens and distribution information of the product.

According to embodiments of the present disclosure, the method includes steps of an item verification server obtaining, from a first user terminal, a detection signal for a first ticket among registered tickets; The product verification server acquires identification information of the first ticket in response to a detection signal for the first ticket, and uses the identification information of the first ticket to create a content or content corresponding to the first ticket. generating data for related applications; and processing, by the product verification server, to transmit the data to the first user terminal and run the content and an application related to the content in the first user terminal.

According to embodiments of the present disclosure, the method includes the item verification server obtaining information about the owner of the first ticket using the identification information of the first ticket included in the detection signal, and the first ticket. It may further include accumulating a reward related to the first ticket to the owner's account using information about the owner of the ticket.

According to embodiments of the present disclosure, the method includes the product verification server receiving detection signals for the registered tickets, generating user content corresponding to terminals of senders of the detection signals, and the user It may further include linking content to content corresponding to the first ticket.

The user contents may be changeable by user input from each of the senders' terminals.

Each of the user contents may be designed to be activated only when communication with each sender's terminal is connected.

According to embodiments of the present disclosure, the method includes, when the item verification server detects a detection signal of the first user within the active range of the first ticket, re-activates user content corresponding to the first user. Additional steps may be included.

According to embodiments of the present disclosure, an item verification server includes one or more processors and a computer-readable medium, wherein the processor detects a detection signal for a first ticket from among registered tickets from a first user terminal. Obtain, obtain identification information of the first ticket in response to a detection signal for the first ticket, and use the identification information of the first ticket to send content corresponding to the first ticket or an application related to the content. data may be generated, the data may be transmitted to the first user terminal, and the content and an application related to the content may be run in the first user terminal.

According to embodiments of the present disclosure, the method includes the steps of a first user who has acquired an article detecting the article through a first user terminal; A product verification server obtaining identification information through detection of the product; Obtaining, by the product verification server, a non-fungible token corresponding to the product using the identification information; The product verification server, in response to the acquisition of the non-fungible token, obtains identification information of the first user from the user terminal and uses the user's identification information to set the user as the owner of the product. 1 generating and recording license data; And the product verification server transmits first packaging data corresponding to the product, including the non-fungible token, digital content corresponding to the product, and identification information of the first user, to the first user terminal, It may include; storing first packaging data corresponding to the product in the user terminal.

According to this embodiment, the product verification server responds to a user input according to detection of the product from a first user terminal, searches for usage rights data corresponding to the product, and sends the usage rights data and the first user terminal to the user input. comparing stored non-fungible tokens; It may further include activating, by the product verification server, the digital content stored in the first user terminal when a predetermined condition is satisfied by comparing the usage right data with the non-fungible token.

According to this embodiment, in response to a user input for moving the first usage right data from the first user terminal to the second user terminal, the product verification server obtains the first usage right data, and obtains the first usage right data. In the data, generate second usage rights data that changes the user's identification information to information related to the second user terminal, move the second usage rights data to the second user terminal, and generate second usage rights data corresponding to the second usage rights data. It may include generating second packaging data and transmitting it to the second user terminal.

According to embodiments of the present disclosure, the distribution company server may further include calculating a first quantity of products purchased through a user's purchase behavior from among identification numbers of products distributed offline.

According to embodiments of the present disclosure, the product verification server calculates a second quantity of tokens converted into usage rights data among non-fungible tokens corresponding to the products, and the second quantity is received from the distribution company server. It may further include determining whether it matches the received first quantity.

According to embodiments of the present disclosure, in the step of generating and recording the first usage right data, the product verification server uses the identification information of the first user to identify the first user as the user who acquired the product. Information on whether the product is the same can be obtained by requesting it from an external distributor server, and if the first user is not the user who acquired the product, the first usage right data can be processed not to be generated.

According to embodiments of the present disclosure, before the step of acquiring the identification information obtained through detection of the product, the identification information of the product is obtained and recorded from an external distributor server, and the identification information obtained from the external distributor server is recorded. In response to the identification information, the product verification server generates non-fungible tokens corresponding to the quantity of the obtained identification information; The product verification server may further perform processing to execute a smart contract for a non-fungible token corresponding to the product in a blockchain system.

According to embodiments of the present disclosure, the product verification server detects the product in the second user terminal and obtains identification information of the product through detection of the product; The product verification server may further include setting whether the second usage right data corresponding to the product can be activated to 1 using the identification information of the product.

The product verification server according to embodiments of the present disclosure includes one or more processors and a computer-readable medium, wherein the processor detects the product through a first user terminal by a first user who has acquired the product, and Obtain identification information through detection of an item, obtain a non-fungible token corresponding to the item using the identification information, and identify the first user from the user terminal in response to acquisition of the non-fungible token. Obtain information and use the user's identification information to generate and record first usage rights data that establishes the user as the owner of the item, the non-fungible token, the digital content corresponding to the item, and the first user. First packaging data corresponding to the product, including identification information, may be transmitted to the first user terminal, and the first packaging data corresponding to the product may be stored in the user terminal.

The processor, in response to a user input based on detection of the article from a first user terminal, searches for license data corresponding to the article, and compares the license data with a non-fungible token stored in the first user terminal, When a predetermined condition is satisfied by comparing the usage right data with the non-fungible token, the digital content stored in the first user terminal can be activated.

The processor, in response to a user input for moving the first usage right data from the first user terminal to the second user terminal, causes the product verification server to obtain the first usage right data, and , generating second license data that changes the user's identification information to information related to the second user terminal, moving the second license data to the second user terminal, and generating a second license data corresponding to the second license data. Packaging data can be generated and transmitted to the second user terminal.

The processor and the distribution company server may calculate the first quantity of products purchased through the user's purchase behavior among the identification numbers of products distributed offline.

The processor calculates a second quantity of tokens converted into usage rights data among the non-fungible tokens corresponding to the goods, and determines whether the second quantity matches the first quantity received from the distributor server. can do.

The processor, using the identification information of the first user, requests and obtains information about whether the first user is the same as the user who acquired the product from an external distributor server, and determines whether the first user acquired the product. If the user is not a user, the first usage right data may not be generated.

The processor obtains and records the identification information of the product from an external distributor server, and generates non-fungible tokens equivalent to the quantity of the obtained identification information in response to the identification information obtained from the external distributor server, and , a smart contract for a non-fungible token corresponding to the item can be processed to be executed on the blockchain system.

The processor detects the article in the second user terminal, obtains identification information of the article through detection of the article, and uses the identification information of the article to generate second license data corresponding to the article. You can set activation availability to 1.

According to embodiments of the present disclosure, the method includes the steps of a first user who has acquired an article detecting the article through a first user terminal; A product verification server obtaining identification information through detection of the product; Obtaining, by the product verification server, a non-fungible token corresponding to the product using the identification information; The product verification server, in response to the acquisition of the non-fungible token, obtains identification information of the first user from the user terminal and uses the user's identification information to set the user as the owner of the product. 1 generating and recording license data; And the product verification server transmits first packaging data corresponding to the product, including the non-fungible token, digital content corresponding to the product, and identification information of the first user, to the first user terminal, It may include storing first packaging data corresponding to the product in the user terminal.

A computer program according to an embodiment of the present invention may be stored in a medium to execute any one of the methods according to an embodiment of the present invention using a computer.

In addition to this, another method for implementing the present invention, another system, and a computer-readable recording medium for recording a computer program for executing the method are further provided.

Other aspects, features and advantages other than those described above will become apparent from the following drawings, claims and detailed description of the invention.

According to any one of the means for solving the above-described problem, a non-fungible token corresponding to the product can be acquired online through detection of the product.

Additionally, among mass-produced items, it is possible to acquire usage rights data including a non-fungible token that proves the scarcity of the user's item.

Additionally, digital content corresponding to the product can be activated on a user terminal holding a non-fungible token.

Additionally, usage rights data including non-fungible tokens can be moved depending on the ownership of the item.

Additionally, the sales quantity of the product can be calculated using the distribution information of the non-fungible token and the distribution information of the product.

Additionally, through non-fungible tokens distributed in correspondence with products, it is possible to prevent products from being distributed without going through a legitimate distributor.

1 is a diagram of an article verification system according to embodiments of the present disclosure.

Figure 2 is a block diagram of the product verification server 100 according to embodiments of the present disclosure.

Figure 3 is a flowchart of a method performed through detection of an article according to embodiments of the present disclosure.

Figure 4 is a flowchart of a process for activating digital content stored in a user terminal according to embodiments of the present disclosure.

Figure 5 is a flowchart of a process for transferring ownership of an article according to embodiments of the present disclosure.

Figure 7 is a flowchart of a process in which sound source data is transmitted to a user terminal that has acquired an album, according to embodiments of the present disclosure.

Figure 8 is a flowchart of a process for verifying the quantity of distributed music records according to embodiments of the present disclosure.

Figure 9 is a flowchart of the execution process of digital content verified with a non-fungible token, according to embodiments of the present disclosure.

Hereinafter, the configuration and operation of the present invention will be described in detail with reference to embodiments of the present invention shown in the attached drawings.

Since the present invention can be modified in various ways and can have various embodiments, specific embodiments will be illustrated in the drawings and described in detail in the detailed description. The effects and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various forms.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. When describing with reference to the drawings, identical or corresponding components will be assigned the same reference numerals and redundant description thereof will be omitted. .

In this specification, terms such as “learning” and “learning” are not intended to refer to mental operations such as human educational activities, but are terms that refer to performing machine learning through procedural computing. Interpret.

In the following embodiments, terms such as first and second are used not in a limiting sense but for the purpose of distinguishing one component from another component.

In the following examples, singular terms include plural terms unless the context clearly dictates otherwise.

In the following embodiments, terms such as include or have mean the presence of features or components described in the specification, and do not exclude in advance the possibility of adding one or more other features or components.

In the drawings, the sizes of components may be exaggerated or reduced for convenience of explanation. For example, the size and thickness of each component shown in the drawings are shown arbitrarily for convenience of explanation, so the present invention is not necessarily limited to what is shown.

In cases where an embodiment can be implemented differently, a specific process sequence may be performed differently from the described sequence. For example, two processes described in succession may be performed substantially at the same time, or may be performed in an order opposite to that in which they are described.

In this specification, “blockchain” refers to a ledger that utilizes software elements composed of an algorithm in which blocks connected in order negotiate service usage history information using encryption techniques and security technologies to secure and maintain integrity. It may refer to a distributed P2P (Peer to Peer) system. Here, the distributed P2P system may be a special form of distributed system. Additionally, a P2P system allows all nodes in the network to provide resources (processing power, storage space, data or network bandwidth, etc.) to each other without coordination by a central node. In addition, “blockchain” may refer to a distributed ledger technology in which the ledger recording usage history information is distributed to a P2P network rather than a central server of a specific organization, and nodes within the network jointly record and manage it.

In this specification, “terminal” may be a smartphone, tablet PC, PC, TV, smart TV, mobile phone, personal digital assistant (PDA), laptop, or non-mobile computing device, but is not limited thereto.

In this specification, digital content includes sound files, video files, audio files, webtoons, e-book files, VR content, 3D content, painting data, image data, photo files, virtual human content, dramas, movies, scenarios, and personally shot videos. , tickets, e-learning content, applications, real-time live video, lectures, conferences, selfies, photo cards, etc., sound source files, video files, audio files, webtoons, e-book files, VR content, 3D content, painting data, image data. , photo files, virtual human content. It may be a combination of at least two of the following: drama, movie, scenario, personal video, ticket, e-learning content, application, real-time live video, lecture, conference, selfie, or photo card.

In this specification, goods refer to all items traded offline, and may include, for example, records, paper packaging, business cards, cards, tags, books, magazines, goods, boxes, shopping bags, etc.

The product verification server 100 according to embodiments of the present disclosure can process digital content corresponding to offline products to be traded online, instead of recording, storing, and distributing digital content to products traded offline. . If offline items such as records, books, and photos remain unsold, they may cause environmental pollution. Instead of recording and storing offline items through the product verification server 100, online digital content can be accessed. By processing, the problem of remaining unsold offline items can be solved. The distribution company server 200 may be a server of a company that provides services for distributing items such as albums, books, photos, photo cards, and tickets offline. The distributor server 200 may operate a platform that sells products recording audio data, text data, video or image data, etc. through offline stores or e-commerce sites. The product verification server 100 may perform a function of distributing content corresponding to the product online in connection with the distribution company server 200. In order to solve the problem of freely copying digital content that exists digitally, the product verification server 100 manages authorized users and usage data of digital content by utilizing an indestructible smart contract for transactions of digital content. You can. When data is recorded and distributed on products, not only are costs incurred in recording the data, but there is also a problem in that data that is not recorded as a product cannot be traded as a product. Through this, a minimum amount of information can be recorded on the product, and digital content and assets corresponding to this information can be recorded and provided online. After distribution of the product, digital content, assets, etc. corresponding to the product can be designed to be changed or replaced. Future-occurring content that does not exist at the present time, such as messages with celebrities (stars, influencers, etc.), schedule information about celebrities, event attendance tickets for celebrities, event discount tickets, separate notices about offline events It may be designed to provide content such as. Goods are produced and distributed by the distributor server 200.

In another embodiment, the product verification system includes transaction details for offline products.

The product verification system includes a product verification server 100, a distributor server 200 that distributes products offline, and a blockchain system 300 that processes non-fungible tokens corresponding to the products, and the first It may further include a user terminal 401 and a second user terminal 402.

The product verification server 100 may generate a non-fungible token corresponding to each product in response to products distributed offline or online and transmit the non-fungible token to the owner of the product. The product verification server 100 may issue non-fungible tokens in advance for distributed products and create a smart contract in response to each non-fungible token.

The product verification server 100 can generate non-fungible tokens corresponding to each mass-produced product such as wine, food, records, books, furniture, electronic products, and pictures. Smart contracts for non-fungible tokens can set up contracts differently depending on the nature of the product. Smart contracts can be implemented differently depending on the data about the contract. When an approval signal for a contract determined by the distributor server is generated, a smart contract corresponding to the approval signal can be designed to operate. As a result of the operation of the smart contract, a non-fungible token can be created and the owner of that token can be determined.

For example, when an approval signal for a content purchase action is generated, the smart contract for the purchase action is executed and ownership of the content may be automatically granted to the user making the purchase.

The product verification server 100 may obtain identification information obtained through detection of the product and search for and obtain a non-fungible token corresponding to the product. Here, the item can be sensed by detecting RF signals. Items can be detected by recognizing visual data such as QR codes and barcodes with a camera. Items can be detected through a camera that takes pictures of the item itself. An item can be detected by the user entering a number recorded on the item. The article may be detected through a separate article sensing means. In response to detection of the article, the article verification server 100 obtains identification information of the article and provides usage rights data including the identification information of the article, a non-fungible token corresponding to the article, and information about the terminal that detected the article. can be created. Here, the usage right data is data about the right to use (ownership, transfer, use, reuse, multiple issuance, etc.) of digital content, applications, services, etc. corresponding to the product. It may include a converted value corresponding to the information, specifically a hash value for identification information, a hash value of the token, etc. The hash function that generates the hash value may be pre-stored or may be generated using input variables such as product identification information. As the smart contract based on detection of the product is executed, usage rights data corresponding to the product may be created or updated. The product verification server 100 may generate usage rights data for digital content corresponding to the product and store it as data about the product. Here, digital content may include anything in the form of digital data and anything created based on data stored in cyberspace corresponding to an article. By detecting the product, usage rights data for the product are generated and can be stored in a separate database or memory. When usage rights data is generated, the product verification server 100 may determine that the owner of the product has been determined. Owner refers to the person with rights to the goods. The owner or right holder may be a person who has at least one of ownership, right to use, right to transfer, and right to issue. Usage right data is generated for each product, and may be updated when the owner of the product changes. The product verification server 100 may generate packaging data corresponding to the product through detection of the product. Packaging data refers to all data required to load content on a user terminal. The product verification server 100 can transmit packaging data to the user's terminal and store it. Packaging data may include data about a non-fungible token corresponding to the product, digital content corresponding to the product, information about the user who is the owner of the product, and authority information granted to the owner of the product. The packaging data may further include product identification information printed on the product or converted from information printed on the product. The product verification server 100 can use packaging data to determine whether access is from the owner or legitimate rights holder when loading content. The product verification server 100 may approve the use of authority held by the user using packaging data.

The product verification server 100 may receive identification information assigned to each of the products in advance and search for and obtain a non-fungible token corresponding to each of the identification information of the products. The product verification server 100 may transmit the non-fungible token to the user terminal of the person acquiring the product and store it.

When a request for token issuance is received from the distributor server 200, the product verification server 100 may create a smart contract corresponding to the request. The product verification server 100 can negotiate with the distributor server 200 for an approval signal that generates token issuance, and process the smart contract according to the negotiation to be executed.

The distributor server 200 refers to a server that manages distribution information for products when distributing products offline or online. The distributor server 200 can generate and manage identification information corresponding to distributed products. The distributor server 200 may transmit identification information corresponding to products to the product verification server 100. Identification information corresponding to products or hash values for the identification information may be transmitted to the product verification server 100 and managed. The distributor server 200 may record data on whether the products are sold in response to an offline or online transfer of ownership, usage rights, transfer rights, issuance rights, etc. of the products.

In Figure 1, one distribution company server 200 is shown, but a system including a plurality of distribution company servers may be possible. The distribution company server 200 can store and manage information about products distributed through existing distribution networks, information about the distribution of products, and data about rights granted to product rights holders. The content rights holder can be granted not only the right to use the content, but also the right to use other services, transfer rights, and publishing rights.

The blockchain system 300 is a system that generates and records non-fungible tokens corresponding to items, and is a system in which a plurality of devices (nodes) are distributedly implemented. The blockchain system 300 is a system in which data is stored in blocks and connected in the form of a chain, and is a distributed data storage system that copies and stores data on numerous computers simultaneously. Non-fungible tokens generated through the blockchain system 300 may be accessible by request from the product verification server 100 or the user terminal. At this time, the user terminal's request may include data received from the product verification server 100.

The blockchain system 300 can provide functions such as issuing non-fungible tokens and creating blocks. The product verification server 100 or the user terminal can access the blockchain system 300 by accessing the interface provided by the system.

The first user terminal 401 is a terminal device including a display device and a processor owned by a user, and connects to the product verification server 100 to provide data about a non-fungible token corresponding to the product or content corresponding to the product. You can receive data about . The first user terminal 401 may access the product verification server 100 through a network and obtain data about the physical product. The first user terminal 401 may be designed to drive digital content corresponding to a physical product.

The second user terminal 402 is a device that has the same structure as the first user terminal 401 and is a terminal device owned by a user different from the first user terminal 401. The second user terminal 402 may be used instead of the first user terminal 401. The first or

second user terminal

401 or 402 may detect an article through an article detection unit, an Rf receiver, a camera, an input unit, etc.

The product verification server 100 may include a processor 110, a memory 120, a communication unit 130, and a sales verification unit 140. However, not all of the illustrated components are essential components. The product verification server 100 may be implemented with more components than the components shown, and the product verification server 100 may also be implemented with fewer components. Below we will look at the above components. The node shown in FIG. 1 may include the same components as the product verification server 100.

According to some embodiments, the communication unit 130 may communicate with an external device. Specifically, the communication unit 130 may be connected to a network either wired or wirelessly to communicate with an external device. Here, the external device may include nodes on the blockchain network and the operator's terminal.

The communication unit 130 may include a communication module that supports one of various wired and wireless communication methods. The communication module may be a short-distance communication module or a wired communication module.

According to some embodiments, the memory 120 is a flash memory type, hard disk type, multimedia card micro type, card type memory (SD, XD memory, etc.). ), RAM (Random Access Memory), SRAM (Static Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), PROM (Programmable Read-Only Memory) magnetic memory, It may include at least one type of storage medium among magnetic disks and optical disks. The memory 120 may store at least one program for executing the operation method of the product verification server 100 on a computer. At least one program stored in the memory 120 may be classified into a plurality of modules according to function.

According to some embodiments, the processor 110 controls the overall operation of the product verification server 100 and may include at least one processor such as a CPU. The processor 110 may include at least one specialized processor corresponding to each function, or may be an integrated processor.

According to some embodiments, the processor 110 may execute a program stored in the memory 120, read data or files stored in the memory 120, or store a new file in the memory 120. Additionally, the processor 110 may execute instructions stored in the memory 120.

The product verification server 100 may further include a sales verification unit 140 that performs the function of verifying products whose ownership is transferred online or offline.

The sales verification unit 140 may obtain identification information by detecting the product and use the identification information to obtain a non-fungible token corresponding to the product. The sales verification unit 140 acquires the user's identification information from the user terminal in response to the acquisition of the non-fungible token, uses the user's identification information to generate and record license data that sets the user as the owner of the product, and records the non-fungible token. Packaging data corresponding to the product, including a token, digital content (content, application, executable file, etc.) corresponding to the product, and user identification information, can be generated and transmitted to the user terminal. Through this, it is possible to acquire a non-fungible token corresponding to the product online through the user terminal by detecting the product. At this time, examples of goods include physical items such as records, books, wine, paintings, artwork, expensive luxury goods, clothing, shoes, bags, accessories, goods, business cards, cards, etc., or digital content. . Goods may be scarce or may be designed to be distributed in limited quantities. For goods, it can be set to be non-transferable.

In this specification, an article may further include a code, tag, information, etc. that can be detected through an electronic device such as a user terminal. Codes, tags, information, etc. included in the product may be detected by a communication unit, a camera, etc. included in the user terminal, but are not limited to this and may be detected through various sensors.

Codes, tags, and information included in the product may include header values, product identification information, management information, information about the type of product, expiration date, rights information (transfer right information, use right information), etc. The management information may be information for identifying the product issued by the product verification server 100.

The user's identification information may be ID information used when the user accesses the product verification server. The user's identification information may be a code issued by the product verification server 100 itself, or may be generated by the user's input. The product verification server 100 may generate and manage user identification information corresponding to the user's access. The product verification server 100 can prevent access by users without user identification information. User identification information can be stored in memory or a separate database.

The product verification server 100 can determine the validity of the user's identification information, including the number of bytes of the user's identification information, whether it matches the stored identification information, whether the validity period of the user's identification information remains, and the number of uses. The validity of the user's identification information can be determined by considering whether it remains, whether it is transferable, and whether it can be reused. By determining the validity of the user's identification information included in the license data, the validity of the license data can be determined. The validity of the license data can be determined by determining whether the user's identification information included in the license data matches the user of the stored license data.

Users whose validity is true can use digital content, transfer digital content, and have access to services related to digital content. Applications or services related to digital content include viewing of performances, private shopping time, use of lounges, early admission to tourist attractions, guides at museums/art galleries, free shipping, discounted purchases, sending and receiving messages with influencers, and influencers. It may include services such as the influencer's schedule and the influencer's private messages.

The sales verification unit 140 searches for usage right data corresponding to the product in response to user input upon detection of the product from the user terminal, and compares the usage right data with the non-fungible token stored in the user terminal to determine the usage right data and the non-fungible token. If the conditions are met by comparison, digital content stored in the user terminal, applications related to the content, etc. can be activated. Applications related to digital content can be determined by data on access rights included in packaging data. At this time, the sales verification unit 140 may determine the validity of the usage right data and perform a process of comparing the valid usage right data with a previously issued non-fungible token. The validity of the license data can be determined based on the non-fungible token included in the license data and the authority information obtained using the token.

The result determined to be valid usage rights data may be converted into an authentication value and stored in the product verification server 100. The product verification server 100 may transmit the authentication value to the user terminal and store it. The product verification server 100 can immediately determine the validity of the license data based on the authentication value stored in the user terminal.

When digital content stored in the user terminal or an application related to digital content is activated, it can be determined whether the digital content was acquired by a corresponding product and is linked to a non-fungible token. As a result of the determination, if the digital content is acquired by a corresponding product or is linked to a non-fungible token, it is possible to determine whether to activate the digital content or an application related to the content by checking the sensing behavior of the product or the stored non-fungible token. Using the sensing behavior of the item or the stored non-fungible token, a decision can be made as to whether to activate it or not. Digital content or applications resulting from the act of transferring a non-transferable item, using an item that cannot be reused, or using an item that has exceeded the maximum number of uses may be deactivated rather than activated. Through this, digital content corresponding to the product or an application related to the content can be activated on the user terminal holding the non-fungible token. Information on non-fungible tokens can be verified (verify, confirm) based on data stored in the blockchain system.

When transferring digital content from a first user terminal to a second user terminal, the sales verification unit 140 may move usage rights data corresponding to the digital content. The sales verification unit 140 may determine the validity of the usage right data and move the usage right data whose validity is true. The sales verification unit 140 obtains first license data for the first user terminal and generates second license data that changes the user's identification information to information related to the transferred second user terminal from the first license data. And the second license data can be moved to the second user terminal. The sales verification unit 140 may generate second packaging data corresponding to the second usage right data and transmit it to the second user terminal. Through usage rights data that includes a non-fungible token that proves the scarcity of digital content corresponding to an article, unlimited production of digital content corresponding to an article can be prevented.

The sales verification unit 140 may separately monitor and manage the quantity of tokens that are converted into usage rights data and managed among non-fungible tokens corresponding to products. At this time, the sales verification unit 140 may generate usage right data including identification information of a user whose validity is true. Validity may be judged based on the act of using the content or application, the act of detecting the item, or the act of activating the content or application. The quantity of tokens allocated to each user can be recorded as the quantity of items sold. The quantity of tokens assigned to each user may be increased upon detection of an item. The number of tokens allocated to each item can be recorded. The quantity of tokens may need to be synchronized to the same value as the sales quantity (distribution quantity) of items stored in the distributor server 200.

The sales verification unit 140 uses the user's identification information to request and obtain information about whether the user is the same as the user who acquired the product from the external distributor server, and generates usage rights data if the connected user is not the user who acquired the product. You can handle it so that it doesn't happen. The sales verification unit 140 may additionally perform a process of verifying the user's identification information at any point after generating the license data and/or packaging data based on the identification information acquired from the user terminal. . The sales verification unit 140 verifies a plurality of pieces of identification information at once and can separately manage usage rights data or packaging data based on unverified pieces of identification information. License data or packaging data based on unverified identification information may be re-verified more than a preset number of times. For example, if the verification process does not pass more than three times, the license data or packaging data may be discarded, making it impossible to activate the digital content or an application related to the digital content. Activity-related information can be set to active (1) or inactive (0).

The sales verification unit 140 can execute a smart contract that generates non-fungible tokens corresponding to products. The sales verification unit 140 may include commands for a smart contract that connects to the blockchain system and generates a non-fungible token. The sales verification unit 140 may confirm the quantity of non-fungible tokens upon request and generate non-fungible tokens corresponding to the quantity. Depending on the type of goods, different smart contracts can be implemented. The sales verification unit 140 manages approval signals for each of a plurality of smart contracts and can execute a smart contract corresponding to the received approval signal.

The sales verification unit 140 can also verify the validity of the non-fungible token stored in the user terminal. The sales verification unit 140 may access the blockchain system to obtain the validity of the non-fungible token and determine the validity of the non-fungible token based on this. Through non-fungible tokens distributed in correspondence with goods, goods that are distributed illegally can be selected.

The sales verification unit 140 may acquire information about the user who acquired an item such as an album or ticket, and transmit sound source data to the user's terminal based on the information about the user. The sales verification unit 140 may generate sound source data including a non-fungible token corresponding to an item such as an album or a ticket, one or more sound source contents corresponding to the item, and information about the terminal. The sound source data may include a link to enter a virtual space corresponding to items such as albums and tickets. Links are created differently for each user, that is, for each product, so that each user can be distinguished only by the link.

In another embodiment, the sales verification unit 140 may provide a real-time live image corresponding to the product to the user terminal in response to detection of the product. Real-time live video refers to content that is played only while it is being transmitted. Real-time live video includes content related to the product and may further include information about the user based on detection of the product. For example, the real-time live video includes a live video of a predetermined performance, and may further include an video displaying the IDs of the first user, second user, and third user who detected the product. The first to third users who detected the item can be seen in each corresponding image.

In another embodiment, the sales verification unit 140 may generate sound source data that can be played less than a predetermined limit. In response to access input exceeding the limit number of times, the sound source data may be in an inactive state.

The sales verification unit 140 may obtain information about users who have acquired items such as albums and tickets from the distributor server. Information about the user may include user identification information or identification information about the user terminal. The user's identification information may be a user ID or a unique number assigned to the user. Identification information for the user terminal may be information uniquely issued to the user terminal, such as the user terminal's phone number, physical address, serial number, etc.

The sales verification unit 140 may transmit a product delivery link corresponding to the product to the user who has acquired the product. The sales verification unit 140 transmits a product delivery link through the user's identification information and causes a page for the product delivery link to be displayed on the user terminal. The page for the product delivery link can receive information from the user about the delivery address, delivery date, delivery method, etc. related to product delivery.

The sales verification unit 140 may transmit random content corresponding to the product to the user who has acquired the product. Here, random content refers to a form in which the format of the content and the applications provided through the content can be changed. For example, 4 minutes of content may be provided to the first user who acquires the same product, and 20 minutes of content may be provided to the second user who acquires the product. Random content may be an image displayed on a user terminal, an item that operates in a certain game, or goods delivered to an actual user. For random content, if first to third content is provided, the provided quantity of each content may be within a set quantity. For example, the first content may be designed to be provided in a set quantity, such as 10 pieces of content, 100 pieces of second content, and 1000 pieces of third content.

The sales verification unit 140 may obtain information about the terminal from the terminal in response to a request from the terminal of the user who has acquired the identification information of the product. The request from the user terminal may be generated by detecting an item or may be generated by user input. Information about the terminal may include terminal model information, serial information, or phone number.

The sales verification unit 140 determines whether a non-fungible token corresponding to the music album exists, and if a non-fungible token exists, may generate sound source data or execution of an application related to the sound source. Here, it is called an album, but it can be replaced with a ticket or product.

The sales verification unit 140 may record information on sales activities of items such as albums and tickets and calculate the sales quantity of albums and tickets. Sales quantity may refer to quantitative information about online or offline sales activities. In other words, it refers to the quantity of items such as albums and tickets sold online or offline. Albums, tickets, etc. contain the right to acquire digital content and may or may not include digital content.

The sales verification unit 140 may generate a non-fungible token corresponding to an album and execute a smart contract for the non-fungible token.

The sales verification unit 140 may receive information on the sales activity of the album from the distribution company server, and collect and generate information on whether or not the non-fungible token of the album is sold by considering the information on the sales activity.

The sales verification unit 140 may execute content for the sound source data by loading a non-fungible token included in the sound source data in response to an execution input of the sound source data from the user terminal. The sales verification unit 140 may determine the validity of a non-fungible token included in the sound source data and execute content for the sound source data. The validity of a non-fungible token can be judged by whether it matches tokens issued through a legitimate process by accessing the blockchain system.

The sales verification unit 140 may be designed to obtain an admission ticket to a predetermined online or offline space by detecting an item. When a signal for detection of an item is obtained by the user terminal, the sales verification unit 140 may generate usage right data and/or packaging data for admission authority in response to the detection of the item. License data includes data linking information about the product and information about the user. Packaging data is data stored to immediately activate content, applications, access rights, admission rights, transfer rights, use rights, etc. corresponding to the product in the terminal where the product has been detected. The sales verification unit 140 may be implemented to provide a predetermined service to the user terminal or user by loading packaging data stored in the user terminal. The sales verification unit 140 may initially check packaging data and guide user terminals without packaging data to perform a packaging data generation procedure. The sales verification unit 140 may secondarily determine the validity of the packaging data of the user terminal using the packaging data and self-managed usage rights data.

In another embodiment, the sales verification unit 140 may obtain a detection signal for the first ticket from the first user terminal among registered tickets. Here, the first ticket may be of various forms such as paper, plastic, or magnetic, and may be substituted for the article described in this specification. The sales verification unit 140 acquires identification information of the first ticket in response to a detection signal for the first ticket, and uses the identification information of the first ticket to apply content corresponding to the first ticket or an application related to the content. You can generate data about . A detection signal for the first ticket may be generated by recognizing the tag included in the first ticket or the first ticket with an image sensor. Identification information of the first ticket may be obtained by combining data included in the detection signal of the first ticket and/or data acquired, changed, or converted through data included in the detection signal. Data on the content corresponding to the first ticket or the application related to the content is stored in advance and can be obtained from the distributor server.

The sales verification unit 140 may transmit data about the content or an application related to the content to the first user terminal and process the content and the application related to the content to run on the first user terminal. The data transmitted to the first user terminal may be data about the content or an application related to the content itself, or may be data about the content or an application related to the content that has been modified.

The sales verification unit 140 may obtain information about the owner of the first ticket using the identification information of the first ticket included in the detection signal. Information about the owner of the first ticket can be obtained through the distributor server or previous access history. With respect to each ticket, an owner determination smart contract may operate to determine the owner of each ticket.

The sales verification unit 140 may use information about the owner of the first ticket to accumulate a reward related to the first ticket to the owner's account. The owner's account may be registered with one or more service providers. Rewards may be credited separately to each of the accounts of one or more owners.

The sales verification unit 140 may receive detection signals for registered tickets, generate user content corresponding to the terminals of senders of the detection signals, and link the user content to content corresponding to the first ticket. .

Here, user contents may be changeable by user input from each sender's terminal. For example, messages, videos, sound sources, etc. entered by the user, such as ‘I am happy today’, ‘Do your best today too’, etc. can be user content. The user content may include commands for the character included in the content, such as moving to the right, moving to the left, using a weapon, etc., and the content corresponding to the first ticket is generated by the user content such as moving to the right, moving to the left, using a weapon, etc. It can be changed through actions such as use.

When a plurality of user contents are received for the content corresponding to the first ticket, each of the user contents is transformed into a combination of the content corresponding to the first ticket and can be activated only in each user terminal. Each of the user contents may be designed to be activated only when communication with each sender's terminal is connected.

In an optional embodiment, item verification server 100 may obtain authorization information for the first ticket using a non-fungible token. Depending on the authority information for the first ticket, it may be determined whether to generate usage rights data. For example, when non-transferable rights information is set for the first ticket, usage rights data may not be generated according to the rights information for the first ticket. It can also be processed so that owner information cannot be changed. When authority information limiting the number of uses is set for the first ticket, usage rights data including the maximum number of uses can be generated according to the authority information for the first ticket. The maximum usage count value may be stored and managed corresponding to the non-fungible token.

In S110, the product verification server 100 allows the first user who acquired the product to detect the product through the first user terminal. The first user can detect the product by photographing the product obtained offline or by recognizing the number or code attached to the product.

In S120, the product verification server 100 may obtain product identification information through detection of the product using a camera, sensor, or input unit. The product verification server 100 may use the product identification information to obtain a non-fungible token corresponding to the product. Non-fungible tokens corresponding to items may be stored and managed in a blockchain system. Product identification information may be assigned to each individual product even if it corresponds to the same product. For example, even if it is a first book, the identification information may be different depending on the number of copies of the first book. Even if it is the first album, the identification information may be different depending on the number of copies of the first album. The product verification server 100 can obtain product identification information by detecting the barcode and QR code printed on the ticket through a camera. The product verification server 100 may obtain product identification information by detecting the RF antenna included in the ticket through the sensor unit. The product verification server 100 may obtain product identification information by inputting information on the ticket.

In S130, the item verification server 100 obtains identification information of the first user from the first user terminal in response to acquisition of the non-fungible token and sets the user as the owner of the item using the identification information of the first user. License data can be created and recorded. The first user terminal or the owner of the first user terminal may be registered as the owner.

In an optional embodiment, the product verification server 100 may obtain authority information for the product using a non-fungible token. Depending on the rights information for the product, it can be decided whether to generate usage rights data. For example, when non-transferable rights information is set for a product, usage right data may not be generated according to the rights information for the product. It can also be processed so that owner information cannot be changed. When authority information limiting the number of uses is set for a product, usage right data including the maximum number of uses can be generated according to the authority information for the product. The maximum usage count value may be stored and managed corresponding to the non-fungible token.

In S140, the product verification server 100 may generate packaging data corresponding to the product, including a non-fungible token, digital content corresponding to the product, and identification information of the first user, and transmit it to the first user terminal. Through this, it is possible to acquire a non-fungible token corresponding to the product online through the user terminal by detecting the product. At this time, examples of goods include physical items such as records, books, wine, paintings, artwork, expensive luxury goods, clothing, shoes, bags, accessories, goods, admission tickets, cards, business cards, coupons, etc. , may be digital content. Goods may be scarce or may be designed to be distributed in limited quantities.

In S210, the product verification server 100 may search for usage right data corresponding to the product in response to user input following detection of the product from the user terminal and compare the usage right data with the non-fungible token stored in the user terminal. The usage rights data may be data separately managed by the product verification server 100. Usage rights data may include values such as non-transferability, maximum number of uses, etc.

In S220, the product verification server 100 may compare the usage right data and the non-fungible token and activate the digital content stored in the user terminal if a set condition is satisfied. Whether the token included in the license data is a valid token, whether the token included in the license data and the token obtained from the packaging data are the same, the information about the terminal included in the license data, and the user's identification information obtained from the packaging data. By considering at least one thing, it can be determined whether digital content is activated. In an optional embodiment, whether the digital content is activated may be determined by considering whether the token included in the usage right data has a non-transferable condition, whether the maximum number of uses is exceeded, etc.

In a state where there is no communication with the product verification server 100, it is possible to determine whether to run the content or an application related to the content by considering the packaging data stored in the user terminal and whether the packaging data is active. When communication with the product verification server 100 is established again, it is possible to verify again whether the packaging data is active.

When digital content stored in the user terminal is activated, the product verification server 100 may determine whether the digital content was acquired by a corresponding product and is associated with a non-fungible token.

As a result of the determination, if the digital content is acquired by a corresponding product or is linked to a non-fungible token, it is possible to determine whether to activate the digital content by detecting the product or checking the non-fungible token.

Through this, digital content corresponding to the product can be activated on the user terminal holding the non-fungible token. Information on non-fungible tokens can be verified (verify, confirm) based on data stored in the blockchain system.

In S310, when transferring digital content from a first user terminal to a second user terminal, the product verification server 100 may move usage right data corresponding to the digital content. The product verification server 100 may change the license data to include information about the second user terminal and record it again. The product verification server 100 obtains first license data for the first user terminal and generates second license data that changes the user's identification information to information related to the transferred second user terminal from the first license data. And the second usage right data can be moved to the second user terminal, but the method is not limited to this. The second usage right data may be stored in the memory of the product verification server 100.

In S320, the product verification server 100 may generate second packaging data corresponding to the second usage right data and transmit it to the second user terminal. Through usage rights data that includes a non-fungible token that proves the scarcity of digital content corresponding to an article, unlimited production of digital content corresponding to an article can be prevented. Digital content can be distributed with rights such as transfer restrictions, maximum number of uses, etc., and use of digital content can be restricted by rights such as transfer restrictions and maximum number of uses.

The non-fungible tokens included in the first usage rights data and the second usage rights data may be the same or different. The first license data and the second license data can be changed into a connected data structure. It may be updated with second usage right data instead of first usage right data, but is not limited to this.

Additionally, the product verification server 100 may execute a user authentication process for the second user terminal as follows.

The product verification server 100 may transmit a signal requesting an action to detect an article to the second user terminal. At this time, the item may be detected for the first time or may have been previously detected. In response to the request signal, the second user terminal detects the product, or the product's code, tag, etc., and determines whether the information about the product obtained through the detected event matches the packaging data stored in the second user terminal. You can judge. If there is identity between the information on the sensed product and the packaging data, usage rights data for the second user terminal may be generated.

If the packaging data is not stored, a procedure for transmitting the packaging data to the second user terminal may be executed. The product verification server 100 may generate packaging data including identification information of the second user based on information about the sensed product and transmit it to the second user terminal. At this time, a process of generating identification information of the second user may be executed.

The product verification server 100 may generate and manage second usage rights data including information about the second user terminal. The product verification server 100 may replace the owner of the product with second usage rights data for a second user and store the data.

Additionally, the product verification server 100 may perform a secure payment function corresponding to the transfer or transfer of the product upon request from the user terminal. A secure payment function may be provided in response to a payment request including the transferee, transferor, and transfer amount. When the payment process for the transfer amount is approved at the transferor terminal, approval completion information regarding this may be transmitted to the transferor terminal. In response to completion of approval, the process of transferring digital content from the transferor terminal to the transferee terminal may be performed as described above.

Figure 6 is a flowchart of a non-fungible token creation process according to embodiments of the present disclosure.

In S410, the product verification server 100 may obtain and record product identification information from an external distributor server.

In S420, the product verification server 100 may generate in advance non-fungible tokens equal to the quantity of identification information obtained in response to the identification information obtained from the distribution company server. Information about non-fungible tokens can be created and managed in the blockchain system.

In S430, the product verification server 100 may process a smart contract for a non-fungible token corresponding to the product to be executed in the blockchain system.

Through this, a non-fungible token equivalent to the distributed quantity of goods can be created. Non-fungible tokens can be created by smart contracts running on the blockchain.

In S510, the product verification server 100 may obtain information about the user who acquired products such as albums, tickets, and invitations. For goods, rights may be set such as non-transferability and maximum use limit.

In S520, the product verification server 100 sends a non-fungible token corresponding to the product, one or more sound source contents corresponding to the product, and sound source data including information about the terminal to the user's terminal based on information about the user. can be created. Sound source content may refer to content related to a non-fungible token. Sound source content may be accessed within a certain limit according to the token. Activation of sound source content may be restricted for accesses exceeding the limit.

In S530, the product verification server 100 may transmit sound source data to the user terminal and process the sound source data to be stored in the user terminal.

In S540, the product verification server 100 may record information on sales activities of music records and calculate the sales quantity of music records.

In S550, the product verification server 100 receives information on the sales activity of the album from an external distributor server, takes the information on the sales activity into account, collects information on whether the non-fungible token of the album is sold, and can be created. The product verification server 100 may load the identification information of the product belonging to the corresponding album and calculate the sales quantity of the product using the quantity of usage rights data corresponding to the product identification information. The validity of each license data can be determined by checking the validity of the token included in each license data through the blockchain system. The product verification server 100 can manage only valid license data by removing license data whose validity is false. The quantity and capacity of usage rights data may match the sales quantity of the product.

In S610, the product verification server 100 may obtain information about the user who acquired the album. Information about the user who acquired the record may include the user's identification information. The user's identification information may include a user ID, the user's phone number, the user's email address, etc., and may be one of various types of information that identifies the user.

In S620, the product verification server 100 may generate a non-fungible token corresponding to an album and execute a smart contract for the non-fungible token.

In S630, the product verification server 100 generates sound source data including a non-fungible token corresponding to the record, one or more sound source contents corresponding to the record, and information about the terminal to the user's terminal based on information about the user. can do.

In S640, the product verification server 100 may transmit sound source data to the user terminal in response to a request from the user terminal and process the sound source data to be stored in the user terminal.

In S650, the product verification server 100 may execute content for the sound source data by loading a non-replaceable token included in the sound source data in response to an execution input of the sound source data from the user terminal.

Through this, music data accessible by a non-fungible token can be selected and executed. If the non-fungible token is invalid or the non-fungible token is not legal, execution of the sound source data may be blocked (locked). If the validity of the non-fungible token is confirmed (if TRUE), the execution of the corresponding sound source data can be unlocked. The validity of the token can be confirmed through the blockchain system.

The device described above may be implemented with hardware components, software components, and/or a combination of hardware components and software components. For example, devices and components described in embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), etc. , may be implemented using one or more general-purpose or special-purpose computers, such as a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. Additionally, a processing device may access, store, manipulate, process, and generate data in response to the execution of software. For ease of understanding, a single processing device may be described as being used; however, those skilled in the art will understand that a processing device includes multiple processing elements and/or multiple types of processing elements. It can be seen that it may include. For example, a processing device may include a plurality of processors or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are possible.

Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing unit to operate as desired, or may be processed independently or collectively. You can command the device. Software and/or data may be used on any type of machine, component, physical device, virtual equipment, computer storage medium or device to be interpreted by or to provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on the medium may be specially designed and configured for the embodiment or may be known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. -Includes optical media (magneto-optical media) and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include machine language code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with limited examples and drawings, various modifications and variations can be made by those skilled in the art from the above description. For example, the described techniques are performed in a different order than the described method, and/or components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or other components are used. Alternatively, appropriate results may be achieved even if substituted or substituted by an equivalent.

Therefore, other implementations, other embodiments, and equivalents of the claims also fall within the scope of the claims described below.

Claims

Processing, by the product verification server, an act of detecting the product through a first user terminal by a first user who has acquired the product;

Obtaining, by the product verification server, identification information through detection of the product in response to the action;

Obtaining, by the product verification server, a non-fungible token corresponding to the product using the identification information;

The item verification server, in response to obtaining the non-fungible token, obtains identification information of the first user from the user terminal and uses the identification information of the first user to identify the first user as the owner of the item. generating and recording first license data that sets; and

The product verification server transmits first packaging data corresponding to the product, including the non-fungible token, digital content corresponding to the product, and identification information of the first user, to the first user terminal, A product verification method for verifying the acquisition of an article using a non-fungible token, comprising: storing first packaging data corresponding to the article in a user terminal.
According to paragraph 1,

The product verification server responds to a user input according to detection of the product from a first user terminal,

Searching for usage right data corresponding to the article and comparing the usage right data with a non-fungible token stored in the first user terminal;

A non-fungible token for acquisition of an article, further comprising the step of activating, by the article verification server, digital content stored in the first user terminal when a predetermined condition is satisfied by comparing the usage right data with the non-fungible token. Product verification method verified by .
According to paragraph 1,

In response to a user input for moving the first usage right data from the first user terminal to the second user terminal,

The product verification server obtains the first license data, generates second license data that changes the user's identification information to information related to the second user terminal from the first license data, and generates the second license data. Move data to the second user terminal,

Generating second packaging data corresponding to the second usage right data and transmitting it to the second user terminal; Product verification method for verifying the acquisition of the product with a non-fungible token.
According to paragraph 1,

Product verification that verifies the acquisition of the product using a non-fungible token, further comprising: calculating, by the distribution company server, a first quantity of products purchased through the user's purchase behavior from among identification numbers of products distributed offline; method.
According to clause 4,

The product verification server calculates a second quantity of tokens converted into usage rights data among non-fungible tokens corresponding to the items, and whether the second quantity matches the first quantity received from the distributor server. A product verification method for verifying the acquisition of an article using a non-fungible token, further comprising: determining.
According to paragraph 1,

In the step of generating and recording the first license data,

The product verification server uses the identification information of the first user to request and obtain information about whether the first user is the same as the user who acquired the product from an external distributor server,

An article verification method for verifying the acquisition of an article with a non-fungible token, wherein if the first user is not the user who acquired the article, the first usage right data is not generated.
According to paragraph 3,

Before the step of obtaining identification information obtained through detection of the article,

Obtain and record the identification information of the product from an external distributor server,

In response to the identification information obtained from the external distribution company server, the product verification server generates non-fungible tokens corresponding to the quantity of the obtained identification information;

An article verification method for verifying the acquisition of an article with a non-fungible token, further comprising processing the article verification server to execute a smart contract for a non-fungible token corresponding to the article in a blockchain system.
According to paragraph 3,

The product verification server detects the product in the second user terminal and obtains identification information of the product through detection of the product;

An article that verifies the acquisition of the article with a non-fungible token, further comprising the step of the article verification server setting whether the second usage right data corresponding to the article can be activated to 1 using the identification information of the article. Verification method.
Comprising one or more processors and a computer-readable medium,

The processor detects the article through a first user terminal by a first user who has acquired the article,

Obtain identification information through detection of the item, and use the identification information to obtain a non-fungible token corresponding to the item,

In response to acquiring the non-fungible token, obtain identification information of the first user from the user terminal and use the identification information of the user to generate first usage rights data that sets the user as the owner of the article. record,

First packaging data corresponding to the product, including the non-fungible token, digital content corresponding to the product, and identification information of the first user, is transmitted to the first user terminal, and the product is sent to the user terminal. An article verification server storing corresponding first packaging data.
According to clause 9,

The processor,

In response to a user input based on detection of the article from a first user terminal, searching for usage right data corresponding to the article, comparing the usage right data with a non-fungible token stored in the first user terminal,

An item verification server that compares the usage right data and the non-fungible token and activates digital content stored in the first user terminal when a predetermined condition is satisfied.
According to clause 9,

The processor,

In response to a user input for moving the first usage right data from the first user terminal to the second user terminal, the product verification server obtains the first usage right data, and identifies the user in the first usage right data. Generating second usage rights data that changes information into information related to the second user terminal, and moving the second usage rights data to the second user terminal,

An item verification server that generates second packaging data corresponding to the second usage right data and transmits it to the second user terminal.
According to clause 9,

The processor,

A product verification server wherein the distribution company server calculates the first quantity of products purchased through a user's purchase behavior among the identification numbers of products distributed offline.
According to clause 12,

The processor,

Product verification, which calculates a second quantity of tokens converted into usage rights data among non-fungible tokens corresponding to the items, and determines whether the second quantity matches the first quantity received from the distributor server. server.
According to clause 9,

The processor,

Using the identification information of the first user, request and obtain information about whether the first user is the same as the user who acquired the product from an external distributor server,

If the first user is not the user who acquired the product, the product verification server processes not to generate the first usage right data.
According to clause 11,

The processor,

Obtain and record the identification information of the product from an external distributor server,

In response to the identification information obtained from the external distributor server, non-fungible tokens corresponding to the quantity of the obtained identification information are generated,

An item verification server that processes execution of a smart contract for a non-fungible token corresponding to the item on a blockchain system.