Electronic ticket management system, electronic ticket management method, attendee terminal, server, and program

Abstract

To provide an electronic ticket management system that can successfully guide a visitor to a target position.SOLUTION: An output unit 401 of a visitor terminal 40 outputs ticket information related to a ticket possessed by a user. An acquisition unit 501 of a gate terminal 50 acquires the ticket information output from the visitor terminal 40. A provision unit 101 of a server 10 provides, to the visitor terminal 40, route information for a route from a gate position where the gate terminal 50 that has obtained the ticket information is positioned to the target position corresponding to the ticket information. A presentation unit 402 of the visitor terminal 40 presents the route from the gate position to the target position on the basis of the route information provided by the server 10.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an electronic ticket management system, an electronic ticket management method, an attendee terminal, a server, and a program. [Background technology]

[0002] An electronic ticket system has been proposed in which ticket data including ticket information and a control program is generated by a ticket issuing device, the generated ticket data is transmitted from the ticket issuing device to a mobile information terminal, and a map to the location of use corresponding to the ticket information is displayed based on the location data contained in the ticket data and the location data of the mobile information terminal obtained by a GPS receiver (positioning device) installed in the mobile information terminal (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-025686 Summary of the Invention [Problem to be solved by the invention]

[0004] At venues (baseball stadiums, stadiums, amphitheaters, etc.) with multiple gates in various locations, it can be difficult for visitors to know which route to take to reach their destination (e.g., their seats) after entering the venue. Furthermore, venues may have multiple floors or may have poor radio signal reception, making it difficult to guide visitors to their seats using a positioning device installed in a mobile information terminal. Thus, it is desirable to guide users to their seats conveniently after entering the venue using an electronic ticket.

[0005] The present invention has been made in view of the above circumstances, and aims to provide an electronic ticket management system and the like that can suitably guide visitors to their target locations. [Means for solving the problem]

[0006] A representative embodiment of the present invention will be briefly described below. The electronic ticket management system according to the present invention is as follows: An electronic ticket management system including an attendee terminal and a gate terminal, the visitor terminal includes an output unit that outputs ticket information related to the ticket; the gate terminal includes an acquisition unit that acquires ticket information output from the visitor terminal; The electronic ticket management system includes a provision unit that provides route information to the visitor terminal, the route information being information based on a route from a gate location where the gate terminal that acquired the ticket information is located to a target location associated with the ticket information, The visitor terminal includes a presentation unit that presents the route information provided by the provision unit. [Effects of the Invention]

[0007] According to the present invention, visitors can be suitably guided to their target positions. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a block diagram showing the configuration of an electronic ticket management system according to an embodiment of the present invention; [Figure 2] 1 is a functional block diagram of an electronic ticket management system according to an embodiment of the present invention. [Figure 3] FIG. 10 is a sequence diagram showing an entrance sequence at the entrance gate of the venue. [Figure 4] 1 is a diagram illustrating an example of the hardware configuration of an information processing device that constitutes an electronic ticket management system according to an embodiment of the present invention. [Figure 5] 10 is a flowchart illustrating an example of a process performed while a ticket application is running. [Figure 6] 10 is a flowchart showing an example of a process performed when ticket information is received. [Figure 7] 10A to 10D are diagrams showing an example of information stored in a server. [Figure 8] FIG. 1 is a diagram showing an example of an overall map of a venue. [Figure 9] 10A to 10D are diagrams showing examples of displays on a visitor terminal. DETAILED DESCRIPTION OF THE INVENTION

[0009] An electronic ticket management system 100 according to an embodiment of the present invention will be described below with reference to the drawings. Note that the same or corresponding parts in the drawings are designated by the same reference numerals.

[0010] FIG. 1 is a block diagram showing the configuration of an electronic ticket management system 100 according to this embodiment. The electronic ticket management system 100 is a system that manages whether or not to permit entry to an event (event venue) based on an electronic ticket corresponding to an attendee terminal 40 (e.g., an electronic ticket owned by a user). The electronic ticket management system 100 also outputs information about a route to a predetermined location associated with the electronic ticket (e.g., the seat location of the user of the attendee terminal 40) to the attendee terminal 40 located at the event venue. A user entering the event venue is also referred to as an attendee. The electronic ticket management system 100 according to this embodiment includes a server 10, an attendee terminal 40, and a gate terminal 50, all of which are connected via a communication network 30 such as the Internet or a mobile communication network. The server 10 and the attendee terminal 40 transmit and receive information via the communication network 30. The server 10 and the gate terminal 50 also transmit and receive information via the communication network 30.

[0011] The server 10 manages event ticket information electronically owned by users and users' admission to event venues based on the ticket information. Based on the ticket information received from the gate terminal 50, the server 10 performs ticket authentication by determining whether the ticket corresponding to the ticket information is valid or not, and transmits the authentication result to the gate terminal 50. This allows the gate terminal 50 to confirm the validity of the presented electronic ticket.

[0012] The server 10 also provides a ticket app, which is an application that has functions such as purchasing tickets for an event and displaying the tickets (electronic tickets) at the event venue. The attendee terminal 40 can access the server 10 via the ticket app. The server 10 provides services according to each function of the ticket app.

[0013] The ticket app may have functions such as providing event information related to the target of the user's support, broadcasting live events, broadcasting recorded events, displaying messages from the target of the user's support, displaying the target's performance and achievements, allowing fans to interact with each other using the app, and purchasing merchandise online.The ticket app also outputs information about the route to the seat location for the event the user is attending.

[0014] The server 10 is a high-performance information processing device that has multiple storage devices and multiple control units such as CPUs. The server 10 may be configured by a communicable information processing device such as a personal computer (PC) or a workstation. The server 10 may be a dedicated device. The server 10 may also be configured by multiple information processing devices.

[0015] The visitor terminal 40 is an information processing device such as a smartphone or tablet that can be carried by the user. A ticket app provided by the server 10 can be installed on the visitor terminal 40. The visitor terminal 40 displays electronic tickets and ticket-related information on the display screen based on user operations on the installed ticket app. The electronic ticket includes, for example, information related to the event date and time and seat location, a ticket code consisting of a two-dimensional code and a barcode, etc., that is specific to the electronic ticket. In a narrow sense, the ticket code displayed on the visitor terminal 40 is also called the electronic ticket.

[0016] Furthermore, the visitor terminal 40 of this embodiment is capable of displaying route information from the entrance gate to the user's seat at the event venue when the user enters the event venue using an electronic ticket via the gate terminal 50. The process and operation for displaying the route information will be described in detail later.

[0017] The gate terminal 50 is a terminal device that includes at least a code reader for reading ticket codes, a communication function for communicating with the server 10, and output means (display screen, speaker, etc.) for outputting authentication results from the server 10. The gate terminal 50 reads the ticket code printed on an electronic ticket or a paper ticket, and transmits a ticket authentication request corresponding to the read ticket code to the server 10 to perform ticket authentication.

[0018] Specifically, gate terminal 50 reads the ticket code printed on the electronic ticket displayed on attendee terminal 40 and presented by the attendee, or on the paper ticket, and transmits a ticket authentication request corresponding to the read ticket code to server 10. Server 10 performs authentication processing based on the information contained in the received ticket authentication request, and transmits the authentication result to gate terminal 50. Upon receiving the authentication result from server 10, gate terminal 50 displays the authentication result on a display screen and outputs a sound corresponding to the authentication result.

[0019] The gate terminal 50 may be a portable terminal carried by staff at the entrance gate, or may be a stationary gate device (automatic ticket gate) equipped with an openable and closable door or bar. If the gate terminal 50 is a portable terminal, the staff may permit or deny entry of the visitor to the venue depending on the authentication result output from the gate terminal 50. If the gate terminal 50 is a stationary gate device, the gate terminal 50 may permit or deny entry of the visitor to the venue by opening or closing a door or bar depending on the authentication result.

[0020] Although two visitor terminals 40 and two gate terminals 50 are shown in FIG. 1, any number of visitor terminals 40 and gate terminals 50 may be used. A predetermined number of gate terminals 50 may be provided at each entrance gate of the event venue. Multiple gate terminals 50 may be provided within the event venue.

[0021] Figure 2 is a functional block diagram of an electronic ticket management system 100 according to this embodiment. As shown in Figure 2, the electronic ticket management system 100 is made up of a server 10, a visitor terminal 40, and a gate terminal 50. The server 10 comprises a providing unit 101. The visitor terminal 40 comprises an output unit 401 and a presentation unit 402. The gate terminal 50 comprises an acquiring unit 501.

[0022] When the ticket app runs on the visitor terminal 40, the output unit 401 of the visitor terminal 40 outputs ticket information related to the ticket owned by the user (visitor). Note that the ticket owned by the user here is an example of a ticket corresponding to the visitor terminal 40. For example, the output unit 401 displays an electronic ticket (ticket code) on a screen (an output device such as a display of the visitor terminal 40). Note that the output unit 401 may also output the ticket information via wireless communication.

[0023] The acquisition unit 501 of the gate terminal 50 acquires the ticket information output from the visitor terminal 40. For example, the acquisition unit 501 reads the electronic ticket output by the output unit 401 to acquire ticket information corresponding to the electronic ticket. The gate terminal 50 transmits a ticket authentication request to the server 10 according to the ticket information acquired by the acquisition unit 501. Note that the acquisition unit 501 may also acquire the ticket information from the visitor terminal 40 via wireless communication.

[0024] The providing unit 101 of the server 10 provides the visitor terminal 40 with route information (route-based information) relating to the route from the gate location where the gate terminal 50 that acquired the ticket information is located to the target location associated with the ticket information. For example, the providing unit 101 identifies the gate location of the gate terminal 50 that sent the ticket authentication request according to the ticket information, and identifies the target location (seat location) associated with the ticket information. The providing unit 101 then generates a route (line) connecting the gate location and the target location based on the map information, route information, etc. of the venue, and transmits the route information associated with the generated route to the visitor terminal 40.

[0025] The presentation unit 402 of the visitor terminal 40 presents the route from the gate position to the target position based on the route information provided by the server 10. For example, the output unit 401 displays on the screen the route connecting the entrance gate to the seat.

[0026] FIG. 3 is a sequence diagram showing the admission sequence in the electronic ticket management system 100. As shown in FIG. 3, when an attendee holds the electronic ticket displayed on the attendee terminal 40 over the code reader of the gate terminal 50 at the admission gate, the gate terminal 50 reads the ticket ID, which is the ticket identification information, and the user ID, which is the user identification information, contained in the electronic ticket. In this case, the ticket ID is the ticket information. The gate terminal 50 then transmits a ticket authentication request to the server 10, including the read ticket ID, user ID, and gate ID, which is its own identification information. Upon receiving the ticket authentication request including the ticket ID, user ID, and gate ID, the server 10 performs ticket authentication processing by checking the ticket identified by the ticket ID and the ticket owned by the user identified by the user ID, and transmits the authentication result to the gate terminal 50. Here, it is assumed that the authentication result is successful (admission OK). When the gate terminal 50 receives the authentication result indicating that the user is allowed to enter the event venue, it displays the authentication result on a display device installed on the gate terminal 50 or on the entrance gate, and performs control such as opening the gate door to allow the user to enter the event venue. Based on the authentication result displayed on the display device, staff may guide the user to the event venue. Furthermore, if the server 10 successfully authenticates the ticket, it generates a route connecting the gate location of the entrance gate identified from the gate ID and the seat location corresponding to the ticket ID, and transmits route information corresponding to the generated route to the attendee terminal 40.

[0027] According to the electronic ticket management system 100 of this embodiment, when an attendee uses ticket information (electronic ticket) output by the attendee terminal 40 to enter an event venue via the gate terminal 50, route information is generated based on the gate location identified by the gate terminal 50 and the seat location identified by the ticket information, and route information from the gate location to the seat location can be provided to the attendee terminal 40. In other words, by entering the event venue using an electronic ticket, an attendee can automatically obtain route information from the entrance gate to their seat location. As a result, even if the attendee terminal 40 cannot identify their current location due to poor signal reception from the positioning device, for example, route information within the venue can be reliably provided to the attendee terminal 40, allowing the attendee to be guided to their preferred seat location.

[0028] 4 is a diagram showing an example of the hardware configuration of an information processing device that constitutes the server 10 and the visitor terminal 40. The server 10 has a processor 11 such as a CPU (Central Processing Unit) or GPU (Graphical Processing Unit), a storage device 12 such as memory, HDD and / or 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, touch panel, mouse and / or microphone. The output device 15 is, for example, a display and / or speaker.

[0029] Similarly, visitor terminal 40 has a processor 41, a storage device 42, a communication interface 43, an input device 44, and an output device 45. Note that unnecessary components in server 10 and visitor terminal 40 may be omitted as appropriate, or other components may be added. Note that gate terminal 50 also has the hardware configuration of an information processing device shown in FIG.

[0030] Next, we will explain the operation of the electronic ticket management system 100. Figure 5 is a flowchart showing an example of the ticket application startup process executed by the visitor terminal 40. The ticket application startup process is executed, for example, by the processor 41 of the visitor terminal 40 reading a program stored in the storage device 42.

[0031] The ticket app running process is executed when the ticket app is running on the visitor terminal 40. In this process, the processor 41 of the visitor terminal 40 determines whether or not a ticket display operation by the user of the visitor terminal 40 has been detected (step S11). The ticket display operation may be any predetermined operation on the ticket app screen.

[0032] If no ticket display operation is detected (step S11; No), processor 41 executes processing according to the user operation (step S12). In step S12, processing is executed to search for, purchase, or transfer a ticket, or to import a paper ticket into the ticket application, according to the user operation in the ticket application. After the processing in step S12, the process returns to step S11, and steps S11 and S12 are repeated, for example, until an operation to close the ticket application is detected in step S12.

[0033] If a ticket display operation is detected (step S11; Yes), the processor 41 acquires user ticket information corresponding to the user ID of the user of the visitor terminal 40 from the server 10 (step S13).

[0034] FIG. 7(A) shows an example of user ticket information stored in the storage device 12 of the server 10. The user ticket information is information indicating ticket information owned by a specific user. For example, as shown in FIG. 7(A), the user ticket information is information that associates a user ID that uniquely identifies a user, a ticket ID that uniquely identifies an event ticket, the event date and time (event date, event period, event time, etc.), the event venue (venue name, location information, etc.) of the event, and a seat ID that identifies a seat location in the event venue (seat number, seat type, block, row, aisle, etc.). If a user owns multiple tickets, multiple ticket IDs may be linked to the user ID. When a user purchases a ticket electronically on a website, application, etc. provided by the server 10, 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. The user ticket information may also include other information. The ticket ID linked to the user ID is not limited to the ticket purchased by the user, but may be the ID of a ticket that has been transferred to the user in a predetermined manner.

[0035] 5, in this embodiment, when a ticket display operation is detected, the attendee terminal 40 (ticket app) displays different information depending on the event date and time of the ticket owned by the user. When the processor 41 acquires the user ticket information, it determines whether or not the user owns a ticket for that day by, for example, referring to the event date and time in the user ticket information (step S14).

[0036] If a ticket for the day is available (step S14; Yes), processor 41 displays the electronic ticket (event information, seat information, ticket code, etc.) for that ticket on the screen (display) of attendee terminal 40 (step S15). In step S15, the gate terminal 50 is also caused to read the electronic ticket displayed on attendee terminal 40. In this way, if the user has a ticket for the day, it is expected that they 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 the gate terminal 50 at the entrance gate.

[0037] At this time, the current time and the opening time (entry 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 seat information may be displayed. Here, the opening time may be included in the user ticket information shown in FIG. 7(A), or may be calculated based on the event opening date and time. The opening time may be the same as the event opening date and time.

[0038] Thereafter, the processor 41 waits until it receives route information generated by the server 10 that has received the ticket authentication request including the ticket ID and the like from the gate terminal 50 (step S16). At this time, if an operation to end the display of the electronic ticket is received, the display of the electronic ticket may be ended.

[0039] When route information is received from the server 10 (step S16; Yes), the processor 41 presents the visitor with a route from the entrance gate to their seat location, for example by displaying a route image corresponding to the route information on the screen of the visitor terminal 40 (step S17).

[0040] After the process of step S17 is completed, the process proceeds to step S12. After the process of step S17, the process may proceed to step S18, where a process corresponding to a ticket other than a same-day ticket is executed.

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

[0042] If there are tickets for the pre-opening event (step S18; Yes), the processor 41 displays a list of tickets for the pre-opening event (such as a list of ticket summaries) on the screen of the attendee terminal 40 (step S19). This allows the user to check the tickets they own for the pre-opening event.

[0043] After the processing of step S19, or if there are no tickets for the upcoming event (step S18; No), ticket information for nearby events that are being held on the same day or in the near future near the current location of the visitor terminal 40 is obtained from the server 10 and displayed on the screen of the visitor terminal 40 (step S20). The ticket information may include the details of the event, the date and time of the event, the venue, a link to purchase tickets, etc. This allows the event to be promoted to users and encourages them to purchase tickets. If there are tickets for the upcoming event, a list of tickets for the upcoming event and ticket information for nearby events may be displayed. Alternatively, the list of tickets for the upcoming event and ticket information for nearby events may be displayed sequentially.

[0044] In the processing of step S20, for example, the current location information of the visitor terminal 40 is obtained from a positioning device such as a GPS (Global Positioning System) equipped in the visitor terminal 40, and a request for ticket information for nearby events, which are events held in locations around (within a predetermined distance from) the obtained current location information, is sent to the server 10. Then, upon receiving the request, the server 10 searches for events from a database or the like that stores event information based on the current location information, current time, etc., and sends ticket information according to the search results to the visitor terminal 40.

[0045] 6 is a flowchart showing an example of the ticket information reception process executed by the server 10. The ticket information reception process is executed by the processor 11 of the server 10 reading a program stored in the storage device 12. In the ticket information reception process, the processor 11 of the server 10 determines whether or not a ticket authentication request has been received from the gate terminal 50 (step S101). If ticket information has not been received (step S101; No), the ticket information reception process ends. Alternatively, the processor 11 may proceed to step S101.

[0046] When a ticket authentication request is received (step S101; Yes), the processor 11 performs authentication processing of the received ticket information (step S102). In step S102, for example, the processor 11 acquires user ticket information corresponding to the user ID included in the ticket authentication request, and determines whether or not the user holds a ticket with the ticket ID included in the ticket authentication request. If the user holds a ticket with the ticket ID included in the ticket authentication request, the authentication is successful; if the user does not hold a ticket with the ticket ID included in the ticket authentication request, the authentication is unsuccessful.

[0047] Next, the processor 11 determines whether the authentication of the ticket information has been successful (step S103). If the ticket authentication has been successful (step S103; Yes), the processor 11 notifies the gate terminal 50 that sent the ticket authentication request that the ticket authentication has been successful (step S104).

[0048] Then, processor 11 acquires gate position information of gate terminal 50 that sent the ticket authentication request based on the gate ID included in the ticket authentication request (step S105). In the processing of step S105, processor 11 acquires position information corresponding to the gate ID based on the gate ID included in the ticket authentication request, for example, by referring to gate position information stored in storage device 12. In this way, processor 11 identifies the gate position, which is the entrance position of the attendee to the venue.

[0049] 7(B) shows an example of gate position information stored in storage device 12 of server 10. As shown in FIG. 7(B), for example, the gate position information is information that associates a gate ID that uniquely identifies gate terminal 50, location information (latitude and longitude information, etc.) of gate terminal 50, connection route information that is information on routes connecting to gate terminal 50, and adjacent gate information that is information on entrance gates adjacent to the entrance gate where gate terminal 50 is installed. The connection route information and adjacent gate information in the gate position information are referenced when generating the route information. Note that the gate position information may also include other information.

[0050] Processor 11 also acquires seat position information based on the ticket ID (step S106). In the processing of step S106, processor 11 acquires a seat ID of the user ticket information based on, for example, the ticket ID included in the ticket authentication request, and acquires seat position information corresponding to the ticket ID by referring to the seat position information stored in storage device 12 based on the seat ID. In this way, processor 11 identifies the seat position that is the target position of the entrant.

[0051] FIG. 7(C) shows an example of seat position information stored in the storage device 12 of the server 10. As shown in FIG. 7(C), the seat position information is information that associates a seat ID that uniquely identifies a seat in an event venue, the position information of the seat (such as latitude and longitude information), and connecting route information that is information about a route connecting the seat (or the closest route if the seat is not adjacent to the route). The connecting route information in the seat position information is referenced when generating route information. Note that the seat position information may also include other information. The event venue may be identified by the seat ID, or the seat position information may separately include identification information for the event venue.

[0052] Next, processor 11 executes a route generation process to generate route information from the position of gate terminal 50 to the seat position (step S107).

[0053] In the process of step S107, processor 11 searches for a route (e.g., the shortest route, the optimal route taking congestion into consideration, etc.) connecting the gate position information acquired in step S105 and the seat position information acquired in step S106 based on the route data of the venue. Then, processor 11 overlays the searched route on the venue map to generate route information to be provided to visitors.

[0054] For example, in this embodiment, the server 10 stores information such as the location and length of routes (passageways, intersections, stairs, etc.) in each venue as venue route data, and searches for routes based on the venue route data.

[0055] FIG. 7(D) shows an example of venue route data stored in storage device 12 of server 10. In this embodiment, venue route data is route network information including nodes (points) that indicate characteristic points of routes (intersections, corners, dead ends, etc.) on a map of the venue, and links (lines) that indicate routes connecting the nodes. As shown in FIG. 7(D), for example, venue route data is information that associates a route ID that uniquely identifies a route, a route type that indicates the type of route (e.g., passageway, intersection, staircase, corner, entrance, dead end, etc.), location information of the route (e.g., start position, end position, etc. for a passageway), and additional information that indicates the length of the route, width of the passageway, etc. Storage device 12 of server 10 stores this venue route data for each venue. Note that the venue route data may also include other information.

[0056] A route ID is stored in the connection route information in the gate position information shown in Fig. 7(B) and the seat position information shown in Fig. 7(C). This makes it possible to identify a route connecting to gate terminal 50 or a seat based on the gate position information and seat position information.

[0057] FIG. 8 shows an example of an overall map of a baseball stadium as an event venue. Note that FIG. 8 shows the seating area on the third base side of the baseball stadium as an example. As shown in FIG. 8, the baseball stadium is equipped with multiple entrance gates (gates g1 to g4 in FIG. 8), entrances to the spectator seats (entrances e1 to e4 in FIG. 8), passages (passage p211 in FIG. 8 as an example), stairs (stairs p221 in FIG. 8 as an example), intersection n001, etc. It is sufficient to store venue route data such as that shown in FIG. 7(D) for each route and feature point in these venues.

[0058] The overall map may include other information, for example, restrooms and shops. The server 10 may store location information of the restrooms and shops as facility information.

[0059] In this embodiment, in step S107, processor 11 selects the route indicated in the connection route information for gate terminal 50 included in the gate position information acquired in step S105 as the first route (starting point), and the route indicated in the connection route information for gate terminal 50 included in the gate position information acquired in step S106 as the last route (ending point), searches for a route connecting these (e.g., the shortest route) based on the venue route data, and generates a series of routes by connecting the searched routes.The generated series of routes is then superimposed on the venue map to generate route information to be provided to visitors.

[0060] The venue map (image data) may be stored in advance in the storage device 12 of the server 10. In step S107, a route map may be generated by superimposing the generated series of routes on a map of the entire venue as shown in Fig. 8 or a map of a portion of the venue (such as a map of the area around the seats). The venue map and the route information generated based on the venue map may be a 2D image, or may be a 3D image if the venue has a hierarchical structure.

[0061] Furthermore, the method of generating the route in step S107 is just one example, and any method may be used to generate route information that indicates at least the route from the gate location where the gate terminal 50 used by the visitor to enter is located to the target location (seat location) according to the ticket information. For example, in generating the route information, a route generation algorithm based on road node and link information in a car navigation system or the like may be used.

[0062] In step S107, the route search is not limited to searching for the shortest route, but different route information may be provided to visitors depending on the route length, aisle width, and route congestion status included in the venue route data. For example, if the aisle width is narrow, a route that avoids that aisle may be selected preferentially. Furthermore, after providing route information to one visitor, route information may be provided to other visitors for a predetermined period of time so that other visitors avoid the route corresponding to the route information provided to the one visitor. In this way, congestion and jams on specific routes within the venue can be prevented.

[0063] In this case, after generating route information for one visitor in step S107, the generated route information may be stored for a predetermined period of time, and routes for other visitors may be searched for and generated during the predetermined period so as to avoid routes (corridors, entrances, stairs, etc.) included in the route information.

[0064] Furthermore, after route information for a particular visitor is provided, while the route information is displayed on the visitor terminal 40, it is presumed that the visitor is viewing the route information and traveling along the presented route. When the visitor closes the route information displayed on the visitor terminal 40, it is presumed that the visitor has arrived at their seat. Therefore, when providing route information to other visitors while the route information provided to one visitor is being displayed, route information that avoids the route presented to the one visitor may be provided to the other visitors. This also helps prevent congestion and jams on specific routes within the venue.

[0065] In this case, after generating route information for one visitor in step S107, the generated route information may be stored, and routes for other visitors may be searched for and generated so as to avoid the routes (passages, entrances, stairs, etc.) included in the route information. Then, for example, visitor terminal 40 may monitor the display status of the route information displayed on its screen, and if the route information is closed, send a message to server 10. Then, when server 10 receives a message that the route information provided to visitor terminal 40 of one visitor has been closed, it may make the route (passages, entrances, stairs, etc.) included in the route information available to other visitors. In other words, the predetermined period may be the period until the route information provided to one visitor is closed.

[0066] Furthermore, the route search method may differ depending on the entrance gate (gate terminal 50) through which the visitor entered the venue. For example, the route search method may differ depending on whether the entrance gate through which the visitor entered is the closest to the seat or not. For example, if the entrance gate through which the visitor entered is not the closest to the seat, a route to an adjacent gate that is closer to the seat than the entrance gate may first be set based on the adjacent gate information included in the gate position information, and then a route from the adjacent gate to the seat position may be searched for. In this way, the visitor can be guided to their seat in an optimal manner even if they enter the venue from an entrance gate other than the closest to the seat.

[0067] The processor 11 then transmits the route information generated in step S107 to the corresponding visitor terminal 40 (step S108), and terminates the ticket information reception process. Information about the visitor terminal 40 to which the route information is to be sent can be identified based on the user ID included in the ticket authentication request. For example, the information about the visitor terminal 40 can be stored separately in association with the user ID.

[0068] Furthermore, if ticket authentication fails in the authentication process of step S102 (step S103; No), processor 11 notifies gate terminal 50 that sent the ticket authentication request that ticket authentication has failed (step S109), and terminates the process when ticket information is received.

[0069] By executing the above-described ticket information reception process, the server 10 can generate route information from the location of the gate terminal 50 through which the attendee entered to the seat location, and provide the route information to the attendee terminal 40. This allows attendees to be guided to their seats in an optimal manner.

[0070] Next, a description will be given of a display example in the electronic ticket management system 100 of this embodiment. Here, a display example will be described in which a display related to a ticket app is displayed on the screen of a smartphone as the attendee terminal 40.

[0071] In this embodiment, an example will be described in which the event is a baseball game and the event venue is a baseball stadium. The event may also be a live performance, another sports event, a fireworks display, etc. The event venue may also be a stadium, an amphitheater, an outdoor venue, etc. Note that the application of this embodiment is not limited to event venues, and may also be any facility in which a seat is associated with each user.

[0072] Fig. 9(A) shows the top screen of the ticket app. When a user launches the ticket app on the attendee terminal 40, the top screen of the ticket app shown in Fig. 9(A) is displayed. This top screen of the ticket app displays items (buttons, icons) such as "Purchase Ticket," "Display Ticket," "Import Ticket," and "Transfer Ticket." Other items may also be included.

[0073] In FIG. 9(A), selecting "Buy Tickets" takes you to a screen where you can purchase tickets by selecting, for example, the event name, date and time, seat type, number of tickets, etc. Selecting "Import Tickets" takes you to a screen where you can import paper ticket information into the fan club app by, for example, entering the paper ticket number, scanning the code printed on the paper ticket, or photographing the paper ticket. Selecting "Transfer Tickets" takes you to a screen where you can transfer your tickets by, for example, specifying a user name, etc.

[0074] Also, when "Display tickets" is selected in Fig. 9(A), if there are tickets for the day, the ticket information for the day and an electronic ticket including the ticket code are displayed as shown in Fig. 9(B). Also, if there are no tickets for the day but there are tickets for events that have not yet started, a list of ticket summaries for the events that have not yet started is displayed as shown in Fig. 9(C). When a ticket is selected in the ticket list, the ticket details and electronic ticket may be displayed.

[0075] Also, although not shown in the figure, if there are no tickets available for the day, ticket information (event details, date and time, venue, link to purchase tickets, etc.) for nearby events that are being held on the same day or in the near future near the current location will also be displayed.

[0076] As shown in Figure 9(B), when an electronic ticket is displayed on an attendee terminal 40 and the attendee holds the electronic ticket over a gate terminal 50 to enter the venue, route information 301 from the position of the gate terminal 50 over which the electronic ticket is held (the position of the entrance gate through which the attendee entered) to the seat is displayed on the screen of the attendee terminal 40, as shown in Figure 9(D). On the screen shown in Figure 9(D), ticket information indicating the seat number etc. is displayed above the route information 301.

[0077] The route information 301 shown in FIG. 9(D) includes a venue map 302, an entire map button 311, a close button 312, and the like. In FIG. 9(D), the venue map 302 is a map of part of the venue, including the entrance gate and the destination seat. The venue map 302 displays the entrance gate (gate g2 in FIG. 9(D)) and the destination seat (seat s2xx in FIG. 9(D)), along with a route (line) 303 from the entrance gate to the seat. The route 303 runs from gate g2 through the concourse below the spectator seats, enters the spectator seats through entrance e2, and then takes the main aisle, stairs p221, and aisle p211 to seat s2xx. By displaying this route information 301 on the attendee terminal 40 used to enter the venue, attendees can be conveniently guided to their destination.

[0078] Note that the route information 301 shown in Figure 9(D) is an example, and the route information presented on the visitor terminal 40 need only indicate the route from the gate location where the gate terminal 50 used by the visitor to enter is located to the target location (seat location) according to the ticket information. Note that, to prevent visitors from walking while looking at the screen of the visitor terminal 40, it is preferable that the route information simply presents the route. Furthermore, the route information is not limited to outputting an image showing the route, and instead of or in addition to outputting an image, the route may be indicated by sound, vibration, etc.

[0079] Furthermore, when an attendee operates the overall map button 311 in FIG. 9(D), the venue map 302 switches to an overall map of the venue. The overall map also needs to show the route from the entrance gate to the seat location. When an attendee operates the close button 312 in FIG. 9(D), the route information 301 closes and switches to, for example, the electronic ticket screen shown in FIG. 9(B). At this time, a message that the route information 301 has been closed may be sent to the server 10. This allows the server 10 to determine whether the route information 301 is displayed on the attendee terminal 40, i.e., whether the attendee is viewing the route information 301 and moving along the route.

[0080] Since it is expected that visitors will use the shops and restrooms at the venue, the locations of the shops and restrooms may be marked up on the venue map 302 or the overall map shown in Figure 9(D). Also, the locations of the shops and restrooms may be displayed by performing a predetermined operation.

[0081] 9(B) and (C) overlap, the two displays may be displayed simultaneously or sequentially. Alternatively, the two displays may be displayed superimposed. In this way, if there are tickets for the day and tickets for the pre-event event, the display and processing can be performed according to the ownership status.

[0082] Also, if there are tickets for an event that has not yet started, a summary list of the tickets for the event that has not yet started is displayed, as shown in Figure 9(C), but it is also possible to display the ticket details and electronic ticket for the event that has not yet started.

[0083] (Variation) 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 embodiments may be omitted or replaced, or any configuration may be added.

[0084] In the above embodiment, route information from the server 10 to the seat is provided to the visitor terminal 40 that has held the electronic ticket over the gate terminal 50. However, the server 10 may also provide the route information to the gate terminal 50 that has acquired the electronic ticket. The gate terminal 50 that has received the route information may then notify the visitor terminal 40 that has held the electronic ticket over it via wireless communication or the like. In other words, the server 10 may provide the route information to the visitor terminal 40 indirectly. In this way, even if the visitor terminal 40 cannot connect to the communications network 30 due to poor radio signal strength or the like at the installation location of the gate terminal 50, the route information can be received via the gate terminal 50, allowing the visitor to be conveniently guided to their target location.

[0085] In addition, when the gate terminal 50 receives the route information, the gate terminal 50 that has received the route information may display the route information on a screen provided on the gate terminal 50 or on a screen installed nearby to present the route information to the entrant, or may output the route information on paper and provide it to the entrant.

[0086] At a given venue, if one gate terminal 50 reads an electronic ticket displayed on one visitor terminal 40 and provides route information to that visitor terminal 40, the gate terminal 50 may be configured not to transmit route information to that visitor terminal 40 even if the gate terminal 50 reads the electronic ticket again. This prevents the same route information from being sent multiple times to the same visitor terminal 40. For example, when a visitor re-enters the venue, this prevents the visitor from being annoyed by having to send route information again even though the visitor's seat location is already known.

[0087] In the above embodiment, when a ticket display operation is detected, the attendee terminal 40 (ticket app) displays different information depending on the event date and time of the ticket owned by the user. That is, if there is a ticket for that day, the electronic ticket for that ticket is displayed, and if there is no ticket for that day, a list of tickets for upcoming events or ticket information for nearby events is displayed. This function is not essential; for example, when the attendee terminal 40 detects a ticket display operation, if there is a ticket for that day, the electronic ticket for that ticket is displayed, and if there is no ticket for that day, a message indicating that there are no tickets for that day may be displayed.

[0088] Furthermore, when the electronic ticket management system 100 presents a route to one attendee terminal and then presents a route to another attendee terminal, it does not have to present a route that avoids the route presented to the first attendee terminal. For example, the electronic ticket management system 100 may provide and present a route to the other attendee terminal without referencing the route presented to the first attendee terminal. In this case, the server 10 may always provide the attendee terminal 40 with the shortest route from the entrance gate to the target location, or may determine the route to provide to the attendee based on other information such as the time of day, ticket sales for the day, and the number of attendees already present.

[0089] In the above embodiment, the server 10 has the functionality of the provider 101, but the gate terminal 50 may also have the functionality of the provider 101. In other words, the electronic ticket management system 100 may be realized by the attendee terminal 40 and the gate terminal 50.

[0090] In the above embodiment, the server 10 outputs route information from the gate terminal 50 to the seat position, but the server 10 may also output route information from the gate terminal 50 to a location that serves as a landmark for the seat position (for example, a convenience store near the seat).

[0091] In the above embodiment, route information from the gate terminal 50 to the seat location is presented. However, if the visitor terminal 40 needs to pass through multiple gates from the entrance to the event venue to the seat location, the content of the route information provided to the visitor terminal 40 may be different depending on whether the visitor terminal 40 transmits or receives data to or from a gate terminal 50 far from the seat or the gate terminal 50 closest to the seat. For example, if the visitor terminal 40 transmits or receives data to or from a gate terminal 50 other than the gate terminal 50 closest to the seat, the server 10 may generate route information that only indicates the direction (e.g., an arrow display) to the next-closest gate terminal 50. Furthermore, if the visitor terminal 40 transmits or receives data to or from the gate terminal 50 closest to the seat, the server 10 may generate route information from the gate terminal 50 that was transmitted or received to the seat location.

[0092] Visitor terminal 40 can be realized using a normal computer, rather than a dedicated device. For example, visitor terminal 40 that performs the above-mentioned processes can be configured by installing a program for executing the above-mentioned functions on a computer included in the terminal device via a communications network.

[0093] The server 10 can be realized using a normal computer, not a dedicated device. For example, the server 10 that executes the above-described processes may be configured by installing a program for executing the above-described functions from a recording medium that stores the program on the computer. Also, one server 10 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 a program for executing the above-described functions may be distributed.

[0095] Furthermore, if an OS (Operating System) provides some of the above 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 flowcharts, sequences, elements included in the embodiments, and their arrangements, materials, conditions, shapes, sizes, etc., described in the embodiments are not limited to those illustrated and can be modified as appropriate. Furthermore, configurations shown in different embodiments can be partially substituted or combined with each other.

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

[0098] (Appendix 1) An electronic ticket management system including an attendee terminal and a gate terminal, the visitor terminal includes an output unit that outputs ticket information related to the ticket; the gate terminal includes an acquisition unit that acquires ticket information output from the visitor terminal; The electronic ticket management system includes a provision unit that provides route information to the visitor terminal, the route information being information based on a route from a gate location where the gate terminal that acquired the ticket information is located to a target location associated with the ticket information, The visitor terminal includes a presentation unit that presents the route information provided by the provision unit. Electronic ticket management system.

[0099] (Appendix 2) When the presentation unit presents a route to one visitor terminal and then presents a route to another visitor terminal within a predetermined time, the presentation unit presents a route that avoids the route presented to the one visitor terminal. 1. An electronic ticket management system as described in Appendix 1.

[0100] (Appendix 3) After presenting a route to one visitor terminal, when the presentation unit presents a route to another visitor terminal while the route presented to the one visitor terminal is displayed, the presentation unit presents a route that avoids the route presented to the one visitor terminal. 1. An electronic ticket management system as described in Appendix 1.

[0101] (Appendix 4) When the visitor terminal receives a predetermined ticket display operation in a case where there are multiple tickets corresponding to the visitor terminal, if the current time corresponds to the admission time of one of the tickets corresponding to the visitor terminal, it displays ticket information related to the ticket corresponding to that admission time, and if the current time does not correspond to the admission time of one of the tickets corresponding to the visitor terminal, it displays a list of tickets corresponding to the visitor terminal. 1. An electronic ticket management system as described in Appendix 1.

[0102] (Appendix 5) When the visitor terminal receives a predetermined ticket display operation, if the current time does not correspond to the admission time of any ticket corresponding to the visitor terminal, it acquires the location information of the visitor terminal, searches for tickets of venues that can be reached within the admission time from the location information, and displays information about the searched tickets. 5. An electronic ticket management system according to any one of appendices 1 to 4.

[0103] (Appendix 6) An electronic ticket management method in an electronic ticket management system including an attendee terminal and a gate terminal, The visitor terminal outputs ticket information relating to the ticket, The gate terminal acquires the ticket information output from the visitor terminal, The electronic ticket management system provides route information to the visitor terminal, the route information being information based on a route from the gate location where the gate terminal that acquired the ticket information is located to the target location associated with the ticket information, The visitor terminal presents the route information. Electronic ticket management methods.

[0104] (Appendix 7) Outputting ticket information relating to the ticket to a gate terminal; receiving route information based on a route from a gate location where the gate terminal that has acquired the ticket information is located to a target location associated with the ticket information; Present the received route information Visitor terminal.

[0105] (Appendix 8) The ticket information output from the visitor terminal to the gate terminal is acquired from the gate terminal. Route information, which is information based on a route from the gate location where the gate terminal that obtained the ticket information is located to the target location associated with the ticket information, is provided to the visitor terminal. server.

[0106] (Appendix 9) Computer, Outputting ticket information relating to the ticket to a gate terminal; receiving route information based on a route from a gate location where the gate terminal that has acquired the ticket information is located to a target location associated with the ticket information; Present the received route information A program that functions as a visitor terminal.

[0107] (Appendix 10) Computer, The ticket information output from the visitor terminal to the gate terminal is acquired from the gate terminal. Route information, which is information based on a route from the gate location where the gate terminal that obtained the ticket information is located to the target location associated with the ticket information, is provided to the visitor terminal. A program that acts as a server. [Industrial Applicability]

[0108] According to the present invention, it is possible to provide an electronic ticket management system, an electronic ticket management method, an attendee terminal, a server, and a program that can suitably guide attendees to their target locations. [Explanation of symbols]

[0109] 10 Servers 30 Communication Network 40 Visitor terminal 50 Gate Terminal 11, 41 processors 12, 42 Storage device 13, 43 Communication Interface 14, 44 input devices 15, 45 output devices 100 Electronic Ticket Management System 101 Provision Department 401 Output section 402 Presentation section 501 Acquisition Department

Claims

1. An electronic ticket management system including an attendee terminal, a gate terminal, and a server, the visitor terminal includes an output unit that outputs ticket information related to the ticket; The gate terminal an acquisition unit that acquires ticket information output from the visitor terminal; The ticket information acquired by the acquisition unit is transmitted to the server; The server storing gate location information indicating the location of the gate terminal, target location information indicating a target location according to the ticket information, and venue route data indicating a route network of the venue according to the ticket information; a provision unit that, upon receiving the ticket information from the gate terminal, generates a route from the gate position where the gate terminal that obtained the ticket information is located to the target position associated with the ticket information based on the gate position information, the target position information, and the venue route data, and provides route information based on this route to the visitor terminal; the visitor terminal includes a presentation unit that presents a route according to the route information provided by the provision unit, When the presentation unit presents a route to one visitor terminal and then presents a route to another visitor terminal within a predetermined time, the presentation unit presents a route that avoids the route presented to the one visitor terminal. Electronic ticket management system.

2. An electronic ticket management system including an attendee terminal, a gate terminal, and a server, the visitor terminal includes an output unit that outputs ticket information related to the ticket; The gate terminal an acquisition unit that acquires ticket information output from the visitor terminal; The ticket information acquired by the acquisition unit is transmitted to the server; The server storing gate location information indicating the location of the gate terminal, target location information indicating a target location according to the ticket information, and venue route data indicating a route network of the venue according to the ticket information; a provision unit that, upon receiving the ticket information from the gate terminal, generates a route from the gate position where the gate terminal that obtained the ticket information is located to the target position associated with the ticket information based on the gate position information, the target position information, and the venue route data, and provides route information based on this route to the visitor terminal; the visitor terminal includes a presentation unit that presents a route according to the route information provided by the provision unit, After presenting a route to one visitor terminal, when the presentation unit presents a route to another visitor terminal while the route presented to the one visitor terminal is displayed, the presentation unit presents a route that avoids the route presented to the one visitor terminal. Electronic ticket management system.

3. An electronic ticket management system including an attendee terminal, a gate terminal, and a server, the visitor terminal includes an output unit that outputs ticket information related to the ticket; The gate terminal an acquisition unit that acquires ticket information output from the visitor terminal; The ticket information acquired by the acquisition unit is transmitted to the server; The server storing gate location information indicating the location of the gate terminal, target location information indicating a target location according to the ticket information, and venue route data indicating a route network of the venue according to the ticket information; a provision unit that, upon receiving the ticket information from the gate terminal, generates a route from the gate position where the gate terminal that obtained the ticket information is located to the target position associated with the ticket information based on the gate position information, the target position information, and the venue route data, and provides route information based on this route to the visitor terminal; The visitor terminal is a presentation unit that presents a route according to the route information provided by the provision unit, When there are multiple tickets corresponding to the visitor terminal, upon receiving a predetermined ticket display operation, if the current time corresponds to the admission time of any of the tickets corresponding to the visitor terminal, the ticket information relating to the ticket corresponding to that admission time is displayed, and if the current time does not correspond to the admission time of any of the tickets corresponding to the visitor terminal, a list of tickets corresponding to the visitor terminal is displayed. Electronic ticket management system.

4. An electronic ticket management system including an attendee terminal, a gate terminal, and a server, the visitor terminal includes an output unit that outputs ticket information related to the ticket; The gate terminal an acquisition unit that acquires ticket information output from the visitor terminal; The ticket information acquired by the acquisition unit is transmitted to the server; The server storing gate location information indicating the location of the gate terminal, target location information indicating a target location according to the ticket information, and venue route data indicating a route network of the venue according to the ticket information; a provision unit that, upon receiving the ticket information from the gate terminal, generates a route from the gate position where the gate terminal that obtained the ticket information is located to the target position associated with the ticket information based on the gate position information, the target position information, and the venue route data, and provides route information based on this route to the visitor terminal; The visitor terminal is a presentation unit that presents a route according to the route information provided by the provision unit, When a predetermined ticket display operation is received, if the current time does not correspond to the admission time of any ticket corresponding to the visitor terminal, the location information of the visitor terminal is acquired, and tickets for venues that can be reached within the admission time are searched for from the location information, and information about the searched tickets is displayed. Electronic ticket management system.

5. An electronic ticket management method in an electronic ticket management system including an attendee terminal, a gate terminal, and a server, comprising: The visitor terminal outputs ticket information relating to the ticket, The gate terminal acquires the ticket information output from the visitor terminal and transmits it to the server, The server: storing gate location information indicating the location of the gate terminal, target location information indicating a target location according to the ticket information, and venue route data indicating a route network of the venue according to the ticket information; When the ticket information is received from the gate terminal, a route is generated from the gate location where the gate terminal that obtained the ticket information is located to the target location associated with the ticket information based on the gate location information, the target location information, and the venue route data, and route information based on this route is provided to the visitor terminal; The visitor terminal, presenting a route according to the route information; When there are multiple tickets corresponding to the visitor terminal, upon receiving a predetermined ticket display operation, if the current time corresponds to the admission time of any of the tickets corresponding to the visitor terminal, the ticket information relating to the ticket corresponding to that admission time is displayed, and if the current time does not correspond to the admission time of any of the tickets corresponding to the visitor terminal, a list of tickets corresponding to the visitor terminal is displayed. Electronic ticket management methods.

6. storing gate location information indicating the location of the gate terminal, target location information indicating a target location according to the ticket information, and venue route data indicating a route network of the venue according to the ticket information; Acquires ticket information output from the visitor terminal to the gate terminal from the gate terminal; Based on the gate position information, the target position information, and the venue route data, a route is generated from the gate position where the gate terminal that obtained the ticket information is located to the target position associated with the ticket information, and route information based on this route is provided to the visitor terminal; After providing the route information to one visitor terminal, if the route information is to be provided to another visitor terminal within a predetermined time, the route information is provided based on a route that avoids the route according to the route information provided to the one visitor terminal. server.

7. Computer, storing gate location information indicating the location of the gate terminal, target location information indicating a target location according to the ticket information, and venue route data indicating a route network of the venue according to the ticket information; Acquires ticket information output from the visitor terminal to the gate terminal from the gate terminal; Based on the gate position information, the target position information, and the venue route data, a route is generated from the gate position where the gate terminal that obtained the ticket information is located to the target position associated with the ticket information, and route information based on this route is provided to the visitor terminal; After providing the route information to one visitor terminal, if the route information is to be provided to another visitor terminal within a predetermined time, the route information is provided based on a route that avoids the route according to the route information provided to the one visitor terminal. A program that acts as a server.

Images