Event management device, event management program, and event management system

Abstract

[Problem] To improve user convenience. [Solution] An event management device 10 is communicably connected to user terminals 20A, 20B, 20C,.... The event management device 10 comprises a management unit 112, a notification unit 113, and a control unit 111. The management unit 112 is capable of managing the status of a user. The management unit 112 is capable of notifying the user regarding a message. The control unit 111 is capable of controlling the management unit 112 and the management unit 112. The control unit 111 is capable of reporting a message that corresponds to the status of the user.

Description

Event management device, event management program, and event management system

[0001] The present invention relates to an event management device, an event management program, and an event management system.

[0002] 2. Description of the Related Art Conventionally, with regard to technology for transmitting and receiving messages using information processing terminals, a communication method has been proposed in which a member of a chat service sends a message to a non-member (for example, see Patent Document 1).

[0003] Also, an event management device is known that manages face-to-face events such as competitive games using physical cards, such as accepting applications to participate, drawing participants by lottery, confirming participation at the event venue, and sending information messages.

[0004] JP 2014-006870 A

[0005] For users who wish to participate in an event, convenience is desirable, and there is room for further improvement in this regard.

[0006] An object of the present invention is to provide an event management device, an event management program, and an event management system that can improve user convenience.

[0007] An event management device according to one aspect of the present invention is an event management device that is communicatively connected to a user terminal, and is equipped with a management means capable of managing a user's status, a notification means capable of notifying a user of a message, and a control means capable of controlling the management means and the notification means, and the control means controls the notification so that a message according to the user's status can be notified.

[0008] An event management program according to one aspect of the present invention is an event management program for a computer that is communicatively connected to a user terminal, and causes the computer to function as a management means capable of managing the user's status, a notification means capable of notifying the user of a message, and a control means capable of controlling the management means and the notification means, and controls the control means so that a message corresponding to the user's status can be notified.

[0009] An event management system according to one aspect of the present invention includes an event management device and a user terminal.

[0010] According to the present invention, it is possible to provide an event management device, an event management program, and an event management system that can improve user convenience.

[0011] It is a diagram showing an example of an event management system 1 in an embodiment. It is a diagram showing an example of the hardware configuration of the event management device 10. It is a diagram showing an example of the hardware configuration of a user terminal 20. It is a diagram showing an example of the functional blocks of the event management device 10. It is a sequence diagram showing an example of processing in the event management system 1.

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An event management device, an event management program, and an event management system according to one aspect of the present invention will be described below with reference to the accompanying drawings.

[0013] <Event Management System 1 in an Embodiment> Fig. 1 is a diagram illustrating an example of an event management system 1 in an embodiment. The event management system 1 includes an event management device 10 and user terminals 20A, 20B, 20C, and so on. The event management device 10 and the user terminals 20A, 20B, 20C, and so on are capable of communicating with each other via a network 2. The network 2 is, for example, a WAN (Wide Area Network) such as the Internet.

[0014] The event management device 10 performs management processes for, for example, face-to-face events, such as accepting applications to participate, selecting participants by lottery, confirming participation at the event venue, and sending information messages. A face-to-face event is, for example, an event such as a competitive game using physical cards (physical cards made of resin or paper). The event management device 10 may be, for example, a physical server device or a virtual server.

[0015] <Hardware Configuration of Event Management Device 10> Fig. 2 is a diagram showing an example of the hardware configuration of the event management device 10. As shown in Fig. 1, the event management device 10 includes a processor 11, a memory 12, and a communication interface 13. The processor 11, the memory 12, and the communication interface 13 are connected by, for example, a bus 19.

[0016] The processor 11 is a circuit that performs signal processing, and is, for example, a central processing unit (CPU) that controls the entire event management device 10. The processor 11 may be realized by other digital circuits such as a field programmable gate array (FPGA) or a digital signal processor (DSP). The processor 11 may also be realized by combining multiple digital circuits.

[0017] The memory 12 includes, for example, a main memory and an auxiliary memory. The main memory is, for example, a RAM (Random Access Memory). The main memory is used as a work area for the processor 11.

[0018] The auxiliary memory is a non-volatile memory such as a magnetic disk, an optical disk, or a flash memory. The auxiliary memory stores various programs that operate the event management device 10. The programs stored in the auxiliary memory are loaded into the main memory and executed by the processor 11.

[0019] The auxiliary memory may also include a portable memory that is removable from the event management device 10. Portable memories include memory cards such as a USB (Universal Serial Bus) flash drive or an SD (Secure Digital) memory card, and external hard disk drives.

[0020] The communication interface 13 is a communication interface that performs communication with the outside of the event management device 10 (for example, the network 2). The communication interface 13 is controlled by the processor 11.

[0021] <Hardware configuration of user terminal 20> Fig. 3 is a diagram showing an example of the hardware configuration of the user terminal 20. Each of the user terminals 20A, 20B, 20C, ... shown in Fig. 1 is configured by, for example, the user terminal 20 shown in Fig. 3. For example, as shown in Fig. 2, the user terminal 20 includes a processor 21, a memory 22, a communication interface 23, and a user interface 24. The processor 21, the memory 22, the communication interface 23, and the user interface 24 are connected by, for example, a bus 29.

[0022] The processor 21 is a circuit that performs signal processing, and is, for example, a CPU that controls the entire user terminal 20. The processor 21 may be realized by other digital circuits such as an FPGA or a DSP. The processor 21 may also be realized by combining multiple digital circuits.

[0023] The memory 22 includes, for example, a main memory and an auxiliary memory. The main memory is, for example, a RAM. The main memory is used as a work area for the processor 21.

[0024] The auxiliary memory is a non-volatile memory such as a magnetic disk, an optical disk, or a flash memory. The auxiliary memory stores various programs that operate the user terminal 20. The programs stored in the auxiliary memory are loaded into the main memory and executed by the processor 21.

[0025] The auxiliary memory may also include a portable memory that is removable from the user terminal 20. Portable memory includes memory cards such as USB flash drives and SD memory cards, and external hard disk drives.

[0026] The communication interface 23 is a communication interface for communicating with the outside (for example, the network 2) of the user terminal 20. The communication interface 23 is controlled by the processor 21.

[0027] The user interface 24 includes, for example, an input device that accepts operation input from the user and an output device that outputs information to the user. The input device can be configured, for example, by keys (e.g., a keyboard) or a remote control. The output device can be configured, for example, by a display or a speaker. The input device and the output device may also be configured by a touch panel or the like. The user interface 24 is controlled by the processor 21.

[0028] <Functional Blocks of the Event Management Device 10> Fig. 4 is a diagram showing an example of functional blocks of the event management device 10. As shown in Fig. 4, the event management device 10 includes, for example, a control unit 111, a management unit 112, a notification unit 113, and a lottery unit 114. The control unit 111, the notification unit 113, and the lottery unit 114 are configured, for example, by the processor 11 shown in Fig. 2 executing a program. The management unit 112 is configured, for example, by the memory 12 (for example, a non-volatile memory) shown in Fig. 2.

[0029] The control unit 111 can control the management unit 112, the notification unit 113, and the lottery unit 114. The control unit 111 is an example of the control means of the present invention.

[0030] The management unit 112 can manage the status of users under the control of the control unit 111. The management unit 112 is an example of a management means of the present invention. A user is a user of the event management device 10, that is, a user who can participate in an event managed by the event management device 10, such as an owner of a user terminal 20A, 20B, 20C, ...

[0031] The notification unit 113 can notify the user of a message under the control of the control unit 111. The notification unit 113 is an example of a notification means of the present invention. The message is a notification message to the user that is sent to, for example, a user terminal (e.g., user terminals 20A, 20B, 20C, ...) owned by the user. For example, the message is an email, an SMS (Short Message Service) message, a chat message, an SNS (Social Networking Service) message, etc.

[0032] The lottery unit 114 is capable of executing an extraction process for selecting users who are permitted to participate in the event from among users who have applied for the event, under the control of the control unit 111. The lottery unit 114 is an example of a lottery means of the present invention.

[0033] <User Registration Table> The management unit 112 stores user registration tables 112A, 112B, ... that register users who have applied for each event (event A, event B, ...) managed by the event management device 10. Note that the user registration tables 112A, 112B, ... may be stored not only in the management unit 112 but also in a device external to the event management device 10 that is accessible by the management unit 112.

[0034] User registration table 112A is a table related to event A. In user registration table 112A, a status and a message destination are associated with each user whose application for event A has been accepted. A status is a user's state, which has multiple stages. A user's status is set to "applied" when the user is registered in user registration table 112A, i.e., when the user's application for event A is accepted. "Applied" is an example of the first stage of the present invention. A user's message destination is the destination of a message to that user. As an example, if the message is an email, the message destination is an email address.

[0035] User registration table 112B is a table relating to event B, which is different from event A. The data structure of user registration table 112B is similar to that of user registration table 112A.

[0036] <Processing in Event Management System 1> Figure 5 is a sequence diagram showing an example of processing in the event management system 1. In the event management system 1, for example, the processing shown in Figure 5 is executed for each event managed by the event management device 10. Here, the processing performed by the event management device 10 for Event A will be described. For Event A, an application period T1, a date and time for announcing the winning entries, and an event period T2 are determined in advance.

[0037] The application period T1 is a period for applications to participate in the event A. During the application period T1, the event management device 10 accepts participation requests from the user terminals 20A, 20B, 20C, . . .

[0038] In this example, first, user terminal 20A transmits a participation request to the event management device 10 based on an operation by user a who owns user terminal 20A (step S11). This participation request includes information indicating a desire to participate in event A, user a's identification information (such as user ID and name), and user a's message destination. Next, the event management device 10 registers user a based on the participation request from user terminal 20A (step S12). Specifically, the event management device 10 registers user a's identification information, user a's message destination, and the status "applied" in association with each other in the user registration table 112A.

[0039] Next, assume that user terminal 20B transmits a participation request to the event management device 10 based on an operation by user b who owns user terminal 20B (step S13). This participation request includes information indicating a desire to participate in event A, user b's identification information (user ID, name, etc.), and user b's message destination. Next, the event management device 10 registers user b based on the participation request from user terminal 20B (step S14). Specifically, the event management device 10 registers user b's identification information, user b's message destination, and the status "Applied" in association with each other in the user registration table 112A.

[0040] Next, assume that user terminal 20C transmits a participation request to the event management device 10 based on an operation by user c who owns user terminal 20C (step S15). This participation request includes information indicating a desire to participate in event A, user c's identification information (user ID, name, etc.), and user b's message destination. Next, the event management device 10 registers user c based on the participation request from user terminal 20C (step S16). Specifically, the event management device 10 registers user c's identification information, user c's message destination, and the status "Applied" in association with each other in the user registration table 112A.

[0041] In addition, the event management device 10 may transmit a message to the user terminals 20A, 20B, and 20C in steps S12, S14, and S16, respectively, to indicate that the registration has been accepted.

[0042] Next, six hours before the date and time when the winners of Event A are to be announced, the event management device 10 sends a first message to the message destinations of each user (in this example, users a, b, and c) who is registered in the user registration table 112A and whose status is "Applied" (step S17). Six hours before is an example of the "first hour before" in the present invention. The first message includes the date and time when the winners of Event A are to be announced.

[0043] In this example, user terminal 20A can receive a message addressed to a message destination corresponding to user a, user terminal 20B can receive a message addressed to a message destination corresponding to user b, and user terminal 20C can receive a message addressed to a message destination corresponding to user c. Therefore, the first message is received by user terminals 20A, 20B, and 20C, and the contents of the first message are notified to users a, b, and c by screen display or the like.

[0044] This allows users a, b, and c to know the date and time of the announcement of the winners of event A a certain time (six hours in this example) before the date and time of the announcement of the winners of event A. This prevents users a, b, and c from accessing the service-side system (e.g., event management device 10) to check the results of the announcement or the date and time of the announcement before the date and time of the announcement of the winners of event A, thereby preventing an increase in the load and network traffic on the service-side system.

[0045] Next, when the date and time for announcing the winners of Event A arrives, the event management device 10 conducts a lottery to select users who will be permitted to participate in Event A (step S18). For example, a maximum number of participants for Event A is predetermined, and the event management device 10 randomly selects a number of users not exceeding the maximum number of participants for Event A from among the users registered in the user registration table 112A and whose status is "Applied." In this example, it is assumed that, of User A, User B, and User C, User A and User B are selected (selected) as users permitted to participate in Event A. In this case, the event management device 10 changes the status of User A and User B in the user registration table 112A from "Applied" to "Permitted to participate." "Permitted to participate" is an example of the second stage of the present invention.

[0046] Next, the event management device 10 sends a second message to the message destination of each user (in this example, users a and c) who is registered in the user registration table 112A and whose status is "allowed to participate" (step S19). The second message includes information that the user is allowed to participate in event A (that is, has been selected). In this example, the second message is received by the user terminals 20A and 20C, and the contents of the second message are notified to users a and c by, for example, displaying them on their screens.

[0047] This allows users a and c to know that they have been permitted to participate (won) in event A. This prevents users a, b, and c from accessing the service-side system (e.g., the event management device 10) to check the results of the winning announcement, thereby preventing an increase in the load and network traffic on the service-side system.

[0048] Next, three hours before the start of event A, the event management device 10 sends a third message to the message destinations of each user (user a and user c in this example) who is registered in the user registration table 112A and whose status is "allowed to participate" (step S20). Three hours before is an example of the second time before in the present invention. The third message includes information indicating the date and time when event A will be held (e.g., event period T2). In this example, the third message is received by user terminals 20A and 20C, and the contents of the third message are notified to users a and c by screen display or the like.

[0049] This allows users a and c to check the date and time of event A a certain time (three hours in this example) before the date and time of event A. This prevents users a and c from accessing the service-side system (e.g., the event management device 10) to check the date and time of event A, thereby preventing an increase in the load and network traffic on the service-side system.

[0050] Furthermore, even if users a and c forget to hold event A, they can be reminded of the holding of event A a certain time (three hours in this example) before the date and time of event A. This reduces users' non-participation in event A due to forgetting to hold event A, improves the efficiency of event holding, and reduces the load and network traffic increase on the service-side system (e.g., the event management device 10).

[0051] During event A's holding period T2, the event management device 10 accepts participation procedures from each user registered in the user registration table 112A and with a status of "Participation Permitted." The participation procedure is performed, for example, by a user arriving at the venue of event A and performing an operation on an information terminal installed at the venue that can communicate with the event management device 10. In this example, it is assumed that of users a and c whose statuses are "Participation Permitted," only user a has completed the participation procedure during event A's holding period T2 (step S21). In this case, the event management device 10 registers a participation history indicating that user a participated in event A (step S22). Specifically, the event management device 10 changes user a's status in the user registration table 112A from "Participation Permitted" to "Participating."

[0052] Furthermore, when the event period T2 ends, the event management device 10 changes the status of users whose status in the user registration table 112A is "permitted to participate," i.e., users who were permitted to participate in event A but did not complete the participation procedure during the event period T2, from "permitted to participate" to "permitted not to participate." "Permitted not to participate" is an example of the third stage of the present invention. In this example, the event management device 10 changes the status of user c in the user registration table 112A from "permitted to participate" to "permitted not to participate."

[0053] Next, on the day after the event period T2, the event management device 10 sends a fourth message to the message destination of each user (in this example, user c) whose status is "Allowed but Not Participating" in the user registration table 112A (step S23). The fourth message includes a message calling attention to participation in future events. In this example, the fourth message is received by the user terminal 20C, and the content of the fourth message is notified to user c by, for example, displaying it on a screen.

[0054] This allows the user c to be alerted about participating in future events, which reduces the likelihood of users not participating due to forgetting to hold future events, improves the efficiency of event hosting, and reduces the load and network traffic on the service-side system (e.g., the event management device 10).

[0055] In this example, the fourth message is sent to user c, who was permitted to participate in event A but did not complete the participation procedure during event period T2, on the day after event period T2. However, the timing of sending the fourth message is not limited to the next day. For example, in addition to or instead of the day after event period T2, the event management device 10 may send the fourth message to user c the next time user c applies for another event (e.g., by requesting participation via user terminal 20C).

[0056] In this way, the event management device 10 is configured to manage the user status and send a message according to the user status. This improves user convenience by, for example, sending a predetermined reminder message at a predetermined time to users who have "applied" or "allowed to participate."

[0057] The event management device 10 can also manage the user status in multiple stages. For example, the event management device 10 manages the user status in multiple stages, such as "applied," "permitted to participate," and "permitted not to participate" (or "participating").

[0058] The event management device 10 also controls the user status so that it can be changed to one of multiple stages as time passes. For example, the event management device 10 sets the user status to "applied" during application period T1 for event A, holds a lottery on the date and time when the winners of event A are announced, and sets the status of users who win to "permitted to participate," sets the status of users who have completed the participation procedure to "participating" when event period T2 arrives, and sets the status of users whose status is "permitted to participate" to "permitted not to participate" after event period T2 has passed.

[0059] The event management device 10 also controls whether users can apply to participate in an event. For example, the event management device 10 accepts participation requests from user terminals 20A, 20B, and 20C during application period T1 for event A.

[0060] The event management device 10 also controls the user's status so that it can be changed for one event that the user has applied for. For example, the event management device 10 controls the user's status so that it can be changed for event A.

[0061] Furthermore, the event management device 10 controls the status of the same user for multiple events so that it can be changed for each event. For example, if the same user applies for event A, event B, ..., the event management device 10 manages the user's status for each of event A, event B, ....

[0062] Furthermore, the event management device 10 controls so that the first message can be notified to users whose status is at the first stage. For example, the event management device 10 notifies users whose status is "Applied" (the stage at which the user has applied to participate in the event) of the first message including the date and time of the announcement of the results of the selection (the time when it will be announced whether or not the user has been permitted to participate in the event).

[0063] The event management device 10 also controls so that a second message can be sent to a user whose status is at the second stage. For example, the event management device 10 sends a second message including information indicating that participation has been permitted to a user whose status is "Participation Permitted" (a stage in which the user is permitted to participate in the event).

[0064] Furthermore, the event management device 10 controls the number of second-stage users associated with one event to be fewer than the number of first-stage users. For example, the event management device 10 executes a lottery process to select second-stage users from among the first-stage users.

[0065] Furthermore, the event management device 10 controls the event management device 10 so that the first message can be notified one hour before the scheduled notification time of the second message. For example, the event management device 10 notifies the first message six hours before the scheduled notification time of the second message.

[0066] The event management device 10 also controls so that a third message can be sent to second-stage users two hours before the start time of the event. For example, the event management device 10 sends a third message including the date and time of the event to users whose status is "Participation Permitted" (a stage in which the user is permitted to participate in the event) three hours before the start time of the event.

[0067] Furthermore, the event management device 10 controls so that a fourth message can be notified to a user whose status is at the third stage. For example, the event management device 10 notifies a user whose status is "permitted not to participate" (a stage where participation in the event is permitted but the user does not participate in the event) of a fourth message including a warning about participating in future events.

[0068] For example, the event management device 10 notifies the fourth message at a predetermined time after the event period ends (for example, the day after the event). Also, the event management device 10 notifies the fourth message when applying for another event.

[0069] The event management method described in the above-described embodiment can be realized by executing a prepared event management program on a computer. The event management program is recorded on a computer-readable storage medium and executed by being read from the storage medium. The event management program may be provided in a form stored on a non-transitory storage medium such as a flash memory, or may be provided via a network such as the Internet. The computer that executes the event management program may be included in an event management device, or may be included in an electronic device such as a smartphone, tablet, or personal computer that can communicate with the event management device, or may be included in a server device that can communicate with these event management devices and electronic devices.

[0070] As described above, this specification describes the following:

[0071] (1) An event management device communicatively connected to a user terminal, comprising: a management means capable of managing a user's status; a notification means capable of notifying a user of a message; and a control means capable of controlling the management means and the notification means, wherein the control means controls the notification of the message according to the user's status.

[0072] (2) The event management device according to (1), wherein the management unit is capable of managing the status in a plurality of stages.

[0073] (3) The event management device according to (1) or (2), wherein the control means controls the status so that it can be changed to one of a plurality of stages as time passes.

[0074] (4) The event management device according to any one of (1) to (3), wherein the control means controls the event management device so that a user can apply to participate in the event.

[0075] (5) The event management device according to any one of (4), wherein the control means controls the status of one event for which application has been made so as to be changeable.

[0076] (6) The event management device according to (4) or (5), wherein the control means controls the status of a single user for a plurality of events so as to be changeable for each event.

[0077] (7) The event management device according to any one of (1) to (6), wherein the control means controls the event management device so that a first message can be notified to a user whose status is at the first stage.

[0078] (8) The event management device according to (7), wherein the first stage is a stage in which a user applies to participate in the event.

[0079] (9) The event management device according to (7) or (8), wherein the control means controls the event management device so that a second message can be notified to the user whose status is at the second stage.

[0080] (10) The event management device according to (9), wherein the control means controls the number of second-stage users associated with one event to be less than the number of first-stage users associated with one event.

[0081] (11) An event management device according to (9) or (10), further comprising a lottery means capable of executing a lottery process, wherein the control means is capable of controlling the lottery means, and the control means controls the event management device so that the second message can be notified to a user who has reached the second stage as a result of the execution of the lottery process.

[0082] (12) The event management device according to any one of (9) to (11), wherein the second stage is a stage in which the user is permitted to participate in the event.

[0083] (13) The event management device according to any one of (9) to (12), wherein the first message is a message regarding a time when permission to participate in the event will be announced.

[0084] (14) The event management device according to any one of (9) to (13), wherein the second message is a message indicating permission to participate in the event.

[0085] (15) The event management device according to any one of (9) to (14), wherein the control means controls the event management device so that the first message can be notified a first hour before the scheduled notification time of the second message.

[0086] (16) The event management device according to any one of (9) to (15), wherein the control means controls the event management device so as to be able to notify a third message to the second-stage user.

[0087] (17) The event management device according to (16), wherein the control means controls the event management device so that the third message can be notified two hours before the start time of the event.

[0088] (18) The event management device according to (16) or (17), wherein the third message is a message about the date and time of the event.

[0089] (19) The event management device according to any one of (1) to (18), wherein the control means controls the event management device so that a fourth message can be notified to the user whose status is at the third stage.

[0090] (20) The event management device according to (19), wherein the third stage is a stage in which the user is permitted to participate in the event but does not participate in the event.

[0091] (21) The event management device according to (19) or (20), wherein the control means controls the fourth message so that it can be notified when applying for another event.

[0092] (22) The event management device according to any one of (19) to (21), wherein the fourth message is a message calling for attention to participation in a future event.

[0093] (23) The event management device according to any one of (1) to (22), which manages an event for a competitive game using physical cards.

[0094] (24) An event management program for a computer communicatively connected to a user terminal, the event management program causing the computer to function as a management means capable of managing a user's status, a notification means capable of notifying a user of a message, and a control means capable of controlling the management means and the notification means, and causing the control means to control the message according to the user's status.

[0095] (25) An event management system including: the event management device according to any one of (1) to (23); and the user terminal.

[0096] REFERENCE SIGNS LIST 1 Event management system 2 Network 10 Event management device 11, 21 Processor 12, 22 Memory 13, 23 Communication interface 19, 29 Bus 20, 20A, 20B, 20C User terminal 24 User interface 111 Control unit 112 Management unit 112A, 112B User registration table 113 Notification unit 114 Lottery unit T1 Application period T2 Event period

Claims

1. An event management device that is communicatively connected to a user terminal, comprising: a management means capable of managing a user's status; a notification means capable of notifying a user of a message; and a control means capable of controlling the management means and the notification means, wherein the control means controls the notification of the message according to the user's status.

2. An event management device according to claim 1, wherein said management means is capable of managing said status in a plurality of stages.

3. An event management device according to claim 1, wherein said control means controls said status so that it can be changed to one of a plurality of stages as time passes.

4. An event management device according to claim 1, wherein the control means controls whether a user can apply to participate in an event.

5. An event management device according to claim 4, wherein said control means controls said status for one event to be applied for so as to be changeable.

6. An event management device according to claim 4, wherein the control means controls the status for a plurality of events so that the status can be changed for each event for the same user.

7. An event management device according to claim 1, wherein said control means controls so that a first message can be notified to a user whose status is at the first stage.

8. An event management device according to claim 7, wherein the first stage is a stage in which a user applies to participate in an event.

9. An event management device according to claim 7, wherein the control means controls the device so that a second message can be notified to the user whose status is at the second stage.

10. An event management device according to claim 9, wherein the control means controls so that the number of second-stage users associated with one event is less than the number of first-stage users associated with one event.

11. An event management device as described in claim 9, further comprising a lottery means capable of executing a lottery process, wherein the control means is capable of controlling the lottery means, and the control means controls the event management device so that the second message can be notified to users who have reached the second stage as a result of the execution of the lottery process.

12. An event management device according to claim 9, wherein the second stage is a stage in which the user is authorized to participate in the event.

13. An event management device according to claim 9, wherein the first message is a message regarding a time when permission to participate in the event will be announced.

14. An event management device according to claim 9, wherein the second message is a message indicating permission to participate in the event.

15. An event management device according to claim 9, wherein the control means controls the first message so that the first message can be notified a first hour before the scheduled notification time of the second message.

16. An event management device according to claim 9, wherein the control means controls the device so that a third message can be notified to the second-stage users.

17. An event management device according to claim 16, wherein the control means controls the third message so that it can be notified a second hour before the start time of the event.

18. An event management device according to claim 16, wherein the third message is a message about the date and time of the event.

19. An event management device according to claim 1, wherein the control means controls the device so that a fourth message can be notified to a user whose status is at the third stage.

20. An event management device according to claim 19, wherein the third stage is a stage in which the user is permitted to participate in the event but does not participate in the event.

21. An event management device according to claim 19, wherein the control means controls the fourth message so that it can be notified when applying for another event.

22. An event management device according to claim 19, wherein the fourth message is a message about caution regarding participation in a future event.

23. An event management device according to claim 1, which manages events relating to a competitive game using physical cards.

24. An event management program for a computer communicatively connected to a user terminal, the event management program causing the computer to function as: a management means capable of managing the user's status; a notification means capable of notifying the user of a message; and a control means capable of controlling the management means and the notification means; and causing the control means to control the notification of the message according to the user's status.

25. An event management system comprising: the event management device according to any one of claims 1 to 23; and the user terminal.

Images