Programs, methods, information processing devices, systems

Abstract

To gain a more accurate understanding of ticket usage. [Solution] A program for operating a computer, the program causing the computer's processor to execute the following steps: marking a ticket as used; sending ticket data, which is information that the ticket has been used, to a server based on the fact that the ticket has been used; displaying a first object on the computer's display unit for accepting operations to the computer; accepting operations to the first object; determining whether the transmission of the ticket data was successful based on the acceptance of the operations; and, if it is determined in the determination step that the transmission of the ticket data was successful, displaying information about the seat associated with the ticket on the display unit.

Description

Technical Field

[0001] The present disclosure relates to a program, a method, an information processing apparatus, and a system.

Background Art

[0002] There is an electronic ticket system that distributes an electronic ticket obtained by digitizing an admission ticket to a mobile terminal and determines whether admission is permitted by checking the electronic ticket stored in the terminal of an event attendee at the entrance of the event venue.

[0003] In Patent Document 1, a data communication terminal capable of data communication and having a storage medium capable of writing the right information of a ticket is used to apply for the purchase of a ticket. The ticket sales center transmits the right information of the ticket, writes the right information of the ticket into the storage medium, and the right information of the ticket written into the storage medium is authenticated at the gate so that the attendee can enter the venue.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In many events, in order to smoothly admit attendees, the determination of whether an attendee can enter and the use process of the ticket are performed without communicating between the terminal to which the electronic ticket is distributed and the server that manages information related to the ticket. After the attendee enters the venue, information regarding the use of the ticket is transmitted from the terminal or the ticket gate apparatus to the server. Thereby, an event operator or the like can grasp the usage status of the ticket (the admission status of the attendee) by checking the information transmitted to the server.

[0006] However, terminals and ticket checking devices may be unable to transmit information to the server depending on the communication conditions. As a result, event organizers and others who are responsible for event management, operation, and other related tasks have had the problem of not being able to accurately grasp the status of ticket usage (the entry status of attendees).

[0007] The purpose of this disclosure is to provide a more accurate understanding of ticket usage. [Means for solving the problem]

[0008] A program for operating a computer, the program causing the computer's processor to execute the following steps: marking a ticket as used; sending ticket data, which is information that the ticket has been used, to a server based on the fact that the ticket has been used; displaying a first object on the computer's display unit for accepting operations to the computer; accepting operations to the first object; determining whether the transmission of the ticket data was successful based on the acceptance of the operations; and, if it is determined in the determination step that the transmission of the ticket data was successful, displaying information about the seat associated with the ticket on the display unit. [Effects of the Invention]

[0009] This disclosure allows for a more accurate understanding of ticket usage. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing the functional configuration of System 1. [Figure 2] This is a block diagram showing the functional configuration of the terminal device 10. [Figure 3] This is a block diagram showing the functional configuration of Server 20. [Figure 4] This is a block diagram showing the functional configuration of the ticket inspection device 30. [Figure 5] It is a diagram showing the data structure of the user table 2021. [Figure 6] It is a diagram showing the data structure of the ticket table 2022. [Figure 7] It is a diagram showing the data structure of the event table 2023. [Figure 8] It is a diagram showing the data structure of the feature amount table 2024. [Figure 9] It is a diagram showing the data structure of the ticket data 182. [Figure 10] It is a flowchart of the ticket issuing process of this embodiment. [Figure 11] It is a schematic diagram showing the outline of the seat display process of the first embodiment. [Figure 12] It is a flowchart of the seat display process of the first embodiment. [Figure 13] It is a flowchart of the first ticket arrival data transmission process of the first embodiment. [Figure 14] It is a flowchart of the second ticket arrival data transmission process of the first embodiment. [Figure 15] It is a schematic diagram showing the outline of the seat display process of the second embodiment. [Figure 16] It is a flowchart of the ticket inspection process of the second embodiment. [Figure 17] It is a flowchart of the seat display process of the second embodiment. [Figure 18] It is a schematic diagram showing an example screen of the seat acquisition screen D1. [Figure 19] It is a schematic diagram showing an example screen of the effect screen D2. [Figure 20] It is a schematic diagram showing an example screen of the display request screen D3. [Figure 21] It is a schematic diagram showing an example screen of the seat display screen D4. [Figure 22] It is a schematic diagram showing an example screen of the seat acquisition screen D5. [Figure 23] It is a block diagram showing the basic hardware configuration of the computer 90.

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for describing the embodiments, the same reference numerals are assigned to common components, and repeated descriptions are omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all of the components shown in the embodiments are essential components of the present disclosure. Further, each drawing is a schematic diagram and is not necessarily drawn precisely.

[0012] Also, in the following description, a "processor" refers to one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may also be another type of processor such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core.

[0013] Also, at least one processor may be a processor in a broad sense such as a hardware circuit (e.g., FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs part or all of the processing.

[0014] Also, in the following description, expressions such as "xxx table" may be used to describe information from which an output is obtained for an input. This information may be data of any structure or a learning model such as a neural network that generates an output for an input. Therefore, "xxx table" can be referred to as "xxx information".

[0015] Also, in the following description, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0016] Furthermore, in the following explanation, the subject of the process may sometimes be "program," but since a program is executed by a processor and performs defined processes using the memory and / or interface as appropriate, the subject of the process may also be the processor (or a device such as a controller that has that processor).

[0017] The program may be installed on a device such as a computer, or it may reside on a program distribution server or a computer-readable (e.g., non-temporary) recording medium. Furthermore, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs.

[0018] Furthermore, in the following explanation, identification numbers are used as identification information for various objects, but other types of identification information (for example, identifiers including letters or symbols) may also be used.

[0019] Furthermore, in the following explanations, when describing similar elements without distinction, a reference code (or a common code among reference codes) may be used, and when describing similar elements with distinction, the element's identification number (or reference code) may be used.

[0020] Furthermore, in the following explanation, only control lines and information lines deemed necessary for the explanation are shown, and not all control lines and information lines in the product are necessarily shown. All components may be interconnected.

[0021] Each information processing device consists of a computer equipped with an arithmetic unit and a memory device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by that hardware configuration will be described later. For both the server and the user terminal, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0022] <1 System Configuration Diagram> Figure 1 is a block diagram showing an example of the overall configuration of System 1. System 1 shown in Figure 1 includes, for example, a terminal device 10, a server 20, and a ticket inspection device 30. The terminal device 10, server 20, and ticket inspection device 30 communicate with each other, for example, via a network 80.

[0023] In Figure 1, the number of terminal devices 10 included in System 1 is not limited to one. There may be two or more terminal devices 10 included in System 1.

[0024] Figure 1 shows an example where System 1 includes one Server 20, but the number of Servers 20 included in System 1 is not limited to one. Server 20 may consist of multiple servers depending on the functions they have. Also, Server 20 may be, for example, a collection of multiple devices. The way in which the multiple functions required to implement Server 20 according to this embodiment are distributed to one or more hardware can be appropriately determined in consideration of the processing capacity of each hardware and / or the specifications required for Server 20.

[0025] In Figure 1, the number of ticket inspection devices 30 included in System 1 is not limited to one. There may be two or more ticket inspection devices 30 included in System 1.

[0026] The terminal device 10 shown in Figure 1 can be implemented, for example, by a mobile device such as a smartphone or tablet that supports a mobile communication system. Alternatively, the terminal device 10 may be implemented by, for example, a stationary PC (Personal Computer) or a laptop PC. Furthermore, the terminal device 10 may be implemented by, for example, a wearable device such as an HMD (Head Mount Display). The terminal device 10 is an information processing device operated by a user who is entering or leaving the target space.

[0027] The terminal device 10 comprises a communication interface 12, an input device 13, an output device 14, memory 15, storage 16, and a processor 19. The input device 13 is a device for receiving input operations from the user (e.g., a touch panel, touchpad, etc.). The output device 14 is a device for presenting information to the user (e.g., a display, speaker, etc.).

[0028] The server 20 is implemented, for example, by a computer connected to the network 80. As shown in Figure 1, the server 20 includes a communication IF 22, an I / O IF 23, memory 25, storage 26, and a processor 29. The I / O IF 23 functions as an interface for an input device to receive input operations from the user and an output device to present information to the user.

[0029] The ticket inspection device 30 shown in Figure 1 can be implemented, for example, by a mobile terminal such as a smartphone or tablet that supports a mobile communication system. Alternatively, the ticket inspection device 30 may be implemented by, for example, a stationary PC (Personal Computer) or a laptop PC. Furthermore, the ticket inspection device 30 may be implemented by, for example, a wearable terminal such as an HMD (Head Mount Display).

[0030] The ticket inspection device 30 is an information processing device located at the ticket inspection station. The ticket inspection station corresponds to the boundary between the target space and the external space. The ticket inspection device 30 is configured to refer to the ticket information held in the ticket presented by the user attempting to enter the target space and to determine whether the user is allowed to enter. The ticket inspection device 30 can also be described as an entry and exit management device that manages entry and exit to the target space.

[0031] The target space refers to a space where at least one of entry and exit is restricted. The target space may be indoors or outdoors. For example, the target space may be an event venue, public transport, office, or shop. Here, "event" includes all kinds of gatherings and activities, such as sporting events, gaming events, seminars, conferences, exhibitions, trade shows, concerts (live events), fan meetings, social gatherings, film screenings, theatrical performances, festivals (including local festivals as well as festivals based on specific themes such as music festivals and food festivals), volunteer events, school events, corporate events, etc.

[0032] In this disclosure, an event venue will be used as an example of the target space for explanation.

[0033] The ticket inspection device 30 includes a communication interface 32, an input device 33, an output device 34, a memory 35, storage 36, and a processor 39. The input device 33 is a device for receiving input operations from the user (e.g., a touch panel, touchpad, etc.). The output device 34 is a device for presenting information to the user (e.g., a display, speaker, etc.).

[0034] Each information processing device consists of a computer equipped with an arithmetic unit and a memory device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by said hardware configuration will be described later. For each of the terminal device 10, server 20, and ticket inspection device 30, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0035] <Terminal device configuration> Figure 2 is a block diagram showing an example configuration of the terminal device 10 shown in Figure 1. As shown in Figure 2, the terminal device 10 includes a communication unit 120, an input device 13, an output device 14, an audio processing unit 17, a microphone 171, a speaker 172, a position information sensor 150, a camera 160, a motion sensor 170, a storage unit 180, and a control unit 190. Each block included in the terminal device 10 is electrically connected, for example, by a bus.

[0036] The communication unit 120 performs processing such as modulation and demodulation processing for the terminal device 10 to communicate with other devices. The communication unit 120 performs transmission processing on the signal generated by the control unit 190 and transmits it to an external source (for example, the server 20). The communication unit 120 performs reception processing on the signal received from an external source and outputs it to the control unit 190.

[0037] The input device 13 is a device for a user operating the terminal device 10 to input instructions or information. The input device 13 can be implemented, for example, by a touch-sensitive device 131 on which instructions are input by touching the operating surface. If the terminal device 10 is a PC, the input device 13 may be implemented by a reader, keyboard, mouse, etc. The input device 13 converts the instructions input by the user into electrical signals and outputs the electrical signals to the control unit 190. The input device 13 may also include, for example, a receiving port that accepts electrical signals input from an external input device.

[0038] The output device 14 is a device for presenting information to the user operating the terminal device 10. The output device 14 is implemented, for example, by a display unit such as a display 141. The display 141 displays data according to the control of the control unit 190. The display 141 is implemented, for example, by an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0039] The audio processing unit 17 performs, for example, digital-to-analog conversion processing of the audio signal. The audio processing unit 17 converts the signal received from the microphone 171 into a digital signal and provides the converted signal to the control unit 190. The audio processing unit 17 also provides the audio signal to the speaker 172. The audio processing unit 17 is implemented, for example, by an audio processing processor. The microphone 171 receives an audio input and provides the audio signal corresponding to that audio input to the audio processing unit 17. The speaker 172 converts the audio signal received from the audio processing unit 17 into audio and outputs the audio to the outside of the terminal device 10.

[0040] The location information sensor 150 is a sensor that detects the position of the terminal device 10, and is, for example, a GPS (Global Positioning System) module. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current position of the terminal device 10, which is equipped with a GPS module, is detected based on the received signals. The location information sensor 150 may also detect the current position of the terminal device 10 from the position of the wireless base station to which the terminal device 10 is connected.

[0041] Camera 160 is a device that receives light using a photodetector and outputs it as a shooting signal.

[0042] The motion sensor 170 includes, for example, an acceleration sensor, an angular velocity sensor, or a combination thereof. However, it is not limited to these. The motion sensor 170 detects the movement of the terminal device 10 and outputs the sensing result.

[0043] The storage unit 180 is implemented by, for example, memory 15 and storage 16, and stores data and programs used by the terminal device 10. The storage unit 180 stores, for example, user information 181.

[0044] User information 181 stores information about the user performing the operation. User information includes, for example, user ID, name, age, address, date of birth, registration date, etc.

[0045] Ticket data 182 is data relating to a ticket for a specified event, transmitted from the server 20, etc., by, for example, a user operating the terminal device 10. Details of ticket data 182 will be described later.

[0046] The control unit 190 is realized when the processor 19 reads a program stored in the memory unit 180 and executes instructions contained in the program. The control unit 190 controls the operation of the terminal device 10. By operating according to the program, the control unit 190 performs the functions of an operation reception unit 191, a transmission / reception unit 192, a presentation control unit 193, a decision unit 194, and a ticket management unit 195.

[0047] The operation reception unit 191 processes instructions or information input from the input device 13. For example, the operation reception unit 191 receives instructions or information input from a touch-sensitive device 131 or the like.

[0048] Furthermore, the operation reception unit 191 receives images input from the camera 160. Specifically, for example, the operation reception unit 191 receives the image data captured by the camera 160.

[0049] Furthermore, the operation reception unit 191 receives voice information input from the microphone 171. Specifically, for example, the operation reception unit 191 receives voice data input from the microphone 171 and converted into digital data by the voice processing unit 17.

[0050] Furthermore, the operation reception unit 191 receives behavioral information input from the motion sensor 170. Specifically, for example, the operation reception unit 191 receives a predetermined behavior detected by the motion sensor 170.

[0051] The transmitting / receiving unit 192 performs processing to enable the terminal device 10 to send and receive data with an external device such as the server 20 in accordance with a communication protocol. Specifically, for example, the transmitting / receiving unit 192 sends instructions input by the user to the server 20. The transmitting / receiving unit 192 receives information provided by the server 20.

[0052] The presentation control unit 193 controls the output device 14 and other devices in order to present various types of information to the user.

[0053] The determination unit 194 determines whether the transmission of the ticket arrival data, described later, from the terminal device 10 to the server 20 was successful for a particular ticket, or whether the server 20 has received the ticket arrival data. Specifically, the decision unit 194 makes the following decisions.

[0054] (Retrieval of information stored in the memory unit 180 of the terminal device 10) The determination unit 194 may determine whether the transmission of the ticket arrival data was successful (whether the server 20 received the ticket arrival data) based on information stored in the storage unit 180 of the terminal device 10 that the terminal device 10 has transmitted the ticket arrival data to the server 20. Specifically, if the determination unit 194 can determine that the terminal device 10 has transmitted the ticket arrival data to the server 20, it may determine that the transmission of the ticket arrival data was successful. For example, the determination unit 194 determines whether the terminal device 10 has sent the ticket data to the server 20 by referring to the "transmission status" item of the ticket data 182 stored in the storage unit 180. Alternatively, the determination unit 194 determines whether the terminal device 10 has sent the ticket data to the server 20 by referring to the ticket data transmission log, etc., stored in the storage unit 180. Furthermore, for example, the determination unit 194 may determine that the terminal device 10 has successfully transmitted the ticket data to the server 20 (for example, that the terminal device 10 has received a response from the server 20 indicating that the ticket data has been received), and that the transmission of the ticket data has been successful (that the server 20 has received the ticket data).

[0055] (Inquiry to other information processing devices) The determination unit 194 may determine whether the transmission of the ticket data was successful (whether the server 20 received the ticket data) by querying other information processing devices to see if the server 20 has received the ticket data for a specific ticket. For example, the decision unit 194 sends an inquiry including the ticket ID to the server 20, and receives information from the server 20 regarding whether or not the server 20 has received the ticket data for the ticket associated with the ticket ID (information regarding the status of receipt of the ticket data by the server 20, the receipt history, and the results of the confirmation such as whether or not the ticket data is stored in the storage unit 202). Based on the information received, the decision unit 194 determines whether or not the server 20 has received the ticket data. Furthermore, for example, if the ticket inspection device 30 transmits the ticket data to the server 20, the determination unit 194 may send an inquiry including the ticket ID to the ticket inspection device 30, and receive information from the ticket inspection device 30 regarding whether or not the ticket inspection device 30 has transmitted the ticket data to the server 20 for the ticket related to the ticket ID (information regarding the status of the ticket data transmission by the ticket inspection device 30, transmission history, etc.). Based on the received information, the determination unit 194 may determine whether or not the server 20 has received the ticket data.

[0056] Ticket Management Department 195 manages information related to tickets. Specifically, the ticket management unit 195 manages ticket information by managing ticket data 182 based on the operation of the terminal device 10. Furthermore, for example, the ticket management unit 195 generates ticket data 182 based on the information of each item of the ticket data transmitted from the server 20 during the ticketing process described later. For example, the ticket management department 195 updates the "Usage Status" item in the ticket data 182 from unused to used based on the fact that the ticket has been marked as used. Furthermore, for example, the ticket management unit 195 updates the "transmission status" item in the ticket data 182 from "not transmitted" to "transmitted" based on the terminal device 10 transmitting the ticket data to the server 20. Furthermore, for example, in the seat display processing described later, the ticket management unit 195 updates the information in the "Information" and "Seat Information" fields of the ticket data 182 based on the information and seat information received by the terminal device 10 from the server 20.

[0057] <Server Functional Configuration> Figure 3 shows an example of the functional configuration of server 20. As shown in Figure 3, server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0058] The communications unit 201 performs processing to enable the server 20 to communicate with external devices.

[0059] The memory unit 202 stores, for example, a user table 2021, a ticket table 2022, an event table 2023, and a feature table 2024.

[0060] User Table 2021 is a table that stores information about users registered for the service related to this disclosure.

[0061] The Ticket Table 2022 is a table that stores information about tickets.

[0062] Event Table 2023 is a table that stores information about events.

[0063] Feature Table 2024 is a table that stores information about human features (for example, facial features).

[0064] The control unit 203 is realized when the processor 29 reads a program stored in the memory unit 202 and executes instructions contained in the program. By operating according to the program, the control unit 203 performs functions as a receive control module 2031, a transmit control module 2032, a presentation control module 2038, a feature acquisition module 2033, a reference feature determination module 2034, and a ticket data generation module 2035.

[0065] The receive control module 2031 controls the process by which the server 20 receives signals from external devices according to a communication protocol. Specifically, for example, the receive control module 2031 receives signals transmitted from the terminal device 10.

[0066] The transmission control module 2032 controls the process by which the server 20 transmits signals to external devices according to a communication protocol.

[0067] The presentation control module 2038 presents various UIs to the user via the terminal device 10. Specifically, for example, the presentation control module 2038 presents various UIs to the user by transmitting information to the terminal device 10 for the terminal device 10 to output various UIs to the output device 14.

[0068] The feature acquisition module 2033 acquires user features. Specifically, the feature acquisition module 2033 acquires features from the user's biometric information using arbitrary feature acquisition techniques for obtaining features from biometric information. For example, if the biometric information is a facial image, the feature acquisition module 2033 will acquire the features of the user's face from the user's facial image using any feature acquisition technique. Furthermore, biometric information is not limited to facial images; it may also include images of other parts of the user's body. For example, biometric information may include data obtained from the user's hands and fingers (fingerprint data, palm print data, vein pattern data, etc.), data obtained from the eyes (iris data, retinal data, etc.), or data obtained from the voice (voiceprint data, etc.).

[0069] The reference feature determination module 2034 determines the reference features. Specifically, the reference feature determination module 2034 determines, as a reference feature, a feature that has a predetermined similarity to the feature based on the ticket purchaser's biometric information (purchaser feature) from the features stored in the feature table 2024 described later (for example, the most similar feature). Note that the purchaser feature may be transmitted from another information processing device, or it may be associated with the purchaser's user information and stored in the storage unit 202 in advance.

[0070] Here, the reference feature is a feature stored in the feature table 2024 (described later) that has a predetermined similarity to the buyer feature. Here, the feature is, for example, information represented as vector information with arbitrary dimensions. Note that the vector information representing the feature may be converted to any data format using any data transformation method.

[0071] Furthermore, the degree of similarity between multiple features corresponds, for example, to the smallness of the Euclidean distance between those features. Therefore, a reference feature is specifically a feature stored in feature table 2024 that has a predetermined Euclidean distance from the buyer feature. As an example, the reference feature is as follows: • Any feature stored in Feature Table 2024 whose Euclidean distance from the buyer feature is less than or equal to a predetermined value (or less than the predetermined value, greater than or equal to the predetermined value, greater than the predetermined value, or within a certain range from the predetermined value) • Among the features stored in Feature Table 2024, the feature with the smallest (or largest) Euclidean distance from the buyer feature.

[0072] The ticket data generation module 2035 generates ticket data in association with users who have obtained or purchased tickets, or users who have won a ticket lottery. Specifically, the ticket data generation module 2035 associates the user's user information (user ID, username, etc.), event information (event ID, event name, event date and time, venue, seating information, etc.), and the reference feature ID determined by the reference feature determination module 2034 with the unissued ticket ID and stores them in the storage unit 202 (for example, the ticket table 2022 described later) in relation to each other.

[0073] Furthermore, for example, the ticket data generation module 2035 generates check data by performing a predetermined operation (an arbitrary operation that converts multiple data into a single unique data) based on the ticket ID, event ID, and reference feature ID. The check data is, for example, data represented as a sequence of numbers or a string.

[0074] Furthermore, for example, the ticket data generation module 2035 generates a code (e.g., a two-dimensional code) that stores at least the check data and the ticket ID, based on any code generation technology.

[0075] <Configuration of the ticket inspection device 30> Figure 4 is a block diagram showing an example configuration of the ticket inspection device 30 shown in Figure 1. As shown in Figure 4, the ticket inspection device 30 includes a communication unit 320, an input device 33, an output device 34, an audio processing unit 37, a microphone 371, a speaker 372, a position information sensor 350, a camera 360, a motion sensor 370, a storage unit 380, and a control unit 390. Each block included in the ticket inspection device 30 is electrically connected, for example, by a bus.

[0076] The communication unit 320 performs modulation and demodulation processing for the ticket inspection device 30 to communicate with other devices. The communication unit 320 performs transmission processing on the signal generated by the control unit 390 and transmits it to an external source (for example, the server 20). The communication unit 320 performs reception processing on the signal received from an external source and outputs it to the control unit 390.

[0077] The input device 33 is a device for users (visitors, staff at the ticket inspection station, etc.) to input instructions or information when operating the ticket inspection device 30. The input device 33 can be implemented, for example, by a touch-sensitive device 331 on which instructions are input by touching the operating surface. If the ticket inspection device 30 is a PC, the input device 33 may be implemented by a reader, keyboard, mouse, etc. The input device 33 converts the instructions input by the user into electrical signals and outputs the electrical signals to the control unit 390. The input device 33 may also include, for example, a receiving port that accepts electrical signals input from an external input device.

[0078] The output device 34 is a device for presenting information to the user operating the ticket inspection device 30. The output device 34 is implemented, for example, by a display 341. The display 341 displays data according to the control of the control unit 390. The display 341 is implemented, for example, by an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0079] The audio processing unit 37 performs, for example, digital-to-analog conversion processing of the audio signal. The audio processing unit 37 converts the signal provided from the microphone 371 into a digital signal and provides the converted signal to the control unit 390. The audio processing unit 37 also provides the audio signal to the speaker 372. The audio processing unit 37 is implemented, for example, by an audio processing processor. The microphone 371 receives an audio input and provides the audio signal corresponding to that audio input to the audio processing unit 37. The speaker 372 converts the audio signal provided from the audio processing unit 37 into audio and outputs the audio to the outside of the ticket inspection device 30.

[0080] The location information sensor 350 is a sensor that detects the position of the ticket inspection device 30, and is, for example, a GPS (Global Positioning System) module. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and based on the received signals, the current position of the ticket inspection device 30, which is equipped with a GPS module, is detected. The location information sensor 350 may also detect the current position of the ticket inspection device 30 from the position of the wireless base station to which the ticket inspection device 30 is connected.

[0081] Camera 360 is a device that receives light using a photodetector and outputs it as a shooting signal.

[0082] The motion sensor 370 includes, for example, an acceleration sensor, an angular velocity sensor, or a combination thereof. However, it is not limited to these. The motion sensor 370 detects the movement of the ticket inspection device 30 and outputs the sensing result.

[0083] The storage unit 380 is implemented by, for example, memory 35 and storage 36, and stores data and programs used by the ticket inspection device 30. For example, the storage unit 380 stores ticket inspection data 381.

[0084] The ticket verification data 381 is used to determine whether a user is allowed to enter based on the presented ticket. The ticket verification data 381 includes, for example, an event ID and a feature table 3811. The feature table 3811 stores information similar to that stored in the feature table 2024, which will be described later, and is stored on the server 20.

[0085] The control unit 390 is realized when the processor 39 reads a program stored in the memory unit 380 and executes instructions contained in the program. The control unit 390 controls the operation of the ticket inspection device 30. By operating according to the program, the control unit 390 performs the functions of an operation reception unit 391, a transmission / reception unit 392, a presentation control unit 393, a ticket data acquisition unit 394, a feature quantity acquisition unit 395, and an entry eligibility determination unit 396.

[0086] The operation reception unit 391 processes instructions or information input from the input device 33. For example, the operation reception unit 391 receives instructions or information input from a touch-sensitive device 331, etc. Specifically, for example, the operation reception unit 391 receives a setting of a predetermined time from the user. The predetermined time includes, for example, the planned wake-up time or the planned confirmation time.

[0087] Furthermore, the operation reception unit 391 receives images input from the camera 360. Specifically, the operation reception unit 391 receives the image data captured by the camera 360. For example, it receives image data of the code displayed on the display 141 of the terminal device 10, and image data of the user.

[0088] Furthermore, the operation reception unit 391 receives audio information input from the microphone 371. Specifically, for example, the operation reception unit 391 receives audio data input from the microphone 371 and converted into digital data by the audio processing unit 37.

[0089] Furthermore, the operation reception unit 391 receives behavioral information input from the motion sensor 370. Specifically, for example, the operation reception unit 391 receives a predetermined behavior detected by the motion sensor 370.

[0090] The transmitting / receiving unit 392 performs processing to enable the ticket inspection device 30 to send and receive data with external devices such as the server 20 according to a communication protocol. Specifically, for example, the transmitting / receiving unit 392 sends instructions input by the user to the server 20. The transmitting / receiving unit 392 receives information provided by the server 20.

[0091] The presentation control unit 393 controls the output device 34 and other devices in order to present information such as information provided by the server 20 to the user.

[0092] The ticket data acquisition unit 394 acquires ticket data. Specifically, the system detects codes (e.g., one-dimensional codes, two-dimensional codes) from images of tickets captured by Camera 360, and then analyzes the codes to obtain the ticket data contained within them. For example, the ticket data acquisition unit 394 acquires the check data and ticket ID contained in the code. The ticket data acquisition unit 394 may acquire information about the ticket from the image of the captured ticket using any image processing technology such as character recognition. Alternatively, the ticket data acquisition unit 394 may acquire information about the ticket contained in the information acquired by the ticket inspection device 30 by analyzing the information using technologies such as NFC (Near Field Communication) and RFID (Radio Frequency Identification).

[0093] The feature acquisition unit 395 acquires user features. Specifically, the feature acquisition unit 395 acquires features from the user's biometric information using any feature acquisition technique for acquiring features from biometric information. For example, if the biometric information is a facial image, the feature acquisition unit 395 acquires the features of the user's face from the facial image captured by the camera 360 using any feature acquisition technique. Furthermore, biometric information is not limited to facial images; it may also include images of other parts of the user's body. For example, biometric information may include data obtained from the user's hands and fingers (fingerprint data, palm print data, vein pattern data, etc.), data obtained from the eyes (iris data, retinal data, etc.), or data obtained from the voice (voiceprint data, etc.).

[0094] The entry / exit determination unit 396 determines whether or not entry into or exit from the target space is permitted. Specifically, the system determines whether entry into or exit from the target space is permitted by comparing the check data obtained by performing predetermined calculations based on the user's features acquired by the feature acquisition unit 395 with the check data acquired by the ticket data acquisition unit 394. For example, first, the admission eligibility determination unit 396 determines a feature from among the features stored in the ticket inspection data 381 that has a predetermined similarity to the user feature acquired by the feature acquisition unit 395, and identifies the feature ID related to that feature. Then, the admission eligibility determination unit 396 generates check data by performing a predetermined calculation based on the identified feature ID, the ticket ID acquired by the ticket data acquisition unit 394, and the event ID included in the ticket inspection data 381. Here, the predetermined calculation is the same calculation that the ticket data generation module 2035 of the server 20 performs when generating check data. The entry / exit determination unit 396 then compares the check data acquired by the ticket data acquisition unit 394 with the check data generated by the entry / exit determination unit 396. If they match, it determines that the user should be allowed to enter or exit; otherwise, it determines that the user should be denied entry or exit.

[0095] <2 Data Structure> Figures 5 to 8 show examples of the data structure of the information stored by server 20. Note that Figures 5 to 8 are examples only and do not exclude data not shown. Furthermore, some of the items exemplified in the data structure may not be present.

[0096] Figure 5 shows the data structure of User Table 2021. User Table 2021 is a table with User ID as the primary key and columns such as User Name and Contact Information.

[0097] The "User ID" field stores the user ID that identifies the user.

[0098] The "Username" field stores the username of a user identified by their User ID. Specifically, the "Username" field stores any string of characters, such as the user's full name or nickname.

[0099] The "Contacts" field stores the contact information of a user identified by their user ID. Specifically, the "Contacts" field may include an email address, phone number, account information for a Social Networking Service (SNS) or other messaging application, or a combination thereof. Contact information is not limited to the examples given here and can include any type of information that can be used to send real-time notifications to the target person via the user's device.

[0100] Figure 6 shows the data structure of ticket table 2022. Ticket table 2022 is a table with ticket ID as the primary key and columns such as event ID, user ID, reference feature ID, guidance information, seat information, and reception status.

[0101] The "Ticket ID" field stores the ticket ID that identifies the ticket.

[0102] The "Event ID" field stores the event ID of the event associated with the ticket identified by the ticket ID.

[0103] The "User ID" field stores the User ID of the user who owns the ticket identified by the Ticket ID.

[0104] The item "Reference Feature ID" is a feature ID that identifies the reference feature quantity of a ticket identified by the ticket ID, and is an item that stores the reference feature ID.

[0105] The "Directions" field stores directions information, which is information used to guide or direct the user to the seat associated with the ticket identified by the ticket ID. Note that the directions information does not include seat information that identifies a specific seat (e.g., seat number). Specifically, the item "Information" may include the following information: (Information about the section to which the seat belongs) • The floor of the venue where the seats are located • Type of section to which the seats belong (arena, stands, balcony, etc.) • Identification information for the section to which the seat belongs (e.g., Arena A1, Stand B2) (Information regarding recommended or mandatory routes for accessing seats) • Information about entrances and gates. For example, identification information for entrance gates, such as "Gate 5". • Directions to pathways. For example, identification information for recommended pathways, such as "Pathway 17".

[0106] The item "Seat Information" is an item that stores seat information, which is information used to identify the seat associated with a ticket identified by the ticket ID. In this disclosure, "seat" refers not only to a seat but also to a specific section or space, and does not necessarily mean that an actual seat is provided. Specifically, for example, the item "Seat Information" stores the identification information of the seat assigned to the ticket, which is identified by the ticket ID.

[0107] The "Reception Status" field stores information regarding the reception status of the ticket data, which will be described later, for tickets identified by the ticket ID. Specifically, the "Reception Status" item stores information indicating that the ticket data has been received if it has already been received, and information indicating that it has not been received if it has not yet been received. The information regarding whether the ticket data has been received or not is, in other words, information to determine whether the ticket identified by the ticket ID has been used or not, and can also be said to be information to determine whether the user has entered the venue or not.

[0108] Figure 7 shows the data structure of Event Table 2023. Event Table 2023 is a table with Event ID as the primary key and columns such as Event Name, Venue, Date and Time.

[0109] The "Event ID" field stores the event ID that identifies the event.

[0110] The "Event Name" field stores the event name of an event identified by its Event ID. Specifically, the "Event Name" field stores string information indicating the name of the event.

[0111] The "Venue" field stores information about the venue of an event identified by its event ID. Specifically, the "Venue" field stores string information indicating the name of the event venue.

[0112] The "Date and Time" field stores date and time information related to the event identified by the event ID. Specifically, the "Date and Time" field stores date and time information related to the event, such as the event start date and time, the event venue opening date and time (entry start date), and the event start date and time.

[0113] Figure 8 shows the data structure of Feature Table 2024. Feature Table 2024 is a table with Feature ID as the primary key and columns such as Feature, etc.

[0114] The "Feature ID" field stores the feature ID that identifies the feature quantity.

[0115] The item "Features" is used to store the features. Specifically, the item "Features" should remember at least one of the following: Features obtained from real people • Features obtained from real people that have undergone anonymization correction (for example, a process that corrects them so that they do not match the original features but have a similarity above a certain level). • Feature quantities obtained from sources that are not real people (for example, facial feature quantities calculated from portraits or computer-generated facial images) • Feature quantities artificially generated through computation (for example, features generated regularly or randomly so as to be distributed with equal density within the representable feature space) • Feature quantities obtained by performing calculations using two or more of the above feature quantities.

[0116] However, the feature table 2024 does not need to store the user's own features obtained to determine the reference feature ID stored in the "Reference Feature ID" item of the ticket table 2022. This ensures that the user's personal information is not stored in the storage unit 202, thus protecting personal information.

[0117] Figure 9 shows an example of the data structure of ticket data 182 stored by the terminal device 10. Note that Figure 9 is just one example and does not exclude data that is not shown. Also, some of the items exemplified in the data structure may not be included.

[0118] Ticket data 182 is data that includes items such as ticket ID, user ID, username, reference feature ID, event ID, event name, venue, date and time, information information, seat information, usage status, and transmission status.

[0119] The "Ticket ID" field is used to store the ticket ID of the ticket.

[0120] The "User ID" field stores the user ID of the user who owns the ticket.

[0121] The "Username" field stores the username of a user identified by their User ID.

[0122] The "Reference Feature ID" field stores the reference feature ID, which is the feature ID referenced when using (authenticating) a ticket.

[0123] The "Event ID" field stores the event ID of the event related to the ticket.

[0124] The "Event Name" field stores the event name of the event identified by the event ID.

[0125] The "Venue" field stores information about the venue of an event identified by its event ID.

[0126] The "Date and Time" field stores date and time information related to an event identified by its Event ID.

[0127] The "Directions" field is used to store information that guides passengers to their seats associated with their tickets.

[0128] The "Seat Information" field is used to store information that identifies the seat associated with the ticket.

[0129] The "Usage Status" field is used to store information regarding the usage status of the ticket.

[0130] The item "Transmission Status" is an item that stores the status of the transmission of information regarding ticket usage to server 20.

[0131] Furthermore, the code obtained by converting the information contained in the ticket data 182 is stored in the storage unit 180. For example, the image data of the code generated by the ticket data generation module 2035 is stored in the storage unit 180.

[0132] <3 operations> (Ticketing process) The ticketing process of this embodiment will now be described. Figure 10 is a flowchart of the ticketing process of this embodiment.

[0133] In step S110, the terminal device 10 executes the acceptance of the purchase operation. Specifically, the terminal device 10 accepts purchase operations performed via the input device 13. The operator of the terminal device 10 is not limited to the ticket purchaser; it may also be someone who operates the terminal device 10 on behalf of the purchaser (for example, an employee at the ticket office). The purchase process may include, for example, entering a user ID, selecting an event, selecting a date and time, selecting a seat type, pressing a purchase button (a button object or physical button), or a combination of these.

[0134] In step S111, the terminal device 10 performs feature acquisition. Specifically, the terminal device 10 acquires image data of the ticket purchaser's face captured by the camera 160. The terminal device 10 performs calculations on the acquired image data to obtain the ticket purchaser's characteristic features (e.g., facial features). Note that the image data may be captured before the start of the ticketing process shown in Figure 11 and stored in the storage unit 180.

[0135] In step S112, the terminal device 10 executes the ticket issuance request. Specifically, the terminal device 10 generates a ticketing request by referring to the content of the purchase operation received in step S110 and the feature quantities acquired in step S111. The ticketing request includes, for example, information that identifies the type of ticket for which issuance is requested (e.g., information that identifies the event, date and time and seat type), as well as the feature quantities and user ID of the ticket purchaser. The terminal device 10 sends the ticketing request to the server 20.

[0136] In step S120, the server 20 performs the identification of the reference feature ID. Specifically, server 20 receives the ticketing request sent in step S112. Server 20 searches the feature table 2024 for features that have a predetermined similarity to the buyer features included in the ticketing request. Server 20 identifies the feature ID associated with the found feature (for example, the feature with the highest similarity to the buyer features) as the reference feature ID.

[0137] In step S121, server 20 performs an update to ticket table 2022. Specifically, server 20 associates the unissued ticket ID with the user ID included in the ticketing request and the reference feature ID identified in step S120, and registers them in ticket table 2022. This makes it possible to identify the ticket purchaser and the reference feature based on the ticket ID.

[0138] In step S122, the server 20 generates ticket data by referring to the updates to ticket table 2022 in step S121.

[0139] The ticket data generated by server 20 includes, for example, the following items. The following items correspond to each item included in ticket data 182. In this embodiment, the information corresponding to the items "Information" and "Seat Information" in ticket data 182 is not included in the ticket data generated in step S122. • Ticket ID: The ticket ID registered in Step S121 • User ID: User ID of the ticket purchaser • Username: Username of the ticket purchaser • Reference Feature ID: The reference feature ID identified in step S121 • Event ID: The event ID for which tickets will be issued. • Event name: Name of the event for which tickets will be issued. • Venue: Information regarding the venue for the event for which tickets are issued. • Date and Time: Information regarding the date and time of the event for which tickets are being issued.

[0140] Server 20 generates data for checking. Specifically, for example, Server 20 generates data for checking by performing predetermined calculations based on the ticket ID, event ID, and reference feature ID.

[0141] Server 20 encodes some or all of the information contained in the generated ticket data into a two-dimensional code or other coded information. The two-dimensional code contains the check data and the ticket ID.

[0142] The server 20 provides the ticket purchaser with the generated ticket data (including the QR code) by transmitting it to the terminal device 10.

[0143] In step S113, the terminal device 10 performs the saving of ticket data. Specifically, the terminal device 10 acquires the ticket data provided in step S122. The terminal device 10 stores the acquired ticket data in the storage unit 180. This allows the terminal device 10 to display the ticket data as needed. Furthermore, the terminal device 10 may optionally perform at least one of the following: The output device 14 (for example, a printing device not shown) prints the ticket data onto paper or other media. The communication unit 120 is instructed to send the ticket data to the user terminal of the ticket purchaser.

[0144] In this embodiment, at step S113, the ticket data 182 does not contain the information that should be stored in the items "Information" and "Seat Information". In other words, in this embodiment, the terminal device 10 cannot display information or seat information at the ticketing stage.

[0145] After step S113, the ticketing process is complete.

[0146] Furthermore, if the ticket inspection method does not acquire the characteristics of the visitor (ticket user) (i.e., visitor characteristics are not used in ticket inspection), the ticket data does not need to include the reference feature ID. In that case, the acquisition of features in step S111 and the identification of the reference feature ID in step S120 do not need to be performed in the ticketing process, and the ticket data generated by the server 20 does not need to include the reference feature ID. (Seat display processing) (First Embodiment) The seat display processing of the first embodiment will now be described. Figure 11 is an explanatory diagram illustrating the overview of the seat display processing of the first embodiment.

[0147] 1) Use of ticket As shown in Figure 11, the terminal device 10 processes ticket usage, for example, at a ticket checkpoint at an event venue. For example, when an event visitor (a user operating the terminal device 10) operates the terminal device 10, an image (i.e., an electronic ticket) generated based on the ticket data 182 stored in the terminal device 10 is displayed on the display 141. When a staff member at the ticket checkpoint operates the terminal device 10, the electronic ticket is marked as used.

[0148] 2) Attempt to send ticket data When a ticket is used, terminal device 10 attempts to send ticket usage data to server 20. If server 20 successfully receives the ticket usage data, it sends the seat information related to the ticket to terminal device 10.

[0149] Ticket usage data refers to information indicating that a ticket has been used (i.e., that the attendee has entered the event venue). Ticket usage data may also include information related to ticket use, and may be data used to maintain, modify, and manage the ticket's usage status. Ticket usage data may include, for example, the following information: • Ticket ID: Corresponds to the information in the "Ticket ID" field of ticket data 182. • Event ID: Corresponds to the information in the "Event ID" field of ticket data 182. • User ID: Corresponds to the "User ID" information in ticket data 182. • Usage Flag: This flag indicates that the ticket has been used and usually contains information such as "TRUE" to show that the ticket has been used. • Date and time of use: This is information regarding the date and time the ticket was used.

[0150] 3) Press the seat acquisition button. Furthermore, once a ticket has been used, the terminal device 10's display 141 displays the seat acquisition screen, which will be described later. The seat acquisition screen displays a "seat acquisition button" object. Based on the visitor's input operation on the seat acquisition button, the terminal device 10 determines whether or not the transmission of the ticket acquisition data to the server 20 was successful (whether or not the server 20 has received the ticket acquisition data).

[0151] If the ticket data transmission in step 2) was successful, the terminal device 10 displays the seat information on the display 141.

[0152] On the other hand, there are cases where ticket data cannot be transmitted in step 2) due to poor communication conditions or other reasons. In that case, the ticket data is sent again from the terminal device 10 to the server 20 in step 3). When the server 20 receives the ticket data, it sends seat information to the terminal device 10. The terminal device 10 displays the received seat information on the display 141.

[0153] In this way, when the ticket is used in step 1), the terminal device 10 attempts to send the ticket data to the server 20 in step 2), and if the transmission is successful, it receives the seat information related to the ticket from the server 20. In step 3), the terminal device 10 determines whether the transmission of the ticket data was successful based on the input operation to the seat acquisition button. If the transmission was successful, the terminal device 10 displays the seat information received from the server 20 in step 2) on the display 141. On the other hand, if the transmission was unsuccessful, the terminal device 10 sends the ticket data to the server 20 again and receives the seat information from the server 20, and displays the received seat information on the display 141.

[0154] Thus, terminal device 10 cannot obtain seat information and cannot present seat information to attendees until it transmits ticket data to server 20. On the other hand, attendees need to check the seat information presented by terminal device 10 in order to move to their seats. Therefore, server 20 receives ticket data related to attendees during the process of attendees moving to their seats. As a result, it becomes possible to more reliably store information regarding ticket usage (in other words, attendee entry status) in server 20 from the time attendees begin entering the venue until they move to their seats and the event begins. Consequently, event organizers and venue managers can more accurately grasp the attendee entry status by checking the information stored in server 20.

[0155] Furthermore, the transmission of ticket acquisition data from the terminal device 10 to the server 20 is performed by the visitor's input operation on the "seat acquisition button." This allows the visitor to recognize the input operation that triggers communication between the terminal device 10 and the server 20 as "an operation to find out their own seat." Therefore, an input operation that would normally be perceived as troublesome can be recognized by the visitor as an operation to find out their own seat. Thus, communication between the terminal device 10 and the server 20 can be achieved without compromising visitor satisfaction. In addition, the terminal device 10 can present a predetermined performance to the user based on the operation of the seat acquisition button and communicate with the server 20 while the performance is being presented. This improves visitor satisfaction during the waiting time when processing is being performed between the terminal device 10 and the server 20.

[0156] Figure 12 is a flowchart of the seat display process in the first embodiment.

[0157] In step S101, the terminal device 10 executes an application for displaying the electronic ticket on the display 141 based on the visitor's operation. The application may be executed via a web browser. When the visitor operates the terminal device 10 to execute the application and performs a predetermined operation, the terminal device 10 displays an object representing the electronic ticket on the display 141.

[0158] In step S102, the terminal device 10 accepts an operation to use the electronic ticket. Specifically, it accepts a predetermined input operation (for example, a swipe operation or touch operation on the electronic ticket object displayed on the display 141) from a staff member at the ticket inspection station or the like via the input device 13 of the terminal device 10. The input operation may also be performed via a predetermined device such as an electronic stamp.

[0159] In step S103, the terminal device 10, based on receiving an operation to use the electronic ticket, updates the information stored in the "Usage Status" item of the ticket data 182 stored in the storage unit 180 from "Unused" to "Used". As a result, the ticket associated with the ticket data 182 becomes used.

[0160] Furthermore, based on receiving the operation to use the electronic ticket, the terminal device 10 displays information indicating that the ticket has been used to the visitor and staff. For example, the terminal device 10 displays an object containing a message such as "Used" superimposed on the electronic ticket on the display 141. When the staff at the ticket checkpoint confirm this display, they allow the visitor to enter. The visitor passes through the ticket checkpoint and enters the venue.

[0161] In step S104, the terminal device 10 sends ticket arrival data to the server 20 based on the fact that the ticket has been used. Specifically, the terminal device 10 attempts to send ticket arrival data to the server 20 by executing the process shown in Figure 13. The attempt to send ticket arrival data does not require that information about the process be displayed on the display 141 (i.e., the process may be executed in the background).

[0162] Figure 13 is a flowchart detailing the process (first ticket data transmission process) in step S104, which attempts to transmit the ticket data.

[0163] In step S1041, the terminal device 10 attempts to send the ticket data to the server 20.

[0164] The terminal device 10 may not be able to connect to the server 20 depending on the communication environment. In particular, in crowded places such as event venues, the likelihood of the terminal device 10 being unable to connect to the server 20 increases. If the terminal device 10 and the server 20 cannot connect (NO in step S1042), the terminal device 10 executes step S1041 again after a predetermined time. In other words, the terminal device 10 repeats attempts to send the ticket data to the server 20 until it succeeds in sending the ticket data. Unless otherwise specified, the case where the terminal device 10 and the server 20 cannot connect includes all cases in which the terminal device 10 fails to successfully send the ticket data to the server 20 (for example, connection errors, timeouts, cases where the server 20 is unable to process the received ticket data and returns an error response to the terminal device 10, etc.).

[0165] If the terminal device 10 and the server 20 are able to connect (YES in step S1042), in step S1043, the server 20 receives the ticket data.

[0166] In step S1044, the server 20 searches the ticket table 2022 based on the ticket ID included in the received ticket data and updates the "Receipt Status" field of the corresponding record to "Received". This records in the server 20 that the ticket associated with the ticket data has been used (i.e., the visitor associated with that ticket has entered).

[0167] In step S1045, the server 20 searches the ticket table 2022 based on the ticket ID included in the ticket data and retrieves the information included in the item "Information Information" and the seat information included in the item "Seat Information". Server 20 transmits the acquired guidance information and seat information to terminal device 10.

[0168] In step S1046, the terminal device 10 receives guidance information and seat information from the server 20. That is, the terminal device 10 receives guidance information and seat information from the server 20 in response to the successful transmission of the ticket data. The terminal device 10 stores the received guidance information and seat information in the "Guidance Information" and "Seat Information" fields of the ticket data 182, respectively.

[0169] After step S1046, the first ticket data transmission process is completed.

[0170] Returning to the explanation of Figure 12. In step S105, the terminal device 10 displays a seat acquisition screen on the display 141, which is a screen for visitors to perform operations to obtain seat information, based on the fact that the ticket has been used. Note that since step S105 is performed based on the fact that the ticket has been used, it may be executed regardless of the start timing, completion timing, and progress of step S104.

[0171] Furthermore, step S105 is performed based on the fact that the ticket has been used, and does not require communication with other information processing devices. Therefore, in steps S101 to S103 related to using the ticket and step S105 related to displaying the seat acquisition screen, the terminal device 10 can complete the processing internally without communicating with other information processing devices. As a result, the processes related to using the ticket and displaying the seat acquisition screen can be executed at high speed regardless of the communication status.

[0172] Figure 18 is a schematic diagram showing an example of a seat acquisition screen D1. The seat acquisition screen D1 includes a display object D11. In addition, the seat acquisition screen D1 may display information related to tickets (e.g., information indicating that the ticket has been used) and information related to events (e.g., information related to the event name, venue, date and time, opening time, and start time).

[0173] Display object D11 is an object for displaying information to visitors. Display object D11 may be displayed superimposed on ticket information, event information, etc., displayed on seat acquisition screen D1. Display object D11 includes display object D111, display object D112, and operation object D113.

[0174] Display object D111 displays information such as whether a ticket has been used and whether the visitor has completed their entry.

[0175] Display object D112 displays guidance information to direct attendees to their seats. However, display object D112 does not display any information that could identify a specific seat. By displaying guidance information, display object D112 can guide attendees to a certain area from their seats. This allows attendees to move within a certain range even if they do not know their seat number. Therefore, it is possible to prevent attendees from loitering in specific locations such as around the entrance after entering the venue.

[0176] The guidance information displayed in display object D112 is generated based on the information of the item "Guidance Information" received from server 20 in step S1046 and stored in ticket data 182. Therefore, if terminal device 10 is unable to send ticket arrival data to server 20 (NO in step S1042), terminal device 10 has not received guidance information from server 20, and therefore guidance information will not be displayed in display object D112.

[0177] Meanwhile, after the ticket data is sent to server 20 and guidance information is received from server 20 (after YES in step S1042 to step S1046), the guidance information is displayed on display object D112.

[0178] Operation object D113 is the first object for receiving operations on terminal device 10. Operation object D113 accepts operations to request seat information. Operation object D113 displays information indicating that it is an object for requesting seat information. This allows visitors to understand that they can find out their seat by operating operation object D113. Operation object D113 corresponds to the seat acquisition button in "3) Pressing the seat acquisition button".

[0179] In step S106, the terminal device 10 accepts an input operation to the operation object D113 by the visitor. However, it is possible that the terminal device 10 may accept an operation to the operation object D113 even if it has not been able to send the ticket data to the server 20 and has not received guidance information from the server 20 (guidance information is not displayed on the display object D112). In that case, the terminal device 10 may cancel the processing in step 104 (especially the processing from NO to step S1041 in step S1042) and execute the processing from step S107 onwards.

[0180] In step S107, the terminal device 10 displays a predetermined animation on the display 141 based on receiving an input operation to the operation object D113. Specifically, the terminal device 10 displays an animation screen on the display 141 that displays the predetermined animation.

[0181] Figure 19 is a schematic diagram showing an example of a performance screen D2. Performance screen D2 includes a display object D21. In addition, performance screen D2 may display information related to tickets (e.g., information indicating that the ticket has been used) and information related to the event (e.g., information related to the event name, venue, date and time, opening time, and start time).

[0182] Display object D21 is an object for presenting information to visitors. As shown in Figure 19, display object D21 may be displayed superimposed on ticket information, event information, etc., displayed on the performance screen D2. Display object D21 includes display object D211, display object D212, and display object D213.

[0183] Display object D211 displays information indicating that seat information is being retrieved. This allows visitors to be aware that seat information is being acquired.

[0184] Display object D212 displays a predetermined effect. Specifically, the predetermined effect is one that makes the visitor aware that the acquisition of seat information has started, that the acquisition of seat information is in progress, or that the acquisition of seat information has been completed. The predetermined effect is a combination of at least one still image and one video. An example of the predetermined effect is as follows: • An animation that retrieves a predetermined element (for example, an object such as a ticket, item, or gift). • Presentations related to drawing lots (for example, spinning reels or roulette wheels, systems where prizes are determined randomly (capsule toys, lotteries, raffles, etc.))

[0185] Furthermore, the display object D212 may display different effects based on the seat information associated with the ticket used in step S103. For example, the display object D212 may display different effects based on the seat type, the section to which the seat belongs, the seat number, etc.

[0186] Display object D213 displays a message to the visitor requesting that the terminal device 10 maintain a state where it can communicate. This allows the visitor to be asked to maintain a state that makes it easier for the terminal device 10 to establish a connection with the server 20 when the terminal device 10 executes step S1121, which is included in step S112 described later.

[0187] Furthermore, while the terminal device 10 displays a predetermined performance on the display 141 in step S107, it proceeds with the processing in steps S108, S112, and S113, which are described below. As a result, the processing in steps S108, S112, and S113 proceeds while the visitor is watching the performance, allowing the visitor to experience the waiting time as an entertaining experience. Therefore, the terminal device 10 can proceed with processing that takes a predetermined amount of time without compromising visitor satisfaction.

[0188] In step S108, the terminal device 10 determines whether the transmission of the ticket data to the server 20 was successful (i.e., whether the server 20 has received the ticket data). Specifically, for example, the terminal device 10 refers to the "transmission status" information in the ticket data 182 to determine whether the ticket data has been transmitted from the terminal device 10 to the server 20. Note that, like step S107, step S108 is also executed based on the acceptance of an input operation to the operation object D113.

[0189] If it is determined that the ticket data has not been successfully transmitted (NO in step S108), in step S112, the terminal device 10 transmits the ticket data to the server 20.

[0190] Figure 14 is a flowchart detailing the process (second ticket data transmission process) in step S112, which attempts to transmit the ticket data.

[0191] In step S1121, the terminal device 10 attempts to send the ticket data to the server 20.

[0192] If the terminal device 10 and the server 20 cannot connect (NO in step S1122), the terminal device 10 proceeds with processing, indicating that it failed to transmit the ticket data (NO in step S113).

[0193] If the terminal device 10 and the server 20 are able to connect (YES in step S1122), in step S1123, the server 20 receives the ticket data.

[0194] The processing in steps S1124 to S1126 is the same as the processing in steps S1044 to S1046 of the first ticket data transmission process shown in Figure 13.

[0195] After step S1126, the terminal device 10 proceeds with processing, assuming that it has successfully transmitted the ticket data (YES in step S113).

[0196] Returning to the explanation of Figure 12. If the transmission of the ticket data fails (NO in step S113), the terminal device 10 displays a message on the display 141 indicating that the transmission of the ticket data was not completed successfully. Specifically, for example, the terminal device 10 displays on the display 141 messages indicating that the transmission of the ticket data was not completed successfully, that seat information could not be obtained successfully, and that it is requesting further operation on the terminal device 10 (specifically, input operation to operation object D113).

[0197] After step S114, the process returns to step S105. That is, the terminal device 10 displays the seat acquisition screen D1 on the display 141 again. Note that the terminal device 10 does not have to display the seat acquisition screen D1; at the very least, it may display an object on the display 141 that accepts an operation to request seat information.

[0198] The terminal device 10 may restart the first ticket data transmission process in step S104 based on the execution of step S105 again.

[0199] If it is determined that the ticket data has been successfully transmitted (i.e., the server 20 has determined that the ticket data has been received) (YES in step S108), or if the ticket data has been successfully transmitted in the process shown in Figure 14 (YES in step S113), in step S109, the terminal device 10 displays a display request screen on the display 141, which is a screen for visitors to request the display of seat information related to their ticket.

[0200] Figure 20 is a schematic diagram showing an example of a display request screen D3. The display request screen D3 includes a display object D31. In addition, the display request screen D3 may display information related to tickets (e.g., information indicating that the ticket has been used) and information related to events (e.g., information related to the event name, venue, date and time, opening time, and start time).

[0201] Display object D31 is an object for displaying information to visitors. As shown in Figure 20, display object D31 may be displayed superimposed on ticket information, event information, etc., displayed on display request screen D3. Display object D31 has display object D311 and operation object D312.

[0202] Display object D311 displays information indicating that the acquisition of seat information has been completed. This allows visitors to recognize that the acquisition of seat information by terminal device 10 has been completed.

[0203] Operation object D312 accepts operations to request the display of seat information.

[0204] Incidentally, when multiple attendees participate in an event together, if they all learn their seating information at the same time, they can share the experience of discovering their seat location, as well as their feelings and impressions about knowing their seat location. Therefore, having multiple attendees learn their seating information at the same time enhances the entertainment value and satisfaction of their event participation and ticket usage experience.

[0205] On the other hand, the processing steps differ depending on whether the ticket data was successfully transmitted in step S104 and the system determined to have successfully transmitted the ticket data in step S108, or whether the ticket data was not transmitted in step S104, the system determined to have not successfully transmitted the ticket data in step S108, and the system transmitted the ticket data in step S113. As a result, the time required for the terminal device 10 to process the data may differ. Furthermore, the time required for the terminal device 10 to process the data may also differ depending on the communication status of each visitor's terminal device 10.

[0206] Therefore, if, after the performance in step S107, the display request screen D3 including the operation object D312 is not displayed, and the seat information is displayed on the display 141, the timing of displaying the seat information will differ depending on whether the ticket data transmission was successful in step S104 and the system determined that the ticket data transmission was successful in step S108, or whether the ticket data was not transmitted in step S104 and the system determined that the ticket data transmission was unsuccessful in step S108 and the ticket data was transmitted in step S113, as well as the communication status of the terminal device 10. Consequently, even if multiple visitors want to know the seat information at the same time, the timing at which the seat information is displayed on the display 141 of each visitor's terminal device 10 may differ depending on the status of the ticket data transmission and the communication status of the terminal device 10.

[0207] Therefore, in the seat display processing of this embodiment, the terminal device 10 displays the operation object D312 (second object) in the same way whether it succeeded in transmitting the ticket data in step S104, or whether it failed to transmit the ticket data in step S104 but transmitted the ticket data in step S113. As a result, multiple visitors can easily synchronize the timing of learning their seat information by simultaneously operating the operation object D312 displayed on their respective terminal devices 10. Thus, by informing multiple visitors of their seat information at the same time, satisfaction with the event participation and ticket usage experience can be improved.

[0208] When a visitor performs an input operation on the operation object D312, in step S110, the terminal device 10 accepts the input operation. Based on the acceptance of the input operation, the terminal device 10 refers to the ticket data 182 and obtains the information for the item "seat information".

[0209] In step S111, the terminal device 10 displays seat information on the display 141. Specifically, the terminal device 10 displays a seat information screen D4 on the display 141. Here, the processes in steps S110 and S111 can be completed within the terminal device 10 without communication between the terminal device 10 and other information processing devices. Therefore, if multiple visitors operate the operation object D312 simultaneously on their respective terminal devices 10, there is a high probability that seat information will be displayed on each of their displays 141 at the same time. Thus, seat information can be more reliably provided to multiple visitors at the same time.

[0210] Figure 21 is a schematic diagram showing an example of a seat display screen D4. The seat display screen D4 includes a display object D41. In addition, the seat display screen D4 may display information related to tickets (e.g., information indicating that the ticket has been used) and information related to events (e.g., information related to the event name, venue, date and time, opening time, and start time).

[0211] Display object D41 is an object for presenting information to visitors. As shown in Figure 21, display object D41 may be displayed superimposed on ticket information, event information, etc., displayed on seat display screen D4. Display object D41 includes display object D411, display object D412, and operation object D413.

[0212] Display object D411 displays information indicating that the acquisition of seat information has been completed.

[0213] Display object D412 displays seat information. Specifically, display object D412 displays information used to identify the seat location, which the terminal device 10 obtained from the "Seat Information" item in the ticket data 182. This allows visitors to confirm the location of their seat.

[0214] Operation object D413 accepts an operation to close display object D41 (hide it from the seat display screen D4). When operation object D413 accepts an operation from a visitor, terminal device 10 hides display object D41.

[0215] After step S111, the seat display process of the first embodiment is terminated.

[0216] (Second Embodiment) The seat display processing of the second embodiment will now be described. Descriptions that overlap with those of the first embodiment will be omitted. Figure 15 is an explanatory diagram illustrating the overview of the second embodiment.

[0217] 1) Use of ticket As shown in Figure 15, the ticket inspection device 30 performs ticket inspection, for example, at a ticket inspection station at an event venue. Specifically, the camera 360 of the ticket inspection device 30 photographs the ticket presented by the visitor and the visitor. For example, the camera 360 of the ticket inspection device 30 photographs the ticket displayed on the display 141 of the terminal device 10 (for example, the code displayed on the ticket) and the visitor's face. In the example in Figure 15, the camera 360 of the ticket inspection device 30 photographs the ticket displayed on the terminal device 10, but it may also photograph a ticket attached to a medium other than the terminal device 10 (for example, paper). From the image captured by the camera 360, the ticket inspection device 30 obtains the ticket data 182 of the ticket and the visitor's features (for example, facial features).

[0218] The ticket inspection device 30 determines whether a visitor is allowed to enter by referring to the information obtained from the photographed ticket and the characteristic quantities of the photographed visitor.

[0219] 2) Sending ticket data The ticket inspection device 30 sends the ticket receipt data to the server 20 for the tickets that were marked as used in 1). The server 20 updates the receipt status of the ticket receipt data to "received" for the tickets for which it has received the data.

[0220] 3) Press the seat acquisition button. The display 141 of the terminal device 10 displays a "seat acquisition button" at a predetermined time. When a visitor presses the seat acquisition button after entering the venue, the terminal device 10 queries the server 20 to see if the server has received the ticket data 182 stored in the storage unit 180. If the server 20 has received the ticket data, the server 20 transmits the seat information related to the ticket data 182 to the terminal device 10. The terminal device 10 displays the received seat information on the display 141. This allows visitors to confirm their seat information by pressing the "seat acquisition button".

[0221] On the other hand, before the visitor enters the venue, that is, before the ticket usage process is performed in 1), the server 20 has not yet received the ticket data from the ticket inspection device 30. Therefore, even if the visitor presses the seat acquisition button before entering the venue and the terminal device 10 queries the server 20, the server 20 will not provide seat information to the terminal device 10 because it has not yet received the ticket data. Consequently, in this case, the visitor cannot confirm their seat information.

[0222] Therefore, in order for visitors to confirm their seats, they must use their tickets at a ticket inspection station equipped with a ticket inspection device 30, and the ticket inspection device 30 must transmit the ticket data to the server 20. As a result, the server 20 can more reliably store information regarding ticket usage (i.e., the visitor's entry status).

[0223] Figure 16 is a flowchart of the ticket inspection process performed in the use of a ticket in the second embodiment.

[0224] In step S201, the ticket inspection device 30 reads the ticket. Specifically, for example, when a visitor presents their ticket, the control unit 390 uses the camera 360 to photograph the ticket and obtains the ticket ID and check data from the code contained in the ticket. At this time, the ticket inspection device 30 may also present the image captured by the camera 360 to the visitor by displaying it on the display 341. This allows the visitor to receive feedback on how their ticket is being photographed and to be prompted to make minor adjustments to the position and orientation of the ticket.

[0225] In step S202, the ticket inspection device 30 acquires feature data. Specifically, when a visitor presents their ticket, the ticket inspection device 30 acquires the visitor's feature data (for example, facial feature data) using the camera 360. At this time, the ticket inspection device 30 may also present the image captured by the camera 360 to the visitor by displaying it on the display 341. This allows the visitor to receive feedback on how they are being photographed and encourages them to make minor adjustments to their position and posture.

[0226] In step S203, the ticket inspection device 30 determines whether or not entry is permitted. Specifically, the ticket inspection device 30 refers to the check data acquired in step S201 and the feature quantities acquired in step S202 to determine whether or not the visitor is permitted entry. For example, the ticket inspection device 30 determines from the features stored in the feature table 3811 that have a predetermined similarity to the visitor's features acquired in step S202, and identifies the feature ID related to that feature. Then, based on the identified feature ID, the ticket ID acquired in step S201, and the event ID included in the ticket inspection data 381, it performs a predetermined calculation to generate check data. The ticket inspection device 30 determines that if the generated check data matches the check data acquired in step S201, it will allow the visitor to enter; otherwise, it determines that it will refuse the visitor's entry.

[0227] In other words, the ticket inspection device 30 allows entry to the visitor if it determines that the purchaser of the presented ticket is the same person as the visitor, and refuses entry to the visitor if it does not determine that the purchaser of the ticket is the same person as the visitor. As a result, visitors cannot enter by presenting tickets purchased through unofficial channels, thus deterring the illegal resale of tickets.

[0228] Furthermore, the ticket inspection device 30 does not need to acquire feature quantities in step S202. In that case, the ticket inspection device 30 does not need to acquire check data from the code contained in the ticket. In that case, the ticket inspection device 30 may query the ticket table 2022 of the server 20 to determine whether the ticket associated with the ticket ID obtained from the code contained in the ticket is valid, whether it has already been used, etc. If the ticket associated with the ticket ID is valid, it may decide to allow the visitor to enter, and if the ticket associated with the ticket ID is invalid, it may decide to refuse the visitor to enter.

[0229] If the ticket inspection device 30 determines in step S204 that it should refuse entry to the visitor, in step S205 the ticket inspection device 30 performs entry error processing. Specifically, the ticket inspection device 30 performs at least one of the following processes: • Alarm activation (for example, by illuminating a lamp, emitting a predetermined sound, displaying a predetermined screen, or a combination thereof, the system will notify the visitor and staff that their entry has been denied, and will prompt staff to provide aftercare.) • Closing gates (for example, closing the bars of an electric gate or flap doors to physically prevent visitors from entering) Furthermore, to prevent congestion near the ticket inspection device 30, aftercare by staff may be provided after visitors have been conveniently allowed into the venue. Aftercare by staff may include interactions to determine whether or not a visitor is the true purchaser of the ticket. For example, staff may ask visitors for their attribute information, contact information, place of purchase, date of purchase, or a combination thereof, and compare this information with the ticket data. After step S205, the ticket inspection process is complete.

[0230] If it is determined in step S204 to allow the visitor to enter, in step S206 the ticket inspection device 30 executes the entry permission process. Specifically, the ticket inspection device 30 performs at least one of the following processes: • Notification that entry has been permitted (for example, by lighting a lamp, emitting a designated sound, displaying a designated screen, or a combination thereof, the visitor and staff will be made aware that entry has been permitted). • Open the gate (for example, open the bars or flap doors of an electric gate to allow visitors to enter)

[0231] In step S207, the ticket inspection device 30 transmits the ticket data to the server 20. Specifically, the ticket inspection device 30 transmits ticket data to the server 20 for tickets related to the determination made in step S203 that permit the visitor's entry.

[0232] When server 20 receives ticket data, it searches ticket table 2022 using the ticket ID included in the ticket data and updates the information stored in the "Receipt Status" field of the corresponding record to "Received". After step S207, the ticket inspection process is complete.

[0233] Figure 17 is a flowchart of the seat display process in the second embodiment.

[0234] First, the terminal device 10 runs an application for displaying seat information. Note that the display of seat information may be performed via a web browser. Furthermore, the function related to displaying seat information may be included in or associated with an application executed by the terminal device 10 when the ticket is presented in step S201 of the ticket inspection process.

[0235] In step S301, the terminal device 10 displays a seat acquisition screen on the display 141, which is a screen for visitors to perform operations to acquire a seat. The terminal device 10 may also execute step S301 at a predetermined timing. A predetermined timing is, for example, the following: (Specific time) • Event opening time • The time before the scheduled start time of the event • A specific time on the day of the event

[0236] Figure 22 is a schematic diagram showing an example of the seat acquisition screen D5 in the second embodiment. The seat acquisition screen D5 includes a display object D51. In addition, the seat acquisition screen D5 may display information related to the ticket (for example, a code related to ticket data 182) and information related to the event (for example, information related to the event name, venue, date and time, opening time, and start time).

[0237] Display object D51 is an object for displaying information to visitors. As shown in Figure 22, display object D51 may be displayed superimposed on ticket information, event information, etc., displayed on seat acquisition screen D5. Display object D51 includes display object D511, operation object D512, operation object D513, and operation object D514.

[0238] Display object D511 displays a message. The message may include, for example, that the time has reached a predetermined point, that visitors are now allowed to enter the venue, and instructions on how to enter (for example, instructions on presenting tickets to the ticket inspection device 30). The message may also include instructions on how to press an object to retrieve seat information after entering (i.e., after using the ticket). The message may also include a message regarding the pressing of the object for obtaining seat information, which should be done when the terminal device 10 is able to communicate.

[0239] Operation object D512 is an object that accepts an operation requesting the display of a ticket. For example, when terminal device 10 accepts an operation request to operation object D512, it displays the ticket on display 141.

[0240] Operation object D513 (the first object) accepts an operation requesting the acquisition of seat information. Operation object D513 displays information indicating that it is an object for requesting seat information. This allows visitors to understand that they can find out their seat by operating operation object D513. Operation object D513 corresponds to the seat acquisition button in "3) Pressing the seat acquisition button".

[0241] The operation object D514 receives an operation for closing the display object D51 (making it non-displayed from the seat acquisition screen D5). When the operation object D514 receives an operation from the visitor, the terminal device 10 makes the display object D51 non-displayed.

[0242] In step S302, the terminal device 10 receives a seat information acquisition request from the visitor. Specifically, the terminal device 10 receives an input operation on an object (operation object D513) for requesting the acquisition of seat information, which is displayed on the display 141.

[0243] In step S303, based on receiving the seat information acquisition request from the visitor, the terminal device 10 displays a predetermined effect on the display 141. Specifically, the terminal device 10 displays an effect screen for displaying the predetermined effect on the display 141.

[0244] FIG. 19 is a schematic diagram showing an example of the effect screen D2. The effect screen D2 displayed in step S303 is common to the effect screen D2 displayed in step S107 of the first embodiment. Note that information indicating that the ticket has been used may not be displayed on the effect screen D2 in the second embodiment.

[0245] Note that while the terminal device 10 is displaying a predetermined effect on the display 141 in step S303, it proceeds with the processing of steps S304 to S309 described below. As a result, since the processing of steps S304 to S309 proceeds while the visitor is enjoying the effect, the waiting time for the processing can be made to be felt by the visitor as an entertaining time. Therefore, the terminal device 10 can proceed with the processing having a predetermined time for progress without impairing the satisfaction of the visitor.

[0246] In step S304, the terminal device 10 determines whether the server 20 has received the ticket data related to the ticket data 182 stored in the storage unit 180 from the ticket inspection device 30. Specifically, for example, the terminal device 10 sends the ticket ID stored in the "ticket ID" item of the ticket data 182 to the server 20, and the server 20 queries whether it has received the ticket data related to the ticket ID and makes a decision based on the query result sent from the server 20.

[0247] In step S305, when the server 20 receives an inquiry from the terminal device 10, it checks whether or not it has received the ticket data related to the received ticket ID. Specifically, the server 20 searches the ticket table 2022 based on the received ticket ID and retrieves the information of the "Reception Status" field of the corresponding record. If the information of the "Reception Status" field indicates that the ticket data has been received, the server 20 determines that the ticket data has been received. If the information of the "Reception Status" field indicates that the ticket data has not been received, the server 20 determines that the ticket data has not been received.

[0248] If the server determines in step S305 that the ticket data has been received (YES in step S306), in step S307, the server 20 retrieves the guidance information stored in the "guidance information" field and the seat information stored in the "seat information" field of the record retrieved in step S305. The server 20 then transmits the information regarding the receipt of the ticket data, the guidance information, and the seat information to the terminal device 10.

[0249] If it is determined in step S305 that the ticket data has not been received (NO in step S306), then in step S308, the server 20 sends information to the terminal device 10 indicating that the ticket data has not been received.

[0250] The terminal device 10 receives information transmitted from the server 20 in step S307 or step S308. The terminal device 10 refers to the received information and determines whether the server 20 has already received the ticket data. Specifically, the terminal device 10 determines whether the received information includes information indicating that the ticket data has been received or information indicating that the ticket data has not been received.

[0251] If the terminal device 10 determines that the server 20 has not received the ticket data (NO in step S309), it displays an error message on the display 141 in step S313. The error message may include, for example, at least one of the following messages. • A message instructing you to request seating again after using your ticket. • A message instructing attendees to request seating again after entering the venue. • A message instructing you to request a seat again after a specified period of time has elapsed. • A message instructing the terminal device 10 to request a seat again once the communication status of the terminal device 10 is good.

[0252] If the terminal device 10 determines that the server 20 has received the ticket data (YES in step S309), it stores the received guidance information and seat information in the "Guidance Information" and "Seat Information" fields of the ticket data 182. Then, in step S310, the terminal device 10 displays a display request screen on the display 141, which is a screen for visitors to request the display of seat information related to their ticket.

[0253] Figure 20 is a schematic diagram showing an example of the display request screen D3. The display request screen D3 displayed in step S310 is the same as the display request screen D3 displayed in step S109 of the first embodiment.

[0254] In step S310, the terminal device 10 may display the guidance information received in step S307 on the display request screen D3. This allows visitors to be guided to a certain area from their seats. As a result, visitors can move to a certain area even if they do not know their seat number. Therefore, it is possible to prevent visitors who have entered the venue from loitering in specific locations such as around the entrance.

[0255] However, even if multiple visitors simultaneously press the seat acquisition button displayed on their respective terminal devices 10 with the aim of obtaining seat information at the same time, the processing speed of each terminal device 10 may differ depending on the communication conditions, etc.

[0256] Therefore, if, after the performance in step S303, the display request screen D3 including the operation object D312 is not displayed, and the seat information is displayed on the display 141, the timing of the display of the seat information will differ among the terminal devices 10. In that case, even if multiple visitors want to know the seat information at the same time, depending on the communication status of the terminal devices 10, the timing at which the seat information is displayed on the display 141 of the terminal devices 10 may differ.

[0257] Therefore, in the seat display processing of the second embodiment, the terminal device 10 does not display the seat information immediately after the performance in step S303, but instead displays the display request screen D3. This allows multiple visitors to easily synchronize the timing of learning about their seat information by simultaneously operating the operation object D312 displayed on their respective terminal devices 10. Thus, by informing multiple visitors of their seat information at the same time, satisfaction with the event participation and ticket usage experience can be improved.

[0258] When a visitor performs an input operation on the operation object D312, in step S311, the terminal device 10 accepts the input operation. Based on the acceptance of the input operation, the terminal device 10 refers to the ticket data 182 and obtains the information for the item "seat information".

[0259] In step S312, the terminal device 10 displays seat information on the display 141. Specifically, the terminal device 10 displays a seat information screen D4 on the display 141. Here, the processes in steps S311 and S312 can be completed within the terminal device 10 without communication between the terminal device 10 and other information processing devices. Therefore, if multiple visitors operate the operation object D312 on their respective terminal devices 10 at the same time, there is a high probability that seat information will be displayed on each of their displays 141 simultaneously. Thus, seat information can be more reliably provided to multiple visitors at the same time.

[0260] Figure 21 is a schematic diagram showing an example of the seat display screen D4. The seat display screen D4 displayed in step S311 is the same as the seat display screen D4 displayed in step S111 of the first embodiment.

[0261] After step S312, the seat display process of the second embodiment is terminated.

[0262] (Effects of not storing seat information in ticket data 182) As described in the seat display processing of the first embodiment and the seat display processing of the second embodiment, the terminal device 10 does not hold the guidance information and seat information in the ticket data 182 unless it receives the guidance information and seat information from the server 20. Therefore, compared with the case where the guidance information and seat information are held in the ticket data 182 in the ticket issuing process, the provider of the service according to the present embodiment can delay the timing of registering the guidance information and seat information in the ticket table 2022 until immediately before the visitor enters the venue. That is, until immediately before the visitor enters the venue, it is possible to delay the determination of the seat assigned to each ticket or change the already assigned seat. Therefore, even if the consideration of the seat arrangement is delayed or the seat arrangement is changed for some reason, various operations related to the assignment of seats to tickets (such as registering seats on tickets and replacing seats) can be performed flexibly.

[0263] <Modified Example> (Modified Example 1) In the above embodiment, the guidance information and seat information were not included in the ticket data 182 generated by the server 20 in the ticket issuing process and stored in the terminal device 10.

[0264] In the seat display processing of the first embodiment, based on the terminal device 10 transmitting the ticket arrival data to the server 20 in the first ticket arrival data transmission process or the second ticket arrival data transmission process, the server 20 transmitted the guidance information and seat information to the terminal device 10. Then, the terminal device 10 stored the guidance information and seat information received from the server 20 in the ticket data 182.

[0265] In the seat display processing of the second embodiment, the terminal device 10 inquired whether the server 20 had received the ticket arrival data. When the server 20 had received the ticket arrival data, the server 20 transmitted the guidance information and seat information to the terminal device 10. Then, the terminal device 10 stored the guidance information and seat information received from the server 20 in the ticket data 182.

[0266] However, the ticket data 182 generated by the server 20 during the ticketing process and stored in the terminal device 10 may include guidance information and seat information.

[0267] Therefore, in this modified example, in the seat display processing of the first embodiment, in the first ticket data transmission processing or the second ticket data transmission processing, the server 20 does not need to transmit guidance information and seat information to the terminal device 10 based on the terminal device 10 transmitting the ticket data to the server 20. Also, in the seat display processing of the second embodiment, when the terminal device 10 queries the server 20 to see if the ticket data has been received, the server 20 does not need to transmit guidance information and seat information to the terminal device 10 if the ticket data has been received.

[0268] In this modified version, unlike the above embodiment, the terminal device 10 retains the guidance information and seat information at least after the ticketing process is completed. Even in this case, the terminal device 10 displays the guidance information and seat information in the same steps as in the above embodiment. That is, after the server 20 determines that it has received the ticket data, the terminal device 10 displays the guidance information and seat information that were previously stored during the ticketing process.

[0269] Furthermore, in this modified version, unlike the above embodiment, the terminal device 10 retains guidance information and seat information at least from the time the ticketing process is completed. Therefore, for example, a staff member may perform a specific operation on the terminal device 10 to display the guidance information and seat information held by the terminal device 10. For example, if the terminal device 10 and the server 20 are unable to communicate during the seat display process (in the first embodiment, the terminal device 10 is unable to send ticket data to the server 20, or in the second embodiment, the terminal device 10 is unable to inquire to the server 20 whether or not the ticket data has been received), attendees may still be unable to confirm their seats even immediately before the event starts. In that case, the terminal device 10 may display the seat information and guidance information included in the ticket data 182 by accepting a specific operation from a staff member. This allows attendees to confirm their seats even if the terminal device 10 and the server 20 are unable to communicate.

[0270] Furthermore, the terminal device 10 may display seat information and guidance information included in the ticket data 182 if communication between the terminal device 10 and the server 20 continues to be impossible at a predetermined time (for example, a predetermined time before the start of the performance, or at a time when attendees can move to their seats before the start of the performance). This allows attendees to confirm their seat and, for example, move to their seat before the start of the performance, even if communication between the terminal device 10 and the server 20 continues to be impossible.

[0271] (Modification 2) In the above embodiment, in the seat display processing of the first embodiment, the terminal device 10 transmitted the ticket data by executing the first ticket data transmission process based on the fact that the ticket had been used. The terminal device 10 then determined whether or not the transmission of the ticket data to the server 20 was successful based on the input operation to the operation object D113, and if it was not successful, it attempted to transmit the ticket data to the server 20 again.

[0272] However, in the seat display processing of the first embodiment, the terminal device 10 may not perform the first ticket data transmission processing, but only the second ticket data transmission processing.

[0273] In this case, the terminal device 10 does not perform the first ticket data transmission process, so the ticket data is not sent from the terminal device 10 to the server 20 before the determination of whether or not the ticket data transmission was successful in step S108. Therefore, in this modified example, the terminal device 10 may perform step S112 (second ticket data transmission process) without performing step S108, based on receiving an input operation related to the seat acquisition request (input operation to operation object D513) in step S106.

[0274] In other words, in this modified example, the terminal device 10 receives an input operation related to a seat acquisition request (an input operation to the operation object D513) in step S106, and transmits the ticket data in step S1121. Then, based on the server 20 receiving the ticket data in step S1123 and transmitting the seat information to the terminal device 10 in step S1125, the terminal device 10 receives the seat information (step S1126) and displays the received seat information on the display 141 (step S111).

[0275] Furthermore, in this modified example, the terminal device 10 does not perform step S108. Therefore, in step S107, while the terminal device 10 is displaying a predetermined animation on the display 141, it performs step S112 (transmission of the second ticket data).

[0276] (Variation 3) In the above embodiment, during the seat display process, the terminal device 10 received guidance information and seat information from the server 20, and then presented the guidance information and seat information to visitors by displaying them on the display 141. However, the information received from the server 20 and presented to visitors is not limited to guidance information and seat information. The information received from the server 20 and presented to visitors may be predetermined information that is useful to visitors. The predetermined information may be, for example, information relating to the following: • A voucher redeemable for a product or benefit. Visitors can receive a product or benefit by presenting the voucher displayed on terminal device 10 to a staff member. • A raffle ticket that allows participants to win a prize or benefit. Visitors can participate in the raffle by presenting the raffle ticket displayed on terminal device 10 to staff or by performing a prescribed operation on the raffle ticket displayed on terminal device 10. • Image data (including still images and videos), audio data, and text data (for example, image data, audio data, and text data related to an event or event performers. As an example, image data, audio data, and text data created by event performers for attendees). • Points that can be used as a substitute for money in the services related to this disclosure. Points may be accumulated in association with the visitor's user ID when the visitor performs a predetermined operation on the terminal device 10, or automatically.

[0277] (Modification 4) In the seat display process of the first embodiment, if the terminal device 10 determines that it has successfully transmitted the ticket data (i.e., if the server 20 determines that it has received the ticket data) (YES in step S108), or if it has transmitted the ticket data in the process shown in Figure 14 (YES in step S113), in step S109 the terminal device 10 displays a display request screen on the display 141, which is a screen for visitors to request the display of seat information related to their ticket. Then, in response to receiving an operation on the display request screen in step S110, it displays the seat information in step S111. Furthermore, in the seat display processing of the second embodiment, the terminal device 10, when it determined that the server 20 had received ticket data from the ticket inspection device 30 (YES in step S309), displayed a display request screen on the display 141, which is a screen for visitors to request the display of seat information related to their ticket. Then, in response to accepting an operation on the display request screen in step S311, the terminal device 10 displayed the seat information in step S312. However, if the terminal device 10 determines that it has successfully transmitted the ticket data, and has transmitted the ticket data in the process shown in Figure 14, it may display the seat information without performing the step of displaying the display request screen. In other words, the terminal device 10 may display the seat information based on the determination that it has successfully transmitted the ticket data and that it has transmitted the ticket data in the process shown in Figure 14.

[0278] (Other variations) In the seat display process of the above embodiment, an event attendee operated the terminal device 10. However, a person other than an attendee (for example, an event venue staff member) may operate the terminal device 10 and advance each step of the seat display process on the terminal device 10.

[0279] In the seat display processing of the above embodiment, as shown in Figures 18 to 22, the terminal device 10 displayed various information on the display 141. However, in addition to displaying various information on the display 141, or instead, the terminal device 10 may present various information to visitors by outputting audio information (such as voice messages) from the speaker 172.

[0280] In the above embodiment, an example was shown in which each step in each process is executed in a specific order. However, the execution order of each step is not limited to the example described, unless there is a dependency. In particular, unless a contradiction arises, the process executed by the terminal device 10 may be executed by the server 20 or the ticket inspection device 30, the process executed by the server 20 may be executed by the terminal device 10 or the ticket inspection device 30, and the process executed by the ticket inspection device 30 may be executed by the terminal device 10 or the server 20.

[0281] <Summary> As described above, the terminal device 10 performs the following steps: marking the ticket as used; sending ticket data, which is information that the ticket has been used, to the server based on the fact that the ticket has been used; displaying a first object on the computer's display unit for accepting operations to the computer; accepting operations to the first object; determining whether the transmission of the ticket data was successful based on the acceptance of the operations; and, if it is determined in the determination step that the transmission of the ticket data was successful, displaying information about the seat associated with the ticket on the display unit. As a result, terminal device 10 cannot obtain seat information and therefore cannot present seat information to attendees until it transmits ticket data to server 20. On the other hand, attendees need to check the seat information presented by terminal device 10 in order to move to their seats. Therefore, server 20 receives ticket data related to attendees during the process of attendees moving to their seats. This makes it possible to more reliably store information regarding ticket usage (in other words, attendee entry status) in server 20 from the time attendees begin entering the venue until they move to their seats and the event begins. Consequently, event organizers and venue managers can more accurately grasp the attendee entry status by checking the information stored in server 20.

[0282] Furthermore, in the step of displaying the first object, the terminal device 10 displays information on its display unit indicating that the operation on the first object is an operation to request information about the seat associated with the ticket. This makes it easy for visitors to understand that they can find out their seat by interacting with the first object.

[0283] Furthermore, if the terminal device 10 determines that it has successfully transmitted the ticket data, it will perform a step to receive information about the seat associated with the ticket from the server, and in the step to display the seat information, it will display the seat information associated with the ticket that it received from the server. As a result, terminal device 10 can receive seat information from server 20 in response to the transmission of ticket data.

[0284] Furthermore, in the step of receiving seat information, the terminal device 10 receives from the server information that identifies the seat and information different from the seat identification information that is used to guide the user to the seat location. Based on the receipt of seat information from the server, the processor performs the step of displaying the seat location guidance information on the display unit, and in the step of displaying seat information, it displays seat identification information. This allows visitors to be guided to their seats before they even know their assigned seats.

[0285] Furthermore, if the terminal device 10 determines in the decision-making step that it has not succeeded in transmitting the ticket data, it performs a step of resending the ticket data to the server, and in the resending step, based on the fact that the ticket data has been sent to the server, it displays information about the seat associated with the ticket on the display unit. This allows the terminal device 10 to transmit ticket data more reliably.

[0286] Furthermore, in the step of retransmitting, the terminal device 10 receives information about the seat associated with the ticket from the server based on the sending of the ticket data to the server, and in the step of displaying the seat information, it displays the seat information associated with the ticket that it received from the server. As a result, terminal device 10 can receive seat information from server 20 based on the re-transmission of ticket data. Therefore, based on the re-transmission of ticket data, visitors will be able to find out their seat.

[0287] Furthermore, in the step of receiving an operation on the first object, the terminal device 10, based on receiving an operation on the first object, causes the display unit to perform a step of displaying a predetermined effect, and while the predetermined effect is being displayed, it performs a step of making a decision and a step of transmitting again. This allows the waiting time for the terminal device 10 to process to be provided to visitors as an entertaining experience.

[0288] Furthermore, regardless of whether the terminal device 10 determines in the decision-making step that the transmission of the ticket data was successful, it causes the display unit to perform a step of displaying a second object for accepting operations to the computer, and in the step of displaying seat information, it displays seat information based on the acceptance of operations to the second object. This allows multiple attendees to access seating information at the same time by synchronizing the operation timing of the second object when attending an event together.

[0289] Furthermore, the System 1 of this Disclosure includes means for marking a ticket as used, a step of sending ticket data, which is information that the ticket has been used, to a server based on the fact that the ticket has been marked as used, means for displaying a first object on a computer display unit for accepting operations to the computer, means for accepting operations to the first object, means for determining whether or not the transmission of the ticket data was successful based on the acceptance of the operations, and, if the determination means determines that the transmission of the ticket data was successful, means for displaying information about the seat associated with the ticket on the display unit.

[0290] Furthermore, the terminal device 10 performs the following steps: displaying a first object for receiving operations to the computer on the computer's display unit; receiving operations to the first object; based on receiving the operations, sending ticket data, which is information that the ticket has been used, to the server; and based on sending the ticket data, displaying information about the seat associated with the ticket on the display unit. As a result, terminal device 10 cannot obtain seat information and cannot present seat information to attendees until it receives an operation on the first object and transmits ticket data to server 20. On the other hand, attendees need to check the seat information presented by terminal device 10 in order to move to their seats. Therefore, server 20 receives ticket data related to attendees during the process of attendees moving to their seats. This makes it possible to more reliably store information regarding ticket usage (in other words, attendee entry status) in server 20 from the time attendees start entering the venue until they move to their seats and the event begins. Consequently, event organizers and venue managers can more accurately grasp the attendee entry status by checking the information stored in server 20.

[0291] Furthermore, in the transmission step, the terminal device 10 receives information about the seat associated with the ticket from the server, and in the step of displaying the seat information, it displays the seat information associated with the ticket that it received from the server. As a result, terminal device 10 can receive seat information from server 20 in response to the transmission of ticket data.

[0292] Furthermore, the terminal device 10 causes the processor to perform a step of displaying a predetermined effect on the display unit based on the acceptance of an operation on the first object in the step of accepting an operation on the first object, and performs a transmission step while the predetermined effect is being displayed. This allows the waiting time for the terminal device 10 to process to be provided to visitors as an entertaining experience.

[0293] Furthermore, the System 1 of this Disclosure includes means for displaying a first object for receiving operations on the computer on the computer's display unit, means for receiving operations on the first object, means for transmitting ticket data, which is information that the ticket has been used, to a server based on the acceptance of the operation, and means for displaying information about the seat associated with the ticket on the display unit based on the transmission of the ticket data.

[0294] <Basic Computer Hardware Configuration> Figure 23 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 includes at least a processor 94, main memory 95, auxiliary storage 96, and a communication interface 99. These are electrically connected to each other by a bus.

[0295] The processor 94 is hardware for executing the instruction set written in a program. The processor 94 consists of an arithmetic unit, registers, peripheral circuits, etc.

[0296] Main memory 95 is used to temporarily store programs and data processed by programs, etc. For example, it is volatile memory such as DRAM (Dynamic Random Access Memory).

[0297] Auxiliary storage device 96 refers to a storage device for saving data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

[0298] A communication IF99 is an interface for inputting and outputting signals for communication with other computers via a network using wired or wireless communication standards.

[0299] A network consists of various mobile communication systems built using the internet, LANs, wireless base stations, etc. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0300] Furthermore, by distributing all or part of each hardware configuration across multiple computers 90 and connecting them to each other via a network, a computer 90 can be virtually realized. Thus, the concept of computer 90 includes not only a computer 90 housed in a single enclosure or case, but also a virtualized computer system.

[0301] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 shown in Figure 14 will be explained. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.

[0302] Furthermore, the functional units of computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 interconnected via a network. The concept of computer 90 includes not only a single computer 90 but also a virtualized computer system.

[0303] The control unit is realized when the processor 94 reads various programs stored in the auxiliary storage device 96, loads them into the main memory device 95, and executes processing according to those programs. The control unit can realize various functional units that perform information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0304] The memory unit is implemented by a main memory 95 and an auxiliary memory 96. The memory unit stores data, various programs, and various databases. The processor 94 can also reserve memory areas corresponding to the memory unit in the main memory 95 or the auxiliary memory 96 according to the program. The control unit can also cause the processor 94 to perform operations such as adding, updating, and deleting data stored in the memory unit according to the various programs.

[0305] A database, specifically a relational database, is used to manage and link data sets called tables, which are structurally defined by rows and columns. In a database, tables are called tables, the columns of a table are called columns, and the rows of a table are called records. In a relational database, relationships can be established and linked between tables.

[0306] Typically, each table has a key column to uniquely identify records, but setting a key on a column is not mandatory. The control unit can instruct the processor 94 to add, delete, or update records in specific tables stored in the memory unit according to various programs.

[0307] The communication unit is implemented by the communication IF99. The communication unit provides the functionality to communicate with other computers 90 via the network. The communication unit can receive information transmitted from other computers 90 and input it to the control unit. The control unit can cause the processor 94 to perform information processing on the received information according to various programs. The communication unit can also transmit information output from the control unit to other computers 90.

[0308] The functions realized by the components described herein may be implemented in a circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the functions described herein. A processor includes transistors and other circuits and is considered a circuitry or processing circuitry. A processor may be a programmed processor that executes a program stored in memory. In this specification, circuitry, unit, and means are hardware programmed to perform or execute the functions described herein. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to perform or execute the functions described herein. If the hardware is a processor that is considered to be a type of circuitry, then the circuitry, means, or unit is a combination of hardware and software used to constitute the hardware and / or processor.

[0309] While several embodiments of this disclosure have been described above, these embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications are permitted without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0310] <Note> The details described in each of the above embodiments are noted below. (Note 1) A program for operating a computer, the program causing the computer's processor to execute the following steps: marking a ticket as used; sending ticket data, which is information that the ticket has been used, to a server based on the fact that the ticket has been used; displaying a first object on the computer's display unit for accepting operations to the computer; accepting operations to the first object; determining whether the transmission of the ticket data was successful based on the acceptance of the operations; and, if it is determined in the determination step that the transmission of the ticket data was successful, displaying information about the seat associated with the ticket on the display unit. (Note 2) The program as described in Appendix 1, wherein in the step of displaying a first object, information is displayed on the display unit indicating that the operation on the first object is an operation to request information about a seat associated with a ticket. (Note 3) The program described in Appendix 1 or Appendix 2, which, when it determines that the transmission of ticket data has been successful, causes the processor to perform a step of receiving information about the seat associated with the ticket from the server, and in the step of displaying the seat information, displays the information about the seat associated with the ticket that was received from the server. (Note 4) The program described in Appendix 3, wherein in the step of receiving seat information, the program receives from the server information that identifies the seat and information that is different from the seat identification information and is used to guide the user to the seat location, and in the step of receiving seat information from the server, the program causes the processor to execute the step of displaying the information that guides the user to the seat location on the display unit, and in the step of displaying seat information, the program displays information that identifies the seat. (Note 5) A program according to any one of the appendices 1 to 4, which causes the processor to perform the following steps: if it determines in the decision step that the transmission of the ticket data has not been successful, to resend the ticket data to the server; and in the resending step, based on the fact that the ticket data has been sent to the server, to display information about the seat associated with the ticket on the display unit. (Note 6) The program described in Appendix 5, which, in the step of resending, receives information about the seat associated with the ticket from the server based on the sending of ticket data to the server, and in the step of displaying the seat information, displays the information about the seat associated with the ticket received from the server. (Note 7) The program described in Appendix 6, which causes the processor to perform a step of displaying a predetermined effect on the display unit based on the acceptance of an operation on the first object in the step of accepting an operation on the first object, and to perform a step of making a decision and a step of sending again while the predetermined effect is being displayed. (Note 8) A program according to any one of the appendices 5 to 7, wherein the processor causes the display unit to perform a step of displaying a second object for accepting operations to the computer, regardless of whether it has determined in the decision step that the transmission of ticket data has been successful, and in the step of displaying seat information, the program displays seat information based on the acceptance of operations to the second object. (Note 9) A method performed by a computer equipped with a processor, wherein the processor performs the steps of: marking a ticket as used; sending ticket data, which is information that the ticket has been used, to a server based on the fact that the ticket has been used; displaying a first object on the computer's display unit for accepting operations to the computer; accepting operations to the first object; determining whether the transmission of the ticket data was successful based on the acceptance of the operations; and, if it is determined in the determination step that the transmission of the ticket data was successful, displaying information about the seat associated with the ticket on the display unit. (Note 10) An information processing device comprising a control unit, wherein the control unit performs the following steps: marking a ticket as used; sending ticket data, which is information that the ticket has been used, to a server based on the fact that the ticket has been used; displaying a first object for accepting operations to the information processing device on the display unit of the information processing device; accepting operations to the first object; determining whether the transmission of ticket data was successful based on the acceptance of operations; and, if it is determined in the determination step that the transmission of ticket data was successful, displaying information about the seat associated with the ticket on the display unit. (Note 11) A system having a computer comprising a processor and memory, comprising: means for marking a ticket as used; a step of sending ticket data, which is information that the ticket has been used, to a server based on the fact that the ticket has been used; means for displaying a first object on the computer's display unit for accepting operations to the computer; means for accepting operations to the first object; means for determining whether or not the transmission of the ticket data was successful based on the acceptance of the operations; and, if the determination means determines that the transmission of the ticket data was successful, means for displaying information about the seat associated with the ticket on the display unit. (Note 12) A program for operating a computer, the program causing the computer's processor to perform the steps of: displaying a first object for accepting operations on the computer on the computer's display unit; accepting operations on the first object; based on accepting operations, sending ticket data, which is information that the ticket has been used, to a server; and based on sending the ticket data, displaying information about the seat associated with the ticket on the display unit. (Note 13) The program described in Appendix 12, which, in the step of sending, receives information about the seat associated with the ticket from the server, and in the step of displaying the seat information, displays the seat information associated with the ticket that was received from the server. (Note 14) The program described in Appendix 13, which causes the processor to perform a step of displaying a predetermined effect on the display unit based on the acceptance of an operation on the first object in the step of accepting an operation on the first object, and to perform a transmission step while the predetermined effect is being displayed. (Note 15) A method performed by a computer equipped with a processor, the method comprising: the step of the processor displaying a first object for accepting operations to the computer on the computer's display unit; the step of accepting operations to the first object; the step of sending ticket data, which is information that the ticket has been used, to a server based on the acceptance of the operations; and the step of displaying information on the seat associated with the ticket on the display unit based on the transmission of the ticket data. (Note 16) An information processing device comprising a control unit and storing information about a ticket, wherein the control unit performs the steps of: displaying a first object for receiving an operation to the information processing device on the display unit of the information processing device; receiving an operation to the first object; based on receiving the operation, transmitting ticket data, which is information that the ticket has been used, to a server; and based on transmitting the ticket data, displaying information about the seat associated with the ticket on the display unit. (Note 17) A system having a computer comprising a processor and memory, the system comprising: means for displaying a first object for receiving operations on the computer on the computer's display unit; means for receiving operations on the first object; means for transmitting ticket data, which is information that the ticket has been used, to a server based on the acceptance of the operation; and means for displaying information on the seat associated with the ticket on the display unit based on the transmission of the ticket data. [Explanation of Symbols]

[0311] 1... System 10…Terminal device 12…Communication IF 120... Communications Department 13…Input device 131... button 14…Output device 141…Display 15…Memory 150…Location information sensor 16…Storage 160... Camera 17…Sound Processing Unit 171... Mike 172...Speaker 180...Storage section 19… Processor 190... Control Unit 20... Server

Claims

1. A program for operating a computer, wherein the program is configured on the computer's processor. Steps to mark a ticket as used, Based on the fact that the aforementioned ticket has been used, the step of sending ticket data, which is information that the aforementioned ticket has been used, to the server, The steps include: displaying a first object on the computer's display unit for receiving operations on the computer; The steps include accepting an operation on the first object, Based on the acceptance of the above operation, a step is to determine whether or not the transmission of the ticket data was successful, If it is determined in the aforementioned determination step that the transmission of the ticket data has been successful, the display unit will display information regarding the seat associated with the ticket. A program that executes something.

2. In the step of displaying the first object, information indicating that the operation on the first object is an operation to request information about the seat associated with the ticket is displayed on the display unit. The program according to claim 1.

3. The aforementioned processor, If it is determined that the aforementioned ticket data has been successfully transmitted, the server receives information regarding the seat associated with the ticket. Make it run, In the step of displaying the seat information, the information regarding the seat associated with the ticket, received from the server, is displayed. The program according to claim 1.

4. In the step of receiving the aforementioned seat information, the server receives information that identifies the seat and information different from the seat identification information, which is used to guide the user to the seat location. The aforementioned processor, Based on receiving information about the seat from the server, the display unit displays information to guide the user to the seat's location. Make it run, The program according to claim 3, wherein, in the step of displaying information relating to the seat, information identifying the seat is displayed.

5. The aforementioned processor, If, in the aforementioned determination step, it is determined that the transmission of the ticket data has not been successful, the ticket data is sent again to the server. In the step of retransmitting, the display unit displays information regarding the seat associated with the ticket based on the fact that the ticket data has been sent to the server, The program according to claim 1, which causes to execute.

6. In the step of retransmitting, based on the transmission of the ticket data to the server, information regarding the seat associated with the ticket is received from the server. In the step of displaying the seat information, the information regarding the seat associated with the ticket, received from the server, is displayed. The program according to claim 5.

7. The aforementioned processor, In the step of receiving an operation on the first object, based on receiving an operation on the first object, the display unit is made to perform a step of displaying a predetermined effect. While the predetermined effect is being displayed, the determination step and the retransmission step are performed. The program according to claim 6.

8. The aforementioned processor, Regardless of whether or not it is determined in the aforementioned determination step that the transmission of the ticket data was successful, the display unit is instructed to perform the step of displaying a second object for accepting operations to the computer. In the step of displaying information about the seat, the information about the seat is displayed based on the acceptance of an operation on the second object. The program according to claim 5.

9. A method performed by a computer having a processor, wherein the processor Steps to mark a ticket as used, Based on the fact that the aforementioned ticket has been used, the step of sending ticket data, which is information that the aforementioned ticket has been used, to the server, The steps include: displaying a first object on the computer's display unit for receiving operations on the computer; The steps include accepting an operation on the first object, Based on the acceptance of the above operation, a step is to determine whether or not the transmission of the ticket data was successful, If it is determined in the aforementioned determination step that the transmission of the ticket data has been successful, the display unit will display information regarding the seat associated with the ticket. How to do it.

10. An information processing apparatus comprising a control unit, wherein the control unit is Steps to mark a ticket as used, Based on the fact that the aforementioned ticket has been used, the step of sending ticket data, which is information that the aforementioned ticket has been used, to the server, The steps include: displaying a first object on the display unit of the information processing device for receiving operations on the information processing device; The steps include accepting an operation on the first object, Based on the acceptance of the above operation, a step is to determine whether or not the transmission of the ticket data was successful, If it is determined in the aforementioned determination step that the transmission of the ticket data has been successful, the display unit will display information regarding the seat associated with the ticket. An information processing device that performs the following actions.

11. A system having a computer comprising a processor and memory, Methods for marking a ticket as used, Based on the fact that the aforementioned ticket has been used, the step of sending ticket data, which is information that the aforementioned ticket has been used, to the server, The computer's display unit includes means for displaying a first object for receiving operations on the computer, Means for receiving operations on the first object, A means for determining whether or not the transmission of the ticket data was successful based on the acceptance of the aforementioned operation, If the means for making the determination determines that the transmission of the ticket data has been successful, the display unit will display information regarding the seat associated with the ticket, A system equipped with these features.

12. A program for operating a computer, wherein the program is configured on the computer's processor. The steps include: displaying a first object for receiving operations on the computer on the computer's display unit; The steps include accepting an operation on the first object, Based on accepting the aforementioned operation, the step of sending ticket data, which is information that the ticket has been used, to the server, The steps include: Based on the transmission of the ticket data, displaying information regarding the seat associated with the ticket on the display unit; A program that executes something.

13. In the transmission step, the server receives information regarding the seat associated with the ticket, In the step of displaying the seat information, the information regarding the seat associated with the ticket, received from the server, is displayed. The program according to claim 12.

14. The aforementioned processor, In the step of receiving an operation on the first object, based on receiving an operation on the first object, the display unit is made to perform a step of displaying a predetermined effect. While the predetermined effect is being displayed, the step of transmitting is performed. The program according to claim 13.

15. A method performed by a computer having a processor, wherein the processor The steps include: displaying a first object for receiving operations on the computer on the computer's display unit; The steps include accepting an operation on the first object, Based on accepting the aforementioned operation, the step of sending ticket data, which is information that the ticket has been used, to the server, The steps include: Based on the transmission of the ticket data, displaying information regarding the seat associated with the ticket on the display unit; How to do it.

16. An information processing device comprising a control unit and storing information related to tickets, wherein the control unit is The steps include: displaying a first object for receiving an operation on the information processing device on the display unit of the information processing device; The steps include accepting an operation on the first object, Based on accepting the aforementioned operation, the step of sending ticket data, which is information that the ticket has been used, to the server, The steps include: Based on the transmission of the ticket data, displaying information regarding the seat associated with the ticket on the display unit; An information processing device that performs the following actions.

17. A system having a computer comprising a processor and memory, Means for displaying a first object for receiving operations on the computer on the computer's display unit, Means for receiving operations on the first object, A means for transmitting ticket data, which is information that the ticket has been used, to a server based on accepting the aforementioned operation, Based on the transmission of the ticket data, the display unit has means for displaying information regarding the seat associated with the ticket, A system equipped with these features.

Images