JP2018161200A - Game server and game program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress excessive issue of an invitation code in a network game.SOLUTION: A game server receives a registration request of an invitation code of a game which is recommended by an inviter, from a game terminal of an inviter, and registers an issue button of the invitation code in a profile page of the inviter. When access from a game terminal of a person who is invited to the profile page for the inviter is performed, and the issue button of the invitation code is touched, the game server sends the invitation code to the game terminal of the person who is invited. When playing a recommended game using the invitation code by the person who is invited, a privilege may be applied to the person who is invited and the inviter.SELECTED DRAWING: Figure 6

Description

  The present invention relates to a technique for inviting another player to a network game.

  The use of smartphones as game terminals as well as communication terminals has become common. Network games popular with smartphones are provided by accessing a platform built on a game server from a smartphone. Network games often have contents that emphasize character development, cooperation and competition with other players, and collection of cards and items.

  The player can enjoy the network game alone, or can form a game group with a plurality of players and enjoy together. The network game has an aspect that an existing player invites a new player and the player layer expands.

  As a method for a certain player A to invite another player B to the game, Patent Document 1 discloses a mechanism called an invite code (invitation code). When player A provides an invitation code to player B, player B can receive various rewards (privileges such as items) in the game by inputting the invitation code to the game server. The privilege is an incentive (incentive) for player B to participate in the game. In addition, if a privilege is given to the player A who invited the player B, the incentive for solicitation increases.

Japanese Patent No. 5545325

  However, for invitees who are not interested in the game, the invitation code sent from the invitee is useless. If an invitation code is frequently sent via SNS (Social Networking Service), the invitee may be even a bad feeling for the game to be invited.

  The present invention is an invention completed based on the above recognition, and its main object is to provide a technique for suppressing the burst of invitation codes in a network game.

The game server in an aspect of the present invention is connected to a plurality of game terminals via a communication network.
The game server invites from a first game terminal operated by the first player to a code registration receiving unit for receiving a registration request for an invitation code of the first game and a web page associated with the first player. A code registration unit for registering a code acquisition unit, a page access receiving unit for receiving an access request to a web page from the second game terminal operated by the second player, and when the access request is received, A page transmission unit that transmits a page to the second game terminal, a code request reception unit that receives an invitation code acquisition request, and an invitation code acquisition request are received from the second game terminal that accessed the web page And a code transmission unit that transmits an invitation code to the second game terminal.

  According to the present invention, it is easy to efficiently distribute an invitation code in a network game.

It is a hardware block diagram of a game system. It is a functional block diagram of a game system. It is a data structure figure of play history information. It is a data structure figure of matching history information. It is a screen figure of a ranking screen. It is a screen figure of a profile screen. It is a screen figure of an invitation code acquisition screen. It is a flowchart which shows the publication process of a recommendation game. It is a flowchart which shows the issuing process of an invitation code. It is a flowchart which shows the download process of a game module.

  In the game system according to the present embodiment, the inviter does not send the invitation code to the invitee, but the inviter posts the invitation code on his / her profile page. Another player (invitee) accesses the inviter's profile page and actively obtains an invitation code therefrom.

Specifically, in the profile page (web page for self-introduction) of the player A (first player) in the game G2 (second game), the game G1 (first game) recommended by the player A is displayed. Post an invitation code. The player B (second player) of the game G2 may be interested in the game G1 by referring to the profile page of the player A. Player B can obtain an invitation code for game G1 from player A. If the player B registers as a player for the game G1 after acquiring the invitation code of the game G1, or if the player B actually plays the game G1, a privilege is given to the player A and the player B.
In the following, a game that invites an invitation like the game G2 is referred to as a “common game (second game)”, and a game that is introduced like the game G1 is referred to as a “recommended game (first game)”. I will call it.

FIG. 1 is a hardware configuration diagram of the game system 100.
In the game system 100, a plurality of game terminals 104 a, 104 b, 104 c... 104 n (hereinafter collectively referred to as “game terminal 104” when collectively referred to or not particularly distinguished) with respect to the game server 102. Connected through. The game terminal 104 in the present embodiment is assumed to be a smartphone. The game terminal 104 may be a portable game machine or a general-purpose computer such as a laptop PC. The game terminal 104 and the Internet 106 are wirelessly connected, but may be wired. A unique ID called a player ID is given in advance to the game player. The game server 102 provides a game to each game terminal 104.

FIG. 2 is a functional block diagram of the game system 100.
As described above, the game system 100 includes the game server 102 and the game terminal 104. Each component of the game terminal 104 and the game server 102 includes an arithmetic unit such as a CPU (Central Processing Unit) and various coprocessors, a storage device such as a memory and a storage, and hardware including a wired or wireless communication line connecting them. This is realized by software that is stored in a storage device and supplies processing instructions to an arithmetic unit. The computer program may be constituted by a device driver, an operating system, various application programs located in an upper layer thereof, and a library that provides a common function to these programs. Each block described below is not a hardware unit configuration but a functional unit block.
The game server 102 may be configured to include a web server, and the game terminal 104 may be configured to include a portable communication terminal and a web browser installed therein.

(Game server 102)
The game server 102 includes a communication unit 108, a data processing unit 110, and a data storage unit 112.
The communication unit 108 is in charge of communication processing with the game terminal 104 via the Internet 106. The data storage unit 112 stores various data. The data processing unit 110 executes various processes based on the data acquired by the communication unit 108 and the data stored in the data storage unit 112. The data processing unit 110 also functions as an interface between the communication unit 108 and the data storage unit 112. The data storage unit 112 stores various data.

  In addition to the game program, the data storage unit 112 stores information indicating the play state of each player. The play state includes the rank of the player, the level and equipment of the player / character, the items held, information on the skill, and the like. The invitation code issuance history is also stored in the data storage unit 112.

The data processing unit 110 includes a player registration unit 116, a matching processing unit 118, a game control unit 114, a privilege granting unit 120, and a code management unit 122.
The player registration unit 116 receives player registration (registration request) from the game terminal 104 via the communication unit 108. When player registration is requested, the player registration unit 116 gives a player ID to the player. When the game module is installed on the game terminal 104, player registration is automatically requested.

  The matching processing unit 118 performs matching (association) between the player and the player. When the communication unit 108 receives a group creation request from the player C, the communication unit 108 sets a game group and discloses the establishment of the game group. Next, when receiving a group participation request designating this game group from the player D, the matching processing unit 118 adds the player D to the game group established by the player C. Players belonging to the same game group can enjoy the same game in cooperation. The matching processing unit 118 can also set a match between a plurality of players. The matching processing unit 118 appropriately registers the relationship between players in the matching history information described later.

  When one player wants to build and maintain a continuous relationship with another player, this player can also make a friend application. For example, when the player E sends a friend request to the game server 102 for the player F, the matching processing unit 118 notifies the game terminal 104 of the player F that the friend E has requested a friend. If the player F approves this, the player E and the player F will become a "friend".

  The friend can know the details of the play history of the friend player, and the friend player's character who supports the character as an NPC (Non Player Character) when playing the game alone. There are various merits such as exchange and lending of information and items. The friend's merit can be arbitrarily designed according to the game, but at least “friend” may be a relationship in which two or more players register each other for the purpose of maintaining a continuous relationship. .

  The game control unit 114 controls the progress of the game in cooperation with the game execution unit 132 of the game terminal 104.

  The privilege granting unit 120 grants a privilege to both the inviter and the invitee when the invitee registers as a player in the recommended game of the inviter. Although the details will be described later, the “privilege” mentioned here may be useful information or useful things for the player to advance the game, such as characters, items, game points (currencies that can be used in the game), and resources. That's fine.

  The code management unit 122 manages the issuance history of the invitation code. The code management unit 122 includes a code registration unit 124. When requested by the inviter (first player) game terminal 104 (hereinafter referred to as “invite terminal (first game terminal)”), the code registration unit 124 displays an invitation code on the invitee's profile page. Register an issue button (acquisition means) for acquisition. Hereinafter, the game terminal 104 of the invitee (second player) is also referred to as “invited terminal (second game terminal)”.

The communication unit 108 includes a player registration reception unit 126, a matching request reception unit 128, a page access reception unit 130, a code registration reception unit 134, a page transmission unit 136, a code request reception unit 138, a code transmission unit 140, and a registration notification unit 142. Including.
The player registration receiving unit 126 receives a player registration request from the game terminal 104. The player registration request includes a game ID (hereinafter also referred to as “GID”) for identifying a game to be registered and the player ID of the registration requester. The matching request reception unit 128 receives a group creation request and a group participation request. The matching request receiving unit 128 also receives a battle request and a friend application. Hereinafter, a request for establishing a relationship between players, such as a group creation request and a friend application, is collectively referred to as a “matching request”.

  The page access receiving unit 130 receives an access request to the profile page (web page) from the game terminal 104. The code registration receiving unit 134 receives an invitation code registration request for the profile page from the invitation terminal. Registration of the invitation code here may be posting the invitation code (character string) as it is on the profile page, or registering the means for acquiring the invitation code like an issue button described later. .

  The page transmission unit 136 transmits a profile page to the game terminal 104. The code request receiving unit 138 receives an invitation code acquisition request from the game terminal 104 (invited terminal). The code transmission unit 140 transmits an invitation code to the invited terminal. The registration notification unit 142 notifies the invitation terminal when the invitee registers as a player in the game.

(Game terminal 104)
The game terminal 104 includes a user interface processing unit 144, a communication unit 146, a data processing unit 148, and a data storage unit 150.
The user interface processing unit 144 accepts operations from the player via the touch panel, and is also in charge of processing related to the user interface such as image display and audio output. The communication unit 146 is in charge of communication processing with the game server 102 and other game terminals 104 via the Internet 106. The data storage unit 150 stores various data. The data processing unit 148 performs various processes based on the data acquired by the user interface processing unit 144 and the communication unit 146 and the data stored in the data storage unit 150. The data processing unit 148 also functions as an interface for the user interface processing unit 144, the communication unit 146, and the data storage unit 150.

The data processing unit 148 includes a game execution unit 132.
The game execution unit 132 controls the progress of the game in cooperation with the game server 102. The game execution unit 132 of the game terminal 104 may be formed as a software module that is downloaded from the game server 102 as part of the function of the game control unit 114. The game execution unit 132 in this embodiment also generates an invitation code.

  The communication unit 146 includes a player registration transmission unit 152, a matching request transmission unit 154, a code registration transmission unit 156, a code request transmission unit 158, a code reception unit 160, and a notification reception unit 162.

  The player registration transmission unit 152 transmits a player registration request. The player registration request is automatically transmitted when the game is installed. The matching request transmission unit 154 transmits a matching request such as a group creation request or a friend application. The code registration transmission unit 156 transmits an invitation code registration request to the profile page as an inviter. The invitation code registration request includes a game ID, a player ID, and an invitation code. The code request transmission unit 158 transmits an invitation code acquisition request as an invitee. The code receiving unit 160 receives an invitation code as an invitee. The notification receiving unit 162 receives a registration notification transmitted from the registration notification unit 142 when the invitee registers as a player in the recommended game as an inviter.

  The communication unit 146 acquires various game information from the game server 102, and the data processing unit 148 causes the user interface processing unit 144 to display a game screen. Further, the user interface processing unit 144 detects various inputs by the user, and the data processing unit 148 notifies the game server 102 of input information via the communication unit 146. In response to this input information, the game control unit 114 of the game server 102 controls the progress of the game in cooperation with the game execution unit 132 of the game terminal 104.

  The user interface processing unit 144 includes an input unit 164 that receives input from the player, and an output unit 166 that outputs various information such as images and sounds to the player. The input unit 164 mainly detects a player's touch operation on the screen as an input.

FIG. 3 is a data structure diagram of the play history information 170.
The play history information 170 is stored in the data storage unit 112 of the game server 102. The play history information 170 indicates a play history for each player and each game, and the game control unit 114 updates the play history information 170 every time the game is played. FIG. 3 shows the play history of the player with player ID = P01 (hereinafter referred to as “player (P01)”).

  The registered name of the player (P01) is “Aloa”. The player (P01) has played a plurality of types of games such as a game (G01) and a game (G02). According to FIG. 3, the player (P01) has a cumulative experience of 78 hours in the game (G01), and the rank is 143. The rank is an index value that means the level of proficiency of the player with the game, and is usually increased each time the player clears a mission set during the game. The ranking of the player (P01) in the game (G01) is 1127th in the whole country. The player (P01) posts an invitation code of the game (G01) (hereinafter referred to as “invitation code (G01)”) (details will be described later).

  The rank of the player (P01) in the game (G02) is 1374, and the rank is first in the country. The player (P01) does not post the invitation code (G02). The player (P01) is not playing the game (G03), but has an invitation code (G03). In this way, an invitation code can be posted for an unplayed game.

  The play history also includes various achievements such as recently cleared stages and missions, the number of enemies defeated, possessed characters, character levels, possessed items such as weapons, armor, etc. Also good.

FIG. 4 is a data structure diagram of the matching history information 180.
The matching history information 180 is stored in the data storage unit 112 of the game server 102. The play history information 170 indicates a matching history for each player, and the matching processing unit 118 updates the matching history information 180 every time matching is established or canceled.

  In the matching history information 180, the relationship between players is indicated by symbols R0 to R2. R0 indicates a friend relationship. According to FIG. 4, the player (P01) and the player (P02) are in a friend relationship.

  R1 means belonging to the same game group in any game. The game group is formed for the purpose of a battle with a common enemy or another game group, or for the purpose of a battle / competition within the game group. What is commonly called a team or guild is a kind of game group. According to FIG. 4, the player (P01) and the player (P04) belong to the same game group.

  R2 indicates a relationship that has belonged to the same game group in the past but does not belong to the same game group now. According to FIG. 4, it can be seen that the player (P01) and the player (P05) belong to the same game group in the past. In addition, R2 may include an exchange history such as having no experience in the same game group but having a battle experience or having interactive conversation in SNS.

  According to FIG. 4, the player (P01) and the player (P03) have no matching history. That is, the two are not friends and have never belonged to the same game group.

FIG. 5 is a screen diagram of the ranking screen 190.
The ranking screen 190 shown in FIG. 5 is a screen showing the rank order in the game (G02). It is assumed that the ranking screen 190 in FIG. 5 is displayed on the game terminal 104 of the player (P02). The player (P02) can display the ranking screen 190 at any timing during the play of the game (G02). In the ranking screen 190, a plurality of player information areas 192 are displayed in a list according to the rank order. In FIG. 5, the player “Aloa” (player (P01)) from the first place to the player “kiyoko” (player (P32)) from the fourth place is shown, but by operating the scroll bar 194, the fifth place The following can also be confirmed.

  In the player information area 192, the player name, rank and rank are displayed. For example, the rank of the first player (P01) (player name “Aloa”) is first and the player rank is “1374”. The player (P02) can display a profile screen (described later with reference to FIG. 6) by touching the player information area 192.

FIG. 6 is a screen view of the profile screen 200.
The profile screen 200 shown in FIG. 6 is displayed when the player (P02) touches the player information area 192 of the first player (P01) (player name “Aloa”) on the ranking screen 190 of FIG. . This profile screen 200 shows the profile of the player (P01).

  The profile screen 200 includes a play state area 202 and a recommended game area 204. The play state area 202 indicates the play state of the player (P01) in the common game, that is, the game (G02). In the play state area 202, in addition to the rank and rank of the player (P01) in the game (G02), the held character and the level that is the skill level are displayed.

  The recommended game area 204 indicates a recommended game selected by the player (P01). In addition to the common game (G02), the player (P01) also plays the games “Super Forest” (game (G01)) and “R-Clear” (game (G04)). By touching the switching button 208, a plurality of recommended game areas 204 can be switched and displayed.

  In the recommended game area 204, a play history in the recommended game of the player (P01) is also displayed. The recommended game area 204 includes an issue button 206. The player (P02) (viewer) can issue an invitation code for a recommended game by touching the issue button 206 (described later).

  According to FIG. 6, the player (P01) (inviter) has experience in playing the recommended game (G01) (game name “Super Forest”), and the rank of the player (P01) in the recommended game (G01) is 143. Overall, it is 1127th. These pieces of information are based on the play history information 170 shown in FIG. When the common game (G02) is played, the code registration unit 124 receives the invitation code posting request of the recommended game (G01) from the player (P01) (inviter), and then the profile screen 200 of the player (P01). In addition to registering the game (G01) issue button 206, the play history is added to the recommended game area 204 with reference to the play history information 170.

  The player (P01) (inviter) can introduce a game that he / she finds interesting as a recommended game on the profile screen 200 of the common game. An issue button 206 is set for each recommended game. The player (P02) (the invitee) can obtain the invitation code of the recommended game (G01) (game name “Super Forest”) from the profile screen 200 of the player (P01).

  Since the play history of the recommended game (G01) by the player (P01) is displayed, how much the player (P02) who is the viewer is crazy about the recommended game (G01) by the player (P01) In other words, it can be determined whether the recommended game is selected based on actual experience. As described above, the inviter can also post a game that he has never played as a recommended game.

FIG. 7 is a screen diagram of the invitation code acquisition screen 210.
The invitation code acquisition screen 210 shown in FIG. 7 is displayed when the player (P02) touches the issue button 206 of the recommended game (G01) (game name “Super Forest”) on the profile screen 200 of FIG. When the issue button 206 is touched, the code transmission unit 140 of the game server 102 transmits the invitation 212 to the game terminal 104 (invited terminal) of the player (P02). When the player (P02) downloads the recommended game (G01) and registers as a player, if the invitation code (code “ABC1724” in the figure) shown in the invitation 212 is input, the privilege granting unit 120 will play the player (P02). As a privilege, “300 points” of game points are given. The game point is a currency for games in which items and the like can be bought in the recommended game (G01).

FIG. 8 is a flowchart showing a recommended game posting process.
A player who becomes an invitee first selects a recommended game. After selection, the game execution unit 132 generates an invitation code (character string) for the recommended game (S10). The code registration transmission unit 156 transmits a registration request including the game ID, player ID, and invitation code of the recommended game to the game server 102 (S12). The code registration receiving unit 134 of the game server 102 receives the registration request.

  In the common game, the code registration unit 124 registers the recommended game designated on the inviter's profile screen 200 (S14). The code registration unit 124 refers to the play history information 170, detects the play history of the inviter's recommended game, and posts it on the profile screen 200 (S16). Finally, the code registration unit 124 sets a recommendation game issue button 206 (S18). The code registration unit 124 associates the invitation code with the issue button 206 in the registration request in S12. The code registration unit 124 notifies the game terminal 104 of the completion of posting the recommended game and the invitation code (S20).

FIG. 9 is a flowchart showing an invitation code issuance process.
When a player accesses the profile screen 200 of another player, the page access receiving unit 130 receives an access request from the game terminal 104 (S30). The page transmission unit 136 transmits the designated web page (profile screen 200) to the requesting game terminal 104 (invited terminal) (S32). The communication unit 146 of the game terminal 104 (invited terminal) displays the profile screen 200 on the screen. The invitee touches the issue button 206 on the profile screen 200 (S34). At this time, the code request transmission unit 158 transmits an invitation code acquisition request including the player ID and the game ID to the game server 102, and the code request reception unit 138 receives the request (S36). The code transmission unit 140 transmits the invitation code associated with the issue button to the game terminal 104 (invited terminal), and the code reception unit 160 receives this (S38). The code management unit 122 records the invitation code issuance history (S40). Specifically, the code management unit 122 records who obtained the invitation code from which inviter for which game.

FIG. 10 is a flowchart showing a game module download process.
Here, the case where the player (P02) of the invited terminal downloads the recommended game (G01) of the player (P01) who is the invitee will be described as an example. First, the invited terminal transmits an installation request for the recommended game (G01) (S50). The game control unit 114 transmits the game module of the game (G01) to the game terminal 104 (S52). The game terminal 104 installs this game module (S54).

  After the installation, the player registration transmission unit 152 automatically transmits a player registration request including the player ID and the game ID to the game server 102 (S56). At this time, when the invitee player (P02) inputs the invitation code acquired on the invitation code acquisition screen 210, the invitation code is also transmitted to the game server 102 together with the player registration request. Upon the player registration request, the acquired invitation code may be automatically transmitted.

  The privilege granting unit 120 grants a predetermined privilege available in the recommended game (G01) to the invited player (P02) (S58). As described with reference to FIG. 7, 300 points are given as a privilege to the invited player (P02). On the other hand, the privilege granting unit 120 also grants a privilege to the player (P01) who issued the invitation code. The player (P01) may be given a privilege that can be used in the recommended game (G01), or may be given a privilege that can be used in the common game (G01). The player (P01) may be able to select which of the recommended game and the common game are to be obtained.

  With the player registration of the invitee player (P02) as a trigger, the registration notification unit 142 transmits a registration notification to the invitee player (P01) (S60). The notification receiving unit 162 of the invitation terminal receives the registration notification. By the registration notification, the player (P01) knows that the player (P02) has registered as a player in the game (G02). By this registration notification, the player (P01) knows that the player (P02) is invited to the game group of the recommended game (G01). Since the player (P02) is a new registrant (beginner) of the recommended game (G01), the player (P01) promptly invites the player (P02) to the game group in which he / she presides or participates. The power can be expanded. In this way, an invitation code can be posted, and a player who has registered as a player using the invitation code can be immediately invited to his / her friends.

  The registration notification unit 142 may transmit a registration notification to the inviter only when the invitee having the matching relationship of any of R0 to R2 described above registers as a player. For the inviter, a friend player, a player who belongs to the same game group, a player who belongs to the same game group in the past, and a player who has a battle experience are more likely to deepen exchanges than the other players. Setting the registration notification transmission conditions as described above is effective in deepening exchanges between players and encouraging re-exchange.

In the above, 100 was demonstrated based on embodiment.
In the game system 100, the invitee does not send the invitation code to the invitee without permission, but the invitee voluntarily acquires the invitation code from the profile screen 200 of the invitee. The player may request the invitation code of the game he wants to invite himself. The invitation applicant is required to confirm the intention in two stages by accessing the profile screen 200 of another player and touching the issue button 206. Conventionally, there are some players who distribute invitation codes by SNS or the like, but such an action is not preferable because it wastefully presses communication traffic on the Internet 106. In the game system 100 according to the present embodiment, such a variation does not occur, so that there is an advantage that the compression of communication traffic can be suppressed.

Conventionally, a player G who wants to receive an invitation may request another player H to issue an invitation code. In this case, it is necessary for the player H to generate an invitation code for the player G and to send it to the player G.
In the present embodiment, the player H has only to post the invitation code on his / her profile screen 200 in advance, and only has to tell the player G that the invitation code can be acquired by accessing his / her profile screen 200. That is, when an invitation is requested, an invitation code is not newly issued in response to the request, but an invitation code can be issued in advance, and it is only necessary to inform the invitation applicant. For this reason, there is also an advantage that the burden on the inviter is reduced.

  The invitation code can be acquired from a web page associated with the invitee such as the profile screen 200. If the invitation code is posted freely on a public web page such as an Internet bulletin board, the appearance of the web page will be messy, which is not preferable. In this embodiment, since the invitation code is posted on the profile screen 200, which is a dedicated web page for the inviter, it does not cause trouble for general viewers.

  In the present embodiment, the player of the common game can be guided to the recommended game. For example, the player of the common game can know what other games are played by other advanced players having a higher rank in the common game by looking at the ranking screen 190 of the common game. High-ranking advanced players tend to attract attention. For this reason, it is thought that the recommendation game which an advanced player chooses gets high recognition. An advanced player may choose a good game even if it is not very famous. The player promotes the game. A player with a higher rank is more likely to attract attention, and has the ability to speak, transmit, and persuade the player to recommend a game.

  On the profile screen 200, the play history of the inviter for the recommended game is also displayed. Therefore, the invitee can determine whether the invitee really plays the recommended game or selects the recommended game based on actual experience. The reliability of the recommendation can be ensured by the play history information 170 managed by the game server 102.

  Also, the player can recommend a game that he has never played. For example, a player (P01) who has never played the game (G03) selects the game (G03) as a recommended game, and the player (P05) uses the invitation code (G03) of the player (P01) to play the game (G03). Is registered as a player. Since the inviter (P01) is also an inexperienced person in the game (G03), the inviter (P01) invites the invitee (P05) who is also an inexperienced person, and at the same time, it becomes easy to start the game (G03). In this way, even an inexperienced person can issue an invitation code, thereby promoting the formation of a game group between inexperienced persons.

  In addition, this invention is not limited to the said embodiment and modification, A component can be deform | transformed and embodied in the range which does not deviate from a summary. Various inventions may be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments and modifications. Moreover, you may delete some components from all the components shown by the said embodiment and modification.

  Although it has been described that the game system 100 is configured by a plurality of game terminals 104 and one game server 102, some of the functions of the game terminal 104 may be realized by the game server 102, or the functions of the game server 102. May be allocated to the game terminal 104. In addition, a third device other than the game server 102 or the game terminal 104 may bear a part of the function.

  The game system 100, which is an aggregate of the functions of the game terminal 104 and the game server 102 described in FIG. 2, can be generally grasped as one “information processing apparatus”. How to allocate a plurality of functions necessary for realizing the present invention to one or a plurality of hardware depends on the processing capability of each hardware, the specifications required for the game system 100, and the like. It only has to be decided.

[Modification]
In the present embodiment, it has been described that an invitation code is generated at the game terminal 104. As a modification, the game server 102 may generate an invitation code. The code registration transmission unit 156 of the invitation terminal transmits a registration request including the game ID and player ID of the recommended game to the game server 102. When the code registration receiving unit 134 of the game server 102 receives the registration request, the code registration unit 124 generates an invitation code and records the invitation code in association with the game ID and the player ID. The game server 102 may notify the inviter of the contents of the invitation code, or may notify only the invitation code generation and not the invitation code itself.

  The privilege given to the inviter or invitee may be a privilege that can be used in the common game, or a privilege that can be used in the recommended game. Further, when the inviter registers the recommended games G2 and G3 in the common game G1, the privilege granting unit 120 may grant any privilege of the games G1 to G3 to the inviter. The privilege granting unit 120 may randomly determine which game privilege is to be given, or may allow the inviter to select. The inviter may be more happy to receive the benefits of the currently playing common game than the recommended games played in the past. Also, when a privilege is generated based on the player registration of the recommended game G2, it may be more pleasing to have a privilege for another recommended game G3 than the recommended game G2 played in the past.

  In the present embodiment, it has been described that privilege grant and registration notification are executed on the condition that the invitee has registered as a player in the recommended game using the invitation code. The player registration here is not only when the player explicitly executes the player registration, but the game server 102 recognizes the new player and temporarily records the player information, for example, the IP address of the game terminal 104. Implicit player registration is also included. The privilege grant or registration notification may be executed when the player downloads the game module, plays the game once or more, or plays the game for a predetermined time or more. The privilege granting unit 120 may grant the privilege to the inviter and the invitee on condition that the invitee and the invitee become friends as well as registering the player for the recommended game. .

  In the present embodiment, it has been described that the player inputs the invitation code when installing the game and registering the player. As a modified example, the invitation code received by the code receiving unit 160 is stored in the data storage unit 112, and the game server 102 communication unit 108 and the data processing unit 110 and the game terminal 104 communication unit 146 at the time of game installation. Player registration and invitation code input may be automatically executed.

  In the recommended game area 204 of the profile screen 200, various play histories may be posted in addition to the rank. For example, the total play time, the character to be held, the latest play date and time, the impression of the recommended game by the inviter, the reason for recommendation, etc. may be described.

  In the present embodiment, the matching history information 180 defines three types of matching histories R0 to R2. In addition to this, there are various relationships between players, such as those who live in the same town, the age difference between the two is within 3 years old, the hobbies registered in the profile are the same, and the same game is being played A relationship can be considered. The matching processing unit 118 may identify a player who knows the contact information by referring to an address book registered in the game terminal 104. The registration notification unit 142 may execute the registration notification even when there is a matching history other than the above-described R0 to R2. For example, the registration notification unit 142 may transmit a registration notification to the player I only when the player registered in the address book of the player I registers the player for the recommended game of the player I.

  In the present embodiment, it has been described that when the inviter notifies the game server 102 of the recommended game, the code registration unit 124 adds the issue button 206 corresponding to the recommended game to the profile screen 200. As a modification, the code registration unit 124 may add the invitation code itself to the profile screen 200. The code registration unit 124 may paste the invitation 212 on the profile screen 200 as it is. “Registration of the invitation code acquisition means” may be registration of an interface for issuing an invitation code, such as the issue button 206, or the invitation 212 including the invitation code is posted so as to be acquired. The invitation code may be posted in a readable form.

  An expiration date may be set for the invitation code. When a predetermined number of days elapses after the issue button 206 is added to the profile screen 200, the code registration unit 124 may automatically delete the issue button 206 from the profile screen 200. Even when the invitee performs player registration after acquiring the invitation code, the privilege granting unit 120 may grant the privilege on the condition that the player registration is executed before the expiration date of the invitation code expires. Good. An upper limit may be set for the number of invitation codes that can be issued per unit period. According to these restrictive settings, the value of the invitation code can be increased by suppressing excessive circulation of the invitation code.

  In this embodiment, it has been described that the inviter can also issue an invitation code for an unexperienced game. As a modification, the inviter may be able to issue an invitation code only for a game in which either he or a friend player is registered as a player. Specifically, when the code registration unit 124 receives a recommendation game registration request from the inviter, the code registration unit 124 searches the matching history information 180 for the invitee's friend, and either the inviter or the friend player determines the recommended game. An invitation code may be registered on condition that the player has a play history. According to such a control method, the invitee himself / herself can advertise the game recommended by the friend player instead of the friend player.

  In this embodiment, it has been described that the inviter selects the recommended game. As a modification, the game server 102 may select a recommended game by a “recommendation selection unit” (not shown). The recommendation selection unit may randomly select a recommended game from games that the inviter has played. The recommendation selection unit may select a predetermined number of games as a recommended game in the descending order of rank and the longest cumulative play time among the games that the player has played. According to such a control method, a game in which the player is deeply involved can be automatically selected, so that it is possible to save the player from selecting a recommended game.

  The number of recommended games that can be posted on the profile screen 200 may be limited. For example, the number of recommended games that can be posted on the profile screen 200 at a time may be within three. By narrowing down the number of recommended games in this way, only recommended recommendation games are posted, so it is considered that the quality of recommendation is improved. In addition, a recommended game may be posted for each game category, such as an action game or a role playing game.

  Generally, a game with a large number of downloads is regarded as a popular game. According to the present embodiment, it is possible to know the degree of satisfaction of the player with respect to the game by checking the total number registered as a recommended game by a large number of players. The data processing unit 110 of the game server 102 may include a “recommendation measurement unit” that indicates the quality of the game by measuring the number of times it is posted as a recommended game on a web page such as the profile screen 200.

  Not only the ranking and friends, but also a player who is playing the same game as himself may be notified. Such a player profile screen 200 may recommend a game that suits his / her preference.

  When the invitation button 206 is touched to acquire the invitation code, the code transmission unit 140 may transmit a friend application confirmation screen asking the player (invitee) whether or not to make a friend application together with the invitation code. When the invitee selects the friend application, the matching processing unit 118 of the game server 102 notifies the invitation terminal that the friend application has been made, and if the inviter accepts, the two are set as friends.

  When the player is registered using the invitation code, the matching processing unit 118 may automatically set two friends as friends. Similarly, the registration notification unit 142 may transmit a friend application confirmation screen that asks the invitee whether or not to make a friend application to the inviter in the registration notification. When the inviter selects the friend application, the matching processing unit 118 notifies the invited terminal that the friend application has been made. If the invitee accepts, the matching processing unit 118 sets two people as friends.

  The benefits are not limited to those available in the game, but may be useful in real life. For example, a movie ticket, a discount ticket at a game center or a retail store, an event invitation ticket, or the like may be given as a privilege.

  The invitation code is not limited to the profile screen 200, and may be a web page that is opened in association with the inviter. For example, an interface for acquiring an invitation code may be registered in the player information area 192 of the ranking screen 190, or the invitation code may be posted on a dedicated page corresponding to the game group.

  In the present embodiment, the game for smartphones has been described. However, the game system 100 may be realized by a home game machine or a personal computer. It may be an arcade game or a game linked with an arcade game.

  100 game system, 102 game server, 104 game terminal, 106 internet, 108 communication unit, 110 data processing unit, 112 data storage unit, 114 game control unit, 116 player registration unit, 118 matching processing unit, 120 privilege granting unit, 122 Code management unit, 124 code registration unit, 126 player registration reception unit, 128 matching request reception unit, 130 page access reception unit, 132 game execution unit, 134 code registration reception unit, 136 page transmission unit, 138 code request reception unit, 140 Code transmission unit, 142 registration notification unit, 144 user interface processing unit, 146 communication unit, 148 data processing unit, 150 data storage unit, 152 player registration transmission unit, 154 matching request transmission unit, 156 code registration transmission 158 code request transmission unit, 160 code reception unit, 162 notification reception unit, 164 input unit, 166 output unit, 170 play history information, 180 matching history information, 190 ranking screen, 192 player information area, 194 scroll bar, 200 profile screen, 202 play status area, 204 recommended game area, 206 issue button, 208 switching button, 210 invitation code acquisition screen, 212 invitation

Claims (8)

Connected to multiple game terminals via a communication network,
A code registration receiving unit for receiving a request for registration of an invitation code of the first game from the first game terminal operated by the first player;
A code registration unit for registering the invitation code acquisition means in a web page associated with the first player;
A page access receiving unit for receiving an access request to the web page from a second game terminal operated by a second player;
A page transmission unit that transmits the web page to the second game terminal when the access request is received;
A code request receiving unit that receives the invitation code acquisition request from the second game terminal that has accessed the web page;
A game server comprising: a code transmission unit configured to transmit the invitation code to the second game terminal on condition that the invitation code acquisition request is received.   The code registration unit registers an acquisition code acquisition unit for the first game on a web page that is associated with the first player and is open to the second game player. The game server according to claim 1. A player registration receiving unit for receiving a player registration request for the first game from the second game terminal;
A player registration unit for registering the second player for the first game when the player registration request is received;
A privilege granting unit that grants the first player a privilege of the second game on the condition that the second player has registered in the first game after obtaining the invitation code of the first game. The game server according to claim 1, further comprising:   4. The code registration unit posts a play history of the first game by the first player on the web page together with an invitation code of the first game. 5. The game server described. A player registration receiving unit for receiving a player registration request for the first game from the second game terminal;
A player registration unit for registering the second player for the first game when the player registration request is received;
A registration notifying unit for notifying the first game terminal of the registration of the second player when the second player registers for the first game after obtaining the invitation code for the first game. The game server according to claim 1, further comprising:   The registration notification unit notifies the registration of the second player to the first game terminal on condition that a matching history exists between the first player and the second player. The game server according to claim 5.   The code registration unit includes an invitation code for the first game on the web page associated with the first player regardless of whether or not the first player has a play history of the first game. The game server according to claim 1, wherein the acquisition means is registered. A function of receiving an invitation code registration request of the first game from the first game terminal operated by the first player;
A function of registering the means for acquiring the invitation code in a web page associated with the first player;
A function of receiving an access request to the web page from a second game terminal operated by a second player;
A function of transmitting the web page to the second game terminal when the access request is received;
A function of receiving an invitation code acquisition request from a second game terminal that has accessed the web page;
A game program causing a computer to exhibit a function of transmitting the invitation code to the second game terminal on condition that the invitation code acquisition request is received.

Images