JP2022130559A - Ticket management server and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a highly convenient ticket management server and a program.

SOLUTION: A ticket management server includes a control unit, a database that stores a ticket ID identifying a ticket and a user telephone number in association with each other, and a communication unit that can communicate with a user terminal of a user via a network. The control unit determines whether there is an incoming call from the user telephone number associated with the ticket ID of the ticket to a predetermined ticketing telephone number that can be received by the communication unit, and causes a ticket issuing device to issue the ticket when a determination condition including the condition that there is a call origination from the user telephone number associated with the ticket ID of the ticket to the ticketing telephone number is satisfied.

SELECTED DRAWING: Figure 6

COPYRIGHT: (C)2022,JPO&INPIT

Description

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

In recent years, with the spread of mobile terminals such as smartphones, electronic tickets are distributed to mobile terminals by converting admission tickets into electronic data. An electronic ticket system for judging acceptance has been proposed.

For example, Patent Literature 1 describes an electronic ticket that uses a stamp that allows simultaneous multi-point contact on the screen of a smartphone, and performs reconciliation processing to indicate that the electronic ticket has been used by the electronic ticket and the stamp corresponding to the electronic ticket. A system is disclosed.

JP 2015-5275 A

Electronic tickets such as those described above are being put to practical use, but there is still room for improvement in terms of preventing fraud and improving convenience. For example, it is required to effectively prevent illegal resale of tickets (so-called scalping, etc.). In addition, when transferring a ticket to a person who does not have a multifunctional terminal (for example, a so-called smartphone) that can install a dedicated application, we will provide a method of use on a terminal that cannot install a dedicated application, or issue a paper ticket However, these methods are also required to prevent fraudulent use and ticketing.

SUMMARY OF THE INVENTION 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 that identify tickets and user telephone numbers in association with each other, and and a communication unit capable of communicating with the user terminal via a network. The control unit determines whether or not there is an incoming call from the user telephone number associated with the ticket ID of the ticket to a predetermined ticketing telephone number capable of receiving power in the communication unit, and determines whether or not the ticket issuance telephone number When a determination condition including a call from a user telephone number associated with the ticket ID of is satisfied, the ticket issuing device is caused to issue a ticket.

In the present invention, in response to the fact that the ticket issuing start operation has been performed on the user terminal by the communication unit, the control unit sends the ticket to a predetermined ticket issuing telephone number that can be received by the communication unit. It is preferable to determine whether or not there is an incoming call from the user telephone number associated with the ticket ID of .

In the present invention, the communication unit includes a network communication unit capable of communicating with the user terminal of the user and the ticket issuing device via the network, and a telephone communication unit capable of communicating with the user terminal via the telephone line, and the control unit , In response to the receipt by the network communication unit of the fact that the ticket issuing start operation has been performed on the user terminal, the telephone communication unit can receive power within a predetermined effective operation time after the ticket issuing start operation is performed. determines whether or not there is an incoming call from the user's telephone number associated with the ticket ID of the ticket to a predetermined ticket issuing telephone number, and corresponds the ticket issuing telephone number to the ticket ID of the ticket within the valid operation time. It is preferable to transmit a command to issue a ticket to the ticket issuing device when the judgment conditions including the fact that there is a call from the attached user telephone number are satisfied.

In the present invention, the communication unit includes a network communication unit capable of communicating with the user terminal of the user via the network, and a telephone communication unit capable of communicating with the user terminal through the telephone line. In response to the receipt by the network communication unit of the fact that the ticket issuance start operation has been performed on the terminal, within a predetermined valid operation time after the ticket issuance start operation is performed, a predetermined amount of power that can be received by the telephone communication unit It is determined whether or not there is an incoming call from the user's telephone number associated with the ticket ID of the ticket to the telephone number for ticket issuance, and the telephone number for ticket issuance is associated with the ticket ID of the ticket within the valid operation time. When the determination conditions including the call from the user's telephone number are satisfied, the data-embedded voice embedded with the ticketing information for issuing the ticket is output from the speaker of the user terminal and sent to the ticket issuing device. A ticket may be issued based on the data-embedded voice output from the user terminal. The ticket issue information embedded in the data-embedded voice may include the printed contents of the ticket to be issued.

In the present invention, the data-embedded voice may be transmitted to the user terminal by voice communication through the telephone line. Alternatively, the data-embedded audio may be sent to the user terminal by live streaming over the network. Alternatively, the data-embedded voice may be transmitted to the user terminal through the network as an audio data file containing the data-embedded voice.

In the present invention, identification information indicating from which one of a plurality of ticket issuing devices a ticket is to be issued is received along with a ticket issuing start operation, and when a determination condition is satisfied, the ticket is printed by the ticket issuing device corresponding to the received identification information. good.

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 prompts the user terminal to access the first site by the user terminal. The access history information to the first site is recorded, the user terminal is made to access the second site in order to perform the ticket issuing start operation, and the user terminal accesses the second site in response to the user terminal It is preferable to acquire access history information to the first site, and the judgment conditions in the judgment made by the control unit are the access history recorded in the user terminal when accessing the first site and the user terminal when accessing the second site. match with the access history acquired from.

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 responds to the access by the user terminal to the first site by the user terminal. First user agent information indicating the user agent used to access the first site is acquired, the user terminal is caused to access the second site in order to perform ticket issuing start operation, and the user terminal accesses the second site. Second user agent information indicating the user agent used for access may be acquired, and the determination condition in the determination performed by the control unit may include matching between the first user agent information and the second user agent information.

A ticket management server according to another embodiment of the present invention includes a control unit, a database that associates and stores ticket IDs that identify tickets and user telephone numbers, and a user terminal of a user via a network. A network communication unit capable of communication and a telephone communication unit capable of communicating with a user terminal through a telephone line are provided. In response to the fact that the user terminal has performed the owner registration start operation for the ticket at the network communication unit, the control unit performs telephone communication within a predetermined valid operation time after the owner registration start operation is performed. The department determines whether or not there is an incoming call from the user's telephone number associated with the ticket ID of the ticket to a predetermined registration telephone number that can receive power, and the ticket is sent to the registration telephone number within the valid operation time. When a determination condition including a call from a user telephone number associated with the ticket ID of is satisfied, the ticket is displayed on the user terminal owned by the user so that it can be used.

In the present invention, it is preferable to transmit the telephone number for registration 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 telephone numbers for registration, and one of the plurality of candidate telephone numbers is notified to the contact of the user as the telephone number for registration in response to the owner registration start operation. do it.

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 responds to the access by the user terminal to the first site. record the access history information to the first site, make the user terminal access the second site in order to perform the owner registration start operation, and the user terminal in response to the user terminal accessing the second site The access history information to the first site should be acquired from the control unit, and the judgment conditions in the judgment made by the control unit are the access history recorded in the user terminal when accessing the first site and the access history used when accessing the second site. match with the access history acquired 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 responds to the access by the user terminal to the first site. acquires the first user agent information indicating the user agent used to access the first site from the user terminal, causes the user terminal to access the second site in order to perform the owner registration start operation, and the user terminal accesses the second site It is preferable to acquire second user agent information indicating the user agent used to access to, and the determination condition in the determination performed by the control unit may include matching between the first user agent information and the second user agent information. .

In order to solve the above problems, a program according to an embodiment of the present invention may cause a computer to function as any 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. 3 is a block diagram showing the configuration of a user terminal 4; FIG. 4 is a flow chart showing a procedure for receiving a ticket; 4 is a flow chart showing a procedure of owner registration processing; Fig. 10 is a flow chart showing a procedure for electronically using a ticket; FIG. 10 is a flow chart showing a procedure of issuing a paper ticket; FIG. 4 is a flow chart showing a procedure for electronically handing over a ticket; 10 is a flow chart showing the procedure of issuing a paper ticket in the second embodiment. FIG. 11 is a flow chart showing the procedure of issuing a paper ticket in the third embodiment. FIG.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[Basic configuration of ticket management system]
As shown in FIG. 1, a ticket management system 1 according to the first embodiment of the present invention comprises a server 2, a plurality of ticket issuing devices 3, and a plurality of user terminals 4. FIG. The server 2, the ticket issuing device 3, and the 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, an arithmetic unit such as a CPU (Central Processing Unit), and storage devices such as RAM (Random Access Memory) and ROM (read only memory). and a display device such as a CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display).

As shown in FIG. 2, the server 2 includes at least a storage unit 201, a control unit 202, a network communication unit 203, and a telephone communication unit 204. FIG. 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 realizing 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 have to be physically integrated with each of the above components. For example, some or all of the above components may be distributed in remote locations, and they may work together to function as the server 2 .

The database DB stores ticket information (e.g., unique ticket ID, performance ID, ticket type, seat number, redemption key, purchaser's user ID, status (used/unused, etc.)) as information on electronic tickets. , ticket image, etc.), information about the user (e.g. unique user ID, name, age, phone number (user phone number), address, gender, other attributes, contact information, etc.), information about the performance (e.g. , event ID, event name, date and time of event, place of event, etc.). In addition, in this embodiment, a mobile phone number and a contact address are required as information about the user. This contact point is a contact point (e-mail address, SNS, etc.) with which the user terminal 4 can transmit and receive information. One ticket ID corresponding to one ticket is associated with one user ID and one entertainment ID. It is possible to specify information on performances that can be entered. When one user purchases multiple tickets for the same performance, multiple ticket IDs linked to the same performance ID are linked to one ticket ID.

The control unit 202 of the server 2 executes processing according to the programs 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 data retrieval, new registration, deletion, and updating with respect to the database DB stored in the storage unit 201, and the ticket issuing device 3, It communicates with the user terminal 4 or the like. Also, the control unit 202 controls the telephone communication unit 204 to acquire the incoming telephone number and transmit necessary voice through the telephone line.

[Configuration of ticket issuing device]
The ticket issuing device 3 prints and issues ticket information on a predetermined sheet based on a command from the server 2 . 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 stores a program that controls the printing unit 304 to print ticket information based on commands from the server 2, and a display unit that displays ticket issuing machine numbers and various screens based on commands from the server 2. A program or the like for controlling 305 is stored. In a ticket management system 1 having 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 has its own ticket issuing machine number. 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 the ticket according to the command from the server 2 and controls the display contents 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. A printing unit 304 is a printer that prints a ticket on a predetermined sheet of paper. The ticket paper may be, for example, a piece of paper pre-cut to a predetermined size and provided with perforations as necessary, or may be roll paper that is cut to a predetermined length each time printing is performed.

The display unit 305 is a display element such as a liquid crystal display that displays the ticket issuing machine number, and displays the ticket issuing machine number, which is an identification number for identifying the ticket issuing device 3, and various notifications 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 . A 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 computing unit such as a CPU, a storage device such as RAM and ROM, a display device such as an LCD, a speaker for outputting sound, and a microphone for collecting sound. etc.

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

An operation unit 401 receives an operation by a user. The operation unit 401 includes a touch panel arranged 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, purchased electronic ticket data 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 or the like to access the server 2, and from the database DB of the server 2, data related to the purchased electronic ticket, etc. is obtained and displayed. In the embodiments described below, it is assumed that 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 . The browser or the like accesses the designated URL to display a website or the like, and as will be described in detail later, performs processing based on various data stored in the storage unit 402 and the operation of the operation unit 401. will be

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

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

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

[Ticket purchase and receipt]
A user purchases a ticket for a desired event from a ticket seller (for example, a ticket sales store, a ticket sales terminal, a ticket site provided on the Internet, etc.). At this time, the user selects various conditions such as the event, the type of seat, the number of seats, and the method of receiving the ticket, and performs the payment procedure. When the electronic ticket is selected as the ticket receiving method, the user uses the ticket management system via his/her mobile terminal. The flow of ticket reception when the electronic ticket is selected as the reception 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 them ( step S100). Then, the server 2 records the user ID received from the seller as the purchaser's user ID linked to the ticket ID received from the seller (step S110). In addition, the server 2 transmits a receipt URL for receiving the purchased ticket at the user terminal 4 to the contact information (e-mail address, SNS account, etc.) linked to the user ID of the purchaser ( step S120). Note that it may be configured so that receipt can be made on the condition that the ticket issue 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 receipt URL transmitted from the server 2 in step S120 using the browser or the like of the user terminal 4 (step S130). As a result, the ticket can be used on the user terminal 4 using a browser or the like. At this time, predetermined identification information is recorded in the browser 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 associates and records the user ID of the purchaser and the cookie. In addition, the server 2 records user agent information (hereinafter referred to as "UA information") indicating the model, browser, OS, etc. of the user terminal 4 that accessed the receipt 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, a user who has purchased a ticket performs owner registration according to the procedure described below.

[Owner registration]
FIG. 6 is a flow chart showing the procedure of owner registration processing. When the user activates 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 the desired ticket is selected from among these, if the owner registration of the ticket has not been completed, the face of the ticket and the owner registration screen for registering the owner of the ticket are displayed (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 or the like used for access and the cookie information left in the browser or the like when the receipt URL was accessed to receive the ticket (step S220 ). Also, the server 2 notifies the user of the telephone number for registration in response to the access to the owner registration screen (step S230). Here, as a method of notifying the user, the telephone number for registration may be sent to the user's contact address, or the user may display it on a web page that can be viewed using a user terminal or the like. You may do so. This telephone number for registration may be a fixed telephone number, or may 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 owner registration processing on the display unit 405 (step S235). When the authentication button is pressed by the user, the server 2 records the pressing time in association with the ticket ID (step S240). The authentication button B1 is an example of an owner registration start operation in the present invention. Further, the user terminal 4 displays the registration telephone number received in step S220 in response to pressing of the authentication button (step S245). Note that the registration telephone number is not transmitted from the server 2 to the user terminal 4 in step S230, but the registration telephone number is transmitted from the server 2 to the user terminal 4 in response to pressing of the authentication button. , may be displayed on the display unit 405 .

Subsequently, the server 2, within a predetermined valid operation time (for example, within 4 seconds) from the pressing time, calls the user phone number recorded in association with the ticket (usually the user terminal 4) to the registered It is determined whether or not a call has been made to the telephone number for the client (step S250). This valid operation time should be short enough to make it difficult for a third party at a remote location to receive the ticket issuing telephone number and dial the telephone number 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 the relevant Whether or not a call has been made to the telephone number for registration is determined as follows. The server 2 uses the telephone communication unit 204 to receive a call to the registration telephone number. 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 that has been called, and confirms whether the ticket ID is a ticket ID whose pressing time is recorded within a period that is the valid operation time before the time of receiving the call. By doing so, it is determined whether or not a call has been made to the registration telephone number within the effective operation time.

If the telephone number for registration is not called within the valid operation time from the pressing time (step S250; No), the owner is not registered, and a screen notifying that the owner registration was not possible is displayed on the user terminal 4. It is displayed on the display unit 405 (step S260), and the owner registration process ends. In addition, if the phone number of the caller is one character different from the user's phone number recorded in connection with the ticket, or if the first letter is missing, etc. It is preferable to configure so as to guide to that effect. By doing so, it is possible to easily notice that the user's telephone number has been registered incorrectly, and to 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 collation processing (step S270). In the matching process, the purchaser's phone number associated with the ticket ID is extracted from the database DB, and matched with the incoming call number in step S250. In addition, the server 2 stores the cookie information and UA information when accessing the receipt URL recorded in association with the purchaser's user ID, and the cookie information and UA information transmitted from the user terminal 4 in step S220. match with If the matching of each information is not confirmed in the collation process (step S270; No), the owner is not registered, and a screen is displayed on the user terminal 4 to notify that the owner registration has not been completed (step S260). ), the owner registration process ends. On the other hand, if matching of information is confirmed in the collation process (step S270; Yes), the server 2 records in the database DB that the owner registration of the ticket has been completed, and uses the ticket in the user terminal 4. It is made displayable in a possible state (step S280). Thereafter, when the browser or the like is activated on the user terminal 4 to access the site of the ticket management system and the ticket is displayed, the ticket is displayed in a usable state.

According to the owner registration process of the procedure described above, the ticket cannot be used unless the person who purchased the ticket registers as the owner, so that illegal transfer or resale can be prevented.
[Use of electronic ticket]

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

FIG. 7 is a flow chart showing an example of the processing procedure of the ticket management system 1 when a ticket whose owner has been registered is electronically used (that is, displayed on the user terminal 4 without issuing a paper ticket). is. The user activates the browser or the like of the user terminal 4 in a state where the user has completed the above-described owner registration in advance, and accesses the ticket face URL for displaying the ticket, thereby displaying the face of the electronic ticket on the user terminal. 4 (step S300) and presented to the attendant at the entrance. Access to the face URL is managed by the server 2 . When accessing the ticket surface URL, the user terminal 4 sends the UA information of the browser used for access and the cookie information left in the browser etc. when accessing the receipt URL to receive the ticket to the server 2. Send.

While visually confirming that the face of the electronic ticket for the event is that of the event, the attendant performs a predetermined deletion operation (for example, performs a predetermined operation on the touch panel of the user terminal 4), "Clear" the ticket as used (step S310). When the user terminal 4 accepts the payment operation, it superimposes a character or image indicating that the ticket has been used (hereinafter referred to as "postmark information") on the face of the ticket, and 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 (immediately after verification or after some time has passed), and the server 2 also The status of the ticket is set to "used" (step S330), and the process ends. When the user terminal 4 accepts the payment operation, it verifies whether the payment operation is correct, and if it is correct, the ticket is regarded as used. good. In addition to verifying the erasing 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 owner of the ticket. may be matched with In the above example, the deletion is performed by accepting the deletion operation on the user terminal 4, but the deletion may be performed by other methods. For example, an identification code (for example, QR code (registered trademark)) is displayed on the display unit 405 of the user terminal 4 along with the face of the ticket. You can also use .

[Issuance of paper tickets]
On the other hand, in the ticket management system 1, it is also possible to issue and use the purchased ticket as a paper ticket. For the issuance of paper tickets, the ticket issuing device 3 may be permanently installed in 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. The ticket may be issued just before the entrance. In the following, a paper ticket issuing process procedure by the ticket management system 1 will be described with reference to the flowchart shown in FIG.

Prior to issuing the ticket, the user activates a browser or the like on the user terminal 4 and accesses the URL of the ticket surface. Access to the face URL is managed by the server 2 . When accessing the ticket surface URL, the user terminal 4 sends the UA information of the browser used for access and the cookie information left in the browser etc. when accessing the receipt URL to receive the ticket to the server 2. Send. The processing procedure up to this point is common to the case of using the ticket electronically.

When the ticket face URL is accessed, the display unit 405 of the user terminal 4 displays an image of the ticket face and a paper issue button. When this paper ticket issuing button is pressed (step S400), the ticket issuing process is started. When the ticket issuing process is started, the ticket cannot be used, transferred, or issued any more.

When the user presses the paper ticket issuing button in step S400, the user terminal 4 displays a screen prompting the user to enter the ticket issuing machine number. When the ticket issuing machine number displayed on the display unit 305 is input to 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 issue button is an example of the ticket issue 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 it (step S420). At this time, the server 2 associates and records the ticket ID of the ticket to be issued and the ticket issuing telephone number. The telephone number for issuing a ticket may be a fixed telephone number, but it is also possible to transmit one number selected from a plurality of candidate telephone numbers and use a different number each time it is displayed. Note that in the configuration in which the ticket issuing telephone number is individually assigned to each ticket issuing device 3 as the ticket issuing machine number, steps S410 and 420 can be omitted, and the telephone number for ticket issuing displayed on the display unit 305 is called. You can start the ticketing process. Therefore, paper tickets can be issued even from a terminal on which a dedicated application cannot be installed.

Subsequently, the user terminal 4 displays on the display unit 405 the telephone number for ticketing received in step S420 and a verification start button for starting verification for issuing a paper ticket (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. FIG. When the collation start button is pressed by the user, the server 2 records the pressing time in association with the ticket ID (step S440).

Subsequently, the server 2 issues the ticket from the telephone of the user telephone number recorded in association with the ticket (usually the user terminal 4) within a predetermined valid operation time (for example, within 4 seconds) from the pressing time. It is determined whether or not a call has been made to the telephone number (step S450). This effective operation time should be short enough to make it difficult to transmit the telephone number for ticket issuing 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, from the telephone of the user telephone number recorded in association with the ticket (usually the user terminal 4) Whether or not a call has been made to the ticket issuing telephone number is determined as follows. The server 2 receives a call to the ticket issuing telephone 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 that has been called, and confirms whether the ticket ID is a ticket ID whose pressing time is recorded within a period that is the valid operation time before the time of receiving the call. Thus, it is determined whether or not a call has been made to the ticket issuing telephone number within the valid operation time.

If the telephone number for ticket issuance is not called within the valid operation time from the pressing time (step S450; No), the ticket is not issued and the fact that the ticket cannot be issued is notified. This 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 phone number of the caller is one character different from the user phone number recorded with the ticket, or if the first letter is missing, etc. It is preferable to configure so as to guide to that effect. By doing so, it is possible to easily notice that the user's telephone number has been registered incorrectly, and to 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 collation processing (step S470). In the verification process, the user's telephone number associated with the ticket ID is extracted from the database DB, and verified with the incoming call number in step S450. In addition, 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 surface URL. do. If it is not confirmed that the information matches in the collation process (step S470; No), the ticket is not issued, and a guidance screen notifying that the ticket cannot be issued is displayed on the display unit 405 of the user terminal 4. The ticket is returned to a usable state (step S460), and the ticket issuing process ends.

On the other hand, if matching of the information is confirmed in the collation process (step S470; Yes), the server 2 records in the database DB that the paper ticket was issued for the ticket, and the ticket issuing machine number received in step S420. A command to print the ticket is transmitted from the printing unit 304 to the ticket issuing device 3 (step S480). The ticket issuing device 3 having the relevant ticket issuing machine number receives this command, prints the ticket by the printing unit 304 (step S490), and ends the ticket issuing process.

As described above, paper tickets can be issued. In the ticket issuing process of this embodiment, verification is performed using the telephone number, cookie information, UA information, etc. at the time of ticket issuance, thereby preventing the issuance of illegal tickets due to, for example, performing the operations necessary for verification from a remote location. can do. The found paper ticket can be used at the entrance of the event in the same way as a conventional paper ticket.

[Ticket stub issue]
The paper ticket issuing process described above can be applied not only to issuing unused paper tickets, but also to issuing used ticket stubs after entering with an electronic ticket. . It is preferable to redeem the ticket at the entrance of the event site, and then issue a stub after verification by telephone number, cookie, UA, etc. in the same procedure as the ticket issuing process described above. In this case, the ticket issuing device 3 may be provided inside the venue (for example, immediately after passing through the entrance). In this way, when an electronic ticket is used for a plurality of people to enter at once, the ticket can be used as a certificate for guidance of the seat number, re-entry, etc. to the visitors who do not have the user terminal 4. A stub can be issued. In addition, paper stubs can be issued in preparation for the case where the remaining battery level of the user terminal 4 is insufficient. It should be noted that the user terminal 4 displays a message on the display unit 405 or It is preferable to prompt the user to issue a paper stub by emitting a notification sound.

[Ticket transfer]
The ticket management system 1 makes it possible to transfer managed tickets from owners to others.

The transfer of the ticket can be done by electronically handing over the ticket by re-registering the person to whom the ticket is to be transferred, or by issuing a paper ticket and handing over the ticket.

[Electronic ticket transfer]
The procedure of the electronic ticket delivery method will be described with reference to the flow chart shown in FIG. In the method of electronically handing over a ticket, first, the user who is the transfer source completes the above-mentioned owner registration in advance, and accesses the ticket face URL to display the ticket to be transferred. Then, the recipient registration button displayed together with the face of the bill is pressed (step S600). When this delivery destination registration button is pressed, a screen prompting the user to enter 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 recorded in the database DB in association with the ticket ID (step S620). Further, the browser or the like of the transfer source user is placed in a state in which the ticket cannot be used or further transferred (step S630).

Upon receiving the ticket ID and the telephone number of the transferee, the server 2 issues an owner registration URL for accessing an owner registration screen for the user of the transferee to perform owner registration processing. is sent to the user's contact information (e-mail address, SNS, etc.) (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 transferee user without going through the transferor user.

The transfer destination user receives the URL transmitted in step S650 using his/her own user terminal 4 (step S660). Then, the transferee user performs owner registration by the same method as steps S200 to S280 in the owner registration process (FIG. 6) at the time of purchase. The server 2 determines whether or not the owner registration by the transferee user has been completed normally within a predetermined period (step S670). When it is determined that the transaction has been completed normally (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 transfer destination user (step S680). On the other hand, if the owner registration by the user of the transferee is not completed normally, for example, if the owner registration is not completed within a predetermined transfer effective period (step S670; No), the server 2 will call the transferee's phone. The record of the number is deleted from the database DB, and the ticket can be displayed in a usable state on the user terminal 4 of the transfer source user (step S690).

As described above, the ticket can be transferred electronically. In this way, even when a ticket is electronically transferred, the same owner registration as at the time of purchase is required, so that the ticket management system 1 can grasp the transfer source and the transfer destination, thereby preventing unauthorized transfer. Resale can be deterred.

[Transfer of paper ticket]
On the other hand, the method of issuing and handing over a paper ticket is a method in which the user, who is the owner, issues a ticket using the ticket issuing device 3 and hands over the issued ticket to the transferee. The issuance of paper tickets may be realized in the same manner as the issuance of paper tickets described above. Note that even when a paper ticket is transferred, unauthorized transfer or resale can be prevented by requiring owner registration before issuing the paper ticket. In this case, if the name of the user registered as the owner is printed on the surface of the paper ticket to be issued, the effect of deterring illegal transfer or resale can be particularly expected.

[Second embodiment]
The ticket management system according to the second embodiment of the present invention differs from the first embodiment in the method of issuing paper tickets. That is, the second embodiment is the same as the first embodiment until collation (step S450 in FIG. 8) is performed. They differ in the hardware configuration associated with the procedure.

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

When the ticket face URL is accessed, the display unit 405 of the user terminal 4 displays an image of the ticket face and a paper issue button. When this paper ticket issuing button is pressed (step S700), the ticket issuing process is started. When the ticket issuing process is started, the ticket cannot be used, transferred, or issued any more.

When the user presses the paper ticket issue button in step S700, the user terminal 4 displays a screen prompting the user to enter the ticket issuing machine number. When the ticket issuing machine number displayed on the display unit 305 is input to 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 issue button is an example of the ticket issue start operation in the present invention. When the server 2 receives 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, or may 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 telephone number for ticketing received in step S720 and a verification start button for starting verification for issuing a paper ticket (step S730). When the user presses the collation start button, the server 2 records the pressing time (step S740).

Subsequently, the server 2 issues the ticket from the telephone (usually the user terminal 4) of the user telephone number recorded in association with the ticket within a predetermined valid operation time (for example, within 4 seconds) from the pressing time. It is determined whether or not a call has been made to the telephone number (step S750). This effective operation time should be short enough to make it difficult to transmit the telephone number for ticket issuing 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 the relevant Whether or not a call has been made to the ticket issuing telephone number is determined as follows. The server 2 receives a call to the ticket issuing telephone 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 that has been called, and confirms whether the ticket ID is a ticket ID whose pressing time is recorded within a period that is the valid operation time before the time of receiving the call. Thus, it is determined whether or not a call has been made to the ticket issuing telephone number within the valid operation time.

If the telephone number for ticket issuance is not called within the valid operation time from the time of pressing (step S750; No), the ticket is not issued and a notification is sent to the effect that the ticket cannot be issued. This 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 phone number of the caller is one character different from the user's phone number recorded in connection with the ticket, or if the first letter is missing, etc. may be configured to guide the By doing so, it is possible to easily notice that the user's telephone number has been registered incorrectly, and to 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 collation processing (step S770). In the matching process, the user's telephone number associated with the ticket ID is extracted from the database DB and compared with the incoming call number in step S750. In addition, 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 surface URL. do. If it is not confirmed that the information matches in the collation process (step S770; No), the ticket is not issued, and a guidance screen notifying that the ticket cannot be issued is displayed on the display unit 405 of the user terminal 4. The ticket is returned to a usable state (step S760), and the ticket issuing process ends.

On the other hand, when matching of information is confirmed in the collation process (step S770; Yes), the server 2 starts voice communication of the telephone received in step S750 in the telephone communication unit 204 (step S780). Then, the telephone communication unit 204 transmits to the user terminal 4 a data-embedded voice in which information (hereinafter referred to as "ticket issuing information") for causing the ticket issuing device 3 to print the ticket is embedded in the voice call ( step S790). Note that the voice call may be disconnected after a predetermined call time has passed. Here, the ticket issue information may include all data on the face of the ticket, or may include only the encrypted ticket ID as necessary. If only the ticket ID is used as the ticket issuing information, the ticket issuing device 3 preferably receives data in which the ticket ID and the data on the face of the ticket are associated with each other from the server 2 in advance and stores the data in the storage unit 301 . Alternatively, each time the ticket issue information is received, the data on the face of the ticket corresponding to the ticket ID may be inquired of the server 2 and received via the network NW. The ticket issuing information may also include the ticket issuing machine number entered in step S710. The ticket issue information may also include time stamp information indicating the time of the ticket issue process, such as the pressing time recorded in step S740 and the time when the telephone number for ticket issuance 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 to the microphone 306 (step S800). The ticket issuing device 3 decodes the voice input to the microphone 306 and acquires ticket issuing information (step S810). Then, the ticket issuing device 3 determines whether or not 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. When the ticket issuing information includes the ticket issuing machine number, the matching of the ticket issuing machine number of the ticket issuing device 3 to which the data-embedded voice is input and the ticket issuing machine number included in the ticket issuing information is included in the condition for judging validity. good. If the ticketing information includes time stamp information, it is preferable that the current time is included within a predetermined ticketing valid period from the time indicated by the time stamp information as a condition for judging validity. The valid period of ticketing should be set to a length of time (for example, 3 minutes) that makes it difficult to record the data-embedded voice and send it to a remote location via the network NW or the like. Also, the condition may include that the voice is input within a predetermined time period after matching of the information is confirmed in the matching process. In addition, it is preferable to include in the conditions for judging validity that information indicating that the collation has been performed in step S780 is included in the ticketing information.

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

On the other hand, if the received ticket issuance information is not valid (step S820; No), the ticket issuing device 3 displays on the display unit 305 that the ticket cannot be issued, and indicates that the ticket has not been issued as a result of the judgment in step S840. Information indicating that is transmitted to the server 2 (step S850). Upon receiving this, the server 2 restores the ticket to a usable state (step S860), and terminates the ticket issuing process.

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

[Modification of Second Embodiment]
In the above-described second embodiment, data-embedded voice is transmitted from the server 2 and received by the user terminal 4 by voice communication 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 output from the speaker 407 of the user terminal 4 . For example, the data-embedded voice is transmitted from the server 2 by live streaming via the network NW, received by the user terminal 4, and is output from the speaker 407 by streaming-playing the data-embedded voice on the user terminal 4. You may make it In addition, the data-embedded voice is transmitted as a voice data file via the network NW, received by the user terminal 4, and the data-embedded voice is reproduced by the user terminal 4. may be output from the speaker 407 . According to these methods, since the data-embedded voice is not degraded in the transmission process from the server 2 to the user terminal 4, it is possible to prevent errors from occurring in the transmission of the ticketing information.

In addition, in a configuration in which data-embedded voice is transmitted as a voice data file via the network NW, the transfer of the voice data file received by the user terminal 4 is restricted, or the voice data file is transmitted to another terminal. It may be configured to restrict playback. For example, the voice data may be associated with cookie information at the time of ticket issuing processing, session information of data communication via the network NW, etc., so that the voice data file can be reproduced only at 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 differs from the first embodiment in the method of issuing paper tickets. That is, the second embodiment is the same as the first embodiment until collation (step S450 in FIG. 8) is performed. They differ in the hardware configuration associated with the procedure.

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

When the ticket face URL is accessed, the display unit 405 of the user terminal 4 displays an image of the ticket face and a paper issue button. When this paper ticket issuing button is pressed (step S900), the ticket issuing process is started. When the ticket issuing process is started, the ticket cannot be used, transferred, or issued any more.

When the user presses the paper ticket issuing button in step S900, the user terminal 4 displays a screen prompting the user to enter the ticket issuing machine number. When the ticket issuing machine number displayed on the display unit 305 is input to 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 issue button is an example of the ticket issue 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, or may 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 telephone number for ticketing received in step S720 and a verification start button for starting verification for issuing a paper ticket (step S930). When the user presses the collation start button, the server 2 records the pressing time (step S940).

Subsequently, the server 2 issues the ticket from the telephone (usually the user terminal 4) of the user telephone number recorded in association with the ticket within a predetermined valid operation time (for example, within 4 seconds) from the pressing time. It is determined whether or not a call has been made to the telephone number for the client (step S950). This effective operation time should be short enough to make it difficult to transmit the telephone number for ticket issuing 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 the relevant Whether or not a call has been made to the ticket issuing telephone number is determined as follows. The server 2 receives a call to the ticket issuing telephone 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 that has been called, and confirms whether the ticket ID is a ticket ID whose pressing time is recorded within a period that is the valid operation time before the time of receiving the call. Thus, it is determined whether or not a call has been made to the ticket issuing telephone number within the valid operation time.

If the telephone number for ticket issuance is not called within the effective operation time from the pressing time (step S950; No), the ticket is not issued and the fact that the ticket cannot be issued is notified. This 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. If the caller's telephone number is different from the user's telephone number recorded in association with the ticket by one character, etc., it is preferable to provide guidance to that effect. By doing so, it is possible to easily notice that the user's telephone number has been registered incorrectly, and to 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 collation processing (step S970). In the verification process, the user's telephone number associated with the ticket ID is extracted from the database DB, and verified with the incoming call number in step S950. In addition, 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 surface URL. do. If it is not confirmed that the information matches in the collation process (step S970; No), the ticket is not issued, and a guidance screen notifying that the ticket cannot be issued is displayed on the display unit 405 of the user terminal 4. The ticket is returned to a usable state (step S960), and the ticket issuing process ends.

On the other hand, if matching of information is confirmed in the collation process (step S970; Yes), the server 2 transmits an identification code (bar code, QR code (registered trademark), etc.), and the display unit 405 of the user terminal 4 is displayed (step S980). The identification code transmitted by the server 2 may include data on the face of the ticket, or may be only an encrypted ticket ID as required. When only the ticket ID is included, the ticket issuing device 3 preferably receives data in which the ticket ID and the data on the face of the ticket are associated with each other from the server 2 in advance and stores the data in the storage unit 301 . Alternatively, each time the identification code is read, the ticket face data corresponding to the ticket ID may be inquired of the server 2 and received via the network NW. The identification code may also include information such as a URL indicating the location of information necessary for issuing a ticket on the network NW. The identification code may also include the ticket issuing machine number entered in step S910. The identification code may also include time stamp information indicating the time of the ticket issuing process, such as the pressing time recorded in step S940 and the time when the telephone number for issuing a ticket was called. It is preferable that the identification code is displayed on the display unit 405 of the user terminal 4 so that the display disappears when a predetermined time elapses.

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

Whether or not the received identification code is legitimate can be determined, for example, as follows. When the identification code includes the ticket issuing machine number, it is preferable to include the match between the ticket issuing machine number of the ticket issuing device 3 that reads the identification code and the ticket issuing machine number included in the identification code as a condition for judging validity. If the identification code includes time stamp information, it is preferable that the current time is within a predetermined ticket valid period from the time indicated by the time stamp information. Also, the condition may include that the identification code is read within a predetermined period of time after the match of the information is confirmed in the collation process. In addition, it is preferable to include information indicating that the verification in step S980 has been performed in the ticketing information as a condition for judging validity.

If the read identification code is valid (step S1020; Yes), the ticket issuing device 3 prints the ticket by the printing unit 304, and as a result of the determination in step S1020, information indicating that the ticket has been issued. to the server 2 (step S1030). In response to this, the server 2 records in the database DB that the paper ticket has been issued (step S1040), and terminates 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 has not been issued. Information or the like indicating this is transmitted to the server 2 (step S1050). In response to this, the server 2 restores the ticket to a usable state (step S1060), and terminates the ticket issuing process.

As described above, when a paper ticket is issued, the identification code displayed on the user terminal 4 is read by the ticket issuing device 3, so even if a call from a remote location succeeds during verification, the ticket is issued. Since the identification code necessary for the identification code cannot be transmitted to the ticket issuing device 3, it is possible to more effectively prevent the issuance of illegal tickets.

Although the embodiments of the present invention have been described above, the present invention is not limited to these examples. In addition, additions, deletions, and design changes made by those skilled in the art to the above-described embodiments, and combinations of the features of each embodiment as appropriate also include the gist of the present invention. as long as it is 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 (17)

a control unit;
a database that associates and stores ticket IDs that identify tickets and user telephone numbers;
a communication unit capable of communicating with a user terminal of a user via a network;
A ticket management server comprising:
The control unit
Determining whether or not there is an incoming call from the user telephone number associated with the ticket ID of the ticket to a predetermined ticket issuing telephone number capable of receiving power in the communication unit,
causing the ticket issuing device to issue the ticket when a determination condition including that the user telephone number associated with the ticket ID of the ticket is called by the ticket issuing telephone number is satisfied; A ticket management server characterized by: In response to the fact that a ticket issuing start operation has been performed on the user terminal by the communication unit, the control unit sends the ticket to a predetermined ticket issuing telephone number that can be received by the communication unit. 2. The ticket management server according to claim 1, wherein it is determined whether or not there is an incoming call from said user telephone number associated with said ticket ID. The communication unit
a network communication unit capable of communicating with the user terminal and the ticket issuing device of the user via a network;
A telephone communication unit capable of communicating with the user terminal through a telephone line,
The control unit
In response to the receipt by the network communication unit of the operation to start issuing a ticket at the user terminal, within a predetermined effective operation time after the operation to start issuing the ticket, to the telephone communication unit. determining whether or not there is an incoming call from the user telephone number associated with the ticket ID of the ticket to a predetermined ticket issuing telephone number capable of receiving power through
When a judgment condition is satisfied, including that there is a call from the user's telephone number associated with the ticket ID of the ticket to the ticket-issuing telephone number within the valid operation time, the ticket is issued to the ticket issuing device. 3. The ticket management server according to claim 2, wherein the ticket management server transmits a command to issue a . The communication unit
a network communication unit capable of communicating with the user terminal of the user via a network;
A telephone communication unit capable of communicating with the user terminal through a telephone line,
The control unit
In response to the receipt by the network communication unit of the operation to start issuing a ticket at the user terminal, within a predetermined effective operation time after the operation to start issuing the ticket, to the telephone communication unit. determining whether or not there is an incoming call from the user telephone number associated with the ticket ID of the ticket to a predetermined ticket issuing telephone number capable of receiving power through
To issue the ticket when a judgment condition including that the user telephone number associated with the ticket ID of the ticket has been called to the ticket issuing telephone number within the effective operation time. wherein the data-embedded voice embedded with the ticket issuing information is output from the speaker of the user terminal, and the ticket issuing device is caused to issue the ticket based on the data-embedded voice output from the user terminal. The ticket management server according to item 1. 5. The ticket management server according to claim 4, wherein the ticket issuing information embedded in the data-embedded voice includes printed contents of the surface of the ticket to be issued. 6. The ticket management server according to claim 4, wherein said data-embedded voice is transmitted to said user terminal by voice communication through a telephone line. 6. The ticket management server according to claim 4, wherein the data-embedded voice is transmitted to the user terminal by live streaming through a network. 6. The ticket management server according to claim 4, wherein said data-embedded voice is transmitted to said user terminal through a network as a voice data file containing said data-embedded voice. Receiving identification information indicating from which one of the plurality of ticket issuing devices the ticket is to be issued in response to the ticket issuing start operation;
9. The ticket management server according to any one of claims 1 to 8, wherein the ticket issuing device corresponding to the received identification information is caused to print the ticket when the determination condition is satisfied. The ticket management server prompts the user terminal of the user to access the first site before the ticket issuance 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 the second site in order to perform the ticket issuing start operation, and obtaining access history information from the user terminal to the first site in response to the user terminal accessing the second site; Acquired,
The judgment conditions in the judgment performed by the control unit are the access history recorded in the user terminal when accessing the first site and the access history obtained from the user terminal when accessing the second site. 10. A ticket management server according to any one of claims 1 to 9, characterized in that it includes that . The ticket management server prompts the user terminal of the user to access the first site before the ticket issuance start operation,
Acquiring first user agent information indicating a user agent used to access the first site from the user terminal 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 ticket issuing start operation, acquiring second user agent information indicating a user agent used by the user terminal to access the second site;
11. The method according to any one of claims 1 to 10, wherein the determination condition in the determination performed by the control unit includes matching between the first user agent information and the second user agent information. Ticket management server. a control unit;
a database that associates and stores ticket IDs that identify tickets and user telephone numbers;
a network communication unit capable of communicating with the user terminal of the user via a network;
A ticket management server comprising a telephone communication unit capable of communicating with the user terminal through a telephone line,
The control unit
the telephone communication within a predetermined effective operation time after the owner registration start operation is performed in response to the fact that the user terminal has performed the owner registration start operation for the ticket, in response to the reception by the network communication unit; 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 registration phone number that can receive power in the department,
If a judgment condition is satisfied, including that there was a call from the user telephone number associated with the ticket ID of the ticket to the registration telephone number within the valid operation time, the ticket is transferred to the user. A ticket management server that displays the available information on the user terminal of . 13. The ticket management server according to claim 12, wherein the telephone number for registration is transmitted to the contact information of the user in response to the owner registration start operation. A plurality of candidate telephone numbers are provided as the registration telephone numbers,
14. The ticket management system according to claim 13, wherein in response to said owner registration start operation being performed, one of a plurality of candidate telephone numbers is notified to said user's contact information as said registration telephone number. server. The ticket management server prompts the user terminal of the user to access the 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;
making the user terminal access the 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; and get
The judgment conditions in the judgment performed by the control unit are the access history recorded in the user terminal when accessing the first site and the access history obtained from the user terminal when accessing the second site. 15. A ticket management server according to any one of claims 12 to 14, characterized in that it includes that . The ticket management server prompts the user terminal of the user to access the first site before the owner registration start operation,
Acquiring first user agent information indicating a user agent used to access the first site from the user terminal 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, obtaining second user agent information indicating a user agent used by the user terminal to access the second site;
16. The method according to any one of claims 12 to 15, wherein the determination condition in the determination performed by the control unit includes matching between the first user agent information and the second user agent information. Ticket management server. A program that causes a computer to function as the ticket management server according to any one of claims 1 to 16.

Images