Electronic ticket management system, electronic ticket management method, visitor 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 entrant terminal, a server, and a program.

Background Art

[0002] There has been proposed an electronic ticket system that generates ticket data including ticket information and a control program by a ticket issuing device, transmits the generated ticket data from the ticket issuing device to a portable information terminal, and displays a map to a usage location corresponding to the ticket information based on position data included in the ticket data and position data of the portable information terminal obtained by a GPS receiver (positioning device) mounted on the portable information terminal (for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a venue (such as a baseball stadium, an arena, an amphitheater, etc.) where there are many gates in various places, after entering the venue, it is difficult for the entrant to know which route to take to reach the target position (for example, a seat). In addition, the venue may have multiple floors or the radio wave may not reach, making it difficult to guide the entrant to the seat using the positioning device mounted on the portable information terminal. Thus, after entering the venue using an electronic ticket, it is desired to suitably guide the user to the seat.

[0005] The present invention has been made in view of the above circumstances, and an object thereof is to provide an electronic ticket management system or the like that can suitably guide an entrant to a target position.

Means for Solving the Problems

[0006] Of the embodiments disclosed in the present application, a brief overview of representative ones is as follows. The electronic ticket management system according to this embodiment is an electronic ticket management system including an entrant terminal and a gate terminal, the entrant terminal includes an output unit that outputs ticket information related to the ticket, the gate terminal includes an acquisition unit that acquires the ticket information output from the entrant terminal, in the electronic ticket management system, there is a provision unit that provides the entrant terminal with route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is arranged to the target position associated with the ticket information. The entrant terminal includes a presentation unit that presents the route information provided by the provision unit.

Advantages of the Invention

[0007] According to the present invention, an entrant can be suitably guided to the target position.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying Out the Invention

[0009] Hereinafter, the electronic ticket management system 100 according to the embodiment of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals.

[0010] FIG. 1 is a block diagram showing the configuration of the electronic ticket management system 100 according to the present embodiment. The electronic ticket management system 100 is a system that manages whether to allow entry to an event (event venue) based on an electronic ticket corresponding to the visitor terminal 40 (for example, an electronic ticket owned by a user). Further, the electronic ticket management system 100 outputs information regarding a route to a predetermined position related to the electronic ticket (for example, the seat position of the user of the visitor terminal 40) to the visitor terminal 40 located in the event venue. A user who enters the event venue is also referred to as a visitor. The electronic ticket management system 100 of this embodiment includes a server 10, a visitor terminal 40, and a gate terminal 50, and each is connected via a communication network 30 such as the Internet or a mobile communication network. The server 10 and the visitor terminal 40 transmit and receive information via the communication network 30. Also, the server 10 and the gate terminal 50 transmit and receive information via the communication network 30.

[0011] The server 10 manages ticket information of an event electronically owned by a user and the entry of the user to the event venue based on the ticket information. The server 10 performs ticket authentication by determining whether the ticket corresponding to the ticket information received from the gate terminal 50 is valid or not, and transmits the authentication result to the gate terminal 50. Thereby, the gate terminal 50 can confirm the validity of the presented electronic ticket.

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

[0013] The ticket application may have functions such as providing event holding information regarding the target of support by the user, live relay of the event, recorded relay of the event, display of messages from the support target, display of achievements / results of the support target, communication between fans using the application, online purchase of goods, etc. Also, the ticket application outputs information regarding the route to the seat position of the event in which the user participates.

[0014] The server 10 is a high-performance information processing device that has a plurality of storage devices or a control unit such as a plurality of CPUs. Note that the server 10 may be configured by a communicable information processing device such as a personal computer (PC) or a workstation. Note that the server 10 may be a dedicated device. Also, the server 10 may be configured by a plurality of information processing devices.

[0015] The attendee terminal 40 is an information processing device such as a smartphone or a tablet that can be carried by the user. The attendee terminal 40 can install the ticket application provided by the server 10. The attendee terminal 40 displays an electronic ticket or information regarding the ticket on the display screen based on the user's operation in the installed ticket application. The electronic ticket includes, for example, information regarding the event holding date and time, seat position, a two-dimensional code, a ticket code composed of a barcode, etc., corresponding to the electronic ticket. Narrowly speaking, the ticket code displayed on the attendee terminal 40 is also referred to as an electronic ticket.

[0016] In addition, when the attendee terminal 40 of this embodiment enters the event venue via the gate terminal 50 using an electronic ticket, it can display the route information from the entrance gate in the event venue to the user's seat. Details of the processing and operations for displaying the route information will be described later.

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

[0018] Specifically, the gate terminal 50 reads the electronic ticket displayed on the attendee terminal 40 and presented by the attendee's operation, or the ticket code described on the paper ticket, and sends a ticket authentication request corresponding to the read ticket code to the server 10. The server 10 performs authentication processing based on the information included in the received ticket authentication request, and sends the authentication result to the gate terminal 50. When the gate terminal 50 receives the authentication result from the server 10, it displays the authentication result on the display screen or outputs a voice corresponding to the authentication result.

[0019] The gate terminal 50 may be a mobile terminal carried by the staff at the entrance gate, or may be an installed gate device (automatic ticket gate) equipped with an openable / closable door or bar. When the gate terminal 50 is a mobile terminal, the staff may permit or reject the attendee's entry into the venue according to the authentication result output from the gate terminal 50. When the gate terminal 50 is an installed gate device, the gate terminal 50 may permit or reject the attendee's entry into the venue by opening or closing the door or bar according to the authentication result.

[0020] In FIG. 1, two visitor terminals 40 and two gate terminals 50 are shown, but the number of visitor terminals 40 and gate terminals 50 may be arbitrary. The gate terminals 50 may be provided in a predetermined number for each entrance gate of the event venue. Note that a plurality of gate terminals 50 may be provided within the event venue.

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

[0022] The output unit 401 of the visitor terminal 40 outputs ticket information related to a ticket owned by a user (visitor) when a ticket application operates on the visitor terminal 40. 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 output ticket information by wireless communication.

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

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

[0025] The presenting 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 the route connecting the entrance gate and the seat on the screen.

[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 in front of the code reader of the gate terminal 50 at the admission gate, the gate terminal 50 reads the ticket ID, which is the identification information of the ticket included in the electronic ticket, and the user ID, which is the identification information of the user. In this case, the ticket ID becomes the ticket information. Then, the gate terminal 50 sends a ticket authentication request including the read ticket ID, user ID, and the gate ID, which is its own identification information, to the server 10. When the server 10 receives a ticket authentication request including the ticket ID, user ID, and gate ID, it performs ticket authentication processing by querying the ticket specified by the ticket ID and the tickets owned by the user specified by the user ID, and sends 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 of admission OK, for example, it displays the authentication result on the gate terminal 50 or a display device provided on the admission gate, and performs control to open the gate door and permit the user to enter the event venue. Note that based on the authentication result displayed on the display device, the staff may guide the user to the event venue. Also, when the ticket authentication is successful, the server 10 generates a path connecting the gate position of the admission gate specified by the gate ID and the seat position corresponding to the ticket ID, and sends the path information corresponding to the generated path to the attendee terminal 40.

[0027] According to the electronic ticket management system 100 of this embodiment, when entering the event venue via the gate terminal 50 using the ticket information (electronic ticket) output by the entrant terminal 40, route information is generated based on the gate position specified by the gate terminal 50 and the seat position specified by the ticket information, and the route information from the gate position to the seat position can be provided to the entrant terminal 40. That is, when the entrant enters the event venue using the electronic ticket, the entrant can automatically obtain the route information from the entrance gate to the seat position. Thereby, even when the current position cannot be specified by the entrant terminal 40 due to, for example, poor radio waves of the positioning device, the route information within the venue can be surely provided to the entrant terminal 40, so that the entrant can be suitably guided to the seat position.

[0028] FIG. 4 is a diagram showing a hardware configuration example of the information processing devices constituting the server 10 and the entrant terminal 40. The server 10 includes a processor 11 such as a CPU (Central Processing Unit) and a GPU (Graphical processing unit), a memory, a storage device 12 such as an HDD and / or an SSD, a communication interface 13 for performing wired or wireless communication, an input device 14 for receiving 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.

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

[0030] Next, the operation of the electronic ticket management system 100 will be described. FIG. 5 is a flowchart showing an example of the processing during ticket application startup executed on the visitor terminal 40. The processing during ticket application startup is executed, for example, when the processor 41 of the visitor terminal 40 reads a program stored in the storage device 42.

[0031] The processing during ticket application startup is processing that is executed on the visitor terminal 40 when the ticket application is started. In this processing, the processor 41 of the visitor terminal 40 determines whether or not it has detected a ticket display operation by the user of the visitor terminal 40 (step S11). The ticket display operation may be any predetermined operation on the screen of the ticket application.

[0032] If the ticket display operation is not detected (step S11; No), the processor 41 executes processing according to the user's operation (step S12). In step S12, processing for searching for, purchasing, transferring tickets, importing paper tickets into the ticket application, etc. is executed according to the user's 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 end operation of the ticket application is detected in step S12.

[0033] When the 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 predetermined user. As shown in FIG. 7(A) for example, the user ticket information includes a user ID that uniquely identifies a user, a ticket ID that uniquely identifies an event ticket, the date and time of the event (event date, event period, event time, etc.), the event venue of the event (venue name, location information, etc.), and a seat ID that identifies the seat position (seat number, seat type, block, row, aisle, etc.) in the event venue. When a user owns a plurality of tickets, it is sufficient that a plurality of ticket IDs are associated with the user ID. When a user purchases a ticket by an electronic method on a website, application, etc. provided by the server 10, the user ticket information corresponding to the ticket is registered in the storage device 12. The user ticket information is referred to for authentication when the user enters the event venue using an electronic ticket. The user ticket information may include other information. Note that the ticket ID associated with the user ID may be not only the ticket purchased by the user but also the ID of a ticket transferred by a predetermined method.

[0035] Returning to FIG. 5, in this embodiment, when a ticket display operation is detected, the entrant terminal 40 (ticket application) is configured to display different information depending on the date and time of the event of the ticket owned by the user. When the processor 41 acquires the user ticket information, the processor 41 determines whether the user has a same-day ticket among the tickets owned by the user by referring to the event date and time of the user ticket information (step S14).

[0036] If there is a same-day ticket (step S14; Yes), the processor 41 displays the electronic ticket (event information, seat information, ticket code, etc.) of the ticket on the screen (display) of the attendee terminal 40 (step S15). In step S15, the electronic ticket displayed on the attendee terminal 40 is further read by the gate terminal 50. In this way, if the user has a same-day ticket, it is assumed that the user will enter the event venue using that ticket, so the electronic ticket is displayed. The user can enter the event venue by holding this electronic ticket in front of the gate terminal 50 at the entrance gate.

[0037] At this time, referring to the current time and the opening time (admission time) of the event venue, if the current time is before the opening time, since admission is not possible, 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 holding date and time. Note that the holding time may be the same time as the holding date and time.

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

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

[0040] After finishing the process of step S17, the process proceeds to the process of step S12. Note that after the process of step S17, the process may proceed to the process of step S18 to execute a process corresponding to a ticket other than the same-day ticket.

[0041] If there is no ticket for the day (step S14; No), the processor 41 determines whether the user has a ticket for the pre-event by referring to the event date and time of the user ticket information (step S18).

[0042] If there is a ticket for the pre-event (step S18; Yes), the processor 41 displays a list of tickets for the pre-event (such as a summary list of tickets) on the screen of the visitor terminal 40 (step S19). Thereby, the user can confirm the tickets owned for the pre-event.

[0043] After the process of step S19 or if there is no ticket for the pre-event (step S18; No), the ticket information of nearby events held on the day or in the near future in the vicinity of the current position of the visitor terminal 40 is acquired from the server 10 and displayed on the screen of the visitor terminal 40 (step S20). The ticket information may include the content of the event, the date and time of the event, the venue, a link for purchasing tickets, etc. Thereby, the event can be promoted to the user and the purchase of tickets can be encouraged. If there are tickets for the pre-event, the list of tickets for the pre-event and the ticket information of nearby events may be displayed. Also, the list of tickets for the pre-event and the ticket information of nearby events may be sequentially displayed.

[0044] In the process of step S20, for example, the current position information of the visitor terminal 40 is acquired from a positioning device such as GPS (Global Positioning System) provided in the visitor terminal 40, and a request for acquiring the ticket information of nearby events, which are events held at locations within the vicinity (a predetermined distance range) of the acquired current position information, is sent to the server 10. Then, when the server 10 receives the acquisition request, it searches for events from a database or the like where event information is stored based on the current position information, the current time, etc., and may send the ticket information corresponding to the search result to the visitor terminal 40.

[0045] FIG. 6 is a flowchart showing an example of processing at the time of receiving ticket information executed by the server 10. The processing at the time of receiving ticket information is executed by the processor 11 of the server 10 reading a program stored in the storage device 12. In the processing at the time of receiving ticket information, 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 processing at the time of receiving ticket information is terminated. Note that the processor 11 may proceed to step S101.

[0046] When a ticket authentication request is received (step S101; Yes), the processor 11 performs an authentication process on the received ticket information (step S102). In step S102, for example, user ticket information corresponding to the user ID included in the ticket authentication request is acquired, and it is determined whether or not the ticket having the ticket ID included in the ticket authentication request is held. If the ticket having the ticket ID included in the ticket authentication request is held, the authentication is successful, and if not, the authentication fails.

[0047] Subsequently, the processor 11 determines whether or not the authentication of the ticket information has been successful (step S103). When the ticket authentication is 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, the processor 11 acquires the gate position information of the gate terminal 50 that sent the ticket authentication request based on the gate ID included in the ticket authentication request (step S105). In the process of step S105, the processor 11 acquires the position information corresponding to the gate ID by referring to, for example, the gate position information stored in the storage device 12 based on the gate ID included in the ticket authentication request. Thereby, the processor 11 specifies the gate position which is the entry position of the entrant into the venue.

[0049] FIG. 7(B) shows an example of gate position information stored in the storage device 12 of the server 10. The gate position information is, for example, as shown in FIG. 7(B), information in which a gate ID that uniquely identifies the gate terminal 50, position information (latitude and longitude information, etc.) of the gate terminal 50, connection path information that is information on the path connected to the gate terminal 50, and adjacent gate information that is information on the entrance gate adjacent to the entrance gate where the gate terminal 50 is installed are associated with each other. The connection path information and adjacent gate information in the gate position information are referred to when generating the path information. Note that the gate position information may include other information.

[0050] Further, the processor 11 acquires seat position information based on the ticket ID (step S106). In the process of step S106, the processor 11 acquires the seat ID of the user ticket information based on, for example, the ticket ID included in the ticket authentication request, and refers to the seat position information stored in the storage device 12 based on the seat ID, thereby acquiring the position information of the seat corresponding to the ticket ID. Thereby, the processor 11 specifies the seat position that is the target position of the person entering the venue.

[0051] FIG. 7(C) shows an example of seat position information stored in the storage device 12 of the server 10. The seat position information is, for example, as shown in FIG. 7(C), information in which a seat ID that uniquely identifies the seat in the event venue, position information (latitude and longitude information, etc.) of the seat, and connection path information that is information on the path connected to the seat (the nearest path if the seat is not adjacent to the path) are associated with each other. The connection path information in the seat position information is referred to when generating the path information. Note that the seat position information may include other information. The event venue may be identifiable by the seat ID, or the seat position information may separately include the identification information of the event venue.

[0052] Subsequently, the processor 11 executes a path generation process for generating path information from the position of the gate terminal 50 to the seat position (step S107).

[0053] In the process of step S107, the processor 11 searches for a path (for example, the shortest path, the optimal path considering congestion, etc.) connecting the gate position information acquired in step S105 and the seat position information acquired in step S106 based on the venue path data of the venue. Then, the searched path is superimposed on the venue map to generate path information for providing to the attendee.

[0054] For example, in this embodiment, the server 10 stores information such as the positions and lengths of the paths (passages, intersections, stairs, etc.) of each venue as venue path data, and searches for a path based on the venue path data.

[0055] FIG. 7(D) shows an example of the venue path data stored in the storage device 12 of the server 10. The venue path data of this embodiment is path network information including nodes (points) indicating characteristic points (intersections, turning corners, dead ends, etc.) of the path in the venue map and links (lines) indicating the paths connecting the nodes. As shown in FIG. 7(D) for example, the venue path data is information in which a path ID uniquely identifying the path, a path type indicating the type of the path such as a passage, an intersection, a stair, a turning corner, an entrance, a dead end, etc., position information of the path (start position, end position, etc. in the case of a passage), and additional information indicating the length of the path, the width of the passage, etc. are associated. The storage device 12 of the server 10 stores this venue path data for each venue. Note that the venue path data may include other information.

[0056] The path ID is stored in the connection path information in the gate position information shown in FIG. 7(B) and the seat position information shown in FIG. 7(C). Thereby, based on the gate position information and the seat position information, the path connecting to the gate terminal 50 and the seat can be specified.

[0057] FIG. 8 shows an example of an overall map of a baseball stadium as an event venue. Note that in FIG. 8, as an example, the seating area on the third base side of the baseball stadium is shown. As shown in FIG. 8, the baseball stadium is provided with a plurality of entrance gates (gates g1 to g4 in FIG. 8), entrances to the spectator seats (entrances e1 to e4 in FIG. 8), passages (passage p211 as an example in FIG. 8), stairs (stairs p221 as an example in FIG. 8), intersection n001, etc. For each of these routes and feature points in the venue, venue route data as shown in FIG. 7(D) may be stored.

[0058] Note that the overall map may contain other information. For example, the overall map may include toilets and souvenir shops. And the server 10 may store the location information of toilets and souvenir shops as facility information.

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

[0060] Note that the venue map (image data) may be pre-stored in the storage device 12 of the server 10. In step S107, the generated series of routes may be superimposed on an overall map of the venue as shown in FIG. 8 or a partial map of the venue (a map near the seats, etc.) to generate a route map. Note that the venue map and the route information generated based on the venue map may be 2D images, or may be 3D images in the case where the venue has a hierarchical structure, etc.

[0061] Also, the method for generating the route in step S107 is just an example. As long as route information indicating a route from at least the gate position where the gate terminal 50 used by the entrant for entry is arranged to the target position (seat position) according to the ticket information is generated, the route information may be generated by any method. For example, in generating the route information, an algorithm for generating a route based on road nodes and link information such as car navigation may be borrowed.

[0062] In step S107, it is not limited to searching for the shortest route during route search. Different route information may be provided to the entrant according to the length of the route, the width of the passage, and the congestion status of the route included in the venue route data. For example, when the width of the passage is narrow, a route avoiding the passage may be preferentially selected. Also, after providing route information to one entrant, for a predetermined period, route information may be provided to other entrants so as to avoid the route corresponding to the route information provided to the one entrant. By doing so, it is possible to prevent a specific route in the venue from becoming congested or jammed.

[0063] In this case, in step S107, after generating the route information of one entrant, the generated route information may be stored for a predetermined period, and for a predetermined period, the routes (passages, entrances, stairs, etc.) included in the route information may be avoided, and the routes of other entrants may be searched and generated.

[0064] Also, after providing the route information of one entrant, while the route information is displayed on the entrant terminal 40, it is presumed that the one entrant is browsing the route information and is moving along the presented route. And when the one entrant closes the route information displayed on the entrant terminal 40, it is presumed that the one entrant has arrived at the seat. Therefore, when providing route information to other entrants while the route information provided to one entrant is being displayed, route information avoiding the route presented to the one entrant may be provided to other entrants. By doing so as well, it is possible to prevent a specific route in the venue from becoming congested or jammed.

[0065] In this case, after generating the route information of one visitor in step S107, the generated route information may be stored, and the routes (passages, entrances, stairways, etc.) included in the route information may be avoided, and the routes of other visitors may be searched for and generated. Then, for example, at the visitor terminal 40, the display state of the route information displayed on the screen is monitored, and when the route information is closed, this fact is transmitted to the server 10. And when the server 10 receives that the route information provided to one visitor's visitor terminal 40 has been closed, the routes (passages, entrances, stairways, etc.) included in the route information may be made available for other visitors. That is, the predetermined period may be the period until the route information provided to one visitor is closed.

[0066] Also, the route search method may be varied according to the entrance gate (gate terminal 50) through which the visitor enters the venue. For example, the route search method may be varied depending on whether the entrance gate through which the visitor enters is the entrance gate closest to the seat and whether it is not the entrance gate closest to the seat. For example, when the entrance gate through which the visitor enters is not the entrance gate closest to the seat, based on the adjacent gate information included in the gate position information, first, a route from the entrance gate to an adjacent gate closer to the seat may be set, and then a route from the adjacent gate to the seat position may be searched for. By doing so, even when a visitor enters the venue from an entrance gate other than the entrance gate closest to the seat, the visitor can be suitably guided to the seat.

[0067] Then, the processor 11 transmits the route information generated in step S107 to the corresponding visitor terminal 40 (step S108), and ends the processing at the time of receiving ticket information. Note that information regarding the visitor terminal 40 that is the transmission destination of the route information may be specified based on the user ID included in the ticket authentication request. For example, the information of the visitor terminal 40 may be separately stored in association with the user ID.

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

[0069] By executing the process of receiving ticket information as described above, in the server 10, it is possible to generate route information from the position of the gate terminal 50 where the entrant entered to the seat position, and provide the route information to the entrant terminal 40. Thereby, the entrant can be suitably guided to the seat.

[0070] Subsequently, a display example in the electronic ticket management system 100 of the present embodiment will be described. Here, a display example will be described when a display related to the ticket application is displayed on the screen of a smartphone as the entrant terminal 40.

[0071] In this embodiment, an example will be described where the event is a baseball game and the event venue is a baseball stadium. The event may be a live event, other sports events, a fireworks display, etc. The event venue may be an arena, an amphitheater, an outdoor venue, etc. Note that the present embodiment is applicable not only to event venues but also to facilities where seats are assigned to each user.

[0072] FIG. 9(A) shows the top screen of the ticket application. When the user performs an operation to start the ticket application on the entrant terminal 40, the top screen of the ticket application shown in FIG. 9(A) is displayed. On this top screen of the ticket application, items (buttons, icons) such as "Purchase Ticket", "Display Ticket", "Import Ticket", and "Transfer Ticket" are displayed. Other items may also be included.

[0073] In FIG. 9(A), when "Purchase Ticket" is selected, for example, the screen transitions to a screen for purchasing tickets by selecting the event name, date and time, seat type, number of tickets, etc. When "Import Ticket" is selected, for example, by entering the number of a paper ticket, reading the code written on the paper ticket, or taking a photo of the paper ticket, the screen transitions to a screen where the information of the paper ticket can be imported into the fan club application. When "Transfer Ticket" is selected, for example, the screen transitions to a screen where the owned tickets can be transferred by specifying the user name, etc.

[0074] Also, in FIG. 9(A), when "Display Ticket" is selected, if there are tickets for the current day, as shown in FIG. 9(B), the ticket information for the current day and the electronic ticket including the ticket code are displayed. Also, if there are no tickets for the current day but there are tickets for pre-event events, as shown in FIG. 9(C), a list of the outlines of the tickets for pre-event events is displayed. In the ticket list, when one ticket is selected, the details of the ticket and the electronic ticket may be displayed.

[0075] Also, although not shown in the figure, if there are no tickets for the current day, the ticket information of neighboring events held on the current day or in the near future in the vicinity of the current location (contents of the event, date and time of the event, venue, link for purchasing tickets, etc.) is also displayed.

[0076] When the electronic ticket is held up to the gate terminal 50 and enters the venue with the electronic ticket displayed on the attendee terminal 40 as shown in FIG. 9(B), as shown in FIG. 9(D), the route information 301 from the position of the gate terminal 50 where the electronic ticket is held up (the position of the entrance gate where entry is made) to the seat is displayed on the screen of the attendee terminal 40. On the screen shown in FIG. 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 overall map button 311, a close button 312, etc. In FIG. 9(D), the venue map 302 is a partial map of the venue including the entrance gate and the seats that are the destination positions. On the venue map 302, an entrance gate (gate g2 in FIG. 9(D)), the seats that are the destination positions (seat s2xx in FIG. 9(D)), and a route (line) 303 from the entrance gate to the seats are displayed. The route 303 is a route that passes through the concourse under the auditorium from gate g2, enters the auditorium from entrance e2, and reaches seat s2xx by taking the main passage, staircase p221, and passage p211. By displaying such route information 301 on the entrant terminal 40 used for entering the venue, the entrants can be suitably guided to the target position.

[0078] Note that the route information 301 shown in FIG. 9(D) is an example, and the route information presented on the entrant terminal 40 may be information indicating a route from at least the gate position where the gate terminal 50 used by the entrant for entry is arranged to the target position (seat position) according to the ticket information. In order to prevent the entrant from walking while looking at the screen of the entrant terminal 40, it is preferable that the route information simply presents the route. Also, the route information is not limited to outputting an image showing the route, and instead of or in addition to the output of the image, it may be information indicating the route by means of sound, vibration, etc.

[0079] Also, when the overall map button 311 in FIG. 9(D) is operated by the entrant, the venue map 302 switches to the overall map of the venue. Even in the overall map, it is sufficient if a route from the entrance gate to the seat position is shown. When the close button 312 in FIG. 9(D) is operated by the entrant, the route information 301 closes and switches, for example, to the electronic ticket screen shown in FIG. 9(B). At this time, it may be configured to transmit to the server 10 that the route information 301 has been closed. Thereby, on the server 10 side, it can be determined whether the route information 301 is being displayed on the entrant terminal 40, that is, whether the entrant is viewing the route information 301 and whether the entrant is in the process of moving along the route.

[0080] Note that since the attendees are assumed to use the shops and toilets at the venue, the shop locations and toilet locations may be marked up on the venue map 302 and the overall map shown in FIG. 9(D). Alternatively, the shop locations and toilet locations may be displayed by a predetermined operation.

[0081] Note that when the conditions in FIGS. 9(B) and 9(C) overlap, the two displays may be shown simultaneously or sequentially. Alternatively, the two displays may be shown in a superimposed manner. By doing so, when there are tickets for the event on the day and tickets for the pre-event, displays and processes according to the ownership status can be performed.

[0082] Also, when there are tickets for the pre-event, as shown in FIG. 9(C), a summary list of the pre-event tickets has been displayed, but the details of the pre-event tickets or the electronic tickets may be displayed.

[0083] (Modification example) Note that the present invention is not limited to the above-described embodiments, and various modifications and applications are possible. For example, partial omission, replacement, addition of any configuration, etc. of the above-described embodiments are possible.

[0084] In the above-described embodiment, the server 10 provides the path information from the server 10 to the seat to the attendee terminal 40 with the electronic ticket held up at the gate terminal 50. However, the server 10 may provide the path information to the gate terminal 50 that has acquired the electronic ticket. Then, the gate terminal 50 that has received the path information may notify the attendee terminal 40 with the electronic ticket held up of the path information by wireless communication or the like. That is, the server 10 may indirectly provide the path information to the attendee terminal 40. By doing so, even when the installation position of the gate terminal 50 has poor radio waves and the attendee terminal 40 cannot connect to the communication network 30, the path information can be received via the gate terminal 50, so that the attendee can be suitably guided to the target position.

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

[0086] In a predetermined venue, when a single gate terminal 50 reads an electronic ticket displayed on a single attendee terminal 40 and provides route information to the single attendee terminal 40, the single attendee terminal 40 may or may not cause the gate terminal 50 to read the electronic ticket again. By doing so, it is possible to prevent the same route information from being transmitted to the same attendee terminal 40 multiple times. For example, when an attendee re-enters the venue, it is possible to prevent the attendee from being bothered by transmitting the route information again even though the seat position has already been grasped.

[0087] In the above embodiment, when a ticket display operation is detected, the attendee terminal 40 (ticket application) is configured to display different information depending on the holding date and time of the ticket owned by the user. That is, if there is a ticket for the current day, the electronic ticket of that ticket is displayed, and if there is no ticket for the current day, a list of tickets for pre-event events or ticket information for nearby events is displayed. Such a function is not essential. For example, when the attendee terminal 40 detects a ticket display operation, if there is a ticket for the current day, the electronic ticket of that ticket may be displayed, and if there is no ticket for the current day, a message indicating that there is no ticket for the current day may be displayed.

[0088] In addition, when the electronic ticket management system 100 presents a route to one visitor terminal and then presents a route to another visitor terminal, it does not necessarily have to present a route that avoids the route presented to the one visitor terminal. For example, the electronic ticket management system 100 may provide and present a route to another visitor terminal without referring to the route presented to the one visitor terminal. In this case, the server 10 may always provide the shortest route from the entrance gate to the target position to the visitor terminal 40, or may determine the route to be provided to the visitor based on other information such as the time zone, the sales status of tickets on the day, and the number of visitors already admitted.

[0089] In the above embodiment, the case where the server 10 has the function of the providing unit 101 has been described, but the gate terminal 50 may have the function of the providing unit 101. That is, the electronic ticket management system 100 may be realized by the visitor terminal 40 and the gate terminal 50.

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

[0091] In the above embodiment, the case of presenting route information from the gate terminal 50 to the seat position has been described. However, in the event venue, when it is necessary to pass through a plurality of gates from the entrance of the event venue to the seat position, the content of the route information provided to the visitor terminal 40 may be changed depending on whether the visitor terminal 40 communicates with a gate terminal 50 far from the seat or with the gate terminal 50 closest to the seat. For example, when the visitor terminal 40 communicates with a gate terminal 50 different from the gate terminal 50 closest to the seat, the server 10 may generate information indicating only the direction of the next closest gate terminal 50 (for example, an arrow display) as the route information. Also, when the visitor terminal 40 communicates with the gate terminal 50 closest to the seat, the server 10 may generate route information from the communicated gate terminal 50 to the seat position.

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

[0093] The server 10 can be realized using a normal computer without using a dedicated device. For example, by installing the program from a recording medium storing the program for executing the above-described functions in the computer, a server 10 that executes the above-described processing may be configured. Also, one server 10 may be configured by a plurality of computers operating in cooperation.

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

[0095] Also, when a part of the above-described functions is provided by an OS (Operation System), the part other than the functions provided by the OS may be provided by a program.

[0096] The embodiments described above are for facilitating the understanding of the present invention and are not for limiting and interpreting the present invention. The flowcharts, sequences, each element 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 appropriately changed. Also, it is possible to partially replace or combine the configurations shown in different embodiments.

[0097] (The invention realized by this embodiment) As described above, this embodiment realizes the invention listed below.

[0098] (Appendix 1) An electronic ticket management system including an attendee terminal and a gate terminal, wherein the attendee terminal includes an output unit that outputs ticket information related to a ticket, the gate terminal includes an acquisition unit that acquires the ticket information output from the attendee terminal, in the electronic ticket management system, a provision unit that provides the attendee terminal with route information, which is information based on a route from a gate position where the gate terminal that has acquired the ticket information is arranged to a target position associated with the ticket information, the attendee terminal includes a presentation unit that presents the route information provided from the provision unit Electronic ticket management system.

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

[0100] (Appendix 3) When the presentation unit presents a route to one attendee terminal and then presents a route to another attendee terminal while the route presented to the one attendee terminal is being displayed, the presentation unit presents a route that avoids the route presented to the one attendee terminal. The electronic ticket management system according to Appendix 1.

[0101] (Appendix 4) When the attendee terminal receives a predetermined ticket display operation when there are a plurality of tickets corresponding to the attendee terminal, if the current time corresponds to the entry time of any of the plurality of tickets corresponding to the attendee terminal, the attendee terminal displays the ticket information related to the ticket corresponding to the entry time, and if the current time does not correspond to the entry time of the plurality of tickets corresponding to the attendee terminal, the attendee terminal displays a list of the tickets corresponding to the attendee terminal. The electronic ticket management system described in Supplementary Note 1.

[0102] (Supplementary Note 5) When the ticket display operation is received by the entrant terminal, if the current time does not correspond to the entry time of any ticket corresponding to the entrant terminal, the position information of the entrant terminal is acquired, tickets of the venue that can be reached within the entry time are searched from the position information, and information regarding the searched tickets is displayed. The electronic ticket management system according to any one of Supplementary Notes 1 to 4.

[0103] (Supplementary Note 6) An electronic ticket management method in an electronic ticket management system including an entrant terminal and a gate terminal, wherein the entrant terminal outputs ticket information related to a ticket, the gate terminal acquires the ticket information output from the entrant terminal, the electronic ticket management system provides the entrant terminal with route information, which is information based on a route from the gate position where the gate terminal that has acquired the ticket information is arranged to a target position associated with the ticket information, and the entrant terminal presents the route information. Electronic ticket management method.

[0104] (Supplementary Note 7) Output ticket information related to a ticket to a gate terminal, receive route information, which is information based on a route from the gate position where the gate terminal that has acquired the ticket information is arranged to a target position associated with the ticket information, and present the received route information. Entrant terminal.

[0105] (Supplementary Note 8) Acquire the ticket information output from the entrant terminal to the gate terminal from the gate terminal, Provide the route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is located to the target position associated with the ticket information, to the visitor terminal. Server.

[0106] (Appendix 9) A program that causes a computer to Output ticket information related to a ticket to a gate terminal, Receive route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is located to the target position associated with the ticket information, And present the received route information Function as a visitor terminal.

[0107] (Appendix 10) A program that causes a computer to Acquire the ticket information output from the visitor terminal to the gate terminal from the gate terminal, And provide the route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is located to the target position associated with the ticket information, to the visitor terminal. Function 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, a visitor terminal, a server, and a program that can suitably guide a visitor to a target position.

Explanation of Signs

[0109] 10 Server 30 Communication Network 40 Visitor Terminal 50 Gate Terminal 11, 41 Processor 12, 42 Storage Device 13, 43 Communication Interface 14, 44 Input Device 15. 45 Output Device 100 Electronic Ticket Management System 101 Provision Department 401 Output Unit 402 Presentation Unit 501 Acquisition Unit

Claims

1. An electronic ticket management system including an attendee terminal and a gate terminal, wherein the attendee terminal includes an output unit that outputs ticket information related to a ticket, the gate terminal includes an acquisition unit that acquires the ticket information output from the attendee terminal, in the electronic ticket management system, a provision unit that provides the attendee terminal with route information, which is information based on a route from a gate position where the gate terminal that has acquired the ticket information is arranged to a target position associated with the ticket information, and the attendee terminal includes a presentation unit that presents the route information provided by the provision unit. Electronic ticket management system.

2. When the presentation unit presents a route to one attendee terminal and then presents a route to another attendee terminal within a predetermined time, the presentation unit presents a route that avoids the route presented to the one attendee terminal. The electronic ticket management system according to claim 1.

3. When the presentation unit presents a route to one attendee terminal and then presents a route to another attendee terminal while the route presented to the one attendee terminal is being displayed, the presentation unit presents a route that avoids the route presented to the one attendee terminal. The electronic ticket management system according to claim 1.

4. When the attendee terminal receives a predetermined ticket display operation and there are multiple tickets corresponding to the attendee terminal, if the current time corresponds to the entry time of any of the multiple tickets corresponding to the attendee terminal, the attendee terminal displays the ticket information related to the ticket corresponding to the entry time, and if the current time does not correspond to the entry time of any of the multiple tickets corresponding to the attendee terminal, the attendee terminal displays a list of tickets corresponding to the attendee terminal. The electronic ticket management system according to claim 1.

5. When the attendee terminal receives a predetermined ticket display operation and the current time does not correspond to the entry time of any of the tickets corresponding to the attendee terminal, the attendee terminal acquires the position information of the attendee terminal, searches for tickets of the venue that can be reached within the entry time from the position information, and displays information related to the searched tickets. The electronic ticket management system according to any one of claims 1 to 4.

6. An electronic ticket management method in an electronic ticket management system including an attendee terminal and a gate terminal, wherein the attendee terminal outputs ticket information related to a ticket, The gate terminal acquires the ticket information output from the visitor terminal, The electronic ticket management system provides the visitor terminal with route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is arranged to the target position associated with the ticket information. The visitor terminal presents the route information. Electronic ticket management method.

7. Output ticket information related to the ticket to the gate terminal, Receive route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is arranged to the target position associated with the ticket information, Present the received route information. Visitor terminal.

8. Acquire the ticket information output from the visitor terminal to the gate terminal from the gate terminal, Provide the visitor terminal with route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is arranged to the target position associated with the ticket information. Server.

9. A computer, Output ticket information related to the ticket to the gate terminal, Receive route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is arranged to the target position associated with the ticket information, Present the received route information. Program for functioning as a visitor terminal.

10. A computer, Acquire the ticket information output from the visitor terminal to the gate terminal from the gate terminal, Provide the visitor terminal with route information, which is information based on the route from the gate position where the gate terminal that has acquired the ticket information is arranged to the target position associated with the ticket information. Program for functioning as a server.

Images