Terminal device, admission registration method, and program

Abstract

To allow subsequent entry registration even if a user does not register upon entry.SOLUTION: When a user terminal 40 is authenticated via single sign-on in at least one of multiple applications, by running an entry registration application, a user using the user terminal 40 is authenticated. If the authentication is successful, events for which the user's entry status is not registered are extracted. If the extracted event has ended, the location where the extracted event was held is identified. Within the period during which the extracted event was held, the location of the user terminal 40 at the time of authentication via single sign-on is identified. If the identified location and the identified event location are within a predetermined range, an attempt is made to register with an admission management server 10 that a user has entered the extracted event.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a terminal device, an admission registration method, and a program. [Background technology]

[0002] A point system has been proposed in which a mobile terminal has the following functions: when one of the conditions is that the location of the mobile terminal is determined to be within a specified location range, it starts accepting a standby start instruction from the user; when the standby start instruction is accepted, it starts waiting for a wireless signal; and when a wireless signal is detected, it is capable of transmitting check-in information including identification information of the mobile terminal to a server via a network; and when the server obtains the check-in information, it updates the user's points related to the identification information of the mobile terminal included in the check-in information (for example, Patent Document 1).

[0003] In addition, a simulation game device has been proposed that uses location information to register location areas of any store, facility, etc. on a map, and then uses the location information to input the name of the store, facility, etc. and check in to the location area of ​​the registered store, registered facility, etc., thereby obtaining and counting points and linking them with online games (for example, Patent Document 2). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 5131883 [Patent Document 2] JP 2018-37051 A Summary of the Invention [Problem to be solved by the invention]

[0005] In technology for awarding points based on checking in to facilities, etc., as described in Patent Documents 1 and 2, for example in a system in which benefits can be obtained by entering an event at a baseball stadium, etc., it is desirable to enable retroactive registration of entry going back to the day of the event, even if a user forgets to check in when entering the event.

[0006] The present invention has been made in consideration of the above-mentioned situation, and aims to provide a terminal device etc. that enables a user to register for admission later even if the user did not register for admission at the time of entry. [Means for solving the problem]

[0007] In order to achieve the above object, the terminal device of the present invention comprises: A terminal device capable of operating a plurality of applications including an admission registration application, The terminal device Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the terminal device is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying a location of the terminal device when the authentication by the single sign-on was performed during a period in which the extracted event was held; If the identified location and the identified venue are within a predetermined range, an attempt is made to register that the user has attended the extracted event.

[0008] If the identified location and the identified venue are not within a predetermined range, an attempt may be made to register that the user has not attended the extracted event.

[0009] If the extracted event is currently being held, authentication information may be displayed on the screen to allow the user to enter the event or to authenticate that the user has entered the event.

[0010] When authenticating the user, the location of the terminal device may be associated with the date and time of the authentication and stored in the terminal device or transmitted to a server for recording location information.

[0011] When extracting an event for which it is not registered whether the user has attended, an event currently being held may be extracted, or, if there is no event currently being held, the most recent event that has already finished may be extracted.

[0012] When extracting an event for which it is not registered whether the user has attended, recent events that are currently being held and have already finished may be extracted.

[0013] In order to achieve the above object, the admission registration method of the present invention comprises the steps of: An admission registration method executed by a terminal device capable of running a plurality of applications including an admission registration application, comprising: The terminal device Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the terminal device is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying a location of the terminal device when the authentication by the single sign-on was performed during a period in which the extracted event was held; If the identified location and the identified venue are within a predetermined range, an attempt is made to register that the user has attended the extracted event.

[0014] In order to achieve the above object, the program of the present invention comprises: A computer capable of running multiple applications, including the admission registration application, Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the computer is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying the location of the computer when the single sign-on authentication was performed during the period in which the extracted event was held; if the identified location and the identified venue are within a predetermined range, attempting to register that the user has attended the extracted event; Function as a terminal device. Effect of the Invention

[0015] According to the present invention, even if a user does not register for admission at the time of admission, admission registration can be made after the fact. [Brief description of the drawings]

[0016] [Figure 1] 1 is a block diagram showing a configuration of an admission management system according to an embodiment of the present invention; [Diagram 2] 1 is a diagram illustrating an example of a hardware configuration of an information processing device that constitutes an entrance management system according to an embodiment of the present invention. [Diagram 3] 1A is a diagram showing an example of user ticket information, FIG. 1B is an example of user entry / non-entry information, and FIG. 1C is an example of user position information. [Figure 4] 13 is a flowchart illustrating an example of an application sign-on process. [Diagram 5] 13 is a flowchart illustrating an example of a process during sign-on to a fan club application. [Figure 6] 13 is a flowchart illustrating an example of a position information recording process. [Figure 7] 13 is a flowchart showing an example of an admission information registration process. [Figure 8] FIG. 11 is a sequence diagram showing an automatic entrance registration sequence in the entrance management system. [Figure 9] 13A to 13D are diagrams showing examples of displays on a user terminal. [Figure 10] 13A and 13B are diagrams showing examples of displays on a user terminal. [Figure 11] 13A and 13B are sequence diagrams showing an admission registration sequence in an admission management system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] An admission control system 100 according to an embodiment of the present invention will now be described with reference to the drawings. Note that the same or corresponding parts in the drawings are given the same reference numerals.

[0018] 1 is a block diagram showing the configuration of an admission management system 100 according to this embodiment. The admission management system 100 is a system that records whether or not a user has entered an event (event venue), and provides users with benefits such as points, coupons, prizes, and tickets based on whether or not they have entered and the number of times they have entered. The admission management system 100 of this embodiment is composed of an admission management server 10, an authentication server 20, a user terminal 40, a check-in device 50, and multiple service servers 60, each of which is connected via a communication network 30 such as the Internet or a mobile communication network.

[0019] The entrance management server 10 manages event ticket information held by the user and whether the user has entered (or attended) the event venue. For example, the entrance management server 10 provides an application for managing whether the user has entered the event. The application has functions such as providing event information related to the target the user supports, live broadcasting of the event, recorded broadcasting of the event, displaying messages from the target, displaying the results and achievements of the target, communication between fans using the application, and online purchase of goods, as well as a function for purchasing tickets to participate in the event and a function for displaying the tickets (electronic tickets) at the event venue. In this embodiment, this application is called a fan club application. The user can access the entrance management server 10 via the fan club application. The entrance management server 10 provides services according to each function of the fan club application.

[0020] The admission management server 10 also manages whether or not a user has entered (attended) an event venue where a specific event is held. Specifically, the admission management server 10 records whether or not a user has entered the event venue based on the user's entry information received from the check-in device 50. In this embodiment, the admission management server 10 records the entry of the user to the event venue, or attempts to record the user's entry to the event venue, which is called admission registration or check-in. The admission management server 10 then performs a process of granting a privilege to the user depending on the entry or absence of the user to a specific event venue and the number of entries. The user can attempt admission registration at the event venue by holding an electronic ticket displayed by the fan club app over the check-in device 50, for example. The fan club app of this embodiment is an example of an admission registration app having a function for admission registration to the event venue.

[0021] In this embodiment, the admission management server 10 stores location information when a user signs on (logs in) to a specific application, and based on the location information, admission registration (automatic check-in) can be performed for an event that has finished and for which admission or non-admission has not been registered. Details of admission registration based on location information will be described later.

[0022] In this embodiment, a group of companies or the like that operates the admission management server 10 is a service provider that provides multiple services (e.g., electronic money services, electronic commerce services, etc.) including at least the services provided by the admission management server 10, such as event ticket sales, electronic ticket distribution, and user admission management to the event venue. The service server 60 is a server that provides and manages these multiple services. Single sign-on using the same account is possible for the multiple services provided by the service provider. In this embodiment, this account is called a group account.

[0023] The authentication server 20 is an SSO server that performs single sign-on (SSO) authentication of the group account. For example, when a user attempts to sign on to a group account, such as signing on to an application (fan club app) for connecting to the entrance management server 10, using the user terminal 40, the entrance management server 10 transmits an authentication request (access information of an authentication screen, etc.) to the authentication server 20 to the user terminal 40. In response to this, the user inputs a sign-on ID and password, and the authentication server 20 authenticates the sign-on ID and password. If the authentication is successful, the authentication server 20 transmits an authentication response (access information of a signed-on screen, an authentication token, etc.) to the user terminal 40, thereby completing the sign-on to the group account. Through the above flow, the single sign-on of the group account is realized. Once the single sign-on to the group account is completed, the user can access services (apps, websites) provided by the entrance management server 10 and the service server 60 without authentication until signing off. In this embodiment, the single sign-on method is assumed to be the SAML (Security Assertion Markup Language) method, but other methods such as a reverse proxy method, an agent method, etc. may be adopted. Also, the authentication procedure may be arbitrary as long as it can realize single sign-on of a group account.

[0024] The user terminal 40 is an information processing device such as a smartphone or tablet that can be carried by a user. The user terminal 40 displays an electronic ticket (e.g., a two-dimensional code, a barcode) and a code indicating a user ID (e.g., a two-dimensional code, a barcode) on the display screen based on the user's operation. The electronic ticket and the code indicating the user ID may be displayed via an application signed on by a group account.

[0025] The check-in device 50 is a device provided at an event venue for registering for admission to the event venue. The procedure for admission registration using the check-in device 50 is also referred to as check-in. The check-in device 50 reads an electronic ticket or code displayed on the user terminal 40, and based on the read information, transmits admission information for the event venue (e.g., information including user, ticket, and device identification information, event date and time, etc.) to the admission management server 10. Based on the received admission information, the admission management server 10 registers that the user has entered the event venue.

[0026] In this embodiment, an entrance gate of the event venue (a reading device installed at the entrance gate) and a self-check-in device installed at a predetermined installation location within the event venue are assumed as the check-in device 50. Fig. 11 is a sequence diagram showing the entrance registration sequence (check-in procedure) in the entrance management system 100.

[0027] FIG. 11(A) shows the admission registration sequence at the admission gate. As shown in FIG. 11(A), when a user holds an electronic ticket displayed on a user terminal 40 over a check-in device 50 at the admission gate, the check-in device 50 reads a ticket ID, which is identification information of the ticket included in the electronic ticket, and a user ID, which is identification information of the user, and transmits them to the admission management server 10. When the admission management server 10 receives the ticket ID and the user ID, it performs an authentication process of the ticket by checking the ticket held by the user specified by the user ID, and transmits the authentication result to the check-in device 50. Note that it is assumed here that the authentication result is successful (admission OK). When the check-in device 50 receives the authentication result of admission OK, it displays the authentication result on a display device provided on the check-in device 50 or the admission gate, for example, and performs control to open the admission gate and permit the user to enter the event venue. Note that a staff member may guide the user to the event venue based on the authentication result displayed on the display device. Furthermore, if the admission management server 10 succeeds in authenticating the ticket, it performs admission registration corresponding to the user ID and ticket ID, and notifies the user terminal 40 that admission registration has been completed. In this way, the user can automatically perform admission registration for the event by entering the event venue using the electronic ticket.

[0028] FIG. 11(B) shows the admission registration sequence at the self-check-in device in the event venue. As shown in FIG. 11(B), when a code indicating the user ID displayed on the user terminal 40 (for example, a code corresponding to a member's card or a point card that can identify the user) is held over the check-in device 50 installed in the venue, the check-in device 50 reads the user ID and transmits it to the admission management server 10 together with the identification information (device ID) of the check-in device 50 as information that can identify the event or the event venue. The device ID may be, for example, the identification information of the event or the event venue, as long as it is information that can identify the sender of the user ID. Upon receiving the user ID and device ID, the admission management server 10 extracts the ticket held by the user identified by the user ID, and performs admission registration corresponding to the user ID and ticket ID according to the possession of a ticket for the event identified by the device ID, and notifies the user terminal 40 that admission registration has been completed. In this way, even if a user enters the event venue with a ticket held by someone else or with a paper ticket, the user can use the self-check-in device in the venue to perform admission registration to the event. It should be noted that check-in may also be possible using a physical paper ticket, a membership card, a point card (a code written on the card), or the like.

[0029] The above description concerns a normal check-in procedure using the check-in device 50. The automatic check-in procedure, which is characteristic of this embodiment, will be described later.

[0030] In addition, in this embodiment, even if the user forgets to register for admission at an event venue as shown in Fig. 11, if it is determined that the user was at the event venue when the event was held based on the user's location information, admission registration after the event is possible. Post-event admission registration will be described later.

[0031] 1 shows two user terminals 40 and one check-in device 50, the number of user terminals 40 and check-in devices 50 may be arbitrary. Also, although two service servers 60 are shown, the number of service servers 60 may be increased or decreased depending on the services provided by the service provider.

[0032] The entrance management server 10, the authentication server 20, and the service server 60 are configured by, for example, a personal computer (PC), a workstation, or other information processing device capable of communication. At least one of the entrance management server 10, the authentication server 20, and the service server 60 may be a dedicated device. The authentication server 20 may be configured integrally with the entrance management server 10. A portion of the functions of one server may be realized by the other server. The service server 60 may be configured integrally with the entrance management server 10. The entrance management server 10 may have at least a portion of the functions of the service server 60.

[0033] 2 is a diagram showing an example of the hardware configuration of information processing devices constituting the entrance management server 10, the authentication server 20, the user terminal 40, and the service server 60. The entrance management server 10 has a processor 11 such as a CPU (Central Processing Unit) or a GPU (Graphical processing unit), a storage device 12 such as a memory, an HDD and / or an SSD, a communication interface 13 for wired or wireless communication, an input device 14 for accepting input operations, and an output device 15 for outputting information. The input device 14 is, for example, a keyboard, a touch panel, a mouse and / or a microphone, etc. The output device 15 is, for example, a display and / or a speaker, etc.

[0034] Similarly, the authentication server 20 has a processor 21, a storage device 22, a communication interface 23, an input device 24, and an output device 25. Similarly, the user terminal 40 has a processor 41, a storage device 42, a communication interface 43, an input device 44, and an output device 45. Similarly, the service server 60 has a processor 61, a storage device 62, a communication interface 63, an input device 64, and an output device 65. Note that unnecessary components may be omitted as appropriate.

[0035] FIG. 3 shows an example of data stored in the storage device 12 of the admission management server 10. The storage device 12 of the admission management server 10 stores, for example, user ticket information indicating tickets held by the user, user entry / departure information indicating whether the user has entered an event, and user location information indicating location information at the time of user sign-on. As shown in FIG. 3(A), the user ticket information is information that associates a user ID that uniquely identifies a user, a ticket ID that uniquely identifies a ticket for an event, the date and time of the event (date, period, time, etc.), and the event venue (venue name, location information, etc.) of the event. When a user holds multiple tickets, the user ID may be linked to multiple ticket IDs. When a user purchases a ticket by electronic means on a website or application provided by the admission management server 10, the user ticket information corresponding to the ticket is registered in the storage device 12. The user ticket information is referenced for authentication when the user enters an event venue using an electronic ticket.

[0036] As shown in FIG. 3B, the user entrance information is information that associates a user ID, the date and time of an event, the event venue, and information indicating whether the user has entered the event. Each user ID is linked to all related events (for example, events corresponding to a fan club to which the user belongs), and information indicating whether the user has entered all of the events is also linked to the user ID. The user entrance information is added whenever a schedule for an event related to the user (for example, an event corresponding to a fan club to which the user belongs) is decided. Thus, the entrance management server 10 acquires or stores the schedule of an event related to the user's support target. When the entrance management server 10 receives the entrance information including the user ID, etc., the information indicating whether the user has entered the corresponding user ticket information is updated to a status indicating that the user has entered based on the entrance information, and the entrance registration is completed. The information indicating whether the user has entered has three statuses, namely, unregistered, entered, and not entered. The status is unregistered until the entrance registration is completed, such as before the event is held, and the status is entered when the entrance information is received. If the user has not entered, the status is entered. The entry management server 10 registers the entry by changing the information indicating the entry status into the entry status.

[0037] As shown in FIG. 3(C), the user location information is recorded by associating a user ID for identifying a user, the sign-on date and time when the user signed on to the group account, and the location information acquired from the user terminal 40 when the user signed on. When a user signs on to a group account, the corresponding new user location information is registered in the storage device 12. Note that, when the user signs on using a terminal device that does not have a positioning device such as a PC, etc., and location information cannot be acquired, the user location information does not need to be recorded. Alternatively, in this case, a status indicating that location information is unknown may be recorded. Note that, when a user signs on to a group account for a service provided by the service server 60, the service server 60 records the user location information and shares it with the entrance management server 10.

[0038] 3 is an example, and may include other information (such as an event ID). If the event venue is fixed, information about the event venue may not be included.

[0039] Next, a description will be given of the operation of the entrance management system 100. The processes shown in Figures 4 and 5 are executed, for example, by the processor 41 of the user terminal 40 reading a program stored in the storage device 42.

[0040] 4 is a flowchart showing an example of application sign-on processing executed by user terminal 40. In the application sign-on processing, processor 41 of user terminal 40 determines whether or not a sign-on operation by a user has been detected for any of the applications available through a group account (step S11). The sign-on operation is, for example, starting an application in user terminal 40, displaying a sign-on screen, or inputting a user ID and password on the sign-on screen. If no sign-on operation is detected (step S11; No), processor 11 ends the application sign-on processing.

[0041] Applications provided by a service provider and available through a group account include, for example, the above-mentioned fan club application that allows users to purchase tickets and has a function for displaying electronic tickets, an electronic money application that has a payment function, a point card application that can display a code corresponding to a user ID, etc. Such applications available through a group account are also called group applications.

[0042] Then, when a sign-on operation for any of the group applications is detected (step S11; Yes), the processor 11 transmits authentication information such as a user ID and a password to the authentication server 20 (step S12).

[0043] If an authentication response is received from the authentication server 20 and the authentication is unsuccessful (step S13; No), the processor 11 displays an authentication failure screen indicating that at least one of the user ID and password is incorrect (step S16), and terminates the application sign-on process.

[0044] When an authentication response is received from the authentication server 20 and the authentication is successful (step S13; Yes), the processor 11 acquires current location information of the user terminal 40 from a positioning device such as a global positioning system (GPS) provided in the user terminal 40, and transmits the information to the entrance management server 10 or the service server 60 (step S14). As a result, when single sign-on is performed to at least one of the group apps, the location information of the user terminal 40 at the time of sign-on or immediately after sign-on can be recorded on the service provider side such as the entrance management server 10 or the service server 60. The current location information of the user terminal 40 may be determined and acquired based on the connected base station or the connected network.

[0045] Then, the processor 11 acquires and displays the top screen (sign-on screen) of the group app from the entrance management server 10 or the service server 60 depending on the started application (step S15), and ends the app sign-on process. After that, the process shifts to the app side, and the process depending on the started application is executed.

[0046] 5 is a flowchart showing an example of processing during fan club app sign-on executed by the user terminal 40. The processing during fan club app sign-on is executed when a fan club app available through a group account is launched in the user terminal 40 and sign-on to the fan club app is completed, and corresponds to the function of the fan club app. This processing is also executed when the fan club app in the user terminal 40 transitions from a suspended state or background to an active state. In this processing, the processor 41 of the user terminal 40 acquires user attendance information corresponding to the signed-on user from the admission management server 10, and determines whether there is a finished event for which the user's attendance is not registered by referring to the event date and time and information indicating attendance in the user attendance information (step S21).

[0047] If there is a finished event for which attendance status is not registered (step S21; Yes), the processor 41 acquires the user location information of the user at the event date and time of the event from the admission management server 10 (step S22). In step S22, a request to acquire user location information including a user ID corresponding to the user attendance status information and the event date and time is sent to the admission management server 10. Then, based on the request, the admission management server 10 extracts user location information whose user ID matches and whose sign-on date and time overlaps with, for example, the event date and time (opening time to closing time, etc.), and transmits the extracted information to the user terminal 40.

[0048] Then, the processor 41 judges whether or not the position information indicated by the acquired user position information substantially matches the position information of the event venue of the user entry / departure information (step S23). In step S23, the processor 41 acquires the position information (latitude, longitude, address, etc.) of the event venue from the entrance management server 10 or separately from the communication network 30, and judges whether or not the position information indicated by the user position information substantially matches the position information of the event venue based on whether the position information is within a predetermined range (within a predetermined distance). The user terminal 40 of this embodiment judges whether or not the user entered the event venue when the event was held based on this judgment. Note that the method of judging whether or not the user entered the event venue is not limited to this, and for example, whether or not the user entered the event venue may be judged based on whether or not the coordinates specified from the user position information were within the event venue on the map. In other words, if it can be considered that the user entered the event venue based on the user position information, it may be judged that the user entered the event venue.

[0049] In addition, if in step S22, the user location information for the date and time of the event cannot be obtained from the admission management server 10, or if the user location information for the date and time of the event is not recorded in the admission management server 10, the process of registering entry or non-entry based on the location information in steps S23 to S25 may be omitted and the process may proceed to step S26.

[0050] If the location information indicated by the user location information substantially matches the location information of the event venue of the user entry presence / absence information (step S23; Yes), the processor 41 determines that the user has entered the event venue, and requests the admission management server 10 to register the admission of the user entry presence / absence information by transmitting admission information including a user ID for identifying the user entry presence / absence information and the event date and time, etc. Then, when the admission registration notification is received, the processor 11 notifies the admission registration by displaying the event name, etc., for which admission has been registered on the display of the user terminal 40 (step S24). In step S24, for example, the processor 41 transmits a request to the admission management server 10 to register information indicating entry (entry present) to the information indicating entry presence / absence of the corresponding user entry presence / absence information. Then, based on a response to the request, it is sufficient to notify the admission registration. As a result, even if a user forgets to check in using the check-in device 50 when entering an event venue, or does not complete the entry registration procedure, if the user's location information has been registered by signing on to a fan club app or other application with a group account at the event venue, subsequent entry registration (automatic check-in) will be possible when displaying the ticket at a later date, improving user convenience.

[0051] For example, even if a user forgets to complete the admission registration procedure using the check-in device 50 when entering an event venue, the user may sign on to the group app in order to use the payment function of the group app or a point card in the event venue when making a payment at a store or the like in the event venue. In this case, the user's location information is recorded without the user's awareness just by starting the group app, and then by starting the fan club app, admission registration after the fact is automatically possible based on the user's location information, improving user convenience. In particular, when only cashless payment is available at the store in the event venue, the user is likely to use the payment function of the group app, which is particularly effective. In addition, when advertising the group app by broadcasting or display in the event venue, the user is likely to start or install the group app on the spot and sign on to the group app. In this case, the user's location information is automatically recorded without the user's awareness, and admission registration after the fact is automatically possible based on the user's location information, improving user convenience.

[0052] If the location information indicated by the user location information does not substantially match the location information of the event venue in the user entry / absence information (step S23; No), the processor 41 determines that the user did not enter the event venue, and requests the admission management server 10 to register that the user did not enter the event venue corresponding to the user entry / absence information (step S25). In step S25, for example, the processor 41 transmits a request to the admission management server 10 to register information indicating that the user has not entered (no entry) in the information indicating entry / absence in the corresponding user entry / absence information. By recording information indicating that the user has not entered in the admission management server 10, it is possible to prevent repeated determinations as to whether or not to register entry for a finished event for which entry has not been registered, and to reduce the processing load. Note that if the user location information at the event date and time is not recorded in the admission management server 10, it may be determined that the user did not enter the event venue, and information indicating that the user has not entered may be registered in the information indicating entry / absence in the corresponding user entry / absence information.

[0053] If it is determined in step S21 that there are multiple completed events for which the user has not registered attendance, then, for example, steps S22 to S25 are executed for the nearest event first, and then the process returns to step S21 and steps S22 to S25 are executed for the next nearest event. That is, if there are multiple tickets for completed events for which attendance has not been registered, a process for registering attendance or not being attended may be executed sequentially based on the position information. The process for registering may be executed in order of the furthest event date and time.

[0054] After registering the entry status of all users for the finished events with entry status unregistered in the processes of steps S22 to S25, or if there is no finished event with entry status unregistered (step S21; No), it is determined whether or not a ticket display operation by the user is detected (step S26). If a ticket display operation is not detected (step S26; No), the processor 41 executes a process according to the user's operation (step S27). In step S27, a process according to each function of the fan club app is executed, such as providing event information, live broadcasting of the event, broadcasting a recorded event, displaying a message from the support target, displaying the performance and achievements of the support target, communication between fans using the app, and online purchase of goods and tickets. After the process of step S27, the process returns to step S26, and steps S26 and S27 are repeated until an operation to end the fan club app is detected in step S27.

[0055] When the ticket display operation is detected (step S26; Yes), the processor 41 acquires user ticket information corresponding to the user ID of the user from the admission management server 10 (step S28).

[0056] In this embodiment, different information is displayed depending on the event date and time of the ticket held by the user. When the processor 41 acquires the user ticket information, it determines whether or not the user has a ticket for that day by referring to the event date and time in the user ticket information (step S29).

[0057] If there is a ticket for that day (step S29; Yes), processor 41 displays the electronic ticket for that ticket (event information, ticket information, ticket code, etc.) on the display of user terminal 40 (step S30). In this way, if the user has a ticket for that day, it is expected that the user will use that ticket to enter the event venue, so the electronic ticket is displayed. The user can enter the event venue by holding this electronic ticket over check-in device 50 at the entrance gate. Such an electronic ticket becomes proof information for the user to enter the event venue, or to prove that the user has entered the event.

[0058] At this time, the current time and the opening time of the event venue are referenced, and if the current time is before the opening time, entry is not possible, so the ticket code for entering the venue may be omitted and only the event information and ticket information may be displayed.

[0059] Thereafter, the processor 41 waits until it receives an admission registration notification transmitted based on the admission management server 10 having received the ticket ID and the like from the check-in device 50 completing the admission registration process (step S31).

[0060] When the admission registration notification is received (step S31; Yes), the processor 41 notifies the user that admission registration has been completed by, for example, displaying on the display of the user terminal 40 that admission registration has been completed (step S32), and proceeds to processing of step S27. Note that after processing of step S32, the processor 41 may proceed to processing of step S33, and execute processing corresponding to tickets other than the ticket for the day.

[0061] If there is no ticket for the day (step S29; No), processor 41 determines whether the user has a ticket for an event that has not yet started by, for example, referring to the event date and time in the user ticket information (step S33).

[0062] If there is a ticket for the pre-opening event (step S33; Yes), the processor 41 displays a list of tickets for the pre-opening event (such as a list of ticket summaries) on the display of the user terminal 40 (step S34). This allows the user to check the tickets for the pre-opening event that he or she possesses.

[0063] After the process of step S34, or if there are no tickets for the pre-start event (step S33; No), the process proceeds to step S27.

[0064] 6 is a flowchart showing an example of a location information recording process executed by the entrance management server 10 and the service server 60. The location information recording process is executed by the processors 11 and 61 of the entrance management server 10 and the service server 60 reading a program stored in the storage devices 12 and 62. Here, an example executed by the entrance management server 10 will be described. In the location information recording process, the processor 11 of the entrance management server 10 judges whether or not a sign-on request to a group account has been received from the user terminal 40 (step S101). Specifically, for example, it judges whether or not a sign-on screen to a group account has been accessed. If a sign-on request has not been received (step S101; No), the location information recording process ends.

[0065] When a sign-on request is received (step S101; Yes), the processor 11 makes an authentication request to the authentication server 20 (step S102). Specifically, for example, the processor 11 redirects the user terminal 40 to a single sign-on authentication page provided by the authentication server 20.

[0066] Thereafter, the processor 11 waits until it receives from the user terminal 40 an authentication response (such as an authentication token) indicating that the authentication in the authentication server 20 has been successful (step S103).

[0067] When an authentication response is received from the user terminal 40 indicating that authentication at the authentication server 20 was successful (step S103; Yes), the processor 11 sends, for example, a top screen (sign-on screen) of an application corresponding to the launched application to the user terminal 40 (step S104).

[0068] The processor 11 also receives current location information of the user terminal 40 from the user terminal 40 at this time, or obtains the current location information by sending a request to the user terminal 40, and records the current location information obtained from the user terminal 40 as user location information in the storage device 12 in association with the user ID and the sign-on date and time (step S105). This allows the entrance management server 10 to record the current location information of the user terminal 40 when the user terminal 40 signs on to the group account, i.e., the user's current location information. Thereafter, the location information recording process ends.

[0069] The processor 61 of the service server 60 also executes a similar location information recording process. The user location information recorded by the service server 60 is then shared with the admission management server 10 by transferring it to the admission management server 10 or making it accessible to the admission management server 10. This also records location information when the user signs on to other applications provided by the service provider using a group account, and the admission management server 10 can refer to the location information when the user signs on to other applications using a group account.

[0070] FIG. 7 is a flowchart showing an example of the admission information registration process executed by the admission management server 10. The admission information registration process is executed by the processor 11 of the admission management server 10 reading a program stored in the storage device 12. In the admission information registration process, the processor 11 of the admission management server 10 judges whether or not admission information indicating that a user has entered an event venue has been received from the check-in device 50 or the user terminal 40 (step S111). The admission information received from the check-in device 50 includes, for example, a user ID, a ticket ID, and information on the sender thereof (check-in device 50, event venue, etc.), and is information capable of identifying the user's admission status information stored in the admission management server 10. If the information on the sender is the device ID of the check-in device 50, the admission management server 10 may store information capable of identifying the event venue from the device ID. If the admission information has not been received (step S111; No), the position information recording process is terminated.

[0071] When the entry information is received (step S111; Yes), the processor 11 searches the storage device 12 for user entry / absence information corresponding to the entry information, and registers information indicating entry (entry present) in the entry / absence information of the user entry / absence information (step S112). The processor 11 then transmits an entry registration notification indicating that the entry registration has been completed to the corresponding user terminal 40 (step S113). This allows the user to know that the entry registration has been completed. Note that information regarding the user terminal 40 to which the entry registration completion notification is to be sent may be stored, for example, in association with a separate user ID.

[0072] Although not shown in the figure, when information indicating that the user has not entered is received from the user terminal 40, information indicating that the user has not entered (no entry) is registered as information indicating entry or non-entry in the user entry or non-entry information.

[0073] Next, the processor 11 refers to the information indicating the presence or absence of admission of the user ticket information of the same user stored in the storage device 12, and judges whether or not the admission bonus conditions are satisfied based on the current admission registration (step S114). The admission bonus conditions (presence or absence of admission, number of admissions, validity period, etc.) and the benefits (coupons, points, etc.) due to the satisfaction of the conditions may be determined in advance. If a subsequent admission registration is performed in step S112 based on the admission information received from the user terminal 40 in step S111, when judging whether or not the admission bonus conditions are satisfied, it is sufficient to judge whether or not the admission bonus conditions are satisfied based on the subsequent admission registration. If the admission bonus conditions are not satisfied (step S114; No), the admission information registration process is terminated.

[0074] If the admission bonus conditions are met (step S114; Yes), the processor 11 performs settings for granting a bonus to the user (step S115). In step S115, the bonus resulting from the fulfillment of the conditions is granted to the user's group account, and the user's email address or the like is notified of this. In this way, the user can be granted a bonus for registering for admission, which can encourage the user to attend the event. Thereafter, the admission information registration process is terminated.

[0075] Next, the automatic admission registration sequence (automatic check-in procedure) for a finished event for which admission has not been registered in the admission management system 100 of this embodiment will be described with reference to FIG.

[0076] As shown in FIG. 8, when a user launches a fan club app on a user terminal 40 and enters a user ID and password on the sign-on screen, the authentication server 20 performs authentication processing for the group account and transmits the authentication result (access information for the admission management server 10) and an authentication token for permitting sign-on to the admission management server 10 to the user terminal 40. Note that it is assumed here that the authentication result is successful (authentication OK). Based on the authentication result of authentication OK, the user terminal 40 transmits the user ID, authentication token, and location information at that time to the admission management server 10. This allows the admission management server 10 to record the location information at the time of sign-on.

[0077] Furthermore, when the fan club app is launched, the user terminal 40 performs an admission determination (steps S21 to S25 in FIG. 5) for a finished event for which admission status is not registered, and if the determination determines that the user has attended a finished event for which admission status is not registered, the user terminal 40 transmits an admission registration request to the admission management server 10. Upon receiving the admission registration request, the admission management server 10 performs admission registration corresponding to the request, and notifies the user terminal 40 that admission registration has been completed. In this way, by signing on to the fan club app, the user's location information at the time of signing on is automatically registered. Furthermore, by launching the fan club app, admission registration for past events for which admission status is not registered can be automatically performed based on past location information.

[0078] Next, a display example in the admission control system 100 of this embodiment will be described with reference to Figures 9 and 10. Here, a display example in which a display related to a fan club app is displayed on the display of a smartphone as the user terminal 40 will be described.

[0079] In this embodiment, an example will be described in which the event is a baseball event, the event venue is a baseball stadium, and the fan club is a baseball team fan club. The event may be a live performance, another sporting event, a fireworks display, etc. Similarly, the fan club app may be an app for supporting an artist, a sports team, or a specific event.

[0080] FIG. 9 shows a display example when signing on to the fan club app using the user terminal 40. When the user starts the fan club app on the user terminal 40 and performs a sign-on operation, a sign-on screen as shown in FIG. 9(A) is displayed. When the user enters a user ID (e.g., an email address) and a password and operates the login button, the sign-on screen (top screen) of the fan club app is displayed as shown in FIG. 9(B). On this top screen, live game reports of the supported team, game schedules, the status of the entrance bonus to the stadium that is the event venue, an icon for displaying a member's card, an icon for displaying a list of coupons, an icon for reading out ticket-related functions, and the like are displayed. It is sufficient that each function of the fan club app can be called from this top screen. Note that the top screen shown in FIG. 9(B) is an example and can be changed as desired.

[0081] When signing on to the fan club app or starting the app while signed on, if there is a ticket for a finished event for which admission is not registered, an attempt is made to register admission to that event. If the user's location information at the event date and time indicates that the user was admitted to the event venue, admission registration processing is executed by the admission management server 10. Then, as shown in FIG. 9(C), the fact that admission has been registered and the name of the event for which admission has been registered are displayed on the user terminal 40, and admission registration is notified. When the "Return to TOP" icon is selected on this screen, the screen transitions to the top screen of FIG. 9(B).

[0082] Furthermore, when an operation is performed to read out a ticket-related function on the top screen of the fan club app shown in Fig. 9(B), a ticket-related screen is displayed, for example, as shown in Fig. 9(D). This ticket-related screen displays items (buttons, icons) such as "Purchase ticket", "Display ticket", "Import ticket", and "Transfer ticket". Items other than these may also be included.

[0083] In Fig. 9(D), when "Buy tickets" is selected, a screen is displayed for purchasing tickets by selecting, for example, the event name, date and time, type of seating, number of tickets, etc. When "Import tickets" is selected, a screen is displayed for importing paper ticket information into the fan club app, for example by inputting the paper ticket number, reading the code printed on the paper ticket, or photographing the paper ticket. When "Transfer tickets" is selected, a screen is displayed for transferring a ticket by specifying, for example, a user name, etc.

[0084] Furthermore, when "Show tickets" is selected in Fig. 9(D), if there are tickets for the day, an electronic ticket including the ticket information for the day and the ticket code is displayed as shown in Fig. 10(A). If there are no tickets for the day, but there are tickets for a pre-event, a list of ticket summaries for the pre-event is displayed as shown in Fig. 10(B). When a ticket is selected in the ticket list, the ticket details and the electronic ticket may be displayed.

[0085] If the conditions in Figures 10(A) and (B) overlap, the two displays may be displayed simultaneously or sequentially. Alternatively, the two displays may be displayed overlapping each other. In this way, if there are tickets for the day and tickets for the event before the event, the display and processing can be performed according to the possession status.

[0086] In addition, if there is a ticket for an event that has not yet started, a summary list of the ticket for the event that has not yet started is displayed, as shown in Figure 10 (B), but it is also possible to display the ticket details and electronic ticket for the event that has not yet started.

[0087] (Modification) The present invention is not limited to the above-described embodiment, and various modifications and applications are possible. For example, some of the above-described embodiment may be omitted or replaced, or any configuration may be added.

[0088] In the above embodiment, the user terminal 40 transmits its location information to the entrance management server 10 or the service server 60 at the time of single sign-on to the group account, and the server records the user location information shown in FIG. 3(C). This is not limiting, and the user location information at the time of single sign-on to the group account may be stored in the user terminal 40. In this case, the user location information is stored in a common area accessible from a plurality of group apps in the storage device 42 of the user terminal 40, so that the user location information can be referenced from the fan club app. The user location information thus stored in the user terminal 40 may be periodically transmitted to the entrance management server 10, so that it is stored synchronously on the server side. The user ticket information shown in FIG. 3(A) and the user entrance / non-entry information shown in FIG. 3(B) may also be stored in the user terminal 40 or synchronously with the entrance management server 10. In this way, the user terminal 40 can refer to the user ticket information, the user entrance / non-entry information, and the user location information without accessing the entrance management server 10 each time, and can execute processing based on the information.

[0089] In the above embodiment, when a ticket for a finished event for which entry is not registered is found when signing on to the fan club app or when starting the app while signed on, entry registration for the event is attempted. This is not limited to the above, and a predetermined function of the fan club app may be attempted when starting the app. For example, entry registration for a finished event for which entry is not registered may be attempted when a ticket display operation is performed while the fan club app is running. In this case, when a ticket for the day or a ticket for an event that has not yet been held is found, priority may be given to the display of the ticket (display in FIG. 10), or priority may be given to the entry registration process or the notification of the completion of entry registration (FIG. 9(C)). In addition, two or more of the displays in FIG. 10 and FIG. 9(C) may be displayed simultaneously or sequentially. Alternatively, two or more of the displays may be displayed in a superimposed manner. In this way, automatic check-in for a past event for which entry is not registered can be performed when a ticket is called up, improving user convenience.

[0090] Also, the user location information may be recorded not only when signing on to the group app, but also when using or starting the group app. For example, the user location information may be recorded in the service server 60 when the payment function or point card of the group app is used within the event venue. By doing so, the user location information is more likely to be recorded, making it easier to register admission after the fact based on the location information. This is particularly effective when only cashless payment is available at the convenience store within the event venue, since there is a high possibility that the user will use the payment function of the group app.

[0091] In the above embodiment, the user terminal 40 obtains user entry information and user location information from the admission management server 10, and determines whether the location information indicated by the user location information at the time of the event that has been completed and for which entry is not registered, approximately matches the location information of the event venue of the event that has been completed, thereby determining whether the user entered the event venue when the event was held for the event that has been completed and for which entry is not registered (step S23 in FIG. 5, etc.). This is not limited to the above, and the admission management server 10 may determine whether the user entered the event venue when the event was held for the event that has been completed and for which entry is not registered, in response to a request from the user terminal 40. For example, the admission management server 10 may execute processes equivalent to steps S23 to S25 in response to an inquiry from the user terminal 40, and return the determination result.

[0092] The user terminal 40 can be realized by using a normal computer, not a dedicated device. For example, the user terminal 40 that executes the above-mentioned processes may be configured by installing a program for executing the above-mentioned functions in a computer included in the terminal device via a communication network.

[0093] The entrance management server 10, the authentication server 20, and the service server 60 can be realized by using a normal computer, not by a dedicated device. For example, the entrance management server 10, the authentication server 20, and the service server 60 that execute the above-mentioned processes may be configured by installing a program for executing the above-mentioned functions on a computer from a recording medium that stores the program. Also, one entrance management server 10, one authentication server 20, and one service server 60 may be configured by multiple computers operating in cooperation with each other.

[0094] Furthermore, the method for supplying the program to the computer is arbitrary. For example, the program may be supplied via a storage medium, a communication line, a communication network, a communication system, etc. For example, a non-transitory computer-readable recording medium storing the program for executing the above-mentioned functions may be distributed.

[0095] Furthermore, in the case where an OS (Operating System) provides some of the above-mentioned functions, the functions other than those provided by the OS may be provided by a program.

[0096] The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit the present invention. The flow charts, sequences, elements included in the embodiments, and their arrangements, materials, conditions, shapes, sizes, etc. are not limited to those illustrated, and can be changed as appropriate. In addition, configurations shown in different embodiments can be partially substituted or combined with each other.

[0097] (Invention realized by this embodiment) As described above, the present embodiment realizes the following inventions.

[0098] (Appendix 1) A terminal device capable of operating a plurality of applications including an admission registration application, The terminal device Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the terminal device is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying a location of the terminal device when the authentication by the single sign-on was performed during a period in which the extracted event was held; if the identified location and the identified venue are within a predetermined range, attempting to register that the user has attended the extracted event; Terminal device.

[0099] (Appendix 2) if the identified location and the identified venue are not within a predetermined range, attempting to register that the user has not attended the extracted event; 2. A terminal device as described in claim 1.

[0100] (Appendix 3) If the extracted event is being held, displaying on a screen authentication information for the user to enter the event or for authenticating that the user has entered the event. 3. A terminal device according to claim 1 or 2.

[0101] (Appendix 4) When authenticating the user, the location of the terminal device is stored in the terminal device in association with the date and time of the authentication, or the location information is transmitted to a server for recording location information. 4. A terminal device according to any one of appendix 1 to 3.

[0102] (Appendix 5) When extracting an event for which it is not registered whether the user has attended, an event currently being held is extracted, or if there is no event currently being held, the most recent event that has already finished is extracted. 5. A terminal device according to any one of appendix 1 to 4.

[0103] (Appendix 6) When extracting an event for which it is not registered whether the user has attended, extracting recent events that are currently being held and have already ended. A terminal device according to any one of claims 1 to 4.

[0104] (Appendix 7) An admission registration method executed by a terminal device capable of running a plurality of applications including an admission registration application, comprising: The terminal device Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the terminal device is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying a location of the terminal device when the authentication by the single sign-on was performed during a period in which the extracted event was held; if the identified location and the identified venue are within a predetermined range, attempting to register that the user has attended the extracted event; How to register for admission.

[0105] (Appendix 8) A computer capable of running multiple applications, including the admission registration application, Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the computer is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying the location of the computer when the single sign-on authentication was performed during the period in which the extracted event was held; if the identified location and the identified venue are within a predetermined range, attempting to register that the user has attended the extracted event; A program that functions as a terminal device. [Industrial Applicability]

[0106] According to the present invention, it is possible to provide a terminal device, an admission registration method, and a program that enable a user to make admission registration after the fact even if the user did not make admission registration at the time of entry. [Explanation of symbols]

[0107] 10. Admission Management Server 20 Authentication Server 30 Communication Network 40 User terminal 50 Check-in device 60 Service Server 11, 21, 41, 61 processors 12, 22, 42, 62 storage device 13, 23, 43, 63 Communication Interface 14, 24, 44, 64 input devices 15, 25, 45, 65 Output Devices 100 Admissions Management System

Claims

1. A terminal device capable of operating a plurality of applications including an admission registration application, The terminal device Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the terminal device is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying a location of the terminal device when the authentication by the single sign-on was performed during a period in which the extracted event was held; if the identified location and the identified venue are within a predetermined range, attempting to register that the user has attended the extracted event; Terminal device.

2. if the identified location and the identified venue are not within a predetermined range, attempting to register that the user has not attended the extracted event; The terminal device according to claim 1 .

3. If the extracted event is being held, displaying on a screen authentication information for the user to enter the event or for authenticating that the user has entered the event. The terminal device according to claim 1 .

4. When authenticating the user, the location of the terminal device is stored in the terminal device in association with the date and time of the authentication, or the location information is transmitted to a server for recording location information. The terminal device according to claim 1 .

5. When extracting an event for which it is not registered whether the user has attended, an event currently being held is extracted, or if there is no event currently being held, the most recent event that has already finished is extracted. The terminal device according to any one of claims 1 to 4.

6. When extracting an event for which it is not registered whether the user has attended, extracting recent events that are currently being held and have already ended. The terminal device according to any one of claims 1 to 4.

7. An admission registration method executed by a terminal device capable of running a plurality of applications including an admission registration application, comprising: The terminal device Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the terminal device is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying a location of the terminal device when the authentication by the single sign-on was performed during a period in which the extracted event was held; if the identified location and the identified venue are within a predetermined range, attempting to register that the user has attended the extracted event; How to register for admission.

8. A computer capable of running multiple applications, including the admission registration application, Authentication is performed by single sign-on in at least one of the plurality of apps, By operating the admission registration application, authentication of a user who uses the computer is performed; If the authentication is successful, extracting an event in which it is not registered whether the user has entered or not; If the extracted event has ended, identifying the venue where the extracted event was held; Identifying the location of the computer when the single sign-on authentication was performed during the period in which the extracted event was held; if the identified location and the identified venue are within a predetermined range, attempting to register that the user has attended the extracted event; A program that functions as a terminal device.

Images