JP6870047B2 - Calendar management system, calendar management method and calendar management program - Google Patents

Description

The present invention relates to a calendar management system, a calendar management method, and a calendar management program that manages calendars of events related to various games.

Today, contents such as various online games are provided to users who use computer terminals such as smartphones. For such an online game, a technique for a player to select a favorite team, participate with other fans of the team, and compete with a player of the opponent team is also being studied (see, for example, Patent Document 1). .. Here, teams compete with each other in a match based on the schedule of an actual event, such as a sports schedule or entertainment schedule. Players play in groups with other players associated with their favorite team.

Further, a technique for motivating a player to evenly select various game elements such as items is also being studied (see, for example, Patent Document 2). The game system described in this document stores a virtual space generator that generates a virtual game space, a character motion control unit that controls the motion of a player character in the virtual game space, and special performances unique to each game element. Equipped with a special performance storage unit. Further, a schedule management unit for managing the period during which the special performance is effective is provided for each game element, and the special performance is enabled for the game element selected by the player based on the schedule.

Special Table 2003-528397 Japanese Unexamined Patent Publication No. 2013-176472

However, many games are offered and various events are planned for each game. Sometimes we overlook such an event. In addition, each event has a fixed schedule, and even if you know the event, if you forget the schedule, you will miss the opportunity to participate in the event.

The present invention has been made in view of the above-mentioned problems, and an object of the present invention is a calendar management method, a calendar management server, and a calendar management program for suppressing forgetting to schedule an event and accurately supporting participation in an event. Is to provide.

The calendar management system that solves the above problems is a notification that does not notify each user about the game used by the user, the game to be registered as a calendar in the game used, and the game to be calendared. A user information storage unit that stores conditions, a calendar storage unit that stores the calendar of the event schedule of the game to be registered for each user, a specific unit that identifies the user of the user terminal by login processing, and the user information. When the calendar registration target game of the specified user is stored in the storage unit, the display control unit for displaying the screen including the event schedule for the calendar registration target game including the event period on the user terminal, and the calendar registration. When the registration of a new event is detected for the target game, the calendar associated with the user is displayed.
The event registration unit that registers the event and the notification method determines whether or not the notification condition is satisfied when the notification time has arrived for the registered event, and notifies if the event satisfies the notification condition. Is provided, and a notification control unit that does not notify when the event does not satisfy the notification condition is provided.
In the calendar management method for solving the above problem, the control unit does not notify each user about the game used by the user, the game to be registered as a calendar in the game used, and the game to be calendared. Using the user information storage unit that stores the notification condition, which is a condition, and the calendar storage unit that stores the calendar of the event schedule of the game to be registered for each user, the user of the user terminal is specified by the login process. A step and a step of displaying a screen including an event schedule for the calendar registration target game including an event period on the user terminal when the calendar registration target game of the specified user is stored in the user information storage unit. When the registration of a new event is detected for the game to be registered in the calendar, the step of registering the event and the notification method in the calendar associated with the user and the notification time of the registered event are set. When it arrives, it is determined whether or not the notification condition is satisfied, a notification is given if the event satisfies the notification condition, and no notification is given if the event does not satisfy the notification condition. To execute.
The calendar management program that solves the above problem does not notify the control unit of the game used by the user, the game to be registered as a calendar in the game used, and the game to be calendared for each user. Using the user information storage unit that stores the notification condition, which is a condition, and the calendar storage unit that stores the calendar of the event schedule of the game to be registered for each user, the user of the user terminal is specified by the login process. A step and a step of displaying a screen including an event schedule for the calendar registration target game including an event period on the user terminal when the calendar registration target game of the specified user is stored in the user information storage unit. When the registration of a new event is detected for the game to be registered in the calendar, the step of registering the event and the notification method in the calendar associated with the user and the notification time of the registered event are set. When it arrives, it is determined whether or not the notification condition is satisfied, a notification is given if the event satisfies the notification condition, and no notification is given if the event does not satisfy the notification condition. To execute.

According to the present invention, it is possible to suppress forgetting to schedule an event and accurately support participation in the event.

The system schematic diagram of this embodiment. The explanatory view of the processing procedure of this embodiment. The explanatory view of the processing procedure of this embodiment. The explanatory view of the processing procedure of this embodiment. The explanatory view of the processing procedure of this embodiment. It is explanatory drawing of the screen example of this embodiment, (a) is an event screen when there is no calendar registration, (b) is an application setting screen, (c) is an event screen when there is calendar registration, (d). Is an explanatory diagram of the calendar registration screen. It is explanatory drawing of the processing procedure of another embodiment, (a) is the notification process which changes a normal method according to a situation, (b) is the description of the notification process which determines the necessity of the notification according to the notification condition. Figure. Explanatory drawing of the processing procedure of another embodiment.

Hereinafter, an embodiment of the calendar management method will be described with reference to FIGS. 1 to 6. The present embodiment assumes a case where event schedule information is provided to users who use a plurality of games.

As shown in FIG. 1, in the present embodiment, a user terminal 10, a management server 20 (calendar management server), and a game server 30 connected via a network such as the Internet are used.

The user terminal 10 is a computer terminal (information processing terminal such as a smartphone) of a user who has been registered as a user. The user terminal 10 is used when participating in a game provided by the game server 30. It is also used when managing a local calendar on the user terminal 10 and participating in various SNSs (social network services). The user terminal 10 stores a plurality of game applications (programs) provided by the respective game servers 30, applications that provide event schedule information, and the like. The user can participate in the game and check the schedule of events by selecting the application to be launched.

The game server 30 is a server computer that provides various games on the Internet. In the present embodiment, the game server 30 provides a game service to the user terminal 10, manages an event held in each game, and provides event information to the user.

The management server 20 is a computer system that manages users who use the game with respect to the user terminal 10. Specifically, the management server 20 functions as a basic system (platform) that organizes users and manages game services provided by various game servers 30. The management server 20 includes a control unit 21 including a CPU, RAM, ROM, and the like, a user information storage unit 22, a calendar storage unit 23, and an event storage unit 24.

By executing the management program, the control unit 21 functions as a user management unit 211, a calendar management unit 212, a notification unit 213, and a synchronization unit 214.
The user management unit 211 executes a process of managing a user who uses the game.
The calendar management unit 212 executes a process of managing the calendar that records the schedule of events related to each user.

The notification unit 213 executes a process of notifying the user terminal 10 based on the event schedule recorded in the calendar.
The synchronization unit 214 executes a process of exporting the user's event schedule to another calendar application. The synchronization unit 214 stores a data format required for importing into various calendar applications.

The user information storage unit 22 records information for authenticating the user, user information regarding the game information used by the user, calendar setting information for specifying an event to be registered in the calendar, and the like. This user information is recorded when the user is registered on the platform, and is updated when the usage registration of the game is performed. The calendar setting information is recorded when the calendar is registered for a new game, and is updated when the setting is changed.

Data related to the user ID, login password, notification destination, and game used are recorded in the user information.
In the user ID data area, data relating to an identifier for identifying each user is recorded.

In the login password data area, data for authentication when the user logs in to the management server 20 is recorded.
In the notification destination data area, data regarding a contact (e-mail address or user terminal) used when notifying this user is recorded.

In the used game data area, data related to an identifier (game ID) for identifying the game used by the user is recorded. The title of the game can be specified by this game ID. Further, in this data area, data regarding the last use date and time of the game by this user is recorded in association with each game ID.

In the calendar setting information, data related to the calendar target game and the notification method is recorded in association with the user ID.
In the user ID data area, data relating to an identifier for identifying each user is recorded.

In the calendar target game data area, data regarding an identifier (game ID) for identifying a target game for registering an event in the calendar of this user is recorded.
In the notification method data area, data for specifying the notification method when the schedule of the event of this game arrives is recorded. In the present embodiment, notification by e-mail or push notification can be specified.

Calendar data for each user is recorded in the calendar storage unit 23. This calendar is recorded when a user is registered and updated when a new event is registered. The calendar is recorded in association with the user ID. In the calendar, event information (game ID, event ID, notification method) is recorded with respect to the event date and time (date and time as the event time).

In the user ID data area, data relating to an identifier for identifying each user is recorded.
In the game ID data area, data regarding an identifier for identifying a game having an event is recorded.

In the event ID data area, data regarding an identifier for identifying an event in this game is recorded.
In the notification method data area, data for specifying the notification method when the schedule of the event of this game arrives is recorded.

Event information related to various games is recorded in the event storage unit 24. This event information includes information on holding guild battles, birthdays of game characters, campaigns related to various games, and the like. The event information includes data related to the event target game, the event ID, the event content, and the event date and time.

In the event target game data area, data regarding an identifier (game ID) for identifying a game having an event is recorded.
In the event ID data area, data regarding an identifier for identifying an event in this game is recorded.

In the event content data area, information for specifying the event content (for example, battle type, character identification information, anniversary type, campaign type, etc.) is recorded.
In the event date / time data area, data related to the date and time of the event is recorded.

(Calendar management process)
The calendar management process will be described with reference to FIG.
Here, first, the control unit 21 of the management server 20 executes the login process (step S1-1). Specifically, when playing a game, the user terminal 10 is used to access the management server 20. In this case, the user management unit 211 of the control unit 21 outputs a login screen to the display of the user terminal 10. Then, the user management unit 211 acquires the user ID and login password entered in the login screen. Then, the user management unit 211 completes the login authentication when the user ID and login password acquired from the user terminal 10 are registered in the user information storage unit 22. Then, the user management unit 211 identifies the user ID of the login user when the login authentication is completed.

Next, the control unit 21 of the management server 20 executes the My Page display process (step S1-2). Specifically, the user management unit 211 of the control unit 21 outputs My Page to the display of the user terminal 10. This My Page contains tabs for selecting "My Apps", "Pre-registration", and "Events". When the "My apps" tab is selected, a list of applications used by this user is output. When the "Pre-registration" tab is selected, a list of pre-registered applications that have not been released yet is output.

Here, when the "event" tab is selected (step S1-3), the control unit 21 of the management server 20 outputs the event screen to the display of the user terminal 10. As will be described later, a list of event schedule calendars, unregistered calendars, and registered calendars is output on this event screen. The process of generating this event screen will be described below.

First, the control unit 21 of the management server 20 executes a determination process of whether or not there is a calendar registration (step S1-4). Specifically, the calendar management unit 212 of the control unit 21 confirms whether or not the calendar associated with the user ID of the logged-in user is recorded in the calendar storage unit 23.

When it is determined that the calendar associated with the user ID is not recorded in the calendar storage unit 23 and there is no calendar registration (when "NO" in step S1-4), the control unit 21 of the management server 20 determines. The registration promotion process is executed (step S1-5). Specifically, the calendar management unit 212 of the control unit 21 tab-outputs the registration promotion banner on the event screen.

In this case, as shown in FIG. 6A, the event screen 500 is output on the display of the user terminal 10. The registration promotion banner 501 is displayed on the event screen 500. The registration promotion banner 501 includes a message recommending event registration. Further, the event screen 500 is provided with a calendar unregistered column 502 for displaying a list of unregistered calendar games.

Next, the control unit 21 of the management server 20 executes a game display process in which the calendar has not been registered (steps S1-6). Specifically, the calendar management unit 212 of the control unit 21 identifies the game IDs of all the games used in the user information associated with the user IDs in the user information storage unit 22. Next, the calendar management unit 212 specifies the last use date and time of each used game, and sorts the game IDs of the used games in the order of newest last used date and time. Then, the calendar management unit 212 identifies the title of the game to be used corresponding to the game ID, and arranges the titles in the calendar unregistered column 502 of the event screen in the order of the newest last usage date and time. The title display of each game displayed in the calendar unregistered field 502 includes an add button.

When this add button is selected, the control unit 21 of the management server 20 executes the additional setting process (step S1-11). Specifically, the calendar management unit 212 of the control unit 21 identifies the game ID of the selected game title. Then, the calendar management unit 212 outputs a screen for making various settings for the game to the display of the user terminal 10.

In this case, as shown in FIG. 6B, the application setting screen 510 is output on the display of the user terminal 10. The application setting screen 510 is provided with an input field for making various settings related to this game. The input field includes a calendar registration field 511. The calendar registration field 511 is provided with a check box for selecting whether or not calendar registration is necessary, and a check box for selecting a method for receiving notifications (for example, e-mail or push notification).

When the check box of the method of receiving calendar registration or notification is selected in the calendar registration field 511, the calendar management unit 212 stores the calendar setting information recording the selected settings for the game ID of this game in the user information storage unit. Register in 22. In this case, the game ID is recorded as the calendar target game in association with the user ID. Further, the calendar management unit 212 records the game ID in association with the notification method.

Next, the control unit 21 of the management server 20 executes the calendar registration process (step S1-12). Specifically, the calendar management unit 212 of the control unit 21 searches the event storage unit 24 for an event associated with the game ID of the additionally registered game. Then, the calendar management unit 212 registers the event date and time and the event content in the calendar storage unit 23 in association with the user ID for the event extracted from the event storage unit 24. In addition, the notification method specified in the calendar setting information is recorded.

If all the unregistered calendar games cannot be displayed in the unregistered calendar column 502, the extended display button 503 shown in FIG. 6A is output. When the extended display button 503 is selected, the unregistered calendar games that are not displayed are output to the calendar unregistered field 502 in the order of the latest usage date and time.

On the other hand, when the calendar associated with the user ID is recorded in the calendar storage unit 23 and it is determined that the calendar is registered (when "YES" in step S1-4), the control unit 21 of the management server 20 , The calendar display process is executed (step S1-7). Specifically, the calendar management unit 212 of the control unit 21 identifies the calendar associated with the user ID in the calendar storage unit 23. Then, the calendar management unit 212 identifies the date on which the event is registered in this calendar.

In this case, as shown in FIG. 6C, the event screen 520 is output on the display of the user terminal 10. A calendar display 521, an event column 522, and a calendar registration game setting button 523 are output on the event screen 520. The date of the current week is output to the calendar display 521. Then, the calendar management unit 212 displays a check button on the calendar display 521 on the date when the event is recorded in the calendar.

Further, when confirming the event of each date displayed on the calendar display 521, the check box of the desired date is selected.
In this case, the control unit 21 of the management server 20 executes the event identification process on the selected date (step S1-31). Specifically, the calendar management unit 212 of the control unit 21 uses the calendar storage unit 23 to identify an event on the selected date from the user's calendar. Next, the calendar management unit 212 sorts the event date and time in the order of earliest.

Next, the control unit 21 of the management server 20 executes the event list display process (step S1-32). Specifically, the calendar management unit 212 of the control unit 21 arranges the titles of the target games of the event in the event column 522 of the event screen 520 in the sorted order. When this title is selected, the calendar management unit 212 identifies the game ID of the selected game title. Then, the calendar management unit 212 displays the event content recorded in the event storage unit 24 in association with the event ID of this event. Further, a change button is displayed in the title of each game displayed in the event column 522.

When the change button is selected, the control unit 21 of the management server 20 executes the calendar change process (step S1-33). Specifically, the calendar management unit 212 of the control unit 21 outputs a calendar setting change screen to the display of the user terminal 10. This calendar setting change screen is provided with a check box for selecting the necessity of notification and a notification method, and a check box for deleting. Here, when the notification necessity or the passbook method is changed, the calendar management unit 212 changes the event information recorded in the calendar storage unit 23. When the delete check box is selected, the calendar management unit 212 deletes the event schedule recorded in the calendar storage unit 23.

When the calendar registration game setting button 523 on the event screen 520 is selected, the control unit 21 of the management server 20 executes the output processing of the calendar setting screen (step S1-8). Specifically, the calendar management unit 212 of the control unit 21 outputs the calendar setting screen 530 to the display of the user terminal 10.

In this case, as shown in FIG. 6D, the calendar setting screen 530 is output on the display of the user terminal 10. The calendar setting screen 530 is provided with a calendar registered column 531 and a calendar unregistered column 532.

Then, the control unit 21 of the management server 20 executes the game display process registered in the calendar (steps S1-9). Specifically, the calendar management unit 212 of the control unit 21 identifies the game IDs of all the calendar target games in the calendar setting information associated with the user ID in the user information storage unit 22. Next, the calendar management unit 212 specifies the last use date and time of each calendar target game by using the user information of the user information storage unit 22, and rearranges the game IDs of the used games in the order of the newest last use date and time. Then, the calendar management unit 212 identifies the title of the game to be used corresponding to the game ID, and arranges the titles in the calendar registered column 531 of the calendar setting screen 530 in the order of the latest usage date and time. A change button is displayed in the title of each game displayed in the calendar registration column 531.

When this change button is selected, the control unit 21 of the management server 20 executes the change setting process (step S1-21). Specifically, the calendar management unit 212 of the control unit 21 identifies the game ID of the selected game title. Then, the calendar management unit 212 outputs the application setting screen 510 shown in FIG. 6B to the display of the user terminal 10. In the input field of the application setting screen 510, the calendar setting information recorded in the user information storage unit is displayed.
Here, when the notification necessity or the passbook method is changed, the calendar management unit 212 changes the calendar setting information recorded in the user information storage unit 22.

Next, the control unit 21 of the management server 20 executes the calendar change process (step S1-22). Specifically, the calendar management unit 212 of the control unit 21 searches the calendar storage unit 23 for an event related to the changed-registered game and associated with the user ID. Then, the calendar management unit 212 changes the event information extracted from the calendar storage unit 23. If the calendar is not registered, the event schedule associated with the user ID is deleted.

Further, the control unit 21 of the management server 20 executes a game display process in which the calendar has not been registered (steps S1-10). Specifically, the calendar management unit 212 of the control unit 21 specifies the game ID of the game to be used associated with the user ID in the user information storage unit 22. Next, the calendar management unit 212 identifies a game ID that is not registered as a calendar target game in the game used by this user. Next, the calendar management unit 212 specifies the last use date and time of each used game, and sorts the game IDs of the used games in the order of newest last used date and time. Then, the calendar management unit 212 identifies the title of the game to be used corresponding to the game ID, and arranges the titles of the games to be used in the order of the latest usage date and time in the calendar unregistered column 532 of the calendar setting screen 530. An add button is displayed in the title of each game displayed in the calendar unregistered column 532. When this add button is selected, as described above, the control unit 21 of the management server 20 executes the additional setting process (step S1-11) and the calendar registration process (step S1-12).

(Calendar registration process)
Next, the calendar registration process will be described with reference to FIG. Here, when a new event related to the game is registered, the event information is registered in the calendar of the user who has registered the calendar.

Here, first, the control unit 21 of the management server 20 executes the acquisition process of a new event (step S2-1). Specifically, the calendar management unit 212 of the control unit 21 acquires a new event from the game server 30. In this case, the calendar management unit 212 registers the game ID, the event ID, the event date and time, and the event content in the event storage unit 24.

Next, the control unit 21 of the management server 20 executes the identification process of the calendar registered user of the new event (step S2-2). Specifically, the calendar management unit 212 of the control unit 21 searches the user information storage unit 22 for calendar setting information in which the game ID of the newly registered event is recorded as the calendar target game. Then, the calendar management unit 212 identifies the user ID of the user who has registered the game in which the event is newly registered as the calendar target game.

Next, the control unit 21 of the management server 20 executes the event registration process (step S2-3). Specifically, the calendar management unit 212 of the control unit 21 registers the event information and the notification method in the calendar storage unit 23 in the calendar associated with the user ID in association with the event date and time.

(Notification processing)
Next, the notification process for the user terminal 10 will be described with reference to FIG. Here, the user is notified of the start of the event.

First, the control unit 21 of the management server 20 executes the schedule monitoring process (step S3-1). Specifically, the notification unit 213 of the control unit 21 compares the current time with the event date and time for the event registered in the calendar storage unit 23.

Next, the control unit 21 of the management server 20 executes a determination process of whether or not the notification time has arrived (step S3-2). Specifically, the notification unit 213 of the control unit 21 determines that the notification time has arrived when the current time is the event date and time.

When it is determined that the notification time has not arrived (when "NO" in step S3-2), the control unit 21 of the management server 20 continues the schedule monitoring process (step S3-1).

On the other hand, when it is determined that the notification time has arrived (when "YES" in step S3-2), the control unit 21 of the management server 20 executes a notification method specifying process (step S3-3). Specifically, the notification unit 213 of the control unit 21 specifies the notification method recorded in the event information of the calendar storage unit 23.

Next, the control unit 21 of the management server 20 executes the notification output process (step S3-4). Specifically, the notification unit 213 of the control unit 21 acquires the notification destination information of this user from the user information storage unit 22. Then, the notification unit 213 transmits a notification to the user terminal 10 by using the specified notification method.

(Export process)
Next, the export process executed in the synchronization unit 214 will be described with reference to FIG. Here, the event schedule is registered in another calendar application.

First, the control unit 21 of the management server 20 executes the output destination designation process (step S4-1). Specifically, the synchronization unit 214 of the control unit 21 displays the export destination selection screen on the display of the user terminal 10. This output destination selection screen includes a check box for selecting another calendar application to be used by the user (for example, the local calendar of the user terminal 10 or the user calendar of the SNS). Then, the synchronization unit 214 acquires the export destination information specified on the output destination selection screen.

Next, the control unit 21 of the management server 20 executes the output processing of the calendar (step S4-2). Specifically, the synchronization unit 214 of the control unit 21 acquires the calendar information associated with the user ID of this user from the calendar storage unit 23. Next, the synchronization unit 214 converts the data format into the data format used in the designated export destination calendar application and provides it to the user terminal 10. Then, in the user terminal 10, the format-converted calendar information is imported into the export destination calendar application.

According to the above embodiment, the following effects can be obtained.
(1) In the above embodiment, the control unit 21 of the management server 20 executes a game display process in which the calendar is not registered (steps S1-6 and S1-10). Here, when this add button is selected, the control unit 21 of the management server 20 executes the additional setting process (step S1-11) and the calendar registration process (step S1-12). This allows you to register game-related events in the calendar. In particular, the user may use games provided by a plurality of game servers 30, and events related to these games can be integrated and registered in the calendar.

Further, the calendar management unit 212 arranges the titles of the games used in the calendar unregistered column 502 on the event screen in the order of the newest last use date and time. As a result, the most recently used game can be prioritized and calendar registration can be promoted.

(2) In the above embodiment, when it is determined that there is calendar registration (when "YES" in step S1-4), the control unit 21 of the management server 20 executes the calendar display process (step S1-7). .. Then, when each date displayed on the calendar display 521 is selected, the control unit 21 of the management server 20 performs the event identification process (step S1-31) and the event list display process (step S1-32) on the designated date. Execute. This makes it possible to check the schedule of events related to the game used.

(3) In the above embodiment, the control unit 21 of the management server 20 executes the calendar-registered game display process (step S1-9). When the change button is selected, the control unit 21 of the management server 20 executes the change setting process (step S1-21) and the calendar change process (step S1-22). This makes it possible to change the calendar registration of events related to the game used at once.

(4) In the above embodiment, when a new event is registered, the control unit 21 of the management server 20 performs a new event acquisition process (step S2-1) and a new event calendar registration user identification process (step S2-). 2), the event registration process (step S2-3) is executed. As a result, events related to the user's game can be registered in the user's calendar.

(5) In the above embodiment, the control unit 21 of the management server 20 executes the schedule monitoring process (step S3-1). When it is determined that the notification time has arrived (when "YES" in step S3-2), the control unit 21 of the management server 20 specifies the notification method (step S3-3) and outputs the notification (step S3). -4) is executed. As a result, it is possible to alert the user of the arrival of the event time and suppress forgetting to schedule the event.

(6) In the above embodiment, the control unit 21 of the management server 20 executes the export process. As a result, the event information registered in the management server 20 can be imported into another calendar application. Then, along with other schedules, it is possible to manage events related to the game used.

The above embodiment may be changed as follows.
-In the above embodiment, the control unit 21 of the management server 20 executes a determination process of whether or not the notification time has arrived (step S3-2). Specifically, the notification unit 213 of the control unit 21 determines that the notification time has arrived when the current time is the event date and time. Instead of this, a predetermined time before the event date and time may be used as the notification time. For this purpose, the notification unit 213 holds data on the grace period. Then, the notification unit 213 transmits a notification when the grace period has expired from the date and time of the event.

In addition, the notification time and notification method may be changed according to the type of event. For example, for an event with a limited number of people, notification is given earlier than the event time. For this purpose, the notification unit 213 holds data on the grace period and the notification method (number of notifications and notification method) according to the type of event (for example, the limited number of people). In this case, the notification unit 213 acquires the event type from the event storage unit 24, and specifies the grace period and the notification method corresponding to this type. Then, the notification unit 213 transmits a notification when the grace period has expired from the date and time of the event.

Further, in the case of an event (for example, a guild battle) that is continuously performed over a predetermined period, a notification may be given when a predetermined time has passed from the end time of the event. In this case, the event period (start time to end time) is stored in the event information of the event storage unit 24. Then, the notification unit 213 notifies when the remaining time until the end time of the event reaches a predetermined time. Here, the notification method may be changed according to the remaining time. In this case, the notification unit 213 holds the notification method determination information for determining the notification method according to the remaining time. Then, using this notification method determination information, for example, the notification frequency is increased or the number of notification channels is increased as the end time is approached. As a result, it is possible to call attention to the user.

-In the above embodiment, when it is determined that the notification time has arrived (when "YES" in step S3-2), the control unit 21 of the management server 20 notifies the notification method specific process (step S3-3). Output processing (step S3-4) of. Here, the notification method may be changed according to the usage status of the user terminal 10. In this case, the user management unit 211 manages the login status of each user. Further, the notification unit 213 holds information for determining the notification method according to the usage status. For example, when the game is being used, it is displayed in the game, and when the game is not being played, an email or push notification is sent.

(Notification processing)
Hereinafter, the notification process in consideration of the usage status of the user terminal 10 will be described with reference to FIG. 7A.

First, the control unit 21 of the management server 20 executes the schedule monitoring process in the same manner as in step S3-1 (step S5-1).
Next, the control unit 21 of the management server 20 executes a determination process of whether or not the notification time has arrived (step S5-2), as in step S3-2.

When it is determined that the notification time has not arrived (when "NO" in step S5-2), the control unit 21 of the management server 20 continues the schedule monitoring process (step S5-1).

On the other hand, when it is determined that the notification time has arrived (when "YES" in step S5-2), the control unit 21 of the management server 20 executes the process of specifying the usage status of the user terminal (step S5-3). .. Specifically, the notification unit 213 of the control unit 21 acquires information regarding the login status of this user from the user management unit 211.

Next, the control unit 21 of the management server 20 executes a notification method determination process according to the usage status (step S5-4). Specifically, the notification unit 213 of the control unit 21 determines that it is a push notification when it is in the logged-in state. On the other hand, if you are logged out, it is decided to send an email.

Next, the control unit 21 of the management server 20 executes the notification output process (step S5-5). Specifically, the notification unit 213 of the control unit 21 transmits a notification to the user terminal 10 by a notification method determined according to the usage status.
As a result, the notification can be given according to the usage status of the user terminal 10.

-In the above embodiment, when it is determined that the notification time has arrived (when "YES" in step S3-2), the control unit 21 of the management server 20 notifies the notification method specific process (step S3-3). Output processing (step S3-4) of. Here, even when the notification time has come, if the user does not want to be notified, it is possible to perform filtering without notifying. In this case, the notification conditions are recorded in association with each event in the calendar setting information of the user information storage unit 22. For this notification condition, for example, the type of event for which notification is required, the keyword included in the title, and the like can be used. As the notification condition, it is also possible to use an event type that does not require notification, a keyword included in the title, and the like.

(Notification processing)
Hereinafter, the filtered notification process will be described with reference to FIG. 7B.
First, the control unit 21 of the management server 20 executes the schedule monitoring process in the same manner as in step S3-1 (step S6-1).

Next, the control unit 21 of the management server 20 executes a determination process of whether or not the notification time has arrived (step S6-2), as in step S3-2.
When it is determined that the notification time has not arrived (when "NO" in step S6-2), the control unit 21 of the management server 20 continues the schedule monitoring process (step S6-1).

On the other hand, when it is determined that the notification time has arrived (when "YES" in step S6-2), the control unit 21 of the management server 20 executes the specification process of the notification method in the same manner as in step S3-3 (when it is determined that the notification time has arrived). Step S6-3).

Next, the control unit 21 of the management server 20 executes a notification necessity determination process according to the notification conditions (step S6-4). Specifically, the notification unit 213 of the control unit 21 acquires event information from the event storage unit 24. Further, the notification unit 213 acquires the notification conditions of the calendar setting information associated with the user ID and the game ID in the user information storage unit 22. Then, the notification unit 213 collates the event information of the event storage unit 24 with the notification condition of the calendar setting information.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not notification is required (step S6-5). Specifically, the notification unit 213 of the control unit 21 determines whether or not notification is necessary according to the agreement between the event information of the event storage unit 24 and the notification condition of the calendar setting information.

When it is determined that the notification is not necessary according to the result of collating the event information with the notification condition (when "NO" in step S6-5), the control unit 21 of the management server 20 performs the schedule monitoring process (step S6- Continue 1).

On the other hand, when it is determined that the notification is necessary according to the collation result of the event information with the notification condition (when "YES" in step S6-5), the control unit 21 of the management server 20 executes the notification output process. (Step S6-6). Specifically, the notification unit 213 of the control unit 21 notifies by the notification method specified in step S6-3.

As a result, only the events desired by the user can be notified. As the notification condition, it is also possible to use an event type that does not require notification, a keyword included in the title, and the like. In this case, if the event information matches the notification conditions, the notification is not performed.

-In the above embodiment, the notification about the event about the game in which the user has registered the calendar is given. Here, the participation status of the event differs for each user. Therefore, the necessity of notification may be determined according to the participation history (event participation status). In this case, it is possible to notify the event of the game that is always participating and to register only the calendar for the event of the game that is not participating. In this case, the management server 20 is provided with an event participation history information storage unit that records the event participation history for each user. In this event participation history information storage unit, data related to information (game ID, event ID, event content, event date and time) that identifies the event that participated is recorded in association with the user ID. Then, the control unit 21 of the management server 20 calculates the event participation rate for each game or event type by using the event participation history information storage unit in the event information notified to the user. Here, when the event participation rate of the event type of the newly registered event is equal to or higher than the reference value, the control unit 21 notifies the user terminal 10. On the other hand, when the event participation rate is less than the reference value, the control unit 21 only registers with the calendar storage unit 23. As a result, even if a plurality of events registered by the user are held at the same time, the game in which the user is always participating can be notified with priority.

-In the above embodiment, the user is notified of an event related to the game for which the user has registered the calendar. In addition to this, in a group event used by a plurality of users, a notification urging other users to participate in the event may be given. In this case, the management server 20 holds group information about users (group users) belonging to the group determined by the user (proposal user) who has proposed to participate in the group event.

(Calendar registration process)
The calendar registration process related to the group user will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a designated process of another game user (step S7-1). Specifically, the calendar management unit 212 of the control unit 21 acquires information about other users (group users) who participate together from the user terminal 10 of the proposed user. Then, the calendar management unit 212 holds the user ID of the group user as group information.

Next, the control unit 21 of the management server 20 executes the process of setting the candidate date and time for the group event (step S7-2). Specifically, the calendar management unit 212 of the control unit 21 acquires data on the event candidate date and time (event time candidate) desired to participate from the user terminal 10 of the proposal user. Then, the calendar management unit 212 holds the acquired event candidate date and time as group information.

Next, the control unit 21 of the management server 20 executes a communication process of whether or not to join the group user (step S7-3). Specifically, the calendar management unit 212 of the control unit 21 transmits an event participation request to the user terminal 10 of another user recorded in the group information. This event participation request includes data on the event candidate date and time recorded in the group information.

Next, the control unit 21 of the management server 20 executes a collection process for participation (step S7-4). Specifically, the calendar management unit 212 of the control unit 21 collects the participation request from the user terminal 10 of the group user. In this case, the data regarding the event candidate date and time that the group user wants to participate in is included in the event candidate date and time.

Next, the control unit 21 of the management server 20 executes the event date / time identification process (step S7-5). Specifically, the calendar management unit 212 of the control unit 21 specifies the event candidate date and time when the group user most requested to participate in the event candidate date and time as the event date and time (event time).

Next, the control unit 21 of the management server 20 executes the calendar registration process of the participating users (step S7-6). Specifically, the calendar management unit 212 of the control unit 21 registers the event schedule of the specified event date and time in the calendar associated with the user ID of the group user who wants to participate in the calendar storage unit 23.

In the above embodiment, the candidate date and time with the highest number of requests for participation is specified as the event date and time. Instead of this, the event date and time may be determined in consideration of the attributes of the users who wish to participate. In this case, in the proposed user, weighting according to the attribute of the group user is set and recorded in the group information. For example, users who are strong in games (users who frequently use many items and games) are given high weighting. Further, the calendar management unit 212 of the control unit 21 sums the weighting of the group users of the participation desired unit for each event candidate date and time. Then, the calendar management unit 212 determines the event candidate date and time with the highest total value as the event date and time. As a result, the event can be executed in consideration of the attributes of the group users.
Next, the technical idea that can be grasped from the above embodiment and another example will be added below.
[1]
For each user, a user information storage unit that stores the game used by the user and the game to be registered as a calendar in the game used.
A calendar storage unit that stores the calendar of the event schedule for each user,
It is a method of managing the calendar using a control unit connected to a user terminal via a network.
The control unit
The login process identifies the user of the user terminal and
When the calendar registration target game of the specified user is stored in the user information storage unit, a screen including an event schedule for the calendar registration target game including an event period is displayed on the user terminal.
When a new event registration is detected for the calendar registration target game, a notification is sent on the user terminal based on the notification method determination information for determining the notification method according to the remaining time until the end time of the event. A calendar management method characterized by doing.
[2]
The calendar management method according to [1], wherein the control unit increases the notification frequency as the end time approaches, based on the notification method determination information.
[3]
The calendar management method according to [1], wherein the control unit increases the number of notification channels and performs notification based on the notification method determination information as the end time approaches.
[4]
The game information used by the user is recorded in the user information storage unit.
The control unit
If there is a game that is not registered as a calendar among the games used by the user recorded in the user information storage unit, the games used are sorted in the order of newest last usage time.
A list of game information of games used by the user but not registered in the calendar is output to the user terminal in the order of newest last usage time.
The calendar management method according to any one of [1] to [3], wherein the game specified in the list is registered in the user information storage unit as a calendar registration target game.
[5]
The control unit
Identify group users who are encouraged to participate in group events used by multiple users
The event guide of the group event is transmitted to the group user,
The item according to any one of [1] to [4], wherein when the group user announces participation in the group event, the group user is registered in the calendar of the group user. Calendar management method.
[6]
The control unit
A plurality of event time candidates for the group event are transmitted to the event guide.
For each event time candidate, identify the participation status of the group users and
The calendar management method according to [5], wherein the event time of the group event is determined according to the participation status.
[7]
The control unit
Identify the attributes of the group users who wish to participate in the group event
The calendar management method according to [5] or [6], wherein the event time is determined from the event time candidates of the group event according to the attribute.
[8]
The control unit
An item owned by a group user is specified, and the group user is weighted based on the item.
The calendar management method according to [7], wherein the event candidate date and time of the group user specified according to the weighting is determined as the event date and time.
[9]
The control unit
Connected to the event participation history information storage unit that records the event participation history for each user,
In the event information notified to the user, the event participation rate is calculated for each game and event type using the event participation history information storage unit.
The item according to any one of [1] to [8], wherein when the event participation rate of the event type of the newly registered event is equal to or higher than the reference value, the user terminal is notified. Calendar management method.
[10]
For each user, a user information storage unit that stores the game used by the user and the game to be registered as a calendar in the game used.
A calendar storage unit that stores the calendar of the event schedule for each user,
It is equipped with a control unit connected to a user terminal via a network.
The control unit
The login process identifies the user of the user terminal and
When the calendar registration target game of the specified user is stored in the user information storage unit, a screen including an event schedule for the calendar registration target game including an event period is displayed on the user terminal.
When the registration of a new event is detected for the game subject to calendar registration, the user terminal notifies the user terminal based on the notification method determination information for determining the notification method according to the remaining time until the end time of the event. A calendar management server characterized by doing.
[11]
For each user, a user information storage unit that stores the game used by the user and the game to be registered as a calendar in the game used.
A calendar storage unit that stores the calendar of the event schedule for each user,
A program for managing the calendar using a control unit connected to a user terminal via a network.
The control unit
The login process identifies the user of the user terminal and
When the calendar registration target game of the specified user is stored in the user information storage unit, a screen including an event schedule for the calendar registration target game including an event period is displayed on the user terminal.
When the registration of a new event is detected for the game subject to calendar registration, a notification is sent on the user terminal based on the notification method determination information for determining the notification method according to the remaining time until the end time of the event. A calendar management program characterized by functioning as a means of doing so.

10 ... user terminal, 20 ... management server, 21 ... control unit, 211 ... user management unit, 212 ... calendar management unit, 213 ... notification unit, 214 ... synchronization unit, 22 ... user information storage unit, 23 ... calendar storage unit, 24 ... Event storage, 30 ... Game server.

Claims (12)

For each user, a user information storage unit that stores notification condition is a user available games is using, and the line power sale conditions calender registered game, and the notification of the calendar registered game in said use game ,
For each user, a calendar storage unit that stores the calendar of the event schedule related to the event of the game to be registered in the calendar, and a calendar storage unit.
A specific part that identifies the user of the user terminal by login processing,
When the calendar registration target game of the specified user is stored in the user information storage unit, a display control unit that displays a screen including an event schedule for the calendar registration target game including an event period on the user terminal.
A notification condition setting unit that accepts an operation of the user who sets the notification condition in association with the type of the event, and a notification condition setting unit.
When the registration of a new event is detected for the game to be registered in the calendar, the event registration unit that registers the event and the notification method in the calendar associated with the user, and the event registration unit.
When the notification time has come for the registered event, it is determined whether or not the type of the event satisfies the notification condition, and if the event satisfies the notification condition, a notification is given and the type of the event is set. A calendar management system including a notification control unit that does not notify when the notification conditions are not satisfied. The calendar management system according to claim 1, wherein the notification control unit increases the notification frequency as the end time of the event approaches when the notification condition is satisfied. The calendar management system according to claim 1, wherein the notification control unit increases the number of notification channels to notify when the notification condition is satisfied and the end time of the event approaches. The game information used by the user is recorded in the user information storage unit.
If there is a game that is not registered in the calendar among the games used by the user recorded in the user information storage unit, the display control unit rearranges the games used in the order of newest usage time.
A list of game information of games used by the user but not registered in the calendar is output to the user terminal in the order of newest last usage time.
The calendar management system according to any one of claims 1 to 3, wherein the event registration unit registers the game specified in the list as a calendar registration target game in the user information storage unit. The specific unit identifies a group user who encourages participation in a group event used by a plurality of users.
The notification control unit transmits an event guide of the group event to the group user, and the notification control unit transmits the event guide of the group event.
The event registration unit according to any one of claims 1 to 4, wherein when the group user announces participation in the group event, the group user registers the group event in the calendar of the group user. Calendar management system. The notification control unit transmits a plurality of event time candidates for the group event to the event guide, and at the same time, the notification control unit transmits a plurality of event time candidates for the group event.
For each event time candidate, the participation status identification unit that specifies the participation status of the group users, and
The calendar management system according to claim 5, further comprising an event timing determination unit that determines the event timing of the group event according to the participation status. An attribute identification unit that specifies the attributes of group users who wish to participate in the group event,
The calendar management system according to claim 5 or 6, further comprising an event time determination unit that determines an event time according to the attribute from the event time candidate of the group event. The event timing determination unit
An item owned by a group user is specified, and the group user is weighted based on the item.
The calendar management system according to claim 7, wherein the event candidate date and time of the group user specified according to the weighting is determined as the event date and time. In the event information notified to the user, the event participation history information storage unit that stores the event participation history of the user is further provided, and a participation rate acquisition unit that acquires the event participation rate for each game and event type is further provided.
The calendar according to any one of claims 1 to 8, wherein the notification control unit notifies the user terminal when the event participation rate of the event type of the newly registered event is equal to or higher than the reference value. Management system. The notification condition setting unit accepts the operation of the user who sets the notification condition for the keyword included in the title of the event.
The calendar management system according to any one of claims 1 to 9. The control unit
For each user, a user information storage unit that stores notification condition is a user available games is using, and the line power sale conditions calender registered game, and the notification of the calendar registered game in said use game ,
For each user, a calendar storage unit that stores the calendar of the event schedule related to the event of the game to be registered in the calendar is used.
The step of identifying the user of the user terminal by the login process,
When the calendar registration target game of the specified user is stored in the user information storage unit, a step of displaying on the user terminal a screen including an event schedule for the calendar registration target game including an event period, and
A step of accepting an operation of the user who sets the notification condition in association with the type of the event, and
When the registration of a new event is detected for the game to be registered in the calendar, the step of registering the event and the notification method in the calendar associated with the user, and
When the notification time has arrived for the registered event, it is determined whether or not the type of the event satisfies the notification condition, and if the event satisfies the notification condition, a notification is given and the type of the event is set. A calendar management method for executing a step of not notifying if the notification condition is not satisfied. In the control unit
For each user, a user information storage unit that stores notification condition is a user available games is using, and the line power sale conditions calender registered game, and the notification of the calendar registered game in said use game ,
For each user, a calendar storage unit that stores the calendar of the event schedule related to the event of the game to be registered in the calendar is used.
The step of identifying the user of the user terminal by the login process,
When the calendar registration target game of the specified user is stored in the user information storage unit, a step of displaying on the user terminal a screen including an event schedule for the calendar registration target game including an event period, and
A step of accepting an operation of the user who sets the notification condition in association with the type of the event, and
When the registration of a new event is detected for the game to be registered in the calendar, the step of registering the event and the notification method in the calendar associated with the user, and
When the notification time has arrived for the registered event, it is determined whether or not the type of the event satisfies the notification condition, and if the event satisfies the notification condition, a notification is given and the type of the event is set. A calendar management program that executes a step that does not notify if the notification conditions are not met.

Images