Information processing device

Abstract

To enhance a user's willingness to receive benefits continuously by the payment of a game charge for each fixed period.SOLUTION: An information processing device includes: a user information storage part for storing user information including information for specifying that a user is the user who has paid a game charge set for each fixed period; an event provision part for providing, within a fixed period last time, an event game that is made playable by the payment of a game charge for the fixed period last time, to a user who has paid a game charge for the fixed period last time; and an event re-provision part for providing, within a fixed period this time, an event game the same as or related to the aforesaid event game that is made playable by the payment of the game charge for the fixed period last time, to the user who has paid the game charge for the fixed period last time, and has also paid a game charge for the successive fixed period this time.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing device and a program. [Background technology]

[0002] Systems are known in which a game fee is set for each fixed period (e.g., a monthly fee) and users who have paid the game fee for the fixed period are permitted to play the game during that fixed period (e.g., Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-200692 A Summary of the Invention [Problem to be solved by the invention]

[0004] In such a system, for example, if a user has paid the game fee for the previous fixed period, the user can receive a benefit for paying the game fee only during that previous fixed period. In order to receive the same benefit in the next fixed period, the user must pay the game fee for the current fixed period. However, there was no mechanism to actively encourage users who had paid the game fee for the previous fixed period to pay the game fee for the current fixed period, which could reduce users' motivation to continue receiving benefits.

[0005] The present invention has been made in consideration of the above circumstances, and its purpose is to increase users' motivation to receive continuous benefits by paying a game fee at regular intervals. [Means for solving the problem]

[0006] The main invention of the present invention to solve the above problems is: a user information storage unit that stores user information including information for identifying whether or not a user has paid a game fee set at a fixed period; an event providing section that provides, to a user who has paid a game fee for a previous fixed period, an event game that has become playable as a result of the user having paid the game fee for the previous fixed period, during the previous fixed period; an event re-providing unit for providing, to a user who has paid a game fee for a previous fixed period and also paid a game fee for a current subsequent fixed period, an event game that is the same as or related to the event game that became playable as a result of the user having paid the game fee for the previous fixed period, during the current fixed period; The present invention relates to an information processing device comprising: According to such an information processing device, by paying the game fee for the previous fixed period and the game fee for the current fixed period, the event game that was playable during the previous fixed period can be played during the current fixed period. Therefore, a user who was unable to play the event game during the previous fixed period or a user who played the event game during the previous fixed period but was unable to complete it can challenge the event game during the current fixed period. This motivates users who have paid the game fee for the previous fixed period to pay the game fee for the current fixed period, thereby increasing the willingness of users to continuously receive benefits by paying the game fee every fixed period.

[0007] Furthermore, when a user who has paid a game fee for a previous fixed period logs in within the previous fixed period, the event providing unit provides the logged-in user with an event game that has become playable as a result of the user having paid the game fee for the previous fixed period; When a user who has paid the game fee for the previous fixed period and has also paid the game fee for the current fixed period does not log in during the previous fixed period, it is desirable for the event re-provision unit to provide, again within the current fixed period, to the user who did not log in an event game that is the same as or related to the event game that was provided during the period in the previous fixed period when the user did not log in. This makes it possible for a user to challenge, within the current fixed period, the event games that were offered during the period in which the user did not log in, even if the user was unable to log in to the event game within the previous fixed period.

[0008] Furthermore, the event providing unit provides the event game that can be played over a plurality of days to a logged-in user who has paid a game fee for a previous fixed period and has logged in within the previous fixed period; When a user who has paid the game fee for the previous fixed period and has also paid the game fee for the current fixed period does not log in on any of the multiple days, it is desirable for the event re-provision unit to re-provide, within the current fixed period, an event game that is the same as or related to the event game that the user who paid the game fee for the previous fixed period was able to play over multiple days for the number of days on which the user did not log in. This means that even if you were unable to log in to all of the event games for multiple days during the previous fixed period, you will be able to challenge the events for the number of days that you were not logged in during the current fixed period.

[0009] Furthermore, when a user who has paid a game fee for a previous fixed period logs in within the previous fixed period, the event providing unit provides the logged-in user with an event game that has become playable as a result of the user having paid the game fee for the previous fixed period, over a number of days spanning the previous fixed period and the current fixed period; When a user who has paid the game fee for the previous fixed period and also paid the game fee for the current fixed period does not log in on any day included in the previous fixed period out of the multiple days, it is desirable for the event re-provision unit to again provide, within the current fixed period, to the user who did not log in an event game that is the same as or related to the event game that was playable over multiple days, for the number of days that the user who paid the game fee for the previous fixed period did not log in on any day included in the previous fixed period out of the multiple days. This means that when event games are provided for multiple days spanning a previous fixed period and a current fixed period, even if you are unable to log in on any of the days included in the previous fixed period, you will be able to challenge the game within the current fixed period for the number of days that you did not log in on any of the days included in the previous fixed period.

[0010] Furthermore, when a user who has paid a game fee for a previous fixed period logs in within the previous fixed period, the event providing unit provides the logged-in user with an event game that has become playable as a result of the user having paid the game fee for the previous fixed period; When a user who has paid the game fee for the previous fixed period and also paid the game fee for the current fixed period is unable to complete the event game that was provided during the period in which the user logged in during the previous fixed period, it is desirable for the event re-provision unit to provide again, within the current fixed period, an event game that is the same as or related to the event game that the user was unable to complete. This allows a player to challenge the event game that he / she was unable to clear within a certain period of time last time, again within the current period of time.

[0011] It is also desirable to have a bonus awarding unit that awards a bonus that is more advantageous to a user who has paid the game fee for the previous fixed period and who performs the operations required to pay the game fee for the current fixed period earlier within the previous fixed period. This makes it possible to motivate users who have paid the game fee for the previous fixed period to pay the game fee for the current fixed period early, thereby further increasing users' desire to receive continuous benefits by paying the game fee at fixed intervals.

[0012] Also, the computer, a user information storage means for storing user information including information for identifying whether or not a user has paid a game fee set at a fixed period; an event providing means for providing, to a user who has paid a game fee for a previous fixed period, an event game that has become playable as a result of the user having paid the game fee for the previous fixed period, during the previous fixed period; an event re-provision means for providing, to a user who has paid a game fee for a previous fixed period and also paid a game fee for a current subsequent fixed period, an event game that is the same as or related to the event game that became playable as a result of the user having paid the game fee for the previous fixed period, within the current fixed period; This is a program that functions as a Such a program can increase the user's motivation to receive continuous benefits by paying a game fee at regular intervals. [Brief description of the drawings]

[0013] [Figure 1] 1 is a configuration diagram illustrating an example of an information processing system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a hardware configuration diagram illustrating an example of a computer according to the present embodiment. [Diagram 3] FIG. 2 is a functional block diagram illustrating an example of a server device according to the embodiment. [Figure 4] FIG. 2 is a functional block diagram illustrating an example of a client terminal according to the embodiment. [Diagram 5] 4 is a flowchart illustrating an example of the operation of the information processing system 1 in the present embodiment. [Figure 6] FIG. 4 is a diagram illustrating an example of user information. [Figure 7] FIG. 2 is a diagram illustrating an example of log history information. [Figure 8] FIG. 13 is a diagram illustrating an example of monthly billing user information. [Figure 9] FIG. 13 is a diagram showing an example of login bonus information. [Figure 10] FIG. 2 is a diagram illustrating an example of event information. [Figure 11] FIG. 13 is an image diagram showing an example of a game screen. [Figure 12] FIG. 11 is a diagram illustrating a first specific example in which the same event game as last month's event game is provided again within the current month. [Figure 13] FIG. 11 is a diagram illustrating a specific example 2 in which the same event game as last month's event game is provided again within the current month. [Figure 14] FIG. 11 is a diagram illustrating a specific example 3 in which the same event game as last month's event game is provided again within the current month. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] The following describes in detail an information processing device, a program, and an information processing system according to an embodiment of the present invention. The present invention can be widely applied to information processing devices, programs, information processing systems, and the like that employ games that can be played by users who have paid a game fee (e.g., a monthly fee) at regular intervals.

[0015] [Embodiment] <System configuration> Fig. 1 is a configuration diagram showing an example of an information processing system 1 according to this embodiment. As shown in Fig. 1, in the information processing system 1 according to this embodiment, one or more client terminals 10 and a server device 20 are connected via a network N.

[0016] The client terminal 10 is a terminal device operated by a user, such as a PC, smartphone, tablet, or a dedicated game device for home or commercial use. The server device 20 manages and controls the game played by the user on the client terminal 10, and processes billing within the game. The network N is the Internet or the like, and includes a mobile wireless base station, etc.

[0017] In addition to the client-server type information processing system 1 shown in Fig. 1, the present invention can also be applied to a single game device by providing a separate mechanism for in-game billing. The information processing system 1 in Fig. 1 is only one example, and it goes without saying that there are various system configurations depending on the application and purpose. For example, the server device 20 in Fig. 1 may be configured to be distributed across multiple computers.

[0018] <Hardware configuration> Client terminal and server device Fig. 2 is a hardware configuration diagram showing an example of a computer 50 according to the present embodiment. The client terminal 10 and the server device 20 according to the present embodiment are realized by, for example, a computer 50 having the hardware configuration shown in Fig. 2. The computer 50 is an example of an information processing device.

[0019] 2, the computer 50 includes a CPU 51, a RAM 52, a ROM 53, a communication interface 54, an input device 55, a display device 56, an external interface 57, and a HDD 58, all of which are connected to one another via a bus line B. The input device 55 and the display device 56 may be connected and used when necessary.

[0020] The CPU 51 is a calculation device that loads programs and data from storage devices such as the ROM 53 and the HDD 58 onto the RAM 52 and executes various processes based on the loaded programs and data, thereby controlling the entire computer and implementing its functions.

[0021] The RAM 52 is an example of a volatile semiconductor memory (storage device) for temporarily storing programs and data, and is also used as a work area when the CPU 51 executes various processes.

[0022] The ROM 53 is an example of a non-volatile semiconductor memory (storage device) that can retain programs and data even when the power is turned off. The ROM 53 stores programs and data such as the BIOS, OS settings, and network settings that are executed when the computer 50 is started.

[0023] The communication interface 54 is an interface for connecting the computer 50 to the network N. This enables the computer 50 to perform data communication via the communication interface 54.

[0024] The input device 55 is a device used by a user or an administrator to input various signals. The input device 55 in this embodiment is, for example, an operating device such as a touch panel, operation keys or buttons, a keyboard, or a mouse.

[0025] The display device 56 is a device for displaying various information on a screen to a user or an administrator. The display device 56 in this embodiment is, for example, a liquid crystal or organic EL display.

[0026] The external interface 57 is an interface for connecting to an external device so as to enable data communication. This allows the computer 50 to read and / or write data from and to a recording medium via the external interface 57. The external device is, for example, a recording medium such as a flexible disk, a CD, a DVD, an SD memory card, or a USB memory.

[0027] The HDD 58 is an example of a non-volatile storage device that stores programs and data, such as the OS, which is the basic software that controls the entire computer, and applications that provide various functions on the OS.

[0028] Instead of the HDD 58, a drive device that uses a flash memory as a storage medium (for example, a solid-state drive (SSD)) may be used.

[0029] The client terminal 10 and the server device 20 according to this embodiment can realize various processes, which will be described later, by executing a program on the computer 50 having the above-mentioned hardware configuration.

[0030] <Software configuration> Server device 3 is a functional block diagram showing an example of the server device 20 according to the present embodiment. The server device 20 according to the present embodiment is realized by, for example, the functional blocks shown in FIG.

[0031] The server device 20 according to the present embodiment realizes a server control unit 200, a server storage unit 220, and a server communication unit 240 by executing a program.

[0032] The server control unit 200 has a function of executing processes related to various games. The server control unit 200 includes a game control unit 201, an event providing unit 202, an event re-providing unit 203, a benefit granting unit 204, a notification unit 205, and a display control unit 206.

[0033] The game control unit 201 controls the progress of various games, such as a competitive game and a lottery game, which will be described later, based on game operations received from a user by the client terminal 10. The game control unit 201 in this embodiment also functions as a competitive game control unit and a lottery game control unit.

[0034] The event providing unit 202 provides an event game to the user. For example, when a user has paid a game fee for a previous fixed period, the event providing unit 202 in this embodiment provides, within the previous fixed period, an event game that became playable as a result of the payment of the game fee for the previous fixed period. Also, when a user continues to pay a game fee for a current fixed period following the previous fixed period, the event providing unit 202 provides, within the current fixed period, the event game that became playable as a result of the payment of the game fee for the current fixed period to the user who has paid the game fee for the current fixed period.

[0035] The event re-providing unit 203 provides again to the user an event game that has already been provided by the event providing unit 202. For example, when a user has paid the game fee for the previous fixed period and has also paid the game fee for the current subsequent fixed period, the event re-providing unit 203 in this embodiment provides again, within the current fixed period, the same event game as the event game that became playable by paying the game fee for the previous fixed period.

[0036] The reward provision unit 204 provides a reward to the user. For example, when a user has paid game fees for a previous fixed period, the reward provision unit 204 in this embodiment provides the user with a reward for the payment of game fees for the previous fixed period within the previous fixed period. Also, when the user continues to pay game fees for the current fixed period, the reward provision unit 204 provides the user with a reward for the payment of game fees for the current fixed period within the current fixed period. The reward provision unit 204 in this embodiment can provide a reward that is more advantageous to the user, for example, the earlier the user who has paid game fees for the previous fixed period performs an operation required to pay game fees for the current fixed period within the previous fixed period.

[0037] The notification unit 205 notifies the user of various information. In this embodiment, the notification unit 205 notifies the user during the current fixed period to encourage payment of the game fee for the next fixed period. The notification unit 205 can notify the user by displaying a screen, sending an email, or by using a push notification.

[0038] The display control unit 206 generates data of various game screens according to the progress of a competitive game or a lottery game executed by the game control unit 201, for example, and controls the screen display of the client terminal 10.

[0039] The server storage unit 220 has a function of storing information related to various games. The server storage unit 220 includes a character information storage unit 221, a user information storage unit 222, a login bonus information storage unit 223, and an event information storage unit 224.

[0040] The character information storage unit 221 is an example of a content information storage unit, and stores character information (content information) related to characters as an example of content. The character information stored in the character information storage unit 221 includes various characters used in fighting games and lottery games, various characters used as benefits, and the like.

[0041] The user information storage unit 222 stores user information about users. The user information stored in the user information storage unit 222 includes information such as the rank of the user, various characters owned by the user, and information for identifying whether the user has paid a game fee every certain period (monthly billing user).

[0042] The login bonus information storage unit 223 is an example of a privilege information storage unit, and stores login bonus information (privilege information) related to a login bonus as an example of a privilege. The login bonus information stored in the login bonus information storage unit 223 sets the type and amount of a login bonus that is granted when a user logs in for each fixed period of time.

[0043] The event information storage unit 224 stores event information related to events. In the event information stored in the event information storage unit 224, an event game is set for each fixed period to be provided to a user who has paid a game fee for each fixed period (a monthly billing user).

[0044] The server communication unit 240 has a function of communicating with the client terminal 10 via the network N.

[0045] Client terminal 4 is a functional block diagram showing an example of the client terminal 10 according to the present embodiment. The client terminal 10 according to the present embodiment is realized by, for example, the functional blocks shown in FIG.

[0046] The client terminal 10 according to this embodiment executes a program to realize a client control unit 100, a client storage unit 120, a client communication unit 140, an operation receiving unit 150, and a screen display unit 160. The client control unit 100 includes a request sending unit 101 and a response receiving unit 102.

[0047] The operation reception unit 150 receives operations from a user who operates the client terminal 10. Furthermore, the client control unit 100 performs processing related to the game in the client terminal 10. The request transmission unit 101 transmits a request to the server device 20 based on the content of the operation received from the user by the operation reception unit 150. The response reception unit 102 receives responses such as processing results in response to the request transmitted by the request transmission unit 101 to the server device 20.

[0048] Furthermore, the client storage unit 120 stores information required for the client terminal 10. The client communication unit 140 communicates with the server device 20. The screen display unit 160 performs screen display of the client terminal 10 under control of the server device 20.

[0049] As described above, in the information processing system 1 according to this embodiment, the server device 20 controls the progress of the game and the display, but the client terminal 10 may also control these. Specifically, at least a part of the functional units of the server control unit 200 may be configured not to be provided in the server control unit 200 of the server device 20, but to be provided in the client control unit 100 of the client terminal 10.

[0050] The client control unit 100 of the client terminal 10 may be of a browser type that receives page data written in HTML (Hyper Text Markup Language) or the like and scripts included in the page data from the server device 20 and performs processing related to the game. The client control unit 100 of the client terminal 10 may be of an application type that performs processing related to the game based on an installed application.

[0051] <Summary> Here, an overview of the system in this embodiment will be described. In the system in this embodiment, a competitive game and a lottery game are provided to users.

[0052] The battle game in this embodiment is a game in which an enemy character appears against a party made up of multiple characters, and each character making up the party battles the enemy character that has appeared.

[0053] In this fighting game, multiple quests are set up, with the objective of defeating enemy characters, depending on the difficulty level. The user can form a party using the characters he owns, select one of the quests and challenge the enemy character to a battle. During the battle, the user may be given a character that is set to be obtainable in the selected quest.

[0054] The lottery game in this embodiment is a game in which, when a user's operation to select a character is received, one of multiple characters subject to the lottery is selected based on the lottery probability of each character, and the selected character is granted to the user.

[0055] In this lottery game, the higher the rarity of a character, the lower the probability of winning the lottery. Users can form their own party using the characters they obtain in the lottery game and play a battle game.

[0056] In addition, in the system of this embodiment, a user can become a monthly billing user by paying a game fee (monthly fee) every month (every fixed period). If a user becomes a monthly billing user, for example, when the user pays the game fee for this month, the user is provided with an event game that becomes playable for the payment of the game fee for this month during the month, and can receive a special benefit for paying the game fee for this month.

[0057] In this embodiment, as a reward for paying the game fee for this month, a login bonus can be received by logging in to the game once per day during this month. The login bonus received by monthly billing users is set to be more advantageous than the login bonus received by users (normal users) who have not paid the game fee for this month.

[0058] Furthermore, if you become a monthly paying user, for example if you have paid last month's game fee and then continue to pay this month's game fee, you will be provided with the same event game for one month during the current month that became available to play by paying last month's game fee.

[0059] Therefore, even if a user who has paid last month's game fee was unable to log in on any day last month and was unable to play last month's event game that became available as a result of paying last month's game fee, he / she can still pay this month's game fee to challenge last month's event game within this month. Also, if a user who has paid last month's game fee logged in on any day last month but was unable to complete last month's event game, he / she can still pay this month's game fee to re-attempt last month's event game that he / she was unable to complete within this month.

[0060] In this way, users who paid last month's game fee can be given an incentive to pay this month's game fee, thereby increasing the willingness of monthly paying users to receive continuous benefits by paying the monthly fee.

[0061] <Operation> FIG. 5 is a flowchart illustrating an example of the operation of the information processing system 1 in this embodiment.

[0062] When the login screen for the competitive game is displayed on the screen display unit 160 of the client terminal 10, the user performs a login operation on the client terminal 10 to log in to the competitive game. When the user performs a login operation on this login screen, the operation acceptance unit 150 of the client terminal 10 accepts the operation content based on the user's login operation.

[0063] The request sending unit 101 of the client terminal 10 sends a login request for a competitive game accompanied by login operation information, such as a user ID and password, to the server device 20 based on the operation content accepted by the operation accepting unit 150 from the user (step S11).

[0064] Next, when the game control unit 201 of the server device 20 accepts a login request for the competitive game from the client terminal 10, the game control unit 201 executes login processing for the competitive game in accordance with login operation information including a user ID, a password, and the like (step S12).

[0065] Specifically, the game control unit 201 of the server device 20 performs user authentication based on the user ID and the like accompanying the login request, by referring to the user information stored in the user information storage unit 222. When the game control unit 201 of the server device 20 successfully authenticates the user, it updates the log history information set in the user information and adds the login date and time of the competitive game.

[0066] FIG. 6 is a configuration diagram showing an example of user information. The user information shown in FIG. 6 has items such as a user ID, the number of owned items, owned characters, party, log history information, monthly billing user information, event provision information, and event clear information. The user ID is information for uniquely identifying a user. The number of owned items is information indicating the number of items owned by the user. The owned characters is information indicating one or more various characters currently owned by the user. The party is information indicating each character that constitutes the user's party. The log history information is information indicating the user's log history. The monthly billing user information is information about monthly billing users. The event provision information is information about events that can be provided to the user. The event clear information is information about events that the user has cleared.

[0067] Fig. 7 is a configuration diagram showing an example of log history information. The log history information shown in Fig. 7 has items such as a log ID, login date and time, and logout date and time. The log ID is information for uniquely identifying log data. The login date and time is information indicating the date and time when a user logged into a fighting game. The logout date and time is information indicating the date and time when a user logged out.

[0068] Returning to Figure 5, next, when the login process for the competitive game is completed in this manner, the game control unit 201 of the server device 20 acquires monthly billing user information from the user information stored in the user information storage unit 222, and, referring to the acquired monthly billing user information, determines whether the logged-in user is a monthly billing user who has paid the game fee for this month (step S13).

[0069] FIG. 8 is a configuration diagram showing an example of monthly billing user information. The monthly billing user information shown in FIG. 8 has items such as payment target, monthly billing user, and payment date and time. The payment target is information indicating the month for which the monthly fee is to be paid. Here, it is assumed that the current month is September, and it is shown that the user has paid the game fee for last month, August, and the game fee for this month, September. The monthly billing user is information indicating whether or not the user has become a monthly billing user for the month for which payment is to be made. The payment date and time is information indicating the date and time when the game fee for that month was paid.

[0070] 5, if it is determined in step S13 that the user is a monthly billing user who has paid the game fee for this month, the process proceeds to step S15, which will be described later. On the other hand, if it is determined that the user is not a monthly billing user who has paid the game fee for this month, the process proceeds to step S14.

[0071] Next, if the bonus granting unit 204 of the server device 20 determines that the user is not a monthly billing user who has paid the game fee for this month (step S13: NO), the bonus granting unit 204 grants a login bonus for a regular user based on the login bonus information stored in the login bonus information memory unit 223 since the user is a regular user who has not paid the game fee for this month (step S14).

[0072] Specifically, the bonus granting unit 204 of the server device 20 grants the login bonus for a normal user set for that day only when the user logs in for the first time on that day, based on the login bonus information stored in the login bonus information storage unit 223. In other words, the login bonus is granted only once a day.

[0073] FIG. 9 is a configuration diagram showing an example of login bonus information. The login bonus information shown in FIG. 9 has items such as a privilege ID, a provision period, privilege contents of a normal user, and privilege contents of a monthly billing user. The privilege ID is information for uniquely identifying a privilege. The provision period is information indicating a period during which a login bonus can be granted. The privilege contents of a normal user are information indicating the contents of a login bonus granted when a normal user logs in during the provision period. Here, an item is set as the login bonus of a normal user, and the number of items granted is also set as shown in parentheses in the figure. The privilege contents of a monthly billing user are information indicating the contents of a login bonus granted when a monthly billing user logs in during the provision period. Here, an item or a character is set as the login bonus of a monthly billing user, and the number of items or characters granted is also set as shown in parentheses in the figure. In this embodiment, the login bonus received by a monthly billing user is set to be more advantageous than the login bonus received by a normal user.

[0074] Returning to FIG. 5, next, if the bonus granting unit 204 of the server device 20 determines that the user is a monthly billing user who has paid the game fee for this month (step S13: YES), the bonus granting unit 204 grants a login bonus as a bonus for paying the game fee for this month (step S15).

[0075] Specifically, the bonus granting unit 204 of the server device 20 grants a login bonus to a monthly billing user, different from a regular user, set on that day, based on the login bonus information stored in the login bonus information storage unit 223.

[0076] The bonus granting unit 204 of the server device 20 grants the login bonus for the monthly billing user set for that day only when the user logs in for the first time on that day. In other words, the login bonus for the monthly billing user is granted only once a day.

[0077] Next, when the bonus granting unit 204 of the server device 20 has granted the login bonus for this month in this manner, the event providing unit 202 provides the event game for this month, which can be played by paying the game fee for this month, to the monthly billing user who has paid the game fee for this month (step S16).

[0078] Specifically, first, the event providing unit 202 of the server device 20 refers to the event information stored in the event information storage unit 224, and obtains the event games for this month that can be provided to monthly billing users who have paid the game fee for this month.

[0079] FIG. 10 is a configuration diagram showing an example of event information. The event information shown in FIG. 10 has items such as an event ID, a provision period, an event content, and a benefit content. The event ID is information for uniquely identifying an event. The provision period is information indicating a period during which an event game can be provided. The event content is information indicating the content of the event game that can be provided. Here, a competitive game (quest) or a lottery game that has a limited provision period is set as the event game. The benefit content is information indicating the benefit content that can be acquired in the event game. Here, items and characters are set as the benefit that can be acquired, and the number of items and characters is also set as shown in parentheses in the figure.

[0080] When an event providing section 202 of the server device 20 acquires event games for this month that can be provided to a monthly billing user who has paid the game fee for this month, the event providing section 202 updates the event providing information for the user set in the user information stored in the user information storage section 222, and registers the acquired event games for this month that can be provided.

[0081] Next, the event re-provision unit 203 of the server device 20 acquires monthly billing user information from the user information stored in the user information storage unit 222, and, by referring to the acquired monthly billing user information, determines whether the monthly billing user who has paid the game fee for this month is also a user who paid the game fee for last month (step S17).

[0082] If it is determined that the monthly billing user who has paid this month's game fee is a user who has not paid last month's game fee (i.e., a user who started paying monthly fees this month), the process proceeds to step S20, which will be described later. On the other hand, if it is determined that the monthly billing user who has paid this month's game fee is a user who has also paid last month's game fee, the process proceeds to the next step S18.

[0083] Next, when it is determined that the monthly billing user who has paid the game fee for this month is also a user who has paid the game fee for last month (step S17: YES), the event re-provision unit 203 of the server device 20 determines whether there are any event games from last month that were provided to other users who logged in during the period of the last month when the user did not log in (step S18).

[0084] Specifically, the event re-provision unit 203 of the server device 20 refers to the log history information shown in Fig. 7 and the event information shown in Fig. 10 to identify last month's event games that were provided during a period of the last month when the monthly billing user, who has paid the last month's game fee and the current month's game fee, did not log in. Then, if at least one event game can be identified, it means that the corresponding event game for last month exists.

[0085] If it is determined that there is no event game from the previous month that was provided to other users who logged in during the period of the previous month when the user did not log in, the process proceeds to step S20, which will be described later. On the other hand, if it is determined that there is an event game from the previous month that was provided to other users who logged in during the period of the previous month when the user did not log in, the process proceeds to the next step S19.

[0086] Next, if the event re-provision unit 203 of the server device 20 determines that there is an event game from last month that was provided to other users who logged in during a period of the last month when the user did not log in (step S18: YES), the event re-provision unit 203 re-provides the same event game as last month's event game to monthly billing users who have paid the game fee for last month and the game fee for this month (step S19).

[0087] Specifically, first, the event re-provision unit 203 of the server device 20 updates the event provision information for the user set in the user information stored in the user information storage unit 222, and additionally registers the same event game as the existing event game for last month as an event game for this month that can be provided.

[0088] In this embodiment, the provision period of the additionally registered event game is set to one month after the provision period of the event game that existed last month. It is not limited to this, and the provision period of the additionally registered event game can also be set to one month within the current month. In this case, the provision of the event game may end when the user plays the event game. It can also be set to a fixed date within the current month.

[0089] Next, the notification unit 205 of the server device 20 notifies the monthly billing user of an event list that lists the event games available for the current month, based on the event provision information set in the user information stored in the user information storage unit 222 (step S20).

[0090] In other words, if it is determined that a monthly billing user who has paid this month's game fee is also a user who has paid last month's game fee (step S17: YES), and if it is determined that there are last month's event games that were provided to other users who logged in during the period of last month when the monthly billing user who paid last month's game fee and this month's game fee did not log in (step S18: YES), the notification unit 205 of the server device 20 will notify the event list that displays the event games for this month set in the event information stored in the event information storage unit 224 and the existing event games for last month.

[0091] On the other hand, if it is determined that a monthly billing user who has paid this month's game fee is a user who has not paid last month's game fee (step S17: NO), or if it is determined that there are no last month's event games that were provided to other users who logged in during the period of last month when the monthly billing user who has paid last month's game fee and this month's game fee did not log in (step S18: NO), the notification unit 205 of the server device 20 will notify an event list that lists only the event games for this month that are set in the event information stored in the event information storage unit 224.

[0092] In this embodiment, the notification is performed by a game screen as shown in Fig. 11. Therefore, when the display control unit 206 of the server device 20 is requested by the notification unit 205 of the server device 20 to execute screen display control, the display control unit 206 performs control to display the game screen on the screen display unit 160 of the client terminal 10.

[0093] 11 is an image diagram showing an example of a game screen. This game screen 500 displays an event list 501 that displays a list of event games for this month that can be provided to monthly fee paying users. Here, assuming that this month is September, the event games for September set in the event information stored in the event information storage unit 224 and the same event games as the August event games that were provided to other users who logged in during the period in August when the monthly fee paying user who paid the September game fee did not log in are displayed in a list.

[0094] As described above, according to the information processing system 1 of this embodiment, a monthly billing user can pay this month's game fee after the previous month's game fee, and be provided with the same event game as last month's event game during this month. This can motivate monthly billing users who have paid last month's game fee to pay this month's game fee. This can increase the motivation of monthly billing users who want to continuously receive benefits by paying the monthly fee.

[0095] Example 1 12 is a diagram explaining a specific example 1 when the same event game as last month's event game is provided again this month. Here, it is assumed that last month was "August" and this month is "September", and that a monthly paying user has paid the game fees for August and September.

[0096] In this specific example 1, as shown in Fig. 12, "Event A" and "Event B" are set as event games for August. A monthly fee-paying user logs in to the fighting game when "Event A" is provided and plays "Event A", but is unable to log in to the fighting game when "Event B" is provided, and is therefore unable to play "Event B".

[0097] If August is in this state, then in the following month of September, the event re-provision unit 203 will provide "Event B," which was provided to other users who logged in during the period in August when the user did not log in, again to the monthly billing user who did not log in within the month of September.

[0098] As a result, even if a user is unable to log in to the competitive game during August and is unable to play "Event B," in September, he or she will be able to challenge the same event game as "Event B" for August that was offered to other users during the period when he or she was not logged in. This gives users who have paid the game fee for August an incentive to pay the game fee for September, thereby increasing users' motivation to receive continuous benefits by paying the game fee at regular intervals.

[0099] Example 2 13 is a diagram explaining specific example 2 when the same event game as last month's event game is provided again this month. Here, as in the above-mentioned specific example 1, it is assumed that last month was "August" and this month is "September", and that the monthly fee paying user has paid the game fees for August and September.

[0100] In this specific example 2, as shown in FIG. 13, a state is shown in which "Event A" is set as the event game for August. Unlike the above-mentioned specific example 1, this "Event A" is set as the event game for August that can be played over multiple days. Here, it is assumed that it can be played over three days. The monthly paying user logs in when "Event A" is provided on the first day of the three days, but is unable to log in when "Event A" is provided on the second and third days.

[0101] If this is the case in August, then in the following month of September, the event re-provision unit 203 will provide the same event game as "Event A" that was playable over those three days again to the monthly paying users who did not log in for just two days out of the three days (the second and third days) during which they did not log in, within the month of September.

[0102] As a result, even if a user is unable to log in to the competitive game during August and is unable to play part of "Event A," in September, the user will be able to challenge the same event game as "Event A" in August that was provided to other users for the number of days that the user was unable to log in. This gives users who have paid the game fee for August an incentive to pay the game fee for September, thereby increasing the user's motivation to receive continuous benefits by paying the game fee at regular intervals.

[0103] Example 3 14 is a diagram explaining specific example 3 when the same event game as last month's event game is provided again this month. Here, as in the above-mentioned specific example 1, it is assumed that last month was "August" and this month is "September", and that the monthly fee paying user has paid the game fees for August and September.

[0104] In this specific example 3, as shown in FIG. 14, the first half of "Event A" is set as the event game for August, and the second half of "Event A" is set as the event game for September. In other words, unlike the above-mentioned specific examples 1 and 2, this "Event A" is set as an event game that can be played over multiple days spanning August and September. Here, it is assumed that the game was playable over five days spanning August and September, and the first three days (three days from the 1st to the 3rd) are set as the event game for August, and the last two days (two days from the 4th to the 5th) are set as the event game for September. In addition, the state is shown in which monthly billing users could not log in during the provision period of "Event A" from the 1st to the 3rd day of the first half of the five days.

[0105] If August is in this state, then in the following month of September, the event re-provision unit 203 will provide the same event game as "Event A" that was playable over those five days to monthly fee paying users who did not log in during the first three days of August (only the three days from the 1st to the 3rd) for which they did not log in during those five days, within one month of September. Here, the first three days are provided again consecutively after the last two days of September (the two days from the 4th to the 5th) of the multiple days.

[0106] As a result, even if a user does not log in for the August portion of "Event A" that spans August and September, in September, the user will be able to challenge the same event game as "Event A" that was provided to other users for the number of days in August that the user did not log in. This gives users who have paid the game fee for August an incentive to pay the game fee for September, thereby increasing the user's willingness to continuously receive benefits by paying the game fee at regular intervals.

[0107] [Other embodiments] The above-described embodiments are provided to facilitate understanding of the present invention, and are not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit of the present invention, and equivalents thereof are also included in the present invention. In particular, the following embodiments are also included in the present invention.

[0108] <Event Re-Provision Department> In the above embodiment, an example was described in which the event re-providing unit 203 of the server device 20 re-provides, within the current month, an event game that is the same as the event game from last month that was provided to another user who logged in during a non-login period during the previous month, but the present invention is not limited to this. An event game that is the same as or related to a user-specific event game that was provided to the user during a non-login period during the previous month and that was not provided to other users may be provided again within the current month.

[0109] For example, if a monthly billing user who has paid the game fee for both last month and this month is unable to complete last month's event game that was provided during the period in which he or she logged in last month, regardless of whether or not he or she played the event game, the event re-provision unit 203 of the server device 20 may provide the same event game that he or she was unable to complete again within the current month.

[0110] In this case, in the process of step S18 of the flowchart shown in Fig. 5, it is determined whether or not there are any event games from last month that were provided during the login period of the previous month and that could not be cleared. That is, the event re-provision unit 203 of the server device 20 identifies, based on the event clear information set in the user information shown in Fig. 6, the event games from last month that were provided during the login period of the previous month by a monthly billing user who has paid the game fee for last month and the game fee for this month and that could not be cleared. Then, if at least one event game can be identified, it is determined that a corresponding event game from last month exists.

[0111] In addition, in the above-described embodiment, an example was given of a case in which the event re-provision unit 203 of the server device 20 re-provisions an event game that is the same as last month's event game within the current month, but the present invention is not limited to this.

[0112] For example, the event re-providing unit 203 of the server device 20 can provide an event game related to an event game from last month during the current month. The event game related to the event game from last month may be an event game that has some kind of relationship between the event from last month and an event that will be provided again during the current month.

[0113] Specifically, if "Character X" was obtained as a bonus by clearing last month's event game "Quest X," it is possible to provide a different type of "Quest Y" within the current month. However, by clearing "Quest Y," the same "Character X" can be obtained as a bonus, creating a relationship between the two.

[0114] Also, if a player wins last month's event game, "Lottery Game N," and thus receives "Character N" as a bonus, it is possible to provide a "Lottery Game M," which is a different type from "Lottery Game N," within the current month. However, the two games are related to each other by allowing the player to win "Lottery Game M" and thus receive the same "Character N" as a bonus.

[0115] Also, if "Character X" can be acquired as a bonus by clearing last month's event game "Quest X," it is possible to provide "Lottery Game Z," a different game type from "Quest X," within the current month. However, the same "Character X" can be acquired as a bonus by winning "Lottery Game Z," making the two related.

[0116] In addition, in the above-described embodiment, an example was given of a case in which the event re-provision unit 203 of the server device 20 re-provisions an event game that is the same as or related to last month's event game within the current month, but the present invention is not limited to this.

[0117] For example, the event re-providing unit 203 of the server device 20 can provide, not only last month's event game, but also an event game that is the same as or related to an event game from several months ago, during the current month.

[0118] <Benefits Granting Department> In the above embodiment, a case where a login bonus is used as an example of a reward is described, but the present invention is not limited to this. For example, the present invention can also be applied to a case where a character or an item is given as a reward for clearing a quest in a battle game.

[0119] In addition, in the above-mentioned embodiment, the bonus granting unit 204 can also grant a bonus that is more advantageous to a monthly billing user who has paid last month's game fee, the earlier during the last month the user performs the operations required to pay this month's game fee.

[0120] For example, if a monthly billing user who has paid the August game fee performs the renewal procedure and fee payment required to pay the September game fee in August, the earlier the user performs the procedure, the rarer the characters, items, etc. will be given as a login bonus for September. It is also possible to increase the number of characters and items given. This can motivate users who have paid last month's game fee to pay this month's game fee early, further increasing the willingness of users to continuously receive benefits by paying game fees at regular intervals.

[0121] <Notification section> In the above embodiment, the notification unit 205 may issue a notification prompting payment of the current month's game fee or renewal procedure as the last day of the previous month approaches. Similarly, the notification unit 205 may issue a notification prompting payment of the next month's game fee or renewal procedure as the last day of the current month approaches. At that time, the notification may be issued to the effect that the earlier the game fee payment or renewal procedure is performed, the more advantageous benefits will be given to monthly billing users. [Explanation of symbols]

[0122] 1. Information Processing Systems 10 Client Terminal 20 Server equipment 50 Computers 51 CPU 52 RAM 53 ROM 54 Communication Interface 55 Input Devices 56 Display device 57 External Interface 58 HDD 100 Client control section 101 Request sending unit 102 Response receiver 120 Client Memory 140 Client Communication Section 150 Operation reception section 160 Screen display section 200 Server control unit 201 Game control unit 202 Events Department 203 Event Re-Provision Department 204 Benefits Granting Department 205 Notification Department 206 Display control unit 220 Server memory 221 Character information storage unit 222 User information storage unit 223 Login Bonus Information Storage Unit 224 Event information storage unit 240 Server Communication Department 500 game screens 501 Event List B Bus Line N Network

Claims

1. a user information storage unit that stores user information including information for identifying whether or not a user has paid a game fee set at a fixed period; an event providing section that provides, to a user who has paid a game fee for a previous fixed period, an event game that has become playable as a result of the user having paid the game fee for the previous fixed period, during the previous fixed period; an event re-providing unit for providing, to a user who has paid a game fee for a previous fixed period and also paid a game fee for a current subsequent fixed period, an event game that is the same as or related to the event game that became playable as a result of the user having paid the game fee for the previous fixed period, during the current fixed period; An information processing device comprising:

2. 2. The information processing device according to claim 1, the event providing unit, when a user who has paid a game fee for a previous fixed period logs in within the previous fixed period, provides the logged-in user with an event game that has become playable as a result of the user having paid the game fee for the previous fixed period; the event re-providing unit, when a user who has paid a game fee for the previous fixed period and also paid a game fee for the current fixed period does not log in within the previous fixed period, re-provides, within the current fixed period, an event game that is the same as or related to the event game that was provided during the period in which the user did not log in during the previous fixed period; 23. An information processing apparatus comprising:

3. 3. The information processing device according to claim 2, the event providing unit provides the event game that can be played over a plurality of days to a logged-in user who has paid a game fee for a previous fixed period and has logged in within the previous fixed period; the event re-provision unit, when a user who has paid the game fee for the previous fixed period and also paid the game fee for the current fixed period does not log in on any one of the multiple days, re-provisions, within the current fixed period, an event game that is the same as or related to the event game that the user who has paid the game fee for the previous fixed period has been able to play over multiple days, for the number of days on which the user did not log in on any one of the multiple days; 23. An information processing apparatus comprising:

4. 4. The information processing device according to claim 2, the event providing unit, when a user who has paid a game fee for a previous fixed period logs in within the previous fixed period, provides the logged-in user with an event game that has become playable as a result of the user having paid the game fee for the previous fixed period, for multiple days spanning the previous fixed period and the current fixed period; the event re-provision unit, when a user who has paid the game fee for the previous fixed period and also paid the game fee for the current fixed period does not log in on any day included in the previous fixed period among the multiple days, re-provisions, within the current fixed period, an event game that is the same as or related to the event game that was playable over multiple days, for the number of days on which the user who has paid the game fee for the previous fixed period did not log in on any day included in the previous fixed period among the multiple days; 23. An information processing apparatus comprising:

5. An information processing device according to any one of claims 1 to 4, the event providing unit, when a user who has paid a game fee for a previous fixed period logs in within the previous fixed period, provides the logged-in user with an event game that has become playable as a result of the user having paid the game fee for the previous fixed period; the event re-provision unit, when a user who has paid the game fee for the previous fixed period and also paid the game fee for the current fixed period is unable to complete the event game that was provided during the period in which the user logged in during the previous fixed period, provides again, within the current fixed period, an event game that is the same as or related to the event game that the user was unable to complete; 23. An information processing apparatus comprising:

6. An information processing device according to any one of claims 1 to 5, a bonus provision unit that provides a bonus that is more advantageous to a user who has paid a game fee for a previous fixed period and who performs an operation required for paying a game fee for a current fixed period earlier within the previous fixed period; An information processing device comprising:

7. Computer, a user information storage means for storing user information including information for identifying whether or not a user has paid a game fee set at a fixed period; an event providing means for providing, to a user who has paid a game fee for a previous fixed period, an event game that has become playable as a result of the user having paid the game fee for the previous fixed period, during the previous fixed period; an event re-provision means for providing, to a user who has paid a game fee for a previous fixed period and also paid a game fee for a current subsequent fixed period, an event game that is the same as or related to the event game that became playable as a result of the user having paid the game fee for the previous fixed period, within the current fixed period; A program to function as a

Images