Electronic ticket management system and electronic ticket management method

Abstract

To provide an electronic ticket management system or the like capable of suitably recording contents related to a performance in which a user participates by using an electronic ticket.SOLUTION: When a performance in which a participant participated using an electronic ticket held in a terminal 20 ends, a server 10 transmits detailed information including period information related to the period in which the ended performance was held to the terminal 20, and the terminal 20 collects the content associated with the period on the basis of the period information included in detailed information received from the server 10, displays the detailed information on the screen, displays the collected content on the screen as selection candidates. Further when any one of the selection candidates is selected by the participant, the server 10 transmits the information associating the content related to the selected selection candidate with the detailed information to the server 10, and records the association information received from the terminal 20 in association with the detailed information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an electronic ticket management system and an electronic ticket management method. [Background technology]

[0002] An electronic ticket management system has been proposed that can guarantee the ownership history of tickets throughout the various periods before and after a performance (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] Incidentally, when attending a performance using a paper ticket, participants can use the paper ticket to record memories of the performance they attended by, for example, attaching the paper ticket to a scrapbook and writing notes on it.

[0005] Even when attendees attend a performance using an electronic ticket that is not issued as a physical object, it is desirable to be able to record memories of the performance.

[0006] The present invention has been made in consideration of the above-mentioned circumstances, and aims to provide an electronic ticket management system and the like that can suitably record content related to an event in which a user has participated using an electronic ticket. [Means for solving the problem]

[0007] In order to achieve the above object, the electronic ticket management system of the present invention comprises: An electronic ticket management system that includes a server and participating terminals and manages the usage history of electronic tickets, When the event in which the participant participated using the electronic ticket held in the participating terminal has ended, The server Obtain detailed information including period information relating to the period during which the completed event was held; recording the acquired detailed information in association with the event in which the participant participated; Sending the acquired detailed information to the participating terminal; The participating terminals are: receiving detailed information sent from the server; Collecting content associated with a period based on period information included in the received detailed information; displaying the received detailed information on a screen and displaying the collected content on the screen as selection candidates; When the participant selects one of the selection candidates, linking information linking the content related to the selected selection candidate to the detailed information is transmitted to the server; The server receiving the linking information transmitted from the participating terminal; The received linking information is linked to the detailed information and recorded. [Effects of the Invention]

[0008] According to the present invention, it is possible to preferably record content relating to a performance in which a participant has attended using an electronic ticket. [Brief explanation of the drawings]

[0009] [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] FIG. 10 is a diagram showing an example of the configuration of an electronic ticket history. [Figure 3] 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 4] 10 is a flowchart showing an example of an electronic ticket history recording process. [Figure 5] 10 is a flowchart showing an example of an electronic ticket history viewing process. [Figure 6] 10A to 10C are diagrams showing examples of displays on a terminal. [Figure 7] 10A and 10B are diagrams showing examples of displays on a terminal. DETAILED DESCRIPTION OF THE INVENTION

[0010] 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.

[0011] 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 comprises a server 10 and a terminal 20. The server 10 and the terminal 20 are connected via a communication network such as the Internet or a mobile communication network.

[0012] The electronic ticket management system 100 according to this embodiment is a system that manages electronic tickets, which are electronic tickets for participating in a performance (event).

[0013] The server 10 is a high-performance information processing device having one or more storage devices and one or more control units such as CPUs (Central Processing Units). 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.

[0014] For example, in response to a request from the terminal 20 based on a user's operation, the server 10 performs processes such as selling electronic tickets to users, providing electronic tickets and information about electronic tickets to the terminal 20, and performing authentication processes when entering a performance venue using an electronic ticket. Furthermore, for example, the server 10 provides a ticket app, which is an application that has functions such as purchasing electronic tickets and displaying the electronic tickets at the performance venue. The server 10 provides services according to each function of the ticket app.

[0015] The terminal 20 is an information processing device such as a smartphone or tablet that can be carried by a user. For example, a ticket app provided by the server 10 can be installed on the terminal 20. The terminal 20 accesses the server 10 based on the installed ticket app or user operation on a web browser. The terminal 20 then displays the electronic ticket and ticket-related information acquired from the server 10 on the display screen. 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 corresponds to the electronic ticket. In a narrow sense, the ticket code displayed on the terminal 20 is also referred to as the electronic ticket. Note that although one terminal 20 is shown in FIG. 1, any number of terminals 20 may be used.

[0016] The ticket app may also have functions such as providing information about events related to the target the user supports, broadcasting live events, broadcasting recorded events, displaying messages from the target, displaying the performance and achievements of the target, allowing fans using the app to interact with each other, and purchasing merchandise online.The ticket app may also output information about the route from a predetermined location (for example, the entrance gate of the performance venue) to the seat location of the event the user is attending.

[0017] Furthermore, for example, the server 10 performs ticket authentication by determining whether or not the electronic ticket corresponding to the electronic ticket information received from a gate terminal (not shown) installed at the gate of the performance venue is valid, and transmits the authentication result to the gate terminal, thereby enabling the gate terminal to confirm the validity of the presented electronic ticket.

[0018] The electronic ticket management system 100 of this embodiment also manages the usage history of electronic tickets. Specifically, the server 10 records the usage history of electronic tickets that a user has used in the past, as well as detailed information about the events that the user has attended using those electronic tickets and content related to those events, in association with each other.

[0019] When attending a performance using a paper ticket, the attendee can record memories of the performance they attended using the paper ticket by attaching the paper ticket to a scrapbook and writing notes on it, etc. In the electronic ticket management system 100 of this embodiment, even when attending a performance using an electronic ticket, the user can record content related to the performance as memories of the performance they attended.

[0020] The detailed information and content recorded in this way in association with each user's electronic ticket usage history can be referenced and viewed by the user at any time thereafter from any terminal by accessing the server 10. Therefore, according to the electronic ticket management system 100 of this embodiment, even if the user changes terminal 20, the detailed information about the event and content related to the event recorded on the server 10 can be viewed from a terminal other than the terminal 20 on which the electronic ticket was used, allowing the user to recall memories related to the event.

[0021] In this embodiment, the content recorded in association with the electronic ticket usage history for each user is also referred to as association information. The object to which association information is associated may be an electronic ticket, a performance, or their identification information. Among the terminals, the terminal 20 used when participating in a performance using an electronic ticket is also referred to as a participation terminal. The terminal 20 used to view the association information recorded in the server 10 is also referred to as a viewing terminal. The viewing terminal may be the same as the participation terminal, or the viewing terminal may be another information processing device such as a PC.

[0022] Next, we will explain the functional configuration of the electronic ticket management system 100. First, we will explain the functional configuration of the server 10. The server 10 includes an electronic ticket management unit 101, a performance detail information acquisition unit 102, a detail information transmission unit 103, a linking information reception unit 104, a view request reception unit 105, a view response transmission unit 106, and a database (DB) 110.

[0023] The electronic ticket management unit 101 performs overall management of electronic tickets for events. The electronic ticket management unit 101 holds information about electronic tickets provided by the server 10 and detailed information about events corresponding to the electronic tickets. The database 110 may store information about electronic tickets and detailed information about events corresponding to the electronic tickets. In this case, the electronic ticket management unit 101 obtains this information from the DB 110. The electronic ticket management unit 101 issues an electronic ticket after user authentication processing, payment processing, etc., based on an electronic ticket acquisition request based on a user's electronic ticket purchase operation on the terminal 20. The issued electronic ticket information is associated with user information and stored in the DB 110 as an electronic ticket owned by the user. The electronic ticket management unit 101 also transmits data of the issued electronic ticket to the terminal 20 that has made the electronic ticket acquisition request. For example, the electronic ticket management unit 101 also performs electronic ticket authentication processing based on electronic ticket information received from a gate terminal installed at the gate of the event venue.

[0024] When an event corresponding to an electronic ticket issued by the electronic ticket management unit 101 has ended, the event detail information acquisition unit 102 acquires detailed information about the event from the electronic ticket management unit 101. The detailed information includes period information indicating the period during which the event was held, location information indicating the location where the event was held, information indicating the content of the event, and the like. The event detail information acquisition unit 102 records the acquired detailed information in the DB 110 in association with the event corresponding to the electronic ticket. This makes it possible to refer to the duration of each event, for example. The period information is a period based on the start time or opening time of the event and the scheduled end time or the actual end time of the event. The server 10 may also acquire the actual end time of the event by accessing an external device that manages the implementation status of the event.

[0025] The detailed information sending unit 103 transmits the detailed information acquired by the event detailed information acquiring unit 102 to the terminals 20 of all users who possess an electronic ticket for the corresponding event. That is, when an event in which a user (participant) participated using an electronic ticket at least temporarily held in the terminal 20 (participant terminal) ends, the server 10 acquires detailed information including period information relating to the period during which the ended event was held, records the acquired detailed information in the DB 110 in association with the event in which the participant participated, and transmits the acquired detailed information to the terminal 20. Note that the server 10 is not limited to recording the detailed information in the DB 110 upon the end of an event, and may also store the detailed information in the DB 110 in advance in association with the event.

[0026] The linking information receiving unit 104 receives linking information from the terminal 20 and records the received linking information by linking it to the corresponding event (detailed information). The linking information is information indicating that content is linked to an event that the user attended using an electronic ticket, and includes data on the linked content (images, text, etc.), a link to the content, and a URL (Uniform Resource Locator). In this way, the electronic ticket management system 100 of this embodiment can record content selected by the user on the terminal 20 by linking it to the event that the user attended using the electronic ticket as memory data for the corresponding event or electronic ticket.

[0027] The viewing request receiving unit 105 receives, from the terminal 20 (viewing terminal), a viewing request for information about an event that the user attended using an electronic ticket. The viewing response sending unit 106 acquires, from the database 110, detailed information and associated information associated with the event corresponding to the viewing request received by the viewing request receiving unit 105, and transmits the information as a viewing response to the terminal 20 that sent the viewing request. If the acquired detailed information is not associated with associated information and recorded, the viewing response sending unit 106 includes the detailed information in the viewing response and transmits it to the terminal 20. If the acquired detailed information is associated with associated information and recorded, the viewing response sending unit 106 includes the detailed information and associated information in the viewing response and transmits it to the terminal 20. Note that since the associated information is recorded based on the user's selection operation of a selection candidate, there are cases where the associated information is not recorded in the database 110. In this case, the viewing response sending unit 106 includes only the detailed information in the viewing response and transmits it to the terminal 20.

[0028] The database 110 stores various information related to electronic tickets. For example, the database 110 stores information about electronic tickets (such as ticket type, number of tickets, usable date and time, and seat information) held by each user of the electronic ticket management system 100. The database 110 also stores, for example, an electronic ticket history for each user of the electronic ticket management system 100. FIG. 2 is a diagram showing an example of the configuration of the electronic ticket history. The electronic ticket history is information indicating a user's electronic ticket usage history, etc. The electronic ticket history is information that associates, for example, a user ID that identifies a user, an electronic ticket ID that identifies an electronic ticket held by the user, a performance ID (such as a performance name or event name) that identifies a performance corresponding to the electronic ticket, detailed information that indicates the details of the performance, and associated information (content) linked to the performance or the detailed information. Each piece of information in the electronic ticket history is recorded for each electronic ticket held by a user. The electronic ticket ID and performance ID are recorded by the electronic ticket management unit 101, for example, when the user acquires an electronic ticket. The detailed performance information acquisition unit 102 records the detailed performance information. The linking information is recorded by the linking information receiving unit 104. Note that other information may be associated with the electronic ticket history.

[0029] Next, a description will be given of the functional configuration of the terminal 20. The terminal 20 includes an electronic ticket receiving unit 201, an electronic ticket display unit 202, a detailed information receiving unit 203, a content collecting unit 204, a selection candidate display unit 205, an associated information transmitting unit 206, a selection operation receiving unit 207, an associated information input unit 208, a viewing request transmitting unit 209, a viewing response receiving unit 210, and a performance information display unit 211.

[0030] The electronic ticket receiving unit 201 transmits an electronic ticket acquisition request to the server 10 in response to a user operation or the like, and receives the corresponding electronic ticket data. This allows the user to hold the electronic ticket in the terminal 20. The electronic ticket display unit 202 displays an electronic ticket corresponding to the electronic ticket data received by the electronic ticket receiving unit 201 on the screen of the terminal 20. The user can enter the venue of the event by, for example, holding the electronic ticket displayed on the screen of the terminal 20 over a gate terminal at the venue of the event.

[0031] Furthermore, the terminal 20 may be configured to hold the electronic ticket over the gate terminal not only when entering but also when leaving and re-entering after leaving. The terminal 20 may also be configured to hold the electronic ticket over the gate terminal when leaving the performance location (performance venue) after a performance. The gate terminal may then acquire electronic ticket information received from the terminal 20 and transmit the timing of entry and exit and the electronic ticket information to the server 10 or another server, so that the server 10 or another server manages the entry and exit status of the terminal 20. The server 10 may acquire information on the entry and exit status of the performance location (entry and exit information) from the gate terminal or another server and transmit the entry and exit information to the terminal 20 together with the detailed information. This allows the terminal 20 to determine the user's entry and exit timing by referring to the entry and exit information. The entry and exit information includes information identifying the performance, such as a performance ID, information identifying the user, information identifying the type of entry and exit, and the time of entry and exit.

[0032] The detailed information receiving unit 203 receives detailed information transmitted from the detailed information transmitting unit 103 of the server 10. The content collecting unit 204 collects content related to the detailed information received by the detailed information receiving unit 203. For example, the content collecting unit 204 collects content associated with a period based on period information included in the detailed information received by the detailed information receiving unit 203 from within the terminal 20 or the Internet. For example, the content collecting unit 204 collects content associated with a time point included in the period information or close to the period (for example, several hours before or after) from within the terminal 20 or the Internet. In other words, the content collecting unit 204 collects content associated with a period based on the period information included in the detailed information. In addition, the content collecting unit 204 collects content associated with a location close to a location related to location information included in the detailed information received by the detailed information receiving unit 203 (for example, a location within a predetermined distance from a performance venue). The collected content may be, for example, photos in the camera roll of the terminal 20, article texts and photos posted by the user to a social networking service (SNS) and their URLs, web search results (news, articles, etc. about the event) using search terms such as the name of the corresponding event, etc. For example, by linking the user's SNS account to the ticket app, the content collection unit 204 can refer to the user's SNS based on the link information and search for content. The content collection unit 204 may search for content from the period from when the terminal 20 holds up the gate terminal to enter the event venue to when it leaves the event venue, or a period before or after that, within the period based on the period information included in the detailed information. By referring to the entrance / exit information included in the detailed information, the content collection unit 204 can search for content not only from when the terminal 20 holds up the gate terminal to enter the event venue to when it leaves the event venue, but also from a period before or after that. This allows the content collection unit 204 to search for content created immediately before entering the event venue or immediately after leaving the event venue.Furthermore, the content collection unit 204 may refer to the entrance / exit information included in the detailed information to distinguish between content corresponding to the inside of the performance venue (such as content relating to the period when the terminal 20 was located inside the performance venue) and content corresponding to the outside of the performance venue (such as content relating to the period when the terminal 20 was located outside the performance venue). The period when the terminal 20 was located inside the performance venue refers to the period from when the user holds the terminal 20 over the gate terminal to enter or re-enter, to when the user holds the terminal 20 over the gate terminal to exit, or when a predetermined period has elapsed since the end of the performance. The period when the terminal 20 was located outside the performance venue refers to the predetermined period immediately before the user holds the terminal 20 over the gate terminal to enter for the first time (for example, one hour before the first entry), the period from when the user leaves until when the user re-enters, the predetermined period after the end of the performance, etc.

[0033] The selection candidate display unit 205 displays the detailed information received by the detailed information receiving unit 203 on the screen, and also displays the content collected by the content collecting unit 204 as selection candidates on the screen of the terminal 20. These selection candidates are content that the user will want to keep as memories of the performance. The selection candidate display unit 205 may display the selection candidates without displaying the detailed information. For example, the selection candidate display unit 205 may display the performance name and the selection candidates. The selection candidate display unit 205 may also display, on the screen, content that was located within the performance venue and content that was located outside the performance venue, based on entrance and exit information, in a distinguished manner. The selection candidate display unit 205 may also highlight either the content that was located within the performance venue or the content that was located outside the performance venue.

[0034] The selection operation receiving unit 207 receives a user's selection operation for the selection candidates displayed by the selection candidate display unit 205. When the user selects one of the selection candidates displayed by the selection candidate display unit 205, the linking information transmitting unit 206 transmits linking information linking the content related to the selected selection candidate to the detailed information to the server 10. Note that it is sufficient if one or more selection candidates can be selected.

[0035] The linking information input unit 208 accepts input of linking information indicating content (text, photo data, etc.) linked to a specific performance (electronic ticket) by the user at any time. The linking information transmission unit 206 also transmits the linking information input by the linking information input unit 208 to the server 10. In this way, the user can manually input content to be kept as a memento of the performance. Note that the linking information input unit 208 may be omitted.

[0036] Based on the user's instructions, the viewing request sending unit 209 sends to the server 10 a viewing request for information about an event that the user attended using an electronic ticket. The viewing response receiving unit 210 receives a viewing response as a response to the viewing request. The viewing response includes detailed information and linking information. The event information display unit 211 displays the detailed information, or the detailed information and linking information, corresponding to the viewing response received by the viewing response receiving unit 210 on the screen of the terminal 20.

[0037] In this way, in the electronic ticket management system 100, when a performance that a participant attended using an electronic ticket has ended, detailed information about the performance is transmitted to the terminal 20, and content corresponding to the detailed information is collected and presented to the user as a selection of content to be recorded. This allows the user to easily select content to keep as a memory. Then, linking information for linking the content selected in accordance with this or content arbitrarily entered by the user to the performance and detailed information is transmitted to the server 10. The linking information is then recorded in the performance and detailed information, i.e., the user's electronic ticket history. As a result, the user can subsequently access the server 10 and view memorable content related to performances they have attended in the past on the terminal 20, etc.

[0038] 1 is merely an example, and some components may be omitted or integrated as long as the functions of the present invention can be realized. Also, other functional components may be added as desired.

[0039] 3 is a diagram showing an example of the hardware configuration of an information processing device constituting the server 10 and the terminal 20. The server 10 has a processor 11 such as a CPU or a GPU (Graphical Processing Unit), a storage device 12 such as a memory, an HDD and / or an SSD, a communication interface 13 for wired or wireless communication, an input device 14 for accepting input operations, and an output device 15 for outputting information. The input device 14 is, for example, a keyboard, a touch panel, a mouse and / or a microphone, etc. The output device 15 is, for example, a display and / or a speaker, etc. The processor 11 reads a program stored in the storage device 12, thereby functioning as each functional unit of the server 10 shown in FIG. 1. Furthermore, a DB 110 is configured by the storage device 12.

[0040] Similarly, the terminal 20 has a processor 21, a storage device 22, a communication interface 23, an input device 24, and an output device 25. The processor 21 reads a program stored in the storage device 22, thereby functioning as each functional unit of the terminal 20 shown in Fig. 1. Note that unnecessary components in the server 10 and the terminal 20 may be omitted as appropriate, and other components may be added.

[0041] Next, the operation of the electronic ticket management system 100 will be described. Fig. 4 is a flowchart showing an example of electronic ticket history recording processing in the server 10 and the terminal 20. The electronic ticket history recording processing on the server 10 side is executed, for example, by the processor 11 of the server 10 reading a program stored in the storage device 12. Furthermore, the electronic ticket history recording processing on the terminal 20 side is executed, for example, by the processor 21 of the terminal 20 reading a program stored in the storage device 22.

[0042] The processor 11 of the server 10 executes an electronic ticket history recording process, for example, at predetermined intervals. In the electronic ticket history recording process on the server 10 side, the processor 11 first determines whether a certain event has ended (step S101). For example, the server 10 refers to the event period for each event for which it provided an electronic ticket, and if there is an event whose event period ended the previous day, it determines that the event has ended. Note that in the case of an event of a sports game such as baseball, the server 10 may access an external server or the like to obtain information on the status of the event and determine that the game has ended.

[0043] If it is determined that a certain event has ended (step S101; Yes), processor 11 acquires detailed information about the event (step S102). Processor 11 then records the acquired detailed information in DB 110 (step S103) and transmits the detailed information to terminals 20 of all participants who participated in the event using electronic tickets (step S104).

[0044] In the electronic ticket history recording process on the terminal 20 side, the processor 21 determines whether or not detailed information about a performance that has finished and that was attended with an electronic ticket acquired by the terminal 20 has been received from the server 10 (step S201). If detailed information has not been received (step S201; No), the electronic ticket history recording process on the terminal 20 side is terminated.

[0045] When the detailed information is received (step S201; Yes), the processor 21 collects content related to the detailed information from the storage device 22 of the terminal 20 or the Internet (step S202). In step S202, as described above, the processor 21 collects content associated with a period based on the period information included in the detailed information, for example, content associated with a time point included in or close to the period related to the period information, and content associated with a location close to a location related to the location information included in the detailed information. Specifically, if the content is to be collected from the storage device 22, the processor 21 references the shooting date and time information and update date and time information of content such as photo data and text data stored in the storage device 22 and collects content that matches the period information included in the detailed information. Furthermore, if the content is photo data or the like and includes location information at the time the content was stored, the processor 21 may collect only content associated with a location close to a location related to the location information included in the detailed information. Furthermore, if the content is to be collected from the Internet, the processor 21 performs a search by show name on a search engine, SNS, or the like, and collects content whose update date and posting date and time match the period information included in the detailed information. When searching SNS, you can search only the user's posts, or you can search other people's posts, or posts in which the user has taken action such as mentioning or quoting. When collecting content from the Internet, you can collect the URL of the link destination, or you can collect image data of a hard copy of the screen.

[0046] The processor 21 then displays the content collected in step S202, along with the detailed information, on the screen of the terminal 20 as content selection candidates to be recorded as memories of the performance (step S203). For example, the detailed information and selection candidates may be displayed on a ticket app installed on the terminal 20. At this time, the user may be notified via the ticket app that detailed information about the performance has been received from the server 10 as the performance has ended. The selection candidates may be displayed as image or text thumbnails, for example. The number of selection candidates to be displayed may be any number, and all or a portion of the collected content may be displayed. Furthermore, content that highly matches the period information and location information included in the detailed information may be displayed preferentially. For example, content may be displayed preferentially in order of proximity of location information indicated by the content to the location information included in the detailed information. Displaying content preferentially means, for example, displaying it at the top of the list, displaying it larger, or displaying it in a way that catches the user's eye. In this way, content related to the performance is automatically collected and displayed as selection candidates as the performance has ended, allowing the user to easily select content they want to keep as a memory.

[0047] Next, processor 21 waits for a user operation and determines whether any of the content candidates for selection displayed on the screen has been selected (step S204). Note that one or more content candidates for selection may be selected. If no content candidate for selection is selected (step S204; No), for example, if none of the content candidates for selection is selected and the screen is closed or an end operation is performed, the electronic ticket history recording process on terminal 20 is terminated. Note that even if the user does not select a content candidate for selection, it may be possible to select a previously presented content candidate and record the selected content in server 10 by later starting the ticket app, for example. In other words, it may be possible for the user to postpone the selection of a content candidate for selection.

[0048] If a content candidate for selection is selected (step S204; Yes), processor 21 transmits linking information to server 10 for linking the selected content to detailed information (electronic ticket history) (step S205). The transmitted linking information includes the user ID of the user of terminal 20, information for identifying the linking destination (electronic ticket ID and event ID), and information related to the content to be linked. The information related to the content includes, for example, photo data if the content is a photo, or the URL of the post or hard copy data if the content is a post to an SNS. After that, processor 21 terminates the electronic ticket history recording process on terminal 20 side.

[0049] After transmitting the detailed information in step S104, or when it is determined that a certain performance has not ended (step S101; No), processor 11 of server 10 determines whether or not it has received linking information from terminal 20 (step S105). If it has not received linking information (step S105; No), the electronic ticket history recording process on the server 10 side is terminated.

[0050] If the linking information is received (step S105; Yes), the processor 11 links the information about the content included in the linking information to the electronic ticket history of the corresponding event of the corresponding user, thereby recording the linking information in the DB 110 (step S106). After that, the electronic ticket history recording process on the server 10 side is terminated.

[0051] By the electronic ticket history recording process described above, content relating to a performance that a user has attended using an electronic ticket can be recorded in the server 10 in association with the electronic ticket history.

[0052] 5 is a flowchart showing an example of the electronic ticket history viewing process in the server 10 and the terminal 20. The electronic ticket history viewing process on the server 10 side is executed, for example, by the processor 11 of the server 10 reading a program stored in the storage device 12. The electronic ticket history viewing process on the terminal 20 side is executed, for example, by the processor 21 of the terminal 20 reading a program stored in the storage device 22. Note that the terminal 20 that executes the electronic ticket history viewing process (the viewing terminal that views the electronic ticket history) may be the same as or different from the participation terminal used when participating in the event using the electronic ticket.

[0053] In the electronic ticket history viewing process on the terminal 20 side, the processor 21 of the terminal 20 first determines whether or not an operation to view the history of events in which the user of the terminal 20 has attended (electronic ticket history) has been detected (step S221). The operation to view the electronic ticket history may be, for example, a viewing operation in which a ticket app is launched on the terminal 20 and a specific electronic ticket or event is designated in the ticket app. If an operation to view the electronic ticket history has not been detected (step S221; No), the electronic ticket history viewing process on the terminal 20 side is terminated.

[0054] If an operation to view the electronic ticket history is detected (step S221; Yes), the processor 21 sends a request to view the electronic ticket history to the server 10 (step S222). The request to view the electronic ticket history includes, for example, the user ID of the user of the terminal 20 and information for identifying the event (electronic ticket ID and event ID).

[0055] In the electronic ticket history viewing process on the server 10 side, the processor 11 of the server 10 determines whether or not a request to view the electronic ticket history has been received from the terminal 20 (step S121). If a request to view the electronic ticket history has not been received (step S121; No), the electronic ticket history viewing process on the server 10 side is terminated.

[0056] When a request to view the electronic ticket history is received (step S121; Yes), the processor 11 searches the DB 110 based on the user ID, electronic ticket ID, etc. included in the view request, and obtains the electronic ticket history corresponding to the view request (step S122).

[0057] Then, the processor 11 determines whether or not the acquired electronic ticket history contains linking information, i.e., whether or not the linking information is linked and recorded in the electronic ticket history (detailed information included in the electronic ticket history) (step S123). Note that since the linking information is recorded based on the user's selection operation of a selection candidate, there may be cases where the linking information is not recorded in the electronic ticket history.

[0058] If there is linking information in the electronic ticket history (step S123; Yes), the processor 11 transmits the detailed information of the performance included in the electronic ticket history and the linking information (content data, etc.) to the terminal 20 (step S124).

[0059] If there is no linking information in the electronic ticket history (step S123; No), the processor 11 transmits only the detailed information of the event included in the electronic ticket history to the terminal 20 (step S125). After the processing of step S124 or S125, the electronic ticket history viewing process on the server 10 side ends.

[0060] After transmitting the request to view the electronic ticket history in step S222, the processor 21 of the terminal 20 determines whether or not information related to the electronic ticket history has been received from the server 10 (step S223). If information related to the electronic ticket history has not been received (step S223; No), the processor 21 waits for reception of information related to the electronic ticket history, for example, for a predetermined period of time.

[0061] If information relating to the electronic ticket history has been received (step S223; Yes), the processor 21 displays the received information relating to the electronic ticket history on the screen of the terminal 20 (step S224). In step S224, if detailed information and linking information have been received as information relating to the electronic ticket history, the detailed information and linking information are displayed on the screen. If only detailed information has been received as information relating to the electronic ticket history, the detailed information is displayed on the screen. After the processing of step S224, the electronic ticket history viewing process on the terminal 20 side is terminated.

[0062] The above-described electronic ticket history viewing process allows the user (participant) to view detailed information about a performance that the user previously attended using an electronic ticket held in terminal 20, as well as linked information, which is content that serves as a memory of that performance. Furthermore, the participation terminal used when attending the performance may be different from the viewing terminal used when viewing the detailed information and linked information; for example, even if the user changes participation terminals after attending a performance, the user can review the detailed information and linked information about the performance from another viewing terminal.

[0063] 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 an electronic ticket is displayed on the screen 300 of a smartphone (the screen of a ticket application installed on the smartphone) as the terminal 20.

[0064] In this display example, the event is a baseball event, and content related to the baseball game and the baseball stadium where the event is held is recorded in association with the electronic ticket history, allowing the content to be viewed as a memory of the event. The event may be a live concert, another sporting event, a fireworks display, or another event. The venue for the event may be a stadium, an amphitheater, an outdoor venue, or the like.

[0065] Fig. 6(A) shows the top screen of the ticket app. When a user launches the ticket app on terminal 20, the top screen of the ticket app shown in Fig. 6(A) is displayed. This top screen of the ticket app displays items (buttons, icons) corresponding to various functions of the ticket app, such as "Purchase Ticket," "Display Ticket," "Import Ticket," "Transfer Ticket," and "Past Tickets." Note that the top screen may also include items other than these depending on the functions of the ticket app.

[0066] "Buy tickets" is an option for purchasing new electronic tickets. When a user selects the "Buy tickets" button, they are redirected to a screen where they can purchase tickets by selecting, for example, the event name, date and time, seat type, number of tickets, etc. "Import tickets" is an option for importing paper tickets, etc. into the ticket app. When a user selects the "Import tickets" button, they are redirected to a screen where they can import paper ticket information into the ticket app by, for example, entering the paper ticket number, scanning the code printed on the paper ticket, or photographing the paper ticket. "Transfer tickets" is an option for transferring electronic tickets that the user owns. When a user selects the "Transfer tickets" button, they are redirected to a screen where they can transfer their electronic tickets by, for example, specifying a username, etc.

[0067] "Display ticket" is an option for displaying the electronic ticket possessed by the user. When the user selects the "Display ticket" button 301, if the electronic ticket possessed by the user is for the day, an electronic ticket 303 including the ticket information for the day (seat information, start time, etc.) and a ticket code 304 is displayed, as shown in Fig. 6(B). With the electronic ticket 303 displayed on the terminal 20, the user can enter the venue by holding the ticket code 304 over a gate terminal installed at the venue of the event (in this case, a baseball stadium).

[0068] The display screen of the electronic ticket 303 shown in FIG. 6(B) also includes a memo field 305, allowing the user to input and save any text. By operating a camera icon 306 displayed in the memo field 305, the user can also save newly taken photos or data of photos stored in the terminal 20 in the memo field 305. The memo field 305 and camera icon 306 are examples of the linked information input unit 208 shown in FIG. 1. The content such as text and photos input in this manner is transmitted to the server 10 as linked information, and the server 10 links the received linked information to the event or detailed information corresponding to the electronic ticket 303 and records it in the electronic ticket history.

[0069] Furthermore, when the "Display Tickets" button 301 is selected, if the user does not have an electronic ticket for the day but has an electronic ticket for a performance that has not yet started, a list of tickets held for the performance that has not yet started may be displayed.

[0070] When a performance that the user participated in using the electronic ticket held in terminal 20 ends, detailed information about the performance is sent from server 10 to terminal 20, and terminal 20 collects content associated with the period in the period information included in the detailed information, for example, a time point included in or close to the period related to the period information. Then, terminal 20 displays the detailed information on the screen, and also displays the collected content on the screen as selection candidates.

[0071] After a user watches a baseball game using the electronic ticket shown in Fig. 6(B), when the game ends, the user is notified of the end of the game via, for example, a ticket app, and a content selection screen (memory selection screen) including detailed information 307 of the finished game and options C1 to C6 for selecting content, as shown in Fig. 6(C), is displayed on the screen of the terminal 20. This screen is used by the user to select content to be recorded on the server 10 for the game corresponding to the detailed information 307.

[0072] In Fig. 6(C), detailed information 307 relating to the electronic ticket is displayed by partially modifying the manner in which the electronic ticket is displayed on terminal 20. As an example of partially modifying the manner, ticket code 304 is omitted from electronic ticket 303 shown in Fig. 6(B) and the notation is simplified. In this way, the display data of the electronic ticket can be reused and utilized. It is also easy to understand which electronic ticket the detailed information 307 corresponds to. Note that the example of partially modifying the manner shown in Fig. 6(C) is just one example; for example, a stamp indicating that the electronic ticket has been used may be displayed, or the electronic ticket may be displayed in a manner in which the stub has been torn off, likening it to a paper ticket.

[0073] In FIG. 6(C), content options C1 to C6 are, for example, thumbnails or summaries of the content. Each of the options C1 to C6 is associated with a selection button 308, which can be operated to select the content (option). A scroll button 309 is displayed to the right of the options C1 to C6, and options subsequent to the options C1 to C6 can be viewed by operating the scroll button 309 or swiping the screen. Finally, when an option is selected with the selection button 308 and the confirmation button 310 superimposed on the option is operated, linking information for linking the content corresponding to the selected option to the event or electronic ticket and recording it is transmitted to the server 10. The linking information is then linked and recorded in the electronic ticket history in the server 10. In this way, the electronic ticket management system 100 of this embodiment allows the user to easily select content to keep as a memento of the event.

[0074] In Fig. 6(A), "Past Tickets" is an item for displaying electronic tickets that the user previously owned (such as electronic tickets that the user has already used or whose performance has already ended) and the user's electronic ticket usage history. When the user selects the "Past Tickets" button 302, if there are electronic tickets that the user previously owned, a list of used or completed electronic tickets is displayed, as shown in Fig. 7(A). The list displays, for example, summary information 321 of past electronic tickets together with a "View Memories" button 322 for viewing detailed information and associated information about the electronic tickets.

[0075] In FIG. 7(A), when the user operates the "View Memories" button 322, this operation is performed to view information about the electronic ticket displayed in the electronic ticket summary information 321. Based on this operation, the server 10 transmits detailed information and linking information recorded in the electronic ticket history corresponding to the electronic ticket to the terminal 20. Then, as shown in FIG. 7(B), the terminal 20 displays a screen containing detailed information 323 about the event viewed and contents M1 to M6 corresponding to the linking information linked to the event (detailed information 323). Each of the contents M1 to M6 is, for example, a thumbnail or summary of the content, and can be enlarged by selecting it on the screen. A scroll button 324 is displayed to the right of the contents M1 to M6, and the user can view content subsequent to the contents M1 to M6 while the content is displayed by operating the scroll button 324 or swiping the screen. In this way, the user can rewatch content that is a memory of events they previously attended using an electronic ticket at any time they like.

[0076] 7B, the detailed information 323 relating to the electronic ticket is also displayed by partially modifying the manner in which the electronic ticket is displayed on the terminal 20. In FIG.

[0077] 7(B), content M1 has a larger display size than the other contents M2 to M6. In this way, a priority order may be set for multiple contents recorded as linked information. The display order and display size of the contents may be varied depending on the priority order. The priority order may be set by the user, or may be automatically set by the electronic ticket management system 100 depending on the selection order of the contents, the browsing history, the location information indicated by the contents, etc.

[0078] The terminal 20 may display content that is presumed to be inside the performance venue with priority, and display content that is presumed to be outside the performance venue with lower priority.

[0079] 6 and 7 are merely examples and may be changed as desired as long as the object of the present invention is achieved. That is, it is sufficient if the content related to the performance in which the user has participated using the electronic ticket can be suitably recorded and the recorded content can be viewed.

[0080] For example, in response to the viewing request received by the viewing request receiving unit 105, the viewing response sending unit 106 may transmit information in which the linking information is superimposed on the detailed information of the tickets for the performance (for example, the detailed information 323), or information in which the detailed information is superimposed on the linked information, as a viewing response to the terminal 20. For example, the viewing response sending unit 106 may transmit the detailed information in a state in which the linking information is superimposed on the detailed information, such as by using an image included in the linked information as the background of the detailed information, to the terminal 20.

[0081] (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.

[0082] The user may be able to edit the association information stored in the server 10 at any timing by operating the terminal 20. For example, the user may be able to edit the display layout of memorable content according to the association information, as shown in Fig. 7(B).

[0083] Furthermore, when content to be linked to an electronic ticket history and recorded on the server 10 is presented on the terminal 20, the user may add content that is not included in the selection candidates and record the added content as linked information on the server 10. In this way, even if the user is unable to properly collect content to record as memories on the terminal 20, the user can add preferred content, improving user convenience. Furthermore, even if the user is unable to properly collect content to record as memories on the terminal 20, the presentation of selection candidates can notify the user that the corresponding performance has ended, prompting the user to record other content.

[0084] In the above embodiment, the server 10 (electronic ticket management unit 101) is described as issuing electronic tickets, but the issuing of electronic tickets and management of tickets held by users may be performed by a separate server. That is, a separate server equipped with the electronic ticket management unit 101 may be provided.

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

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

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

[0091] (Appendix 1) An electronic ticket management system that includes a server and participating terminals and manages the usage history of electronic tickets, When the event in which the participant participated using the electronic ticket held in the participating terminal has ended, The server Obtain detailed information including period information relating to the period during which the completed event was held; recording the acquired detailed information in association with the event in which the participant participated; Sending the acquired detailed information to the participating terminal; The participating terminals are: receiving detailed information sent from the server; Collecting content associated with a period based on period information included in the received detailed information; displaying the received detailed information on a screen and displaying the collected content on the screen as selection candidates; When the participant selects one of the selection candidates, linking information linking the content related to the selected selection candidate to the detailed information is transmitted to the server; The server receiving the linking information transmitted from the participating terminal; The received linking information is linked to the detailed information and recorded. Electronic ticket management system.

[0092] (Appendix 2) a viewing terminal including the participating terminal transmits a viewing request to the server based on an instruction from the participant; The server Upon receiving the viewing request from the viewing terminal, the participant using the viewing terminal obtains detailed information recorded in association with the event in which the participant participated; If the acquired detailed information is not recorded in association with associated information, the detailed information is included in a viewing response and transmitted to the viewing terminal; If the acquired detailed information is recorded in association with associated information, the detailed information and the associated information are included in the viewing response and transmitted to the viewing terminal; The viewing terminal is When the viewing response is received, the information included in the viewing response is displayed. 1. An electronic ticket management system as described in Appendix 1.

[0093] (Appendix 3) The detailed information includes location information regarding the location where the event was held, The participating terminal preferentially displays, as the selection candidates, content associated with a location close to the location related to the location information. 1. An electronic ticket management system as set forth in Appendix 1 or 2.

[0094] (Appendix 4) The participating terminal displays detailed information about the electronic ticket by partially modifying the manner in which the temporarily stored electronic ticket is displayed on the participating terminal. The electronic ticket management system according to claim 1. 1. An electronic ticket management system as described in Appendix 1, 2 or 3.

[0095] (Appendix 5) The viewing terminal displays detailed information and linking information related to the electronic ticket by partially modifying the manner in which the temporarily stored electronic ticket is displayed on the participating terminal. 1. An electronic ticket management system as described in Appendix 2.

[0096] (Appendix 6) The participating terminals are: Accepting input of content corresponding to the event corresponding to the electronic ticket or detailed information about the event; transmitting linking information linking the received content to the performance or the detailed information to the server; The server receiving the linking information transmitted from the participating terminal; The received linking information is linked to the performance or the detailed information and recorded. 6. An electronic ticket management system according to any one of appendices 1 to 5.

[0097] (Appendix 7) If the acquired detailed information is recorded in association with associated information, the associated information is superimposed on the detailed information and included in the viewing response, and the viewing response is transmitted to the viewing terminal. 10. An electronic ticket management system as set forth in Appendix 2 or 5.

[0098] (Appendix 8) The server Acquire entry and exit information of the venue of the event from the participating terminal; The entrance / exit information is included in the detailed information and transmitted to the participating terminals; The participating terminals are: Among the collected contents, contents for a period during which the person was located inside the venue of the performance and contents for a period during which the person was located outside the venue of the performance are displayed on the screen separately based on the entrance / exit information. 8. An electronic ticket management system according to any one of appendices 1 to 7.

[0099] (Appendix 9) The participating terminals are: highlighting either the content during the period when the user was located inside the venue of the performance or the content during the period when the user was located outside the venue of the performance; 10. An electronic ticket management system as described in Appendix 8.

[0100] (Appendix 10) An electronic ticket management method executed by a server and participating terminals, comprising: When the event in which the participant participated using the electronic ticket held in the participating terminal has ended, The server Obtain detailed information including period information relating to the period during which the completed event was held; recording the acquired detailed information in association with the event in which the participant participated; Sending the acquired detailed information to the participating terminal; The participating terminals are: receiving detailed information sent from the server; Collecting content associated with a period based on period information included in the received detailed information; displaying the received detailed information on a screen and displaying the collected content on the screen as selection candidates; When the participant selects one of the selection candidates, linking information linking the content related to the selected selection candidate to the detailed information is transmitted to the server; The server receiving the linking information transmitted from the participating terminal; The received linking information is linked to the detailed information and recorded. Electronic ticket management methods. [Industrial Applicability]

[0101] According to the present invention, it is possible to provide an electronic ticket management system and an electronic ticket management method that can suitably record content related to a performance in which a user has participated using an electronic ticket. [Explanation of symbols]

[0102] 10 Server, 20 Terminal, 11, 21 Processor, 12, 22 Storage device, 13, 23 Communication interface, 14, 24 Input device, 15, 25 Output device, 100 Electronic ticket management system, 101 Electronic ticket management unit, 102 Performance detailed information acquisition unit, 103 Detailed information transmission unit, 104 Linking information reception unit, 105 Viewing request reception unit, 106 Viewing response transmission unit, 110 Database, 201 Electronic ticket reception unit, 202 Electronic ticket display unit, 203 Detailed information reception unit, 204 Content collection unit, 205 Selection candidate display unit, 206 Linking information transmission unit, 207 Selection operation reception unit, 208 Linking information input unit, 209 Viewing request transmission unit, 210 Viewing response reception unit, 211 Performance information display unit, 300 Screen, 301, 302, 322 Button, 303 Electronic ticket, 304 ticket code, 305 memo field, 306 icon, 307, 323 detailed information, 308 selection button, 309, 324 scroll button, 310 confirm button, 321 summary information, C1 to C6 options, M1 to M6 content.

Claims

1. An electronic ticket management system that includes a server and participating terminals and manages the usage history of electronic tickets, When the event in which the participant participated using the electronic ticket held in the participating terminal has ended, The server Obtain detailed information including period information relating to the period during which the completed event was held; recording the acquired detailed information in association with the event in which the participant participated; Sending the acquired detailed information to the participating terminal; The participating terminals are: receiving detailed information sent from the server; Collecting content associated with a period based on period information included in the received detailed information; displaying the received detailed information on a screen and displaying the collected content on the screen as selection candidates; When the participant selects one of the selection candidates, linking information linking the content related to the selected selection candidate to the detailed information is transmitted to the server; The server receiving the linking information transmitted from the participating terminal; The received linking information is linked to the detailed information and recorded. Electronic ticket management system.

2. a viewing terminal including the participating terminal transmits a viewing request to the server based on an instruction from the participant; The server Upon receiving the viewing request from the viewing terminal, the participant using the viewing terminal obtains detailed information recorded in association with the event in which the participant participated; If the acquired detailed information is not recorded in association with associated information, the detailed information is included in a viewing response and transmitted to the viewing terminal; If the acquired detailed information is recorded in association with associated information, the detailed information and the associated information are included in the viewing response and transmitted to the viewing terminal; The viewing terminal is When the viewing response is received, the information included in the viewing response is displayed. The electronic ticket management system according to claim 1 .

3. The detailed information includes location information regarding the location where the event was held, The participating terminal preferentially displays, as the selection candidates, content associated with a location close to the location related to the location information. The electronic ticket management system according to claim 1 .

4. The participating terminal displays detailed information about the electronic ticket by partially modifying the manner in which the temporarily stored electronic ticket is displayed on the participating terminal. The electronic ticket management system according to claim 1 .

5. The viewing terminal displays detailed information and linking information related to the electronic ticket by partially modifying the manner in which the temporarily stored electronic ticket is displayed on the participating terminal. The electronic ticket management system according to claim 2 .

6. The participating terminals are: Accepting input of content corresponding to the event corresponding to the electronic ticket or detailed information about the event; transmitting linking information linking the received content to the performance or the detailed information to the server; The server receiving the linking information transmitted from the participating terminal; The received linking information is linked to the performance or the detailed information and recorded. The electronic ticket management system according to any one of claims 1 to 5.

7. If the acquired detailed information is recorded in association with associated information, the associated information is superimposed on the detailed information and included in the viewing response, and the viewing response is transmitted to the viewing terminal. The electronic ticket management system according to claim 2 .

8. The server Acquire entry and exit information of the venue of the event from the participating terminal; The entrance / exit information is included in the detailed information and transmitted to the participating terminals; The participating terminals are: Among the collected contents, contents for a period during which the person was located inside the venue of the performance and contents for a period during which the person was located outside the venue of the performance are displayed on the screen separately based on the entrance / exit information. The electronic ticket management system according to claim 1 .

9. The participating terminals are: highlighting either the content during the period when the user was located inside the venue of the performance or the content during the period when the user was located outside the venue of the performance; The electronic ticket management system according to claim 8 .

10. An electronic ticket management method executed by a server and participating terminals, comprising: When the event in which the participant participated using the electronic ticket held in the participating terminal has ended, The server Obtain detailed information including period information relating to the period during which the completed event was held; recording the acquired detailed information in association with the event in which the participant participated; Sending the acquired detailed information to the participating terminal; The participating terminals are: receiving detailed information sent from the server; collect content associated with a period based on the period related to the period information included in the received detailed information; displaying the received detailed information on a screen and displaying the collected content on the screen as selection candidates; When the participant selects one of the selection candidates, linking information linking the content related to the selected selection candidate to the detailed information is transmitted to the server; The server receiving the linking information transmitted from the participating terminal; The received linking information is linked to the detailed information and recorded. Electronic ticket management methods.

Images