JP2021043610A - Event management system - Google Patents

Abstract

To provide an event management system capable of easily applying for participation in a desired event while a member grasps the existence of an event scheduled to be held in real time.SOLUTION: An event management system 1 includes a user information database 11, an event information database 12, a management server 10, and a plurality of user terminals 20 (20A, 20B, 20C, ...). In the event information database 12, the category, scheduled date, maximum number of people, number of applicants, and registered user identification information of each event are registered as event information. The user terminal 20 displays a calendar screen on which an icon indicating event holding is arranged on the scheduled date of the event, and transmits, if an application for the event is accepted, the application request for the event and the user identification information to the management server 10. The management server 10 updates the number of applicants for the event and adds the user identification information to the applied user identification information.SELECTED DRAWING: Figure 1

Description

The present invention relates to an event management system for an event operator to manage a plurality of events.

Conventionally, various techniques for managing schedules have been proposed. For example, in the schedule management system described in Patent Document 1, for each schedule data to be managed, the arrival of the notification timing of the event specified by the schedule data is monitored, and the participation availability status of each prospective event participant is shown. It is described that the participation availability management data is disclosed and the extension telephone assigned to each prospective participant of the event whose notification timing has arrived is notified of the event. In addition, the availability of participation in the event is acquired from these extension telephones via the main unit, and the participation availability management data indicating the participation availability status of each prospective participant of this event is updated based on the acquired participation availability. Etc. are also described.

Japanese Patent No. 6361774

By the way, it is an urgent issue for event operators who plan and manage events to improve the participation rate of the events to be held. On the other hand, the inventor of the present application considered that it is preferable that the member can easily apply for participation in a desired event while grasping the existence of the event to be held in real time.

However, among the conventional schedule management methods including the above-mentioned Patent Document 1, there is no technique that allows members to easily apply for participation in a desired event while grasping the existence of an event scheduled to be held in real time. ..

Therefore, an object of the present invention is to provide an event management system that allows a member to easily apply for participation in a desired event while grasping the existence of an event scheduled to be held in real time.

In order to achieve the above object, the present invention is an event management system for managing a plurality of events for which categories are set, an event information database capable of registering event information related to the plurality of events, and the event. The event information database includes a management server configured to be able to access the information database and a plurality of user terminals configured to be able to communicate with the management server via a network, and the event information database is a category of each event. The scheduled date, the maximum number of people, the number of applicants, and the applied user identification information can be registered as the event information. The event management application is installed on each of the plurality of user terminals, and the plurality of users. One of the terminals, the user terminal, executes the event management application, displays a selection screen for selecting a desired category, and when a specific category is selected from the selection screen, the specific category is set. The management server requests the event information of at least one event, and the management server acquires the event information of the at least one event from the event information database and transmits the event information to the one user terminal. Based on the at least one event information, the user terminal of the user terminal displays a calendar screen on which an icon indicating event holding is arranged on the scheduled date of the at least one event, and the at least one event via the calendar screen. When an application for one event is accepted from among the above, the application request for the one event and the user identification information are transmitted to the management server, and the management server sends the application request for the one event and the user identification information to the management server. In response to the application request for the event, the number of applicants for the one event in the event information database is updated, and the user identification information is added to the applied user identification information for the one event in the event information database. It provides an event management system featuring the addition of.

Here, it is preferable that the management server notifies by push notification that a new event is added to each of the plurality of user terminals when the event information regarding the new event is registered in the event information database.

Further, a user information database capable of registering user information regarding a plurality of users who use the event management application is further provided, and the user information database can register user identification information, gender, and age of each user as the user information. The event information database is configured, and the gender designation and age limit of each event can be further registered as the event information, and the management server applies to the one event received from the one user terminal. In response to the request, the gender and age of the record including the user identification information received from the one user terminal is acquired from the user information database, and the gender designation and age restriction of the one event in the event information database are obtained. It is determined whether or not the gender and age of the record satisfy both the gender designation and the age limit of the one event, and the gender and age of the record are the gender designation and age limit of the one event. On condition that it is determined that both conditions are satisfied, the number of applicants for the one event in the event information database is updated, and the applied user identification information of the one event in the event information database is added. It is preferable to add user identification information.

Further, the management server transmits an application permission notification to the one user terminal on condition that the gender and age of the record satisfy both the gender designation and the age limit of the one event. , The user terminal preferably displays an application completion screen in response to the application permission notification.

Further, when the gender and age of the one record do not satisfy the conditions of the gender designation or the age limit of the one event, the management server sends a non-application notification to the one user terminal, and the user. It is preferable that the terminal displays the application non-application screen in response to the application non-application notification.

According to the present invention, a calendar screen on which an icon indicating event holding is arranged is displayed on the scheduled date of at least one event, and an application for one event is accepted via the calendar screen. Therefore, it is possible for a member to easily apply for participation in a desired event while grasping the existence of the event scheduled to be held in real time.

The figure which shows the schematic structure of the event management system which concerns on embodiment. The figure which shows the user information database. The figure which shows the event information database. A sequence diagram showing the interaction between the user terminal and the management server. The figure which shows the home screen of an event management application. The figure which shows the display form of a pull-down menu. The figure which shows the event list screen of an event management application. The figure which shows the detail screen of an event. The figure which shows the application completion screen of an event. The figure which shows the event application impossible screen.

<1. Embodiment>
Hereinafter, the event management system according to the embodiment of the present invention will be described in detail with reference to FIGS. 1 to 10. Specifically, as an example of the event management system of the present invention, the event management system 1 shown in FIG. 1 will be described as an example.

As shown in FIG. 1, the event management system 1 includes a management server 10, a user information database 11, an event information database 12, and a plurality of user terminals 20 (20A, 20B, 20C, ...). To.

The management server 10 is connected to the user information database 11 and the event information database 12, respectively, and can access both of them.

The management server 10 has a hardware configuration similar to that of a known server device. Specifically, the management server 10 includes a processor, a RAM (Random Access Memory) that functions as a work area of the processor, and a ROM (Read Only Memory) that stores control programs and data executed by the processor.

The management server 10 is also provided with a network interface, a monitor, an input device, an auxiliary storage device, and the like.

Each function of the management server 10 is realized by a program executed in the above-mentioned hardware and processor.

Each user terminal 20 (20A, 20B, 20C, ...) Is connected to the management server 10 via the communication network NW, and can perform network communication with the management server 10.

The management server 10 is wiredly connected to the communication network NW via a LAN cable. On the other hand, each user terminal 20 is wirelessly connected to the communication network NW by Wi-Fi (registered trademark).

Each user terminal 20 has the same hardware configuration as a known smartphone or the like. The user terminal 20 includes a processor, a RAM that functions as a work area of the processor, and a ROM that stores a control program and data executed by the processor.

Further, the user terminal 20 is also provided with a display device that displays various information to the user, a touch panel that functions as an input device operated by the user, and an auxiliary storage device that stores various information and data.

Further, the event management application AP that operates on the OS (Operating System) is installed in the user terminal 20. The event management application AP is an application provided to members by an event operator who plans and manages various events. The event management application AP is used to browse various events to be held and to apply for participation in a desired event.

Prior to using the event management application AP, each member needs to perform user registration (member registration) via a user registration screen (not shown) when the event management application AP is started for the first time. The member information (user information) entered on the user registration screen is transmitted from the user terminal 20 to the management server 10. The management server 10 registers the user information received from the user terminal 20 in the user information database 11 (see FIG. 2) as new user information.

As shown in FIG. 2, the user information of each member is recorded in the user information database 11 as records RC11, RC12, .... As the fields (input items) of each record, "user ID", "gender", "age" and "name" are prepared. As described above, a record of user information regarding a new user is added to the user information database 11 each time a user is registered in the user terminal 20.

Information about the event (event information) managed by the event operator is registered in the event information database 12 by the management server 10.

As shown in FIG. 3, the event information database 12 is designed to record a record for each event. In the event information database 12, "event ID", "category", "scheduled date", "maximum number of people", "number of applicants", "gender designation", "age limit" and "Applied user ID" is prepared. Every time a new event occurs, a record of event information related to the new event is added to the event information database 12.

In this embodiment, information about an event planned and operated by the event business operator is recorded in the event information database 12.

Subsequently, the interaction between the management server 10 and the specific user terminal 20 will be described with reference to the sequence diagram of FIG.

When an icon (not shown) corresponding to the event management application AP is selected via the touch panel of the user terminal 20, the user terminal 20 activates the event management application AP (step S1). Along with this, the user terminal 20 displays the home screen GA1 (see FIG. 5) on the touch panel (step S2).

As shown in FIG. 5, the home screen GA1 includes a pull-down menu PD and a calendar CA arranged below the pull-down menu PD.

The pull-down menu PD is for letting the user select a desired event category, and is an example of the selection screen according to the present invention. When the pull-down menu PD is operated by the user, the pre-registered event categories are listed from top to bottom, as shown in FIG.

As shown in FIG. 5, the calendar CA is a monthly calendar starting on Sunday, and is an example of a calendar screen according to the present invention. When the home screen is started (initial state), it is set as standard so that this month's calendar is displayed. In the calendar CA, the grayed out part (June 10, 2019) corresponds to today. Further, at the lower part of the calendar CA, a switching key for switching the calendar display to the previous month (May) or the next month (July) is provided.

When a specific category (for example, "marriage activity event") is selected from the listed event categories, the user terminal 20 requests the management server 10 for event information of the event in which the specific category is set (step S3). ).

On the other hand, the management server 10 accesses the event information database 12, extracts all the records matching the specific category, and acquires all the extracted records as the event information of the event in which the specific category is set (). Step S4).

For example, when the specific category is "marriage activity event", the management server 10 extracts all the records in which "marriage activity" is entered in the field "category". Similarly, when the specific category is "grass baseball event", the management server 10 extracts all the records in which "grass baseball" is input in the field "category".

Then, the management server 10 transmits the event information (information of all the extracted records) acquired in step S4 to the user terminal 20 (step S5). For example, when the specific category is "marriage activity event", the management server 10 transmits the information of the records RC22 and RC24 to the user terminal 20.

The user terminal 20 specifies the scheduled date of an event in a specific category (for example, "marriage activity event") based on the event information received from the management server 10. Here, the user terminal 20 specifies June 22, 2019 and June 30, 2019 as the scheduled dates of the "marriage activity event" from the information of the records RC22 and RC24.

Then, as shown in FIG. 7, the user terminal 20 touches the event list screen GA2 including the calendar CA in which the heart icon is arranged on the scheduled event dates (June 22, 2019 and June 30, 2019). Display on. Here, the heart icon is an icon indicating the holding of an event of the "marriage activity event", and is an example of the "icon indicating the holding of the event" according to the present invention. In the event list screen GA2, a specific category (here, "marriage activity event") selected by the user is displayed in the pull-down menu PD.

As shown in FIG. 7, it is assumed that, for example, the icon of June 22, 2019 is selected in the calendar CA of the event list screen GA2. In that case, as shown in FIG. 8, the user terminal 20 details the event to be held on June 22, 2019, based on the event information (specifically, the information of the record RC22) received from the management server 10. The screen GA3 is popped up on the touch panel.

On the detail screen GA3, the date and time, place, age limit, maximum number of participants and current number of applicants for the marriage event are displayed based on the event information received from the management server 10, and an application button is displayed to apply for participation. It is displayed.

When the application button on the detail screen GA3 is pressed, the user terminal 20 transmits an application request and a user ID for the event scheduled to be held on June 22, 2019 to the management server 10 (step S7).

The management server 10 responds to the application request from the user terminal 20 and executes a process of determining whether or not to apply for the event (step S8).

Specifically, the management server 10 acquires the gender and age of the record including the user ID received from the user terminal 20 from the user information database 11. For example, when the user ID is "0005", the management server 10 acquires the gender (female) and age (38) of the record RC15 (see FIG. 2) from the user information database 11.

Next, the management server 10 refers to the gender designation and age restriction of the record RC22 (see FIG. 3) corresponding to the event for which the application request is accepted (the marriage activity event to be held on June 22, 2019). Then, the management server 10 determines whether or not the gender and age of the record RC15 shown in FIG. 2 satisfy both the gender designation and the age limit of the record RC22 shown in FIG. In this example, as shown in record RC22 of FIG. 3, there is no gender designation and the age limit is less than 20 years. Therefore, the management server 10 determines that the gender (female) and age (38) of the record RC15 shown in FIG. 2 satisfy both the gender designation and the age limit of the record RC22 shown in FIG. Then, the management server 10 updates the number of applicants for the record RC22 from "8" to "9", and newly adds the user ID "0005" to the applied user ID.

After that, the management server 10 transmits an application completion notification to the user terminal 20 notifying that the application for the event has been completed (step S9). When the user terminal 20 receives the application completion notification from the management server 10, as shown in FIG. 9, the user terminal 20 displays on the touch panel the application completion screen GA4 stating that the application for the event has been completed under the calendar CA (step). S10).

On the application completion screen GA4, the icon displayed on the scheduled date of the event for which the application is completed in the calendar CA is changed from white to black. As a result, the user can easily grasp that he / she is planning to participate in the marriage event held on June 22, 2019.

On the other hand, when the user with the user ID "0003" shown in FIG. 2 applies for the marriage hunting event to be held on June 22, 2019, the age of the user (15 years old) is the age of the marriage hunting event. Does not meet the limit (under 20 years old).

In this case, instead of step S9 described above, the management server 10 transmits a notification that the application cannot be made to the user terminal 20 to the effect that the application for the event cannot be made (step S11). When the user terminal 20 receives the application prohibition notification from the management server 10, as shown in FIG. 10, the user terminal 20 displays the application prohibition screen GA5 including the pop-up screen 51 describing the reason why the application cannot be made (step S12).

According to the above-described embodiment, when a specific category is selected via the pull-down menu PD (see FIGS. 5 and 6), a calendar CA in which an icon indicating the event is held on the scheduled date of the event of the specific category is arranged. Is displayed (see FIG. 7). Then, the application for one event is accepted via the calendar CA. Therefore, it is possible for a member to easily apply for participation in a desired event while grasping the existence of the event scheduled to be held in real time.

Further, according to the above-described embodiment, the application is completed on condition that the gender and age of the event applicant satisfy both the gender designation and the age limit set for the event. .. Conversely, if the gender and age of the event applicant do not meet the gender designation or age limit set for the event, the application cannot be made. Therefore, it is possible to distinguish the participants of the event in advance and gather the participants suitable for the event to be held.

<2. Modification example>
The event management system according to the present invention is not limited to the above-described embodiment, and various modifications and improvements can be made within the scope of claims.

For example, in the above-described embodiment, the case where the information about the event planned and operated by the event business operator is recorded in the event information database 12 is illustrated, but the present invention is not limited to this. Information about an event planned by a business operator other than the event business operator may be recorded in the event information database 12.

Specifically, the information on the advertising event planned and operated by the consumer electronics mass retailer chain may be recorded, or the information on the day labor business recruited by the day laborer may be recorded. This makes it possible to apply for more events (advertising events and day laborers) via the event management application AP.

Further, in the above-described embodiment, the case where the monthly calendar starting on Sunday is displayed as the calendar CA is illustrated, but the present invention is not limited to this, and the weekly calendar may be displayed. In that case, since it is possible to secure a larger space for each day than the monthly calendar, not only the icon but also the details of the event may be displayed.

Further, in the above-described embodiment, the case where the event management application AP is activated in response to the touch operation of the icon has been illustrated, but the present invention is not limited to this. The event management application AP may be started by the touch operation of the message screen accompanying the push notification.

Here, the push notification may be notified to the user terminals 20 (20A, 20B, 20C, ...) Of each member by the management server 10. Specifically, the management server 10 sends a new event to the user terminals 20 (20A, 20B, 20C, ...) Of each member by push notification at the timing when the new event information is registered in the event information database 12. It should be notified.

As described above, the event management system according to the present invention is suitable for managing the event schedule.

1 Event management system 10 Management server 11 User information database 12 Event information database 20 User terminal AP Event management application CA Calendar GA1 Home screen GA2 Event list screen GA3 Detailed screen GA4 Application completion screen GA5 Application not possible screen NW communication network PD pull-down menu

Claims (5)

An event management system for managing multiple events with categories set.
An event information database that can register event information related to the plurality of events, and
A management server configured to access the event information database,
A plurality of user terminals configured to be able to communicate with the management server via a network,
With
The event information database is configured so that the category, scheduled date, maximum number of people, number of applicants, and registered user identification information of each event can be registered as the event information.
An event management application is installed on each of the plurality of user terminals.
One of the plurality of user terminals executes the event management application, and the user terminal executes the event management application.
Display the selection screen for selecting the desired category,
When a specific category is selected from the selection screen, the management server is requested to provide event information for at least one event in which the specific category is set.
The management server acquires event information of the at least one event from the event information database and transmits it to the one user terminal.
The one user terminal is
Based on the at least one event information, a calendar screen on which an icon indicating the event holding is arranged on the scheduled date of the at least one event is displayed.
When an application for one event from the at least one event is accepted via the calendar screen, an application request for the one event and user identification information are transmitted to the management server.
The management server updates the number of applicants for the one event in the event information database in response to the application request for the one event from the one user terminal, and at the same time, the management server updates the number of applicants for the one event in the event information database. An event management system characterized by adding the user identification information to the applied user identification information of one event. The management server is characterized in that when event information related to a new event is registered in the event information database, the management server notifies by push notification that a new event is added to each of the plurality of user terminals. The event management system according to 1. Further provided with a user information database capable of registering user information regarding a plurality of users who use the event management application.
The user information database is configured so that user identification information, gender, and age of each user can be registered as the user information.
In the event information database, the gender designation and age limit of each event can be further registered as the event information.
The management server
In response to the application request for the one event received from the one user terminal, the gender and age of the record including the user identification information received from the one user terminal are acquired from the user information database.
With reference to the gender designation and age limit of the one event in the event information database, it is determined whether or not the gender and age of the record satisfy both the gender designation and age limit of the one event.
On condition that it is determined that the gender and age of the record satisfy both the gender designation and the age limit of the event, the number of applicants for the event in the event information database is updated and the number of applicants for the event is updated. The event management system according to claim 1 or 2, wherein the user identification information is added to the applied user identification information of the one event in the event information database. The management server sends an application permission notification to the one user terminal on condition that the gender and age of the record satisfy both the gender designation and the age limit of the one event.
The event management system according to claim 3, wherein the user terminal displays an application completion screen in response to the application permission notification. If the gender and age of the one record do not meet the conditions of gender designation or age restriction of the one event, the management server sends a non-application notification to the one user terminal.
The event management system according to claim 3, wherein the user terminal displays a non-application screen in response to the non-application notification.

Images