WO2023286773A1 - Procédé et système de fabrication pour produit fabriqué par impression - Google Patents

Procédé et système de fabrication pour produit fabriqué par impression Download PDF

Info

Publication number
WO2023286773A1
WO2023286773A1 PCT/JP2022/027436 JP2022027436W WO2023286773A1 WO 2023286773 A1 WO2023286773 A1 WO 2023286773A1 JP 2022027436 W JP2022027436 W JP 2022027436W WO 2023286773 A1 WO2023286773 A1 WO 2023286773A1
Authority
WO
WIPO (PCT)
Prior art keywords
ticket
data
identification information
product
content
Prior art date
Application number
PCT/JP2022/027436
Other languages
English (en)
Japanese (ja)
Inventor
昌浩 河上
幸雄 春名
仁 竹内
Original Assignee
Ｘクリエーション株式会社
ｂａｃｏｏｒ ｄＡｐｐｓ株式会社
株式会社Ａｉ商事
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ｘクリエーション株式会社, ｂａｃｏｏｒ ｄＡｐｐｓ株式会社, 株式会社Ａｉ商事 filed Critical Ｘクリエーション株式会社
Priority to JP2023534817A priority Critical patent/JPWO2023286773A1/ja
Publication of WO2023286773A1 publication Critical patent/WO2023286773A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B1/00—Machines for printing and issuing tickets

Definitions

  • 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 all the descriptions described in the Japanese Application.
  • Patent Document 1 discloses a ticket issuing system installed in a convenience store or the like.
  • the ticket issuing system of Patent Literature 1 includes a management device and a ticket issuing device that issues a ticket based on an instruction from the management device.
  • the ticket issuing device functions as a printer and prints ticket information on ticket paper.
  • Patent Document 2 discloses a content providing system for a content print service.
  • the content providing system of Patent Literature 2 includes a terminal and a content providing server.
  • the terminal and the content providing server are connected via a network.
  • a terminal is used by a user to purchase content provided by the content providing system.
  • a terminal is, for example, a multi-function machine provided in a store such as a convenience store.
  • the MFP has a function as a printer.
  • a multifunction device prints content such as photographs purchased by a user by operating the multifunction device.
  • ticket data or images such as photographs are sometimes treated as digital information instead of being printed on tangible media such as paper.
  • a digital ticket can be displayed on a user terminal such as a smart phone. If a digital ticket can be handled on a user terminal such as a smart phone, it will be very convenient for the user. Moreover, if an image can be displayed on a user terminal such as a smart phone, the enjoyment of the user will increase.
  • NFTs Non-Fungible Tokens
  • NFT is a type of token whose owner is recorded on the blockchain.
  • Tokens in blockchain include non-fungible tokens and fungible tokens.
  • Fungible Tokens may have currency properties, such as being interchangeable with fiat currency.
  • NFTs are non-fungible tokens. NFTs are recorded on a blockchain whose owner is a distributed ledger computer system. Using this, NFTs are used to trade digital data such as game items or digital art.
  • fungible tokens (crypto assets) on the blockchain are required to obtain NFTs.
  • a fungible token (cryptographic asset) in a blockchain is, for example, Bitcoin or Ether.
  • the present inventors have developed products that are manufactured by printing on a tangible medium such as paper, such as the ticket of Patent Document 1 or the photograph of Patent Document 2. A novel idea of using the issuing device was obtained.
  • the issuing device here is, for example, the ticket issuing device of Patent Document 1 or the multi-function device for the content print service of Patent Document 2.
  • Both the ticket of Patent Document 1 and the photograph of Patent Document 2 are types of products issued by printing. Contents such as tickets or photographs printed on a tangible medium such as paper can be easily obtained at stores such as convenience stores. A technology or a related technology that makes it possible to obtain NFTs using such easily available products is desired.
  • a certain aspect of the present disclosure is a method of manufacturing a product.
  • first identification information for identifying a product manufactured by printing is acquired by an issuing device for printing the product, and printing of the product identified by the first identification information is performed.
  • data from an external device via a network using the first identification information, and the issuing device prints the data for printing, wherein the first
  • the data for printing of the product identified by the identification information includes data of a machine-readable code, the code being recorded on a blockchain, the management system of non-fungible tokens is used to print the product.
  • the code when read by a terminal, transmits the second identification information indicated by the code to the management system; is obtained from the terminal, and the management system is used to transmit the commodity non-fungible token identified by the second identification information to a blockchain account utilized in the terminal that read the code.
  • FIG. 1 is a configuration diagram of a system according to the first embodiment.
  • FIG. 2 is a configuration diagram of the ticket NFT management system.
  • FIG. 3 is a flowchart of a ticket manufacturing method.
  • FIG. 4 is a flow chart of the ticket manufacturing method.
  • FIG. 5 is a diagram showing a procedure for obtaining a ticket NFT.
  • FIG. 6 is a diagram showing a digital ticket and a ticket NFT.
  • FIG. 7 is a configuration diagram of a system according to the second embodiment.
  • FIG. 8 is a diagram showing a screen example of the content introduction website.
  • FIG. 9 is a configuration diagram of the content NFT management system.
  • FIG. 10 is a flow chart of a content production method.
  • FIG. 11 is a flow chart of a content production method.
  • FIG. 12 is a diagram showing a procedure for obtaining a content NFT.
  • FIG. 13 is a diagram showing digital content and content NFT.
  • first identification information for identifying a product to be manufactured by printing is acquired by an issuing device for printing the product, and the product is identified by the first identification information.
  • the issuing device uses the first identification information to acquire data for printing the product to be printed from an external device via a network, and the issuing device prints the data for printing. , be prepared.
  • the product manufacturing process may include processes other than printing.
  • a product manufactured by printing may be a product manufactured by a process including at least printing.
  • the part obtained by printing may be part of the component of the product.
  • the data for printing the product identified by the first identification information may include machine-readable code data.
  • the code indicates at least second identification information for a non-fungible token management system recorded in a blockchain to identify a product non-fungible token associated with the product-related data. can be done.
  • the management system acquires the second identification information indicated by the code from the terminal, and the management system reads the non-fungible product identified by the second identification information. It can be used to send tokens to a blockchain account used in the terminal that read the code.
  • the blockchain account used in the terminal that read the code is, for example, the blockchain account of the user who owns the terminal.
  • the external device acquires the second identification information indicated by the code from the management system or from the management system via the device that acquired the second identification information from the management system. Further, it is preferable to provide.
  • the product may be a printed ticket.
  • the product-related data may be ticket data comprising information contained in the ticket.
  • the product non-fungible token may be a ticket non-fungible token associated with the ticket data.
  • the product may be printed content.
  • the product-related data may be content data comprising information included in the printed content.
  • the product non-fungible token may be a content non-fungible token associated with the content data.
  • the issuing device is preferably installed in a retail store.
  • the issuing device is configured to process payment for the product and to print the product after payment is processed. is preferred.
  • the website on which the product is posted is, for example, a ticket reservation website or a content introduction website.
  • the second identification information is associated with the first identification information in the management system, or is the same as the first identification information Information is preferred.
  • the second identification information may be associated with the first identification information in the external device.
  • a system includes an issuing device, an external device connected to the issuing device via a network, and a management system for non-fungible tokens recorded in a blockchain, The device acquires first identification information for identifying a product, acquires data for printing the product identified by the first identification information from the external device, and prints the data for printing.
  • the data for printing the product includes data in a machine-readable code, the code being recorded on a blockchain in a non-fungible token management system
  • the management system is configured to indicate at least second identification information for identifying the non-fungible token associated with the product, and the management system acquires the second identification information from the terminal that has read the code, the It is configured to send the commodity non-fungible token identified by the second identification information to a blockchain account utilized in the terminal that read the code.
  • a system includes an issuing device and an external device connected to the issuing device via a network, and the issuing device acquires first identification information for identifying a product. , acquiring data for printing of the product identified by the first identification information from the external device, and executing a process of printing the data for printing;
  • the data includes data in a machine-readable code, the code for identifying a non-fungible token associated with the commodity in a blockchain-recorded non-fungible token management system.
  • the external device transmits the two identification information indicated by the code from the management system or via the device that acquired the two identification information from the management system Configured to retrieve from a management system.
  • FIG. 1 shows an example of a system 500 according to the first embodiment.
  • the product in the first embodiment is a printed ticket 1 .
  • Ticket 1 is a tangible object.
  • a system 500 according to the first embodiment is used to issue and use a ticket 1 .
  • the system 500 according to the first embodiment also handles the digital ticket 13A displayed on the user terminal 30.
  • FIG. 1 shows an example of a system 500 according to the first embodiment.
  • the product in the first embodiment is a printed ticket 1 .
  • Ticket 1 is a tangible object.
  • a system 500 according to the first embodiment is used to issue and use a ticket 1 .
  • the system 500 according to the first embodiment also handles the digital ticket 13A displayed on the user terminal 30.
  • FIG. 1 shows an example of a system 500 according to the first embodiment.
  • the product in the first embodiment is a printed ticket 1 .
  • Ticket 1 is a tangible object.
  • a system 500 according to the first embodiment is used to issue and use a ticket 1 .
  • a ticket 1 is, for example, a ticket for admission to an event, a ticket for admission to a facility, a ticket for a vehicle, a ticket for enjoying other services, a ticket in exchange for a product, a gift certificate, or a discount coupon.
  • Events are, for example, concerts, movies, plays, exhibitions, expositions, sporting events, and festivals.
  • Facilities are, for example, amusement parks, zoos, botanical gardens, art galleries, museums, movie theaters, shops, and tourist facilities.
  • Vehicles are, for example, planes, ships, trains, buses, and taxis.
  • ticket 1 is configured by printing ticket data on ticket paper.
  • the ticket data as shown in FIG. 1, includes, for example, venue, event name, date and time, seat, and ticket number.
  • a ticket number is a number unique to each ticket.
  • the ticket number is the same as the ticket exchange number (first identification information) described later.
  • the ticket shown in FIG. 1 is given "abcdefg" as a ticket number (exchange number; first identification information).
  • a machine-readable code 1A is attached to the ticket 1 by printing together with the ticket data described above.
  • Code 1A is, for example, a two-dimensional code. Code 1A will be described later. Code 1A also constitutes ticket data.
  • the digital ticket 13A is an electronic version of the ticket data and other data included in the ticket 1.
  • the digital ticket 13A includes, as ticket data, data relating to, for example, venue, event name, date and time, seat, and ticket number.
  • the digital ticket 13A is stored in a database 13, which will be described later.
  • a user who is a purchaser of ticket 1 may use ticket 1 or digital ticket 13A when entering an event.
  • the ability to use the digital ticket 13A eliminates the need for the user to bring the paper ticket 1 when entering an event or the like, improving user convenience.
  • the user since the user can obtain not only the digital information of the digital ticket 13A but also the tangible object of the paper ticket 1, the user has a high sense of purchase, which is preferable.
  • the system 500 includes an issuing device 200 and a ticket issuing server 300.
  • the issuing device 200 is installed, for example, in a retail store.
  • a retail store is, for example, a convenience store, a supermarket, or a department store.
  • the issuing device 200 is configured to issue a ticket 1 by printing ticket data on a ticket paper.
  • the issuing device 200 is installed, for example, at a checkout counter of a store and operated by store staff.
  • the issuing device 200 may be installed in the store so that customers can directly operate it.
  • the issuing device 200 Upon receiving an operation by an operator such as a store staff member or a customer (user), the issuing device 200 acquires necessary ticket data from the ticket issuing server 300 outside the store, and prints the ticket data to generate a ticket 1. to be issued.
  • the issuing device 200 is configured to receive an input of a ticket exchange number, which will be described later. Input of the exchange number is performed, for example, by operating a key or reading a code indicating the exchange number with a reader.
  • the issuing device 200 is configured to accept a payment operation for the price of the ticket 1 and execute payment processing for settlement of the price prior to the issuance of the ticket 1.
  • Ticket 1 is issued after the payment process is completed.
  • Payment is made, for example, by cash, credit card, electronic money, or direct debit from a bank account.
  • a person (user) who intends to purchase the ticket 1 can pay for the ticket 1 at a store such as a convenience store, so the ticket 1 can be easily obtained. Also, by paying for the ticket 1 at the store, a non-fungible token 101, which will be described later, can be obtained. Since the issuing device 200 can process payment, the issuing device 200 can also be regarded as the payment processing device 200 .
  • system 500 preferably includes a plurality of issuing devices 200. Each of the plurality of issuing devices 200 is installed in the store.
  • the ticket issuing server 300 is connected to the issuing device 200 via the network 15 such as the Internet.
  • the ticket issuing server 300 is an external device installed at a location separate from the issuing device 200 so that a plurality of issuing devices 200 can be connected.
  • the ticket issuing server 300 has ticket data for a ticket 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 .
  • the ticket issuing server 300 is composed of a computer equipped with a processor and memory.
  • the ticket issuing server 300 may be composed of one computer, or may be composed of a plurality of computers connected via the network 15 .
  • a memory is connected to the processor.
  • Memory includes, for example, a primary storage device and a secondary storage device.
  • a primary storage device is, for example, a RAM.
  • the secondary storage device is, for example, a hard disk drive (HDD) or solid state drive (SSD).
  • the memory contains computer programs that are executed by the processor.
  • the processor reads and executes computer programs stored in memory.
  • a computer program for the ticket issuing server 300 has program code for causing a computer to function as the ticket issuing server 300 .
  • the system 500 can include a ticket reservation web server 400 connected to the network 15.
  • the ticket reservation web server provides a web site that is browsed by ticket 1 purchasers. This website accepts a ticket 1 reservation operation by a person who wishes to purchase the ticket 1, and outputs the ticket 1 exchange number (first identification information). The ticket 1 exchange number is input to the issuing device 200 to issue the ticket 1 .
  • the ticket reservation web server 400 may be configured to receive a payment operation for the price of the ticket 1 and execute payment processing to settle the price. In this case, no payment is required at the store where the issuing device 200 is installed, or only the ticket issuing fee may be paid.
  • the ticket reservation web server 400 is composed of a computer with a processor and memory.
  • the ticket reservation web server 400 may be composed of one computer, or may be composed of a plurality of computers connected via the network 15 .
  • a memory is connected to the processor.
  • Memory includes, for example, a primary storage device and a secondary storage device.
  • a primary storage device is, for example, a RAM.
  • the secondary storage device is, for example, a hard disk drive (HDD) or solid state drive (SSD).
  • the memory contains computer programs that are executed by the processor.
  • the processor reads and executes computer programs stored in memory.
  • a computer program for the ticket reservation web server 400 has program code for causing a computer to function as the ticket reservation web server 400 .
  • the system 500 can include a ticket non-fungible token management system 10 (ticket NFT management system 10) connected to the network 15.
  • ticket NFT management system 10 ticket non-fungible token management system 10
  • FIG. 2 shows the ticket NFT management system 10.
  • the ticket NFT management system 10 uses the blockchain 11 to manage the digital ticket 13A and the non-fungible token 101 (ticket NFT 101) associated with the digital ticket 13A.
  • the ticket NFT management system 10 comprises a database 13 in which digital tickets 13A are stored.
  • the database 13 is composed of, for example, a file system connected to a network 15 such as the Internet.
  • the file system comprises one computer or multiple computers connected to network 15 .
  • the database 13 is configured by an IPFS (InterPlanetary File System), for example.
  • IPFS is an example of a P2P (Peer to Peer) distributed file system.
  • the digital ticket 13A stored in the database 13 is displayed on the terminal 30 of the user who owns the digital ticket 13A.
  • the user can display the digital ticket 13A on the terminal 30 to enter or participate in the event.
  • the blockchain 11 is used for managing the digital ticket 13A.
  • the blockchain 11 is configured by a P2P (Peer to Peer) computer network system in which a plurality of computers are interconnected.
  • P2P Peer to Peer
  • token transactions are possible between blockchain addresses, and token transaction records are recorded in the distributed ledger of the blockchain 11.
  • a blockchain address indicates, for example, a user account on the blockchain 11 .
  • the account 110 has a given blockchain address (user address).
  • a blockchain address is expressed, for example, as 0xZZZZZZZ. Note that each Z is independently any number or symbol, and the number of digits of Z is a predetermined number in the blockchain.
  • Tokens that can be traded on the blockchain 11 include fungible tokens (fungible tokens) and non-fungible tokens (non-fungible tokens: NFT).
  • fungible tokens fungible tokens
  • non-fungible tokens non-fungible tokens
  • a fungible token is, for example, Ether.
  • NFTs are non-fungible tokens.
  • an NFT has a unique identifier in the blockchain 11 to allow it to be distinguished from other NFTs. This identifier is hereinafter referred to as the NFT identifier.
  • the NFT identifier may also be denoted as "NFT_ID”.
  • the digital ticket 13A is associated with the non-fungible token 101. That is, the digital ticket 13A is converted to NFT.
  • the non-fungible token 101 associated with the digital ticket 13A is also called a "ticket NFT 101" ("NFT ticket/NFTticket” is a registered trademark in Japan).
  • NFT_ID NFT identifier
  • the correspondence between the digital ticket 13A and the ticket NFT101 is realized, for example, by associating the digital ticket 13A with NFT_ID: A of the corresponding ticket NFT101 and storing it in the database 13.
  • NFT_ID: A of the corresponding ticket NFT101 When one digital ticket 13A is associated only with NFT_ID:A of one corresponding ticket NFT101, a one-to-one correspondence between the ticket NFT101 and the digital ticket 13A is realized.
  • the ticket NFT 101 itself does not need to have the ticket data included in the digital ticket 13A, so the amount of data of the ticket NFT 101 recorded on the blockchain 11 can be reduced. As a result, the cost of using the blockchain 11 can be reduced.
  • a single digital ticket 13A may be associated with the NFT_IDs of multiple ticket NFTs 101.
  • the data of each of the plurality of digital tickets 13A may be the same, such as admission tickets for events or facilities without seat assignment, even if one digital ticket 13A is associated with the NFT_ID of a plurality of ticket NFTs 101 good.
  • the owner (and owner history) of the ticket NFT 101 is recorded in the blockchain 11. Therefore, the owner of the ticket NFT101 does not need centralized management, and management and confirmation of the owner of the ticket NFT101 are easy. The owner of the ticket NFT101 can be easily proved by the record of the blockchain 11.
  • Proof of being the owner of ticket NFT101 is also proof of being the owner of digital ticket 13A.
  • the digital ticket 13A is associated with the ticket NFT 101 whose owner is recorded in the blockchain 11. Further, when the digital ticket 13A and the ticket NFT101 are associated one-to-one, when the owner of the ticket NFT101 is changed, the owner of the digital ticket 13A is also changed accordingly. That is, in the embodiment, the digital ticket 13A is associated with the ticket NFT101 so that the owner change occurs when the owner of the ticket NFT101 changes.
  • the record of the owner of the ticket NFT 101 recorded in the blockchain 11 can be used as the record of the owner of the digital ticket 13A, management of the owner of the digital ticket 13A itself (change of owner (including management of It is also possible to trade (sell/transfer to a third party) the ticket NFT 101 for trading the digital ticket 13A.
  • the blockchain 11 which is a computer network system, comprises a smart contract 130.
  • the smart contract 130 is software (computer program) implemented executable in the blockchain, and automatically executes a predetermined protocol.
  • the 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 called by another computer via network 15 . Another computer that calls the smart contract 130 is, for example, the ticket NFT management server 12 or the user terminal 30, which will be described later.
  • a user account 110 is provided for each user in the blockchain 11.
  • the user is, for example, the owner of ticket NFT101.
  • the user by purchasing the paper ticket 1, the user can become the owner of the ticket NFT 101 associated with the digital ticket 13A and use the digital ticket 13A.
  • the user account 110 has a blockchain address.
  • non-fungible tokens or fungible tokens owned by users are recorded in association with user accounts.
  • the fact that the token is recorded in association with the user account (blockchain address) can also be said to be “the token is stored in the user account (blockchain address).”
  • the fact that a token is stored in a certain account (blockchain address) can also be said to be "the account (blockchain address) owns the token”.
  • a contract address is a type of blockchain address.
  • the owner of the ticket NFT 101 is the user who has the user account 110. Therefore, the owner of digital ticket 13A associated with ticket NFT 101 is the user with user account 110 . As will be described later, the ticket NFT 101 is sent to the user account 110 by performing a predetermined operation after the user purchases the paper ticket 1 .
  • the ticket NFT101 (NFT_ID: A) is stored in the contract address 140 of the smart contract 130 or the blockchain address managed by the smart contract 130, for example, as shown in FIG. ing.
  • “Managed by smart contract 130” means at least that smart contract 130 can send tokens stored at its blockchain address.
  • the accounts managed by smart contract 130 may be accounts for ticket sellers of digital tickets 13A.
  • the ticket NFT management system 10 may include a ticket NFT management server 12.
  • the ticket NFT management server 12 can constitute the ticket NFT management system 10 of the embodiment together with the smart contract 130 described above.
  • the ticket NFT management server 12 is connected to the network 15 .
  • the ticket NFT management server 12 provides functions necessary for allowing the user to obtain the ticket NFT 101 associated with the digital ticket 13A.
  • the ticket NFT management server 12 is composed of a computer with a processor 12A and memory 12B.
  • the ticket NFT management server 12 may be configured by one computer, or may be configured by multiple computers connected via the network 15 .
  • Memory 12B is connected to processor 12A.
  • the memory 12B includes, for example, a primary storage device and a secondary storage device.
  • a primary storage device is, for example, a RAM.
  • the secondary storage device is, for example, a hard disk drive (HDD) or solid state drive (SSD).
  • Memory 12B contains a computer program 12C that is executed by processor 12A.
  • Processor 12A reads and executes computer program 12C stored in memory 12B.
  • the computer program 12C has program code for causing the computer to function as the ticket NFT management server 12 .
  • the user who is the owner of the ticket NFT101 associated with the digital ticket 13A has a user terminal 30 (see FIG. 1).
  • the user terminal 30 can be used, for example, to use the digital ticket 13A.
  • the user terminal 30 is, for example, a mobile device such as a smartphone or tablet.
  • a user terminal 30 is connectable to the network 15 .
  • the user terminal 30 is configured by a computer having a processor and memory.
  • a memory is connected to the processor.
  • Memory includes, for example, a primary storage device and a secondary storage device.
  • a primary storage device is, for example, a RAM.
  • the secondary storage device is, for example, a hard disk drive (HDD) or solid state drive (SSD).
  • the memory contains computer programs that are executed by the processor.
  • the processor reads and executes computer programs stored in 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.
  • the computer program of the user terminal 30 is, for example, a wallet application program for displaying the token 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 application programs provide functions that allow user operations for storing tokens, sending and receiving tokens.
  • the computer program of the user terminal 30 has program code for displaying the NFT or fungible token associated with the user account 110 in the blockchain 11 on the display of the user terminal 30.
  • the computer program of the user terminal 30 displays the digital ticket 13A (ticket data) associated with the ticket NFT101.
  • the user's terminal 30 displays the data 13A associated with the NFT 101 owned by the user, but does not display the data associated with the NFT not owned by the user.
  • database 13 permits access to data 13A from the owner of NFT 101 associated with data 13A. However, access control is performed so that access to the data 13A from anyone other than the owner is not permitted.
  • the database 13 can grasp the owner of the NFT 101 associated with the data 13A by referring to the block chain 11.
  • FIG. 3 shows the procedure for issuing ticket 1 using the system 500 (method for manufacturing ticket 1).
  • a person (user) who wishes to purchase a ticket 1 accesses the ticket reservation Web server 400 using the terminal 30 and performs a reservation operation for the ticket he wishes to purchase.
  • ticket data for ticket 1 is generated (step S301: ticket reservation processing).
  • the generated ticket data includes, for example, the venue, event name, date and time, seat, and ticket number.
  • the exchange number first identification information
  • the ticket number also serves as the exchange number.
  • the ticket data is transmitted from the ticket reservation web server 400 to (the ticket NFT management server 12 of) the ticket NFT management system 10 and the ticket issuing server 300 (step S302).
  • the ticket data transmitted to the ticket NFT management system 10 is used for generation of the ticket NFT 101 and the like. Generation of the ticket NFT101 will be described later.
  • the ticket data transmitted to the ticket issuing server 300 is stored in the ticket issuing server 300 .
  • the ticket data stored in the ticket issuing server 300 is transmitted to the issuing device 200 in response to a data request using the exchange number.
  • the ticket reservation web server 400 outputs the exchange number (first identification information) for issuing ticket 1 (step S307).
  • the output of the exchange number may be displayed on the terminal 30, or may be sent to the user's e-mail 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 ID of the user (ticket purchaser).
  • the user who has obtained the exchange number visits a store such as a convenience store and has a ticket 1 issued (steps S309 to S312).
  • the user first presents the exchange number or a code indicating the exchange number to the store staff.
  • the store staff for example, causes the issuing device 200 to acquire the exchange number (first identification information) by reading the code indicating the exchange number with a reader (step S309).
  • the issuing device 200 may also acquire information such as a user ID.
  • the issuing device 200 processes payment for the ticket 1 corresponding to the exchange number (step S310). Payment processing may be performed using a settlement server (not shown). As a result, the payment for the ticket 1 is completed.
  • the issuing device 200 acquires the ticket data after the payment is processed (step S311). The acquisition of ticket data may be performed before the payment process (step S310).
  • the issuing device 200 uses the acquired exchange number (first identification information) to acquire the ticket data. More specifically, the issuing device 200 transmits the exchange number to the ticket issuing server 300 (step S311A).
  • the ticket issuing server 300 that has received the exchange number transmits ticket data corresponding to the exchange number to the issuing device 200 (step S311B).
  • the ticket data includes data of the two-dimensional code 1A, as will be described later.
  • the ticket data is data for printing the ticket 1 .
  • the issuing device 200 prints the ticket data for printing the ticket 1 on the ticket paper and issues the ticket 1 (step S312).
  • a printed ticket 1 has a two-dimensional code 1A, as shown in FIG.
  • the two-dimensional code 1A is used, for example, to obtain a ticket NFT 101 associated with a digital ticket 13A, which is an electronic version of the ticket 1.
  • the ticket NFT management system 10 Upon receiving the ticket data from the ticket reservation web server 400, the ticket NFT management system 10 executes processing for the ticket NFT 101 (steps S303 to S305).
  • processing is performed to associate the received ticket data with the NFT (initial NFT) (step S303: generate ticket NFT101).
  • the NFT with which the ticket data is associated is issued in the blockchain 11 as an initial NFT at or before step S403. Issuance of the initial NFT is achieved by executing a prepared NFT issuance command in the blockchain 11 .
  • the computer that constitutes the blockchain receives the NFT issuance command and executes the NFT issuance process in the blockchain. Issued NFTs are recorded on the blockchain.
  • NFT_ID is given to the NFT issued in the blockchain. Issuance of the initial NFT is performed by the ticket NFT management server 12 or the smart contract 130, for example.
  • the issued initial NFT is stored, for example, at contract address 140 of smart contract 130 .
  • the ticket NFT management server 12 of the ticket NFT management system 10 acquires the NFT_ID (NFT_ID: A) of the initial NFT.
  • the ticket NFT management server 12 associates the NFT_ID and the ticket data with each other and stores them in the database 13 .
  • the ticket data is incorporated into the initial NFT.
  • the NFT in which the ticket data is embedded is the ticket NFT101.
  • the ticket data stored in the database 13 becomes the digital ticket 13A.
  • the database 13 allows the digital ticket 13A to be referenced by the user recorded in the blockchain 11 as the owner of the ticket NFT 101 (NFT with NFT_ID: A) associated with the digital ticket 13A. are stored in the database 13 as shown in FIG. As a result, the digital ticket 13A is substantially integrated with the ticket NFT 101 and converted into an NFT.
  • the ticket NFT 101 and the digital ticket 13A may be associated with each other, for example, by having the ticket NFT 101 have a URI (Uniform Resource Identifier) indicating the digital ticket 13A stored in the database 13.
  • URI Uniform Resource Identifier
  • the ticket NFT management server 12 generates code data indicating at least the second identification information for identifying the ticket NFT 101 (step S304).
  • the code is, for example, a machine-readable two-dimensional code.
  • the two-dimensional code data is data representing a two-dimensional code pattern or data for generating the pattern.
  • the data for generating the pattern of the two-dimensional code 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.
  • the second identification information for identifying the ticket NFT101 may be the NFT_ID: A of the ticket NFT101, but here, the ticket number (exchange number) of the digital ticket 13A and the ticket 1 associated with the ticket NFT101 "abcdefg ” is used as the second identification information. That is, the second identification information for identifying the ticket NFT101 is the same as the ticket number (exchange number), which is the first identification number for identifying the ticket 1 .
  • the ticket NFT management server 12 associates the ticket number "abcdefg" with the NFT_ID: A so that the NFT_ID: A of the ticket NFT101 can be grasped from the ticket number "abcdefg", which is the second identification information of the ticket NFT101. It is saved in the management database 12D of the ticket NFT management server 12 (see FIG. 5). By referring to the management database 12D, the ticket NFT management server 12 can grasp the NFT_ID from the ticket number, which is the second identification information, and can also grasp the ticket number from the NFT_ID.
  • the ticket NFT management server 12 transmits the generated two-dimensional code data and the ticket number (exchange number) of ticket 1 to which the two-dimensional code should be attached to the ticket issuing server 300 (step S305).
  • the ticket NFT management system 10 transmits a processing completion notice to the ticket reservation web server 400 as necessary (step S306).
  • the ticket issuing server 300 which has received the two-dimensional code data and the ticket number (exchange number) of the ticket 1 to which the two-dimensional code is to be attached, has the received two-dimensional code data with the received ticket number (exchange number). It is saved in association with the ticket data (step S308). As a result, the ticket issuing server 300 can add the two-dimensional code data to the ticket data received from the ticket reservation web server 400 and store the data.
  • the ticket data that the issuing device 200 acquires from the ticket issuing server 300 has 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 FIG. 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 acquire the ticket NFT101.
  • FIG. 4 shows another example of the ticket 1 issuing procedure (ticket 1 manufacturing method) using the system 500 .
  • tickets that are not particularly described are the same as in the example of FIG.
  • a person (user) who wishes to purchase a ticket 1 performs a ticket reservation operation in the same manner as in step S301.
  • ticket data for ticket 1 is generated (step S401: ticket reservation processing).
  • the ticket data including the ticket number (exchange number) is transmitted from the ticket reservation web server 400 to (the ticket NFT management server 12 of) the ticket NFT management system 10 (step S402).
  • the ticket data transmitted to the ticket NFT management system 10 is used for the processing of steps S403 and S404. Steps S403 and S404 are the same as steps S303 and S304 in FIG.
  • the ticket NFT management server 12 transmits 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).
  • the ticket reservation web server 400 adds the received two-dimensional code data to the generated ticket data and saves it.
  • the ticket reservation web server 400 transmits the ticket data including the two-dimensional code data to the ticket issuing server 300 (step S406).
  • the ticket reservation web server 400 outputs the exchange number (first identification information) to issue ticket 1 (step S407).
  • the ticket issuing server 300 stores the ticket data received from the ticket reservation web server 400 (step S408).
  • Steps S409 to S412 are the same as steps S309 to S312 in FIG.
  • FIG. 5 shows the procedure for the user to obtain the ticket NFT 101 corresponding to ticket 1 using issued ticket 1.
  • the digital ticket 13A is displayed on the display 31 of the user terminal 30 (see FIG. 6).
  • the ticket NFT 101 is stored in the contract address 140 or the like of the smart contract 130 (see FIG. 2).
  • the user who obtained the paper ticket 1 causes the user terminal 30 to read the two-dimensional code 1A attached to the ticket 1 (step S501).
  • the user terminal 30 includes a reader such as a camera (not shown) for reading the machine-readable code 1A. By this reading, the user terminal 30 acquires the URL indicated by the code 1A (the domain of the ticket NFT management server 12 and the ticket number (second identification information)).
  • the user terminal 30 that has acquired the URL executes network access according to the URL (step S502). That is, the user terminal 30 accesses the ticket NFT management server 12 according to the URL and transmits the ticket number “abcdefg”, which is the second identification information, to the management server 12 . Access from the user terminal 30 to the ticket NFT management server 12 is an operation request (owner change request) to change the owner of the ticket NFT 101 corresponding to the ticket 1 to the user.
  • owner change request owner of the ticket NFT 101 corresponding to the ticket 1 to the user.
  • the user's account (blockchain address) in the blockchain 11 may be transmitted from the user terminal 30 to the ticket NFT management server 12 .
  • the ticket NFT management server 12 acquires the ticket number "abcdefg", which is the second identification information, from the user terminal 30 through access from the user terminal 30.
  • the ticket NFT management server 12 has a management database 12D shown in FIG.
  • the management server 12 refers to the management database 12 ⁇ /b>D and converts the acquired ticket number “abcdefg” into NFT_ID:A indicating the ticket NFT 101 in the block chain 11 . Note that if the second identification information indicated by the code 1A is the NFT_ID itself, it is not necessary to refer to the management database 12D.
  • the ticket NFT management server 12 acquires the NFT_ID: A for identifying the ticket NFT101
  • the ticket NFT101 indicated by the NFT_ID: A is the target of the owner change operation
  • the smart contract is used for the NFT owner change operation. 130 (step S503).
  • the ticket NFT management server 12 gives the smart contract 130 the NFT_ID: A of the ticket NFT 101 to be operated and the user's blockchain account 110 (blockchain address).
  • the smart contract 130 identifies the ticket NFT101 to be operated by NFT_ID: A of the ticket NFT101.
  • Smart contract 130 also identifies the user who is the new owner of ticket NFT 101 by the user's blockchain account 110 .
  • the called smart contract 130 executes an operation to change the owner of the identified ticket NFT 101 to be operated to the identified user (step S504).
  • This operation is performed by the smart contract 130 executing a command to send the ticket NFT 101 from the contract address 140 of the smart contract 130 to the user's blockchain address 110 in the blockchain 11 .
  • the user owns the ticket NFT101 corresponding to the ticket 1.
  • the change of the owner of the ticket NFT101 to the user is recorded in the blockchain 11.
  • the smart contract 130 may notify the ticket NFT management server 12 of the owner change completion notification.
  • the digital ticket associated with the ticket NFT101 is displayed on the user terminal 30 of the user who has become the owner of the ticket NFT101 by the owner change request using the reading of the code 1A as described above.
  • 13A is displayed.
  • the display 31 of the user terminal 30 shown in FIG. 6 displays a ticket NFT display screen 33 showing the digital ticket 13A associated with the ticket NFT101.
  • An application program is installed in the user terminal 30 to display the data 13A associated with the NFT 101 owned by the user.
  • This application program displays the ticket NFT101 and the digital ticket 13A associated with the ticket NFT101. Sending of the aforementioned change of ownership request may be performed by this application program.
  • the digital ticket 13A is stored in the database 13.
  • the ticket NFT management server 12 and the database 13 execute processing for displaying the digital ticket 13A on the terminal 30 of the user who has become the owner of the ticket NFT101. In this way, by obtaining the ticket NFT101, the user can use it, such as displaying the digital ticket 13A associated with the ticket NFT101.
  • the product is printed content 1 . Except for whether the product is a ticket or a content, the second embodiment has many points in common with the first embodiment. In the second embodiment, points that are not particularly described are the same as in the first embodiment. In the second embodiment, elements that are the same as or functionally common to the first embodiment are assigned the same reference numerals as in the first embodiment.
  • FIG. 7 shows an example of a system 500 according to the second embodiment.
  • a system 500 according to the second embodiment is for providing a content print service, and is used for issuing content 1, which is printed matter.
  • the system 500 according to the second embodiment also handles digital content 13A displayed on the user terminal 30.
  • the printed content 1 is configured by, for example, printing content data on printing paper for content.
  • Content data includes, for example, image data.
  • Materials of image data are, but not limited to, celebrities, singers, athletes, other celebrities, characters in cartoons, games, animation, etc., game items, vehicles, machines, instruments, animals, plants, and the like.
  • Content 1 is purchased, for example, by a fan such as an entertainer.
  • Content data has a product number.
  • the product number may be a number assigned in common to a plurality of contents 1 of the same type, but here, it is assumed to be a unique number for each individual content 1 .
  • the content 1 shown in FIG. 7 is given "aaaaa" as the product number (first identification information).
  • the content data may have a first product number assigned in common to a plurality of contents 1 of the same type and a second product number unique to each individual content 1 .
  • a machine-readable code 1A is attached to content 1 by printing together with the content data described above.
  • Code 1A is, for example, a two-dimensional code. Code 1A will be described later. configure content data;
  • the digital content 13A is the electronic version of the content data and other data included in the content 1.
  • the digital content 13A includes, as content data, image data that is the same as or related to the content 1, data regarding product numbers, and the like.
  • Digital content 13A is stored in database 13 .
  • a user who is a purchaser of Content 1 can collect, appreciate, and enjoy printed Content 1.
  • the user can display and enjoy not only the printed content 1 but also the digital content 13A having the same or related image data as the content on the terminal 30.
  • FIG. since the user can obtain not only the digital information of the digital content 13A but also the tangible item of the content 1 printed on paper, the user has a strong sense of purchase, which is preferable.
  • a 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 on printing paper and issue the printed content 1 .
  • the issuing device 200 is, for example, a multi-function device installed in a store that performs a content print service or the like.
  • MFPs are used to provide content print services as well as other print services, copy services, and facsimile services. MFPs can generally be operated directly by customers visiting the store, but may also be operated by store staff.
  • the issuing device 200 Upon receiving an operation by an operator such as a customer (user), the issuing device 200 acquires necessary content data from the content issuing server 300 and issues content 1 by printing the content data.
  • the issuing device 200 is configured to receive an input of a product number. The entry of the product number is performed, for example, by operating a key or by reading a code indicating the product number with a reader included in the multifunction machine.
  • the issuing device 200 is configured to receive a payment operation for the price of the content 1 and execute payment processing to settle the price before the content 1 is issued.
  • Content 1 is issued after the payment process is completed.
  • a person (user) who intends to purchase the content 1 can pay for the content 1 at a store such as a convenience store, so that the content 1 can be obtained easily. Also, the content NFT101 can be easily obtained by paying for the content 1 at the store.
  • the content issuing server 300 is connected to the issuing device 200 via the network 15 .
  • the content issuing server 300 is an external device installed at a location separate from the issuing device 200 so that a plurality of issuing devices 200 can be connected.
  • the content issuing server 300 has content data for content 1 published by the issuing device 200 and is configured to transmit the content data to the issuing device 200 in response to a request from the issuing device 200 .
  • the content issuing server 300 is composed of a computer equipped with a processor and memory.
  • the content issuing server 300 has a computer program. This computer program has program code for causing a computer to function as the content issuing server 300 .
  • a system 500 according to the second embodiment can include a content introduction web server 400 connected to the network 15 .
  • the content introduction web server provides a website 600 (see FIG. 8) that is browsed by those who wish to purchase the content 1 .
  • This website 600 displays a list of contents that can be issued by the issuing device 200 and product numbers of each of the contents.
  • the website 600 may display the price of each content.
  • the content introduced on the website may include content with the content NFT 101 and content without the content NFT 101 .
  • the content introduction web server 400 is composed of a computer equipped with a processor and memory.
  • the content introduction web server has a computer program. This computer program has program code for causing a computer to function as the content introduction Web server 400 .
  • a system 500 according to the second embodiment can include a content non-fungible token management system 10 (content NFT management system 10) connected to the network 15.
  • content NFT management system 10 content non-fungible token management system 10
  • FIG. 9 shows the content NFT management system 10.
  • the content NFT management server 12, database 13 and smart contract 130 shown in FIG. 9 have the same functions as the ticket NFT management server 12, database 13 and smart contract 130 shown in FIG.
  • the digital content 13A is associated with the non-fungible token 101. That is, the digital content 13A is converted to NFT.
  • the non-fungible token 101 associated with the digital content 13A is also called "content NFT 101".
  • NFT_ID NFT identifier
  • the correspondence between the digital content 13A and the content NFT101 is realized, for example, by associating the digital content 13A with NFT_ID: A of the corresponding content NFT101 and storing it in the database 13.
  • NFT_ID: A of the corresponding content NFT101 When one digital content 13A is associated only with NFT_ID:A of one corresponding content NFT101, one-to-one correspondence between the content NFT101 and the digital content 13A is realized.
  • a single digital content 13A may be associated with the NFT_IDs of multiple content NFTs 101.
  • one digital content 13A may be associated with the NFT_IDs of the plurality of content NFTs 101.
  • the owner (and owner history) of the content NFT 101 is recorded in the blockchain 11. Proof of being the owner of the content NFT 101 is also proof of being the owner of the digital content 13A. It is also possible to trade (sell/transfer to a third party) the content NFT 101 for trading the digital content 13A.
  • the content NFT 101 associated with the digital content 13A is stored in the blockchain user account 110, the user who has that user account is also the owner of the digital content 13A. As will be described later, the content NFT 101 is sent to the user account 110 by performing a predetermined operation after the user purchases the printed content 1 .
  • the content NFT management system 10 may include a content NFT management server 12.
  • the content NFT management server 12 can configure the content NFT management system 10 of the embodiment together with the smart contract 130 .
  • the content NFT management server 12 provides functions necessary for allowing the user to obtain the content NFT 101 associated with the digital content 13A.
  • the content NFT management server 12 is composed of a computer having a processor 12A and a memory 12B.
  • a computer program 12C stored in the memory 12B has program code for causing a computer to function as the content NFT management server 12.
  • the user who is the owner of the content NFT101 associated with the digital content 13A has a user terminal 30 (see FIG. 7).
  • the user terminal 30 can be used for browsing the digital content 13A associated with the content NFT 101 owned by the user.
  • FIG. 10 shows the procedure for issuing content 1 using the system 500 (method for producing content 1).
  • a person (user) who wishes to purchase the content 1 uses the terminal 30 to confirm the product number described on the content introduction website 600 .
  • the user visits a store such as a convenience store and has Content 1 issued (steps S1001 to S1003, S1010, S1011).
  • the user first inputs a product number to the issuing device 200.
  • the issuing device 200 acquires the item number of the content 1 (step S1001).
  • the display of the issuing device 200 allows selection of the content to be purchased from the list of purchasable content 1, the user selects the content 1 that the user wishes to purchase, and the issuing device 200 displays the content 1. You can get the item number.
  • the issuing device 200 processes payment for content 1 (step S1002). As a result, the payment for the content 1 is completed.
  • the issuing device 200 acquires the content data after the payment is processed (step S1011). Note that acquisition of content data may be performed before payment processing (step S1002).
  • the issuing device 200 uses the acquired product number (first identification information) to acquire content data. More specifically, the issuing device 200 transmits the item number to the content issuing server 300 (step S1003).
  • the content issuing server 300 transmits the content data corresponding to the product number to the issuing device 200 (step S1009).
  • the issuing device acquires content data.
  • the acquired content data includes the data of the two-dimensional code 1A.
  • the content data is data for printing the content 1 .
  • the issuing device 200 prints the content data for printing the content 1 on printing paper and issues the content 1 (step S1011).
  • the printed content 1 has a two-dimensional code 1A as shown in FIG.
  • the two-dimensional code 1A is used, for example, to obtain the content NFT101 associated with the digital content 13A, which is the digitized content 1.
  • FIG. 1
  • the content issuing server 300 transmits 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 of various content items 1 that can be issued in association with product numbers.
  • the content data transmitted to the content NFT management system 10 can be identified from the product number transmitted in step S1003 from the content data of the content 1 to be published transmitted from the issuing device 200 .
  • the content NFT management system 10 Upon receiving the content data, the content NFT management system 10 executes processing for the content NFT 101 (steps S1005 to S1007).
  • step S1003 generation of content NFT101.
  • the content data is incorporated into the initial NFT.
  • An NFT in which content data is incorporated is content NFT101.
  • the content data stored in the database 13 becomes the digital content 13A.
  • the content NFT management server 12 generates two-dimensional code data indicating at least the second identification information for identifying the content NFT 101 (step S1004).
  • the two-dimensional code indicates a URL (Uniform Resource Locator), and the URL indicates, for example, the domain of the content NFT management server 12 and the second identification information.
  • URL Uniform Resource Locator
  • the second identification information for identifying the content NFT101 may be NFT_ID: A of the content NFT101, but here, "aaaaa”, which is the product number of the digital content 13A and the content 1 associated with the content NFT101, is the second identification information. 2 used as identification information.
  • 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 .
  • the content NFT management server 12 associates the product number "aaaaa” with the NFT_ID: A so that the NFT_ID: A of the content NFT 101 can be grasped from the product number "aaaaa” that is the second identification information of the content NFT 101, It is saved in the management database 12D of the content NFT management server 12 (see FIG. 12).
  • the content NFT management server 12 can grasp the NFT_ID from the product number, which is the second identification information, and can also grasp the product number from the NFT_ID.
  • the content NFT management server 12 transmits 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).
  • the content issuing server 300 which has received the two-dimensional code data and the product number of the content 1 to which the two-dimensional code is to be attached, stores the received two-dimensional code data in association with the content data having the received product number. (Step S1008). Thereby, the content issuing server 300 can add the two-dimensional code data to the content data and save it.
  • the content issuing server 300 transmits content data including two-dimensional code data to the issuing device 200 (step S1009), and the issuing device 200 receives the content data (step S1010).
  • the content 1 produced by printing this content data has a two-dimensional code 1A, as shown in FIG. 7, and this two-dimensional code 1A has second identification information for identifying the content NFT101.
  • the two-dimensional code 1A is used by the user to acquire the content NFT101.
  • FIG. 11 shows another example of the content 1 issuing procedure (content 1 manufacturing method) using the system 500 .
  • points not particularly described are the same as in the example of FIG.
  • step S1003 before the content issuing server 300 receives a content data request (step S1003) from the issuing device 200, the processing of steps S1005 and S1006 is executed.
  • the content NFT management system 10 receives content data in advance from the content issuing server 300, executes steps S1005 and S1006, and converts the content data to NFT.
  • 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, the product number (first identification number) and Two-dimensional code data indicating the same product number (second identification information) is transmitted to the content issuing server 300 (step S1007). Subsequent processing is performed in the same manner as in FIG. In the case of the processing of FIG. 11, since the content data is converted to NFT in advance, the content 1 can be quickly issued.
  • FIG. 12 shows a procedure for the user to acquire the content NFT 101 corresponding to the content 1 using the published content 1.
  • Steps S1201, S1202, S1203, and S1204 shown in FIG. 12 are substantially the same processes as steps S501, S502, S503, and S504 shown in FIG.
  • digital content 13A associated with content NFT101 is displayed on the user terminal 30 of the user who has become the owner of content NFT101 by means of an owner change request using reading of code 1A. be.
  • the display 31 of the user terminal 30 displays a content NFT display screen 33 showing the digital content 13A associated with the content NFT101. In this way, by obtaining the content NFT101, the user can use it, such as displaying the digital content 13A associated with the content NFT101.
  • the issuing device acquires the first identification information, the issuing device acquires data identified by the first identification information from an external device via a network; the data is printed by the issuing device; provided that The data identified by the first identification information includes data of a machine-readable code, and the code is recorded in a block chain and the non-fungible token management system identifies the non-fungible token. at least indicating the second identification information for doing.
  • the data identified by the first identification information acquired by the issuing device includes code data indicating at least the second identification information for identifying the non-fungible token. Therefore, by causing the issuing device to acquire the first identification information, a printed matter to which a code for identifying the non-fungible token is added can be obtained.
  • Said code is When read by the terminal, The management system acquires the second identification information indicated by the code from the terminal, Preferably, said management system is used to transmit said non-fungible token identified by said second identification information to a blockchain account utilized at the terminal that read said code.
  • an issuing device configured to execute payment processing for accepting payment of a price acquires data for printing from an external device via a network; the data is printed by the issuing device; provided that The data identified by the first identification information includes data of a machine-readable code, and the code is recorded in a block chain and the non-fungible token management system identifies the non-fungible token. at least indicating the second identification information for doing.
  • a printed matter to which a code for identifying a non-fungible token is attached by producing a printed matter to which a code for identifying a non-fungible token is attached by an issuing device having a function of accepting payment becomes easier to obtain.
  • a method performed by a device for sending data for printing a machine-readable code to an issuing device for printing said code comprising: The code indicates at least second identification information for a non-fungible token management system recorded in a blockchain to identify the non-fungible token; said device obtaining data for printing said code from said management system; Method.
  • the device that transmits the data for printing the code to the issuing device obtains the second identification information for identifying the non-fungible token from the management system of the non-fungible token. Data can be sent to the issuing device for printing of a code indicative of second identification information for identifying the bulltoken.
  • 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 code image data includes the second identification information.
  • the data for generating the code image data includes a URL for accessing the management system.

Abstract

L'invention concerne une technique pour permettre l'obtention d'un jeton non fongible (NFT) par l'intermédiaire d'un produit facilement disponible. Le procédé divulgué comprend les étapes suivantes : des premières informations d'identification permettant d'identifier un produit fabriqué par impression sont acquises par un dispositif d'émission pour imprimer le produit ; des données permettant d'imprimer le produit identifié par les premières informations d'identification sont acquises par le dispositif d'émission depuis un dispositif externe par l'intermédiaire d'un réseau à l'aide des premières informations d'identification ; et les données d'impression sont imprimées par le dispositif d'émission. Les données permettant d'imprimer le produit identifié par les premières informations d'identification comprennent des données pour un code lisible par machine. Le code indique au moins des secondes informations d'identification pour qu'un système de gestion de NFT enregistrés dans une chaîne de blocs identifie un produit de NFT avec lequel des données relatives au produit sont associées. Lorsque le code est lu par un terminal, le système de gestion acquiert les secondes informations d'identification indiquées par le code depuis le terminal, et transmet le jeton non fongible du produit identifié par les secondes informations d'identification à un compte de chaîne de blocs utilisé dans le terminal qui lit le code.
PCT/JP2022/027436 2021-07-12 2022-07-12 Procédé et système de fabrication pour produit fabriqué par impression WO2023286773A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2023534817A JPWO2023286773A1 (fr) 2021-07-12 2022-07-12

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021115309 2021-07-12
JP2021-115309 2021-07-12

Publications (1)

Publication Number Publication Date
WO2023286773A1 true WO2023286773A1 (fr) 2023-01-19

Family

ID=84919341

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/027436 WO2023286773A1 (fr) 2021-07-12 2022-07-12 Procédé et système de fabrication pour produit fabriqué par impression

Country Status (2)

Country Link
JP (1) JPWO2023286773A1 (fr)
WO (1) WO2023286773A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7383844B1 (ja) 2023-06-06 2023-11-20 株式会社メディアドゥ 利用認証システム、利用認証プログラムおよび利用認証方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019185510A (ja) * 2018-04-13 2019-10-24 ビリングシステム株式会社 チケット管理システム、チケット管理装置、チケット管理方法、および、チケット管理プログラム
US20200005284A1 (en) * 2018-07-01 2020-01-02 Madhu Vijayan Systems and Methods for Implementing Blockchain-Based Content Engagement Platforms Utilizing Media Wallets
JP2021089640A (ja) * 2019-12-05 2021-06-10 ｂａｃｏｏｒ ｄＡｐｐｓ株式会社 対象物を管理する方法及び管理サーバ
WO2021132483A1 (fr) * 2019-12-26 2021-07-01 シビラ株式会社 Procédé de liaison d'application, programme informatique et système de liaison d'application

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019185510A (ja) * 2018-04-13 2019-10-24 ビリングシステム株式会社 チケット管理システム、チケット管理装置、チケット管理方法、および、チケット管理プログラム
US20200005284A1 (en) * 2018-07-01 2020-01-02 Madhu Vijayan Systems and Methods for Implementing Blockchain-Based Content Engagement Platforms Utilizing Media Wallets
JP2021089640A (ja) * 2019-12-05 2021-06-10 ｂａｃｏｏｒ ｄＡｐｐｓ株式会社 対象物を管理する方法及び管理サーバ
WO2021132483A1 (fr) * 2019-12-26 2021-07-01 シビラ株式会社 Procédé de liaison d'application, programme informatique et système de liaison d'application

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7383844B1 (ja) 2023-06-06 2023-11-20 株式会社メディアドゥ 利用認証システム、利用認証プログラムおよび利用認証方法

Also Published As

Publication number Publication date
JPWO2023286773A1 (fr) 2023-01-19

Similar Documents

Publication Publication Date Title
US7209889B1 (en) Secure system for the issuance, acquisition, and redemption of certificates in a transaction network
CN105787712A (zh) 用收据存储来处理支付收据
WO2018047982A1 (fr) Procédé de paiement et système de paiement utilisant des informations de code
JP2002024730A (ja) 携帯電話による電子決済方法とシステム
JP6990796B2 (ja) 決済処理方法
WO2020013206A1 (fr) Système de gestion de billet et son procédé d'exploitation
JP6910509B1 (ja) 決済処理方法
JP6990797B2 (ja) 決済処理方法
WO2023286773A1 (fr) Procédé et système de fabrication pour produit fabriqué par impression
JP6845960B1 (ja) 決済処理方法及び決済処理装置
JP4237012B2 (ja) レシート発行管理装置、レシート発行管理システム、及びレシート発行管理装置用プログラム
TWM506330U (zh) 電子票券購票系統
JP5259998B2 (ja) 画像付加商品の取引方法及びシステム
JP2002123729A (ja) チケット発行・照会装置、チケット発行・照会方法
JP6783097B2 (ja) 決済方法および決済支援方法
JP7269188B2 (ja) 出力制御プログラム、出力制御装置及び出力制御方法
JP7130089B2 (ja) 情報処理装置、免税処理システム、プログラムおよび免税実行方法
JP7363097B2 (ja) 販売システム、ゲート装置、サーバ、レジ端末、及び販売方法
JP7373178B1 (ja) 情報処理方法、プログラム、情報処理装置、コレクションアイテム用の収容ケース及び情報処理システム
JP6797264B2 (ja) 商品データ処理装置、プログラム、及び商品データ処理方法
JP6217043B2 (ja) 出入金管理サーバ装置、出入金管理システム、およびその動作方法
JP2023179831A (ja) 販売データ管理システム、情報処理装置、および端末装置
TWI626611B (zh) 二手票券交易系統及其方法
JP5545558B2 (ja) 画像付加商品の取引方法及びシステム
JP2022031858A (ja) 決済処理方法及び決済処理装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22842116

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023534817

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE