Program, method, and system

Abstract

To provide a ticket system capable of suppressing a visitor's eagerness for fraudulence while performing ticket inspection processing of many visitors in a short time by providing a fixed fraudulence detection mechanism while making the ticket inspection processing an extremely simple procedure.SOLUTION: A step of acquiring at least one of a ticket ID for identifying ticket information and a user ID and a face image of a user at the time of use of a facility that provides various services and registering the ticket ID and the user ID and the face image in association with each other; A step of extracting a user who may match a predetermined condition, and a step of supporting a predetermined measure for the user when the user who may match the predetermined condition is extracted are executed.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present disclosure relates to programs, methods, and systems. [Background technology]

[0002] 2. Description of the Related Art In order to prevent ticket resale and fraudulent use, a ticket inspection system is known in which visitors are required to register their facial photograph when purchasing a ticket and their facial photograph is taken upon entry to verify the identity of the visitor.

[0003] Patent Document 1 discloses a system for managing admission to a facility, which compares a facial photograph registered when purchasing a ticket with a facial photograph acquired at the time of admission to confirm that the visitor is the one who purchased the ticket, thereby preventing the fraudulent resale of tickets. [Prior art documents] [Patent documents]

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

[0005] However, with conventional technology, it takes time to match a person's face with a pre-registered photograph, and this can result in excessively long entry times for events with large attendances, such as sporting events.

[0006] To provide a ticket system that can perform ticket inspection processing for many visitors in a short time and suppress the visitors' desire to commit fraud by providing a certain fraud detection mechanism while making ticket inspection processing an extremely simple procedure. [Means for solving the problem]

[0007] A program according to one embodiment of the present disclosure causes a computer processor to execute the following steps: when using a facility that provides various services, acquiring at least one of a ticket ID and a user ID that identify ticket information and a facial image of the user, and linking and registering these; extracting users who may meet specified conditions using at least one of image information captured by a surveillance camera within the facility and the registered facial image; and, when a user who may meet the specified conditions is extracted, providing support for specified measures to the user. [Effects of the Invention]

[0008] According to the present disclosure, ticket inspection procedures are simplified to an extremely simple manner, making it possible to inspect the tickets of many visitors in a short period of time. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing the configuration of a ticket system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a block diagram showing the configuration of a user terminal according to the present embodiment. [Figure 3] FIG. 2 is a block diagram showing the configuration of a ticket management server according to the present embodiment. [Figure 4] 1 is a block diagram showing the configuration of a ticket inspection device according to an embodiment of the present invention; [Figure 5] FIG. 2 is a block diagram showing an example of the configuration of an attendant terminal according to the present embodiment. [Figure 6] FIG. 1 is an explanatory diagram of an overview of the present embodiment. [Figure 7] 3A and 3B are diagrams illustrating an example of the data structure of a user database and an event database according to the present embodiment. [Figure 8] 3A and 3B are diagrams illustrating an example of the data structure of a ticket database and an attendee database according to the present embodiment. [Figure 9] 10 is a flowchart of a ticket issuing process according to the present embodiment. [Figure 10] 10 is a flowchart of the first half of the ticket inspection process according to the present embodiment. [Figure 11] 10 is a flowchart of the second half of the ticket inspection process according to the present embodiment. [Figure 12] This is an example of a screen notifying a person to retake a temperature test. [Figure 13] 10 is a flowchart of a process for detecting a suspect entrant according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and repeated description thereof will be omitted.

[0011] (1) Ticket System 1 Configuration The following describes the configuration of the ticket system 1. Fig. 1 is a block diagram showing the configuration of the ticket system 1 of this embodiment.

[0012] As shown in FIG. 1, the ticket system 1 includes a user terminal 10, a ticket management server 20, a ticket inspection device 30, and an attendant terminal 40. The user terminal 10, the ticket management server 20, the ticket inspection device 30, and the attendant terminal 40 can be connected via a network (for example, the Internet or an intranet) NW.

[0013] The user terminal 10 is an information processing device that is owned by the ticket purchaser himself / herself. The user terminal 10 is configured to request ticket information from the ticket management server 20.

[0014] In the following description, the information processing device may include various computers, such as a smartphone, a tablet terminal, a personal computer, a server computer (e.g., a web server, an application server, a database server, or a combination thereof), a wearable device (e.g., a smart watch or smart glasses), etc.

[0015] Ticket information is information related to a ticket. Specifically, ticket information may include information that identifies the ticket, information related to the authority that the ticket certifies (e.g., information related to the event that the ticket covers), information related to the purchaser of the ticket (e.g., a user ID), or a combination thereof, or code information that encodes them (e.g., a QR code (registered trademark) or other one-dimensional or two-dimensional code).

[0016] A ticket is a carrier of ticket information. Specifically, a ticket may be an image of ticket information (i.e., an electronic ticket) displayed on a user terminal 10 held by an attendee. The user terminal 10 held by an attendee is a mobile computer (smartphone, tablet terminal, laptop computer, or wearable device) connectable to a network NW. Alternatively, a ticket may be paper or other medium on which ticket information is printed.

[0017] The ticket management server 20 is an information processing device. The ticket management server 20 is configured to issue tickets (i.e., issue ticket information) in response to a request from the user terminal 10. The ticket management server 20 is also configured to manage the issued ticket information.

[0018] The ticket inspection device 30 is an information processing device located at a ticket inspection station of a facility. The ticket inspection device 30 is configured to refer to ticket information held on a ticket presented by a person entering an event venue (hereinafter referred to as an "entrant"), for example, and determine whether the entrant is permitted to enter. The ticket inspection device 30 also takes a facial image of the entrant and stores it in association with the ticket information. The ticket inspection device 30 is also configured to determine whether the entrant has a high fever by referring to the measurement result of the entrant's body temperature measured when the ticket is presented. Furthermore, the ticket inspection device 30 is configured to send a notification to the entrant's contact information depending on the determination result of whether the entrant has a high fever.

[0019] A facility refers to a space where a service is provided. For example, an event venue is included in a facility. A facility may be a part of a space within an area, such as an amusement facility in a theme park. A facility may be an indoor facility or an outdoor facility. For example, an event venue included in a facility is a performance venue, and includes, for example, a concert venue, a theater venue, a game venue, an exhibition venue, or a combination thereof. Multiple surveillance cameras are installed in the facility in advance, and capture video of the faces of attendees coming and going within the event venue. The video of attendees' faces captured within the event venue is divided into still image frames (images taken within the venue) taken from multiple directions for each attendee, and these are stored in a surveillance camera database. Note that the facility may be equipped with only one surveillance camera.

[0020] The attendant terminal 40 is an information processing device carried by an attendant who manages the event venue (including monitoring the event venue). The attendant terminal 40 may include various portable computers such as a smartphone, a tablet terminal, or a wearable device (e.g., a smart watch or smart glasses). The attendant terminal 40 may also be a general personal computer that is not portable. Event staff will monitor for any fraudulent behavior by attendees within the event venue, including disruptive behavior within the event venue, failure to comply with necessary event management requests, unauthorized entry with counterfeit or duplicated tickets, and unauthorized entry with illegally resold tickets.

[0021] (1-1) Configuration of the User Terminal 10 The following describes the configuration of the user terminal 10. Fig. 2 is a block diagram showing the configuration of the user terminal 10 of this embodiment.

[0022] 2, the user terminal 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14. The user terminal 10 is connectable to at least one of an input device 15 and an output device 16.

[0023] The storage device 11 is configured to store programs and data, and is, for example, a combination of a read-only memory (ROM), a random access memory (RAM), and a storage (for example, a flash memory or a hard disk).

[0024] The programs include, for example, the following programs: OS (Operating System) programs Applications that process information (e.g., web browsers)

[0025] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0026] The processor 12 is configured to implement the functions of the user terminal 10 by running a program stored in the storage device 11. The processor 12 is an example of a computer.

[0027] The input / output interface 13 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 15 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 16.

[0028] The input device 15 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof.

[0029] The output device 16 is, for example, a display, a speaker, a printing device, or a combination thereof.

[0030] The communication interface 14 is configured to control communication between the user terminal 10 and an external device (for example, at least one of the ticket management server 20, the ticket inspection device 30, or the attendant terminal 40).

[0031] (1-2) Configuration of ticket management server 20 The following describes the configuration of the ticket management server 20. Fig. 3 is a block diagram showing the configuration of the ticket management server 20 of this embodiment.

[0032] 3, the ticket management server 20 includes a storage device 21, a processor 22, an input / output interface 23, and a communication interface 24. The ticket management server 20 is connectable to at least one of an input device 25 and an output device 26.

[0033] The storage device 21 is configured to store programs and data, and is, for example, a combination of ROM, RAM, and storage (for example, flash memory or a hard disk).

[0034] The programs include, for example, the following programs: OS programs Application programs that perform information processing

[0035] The data includes, for example, the following data: Databases referenced in information processing - Results of information processing

[0036] The processor 22 is configured to implement the functions of the ticket management server 20 by running a program stored in the storage device 21. The processor 22 is an example of a computer.

[0037] The input / output interface 23 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 25 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 26.

[0038] The input device 25 is, for example, a keyboard, a pointing device, a touch panel, a sensor, or a combination thereof.

[0039] The output device 26 is, for example, a display, a speaker, or a combination thereof.

[0040] The communication interface 24 is configured to control communication between the ticket management server 20 and an external device (for example, at least one of the user terminal 10, the ticket inspection device 30, or the attendant terminal 40).

[0041] (1-3) Configuration of ticket inspection device 30 The following describes the configuration of the ticket inspection device 30. Fig. 4 is a block diagram showing the configuration of the ticket inspection device 30 of this embodiment. Fig. 5 is a block diagram showing an example of the configuration of an input device connectable to the ticket inspection device 30 of this embodiment.

[0042] 4, the ticket inspection device 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface 34. The ticket inspection device 30 is connectable to at least one of an input device 35 and an output device 36.

[0043] The storage device 31 is configured to store programs and data, and is, for example, a combination of ROM, RAM, and storage.

[0044] The programs include, for example, the following programs: OS programs Application programs that perform information processing

[0045] The data includes, for example, the following data: Databases referenced in information processing Data obtained through information processing

[0046] The processor 32 is configured to execute a program stored in the storage device 31 to realize the functions of the ticket inspection device 30. The processor 32 is an example of a computer.

[0047] The input / output interface 33 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 35 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 36.

[0048] The input device 35 is, for example, a keyboard, a pointing device, a touch panel, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof. As an example, as shown in FIG. 6, the input device 35 includes a thermography device 351 and a visible light camera 352. The thermograph 351 is configured to photograph the visitor when the visitor presents the ticket. Visible light camera 352 is configured to photograph the ticket and the attendee when the ticket is presented by the attendee.

[0049] The input device 35, either alone or in cooperation with the processor 32, realizes at least an authentication information acquisition means and a body temperature measurement means.

[0050] The authentication information acquisition means reads information (hereinafter referred to as "authentication information") necessary for determining whether or not a visitor is permitted to enter when the visitor presents the ticket. The authentication information includes, for example: Ticket Information

[0051] A ticket has a ticket information area for reading ticket information, where the ticket information is displayed or printed.

[0052] The authentication information acquisition means can acquire ticket information by combining the visible light camera 352 with an application that analyzes an image captured by the visible light camera 352 to extract an image of ticket information and restores the ticket information from the image of ticket information. When acquiring ticket information, information processing such as OCR (Optical Character Recognition) processing or decoding processing is performed as necessary.

[0053] The ticket and the attendee may be photographed simultaneously or sequentially by the same visible light camera 352, or one may be photographed by the visible light camera 352 and the other by another visible light camera not shown.

[0054] The body temperature measuring means measures the body temperature of the visitor when the visitor presents the ticket. The temperature measurement means preferably measures the temperature of visitors without contact, which eliminates the need for disinfection after measurement. Also, even if a visitor has an infectious disease, there is little risk of the infection spreading to other visitors and ticket inspection staff.

[0055] The body temperature measurement means can measure the body temperature of visitors non-contact by combining a thermograph 351 with an application that analyzes the thermographic image taken by the thermograph 351 to extract an image of the visitor, and obtains the temperature determined by referring to the pixel values ​​of the image of the visitor as the measurement result of the visitor's body temperature (more precisely, body surface temperature).

[0056] Depending on the shooting conditions, there is a risk that people other than visitors may appear in the thermographic image. Measurement results of visitors in the thermographic image can be distinguished from those of other people based on interocular distance. Measurement results of people whose interocular distance falls within an allowable range determined based on the distance from the position where the visitor is required to present their ticket to the point where the thermographic image was taken and the standard human interocular distance are extracted from the thermographic image as visitor measurement results. Instead of or in addition to interocular distance, facial size, inter-part distance, or a combination of these may be used as criteria to distinguish between visitor measurement results and those of other people in the thermographic image.

[0057] In general, thermography-based body temperature measurements are subject to errors due to factors such as imaging conditions. For example, if the imaging distance is excessively long, the temperature at the measurement point may be averaged with the temperature of the surrounding space, resulting in a lower-than-actual peak temperature. Therefore, the body temperature measurement means may estimate the distance from the imaging point of the thermographic image to the visitor by referencing the interocular distance of the visitor in the thermographic image, and acquire the temperature determined by referencing the estimated distance and the pixel values ​​of the area corresponding to the visitor in the thermographic image as the measurement result of the visitor's body temperature. Instead of or in addition to interocular distance, the distance from the imaging point of the thermographic image to the visitor may be estimated based on facial size, inter-partial distance, or a combination of these.

[0058] The output device 36 may be, for example, a display, a speaker, an alarm, an electric gate, or a combination thereof.

[0059] The communication interface 34 is configured to control communication between the ticket inspection device 30 and an external device (for example, at least one of the user terminal 10, the ticket management server 20, or the attendant terminal 40).

[0060] (1-4) Configuration of attendant terminal The following describes the configuration of the staff terminal 40. Fig. 5 is a block diagram showing the configuration of the user terminal 10 of this embodiment.

[0061] 5, the attendant terminal 40 includes a storage device 41, a processor 42, an input / output interface 43, and a communication interface 44. The attendant terminal 40 is connectable to at least one of an input device 45 and an output device 46.

[0062] The storage device 41 is configured to store programs and data, and is, for example, a combination of a read-only memory (ROM), a random access memory (RAM), and a storage (for example, a flash memory or a hard disk).

[0063] The programs include, for example, the following programs: OS (Operating System) programs Applications that process information (e.g., web browsers)

[0064] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0065] The processor 42 is configured to implement the functions of the attendant terminal 40 by running a program stored in the storage device 41. The processor 42 is an example of a computer.

[0066] The input / output interface 43 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 45 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 46.

[0067] The input device 45 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof.

[0068] The output device 46 is, for example, a display, a speaker, a printing device, or a combination thereof.

[0069] The communication interface 44 is configured to control communication between the attendant terminal 40 and an external device (for example, at least one of the user terminal 10, the ticket management server 20, or the ticket inspection device 30).

[0070] (2) Overview of the embodiment An outline of this embodiment will be described below with reference to Fig. 6. The tickets handled by the ticket system 1 of the present invention include various types of vouchers such as admission tickets, usage tickets, course tickets, boarding tickets, membership cards, and theme park passports that users are required to present when using facilities that provide various services. The various services offered include a wide variety of activities, such as offering concert and sports viewing experiences at event venues and stadiums, exhibiting museum collections for viewing, providing attractions at amusement facilities, providing training equipment at sports gyms, and offering lectures at regional institutions. The ticket system of the present invention uses at least one of the ticket information (or user ID) and face image acquired at the time of entry to extract users who may meet certain conditions, and when a user who may meet the certain conditions is extracted, it provides support for certain measures for that user. These details will be explained using specific examples. In this embodiment, an example of visiting an event venue where a concert is being held will be described. Visitors (users) to the event venue enter the event venue through a ticket inspection station set up at the venue. At this time, they present their ticket at the ticket inspection station and enter the venue.

[0071] 6, the ticket inspection device 30 is placed at a ticket inspection station. At the ticket inspection station, a plurality of people are queued up, and tickets are inspected for each person in turn.

[0072] When the visitor TP presents the ticket TC, the visible light camera 352 captures an image of the visitor TP and the ticket TC that are within the imaging range of the visible light camera 352. The ticket inspection device 30 (specifically, the processor 32) acquires ticket information of the ticket TC and an image of the visitor TP's face from the image captured by the visible light camera 352.

[0073] The ticket inspection device 30 refers to the ticket information of the ticket TC and the ticket database to determine whether the ticket information is a valid ticket for the event and to determine whether the attendee TP is allowed to enter. As an example, the ticket inspection device 30 checks whether the ticket information of the attendee TP is properly issued ticket information.

[0074] The ticket inspection device 30 creates an attendee database using the acquired facial images of attendees. The ticket inspection device 30 then detects suspected fraudulent activity using at least one of the attendee facial images and the images taken within the event venue and stored in the surveillance camera database.

[0075] When suspicion of fraudulent activity is detected, information about the suspected entrant suspected of committing the fraudulent activity is sent to the attendant terminal 40. The attendant uses the information about the suspected entrant sent to the attendant terminal 40 to confirm the fraudulent activity on-site. If fraudulent activity is confirmed, a report to that effect is entered into the attendant terminal 40. Then, the ticket management server 20 imposes sanctions on the suspected entrant who is determined to have committed fraud, and anyone involved in the activity, such as restricting their ability to purchase tickets in the future.

[0076] Furthermore, when the visitor TP presents the ticket TC, the thermograph 351 in the ticket inspection device 30 photographs the visitor TP who is within the imaging range of the thermograph 351. The ticket inspection device 30 obtains the measurement result of the visitor TP's body temperature from the thermographic image taken by the thermograph 351.

[0077] The ticket inspection device 30 determines whether or not the visitor TP has a high fever by referring to the acquired measurement results. The ticket inspection device 30 sends a notification to the visitor TP's contact information depending on the determination result of whether or not the visitor TP has a high fever. At the very least, if the ticket inspection device 30 determines that the visitor TP has a high fever, it sends a notification to the visitor TP to urge them to undergo a formal temperature measurement or to promptly leave the event venue.

[0078] In this way, the ticket inspection device 30 determines whether or not to admit the visitor TP without referencing the temperature measurement results, while also referencing the measurement results to determine whether the visitor TP has a high fever. If the visitor TP is determined to have a high fever, a notification is sent to the visitor TP's contact information. This prevents the visitor TP from being held up at the ticket inspection station solely because of a high fever. Therefore, people around the visitor do not notice that the visitor has a high fever, and they do not feel any ill feelings, such as anxiety or disgust, at the presence of someone with a high fever nearby. On the other hand, the visitor is not denied entry solely because of a high fever and is not subject to curious gazes. Therefore, this ticket inspection device 30 and the ticket system 1 including this ticket inspection device 30 prevent any discomfort experienced by visitors to the event venue due to temperature checks, thereby preventing confusion and trouble even if a person with a high fever is discovered. Furthermore, a visitor TP determined to have a high fever can check the received notification and undergo a formal temperature check or be urged to promptly leave the event venue. Therefore, it is possible to prevent the spread of infection caused by TPs who are determined to have a high fever staying at the event venue for a long period of time.

[0079] (3) Database The databases of this embodiment will be described below. The following databases are stored in the storage device 21. However, a copy of at least a part of the following databases may also be stored in the storage device 31.

[0080] (3-1) User database The user database of this embodiment will now be described with reference to Fig. 8A, which shows the data structure of the user database of this embodiment.

[0081] The user database stores user information, which is information about users of the ticket system 1. As shown in FIG. 8, the user database includes a "User ID" field, a "Login PASS" field, a "User Name" field, a "User Attributes" field, a "Contact Information" field, a "Payment Method" field, and an "Action Status" field.

[0082] The "user ID" field stores an ID for identifying the user who purchases the ticket.

[0083] The "Login PASS" field stores the password that the user corresponding to the user ID is required to enter when logging in to the ticket system 1 to purchase a ticket.

[0084] The "user name" field stores the name of the user corresponding to the user ID.

[0085] The "User Attributes" field stores attribute information of the user identified by the user ID. The attribute information is information about the user's attributes. The attributes may include, for example, name, date of birth, gender, age, or a combination thereof. The "user attributes" field may also include the user's status, such as fan club membership, that is relevant to the provision of the event.

[0086] The "Contact" field stores contact information for a user identified by a user ID. The contact information is information related to the user's contacts. The contact information may be, for example, an email address, a phone number, account information for a social networking service (SNS) or other messaging-enabled application, or a combination thereof. The contact information is not limited to the examples given here and may include any type of information that can be used to send notifications to attendees in real time via the user terminal 10.

[0087] The "Payment Method" field stores the payment method for purchasing a ticket.

[0088] The "Action Status" field stores the details of various sanctions applied as penalties to a user corresponding to a user ID who has engaged in fraudulent activity. Examples of various sanctions include the following. Note that the details of the sanctions may be other, as long as they act as a deterrent to the user from engaging in fraudulent activity. -Exit from the facility on the day Addition to a blacklist, a list of attendees who will be subject to certain restrictions or special monitoring, such as being barred from entry (blacklists may be shared with other venues) · Restrictions on ticket purchases for a certain period of time (or in the future) - Revocation of membership in fan clubs, etc. - Prohibition on participating in events (including attending as a companion) Restrictions on viewing online events by the same host Restrictions on purchasing various goods from online shops

[0089] (3-2) Event database FIG. 8B is a diagram illustrating an example of the data structure of the event database. As shown in Fig. 8B, the event database stores event information. The event information is information about an event held at an event venue to which a user purchases a ticket. As shown in FIG. 8B, the event database includes an "Event ID" field, an "Event Name" field, an "Operating Company" field, an "Event Content" field, a "Performers" field, an "Event Date" field, and an "Event Time" field.

[0090] The "event ID" field stores an ID for identifying the event.

[0091] The "event name" field stores information about the name of the event corresponding to the event ID.

[0092] The "operating company" field stores information about the operating company of the event corresponding to the event ID.

[0093] The "event content" field stores information about the content of the event corresponding to the event ID. Examples of information about the event content include "professional baseball" or "concert."

[0094] The "performer" field stores information about the performers of the event corresponding to the event ID. Information about performers includes team names, band names, group names, singer or actor names, etc.

[0095] The "Event Date" field stores information about the event date and time corresponding to the event ID.

[0096] The "venue time" field stores the venue time of the event corresponding to the event ID. The venue time is the time when visitors start entering the event venue.

[0097] (3-3) Ticket database The ticket database and the attendee database of this embodiment will now be described. Fig. 8A is a diagram showing an example of the data structure of the ticket database of this embodiment.

[0098] As shown in FIG. 8A, the ticket database stores ticket information. The ticket database includes a "ticket ID" field, an "event ID" field, a "purchaser ID" field, a "seat number" field, a "ticket inspection status" field, a "ticket price" field, and a "purchase date and time" field.

[0099] The "Ticket ID" field stores a ticket ID. The ticket ID is information that identifies the ticket.

[0100] The "event ID" field stores the event ID of the event to which the ticket corresponding to the ticket ID applies.

[0101] The "Purchaser ID" field stores the user ID of the user who purchased the ticket corresponding to the ticket ID. The user's SNS ID may also be registered as the purchaser ID. If the purchaser is accompanied by someone, the companion ID may also be registered along with the purchaser ID.

[0102] The "seat number" field stores seat number information. The seat number information is information about the seat (an example of a "zone") assigned to the purchaser of the ticket identified by the ticket ID.

[0103] The "ticket inspection status" field stores information indicating whether the ticket corresponding to the ticket ID has been inspected. For example, if the ticket has been inspected, "after tearing" is displayed, and if the ticket has not been inspected, "before tearing" is displayed.

[0104] The "ticket price" field stores information about the price of the ticket corresponding to the ticket ID.

[0105] The "Purchase Date and Time" field stores information about the date and time when the ticket corresponding to the ticket ID was purchased.

[0106] (3-4) Visitor database 8B is a diagram showing an example of the data structure of the attendee database of this embodiment. As shown in FIG. 8B, the attendee database stores information about attendees at the event venue.

[0107] As shown in Figure 8B, the attendee database includes a "attendee ID" field, an "event ID" field, a "ticket ID" field, a "seat number" field, a "purchaser ID" field, an "attendee facial image" field, a "ticket inspection time" field, a "temperature inspection result" field, and a "response status" field.

[0108] The "Visitor ID" field stores a visitor ID that identifies a visitor. The visitor ID is an ID that is assigned in the order in which ticket inspection processing is performed, for example.

[0109] The "event ID" field stores the event ID of the event attended by the visitor corresponding to the visitor ID.

[0110] The "Ticket ID" field stores the ticket ID of the ticket held by the attendee corresponding to the attendee ID. In other words, the ticket ID field in the attendee database stores the ticket ID of the ticket presented by the attendee at ticket inspection.

[0111] The "seat number" field stores the seat number associated with the ticket ID of the ticket held by the attendee corresponding to the attendee ID.

[0112] The "Purchaser ID" field stores the user ID of the purchaser of the ticket held by the attendee corresponding to the attendee ID. If SNS IDs or companion IDs are registered in the ticket database, these IDs may also be stored along with the "Purchaser ID."

[0113] The "visitor face image" field stores a face image of the visitor corresponding to the visitor ID, taken at the time of ticket inspection.

[0114] The "ticket inspection time" field stores the time when the visitor corresponding to the visitor ID carried out the ticket inspection process.

[0115] The "First temperature check result" field stores the result of the temperature check (first temperature check) conducted for the visitor corresponding to the visitor ID during the ticket inspection process. The temperature check result will be displayed as "normal temperature" if the body temperature is below the specified temperature, and as "high temperature" if the body temperature is above the specified temperature.

[0116] The "Second Temperature Check Result" field stores the results of the retest that is required for visitors who, among those corresponding to the visitor ID, were determined to have a high temperature in the first temperature check. In other words, it can be confirmed that visitors whose first temperature check result was determined to be high and whose second temperature check result has not been entered did not undergo the retest that they should have taken.

[0117] The "Response Status" field stores the details of the response currently being taken for the visitor corresponding to the visitor ID. For example, the response status items and details are as follows: No action (default setting) - No particular suspicion of fraudulent activity is detected Suspicion detected: Suspicion of fraudulent activity has been detected Tracking: A staff member is tracking a suspected visitor or checking for fraudulent activity. · Restrictions have been addressed... Some sanctions have been implemented ·Exited: The person has been expelled from the facility

[0118] (4) Control processing The ticket processing of this embodiment will be described.

[0119] (4-1) Ticketing process The ticket issuing process of this embodiment will be described below with reference to the flowchart of FIG.

[0120] As shown in FIG. 9, the user terminal 10 executes reception of a purchase operation (S110). Specifically, the processor 12 receives a purchase operation performed on the input device 15 via the input / output interface 13 . The ticket purchaser is not limited to the user himself / herself, but may be a person (for example, a ticket sales attendant) who operates a ticket purchase terminal having the same configuration as the user terminal 10 on behalf of the user. The purchasing operation may include, for example, inputting a user ID, selecting a show, selecting a date and time, selecting a seat type, pressing a purchase button (a button object or a physical button), or a combination thereof.

[0121] After step S110, the user terminal 10 executes a ticket issuance request (S111). Specifically, processor 12 generates a ticket issuance request by referring to the content of the purchase operation accepted in step S110. The ticket issuance request includes, for example, information specifying the type of ticket for which issuance is requested (e.g., information specifying the event, date and time, and seat type) and the user ID of the ticket purchaser. Processor 12 transmits the ticket issuance request to ticket management server 20 via communication interface 14.

[0122] After step S120, the ticket management server 20 updates the ticket database (S120). Specifically, the processor 22 newly registers the user ID included in the ticket issuance request in the ticket database (FIG. 8A) in association with the unissued ticket ID, and updates the purchase date and time, thereby making it possible to identify the ticket purchaser based on the ticket ID.

[0123] After step S121, the ticket management server 20 provides ticket information (S121). Specifically, the processor 22 generates ticket information by referring to the updated contents of the database in step S121. The ticket information includes the ticket ID newly registered in step S121. Furthermore, the ticket information may include the user ID of the ticket purchaser identified in step S121. Some or all of the information included in the ticket information may be encoded, for example, into a QR code or other code information. The processor 22 provides the generated ticket information to the ticket purchaser. As an example, the processor 22 transmits the generated ticket information to the user terminal 10 via the communication interface 24.

[0124] After step S122, the user terminal 10 saves the ticket information (S112). Specifically, the processor 12 acquires the ticket information provided in step S122. The processor 12 stores the acquired ticket information in the storage device 11. This allows the processor 12 to display the ticket information as needed. Furthermore, the processor 12 may optionally perform at least one of the following: · Causes the output device 16 (printing device) to print the ticket information onto paper or other media. The communication interface 14 transmits the ticket information to the user terminal 10 of the ticket purchaser.

[0125] (4-2) Ticket inspection The ticket inspection process of this embodiment will now be described with reference to Fig. 10, which is a flowchart showing the first half of the ticket inspection process of this embodiment.

[0126] 10, the user terminal 10 displays the ticket information (step S113). Specifically, in response to an attendee who has come to the event venue operating the user terminal 10 at the ticket inspection station of the event venue, the processor 12 reads and displays the ticket information stored in the storage device 11. At this time, the ticket information may be displayed in the form of a two-dimensional code such as a QR code. The attendee presents the displayed ticket information to the ticket inspection device 30.

[0127] After step S113, the ticket inspection device 30 reads the ticket (S130). Specifically, when an attendee presents a ticket, processor 32 cooperates with visible light camera 352 to read the ticket information. In step S130, the processor 32 may display the image captured by the visible light camera 352 on the output device 36 (display) for the visitor. This provides the visitor with feedback on how the ticket is being photographed, and encourages them to make fine adjustments to the position and orientation of the ticket.

[0128] At this time, the ticket inspection device 30 takes a photograph of the face of the entrant (step S131). Specifically, when an attendee presents ticket information, processor 32 captures a facial image of the attendee in cooperation with visible light camera 352. In this embodiment, the ticket ID and facial image are acquired at the same time using the same imaging device, but they may be captured using different imaging devices. In step S131, the processor 32 may display the image captured by the visible light camera 352 on the output device 36 (display) for visitors or staff. This provides feedback to visitors about how they are being photographed, and encourages them to make fine adjustments to their position or posture. For example, an attendant at the ticket inspection station may use a smartphone to take a photo of the visitor's face and ticket ID and then process the visitor.

[0129] After step S131, the ticket inspection device 30 measures the body temperature (S132). Specifically, when an attendee presents ticket information, the processor 32 works in cooperation with the thermograph 351 to measure the attendee's body temperature. In step S132, the processor 32 does not display the thermographic image taken by the thermograph 351 on the output device 36 (display) for the visitor. This prevents people around the visitor from noticing that they have a high fever, and prevents the visitor from becoming upset after learning that they have a high fever. However, the processor 32 may display the thermographic image taken by the thermograph 351 on the output device 36 (display) for the attendant.

[0130] The ticket inspection device 30 may perform steps S130, S131, and S132 in an order different from that shown in Fig. 10. As an example, the ticket inspection device 30 may perform two or more of these steps simultaneously.

[0131] After step S130 and step S130, the ticket inspection device 30 determines whether or not entry is permitted (S133). Specifically, processor 32 refers to the ticket information read in step S130 and the ticket database to determine whether or not the attendee is permitted to enter. As an example, processor 32 determines to permit entry to the spectator if the ticket ID included in the ticket information acquired in step S131 is stored in the ticket database and relates to a properly purchased ticket. On the other hand, processor 32 determines to deny entry to the spectator if the ticket ID included in the ticket information does not relate to a properly purchased ticket. Furthermore, the acquired facial image may be compared with a pre-created blacklist without referencing the ticket ID, and a decision may be made to deny entry to visitors who fall on the blacklist. In this case, information about people on the blacklist (personal information, images, image features, etc.), user IDs, and ticket IDs linked to the user IDs may be stored in a database in advance.

[0132] As mentioned above, a copy of at least a part of the database stored in storage device 21 may also be stored in storage device 31. In this case, ticket inspection device 30 can quickly determine whether or not a visitor is allowed to enter by referring to the copy stored in storage device 31, without accessing ticket management server 20. However, from the perspective of protecting personal information, the user database (FIG. 7A) may be excluded from the targets of duplication.

[0133] In other words, the ticket inspection device 30 allows entry to a visitor if it determines that the ticket information presented by the visitor is genuine, and denies entry to a visitor if it does not determine that the ticket information presented by the visitor is genuine. This prevents a visitor from entering the venue by presenting a counterfeit ticket, thereby preventing people from entering the venue using fraudulent means. Regarding refusal of entry to a pedestrian, from the viewpoint of efficiency of ticket inspection processing, entry may not be refused at the ticket inspection station, but rather a specified notice (including, for example, a notice that entry will be denied or a notice requesting further confirmation) may be issued to the pedestrian or staff member whose entry is to be refused, and the matter may be handled separately at the staff member's booth.

[0134] Fig. 11 is a flowchart showing the second half of the ticket inspection process according to this embodiment, and Fig. 12 is an example of a screen displaying a notice for a re-inspection of body temperature measurement. If entry is not permitted in step S133, the ticket inspection device 30 executes entry error processing (S135). Specifically, when it is determined in step S133 that the entry of the visitor is to be denied (NO in step S134), processor 32 performs at least one of the following processes. - Issuing an alarm (for example, lighting a lamp, emitting a specified sound, displaying a specified screen, or a combination of these to let the visitor and the attendant know that their entry has been denied, and to prompt the attendant to take follow-up measures) Closing gates (e.g., closing power gate bars or flap doors to physically block entry of visitors)

[0135] In order to prevent congestion near the ticket inspection device 30, aftercare by an attendant may be provided after providing a specified service, such as allowing the attendant to enter the event venue for convenience. Aftercare by an attendant may involve the attendant visiting the seat where the attendant is staying or the location of the facility they are using, by referring to surveillance camera footage and the usage history of various services, and conducting a discussion to confirm the authenticity of the ticket. A notification may also be sent to the user terminal of the unauthorized attendant, encouraging them to visit the attendant's booth. As an example, the attendant may ask the attendant for attribute information, contact information, time of ticket purchase, or a combination of these, and compare this with the ticket information. Examples of information that the attendant may confirm include the following: Personal information of the purchaser and accompanying persons (name, gender, age / generation, date of birth, address, nearest station, contact information, hometown, alma mater, etc.) - Confirmation of identification of the purchaser and accompanying person (driver's license, passport, health insurance card, utility bill-related documents, etc.) Relationship with the purchaser and accompanying persons (family, friends, etc.) After step S135, the ticket inspection process of FIG. 11 ends.

[0136] If entry is permitted in step S133, the ticket inspection device 30 grants permission for entry (S136). Specifically, when processor 32 determines in step S133 that the visitor is permitted to enter (YES in step S134), it presents a notification to at least either the attendant or the visitor that entry has been permitted.

[0137] When permitting entry, at least one of the following processes may be performed. Notification that entry has been permitted (for example, lighting a lamp, outputting a specified sound, displaying a specified screen, or a combination of these to let the visitor and the attendant know that entry has been permitted) Opening gates (e.g., opening electric gate bars or flap doors to allow people in)

[0138] After step S136, the ticket inspection device 30 executes a high fever determination (S137). Specifically, processor 32 refers to the measurement result of the entrant's body temperature in step S132 and determines whether the entrant has a high fever (for example, whether the entrant's body temperature is above a threshold). This determination can also be called a first temperature check. The threshold may be fixed (e.g., 37.5°C) or variable. In the latter case, the threshold may be determined by referring to the body temperature measurement results of other people whose entry or exit eligibility to the event venue was determined before the person entering the event. This can reduce errors in judgment due to fluctuations in shooting conditions (e.g., ambient temperature). If it is determined in step S137 that the entrant does not have a high fever (NO in step S138), the ticket inspection process in FIG. 11 ends.

[0139] After step S137, the ticket inspection device 30 transmits a notification (S139). Specifically, if the ticket inspection device 30 determines in step S137 that the entrant has a high fever (YES in step S138), it sends a notification to the entrant's contact information identified from the ticket information (e.g., ticket ID or user ID) read in step S130.

[0140] The notification sent in step S137 is displayed as a message image on the display of the visitor's user terminal 10, for example, as shown in Fig. 12. By checking the notification, the visitor is urged to promptly exit the premises and undergo a formal temperature check (secondary temperature check). The notification includes, for example, at least one of the following information: Information encouraging visitors to undergo formal temperature checks (M10) Information about temperature check stations at event venues (M11) Information to encourage visitors to leave promptly Information that a visitor has a high fever (M10) Information informing visitors that they may be infected with an infectious disease Information informing visitors that they are suspected of having a specific infectious disease (e.g., an infectious disease determined by reference to the epidemic information on infectious diseases at the time of sending the notification) (M10) Information about exits to the event venue Information about medical facilities associated with the event venue (e.g., name, address, contact details, or a combination thereof) Information informing attendees that they have not been assigned an area (e.g., reserved seating) at the event venue (use case of notifying attendees of an area assignment after entering the venue) Information about the booth that will attract visitors

[0141] Note that steps S137 to S139 may be executed independently of steps S133 to S136. As an example, step S137 may be executed before step S133. After step S139, the ticket inspection process of FIG. 11 ends.

[0142] (4-3) Detection of suspected entrants The process for detecting suspected entrants in this embodiment will now be described. Fig. 13 is a flowchart of the process for detecting suspected entrants in this embodiment. The process for detecting suspected entrants is carried out after the ticket inspection process described above. The process for detecting suspected entrants may be carried out sequentially in parallel with the ticket inspection process using ticket information that has already been inspected, or may start after the entrant's entry time has ended (after the inspection process for all tickets has been completed). 13, the ticket inspection device 30 creates a visitor database (step S140). Specifically, the processor 32 of the ticket inspection device 30 assigns visitor IDs to visitors in the order in which the ticket inspection process (ticket tearing) is performed, and stores each item in the visitor database by referring to the ticket database and the user database. At this time, a facial image taken at the time of ticket tearing is stored in the visitor database.

[0143] At this time, the processor 32 may use part of the contents of the attendee database to create or update a check-in list for staff patrolling the event venue. The check-in list is information about a list of the results of ticket inspection processing for each visitor. The check-in list includes, for example, at least one of the following elements: Check-in time Ticket ID presented by the attendee User ID associated with ticket ID Username associated with the user ID The result of the admission decision (step S133) (admission permitted / admission denied) - Result of high fever judgment (step S136) (high fever / normal temperature) Whether or not the visitor who was diagnosed with a high fever confirmed the notification Did staff members officially take the temperature of visitors who were diagnosed with a high fever or ask them to leave? The area assigned to you at the event venue (e.g., reserved seating)

[0144] The check-in list can be used, for example, as a list of people who have been diagnosed with a high fever or information about a list of areas assigned to people who have been diagnosed with a high fever.

[0145] After step S140, the ticket inspection device 30 detects suspected entrants (step S141). Specifically, the processor 32 of the ticket inspection device 30 detects suspected entrants who are suspected of committing fraudulent acts using at least one of the information registered in the attendee database and images of entrants taken inside the venue stored in the surveillance camera database. Examples of types of fraudulent acts that the processor 32 detects as suspected include the following: - Entering the venue using tickets obtained through illegal resale Entering the event venue without a ticket (without passing through the ticket inspection station) - Sharing the same ticket with multiple people (including sharing across different days) Using a seat other than the original seat Refusing to undergo a re-examination of the temperature -Various illegal acts against others (violence, molestation, bringing in dangerous items, bringing in items prohibited by the event organizer, etc.) · Nuisance behavior that disrupts the operation of the event (drunkenness, disturbance, etc.) Other actions prohibited by the event organizer (such as selling related goods without permission)

[0146] For example, in the case of fraudulent ticket resale, if different user IDs are linked to attendees with the same facial image at multiple events held on different days, the processor 32 detects this as a suspicion of fraudulent ticket resale. That is, the processor 32 compares multiple facial images linked to multiple ticket IDs corresponding to the same user but different events, and detects fraudulent ticket resale if it determines that the multiple facial images belong to different people.

[0147] In addition, in the case of multiple people sharing the same ticket, if a single ticket ID is linked to facial images of multiple attendees in the attendee database, processor 32 compares the facial images. If it determines that the facial images belong to different people, it determines that the ticket associated with the ticket ID is shared, and detects the attendee who entered the venue by presenting the ticket ID as a suspected attendee. Note that if social media IDs or companion IDs are registered in the attendee database, these pieces of information may be used as keys to check for duplicate facial images of attendees.

[0148] Furthermore, in the case of an act of entering the event venue without a ticket (without passing through the ticket inspection booth), processor 32 compares the face of the visitor captured in the image taken inside the venue with the face image registered in the visitor database. Processor 32 then checks whether any visitor captured in the image taken inside the venue is not registered in the visitor database. If processor 32 confirms that there is a visitor not registered in the visitor database, processor 32 determines that the visitor may have entered the event venue without a ticket and detects the visitor as a suspect visitor.

[0149] In addition, in the case of an act of using a seat other than the original seat, processor 32 refers to the attendee database, and if the facial image of the attendee who should be sitting at the registered seat number differs from the person sitting in that seat in the image taken inside the venue, it detects the person sitting in that seat as a suspect attendee.

[0150] In addition, in regards to illegal resale, if the estimated values ​​such as gender and age calculated from the facial image of the visitor differ from the registered information of the purchaser / accompanying person, it may be detected as a suspicion of illegal resale. Furthermore, the method for detecting suspicion of unauthorized resale may be any of the following. If the same person purchases tickets for multiple events but the data registered in the attendee database does not include the same person, it will be determined that the purchaser did not attend the events. If the same person purchases multiple tickets and the facial image of the accompanying person is different each time, this will be detected as a suspected case of fraudulent resale. If the face image at the time of entry and the person sitting in the seat are different, or if someone is sitting in a seat for which no entry data exists, it will be determined to be a "resale of good seats." If different user IDs are linked to attendees with the same face image at multiple events held on different days, this will be detected as a suspected case of illegal resale. For example, if a purchaser holds a book ID that contains the same ticket information for multiple tickets, the tickets managed by the same book ID may be considered to belong to the same visitor group, and ticket exchange within that group may be allowed as an exception.

[0151] In addition, with regard to refusal to comply with a re-examination of the temperature, the processor 32 detects as a suspected entrant any entrant who does not comply with the re-examination after a certain period of time has elapsed after receiving notification of the re-examination.

[0152] In addition, for various illegal acts against the surrounding area, nuisance acts that disrupt the operation of the event, and other acts prohibited by the event organizer, processor 32 detects these acts from images taken within the venue, determines the user information of the relevant attendee from the user database, and detects the perpetrator as a suspected attendee.

[0153] After step S141, the ticket inspection device 30 supports sanctions (step S142). Supporting sanctions is a process of providing information about the suspected entrant who will be subject to sanctions to the attendant terminal 40, thereby making subsequent sanctions more efficient and preventing false detections. Specifically, the processor 32 transmits information to the attendant terminal 40 via the communication interface, prompting the attendant terminal 40 to confirm the fraudulent use. At this time, the information transmitted to the attendant terminal 40 includes at least one of the following: Types of fraudulent activity A map of the event venue showing the locations of illegal activity - Images taken inside the venue showing illegal activity A map of the event venue showing the location of the suspected attendees photographed in the images taken within the venue -Facial image of the suspected visitor registered in the visitor database User information of the suspected entrant The seat number of the suspected attendee and a map of the event venue Information about the location within the event venue where actions such as merchandise purchases were made using the suspected attendee's account information and payment information - Instructions on how to deal with suspected visitors Of these, information about suspected visitors captured in images taken inside the venue may be processed based only on information captured from the front.

[0154] After step S142, the staff member terminal 40 confirms the suspected entrant (step S150). Specifically, based on the information provided to the staff member terminal 40, the staff member goes to the site and confirms whether the suspected entrant is actually engaging in fraudulent activity. The staff member then inputs the confirmation results into the staff member terminal 40, thereby determining whether the suspected entrant has engaged in fraudulent activity and whether the suspected entrant is a suspected entrant. The input confirmation results are sent to the ticket management server 20 and the ticket inspection device 30.

[0155] After step S150, the ticket management server 20 takes sanctions (step S160). Specifically, the processor 22 of the ticket management server 20 updates the "sanction status" field in the user database for the user who is the target of the sanctions. As a result, various restrictions set as sanctions are subsequently applied to the user. From the perspective of deterrence, it is desirable that the sanctions be applied to the suspected attendee or all users involved in the purchase of tickets used by the suspected attendee. Note that, at the discretion of the event organizer, relief measures may be given to users who purchased tickets without knowing that illegal resale was prohibited. Furthermore, in cases where someone without a user ID commits fraud, such as entering an event venue without a ticket, a blacklist can be created that registers personal information such as the person's name, gender, address, and facial photo (including features), and restrictions similar to those imposed by sanctions can be imposed. The content of the sanctions can be set appropriately based on the type of fraudulent behavior, the number of times, etc.

[0156] (5) Effects As described above, the ticket system 1 according to this embodiment uses at least one of image information captured by a surveillance camera and information registered in the attendee database to detect suspected attendees who are suspected of engaging in fraudulent activities. Then, sanctions are imposed on users involved in the purchase of tickets by the suspected attendees. This ensures a deterrent against fraudulent activities such as the unauthorized resale of tickets. Furthermore, when inspecting tickets, it is sufficient to simultaneously photograph the ticket information and the face image of the visitor, and there is no need to compare the face image of the visitor with a pre-registered face image, so that the ticket inspection process is an extremely simple procedure, and tickets of many visitors can be inspected in a short time. Furthermore, unlike systems where visitors must register the facial information of themselves and their companions in advance, such as those used in general facial recognition, this system does not require visitors to decide on their companions until the last minute, and also eliminates the hassle of registering facial information in advance.

[0157] Furthermore, if the ticket ID and face image are acquired at the same time by the same imaging device when entering an event venue, the workload of ticket inspection processing can be significantly reduced, and ticket inspection processing of visitors can be carried out efficiently in an extremely short time.

[0158] In addition, information is sent to the attendant terminal 40 prompting confirmation of fraudulent use, and upon input of fraud confirmation from the attendant terminal 40, the attendant is detected as the suspected attendant. Therefore, by having the attendant confirm fraudulent activity, erroneous detection of suspected attendants can be reduced.

[0159] Furthermore, the ticket inspection device 30 determines whether or not to admit a visitor without referencing the visitor's temperature measurement results, while also referencing the measurement results to determine whether the visitor has a high fever. If the visitor is determined to have a high fever, a notification is sent to the visitor's contact information. This prevents the visitor from being held at the ticket inspection station solely because of a high fever. Therefore, surrounding people do not notice that the visitor has a high fever, and do not feel any ill feelings, such as anxiety or disgust, at being nearby someone with a high fever. On the other hand, the visitor is not denied entry solely because of a high fever and is not subject to curious gazes. Therefore, this ticket inspection device 30 and the ticket system 1 including this ticket inspection device 30 avoid causing discomfort to anyone entering the event venue due to temperature checks, thereby preventing confusion and trouble even if a person with a high fever is discovered. Furthermore, visitors who are determined to have a high fever can check the received notification and undergo a formal temperature check or be urged to immediately leave the event venue. This prevents the spread of infection due to visitors who are determined to have a high fever staying at the event venue for a long period of time. (6) Variations A modification of this embodiment will now be described.

[0160] (6-1) Variation 1 Modification 1 will be described. In Modification 1, an attendant checks for fraudulent activity using a check-in list created by ticket inspection device 30. In this case, the detection of suspected fraudulent activity by ticket inspection device 30 is omitted, and suspected entrants are detected simply by inputting the results of the fraudulent activity confirmation into attendant terminal 40.

[0161] Specifically, using the check-in list described above, staff members patrol the event venue while consulting the call list, monitoring for anyone engaging in fraudulent activity. For example, if a staff member finds a person in an area assigned to an attendee determined to have a high fever, the staff member will call out to that person (e.g., request that they present their ticket). This allows the person to be forced to have their temperature taken or be expelled, even if they do not see the notice urging them to undergo a re-examination (formal temperature check) or to leave, or if they ignore it and try to remain. Furthermore, if the person simply misunderstood the area assigned to them, they can be guided to the correct area. The staff member places a check mark in the box for the person whose temperature they have taken or expelled, or in the box for the area they have confirmed to be unoccupied. By sharing the status of the call list between the terminals of multiple staff members, it is possible to accurately identify people who have not yet had their temperature taken or been confirmed to leave the venue, and to have those who are determined to have a high fever taken their temperature or be expelled from the event venue within the limited time between the doors opening and the start of the performance.

[0162] (6-2) Variation 2 Modification 2 will now be described. In Modification 2, after misconduct is confirmed, the relevant entrant is notified of the suspected misconduct. Specifically, after the above-mentioned step S150, a notification of the suspected misconduct is sent to the relevant user terminal 10. The notification of the suspected misconduct includes at least one of the following items: - Notification that fraudulent activity by the user has been confirmed Guidance for visiting the staff booth where staff are stationed - Information about sanctions that will be imposed if you refuse to visit the staff booth

[0163] If a suspected entrant visits the staff booth, they will check their ID and ask questions about any misconduct, and will carry out confirmation work on the suspected entrant. If the staff confirms any further misconduct, or if the entrant refuses to visit the staff booth, they will be subject to disciplinary action.

[0164] (6-3) Variation 3 A description will be given of Modification 3. Modification 3 is an example in which tickets and temperatures of visitors are checked when they exit the venue.

[0165] The ticket inspection device 30 of the third modification determines whether or not an attendee attempting to leave the event venue can leave, and also determines whether the attendee has a high fever. The exit may be a temporary exit with the intention of re-entry. Entry is not limited to first-time entry, and may be a re-entry.

[0166] The ticket inspection process of the ticket inspection device 30 of the third modified example can be realized by appropriately replacing the word "enter" with the word "exit" in the ticket inspection process of this embodiment (FIG. 11).

[0167] Modification 3 can be combined with this embodiment. That is, the ticket inspection device 30 may determine whether or not an attendee is permitted to enter the event venue, and may also determine whether or not an attendee is permitted to leave the event venue.

[0168] (6-4) Variation 4 We will now explain Modification 4. Modification 4 is an example in which, when a visitor is determined to have a high fever, a person who was in a predetermined positional relationship with the visitor (hereinafter referred to as a "contact person") is identified, and a notification is sent to the contact person's contact information.

[0169] Specifically, the ticket inspection device 30 identifies people who have come into contact with the attendee when entering or leaving the event venue, or while the attendee is staying at the event venue.

[0170] In a first example of contact identification, the ticket inspection device 30 identifies as a contact at least one person who was waiting in line adjacent to a visitor determined to have a high fever when entering or leaving the event venue. The people who were waiting in line adjacent to the visitor can be identified from the ticket inspection history. The number of people may be fixed or may be variable depending on the nature of the infectious disease determined by referring to epidemic information on infectious diseases at the time the notification is sent, or the distance between visitors determined by the ticket inspection station. As an example, the ticket inspection device 30 identifies as contacts the person who was waiting in line one place in front of the visitor, the person who was two places in front of the visitor, and the person who was waiting in line one place behind the visitor.

[0171] In a second example of contact person identification, the ticket inspection device 30 identifies as a contact person a person who, while staying at the event venue, was assigned an area (e.g., an adjacent seat) that has a predetermined positional relationship with the area assigned to the attendee. The ticket inspection device 30 may inquire about the area assigned to each person from the ticket management server 20 or another external device. The seat assigned to each person can be identified from the seat number information stored in the ticket database (FIG. 7) described above.

[0172] In a third example of identifying contact persons, the ticket inspection device 30 refers to information exchanged between user terminals 10 using close proximity wireless communication (e.g., Bluetooth) when they are in close proximity to each other, and identifies as contact persons those who were around the attendee determined to have a high fever when entering or leaving the event venue, or while staying at the event venue. Contact persons may also be identified using images captured by a surveillance camera.

[0173] After identifying the contact person, the ticket inspection device 30 sends a notification to the contact information of the identified contact person. The contact information of the contact person can be identified, for example, from the ticket information presented by the contact person.

[0174] By checking the notification, those who have come into contact with the infected person will be aware that they may have been infected with the infectious disease and will be encouraged to change their behavior. For example, after checking the notification, those who have come into contact with the infected person will be encouraged to take actions such as carefully monitoring their own health condition or avoiding places where many people gather. Furthermore, if those who have come into contact with the infected person develop a fever, they will be encouraged to contact a designated hotline, which will allow information to be collected that will contribute to understanding the actual state of the infectious disease. The notification may include, for example, at least one of the following information: Information that the contact person may have come into contact with someone who has a high fever Information that informs you that your contacts may have contracted some kind of infectious disease Information that indicates that the contact may have contracted a specific infectious disease (e.g., an infectious disease determined by reference to epidemic information on infectious diseases at the time of sending the notification). Information on who to contact if a person in contact with you develops a fever

[0175] As explained above, when a entrant is determined to have a high fever, the ticket inspection device 30 of Modification 4 identifies those who have come into contact with the entrant in a predetermined positional relationship and sends a notification to the contact information of those people. This makes it possible to warn those people who may have been infected with an infectious disease by the entrant determined to have a high fever, and to prevent the further spread of the infectious disease originating from those people.

[0176] (7) Other variations The storage device 11 may be connected to the user terminal 10 via a network NW. The storage device 21 may be connected to the ticket management server 20 via a network NW. The storage device 31 may be connected to the ticket inspection device 30 via a network NW. The storage device 41 may be connected to the attendant terminal 40 via a network NW.

[0177] The above ticket inspection process may be performed by the ticket inspection device 30 alone as shown in FIG. 11, or may be performed in cooperation with the ticket inspection device 30 and another device (for example, the ticket management server 20). Furthermore, the ticket inspection process may read ticket information not by using a photographing device but by other electronic means. For example, the following may be mentioned: A method for stamping an electronic stamp on a ticket displayed by the user terminal 10 - Using an RFID antenna to read ticket information contained in tags carried by visitors A method of reading ticket information from the user terminal 10 or membership card using other wireless communication such as Bluetooth (registered trademark) or NFC. As an example of the above, ticket inspection processing may be performed using a terminal that reads a membership card, which is an NFC card, and a camera that photographs the face of the entrant. As another example, ticket inspection may be performed using a terminal that uses RFID or Bluetooth (registered trademark) to identify visitors at a medium distance and a camera that photographs their faces. In these cases, it is possible to omit taking a photograph of the ticket ID or member ID (membership card) using the photographing device.

[0178] The above-mentioned process for detecting a suspected visitor may be performed entirely by the ticket inspection device 30 as shown in FIG. 13, or part or all of the process may be performed by the ticket management server 20 or another computer.

[0179] In the embodiment, an example has been shown in which ticket information is read. However, instead of reading the ticket information, a user ID may also be read. That is, the user ID and face image of the entrant may be acquired during ticket inspection, and the ticket inspection device 30 may then check the user ID and ticket ID. In this case, a check is subsequently made to see if there is ticket information linked to the user ID. If there is no ticket information linked to the user ID, the entrant is detected as a suspected unauthorized entry. In this case, the user's access authority is confirmed by reading the user ID stored in the electronic tag included in the membership card or the one-dimensional / two-dimensional code printed on the membership card. In other words, the ticket system may obtain information that proves the user's access authority to the facility instead of ticket information. Specific examples of such cases are listed below. When reading the user ID associated with ticket information in advance from visitors to the event venue - When reading the user ID of a gym user When reading the user ID of a person who has previously made an electronic payment for the purchase of tickets for each amusement facility in a theme park

[0180] For example, when applying this invention to users of a sports gym, a membership card and a facial image of the user are acquired when the user starts using the gym. If unauthorized use is detected after the user is initially permitted to use the gym, a staff member can individually speak to the user. Furthermore, when the present invention is applied to users of amusement facilities in a theme park, for example, a user ID and a facial image are acquired at the boarding gate of a roller coaster (facility) and boarding is permitted. If, for example, there is a shortage of tickets purchased in advance, a notice to that effect is sent and an attendant speaks to the user individually.

[0181] When reading a user ID such as a membership card, fraudulent use can be confirmed by checking whether the user ID is valid for use at the facility or whether the user ID is linked to ticket information that allows use at the facility.

[0182] In the embodiment, an example is shown in which a facial image of the visitor is captured. However, the facial image of the visitor may also be captured by video recording. For example, when using a means with a relatively wide communication range such as RFID, facial images of the visitor passing through the entrance gate may be continuously captured as video, and still image frames may be extracted from the video captured within a certain time range from the reading of the ticket information and linked to the visitor who presented the ticket.

[0183] In the embodiment, an example has been shown in which a facial image of a visitor is captured. However, instead of a facial image of a visitor, information on other biometrics (for example, fingerprints, palm prints, irises, veins, myoelectric potential, etc.) may be acquired. Furthermore, information on the visitor's gait, clothing, accessories, or personal accessories such as glasses may be acquired as information for identifying the visitor. In this case, for example, a QR code containing ticket information may be read by a reading terminal, and the palm of the visitor's hand may be photographed by a camera.

[0184] In the embodiment, an example has been shown in which the body temperature measurement means is realized using the thermography 351. However, instead of the thermography 351, or in addition to the thermography 351, the body temperature measurement means can also be realized using an infrared thermometer. In addition, instead of an infrared thermometer, any means for measuring human body temperature can be applied, such as an electronic thermometer, a liquid crystal type, an optical type, a type equipped with artificial intelligence, etc. Furthermore, the measurement location is not limited to the face, and other parts such as the wrist or ear may also be measured.

[0185] In the embodiment, an example is shown in which a notification including information informing that an area (e.g., a reserved seat) at the event venue has not been allocated to the contact information of an attendee determined to have a high fever is sent to the contact information of the attendee. However, the ticket inspection device 30 may send a notification including information about the area to be allocated to the attendee to the contact information of an attendee determined not to have a high fever, but may not send a notification including information about the area to be allocated to the attendee to the contact information of an attendee determined to have a high fever.

[0186] In the embodiment, an example has been shown in which the ticket management server 20 transmits ticket information to the user terminal 10. However, instead of the ticket information, the ticket management server 20 may transmit resource information (e.g., a URL (Uniform Resource Locator)) for referencing the resource in which the ticket information is saved to the user terminal 10. Attendees can display the ticket information on the display of their own user terminal 10 by accessing the resource indicated by the resource information using their own user terminal 10.

[0187] A visitor who has been diagnosed with a high fever and temporarily left the event may attempt to re-enter the event venue in the hope that the high fever diagnosis will be overturned. In such cases, various measures can be taken to prevent the visitor from re-entering. As an example, the ticket inspection device 30 rewrites, for example, a flag ("high fever flag") in the check-in list associated with the ticket ID of the ticket presented by an entrant determined to have a high fever from "0" to "1." Then, when determining whether or not to allow entry (step S133), the ticket inspection device 30 refers to the check-in list, and if the high fever flag associated with the ticket ID is "1," determines to deny entry to the target without referring to any other information.

[0188] In the embodiment, some or all of the information included in the ticket information is encoded in, for example, a QR code or other code information. For example, the ticket may include a QR code containing the ticket ID and a reference character string. During the ticket issuing process, the processor 22 of the ticket management server 20 generates a reference character string by performing a predetermined function calculation using, for example, the ticket ID and the performance ID (information identifying the performance that the ticket is for) as arguments. The event ID corresponding to the event to be inspected and the above function are stored in memory device 31 of ticket inspection device 30. During the ticket inspection process, processor 32 of ticket inspection device 30 generates an authentication target string by performing an operation on the function read from memory device 31 using the ticket ID read from the ticket and the event ID read from memory device 31 as arguments. Ticket inspection device 30 compares the reference string read from the ticket with the authentication target string to determine whether the patron is allowed to enter. According to this example, it is possible to prevent illegal resale of tickets without storing personal information of users in the storage device 31 of the ticket inspection device 30.

[0189] In the embodiment, a notification is sent to a suspected entrant who is suspected of unauthorized entry, but the present invention is not limited to this. That is, the present invention is a system that can extract users who may meet certain conditions and provide support for certain measures against those users. The certain conditions include the following: - Visitors who were granted the benefits (number of visitors, other benefits) Visitors who require special treatment, such as celebrities Visitors who would like to answer the questionnaire Visitors who have lost or forgotten items or other matters to be notified Visitors who wish to carry out various sales activities such as announcing campaigns, proposing merchandise, or greeting others. Support for prescribed measures includes: Notifications encouraging you to visit the staff booth Notification of special treatment such as VIP seating Notifications requesting you to respond to surveys Notification of the granting of benefits In these cases, the attendant terminal is notified of the necessary information to identify the visitor who is the target of the prescribed measures. The attendant checks the transmitted information, searches for users who may meet the prescribed conditions, confirms whether or not they meet the prescribed conditions, and then takes the necessary measures.

[0190] The contents detected by the present invention and the terminals that are linked to it are not limited to those described above. For example, various suspected fraudulent activities can be detected in the following manner. -Detecting actions that may match certain conditions from surveillance camera footage ··Detect people whose behavior is likely to be illegal by using video analysis with artificial intelligence. Detect people who may be in poor health, such as those with a pale complexion. Detect suspected prohibited pets. Detect any other suspected prohibited activities. · Baggage inspection is carried out using X-ray sensors, infrared sensors, etc. Detect people who are likely to be caught in baggage inspections by photo · Breathalyzer tests are conducted using breathalyzer sensors. -Detect facial photos of people who are restricted from entering. ··Utilizing police wanted lists ··Utilizing a list of photographs of past fraudulent users (those who have been confirmed to have committed fraud)

[0191] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above-described embodiments. Furthermore, the above-described embodiments can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above-described embodiments and modifications can be combined.

[0192] (8) Supplementary Notes The matters explained in the embodiment and the modified examples are additionally noted below.

[0193] (Appendix 1) The computer processor When using a facility that provides various services, a step of acquiring at least one of a ticket ID and a user ID that identify ticket information, and a facial image of the user, and linking and registering these together; extracting users who may meet predetermined conditions using at least one of image information captured by a surveillance camera in the facility and registered face images; and a program for executing a step of supporting a predetermined measure for a user when a user who may meet predetermined conditions is extracted.

[0194] (Appendix 2) In the step of extracting users who may match a predetermined condition, Executing a step of detecting a suspected entrant who is suspected of misusing the facility; In the step of providing support for a predetermined measure, A program as described in Appendix 1, which executes a step of supporting specified sanctions against a suspected user suspected of fraudulent use or at least one user involved in the distribution of tickets used by said suspected user.

[0195] (Appendix 3) In the step of supporting measures, Sending information indicating the possibility that the user meets the predetermined conditions to the attendant terminal; A program described in Appendix 1 or 2, which determines that a user meets specified conditions through input operations on an attendant terminal.

[0196] (Appendix 4) In the step of detecting a suspected entrant, A program described in any of Appendices 1 to 3, which compares multiple facial images registered in an attendee database and linked to multiple ticket IDs corresponding to the same user but different events, and if it is determined that the multiple facial images belong to different people, detects the attendee corresponding to the multiple facial images as a suspect attendee.

[0197] (Appendix 5) In the step of detecting a suspected entrant, A program described in any of Appendices 1 to 4, which compares multiple facial images when they are linked to a ticket ID registered in an attendee database, and if it is determined that the multiple facial images belong to different people, detects the attendee corresponding to the multiple facial images as a suspect attendee.

[0198] (Appendix 6) In the step of detecting a suspected entrant, The face of the visitor captured in the image information is compared with the face image registered in the visitor database, A program according to any one of appendices 1 to 5, which detects visitors whose facial images are not registered in the visitor database as suspected visitors.

[0199] (Appendix 7) The processor A step of measuring the temperature of visitors when using the facility; and further executing a step of determining whether the user has a high fever by referring to the measurement result of the user's body temperature. In the step of detecting a suspect user, A program described in any one of appendices 1 to 6, which detects a user who is determined to have a high temperature as a suspected entrant.

[0200] (Appendix 8) and further executing a step of sending a notice of re-examination to the contact information of the visitor who is determined to have a high fever in the step of determining. In the step of detecting a suspected entrant, 10. The program of claim 7, wherein an entrant who does not comply with re-inspection after receiving notification of re-inspection is detected as a suspect entrant.

[0201] (Appendix 9) A program described in any of Annexes 1 to 7, where the prescribed sanction is a restriction on future use of the service.

[0202] (Appendix 10) In the step of supporting sanctions, A program described in any of Appendices 1 to 8, which provides information indicating the location of a suspected entrant to an attendant terminal.

[0203] (Appendix 11) The computer's processor When using a facility that provides various services, a step of acquiring at least one of a ticket ID and a user ID that identify ticket information, and a facial image of the user, and linking and registering these together; extracting users who may meet predetermined conditions using at least one of image information captured by a surveillance camera in the facility and registered face images; and a step of supporting predetermined measures for a user when a user who may meet predetermined conditions is extracted.

[0204] (Appendix 12) a computer processor; a module that acquires at least one of a ticket ID and a user ID for identifying ticket information and a facial image of a user when the user uses a facility that provides various services, and links and registers these together; a module that extracts users who may meet predetermined conditions using at least one of image information captured by a surveillance camera within the facility and registered facial images; A system comprising: a module that, when a user who may meet predetermined conditions is extracted, supports the user with predetermined measures. [Explanation of symbols]

[0205] 1: Ticket system 10: User terminal 20: Ticket management server 30: Ticket inspection device 351: Thermography 352: Visible light camera 40: Staff terminal

Claims

1. The computer processor When using a facility that provides various services, a step of acquiring at least one of a ticket ID and a user ID that identify ticket information, and a facial image of the user, and linking and registering these together; extracting users who may meet predetermined conditions using at least one of image information captured by a surveillance camera in the facility and the registered face image; and a step of supporting a predetermined measure for a user when the user who may meet the predetermined conditions is extracted.

2. In the step of supporting the measure, transmitting information indicating the possibility that the user meets the predetermined condition to an attendant terminal; 2. The program according to claim 1, wherein the user is determined to be a person who meets the predetermined condition by an input operation to the attendant terminal.

3. In the step of extracting users who may meet the predetermined conditions, Executing a step of detecting a suspected entrant who is suspected of misusing the facility; In the step of providing support for the predetermined measure, The program of claim 1, which executes a step of supporting predetermined punitive measures against a suspect user suspected of committing the fraudulent use or at least one user involved in the distribution of tickets used by the suspect user.

4. In the step of detecting a suspected entrant, The program described in claim 3 compares multiple facial images linked to multiple ticket IDs for the same registered user but different events, and if it is determined that the multiple facial images belong to different people, detects the entrant corresponding to the multiple facial images as the suspect entrant.

5. In the step of detecting a suspected entrant, A program as described in claim 3 or 4, which compares multiple facial images when they are linked to a registered ticket ID, and if it is determined that the multiple facial images belong to different people, detects the entrant corresponding to the multiple facial images as the suspect entrant.

6. In the step of detecting a suspected entrant, Comparing the face of the visitor captured in the image information with a registered face image, 6. The program according to claim 3, wherein a visitor whose face image is not registered is detected as the suspected visitor.

7. the processor, measuring the body temperature of visitors when using the facility; and further executing a step of determining whether the user has a high fever by referring to the measurement result of the user's body temperature. In the step of detecting a suspect user, The program according to claim 3 , wherein a user who is determined to have a high temperature is detected as the suspected entrant.

8. and sending a notification of re-examination to the contact information of the visitor who is determined to have a high fever in the determining step. In the step of detecting a suspected entrant, The program according to claim 7, wherein an entrant who does not comply with the reinspection after receiving the notice of the reinspection is detected as the suspect entrant.

9. The program according to claim 1 , wherein the predetermined sanction is a restriction on future use of the service.

10. In the step of supporting the sanctions, 10. The program according to claim 3, further comprising providing information indicating the location of a suspected visitor suspected of fraudulent use to an attendant terminal.

11. The computer's processor When using a facility that provides various services, a step of acquiring at least one of a ticket ID and a user ID that identify ticket information, and a facial image of the user, and linking and registering these together; extracting users who may meet predetermined conditions using at least one of image information captured by a surveillance camera in the facility and the registered face image; and when a user who may meet the predetermined conditions is extracted, providing support for the user with a predetermined measure.

12. a computer processor; a module that acquires at least one of a ticket ID and a user ID for identifying ticket information and a facial image of a user when the user uses a facility that provides various services, and links and registers these together; a module that extracts users who may meet predetermined conditions using at least one of image information captured by a surveillance camera in the facility and the registered face image; and a module that, when a user who may meet the predetermined conditions is extracted, supports the user with predetermined measures.

Images