Ticket management device and ticket management method

JPWO2024142301A5Active Publication Date: 2025-01-24RAKUTEN GROUP INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024567077
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-12-27
Filing Date
2022-12-27
Publication Date
2025-01-24
Estimated Expiration
2042-12-27

AI Technical Summary

Technical Problem

Event organizers face equipment wastage and inefficiency when ticket holders fail to attend events without notice, leading to unused facilities and financial disadvantages.

Method used

A system utilizing location information from user terminals to estimate cancellation possibilities by comparing the time required to reach the event venue with the event's grace period, sending confirmation messages, and processing cancellations to sell surplus tickets effectively.

Benefits of technology

This solution allows for the effective utilization of event venue facilities by identifying likely cancellations and selling surplus tickets, thereby minimizing waste and optimizing event participation.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

In the present invention, a ticket management device has one or a plurality of processors. The one or plurality of processors performs a process including: acquiring the current location of a wireless communication terminal owned by a user who has purchased a ticket to attend an event; acquiring the time required to travel from the current location of the wireless communication terminal to the venue of the event; estimating the possibility that the user will cancel attendance at the event by comparing the grace period from the current time to the start time of the event with the required time; and if the estimated cancellation possibility satisfies a prescribed condition, transmitting a message to the wireless communication terminal to confirm whether or not the attendance be cancelled.
Need to check novelty before this filing date? Find Prior Art

Description

Cancellation estimation using location information

[0001] The present disclosure relates to cancellation estimation using location information.

[0002] Generally, participants in an event such as a concert or a sporting event purchase tickets in advance from the event organizer and present the tickets on the day of the event to enter the event venue. In recent years, tickets have been issued as electronic tickets, and ticket information is stored in a terminal device such as a smartphone carried by the user.

[0003] Japanese Patent Application Laid-Open No. 2020-194504

[0004] However, if an event participant is suddenly unable to attend the event, there is a problem that the facilities at the event venue are wasted. In particular, if a participant who purchased a ticket does not show up at the event venue without permission, the facilities such as seats reserved for that participant will not be used effectively, and the event organizer will suffer a disadvantage.

[0005] The present disclosure has been made in consideration of the above, and aims to provide a cancellation estimation method using location information that enables effective use of facilities at an event venue.

[0006] According to one aspect of the present disclosure, a ticket management device includes one or more processors that execute a process including acquiring a current location of a wireless communication terminal carried by a user who has purchased a ticket to participate in an event, acquiring a required travel time from the current location of the wireless communication terminal to the event venue, estimating a likelihood that the user will cancel their participation in the event by comparing the required travel time with a grace period from the current time to the start time of the event, and transmitting a message to the wireless communication terminal to confirm whether or not the user will cancel if the estimated likelihood of cancellation satisfies a predetermined condition.

[0007] Furthermore, according to one aspect of the present disclosure, a cancellation estimation method includes acquiring the current location of a wireless communication terminal carried by a user who has purchased a ticket to participate in an event, acquiring a required time for traveling from the current location of the wireless communication terminal to the event venue, estimating the possibility that the user will cancel their participation in the event by comparing the required time with a grace period from the current time to the start time of the event, and, if the estimated possibility of cancellation satisfies a predetermined condition, sending a message to the wireless communication terminal to confirm whether or not there will be a cancellation.

[0008] FIG. 1 is a diagram showing an example of a cancellation estimation system according to an embodiment. FIG. 2 is a block diagram showing the configuration of a ticket management device according to an embodiment. FIG. 3 is a flow diagram showing the operation of a ticket management device according to an embodiment. FIG. 4 is a flow diagram showing a required time calculation method. FIG. 5 is a sequence diagram showing a cancellation estimation method. FIG. 6 is a block diagram showing an example of the hardware configuration of a ticket management device.

[0009] Hereinafter, an embodiment according to the present disclosure will be described with reference to the accompanying drawings. The embodiment described below is an example and should not be construed as being limited by this description.

[0010] Fig. 1 is a diagram showing an example of a cancellation estimation system according to an embodiment. The cancellation estimation system shown in Fig. 1 estimates the possibility that a participant who has a ticket will cancel their participation in an event when an event in which the participant can participate is held at an event venue V. The cancellation estimation system includes a ticket management device 100 and a map information system 200, and the ticket management device 100 is connected to a mobile network that includes a base station 10 and a user terminal 20.

[0011] The base station 10 forms a cell within a range where radio waves can reach, and performs wireless communication with the user terminals 20 within the cell. Each cell formed by the base station 10 is assigned a cell ID, which is identification information, and it is possible to identify the base station 10 that forms each cell from the cell ID.

[0012] When a user terminal 20 is present within a cell formed by a base station 10, it performs wireless communication with the base station 10 that forms this cell. Of these user terminals 20, the user terminals 20 of participants attending an event held at an event venue V store ticket information for tickets required to participate in the event. Therefore, event participants can enter the event venue V and participate in the event by, for example, presenting the ticket information stored in the user terminal 20.

[0013] The ticket management device 100 manages ticket information stored in the user terminals 20. The ticket management device 100 stores ticket information issued to the user terminals 20 of participants who purchased tickets, in association with the identification information of the user terminals 20. The ticket management device 100 then estimates the likelihood of canceling participation in the event based on the current location of each user terminal 20 before the event starts. The ticket management device 100 checks whether or not a cancellation has occurred for user terminals 20 that are likely to cancel their participation in the event, and if a cancellation is confirmed, reflects the occurrence of the cancellation in the ticket information. The configuration and operation of the ticket management device 100 will be described in detail later.

[0014] The map information system 200 is a system that stores map information and collects dynamic information such as weather and traffic information, and is capable of processing the map information and searching for composite information. An example of such a map information system 200 is a dynamic map system. Upon receiving a request from the ticket management device 100, the map information system 200 calculates the amount of time required to travel from the current location of the user terminal 20 to the event venue V. At this time, the map information system 200 searches for the shortest route from the current location of the user terminal 20 to the event venue V, and calculates the amount of time required for the shortest route taking into account weather and traffic information.

[0015] Fig. 2 is a block diagram showing the configuration of a ticket management device 100 according to one embodiment. The ticket management device 100 shown in Fig. 2 includes a communication interface unit (hereinafter abbreviated as "communication I / F unit") 110, a ticket information storage unit 120, a cell ID collection unit 130, a required time acquisition unit 140, a cancellation estimation unit 150, a cancellation confirmation unit 160, a cancellation processing unit 170, and a sales processing unit 180.

[0016] The communication I / F unit 110 has an interface for communicating with the base station 10, the user terminal 20, and the map information system 200, and transmits and receives various information. Specifically, the communication I / F unit 110 receives, from the user terminal 20, the cell ID of the cell in which the user terminal 20 is located, and transmits a calculation request to the map information system 200 to calculate the required time.

[0017] The ticket information storage unit 120 stores ticket information issued to the user terminal 20 in association with the identification information of the user terminal 20. That is, when a user purchases a ticket to participate in an event, the ticket information storage unit 120 stores the ticket information, including information such as the date and time of the event, the venue, and the type of seating, in association with the identification information of the user terminal 20 of the user.

[0018] Before the event starts, the cell ID collection unit 130 calculates the grace period from the current time until the start of the event, and when the grace period reaches a predetermined time, transmits a request to send a cell ID to the user terminals 20 that hold the ticket information. The cell ID collection unit 130 then collects, from the user terminals 20, cell IDs that identify the cell with which each user terminal 20 is currently communicating. The cell ID collection unit 130 identifies the location of the base station 10 that corresponds to the cell ID collected from the user terminals 20, and notifies the required time acquisition unit 140 of the location of the base station 10 as the current location of each user terminal 20.

[0019] When the current location of the user terminal 20 is notified by the cell ID collection unit 130, the required time acquisition unit 140 transmits a request to the map information system 200 to calculate the required time from the current location of the user terminal 20 to the event venue V. Then, in response to the calculation request, the required time acquisition unit 140 acquires the required time from the current location of the user terminal 20 to the event venue V from the map information system 200.

[0020] The cancellation estimation unit 150 estimates the likelihood that a user possessing a user terminal 20 will cancel their participation in the event based on the time required for each user terminal 20 to reach the event venue V. Specifically, the cancellation estimation unit 150 compares the grace period until the start of the event with the time required for the user terminal 20 to reach the event venue V, and determines whether the required time is equal to or less than the grace period. If the required time is equal to or less than the grace period, the cancellation estimation unit 150 estimates that the user will not be likely to cancel because they will arrive at the event venue V in time for the start of the event. Furthermore, if the required time exceeds the grace period, the cancellation estimation unit 150 estimates that the user will not be likely to arrive at the event venue V in time for the start of the event, and therefore the user will likely cancel.

[0021] The cancellation confirmation unit 160 transmits a confirmation message as to whether or not to cancel participation in the event to the user terminal 20 of the user who is estimated by the cancellation estimation unit 150 to be highly likely to cancel. Then, the cancellation confirmation unit 160 receives information indicating whether or not participation in the event has been canceled from the user terminal 20 as a response to the transmitted confirmation message.

[0022] The cancellation processing unit 170 executes cancellation processing for a user whose cancellation of participation in the event has been confirmed by the cancellation confirmation unit 160. Specifically, the cancellation processing unit 170 updates the ticket information stored in the ticket information storage unit 120 in association with the user terminal 20 of the user who cancels participation in the event, and registers the cancellation.

[0023] When the cancellation processing unit 170 executes the cancellation processing, the sales processing unit 180 executes the sales processing of the surplus tickets generated by the cancellation. That is, the sales processing unit 180, for example, carries out the procedure to sell the surplus tickets on a predetermined sales site, or inquires of pre-registered user terminals 20 about whether or not they have purchased any surplus tickets. When the surplus tickets are purchased, the sales processing unit 180 updates the ticket information of the surplus tickets stored in the ticket information storage unit 120 and associates them with the user terminal 20 of the user who purchased them.

[0024] Next, a ticket management method using the ticket management device 100 configured as described above will be described with reference to the flowchart shown in FIG.

[0025] Before the start of an event, the ticket information storage unit 120 of the ticket management device 100 stores ticket information associated with the identification information of the user terminals 20 of participants who have purchased tickets for the event. The cell ID collection unit 130 then calculates the grace period from the current time until the start of the event (step S101), and transmits a cell ID transmission request to the user terminals 20 of the participants who have purchased tickets when the grace period reaches a predetermined time. In response to the transmission request, the user terminals 20 of the participants transmit the cell IDs of the cells in which they currently reside to the ticket management device 100 via the base station 10. The cell IDs transmitted from each user terminal 20 are acquired by the cell ID collection unit 130 (step S102).

[0026] Since the cell ID is identification information unique to the base station 10, the cell ID collection unit 130 identifies the base station 10 to which each user terminal 20 is connected from the cell ID. Then, the location of the base station 10 is identified, and the location of the connected base station 10 is notified to the required time acquisition unit 140 as the current location of each user terminal 20. Note that instead of collecting cell IDs from each user terminal 20, the cell ID collection unit 130 may collect, from each user terminal 20, location information of the current location measured by the user terminal 20 using, for example, a global positioning system (GPS) or the like.

[0027] When the current location of each user terminal 20 is notified, the required time acquisition unit 140 transmits a request to the map information system 200 to calculate the required time from the current location of the user terminal 20 to the event venue V (step S103). The map information system 200 calculates the required time for each user terminal 20 to travel to the event venue V, and transmits information on the required time for each user terminal 20 to the ticket management device 100. The calculation of the required time by the map information system 200 will be described in detail later. The required time information transmitted from the map information system 200 is acquired by the required time acquisition unit 140.

[0028] Then, the cancellation estimation unit 150 uses the required time for each user terminal 20 to estimate the possibility that the user possessing each user terminal 20 will cancel their participation in the event. Specifically, the grace period until the start of the event is compared with the required time to reach the event venue V, and it is determined whether the user will arrive at the event venue V in time for the start of the event (step S104). If the result of this determination is that the required time is less than the grace period and the user will arrive at the event venue V in time for the start of the event (step S104: Yes), it is determined that the user is unlikely to cancel their participation in the event, and the processing ends.

[0029] On the other hand, if the result of the determination in step S104 is that the required time exceeds the grace period and the user will not arrive at the event venue V in time for the start of the event (step S104 No), it is then determined whether the user will arrive at the event venue V in time for the end of the event (step S105). This determination can be made, for example, by comparing the time obtained by adding the grace period until the start of the event to the duration of the event with the time required to reach the event venue V. Furthermore, for example, if the time allowed for entry into the event venue V after the start of the event is limited, the time obtained by adding the grace period for entry may be compared with the required time.

[0030] As a result of the determination in step S105, if the required time is equal to or less than the grace period plus the event duration, and the user will arrive at the event venue V in time for the event to end (step S105 Yes), it is determined that there is a possibility that the user will be late for the event. On the other hand, if the required time exceeds the grace period plus the event duration, and the user will not arrive at the event venue V in time for the event to end (step S105 No), it is determined that there is a high possibility that the user will cancel their participation in the event.

[0031] If it is determined that the user is likely to cancel participation in the event, the cancellation confirmation unit 160 transmits a confirmation message to the user terminal 20 inquiring whether or not to cancel participation in the event (step S106). If it is determined that the user is likely to be late for the event, the cancellation confirmation unit 160 transmits a confirmation message to the user terminal 20 inquiring whether or not to cancel participation in the event (step S107), notifying the user that the user may not make it in time for the start of the event.

[0032] The user terminal 20 that receives the confirmation message presents the confirmation message to the user and transmits a response indicating whether or not the user intends to cancel to the ticket management device 100. The response regarding whether or not the user intends to cancel transmitted from the user terminal 20 is acquired by the cancellation confirmation unit 160. The cancellation processing unit 170 then determines whether or not a response indicating that participation in the event will be canceled has been obtained (step S108). If the result of this determination indicates that participation in the event will not be canceled (step S108 No), it is determined that the user will participate in the event, and the process ends.

[0033] On the other hand, if a response indicating that participation in the event will be canceled is received (Yes in step S108), a cancellation process is executed (step S109). That is, the ticket information stored in the ticket information storage unit 120 is updated, and the fact that participation in the event has been canceled is registered for the user terminal 20 of the user who cancels participation in the event. When such a cancellation occurs, the canceled tickets become surplus tickets. Therefore, the sales processing unit 180 executes a sales process to sell the surplus tickets. As a result, the canceled tickets are purchased by other participants, and this participant can participate in the event, thereby enabling effective use of the facilities at the event venue V.

[0034] Next, a required time calculation method using the map information system 200 will be described with reference to the flowchart shown in FIG.

[0035] The map information system 200 receives a required time calculation request from the ticket management device 100, which request includes information on the current location of the user terminal 20 and the location of the event venue V (step S201). In response to this request, the map information system 200 searches for the shortest route from the current location of the user terminal 20 to the event venue V (step S202). The shortest route searched here is the route that requires the shortest travel time from the current location of the user terminal 20 to the event venue V, and various means of transportation for traveling along this route may be included.

[0036] After obtaining the shortest route through the search, the map information system 200 obtains weather information and traffic information for the shortest route (step S203).The map information system 200 then calculates the actual travel time based on the travel time for traveling along the shortest route, taking into account weather and traffic conditions (step S204).The map information system 200 calculates the travel time from the current location to the event venue V for each user terminal 20, and transmits travel time information including the travel time for each user terminal 20 to the ticket management device 100 (step S205).

[0037] In this way, the required time is calculated based on weather and traffic conditions, so the ticket management device 100 is notified of the time required for the user terminal 20 to actually travel to the event venue V, and the possibility of cancellation can be accurately estimated.

[0038] FIG. 5 is a sequence diagram showing a cancellation estimation method in the above cancellation estimation system.

[0039] Assume that a user terminal 20 holding ticket information for participating in an event is currently connected to a base station 10 that forms the cell in which the user terminal 20 is located (step S301). When a predetermined time has elapsed until the start of the event, the ticket management device 100 transmits a request for a cell ID to the user terminal 20 holding the ticket information (step S302). In response to this request, the user terminal 20 transmits the cell ID of the cell formed by the base station 10 to which the user terminal 20 is currently connected to the ticket management device 100 (step S303).

[0040] The ticket management device 100 collects cell IDs from each user terminal 20 that holds ticket information, and identifies the base station 10 corresponding to the cell ID. The ticket management device 100 then determines the location of the base station 10 as the current location of the user terminal 20 and transmits a request to the map information system 200 to calculate the required time from the current location of the user terminal 20 to the event venue V (step S304). The map information system 200 searches for the shortest route from the current location of each user terminal 20 to the event venue V (step S305), and calculates the required time to the event venue V for each user terminal 20 by taking into account weather and traffic information on the shortest route (step S306). The map information system 200 transmits required time information, including the required time for each user terminal 20, to the ticket management device 100 (step S307).

[0041] The ticket management device 100 estimates the likelihood that the user of the user terminal 20 will cancel their participation in the event based on the required time for each user terminal 20 (step S308). That is, the ticket management device 100 compares the grace period until the start of the event with the required time for the user terminal 20 to reach the event venue V, and if the required time is less than the grace period, the ticket management device 100 estimates that the user will arrive at the event venue V in time for the start of the event, and therefore is unlikely to cancel. On the other hand, if the required time exceeds the grace period, the ticket management device 100 estimates that the user will not arrive at the event venue V in time for the start of the event, and therefore is likely to either be late for the event or to cancel their participation in the event.

[0042] The ticket management device 100 sends a confirmation message to the user terminal 20 of a user who is estimated to be likely to be late or to cancel his / her participation in the event, asking whether or not the user will cancel (step S309). The user terminal 20 presents the confirmation message to the user and accepts an answer. The user terminal 20 then sends a response indicating whether or not the user will cancel to the ticket management device 100 (step S310). If the ticket management device 100 receives an answer indicating cancellation, it executes a cancellation process to register the cancellation in the ticket information associated with the user terminal 20 (step S311).

[0043] In this way, the ticket management device 100 estimates the likelihood of a user canceling based on the time required to travel from the current location of the user terminal 20 to the event venue V, and inquires about whether or not users who are likely to cancel will cancel. This makes it possible to know in advance that users who are likely to cancel will cancel their participation in the event, and to sell any surplus tickets resulting from the cancellation to other users. As a result, other users who purchase surplus tickets can participate in the event, thereby enabling effective use of the facilities at the event venue V.

[0044] As described above, according to this embodiment, the ticket management device acquires the current location of the user terminal carried by the user who purchased the ticket, acquires the estimated travel time from the current location to the event venue, and estimates the likelihood that the user will cancel their participation in the event based on the estimated travel time. The device then checks with users who are likely to cancel whether they will cancel, and executes cancellation processing for users who respond indicating that they will cancel. Therefore, surplus tickets resulting from cancellations can be sold to other users, and by having these users participate in the event, the facilities at the event venue can be utilized more effectively.

[0045] In the above embodiment, the location of the base station 10 to which the user terminal 20 is connected is used as the current location of the user terminal 20. However, it goes without saying that the current location determined by the user terminal 20 may also be used. In this case, the user terminal 20 may determine its own current location using, for example, GPS, and transmit the current location to the ticket management device 100 instead of the cell ID.

[0046] The ticket management device 100 according to the embodiment can be configured using a processor and a memory. Fig. 6 is a block diagram showing an example of the hardware configuration of the ticket management device 100 according to the embodiment. As shown in Fig. 6, the ticket management device 100 includes a processor 101, a memory 102, a storage 103, and a communication unit 104.

[0047] The processor 101 includes, for example, a central processing unit (CPU), a field programmable gate array (FPGA), or a digital signal processor (DSP), and controls the entire ticket management device 100 and executes various types of information processing.

[0048] The memory 102 includes, for example, a random access memory (RAM) or a read only memory (ROM), and stores information used in the information processing executed by the processor 101 .

[0049] The storage 103 includes, for example, a hard disk drive (HDD) or a solid state drive (SSD), and stores various types of data.

[0050] The communication unit 104 has an interface for performing wired or wireless communication, and communicates with the base station 10 and the map information system 200 .

[0051] The ticket management device 100 may also have other components not shown, such as a display and an operation switch.

[0052] The processing performed by the ticket management device 100 described in the above embodiment can also be written as a computer-executable program. In this case, this program can be stored on a computer-readable, non-transitory recording medium and installed on the computer. Examples of such recording media include portable recording media such as CD-ROMs, DVDs, and USB memory, as well as semiconductor memories such as flash memories.

[0053] It should be noted that the present disclosure is not limited to the above-described embodiment, but also includes various modifications in which components are added, deleted, or converted from the above-described configuration.

[0054] The present disclosure described above includes the following [1] to [7].

[0055] [1] A ticket management device having one or more processors that executes processes including: acquiring the current location of a wireless communication terminal carried by a user who has purchased a ticket to participate in an event; acquiring the required time for traveling from the current location of the wireless communication terminal to the venue of the event; estimating the possibility that the user will cancel their participation in the event by comparing the required time with the grace period from the current time until the start time of the event; and, if the estimated possibility of cancellation satisfies a predetermined condition, sending a message to the wireless communication terminal to confirm whether or not the user will cancel.

[0056] [2] The ticket management device described in [1] above acquires the required time by calculating the required time from the travel time required to travel the shortest route from the current location of the wireless communication terminal to the event venue, based on the weather and traffic conditions on the shortest route.

[0057] [3] The ticket management device according to [1] or [2], wherein the estimation is performed by estimating that the user is likely to cancel participation in the event if the required time exceeds the grace time.

[0058] [4] The ticket management device according to [3], wherein the estimation is performed by estimating that the user is likely to be late for the event if the required time is equal to or less than the grace time plus the duration of the event.

[0059] [5] The ticket management device according to [1] or [2], wherein acquiring the current location includes acquiring identification information of a cell in which the wireless communication terminal is located, and identifying the location of a base station corresponding to the cell from which the identification information is acquired.

[0060] [6] The ticket management device described in [1] or [2] above, wherein the processing further includes: when a response indicating cancellation to the message is obtained from the wireless communication terminal, executing a cancellation process for the ticket associated with the wireless communication terminal; and executing a sales process for the ticket for which the cancellation process is being executed.

[0061] [7] A cancellation estimation method comprising: acquiring the current location of a wireless communication terminal carried by a user who has purchased a ticket to participate in an event; acquiring the time required to travel from the current location of the wireless communication terminal to the venue of the event; estimating the possibility that the user will cancel their participation in the event by comparing the time allowed from the current time until the start time of the event with the required time; and, if the estimated possibility of cancellation satisfies a predetermined condition, sending a message to the wireless communication terminal to confirm whether or not there will be a cancellation.

[0062] REFERENCE SIGNS LIST 10 Base station 20 User terminal 100 Ticket management device 101 Processor 102 Memory 103 Storage 104 Communication unit 110 Communication I / F unit 120 Ticket information storage unit 130 Cell ID collection unit 140 Required time acquisition unit 150 Cancellation estimation unit 160 Cancellation confirmation unit 170 Cancellation processing unit 180 Sales processing unit 200 Map information system

Claims

1. One or more processors; The one or more processors: Obtaining a current location of a wireless communication terminal possessed by a user who has purchased a ticket to participate in an event; acquiring a required time required for travel from a current location of the wireless communication terminal to a venue of the event; transmitting a message to the wireless communication terminal based on a comparison result between a grace period from a current time to a start time of the event and the required time; Perform a process including Sending the message comprises: if the required time is equal to or less than the time obtained by adding the grace time to the duration of the event, transmitting a message to the wireless communication terminal notifying the wireless communication terminal that the event may not be in time for the start of the event and asking whether or not to cancel the event; If the required time exceeds a time obtained by adding the grace time to the duration of the event, a message is sent to the wireless communication terminal to confirm whether or not the event is to be canceled. Ticket management device.

2. Obtaining the required time A required time is obtained based on a travel time required to travel the shortest route from the current location of the wireless communication terminal to the venue of the event, the required time being calculated according to weather and traffic conditions of the shortest route. The ticket management device according to claim 1 .

3. The obtaining of the current location includes: Obtaining identification information of a cell in which the wireless communication terminal is located; determining the location of a base station corresponding to a cell from which the identification information is obtained; 3. The ticket management device according to claim 1, further comprising:

4. The process comprises: When a response to the message indicating cancellation is obtained from the wireless communication terminal, a cancellation process is executed for the ticket associated with the wireless communication terminal; Executing a sales process for the ticket for which the cancellation process is executed; The ticket management device according to claim 1 or 2, further comprising:

5. Obtaining a current location of a wireless communication terminal possessed by a user who has purchased a ticket to participate in an event; acquiring a required time required for travel from a current location of the wireless communication terminal to a venue of the event; transmitting a message to the wireless communication terminal based on a comparison result between a grace period from a current time to a start time of the event and the required time; having Sending the message comprises: if the required time is equal to or less than the time obtained by adding the grace time to the duration of the event, transmitting a message to the wireless communication terminal notifying the wireless communication terminal that the event may not be in time for the start of the event and asking whether or not to cancel the event; If the required time exceeds a time obtained by adding the grace time to the duration of the event, a message is sent to the wireless communication terminal to confirm whether or not the event is to be canceled. Ticket management methods.