Information processing system, program, and information processing method

Abstract

To provide a technology for giving added values.SOLUTION: An information processing system executes NFT distribution processing based on a user's request to distribute NFTs, and executes ticket distribution processing based on a user's request to distribute tickets after receiving the NFTs. A program causes a computer to execute the steps of performing the NFT distribution processing based on the user's request to distribute NFTs, and of performing the ticket distribution processing based on the user's request to distribute tickets after receiving the NFTs.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present disclosure relates to an information processing system, a program, and an information processing method. [Background technology]

[0002] In recent years, non-fungible tokens (NFTs), which can guarantee and prove the uniqueness and ownership of digital art, digital trading cards, game items, and other digital assets, have become widely recognized and widespread. For example, Patent Document 1 discloses technology for using NFTs as digital tickets. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2023 / 286774 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the technology disclosed in Patent Document 1 is a technology for simply using NFTs as digital tickets, and there is still room for improvement.

[0005] The present disclosure aims to provide a technology that adds value to improve the above technology. [Means for solving the problem]

[0006] The information processing system according to the present disclosure executes an NFT distribution process based on a user's request for NFT distribution, and executes a ticket distribution process based on a ticket distribution request by a user who has received an NFT. The information processing system according to the present disclosure also executes a ticket distribution process based on a user's request for ticket distribution, and executes an NFT distribution process based on an NFT distribution request by a user who has received a ticket.

[0007] Furthermore, a program according to the present disclosure causes a computer to execute a procedure for executing an NFT distribution process based on a user's request for NFT distribution, and a procedure for executing a ticket distribution process based on a ticket distribution request by a user who has received an NFT. Further, a program according to the present disclosure causes a computer to execute a procedure for executing a ticket distribution process based on a user's request for ticket distribution, and a procedure for executing an NFT distribution process based on an NFT distribution request by a user who has received a ticket.

[0008] Furthermore, the information processing method according to the present disclosure is an information processing method executed by a computer, and includes the step of executing an NFT distribution process based on a user's request for NFT distribution, and the step of executing a ticket distribution process based on a ticket distribution request by a user who has received an NFT. Furthermore, the information processing method according to the present disclosure is an information processing method executed by a computer, and includes the step of executing a ticket distribution process based on a user's request for ticket distribution, and the step of executing an NFT distribution process based on an NFT distribution request by a user who has received a ticket. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to provide a technology that adds value. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of an information processing system according to an embodiment of the present disclosure. [Figure 2]FIG. 2 is a diagram illustrating an image of each database. [Figure 3] A figure showing an example of the data structure of an NFT. [Figure 4] FIG. 10 is a diagram showing an example of a screen displayed on an NFT viewer. [Figure 5] FIG. 3 is a sequence diagram showing an example of a processing flow according to the first embodiment. [Figure 6] FIG. 10 is a sequence diagram showing an example of a processing flow according to the second embodiment. [Figure 7] FIG. 11 is a sequence diagram showing an example of a processing flow according to the third embodiment. [Figure 8] FIG. 13 is a sequence diagram showing an example of a processing flow according to the fourth embodiment. [Figure 9] FIG. 13 is a sequence diagram showing an example of a processing flow according to the fifth embodiment. [Figure 10] FIG. 20 is a sequence diagram showing an example of a processing flow according to the sixth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. However, more detailed explanation than necessary, for example, detailed explanation of well-known matters or redundant explanation of substantially the same configuration, may be omitted.

[0012] The drawings described below and referenced below are provided to help those skilled in the art understand the present disclosure, and are not intended to limit the scope of the claims of the present disclosure.

[0013] In each embodiment of the present disclosure, an NFT ticket, which is a set of a ticket and an NFT, is provided to a user. Possible patterns for providing an NFT ticket include a case where the NFT and ticket are provided for a fee, a case where the NFT is provided free of charge and the ticket is provided for a fee, a case where the NFT is provided for a fee and the ticket is provided free of charge, and a case where the NFT and ticket are provided free of charge. Possible methods for a user to acquire an NFT ticket include a method where the ticket and NFT are acquired as a set, a method where the ticket can be acquired by acquiring an NFT, a method where the ticket can be acquired by acquiring an NFT, a method where the ticket can be acquired in the process of acquiring an NFT, and so on.

[0014] Tickets include tickets with a predetermined code image printed on a thin medium such as paper or plastic, and digital tickets, which are digitized tickets without using a thin medium. Digital tickets are stored in a storage device or the like within a user's device (such as a smartphone), and the code image is displayed as a digital ticket on the device's screen. Examples of code images include QR codes (registered trademarks, omitted below) and barcodes. Examples of tickets include transportation tickets such as public transportation tickets (railroad tickets), airplane boarding passes, and ship tickets; taxi tickets; admission tickets to art galleries, museums, exhibition halls, live shows, concerts, theaters, amusement parks, amusement facilities, attraction facilities, restaurants, and various events; coupons offering a predetermined discount or up to a predetermined limit; betting tickets for public races or favorite celebrities; and keys (electronic keys) for various facilities such as accommodations and public facilities. The code image can be scanned by a predetermined scanner (e.g., a scanner attached to a ticket gate, boarding gate, entrance gate, entrance gate, cash register, etc.) and used in the same way as a ticket.

[0015] [Embodiment 1] FIG. 1 is a diagram illustrating an example of the configuration of an information processing system according to the first embodiment of the present disclosure.

[0016] The information processing system 1 includes an NFT processing device 10. The NFT processing device 10 is communicatively connected to a ticket processing device 20, a user device 30, and a blockchain 40 via a communication network N.

[0017] The communication network N is configured, for example, from the Internet, a mobile communication network, a LAN (Local Area Network), etc., or a combination of these.

[0018] The NFT processing device 10 and the ticket processing device 20 are information processing devices, such as a server computer or a personal computer. These information processing devices are configured with a CPU, storage, ROM, RAM, input / output I / F, a communication unit, a display unit, etc. Note that information processing devices are well-known technology, so detailed explanations will be omitted.

[0019] The user device 30 is, for example, a mobile terminal or personal computer owned by the user. The mobile terminal is, for example, a smartphone, a tablet terminal, etc. The user device 30 holds a wallet W30 and therefore holds user data such as a wallet address. Furthermore, the NFTs held by the user have a function that allows the user to check the NFTs they own, and can be checked, for example, from an NFT viewer.

[0020] The blockchain 40 is a distributed computing system consisting of multiple node terminals. Each node terminal sends and receives transaction data related to the blockchain 40. Each node terminal records processing requests notified to the blockchain 40 from outside, executes the processing in response to the processing request, and records the results in storage managed by the node terminal. The processing request is transmitted to each node terminal, and each node terminal executes the same processing for that processing request and records the output, thereby enabling each node terminal to hold exactly the same information even in a distributed environment. The processing executed on this blockchain 40 is called a smart contract.

[0021] A smart contract is a computer program that is executed on each node terminal, and similar to a processing request, after the blockchain 40 receives a request to register the program, it distributes it to each node terminal and registers it.

[0022] The NFT processing device 10 includes an NFT processing unit 11, a ticket transaction processing unit 12, a behavior history processing unit 13, etc. The NFT processing unit 11 executes various processes related to NFTs by using a processor such as a CPU to execute an NFT processing program and an NFT transaction processing program stored in storage, etc. The ticket transaction processing unit 12 executes various processes related to NFT transactions by using a processor such as a CPU to execute a ticket transaction processing program stored in storage, etc.

[0023] The storage etc. stores an NFT management database (NFT management DB) 14, a distribution management database (distribution management DB) 15, a user management database (user management DB) 16, a behavior history database (behavior history DB) 17, etc. The NFT management DB 14 is a database that stores data related to content etc. to be converted into NFTs. The distribution management DB 15 is a database that stores data related to the distribution etc. of NFTs. The user management DB 16 is a database that stores data related to NFTs etc. held by users. The behavior history DB 17 is a database that stores data related to the behavior history etc. of users who have received NFTs.

[0024] FIG. 2 is a diagram illustrating an example of each database. FIG. 2(a) is a diagram illustrating an example of the NFT management DB 14. The NFT management DB 14 includes a serial number sequence (No.) that stores the serial number of an NFT ticket, a ticket identification data sequence (ticket ID) that stores ticket identification data for a digital ticket, a chain ID sequence that identifies the blockchain 40, a contract address sequence of a smart contract corresponding to the NFT, and a metadata sequence that stores metadata used when converting to NFT. The NFT management DB 14 may also be configured to manage a content sequence that stores content to be converted to NFT (image data, video data, sound data, etc.).

[0025] 2(b) is a diagram showing an example of the distribution management DB 15. The distribution management DB 15 includes a distribution serial number column (distribution No.) that stores the serial number of the NFT ticket to be distributed, a ticket identification data column (ticket ID) that stores the ticket identification data of the digital ticket, a token ID column that stores the token identification data (token ID) of the NFT, and a distribution data column. The distribution data column includes a distribution period column that stores the distribution period (sales period) of the NFT ticket, a distributed column that stores whether the NFT ticket has been distributed or not, a distribution date and time column that stores the date and time of distribution, a user ID column that stores the user identification data (user ID) of the user who distributed the ticket, a wallet address column that stores the user's wallet address, etc.

[0026] 2(c) is a diagram showing an example of the user management DB 16. The user management DB 16 includes a user ID column that stores user identification data, a wallet address column that stores wallet addresses, a distributed NFT column, etc. The distributed NFT column stores the token ID of the NFT distributed to the user.

[0027] 2(d) is a diagram showing an example of the behavior history DB 17. The behavior history DB 17 includes a user ID column that stores user identification data, a distributed NFT column that stores token IDs of distributed NFTs, a ticket ID column that stores ticket IDs, a ticket usage history column, etc. The ticket usage history column stores the user's digital ticket usage history based on digital ticket usage data transmitted from the ticket processing device 20, which will be described later.

[0028] The NFT processing unit 11 executes various processes related to NFT processing. When distributing a new NFT ticket, the NFT processing unit 11 executes pre-distribution processing. In the pre-distribution processing, the NFT content data (content to be converted into NFT) to be distributed together with the digital ticket, metadata for NFT conversion, etc. are registered in the NFT management DB 14 in association with the ticket identification data (ticket ID) of the digital ticket sent from the ticket processing device 20 (described later). The distribution number, ticket ID, and distribution period are also registered in the distribution management DB 15.

[0029] Furthermore, when an NFT ticket is distributed to a user, the NFT processing unit 11 executes an NFT distribution process. In the distribution process, first, content data and metadata corresponding to the ticket ID are extracted from the NFT management DB 14. Next, the extracted content data and metadata are converted into an NFT, transaction data for distributing the NFT to the user's wallet address is generated, and the transaction data is sent to the blockchain 40. Furthermore, upon completion of the NFT distribution, post-distribution processing is executed. In the post-distribution processing, the token ID of the distributed NFT, the fact that the NFT has been distributed, the distribution date and time, the user ID of the user who distributed the NFT, the user's wallet address, etc. are registered in the distribution management DB 15. Furthermore, if the user to whom the NFT was distributed this time is a new user, the user ID and the token ID of the distributed NFT are registered in the user management DB 16. If the user is an existing user, the token ID of the distributed NFT is additionally registered in association with the user ID in the user management DB 16. Furthermore, the ticket ID of the distributed digital ticket is transmitted to the ticket processing device 20, which will be described later.

[0030] In addition, when the NFT processing unit 11 receives a request to obtain a digital ticket from a user, it identifies the ticket ID corresponding to the user ID, generates a QR code for the identified ticket ID, and sends the generated QR code as a digital ticket.

[0031] In addition, the NFT processing unit 11 executes a usage history registration process to store the usage history of the digital ticket in association with the user's ticket ID based on the received usage history data of the digital ticket transmitted from the ticket processing device 20 described below.

[0032] If the NFT ticket is for sale (provided for a fee), the ticket transaction processing unit 12 executes transaction processing related to the distribution of the NFT ticket (processing related to payment if the ticket is distributed for a fee).

[0033] The ticket processing device 20 includes a ticket processing unit 21. The ticket processing unit 21 executes various processes related to tickets by executing a ticket processing program stored in storage or the like using a processor such as a CPU. The storage or the like stores a ticket management database (ticket management DB) 22 and the like.

[0034] The ticket management DB22 stores ticket identification data (ticket ID) for identifying (verifying) the digital tickets to be distributed (sold), distribution data indicating whether or not the tickets have been distributed (sold), and ticket usage history data (entry date and time, exit date and time, station, etc.).

[0035] The ticket processing unit 21 generates (or registers) identification data (ticket ID) for the digital ticket to be distributed, and transmits the generated ticket ID to the NFT processing device 10. For example, if a railway company distributes (sells) 100 one-day passes for Tokyo as digital tickets, it generates 100 different ticket IDs and transmits the 100 different ticket IDs to the NFT processing device 10. The ticket ID is data used to verify the digital ticket. When an NFT ticket is distributed to a user, the NFT processing device 10 transmits the distributed ticket ID. Upon receiving the ticket ID, the ticket processing unit 21 registers the digital ticket with the ticket ID in the ticket management DB 22 as having been sold.

[0036] Also, in the case of a railway company, when a QR code (registered trademark (omitted below)) serving as a digital ticket (Tokyo one-day free ticket) is scanned at a ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID from the QR code and sends a matching request to the ticket processing device 20, including the identified ticket ID, entry date and time data (or exit date and time data), station data, etc. When the ticket processing device 21 receives the matching request, the ticket processing device 21 executes a matching process for the ticket ID and returns the matching result to the ticket gate. In accordance with the matching process, the ticket processing device 21 registers the usage history (entry date and time, exit date and time, station, etc.) in the ticket management DB. Furthermore, when the matching process is completed, the ticket processing device 21 sends the usage history to the NFT processing device 10.

[0037] Also, in the case of a railway company, when a QR code (registered trademark (omitted below)) serving as a digital ticket (Tokyo one-day free ticket) is scanned at a ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID from the QR code and sends a matching request to the ticket processing device 20, including the identified ticket ID, entry date and time data (or exit date and time data), station data, etc. When the ticket processing device 21 receives the matching request, the ticket processing device 21 executes a matching process for the ticket ID and returns the matching result to the ticket gate. In accordance with the matching process, the ticket processing device 21 registers the usage history (entry date and time, exit date and time, station, etc.) in the ticket management DB. Furthermore, when the matching process is completed, the ticket processing device 21 sends the usage history to the NFT processing device 10.

[0038] FIG. 3 is a diagram showing an example of the data structure of an NFT. For example, NFTs are distributed based on the ERC-721 (Ethereum Request for Comments 721) standard. NFTs are defined based on index data, metadata, content data, ticket data, etc. Note that metadata can be defined in various ways other than those described above.

[0039] The index data includes a token ID, which is data for identifying (specifying) an NFT, holder data, which is data for identifying (specifying) the holder (wallet address, etc.), a token URI (Uniform Resource Identifier), etc. The token URI is data that indicates the storage location of metadata corresponding to the NFT, and is, for example, the URN (Uniform Resource Name) or URL (Uniform Resource Locator) of the metadata.

[0040] The metadata includes a content ID, which is identification data used to identify the NFT content, a description such as the content name, content type (image (still image), video, sound, etc.), explanatory text (explanation about the NFT and content, explanation about how to obtain and use the digital ticket, distribution period, expiration date, etc.), sales price, a content URL, which is data indicating the storage location of the content data, and a ticket URL, which is data indicating the storage location of the digital ticket data (URL of the ticket processing device, digital ticket to be distributed, etc.).

[0041] Once the distribution of NFTs to the user is complete, the user can operate the user device 30 to access the NFT viewer and check the NFTs they own on the NFT viewer's owned NFT confirmation screen. Figure 4 shows an example of a screen displayed on the NFT viewer.

[0042] 4(a) is an example of an owned NFT confirmation screen. The owned NFT confirmation screen 31 displays various NFT tickets owned by the user. As examples, this owned NFT confirmation screen 31 displays a ticket NFT image TC1, an admission ticket image TC2, a voting ticket NFT image TC3, and an electronic key NFT image TC4.

[0043] Figure 4(b) shows an example of an NFT display screen 32 that appears when a ticket NFT image TC1 is selected (tapped or clicked). The NFT display screen 32 displays ticket NFT information TC10. The ticket NFT information TC10 displays an NFT content image (ticket NFT content image) TC11 and explanatory text TC12. The explanatory text TC12 displays the NFT content name, content type, explanatory text (explanation of the NFT and content, how to obtain and use the digital ticket, distribution deadline, expiration date, etc.), content URL, ticket URL, etc., based on metadata. The ticket URL can be linked to the digital ticket acquisition site (page) by selecting the NFT content image, or it can be accessed by selecting a ticket URL displayed separately from the content image. If the content is dynamic content such as video or audio, selecting the NFT content image plays the specified dynamic content via the content URL. Depending on the metadata definition, various functions other than those described above can be added.

[0044] 4(c) is an example of a digital ticket display screen 33 that is displayed when the ticket NFT image TC11 is selected (tapped or clicked). A digital ticket image TC110 is displayed on the digital ticket display screen 33. The digital ticket image TC110 displays a digital ticket code image TC111 and explanatory text, etc. TC112.

[0045] 5 is a sequence diagram showing an example of the flow of processing according to the first embodiment. In this sequence, an example will be described in which 100 NFT tickets (one-day free passes within Tokyo) are distributed as digital tickets.

[0046] First, as a preparation stage, the NFT processing device 10 generates content to be converted into NFT or acquires content to be converted into NFT, and also generates metadata (step S1).

[0047] Furthermore, as a preparation stage, the ticket processing device 20 registers 100 different ticket identification data (ticket IDs) for digital tickets to be distributed as a set with NFTs (step S2).

[0048] Next, the ticket processing device 20 transmits the 100 different ticket IDs to the NFT processing device 10 (step S3).

[0049] Next, the NFT processing device 10 executes pre-distribution processing (step S4). Next, when the NFT processing device 10 finishes the pre-distribution processing, it enables users to receive NFT tickets on an NFT distribution site or the like (for example, displays the NFT ticket on an NFT distribution list screen) (step S5).

[0050] The user accesses the NFT distribution site using the user device 30, and if the user wishes to receive (obtain) an NFT ticket, the user transmits an NFT ticket distribution request to the NFT processing device 10 via the NFT distribution site (step S6).

[0051] When the NFT processing device 10 receives the NFT ticket distribution request, it executes the NFT ticket transaction process (step S7).

[0052] Next, the NFT processing device 10 generates transaction data related to the generation of the NFT (describes the contents of the transaction) (step S8).

[0053] Next, the NFT processing device 10 transmits an NFT registration request to the blockchain 40 (step S9). In the NFT registration request, a transaction including digital signature data obtained by encrypting the transaction data with a private key and the transaction data is transmitted to the blockchain 40.

[0054] The blockchain 40 that receives the transaction verifies the authenticity of the digital signature data. If the blockchain 40 confirms that the digital signature data is authentic, it distributes the NFT by executing a smart contract that registers the transaction data linked to the digital signature data in a block (step S10).

[0055] Once verification and registration based on the transaction data is completed, the blockchain 40 returns a transaction log to the NFT processing device 10 (step S11).

[0056] Upon receiving the transaction log, the NFT processing device 10 executes post-distribution processing (step S12). Next, upon completing the post-distribution processing, the NFT processing device 10 transmits a distribution notification (for example, an NFT receiving URL) indicating that the distribution of the NFT has been completed to the user device 30 (step S13).

[0057] Upon receiving the distribution notification, the user operates the user device 30 to access the recipient included in the distribution notification. The recipient then connects to the wallet W30 and receives the NFT. Once receipt is complete, the user operates the user device 30 to access the NFT viewer and confirm the distributed NFT on the owned NFT confirmation screen 31 (see FIG. 4(a)) (step S14).

[0058] When a user obtains a digital ticket, the user accesses the NFT viewer on the user device 30 (step S15) and selects the NFT content image TC11 corresponding to the digital ticket on the NFT display screen 32 (see Figure 4(b)) (step S16).

[0059] Once the NFT image is selected, the user device 30 transmits a digital ticket request (including the user ID) to the NFT processing device 10 (step S17). A signature is required when transmitting the digital ticket request. There are, for example, three types of signature methods. The first signature method (Signature 1) emphasizes strictness (confidentiality, high security level, etc.). Signature 1 requires a signature in the wallet every time. For example, a signature based on the token contract address and ticket use date is required. The second signature method (Signature 2) ensures a certain degree of strictness. From the perspective of usability, Signature 2 does not require a signature in the wallet every time (signing is required periodically or at random times). For example, a signature based on the ticket use date is required. The third signature method (Signature 3) emphasizes usability. For example, Signature 3 requires a signature based on a password registered on an NFT distribution site or NFT viewer, a shared key (password, etc.) used for My Apps, etc. The order of strictness (confidentiality, high security level, etc.) is Signature 1 > Signature 2 > Signature 3. The NFT processing device 10 selects one of Signatures 1 to 3 depending on the level of strictness (type of digital ticket, first distribution and subsequent distributions, user credibility, usability, etc.).

[0060] When receiving a digital ticket request, the NFT processing device 10 compares the user ID with the signature (e.g., Signature 1), and if these are confirmed, identifies the ticket ID from the user ID and generates (QR-encodes) a QR code including the ticket ID, etc. (step S18).

[0061] Next, the NFT processing device 10 transmits the digital ticket data (QR code) to the user device 30 (step S19). When the user device 30 receives the digital ticket data (step S20), the digital ticket data is stored in storage or the like of the user device 30. The stored digital ticket data is displayed as a digital ticket code image TC111 on the digital ticket display screen 33 of the NFT viewer (see FIG. 4(c)). Note that in step S18, the NFT processing device 10 may extract (or generate) the ticket ID, etc., without generating a QR code, and transmit the ticket ID, etc. to the user device 30 in step S19. In this case, a QR code including the ticket ID, etc., is generated (QR-encoded) by a QR code generation application (program) installed on the user device 30.

[0062] When the user uses the digital ticket at the ticket gate, the digital ticket is displayed on the screen of the user device 30 (step S21).

[0063] The user causes the ticket gate to scan the digital ticket displayed on the screen of the user device 30 (step S22).

[0064] When the digital ticket is scanned by the ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID and sends a matching request including the identified ticket ID to the ticket processing device 20 (step S23). Upon receiving the matching request, the ticket processing device 20 matches the ticket ID and registers the usage history (step S24), and sends the matching result to the ticket gate (step S25).

[0065] After transmitting the matching result to the ticket gate, the ticket processing device 20 transmits the usage history data to the NFT processing device 10 (step S26).

[0066] Upon receiving the usage history data, the NFT processing device 10 executes a usage history registration process (step S27).

[0067] For example, if the digital ticket is a ticket that can be used for a specified period, such as a free pass, a round-trip ticket, or a coupon that can be used up to a specified upper limit, each process from step S21 to step S27 will be executed multiple times.

[0068] Furthermore, NFT ticket transaction processing may be divided into NFT transaction processing (payment processing) and ticket payment processing. In this case, it is conceivable to execute ticket transaction processing by adding a transaction processing function to the ticket processing unit 21 of the ticket processing device 20.

[0069] As described above, according to this embodiment, NFT tickets, which are sets of an NFT and a ticket, can be distributed to users (for a fee or free of charge). Furthermore, users who acquire an NFT ticket can obtain a digital ticket in addition to the NFT. The users can then use the acquired digital ticket. Therefore, it is possible to impart added value in the form of an NFT to a ticket (or add value in the form of a ticket to an NFT), thereby motivating users to acquire tickets (or NFTs). Furthermore, because the behavioral history DB17 of the NFT processing device 10 stores the behavioral history of users who have acquired NFT tickets, it is possible to obtain marketing use data such as each user's behavioral patterns and preferences.

[0070] [Embodiment 2] Next, a second embodiment of the present disclosure will be described. Note that in this embodiment, differences from the first embodiment will be described, and a description of similarities will be omitted. In the first embodiment, the NFT processing device 10 receives the ticket ID of the digital ticket from the ticket processing device 20 in advance during the preparation stage. However, in this embodiment, the NFT processing device 10 does not receive the ticket ID from the ticket processing device 20 during the preparation stage. The process related to obtaining the NFT is then executed first by the NFT processing device 10. Furthermore, when an NFT image is selected, the NFT processing device 10 receives the ticket ID from the ticket processing device 20 and executes the process related to the digital ticket.

[0071] Therefore, the NFT management DB14 of this embodiment (see Figure 2(a)) includes a serial number column (No.) that stores the serial number of the NFT ticket, a content column that stores the content to be converted into NFT (image data, video data, sound data, etc.), a metadata column that stores the metadata used when converting into NFT, etc., but does not have a ticket identification data column (ticket ID) that stores the ticket identification data of the digital ticket.

[0072] In addition, in the pre-distribution process in the NFT processing unit 11 in this embodiment, the content data of the NFT (content to be converted into NFT) to be distributed together with the digital ticket, metadata for NFT conversion, etc. are registered in the NFT management DB 14. In addition, the distribution number and distribution period are registered in the distribution management DB 15.

[0073] Furthermore, when the NFT processing unit 11 receives a request to acquire a digital ticket from a user, it requests a ticket ID from the ticket processing device 20, and stores the ticket ID sent from the ticket processing device 20 in response to the request in the ticket identification data string (ticket ID) of the distribution management DB as the ticket ID corresponding to the user ID. Then, it generates a QR code for the ticket ID and transmits the generated QR code as a digital ticket.

[0074] Furthermore, when a ticket ID is requested by the NFT processing device 10, the ticket processing unit 21 generates (or registers) identification data (ticket ID) for a newly distributed digital ticket and registers the generated ticket ID in the ticket management DB 22. Furthermore, the ticket processing unit 21 transmits the generated ticket ID to the NFT processing device 10.

[0075] 6 is a sequence diagram showing an example of the flow of processing according to the second embodiment. In this sequence, an example will be described in which 100 NFT tickets (one-day free passes within Tokyo) are distributed as digital tickets.

[0076] First, as a preparation stage, the NFT processing device 10 generates content to be converted into NFT or acquires content to be converted into NFT, and also generates metadata (step S31).

[0077] Next, the NFT processing device 10 executes pre-distribution processing (step S32). Next, when the NFT processing device 10 finishes the pre-distribution processing, it enables the user to receive the NFT ticket on an NFT distribution site or the like (for example, displays it on an NFT distribution list screen) (step S33).

[0078] The user accesses the NFT distribution site using the user device 30, and if the user wishes to receive an NFT ticket, sends an NFT ticket distribution request to the NFT processing device 10 through the NFT distribution site (step S34).

[0079] When the NFT processing device 10 receives the NFT ticket distribution request, it executes the NFT ticket transaction process (step S35).

[0080] Next, the NFT processing device 10 generates transaction data related to the generation of the NFT (describes the contents of the transaction) (step S36).

[0081] Next, the NFT processing device 10 transmits an NFT registration request to the blockchain 40 (step S37). In the NFT registration request, a transaction including digital signature data obtained by encrypting the transaction data with a private key and the transaction data is transmitted to the blockchain 40.

[0082] The blockchain 40 that received the transaction verifies the authenticity of the digital signature data. If the blockchain 40 confirms that the digital signature data is authentic, it distributes the NFT by executing a smart contract that registers the transaction data linked to the digital signature data in a block (step S38).

[0083] Once verification and registration based on the transaction data is completed, the blockchain 40 returns a transaction log to the NFT processing device 10 (step S39).

[0084] Upon receiving the transaction log, the NFT processing device 10 executes post-distribution processing (step S40). Next, upon completing the post-distribution processing, the NFT processing device 10 transmits a distribution notification indicating that the distribution of the NFT has been completed to the user device 30 (step S41).

[0085] Upon receiving the distribution notification, the user operates the user device 30 to access the NFT viewer and confirm the distributed NFT on the owned NFT confirmation screen 31 (see Figure 4(a)) (step S42).

[0086] When a user obtains a digital ticket, the user accesses the NFT viewer on the user device 30 (step S43) and selects the NFT content image TC11 corresponding to the digital ticket on the NFT display screen 32 (see Figure 4(b)) (step S44).

[0087] When the NFT image is selected, a digital ticket request (including the user ID) is sent from the user device 30 to the NFT processing device 10 (step S45).

[0088] When the digital ticket request is received, the user ID and signature (e.g., Signature 1) are verified, and if these are confirmed, the NFT processing device 10 requests a ticket ID from the ticket processing device 20 (ticket ID request) (step S46).

[0089] When the ticket ID request is received from the NFT processing device 10, the ticket processing device 20 generates a new ticket ID and registers the generated ticket ID in the ticket management DB 22 (step S47). After registering the ticket ID in the ticket management DB 22, the ticket processing device 20 transmits the generated ticket ID to the NFT processing device 10 (step S48).

[0090] Upon receiving the ticket ID, the NFT processing device 10 stores (registers) the ticket ID in the ticket identification data string (ticket ID) of the distribution management DB as a ticket ID corresponding to the user ID, and also generates (QR-encodes) the ticket ID and a QR code including the ticket ID, etc. (step S49).

[0091] Next, the NFT processing device 10 transmits the digital ticket data (QR code) to the user device 30 (step S50). When the user device 30 receives the digital ticket data (step S51), the digital ticket data is stored in storage or the like of the user device 30. The stored digital ticket data is displayed as a digital ticket code image TC111 on the digital ticket display screen 33 of the NFT viewer (see FIG. 4(c)). Note that in step S49, the NFT processing device 10 may extract (or generate) the ticket ID, etc., without generating a QR code, and transmit the ticket ID, etc. to the user device 30 in step S50. In this case, a QR code including the ticket ID, etc., is generated (QR-encoded) by a QR code generation application (program) installed on the user device 30.

[0092] When the user uses the digital ticket at the ticket gate, the digital ticket is displayed on the screen of the user device 30 (step S52).

[0093] The user causes the ticket gate to scan the digital ticket displayed on the screen of the user device 30 (step S53).

[0094] When the digital ticket is scanned by the ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID and sends a matching request including the identified ticket ID to the ticket processing device 20 (step S54). Upon receiving the matching request, the ticket processing device 20 performs ticket ID matching and registers the usage history (step S55), and sends the matching result to the ticket gate (step S56).

[0095] After transmitting the matching result to the ticket gate, the ticket processing device 20 transmits the usage history data to the NFT processing device 10 (step S57).

[0096] Upon receiving the usage history data, the NFT processing device 10 executes a usage history registration process (step S58).

[0097] For example, if the digital ticket is a ticket that can be used for a specified period, such as a free pass, a round-trip ticket, or a coupon that can be used up to a specified upper limit, each of the processes in steps S52 to S58 will be executed multiple times.

[0098] Furthermore, NFT ticket transaction processing may be divided into NFT transaction processing (payment processing) and ticket payment processing. In this case, it is conceivable to execute ticket transaction processing by adding a transaction processing function to the ticket processing unit 21 of the ticket processing device 20.

[0099] As described above, according to this embodiment, an NFT ticket, which is a set of an NFT and a ticket, can be distributed to a user (paid distribution or free distribution) using a method different from that of the first embodiment. Furthermore, a user who acquires an NFT ticket can obtain a digital ticket in addition to the NFT. The user can then use the acquired digital ticket. Therefore, it is possible to impart added value in the form of an NFT to a ticket (or add value in the form of a ticket to an NFT), thereby motivating the user to acquire a ticket (or an NFT). Furthermore, because the behavioral history DB17 of the NFT processing device 10 stores the behavioral history of users who have acquired NFT tickets, it is possible to obtain marketing use data such as each user's behavioral patterns and preferences.

[0100] [Embodiment 3] Next, a third embodiment of the present disclosure will be described. Note that in this embodiment, differences from the second embodiment will be described, and similarities will not be described again. In the second embodiment, the process related to obtaining an NFT was first executed by the NFT processing device 10, and when an NFT image was selected, the NFT processing device 10 received a ticket ID from the ticket processing device 20 and executed the process related to the digital ticket. However, in this embodiment, if a user who has obtained an NFT wishes to obtain a digital ticket, the process related to obtaining the digital ticket is executed by the ticket processing device 20.

[0101] Therefore, the NFT management DB14 of this embodiment (see Figure 2(a)) includes a serial number column (No.) that stores the serial number of the NFT, a content column that stores the content to be converted into NFT (image data, video data, sound data, etc.), a metadata column that stores the metadata used when converting into NFT, etc., but does not have a ticket identification data column (ticket ID) that stores the ticket identification data of the digital ticket.

[0102] In addition, in the pre-distribution process in the NFT processing unit 11 in this embodiment, the content data of the NFT (content to be converted into NFT) to be distributed together with the digital ticket, metadata for NFT conversion, etc. are registered in the NFT management DB 14. In addition, the distribution number and distribution period are registered in the distribution management DB 15.

[0103] Furthermore, when the NFT processing unit 11 receives a ticket ID (including a user ID) from the ticket processing device 20, it stores the ticket ID in association with the user ID in the ticket identification data string (ticket ID) of the distribution management DB.

[0104] Furthermore, when a digital ticket distribution request is received from the user device 30, the ticket processing unit 21 executes transaction processing related to the distribution of the digital ticket (processing related to payment in the case of paid distribution). Then, when the transaction processing is completed, the ticket processing unit 21 generates (or registers) identification data (ticket ID) for the newly distributed digital ticket and registers it in the ticket management DB 22. The ticket processing unit 21 also generates a QR code for the generated ticket ID and transmits the generated QR code as a digital ticket to the user device 30. The ticket ID (including the user ID) is also transmitted to the NFT processing device 10.

[0105] Therefore, since the transaction processing related to the distribution of digital tickets is performed by the ticket processing device 20, the NFT processing device 10 does not have a ticket transaction processing unit 12.

[0106] Also, the ticket URL in the metadata is the URL of the digital ticket distribution site (see Figure 3).

[0107] 7 is a sequence diagram showing an example of the flow of processing according to the third embodiment. In this sequence, an example will be described in which 100 NFT tickets (one-day free passes within Tokyo) are distributed as digital tickets.

[0108] First, as a preparation stage, the NFT processing device 10 generates content to be converted into NFT or acquires content to be converted into NFT, and also generates metadata (step S61).

[0109] Next, the NFT processing device 10 executes pre-distribution processing (step S62). Next, when the NFT processing device 10 finishes the pre-distribution processing, it enables users to receive NFTs on an NFT distribution site or the like (for example, displays the NFT on an NFT distribution list screen) (step S63).

[0110] The user browses the NFT distribution site using the user device 30, and if the user wishes to receive an NFT, the user sends an NFT distribution request to the NFT processing device 10 through the NFT distribution site (step S64).

[0111] Next, the NFT processing device 10 generates transaction data related to the generation of the NFT (describes the contents of the transaction) (step S65).

[0112] Next, the NFT processing device 10 transmits an NFT registration request to the blockchain 40 (step S66). In the NFT registration request, a transaction including digital signature data obtained by encrypting the transaction data with a private key and the transaction data is transmitted to the blockchain 40.

[0113] The blockchain 40 that received the transaction verifies the authenticity of the digital signature data. If the blockchain 40 confirms that the digital signature data is authentic, it distributes the NFT by executing a smart contract that registers the transaction data linked to the digital signature data in a block (step S67).

[0114] Once verification and registration based on the transaction data is completed, the blockchain 40 returns a transaction log to the NFT processing device 10 (step S68).

[0115] Upon receiving the transaction log, the NFT processing device 10 executes post-distribution processing (step S69). Next, upon completing the post-distribution processing, the NFT processing device 10 transmits a distribution notification indicating that the distribution of the NFT has been completed to the user device 30 (step S70).

[0116] Upon receiving the distribution notification, the user operates the user device 30 to access the NFT viewer and confirm the distributed NFT on the owned NFT confirmation screen 31 (see Figure 4(a)) (step S71).

[0117] If the user wishes to receive (purchase) a digital ticket (step S72: YES), the user accesses the NFT viewer on the user device 30 (step S73) and selects the ticket URL displayed in TC12, such as the description of the NFT corresponding to the digital ticket, on the NFT display screen 32 (see Figure 4(b)) (step S74).

[0118] When the ticket URL is selected, a digital ticket distribution site is accessed, and if the user wishes to receive a digital ticket, a digital ticket distribution request (including the user ID) is sent from the user device 30 to the ticket processing device 20 via the digital ticket distribution site (step S75). Note that in step S75, the digital ticket distribution request may be sent to the ticket processing device 20 via the NFT processing device 10. In this case, the NFT processing device 10 may compare the user ID with a signature (for example, signature 1).

[0119] Upon receiving the digital ticket distribution request, the ticket processing device 20 executes transaction processing related to the distribution of the digital ticket (step S76).

[0120] When the transaction process for distribution of the digital ticket is completed, the ticket processing device 20 generates a new ticket ID and generates (QR-encodes) a QR code for the ticket ID (step S77).

[0121] Next, the ticket processing device 20 transmits the digital ticket data (QR code) to the user device 30 (step S78).

[0122] Next, the ticket processing device 20 transmits the ticket ID (including the user ID) to the NFT processing device 10 (step S79).

[0123] Upon receiving the ticket ID, the NFT processing device 10 stores (registers) the ticket ID in the ticket identification data string (ticket ID) of the distribution management DB as a ticket ID corresponding to the user ID (step S80).

[0124] When the user device 30 receives the digital ticket data (step S81), the digital ticket data is stored in storage or the like of the user device 30. The stored digital ticket data is displayed as a digital ticket code image TC111 on the digital ticket display screen 33 of the NFT viewer (see FIG. 4(c)).

[0125] When the user uses the digital ticket at the ticket gate, the digital ticket is displayed on the screen of the user device 30 (step S82).

[0126] The user causes the ticket gate to scan the digital ticket displayed on the screen of the user device 30 (step S83).

[0127] When the digital ticket is scanned by the ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID and sends a matching request including the identified ticket ID to the ticket processing device 20 (step S84). Upon receiving the matching request, the ticket processing device 20 matches the ticket ID and registers the usage history (step S85), and sends the matching result to the ticket gate (step S86).

[0128] After transmitting the matching result to the ticket gate, the ticket processing device 20 transmits the usage history data to the NFT processing device 10 (step S87).

[0129] Upon receiving the usage history data, the NFT processing device 10 executes a usage history registration process (step S88).

[0130] For example, if the digital ticket is a ticket that can be used for a specified period, such as a free pass, a round-trip ticket, or a coupon ticket that can be used up to a specified upper limit, each process from step S81 to step S87 will be executed multiple times.

[0131] As described above, according to this embodiment, a user who has acquired an NFT can, if they wish, acquire a digital ticket (either for a fee or free of charge) in addition to acquiring the NFT. The user can then use the acquired digital ticket. Therefore, it is possible to add value in the form of an NFT to a ticket (or add value in the form of a ticket to an NFT), thereby motivating the user to acquire a ticket (or an NFT). Furthermore, because the behavioral history DB17 of the NFT processing device 10 stores the behavioral history of users who have acquired NFTs and tickets, it is possible to obtain marketing use data such as each user's behavioral patterns and preferences.

[0132] [Embodiment 4] Next, a fourth embodiment of the present disclosure will be described. Note that in this embodiment, differences from the third embodiment will be described, and a description of similarities will be omitted. In the third embodiment, if a user wishes to obtain a digital ticket after obtaining an NFT, the ticket processing device 20 executes processing related to obtaining the digital ticket. However, in this embodiment, if a user wishes to obtain a digital ticket during the process of obtaining an NFT, the ticket processing device 20 executes processing related to obtaining the digital ticket.

[0133] Therefore, the NFT management DB14 of this embodiment (see Figure 2(a)) includes a serial number column (No.) that stores the serial number of the NFT, a content column that stores the content to be converted into NFT (image data, video data, sound data, etc.), a metadata column that stores the metadata used when converting into NFT, etc., but does not have a ticket identification data column (ticket ID) that stores the ticket identification data of the digital ticket.

[0134] In addition, in the pre-distribution process in the NFT processing unit 11 in this embodiment, the content data of the NFT (content to be converted into NFT) to be distributed together with the digital ticket, metadata for NFT conversion, etc. are registered in the NFT management DB 14. In addition, the distribution number and distribution period are registered in the distribution management DB 15.

[0135] Furthermore, when the NFT processing unit 11 receives a ticket ID (including a user ID) from the ticket processing device 20, it stores the ticket ID in association with the user ID in the ticket identification data string (ticket ID) of the distribution management DB.

[0136] Furthermore, when a digital ticket distribution request is received from the user device 30, the ticket processing unit 21 executes transaction processing related to the distribution of the digital ticket (processing related to payment in the case of paid distribution). Then, when the transaction processing is completed, the ticket processing unit 21 generates (or registers) identification data (ticket ID) for the newly distributed digital ticket and registers it in the ticket management DB 22. The ticket processing unit 21 also generates a QR code for the generated ticket ID and transmits the generated QR code as a digital ticket to the user device 30. The ticket ID (including the user ID) is also transmitted to the NFT processing device 10.

[0137] Furthermore, the ticket URL in the metadata does not include the URL of the digital ticket distribution site (see Figure 3). Instead, between the time an NFT registration request is sent to the blockchain 40 and the time a log response is returned from the blockchain 40, a URL (or link) for accessing the digital ticket distribution site, along with a description and guidance of the digital ticket, is sent to the user device 30. A user wishing to obtain a digital ticket can obtain the digital ticket by selecting the URL.

[0138] 8 is a sequence diagram showing an example of the flow of processing according to the fourth embodiment. In this sequence, an example will be described in which 100 NFT tickets (one-day free passes within Tokyo) are distributed as digital tickets.

[0139] First, as a preparation stage, the NFT processing device 10 generates content to be converted into NFT or acquires content to be converted into NFT, and also generates metadata (step S101).

[0140] Next, the NFT processing device 10 executes pre-distribution processing (step S102). Next, when the NFT processing device 10 finishes the pre-distribution processing, it enables users to receive NFTs on an NFT distribution site or the like (for example, displays the NFT on an NFT distribution list screen) (step S103).

[0141] The user browses the NFT distribution site using the user device 30, and if the user wishes to acquire an NFT, the user sends an NFT distribution request to the NFT processing device 10 through the NFT distribution site (step S104).

[0142] Next, the NFT processing device 10 generates transaction data related to the generation of the NFT (describes the contents of the transaction) (step S105).

[0143] Next, the NFT processing device 10 transmits an NFT registration request to the blockchain 40 (step S106). In the NFT registration request, a transaction including digital signature data obtained by encrypting the transaction data with a private key and the transaction data is transmitted to the blockchain 40.

[0144] The blockchain 40 that received the transaction verifies the authenticity of the digital signature data. If the blockchain 40 confirms that the digital signature data is authentic, it distributes the NFT by executing a smart contract that registers the transaction data linked to the digital signature data in a block (step S107).

[0145] Next, following step S106, the NFT processing device 10 transmits to the user device 30 a link (URL) to the ticket distribution destination where the digital ticket will be distributed, as well as an explanation and guidance text for the digital ticket (step S108).

[0146] If the user wishes to receive (purchase) a digital ticket (step S109: YES), the user selects the link of the ticket distribution destination displayed on the screen of the user device 30 (step S110). When the link of the ticket distribution destination is selected, a digital ticket distribution request (including the user ID) is sent from the user device 30 to the ticket processing device 20 via the digital ticket distribution destination (step S111). Note that in step S111, the digital ticket distribution request may be sent to the ticket processing device 20 via the NFT processing device 10. In this case, the NFT processing device 10 may verify the user ID and a signature (for example, signature 1).

[0147] Upon receiving the digital ticket distribution request, the ticket processing device 20 executes transaction processing related to the distribution of the digital ticket (step S112).

[0148] When the transaction process for distribution of the digital ticket is completed, the ticket processing device 20 generates a new ticket ID and generates (QR-encodes) a QR code for the ticket ID (step S113).

[0149] Next, the ticket processing device 20 transmits the digital ticket data (QR code) to the user device 30 (step S114).

[0150] When the user device 30 receives the digital ticket data (step S115), the digital ticket data is stored in storage or the like of the user device 30. The stored digital ticket data is displayed as a digital ticket code image TC111 on the digital ticket display screen 33 of the NFT viewer (see FIG. 4(c)).

[0151] Next, the ticket processing device 20 transmits the ticket ID (including the user ID) to the NFT processing device 10 (step S116).

[0152] Upon receiving the ticket ID, the NFT processing device 10 stores (registers) the ticket ID in the ticket identification data string (ticket ID) of the distribution management DB as a ticket ID corresponding to the user ID (step S117).

[0153] Once verification and registration based on the transaction data is completed, the blockchain 40 returns a transaction log to the NFT processing device 10 (step S118).

[0154] Upon receiving the transaction log, the NFT processing device 10 executes post-distribution processing (step S119). Next, upon completing the post-distribution processing, the NFT processing device 10 transmits a distribution notification indicating that the distribution of the NFT has been completed to the user device 30 (step S120).

[0155] Upon receiving the distribution notification, the user operates the user device 30 to access the NFT viewer and confirm the distributed NFT on the owned NFT confirmation screen 31 (see Figure 4(a)) (step S121).

[0156] When a user who has a digital ticket (step S122: YES) uses the digital ticket at the ticket gate, the digital ticket is displayed on the screen of the user device 30 (step S123).

[0157] The user causes the ticket gate to scan the digital ticket displayed on the screen of the user device 30 (step S124).

[0158] When the digital ticket is scanned by the ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID and sends a matching request including the identified ticket ID to the ticket processing device 20 (step S125). Upon receiving the matching request, the ticket processing device 20 matches the ticket ID and registers the usage history (step S126), and sends the matching result to the ticket gate (step S127).

[0159] After transmitting the matching result to the ticket gate, the ticket processing device 20 transmits the usage history data to the NFT processing device 10 (step S128).

[0160] Upon receiving the usage history data, the NFT processing device 10 executes a usage history registration process (step S129).

[0161] For example, if the digital ticket is a ticket that can be used for a specified period, such as a one-time pass, a round-trip ticket, or a coupon that can be used up to a specified upper limit, each of the processes in steps S123 to S129 will be executed multiple times.

[0162] As described above, according to this embodiment, a user who receives an NFT can receive a digital ticket (paid or free). Furthermore, if the user who receives an NFT wishes, they can acquire a digital ticket during the NFT distribution process. The user can then use the acquired digital ticket. Therefore, since it is possible to impart added value in the form of an NFT to a ticket (or add value in the form of a ticket to an NFT), it is possible to motivate the user to acquire a ticket (or an NFT). Furthermore, since the behavioral history DB17 of the NFT processing device 10 stores the behavioral history of users who have acquired NFTs and tickets, it is possible to acquire marketing use data such as each user's behavioral patterns and preferences.

[0163] [Embodiment 5] Next, a fifth embodiment of the present disclosure will be described. Note that in this embodiment, differences from the first to fourth embodiments will be described, and a description of similarities will be omitted. In the first to fourth embodiments, users were able to receive NFTs and digital tickets. However, in this embodiment, if a user who holds a thin medium ticket wishes, the user can receive an NFT by executing a process related to acquiring an NFT on the NFT processing device 10.

[0164] Therefore, the NFT management DB14 of this embodiment (see Figure 2(a)) includes a serial number column (No.) that stores the serial number of the NFT, a content column that stores the content to be converted into NFT (image data, video data, sound data, etc.), a metadata column that stores the metadata used when converting into NFT, etc., but does not have a ticket identification data column (ticket ID) that stores the ticket identification data of the digital ticket.

[0165] Furthermore, in the pre-distribution process in the NFT processing unit 11 in this embodiment, the content data of the NFT to be distributed to the user who holds the ticket (the content to be converted into an NFT), the metadata for converting into an NFT, etc. are registered in the NFT management DB 14. In addition, the distribution number and distribution period are registered in the distribution management DB 15.

[0166] Furthermore, when the NFT processing unit 11 receives a ticket ID from the ticket processing device 20, it stores the ticket ID in the ticket identification data string (ticket ID) of the distribution management DB.

[0167] The NFT processing unit 11 also generates in advance QR image data for a QR code that is scanned by the user device 30 when the user holding the ticket receives the NFT. This QR code is a QR code that has been converted from link (URL) data for accessing the NFT distribution site. The NFT processing unit 11 then transmits this data to the ticket processing device 20 in advance.

[0168] Furthermore, the ticket processing unit 21 executes transaction processing related to the distribution of tickets when a user purchases a ticket from a ticket issuing machine (processing related to payment in the case of paid distribution). Then, when the transaction processing is completed, it generates (or registers) identification data (ticket ID) for the newly distributed ticket and registers it in the ticket management DB 22. It also generates a QR code for the generated ticket ID and sends image data of the generated QR code, the ticket ID, and QR image data received from the NFT processing unit 11 to the ticket issuing machine. The ticket issuing machine prints a QR code image of the ticket ID, the ticket ID, and a QR code image of the NFT distribution site on the ticket, issues it to the user from the ticket issuing machine, and sends a notification of issuance completion to the ticket processing unit 21. Upon receiving the notification of issuance completion, the ticket processing unit 21 sends the issued (distributed) ticket ID to the NFT processing device 10.

[0169] Therefore, two types of code images are displayed on the ticket held by the user: a QR code image of the ticket ID (first code) and a QR code image of the NFT distribution site (second code). The ticket also displays the ticket ID. When the user uses the ticket as a ticket, the QR code image of the ticket ID is scanned by a scanner. When the user acquires an NFT, the QR code image of the NFT distribution site is scanned by the user device 30. Note that a URL may be printed instead of a QR code image as a link to the NFT distribution site. In this case, the user accesses the NFT distribution site by entering this URL into a browser or the like on the user device 30. When receiving an NFT on the NFT distribution site, the user enters the ticket ID displayed on the ticket. The entered ticket ID is compared with ticket IDs stored in the distribution management DB 15 in the NFT processing device 10.

[0170] Furthermore, the ticket URL in the metadata does not include the URL of the digital ticket distribution site (see Figure 3). Instead, between the time an NFT registration request is sent to the blockchain 40 and the time a log response is returned from the blockchain 40, a URL (or link) for accessing the digital ticket distribution site, along with a description and guidance of the digital ticket, is sent to the user device 30. A user wishing to obtain a digital ticket can obtain the digital ticket by selecting the URL.

[0171] 9 is a sequence diagram showing an example of the flow of processing according to the fifth embodiment. In this sequence, an example will be described in which 100 NFT tickets (one-day free passes within Tokyo) are distributed as tickets.

[0172] First, as a preparation stage, the NFT processing device 10 generates content to be converted into NFT or acquires content to be converted into NFT, and also generates metadata (step S151).

[0173] Next, the NFT processing device 10 executes pre-distribution processing (step S152). Note that in the pre-distribution processing, QR image data of a QR code that is scanned by the user device 30 when the user holding the ticket receives the distribution of the NFT is generated. Next, when the NFT processing device 10 finishes the pre-distribution processing, it enables the user to receive the distribution of the NFT on an NFT distribution site or the like (for example, displays it on an NFT distribution list screen) (step S153).

[0174] Next, the NFT processing device 10 transmits NFT distribution destination data including QR image data for NFT distribution to the ticket processing device 20, which is used when the user holding the ticket receives the NFT (step S154).

[0175] When the ticket processing device 20 receives a notification of completion of issuance from the ticket issuing machine, it transmits the ticket ID to the NFT processing device 10 (step S155).

[0176] Upon receiving the ticket ID, the NFT processing device 10 stores (registers) the ticket ID in the ticket identification data string (ticket ID) of the distribution management DB (step S156).

[0177] When a user who holds a ticket receives an NFT, the user scans the second code printed on the ticket with the user device 30 and browses the NFT distribution site. If the user wishes to obtain an NFT, the user enters the ticket ID printed on the ticket on the NFT distribution site and sends an NFT distribution request (including the ticket ID) to the NFT processing device 10 (step S157).

[0178] Next, the NFT processing device 10 generates transaction data related to the generation of the NFT (describes the contents of the transaction) (step S158).

[0179] Next, the NFT processing device 10 transmits an NFT registration request to the blockchain 40 (step S159). In the NFT registration request, a transaction including digital signature data obtained by encrypting the transaction data with a private key and the transaction data is transmitted to the blockchain 40.

[0180] The blockchain 40 that receives the transaction verifies the authenticity of the digital signature data. If the blockchain 40 confirms that the digital signature data is authentic, it distributes the NFT by executing a smart contract that registers the transaction data linked to the digital signature data in a block (step S160).

[0181] Once verification and registration based on the transaction data is completed, the blockchain 40 returns a transaction log to the NFT processing device 10 (step S161).

[0182] Upon receiving the transaction log, the NFT processing device 10 executes post-distribution processing (step S162). Next, upon completing the post-distribution processing, the NFT processing device 10 transmits a distribution notification indicating that the distribution of the NFT has been completed to the user device 30 (step S163).

[0183] Upon receiving the distribution notification, the user operates the user device 30 to access the NFT viewer and confirm the distributed NFT on the owned NFT confirmation screen 31 (see Figure 4(a)) (step S164).

[0184] When a user holding a ticket uses the ticket at a ticket gate, the user causes the ticket gate to scan the first code on the ticket (step S165).

[0185] When the first code is scanned by the ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID and sends a matching request including the identified ticket ID to the ticket processing device 20 (step S166). Upon receiving the matching request, the ticket processing device 20 matches the ticket ID and registers the usage history (step S167), and sends the matching result to the ticket gate (step S168).

[0186] After transmitting the matching result to the ticket gate, the ticket processing device 20 transmits the usage history data to the NFT processing device 10 (step S169).

[0187] Upon receiving the usage history data, the NFT processing device 10 executes a usage history registration process (step S170).

[0188] For example, if the ticket is a ticket that can be used for a predetermined period, such as a one-time pass, a round-trip ticket, or a coupon that can be used up to a predetermined upper limit, each of the processes in steps S165 to S170 will be executed multiple times.

[0189] As described above, according to this embodiment, a user who owns a ticket can receive an NFT (paid distribution or free distribution). Furthermore, if the user who owns the ticket wishes, they can acquire a digital ticket in the process of NFT distribution. Therefore, since it is possible to impart added value in the form of an NFT to a ticket (or add value in the form of a ticket to an NFT), it is possible to motivate the user to acquire a ticket (or an NFT). Furthermore, since the behavioral history DB17 of the NFT processing device 10 stores the behavioral history of users who have acquired NFTs and tickets, it is possible to acquire marketing use data such as each user's behavioral patterns and preferences.

[0190] [Embodiment 6] Next, a sixth embodiment of the present disclosure will be described. Note that in this embodiment, differences from the fifth embodiment will be described, and a description of similarities will be omitted. In the fifth embodiment, if a user who holds a thin medium ticket wishes, the user could receive an NFT by executing a process related to acquiring an NFT on the NFT processing device 10. However, in this embodiment, if a user who holds a digital ticket wishes, the user can receive an NFT by executing a process related to acquiring an NFT on the NFT processing device 10.

[0191] Therefore, the NFT management DB14 of this embodiment (see Figure 2(a)) includes a serial number column (No.) that stores the serial number of the NFT, a content column that stores the content to be converted into NFT (image data, video data, sound data, etc.), a metadata column that stores the metadata used when converting into NFT, etc., but does not have a ticket identification data column (ticket ID) that stores the ticket identification data of the digital ticket.

[0192] In addition, in the pre-distribution process in the NFT processing unit 11 in this embodiment, the content data of the NFT to be distributed to the user who holds the digital ticket (the content to be converted into NFT), the metadata when converting into NFT, etc. are registered in the NFT management DB 14. In addition, the distribution number and distribution period are registered in the distribution management DB 15.

[0193] Furthermore, when the NFT processing unit 11 receives a ticket ID from the ticket processing device 20, it stores the ticket ID in the ticket identification data string (ticket ID) of the distribution management DB.

[0194] In addition, the NFT processing unit 11 transmits link (URL) data to the ticket processing device 20 in advance, which is used by a user who holds a digital ticket to access an NFT distribution site from the user device 30 when the user receives an NFT.

[0195] Furthermore, when a digital ticket distribution request is received from the user device 30, the ticket processing unit 21 executes transaction processing related to the distribution of the digital ticket (processing related to payment in the case of paid distribution). Then, upon completion of the transaction processing, the ticket processing unit 21 generates (or registers) identification data (ticket ID) of the newly distributed ticket and registers it in the ticket management DB 22. The ticket processing unit 21 also generates a QR code for the generated ticket ID and completes the distribution of the digital ticket by transmitting image data of the generated QR code, the ticket ID, and link (URL) data of the NFT distribution site received from the NFT processing unit 11 to the user device 30. Upon receiving the digital ticket, the user device 30 stores QR code image data of the ticket ID, ticket ID data, and link (URL) data of the NFT distribution site. Images and the like based on this data can be displayed on the screen of the user device 30. Upon completion of the distribution of the digital ticket, the ticket processing unit 21 transmits the distributed ticket ID to the NFT processing device 10.

[0196] 10 is a sequence diagram showing an example of the flow of processing according to the sixth embodiment. In this sequence, an example will be described in which 100 NFT tickets (one-day free passes within Tokyo) are distributed as tickets.

[0197] First, as a preparation stage, the NFT processing device 10 generates content to be converted into NFT or acquires content to be converted into NFT, and also generates metadata (step S171).

[0198] Next, the NFT processing device 10 executes pre-distribution processing (step S172). Note that in the pre-distribution processing, QR image data of a QR code that is scanned by the user device 30 when a user who holds a digital ticket receives an NFT is generated. Next, when the NFT processing device 10 finishes the pre-distribution processing, it enables the user to receive an NFT on an NFT distribution site or the like (for example, displays it on an NFT distribution list screen) (step S173).

[0199] The user who receives (purchases) a digital ticket browses the ticket distribution site from the user device 30 (step S174) and transmits a digital ticket distribution request through the ticket distribution site (step S175).

[0200] Upon receiving the digital ticket distribution request, the ticket processing device 20 executes transaction processing related to the distribution of the digital ticket (step S176).

[0201] When the transaction process for distribution of the digital ticket is completed, the ticket processing device 20 generates a new ticket ID and generates (QR-encodes) a QR code for the ticket ID (step S177).

[0202] Next, the ticket processing device 20 transmits the digital ticket data (QR code) to the user device 30 (step S178).

[0203] Next, the ticket processing device 20 transmits the ticket ID (including the user ID) to the NFT processing device 10 (step S179).

[0204] Upon receiving the ticket ID, the NFT processing device 10 stores (registers) the ticket ID in the ticket identification data string (ticket ID) of the distribution management DB (step S180).

[0205] When a user who holds a digital ticket receives an NFT, the user displays the digital ticket on the screen of the user device 30. The user then selects the link (URL) of the NFT distribution site displayed along with the digital ticket and browses the NFT distribution site. If the user wishes to obtain an NFT, the user enters the ticket ID displayed along with the digital ticket into the NFT distribution site and sends an NFT distribution request (including the ticket ID) to the NFT processing device 10 (step S181).

[0206] Next, the NFT processing device 10 generates transaction data related to the generation of the NFT (describes the contents of the transaction) (step S182).

[0207] Next, the NFT processing device 10 transmits an NFT registration request to the blockchain 40 (step S183). In the NFT registration request, a transaction including digital signature data obtained by encrypting the transaction data with a private key and the transaction data is transmitted to the blockchain 40.

[0208] The blockchain 40 that received the transaction verifies the authenticity of the digital signature data. If the blockchain 40 confirms that the digital signature data is authentic, it distributes the NFT by executing a smart contract that registers the transaction data linked to the digital signature data in a block (step S184).

[0209] Once verification and registration based on the transaction data is completed, the blockchain 40 returns a transaction log to the NFT processing device 10 (step S185).

[0210] Upon receiving the transaction log, the NFT processing device 10 executes post-distribution processing (step S186). Next, upon completing the post-distribution processing, the NFT processing device 10 transmits a distribution notification indicating that the distribution of the NFT has been completed to the user device 30 (step S187).

[0211] Upon receiving the distribution notification, the user operates the user device 30 to access the NFT viewer and confirm the distributed NFT on the owned NFT confirmation screen 31 (see Figure 4(a)) (step S188).

[0212] When a user who has a digital ticket uses the digital ticket at a ticket gate, the digital ticket is displayed on the screen of the user device 30 (step S189).

[0213] The user causes the ticket gate to scan the digital ticket displayed on the screen of the user device 30 (step S190).

[0214] When the digital ticket is scanned by the ticket gate, the ticket gate (or a ticket gate management server installed at the station, etc.) identifies the ticket ID and sends a matching request including the identified ticket ID to the ticket processing device 20 (step S191). Upon receiving the matching request, the ticket processing device 20 matches the ticket ID and registers the usage history (step S192), and sends the matching result to the ticket gate (step S193).

[0215] After transmitting the matching result to the ticket gate, the ticket processing device 20 transmits the usage history data to the NFT processing device 10 (step S194).

[0216] Upon receiving the usage history data, the NFT processing device 10 executes a usage history registration process (step S195).

[0217] In addition, if the ticket is a ticket that can be used for a specified period, such as a free pass, a round-trip ticket, a coupon that can be used up to a specified upper limit, or a ticket such as a key that can be used repeatedly, each of the processes in steps S189 to S195 will be executed multiple times.

[0218] As described above, according to this embodiment, a user who owns a digital ticket can receive an NFT (paid distribution or free distribution). Furthermore, if a user who owns a digital ticket wishes, they can acquire an NFT. Therefore, since it is possible to impart added value in the form of an NFT to a ticket (or add value of a ticket to an NFT), it is possible to motivate users to acquire tickets (or NFTs). Furthermore, because the behavioral history DB17 of the NFT processing device 10 stores the behavioral history of users who have acquired NFTs and tickets, it is possible to acquire marketing use data such as each user's behavioral patterns and preferences.

[0219] The technology of the present disclosure can be embodied in various forms, such as an information processing system, an information processing device, an information processing method, a program, or a recording medium. For example, a program for realizing software may be provided as a non-transitory computer-readable recording medium, or may be provided so as to be downloadable from an external server. Furthermore, the program may be provided by cloud computing, in which each program is started by an external computer (e.g., a cloud server) and the program functions are realized on each terminal. [Explanation of symbols]

[0220] 10 NFT processing device, 20 ticket processing device, 30 user device, 40 blockchain

Claims

1. Executes a distribution process for NFTs (Non-Fungible Tokens) based on a distribution request from a user; An information processing system that executes ticket distribution processing based on a ticket distribution request from a user who has received an NFT.

2. Executes ticket distribution processing based on a ticket distribution request from a user; An information processing system that executes an NFT distribution process based on a request for NFT distribution from a user who has received a ticket.

3. 3. The information processing system according to claim 1, wherein a signature is requested from the user in the ticket distribution process, and the requested signature is varied according to a predetermined level.

4. 3. The information processing system according to claim 1, wherein a signature including a contract address is requested from the user in the ticket distribution process.

5. 3. The information processing system according to claim 1, wherein a signature including a ticket use date is requested from the user in the ticket distribution process.

6. 3. The information processing system according to claim 1, wherein a signature including a password is requested from the user in the ticket distribution process.

7. 3. The information processing system according to claim 1, wherein the ticket distribution process requires the user to provide a first signature or a second signature having lower confidentiality than the first signature.

8. A procedure for executing an NFT distribution process based on a user's request for NFT distribution; A program that causes a computer to execute a procedure for executing a ticket distribution process based on a ticket distribution request from a user who has received an NFT.

9. a procedure for executing a ticket distribution process based on a ticket distribution request made by a user; A program that causes a computer to execute a procedure for executing an NFT distribution process based on a request for NFT distribution from a user who has received a ticket.

10. 1. A computer-implemented information processing method, comprising: Executing an NFT distribution process based on a user's request for NFT distribution; An information processing method including a step of executing a ticket distribution process based on a ticket distribution request from a user who has received an NFT.

11. 1. A computer-implemented information processing method, comprising: a step of executing a ticket distribution process based on a ticket distribution request from a user; An information processing method including a step of executing an NFT distribution process based on a request for NFT distribution from a user who has received a ticket.

Images