Ticket issuance system and program

Abstract

To provide a ticket issuing system, a ticket examination device, and a program for issuing tickets that can smoothly verify the identity of a user while taking into consideration the protection of personal information.SOLUTION: A ticket issuing system includes the steps of: acquiring a feature amount table for storing feature amount data including feature information concerning exemplary biometric information and a feature ID for identifying the feature amount data, and feature information concerning biometric information of a user of a ticket to be issued (S110); identifying, from among the feature amount data stored in the feature amount table, similar feature amount data whose degree of similarity with the feature information concerning the acquired biometric information satisfies a predetermined criterion (S120); acquiring a feature ID corresponding to the similar feature amount data (S130); and issuing a ticket that records authentication information including the feature ID corresponding to the acquired similar feature amount data (S160).SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to a ticket issuing system for issuing tickets used for admission to entertainment and the like, a ticket inspection device for inspecting tickets issued by the ticket issuing system, and a program for realizing these by a computer.

Background Art

[0002] Recently, illegal reselling of various entertainment tickets has become a problem. Therefore, information of the legitimate ticket holder (for example, biometric information such as face image, fingerprint, iris, vein, myoelectric potential, etc. that can identify an individual) is recorded on the ticket, and when entering the entertainment venue, it is proposed to confirm whether the person trying to enter using the ticket is the true holder of the ticket. For example, in Patent Document 1, information indicating the face of the ticket holder or the feature amount of the ticket holder's own face is recorded as information of the legitimate holder, the face of the person trying to enter at the entrance is photographed, and it is disclosed that it is confirmed whether the person trying to enter is the legitimate holder by face authentication that collates with the face of the ticket holder or the feature amount of the ticket holder's own face recorded on the ticket. In the following description, coupons, stamp cards, event tickets, product exchange tickets, etc. are collectively referred to as "tickets".

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Conventional methods for verifying ticket holders using facial recognition, such as the method disclosed in Patent Document 1, record facial images and facial features on the ticket as information about the legitimate holder's face. Since facial images and facial features are the personal information of the holder, recording them on the ticket raises concerns from the perspective of protecting personal information and security, as personal information could be unintentionally passed on to third parties. If data recorded on a large number of tickets is analyzed and the information of the legitimate holder (or a method for identifying them) necessary for facial recognition is deciphered, it may become possible to fraudulently create tickets. Furthermore, facial images contain a large amount of information, and even if only features are recorded to reduce the amount of information, reading and matching the information during ticket inspection can take time, hindering the smooth processing of entrants and potentially causing congestion and delays. In addition, there are methods to enhance personal authentication using electronic tickets with smartphones, but various problems such as not being applicable to users without smartphones and inconveniences arising when the battery runs out have hindered their widespread adoption. [Means for solving the problem]

[0005] The ticket issuing system according to an embodiment of the present invention was made to solve the above problems and comprises: a feature table that stores feature data including characteristic information relating to exemplary biometric information and a feature ID for identifying said feature data in association with each other; a user feature information acquisition means that acquires feature information relating to the biometric information of the user of the ticket to be issued; a similar feature data identification means that identifies similar feature data from among the feature data stored in the feature table whose similarity to the biometric information feature information acquired by the user feature information acquisition means satisfies a predetermined standard, and acquires a feature ID corresponding to said similar feature data; and a ticket issuing means that issues a ticket on which authentication information including a feature ID corresponding to the similar feature data acquired by the similar feature data identification means is recorded.

[0006] In this invention, the characteristic information relating to biological information may be characteristic information relating to the appearance of a person's face. Furthermore, the authentication information may include a feature ID corresponding to multiple feature data. In addition to the feature ID, the authentication information may also include a ticket ID for identifying the ticket and / or information about the performance that can be entered with the ticket.

[0007] In this invention, the ticketing means may record the feature ID on the ticket surface in a manner that allows for machine reading. Furthermore, the feature data stored in the feature table may include feature information relating to the appearance of a fictitious person's face.

[0008] In the present invention, the ticket issuance system may further include a feature data registration means, which, when the similar feature data identification means cannot identify similar feature data from among the feature data stored in the feature table that has a degree of agreement with the feature information relating to biometric information acquired by the user feature information acquisition means of a predetermined value or higher, registers new feature data in the feature table based on the biometric information acquired by the user feature information acquisition means that has a degree of agreement with the biometric information acquired by the user feature information acquisition means of a predetermined value or higher.

[0009] A ticket issuing system according to another embodiment of the present invention includes: a feature table that stores feature data including characteristic information relating to exemplary biometric information and a feature ID for identifying said feature data in association with each other; a user feature information acquisition means for acquiring feature information relating to the biometric information of the user of the ticket to be issued; a similar feature data identification means for identifying similar feature data from among the feature data stored in the feature table whose similarity to the biometric information feature information acquired by the user feature information acquisition means satisfies a predetermined standard, and acquiring the feature ID corresponding to said similar feature data; a ticket issuing means for issuing a ticket that records authentication information including a ticket ID for identifying the ticket to be issued; and a recording means for recording the feature ID corresponding to the similar feature data acquired by the similar feature data identification means in association with the ticket ID.

[0010] Furthermore, the ticket inspection device according to the embodiment of the present invention inspects the ticket held by a user who is about to pass through a ticket inspection station. The ticket inspection device includes a feature table that stores feature data, which is characteristic information relating to exemplary biometric information, in association with identification information; a user biometric information acquisition means that acquires the biometric information of a user using the ticket; a feature information calculation means that calculates feature information for the biometric information of the user acquired by the user biometric information acquisition means; an identification information acquisition means that acquires identification information recorded on the ticket; a comparison feature data acquisition means that obtains feature data associated with the identification information acquired by the identification information acquisition means by querying the feature table; and a determination means that determines the degree of agreement between the feature information calculated by the feature information calculation means and the feature data acquired by the comparison feature data acquisition means, and outputs a determination result according to the degree of agreement.

[0011] In this invention, the characteristic information relating to biological information may be characteristic information relating to the appearance of a human face.

[0012] In the present invention, the ticket inspection device may further include: similar feature data identification means, which, when identification information is not recorded on the ticket, identifies similar feature data from among the feature data stored in the feature table whose degree of agreement with the feature information related to biometric information acquired by the feature information calculation means is equal to or greater than a predetermined value, and acquires identification information corresponding to the similar feature data; and similar feature data recording means, which records the identification information corresponding to the similar feature data identified by the similar feature data identification means as similar feature data corresponding to the ticket.

[0013] In this invention, the identification information is preferably recorded on the ticket in a manner that allows it to be read by a machine. The identification information acquisition means is preferably obtained by reading the identification information recorded on the ticket held by the user.

[0014] In the present invention, the means for acquiring user biometric information and the means for acquiring identification information are implemented by a common imaging means, which acquires a user image including the user's face and the ticket the user is holding, and the means for acquiring identification information reads the identification information recorded on the ticket the user is holding by analyzing the user image captured by the imaging means. At this time, the feature information calculation means recognizes the face that appears in a predetermined position on the ticket surface in the user image as the face of the person entering, and calculates feature information regarding the appearance of that face.

[0015] In the present invention, the means for acquiring user biometric information is implemented by an imaging means, which acquires a user image including the user's face, identifies the user in the user image based on the distance from the imaging means to the person in the user image, and acquires their biometric information.

[0016] Furthermore, another embodiment of the present invention is a ticket inspection device that inspects the tickets held by a user attempting to pass through a ticket inspection station. The ticket inspection device includes a feature table that stores feature data, which is characteristic information relating to exemplary biometric information, in association with feature IDs; a ticket information table that stores a ticket ID for identifying a ticket in association with the feature ID corresponding to the user of the ticket; a user biometric information acquisition means for acquiring the biometric information of the user using the ticket; a feature information calculation means for calculating feature information for the biometric information of the user acquired by the user biometric information acquisition means; a ticket ID acquisition means for acquiring the ticket ID recorded on the ticket; a comparison feature data acquisition means for identifying the feature ID associated with the ticket ID acquired by the ticket ID acquisition means by querying the ticket information table, and acquiring the feature data corresponding to the identified feature ID by querying the feature table; and a determination means for determining the similarity between the feature information calculated by the feature information calculation means and the feature data acquired by the comparison feature data acquisition means, and outputting a determination result according to the similarity.

[0017] The program according to an embodiment of the present invention causes a computer to function as any of the above ticket issuing systems. Further, the program according to an embodiment of the present invention causes a computer to function as any of the above ticket checking devices.

Brief Explanation of Drawings

[0018] [Figure 1] It is a schematic diagram showing the configuration of a ticket issuing system. [Figure 2] It is a block diagram showing the configuration of a server. [Figure 3] It is a block diagram showing the configuration of a ticket purchase terminal. [Figure 4] It is a block diagram showing the configuration of a ticket issuing machine. [Figure 5] It is a block diagram showing the configuration of a ticket checking device. [Figure 6] It is a flowchart showing the procedure of ticket issuing processing. [Figure 7] It shows an example of the ticket face of a ticket issued by a ticket issuing system. [Figure 8] It is a flowchart showing the procedure of ticket checking processing. [Figure 9] It shows an example of the display on the display unit of the ticket checking device. [Figure 10] It is a flowchart showing the procedure of ticket checking processing in the third embodiment. [Figure 11] It is a flowchart showing the procedure of ticket checking processing in the fourth embodiment. [Figure 12] It is a flowchart showing the procedure of ticket issuing processing in the fifth embodiment. [Figure 13] It is a flowchart showing the procedure of ticket checking processing in the fifth embodiment.

Modes for Carrying Out the Invention

[0019] 〔First Embodiment〕 Hereinafter, a ticket issuing system 1 according to the first embodiment of the present invention and a ticket inspection device 5 for inspecting tickets issued by the ticket issuing system 1 will be described with reference to the drawings.

[0020] Figure 1 is a schematic diagram showing the configuration of the ticket issuance system 1. As shown in Figure 1, the ticket issuance system 1 comprises a server 2, a ticket purchase terminal 3, and a ticket issuing machine 4. The server 2, the ticket purchase terminal 3, and the ticket issuing machine 4 are connected to each other via a network NW. The server 2, the ticket purchase terminal 3, and the ticket issuing machine 4 may be located in physically separate remote locations, or some or all of them may be located in the same location.

[0021] Server 2 is, for example, a computer system, and consists of an input / output device such as a keyboard, mouse, and touch panel, a processing unit such as a CPU (Central Processing Unit), a storage device such as RAM (Random Access Memory) and ROM (read-only memory), and a display device such as a CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display).

[0022] Figure 2 is a block diagram showing the configuration of Server 2. As shown in Figure 2, Server 2 comprises at least a control unit 20, a storage unit 22, and a communication unit 24. In addition to these, Server 2 may also be equipped with input means (e.g., keyboard, mouse, etc.) and output means (e.g., display, printer, etc.) as needed.

[0023] The control unit 20 executes processing according to a program stored in the storage unit 22 based on requests transmitted from the ticket purchase terminal 3. For example, the control unit 20 may perform processes such as searching for, registering, deleting, and updating data in the ticket database 22A and feature table 22B stored in the storage unit 22, or it may perform a process to find feature data from the feature table 22B in which the similarity between the ticket holder's face image (hereinafter, the face image may simply be referred to as "face image") and the feature data satisfies a predetermined criterion (for example, the degree of similarity is greater than or equal to a predetermined value). In other words, the control unit 20 functions as a similar feature data identification means that identifies similar feature data from among the feature data stored in the feature table 22B in which the similarity to the user's face image satisfies a predetermined criterion, and obtains a feature ID corresponding to the similar feature data, based on a program stored in the storage unit 22. Furthermore, the control unit 20 functions as a feature data registration means that, based on a program stored in the memory unit 22, if it cannot identify similar feature data from the feature data stored in the feature table 22B that meets a predetermined standard of similarity to the user's face image, it registers new feature data that meets a predetermined standard of similarity to the user's face image in the feature table 22B based on the user's face image.

[0024] The memory unit 22 stores programs executed by the control unit 20 and data used in those programs. For example, the memory unit 22 stores programs for realizing the functions of the server 2 in the ticket issuance system 1, a ticket database 22A that aggregates information related to tickets issued by the ticket issuance system 1, and a feature table 22B that stores feature data including characteristic information related to exemplary biometric information, associated with a feature ID which is identification information. In this embodiment, the feature information related to biometric information included in the feature data is feature information related to the appearance of a person's face (for example, feature parameter values). The feature table 22B may include feature data based on images of non-existent people's faces (for example, information representing facial features calculated from faces generated by drawings or computer graphics). The feature table 22B may also include feature data generated by calculation without being based on facial images. When generating feature data by calculation, it is preferable to generate the feature data so that the feature data is distributed with equal density within the feature space that can be represented by the feature data. The server 2 does not have to be configured with each of the above components as a single physical unit. For example, some or all of the above components may be distributed across remote locations, and they can work together to function as server 2. The communication unit 24 communicates with the ticket purchase terminal 3, ticket issuing machine 4, etc., via the network NW under the control of the control unit 20.

[0025] The ticket purchase terminal 3 is a device operated by the purchaser or a ticket vendor when purchasing a ticket, to send the information necessary for ticket issuance to the server 2. Here, the information necessary for ticket issuance includes at least information about the ticket to be purchased and a facial image of the person who will be the holder of the purchased ticket (typically the purchaser). The ticket purchase terminal 3 may be, for example, a terminal device installed at a ticket vendor, or it may be a computer owned by an individual purchaser.

[0026] Figure 3 is a block diagram showing the configuration of the ticket purchase terminal 3. As shown in Figure 3, the ticket purchase terminal 3 comprises at least an operation unit 30, a storage unit 31, a control unit 32, a communication unit 33, a display unit 34, and a camera 35. The ticket purchase terminal 3 may be, for example, a notebook computer or tablet terminal with a built-in camera 35, or a computer without a built-in camera 35 may be used with the camera 35 connected to it. In this embodiment, the camera 35 functions as part of a user characteristic information acquisition means that acquires characteristic information relating to the biometric information of the user of the issued ticket.

[0027] The operation unit 30 accepts operations from the purchaser or the ticket sales office staff. The operation unit 30 includes a touch panel superimposed on the display unit 34 and other buttons. The storage unit 31 is a storage medium such as ROM, RAM, or hard disk, and stores programs executed by the control unit 32 and data used by those programs. For example, the storage unit 31 stores the operating system (OS), application programs for transmitting information necessary for purchasing and issuing tickets to the server 2, etc. The control unit 32 is an arithmetic unit such as a CPU, and executes various programs stored in the storage unit 31. The communication unit 33 communicates with the server 2 via the network NW. The display unit 34 is a display element such as a liquid crystal display or organic EL display, and under the control of the control unit 32, displays various information (for example, a user interface for purchasing tickets). The display unit 34 works in cooperation with the touch panel of the operation unit 30 to realize various input interfaces.

[0028] The ticketing machine 4 issues tickets by printing ticket information on a predetermined form based on commands from the server 2. The ticketing machine 4 records authentication information, including a feature ID (identification information) corresponding to similar feature data, on the ticket surface in a machine-readable manner, along with other information such as information on the performances that can be entered with the ticket. Specifically, the feature ID, etc., is encoded into a QR code (registered trademark) and printed on the ticket surface. The ticketing machine 4 is preferably located in the same place as the ticket purchase terminal 3 (for example, a ticket sales office). Figure 4 is a block diagram showing the configuration of the ticketing machine 4. As shown in Figure 4, the ticketing machine 4 comprises at least a storage unit 40, a control unit 42, a communication unit 44, and a printing unit 46. In addition to these, the ticketing machine 4 may also be equipped with input means (e.g., keyboard, mouse, etc.) and output means (e.g., display, printer, etc.) as needed.

[0029] The memory unit 40 stores programs executed by the control unit 42, as well as data used by those programs. For example, the memory unit 40 stores a program that controls the printing unit 46 to print ticket information based on instructions from the server 2.

[0030] The control unit 42 executes various programs stored in the memory unit 40. For example, the control unit 42 controls the printing unit 46 to print tickets in response to commands from the server 2.

[0031] The communication unit 44 communicates with the server 2 via the network NW. In addition, the communication unit 44 may be configured to enable near-field communication (NFC), infrared communication, visible light communication, etc. The printing unit 46 is a printer that prints tickets on predetermined paper. The ticket paper may be, for example, pre-cut to predetermined dimensions and perforated as needed, or roll paper may be used and cut to a predetermined length each time printing is required.

[0032] The ticket inspection device 5 is a device for checking the tickets held by users attempting to pass through a ticket inspection station. In this example, the ticket inspection device 5 checks tickets issued by the ticket issuance system 1 at a ticket inspection station set up at the entrance to the performance. Figure 5 is a block diagram showing the configuration of the ticket inspection device 5. The ticket inspection device 5 comprises a control unit 51, a storage unit 52, a display unit 53, a communication unit 54, and a camera 55. In addition to these, the ticket inspection device 5 may also be equipped with input means (e.g., keyboard, mouse, etc.) as needed. The ticket inspection device 5 may use a notebook computer, tablet terminal, etc., with a built-in camera 55.

[0033] The control unit 51 is an arithmetic unit such as a CPU, and executes various programs stored in the storage unit 52. The storage unit 52 is a storage medium such as ROM, RAM, or hard disk, and stores programs executed by the control unit 51 and data used by those programs. For example, the storage unit 52 stores the operating system (OS), a program for ticket inspection processing, and the ticket inspection feature table 52A. The ticket inspection feature table 52A is a database that stores feature data, which is information indicating the characteristics of a person's face, in association with feature IDs, which are identification information. The ticket inspection feature table 52A may use the feature table 22B used by the server 2 at the time of ticketing as is (including those that were not identified as similar feature data at the time of ticketing), or it may store only the feature data that was identified as similar feature data at the time of ticketing.

[0034] The display unit 53 is a display element such as a liquid crystal display or an organic EL display, and displays various information under the control of the control unit 51. The communication unit 54 communicates with the server 2, etc. via the network NW. The camera 55 corresponds to the means for acquiring user biometric information in the present invention, and is positioned to photograph the front of the ticket inspection device 5, and captures a user image including the face of the user using the ticket and the ticket held by the user. The red light 56 ​​is an example of a notification means that operates under the control of the control unit 51, and is controlled to light up, for example, when the similarity between the face image extracted from the user image and the feature data obtained from the ticket inspection feature table does not meet a predetermined standard (for example, when the degree of similarity does not exceed a predetermined value).

[0035] The control unit 51 extracts the user's face image from the user image captured by the camera 55, based on a program stored in the memory unit 52. The control unit 51 also analyzes the user image captured by the camera 55 to read the QR code recorded on the ticket held by the user, based on a program stored in the memory unit 52, and obtains the feature ID encoded in the QR code. The control unit 51 also queries the ticket inspection feature table 52A to obtain feature data associated with the obtained feature ID, based on a program stored in the memory unit 52. The control unit 51 also calculates the similarity between the face image extracted from the user image and the feature data obtained from the ticket inspection feature table, based on a program stored in the memory unit 52, and permits the user to pass through the ticket inspection station if the similarity meets a predetermined standard. In this way, the control unit 51 realizes the functions of the feature information calculation means, identification information acquisition means, face image acquisition means, and determination means of the present invention by executing the program stored in the memory unit 52.

[0036] [Ticket Issuance] Next, referring to the flowchart shown in Figure 6, the procedure for issuing tickets using the ticket issuance system 1 configured as described above will be explained.

[0037] In this example, tickets are issued when the purchaser or a ticket vendor operates the ticket purchase terminal 3. This example explains the case where the purchaser themselves is the user of the ticket (i.e., the person who uses the ticket to enter the venue). First, the purchaser or a ticket vendor selects the venue, seat type, etc., on the ticket purchase terminal 3 and performs a purchase operation, such as pressing the purchase button (step S100). The ticket purchase terminal 3 sends the selected ticket information and the user's facial image to the server 2, which retrieves them (step S110). The facial image may be taken by the camera 35 of the ticket purchase terminal 3, or it may be an image that the user has taken in advance and is imported into the ticket purchase terminal 3 via wired or wireless communication.

[0038] Server 2 queries the feature table 22B with the user's face image received from the ticket purchase terminal 3 (step S120). At this time, Server 2 calculates the similarity between each feature data stored in the feature table 22B and the user's face using an arbitrary face matching method. It is preferable to extract feature information from the face image and calculate the degree of similarity based on the extracted features and the feature information contained in the feature data. The similarity is calculated as a score normalized to a value from 0 to 10, for example. If there is feature data whose similarity to the user's face image meets a predetermined criterion (step S120; Yes), Server 2 identifies one similar feature data whose similarity to the user's face image meets the predetermined criterion and obtains the feature ID corresponding to the identified similar feature data (step S130). It is preferable that Server 2 completely deletes the user's face image from Server 2 after identifying the similar feature data.

[0039] Server 2 may calculate the degree of similarity between the user's face image and all the feature data included in feature table 22B, and identify the feature data with the highest degree of similarity as satisfying a predetermined condition. Alternatively, it may query the feature data one by one in any order, and when it finds a feature data whose similarity satisfies a predetermined condition (for example, a degree of similarity equal to or greater than a predetermined value), it may identify that feature data as a similar feature data and refrain from further querying. Identifying the one with the highest degree of similarity takes time to complete, but it can improve the accuracy of authentication. If further querying is not performed when feature data that satisfies a predetermined condition is found, the accuracy of authentication may be sacrificed, but it is possible to complete the process in a short time.

[0040] If the feature data in the feature table 22B does not contain any feature data that meets a predetermined criterion for similarity to the user's face image (step S120; No), the server 2 registers new feature data based on the user's face image in the feature table 22B (step S140), identifies the new feature data as similar feature data, and obtains its feature ID (step S130).

[0041] When registering new feature data in step S140, server 2 may register information indicating facial features calculated from the user's face image itself as feature data. However, it is preferable to generate and register feature data that satisfies a predetermined standard of similarity to the user's face image, rather than the user's face image itself. Specifically, it is preferable to generate feature data that has a degree of agreement with the user's face image of a predetermined value or higher, but does not perfectly match (there are parts that are moderately dissimilar). In this way, the user's face image, which is personal information, is not directly included in the feature table 22B, and operation can be carried out with consideration for privacy.

[0042] Once similar feature data is identified, server 2 stores the feature ID of the identified similar feature data in the ticket database 22A, linking it to the information of the ticket to be purchased (step S150).

[0043] Next, Server 2 generates the information to be printed on the ticket and sends it to the ticket machine 4 (step S160). The information to be printed on the ticket includes authentication information required for ticket inspection upon entry, event information, ticket type information, etc. In this example, the authentication information is a QR code (registered trademark) containing the feature ID of similar feature data.

[0044] As shown in Figure 7, the ticketing machine 4, having received the information to be printed on the ticket, prints on the ticket the text containing information about the event, the type of ticket, and a QR code containing authentication information.

[0045] As described above, tickets issued in this manner do not contain personal information such as the user's facial image in the authentication information, thus preventing the leakage of personal information via tickets. Furthermore, the feature ID of the similar feature data is smaller in size compared to the facial image itself, allowing for quick reading of the authentication information when performing the ticket inspection process using the ticket inspection device 5 described later.

[0046] [Ticket Usage] Next, referring to the flowchart shown in Figure 8, we will explain the procedure for checking tickets issued by the ticket issuance system 1 for each individual attendee at the ticket inspection station set up at the entrance of the venue for events and other performances.

[0047] A ticket inspection station is set up at the entrance of the performance venue, and a ticket inspection device 5 is installed so that the camera 55 faces the direction from which attendees are entering. The ticket inspection device 5 has a ticket inspection feature table 52A that stores the feature data used when issuing tickets, stored in advance (before the start of admission). The ticket inspection device 5 may receive a copy of the feature table 22B from the server 2 via the communication unit 54 and use this as the ticket inspection feature table 52A.

[0048] When entry begins, the ticket inspection device 5 starts taking pictures with the camera 55 (step S200). At this time, the person entering with a ticket stands in front of the ticket inspection device 5 so that both the ticket and their face are photographed simultaneously. At this time, as shown in Figure 9, the display unit 53 of the ticket inspection device 5 may display instructions to hold the ticket close to the face, the image being taken by the camera 55, and the authentication result. Alternatively, the device may be configured to photograph the ticket and the person's face sequentially rather than simultaneously. Furthermore, the control unit 51 may be configured to instruct the person to remove glasses, sunglasses, a mask, etc., if it recognizes from the image being taken by the camera 55 that the person is wearing them.

[0049] The control unit 51 of the ticket inspection device 5 recognizes a face and a QR code from the image (user image) captured by the camera 55 (step S210). The control unit 51 then analyzes the recognized QR code to obtain a feature ID included in the authentication information (step S220). Next, it obtains feature data corresponding to the obtained feature ID from the ticket inspection feature table 52A (step S230). The control unit 51 then calculates the similarity between the face contained in the video captured by the camera 55 and the obtained feature data (step S240).

[0050] When inspecting tickets, it is advisable to fix the positional relationship between the face and the ticket, such as by positioning the ticket below the face, when taking the photograph. The system should then recognize and extract the face of the person entering the facility that is positioned in a predetermined location relative to the ticket. Alternatively, the system may recognize the face of the person entering the facility based on the distance from the ticket inspection device 5 (depth in the user's image). For example, the system may be equipped with a distance sensor to measure the distance to the person entering the facility, or it may recognize the face of the person entering the facility as the one that occupies the largest area of ​​the image among multiple faces in the user's image. In this way, even if multiple people are captured in the video, the person to be authenticated can be easily identified. The ticket inspection device 5 may be configured to authenticate multiple people simultaneously. In this case, the system should authenticate a number of people corresponding to the number of QR codes recognized, and the face recognized in a predetermined location relative to the QR code (for example, above the QR code) should be the target of authentication.

[0051] Next, the control unit 51 determines whether the calculated similarity meets a predetermined standard (the standard may be lower than that at the time of ticket issuance) (step S250). The determination in step S250 is an example of a determination according to the similarity in the present invention. If the similarity meets a predetermined standard (for example, if the degree of match is equal to or greater than a predetermined value) (step S250; Yes), a message indicating that entry is permitted is displayed on the display unit 53 (step S260). On the other hand, if the similarity does not meet a predetermined standard (for example, if the degree of match is less than a predetermined value) (step S250; No), a message indicating that entry is permitted is not displayed on the display unit 53, and the red light 56 ​​is illuminated to notify the staff of the facial recognition mismatch. In addition, for example, an alarm such as a warning display, a warning sound, or flashing light may be issued (step S270). Thus, the ticket inspection process for one entrant is completed after either step S260 or S270. Note that the output of the result when the similarity does not meet a predetermined standard is not limited to the above. For example, instead of issuing notifications or warnings, the system could display an entry permit on the display unit 53 to avoid congestion at the ticket inspection station, while notifying the ticket inspection station staff that the similarity does not meet the prescribed criteria, and allowing the staff to verify whether the entrant is fraudulent or not after passing through the ticket inspection station.

[0052] At the entrance to the event venue, the same process is carried out for each individual attendee. This configuration makes it possible to prevent fraudulent use or transfer of tickets while ensuring smooth ticket inspection at the entrance.

[0053] [Second Embodiment] Next, a second embodiment of the present invention will be described. The configuration of the ticket issuing system 1 and the ticket inspection device 5 according to this embodiment differs from that of the first embodiment in the following respects. Points that are not specifically mentioned below are the same as those in the first embodiment and will therefore not be described.

[0054] In the ticket issuance system 1 of this embodiment, the server 2 has a user information database 22C in the storage unit 22. This user information database 22C stores various information about the user (for example, date of birth, gender, address, telephone number, registration date, etc.) linked to a user ID that identifies the user. In this embodiment, the ticket database 22A stores the user ID of the user linked to the ticket ID of each ticket. Therefore, in this embodiment, by identifying the ticket ID, it is possible to refer to various attributes of the user via the user ID linked to the ticket ID.

[0055] Furthermore, in this embodiment, the ticket inspection device 5 is capable of communicating with the server 2 via the network NW. The ticket inspection process is then carried out while communication with the server 2 via the network NW is possible.

[0056] When purchasing and issuing tickets, the user ID is sent from the ticket purchase terminal 3 to the server 2 as one of the pieces of information required for ticket issuance. Server 2 records the user ID received from the ticket purchase terminal in the ticket database 22A, linking it to the ticket ID of the ticket being sold. In addition, Server 2 includes the ticket ID, along with the feature ID corresponding to the similar feature data, as authentication information. Then, a QR code containing this authentication information is printed on the ticket surface.

[0057] When a ticket is used, the ticket inspection device 5, located at the ticket inspection station, recognizes the QR code from the image on the ticket and analyzes it, similar to the first embodiment. It then obtains the feature ID and ticket ID included in the authentication information. With respect to the obtained feature ID, similar to the first embodiment, the similarity between the corresponding feature data and the captured facial image is calculated and used for authentication. On the other hand, with respect to the obtained ticket ID, the device queries the server 2 for information about the user associated with that ticket ID. Specifically, attribute information such as the user's age and gender associated with the ticket ID is obtained from the server 2. Then, the image of the entrant captured by the camera 55 is compared with the attribute information (i.e., it is determined whether the entrant possesses those attributes). The result of the attribute information comparison, similar to the result of the feature data comparison, can be used to determine whether or not the entrant is allowed to pass through the ticket inspection station. In this way, the possibility of passing through the ticket inspection station by fraudulent means such as impersonation can be reduced. Alternatively, instead of comparing attribute information as described above, the attribute information obtained from the server 2 may be presented to the staff at the ticket inspection station as reference information for visually identifying fraudulent entrants.

[0058] [Third Embodiment] Next, a third embodiment of the present invention will be described. The configuration of the ticket issuing system 1 and the ticket inspection device 5 according to this embodiment differs from the embodiments described above in the points described below. Points that are not specifically mentioned below are the same as in the first embodiment and will therefore not be described.

[0059] In the ticket issuance system 1 of this embodiment, the ticket database 22A stores a feature ID associated with the ticket ID of each ticket. Unlike the first embodiment and others, in this embodiment, the user's similar feature data does not need to be finalized before printing the ticket. If the user's similar feature data is finalized before printing the ticket, the feature ID corresponding to that similar feature data is associated with the ticket ID and stored in the ticket database 22A. In addition, authentication information including the feature ID (and, if necessary, the ticket ID, as in the second embodiment) is printed on the ticket surface as a QR code, similar to the first embodiment.

[0060] On the other hand, if the user's human-dex information has not been finalized by the time the ticket is printed, the ticket will have a QR code printed on it that includes information indicating that the characteristic ID is undetermined, along with the ticket ID.

[0061] Furthermore, in this embodiment, the ticket inspection device 5 is capable of communicating with the server 2 via the network NW. The ticket inspection process is then carried out while communication with the server 2 via the network NW is possible. The ticket inspection process in this embodiment will be described below with reference to the flowchart shown in Figure 10.

[0062] Similar to the first embodiment, a ticket inspection station is set up at the entrance to the performance venue, and the ticket inspection device 5 is installed so that the camera 55 faces the direction from which the attendees are entering. When entry begins, the ticket inspection device 5 starts taking pictures with the camera 55 (step S300). The images taken will include the ticket and the face of the attendee.

[0063] The control unit 51 of the ticket inspection device 5 recognizes the face and the QR code from the image (user image) captured by the camera 55 (step S305). Then, the control unit 51 analyzes the recognized QR code to obtain authentication information (step S310). The control unit 51 determines whether or not the authentication information contains the feature ID of the similar feature data (step S315).

[0064] If the feature ID of the similar feature data is not included in the authentication information (Step 315; No), the ticket inspection device 5 queries the server 2 to see if the feature ID is registered for the acquired ticket ID (Step S320). If the server 2 replies that the feature ID is not registered (Step S320; No), the ticket inspection device 5 sends the acquired ticket ID and the image of the entrant taken by the camera 55 to the server 2. Upon receiving this, the server 2 identifies the similar feature data from the feature table 22B using the same method as in the first embodiment, associates the feature ID corresponding to the similar feature data with the ticket ID, and stores it in the ticket database (Step S325). If the feature ID of the similar feature data is not included in the authentication information, the ticket inspection process is completed. As shown in the processing in Step S325, the server 2 functions as a similar feature data identification means and a similar feature data recording means in the present invention. The identification of similar feature data and the corresponding feature ID may be performed by the ticket inspection device 5 using the ticket inspection feature table 52A. In this case, the ticket inspection device 5 should send the ticket ID and the feature ID of the identified similar feature data to the server 2.

[0065] On the other hand, if server 2 responds that a feature ID is registered (step S320; Yes), ticket inspection device 5 obtains the feature ID associated with the ticket ID from server 2 (step S330) and obtains the feature data corresponding to the feature ID from the ticket inspection feature table 52A (step S335). Then, the control unit 51 of ticket inspection device 5 calculates the similarity between the face of the entrant included in the video captured by camera 55 and the obtained feature data (step S340). Subsequently, the control unit 51 determines whether the calculated similarity meets a predetermined standard (for example, whether the degree of agreement is equal to or greater than a predetermined value) (step S345). This determination in step S345 is an example of a determination based on similarity in the present invention. If the similarity meets the predetermined standard (step S345; Yes), a message indicating that entry is permitted is displayed on the display unit 53 (step S350). On the other hand, if the similarity does not meet the predetermined criteria (step S345; No), the display unit 53 will not show that entry is permitted, and the red light 56 ​​will be illuminated to notify the staff of the facial recognition mismatch. In addition, for example, an alarm may be issued, such as a warning display, a warning sound, or a flash of light (step S355). After either step S350 or S355, the ticket inspection process for one entrant is completed.

[0066] On the other hand, if the authentication information includes a feature ID from similar feature data (step 315; Yes), the processing in steps S335 to S355 is performed using that feature ID. That is, similar to the first embodiment, the passability of the ticket check is determined by authentication using similar feature data.

[0067] As described above, according to this embodiment, even if the similar feature data cannot be determined before printing the ticket, it becomes possible to associate the similar feature data with the ticket when the ticket is first passed through the ticket checkpoint, thereby preventing a different user from using the ticket during subsequent checks (e.g., re-entry).

[0068] In this embodiment, as in the second embodiment, the server 2 may have a user information database 22C in the storage unit 22, and store the user's face image (or feature ID obtained therefrom) acquired at the time of initial entry, linked to the user ID. The user's face image (or feature ID) stored in this manner may be used to generate authentication information when the user purchases a new ticket.

[0069] [Fourth Embodiment] Next, a fourth embodiment of the present invention will be described. The configuration of the ticket issuing system 1 and the ticket inspection device 5 according to this embodiment differs from the embodiments described above in the points described below. Points that are not specifically mentioned below are the same as in the first embodiment, etc., and therefore will not be explained.

[0070] In the first embodiment, tickets were printed on paper from a ticketing machine. However, in the ticketing system of this embodiment, instead of printing tickets on paper, the ticket image is displayed on a mobile device such as a smartphone, and this is used for ticket verification, employing what is known as an electronic ticket. Also, in this embodiment, as in the second embodiment, the storage unit 22 stores a user information database 22C and stores various information about the user (including at least information on the destination of the electronic ticket) linked to the user ID. The ticket database 22A stores the user ID of the ticket holder linked to the ticket ID.

[0071] Unlike the first embodiment, in this embodiment, the user's similar feature data does not need to be finalized by the time the ticket is used (i.e., when the ticket is inspected). If the user's similar feature data is finalized before the ticket inspection, authentication information including the feature ID corresponding to that similar feature data is recorded on the electronic ticket. The authentication information may be displayed as a QR code on the ticket and read by the inspection device 5 during inspection, or it may be transmitted to the inspection device 5 using wireless communication or the like without displaying the authentication information on the mobile terminal screen.

[0072] Once the user's similar feature data is finalized, the authentication information recorded on the electronic ticket will include a feature ID corresponding to the similar feature data. On the other hand, if the user's similar feature data is not yet finalized, the authentication information recorded on the electronic ticket will include information indicating that the feature ID is undetermined. Subsequently, once the similar feature data is finalized, the authentication information will be updated to include the feature ID corresponding to the similar feature data. For example, if the authentication information is displayed as a QR code on the ticket, the QR code displayed on the ticket will change before and after the similar feature data is finalized.

[0073] Next, the ticket inspection process in this embodiment will be explained with reference to the flowchart shown in Figure 11. In the following explanation, the example will be one in which the authentication information is displayed as a QR code on the ticket.

[0074] Similar to the first embodiment, a ticket inspection station is set up at the entrance to the performance venue, and the ticket inspection device 5 is installed so that the camera 55 faces the direction from which the attendees are entering. When entry begins, the ticket inspection device 5 starts taking pictures with the camera 55 (step S400). The images taken include the ticket displayed on the screen of the attendee's mobile device and the attendee's face.

[0075] The control unit 51 of the ticket inspection device 5 recognizes the face and the QR code from the image (user image) captured by the camera 55 (step S405). Then, the control unit 51 analyzes the recognized QR code to obtain authentication information (step S410). The control unit 51 determines whether or not the authentication information contains the feature ID of the similar feature data (step S415).

[0076] If the feature ID of the similar feature data is not included in the authentication information (step 415; No), the ticket inspection device 5 transmits the acquired ticket ID and the image of the entrant taken by the camera 55 to the server 2. Upon receiving this, the server 2 identifies the similar feature data from the feature table 22B using the same method as in the first embodiment (step S420). Alternatively, the ticket inspection device 5 may use the ticket inspection feature table 52A to identify the similar feature data and the corresponding feature ID. In this case, the ticket inspection device 5 should transmit the ticket ID and the feature ID of the identified similar feature data to the server 2. At this time, the server 2 may also store the feature ID corresponding to the similar feature data in the ticket database, linked to the ticket ID.

[0077] Next, Server 2 generates updated authentication information that includes feature IDs corresponding to the similar feature data and sends it to the user whose user ID is linked to the ticket ID (step S425). The user's mobile device updates the electronic ticket to use the received updated authentication information for subsequent ticket checks (step S430). If the feature IDs from the similar feature data are not included in the authentication information, the ticket check process ends here.

[0078] On the other hand, if the authentication information includes a feature ID of similar feature data (step 415; Yes), the feature data corresponding to that feature ID is obtained from the ticket inspection feature table 52A (step S435). The control unit 51 of the ticket inspection device 5 then calculates the similarity between the visitor's face included in the video captured by the camera 55 and the obtained feature data (step S440). Subsequently, the control unit 51 determines whether the calculated similarity meets a predetermined standard (for example, whether the degree of match is greater than or equal to a predetermined value) (step S445). This determination in step S445 is an example of a determination based on similarity in the present invention. If the similarity meets the predetermined standard (step S445; Yes), a message indicating that entry is permitted is displayed on the display unit 53 (step S450). On the other hand, if the similarity does not meet the predetermined standard (step S445; No), a message indicating that entry is permitted is not displayed on the display unit 53, and a red light 56 ​​is illuminated to notify the staff of the mismatch in facial recognition. In addition, warnings such as warning displays, warning sounds, and flashing lights may be issued (step S455). After either step S450 or S455, the ticket inspection process for one entrant is completed.

[0079] As described above, according to this embodiment, even if similar feature data cannot be determined by the time of the first ticket inspection, it becomes possible to link the similar feature data to the electronic ticket when passing through the ticket inspection point for the first time, thereby preventing a different user from using the ticket during subsequent ticket inspections (e.g., re-entry).

[0080] In this embodiment, as in the second embodiment, the server 2 may have a user information database 22C in the storage unit 22, and store the user's facial image (or feature ID obtained therefrom) acquired at the time of initial entry, linked to the user ID. The user's facial image (or feature ID) stored in this manner may be used to generate authentication information when the user purchases a new ticket.

[0081] [Fifth Embodiment] Next, a fifth embodiment of the present invention will be described. The configuration of the ticket issuing system 1 and the ticket inspection device 5 according to this embodiment differs from the embodiments described above in the points described below. Points that are not specifically mentioned below are the same as in the first embodiment, etc., and therefore will not be explained.

[0082] In the first embodiment, the characteristic ID was included in the QR code as authentication information recorded on the ticket when it was issued. However, in the ticket issuance system of this embodiment, the authentication information recorded on the ticket does not include the characteristic ID, but rather includes a ticket ID to identify the ticket. The ticket database 22A stores the user ID of the ticket user in association with the ticket ID. In addition, the ticket inspection device of this embodiment includes a ticket information table 52B that stores the ticket ID of a ticket that can be used at an event where ticket inspection is performed, in association with the characteristic ID corresponding to the user of that ticket.

[0083] Figure 12 shows the procedure for issuing tickets using the ticket issuance system 1 of this embodiment.

[0084] In this example, tickets are issued when the purchaser or a ticket vendor operates the ticket purchase terminal 3. This example explains the case where the purchaser themselves is the user of the ticket (i.e., the person who uses the ticket to enter the venue). First, the purchaser or a ticket vendor selects the venue, seat type, etc., on the ticket purchase terminal 3 and performs a purchase operation, such as pressing the purchase button (step S500). The ticket purchase terminal 3 sends the selected ticket information and the user's facial image to the server 2, which retrieves them (step S510). The facial image may be taken by the camera 35 of the ticket purchase terminal 3, or it may be an image that the user has taken in advance and is imported into the ticket purchase terminal 3 via wired or wireless communication.

[0085] Server 2 queries the feature table 22B for the user's face image received from the ticket purchase terminal 3 (step S520). If Server 2 finds any feature data that meets a predetermined criterion for similarity to the user's face image (step S520; Yes), Server 2 identifies one similar feature data that meets the predetermined criterion for similarity to the user's face image and obtains the feature ID corresponding to the identified similar feature data (step S530). It is preferable that Server 2 completely deletes the user's face image from Server 2 after identifying the similar feature data.

[0086] If the feature data in the feature table 22B does not contain any feature data that meets a predetermined criterion for similarity to the user's face image (step S520; No), the server 2 registers new feature data based on the user's face image in the feature table 22B (step S540), identifies the new feature data as similar feature data, and obtains its feature ID (step S530).

[0087] Once similar feature data is identified, server 2 stores the feature IDs of the identified similar feature data in the ticket database 22A, linking them to the ticket ID of the ticket to be purchased (step S550).

[0088] Next, Server 2 generates the information to be printed on the ticket and sends it to the ticketing machine 4 (step S560). The information to be printed on the ticket includes authentication information required for ticket inspection upon entry, event information, ticket type information, etc. In this example, the authentication information is a QR code (registered trademark) that includes the ticket ID but does not include the feature ID.

[0089] The ticket machine 4, having received the information to be printed on the ticket, prints text such as event information and ticket type information, as well as a QR code containing authentication information, onto the ticket surface.

[0090] As described above, tickets issued in this manner not only do not contain personal information such as the user's facial image in the authentication information, but also do not include feature IDs associated with the user's facial features, thus preventing the leakage of personal information via tickets.

[0091] Figure 13 is a flowchart showing the procedure for ticket inspection, which is carried out for each individual attendee at a ticket inspection station set up at the entrance of an event venue, etc., using the ticket issuance system 1 of this embodiment.

[0092] A ticket inspection station is set up at the entrance of the performance venue, and a ticket inspection device 5 is installed so that the camera 55 faces the direction from which attendees are entering. The ticket inspection device 5 is pre-stored (before the start of admission time) a ticket inspection feature table 52A containing feature data used when issuing tickets, and a ticket information table 52B in which the similar feature IDs of the users of each ticket are associated with the ticket IDs of the tickets that can be used to enter the performance. The ticket inspection device 5 receives copies of the feature table 22B and the ticket database 22A from the server 2 via the communication unit 54, and uses these as the ticket inspection feature table 52A and the ticket information table 52B, respectively.

[0093] When entry begins, the ticket inspection device 5 starts taking pictures with the camera 55 (step S600). At this time, the person entering with a ticket stands in front of the ticket inspection device 5 so that both the ticket and their face are photographed simultaneously. At this time, as in the first embodiment, the display unit 53 of the ticket inspection device 5 may display instructions to hold the ticket close to the face, the image being taken by the camera 55, and the authentication result.

[0094] The control unit 51 of the ticket inspection device 5 recognizes the face and the QR code from the image (user image) captured by the camera 55 (step S610). The control unit 51 then analyzes the recognized QR code to obtain the ticket ID included in the authentication information (step S620). Next, it queries the ticket information table 52B to identify the feature ID corresponding to the obtained ticket ID and obtains the feature data corresponding to the identified feature ID from the ticket inspection feature table 52A (step S630). The control unit 51 then calculates the similarity between the face included in the video captured by the camera 55 and the obtained feature data (step S640).

[0095] Next, the control unit 51 determines whether the calculated similarity meets a predetermined standard (the standard may be lower than that at the time of ticket issuance) (step S650). The determination in step S650 is an example of a determination according to the similarity in the present invention. If the similarity meets a predetermined standard (for example, if the degree of match is equal to or greater than a predetermined value) (step S650; Yes), a message indicating that entry is permitted is displayed on the display unit 53 (step S660). On the other hand, if the similarity does not meet a predetermined standard (for example, if the degree of match is less than a predetermined value) (step S650; No), a message indicating that entry is permitted is not displayed on the display unit 53, and the red light 56 ​​is illuminated to notify the staff of the facial recognition mismatch. In addition, for example, an alarm such as a warning display, a warning sound, or flashing light may be issued (step S670). Thus, the ticket inspection process for one entrant is completed after either step S660 or S670. Note that the output of the result when the similarity does not meet a predetermined standard is not limited to the above. For example, instead of issuing notifications or warnings, the system could display an entry permit on the display unit 53 to avoid congestion at the ticket inspection station, while notifying the ticket inspection station staff that the similarity does not meet the prescribed criteria, and allowing the staff to verify whether the entrant is fraudulent or not after passing through the ticket inspection station.

[0096] At the entrance to the event venue, the same process is carried out for each individual attendee. This configuration makes it possible to prevent fraudulent use or transfer of tickets while ensuring smooth ticket inspection at the entrance.

[0097] [Variations of the Embodiment] Although embodiments of the present invention have been described above, the present invention is not limited to these examples. For example, in the above embodiments, authentication was performed using facial images, but authentication using other biometric information (e.g., fingerprints, iris, veins, electromyography, etc.) may be used instead of facial images. In this case, it is preferable to store multiple patterns (i.e., indices) of biometric information in a feature table linked to feature IDs, and include feature IDs corresponding to patterns that are close to the user's biometric information in the authentication information.

[0098] Furthermore, while the above embodiments include one feature ID in the authentication information, multiple feature IDs may be included in the authentication information. For example, a predetermined number (e.g., 3) of similar feature data may be identified in order of decreasing degree of matching with the user's face image, and the feature ID corresponding to each similar feature data may be included in the authentication information. Alternatively, the feature data included in the feature table may be classified into multiple groups, similar feature data with a degree of matching with the user's face image higher than a predetermined value may be identified from each group, and the feature ID corresponding to each similar feature data may be included in the authentication information.

[0099] If the authentication information recorded on the ticket includes multiple feature IDs, the ticket inspection device should allow passage through the ticket inspection point if the degree of match with the feature data corresponding to a predetermined number of feature IDs (which may be one, some, or all) is above a predetermined value. Furthermore, the authentication information may also include information about the performances that the ticket is valid for (such as a performance ID), and the ticket inspection device may determine whether or not entry is permitted based on the performance information included in the authentication information.

[0100] Furthermore, in each of the above embodiments, the ticket inspection device 5 compares the similarity between the acquired user's biometric information (i.e., facial image) and the feature data corresponding to the feature ID associated with the ticket, and makes a determination (such as whether or not entry is permitted) based on the comparison result. However, the determination may be made by other methods. For example, based on the user's biometric information acquired by the ticket inspection device 5, new feature data similar to the feature information related to the biometric information may be obtained, and a feature ID corresponding to this newly obtained feature data may be identified. The determination may then be made based on the comparison result between the feature ID identified by the ticket inspection device 5 and the feature ID associated with the ticket.

[0101] Specifically, the determination may be made based on whether the similar feature ID identified by the ticket inspection device 5 is the same as the feature ID associated with the ticket. Alternatively, the ticket may be assigned multiple similar feature IDs, and the ticket inspection device 5 may identify multiple feature IDs, with the determination being made based on whether the number of matching feature IDs reaches a predetermined level.

[0102] Furthermore, in each of the above embodiments, during ticket issuance and ticket inspection, a process is performed to identify similar feature data whose similarity to the face image meets a predetermined criterion, but the predetermined criterion used at this time is arbitrary. For example, the predetermined criterion may be that the degree of agreement with the feature data is equal to or greater than a predetermined value. Alternatively, without comparing with a predetermined value, the predetermined criterion may be that the degree of agreement with the face information is the highest, and the feature data with the highest degree of agreement (or, in the case of identifying multiple similar feature data, the first to a predetermined number of similar feature data) may be identified as similar feature data.

[0103] Furthermore, in the first embodiment described above, the ticket purchase terminal 3 captured a facial image of the user (the purchaser) at the time of ticket purchase and sent it to the server 2. However, after ticket purchase, a facial image of the user (which may be a different person from the purchaser) could be sent to the server 2 before the ticket is issued. Specifically, when a ticket is purchased, the server 2 would issue information to access a ticketing website, and the user would access this website and send a photo to the server 2 before the ticket is issued. In this case, once the server 2 receives the photo, it would issue ticketing information (for example, identification information and a password) to the purchaser, and the user would take this ticketing information to a store or other location where a ticketing machine 4 is installed to issue the ticket. With such a configuration, it becomes easy to purchase multiple tickets at once and register the facial image of each entrant for each ticket.

[0104] Furthermore, it would be beneficial to print an image (caricature) of a face that has a high degree of similarity to the similarity feature data, generated based on the similarity feature data, on the ticket surface. This would allow for the estimation of the ticket holder and enable the distribution of tickets to the correct owner in cases such as when multiple tickets are purchased. Additionally, if user information is linked to the ticket, the user information may be printed on the ticket surface.

[0105] Furthermore, in the above embodiment, feature data was pre-registered in the feature table 22B, but it is not necessary for the feature table 22B to contain this data beforehand. In other words, the initial state of the feature table 22B may be one that does not contain any feature data. In this case, if feature data with a matching degree of a predetermined value or higher is not included in the feature table 22B (this is always the case for the first ticket issuer), it is advisable to register feature data based on the purchaser's facial image in the feature table 22B. In this way, the feature data included in the feature table 22B will differ for each performance. As a result, even if a large amount of authentication information is analyzed, it will become impossible to estimate and generate authentication information, and fraud can be effectively prevented.

[0106] Furthermore, in the above embodiment, the authentication information was printed on the ticket surface as a QR code, but the authentication information may be recorded on the ticket by other means as long as it can be recognized by the ticket inspection device 5. For example, a barcode, string of characters, graphic, etc., may be printed on the ticket surface as authentication information. For example, the ticket may be configured to have a storage medium capable of holding electronic data such as memory, and the authentication information recorded on the storage medium may be transmitted to the ticket inspection device 5 by any means such as wireless communication (e.g., short-range wireless communication using RF tags) or visible light communication. Alternatively, an IC chip containing the authentication information may be embedded in the ticket, and the ticket inspection device 5 may read the authentication information stored on the IC chip via wired or wireless communication.

[0107] Furthermore, although the above embodiment was described using the example of applying the ticket issuance system and ticket inspection device to paper tickets, the tickets may also be electronic tickets implemented using a mobile device such as a smartphone.

[0108] Furthermore, in the above embodiment, the ticket inspection device 5 at the ticket inspection station simultaneously photographed the ticket and the visitor's face with a single camera 55, but these may be photographed at different times and / or with different devices. For example, the visitor's face may be photographed with camera 55, and the QR code printed on the ticket may be read by a separately provided QR code reader.

[0109] Furthermore, in the first embodiment described above, the example was given of printing the tickets to be issued on special paper from a dedicated ticketing machine 4. However, the tickets may also be printed on plain paper from a regular printer at the purchaser's home or elsewhere. In this case, the regular printer at the purchaser's home or elsewhere can be interpreted as acting as the ticketing machine.

[0110] Furthermore, any modifications made by those skilled in the art to the aforementioned embodiments, including additions, deletions, or design changes to components, or combinations of features from each embodiment, are also included within the scope of the present invention, as long as they retain the essence of the present invention. [Explanation of symbols]

[0111] 1. Ticket Issuance System 2 servers 3 Ticket purchase terminal 4 Ticket machine 5. Ticket Inspection Device

Claims

1. A storage means for storing feature data containing characteristic information relating to exemplary biometric information and identification information for identifying said feature data in association with each other, A means for acquiring biometric information of a user, Similar feature data identification means that identifies similar feature data from among the feature data stored by the storage means, whose similarity to the biometric information acquired by the biometric information acquisition means satisfies a predetermined criterion, and acquires the identification information corresponding to the similar feature data, Authentication information output means that generates authentication information including the identification information acquired by the similar feature data identification means and outputs it to a ticket issuing machine, A ticketing system equipped with the following features.

2. The ticket issuing system according to claim 1, wherein the biometric information is information of the user's facial image.

3. A program that causes a computer to function as the ticket issuing system described in claim 1.

Images