JP7722460B2 - Determination system, determination method, and program - Google Patents

Description

This disclosure relates to technology for determining the validity of an electronic ticket.

In order to confirm whether a person requesting a service is eligible to receive that service, authentication is performed using electronic tickets. For example, whether a person requesting admission is eligible to enter a restricted entry location, such as an event venue, can be confirmed by verifying the electronic ticket presented by the person requesting admission.

Patent document 1 describes an electronic ticket system that reads a two-dimensional barcode displayed on a mobile phone as an electronic ticket, compares it with information registered in a ticket issuance database, and performs authentication processing for the electronic ticket.

Patent document 2 describes an authentication terminal 30 that reads a digital ticket output to a mobile terminal 20 and performs authentication processing based on the read content. The digital ticket contains time data indicating the time at which it was output. The authentication terminal 30 performs authentication by comparing the time indicated by the time data with the time at the time of authentication.

Japanese Patent Application Publication No. 2005-316963 Japanese Patent Application Publication No. 2003-242116

There has been a constant stream of cases in which unauthorized individuals attempt to obtain services by misusing the various functions of information terminals used to present electronic tickets. For example, unauthorized individuals may gain access to restricted areas by duplicating electronic tickets that they have not actually purchased. There is a need for technology that can more reliably prevent such fraud involving electronic tickets.

One aspect of the present disclosure has been made in consideration of the above-mentioned problems, and one of its objectives is to prevent fraud related to electronic tickets.

A determination system according to one aspect of the present disclosure includes a generation means for generating an information code corresponding to the electronic ticket, which is sent to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal; an acquisition means for acquiring from the first user terminal location information indicating the location of the first user terminal when the first user terminal displayed the information code; and a determination means for determining that the electronic ticket is invalid if the distance between the location of the first user terminal indicated by the location information and the location of a reading device that read the information code from a second user terminal is greater than or equal to a first threshold value.

A determination method according to one aspect of the present disclosure includes at least one processor generating an information code corresponding to the electronic ticket to be sent to a first user terminal of a user who purchased the electronic ticket in response to a request from the first user terminal; acquiring location information from the first user terminal indicating the location of the first user terminal at the time the first user terminal displayed the information code; and determining that the electronic ticket is invalid if the distance between the location of the first user terminal indicated by the location information and the location of a reading device that read the information code from a second user terminal is greater than or equal to a first threshold.

A program according to one aspect of the present disclosure is a program for causing one or more computers to function as a determination system, and causes one or more computers to perform the following operations: generate an information code corresponding to the electronic ticket to be sent to a first user terminal of a user who purchased the electronic ticket in response to a request from the first user terminal; obtain location information from the first user terminal indicating the location of the first user terminal at the time the first user terminal displayed the information code; and determine that the electronic ticket is invalid if the distance between the location of the first user terminal indicated by the location information and the location of a reading device that read the information code from a second user terminal is greater than or equal to a first threshold.

One aspect of the present disclosure makes it possible to prevent fraud involving electronic tickets.

FIG. 1 is a block diagram illustrating a configuration of a determination system according to a first exemplary embodiment of the present disclosure. FIG. 1 is a flowchart showing the flow of a determination method according to a first exemplary embodiment of the present disclosure. FIG. 10 is a diagram illustrating a specific example in which the determination system of the present disclosure is applied to a ticket management system. 1 is a block diagram showing the configuration of a ticket management system and a main part of a determination system applied to the ticket management system. FIG. 2 is a block diagram showing the main configuration of a user terminal. FIG. 2 is a diagram illustrating an example of ticket information and a data structure of a ticket information database. FIG. 10 illustrates an example of a data structure of a threshold table. 10A and 10B are diagrams illustrating an example of the data structure of code management information and a code management information database. 10 is a flowchart showing the flow of processing in the ticket management system and the user terminal. 10 is a flowchart illustrating an example of a determination process executed by a determination unit. 10 is a flowchart illustrating another example of the determination process executed by the determination unit. FIG. 10 is a diagram showing an example of a determination result display screen. FIG. 10 is a diagram showing an example of a determination result display screen. FIG. 10 is a diagram showing an example of a determination result display screen. FIG. 2 is a block diagram showing an example of a hardware configuration of a determination system 100 according to each exemplary embodiment of the present disclosure. FIG. 10 is a diagram showing an example of a screen displaying an email containing link information.

[Example Embodiment 1]
A first exemplary embodiment of the present disclosure will be described in detail with reference to the drawings. This exemplary embodiment is a base form for the exemplary embodiments described below.

<Configuration of the Determination System>
1 is a block diagram showing the configuration of a determination system according to this exemplary embodiment. As shown in the figure, the determination system 100 includes a generating unit 22, an acquiring unit 23, and a determining unit 24.

In this exemplary embodiment, the generation unit 22 is configured to realize a generation means. In response to a request from the first user terminal of a user who purchased an electronic ticket, the generation unit 22 generates an information code corresponding to the above-mentioned electronic ticket, which is sent to the first user terminal.

In this exemplary embodiment, the acquisition unit 23 is a component that realizes an acquisition means. The acquisition unit 23 acquires, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displayed the information code.

In this exemplary embodiment, the determination unit 24 is configured to realize a determination means. If the distance between the location of the first user terminal indicated by the location information and the location of the reading device that read the information code from the second user terminal is greater than or equal to a first threshold, the determination unit 24 determines that the electronic ticket corresponding to the information code displayed on the second user terminal is invalid.

<Flow of the judgment method>
2 is a flow diagram illustrating a flow of a determination method according to the present exemplary embodiment. The determination method illustrated in FIG. 2 includes generating, obtaining, and determining by at least one processor.

The above-mentioned generating means that at least one processor generates an information code corresponding to the electronic ticket in step S1, which is sent to the first user terminal of the user who purchased the electronic ticket in response to a request from the first user terminal.

The above-mentioned obtaining means that at least one processor obtains, in step S2, location information from the first user terminal indicating the location of the first user terminal when the first user terminal displayed the information code.

The above-mentioned determination means that at least one processor determines that the electronic ticket is invalid if the distance between the location of the first user terminal indicated by the location information and the location of the reading device that read the information code from the second user terminal is greater than or equal to a first threshold value.

In other words, the determination includes, in step S3, comparing the distance between the location of the first user terminal indicated by the location information and the location of the reader that read the information code from the second user terminal with a first threshold. The determination includes, in step S4, determining that the electronic ticket is invalid if the distance is greater than or equal to the first threshold.

Note that, in step S3, if the above-mentioned distance is less than the first threshold, the determination system 100 may proceed from NO in step S3 to step S5. Step S5 may be an optional determination process. In step S5, the determination system 100 may determine that the electronic ticket is valid, or may determine the validity of the electronic ticket based on additional conditions.

<Effects>
According to the above-described configuration and method, when a first user terminal receives an information code issued by the determination system 100 and displays the information code on its own terminal, the determination system 100 acquires the location information of the first user terminal. Next, the information code is read by a reading device from a second user terminal that presented the information code (at this point, it is unknown whether the second user terminal is the same terminal as the first user terminal). The determination system then compares location A of the first user terminal indicated by the location information with location B of the reading device that read the information code from the second user terminal.

In cases where an information code is legitimately presented by a legitimate user who has purchased an electronic ticket, the first user terminal displays the above-mentioned information code for reading by the reading device, and the reading device reads the information code on the spot. Therefore, position A of the first user terminal when it displays the information code and position B when the reading device reads the information code (from the second user terminal) will be approximately the same.

On the other hand, there is a possibility that an information code may be fraudulently presented by a fraudulent user other than the purchaser who purchased the electronic ticket. In such a case, the purchaser's first user terminal displays the above-mentioned information code to be read by a reading device, and a second user terminal belonging to the fraudulent user obtains a copy of the information code from the first user terminal in some way. The second user terminal then displays the obtained copy on its own terminal, which is then read by a reading device. Therefore, there is a possibility that the position A of the first user terminal when the purchaser's first user terminal displays the information code may not match the position B when the reading device reads the copy of the information code from the fraudulent user's second user terminal.

From the above, the determination system 100 can determine that the information code (electronic ticket) is invalid at least when positions A and B are separated by more than the first threshold value.

As an example, the determination system 100 may determine that the first user terminal that displayed the information code and the second user terminal that had the information code read by the reading device are different terminals based on the fact that positions A and B are separated by a first threshold value or more.

As described above, it is possible to verify whether the user terminal of a person attempting to receive the service, who is present at the site where the ticket is being verified and who is using a reading device, is the user terminal of the person who purchased the electronic ticket. Therefore, electronic tickets that have been obtained illegally through duplication or interception can be determined to be invalid, thereby preventing fraud involving electronic tickets, such as the resale of electronic tickets and the impersonation of qualified individuals.

Exemplary Embodiment 2
A second exemplary embodiment of the present disclosure will be described in detail with reference to the drawings. Note that components having the same functions as those described in the first exemplary embodiment are denoted by the same reference numerals, and their description will not be repeated.

<Application example of the judgment system>
FIG. 3 is a diagram showing a specific example in which the determination system 100 of the present disclosure is applied to a ticket management system 1000.

The ticket management system 1000 is a system for providing an agency service for selling and managing electronic tickets, selling electronic tickets to users on behalf of tenants to participate in events hosted by the tenants, and managing the sold electronic tickets. Hereinafter, electronic tickets will be simply referred to as tickets. The ticket management system 1000 may be operated by a service provider that provides this agency service.

The ticket management system 1000 includes, as an example, a server 1, a reading device 2, and a memory unit 11.

In this exemplary embodiment, the determination system 100 of the present disclosure will be described as being applied to the server 1 and memory unit 11 of the determination system 100. Without being limited to this, the entire or part of the determination system 100 may be applied to the reading device 2, or may be distributed and applied to the server 1 and the reading device 2. In this exemplary embodiment, the memory unit 11 may be implemented by a storage device external to the server 1 (such as a cloud server), as shown. Without being limited to this, the memory unit 11 may be implemented as an internal memory of the server 1, an internal memory of the reading device 2, or distributed across multiple internal memories. Each device in the ticket management system 1000, the server 1, the reading device 2, and the memory unit 11, are connected to each other so as to be able to communicate with each other via a communication network such as the Internet.

The server 1 manages sold tickets and determines their validity when the ticket is used. In this exemplary embodiment, as an example, the server 1 may further have a function for selling tickets to users. In this exemplary embodiment, the ticket is realized as an information code of a display type capable of holding various information, such as a one-dimensional code such as a barcode or a two-dimensional code. In this exemplary embodiment, as an example, a QR code (registered trademark) may be adopted as the information code. The server 1 provides an information code corresponding to the ticket to the user terminal 3 of the user who purchased the ticket.

The user terminal 3 is an information processing device that has the function of communicating with the server 1 and the function of displaying an information code. The user terminal 3 may be a small information processing device that is highly portable. The user terminal 3 may be, for example, a smartphone, tablet, small game console, mobile phone, etc.

The memory unit 11 is a storage device that stores data or databases required for the server 1 to perform various processes.

Reading device 2 is a device that reads the information code corresponding to the ticket sold to the user. In this exemplary embodiment, as an example, reading device 2 may be a QR code (registered trademark) reader for reading QR codes (registered trademark). Reading device 2 may be a handheld device that can be held by an attendant checking the ticket, or a stationary device that the user uses by holding the information code over a readable position.

<The process from purchasing a ticket to using it>
A user who wishes to participate in a desired event operates his/her user terminal 3 to communicate with the server 1 and executes a ticket purchase procedure to purchase a ticket corresponding to the desired event.

The server 1 communicates with the user terminal 3, and upon receiving a ticket purchase procedure from the user terminal 3, executes various processes for selling the ticket and registers information about the ticket that has been traded with the user in the memory unit 11. Information about the ticket that has been traded is hereinafter referred to as ticket information.

The information code corresponding to the ticket is used at the event venue to prove to staff that the user is eligible to enter the event venue. Therefore, at the point when the sale is completed, the server 1 does not provide the information code to the user terminal 3. As an example, the server 1 may provide the user terminal 3 with link information for calling up the process so that the user terminal 3 can easily execute the process that requests the information code when necessary.

When the event date and time arrives, the user goes to the event venue and operates the user terminal 3, causing the user terminal 3 to execute a process to request an information code from the server 1. The user terminal 3 then sends an information code issuance request, which is a message requesting the issuance of an information code, to the server 1. The information code issuance request contains various information to identify which user is requesting a ticket for which event.

The server 1 compares the information code issuance request with the ticket information registered in the memory unit 11, generates an information code corresponding to the requested ticket, and issues it to the user terminal 3.

The user terminal 3 displays the information code received from the server 1 on the display unit of the user terminal 3. In this exemplary embodiment of the ticket management system 1000, when the user terminal 3 displays the information code on the display unit, it is configured to transmit the location information of the user terminal 3 at that time to the server 1.

The server 1 registers the location information received from the user terminal 3 to which the information code was issued in the memory unit 11, including the information related to the issued information code. The information related to the issued information code, including the above-mentioned location information, will be referred to as code management information below.

The user presents the information code displayed on the user terminal 3 to the reading device 2, causing the reading device 2 to read the information code. Upon reading the information code, the reading device 2 requests the server 1 to determine whether the read information code is valid or invalid. For example, the reading device 2 sends a validity determination request, which is a message requesting that the server 1 determine whether the information code is valid or invalid, to the server 1. The validity determination request includes various information for identifying which user's and which event's ticket the reading device 2 has read.

The server 1 compares the validity determination request with the ticket information and code management information registered in the memory unit 11 to determine the validity of the read information code. The ticket validity determination process performed by the server 1 will be described in detail later. The server 1 returns the determination result to the reading device 2.

Any user who presents an information code that is determined to be valid will be confirmed as a legitimate user who has purchased a ticket and will be allowed entry to the event venue.

<About user devices>
Hereinafter, the user terminal 3 of the user who has executed the ticket purchase procedure with the server 1 will be referred to as the first user terminal 3A. With regard to the user terminal 3 that subsequently requests the information code of the purchased ticket from the server 1 and receives the information code, the server 1 can verify that it is the same as the first user terminal 3A that purchased the ticket. Therefore, the user terminal 3 that receives and displays the information code and provides location information at that time can also be referred to as the first user terminal 3A.

On the other hand, the user terminal 3 that presents the information code to the reading device 2 and has the information code read is not necessarily the same as the first user terminal 3A. This is because, after an authorized user who purchased a ticket using the first user terminal 3A displays the information code on the first user terminal 3A, there is a way to fraudulently display the information code on another user terminal 3 of another unauthorized user, regardless of whether the authorized user intended it or not.

Therefore, when the reading device 2 successfully reads the information code, it is difficult for it to determine whether the user terminal 3 that presented the information code is the first user terminal 3A of an authorized user or another user terminal 3 of an unauthorized user.

In this exemplary embodiment, the user terminal 3 that presents the information code to the reading device 2 will be referred to below as the second user terminal 3B. When the reading device 2 reads the information code, the second user terminal 3B is certainly located near the reading device 2 so that the reading device 2 can read it. However, at the time the information code is read, it is unclear to the reading device 2 whether the second user terminal 3B is the first user terminal 3A of an authorized user or another user terminal 3 of an unauthorized user.

In addition, when there is no need to distinguish between the first user terminal 3A and the second user terminal 3B, they will simply be referred to as user terminal 3.

<Ticket management system configuration>
FIG. 4 is a block diagram showing the configuration of the ticket management system 1000 and the main components of the determination system 100 applied to the ticket management system 1000.

(Server 1 and Storage Unit 11)
The server 1 includes, for example, a control unit 10 and a communication unit 12. The storage unit 11 is connected to the server 1 so that the control unit 10 can access it.

The control unit 10 provides overall control of the server 1. The control unit 10 is configured, for example, by an arithmetic device such as a CPU (central processing unit) or a dedicated processor. Each part of the control unit 10, described below, can be realized by the arithmetic device reading out and executing a program stored in a storage device realized, for example, as a ROM (read only memory) into a RAM (random access memory).

As an example, the control unit 10 may further include one or more of the sales processing unit 21, notification unit 25, change unit 26, and count unit 27 in addition to the generation unit 22, acquisition unit 23, and determination unit 24 described in exemplary embodiment 1. In this exemplary embodiment, the control unit 10 may further include the sales processing unit 21 and notification unit 25. The change unit 26 and count unit 27 will be described in detail in other exemplary embodiments.

The memory unit 11 stores various data used by the control unit 10. The memory unit 11 may be configured as an external storage device of the server 1, or as built-in memory provided in the server 1. In this exemplary embodiment, the memory unit 11 stores a ticket information database 31 (hereinafter referred to as ticket information DB31), a threshold table 32 (hereinafter referred to as threshold TBL32), and a code management information database 33 (hereinafter referred to as code management information DB33).

As shown in Figure 4, the determination system 100 of the present disclosure includes a generation unit 22, an acquisition unit 23, a determination unit 24, a notification unit 25, a change unit 26, and a counting unit 27 in the server 1. The determination system 100 also stores a ticket information DB 31, a threshold TBL 32, and a code management information DB 33 in the memory unit 11.

The communication unit 12 is a communication device that enables the server 1 to communicate with other devices via a network. For example, the communication unit 12 can communicate with the user's user terminal 3 and the reading device 2 via the Internet.

The sales processing unit 21 of the control unit 10 communicates with the user terminal 3 and accepts the ticket purchase procedure executed by the user terminal 3, thereby performing processing to sell tickets to the user of the user terminal 3. The sales processing unit 21 registers ticket information related to the purchased ticket in the ticket information DB 31. The data structure of the ticket information and ticket information DB 31 will be described in detail later with reference to a separate figure.

In response to an information code issuance request from the first user terminal 3A, the generation unit 22 generates an information code, for example, a QR code (registered trademark), corresponding to the specified ticket. The information code generated by the generation unit 22 is sent to the first user terminal 3A via the communication unit 12, and the information code is thus issued. The generation unit 22 registers code management information for the generated information code in the code management information DB 33. The generation unit 22 may also register part of the code management information related to the generated information code in the code management information DB 33.

The acquisition unit 23 acquires the location information of the first user terminal 3A when the first user terminal 3A displays the issued information code. For example, the first user terminal 3A may be configured to acquire and transmit the location information of its own terminal to the server 1 when the first user terminal 3A displays the above-mentioned information code on its display unit. The acquisition unit 23 acquires the location information of the first user terminal 3A via the communication unit 12. The acquisition unit 23 registers the acquired location information in the code management information DB 33 as part of the above-mentioned code management information.

The determination unit 24 accepts a validity determination request from the reading device 2 and determines whether the requested information code is valid or invalid. In this exemplary embodiment, the determination unit 24 determines the validity of the ticket based on the positional relationship between the first user terminal 3A displaying the information code and the reading device 2 when the information code is read from the second user terminal 3B.

Specifically, the determination unit 24 compares the location information of the first user terminal 3A displaying the above-mentioned information code with the location information of the reading device 2 at the time the information code was read. The location information of the reading device 2 may be provided by the reading device 2, or may be pre-registered in the memory unit 11. The determination unit 24 then calculates the distance between the first user terminal 3A and the reading device 2. The determination unit 24 may determine that the ticket is invalid if the calculated distance is equal to or greater than a first threshold.

As an example, the judgment unit 24 may determine that the first user terminal 3A that displayed the information code and the second user terminal 3B that presented the information code to the reading device 2 are different terminals if the calculated distance is greater than or equal to a first threshold value.

The determination unit 24 may also determine the validity of the ticket based on the time difference between the generation time when the information code addressed to the first user terminal 3A is generated and the reading time when the reading device 2 reads the information code from the second user terminal 3B. Specifically, the determination unit 24 may calculate the time difference between the above-mentioned generation time and the above-mentioned reading time, and determine that the ticket is invalid if the time difference is equal to or greater than a second threshold.

The determination unit 24 may then determine that the ticket is valid if the calculated distance is less than the first threshold and the calculated time difference is less than the second threshold.

The notification unit 25 notifies the reading device 2 of the result of the judgment process performed by the judgment unit 24 (hereinafter referred to as the judgment result) via the communication unit 12.

(Reader 2)
The reading device 2 includes, for example, a control unit 40, a storage unit 41, a communication unit 42, and a reading unit 43. The reading device 2 may further include one or more of a GPS 44, a display unit 45, and a short-range wireless communication unit 46.

The control unit 40 provides overall control of the reading device 2. The control unit 40 is configured, for example, by a calculation device such as a CPU or a dedicated processor. Each part of the control unit 40 described below can be realized by the calculation device reading out and executing a program stored in a storage device (storage unit 41) realized, for example, as a ROM into a RAM or the like.

The control unit 40 may, for example, be provided with a request unit 51.

The memory unit 41 stores various data used by the control unit 40. The memory unit 41 may be configured, for example, as an internal memory provided in the reading device 2.

The communication unit 42 is a communication device that allows the reading device 2 to communicate with other devices via a network. For example, the communication unit 42 can communicate with the user's user terminal 3 or with the server 1 via the Internet.

The reading unit 43 is a mechanism for reading the information code and is composed of a light source for irradiating light onto the information code and an imaging element for receiving reflected light to obtain an image of the information code.

The GPS (Global Positioning System) 44 consists of a module that receives signals from GPS satellites in order to perform positioning of the reading device 2. The signals received by the GPS 44 are processed by the control unit 40 as information including the position information of the reading device 2, such as latitude, longitude, and altitude. If the reading device 2 is a stationary type and its location is fixed, the position information of the reading device 2 can be registered in advance in the memory unit 11 or memory unit 41, and therefore the GPS 44 may be omitted.

The display unit 45 displays information processed by the control unit 40 and is configured, for example, by a liquid crystal display (LCD) or an organic electroluminescence (EL) display. If there is no information to display on the reading device 2, the display unit 45 may be omitted. Alternatively, the display unit 45 may be implemented as an external display device connected to the reading device 2 so that it can communicate with it.

The short-range wireless communication unit 46 realizes wireless communication with an external device over a relatively short range. The short-range wireless communication method or standard implemented by the short-range wireless communication unit 46 may be, for example, Bluetooth (registered trademark), RFID (Radio Frequency IDentification), or infrared communication. If there is no information to be obtained directly from the second user terminal 3B in the ticket management system 1000, the short-range wireless communication unit 46 may be omitted. For example, the short-range wireless communication unit 46 may obtain identification information unique to the second user terminal 3B from the second user terminal 3B.

The request unit 51 of the control unit 40 requests the server 1 to determine the validity of the information code read by the reading unit 43. For example, the request unit 51 generates a validity determination request, which is a message requesting that the validity of the information code be determined, and transmits it to the server 1. As an example, the request unit 51 may generate a validity determination request that includes various information extracted from the information code read by the reading unit 43, the reading time at which the information code was read, and a reading device ID for uniquely identifying the reading device 2. In another exemplary embodiment, the request unit 51 may include in the validity determination request the location information of the reading device 2 obtained by the GPS 44 at the above-mentioned reading time. Alternatively, the request unit 51 may include in the validity determination request identification information obtained directly from the second user terminal 3B via the short-range wireless communication unit 46.

Furthermore, the control unit 40 may be provided with a display control unit 52. The display control unit 52 may display the judgment result notified by the notification unit 25 of the server 1 on the display unit 45.

(User terminal 3)
5 is a block diagram showing the main components of the user terminal 3. The user terminal 3 is, for example, a smartphone, and is configured to include a control unit 60, a storage unit 61, a communication unit 62, an operation unit 63, a GPS 64, and a display unit 65. The user terminal 3 may further include a short-range wireless communication unit 66. The user terminal 3 may also include various components (not shown) that are included in a typical smartphone.

The control unit 60 provides overall control of the user terminal 3. The control unit 60 is composed of, for example, a calculation device such as a CPU or a dedicated processor. Each part of the control unit 60 described below can be realized by the calculation device reading out and executing a program stored in a storage device (storage unit 61) realized in a ROM or the like into a RAM or the like.

The control unit 60 includes, by way of example, a purchase processing unit 71, a code processing unit 72, and a location information processing unit 73. The control unit 60 may further include an identification information processing unit 74, as necessary. The control unit 60 may also include various components (not shown) that are included in the control units of typical smartphones.

The memory unit 61 stores various data used by the control unit 60. The memory unit 61 may be configured, for example, as an internal memory provided in the user terminal 3.

The communication unit 62 is a communication device that enables the user terminal 3 to communicate with other devices via a network. For example, the communication unit 62 can communicate with the server 1 or the reading device 2 via a mobile phone network, the Internet, etc.

The operation unit 63 is an input device through which the user inputs instruction operations to the user terminal 3. The operation unit 63 may be a touch panel formed integrally with the display unit 65.

GPS 64 consists of a module that receives signals from GPS satellites in order to perform positioning of the user terminal 3. The signals received by GPS 64 are processed by the control unit 60 as information including the location information of the user terminal 3, such as latitude, longitude, and altitude.

The display unit 65 displays information processed by the control unit 60 and is configured, for example, by a liquid crystal display device or an organic EL display. The display unit 65 may also be a touch panel formed integrally with the operation unit 63. The display unit 65 can display the information code issued by the server 1 in a manner that can be read by the reading device 2, in accordance with instructions from the code processing unit 72 (described below).

The short-range wireless communication unit 66 realizes wireless communication with an external device over a relatively short range. The short-range wireless communication method or standard implemented by the short-range wireless communication unit 66 may be, for example, Bluetooth (registered trademark), RFID, or infrared communication. The short-range wireless communication unit 66 can transmit identification information unique to the user terminal 3 to the reading device 2, for example, in accordance with instructions from the identification information processing unit 74, which will be described later.

In this exemplary embodiment, as an example, of the above-mentioned components provided in the control unit 60, the purchase processing unit 71, code processing unit 72, and location information processing unit 73 may be realized as a "ticket purchase application." The "ticket purchase application" may be provided by a service provider that operates the ticket management system 1000.

There are no particular limitations on the manner in which the service provider provides the "ticket purchase application" to the user's user terminal 3. As an example, the "ticket purchase application" may be provided as an application that operates in conjunction with a messaging application running on the user terminal 3.

For example, when the above-mentioned messaging application is installed, the service provider's server 1 and the user's user terminal 3 each obtain account information issued by the messaging application. When the user authorizes the service provider's account information as a communication partner (so-called friend registration), the server 1 and user terminal 3 may be able to communicate via the messaging application. The service provider's server 1 may then provide a "ticket purchase application" to the user's user terminal 3 via the messaging application. The "ticket purchase application" may be provided as a browser application that can be used in the messaging application's browser.

The purchase processing unit 71 of the control unit 60 communicates with the server 1 and executes the ticket purchase procedure. The ticket purchase procedure is a procedure for a user to purchase a ticket to participate in a desired event from the event organizer via a service provider. The ticket purchase procedure may include, for example, a process for the user to specify the desired event, a process for the user to confirm the purchase of the ticket at the selling price offered by the service provider, and a process for the user to specify a payment method.

After the ticket purchase procedure is completed, the purchase processing unit 71 may store information for identifying the purchased ticket in the memory unit 61.

The code processing unit 72 requests the server 1 for an information code corresponding to the purchased ticket and displays the information code received from the server 1 on the display unit 65. In this exemplary embodiment, for example, the code processing unit 72 generates an information code issuance request in response to the user inputting an operation to instruct the issuance of a ticket. The code processing unit 72 generates an information code issuance request including information for identifying the user or the user terminal 3 and information for identifying the purchased ticket specified by the user, and sends the information code issuance request to the server 1.

When the code processing unit 72 receives the requested information code from the server 1, it displays the information code on the display unit 65.

The location information processing unit 73 transmits to the server 1 location information indicating the location of the user terminal 3 when the code processing unit 72 causes the information code to be displayed on the display unit 65. In this exemplary embodiment, for example, the location information processing unit 73 may transmit to the server 1 the latitude and longitude information acquired by the GPS 64 when the information code is displayed on the display unit 65 as the location information of the user terminal 3.

The identification information processing unit 74 processes identification information unique to the user terminal 3. The identification information unique to the user terminal 3 is information for uniquely identifying the user terminal 3 that has a one-to-one correspondence with the user in the ticket management system 1000 and the determination system 100. Therefore, the identification information unique to the user terminal 3 allows the user to be uniquely identified in the ticket management system 1000 and the determination system 100.

As an example, the identification information unique to the user terminal 3 may be information individually assigned to the user terminal 3. More specifically, the identification information unique to the user terminal 3 may be a telephone number, an email address, or the like. Alternatively, the identification information unique to the user terminal 3 may be account information assigned to the user terminal 3 through an application installed on the user terminal 3. For example, the account information may be account information assigned in the above-mentioned messaging application.

When a short-range wireless communication connection is established with the reading device 2, the identification information processing unit 74 can transmit identification information unique to the user terminal 3 stored in the memory unit 61 to the reading device 2 via the short-range wireless communication unit 66.

<Ticket information database>
6 is a diagram showing an example of the data structure of the ticket information and ticket information DB 31 stored in the storage unit 11 of the determination system 100. The ticket information DB 31 is a database for registering ticket information for each ticket purchased by various users. One piece of ticket information may include, for example, the following items: ticket ID, purchaser ID, organizer ID, event ID, event name, event date and time, event location, seat reservation information, and status.

The ticket ID is identification information used to uniquely identify a purchased ticket. The sales processing unit 21 assigns a ticket ID to each purchased ticket so that it does not overlap with other tickets.

The purchaser ID is identification information for uniquely identifying the purchaser who purchased the ticket or the purchaser's user terminal 3. In other words, the purchaser ID is identification information specific to the user terminal 3. As shown in the example, the purchaser ID may be the telephone number of the user terminal 3. The sales processing unit 21 associates the telephone number of the user terminal 3 on which the ticket purchase procedure was completed with the purchased ticket.

In this exemplary embodiment, the purchaser ID may function as information indicating the destination for the server 1 to provide information to the user terminal 3.

The organizer ID is information used to uniquely identify the tenant hosting the event that can be attended with the purchased ticket.

The event ID is information that uniquely identifies the event that you can attend with the purchased ticket.

The event name is information that indicates the name of the event that can be attended with the purchased ticket. The event name may be generated to include a string of characters that allows the user or venue staff to identify the content of the event.

The opening date and time (entry date and time) indicates the date and time when the event will be held. In this exemplary embodiment, as an example, the opening date and time does not indicate the so-called opening time when the event starts, but rather the first time when tickets that allow entry to the location where the event will start can be checked (doors opening time).

The venue (entry location) indicates the location where the event is being held. In the illustrated example, the venue is listed as information indicating the name of the location, but the venue may also be identification information that uniquely identifies the location.

Seat designation information is information that indicates the area and location of the venue that can be used by the ticket purchaser. If there are no restrictions on the area within the venue that can be used by the ticket purchaser, this item may be omitted.

The status is information that indicates whether the ticket has been used or not. The status "Used" shown in the figure indicates that the ticket has been used. "Ticket used" means that the ticket has been determined to be valid and the user has gained entry to the event venue.

The "unused" status indicates that the ticket has not been used. "Unused ticket" means that the ticket has not yet been determined to be valid and the user has not yet entered the venue.

The sales processing unit 21 associates the event ID, event name, event date and time, event location, and seat reservation information of the event that can be attended with the purchased ticket with the ticket ID, and registers the ticket information consisting of each of these items in the ticket information DB 31.

When the generation unit 22 receives an information code issuance request from a user terminal 3, it checks whether the ticket information for the ticket specified in the information code issuance request is registered in the ticket information DB 31. Furthermore, if the user terminal 3 that sent the information code issuance request matches the user terminal 3 indicated by the purchaser ID included in the ticket information, the generation unit 22 determines that the request is valid and generates an information code corresponding to the requested ticket. The generation unit 22 may generate an information code for the requested ticket in which all or some of the above-mentioned items contained in the ticket information are embedded.

Furthermore, the sales processing unit 21 may set the status item to "unused" as the initial value when ticket information is registered. When the determination unit 24 determines that the ticket is valid, it may update the status from "unused" to "used." Then, when the determination unit 24 receives another validity determination request for a "used" ticket, it may determine that the information code is invalid. This configuration makes it possible to prevent fraudulent attempts by multiple people to enter using a single ticket.

<Threshold Management Table>
7 is a diagram showing an example of the data structure of the threshold value TBL 32 stored in the storage unit 11. The threshold value TBL 32 is a table for defining threshold values of conditions checked by the determination system 100 to determine the validity of an information code (ticket).

In this exemplary embodiment, as an example, a threshold may be defined for each event. Therefore, the threshold TBL 32 is configured to store thresholds in association with event IDs. If there are multiple conditions checked by the determination system 100, multiple thresholds may be defined for each upper limit for each event. In this exemplary embodiment, as an example, the determination unit 24 of the determination system 100 determines the validity of a ticket based on two conditions: a location condition and a time condition. Therefore, in the threshold TBL 32, for each event, a "position deviation tolerance distance (first threshold)" which is a threshold for the location condition, and a "refresh time (second threshold)" which is a threshold for the time condition are defined.

In this exemplary embodiment, each threshold value may be set in advance to an appropriate value determined based on the hardware and software resources and performance of the ticket checking location at the venue entrance. For example, each threshold value may be set based on the scale of the event, the expected number of attendees, the expected level of congestion, the number of readers 2 installed, the number of staff members to be deployed, etc.

When the judgment unit 24 receives a validity judgment request from the reading device 2, it reads an appropriate threshold value from the threshold TBL 32 based on the event of the requested ticket and can judge the validity of the ticket according to the event.

<Code management information database>
FIG. 8 shows an example of the data structure of the code management information and the code management information DB 33 stored in the storage unit 11. The code management information DB 33 is a database for managing information related to the information codes issued by the generation unit 22. One piece of code management information is generated for each information code issued by the generation unit 22 and registered in the code management information DB 33. The generation unit 22 may generate and issue an information code multiple times for one ticket. For example, it is conceivable that a legitimate user who fails to authenticate a ticket for some reason may request a reissue of an information code for that ticket. Therefore, multiple pieces of code management information may be registered for one ticket.

As an example, the code management information may include the following items: code ID, ticket ID, purchaser ID, display position, reading position, generation time, reading time, and judgment result.

When the generation unit 22 issues one information code, it registers one piece of code management information related to that information code in the code management information DB 33.

The code ID is identification information for uniquely identifying the issued information code. The determination system 100 can use this code ID to identify each issued information code when multiple information codes are issued for a single ticket.

The ticket ID is identification information that uniquely identifies the ticket to which the issued information code corresponds.

The purchaser ID is identification information for uniquely identifying the user terminal 3 of the user who purchased the ticket. As described above, the purchaser ID is specific to the user terminal 3 and may be information indicating the contact information of the user terminal 3. One example of the purchaser ID is the telephone number of the user terminal 3.

The generation time is information indicating the date and time when the generation unit 22 generated the information code in response to an information code issuance request.

The display position is information indicating the location of the first user terminal 3A when the first user terminal 3A displays the issued information code. In this exemplary embodiment, the display position may be latitude and longitude information of the first user terminal 3A.

The reading time is information indicating the date and time when the reading device 2 read the information code.

The reading position is information indicating the position of the reading device 2 when the reading device 2 reads the information code presented by the second user terminal 3B. In this exemplary embodiment, the reading position may be latitude and longitude information of the reading device 2.

The judgment result is information indicating the result of the judgment unit 24's judgment on whether the information code is valid or invalid. "Valid" in the figure indicates that the judgment unit 24 has judged the information code to be valid, and "Invalid" indicates that the judgment unit 24 has judged the information code to be invalid.

When the generation unit 22 generates an information code, it registers the code ID, ticket ID, purchaser ID, and generation time of the information code in the code management information DB 33 as part of the code management information. When the information code is generated, the items after the generation time may be null, and will be completed in a timely manner by each unit of the server 1.

Specifically, when the acquisition unit 23 receives the latitude and longitude information of the first user terminal 3A when the information code is displayed from the first user terminal 3A, it associates the received latitude and longitude information with the code ID of the information code and registers it as the display position.

When the determination unit 24 receives a validity determination request from the reading device 2, it may identify the information code whose validity is to be determined based on the code ID included in the validity determination request. The determination unit 24 may then associate the reading time and reading position included in the validity determination request with the code ID of the identified information code and register them in the code management information DB 33. If the reading device 2 is a stationary type and has a fixed reading position, the determination unit 24 may identify the reading device 2 that sent the validity determination request and register the latitude and longitude information previously registered for the identified reading device 2 as the reading position in the code management information DB 33.

The determination unit 24 calculates the distance between the display position, which is the position information of the first user terminal 3A that displayed the information code, and the reading position, which is the position information of the reading device 2 when the reading device 2 reads the information code from the second user terminal 3B. The determination unit 24 compares the calculated distance with the positional deviation allowable distance set for the event in the threshold TBL32. The event can be identified from the ticket ID associated with the information code whose validity is to be determined. If the calculated distance is equal to or greater than the positional deviation allowable distance, the determination unit 24 determines that the second user terminal 3B is not the first user terminal 3A, and determines that the information code presented by the second user terminal 3B is invalid.

In this exemplary embodiment, the determination unit 24 further calculates the time difference between the generation time when the information code addressed to the first user terminal 3A is generated and the reading time when the reading device 2 reads the information code from the second user terminal 3B. The determination unit 24 compares the calculated time difference with the refresh time set for the event in the threshold TBL32. If the calculated time difference is equal to or greater than the refresh time, the determination unit 24 determines that the information code has expired and is invalid.

The judgment unit 24 associates the judgment result ('valid' or 'invalid') derived for the information code with the code ID of the information code and registers it in the code management information DB 33.

<Processing overview>
FIG. 9 is a flowchart showing the flow of processing by the ticket management system 1000 and the user terminal 3.

In step S101, first, the purchase processing unit 71 of the first user terminal 3A executes the ticket purchase procedure with the server 1.

In step S102, the sales processing unit 21 of the server 1 generates ticket information for the ticket for which the ticket purchase procedure has been completed and registers it in the ticket information DB 31. Here, the sales processing unit 21 may provide various information related to the purchased ticket to the first user terminal 3A. The various information includes, for example, the ticket ID, event ID, event name, event date and time, event location, seat reservation information, etc.

In step S103, the code processing unit 72 of the first user terminal 3A requests the server 1 to issue an information code. For example, the code processing unit 72 generates an information code issuance request including information identifying the ticket, such as a ticket ID and event ID, and a purchaser ID (such as a telephone number) for identifying the first user terminal 3A, and sends it to the server 1.

When the date and time of the event for which the authorized user has purchased a ticket arrives, the authorized user is expected to carry the first user terminal 3A to the event venue and perform operational input to display the information code in front of the reading device 2. In response to the operational input, the code processing unit 72 generates the above-mentioned information code issuance request and sends it to the server 1, thereby requesting the information code from the server 1.

In step S104, the generation unit 22 of the server 1 verifies the information code issuance request and confirms whether the requested ticket is a ticket purchased by the first user terminal 3A. The generation unit 22 may perform the above-mentioned confirmation based on whether the pair of ticket ID and purchaser ID included in the information code issuance request matches the pair of ticket ID and purchaser ID registered in the ticket information DB 31.

If the ticket information for the requested ticket is not registered in the ticket information DB 31, the generation unit 22 proceeds to NO in step S104. Here, the generation unit 22 may send an error message to the first user terminal 3A indicating that the information code cannot be issued, and cancel subsequent processing. On the other hand, if the ticket information is registered in the ticket information DB 31, the generation unit 22 proceeds from YES in step S104 to step S105.

In step S105, the generation unit 22 generates an information code that embeds at least a portion of the ticket information related to the requested ticket and issues it to the first user terminal 3A. Here, the generation unit 22 may register code management information related to the issued information code in the code management information DB 33. For example, the generation unit 22 registers the code ID, ticket ID, purchaser ID, and generation time, etc., as part of the code management information in the code management information DB 33.

In step S106, the code processing unit 72 of the first user terminal 3A receives the issued information code from the server 1 and displays the information code on the display unit 65.

In step S107, the location information processing unit 73 acquires from the GPS 64 the latitude and longitude information of the first user terminal 3A at the time the information code is displayed on the display unit 65 and transmits it to the server 1. The location information processing unit 73 may transmit the latitude and longitude information associated with the code ID to the server 1 so that it is possible to determine which information code was displayed and the latitude and longitude information.

In step S108, the acquisition unit 23 of the server 1 acquires latitude and longitude information from the first user terminal 3A.

In step S109, the acquisition unit 23 registers the acquired latitude and longitude information as a display position in the code management information DB 33. Because the latitude and longitude information is associated with a code ID, the acquisition unit 23 can determine which information code to associate the latitude and longitude information with.

It is assumed that a user (here, it is not yet known whether they are an authorized user or not) will present their own second user terminal 3B with the information code displayed to the reading device 2. When the information code is presented, the reading device 2 will begin the process of reading the information code. If this user is an authorized user, according to the assumptions above, the authorized user will operate the first user terminal 3A in front of the reading device 2 to display the information code, and then immediately present the information code to the reading device 2 on the spot.

In step S110, the request unit 51 of the reading device 2 waits for the reading unit 43 to complete reading the information code. When the reading unit 43 completes reading the information code, the request unit 51 proceeds from YES in step S110 to step S111.

In step S111, the request unit 51 requests the server 1 to determine the validity of the information code read by the reading unit 43. For example, the request unit 51 generates a validity determination request and sends it to the server 1. The validity determination request may include the code ID embedded in the read information code, the reading position and reading time of the reading device 2. The validity determination request may also include an event ID. If the reading position of the reading device 2 is fixed, the request unit 51 may include identification information of the reading device 2 in the validity determination request instead of the reading position.

In step S112, the determination unit 24 of the server 1 executes a determination process to determine the validity of the information code in response to the validity determination request. As described above, in this exemplary embodiment, the determination unit 24 determines the validity of the ticket based on two conditions: a location condition and a time condition. The detailed process flow will be described later with reference to a separate diagram.

In step S113, the notification unit 25 returns the judgment result output by the judgment unit 24 to the reading device 2. The notification unit 25 may also notify the first user terminal 3A of the judgment result.

In step S114, the display control unit 52 of the reading device 2 displays the judgment result on the display unit 45.

In step S115, the code processing unit 72 of the first user terminal 3A may display the judgment result for the displayed information code on the display unit 65. This configuration has the advantage that if the user terminal 3 that presented the information code to the reading device 2 is the first user terminal 3A of an authorized user, the judgment result is presented to the user on the spot. Furthermore, even if the user terminal 3 that presented the information code to the reading device 2 is the second user terminal 3B of a person who is not an authorized user, the notification has the following advantages. Specifically, since the authorized user will receive the judgment result for an act of presentation that they do not remember performing, they will be able to quickly realize that their ticket is being used fraudulently and take measures.

In this way, users whose tickets (information codes) are determined to be valid will be recognized by staff as legitimate users and will be able to enter the event venue.

A user whose ticket (information code) is determined to be invalid is either a legitimate user who failed to present the ticket in a way that met the two conditions mentioned above, or a fraudster who presented a fraudulent ticket. The former can attempt to enter again by consulting with an attendant and having the information code reissued. The latter will be prohibited from entering if fraud is discovered. In this way, it is possible to prevent ticket fraud.

<Specific example of determination process>
FIG. 10 is a flowchart showing an example of the determination process executed by the determination unit 24.

In step S201, the judgment unit 24 identifies the information code read by the reading device 2 that is the target of the judgment process from the code management information DB 33. Specifically, the judgment unit 24 can identify the information code that is the target of the judgment process from the code management information DB 33 based on the code ID included in the validity judgment request sent from the reading device 2.

In step S202, the determination unit 24 reads the allowable positional deviation distance of the event to which the identified information code corresponds from the threshold TBL 32. The determination unit 24 may identify the event to which the information code corresponds based on the event ID included in the validity determination request, or may identify the event based on the event ID associated with the above-mentioned code ID in the code management information DB 33.

In step S203, the judgment unit 24 calculates the distance between the first user terminal 3A and the reading device 2 for the target information code based on the display position registered in the code management information DB 33 and the reading position of the reading device 2.

In step S204, the determination unit 24 compares the calculated distance with the positional misalignment allowable distance read in step S202. If the calculated distance is equal to or greater than the positional misalignment allowable distance, the determination unit 24 proceeds from YES in step S204 to step S205. On the other hand, if the calculated distance is less than the positional misalignment allowable distance, the determination unit 24 proceeds from NO in step S204 to step S207.

In step S205, the determination unit 24 may determine that the second user terminal 3B that presented the information code to the reading device 2 is a different terminal from the first user terminal 3A of the authorized user, based on the fact that the location condition is not satisfied as described above. This process may be omitted.

In step S206, the judgment unit 24 judges that the information code read by the reading device 2 is invalid and that the ticket based on such information code is invalid. The judgment unit 24 outputs a judgment result indicating "invalid." The judgment unit 24 may store the value "invalid" as the judgment result for the information code in the code management information DB 33. The judgment unit 24 may output the judgment result indicating "invalid" to the notification unit 25.

In step S207, the judgment unit 24 reads the refresh time of the event corresponding to the identified information code from the threshold TBL 32. The judgment unit 24 may have read the refresh time together with the positional misalignment allowable distance in step S202.

In step S208, the judgment unit 24 calculates the time difference between the generation time registered in the code management information DB 33 for the target information code and the reading time when the reading device 2 reads the information code.

In step S209, the judgment unit 24 compares the calculated time difference with the refresh time read in step S207. If the calculated time difference is equal to or greater than the refresh time, the judgment unit 24 proceeds from YES in step S209 to step S206. On the other hand, if the calculated time difference is less than the refresh time, the judgment unit 24 proceeds from NO in step S209 to step S210.

In step S210, the judgment unit 24 judges that the information code read by the reading device 2 is valid and that the ticket based on such information code is valid. The judgment unit 24 outputs a judgment result indicating "valid." The judgment unit 24 may store the value "valid" as the judgment result for the information code in the code management information DB 33. The judgment unit 24 may output the judgment result indicating "valid" to the notification unit 25.

<Effects>
As described above, the determination unit 24 can further determine that the ticket is invalid if the time difference between the generation time, which is the time when the generation unit 22 generates the information code, and the reading time, which is the time when the reading device 2 reads the information code, is equal to or greater than the second threshold value. In this exemplary embodiment, the second threshold value is, for example, the refresh time described above.

In other words, the determination unit 24 can determine that the ticket is valid if the distance between the first user terminal 3A and the reading device 2 is less than the first threshold value and the time difference is less than the second threshold value. In this exemplary embodiment, the first threshold value is, for example, the above-mentioned allowable positional misalignment distance.

Since the validity of a ticket is determined based not only on location information but also on time information, the validity of the ticket can be confirmed more accurately compared to when the determination is based only on location information or only on time information. In other words, it is more accurately confirmed that a person present at the site where the reader device 2 is located, such as an entrance, and the second user terminal 3B carried by that person are the ticket purchaser and the first user terminal 3A of that purchaser. This increases the reliability of the determination and makes it possible to further improve security.

In general, improving reliability (the reliability of invalidity determination) and improving service (the smoothness of entry procedures) are in a trade-off relationship that is difficult to achieve. For example, in a configuration where determination is based solely on time information, the shorter the validity period of the information code (the refresh time mentioned above) is set, the higher the reliability can be. On the other hand, it becomes more difficult for users to operate the reader device 2 to successfully read the information code within the validity period after it is displayed. In this way, placing emphasis on improving reliability may result in a loss of service quality (convenience for users).

In contrast, the above-described configuration uses both location information and time information as criteria for judgment, making it possible to accurately confirm that a person present at the scene is a legitimate user without drastically shortening the validity period set for the information code. This improves reliability without sacrificing convenience, and the configuration of the present disclosure, which uses location information in combination with time information as a criteria for judgment, offers significant advantages.

<Modification of Determination Process (1)>
FIG. 11 is a flowchart showing another example of the determination process executed by the determination unit 24.

In this modified example, the determination unit 24 may execute steps S301 and S302 in addition to the steps of the determination process shown in Figure 10. That is, the determination unit 24 may more reliably confirm the identity of the second user terminal 3B by comparing the identification information unique to the second user terminal 3B with the identification information unique to the first user terminal 3A. In this modified example, steps S303 and S304, which will be described later, may or may not be omitted.

In this variant, while the reading device 2 and the second user terminal 3B are approaching each other to read the information code, the reading device 2 acquires identification information unique to the second user terminal 3B from the second user terminal 3B via the short-range wireless communication unit 46. The identification information unique to the second user terminal 3B may be, for example, account information for a messaging application, or more specifically, a telephone number. The short-range wireless communication unit 46 of the second user terminal 3B can transmit the identification information unique to the second user terminal 3B to the reading device 2 via a short-range wireless communication means such as Bluetooth (registered trademark).

In this modified example, in step S111 shown in Figure 9, the request unit 51 of the reading device 2 includes the identification information of the second user terminal 3B obtained during the above-mentioned period in a validity determination request and sends it to the server 1.

In the judgment process shown in Figure 11, for example, the judgment unit 24 may execute steps S301 and S302 after confirming that the position condition is satisfied (NO in step S204).

In step S301, the determination unit 24 reads out identification information unique to the first user terminal 3A from the code management information DB 33. In this modified example, for example, the determination unit 24 reads out from the code management information DB 33 a purchaser ID indicating the purchaser of the ticket to which the identified information code corresponds. The purchaser ID is, for example, a telephone number.

In step S302, the judgment unit 24 compares the identification information unique to the second user terminal 3B, which is included in the validity judgment request, with the read identification information of the first user terminal 3A. The identification information unique to the second user terminal 3B is, for example, a telephone number. If the two pieces of identification information do not match, the judgment unit 24 proceeds from NO in step S302 to step S205 and executes the processes from step S205 onwards. That is, the judgment unit 24 judges that the ticket is invalid. On the other hand, if the two pieces of identification information match, the judgment unit 24 proceeds from YES in step S302 to step S207 and executes the processes from step S207 onwards. That is, the judgment unit 24 proceeds to the process of determining the validity of the ticket based on the time condition.

The above-mentioned method allows for more accurate verification that people present at the event venue are legitimate users who are entitled to enter, further improving the reliability of the determination system.

Whether or not to incorporate the above-mentioned process of verifying identification information unique to the user terminal 3 into the determination of ticket validity may be determined as appropriate. Generally, it is difficult to achieve both improved reliability (reliability of invalidity determination) and improved service (smooth entry procedures). Therefore, the determination system 100 can be configured as appropriate, for example, to incorporate verification of identification information at event venues where improved reliability is more important, and not to employ verification of identification information at event venues where improved service is more important.

Alternatively, in step S105 of Fig. 9, the generation unit 22 may generate an information code in which information capable of identifying identification information (telephone number as a purchaser ID) unique to the first user terminal 3A is embedded. The information code generated here is configured so that when the information code is displayed on the second user terminal 3B, identification information (telephone number) unique to the second user terminal 3B can be added.

Therefore, in step S111, the request unit 51 of the reading device 2 sends an information code including information capable of identifying the purchaser ID (telephone number) of the first user terminal 3A and the telephone number of the second user terminal 3B to the server 1 and requests a validity determination.

In response to this request, in step S301, the determination unit 24 of the server 1 extracts the purchaser ID (telephone number) of the first user terminal 3A that was previously embedded in the information code read by the reading device 2. Alternatively, if the purchaser ID is not embedded in the information code, the determination unit 24 can identify the purchaser ID from the code management information DB 33 based on the code ID and ticket ID embedded in the information code.

In step S302, the judgment unit 24 compares the purchaser ID (identification information of the first user terminal 3A) of the purchaser of the electronic ticket identified based on identifiable information such as the purchaser ID, code ID, and ticket ID with the telephone number (identification information) of the second user terminal 3B added to the information code read by the reading device 2.

If the telephone number of the second user terminal 3B does not match the telephone number of the first user terminal 3A (NO in step S302), the determination unit 24 determines that the electronic ticket is invalid (step S206). If necessary, the determination unit 24 may determine in step S205 that the first user terminal 3A and the second user terminal 3B are different terminals. On the other hand, if the telephone numbers (identification information) of the two terminals match, the determination unit 24 proceeds from YES in step S302 to step S207 and executes the processing from step S207 onwards. In other words, the determination unit 24 proceeds to the process of determining the validity of the ticket based on the time condition.

The above-described method allows for more accurate confirmation that people present at the event venue are legitimate users with admission rights, further improving the reliability of the determination system. Furthermore, the reading device 2 can obtain the identification information of the second user terminal 3B that presented the information code simply by reading the information code. Therefore, there is no need to perform short-range wireless communication between the second user terminal 3B and the reading device 2 to exchange the identification information of the second user terminal 3B, simplifying the operation required for the reading device 2 to successfully read the electronic ticket. As a result, it is possible to achieve both improved user convenience and improved security reliability.

This modified example makes it possible to deal with the following method of fraudulently transferring information codes, for example. According to the determination system 100 described in each of the exemplary embodiments above, fraudulent entry cannot be achieved by photographing an information code displayed on the first user terminal 3A and fraudulently transferring the image. Therefore, fraudulent users may commit fraud by forwarding an email received by the first user terminal 3A from the server 1, which includes link information for calling up a process that requests the information code, from the first user terminal 3A to the second user terminal 3B.

Figure 16 shows an example of an email containing link information. The illustrated email is an example of an email displayed on the second user terminal 3B of the person to whom the electronic ticket has been transferred and who is planning to use it fraudulently. The illustrated email was sent once from the server 1 to the purchaser's first user terminal 3A, and then forwarded by the first user terminal 3A to the second user terminal 3B. It is assumed that the second user terminal 3B will select the link information 161 for requesting an information code contained in the forwarded email, and request the information code corresponding to the electronic ticket purchased by the purchaser from the server 1.

However, even if such a method were to be considered, as described above, when the second user terminal 3B displays the information code provided by the server 1, it would have no choice but to display the information code to which identification information unique to the second user terminal 3B has been added.

When such an information code is read by the reading device 2, the determination unit 24 compares the identification information of the second user terminal 3B added to the information code with the identification information of the first user terminal 3A pre-registered in the code management information DB 33. The determination unit 24 can then detect impersonation based on a mismatch between these pieces of identification information. In this way, the determination unit 24 can determine that the information code (electronic ticket) displayed by the second user terminal 3B is invalid.

<Modification of Determination Process (2)>
In this modified example, the determination unit 24 may execute steps S303 and S304 in addition to the steps of the determination process shown in FIG. 10 . That is, the determination unit 24 can prevent a legitimate user with a valid ticket from entering an event at a wrong venue and/or date and time. Hereinafter, "an erroneous entry" refers to "a legitimate user with a valid ticket entering an event at a wrong venue or date and time, despite mistakenly entering at least one of the venue and date and time permitted by the ticket." The determination unit 24 and the notification unit 25 may be configured to prevent this erroneous entry. The determination unit 24 and notification unit 25 for preventing erroneous entry may be provided not only in the server 1 but also in the reading device 2.

In this variant, the above-mentioned steps S301 and S302 may or may not be omitted.

In this modified example, in step S105 shown in FIG. 9, the generation unit 22 of the server 1 generates an information code embedded with information including at least one of the venue (entry location) and event date and time (entry date and time) permitted to the user who purchased the ticket. When a user purchases a ticket for an event, in this modified example, as an example, the generation unit 22 may generate an information code including the event ID, venue, and event date and time of the event in addition to the code ID, reading position, and reading time. Furthermore, the generation unit 22 may include seat reservation information in the information code as necessary.

In this modified example, the reading unit 43 of the reading device 2 reads the information code in which the various types of information described above are embedded. In step S111 shown in FIG. 9, the request unit 51 of the reading device 2 includes the code ID, event ID, event location, and event date and time extracted from the read information code in a validity determination request and sends it to the server 1. The request unit 51 also includes the reading position and reading time when the reading device 2 read the information code in the validity determination request.

In the judgment process shown in Figure 11, for example, the judgment unit 24 may execute steps S303 and S304 after confirming that the position conditions and time conditions are satisfied (NO in step S209).

In step S303, the judgment unit 24 compares the reading position and reading time of the information code being judged with the venue and date and time of the event extracted from the information code. If at least one of the reading position and reading time at which the reading device 2 read the information code contradicts the information read from the information code (e.g., venue and date and time of the event), the judgment unit 24 proceeds from YES in step S303 to step S304.

In step S304, the judgment unit 24 determines that an incorrect entry has occurred (although the ticket is valid and not fraudulent).

On the other hand, if the determination unit 24 determines that neither the reading position nor the reading time contradicts the read information, it proceeds from NO in step S303 to step S210. In other words, the determination unit 24 determines that no erroneous entry has occurred and that the ticket is valid.

Here, the determination unit 24 does not have to immediately determine that there is a "conflict" based on the fact that the read position and the venue location do not completely match. For example, if the point indicated by the read position (latitude and longitude information) corresponds to an area within the venue premises and within a predetermined distance from the premises, the determination unit 24 can determine that there is no "conflict" between the read position and the venue location. The determination unit 24 may also determine that there is a "conflict" between the read position and the venue location if the point indicated by the read position is away from the venue premises by more than a predetermined distance.

The read time is also not immediately determined to be "inconsistent" based on the fact that it does not completely match the event date and time. For example, if the read time falls within the time period from the opening time when entry to the event venue is permitted to begin until the closing time when the event itself ends, the determination unit 24 can determine that the read time and the event date and time are "not inconsistent." The determination unit 24 may also determine that the read time and the event date and time are "inconsistent" based on (1) the date included in the read time does not match the date indicated by the event date and time, or (2) the dates match but the time indicated by the read time is outside the range of the time period described above.

The determination unit 24 determines that an erroneous entry has occurred based on the fact that at least one of the reading position and reading time is inconsistent with the event location or event date and time.

If the judgment unit 24 outputs a judgment result that an erroneous entry has occurred, as shown in step S113 of Figure 9, the notification unit 25 notifies at least one of the second user terminal 3B and the reading device 2 that presented the information code of this fact.

According to the above-mentioned method, if a user mistakenly arrives at a location or time that differs from the permitted entry location or entry date and time, the user can be notified of the error via a reading device or user terminal. This makes it possible to prevent users from mistakenly entering a location or time that they are not authorized to enter.

<Modification of Determination Process (3)>
The determination unit 24 may output a reason for invalidation, indicating which condition was used to determine that the ticket was invalid, along with the determination result. For example, the determination unit 24 may determine that the ticket is invalid because the location condition is not met (via YES in step S204). In this case, the notification unit 25 may transmit the determination result "invalid" and the reason for invalidation "display position inconsistency" to the reading device 2.

For example, the judgment unit 24 may determine that the time condition is not met and that the ticket is invalid (via YES in step S209). In this case, the notification unit 25 may send the judgment result "invalid" and the invalidation reason "expired" to the reading device 2.

For example, the determination unit 24 may determine that the conditions of the identification information are not met and that the ticket is invalid (via NO in step S302). In this case, the notification unit 25 may transmit the determination result "invalid" and the reason for invalidation "ID mismatch" to the reading device 2. Note that the reason for invalidation does not need to be in language, and may be supplied to the reading device 2 as an error code.

<Display of judgment results>
12 to 14 are diagrams showing examples of the determination result display screen displayed on the display unit of the reading device 2. FIG.

When the communication unit 42 receives a judgment result indicating "valid" from the server 1, the display control unit 52 of the reading device 2 may, as an example, display the judgment result display screen 500 shown in Figure 12 on the display unit 45.

Specifically, the display control unit 52 may generate the determination result display screen 500 to include a first area 501 indicating that the ticket has been determined to be valid. The display control unit 52 may further generate the determination result display screen 500 to include a second area 502 indicating various information about the event that can be attended with the ticket determined to be valid. The various information about the event includes, for example, the event name, date and time, venue, and seat reservation information. The display control unit 52 may display the seat reservation information as a seating guide such as a map in the second area 502. In this case, the user's reserved seat may be highlighted in a different display mode from other seats. For example, the display control unit 52 may display seats other than the user's reserved seat in white and the user's reserved seat in red.

When the communication unit 42 receives a judgment result indicating "invalid" from the server 1, the display control unit 52 may, as an example, display the judgment result display screen 510 shown in Figure 13 on the display unit 45.

Specifically, the display control unit 52 may generate the judgment result display screen 510 so that it includes a third area 511 for indicating that the ticket has been determined to be invalid. The display control unit 52 may further generate the judgment result display screen 510 so that it includes a fourth area 512 for indicating the reason why the ticket is invalid.

Furthermore, the message displayed in the third area 511 urging the user to reissue the information code may be changed depending on the reason for invalidation. For example, if the reason for invalidation is "display position inconsistency," it is possible that the user displayed the information code too early before arriving at the event venue. Therefore, the display control unit 52 may display a message in the third area 511 stating, "Please issue the information code again near the reading device 2."

Alternatively, for example, if the reason for invalidation is "expired," it is possible that the user has had the information code displayed and is waiting for a long time before having the reading device 2 read it. Therefore, the display control unit 52 may display a message in the third area 511 saying, "Please issue the information code again just before having the reading device 2 read it."

When the communication unit 42 receives a judgment result indicating "incorrect entry" from the server 1, the display control unit 52 may, as an example, display the judgment result display screen 520 shown in Figure 14 on the display unit 45.

Specifically, the display control unit 52 may generate the determination result display screen 520 to include a fifth area 521 for indicating that an incorrect entry has occurred. The display control unit 52 may further generate the determination result display screen 520 to include a sixth area 522 for displaying correct information about events to be held at the venue in question, so that the correct information about events that the user can attend using the ticket they own can be compared.

More specifically, one reason why an entry may be determined to be incorrect is that the user displayed the information code before the opening time of the event they are attending. Therefore, the display control unit 52 may display a message on the determination result display screen 520 stating, "The information code may have been displayed before the opening time. Please issue the information code again just before having it read by the reading device 2."

In this way, the judgment results are presented in an easy-to-understand manner to staff and users, making subsequent guidance by staff and user actions smoother.

Exemplary Embodiment 3
A third exemplary embodiment of the present disclosure will be described in detail with reference to the drawings. Note that components having the same functions as those described in the previous exemplary embodiment are denoted by the same reference numerals, and the description thereof will not be repeated.

<Configuration of the Determination System>
4 shows the configuration of the main parts of the determination system 100 according to this exemplary embodiment. In this exemplary embodiment, the control unit 10 of the server 1 includes a change unit 26 as part of the determination system 100.

The modification unit 26 modifies the event threshold defined in the threshold TBL 32 in accordance with input information regarding the event.

Input information about an event refers to various information that correlates with the ticket validation process for that event. For example, input information may include information about the hardware or software resources required to perform the ticket validation process and the target population for the ticket validation process. Furthermore, the input information has values that may change over the period in which the ticket validation process is being carried out.

More specifically, the input information about the event includes the following:
(1) the number of tickets that the reader 2 has read per unit time; (2) the number of users waiting to use the reader 2; (3) the length of the queue of users waiting to use the reader 2; and
(4) At least one of the number of tickets sold and the number of unread tickets calculated from the number of tickets that have been read by the reading device 2 may be used.

Based on input information regarding the above-mentioned event collected in real time from the site where ticket verification work is carried out, the modification unit 26 determines the optimal threshold for the event and updates the threshold TBL32.

For example, the modification unit 26 may analyze that the number of users in input information (2) is gradually increasing, or the queue length in input information (3) is getting longer, but the number of tickets in input information (1) has not changed since the off-peak time period. In this case, the modification unit 26 determines that it is taking a long time to determine the validity of the tickets, causing a slowdown in the flow of people. The modification unit 26 may then decide to relax the conditions in order to speed up the ticket verification process. For example, the modification unit 26 may relax the conditions for the event by increasing the allowable positional deviation distance or the refresh time.

For example, the modification unit 26 may change the allowable positional deviation distance depending on the length of the matrix of input information (3).

For example, if the number of unread tickets in the input information (4) has not decreased below the expected number when the start time of the performance is approaching a predetermined time, the change unit 26 may predict that the event will be crowded just before the start time.The change unit 26 may then relax the conditions for the event by increasing the allowable positional deviation distance or the refresh time.

By relaxing the conditions in this way, users can complete the operation to display the information code on the user terminal 3 early, allowing them to quickly present the information code when it is their turn to use the reading device 2. Relaxing the conditions also reduces the chances that legitimate users will fail to present the information code and have to try again. Overall, this makes it possible to make the ticket verification process proceed more smoothly.

Alternatively, the modification unit 26 may analyze that the number of tickets indicated by input information (1) is greater than expected during a time period when the number of users indicated by input information (2) is relatively low, or during a time period when the queue length indicated by input information (3) is relatively short. In this case, the modification unit 26 may tighten the conditions for the event by shortening the allowable positional deviation distance or the refresh time in order to more reliably detect unauthorized entry, thereby improving the reliability of the determination system 100.

The processing performed by the modification unit 26 may be performed by AI (Artificial Intelligence). In this case, the AI may run on the control device (control unit 10) of the server 1, or on another device (such as an edge computer or cloud server).

<Effects>
With the above configuration, even if the status of the actual ticket verification work for the event changes from moment to moment, the optimum threshold value is set according to the situation at that time, so the determination system 100 can always perform the optimum determination process that takes into consideration the balance between reliability and quality of service while the ticket verification work is being carried out.

Exemplary Embodiment 4
A fourth exemplary embodiment of the present disclosure will be described in detail with reference to the drawings. Note that components having the same functions as those described in the previous exemplary embodiment are denoted by the same reference numerals, and the description thereof will not be repeated.

<Configuration of the Determination System>
4 shows the main configuration of the determination system 100 according to this exemplary embodiment. In this exemplary embodiment, the control unit 10 of the server 1 includes a change unit 26 and a count unit 27 as part of the determination system 100.

The counting unit 27 counts the number of erroneous judgments. An erroneous judgment refers to a case where a valid ticket for a legitimate user is judged to be invalid due to an error in the user's method of presenting the information code. In this exemplary embodiment, when the judgment unit 24 judges a ticket to be invalid more than once and then judges it to be valid the final time in response to multiple information code issuance requests from the same user terminal 3, the counting unit 27 counts the number of erroneous judgments, assuming that the invalid judgment was an error.

The counting unit 27 may count, for each user, the number of times the information code was judged to be invalid (i.e., the number of times the user failed to present the information code) until it was finally judged to be valid, as the number of erroneous judgments.The counting unit 27 may then count the cumulative number of erroneous judgments for each user as the number of erroneous judgments that occurred in that event.

For example, according to the code management information DB 33 shown in Figure 8, three information code issuance requests were made from the same user terminal 3 (purchaser ID: 090-6666-7777), and the judgment unit 24 judged all three requests to be invalid. Then, upon a fourth information code issuance request, the judgment unit 24 judges the ticket to be valid and stores the judgment result of "valid" in the blank space in the judgment result column shown. In this example, the counting unit 27 counts the number of incorrect judgments as three.

Alternatively, the counting unit 27 may count the number of users who were determined to be invalid at least once before the information code was finally determined to be valid (i.e., users who failed to present the information code at least once) as the number of erroneous determinations.The counting unit 27 may then count the cumulative number of users who failed at least once as the number of erroneous determinations that occurred in that event.

In the example shown in Figure 8, according to the code management information DB 33, there is one user who has failed to present the information code at least once: user "Purchaser ID: 090-6666-7777." Therefore, in this case, the counting unit 27 counts the number of incorrect judgments as one.

In this exemplary embodiment, the modification unit 26 modifies the threshold for an event depending on the number of incorrect judgments for that event counted by the counting unit 27.

For example, the modification unit 26 may modify the threshold value so that the conditions are relaxed as the number of erroneous determinations increases. Furthermore, the modification unit 26 may modify the threshold value so that the conditions are relaxed when the proportion of users whose tickets are determined to be valid and whose erroneous determinations are made exceeds expectations.

<Effects>
The above-described configuration allows the threshold to be optimized according to the erroneous judgments that are identified during the actual ticket verification process for an event. This prevents the loss of user convenience in order to increase reliability. In this way, the judgment system 100 can always perform optimal judgment processing that takes into account the balance between reliability and quality of service during the period in which the ticket verification process is being performed.

Exemplary Embodiment 5
A fifth exemplary embodiment of the present disclosure will be described in detail with reference to the drawings. Note that components having the same functions as those described in the previous exemplary embodiments are denoted by the same reference numerals, and the description thereof will not be repeated.

In this exemplary embodiment 2, all or some of the sales processing unit 21, generation unit 22, acquisition unit 23, judgment unit 24, notification unit 25, change unit 26 and counting unit 27 provided in the control unit 10 of the server 1 may be provided in the control unit 40 of the reading device 2.

For example, the determination process performed by the determination unit 24 of the server 1 may be performed by a determination unit 24 provided in the control unit 40 of the reading device 2.

In this exemplary embodiment, the location information processing unit 73 of the first user terminal 3A transmits the latitude and longitude information of the first user terminal 3A at the time the information code is displayed to the reading device 2 via the communication unit 62. The first user terminal 3A may have been notified in advance by the server 1 of the address information of the reading device 2 to which the latitude and longitude information will be transmitted.

Alternatively, there may be multiple reading devices 2 at an event venue, and it may not be known which reading device 2 a user will use until the user actually arrives on the day. In this case, when the request unit 51 of the reading device 2 reads the information code from the second user terminal 3B, it may request the address information of the first user terminal 3A, which is the legitimate owner of the information code, from the server 1.

The reading device 2 may communicate with the first user terminal 3A using the address information of the first user terminal 3A obtained from the server 1, and obtain from the first user terminal 3A the latitude and longitude information when the above-mentioned information code is displayed. Alternatively, the request unit 51 may obtain the latitude and longitude information of the first user terminal 3A from the server 1.

The judgment unit 24 of the reading device 2 determines that the ticket is invalid if the distance between the latitude and longitude information of the first user terminal 3A and the location information of the reading device 2 itself is greater than or equal to a first threshold.

[Software implementation example]
Some or all of the functions of the determination system 100 may be realized by hardware such as an integrated circuit (IC chip), or by software.

In the latter case, the determination system 100 is realized, for example, by one or more computers that execute program instructions, which are software that realize each function. An example of such a computer (hereinafter referred to as computer C) is shown in Figure 15. Computer C has at least one processor C1 and at least one memory C2. Memory C2 stores program P for operating computer C as determination system 100. In computer C, processor C1 reads and executes program P from memory C2, thereby realizing each function of determination system 100.

The processor C1 may be, for example, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), DSP (Digital Signal Processor), MPU (Micro Processing Unit), FPU (Floating Point Number Processing Unit), PPU (Physics Processing Unit), microcontroller, or a combination thereof. The memory C2 may be, for example, a flash memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or a combination thereof.

Computer C may further include RAM (Random Access Memory) for expanding program P during execution and for temporarily storing various data. Computer C may also include a communications interface for sending and receiving data to and from other devices. Computer C may also include an input/output interface for connecting input/output devices such as a keyboard, mouse, display, and printer.

The program P can also be recorded on a non-transitory, tangible recording medium M that can be read by the computer C. Such a recording medium M can be, for example, a tape, a disk, a card, a semiconductor memory, or a programmable logic circuit. The computer C can acquire the program P via such a recording medium M. The program P can also be transmitted via a transmission medium. Such a transmission medium can be, for example, a communications network or broadcast waves. The computer C can also acquire the program P via such a transmission medium.

[Additional Note 1]
The present disclosure is not limited to the exemplary embodiments described above, and various modifications are possible within the scope of the claims. For example, exemplary embodiments obtained by appropriately combining the technical means disclosed in the exemplary embodiments described above are also included in the technical scope of the present disclosure.

[Additional Note 2]
Some or all of the above-described exemplary embodiments can also be described as follows, although the present disclosure is not limited to the following described aspects.

(Appendix 1)
a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code;
A determination system comprising a determination means for determining that the electronic ticket is invalid when the distance between the location of the first user terminal indicated by the location information and the location of the reading device that read the information code from the second user terminal is greater than a first threshold value.

The above-described configuration makes it possible to verify whether the user terminal of a person attempting to receive the service, who is present at the site where the ticket is being verified and who is using a reading device, is the user terminal of the person who purchased the electronic ticket. Therefore, electronic tickets that have been obtained fraudulently using a device other than the purchaser, such as by duplication or interception, can be determined to be invalid. As a result, it is possible to prevent fraud involving electronic tickets, such as the resale of electronic tickets and impersonation of purchasers.

(Appendix 2)
The determination system described in Appendix 1, wherein the determination means determines that the electronic ticket is invalid if the time difference between the generation time, which is the time when the generation means generates the information code, and the reading time, which is the time when the reading device reads the information code, is greater than a second threshold.

With the above-mentioned configuration, by using both location information and time information as criteria for judgment, it is possible to accurately confirm that a person present at the scene is a legitimate user without drastically shortening the validity period set for the information code. In this way, reliability can be improved without sacrificing convenience, so the above-mentioned configuration, which uses location information in combination with time information as a criteria for judgment, offers significant advantages.

(Appendix 3)
The determination means
A determination system as described in Appendix 2, which determines that the electronic ticket is valid if the distance is less than the first threshold and the time difference is less than the second threshold.

With the above-mentioned configuration, by using both location information and time information as criteria for judgment, it is possible to accurately confirm that a person present at the scene is a legitimate user without drastically shortening the validity period set for the information code. In this way, reliability can be improved without sacrificing convenience, so the above-mentioned configuration, which uses location information in combination with time information as a criteria for judgment, offers significant advantages.

(Appendix 4)
A determination system described in any one of Appendices 1 to 3, wherein the determination means determines that the electronic ticket is invalid if the identification information unique to the first user terminal displaying the information code does not match the identification information unique to the second user terminal obtained from the second user terminal via short-range wireless communication when the reading device reads the information code.

The above-mentioned configuration makes it possible to more accurately confirm that the person who is present at the site where the validity of the electronic ticket is being confirmed and who presents the electronic ticket is a person who has the funds to receive the services related to the electronic ticket, thereby further improving the reliability of the determination system.

(Appendix 5)
the generating means generates the information code in which information capable of identifying identification information unique to the first user terminal is embedded, and the information code is capable of adding the identification information unique to the second user terminal when the information code is displayed on the second user terminal;
A determination system described in any one of Appendices 1 to 3, wherein the determination means determines that the electronic ticket is invalid if the identification information unique to the second user terminal added to the information code read by the reading device does not match the identification information unique to the first user terminal identified based on the identifiable information.

The above-described configuration enables more accurate confirmation that a person who is present at the site where the validity of an electronic ticket is being confirmed and who presents the electronic ticket is a person with the right to receive the service related to the electronic ticket, thereby further improving the reliability of the determination system. Furthermore, the reading device can obtain the identification information of the second user terminal that presented the information code from the read information code. Therefore, there is no need to perform short-range wireless communication between the second user terminal and the reading device to exchange the identification information of the second user terminal. This simplifies the operation required to have the reading device successfully read the electronic ticket. As a result, it is possible to achieve both improved user convenience and improved security reliability.

(Appendix 6)
the number of electronic tickets that have been read by the reading device per unit time;
the number of users waiting to use the reading device;
the length of the queue of users waiting to use the reader; and
A determination system described in any one of Appendices 1 to 5, comprising a change means for changing the threshold value in accordance with at least one of the number of electronic tickets sold and the number of unread electronic tickets calculated from the number of electronic tickets that have been read by the reading device.

With the above-described configuration, even if the status of the actual ticket verification work being carried out for the service changes from moment to moment, the optimal threshold is set according to the situation at that time. As a result, the determination system can always perform the optimal determination process that takes into account the balance between reliability and service quality while the ticket verification work is being carried out.

(Appendix 7)
a counting means for counting the number of erroneous determinations, when the determination means determines the request as invalid at least once and determines the request as valid at the last time, based on multiple requests from the same user terminal; and
7. The determination system according to claim 1, further comprising: a change means for changing the threshold value according to the number of times the erroneous determination occurs.

The above-described configuration makes it possible to optimize the threshold for a service in response to the erroneous judgment situations that become apparent as ticket verification work is actually carried out. This avoids compromising user convenience in order to increase reliability. In this way, the judgment system can always perform optimal judgment processing that takes into account the balance between reliability and service quality while ticket verification work is being carried out.

(Appendix 8)
the generating means generates the information code in which information including at least one of an admission location and an admission date and time permitted to the user who purchased the electronic ticket is embedded;
A determination system described in any one of Appendices 1 to 7, comprising a notification means for notifying at least one of the user terminal that presented the information code and the reading device if at least one of the location and time at which the reading device read the information code contradicts the information read from the information code.

With the above-described configuration, if a user mistakenly arrives at a location or time that differs from the permitted entry location or entry date and time, the user can be notified of the error via a reading device or user terminal. This makes it possible to prevent users from mistakenly entering a location or time that they are not authorized to enter.

(Appendix 9)
At least one processor
generating an information code corresponding to the electronic ticket to be transmitted to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displayed the information code;
A determination method including determining that the electronic ticket is invalid if the distance between the location of the first user terminal indicated by the location information and the location of the reading device that read the information code from the second user terminal is greater than a first threshold.

(Appendix 10)
A program for causing a computer to function as a determination system, the program comprising:
a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code; and
A program that functions as a judgment means that determines that the electronic ticket is invalid when the distance between the location of the first user terminal indicated by the location information and the location of the reading device that read the information code from the second user terminal is greater than a first threshold.

[Appendix 3]
Some or all of the above-described exemplary embodiments can also be expressed as follows.

at least one processor, the processor comprising:
a generation process for generating an information code corresponding to the electronic ticket to be transmitted to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
an acquisition process of acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displayed the information code;
A determination system that executes a determination process to determine that the electronic ticket is invalid if the distance between the location of the first user terminal indicated by the location information and the location of the reading device that read the information code from the second user terminal is greater than a first threshold.

The determination system may further include at least one memory, which may store a program for causing the processor to execute the generation process, the acquisition process, and the determination process. The program may also be recorded on a computer-readable, non-transitory, tangible recording medium.

1 Server 2 Reading device 3 User terminal 3A First user terminal 3B Second user terminal 10, 40, 60 Control unit 11, 41, 61 Storage unit 12, 42, 62 Communication unit 21 Sales processing unit 22 Generation unit (generation means)
23 Acquisition Department (Acquisition Means)
24 Judgment unit (judgment means)
25 Notification Department (Notification Means)
26 Change unit (change means)
27 Counting unit (counting means)
43 Reading unit 44, 64 GPS
45, 65 Display units 46, 66 Short-range wireless communication unit 51 Request unit 52 Display control unit 63 Operation unit 71 Purchase processing unit 72 Code processing unit 73 Position information processing unit 74 Identification information processing unit 100 Determination system 1000 Ticket management system

Claims (19)

a generating means for generating an information code corresponding to the electronic ticket and transmitting the information code to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code;
a determination means for determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value ;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request.
Judging system. The determination system described in claim 1, wherein the determination means acquires a generation time, which is the time when the generation means generates the information code, and a reading time , which is the time when the reading device reads the information code, and determines that the electronic ticket is invalid if the time difference between the generation time and the reading time is greater than a second threshold. The determination means
The determination system according to claim 2 , wherein the electronic ticket is determined to be valid if the distance is less than the first threshold and the time difference is less than the second threshold. A determination system as described in any one of claims 1 to 3, wherein the determination means acquires identification information unique to the first user terminal that displays the information code, and acquires identification information unique to the second user terminal from the second user terminal via short-range wireless communication when the reading device reads the information code, and determines that the electronic ticket is invalid if the identification information unique to the first user terminal does not match the identification information unique to the second user terminal. the generating means generates the information code in which information capable of specifying identification information unique to the first user terminal is embedded,
When the information code is displayed on the second user terminal, identification information unique to the second user terminal is added to the information code;
A determination system described in any one of claims 1 to 3, wherein the determination means determines that the electronic ticket is invalid if the identification information unique to the second user terminal added to the information code read by the reading device does not match the identification information unique to the first user terminal identified based on the identifiable information. the number of electronic tickets that have been read by the reading device per unit time;
the number of users waiting to use the reading device;
the length of the queue of users waiting to use the reader; and
A determination system as described in any one of claims 1 to 5, comprising a change means for acquiring as input information at least one of the number of electronic tickets sold and the number of unread electronic tickets calculated from the number of electronic tickets that have been read by the reading device, and for changing at least one of the thresholds referenced by the determination means, including the first threshold, in accordance with the acquired input information. a counting means for counting the number of erroneous determinations, when the determination means determines the request as invalid at least once and determines the request as valid at the last time, based on multiple requests from the same user terminal; and
The judgment system according to claim 1 , further comprising: a change means for changing at least one of the thresholds referred to by the judgment means, including the first threshold, depending on the number of times the incorrect judgment has occurred. the generating means acquires from a ticket information database at least one of the location and date of admission permitted to the user who purchased the electronic ticket, and generates the information code in which the acquired information is embedded;
A determination system as described in any one of claims 1 to 7, further comprising a notification means for notifying at least one of the user terminal that presented the information code and the reading device of the fact that at least one of the location and time at which the reading device read the information code contradicts the information read from the information code. At least one processor
generating an information code corresponding to the electronic ticket to be transmitted to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displayed the information code;
determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value ;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
generating the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
Judgment method. A program for causing a computer to function as a determination system, the program comprising:
a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code; and
and determining that the electronic ticket is invalid when the distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request.
program. a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code;
a determination means for determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
the generating means generates the information code in which information capable of specifying identification information unique to the first user terminal is embedded,
When the information code is displayed on the second user terminal, identification information unique to the second user terminal is added to the information code;
A determination system in which the determination means determines that the electronic ticket is invalid if the identification information unique to the second user terminal added to the information code read by the reading device does not match the identification information unique to the first user terminal identified based on the identifiable information. At least one processor
generating an information code corresponding to the electronic ticket to be transmitted to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displayed the information code;
determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
generating the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
In the generating step, the information code is generated in which information capable of specifying identification information unique to the first user terminal is embedded;
When the information code is displayed on the second user terminal, identification information unique to the second user terminal is added to the information code;
A determination method in which, in the determination, the electronic ticket is determined to be invalid if the identification information unique to the second user terminal added to the information code read by the reading device does not match the identification information unique to the first user terminal identified based on the identifiable information. A program for causing a computer to function as a determination system, the program comprising:
a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code; and
and determining that the electronic ticket is invalid when the distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
the generating means generates the information code in which information capable of specifying identification information unique to the first user terminal is embedded,
When the information code is displayed on the second user terminal, identification information unique to the second user terminal is added to the information code;
The determination means is a program that determines that the electronic ticket is invalid if the identification information unique to the second user terminal added to the information code read by the reading device does not match the identification information unique to the first user terminal identified based on the identifiable information. a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code;
a determination means for determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
the number of electronic tickets that have been read by the reading device per unit time;
the number of users waiting to use the reading device;
the length of the queue of users waiting to use the reader; and
A determination system comprising: a change means for acquiring, as input information, at least one of the number of electronic tickets sold and the number of unread electronic tickets calculated from the number of electronic tickets that have been read by the reading device; and a change means for changing, in accordance with the acquired input information, at least one of the thresholds referenced by the determination means, including the first threshold. At least one processor
generating an information code corresponding to the electronic ticket to be transmitted to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displayed the information code;
determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
generating the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
the at least one processor:
the number of electronic tickets that have been read by the reading device per unit time;
the number of users waiting to use the reading device;
the length of the queue of users waiting to use the reader; and
A determination method comprising: acquiring, as input information, at least one of the number of electronic tickets sold and the number of unread electronic tickets calculated from the number of electronic tickets that have been read by the reading device; and changing, according to the acquired input information, at least one of the thresholds referenced in the determination, including the first threshold. A program for causing a computer to function as a determination system, the program comprising:
a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code; and
and determining that the electronic ticket is invalid when the distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
The computer
the number of electronic tickets that have been read by the reading device per unit time;
the number of users waiting to use the reading device;
the length of the queue of users waiting to use the reader; and
A program that acquires as input information at least one of the number of electronic tickets sold and the number of unread electronic tickets calculated from the number of electronic tickets that have been read by the reading device, and further functions as a modification means that changes at least one of the thresholds referenced by the determination means, including the first threshold, according to the acquired input information. a generating means for generating an information code corresponding to the electronic ticket and transmitting the information code to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code;
a determination means for determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
a counting means for counting the number of erroneous determinations, when the determination means determines the request as invalid at least once and determines the request as valid at the last time, based on multiple requests from the same user terminal;
A determination system further comprising: a change unit that changes at least one of the thresholds referred to by the determination unit, including the first threshold, in accordance with the number of times of the erroneous determination. At least one processor
generating an information code corresponding to the electronic ticket to be transmitted to a first user terminal of a user who has purchased the electronic ticket in response to a request from the first user terminal;
acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displayed the information code;
determining that the electronic ticket is invalid when a distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
generating the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
In the determination, triggered by multiple requests from the same user terminal, if the request is determined to be invalid at least once and is determined to be valid at the last time, the invalid determination is considered to be an error and the number of erroneous determinations is counted;
The determination method further includes changing at least one of thresholds referred to in the determination, including the first threshold, according to the number of times the erroneous determination occurs. A program for causing a computer to function as a determination system, the program comprising:
a generating means for generating an information code corresponding to the electronic ticket, which is to be transmitted to a first user terminal of a user who has purchased the electronic ticket, in response to a request from the first user terminal;
an acquisition means for acquiring, from the first user terminal, location information indicating the location of the first user terminal when the first user terminal displays the information code; and
and determining that the electronic ticket is invalid when the distance between the location of the first user terminal indicated by the location information and the location of a reader that reads the information code from the second user terminal is equal to or greater than a first threshold value;
the location of the reader is provided by the reader when it reads the information code or is stored in advance;
the generating means generates the information code corresponding to the electronic ticket based on information identifying the electronic ticket included in the request;
The computer
a counting means for counting the number of erroneous determinations, when the determination means determines the request as invalid at least once and determines the request as valid at the last time, based on multiple requests from the same user terminal; and
a change unit that changes at least one of the thresholds referred to by the determination unit, including the first threshold, according to the number of times of the erroneous determination.