JP7364747B2 - Ticket management server and program - Google Patents

Description

The present invention relates to a ticket management server used in a ticket management system that monitors tickets used for admission to events and the like.

In recent years, with the spread of mobile terminals such as smartphones, electronic tickets are distributed to mobile terminals, and visitors can enter by checking the electronic ticket stored on their terminals at the entrance. An electronic ticket system has been proposed that determines availability.

For example, Patent Document 1 discloses an electronic ticket that uses a stamp that can be touched at multiple points simultaneously on the screen of a smartphone to erase the electronic ticket as used by an electronic ticket and a stamp corresponding to the electronic ticket. system is disclosed.

Unexamined Japanese Patent Publication No. 2015-5275

Although electronic tickets such as those described above are being put into practical use, there is still room for improvement in terms of preventing fraud and improving convenience. For example, it is necessary to effectively prevent illegal resale of tickets (so-called scalpers). In addition, if you are transferring a ticket to someone who does not have a multi-function terminal (for example, a smartphone) that can install a dedicated application, we will provide instructions on how to use it on a terminal that cannot install a dedicated application, or issue a paper ticket. However, these methods are also required to prevent unauthorized use and ticket issuance.

The present invention has been made to solve the above problems, and an object of the present invention is to provide an improved ticket management system.

In order to solve the above problems, a ticket management system according to an embodiment of the present invention includes a control unit, a database that stores ticket IDs for identifying tickets and user telephone numbers in association with each other, and a and a communication unit capable of communicating with a user terminal via a network. The control unit determines whether or not the communication unit receives a call from a user phone number associated with the ticket ID of the ticket at a predetermined ticketing phone number that can receive power, and transmits the ticket to the ticketing phone number. A ticket issuing device is caused to issue a ticket when a determination condition including that there is a call from a user telephone number associated with a ticket ID is satisfied.

In the present invention, in response to the communication unit receiving a notification that a ticket issuance start operation has been performed on the user terminal, the control unit sends the ticket to a predetermined ticketing telephone number that can receive power at the communication unit. It is preferable to determine whether there is an incoming call from the user telephone number associated with the ticket ID.

In the present invention, the communication unit includes a network communication unit capable of communicating with a user terminal and a ticket issuing device of a user via a network, and a telephone communication unit capable of communicating with a user terminal via a telephone line, and a control unit , in response to the network communication department receiving a notification that the ticket issuance start operation has been performed on the user terminal, the telephone communication department can receive power within a predetermined valid operation time after the ticket issuance start operation is performed. Determine whether or not a predetermined ticketing phone number receives an incoming call from the user phone number associated with the ticket ID of the ticket, and respond to the ticket ID of the ticket to the ticketing phone number within the valid operation time. It is preferable to send an instruction to the ticket issuing device to issue a ticket when the determination conditions including that there is a call from the assigned user telephone number are met.

In the present invention, the communication unit includes a network communication unit capable of communicating with a user terminal of a user via a network, and a telephone communication unit capable of communicating with a user terminal via a telephone line; In response to the network communication unit receiving a notification that the ticket issuance start operation has been performed on the terminal, a predetermined call that can be received at the telephone communication unit is made within a predetermined valid operation time after the ticket issuance start operation is performed. Determine whether or not the ticketing phone number receives an incoming call from the user phone number associated with the ticket ID of the ticket, and the ticketing phone number is associated with the ticket ID of the ticket within the valid operation time. When the judgment conditions, including that there is a call from the user's phone number, are met, a data-embedded voice with embedded ticketing information for issuing a ticket is output from the speaker of the user terminal, and the ticket issuing device Tickets may be issued based on the data-embedded voice output from the user terminal. Note that the ticketing information embedded in the data-embedded audio may include the printed content of the face of the ticket to be issued.

In the present invention, it is preferable that the data-embedded audio is transmitted to the user terminal through a voice call over a telephone line. Alternatively, the data-embedded audio may be transmitted to the user terminal by live streaming over the network. Alternatively, the data-embedded audio may be transmitted to the user terminal via the network as an audio data file containing the data-embedded audio.

In the present invention, when a ticket issuance start operation is performed, identification information indicating which of a plurality of ticket issuing devices should issue a ticket is received, and when a determination condition is met, the ticket issuing device corresponding to the received identification information is caused to print the ticket. good.

In the present invention, the ticket management server prompts the user terminal of the user to access the first site before the ticket issuing start operation, and in response to the user terminal's access to the first site, the ticket management server prompts the user terminal to access the first site. The access history information to the first site is recorded, and the user terminal is made to access the second site in order to perform the ticket issuing operation, and in response to the user terminal accessing the second site, the user terminal records the access history information to the first site. It is recommended to obtain access history information to one site, and the judgment conditions for the judgment made by the control unit are the access history recorded on the user terminal when accessing the first site and the user terminal when accessing the second site. It is preferable to include a match with the access history obtained from the access history.

In the present invention, the ticket management server prompts the user terminal of the user to access the first site before the ticket issuance start operation, and in response to the access by the user terminal to the first site, the ticket management server prompts the user terminal to access the first site. Obtains first user agent information indicating the user agent used to access the first site, causes the user terminal to access the second site in order to perform the ticket issuing operation, and causes the user terminal to access the second site. It is preferable to obtain second user agent information indicating the user agent used for the access, and the judgment condition for the judgment made by the control unit may include that the first user agent information and the second user agent information match.

A ticket management server according to another embodiment of the present invention includes a control unit, a database that stores ticket IDs for identifying tickets and user telephone numbers in association with each other, and communication with user terminals of users via a network. It includes a network communication unit capable of communicating, and a telephone communication unit capable of communicating with a user terminal through a telephone line. In response to reception by the network communication unit that an operation to start owner registration for the ticket has been performed on the user terminal, the control unit performs telephone communication within a predetermined valid operation time after the operation to start owner registration is performed. The department determines whether or not a predetermined registration phone number that can receive calls receives a call from the user phone number associated with the ticket ID of the ticket, and sends the ticket to the registration phone number within the valid operation time. When a determination condition including that there is a call from a user telephone number associated with a ticket ID is satisfied, the ticket is displayed in a usable state on a user terminal held by the user.

In the present invention, it is preferable to send the registration telephone number to the user's contact information in response to the owner registration start operation being performed.

In the present invention, a plurality of candidate telephone numbers are provided as registration telephone numbers, and in response to an operation to start owner registration, one of the plurality of candidate telephone numbers is notified to the user's contact information as the registration telephone number. It's good to do that.

In the present invention, the ticket management server prompts the user terminal of the user to access the first site before the owner registration start operation, and in response to the user terminal's access to the first site, the ticket management server prompts the user terminal to access the first site. record the access history information to the first site, cause the user terminal to access the second site in order to perform an operation to start owner registration, and in response to the user terminal accessing the second site, the user terminal It is preferable to obtain access history information to the first site from , and the criteria for the judgment made by the control unit are the access history recorded on the user terminal when accessing the first site and the information used when accessing the second site. It is preferable to include that the access history obtained from the user terminal matches the access history obtained from the user terminal.

In the present invention, the ticket management server prompts the user terminal of the user to access the first site before the owner registration start operation, and in response to the user terminal's access to the first site, the ticket management server prompts the user terminal to access the first site. acquires first user agent information indicating the user agent used to access the first site, causes the user terminal to access the second site in order to perform the owner registration start operation, and It is preferable to obtain second user agent information indicating the user agent used to access the , and it is preferable that the judgment conditions for the judgment made by the control unit include that the first user agent information and the second user agent information match. .

In order to solve the above problems, the program according to the embodiment of the present invention may cause a computer to function as one of the above ticket management servers.

1 is a schematic diagram showing the configuration of a ticket management system 1. FIG. 2 is a block diagram showing the configuration of a server 2. FIG. 3 is a block diagram showing the configuration of a ticket issuing device 3. FIG. 2 is a block diagram showing the configuration of a user terminal 4. FIG. It is a flowchart showing the procedure when receiving a ticket. It is a flowchart which shows the procedure of an owner registration process. It is a flowchart showing a procedure for using a ticket electronically. 2 is a flowchart illustrating a procedure for issuing a paper ticket. It is a flowchart showing a procedure for electronically delivering a ticket. It is a flowchart which shows the procedure of the paper ticket issuing process in 2nd Embodiment. 12 is a flowchart illustrating the procedure of paper ticket issuing processing in the third embodiment.

Embodiments of the present invention will be described below with reference to the drawings.

[Basic configuration of ticket management system]
As shown in FIG. 1, the ticket management system 1 according to the first embodiment of the present invention includes a server 2, a plurality of ticket issuing devices 3, and a plurality of user terminals 4. The server 2, ticket issuing device 3, and user terminal 4 are connected via a network NW such as the Internet. The server 2 and user terminal 4 are also connected to the telephone line network TL.

[Server configuration]
The server 2 is, for example, a computer system, and includes input/output devices such as a keyboard, mouse, and touch panel, arithmetic units such as a CPU (Central Processing Unit), and storage devices such as a RAM (Random Access Memory) and a ROM (read only memory). It consists of a main body equipped with a main body, a display device such as a CRT (Cathode Ray Tube), an LCD (Liquid Crystal Display), etc.

As shown in FIG. 2, the server 2 includes at least a storage section 201, a control section 202, a network communication section 203, and a telephone communication section 204. The storage unit 201 of the server 2 stores programs executed by the control unit 202, data used in the programs, and the like. For example, the storage unit 201 stores a program for implementing the functions of the server 2 in the ticket management system 1, a database DB related to electronic tickets managed by the ticket management system 1, a program for performing payment processing, and the like. The server 2 does not need to have the above-mentioned components physically integrated. For example, some or all of the above components may be distributed and arranged in remote locations, and they may work together to function as the server 2.

The database DB stores ticket information (for example, unique ticket ID, entertainment ID, ticket type, seat number, cancellation key, user ID of the purchaser, status (used/unused, etc.)) as information regarding electronic tickets. , ticket image, etc.), information about users (e.g., unique user ID, name, age, telephone number (user phone number), address, gender, other attributes, contact information, etc.), information about entertainment (e.g. , performance ID, performance name, event date and time, event location, etc.). Note that in this embodiment, a mobile phone number and contact information are required as information regarding the user. This contact information is a contact information (email address, SNS, etc.) that allows the user terminal 4 to send and receive information. One user ID and one entertainment ID are linked to one ticket ID corresponding to one ticket, and once the ticket ID is specified, information about the user who purchased the ticket and information about the ticket can be obtained. It is possible to specify information on performances that can be entered. When one user purchases multiple tickets for the same show, multiple ticket IDs linked to the same show ID will be linked to one ticket ID.

The control unit 202 of the server 2 executes processing according to the program stored in the storage unit 201 based on requests and the like transmitted from the user terminal 4. For example, the control unit 202 executes processing such as searching, new registration, deletion, and updating of data in the database DB stored in the storage unit 201, and the control unit 202 executes processes such as searching, new registration, deletion, and updating of data in the database DB stored in the storage unit 201, and communicates with the ticket issuing device 3, It also communicates with the user terminal 4 and the like. Further, the control unit 202 controls the telephone communication unit 204 to obtain the incoming telephone number and transmit necessary audio through the telephone line.

[Configuration of ticket issuing device]
Based on a command from the server 2, the ticket issuing device 3 prints ticket information on a predetermined sheet of paper and issues the ticket. As shown in FIG. 3, the ticket issuing device 3 includes at least a storage section 301, a control section 302, a communication section 303, a printing section 304, a display section 305, a microphone 306, and a camera 307.

The storage unit 301 stores programs executed by the control unit 302, data used in the programs, and the like. For example, the storage unit 301 includes a program that controls the printing unit 304 to print ticket information based on instructions from the server 2, and a display unit that controls the printing unit 304 to display ticket issuing machine numbers and various screens based on instructions from the server 2. Programs and the like for controlling 305 are stored. In a ticket management system 1 that includes a plurality of ticket issuing devices 3, a ticket issuing machine number is assigned to each ticket issuing device 3 in order to identify each ticket issuing device 3, and each ticket issuing device 3 assigns its own ticket issuing machine number. The information is stored in the control unit 302. Note that the ticket issuing machine number may be a ticket issuing telephone number individually assigned to each ticket issuing device 3.

The control unit 302 executes various programs stored in the storage unit 301. For example, the control unit 302 controls the printing unit 304 to print a ticket in response to a command from the server 2, and controls the display content of the display unit 305.

The communication unit 303 communicates with the server 2 via the network NW. In addition, the communication unit 303 may be configured to enable near field communication (NFC), infrared communication, visible light communication, and the like. The printing unit 304 is a printer that prints tickets on predetermined paper. The ticket paper may be, for example, a piece of paper that is pre-cut to a predetermined size and provided with perforations as necessary, or it may be a roll of paper that is cut to a predetermined length each time it is printed.

The display unit 305 is a display element such as a liquid crystal display, and displays the ticket issuing machine number, which is an identification number for identifying the ticket issuing device 3, and various notification and guidance screens. Note that the ticket issuing machine number may be displayed on a label or the like on which the ticket issuing machine number is printed instead of/in conjunction with the display section 305. Microphone 306 accepts voice input.

[Configuration of user terminal]
The user terminal 4 is, for example, a tablet terminal or a smartphone, and includes a touch panel, a calculation unit such as a CPU, a storage device such as RAM and ROM, a display device such as an LCD, a speaker that outputs audio, and a microphone that collects audio. Equipped with etc.

As shown in FIG. 4, the user terminal 4 includes at least an operation section 401, a storage section 402, a control section 403, a communication section 404, a display section 405, a microphone 406, and a speaker 407.

The operation unit 401 accepts operations by the user. The operation unit 401 includes a touch panel placed over the display unit 405 and other buttons. The storage unit 402 stores programs executed by the control unit 403, data used in the programs, and the like. The storage unit 402 stores, for example, an operating system (OS), an application program for the ticket management system 1, data on purchased electronic tickets used in this application program, user information, and the like.

As an application program for using the ticket management system 1, dedicated application software may be used, but a more versatile browser or messenger application may also be used. When using a browser or messenger application (hereinafter referred to as a browser, etc.), the user terminal 4 uses the browser etc. to access the server 2, and from the database DB of the server 2, data regarding purchased electronic tickets etc. It is recommended that the configuration be configured to retrieve and display the . In the embodiment described below, a browser or the like is used as an application program for using the ticket management system 1.

The control unit 403 executes various programs such as a browser stored in the storage unit 402. In addition to accessing a specified URL and displaying a website, etc., the browser etc. performs processing based on various data stored in the storage unit 402 and operations on the operation unit 401, as will be described in detail later. be exposed.

The communication unit 404 communicates with the server 2 via the network NW. The communication unit 404 also performs voice calls using the telephone line network TL. Note that the network NW and the telephone line network TL may be common.

The display unit 405 is a display element such as a liquid crystal display, and displays various information (the face of the electronic ticket) under the control of the control unit 403. The display unit 405 realizes various input interfaces in cooperation with the touch panel of the operation unit 401.

[Basic operation of ticket management system]
The basic flow of a user purchasing and using a ticket using the ticket management system 1 configured as described above will be explained.

[Purchasing and receiving tickets]
A user purchases a ticket for a desired event from a ticket seller (for example, a ticket sales store, ticket sales terminal, ticket site provided on the Internet, etc.). At this time, the user selects various conditions such as event, seat type, number of seats, method of receiving tickets, etc., and performs payment procedures. If the user selects an electronic ticket as the ticket receiving method, the user will use the ticket management system via his/her own mobile terminal. The flow of ticket receipt when an electronic ticket is selected as the receipt method will be described below with reference to the flowchart shown in FIG.

When the payment for the purchased ticket is completed, the ticket seller transmits the ticket ID of the purchased ticket and the user ID of the user who purchased the ticket to the server 2, and the server 2 receives this ( Step S100). Then, the server 2 records the user ID received from the seller as the user ID of the purchaser linked to the ticket ID received from the seller (step S110). Additionally, the server 2 sends a receipt URL for receiving the purchased ticket on the user terminal 4 to the contact information (email address, SNS account, etc.) linked to the purchaser's user ID ( Step S120). Note that the configuration may be such that receipt can be made on condition that the ticket issuing number, telephone number, etc. are input. Access to this receiving URL is managed by the server 2.

The user receives the ticket by accessing the receiving URL sent from the server 2 in step S120 using the browser of the user terminal 4 (step S130). This allows the ticket to be used on the user terminal 4 using a browser or the like. At this time, predetermined identification information is recorded in the browser or the like of the user terminal 4 used to access the receiving URL as history information (so-called cookie) indicating that the receiving URL has been accessed. The server 2 records the user ID of the purchaser in association with the cookie. In addition, the server 2 records information related to the user agent (hereinafter referred to as "UA information") indicating the model, browser, OS, etc. of the user terminal 4 that accessed the receiving URL, in association with the purchaser's user ID. do.

In the ticket management system of this embodiment, a ticket whose owner is not registered cannot be used. Therefore, the user who purchased the ticket registers as the owner using the procedure described below.

[Owner registration]
FIG. 6 is a flowchart showing the procedure of owner registration processing. When the user starts up a browser or the like using the user terminal 4 and accesses the site of the ticket management system, performances for which tickets have been purchased are displayed in a selectable manner (step S200). When a desired ticket is selected from among these, if the ticket owner registration has not been completed, an owner registration screen for registering the owner of the ticket is displayed together with the ticket face (step S210). . Access to this owner registration screen is managed by the server 2. Access the displayed owner registration screen. At this time, the user terminal 4 transmits to the server 2 the UA information of the browser used for access and the cookie information left on the browser etc. when accessing the receipt URL to receive the ticket (step S220 ). Furthermore, in response to the access to the owner registration screen, the server 2 notifies the user of the registration telephone number (step S230). Here, as a method of notifying the user, the registration phone number may be sent to the user's contact information, or it may be displayed on a web page that the user can view using a user terminal etc. You can do it like this. This registration telephone number may be a fixed telephone number, but it may also be a different number each time it is displayed, by transmitting one number selected from a plurality of candidate telephone numbers.

Subsequently, the user terminal 4 displays an authentication button for starting the owner registration process on the display unit 405 (step S235). When the user presses the authentication button, the server 2 records the press time in association with the ticket ID (step S240). The authentication button B1 is an example of the owner registration start operation in the present invention. Furthermore, in response to the depression of the authentication button, the user terminal 4 displays the registration telephone number received in step S220 (step S245). Note that instead of transmitting the registration telephone number from the server 2 to the user terminal 4 in step S230, the registration telephone number is transmitted from the server 2 to the user terminal 4 in response to the pressing of the authentication button. , may be displayed on the display section 405.

Next, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, the server 2 receives the registration from the phone (usually the user terminal 4) with the user's phone number recorded in association with the ticket. It is determined whether a call has been made to the telephone number (step S250). This effective operation time is preferably set to be short enough to make it difficult to transmit the ticket issuing telephone number to a third party at a remote location and dial the telephone number by proxy operation from the remote location.

In step S250, the server 2, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, receives a call from the phone (usually the user terminal 4) having the user phone number recorded in association with the ticket. It is determined as follows whether a call has been made to the registration telephone number. The server 2 receives calls to the registration phone number through the telephone communication unit 204. Then, the telephone communication unit 204 identifies the telephone number of the caller and the telephone number of the caller (any of the candidate telephone numbers). The server 2 identifies the ticket ID based on the telephone number called, and confirms whether the ticket ID is a ticket ID whose press time was recorded within a period extending back by the valid operation time from the time the call was received. By doing so, it is determined whether a call has been made to the registration telephone number within the valid operation time.

If no call is made to the registration phone number within the valid operation time from the pressing time (step S250; No), the owner will not be registered and a screen will be displayed on the user terminal 4 notifying that the owner registration was not possible. The information is displayed on the display unit 405 (step S260), and the owner registration process ends. In addition, if the caller's phone number differs by one character from the user's phone number recorded in connection with the ticket, or if the first letter is missing, etc., it is assumed that the caller's phone number was entered incorrectly. It is preferable to configure the system to provide guidance to that effect. In this way, it is possible to easily make the user aware that the user's telephone number has been registered in error, and prompt the user to correct the user's telephone number.

On the other hand, if a call is made to the registration telephone number within the valid operation time from the pressing time (step S250; Yes), the server 2 performs a verification process (step S270). In the verification process, the purchaser's telephone number linked to the ticket ID is extracted from the database DB, and is verified against the number received in step S250. The server 2 also transfers the cookie information and UA information sent from the user terminal 4 in step S220 to the cookie information and UA information when the receipt URL recorded in association with the purchaser's user ID is accessed. Check with If the matching of each information is not confirmed in the matching process (step S270; No), the owner is not registered, and a screen is displayed on the user terminal 4 notifying that the owner registration was not possible (step S260). ), the owner registration process ends. On the other hand, if it is confirmed that the information matches in the matching process (step S270; Yes), the server 2 records that the owner registration for the ticket has been completed in the database DB, and also allows the user terminal 4 to use the ticket. It is made displayable in a possible state (step S280). Thereafter, when the user launches a browser or the like on the user terminal 4 and accesses the site of the ticket management system to display the ticket, the ticket will be displayed in a usable state.

According to the owner registration process as described above, the ticket cannot be used unless the person who purchased the ticket registers as the owner, so it is possible to prevent unauthorized transfer or resale.
[Use of electronic ticket]

As described above, electronic tickets managed by the ticket management system 1 can be used by registering the owner. As explained below, tickets can be used electronically or as paper tickets.

FIG. 7 is a flowchart showing an example of the processing procedure of the ticket management system 1 when using a ticket whose owner has been registered electronically (that is, by displaying it on the user terminal 4 without issuing a paper ticket). It is. The user can display the face of the electronic ticket on the user terminal by starting the browser etc. of the user terminal 4 and accessing the ticket face URL for displaying the ticket after the user has completed the above-mentioned owner registration in advance. 4 on the display unit 405 (step S300), and present it to the staff at the entrance. Access to the ticket URL is managed by the server 2. When the user terminal 4 accesses the ticket URL, the user terminal 4 sends to the server 2 the UA information of the browser used for access and the cookie information left on the browser etc. when accessing the receipt URL to receive the ticket. Send.

The staff member visually confirms that the face of the electronic ticket for the event is for the event, and performs a predetermined redemption operation (for example, performs a predetermined operation on the touch panel of the user terminal 4). The ticket is "crossed out" to mark it as used (step S310). When the user terminal 4 receives the redemption operation, it displays text or images indicating that the ticket has been used (hereinafter referred to as "postmark information") superimposed on the ticket surface, and also changes the status of the ticket to "used". (Step S320). In addition, the user terminal 4 notifies the server 2 that the ticket has been used at an appropriate timing (either immediately after verification or after some time has passed), and the server 2 also informs the server 2 that the ticket has been used. The status of the ticket is set to "used" (step S330), and the process ends. In addition, when the user terminal 4 receives a redemption operation, it verifies whether the redemption operation is correct, marks the ticket as used only if it is correct, and issues a warning/notification, etc. if it is incorrect. good. In addition to verifying the redemption operation, the cookie information and UA information transmitted from the user terminal 4 in step S300 are recorded in association with the user ID of the ticket holder. You may also check with Note that in the above example, erasure was performed by accepting an erasure operation on the user terminal 4, but erasure may be performed by other methods. For example, by displaying an identification code (such as a QR code (registered trademark)) on the display unit 405 of the user terminal 4 along with the face of the ticket, and reading this at the entrance and checking it with the server 2, the server 2 You can also perform the erasing process using .

[Issuance of paper tickets]
On the other hand, the ticket management system 1 also allows purchased tickets to be issued and used as paper tickets. For issuing paper tickets, the ticket issuing device 3 may be permanently installed at a ticket shop or the like so that tickets can be issued in advance before the performance, or the ticket issuing device 3 may be installed near the entrance of the performance. Tickets may be issued immediately before admission. Below, with reference to the flowchart shown in FIG. 8, the procedure for issuing paper tickets by the ticket management system 1 will be explained.

Prior to ticket issuance processing, the user starts up a browser or the like on the user terminal 4 and accesses the ticket URL. Access to the ticket URL is managed by the server 2. When the user terminal 4 accesses the ticket URL, the user terminal 4 sends to the server 2 the UA information of the browser used for access and the cookie information left on the browser etc. when accessing the receipt URL to receive the ticket. Send. The processing procedure up to this point is the same as when using tickets electronically.

When the ticket URL is accessed, a paper ticket issuing button is displayed on the display unit 405 of the user terminal 4 along with an image of the ticket. When this paper ticket issuing button is pressed (step S400), ticket issuing processing is started. Once the ticket issuance process begins, the ticket becomes unavailable for use, transfer, or further ticket issuance.

When the user presses the paper ticket issuing button in step S400, a screen prompting the user to input the ticket issuing machine number is displayed on the user terminal 4. When the ticket issuing machine number displayed on the display unit 305 is input into the user terminal 4 in response to this, the user terminal 4 transmits the ticket issuing machine number to the server 2 (step S410). Pressing the paper ticket issuing button is an example of a ticket issuing start operation in the present invention. When the server 2 receives the ticket issuing machine number, it transmits the ticket issuing telephone number to the user terminal 4, and the user terminal 4 receives this (step S420). At this time, the server 2 records the ticket ID of the ticket to be issued in association with the ticket issuing telephone number. The ticket issuing telephone number may be a fixed telephone number, but it may also be a different number each time it is displayed by transmitting one number selected from a plurality of candidate telephone numbers. Note that in a configuration in which a ticket issuing telephone number is individually assigned to each ticket issuing device 3 as a ticket issuing machine number, step S410 and step 420 can be omitted, and a call is made to the ticket issuing telephone number displayed on the display unit 305. You can start the ticketing process just by clicking on the button. Therefore, it is possible to issue paper tickets even from a terminal that cannot be installed with a dedicated application.

Subsequently, the user terminal 4 displays on the display unit 405 the ticket issuing telephone number received in step S420 and a verification start button for starting verification for paper ticket issuance (step S430). Note that the ticket issuing telephone number transmitted and displayed in steps S420 and S430 may be configured to be displayed on the display section 305 of the ticket issuing device 3 instead of the display section 405 of the user terminal 4. When the user presses the verification start button, the server 2 records the pressing time in association with the ticket ID (step S440).

Next, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, the server 2 issues the ticket from the phone (usually the user terminal 4) with the user's phone number recorded in association with the ticket. It is determined whether a call has been made to the telephone number (step S450). This effective operation time is preferably set to be short enough to make it difficult to transmit the ticket issuing telephone number to a remote location and dial the telephone number by proxy operation from the remote location.

In step S450, the server 2, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, receives a call from the phone (usually the user terminal 4) having the user phone number recorded in association with the ticket. It is determined as follows whether a call has been made to the ticket issuing telephone number. The server 2 receives calls to the ticket issuing telephone number through the telephone communication section 204. Then, the telephone communication unit 204 identifies the telephone number of the caller and the telephone number of the caller (any of the candidate telephone numbers). The server 2 identifies the ticket ID based on the telephone number called, and confirms whether the ticket ID is a ticket ID whose press time was recorded within a period extending back by the valid operation time from the time the call was received. This determines whether a call has been made to the ticket issuing telephone number within the valid operation time.

If a call is not made to the ticketing phone number within the valid operation time from the pressing time (step S450; No), the ticket will not be issued and a notification will be sent that the ticket cannot be issued. A screen is displayed on the display unit 405 of the user terminal 4, and the ticket is returned to a usable state (step S460), and the ticket issuing process ends. In addition, if the caller's phone number is one character different from the user's phone number recorded in connection with the ticket, or if the first letter is missing, or if it is assumed to be an incorrect input, etc. It is preferable to configure the system to provide guidance to that effect. In this way, it is possible to easily make the user aware that the user's telephone number has been registered in error, and prompt the user to correct the user's telephone number.

On the other hand, if a call is made to the ticket issuing telephone number within the valid operation time from the pressing time (step S450; Yes), the server 2 performs a verification process (step S470). In the verification process, the user telephone number linked to the ticket ID is extracted from the database DB, and is verified against the number received in step S450. Additionally, the server 2 collates the cookie information and UA information recorded in association with the user ID of the ticket holder with the cookie information and UA information sent from the user terminal 4 when accessing the ticket URL. do. If it is not confirmed that the information matches in the matching process (step S470; No), the ticket will not be issued, and a guidance screen will be displayed on the display unit 405 of the user terminal 4 to notify that the ticket cannot be issued. The ticket is returned to a usable state (step S460), and the ticket issuing process ends.

On the other hand, if it is confirmed that the information matches in the matching process (step S470; Yes), the server 2 records in the database DB that a paper ticket has been issued for the ticket, and also records the ticket issuing machine number received in step S420. The printing unit 304 sends a command to the ticket issuing device 3 to print the ticket (step S480). The ticket issuing device 3 of the ticket issuing machine number receives this command, prints the ticket in the printing unit 304 (step S490), and ends the ticket issuing process.

In the manner described above, it is possible to issue paper tickets. In the ticketing process of this embodiment, by performing verification using phone numbers, cookie information, UA information, etc. at the time of ticket issuance, it is possible to prevent fraudulent ticket issuance by, for example, performing operations necessary for verification from a remote location. can do. Once discovered, the paper ticket can be used at the event entrance just like traditional paper tickets.

[Issuance of ticket stubs]
The paper ticket issuance process described above can be applied not only to issuing unused paper tickets, but also to issuing stubs of used tickets after entering with an electronic ticket. . It is preferable to erase the ticket at the entrance of the event venue, and then issue a stub after verifying the phone number, cookie, UA, etc. using the same procedure as the ticket issuing process described above. In this case, the ticket issuing device 3 may be provided within the venue (for example, immediately after passing through the entrance). In this way, when entering using electronic tickets for multiple people at the same time, those who do not have the user terminal 4 can be provided with seat number information or as a certificate for re-entry, etc. A stub can be issued. Furthermore, a paper ticket stub can be issued in case the battery level of the user terminal 4 is insufficient. Note that when the user terminal 4 erases electronic tickets, if the number of tickets used at the same time is plural or if the remaining battery level is below a predetermined threshold, the user terminal 4 displays a message on the display unit 405, It is a good idea to prompt the user to issue a paper stub by emitting a notification sound.

[Ticket transfer]
The ticket management system 1 allows a managed ticket to be transferred from the owner to another person.

Tickets can be transferred either electronically by having the transferee register as the owner again, or by issuing and transferring paper tickets.

[Electronic ticket transfer]
The procedure of the electronic ticket delivery method will be described with reference to the flowchart shown in FIG. In the electronic ticket transfer method, first, the transfer source user completes the above-mentioned owner registration in advance, and then displays the ticket to be transferred by accessing the ticket URL. Then, the user presses the delivery destination registration button displayed together with the face of the card (step S600). When this delivery destination registration button is pressed, a screen prompting the user to input the telephone number of the delivery destination is displayed on the user terminal 4. When the telephone number of the delivery destination is entered on the screen (step S610), the telephone number is transmitted to the server 2 together with the ticket ID, and is recorded in the database DB in association with the ticket ID (step S620). Further, the transfer source user's browser or the like is set in a state where the ticket cannot be used or further transferred (step S630).

When the server 2 receives the ticket ID and the phone number of the transferee, it issues an owner registration URL for accessing the owner registration screen for the user of the transferee to perform the owner registration process, and (step S640). The transfer source user transfers this owner registration URL to the transfer destination user (step S650). Note that the owner registration URL may be sent directly from the server 2 to the transfer destination user without going through the transfer source user.

The transfer destination user receives the URL transmitted in step S650 using his own user terminal 4 (step S660). Then, the transfer destination user registers the owner in the same manner as steps S200 to S280 in the owner registration process at the time of purchase (FIG. 6). The server 2 determines whether the owner registration by the transfer destination user has been successfully completed within a predetermined period (step S670). If it is determined that the ticket has been successfully completed (step S670; Yes), the transfer destination user is recorded as the owner of the ticket in the database DB of the server 2, and the transfer source user is no longer the owner. Then, the ticket can be displayed in a usable state on the user terminal 4 of the transferee user (step S680). On the other hand, if the owner registration by the transferee user is not completed normally (step S670; No), for example, when the owner registration is not completed within the predetermined transfer validity period, the server 2 The record of the number is deleted from the database DB, and the ticket is displayed in a usable state on the user terminal 4 of the transfer source user (step S690).

In the manner described above, tickets can be transferred electronically. In this way, by requiring the same owner registration as at the time of purchase when transferring a ticket electronically, the ticket management system 1 can keep track of the transfer source and transferee, thereby preventing fraudulent transfers. Resale can be inhibited.

[Transfer of paper tickets]
On the other hand, the method of issuing and delivering a paper ticket is a method in which the user who owns the ticket issues the ticket using the ticket issuing device 3 and passes the issued ticket to the transferee. The issuance of paper tickets may be realized in the same manner as the above-mentioned issuance of paper tickets. Incidentally, even when transferring paper tickets, if the configuration is such that owner registration is required before the paper ticket is issued, unauthorized transfer or resale can be prevented. In this case, if the name of the user who is registered as the holder is printed on the face of the issued paper ticket, it can be particularly expected to be effective in deterring illegal transfer or resale.

[Second embodiment]
The ticket management system according to the second embodiment of the present invention is different from the first embodiment in the method of issuing paper tickets. That is, the second embodiment is the same as the first embodiment until the verification (step S450 in FIG. 8) is performed, but after the verification is successful, the procedure and procedure for issuing a paper ticket from the ticket issuing device 3 are changed. The difference is in the hardware configuration related to the procedure.

FIG. 10 is a flowchart showing the procedure of ticket issuing processing by the ticket issuing device 3 in the second embodiment. Prior to ticket issuance processing, the user starts a browser or the like on the user terminal 4 and accesses the ticket URL. Access to the ticket URL is managed by the server 2. When the user terminal 4 accesses the ticket URL, the user terminal 4 sends to the server 2 the UA information of the browser used for access and the cookie information left on the browser etc. when accessing the receipt URL to receive the ticket. Send.

When the ticket URL is accessed, a paper ticket issuing button is displayed on the display unit 405 of the user terminal 4 along with an image of the ticket. When this paper ticket issuing button is pressed (step S700), ticket issuing processing is started. Once the ticket issuance process begins, the ticket becomes unavailable for use, transfer, or further ticket issuance.

When the user presses the paper ticket issuing button in step S700, a screen prompting the user to input the ticket issuing machine number is displayed on the user terminal 4. When the ticket issuing machine number displayed on the display section 305 is input into the user terminal 4 in response to this, the user terminal 4 transmits the ticket issuing machine number to the server 2 (step S710). Pressing the paper ticket issuing button is an example of a ticket issuing start operation in the present invention. Upon receiving the ticket issuing machine number, the server 2 transmits the ticket issuing telephone number to the user terminal 4 (step S720). This ticket issuing telephone number may be a fixed telephone number, but it may also be a different number each time it is displayed, by transmitting one number selected from a plurality of candidate telephone numbers.

Subsequently, the user terminal 4 displays on the display unit 405 the ticket issuing telephone number received in step S720 and a verification start button for starting verification for paper ticket issuance (step S730). When the user presses the check start button, the server 2 records the press time (step S740).

Next, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, the server 2 issues the ticket from the phone (usually the user terminal 4) with the user's phone number recorded in association with the ticket. It is determined whether a call has been made to the telephone number (step S750). This effective operation time is preferably set to be short enough to make it difficult to transmit the ticket issuing telephone number to a remote location and dial the telephone number by proxy operation from the remote location.

In step S750, the server 2, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, receives a call from the phone (usually the user terminal 4) having the user phone number recorded in association with the ticket. It is determined as follows whether a call has been made to the ticket issuing telephone number. The server 2 receives calls to the ticket issuing telephone number through the telephone communication section 204. Then, the telephone communication unit 204 identifies the telephone number of the caller and the telephone number of the caller (any of the candidate telephone numbers). The server 2 identifies the ticket ID based on the telephone number called, and confirms whether the ticket ID is a ticket ID whose press time was recorded within a period extending back by the valid operation time from the time the call was received. This determines whether a call has been made to the ticket issuing telephone number within the valid operation time.

If a call is not made to the ticketing phone number within the valid operation time from the pressing time (step S750; No), the ticket will not be issued and a notification will be sent that the ticket cannot be issued. A screen is displayed on the display unit 405 of the user terminal 4, and the ticket is returned to a usable state (step S760), and the ticket issuing process ends. In addition, if the caller's phone number differs by one character from the user's phone number recorded in connection with the ticket, or if the first letter is missing, etc., if it is assumed that it was entered incorrectly, we will notify you. It is preferable to configure the system so that it guides you through the process. In this way, it is possible to easily make the user aware that the user's telephone number has been registered in error, and prompt the user to correct the user's telephone number.

On the other hand, if a call is made to the ticket issuing telephone number within the valid operation time (step S750; Yes), the server 2 performs a verification process (step S770). In the verification process, the user telephone number linked to the ticket ID is extracted from the database DB, and is verified against the number received in step S750. Additionally, the server 2 collates the cookie information and UA information recorded in association with the user ID of the ticket holder with the cookie information and UA information sent from the user terminal 4 when accessing the ticket URL. do. If it is not confirmed that the information matches in the matching process (step S770; No), the ticket will not be issued, and a guidance screen will be displayed on the display unit 405 of the user terminal 4 to notify that the ticket cannot be issued. The ticket is returned to a usable state (step S760), and the ticket issuing process ends.

On the other hand, if the matching of the information is confirmed in the matching process (step S770; Yes), the server 2 causes the telephone communication unit 204 to start a voice call using the telephone received in step S750 (step S780). Then, the telephone communication unit 204 transmits data-embedded voice embedded with information (hereinafter referred to as "ticketing information") for causing the ticket issuing device 3 to print a ticket to the user terminal 4 during the voice call ( Step S790). Note that it is preferable that the voice call is disconnected after a predetermined call time has elapsed. Here, the ticketing information may include all the data on the ticket surface, or may include only the encrypted ticket ID if necessary. When the ticketing information is only the ticket ID, the ticketing device 3 preferably receives data in which the ticket ID and the data on the ticket surface are associated with each other from the server 2 and stores it in the storage unit 301 in advance. Alternatively, each time ticketing information is received, data on the ticket surface corresponding to the ticket ID may be referred to the server 2 and received via the network NW. Further, the ticketing information may include the ticketing machine number input in step S710. The ticketing information may also include time stamp information indicating the time of the ticketing process, such as the press time recorded in step S740 and the time when the ticketing telephone number was called.

The user holds the speaker 407 of the user terminal 4 over the microphone 306 of the ticket issuing device 3 and inputs the data-embedded voice into the microphone 306 (step S800). The ticket issuing device 3 decodes the voice input to the microphone 306 and obtains ticket issuing information (step S810). Then, the ticket issuing device 3 determines whether the received ticket issuing information is valid (step S820).

Whether or not the received ticketing information is valid may be determined, for example, as follows. If the ticketing information includes a ticketing machine number, the conditions for determining validity include the fact that the ticketing machine number of the ticketing device 3 into which the data-embedded voice has been input matches the ticketing machine number included in the ticketing information. good. Further, when the ticketing information includes time stamp information, it is preferable to include, as a condition for determining validity, that the current time is within a predetermined ticketing validity period from the time indicated by the time stamp information. During the ticket issue validity period, it is preferable to set the time (for example, 3 minutes) to such an extent that it is difficult to record the data-embedded voice and send it to a remote location via a network NW or the like. Further, the condition may include that the voice is input within a predetermined time after the matching of the information is confirmed in the matching process. In addition, the conditions for determining validity may include the fact that the ticketing information includes information indicating that the verification in step S780 has been performed.

If the received ticketing information is valid (step S820; Yes), the ticketing device 3 prints the ticket in the printing unit 304, and prints information indicating that the ticket has been issued, such as the result of the determination in step S820. is transmitted to server 2 (step S830). In response to this, the server 2 records in the database DB that a paper ticket has been issued for the ticket (step S840), and ends the ticket issuing process.

On the other hand, if the received ticketing information is not valid (step S820; No), the ticketing device 3 displays on the display unit 305 that the ticket cannot be issued, and does not issue the ticket based on the result of the judgment in step S840. The server 2 transmits information indicating that the server 2 has received the request (step S850). In response to this, the server 2 returns the ticket to a usable state (step S860), and ends the ticket issuing process.

As described above, when issuing a paper ticket, by transmitting ticketing information from the user terminal 4 to the ticketing device 3 via the data-embedded voice, it was possible to successfully make a call from a remote location at the time of verification. However, since the data-embedded voice required for ticket issuance cannot be transmitted to the ticket issuing device 3, it is possible to more effectively prevent the issuance of fraudulent tickets.

[Modification of the second embodiment]
In the second embodiment described above, the data-embedded voice is transmitted from the server 2 and received by the user terminal 4 through a voice call via the telephone line TL. However, the data-embedded voice may be transmitted to the user terminal 4 by a method other than voice communication via the telephone line TL, and may be output from the speaker 407 of the user terminal 4. For example, the data-embedded audio is transmitted from the server 2 by live streaming via the network NW, received by the user terminal 4, and outputted from the speaker 407 by playing the data-embedded audio in streaming on the user terminal 4. You may also do so. In addition, data-embedded audio can be transmitted by transmitting the data-embedded audio as an audio data file via the network NW, received by the user terminal 4, and played the audio data file on the user terminal 4. may be output from the speaker 407. According to these methods, since the data-embedded audio does not deteriorate during the transmission process from the server 2 to the user terminal 4, it is possible to prevent errors from occurring in the transmission of ticketing information.

In addition, in a configuration in which the data-embedded audio is transmitted as an audio data file via the network NW, it is possible to restrict the transfer of the audio data file received by the user terminal 4, or to transfer the audio data file to another terminal. It may be configured to restrict playback. For example, it is preferable to associate the audio data with cookie information at the time of ticket issuing processing, session information of data communication via the network NW, etc., so that the audio data file can be played only on the user terminal 4 used for the ticket issuing processing.

[Third embodiment]
The ticket management system according to the third embodiment of the present invention is different from the first embodiment in the method of issuing paper tickets. That is, the second embodiment is the same as the first embodiment until the verification (step S450 in FIG. 8) is performed, but after the verification is successful, the procedure and procedure for issuing a paper ticket from the ticket issuing device 3 are changed. The difference is in the hardware configuration related to the procedure.

FIG. 11 is a flowchart showing the procedure of ticket issuing processing by the ticket issuing device 3 in the third embodiment. Prior to ticket issuance processing, the user starts a browser or the like on the user terminal 4 and accesses the ticket URL. Access to the ticket URL is managed by the server 2. When the user terminal 4 accesses the ticket URL, the user terminal 4 sends to the server 2 the UA information of the browser used for access and the cookie information left on the browser etc. when accessing the receipt URL to receive the ticket. Send.

When the ticket URL is accessed, a paper ticket issuing button is displayed on the display unit 405 of the user terminal 4 along with an image of the ticket. When this paper ticket issuing button is pressed (step S900), ticket issuing processing is started. Once the ticket issuance process begins, the ticket becomes unavailable for use, transfer, or further ticket issuance.

When the user presses the paper ticket issuing button in step S900, a screen prompting the user to input the ticket issuing machine number is displayed on the user terminal 4. When the ticket issuing machine number displayed on the display unit 305 is input into the user terminal 4 in response to this, the user terminal 4 transmits the ticket issuing machine number to the server 2 (step S910). Pressing the paper ticket issuing button is an example of a ticket issuing start operation in the present invention. When the server 2 receives the ticket issuing machine number, it transmits the ticket issuing telephone number to the user terminal 4 (step S920). This ticket issuing telephone number may be a fixed telephone number, but it may also be a different number each time it is displayed, by transmitting one number selected from a plurality of candidate telephone numbers.

Subsequently, the user terminal 4 displays on the display unit 405 the ticket issuing telephone number received in step S720 and a verification start button for starting verification for paper ticket issuance (step S930). When the user presses the check start button, the server 2 records the press time (step S940).

Next, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, the server 2 issues the ticket from the phone (usually the user terminal 4) with the user's phone number recorded in association with the ticket. It is determined whether a call has been made to the telephone number (step S950). This effective operation time is preferably set to be short enough to make it difficult to transmit the ticket issuing telephone number to a remote location and dial the telephone number by proxy operation from the remote location.

In step S950, the server 2, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, receives a call from the phone (usually the user terminal 4) having the user phone number recorded in association with the ticket. It is determined as follows whether a call has been made to the ticket issuing telephone number. The server 2 receives calls to the ticket issuing telephone number through the telephone communication section 204. Then, the telephone communication unit 204 identifies the telephone number of the caller and the telephone number of the caller (any of the candidate telephone numbers). The server 2 identifies the ticket ID based on the telephone number called, and confirms whether the ticket ID is a ticket ID whose press time was recorded within a period extending back by the valid operation time from the time the call was received. This determines whether a call has been made to the ticket issuing telephone number within the valid operation time.

If a call is not made to the ticketing phone number within the valid operation time from the pressing time (step S950; No), the ticket will not be issued and a notification will be sent that the ticket cannot be issued. A screen is displayed on the display unit 405 of the user terminal 4, and the ticket is returned to a usable state (step S960), and the ticket issuing process ends. Note that, if the caller's telephone number differs by one character from the user's telephone number recorded in association with the ticket, it is preferable to configure the system to inform the user of this fact. In this way, it is possible to easily make the user aware that the user's telephone number has been registered in error, and prompt the user to correct the user's telephone number.

On the other hand, if a call is made to the ticket issuing telephone number within the valid operation time (step S950; Yes), the server 2 performs a verification process (step S970). In the verification process, the user telephone number linked to the ticket ID is extracted from the database DB, and is verified against the number received in step S950. Additionally, the server 2 collates the cookie information and UA information recorded in association with the user ID of the ticket holder with the cookie information and UA information sent from the user terminal 4 when accessing the ticket URL. do. If it is not confirmed that the information matches in the matching process (step S970; No), the ticket will not be issued, and a guidance screen will be displayed on the display unit 405 of the user terminal 4 to notify that the ticket cannot be issued. The ticket is returned to a usable state (step S960), and the ticket issuing process ends.

On the other hand, if it is confirmed that the information matches in the matching process (step S970; Yes), the server 2 transmits an identification code (bar code, QR code (registered trademark), etc.) to the display unit 405 of the user terminal 4. (Step S980). The identification code transmitted by the server 2 may include the data on the ticket surface, or may include only the encrypted ticket ID if necessary. When only the ticket ID is included, it is preferable that the ticket issuing device 3 receives data in which the ticket ID and the data on the ticket surface are associated with each other from the server 2 in advance and stores it in the storage unit 301. Alternatively, each time the identification code is read, data on the ticket surface corresponding to the ticket ID may be referred to the server 2 and received via the network NW. Further, the identification code may include information such as a URL indicating the location of information necessary for issuing a ticket on the network NW. Further, the identification code may include the ticket issuing machine number input in step S910. The identification code may also include time stamp information indicating the time of ticket issuing processing, such as the press time recorded in step S940 and the time when a call was made to the ticket issuing telephone number. The identification code may be configured so that the display disappears after a predetermined period of time has elapsed after being displayed on the display unit 405 of the user terminal 4.

The user holds the display unit 405 of the user terminal 4 over the camera 307 of the ticket issuing device 3 and causes the ticket issuing device 3 to read the identification code (step S990). Then, the ticket issuing device 3 determines whether the read identification code is valid (step S1020).

Whether or not the received identification code is valid may be determined, for example, as follows. When the identification code includes a ticket issuing machine number, it is preferable to include the condition for determining validity that the ticket issuing machine number of the ticket issuing device 3 that read the identification code and the ticket issuing machine number included in the identification code match. Further, in the case where the identification code includes time stamp information, it is preferable to include, as a condition for determining validity, that the current time is within a predetermined ticket issue validity period from the time indicated by the time stamp information. Further, the condition may include that the identification code is read within a predetermined time after the matching of information is confirmed in the matching process. In addition, the conditions for determining validity may include the fact that the ticketing information includes information indicating that the verification in step S980 has been performed.

If the read identification code is valid (step S1020; Yes), the ticket issuing device 3 prints the ticket in the printing unit 304, and as a result of the determination in step S1020, prints information indicating that the ticket has been issued. is transmitted to server 2 (step S1030). In response to this, the server 2 records in the database DB that a paper ticket has been issued for the ticket (step S1040), and ends the ticket issuing process.

On the other hand, if the read identification code is not valid (step S1020; No), the ticket issuing device 3 displays on the display unit 305 that the ticket cannot be issued, and as a result of the determination in step S1040, the ticket is not issued. Information indicating this is transmitted to the server 2 (step S1050). In response to this, the server 2 returns the ticket to a usable state (step S1060), and ends the ticket issuing process.

As described above, when issuing a paper ticket, the ticket issuing device 3 reads the identification code displayed on the user terminal 4. Since the necessary identification code cannot be transmitted to the ticket issuing device 3, it is possible to more effectively prevent the issuance of fraudulent tickets.

Although the embodiments of the present invention have been described above, the present invention is not limited to these examples. Furthermore, the gist of the present invention may be obtained by appropriately adding, deleting, or changing the design of the above-described embodiments by those skilled in the art, or by appropriately combining the features of each embodiment. within the scope of the present invention.

1 Ticket management system 2 Server 3 Ticket issuing device 4 User terminal NW Network TL Telephone line network

Claims (15)

a control unit;
a database that stores ticket IDs for identifying tickets and user telephone numbers in association with each other;
a communication unit capable of communicating with the user terminal of the user via the network;
A ticket management server comprising:
The control unit includes:
Determining whether or not there is an incoming call from the user phone number associated with the ticket ID of the ticket to a predetermined ticketing phone number that can receive power in the communication department;
causing the ticket issuing device to issue the ticket when a determination condition including that the ticket issuing telephone number received a call from the user telephone number associated with the ticket ID of the ticket is satisfied ;
The ticket management server further includes:
prompting the user terminal to access a first site before the user performs a ticket issuing operation for the ticket from the user terminal;
causing the user terminal to record access history information to the first site in response to access by the user terminal to the first site;
causing the user terminal to access a second site in order to perform the ticketing start operation, and access history information from the user terminal to the first site in response to the user terminal accessing the second site; get
The judgment conditions for the judgment made by the control unit include an access history recorded in the user terminal when accessing the first site, and an access history acquired from the user terminal when accessing the second site. A ticket management server characterized in that: the ticket management server matches the ticket management server. In response to the communication unit receiving a notification that the ticket issuance start operation for the ticket has been performed on the user terminal, the control unit sets the predetermined ticket issuing telephone number that can receive power at the communication unit. 2. The ticket management server according to claim 1, wherein the ticket management server determines whether or not there is an incoming call from the user telephone number associated with the ticket ID of the ticket. The communication department includes:
a network communication unit capable of communicating with the user terminal and the ticket issuing device via a network;
comprising a telephone communication unit capable of communicating with the user terminal through a telephone line,
The control unit includes:
In response to reception by the network communication unit that the ticket issuance start operation for the ticket has been performed on the user terminal, the telephone communication is performed within a predetermined valid operation time after the ticket issuance start operation is performed. Determining whether or not there is an incoming call from the user phone number associated with the ticket ID of the ticket to the predetermined ticket issuing phone number that can receive calls at the department;
If the judgment conditions are met, including that the ticket issuing telephone number received a call from the user telephone number associated with the ticket ID of the ticket within the valid operation time, the ticket issuing device 3. The ticket management server according to claim 2, wherein the ticket management server transmits an instruction to issue a ticket. The communication department includes:
a network communication unit capable of communicating with the user terminal via a network;
comprising a telephone communication unit capable of communicating with the user terminal through a telephone line,
The control unit includes:
In response to reception by the network communication unit that the ticket issuance start operation for the ticket has been performed on the user terminal, the telephone communication is performed within a predetermined valid operation time after the ticket issuance start operation is performed. Determining whether or not there is an incoming call from the user phone number associated with the ticket ID of the ticket to the predetermined ticket issuing phone number that can receive calls at the department;
To issue the ticket when a determination condition including that the ticket issuing telephone number receives a call from the user telephone number associated with the ticket ID of the ticket within the valid operation time; A data-embedded voice in which ticketing information is embedded is outputted from a speaker of the user terminal, and the ticket issuing device is caused to issue the ticket based on the data-embedded voice outputted from the user terminal. The ticket management server described in Section 1. 5. The ticket management server according to claim 4, wherein the ticketing information embedded in the data-embedded audio includes printed content on the face of the ticket to be issued. 6. The ticket management server according to claim 4, wherein the data-embedded voice is transmitted to the user terminal by voice communication over a telephone line. 6. The ticket management server according to claim 4, wherein the data-embedded audio is transmitted to the user terminal by live streaming over a network. 6. The ticket management server according to claim 4, wherein the data-embedded audio is transmitted to the user terminal via a network as an audio data file containing the data-embedded audio. Receiving identification information indicating which of the plurality of ticket issuing devices should issue the ticket in response to the ticket issuing start operation;
9. The ticket management server according to claim 1, wherein when the determination condition is satisfied, the ticket issuing device corresponding to the received identification information is caused to print the ticket. The ticket management server prompts the user terminal to access the first site before the ticketing start operation,
In response to an access by the user terminal to the first site, first user agent information indicating a user agent used to access the first site from the user terminal is obtained;
causing the user terminal to access the second site in order to perform the ticketing start operation, and acquiring second user agent information indicating the user agent used by the user terminal to access the second site;
10. The determination condition for the determination performed by the control unit includes that the first user agent information and the second user agent information match. Ticket management server. a control unit;
a database that stores ticket IDs for identifying tickets and user telephone numbers in association with each other;
a network communication unit capable of communicating with the user terminal of the user via the network;
A ticket management server comprising a telephone communication unit capable of communicating with the user terminal through a telephone line,
The control unit includes:
In response to reception by the network communication unit that an operation to start owner registration for the ticket has been performed on the user terminal, the telephone communication is performed within a predetermined valid operation time after the operation to start owner registration is performed. Determine whether or not there is an incoming call from the user phone number associated with the ticket ID of the ticket at a predetermined registered phone number that can receive calls at the department;
If the judgment conditions are met, including that the registration phone number received a call from the user phone number associated with the ticket ID of the ticket within the valid operation time, the ticket is transferred to the user. to display the information in a usable manner on the user terminal owned by the user ,
The ticket management server prompts the user terminal of the user to access a first site before the owner registration start operation,
causing the user terminal to record access history information to the first site in response to access by the user terminal to the first site;
causing the user terminal to access a second site in order to perform the owner registration start operation, and access history information from the user terminal to the first site in response to the user terminal accessing the second site; get
The judgment conditions for the judgment made by the control unit include an access history recorded in the user terminal when accessing the first site, and an access history acquired from the user terminal when accessing the second site. A ticket management server characterized in that: the ticket management server matches the ticket management server. 12. The ticket management server according to claim 11 , wherein the registration telephone number is transmitted to the user's contact information in response to the owner registration start operation being performed. A plurality of candidate phone numbers are provided as the registration phone number,
13. Ticket management according to claim 12 , characterized in that, in response to the owner registration start operation being performed, any one of a plurality of candidate telephone numbers is notified to the contact information of the user as the registration telephone number. server. The ticket management server prompts the user terminal of the user to access a first site before the owner registration start operation,
In response to an access by the user terminal to the first site, first user agent information indicating a user agent used to access the first site from the user terminal is obtained;
causing the user terminal to access a second site in order to perform the owner registration start operation, and acquiring second user agent information indicating a user agent used by the user terminal to access the second site;
14. The determination condition for the determination performed by the control unit includes that the first user agent information and the second user agent information match. Ticket management server. A program that causes a computer to function as a ticket management server according to any one of claims 1 to 14 .

Images