JP2017215938A - System, device, method and program for managing electronic ticket - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an electronic ticket management system, an electronic ticket management device, an electronic ticket management method, and an electronic ticket management program that improve usability of electronic tickets.SOLUTION: An electronic ticket management system includes: a transmission section for transmitting information related to a payment price for a user; a storage section for storing identification information of the user in association with a charge amount corresponding to the payment price; a portable terminal with a specified surface for transmitting unique information of a pressing member depressed relative to the specified surface, and a use amount selected by the user; an authentication section for determining whether the unique information matches prestored information, and transmitting information related to authentication success in the case that the information pieces are determined to match each other; and an update section for updating the charge amount stored in the storage section at a balance obtained by subtracting the use amount from the charge amount in the case that information related to the authentication success is received.SELECTED DRAWING: Figure 6

Description

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

  In recent years, touch panel terminals represented by smartphones and the like have become widespread. Business methods that have been performed manually in the past are being replaced by methods using a touch panel terminal. As one of the business methods using the touch panel terminal described above, an electronic ticket image is displayed on the touch panel display of the touch panel terminal at an event venue such as a concert venue, and an operation such as tapping is performed on the electronic ticket image. A method of executing a process for using an electronic ticket is known (for example, see Patent Documents 1 and 2).

JP 2013-238937 A JP 2014-149556 A

  However, with the above technique, the electronic ticket can only be used for specific purposes such as admission to a concert venue. That is, the usability of the electronic ticket is not good.

  In one aspect, an object of the present invention is to provide an electronic ticket management system, an electronic ticket management device, an electronic ticket management method, and an electronic ticket management program that can improve the usability of an electronic ticket.

  In one aspect, the electronic ticket management system includes a transmission unit that transmits information related to a user's payment price, a storage unit that associates and stores the identification information of the user and a charge amount corresponding to the payment price. And a mobile terminal that transmits the specific information of the pressing member pressed against the predetermined surface and the usage amount selected by the user, and the specific information is stored in advance. An authentication unit that transmits information related to successful authentication when it is determined to match, and when the information related to successful authentication is received, the usage amount is calculated from the charge amount. An update unit that updates the charge amount stored in the storage unit with a balance obtained by subtraction.

  When the mobile terminal receives information related to the authentication success, the mobile terminal may display used information for the usage amount. The information specific to the pressing member may include information relating to the store where the pressing member is disposed. The information regarding the store where the pressing member is arranged is stored, and when the information related to the authentication success is received, the information processing device further includes a storage unit that transmits the information related to the store. When the information related to the authentication success is received from the authentication unit and the information related to the store is received from the storage unit, the information related to the store may be displayed. The information related to the store stored in the storage unit may be the number of times the authentication unit transmits information related to authentication success for the pressing member in the store.

  In one aspect, the electronic ticket management device has a storage unit that stores a charge amount corresponding to a user's payment price and the user's identification information in association with each other, and a predetermined surface of the portable terminal that includes the predetermined surface. An authentication unit that determines whether or not the unique information of the pressed member that has been pressed matches information stored in advance, and transmits information related to successful authentication if it is determined to match, An update unit that updates the charge amount stored in the storage unit with a balance obtained by subtracting the usage amount transmitted from the mobile terminal from the charge amount when the information is received. It is characterized by that.

  In one aspect, in the electronic ticket management method, the storage unit stores the charge amount corresponding to the user's payment price and the identification information of the user in association with each other, and the authentication unit has a predetermined surface. Determining whether or not the unique information of the pressed member pressed against the predetermined surface matches information stored in advance, and when it is determined to match, information related to the authentication success is transmitted, and the updating unit When the information related to the authentication success is received, the charge amount stored in the storage unit is updated with a balance obtained by subtracting the use amount transmitted from the mobile terminal from the charge amount. It is characterized by that.

  In one aspect, an electronic ticket management program stores a charge amount corresponding to a user's payment price and a user's identification information in a storage unit in association with a computer, and a portable terminal having a predetermined surface Determining whether or not the unique information of the pressed member pressed against the predetermined surface matches information stored in advance, and transmitting information related to successful authentication when it is determined to match, A process of updating the charge amount stored in the storage unit with a balance obtained by subtracting the charge amount transmitted from the portable terminal from the charge amount when information related to the authentication success is received; , Is executed.

  Usability of electronic tickets can be improved.

It is a figure which illustrates the whole structure of the electronic ticket management system which concerns on embodiment. (A) And (b) is a figure which illustrates the screen displayed on a ticket sales terminal. It is a figure which illustrates a ticketing ticket. (A) And (b) is a figure which illustrates the additional purchase screen displayed on a portable terminal. (A)-(d) is a figure which illustrates about utilization of the electronic ticket using a portable terminal. (A) is a functional block diagram of the server, (b) is a diagram illustrating a user information table stored in the user information storage unit, (c) is stored in the wallet information storage unit It is a figure which illustrates a wallet information table, (d) is a figure which illustrates the ticket information table stored in the ticket information storage part, (e) is an authentication information table stored in the authentication information storage part. It is a figure illustrated. It is a sequence diagram showing an example of operation | movement of an electronic ticket management system. (A)-(c) is a figure which illustrates the flowchart showing each process of an electronic ticket management system. It is a figure which illustrates the flowchart showing each process of an electronic ticket management system. It is a figure which illustrates the flowchart showing each process of an electronic ticket management system. It is a figure which illustrates hardware constitutions. (A) is a functional block diagram of a server, (b) is a figure which illustrates the store information table stored in the store information storage part. It is a sequence diagram showing an example of operation | movement of an electronic ticket management system. It is a figure which illustrates the flowchart showing each process of an electronic ticket management system. It is a figure which illustrates the display of a touch panel.

  Hereinafter, embodiments will be described with reference to the drawings.

(First embodiment)
FIG. 1 is a diagram illustrating the overall configuration of an electronic ticket management system 100 according to the first embodiment. As illustrated in FIG. 1, the electronic ticket management system 100 has a configuration in which a ticket sales terminal 10, a portable terminal 20, a ticket use terminal 30, and the like are connected to a server 50 via an electric communication line 40 such as the Internet. The connection means to the telecommunication line 40 may be either wired or wireless. As an example, the ticket selling terminal 10 and the ticket using terminal 30 are connected to the telecommunication line 40 by a wired line such as a LAN. As an example, the mobile terminal 20 is connected to the telecommunication line 40 by radio. As an example, when the electronic ticket management system 100 is used in a specific island, the ticket sales terminal 10 is installed in a store such as a port, and the ticket use terminal 30 is installed in a plurality of stores such as a souvenir shop and a restaurant. . A stamp 60 is arranged at a store where the ticket use terminal 30 is installed.

  First, an outline of operation of the electronic ticket management system 100 will be described. A user presents user information and purchases an electronic ticket at a sales store equipped with the ticket sales terminal 10. For example, the user information includes a name, an address, an e-mail address, and the like. The salesperson at the sales store issues an electronic ticket having a charge amount corresponding to the payment price in exchange for the payment price from the user. An electronic ticket is an electronic version of a gift certificate. For example, an electronic ticket is an electronic gift certificate of 1,000 yen. Usually, the payment amount and the charge amount are the same, but they may be different.

  FIG. 2A and FIG. 2B are diagrams illustrating screens displayed on the ticket sales terminal 10. As illustrated in FIGS. 2A and 2B, a name, an address, a mail address, and the like are input as user information. In addition, the number of sets is input. The number of sets represents the quantity of electronic ticket sales units. As an example, 6,000 yen is assumed to be an electronic ticket sales unit. In the case of a gift certificate of 1,000 yen units, 6 gift certificates are sales units. In the example of FIG. 2B, since two sets are sold, an electronic ticket equivalent to 12,000 yen is sold.

  FIG. 3 is a diagram illustrating a ticket issued (hereinafter referred to as a ticket issuing ticket) corresponding to the electronic ticket. The total amount that can be used is printed on the ticket issued. In addition, the expiration date of the electronic ticket, the serial number for additional purchase, the number of sets that can be additionally purchased, and the like are printed. FIG. 4A and FIG. 4B are diagrams illustrating an additional purchase screen displayed on the mobile terminal 20. As illustrated in FIG. 4A, input of a serial number for additional purchase is required. When the serial number for additional purchase is input, as illustrated in FIG. 4B, input of the number of additional purchase sets is requested. For the additional purchase settlement, a credit card settlement via the telecommunication line 40 can be used.

  The user accesses the URL printed on the ticket-issuing ticket when validating the purchased electronic ticket. For example, the QR code (registered trademark) illustrated in FIG. 3 can be used. FIG. 5A to FIG. 5D are diagrams illustrating the use of an electronic ticket using the mobile terminal 20. As illustrated in FIG. 5A, when the URL printed on the ticketing ticket is accessed from the portable terminal 20, the expiration date, the balance of available electronic tickets (total available amount), and the like are displayed.

  A user uses an electronic ticket as a consideration for goods, services, etc. at a store equipped with the ticket use terminal 30. For example, as illustrated in FIG. 5B, the user selects an amount corresponding to the number of gift certificates to be used as the usage amount. In the example of FIG. 5B, “4,000 yen” corresponding to four 1,000 yen gift certificates is selected. A salesperson in the store presses the dedicated stamp 60 on a predetermined area of a predetermined surface such as a touch panel of the mobile terminal 20.

  The stamp 60 is arranged in a plurality of stores where the ticket use terminal 30 is installed. The stamp 60 includes information unique to each stamp 60. The information unique to each stamp 60 includes information indicating that the stamp 60 is a regular stamp used in the electronic ticket management system 100, identification information of a store provided with the stamp 60, and the like.

  For example, the stamp 60 includes protrusions at predetermined locations on the pressing surface of the touch panel of the mobile terminal 20. Each protrusion is provided with a spring property, and the length of each protrusion is varied. Thereby, each protrusion can set a combination in the pressing order with respect to the touch panel of the portable terminal 20. A combination of the pressing order, the arrangement position of each protrusion, and the like can be used as information unique to each stamp 60.

  In the present embodiment, the stamp 60 is used as a pressing member for the mobile terminal 20, but is not limited to the stamp. Other pressing members may be used as long as they can give unique information to the predetermined surface of the mobile terminal 20.

  When the stamp 60 is pressed on the touch panel of the mobile terminal 20, a mark indicating that the usage amount has been used is displayed on the mobile terminal 20 as illustrated in FIG. Thereby, since the price is paid at the store, the product, service, etc. are provided to the user. Also, the use of the number of gift certificates corresponding to the usage amount is prohibited. In addition, as illustrated in FIG. 5D, a balance or the like may be displayed on the screen of the mobile terminal 20.

  Next, the operation of each part of the electronic ticket management system 100 will be described in detail with respect to the operation of the electronic ticket management system 100 described above. FIG. 6A is a functional block diagram of the server 50. As illustrated in FIG. 6A, the server 50 includes a user information management unit 51, a user information storage unit 52, a wallet management unit 53, a wallet information storage unit 54, a ticket management unit 55, and a ticket information storage unit 56. , Functions as an authentication unit 57, an authentication information storage unit 58, and the like.

  FIG. 6B is a diagram illustrating a user information table stored in the user information storage unit 52. FIG. 6C is a diagram illustrating a wallet information table stored in the wallet information storage unit 54. FIG. 6D is a diagram illustrating a ticket information table stored in the ticket information storage unit 56. FIG. 6E is a diagram illustrating an authentication information table stored in the authentication information storage unit 58.

  FIG. 7 is a sequence diagram illustrating an example of the operation of the electronic ticket management system 100. FIG. 8A to FIG. 8C, FIG. 9 and FIG. 10 are diagrams illustrating flowcharts representing respective processes of the electronic ticket management system 100. Hereinafter, the operation of the electronic ticket management system 100 will be described in detail with reference to FIGS.

(User information storage processing)
The user information storage unit 52 stores the user information of each user in the user information table. As illustrated in FIG. 6B, fields such as “user ID”, “name”, “address”, and “mail address” of each user are set in the user information table. As illustrated in FIG. 7 and FIG. 8A, the user information management unit 51 determines whether user information has been received from the ticket sales terminal 10 (step S1). If it is determined “No” in step S1, step S1 is executed again. When it is determined as “Yes” in step S1, the user information management unit 51 sets a user ID as user identification information for the user information (step S2). Next, the user information management unit 51 associates the user ID with the user information, and stores the user ID and the user information in the user information table (step S3).

(Wallet information storage process)
The wallet information storage unit 54 stores wallet information regarding the amount of money available to each user in the wallet information table. The wallet information represents the user's wallet function. In the wallet information table, as the wallet information, “wallet ID”, “user ID”, “remaining amount”, “charge upper limit”, “expiration date”, “purchasing sales office”, “valid / invalid”, “serial” Columns such as “number” are set.

  As illustrated in FIGS. 7 and 8B, the wallet management unit 53 determines whether the number of sets has been received from the ticket sales terminal 10 (step S11). If it is determined “No” in step S11, step S11 is executed again. If “Yes” is determined in step S11, the wallet management unit 53 sets the wallet ID, the expiration date, and the serial number (step S12). Next, the wallet management unit 53 associates the wallet ID with the user ID, the amount corresponding to the number of ticket sets, the charge upper limit, the expiration date, the identification information of the ticket selling terminal 10, and the serial number, The information is stored in the information table (step S13).

  At this time, the amount corresponding to the number of ticket sets is stored as the charge amount in the “Remaining amount” column. The wallet ID stores a unique URL for each user. Further, the identification information of the ticket sales terminal 10 is stored in the “purchase sales office” column. The charge upper limit may vary depending on the user, but may be a common amount for each user. As the expiration date, a date that is a predetermined number of days after the sales date of the number of ticket sets is set. At this time, identification information related to invalidity is stored in the “valid / invalid” column.

  Next, the wallet management unit 53 transmits information stored in the “remaining amount”, “charge upper limit amount”, “expiration date”, and “serial number” columns of the wallet information to the ticket sales terminal 10 (step S40). S14). Thereby, the ticket sales terminal 10 can print the ticket issuing ticket illustrated in FIG.

(Ticket activation process)
As illustrated in FIGS. 7 and 8C, the wallet management unit 53 determines whether or not the URL printed on the ticketing ticket has been accessed from the portable terminal 20 (step S21). That is, in step S21, it is determined whether or not the URL of the wallet ID has been accessed. If it is determined “No” in step S21, step S21 is executed again. If “Yes” is determined in step S21, the wallet management unit 53 stores the identification information related to validity in the “valid / invalid” column associated with the wallet ID in the wallet information table (step S22). ). Thereby, the electronic ticket is validated.

(Ticket issuing process)
The ticket information storage unit 56 stores information related to the electronic ticket used by each user in the ticket information storage table. In the ticket information storage table, fields such as “ticket ID”, “use amount”, “status”, and “wallet ID” are set. The authentication information storage unit 58 stores information unique to the stamp 60 of each store that can use the electronic ticket and the store ID where the stamp 60 is arranged in the authentication information table.

  When a usage amount corresponding to the number of gift certificates used on the mobile terminal 20 is selected, information (wallet ID) related to the URL accessed by the mobile terminal 20 and the usage amount are stored in the wallet management unit 53. Sent. As illustrated in FIGS. 7 and 9, the wallet management unit 53 determines whether or not the usage amount and the wallet ID have been received from the mobile terminal 20 (step S31). If “No” is determined in step S31, the process is executed again from step S31. If “Yes” is determined in step S31, the usage amount and the wallet ID are transmitted to the ticket management unit 55 (step S32).

  Next, the ticket management unit 55 sets a ticket ID (step S33). Next, the ticket management unit 55 associates the usage amount and the wallet ID with the ticket ID and stores them in the ticket information storage table (step S34). At this point, information related to “before use” is stored in the “status” column of the ticket information storage table.

  When the stamp 60 is pressed in a predetermined area of the touch panel of the mobile terminal 20, stamp information unique to the stamp 60 is transmitted from the mobile terminal 20 to the wallet management unit 53. Next, the wallet management unit 53 determines whether or not stamp information has been received from the mobile terminal 20 (step S35). If it is determined “No” in step S35, step S35 is executed again. When it is determined as “Yes” in step S35, the wallet management unit 53 transmits the received stamp information to the authentication unit 57 (step S36).

  Next, the authentication unit 57 determines whether or not the stamp information received from the wallet management unit 53 matches any stamp information stored in the authentication information table (step S37). If “No” is determined in step S37, the authentication unit 57 transmits information related to the authentication failure to the wallet management unit 53 (step S38). Thereby, the ticket issuing process ends. If it is determined as “Yes” in step S37, the authentication unit 57 transmits information related to the authentication success and the store ID associated with the stamp information to the ticket management unit 55, and the ticket management unit 55 Information related to the authentication success is transmitted to 20 (step S39).

  Thereby, the portable terminal 20 displays a mark related to the used amount of money on the touch panel (step S40). Next, the ticket management unit 55 stores the information after use in the “status” column of the ticket information storage table (step S41). Next, the ticket management unit 55 transmits the usage amount stored in the ticket information storage table and information related to the authentication success to the wallet management unit 53 (step S42). Next, the wallet management unit 53 stores the amount obtained by subtracting the usage amount from the balance associated with the wallet ID in the “balance” column (step S43).

(Additional purchase processing)
As described above, the ticket sales terminal 10 is not necessarily used for the additional purchase of the electronic ticket. As described above, credit card payment using the mobile terminal 20 can be used. For example, as illustrated in FIG. 4A and FIG. 4B, the user transmits the serial number and the number of additional sets to the wallet management unit 53 using the mobile terminal 20. At this time, the user may perform credit settlement using the mobile terminal 20. In this case, information relating to the completion of credit settlement is also transmitted to the wallet management unit 53.

  FIG. 10 is a diagram illustrating a flowchart representing the additional purchase process. As illustrated in FIG. 10, the wallet management unit 53 determines whether or not a serial number has been received from the mobile terminal 20 (step S51). If it is determined “No” in step S51, step S51 is executed again. When it is determined as “Yes” in Step S51, the wallet management unit 53 determines whether or not the number of additional sets has been received from the mobile terminal 20 (Step S52).

  If it is determined “No” in step S52, step S52 is executed again. When it is determined as “Yes” in Step S52, the wallet management unit 53 determines whether or not information related to the completion of the credit payment is received from the mobile terminal 20 (Step S53). If it is determined “No” in step S53, step S53 is executed again. If “Yes” is determined in step S53, the wallet management unit 53 adds the amount corresponding to the number of additional sets to the balance in the wallet information table, and updates the “balance” column in the wallet information table (step S54). ).

  Next, effects of the electronic ticket management system 100 will be described. A general electronic ticket is used, for example, as an alternative to a ticket presented at the entrance of a concert venue or the like. Specifically, the information related to the purchased ticket is displayed on the mobile terminal, and the venue staff presses a stamp on the mobile terminal to make the ticket used. Such electronic tickets can only be used for specific purposes such as admission to a concert venue. Therefore, it cannot be used for various purposes. That is, it is not easy to use.

  Thus, it is conceivable to use an electronic ticket as a substitute for a gift certificate. By giving the electronic ticket a function as a gift certificate, the electronic ticket can be used for various purposes. For example, it can be used for purchasing a plurality of products at a store or the like. However, a predetermined amount is associated with each gift certificate. For example, 1,000 yen is associated with one gift certificate. In such a case, when trying to purchase a 5,000 yen gift certificate as an electronic ticket, a process of issuing five gift certificates is required. In order to realize each gift certificate as an electronic ticket, it is necessary to give unique information to each gift certificate. In this case, it is necessary to have a memory capacity, a calculation amount required for the settlement processing of the specific information, and the like. That is, a memory capacity, a calculation amount, and the like corresponding to the number of gift certificates are required. Therefore, in order to reduce the memory capacity, the calculation amount, etc., it is necessary to reduce the number of issued gift certificates. That is, it becomes necessary to increase the amount of one gift certificate. For example, a large amount of money such as 10,000 is associated with one gift certificate. In this case, it is difficult to purchase a small amount of product, and the usability of the electronic ticket is deteriorated.

  On the other hand, according to the electronic ticket management system 100 according to the present embodiment, even if the user uses the electronic ticket, the balance is only updated. That is, regardless of the number of gift certificates, unique information such as a user ID and a wallet ID is given to each electronic ticket. In this case, the memory capacity, the calculation amount, etc. can be greatly reduced. In addition, since it is not necessary to take measures such as reducing the number of gift certificates issued, there is no need to issue expensive gift certificates that are not easy to use. From the above, it is possible to improve the user-friendliness and reduce the memory capacity and the calculation amount.

  Moreover, according to the electronic ticket management system 100 according to the present embodiment, a mobile terminal already owned by the user can be used. In this case, it is not necessary to issue a new IC card like an electronic currency. Therefore, there is no need to manufacture an IC card issuing machine or an IC card. Further, it is only necessary to place the stamp 60 in the electronic ticket using store, and it is not necessary to newly install an IC card reader or the like. Therefore, it is not necessary to manufacture an IC card reader. From the above, the introduction cost of the electronic ticket management system 100 can be suppressed, and the labor required for the introduction of the electronic ticket management system 100 can be omitted.

  FIG. 11 is a block diagram illustrating a hardware configuration of the ticket sales terminal 10, the mobile terminal 20, the ticket use terminal 30, and the server 50. As illustrated in FIG. 11, the ticket sales terminal 10 includes a CPU 110, a RAM 120, a storage device 130, a communication device 140, a display device 150, and the like. The portable terminal 20 includes a CPU 210, a RAM 220, a storage device 230, a communication device 240, a display device 250, and the like. The ticket using terminal 30 includes a CPU 310, a RAM 320, a storage device 330, a communication device 340, a display device 350, and the like. The server 50 includes a CPU 410, a RAM 420, a storage device 430, a communication device 440, a display device 450, and the like.

  CPUs (Central Processing Units) 110, 210, 310, and 410 are central processing units. RAM (Random Access Memory) 120, 220, 320, and 420 are volatile memories that temporarily store programs executed by the CPUs 110, 210, 310, and 410, data processed by the CPUs 110, 210, 310, and 410, respectively. is there. The storage devices 130, 230, 330, and 430 are nonvolatile storage devices. As the storage devices 130, 230, 330, and 430, for example, a ROM (Read Only Memory), a solid state drive (SSD) such as a flash memory, a hard disk driven by a hard disk drive, or the like can be used. When the CPU 410 executes the electronic ticket management program stored in the storage device 430, a user information management unit 51, a user information storage unit 52, a wallet management unit 53, a wallet information storage unit 54, A ticket management unit 55, a ticket information storage unit 56, an authentication unit 57, and an authentication information storage unit 58 are realized. Note that the display device 250 of the mobile terminal 20 functions as a touch panel.

  In the above embodiment, one server is used, but a plurality of servers may be used. For example, a first server that functions as a user information management unit 51 and a user information storage unit 52, a second server that functions as a wallet management unit 53 and a wallet information storage unit 54, a ticket management unit 55, and a ticket information storage unit 56 A fourth server that functions as the third server, the authentication unit 57, and the authentication information storage unit 58 may be used.

  In the above-described embodiment, the ticket sales terminal 10 functions as an example of a transmission unit that transmits information related to a user's payment price. The wallet information storage unit 54 functions as an example of a storage unit that stores user identification information and a charge amount corresponding to a payment price in association with each other. The mobile terminal 20 has a predetermined surface and functions as an example of a mobile terminal that transmits the unique information of the pressing member pressed against the predetermined surface and the usage amount selected by the user. The authentication unit 57 functions as an example of an authentication unit that determines whether or not the unique information of the pressing member matches information stored in advance, and transmits information related to successful authentication when it is determined to match. When the wallet management unit 53 receives information related to successful authentication, it functions as an example of an update unit that updates the charge amount stored in the storage unit with a balance obtained by subtracting the usage amount from the charge amount. . The server 50 functions as an example of an electronic ticket management device.

(Second Embodiment)
In the first embodiment, as illustrated in FIG. 5C, when the stamp 60 is pressed on the touch panel of the mobile terminal 20, authentication is performed by the authentication unit 57, but this authentication may be illegally avoided. is there. For example, assume that the user has illegally created the screens of FIGS. 5B and 5C. In the store, an unauthorized application that displays the screen of FIG. 5C when the user presents the screen of FIG. 5B to the store salesperson and the salesperson presses the stamp 60 on the touch panel. If used, the salesperson may not be aware of fraud. Therefore, in the second embodiment, a technique for preventing unauthorized use of an electronic ticket is disclosed.

  The electronic ticket management system 100a according to the second embodiment is different from the electronic ticket management system 100 according to the first embodiment in that a server 50a is provided instead of the server 50. About the same structure as 1st Embodiment, description is abbreviate | omitted by attaching | subjecting the same code | symbol.

  FIG. 12A is a functional block diagram of the server 50a. As illustrated in FIG. 12A, the server 50 a functions as a store management unit 71 and a store information storage unit 72 in addition to the function of the server 50. FIG. 12B is a diagram illustrating a store information table stored in the store information storage unit 72. As illustrated in FIG. 12B, fields such as “store ID”, “store name”, “cumulative number”, and “mail address” are set in the store information table. In the store information table, store names, cumulative numbers, and e-mail addresses are stored in advance in association with store IDs. The store name is a store name provided with the ticket use terminal 30. The cumulative number is the cumulative number of times that the electronic ticket has been used in the store, and is the number of times that the authentication unit 57 has transmitted information related to successful authentication for the stamp 60 placed in the store. The e-mail address is the e-mail address of the store.

  FIG. 13 is a sequence diagram illustrating an example of the operation of the electronic ticket management system 100a. FIG. 14 is a diagram illustrating a flowchart representing each process of the electronic ticket management system 100a. User information storage processing, wallet information storage processing, and ticket validation processing are the same as in the first embodiment. Details of the operation of the electronic ticket management system 100a after the user information storage process, the wallet information storage process, and the ticket validation process are completed will be described below with reference to FIGS.

  As illustrated in FIG. 14, steps S31 to S38 are the same as the flowchart of FIG. 9. When it is determined as “Yes” in step S37, the authentication unit 57 transmits information related to the authentication success and the store ID associated with the stamp information to the ticket management unit 55 (step S51). Next, the ticket management unit 55 transmits the store ID received in step S51 to the store management unit 71 (step S52).

  When the store management unit 71 receives the store ID from the ticket management unit 55, the store management unit 71 updates the cumulative number by adding 1 to the cumulative number stored in the store information storage unit 72, and stores the store name associated with the store ID. The updated cumulative number and e-mail address are transmitted to the ticket management unit 55 (step S53). Next, the ticket management unit 55 transmits an e-mail describing information related to ticket use to the e-mail address received in step S53 (step S54). Next, the ticket management unit 55 transmits the information related to the authentication success, the store name received in step S53, the cumulative number, and the current time to the portable terminal 20 (step S55).

  Thereby, as illustrated in FIG. 15, the mobile terminal 20 displays a mark indicating that the usage amount has been used on the touch panel, and also displays the cumulative number, the store name, and the current time (step S56). Next, the ticket management unit 55 stores the information after use in the “status” column of the ticket information storage table (step S57). Next, the ticket management unit 55 transmits the usage amount stored in the ticket information storage table and information related to the authentication success to the wallet management unit 53 (step S58). Next, the wallet management unit 53 stores the amount obtained by subtracting the usage amount from the balance associated with the wallet ID in the “balance” column (step S59).

  According to the present embodiment, the accumulated number is displayed on the touch panel of the mobile terminal 20 as the confidential information that the user cannot know. The salesperson of the store can determine whether or not the user of the electronic ticket is fraudulent by checking the cumulative number. Note that the ticket use terminal 30 may periodically receive the accumulated number from the store management unit 71. Thereby, the salesperson can confirm the present accumulation number.

  In addition, if the store name displayed on the touch panel is a modified store name (abbreviated name, nickname, etc.) that the user cannot know but has been notified to the salesperson in advance, the user of the electronic ticket has made a fraud. It can be determined whether or not. In addition, as confidential information that the user cannot know, information related to the store where the stamp 60 is arranged is displayed on the touch panel of the mobile terminal 20 to determine whether the user of the electronic ticket is fraudulent. can do.

  In addition, if the electronic ticket is properly used, an e-mail is delivered to the ticket use terminal 30, so the salesperson can determine whether or not the user of the electronic ticket is fraudulent.

  In 2nd Embodiment, the store information storage part 72 memorize | stores the information which concerns on the shop where the pressing member is arrange | positioned, and when the information which concerns on authentication is received, the memory | storage part which transmits the information which concerns on a shop Functions as an example.

  Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications and changes can be made within the scope of the gist of the present invention described in the claims. It can be changed.

DESCRIPTION OF SYMBOLS 10 Ticket sales terminal 20 Portable terminal 30 Ticket use terminal 40 Telecommunication line 50 Server 51 User information management part 52 User information storage part 53 Wallet management part 54 Wallet information storage part 55 Ticket management part 56 Ticket information storage part 57 Authentication part 58 Authentication Information Storage Unit 60 Stamp 100 Electronic Ticket Management System

Claims (8)

A transmission unit for transmitting information relating to the user's payment fee;
A storage unit that stores the identification information of the user in association with the charge amount corresponding to the payment price;
A portable terminal that includes a predetermined surface and transmits the unique information of the pressing member pressed against the predetermined surface and the usage amount selected by the user;
It is determined whether or not the unique information matches information stored in advance, and an authentication unit that transmits information related to successful authentication when it is determined to match,
An update unit that updates the charge amount stored in the storage unit with a balance obtained by subtracting the use amount from the charge amount when information related to the authentication success is received. A featured electronic ticket management system.   The electronic ticket management system according to claim 1, wherein the mobile terminal displays used information for the usage amount when receiving information related to the authentication success.   3. The electronic ticket management system according to claim 1, wherein the unique information of the pressing member includes information relating to a store in which the pressing member is disposed. A storage unit that stores a charge amount corresponding to a user's payment price and the identification information of the user in association with each other;
It is determined whether or not the unique information of the pressing member pressed against the predetermined surface of the mobile terminal having the predetermined surface matches the information stored in advance, and information related to the authentication success when it is determined that they match An authentication unit that transmits
An update unit that updates the charge amount stored in the storage unit with a balance obtained by subtracting the use amount transmitted from the mobile terminal from the charge amount when information related to the authentication success is received. An electronic ticket management device comprising: The storage unit stores the charge amount corresponding to the payment price of the user and the identification information of the user in association with each other,
The authentication unit determines whether or not the unique information of the pressing member pressed against the predetermined surface of the portable terminal having the predetermined surface matches the information stored in advance, and the authentication is successful when it is determined that they match Send information about
When the update unit receives the information related to the authentication success, the charge amount stored in the storage unit is obtained by subtracting the use amount transmitted from the mobile terminal from the charge amount. An electronic ticket management method comprising: updating. On the computer,
A process of associating the charge amount corresponding to the user's payment price and the identification information of the user in the storage unit;
It is determined whether or not the unique information of the pressing member pressed against the predetermined surface of the mobile terminal having the predetermined surface matches the information stored in advance, and information related to the authentication success when it is determined that they match The process of sending
A process of updating the charge amount stored in the storage unit with a balance obtained by subtracting the charge amount transmitted from the portable terminal from the charge amount when information related to the authentication success is received; And an electronic ticket management program. Storing information related to the store in which the pressing member is arranged, and further including a storage unit that transmits information related to the store when the information related to the successful authentication is received;
The said portable terminal displays the information which concerns on the said store, when the information which concerns on the said authentication success is received from the said authentication part, and the information which concerns on the said store is received from the said memory | storage part. The electronic ticket management system according to claim 3.   The electronic ticket management system according to claim 7, wherein the information related to the store stored in the storage unit is the number of times the authentication unit transmits information related to successful authentication for the pressing member in the store.

Images