Face recognition-based ticket authentication system

Abstract

This face recognition-based ticket authentication system comprises: a user terminal for purchasing a ticket; an entry authentication terminal for authenticating the ticket purchased by the user terminal; an entry control AR glass for displaying a ticket authentication result of the entry authentication terminal for entry control; and a ticket issuance server for issuing the ticket purchased by the user terminal.

Description

Facial recognition-based ticket authentication system

[0001] The present invention relates to a ticket authentication system, and more specifically, to a facial recognition-based ticket authentication system.

[0002]

[0003] To enter concerts, fairs, exhibitions, stadiums, etc., you must purchase a ticket or mobile ticket and have your ticket checked each time you enter.

[0004] In addition, when boarding an airplane, ship, train, etc., you must authenticate yourself using a paper boarding pass or mobile boarding pass before boarding.

[0005] However, these tickets or boarding passes can be either named tickets or boarding passes, or anonymous tickets or boarding passes.

[0006] In the case of concerts, exhibitions, and stadiums, tickets are often sold at very high prices, so even if they are anonymous, the damage can be very great if they are lost or stolen.

[0007] Additionally, even in the case of a named boarding pass, there is a very high possibility that someone else can steal it.

[0008] Meanwhile, when a large number of passengers enter or board simultaneously, the entry and boarding times become extremely congested, requiring significant manpower to verify each entry and boarding. Naturally, errors also occur frequently during the entry and boarding process.

[0009] To address these various issues, a more convenient and secure process is needed to issue tickets and perform the entry process.

[0010]

[0011] An object of the present invention is to provide a facial recognition-based ticket authentication system.

[0012]

[0013] A facial recognition-based ticket authentication system according to the purpose of the present invention described above may be configured to include a user terminal for purchasing a ticket; and an entry authentication terminal for authenticating a ticket purchased from the user terminal.

[0014] Here, it may be configured to further include a ticket issuing server that issues tickets purchased from the user terminal.

[0015] And the user terminal may be configured to display the purchased ticket, and the entry authentication terminal may be configured to authenticate the ticket displayed on the user terminal.

[0016]

[0017] According to the facial recognition-based ticket authentication system described above, the entry process is performed using facial information obtained when purchasing a ticket even without presenting the ticket, thereby enabling free entry or boarding without separate ticket authentication, and making the entry process easy and quick. In addition, it has the effect of preventing theft of user terminals or tickets and allowing entry only to true right holders.

[0018] Meanwhile, even when authenticating by presenting a ticket, the mobile ticket and QR code are displayed when the user terminal recognizes a specific mark image of the entry authentication terminal, so that the ticket is displayed only during entry authentication, thereby preventing the mobile ticket from being stolen by thieves.

[0019] On the other hand, in the case of anonymous tickets, the transfer and acquisition of anonymous tickets are directly brokered through the ticket issuing server, and the transfer and acquisition history is stored on the blockchain, which makes it possible to track black market tickets and has the effect of preventing the rampant sale of black market tickets.

[0020] Additionally, it has the effect of enabling the user's fandom authentication by authenticating the fandom mobile ID and linking the ticket issuance history linked to the fandom mobile ID.

[0021] On the other hand, the entry authentication manager is configured to display the entry authentication results of each entrant or passenger through the entry authentication AR glasses at the entry site, which has the effect of accurately identifying and finding out whether the entrant or passenger has been authenticated for entry.

[0022]

[0023] Figures 1 to 3 are block diagrams of a facial recognition-based ticket authentication system according to one embodiment of the present invention.

[0024]

[0025] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated in the drawings and detailed descriptions of specific embodiments for carrying out the invention are provided. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention. Throughout the description of each drawing, similar reference numerals have been used to designate similar components.

[0026] Terms such as first, second, A, and B may be used to describe various components, but these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. The term "and / or" includes a combination of multiple related items described herein or any of multiple related items described herein.

[0027] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0028] The terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, it should be understood that the terms "comprise" or "have" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0029] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0030] Hereinafter, a preferred embodiment according to the present invention will be described in detail with reference to the attached drawings.

[0031] Figures 1 to 3 are block diagrams of a facial recognition-based ticket authentication system according to one embodiment of the present invention.

[0032] Referring to FIGS. 1 to 3, a facial recognition-based ticket authentication system according to one embodiment of the present invention may be configured to include a user terminal (100), an entry authentication terminal (200), entry control AR glasses (300), and a ticket issuing server (400).

[0033] Below, the detailed configuration is explained.

[0034] The user terminal (100) may be configured to purchase tickets, store and display the purchased tickets, and use them for entry authentication. The entry authentication process may include ticket authentication processes for entering concert halls, fairs, exhibition halls, etc., and ticket authentication processes for boarding airplanes, ships, trains, etc.

[0035] The user terminal (100) may be configured to include a ticket search module (101), a ticket purchase module (102), a user terminal-side camera module (103), a user face image upload module (104), a ticket reception module (105), a ticket wallet module (106), an entry ticket selection control module (107), a user terminal-side synchronization mark image real-time reception module (108), a user terminal-side synchronization mark image real-time comparison module (109), a ticket display module (110), a user mobile ID storage module (111), a user mobile ID display module (112), an anonymous ticket transfer module (113), and an anonymous ticket transfer module (114).

[0036] Below, the detailed configuration is explained.

[0037] The ticket search module (101) can be configured to search for tickets on a ticket issuing server (400).

[0038] The ticket purchase module (102) can be configured to purchase a ticket searched by the ticket search module (101).

[0039] The user terminal camera module (103) can be configured to create a user face image through a self-photograph of the user during the ticket purchase process of the ticket purchase module (102).

[0040] And the user terminal side camera module (103) can be configured to capture a synchronization mark image during the user's entry authentication process.

[0041] Here, the synchronization mark image is a predetermined synchronization mark image that is displayed in synchronization on the user terminal (100) and the entry authentication terminal (200). Authentication using this synchronization mark image can enable or disable the user terminal (100) from displaying a ticket.

[0042] The user face image upload module (104) can be configured to upload a user face image generated by a user terminal-side camera module (103) to a ticket issuing server (400).

[0043] The ticket receiving module (105) may be configured to receive a ticket issued from a ticket issuing server (400). Here, the ticket may be a mobile ticket.

[0044] The ticket wallet module ((106)) can be configured to store tickets received from the ticket receiving module (105).

[0045] The entry ticket selection control module (107) may be configured to allow the user to select and input a specific ticket from among the tickets stored in the ticket wallet module (106) during the entry authentication process. That is, when entering or boarding, the user may select and use one of the multiple tickets in the ticket wallet module (106).

[0046] At this time, when a certain ticket is selected and input, the entry ticket selection control module (107) recognizes that the entry authentication process is in progress and can control the user terminal camera module (103) to capture a synchronization mark image. This synchronization mark image is displayed on the entry authentication terminal (200), and when the user terminal camera module (103) recognizes the synchronization mark image on the entry authentication terminal (200), the ticket is displayed and the entry authentication process is performed.

[0047] The user terminal-side synchronization mark image real-time reception module (108) may be configured to receive a synchronization mark image and the corresponding mark time interval in real time from the ticket issuing server (400). Here, the synchronization mark image may be configured to change for each mark time interval. For example, various synchronization mark images, such as a specific gorilla image, a specific banana image, a flag image of a specific country, or a face image of a specific celebrity, may be configured to change every 30 seconds. As another example, the synchronization mark image may be changed every minute starting at 8:00 PM when the entry authentication process begins.

[0048] The user terminal-side synchronization mark image real-time comparison module (109) can be configured to compare in real time the synchronization mark image of the corresponding mark time section received in real time from the user terminal-side synchronization mark image real-time reception module (108) with the synchronization mark image captured by the user terminal-side camera module (103).

[0049] The ticket display module (110) may be configured to display the ticket when the real-time comparison result of the real-time comparison module (109) on the user terminal side of the synchronization mark image is confirmed to match the synchronization mark image. In other words, since the ticket of the user terminal (100) is displayed only when the synchronization mark image of the user terminal (100) and the synchronization mark image of the entry authentication terminal (200) match each other, the QR code on the ticket or the ticket image itself can be prevented from being stolen by secret photography or image capture.

[0050] The user mobile ID storage module (111) can be configured to store a user mobile ID. The user mobile ID may include a resident registration card or driver's license. Additionally, it may include other identification documents, such as employee IDs, student IDs, and certificates, and may also include fandom mobile IDs issued by specific idol groups or entertainment agencies.

[0051] The user mobile ID display module (112) may be configured to display the user mobile ID stored in the user mobile ID storage module (111) in real time if the ticket displayed by the ticket display module (110) is a registered ticket. A registered ticket may be, for example, an airplane boarding pass or an expensive ticket for admission to a concert or stadium.

[0052] The anonymous ticket transfer module (113) can be configured to transfer a predetermined anonymous ticket among the tickets stored in the ticket wallet module (106) to another user terminal (100A).

[0053] The anonymous ticket transfer module (114) can be configured to transfer an anonymous ticket from another user terminal (100A) and store it in the ticket wallet module (106).

[0054] At this time, the user terminal camera module (103) may be configured to generate a user face image through a self-photograph of the transferor or transferee during the ticket transfer process of the anonymous ticket transfer module (113) or the ticket transfer process of the anonymous ticket transfer module (114).

[0055] And the user face image upload module (104) can be configured to upload the user face image of the transferor or transferee generated by the user terminal side camera module (103) to the ticket issuing server (400).

[0056] The entry authentication terminal (200) can be configured to authenticate a ticket purchased from a user terminal (100) during the entry authentication process.

[0057] The entry authentication terminal (200) may be configured to include a user face information reception module (201), a user face information storage module (202), an entry terminal-side synchronization mark image real-time reception module (203), a synchronization mark image display module (204), a ticket QR recognition module (205), a QR-based user face information search module (206), an entry terminal-side camera module (207), a user face information extraction module (208), a user entry authentication module (209), a user mobile ID reception module (210), a user mobile ID storage module (211), a user mobile ID authentication module (212), an entry control module (213), and a user entry authentication result transmission module (214).

[0058] Below, the detailed configuration is explained.

[0059] The user face information receiving module (201) may be configured to receive user face information in advance from the ticket issuing server (400).

[0060] The user face information storage module (202) may be configured to store user face information previously received from the user face information reception module (201).

[0061] The entry terminal-side synchronization mark image real-time reception module (203) can be configured to receive a synchronization mark image and the corresponding mark time section in real time from the ticket issuing server (400).

[0062] The synchronization mark image display module (204) can be configured to display a synchronization mark image received in real time from the entry terminal-side synchronization mark image real-time reception module (203) in real time during the corresponding mark time section.

[0063] The ticket QR recognition module (205) can be configured to recognize the QR of a ticket displayed on the ticket display module (110) of the user terminal (100).

[0064] The QR-based user face information inquiry module (206) can be configured to inquire user face information on the ticket issuing server (400) in real time through a link of a QR recognized by the ticket QR recognition module (205).

[0065] The entry terminal side camera module (207) can be configured to capture the user's face during the user's entry process and generate a user's face image in real time.

[0066] The user face information extraction module (208) may be configured to extract user face information in real time from a user face image generated in real time by the entry terminal-side camera module (207). Here, the user face information is feature information extracted from the user face image, and may be configured to enable liveness recognition that can recognize a moving user face as it is.

[0067] The user entry authentication module (209) may be configured to perform user entry authentication by comparing the user face information extracted in real time by the user face information extraction module (208) with the user face information stored in the user face information storage module (202). In other words, entry authentication can be performed by receiving and securing the user face information in advance.

[0068] Additionally, as another method, the user entry authentication module (209) may be configured to perform user entry authentication by comparing the user face information retrieved in real time from the QR-based user face information retrieval module (206). Entry authentication can be performed by receiving specific user face information in real time using a QR link.

[0069] The user mobile ID reception module (210) may be configured to receive the user mobile ID in advance from the ticket issuing server (400).

[0070] The user mobile ID storage module (211) may be configured to store a user mobile ID received in advance from the mobile ID reception module (210).

[0071] The user mobile ID authentication module (212) can be configured to recognize the user mobile ID displayed in the user mobile ID display module (112) of the user terminal (100), and perform user entry authentication by comparing the recognized user mobile ID with the user mobile ID stored in the user mobile ID storage module (211) of the entry authentication terminal (200).

[0072] The entry control module (213) may be configured to perform user entry control based on the user entry authentication result performed by the user entry authentication module (212) and the user entry authentication result of the user mobile ID authentication module (212). That is, the authentication result may be output through a speaker or display, etc., to allow or exclude entry.

[0073] The user entry authentication result transmission module (214) can be configured to transmit the user entry authentication result performed by the user entry authentication module (209) and the user entry authentication result of the user mobile ID authentication module (212) to the entry control AR glasses (300) and the ticket issuing server (400) in real time.

[0074] The entry control AR glasses (300) can be configured to display the ticket authentication results of the entry authentication terminal (200) for entry control. The entry authentication manager can wear the entry control AR glasses (300) at the entry authentication site. The entry control AR glasses (300) display the ticket authentication results on the faces of visitors or passengers in AR format, allowing the ticket authentication results of visitors and passengers on site to be immediately confirmed. Therefore, even if multiple people enter or board at the same time, unauthenticated visitors or passengers can be accurately identified.

[0075] Specifically, the entry control AR glasses (300) receive only the facial feature information of unauthenticated entrants or unauthenticated passengers from the user entry authentication result transmission module (214), and the entry control AR glasses (300) can find and identify entrants or passengers with the received facial feature information among multiple entrants or passengers, so that unauthenticated entrants or passengers can be easily found with a small amount of computation. Even when a large number of entrants or passengers enter or board at the same time with only facial authentication without separate QR authentication, the on-site manager controlling entry / boarding can easily find unauthenticated entrants or passengers.

[0076] The ticket issuing server (400) may be configured to issue tickets purchased from a user terminal (100).

[0077] The ticket issuing server (400) includes a ticket database (401), a ticket sales module (402), a user face image reception module (403), a user face image database (404), a face information extraction module (405), a face information database (406), a user face information QR generation module (407), a user face image reflection module (408), a ticket issuing module (409), a face information provision module (410), a real-time mark image collection module (411), a mark image storage module (412), a synchronized mark image real-time generation module (413), a synchronized mark image real-time transmission module (414), a user mobile ID database (415), a user mobile ID provision module (416), a ticket transfer / acquisition mediation module (417), a ticket blockchain generation module (418), a ticket blockchain synchronization module (419), a ticket blockchain inquiry module (420), a ticket blacklist detection module (421), a user entry authentication result reception module (422), a user entry authentication result storage module (423), and automatic ticket refund processing. It can be configured to include a module (424), a fandom ticketing history creation module (425), and a fandom ticketing history database (426).

[0078] Below, the detailed configuration is explained.

[0079] The ticket database (401) can be configured to store unissued tickets, issued tickets, purchasers of issued tickets, transferors and transferees in a linked manner.

[0080] The ticket sales module (402) may be configured to sell unissued tickets stored in the ticket database (401) to the user terminal (100).

[0081] The user face image receiving module (403) may be configured to receive a user face image as a purchaser, transferor, or assignee of a ticket sold by the ticket selling module (402).

[0082] The user face image database (404) can be configured to store user face images received from the user face image receiving module (403).

[0083] The user face information extraction module (405) can be configured to extract user face information from a user face image stored in a user face image database (404).

[0084] The user face information database (406) can be configured to store user face information extracted from the user face information extraction module (405).

[0085] The user face information QR generation module (407) can be configured to generate a QR including a link for searching user face information stored in the user face information database (406), and to reflect the generated QR in tickets sold by the ticket sales module (402).

[0086] The user face image reflection module (408) can be configured to reflect the user face image stored in the user face image database (404) to the corresponding ticket sold by the ticket sales module (402).

[0087] The ticket issuing module (409) can be configured to issue a ticket in which a QR code is reflected in the user face information QR generation module (407) and a user face image is reflected in the user face image reflection module (408). The ticket authentication manager can visually confirm the face on the ticket as needed.

[0088] The face information provision module (410) may be configured to provide user face information extracted from the user face information extraction module (405) to the entry authentication terminal (200).

[0089] The real-time collection module (411) for a mark image can be configured to collect a predetermined mark image in real time on the Internet. The mark image can include various unspecified images such as various trademarks, logos, national flags, and people.

[0090] The mark image storage module (412) can be configured to store mark images collected in real time from the mark image real-time collection module (411).

[0091] The synchronization mark image real-time generation module (413) can be configured to generate a synchronization mark image and a corresponding mark time section in real time using the mark image stored in the mark image storage module (412).

[0092] The synchronization mark image real-time transmission module (414) can be configured to transmit the synchronization mark image and the corresponding mark time section generated in real time by the synchronization mark image real-time generation module (413) to the user terminal (100) and the entry authentication terminal (200) in real time.

[0093] The user mobile ID database (415) can be configured to store user mobile IDs in advance.

[0094] The user mobile ID provision module (416) can be configured to provide a user mobile ID pre-stored in the user mobile ID database (415) to the entry authentication terminal (200).

[0095] The ticket transfer / acquisition mediation module (417) may be configured to mediate the ticket transfer of the ticket transfer module (113) of the user terminal (100) and the ticket acquisition of the ticket acquisition module (114) of the user terminal (100), and store the mediation result and the transferor and transferee of the corresponding ticket in the ticket database (401).

[0096] The ticket blockchain creation module (418) can be configured to create a ticket blockchain including tickets and ticket purchasers stored in the ticket database (401) and store the same on a blockchain node.

[0097] The ticket blockchain synchronization module (419) can be configured to additionally create blocks regarding the transferor and transferee of tickets stored in the ticket database (401) and synchronize them by adding them to the ticket blockchain stored on the blockchain node.

[0098] The ticket blockchain query module (420) can be configured to verify and query the ticket blockchain on the blockchain node.

[0099] This will ensure that all purchase / transfer / acceptance processes for already issued tickets are recorded.

[0100] The ticket scalping detection module (421) can be configured to track and detect scalped tickets by querying the ticket database (401) or using the ticket blockchain query result of the ticket blockchain query module (420).

[0101] The user entry authentication result receiving module (422) may be configured to receive the user entry authentication result from the user entry authentication result transmitting module (214) of the ticket issuing server (400).

[0102] The user entry authentication result storage module (423) may be configured to store the user entry authentication result received from the user entry authentication result reception module (422).

[0103] The automatic ticket refund processing module (424) can be configured to compare the ticket stored in the ticket database (401) with the user entry authentication result stored in the user entry authentication result storage module (423), and if the user's entry is not confirmed as a result of the comparison, automatically refund the ticket to the user according to a predetermined refund policy.

[0104] The fandom ticketing history creation module (425) can be configured to link and search the fandom mobile ID and the ticket stored in the ticket database (401) when the user mobile ID stored in the user mobile ID database (415) of the ticket issuing server (400) is a fandom mobile ID.

[0105] And the fandom ticketing history creation module (425) can be configured to create a fandom ticketing history for the user based on the search result.

[0106] The fandom ticketing history database (426) can be configured to store fandom ticketing history generated by the fandom ticketing history generation module (425).

[0107] Although the present invention has been described with reference to the above embodiments, it will be understood by those skilled in the art that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below.

Claims

1. User terminal purchasing a ticket; A facial recognition-based ticket authentication system including an entry authentication terminal for authenticating a ticket purchased from the user terminal.

2. In paragraph 1, A facial recognition-based ticket authentication system characterized in that it further includes a ticket issuing server that issues tickets purchased from the user terminal.

3. In paragraph 1, The above user terminal is configured to display the purchased ticket, A facial recognition-based ticket authentication system, characterized in that the above entry authentication terminal is configured to authenticate a ticket displayed on the user terminal.

Images