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

Abstract

To improve convenience of a user.SOLUTION: The event management device 10 is communicably connected to user terminals 20A, 20B, 20C,. The event management apparatus 10 includes a management unit 112, a notification unit 113, and a control unit 111. The management unit 112 can manage the status of the user. The management unit 112 can notify the user of a message. The control unit 111 can control the management unit 112 and the management unit 112. The control unit 111 can notify a message corresponding to the status of the user.SELECTED DRAWING: Figure 5

Description

[Technical Field]

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

[0002] BACKGROUND ART Conventionally, with regard to technology for transmitting and receiving messages using information processing terminals, a communication method for sending messages from members of a chat service to non-members has been proposed (for example, 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. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-006870 Summary of the Invention [Problem to be solved by the invention]

[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. [Means for solving the problem]

[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. [Effects of the Invention]

[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. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating an example of an event management system 1 according to an embodiment. [Figure 2] 1 is a diagram illustrating an example of a hardware configuration of an event management device 10. FIG. [Figure 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of a user terminal 20. [Figure 4] FIG. 2 is a diagram illustrating an example of functional blocks of the event management device 10. [Figure 5] 3 is a sequence diagram showing an example of processing in the event management system 1. FIG. DETAILED DESCRIPTION OF THE INVENTION

[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 the Embodiment> 1 is a diagram illustrating an example of an event management system 1 according to an embodiment. The event management system 1 includes an event management device 10 and user terminals 20A, 20B, 20C, etc. The event management device 10 and the user terminals 20A, 20B, 20C, etc. can communicate with each other via a network 2. The network 2 is, for example, a wide area network (WAN) 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, drawing lots for participants, 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 illustrating an example of the hardware configuration of the event management device 10. The event management device 10 illustrated in Fig. 1 includes, for example, 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 CPU (Central Processing Unit) that controls the entire event management device 10. The processor 11 may be realized by other digital circuits such as an FPGA (Field Programmable Gate Array) or a DSP (Digital Signal Processor). The processor 11 may also be realized by combining a plurality of digital circuits.

[0017] The memory 12 includes, for example, a main memory and an auxiliary memory. The main memory is, for example, a random access memory (RAM). 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 an external hard disk drive.

[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 memories include 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 the 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 can execute an extraction process to select 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, ... in which users who have applied for each event (event A, event B, ...) managed by the event management device 10 are registered. 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 the management unit 112 can access.

[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, that is, 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 the same as that of user registration table 112A.

[0036] <Processing in Event Management System 1> Fig. 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 Fig. 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 applying 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 (user ID, name, etc.), 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 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, identification information (user ID, name, etc.) of user c, and a message destination of user b. 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 the identification information of user c, the message destination of user c, and the status "Applied" in association with each other in the user registration table 112A.

[0041] 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 will be announced, the event management device 10 sends a first message to the message destination of each user (in this example, user a, user b, and user 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 will 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 (for example, event management device 10) to check the results of the announcement or the date and time of the announcement of the winners of event A before the date and time of the announcement, 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 determined in advance, and the event management device 10 randomly selects users whose status is "applied" in the user registration table 112A so that the number of users does not exceed the maximum number of participants for event A. In this example, it is assumed that, of users a, b, and c, users a and b are selected (selected) as users who will be permitted to participate in event A. In this case, the event management device 10 changes the status of users a and 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 transmits a second message to the message destination of each user (user a and user c in this example) who is registered in the user registration table 112A and whose status is "permitted to participate" (step S19). The second message includes information that the user is permitted to participate in event A (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 user a and user c by displaying the contents on their screens, etc.

[0047] This allows users a and c to know that they have been permitted to participate in (won) event A. This prevents users a, b, and c from accessing the service-side system (for example, the event management device 10) to check the results of the announcement of the winning entries, 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 destination 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 hour before in the present invention. The third message includes information indicating the date and time when event A will be held (for example, holding 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 (for example, the event management device 10) to check the date and time of event A, thereby suppressing an increase in the load and network traffic on the service-side system.

[0050] Furthermore, even if user a and user 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 (for example, the event management device 10).

[0051] During the event A holding period T2, the event management device 10 accepts participation procedures from each user who is registered in the user registration table 112A and whose status is "permitted to participate." The participation procedure is performed, for example, by a user who arrives at the venue of event A and performs 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 status is "permitted to participate," only user a has performed participation procedures during the event 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 the status of user a in the user registration table 112A from "permitted to participate" 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 transmits a fourth message to the message destination of each user (user c in this example) whose status is "permitted not to participate" 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 in future events due to forgetting to hold the events, improves the efficiency of event holding, and reduces the load on the service-side system (e.g., the event management device 10) and the increase in network traffic.

[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 (for example, by requesting participation via user terminal 20C).

[0056] In this way, the event management device 10 is configured to manage the user status and notify messages 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] Furthermore, the event management device 10 controls the user status so that it can be changed to one of a plurality of 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 to announce the winners of event A and sets the status of the users who win to "permitted to participate" when the event period T2 arrives and sets the status of the users who have completed the participation procedure to "participating," and after the event period T2 has passed, sets the status of the users whose status is "permitted to participate" to "permitted not to participate."

[0059] Furthermore, the event management device 10 controls so that 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] Furthermore, the event management device 10 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 a plurality of events so that the status of the same user can be changed for each event. For example, if the same user applies for each of 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 as to be able to notify a first message to a user whose status is at the first stage. For example, the event management device 10 notifies a user whose status is "Applied" (the stage at which the user has applied to participate in the event) of a 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] Furthermore, the event management device 10 controls so that a second message can be notified to a user whose status is at the second stage. For example, the event management device 10 notifies a user whose status is "participation permitted" (a stage where the user is permitted to participate in the event) of a second message including information indicating that participation has been permitted.

[0064] Furthermore, the event management device 10 controls so that the number of second-stage users associated with one event is smaller 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 first message so that it 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] Furthermore, the event management device 10 controls so that a third message can be notified to second-stage users two hours before the start time of the event. For example, the event management device 10 notifies users whose status is "Participation Permitted" (a stage where users are permitted to participate in the event) of a third message including the date and time of the event three hours before the start time of the event.

[0067] Furthermore, the event management device 10 controls so as to be able to notify a fourth message to a user whose status is at the third stage. For example, the event management device 10 notifies a user whose status is "permitted non-participation" (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 participation in future events.

[0068] For example, the event management device 10 notifies the fourth message at a predetermined time after the end of the event period (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 communicably connected to a user terminal, a management means for managing the status of a user; a notification means capable of notifying a user of a message; a control means capable of controlling the management means and the notification means, the control means controls so that the message corresponding to the user's status can be notified; Event management device.

[0072] (2) The event management device according to (1), The management means is capable of managing the status in multiple stages. Event management device.

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

[0074] (4) An event management device according to any one of (1) to (3), The control means controls whether a user can apply to participate in an event. Event management device.

[0075] (5) (4) An event management device according to any one of (1) to (3), the control means controls the status of one event to be applied for so as to be changeable; Event management device.

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

[0077] (7) An event management device according to any one of (1) to (6), the control means controls so as to notify a first message to the user whose status is at the first stage; Event management device.

[0078] (8) (7) An event management device according to the present invention, The first stage is when the user applies to participate in the event. Event management device.

[0079] (9) The event management device according to (7) or (8), the control means controls so as to notify a second message to the user whose status is at the second stage; Event management device.

[0080] (10) (9) An event management device according to the present invention, The control means performs control so that the number of second-stage users associated with one event is smaller than the number of first-stage users associated with one event. Event management device.

[0081] (11) The event management device according to (9) or (10), further comprising lottery means capable of executing lottery processing; the control means is capable of controlling the lottery means, the control means controls so as to notify the second message to users who have reached the second stage as a result of the execution of the lottery process; Event management device.

[0082] (12) An event management device according to any one of (9) to (11), The second stage is when the user is authorized to participate in the event. Event management device.

[0083] (13) An event management device according to any one of (9) to (12), The first message is a message about the announcement time of whether or not you are permitted to participate in the event. Event management device.

[0084] (14) An event management device according to any one of (9) to (13), The second message above is a message that allows you to participate in the event. Event management device.

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

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

[0087] (17) (16) An event management device according to (16), the control means controls the third message so as to be notifiable two hours before the start time of the event; Event management device.

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

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

[0090] (20) The event management device according to (19), The third stage is when the user is allowed to participate in the event but does not actually participate in the event. Event management device.

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

[0092] (twenty two) An event management device according to any one of (19) to (21), The fourth message above is a message about caution when participating in future events. Event management device.

[0093] (twenty three) An event management device according to any one of (1) to (22), Manage events for physical card-based competitive games; Event management device.

[0094] (twenty four) An event management program for a computer communicably connected to a user terminal, Management means for managing the status of users; notification means for notifying a user of a message; a control means capable of controlling the management means and the notification means; and causing the computer to function as causing the control means to perform control so as to notify the message corresponding to the status of the user; Event management program.

[0095] (twenty five) An event management device according to any one of (1) to (23); The user terminal; Event management system including: [Explanation of symbols]

[0096] 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 Department 112A, 112B User registration table 113 Notification Department 114 Lottery Section T1 Application Period T2 Event Period

Claims

1. An event management device communicably connected to a user terminal, a management means for managing the status of a user; a notification means capable of notifying a user of a message; a control unit capable of controlling the management unit and the notification unit, the control means controls the notification of the message according to the user's status; Event management device.

2. The event management device according to claim 1, The management means is capable of managing the status in a plurality of stages. Event management device.

3. The event management device according to claim 1, the control means controls the status so as to be changeable to one of a plurality of stages as time passes. Event management device.

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

5. The event management device according to claim 4, the control means controls the status of one event to be applied for so as to be changeable; Event management device.

6. The event management device according to claim 4, the control means controls the status of the same user to be changeable for each of a plurality of events; Event management device.

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

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

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

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

11. The event management device according to claim 9, further comprising lottery means capable of executing lottery processing; the control means is capable of controlling the lottery means, the control means controls the user to be placed in the second stage by the execution of the lottery process so as to be able to notify the second message. Event management device.

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

13. The event management device according to claim 9, the first message is a message about a time when permission to participate in the event will be announced; Event management device.

14. The event management device according to claim 9, the second message is a message indicating permission to participate in the event; Event management device.

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

16. The event management device according to claim 9, the control means controls the device so that a third message can be notified to the second-stage user; Event management device.

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

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

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

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

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

22. 20. The event management device according to claim 19, The fourth message is a message about caution regarding participation in future events. Event management device.

23. The event management device according to claim 1, Manage events for physical card-based competitive games; Event management device.

24. An event management program for a computer communicably connected to a user terminal, Management means for managing the status of users; notification means for notifying a user of a message; a control means capable of controlling the management means and the notification means; causing the computer to function as causing the control means to perform control so as to notify the message according to the user's status; Event management program.

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

Images