Server device, system, control method and program for server device
A server device and system authenticate ticket holders using biometric data and location verification to prevent illegal ticket resale by ensuring valid ticket holders are at the correct event location and time.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- NEC CORP
- Filing Date
- 2024-11-11
- Publication Date
- 2026-05-21
AI Technical Summary
The illegal resale of tickets for events is difficult to prevent due to the challenges of installing dedicated authentication terminals at various venues where events are held.
A server device and system that stores biometric information of ticket purchasers in association with their ticket information, and performs authentication using biometric information, current location, and authentication date and time to verify ticket validity.
Prevents illegal ticket resale by ensuring that only authorized individuals with valid tickets at the correct time and location can enter event venues.
Smart Images

Figure 2026084406000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a server device, a system, a control method for a server device, and a program.
Background Art
[0002] There are technologies related to user authentication.
[0003] For example, Patent Document 1 describes providing an authentication system that can perform authentication processing using a face image suitable for face authentication. The authentication system of Patent Document 1 includes a mobile terminal and an authentication device installed at the entrance of a specific room. The mobile terminal is carried by a user and transmits a captured image by an imaging unit to the authentication device as authentication information. The authentication device has a control unit, a code reader, and an imaging unit. When a predetermined identification number and face feature points to be authenticated are read from an information code by the code reader, the control unit performs a first collation process based on the face feature points extracted from the captured image transmitted from the mobile terminal and the face feature points read from the information code. On the other hand, when a captured image is not received from the mobile terminal, the control unit performs a second collation process based on the face feature points extracted from the captured image of the imaging unit and the face feature points read from the information code.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0005] In recent years, the illegal resale of tickets for events and other similar activities has become a problem. One possible technology to prevent such illegal resale is to utilize biometric authentication, as disclosed in Patent Document 1. However, the authentication system disclosed in Patent Document 1 requires the installation of an authentication terminal for authenticating the person being authenticated at the entrance to an area where user access is restricted.
[0006] It is difficult to install dedicated authentication terminals at all venues (indoors and outdoors) where events are held.
[0007] The primary objective of this invention is to provide a server device, a system, a control method for the server device, and a program that contribute to preventing the illegal resale of tickets for events and the like. [Means for solving the problem]
[0008] According to a first aspect of the present invention, a server device is provided, comprising: a storage means for storing in association the biometric information of each of a plurality of ticket purchasers with information relating to the purchased tickets; and an authentication means for receiving the biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the terminal of the person to be authenticated, performing a matching process using the received biometric information and the plurality of stored biometric information to identify the person to be authenticated from among the plurality of ticket purchasers, authenticating the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notifying the terminal of the authentication result.
[0009] According to a second aspect of the present invention, a system is provided comprising: a terminal of a person to be authenticated; a server device, the server device having storage means for storing in association between the biometric information of each of a plurality of ticket purchasers and the purchased ticket information relating to the purchased ticket; and authentication means for receiving the biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the authentication date and time from the terminal of the person to be authenticated; performing a matching process using the received biometric information and the plurality of stored biometric information to identify the person to be authenticated from among the plurality of ticket purchasers; authenticating the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the authentication date and time; and notifying the terminal of the authentication result.
[0010] A third aspect of the present invention provides a control method for a server device, comprising: a storage step of storing in association the biometric information of each of a plurality of ticket purchasers with the purchased ticket information; and an authentication step of receiving the biometric information of the person to be authenticated, information regarding the current location of the terminal and information regarding the authentication date and time from the terminal of the person to be authenticated, performing a matching process using the received biometric information and the plurality of stored biometric information to identify the person to be authenticated from among the plurality of ticket purchasers, authenticating the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location and information regarding the authentication date and time, and notifying the terminal of the authentication result.
[0011] According to a fourth aspect of the present invention, a program is provided for a computer mounted on a server device to perform a storage process that stores, in association with the biometric information of each of several ticket purchasers and the purchased ticket information relating to the purchased ticket; and an authentication process that receives the biometric information of the person to be authenticated, information regarding the current location of the terminal and information regarding the authentication date and time from the terminal of the person to be authenticated, performs a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the several ticket purchasers, authenticates the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location and the information regarding the authentication date and time, and notifies the terminal of the authentication result. [Effects of the Invention]
[0012] According to each aspect of the present invention, a server device, a system, a control method for the server device, and a program are provided that contribute to preventing the illegal resale of tickets for participation in events, etc. However, the effects of the present invention are not limited to those described above. The present invention may produce other effects in lieu of or in conjunction with the effects described above. [Brief explanation of the drawing]
[0013] [Figure 1] Figure 1 is a diagram illustrating the outline of one embodiment. [Figure 2] Figure 2 is a flowchart showing the operation of one embodiment. [Figure 3] Figure 3 is a diagram showing an example of the schematic configuration of the information processing system related to this disclosure. [Figure 4] Figure 4 is a diagram illustrating the operation of the information processing system related to this disclosure. [Figure 5] Figure 5 shows an example of the processing configuration of the server device related to this disclosure. [Figure 6] Figure 6 shows an example of a ticket purchaser management database related to this disclosure. [Figure 7]Figure 7 is a flowchart showing an example of the operation of the authentication unit related to this disclosure. [Figure 8] Figure 8 shows an example of the processing configuration of the terminal related to this disclosure. [Figure 9] Figure 9 shows an example of the display on the terminal related to this disclosure. [Figure 10] Figure 10 shows an example of the display on the terminal related to this disclosure. [Figure 11] Figure 11 shows an example of the hardware configuration of the server device related to this disclosure. [Modes for carrying out the invention]
[0014] First, an overview of one embodiment will be described. The reference numerals in the drawings attached to this overview are provided for convenience as examples to aid understanding, and this overview is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units, not hardware units. The connecting lines between blocks in each drawing include both bidirectional and unidirectional lines. Unidirectional arrows schematically indicate the flow of the main signal (data) and do not exclude bidirectional flow. In this specification and in the drawings, elements that can be similarly described are given the same reference numerals to avoid redundant explanation.
[0015] The server device 100 according to an embodiment includes a storage unit 101 and an authentication unit 102 (see FIG. 1). The storage unit 101 stores, in association with each other, biometric information of a plurality of ticket purchasers and purchase ticket information regarding the purchased tickets (step S1 in FIG. 2). The authentication unit 102 receives, from the terminal of the authenticated person, biometric information of the authenticated person, information regarding the current position of the terminal, and information regarding the authentication date and time, and executes a collation process using the received biometric information and the plurality of stored biometric information (step S2). By executing the collation process, the authentication unit 102 identifies the authenticated person from among the plurality of ticket purchasers, and authenticates the identified authenticated person based on the purchase ticket information of the identified authenticated person, the received information regarding the current position, and the information regarding the authentication date and time (step S3). The authentication unit 102 notifies the terminal of the authentication result (step S4).
[0016] The server device 100 acquires biometric information of the authenticated person, information regarding the current position of the terminal, and information regarding the authentication date and time from the terminal of the authenticated person. The server device 100 identifies the authenticated person from among a plurality of ticket purchasers who have purchased tickets in advance by executing a collation process using the biometric information. The server device 100 authenticates the authenticated person based on the purchased ticket information set for the identified authenticated person, the current position of the terminal, and the authentication date and time. Specifically, the server device 100 determines whether the authenticated person has the right to enter the event venue using the authentication date and time. That is, the server device 100 determines whether the authenticated person has a valid ticket from a temporal perspective. Further, the server device 100 determines whether the authenticated person is attempting to be authenticated at the event venue using the current position. That is, the server device 100 makes a determination regarding the authentication location of the authenticated person using the current position of the authenticated person. When the server device 100 succeeds in these determinations, it determines that the authentication of the authenticated person has succeeded. The server device 100 transmits the authentication result to the terminal. By such an operation of the server device 100, fraud such as a person who has purchased a ticket being authenticated at a location away from the event venue at a time other than the time when they can enter the event venue and then handing over the authentication success screen to another person is prevented. That is, fraud such as the illegal resale of tickets for participating in an event or the like is prevented.
[0017] Specific embodiments will be described in more detail below with reference to the drawings.
[0018] [First Embodiment] The first embodiment will be described in more detail with reference to the drawings.
[0019] [Configuration of System] FIG. 3 is a diagram showing an example of the schematic configuration of an information processing system (authentication system) according to an embodiment of the present disclosure. As shown in FIG. 3, the information processing system includes a server device 10.
[0020] The information processing system according to the first embodiment provides, for example, an authentication service for events held in various locations such as suburban stadiums (e.g., rock festivals).
[0021] Server device 10 is a server that manages and controls the authentication service and ticket sales mentioned above. Although not particularly limited, server device 10 may be managed and operated by an event planning company, etc. Alternatively, a company commissioned by an event planning company may manage and operate server device 10. Server device 10 may be installed in the event planning company's building or on a network (on the cloud).
[0022] The user (event participant) possesses device 20.
[0023] The devices shown in Figure 3 are interconnected. Specifically, the server device 10 and the terminal 20 are connected by wired or wireless communication means and are configured to communicate with each other.
[0024] The configuration of the information processing system shown in Figure 3 is illustrative and not intended to limit its configuration. For example, the information processing system may include multiple server devices 10. Load balancing and redundancy may be achieved by the multiple server devices 10.
[0025] [General operation] Next, we will describe the general operation of the information processing system according to the first embodiment.
[0026] <Purchase Tickets> Users who wish to participate in the event must purchase a ticket in advance. To do so, users operate terminal 20 to access server device 10 and create an account. Users (those wishing to participate in the event) register their name, gender, date of birth, address, login information, phone number, email address, biometric information, etc. on the web page provided by server device 10.
[0027] Examples of biometric information include data (feature quantities) calculated from individual physical characteristics such as face, fingerprints, voiceprints, veins, retina, and iris patterns. Alternatively, biometric information may be image data such as face images or fingerprint images. Biometric information only needs to include information about the user's physical characteristics. In the first embodiment, we will describe the case in which biometric information (face image or feature quantities generated from a face image) relating to a person's "face" is used.
[0028] The server device 10 obtains the user's name and other information, and then generates an account for the user. Once the account is generated, the user can purchase a ticket.
[0029] Once a user decides which ticket to purchase, the server device 10 stores the purchased ticket information in the user's account.
[0030] For example, the server device 10 stores the event venue name, event date, and entry time (e.g., opening time to closing time) in the user's account as purchased ticket information. The user's account also stores the ticket purchaser's name, gender, date of birth, address, login information, biometric information, telephone number, email address, etc., as ticket purchaser information.
[0031] In this way, the server device 10 stores ticket purchaser information and purchased ticket information in the ticket purchaser management database. Details of the ticket purchaser management database will be described later.
[0032] <Entering the event venue> On the day of the event, participants head to the event venue. Staff members are waiting at the entrance of the event venue.
[0033] The user (event participant) uses terminal 20 to inform the staff that they have the authority to enter the event venue. Specifically, the user receives authentication to enter the event venue via terminal 20.
[0034] First, terminal 20 acquires the user's biometric information. For example, terminal 20 acquires the user's facial image through a so-called selfie.
[0035] Furthermore, terminal 20 calculates its current location (latitude and longitude). For example, terminal 20 calculates its current location using GPS (Global Positioning System) signals. For example, the calculated current location may also be in the form of code information (QR (Quick Response) code, one-time code, etc.). Note that QR code is a registered trademark.
[0036] Terminal 20 notifies the server device 10 of the acquired biometric information, current location, and authentication date and time (current time). Specifically, terminal 20 sends an authentication request to the server device 10 that includes biometric information, information about the current location, and information about the authentication date and time (see Figure 4). For example, the authentication date and time will be the date and time when the user acquired biometric information and the current location using terminal 20.
[0037] The server device 10 authenticates users (authenticated persons) who attempt to enter the event venue using the information included in the authentication request.
[0038] Specifically, the server device 10 identifies the person to be authenticated through a matching process using the biometric information included in the authentication request and the biometric information stored in the ticket purchaser management database.
[0039] The server device 10 authenticates the identified person based on the purchase ticket information of the identified person, the current location information received from the terminal 20, and the authentication date and time information.
[0040] Specifically, the server device 10 determines whether the identified user possesses (purchases) a valid ticket. More specifically, the server device 10 determines whether the authenticated user's ticket is valid based on the current location and authentication date and time notified from the terminal 20, and the authenticated user's purchased ticket information identified through the matching process.
[0041] The server device 10 determines whether the authentication date included in the authentication date and time of the person being authenticated is an event day, and whether the authentication time included in the authentication date and time of the person being authenticated is included in the entry time slot.
[0042] Furthermore, the server device 10 determines whether the person to be authenticated is attempting to be authenticated at the event venue. If the person to be authenticated is currently near the event venue, the server device 10 determines that the person to be authenticated is attempting to be authenticated at the event venue. If the person to be authenticated is far from the event venue, the server device 10 determines that the person to be authenticated is not attempting to be authenticated at the event venue.
[0043] If the authenticated person attempts to enter the event venue during the entry time on the ticketed date, and the authenticated person has been authenticated near the event venue, the server device 10 determines that the authentication was successful. For example, if the authenticated person (1) has successfully undergone verification using biometric information, (2) the authentication date and time is the event date and time and entry time (for example, from opening time to closing time), and (3) the current location is near the event venue, the server device 10 determines that the authentication was successful.
[0044] The server device 10 determines authentication to be unsuccessful if the matching process fails, if the authentication date and the event date do not match, if the person being authenticated is attempting to enter the event venue outside of the designated entry time, or if the person being authenticated is not attempting to be authenticated at the event venue. For example, the server device 10 determines authentication to be unsuccessful if the person being authenticated fails the matching process using biometric information, if the authentication date and time are not within the event date and entry time (e.g., from opening time to closing time), or if the current location is not near the event venue.
[0045] The server device 10 notifies the terminal 20 of the authentication result (authentication successful, authentication failed). The terminal 20 displays the authentication result.
[0046] The user (authenticated person) presents the screen displaying "authentication successful" to the staff. Upon confirming the screen displaying "authentication successful," the staff will permit the user to enter the event venue.
[0047] Next, we will describe the details of each device included in the information processing system according to the first embodiment.
[0048] [Server equipment] Figure 5 shows an example of the processing configuration (processing module) of the server device 10 according to the embodiment disclosed herein. Referring to Figure 5, the server device 10 comprises a communication control unit 201, an account control unit 202, a sales control unit 203, an authentication unit 204, and a storage unit 205.
[0049] 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 terminal 20. The communication control unit 201 also transmits data to terminal 20. 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, other processing modules send and receive data with other devices via the communication control unit 201. The communication control unit 201 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.
[0050] The account control unit 202 is a means for performing control related to the account.
[0051] The account control unit 202 obtains the user's name, gender, date of birth, address, login information (ID, password), telephone number, email address, biometric information (facial image, etc.) from a designated web page or the like.
[0052] The account control unit 202 generates features from the acquired face image. Note that existing technologies can be used for the feature generation process, so a detailed explanation is omitted. For example, the account control unit 202 extracts features such as eyes, nose, and mouth from the face image. Then, the account control unit 202 calculates the position of each feature point and the distance between each feature point as features (generating a feature vector consisting of multiple features).
[0053] Furthermore, the account control unit 202 generates a user ID to identify the user. The user ID can be any information that can uniquely identify the user. For example, the account control unit 202 may assign a unique value each time an account is created and use that as the user ID.
[0054] The account control unit 202 stores the generated user ID, name, biometric information (features), etc., in the ticket purchaser management database (see Figure 6). Note that the ticket purchaser management database shown in Figure 6 is an example and is not intended to limit the items to be stored. For example, the ticket purchaser management database may also store the user's facial image.
[0055] Furthermore, multiple purchase ticket information entries may be set for a single entry (single account). That is, if one user purchases multiple tickets, the purchase ticket information for each ticket will be set for a single entry.
[0056] The sales control unit 203 is a means for performing control related to the sale of tickets.
[0057] When a user who has created an account performs a predetermined action (for example, pressing the ticket purchase button), the sales control unit 203 displays a list of tickets available for purchase on the terminal 20. For example, the list of tickets available for purchase may be extracted by considering the user's past purchase history, information such as the user's favorite artists that the user has registered in advance, the purchase history of other users with similar hobbies and interests, the purchase history of other users of the same age, the user's address, the user's age, etc.
[0058] The user selects the ticket they wish to purchase from the list of tickets displayed on terminal 20.
[0059] Once the user has finished selecting the tickets to purchase, the sales control unit 203 stores the information of the selected tickets (purchase ticket information; for example, event venue name, event date, entry time slot, etc.) in the ticket purchaser management database. In this way, the ticket purchaser management database stores the purchase ticket information, including information about the event venue, the event date, and the time slot during which event participants can enter the event venue, in association with information about the user (user ID, name, biometric information (features), etc.).
[0060] The sales control unit 203 retrieves the purchased ticket information by referring to table information, etc., which stores information on each ticket available for sale to the user. The sales control unit 203 stores the retrieved purchased ticket information in the ticket purchaser's entry.
[0061] Once the purchased ticket information is stored in the ticket management database, the sales control unit 203 settles the payment for the purchased tickets.
[0062] For example, the sales control unit 203 processes payment for tickets using a credit card, electronic money, etc. Once payment for the purchased tickets is complete, the sales control unit 203 notifies the user accordingly.
[0063] Further details regarding ticket sales and payment are omitted. This is because ticket sales and other related matters are obvious to those skilled in the art and are outside the scope of this disclosure.
[0064] The authentication unit 204 is a means for authenticating the person to be authenticated. Specifically, the authentication unit 204 processes authentication requests received from the terminal 20. For example, a user may launch a dedicated application on the terminal 20 for managing tickets purchased by the user and send an authentication request by selecting a ticket.
[0065] The authentication unit 204 receives biometric information of the person to be authenticated, information about the current location of the terminal 20, and information about the authentication date and time from the terminal 20 of the person to be authenticated. The authentication unit 204 identifies the person to be authenticated from among multiple ticket purchasers by performing a matching process using the received biometric information and multiple biometric information stored in the ticket purchaser management database. The authentication unit 204 authenticates the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information about the current location, and the authentication date and time. The authentication unit 204 notifies the terminal 20 of the authentication result.
[0066] Figure 7 is a flowchart illustrating an example of the operation of the authentication unit 204 according to the embodiment disclosed herein. The operation of the authentication unit 204 will be explained with reference to Figure 7.
[0067] When the authentication unit 204 receives an authentication request from terminal 20, it performs a matching process using the biometric information (face image) included in the authentication request and the biometric information stored in the ticket purchaser management database (step S101).
[0068] The authentication unit 204 generates feature vectors from the facial image included in the authentication request. The authentication unit 204 sets the generated feature vectors as the matching target and performs a matching process with the feature vectors registered in the ticket purchaser management database. More specifically, the authentication unit 204 sets the generated feature vectors (feature vectors) as the matching target and performs a one-to-many (N is a positive integer, the same applies hereafter) matching with multiple feature vectors registered in the ticket purchaser management database.
[0069] The authentication unit 204 calculates the similarity between the feature quantities to be matched and each of the multiple feature quantities on the registration side. This similarity can be calculated using methods such as the chi-squared distance or the Euclidean distance. Note that the greater the distance, the lower the similarity, and the closer the distance, the higher the similarity.
[0070] The authentication unit 204 determines that the matching process was successful if, among the multiple features registered in the ticket purchaser management database, there is a feature whose similarity to the feature to be matched is equal to or greater than a predetermined value. The authentication unit 204 determines that the matching process failed if no such feature exists.
[0071] If the matching process fails (step S102, No branch), the authentication unit 204 notifies the terminal 20 that the authentication of the person to be authenticated has failed. Specifically, the authentication unit 204 sends a negative response as a response to the authentication request (step S103).
[0072] If the matching process is successful (step S102, Yes branch), the authentication unit 204 determines whether the ticket of the person to be authenticated (the ticket purchaser corresponding to the feature with the greatest similarity) identified by the matching process is valid or not (ticket validity determination; step S104).
[0073] If the authentication unit 204 finds that no purchased ticket information is set for the user identified through the matching process, it determines that the person being authenticated (the person wishing to attend the event) does not possess a valid ticket. In this case, the authentication unit 204 sets the result of the ticket validity determination to failure. For example, if one or more ticket information entries are set for the user identified through the matching process, the authentication unit 204 may send a list of one or more ticket information entries to the person being authenticated's terminal 20, the person being authenticated may select the ticket they wish to authenticate, and the authentication unit 204 may determine the validity of the ticket selected by the person being authenticated.
[0074] If the authenticated user's account has purchased ticket information set up, the authentication unit 204 determines the validity of the ticket based on the authentication date and time included in the authentication request and the event date and entry time set up in the purchased ticket information stored in the authenticated user's account.
[0075] If the authentication date of the person being authenticated is different from the event date, or if the authentication time of the person being authenticated is not included in the entry time slot, the authentication unit 204 determines that the person being authenticated's ticket is not valid. In this case, the authentication unit 204 sets the ticket validity determination result to failure.
[0076] If the authentication date is the event date and the authentication time falls within the entry time slot, the authentication unit 204 determines the validity of the ticket based on the current location included in the authentication request and the event venue name set in the purchased ticket information.
[0077] The authentication unit 204 refers to a table that stores event venue names and location information (coordinates; latitude, longitude) of the event venues in association, and obtains the location information of the venue where the event will be held. The authentication unit 204 obtains the location information of the event venues that the authenticated person can enter with the ticket they purchased.
[0078] If the current location of the authenticated person (terminal 20) is not within a predetermined range centered on the event venue (a predetermined range centered on the entrance of the event venue), the authentication unit 204 determines that the authenticated person's ticket is not valid. In this case, the authentication unit 204 sets the result of the ticket validity determination to failure.
[0079] If the current location of the authenticated person (terminal 20) is within a predetermined range centered on the event venue, the authentication unit 204 determines that the authenticated person's ticket is valid. In this case, the authentication unit 204 sets the result of the ticket validity determination to success.
[0080] Here, the specified range may be changed taking into consideration the degree of congestion at the event venue, the time of day, the weather, the status of public transportation, the type of event, the security level, real-time feedback, etc.
[0081] For example, regarding the degree of congestion at an event venue, a wider range may be set when the venue is very crowded, and a narrower range may be set when the venue is not very crowded.
[0082] For example, regarding time zones, a wider range may be set for times when people are concentrated, such as immediately before or after the start and end of an event, while a narrower range may be set for relatively stable times, such as during the event itself.
[0083] For example, regarding weather conditions, the designated area may be set wider in case of rain, taking into account that people will move more slowly by using umbrellas, etc. On extremely hot days, the designated area may be set wider to take into account the possibility of dispersing the waiting line as a measure against heatstroke.
[0084] For example, regarding the status of public transportation, the predetermined range may be temporarily set wider based on delay information for surrounding public transportation.
[0085] For example, regarding the type of event, if there are multiple stages, such as in a music festival, a predetermined area may be set centered on any location within the entire venue.
[0086] For example, regarding security levels, the specified range may be narrowed for events requiring high security.
[0087] For example, for real-time feedback, data on the success rate and waiting time of authentication for other unauthenticated participants in the event may be analyzed in real time, and an optimal predetermined range may be dynamically set.
[0088] If the ticket validity check fails (step S105, No branch), the authentication unit 204 sends a negative response as a response to the authentication request (step S103).
[0089] If the ticket validity check is successful (step S105, Yes branch), the authentication unit 204 notifies the terminal 20 of the successful authentication. The authentication unit 204 sends an affirmative response in response to the authentication request (step S106).
[0090] In this way, the authentication unit 204 determines whether the authentication date of the person to be authenticated matches the event date stored in association with the person to be authenticated identified by the matching process. The authentication unit 204 also determines whether the authentication time of the person to be authenticated falls within the time period in association with the person to be authenticated identified by the matching process that is permitted to enter the event venue. Furthermore, the authentication unit 204 determines whether the current location notified from the terminal 20 falls within a predetermined range centered on the event venue. If each of these determinations is successful, the authentication unit 204 determines that the ticket of the person to be authenticated identified by the matching process is valid and determines that the authentication of the person to be authenticated has been successful.
[0091] The storage unit 205 is a means for storing information necessary for the operation of the server device 10. A ticket purchaser management database is constructed in the storage unit 205. The storage unit 205 uses the ticket purchaser management database to store the biometric information of multiple ticket purchasers in association with the purchased ticket information.
[0092] [Terminal] Figure 8 shows an example of the processing configuration (processing module) of terminal 20 according to the embodiment disclosed herein. Referring to Figure 8, terminal 20 comprises a communication control unit 301, an authentication control unit 302, and a storage unit 303.
[0093] The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the server device 10. The communication control unit 301 also transmits data to the server device 10. The communication control unit 301 passes the data received from other devices to other processing modules. The communication control unit 301 transmits the data acquired from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 301. The communication control unit 301 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.
[0094] The authentication control unit 302 is a means for controlling the authentication of the person to be authenticated (a user who wishes to enter the event venue).
[0095] The authentication control unit 302 controls the camera on the terminal 20 to acquire biometric information (facial image). Specifically, the authentication control unit 302 acquires image data in response to user operations.
[0096] The authentication control unit 302 attempts to extract a face image from the acquired image data.
[0097] Specifically, the authentication control unit 302 extracts face images (face regions) from the image data using a learning model trained by a Convolutional Neural Network (CNN). Alternatively, the authentication control unit 302 may extract face images from the image data using methods such as template matching.
[0098] If a facial image cannot be extracted, the authentication control unit 302 notifies the user of this fact and re-acquires the image data. The authentication control unit 302 then extracts the facial image from the re-acquired image data.
[0099] When a face image is detected from the image data, the authentication control unit 302 calculates the current location of the terminal (terminal 20).
[0100] For example, the authentication control unit 302 receives GPS signals from GPS (Global Positioning System) satellites, performs positioning, and generates location information including the latitude and longitude of its own device. Alternatively, the authentication control unit 302 may communicate with a wireless access point and treat the location of the wireless access point as the location of its own device. Alternatively, the authentication control unit 302 may generate location information based on the strength of radio waves received from the wireless access point.
[0101] Once the current location is calculated, the authentication control unit 302 sends an authentication request to the server device 10 that includes biometric information (face image), information about the current location (latitude and longitude), and information about the authentication time (current time).
[0102] The authentication control unit 302 receives a response (affirmative response, negative response) to the authentication request.
[0103] When an affirmative response is received, the authentication control unit 302 displays a message indicating that authentication was successful. For example, the authentication control unit 302 displays a screen as shown in Figure 9.
[0104] When notifying the user of successful authentication, the authentication control unit 302 may display the authentication date and time and the authentication location, as shown in Figure 9. In this case, the authentication control unit 302 may identify the landmark where the terminal is located based on the terminal's location information and display the name of the identified landmark.
[0105] If a negative response is received, the authentication control unit 302 displays a message indicating that authentication failed. For example, the authentication control unit 302 displays a screen as shown in Figure 10.
[0106] The memory unit 303 is a means for storing information necessary for the operation of the terminal 20.
[0107] Next, a modified example of the first embodiment will be described.
[0108] <Example 1> The server device 10 may verify the identity of the user after selling the ticket to the user. Specifically, the sales control unit 203 may verify the identity of the ticket purchaser after selling the ticket to the user.
[0109] In this case, the storage unit 205 may store the biometric information of the ticket purchaser who has successfully verified their identity in the ticket purchaser management database. That is, the storage unit 205 may store the biometric information of the ticket purchaser who has successfully verified their identity in association with the purchased ticket information.
[0110] Specifically, once the payment for the ticket is completed, the sales control unit 203 displays a GUI (Graphical User Interface) on the terminal 20 and obtains a copy of the identification document (image data showing the identification document), such as a My Number Card, passport, or driver's license.
[0111] Furthermore, the sales control unit 203 acquires the ticket purchaser's biometric information (e.g., facial image) via the terminal 20. For example, the sales control unit 203 displays a GUI on the terminal 20 and instructs the ticket purchaser to take a selfie.
[0112] The sales control unit 203 performs identity verification using the acquired biometric information (facial image) and biometric information obtained from identity verification documents. The sales control unit 203 determines whether the two biometric pieces of information are substantially the same and performs identity verification.
[0113] The sales control unit 203 generates feature quantities from both the acquired facial image and the facial image obtained from the identity verification document (image data showing the identity verification document).
[0114] Next, the sales control unit 203 performs a matching process (one-to-one matching) using the two generated feature quantities. Specifically, the sales control unit 203 calculates the similarity between corresponding face images using the two feature quantities. Based on the result of thresholding the calculated similarity, the sales control unit 203 determines whether the two images are face images of the same person.
[0115] If the similarity is greater than a predetermined value (if the distance is shorter than a predetermined value), the sales control unit 203 determines that identity verification was successful. If the similarity is less than or equal to the predetermined value, the sales control unit 203 determines that identity verification failed.
[0116] If identity verification is successful, the sales control unit 203 stores the ticket purchaser's biometric information in the ticket purchaser's account. At this time, the sales control unit 203 may store the feature quantities generated from the facial image obtained by a selfie in the ticket purchaser management database, or it may store the feature quantities generated from the facial image obtained from the identity verification document in the ticket purchaser management database.
[0117] The biometric information (features) stored in the ticket purchase management database is used for authentication when users enter the event venue.
[0118] In this way, the sales control unit 203 may perform identity verification of the user who purchased the ticket (the user who paid for the ticket). This operation of the sales control unit 203 prevents the biometric information of a third party who is not the ticket purchaser from being stored in the ticket purchaser management database. More specifically, it prevents fraud (impersonation) in which a ticket purchaser registers another person's biometric information (facial image or features) to their account.
[0119] <Modification 2> Alternatively, the server device 10 may perform identity verification using facial VCs (Verifiable Credentials) that guarantee a facial image, instead of the user's identification documents. The user requests the issuance of facial VCs from a local government or similar entity and obtains them. The terminal 20 stores the facial VCs in a digital wallet or similar device.
[0120] After selling a ticket to a user, the sales control unit 203 acquires face VCs and the user's biometric information (face image) from the terminal 20. The sales control unit 203 verifies the acquired face VCs. If the verification of the face VCs is successful, the sales control unit 203 performs identity verification using the face image obtained from the face VCs and the user's face image (face image obtained through selfie).
[0121] Thus, the sales control unit 203 may perform identity verification using biometric information obtained from identity verification documents, or it may perform identity verification using facial images obtained from facial VCs (Verifiable Credentials).
[0122] <Variation 3> The server device 10 may perform identity verification (authentication) of the user when creating the user's account, instead of or in addition to identity verification after ticket sales.
[0123] Specifically, the account control unit 202 acquires image data of identity verification documents and a self-taken facial image, and performs identity verification. If identity verification is successful, the account control unit 202 generates feature quantities from the facial image obtained from the identity verification documents and the self-taken facial image, and stores them in the account. At this time, the account control unit 202 may also acquire the user's name, gender, date of birth, address, etc. from the identity verification documents and store the name, date of birth, etc. in the account.
[0124] For example, when generating a user ID to identify a user, the account control unit 202 may obtain face VCs and the user's biometric information (face image) from the terminal 20. The account control unit 202 verifies the obtained face VCs. If the verification of the face VCs is successful, the account control unit 202 performs identity verification using the face image obtained from the face VCs and the user's face image (face image obtained by taking a selfie).
[0125] Even if identity verification is performed when creating an account, the biometric information (features) used for identity verification will be used in the authentication process when the user enters the event venue.
[0126] <Modification 4> The server device 10 may require successful identity verification before selling tickets with age restrictions to users. The sales control unit 203 may use the date of birth set in the account for which identity verification has been successful to determine whether or not to sell tickets with age restrictions.
[0127] <Modification 5> When selling tickets to a user, the server device 10 may obtain the terminal ID (individual identification number of a smartphone, etc.) of the terminal 20 used by the user. For example, when the sales control unit 203 completes the payment for the tickets sold to the user, it requests the terminal 20 to provide the terminal ID. Alternatively, the sales control unit 203 displays a GUI on the terminal 20 and instructs the user to enter the terminal ID.
[0128] The sales control unit 203 obtains the terminal ID from terminal 20. The sales control unit 203 stores the obtained terminal ID in the user's entry. If the terminal ID differs for each ticket sold, the sales control unit 203 stores the terminal ID in association with the sold ticket information.
[0129] The server device 10 may authenticate the person being authenticated (the user attempting to enter the event venue) using the terminal ID of the terminal 20 used when the person purchased the ticket.
[0130] In this case, the authentication control unit 302 of terminal 20 sends an authentication request to the server device 10 that includes the biometric information of the person to be authenticated, information about the current location, information about the date and time of authentication, and the terminal ID.
[0131] If the authentication unit 204 of the server device 10 determines that the authenticated person's ticket is valid based on the determination using the current location and authentication date and time, it determines whether the terminal ID stored in the authenticated person's account matches the terminal ID included in the authentication request. For example, after determining whether the terminal ID stored in the authenticated person's account matches the terminal ID included in the authentication request, the authentication unit 204 may perform a determination using the current location and authentication date and time.
[0132] If the two terminal IDs do not match, the authentication unit 204 determines that the authentication of the person being authenticated has failed. In this case, the authentication unit 204 sends a negative response indicating authentication failure to terminal 20.
[0133] If the two terminal IDs match, the authentication unit 204 determines that the authentication of the person to be authenticated has been successful. In this case, the authentication unit 204 sends an affirmative response indicating successful authentication to the terminal 20.
[0134] Thus, the storage unit 205 may further store the terminal IDs of the terminals 20 used by each of the multiple ticket purchasers when they purchased their tickets. The authentication unit 204 may receive the terminal ID from the authenticated person's terminal 20 and authenticate the identified authenticated person based on the authenticated person's purchased ticket information identified by the matching process, the current location of the terminal 20, the authentication time, and the terminal ID.
[0135] More specifically, the authentication unit 204 determines whether the authentication date of the person to be authenticated matches the event date stored in association with the person to be authenticated identified through the matching process. The authentication unit 204 also determines whether the authentication time of the person to be authenticated falls within the time frame in association with the event venue that the identified person to be authenticated is permitted to enter. Furthermore, the authentication unit 204 determines whether the current location of terminal 20 falls within a predetermined range centered on the event venue. In addition, the authentication unit 204 determines whether the terminal ID stored in association with the identified person to be authenticated matches the terminal ID received from the person to be authenticated's terminal 20. If the authentication unit 204 succeeds in these determinations, it determines that the authentication of the person to be authenticated identified through the matching process has been successful.
[0136] <Variation 6> In the above embodiment, the case in which the server device 10 authenticates a person to be authenticated using facial information (facial image, feature quantities generated from the facial image) was described. However, the server device 10 may also authenticate a person to be authenticated using other biometric information, such as fingerprint information or iris information.
[0137] As described above, the server device 10 according to the first embodiment receives an authentication request from a terminal 20 of a user attempting to enter an event venue, etc., which includes the biometric information of the person to be authenticated, information regarding the current location of the terminal 20, and information regarding the date and time of authentication. The server device 10 identifies the person to be authenticated from among multiple ticket purchasers who have purchased tickets in advance by performing a matching process using the biometric information. The server device 10 determines whether the person to be authenticated has the authority to enter the event venue using the date and time of authentication included in the authentication request. Furthermore, the server device 10 determines whether the person to be authenticated is attempting to be authenticated at the event venue using the information regarding the current location included in the authentication request. If the server device 10 succeeds in these determinations, it determines that the authentication of the person to be authenticated has been successful. As a result, fraud is prevented in which a person who has purchased a ticket may authenticate at a location away from the event venue at a time other than the date and time when they are allowed to enter the event venue, and then pass on the screen of successful authentication to another person.
[0138] Furthermore, in the information processing system according to the embodiment disclosed herein, the authentication of the person to be authenticated is performed via terminal 20. Therefore, this information processing system can provide authentication suitable for events held outdoors. It is difficult to install large-scale gate devices equipped with gates or flappers at the venue of an outdoor event. However, the information processing system disclosed herein can authenticate the person to be authenticated without installing such large-scale gate devices.
[0139] Furthermore, the server device 10 may authenticate the person being authenticated using the terminal ID in addition to biometric information, the current location of the terminal 20, and the authentication date and time. More specifically, the server device 10 may set the condition for successful authentication as the terminal 20 used by the ticket purchaser at the time of ticket purchase matching the terminal 20 used by the user seeking authentication. As a result, fraudulent activities such as one person purchasing a large number of tickets using one terminal 20 and reselling the purchased tickets to others are prevented.
[0140] Next, we will describe the hardware of each device that makes up the information processing system. Figure 11 shows an example of the hardware configuration of server device 10.
[0141] The server device 10 can be configured using an information processing device (a so-called computer), and has the configuration illustrated in Figure 11. For example, the server device 10 includes a processor 311, memory 312, input / output interface 313, and communication interface 314, etc. The components of the processor 311, etc., are connected by an internal bus or the like and are configured to communicate with each other.
[0142] However, the configuration shown in Figure 11 is not intended to limit the hardware configuration of the server device 10. The server device 10 may include hardware not shown, and it may not have to have an input / output interface 313 if necessary. Also, the number of processors 311 etc. included in the server device 10 is not intended to be limited to the example in Figure 11; for example, multiple processors 311 may be included in the server device 10.
[0143] The processor 311 is a programmable device such as a CPU (Central Processing Unit), MPU (Micro Processing Unit), or DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs, including an operating system (OS).
[0144] Memory 312 includes RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), etc. Memory 312 stores the OS program, application programs, and various data.
[0145] The input / output interface 313 is an interface for a display device or input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device that accepts user input such as a keyboard or mouse.
[0146] The communication interface 314 is a circuit, module, etc., that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card), etc.
[0147] The functions of the server device 10 are realized by various processing modules. These processing modules are realized, for example, by the processor 311 executing a program stored in memory 312. The program can also be recorded on a computer-readable storage medium. The storage medium can be a non-transitory material such as semiconductor memory, hard disk, magnetic recording medium, or optical recording medium. In other words, the present invention can also be embodied as a computer program product. Furthermore, the program can be downloaded via a network or updated using the storage medium on which the program is stored. Moreover, the processing module may be realized by a semiconductor chip.
[0148] Terminal 20 can also be configured using an information processing device, similar to server device 10, and its basic hardware configuration is identical to that of server device 10, so its explanation will be omitted. Terminal 20 is equipped with a camera for photographing the authenticated person.
[0149] The server device 10, which is an information processing device, is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the server device 10 executes a control method for the server device 10 using this program. Similarly, the terminal 20 is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the terminal 20 executes a control method for the terminal 20 using this program.
[0150] [Differentiation] The configuration and operation of the information processing system described in the above embodiment are illustrative examples and are not intended to limit the system configuration.
[0151] The information processing system according to the embodiment disclosed herein assumes that user authentication is performed in the presence of staff waiting at the entrance of the event venue. Therefore, the fact of successful authentication is presented to the staff shortly after terminal 20 notifies server device 10 of acknowledgment (successful authentication). For this reason, terminal 20 may clear the screen shown in Figure 9 after a predetermined time has elapsed (for example, 3 seconds) after receiving the acknowledgment. For example, the predetermined time may be a time related to a dynamic expiration date. Specifically, the expiration date may be dynamically adjusted according to the scale of the event, the number of attendees, the time of day, and the weather. Specifically, a longer expiration date may be set during crowded times or bad weather, and a shorter expiration date may be set during off-peak times or good weather. For example, if a longer expiration date is set, all or part of the initial authentication (authentication using biometric information, current location, authentication date and time, and terminal ID) may be performed at regular intervals. Furthermore, the authentication performed at regular intervals may be different from the initial authentication. For example, this could involve responding to a push notification that the expiration date is approaching, scanning a QR code placed at a specific point within the venue, or entering a one-time passcode sent to terminal 20.
[0152] Alternatively, the server device 10 may notify the terminal 20 of the period during which the authentication success is valid. For example, the server device 10 sends an acknowledgment to the terminal 20 that includes the expiration date (validity period) during which the authenticated person's authentication success is considered valid. Once the expiration date has passed, the terminal 20 clears the screen shown in Figure 9.
[0153] Terminal 20 may send an authentication request to server device 10 that includes the time (time of capture, time of image acquisition) when the user was photographed in order to acquire biometric information (facial image). Server device 10 may authenticate the person to be authenticated depending on whether the authentication time and the time of capture are substantially the same. Server device 10 may use the time of capture to prevent fraudulent entry using the facial image of a ticket purchaser.
[0154] If the server device 10 successfully authenticates the person to be authenticated, it may send the person's biometric information (facial image at the time of ticket purchase) to the terminal 20. The terminal 20 may display the facial image received from the server device 10 on a screen as shown in Figure 9. This operation prevents unauthorized entry through lending or borrowing of the terminal 20.
[0155] Terminal 20 may change the design of the screen displaying successful authentication for each event or date and time. In this case, the design of the successful authentication screen corresponding to the event will be made known to the staff before the event starts. This action prevents fraudulent entry through the forgery of the successful authentication screen.
[0156] In the above embodiment, the case in which the server device 10 performs a one-to-many matching (one-to-many authentication) using biometric information to identify the person to be authenticated was described. However, the server device 10 may also perform a one-to-one matching (one-to-one authentication) using biometric information to authenticate the person to be authenticated. For example, one-to-one matching may be performed after a user operates the terminal 20 and logs in to an account generated on the server device 10. In this case, the server device 10 identifies the person to be authenticated using the login information. The authentication unit 204 of the server device 10 performs one-to-one matching using the biometric information stored in the account of the identified person to be authenticated and the biometric information included in the authentication request. If the one-to-one matching is successful, the authentication unit 204 performs a ticket validity determination and authenticates the person to be authenticated. Generally, one-to-one matching (one-to-one authentication) has higher authentication accuracy and a lower possibility of false authentication than one-to-many matching. Therefore, by using one-to-one matching, the information processing system disclosed in this application can be suitably applied to events with tens or hundreds of thousands of participants.
[0157] In the above embodiment, the case in which the ticket purchaser management database is configured inside the server device 10 was described, but the database may be built on an external database server or the like. In other words, some functions of the server device 10 may be implemented on another server. More specifically, it is sufficient that the "authentication unit (authentication means)" etc. described above is implemented in any device included in the system.
[0158] The form of data transmission and reception between each device (server device 10, terminal 20) is not particularly limited, but the data transmitted and received between these devices may be encrypted. Since biometric information and the like are transmitted and received between these devices, it is desirable that encrypted data be transmitted and received in order to properly protect this information.
[0159] In the flowcharts (sequence diagrams) used in the above description, multiple processes (processes) are shown in order, but the execution order of the processes performed in the embodiment is not limited to the order in which they are shown. In the embodiment, the order of the illustrated processes can be changed to the extent that it does not impair the content, for example, by executing each process in parallel.
[0160] The embodiments described above are explained in detail to facilitate understanding of the disclosure, and it is not intended that all the configurations described above are necessary. Furthermore, when multiple embodiments are described, each embodiment may be used individually or in combination. For example, it is possible to replace parts of the configuration of one embodiment with those of another embodiment, or to add configurations from other embodiments to the configuration of one embodiment. In addition, it is possible to add, delete, or replace parts of the configuration of one embodiment with those of another.
[0161] As described above, the industrial applicability of the present invention is clear, and it is particularly suitable for application to information processing systems that authenticate users who have purchased tickets.
[0162] Some or all of the above embodiments may also be described as follows, but are not limited to the following:
[0163] [Note 1] A storage means that associates the biometric information of multiple ticket purchasers with the purchase information of the tickets they purchased, Authentication means that receive biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the person to be authenticated's terminal, perform a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticate the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notify the terminal of the authentication result. A server device equipped with the following features.
[0164] [Note 2] The aforementioned purchase ticket information includes information about the event venue, the date of the event, and the time slots during which entry to the event venue is permitted. The authentication means determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period in association with the identified person to be authenticated that allows entry to the event venue, and the received current location falls within a predetermined range centered on the event venue, as described in Appendix 1.
[0165] [Note 3] The storage means further stores the terminal ID of the terminal used by each of the multiple ticket purchasers when they purchased the ticket. The authentication means is a server device as described in Appendix 2, which receives a terminal ID from the terminal of the person to be authenticated and authenticates the identified person to be authenticated based on the purchase ticket information of the identified person to be authenticated, the current location of the terminal, the authentication time, and the terminal ID.
[0166] [Note 4] The authentication means determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period in association with the identified person to be authenticated during which entry into the event venue is permitted, the received current location falls within a predetermined range centered on the event venue, and the terminal ID stored in association with the identified person to be authenticated matches the terminal ID received from the person to be authenticated. This is the server device described in Appendix 3.
[0167] [Note 5] The system further includes sales control means for controlling ticket sales, The sales control means, after selling the ticket, performs identity verification of the ticket purchaser. The storage means is a server device according to any one of the appendices 1 to 4, which stores the biometric information of the ticket purchaser who has successfully verified their identity in association with the purchased ticket information.
[0168] [Note 6] The sales control means is a server device as described in Appendix 5, which performs the identity verification using biometric information obtained from identity verification documents.
[0169] [Note 7] The sales control means is a server device as described in Appendix 5 that performs identity verification using facial images obtained from facial VCs (Verifiable Credentials).
[0170] [Note 8] The authenticated user's device and Server device, Includes, The server device is A storage means that associates the biometric information of multiple ticket purchasers with the purchase information of the tickets they purchased, Authentication means that receives biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the terminal of the person to be authenticated, performs a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticates the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notifies the terminal of the authentication result. A system that includes these features.
[0171] [Note 9] The aforementioned purchase ticket information includes information about the event venue, the date of the event, and the time slots during which entry to the event venue is permitted. The authentication means determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period in association with the identified person to be authenticated that allows entry to the event venue, and the received current location falls within a predetermined range centered on the event venue, as described in Appendix 8.
[0172] [Note 10] The storage means further stores the terminal ID of the terminal used by each of the multiple ticket purchasers when they purchased the ticket. The authentication means receives a terminal ID from the authenticated person's terminal and authenticates the identified authenticated person based on the identified authenticated person's purchased ticket information, the current location of the terminal, the authentication time, and the terminal ID, as described in Appendix 9.
[0173] [Note 11] The authentication means determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period in association with the identified person to be authenticated during which entry into the event venue is permitted, the received current location falls within a predetermined range centered on the event venue, and the terminal ID stored in association with the identified person to be authenticated matches the terminal ID received from the person to be authenticated. This is the system described in Appendix 10.
[0174] [Note 12] The system further includes sales control means for controlling ticket sales, The sales control means, after selling the ticket, performs identity verification of the ticket purchaser. The storage means stores the biometric information of the ticket purchaser who has successfully verified their identity in association with the purchased ticket information, as described in any one of the appendices 8 to 11.
[0175] [Note 13] The sales control means is the system described in Appendix 12, which performs the identity verification using biometric information obtained from identity verification documents.
[0176] [Note 14] The sales control means is the system described in Appendix 12 that performs identity verification using facial images obtained from facial VCs (Verifiable Credentials).
[0177] [Note 15] A memory process that associates the biometric information of multiple ticket purchasers with the ticket purchase information of each ticket purchaser, The authentication process involves receiving biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the person to be authenticated's terminal, performing a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticating the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notifying the terminal of the authentication result. A control method for a server device, comprising the following features.
[0178] [Note 16] The aforementioned purchase ticket information includes information about the event venue, the date of the event, and the time slots during which entry to the event venue is permitted. The server device control method described in Appendix 15, wherein the authentication step determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period in association with the identified person to be authenticated that allows entry to the event venue, and the received current location falls within a predetermined range centered on the event venue.
[0179] [Note 17] The storage step further stores the terminal ID of the terminal used by each of the multiple ticket purchasers when they purchased the ticket. The authentication step involves receiving a terminal ID from the authenticated person's terminal and authenticating the identified authenticated person based on the identified authenticated person's purchase ticket information, the current location of the terminal, the authentication time, and the terminal ID, as described in Appendix 16.
[0180] [Note 18] The server device control method described in Appendix 17, wherein the authentication step determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period during which the person to be authenticated can enter the event venue stored in association with the identified person to be authenticated, the received current location falls within a predetermined range centered on the event venue, and the terminal ID stored in association with the identified person to be authenticated matches the terminal ID received from the person to be authenticated's terminal.
[0181] [Note 19] It further includes a sales control process that controls ticket sales, The sales control process, after selling the ticket, performs identity verification of the ticket purchaser. The control method for a server device according to any one of the appendices 15 to 18, wherein the storage step stores the biometric information of the ticket purchaser who has successfully verified their identity in association with the purchased ticket information.
[0182] [Note 20] The sales control process is a control method for the server device described in Appendix 19, which performs the identity verification using biometric information obtained from identity verification documents.
[0183] [Note 21] The sales control step is a control method for the server device described in Appendix 19, which performs identity verification using facial images obtained from facial VCs (Verifiable Credentials).
[0184] [Note 22] The computer installed in the server device The system stores and associates the biometric information of multiple ticket purchasers with the ticket purchase information associated with those purchases, and performs memory processing. The authentication process involves receiving biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the person to be authenticated's terminal, performing a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticating the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notifying the terminal of the authentication result. A program to execute.
[0185] [Note 23] The aforementioned purchase ticket information includes information about the event venue, the date of the event, and the time slots during which entry to the event venue is permitted. The authentication process is the program described in Appendix 22, which determines that the authentication of the identified person has been successfully performed if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period in association with the identified person to be authenticated during which entry into the event venue is permitted, and the received current location falls within a predetermined range centered on the event venue.
[0186] [Note 24] The aforementioned storage process further stores the terminal ID of the terminal used by each of the multiple ticket purchasers when they purchased the ticket. The authentication process is a program as described in Appendix 23, which receives a terminal ID from the authenticated person's terminal and authenticates the identified authenticated person based on the identified authenticated person's purchased ticket information, the current location of the terminal, the authentication time, and the terminal ID.
[0187] [Note 25] The authentication process is the program described in Appendix 24, which determines that the authentication of the identified person has been successfully performed if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period during which the person to be authenticated can enter the event venue stored in association with the identified person to be authenticated, the received current location falls within a predetermined range centered on the event venue, and the terminal ID stored in association with the identified person to be authenticated matches the terminal ID received from the person to be authenticated's terminal.
[0188] [Note 26] It further includes sales control processing to control ticket sales, The aforementioned sales control process performs identity verification of the ticket purchaser after the ticket has been sold. The memory processing is a program according to any one of the appendices 22 to 25, which stores the biometric information of the ticket purchaser who has successfully verified their identity in association with the purchased ticket information.
[0189] [Note 27] The sales control process is the program described in Appendix 26, which performs the identity verification using biometric information obtained from identity verification documents.
[0190] [Note 28] The sales control process is the program described in Appendix 26 that performs identity verification using facial images obtained from facial VCs (Verifiable Credentials).
[0191] Furthermore, some or all of the configurations described in Appendices 2 to 7, which are subordinate to Appendice 1 above, may also be subordinate to Appendices 8, 15, and 22 in the same way as those described in Appendices 2 to 7. Moreover, not limited to Appendices 1, 8, 15, and 22, some or all of the configurations described as appendices may also be subordinate to various hardware, software, various recording means for recording software, or systems, without departing from the embodiments described above.
[0192] Furthermore, each disclosure of the above-mentioned prior art documents cited herein is incorporated herein by reference. Although 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. That is, the present invention naturally includes the entire disclosure, including the claims, and various modifications and alterations that can be made by those skilled in the art in accordance with the technical idea. [Explanation of Symbols]
[0193] 10 Server devices 20 devices 100 Server Devices 101 Memory means 102 Authentication methods 201 Communication Control Unit 202 Account Control Unit 203 Sales Control Unit 204 Certification Department 205 Storage section 301 Communication Control Unit 302 Authentication Control Unit 303 Storage section 311 Processors 312 memory 313 Input / Output Interfaces 314 Communication Interface
Claims
1. A storage means that associates the biometric information of multiple ticket purchasers with the purchase information of the tickets they purchased, Authentication means that receive biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the person to be authenticated's terminal, perform a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticate the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notify the terminal of the authentication result. A server device equipped with the following features.
2. The aforementioned purchase ticket information includes information about the event venue, the date of the event, and the time slots during which entry to the event venue is permitted. The server device according to claim 1, wherein the authentication means determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period stored in association with the identified person to be authenticated during which entry into the event venue is permitted, and the received current location falls within a predetermined range centered on the event venue.
3. The storage means further stores the terminal ID of the terminal used by each of the multiple ticket purchasers when they purchased the ticket. The server device according to claim 2, wherein the authentication means receives a terminal ID from the terminal of the person to be authenticated and authenticates the identified person to be authenticated based on the purchase ticket information of the identified person to be authenticated, the current location of the terminal, the authentication time, and the terminal ID.
4. The server device according to claim 3, wherein the authentication means determines that the authentication of the identified person has been successful if the authentication date of the person to be authenticated matches the event date stored in association with the identified person to be authenticated, the authentication time of the person to be authenticated falls within the time period during which the person to be authenticated can enter the event venue stored in association with the identified person to be authenticated, the received current location falls within a predetermined range centered on the event venue, and the terminal ID stored in association with the identified person to be authenticated matches the terminal ID received from the person to be authenticated's terminal.
5. The system further includes sales control means for controlling ticket sales, The sales control means, after selling the ticket, performs identity verification of the ticket purchaser. The server device according to any one of claims 1 to 4, wherein the storage means stores the biometric information of the ticket purchaser who has successfully verified their identity in association with the purchased ticket information.
6. The server device according to claim 5, wherein the sales control means performs the identity verification using biometric information obtained from identity verification documents.
7. The server device according to claim 5, wherein the sales control means performs identity verification using facial images obtained from facial VCs (Verifiable Credentials).
8. The authenticated user's device and Server device, Includes, The server device is A storage means that associates the biometric information of multiple ticket purchasers with the purchase information of the tickets they purchased, Authentication means that receives biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the terminal of the person to be authenticated, performs a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticates the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notifies the terminal of the authentication result. A system that includes these features.
9. A memory process that associates the biometric information of multiple ticket purchasers with the ticket purchase information of each ticket purchaser, The authentication process involves receiving biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the person to be authenticated's terminal, performing a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticating the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notifying the terminal of the authentication result. A control method for a server device, comprising the following features.
10. The computer installed in the server device The system stores and associates the biometric information of multiple ticket purchasers with the ticket purchase information associated with those purchases, and performs memory processing. The authentication process involves receiving biometric information of the person to be authenticated, information regarding the current location of the terminal, and information regarding the date and time of authentication from the person to be authenticated's terminal, performing a matching process using the received biometric information and the stored multiple biometric information to identify the person to be authenticated from among the multiple ticket purchasers, authenticating the identified person to be authenticated based on the purchased ticket information of the identified person to be authenticated, the received information regarding the current location, and the information regarding the date and time of authentication, and notifying the terminal of the authentication result. A program to execute.