JP5715100B2 - GAME SYSTEM, GAME SYSTEM CONTROL METHOD AND PROGRAM - Google Patents

Description

  The present invention relates to a game system, a game system control method, and a program.

  A game is provided by an SNS (Social Networking Service) system. In such a system, a user can receive a game by registering a game provided in the SNS system after completing membership registration in a member information registration server that manages SNS member information. For example, Patent Document 1 below discloses a system that provides a user with a plurality of services on a portal site.

JP 2010-113462 A

  However, since membership registration requires input of personal information, there are not a few users who are hesitant about membership registration even though they are interested in the game itself, and have these users experience the game. I couldn't. On the other hand, it is conceivable to set up a system unrelated to the SNS system and provide the user with a trial version game. However, even if the trial version game is played, it is actually used. Since no data is transferred to the system, the user's play content is wasted.

  The present invention has been made in view of the above-mentioned problems, and its purpose is to allow a user to experience a game before registering member information, and to at least part of the user's play contents as member information. Another object of the present invention is to provide a game system, a game system control method, and a program that can be taken over even after registration.

  The present invention for solving the above problems will be described below. In addition, in order to make an understanding of this invention easy, the reference sign of an accompanying drawing is attached in parenthesis writing, However, This invention is not limited to the aspect of illustration.

  That is, in the game system (7) according to the present invention, the game system (7) includes a game server (5) that can be connected to the client device (3) and the member information management device (4) via communication. A game is executed based on player identification information generating means (50, S109) for generating player identification information for identifying a player who operates the client device in response to a request from the client device, and data received from the client device. And update means (50, S111) for updating the game information associated with the player identification information, an address for accessing the member information management device based on predetermined data received from the client device, For taking over game information associated with player identification information Notification means (50, 54, S116) for notifying the client apparatus of link information including inherited handover information, and the client apparatus notified of the link information by the notification means, based on the link information, By accessing the member information management device and executing member registration, the member identification information generated by the member information management device, the transfer information acquisition means (50, 54, S304) for acquiring the transfer information, and the acquisition Storage means (50, 52, S315) for storing at least a part of the game information to be handed over by the handed over information in association with the player identification information corresponding to the acquired member identification information. Features.

  A game system control method according to the present invention is a game system control method including a game server that is connectable to a client device and a member information management device via communication, in response to a request from the client device. A player identification information generating step for generating player identification information for identifying a player who operates the client device, and a game is executed based on data received from the client device, and game information associated with the player identification information is updated. An update step, based on predetermined data received from the client device, an address for accessing the member information management device, and unique takeover information for taking over the game information associated with the player identification information. Includes link information before A notification step of notifying the client device, and the client device to which the link information has been notified by the notification step accesses the member information management device based on the link information and executes member registration, whereby the member information The member identification information generated by the management device, the handover information acquisition step for acquiring the transfer information, and at least a part of the game information to be transferred by the acquired transfer information correspond to the acquired member identification information. And a storage step of storing the information in association with the player identification information.

  Further, the program according to the present invention provides player identification information for identifying a player who operates a client device in response to a request from the client device, with a computer that can be connected to the client device and the member information management device via communication. A player identification information generating means for generating a game, an update means for executing game based on data received from the client device, updating game information associated with the player identification information, and a predetermined received from the client device Notification means for notifying the client device of link information including an address for accessing the member information management device and unique transfer information for taking over the game information associated with the player identification information based on the data And by the notification means Member identification information generated by the member information management device by the client device notified of the link information accessing the member information management device based on the link information and performing member registration, and the takeover information And a storage means for storing at least a part of the game information to be transferred by the acquired transfer information in association with the player identification information corresponding to the acquired member identification information. It is a program to make it.

  According to the present invention, a user can experience a game before registering member information, and at least a part of the user's play contents can be taken over even after registering the member information.

  In one aspect of the present invention, the game server stores the player identified by the player identification information corresponding to the member identification information in association with the player identification information corresponding to the member identification information by the storage unit. The execution of the game may be started based on the played game information.

  In one aspect of the present invention, the notification unit notifies the client device of the link information when predetermined data received from the client device requires processing by the member information management device. Also good.

  In one aspect of the present invention, the notifying unit sends the link information to the client device when a state of the game executed based on predetermined data received from the client device satisfies a predetermined condition. It is good also as notifying.

  In the aspect of the invention, the link information includes a takeover process request link including a predetermined link of the game server and the unique takeover information, and the takeover information acquisition unit is configured so that the client device has the link information. After accessing the member information management device based on the information and executing member registration, accepting access based on the takeover processing request link included in the link information from either the member information management device or the client device Then, the takeover information may be acquired.

  In one aspect of the present invention, the storage unit adds, to the acquired member identification information, an item selected by a player who operates the client device from game information to be transferred by the transfer information. It may be stored in association with the corresponding player identification information.

  The game system according to the present invention includes a client device, a game server that controls the game, and a member information management device, and the client device includes request means for requesting the game server to start the game. The game server includes: player identification information generating means for generating player identification information for identifying a player corresponding to the client device in response to a request from the request means; and data received from the client device, The member when the game is executed and the state of the game executed based on the data received from the client device and the update means for updating the game information associated with the player identification information satisfies a predetermined condition. An address for accessing the information management device and the player Notification means for notifying the client apparatus of link information including unique handover information for taking over game information associated with other information, and the client apparatus includes link information notified by the notification means. And a registration request unit that accesses the member information management device and requests registration of user information to the member information management device, wherein the member information management device receives information according to a request from the registration request unit. User identification information generating means for generating user identification information for identifying a registered user, wherein the game server uses the user identification information and the handover information acquisition means for acquiring the handover information, and the acquired handover information. At least part of the game information to be handed over is transferred to the acquired user identification information. A game system, characterized by further comprising a, a storage means for storing in association with the player identification information corresponding to.

It is a system configuration figure of the SNS system concerning a 1st embodiment. It is a figure which shows an example of a trial version game guidance screen. It is a figure which shows an example of the start confirmation screen of a trial version game. It is a figure which shows an example of a simple information registration screen. It is a figure which shows an example of the game start screen of a trial version. It is a figure which shows an example of the item purchase screen of a trial version. It is a figure which shows an example of a member information registration screen. It is a figure which shows an example of a game registration confirmation screen. It is a figure which shows an example of a player ID issue confirmation screen. It is a figure which shows an example of a data transfer confirmation screen. It is a figure which shows an example of the item purchase screen for production. It is a figure which shows an example of a structure of each apparatus contained in the SNS system which concerns on 1st Embodiment. It is a figure which shows an example of the player ID table for trial versions. It is a figure which shows an example of the game data management table for trial versions. It is a figure which shows an example of a production player ID table. It is a figure which shows an example of the game data management table (A) for performance. It is a figure which shows an example of the sequence which concerns on 1st Embodiment. It is a figure which shows an example of the sequence which concerns on 1st Embodiment. It is a figure which shows an example of the sequence which concerns on 1st Embodiment. It is a figure which shows an example of the sequence which concerns on 2nd Embodiment. It is a figure which shows an example of the sequence which concerns on 2nd Embodiment. It is a system configuration figure of an SNS system concerning a 3rd embodiment. It is a figure which shows an example of a structure of each apparatus contained in the SNS system which concerns on 3rd Embodiment. It is a figure which shows an example of the sequence which concerns on 3rd Embodiment. It is a figure which shows an example of the sequence which concerns on 3rd Embodiment. It is a figure which shows an example of the sequence which concerns on 3rd Embodiment. It is a figure which shows an example of the sequence which concerns on 3rd Embodiment.

  Hereinafter, embodiments of the present invention (hereinafter referred to as embodiments) will be described with reference to the drawings.

[1. First Embodiment]
First, an SNS (Social Networking Service) system 1 according to a first embodiment of the present invention will be described with reference to FIGS.

  In FIG. 1, the system block diagram of the SNS system 1 which concerns on 1st Embodiment was shown. As shown in FIG. 1, the SNS system 1 includes a client device 3, a platform server 4, and a game system 7. The game system 7 includes a game server 5, and the client device 3, the platform server 4, and the game server 5 are capable of data communication via the network 2. In the present embodiment, for simplicity of explanation, the number of game servers 5 is one, but there may be a plurality of game servers.

  The client device 3 is a computer operated by a user, and may be, for example, a mobile phone, a smartphone (multifunctional mobile phone), a PDA, a personal computer, or the like. In the present embodiment, a web browser is activated in the client device 3 to communicate with the platform server 4 and the game server 5 using the web browser, and a display screen based on data received from the platform server 4 and the game server 5 is displayed on the web browser. It may be displayed on the top.

  The platform server 4 is a computer that manages information on services such as social games provided in the SNS system 1 and information on users who receive the services. For example, the platform server 4 may function as a portal site for the SNS system 1. In this case, the client device 3 first accesses the platform server 4 to complete user authentication, and then accesses the desired game server 5 via the platform server 4 or directly to provide a game from the game server 5. Will receive. The platform server 4 may also perform billing processing when a user purchases an item in a social game provided by the game server 5, information management of relevance between a plurality of registered users, and the like.

  The game server 5 is a computer that provides a social game service to the client device 3. For example, the game server 5 manages game data (for example, level, item, stage, etc.) of the player with respect to a player ID for identifying the player of the game in the social game, and the player operation data received from the client device 3. And the social game is controlled based on the game data of the player.

  In general, in order to execute a social game provided in the SNS system 1, the user first accesses the platform server 4 by the client device 3 and completes member registration, and then selects a desired social game and registers the social game. Need to do. Here, since membership registration requires input of personal information, there are not a few users who feel that the threshold is high, and the user's need to decide whether to register as a member after first experiencing a social game It did not correspond to. Therefore, in the present embodiment, before the member registration with the platform server 4, the client device 3 can receive the social game trial version from the game server 5, and the member registration with the platform server 4 can be performed. After the completion, at least a part of the game data of the social game in the trial version is transferred to the actual social game. Note that in the trial version of the social game, the use of a function (for example, item purchase or use of a friend list) that involves processing on the platform server 4 is restricted.

[1.1. Screen transition example]
Hereinafter, with reference to an example of the screen transition shown in FIGS. 2 to 11, from the provision process of the trial version social game before membership registration, which is executed in the SNS system 1 according to the present embodiment, the performance after membership registration is performed. The flow up to the provision of social games will be described.

  First, the client device 3 accesses the game server 5, for example, and displays a trial version game guide screen including the link 10 to the trial version social game shown in FIG. The trial version game guidance screen is not limited to the game server 5 and may be provided from another server.

  Here, in the client device 3, when the link 10 on the trial version game guide screen is selected, the client device 3 accesses the game server 5 according to the link. Then, the game server 5 provides the client apparatus 3 with a trial confirmation screen for the trial version game shown in FIG.

  When the “play” link 11 on the trial version game start confirmation screen of FIG. 3 is selected in the client device 3, a message to that effect is transmitted to the game server 5. Then, the game server 5 provides a simple information registration screen shown in FIG.

  In the client device 3, after entering information in the column of the nickname (game nickname) used in the trial version of the social game on the simple information registration screen of FIG. Information on the nickname (game nickname) is transmitted to the game server 5.

  In the game server 5, the trial version game start screen shown in FIG. 5 is provided to the client device 3, and the trial version social game is advanced according to the data received from the client device 3.

  Here, when the game server 5 receives a purchase request for an item in the trial social game from the client device 3, the game server 5 selects the “Purchase” link 13 on the item purchase screen as shown in FIG. In addition to disabling, a “member registration” link 14 is displayed to notify the user that membership registration is required to purchase the item.

  When the client device 3 selects the “member registration” link 14 in FIG. 6, the client device 3 accesses the platform server 4 according to the link defined in the “member registration” link 14.

  When the identification information of the client device 3 (for example, the contractor ID given by the mobile communication carrier) is unregistered, the platform server 4 registers the membership information shown in FIG. Provide a screen. The nickname registered on the member information registration screen shown in FIG. 7 is a nickname for the platform server 4, and may be information independent of the game nickname registered in FIG.

  In the client device 3, when the “registration” link 15 is selected after the information is input in the information input field of the member information registration screen of FIG. 7, the input information is transmitted to the platform server 4.

  After registering the user information based on the information received from the client device 3, the platform server 4 displays a game registration confirmation screen for registering the social game provided by the game server 5 shown in FIG. provide.

  When the client device 3 selects the link 16 “Start game now” on the game registration confirmation screen in FIG. 8, the client device 3 transmits a message to that effect to the platform server 4. Upon receiving the confirmation of game registration, the platform server 4 generates a unique key (takeover unique key) for taking over the game data of the player in the trial version of the social game, and sends the takeover unique key to the client device 3. The link to be included is designated and redirected to the game server 5.

  The game server 5 provides the client device 3 with a player ID issuance confirmation screen for confirming whether or not to newly issue a production player ID shown in FIG. 9, and issues a new player ID from the client device 3. If there is a notification to do so, a player ID is newly issued.

  When the game server 5 determines that there is game data to be taken over based on the takeover unique key included in the link used by the client device 3 for access, the trial version of the social game shown in FIG. The client device 3 is provided with a data takeover confirmation screen for confirming whether or not to take over the game data of the player in the actual social game.

  When the “takeover” link 17 in FIG. 10 is selected in the client device 3, the fact is transmitted to the game server 5, and the game server 5 stores the trial version of the social game stored in association with the takeover unique key. Is copied as the game data of the player ID for production in the social game for production.

  The game server 5 advances the social game based on the copied game data after the copy is completed. For example, as shown in FIG. 11, the game server 5 may provide the client device 3 with an item purchase screen based on a state where the user has suspended for membership registration. At this time, since the user has completed membership registration on the platform server 4, the user can execute item purchase on the item purchase screen.

  The above is an example of the flow of processing in the SNS system 1 according to the present embodiment. Specific examples of functions and processing of each device provided in the SNS system 1 for realizing the above-described processing will be described below.

[1.2. Functional block diagram]
FIG. 12 illustrates the configurations of the client device 3, the platform server 4, and the game server 5 included in the SNS system 1. Hereinafter, the configuration of each device will be described in order.

[1.2.1. Configuration of Client Device 3]
First, the configuration of the client device 3 will be described. As illustrated in FIG. 12, the client device 3 includes a control unit 30, a storage unit 32, a communication unit 34, an input unit 36, and a display unit 38.

  The control unit 30 includes a CPU (Central Processing Unit), executes various arithmetic processes based on a program stored in the storage unit 32, and controls each unit of the client device 3.

  The storage unit 32 stores a control program such as an operating system of the client device 3, an application program such as a web browser, and data, and is also used as a work memory of the control unit 30. The program may be supplied to the client device 3 in a state of being stored in an information storage medium such as an optical disk, a magnetic disk, a magnetic tape, a magneto-optical disk, a flash memory, or the client device via a data communication unit such as the Internet. 3 may be supplied.

  The communication unit 34 includes a wireless communication antenna and communicates with the platform server 4 and the game server 5. For example, the communication unit 34 includes a mobile communication antenna for mobile communication, wirelessly communicates with a base station device (not shown) via the mobile communication antenna, and connects to the network 2 via the base station device, so that the platform server 4 Or data communication with the game server 5.

  The input unit 36 is realized by an input device such as a touch panel or a keyboard, and receives an operation input from a user.

  The display unit 38 is realized by a display device such as a liquid crystal display, and displays a result (screen) of information processing by the control unit 30.

[1.2.2. Configuration of Platform Server 4]
Next, the configuration of the platform server 4 will be described. As illustrated in FIG. 12, the platform server 4 includes a control unit 40, a storage unit 42, and a communication unit 44.

  The control unit 40 includes a CPU (Central Processing Unit), executes various arithmetic processes based on a program stored in the storage unit 42, and controls each unit of the platform server 4.

  The storage unit 42 stores a control program such as an operating system of the platform server 4 and data, and is also used as a work memory of the control unit 40. The program may be supplied to the platform server 4 in a state stored in an information storage medium such as an optical disk, a magnetic disk, a magnetic tape, a magneto-optical disk, a flash memory, or the platform server via data communication means such as the Internet. 4 may be supplied.

  The storage unit 42 may store, for example, user information, game server 5 information, and the like. The user information includes identification information of the client device 3 (for example, a mobile communication carrier contractor ID), a user's name, nickname, e-mail address, password, registered game information, possession points, user's information A friend list (a list of related users) or the like may be included.

  The communication unit 44 includes a network interface card and communicates with the client device 3 and the game server 5 via the network 2 connected via the network interface card.

[1.2.3. Configuration of game server 5]
Next, the configuration of the game server 5 will be described. As shown in FIG. 12, the game server 5 includes a control unit 50, a storage unit 52, and a communication unit 54.

  The control unit 50 includes a CPU (Central Processing Unit), executes various arithmetic processes based on a program stored in the storage unit 52, and controls each unit of the game server 5.

  The storage unit 52 stores a control program such as an operating system of the game server 5 and data, and is also used as a work memory of the control unit 50. The program may be supplied to the game server 5 in a state stored in an information storage medium such as an optical disk, a magnetic disk, a magnetic tape, a magneto-optical disk, a flash memory, or the game server via a data communication unit such as the Internet. 5 may be supplied.

  13 to 16 show an example of data stored in the storage unit 52 of the game server 5 in the present embodiment. FIGS. 13 and 14 are data related to the trial version of the social game, and FIGS. 15 and 16 are data related to the social game for production. Details of these data shown in FIGS. 13 to 16 will be described together with a sequence diagram to be described later.

  The communication unit 54 includes a network interface card and communicates with the client device 3 and the platform server 4 via the network 2 connected via the network interface card.

[1.3. Sequence Diagram]
Next, details of the processing performed in the SNS system 1 will be described with reference to the sequence diagrams shown in FIGS.

[1.3.1. Processing related to the provision of trial social games]
First, referring to the sequence diagram shown in FIG. 17, the flow of processing relating to provision of a trial version of a social game will be described. As illustrated in FIG. 17, the client device 3 acquires the address of a site that provides a trial version of the social game based on, for example, the website illustrated in FIG. 2 (S101), and based on the acquired address. The game server 5 is accessed (S102).

  Based on the address accessed from the client device 3, the game server 5 transmits display data for displaying a trial version social game start confirmation screen (for example, see FIG. 3) to the client device 3 (S <b> 103).

  The client device 3 determines the start of the trial version of the social game based on the user input on the start confirmation screen displayed based on the received display data (S104), and if not started (S104: N), the processing Is finished and is started (S104: Y), the game server 5 is requested to start the trial version of the social game (S105).

  When the game server 5 receives a request for starting the trial version of the social game, the game server 5 displays display data for displaying a simple information registration screen (see, for example, FIG. 4) for registering information necessary for executing the trial version of the social game. The data is transmitted to the client device 3 (S106).

  The client device 3 accepts user information input to the simple information registration screen displayed based on the received display data (S107), and transmits the input information (for example, a nickname for the game) to the game server 5 (S108).

  The game server 5 issues a trial version player ID for identifying a game player corresponding to the client apparatus 3 in the trial version of the social game based on the information received from the client apparatus 3 (S109). The game is started (see, for example, FIG. 5). Here, the game server 5 stores the issued trial version player ID in, for example, the trial version player ID table shown in FIG.

  As shown in FIG. 13, in the trial version player ID table, trial version player IDs, game nicknames, and registration date and time information are stored in association with each other. Of course, the trial version player ID table is not limited to the above-described mode. When the contractor ID of the mobile communication carrier is acquired from the client device 3, the contractor ID is further associated and stored. Also good.

  Returning to the sequence diagram of FIG. The client device 3 and the game server 5 perform data communication with each other (S110), and the game server 5 updates the game data associated with the trial version player ID based on the data received from the client device 3 (S111). . For example, the game data may be managed in the trial version game data management table shown in FIG.

  As shown in FIG. 14, in the trial version game data management table, a trial version player ID, a takeover unique key, and game data (level, item, stage, etc.) are stored in association with each other. Here, the unique key for handover is unique information for specifying the game data of the trial version player ID used when the game data of the trial version player ID is taken over as the game data of the production player ID. is there. A valid period may be set for the unique key for handover. If the trial version player IDs are generated so as not to overlap, the trial version player ID may be used as a unique key for handover.

  Returning to the sequence diagram of FIG. 17 again, the description will be continued. Based on the data received from the client device 3, the game server 5 determines whether or not a condition (member registration necessary condition) necessary for member registration with the platform server 4 is satisfied (S <b> 112). For example, the member registration requirement is whether or not a predetermined process (for example, an item purchase process) that requires processing on the platform server 4 is selected, and the user's game progress in the trial version of the social game is at a predetermined stage. It may be configured by any one or a combination of conditions such as whether or not the game execution time of the user in the trial version of the social game has reached a predetermined time.

  If the game server 5 determines that the client device 3 does not satisfy the member registration requirement (S112: N), the game server 5 returns to S110 and determines that the client device 3 satisfies the member registration requirement. (S112: Y), a unique key for taking over for taking over the game data of the trial version player ID is generated (S113). The game server 5 may store the generated unique key for handover in, for example, a game data management table for a trial version shown in FIG. And the game server 5 produces | generates the link (URL) for the taking over process of the game server 5 containing the produced | generated unique key for taking over (S114). For example, the unique key for handover of the trial version player ID “TP00002” is “aaaaaaa”, and the link for the social game handover processing provided by the game server 5 is “http://aaa.jp/succeed.php”. Then, the link for the game server 5 for taking over the game data of the trial version player ID “TP00002” is “http://aaa.jp/succeed.php?key=aaaaaaa”.

  Furthermore, the game server 5 converts the link for the takeover process of the game server 5 into a link for obtaining via the platform server 4 (link via platform) (S115). For example, if the game server 5 has a social game game identifier “1” and the link to the platform server 4 is “http://bbb.jp/”, the game server 5 links via the platform. Is generated as “http://bbb.jp/1/?url=http%3A%2F%2Faaa.jp%2Fsucceed.php%3Fkey%3Daaaaaaa”. It should be noted that the character string after url = in the above-mentioned link via the platform is an encoded link for the takeover processing of the game server 5.

  The game server 5 transmits the converted platform link as a redirect destination link to the client device 3 (S116). Then, the client device 3 accesses the platform server 4 based on the platform link received from the game server 5 (S117). The subsequent processing continues from the sequence diagram shown in FIG.

[1.3.2. Member registration process]
As shown in FIG. 18, the platform server 4 specifies a game to be registered based on the game identifier included in the link via the platform used by the client device 3 for access, and also includes a header of communication data from the client device 3. Based on the information, user information (for example, subscriber ID of a mobile communication carrier) is specified (S201). The platform server 4 determines whether or not the identified contractor ID is already registered in the storage unit 42 (S202). If not registered (S202: N), the member information registration screen is displayed on the client device 3. Display data for displaying (for example, see FIG. 7) is transmitted (S203).

  The client device 3 accepts user information input to the member information registration screen displayed based on the received display data (S204), and transmits the input information to the platform server 4 (S205).

  The platform server 4 issues a new social member ID based on the information received from the client device 3, and registers the user information received from the client device 3 in association with the issued social member ID (S206).

  When the identified contractor ID is already registered in the storage unit 42 in S202 (S202: Y), or after S206, the platform server 4 determines that the registration target game identified in S201 is a social network related to the registration process. It is determined whether the member ID has been registered (S207). Whether the game to be registered for the social member ID has been registered may be determined based on whether the game identifier included in the platform link is included in the registered game list of the social member ID.

  In S207, the platform server 4 displays a game registration screen (see, for example, FIG. 8) on the client device 3 when the registration target game has not been registered for the social member ID related to the process (S207: N). Display data to be transmitted is transmitted (S208).

  When the user information input to the game registration screen displayed based on the received display data does not permit registration (S209: N), the client device 3 ends the process and permits registration (S209). : Y), request the platform server 4 to register the game (S210).

  When receiving a game registration request from the client device 3, the platform server 4 updates the registered game list of the corresponding social member ID with a game identifier for identifying the game to be registered (S211). The processing performed after the registration target game is registered (after S211 or when registered in S207) will be described with reference to the sequence diagram shown in FIG.

[1.3.3. Data transfer processing]
As shown in FIG. 19, the platform server 4 redirects the client device 3 that has completed member registration and game registration to a link via platform (S301).

  When the client device 3 accesses the link via the platform (S302), the platform server 4 decodes and acquires the takeover processing link of the game server 5 encoded in the platform via link, and based on the takeover processing link. The game server 5 is accessed (S303). When accessing the game server 5 (HTTP request), the platform server 4 may include a social member ID corresponding to the client device 3 in the argument or header information of the HTTP request.

  The game server 5 acquires the takeover unique key included in the takeover processing link related to the HTTP request from the platform server 4 and acquires the social member ID included in the HTTP request (S304).

  The game server 5 determines the validity of the acquired takeover unique key (S305). Whether the takeover unique key is valid or not is determined by whether there is a takeover unique key, and if the takeover unique key has a valid period, whether or not the valid period has passed. It is good to do. When the game server 5 determines that the takeover unique key is not valid (S305: N), the game server 5 notifies the client device 3 of an error indicating that no takeover data exists (S306). . If the game server 5 determines that the acquired unique key for handover is valid (S305: Y), the game server 5 issues a player ID issuance confirmation screen for confirming whether or not to issue a new player ID to the user (S305: Y). For example, display data for displaying (see FIG. 9) is transmitted to the client device 3 via the platform server 4 (S307).

  If the user does not select to issue the player ID on the player ID issuance confirmation screen displayed based on the received display data (S308: N), the client device 3 ends the process, When the user selects to issue the player ID on the ID issue confirmation screen (S308: Y), the game server 5 is requested to issue a new player ID via the platform server 4 (S309).

  When the game server 5 receives the player ID issuance request from the client device 3, the game server 5 newly issues a production player ID (S310), and the issued player ID, for example, a production player ID table shown in FIG. To remember. As shown in FIG. 15, in the production player ID table, information of a player ID, a social member ID, a nickname, and a registration date is stored in association with each other.

  Next, for the newly issued player ID, the game server 5 selects an item to be transferred from the game data linked to the unique key for transfer (S311). For example, the game server 5 may select all items of game data linked to the unique key for takeover as takeover target data, or some items (for example, items, levels, ability values) of the game data. At least one) may be selected as data to be taken over. When selecting a part of the game data as the data to be handed over, the user may select data to be selected as the data to be handed over, or may select a predetermined item.

  The game server 5 transmits to the client device 3 via the platform server 4 display data for displaying a takeover confirmation screen (for example, see FIG. 10) for confirming whether or not the takeover target data is to be taken over by the production player ID. (S312).

  If the user does not select to take over the takeover confirmation screen displayed based on the received display data (S313: N), the client device 3 ends the process and displays the user on the takeover confirmation screen. Is selected to take over (S313: Y), the game server 5 is requested to take over the data to be taken over via the platform server 4 (S314).

  When the game server 5 receives the takeover request from the client device 3, the game server 5 copies the takeover target data to the game data of the actual player ID and executes the takeover process (S315).

  For example, the game server 5 copies the game data selected from the trial version game data management table shown in FIG. 16B to the actual game data management table shown in FIG. Specifically, the game server 5 uses the game target data selected from the game data included in the record specified by the unique key for handover from the game data management table for the trial version for the production. It is good also as copying to the game data of player ID.

  And the game server 5 produces | generates the game page of a social game based on the game data of player ID in which the transfer object data was copied (S316), and the client apparatus 3 via the platform server 4 produces | generates the produced | generated game page. In addition, user operation information is received from the client device 3 and game communication is performed with each other (S317). Then, the game server 5 updates the game data associated with the production player ID based on the data received from the client device 3 (S318).

  The game server 5 returns to S316 when not ending the social game (S319: N), and ends the process when ending (S319: Y).

  According to the SNS system 1 which concerns on 1st Embodiment demonstrated above, even before the member registration to the platform server 4, a trial version social game can be provided to a user. Moreover, since membership registration to the platform server 4 is required in order to continue the trial version of the social game, it is also a motivation for membership registration. In addition, after membership registration with the platform server 4, the game data of the user in the trial version of the social game can be transferred to the actual social game, so that the game play in the trial version is not wasted for the user.

[2. Second Embodiment]
Next, a second embodiment of the present invention will be described. In the first embodiment described above, the client device 3 and the game server 5 communicate with each other via the platform server 4, whereas in the second embodiment, the authentication of the client device 3 is performed. After the completion, the client device 3 and the game server 5 are configured to directly communicate with each other, which is different from the first embodiment. Hereinafter, the second embodiment will be described with a focus on differences from the first embodiment. Specifically, since the description of FIGS. 1 to 18 in the first embodiment is common to the second embodiment, in the second embodiment, after the game to be registered in FIG. 18 is registered ( Processing performed after S211 or when registered in S207) will be described with reference to the sequence diagrams shown in FIGS.

[2.1. Authentication processing of client device 3]
As shown in FIG. 20, the platform server 4 issues a unique key for authentication indicating that the client device 3 that has completed member registration and game registration has been authenticated (S401). For example, the platform server 4 may store a set of a social member ID (for example, SID = “S00101”) and an authentication unique key (for example, authkey = “bbbbbb”).

  Next, the platform server 4 generates a destination link for redirecting the client device 3 (S402). For example, the platform server 4 includes the social member ID (and the generated unique key for authentication) in the link (http://aaa.jp/succeed.php?key=aaaaaaa) for the takeover process of the game server 5. And the redirect destination link (http://aaa.jp/succeed.php?key=aaaaaaa&SID=S00101&authkey=bbbbbb), and the platform server 4 sends the generated redirect destination link to the client device. 3 (S403).

  The client device 3 accesses the game server 5 based on the redirect destination link received from the platform server 4 (S404).

  The game server 5 acquires the social member ID and authentication unique key included in the link accessed from the client device 3 (S405), and the social member ID and authentication unique key acquired in the platform server 4 are valid. (S406). The platform server 4 sends an authentication result to the game server based on whether or not the set of the stored social member ID and authentication unique key matches the set of the social member ID and authentication unique key related to the inquiry. Return to 5.

  If the authentication result returned from the platform server 4 is unsuccessful (NG) (S407: N), the game server 5 ends the process, and if the authentication result returned from the platform server 4 is successful (OK). If this is the case (S407: Y), a session is established with the client device 3 (S408). Thereafter, the game server 5 and the client device 3 communicate directly. The subsequent processing continues from the sequence diagram shown in FIG.

[2.2. Data transfer processing]
As shown in FIG. 21, the game server 5 acquires the takeover unique key included in the redirect destination link accessed from the client device 3 (S501), and determines the validity of the acquired takeover unique key. (S502). Whether the takeover unique key is valid or not is determined by whether there is a takeover unique key, and if the takeover unique key has a valid period, whether or not the valid period has passed. It is good to do. If the game server 5 determines that the takeover unique key is not valid (S502: N), the game server 5 notifies the client device 3 of an error indicating that there is no takeover data (S503). If the game server 5 determines that the acquired unique key for takeover is valid (S503: Y), the game server 5 issues a player ID issuance confirmation screen for confirming whether or not to issue a new player ID to the user (S503: Y). For example, display data for displaying (see FIG. 9) is transmitted to the client apparatus 3 (S504).

  If the user does not select to issue a player ID on the player ID issuance confirmation screen displayed based on the received display data (S505: N), the client device 3 ends the process, and the player When the user selects to issue a player ID on the ID issue confirmation screen (S505: Y), the game server 5 is requested to issue a new player ID (S506).

  When the game server 5 accepts a player ID issuance request from the client device 3, the game server 5 newly issues a production player ID (S507), and the issued player ID, for example, a production player ID table shown in FIG. To remember.

  Next, the game server 5 selects an item to be handed over from the game data associated with the handing over unique key for the newly issued player ID (S508). For example, the game server 5 may select all items of game data linked to the unique key for takeover as takeover target data, or some items (for example, items, levels, ability values) of the game data. At least one) may be selected as data to be taken over. When selecting a part of the game data as the data to be handed over, the user may select data to be selected as the data to be handed over, or may select a predetermined item.

  The game server 5 transmits display data for displaying a takeover confirmation screen (see, for example, FIG. 10) for confirming whether or not the takeover target data is taken over to the production player ID to the client device 3 (S509).

  If the user does not select to take over the takeover confirmation screen displayed based on the received display data (S510: N), the client device 3 terminates the process and returns to the takeover confirmation screen. Is selected to take over (S510: Y), the game server 5 is requested to take over the data to be taken over (S511).

  When the game server 5 receives the takeover request from the client device 3, the game server 5 copies the takeover target data to the game data of the actual player ID and executes the takeover process (S512).

  For example, the game server 5 copies the game data selected from the trial version game data management table shown in FIG. 16B to the actual game data management table shown in FIG. Specifically, the game server 5 uses the game target data selected from the game data included in the record specified by the unique key for handover from the game data management table for the trial version for the production. It is good also as copying to the game data of player ID.

  And the game server 5 produces | generates the game page of a social game based on the game data of player ID with which the inheritance object data was copied (S513), transmits the produced | generated game page to the client apparatus 3, Moreover, User operation information is received from the client device 3, and game communication is performed with each other (S514). Then, the game server 5 updates the game data associated with the production player ID based on the data received from the client device 3 (S515).

  The game server 5 returns to S513 when not ending the social game (S516: N), and ends the process when ending (S516: Y).

  According to the SNS system 1 which concerns on 2nd Embodiment demonstrated above, even before the member registration to the platform server 4, a trial version social game can be provided to a user. Moreover, since membership registration to the platform server 4 is required in order to continue the trial version of the social game, it is also a motivation for membership registration. In addition, after membership registration with the platform server 4, the game data of the user in the trial version of the social game can be transferred to the actual social game, so that the game play in the trial version is not wasted for the user. In the second embodiment, since the client device 3 and the game server 5 communicate directly when executing the game, the response of the game can be improved.

[3. Third Embodiment]
Next, a third embodiment of the present invention will be described. In the above-described first embodiment, the game server 5 provides both the trial version of the social game and the production social game. However, in the third embodiment, the trial version of the social game is provided. The trial version game server 6 and the game server 5 that provides the production social game are separated. Hereinafter, the third embodiment will be described with a focus on differences from the first embodiment.

[3.1. System Configuration]
FIG. 22 shows a system configuration diagram of the SNS system 1 according to the third embodiment. As shown in FIG. 22, the SNS system 1 includes a client device 3, a platform server 4, and a game system 7. The game system 7 includes a game server 5 and a trial version game server 6, and the client device 3, the platform server 4, the game server 5, and the trial version game server 6 can each perform data communication via a network.

[3.2. Functional block diagram]
FIG. 23 shows configurations of the client device 3, the platform server 4, the game server 5, and the trial version game server 6 included in the SNS system 1 according to the third embodiment. Since the client device 3 and the platform server 4 are the same as those in the first embodiment, description thereof is omitted. Further, the game server 5 is different from the first embodiment in that the data related to the trial version of the social game is not stored in the storage unit 52 in FIGS. 13 and 14. The configuration of the trial version game server 6 will be described below.

[3.2.1. Configuration of trial version game server]
As shown in FIG. 23, the trial version game server 6 includes a control unit 60, a storage unit 62, and a communication unit 64.

  The control unit 60 includes a CPU (Central Processing Unit), executes various arithmetic processes based on a program stored in the storage unit 62, and controls each unit of the trial version game server 6.

  The storage unit 62 stores a control program such as an operating system of the trial version game server 6 and data, and is also used as a work memory of the control unit 60. The program may be supplied to the trial version game server 6 in a state stored in an information storage medium such as an optical disk, a magnetic disk, a magnetic tape, a magneto-optical disk, or a flash memory, or via a data communication means such as the Internet. May be supplied to the trial version game server 6. The storage unit 62 stores data relating to the trial version of the social game shown in FIGS. 13 and 14.

  The communication unit 54 includes a network interface card and communicates with the client device 3 and the platform server 4 via the network 2 connected via the network interface card.

[3.3. Sequence Diagram]
Next, details of processing performed in the SNS system 1 according to the third embodiment will be described with reference to the sequence diagrams shown in FIGS.

[3.3.1. Processing related to the provision of trial social games]
First, with reference to the sequence diagram shown in FIG. 24, the flow of processing related to providing a trial version of a social game will be described. As shown in FIG. 24, the client device 3 acquires the address of the site that provides the trial version of the social game based on the website shown in FIG. 2, for example (S601), and based on the acquired address The trial version game server 6 is accessed (S602).

  The trial version game server 6 transmits display data for displaying a trial version social game start confirmation screen (for example, see FIG. 3) to the client apparatus 3 based on the address accessed from the client apparatus 3 (S603). .

  The client device 3 determines the start of the trial version of the social game based on the user input on the start confirmation screen displayed based on the received display data (S604), and if not started (S604: N), the processing Is terminated (S604: Y), the trial version game server 6 is requested to start the trial version social game (S605).

  When the trial version game server 6 receives a request to start the trial version of the social game, the trial version game server 6 displays a simple information registration screen (for example, see FIG. 4) for registering information necessary for executing the trial version of the social game. The display data is transmitted to the client device 3 (S606).

  The client device 3 accepts user information input to the simple information registration screen displayed based on the received display data (S607), and transmits the input information (for example, nickname) to the trial version game server 6 (S608). .

  Based on the information received from the client device 3, the trial version game server 6 issues a trial version player ID for identifying the game player corresponding to the client device 3 in the trial version of the social game (S609). The social game of the version is started (see, for example, FIG. 5). Here, the trial version game server 6 stores the issued trial version player ID in, for example, the trial version player ID table shown in FIG.

  Returning to the sequence diagram of FIG. The client device 3 and the trial version game server 6 perform data communication with each other (S610), and the trial version game server 6 is based on the data received from the client device 3 and game data associated with the trial version player ID. Is updated (S611). For example, the game data may be managed in the trial version game data management table shown in FIG.

  Returning to the sequence diagram of FIG. 24 again, the description will be continued. Based on the data received from the client device 3, the trial version game server 6 determines whether or not a condition (member registration necessary condition) necessary for member registration with the platform server 4 is satisfied (S612). For example, the member registration requirement is whether or not a predetermined process (for example, an item purchase process) that requires processing on the platform server 4 is selected, and the user's game progress in the trial version of the social game is at a predetermined stage. It may be configured by any one or a combination of conditions such as whether or not the game execution time of the user in the trial version of the social game has reached a predetermined time.

  When the trial version game server 6 determines that the client device 3 does not satisfy the member registration requirement (S612: N), the trial version game server 6 returns to S610 and determines that the client device 3 satisfies the member registration requirement. If so (S612: Y), a takeover unique key for taking over the game data of the trial version player ID is generated (S613). The trial version game server 6 may store the generated takeover unique key in, for example, the trial version game data management table shown in FIG. Then, the trial version game server 6 generates a link (URL) for the handover process of the trial version game server 6 including the generated unique key for handover (S614). For example, the takeover unique key of the trial version player ID “TP00002” is “aaaaaaa”, and the social game takeover processing link provided by the trial version game server 6 is “http://aaa.jp/succeed”. .php ”, the link for the trial version game server 6 for transferring the game data of the trial version player ID“ TP00002 ”is“ http://aaa.jp/succeed.php?key=aaaaaaa ” .

  Further, the trial version game server 6 converts the link for the takeover process of the trial version game server 6 into a link (link via platform) for obtaining via the platform server 4 (S615). For example, the trial version game server 6 sets the game identifier of the social game provided by the trial version game server 6 to “1” and the link to the platform server 4 to “http://bbb.jp/”. Generates a link via the platform as “http://bbb.jp/1/?url=http%3A%2F%2Faaa.jp%2Fsucceed.php%3Fkey%3Daaaaaaa”. It should be noted that the character string after url = in the above-described link via the platform is an encoded link for the takeover process of the trial version game server 6.

  The trial version game server 6 transmits the converted platform link as a redirect destination link to the client device 3 (S616). Then, the client device 3 accesses the platform server 4 based on the platform link received from the trial version game server 6 (S617). The subsequent processing continues from the sequence diagram shown in FIG.

[3.3.2. Member registration process]
As shown in FIG. 25, the platform server 4 specifies a game to be registered based on a game identifier included in the link via the platform used by the client device 3 for access, and also includes a header of communication data from the client device 3. Based on the information, the subscriber ID of the mobile communication carrier is specified (S701). The platform server 4 determines whether or not the identified contractor ID has already been registered in the storage unit 42 (S702), and if not registered (S702: N), the member information registration screen is displayed on the client device 3. Display data for displaying (for example, see FIG. 7) is transmitted (S703).

  The client device 3 accepts user information input on the member information registration screen displayed based on the received display data (S704), and transmits the input information to the platform server 4 (S705).

  The platform server 4 issues a new social member ID based on the information received from the client device 3, and registers the user information received from the client device 3 in association with the issued social member ID (S706).

  When the identified contractor ID is already registered in the storage unit 42 in S702 (S702: Y), or after S706, the platform server 4 determines that the registration target game identified in S701 is a social related to the registration process. It is determined whether or not the member ID has been registered (S707). Whether the game to be registered for the social member ID has been registered may be determined based on whether the game identifier included in the platform link is included in the registered game list of the social member ID.

  In S707, the platform server 4 displays a game registration screen (see, for example, FIG. 8) on the client device 3 when the registration target game has not been registered for the social member ID related to the process (S707: N). Display data to be transmitted is transmitted (S708).

  If the user information input to the game registration screen displayed based on the received display data does not permit registration (S709: N), the client device 3 terminates the process and permits registration (S709). : Y), request the platform server 4 to register the game (S710).

  When receiving a game registration request from the client device 3, the platform server 4 updates the registered game list of the corresponding social member ID by adding a game identifier for identifying the game to be registered (S711). Processing performed after the registration target game is registered (after S711 or when registered in S707) will be described with reference to the sequence diagrams shown in FIGS.

[3.3.3 (1) Data takeover process 1]
As shown in FIG. 26, the platform server 4 redirects the client device 3 that has completed member registration and game registration to the link via platform (S801).

  When the client device 3 accesses the platform link (S802), the platform server 4 decodes and acquires the takeover processing link of the game server 5 encoded in the platform link, and based on the takeover processing link. The game server 5 is accessed (S803). When accessing the game server 5 (HTTP request), the platform server 4 may include a social member ID corresponding to the client device 3 in the argument or header information of the HTTP request.

  The game server 5 acquires the takeover unique key included in the takeover processing link related to the HTTP request from the platform server 4 and acquires the social member ID included in the HTTP request (S804).

  The game server 5 inquires of the trial version game server 6 whether or not the acquired unique key for handover is valid (S805). The trial version game server 6 determines whether the takeover unique key related to the inquiry is valid, whether there is a takeover unique key, and if the takeover unique key has a valid period, The determination may be made based on whether the valid period has elapsed. Then, the game server 5 acquires the determination result from the trial version game server 6, and if the takeover unique key is not valid (S806: N), an error message indicating that there is no takeover data is displayed on the platform server 4. To the client device 3 (S807). On the other hand, when the takeover unique key is valid (S806: Y), the game server 5 requests the trial version game server 6 to transfer the game data associated with the takeover unique key. The game data is acquired from the trial version game server 6 (S809).

  Next, the game server 5 displays display data for displaying a player ID issuance confirmation screen (for example, see FIG. 9) for confirming whether or not to newly issue a player ID to the user via the platform server 4. 3 (S810).

  When the user does not select to issue a player ID on the player ID issuance confirmation screen displayed based on the received display data (S811: N), the client device 3 ends the process. Hereinafter, processing performed when the user selects to issue a player ID on the player ID issuance confirmation screen (S811: Y) will be described with reference to the sequence diagram of FIG.

[3.3.3 (2) Data takeover process 2]
As shown in FIG. 27, when the user selects to issue a player ID on the player ID issuance confirmation screen (S811: Y), the client device 3 plays a game via the platform server 4. The server 5 is requested to issue a new player ID (S812).

  When the game server 5 receives the player ID issuance request from the client device 3, the game server 5 newly issues a production player ID (S813), and the issued player ID is, for example, a production player ID table shown in FIG. To remember. As shown in FIG. 15, in the production player ID table, information of a player ID, a social member ID, a nickname, and a registration date is stored in association with each other.

  Next, the game server 5 selects an item to be transferred from the game data associated with the unique key for transfer for the newly issued player ID (S814). For example, the game server 5 may select all items of game data linked to the unique key for takeover as takeover target data, or some items (for example, items, levels, ability values) of the game data. At least one) may be selected as data to be taken over. When selecting a part of the game data as the data to be handed over, the user may select data to be selected as the data to be handed over, or may select a predetermined item.

  The game server 5 transmits to the client device 3 via the platform server 4 display data for displaying a takeover confirmation screen (for example, see FIG. 10) for confirming whether or not the takeover target data is to be taken over by the production player ID. (S815).

  If the user does not select to take over the takeover confirmation screen displayed based on the received display data (S816: N), the client device 3 ends the process and returns to the takeover confirmation screen. Is selected to take over (S816: Y), the game server 5 is requested to take over the data to be taken over via the platform server 4 (S817).

  When the game server 5 receives the takeover request from the client device 3, the game server 5 copies the takeover target data to the game data of the actual player ID and executes the takeover process (S818).

  And the game server 5 produces | generates the game page of a social game based on the game data of player ID with which the inheritance object data was copied (S819), and the client apparatus 3 via the platform server 4 produces | generates the produced game page. In addition, user operation information is received from the client device 3 and game communication is performed with each other (S820). Then, the game server 5 updates the game data associated with the production player ID based on the data received from the client device 3 (S821).

  The game server 5 returns to S819 when not ending the social game (S822: N), and ends the process when ending (S822: Y).

  According to the SNS system 1 according to the third embodiment described above, it is possible to provide a trial version of a social game to a user even before membership registration with the platform server 4. Moreover, since membership registration to the platform server 4 is required in order to continue the trial version of the social game, it is also a motivation for membership registration. In addition, after membership registration with the platform server 4, the game data of the user in the trial version of the social game can be transferred to the actual social game, so that the game play in the trial version is not wasted for the user. Further, by separating the trial version game server 6 that provides the trial version of the social game and the game server 5 that provides the production social game, a malfunction of the trial version game server 6 affects the game server 5. You can avoid that.

  In the SNS system 1 according to the third embodiment, the client device 3 directly accesses the game server 5 after the authentication with the platform server 4 as described in the second embodiment. Of course it is good.

  The present invention is not limited to the above embodiment. For example, in the above-described embodiment, the trial version player ID and the production player ID are separated, but the flag indicating that the trial version or the production use is associated with the player ID and the flag value is switched. Thus, the trial version player ID and the production player ID may be shared.

  Further, data relating to the player ID for the trial version (for example, FIG. 13 and FIG. 14) may be deleted when a predetermined time has elapsed since registration.

  Moreover, although this invention demonstrated the example applied to the social game, it cannot be overemphasized that it can apply similarly to another online game.

  1 SNS system, 2 network, 3 client device, 4 platform server, 5 game server, 6 trial game server, 7 game system, 10-17 links, 30 control unit, 32 storage unit, 34 communication unit, 36 input unit , 38 display unit, 40 control unit, 42 storage unit, 44 communication unit, 50 control unit, 52 storage unit, 54 communication unit, 60 control unit, 62 storage unit, 64 communication unit.

Claims (8)

In Gate beam system can be connected via a communication with the client device and the member information management device,
Player identification information generating means for generating player identification information for identifying a player who operates the client device in response to a request from the client device;
Updating means for executing a game based on data received from the client device and updating game information associated with the player identification information;
A game associated with the first address for accessing the member information management device, the second address for accessing the game system, and the player identification information based on predetermined data received from the client device A notifying means for notifying the client device of link information including a takeover processing request link including unique takeover information for taking over the information;
Link information by the notifying means is notified the client device, after performing member registration by accessing the member information management device based on the first address included in the link information, the member information management device Alternatively, the member identification information generated by the member information management device and the handover information for acquiring the handover information by accepting access based on the handover processing request link including the second address from either of the client devices. Acquisition means;
And a storage unit that stores at least a part of the game information to be transferred by the acquired transfer information in association with the player identification information corresponding to the acquired member identification information. . The game system according to claim 1,
The game system is configured for the player identified by the player identification information corresponding to the member identification information based on the game information stored by the storage unit in association with the player identification information corresponding to the member identification information. A game system characterized by starting execution. The game system according to claim 1 or 2,
The notifying means notifies the client device of the link information when predetermined data received from the client device requires processing by the member information management device. The game system according to claim 1 or 2,
The notification unit notifies the client device of the link information when a state of the game executed based on predetermined data received from the client device satisfies a predetermined condition. . The game system according to any one of claims 1 to 4 ,
The storage unit stores an item selected by the player operating the client device from the game information to be transferred by the transfer information in association with the player identification information corresponding to the acquired member identification information. A game system characterized by A method for controlling a Gate beam system can be connected via a communication with the client device and the member information management device,
A player identification information generating step for generating player identification information for identifying a player who operates the client device in response to a request from the client device;
An update step of executing a game based on data received from the client device and updating game information associated with the player identification information;
A game associated with the first address for accessing the member information management device, the second address for accessing the game system, and the player identification information based on predetermined data received from the client device A notification step for notifying the client device of link information including a takeover processing request link including unique takeover information for taking over the information;
Link information by the notification step is notified the client device, after performing member registration by accessing the member information management device based on the first address included in the link information, the member information management device Alternatively, the member identification information generated by the member information management device and the handover information for acquiring the handover information by accepting access based on the handover processing request link including the second address from either of the client devices. An acquisition step;
And a storage step of storing at least a part of the game information to be transferred by the acquired transfer information in association with the player identification information corresponding to the acquired member identification information. Control method. A computer that can be connected to a client device and a member information management device via communication.
Player identification information generating means for generating player identification information for identifying a player who operates the client device in response to a request from the client device;
Updating means for executing a game based on data received from the client device and updating game information associated with the player identification information;
A game associated with the first address for accessing the member information management device, the second address for accessing the game system, and the player identification information based on predetermined data received from the client device A notifying means for notifying the client device of link information including a takeover processing request link including unique takeover information for taking over the information;
Link information by the notifying means is notified the client device, after performing member registration by accessing the member information management device based on the first address included in the link information, the member information management device Alternatively, the member identification information generated by the member information management device and the handover information for acquiring the handover information by accepting access based on the handover processing request link including the second address from either of the client devices. Acquisition means;
A program for causing at least a part of game information to be transferred by the acquired transfer information to function as storage means for storing in association with player identification information corresponding to the acquired member identification information. Including a client device, a game server for controlling the game, and a member information management device,
The client device is
Request means for requesting the game server to start the game,
The game server
Player identification information generating means for generating player identification information for identifying a player corresponding to the client device in response to a request by the request means;
Updating means for executing the game based on data received from the client device and updating game information associated with the player identification information;
A game associated with the first address for accessing the member information management device, the second address for accessing the game system, and the player identification information based on predetermined data received from the client device A takeover processing request link including unique takeover information for taking over information , and a notification means for notifying the client device of link information including the link information,
The client device is
Further comprising registration request means for accessing the member information management device based on the first address included in the link information notified by the notification means, and requesting the member information management device to register user information. ,
The member information management device includes:
Member identification information generating means for generating member identification information for identifying a user whose information is registered in response to a request by the registration request means;
The game server
After the member identification information is generated by the member identification information generation means, an access based on the takeover processing request link including the second address is accepted from either the member information management device or the client device. , a member identification information the member information management device has generated, the takeover information acquiring means for acquiring the takeover information,
A storage means for storing at least part of the game information to be transferred by the acquired transfer information in association with the player identification information corresponding to the acquired member identification information; system.

Images