Server apparatus, control method of server apparatus, and program

Abstract

To provide a server apparatus for realizing the distribution of tickets for which purchase qualifications are set.SOLUTION: The server apparatus includes ticket sale control means and transaction control means. When a first ticket is sold to a first user, the ticket sale control means registers a first NFT ticket corresponding to the first ticket in an NFT management system. When a second user wishes to purchase the first NFT ticket, the transaction control means determines whether or not the second user is qualified to purchase the first ticket. The transaction control means allows the second user to purchase the first NFT ticket if the second user is qualified to purchase the first ticket.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a server device, a control method for a server device, and a program. [Background technology]

[0002] There is technology available that utilizes blockchain and non-fungible tokens.

[0003] For example, Patent Document 1 states that a blockchain system that allows users to contribute to society is provided. The blockchain system of Patent Document 1 includes a base cryptocurrency, at least one auxiliary currency that can be used for specific purposes, and multiple purpose-specific tokens that can be used for specific different purposes. The blockchain system of Patent Document 1 includes an auxiliary currency granting unit and a purpose-specific token granting unit. The auxiliary currency granting unit grants the auxiliary currency to the user when the user uses (consumes) the base cryptocurrency from the user terminal. The purpose-specific token granting unit grants at least one purpose-specific token to the user when the user uses the auxiliary currency from the user terminal. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2023-006292 A Summary of the Invention [Problem to be solved by the invention]

[0005] As disclosed in Patent Document 1, attempts are being made to utilize blockchain technology to solve various problems. For example, non-fungible token (NFT) tickets, which write electronic tickets to a blockchain, are becoming more widespread.

[0006] Here, the tickets purchased by users include tickets for which the purchase condition is that the user must live in a specific area, and tickets that are discounted because the user is disabled. To buy and sell (transfer) such tickets, the transferee of the ticket is required to have the same qualifications as the transferor (resident of a specific area, disabled person). However, existing ticket buying and selling systems do not take the above restrictions into consideration, and there is a problem in that a user who purchases a ticket with ticket purchase qualifications set cannot sell that ticket (legally).

[0007] A primary object of the present invention is to provide a server device, a method for controlling a server device, and a program that contribute to realizing the circulation of tickets with purchase qualifications set. [Means for solving the problem]

[0008] According to a first aspect of the present invention, a server device is provided which includes a ticket sales control means which, when a first ticket is sold to a first user, registers a first NFT (Non-Fungible Token) ticket corresponding to the first ticket in an NFT management system, and a buying and selling control means which, when a second user wishes to purchase the first NFT ticket, determines whether the second user is eligible to purchase the first ticket, and, if the second user is eligible to purchase the first ticket, allows the second user to purchase the first NFT ticket.

[0009] According to a second aspect of the present invention, a control method for a server device is provided, in which, when a first ticket is sold to a first user in a server device, a first NFT (Non-Fungible Token) ticket corresponding to the first ticket is registered in an NFT management system, and when a second user wishes to purchase the first NFT ticket, it is determined whether the second user is eligible to purchase the first ticket, and if the second user is eligible to purchase the first ticket, the second user is permitted to purchase the first NFT ticket.

[0010] According to a third aspect of the present invention, a program is provided to cause a computer mounted on a server device to execute the following processes: when a first ticket is sold to a first user, registering a first NFT (Non-Fungible Token) ticket corresponding to the first ticket in an NFT management system; and when a second user wishes to purchase the first NFT ticket, determining whether the second user is eligible to purchase the first ticket, and allowing the second user to purchase the first NFT ticket if the second user is eligible to purchase the first ticket. Effect of the Invention

[0011] According to each aspect of the present invention, a server device, a method for controlling a server device, and a program are provided that contribute to realizing the circulation of tickets for which purchase qualifications are set. Note that the effects of the present invention are not limited to those described above. The present invention may achieve other effects instead of or in addition to the effects described above. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram for explaining an overview of an embodiment. [Diagram 2] FIG. 2 is a flowchart for explaining the operation of one embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a schematic configuration of an information processing system according to the present disclosure. [Figure 4] FIG. 4 is a diagram for explaining the operation of the information processing system according to the present disclosure. [Diagram 5] FIG. 5 is a diagram for explaining the operation of the information processing system according to the present disclosure. [Figure 6] FIG. 6 is a diagram for explaining the operation of the information processing system according to the present disclosure. [Figure 7] FIG. 7 is a diagram illustrating an example of a processing configuration of the service server according to the present disclosure. [Figure 8]FIG. 8 is a diagram showing an example of a display of a terminal according to the present disclosure. [Figure 9] FIG. 9 is a flowchart showing an example of the operation of the ticket sales control unit according to the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating an example of a ticket management database according to the present disclosure. [Figure 11] FIG. 11 is a flowchart showing an example of the operation of the authentication unit according to the present disclosure. [Figure 12] FIG. 12 is a flowchart showing an example of the operation of the buying and selling control unit according to the present disclosure. [Figure 13] FIG. 13 is a diagram for explaining the operation of an information processing system according to a modification of the present disclosure. [Figure 14] FIG. 14 is a diagram illustrating an example of a hardware configuration of a service server according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] First, an outline of one embodiment will be described. The reference numerals in the drawings are added to each element for convenience as an example to aid in understanding, and the description of the outline is not intended to be limiting. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units rather than hardware units. The connection lines between the blocks in each drawing include both bidirectional and unidirectional. The unidirectional arrows are used to diagrammatically indicate the flow of the main signal (data) and do not exclude bidirectionality. In this specification and the drawings, elements that can be similarly described may be given the same reference numerals to avoid redundant description.

[0014] The server device 100 according to an embodiment includes a ticket sales control means 101 and a buying and selling control means 102 (see FIG. 1). When the ticket sales control means 101 sells a first ticket to a first user, the ticket sales control means 101 registers a first NFT ticket corresponding to the first ticket in the NFT management system (step S1 in FIG. 2). When a second user wishes to purchase the first NFT ticket, the buying and selling control means 102 determines whether the second user is qualified to purchase the first ticket (step S2). When the second user is qualified to purchase the first ticket, the buying and selling control means 102 permits the second user to purchase the first NFT ticket (step S3).

[0015] As described above, tickets purchased by users include tickets for which the purchase condition is to live in a specific area and tickets that are discounted because the user is disabled. To buy and sell such tickets, the transferee of the ticket must have the same qualifications as the transferor (a resident of a specific area, a disabled person). Thus, when an NFT ticket is bought and sold, the server device 100 determines whether or not the person who wishes to purchase the ticket is qualified to purchase the ticket, and permits users who are qualified to purchase the ticket. As a result, distribution (buying and selling) of tickets for which purchase qualifications are set is realized.

[0016] Specific embodiments will be described in more detail below with reference to the drawings.

[0017] [First embodiment] The first embodiment will be described in more detail with reference to the drawings.

[0018] [System configuration] 3 is a diagram showing an example of a schematic configuration of an information processing system according to an embodiment of the present disclosure. As shown in FIG. 3, the information processing system includes a plurality of service providers A to C.

[0019] Each service provider is a business entity that provides services to users using biometric authentication. In the information processing system disclosed in the present application, it is assumed that service providers belonging to various business types and industries provide services using biometric authentication. Note that the services provided by the service providers may be either paid or free.

[0020] For example, examples of service providers include businesses that operate means of transportation such as airplanes and railways, businesses that provide accommodation services, and businesses that provide events such as concerts. Alternatively, businesses such as retail stores are also included in the service providers disclosed in this application. In addition, service providers are not limited to private businesses. Public institutions such as local governments may also be service providers.

[0021] 3, each service provider includes a service server 10 and at least one authentication terminal 20. The devices included in the service provider (service server 10, authentication terminal 20) are connected to each other so that they can communicate with each other. Specifically, the service server 10 and the authentication terminal 20 are connected by a wired or wireless communication means.

[0022] The service server 10 is connected to a network. The service server 10 may be installed in the premises of a service provider, or may be installed on a cloud.

[0023] The service server 10 sells tickets necessary for users to receive services. The service server 10 also controls biometric authentication of users (persons to be authenticated) who wish to receive services. Each service server 10 performs biometric authentication of the person to be authenticated using biometric information.

[0024] For example, a service server 10 of an airline company sells airline tickets. The service server 10 determines whether or not a user has purchased a correct ticket (airline ticket) at check-in before boarding an aircraft. Alternatively, a service server 10 of a hotel sells rooms (reserves rooms). The service server 10 determines whether or not a user who has appeared at the hotel has made a correct reservation, and determines whether or not the user can check in.

[0025] Examples of biometric information include data (feature amounts) calculated from physical characteristics unique to an individual, such as a face, fingerprint, voiceprint, veins, retina, or iris pattern. Alternatively, the biometric information may be image data such as a face image or fingerprint image. The biometric information may be any information that includes a user's physical characteristics. In the embodiment disclosed in the present application, a case will be described in which biometric information related to a person's "face" (a face image or feature amounts generated from a face image) is used.

[0026] The authentication terminal 20 is a device that serves as an interface for users who receive services. The authentication terminal 20 is installed at the service providing location of each service provider. More specifically, the authentication terminal 20 is installed at an airport, hotel, or the like that the user actually visits.

[0027] The authentication terminal 20 has functions and forms according to the type of business of the service provider. For example, the authentication terminal 20 installed in an airport can be a kiosk terminal. Also, the authentication terminal 20 installed in a hotel can be a tablet terminal.

[0028] As shown in FIG. 3, the information processing system includes an NFT (Non-Fungible Token) management system 30.

[0029] The NFT management system 30 is a system for managing non-fungible tokens including NFT tickets, etc. The NFT management system 30 manages owners of NFTs, etc. on a blockchain (not shown in FIG. 3, etc.).

[0030] The blockchain used by the NFT management system 30 records the history of the NFTs managed by the NFT management system 30. The blockchain certifies the owner of the NFTs managed by the NFT management system 30.

[0031] Metadata related to NFTs is recorded in the blockchain. Specifically, for each NFT, an identifier, creation date and time, an owner address (user ID; for example, a wallet address) that identifies the holder, a uniform resource locator (URL) that indicates the location of an object such as an NFT ticket, etc. are stored in the blockchain as metadata. In the following description, the URL that indicates the location of an object such as an NFT ticket is referred to as a "ticket URL."

[0032] The NFT management system 30 has a function as an NFT marketplace in addition to a function for managing NFTs. The NFT marketplace realizes distribution such as purchase and sale of NFT tickets. For example, the NFT marketplace provides information on NFT tickets that are the subject of trading, and accepts requests to sell and purchase NFT tickets. Alternatively, the NFT marketplace handles settlement of the price of NFT tickets.

[0033] The NFT management system 30 has a smart contract function. A smart contract is a computer protocol for automatically executing protocols such as contracts on a blockchain. Operations such as changing the owner of an NFT are performed by the smart contract on the blockchain.

[0034] 3, a user carries a terminal 40. The user operates the terminal 40 to purchase an airline ticket, make a hotel reservation, and the like.

[0035] The devices shown in Fig. 3 are connected to each other. For example, the service server 10 and the NFT management system 30 are connected by wired or wireless communication means and configured to be able to communicate with each other.

[0036] The configuration of the information processing system shown in Fig. 3 is an example, and is not intended to be limiting. For example, each service provider may include multiple service servers 10. Also, although three service providers are illustrated in Fig. 3, it goes without saying that this is not intended to limit the number of service providers.

[0037] [General operation] Next, an outline of the operation of the information processing system according to the first embodiment will be described.

[0038] <Ticket purchase> A user who wishes to receive a service from a service provider must obtain the "right to receive the service" from the service provider. Hereinafter, the right to receive a service will be referred to as the "right to receive the service." The service provider sells a "ticket" that certifies the user's right to receive the service.

[0039] It is assumed that the user has previously opened an account in the NFT management system 30. The user has a crypto asset account with the wallet address as the user ID (account ID).

[0040] A user purchases a ticket from a service provider (step S01 in FIG. 4). The user operates the terminal 40 to access the service server 10 of the service provider from which the user wishes to enjoy the service. The user purchases a ticket on a WEB page provided by the service server 10.

[0041] When selling a ticket, the service server 10 performs identity verification of the user. Specifically, the service server 10 performs identity verification using an identification card such as a passport, a driver's license, or a My Number card.

[0042] If the identity verification is successful, the service server 10 determines whether or not the user is qualified to purchase the ticket that the user desires to purchase. In other words, the service server 10 determines whether or not the user is qualified to receive the service.

[0043] For example, if a user is trying to purchase a ticket that is only available to residents of a specific area, the service server 10 determines whether the address of the user is included in the specific area. Alternatively, if a user is trying to purchase a ticket with a discount for people with disabilities, the service server 10 determines whether the user is a person with disabilities who is eligible for the discount.

[0044] The service server 10 performs the above-mentioned determination (determination of eligibility to purchase a ticket) using a My Number card, a disability certificate, or the like obtained from the user.

[0045] The service server 10 also sells tickets for which no ticket purchase qualification is set.

[0046] The service server 10 sells tickets to users who have been successfully identified and who are qualified to purchase tickets. The service server 10 registers the ticket purchased by the user as an NFT ticket in the NFT management system 30 (step S02). Specifically, the service server 10 uploads the user ID (wallet address), biometric information (e.g., a facial image), and detailed ticket information of the user who purchased the ticket to the NFT management system 30.

[0047] The ticket detail information includes information on the service provider (for example, the name of the service provider and the address of the service server 10), the place where the service is provided, the date and time of the service, and the qualifications for purchasing the ticket.

[0048] The NFT management system 30 manages the uploaded information as an NFT ticket on the blockchain. The biometric information of the user (owner of the NFT ticket) is stored on the blockchain or other storage as the NFT ticket (metadata of the NFT ticket) together with detailed ticket information. The NFT management system 30 also transmits the token ID (transaction ID) and ticket URL issued for the NFT ticket to the service server 10 (step S03).

[0049] The service server 10 stores the token ID, ticket URL, and the like acquired from the NFT management system 30. The service server 10 stores the acquired token ID, ticket URL, and the corresponding ticket type, etc., in association with each other.

[0050] The service server 10 transmits the acquired token ID and ticket URL to the terminal 40. The terminal 40 stores the acquired token ID, etc. The terminal 40 stores the name of the purchased ticket in association with the acquired token ID and ticket URL. For example, the terminal 40 manages information about the purchased NFT ticket (token ID, ticket URL) using a digital wallet. That is, the terminal 40 may manage the NFT ticket using a digital wallet in addition to identification, electronic money, credit cards, etc.

[0051] <Provision of services> A user who has purchased a ticket (right to enjoy a service) visits a location where the service is provided. The user is authenticated by an authentication terminal 20 installed at the service providing location (for example, an airport or a hotel) (see FIG. 5).

[0052] The user (person to be authenticated) moves in front of the authentication terminal 20. The user operates the terminal 40 to present information for identifying the NFT ticket issued by the service server 10 (ticket identification information; for example, a token ID or ticket URL) to the authentication terminal 20.

[0053] Specifically, the terminal 40 converts the ticket identification information (token ID, ticket URL) into a two-dimensional barcode or the like in response to the user's operation and displays it. The user presents the terminal 40, on which the two-dimensional barcode (token ID and ticket URL corresponding to the ticket to be used) is displayed, to the authentication terminal 20.

[0054] The authentication terminal 20 acquires ticket identification information (token ID, ticket identification information) from the presented two-dimensional barcode. The authentication terminal 20 also captures an image of the user (person to be authenticated) in front of it to acquire biometric information (for example, a face image).

[0055] The authentication terminal 20 transmits an authentication request including the acquired ticket-specific information and biometric information to the service server 10 (step S11).

[0056] The service server 10 acquires the NFT ticket from the NFT management system 30 using the ticket identification information (token ID, ticket URL) included in the authentication request (step S12). For example, the service server 10 acquires the NFT ticket by transmitting the token ID to the NFT management system 30. Alternatively, the service server 10 acquires the NFT ticket by accessing the ticket URL.

[0057] The service server 10 performs biometric authentication using the biometric information included in the NFT ticket (biometric information of the ticket owner) and the biometric information included in the authentication request (biometric information of the person to be authenticated who appears at the service providing location).

[0058] If the biometric authentication is successful, the service server 10 verifies the validity of the ticket. Specifically, the service server 10 determines the validity of the ticket by using the ticket detail information included in the NFT ticket.

[0059] For example, the service server 10 verifies the validity of the ticket (airline ticket) by comparing the flight departure date and time with the authentication date and time, or verifies the validity of the ticket using the scheduled hotel check-in date and the authentication date and time.

[0060] If the biometric authentication is successful and the ticket is valid, the service server 10 determines that the authentication of the authenticated person has succeeded. The service server 10 notifies the authentication result (authentication success, authentication failure) to the authentication terminal 20 (step S13). The authentication terminal 20 provides services to the authenticated person who has succeeded in biometric authentication.

[0061] <Transfer of NFT Ticket> The user can transfer the purchased NFT ticket (service enjoyment right) to others. That is, the user can sell the right to receive the service held by himself / herself.

[0062] The user (ticket owner) can sell the NFT ticket in the NFT marketplace provided by the NFT management system 30. The user (transferor of the ticket) specifies the ticket (token ID) to be sold in the NFT marketplace and inputs conditions such as the desired selling price to the NFT marketplace (step S21 in FIG. 6).

[0063] The NFT management system 30 identifies the NFT ticket to be sold based on the token ID. The NFT management system 30 publishes the identified NFT ticket (publishes it as the NFT ticket for sale). At that time, the NFT management system 30 publishes the ticket detailed information of the NFT ticket (service provider, service providing location, service providing date and time, ticket purchase eligibility, etc.).

[0064] With reference to the published information, the user (assignee) considers purchasing the NFT ticket. The user who has decided to purchase the NFT ticket operates the terminal 40 and applies to the NFT management system 30 for ticket purchase (step S22). That is, the person who wishes to purchase the ticket indicates the intention to purchase the NFT ticket under the conditions published in the NFT marketplace.

[0065] After that, the NFT management system 30 connects the ticket purchaser and the service provider. The NFT management system 30 enables communication between the ticket purchaser's terminal 40 and the service provider's service server 10. At that time, the NFT management system 30 notifies the service server 10 of the token ID of the NFT ticket to be sold via the user's terminal 40.

[0066] For example, the NFT management system 30 displays a URL (Uniform Resource Locator) with an embedded token ID on the terminal 40 of the person wishing to purchase a ticket. When the person wishing to purchase a ticket clicks on the URL, the terminal 40 accesses the service server 10. Alternatively, the NFT management system 30 may notify the terminal 40 of the address of the service server 10 and instruct it to connect to the service server 10. The terminal 40 may access the service server 10 in accordance with the instruction and notify the service server 10 of the token ID of the NFT ticket to be traded.

[0067] The service server 10, which is now able to communicate with the terminal 40, determines whether the person wishing to purchase a ticket is able to purchase a ticket. Specifically, the service server 10 performs the same ticket sales procedure (identification, ticket purchase qualification determination) as when the ticket to be sold was initially sold.

[0068] If the identity verification of the ticket buyer and the determination of the ticket purchase eligibility are successful, the service server 10 approves the sale of the NFT ticket to that ticket buyer. The service server 10 notifies the NFT management system 30 (NFT marketplace) that a sale has been completed between the owner of the NFT ticket and the person wishing to purchase the NFT ticket.

[0069] Specifically, the service server 10 sends an "owner change instruction" including the token ID of the NFT ticket for which the sale has been completed, the user ID and biometric information of the new ticket owner to the NFT management system 30 (step S23).

[0070] The NFT management system 30 identifies the NFT ticket for which the sale has been completed based on the token ID. The NFT management system 30 sets the user ID and biometric information notified by the service server 10 as the information of the new ticket owner and issues an NFT ticket. At that time, the NFT management system 30 sets the ticket detailed information of the transferred NFT ticket as the ticket detailed information of the new NFT ticket. The NFT management system 30 transmits a new token ID and ticket URL corresponding to the new NFT ticket to the service server 10 (step S24).

[0071] Note that the NFT management system 30 invalidates the old NFT ticket corresponding to the transferred ticket. For example, the NFT management system 30 invalidates the old NFT ticket by deleting the owner information (user ID) of the old NFT ticket.

[0072] The service server 10 stores the received new token ID and the like, and transmits the token ID and ticket URL to the terminal 40 of the new ticket owner.

[0073] If identity verification of the ticket buyer fails or if the ticket buyer does not have the qualifications to purchase a ticket, the service server 10 sends a "notice of non-sale" including the token ID of the NFT ticket that is the subject of sale to the NFT management system 30. In this case, the NFT management system 30 notifies the ticket buyer via the terminal 40 that the ticket cannot be purchased.

[0074] When the owner of an NFT ticket changes, the NFT management system 30 performs settlement processing for the sale and purchase of the NFT ticket. The NFT management system 30 settles the price agreed upon between the transferor (old ticket owner) and the transferee (new ticket owner). The NFT management system 30 transfers cryptocurrency corresponding to the purchase and sale amount from the transferee's cryptocurrency account to the transferor's cryptocurrency account.

[0075] The new ticket owner can use the NFT ticket in the same way as the old ticket owner. The new ticket owner simply operates the terminal 40 to present the ticket identification information (token ID, ticket URL) received from the service server 10 to the authentication terminal 20.

[0076] Next, each device included in the information processing system according to the first embodiment will be described in detail.

[0077] [Service Server] 7 is a diagram showing an example of a processing configuration (processing module) of the service server 10 according to the embodiment of the present disclosure. Referring to FIG. 7, the service server 10 includes a communication control unit 201, a ticket sales control unit 202, an authentication unit 203, a buying and selling control unit 204, and a storage unit 205.

[0078] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the NFT management system 30. The communication control unit 201 also transmits data to the NFT management system 30. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, the other processing modules transmit and receive data to and from other devices via the communication control unit 201. The communication control unit 201 has a function as a receiver that receives data from other devices and a function as a transmitter that transmits data to other devices.

[0079] The ticket sales control unit 202 is a means for controlling ticket sales. When the ticket sales control unit 202 sells a first ticket to a first user, it registers a first NFT ticket corresponding to the first ticket in the NFT management system 30. At that time, the ticket sales control unit 202 registers in the NFT management system 30 the first NFT ticket in which the biometric information of the first user is the biometric information of the owner of the first ticket.

[0080] When a user operates the terminal 40 to access the ticket sales page, the ticket sales control unit 202 sells the ticket on the ticket sales page. When selling a ticket that requires a certain qualification to purchase, the ticket sales control unit 202 clearly displays the necessary qualification information on the ticket sales page. For example, the ticket sales control unit 202 displays a GUI (Graphical User Interface) such as that shown in FIG. 8 on the terminal 40.

[0081] When selling a ticket, the ticket sales control unit 202 acquires information about the ticket purchaser. For example, the ticket sales control unit 202 acquires the wallet address (user ID of the cryptocurrency account) of the ticket purchaser.

[0082] Hereinafter, the operation of the ticket sales control unit 202 will be described with reference to FIG.

[0083] When a user decides to purchase a ticket (when the purchase button shown in FIG. 8 is pressed), the ticket sales control unit 202 performs identity verification of the user (step S101).

[0084] Specifically, the ticket sales control unit 202 displays a GUI on the terminal 40 and acquires the user's identification card. The ticket sales control unit 202 acquires a copy of an identification card (image data showing the identification card) on which biometric information is written, such as a passport, a driver's license, or a My Number card.

[0085] After that, the ticket sales control unit 202 acquires biometric information (e.g., a face image) of the user. For example, the ticket sales control unit 202 instructs the user to take a so-called selfie via the terminal 40 to acquire the biometric information of the ticket purchaser.

[0086] The ticket sales control unit 202 extracts biometric information (face image) from image data showing the identification card. The ticket sales control unit 202 generates feature amounts from the extracted face image.

[0087] Since existing technology can be used for the feature generation process by the ticket sales control unit 202, detailed description thereof will be omitted. For example, the ticket sales control unit 202 extracts the eyes, nose, mouth, etc. as feature points from a face image. After that, the ticket sales control unit 202 calculates the position of each feature point and the distance between each feature point as feature amounts (generates a feature vector consisting of multiple feature amounts).

[0088] The ticket sales control unit 202 also generates feature quantities from a facial image obtained by photographing the user.

[0089] The ticket sales control unit 202 executes one-to-one authentication using features obtained from the biometric information on the identification card and features obtained from the face image of the user.

[0090] The ticket sales control unit 202 calculates the similarity between the two feature quantities. The similarity can be calculated using chi-square distance, Euclidean distance, etc. The greater the distance, the lower the similarity, and the closer the distance, the higher the similarity.

[0091] The ticket sales control unit 202 determines that identity verification has been successful if the similarity is equal to or greater than a predetermined value, and determines that identity verification has failed if the similarity is smaller than the predetermined value.

[0092] If the identity verification fails (step S102, No branch), the ticket sales control unit 202 determines that the ticket cannot be sold. In this case, the ticket sales control unit 202 notifies the user that the ticket cannot be sold, and ends the process.

[0093] If the identity verification is successful (step S102, Yes branch), the ticket sales control unit 202 determines whether the user is eligible to purchase a ticket if purchase eligibility is set for the ticket that the user has decided to purchase (ticket purchase eligibility determination; step S103).

[0094] For example, if a user selects a ticket that requires address verification, the ticket sales control unit 202 determines whether the user is eligible to purchase the ticket using the address obtained from the identification card acquired during identity verification.

[0095] Alternatively, the ticket sales control unit 202 acquires information (documents) from the user as necessary to determine whether or not the user is qualified to purchase a ticket. For example, if the user selects a ticket that can only be purchased by disabled people, the ticket sales control unit 202 acquires a copy of the disability certificate (image data showing the disability certificate) using a GUI. The ticket sales control unit 202 reads out the level of disability, etc. from the image data showing the disability certificate using OCR (Optical Character Recognition) technology. The ticket sales control unit 202 uses the read-out level, etc. to determine whether or not the user is qualified to purchase a ticket.

[0096] If the user does not have the qualifications to purchase a ticket (step S104, No branch), the ticket sales control unit 202 determines that the ticket cannot be sold. In this case, the ticket sales control unit 202 notifies the user that the ticket cannot be sold, and ends the process.

[0097] If the user is eligible to purchase a ticket (step S104, Yes branch), the ticket sales control unit 202 sells the ticket selected by the user to the user. Specifically, the ticket sales control unit 202 performs settlement processing for the sold ticket. At that time, the ticket sales control unit 202 bills the user for the price after applying a disability discount, etc. Alternatively, the ticket sales control unit 202 applies for a disability discount, etc. to a local government, etc., and bills the user for the price after applying for a disability discount, etc.

[0098] If a user selects a ticket for which no ticket purchase qualification is set, the ticket sales control unit 202 determines that the user unconditionally has ticket purchase qualification.

[0099] When the payment for the ticket sold to the user is completed, the ticket sales control unit 202 registers the ticket purchased by the user as an NFT ticket in the NFT management system 30 (step S105). Specifically, the ticket sales control unit 202 uploads the user's user ID (cryptocurrency account user ID; wallet address), biometric information (for example, a face image obtained from an identification card or a selfie), and detailed ticket information to the NFT management system 30.

[0100] The ticket sales control unit 202 receives the token ID (transaction ID) of the NFT ticket, the ticket URL, etc. from the NFT management system 30. The ticket sales control unit 202 transmits the acquired token ID, ticket URL, etc. to the user terminal 40 (step S106).

[0101] The ticket sales control unit 202 also stores the token ID, ticket URL, etc. acquired from the NFT management system 30. The ticket sales control unit 202 associates the acquired token ID, etc. with the corresponding ticket type and stores them in the ticket management database (see FIG. 10). Note that the ticket management database shown in FIG. 10 is merely an example, and is not intended to limit the items to be stored.

[0102] Note that detailed descriptions of individual ticket sales, such as airline ticket sales and hotel reservations, will be omitted because details regarding individual tickets are outside the scope of the present disclosure.

[0103] In this way, the ticket sales control unit 202 acquires the identification card of the first user, and if identity verification using the identification card is successful and the first user is eligible to purchase the first ticket, sells the first ticket to the first user. Furthermore, the ticket sales control unit 202 transmits information for identifying the first NFT ticket (token ID, ticket ULR) issued by registering the first NFT ticket in the NFT management system 30 to the terminal 40 possessed by the first user.

[0104] The authentication unit 203 is a means for authenticating the person to be authenticated. Specifically, the authentication unit 203 processes an authentication request received from the authentication terminal 20.

[0105] The operation of authentication unit 203 will be described with reference to FIG.

[0106] When the authentication unit 203 receives an authentication request from the authentication terminal 20, it acquires an NFT ticket corresponding to the ticket identification information using the ticket identification information (token ID, ticket URL) included in the authentication request (step S201). For example, the authentication unit 203 acquires the NFT ticket corresponding to the token ID by transmitting the token ID to the NFT management system 30.

[0107] Upon acquiring the NFT ticket, the authentication unit 203 performs biometric authentication using the biometric information contained in the NFT ticket (biometric information of the ticket owner) and the biometric information contained in the authentication request (biometric information of the person to be authenticated who appears at the service provision location) (step S202).

[0108] Specifically, the authentication unit 203 generates features from each of the two pieces of biometric information (face images). The authentication unit 203 calculates the similarity between the two features. If the calculated similarity is equal to or greater than a predetermined value, the authentication unit 203 determines that the authentication is successful. If the calculated similarity is smaller than the predetermined value, the authentication unit 203 determines that the authentication is unsuccessful.

[0109] If the biometric authentication fails (step S203, No branch), the authentication unit 203 sets the authentication result to "authentication failure" (step S204).

[0110] If the biometric authentication is successful (step S203, Yes branch), the authentication unit 203 verifies the validity of the ticket (step S205). Specifically, the authentication unit 203 determines the validity of the ticket using the ticket detail information included in the NFT ticket.

[0111] For example, the authentication unit 203 included in the hotel service server 10 determines the validity of the ticket using the planned check-in date and authentication date and time written in the ticket details information. Specifically, if the authentication date and time is after the possible check-in time on the planned check-in date and the NFT ticket is not used or invalid, the authentication unit 203 determines that the ticket is valid.

[0112] Note that detailed explanations regarding the determination of the validity of various tickets will be omitted, as details regarding the determination of the validity of individual tickets are outside the scope of the present disclosure.

[0113] If the ticket is invalid (step S206, No branch), the authentication unit 203 sets the authentication result to "authentication failed" (step S204).

[0114] If the ticket is valid (step S206, Yes branch), the authentication unit 203 sets the authentication result to "authentication successful" (step S207).

[0115] The authentication unit 203 transmits the authentication result (authentication success, authentication failure) to the authentication terminal 20 (step S208). If the authentication is successful, the authentication unit 203 transmits an affirmative response indicating that to the authentication terminal 20. If the authentication is unsuccessful, the authentication unit 203 transmits a negative response indicating that to the authentication terminal 20.

[0116] If authentication of the person to be authenticated is successful, the authentication unit 203 notifies the NFT management system 30 that the NFT ticket has been used, as necessary. Specifically, the authentication unit 203 notifies the NFT management system 30 of a "ticket used notification" including the token ID of the NFT ticket. In response to receiving the notification, the NFT management system 30 sets the NFT ticket corresponding to the token ID to "used." For example, the NFT management system 30 sets the NFT ticket to "used" by writing "used" in the ticket details information or by erasing the owner's information.

[0117] In this way, the authentication unit 203 receives an authentication request including information for identifying the first NFT ticket and biometric information of the person to be authenticated from the authentication terminal 20. The authentication unit 203 acquires the first NFT ticket from the NFT management system 30 based on the information for identifying the first NFT ticket included in the authentication request. The authentication unit 203 performs biometric authentication using the biometric information included in the first NFT ticket and the biometric information included in the authentication request. If the biometric authentication (one-to-one authentication) is successful and the ticket is valid, the authentication unit 20 notifies the authentication terminal 20 of successful authentication.

[0118] The buying and selling control unit 204 is a means for executing control regarding the buying and selling of NFT tickets.

[0119] When a second user wishes to purchase a first NFT ticket, the buying and selling control unit 204 determines whether or not the second user is qualified to purchase the first ticket. When the second user is qualified to purchase the first ticket, the buying and selling control unit 204 permits the second user to purchase the first NFT ticket. When the buying and selling control unit 204 permits the second user to purchase the first NFT ticket, it registers a second NFT ticket in the NFT management system 30, in which the biometric information of the second user is the biometric information of the owner of the first ticket.

[0120] The operation of the buying and selling control unit 204 will be described with reference to FIG.

[0121] The buying and selling control unit 204 acquires the token ID of the NFT ticket being bought and sold from the terminal 40 held by the person who wishes to purchase the NFT ticket.

[0122] The buying and selling control unit 204 identifies the type of ticket that is the subject of buying and selling based on the received token ID. Specifically, the buying and selling control unit 204 searches the ticket management database using the received token ID as a key, and identifies the type of ticket that corresponds to the received token ID.

[0123] After that, the buying and selling control unit 204 obtains an identification card from the person who wishes to purchase a ticket and performs identity verification (step S301). Note that the identity verification process of the buying and selling control unit 204 can be the same as the identity verification process of the ticket sales control unit 202, so a detailed description thereof will be omitted.

[0124] If identity verification fails (step S302, No branch), the buying and selling control unit 204 sets the buying and selling of the NFT ticket to be denied (step S303).

[0125] If the identity verification is successful (step S302, Yes branch), the buying and selling control unit 204 judges whether the person who wishes to purchase a ticket is qualified to purchase a ticket (step S304). Note that the ticket purchase qualification judgment process of the buying and selling control unit 204 can be the same as the ticket purchase qualification judgment process of the ticket selling control unit 202, so a detailed description will be omitted.

[0126] In addition, if the NFT ticket being traded does not have ticket purchase qualifications set, the trading control unit 204 may determine that the person wishing to purchase the ticket is qualified to purchase the ticket.

[0127] If the ticket purchaser does not have the qualifications to purchase an NFT ticket (step S305, No branch), the buying and selling control unit 204 sets the buying and selling of the NFT ticket to be denied (step S303).

[0128] If the ticket purchaser is qualified to purchase an NFT ticket (step S305, Yes branch), the buying and selling control unit 204 sets the buying and selling of the NFT ticket to approved (step S306).

[0129] Once the decision as to whether the NFT ticket can be bought or sold (whether the buy and sell is approved or rejected) is determined, the buy and sell control unit 204 issues instructions and notifications to the NFT management system 30 according to the determined result (instructions to the system; step S307).

[0130] When approving the sale and purchase of the NFT ticket, the sale and purchase control unit 204 instructs the NFT management system 30 to change the owner of the NFT ticket. Specifically, the sale and purchase control unit 204 sends to the NFT management system 30 an "owner change instruction" that includes the token ID of the NFT ticket for which the sale and purchase has been completed, and the user ID and biometric information of the new ticket owner.

[0131] In response to sending the owner change instruction, the buying and selling control unit 204 receives the token ID, ticket URL, etc. corresponding to the NFT ticket whose owner has changed. The buying and selling control unit 204 stores the received token ID, etc. in the ticket management database. Furthermore, the buying and selling control unit 204 transmits the received token ID, etc. to the terminal 40 of the person wishing to purchase the ticket (transferee).

[0132] If the sale or purchase of the NFT ticket is denied, the sale and purchase control unit 204 notifies the NFT management system 30 of that effect. Specifically, the sale and purchase control unit 204 sends a "sale and purchase denial notice" to the NFT management system 30, which includes the token ID of the NFT ticket that is the subject of the sale or purchase.

[0133] In this way, if the buying and selling control unit 204 succeeds in verifying the identity of the second user and the second user is eligible to purchase the first ticket, the buying and selling control unit 204 permits the second user to purchase the first NFT ticket. Furthermore, the buying and selling control unit 204 transmits information for identifying the second NFT ticket, which is issued by registering the second NFT ticket in the NFT management system 30, to the terminal 40 possessed by the second user.

[0134] The storage unit 205 is a means for storing information necessary for the operation of the service server 10. For example, the storage unit 205 stores types of tickets and corresponding ticket purchasing qualifications in association with each other.

[0135] [Authentication device] Description of the configuration and operation of the authentication terminal 20 will be omitted, as the configuration and operation of the authentication terminal 20 will be clear to those skilled in the art. The authentication terminal 20 acquires ticket-specific information and biometric information from the person to be authenticated, and transmits an authentication request including this information to the service server 10. The authentication terminal 20 may execute processing according to the response (positive response, negative response) received from the service server 10. When a positive response (authentication success) is received, the authentication terminal 20 may provide a service to the person to be authenticated.

[0136] [NFT Management System] Explanation of the configuration and operation of the NFT management system 30 will be omitted because the configuration and operation of the NFT management system 30 are obvious to those skilled in the art. The NFT management system 30 is realized by implementing the functions described above in an existing system that manages NFT tickets, etc.

[0137] Specifically, when a buyer appears for an NFT ticket put up for sale on the NFT marketplace, the NFT management system 30 connects the buyer's terminal 40 to the service server 10 of the service provider who sold the NFT ticket.

[0138] Alternatively, when the NFT management system 30 receives an owner change instruction from the service server 10, it can issue a new NFT ticket with a changed owner using the new user ID and biometric information included in the instruction. Furthermore, when the NFT management system 30 receives a "sale and purchase not possible notice" from the service server 10, it can notify the person who wishes to purchase the ticket that the ticket cannot be purchased.

[0139] Alternatively, when the NFT management system 30 receives a ticket used notification, it can set the NFT ticket corresponding to the token ID included in the notification to "used."

[0140] [Device] Examples of the terminal 40 include a smartphone, a mobile phone, a game machine, a mobile terminal device such as a tablet, a computer (personal computer, notebook computer), etc. The terminal 40 can be any equipment or device that can accept user operations and communicate with the service server 10, etc. Also, since the configuration of the terminal 40 is clear to those skilled in the art, detailed explanations will be omitted.

[0141] Next, a modification of the first embodiment will be described.

[0142] <Variation 1> In the above embodiment, it has been described that identity verification of the transferee (person wishing to purchase the ticket) is performed when buying and selling an NFT ticket. When buying and selling an NFT ticket, the service server 10 may perform identity verification of the transferor (owner) of the NFT ticket.

[0143] Specifically, when a person wishing to purchase an NFT ticket appears, the buying and selling control unit 204 of the service server 10 requests the ticket owner's terminal 40 to submit an identification document. After successfully verifying the identity of the ticket owner, the buying and selling control unit 204 may then perform identity verification of the person wishing to purchase the ticket.

[0144] Such operation of the service server 10 prevents a third party other than the NFT ticket owner from impersonating the owner and reselling the ticket.

[0145] <Variation 2> The service server 10 may use so-called liveness authentication when performing biometric authentication of a user. By using liveness authentication, the service server 10 prevents fraud (impersonation) using photographs, etc. In other words, the service server 10 can perform more reliable authentication (identification) by using liveness authentication.

[0146] <Variation 3> In the above embodiment, the explanation has been given on the assumption that the service provider handles one ticket (service enjoyment right). However, the system may include a service provider that handles multiple tickets.

[0147] For example, the information processing system may include a service provider such as a travel agency that makes all-in-one arrangements for transportation, accommodation, etc. For example, as shown in FIG. 13, a travel agency may be included in the system.

[0148] In this case, the user inputs the user's home address, desired sightseeing spots, itinerary, etc. to the travel agency's service server 10. The service server 10 generates a travel plan that matches the user's requests. The service server 10 determines the travel route and arranges the necessary tickets (for transportation, accommodation, sightseeing spots, etc.).

[0149] The travel agency service server 10 sells the right to travel according to the generated itinerary to the user. The right to travel includes the right to board an airplane, the right to stay in a hotel, the right to enter a tourist spot, etc.

[0150] Specifically, the service server 10 of the travel agency acquires a travel route by requesting a route search from a service provider that performs route search. The service server 10 of the travel agency acquires a travel route by inputting a departure point, a destination, a schedule, etc., into the service server 10 of the route calculation business.

[0151] Once the travel route is acquired, the travel agency service server 10 arranges for the tickets necessary to realize the travel plan. The travel agency service server 10 purchases the tickets from each service provider such as an airline, a railway company, a hotel, etc.

[0152] In this case, when the travel agency service server 10 has completed the identity verification of the user, it requests each service provider to sell the most suitable ticket for the user while providing the information obtained from the identification card (e.g., My Number card) used for the identity verification to each service provider. Alternatively, when the user has a disability certificate, the travel agency service server 10 requests each service provider to sell the most suitable ticket while providing the information obtained from the disability certificate to each service provider.

[0153] The requested service provider selects the most suitable ticket for the user while taking into consideration discounts and other factors set by the local government, etc. The service provider may select the most suitable ticket for the user using a learning model obtained by machine learning, etc. Each service provider transmits information and price of the selected ticket to the service server 10 of the travel agency.

[0154] In this way, if there is a discount or the like that can be applied to the user using information obtained from the identification card (e.g., My Number card) or disability certificate presented by the user, each service provider sells the ticket (service enjoyment right) to which the discount has been applied. Alternatively, the service server 10 of each service provider may automatically apply for subsidies or the like to the local government before or after the trip, and charge the user the ticket price after deducting the subsidy.

[0155] When a user agrees to (indicates intention to purchase) a travel plan including tickets (ticket fees) acquired from each service provider, the travel agency's service server 10 sells the right to travel according to that travel plan to the user. In other words, the travel agency's service server 10 sells to the user a "service right" consisting of multiple service rights such as airline tickets, hotel accommodation, and tickets to tourist spots.

[0156] In this case, the travel agency's service server 10 (ticket sales control unit 202) registers the user's biometric information, detailed ticket information regarding multiple tickets, and an NFT ticket including ticket purchase qualifications in the NFT management system 30.

[0157] By presenting the ticket identification information (token ID, ticket URL) to each service provider at the travel destination, the user can receive services from each service provider.

[0158] In this way, the ticket sales control unit 202 sells to the first user a second ticket that is necessary to receive services from each of a plurality of service providers and that consists of a plurality of tickets corresponding to each of the plurality of service providers. Upon selling the second ticket to the first user, the ticket sales control unit 202 registers in the NFT management system 30 a third NFT ticket that uses the biometric information of the first user as the biometric information of the owner of the second ticket.

[0159] Furthermore, a user can also transfer a service right consisting of multiple service rights (tickets) (for example, the right to travel according to a travel plan created by a travel agency) to another person.

[0160] In this case, the NFT management system 30, as described above, connects the travel agency's service server 10 and the terminal 40 of the person wishing to purchase a ticket. The travel agency's service server 10 performs identity verification of the person wishing to purchase a ticket. Furthermore, the service server 10 determines whether the person wishing to purchase a ticket is eligible to receive discounts and the like from each service provider.

[0161] Specifically, the travel agency's service server 10 transmits the ticket purchaser's identification (e.g., My Number card information), disability certificate, ticket type, etc. to the service server 10 of each service provider, and requests a determination regarding the ticket purchase eligibility.

[0162] The service server 10 of each service provider determines whether or not the ticket purchaser is qualified to purchase a ticket based on the acquired information (information obtained from the My Number card or the disability certificate) and the type of ticket.

[0163] If the travel agency's service server 10 receives "not eligible to purchase tickets" from at least one of the multiple service providers, it determines that the ticket purchaser cannot purchase a ticket (e.g., the right to travel according to the generated travel plan). In this case, the travel agency's service server 10 sends a sale and purchase ineligibility notice to the NFT management system 30.

[0164] When "eligible to purchase tickets" is obtained from each service provider, the travel agency's service server 10 determines that the ticket purchaser can purchase a ticket (the right to travel). In this case, the travel agency's service server 10 sends an owner change notification to the NFT management system 30.

[0165] In this way, when the second user wishes to purchase a third NFT ticket, the buying and selling control unit 204 determines whether or not the second user is qualified to purchase each of the multiple tickets included in the second ticket. If the second user is qualified to purchase each of the multiple tickets, the buying and selling control unit 204 permits the second user to purchase the third NFT ticket.

[0166] As described above, the information processing system may include a service provider that sells a single ticket (a single service right) consisting of multiple service rights to a user. For example, a travel agency automatically generates a travel plan according to the user's wishes, and automatically arranges tickets, etc. to which the discounts available to the user are applied. At that time, each service provider automatically calculates fees that reflect subsidies, etc., and applies to local governments, etc. The user can enjoy a comfortable trip by operating the terminal 40 and presenting the NFT ticket to a service provider (airport, hotel, etc.) at the travel destination. In other words, the traveler does not need to access the service provider's web page or enter an ID, etc., on the web page during the trip.

[0167] As described above, the service server 10 according to the first embodiment registers the ticket purchased by the user as an NFT ticket in the blockchain (NFT management system 30). Registering the ticket as an NFT prevents tampering with the ticket.

[0168] Furthermore, when a ticket purchaser attempts to purchase a ticket with a set purchase qualification, the service server 10 determines whether the ticket purchaser has the ticket purchase qualification. The service server 10 permits ticket purchase (buying and selling of NFT tickets) only to users with the ticket purchase qualification. As a result, circulation (legitimate buying and selling) of tickets with purchase qualification set is realized. Furthermore, a user who cannot use a ticket (cannot receive the service) for some reason can sell the ticket he / she owns on the NFT marketplace, so the user does not need to pay a cancellation fee to the service provider. In other words, even if a user cancels a trip or the like, the user can transfer the purchased ticket to another person. The user can sell the purchased ticket (service enjoyment right) for a higher amount than the cancellation fee paid to each service provider.

[0169] Furthermore, the service server 10 performs identity verification of the person who wishes to purchase a ticket and determines the eligibility to purchase a ticket, thereby preventing fraudulent transactions (fraudulent resale) such as impersonation.

[0170] Furthermore, the service server 10 registers an NFT ticket in the NFT management system 30, which has the ticket purchaser's biometric information as the ticket owner's biometric information. Since the ticket owner's biometric information is set in the NFT ticket, the service provider can perform authentication using that biometric information. As a result, the service provider can confirm that the owner of the NFT ticket and the person to be authenticated (the user who wishes to receive the service) are the same person. In this regard, since that authentication is performed even when the NFT ticket is transferred, fraudulent transactions such as buying and selling tickets without changing the ticket owner's name are prevented.

[0171] Next, the hardware of each device constituting the information processing system will be described.

[0172] The service server 10 can be configured by an information processing device (so-called a computer), and has the configuration exemplified in Fig. 14. For example, the service server 10 has a processor 311, a memory 312, an input / output interface 313, a communication interface 314, etc. The components such as the processor 311 are connected by an internal bus or the like, and are configured to be able to communicate with each other.

[0173] However, the configuration shown in Fig. 14 is not intended to limit the hardware configuration of the service server 10. The service server 10 may include hardware not shown, and may not include the input / output interface 313 as necessary. Furthermore, the number of processors 311 and the like included in the service server 10 is not intended to be limited to the example shown in Fig. 14, and for example, the service server 10 may include multiple processors 311.

[0174] The processor 311 is, for example, a programmable device such as a central processing unit (CPU), a micro processing unit (MPU), or a digital signal processor (DSP). Alternatively, the processor 311 may be a device such as a field programmable gate array (FPGA), or an application specific integrated circuit (ASIC). The processor 311 executes various programs including an operating system (OS).

[0175] The memory 312 is a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), a solid state drive (SSD), etc. The memory 312 stores an OS program, application programs, and various data.

[0176] The input / output interface 313 is an interface for a display device and an input device (not shown). The display device is, for example, a liquid crystal display, etc. The input device is, for example, a keyboard, a mouse, etc. that accepts user operations.

[0177] The communication interface 314 is a circuit, a module, etc. that communicates with other devices. For example, the communication interface 314 includes a network interface card (NIC).

[0178] The functions of the service server 10 are realized by various processing modules. The processing modules are realized, for example, by the processor 311 executing a program stored in the memory 312. The program can be recorded in a computer-readable storage medium. The storage medium can be a non-transitory medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. That is, the present invention can also be embodied as a computer program product. The program can be downloaded via a network, or updated using a storage medium storing the program. The processing modules may also be realized by a semiconductor chip.

[0179] The service server 10, which is an information processing device, is equipped with a computer, and the computer executes a program to realize the functions of the service server 10. The service server 10 also executes a control method for the service server 10 by the program.

[0180] [Variations] The configuration, operation, etc. of the information processing system described in the above embodiment are merely examples, and are not intended to limit the system configuration, etc.

[0181] The information processing system described above may provide services not only for domestic users (residents) but also for foreign users (inbound passengers). That is, the information processing system may provide off-airport services for inbound passengers using NFT. In this case, the foreign user makes reservations for airline tickets and hotels in his / her own country. After that, when the user boards an aircraft and arrives in the territory of Japan, the biometric information is registered in the NFT management system 30. That is, the foreign user registers biometric information (opts in to the use of biometric information) in Japan. In this way, the purchase of tickets and the registration of biometric information may be separate procedures. In addition, by applying (purchasing the service) in advance, the foreign user can complete the procedures for delivering a suitcase from the airport to the hotel and the check-in procedures at the hotel or airport by biometric authentication. That is, the foreign user does not need to present a passport or the like to a staff member or the like. Alternatively, the user (foreign user, Japanese user) can complete the procedures and payments when using public transportation by biometric authentication. In addition, since strict identification of users is completed by biometric authentication, users can enjoy special treatment such as the use of dedicated gates or priority gates. Alternatively, users can receive services using biometric authentication at places such as ski resorts, hot springs, and beaches. Alternatively, users can enjoy services such as checking mileage status and boarding pass information at airports, etc., using biometric authentication.

[0182] The service server 10 of each service provider may store biometric information (e.g., face image) of the user. The service server 10 may store the biometric information of the user and ticket identification information (token ID, ticket URL) of the ticket purchased by the user in association with each other. In this case, the authentication terminal 20 transmits an authentication request including the biometric information of the person to be authenticated. The authentication unit 203 executes a matching process (one-to-N matching, N is a positive integer) using the biometric information included in the authentication request and the biometric information stored in advance to identify the person to be authenticated. The authentication unit 203 may acquire an NFT ticket from the NFT management system 30 using the ticket identification information stored in association with the identified person to be authenticated. The authentication unit 203 may authenticate the person to be authenticated using the acquired NFT ticket. That is, the service server 10 on the network (service server 10 on the cloud) may authenticate the person to be authenticated using the biometric information of the user and the NFT ticket acquired from the blockchain. As a result, the user can receive services through face authentication.

[0183] In the above embodiment, a case has been described in which a ticket management database, etc. is configured inside the service server 10, but the database may be constructed in an external database server, etc. In other words, some of the functions of the service server 10 may be implemented in another server. More specifically, the above-described "buying and selling control unit (buying and selling control means)" etc. may be implemented in any of the devices included in the system.

[0184] Although the form of data transmission and reception between each device (service server 10, terminal 40, etc.) is not particularly limited, the data transmitted and received between these devices may be encrypted. Biometric information of users and the like is transmitted and received between these devices, and in order to appropriately protect this information, it is desirable to transmit and receive encrypted data.

[0185] In the flow charts (flow charts, sequence diagrams) used in the above description, multiple steps (processes) are described in order, but the order of execution of the steps executed in the embodiments is not limited to the order described. In the embodiments, the order of the steps shown in the figures can be changed to a degree that does not interfere with the content, such as executing each process in parallel.

[0186] The above-mentioned embodiments have been described in detail to facilitate understanding of the present disclosure, and it is not intended that all of the configurations described above are necessary. In addition, when a plurality of embodiments are described, each embodiment may be used alone or in combination. For example, it is possible to replace a part of the configuration of an embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of an embodiment. Furthermore, it is possible to add, delete, or replace a part of the configuration of an embodiment with another configuration.

[0187] The above explanation makes the industrial applicability of the present invention clear, and the present invention can be suitably applied to information processing systems that sell NFT tickets to users.

[0188] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes.

[0189] [Appendix 1] A ticket sales control means for registering a first NFT (Non-Fungible Token) ticket corresponding to a first ticket in an NFT management system when a first ticket is sold to a first user; a buying and selling control means for, when a second user wishes to purchase the first NFT ticket, determining whether or not the second user is eligible to purchase the first ticket, and permitting the second user to purchase the first NFT ticket if the second user is eligible to purchase the first ticket; A server device comprising: [Appendix 2] The server device described in Appendix 1, wherein the ticket sales control means, upon selling the first ticket to the first user, registers the first NFT ticket in the NFT management system, with the biometric information of the first user as the biometric information of the owner of the first ticket. [Appendix 3] The server device described in Appendix 2, wherein the buying and selling control means, when permitting the second user to purchase the first NFT ticket, registers a second NFT ticket in the NFT management system, the second NFT ticket having the biometric information of the second user as the biometric information of the owner of the first ticket. [Appendix 4] The server device described in Appendix 3, wherein the buying and selling control means obtains identification of the second user, and if the identity verification of the second user is successful using the identification and the second user is eligible to purchase the first ticket, permits the second user to purchase the first NFT ticket. [Appendix 5] The server device described in Appendix 4, wherein the buying and selling control means transmits information for identifying the second NFT ticket, which is issued by registering the second NFT ticket in the NFT management system, to a terminal possessed by the second user. [Appendix 6] The server device described in Appendix 1, wherein the ticket sales control means acquires identification of the first user, and sells the first ticket to the first user if identity verification using the identification is successful and the first user is eligible to purchase the first ticket. [Appendix 7] The server device described in Appendix 6, wherein the ticket sales control means transmits information for identifying the first NFT ticket, which is issued by registering the first NFT ticket in the NFT management system, to a terminal possessed by the first user. [Appendix 8] the ticket sales control means is necessary for receiving services from each of a plurality of service providers, and when a second ticket consisting of a plurality of tickets corresponding to each of the plurality of service providers is sold to the first user, a third NFT ticket having the biometric information of the first user as the biometric information of the owner of the second ticket is registered in the NFT management system; The server device described in any one of Appendices 2 to 7, wherein the buying and selling control means, when the second user wishes to purchase the third NFT ticket, determines whether the second user is eligible to purchase each of the multiple tickets included in the second ticket, and if the second user is eligible to purchase each of the multiple tickets, permits the second user to purchase the third NFT ticket. [Appendix 9] In the server device, When a first ticket is sold to a first user, a first NFT (Non-Fungible Token) ticket corresponding to the first ticket is registered in an NFT management system; A control method for a server device, when a second user wishes to purchase the first NFT ticket, determining whether the second user is eligible to purchase the first ticket, and allowing the second user to purchase the first NFT ticket if the second user is eligible to purchase the first ticket. [Appendix 10] A computer installed in the server device When a first ticket is sold to a first user, a process of registering a first NFT (Non-Fungible Token) ticket corresponding to the first ticket in an NFT management system; When a second user wishes to purchase the first NFT ticket, a process of determining whether the second user is eligible to purchase the first ticket, and permitting the second user to purchase the first NFT ticket if the second user is eligible to purchase the first ticket; A program for executing the above.

[0190] In addition, some or all of the configurations described in Supplementary Notes 2 to 8 that are dependent on Supplementary Note 1 above may also be dependent on Supplementary Notes 9 and 10 in the same dependent relationship as Supplementary Notes 2 to 8. Furthermore, not limited to Supplementary Notes 1, 9, and 10, but similarly, some or all of the configurations described as supplementary notes may be dependent on various hardware, software, various recording means for recording software, or systems within the scope of each of the above-mentioned embodiments.

[0191] The disclosures of the above cited prior art documents are incorporated herein by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications are possible without departing from the scope and spirit of the present invention. In other words, the present invention naturally includes various modifications and amendments that a person skilled in the art can make in accordance with the entire disclosure, including the scope of the claims, and the technical ideas. [Explanation of symbols]

[0192] 10 Service Server 20 Authentication terminal 30 NFT Management Systems 40 Terminals 100 Server device 101 Ticket sales control measures 102 Trading Control Measures 201 Communication control section 202 Ticket Sales Control Unit 203 Authentication Department 204 Trading Control Unit 205 Storage section 311 Processor 312 Memory 313 Input / Output Interface 314 Communication Interface

Claims

1. a ticket sales control means for registering a first NFT (Non-Fungible Token) ticket corresponding to the first ticket in an NFT management system when the first ticket is sold to a first user; a buying and selling control means for, when a second user wishes to purchase the first NFT ticket, determining whether or not the second user is qualified to purchase the first ticket, and permitting the second user to purchase the first NFT ticket if the second user is qualified to purchase the first ticket; A server device comprising:

2. The server device according to claim 1, wherein the ticket sales control means, upon selling the first ticket to the first user, registers the first NFT ticket in the NFT management system, the first NFT ticket having the biometric information of the first user as the biometric information of the owner of the first ticket.

3. The server device according to claim 2, wherein the buying and selling control means, when permitting the second user to purchase the first NFT ticket, registers a second NFT ticket in the NFT management system, the second NFT ticket having the biometric information of the second user as the biometric information of the owner of the first ticket.

4. The server device of claim 3, wherein the buying and selling control means obtains identification of the second user, and if the second user's identity is successfully verified using the identification and the second user is eligible to purchase the first ticket, permits the second user to purchase the first NFT ticket.

5. The server device according to claim 4, wherein the buying and selling control means transmits information for identifying the second NFT ticket, which is issued by registering the second NFT ticket in the NFT management system, to a terminal possessed by the second user.

6. The server device according to claim 1, wherein the ticket sales control means acquires identification of the first user, and sells the first ticket to the first user if identity verification using the identification is successful and the first user is eligible to purchase the first ticket.

7. The server device according to claim 6, wherein the ticket sales control means transmits information for identifying the first NFT ticket, which is issued by registering the first NFT ticket in the NFT management system, to a terminal possessed by the first user.

8. the ticket sales control means is necessary for receiving services from each of a plurality of service providers, and when a second ticket consisting of a plurality of tickets corresponding to each of the plurality of service providers is sold to the first user, a third NFT ticket having the biometric information of the first user as the biometric information of the owner of the second ticket is registered in the NFT management system; The server device according to any one of claims 2 to 7, wherein the buying and selling control means, when the second user wishes to purchase the third NFT ticket, determines whether the second user is eligible to purchase each of the multiple tickets included in the second ticket, and if the second user is eligible to purchase each of the multiple tickets, allows the second user to purchase the third NFT ticket.

9. In the server device, When a first ticket is sold to a first user, a first NFT (Non-Fungible Token) ticket corresponding to the first ticket is registered in an NFT management system; A control method for a server device, when a second user wishes to purchase the first NFT ticket, determining whether the second user is eligible to purchase the first ticket, and allowing the second user to purchase the first NFT ticket if the second user is eligible to purchase the first ticket.

10. A computer installed in the server device When a first ticket is sold to a first user, a process of registering a first NFT (Non-Fungible Token) ticket corresponding to the first ticket in an NFT management system; When a second user desires to purchase the first NFT ticket, a process of determining whether the second user is eligible to purchase the first ticket, and permitting the second user to purchase the first NFT ticket if the second user is eligible to purchase the first ticket; A program for executing the above.

Images