Game Management System
The game management system addresses the limitation of individual game payments by granting in-game currency across multiple games, enhancing user motivation and engagement through a unified payment system.
Patent Information
- Application Number
- JP2026206675
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-09-15
- Publication Date
- 2026-11-19
AI Technical Summary
Conventional game payment systems require users to pay individually for each game, limiting their ability to play multiple games advantageously and reducing motivation to play games outside their paid subset.
A game management system that receives charges from users and grants in-game currency across multiple games, calculated based on the amount of charges, allowing users to play each game more advantageously and increasing motivation to play a variety of games.
Users can earn in-game currency across multiple games, gaining an advantage and enhancing their motivation to play a broader range of games, thereby improving user engagement and enjoyment.
Smart Images

Figure 2026183102000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a game management system.
Background Art
[0002] There are so-called social games that are provided to mobile terminals such as users' smartphones and allow interaction with other users via an internet line. Such social games introduce a payment system that allows users to obtain advantageous items and characters by making payments.
[0003] Furthermore, an item lottery function that allows users to randomly obtain items usable in games is known (see, for example, Patent Document 1).
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of Invention
Problems to be Solved by the Invention
[0005] In conventional games, the payment system is independent for each game, and users make payments on a per-game basis. When a user wishes to play multiple games more advantageously than others, the user is required to make a payment for each individual game. For users, concentrating payments on a single game allows them to play that game more advantageously than distributing payments across multiple games, so the games users play are limited to a subset of games for which they have made payments, and motivation to play games other than the paid games is unlikely to arise.
[0006] This invention was made in view of these circumstances, and its purpose is to improve the motivation for users to play multiple games by charging for them. [Means for solving the problem]
[0007] According to the present invention, a game management system is provided which includes a reception unit and a granting unit, wherein the reception unit receives charges from users, and the granting unit grants the user in-game currency for each of multiple games, which is calculated based on the amount of the charges.
[0008] This configuration allows users to earn in-game currency across multiple games, giving them an advantage over others in each game and increasing their motivation to play multiple games.
[0009] The following are examples of various embodiments of the present invention. The embodiments shown below are combinable with each other. Furthermore, each feature independently constitutes the invention.
[0010] Preferably, the plurality of games are included in a predetermined group, and the reception unit accepts charges from the user for the predetermined group. Preferably, the plurality of games are included in a predetermined group, and the reception unit accepts charges from the user for any one of the games included in the predetermined group. Preferably, the granting unit grants the user the charge amount and the in-game currency for each of the plurality of games, which is converted based on a coefficient for each of the plurality of games. Preferably, the system further includes a target amount setting unit, which sets a target amount for each of the plurality of games from the charge amount received from the user to be used for conversion into in-game currency, and the granting unit grants the user the in-game currency for each of the plurality of games, which is converted based on the target amount for each of the plurality of games set by the target amount setting unit. Preferably, the system further comprises a first storage unit and a second storage unit, the first storage unit storing history information of charges received from the user, the second storage unit storing history information of the granting of in-game currency for each of the multiple games to the user based on the charges received from the user, and the target amount setting unit sets at least a portion of the amount of charges received from the user that has not been used to grant in-game currency to the user for each of the multiple games as the target amount for each of the multiple games, based on the information stored in the first and second storage units. Preferably, for a game that started being offered after the user's charge, the target amount setting unit calculates the cumulative charge amount over a predetermined period based on the charge history information and sets the target amount. Preferably, the first storage unit stores the predetermined period for each of the multiple games. Preferably, the second storage unit has an upper limit set for the in-game currency for each of the multiple games. [Brief explanation of the drawing]
[0011] [Figure 1] This diagram shows an overview of the game management system 100 according to the first embodiment of the present invention. [Figure 2] This is a block diagram showing the hardware configuration of the management server 30. [Figure 3] Block diagram showing the functional configuration of the game management system 100. [Figure 4] Figure 4A shows the table configuration of the billing history storage unit 42. Figure 4B shows the table configuration of the currency information storage unit 44. [Figure 5] This figure shows an overview of the game management system 200 according to the second embodiment. [Figure 6] Functional configuration of game management system 200. (Box of cards.) [Figure 7] Figure 7A shows the table configuration of the billing history storage unit 142. Figure 7B shows the table configuration of the currency information storage unit 144. [Figure 8] This diagram illustrates the relationship between the amount charged and the amount awarded in the game management system 200. [Figure 9] This diagram shows an overview of the game management system 300 according to the third embodiment. [Figure 10] Block diagram showing the functional configuration of the Game Management System 300. [Figure 11] Figure 11A shows the table configuration of the billing history storage unit 242. Figure 11B shows the table configuration of the currency information storage unit 244. [Modes for carrying out the invention]
[0012] <1. First Embodiment> (1.1. Overview of Game Management System 100) Referring to Figure 1, an overview of the game management system 100 according to the first embodiment will be described. As shown in Figure 1, the game management system 100 comprises a management server 30 and a game provision system 50, and is configured to communicate with a user terminal 10. The game provision system 50 is implemented by multiple server devices.
[0013] The user terminal 10 is implemented by a mobile terminal such as a smartphone owned by a game user (hereinafter simply referred to as a user). The management server 30 is a server that accepts charges from users and manages charge information. The game providing system 50 is configured to be capable of providing a plurality of games. The game providing system 50 classifies and manages the plurality of games into respective predetermined groups.
[0014] For the games provided by the game providing system 50, the user designates any one of a plurality of classified groups to make a payment. The management server 30 accepts the charge from the user, and grants the user the in-game currency for each of the plurality of games in the group designated by the user, which is converted based on the amount of the charge and a conversion coefficient (hereinafter also simply referred to as a coefficient) set for each game. Note that when all of the plurality of games belong to the same group, the management server 30 may skip the process of the user designating a group.
[0015] With such a configuration, since the charge from the user is granted as in-game currency in a plurality of games, it becomes possible for the user to play each of the plurality of games more advantageously than others, and the motivation for the user to play the plurality of games can be improved.
[0016] Here, the group is, for example, a company that provides games, and the games provided by the company may be classified into the same group. By classifying a plurality of games released by one company into the same group, the user can play each of the plurality of games released by that company more advantageously than others by paying for the group, and the motivation for the user to play the plurality of games can be improved.
[0017] (1.2. Hardware Configuration of Management Server 30) The hardware configuration of the management server 30 will be described with reference to Figure 2. Note that since the game providing system 50 can be implemented by the configuration included in the management server 30, the description thereof will not be repeated.
[0018] Figure 2 is a block diagram showing the hardware configuration of the management server 30 according to the present embodiment. The management server 30 includes a main control unit 31 that governs the overall operation of the management server 30, a main storage unit 32 used as a work area or the like when the main control unit 31 executes various programs, and an auxiliary storage unit 33 in which various programs, various data, and the like are stored in advance.
[0019] Further, the management server 30 includes a communication unit 34 that is connected to other information processing apparatuses such as the user terminal 10 and the game providing system 50 via a communication line, and transmits and receives various data to and from the other information processing apparatuses and the like. Further, the management server 30 may be provided with an operation input unit 35 that is configured with a keyboard, a mouse, and the like to receive input of various operations, and a monitor 36 such as a liquid crystal display device that displays various images.
[0020] The main control unit 31, the main storage unit 32, the auxiliary storage unit 33, the communication unit 34, the operation input unit 35, and the monitor 36 are electrically connected to each other via a system bus 37. Accordingly, the main control unit 31 can perform access to the main storage unit 32 and the auxiliary storage unit 33, grasp of the operation state for the operation input unit 35, display of images on the monitor 36, transmission and reception of various data to and from other information processing apparatuses and the like via the communication unit 34, and the like, respectively.
[0021] (1.3. Functional Configuration of Game Management System 100) The functional configuration of the game management system 100 will be described with reference to Figure 3. As described above, the game management system 100 includes the management server 30 and the game providing system 50.
[0022] (1.3.1. Management Server 30) As shown in Figure 3, the management server 30 includes a reception unit 41, a charge history storage unit 42, and a granting unit 43. The reception unit 41 and the granting unit 43 are implemented as functions of the main control unit 31. The charge history storage unit 42 is implemented as a function of the auxiliary storage unit 33.
[0023] The reception unit 41 receives the charge from the user and registers the charge history information in the charge history storage unit 42.
[0024] The billing history storage unit 42 stores billing history information received from the user. The billing history storage unit 42 includes a billing history table T1 and an award coefficient table T2. The configuration of the billing history table T1 and the award coefficient table T2 will be described in detail later.
[0025] The granting unit 43 refers to the billing history table T1 and the granting coefficient table T2, and grants the user the in-game currency for each of the multiple games, which is calculated based on the user's billing amount. Details on the granting of in-game currency based on billing amount will be described later. (1.3.2. Game Provision System 50)
[0026] The game provision system 50 includes a currency information storage unit 44 and a provision unit 47. The currency information storage unit 44 is implemented as a function of the auxiliary storage unit 33. The provision unit 47 is implemented as a function of the main control unit 31.
[0027] The currency information storage unit 44 stores historical information of in-game currency granted by the granting unit 43. The currency information storage unit 44 includes a currency granting table T3. The configuration of the currency granting table T3 will be described in detail later. The provisioning unit 47 is configured to provide multiple games to the user.
[0028] The above-described functional configuration can be realized by the CPU (Central Processing Unit) implemented as the main control unit 31 executing a program, or it may be realized by hardware.
[0029] If implemented by executing a program, the program may be stored in the auxiliary storage unit 33, or in a non-temporary recording medium readable by a computer. Alternatively, the program may be read from an external storage device and implemented through so-called cloud computing. Furthermore, if implemented by hardware, it can be implemented by various circuits such as ASICs, SOCs, FPGAs, or DRPs.
[0030] (1.4. Table configuration of billing history storage unit 42 and currency information storage unit 44) Referring to Figures 4A and 4B, the table configuration of the billing history storage unit 42 and currency information storage unit 44 will be described. The billing history storage unit 42 includes a billing history table T1 and an allocation coefficient table T2. The currency information storage unit 44 includes a currency allocation table T3.
[0031] (1.4.1. Billing History Table T1) The billing history table T1 is a table that stores the history of user billing. As shown in Figure 4A, the billing history table T1 has a billing ID column, a user ID column, a billing group column, a billing amount (yen) column, and a billing date column. The billing ID column holds a billing ID to uniquely identify the record in the billing history table T1. The user ID column holds a user ID to uniquely identify the user who made the billing.
[0032] The billing group column holds the group name specified by the user at the time of billing. In the game management system 100, multiple games provided by the game provision system 50 are classified into predetermined groups, and the system is configured so that users can specify a group when making a bill.
[0033] The "Charge Amount (yen)" column holds the amount charged by the user (hereinafter also referred to as "Charge Amount"). The "Charge Date" column holds the date on which the user made the charge.
[0034] In this way, the billing history table T1 stores the history of user billing, and the reception unit 41 receives billing requests from users and registers them in the billing history table T1.
[0035] (1.4.2. Assignment Coefficient Table T2) The Grant Coefficient Table T2 is a table that stores a conversion coefficient for converting the amount charged by a user into in-game currency for each game provided by the game provision system 50. The Grant Coefficient Table T2 has a Game ID column, a Game Name column, a Game Group column, and a Coefficient column. The Game ID column holds a Game ID for uniquely identifying multiple games provided by the game provision system 50. The Game Name column holds the name of the game.
[0036] The Game Group column holds the name of the group to which the game belongs. The Coefficient column holds the conversion coefficient used when the game is converted from the amount charged.
[0037] The granting unit 43 refers to the billing history table T1 and the granting coefficient table T2, and registers the in-game currency for each of the multiple games, which is converted based on the user's billing amount, in the currency granting table T3.
[0038] (1.4.3. Currency Grant Table T3) The currency grant table T3 is a table that stores historical information of in-game currency granted by the granting unit 43. As shown in Figure 4B, the currency grant table T3 has a No column, a billing ID column, a grant target game column, a currency grant amount (yen) column, and an addition date column.
[0039] The No column holds a sequential number to uniquely identify the record in the currency grant table T3. The Charge ID column is a foreign key to the Charge ID column in the Charge History table T1 and holds the Charge ID associated with the granting of in-game currency by the granting unit 43.
[0040] The "Games to be Granted" column holds the name of the game in which the granting unit 43 granted in-game currency. The "Currency Granted Amount (yen)" column holds the amount of in-game currency granted by the granting unit 43 based on the user's billing amount and conversion factor. The "Addition Date" column holds the date on which the granting unit 43 granted the in-game currency.
[0041] Furthermore, in-game currency is granted in units of currency (or items equivalent to currency) within the target game. Therefore, the currency grant table T3 may include a column that holds the amount (or the number of items equivalent to currency) in units of in-game currency corresponding to each game.
[0042] (1.4.4. Flow of in-game currency distribution) The following explanation will describe the granting of in-game currency by the granting unit 43, using the case where the charge ID is 3 (record R1 in the charge history table T1) as an example. When the receiving unit 41 receives a charge of 10,000 yen from a user, it registers record R1 with charge ID=3 in the charge history table T1.
[0043] The granting unit 43 refers to the billing history table T1 and the granting coefficient table T2 and registers the amount of in-game currency to be granted based on the billing amount in the currency granting table T3. Here, since the billing with billing ID=3 is billed to group A (see record R1 in billing history table T1), the granting unit 43 refers to the granting coefficient table T2 and obtains the conversion coefficient for the game belonging to group A.
[0044] In the allocation coefficient table T2, the conversion coefficients for games A1, A2, and A3 belonging to group A are 1, 1, and 0.5, respectively (see record R2 in allocation coefficient table T2). Therefore, the allocation unit 43 multiplies the charge amount of 10,000 yen by the conversion coefficient to 10,000 yen, 10,000 yen, and 5,000 yen, which are allocated to the user as in-game currency in games A1, A2, and A3 belonging to group A, and registers this in the currency allocation table T3 (see record R3 in currency allocation table T3 / corresponds to Figure 1).
[0045] As described above, the game management system 100 according to this embodiment includes a reception unit 41 and a granting unit 43. The reception unit 41 receives charges from users, and the granting unit 43 grants the user the in-game currency for each of the multiple games, which is calculated based on the amount of the charges.
[0046] This configuration allows users to earn in-game currency across multiple games, giving them an advantage over others in each game and increasing their motivation to play multiple games. Furthermore, including many games within a group allows users to enjoy a variety of games within that group, leading to longer-term user engagement.
[0047] <2. Second Embodiment> Referring to Figures 5 to 8, an overview of the game management system 200 according to the second embodiment will be described. The following description will focus on the differences from the first embodiment.
[0048] (2.1. Overview of Game Management System 200) Referring to Figure 5, the overview of the game management system 200 will be explained. As shown in Figure 5, the game management system 200 differs from the first embodiment in that the user pays a fixed monthly fee to the management server 130.
[0049] The management server 130, which receives monthly subscription payments from users, grants in-game currency each month for multiple games provided by the game provision system 150. On the other hand, for new games released after the user's subscription payments have started, the in-game currency granted is based on the sum of the amount paid in the month of release and the amount of money paid up to that month.
[0050] (2.2. Functional Configuration of Game Management System 200) Referring to Figure 6, the functional configuration of the game management system 200 will be explained. The game management system 200 comprises a management server 130 and a game provisioning system 150.
[0051] As shown in Figure 6, the management server 130 includes a reception unit 141, a billing history storage unit 142, a granting unit 143, a provisioning unit 147, and a target amount setting unit 145. The target amount setting unit 145 sets the target amount to be used for conversion into in-game currency for each of the multiple games from the billing amounts received from the user.
[0052] Specifically, the target amount setting unit 145 sets the monthly charge amount as the target amount for games that have already been released when the user starts paying. On the other hand, for games that are released after the user starts paying, the target amount is set to the sum of the charge amount for the month of release and the accumulated charge amount up to the month of release.
[0053] The granting unit 143 grants in-game currency to each of the multiple games based on the target amount set by the target amount setting unit 145, and registers it in the currency information storage unit 144 of the game provision system 150.
[0054] (2.3. Table configuration of billing history storage unit 142 and currency information storage unit 144) Referring to Figures 7A and 7B, the table configurations of the billing history storage unit 142 and the currency information storage unit 144 will be described. The billing history storage unit 142 includes a billing history table T11, an allocation coefficient table T12, and a release condition table T13. The currency information storage unit 144 includes a currency allocation table T14.
[0055] (2.3.1. Billing History Table T11) As shown in Figure 7A, the billing history table T11 has a billing start date column instead of the billing date column in the billing history table T1 in Figure 4. The billing start date column holds the date on which the user's recurring billing began.
[0056] (2.3.2. Release Conditions Table T13) The release conditions table T13 stores, for each game provided by the game provision system 150, the release date of the game and the cumulative period of charges that will qualify for in-game currency at the time of release. The release conditions table T13 has columns for Game ID, Game Name, Release Date, and Cumulative Charge Period (Months).
[0057] The Release Date column holds the date the game is released. The Billing Cumulative Period (Months) column holds the cumulative period of pre-release billing (corresponding to the "predetermined period" in the claims) that is set as the basis for conversion of in-game currency when the game is released.
[0058] (2.3.3. Flow of in-game currency distribution) The following explanation of the granting of in-game currency by the granting unit 143 will be given using the case where the charge ID is 1 (record R11 in the charge history table T11) as an example. When the reception unit 141 receives a request from a user to start a fixed-rate charge of 3,000 yen, it registers record R11 with charge ID = 1 in the charge history table T11.
[0059] The target amount setting unit 145 sets the target amount to be used for conversion into in-game currency for each of the multiple games included in the group of games to be charged, from the amount of charges received from the user.
[0060] At the time record R11 is registered, games A1 to A3 have already been released (see record R12 in release condition table T13). Therefore, the target amount setting unit 145 sets the fixed charge amount of 3000 yen as the amount to be converted into in-game currency.
[0061] The granting unit 143 grants in-game currency to games A1 to A3 based on the target amount set by the target amount setting unit 145 and the conversion coefficients stored in the coefficient column of the granting coefficient table T12, and registers this information in the currency granting table T14. In this way, each time a monthly fixed-rate charge is made, the history information of the granted in-game currency is registered in the currency granting table T14 (record R14 of the currency granting table T14).
[0062] In contrast, when game A4 is released after the start of fixed-rate billing with billing ID=1 (see record R13 in release condition table T13), the target amount setting unit 145 refers to release condition table T13 and obtains the cumulative billing period for game A4. Then, based on the fixed-rate billing amount in the month game A4 is released (3000 yen) and the billing amount corresponding to the cumulative period for game A4 (2 months) (6000 yen), it sets the target amount for conversion to in-game currency (9000 yen). The granting unit 143 grants in-game currency for game A4 based on the target amount set by the target amount setting unit 145 and the conversion coefficient (1) for game A4 held in the coefficient column of granting coefficient table T12, and registers the history information in currency granting table T14 (corresponding to record R15).
[0063] Referring to Figure 8, the relationship between the amount charged and the amount awarded in the game management system 200 described above will be explained. As shown in Figure 8, for users who started paying in January, for existing games A1 to A3, the amount obtained by multiplying the fixed-rate charge by a conversion factor is awarded as in-game currency each month. In contrast, for game A4, which was released after the user's fixed-rate payment started, a portion of the charges made before the release (i.e., the amount for which in-game currency was not awarded) is also subject to conversion into in-game currency.
[0064] Thus, the game management system 200 further includes a target amount setting unit 145, which sets the target amount to be used for conversion into in-game currency from the fixed-rate charges received from users. For games that started being offered after the user began fixed-rate charges, the target amount setting unit 145 calculates the cumulative charges over a predetermined period based on the charge history information and sets the target amount. The granting unit 143 grants the in-game currency converted based on the previously set target amount.
[0065] This configuration ensures that users receive in-game currency equivalent to the amount they have accumulated through previous in-game purchases each time a new game is released, thus motivating them to play new games. Furthermore, because it is a subscription-based system, an increase in the number of users utilizing the system increases its ability to attract new customers, thus motivating new users to join.
[0066] <3. Third Embodiment> Referring to Figures 9 to 11, an overview of the game management system 300 according to the third embodiment will be described.
[0067] (3.1. Overview of Game Management System 300) Referring to Figure 9, the overview of the game management system 300 will be explained. As shown in Figure 9, the game management system 300 differs from the above embodiment in that it does not have a management server.
[0068] The user makes a payment to the game provision system 250, specifying the game. The game provision system 250 grants in-game currency to the game specified by the user and to other games within the group to which that game belongs.
[0069] (3.2. Functional Configuration of Game Management System 300) Referring to Figure 10, the functional configuration of the game management system 300 will be explained. The game management system 300 includes a game provision system 250. As shown in Figure 10, the game provision system 250 includes a reception unit 241, a billing history storage unit 242, a granting unit 243, a currency information storage unit 244, and a provision unit 247.
[0070] (3.3. Table configuration of billing history storage unit 242 and currency information storage unit 244) Referring to Figures 11A and 11B, the table configurations of the billing history storage unit 242 and the currency information storage unit 244 will be described. The billing history storage unit 242 includes a billing history table T21 and an allocation ratio table T22. The currency information storage unit 244 includes a currency allocation table T23.
[0071] (3.3.1. Billing History Table T21) As shown in Figure 11A, the billing history table T21 has a billing game column instead of the billing group column in the billing history table T1 in Figure 4. The billing game column holds the name of the game to which the user is billed.
[0072] (3.3.2. Allocation Ratio Table T22) The allocation ratio table T22 has a ratio column instead of a coefficient column in the allocation coefficient table T2 shown in Figure 4. The ratio column holds the conversion ratio used when converting the amount charged to in-game currency between the game specified by the user at the time of payment and that game.
[0073] (3.3.3. Flow of in-game currency distribution) The following explanation of the granting of in-game currency by the granting unit 243 will be given using the case where the charge ID is 2 (record R21 in the charge history table T21) as an example. When the receiving unit 241 receives a charge of 6,000 yen from a user, it registers record R21 with charge ID=2 in the charge history table T21.
[0074] The granting unit 243 refers to the billing history table T21 and the granting ratio table T22 and registers the amount of in-game currency to be granted based on the billing amount in the currency granting table T23. Here, the billing with billing ID=2 is for game A3 (see record R21 in billing history table T21). Then, the granting unit 243 refers to the granting ratio table T22 and obtains the conversion coefficient for games in group A to which game A3 belongs.
[0075] In the allocation ratio table T22, the conversion factors for games A1, A2, and A3 belonging to group A are 1, 1, and 0.5, respectively (see record R22 in allocation ratio table T22). In other words, for game A3, the amount spent on games A1 and A2 will be converted to in-game currency at a rate of twice as much. The allocation unit 243 allocates 12,000 yen, 12,000 yen, and 6,000 yen as in-game currency to games A1, A2, and A3 for a spending amount of 6,000 yen, and registers this in the currency allocation table T23 (record R23 in currency allocation table T23 / corresponding to Figure 9).
[0076] As described above, in the game management system 300, the reception unit 241 receives a charge from a user for any one of the games included in a predetermined group, and the granting unit 243 grants the user the in-game currency for each of the multiple games, which is calculated based on the charge amount.
[0077] By adopting this configuration, it becomes unnecessary to have a management server and a game provisioning system, making it possible to apply the present invention with a simpler configuration. <4. Other Embodiments>
[0078] While embodiments and variations of the present invention have been described above, the application of this disclosure is not limited to the above. For example, in the above embodiments, the user terminal 10 was implemented as a mobile terminal such as a smartphone, but the application is not limited to this example. For example, the user terminal 10 may be implemented by installing software on a home PC or the like.
[0079] Furthermore, the currency information storage unit may be configured to set an upper limit on the amount of in-game currency granted to users for each of the multiple games. This prevents problems such as the balance among users in the game being severely disrupted and the enjoyment diminished due to excessive accumulation of charges, especially in the case of fixed-rate billing.
[0080] Furthermore, in the second embodiment, the system may be configured to allow the user to change the monthly billing amount as appropriate. In this case, the billing history table T11 may have a column for the billing change date.
[0081] Furthermore, while the above embodiment involves user charges in yen, it is not limited to this example. For example, charges may be made in foreign currencies such as dollars, or in cryptocurrencies (virtual currencies) based on cryptographic technologies such as blockchain. Alternatively, charges may be made using points issued by a specific company that can be used when making purchases.
[0082] Furthermore, the present invention can also be implemented as a program that enables the management server and game provisioning system to function in order to realize the above-described system.
[0083] Furthermore, the present invention can also be realized as a computer-readable, non-temporary recording medium for storing the above-mentioned program.
[0084] While various embodiments of the present invention have been described, these are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included within the scope and spirit of the invention, as well as within the scope of the invention and its equivalents as described in the claims. [Explanation of symbols]
[0085] 10: User terminal 30,130: Management Server 31: Main Control Unit 32: Main memory 33:Auxiliary storage section 34: Communications Department 35: Operation Input Section 36: Monitor 37: System bus 41,141,241: Reception Department 42,142,242: Billing history storage unit 43,143,243: Assignment section 44,144,244: Currency information storage unit 47,147,247:Providing Department 145: Target Amount Setting Section 50,150,250: Game provision system 100,200,300: Game Management System
Claims
1. A game management system comprising a reception unit and a granting unit, wherein the reception unit receives charges from users, and the granting unit grants the user in-game currency for each of multiple games, calculated based on the amount of the charges.
2. A game management system according to claim 1, wherein the plurality of games are included in a predetermined group, and the reception unit receives payments from the user for the predetermined group.
3. A game management system according to claim 1, wherein the plurality of games are included in a predetermined group, and the reception unit receives a charge from the user for any one of the games included in the predetermined group.
4. A game management system according to any one of claims 1 to 3, wherein the granting unit grants to the user the amount of charge and the in-game currency of each of the plurality of games, which is calculated based on a coefficient for each of the plurality of games.
5. A game management system according to any one of claims 1 to 4, further comprising a target amount setting unit, wherein the target amount setting unit sets a target amount for each of the plurality of games to be used for conversion into in-game currency from the amount of charges received from the user, and the granting unit grants the user the in-game currency for each of the plurality of games, which has been converted based on the target amount for each of the plurality of games set by the target amount setting unit.
6. A game management system according to claim 5, further comprising a first storage unit and a second storage unit, wherein the first storage unit stores history information of charges received from the user, the second storage unit stores history information of the granting of in-game currency for each of the plurality of games to the user based on the charges received from the user, and the target amount setting unit sets at least a portion of the amount of charges received from the user that has not been granted in-game currency to the user for each of the plurality of games as the target amount for each of the plurality of games, based on the information stored in the first storage unit and the second storage unit.
7. A game management system according to claim 6, wherein, for a game that has been started to be provided after the user has made a payment, the target amount setting unit calculates the cumulative amount of payments made over a predetermined period based on the payment history information and sets the target amount.
8. A game management system according to claim 7, wherein the first storage unit stores the predetermined period for each of the plurality of games.
9. A game provision system according to any one of claims 6 to 8, wherein the second storage unit is configured such that an upper limit on the amount of in-game currency is set for each of the plurality of games.
Citation Information
Patent Citations
Game program
JP2004041561A
