JP2023159643A - electronic ticket system - Google Patents

Abstract

To provide a system that can easily and reliably check legitimacy of a person holding an electronic ticket.SOLUTION: An electronic ticket system 10 is equipped with a server connected to a smartphone 22 of a user, in which the server includes: a user DB 42 where a face photos of the user is registered; an event DB 44 where event information is registered; a ticket DB 46 where an event ID related to an electronic ticket obtained by the user is registered; and means for transmitting the electronic ticket 60 to the smartphone 22. The electronic ticket 60 includes the face photo of the user 51, an event name 62, and an availability display band 64. The server transmits, when the user reads a two-dimensional code provided at an event site, a check-in screen 66 with an admission confirmation button 67 to the smartphone 22, and transmits, when the admission confirmation button 67 is touched by a staff at the event site, a used electronic ticket 68 with a used display band 69 displayed to the smartphone 22.SELECTED DRAWING: Figure 1

Description

Application for application of Article 30, Paragraph 2 of the Patent Act Published on the website (https://gicz.tokyo/p) on December 22, 2021

The present invention relates to an electronic ticket system, and in particular to a technology that allows anyone to freely plan an event and distribute event participation tickets to general users without having to build their own system.

With the spread of the Internet and smartphones (hereinafter referred to as "smartphones"), tickets for participation in events such as concerts and sports tournaments are shifting from traditional paper tickets to electronic tickets (see the following non-patent literature). 1 and 2).
Comparison of 8 electronic ticket system/apps! How to create a digital ticket (Internet URL: http://blog.500mails.com/online-ticket-system-comparison/ Search date: March 14, 2022) What is an electronic ticket? Types, advantages and disadvantages Internet URL: https://www.ic-net.co.jp/media/ticket_sales/a12 Search date: March 14, 2022

By using these existing electronic ticket services, event organizers can plan and announce various events with relatively little effort, and can issue participation tickets to general users at low cost.
In addition, on the day of the event, it is necessary to confirm the presence and validity of participation tickets before allowing users to enter the venue, but this is also done by scanning the barcode or 2D code displayed on the user's smartphone screen. This eliminates the need for staff to manually tear up tickets and hand over stubs to users, as was the case in the past. In addition, there is an advantage that status management of admission/non-entry can be performed on a user-by-user basis.
Users also have the advantage of being able to obtain tickets immediately via a device such as a smartphone without having to wait for paper tickets to be mailed, and there is no risk of them being lost.

In this way, there is no doubt that there are many benefits to both event organizers and users by using electronic ticketing services, but unlike the existing system, barcodes displayed on smartphone screens are The conventional method of checking admission by reading tickets, etc., had the problem that it was difficult to detect fraud such as ticket resale or counterfeiting.
The present invention was devised in view of the current situation, and aims to realize a system that can easily and reliably check the legitimacy of a person holding an electronic ticket.

In order to achieve the above object, the electronic ticket system according to claim 1 is an electronic ticket system comprising a server connected to each user terminal owned by a plurality of users via a network, the electronic ticket system comprising: is a storage means for registering image data of each user's face photograph in association with a user ID, an event storage means for registering information regarding multiple events in association with an event ID, and an electronic storage means acquired by the user. It is equipped with a ticket storage means for registering the event ID related to the ticket in association with the user ID, and a means for transmitting the electronic ticket obtained by the user to the user terminal, and the electronic ticket displayed on the display of the user terminal is contains the user's face photo, the event name, and an availability display indicating that the electronic ticket is available for use, and the user connects to the server via the user terminal and goes to the event venue. When the installed code (two-dimensional code or barcode) is read with the camera of the user terminal, the above server identifies the event based on the event ID included in the code and identifies the user as the ticket holder for that event. It is confirmed whether the ticket is registered in the ticket storage means, and if the person is the ticket holder, a check-in screen with an entry confirmation button is sent to the user terminal, and the face photo on the electronic ticket and the user's face are sent to the user terminal. When the above admission confirmation button is touched by the staff at the event venue who has confirmed that the person is the same person by comparing the numbers, a used indication will be displayed on the electronic ticket indicating that the electronic ticket has been used. It is characterized by

The electronic ticket system according to claim 2 is the system according to claim 1, wherein the event storage means records the number of times the coupon type electronic ticket can be used, and the user can use the ticket type electronic ticket through the user terminal. When connected to the above server and read the code installed at the event venue with the camera of the user terminal, the above server identifies the event based on the event ID included in the code, and also identifies the user as the ticket holder for that event. The user checks whether the ticket is registered in the ticket storage means and whether there are any remaining number of uses. A check-in screen with a confirmation button is sent to the user terminal, and when the entry confirmation button is touched by the staff at the event venue, the server stores information indicating the fact of use (date and time of use, number of uses, etc.) of the ticket. In addition to the means, if the user is the acquirer of the ticket and there is no remaining number of uses, a used indication indicating that the electronic ticket has been used will be displayed on the electronic ticket. It is characterized by

The electronic ticket system according to claim 3 is an electronic ticket system that includes a server that is connected to each user terminal owned by a plurality of users via a network, and the server is configured to register each user in association with a user ID. a storage means for registering image data of a face photograph of a user; an event storage means for registering information regarding multiple events in association with an event ID; and an event storage means for registering information regarding multiple events in association with an event ID; It is equipped with a ticket storage means to associate and register tickets, and a means to send an electronic participation certificate to the user terminal, and the electronic participation certificate displayed on the display of the user terminal contains the user's face photo and A list of unused electronic tickets is included, and when a user selects to use an electronic ticket corresponding to the event from the list at the event venue, the server displays a check-in screen with an admission confirmation button to the user. When the entry confirmation button is touched by the staff at the event venue who has confirmed that the person is the same person by comparing the face photo on the electronic participation certificate and the user's face, the electronic ticket is confirmed to have been used. The feature is that a used indication is displayed on the electronic participation card to indicate that it has been used.

The electronic ticket system according to claim 4 is the system according to claim 3, wherein the event storage means records the number of times the coupon type electronic ticket can be used, and the unused electronic tickets in the list are recorded. The ticket includes a coupon-type electronic ticket that has a remaining number of uses, and when the user selects to use a coupon-type electronic ticket from the above list, the above server sends a check mark with an admission confirmation button. When the entry confirmation button is touched by the staff at the event venue who has confirmed that the user's face is the same person by sending the login screen to the user terminal and comparing the face photo on the electronic participation card with the user's face, the server will be used. If the information indicating the fact of the above is added to the ticket storage means and there are no more number of uses remaining, a used indication indicating that the ticket-type electronic ticket has been used will be displayed on the electronic participation certificate. It is characterized by

The electronic ticket system according to claim 5 is the system according to claim 1 or 3, wherein a plurality of seat numbers related to an event are registered in the event storage means, and the server is configured to receive information from the user terminal. When a request to obtain a ticket is sent, the above-mentioned ticket storage means is referred to, the seat numbers for which the issued flag is not set are extracted, the list is sent to the user terminal, and the user terminal retrieves the seat numbers from the above list. When a request to acquire a specific seat number is sent and, in the case of a fee, the necessary payment processing is completed, an issued flag is set for the seat number in the ticket storage means. It is characterized by

The electronic ticket system according to claim 6 is the system according to claim 1 or 3, wherein the total number of tickets for the event and the application period are registered in the event storage means, and the server is configured to control the electronic ticket system from the user terminal. If a request to obtain a ticket is sent within the application period, the user will be provisionally registered as an applicant in the ticket storage means, and at a predetermined timing, the total number of tickets will be collected from among the applicants stored in the ticket storage means. The system is characterized by randomly extracting winners and sending notification of winning to each winner's user terminal.

In the case of the electronic ticket system according to claim 1, a user can display an electronic ticket for the event on a user terminal such as a smartphone by simply reading a two-dimensional code or barcode installed at the event venue.
Moreover, since the e-ticket displays the user's face photo, event venue staff can easily and reliably confirm that the e-ticket holder is the legitimate ticket purchaser, preventing fraudulent impersonation. can be easily eliminated.
Additionally, when a staff member touches the admission confirmation button on the check-in screen, an electronic ticket with a used indication engraved on it will be displayed on the user terminal, effectively preventing unauthorized reuse. becomes possible.

In the case of the electronic ticket system according to claim 3, an electronic participation certificate containing a list of unused electronic tickets acquired by the user is displayed on the user terminal such as a smartphone, and the electronic participation certificate includes the user's face. Because the photo is displayed, event venue staff can easily and reliably confirm that the holder of the e-ticket in question is the legitimate purchaser of the e-ticket listed, easily eliminating fraudulent impersonation. It becomes possible.
In addition, when a staff member touches the admission confirmation button on the check-in screen, the corresponding electronic ticket will be displayed on the electronic participation card with a “used” indication engraved from then on, resulting in unauthorized reuse. can be effectively prevented.

1 is a block diagram showing the overall configuration of an electronic ticket system according to the present invention. It is a figure showing an example of table composition of user DB. FIG. 2 is a screen configuration diagram showing an example of a GIC passport. It is a figure showing an example of table composition of event DB. It is a figure showing an example of table composition of ticket DB. It is a flowchart which shows the processing procedure concerning acquisition of an electronic ticket. It is a figure showing an example of a screen composition concerning acquisition of an electronic ticket. It is a figure showing an example of a screen composition concerning acquisition of an electronic ticket. A diagram showing an example of the screen configuration of an electronic ticket and an example of screen transitions when used. It is a flowchart showing a processing procedure related to the use of an electronic ticket. It is a figure which shows the screen structure example and transition example in the case of using an electronic ticket as a coupon ticket. FIG. 2 is a diagram showing an example of a screen configuration when specifying a seat using this electronic ticket system. It is a figure showing an example of a screen composition when a lottery is performed with this electronic ticket system. It is a figure which shows the example of a screen structure in other embodiments of an electronic ticket, and the example of a transition of a screen accompanying use. It is a figure which shows the example of a screen structure in other embodiments of an electronic ticket, and the example of a transition of a screen accompanying use.

FIG. 1 is a block diagram showing a configuration example of an electronic ticket system 10 according to the present invention, which includes a Web server 14, an AP (Application) server 16, a DB (Database ) has 18 servers.
The web server 14 is connected via the Internet 20 to user terminals such as smartphones 22 and PCs 24 owned by a large number of users α, and user terminals such as smartphones 22 and PCs 24 owned by multiple organizers β. .
However, the hardware configuration of the present invention is not limited to the above, and for example, a server that integrates the functions of the Web server 14, AP server 16, and DB server 18 may also be used.
Both the user α and the organizer β refer to users of the system 10, and in the case of hosting an event, the user is the organizer β, and in the case of participating in the event, the user α is the user.

The AP server 16 includes a user management section 30, an event generation section 32, a ticket processing section 34, and a payment processing section 36.
These user management section 30, event generation section 32, ticket processing section 34, and payment processing section 36 are functional components realized by the CPU of the AP server 16 operating according to the OS and a dedicated application program.
The payment processing unit 36 is connected to a plurality of payment servers 38 via a communication network. Each payment server 38 is managed by a financial institution such as a credit card company, an electronic payment service company, or a bank.

The DB server 18 includes a DB management unit 40, and executes processing such as storing and extracting necessary data in response to requests from the AP server 16.
This DB management unit 40 is realized by the CPU of the DB server 18 operating in accordance with the OS and general-purpose database software.
In the storage device of the DB server 18, a user DB 42, an event DB 44, a ticket DB 46, and an image storage section 48 are provided.

As shown in FIG. 2, the user DB 42 stores records including data items such as "user ID,""emailaddress,""name,""face photo image," and "registration date and time."
When using this system 10, it is essential that the users (user α and organizer β) complete user registration in advance or at the time of use.

In other words, although not shown, when a user accesses the web server 14 via a smartphone 22, PC 24, etc. and enters an email address and name (full name or nickname) according to a predetermined form, the user management section 30 of the AP server 16 and is registered in the user DB 42 via the DB management unit 40 of the DB server 18.

Since this user registration requires the provision of a facial photograph, the user uploads an image file of his/her facial photograph to the web server 14 by taking a selfie using the camera of the smartphone 22, or the like.
The image file of this face photo is stored in the image storage unit 48 via the user management unit 30 and the DB management unit 40, and its location information is registered in the “face photo image” data item of the user DB 42.
Incidentally, at the time of user registration, a unique 16-digit user ID (Zic Z member number) is automatically assigned by the user management section 30 and registered in the user DB 42.

When a user who has completed user registration accesses the web server 14 from the smartphone 22, a passport screen 50 is displayed on the display of the smartphone 22, as shown in FIG.
This passport screen 50 displays the user's face photo 51 and ZIC Z membership number (user ID) 52.
The user who has acquired this passport will be able to participate in his/her favorite events as the user α or plan the event as the organizer β.

When planning a new event, the organizer β logs into the web server 14 via the smartphone 22 or PC 24 and enters the necessary information in a prescribed form (not shown), and the event generation unit 32 and DB management unit 40 create an event. Event information is registered in DB44.

FIG. 4 shows an example of records stored in the event DB 44, including "event ID", "user ID" of organizer β, "organizer information", "event name", "event category", and "event content". ”, “Event date and time”, “Event location”, “Event URL”, “Flyer image”, “Ticket name”, “Ticket price”, “Total number of tickets”, “Number of tickets that can be obtained at one time”, “Usage Data items such as "Sales start date and time", "Sales end date and time", "Person who pays commission", "Sales proceeds transfer account", and "Updated date and time" are provided.

Here, "user information" refers to information that event organizer β wants to obtain from user α, such as name, gender, age, region of residence, etc., and refers to the information that user α is required to input when obtaining a ticket. (Details will be explained later).

FIG. 5 shows an example of records stored in the ticket DB 46, including "event ID", "ticket ID", "ticket price", "user ID" of user α, "email address", Data items such as "user information", "sale date and time", "payment method (payment type)", "payment date and time", and "usage date and time" are provided at the time of acquisition.

Below, the processing procedure when user α acquires an electronic ticket will be explained according to the flowchart of FIG. 6.
First, user α accesses the dedicated site from the smartphone 22, enters the email address and user ID, logs in to the web server 14, and selects the option to obtain tickets from the menu (S10). ) is transmitted (S12).

When the user enters a search keyword (for example, "marathon") on this screen (S14), a search result screen is transmitted from the Web server 14 (S16).
FIG. 7 shows the search results displayed on the same screen, and a plurality of tickets related to the marathon are listed.
In response, the user checks the ticket name of each ticket, checks the selection column of the required ticket, inputs the number of tickets to be acquired, and then touches the order button 54 (S18).

As a result, as shown in FIG. 8(a), a user information input screen 56 is transmitted from the web server 14 to the smartphone 22 (S20).
On this screen 56, the user's name (or nickname) and email address are set as mandatory conditions for acquiring a ticket, and input of gender and prefecture are set as optional conditions.
However, this is just an example, and the organizer β can also set different information as “user information” when registering event information.

When the user α inputs user information and touches the send button 57 (S22), the payment method selection screen 58 is sent from the web server 14 to the smartphone 22 (S24), as shown in FIG. 8(b). .
When the user checks a specific payment method (for example, "credit card") on this screen 58 and touches the selection button 59 (S26), a payment information input screen (not shown) is sent from the web server 14. (S28).

In response, when the user inputs the credit number, expiration date (year/month), security code, etc. (S30), the payment processing section 36 of the AP server 16 executes payment processing (S32). That is, the payment processing unit 36 transmits payment information to the corresponding payment server 38 and requests payment of the ticket price.
When the payment is completed, ticket information is newly generated by the ticket processing unit 34 and registered in the ticket DB 46 by the DB management unit 40 (S34).
At a later date, all ticket prices will be transferred to the organizer β's bank account.

Note that if the ticket is free (ticket price = 0 yen), steps S24 to S32 are omitted, and registration of the ticket information is executed immediately after the user α inputs the user information.

Thereafter, the electronic ticket is sent from the web server 14 to the smartphone 22 of the user α (S36) and displayed on the display of the smartphone 22 (S38).
FIG. 9(a) shows an example of an electronic ticket 60, which includes user α's face photo 51, ticket name 61, event organizer name 62, ZIC Z member number (user ID) 52, user Name 63 etc. are displayed.
In the area where the ticket name 61 is displayed, a blue band indicating "unused", that is, a usable display band 64 is arranged in the background. However, the color of the available display band 64 is not limited to blue. Furthermore, it is also possible to use something other than a band with a specific color to indicate the availability of the electronic ticket.

Next, according to the flowchart of FIG. 10, the processing procedure when user α uses the electronic ticket will be explained.
That is, when user α visits the event venue on the day of the event, logs in to the web server 14 using the browser on the smartphone 22, and requests transmission of a specific electronic ticket (S50), the corresponding electronic ticket is sent from the web server 14. (S52), and the electronic ticket 60 shown in FIG. 9(a) is displayed on the display of the smartphone 22 (S54).
User α presents this electronic ticket 60 to the staff at the event venue.
At this time, the staff confirms that the face photo 51 of the electronic ticket 60 matches the face of the user α and that a blue band (availability display band 64) is displayed.
Next, as shown in FIG. 9(b), when the user α reads a two-dimensional code 65 such as a QR code (registered trademark) or a barcode installed at the reception of the event venue with the camera of the smartphone 22 (S56 ), a check-in screen for the event is transmitted from the web server 14 (S58), and a check-in screen 66 is displayed on the display of the smartphone 22, as shown in FIG. 9(c) (S60).

That is, since the two-dimensional code 65 includes an event ID, the ticket processing unit 34 identifies the event based on this event ID, and also refers to the ticket DB 46 to identify the user as the person who acquired the ticket for the event. After confirming that person α exists, a check-in screen 66 is generated and sent to the smartphone 22.
Incidentally, if user α is not registered in the ticket DB 46 as the person who acquired the ticket, the ticket processing unit 34 will send an error message such as "Unavailable because it has not been acquired" to the smartphone instead of sending the check-in screen 66. Return to 22.

This check-in screen 66 displays, in addition to the name of the event, an admission confirmation button 67 that should be touched by the staff at the event venue.
User α presents this check-in screen 66 to the staff.
In response, the staff touches the admission confirmation button 67 with a touch pen or finger (S62).

As a result, the ticket processing unit 34 records the usage date and time in the corresponding record of the ticket DB 46 (S64), and as shown in FIG. 9(d), the used electronic ticket 68 is transmitted from the web server 14 to the smartphone 22 ( S66) and displayed on the display (S68).

In this used electronic ticket 68, the background of the area displaying the ticket name 61 is replaced with a red used display band 69 indicating "used". However, the color of the used display band 69 is not limited to red. Furthermore, it is also possible to use something other than a band with a specific color to indicate that the electronic ticket has been used.
After that, even if user α logs in to the web server 14 again, the used electronic ticket 68 with the red used display band 69 will always be displayed on the smartphone 22, preventing unauthorized reuse of the same ticket. is prevented.
On the other hand, inside the event venue, possession of a used electronic ticket 68 with a red used display band 69 serves as proof that the official admission procedure (check-in) has been completed.

As mentioned above, the venue staff visually examines the face photo 51 displayed on the electronic ticket 60 and the face of the visitor α, determines that they are the same person, and then touches the admission confirmation button 67 on the check-in screen 66. Since the system allows entry to the venue through the use of tickets, it is possible to verify identity extremely easily and accurately, and it is possible to reliably exclude those who have obtained tickets through illegal resale or theft from entering the venue.
Note that if the face photo 51 on the electronic ticket 60 does not match the face of the user α, the staff will naturally refuse to participate in the event, and the two-dimensional code 65 will not be read, therefore the check-in screen 66 display is also not permitted.

Using this electronic ticket system 10, it is also possible to issue not only one-time tickets but also electronic tickets (electronic coupon tickets) that can be used repeatedly a predetermined number of times.
FIG. 11(a) shows a 12-ticket electronic ticket 70a issued by a certain massage parlor. Similar to the general electronic ticket 60 described above, the user's face photo 51 and the ticket name ( Ticket name) 61, organizer name (issuer name) 62, Zic Z member number (user ID) 52, name 63, etc. are displayed.
In the area where the ticket name 61 is displayed, a blue availability display band 64 is placed in the background.
Also, "Number of users/total number" is displayed, such as "0/12". In this case, since it is currently unused, it is expressed that it can be used 12 more times, that is, the number of remaining uses is 12.

When user α visits the store that is the event venue and presents the coupon-type electronic ticket 70a shown in FIG. Check that the band (availability display band 64) is displayed.
Next, when user α reads the two-dimensional code installed at the reception desk of the store with the camera of the smartphone 22, a check-in screen for the store is automatically sent from the web server 14 and displayed on the display of the smartphone 22. (not shown).
On the other hand, when the store staff touches the admission confirmation button on the check-in screen, the ticket processing unit 34 records the usage date and time in the corresponding record of the ticket DB 46, and as shown in FIG. The used screen 70b is sent from the web server 14 to the smartphone 22 and displayed on the display.
In this case, the blue availability display band 64 is still placed in the background of the part where the ticket name 61 is displayed, but the "number of uses/total number" is "1/12" (remaining number of uses: 12 - 1 = 11) has been updated as follows.

When user α uses up all the coupons, as shown in FIG. 11(c), the “number of uses/total number” of the coupon-type electronic ticket 70c is “12/12 (= remaining number of uses: 0 )" and the background of the part displaying the ticket name 61 is replaced with a red used display band 69.

When issuing this coupon-type electronic ticket 70, the organizer β specifies the issuance of a "coupon-type electronic ticket" at the time of event planning, and also sets the number of times it can be used.
This number of available uses is recorded in the event DB 44 and ticket DB 46.
Furthermore, each time the user α uses a coupon ticket, the ticket processing unit 34 registers information such as the date and time of use in the ticket DB 46, thereby managing the usage status (remaining number of tickets used) of the coupon ticket.

This electronic ticket system 10 can also be used to issue seat-assigned electronic tickets.
In this case, user α narrows down the desired seats in advance.
That is, user α accesses organizer β's homepage using smartphone 22 or PC 24 and requests seat display for a concert, etc., and as shown in FIG. '', a detailed seating chart 82 showing the individual seat numbers and positions included in the group of E seats is expanded.
By viewing this detailed seating chart 82, the user α can get an idea of the seat he/she desires.

Next, user α accesses the web server 14 from the smartphone 22 and inquires about the availability of the corresponding electronic ticket.
As a result, the vacant seat list 83 for the concert is transmitted from the web server 14 and displayed on the display of the smartphone 22, as shown in FIG. 12(b).
The user α finds a seat close to his/her preference from this vacant seat list 83 and touches the selection button 84.
After that, you can obtain a seat-assigned electronic ticket by performing the same steps as for obtaining a general electronic ticket, such as inputting user information, selecting a payment method, and inputting payment information.
The ticket processing unit 34 flags the seat number in the ticket DB 46 as "issued".
Of course, this seat reservation type electronic ticket can also be issued for free events (ticket price = 0 yen).

When issuing this seat-reserved electronic ticket, the organizer β specifies the issuance of a "seat-reserved electronic ticket" at the time of event planning, inputs the total number of seats and individual seat numbers, and registers them in the event DB44. I'll keep it.
When the user α obtains an electronic ticket for a specific seat number, the ticket processing unit 34 generates ticket information including the seat number and stores it in the ticket DB 46.
Further, the ticket processing unit 34 generates the vacant seat list 83 by referring to the ticket information (seat numbers with the issued flag set) stored in the ticket DB 46.

Although not shown, the ticket screen for this seat-assigned electronic ticket includes the face photo of user α, ticket name, event date and time, seat number, event organizer name, ZIC Z member number (user ID), and usage information. The person's name, etc. is displayed.
Further, in the area where the ticket name and seat number are displayed, a blue availability display band 64 indicating unused status is placed in the background.
When the user α arrives at the venue and reads the two-dimensional code installed at the venue with the camera of the smartphone 22, a check-in screen (not shown) is sent from the web server 14.

On the other hand, when the venue staff confirms that the face photo on the check-in screen and the user At the same time, the used electronic ticket is sent from the web server 14 to the smartphone 22 and displayed on the display.
In this used electronic ticket, the background of the portion displaying the ticket name and seat number is replaced with a red used display band 69 indicating that the ticket has been used, similar to the above.

This electronic ticket system 10 can also be used to issue lottery-type electronic tickets.
In this case, the organizer β specifies the issuance of a "lottery type electronic ticket" when planning the event, and also sets the application period (start date/time/end date/time), total number of tickets, etc. in the event DB 44.

When the user α applies to obtain a lottery-type electronic ticket within the application period, the ticket processing unit 34 registers the ticket information in the ticket DB 46.
However, since the acquisition has not been finalized at this point, even if there is a fee, the payment will not be made. In addition, a flag of "applying" is set in the ticket information.
When the lottery date and time arrives and the organizer β requests the Web server 14 to conduct the lottery, a lottery screen 90 is displayed on the display of the organizer β's PC 24, as shown in FIG. 13(a).
Here, when the organizer β clicks on the "Random Lottery" button 91, the ticket processing unit 34 randomly extracts the set total number of tickets from among the large number of applicants.

FIG. 13(b) shows a lottery result screen 92, in which the winning applicants in the applicant list 93 are marked as winning.
An e-mail notifying the winner will be automatically sent from the web server 14 to the winner.
When the winner accesses the Web server 14 and pays for the ticket within a predetermined period, the "applying" flag is changed to "issued" and an electronic ticket is issued.
It goes without saying that lottery-type electronic tickets can also be issued for free events (ticket price = 0 yen).

In the embodiment shown in FIG. 9, the user α displays a compatible electronic ticket 60 on the display of the smartphone 22 in advance at the event venue, and reads the two-dimensional code 65 installed at the event venue with a camera. Although it was necessary to display the check-in screen 66, the present invention is not limited to this method.

14 and 15 show other embodiments of the invention.
In this case, when the user α logs in to the web server 14, the screen of the electronic participation card 100 shown in FIG. 14(a) is displayed on the display of the smartphone 22.
This electronic participation certificate 100 includes a face photo 51 of user α and a list 104 of electronic ticket names 102 that can be used by the user α at the moment, and has a function to bundle multiple electronic tickets. There is.
Each electronic ticket name 102 in this list 104 has a blue availability display band 64 arranged in the background to indicate that it is available for use.
This list 104 is generated by the ticket processing unit 34 referring to the ticket DB 46.

At this point, the user α presents the electronic participation certificate 100 to the staff at the event venue and asks them to confirm that his face matches the person in the face photo 51.
Next, when the user α touches any available display band 64, a selection screen 106 for the ticket to be used this time is displayed, as shown in FIG. 14(b). On this available ticket selection screen 106, available electronic ticket selection buttons 108 are arranged.

On the other hand, when user α touches the electronic ticket selection button 108 (○○ Sentai Show (Adult) and ○○ Sentai Show (Child)), the corresponding selection button is displayed as shown in FIG. 14(c). The color of 108 changes from white to yellow, and the use button 110 becomes selectable.

Next, when the user α touches the use button 110 on the ticket selection screen 106, a reconfirmation screen 112 appears, prompting the user α to reconfirm, as shown in FIG. 14(d).
Here, when the user α touches the use button 114 again, a check-in screen 118 including an admission confirmation button 116 is displayed on the display of the smartphone 22, as shown in FIG. 15(a). This admission confirmation button 116 displays the word "use" and has the same appearance as the previous use buttons 110 and 114, but it should be touched by the staff at the event venue, not by user α. .

User α presents this check-in screen 118 to the staff and asks them to touch the admission confirmation button 116. As a result, the updated electronic participation card 100 is displayed on the display of the smartphone 22, as shown in FIG. 15(b). In this electronic participation certificate 100, a red used display band 69 is placed in the background of the electronic ticket that has just been used.
Also, on the server side, the ticket processing unit 34 executes a process of recording the usage date and time in the corresponding record of the ticket DB 46.

As a trial, when user α touches the remaining electronic ticket name (XX Dinner Show) with the blue available display band 64 on this participation card screen, the usage ticket selection screen appears as shown in Figure 15(c). 106 is displayed, but used electronic tickets are listed as used electronic tickets in the usage history column 120 and are excluded from selection.
This used electronic ticket has a red used display band 69 arranged in the background, and also has the ticket name 102 and date and time of use 122 written on it.

According to this embodiment, the organizer β can save the effort of installing two-dimensional codes at the venue.
Further, since the electronic participation card 100 has a function of bundling and listing a plurality of electronic tickets acquired by the user α, there is an advantage that the electronic tickets can be easily managed by the user α.
It goes without saying that the above-mentioned coupon type electronic ticket, seat reservation type electronic ticket, and lottery type electronic ticket can also be applied to this embodiment.

10 Electronic ticket system
12 Data center (server group)
14 Web server
16 AP server
18 DB server
20 Internet
22 Smartphone
24 Computer
30 User Management Department
32 Event generation section
34 Ticket processing section
36 Payment Processing Department
38 Payment server
40 DB management department
42 User DB
44 Event DB
46 Ticket DB
48 Image storage section
50 Passport screen
51 Face photo
56 User information input screen
58 Payment method selection screen
60 Electronic ticket
61 Ticket name
64 Available display band
65 QR code
66 Check-in screen
67 Admission confirmation button
68 Used electronic ticket
69 Used display band
70 coupon-type electronic tickets
81 Seating chart
82 Detailed seating chart
83 Vacancy list
90 Lottery screen
92 Lottery result screen
93 Applicant list
100 Electronic participation certificate
102 Electronic ticket name
104 List of electronic ticket names
106 Ticket selection screen
108 selection button
110 Use button
112 Reconfirmation screen
114 Use button
116 Admission confirmation button
118 Check-in screen
120 Usage history field
122 Usage date and time α User α
β Organizer β

Claims (6)

An electronic ticket system comprising a server connected to each user terminal owned by a plurality of users via a network,
The server includes a storage means for registering image data of each user's face photograph in association with a user ID;
an event storage means for registering information regarding multiple events in association with an event ID;
a ticket storage means for registering an event ID related to an electronic ticket obtained by a user in association with a user ID;
Equipped with a means for transmitting the electronic ticket obtained by the user to the user terminal,
The electronic ticket displayed on the display of the user terminal includes the user's face photo, the event name, and an availability display indicating that the electronic ticket is available for use.
When the user connects to the server via the user terminal and reads the code installed at the event venue with the camera of the user terminal, the server identifies the event based on the event ID included in the code, and Checking whether the user is registered in the ticket storage means as a ticket acquirer for the event;
If you are the ticket acquirer, send a check-in screen with an admission confirmation button to the user terminal,
When the entrance confirmation button is touched by the staff at the event venue who has confirmed that the user is the same person by comparing the face photo on the electronic ticket with the user's face, a used display will be displayed indicating that the electronic ticket has been used. An electronic ticket system characterized by displaying on an electronic ticket. The event storage means records the number of times the coupon type electronic ticket can be used.
When the user connects to the server via the user terminal and reads the code installed at the event venue with the camera of the user terminal, the server identifies the event based on the event ID included in the code, and Checking whether the user is registered in the ticket storage means as a ticket acquirer for the event and whether there are any remaining number of uses;
If the user is the person who acquired the ticket and there is a remaining number of uses, a check-in screen with an admission confirmation button is sent to the user terminal,
When the admission confirmation button is touched by the staff at the event venue, the server adds information indicating the fact of use to the ticket storage means,
A claim characterized in that, if the user is the acquirer of the ticket and there is no remaining number of uses, a used indication indicating that the electronic ticket has been used is displayed on the electronic ticket. The electronic ticket system described in Section 1. An electronic ticket system comprising a server connected to each user terminal owned by a plurality of users via a network,
The server includes a storage means for registering image data of each user's face photograph in association with a user ID;
an event storage means for registering information regarding multiple events in association with an event ID;
a ticket storage means for registering an event ID related to an electronic ticket obtained by a user in association with a user ID;
Equipped with a means for transmitting an electronic participation certificate to a user terminal,
The electronic participation certificate displayed on the display of the user terminal includes the user's face photo and a list of unused electronic tickets acquired by the user.
When the user selects to use an electronic ticket corresponding to the event from the list above at the event venue, the server sends a check-in screen with an admission confirmation button to the user terminal,
When the entrance confirmation button is touched by the staff at the event venue who has confirmed that the user is the same person by comparing the face photo on the electronic participation card and the user's face, the electronic ticket will be marked as used. An electronic ticket system characterized in that a display is displayed on an electronic participation certificate. The event storage means records the number of times the coupon type electronic ticket can be used.
The unused electronic tickets in the list above include coupon-type electronic tickets that have a remaining number of uses.
When the user selects to use a coupon type electronic ticket from the above list, the above server sends a check-in screen with an admission confirmation button to the user terminal,
When the entry confirmation button is touched by the staff at the event venue who has confirmed that the user is the same person by comparing the face photo on the electronic participation card and the user's face, the server stores the information indicating the fact of use into the ticket storage means. and add it to
4. The electronic ticket according to claim 3, wherein when there is no remaining number of tickets available, a used indication indicating that the ticket-type electronic ticket has been used is displayed on the electronic participation certificate. ticket system. A plurality of seat numbers related to the event are registered in the event storage means,
When a request to obtain a ticket is sent from the user terminal, the server refers to the ticket storage means, extracts seat numbers for which the issued flag is not set, and sends the list to the user terminal. death,
When a request to obtain a specific seat number from the above list is sent from the user terminal and, in the case of a fee, the necessary payment processing is completed, the issued ticket is displayed for the seat number in the above ticket storage means. 4. The electronic ticket system according to claim 1, wherein a flag is set. The total number of tickets for the event and the application period are registered in the event storage means,
When a request to obtain a ticket is sent from the user terminal within the application period, the server temporarily registers the user as an applicant in the ticket storage means,
Randomly extract winners for the total number of tickets from among the applicants stored in the ticket storage means at a predetermined timing,
4. The electronic ticket system according to claim 1, wherein a notification of winning is sent to each winner's user terminal.

Images