Manufacturing method and system for products produced by printing

Abstract

Provided is a technique for enabling procurement of a non-fungible token (NFT) by using a readily available product. The disclosed method comprises: first identification information for identifying a product manufactured by printing being acquired by an issuing device for printing the product; data for printing the product identified by the first identification information being acquired by the issuing device from an external device via a network by using the first identification information; and, the data for printing being printed by the issuing device. The data for printing the product identified by the first identification information includes data for machine-readable code. The code indicates at least second identification information for a management system for NFTs recorded in a blockchain to identify a product NFT with which data related to the product are associated. When the code is read by a terminal, the management system acquires the second identification information indicated by the code from the terminal, and transmits the product non-fungible token identified by the second identification information to a blockchain account used in the terminal that read the code.

Description

Technical Field

[0001] The present disclosure relates to a method and system for manufacturing products manufactured by printing. This application claims priority based on Japanese Application No. 2021-115309 filed on July 12, 2021, and incorporates by reference all the descriptions set forth in the Japanese application.

Background Art

[0002] Patent Document 1 discloses a ticket issuing system installed in a convenience store or the like. The ticket issuing system of Patent Document 1 includes a management device and a ticket issuing device that issues tickets based on an instruction from the management device. The ticket issuing device has a function as a printer and prints ticket information on ticket paper.

[0003] Patent Document 2 discloses a content providing system for a content printing service. The content providing system of Patent Document 2 includes a terminal and a content providing server. The terminal and the content providing server are connected via a network. The terminal is used for a user to purchase content provided by the content providing system. The terminal is, for example, a multifunction device provided in a store such as a convenience store. The multifunction device has a function as a printer. The multifunction device prints content such as photos purchased by the user operating the multifunction device.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

[0005] Here, ticket data or images such as photographs may be treated as digital information rather than being printed on tangible media such as paper. For example, digital tickets can be displayed on user devices such as smartphones. If digital tickets can be handled on user devices such as smartphones, user convenience is greatly enhanced. Also, if images can be displayed on user devices such as smartphones, the user's enjoyment increases.

[0006] The inventors conceived the idea of ​​using non-fungible tokens (NFTs) on a blockchain for valuable digital data such as ticket data or images.

[0007] NFTs are a type of token whose owner is recorded on the blockchain. Besides non-fungible tokens, there are also fungible tokens. Fungible tokens can sometimes possess currency-like properties, such as being exchangeable for fiat currency.

[0008] Unlike fungible tokens, NFTs are non-fungible tokens. The ownership of an NFT is recorded on a blockchain, a distributed ledger computer system. This allows NFTs to be used for trading digital data such as game items or digital art.

[0009] Since NFT transactions take place on the blockchain, obtaining an NFT generally requires a fungible token (cryptocurrency) on the blockchain. Examples of fungible tokens (cryptocurrencies) on the blockchain include Bitcoin or Ethereum.

[0010] However, blockchain technology is not yet widespread enough for many people to use. Therefore, even if one tries to use NFTs to trade valuable digital data such as ticket data or images, it can be difficult for users who are unfamiliar with blockchain and do not hold fungible tokens (crypto assets) to obtain such NFTs.

[0011] Therefore, the present inventors came up with a novel idea to facilitate the acquisition of NFTs by utilizing products manufactured by printing on tangible media such as paper, as shown in Patent Document 1 (ticket) or Patent Document 2 (photograph), and the issuing device for such products. The issuing device here is, for example, the ticket issuing device in Patent Document 1 or the multifunction printer for content printing services in Patent Document 2.

[0012] The tickets in Patent Document 1 and the photographs in Patent Document 2 are both types of products issued by printing. Content such as tickets or photographs printed on a tangible medium like paper can be easily obtained at stores such as convenience stores. There is a need for a technology or related technology that enables the acquisition of NFTs using such easily obtainable products.

[0013] One aspect of this disclosure is a method for manufacturing a product. The method of disclosure comprises: an issuing device for printing a product acquires first identification information for identifying a product to be manufactured by printing; the issuing device acquires data for printing the product identified by the first identification information from an external device via a network using the first identification information; and the issuing device prints the data for printing, wherein the data for printing the product identified by the first identification information includes data of a machine-readable code, the code indicates at least second identification information for a non-fungible token management system recorded on a blockchain to identify a product non-fungible token to which data related to the product is associated; when the code is read by a terminal, the management system acquires the second identification information indicated by the code from the terminal; and the management system is used to transmit the product non-fungible token identified by the second identification information to a blockchain account used by the terminal that read the code.

[0014] Other aspects of this disclosure and further details thereof will be described in the embodiments described below. [Brief explanation of the drawing]

[0015] [Figure 1] Figure 1 is a diagram showing the configuration of the system according to the first embodiment. [Figure 2] Figure 2 is a diagram illustrating the configuration of the ticket NFT management system. [Figure 3] Figure 3 is a flowchart of the ticket manufacturing method. [Figure 4] Figure 4 is a flowchart of the ticket manufacturing method. [Figure 5] Figure 5 shows the procedure for obtaining a ticket NFT. [Figure 6] Figure 6 shows digital tickets and ticket NFTs. [Figure 7] Figure 7 is a diagram showing the configuration of the system according to the second embodiment. [Figure 8] FIG. 8 is a diagram showing an example screen of a content introduction website. [Figure 9] FIG. 9 is a configuration diagram of a content NFT management system. [Figure 10] FIG. 10 is a flowchart of a method for manufacturing content. [Figure 11] FIG. 11 is a flowchart of a method for manufacturing content. [Figure 12] FIG. 12 is a diagram showing a procedure for obtaining a content NFT. [Figure 13] FIG. 13 is a diagram showing digital content and a content NFT.

Embodiments for Carrying Out the Invention

[0016] <1. Overview of the Method and System>

[0017] (1) The method for manufacturing a product according to the embodiment is such that an issuing device for printing the product acquires first identification information for identifying the product manufactured by printing, and the issuing device acquires data for printing the product identified by the first identification information from an external device via a network using the first identification information, and the issuing device prints the data for printing. Note that the manufacturing process of the product may include processes other than printing. The product manufactured by printing only needs to be a product manufactured by a process including at least printing. In the product, the part obtained by printing may be a part of the components of the product.

[0018] The data for printing the product identified by the first identification information may include data for a machine-readable code. The code may indicate at least a second identification information for a non-fungible token management system recorded on a blockchain to identify a product non-fungible token to which data related to the product is associated. When the code is read by a terminal, the management system may use the second identification information indicated by the code to obtain the second identification information from the terminal, and the management system may use the product non-fungible token identified by the second identification information to a blockchain account used by the terminal that read the code. The blockchain account used by the terminal that read the code is, for example, the blockchain account of the user who owns the terminal.

[0019] (2) Preferably the external device further includes obtaining the second identification information indicated by the code from the management system, or from the management system via a device that has obtained the second identification information from the management system.

[0020] (3) In (1) or (2) above, the product may be a printed ticket. The data associated with the product may be ticket data having information contained in the ticket. The product nonfungible token may be a ticket nonfungible token to which the ticket data is associated.

[0021] (4) In (1) or (2) above, the product may be printed content. The data associated with the product may be content data having information contained in the printed content. The product nonfungible token may be a content nonfungible token to which the content data is associated.

[0022] (5) In any one of the above paragraphs (1) to (4), it is preferable that the issuing device is a device installed inside a retail store.

[0023] (6) In any one of the above paragraphs (1) to (5), it is preferable that the issuing device is configured to process payment for the goods and to print the goods after the payment has been processed.

[0024] (7) Preferably, the first identification information is displayed on the website where the product is listed, as described in any one of items (1) to (6) above. The website where the product is listed is, for example, a ticket reservation website or a content introduction website.

[0025] (8) In any one of the above paragraphs (1) to (7), it is preferable that the second identification information is associated with the first identification information in the management system, or is the same information as the first identification information. The second identification information may also be associated with the first identification information in the external device.

[0026] (9) The system according to the embodiment comprises an issuing device, an external device connected to the issuing device via a network, and a management system for non-fungible tokens recorded on a blockchain, wherein the issuing device is configured to acquire first identification information for identifying a product, acquire data for printing the product identified by the first identification information from the external device, and print the data for printing, wherein the data for printing the product includes machine-readable code data, the code is configured to indicate at least second identification information for identifying a non-fungible token associated with the product in a management system for non-fungible tokens recorded on a blockchain, and the management system is configured to, upon acquiring the second identification information from a terminal that reads the code, send the product non-fungible token identified by the second identification information to a blockchain account used by the terminal that read the code.

[0027] (10) A system according to an embodiment comprises an issuing device and an external device connected to the issuing device via a network, wherein the issuing device is configured to acquire first identification information for identifying a product, acquire data for printing the product identified by the first identification information from the external device, and print the data for printing, wherein the data for printing the product includes machine-readable code data, the code is configured to indicate at least second identification information for identifying a non-fungible token associated with the product in a non-fungible token management system recorded on a blockchain, and the external device is configured to acquire the second identification information indicated by the code from the management system, or from the management system via a device that has acquired the second identification information from the management system.

[0028] <2. Examples of manufacturing methods and systems for goods produced by printing>

[0029] <2.1 First Embodiment: Ticket Issuance System>

[0030] Figure 1 shows an example of a system 500 according to the first embodiment. In the first embodiment, the product is a printed ticket 1. The ticket 1 is a tangible object. The system 500 according to the first embodiment is used for issuing and using the ticket 1. The system 500 according to the first embodiment also handles digital tickets 13A displayed on a user terminal 30.

[0031] Ticket 1 is, for example, an admission ticket to an event, an admission ticket to a facility, a ride ticket, a ticket for enjoying other services, a voucher for goods, a gift certificate, and a discount coupon. An event is, for example, a concert, a movie, a play, an exhibition, a trade fair, a sporting event, and a festival. A facility is, for example, an amusement park, a zoo, a botanical garden, an art museum, a museum, a cinema, a shop, and a tourist attraction. A ride is, for example, an airplane, a ship, a train, a bus, and a taxi.

[0032] Ticket 1 is constructed, for example, by printing ticket data on ticket paper. As shown in Figure 1, the ticket data includes, for example, the venue, event name, date and time, seat number, and ticket number. The ticket number is a unique number for each individual ticket. Here, as an example, the ticket number is assumed to be the same as the ticket exchange number (first identification information) described later. The ticket shown in Figure 1 is assigned the ticket number (exchange number; first identification information) "abcdefg".

[0033] Ticket 1 has the aforementioned ticket data along with a machine-readable code 1A printed on it. Code 1A is, for example, a two-dimensional code. Code 1A will be explained later. Code 1A also constitutes the ticket data.

[0034] Digital ticket 13A is an electronic version of the ticket data and other data included in ticket 1. The ticket data of digital ticket 13A includes, for example, data regarding the venue, event name, date and time, seat number, and ticket number. Digital ticket 13A is stored in database 13, which will be described later.

[0035] A user who has purchased Ticket 1 may use Ticket 1 or Digital Ticket 13A when entering the event. The ability to use Digital Ticket 13A eliminates the need for the user to carry their physical Ticket 1 when entering the event, thus improving user convenience. Furthermore, because the user receives not only digital information (Digital Ticket 13A) but also a tangible physical item (Paper Ticket 1), it enhances the user's sense of purchase and is therefore preferable.

[0036] The system 500 according to the first embodiment includes an issuing device 200 and a ticket issuing server 300. The issuing device 200 is installed, for example, in a retail store. The retail store is, for example, a convenience store, a supermarket, or a department store. The issuing device 200 is configured to print ticket data on ticket paper and issue ticket 1. The issuing device 200 is installed, for example, at the cash register counter of the store and operated by store staff. The issuing device 200 may also be installed in the store so that customers can operate it directly.

[0037] When the issuing device 200 receives an operation from an operator such as a store staff member or a customer (user), it obtains the necessary ticket data from the ticket issuing server 300 located outside the store and issues ticket 1 by printing that ticket data. The issuing device 200 is configured to accept input of a ticket exchange number, which will be described later. The exchange number is entered, for example, by key operation or by reading a code indicating the exchange number with a reader.

[0038] The issuing device 200 is configured to accept payment requests for ticket 1 and perform payment processing prior to issuing ticket 1. Ticket 1 is issued after the payment processing is completed. Payment can be made, for example, by cash, credit card, electronic money, or bank account debit. A person (user) who wishes to purchase ticket 1 can pay for ticket 1 at a store such as a convenience store, making it easy to obtain ticket 1. In addition, by paying for ticket 1 at a store, it is also possible to obtain the non-fungible token 101 described later. Since the issuing device 200 can process payments, it can also be considered as a payment processing device 200.

[0039] Furthermore, it is preferable that the system 500 is equipped with multiple issuing devices 200. Each of the multiple issuing devices 200 is installed in the store.

[0040] The ticket issuing server 300 is connected to the issuing device 200 via a network 15 such as the Internet. The ticket issuing server 300 is an external device installed in a separate location from the issuing device 200 so that multiple issuing devices 200 can be connected to it. The ticket issuing server 300 holds ticket data for tickets 1 issued by the issuing device 200 and is configured to transmit the ticket data to the issuing device 200 in response to a request from the issuing device 200.

[0041] The ticket issuance server 300 is comprised of a computer equipped with a processor and memory. The ticket issuance server 300 may be comprised of a single computer or multiple computers connected via a network 15. The memory is connected to the processor. The memory comprises, for example, primary storage and secondary storage. The primary storage is, for example, RAM. The secondary storage is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The memory contains computer programs executed by the processor. The processor reads and executes the computer programs stored in memory. The computer program for the ticket issuance server 300 has program code to cause the computer to function as the ticket issuance server 300.

[0042] The system 500 according to the first embodiment may include a ticket reservation web server 400 connected to the network 15. The ticket reservation web server provides a website that is viewed by people who wish to purchase ticket 1. This website accepts reservation operations for ticket 1 by people who wish to purchase ticket 1 and outputs an exchange number (first identification information) for ticket 1. The exchange number for ticket 1 is input to the issuing device 200 for issuing ticket 1. The ticket reservation web server 400 may also be configured to accept payment operations for the price of ticket 1 and execute payment processing to settle the payment. In this case, at the store where the issuing device 200 is installed, payment is not required, or only a ticket issuance fee needs to be paid.

[0043] The ticket reservation web server 400 is comprised of a computer equipped with a processor and memory. The ticket reservation web server 400 may be comprised of a single computer or multiple computers connected via a network 15. The memory is connected to the processor. The memory comprises, for example, primary storage and secondary storage. The primary storage is, for example, RAM. The secondary storage is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The memory contains computer programs executed by the processor. The processor reads and executes the computer programs stored in memory. The computer program for the ticket reservation web server 400 has program code to cause the computer to function as the ticket reservation web server 400.

[0044] The system 500 according to the first embodiment may include a ticket non-fungible token management system 10 (ticket NFT management system 10) connected to the network 15.

[0045] Figure 2 shows the ticket NFT management system 10. The ticket NFT management system 10 according to this embodiment uses a blockchain 11 to manage digital tickets 13A and non-fungible tokens 101 (ticket NFTs 101) associated with the digital tickets 13A.

[0046] The ticket NFT management system 10 includes a database 13 in which digital tickets 13A are stored. The database 13 is comprised of a file system connected to a network 15, such as the Internet. The file system comprises one or more computers connected to the network 15. The database 13 is comprised of, for example, an IPFS (InterPlanetary File System). IPFS is an example of a P2P (Peer to Peer) distributed file system. When a digital ticket 13A is issued electronically, the digital ticket 13A is stored in the database 13.

[0047] The digital ticket 13A stored in database 13 is displayed on the terminal 30 of the user who owns the digital ticket 13A. For example, a user can enter or participate in an event by displaying the digital ticket 13A on terminal 30.

[0048] In this embodiment, a blockchain 11 is used for managing the digital ticket 13A. The blockchain 11 is comprised of a P2P (Peer to Peer) computer network system in which multiple computers are interconnected.

[0049] In Blockchain 11, tokens can be traded between blockchain addresses, and records of token transactions are recorded in the distributed ledger of Blockchain 11. A blockchain address represents, for example, a user account on Blockchain 11. For example, if a user has account 110 on Blockchain 11, then account 110 has a predetermined blockchain address (user address).

[0050] Blockchain addresses are represented as, for example, 0xZZZZZZZ. Each Z is an independent, arbitrary number or symbol, and the number of Z digits is predetermined within the blockchain.

[0051] In Blockchain 11, tradable tokens include fungible tokens (fungible tokens) and non-fungible tokens (NFTs). An example of a fungible token is Ether.

[0052] Unlike fungible tokens, NFTs are non-fungible tokens. To ensure non-fungibility, NFTs have a unique identifier on Blockchain 11 that allows them to be distinguished from other NFTs. Hereafter, this identifier will be referred to as the NFT identifier. The NFT identifier is sometimes written as "NFT_ID".

[0053] In the first embodiment, the digital ticket 13A is associated with the non-fungible token 101. That is, the digital ticket 13A is NFT-enabled. The non-fungible token 101 associated with the digital ticket 13A is also referred to as "ticket NFT 101" ("NFT ticket / NFTticket" is a registered trademark in Japan). Hereinafter, the NFT identifier (NFT_ID) of ticket NFT 101 will be represented by "A".

[0054] In the first embodiment, the association between the digital ticket 13A and the ticket NFT 101 is achieved, for example, by associating the digital ticket 13A with the NFT_ID:A of the corresponding ticket NFT 101 and storing it in the database 13. If one digital ticket 13A is associated with only one corresponding ticket NFT 101's NFT_ID:A, a one-to-one correspondence between the ticket NFT 101 and the digital ticket 13A is achieved. In this embodiment, the ticket NFT 101 itself does not need to contain the ticket data included in the digital ticket 13A, so the amount of data of the ticket NFT 101 recorded in the blockchain 11 can be reduced. As a result, the cost of using the blockchain 11 can be reduced.

[0055] A single digital ticket 13A may be associated with the NFT_IDs of multiple ticket NFTs 101. In cases where the data for each of the multiple digital tickets 13A can be identical, such as admission tickets for events or facilities without assigned seating, a single digital ticket 13A may be associated with the NFT_IDs of multiple ticket NFTs 101.

[0056] The owner (and ownership history) of ticket NFT101 is recorded on blockchain 11. Therefore, the owner of ticket NFT101 does not need to be centrally managed, and the management and verification of ticket NFT101 owners is easy. Ownership of ticket NFT101 can be easily proven by the record on blockchain 11.

[0057] Proof of ownership of ticket NFT101 also serves as proof of ownership of digital ticket 13A. This is because digital ticket 13A is associated with ticket NFT101, whose owner is recorded in blockchain 11. Furthermore, if digital ticket 13A and ticket NFT101 are associated one-to-one, then if the owner of ticket NFT101 changes, the owner of digital ticket 13A will also change accordingly. In other words, in this embodiment, digital ticket 13A is associated with ticket NFT101 in such a way that a change in the owner of ticket NFT101 results in a change in the owner of ticket NFT101.

[0058] In this embodiment, the record of the owner of the ticket NFT 101 recorded on the blockchain 11 can be used as the record of the owner of the digital ticket 13A. Therefore, there is no need to centrally manage the owner of the digital ticket 13A itself (including the management of changes in ownership), making management easier. Furthermore, it is possible to trade the ticket NFT 101 (sell or transfer it to a third party) for the purpose of trading the digital ticket 13A.

[0059] In this embodiment, the blockchain 11, which is a computer network system, includes a smart contract 130. The smart contract 130 is software (computer program) implemented in a way that makes it executable on the blockchain, and it automatically executes a predetermined protocol.

[0060] Smart contract 130 has a contract address 140, which is a blockchain address. Smart contract 130 is stored at contract address 140. Smart contract 130 is executed by being invoked by another computer via the network 15. Other computers that invoke smart contract 130 are, for example, the ticket NFT management server 12 or user terminal 30 described later.

[0061] A user account 110 is provided for each user on the blockchain 11. In this embodiment, a user is, for example, the owner of a ticket NFT 101. As described later, a user can become the owner of a ticket NFT 101 to which a digital ticket 13A is associated by purchasing a paper ticket 1, and can then use the digital ticket 13A.

[0062] User account 110 has a blockchain address. In blockchain 11, non-fungible or fungible tokens owned by a user are recorded in association with the user account. The fact that a token is recorded in association with a user account (blockchain address) can also be said to mean that "the token is stored in the user account (blockchain address)." Furthermore, the fact that a token is stored in a certain account (blockchain address) can also be said to mean that "the account (blockchain address) owns the token." Note that a contract address is a type of blockchain address.

[0063] If user account 110 stores a ticket NFT 101 associated with digital ticket 13A, then the owner of that ticket NFT 101 is the user with user account 110. Therefore, the owner of the digital ticket 13A associated with ticket NFT 101 is the user with user account 110. As described later, the ticket NFT 101 is sent to user account 110 after the user purchases a paper ticket 1 and performs a predetermined operation.

[0064] Prior to the issuance of ticket 1, ticket NFT 101 (NFT_ID: A) is stored, for example, in the contract address 140 of smart contract 130 or in a blockchain address managed by smart contract 130, as shown in Figure 2. "Managed by smart contract 130" means that smart contract 130 can send the token stored in its blockchain address. The account managed by smart contract 130 may be an account for the ticket seller of digital ticket 13A.

[0065] The ticket NFT management system 10 according to this embodiment may include a ticket NFT management server 12. The ticket NFT management server 12, together with the smart contract 130 described above, may constitute the ticket NFT management system 10 of this embodiment. The ticket NFT management server 12 is connected to a network 15. The ticket NFT management server 12 provides the necessary functions to allow a user to obtain a ticket NFT 101 to which a digital ticket 13A is associated.

[0066] The ticket NFT management server 12 is comprised of a computer equipped with a processor 12A and memory 12B. The ticket NFT management server 12 may be comprised of a single computer or multiple computers connected via a network 15. Memory 12B is connected to the processor 12A. Memory 12B comprises, for example, primary storage and secondary storage. Primary storage is, for example, RAM. Secondary storage is, for example, a hard disk drive (HDD) or solid state drive (SSD). Memory 12B contains a computer program 12C executed by the processor 12A. The processor 12A reads and executes the computer program 12C stored in memory 12B. The computer program 12C contains program code to cause the computer to function as the ticket NFT management server 12.

[0067] Furthermore, a user who owns the ticket NFT 101 associated with the digital ticket 13A has a user terminal 30 (see Figure 1). The user terminal 30 can be used for purposes such as using the digital ticket 13A.

[0068] The user terminal 30 is, for example, a mobile device such as a smartphone or tablet. The user terminal 30 is connectable to the network 15. The user terminal 30 is composed of a computer equipped with a processor and memory. The memory is connected to the processor. The memory includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The memory contains computer programs executed by the processor. The processor reads and executes the computer programs stored in the memory. The computer program of the user terminal 30 has program code for processing such as obtaining the ticket NFT 101 and using the digital ticket 13A.

[0069] The computer program on the user terminal 30 is, for example, a wallet application program for displaying tokens stored in the user account 110 of the blockchain 11 on the user terminal 30, or an application program for using the digital ticket 13A. Such an application program provides functions that enable user operations for storing tokens and sending and receiving tokens.

[0070] The computer program of the user terminal 30 has program code for displaying NFTs or fungible tokens associated with user accounts 110 in blockchain 11 on the display of the user terminal 30. When displaying ticket NFT 101, the computer program of the user terminal 30 displays the digital ticket 13A (ticket data) associated with ticket NFT 101.

[0071] On the user's terminal 30, data 13A associated with NFT 101 owned by that user is displayed, but data associated with NFTs not owned by that user is not displayed. In database 13, to prevent the display of data on terminals other than the owner of NFT 101 associated with data 13A, database 13 is configured to allow access to data 13A from the owner of NFT 101 associated with data 13A, but to prevent access to data 13A from non-owners. Database 13 can determine the owner of NFT 101 associated with data 13A by referring to blockchain 11.

[0072] Figure 3 shows the procedure for issuing ticket 1 using system 500 (method of manufacturing ticket 1). A person wishing to purchase ticket 1 (user) accesses the ticket reservation web server 400 using terminal 30 and makes a reservation for the ticket they wish to purchase. This generates ticket data for ticket 1 (step S301: ticket reservation processing). The generated ticket data includes, for example, the venue, event name, date and time, seat number, and ticket number. When the ticket data is generated, an exchange number (first identification information) for ticket 1 is also generated, but here, as mentioned above, the ticket number also serves as the exchange number.

[0073] Ticket data is transmitted from the ticket reservation web server 400 to the ticket NFT management system 10 (specifically the ticket NFT management server 12) and the ticket issuance server 300 (step S302). The ticket data transmitted to the ticket NFT management system 10 is used for generating ticket NFTs 101, etc. The generation of ticket NFTs 101 will be described later. The ticket data transmitted to the ticket issuance server 300 is stored in the ticket issuance server 300. The ticket data stored in the ticket issuance server 300 is transmitted to the issuance device 200 in response to a data request using an exchange number.

[0074] The ticket reservation web server 400 outputs an exchange number (first identification information) for issuing ticket 1 (step S307). The exchange number may be displayed on the terminal 30 screen or sent to the user's email address. The exchange number may be output in the form of a machine-readable code, such as a two-dimensional code. The code may include information such as the user's (ticket purchaser's) ID.

[0075] A user who has obtained an exchange number visits a store such as a convenience store and has Ticket 1 issued (steps S309 to S312). To issue Ticket 1, the user first presents the exchange number or a code indicating the exchange number to the store staff. The store staff, for example, reads the code indicating the exchange number with a reader, causing the issuing device 200 to obtain the exchange number (first identification information) (step S309). The issuing device 200 may also obtain information such as the user ID.

[0076] The issuing device 200 processes the payment for ticket 1 corresponding to the exchange number (step S310). The payment processing may be performed using a settlement server (not shown). This completes the payment for ticket 1. After the payment is processed, the issuing device 200 acquires the ticket data (step S311). Note that the acquisition of the ticket data may be performed before the payment processing (step S310). To acquire the ticket data, the issuing device 200 uses the acquired exchange number (first identification information). More specifically, the issuing device 200 transmits the exchange number to the ticket issuing server 300 (step S311A). The ticket issuing server 300, having received the exchange number, transmits the ticket data corresponding to the exchange number to the issuing device 200 (step S311B). The ticket data includes the data of the 2D code 1A, as described later. The ticket data is the data for printing ticket 1.

[0077] The issuing device 200 prints ticket data for printing ticket 1 onto ticket paper and issues ticket 1 (step S312). The printed ticket 1 has a two-dimensional code 1A, as shown in Figure 1. The two-dimensional code 1A is used to obtain the ticket NFT 101, which is associated with the digital ticket 13A, an electronic version of ticket 1.

[0078] Now, the ticket NFT management system 10, having received ticket data from the ticket reservation web server 400, executes processing for the ticket NFT 101 (steps S303 to S305).

[0079] First, the ticket NFT management system 10 processes the received ticket data to associate it with an NFT (initial NFT) (step S303: generation of ticket NFT 101). The NFT to which the ticket data is associated is issued as an initial NFT on the blockchain 11 at or before step S403. The issuance of the initial NFT is achieved by executing an NFT issuance command prepared on the blockchain 11. When an NFT issuance command is executed on the blockchain, the computers constituting the blockchain accept the NFT issuance command and execute the process of issuing the NFT on the blockchain. The issued NFT is recorded on the blockchain. An NFT_ID is assigned to the NFT issued on the blockchain. The issuance of the initial NFT is performed, for example, by the ticket NFT management server 12 or the smart contract 130. The issued initial NFT is stored, for example, at the contract address 140 of the smart contract 130.

[0080] The ticket NFT management server 12 of the ticket NFT management system 10 obtains the NFT_ID (NFT_ID:A) of the initial NFT. The ticket NFT management server 12 associates the NFT_ID with the ticket data and stores it in the database 13. This means that the ticket data is embedded in the initial NFT. The NFT with the embedded ticket data is the ticket NFT 101. The ticket data stored in the database 13 becomes the digital ticket 13A.

[0081] As described above, the database 13 stores the digital ticket 13A in such a way that it is accessible to users recorded in the blockchain 11 as the owner of the ticket NFT 101 (an NFT with NFT_ID: A) associated with the digital ticket 13A. In this way, the digital ticket 13A is effectively integrated with the ticket NFT 101 and becomes an NFT. The association between the ticket NFT 101 and the digital ticket 13A may be achieved, for example, by having the ticket NFT 101 have a URI (Uniform Resource Identifier) ​​that points to the digital ticket 13A stored in the database 13.

[0082] The ticket NFT management server 12 generates code data that at least indicates second identification information for identifying the ticket NFT 101 (step S304). The code is, for example, a machine-readable two-dimensional code. The data for the two-dimensional code is data that indicates the pattern of the two-dimensional code, or data for generating that pattern. The data for generating the two-dimensional code pattern indicates, for example, a URL (Uniform Resource Locator), and the URL indicates, for example, the domain of the ticket NFT management server 12 and the second identification information. The generated two-dimensional code indicates the aforementioned URL.

[0083] The second identification information for identifying ticket NFT101 could be the NFT_ID:A of ticket NFT101, but here, "abcdefg", which is the ticket number (exchange number) of digital ticket 13A and ticket 1 associated with ticket NFT101, is used as the second identification information. In other words, the second identification information for identifying ticket NFT101 is the same as the ticket number (exchange number), which is the first identification number for identifying ticket 1.

[0084] The ticket NFT management server 12 associates the ticket number "abcdefg" with the NFT_ID:A of ticket NFT 101, which is the second identification information of ticket NFT 101, and stores this association in the management database 12D of the ticket NFT management server 12 (see Figure 5). By referring to the management database 12D, the ticket NFT management server 12 can obtain the NFT_ID from the ticket number, which is the second identification information, and can also obtain the ticket number from the NFT_ID.

[0085] The ticket NFT management server 12 sends the generated 2D code data and the ticket number (exchange number) of ticket 1 to which the 2D code should be attached to the ticket issuance server 300 (step S305). Once the above process is complete, the ticket NFT management system 10 sends a processing completion notification to the ticket reservation web server 400 as necessary (step S306).

[0086] The ticket issuing server 300, upon receiving the 2D code data and the ticket number (exchange number) of ticket 1 to which the 2D code should be attached, stores the received 2D code data in association with the ticket data that has the received ticket number (exchange number) (step S308). This allows the ticket issuing server 300 to add the 2D code data to the ticket data received from the ticket reservation web server 400 and store it.

[0087] The ticket data obtained by the issuing device 200 from the ticket issuing server 300 includes the two-dimensional code data added as described above. Therefore, the ticket 1 manufactured by printing the ticket data has a two-dimensional code 1A, as shown in Figure 1, and this two-dimensional code 1A has second identification information for identifying the ticket NFT 101. The two-dimensional code 1A is used by the user to obtain the ticket NFT 101.

[0088] Figure 4 shows another example of the procedure for issuing ticket 1 using system 500 (method of manufacturing ticket 1). In Figure 4, points not specifically explained are the same as in the example in Figure 3. A person wishing to purchase ticket 1 (user) performs a ticket reservation operation, similar to step S301. This generates ticket data for ticket 1 (step S401: ticket reservation process).

[0089] Ticket data, including the ticket number (exchange number), is transmitted from the ticket reservation web server 400 to the ticket NFT management system 10 (specifically, the ticket NFT management server 12) (step S402). The ticket data transmitted to the ticket NFT management system 10 is used in the processing of steps S403 and S404. Steps S403 and S404 are the same as steps S303 and S304 in Figure 3.

[0090] The ticket NFT management server 12 sends the two-dimensional code data generated in step S404 and the ticket number (exchange number) of ticket 1 to which the two-dimensional code should be attached to the ticket reservation web server 400 (step S405).

[0091] The ticket reservation web server 400 adds the received 2D code data to the generated ticket data and saves it. The ticket reservation web server 400 sends the ticket data including the 2D code data to the ticket issuance server 300 (step S406). The ticket reservation web server 400 outputs an exchange number (first identification information) for issuing ticket 1 (step S407). The ticket issuance server 300 saves the ticket data received from the ticket reservation web server 400 (step S408).

[0092] Users who have obtained an exchange number visit a store such as a convenience store and have Ticket 1 issued (steps S409 to S412). Steps S409 to S412 are the same as steps S309 to S312 in Figure 3.

[0093] Figure 5 shows the procedure for a user to obtain the ticket NFT 101 corresponding to ticket 1 using the issued ticket 1. When the user obtains the ticket NFT 101, the digital ticket 13A is displayed on the display 31 of the user terminal 30 (see Figure 6). Before the user obtains the ticket NFT 101, the ticket NFT 101 is stored in the contract address 140 of the smart contract 130, etc. (see Figure 2).

[0094] First, the user who obtains the paper ticket 1 has the user terminal 30 read the 2D code 1A attached to the ticket 1 (step S501). The user terminal 30 is equipped with a reader, such as a camera (not shown), that can read the machine-readable code 1A. Through this reading, the user terminal 30 obtains the URL indicated by the code 1A (the domain of the ticket NFT management server 12 and the ticket number (second identification information)).

[0095] The user terminal 30, having obtained the URL, performs network access according to that URL (step S502). That is, the user terminal 30 accesses the ticket NFT management server 12 according to the URL and sends the ticket number "abcdefg", which is the second identification information, to the management server 12. The access from the user terminal 30 to the ticket NFT management server 12 is a request for an operation to change the owner of the ticket NFT 101 corresponding to ticket 1 to the user (owner change request). In addition, when the user terminal 30 accesses the ticket NFT management server 12, the user's account on blockchain 11 (blockchain address) may also be sent from the user terminal 30 to the ticket NFT management server 12.

[0096] The ticket NFT management server 12 obtains the ticket number "abcdefg", which is the second identification information, from the user terminal 30 upon access from the user terminal 30. The ticket NFT management server 12 has a management database 12D as shown in Figure 5. The management server 12 refers to the management database 12D and converts the obtained ticket number "abcdefg" into NFT_ID:A, which represents ticket NFT 101 in the blockchain 11. Note that if the second identification information represented by code 1A is the NFT_ID itself, it is not necessary to refer to the management database 12D.

[0097] When the ticket NFT management server 12 obtains an NFT_ID:A to identify ticket NFT 101, it selects ticket NFT 101, indicated by NFT_ID:A, as the target for the ownership change operation and calls the smart contract 130 to perform the NFT ownership change operation (step S503). When making the call, the ticket NFT management server 12 provides the smart contract 130 with the NFT_ID:A of the target ticket NFT 101 and the user's blockchain account 110 (blockchain address). The smart contract 130 identifies the target ticket NFT 101 by its NFT_ID:A. The smart contract 130 also identifies the user who is the new owner of ticket NFT 101 by the user's blockchain account 110.

[0098] The invoked smart contract 130 performs an operation to change the owner of the identified target ticket NFT 101 to the identified user (step S504). This operation is performed by smart contract 130 executing a command in blockchain 11, which is sent from ticket NFT 101 and smart contract 130's contract address 140 to the user's blockchain address 110. As a result, the user comes to own ticket NFT 101 corresponding to ticket 1. The change in ownership of ticket NFT 101 to the user is recorded in blockchain 11. Smart contract 130 may also notify the ticket NFT management server 12 of the completion of the ownership change.

[0099] As a result of the ownership change request using the reading of code 1A as described above, the user terminal 30 of the user who has become the owner of ticket NFT 101 will display the digital ticket 13A associated with that ticket NFT 101, as shown in Figure 6. As shown in Figure 6, the display 31 of the user terminal 30 will display a ticket NFT display screen 33 showing the digital ticket 13A associated with ticket NFT 101. The user terminal 30 has an application program installed for displaying the data 13A associated with the NFT 101 owned by the user. The display of ticket NFT 101 and the digital ticket 13A associated with ticket NFT 101 is performed by this application program. The transmission of the aforementioned ownership change request may also be performed by this application program.

[0100] As mentioned above, the digital ticket 13A is stored in the database 13. The ticket NFT management server 12 and the database 13 execute a process to display the digital ticket 13A on the terminal 30 of the user who has become the owner of the ticket NFT 101. In this way, by obtaining the ticket NFT 101, the user can use it to display the digital ticket 13A associated with the ticket NFT 101.

[0101] <2.2 Second Embodiment: Content Publishing System>

[0102] Figures 7 to 13 show a second embodiment. In the second embodiment, the product is printed content 1. Except for the fact that the product is a ticket or content, the second embodiment is similar in many respects to the first embodiment. In the second embodiment, elements that are the same as or functionally the same as those in the first embodiment are denoted by the same reference numerals.

[0103] Figure 7 shows an example of the system 500 according to the second embodiment. The system 500 according to the second embodiment is for providing content printing services and is used for issuing printed content 1, etc. The system 500 according to the second embodiment also handles digital content 13A displayed on the user terminal 30.

[0104] Printed content 1 is composed of, for example, content data printed on content printing paper. The content data includes, for example, image data. The material of the image data is not particularly limited, but could include celebrities, singers, athletes, other famous people, characters from comics, games, and animations, game items, vehicles, machines, tools, animals, plants, etc. Content 1 is purchased, for example, by fans of celebrities, etc.

[0105] Content data has a product number. The product number may be a number that is common to multiple Content 1 of the same type, but here it will be a number unique to each individual Content 1. Here, as an example, Content 1 shown in Figure 7 is assigned the product number (first identification information) "aaaaa". Note that content data may have a first product number that is common to multiple Content 1 of the same type, and a second product number unique to each individual Content 1.

[0106] Content 1 includes the aforementioned content data, along with a machine-readable code 1A printed on it. Code 1A is, for example, a two-dimensional code. Code 1A will be described later. It constitutes the content data.

[0107] Digital content 13A is an electronic version of the content data and other data included in content 1. Digital content 13A includes, for example, image data identical to or related to content 1, and data related to product numbers, as content data. Digital content 13A is stored in database 13.

[0108] A user who purchases Content 1 can collect and enjoy the printed Content 1. In addition to the printed Content 1, the user can also enjoy displaying Digital Content 13A, which has the same or related image data, on the terminal 30. Moreover, since the user obtains not only digital information in the form of Digital Content 13A, but also a tangible object in the form of Content 1 printed on paper, the user has a strong sense of purchase satisfaction, making it a desirable system.

[0109] The system 500 according to the first embodiment includes an issuing device 200 and a content issuing server 300. The issuing device 200 is installed, for example, in a retail store. The issuing device 200 is configured to print content data onto printing paper and issue the printed content 1. The issuing device 200 is, for example, a multifunction printer installed in the store that provides content printing services, etc. The multifunction printer is used to provide content printing services as well as other printing services, copying services, and facsimile services. The multifunction printer can generally be operated directly by customers, but it may also be operated by store staff.

[0110] When the issuing device 200 receives an operation from an operator such as a customer (user), it obtains the necessary content data from the content issuing server 300 and issues content 1 by printing that content data. The issuing device 200 is configured to accept input of a product number. Input of the product number is performed, for example, by key operation or by reading a code indicating the product number with a reader on the multifunction printer.

[0111] The issuing device 200 is configured to accept payment requests for content 1 and perform payment processing prior to issuing content 1. Content 1 is issued after the payment processing is completed. Users who wish to purchase content 1 can easily obtain it by paying for it at stores such as convenience stores. In addition, by paying for content 1 at a store, users can also easily obtain content NFT 101.

[0112] The content publishing server 300 is connected to the publishing device 200 via the network 15. The content publishing server 300 is an external device installed separately from the publishing device 200 so that multiple publishing devices 200 can be connected to it. The content publishing server 300 holds content data for content 1 published by the publishing device 200 and is configured to transmit the content data to the publishing device 200 in response to a request from the publishing device 200.

[0113] The content publishing server 300 is comprised of a computer equipped with a processor and memory. The content publishing server 300 has a computer program. This computer program contains program code that causes the computer to function as the content publishing server 300.

[0114] The system 500 according to the second embodiment may include a content introduction web server 400 connected to the network 15. The content introduction web server provides a website 600 (see Figure 8) that can be viewed by those who wish to purchase content 1. This website 600 displays a list of content that can be issued by the issuing device 200, and the product number of each piece of content. The website 600 may also display the price of each piece of content. Furthermore, the content introduced on the website may include content with and without NFT 101.

[0115] The content introduction web server 400 is comprised of a computer equipped with a processor and memory. The content introduction web server has a computer program. This computer program contains program code that causes the computer to function as the content introduction web server 400.

[0116] The system 500 according to the second embodiment may include a content non-fungible token management system 10 (content NFT management system 10) connected to the network 15.

[0117] Figure 9 shows the content NFT management system 10. The content NFT management server 12, database 13, and smart contract 130 shown in Figure 9 have the same functions as the ticket NFT management server 12, database 13, and smart contract 130 shown in Figure 2.

[0118] In the second embodiment, the digital content 13A is associated with a non-fungible token 101. That is, the digital content 13A is NFT-enabled. The non-fungible token 101 associated with the digital content 13A is also referred to as "content NFT 101". Hereinafter, the NFT identifier (NFT_ID) of content NFT 101 will be represented by "A".

[0119] In the second embodiment, the association between digital content 13A and content NFT 101 is achieved, for example, by associating digital content 13A with the NFT_ID:A of the corresponding content NFT 101 and storing it in the database 13. If one digital content 13A is associated with only one corresponding content NFT 101's NFT_ID:A, a one-to-one correspondence between content NFT 101 and digital content 13A is achieved.

[0120] A single digital content 13A may be associated with the NFT_IDs of multiple content NFTs 101. If the data for each of the multiple digital content 13A can be identical, a single digital content 13A may be associated with the NFT_IDs of multiple content NFTs 101.

[0121] The owner (and ownership history) of Content NFT101 is recorded on Blockchain 11. Proof of ownership of Content NFT101 also serves as proof of ownership of Digital Content 13A. It is also possible to trade (sell or transfer to a third party) Content NFT101 for the purpose of trading Digital Content 13A.

[0122] If a content NFT 101 associated with digital content 13A is stored in a blockchain user account 110, the user with that user account is also the owner of the digital content 13A. As described later, the content NFT 101 is sent to the user account 110 after the user purchases printed content 1 and performs a predetermined operation.

[0123] The content NFT management system 10 according to this embodiment may include a content NFT management server 12. The content NFT management server 12, together with a smart contract 130, may constitute the content NFT management system 10 of this embodiment. The content NFT management server 12 provides the necessary functions to allow a user to obtain the content NFT 101 to which the digital content 13A is associated.

[0124] The content NFT management server 12 is comprised of a computer equipped with a processor 12A and memory 12B. The computer program 12C stored in memory 12B contains program code that causes the computer to function as the content NFT management server 12.

[0125] Furthermore, a user who owns the content NFT 101 associated with the digital content 13A has a user terminal 30 (see Figure 7). The user terminal 30 can be used to view the digital content 13A associated with the content NFT 101 owned by the user.

[0126] Figure 10 shows the procedure for issuing content 1 using system 500 (method of manufacturing content 1). A person who wishes to purchase content 1 (user) checks the product number listed on the content introduction website 600 using terminal 30. The user visits a store such as a convenience store and has content 1 issued (steps S1001 to S1003, S1010, S1011). To issue content 1, the user first inputs the product number into the issuing device 200. As a result, the issuing device 200 obtains the product number of content 1 (step S1001). If the display of the issuing device 200 allows the user to select the content they wish to purchase from a list of available content 1, the issuing device 200 may obtain the product number of content 1 by the user's selection operation of the content 1 they wish to purchase.

[0127] The issuing device 200 processes the payment for content 1 (step S1002). This completes the payment for content 1. After the payment is processed, the issuing device 200 acquires the content data (step S1011). Note that the acquisition of content data may be performed before the payment processing (step S1002). To acquire the content data, the issuing device 200 uses the acquired product number (first identification information). More specifically, the issuing device 200 transmits the product number to the content issuing server 300 (step S1003).

[0128] The content publishing server 300 transmits content data corresponding to the product number to the publishing device 200 (step S1009). The publishing device acquires the content data. The acquired content data includes the data for the 2D code 1A. The content data is the data for printing content 1.

[0129] The issuing device 200 prints content data for printing content 1 onto printing paper and issues content 1 (step S1011). The printed content 1 has a two-dimensional code 1A, as shown in Figure 7. The two-dimensional code 1A is used to obtain the content NFT 101, which is associated with the digital content 13A, which is an electronic version of content 1.

[0130] In order to include the data for the 2D code 1A from the content issuing server 300 to the issuing device 200, the content issuing server 300 sends the content data of the content 1 to be issued to the content NFT management system 10 (step S1004). The content issuing server 300 has content data for various content 1 that can be issued, associated with product numbers. The content data sent to the content NFT management system 10 can be identified from the content data of the content 1 to be issued sent from the issuing device 200 and the product number sent in step S1003.

[0131] The content NFT management system 10, upon receiving the content data, performs processing for the content NFT 101 (steps S1005 to S1007).

[0132] First, the content NFT management system 10 processes the received content data to associate it with an NFT (initial NFT) (step S1003: generation of content NFT 101). This means that the content data is embedded in the initial NFT. The NFT with the embedded content data is content NFT 101. Also, the content data stored in the database 13 becomes digital content 13A.

[0133] The content NFT management server 12 generates data for a two-dimensional code that shows at least second identification information for identifying the content NFT 101 (step S1004). The two-dimensional code shows a URL (Uniform Resource Locator), which shows, for example, the domain of the content NFT management server 12 and the second identification information.

[0134] The second identification information for identifying content NFT101 could be the NFT_ID:A of content NFT101, but here, "aaaaa," which is the product number of digital content 13A and content 1 associated with content NFT101, is used as the second identification information. In other words, the second identification information for identifying content NFT101 is the same as the product number, which is the first identification number for identifying content 1.

[0135] The content NFT management server 12 associates the product number "aaaaa" with the NFT_ID:A of the content NFT 101, and stores this association in the management database 12D of the content NFT management server 12 (see Figure 12). By referring to the management database 12D, the content NFT management server 12 can obtain the NFT_ID from the product number, which is the second identification information of the content NFT 101, and can also obtain the product number from the NFT_ID.

[0136] The content NFT management server 12 sends the generated two-dimensional code data and the product number of the content 1 to which the two-dimensional code should be attached to the content issuing server 300 (step S1007).

[0137] The content issuing server 300, upon receiving the two-dimensional code data and the product number of the content 1 to which the two-dimensional code should be attached, stores the received two-dimensional code data in association with the content data that has the received product number (step S1008). This allows the content issuing server 300 to add the two-dimensional code data to the content data and store it.

[0138] The content publishing server 300 transmits content data, including two-dimensional code data, to the publishing device 200 (step S1009), and the publishing device 200 receives the content data (step S1010). The content 1, manufactured by printing this content data, has a two-dimensional code 1A, as shown in Figure 7, and this two-dimensional code 1A has second identification information for identifying the content NFT 101. The two-dimensional code 1A is used by the user to obtain the content NFT 101.

[0139] Figure 11 shows another example of the procedure for publishing content 1 using system 500 (a method for manufacturing content 1). In Figure 11, the procedure is the same as in the example in Figure 10 unless otherwise specified.

[0140] In Figure 11, steps S1005 and S1006 are executed before the content publishing server 300 receives a content data request (step S1003) from the publishing device 200.

[0141] The content NFT management system 10 receives content data in advance from the content publishing server 300, and executes steps S1005 and S1006 to convert the content data into NFTs.

[0142] Then, when the content NFT management system 10 receives the product number (first identification information) of the content 1 to be issued from the issuing device 200 via the content issuing server 300, it sends 2D code data indicating the same product number (second identification information) as the product number (first identification number) to the content issuing server 300 (step S1007). Subsequent processing is carried out in the same manner as in Figure 10. In the case of the processing in Figure 11, since the content data has been converted into an NFT in advance, the issuance of content 1 can be carried out quickly.

[0143] Figure 12 shows the procedure for a user to obtain the content NFT 101 corresponding to content 1 using the issued content 1. Steps S1201, S1202, S1203, and S1204 shown in Figure 12 are substantially the same as steps S501, S502, S503, and S504 shown in Figure 5.

[0144] As shown in Figure 13, the user terminal 30 of the user who became the owner of content NFT 101 through an ownership change request using the reading of code 1A displays the digital content 13A associated with content NFT 101. As shown in Figure 13, the display 31 of the user terminal 30 displays a content NFT display screen 33 showing the digital content 13A associated with content NFT 101. In this way, by obtaining content NFT 101, the user can use it to display the digital content 13A associated with content NFT 101.

[0145] The present invention is not limited to the above embodiments, and various modifications are possible.

[0146] <3. Addendum>

[0147] This disclosure includes the following:

[0148] <3.1 Section 1>

[0149] The first identification information issuing device acquires, The issuing device obtains the data identified by the first identification information from an external device via the network. The aforementioned data is printed by the issuing device. Equipped with, The data identified by the first identification information includes machine-readable code data, the code indicating at least a second identification information for a non-fungible token management system recorded on a blockchain to identify a non-fungible token. method.

[0150] The data identified by the first identification information acquired by the issuing device includes data of a code that indicates at least a second identification information for identifying a non-fungible token. Therefore, by causing the issuing device to acquire the first identification information, a printed document with a code for identifying a non-fungible token is obtained.

[0151] <3.2 Section 2>

[0152] In the method described in paragraph 1 above, The aforementioned code is, When read by the device, The management system obtains the second identification information indicated by the code from the terminal. The management system sends the non-fungible token identified by the second identification information to a blockchain account used by the terminal that read the code. It is preferable to use it for that purpose.

[0153] <3.3 Section 3>

[0154] An issuing device configured to perform payment processing and accept payment for the service obtains data for printing from an external device via a network, The aforementioned data is printed by the issuing device. Equipped with, The data identified by the first identification information includes machine-readable code data, the code indicating at least a second identification information for a non-fungible token management system recorded on a blockchain to identify a non-fungible token. method.

[0155] By having an issuing device that accepts payments produce printed materials with codes to identify non-fungible tokens, it becomes easier to obtain printed materials with codes to identify non-fungible tokens.

[0156] <3.3 Section 3>

[0157] A method performed by a device that transmits data for printing a machine-readable code to an issuing device that prints the code, The aforementioned code indicates at least a second identification information for identifying nonfungible tokens in a management system for nonfungible tokens recorded on the blockchain, The device includes obtaining data for printing the code from the management system. method.

[0158] The device that transmits data for printing the code to the issuing device can transmit data for printing a code indicating the second identification information for identifying the non-fungible token to the issuing device by obtaining second identification information for identifying the non-fungible token from the non-fungible token management system.

[0159] The data for printing the code preferably includes image data of the code, or data for generating the image data of the code. The data for generating the image data of the code includes the second identification information. The data for generating the image data of the code preferably includes a URL for accessing the management system.

[0160] <3.4 Section 4>

[0161] A system or apparatus configured to perform the method described in any one of the preceding paragraphs 1 to 3. [Explanation of Symbols]

[0162] 1: Tickets; Content 1A: 2D code 10: Ticket Non-Fungible Token Management System; Content Non-Fungible Token Management System 11: Blockchain 12: Ticket NFT management server; Content NFT management server 12A: Processor 12B: Memory 12C: Computer Programs 12D: Management Database 13: Database 13A: Digital tickets; digital content 15: Network 30: Terminal 31: Display 33: Ticket NFT display screen; Content NFT display screen 101: Non-fungible tokens 110: User Account 110: Blockchain address 130: Smart Contracts 140: Contract address 200: Issuing device 300: Ticket issuance server; Content issuance server 400: Ticket reservation web server; Content introduction web server 500: System 600: Content Introduction Website

Claims

1. A printing device for printing a product acquires first identification information for identifying a product manufactured by printing. The issuing device obtains data for printing the product identified by the first identification information from an external device via a network using the first identification information. The issuing device prints the data for printing. Equipped with, The data for printing the product identified by the first identification information includes machine-readable code data, the code indicating at least a second identification information for a non-fungible token management system recorded on a blockchain to identify a product non-fungible token to which data related to the product is associated. The aforementioned code is, When read by the device, The management system obtains the second identification information indicated by the code from the terminal. The management system sends the product nonfungible token identified by the second identification information to the blockchain account used by the terminal that read the code. Used for A method of manufacturing products produced by printing.

2. The external device further includes obtaining the second identification information indicated by the code from the management system, or from the management system via a device that has obtained the second identification information from the management system. A method for manufacturing the product described in claim 1.

3. The aforementioned product is a printed ticket, The data related to the aforementioned product is ticket data containing the information included in the ticket, The aforementioned product nonfungible token is a ticket nonfungible token to which the aforementioned ticket data is associated. A method for manufacturing the product described in claim 1.

4. The aforementioned product is printed content, The data related to the aforementioned product is content data having information contained in the printed content, The aforementioned product nonfungible token is a content nonfungible token to which the aforementioned content data is associated. A method for manufacturing the product described in claim 1.

5. The aforementioned issuing device is a device installed inside a retail store. A method for manufacturing the product described in claim 1.

6. The issuing device is configured to process payment for the goods and print the goods after the payment has been processed. A method for manufacturing the product described in claim 1.

7. The website on which the aforementioned product is listed further includes displaying the first identification information. A method for manufacturing the product described in claim 1.

8. The second identification information is associated with the first identification information in the management system, or is the same information as the first identification information. A method for manufacturing the product described in claim 1.

9. Issuing device and An external device connected to the issuing device via a network, A management system for non-fungible tokens recorded on the blockchain, Equipped with, The issuing device is configured to acquire first identification information for identifying a product, acquire data for printing the product identified by the first identification information from the external device, and execute a process to print the data for printing. The data for printing the aforementioned product includes machine-readable code data, The code is configured to indicate at least a second identification information for identifying a non-fungible token associated with the product in a management system for non-fungible tokens recorded on the blockchain, The management system is configured to, upon obtaining the second identification information from the terminal that read the code, send the non-fungible token identified by the second identification information to the blockchain account used by the terminal that read the code. system.

Images