Information processing device, information processing system, information processing method, and program

Abstract

The present invention is to realize a configuration for easily and reliably executing the transfer of tickets between a ticket transfer terminal and a ticket usage terminal. The present invention is provided with a ticket transfer terminal, a ticket usage terminal, and a ticket management server, wherein the ticket transfer terminal registers, in a database of the ticket management server, data about (a) the type of ticket to be transferred and an identifier, (b) an IC card identifier (ID) registered in a ticket usage terminal which is the ticket transfer destination, and (c) a ticket transfer notification condition for the ticket usage terminal. When it is determined that the ticket usage terminal satisfies the ticket transfer notification condition registered in the database, the server transmits to the ticket usage terminal a ticket transfer notification indicating that the transfer ticket can be received, and transmits to the ticket usage terminal a ticket in response to the reception of a request for transfer from the ticket usage terminal.

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device, an information processing system, an information processing method, and a program. More specifically, the present disclosure relates to an information processing device, an information processing system, an information processing method, and a program that perform a process of transferring various tickets such as train tickets and coupons using a user terminal such as a smartphone. [Background technology]

[0002] In recent years, the use of mobile user devices such as smartphones with cashless payment functions has been expanding. By using a user terminal with cashless payment functionality, it becomes possible to pay for shopping, dining, etc., or to pay for train and bus fares and use commuter passes using the user terminal without having to carry cash.

[0003] Furthermore, if tickets such as train or bus tickets, reserved seat tickets, multiple-ride tickets, amusement park admission tickets, or reserved seat tickets for theaters are purchased in advance via the Internet and downloaded to a user device such as a smartphone, the ticket information can be read and the ticket can be used by holding the user device over a reading device at a ticket gate or entrance gate.

[0004] For example, a single user can purchase tickets for multiple people online at once, such as train tickets for a group trip or a business trip with multiple people. However, in this case, unless the purchased ticket information is recorded on the user terminal of each user who will actually use the ticket, each user will not be able to use the ticket even if they hold their user terminal over a reading device at a ticket gate or entrance gate.

[0005] A conventional technique that discloses a configuration for solving such a problem is, for example, Patent Document 1 (Japanese Patent Laid-Open Publication No. 2013-206214). Patent Document 1 discloses a configuration in which user A transfers a limited express ticket registered in association with his / her own IC card a to IC card b of user B. Specifically, user A registers the identifier of IC card b of user B, to whom the limited express ticket will be transferred, in a server, and notifies user B of the limited express ticket identifier. The limited express ticket identifier of the limited express ticket purchased by user A is registered in the server.

[0006] User B inserts his / her IC card b into the ticket machine and inputs the express ticket identifier notified by User A. The server compares the identifier of IC card b and the input express ticket identifier with the information registered on the server, and if the comparison is successful, it registers the express ticket as data associated with IC card b. In other words, it sets up the express ticket to be usable when passing through the ticket gate with IC card b.

[0007] However, with this method, user B needs to remember the express ticket identifier notified by user A, and must enter the express ticket identifier correctly into the ticket machine. This also creates the problem that if user B forgets the express ticket identifier, the ticket will no longer be usable. There are also the following challenges: Issue 1: The need to renovate infrastructure such as ticket vending machines is an obstacle to introducing the service. Problem 2: User B, who wants to receive the ticket, needs to go to the ticket vending machine in advance to receive the ticket. Issue 3: User A, who hands over the ticket, must determine in advance that User B, who will receive the ticket, is the only person. This cannot be used, for example, when the participants in a group trip or multiple business travelers are not confirmed until the day of the trip, or when a multiple-ride ticket or express ticket is handed over so that it can be used at any time by any of the group or multiple business travelers.

[0008] The above-mentioned issues 1 and 2 are partially resolved by smartphones equipped with IC chips that have contactless IC card functionality. Specifically, User A, who hands over the ticket, operates his / her smartphone to notify User B, who will receive the ticket, via email or app that the ticket will be handed over. User B, who receives the ticket, then operates his / her smartphone to confirm the notification and use the smartphone's communication function to securely download the ticket from the server to the smartphone's IC chip in advance. As a result, both User A, who hands over the ticket, and User B, who receives the ticket, can simply operate their smartphones, eliminating the need to go to a ticket vending machine to hand over or receive the ticket, and eliminating the need to modify infrastructure such as ticket vending machines. However, there is the following issue 4.

[0009] Issue 4: When receiving a ticket via smartphone as described above, the receiving user B must be aware of the notification and must operate the smartphone in a planned manner to download the ticket; if they forget, they may not be able to receive the ticket and may not be able to use it (for example, to board an express train). However, if the ticket is downloaded too early in advance, in the event of a sudden change in plans, the downloaded ticket must be returned to user A, who can then refund it or give it back to someone else on a group trip or business trip, which involves a cumbersome process and effort. Therefore, for example, in the case of an express ticket, there is an issue of making it possible for user B to receive the ticket after it is certain that the ticket will be used, such as after user B has passed through the ticket gate at the nearest station to user B on the day of the trip or business trip.

[0010] Patent Document 2 (International Publication No. WO2019 / 123851 A1) discloses the following configuration: When a smartphone equipped with an IC chip with contactless IC card functionality is held over a ticket gate, the smartphone detects the amount and balance paid with electronic money stored in the contactless IC card stored in the smartphone, the identifier of the ticket gate, and other information from the content of the proximity communication between the smartphone and the ticket gate, and displays the fact that the ticket gate has been passed, the amount paid, the balance, and other information on the smartphone screen. However, with this configuration, passing through the ticket gate does not trigger the collection of a ticket. [Prior art documents] [Patent documents]

[0011] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-206214 [Patent Document 2] International Publication: WO2019 / 123851 Summary of the Invention [Problem to be solved by the invention]

[0012] The present disclosure has been made in consideration of, for example, the above-mentioned problems 3 and 4, and aims to provide an information processing device, an information processing system, an information processing method, and a program that enable various tickets such as train passes and coupons to be easily transferred between user terminals. [Means for solving the problem]

[0013] A first aspect of the present disclosure provides: a storage unit for storing ticket transfer notification conditions; a data processing unit that receives a request from a ticket use terminal and, if the ticket transfer notification condition is met, instructs the ticket use terminal to write ticket information; The information processing device has:

[0014] Furthermore, a second aspect of the present disclosure is The IC card identifier (ID) recorded in the ticket usage terminal is received from the ticket transfer destination terminal, The information processing device has a data processing unit that transmits the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and the ticket transfer notification conditions for the ticket use terminal to a ticket management server.

[0015] Furthermore, a third aspect of the present disclosure is A ticket transfer notification is received from the ticket management server, indicating that the transfer ticket can be received, and a confirmation message is displayed on the display unit asking whether or not to receive the ticket. Sending the user's confirmation response to the ticket management server; If the user's confirmation response is a response indicating ticket receipt, the information processing device has a data processing unit that receives the transfer ticket from the ticket management server.

[0016] Furthermore, a fourth aspect of the present disclosure is An information processing system having a ticket transfer terminal, a ticket use terminal, and a ticket management server, The ticket transfer terminal (a) the type or identifier of the ticket being transferred; (b) the conditions for notifying the ticket transfer to the ticket use terminal; Sending the above data (a) to (b) to the ticket management server; The ticket management server The data (a) to (b) received from the ticket transfer terminal are registered in a database; The ticket use terminal determines whether or not the ticket transfer notification conditions registered in the database are satisfied; When the ticket use terminal determines that the ticket transfer notification conditions are met, the information processing system transmits to the ticket use terminal a ticket transfer notification indicating that the transfer ticket can be received.

[0017] Furthermore, a fifth aspect of the present disclosure is An information processing method executed in an information processing device, a data processing unit of the information processing device, The information processing method receives a request from a ticket use terminal, and if the request matches the ticket transfer notification conditions stored in the storage unit, instructs the ticket use terminal to write ticket information.

[0018] Furthermore, a sixth aspect of the present disclosure is An information processing method executed in an information processing device, a data processing unit of the information processing device, The IC card identifier (ID) recorded in the ticket usage terminal is received from the ticket transfer destination terminal, The information processing method includes transmitting the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal to a ticket management server.

[0019] Furthermore, a seventh aspect of the present disclosure is An information processing method executed in an information processing device, a data processing unit of the information processing device, A ticket transfer notification is received from the ticket management server, indicating that the transfer ticket can be received, and a confirmation message is displayed on the display unit asking whether or not to receive the ticket. Sending the user's confirmation response to the ticket management server; If the user's confirmation response is a response indicating ticket receipt, the information processing method receives the transfer ticket from the ticket management server.

[0020] Furthermore, an eighth aspect of the present disclosure is A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; The program receives a request from a ticket use terminal, and if the request matches the ticket transfer notification conditions stored in the storage unit, instructs the ticket use terminal to write ticket information.

[0021] Furthermore, a ninth aspect of the present disclosure is A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A process of receiving an IC card identifier (ID) recorded in the ticket usage terminal from the ticket transfer destination ticket usage terminal; The program executes a process of transmitting the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and the ticket transfer notification conditions for the ticket use terminal to the ticket management server.

[0022] Furthermore, a tenth aspect of the present disclosure is A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A process of receiving a ticket transfer notification from the ticket management server, indicating that the transfer ticket can be received, and displaying a confirmation message on the display unit asking whether or not to receive the ticket; sending a user confirmation response to the ticket management server; If the user's confirmation response indicates ticket reception, the program executes a process for receiving the transfer ticket from the ticket management server.

[0023] The program of the present disclosure is, for example, a program that can be provided in a computer-readable format via a storage medium or communication medium to an information processing device or computer system capable of executing various program codes. By providing such a program in a computer-readable format, processing according to the program is realized on the information processing device or computer system.

[0024] Further objects, features, and advantages of the present disclosure will become apparent from the following detailed description of the embodiments of the present disclosure and the accompanying drawings. Note that in this specification, a system refers to a logical collective configuration of multiple devices, and is not limited to devices that are housed in the same housing.

[0025] According to the configuration of one embodiment of the present disclosure, a configuration is realized that allows ticket transfer between a ticket transfer terminal and a ticket use terminal to be easily and reliably executed. Specifically, for example, a system may have a ticket transfer terminal, a ticket use terminal, and a ticket management server, and the ticket transfer terminal registers the following data in the ticket management server's database: (a) the type or identifier of the ticket to be transferred, (b) the IC card identifier (ID) recorded in the ticket use terminal to which the ticket is to be transferred, and (c) the ticket transfer notification conditions for the ticket use terminal. If the server determines that the ticket use terminal meets the ticket transfer notification conditions registered in the database, it sends a ticket transfer notification to the ticket use terminal indicating that the transferred ticket is available for receipt, and sends the ticket to the ticket use terminal in response to the transfer request received from the ticket use terminal. This configuration realizes a configuration that allows ticket transfer between the ticket transfer terminal and the ticket use terminal to be easily and reliably executed. The effects described in this specification are merely examples and are not limiting, and additional effects may also be present. [Brief explanation of the drawings]

[0026] [Figure 1] FIG. 1 is a diagram illustrating a configuration example of an information processing system according to the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating a configuration example of an information processing system according to the present disclosure. [Figure 3] FIG. 1 is a diagram illustrating a configuration example of an information processing system according to the present disclosure. [Figure 4] FIG. 10 is a diagram illustrating an example of a card application in a user terminal such as a smartphone owned by a user. [Figure 5]FIG. 10 is a diagram illustrating an example of a card application in a user terminal such as a smartphone owned by a user. [Figure 6] FIG. 10 is a diagram illustrating the configuration of an IC chip in a user terminal. [Figure 7] FIG. 10 is a diagram illustrating the configuration of an IC chip in a user terminal. [Figure 8] 10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 9] 10A and 10B are diagrams illustrating an example of display data (UI) output to a user terminal during the ticket transfer process and transfer ticket usage process of the present disclosure. [Figure 10] 10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 11] 10A and 10B are diagrams illustrating an example of display data (UI) output to a user terminal during the ticket transfer process and transfer ticket usage process of the present disclosure. [Figure 12] 10A and 10B are diagrams illustrating an example of display data (UI) output to a user terminal during the ticket transfer process and transfer ticket usage process of the present disclosure. [Figure 13] 10 is a diagram illustrating an example of recorded data in a ticket transfer processing management database managed by a ticket management server. FIG. [Figure 14] 10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 15] 10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 16] 10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 17] 10A and 10B are diagrams illustrating an example of display data (UI) output to a user terminal during the ticket transfer process and transfer ticket usage process of the present disclosure. [Figure 18]10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 19] 10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 20] 10 is a sequence diagram illustrating a sequence of a ticket transfer process and a transfer ticket usage process according to the present disclosure. FIG. [Figure 21] 10A and 10B are diagrams illustrating an example of display data (UI) output to a user terminal during the ticket transfer process and transfer ticket usage process of the present disclosure. [Figure 22] 10A and 10B are diagrams illustrating an example of a use case of a ticket transfer process and a transfer ticket usage process according to the present disclosure. [Figure 23] 10A and 10B are diagrams illustrating an example of a use case of a ticket transfer process and a transfer ticket usage process according to the present disclosure. [Figure 24] FIG. 1 is a diagram illustrating an example of the configuration of a user terminal such as a smartphone. [Figure 25] FIG. 1 is a diagram illustrating an example of the configuration of a user terminal such as a smartphone or an information processing device such as a server. DETAILED DESCRIPTION OF THE INVENTION

[0027] The information processing device, information processing system, information processing method, and program of the present disclosure will be described in detail below with reference to the drawings. The description will be made according to the following items. 1. Configuration example of information processing system of the present disclosure 2. Applications and IC chips in user devices 3. Specific examples of ticket transfer and usage sequences disclosed herein 3-(1) Data acquisition and storage sequence from ticket use terminal (user terminal b) by ticket transfer terminal (user terminal a) 3-(2) Data transmission from the ticket transfer terminal (user terminal a) to the ticket management server (service provider) and database registration processing sequence in the ticket management server (service provider) 3-(3) The ticket management server (service provider) checks whether the ticket use terminal (user terminal b) satisfies the ticket transfer notification conditions and executes the ticket transfer notification process. 3-(4) Processing sequence when a ticket usage terminal (user terminal b) uses a transfer ticket 4. Various use cases of the ticket transfer process disclosed herein 4-(1) Example of a process where a company distributes tickets to employees 4-(2) Example of a process where a company distributes tickets to customers 4-(3) Example of a process where a campaign organizer distributes tickets to campaign applicants 4-(4) Example of a process in which an advertising entity distributes tickets to members or an unspecified number of customers 5. Configuration examples of information processing devices 6. Summary of the Disclosure

[0028] [1. Configuration example of information processing system disclosed herein] First, a configuration example of an information processing system according to the present disclosure will be described.

[0029] The present disclosure provides a configuration that enables various tickets, such as train tickets, admission tickets, and complimentary tickets, to be easily transferred between user terminals.

[0030] FIG. 1 is a diagram illustrating an example of a configuration of an information processing system according to the present disclosure. Figure 1 shows the following configurations: (1) Ticket transfer user A,10, (2) Ticket transfer terminal (user terminal a) 11; (3) Ticket user B,20, (4) ticket use terminal (user terminal b) 21; (5) Ticket management server (service provider) 50, (6) Ticket usage confirmation device (R / W (reader / writer)) 60,

[0031] In the configuration of the present disclosure, a "ticket" refers to, for example, Train, bus, taxi, airplane and other transportation tickets, express tickets, reserved seat tickets, green tickets, upgrade tickets, multiple-ride tickets, discount tickets, local one-day passes, and complimentary tickets. Admission tickets, complimentary tickets, reserved seat tickets, discount tickets, and accommodation vouchers for amusement parks, theme parks, theaters, cinemas, art galleries, museums, accommodation facilities, events, etc. Gift certificates, coupons, discount coupons, complimentary coupons, and coupons that can be used at stores. Electronic money that can be used at station ticket gates, facility entrance / exit gates, and store payment terminals. For example, it includes various tickets such as these, and may be either paid or free.

[0032] In the embodiments of the present disclosure described below, "transfer" is not limited to one-to-one transfers but also includes one-to-many distributions. Furthermore, there are no restrictions on the payment or fees involved in the "transfer," and it may be either paid or free of charge.

[0033] In addition, the ticket can be written onto an IC chip with contactless IC card functionality installed in the ticket usage terminal (user b) 21 and used by holding it up to an IC card reader, or by reading it with a one-dimensional / two-dimensional barcode reader, or displayed on the screen of the ticket usage terminal (user b) 21 so that store clerks or others can see it.

[0034] A ticket transfer user A 10 shown in FIG. 1 uses a ticket transfer terminal (user terminal a) 11, and a ticket using user B 20 uses a ticket using terminal (user terminal b) 21. These user terminals 11 and 21 are, for example, smartphones.

[0035] A ticket management server (service provider) 50 shown in FIG. 1 is a service provider that provides tickets and manages their use, for example.

[0036] Specifically, there are various service providers, such as a service provider that sells and manages the use of train tickets, a service provider that sells and manages the use of theme park admission tickets, a service provider that issues and manages the use of coupons for stores and restaurants, etc. Although only one ticket management server (service provider) 50 is shown in Fig. 1, many ticket management servers (service providers) 50 exist on the network.

[0037] For example, if the ticket management server (service provider) 50 is a service provider that sells and manages the use of train tickets, the ticket management server (service provider) 50 communicates with user terminals to sell train tickets. The ticket management server (service provider) 50 also receives information acquired by near-field communication between a reader / writer (R / W) (= ticket use confirmation device (R / W) 60 shown in FIG. 1) installed at the ticket gate and the user terminal from the user terminal or the reader / writer (R / W) to manage the use of the train tickets. The ticket management server (service provider) 50 also manages the transfer of tickets and the like between user terminals.

[0038] 1 may be a reading device without a writing function. Furthermore, the ticket usage confirmation device (R / W) 60 may include the following different types of devices. (Type a) "Ticket usage confirmation device" for using the transferred ticket / for reporting the usage to the ticket management server (Type b) "Ticket gate / entrance / exit gate device (R / W)" at a station or facility entrance / exit gate that triggers the ticket usage terminal to inquire about the existence of a transferable ticket to the ticket management server.

[0039] In the configuration shown in FIG. 1, the ticket transfer terminal (user terminal a) 11, the ticket use terminal (user terminal b) 21, and the ticket management server (service provider) 50 are configured to be able to communicate via a network. The ticket management server (service provider) 50 and the ticket usage confirmation device (R / W (reader / writer)) 60 are also connected via a network, enabling communication.

[0040] A ticket transfer user A 10 uses a ticket transfer terminal (user terminal a) 11 to purchase a ticket. For example, the ticket transfer terminal (user terminal a) 11 accesses the ticket management server (service provider) 50 and purchases the ticket from the ticket management server 50.

[0041] Ticket transfer user A (10) can transfer the purchased ticket to ticket using user B (20). A ticket transfer user A, 10, uses a ticket transfer terminal (user terminal a) 11 to access a ticket management server (service provider) 50 and registers the ticket transfer recipient and the conditions for notifying the ticket transfer recipient (ticket transfer notification conditions). The ticket transfer user A, 10 can also be a ticket user. For example, if a ticket is purchased for use by the family, and all family members, including the purchaser, are registered as users, the purchaser can receive the ticket if they meet the conditions when holding up their own terminal. The recipient of the ticket is identified by, for example, the IC card identifier (ID) of the IC chip mounted on the ticket use terminal.

[0042] The ticket management server (service provider) 50 refers to this registration information and determines whether the registered ticket transferee meets the transfer notification conditions, and if so, notifies the registered ticket transferee, for example, the ticket usage terminal (user terminal b) 21 shown in Figure 1, that a transfer ticket exists.

[0043] For example, if the ticket usage terminal (user terminal b) 21 used by ticket user B, 20 shown in Figure 1 is the transferee of a ticket registered in the ticket management server 50, the ticket management server (service provider) 50 notifies the ticket usage terminal (user terminal b) 21 that there is a ``transfer ticket'' available for receipt.

[0044] Specifically, for example, when an IC chip equipped in the ticket usage terminal with contactless IC card functionality is read by a contactless IC card reader at a ticket gate or facility entrance gate, the ticket usage terminal (user terminal b) 21 inquires of the ticket management server (service provider) 50 about the existence of a transfer ticket. In response to the inquiry, the ticket management server (service provider) 50 refers to the registration information to determine whether the registered transferee of the ticket satisfies the transfer notification conditions, and if so, notifies the registered transferee of the ticket, for example, the ticket usage terminal (user terminal b) 21 shown in Fig. 1, that a transfer ticket exists.

[0045] Communication between the ticket usage terminal (user terminal b) 21 and the ticket gate or facility entrance gate may be by short-range communication (NFC including FeliCa (registered trademark)) or by near field communication such as UWB. In this case, the user does not necessarily hold the usage terminal over the usage confirmation device, but communication between the ticket usage confirmation device and the ticket usage confirmation device (user terminal b) 21 occurs when the user approaches or passes by the confirmation device.

[0046] A ticket user B, 20 using a ticket use terminal (user terminal b) 21 receives notification from the ticket management server (service provider) 50 that there is a "transfer ticket" available for receipt, and if the user wishes to receive and use this "transfer ticket," the user sends a ticket transfer request to the ticket management server 50 as a user confirmation response.

[0047] In response to receiving this ticket transfer request, the ticket management server 50 updates the registration data to enable the ticket purchased by the ticket transfer user A 10 to be used at the ticket use terminal (user terminal b) 21 of the ticket use user B 20.

[0048] The ticket management server (service provider) 50 refers to the transfer notification condition information corresponding to the ticket transferee that has been registered in advance on the server, and determines whether the registered ticket transferee satisfies the transfer notification conditions, and only if the conditions are met, notifies the registered ticket transferee that a transfer ticket exists.

[0049] The ticket transfer notification conditions are, for example, the following conditions. (Condition a) The IC card (an IC card with an IC card identifier (ID) that has been registered in advance as a transfer notification condition) installed in the ticket use terminal (user terminal b) 21 of ticket user B, 20 is held over the ticket use confirmation device (R / W) 60 to perform near-field communication, and the ticket use user B, 20 enters or exits through a station ticket gate or facility entrance / exit gate that has been registered in advance as a transfer notification condition. (Condition b) The ticket use terminal (user terminal b) 21 of ticket use user B 20 enters a predetermined area such as a pre-registered station.

[0050] For example, such transfer notification conditions are registered in the database of the ticket management server (service provider) 50, and when these registered transfer notification conditions are met, the ticket usage terminal (user terminal b) 21 is notified that a transfer ticket exists.

[0051] The above examples of ticket transfer notification conditions (condition a) to (condition b) are just examples. These transfer notification conditions vary depending on the service provider, and can be set as different conditions for each ticket type and ticket use terminal.

[0052] For example, it is possible to set the time the ticket is used by the ticket use terminal or the attributes of the user who uses the ticket use terminal as the transfer notification condition. Specifically, for example, it is possible to set up a process to notify users that a ticket (discount coupon) will be issued only if they visit a certain store on Tuesday mornings, or to send notifications only to a specific age group, such as women in their 20s.

[0053] Note that time information may be used as a condition for notifying the transfer of a ticket. For example, to encourage people to use trains during off-peak hours, a green ticket will be issued (transferred) when a specific IC card is swiped through the ticket gate during off-peak hours. Alternatively, if you enter the ticket gate at the station nearest to your company during late-night overtime hours by waving your commuter pass (an IC card stored in the terminal) you will be given (transferred) a reserved seat ticket.

[0054] One method for setting the transfer notification conditions is to register the attributes of the user who will use the ticket use terminal in the database of the ticket management server (service provider) 50 in advance. However, it is not necessary to register the user attributes of each ticket using user B in advance in the ticket management server (service provider) 50, and the user attributes may be included in the information sent from the ticket using terminal (user terminal b) 21 to the ticket management server (service provider) 50 to inquire about the availability of a transfer ticket.

[0055] These conditions can be registered by the ticket transfer user A 10 using the ticket transfer terminal (user terminal a) 11 to access the ticket management server 50. For example, when determining whether the above condition (condition a) is met, the ticket management server 50 uses information received from the ticket usage terminal (user terminal b) 21 of ticket user B, 20, or the ticket usage confirmation device (R / W) 60 shown in Figure 1.

[0056] When determining whether or not the condition (condition a) is satisfied, the ticket management server 50 may perform the following process: The ticket usage terminal (user terminal b) 21 of the ticket using user B, 20 is held over the ticket usage confirmation device (R / W) 60, and the history of the event is written from the ticket usage confirmation device (R / W) 60 to a secure memory in the ticket usage terminal (user terminal b) 21. Thereafter, when the ticket usage terminal (user terminal b) 21 inquires of the ticket management server 50 whether there is a ticket available for collection, the history may be read from the secure memory and transmitted from the ticket usage terminal (user terminal b) 21 to the ticket management server 50, and a determination may be made based on this transmitted data.

[0057] For example, the ticket use terminal (user terminal b) 21 of ticket use user B 20 transmits the identifier of the ticket use confirmation device (R / W) 60 acquired through near field communication with the ticket use confirmation device (R / W) 60 to the ticket management server 50. Alternatively, the ticket usage confirmation device (R / W) 60 transmits to the ticket management server 50 an identifier (user terminal identifier or IC card identifier (ID) in the user terminal) read from the ticket usage terminal (user terminal b) 21.

[0058] Based on this received information, the ticket management server 50 determines whether the ticket use terminal (user terminal b) 21 satisfies the ticket transfer notification conditions registered in advance in the database.

[0059] For example, the ticket transfer notification condition of the ticket use terminal (user terminal b) 21 is the above (condition a), that is, (Condition a) The ticket use terminal (user terminal b) 21 of ticket use user B 20 is held over the ticket use confirmation device (R / W) 60 to perform near-field communication. If this condition is set, the ticket management server 50 performs the following confirmation process.

[0060] The ticket management server 50 confirms that the ticket use terminal (user terminal b) 21 of the ticket use user B 20 has been held over the ticket use confirmation device (R / W) 60 to perform near-field communication. If this confirmation is made, the ticket management server 50 notifies the ticket use terminal (user terminal b) 21 that a transfer ticket exists.

[0061] There may be cases where multiple IC cards are issued to the ticket use terminal (user terminal b) 21. In this case, the ticket use user B 20 may hold a card other than the IC card identifier (ID) of the transfer target over the ticket use confirmation device (R / W) 60. In such a case, the ticket management server 50 must perform processing such that the transfer process is performed only when the IC card corresponding to the IC card identifier (ID) of the transfer target is being used. It is also possible to configure the IC card specified in the transfer notification conditions and the ticket transfer destination IC card to be different.

[0062] Furthermore, for example, the ticket transfer notification condition of the ticket use terminal (user terminal b) 21 may be the above (condition b), i.e., (Condition b) The ticket use terminal (user terminal b) 21 of ticket use user B 20 enters a predetermined area such as a pre-registered station. If this condition is set, the ticket management server 50 performs the following confirmation process.

[0063] The ticket management server 50 receives location information from the ticket using terminal (user terminal b) 21 of the ticket using user B 20, and determines whether or not the above (condition b) is satisfied.

[0064] The application of the ticket use terminal (user terminal b) 21 transmits to the ticket management server 50 the location information detected by a location detection means such as a GPS provided in the ticket use terminal (user terminal b) 21. Based on this received information, the ticket management server 50 checks whether the above (condition b) is met, i.e., whether the ticket using terminal (user terminal b) 21 of ticket using user B, 20 has entered a predetermined area such as a pre-registered station.

[0065] When the ticket management server 50 confirms that the ticket usage terminal (user terminal b) 21 of ticket user B, 20 has entered a specified area such as a pre-registered station, it notifies the ticket usage terminal (user terminal b) 21 that a transfer ticket is available.

[0066] The determination of whether or not the user has entered the station based on the position information such as GPS may be performed by an application in the ticket use terminal (user terminal b) 21, rather than by the ticket management server 50.

[0067] Although FIG. 1 shows a station ticket gate as the ticket usage verification device (R / W) 60, various different configurations of the ticket usage verification device (R / W) 60 are available. For example, as shown in FIG. 2, it is possible to set the R / W (reader / writer) of the store as the ticket usage confirmation device (R / W) 60. Alternatively, the device may be a ticket usage verification device (R / W) provided at the entrance gate of a theme park, theater, art museum, museum, movie theater, amusement facility, or the like.

[0068] Alternatively, a configuration as shown in FIG. 3 may be used. In the configuration shown in FIG. 3, the ticket management server (service provider) 50 is configured as a single aggregate made up of the following multiple devices. Ticket transfer relay service function providing server (ticket transfer relay service provider) 50a Ticket sales and usage management service function provider server (ticket sales and usage management service provider) 50b

[0069] The ticket sales and usage management service function providing server (ticket sales and usage management service provider) 50b provides and manages the usage of tickets. This function exists in plural for each of the plural ticket sales and usage management service providers.

[0070] The ticket transfer relay service function providing server (ticket transfer relay service provider) 50a is responsible for the relay function of relaying and distributing communications between the ticket transfer terminal (user terminal a) 11 and the ticket usage terminal (user terminal b) 21 and multiple ticket sales and usage management service function providing servers (ticket sales and usage management service providers) 50b.

[0071] If the ticket needs to be written to the IC chip of the ticket use terminal, the ticket transfer relay service function providing server (ticket transfer relay service provider) 50a writes the ticket to the IC chip of the ticket use terminal using the IC chip secure data writing server 51. Generally, the IC chip secure data writing server 51 may be a server separate from the ticket management server and provided by a different service provider.

[0072] The processing sequence when performing processing using the configuration shown in FIG. 3 is as follows. 1) The ticket transfer terminal (user terminal a) 11 registers the ticket identifier to be transferred from the purchased ticket identifiers obtained from the ticket sales and usage management server function providing server 50b in the ticket transfer relay server function providing server 50a, along with the ticket transfer recipient and ticket transfer notification conditions.

[0073] 2) When the ticket use terminal (user terminal b) 21 is held over a ticket gate, an entrance gate of a facility, or a payment terminal of a store or vending machine, or when entry into a station or facility is detected by location information detection such as GPS, it makes an inquiry about the presence or absence of a transferable ticket, and sends the ticket use terminal (user terminal b) 21's IC card number, the identifier of the ticket gate that was held over, the identifier of the station or facility where entry was identified by location information detection, user attributes, etc. to the ticket transfer relay server function providing server 50a.

[0074] 3) The ticket transfer relay server function providing server 50a uses the contents of the inquiry received from the ticket usage terminal (user terminal b) 21 to list tickets eligible for transfer that meet the conditions from the ticket transfer recipients and ticket transfer notification conditions registered in the ticket transfer relay server function providing server 50a, and notifies the ticket usage terminal (user terminal b) 21 of the tickets eligible for transfer.

[0075] 4) When the ticket usage terminal (user terminal b) 21 receives the ticket to be transferred, it displays it on the screen and asks the user to confirm whether or not to use the ticket. If the user selects to use the ticket, it makes a ticket transfer request to the ticket sales and usage management server function providing server 50b for the ticket.

[0076] In this case, in some embodiments, the transfer request is made to the ticket sales utilization management server function providing server 50b via the ticket transfer relay server function providing server 50a, and in other embodiments, the request destination server information is included in the data of the ticket to be transferred, and the ticket utilization terminal (user terminal b) 21 makes the transfer request directly to the ticket sales utilization management server function providing server 50b for that ticket without going through the ticket transfer relay server function providing server 50a.

[0077] 5) Upon receiving the transfer request, the ticket sales utilization management server function providing server 50b responds with the ticket to the ticket use terminal (user terminal b) 21 (via the ticket transfer relay server providing server 50a if the request was made via the ticket transfer relay server providing server 50a) (the ticket use terminal downloads the ticket). At this time, if the ticket needs to be written to an IC chip mounted on the ticket use terminal (user terminal b) 21, the ticket sales utilization management server function providing server 50b uses the IC chip secure writing server 51 to write the ticket to the IC chip of the ticket use terminal. Generally, the server in question may be a different server or a different service provider from the ticket management server (ticket transfer relay server function, ticket sales and usage management server function).

[0078] [2. Applications and IC chips in user devices] Next, the application in the user terminal and the IC chip will be explained.

[0079] As shown in FIGS. 1 and 2, a ticket transfer user A 10 uses a ticket transfer terminal (user terminal a) 11, and a ticket using user B 20 uses a ticket using terminal (user terminal b) 21. These user terminals 11 and 21 are, for example, smartphones.

[0080] These user terminals 11 and 21 are installed with at least one electronic money application and a transfer processing management application, which is a program that executes the ticket transfer and usage processing of the present disclosure. A specific example of an application installed on a user terminal used by each user will be described.

[0081] 4 and 5 are diagrams showing specific examples of apps installed on the ticket transfer terminal (user terminal a) 11 and the ticket use terminal (user terminal b) 21. FIG. As shown in Figures 4 and 5, a transfer process management application 31a, which is a program that performs various processes related to the ticket transfer process of the present disclosure, and multiple different electronic money applications are installed on a user terminal such as a smartphone.

[0082] Figures 4 and 5 show an example where the following four types of electronic money applications are installed. Transportation IC card compatible app 31p Transportation IC card Q compatible app 31q Distribution IC card compatible app 31r Distribution IC card S compatible app 31s

[0083] These are electronic money applications provided by different service providers. Users conduct near-field communication by bringing their smartphone or other user device close to a reader / writer installed at a store or ticket gate managed by each service provider. Through this proximity communication, the reader / writer performs processes such as recording usage history information in the secure memory in the IC chip in the user terminal.

[0084] 1 and 2 corresponds to a server managed by a certain service provider, and the ticket usage confirmation device (R / W) 60 corresponds to one or more service providers. Some service providers handle tickets that are not written to IC cards, but only tickets that require the user to show the smartphone screen or scan a two-dimensional code to a store clerk when using the ticket, and the service provider may not be associated with an IC card compatible app or ticket usage device (R / W).

[0085] 6 and 7 show examples of the configuration of an IC chip configured in a user terminal, for example, an IC chip equipped with a secure memory. As shown in FIGS. 6 and 7, the IC chip 32 includes an IC card identifier (ID) corresponding to an electronic money application provided by each service provider. In addition, a recording area for usage history information of each IC card application is provided. The usage history information includes, for example, electronic money balance information.

[0086] The examples shown in Figures 6 and 7 are examples of an IC chip 32 having IC card identifiers (IDs) corresponding to the four electronic money applications described with reference to Figures 4 and 5, respectively, and a secure memory having a recording area for recording usage history information for each IC card application. Depending on the IC chip 32, some IC card identifiers (IDs) corresponding to the various electronic money applications may have a common value.

[0087] The recording area 32P is a storage area for usage history information including an IC card identifier (ID) corresponding to the transport IC card P compatible application 31p and electronic money balance information, etc. Information on available tickets may also be included in the storage area. The recording area 32Q is a storage area for IC card identifiers (IDs) corresponding to the transport IC card Q compatible application 31q, and usage history information including electronic money balance information, etc. Information on available tickets may also be included in the storage area. The recording area 32R is a storage area for IC card identifiers (IDs) corresponding to the distribution-system IC card R compatible applications 31r, and usage history information including electronic money balance information, etc. Information on available tickets may be included in the storage area. The recording area 32S is a storage area for IC card identifiers (IDs) corresponding to the distribution-system IC card R compatible applications 31s, and usage history information including electronic money balance information, etc. Information on available tickets may also be included in the storage area.

[0088] In this way, the user terminals 11 and 21 have an IC chip 32 with a secure memory that individually records usage history information including purchase ticket information corresponding to the electronic money application provided by each service provider and electronic money balance information.

[0089] When a user terminal such as a smartphone is brought close to a ticket usage confirmation device (R / W) 60 installed in a store or ticket gate, the ticket usage confirmation device (R / W) 60 executes a process to rewrite the usage history information of the IC card.

[0090] [3. Specific examples of ticket transfer and usage sequences disclosed in this disclosure] Next, a specific example of the ticket transfer and usage sequence of the present disclosure will be described.

[0091] The following processing sequence will be explained in order with reference to the sequence diagrams in FIG. 8 and subsequent figures. (1) Sequence of data acquisition and storage by the ticket transfer terminal (user terminal a) 11 from the ticket use terminal (user terminal b) 21 (2) Data transmission from the ticket transfer terminal (user terminal a) 11 to the ticket management server (service provider) 50, and database registration processing sequence in the ticket management server (service provider) 50 (3) A process sequence in which the ticket management server (service provider) 50 checks whether the ticket use terminal (user terminal b) 12 satisfies the ticket transfer notification conditions and executes the ticket transfer notification. (4) Processing sequence when the ticket use terminal (user terminal b) 12 uses a transfer ticket

[0092] The ticket transfer and usage sequence of the present disclosure is performed by sequentially executing the above processes (1) to (4). The processing sequence of (1) to (4) above will be explained below in order.

[0093] (3-(1) Sequence of data acquisition and storage by the ticket transfer terminal (user terminal a) 11 from the ticket use terminal (user terminal b) 21) First, with reference to FIG. 8 and subsequent figures, "(1) Sequence of data acquisition and storage by the ticket transfer terminal (user terminal a) 11 from the ticket use terminal (user terminal b) 21" will be described.

[0094] The sequence diagrams in FIG. 8 and subsequent figures show, from left to right, the following configurations: (1) Ticket transfer user A,10, (2) Ticket transfer terminal (user terminal a) 11; (3) Ticket management server (service provider) 50, (4) Ticket usage confirmation device (R / W (reader / writer)) 60, (5) ticket use terminal (user terminal b) 21; (6) Ticket user B,20,

[0095] 8 indicates the "transfer processing management application" in the ticket transfer terminal (user terminal a) 11. In the processing sequence described with reference to FIG. 8 and subsequent figures, the processing executed by the "ticket transfer terminal (user terminal a) 11" is primarily the processing executed by the "transfer processing management application."

[0096] 8 shows the "ticket use terminal (user terminal b) 21" and the "transfer processing management application" in the ticket use terminal (user terminal b) 12 and the IC chip. In the processing sequence described with reference to Figure 8 onwards, the processing executed by the "ticket use terminal (user terminal b) 21" is mainly processing executed by the "transfer processing management application" of the "ticket use terminal (user terminal b) 21". The "transfer processing management app" of the "ticket usage terminal (user terminal b) 21" also reads recorded data from the "IC chip" of the "ticket usage terminal (user terminal b) 21" and receives instructions to write the transferred ticket if the transferred ticket is a ticket that needs to be written to an IC card.

[0097] The details of the processing of each processing step shown in the sequence diagrams in FIG. 8 and subsequent figures will be explained below in order. (Step S101) First, in step S101, the transfer process management application of the ticket use terminal (user terminal b) 21 reads the IC card identifier (ID) from the IC chip of the ticket use terminal (user terminal b) 21.

[0098] Note that, when various IC card compatible applications are installed on the ticket using terminal (user terminal b) 21 and there are multiple usable IC cards, the IC card identifiers (IDs) of all the IC cards may be read and the process from step S102 onwards may be executed collectively for the read IC card identifiers (IDs), or the process from step S102 onwards may be executed sequentially for each of the read IC card identifiers (IDs).Alternatively, the ticket using user B may be asked to select the IC card to be read, and only the IC card identifier (ID) of the selected IC card may be read, and the process from step S102 onwards may be executed collectively or individually for the read IC card identifiers (IDs).

[0099] Here, if there are multiple IC card identifiers (IDs) read and the processing from step S102 onwards is configured to be executed collectively, the IC card identifiers (IDs) are treated as a list consisting of one or more IC card identifiers (IDs).

[0100] With reference to FIG. 9, an example of display data (UI) output to the display unit of the ticket use terminal (user terminal b) 21 during the processing of step S101 in FIG. 8 will be described. The display data shown in FIG. 9 is data that is generated by the transfer process management application of the ticket use terminal (user terminal b) 21 and output to the display unit.

[0101] The process of step S101 in FIG. 8 is a process in which the transfer process management application of the ticket use terminal (user terminal b) 21 reads the IC card identifier (ID) from the IC chip of the ticket use terminal (user terminal b) 21. The display data is switched in order from step S101-1 to step S101-4 shown in FIG.

[0102] The display data in step S101-1 shown in FIG. 9 is display data for the following inquiry message to ticket user B,20. "Do you want to share your IC card ID with the ticket transfer user?"

[0103] When the ticket using user B 20 enters "Yes" in response to this inquiry, the display data of step S101-2 shown in FIG. 9, that is, the following inquiry message for the ticket using user B 20, is displayed. "Do you want to obtain the IC card identifier (ID) from the IC chip?"

[0104] When ticket user B 20 responds to this inquiry by answering "Yes," the display data of step S101-3 shown in FIG. 9, that is, the following processing status notification message for ticket user B 20, is displayed. "The IC card identifier (ID) is obtained from the IC chip."

[0105] If ticket user B 20 responds to this inquiry by typing "cancel," the process is cancelled. If ticket user B, 20 does not input "cancel", the process will continue. When the process of obtaining the IC card identifier (ID) from the IC chip is completed, the following process confirmation message and the obtained "IC card identifier (ID)" will be displayed to ticket user B, 20. "IC card identifier (ID) obtained from IC chip" IC card ID (identifier) ​​= 01238765332

[0106] Furthermore, the following multiple options for processing to be performed on the acquired IC card identifier (ID) are displayed. (a) Copy to clipboard (b) Start the sharing process using the app (c) Start the sharing process using a messaging app The user selects one of these options. Here, the explanation will be given assuming that the user has selected (b). If "(b) Start sharing process using app" is selected, for example, the IC card identifier is sent to the ticket transfer terminal (user terminal a) 11 of the ticket transfer user A, 10 in cooperation with a contacts app in the ticket use terminal (user terminal b) 21 to have the ticket use user B designate the ticket transfer user A, 10.

[0107] When the user selects (b), that is, "(b) Start sharing process using application," the process from step S102 onward shown in FIG. 8 is started. The processing from step S102 onwards will be described.

[0108] (Step S102) In step S102, the transfer process management application of the ticket use terminal (user terminal b) 21 transmits the IC card identifier (ID) acquired from the IC chip to the ticket transfer terminal (user terminal a) 11 of the ticket transfer user A 10. In addition, the method of sending data from the transfer processing management app of the ticket usage terminal (user terminal b) 21 to the transfer processing management app of the ticket transfer terminal (user terminal a) 11 is not limited to via the network (server), but can also be done P2P by touching the terminals to each other using a communication means such as NFC.

[0109] This transmission data is acquired by the transfer process management application of the ticket transfer terminal (user terminal a) 11.

[0110] (Step S103) Next, in step S103, the transfer processing management application of the ticket transfer terminal (user terminal a) 11 stores the IC card identifier (ID) received from the ticket use terminal (user terminal b) 21 in a memory.

[0111] (3-(2) Data transmission from the ticket transfer terminal (user terminal a) 11 to the ticket management server (service provider) 50, and database registration processing sequence in the ticket management server (service provider) 50) Next, with reference to Figures 10 and onwards, "(2) Data transmission from ticket transfer terminal (user terminal a) 11 to ticket management server (service provider) 50, and database registration processing sequence in ticket management server (service provider) 50" will be described.

[0112] The process shown in FIG. 10 is mainly executed by the transfer process management application of the ticket transfer terminal (user terminal a) 11 that receives the IC card identifier (ID) from the ticket use terminal (user terminal b) 21.

[0113] (Step S111) A ticket transfer user A 10 using a ticket transfer terminal (user terminal a) 11 starts up the transfer process management application of the ticket transfer terminal (user terminal a) 11 and inputs data required to carry out the ticket transfer process.

[0114] For example, the following data is input. (a) User name (Ticket transfer user A, 10's user name) (b) Ticket transfer terminal IC card identifier (ID) (c) The type or identifier of the ticket being transferred. (d) Ticket terminal IC card identifier (ID) (e) Ticket Transfer Notification Conditions The above data is input by specifying a selection from the options that the transfer processing management application obtains from the ticket management server and displays, or the IC card identifier (ID) of the ticket usage terminal received from the ticket usage terminal. Depending on the ticket to be transferred and the service provider of the ticket management server, the process may not require inputting all the data.

[0115] (a) The user name is the user name of the ticket transfer user A,10. This is used to display on the screen of the ticket usage terminal that a transferable ticket is available. In addition, the determination in the ticket management server (c) of whether the type or identifier of the ticket to be transferred is owned by the ticket transfer user A, 10 may be performed using the ID and password used to log in to the ticket management server, (a) User name (Ticket transfer user A, 10's user name) (b) Ticket transfer terminal IC card identifier The process may be performed using the above.

[0116] (c) the type or identifier of the ticket being transferred; When specifying "ticket type," it is used when it is not necessary to identify each ticket individually. For example, it is used when specifying discount coupons, complimentary coupons, coupons, etc., which can be transferred to an unspecified number of people without any problem. Specifically, a "ticket type" might be something like "Get one free drink when you spend 1,000 yen or more at XX store (valid until XX / XX / XX)." On the other hand, when specifying a "ticket identifier," it is necessary to identify each ticket, as the name suggests, and it is used for tickets that are purchased for a certain price and require management of transfers and usage. The type of ticket with the specified ticket identifier, such as a Shinkansen ticket from Tokyo to Shin-Osaka, a limited express ticket, or a green ticket, can be determined from the ticket identifier on the ticket management server, and when sending a transfer notification to the ticket usage terminal, the ticket management server automatically includes this information in the transfer notification.

[0117] (d) The ticket usage terminal IC card identifier (ID) is the identifier received from the ticket usage terminal (user terminal b) 21 in step S102 described above with reference to FIG. This data is used by the ticket management server (service provider) 50 to confirm the recipient of the ticket.

[0118] (e) The ticket transfer notification conditions are conditions for the ticket transfer user A, 10 to notify the ticket using user B, 20 that the ticket will be transferred. For example, the following conditions are as explained above. (Condition a) The IC card (an IC card with an IC card identifier (ID) that has been registered in advance as a transfer notification condition) installed in the ticket use terminal (user terminal b) 21 of ticket user B, 20 is held over the ticket use confirmation device (R / W) 60 to perform near-field communication, and the ticket use user B, 20 enters or exits through a station ticket gate or facility entrance / exit gate that has been registered in advance as a transfer notification condition. (Condition b) The ticket use terminal (user terminal b) 21 of ticket user B 20 enters a predetermined area, such as a station, designated by the ticket transfer user.

[0119] The data required for performing the ticket transfer process is defined by the ticket management server (service provider) 50 and differs for each ticket management server (service provider) 50. The above data (a) to (e) are examples.

[0120] For example, in addition to the above data, the data required to perform the ticket transfer process may include data such as the "identifier of the ticket usage terminal," "attributes of ticket usage user B, 20," and "attributes of ticket transfer user A, 10."

[0121] (Step S112) Next, in step S112, the ticket transfer terminal (user terminal a) 11 transmits the data input in step S111 to the ticket management server (service provider) 50.

[0122] That is, the following data required for performing the ticket transfer process is transmitted to the ticket management server (service provider) 50. (a) User name (Ticket transfer user A, 10's user name) (b) Ticket transfer terminal IC card identifier (ID) (c) The type or identifier of the ticket being transferred. (d) Ticket terminal IC card identifier (ID) (e) Ticket Transfer Notification Conditions

[0123] As mentioned above, the data required to perform the ticket transfer process varies depending on the ticket being transferred and the ticket management server (service provider) 50, and not all data may be required. In addition to this data, data such as the "identifier of the ticket usage terminal," "attributes of ticket usage user B, 20," and "attributes of ticket transfer user A, 10" may also be included.

[0124] (Steps S113 to S114) Next, in step S113, the ticket management server (service provider) 50 registers the data received from the ticket transfer terminal (user terminal a) 11 in step S112 in a database.

[0125] When the registration process is completed, the ticket management server (service provider) 50 transmits a registration completion notice to the ticket transfer terminal (user terminal a) 11 in step S114.

[0126] 11 and 12 show examples of representative display data (UI) output to the display unit of the ticket transfer terminal (user terminal a) 11 during execution of the sequence shown in FIG. The display data shown in FIGS. 11 and 12 is data that is generated by the transfer process management application of the ticket transfer terminal (user terminal a) 11 and output to the display unit.

[0127] The display data shown in FIG. 11 (step S111-1) is the display data for the following data input request message to ticket transfer user A,10. For IC card compatible tickets to be transferred, please specify the IC card identifier (ID) of the IC card on the ticket terminal to which the ticket will be transferred.

[0128] In response to this data input request message, the ticket transfer user A, 10, selects from the IC card identifiers (IDs) of the ticket use terminals received from the ticket use terminals and stored in the transfer processing management application of the ticket transfer terminals. As shown in the figure, the input identifier is not limited to one, and multiple identifiers can be selected.

[0129] The display data shown in FIG. 11 (step S111-2) is the display data for the following data input request message to ticket transfer user A,10. "For IC card compatible tickets to be transferred, please specify the ticket transfer notification conditions for the ticket terminal to which the ticket will be transferred."

[0130] In response to this data input request message, the ticket transfer user A, 10 specifies the ticket transfer notification conditions for the ticket use terminal to which the ticket is to be transferred. For example, as shown in the figure, "passing through the ticket gate" can be specified as a transfer notification condition.

[0131] The display data shown in FIG. 12 (step S111-3) is the display data for the following confirmation request message to ticket transfer user A,10. "Regarding the IC card compatible ticket you plan to transfer, we will register the following data for the ticket transfer process. Is this OK?"

[0132] When ticket transfer notification conditions include passing through a ticket gate or gate, the condition for the ticket transfer notification is specified as passing through a ticket gate or gate at a station or facility in the area where the ticket of the specified ticket type or ticket identifier can be used or can lead to use. For example, when transferring a Shinkansen ticket from Tokyo to Osaka, the ticket transfer notification condition is not automatically set to only pass through a ticket gate at Tokyo Station, but also to pass through a ticket gate at any JR station within Tokyo. The list of stations and facilities where each ticket can be used or can lead to use is managed in a database by the ticket management server (service provider). Alternatively, the ticket transfer user can specify the specific station or facility names.

[0133] When the ticket transfer user A, 10 touches the "Register" icon in response to this data confirmation request message, the data transmission process of step S112 shown in FIG. 10 is performed. That is, the ticket transfer terminal (user terminal a) 11 transmits the data input in step S111 to the ticket management server (service provider) 50.

[0134] Then, in step S113, the ticket management server (service provider) 50 registers the received data from the ticket transfer terminal (user terminal a) 11 in a memory unit (database), and when the registration process is completed, in step S114, the ticket management server (service provider) 50 sends a registration completion message to the ticket transfer terminal (user terminal a) 11.

[0135] When the ticket transfer terminal (user terminal a) 11 receives the registration completion message from the ticket management server (service provider) 50, the ticket transfer terminal (user terminal a) 11 displays the data shown in FIG. 12 (step S114) on the display unit. That is, the following message is displayed: "Regarding the IC card compatible ticket to be transferred, the data required for ticket transfer, (a) user name, (d) ticket recipient IC card identifier (ID), and (e) ticket transfer notification conditions, have been registered." You will be notified when a ticket is used on a registered "ticket usage device."

[0136] 10, the ticket management server (service provider) 50 stores in a storage unit the data received from the ticket transfer terminal (user terminal a) 11. That is, a database is created in which data required for the ticket transfer process is registered.

[0137] An example of registered data in a database generated by the ticket management server (service provider) 50, that is, a "ticket transfer processing management database", will be described with reference to FIG.

[0138] The registration data in the database shown in Figure 13 is an example of data received by the ticket management server (service provider) 50 from the ticket transfer terminal (user terminal a) 11 in step S112 of the sequence described with reference to Figure 10, and registered in the database in step S113.

[0139] As shown in FIG. 13, the registered data in the "ticket transfer processing management database" is configured as corresponding data for each of the following data. (a) User name (Ticket transfer user A, 10's user name) (b) Ticket transfer terminal IC card identifier (ID) (c) The type or identifier of the ticket being transferred. (d) Ticket terminal IC card identifier (ID) (e) Ticket Transfer Notification Conditions (f) Other

[0140] The ticket management server (service provider) 50 refers to this database registration data and executes the process of transmitting a ticket transfer notification to the ticket use terminal (user terminal b) 12 and the process of transferring the ticket.

[0141] The types of data registered in the database shown in FIG. 13 differ depending on the ticket management server (service provider) 50. For example, if the attributes of the user of the ticket use terminal are set as the ticket transfer notification conditions, the attributes of the user of the ticket use terminal are registered as (f) other data.

[0142] Furthermore, if the location of the ticket use terminal is set as a condition for ticket transfer notification, the identifier of the ticket use terminal is registered as (f) other data. In this case, the ticket management server (service provider) 50 receives from the ticket usage terminal (user terminal b) 12 the identifier of the ticket usage terminal and the user terminal location information measured by GPS or the like, and determines whether the location of the ticket usage terminal (user terminal b) 12 satisfies the ticket transfer notification conditions.

[0143] After registering the data shown in FIG. 13 in the database, the ticket management server (service provider) 50 executes the process of transmitting a ticket transfer notification to the ticket use terminal (user terminal b) 12 and the process of transferring the ticket. The processing sequence will be described with reference to FIG. 14 and subsequent figures.

[0144] (3-(3) Processing sequence in ticket management server (service provider) 50 to check whether ticket use terminal (user terminal b) 12 satisfies the ticket transfer notification conditions and to execute ticket transfer notification) Referring to Figure 14 and subsequent figures, we will explain "(3) The process in the ticket management server (service provider) 50 to check whether the ticket use terminal (user terminal b) 12 satisfies the ticket transfer notification conditions and the processing sequence to execute the ticket transfer notification."

[0145] The processing sequence described with reference to Figure 14 onwards is a sequence when the ticket transfer notification condition is set to "enter through the ticket gate at XX station." In other words, this is an example of a sequence that performs processing corresponding to the data registered in the first entry of the database shown in Figure 13.

[0146] (Step S121) The ticket using user B 20 holds the ticket using terminal (user terminal b) 21 over the ticket use confirmation device (R / W) 60 in step S121.

[0147] (Step S122) Next, in step S122, the ticket usage terminal (user terminal b) 21 performs near-field communication with the ticket usage confirmation device (R / W) 60, and detects that the identifier of the ticket usage confirmation device has been written to the usage history of the IC card when the ticket usage process of the IC card recorded in the IC chip of the ticket usage terminal is performed, and the transfer processing management app of the ticket usage terminal acquires the identifier of the ticket usage confirmation device. In addition, separate from the ticket usage process of the IC card recorded in the IC chip of the ticket usage terminal, the ticket usage terminal may perform a process via near-field communication with the ticket usage confirmation device to obtain the identifier of the ticket usage confirmation device.

[0148] This identifier acquisition process is performed by the transfer process management application b of the ticket use terminal (user terminal b) 21.

[0149] (Step S131) Next, in step S131, the transfer processing management application b of the ticket use terminal (user terminal b) 21 sends a request to the ticket management server (service provider) 50 to inquire whether there is a transfer ticket that meets the ticket transfer notification conditions.

[0150] The request includes information acquired by the transfer processing management application b in step S121. For example, (a) Ticket usage confirmation device identifier (b) The IC card identifier (ID) recorded on the IC chip of the ticket terminal

[0151] In addition, if the transfer processing management app b has acquired the details of the ticket usage process of the IC card recorded in the IC chip of the ticket usage terminal by the ticket usage confirmation device, such as the type of entry or exit through the ticket gate, and the amount of electronic money paid in connection with the entry or exit, these may be included in the request. Furthermore, if the transfer processing management app b is able to obtain the settings of the ticket usage terminal (user terminal b) 21 or user attribute information held by the app installed on (user terminal b) 21, it may include this information in the request.

[0152] (Step S132) Next, in step S132, the ticket management server (service provider) 50 executes a process of determining whether or not the ticket transfer notification conditions are met based on the data received from the ticket use terminal (user terminal b) 21.

[0153] This process is carried out by collating the registered data in the "ticket transfer process management database" described above with reference to FIG. 13 with the data received from the ticket use terminal (user terminal b) 21.

[0154] That is, first, it is determined whether the "IC card identifier (ID)" contained in the data received from the ticket usage terminal (user terminal b) 21 matches the "ticket usage terminal IC card identifier (ID)" registered in the "ticket transfer processing management database." If they match, it is further determined based on the data received from the ticket use terminal (user terminal b) 21 whether or not the ticket transfer notification conditions registered in the "ticket transfer processing management database" are met.

[0155] (Step S133) In step S132, if the ticket management server (service provider) 50 determines that the "IC card identifier" contained in the data received from the ticket usage terminal (user terminal b) 21 matches the "ticket usage terminal IC card identifier" registered in the "ticket transfer processing management database" or meets the ticket transfer notification conditions, it executes processing in step S133.

[0156] As a process to be performed when multiple conditions are met simultaneously, for example, all possible ticket options that can be received may be displayed and the user may select from among them.

[0157] In step S133, the ticket management server (service provider) 50 transmits the following data to the ticket use terminal (user terminal b) 21: (a) The Ticket Transfer User who authorized the Ticket Transfer; (b) Contents of the Transferred Ticket These will be sent as ticket transfer notifications. In addition, if there are transfer tickets that meet multiple ticket transfer notification conditions, all of them may be sent, or the transfer tickets may be narrowed down and sent based on conditions such as a high degree of match or an approaching ticket expiration date.

[0158] (Step S134) Next, based on the data received from the ticket management server (service provider) 50, the ticket use terminal (user terminal b) 21 displays on the display unit a display screen (UI) that asks the user to confirm whether or not to accept the transfer ticket. In addition, if the transfer ticket is a ticket that is transferred by writing it from a specific IC card compatible app to an IC card stored in the IC chip, user confirmation will be displayed on the display unit only if the IC card is stored in the IC chip of the ticket usage terminal.

[0159] An example of this display screen is shown in Fig. 17. The screen shown in Fig. 17 (S134) is an example of a UI displayed on the ticket use terminal (user terminal b) 21 in step S134. FIG. 17 shows an example of the following message: "Mr. XXYYYYY has authorized the transfer of his IC card P-compatible ticket (green ticket). Would you like to accept it?"

[0160] In this example, the transfer ticket is a green ticket. The ticket management server (service provider) 50 acquires the contents of the transfer ticket based on the ticket identifier registered in the "ticket transfer processing management database," and transmits the acquired contents of the transfer ticket in step S133. The transfer processing management application b of the ticket use terminal (user terminal b) 21 then displays the contents.

[0161] The process in which the ticket using user B 20 selects "Yes" on this UI corresponds to the process in step S135 shown in FIG.

[0162] (Steps S135a, b) As described above, the process of step S135a is a process in which the ticket using user B 20 agrees to receive the transfer ticket on the display screen (UI) shown in FIG. 17 (S134).

[0163] In step S135b, the transfer process management application b of the ticket use terminal (user terminal b) 21 sends a confirmation response to the ticket management server (service provider) 50 confirming that the user has received the ticket.

[0164] When the processing of steps S135a and S135b is executed, the display unit of the ticket use terminal (user terminal b) 21 displays, for example, a message shown in FIG. 17 (S135). For example, the following message is displayed: "I will receive the transferred IC card P compatible ticket (green ticket) from Mr. / Ms. △Yama. When the ticket is used, Mr. / Ms. △Yama will be notified of the ticket use." This message data is generated by the transfer process management application b of the ticket use terminal (user terminal b) 21 based on the data received from the ticket management server (service provider) 50.

[0165] (Step S136) When the ticket management server (service provider) 50 receives a confirmation response from the ticket use terminal (user terminal b) 21 that ticket user B 20 has received the ticket, in step S136, it transmits information for enabling the transfer ticket to be used at the ticket use terminal (user terminal b) 21, such as data such as a ticket identifier, to the ticket use terminal (user terminal b) 21. In the case of a ticket that does not require the transfer ticket to be written to an IC card stored in the IC chip of the ticket use terminal when the transfer ticket is used, the information may be transmitted as a two-dimensional code to be scanned when the ticket is used, or as a ticket image to be shown to a store clerk, etc.

[0166] (Step S137) The ticket usage terminal (user terminal b) 21 receives information, such as a ticket identifier, from the ticket management server (service provider) 50 to enable the transfer ticket to be used at the ticket usage terminal (user terminal b) 21. In step S137, if the transfer ticket requires the transfer ticket to be written to an IC card stored in the IC chip of the ticket usage terminal in order to be used, the ticket usage terminal (user terminal b) 21 writes the received ticket identifier, etc. to the IC card recorded in the IC chip of the ticket usage terminal.

[0167] In addition, when applying the configuration of Figure 3 to write the ticket identifier etc. of a transfer ticket to an IC card, the ticket management server (service provider) 50 and the IC chip secure writing server 51 work together to enable the process of securely writing the transfer ticket.

[0168] For example, in the case of a green ticket, which must be written onto an IC card recorded in the IC chip of the ticket usage terminal in order to be used as a transfer ticket, the ticket management server and the IC chip secure writing server 51 work together to write data such as the ticket identifier of the transfer ticket.

[0169] This process is executed by the transfer process management application b of the ticket use terminal (user terminal b) 21 in cooperation with the two servers. This data writing process enables the ticket usage terminal (user terminal b) 21 to use the transfer ticket.

[0170] The processing example described with reference to FIGS. 14 to 16 is a sequence when the ticket transfer notification condition is set to "enter through the ticket gate at XX station." In this case, the ticket use terminal (user terminal b) 21 performs the following in step S131 of FIG. 15: (a) Ticket usage confirmation device identifier (b) The IC card identifier (ID) recorded on the IC chip of the ticket terminal These and other data are sent to the ticket management server (service provider) 50 together with a request to check whether or not there is a transfer ticket that meets the ticket transfer notification conditions.

[0171] As mentioned above, if the transfer processing management app b has acquired the details of the ticket usage process of the IC card recorded in the IC chip of the ticket usage terminal by the ticket usage confirmation device, such as the type of entry or exit at the ticket gate, and the amount of electronic money paid in connection with the entry or exit, these may be included in the request. Furthermore, if the transfer processing management app b is able to obtain the settings of the ticket usage terminal (user terminal b) 21 or user attribute information held by the app installed on (user terminal b) 21, it may include this information in the request.

[0172] For example, in addition to "entering the ticket gate at XX station" as a condition for ticket transfer notification, "Ticket user B 20 using ticket terminal (user terminal b) 21 is in a predefined location, for example, within XX station" When such additional conditions are included, the data that the ticket use terminal (user terminal b) 21 transmits to the ticket management server (service provider) 50 will be different data.

[0173] The process when such a ticket transfer notification condition is set will be described with reference to FIGS. 18 and 19 correspond to the processing sequence of FIGS. 14 and 15 described above. However, as a condition for ticket transfer notification, (1) "Enter the ticket gate at XX station" (2) “Ticket user B, 20, who is using the ticket use terminal (user terminal b) 21, is in a predetermined location, for example, within the premises of XX station.” This is the processing sequence when these two conditions are set.

[0174] (Step S121b) The ticket using user B 20 holds the ticket using terminal (user terminal b) 21 over the ticket use confirmation device (R / W) 60 in step S121b.

[0175] (Step S122b) Next, in step S122b, the ticket use terminal (user terminal b) 21 performs near field communication with the ticket use confirmation device (R / W) 60 and reads the identifier of the ticket use confirmation device (R / W) 60 from the ticket use confirmation device (R / W) 60.

[0176] The read identifier is used in the transfer process management application b of the ticket use terminal (user terminal b) 21.

[0177] (Step S123b) Next, in step S123b, the transfer processing management application b of the ticket use terminal (user terminal b) 21 acquires the current location of the ticket use terminal (user terminal b) 21 from a location information acquisition unit such as a GPS provided in the ticket use terminal (user terminal b) 21.

[0178] (Step S131b) Next, in step S131b, the transfer process management application b of the ticket use terminal (user terminal b) 21 sends the following to the ticket management server (service provider) 50: (a) Ticket usage confirmation device identifier (b) The IC card identifier (ID) recorded on the IC chip of the ticket terminal (c) Location information of the ticket terminal These data are transmitted.

[0179] Instead of these data, the configuration may be such that history data such as "Entry processing was performed at the ticket gate of XX station" is transmitted, which is written from the ticket usage confirmation device to the memory area of ​​the IC card of the ticket usage terminal (user terminal b) 21.

[0180] In this processing sequence, the transmission data in step S131 described above with reference to FIG. 15 is (a) Ticket usage confirmation device identifier (b) The IC card identifier (ID) recorded on the IC chip of the ticket terminal In addition to these data, (c) Location information of the ticket terminal This data is also sent.

[0181] As described above, the transmission data is data defined by the ticket management server (service provider) 50, that is, data for determining whether the ticket transfer notification conditions are met. "Ticket user B 20 using ticket terminal (user terminal b) 21 is in a predefined location, for example, within XX station" This condition is also included in the ticket transfer notification conditions, (c) Location information of the ticket terminal This data is also sent.

[0182] (Step S132b) Next, in step S132b, the ticket management server (service provider) 50 executes a process of determining whether or not the ticket transfer notification conditions are met based on the data received from the ticket use terminal (user terminal b) 21.

[0183] This process is carried out by checking the registered data in the "ticket transfer process management database" described above with reference to FIG. 13 against the data received from the ticket use terminal (user terminal b) 21.

[0184] That is, first, it is determined whether the "IC card identifier (ID)" contained in the data received from the ticket usage terminal (user terminal b) 21 matches the "ticket usage terminal IC card identifier (ID)" registered in the "ticket transfer processing management database." If they match, it is further determined based on the data received from the ticket use terminal (user terminal b) 21 whether or not the ticket transfer notification conditions registered in the "ticket transfer processing management database" are met.

[0185] Processing from step S133 onwards is performed only if it is determined that the "IC card identifier (ID)" included in the data received from the ticket usage terminal (user terminal b) 21 matches the "ticket usage terminal IC card identifier (ID)" registered in the "ticket transfer processing management database" and further meets the ticket transfer notification conditions.

[0186] (Step S133b) In step S132b, if the ticket management server (service provider) 50 determines that the "IC card identifier (ID)" included in the received data from the ticket usage terminal (user terminal b) 21 matches the "ticket usage terminal IC card identifier (ID)" registered in the "ticket transfer processing management database" and further determines that the ticket transfer notification conditions are met, it executes processing in step S133b.

[0187] As a process to be performed when multiple conditions are met simultaneously, for example, all possible ticket options that can be received may be displayed and the user may select from among them.

[0188] In step S133b, the ticket management server (service provider) 50 transmits the following data to the ticket use terminal (user terminal b) 21: (a) The name of the user who authorized the ticket transfer (ticket transfer user name) (b) Details of the transferred ticket (type of ticket, etc.) These data are the data registered in the "ticket transfer processing management database" described above with reference to FIG.

[0189] (Step S134b) Next, in step S134b, the ticket usage terminal (user terminal b) 21 displays a display screen (UI) on the display unit, requesting user confirmation as to whether or not to accept the transfer ticket, based on the data received from the ticket management server (service provider) 50. As explained above, this display screen is the screen shown in FIG. 17 (S134). In addition, if the transfer ticket is a ticket that is transferred by writing it from a specific IC card compatible app to an IC card stored in the IC chip, user confirmation will be displayed on the display unit only if the IC card is stored in the IC chip of the ticket usage terminal.

[0190] The following process is the same as the process described with reference to FIG.

[0191] (3-(4) Processing sequence when the ticket use terminal (user terminal b) 12 uses the transfer ticket) Next, with reference to FIG. 20, "(4) Processing sequence when ticket use terminal (user terminal b) 12 uses a transfer ticket" will be described.

[0192] The sequence described with reference to FIG. 20 is a processing sequence after the transfer ticket becomes usable at the ticket use terminal (user terminal b) 12.

[0193] (Step S151) The ticket using user B 20 holds the ticket using terminal (user terminal b) 21 over the ticket use confirmation device (R / W) 60 in step S151.

[0194] The ticket usage confirmation device (R / W) 60 over which the ticket usage terminal (user terminal b) 21 is held when using the ticket may be different from or the same as the ticket usage confirmation device (R / W) 60 held over in step S121b.

[0195] The ticket using terminal (user terminal b) 21 used by ticket using user B 20 is set to be able to use transfer tickets. Specifically, for example, a ticket identifier and the like are recorded in the IC card data recording area of ​​the IC chip.

[0196] For example, a ticket usage confirmation device (R / W) 60 provided at a ticket gate of a station reads the ticket identifier from the IC chip of the ticket usage terminal (user terminal b) 21, and opens the ticket gate based on confirmation of the ticket identifier read. Ticket user B 20 is now able to pass through the gate.

[0197] (Step S152) Next, in step S152, the ticket usage confirmation device (R / W) 60 notifies the ticket management server (service provider) 50 of the usage of the transferred ticket. For example, the ticket identifier read from the IC chip of the ticket use terminal (user terminal b) 21 is sent to the ticket management server (service provider) 50 to notify the use of the transferred ticket.

[0198] (Step S153) When the ticket management server (service provider) 50 receives a notification of transfer ticket usage from the ticket usage confirmation device (R / W) 60, it updates the registered data in the "ticket transfer processing management database" managed by the ticket management server (service provider) 50 based on the received data.

[0199] Specifically, for example, the used transfer ticket identifier received from the ticket usage confirmation device (R / W) 60 is processed to register the transfer ticket identifier registered in the "ticket transfer processing management database" as a used ticket.

[0200] (Step S154) Next, the ticket management server (service provider) 50 notifies the ticket transfer terminal (user terminal a) 11 that the transfer ticket has been used.

[0201] (Step S155) Next, the ticket transfer terminal (user terminal a) 11 displays display data based on the transfer ticket usage notification from the ticket management server (service provider) 50 on the display unit of the ticket transfer terminal (user terminal a) 11.

[0202] For example, a message such as that shown in FIG. 21 is displayed on the display unit. The example shown in FIG. 21 displays the following message: "The green ticket for which transfer permission has been registered has been used. Transferee IC card identifier (ID) = 342a775." "There are three green tickets remaining that have been registered for transfer permission."

[0203] This display data is a message generated by the transfer process management application a of the ticket transfer terminal (user terminal a) 11 based on the data received from the ticket management server (service provider) 50.

[0204] By seeing this message, the ticket transfer user A, 10 can know that the transfer ticket has been used and how many transfer tickets remain.

[0205] [4. Various use cases of the ticket transfer process disclosed herein] Next, various examples of how the ticket transfer process of the present disclosure can be used will be described.

[0206] In the above-described embodiment, the ticket transfer user A, 10 and the ticket using user B, 20 are both individuals, and the process has been described as an example in which a ticket is transferred based on personal connections, such as friendships, family relationships, or colleagues accompanying each other on a business trip.

[0207] As an example of transfer within a family, someone in the family can purchase a multiple-use ticket, and as long as there are tickets remaining, the family, including the purchaser (who has previously sent the IC card identifiers (IDs) recorded on the IC chips of all members' ticket usage terminals to the ticket management server as potential transferees), can receive the multiple-use ticket when it is used and transfer it to a member of the family.

[0208] Furthermore, the ticket transfer process according to the configuration of the present disclosure is not limited to such interpersonal transactions, but various different processes are possible. The following processing example will be described. (1) Example of a company distributing tickets to employees (2) Example of a process where a company distributes tickets to customers (3) Example of a process where a campaign organizer distributes tickets to campaign applicants (4) Example of a process in which an advertising entity distributes tickets to members or an unspecified number of customers

[0209] (4-(1) Example of a company distributing tickets to employees) First, an example of a process in which a company distributes tickets to employees will be described.

[0210] For example, as shown in FIG. 22, a process can be performed in which tickets purchased by a company, such as tickets for airplanes, trains, taxis, etc., can be transferred to employees of the company.

[0211] In this case, the ticket transfer user A, 10, is an accountant of a company, and the ticket transfer terminal (user terminal a) is a company terminal such as a company PC. On the other hand, ticket using user B 20 is a group of employees. Each employee has a terminal such as a smartphone, which serves as a ticket using terminal (user terminal b) 21.

[0212] When the employee finishes work at the business trip destination and holds the ticket use terminal (user terminal b) 21 over the ticket gate at the station, a ticket transfer notice is displayed on the ticket use terminal (user terminal b) 21 according to the sequence described above. The employee, who is the ticket user B, 20, sees this ticket transfer notice and can receive and use the transferred ticket provided by the company.

[0213] (4-(2) Example of a process where a company distributes tickets to customers) Next, an example of a process in which a company distributes tickets to customers will be described.

[0214] As shown in FIG. 23, for example, a restaurant management company can apply this to a process in which it issues coupons to member customers who visit each restaurant it manages.

[0215] 23, the tickets are restaurant meal tickets, discount tickets, complimentary tickets, coupon tickets, etc. Ticket transfer user A, 10 is a ticket manager at the restaurant, and the ticket transfer terminal (user terminal a) is a company terminal such as a company PC. In this example, the ticket management server (service provider) 50 is also operated by the restaurant.

[0216] This is not limited to cases where a restaurant management company transfers tickets that can be used at its own stores to restaurant customers, but can also be used as a means of sending customers between multiple companies. For example, a process could be used where users who exit a specific station ticket gate by 8:00 a.m. are given discount tickets that can be used at the nearest store.

[0217] On the other hand, the ticket user B 20 is a pre-registered member customer. The terminal such as a smartphone owned by each member customer serves as the ticket usage terminal (user terminal b) 21.

[0218] When a member customer who is ticket using user B, 20, holds the ticket using terminal (user terminal b) 21 over the restaurant's reader / writer (R / W), i.e., ticket using confirmation device (R / W) 60, a ticket transfer notification is displayed on the ticket using terminal (user terminal b) 21 according to the sequence described above.

[0219] In this example, a notification is displayed that a coupon such as a meal ticket will be transferred. The customer, who is the ticket user B, 20, sees this ticket transfer notification, receives the transferred ticket, and can use it the next time he or she visits the store.

[0220] In this case, the ticket provided does not necessarily have to be written to an IC chip, but may be in the form of a ticket that the user shows to the store clerk on their smartphone screen or has the clerk scan a two-dimensional code when using it at the store.

[0221] In this way, the ticket transfer process of the present disclosure can be used in a variety of ways, not just for transferring tickets between individuals.

[0222] (4-(3) Example of a process where a campaign organizer distributes tickets to campaign applicants) Next, an example of a process in which a campaign organizer distributes tickets to campaign applicants will be described.

[0223] It is also possible to apply this to a process of distributing coupons, gift certificates, or other tickets by lottery or on a first-come, first-served basis to users who have applied for a company's campaign.

[0224] Specifically, for example, a campaign applicant uses a user terminal to transmit an IC card identifier to a ticket management server, which is a service provider of a company hosting the campaign. The campaign organizer will select winners (ticket recipients) from among applicants by lottery or on a first-come, first-served basis.

[0225] The user then goes shopping at a store operated by the campaign sponsor and pays with their IC card using their user terminal. Alternatively, during the time period designated by the campaign sponsor, they hold their user terminal over the ticket gate at a station or the entrance / exit gate of a facility to enter or exit the station or facility. At this time, the user terminal sends a request to the ticket management server, which is a service provider of the campaign sponsor, to check if there are any transfer tickets available.

[0226] If the received IC card identifier (ID) is registered in the database as a winner, the ticket management server, which is a service provider for the campaign sponsoring company, notifies the user terminal that the transfer ticket (coupon, etc.) can be received, i.e., that the user has won. Based on this notification, the user can receive and use the coupon.

[0227] It is also possible to sequentially receive user location information from each user's user terminal, select only users entering a specific area as ticket transfer recipients, and send ticket transfer notifications only to the selected users.

[0228] (4-(4) Example of a process in which an advertising entity distributes tickets to members or an unspecified number of customers) Next, an example of a process in which an advertising entity distributes tickets to an unspecified number of customers will be described.

[0229] For example, an advertising entity advertising a certain product registers any of the following conditions for notification of the transfer of tickets it wishes to distribute in the service provider's ticket management server: the identifier of the ticket usage confirmation device, the time of entry and exit at the ticket gate at a station or facility entrance and exit gate, and user attributes (gender, age, hobbies, preferences, etc.).

[0230] When the ticket use terminal is held over the ticket use confirmation device, it sends a request to the ticket management server to check whether there is a transfer ticket that meets the transfer notification conditions.

[0231] If there is a ticket that matches the transfer notification conditions registered by the advertiser, a notification of the transferred ticket is sent to the ticket use terminal according to the above-mentioned process, and the user of the ticket use terminal responds to confirm receipt of the ticket from the advertiser and receives information for using the ticket, thereby becoming able to use the ticket.

[0232] In addition, rather than being triggered by the ticket usage terminal being held over the ticket usage confirmation device, the ticket management server may select a ticket user who meets the ticket transfer notification conditions from an accumulation of requests received in the past by the ticket management server, and notify the ticket usage terminal of the transferred ticket from the ticket management server. In this way, the ticket transfer process of the present disclosure can be used in a variety of ways.

[0233] The ticket transfer process of the present disclosure has been described above. The configuration of the present disclosure has the following advantages, for example: There will be no need to modify the infrastructure of reading devices such as ticket vending machines and ticket gates. The advantage is that it is only necessary to add and register the identifiers of the reading devices at stations in the corresponding area to the ticket management server (service provider) 50, and there are very few cost and time limitations on expanding the corresponding area.

[0234] In addition, tickets such as coupons, promotional tickets, product vouchers, and discount coupons that do not specify a date or time can be transferred, and the user to whom the ticket is transferred can use it any time within the expiration date, or anyone in a specified group can use it.

[0235] It can also be used to distribute product vouchers for campaign prizes. Furthermore, it is possible to process the process so that anyone can receive discount coupons on a first-come, first-served basis when they exit the ticket gate at a specified station on a specified date and time.

[0236] Furthermore, there is no need to stop at a ticket machine before passing through a ticket gate or other reading device. If the user to whom the ticket has been transferred wants to use the ticket on the same day, they can simply specify that they want to use it on the app after passing through the ticket gate (on conventional lines).If they do not want to use the ticket, they can leave it and use it at a later date as long as it is within the expiration date.

[0237] [5. Configuration example of information processing device] Next, a configuration example of an information processing device used for the processing of the present disclosure will be described. FIG. 24 is a diagram illustrating an example of the configuration of a user terminal such as a smartphone. FIG. 25 is a diagram illustrating an example of the hardware configuration of a user terminal and a server. Each of these components will be described in turn.

[0238] First, with reference to FIG. 24, a configuration example of an information processing device 150 such as a smartphone used as a user terminal will be described. As shown in Figure 24, an information processing device 150 such as a smartphone has a control unit (microcomputer, etc.) 151, an operation unit 152, a display unit 153, a secure element 154, a memory 155, a clock 156, a location information acquisition unit 157, a first communication unit 170, a second communication unit 180, and a power supply unit 190.

[0239] The first communication unit 170 includes a Bluetooth (registered trademark) communication unit 171, a Wi-Fi communication unit 172, and an other communication unit 173. The second communication unit 180 includes an NFC-CLF 181, a near field communication means 182, and an other communication unit 183.

[0240] The control unit (microcomputer or the like) 151 functions as a data processing unit that controls the processes executed in the information processing device 150. Note that the control programs, applications, etc. executed by the control unit (microcomputer or the like) 151 are stored in a memory 155.

[0241] The operation unit 152 is an operation unit that can be operated by the user, and includes various switches as well as a touch panel on the display unit 153. The user can select or input various information via the operation unit 152.

[0242] The display unit 153 is, for example, a liquid crystal display, and is used to display execution information of various applications.

[0243] The secure element 154 is an IC chip configured as an element having a secure memory and a memory control unit. The secure memory in the secure element 154 stores IC card identifiers (IDs) corresponding to each electronic money, usage history information, and the like, as explained above with reference to FIG. 2.

[0244] As described above, the memory 155 stores the control program executed by the control unit 151, applications such as a mobile electronic money application, user ID information, and the like. The clock 156 is clock information and outputs clock information to each processing unit. The location information acquisition unit 157 communicates with, for example, a GPS satellite and acquires current location information.

[0245] The first communication unit 170 is configured by a Bluetooth (registered trademark) communication unit 171, a Wi-Fi communication unit 172, and other communication units 173, and is used for communication with external devices, for example, a server, a PC, a smartphone, etc. The second communication unit 180 includes an NFC-CLF 181, a near field communication means 182, and other communication units 183, and performs communication processing with, for example, an IC card 130, or a reader / writer (R / W) 21 installed in a store, a ticket gate, etc. NFC-CLF181 is an NFC (Near Field Communication)-CLF (Contactless Front End) IC chip for short-range communication.

[0246] Next, with reference to FIG. 25, an example of the hardware configuration of an information processing device that constitutes a user terminal such as a smartphone, a ticket management server, and a ticket usage confirmation device will be described.

[0247] The configuration example shown in FIG. 25 will be described. A CPU (Central Processing Unit) 301 functions as a control unit or data processing unit that executes various processes in accordance with programs stored in a ROM (Read Only Memory) 302 or a storage unit 308. For example, it executes processes in accordance with the sequences described in the above-mentioned embodiments. A RAM (Random Access Memory) 303 stores programs and data executed by the CPU 301. The CPU 301, ROM 302, and RAM 303 are interconnected by a bus 304.

[0248] CPU 301 is connected to input / output interface 305 via bus 304, and input / output interface 305 is connected to input unit 306 including various switches, a keyboard, a mouse, a microphone, etc., and output unit 307 including a display, a speaker, etc. CPU 301 executes various processes in response to commands input from input unit 306, and outputs the processed results to output unit 307, for example.

[0249] The storage unit 308 connected to the input / output interface 305 is made up of, for example, a flash memory, a hard disk, etc., and stores various data and programs executed by the CPU 301. The communication unit 309 functions as a transmitter / receiver for data communication via a network such as short-range communication, Wi-Fi communication, Bluetooth (registered trademark) (BT) communication, or the Internet or a local area network, and communicates with external devices.

[0250] A drive 310 connected to the input / output interface 305 drives removable media 311 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory such as a memory card, and executes recording or reading of data.

[0251] 6. Summary of the Disclosure The embodiments of the present disclosure have been described in detail above with reference to specific examples. However, it is obvious that those skilled in the art can modify or substitute the embodiments without departing from the gist of the present disclosure. In other words, the present invention has been disclosed in the form of examples and should not be interpreted as being limited. To determine the gist of the present disclosure, the claims should be taken into consideration.

[0252] The technology disclosed in this specification can be configured as follows. (1) a storage unit for storing ticket transfer notification conditions; a data processing unit that receives a request from a ticket use terminal and, if the ticket transfer notification conditions are met, instructs the ticket use terminal to write ticket information; An information processing device having the above.

[0253] (2) The data processing unit receiving user response information from the ticket use terminal as to whether or not to accept the ticket transfer; The information processing device according to (1) instructs the ticket use terminal to write ticket information in response to user response information indicating that the ticket is to be transferred.

[0254] (3) The information processing device according to (1) or (2), wherein the instruction to write the ticket information to the ticket use terminal is an instruction to write to an IC chip in the ticket use terminal.

[0255] (4) The information processing device An information processing device described in any one of (1) to (3), in which the ticket usage terminal receives identifier information required to determine whether or not to issue the write instruction when it performs near-field communication with an external ticket usage confirmation device.

[0256] (5) The data processing unit The IC card identifier (ID) recorded in the ticket usage terminal is received from the ticket transfer destination terminal, The information processing device according to any one of (1) to (4) transmits the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal to a ticket management server.

[0257] (6) Receive the IC card identifier (ID) recorded in the ticket usage terminal from the ticket usage terminal to which the ticket is to be transferred, An information processing device having a data processing unit that transmits the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal to a ticket management server.

[0258] (7) The data processing unit The information processing device according to (6) specifies a plurality of ticket use terminals as ticket transfer destinations, sets ticket transfer notification conditions for each terminal, and transmits the conditions to the ticket management server.

[0259] (8) The data processing unit The information processing device according to any one of (6) to (7), wherein the information processing device transmits, to the ticket management server, near-field communication between the ticket use terminal and an external ticket use confirmation device as the ticket transfer notification condition.

[0260] (9) The data processing unit An information processing device described in any of (6) to (8), which outputs display data indicating completion of use of the transfer ticket to a display unit in response to receiving a notification from the ticket management server indicating that the transfer ticket has been used at the ticket use terminal.

[0261] (10) Receive a ticket transfer notification from the ticket management server indicating that the transfer ticket is available, and display a confirmation message on the display unit asking whether or not to accept the ticket; Sending the user's confirmation response to the ticket management server; an information processing device having a data processing unit that receives the transfer ticket from the ticket management server when the user's confirmation response indicates ticket receipt;

[0262] (11) The data processing unit The information processing device according to (10) obtains an IC card identifier (ID) recorded in the ticket use terminal and transmits it to the ticket transfer terminal that is the ticket transfer source.

[0263] (12) The ticket transfer notification conditions registered in the ticket management server are: In the case of proximity communication between the information processing device and an external ticket usage confirmation device, The data processing unit When near-field communication is performed between the information processing device and an external ticket usage confirmation device, an identifier of the ticket usage confirmation device is received and transmitted to the ticket management server; The ticket transfer notification conditions registered in the ticket management server are: When the information processing device is located at a specific location, The data processing unit The information processing device according to (10) or (11), which transmits location information of the information processing device to the ticket management server.

[0264] (13) An information processing system having a ticket transfer terminal, a ticket use terminal, and a ticket management server, The ticket transfer terminal (a) the type or identifier of the ticket being transferred; (b) the conditions for notifying the ticket transfer to the ticket use terminal; Sending the above data (a) to (b) to the ticket management server; The ticket management server The data (a) to (b) received from the ticket transfer terminal are registered in a database; The ticket use terminal determines whether or not the ticket transfer notification conditions registered in the database are satisfied; When the ticket use terminal determines that the ticket transfer notification conditions are met, the information processing system transmits to the ticket use terminal a ticket transfer notification indicating that the transfer ticket can be received.

[0265] (14) An information processing method executed in an information processing device, a data processing unit of the information processing device, An information processing method for receiving a request from a ticket use terminal and instructing the ticket use terminal to write ticket information when the request matches ticket transfer notification conditions stored in a storage unit.

[0266] (15) An information processing method executed in an information processing device, a data processing unit of the information processing device, The IC card identifier (ID) recorded in the ticket usage terminal is received from the ticket transfer destination terminal, An information processing method for transmitting the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal to a ticket management server.

[0267] (16) An information processing method executed in an information processing device, a data processing unit of the information processing device, A ticket transfer notification is received from the ticket management server, indicating that the transfer ticket can be received, and a confirmation message is displayed on the display unit asking whether or not to receive the ticket. Sending the user's confirmation response to the ticket management server; The information processing method includes receiving a transfer ticket from the ticket management server if the user's confirmation response indicates ticket acceptance.

[0268] (17) A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A program for receiving a request from a ticket use terminal and instructing the ticket use terminal to write ticket information when the request matches a ticket transfer notification condition stored in a storage unit.

[0269] (18) A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A process of receiving an IC card identifier (ID) recorded in the ticket usage terminal from the ticket transfer destination ticket usage terminal; A program that executes a process of transmitting the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and the ticket transfer notification conditions for the ticket use terminal to a ticket management server.

[0270] (19) A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A process of receiving a ticket transfer notification from the ticket management server, indicating that the transfer ticket can be received, and displaying a confirmation message on the display unit asking whether or not to receive the ticket; sending a user confirmation response to the ticket management server; a program for executing a process for receiving a transfer ticket from the ticket management server when the user's confirmation response indicates that the ticket has been received;

[0271] (20) The ticket transfer notification conditions registered in the ticket management server are: In the case of proximity communication between the information processing device and an external ticket usage confirmation device, When near-field communication is performed between the information processing device and an external ticket usage confirmation device, The program causes the data processing unit to The program according to (19), which causes the identifier of the ticket usage confirmation device to be received and transmitted to the ticket management server.

[0272] Furthermore, the series of processes described in this specification can be executed by hardware, software, or a combination of both. When executing processes by software, a program recording the processing sequence can be installed and executed in the memory of a computer incorporated in dedicated hardware, or the program can be installed and executed on a general-purpose computer capable of executing various processes. For example, the program can be pre-recorded on a recording medium. In addition to installing the program on a computer from the recording medium, the program can also be received via a network such as a LAN (Local Area Network) or the Internet and installed on a recording medium such as an internal hard disk.

[0273] The various processes described in this specification may not only be executed in chronological order as described, but may also be executed in parallel or individually depending on the processing capabilities of the devices executing the processes or as needed. Furthermore, in this specification, a system refers to a logical collective configuration of multiple devices, and is not limited to devices that are all located in the same housing. [Industrial Applicability]

[0274] As described above, according to the configuration of one embodiment of the present disclosure, a configuration is realized that allows ticket transfer between a ticket transfer terminal and a ticket use terminal to be easily and reliably executed. Specifically, for example, a system may have a ticket transfer terminal, a ticket use terminal, and a ticket management server, and the ticket transfer terminal registers the following data in the ticket management server's database: (a) the type or identifier of the ticket to be transferred, (b) the IC card identifier (ID) recorded in the ticket use terminal to which the ticket is to be transferred, and (c) the ticket transfer notification conditions for the ticket use terminal. If the server determines that the ticket use terminal meets the ticket transfer notification conditions registered in the database, it sends a ticket transfer notification to the ticket use terminal indicating that the transferred ticket is available for receipt, and sends the ticket to the ticket use terminal in response to the transfer request received from the ticket use terminal. This configuration realizes a configuration that allows ticket transfer between the ticket transfer terminal and the ticket use terminal to be easily and reliably executed. [Explanation of symbols]

[0275] 11 Ticket transfer terminal 21 Ticket terminal 50 Ticket Management Server (Service Provider) 60 Ticket usage management device (R / W) 150 Information processing equipment 151 Control unit (microcomputer, etc.) 152 Operation section 153 Display section 154 Secure Element 155 memory 156 Clock 157 Location information acquisition unit 170 First Communications Department 180 Second Communications Department 190 Power supply section 301 CPU 302 ROM 303 RAM 304 Bus 305 Input / Output Interface 306 Input section 307 Output section 308 Storage section 309 Communications Department 310 Drive 311 Removable Media

Claims

1. a storage unit for storing ticket transfer notification conditions; a data processing unit that receives a request from a ticket use terminal and instructs the ticket use terminal to write ticket information when the ticket transfer notification condition is met; The data processing unit Receive an IC card identifier (ID) recorded in the ticket usage terminal from the ticket transfer destination ticket usage terminal, An information processing device receives, from the ticket transfer terminal, the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal.

2. The data processing unit receiving user response information from the ticket use terminal as to whether or not to accept the ticket transfer; 2. The information processing device according to claim 1, wherein an instruction to write ticket information to the ticket use terminal is issued in response to user response information indicating that the ticket is to be transferred.

3. 2. The information processing apparatus according to claim 1, wherein the instruction to write the ticket information to the ticket use terminal is an instruction to write the ticket information to an IC chip in the ticket use terminal.

4. The information processing device includes: The information processing device according to claim 1 , wherein the ticket use terminal receives identifier information required to determine whether or not to issue the write instruction when it has performed near-field communication with an external ticket use confirmation device.

5. Receive an IC card identifier (ID) recorded in the ticket usage terminal from the ticket transfer destination ticket usage terminal, An information processing device having a data processing unit that transmits the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal to a ticket management server.

6. The data processing unit 6. The information processing device according to claim 5, wherein a plurality of ticket use terminals are designated as ticket transfer recipients, ticket transfer notification conditions are set for each terminal, and the conditions are transmitted to the ticket management server.

7. The data processing unit The information processing device according to claim 5 , wherein near field communication between the ticket use terminal and an external ticket use confirmation device is transmitted to the ticket management server as the ticket transfer notification condition.

8. The data processing unit 6. The information processing device according to claim 5, wherein, in response to receiving a notification from the ticket management server indicating that the transfer ticket has been used at the ticket use terminal, display data indicating that the transfer ticket has been used is output to a display unit.

9. A data processing unit that acquires an IC card identifier (ID) recorded in the ticket use terminal and transmits it to the ticket transfer terminal that is the ticket transfer source, The data processing unit further executes communication with a ticket management server that receives the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and the ticket transfer notification conditions for the ticket use terminal from the ticket transfer terminal and registers them in a database; receiving a ticket transfer notification from the ticket management server indicating that the transfer ticket can be received, and displaying a confirmation message on the display unit asking whether or not to receive the ticket; Sending the user's confirmation response to the ticket management server; If the user's confirmation response indicates ticket receipt, the information processing device executes a process of receiving the transfer ticket from the ticket management server.

10. The data processing unit 10. The information processing device according to claim 9, wherein an IC card identifier (ID) recorded in the ticket use terminal is acquired and transmitted to the ticket transfer terminal that is the ticket transfer source.

11. The ticket transfer notification conditions registered in the ticket management server are: In the case of proximity communication between the information processing device and an external ticket usage confirmation device, The data processing unit When near-field communication is performed between the information processing device and an external ticket usage confirmation device, an identifier of the ticket usage confirmation device is received and transmitted to the ticket management server; The ticket transfer notification conditions registered in the ticket management server are: When the information processing device is located at a specific location, The data processing unit The information processing device according to claim 9 , wherein the location information of the information processing device is transmitted to the ticket management server.

12. An information processing system having a ticket transfer terminal, a ticket use terminal, and a ticket management server, The ticket transfer terminal (a) the type or identifier of the ticket to be transferred; (b) conditions for notifying the ticket transfer to the ticket use terminal; (c) an IC card identifier (ID) recorded in the ticket use terminal in advance received from the ticket use terminal; Transmitting the above data (a) to (c) to the ticket management server; The ticket management server The data (a) to (c) received from the ticket transfer terminal are registered in a database; Receive an IC card identifier (ID) recorded in the ticket usage terminal from the ticket transfer destination ticket usage terminal, It is determined whether the received IC card identifier (ID) matches the IC card identifier (ID) recorded in the database, and if they match, The ticket use terminal determines whether or not the ticket transfer notification conditions registered in the database are satisfied; When the ticket use terminal determines that the ticket transfer notification conditions are met, the information processing system transmits to the ticket use terminal a ticket transfer notification indicating that the transfer ticket can be received.

13. An information processing method executed in an information processing device, a data processing unit of the information processing device, receiving a request from a ticket use terminal, and if the request matches the ticket transfer notification conditions stored in the storage unit, issuing an instruction to write ticket information to the ticket use terminal; The data processing unit further Receive an IC card identifier (ID) recorded in the ticket usage terminal from the ticket transfer destination ticket usage terminal, An information processing method for receiving, from a ticket transfer terminal, the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal.

14. An information processing method executed in an information processing device, a data processing unit of the information processing device, Receive an IC card identifier (ID) recorded in the ticket usage terminal from the ticket transfer destination ticket usage terminal, An information processing method for transmitting the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal to a ticket management server.

15. An information processing method executed in an information processing device, a data processing unit of the information processing device, An IC card identifier (ID) recorded in the information processing device is acquired and transmitted to a ticket transfer terminal that is the ticket transfer source; executes communication with a ticket management server that receives the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal from the ticket transfer terminal and registers them in a database; receiving a ticket transfer notification from the ticket management server indicating that the transfer ticket can be received, and displaying a confirmation message on the display unit asking whether or not to receive the ticket; Sending the user's confirmation response to the ticket management server; The information processing method includes receiving a transfer ticket from the ticket management server if the user's confirmation response indicates ticket acceptance.

16. A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A request is received from a ticket use terminal, and if the request matches the ticket transfer notification conditions stored in the storage unit, an instruction is given to the ticket use terminal to write ticket information; and The IC card identifier (ID) recorded in the ticket use terminal is received from the ticket use terminal to which the ticket is to be transferred, A program for receiving, from a ticket transfer terminal, the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and ticket transfer notification conditions for the ticket use terminal.

17. A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A process of receiving an IC card identifier (ID) recorded in the ticket use terminal from the ticket use terminal to which the ticket is to be transferred; A program that executes a process of transmitting the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and the ticket transfer notification conditions for the ticket use terminal to a ticket management server.

18. A program for causing an information processing device to execute information processing, a data processing unit of the information processing device; A process of acquiring an IC card identifier (ID) recorded in the information processing device and transmitting it to a ticket transfer terminal that is the ticket transfer source; A communication process with a ticket management server that receives the ticket identifier of the ticket to be transferred, the IC card identifier (ID), and the ticket transfer notification conditions for the ticket use terminal from the ticket transfer terminal and registers them in a database; receiving a ticket transfer notification from the ticket management server indicating that the transfer ticket can be received, and displaying a confirmation message on a display unit asking whether or not to receive the ticket; sending a user confirmation response to the ticket management server; a program for executing a process for receiving a transfer ticket from the ticket management server when the user's confirmation response indicates that the ticket has been received;

19. The ticket transfer notification conditions registered in the ticket management server are: near-field communication between the information processing device and an external ticket usage confirmation device; When near-field communication is performed between the information processing device and an external ticket usage confirmation device, The program causes the data processing unit to 19. The program according to claim 18, wherein the program causes the identifier of the ticket usage confirmation device to be received and transmitted to the ticket management server.

Images