JP7511212B2 - Control method, control program, and server device - Google Patents

Description

The present invention relates to a server, its control program, and a system.

In recent years, servers that provide games to mobile terminals via communication networks have become widespread. Games provided by such servers include those in which multiple users can participate (so-called "social games"), and it is known that users can not only compete and cooperate with each other, but also communicate with each other (for example, Patent Document 1).

Also, as such a social game, for example, a game in which a player battles an enemy character using cards (so-called "card battle game") is known (for example, Patent Document 2). In a card battle game, a user cooperates with other users and battles an enemy character prepared in a game program using cards. A user can own any number of cards. A user also composes a deck using at least one card from the cards they own. Each card has parameters such as attack power, defense power, and vitality, and a user reduces the vitality parameter value of an enemy character based on the parameter value of a card that composes the deck. An enemy character also has parameters similar to those of a card, and reduces the vitality parameter value of a card based on this parameter value. By alternating attacks, the battle ends when the vitality parameter value of a card that composes the deck or the vitality parameter value of an enemy character becomes 0.

JP 2005-034303 A JP 2012-061059 A

However, in conventional social games, multiple users simply attack enemy characters, and communication between users after defeating the enemy character is neglected, and there is no mechanism to stimulate communication between users after defeating the enemy character. As a result, users may lose their motivation to continue playing the game.

The present invention was made to solve these problems, and aims to provide a server, its control program, and a system that can maintain and increase users' motivation to continue playing the game.

The server according to the present invention is a server that provides a service that allows users to be associated with each other, and includes a storage unit that stores, for each user receiving the service, the identification information of other users associated with that user, as well as the identification information of each event provided within the service and the identification information of each user participating in each event, a communication unit that communicates with each user's terminal, a transmission unit that transmits an event list including the identification information of each event to each user's terminal, a user registration unit that, when a participation request for an event selected from the event list is received from each user's terminal, stores the identification information of the user associated with that terminal in the storage unit, thereby allowing the user to participate in the event, an event progression unit that progresses the event when a request to progress the event is received from the terminal of each user participating in the event, and a user association unit that, when the event is finished, associates the identification information of each user who participated in the event with each other and stores it in the storage unit.

In addition, in the server according to the present invention, it is preferable that the users participating in the event are not associated with each other before the event ends.

In addition, in the server according to the present invention, when an event ends, the event progression unit transmits a user list including identification information of each user who participated in the event to the terminal of each user who participated in the event, and when a request for association with a user selected from the user list is received from the terminal of each user who participated in the event, the user association unit associates the identification information of the user related to the terminal with the identification information of the user selected from the user list and stores them in the memory unit, thereby associating the user related to the terminal with the user selected from the user list.

In addition, in the server according to the present invention, it is preferable that each user in the user list is ranked based on the degree of contribution to the progress of the event.

In addition, in the server according to the present invention, it is preferable that, among the users in the user list, those whose contribution to the progress of the event is greater than a threshold value are pre-selected.

In addition, in the server according to the present invention, when an event ends, it is preferable that the user association unit associates with each other the identification information of each user who participated in the event and whose contribution to the progress of the event is greater than a threshold value, and stores the associated information in the memory unit, thereby associating each of the users who participated in the event with each other.

The server control program according to the present invention is a server that provides a service that allows users to be associated with each other, and stores, for each user receiving the service, the identification information of other users associated with that user, and also has a storage unit that stores the identification information of each event provided within the service and the identification information of each user participating in each event, and causes the server to transmit an event list including the identification information of each event to each user's terminal, and when a request to participate in an event selected from the event list is received from each user's terminal, the server stores the identification information of the user associated with that terminal in the storage unit, thereby allowing the user to participate in the event, and when a request to progress the event is received from the terminal of each user participating in the event, the server progresses the event, and when the event is completed, the identification information of each user who participated in the event is stored in the storage unit in association with each other, thereby causing the server to execute association of each user who participated in the event.

The system according to the present invention is a system including a server that provides a service that allows users to be associated with each other, and a terminal of each user that receives the service. The server includes a storage unit that stores, for each user that receives the service, the identification information of other users associated with that user, and also stores the identification information of each event provided within the service and the identification information of each user participating in each event. The server includes a communication unit that communicates with each user's terminal, a transmission unit that transmits an event list including the identification information of each event to each user's terminal, a user registration unit that, when a participation request for an event selected from the event list is received from each user's terminal, stores the identification information of the user associated with the terminal in the storage unit, thereby allowing the user to participate in the event, an event progression unit that progresses the event when a request to progress the event is received from the terminal of each user that is participating in the event, and a user association unit that, when the event is finished, associates the identification information of each user that participated in the event with each other by storing them in the storage unit. The terminal includes a communication unit that communicates with the server, a reception unit that receives the event list, and a transmission unit that transmits the participation request and progress request to the server.

The server, its control program, and system of the present invention associate users who participated in the same event within the service with each other, thereby stimulating communication between users who have achieved the same goal, making it possible to maintain and increase users' desire to continue using the service, and keeping users attracted to the service.

FIG. 1 is a diagram illustrating an example of a schematic configuration of a game system. FIG. 2 is a diagram illustrating an example of a schematic configuration of a mobile terminal. FIG. 2 illustrates an example of a schematic configuration of a server. 4A to 4C are diagrams illustrating examples of data structures of various management tables. FIG. 13 is a diagram illustrating an example of a display screen of a mobile terminal. FIG. 11 is a diagram showing an example of an operation sequence of the game system. FIG. 11 illustrates an example of an operational flow of a server.

Various embodiments of the present invention will be described below with reference to the drawings. However, please note that the technical scope of the present invention is not limited to these embodiments, but extends to the inventions described in the claims and their equivalents.

(1) Overview of the Present Embodiment In the present embodiment, the server provides a service that allows communication between users. In particular, the server provides a community-type service called a social networking service (SNS). That is, the server transmits user information (e.g., name, diary, bulletin board, game progress, etc.) not only to the logged-in user but also to users who are friends with the logged-in user, enabling communication between users. Note that the server may provide the service only to users who have registered as members.

Each user can form a friend relationship with other users. When a friend request is received from one user to another user, the server associates the users with each other. For example, the server receives a friend request from user a's mobile device to user b. The server transmits the friend request from user a to user b's mobile device. Then, when an approval response to the friend request from user a is received from user b's mobile device, the server determines that a friend relationship between user a and user b has been established, and registers user b's identification information in association with user a's identification information, and registers user a's identification information in association with user b's identification information.

Each user can also post messages on the bulletin board. When the server receives a message posted on the bulletin board from user a's mobile device, it transmits a web page including the received message to user a's mobile device. The server also makes user a's message available to users who are friends of user a. For example, user a's message can be viewed by user b, who is also friends of user a, and user b can comment on and rate (e.g., "like") user a's message, allowing communication between users.

In this embodiment, the server also provides an online game service in which multiple users can participate. In particular, the server provides a card battle game service in which multiple users (preferably multiple users who are not associated with each other) cooperate to battle against an enemy character. In response to an instruction from a user, the mobile terminal requests the server to participate in a battle (event) against an enemy character. In response to a request from the mobile terminal, the server allows the user to participate in the battle. In addition, in response to a request from the mobile terminal, the server progresses the battle. Then, when the battle ends, the server associates the users who participated in the battle with each other.

(2) Configuration of Game System 1 FIG. 1 shows an example of a schematic configuration of the game system 1.

The game system 1 includes at least one mobile terminal 2 and a server 3. The mobile terminal 2 and the server 3 are connected to each other via a communication network, for example, via a base station 4, a mobile communication network 5, a gateway 6, and the Internet 7. A program executed on the mobile terminal 2 (e.g., a browsing program) and a program executed on the server 3 (e.g., a game program) communicate with each other using a communication protocol such as Hypertext Transfer Protocol (HTTP).

(2.1) Configuration of the Portable Terminal 2 FIG. 2 shows an example of a schematic configuration of the portable terminal 2.

The portable terminal 2 connects to the server 3 via a base station 4, a mobile communication network 5, a gateway 6, and the Internet 7, and communicates with the server 3. The portable terminal 2 requests the server 3 to proceed with the card battle game in response to a user's operation of an operation unit 23 (buttons, etc.). The portable terminal 2 also receives and displays display data relating to the progress of the card battle game from the server 3. To this end, the portable terminal 2 includes a device communication unit 21, a device memory unit 22, an operation unit 23, a display unit 24, and a device processing unit 25.

In this embodiment, the mobile terminal 2 is assumed to be a multi-function mobile phone (a so-called "smartphone"), but the present invention is not limited to this. The mobile terminal 2 may be any device to which the present invention is applicable, such as a mobile phone (a so-called "feature phone"), a personal digital assistant (PDA), a portable game machine, a portable music player, a tablet PC, etc.

The terminal communication unit 21 has a communication interface circuit including an antenna sensitive to a specific frequency band, and connects the mobile terminal 2 to a wireless communication network. The terminal communication unit 21 establishes a wireless signal line with the base station 4 using a method such as Code Division Multiple Access (CDMA) via a channel assigned by the base station 4, and communicates with the base station 4. The terminal communication unit 21 then transmits data supplied from the terminal processing unit 25 to the server 3, etc. The terminal communication unit 21 also supplies data received from the server 3, etc. to the terminal processing unit 25.

The terminal storage unit 22 includes at least one of a semiconductor memory, a magnetic disk device, and an optical disk device, for example. The terminal storage unit 22 stores an operating system program, a driver program, an application program, data, etc. used for processing in the terminal processing unit 25. For example, the terminal storage unit 22 stores, as driver programs, an input device driver program that controls the operation unit 23, an output device driver program that controls the display unit 24, etc. Furthermore, the terminal storage unit 22 stores, as application programs, programs that acquire and display display data related to the progress of the card battle game, etc. Furthermore, the terminal storage unit 22 stores, as data, display data, video data, image data, etc. related to the progress of the card battle game. Furthermore, the terminal storage unit 22 may temporarily store temporary data related to a predetermined process.

The operation unit 23 may be any device capable of operating the mobile terminal 2, such as a touchpad or a keyboard. A user can input characters, numbers, and the like using the operation unit 23. When operated by a user, the operation unit 23 generates a signal corresponding to the operation. The generated signal is then supplied to the device processing unit 25 as an instruction from the user.

The display unit 24 may be any device capable of displaying video, images, etc., such as a liquid crystal display or an organic EL (Electro-Luminescence) display. The display unit 24 displays video corresponding to video data supplied from the device processing unit 25, images corresponding to image data, etc.

The device processing unit 25 includes one or more processors and their peripheral circuits. The device processing unit 25 centrally controls the overall operation of the mobile device 2 and is, for example, a CPU (Central Processing Unit). The device processing unit 25 controls the operation of the device communication unit 21, the display unit 24, etc. so that various processes of the mobile device 2 are executed in an appropriate order according to the programs stored in the device storage unit 22, the operation of the operation unit 23, etc. The device processing unit 25 executes processes based on the programs (operating system programs, driver programs, application programs, etc.) stored in the device storage unit 22. The device processing unit 25 can also execute multiple programs (application programs, etc.) in parallel.

(2.1.1) Configuration of the device processing unit 25 The device processing unit 25 includes at least a browsing execution unit 251. Each of these units is a functional module realized by a program executed by a processor included in the device processing unit 25. Alternatively, each of these units may be implemented in the mobile device 2 as firmware.

The browsing execution unit 251 acquires and displays display data related to the progress of the card battle game. That is, in response to instructions from the user, it transmits a request to acquire display data related to the progress of the card battle game to the server 3 via the device communication unit 21. The browsing execution unit 251 also receives corresponding display data from the server 3 via the device communication unit 21. The browsing execution unit 251 creates drawing data based on the received display data. That is, the browsing execution unit 251 analyzes the received display data to identify control data and content data, lays out the identified content data according to the identified control data, and creates drawing data. The browsing execution unit 251 then outputs the created drawing data to the display unit 24.

(2.2) Configuration of Server 3 FIG. 3 shows an example of a schematic configuration of the server 3.

The server 3 progresses the card battle game in response to a request from the mobile device 2. The server 3 also creates display data related to the progress of the card battle game and transmits it to the mobile device 2. To this end, the server 3 includes a server communication unit 31, a server storage unit 32, and a server processing unit 33.

The server communication unit 31 includes a communication interface circuit for connecting the server 3 to the Internet 7, and communicates with the Internet 7. The server communication unit 31 then supplies data received from the mobile terminal 2 or the like to the server processing unit 33. The server communication unit 31 also transmits data supplied from the server processing unit 33 to the mobile terminal 2 or the like.

The server storage unit 32 includes, for example, at least one of a magnetic tape device, a magnetic disk device, and an optical disk device. The server storage unit 32 stores an operating system program, a driver program, an application program, data, and the like used in the processing in the server processing unit 33. For example, the server storage unit 32 stores, as an application program, a card battle game program that progresses a card battle game and creates display data related to the results. The server storage unit 32 also stores, as data, a battle management table (FIG. 4(a)) that manages battles, an enemy management table (FIG. 4(b)) that manages enemy characters, a user management table (FIG. 4(c)) that manages users, a card management table (FIG. 4(d)) that manages cards, and an association management table (FIG. 4(e)) that manages associations between users. The server storage unit 32 may also temporarily store temporary data related to a predetermined process.

Figure 4 shows an example of the data structure of various management tables.

Figure 4 (a) shows an example of the data structure of a battle management table that manages battles. For each battle, the battle management table includes the battle's identification number (ID), name, end date and time, enemy character ID and stamina parameters (current values), participating user IDs and number of attacks, etc.

Figure 4 (b) shows an example of the data structure of an enemy management table that manages enemy characters. For each enemy character, the enemy management table includes parameters such as the enemy character's ID, name, image data file name, attack power, defense power, and stamina (initial value).

Figure 4 (c) shows an example of the data structure of a user management table that manages users. For each user, the user management table includes the user's ID, name, image data file name, parameters such as stamina, IDs of owned cards, IDs of owned cards that make up the deck, stamina parameters (current values), and IDs of associations to which the user belongs.

Figure 4 (d) shows an example of the data structure of a card management table that manages cards. The card management table includes, for each card, parameters such as the card's ID, name, image data file name, attack power, defense power, and stamina (initial value).

Figure 4 (e) shows an example of the data structure of an association management table that manages associations between users. For each association, the association management table includes the ID of the association, the ID of the user to which it belongs, etc.

The server processing unit 33 includes one or more processors and their peripheral circuits. The server processing unit 33 centrally controls the overall operation of the server 3, and is, for example, a CPU. The server processing unit 33 controls the operation of the server communication unit 31, etc., so that various processes of the server 3 are executed in an appropriate order according to the programs, etc. stored in the server storage unit 32. The server processing unit 33 executes processes based on the programs (operating system programs, driver programs, application programs, etc.) stored in the server storage unit 32. The server processing unit 33 can also execute multiple programs (application programs, etc.) in parallel.

(2.2.1) Configuration of the server processing unit 33 The server processing unit 33 includes a control unit 331, a user participation unit 332, a battle progression unit 333, and a user association unit 334. Each of these units is a functional module realized by a program executed by a processor included in the server processing unit 33. Alternatively, each of these units may be implemented in the server 3 as firmware.

The processing performed by the control unit 331 is described below.

The control unit 331 controls the progress of the card battle game and instructs the user participation unit 332, the battle progress unit 333, the user association unit 334, etc. to execute processing as appropriate.

When a user authentication request is received from the mobile device 2 via the server communication unit 31, the control unit 331 analyzes the received user authentication request to identify the user ID and password. Then, the control unit 331 instructs the user authentication unit (not shown) to execute processing using the identified user ID and password as parameters.

When the user is authenticated by a user authentication unit (not shown), the control unit 331 creates home screen display data. That is, the control unit 331 references the match management table stored in the server storage unit 32, and identifies matches whose end date and time have not yet passed. The control unit 331 also extracts the ID, name, and end date and time of the identified match. The control unit 331 then creates home screen display data that includes the extracted match ID, the identified user ID, etc., and that displays the extracted match name and end date and time, a button for receiving an instruction to participate in a match, etc., in a predetermined layout.

The control unit 331 transmits the created home screen display data to the mobile device 2 via the server communication unit 31.

Figure 5 shows an example of a display screen of the mobile device 2.

Figure 5 (a) shows a home screen 500 that is displayed based on the home screen display data. For each match, the name of the match and the end date and time 501, 503 are displayed on the left side of the screen, and "Join" buttons 502, 504 are displayed on the right side of the screen. Pressing the "Join" buttons 502, 504 requests participation in the corresponding match from the server 3 via the device communication unit 21.

When a request to join a battle is received from the mobile device 2 via the server communication unit 31, the control unit 331 instructs the user participation unit 332 to execute processing using the received battle participation request as a parameter.

In addition, when a match progress request is received from the mobile device 2 via the server communication unit 31, the control unit 331 instructs the match progress unit 333 to execute processing using the received match progress request as a parameter.

Furthermore, when a user association request is received from the mobile device 2 via the server communication unit 31, the control unit 331 instructs the user association unit 334 to execute processing using the received user association request as a parameter.

The control unit 331 transmits the created battle screen display data, etc. to the mobile device 2 via the server communication unit 31.

The processing performed by the user participation unit 332 is described below.

The user participation unit 332 allows the user to participate in a battle. That is, the user participation unit 332 analyzes the given battle participation request to identify the battle ID and the user ID. The user participation unit 332 also uses the identified battle ID as a key to refer to the battle management table stored in the server storage unit 32 and identifies the corresponding battle. The user participation unit 332 then adds the identified user ID to the IDs of the users participating in the identified battle.

The user participation unit 332 creates battle screen display data. That is, the user participation unit 332 extracts the ID and vitality parameters of the enemy character of the specified battle. The user participation unit 332 also refers to the enemy management table stored in the server storage unit 32 using the extracted enemy ID as a key, and extracts the file name of the image data of the corresponding enemy character. The user participation unit 332 also refers to the user management table stored in the server storage unit 32 using the specified user ID as a key, and extracts the corresponding user's vitality parameters and the IDs of the owned cards that make up the deck. The user participation unit 332 also refers to the card management table stored in the server storage unit 32 using the extracted card ID as a key, and extracts the file name of the image data of the corresponding card. The user participation unit 332 then creates battle screen display data that includes the specified battle ID, user ID, etc., and that displays the extracted enemy character vitality parameters, user vitality parameters, an image indicated by the file name, a button for receiving an instruction to execute an attack, etc., in a predetermined layout.

Then, the user participation unit 332 ends the processing.

Figure 5 (b) shows a battle screen 510 displayed based on the battle screen display data. An enemy character image 511 and a strength parameter gauge 512 are displayed at the top of the screen, while images 513-515 of cards that make up the deck and a user's strength parameter gauge 516 are displayed at the bottom of the screen. In addition, multiple buttons are displayed at the bottom of the screen, and pressing an "attack" button 517 requests the server 3 to execute an attack via the device communication unit 21.

The processing performed by the battle progression unit 333 is explained below.

The match progression unit 333 determines whether the end date and time of the match has passed. That is, the match progression unit 333 analyzes the match progression request given to identify the match ID, instruction content, and user ID. The match progression unit 333 also uses the identified match ID as a key to refer to the match management table stored in the server storage unit 32 to identify the corresponding match. The match progression unit 333 then determines whether the end date and time of the identified match has passed.

If the end date and time of the specified match has not passed, the match progression unit 333 progresses the match according to the specified instruction content. That is, if the specified instruction content is "perform an attack," the match progression unit 333 executes an attack process.
For example, the battle progression unit 333 uses the identified battle ID as a key to refer to the battle management table stored in the server storage unit 32 and identifies the corresponding battle. The battle progression unit 333 then extracts the ID and vitality parameters of the enemy character in the identified battle. The battle progression unit 333 also uses the extracted enemy ID as a key to refer to the enemy management table stored in the server storage unit 32 and extracts parameters such as the attack power and defense power of the corresponding enemy character.
Similarly, the battle progression unit 333 uses the identified user ID as a key to refer to the user management table stored in the server storage unit 32 and identifies the corresponding user. The battle progression unit 333 then extracts the IDs and vitality parameters of the owned cards that make up the deck of the identified user. The battle progression unit 333 also uses the extracted card ID as a key to refer to the card management table stored in the server storage unit 32 and extracts parameters such as the attack power and defense power of the corresponding card.
The battle progression unit 333 then performs a battle simulation based on the extracted enemy character parameters and card parameters. For example, the battle progression unit 333 reduces the enemy character's vitality parameter value based on the card's attack power parameter value and the enemy character's defense power parameter value. Similarly, the battle progression unit 333 reduces the card's vitality parameter value based on the enemy character's attack power parameter value and the card's defense power parameter value.
The battle progression unit 333 updates the vitality parameters of the enemy character in the identified battle. The battle progression unit 333 also increments (+1) the number of attacks of the user corresponding to the identified user ID among the users participating in the identified battle. Similarly, the battle progression unit 333 updates the vitality parameters of the owned cards that make up the deck of the identified user.

The battle progression unit 333 determines whether the updated stamina parameter value of the enemy character has become 0. If the updated stamina parameter value of the enemy character is not 0, the battle progression unit 333 creates battle screen display data. That is, the battle progression unit 333 extracts the ID and stamina parameter of the enemy character of the specified battle. Furthermore, the battle progression unit 333 uses the extracted enemy ID as a key to refer to the enemy management table stored in the server storage unit 32 and extracts the file name of the image data of the corresponding enemy character. Furthermore, the battle progression unit 333 extracts the stamina parameter of the specified user and the ID of the owned card that constitutes the deck. Furthermore, the battle progression unit 333 uses the extracted card ID as a key to refer to the card management table stored in the server storage unit 32 and extracts the file name of the image data of the corresponding card. The battle progression unit 333 then creates battle screen display data that includes the identified battle ID, user ID, etc., and that displays the extracted enemy character's vitality parameters, the user's vitality parameters, an image indicated by the file name, buttons for receiving instructions to execute an attack, etc., in a predetermined layout.

On the other hand, when the updated stamina parameter value of the enemy character becomes 0, the battle progression unit 333 creates user selection screen display data. That is, the battle progression unit 333 extracts the IDs and number of attacks of the users participating in the specified battle. The battle progression unit 333 also uses the extracted participating user ID as a key to refer to the user management table stored in the server storage unit 32 and extracts the name of the corresponding participating user and the file name of the image data. The battle progression unit 333 then creates user selection screen display data for displaying the names and images of the extracted participating users in descending order of the number of attacks, including the extracted participating user ID and the specified user ID, and displaying the display area, check boxes for receiving instructions to select participating users, buttons for receiving instructions to associate users, etc., in a predetermined layout.

In addition, if the end date and time of the specified match has passed, the match progress unit 333 creates user selection screen display data.

On the other hand, if the identified instruction content is something else, the battle progression unit 333 executes processing related to the identified instruction content.

Then, the match progression unit 333 ends the processing.

Figure 5 (c) shows a user selection screen 520 that is displayed based on the user selection screen display data. On the left side of the screen, images and names 521, 523, 525 of users who participated in the match are displayed in descending order of their contribution to the match (e.g., number of attacks). Also, check boxes 522, 524, 526 are displayed on the right side of the screen, and checking one of them selects the corresponding participating user. Furthermore, a "Confirm" button 527 is displayed at the bottom of the screen, and pressing this button requests the server 3 to associate the users with each other via the device communication unit 21.

The processing performed by the user association unit 334 is described below.

The user association unit 334 determines whether one or more participating users have been selected. That is, the user association unit 334 analyzes the provided user association request to identify the participating user ID and the user ID. Then, the user association unit 334 determines whether one or more participating user IDs have been identified.

When one or more participating users are selected, the user association unit 334 associates the user with the participating users. That is, when one or more participating user IDs are specified, the user association unit 334 assigns a number to the association ID, associates it with the participating user ID and the user ID, etc., and adds it to the association management table stored in the server storage unit 32. The user association unit 334 also refers to the user management table stored in the server storage unit 32 using the specified participating user ID as a key, and adds the assigned association ID to the association ID to which the corresponding participating user belongs. Similarly, the user association unit 334 refers to the user management table stored in the server storage unit 32 using the specified user ID as a key, and adds the assigned association ID to the association ID to which the corresponding user belongs.

The user association unit 334 creates match end screen display data. That is, the user association unit 334 creates match end screen display data that includes the identified user ID, etc., and displays text indicating that the match has ended, text indicating that the user is associated with a user who participated in the match, a button for receiving an instruction to transition to the home screen, etc., in a predetermined layout.

On the other hand, if no participating users have been selected, the user association unit 334 creates match end screen display data. That is, the user association unit 334 creates match end screen display data that includes the identified user ID, etc., and displays text indicating that the match has ended, a button for receiving an instruction to transition to the home screen, etc., in a predetermined layout.

Then, the user association unit 334 ends the process.

Figure 5 (d) shows a match end screen 530 that is displayed based on the match end screen display data. At the top of the screen, text 531 indicating that the match has ended and text 532 indicating that the user has been associated with users 3 and 4 who participated in the match are displayed, and at the bottom of the screen, a "back" button 533 is displayed; pressing the "back" button 533 requests the server 3 via the device communication unit 21 to transition to the home screen.

(3) Operation of Game System 1 Fig. 6 is a diagram showing an example of an operation sequence of the game system 1. In the operation sequence described below, users a and b are assumed to be users, the portable terminal 2 of user a is the portable terminal 2a, and the portable terminal 2 of user b is the portable terminal 2b. The operation sequence is executed mainly by the device processing units 25a and 25b and the server processing unit 33 in cooperation with the respective elements of the portable terminals 2a and 2b and the server 3, based on programs previously stored in the device storage units 22a and 22b and the server storage unit 32.

User a instructs the device processing unit 25a via the operation unit 23a to execute a program that acquires and displays display data related to the progress of the card battle game. The device processing unit 25a starts processing based on the program. That is, when a user ID and password are input by user a via the operation unit 23a, the browsing execution unit 251a realized by the program transmits a user authentication request including the input user ID, password, etc. to the server 3 via the device communication unit 21a (step S600).

When a user authentication request is received from the mobile device 2a via the server communication unit 31, the control unit 331 analyzes the received user authentication request to identify the user ID and password. Then, the control unit 331 instructs the user authentication unit (not shown) to execute authentication processing for user a using the identified user ID and password as parameters (step S602).

When user a is authenticated by a user authentication unit (not shown), the control unit 331 creates home screen display data for user a (step S604).

The control unit 331 transmits the created home screen display data to the mobile device 2a via the server communication unit 31 (step S606).

When home screen display data is received from the server 3 via the device communication unit 21a, the browsing execution unit 251a creates drawing data based on the received home screen display data. The browsing execution unit 251a also outputs the created drawing data to the display unit 24a to display the home screen (step S608).

When user a issues an instruction to participate in a match via operation unit 23a on the home screen, viewing execution unit 251a transmits a match participation request including the user ID included in the received home screen display data, a match ID corresponding to the match, etc., to server 3 via device communication unit 21a (step S610).

When a request to join a battle is received from the mobile device 2a via the server communication unit 31, the control unit 331 instructs the user participation unit 332 to execute processing using the received request to join a battle as a parameter (step S612).

Figure 7 (a) shows an example of the operation flow of the user participation unit 332.

The user participation unit 332 allows the user to participate in the battle (step S700).

The user participation unit 332 also creates battle screen display data (step S702).

Then, the user participation unit 332 ends the processing.

Returning to FIG. 6, the control unit 331 transmits the created battle screen display data to the mobile device 2a via the server communication unit 31 (step S614).

When battle screen display data is received from the server 3 via the device communication unit 21a, the viewing execution unit 251a creates drawing data based on the received battle screen display data. The viewing execution unit 251a also outputs the created drawing data to the display unit 24a, causing the battle screen to be displayed (step S616).

When user a issues an instruction to execute an attack or the like on the battle screen via the operation unit 23a, the viewing execution unit 251a transmits a battle progress request including the battle ID and user ID, instruction content, etc., contained in the received battle screen display data to the server 3 via the device communication unit 21a (step S618).

When a match progress request is received from the mobile device 2a via the server communication unit 31, the control unit 331 instructs the match progress unit 333 to execute processing using the received match progress request as a parameter (step S620).

Figure 7 (b) shows an example of the operation flow of the battle progression unit 333.

The match progress unit 333 determines whether the match end date and time has passed (step S710).

Then, if the end date and time of the identified match has not passed (step S710-No), the match progression unit 333 progresses the match according to the identified instruction content.

In other words, if the identified instruction content is "perform an attack" (step S712-Yes), the battle progression unit 333 executes the attack process (step S714).

The battle progression unit 333 also determines whether the updated enemy character's physical strength parameter value has become 0 (step S716).

Then, if the updated stamina parameter value of the enemy character is not 0 (step S716-No), the battle progression unit 333 creates battle screen display data (step S718).

On the other hand, if the updated stamina parameter value of the enemy character becomes 0 (step S716-Yes), the battle progression unit 333 creates user selection screen display data (step S720).

Also, if the end date and time of the identified match has passed (step S710-Yes), the match progression unit 333 creates user selection screen display data (step S720).

On the other hand, if the identified instruction content is something else (step S712-No), the battle progression unit 333 executes processing related to the identified instruction content (step S722).

Then, the match progression unit 333 ends the processing.

Returning to FIG. 6, if the match has not ended, the control unit 331 transmits the created match screen display data to the mobile device 2a via the server communication unit 31 (step S622).

On the other hand, when a request to join a battle is received from the mobile device 2b via the server communication unit 31, the control unit 331 instructs the user participation unit 332 to execute processing using the received request to join a battle as a parameter (step S624).

The control unit 331 transmits the created battle screen display data to the mobile device 2a via the server communication unit 31 (step S626).

When battle screen display data is received from the server 3 via the device communication unit 21a, the viewing execution unit 251a creates drawing data based on the received battle screen display data. The viewing execution unit 251a also outputs the created drawing data to the display unit 24a, causing the battle screen to be displayed (step S628).

When user a issues an instruction to execute an attack or the like on the battle screen via the operation unit 23a, the viewing execution unit 251a transmits a battle progress request including the battle ID, user ID, instruction content, etc. contained in the received battle screen display data to the server 3 via the device communication unit 21a (step S630).

When a match progress request is received from the mobile device 2a via the server communication unit 31, the control unit 331 instructs the match progress unit 333 to execute processing using the received match progress request as a parameter (step S632).

When the match ends, the control unit 331 transmits the created user selection screen display data to the mobile device 2a via the server communication unit 31 (step S634).

When user selection screen display data is received from the server 3 via the device communication unit 21a, the browsing execution unit 251a creates drawing data based on the received user selection screen display data. In addition, the browsing execution unit 251a outputs the created drawing data to the display unit 24a, causing the user selection screen to be displayed (step S636).

When user a instructs association between users via the operation unit 23a on the user selection screen, the browsing execution unit 251a transmits a user association request including the user ID included in the received user selection screen display data, the participating user ID corresponding to the selected participating user, etc., to the server 3 via the terminal communication unit 21a (step S638).

When a user association request is received from the mobile device 2a via the server communication unit 31, the control unit 331 instructs the user association unit 334 to execute processing using the received user association request as a parameter (step S640).

Figure 7 (c) is a diagram showing an example of the operation flow of the user association unit 334.

The user association unit 334 determines whether one or more participating users have been selected (step S730).

Then, if one or more participating users are selected (step S730-Yes), the user association unit 334 associates the user with the participating users (step S732).

The user association unit 334 also creates match end screen display data (step S734).

On the other hand, if no participating users have been selected (step S730-No), the user association unit 334 creates match end screen display data (step S736).

Then, the user association unit 334 ends the process.

Returning to FIG. 6, the control unit 331 transmits the created battle end screen display data to the mobile device 2a via the server communication unit 31 (step S642).

When the match end screen display data is received from the server 3 via the device communication unit 21a, the viewing execution unit 251a creates drawing data based on the received match end screen display data. The viewing execution unit 251a also outputs the created drawing data to the display unit 24a, causing the match end screen to be displayed (step S644).

As explained above, by linking users who participated in the same match within a game, communication between users who achieved the same goal is stimulated, which makes it possible to maintain and increase users' motivation to continue playing the game, and keeps users attracted to the service.

Note that the present invention is not limited to this embodiment. For example, in this embodiment, the names of users who participated in the match on the user selection screen are displayed in descending order of their contribution to the match, and the number of attacks is used as the contribution, but other contributions may be used. For example, the number of times a match was participated in, the reduction amount of the enemy character's vitality parameter value, the number of times an item was used, etc. may be used. Also, any criteria may be used, not limited to the contribution to the match. Furthermore, any criteria may be set. This makes it easier to associate with desired users, and is expected to further increase motivation to continue.

In this embodiment, the users to be associated are manually selected on the user selection screen (by manually checking the corresponding checkbox), but they may be automatically selected based on a predetermined criterion and the corresponding checkbox may be automatically checked. Alternatively, only the selected users may be displayed. Furthermore, the association may be performed automatically without querying the user via the user selection screen. As the predetermined criterion, for example, the contribution to the match is greater than a threshold value, the user's attributes are predetermined attributes, the number, type, and attributes of owned cards, items, etc. may be predetermined, and so on. Any criterion may also be set. This makes it easier to associate with desired users, and is expected to further increase motivation to continue.

In addition, although the present embodiment does not specifically limit the number of users that can participate in one match, it may be possible to limit it. Alternatively, multiple mutually independent groups may be managed for one match, and when the number of users participating in one group reaches a threshold value (e.g., 20 users), a new group may be created and new users may participate in that group. This can reduce/distribute the load, improve stability, reduce operating costs, etc.

In addition, in this embodiment, the invention is applied to a card battle game, but it may also be applied to other games or services with similar mechanisms, not limited to card battle games.

In addition, computer programs for causing a computer to realize each function provided by the terminal processing unit 25 and the server processing unit 33 may be provided in a form recorded on a computer-readable recording medium such as a magnetic recording medium or an optical recording medium.

It should be understood by those skilled in the art that various changes, substitutions, and modifications can be made thereto without departing from the spirit and scope of the present invention.

REFERENCE SIGNS LIST 1 Game system 2 Mobile terminal 21 Terminal communication unit 22 Terminal storage unit 23 Operation unit 24 Display unit 25 Terminal processing unit 251 View execution unit 3 Server 31 Server communication unit 32 Server storage unit 33 Server processing unit 331 Control unit 332 User participation unit 333 Battle progression unit 334 User association unit 4 Base station 5 Mobile communication network 6 Gateway 7 Internet

Claims (12)

A method for controlling a terminal of a first user among a plurality of users who can participate in a battle event, comprising:
The terminal,
Transmitting, in response to a first operation by the first user, identification information of the first user and a participation request for allowing the first user to participate in the battle event;
When the battle event in which the first user participated has ended, displaying a user list of one or more second users other than the first user who participated in the battle event;
Including,
the second user is a user automatically selected from among users other than the first user who participated in the battle event,
In displaying the user list, the terminal
displaying , on the same first screen, options for the first user to select whether or not to transmit a request to associate the second user with the first user, and the user list;
the user list does not include users who do not satisfy a predetermined condition among users other than the first user who participated in the battle event ;
A control method comprising: A method for controlling a terminal of a first user among a plurality of users who can participate in a battle event, comprising:
The terminal,
Transmitting, in response to a first operation by the first user, identification information of the first user and a participation request for allowing the first user to participate in the battle event;
When the battle event in which the first user participated has ended, displaying a user list of one or more second users other than the first user who participated in the battle event;
Including,
the second user is a user automatically selected from among users other than the first user who participated in the battle event,
In displaying the user list, the terminal
displaying, on the same first screen, the user list in which each of the second users is arranged based on the number of attacks made by each of the second users in the battle event, the number of times each of the second users used an item in the battle event, or the amount of reduction made by each of the second users in the battle event of an opponent, and options for the first user to select whether or not to transmit a request to associate the second user with the first user;
A control method comprising: The control method according to claim 1 or 2, wherein each of the options corresponding to each of the second users is displayed differently depending on whether or not the selection is instructed by the first user. The control method according to claim 1 , wherein the user list includes an image or a name of each of the second users corresponding to each of the options. The terminal,
transmitting a change instruction to change a parameter value of an opponent in the battle event in response to a second operation by the first user;
receiving information indicative of the parameter value that has been changed;
receiving information regarding the end of the battle event, the information being transmitted when an end condition regarding the parameter value is satisfied;
The control method according to any one of claims 1 to 4 , comprising: The terminal,
receiving information regarding one or more of the ongoing competitive events for which the termination condition has not been satisfied;
displaying a second screen on which the first operation can be performed to instruct transmission of the participation request for one or more of the ongoing battle events for which the end condition has not been satisfied;
The control method of claim 5 , comprising: transmitting, by the terminal, a request to associate the first user with the second user selected in response to the operation of the option by the first user;
Including,
The control method according to claim 1 , wherein the first user and the second user are associated with each other based on an authorization response by the second user to which association with the first user is requested. the terminal sending a message viewable by the second user associated with the first user;
The control method of claim 7 , comprising: A control program for a terminal of a first user among a plurality of users who can participate in a battle event,
The terminal,
Transmitting, in response to a first operation by the first user, identification information of the first user and a participation request for allowing the first user to participate in the battle event;
When the battle event in which the first user participated has ended, displaying a user list of one or more second users other than the first user who participated in the battle event;
Run the command,
the second user is a user automatically selected from among users other than the first user who participated in the battle event,
In displaying the user list, the terminal
displaying, on the same first screen, an option for the first user to select whether or not to transmit a request to associate the second user with the first user, and the user list ;
Run the command ,
the user list does not include users who do not satisfy a predetermined condition among users other than the first user who participated in the battle event ;
A control program comprising: A control program for a terminal of a first user among a plurality of users who can participate in a battle event,
The terminal,
Transmitting, in response to a first operation by the first user, identification information of the first user and a participation request for allowing the first user to participate in the battle event;
When the battle event in which the first user participated has ended, displaying a user list of one or more second users other than the first user who participated in the battle event;
Run the command,
the second user is a user automatically selected from among users other than the first user who participated in the battle event,
In displaying the user list, the terminal
displaying, on the same first screen, the user list in which each of the second users is arranged based on the number of attacks made by each of the second users in the battle event, the number of times each of the second users used an item in the battle event, or the amount of reduction made by each of the second users in the battle event of an opponent, and options for the first user to select whether or not to transmit a request to associate the second user with the first user;
A control program for causing the user to execute the above steps. A terminal of a first user among a plurality of users who can participate in a battle event,
Transmitting, in response to a first operation by the first user, identification information of the first user and a participation request for allowing the first user to participate in the battle event;
a processing unit that, when the battle event in which the first user participated has ended, displays a user list of one or more second users other than the first user who participated in the battle event;
the second user is a user automatically selected from among users other than the first user who participated in the battle event,
The processing unit, in displaying the user list,
displaying , on the same first screen, options for the first user to select whether or not to transmit a request to associate the second user with the first user, and the user list;
the user list does not include users who do not satisfy a predetermined condition among users other than the first user who participated in the battle event ;
A server device comprising: A terminal of a first user among a plurality of users who can participate in a battle event,
Transmitting, in response to a first operation by the first user, identification information of the first user and a participation request for allowing the first user to participate in the battle event;
a processing unit that displays, when the battle event in which the first user participated has ended, a user list of one or more second users other than the first user who participated in the battle event.
Equipped with
the second user is a user automatically selected from among users other than the first user who participated in the battle event,
The processing unit, in displaying the user list,
displaying, on the same first screen, the user list in which each of the second users is arranged based on the number of attacks made by each of the second users in the battle event, the number of times each of the second users used an item in the battle event, or the amount of reduction made by each of the second users in the battle event of an opponent, and options for the first user to select whether or not to transmit a request to associate the second user with the first user;
A server device comprising:

Images