JP7814029B2 - Electronic Ticket System - Google Patents

Description

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

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

With the spread of the Internet and smartphones (hereinafter referred to as "smartphones"), tickets for events such as concerts and sporting events are shifting from traditional paper to electronic ones (see Non-Patent Documents 1 and 2 below).
Comparing 8 e-ticket systems and apps! How to create digital tickets (Internet URL: http://blog.500mails.com/online-ticket-system-comparison/ Retrieved March 14, 2022) What are e-tickets? Types, advantages and disadvantages. Internet URL: https://www.ic-net.co.jp/media/ticket_sales/a12. Search date: March 14, 2022.

By utilizing these existing electronic ticket services, event organizers can plan and announce various events with relatively little effort, and issue participation tickets to general users at low cost.
Furthermore, on the day of the event, users will need to be allowed into the venue after confirming whether they have a participation ticket and whether it is legitimate, but this can also be done by simply scanning the barcode or 2D code displayed on the user's smartphone screen, eliminating the need for staff to tear off the ticket by hand and hand the stub to the user as was done in the past. This also has the added benefit of allowing entry/exit status management for each user.
For users, there is also the benefit of being able to instantly obtain tickets via a smartphone or other device without having to wait for paper tickets to be mailed, and there is no risk of losing them.

As such, there is no doubt that using electronic ticket services offers many benefits to both event organizers and users. However, the existing system, which checks entry by scanning barcodes displayed on smartphone screens, still leaves a problem: it is difficult to detect fraud such as ticket resale and counterfeiting.
The present invention was devised in light of the current situation, and aims to realize a system that makes it possible to easily and reliably check the legitimacy of a person who possesses an electronic ticket.

In order to achieve the above object, the electronic ticket system described in 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 server comprising a storage means for registering image data of each user's facial photograph in association with a user ID, an event storage means for registering information on a plurality of events in association with the event ID, a ticket storage means for registering the event ID related to an electronic ticket acquired by a user in association with the user ID, and a means for transmitting the electronic ticket acquired by the user to the user terminal, and the electronic ticket displayed on the display of the user terminal includes the user's facial photograph, the event name, and an availability indicator indicating that the electronic ticket is available for use. When a user connects to the server via the user terminal and uses the camera on the user terminal to read a code (two-dimensional code or barcode) installed at the event venue, the server identifies the event based on the event ID included in the code and checks whether the user is registered in the ticket storage means as a ticket holder for that event. If the user is a ticket holder, a check-in screen with an admission confirmation button is sent to the user terminal. When the admission confirmation button is touched by event venue staff who compare the photo on the electronic ticket with the user's face to confirm that they are the same person, a "used" indicator is displayed on the electronic ticket indicating that the electronic ticket has been used.

The electronic ticket system described in claim 2 is the system of claim 1, wherein the event storage means records the number of times a multi-ride electronic ticket can be used. When a user connects to the server via the user terminal and uses the user terminal's camera to scan a code installed at the event venue, the server identifies the event based on the event ID included in the code and checks whether the user is registered in the ticket storage means as a ticket holder for that event and whether the user has any remaining uses. If the user is a ticket holder and has any remaining uses, a check-in screen with an admission confirmation button is sent to the user terminal. When the admission confirmation button is touched by a staff member at the event venue, the server adds information indicating use (such as the date and time of use and the number of uses), to the ticket storage means. If the user is a ticket holder and has no remaining uses, a "used" indicator is displayed on the electronic ticket indicating that the electronic ticket has been used.

The electronic ticket system described in claim 3 is an electronic ticket system comprising a server connected via a network to each user terminal owned by a plurality of users. The server comprises storage means for registering image data of each user's facial photograph in association with a user ID, event storage means for registering information about a plurality of events in association with the event ID, ticket storage means for registering event IDs related to electronic tickets acquired by users in association with the user ID, and means for sending electronic participation certificates to the user terminals. The electronic participation certificate displayed on the display of the user terminal includes the user's facial photograph and a list of unused electronic tickets acquired by the user. When the user selects to use an electronic ticket for that event from the list at the event venue, the server sends a check-in screen with an admission confirmation button to the user terminal. When the admission confirmation button is touched by a staff member at the event venue who compares the facial photograph on the electronic participation certificate with the user's face and confirms that they are the same person, a "used" indication is displayed on the electronic participation certificate indicating that the electronic ticket has been used.

The electronic ticket system described in claim 4 is the system of claim 3, wherein the event storage means records the number of times that a multi-ride electronic ticket can be used, and the unused electronic tickets in the list include multi-ride electronic tickets with remaining uses, and when a user selects to use a multi-ride electronic ticket from the list, the server sends a check-in screen with an admission confirmation button to the user's terminal, and when the admission confirmation button is touched by an event venue staff member who compares the face photograph on the electronic participation certificate with the user's face and confirms that they are the same person, the server adds information indicating the use to the ticket storage means, and when the remaining uses are exhausted, a "used" indication is displayed on the electronic participation certificate indicating that the multi-ride electronic ticket has been used.

The electronic ticket system described in claim 5 is the system of claim 1 or 3, wherein the event storage means registers multiple seat numbers related to an event, and when a ticket acquisition request is sent from the user terminal, the server references the ticket storage means, extracts seat numbers for which the issued flag is not set, and sends this list to the user terminal. When a ticket acquisition request is sent from the user terminal for a specific seat number in the list, and if a paid seat is required, the server sets an issued flag for that seat number in the ticket storage means when payment processing for the required fee is completed.

The electronic ticket system described in claim 6 is the system of claim 1 or 3, wherein the event storage means stores the total number of tickets for the event and the application period, and when a ticket acquisition request is sent from the user terminal within the application period, the server provisionally registers the user as an applicant in the ticket storage means, randomly selects winners from the applicants stored in the ticket storage means at a predetermined timing based on the total number of tickets, and sends a notification of winning to the user terminal of each winner.

In the case of the electronic ticket system according to claim 1, a user can display the electronic ticket for the event on a user terminal such as a smartphone simply by scanning a two-dimensional code or barcode installed at the event venue.
Furthermore, because the electronic ticket displays the user's photograph, staff at the event venue can easily and reliably confirm that the holder of the electronic ticket is the legitimate ticket purchaser, making it easy to eliminate fraudulent impersonation attempts.
Furthermore, once a staff member touches the admission confirmation button on the check-in screen, an electronic ticket stamped with a used indication will be displayed on the user's terminal, effectively preventing unauthorized reuse.

In the case of the electronic ticket system of claim 3, an electronic participation certificate containing a list of unused electronic tickets acquired by the user is displayed on the user's terminal such as a smartphone, and since this electronic participation certificate displays the user's photograph, staff at the event venue can easily and reliably confirm that the holder of the electronic participation certificate is the legitimate purchaser of the electronic tickets on the list, making it easy to eliminate fraudulent impersonation.
Furthermore, once a staff member touches the admission confirmation button on the check-in screen, the corresponding electronic ticket will be displayed on the electronic participation certificate with a stamped indication that it has been used, effectively preventing unauthorized reuse.

1 is a block diagram showing the overall configuration of an electronic ticket system according to the present invention. FIG. 2 is a diagram illustrating an example of a table configuration of a user DB. FIG. 10 is a diagram showing an example of a screen layout of a GIC passport. FIG. 2 is a diagram illustrating an example of a table configuration of an event DB. FIG. 2 is a diagram illustrating an example of a table configuration of a ticket DB. 10 is a flowchart showing a processing procedure for obtaining an electronic ticket. FIG. 10 is a diagram showing an example of a screen configuration related to obtaining an electronic ticket. FIG. 10 is a diagram showing an example of a screen configuration related to obtaining an electronic ticket. This figure shows an example of the screen layout of an electronic ticket and an example of the screen transitions that occur when the ticket is used. 10 is a flowchart showing a processing procedure for using an electronic ticket. 10A and 10B are diagrams showing examples of screen configurations and transitions when an electronic ticket is used as a coupon ticket. FIG. 10 is a diagram showing an example of a screen configuration when seat reservation is performed in this electronic ticket system. FIG. 10 is a diagram showing an example of a screen configuration when a lottery is held in this electronic ticket system. 10A and 10B are diagrams showing an example of a screen configuration and an example of screen transitions associated with use in another embodiment of an electronic ticket. 10A and 10B are diagrams showing an example of a screen configuration and an example of screen transitions associated with use in another embodiment of an electronic ticket.

FIG. 1 is a block diagram showing an example of the configuration of an electronic ticket system 10 according to the present invention, which includes a web server 14, an AP (Application) server 16, and a DB (Database) server 18 installed in a data center (group of servers) 12.
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 to user terminals such as smartphones 22 and PCs 24 owned by a plurality of 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 can also be used.
Both user α and organizer β refer to users of the system 10, and when an event is organized, the user becomes organizer β, and when an event is participated in, the user becomes user α.

The AP server 16 includes a user management unit 30, an event generation unit 32, a ticket processing unit , and a payment processing unit .
The user management unit 30, the event generation unit 32, the ticket processing unit 34, and the payment processing unit 36 are functional components realized by the CPU of the AP server 16 operating in accordance with the OS and dedicated application programs.
The payment processing unit 36 is connected via a communication network to a plurality of payment servers 38. 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 processes such as storing and extracting necessary data in response to requests from the AP server 16 .
The 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.
The DB server 18 has a storage device in which a user DB 42, an event DB 44, a ticket DB 46, and an image storage unit 48 are provided.

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

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

When registering as a user, a facial photograph is required, so the user takes a selfie using the camera on the smartphone 22, and uploads an image file of the photograph to the web server 14.
The image file of this facial photograph 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 data item "facial photograph image" in the user DB 42.
Incidentally, when a user registers, a unique 16-digit user ID (GicZ member number) is automatically assigned by the user management unit 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 facial photograph 51 and GicZ membership number (user ID) 52.
A user who has acquired this passport can then participate in any event of their choice as a user α or plan an event as a organizer β.

When planning a new event, organizer β logs in to web server 14 via smartphone 22 or PC 24 and enters the necessary information into a specified form (not shown), and the event information is then registered in event DB 44 by event generation unit 32 and DB management unit 40.

Figure 4 shows an example of a record stored in event DB44, and includes data items such as "Event ID," "User ID" of organizer β, "Organizer Information," "Event Name," "Event Category," "Event Content," "Event Date and Time," "Event Location," "Event URL," "Flyer Image," "Ticket Name," "Ticket Price," "Total Number of Tickets," "Number of Tickets Available at One Time," "User Information," "Sales Start Date and Time," "Sales End Date and Time," "Fee Payer," "Sales Proceeds Transfer Account," and "Update Date and Time."

Here, "user information" refers to information such as name, gender, age, and area of residence that event organizer β wants to obtain from user α, and is information that user α is required to enter when purchasing a ticket (details will be provided later).

Figure 5 shows an example of a record stored in ticket DB46, and includes data items such as "Event ID," "Ticket ID," "Ticket Price," "User ID" and "Email Address" of user α, "User Information" entered by the user when acquiring the ticket, "Sale Date and Time," "Payment Method (Payment Type)," "Payment Date and Time," and "Use Date and Time."

The processing procedure when user α acquires an electronic ticket will be described below with reference to the flowchart of FIG.
First, user α accesses the dedicated website from his/her smartphone 22, enters his/her email address and user ID to log in to the web server 14, and selects "Get a ticket" from the menu (S10), which sends an event search screen (not shown) (S12).

When the user enters a search keyword (for example, "marathon") on this screen (S14), a search result screen is sent from the Web server 14 (S16).
FIG. 7 shows the search results displayed on the same screen, with multiple tickets related to the marathon listed.
In response, the user checks the name of each ticket, checks the selection box for the ticket they need, enters the number of tickets they want, and then touches the order button 54 (S18).

As a result, as shown in FIG. 8(a), a user information input screen 56 is sent 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 required conditions for obtaining a ticket, and input of gender and prefecture are set as optional conditions.
However, this is merely an example, and organizer β can also set different information as "user information" when registering event information.

When user α inputs user information and touches the send button 57 (S22), a 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 (e.g., "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 enters the credit card number, expiration date (year/month), security code, etc. (S30), the payment processing unit 36 of the AP server 16 executes the payment processing (S32). That is, the payment processing unit 36 transmits the payment information to the corresponding payment server 38 and requests payment of the ticket price.
Then, when the payment is completed, new ticket information is 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, the ticket price will be transferred in one lump sum to the bank account of organizer β.

If the ticket is free (ticket price = 0 yen), steps S24 to S32 are skipped, and ticket information is registered immediately after user α enters their user information.

After this, the electronic ticket is sent from the web server 14 to the smartphone 22 of user α (S36) and displayed on the display of the smartphone 22 (S38).
Figure 9(a) shows an example of an electronic ticket 60, which displays a photo of user α's face 51, the ticket name 61, the name of the event organizer 62, the GicZ membership number (user ID) 52, the user's name 63, etc.
The area displaying the ticket name 61 has a blue band indicating "unused," i.e., an available use indication band 64, set against the background. However, the color of the available use indication band 64 is not limited to blue. Also, a band other than a specific color may be used to indicate the available use of an electronic ticket.

Next, the processing procedure when user α uses an electronic ticket will be described with reference to the flowchart of FIG.
That is, when user α visits the event venue on the day of the event, logs in to the web server 14 using a browser on his/her smartphone 22, and requests the 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 Figure 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 member checks that the face photograph 51 on the electronic ticket 60 matches the face of the user α, and that the blue band (available use display band 64) is displayed.
Next, as shown in Figure 9(b), when user α uses the camera on his/her smartphone 22 to scan a two-dimensional code 65 such as a QR code (registered trademark) or a barcode installed at the reception desk of the event venue (S56), a check-in screen for the event is sent from the web server 14 (S58), and as shown in Figure 9(c), a check-in screen 66 is displayed on the display of the smartphone 22 (S60).

In other words, since the two-dimensional code 65 contains the event ID, the ticket processing unit 34 identifies the event based on this event ID, and then refers to the ticket DB 46 to confirm that the user α is present as a ticket holder for the event, before generating a check-in screen 66 and sending it to the smartphone 22.
Incidentally, if user α is not registered in the ticket DB 46 as the person who has acquired the ticket, the ticket processing unit 34 returns an error message such as "Cannot be used because ticket has not been acquired" to the smartphone 22 instead of sending the check-in screen 66.

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

As a result, the ticket processing unit 34 records the date and time of use in the corresponding record in the ticket DB 46 (S64), and as shown in Figure 9(d), the used electronic ticket 68 is sent 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 indicator band 69 indicating "used." However, the color of the used indicator band 69 is not limited to red. Also, an indicator other than a band with a specific color can be used to indicate that an 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 indicator 69 will always be displayed on the smartphone 22, preventing the same ticket from being fraudulently reused.
Meanwhile, inside the event venue, possession of a used electronic ticket 68 with a red used indicator band 69 serves as proof that the official admission procedure (check-in) has been completed.

As described above, the venue staff visually checks the face of the visiting user α against the photograph 51 displayed on the electronic ticket 60, and if they determine that they are the same person, the person touches the admission confirmation button 67 on the check-in screen 66 to be permitted entry. This makes it extremely easy and accurate to verify the identity of the person, and it is possible to reliably exclude entry to those who have obtained tickets through fraudulent resale or theft.
Furthermore, if the face of user α does not match the photograph 51 on the electronic ticket 60, the staff will naturally refuse participation in the event, and will not be allowed to read the two-dimensional code 65, nor will they be allowed to display the check-in screen 66.

Using this electronic ticket system 10, it is also possible to issue electronic tickets (electronic coupon tickets) that can be used repeatedly a predetermined number of times, rather than tickets that can only be used once.
Figure 11(a) shows a 12-ticket multi-ride type electronic ticket 70a issued by a massage parlor, which, like the general electronic ticket 60 described above, displays the user's face photo 51, ticket name (multi-ride ticket name) 61, organizer name (issuer name) 62, GicZ membership number (user ID) 52, name 63, etc.
The portion displaying the ticket name 61 has a blue available ticket display band 64 in the background.
Also, the "Number of uses/total number" is displayed as "0/12." In this case, since the ticket has not yet been used, it means that there are 12 more uses available, i.e., there are 12 remaining uses.

When user α visits a store that is an event venue and presents the multi-ride electronic ticket 70a shown in Figure 11(a), the store staff confirms that the face photograph 51 matches the face of user α and that a blue band (available use indication band 64) is displayed.
Next, when user α scans the two-dimensional code installed at the store's reception desk with the camera on his/her smartphone 22, a check-in screen to the store is automatically sent from the web server 14 and displayed on the display of the smartphone 22 (not shown).
In response to this, when a store staff member touches the entry confirmation button on the check-in screen, the ticket processing unit 34 records the date and time of use in the corresponding record in the ticket DB 46, and a one-time use screen 70b is sent from the web server 14 to the smartphone 22 and displayed on the display, as shown in Figure 11 (b).
In this case, the blue available tickets indicator 64 is still displayed in the background of the area displaying the ticket name 61, but the "Number of uses/total number" has been updated to "1/12" (number of remaining uses: 12 - 1 = 11).

When user α has used up all of the tickets, as shown in Figure 11(c), the "Number of uses/total number" of the ticket-type electronic ticket 70c is updated to "12/12 (= number of remaining uses: 0)," and the background of the area displaying the ticket name 61 is replaced with a red used indication band 69.

When issuing this multi-ticket type electronic ticket 70, the organizer β specifies the issuance of a "multi-ticket type electronic ticket" when planning the event, and also sets the number of times it can be used.
This number of times the facility can be used is recorded in the event DB 44 and ticket DB 46.
Furthermore, each time 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 coupon tickets) of the coupon ticket.

This electronic ticket system 10 can also be used to issue seat-reserved electronic tickets.
In this case, user α narrows down the seats he or she wants in advance.
That is, when user α accesses the homepage of organizer β using smartphone 22 or PC 24 and requests a seat display for a concert or the like, and selects "Seat E" in the displayed seating chart 81 as shown in Figure 12(a), a detailed seating chart 82 is displayed, showing the individual seat numbers and positions included in the group of seats E.
By viewing this detailed seating chart 82, user α can get an idea of the seat he or she wants.

Next, user α accesses the web server 14 from the smartphone 22 and inquires about the availability of the relevant electronic ticket.
As a result, as shown in FIG. 12( b ), a list of available seats 83 for the concert is sent from the web server 14 and displayed on the display of the smartphone 22 .
User α finds a seat that is closest to his/her preference from the vacant seat list 83 and touches the selection button 84.
After that, you can obtain a reserved-seat electronic ticket by following the same steps as when obtaining a regular electronic ticket, i.e., entering user information, selecting a payment method, entering payment information, etc.
The ticket processing unit 34 sets a flag for the seat number in the ticket DB 46 as "issued."
Of course, this seat-reserved 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" when planning the event, and also inputs the total number of seats and individual seat numbers, which are then registered in the event DB 44.
When user α acquires an electronic ticket with a specific seat number, the ticket processing unit 34 generates ticket information including the seat number and stores it in the ticket DB 46 .
The ticket processing unit 34 also generates the vacant seat list 83 by referencing the ticket information (seat numbers for which an issued flag is set) stored in the ticket DB 46 .

Although not shown in the figure, the ticket screen for this seat-reserved electronic ticket displays a photo of user α, the ticket name, the date and time of the event, the seat number, the name of the event organizer, the GicZ membership number (user ID), the user's name, etc.
Additionally, the portion displaying the ticket name and seat number has a blue available use indicator band 64, indicating that the ticket is not yet in use, in the background.
When user α arrives at the venue and scans the two-dimensional code installed at the venue with the camera of smartphone 22, a check-in screen (not shown) is sent from web server 14.

In response, when the venue staff confirms that the facial photo on the check-in screen is the same as that of user α and then touches the entry confirmation button, the ticket processing unit 34 records the date and time of use in the corresponding record in the ticket DB 46, and the used electronic ticket is sent from the web server 14 to the smartphone 22 and displayed on the screen.
In this used electronic ticket, the background of the area displaying the ticket name and seat number has been replaced with a red used indication band 69, similar to the above.

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

When a user α applies for a lottery-type electronic ticket within the application period, a ticket processing unit 34 registers the ticket information in a ticket DB 46.
However, since the acquisition has not been confirmed at this point, payment will not be made even if the ticket is paid. Also, a "Submission in progress" flag will be set in the ticket information.
When the lottery date and time arrives and the organizer β requests the Web server 14 to hold a lottery, a lottery screen 90 is displayed on the display of the PC 24 of the organizer β, as shown in FIG. 13(a).
Here, when the organizer β clicks the "random lottery" button 91, the ticket processing unit 34 randomly selects the set total number of tickets from among the many applicants.

FIG. 13(b) shows the lottery result screen 92, in which the winning applicants in the applicant list 93 are marked with a win check mark.
The winners will automatically receive an e-mail from the Web server 14 informing them of their win.
If the winner accesses the Web server 14 within a predetermined period and pays the ticket fee, the "Application in progress" flag is changed to "Issued" and the electronic ticket is issued.
It goes without saying that lottery-based electronic tickets can also be issued for free events (ticket price = 0 yen).

In the embodiment shown in Figure 9, user α had to display the corresponding electronic ticket 60 on the display of their smartphone 22 in advance at the event venue, and then use a camera to read a two-dimensional code 65 installed at the event venue to display the check-in screen 66, but the present invention is not limited to this method.

14 and 15 show another embodiment of the present invention.
In this case, when user α logs in to the web server 14, the screen of the electronic participation certificate 100 shown in FIG.
This electronic participation certificate 100 includes a face photograph 51 of the user α and a list 104 of the names 102 of electronic tickets currently available to the user α, and has the function of bundling multiple electronic tickets.
Each electronic ticket name 102 in this list 104 has a blue available status indicator band 64 placed in the background, indicating that the ticket is available for use.
This list 104 is generated by the ticket processing unit 34 by referring to the ticket DB 46 .

At this point, user α presents electronic participation certificate 100 to the staff at the event venue, and has them confirm that his or her face matches the person in facial photograph 51.
Next, when user α touches one of the available ticket display bands 64, a selection screen 106 for the ticket to be used this time is displayed, as shown in Fig. 14(b). This selection screen 106 for the ticket to be used has buttons 108 for selecting available electronic tickets.

In response to this, when user α touches the selection button 108 for the electronic ticket they wish to use (XX Sentai Show (Adult) and XX Sentai Show (Children)), the color of the corresponding selection button 108 changes from white to yellow, and the use button 110 becomes selectable, as shown in Figure 14(c).

Next, when user α touches the use button 110 on the ticket selection screen 106, a reconfirmation screen 112 appears as shown in FIG. 14(d), prompting user α to reconfirm.
If user α then touches the use button 114 again, as shown in Figure 15(a), a check-in screen 118 with an admission confirmation button 116 will appear on the display of smartphone 22. 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 event venue staff, not user α.

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

If user α touches the name of the remaining electronic ticket (XX Dinner Show) with the blue available use indicator 64 on the participation certificate screen, the ticket selection screen 106 will be displayed as shown in Figure 15(c), but the electronic ticket that has already been used will be listed as an already used electronic ticket in the usage history column 120 and will not be available for selection.
This used electronic ticket has a red used indication band 69 on the background, and the ticket name 102 and the date and time of use 122 are written on it.

According to this embodiment, it is possible for the organizer β to avoid the trouble of placing two-dimensional codes at the venue.
Furthermore, the electronic participation certificate 100 has a function of bundling and listing multiple electronic tickets acquired by user α, which provides the advantage of making it easier for user α to manage the electronic tickets.
It goes without saying that the above-mentioned multi-ticket type electronic tickets, seat reservation type electronic tickets, and lottery type electronic tickets can also be applied in 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 PC
30 User Management Department
32 Event Generation Unit
34 Ticket Processing Unit
36 Payment processing section
38 Payment Server
40 DB management department
42 User DB
44 Event DB
46 Ticket DB
48 Image storage unit
50 Passport Screen
51 Photo
56 User information input screen
58 Payment method selection screen
60 e-tickets
61 Ticket Name
64 Available Display Band
65 QR Code
66 Check-in screen
67 Entry confirmation button
68 Used e-tickets
69 Used display band
70 Multi-ticket e-tickets
81 Seating Chart
82 Detailed seating chart
83 Vacant Seat 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 Select button
110 Use button
112 Reconfirmation screen
114 Use button
116 Entry confirmation button
118 Check-in screen
120 Usage history column
122 Usage date and time α User α
β Organizer β

Claims (6)

An electronic ticket system including a server connected to each of a plurality of user terminals via a network,
The server includes: a storage means for registering image data of a facial photograph of each user in association with the user ID;
an event storage means for registering information about a plurality of events in association with an event ID;
a ticket storage means for registering an event ID related to an electronic ticket acquired by a user in association with a user ID;
means for transmitting an electronic ticket acquired by a user to a user terminal;
The electronic ticket displayed on the display of the user terminal includes a user's face photo, the event name, and an availability indicator 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 checks whether the user is registered in the ticket storage means as a ticket acquirer for the event,
If the user is a ticket holder, a check-in screen with an admission confirmation button is sent to the user terminal.
When the admission confirmation button is touched by a staff member at the event venue who has confirmed that the face photograph on the electronic ticket is the same as the user's face by comparing the face photograph on the electronic ticket with the user's face, a display indicating that the electronic ticket has been used is displayed on the electronic ticket. The event storage means stores the number of times that a 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 checks 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 ticket holder and has remaining usage, a check-in screen with an admission confirmation button is sent to the user terminal;
When the admission confirmation button is touched by a staff member at the event venue, the server adds information indicating the fact of use to the ticket storage means,
The electronic ticket system described in claim 1, characterized in that if the user is the ticket acquirer and there are no remaining uses, a used indication indicating that the electronic ticket has been used is displayed on the electronic ticket. An electronic ticket system including a server connected to each of a plurality of user terminals via a network,
The server includes: a storage means for registering image data of a facial photograph of each user in association with the user ID;
an event storage means for registering information about a plurality of events in association with an event ID;
a ticket storage means for registering an event ID related to an electronic ticket acquired by a user in association with a user ID;
means for transmitting an electronic participation certificate to a user terminal;
The electronic participation certificate displayed on the display of the user's terminal includes the user's face photo and a list of unused electronic tickets acquired by the user.
When the user selects the use of an electronic ticket corresponding to the event from the list at the event venue, the server transmits a check-in screen with an admission confirmation button to the user terminal,
When the admission confirmation button is touched by a staff member at the event venue who has confirmed that the face photograph on the electronic participation certificate is the same as the user's face by comparing it with the face of the user, a display indicating that the electronic ticket has been used is displayed on the electronic participation certificate. This electronic ticket system is characterized in that The event storage means stores the number of times that a coupon-type electronic ticket can be used,
The unused e-tickets in the list above include multi-ticket e-tickets with remaining usage.
When the user selects the use of a multi-ticket type electronic ticket from the list, the server sends a check-in screen with an admission confirmation button to the user terminal,
When the event venue staff touches the admission confirmation button after comparing the face photograph on the electronic participation certificate with the user's face and confirming that they are the same person, the server adds information indicating the fact of use to the ticket storage means,
The electronic ticket system described in claim 3, characterized in that when there are no more available uses, a used indication indicating that the multiple-use electronic ticket has been used is displayed on the electronic participation certificate. The event storage means has a plurality of seat numbers related to the event registered therein,
When a ticket acquisition request is sent from the user terminal, the server refers to the ticket storage means, extracts seat numbers for which an issued flag is not set, and sends the list to the user terminal;
An electronic ticket system as described in claim 1 or 3, characterized in that a request for acquisition of a specific seat number in the list is sent from a user terminal, and when the payment process for the necessary fee is completed in the case of a paid seat, an issued flag is set for the seat number in the ticket storage means. The event storage means stores the total number of tickets for the event and the application period,
When a request for ticket acquisition is transmitted from the user terminal within the application period, the server provisionally registers the user as an applicant in the ticket storage means;
At a predetermined timing, winners are randomly selected from among the applicants stored in the ticket storage means, the number of winners being equal to the total number of tickets;
4. The electronic ticket system according to claim 1, wherein a notification of winning is sent to the user terminal of each winner.