JP7515082B2 - Electronic ticket management system, electronic ticket management server, electronic ticket management method and program - Google Patents

Description

The present invention relates to an electronic ticket management system, an electronic ticket management server, an electronic ticket management method, and a program.

For example, when a paper ticket is used as an admission ticket, product voucher, discount ticket, multiple-ride ticket, gift certificate, coupon, or other ticket, information about the ticket is printed on the paper. The printed ticket is sent to the user, for example by mail or hand delivery. When the user uses the ticket, the ticket becomes used, for example by the user handing it to a store staff member, or by the store staff tearing off part of the ticket. When it is necessary to tally up information such as the number of tickets used, the date and time the tickets were used, this is done by the store, etc.

For example, when an electronic ticket is used as an admission ticket or the like, the electronic ticket is displayed on a user terminal or the like using a web browser, an application, etc. Display data of the electronic ticket is distributed from a distributor to the user terminal by using, for example, email, a social networking service (SNS) application, etc.
In one example of using an electronic ticket, the electronic ticket displayed on the user terminal is presented to a store staff member, etc. In this example, the store staff member, etc. cannot switch the electronic ticket to a used state, so there is a risk that the used electronic ticket may be used again fraudulently.
In another example of using an electronic ticket, a use button or the like included in the electronic ticket displayed on the touch panel of the user terminal is operated (e.g., clicked) by a store staff member, etc. In this example, the electronic ticket is switched to a used state by the operation of the store staff, etc., but information regarding the store where the electronic ticket was used (information indicating which store the electronic ticket was used at) cannot be generated.
In yet another example of the use of an electronic ticket, identification information such as a code contained in the electronic ticket displayed on the user terminal is read by a reader installed in the store. In this example, the electronic ticket is switched to a used state by reading the identification information, and information about the store where the electronic ticket was used is generated, but since it is necessary to install equipment such as a reader in the store, a large system modification cost is incurred.

Furthermore, electronic ticket systems with simplified operations have been known for some time (see, for example, Patent Document 1). In the technology described in Patent Document 1, access information for electronic ticket data is notified to a user terminal, and the electronic ticket data is transmitted to the user terminal in response to access from the user terminal.
In the technology described in Patent Document 1, a URL for downloading a barcode required to obtain electronic ticket data is sent to a user terminal by an e-mail containing the download URL. Furthermore, the user operates the user terminal to access the URL, whereby the barcode is downloaded to the user terminal.
However, when a URL is displayed on a user terminal so that a user can access the URL, if the URL does not fit on the display screen of the user terminal (i.e., if the URL extends beyond the display screen of the user terminal), the user may find it difficult to operate the user terminal. Furthermore, if the user finds it difficult to operate the user terminal, the user may not want to use the electronic ticket.

JP 2006-107368 A

In view of the above-mentioned problems, the present invention aims to provide an electronic ticket management system, an electronic ticket management server, an electronic ticket management method, and a program that can improve user convenience and promote the use of electronic tickets.

One aspect of the present invention is an electronic ticket management system that includes a user terminal, an electronic stamp, and a server unit, and that performs authentication processing of an electronic ticket displayed on the user terminal by using the display screen of the electronic ticket and the electronic stamp when the electronic ticket is used, and the server unit includes an electronic ticket URL issuing unit that issues an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket, and the electronic ticket URL is an abbreviated URL.

In one aspect of the electronic ticket management system of the present invention, the server unit includes an electronic ticket management server having the electronic ticket URL issuing unit, and an electronic ticket sales server that sells the electronic tickets, and the electronic ticket sales server may include a communication unit that transmits the electronic ticket URL issued by the electronic ticket URL issuing unit to the user terminal via at least one of a first channel using email and a second channel using an app installed on the user terminal.

In one aspect of the electronic ticket management system of the present invention, the electronic ticket management server may include a management unit that manages at least one of the channel used to transmit the electronic ticket URL to the user terminal, the number of electronic tickets issued, the date and time of issuance of the electronic ticket, the facility at which the electronic ticket was used, the number of times the electronic ticket was used, and the date and time of use of the electronic ticket.

In one aspect of the electronic ticket management system of the present invention, the server unit includes an authentication processing unit that performs authentication processing of the electronic ticket, and the authentication processing unit may perform cancellation processing of the electronic ticket by using a display screen of the electronic ticket and the electronic stamp.

In one aspect of the electronic ticket management system of the present invention, the server unit includes an electronic ticket display data generation unit that generates display data for the electronic ticket, and the electronic ticket display data generation unit may generate the display data for the electronic ticket so that the user terminal can display the electronic ticket in both cases where a web browser is used and where an app installed on the user terminal is used.

In one aspect of the electronic ticket management system of the present invention, the server unit may include an electronic ticket display restriction unit that restricts the electronic ticket from being displayed on the user terminal unless the web browser and one of the apps installed on the user terminal that is used to access the electronic ticket URL are used.

In one aspect of the electronic ticket management system of the present invention, the electronic ticket may be a single ticket type electronic ticket, and the single ticket type electronic ticket may correspond to one electronic ticket URL, and the user terminal may display the single ticket type electronic ticket by accessing the one electronic ticket URL.

In one aspect of the electronic ticket management system of the present invention, the electronic ticket may be a multi-ticket type electronic ticket that includes multiple electronic tickets of the same type, and the user terminal may display a list of the multi-ticket type electronic tickets by accessing the electronic ticket URL, and the user terminal may display the at least one selected electronic ticket by selecting at least one electronic ticket from the list of multi-ticket type electronic tickets.

In one aspect of the electronic ticket management system of the present invention, the electronic ticket is a set-type electronic ticket that includes multiple electronic tickets of different types, and the user terminal may display a list of the set-type electronic tickets by accessing the electronic ticket URL, and the user terminal may display the selected at least one electronic ticket by selecting at least one electronic ticket from the list of the set-type electronic tickets.

One aspect of the present invention is an electronic ticket management server that performs authentication processing of an electronic ticket displayed on a user terminal by using a display screen and an electronic stamp of the electronic ticket when the electronic ticket is used, and that includes an electronic ticket URL issuing unit that issues an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket, and the electronic ticket URL is an abbreviated URL.

One aspect of the present invention is an electronic ticket management method that includes an authentication processing step for performing authentication processing of an electronic ticket displayed on a user terminal by using a display screen and an electronic stamp of the electronic ticket when the electronic ticket is used, and an electronic ticket URL issuing step for issuing an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket, and the electronic ticket URL is an abbreviated URL.

One aspect of the present invention is a program for causing a computer to execute an authentication processing step for performing authentication processing of an electronic ticket displayed on a user terminal by using a display screen and an electronic stamp of the electronic ticket when the electronic ticket is used, and an electronic ticket URL issuing step for issuing an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket, the electronic ticket URL being an abbreviated URL.

The present invention provides an electronic ticket management system, an electronic ticket management server, an electronic ticket management method, and a program that can improve user convenience and promote the use of electronic tickets.

1 is a diagram illustrating an example of a schematic configuration of an electronic ticket management system according to a first embodiment. 10A to 10C are diagrams for explaining an example of the transition of a display screen of a user terminal of the electronic ticket management system of the first embodiment. 2 is a diagram for explaining an example of the flow of data etc. between the user terminal, the electronic ticket sales server, and the electronic ticket management server shown in FIG. 1. 2 is a diagram for explaining an example of the flow of information displayed on the management screen of the management section of the electronic ticket management server shown in FIG. 1 . FIG. 2 is a sequence diagram for explaining an example of processing executed in the electronic ticket management system of the first embodiment. 13 is a diagram for explaining an example of the transition of a display screen of a user terminal of an electronic ticket management system of the second embodiment. FIG. 13 is a diagram for explaining an example of the transition of a display screen of a user terminal of an electronic ticket management system according to the third embodiment. FIG.

First Embodiment
Hereinafter, embodiments of an electronic ticket management system, an electronic ticket management server, an electronic ticket management method, and a program according to the present invention will be described with reference to the accompanying drawings.

FIG. 1 is a diagram showing an example of a schematic configuration of an electronic ticket management system 1 according to the first embodiment.
1, the electronic ticket management system 1 is a system that manages electronic tickets such as electronic admission tickets, electronic product (or service) vouchers, electronic discount tickets, electronic coupons, electronic product (or service) tickets, electronic coupons, etc. The electronic ticket management system 1 includes a user terminal 11, an electronic stamp 12, and a server unit 13.
The user terminal 11 is, for example, a mobile terminal such as a smartphone, or a terminal device such as a PC (personal computer). The user terminal 11 is used by, for example, a user of the electronic ticket management system 1 (for example, a person who wishes to use an electronic ticket). The user terminal 11 includes a communication unit 11A, a display unit 11B, and an input unit 11C. The communication unit 11A transmits data to the server unit 13 and receives data from the server unit 13. The display unit 11B performs display based on data received from the server unit 13, for example. The display unit 11B has a function of displaying an electronic ticket, etc. The input unit 11C accepts input operations by, for example, a user, etc. The display unit 11B and the input unit 11C are, for example, configured by a touch panel (more specifically, for example, a capacitive multi-touch touch panel).

The electronic stamp 12 is used for electronic ticket authentication and the like. The electronic stamp 12 is configured in the same manner as the stamp shown in FIG. 1 of JP 2017-215938 A. The electronic stamp 12 is placed in a facility such as a store where electronic tickets can be used. When the electronic stamp 12 is pressed down on a touch panel or the like that functions as the input unit 11C described above, the unique information of the electronic stamp 12 (for example, the information described in paragraphs 0020 and 0021 of JP 2017-215938 A (including identification information of the facility such as a store where the electronic stamp 12 is placed)) is input to the input unit 11C. When multiple electronic stamps 12 are placed in multiple facilities, each of the multiple electronic stamps 12 has unique information corresponding to each of the multiple facilities.

The server unit 13 performs authentication processing of electronic tickets, etc. The server unit 13 includes, for example, an electronic ticket sales server 13A and an electronic ticket management server 13B.
The electronic ticket sales server 13A sells electronic tickets. The electronic ticket sales server 13A is managed by, for example, a business entity that issues and sells electronic tickets. The electronic ticket sales server 13A includes, for example, a communication unit 13A1, a processing unit 13A2, and a storage unit 13A3. The communication unit 13A1 transmits data to the user terminal 11, the electronic ticket management server 13B, and receives data from the user terminal 11, the electronic ticket management server 13B, and the like. The processing unit 13A2 generates data to be transmitted to the user terminal 11, the electronic ticket management server 13B, and the like, and processes data received from the user terminal 11, the electronic ticket management server 13B, and the like. The storage unit 13A3 stores data received from the user terminal 11, the electronic ticket management server 13B, and the like, data generated by the processing unit 13A2, and processing results by the processing unit 13A2.

The electronic ticket management server 13B is a server managed by, for example, a business that performs authentication processing of electronic tickets, etc. The electronic ticket management server 13B includes, for example, a communication unit 13B1, an electronic ticket display data generation unit 13B2, an electronic ticket URL issuing unit 13B3, an authentication processing unit 13B4, a used screen display data generation unit 13B5, a management unit 13B6, an electronic ticket display restriction unit 13B7, and a storage unit 13B8.
The communication unit 13B1 transmits data to the user terminal 11, the electronic ticket sales server 13A, etc., and receives data from the user terminal 11, the electronic ticket sales server 13A, etc. The electronic ticket display data generation unit 13B2 generates electronic ticket display data, which is data for the display unit 11B of the user terminal 11 to display an electronic ticket, for example.
The electronic ticket URL issuing unit 13B3 issues an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal 11 to receive electronic ticket display data. In detail, the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 is an abbreviated URL such as that described in FIG. 3 of JP-A-2017-173924 and paragraph 0069 of JP-A-2012-174205, for example.
The authentication processing unit 13B4 performs authentication processing of the electronic ticket by using the display screen of the electronic ticket and the electronic stamp 12. The used screen display data generating unit 13B5 generates used screen display data, which is data for, for example, the display unit 11B of the user terminal 11 to display that the electronic ticket has been used.
The management unit 13B6 manages information related to the electronic ticket. The electronic ticket display restriction unit 13B7 restricts the electronic ticket from being displayed on the user terminal 11 under certain conditions. The storage unit 13B8 stores data received from the user terminal 11, the electronic ticket sales server 13A, etc., data generated by the electronic ticket display data generation unit 13B2, the used screen display data generation unit 13B5, etc., processing results by the authentication processing unit 13B4, etc.
In the example shown in FIG. 1, the electronic ticket management server 13B includes an electronic ticket display restriction unit 13B7, but in other examples, the electronic ticket management server 13B does not need to include the electronic ticket display restriction unit 13B7.

2 is a diagram for explaining an example of transition of the display screen of the user terminal 11 of the electronic ticket management system 1 of the first embodiment. In detail, FIG. 2(A) shows the display screen of the user terminal 11 when browsing an electronic ticket purchasing site (EC (Electronic Commerce) site). FIG. 2(B) shows the display screen of the user terminal 11 when purchasing an electronic ticket (coffee ticket). FIG. 2(C) shows the display screen of the user terminal 11 when the communication unit 11A of the user terminal 11 receives an email including an electronic ticket URL. FIG. 2(D) shows the display screen of the user terminal 11 when the display unit 11B of the user terminal 11 displays the electronic ticket. FIG. 2(E) shows the display screen of the user terminal 11 after the authentication process of the electronic ticket is performed by the authentication process unit 13B4 of the electronic ticket management server 13B. That is, FIG. 2(D) and FIG. 2(E) show the display screen of the user terminal 11 when the electronic ticket is used (when the electronic ticket is used at a store).
In the example shown in FIG. 2, a user (a user of the user terminal 11) purchases an electronic ticket (a coffee ticket) at an electronic ticket purchasing site, and uses the electronic ticket at a store.

Specifically, on the display screen of the user terminal 11 shown in Fig. 2(A), the display unit 11B of the user terminal 11 displays an electronic ticket purchasing site that sells electronic tickets such as "aquarium admission tickets" and "coffee tickets (cafe coffee vouchers)." When a user who wishes to purchase a "coffee ticket" taps the "cafe coffee voucher" button on the display screen of the user terminal 11, the display screen of the user terminal 11 transitions from Fig. 2(A) to Fig. 2(B).
On the display screen of user terminal 11 shown in Fig. 2(B), display unit 11B of user terminal 11 displays the amount of the "coffee ticket," the expiration date, the stores where the "coffee ticket" can be used, etc., and input unit 11C of user terminal 11 accepts input operations by the user (for example, input operation of the number of "coffee tickets" to purchase, the email address to which the tickets will be sent, credit card information, purchase confirmation operation). When a user wishing to purchase a "coffee ticket" taps the "Purchase" button on the display screen of user terminal 11, the display screen of user terminal 11 transitions from Fig. 2(B) to Fig. 2(C).

2(C), the display unit 11B of the user terminal 11 displays the electronic ticket URL "https://multicp.jp/abc1234", which is information necessary for the user terminal 11 to receive display data of the electronic ticket (coffee ticket). This electronic ticket URL was issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B. This electronic ticket URL was also included in an email sent to the user terminal 11 from the communication unit 13A1 of the electronic ticket sales server 13A and delivered to the user terminal 11.
When a user who wishes to use a "coffee ticket" taps the electronic ticket URL on the display screen of the user terminal 11, the user terminal 11 accesses the electronic ticket URL, and electronic ticket display data generated by the electronic ticket display data generation unit 13B2 of the electronic ticket management server 13B is transmitted from the electronic ticket management server 13B to the user terminal 11. As a result, as shown in Fig. 2(D), the display unit 11B of the user terminal 11 becomes able to display the electronic ticket (coffee ticket).
In detail, the electronic ticket display data generation unit 13B2 generates display data for the electronic ticket so that the display unit 11B of the user terminal 11 can display the electronic ticket whether a web browser is used or an app installed on the user terminal 11 is used.
Therefore, in the example shown in Figure 2, user convenience can be improved compared to a case in which the electronic ticket cannot be displayed on the user terminal 11 without using a web browser, or a case in which the electronic ticket cannot be displayed on the user terminal 11 without using an app installed on the user terminal 11.

In addition, the electronic ticket display restriction unit 13B7 of the electronic ticket management server 13B imposes restrictions so that the electronic ticket (coffee ticket) is not displayed on the user terminal 11 as shown in Figure 2 (D) unless a web browser or an app installed on the user terminal 11 is used to access the electronic ticket URL "https://multicp.jp/abc1234" shown in Figure 2 (C).
That is, in the example shown in Fig. 2, the web browser and one of the applications installed in the user terminal 11 (e.g., the web browser) are used to access the electronic ticket URL shown in Fig. 2(C) and to display the electronic ticket shown in Fig. 2(D). As a result, the electronic ticket display restriction unit 13B7 does not restrict the display of the electronic ticket, and the electronic ticket (coffee ticket) is displayed on the user terminal 11 as shown in Fig. 2(D).
Therefore, in the example shown in Figure 2, the risk of the electronic ticket display data generated by, for example, the electronic ticket display data generation unit 13B2 being copied and the electronic ticket being used fraudulently can be reduced more than in the case where the electronic ticket display restriction unit 13B7 is not provided.

When using the electronic ticket (coffee ticket), the user comes to the store carrying the user terminal 11 and shows the display screen of the user terminal 11 (the coffee ticket display screen) shown in FIG. 2(D) to the store staff.
The store staff presses (contacts) the electronic stamp 12 against the display screen (touch panel) of the user terminal 11. As a result, the input unit 11C of the user terminal 11 accepts an input operation using the electronic stamp 12, and information unique to the electronic stamp 12 is input to the input unit 11C. In other words, the touch panel of the user terminal 11 detects multiple contact positions (protrusion positions) of the electronic stamp 12.
The communication unit 11A of the user terminal 11 transmits the unique information of the electronic stamp 12 inputted into the input unit 11C to the electronic ticket management server 13B.
The authentication processing unit 13B4 of the electronic ticket management server 13B performs authentication processing of the electronic ticket (in detail, determines the validity and consistency of the electronic ticket and electronic stamp 12) based on the unique information of the electronic stamp 12 sent from the user terminal 11 and information about the electronic ticket (e.g., expiration date, etc.) that has been pre-stored in, for example, the memory unit 13B8 of the electronic ticket management server 13B.
If the electronic ticket and electronic stamp 12 are valid and consistent, the authentication processing unit 13B4 cancels the electronic ticket and the store staff serves the coffee to the user. In other words, if the electronic ticket and electronic stamp 12 are valid and consistent, the authentication processing unit 13B4 treats the electronic ticket as a used electronic ticket.
Specifically, when the authentication processing unit 13B4 determines that the electronic ticket and electronic stamp 12 are valid and consistent, the used screen display data generation unit 13B5 of the electronic ticket management server 13B generates used screen display data, which is data for displaying on the display screen of the user terminal 11 that the electronic ticket has been used.
The communication unit 13B1 of the electronic ticket management server 13B transmits to the user terminal 11 the used screen display data generated by the used screen display data generation unit 13B5.
The display unit 11B of the user terminal 11 displays a used electronic ticket (USED coffee ticket) indicating that the electronic ticket has been used, based on the used screen display data transmitted from the electronic ticket management server 13B.
In the display screen of the user terminal 11 shown in FIG. 2(E), the display unit 11B of the user terminal 11 displays a used electronic ticket, indicating that the electronic ticket has been used.

2, when an electronic ticket displayed on the display screen of the user terminal 11 is used, the authentication processing unit 13B4 performs authentication processing for the electronic ticket by using the electronic ticket display screen and the electronic stamp 12. An electronic ticket URL, which is information necessary for the user terminal 11 to receive display data of the electronic ticket, is issued by the electronic ticket URL issuing unit 13B3. An abbreviated URL is used as the electronic ticket URL.
Therefore, in the example shown in Figure 2, even if the display screen of the user terminal 11 is small as shown in Figure 2 (C), the user terminal 11 can display the entire electronic ticket URL (shortened URL), thereby improving user convenience and promoting the use of electronic tickets.

Also, in the example shown in Figure 2, the communication unit 13A1 of the electronic ticket sales server 13A transmits the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B to the user terminal 11 via a channel using e-mail.
The management unit 13B6 of the electronic ticket management server 13B manages that e-mail is the channel used to transmit the electronic ticket URL to the user terminal 11. The management unit 13B6 also manages, for example, as shown in Fig. 2(B), that the number of electronic tickets (coffee tickets) issued is "one", the issuance date and time of the coffee ticket, the store (facility) where the coffee ticket was used, that the number of coffee tickets used is "one", and the date and time of use of the coffee ticket.
As a result, in the example shown in FIG. 2, the effect of the channel using e-mail (for example, the effect of when, where, and how much an e-ticket is used) can be measured.

Furthermore, in the example shown in Figure 2, the authentication processing unit 13B4 of the electronic ticket management server 13B uses the electronic ticket display screen and electronic stamp 12 shown in Figure 2 (D) to determine whether the electronic ticket and electronic stamp 12 are valid and consistent, and performs a cancellation process for the electronic ticket if the electronic ticket and electronic stamp 12 are valid and consistent.
Therefore, in the example shown in FIG. 2, it is possible to prevent the risk of an electronic ticket that has already been used being used fraudulently.

In the example shown in Fig. 2, the electronic ticket (coffee ticket) purchased by the user as shown in Fig. 2(A) is a single ticket type electronic ticket. A single ticket type electronic ticket corresponds to one electronic ticket URL. In other words, one coffee ticket corresponds to one electronic ticket URL "https://multicp.jp/abc1234" as shown in Fig. 2(C).
When the user terminal 11 accesses the electronic ticket URL, electronic ticket display data corresponding to one coffee ticket is sent from the electronic ticket management server 13B to the user terminal 11, and one coffee ticket is displayed on the user terminal 11 as shown in Figure 2 (D).

In the example shown in FIG. 2, the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 is sent to the user terminal 11 via a channel using e-mail sent by the EC site.
In another example, the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 may be transmitted to the user terminal 11 via a channel using e-mail as the content of a mail magazine.
In yet another example, the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 may be transmitted to the user terminal 11 via a channel using an app (e.g., an SNS app) installed on the user terminal 11.

FIG. 3 is a diagram for explaining an example of the flow of data and the like between the user terminal 11, the electronic ticket sales server 13A, and the electronic ticket management server 13B shown in FIG.
In the example shown in Figure 3, when a user uses the user terminal 11 to purchase an electronic ticket at an electronic ticket purchasing site, information entered into the input section 11C of the user terminal 11 (electronic ticket purchase request) is transmitted from the user terminal 11 to the electronic ticket sales server 13A.
In response to an electronic ticket purchase request sent from the user terminal 11, the electronic ticket sales server 13A uses, for example, an API (Application Programming Interface) to send an electronic ticket URL issuance request to the electronic ticket management server 13B.
The electronic ticket management server 13B issues an electronic ticket URL in response to the electronic ticket URL issuance request sent from the electronic ticket sales server 13A, and transmits the electronic ticket URL to the electronic ticket sales server 13A, for example, by using an API.
The electronic ticket sales server 13A transmits the electronic ticket URL transmitted from the electronic ticket management server 13B to the user terminal 11 via e-mail or the like.
The user terminal 11 displays an e-mail containing the electronic ticket URL sent from the electronic ticket sales server 13A.

In the example shown in FIG. 2, the user uses the same user terminal 11 (smartphone) when purchasing an electronic ticket and when displaying the electronic ticket URL, but as in the example shown in FIG. 3, the user may use a PC as the user terminal 11 when purchasing an electronic ticket and a smartphone as the user terminal 11 when displaying the electronic ticket URL.

FIG. 4 is a diagram for explaining an example of the flow of information displayed on the management screen of the management unit 13B6 of the electronic ticket management server 13B shown in FIG.
In the example shown in FIG. 4, when a user purchases an electronic ticket, the user terminal 11 displays an "electronic ticket purchase screen."
Furthermore, when a user purchases an electronic ticket, the user terminal 11 transmits data requesting issuance of an electronic ticket (electronic ticket issuance request data) to the server unit 13, and the electronic ticket management server 13B of the server unit 13 transmits an email or the like including an electronic ticket URL to the user terminal 11 via the electronic ticket sales server 13A of the server unit 13. The electronic ticket issuance request is made using an API.
When using the electronic ticket, the user comes to the store carrying the user terminal 11 and shows the display screen of the user terminal 11 (the display screen of the "drink exchange ticket") to the store staff.
When a store staff member touches the electronic stamp 12 (see FIG. 2) to the display screen of the user terminal 11 , the unique information of the electronic stamp 12 is detected by the user terminal 11 .
The user terminal 11 transmits the unique information of the electronic stamp 12 to the electronic ticket management server 13B of the server unit 13, and the electronic ticket management server 13B performs authentication processing and cancellation processing of the electronic ticket.
The electronic ticket management server 13B transmits used screen display data to the user terminal 11 for displaying on the display screen of the user terminal 11 that the electronic ticket has been used, and the user terminal 11 displays a used electronic ticket "USED drink voucher" indicating that the electronic ticket has been used.
The management unit 13B6 of the electronic ticket management server 13B manages information related to electronic tickets (specifically, for example, product (or service) registration/sales management/reports/e-ticket issuance/usage history confirmation, etc.). For example, a business operator who issues and sells electronic tickets can use a display screen (management screen) to view information managed by the management unit 13B6 (for example, sales status and usage status of electronic tickets). The management unit 13B6 also has a function of extracting managed information. The management unit 13B6 can generate, for example, reports by product sold, reports by store, reports by channel, store reports by product sold and used, product reports by channel, and balance summary reports (reports by product sold of unused balances against the issued amount of electronic tickets), and display them on the management screen.

FIG. 5 is a sequence diagram for explaining an example of a process executed in the electronic ticket management system 1 of the first embodiment.
In the example shown in FIG. 5, first, a process for registering a product for which an electronic ticket can be used is carried out.
Specifically, in step S10, the electronic ticket management server 13B registers the product.
In step S11, the electronic ticket management server 13B transmits information about the product registered in step S10 to the electronic ticket sales server 13A.
In step S12, the electronic ticket sales server 13A stores and manages the product information transmitted in step S11.

Next, processing related to the issuance and distribution of the electronic ticket is carried out.
Specifically, in step S13, the user terminal 11 requests product information from the electronic ticket sales server 13A in response to, for example, an input operation by the user (for example, the user terminal 11 accesses an EC site).
In step S14, the electronic ticket sales server 13A transmits product information to the user terminal 11.
In step S15, the user terminal 11 displays information about the product (for example, the user terminal 11 displays the information shown in FIG. 2A).
In step S16, the user terminal 11 requests electronic ticket purchase screen data in response to, for example, an input operation by the user.
In step S<b>17 , the electronic ticket sales server 13</b>A transmits electronic ticket purchase screen data to the user terminal 11 .
In step S18, the user terminal 11 displays an electronic ticket purchase screen (for example, the screen shown in FIG. 2(B)).
In step S19, the user terminal 11 transmits data requesting the purchase of a product to the electronic ticket sales server 13A in response to, for example, an input operation by the user.
In step S20, the electronic ticket sales server 13A requests the electronic ticket management server 13B to issue an electronic ticket. More specifically, the electronic ticket sales server 13A requests the electronic ticket URL from the electronic ticket management server 13B.
In step S21, the electronic ticket management server 13B issues an electronic ticket URL.
In step S22, the electronic ticket management server 13B transmits the electronic ticket URL to the electronic ticket sales server 13A.
In step S23, the electronic ticket sales server 13A sends an email or the like including the electronic ticket URL to the user terminal 11.
In step S24, the user terminal 11 displays an e-mail containing the electronic ticket URL (for example, the screen shown in FIG. 2C).

Processing for use of the electronic ticket then takes place.
Specifically, in step S25, the user terminal 11 accesses the electronic ticket URL in response to, for example, an input operation by the user (for example, a tap operation on the electronic ticket URL).
In step S26, the electronic ticket management server 13B generates electronic ticket display data.
In step S27, the electronic ticket management server 13B transmits electronic ticket display data to the user terminal 11.
In step S28, the user terminal 11 displays the single-ticket electronic ticket based on the electronic ticket display data transmitted from the electronic ticket management server 13 B. In detail, the user terminal 11 displays, for example, a screen shown in FIG. 2D in response to, for example, an input operation by the user.
In step S29, the user terminal 11, which is presented to a store staff member by the user, for example, accepts input of information unique to the electronic stamp 12. In detail, the electronic stamp 12 is affixed to the user terminal 11 by the store staff member, for example.
In step S30, the user terminal 11 transmits information unique to the electronic stamp 12 and the like to the electronic ticket management server 13B.
In step S31, the electronic ticket management server 13B performs authentication processing of the electronic ticket based on the unique information of the electronic stamp 12 and the like.
In step S32, the electronic ticket management server 13B generates used screen display data for displaying on the display screen of the user terminal 11 a message indicating that the electronic ticket has been used.
In step S33, the electronic ticket management server 13B transmits the used screen display data to the user terminal 11.
In step S34, the user terminal 11 displays a used screen (for example, the screen shown in FIG. 2(E)) based on the used screen display data.

As described above, in the electronic ticket management system 1 of the first embodiment, the electronic stamp 12 is used for the authentication process of the electronic ticket, so that the store does not need to modify its system. As a result, costs can be significantly reduced compared to when a reader or the like is installed in the store.
Furthermore, the authentication process for electronic tickets using the electronic stamp 12 is intuitive and easy for users to understand, and is an analog, enjoyable experience, which promotes the use of electronic tickets and increases the ability of stores to attract customers.
Since the unique information of the electronic stamp 12 can be generated in more than millions of different ways, authentication processing of the electronic ticket can be performed with high security.
Because electronic tickets are used instead of paper tickets, the effort required for ticket management (e.g., inventory management), collection, and tallying at ticket issuing and selling businesses and stores can be significantly reduced. Moreover, all management of electronic ticket information can be performed in the server unit 13. Furthermore, the risk of tickets that have passed their expiration date being used by mistake can be reduced. Furthermore, compared to when paper tickets are used, the burden on users to store tickets and the burden on users to bring tickets to stores can be reduced, improving user satisfaction. Furthermore, the cost of sending tickets to users can be significantly reduced compared to when paper tickets are mailed.

Second Embodiment
A second embodiment of the electronic ticket management system, the electronic ticket management server, the electronic ticket management method, and the program according to the present invention will be described below.
The electronic ticket management system 1 of the second embodiment is configured similarly to the electronic ticket management system 1 of the first embodiment described above, except for the points described below. Therefore, the electronic ticket management system 1 of the second embodiment can achieve the same effects as the electronic ticket management system 1 of the first embodiment described above, except for the points described below.

As described above, in the electronic ticket management system 1 of the first embodiment, the electronic ticket purchased by the user is a single ticket type electronic ticket, and the single ticket type electronic ticket corresponds to one electronic ticket URL. That is, one coffee ticket corresponds to one electronic ticket URL "https://multicp.jp/abc1234" shown in Fig. 2(C). When the user terminal 11 accesses the electronic ticket URL, for example, electronic ticket display data corresponding to one coffee ticket is transmitted from the electronic ticket management server 13B to the user terminal 11, and for example, one coffee ticket is displayed on the user terminal 11 as shown in Fig. 2(D).
On the other hand, in the electronic ticket management system 1 of the second embodiment, the electronic ticket purchased by the user is a coupon-type electronic ticket that includes a plurality of electronic tickets of the same type.

Fig. 6 is a diagram for explaining an example of the transition of the display screen of the user terminal 11 of the electronic ticket management system 1 of the second embodiment. In detail, Fig. 6(A) shows the display screen of the user terminal 11 when the communication unit 11A of the user terminal 11 receives an email including an electronic ticket URL. Fig. 6(B) shows the display screen of the user terminal 11 after the user terminal 11 has transitioned by accessing the electronic ticket URL. Fig. 6(C) shows the display screen of the user terminal 11 when the display unit 11B of the user terminal 11 displays one electronic ticket out of a coupon-type electronic ticket including multiple electronic tickets of the same type.
In the example shown in Figure 6, a user (a user of user terminal 11) purchases a multiple-use electronic ticket (a multiple-use electronic ticket including multiple beer tickets) from, for example, an electronic ticket purchasing site, and uses one of the multiple beer tickets at a store.

Specifically, in the display screen of the user terminal 11 shown in Fig. 6(A), the display unit 11B of the user terminal 11 displays an electronic ticket URL "https://multicp.jp/beer/abc1234" which is information necessary for the user terminal 11 to receive display data of a list of coupon-type electronic tickets including multiple beer tickets. This electronic ticket URL is issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B. In addition, this electronic ticket URL is delivered to the user terminal 11, for example, by being included in an e-mail sent from the communication unit 13A1 of the electronic ticket sales server 13A to the user terminal 11.
When a user who wishes to use a "beer ticket" taps the electronic ticket URL on the display screen of the user terminal 11, the user terminal 11 accesses the electronic ticket URL. Display data of a list of multi-ticket type electronic tickets including multiple beer tickets, generated by the electronic ticket display data generation unit 13B2 of the electronic ticket management server 13B, is transmitted from the electronic ticket management server 13B to the user terminal 11. Furthermore, as shown in Fig. 6(B), the display unit 11B of the user terminal 11 displays a list of multi-ticket type electronic tickets including multiple beer tickets.
In the example shown in Figure 6 (B), one of the multiple beer tickets is in a used state, but when the display unit 11B of the user terminal 11 first displays a list of the multiple-use ticket type electronic ticket, all of the multiple beer tickets are displayed in an unused state.
In addition, the electronic ticket display data generation unit 13B2 generates display data for a list of multiple-use ticket type electronic tickets so that the display unit 11B of the user terminal 11 can display a list of multiple-use ticket type electronic tickets, whether a web browser is used or an app installed on the user terminal 11 is used.
Therefore, in the example shown in Figure 6, user convenience can be improved compared to a case in which a list of multi-ride electronic tickets cannot be displayed on the user terminal 11 without using a web browser, or a case in which a list of multi-ride electronic tickets cannot be displayed on the user terminal 11 without using an app installed on the user terminal 11.

When a user who wishes to use a "beer ticket" selects (e.g. taps) one electronic ticket (more specifically, an unused beer ticket) from the list of coupon-type electronic tickets on the display screen of the user terminal 11, the user terminal 11 accesses the electronic ticket management server 13B, and electronic ticket display data generated by the electronic ticket display data generation unit 13B2 of the electronic ticket management server 13B is transmitted from the electronic ticket management server 13B to the user terminal 11. As a result, as shown in Fig. 6(C), the display unit 11B of the user terminal 11 becomes able to display the selected one electronic ticket (unused beer ticket).
In addition, the electronic ticket display restriction unit 13B7 of the electronic ticket management server 13B imposes restrictions so that the electronic ticket (beer ticket) will not be displayed on the user terminal 11 as shown in Figure 6 (C) unless a web browser or an app installed on the user terminal 11 is used to access the electronic ticket URL "https://multicp.jp/beer/abc1234" shown in Figure 6 (A).
That is, in the example shown in Fig. 6, the web browser and one of the applications installed in the user terminal 11 (e.g., the web browser) are used to access the electronic ticket URL shown in Fig. 6(A) and to display the electronic ticket (beer ticket) shown in Fig. 6(C). As a result, the electronic ticket display restriction unit 13B7 does not restrict the display of the electronic ticket, and the electronic ticket (beer ticket) is displayed on the user terminal 11 as shown in Fig. 6(C).
Therefore, in the example shown in Figure 6, the risk of electronic ticket display data generated by, for example, the electronic ticket display data generation unit 13B2 being copied and electronic tickets (beer tickets) being used fraudulently can be reduced more than in the case where the electronic ticket display restriction unit 13B7 is not provided.

When using the electronic ticket (beer ticket), the user comes to the store carrying the user terminal 11 and shows the display screen of the user terminal 11 (beer ticket display screen) shown in FIG. 6(C) to the store staff.
The store staff presses (contacts) the electronic stamp 12 against the display screen (touch panel) of the user terminal 11. As a result, the input unit 11C of the user terminal 11 accepts an input operation using the electronic stamp 12, and information unique to the electronic stamp 12 is input to the input unit 11C.
The authentication processing unit 13B4 of the electronic ticket management server 13B performs authentication processing of the electronic ticket (in detail, determines the validity and consistency of the electronic ticket and electronic stamp 12) based on the unique information of the electronic stamp 12 sent from the user terminal 11 and information about the electronic ticket (beer ticket) (e.g., expiration date) that has been pre-stored in the memory unit 13B8 of the electronic ticket management server 13B.
If the electronic ticket and electronic stamp 12 are found to be valid and consistent, the authentication processing unit 13B4 performs a cancellation process for the electronic ticket (beer ticket), and the store staff provides the user with beer.
Specifically, when the authentication processing unit 13B4 determines that the electronic ticket (beer ticket) and electronic stamp 12 are valid and consistent, the used screen display data generation unit 13B5 of the electronic ticket management server 13B generates used screen display data, which is data for displaying on the display screen of the user terminal 11 that the electronic ticket (beer ticket) has been used.
The display unit 11B of the user terminal 11 displays a used electronic ticket (not shown) indicating that the electronic ticket (beer ticket) has been used, based on the used screen display data transmitted from the electronic ticket management server 13B.

6, when an electronic ticket (beer ticket) displayed on the display screen of the user terminal 11 is used, the authentication processing unit 13B4 performs authentication processing for the electronic ticket by using the display screen of the electronic ticket and the electronic stamp 12. An electronic ticket URL, which is information necessary for the user terminal 11 to receive display data of a list of multi-ticket type electronic tickets, is issued by the electronic ticket URL issuing unit 13B3. A shortened URL is used as the electronic ticket URL.
Therefore, in the example shown in Figure 6, even if the display screen of the user terminal 11 is small as shown in Figure 6 (A), the user terminal 11 can display the entire electronic ticket URL (shortened URL), thereby improving user convenience and promoting the use of electronic tickets (beer tickets).

Also, in the example shown in Figure 6, the communication unit 13A1 of the electronic ticket sales server 13A transmits the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B to the user terminal 11 via a channel using e-mail.
The management unit 13B6 of the electronic ticket management server 13B manages that the channel used to transmit the electronic ticket URL to the user terminal 11 is email. The management unit 13B6 also manages, for example, that the number of issued multi-ticket electronic tickets is one copy, the issue date and time of the multi-ticket electronic ticket, the store (facility) where each beer ticket included in the multi-ticket electronic ticket was used, the number of times multiple beer tickets included in the multi-ticket electronic ticket were used, and the date and time when each beer ticket included in the multi-ticket electronic ticket was used.
As a result, in the example shown in FIG. 6, the effect of the channel using e-mail (for example, the effect of when, where, and how much an e-ticket is used) can be measured.

Furthermore, in the example shown in Figure 6, the authentication processing unit 13B4 of the electronic ticket management server 13B uses the beer ticket display screen and electronic stamp 12 shown in Figure 6 (C) to determine whether the beer ticket and electronic stamp 12 are valid and consistent, and performs a cancellation process for the beer ticket.
Therefore, in the example shown in FIG. 6, the risk of fraudulent use of used beer tickets can be reduced.
In addition, when the beer ticket cancellation process is performed, as shown in FIG. 6(B), the used beer tickets among the multiple beer tickets included in the list of the multiple-ticket type electronic ticket are displayed in a used state as "USED."
Therefore, in the example shown in Figure 6, the user can easily grasp the number of used beer tickets and the number of unused beer tickets among the multiple beer tickets included in the list of the multiple-use ticket type electronic ticket.

In addition, in the example shown in Figure 6, the electronic ticket (beer ticket) purchased by the user is a multiple-use ticket type electronic ticket, and when the user terminal 11 accesses the electronic ticket URL, a list of multiple-use ticket type electronic tickets is displayed on the user terminal 11.
Therefore, if the user remembers one electronic ticket URL, the user can display a list of the coupon-type electronic tickets on the user terminal 11. In other words, the user does not need to remember the URLs corresponding to all the beer tickets.
Therefore, in the example shown in FIG. 6, it is possible to improve convenience for users and promote the use of multi-ticket type electronic tickets.
In the example shown in Fig. 6, a user (user of the user terminal 11) uses one of a plurality of beer tickets at a store, but in other examples, a user may use two or more of a plurality of beer tickets at the store at the same time. In this example, a user who wishes to use a "beer ticket" selects (e.g., taps) two or more electronic tickets (more specifically, unused beer tickets) from a list of coupon-type electronic tickets on the display screen of the user terminal 11. As a result, the two or more selected electronic tickets (unused beer tickets) are displayed on the user terminal 11, as in the example shown in Fig. 6 (C).
In this example, the store staff stamps (contacts) the electronic stamp 12 on each of the two or more electronic tickets (unused beer tickets) displayed on the display screen (touch panel) of the user terminal 11. If the authentication processing unit 13B4 determines that the electronic tickets (beer tickets) and the electronic stamp 12 are valid and consistent, two or more used electronic tickets indicating that two or more electronic tickets (beer tickets) have been used are displayed on the user terminal 11.

Third Embodiment
A third embodiment of the electronic ticket management system, the electronic ticket management server, the electronic ticket management method, and the program according to the present invention will be described below.
The electronic ticket management system 1 of the third embodiment is configured similarly to the electronic ticket management system 1 of the first embodiment described above, except for the points described below. Therefore, the electronic ticket management system 1 of the third embodiment can achieve the same effects as the electronic ticket management system 1 of the first embodiment described above, except for the points described below.

In the electronic ticket management system 1 of the third embodiment, the electronic ticket purchased by the user is a set-type electronic ticket that includes multiple electronic tickets of different types.

Fig. 7 is a diagram for explaining an example of transition of the display screen of the user terminal 11 of the electronic ticket management system 1 of the third embodiment. In detail, Fig. 7(A) shows the display screen of the user terminal 11 when the communication unit 11A of the user terminal 11 receives an email including an electronic ticket URL. Fig. 7(B) shows the display screen of the user terminal 11 after the user terminal 11 has transitioned by accessing the electronic ticket URL. Fig. 7(C) shows the display screen of the user terminal 11 when the display unit 11B of the user terminal 11 displays one electronic ticket out of a set-type electronic ticket including multiple electronic tickets of different types.
In the example shown in Figure 7, a user (a user of user terminal 11) purchases a set-type electronic ticket (a set-type electronic ticket including a dessert ticket, a drink ticket, and a potato ticket) from, for example, an electronic ticket purchasing site, and uses the potato ticket at a store.

Specifically, on the display screen of the user terminal 11 shown in Fig. 7(A), the display unit 11B of the user terminal 11 displays an electronic ticket URL "https://multicp.jp/set/abc1234" which is information necessary for the user terminal 11 to receive display data of a list of set-ticket-type electronic tickets including a dessert ticket, a drink ticket, and a potato ticket. This electronic ticket URL is issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B. In addition, this electronic ticket URL is delivered to the user terminal 11, for example, by being included in an e-mail sent from the communication unit 13A1 of the electronic ticket sales server 13A to the user terminal 11.
For example, when a user who wishes to use a "potato ticket" taps the electronic ticket URL on the display screen of the user terminal 11, the user terminal 11 accesses the electronic ticket URL. Also, display data of a list of set ticket-type electronic tickets including a dessert ticket, a drink ticket, and a potato ticket, generated by the electronic ticket display data generation unit 13B2 of the electronic ticket management server 13B, is transmitted from the electronic ticket management server 13B to the user terminal 11. Furthermore, as shown in Fig. 7(B), the display unit 11B of the user terminal 11 displays a list of set ticket-type electronic tickets including a dessert ticket, a drink ticket, and a potato ticket.
In addition, the electronic ticket display data generation unit 13B2 generates display data for a list of set ticket-type electronic tickets so that the display unit 11B of the user terminal 11 can display a list of set ticket-type electronic tickets, whether a web browser is used or an app installed on the user terminal 11 is used.
Therefore, in the example shown in Figure 7, user convenience can be improved compared to a case in which a list of set ticket-type electronic tickets cannot be displayed on the user terminal 11 without using a web browser, or a case in which a list of set ticket-type electronic tickets cannot be displayed on the user terminal 11 without using an app installed on the user terminal 11.

When a user who wishes to use a "potato ticket" selects (e.g., taps) one electronic ticket (more specifically, an unused potato ticket) from the list of set ticket-type electronic tickets on the display screen of the user terminal 11, the user terminal 11 accesses the electronic ticket management server 13B, and electronic ticket display data generated by the electronic ticket display data generation unit 13B2 of the electronic ticket management server 13B is transmitted from the electronic ticket management server 13B to the user terminal 11. As a result, as shown in Fig. 7(C), the display unit 11B of the user terminal 11 becomes able to display the selected one electronic ticket (unused potato ticket).
In addition, the electronic ticket display restriction unit 13B7 of the electronic ticket management server 13B imposes restrictions so that the electronic ticket (potato ticket) is not displayed on the user terminal 11 as shown in Figure 7 (C) unless a web browser or an app installed on the user terminal 11 is used to access the electronic ticket URL "https://multicp.jp/set/abc1234" shown in Figure 7 (A).
That is, in the example shown in Fig. 7, the web browser and one of the applications installed in the user terminal 11 (e.g., the web browser) are used to access the electronic ticket URL shown in Fig. 7(A) and to display the electronic ticket (potato ticket) shown in Fig. 7(C). As a result, the electronic ticket display restriction unit 13B7 does not restrict the display of the electronic ticket, and the electronic ticket (potato ticket) is displayed on the user terminal 11 as shown in Fig. 7(C).
Therefore, in the example shown in Figure 7, the risk of electronic ticket display data generated by, for example, the electronic ticket display data generation unit 13B2 being copied and electronic tickets (potato tickets) being used fraudulently can be reduced more than in the case where the electronic ticket display restriction unit 13B7 is not provided.

When using the electronic ticket (potato ticket), the user comes to the store carrying the user terminal 11 and shows the display screen of the user terminal 11 (the potato ticket display screen) shown in Figure 7 (C) to the store staff.
The store staff presses (contacts) the electronic stamp 12 against the display screen (touch panel) of the user terminal 11. As a result, the input unit 11C of the user terminal 11 accepts an input operation using the electronic stamp 12, and information unique to the electronic stamp 12 is input to the input unit 11C.
The authentication processing unit 13B4 of the electronic ticket management server 13B performs authentication processing of the electronic ticket (in detail, determines the validity and consistency of the electronic ticket and electronic stamp 12) based on the unique information of the electronic stamp 12 sent from the user terminal 11 and information (e.g., expiration date) about the electronic ticket (potato ticket) that has been pre-stored in the memory unit 13B8 of the electronic ticket management server 13B.
If the electronic ticket and electronic stamp 12 are found to be valid and consistent, the authentication processing unit 13B4 performs a cancellation process for the electronic ticket (potato voucher), and the store staff provides the potato voucher to the user.
Specifically, when the authentication processing unit 13B4 determines that the electronic ticket (potato ticket) and electronic stamp 12 are valid and consistent, the used screen display data generation unit 13B5 of the electronic ticket management server 13B generates used screen display data, which is data for displaying on the display screen of the user terminal 11 that the electronic ticket (potato ticket) has been used.
The display unit 11B of the user terminal 11 displays a used electronic ticket (not shown) indicating that the electronic ticket (potato ticket) has been used, based on the used screen display data transmitted from the electronic ticket management server 13B.

7, when an electronic ticket (potato ticket) displayed on the display screen of the user terminal 11 is used, the authentication processing unit 13B4 performs authentication processing for the electronic ticket by using the electronic ticket display screen and the electronic stamp 12. An electronic ticket URL, which is information necessary for the user terminal 11 to receive display data of a list of set ticket-type electronic tickets, is issued by the electronic ticket URL issuing unit 13B3. An abbreviated URL is used as the electronic ticket URL.
Therefore, in the example shown in Figure 7, even if the display screen of the user terminal 11 is small as shown in Figure 7 (A), the user terminal 11 can display the entire electronic ticket URL (shortened URL), thereby improving user convenience and promoting the use of electronic tickets (potato tickets).

Also, in the example shown in Figure 7, the communication unit 13A1 of the electronic ticket sales server 13A transmits the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B to the user terminal 11 via a channel using e-mail.
The management unit 13B6 of the electronic ticket management server 13B manages that e-mail is the channel used to transmit the electronic ticket URL to the user terminal 11. The management unit 13B6 also manages, for example, that only one set of electronic tickets has been issued, the issue date and time of the set electronic ticket, the store (facility) where the dessert ticket, drink ticket, and potato ticket included in the set electronic ticket were used, the number of times the electronic tickets out of the dessert ticket, drink ticket, and potato ticket included in the set electronic ticket were used, and the date and time when the dessert ticket, drink ticket, and potato ticket included in the set electronic ticket were used.
As a result, in the example shown in FIG. 7, the effect of the channel using e-mail (for example, the effect of when, where, and how much an e-ticket is used) can be measured.

Furthermore, in the example shown in Figure 7, the authentication processing unit 13B4 of the electronic ticket management server 13B uses the potato ticket display screen and electronic stamp 12 shown in Figure 7 (C) to determine whether the potato ticket and electronic stamp 12 are valid and consistent, and if the potato ticket and electronic stamp 12 are valid and consistent, it performs a cancellation process for the potato ticket.
Therefore, in the example shown in Figure 7, the risk of fraudulent use of used potato coupons can be reduced.
In addition, when the process of canceling a potato voucher is performed, the potato voucher that has been used among the dessert voucher, drink voucher and potato voucher included in the list of the set ticket type electronic ticket is displayed as being in a used state.
Therefore, in the example shown in Figure 7, a user can easily distinguish between used potato vouchers and unused dessert vouchers and drink vouchers among the dessert vouchers, drink vouchers and potato vouchers included in the list of set-type electronic tickets.

In addition, in the example shown in Figure 7, the electronic ticket purchased by the user is a set-type electronic ticket, and when the user terminal 11 accesses the electronic ticket URL, a list of set-type electronic tickets is displayed on the user terminal 11.
Therefore, if the user remembers one electronic ticket URL, the user can display a list of set-type electronic tickets on the user terminal 11. In other words, the user does not need to remember the URLs corresponding to each of the dessert ticket, drink ticket, and potato ticket.
Therefore, in the example shown in FIG. 7, it is possible to improve convenience for the user and promote the use of set-type electronic tickets.
In the example shown in FIG. 7, a user (a user of the user terminal 11) uses a potato voucher of a set ticket-type electronic ticket (a set ticket-type electronic ticket including a dessert voucher, a drink voucher, and a potato voucher) at a store, but in other examples, a user may use two or more electronic tickets (e.g., a drink voucher and a potato voucher) of the set ticket-type electronic tickets at the store at the same time. In this example, a user who wishes to use, for example, a "drink ticket" and a "potato voucher" selects (e.g., taps) two electronic tickets (more specifically, the unused "drink ticket" and "potato voucher") from a list of set ticket-type electronic tickets on the display screen of the user terminal 11. As a result, the selected two electronic tickets (the unused "drink ticket" and "potato voucher") are displayed on the user terminal 11, as in the example shown in FIG. 7(C).
Also, in this example, the store staff stamps (contacts) the electronic stamp 12 onto each of two or more electronic tickets (e.g., unused "drink ticket" and "fry ticket") displayed on the display screen (touch panel) of the user terminal 11. If the authentication processing unit 13B4 determines that the electronic tickets (e.g., "drink ticket" and "fry ticket") and the electronic stamp 12 are valid and consistent, two or more used electronic tickets indicating that two or more electronic tickets (e.g., "drink ticket" and "fry ticket") have been used are displayed on the user terminal 11.

Fourth Embodiment
A fourth embodiment of the electronic ticket management system, the electronic ticket management server, the electronic ticket management method, and the program according to the present invention will now be described.
The electronic ticket management system 1 of the fourth embodiment is configured similarly to the electronic ticket management system 1 of the first embodiment described above, except for the points described below. Therefore, the electronic ticket management system 1 of the fourth embodiment can achieve the same effects as the electronic ticket management system 1 of the first embodiment described above, except for the points described below.

As described above, in the electronic ticket management system 1 of the first embodiment, the communication unit 13A1 of the electronic ticket sales server 13A transmits the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B to the user terminal 11 via a channel using e-mail.
On the other hand, in an example of the electronic ticket management system 1 of the fourth embodiment, the communication unit 13A1 of the electronic ticket sales server 13A can transmit the electronic ticket URL issued by the electronic ticket URL issuing unit 13B3 of the electronic ticket management server 13B to the user terminal 11 via a channel using e-mail, and can also transmit the electronic ticket URL to the user terminal 11 via a channel using, for example, an app (e.g., an SNS app) installed on the user terminal 11.
The management unit 13B6 of the electronic ticket management server 13B manages the number of issued electronic tickets sent to the user terminal 11 via a channel using email, the issue date and time of the electronic tickets, the store (facility) where the electronic ticket was used, the number of uses of the electronic ticket, the date and time of use of the electronic ticket, etc. Furthermore, the management unit 13B6 also manages the number of issued electronic tickets sent to the user terminal 11 via a channel using, for example, an app installed on the user terminal 11, the issue date and time of the electronic tickets, the store (facility) where the electronic ticket was used, the number of uses of the electronic ticket, the date and time of use of the electronic ticket, etc.
As a result, in an example of the electronic ticket management system 1 of the fourth embodiment, the effectiveness of a channel using e-mail (e.g., the effectiveness of when, where, and how much an electronic ticket was used) can be measured and compared with the effectiveness of a channel using an app installed on the user terminal 11.

As described above, in the electronic ticket management system 1 of the first embodiment, single-ticket electronic tickets are sold via a channel using e-mail, for example. In the electronic ticket management system 1 of the second embodiment, multi-ticket electronic tickets are sold via a channel using e-mail, for example.
On the other hand, in another example of the electronic ticket management system 1 of the fourth embodiment, single-ticket type electronic tickets are sold via a channel using e-mail, and multiple-ticket type electronic tickets or set-ticket type electronic tickets are also sold via a channel using an app installed on, for example, a user terminal 11.
In another example of the electronic ticket management system 1 of the fourth embodiment, the number of issued single ticket electronic tickets sold via a channel using e-mail, the issue date and time of the single ticket electronic tickets, the store (facility) where the single ticket electronic tickets were used, the number of uses of the single ticket electronic tickets, the use date and time of the single ticket electronic tickets, etc. Furthermore, for example, the number of issued multi-ticket electronic tickets or set ticket electronic tickets sold via a channel using an application installed on the user terminal 11, the issue date and time of the multi-ticket electronic tickets or set ticket electronic tickets, the store (facility) where the multi-ticket electronic tickets or each electronic ticket included in the set ticket electronic tickets were used, the number of uses of each electronic ticket included in the multi-ticket electronic tickets or set ticket electronic tickets, the use date and time of each electronic ticket included in the multi-ticket electronic tickets or set ticket electronic tickets, etc. are managed.
As a result, in another example of the electronic ticket management system 1 of the fourth embodiment, it is possible to measure and compare the effectiveness of a channel using e-mail with the effectiveness of a channel using an application installed on the user terminal 11, and it is also possible to measure and compare the effectiveness of a single-ticket type electronic ticket with the effectiveness of a multiple-ticket type electronic ticket or a set-ticket type electronic ticket.

Although the above describes the form for carrying out the present invention using the embodiments, the present invention is not limited to these embodiments in any way, and various modifications and substitutions can be made without departing from the scope of the present invention. The configurations described in the above-mentioned embodiments and examples may be combined as appropriate.

In addition, all or part of the functions of each unit of the electronic ticket management system 1 in the above-mentioned embodiment may be realized by recording a program for realizing these functions on a computer-readable recording medium, and having a computer system read and execute the program recorded on the recording medium. Note that the "computer system" here includes hardware such as the OS and peripheral devices.
Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage units such as hard disks built into computer systems. Furthermore, "computer-readable recording medium" may also include those that dynamically hold a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in such cases. Furthermore, the above program may be one that realizes part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

1...Electronic ticket management system, 11...User terminal, 11A...Communication unit, 11B...Display unit, 11C...Input unit, 12...Electronic stamp, 13...Server unit, 13A...Electronic ticket sales server, 13A1...Communication unit, 13A2...Processing unit, 13A3...Storage unit, 13B...Electronic ticket management server, 13B1...Communication unit, 13B2...Electronic ticket display data generation unit, 13B3...Electronic ticket URL issuing unit, 13B4...Authentication processing unit, 13B5...Used screen display data generation unit, 13B6...Management unit, 13B7...Electronic ticket display restriction unit, 13B8...Storage unit

Claims (10)

The system comprises a user terminal, an electronic stamp, and a server unit,
an electronic ticket management system that performs authentication processing of an electronic ticket by using a display screen of the electronic ticket and the electronic stamp when the electronic ticket displayed on the user terminal is used,
The server unit is
an electronic ticket display data generation unit that generates display data for the electronic ticket;
an electronic ticket URL issuing unit that issues an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket;
An electronic ticket display restriction unit;
the electronic ticket display data generation unit generates display data of the electronic ticket so that the user terminal can display the electronic ticket in both cases where the user terminal uses a web browser and where the user terminal uses an application installed in the user terminal;
the electronic ticket URL issuing unit issues a shortened URL as the electronic ticket URL that enables the user terminal to display the entire electronic ticket URL, both when the user terminal uses a web browser and when the user terminal uses an application installed in the user terminal ;
The electronic ticket display restriction unit restricts the electronic ticket from being displayed on the user terminal unless the web browser or one of the applications installed on the user terminal that was used to access the shortened URL is used.
Electronic ticket management system. The server unit is
an electronic ticket management server including the electronic ticket URL issuing unit;
an electronic ticket sales server that sells the electronic tickets;
the electronic ticket sales server includes a communication unit that transmits the electronic ticket URL issued by the electronic ticket URL issuing unit to the user terminal via at least a first channel using email and a second channel using an application installed on the user terminal;
The electronic ticket management system according to claim 1 . The electronic ticket management server
a management unit that manages at least one of the channel used to transmit the electronic ticket URL to the user terminal, the number of issued electronic tickets, the issue date and time of the electronic ticket, the facility at which the electronic ticket was used, the number of times the electronic ticket was used, and the date and time of use of the electronic ticket;
The electronic ticket management system according to claim 2 . the server unit includes an authentication processing unit that performs authentication processing of the electronic ticket,
the authentication processing unit performs a canceling process for the electronic ticket by using a display screen of the electronic ticket and the electronic stamp.
The electronic ticket management system according to claim 1 . the electronic ticket is a single ticket electronic ticket,
The single-ticket electronic ticket corresponds to one electronic ticket URL,
The user terminal displays the single ticket type electronic ticket by accessing the one electronic ticket URL.
The electronic ticket management system according to claim 1 . the electronic ticket is a coupon-type electronic ticket including multiple electronic tickets of the same type,
By accessing the electronic ticket URL, the user terminal displays a list of the multi-ticket type electronic tickets;
by selecting at least one electronic ticket from the list of the multi-ticket type electronic tickets, the user terminal displays the selected at least one electronic ticket.
The electronic ticket management system according to claim 1 . the electronic ticket is a set electronic ticket including a plurality of electronic tickets of different types,
By accessing the electronic ticket URL, the user terminal displays a list of the set electronic tickets;
by selecting at least one electronic ticket from the list of set-type electronic tickets, the user terminal displays the selected at least one electronic ticket;
The electronic ticket management system according to claim 1 . An electronic ticket management server that performs authentication processing of an electronic ticket by using a display screen of the electronic ticket and an electronic stamp when an electronic ticket displayed on a user terminal is used,
an electronic ticket display data generation unit that generates display data for the electronic ticket;
an electronic ticket URL issuing unit that issues an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket;
An electronic ticket display restriction unit;
the electronic ticket display data generation unit generates display data of the electronic ticket so that the user terminal can display the electronic ticket in both cases where the user terminal uses a web browser and where the user terminal uses an application installed in the user terminal;
the electronic ticket URL issuing unit issues a shortened URL as the electronic ticket URL that enables the user terminal to display the entire electronic ticket URL, both when the user terminal uses a web browser and when the user terminal uses an application installed in the user terminal ;
the electronic ticket display restriction unit restricts the electronic ticket from being displayed on the user terminal unless the web browser or an application installed on the user terminal is used to access the short URL;
Electronic ticket management server. an authentication processing step in which the server unit performs authentication processing of the electronic ticket by using a display screen and an electronic stamp of the electronic ticket when the electronic ticket displayed on the user terminal is used;
a step of the server unit generating display data of the electronic ticket;
an electronic ticket URL issuing step of the server unit issuing an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket;
The server unit includes an electronic ticket display restriction step,
the step of generating display data for the electronic ticket includes generating display data for the electronic ticket so that the user terminal can display the electronic ticket in both cases where the user terminal uses a web browser and where the user terminal uses an application installed on the user terminal;
the electronic ticket URL issuing step includes issuing a shortened URL as the electronic ticket URL that enables the user terminal to display the entire electronic ticket URL, both in a case where the user terminal uses a web browser and in a case where the user terminal uses an application installed in the user terminal ;
the electronic ticket display restriction step restricts the electronic ticket from being displayed on the user terminal unless the web browser or an application installed on the user terminal is used to access the short URL;
How to manage your electronic tickets. On the computer,
an authentication processing step of performing authentication processing of the electronic ticket by using a display screen of the electronic ticket and an electronic stamp when the electronic ticket displayed on the user terminal is used;
generating display data for the electronic ticket;
an electronic ticket URL issuing step of issuing an electronic ticket URL (Uniform Resource Locator), which is information necessary for the user terminal to receive display data of the electronic ticket;
An electronic ticket display restriction step; and a program for executing the step,
the step of generating display data for the electronic ticket includes generating display data for the electronic ticket so that the user terminal can display the electronic ticket in both cases where the user terminal uses a web browser and where the user terminal uses an application installed on the user terminal;
the electronic ticket URL issuing step includes issuing a shortened URL as the electronic ticket URL that enables the user terminal to display the entire electronic ticket URL, both in a case where the user terminal uses a web browser and in a case where the user terminal uses an application installed in the user terminal ;
the electronic ticket display restriction step restricts the electronic ticket from being displayed on the user terminal unless the web browser or an application installed on the user terminal is used to access the short URL;
program.

Images