GB2436446A

GB2436446A - Multiple ticket reservation system

Info

Publication number: GB2436446A
Application number: GB0704523A
Authority: GB
Inventors: Takahito Igarashi
Original assignee: Oki Electric Industry Co Ltd
Current assignee: Oki Electric Industry Co Ltd
Priority date: 2006-03-20
Filing date: 2007-03-08
Publication date: 2007-09-26
Also published as: GB0704523D0; JP4311408B2; JP2007257053A

Abstract

A ticket issue system that can issue plural tickets can be issued from one item of information is provided. A ticket server (120) includes a ticket information storage unit (127) that associates an item of ticket link information with information on plural reserved tickets and stores the information, a code creation unit (126) that creates a ticket information code including the ticket link information, and a ticket issue processing unit (125) that receives the ticket information code from a ticket verification terminal (400), and transmits the information on the plural tickets associated with the ticket information code to the ticket verification terminal. Each user terminal (300) includes a code receiving unit that receives the ticket information code from the ticket server (120). The ticket verification terminal (400) includes a code referral processing unit (403) that checks the ticket information code with the ticket server (120) and receives ticket information.

Description

TICKET ISSUE SYSTEM AND TICKET SERVER

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates to a ticket issue system and a ticket server. More particularly, the present invention relates to a ticket issue system and a ticket server using an electronic ticket.

Description of the Related Art

As a substitute for paper tickets used as entrance tickets when seeing movies, concerts, sport games, exhibitions of an IT field, and the like, electronic tickets using cellular phones, IC cards or the like have been increasingly used. When using a cellular phone as an electronic ticket, a user accesses the Internet through the cellular phone, makes a code, such as a QR code, used as a substitute for an entrance ticket, displayed on a screen of the cellular phone, holds the cellular phone over a read device (reader) that is disposed in an entrance of a concert hail or an exhibit hall for the code to be scanned, and gains admission.

Generally, it has been only an individual person who reserves a ticket using a cellular terminal that can purchase the ticket, and has not been possible to reserve arid issue tickets corresponding to plural persons at the same time. In order to resolve this problem, for example, JP-A-2002-366817 p has disclosed a reservation and ticketing system in which tickets corresponding to plural persons can be simultaneously reserved or ticketed through one portable terminal.

However, according to the reservation and ticketing system that is disclosed in JP-A-2002-366817, there is a problem in that the people other than the representative or approver who has reserved the tickets cannot gain admission when they are not accompanied by the representative or the approver. That is, since one code corresponds to one ticket, plural tickets cannot be issued from the one code.

SUMMARY OF THE INVENTION

The present invention has been made in view of the above circumstances and provides a ticket issue system and a ticket server.

According to an aspect of the invention, there is provided a ticket issue system, comprising: a ticket server that issues reserved tickets; one or more user terminals that receive the tickets; and a ticket verification terminal that verifies the tickets, wherein the ticket server comprises: a ticket information storage unit that stores an item of ticket link information so as to be associated with information on the plural reserved tickets; a code creation unit that creates a ticket information code including the ticket link information; and a ticket issue processing unit that receives p the ticket information code from the ticket verification terminal, and transmits the information on the plural tickets associated with the ticket information code to the ticket verification terminal, each of the user terminals comprises a code receiving unit that receives the ticket information code from the ticket server, and the ticket verification terminal comprises a code referral processing unit that checks the ticket information code received from the user terrriinal with the ticket server and receives the information on the tickets.

According to this structure, if the ticket verification terminal transmits an item of ticket information code read from the user terminal to the ticket server, the ticket server transmits to the ticket verification terminal, the information on the plural tickets which is associated with the item of ticket information code by the ticket link information. As a result, the ticket verification terminal can acquire information on the plural tickets from the one ticket information code read from the user terminal.

Furthermore, the ticket issue system according to the aspect of the invention may include a reservation terminal that reserves tickets and a ticket reservation host that performs a ticket reservation process on the basis of reservation data transmitted from the reservation terminal. The ticket reservation host may include a reservation data transmission unit that transmits to the ticket server, the reservation data on the basis of which the reservation process is completed, and notifies the ticket server of a ticket issue request. The ticket issue processing unit of the ticket server may store the reservation data received from the ticket reservation host in the ticket information storage unit, and notifies the reservation terminal of information indicating a destination for connection to the ticket server.

Here, the reservation terminal may include a ticket link information transmission unit that transmits the ticket link information to the ticket server based on reception destinations of the reserved tickets. Accordingly, the ticket issue processing unit of the ticket server can acquire the ticket link information received from the reservation terminal and store it in the ticket information storage unit so as to be associated with the reservation data stored in the ticket information storage unit. As such, by associating the ticket link information with the reservation data, it becomes possible to associate the plural reservation data with each other by the ticket link information.

The ticket issue processing unit of the ticket server may create verification data for verifying the ticket information code, and store the created verification data in the ticket information storage unit so as to be associated with the ticket link information. The verifictjon data is a code for verifying the ticket information code that is read from b the user terminal by the ticket verification terminal. Here, the ticket issue processing unit of the ticket server may communicate the ticket information code including the verification data in response to a request from the user terminals. For example, the ticket issue processing unit of the ticket server may notify the user terminals of connection destination information for acquiring the ticket information code, and notify the user terminal of the ticket information code when the user terminal is connected to the destination for connection using the connection destination information.

The ticket issue processing unit of the ticket server may compare the ticket information code received from the ticket verification terminal and the verification data stored in the ticket information storage unit, and determine whether the tickets are issued or not on the basis of the comparison result. For example, when the ticket information code received from the ticket verification terminal is verified, the ticket issue processing unit of the ticket server may transmit the information on the plural tickets associated with the verified ticket information code to the ticket verification terminal.

According to another aspect of the invention, there is provided a ticket server issues reserved tickets, comprising: a ticket information storage unit that stores an item of ticket link information so as to be associated with information on ) the plural reserved tickets; a code creation unit that creates a ticket information code comprising the ticket link information; and a ticket issue processing unit that issues information on the plural tickets associated with the ticket information code. According to this structure, the ticket server can transmit the information on the plural tickets by one item of ticket link information.

Here, the ticket issue processing unit may store the item of ticket link information so as to be associated with the information on the plural tickets stored in the ticket information storage unit, on the basis of reception destinations information of the tickets.

The ticket issue processing unit may create verification data for verifying the ticket information code, and store the created verification data in the ticket information storage unit so as to be associated with the ticket link information.

Furthermore, the ticket issue processing unit may compare the ticket information code transmitted to the ticket server and the verification data stored in the ticket information storage unit, and determine whether the tickets are issued or not on the basis of the comparison result. For example, when the ticket information code is verified, the ticket issue processing unit may issue the information on the plural tickets associated with the verified ticket information code.

According to the aspects of the invention, it is possible to provide a ticket issue system and a ticket server that are capable of issuing plural tickets from one item of information on the tickets.

BRIEF DESCRIPTION OF THE DRJ\WINGS

Preferred exemplary embodiments of the present invention will, be described in detail based on the following figures, wherein: Fig. 1 is a diagram illustrating a schematic structure of a ticket issue system according to an embodiment of the invention; Fig. 2 is a block diagram illustrating schematic structures of devices that are included in a ticket issue system according to an embodiment of the invention; Fig. 3A is a diagram illustrating contents stored in a reservation data storage unit; Fig. 3B is a diagram illustrating contents stored in a user information storage unit; Fig. 4A is a diagram illustrating contents stored in a ticket information storage unit; Fig. 4B is a diagram illustrating contents stored in a group ID storage unit; Fig. 4C is a diagram illustrating contents stored in a verification data storage unit; Fig. 5 is a flowchart illustrating a schematic flow of a ticket reserving process according to an embodiment of the invention; Fig. 6 is a flowchart illustrating a schematic flow of a ticket distributing process according to an embodiment of the invention; Fig. 7 is a flowchart illustrating a group ID and verification data creating sequence; Fig. 8 is a flowchart illustrating a schematic flow of a ticket issuing process according to an embodiment of the invention; Fig. 9isadiagramillustratingan example ofa reception destination input screen; and Fig. 10 is a diagram illustrating an example of a confirmation screen.

DETAILED DESCRIPTION OF THE INVENTION

Hereinafter, the preferred embodiments of the invention will be described in detail with reference to the accompanying drawings. Note that, in the present specification and the drawings, constituent elements that have substantially the same functional structures are denoted by the same reference

numeral so as to avoid the repetitive description.

First, a schematic structure of a ticket issue system according to an embodiment of the invention will be described with reference to Fig. 1. Fig. 1 is a diagram illustrating a schematic structure of a ticket issue system according to an embodiment of the invention.

As shown in Fig. 1, a ticket issue system 1 according to an embodiment of the invention includes an electronic ticket selling site 100 that sells a ticket for a concert, a movie or the like, a reservation terminal 200 that reserves the ticket, a user terminal 300 that receives the ticket reserved using the reservation terminal 200, a ticket verification terminal 400, and a communication network 500, such as an Internet network. Further, the communication network 500 includes a cellular phone communication network.

The electronic ticket selling site 100 is a ticket selling service site using the communication network 500, such as the Internet, and can issue a ticket having been purchased by a customer who reserves the ticket as an electronic ticket.

For example, the electronic ticket selling site 100 can be constructed as a membership site where a ticket selling service is provided to members who have been registered as the members.

The members each register member information, such as name or mail address, in advance, and thus can use the ticket issue system 1 according to this embodiment. The electronic ticket selling site 100 includes a ticket reservation host 110, a ticket server 120, and a mail server 130.

The ticket reservation host 110 reserves a ticket according to a ticket reservation application from the customer, notifies the ticket server 120 of the reservation information so as to request the issue of an electronic ticket.

The ticket reservation host 110 according to this embodiment is constructed as a host, but may be constructed as a server including a Web server.

The ticket server 120 receives the electronic ticket issue request from the ticket reservation host 110 and performs an issue process on the reserved ticket. Further, according to the request from the user terminal 300, the ticket server issues the ticket transferred to the user from the customer who reserves the ticket as an electronic ticket that is obtained by converting the ticket into a two-dimensional code, such as, for example, a QR code.

The mail server 130 is a server that is used when transmitting an electronic mail from the ticket server 120 to the reservation terminal 200 or the user terminal 300.

The reservation terminal 200 is a terminal that is used by the customer when the customer reserves the ticket, designates a ticket recipient, or distributes the ticket. As the reservation terminal 200, a terminal (for example, a personal computer, a cellular phone, and the like) that is capable of accessing the Internet can be used.

The user terminal 300 is a terminal through which the ticket assigned to the user from the customer who reserves the ticket is acquired as the electronic ticket, and may be a terminal (for example, a personal computer, a cellular phone, and the like) that can access the Internet. Further, the user terminal 300 displays the two-dimensional code acquired as the electronic ticket so as to be used as a substitute for an entrance ticket used when entering an event site.

The ticket verification terminal 400 is a terminal that reads the two-dimensional code displayed on the user terminal 300 and verifies the ticket. For example, the ticket verification terminal 400 is disposed in an event site and transmits verification information included in the two-dimensional code read from the user terminal 300 to the ticket server 120. Then, the ticket server 120 notifies the user of the verification result on the two-dimensional code.

At this time, when the two-dimensional code is verified, a process is performed for allowing the user to enter the event site by opening a gate of the event site or issuing a ticket stub to the user. In contrast, when the two-dimensional code is not verified, a process is performed for transmitting to the user, amessage indicating that the code cannot be verified.

In this ticket issue system 1, first, the customer accesses the electronic ticket selling site 100 by using the reservation terminal 200, such as the personal computer, and reserves plural tickets. If the ticket reservation is completed, a URL on a page (ticket receiving destination information input page) for inputting ticket receiving destinations as connection destination information is transmitted to the reservation terminal 200 from the ticket server 120 by sending a mail through the mail sever 130. The customer who is notified of the URL on the ticket receiving destination information input page accesses the ticket receiving destination information input page and inputs mail addresses or the like that are the information indicating the ticket receiving destination. In addition, on the basis of the information input by the customer, the ticket server 120 notifies the user terminal 300, such as the cellular phone, of a URL on a page (download page) for downloading a two-dimensional code serving as the connection destination information by sending a mail through the mail server 130.

The user who is notified of the URL on the download page accesses the notified download page using the user terminal 300, such as, for example, the cellular phone, and downloads a two-dimensional code functioning as substitute for a paper ticket through the user terminal 300. In addition, the user makes the downloaded two-dimensional code displayed on a screen of the user terminal 300, and holds the user terminal 300 over the ticket verification terminal 400 that is disposed in the event site or the like, such that the ticket is verified.

When the ticket is verified, the user can enter the event site, but when the ticket is not verified, the user is notified of a message indicating that the user cannot enter the event site.

Next, respective devices that are included in the ticket issue system 1 according to the embodiment of the invention will be described with reference to Fig. 2. Fig. 2 is a block diagram illustrating schematic structures of devices that are included in a ticket issue system 1 according to the embodiment of the invention.

As shown in Fig. 2, the ticket reservation host 110 includes a communication unit ill, a reservation management processing unit 113, and a reservation data storage unit 115.

The communication unit ill exchanges ticket reservation data with the reservation terminal 200 through the communication network 500. Further, when the reservation is completed, the ticket reservation host 110 transmits the ticket reservation data to the ticket server 120, and requests the ticket server to issue an electronic ticket.

The reservation management processing unit 113 confirms whether it is possible to make a reservation according to the contents of reservation application data received from the reservation terminal 200. The reservation data storage unit is for storing reservation data, and includes a memory, such as, for example, a RPi'4 or a hard disk. Specifically, as shown in Fig. 3A, the reservation data storage unit 115 stores ticket reservation information including an event name 115a, an event date 115b, a seat type 115c, a seat number ll5d, a p customer ID 115e, a reserved date 115f, and the like.

Further, as shown in Fig. 3B, the ticket reservation host may include a user information storage unit 117 that stores a mail address 117b of a user associating with a user ID 117a.

The information that is stored in the user information storage unit 117 may be member information of the ticket issue system 1. For example, the user ID 117a may be used as a login ID required at the time of using a ticket selling service site.

The ticket server 120 includes a communication unit 121, a ticket issue processing unit 125, a code creating unit 126, a ticket information storage unit 127, a group ID storage unit 128, and a verification data storage unit 129.

The communication unit 121 includes a reservation data receiving unit 122 that receives ticket reservation information from the ticket reservation host 110, a reception destination information receiving unit 123 that receives recipient information of the ticket transmitted from the reservation terminal 200, and a mail sending unit 124 that sends an electronic mail to the reservation terminal 200 or the user terminal 300 through the mail server 130. Further, the communication unit 121 includes a ticket information code receiving unit (not shown) that receives from the ticket verification terminal 400, a ticket information code, such as, for example, a QR code, which contains information for specifying a ticket to be issued (for example, a ticket issue

B

sequence number, verification data or the like) The ticket issue processing unit 125 receives the ticket information code from the ticket verification terminal 400, acquires information on plural tickets associated with the ticket information code from the ticket information storage unit 127, the group ID storage unit 128, and the verification data storage unit 129, and transmits it to the ticket verification terminal 400.

Further, the ticket issue processing unit 125 associates ticket link information received from the reservation terminal with the reservation data stored in the ticket information storage unit 127, and stores it in the group ID storage unit 128. The ticket link information is the information that associates the tickets to be simultaneously issued with one another. For example, the ticket link information is used by assigning the same ID (hereinafter, referred to as "group ID") to the associated tickets. Specifically, the same group ID can be assigned to the tickets whose recipients are the same.

In this case, it is considered that the same group IDis assigned to the tickets whose recipient information (for example, amail address, a telephone number or the like) is the same.

Furthermore, the ticket issue processing unit 125 creates verification data for verifying a ticket information code, associates the created verification data with the ticket link information, and stores it in the verification data storage unit 129. The ticket issue processing unit 125 performs a verifying process on the ticket information code downloaded by the user using the verification data. That is, the ticket issue processing unit 125 receives a ticket issue sequence number and verification data included in the ticket information code which the ticket verification terminal 400 reads from the user terminal 300, and compares the ticket issue sequence number and the verification data with the verification data stored in the verification data storage unit 129. On the basis of the comparison result, the ticket issue processing unit 125 determines whether the ticket is issued or not. When the ticket information code is verified, the ticket issue processing unit 125 transmits information on plural tickets associated with the verified ticket information code to the ticket verification terminal 400. Meanwhile, when the ticket information code is not verified, the ticket issue processing unit 125 transmits to the ticket verification terminal 400, information indicating that the ticket information code is not verified.

Further, the ticket issue processing unit 125 stores the reservation data received from the ticket reservation host 110 in the ticket information storage unit 127, and notifies the reservation terminal 200 of an URL on a ticket receiving destination information input page by sending a mail through the mail server 130. Furthermore, through the mail server 130, the ticket issue processing unit 125 notifies the user terminal 300 of a URL on a download page for the user to acquire the ticket information code. If the user accesses the download page through the user terminal 300, the ticket issue processing unit 125 notifies the user terminal 300 of ticket information code including a ticket issue sequence number, ve-ification data or the like.

The code creating unit 126 creates a ticket information code including information for specifying a ticket (for example, a ticket issue sequence number, verification data or the like) to be issued. If the user accesses the download page through the user terminal 300, the code creating unit 126 receives a request from the ticket issue processing unit 125, arid creates a ticket information code on the basis of information on one ticket among plural issued tickets.

The ticket information storage unit 127 stores the reservation data received from the ticket reservation host 110, and includes a memory, such as, for example, a RPM or a hard disk. Specifically, as shown in Fig. 4A, the ticket information storage unit 127 stores ticket reservation information that includes a ticket issue sequence number 127a, an event name l27b, an event date 127c, a seat type 127d, a seat number 127e or the like.

The group ID storage unit 128 stores ticket link information which makes the respective tickets link with the

U

respective distribution destinations on the basis of the ticket receiving destination information received from the reservation terminal 200, and includes a memory, such as, for example, a RAM or a hard disk. Specifically, as shown in Fig. 4B, thegrouplDstorageunit 128 stores ticket linkinforrnation that includes a ticket issue sequence number 128a, a customer ID 128b, a group ID 128c, and the like. The customer ID 128b may be an ID that corresponds to the user ID 117a that is stored in the user information storage unit 117 of the ticket reservation host 110.

The verification data storage unit 129 stores verification data for verifying the ticket information code, and includes a memory, such as, for example, a RAM or a hard disk. Specifically, as shown in Fig. 4C, theverificationdata storage unit 129 stores verification information that includes a ticket issue sequence number 129a, verification data 129b, and the like.

Although, in this embodiment, the ticket information storage unit 127, the group ID storage unit 128, and the verification data storage unit 129 have been described as individual tables, the invention is not limited thereto, and the information that is stored in the ticket information storage unit 127, the group ID storage unit 128, and the verification data storage unit 129 may be collectedly stored

in one table.

The reservation terminal 200 includes a communication unit 201, a reservation processing unit 203, an input unit 205, and a display unit 207. The communication unit 201 exchanges reservation data for reserving the ticket with the ticket reservation host 110, and transmits receiving destinations of plural reserved tickets to the ticket server 120. The reservation processing unit 203 performs a process to create reservation data that is transmitted to the ticket reservation host 110. The input unit 205 is provided for the purpose of inputting the reservation data, and an input unit, such as, for example, a keyboard or a mouse, may be used as the input unit 205. The display unit 207 is provided to display a communication result or the like with the ticket reservation host 110 or the ticket server 120.

The user terminal 300 has a structure that is substantially equal to the structure of the reservation terminal 200, and includes a communication unit 301, a code information processing unit 303, an input unit 305, and a display unit 307. In the user terminal 300, the communication unit 301 accesses the ticket server 120 to access the download page and downloads the ticket information code from the ticket server 120. In this way, the communication unit 301 performs a communication with the communication unit 121 of the ticket server 120. The code information processing unit 303 performs a process that accesses the ticket server 120, or a data process that displays the ticket information code acquired from the ticket server 120 on the display unit 307. The input unit 305 is provided, for example, to perform an input operation for accessing the download page. The display unit 307 is provided to display the ticket information code that is acquired from the ticket server 120.

Here, the reservation terminal 200 and the user terminal 300 may be the same. That is, the case where the user and the customer who reserves the ticket are the same or the case where the ticket is reserved and received by using the same terminal rnaybeconsidered. In this case, a terminalmayhavea function of the reservation terminal 200 and a function of the user terminal 300.

The ticket verification terminal 400 includes a communication unit 401, a code referral processing unit 403, a code read unit 405, a display unit 407, and an issue unit 409. The communication unit 401 transmits the information included in the ticket information code as inquiry information to the ticket server 120. The inquiry information, such as, for example, a ticket issue sequence number or verification data, may be used. The code referral processing unit 403 creates inquiry information inquiring to the ticket server 120 on the basis of the ticket information code read from the user terminal 300 by the code read unit 405. The code read unit 405reads the ticket information code that is displayed on the display unit 307 of the user terminal 300. The display unit 407 displays a method of using the ticket verification terminal 400, a process situation during a verification process or the like, a verification result from the ticket server 120, and the like. The issue unit 409 issues a ticket stub according to the verification result from the ticket server 120.

The respective devices that form the ticket issue system 1 according to this embodiment have been described. In the ticket issue system 1 according to this embodiment, plural tickets can be issued to one user by using the group ID that serves as ticket link information associating the plural tickets with one another.

Hereinafter, processes of ticket reservation, distribution, and verification in the ticket issue system 1 according to this embodiment will be described with reference to Figs. 5 to 8. Fig. 5 is a flowchart illustrating a schematic flow of a ticket reserving process according to the embodiment.

Fig. 6 is a flowchart illustrating a schematic flow of a ticket distributing process according to the embodiment. Fig. 7 is a flowchart illustrating a group ID and verification data creating sequence. Fig. 8 is a flowchart illustrating a schematic flow of a ticket verifying process according to the embodiment.

<1. Ticket Reserving Process> First, a ticket reserving process will be described with reference to Fig. 5. AsshowninFig. 5, acustomerwho reserves a ticket accesses the ticket reservation host 110 of the electronic ticket selling site 100 through the reservation terminal 200 (Step SlOl) . If a communication with the ticket reservation host 110 of the electronic ticket selling site 100 starts (Step 5103) , the customer creates ticket reservation application data by using the reservation terminal 200 (Step S105) The reservation application data includes customer information, such as a user ID, or information on an event, such as an event code, an event date, a seat type, the number of tickets, and a reserved date. When completing to create the reservation application data, the reservation terminal 200 transmits the application data to the ticket reservation host (Step S107) The ticket reservation host 110 that has received the ticket application data compares the application data and the reservation situation data stored in the reservation data storage unit 115 (Step S109), and determines whether the reservation is possible or not (Step Sill) . When it is determined that the reservation is possible, payment is made between the reservation terminal 200 and the ticket reservation host 110 (Step Sl13) . The payment is made by known methods using electronic money or a credit card. In this embodiment, the description is made on the case that even when plural tickets are reserved, the customer collectively makes payment. However, the invention is not limited to the above-described example, but plural persons may individually make payment.

If the payment iscornpletelymade, the ticket reservation host 110 performs an updating process on the reservation situation data that is stored in the reservation data storage unit 115 (Step S115) . Then, the ticket server 120 is notified of an electronic ticket issue request (Step S117) . When the ticket server 120 is notified of the electronic ticket issue request, the ticket server 120 is also notified of ticket reservation information including a mail address of a representative, the number of purchased tickets, event codes, information specifying a seat, and the like. When the ticket server 120 receives the electronic ticket issue request from the ticket reservation host 110 (Step S201), an electronic ticket distributing process starts.

Meanwhile, when it is determined in step Sill that the reservation is not possible, the ticket reservation host 110 notifies the reservation terminal 200 of a message indicating that the reservation is not possible (Step S119) . At this time, the ticket reservation host 110 transmits to the reservation terminal 200, a message inquiring whether the customer reserves a ticket again or not (Step S121) . When the customer selects to reserve a ticket again, processes staring from step S105 are performed again. When the customer selects not to reserve a ticket again, the reservation process is completed.

<2. Ticket Distributing Process> Next, a ticket distributing process of the reserved tickets will be described with reference to Fig. 6. The ticket server 120, which has received an electronic ticket issue request frornthe ticket reservationhost 110 instepS20l, sends a mail notifying a URL on a ticket distribution page to the reservation terminal 200 through the mail server 130 (Step 5203) . After the reservation terminal 200 receives the mail notifying the URL on the ticket distribution page from the ticket server 120 (Step S205), the reservation terminal 200 accesses the URL on the ticket distribution page so as to distribute the electronic tickets (Step S207) . At this time, since the ticket server 120 requests the customer to input a login password (Step S209), the customer inputs the login password (Step S2l1) . After the login password input by the user is verified by the ticket server 120 (Step S213), the customer can start a distribution sequence. Further, at the time of the login on the ticket distribution page, it may be possible to use a user ID or a password having been registered when the customer uses the ticket selling service site.

When the login password is verified, the ticket server confirms the number of tickets reserved by the customer on the basis of the reservation information having been acquired in step Sl17 (Step S215) . In the ticket issue system 1 according to this embodiment, when the number of reserved tickets is two or more, the ticket distributing process can be performed, and when the number of reserved ticket is one, the process proceeds to a ticket issue process. when the numberof tickets istwoormore, theticketserverl2oinquires the reservation terminal 200 of whether or not the tickets are distributed or issued (Step S217) . If the customer determines whether or not to distribute the tickets, the determined contents are transmitted to the ticket server 120 (Step S219) and the processes in the ticket server 120 and the reservation terminal 200 are determined according to the determined contents (Steps S223 and S221) When the customer selects the ticket distribution, the ticket server 120 requests the reservation terminal 200 to input mail addresses of distribution destinations to which the tickets are distributed (Step S225) . If the reservation terminal 200 receives the input request from the ticket server 120, a screen for inputting the mail addresses of the distribution destinations (reception destination input screen 211) is displayed on the display unit 207. For example, as shown in Fig. 9, in the reception destination input screen 211, a mail address input column 213 for inputting a mail address is provided for each of the tickets having been reserved by the customer. The customer inputs mail addresses of recipients of tickets, presses a decision button 215 that is provided on the reception destination input screen 211, and transmits the mail addresses of the recipients to the ticket server 120 (Step S227) The ticket server 120 that has received the mail addresses of the recipients performs a process that requests the customer to confirm the mail addresses of the ticket receiving destinations (Step S229) . For example, a confirmation screen 221 shown in Fig. 10 is displayed on the display unit 207 of the reservation terminal 200. The confirmation screen 221 is displayed in a non-active state such that the mail addresses having been input through the reception destination input screen 211 cannot be changed (see reference numeral 223) . Then, as the result of confirmation, when the customer determines that there is no error in the input contents, the customer presses a Yes' button 225 on the confirmation screen 221 and performs a ticket distributing process (Step S233) At this time, the ticket server 120 uses the information indicating the ticket receiving destinations having been input through the reservation terminal 200 as ticket link information, and associates it with the ticket information to store in the ticket information storage unit 127.

Specifically, the ticket server 120 assigns the same group ID to the tickets whose recipients, mail addresses having been input through the reservation terminal 200 are the same (Step 5233a in Fig. 7) For example, as shown in Fig. 10, assume that the customer reserves six tickets and three persons are going to receive two tickets, respectively. As shown in Fig. 4A, ticket issue sequence numbers l27a are sequentially assigned to the six tickets that have been reserved by the customer. If the ticket distributing process is performed in step S233, the ticket issue processing unit 125 of the ticket server 120 assigns the same group ID to the tickets whose recipients, mail addresses are the same. In Fig. 10, the first and second tickets are received by the same recipient, the third and fourth tickets are received by the same recipient, and the fifth and sixth tickets are received by the same recipient. Therefore, as shown in Fig. 4B, by the ticket issue processing unit 125, a group ID 1' is assigned to ticket issue sequence numbers 001' and 002', a group ID 2' is assigned to ticket issue sequence numbers 003' and 004', and a group ID 3' is assigned to ticket issue sequence numbers 005' and 006'. Further, the group ID 128c is stored in the group ID storage unit 128 so as to be associated with the ticket issue sequence number 128a.

If the group IDs are respectively assigned to the corresponding ticket issue sequence numbers, on the basis of ticket data having a smallest ticket issue sequence number among the ticket issue sequence numbers in the same group ID (data of gray portions in Fig. 4A), the ticket server 120

I

creates verification data (Step S233b in Fig. 7) . At this time, the verification data is used in a verification process performed when the ticket is issued and is created for each ticket. For example, in Fig. 4B, if viewing the tickets each having the group ID 1', the ticket data having a smallest ticket issue sequence number is ticket data that has a ticket issue sequence number of 001'. Accordingly, the verification data having the ticket issue sequence numbers 001' and 002' are created on the basis of the ticket data having the ticket issue sequence number 001'.

Similarly, the verification data having the ticket issue sequence numbers 003' and 004' is created on the basis of the ticket data having the ticket issue sequence number 003', and the verification data having the ticket issue sequence numbers 005' and 006' is created on the basis of the ticket data having the ticket issue sequence number 005'. The verification data thus created is assigned to the ticket issue sequence number 129b, as shown in Fig. 4C. As such, the same group ID is assigned to the tickets whose recipients are the same, which classifies the tickets to be issued to the respective recipients.

Meanwhile, when the input contents need to be corrected due to errors, or the like, the customer presses a No' button 227 on the confirming screen 221 so as to stop the ticket distributing process, and processes starting from step S227

V

are performed again.

If the ticket distributing process is completed by the ticket server 120 in step S233, the ticket server 120 transmits to the user terminal 300 being a ticket distribution destination, a mail notifying a URL on a page for downloading QR code serving as ticket information code, through the mail server 130 (Step S235) . Vhen the user terminal 300 receives the mail notifying the URL on the page for downloading the QR code (Step S237), an electronic ticket verifying process can be performed.

Here, a broken line that is shown toward the reservation terminal 200 from step S235 shown in Fig. 6 indicates a flow of information in the case that the reservation terminal 200 becomes the user terminal 300. In this case, the mail notifying the URL on the page for downloading the QR code is also sent to the reservation terminal 200. After sending the mail notifying the URL on the page for downloading the QR code serving as the connection destination information, the ticket server 120 sends to the reservation terminal 200, a mail including a message that the ticket distributing process is completed, through the mail server 130 (Step S239) <3. Ticket Verifying process> Next, a ticket verifying process will be described with reference to Fig. 8. The user terminal 300, which has received the mail notifying the URL on the page for downloading the QR t code in step S237, accesses the URL on the page for downloading the QR code of the ticket server 120 so as to download the QR code (Step S301) . In response to the access, the ticket server allows the code creating unit 126 to create the QR code (Step S303), and transmits the created QR code to the user terminal 300 (Step S305) In this case, the QR code that is created in step S303 is created on the basis of data of a ticket having a smallest ticket issue sequence number among the plural tickets each having the same group ID. For example, if the user terminal 300 that has received the tickets having the ticket issue sequence numbers 001' and 002' accesses the ticket server 120, the ticket server 120 allows the code creating unit 126 to create the QR code on the basis of the data of the ticket having the ticket issue sequence number 001'. That is, the QR code that is displayed on the user terminal 300 is created on the basis of information on one ticket, and even when plural tickets are issued, the QR code including ticket information on the plural tickets is not created. The user terminal 300 receives the QR code created in the above-described method, and displays the created QR code on the display unit 307 of the user terminal 300 (Step S307) If the recipient of the ticket whose QR code is displayed on the display unit 307 of the user terminal 300 holds the user terminal 300 over the code read unit 405 of the ticket verification terminal 400, the code read unit 405 of the ticket verification terminal 400 reads the QR code (Step S309) . The ticket verification terminal 400 that has read the QR code transmits a ticket verification request message to the ticket serverl20bythecodereferralprocessingunit4o3 (StepS3ll).

At this time, the ticket issue sequence number and the verification data that have been read from the QR code are transmitted to the ticket server 120. After receiving the ticket verification request, the ticket server 120 starts a ticket verifying process (Step S313) According to the ticket verifying process, first, the ticket issue processing unit 125 compares the verification data transmitted from the ticket verification terminal 400 and the verification data 129b stored in the verification data storage unit 129 so as to be associated with the ticket issue sequence number 129a. As the result of the comparison in the ticket server 120 (Step S315) , when the verification data that is transmitted from the ticket verification terminal 400 is equal to the verification data stored in the verification data storage unit 129, the ticket server 120 searches tickets having the same group ID as the verified tickets from the group ID storage unit 128 (Step S317) For example, assume that the recipients of the tickets having the ticket issue sequence numbers 001' and 002' display the QR code on the display units of the respective user terminals 300 and hold the respective user terminals 300 over the code read unit 405 of the ticket verification terminal 400.

In this case, the QR code that is displayed on the user terminal 300 is the code that is created on the basis of the information on the ticket having the ticket issue sequence number 001'.

The ticket issue sequence number and the verification data read from the QR code is transmitted to the ticket server 120 and, when determined to be equal to the verification data stored in the verification data storage unit 129, the group ID, which is stored so as to be associated with the ticket issue sequence number, is acquired from the group ID storage unit 128.

As shown in Fig. 4B, the group ID having the ticket issue sequence number of 001' is 1' . When acquiring the group ID of the verified ticket, the ticket issue processing unit 125 searches the ticket issue sequence numbers having the group ID of 1' from the group ID storage unit 128. As such, the ticket that is issued together with the ticket having the ticket issue sequence number 001' is searched. In this case, the ticket having the ticket issue sequence number 002' to which the group ID 1' is assigned is to be issued. Accordingly, two tickets having the ticket issue sequence numbers 001' and 002' are to be issued.

If the tickets to be issued are determined, the ticket information (for example, a ticket issue sequence number, an event name, an event date, a seat type, a seat number, and the like), which is associated with the ticket issue sequence number of the determined ticket, is acquired from the ticket information storage unit 127, and is transmitted to the ticket verification terminal 400 (Step S319) The ticket verification terminal 400 determines the ticket information transmitted from the ticket server 120 (Step S321), and when the transmitted ticket information is verified, for example, an entrance gate is opened, or a process is performed for issuing a ticket stub by the issue unit 409 (Step S323) Meanwhile, when the ticket information transmitted from the ticket server 120 is not verified, the ticket server 120 notifies the recipient of the information indicating that the ticket cannot be issued, through the display unit 407 of the ticket verification terminal 400 (Step S325) Until now, processes of the ticket reservation, distribution, and verification according to the embodiment of the invention have been described. In the ticket issue system 1 according to this embodiment, it becomes possible to issue plural tickets on the basis of ticket information code having information on one ticket. Therefore, it is possible to realize electronic tickets that correspond to plural paper tickets that are collected. Further, since the electronic tickets can be distributed to the people other than the customer, the recipients who have received the ticket information code can independently enter an even site.

Although the preferred embodiment of the present invention has been described with reference to the accompanying drawings, it is needles to say that the invention is not limited to a specific example. It will be apparent to those skilled in the art that various modifications and changes may be made without departing from the scope of the claims, and all changes and modifications fall within a technical range of the invention.

For example, in the above-described embodiment, the verifying process on the ticket information code has been performed by the ticket issue processing unit 125 of the ticket server 120. However, the invention is not limited thereto, but the verifying process on the ticket information code may be performed, for example, by the ticket verification terminal 400.

Further, in the above-described embodiment, when the number of reserved tickets is two or more, an access to the ticket distribution page becomes possible, and the mail addresses of the recipients of the tickets can be input.

However, the invention is not limited thereto. For example, it may be possible to input the mail addresses of the recipients of the tickets regardless of the number of reserved tickets.

Furthermore, in the above-described embodiment, the ticket information code is the two-dimensional code, but the invention is not limited thereto. For example, the ticket information code may be a bar code.

The invention can be applied to a ticket issue system.

In particular, the invention can be applied to a ticket issue system using an electronic ticket.

Claims

WHAT IS CLAIMED IS: 1. A ticket issue system, comprising: a ticket

server that issues reserved tickets; one or more user terminals that receive the tickets; and a ticket verification terminal that verifies the tickets, wherein the ticket server comprises: a ticket information storage unit that stores an item of ticket link information so as to be associated with information on the plural reserved tickets; a code creation unit that creates a ticket information code including the ticket link information; and a ticket issue processing unit that receives the ticket information code from the ticket verification terminal, and transmits the information on the plural tickets associated with the ticket information code to the ticket verification terminal, each of the user terminals comprises a code receiving unit that receives the ticket information code from the ticket server, and the ticket verification terminal comprises a code referral processing unit that checks the ticket information code received from the user terminal with the ticket server and receives the information on the tickets.

2. The ticket issue system according to claim 1, further comprising: a reservation terminal that reserves the tickets; and a ticket reservation host that performs a ticket reservation process on the basis of reservation data transmitted from the reservation terminal, wherein the ticket reservation host comprises a reservation data transmission unit that transmits, to the ticket server, the reservation data on the basis of which the reservation process is completed, and notifies the ticket server of a ticket issue request, and the ticket issue processing unit of the ticket server stores the reservation data received from the ticket reservation host in the ticket information storage unit, and notifies the reservation terminal of information indicating a destination for connection to the ticket server.

3. The ticket issue system according to claim 2, wherein the reservation terminal comprises a ticket link information transmission unit that transmits the ticket link information to the ticket server based on reception destinations of the reserved tickets, and the ticket issue processing unit of the ticket server stores the ticket link information received from the reservation terminal so as to be associated with the reservation data stored in the ticket information storage unit.

LI. The ticket issue system according to any one of claims 1 to 3, wherein the ticket issue processing unit of the ticket server creates verification data for verifying the ticket information code, and stores the created verification data in the ticket information storage unit so as to be associated with the ticket link information.

5. The ticket issue system according to claim 4, wherein the ticket issue processing unit of the ticket server communicates the ticket information code comprising the verification data in response to a request from the user terminals.

6. The ticket issue system according to any one of claims 1 to 5, wherein the ticket issue processing unit of the ticket server notifies the user terminals of connection destination information for acquiring the ticket information code.

7. The ticket issue system according to any one of claims 4 to 6, wherein the ticket issue processing unit of the ticket server compares the ticket information code received from the ticket verification terminal and verification data stored in the ticket information storage unit, and determines whether the tickets are to be issued or not on the basis of the comparison result.

8. The ticket issue system according to claim 7, wherein, when the ticket information code received from the ticket verification terminal is verified, the ticket issue processing unit of the ticket server transmits the information on the plural tickets associated with the verified ticket information code to the ticket verification terminal.

9. A ticket server that issues reserved tickets, comprising: a ticket information storage unit that stores an item of ticket link information so as to be associated with information on the plural reserved tickets; a code creation unit that creates a ticket information code comprising the ticket link information; and a ticket issue processing unit that issues information on the plural tickets associated with the ticket information code.

10. The ticket server according to claim 9, wherein the ticket issue processing unit stores the item of ticket link information so as to be associated with the information on the plural tickets stored in the ticket information storage unit, on the basis of information indicating reception destinations of the tickets.

11. The ticket server according to claim 9 or 10, wherein the ticket issue processing unit creates verification data for verifying the ticket information code, and stores the created verification data in the ticket information storage unit so as to be associated with the ticket link information.

12. The ticket server according to claim 11, wherein the ticket issue processing unit compares the ticket information code transmitted to the ticket server and the verification data stored in the ticket information storage unit, and determines whether the tickets are to be issued or not on the basis of the comparison result.

13. The ticket server according to claim 12, wherein, when the ticket information code is verified, the ticket issue processing unit issues the information on the plural tickets associated with the verified ticket information code.