JP6480385B2 - Information processing system, information processing method, and program - Google Patents

Description

  Some embodiments according to the present invention relate to an information processing system, an information processing method, and a program.

  In recent years, an electronic ticket issuing system using a portable terminal such as a so-called smartphone has been considered (for example, see Patent Document 1). In Patent Document 1, when an event ticket purchase is desired, if the ticket purchase settlement process is performed by accessing the ticket purchase page, the server may transmit the event ticket data to the purchaser's portable terminal. It is disclosed.

Japanese Patent No. 5256372

Here, in the case of a particularly popular ticket, the ticket purchaser may try to resell the ticket by raising the price. In this regard, in the method described in Patent Document 1, information such as the ticket purchaser's ID is registered in the database in association with the event. Therefore, as long as the purchaser himself uses the ID, it seems that the resale of the ticket does not occur.
However, even if information such as an ID is registered in association with an event as described in Patent Document 1, an act of reselling a ticket together with a user account including a user ID cannot be prevented.

  Some aspects of the present invention have been made in view of the above-described problems and the like, and provide an information processing system, an information processing method, and a program that can suppress a user's free resale of tickets. Objective.

  The information processing system according to the present invention inputs user information for identifying a user and terminal information for identifying a ticket receiving terminal from which the user receives the electronic ticket from one or more users who apply for an electronic ticket. Receiving means, a means for specifying a target user to transmit the electronic ticket among the one or more users, user information for specifying the user from an application of a user terminal operated by the user, and the Means for receiving terminal information for identifying a user terminal; user information received from the user terminal matches the user information related to the target user; and the terminal information received from the user terminal receives the ticket received by the target user. If it matches the terminal information related to the terminal, the ticket data related to the electronic ticket is And a first transmission means for transmitting to the application of The terminals.

  According to the information processing method of the present invention, from one or more users who apply for an electronic ticket, user information for specifying the user and terminal information for specifying the ticket receiving terminal from which the user receives the electronic ticket are input. The user information for identifying the user from the application of the user terminal operated by the user, the user information, and the user Receiving terminal information for identifying a terminal; user information received from a user terminal matches user information related to the target user; and terminal information received from the user terminal is the ticket receiving terminal of the target user If it matches the terminal information related to the Performed by the information processing system and transmitting to the application of the user terminal.

  The program according to the present invention receives input of user information for specifying a user and terminal information for specifying a ticket receiving terminal from which the user receives the electronic ticket from one or more users who apply for an electronic ticket. Processing, processing for identifying a target user to which the electronic ticket is transmitted among the one or more users, user information for identifying the user from an application of the user terminal operated by the user, and the user terminal The process of receiving the terminal information for specifying, the user information received from the user terminal matches the user information related to the target user, and the terminal information received from the user terminal relates to the ticket receiving terminal of the target user If it matches the terminal information, the ticket data related to the electronic ticket is stored in the user terminal. To execute a process of transmitting to the serial application to the information processing system.

  In the present invention, “part”, “means”, “apparatus”, and “system” do not simply mean physical means, but “part”, “means”, “apparatus”, “system”. This includes the case where the functions possessed by "are realized by software. Further, even if the functions of one “unit”, “means”, “apparatus”, and “system” are realized by two or more physical means or devices, two or more “parts” or “means”, The functions of “device” and “system” may be realized by a single physical means or device.

  ADVANTAGE OF THE INVENTION According to this invention, the information processing system, the information processing method, and program which can suppress the resale action of the ticket free by a user can be provided.

It is a figure showing an example of composition of a ticket system concerning an embodiment. It is a figure which shows the specific example of a function structure of the management server which concerns on embodiment. It is a figure which shows the specific example of a function structure of the ticket application which concerns on embodiment. It is a flowchart which shows the specific example of the flow of a process of the ticket system which concerns on embodiment. It is a flowchart which shows the specific example of the flow of a process of the ticket system which concerns on embodiment. It is a figure which shows the specific example of the display screen displayed in the ticket system which concerns on embodiment. It is a figure which shows the specific example of the display screen displayed in the ticket system which concerns on embodiment. It is a flowchart which shows the specific example of the flow of a process of the ticket system which concerns on embodiment. It is a figure which shows the specific example of the hardware constitutions of the management server which concerns on embodiment. It is a figure which shows the specific example of the hardware constitutions of the portable terminal which concerns on embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiment described below is merely an example, and there is no intention to exclude various modifications and technical applications that are not explicitly described below. That is, the present invention can be implemented with various modifications without departing from the spirit of the present invention. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. The drawings are schematic and do not necessarily match actual dimensions and ratios. In some cases, the dimensional relationships and ratios may be different between the drawings.

  1 to 9 are diagrams for explaining the embodiment. Hereinafter, embodiments will be described along the following flow with reference to these drawings. First, an outline of the ticket system according to the embodiment will be described in “1”. Next, “2” describes the functional configuration of the management server and ticket application used in the ticket system, and “3” describes the processing flow of the ticket system. In “4”, a specific example of a hardware configuration capable of mounting a management server and a portable terminal included in the ticket system will be described. Finally, the effects and the like according to the present embodiment will be described after “5”.

(1. Overview)
First, with reference to FIG. 1, an outline of the configuration and processing of the ticket system 1 according to the embodiment will be described. The ticket system 1 includes, for example, portable terminals 100A and 100B (hereinafter collectively referred to as a portable terminal 100) used by users UA and UB (hereinafter collectively referred to as a user U) who can purchase and use tickets. And a management server 200 managed by a service provider that provides a ticket service. The portable terminal 100 and the management server 200 can communicate with each other via a network N by wire or wireless.

  In the ticket system 1, the user U uses the ticket application installed in the portable terminal 100 (hereinafter also referred to as a ticket application. Hereinafter, the application program is also simply referred to as “application”) to provide an electronic ticket service. Can receive. Specifically, the user U enters in advance into a stadium such as soccer or baseball, various facilities such as an amusement park or zoo, a live venue, etc. (hereinafter collectively referred to simply as “venue”). The electronic ticket application of the portable terminal 100 downloads electronic ticket data related to the ticket. The user U presents a display screen displaying the electronic ticket to the attendant at the venue. The staff inputs a predetermined operation (for example, a specific pattern tracing operation or a swipe operation) on the display screen, or an electronic stamp member having a specific pattern is stamped on the screen (to the touch panel). When a contact operation or the like is performed, the ticket application performs a tear-off process (consumption process) in which the electronic ticket is used. Further, the ticket application notifies the management server 200 that the electronic ticket has been used. Hereinafter, an operation of inputting a specific operation or stamping a stamp member on the screen (such as a touch operation on the touch panel) in order to make the electronic ticket used is also referred to as a tearing operation.

  It is not always necessary for the attendant at the venue to perform the cutting operation. For example, it is conceivable that an entrance management device for making an electronic ticket used at the entrance gate of the venue is arranged and the smashing process is performed by the entrance management device. In this case, for example, when the user performs an operation to bring the portable terminal 100 close to the admission management device, near field communication (NFC) is performed between the portable terminal 100 and the admission management device. This is done, and the ticket application of the portable terminal 100 only needs to perform a tearing process in which the electronic ticket has been used.

  As described above, the ticket application is installed in the portable terminal 100, and the user U can receive provision of the ticket service by using the ticket application. Specifically, the portable terminal 100 can download electronic ticket data purchased by the user U from the management server 200 and display a display screen related to the electronic ticket. Further, when a cutting operation is input on the display screen of the electronic ticket, the portable terminal 100 notifies the management server 200 that the electronic ticket has been used. The portable terminal 100 can be realized by, for example, a mobile phone called a feature phone or a so-called smartphone, a tablet terminal, a PDA (Personal Digital Assistant), a portable game machine, or the like.

  In the following description, an example in which a ticket application is installed in the portable terminal 100 and electronic ticket data is downloaded to the ticket application will be mainly described.

  The management server 200 is a server that sells and manages electronic tickets. Note that the function of the management server 200 is not necessarily physically realized by one server, and can be realized by a plurality of servers.

  For example, the management server 200 provides a ticket sales site. The user U operates the browser on the portable terminal 100 or other information processing terminal to access the ticket sales site and apply for ticket purchase on the ticket sales site (hereinafter referred to as purchase application). Or an offer.) In this embodiment, at this time, the user U registers terminal information (for example, a telephone number) of the portable terminal 100 that downloads (receives) the ticket. In the information related to the ticket purchase application, the management server 200 manages the identification information of the user U and the terminal information of the terminal that receives the ticket (hereinafter also referred to as a ticket receiving terminal) in association with each other. After that, for example, as a result of lottery or the like, after the user U acquires the ticket purchase right, the user U activates the ticket application of the portable terminal 100, and when the ticket application accesses the management server 200, the management server 200 It is confirmed whether the terminal information of the portable terminal 100 matches the terminal information registered as the ticket receiving terminal. As a result, if the terminal information matches, the management server 200 transmits the electronic ticket data to the portable terminal 100. In addition, when the management server 200 receives information indicating that the electronic ticket has been used from the portable terminal 100, the management server 200 updates the status information related to the electronic ticket to used.

  As described above, in the ticket system 1 according to the present embodiment, the information of the ticket receiving terminal that receives the ticket is registered in the user U at the time of applying for ticket purchase. Thereby, the user U can receive / use the electronic ticket only at the terminal registered as the ticket receiving terminal. As a result, it is possible to prevent the electronic ticket from being resold freely.

  As described above, the network N connects the portable terminal 100 and the management server 200 so that they can communicate with each other. The network N can be realized by, for example, the Internet, and can include a wireless LAN access point, a mobile phone base station, and the like.

  In the ticket system 1 according to the present embodiment, a ticket held by the user UA can be sold to another user UB under the management of the management server 200. Thereby, for example, even when the user UA cannot go to the event related to the ticket, the ticket is not wasted. Further, since the ticket is sold only under the management of the management server 200, it is possible to prevent the ticket from being resold by raising the amount of money illegally. For example, the buying and selling of tickets at a fixed price or a price obtained by adding a fee to the fixed price can be guaranteed.

  Furthermore, the management server 200 according to the present embodiment manages ticket management data for managing each issued ticket (which can include not only an electronic ticket but also a paper ticket) and a user who holds each ticket. . As a result, when each user applies for ticket sales, it is possible to confirm that the user has a valid ticket (not having acquired the ticket without going through the service provider). is there. If the user U who has a paper ticket right sells the ticket, for example, the user U applies for the sale of the ticket on the website provided by the management server 200 and also asks the service provider. A paper ticket will be mailed to you. When the user who applied for the sale matches the ticket holder data managed on the ticket management data, the management server 200 sells the ticket to another user. At this time, the ticket sold by the management server 200 does not necessarily have to be a paper ticket, and can be sold as an electronic ticket. If a paper ticket has not been received from the ticket sale applicant at the time of sale, the management server 200 displays that the electronic ticket sold to the purchaser cannot be used. Thereafter, when a paper ticket is received from the ticket seller, it is possible to avoid duplicate use of the same seat ticket by displaying seat information on the ticket surface of the purchaser's electronic ticket.

  A ticket purchaser (also referred to as a purchase applicant) who buys and sells tickets between users is a ticket sold for a certain event in the same way as when purchasing a normal ticket (however, other users possess and sell it). Apply for the purchase of the applied ticket). At this time, the user U who wants to purchase registers terminal information (for example, a telephone number) of the portable terminal 100 that receives the electronic ticket. For example, the management server 200 can determine, by lottery, to which purchase applicant the ticket for which the sale is requested by the seller is sold. At this time, for example, whether or not a plurality of consecutive seats is desired, a ticket type (for example, whether or not the ticket can be used only by a fan club member), and the like may be considered.

  Here, when the ticket purchase applicant applies for the purchase, the ticket purchase applicant may apply for the entire ticket of the same type, not for the individual ticket to be sold. For example, let us consider a case in which a total of 10 sale applications have been made from a plurality of sale applicants for the SS seat of the event “XXX” held at the venue “XX” on XX month × day. In this case, for example, each purchase applicant who desires to purchase one SS seat for the event can make a purchase application for each of the ten tickets. As a result, when purchasing a ticket, the purchase applicant does not have to repeatedly apply for (entry) the same performance.

  Note that an application for selling a ticket and an application for purchasing a ticket for which an application for sale has been made can be made, for example, on a browser installed in the portable terminal 100 of the user U. It is also conceivable to apply on a browser of another information processing apparatus (for example, a personal computer (PC)) other than the portable terminal 100 in which a ticket application for using an electronic ticket is installed.

  In the following example, the user UA applies for the sale of a ticket using the browser of the portable terminal 100A owned by the user, and the user UB applies for the purchase of the ticket using the browser of the portable terminal 100B owned by the user UA. I will explain it mainly. In this case, the user UA is a user who wants to sell, and the user UB is a user who wants to purchase.

(2. Functional configuration)
Hereinafter, the functional configuration of the management server 200 according to the present embodiment and the ticket application 300 installed in the portable terminal 100 will be described with reference to FIGS. 2 and 3.

(2.1 Functional configuration of management server 200)
First, the functional configuration of the management server 200 will be described with reference to FIG. FIG. 2 is a functional block diagram illustrating a specific example of the functional configuration of the management server 200. The management server 200 is roughly divided into a website providing unit 210, a ticket status changing unit 230, a lottery unit 240, a ticket acquisition request receiving unit 250, a ticket data transmitting unit 260, a message transmitting unit 270, and a database (DB) 280. Including. As described above, the functional configuration of the management server 200 is not necessarily realized by a single server, and may be realized by a plurality of servers.

  The website providing unit 210 provides a website for providing an electronic ticket service on a network N that is, for example, the Internet. The website provides various information such as tickets sold, actually sells tickets, accepts applications for selling tickets held by user U, and other users wish to sell You can accept applications for purchases of tickets that you have. For this purpose, the website providing unit 210 transmits a web page described in HTML (HyperText Markup Language) or the like to the portable terminal 100 used by the user U, and the input result or the like by the user U is transmitted to the portable terminal. Receive from 100. The website providing unit 210 includes a user screen transmission unit 211, an authentication unit 213, a purchaseable ticket information acquisition unit 215, a ticket purchase application reception unit 217, a settlement information reception unit 219, a possessed ticket information acquisition unit 221, and a ticket sale application reception unit. 223 and a ticket status confirmation unit 225.

  The user screen transmission unit 211 creates and transmits an appropriate web page to the portable terminal 100 operated by the user U. Specifically, for example, a list screen of tickets to be sold (a list of tickets sold by a service provider or event organizer or a list of tickets that have been applied for sale by a user UA who wants to sell), purchase or sale of tickets The user screen transmission unit 211 transmits various web pages related to an application screen for requesting a screen, a screen indicating various notes / confirmations, and the like to the browser of the portable terminal 100.

  The authentication unit 213 performs an authentication process for the user U who has accessed the website of the website providing unit 210. More specifically, for example, the user U is requested to input a user ID and password, and whether or not the user ID and password input from the user U match those managed as user information 281 in the DB 280. The authentication unit 213 confirms. When the user registration by the user U is not performed, the authentication unit 213 prompts the user U to register a new member through the website display screen provided by the website providing unit 210. When the user U performs user registration on the screen, the authentication unit 213 assigns a user ID to the user U. For example, on the display screen of the website provided by the website providing unit, or issuance of the message transmitting unit 270 The user ID is notified to the portable terminal 100 through the message to be transmitted. In this case, various information related to the user U such as the assigned user ID is stored in the DB 280 as user information 281.

  The purchaseable ticket information acquisition unit 215 acquires ticket information that can be purchased by the user U from the ticket management data 283 and the ticket status information 285 of the DB 280. Tickets that can be purchased by the user U include tickets that are sold by the service provider or ticket organizer, as well as tickets that are requested for sale by the user UA who wants to sell. Information on tickets that can be purchased by the user U acquired by the purchaseable ticket information acquisition unit 215 is processed by the user screen transmission unit 211 and then transmitted to the portable terminal 100 of the user U as a web page.

  The ticket purchase application reception unit 217 receives a purchase application for the ticket selected by the user U from the portable terminal 100 of the user U. At this time, when the user U who applied for the purchase has obtained the purchase right of the ticket (for example, won the ticket), the terminal information (for example, the telephone number) of the terminal that receives the ticket as an electronic ticket is also input. The receiving unit 217 accepts. In this way, by inputting the terminal information of the terminal that receives the electronic ticket before the user U acquires the ticket purchase right, the ticket purchase right (right to receive the ticket) is illegally transmitted to other users. It can be prevented from being resold. Various information received by the ticket purchase application receiving unit 217 is stored in the DB 280 as ticket purchase applicant information 287.

  The payment information receiving unit 219 receives payment information used when the user U purchases a ticket from the portable terminal 100 of the user U. The payment information can include, for example, payment means (payment at a convenience store, credit card payment, etc.), information such as a credit card number, the type of convenience store, and the like. The payment information from the user U may be input either when applying for a ticket purchase or when the user can purchase the ticket (for example, after winning the ticket). However, if the payment information is accepted when the ticket purchase application is made, the user U can receive the ticket immediately when the user U's ticket win is determined, particularly when the user U wishes to pay by credit card. .

  The possessed ticket information acquisition unit 221 acquires the ticket information held by each user U who has accessed the website provided by the website providing unit 210 by referring to the ticket management data 283 of the DB 280. The ticket information held by the user U is processed by the user screen transmission unit 211 and then transmitted to the portable terminal 100 of the user U as a web page.

  The ticket sale application receiving unit 223 receives a sale application for a ticket held by the user U from the portable terminal 100 of the user U. Information of the user U who applied for ticket sales is stored in the DB 280 as ticket sales applicant information 289.

  The ticket status confirmation unit 225 confirms the status of each ticket by referring to the ticket status information 285. The ticket status information 285 includes the issued ticket medium (for example, a paper ticket or an electronic ticket), whether the ticket is being applied for sale, and whether the ticket has been used. Information on whether or not the electronic ticket has been downloaded to the ticket application is included. Therefore, for example, when a ticket application is made by a user, the ticket status confirmation unit 225 determines whether or not the ticket is issued as an electronic ticket. Can check whether it has been downloaded to the ticket application of the user U.

  The ticket status changing unit 230 changes the contents of the ticket status information 285 as necessary. For example, the ticket status changing unit 230 changes the ticket status information 285 when the payment by the ticket purchaser is completed, when downloading of the electronic ticket data is completed, or when a ticket sale application is made.

  The lottery unit 240 determines, for each ticket sold, which purchase requesting user who wants to purchase the ticket is given the purchase right. At this time, for example, the lottery unit 240 can consider whether or not it is desired to purchase a plurality of consecutive tickets and whether or not the purchaser is a member of a fan club. For example, if there are tickets that can be used only by fan club members and tickets that can be used by non-fan club members for the same event, if the purchaser is a fan club member, If the ticket is not a member of the fan club, the lottery may be performed only for tickets that can be used without being a member of the fan club. In this case, information regarding whether or not the user is a member of a fan club can be registered by the user at the time of application (application) for ticket purchase or registration of the user information 281, for example.

  The ticket acquisition request receiving unit 250 receives a ticket data acquisition request from the ticket application of the portable terminal 100. At this time, the ticket acquisition request receiving unit 250 can accept user information for identifying the user, terminal information of the portable terminal 100, and exchange number information for receiving the ticket.

  The ticket data transmission unit 260 transmits ticket data to the portable terminal 100. At this time, the ticket data transmission unit 260 is registered as a ticket receiving terminal in advance by the user who has received the ticket exchange request received with the ticket acquisition request and has obtained the ticket purchase right related to the ticket exchange number. If the received terminal information matches the received terminal information, the ticket data is transmitted to the portable terminal 100.

  The message transmission unit 270 notifies the user U of various messages related to ticket sales and the like as mails and messages of a messenger application. For example, when the user U wins a ticket that has been applied for purchase, the message transmission unit 270 displays information such as a winning fact and an exchange number for receiving the winning ticket by e-mail or a messenger application. Is notified to the user U. In addition, when a ticket that the user U has applied for sale is purchased by another user, the message transmission unit 270 notifies the user U that the sale has been completed. Hereinafter, the case where the message transmission unit 270 notifies a message by mail will be mainly described.

  The DB 280 manages user information 281, ticket management data 283, ticket status information 285, ticket purchase applicant information 287, and ticket sale applicant information 289.

  The user information 281 is various information regarding each user U who uses the ticket service provided by the management server 200. The user information 281 includes the name and address of the user U, gender, information such as a credit card used for payment, a user ID and password used for authentication, identification information related to the portable terminal 100 used, information on purchased tickets, etc. Can be included. Also, the user information includes information on various user types such as information on the fan club to which the user U belongs (for example, fan club members of the artist “XXXXX”), member types (platinum members, gold members, etc.) 281 can also be included.

  The ticket management data 283 is data for managing each ticket issued by the event organizer / service provider for each event, for example. In particular, regardless of whether the issuing medium is a paper ticket or an electronic ticket, the information on the holders of all tickets can be managed by the ticket management data 283. By referring to the ticket management data 283, it is possible to check which ticket U holds legitimately. In addition, the ticket management data 283 includes various information related to tickets, such as performance names, venue names, ticket types, ticket attributes based on user attributes, various deadlines, exchange numbers for receiving tickets, and the like. Can also be included.

  The ticket status information 285 is data for managing various states of issued tickets. The ticket status information 285 includes a medium of each issued ticket (for example, whether it is a paper ticket or an electronic ticket), whether the ticket is being applied for sale, whether the ticket has been used, Information such as whether or not the electronic ticket has already been downloaded to the ticket application is included.

  The ticket purchase applicant information 287 is various information related to the ticket purchase applicant who applied for ticket purchase. The ticket purchase applicant information 287 includes, for example, various types of information related to the payment used by the user U when the user U has acquired the right to purchase a ticket (for example, winning a lottery for ticket purchase). Information related to the settlement includes, for example, settlement means (for example, cash on delivery by courier, credit card settlement, convenience store payment, etc.), settlement information such as credit card number when performing credit card settlement, receipt Information such as means (electronic ticket, receipt at convenience store, courier service, etc.) is included. In addition, the ticket purchase applicant information 287 may include terminal information of the portable terminal 100 used when the ticket purchase applicant and a companion accompanying the ticket purchase applicant receive an electronic ticket. it can. As the terminal information, for example, identification information uniquely assigned to the portable terminal 100, identification information individually assigned to the ticket application, a telephone number assigned to the portable terminal 100, or the like can be used. In the present embodiment, a case where a telephone number is used as terminal information will be mainly described.

  The ticket sale applicant information 289 is various information related to the ticket sale applicant who applied for the ticket sale. The ticket sale applicant information 289 includes, for example, various types of information related to the settlement in which the user U receives the sale amount when the sale of the ticket is established.

(2.2 Functional configuration of ticket application 300)
Next, a functional configuration of the ticket application 300 installed in the portable terminal 100 will be described with reference to FIG. FIG. 3 is a functional block diagram showing a specific example of the functional configuration of the ticket application 300. The ticket application 300 includes an authentication unit 310, a terminal information acquisition unit 320, a ticket acquisition unit 330, a ticket sale application unit 340, a message display unit 350, a browser activation unit 360, and a database (DB) 370.

  For example, when the ticket application 300 is activated, the authentication unit 310 performs authentication processing with the management server 200 using user information such as the user ID and password of the user U. The user information 371 used for the authentication may be requested from the user U at the time of activation, or may be read in advance in the DB 370 at the second and subsequent activations.

  The terminal information acquisition unit 320 acquires terminal information 373 that can include information for identifying the portable terminal 100, such as a telephone number. As a method for acquiring the terminal information 373, for example, reading from the OS, receiving input from the user U, registering as terminal information 373 in the DB 370, or reading terminal information 373 registered in advance in the DB 370 may be considered. It is done.

  The ticket acquisition unit 330 issues a ticket to the management server 200 in response to an operation input from the user U related to receipt of the ticket (for example, an input of a ticket exchange number notified to the user who has obtained the ticket purchase right). A data transmission request is transmitted, and ticket data that can be received by the user U is received from the management server 200. The transmission request can include part of user information 371 and terminal information 373 for identifying the user U and the portable terminal 100. The received ticket data is stored in the DB 370 as ticket information 375.

  The ticket sale application unit 340 applies to the management server 200 for sale of the electronic ticket stored as the ticket information 375 in the DB 370 according to, for example, a user operation. When the application is made, the status of the ticket information 375 in the DB 370 becomes “pending sale”, and the user U cannot use the electronic ticket unless the application is canceled.

  The message display unit 350 displays various warnings and messages for confirmation to the user U. For example, the message display unit 350 displays a message indicating that a ticket sale is being applied, a message for confirming whether or not the sale is actually performed, and the like.

  The browser activation unit 360 activates a browser on the portable terminal 100. For example, after the ticket sale application unit 340 makes a ticket sale application to the management server 200, the browser activation unit 360 activates the browser, and the browser displays a transaction explanation screen or a final confirmation screen as a web page. it can.

  The DB 370 manages various types of information including user information 371, terminal information 373, and ticket information 375.

  The user information 371 is information related to the user account of the user U who uses the ticket application 300. As user information 371, information, such as a user ID and a password, can be included, for example. As described above, the authentication unit 310 performs authentication with the management server 200 using the user information 371.

  The terminal information 373 is identification information uniquely assigned to the portable terminal 100 or the ticket application 300. The management server 200 can identify the portable terminal 100 used by the user U by referring to the terminal information 373. In this embodiment, a telephone number is used as the terminal information 373 as described above. By making the user U register the telephone number of the ticket receiving terminal in advance when applying for the ticket purchase, it is possible to prevent the portable data terminal 100 having a different telephone number from receiving ticket data when receiving the ticket. it can.

  The ticket information 375 is various information related to an electronic ticket that can be used or used by the user U. The ticket information 375 can include, for example, information such as a performance name, a venue name, a ticket type, a ticket type based on an attribute of a user to be used, an image to be displayed as an electronic ticket, a validity period, and the like. In addition, the ticket information 375 can include a cutting operation pattern for performing a cutting process, authentication information, and the like. As described above, the ticket acquisition unit 330 acquires the ticket information 375 from the management server 200.

(3 Process flow)
Hereinafter, the processing flow of the ticket system 1 will be described with reference to FIGS. 4, 5, and 7. 4 and 5 are flowcharts showing the flow of processing of the ticket system 1 according to the present embodiment.

  Each processing step to be described later can be executed in any order or in parallel as long as there is no contradiction in processing contents, and other steps can be added between the processing steps. good. Further, a step described as a single step for convenience can be executed by being divided into a plurality of steps, and a step described as being divided into a plurality of steps for convenience can be executed as one step.

(3.1 Processing when applying for sale of electronic tickets)
First, the flow of processing relating to a sale application for an electronic ticket held will be described with reference to FIG. FIG. 4 is a flowchart showing a processing flow of the ticket system 1 related to the application for selling the electronic ticket.

  In the example of FIG. 4, a browser 110 and a ticket application 300 are installed in the portable terminal 100. Further, it is assumed that the user U has already purchased one or more electronic tickets. Note that, as described above, the browser 110 used by the user U when applying for an electronic ticket sale does not necessarily have to be on the portable terminal 100 in which the ticket application 300 is installed. For example, it is conceivable to make a sale application relating to a previously purchased ticket using a browser of a personal computer (PC).

  The user U accesses the ticket service site provided by the management server 200 using the browser 110 of the portable terminal 100 (S401). The website providing unit 210 of the management server 200 receives the access and transmits a web page corresponding to the accessed URL to the portable terminal 100 (S403). For example, in response to a user operation on the web page, the browser 110 of the portable terminal 100 performs a login process with the management server 200 (S405 and S407). More specifically, for example, the management server 200 that receives an input of a user ID and password from the user U on the browser 110 may collate the user ID and password managed on the user information 281. . At this time, if the user U has not performed user registration for the ticket service, the management server 200 may perform member registration processing for the user U.

  Thereafter, for example, when the management server 200 receives a viewing request for the list screen of the owned tickets of the user U from the portable terminal 100 in response to the operation of the user U on the browser 110, the owned ticket information acquisition unit 221 Information of the possessed tickets is extracted from the ticket management data 283. The user screen transmission unit 211 generates a web page related to the list screen in which the information of the possessed ticket is listed, and transmits the web page to the portable terminal 100 (S409). The browser 110 that has received the web page of the list screen displays the list screen on the display (S411).

  After that, when the selection of the ticket to be sold is received from the user U on the browser 110 on the list screen or the individual ticket details screen (S413), the browser 110 inquires the management server 200 about the status of the ticket. This is performed (S415). Upon receiving the inquiry, the ticket status confirmation unit 225 of the management server 200 confirms whether the ticket to be sold is an electronic ticket or an electronic ticket, and confirms whether the ticket has been received by the ticket application 300. Is sent back to the portable terminal 100 as a web page (S417).

  When the ticket application 300 has not received an electronic ticket (including a case where a ticket is issued as a paper ticket; No in S419), the browser 110 requests the management server 200 for a ticket sale application (S421). ). Upon receiving the request, the ticket sale application receiving unit 223 of the management server 200 confirms whether or not the user is a valid ticket holder with reference to the ticket status information 285 and then relates to the corresponding ticket. The ticket status information 285 is changed during acceptance of the sale application (S423).

  On the other hand, when the ticket application 300 has received an electronic ticket (Yes in S419), the browser 110 displays a message that prompts the user U to start the ticket application 300 based on the web page from the management server 200. (S425). The ticket application 300 is activated in response to an operation by the user U that has received the message, and after the login process is completed (S427), when an operation input for applying for ticket sales is received from the user U, the ticket sale of the ticket application 300 is performed. The application unit 340 requests the management server 200 to apply for ticket sales (S429). In response to the request, the ticket sale application receiving unit 223 of the management server 200 changes the ticket status information 285 related to the relevant ticket to accept the sale application (S423). After requesting to sell a ticket, the browser activation unit 360 of the ticket application 300 activates the browser 110 (S431).

  When a ticket sale application is made on the browser 110 or the ticket application 300, the management server 200 transmits a web page of a transaction explanation screen or a final confirmation screen to the portable terminal 100 (S433), and the browser 110 displays those screens. Is displayed on the display (S435). When the user selects the confirmation button on the final confirmation screen, the browser 110 makes a formal sale application to the management server 200 (S437). The management server 200 that has received the sale application updates the status of the corresponding ticket managed by the ticket status information 285 from the sale application acceptance to the sale application (S439). Then, the management server 200 transmits a web page related to the sales application completion screen to the portable terminal 100 (S441). Based on the received web page, the browser 110 displays a sale application completion screen on the display (S443). In addition, the management server 200 transmits a sale transmission completion email or message to a user U email address or message destination registered in advance (S445).

(3.2 Processing when applying for electronic ticket purchase)
Next, a flow of processing related to an application for purchasing an electronic ticket by the user U will be described with reference to FIG. FIG. 5 is a flowchart showing a processing flow of the ticket system 1 related to the electronic ticket purchase application.

  Note that the ticket that the user U applies for purchase may be a ticket that an event organizer or service provider intends to sell, or a ticket that is held by another user and that is applied for sale. It doesn't matter. The following description will focus on the flow of processing when the user U purchases a ticket for which another user has applied for sale.

  As described above, the browser 110 used when the user U applies for an electronic ticket purchase does not necessarily have to be on the portable terminal 100. For example, it is conceivable to make a purchase application using a browser of a personal computer.

  The user U accesses the ticket service site provided by the management server 200 using the browser 110 of the portable terminal 100 (S501). The website providing unit 210 of the management server 200 receives the access and transmits a web page corresponding to the accessed URL to the portable terminal 100 (S503). For example, in response to a user operation on the web page, the browser 110 of the portable terminal 100 performs a login process with the management server 200 (S505 and S507). More specifically, for example, the management server 200 that receives an input of the user ID and password from the user U on the browser 110 and receives it from the browser 110 checks the user ID and password managed on the user information 281. Just do it. At this time, if the user U has not performed user registration for the ticket service, the member registration process of the user U may be performed between the browser 110 and the management server 200.

  Thereafter, when the management server 200 receives from the portable terminal 100 a browsing request for the list screen of the purchaseable tickets, for example, according to the operation of the user U on the browser 110, the purchaseable ticket information acquisition unit 215 causes the user to purchase the purchaseable ticket information. Information on tickets that U can purchase is extracted from the ticket management data 283. At this time, the ticket that can be purchased by the user U includes either or both of a ticket sold by an event organizer or a service provider and a ticket that another user who holds the ticket applies for sale. be able to. At this time, the tickets that can be purchased can be changed according to the user type of the user U. Specifically, for example, if the user U is a member of a fan club of a specific musician after referring to the user information 281 related to the user U, a ticket for the fan club-limited event of the musician, The ticket can be a ticket that can be purchased by the user U. On the other hand, the user U who is not a member of the fan club may make a ticket that can be purchased only for the general public other than the fan club limited event. The user screen transmission unit 211 generates a web page related to a list screen that lists information on tickets that can be purchased by the user U acquired by the purchaseable ticket information acquisition unit 215 and transmits the generated web page to the portable terminal 100. (S509). The browser 110 that has received the web page of the list screen displays the list screen on the display (S511).

  Thereafter, when the browser 110 receives a selection of a purchase application target ticket from the user U on the list screen or the individual ticket details screen, the browser 110 notifies the management server 200 of the selection (S513). . When the ticket purchase application reception unit 217 of the management server 200 receives the notification, the user screen transmission unit 211 displays a web page related to a registration screen for information regarding the purchase applicant and, if necessary, a companion, on the portable terminal 100. (S515). The browser 110 of the portable terminal 100 displays a registration screen for information on the purchase requester and / or accompanying person (S517).

  6a and 6b show specific examples of registration screens 60a and 60b (hereinafter also collectively referred to as registration screen 60) of purchase applicant (applicant) information and companion information. FIG. 6A is a specific example of a purchase applicant information registration screen 60a, and FIG. 6B is a specific example of a companion information registration screen 60b. As shown in FIGS. 6a and 6b, on each registration screen, the e-mail address, full name (first name and last name) of the applicant and accompanying person, and the reading pseudonym are respectively displayed in text boxes 61a and 61b, 63a and 63b, and 65a and 65b can be input. In addition, the telephone number can be registered in the text boxes 67a and 67b. This telephone number information is terminal information for identifying the portable terminal 100 that receives the purchased ticket as an electronic ticket. In this way, by receiving registration of a telephone number at the time of application, it is possible to prevent resale or the like of a user account to a third party after winning a ticket.

  When the user U also purchases various information related to the user U who is a purchase requester, the telephone number related to the ticket receiving terminal, and the companion ticket on the registration screen 60 of such purchase requester information and companion information In step S519, the browser 110 transmits the information to the management server 200 after registering the various information related to the accompanying person and the telephone number related to the ticket receiving terminal. The ticket purchase application reception unit 217 of the management server 200 that has received the information registers the information received by the ticket purchase application reception unit 217 in the DB 280 as ticket purchase application information 287 (S521).

  Further, the user screen transmission unit 211 of the management server 200 transmits a web page related to a payment information registration screen that prompts registration of payment information used by the user U to the portable terminal 100 when the ticket is won (S523). The browser 110 displays a payment information registration screen based on the received web page (S525), and receives payment information input from the user U (S527). The payment information includes the type of payment used by the user U when the ticket is won (cash on delivery by courier, payment by credit card, payment at a convenience store, etc.), credit card number and expiration date for payment by credit card Information, convenience store line information, and the like may be included when payment is made at a convenience store.

  When the user presses the registration button on the payment information registration screen, for example, the browser 110 transmits the input payment information to the management server 200 (S527). The settlement information receiving unit 219 of the management server 200 registers the received settlement information in the DB 280 as a part of the ticket purchase applicant information 287 (S529).

  In this way, after receiving a ticket purchase application (application) from one or more users U, when the predetermined lottery time comes (S531), the lottery unit 240 of the management server 200 determines which ticket purchase right to which A lottery for determining whether to give to the user U is performed (S533). Then, an email for notifying the lottery result is sent to the user U who is each purchase applicant, for example, to an email address registered in advance on the registration screen 60 (S535). At this time, the message transmission unit 270 can describe information on the exchange number necessary for receiving the ticket in the mail transmitted to the user U who is the winner of the ticket. Note that the message transmission means does not necessarily need to be an e-mail, and may be, for example, a message of a messenger application that can send and receive messages in real time.

  Thereafter, when the settlement is completed (Yes in S537), the management server 200 changes the ticket owner in the ticket management data 283 from the ticket sale applicant to the ticket purchase applicant (S539). For example, in the case of credit card payment, the completion of payment is the completion of payment processing with a payment service provided by a payment company using a credit card number registered in advance as payment information, a convenience store or a courier service. By receiving a notification to that effect from the merchant payment server, the management server 200 can grasp it. In addition, the ticket sale applicant is paid a ticket sale price (a fee may be deducted).

(3.3 Electronic ticket receipt processing)
A flow of processing when the user U receives a winning ticket (having a purchase right) as an electronic ticket will be described with reference to FIG. FIG. 7 is a flowchart showing a flow of processing of the ticket system 1 related to receipt of the electronic ticket.

  When the ticket application 300 of the portable terminal 100 is activated in response to a user U operation or the like (S701), the authentication unit 310 of the ticket application 300 performs an authentication process with the authentication unit 213 of the management server 200 (S703 and S705). At this time, the authentication unit 310 of the ticket application 300 may receive a user ID and password input from the user U as necessary, or the user ID and password information registered in the DB 370 as user information 371 in advance. It may be used.

  Thereafter, for example, when the user U operates a ticket receiving button or the like, the ticket application 300 starts a ticket receiving process (Yes in S707). Specifically, the ticket acquisition unit 330 first requests the user U to input a ticket exchange number (S709). When the telephone number (terminal information) is not registered in the DB 370 of the ticket application 300, the terminal information acquisition unit 320 acquires the telephone number of the portable terminal 100 (S713). Specifically, when the telephone number information can be acquired from the OS, the terminal information acquisition unit 320 acquires the telephone number information from the OS. Further, when the telephone number information cannot be read from the OS, the terminal information acquisition unit 320 may request the user U to input the telephone number of the portable terminal 100. In addition, the validity of the telephone number may be confirmed using SMS (Short Message Service) for the telephone number input at that time.

  When the information on the exchange number and the telephone number is obtained, the ticket acquisition unit 330 of the ticket application 300 transmits a ticket acquisition request including the information and user information to the management server 200. When receiving the ticket acquisition request (S717), the ticket acquisition request receiving unit 250 of the management server 200 reads the ticket purchase applicant information 287 of the DB 280 related to the winner of the ticket corresponding to the exchange number (S719). As a result, the ticket data transmission unit 260 confirms whether the telephone number (terminal information) and user information registered in advance as relating to the ticket receiving terminal and the received telephone number and user information match. (S721). If the telephone number and the user information do not match (No in S721), the ticket data transmission unit 260 transmits an error message to the portable terminal 100 (S723). When the telephone number or user information received in the ticket acquisition request matches the telephone number or user information registered in advance as relating to the ticket receiving terminal (Yes in S721), the ticket data transmission unit 260 Transmits ticket data (S725).

  When the ticket application 300 of the portable terminal 100 receives the ticket data from the management server 200 (Yes in S727), the message display unit 350 displays a message indicating that the ticket has been received (S729). If the ticket has been applied for sale from another user, the other user is notified of the fact that the ticket has been sold by e-mail or a message on the ticket application. .

On the other hand, when the ticket application 300 receives an error message from the management server 200 (No in S727), the message display unit 350 displays the error message (S731).

(4 hardware configuration)
Hereinafter, a hardware configuration capable of realizing the management server 200 and the portable terminal 100 will be described with reference to FIGS. 8 and 9.

(4.1 Management Server 200)
First, a hardware configuration capable of realizing the management server 200 will be described with reference to FIG. FIG. 8 is a diagram illustrating a specific example of a hardware configuration capable of realizing the management server 200. As shown in FIG. 8, the management server 200 includes a control unit 801, a communication I / F (interface) unit 805, a storage unit 807, a display unit 811, and an input unit 813, and each unit is a bus line 815. Connected through.

  The control unit 801 includes a CPU (Central Processing Unit. Not shown), a ROM (Read Only Memory. Not shown), a RAM (Random Access Memory) 803, and the like. By executing a control program 809 stored in the storage unit 807, the control unit 801 is configured to be able to realize the above-described processing related to the ticket service in addition to the function as a general information processing apparatus. For example, the website providing unit 210, the ticket status changing unit 230, the lottery unit 240, the ticket acquisition request receiving unit 250, the ticket data transmitting unit 260, and the message transmitting unit 270 described with reference to FIG. 2 are temporarily stored in the RAM 803. In addition, it can be realized as a control program 809 operating on the CPU.

  In addition to the code included in the control program 809, the RAM 803 stores part of the user information 281, ticket management data 283, ticket status information 285, ticket purchase applicant information 287, and ticket sale applicant information 289 shown in FIG. Or keep everything temporarily. The RAM 803 is also used as a work area when the CPU executes various processes.

  The communication I / F unit 805 is a device for performing data communication with an external apparatus including the portable terminal 100 via a wired or wireless network N. The communication I / F unit 805 performs all communications performed by the website providing unit 210, the ticket acquisition request receiving unit 250, the ticket data transmitting unit 260, and the message transmitting unit 270 shown in FIG. Do.

  The storage unit 807 is a nonvolatile storage medium such as an HDD (Hard Disk Drive) or a flash memory. The storage unit 807 stores an operation system (OS) and data (not shown) for realizing a function as a general information processing apparatus. The storage unit 807 stores a control program 809 and a DB 280.

  The control program 809 is a program for performing processing related to the above ticket service. As described above, the website providing unit 210, the ticket status changing unit 230, the lottery unit 240, the ticket acquisition request receiving unit 250, the ticket data transmitting unit 260, and the message transmitting unit 270 shown in FIG. obtain.

  The DB 280 can include various data necessary for providing an electronic ticket service, such as user information 281, ticket management data 283, ticket status information 285, ticket purchase applicant information 287, and ticket sale applicant information 289. Various data included in the DB 280 is loaded into the RAM 803 as necessary, and is referred to by the CPU included in the control unit 801.

  The display unit 811 is a display device for presenting information to the service provider. Specific examples of the display unit 811 include a liquid crystal display and an organic EL (Electro-Luminescence) display. The input unit 813 is a device for receiving input from a service provider. Specific examples of the input unit 813 include a keyboard, a mouse, and a touch panel.

  The management server 200 does not necessarily include the display unit 811 and the input unit 813. The display unit 811 and the input unit 813 may be connected to the management server 200 from the outside via various interfaces such as a USB (Universal Serial Bus) and a display port.

(4.2 Portable terminal 100)
Next, a hardware configuration capable of realizing the portable terminal 100 will be described with reference to FIG. FIG. 9 is a diagram illustrating a specific example of the hardware configuration of the portable terminal 100. As shown in FIG. 9, the portable terminal 100 includes a control unit 151, a communication interface (I / F) unit 155, a storage unit 157, a touch panel display 159, and an input unit 165, and each unit is a bus line. 167 is connected.

  The control unit 151 includes a CPU, a ROM, a RAM 153, and the like. The control unit 151 can execute the ticket application 300, the browser 110, and the mail application 120 stored in the storage unit 157. Thereby, in addition to the function as a general information processing apparatus, the portable terminal 100 can implement various processes related to the ticket service described above.

  The RAM 153 temporarily stores part or all of the user information 371, terminal information 373, and ticket information 375 shown in FIG. 3 in addition to the codes included in the ticket application 300, the browser 110, and the mail application 120. To do. The RAM 153 is also used as a work area when the CPU executes various processes.

  The communication I / F unit 155 is a device for performing data communication with an external apparatus including the management server 200 via a wired or wireless network N. The communication I / F unit 155 performs all communications performed by the authentication unit 310, the terminal information acquisition unit 320, the ticket acquisition unit 330, the ticket sale application unit 340, and the like illustrated in FIG.

  The storage unit 157 is a non-volatile storage medium such as an HDD or a flash memory. The storage unit 157 stores an operation system (OS), applications, and data (not shown) for realizing a function as general information processing. The storage unit 157 stores the ticket application 300, the browser 110, and the mail application 120.

  The browser 110 is an application program that allows the user U to browse various websites on the network N including the ticket service site provided by the management server 200.

The mail application 120 is an application program for the user U to send and receive messages to and from the management server 200 and other users. In addition to or in addition to the mail application 120, a messenger application that has a relatively high real-time property and can exchange short messages can be stored in the storage unit 157 and executed by the control unit 151. It is good.
Since the ticket application 300 has been described above with reference to FIG. 3, the description thereof is omitted here.

  The touch panel display 159 is a device in which a display unit 161 that is a display device that presents information and a touch panel unit 163 that receives an operation input are mounted in an overlapping manner. By using the touch panel display 159, the user U can obtain an intuitive operational feeling as if he / she directly operated the display content displayed on the display unit 161.

  The input unit 165 is a device provided separately from the touch panel display 159 for accepting an operation input from the user U. Specific examples of the input unit 165 include operation buttons, a keyboard, a mouse, and the like.

  Note that the portable terminal 100 does not necessarily include the input unit 165. The input unit 165 may be connected to the portable terminal 100 from the outside via various interfaces such as USB (Universal Serial Bus) and Bluetooth (registered trademark).

(5. Effects of the present embodiment)
As described above, in the ticket system 1 according to this embodiment, when the user U applies for ticket purchase, the user U receives input of terminal information related to a terminal that receives an electronic ticket. That is, since the terminal that can receive the ticket is determined before the user U obtains the ticket purchase right, after the user U obtains the ticket purchase right, the ticket receipt right is given to another user. It can be prevented from being resold freely.

  On the other hand, on the ticket service provided by the management server 200, it is possible to apply for sale of a purchased ticket and purchase application for a ticket for which another user has applied for sale. As a result, even when the user U's ticket is no longer necessary due to, for example, a schedule change, other users can purchase and use it. Further, at this time, the management server 200 mediates the buying and selling, thereby preventing the buying and selling of tickets at an unreasonably high price.

  Further, the management server 200 manages data of all holders of issued tickets in the ticket management data 283. Thereby, it is possible to confirm whether or not the user U who wants to sell the ticket is a valid ticket holder regardless of whether the ticket is a paper ticket or an electronic ticket.

(6 Appendix)
Note that the configurations of the above-described embodiments may be combined or some components may be replaced. The configuration of the present invention is not limited to the above-described embodiment, and various modifications may be made without departing from the scope of the present invention.

1: Ticket system 100: Portable terminal 200: Management server 210: Website providing unit 211: User screen transmission unit 213: Authentication unit 215: Purchaseable ticket information acquisition unit 217: Ticket purchase application reception unit 219: Settlement information reception unit 221: Holding ticket information acquisition unit 223: Ticket sale application reception unit 225: Ticket status confirmation unit 230: Ticket status change unit 240: Lottery unit 250: Ticket acquisition request reception unit 260: Ticket data transmission unit 270: Message transmission unit 280: Database (DB)
300: Ticket application 310: Authentication unit 320: Terminal information acquisition unit 330: Ticket acquisition unit 340: Ticket sale application unit 350: Message display unit 360: Browser activation unit 370: Database (DB)
N: Network

Claims (6)

Accepting means for accepting user information for identifying a user, inputted from one or more users applying for an electronic ticket, and terminal information for identifying a ticket receiving terminal from which the user receives the electronic ticket;
Means for identifying a target user who can use the electronic ticket among the one or more users;
From different applications and the browser of the user terminal operated by the user, Yu chromatography The has registered the application, the user information for identifying the user, the application is read from the user terminal operation system (OS) However, means for receiving terminal information for specifying the user terminal,
It matches the user information that the user information according to the target user that a user information the user has registered the application received from the user terminal, the application to a terminal information received from the user terminal read from OS An information processing system comprising: a first transmission unit configured to transmit ticket data related to the electronic ticket to the application of the user terminal when the terminal information matches the terminal information related to the ticket receiving terminal of the target user. The accepting means identifies user information for identifying a companion in addition to user information and terminal information relating to a user who applies for the electronic ticket, and the ticket receiving terminal from which the companion receives the electronic ticket. Receiving device information for
The information processing system according to claim 1. Second transmission means for transmitting an exchange number for receiving the electronic ticket to the target user;
Means for receiving an input of the exchange number from a user terminal;
The first transmission means, when the user information received from the user terminal, the terminal information, and the exchange number match those related to the target user and the ticket receiving terminal of the target user, the ticket data Sending to the application of the user terminal,
The information processing system according to claim 1 or 2. The accepting means accepts input of an email address as the user information,
The second transmission means transmits the exchange number to the mail address of the target user.
The information processing system according to claim 3. Receiving user information for identifying a user, input from one or more users applying for an electronic ticket, and terminal information for identifying a ticket receiving terminal from which the user receives the electronic ticket;
Identifying a target user who can use the electronic ticket among the one or more users;
From different applications and the browser of the user terminal operated by the user, Yu chromatography The has registered the application, the user information for identifying the user, the application is read from the user terminal operation system (OS) However, receiving the terminal information for identifying the user terminal,
It matches the user information that the user information according to the target user that a user information the user has registered the application received from the user terminal, the application to a terminal information received from the user terminal read from OS An information processing method in which an information processing system performs a step of transmitting ticket data related to the electronic ticket to the application of the user terminal when the terminal information matches the terminal information related to the ticket receiving terminal of the target user. A process of receiving user information for identifying a user input from one or more users who apply for an electronic ticket, and terminal information for identifying a ticket receiving terminal from which the user receives the electronic ticket;
A process of identifying a target user who can use the electronic ticket among the one or more users;
From different applications and the browser of the user terminal operated by the user, Yu chromatography The has registered the application, the user information for identifying the user, the application is read from the user terminal operation system (OS) However, the process of receiving terminal information for identifying the user terminal,
The user information received from the user terminal and registered by the user in the application matches the user information related to the target user, and the terminal information received from the user terminal and read by the OS from the application If the terminal information matches the terminal information relating to the ticket receipt terminal of the target user, a program for executing a process of transmitting the ticket data relating to the electronic ticket to the application of the user terminal to the information processing system .

Images