JP7389198B2 - Ticket provision method and ticket provision system - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act Article 30, Paragraph 2 of the Patent Act applies as of May 10, 2017, at https://itunes. apple. com/app/id1175974437 and https://play. google. com/store/apps/details? id=jp. lhe. Published in ebilet

The present invention relates to a ticket providing method, a ticket providing device, and a program for a mobile terminal for providing electronic tickets that can be displayed on a mobile terminal.

2. Description of the Related Art Conventionally, a technique for distributing tickets for participating in an event to a mobile terminal is known. Patent Document 1 discloses a ticket vending device that acquires a phone number of a mobile terminal and delivers a ticket image in which the acquired phone number is embedded to the mobile terminal. When a user of a mobile terminal uses a ticket to enter, the mobile terminal transmits the ticket image and phone number to the admission management device. The admission management device permits admission when the telephone number embedded in the ticket image and the telephone number transmitted from the mobile terminal match. By doing so, entry is permitted only when the user who purchased the ticket uses the ticket himself, and unauthorized use due to duplication of the ticket is prevented.

Japanese Patent Application Publication No. 2004-094468

Conventional ticket vending devices need to obtain the phone number of the mobile terminal of the user who purchases the ticket. In order for the ticket sales device to obtain the phone number of the mobile terminal, it is assumed that the application software installed on the mobile terminal transmits the phone number to the ticket sales device. However, if the OS (Operating System) of the mobile terminal does not output the mobile terminal's telephone number to the application software, the application software will be able to identify the owner of the mobile terminal to the ticket vending machine like a telephone number. could not send the information. Therefore, there is a problem in that the ticket vending device may not be able to obtain the phone number of the mobile terminal.

The present invention has been made in view of these points, and it is an object of the present invention to enable a device that provides electronic tickets to provide electronic tickets based on the telephone number of a mobile terminal.

In the ticket providing method of the first aspect of the present invention, a ticket providing device that provides an electronic ticket creates a reserved electronic ticket corresponding to a reservation phone number that is a phone number of a mobile terminal set at the time of reserving the electronic ticket. and a creation step of storing the reserved electronic ticket in a storage medium, and when the application software used to obtain the reserved electronic ticket is activated on the mobile terminal, the ticket providing device sends a ticket purchase telephone number to the mobile terminal. an information notification step of notifying the number and the terminal-specific information unique to the mobile terminal or a token associated with the terminal-specific information; a transmitting step of transmitting a short mail including the token; and a step of transmitting a short mail including the token, and a step of transmitting a short mail containing the token, and a step of transmitting a short mail including the token, and a step of transmitting a short mail including the token, and a step of transmitting a short mail including the token, and a step of transmitting a short mail including the token, and a step of transmitting a short mail including the token, and a step of transmitting a short mail including the token. the mobile terminal having the terminal-specific information included in the short mail or the mobile terminal having the terminal-specific information corresponding to the token; providing the reserved electronic ticket to the user.

In the above ticket providing method, after a predetermined time has elapsed since the mobile terminal executed the sending step, the mobile terminal determines whether or not the terminal phone number matches the reserved phone number. The method may further include the step of displaying an operation screen for requesting authentication.

Further, in the above ticket providing method, after the ticket providing device determines whether or not the terminal phone number matches the reservation phone number, the ticket providing device transmits a session ID to the mobile terminal. further comprising the step of providing an electronic ticket created by the ticket providing device on the condition that the ticket providing device receives a message including the session ID and requesting an electronic ticket from the mobile terminal in the providing step. A ticket may be provided to the mobile terminal.

Further, in the sending step, the short mail may further include application specifying information for specifying the application software.

Further, after the sending step, a relay device corresponding to the ticket purchasing phone number extracts the terminal phone number and the terminal specific information or the token from the short mail, and extracts the terminal phone number and the token. The method may further include the step of transmitting the information to the ticket providing device.

Further, the above ticket providing method includes, before the information notification step, a step of transmitting a startup notification message from the mobile terminal to the ticket providing device indicating that the application software has been started; The method may further include the steps of creating the terminal-specific information in response to receiving the activation notification message and storing it in the storage medium.

Further, in the step of creating the terminal-specific information, if the terminal-specific information previously created for the same mobile terminal is stored in the storage medium, the terminal-specific information stored in the storage medium The information may be deleted and new terminal-specific information may be created.

In the providing step, the reservation is made on the condition that the short mail is sent within a predetermined period of time after the terminal-specific information or the token is sent to the mobile terminal in the information notification step. The electronic ticket may be provided to the mobile terminal.

The steps executed before the creation step include an acquisition step in which a ticket reservation device that accepts ticket reservations acquires a ticket reservation request requesting a ticket reservation from an information input device; and a step that the ticket reservation device acquires in the acquisition step. a step of requesting the reservation telephone number from the information input device if the reservation telephone number is not associated with the ticket reservation request; The method may further include a number receiving step of receiving a number.

As a step executed before the creation step, a first code transmission step of transmitting an authentication code to a relay device, and the relay device that has received the authentication code includes the authentication code addressed to the reserved telephone number. It further includes a second code sending step of sending a short mail, and in the creation step, the ticket providing device sends an authentication code that matches the authentication code that the relay device sent to the reservation phone number. After the ticket reservation device receives the ticket from the mobile terminal, a reserved electronic ticket corresponding to the reservation telephone number may be created and stored in a storage medium.

In the ticket providing method of the second aspect of the present invention, a ticket providing device that provides an electronic ticket creates a reserved electronic ticket corresponding to a reservation phone number that is a phone number of a mobile terminal set at the time of reserving the electronic ticket. and a creation step of storing the reserved electronic ticket in a storage medium, and when the application software used to obtain the reserved electronic ticket is activated on the mobile terminal, the ticket providing device sends a ticket purchase telephone number to the mobile terminal. an information notification step of notifying the number and terminal-specific information specific to the mobile terminal or a token associated with the terminal-specific information; and a calling step of making a call from the mobile terminal to the ticket purchase telephone number. , after the calling step, a sending step of sending a tone signal corresponding to the terminal-specific information or the token to a device corresponding to the ticket purchasing telephone number; The terminal telephone number, which is a telephone number, is determined to match the reservation telephone number associated with the reserved electronic ticket stored in the storage medium. and providing the reserved electronic ticket to the mobile terminal having terminal-specific information or the mobile terminal having terminal-specific information corresponding to the token.

A ticket providing device according to a third aspect of the present invention includes a reservation request acquisition unit that acquires a reservation request for an electronic ticket in association with a reservation telephone number that is a telephone number of a mobile terminal set at the time of reservation of an electronic ticket; a creation unit that creates a reserved electronic ticket in association with a telephone number and stores the created reserved electronic ticket in a storage unit; a message acquisition unit that acquires a message from the mobile terminal; a notification unit that notifies the mobile terminal of a ticket purchase telephone number and terminal-specific information unique to the mobile terminal or a token associated with the terminal-specific information in response to acquiring a request message for a completed electronic ticket; and the terminal phone number, which is the sender's phone number of the short mail sent from the mobile terminal to the ticket purchase phone number, is the phone number associated with the reserved electronic ticket stored in the storage unit. on the condition that the mobile terminal has the terminal-specific information included in the short mail or the mobile terminal has the terminal-specific information corresponding to the token, on the condition that it is determined to match the reserved phone number. and a providing unit that provides the reserved electronic ticket to the user.

A program for a mobile terminal according to a fourth aspect of the present invention includes a transmission control unit that causes a processor of the mobile terminal to transmit a message to a ticket providing device notifying that an operation for acquiring a reserved electronic ticket has started, and a ticket purchasing device. functions as a reception control unit that receives a mobile phone number and terminal-specific information specific to the mobile terminal or a token associated with the terminal-specific information from the ticket providing device, and a display control unit that displays the information on the display unit. The transmission control unit transmits a short mail containing the mobile terminal having the phone number of the mobile terminal and the terminal-specific information or the token to the ticket purchase phone number, and the reception control unit: After the transmission control unit transmits the short mail, the transmission control unit receives the reserved electronic ticket associated with the phone number of the mobile terminal and the terminal unique information from the ticket providing device, and the display control unit receives the reserved electronic ticket associated with the phone number of the mobile terminal and the terminal unique information, and The completed electronic ticket is displayed on the display section.

According to the present invention, an effect is achieved in that a device that provides electronic tickets can provide electronic tickets based on the telephone number of a mobile terminal.

FIG. 1 is a diagram for explaining an overview of a ticket providing system according to a first embodiment. FIG. 2 is a diagram showing the configuration of a mobile terminal. It is a diagram showing the configuration of a ticket providing device. It is a diagram showing an example of a ticket management database. It is a diagram showing the transition of screens displayed by application software for acquiring a reserved electronic ticket. FIG. 2 is a sequence diagram showing the flow of processing between a mobile terminal, a ticket providing device, and a relay device. FIG. 2 is a diagram for explaining an overview of a ticket providing system according to a second embodiment. FIG. 2 is a sequence diagram showing the flow of processing between a mobile terminal, a ticket providing device, and a relay device. FIG. 1 is a diagram for explaining an overview of a ticket providing system. It is a diagram showing the configuration of a ticket providing device. It is a diagram showing the configuration of a ticket reservation device. It is a sequence diagram showing the flow of processing between a computer, a mobile terminal, a relay device, and a ticket reservation device.

<First embodiment>
[Overview of ticket provision system S1]
FIG. 1 is a diagram for explaining an overview of the ticket providing system S1 of the first embodiment. In FIG. 1, a computer 1, a mobile terminal 2, a ticket providing device 3, and a relay device 4 are shown. The computer 1 is an information input device through which a user inputs various information for purchasing an electronic ticket that can be displayed on the mobile terminal 2 . An electronic ticket is computerized information indicating that a person is entitled to receive some kind of product or service.

The mobile terminal 2, the ticket providing device 3, and the relay device 4 constitute a ticket providing system S1 that receives an electronic ticket reservation from the computer 1 and displays the electronic ticket on the mobile terminal 2. The mobile terminal 2 is, for example, a smartphone or a tablet terminal, and transmits data between the ticket providing device 3 and the relay device 4 via a mobile phone network, a wireless communication line of Wi-Fi (registered trademark), and a network such as the Internet. Send and receive.

The ticket providing device 3 is a server that can transmit and receive data between the mobile terminal 2 and the relay device 4. The relay device 4 is a server that can transmit and receive data between the mobile terminal 2 and the ticket providing device 3. In this embodiment, a case will be described in which the ticket providing device 3 and the relay device 4 are different servers, but the ticket providing device 3 and the relay device 4 may be configured as an integrated server.
Hereinafter, with reference to FIG. 1, a flow from when a user who purchases an electronic ticket reserves an electronic ticket to when the electronic ticket can be used will be explained.

First, the user performs an operation on the computer 1 to purchase an electronic ticket. Specifically, the user inputs on the computer 1 the type of electronic ticket to purchase, the telephone number of the mobile terminal 2 on which the electronic ticket is displayed, and the payment method. The computer 1 transmits a ticket reservation request requesting a ticket reservation to the ticket providing device 3 ((1) in FIG. 1). The ticket reservation request includes the type of electronic ticket input, the telephone number of the mobile terminal 2, and information regarding payment.

When the ticket providing device 3 receives a ticket reservation request from the computer 1, it creates data on a reserved electronic ticket in association with the reservation telephone number input in the computer 1, and stores it in a storage medium. The reserved electronic ticket is an electronic ticket corresponding to the type of electronic ticket included in the ticket reservation request. After storing the reserved electronic ticket in the storage medium, the ticket providing device 3 transmits a reservation completion notification indicating that the reservation of the electronic ticket is completed to the computer 1 ((2) in FIG. 1).

Thereafter, when using the reserved electronic ticket, the user can display the reserved electronic ticket on the mobile terminal 2 by activating application software for acquiring the reserved electronic ticket on the mobile terminal 2. Below, the procedure for a user to obtain a reserved electronic ticket will be explained.

When the user starts the application software, the mobile terminal 2 transmits a start notification message to the ticket providing device 3 ((3) in FIG. 1). Upon receiving the activation notification message, the ticket providing device 3 creates terminal-specific information specific to the mobile terminal 2 (hereinafter referred to as a terminal-specific ID). The terminal unique ID is, for example, an 8-digit character string composed of alphanumeric characters and alphabets, and is assigned to the mobile terminal 2 each time the ticket providing device 3 receives an activation notification message. The ticket providing device 3 notifies the mobile terminal 2 of the created terminal-specific ID ((4) in FIG. 1). The ticket providing device 3 notifies the mobile terminal 2 of the terminal-specific ID every time it receives a startup notification message, so that even if the user changes the model of the mobile terminal 2, the user can still use the mobile terminal 2 after the model change. You can obtain an electronic ticket.

Subsequently, the mobile terminal 2 transmits the terminal-specific ID to the ticket providing device 3 in order to notify that the terminal-specific ID has been successfully received ((5) in FIG. 1). When the ticket providing device 3 receives the terminal-specific ID from the mobile terminal 2, it creates a token that is a character string used to authenticate the mobile terminal 2. The token is created based on the terminal unique ID and is, for example, a 20-digit character string composed of alphanumeric characters and alphabets. The ticket providing device 3 notifies the mobile terminal 2 of the ticket purchase telephone number and the token associated with the terminal-specific ID unique to the mobile terminal 2 ((6) in FIG. 1). The ticket purchase phone number is transmitted to the relay device 4 that acquires information used to authenticate that the mobile terminal 2 has the same phone number as the reservation phone number associated with the reserved electronic ticket. It's a phone number.

When the mobile terminal 2 receives the ticket purchase telephone number and the token, it sends a short mail to the ticket purchase telephone number whose body is the character string of the token ((7) in FIG. 1). A short mail is a message that can be sent using Short Message Service (SMS), which allows messages to be exchanged using a telephone number. The text of the short mail sent by the mobile terminal 2 includes a token.

When the relay device 4 receives the short mail from the mobile terminal 2, it extracts a token from the text and identifies the telephone number of the mobile terminal 2 that is the sender of the short mail. The relay device 4 transmits the extracted token and the specified telephone number (hereinafter referred to as the terminal telephone number) to the ticket providing device 3 ((8) in FIG. 1). For example, the relay device 4 transmits the token and the terminal telephone number to a predetermined URL (Uniform Resource Locator) that the ticket providing device 3 can access.

When the ticket providing device 3 receives an authentication request from the mobile terminal 2 after receiving the token and the terminal telephone number ((9) in FIG. 1), the terminal telephone number included in the short mail is sent to the reservation stored in the storage medium. The mobile terminal 2 is authenticated by determining whether it matches the reservation telephone number associated with the completed electronic ticket ((10) in FIG. 1). The ticket providing device 3 provides the reserved electronic ticket to the mobile terminal 2 with the terminal-specific ID corresponding to the token, on the condition that the terminal telephone number matches the reserved telephone number ((in FIG. 1) 11)).

Note that after the authentication in the ticket providing device 3 is completed, the ticket providing device 3 may provide the mobile terminal 2 with a session ID used for transmitting the reserved electronic ticket. In this case, the mobile terminal 2 can acquire the reserved electronic ticket by transmitting a message including the session ID to the ticket providing device 3.
Further, in the above description, the case where the user reserves a ticket on the computer 1 is illustrated, but the user may reserve a ticket on the mobile terminal 2.
Hereinafter, the configurations of the mobile terminal 2 and the ticket providing device 3 will be explained in detail.

[Configuration of mobile terminal 2]
FIG. 2 is a diagram showing the configuration of the mobile terminal 2. As shown in FIG. The mobile terminal 2 includes a display section 21 , an operation section 22 , a communication section 23 , a storage section 24 , and a control section 25 .

The display unit 21 is a display. The display unit 21 displays an operation screen of application software for receiving an electronic ticket from the ticket providing device 3 under the control of the control unit 25 . Further, the display unit 21 displays the electronic ticket provided by the ticket providing device 3.

The operation unit 22 is, for example, a touch panel provided over the display unit 21. The operation unit 22 notifies the control unit 25 of the coordinates touched by the user.

The communication unit 23 is a communication interface for transmitting and receiving data between the ticket providing device 3 and the relay device 4. The communication unit 23 includes a wireless communication module for connecting to a mobile phone network or a Wi-Fi access point.

The storage unit 24 includes a ROM (Read Only Memory) and a RAM (Random Access Memory). The storage unit 24 stores programs executed by the control unit 25. The storage unit 24 also stores the ticket purchase telephone number, token, and electronic ticket provided by the ticket providing device 3.

The control unit 25 is, for example, a CPU (Central Processing Unit). The control unit 25 functions as a transmission control unit 251, a reception control unit 252, and a display control unit 253 by executing a program stored in the storage unit 24.

When the user operates the operation unit 22 to start application software for acquiring an electronic ticket, the transmission control unit 251 notifies the user via the communication unit 23 that the operation to acquire a reserved electronic ticket has started. A startup notification message is sent to the ticket providing device 3. Further, when the reception control unit 252 receives the ticket purchase telephone number and token from the ticket providing device 3, the transmission control unit 251 transmits a short mail containing the received token to the ticket purchase telephone number.

The transmission control unit 251 may transmit a short mail that further includes application specifying information for specifying the application software. By doing this, the relay device 4 that receives the short mail recognizes that the short mail is from the application software for acquiring an electronic ticket, and executes the necessary processing to acquire the electronic ticket. becomes possible.

The reception control unit 252 receives the ticket purchase telephone number and the token associated with the terminal-specific ID unique to the mobile terminal 2 from the ticket providing device 3 . Furthermore, after the transmission control unit 251 transmits the short mail, the reception control unit 252 receives the reserved electronic ticket associated with the phone number of the mobile terminal 2 from the ticket providing device 3.

The display control unit 253 causes the display unit 21 to display various information such as text or images. The display control unit 253 causes the display unit 21 to display, for example, an operation screen of application software for acquiring an electronic ticket. Further, the display control unit 253 causes the display unit 21 to display the reserved electronic ticket received by the reception control unit 252.

[Configuration of ticket providing device 3]
FIG. 3 is a diagram showing the configuration of the ticket providing device 3. As shown in FIG. The ticket providing device 3 includes a communication section 31, a storage section 32, and a control section 33. The control unit 33 functions as a reservation request acquisition unit 331, a creation unit 332, a message acquisition unit 333, a notification unit 334, a determination unit 335, and a provision unit 336 by executing programs stored in the storage unit 32.

The communication unit 31 is a communication interface for connecting to a network such as the Internet, and includes, for example, a LAN (Local Area Network). The communication unit 31 inputs data received from the mobile terminal 2 and the relay device 4 to the control unit 33, and transmits the data input from the control unit 33 to the mobile terminal 2 or the relay device 4.

The storage unit 32 includes storage media such as ROM, RAM, and hard disk. The storage unit 32 stores programs executed by the control unit 33. The storage unit 32 also stores a ticket management database for managing reserved electronic tickets.

FIG. 4 is a diagram showing an example of a ticket management database. FIG. 4A shows the ticket management database in a state where an electronic ticket has been reserved, but the reserved electronic ticket has not been provided to the mobile terminal 2. FIG. 4(b) shows the ticket management database in a state where some of the reserved electronic tickets have been provided to the mobile terminal 2.

In the ticket management database, the ticket type for specifying the type of electronic ticket, the reservation telephone number which is the telephone number of the mobile terminal 2 set at the time of reservation in the computer 1, and the provided flag are associated. The provided flag indicates whether or not the provision of the reserved electronic ticket to the mobile terminal 2 has been completed, and if the provided flag is "1", it means that the reserved electronic ticket has been provided to the mobile terminal 2. It shows.

Returning to FIG. 3, the configuration of each part of the control section 33 will be explained.
The reservation request acquisition unit 331 acquires from the computer 1 an electronic ticket reservation request that includes a reservation telephone number that is the telephone number of the mobile terminal 2 set at the time of electronic ticket reservation. The reservation request acquisition unit 331 notifies the creation unit 332 of the acquired reservation request.

When the creation unit 332 receives the notification of the reservation request from the reservation request acquisition unit 331, it creates a reserved electronic ticket in association with the reservation telephone number, and stores the created reserved electronic ticket in the storage unit 32. Specifically, the creation unit 332 creates data that associates the type of electronic ticket included in the reservation request with the reservation telephone number, and registers it in the ticket management database shown in FIG. 4(a).

The message acquisition unit 333 acquires various messages from the mobile terminal 2. For example, the message acquisition unit 333 acquires a startup notification message that notifies that application software for acquiring an electronic ticket has been launched on the mobile terminal 2. The message acquisition unit 333 also acquires an authentication request message requesting authentication as to whether or not the mobile terminal 2 is the mobile terminal corresponding to the reserved telephone number. The message acquisition unit 333 notifies the notification unit 334 that the activation notification message has been acquired. Furthermore, the message acquisition unit 333 notifies the determination unit 335 that the authentication request message has been acquired.

The notification unit 334 creates a terminal-specific ID unique to the mobile terminal 2 in response to the message acquisition unit 333 acquiring the activation notification message, and stores the created terminal-specific ID in the storage unit 32. If a terminal unique ID created in the past for the same mobile terminal 2 is stored in the storage unit 32, the notification unit 334 deletes the terminal unique ID stored in the storage unit 32 and creates a new terminal. Create a unique ID. The notification unit 334 determines whether the mobile terminal 2 that sent the activation notification message is the same as the mobile terminal 2 that created the terminal unique ID in the past, based on the MAC address included in the activation notification message, for example. I can do it. By doing so, it is possible to prevent multiple terminal-specific IDs from being assigned to the same mobile terminal 2 and providing multiple electronic tickets.

The notification unit 334 notifies the mobile terminal 2 of the created terminal-specific ID via the communication unit 31. Furthermore, the notification unit 334 creates a token associated with the terminal-specific ID. The notification unit 334 creates a token that is longer than the terminal-specific ID, for example, based on the time when the startup notification message was received and the terminal-specific ID. By creating a token with a character string longer than the terminal-specific ID, the notification unit 334 can use more tokens than the number of terminal-specific IDs. The notification unit 334 notifies the mobile terminal 2 of the ticket purchase telephone number and token.

The determination unit 335 acquires, from the relay device 4, the terminal telephone number, which is the telephone number of the mobile terminal 2 that is the sender of the short mail received by the relay device 4, and the token included in the short mail. Upon receiving notification from the message acquisition unit 333 that the authentication request message has been acquired, the determination unit 335 executes authentication processing. Specifically, the determination unit 335 determines whether the terminal phone number of the mobile terminal 2 that sent the short mail matches the reservation phone number associated with the reserved electronic ticket stored in the storage unit 32. .

If the terminal telephone number matches the reserved telephone number, the determining unit 335 determines that the provision unit provides the reserved electronic ticket to the mobile terminal 2 having the terminal-specific ID associated with the token acquired from the relay device 4. Allow 336. When the determining unit 335 determines that the terminal telephone number does not match the reserved telephone number, the providing unit 336 provides the reserved electronic ticket to the mobile terminal 2 having the terminal-specific ID associated with the token acquired from the relay device 4. prohibited.

Note that a validity period may be set for the token. Specifically, the determination unit 335 determines the reserved electronic ticket on the condition that the short mail is sent within a predetermined period of time after the notification unit 334 sends the token to the mobile terminal 2. Send to mobile terminal 2. For example, the determination unit 335 sets the period during which the reserved electronic ticket can be used as the validity period of the token. By doing so, the notification unit 334 can reuse the same token after the validity period has elapsed, thereby preventing the number of usable tokens from running out.

The providing unit 336 sends a message to the mobile terminal 2 having the terminal unique ID corresponding to the token included in the short mail, on the condition that the determining unit 335 determines that the terminal telephone number matches the reserved telephone number. and provide reserved electronic tickets. Specifically, when the providing unit 336 receives a message requesting authentication that includes the terminal-specific ID corresponding to the token from the mobile terminal 2 where an operation for authenticating the mobile terminal 2 has been performed, The session ID is transmitted to the mobile terminal 2 on condition that provision of the reserved electronic ticket is permitted by the determination unit 335. Upon receiving the message including the session ID from the mobile terminal 2 , the providing unit 336 transmits to the mobile terminal 2 a reserved electronic ticket associated with the same reservation telephone number as the terminal telephone number received from the relay device 4 .

[Flow of obtaining a reserved electronic ticket]
FIG. 5 is a diagram showing the transition of screens displayed by the application software for acquiring a reserved electronic ticket. FIG. 6 is a sequence diagram showing the flow of processing between the mobile terminal 2, the ticket providing device 3, and the relay device 4. Hereinafter, with reference to FIGS. 5 and 6, the flow until the user obtains a reserved electronic ticket on the mobile terminal 2 will be explained.

When the user starts the application software (S11), the mobile terminal 2 displays a "start usage" button as shown in FIG. 5(a). When the user performs an operation of touching the “start use” button (YES in S12), the transmission control unit 251 of the mobile terminal 2 transmits an activation notification message to the ticket providing device 3.

In the ticket providing device 3, when the message acquisition unit 333 receives the activation notification message, the notification unit 334 creates a terminal unique ID (S13). The notification unit 334 transmits the created terminal-specific ID to the mobile terminal 2. Subsequently, the mobile terminal 2 transmits the received terminal-specific ID to the ticket providing device 3. In the ticket providing device 3, when the message acquisition unit 333 receives the terminal-specific ID, the notification unit 334 creates a token based on the terminal-specific ID (S14). The notification unit 334 transmits the created token to the mobile terminal 2 together with the ticket purchase telephone number.

When the mobile terminal 2 receives the ticket purchase telephone number and token, it displays the "Send SMS" button as shown in FIG. 5(b). When the user of the mobile terminal 2 performs an operation of touching the "Send SMS" button (YES in S15), the transmission control unit 251 transmits a short mail including a token to the ticket purchase telephone number.

When the relay device 4 receives the short mail, it extracts the token included in the body of the received short mail (S16). The relay device 4 transmits the retrieved token and the telephone number of the sender of the short mail, that is, the terminal telephone number of the mobile terminal 2 to the ticket providing device 3.

Subsequently, when the mobile terminal 2 sends the short mail, it displays an "Authenticate" button as shown in FIG. 5(c). When the user performs an operation of touching the "Authenticate" button (YES in S17), the transmission control unit 251 transmits an authentication request including the terminal-specific ID to the ticket providing device 3. Note that the display control unit 253 sends the authentication request after the ticket providing device 3 waits a predetermined time necessary for acquiring the token and the terminal phone number of the mobile terminal 2 from the relay device 4 after transmitting the short mail. It is preferable to display an "authenticate" button as an operation screen for performing this. By doing so, it is possible to prevent an authentication request from being sent to the ticket providing device 3 before the ticket providing device 3 is in a state where it can authenticate.

Upon receiving the authentication request from the mobile terminal 2, the determination unit 335 of the ticket providing device 3 stores the terminal telephone number sent from the relay device 4 together with the token associated with the terminal unique ID included in the authentication request. The mobile terminal 2 is authenticated by comparing it with the reserved telephone number stored in the section 32 (S18). If the terminal telephone number and the reserved telephone number are the same, the determining unit 335 determines that the mobile terminal 2 is the mobile terminal corresponding to the reserved telephone number, and transmits the session ID to the mobile terminal 2.

Thereafter, the transmission control unit 251 transmits an electronic ticket provision request including the session ID to the ticket provision device 3. The providing unit 336 transmits the reserved electronic ticket to the mobile terminal 2 in response to receiving the electronic ticket provision request (S19). The display control unit 253 displays the received reserved electronic ticket on the display unit 21, as shown in FIG. 5(d) (S20).

[Effects of the ticket providing system S1 of the first embodiment]
As explained above, in the ticket providing system S1, the ticket providing device 3 creates and stores a reserved electronic ticket corresponding to the reservation telephone number, which is the telephone number of the mobile terminal 2 set at the time of reservation of the electronic ticket. Store it on a medium. After that, when a request to obtain an electronic ticket is received from the mobile terminal 2, the ticket providing device 3 sends the mobile terminal 2 a ticket purchase telephone number and a token associated with the terminal-specific ID unique to the mobile terminal 2. Notify. Then, the mobile terminal 2 sends a short mail containing the token to the notified ticket purchase telephone number. Based on the information sent from the relay device 4, the ticket providing device 3 identifies the token included in the short mail, and also identifies the terminal telephone number of the mobile terminal 2, which is the sender telephone number of the short mail. .

The determining unit 335 of the ticket providing device 3 authenticates the mobile terminal 2 by determining whether the specified terminal telephone number is the same as the reserved telephone number, and if the terminal telephone number is the same as the reserved telephone number, the terminal telephone number is the same as the reserved telephone number. , the providing unit 336 provides the electronic ticket to the mobile terminal 2 having the terminal-specific ID corresponding to the token included in the short mail. By doing so, the ticket providing device 3 can authenticate the mobile terminal 2 based on the phone number of the mobile terminal 2 even if the application software of the mobile terminal 2 cannot obtain the phone number of the mobile terminal 2. , it becomes possible to provide the electronic ticket only to the reserved mobile terminal 2.

[Modified example]
In the above description, the notification unit 334 of the ticket providing device 3 created a token associated with the terminal-specific ID, and notified the mobile terminal 2 of the created token. Then, the mobile terminal 2 sent the short mail including the token to the relay device 4. On the other hand, the notification unit 334 of the ticket providing device 3 may use the terminal-specific ID itself as a token, and the mobile terminal 2 may transmit a short mail including the terminal-specific ID to the relay device 4. In this case, the providing unit 336 provides the electronic ticket to the mobile terminal 2 having the terminal-specific ID included in the short mail. In this way, by using a terminal-specific ID instead of a token, it is possible to reduce the number of processing steps and the amount of data managed by the ticket providing device 3.

<Second embodiment>
In the ticket providing system S1 of the first embodiment, a short mail containing a terminal telephone number and a terminal-specific ID or token is sent from the mobile terminal 2 to the relay device 4. On the other hand, in the ticket providing system S2 of the second embodiment, instead of the mobile terminal 2 transmitting a short mail, after the mobile terminal 2 makes a telephone call to the relay device 4, the user This differs from the ticket providing system S1 in that the ID or token is input on the mobile terminal 2.

FIG. 7 is a diagram for explaining the outline of the ticket providing system S2. Hereinafter, only the differences from the outline of the ticket providing system S1 shown in FIG. 1 will be explained.

When the ticket providing device 3 notifies the mobile terminal 2 of the ticket purchase telephone number and the token associated with the terminal-specific ID unique to the mobile terminal 2 ((6) in FIG. 7), the mobile terminal 2 displays the token number. Subsequently, the mobile terminal 2 makes a telephone call to the relay device 4 corresponding to the ticket purchase telephone number ((21) in FIG. 7). The mobile terminal 2 may automatically make the call, or the mobile terminal 2 may display a message prompting the user to make the call, and the mobile terminal 2 may make the call in response to the user's operation.

When the relay device 4 receives an incoming telephone call, it recognizes the originating number transmitted at the time of the incoming telephone call as the terminal telephone number. Then, the relay device 4 transmits voice guidance prompting the user to input a token to the mobile terminal 2 ((22) in FIG. 7). The user of the mobile terminal 2 inputs the displayed token number in response to the voice guidance. The mobile terminal 2 transmits a DTMF (Dual-Tone Multi-Frequency) signal corresponding to the input token number to the relay device 4 ((23) in FIG. 7). Relay device 4 recognizes the token based on the received DTMF signal. The relay device 4 transmits the terminal telephone number recognized at the time of receiving the call and the token recognized based on the DTMF signal to the ticket providing device 3 ((8) in FIG. 7).

FIG. 8 is a sequence diagram showing the flow of processing between the mobile terminal 2, the ticket providing device 3, and the relay device 4. The process up to the point where the ticket providing device 3 creates a token in step S14 is the same as the sequence diagram shown in FIG. When the mobile terminal 2 receives the ticket purchase telephone number and token, it displays the received token (S21). Here, the mobile terminal 2 may display the ticket purchase telephone number together with the token.

When the mobile terminal 2 determines that a telephone call operation has been performed (YES in S22), the mobile terminal 2 makes a telephone call to the ticket purchase telephone number. When the mobile terminal 2 makes a telephone call, the telephone switching network notifies the relay device 4 of the terminal telephone number of the mobile terminal 2. When the relay device 4 receives an incoming telephone call, it transmits voice guidance to the mobile terminal 2 prompting the user to input a token.

When the user of the mobile terminal 2 inputs the token displayed in step S21 (S23), the mobile terminal 2 transmits a DTMF signal corresponding to the token number. When the relay device 4 receives the DTMF signal, it recognizes the token indicated by the DTMF signal, and transmits the terminal telephone number and the token to the ticket providing device 3. The following procedure is the same as the sequence diagram shown in FIG.

Note that FIG. 8 shows a procedure in which an authentication request is transmitted from the mobile terminal 2 to the ticket providing device 3 in response to the authentication operation performed in step 17. In this case, the user of the mobile terminal 2 ends the call after inputting the token in step S23, and separately performs the authentication operation in step S17.

On the other hand, the mobile terminal 2 may maintain the communication state with the relay device 4 until the authentication is completed. In this case, when the relay device 4 receives the token from the mobile terminal 2, it plays an audio guidance to the mobile terminal 2 saying, "Please wait until authentication is completed." Then, even if no authentication operation is performed on the mobile terminal 2, the relay device 4 makes an authentication request to the ticket providing device 3, and when the authentication is completed, a voice guidance saying "Authentication is completed" is sent to the mobile terminal 2. Stream to terminal 2.

[Effects of ticket providing system S2 of the second embodiment]
As explained above, in the ticket providing system S2, the mobile terminal 2 transmits a DTMF signal corresponding to a token to the relay device 4 after making a telephone call instead of transmitting a short mail. By doing so, even in the mobile terminal 2 which does not have the function of sending short mail, the same effect as that of the ticket providing system S1 can be obtained.

Note that in the ticket providing system S2, instead of transmitting a token from the ticket providing device 3 to the mobile terminal 2 and from the mobile terminal 2 to the relay device 4, the ticket providing device 3 sends a terminal-specific ID to the mobile terminal 2. , and the terminal-specific ID may be transmitted from the mobile terminal 2 to the relay device 4.

<Third embodiment>
[Overview of ticket provision system S3]
In the ticket providing systems S1 and S2 of the first and second embodiments, an example has been described in which the device that accepts ticket reservations and the device that displays electronic tickets on the mobile terminal 2 are the same. In contrast, in the example of this embodiment, an example will be described in which the ticket reservation device that accepts ticket reservations and the ticket provision device that displays electronic tickets on the mobile terminal 2 are different devices.

FIG. 9 is a diagram for explaining the outline of the ticket providing system S3. FIG. 9 shows a computer 1, a mobile terminal 2, a relay device 4, a ticket providing device 50, and a ticket reservation device 60. The ticket providing device 50 of the third embodiment executes the function of displaying an electronic ticket on the mobile terminal 2, which is one of the functions of the ticket providing device 3 of the first embodiment, and the ticket reservation device 60 executes the function of displaying an electronic ticket on the mobile terminal 2. Among the functions of the ticket providing device 3, the function of accepting ticket reservations is executed. The mobile terminal 2 and the relay device 4 in FIG. 9 are the same as the mobile terminal 2 and the relay device 4 in the first embodiment, so a description thereof will be omitted.

The computer 1 is an information input device through which a user inputs various information for purchasing an electronic ticket. The user inputs on the computer 1 the type of electronic ticket to purchase, a user ID for identifying the user, and a payment method. When the user performs an operation to purchase an electronic ticket on the computer 1, the computer 1 transmits a ticket reservation request including information regarding the input electronic ticket type, user ID, and payment method to the ticket reservation device 60. ((1) in FIG. 9).

The ticket reservation device 60 receives a ticket reservation request from a user. The ticket reservation device 60 reads the user's personal information registered in association with the user ID included in the ticket reservation request from the storage unit. The ticket reservation device 60 determines whether the user's mobile phone number is registered in association with the read personal information of the user. If the ticket reservation device 60 determines that the user's mobile phone number is not registered in the user's read personal information, it requests the user's mobile phone number from the computer 1 ((2) in FIG. 9). In response to the request from the ticket reservation device 60, the computer 1 transmits the user's mobile phone number to the ticket reservation device 60 ((3) in FIG. 9).

When the ticket reservation device 60 receives the mobile phone number from the computer 1, it associates the mobile phone number received from the computer 1 with the user ID and registers it in the storage unit. The ticket reservation device 60 notifies the ticket providing device 50 of reservation information indicating the content of the ticket reservation request received from the computer 1. Further, the ticket reservation device 60 notifies the ticket providing device 50 of the mobile phone number received from the computer 1 as the reservation phone number ((4) in FIG. 9).

When the ticket providing device 50 is notified of the reservation information and reservation phone number from the ticket reservation device 60, it creates a reserved electronic ticket corresponding to the type of electronic ticket included in the reservation information ((in FIG. 9)). 5)) The created reserved electronic ticket is stored in the storage unit in association with the reservation telephone number. The processing from (6) to (14) in FIG. 9 is the same as the processing from (3) to (11) in FIG. 1, so a description thereof will be omitted.

[Configuration of ticket providing device 50]
FIG. 10 is a diagram showing the configuration of the ticket providing device 50. When compared with FIG. 3, the difference is that an information acquisition section 501 is provided instead of the reservation request acquisition section 331. Identical functional blocks are designated by the same reference numerals and their description will be omitted. The information acquisition unit 501 acquires reservation information and a reservation telephone number from the ticket reservation device 60 via the communication unit 31 . The information acquisition unit 501 notifies the creation unit 332 of the acquired reservation information and reservation telephone number.

When the creation unit 332 receives notification of the reservation information and reservation telephone number from the information acquisition unit 501, it creates a reserved electronic ticket in association with the reservation telephone number, and stores the created reserved electronic ticket in the storage unit 32. Specifically, the creation unit 332 creates data that associates the type of electronic ticket included in the reservation information with the reservation telephone number, and registers it in the ticket management database shown in FIG. 4(a).

[Configuration of ticket reservation device 60]
FIG. 11 is a diagram showing the configuration of the ticket reservation device 60. The ticket reservation device 60 includes a communication section 61, a storage section 62, and a control section 63. The communication unit 61 is an interface for communicating with the computer 1, the mobile terminal 2, the relay device 4, and the ticket providing device 50. The storage unit 62 includes ROM and RAM. The storage unit 62 stores programs executed by the control unit 63.

The control unit 63 is, for example, a CPU. The control unit 63 functions as an acquisition unit 631 and a communication control unit 632 by executing a program stored in the storage unit 62. The acquisition unit 631 acquires a ticket reservation request requesting a ticket reservation from the computer 1 via the communication unit 61 . The acquisition unit 631 extracts the user ID included in the acquired ticket reservation request. The acquisition unit 631 determines whether the mobile phone number associated with the extracted user ID is registered in the storage unit 62 and notifies the communication control unit 632 of the determination result.

The communication control unit 632 communicates with the computer 1 , the mobile terminal 2 , the relay device 4 , and the ticket providing device 50 via the communication unit 61 . If the acquisition unit 631 determines that the mobile phone number associated with the extracted user ID is registered in the storage unit 62, the communication control unit 632 sends a reservation completion notification to the computer indicating that the electronic ticket reservation has been completed. Send to 1.

When determining that the mobile phone number associated with the ticket reservation request acquired by the acquisition unit 631 is not registered in the storage unit 62, the communication control unit 632 requests the computer 1 for the mobile phone number. For example, the communication control unit 632 causes the display of the computer 1 to display an input form for inputting a mobile phone number. The communication control unit 632 requests the computer 1 for a mobile phone number, and then receives the mobile phone number from the computer 1.

The communication control unit 632 generates an authentication code based on the received mobile phone number in order to suppress impersonation of the user of the mobile terminal 2. The authentication code is a 20-digit character string made up of alphanumeric characters and alphabets including, for example, a mobile phone number. Communication control unit 632 transmits the received mobile phone number and the generated authentication code to relay device 4 .

When the communication control unit 632 receives an authentication code that matches the transmitted authentication code from the computer 1 or the mobile terminal 2 after the relay device 4 sends a short mail containing the authentication code to the received mobile phone number, It is determined that the person who reserved the ticket is the user of this mobile phone number. In this case, the communication control unit 632 associates the received mobile phone number with the user ID acquired by the acquisition unit 631 and registers it in the storage unit 62, and sends a reservation completion notification to the computer indicating that the electronic ticket reservation has been completed. Send to 1.

After receiving from the computer 1 an authentication code that matches the authentication code sent by the relay device 4 to the received mobile phone number, the communication control unit 632 notifies the reservation information to the ticket providing device 50 and also updates the notified reservation. The ticket providing device 50 is instructed to create a reserved electronic ticket corresponding to the information. At this time, the ticket reservation device 60 notifies the ticket providing device 50 of the mobile phone number received from the computer 1 as the reservation phone number. The created reserved electronic ticket is stored in the storage medium of the ticket providing device 50 in association with the notified reservation telephone number.

On the other hand, if the relay device 4 does not receive an authentication code that matches the authentication code after the relay device 4 sends a short mail containing the authentication code to the received mobile phone number, the communication control unit 632 controls the creation of a reserved electronic ticket. No instructions are given to the ticket providing device 50.

[Process flow when reserving tickets]
FIG. 12 is a sequence diagram showing the flow of processing between the computer 1, the mobile terminal 2, the relay device 4, and the ticket reservation device 60. This process is started when the user performs an operation on the computer 1 to purchase an electronic ticket.

First, when the user performs an operation to purchase an electronic ticket on the computer 1, the computer 1 sends a ticket reservation request including information regarding the input electronic ticket type, user ID, and payment method to the ticket reservation device 60. Send to. The acquisition unit 631 of the ticket reservation device 60 determines whether the mobile phone number associated with the user ID included in the acquired ticket reservation request is registered in the storage unit 62 (S31).

The communication control unit 632 of the ticket reservation device 60 determines that the mobile phone number associated with the user ID included in the acquired ticket reservation request is not registered in the storage unit 62 (NO in S31). , requests the computer 1 for a mobile phone number. Computer 1 transmits the mobile phone number to ticket reservation device 60.

Communication control unit 632 generates an authentication code based on the received mobile phone number. Communication control unit 632 transmits the generated authentication code and the received mobile phone number to relay device 4 . The relay device 4 sends a short mail containing the received authentication code to the mobile phone number received from the ticket reservation device 60. For example, the relay device 4 sends a short mail containing the authentication code as the main text.

The user checks the authentication code included in the short mail received by the mobile terminal 2. The user inputs the confirmed authentication code into the computer 1, and the computer 1 transmits the input authentication code to the ticket reservation device 60. For example, the computer 1 sends the input authentication code to the ticket reservation device 60 by e-mail.

Communication control unit 632 determines whether the received authentication code matches the authentication code sent by relay device 4 to the received mobile phone number. If the received authentication code and the authentication code sent by the relay device 4 to the received mobile phone number match, the communication control unit 632 transmits reservation information indicating the content of the received ticket reservation request to the ticket providing device. 50, and the received mobile phone number is sent to the ticket providing device 50 as a reservation phone number. Furthermore, the communication control unit 632 transmits a reservation completion notification to the computer 1. The creation unit 332 of the ticket providing device 50 creates a reserved electronic ticket in association with the reservation telephone number acquired by the information acquisition unit 501, stores the created reserved electronic ticket in the storage unit 32 (S32), and executes the process. finish.

Furthermore, when the acquisition unit 631 determines that the mobile phone number associated with the user ID included in the ticket reservation request acquired in the determination in S31 is registered in the storage unit 62, the communication control unit 632 (in S31) YES), the reservation information indicating the contents of the received ticket reservation request is transmitted to the ticket providing device 50, and the registered mobile phone number is transmitted to the ticket providing device 50 as the reservation telephone number. The communication control unit 632 transmits a reservation completion notification to the computer 1. The creation unit 332 of the ticket providing device 50 creates a reserved electronic ticket in association with the reservation telephone number acquired by the information acquisition unit 501, and stores the created reserved electronic ticket in the storage unit 32 (S32). The subsequent processing is similar to the processing flow shown in FIG.

According to the present embodiment, if the mobile phone number associated with the ticket reservation request acquired by the acquisition unit 631 is not registered in the storage unit 62 (NO in S31), the communication control unit 632 transmits the request to the computer 1. , ask for your mobile phone number. Therefore, it is possible to prevent failure to obtain a mobile phone number when reserving a ticket.

Further, according to the present embodiment, the communication control unit 632 transmits an authentication code to the received mobile phone number, and creates a reserved electronic ticket after receiving an authentication code that matches the transmitted authentication code. With such a configuration, the communication control unit 632 can suppress unauthorized use of another person's mobile phone number. Furthermore, the communication control unit 632 authenticates whether or not the user is the user of the mobile terminal 2 at the time of ticket reservation, and the determination unit 335 determines whether or not the user is the user of the mobile terminal 2 at the time of ticket reservation. Since it is authenticated whether or not it is, the accuracy of authentication can be further improved.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and changes can be made within the scope of the gist. be. For example, the specific embodiment of dispersion/integration of devices is not limited to the above embodiments, and all or part of the devices may be configured by functionally or physically distributing/integrating them in arbitrary units. I can do it. In addition, new embodiments created by arbitrary combinations of multiple embodiments are also included in the embodiments of the present invention. The effects of the new embodiment resulting from the combination have both the effects of the original embodiment.

For example, in the above description, the ticket providing device 3 and the relay device 4 are separate devices, but the ticket providing device 3 may have the functions of the relay device 4 built-in. Further, in the first to third embodiments, an example was described in which the computer 1 and the mobile terminal 2 are separate devices, but the present invention is not limited to this. For example, the computer 1 may be the mobile terminal 2.

1 Computer 2 Mobile terminal 3 Ticket providing device 4 Relay device 21 Display section 22 Operating section 23 Communication section 24 Storage section 25 Control section 31 Communication section 32 Storage section 33 Control section 50 Ticket providing device 60 Ticket reservation device 61 Communication section 62 Storage section 63 Control unit 251 Transmission control unit 252 Reception control unit 253 Display control unit 331 Reservation request acquisition unit 332 Creation unit 333 Message acquisition unit 334 Notification unit 335 Determination unit 336 Providing unit 631 Acquisition unit 632 Communication control unit 633 Authentication unit

Claims (10)

a step in which the ticket providing device notifies the mobile terminal of a ticket purchase telephone number and terminal-specific information unique to the mobile terminal or a token associated with the terminal-specific information;
a display step in which the mobile terminal displays a screen for transmitting a short mail containing the terminal-specific information or the token and addressed to the ticket purchase telephone number ;
After the ticket providing device receives the terminal-specific information or the token included in the short mail sent from the mobile terminal to the ticket purchase phone number, A certain terminal phone number has the terminal-specific information included in the short mail, on the condition that it is determined that the terminal phone number matches the reservation phone number stored in advance in the storage medium in association with the reserved electronic ticket. providing the reserved electronic ticket to the mobile terminal having the terminal-specific information corresponding to the mobile terminal or the token;
A ticket provision method having for determining whether the terminal telephone number matches the reserved telephone number after the mobile terminal receives a predetermined operation by the user of the mobile terminal on the screen for sending the short mail; further comprising the step of displaying an operation screen for making an authentication request;
The ticket providing method according to claim 1. The method further comprises the step of transmitting a session ID from the ticket providing device to the mobile terminal after the ticket providing device determines whether the terminal phone number matches the reservation phone number.
In the providing step, the ticket providing device sends the electronic ticket created by the ticket providing device to the mobile terminal on the condition that the ticket providing device receives a message from the mobile terminal that includes the session ID and requests an electronic ticket. provide,
The ticket providing method according to claim 1 or 2. Between the displaying step and the providing step, the mobile terminal transmits the short mail further including application specifying information for specifying application software used to obtain the reserved electronic ticket.
The ticket providing method according to any one of claims 1 to 3. After the display step, a relay device corresponding to the ticket purchase phone number extracts the terminal- specific information or the token from the short email, and transmits the extracted terminal -specific information or the token to the ticket providing device. further comprising the step of
The ticket providing method according to any one of claims 1 to 4. Before the step of notifying the mobile terminal ,
transmitting an activation notification message from the mobile terminal to the ticket providing device indicating that application software used to obtain the reserved electronic ticket has been activated on the mobile terminal;
a step in which the ticket providing device creates the terminal-specific information in response to receiving the activation notification message and stores it in the storage medium;
further having,
The ticket providing method according to any one of claims 1 to 5. In the step of creating the terminal-specific information, if the terminal-specific information previously created for the same mobile terminal is stored in the storage medium, the terminal-specific information stored in the storage medium is deleting and creating new terminal-specific information;
The ticket providing method according to claim 6. In the providing step, the reservation is provided on the condition that the short mail is sent before a predetermined time elapses after the ticket providing device sends the terminal-specific information or the token to the mobile terminal. providing the completed electronic ticket to the mobile terminal;
The ticket providing method according to any one of claims 1 to 7. As a step executed before the step of notifying the mobile terminal ,
an acquisition step in which the ticket reservation device that accepts ticket reservations acquires a ticket reservation request requesting ticket reservation from the information input device;
a requesting step of requesting the reservation telephone number from the information input device when the reservation telephone number is not associated with the ticket reservation request acquired by the ticket reservation device in the acquisition step;
a number receiving step of receiving the reserved telephone number from the information input device after the requesting step;
further having,
The ticket providing method according to any one of claims 1 to 8. comprising a ticket providing device and a mobile terminal capable of communicating with the ticket providing device,
The ticket providing device includes:
a notification unit that notifies the mobile terminal of a ticket purchase telephone number and terminal-specific information unique to the mobile terminal or a token associated with the terminal-specific information;
After the ticket providing device receives the terminal-specific information or the token included in the short mail sent from the mobile terminal to the ticket purchase phone number, On the condition that the terminal telephone number is determined to match the reservation telephone number stored in the storage medium in advance in association with the reserved electronic ticket, the terminal telephone number having the terminal-specific information included in the short mail a providing unit that provides the reserved electronic ticket to a mobile terminal or the mobile terminal having the terminal-specific information corresponding to the token;
has
The mobile terminal has a display unit that displays a screen for transmitting the short mail addressed to the ticket purchase telephone number, which includes the terminal-specific information or a token associated with the terminal-specific information.
Ticket provision system.

Images