Program, server system, and entertainment system
Patent Information
- Application Number
- JP2024229667
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-12-26
- Publication Date
- 2025-03-14
- Estimated Expiration
- 2040-12-11
Smart Images

Figure 2025036604000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a program for executing a game having an associated user registration function. [Background technology]
[0002] In video games, a friend registration function is known as a function that allows other users to be registered as related users. For example, Patent Document 1 discloses a technology that manages friends according to whether they are distant or not, and displays a friend effect according to whether they are distant or not. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2011-206484 A Summary of the Invention [Problem to be solved by the invention]
[0004] In the technology of Patent Document 1, related users (friends) are classified according to whether they are distant or not, but a technology for classifying and managing related users (friends) by defining the degree of intimacy, etc., is also known as a conventional technology. However, in any of the conventional technologies, the classification technology for related users determines and classifies the degree of association between users only in a virtual space (cyberspace, game space). Also, although the example of a video game has been described, in other applications such as SNS (Social Networking Service), the same determination and classification method is used for related users.
[0005] The problem to be solved by the present invention is to provide a technique for realizing a related user classification method different from the conventional one. [Means for solving the problem]
[0006] A first invention for solving the above problem is a program for causing a user terminal of a user to execute an application having a related user registration function capable of registering other users as related users with whom the user is involved, the program comprising: a first type related user registration means (e.g., a first type related user registration unit 231 in FIG. 19 ) for registering, as the first type related user, the other users who satisfy a first condition for being able to be registered as a first type related user; a second type related user registration means (e.g., a second type related user registration unit 233 in FIG. 19 ) for registering, as the second type related user, the other users who satisfy a second condition, which is different from the first condition, for being able to be registered as a second type related user; and a related action in the application which is an action involving related users, the related action including: 1) an action involving the first type related user without involving the second type related user; the second type related user registration means has a confirmation process execution control means (e.g., a confirmation process execution control unit 235 shown in FIG. 19) that executes a confirmation process including attempting a specified communication with the terminal of the other user as a specified confirmation process defined to confirm that the other user is within a specified distance range, and the second type related user registration means causes the user terminal to function as a related action control means (e.g., a related game play control unit 241 in FIG. 19) that controls the execution of the other user's terminal based on a first type action control when the other user is involved in the game, and 2) a related action based on a second type action control when the other user is not involved in the game but the second type related user is involved, and the second type related user registration means has a confirmation process execution control means (e.g., a confirmation process execution control unit 235 shown in FIG. 19) that executes a confirmation process including attempting a specified communication with the terminal of the other user as a destination, as a specified confirmation process defined to confirm that the other user is within a specified distance range, and determines whether the second condition is satisfied by including in the second condition that the other user has been confirmed by the confirmation process.
[0007] According to the first invention, various related users who are related to the user can be registered, with other users who satisfy the first condition as first-type related users and other users who satisfy a second condition different from the first condition as second-type related users. Then, for the second-type related users, it is possible to determine that the second condition includes confirmation that the user is within a predetermined distance range from the user, and to register the user. In addition, for related actions involving related users, different action controls (first-type action control or second-type action control) can be performed for related actions involving first-type related users and related actions involving second-type related users to control their execution. Therefore, it is possible to realize a method of classifying related users that is different from the conventional method.
[0008] Further, a second invention is a program of the first invention, in which the related action control means 3) controls the execution of related actions based on a third type action control when the first type related user and the second type related user are involved.
[0009] According to the second invention, when a first type related user and a second type related user are involved in a related action involving related users, a third type action control can be performed to control the execution of the related action.
[0010] In addition, the third invention is a program of the first or second invention for causing the user terminal to further function as a privilege-granting control means (e.g., the privilege-granting control unit 239 in Figure 19) that controls the granting of a given privilege to a second type related user and / or the own user when a new second type related user is registered by the second type related user registration means.
[0011] According to the third invention, when another user is registered as a second type related user of the user, a benefit can be given to the user and the registered other user. Therefore, for example, when the application is a game application, it is possible to encourage users who play the game to register as second type related users.
[0012] In addition, a fourth invention is a program of the third invention, which further causes the user terminal to function as a registration deletion means (e.g., the registration deletion unit 237 in Figure 19) for deregistering the second type related user, and the bonus granting control means grants the bonus only when the other user who has not been registered as the second type related user in the past is newly registered as the second type related user by the second type related user registration means.
[0013] According to the fourth invention, if a user who has been registered as a second type related user in the past and whose registration has since been deleted is registered again as a second type related user, it is possible to prevent the user from being granted benefits.
[0014] Further, a fifth invention is a program of any of the first to fourth inventions, further causing the user terminal to function as a registration deregistration means for deregistrating the registration of the second type related user, and the second type related user registration means registers, as the second type related user, another user who was previously registered as the second type related user and who satisfies the first condition.
[0015] According to the fifth invention, if a user who was previously registered as a second type related user and whose registration was subsequently deleted satisfies the first condition for being able to be registered as a first type related user, it is possible to register the user as a second type related user rather than a first type related user.
[0016] Further, a sixth invention is a program of any of the first to fifth inventions, in which the confirmation process execution control means executes the confirmation process, including controlling the display of a given registration identifier on the user terminal and receiving information of the registration identifier from the other user's terminal.
[0017] According to the sixth invention, for example, when one of the user and the other user displays a registration identifier on his / her terminal (user terminal) and the other user performs a procedure to have his / her terminal (user terminal) read the registration identifier, it becomes possible to confirm that the other user is within a specified distance range and to register the other user as a second type related user.
[0018] Further, a seventh invention is a program of any of the first to sixth inventions, wherein the user terminal is equipped with a positioning unit (e.g., positioning module 1555 in FIG. 2), and the confirmation process execution control means executes the confirmation process including communication to acquire other user positions from the other user's terminals, and determining that the distance between the acquired other user positions and the positioning position by the positioning unit is within the distance range.
[0019] According to the seventh invention, the positioning unit determines the user position of the user itself, and also obtains the user positions of other users, and it is possible to confirm that the other users are within a predetermined distance range based on the distance between the user positions.
[0020] Further, an eighth invention is a program of the seventh invention, in which the second type related user registration means registers the second type related user in association with the acquired other user positions related to the second type related user.
[0021] According to the eighth aspect of the present invention, when a second type related user is registered, the user position of the second type related user acquired during the registration can be recorded. In other words, the user position of the second type related user when the user is confirmed to be within a predetermined distance range from the user and registered as a second type related user can be recorded.
[0022] Further, a ninth invention is a program of the seventh or eighth invention, in which the second type related user registration means communicates to obtain a first type related user position from the terminal of the first type related user, and if the distance between the first type related user position and the position measured by the positioning unit is within the distance range, registers the first type related user as the second type related user.
[0023] According to the ninth invention, when a user registered as a first type related user is within a predetermined distance range, it is possible to change the registration of the user from being registered as a first type related user to being registered as a second type related user.
[0024] Further, a tenth invention is a program of any of the seventh to ninth inventions, in which the second type related user registration means registers the second type related users in multiple stages depending on the elapsed time during which the distance between the other user's position and the position determined by the positioning unit is within the distance range.
[0025] According to the tenth invention, when registering second type related users by confirming that other users are within a predetermined distance range based on the distance between user positions, it is possible, for example, to rank the second type related users based on the length of time they spent within that distance range.
[0026] An eleventh invention is the program according to any one of the first to tenth inventions, wherein the predetermined communication is short-distance wireless communication or communication for confirming that the relay base station is the same.
[0027] According to the eleventh aspect of the present invention, confirmation that another user is within a predetermined distance range can be performed by short-distance wireless communication, or by communication for confirming that the relay base station is the same.
[0028] In addition, a twelfth invention is a program of any of the first to eleventh inventions, in which the second type related user registration means determines whether the second condition is satisfied by including in the second condition that a specified multiplayer game has been played in which the user and the other users participate.
[0029] According to the twelfth invention, for example, in addition to confirming that other users are within a predetermined distance range, a second type related user can be registered on the condition that they have played a multiplayer game together.
[0030] In addition, a 13th invention is a program of any of the first to 12th inventions, in which the second type related user registration means allows registration of a new second type related user when a given limit on the number of registered users has not been reached.
[0031] According to the thirteenth aspect of the present invention, a second type related user can be newly registered on condition that a given limit on the number of registered users has not been reached.
[0032] Further, a 14th invention is a program of the 13th invention, in which the limited number of users is a number related to the total number of registered first type related users and second type related users, and the second type related user registration means allows registration of a new second type related user to the user terminal when the total number of registered first type related users and second type related users registered in association with the own user has reached the limited number of users, and when the total number of registered first type related users and second type related users registered in association with the other user has not reached the limited number of users.
[0033] According to the fourteenth aspect of the present invention, it is possible to allow a second type related user to be registered if the total number of registered first type related users and second type related users registered by other users has not reached the limit. In other words, even if the total number of registered first type related users and second type related users registered by a user has reached the limit, the user can be registered as a second type related user depending on other users.
[0034] In addition, a 15th invention is a program of any of the first to 12th inventions, in which the first type related user registration means does not allow the registration of a new first type related user if the total number of registered first type related users and the second type related users has reached a given limit, and the second type related user registration means allows the registration of a new second type related user regardless of whether the total number of registered first type related users and the second type related users has reached the limit.
[0035] According to the fifteenth invention, in a situation where the total number of first type related users and second type related users registered by the user reaches the limit, new registration of first type related users is not allowed. On the other hand, even in the same situation, it is possible to allow registration of second type related users. In other words, it is possible to register second type related users even if the limit is exceeded.
[0036] Further, a 16th invention is a program of any of the first to fifteenth inventions, wherein the confirmation process execution control means executes the confirmation process, including communicating with the other user's terminal to exchange exchange information selected by the own user, and the second type related user registration means registers the second type related users in multiple stages based on the exchange information selected by the own user.
[0037] According to the sixteenth invention, when registering other users as second type related users, exchange information can be exchanged with each other, making it possible to rank the second type related users according to the content of the exchange information.
[0038] Further, a 17th invention is a program of any of the 1st to 15th inventions, wherein there are multiple types of the specified communication, the confirmation process execution control means is capable of executing the confirmation process by attempting different types of the specified communication, and the second type related user registration means registers the second type related users in multiple stages based on the type of the specified communication attempted when confirmed by the confirmation process.
[0039] According to the seventeenth aspect of the present invention, a confirmation process can be executed in which different types of predetermined communication are tried and performed. Then, it becomes possible to rank the second type related users depending on which type of predetermined communication was tried and confirmed when registering another user as a second type related user.
[0040] Further, an eighteenth invention is a server system communicatively connected to a first user terminal of a first user and a second user terminal of a second user, comprising: a first type related user registration means (e.g., a first type related user registration unit 231 in FIG. 15 ) for registering the first user and the second user as first type related users when a first condition under which the first user and the second user can be registered as a first type related user is satisfied; a second type related user registration means (e.g., a second type related user registration unit 233 in FIG. 15 ) for registering the first user and the second user as second type related users when a second condition under which the first user and the second user can be registered as a second type related user is satisfied, the second condition being different from the first condition; and a related act including: 1) a first type related user registration unit (e.g., a first type related user registration unit 234 in FIG. 15 ) for registering the first user and the second user as second type related users when a second condition under which the first user and the second user can be registered as a second type related user is satisfied; a related action control means (e.g., the related game play control unit 241 in FIG. 15) that controls the execution of the related action based on a first type action control when the first type related users are involved, and 2) the related action based on a second type action control when the second type related users are involved, wherein the second type related user registration means has a confirmation process execution control means (e.g., the confirmation process execution control unit 235 shown in FIG. 15) that executes a confirmation process including attempting a specified communication between the first user terminal and the second user terminal as a specified confirmation process defined to confirm that the first user and the second user are within a specified distance range, and the server system (e.g., the server system 1100 in FIG. 1) that includes in the second condition what has been confirmed by the confirmation process and determines whether the second condition is satisfied.
[0041] According to the eighteenth aspect, a server system that provides the same effects as the first aspect can be realized.
[0042] A nineteenth aspect of the present invention is an entertainment system (for example, the game system 1000 in FIG. 1) including the server system of the eighteenth aspect of the present invention, and the first user terminal and the second user terminal.
[0043] According to the nineteenth aspect of the present invention, an entertainment system that provides the same effects as the first aspect of the present invention can be realized. [Brief description of the drawings]
[0044] [Figure 1] FIG. 1 is a diagram showing an example of the overall configuration of a game system. [Diagram 2] FIG. 2 is a diagram showing an example of the device configuration of a user terminal. [Diagram 3] FIG. 13 is a diagram for explaining an outline of a related user registration function. [Figure 4] FIG. 4 is a diagram showing an example of the data structure of related user data; [Diagram 5] 11 is a flowchart showing the flow of a second type related user registration process. [Figure 6] A diagram explaining new registration of face-to-face friends. [Figure 7] FIG. 11 is a diagram illustrating a third confirmation process. [Figure 8] FIG. 4 is a diagram showing an example of the data configuration of face-to-face meeting data. [Figure 9] FIG. 13 is a diagram showing an example of setting related game play control information. [Figure 10] FIG. 13 is a diagram showing an example of a friend screen. [Figure 11] FIG. 13 is a diagram showing an example of a search screen. [Figure 12] FIG. 13 is a diagram showing an example of a face-to-face registration screen. [Figure 13] FIG. 13 is a diagram showing an example of a registration completion screen. [Figure 14] FIG. 13 is a diagram showing an example of a face-to-face meeting end screen. [Figure 15] FIG. 2 is a block diagram showing an example of the functional configuration of the server system. [Figure 16] FIG. 4 is a diagram showing an example of a data configuration of user management data. [Figure 17] FIG. 4 is a block diagram showing an example of the functional configuration of a user terminal. [Figure 18] 6 is a flowchart showing a process flow in the server system. [Figure 19] FIG. 13 is a diagram showing an example of the functional configuration of a user terminal in the first modification example. [Figure 20] FIG. 4 is a diagram showing an example of a data configuration of intimacy data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0045] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. Note that the present invention is not limited to the embodiments described below, and the forms to which the present invention can be applied are not limited to the following embodiments. In addition, in the description of the drawings, the same parts are given the same reference numerals.
[0046] [Overall configuration] Fig. 1 is a diagram showing an example of the overall configuration of a game system 1000 in this embodiment. As shown in Fig. 1, the game system 1000 includes, as an entertainment system, a server system 1100 which is a computer system, and a user terminal 1500 owned by a player (user) 2 of the game of this embodiment, which are connected to each other so as to be able to communicate data with each other via a network N. In this embodiment, the application will be described as a game application.
[0047] The network N refers to a communication path that allows data communication. In other words, the network N includes a dedicated line (dedicated cable) for direct connection, a LAN (Local Area Network) using Ethernet (registered trademark), etc., as well as a telephone communication network, a cable network, the Internet, and other communication networks, and the communication method can be either wired or wireless.
[0048] The server system 1100 includes a main device 1101, a keyboard 1106, a touch panel 1108, and a storage 1140. The main device 1101 includes a built-in control board 1150 on which are mounted various electronic components such as a CPU (Central Processing Unit) 1151, a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), etc., various IC memories 1152 such as a VRAM, a RAM, a ROM, etc., and a communication device 1153. Note that a part or the whole of the control board 1150 may be realized by an ASIC (Application Specific Integrated Circuit), an FPGA (Field-programmable gate array), or a SoC (System on a Chip).
[0049] This server system 1100 realizes a user management function related to user registration and the like, and a game management function that provides data necessary for playing the game on the user terminal 1500 and manages execution control of the game on the user terminal 1500, by the CPU 1151 and the like performing calculations based on predetermined programs and data. In other words, the game in this embodiment is realized as a kind of client-server type online game. User 2 accesses the server system 1100 with his / her own user terminal 1500, logs in with an issued account, and enjoys the game of this embodiment.
[0050] The server system 1100 also cooperates with an external electronic payment server operated by an electronic payment service provider or the like to carry out a purchase procedure (billing process) for game coins, which are in-game currency. During the billing process, the electronic payment server responds to an inquiry from the server system 1100 and performs a process of settling the purchase amount of the game coins with the credit card, prepaid card or the like of the user 2. The server system 1100 then grants the user 2 game coins equivalent to the purchase amount settled by the electronic payment server.
[0051] 1, the server system 1100 may be configured to include multiple blade servers each assigned to one function, and connected to each other via an internal bus for data communication. Alternatively, the server system 1100 may be configured to function as a whole as multiple independent servers installed at separate locations communicating data via a network N.
[0052] The user terminal 1500 is a computer system that functions as a man-machine interface, and can connect to the network N via a mobile phone base station or a wireless communication base station, etc., and perform data communication with the server system 1100. This user terminal 1500 can take the form of, for example, a smartphone, a mobile phone, a portable game device, a stationary home game device, a controller for a stationary home game device, an arcade game device, a personal computer, a tablet computer, a wearable computer, etc.
[0053] Fig. 2 is a diagram showing an example of the device configuration of a smartphone, which is an example of the user terminal 1500. As shown in Fig. 2, the user terminal 1500 includes a directional input key 1502, a home key 1504, a touch panel 1506 that functions as an image display device and a contact position input device, a built-in battery 1509, a speaker 1510, a microphone 1512, a camera 1520, a control board 1550, and a memory card reader 1542 that can read and write data to a memory card 1540 that is a computer-readable storage medium. In addition, a power button, a volume control button, etc., which are not shown, are provided.
[0054] The control board 1550 is equipped with various microprocessors such as a CPU 1551, a GPU, and a DSP, various IC memories 1552 such as a VRAM, a RAM, and a ROM, a wireless communication module 1553 for wireless communication with a mobile phone base station or a wireless communication base station connected to the network N, a positioning module 1555, an interface circuit 1557, and the like. The interface circuit 1557 includes a circuit for receiving signals from the direction input key 1502 and the home key 1504, a driver circuit for the touch panel 1506, an output amplifier circuit for outputting an audio signal to the speaker 1510, an audio signal generating circuit for generating an audio signal collected by the microphone 1512, a circuit for inputting image data of an image captured by the camera 1520, and a signal input / output circuit for the memory card reader 1542. Each of these elements mounted on the control board 1550 is electrically connected to each other via a bus circuit or the like, and is connected so as to be able to read and write data and transmit and receive signals. Note that a part or all of the control board 1550 may be configured with an ASIC, an FPGA, or an SoC.
[0055] In this control board 1550, a game client program and various setting data required to execute this game client program are stored in IC memory 1552. The game client program and the like are downloaded from server system 1100 at an appropriate timing. The game client program and the like may be read from a separately obtained storage medium such as memory card 1540. Then, CPU 1551 and the like execute the game client program to perform calculation processing, and control each part of user terminal 1500 in response to operational inputs to touch panel 1506, directional input keys 1502, and home key 1504, thereby enabling user 2 to play the game.
[0056] The positioning module 1555 is a means for acquiring information (user position) of the current position of the user 2 (to be precise, the user terminal 1500). In this embodiment, a known positioning system is used to acquire position coordinates and orientation in real space. That is, the positioning module 1555 provides a positioning function in the user terminal 1500 by receiving a signal provided from the positioning system and outputting positioning information including the user position at a predetermined period (for example, every second). As the positioning system, for example, a Global Navigation Satellite System (GNSS), which is a satellite positioning system represented by a Global Positioning System (GPS), can be used. In this case, the positioning module 1555 can be realized by a known GPS module, a GPS receiver, or the like. Galileo or a Beidou system (BDS) other than GPS may be used. In addition, a system that performs positioning by triangulation based on communication with multiple communication base stations and mobile stations, or an RTK positioning system using both GNSS and base station communication may be used. The "positioning information" includes the positioning date and time (UTC: Coordinated Universal Time), position coordinates (latitude, longitude, altitude), direction, etc. The position coordinates obtained by the positioning module 1555 (i.e., the position of the user terminal 1500) are called the "user position."
[0057] In this embodiment, the positioning information measured by the positioning module 1555 is associated with the account (user ID) of the user 2 of the own device and transmitted periodically or intermittently to the server system 1100. The server system 1100 manages the reception history of the positioning information from the user terminal 1500 for each user, thereby making it possible to track the current user position of each user 2 participating in the game.
[0058] The positioning module 1555 can be replaced with a configuration of a communication device that wirelessly communicates with a mobile phone base station of a mobile phone or a wireless communication base station of a Wi-Fi network, and a direction sensor. That is, it can be replaced with acquisition of so-called simplified position information, in which pre-measured position information of a connected wireless base station is acquired and this is used as the position coordinates of the device in real space. Then, the direction in real space to which the device is facing may be acquired by the direction sensor.
[0059] In this embodiment, an idol simulation game in which an idol is produced and trained is exemplified. A user selects a favorite idol character, and while securing the necessary stamina, the user enjoys training the idol character by having the idol character work as an idol, taking lessons and auditions, etc. In the process, the user also progresses through the game while clearing various events such as events in which the user plays against other users in mini-games or cooperates with them, and events in which the user gathers at a specific location (event venue) in real space. The contents of the mini-games played with other users are not particularly limited. For example, the user may play a music game using the idol character that the user has trained and compete for scores, or may play a music game with each idol character forming a unit and aiming for a high score.
[0060] The game of this embodiment has a related user registration function (also called a friend function) that allows a user to register other users as related users (so-called friends) with whom the user has a relationship. Specifically, a "friend" can be registered as a first-class related user, and a "face-to-face friend" can be registered as a second-class related user. When a friend or face-to-face friend is registered using this related user registration function, the users can give each other stamina and other items required to play the game.
[0061] FIG. 3 is a diagram for explaining an overview of the related user registration function, showing the registration status of friends and face-to-face friends of a certain user 2a. As described above, the related user registration function of this embodiment allows users to register friends and face-to-face friends, but the upper limit of the number of people that can be registered (the maximum number of registration slots), which is a given limit, is set for each user and updated as needed. For example, the upper limit of the number of people is raised when the user level of the user reaches a predetermined level. The upper limit of the number of people may be increased not only based on the user level, but also based on the play time, game progress, etc., and an additional registration slot may be granted as an event reward.
[0062] More specifically, the upper limit number is set as the upper limit number of the total number of registered friends and meeting friends, and is updated. In FIG. 3, the upper limit number of the user 2a is 7 people, so the total number of registered friends (4 people) and meeting friends (1 person) does not reach the upper limit number (7 people), and two registration slots remain. Therefore, two more users can be registered as friends or meeting friends. The registration slots for friends and the registration slots for meeting friends may be set separately. For example, the upper limit number (restricted number of people) for friends is 4 people, and the upper limit number (restricted number of people) for meeting friends is 3 people, making a total of seven people the upper limit number. In that case, in the example of FIG. 3, the registration slots for friends are filled, so another user cannot be registered as a friend, but two more meeting friends can be registered.
[0063] FIG. 4 is a diagram showing an example of the data configuration of related user data 520 set for user 2a shown in FIG. 3. In order to realize the related user registration function, server system 1100 manages related user data 520 shown in FIG. 4 for each user participating in the game (see FIG. 16). Specifically, related user data 520 stores upper limit number of users 521, friend list 523, and face-to-face friend list 525 as shown in FIG. 4. A total of upper limit number of users 521 (7 in this case) can be registered in friend list 523 and face-to-face friend list 525. Server system 1100 updates upper limit number of users 521 from time to time according to user level 515 (see FIG. 16) of the corresponding user (user 2a in this case). Then, when registering a friend for user 2a, friend list 523 is updated, and when registering a face-to-face friend, friend list 523 is updated. At that time, it is determined whether there is a registration frame remaining based on upper limit number of users 521 and the number of registered users in each list 523, 525.
[0064] [detail] In this embodiment, in order to realize the above-mentioned related user registration function, the server system 1100 performs a first type related user registration process, a second type related user registration process, a deregistration process, a bonus granting control process, and a related game play control process.
[0065] 1. Type 1 related user registration process In the first type related user registration process, the server system 1100 registers as a friend a user who satisfies a first condition that allows the user to be registered as a friend (first type related user).
[0066] The first condition is, for example, "a friend registration procedure has been completed between a first user and a second user." In this embodiment, when a user (first user) makes a registration request (friend request) to another user (second user) whom the user wants to make a friend, and the second user approves the request, the friend registration procedure is completed. Therefore, the server system 1100 determines the first condition by monitoring a friend request operation on any one of the user terminals 1500 and an approval operation on the other user terminals 1500 in response to the friend request operation.
[0067] In addition, the server system 1100 determines a given limit number condition in addition to the first condition in order to limit the total number of registered friends and meet friends. In this embodiment, an upper limit number of the total number of registered users is set for each user. Therefore, in this embodiment, the limit number condition is "there is a vacancy in the registration frame for the first user, and there is a vacancy in the registration frame for the second user." When the limit number condition is satisfied, the server system 1100 allows each target user (the first user and the second user) to register a new friend.
[0068] Then, when the friend registration procedure between the users is completed (the first condition is satisfied) and there is remaining registration space for both users (the limited number of users condition is satisfied), the server system 1100 adds each other to each user's friend list 523 and updates the related user data 520.
[0069] In addition, if the face-to-face data 530 described below has already been generated for a pair of users (a first user and a second user) who have completed the friend registration procedure, the server system 1100 does not register the friends, but instead makes them eligible for re-registration of a face-to-face friend described below.
[0070] 2. Type 2 related user registration process In the second type related user registration process, the server system 1100 performs new registration of a face-to-face friend for a pair of users who have recently performed a face-to-face procedure, and performs re-registration of a face-to-face friend for a pair of users who have previously performed a face-to-face procedure. Fig. 5 is a flowchart showing the flow of the second type related user registration process.
[0071] 2-1. About new registration In the second type related user registration process, the server system 1100 registers as a face-to-face friend a user who satisfies a second condition that is different from the first condition and that is a condition for being able to be registered as a face-to-face friend (second type related user). To this end, the server system 1100 first determines the second condition when newly registering a face-to-face friend (steps S101 to S109), as shown in Fig. 5. Fig. 6 is a diagram for explaining the new registration of a face-to-face friend.
[0072] First, in order to register a face-to-face friend, the users who want to register must meet each other face to face. The face-to-face procedure is the procedure for this purpose.
[0073] The second condition is, for example, "the face-to-face procedure between the first user and the second user is completed." More specifically, the server system 1100 executes a predetermined confirmation process while the target users, the first user A and the second user B illustrated in FIG. 6, etc., proceed with the face-to-face procedure, and the face-to-face procedure ends when confirmation is made by the confirmation process. The second condition is satisfied upon the completion of the process.
[0074] Here, the confirmation process is defined to confirm that a first user A and a second user B are within a specified distance range, and includes attempting a specified communication between the user terminal (first user terminal) 1500a of the first user A and the user terminal (second user terminal) 1500b of the second user B.
[0075] In this embodiment, the server system 1100 uses a two-dimensional code C1 such as a QR code (registered trademark) as a given registration identifier, and executes a first confirmation process in which one of the first user terminal 1500a and the second user terminal 1500b (the second user terminal 1500b in FIG. 6) receives information of the two-dimensional code C1 from the other (the first user terminal 1500a in FIG. 6), thereby causing the one user terminal 1500 to attempt a predetermined communication. In addition, the server system 1100 executes a second confirmation process in which it is determined that the distance D1 between the user position of the first user A and the user position of the second user B is within a predetermined distance range, thereby confirming that the two users have actually met face to face. In addition, in this embodiment, a third confirmation process is executed to control information exchange between the first user A and the second user B. FIG. 7 is a diagram for explaining the third confirmation process.
[0076] Specifically, as shown in Fig. 5, the server system 1100 first executes a first confirmation process (step S101). That is, first, one of the first user terminal 1500a or the second user terminal 1500b displays the two-dimensional code C1, and the other activates the camera 1520 to read it, thereby controlling the execution of communication to receive information on the two-dimensional code C1. Then, when the server system 1100 detects that the reception has been successful, it determines that confirmation by the first confirmation process has been made (step S103: YES).
[0077] Next, the server system 1100 executes the second confirmation process (step S105). That is, first, the user position of the first user A is acquired, and the user position of the second user B is acquired. The user positions may be acquired by performing communication to acquire positioning information from each user terminal 1500a, 1500b at the time of execution of the second confirmation process, or by reading the latest user positions from the reception history of positioning information separately and periodically received from each user A, B. Then, the server system 1100 determines whether the distance D1 between the acquired user positions is within a predetermined distance range, and if the result is affirmative, it is determined that the second confirmation process has been confirmed (step S107: YES). The distance range may be, for example, within 1 m or within 5 m, and can be set appropriately.
[0078] Next, the server system 1100 executes a third confirmation process (step S109). In this embodiment, items that can be exchanged in the information exchange by the third confirmation process (exchangeable items) are determined in advance, and the designation of the items to be exchanged (exchange items) is accepted for each user. The exchangeable items may be determined appropriately according to the content of the game, etc. For example, the user's level, game play history, follower list, gender, age, birthday, etc. are included. Then, the server system 1100 controls the exchange by setting the content of the exchange item designated by the first user A ("level" in the example of FIG. 7) as the first user A's exchange information M21, and the content of the exchange item designated by the second user B ("level", "play history", and "gender" in the example of FIG. 7) as the second user B's exchange information M23. For example, this can be realized by controlling each user terminal 1500a, 1500b to display the other party's exchange information so that it can be viewed. In this embodiment, when a face-to-face friend is selected on the friend screen (see FIG. 10) described later, a profile screen including the disclosure of the exchange information received from the corresponding user is displayed.
[0079] In addition, when executing the third confirmation process, the server system 1100 sets a meeting rank between the user and the other party according to the type of exchange items designated by each of the users A and B (i.e., the number and type of exchange items disclosed to the other party). For example, the meeting rank is set higher as the number of exchange items with higher scores increases. In this case, it can be realized by determining a score for each exchangeable item in advance and ranking the total score of the exchange items. This makes it possible to register meeting friends by distinguishing them into multiple stages based on the exchange information. The example in FIG. 7 shows an example in which the meeting rank is set in three stages from "1" to "3", and the meeting rank between the user B, who has a large number of exchange items, is set higher than the user A, who has a small number of exchange items.
[0080] The face-to-face ranking may have two stages or four or more stages. The exchange items may be the same for each user A and B, not limited to a configuration in which the exchange items are designated individually by each user A and B. Items designated by both users ("user level" in the example of FIG. 7) may be extracted and used as the exchange items, or a configuration in which a designation by one of the first user and the second user is accepted may be used.
[0081] Also, instead of being limited to a configuration in which the user specifies the items to be exchanged with the other person each time a meeting procedure is performed, each user may prepare a plurality of types of business cards with different contents in advance and specify which business cards to exchange when the meeting procedure is performed. For example, various types of business cards may be prepared, such as for acquaintances, friends, best friends, etc. In this case, the meeting rank can be set according to which type of business card was exchanged.
[0082] If the server system 1100 has executed the third confirmation process, it is determined that the second condition is satisfied. At this point, the face-to-face meeting procedure is completed.
[0083] If the second condition is satisfied, the server system 1100 then determines whether or not the face-to-face data 530 for the pair of users A and B has already been generated. The face-to-face data 530 is generated in step S115 when the pair of users is newly registered. Therefore, if the face-to-face data 530 has already been generated (step S113: YES), the server system 1100 performs the processes of steps S121 to S123 since this is not a new registration, and re-registers the face-to-face friend. If there is no face-to-face data 530 for the pair of users (step S113: NO), the server system 1100 performs the processes of steps S115 to S119 to newly register the face-to-face friend.
[0084] If a new registration is to be made, the server system 1100 first generates face-to-face data 530 for the pair of users (step S115). Through this process, face-to-face data 530 is generated for the pair of users who have newly performed (completed) the face-to-face procedure. More specifically, even if the latter limit number condition is not met, the face-to-face data 530 is generated. It would be a waste to invalidate the entire procedure because there is no space in the registration frame after the face-to-face procedure has been performed between users who have met face-to-face, so the face-to-face data 530 is generated. On the other hand, this face-to-face data 530 is designed not to be deleted even if the registration of the face-to-face friend is deleted through the registration deletion process.
[0085] Fig. 8 is a diagram showing an example of the data configuration of the face-to-face meeting data 530. As shown in Fig. 8, one face-to-face meeting data 530 stores first user data 531 related to a first user who is one of the target users, second user data 533 related to a second user who is the other of the users, face-to-face meeting date and time 535, and face-to-face meeting place 537.
[0086] The first user data 531 includes a user ID 5311 of the corresponding user, a type of exchange item 5313 designated by the user for information exchange in the third confirmation process, and a face-to-face rank 5315 for the other party (second user). Similarly, the second user data 533 includes a user ID 5331 of the corresponding user, a type of exchange item 5333 designated by the user for information exchange in the third confirmation process, and a face-to-face rank 5335 for the other party (first user).
[0087] The date and time of the meeting is set in the meeting date and time 535 .
[0088] A location based on the user positions of the first user and / or the second user at the time of the meeting procedure (e.g., a place name, a building or facility name, etc.) is set in the meeting location 537. Since the user positions of the first user and the second user are within a predetermined distance range, a location based on either one of the user positions may be set, or a location including both may be set.
[0089] Returning to FIG. 5, the server system 1100 then determines the limit number condition in the same manner as the first type related user registration process in order to limit the total number of registered friends and face-to-face friends. If the limit number condition is met (step S117: YES), each user is permitted to register a new face-to-face friend. In this case, the server system 1100 adds each user to the face-to-face friend list 525 of each user and updates the related user data 520 (new registration; step S119). With the execution of step S119 here, the registration of face-to-face friends is completed. Therefore, if the limit number condition is not met (step S117: NO), the registration of face-to-face friends is not completed. In other words, The person will not be registered as a meet-up friend (new registration). However, since the meet-up procedure has been completed and the meet-up data 530 has been generated, the benefits described below will be given.
[0090] On the other hand, if re-registration is to be performed, the server system 1100 judges the limit number of users condition in the same manner as in step S117. Then, if the limit number of users condition is met (step S121: YES), each user is added to the face-to-face friend list 525 of the other user, and the related user data 520 is updated (step S123). At this time, it is preferable to update the face-to-face data 530 as appropriate. That is, when an exchange item different from that at the time of past registration is specified during execution of the third process in step S109, and information is exchanged, the item is added to the exchange item types 5313, 5333 to update them, and the face-to-face ranks 5315, 5335 may be updated based on the number and type of the updated exchange item types 5313, 5333.
[0091] 2-2. Re-registration In this embodiment, the server system 1100 re-registers each user as a meeting friend if (1) the meeting data 530 has already been generated for a pair of users who have completed the meeting procedure. This corresponds to the processing from YES in step S113 to step S123 in Fig. 5. The reason why the case of (1) is distinguished as a re-registration from a new registration is to limit the granting of the meeting benefit in the benefit granting control processing at a later stage to the time of new registration.
[0092] As described above in the description of the first type related user registration process, (2) when the face-to-face data 530 has already been generated for a pair of users who have completed the friend registration procedure, they are also eligible for re-registration. This is because the pair of users has previously completed the face-to-face procedure and meets the second condition required for registering a face-to-face friend (the two have already met face-to-face). Examples of cases where re-registration occurs due to (1) or (2) include cases where users met in the past and completed the face-to-face procedure itself, but were not registered as face-to-face friends because they did not meet the limited number of people condition, and then both users vacated the registration slot and performed the friend registration procedure. There are also cases where users were previously registered as face-to-face friends, but the registration was deleted by a registration deletion process, and then each user performed the friend registration procedure or face-to-face procedure.
[0093] 3. Cancellation of registration In the registration deletion process, the server system 1100 deletes the registration of a friend or a meet-up friend for each user. In this embodiment, the user can specify a friend or a meet-up friend from a friend menu, which will be described later, to perform a relationship deletion operation. When the server system 1100 detects the relationship deletion operation on the user terminal 1500, if the specified user is a friend, the server system 1100 deletes the specified user from the friend list 523 of the user who performed the operation and updates the related user data 520. In the case of a meet-up friend, the server system 1100 deletes the user from the meet-up friend list 525 and updates the related user data 520. This registration deletion process allows the friend relationship or meet-up friend relationship between registered users to be deleted.
[0094] 4.Benefit Granting Control Processing In the privilege granting control process, when new face-to-face data 530 is generated in the second type related user registration process, the server system 1100 performs control to grant a given privilege (face-to-face privilege) to each target user (first user and second user). In this embodiment, the contents of the privilege to be granted for each face-to-face rank of "1" to "3" are determined in advance (see face-to-face privilege data 551 in FIG. 15). The higher the rank, the more luxurious the contents are, and the more advantageous the setting is for the user. Then, a face-to-face privilege according to the face-to-face rank 5315, 5335 (see FIG. 8) is granted to each user.
[0095] That is, in this embodiment, if a pair of users who have completed the meet-and-greet procedure is a new combination, the meet-and-greet bonus will be given even if they are not registered as meet-and-greet friends because there are no vacancies in the registration frame. This allows a user to obtain many meet-and-greet bonuses by meeting other users and completing the meet-and-greet procedure many times. On the other hand, no meet-and-greet bonus is given when users who have previously completed the meet-and-greet procedure re-register. This can prevent the same users from repeatedly performing the meet-and-greet procedure and receiving the meet-and-greet bonus many times.
[0096] The meeting bonus may include various game objects such as characters and items, stamina, game coins, game points that can be accumulated during game play, etc. In addition, bonuses such as increasing the stamina recovery speed for a certain period of time, strengthening the character, boosting the score, etc. may also be included.
[0097] Although the face-to-face privilege is granted to both the first user and the second user in the above embodiment, the face-to-face privilege may be granted only to the first user, or only to the second user. The face-to-face privilege may include a privilege granted each time a new face-to-face procedure is completed, and a privilege granted when the number of people who have completed the face-to-face procedure reaches a predetermined number. In this case, the content of the privilege to be granted may be determined for each number of people to whom the privilege is to be granted.
[0098] 5. Related game play control processing In this embodiment, as an example of a related action that is an action involving related users, a game play involving related users (related game play) is exemplified. In the related game play control process, when friends are involved in the related game play, control is performed to execute the related game play based on a first type game control corresponding to a first type action control, and when face-to-face friends are involved, control is performed to execute the related game play based on a second type game control corresponding to a second type action control.
[0099] In this embodiment, "exchanging gifts between friends or meeting friends" is exemplified as the related game play. When exchanging gifts between friends, the execution of the related game play is controlled using friend-oriented game control information defined for friends. When exchanging gifts between meeting friends, the execution of the related game play is controlled using friend-oriented game control information defined for meeting friends.
[0100] FIG. 9 is a diagram showing a setting example of game control information (related game play control information) 560 for related game play. As shown in FIG. 9, the related game play control information 560 stores game control information 561 for friends and game control information 563 for meeting friends. In each of the game control information 561 and 563 for friends and meeting friends, the contents of a present (present contents) to be given to each other in the corresponding related game play are set. The present contents can include, for example, various game objects, stamina, game coins, game points, tickets for item lottery, and the like, similar to the meeting privilege. Specifically, the contents of the present are set to be more luxurious in the game control information 563 for friends to meet than in the game control information 561 for friends.
[0101] More specifically, as shown in Fig. 9, multiple types of game control information 561, 563 are prepared, and one of them is selected and used when playing a related game. In the example of Fig. 9, in playing a related game with a friend, players exchange a predetermined number of stamina, and in playing a related game with a meeting friend, players exchange a predetermined number of game coins and a rare item randomly selected from a group of rare items prepared as presents.
[0102] 6. Display screen The friend registration procedure, the face-to-face procedure, related game play with friends or face-to-face friends who have been registered through each procedure, and the operation to dissolve relationships with friends or face-to-face friends are performed, for example, by selecting a friend menu on a game menu screen, etc. Fig. 10 is a diagram showing an example of a friend screen that is displayed when the friend menu is selected. This friend screen is displayed by selecting the friend tab T31 at the bottom, an unapproved screen is displayed when the unapproved tab T33 is selected, and a search screen is displayed when the search tab T35 is selected, allowing the screens to be switched.
[0103] 10, the friend screen displays a list of users (friends) who the user (own user) of the user terminal 1500 has registered as friends and users (face-to-face friends) who have registered as face-to-face friends, for example, in the order of their registration. In the list display, a mark MK3 indicating that the user is a face-to-face friend is added to the icon of the face-to-face friend, and the user is displayed so as to be identifiable from the friend user. In addition, the location set as face-to-face location 537 in face-to-face data 530 (the location where the face-to-face procedure with the relevant user was performed) is added to the face-to-face friend, which serves as a clue for remembering the relevant user.
[0104] In addition, friends and meeting friends may be displayed separately in a list. In this case, the display order of the meeting friends may be sorted based on the meeting place 537. For example, users with the same meeting place 537 may be arranged together, or the meeting places 537 may be sorted in order of proximity to the user's current location.
[0105] When a friend or a face-to-face friend is selected on this friend screen, the profile screen (not shown) of that user can be displayed. The profile screen displays the user's name, the type of idol character being trained, a self-introduction previously entered by the user, and, if the user is a face-to-face friend, the exchange information of the user received during the information exchange during the face-to-face procedure. In addition, a relationship termination button for the friend or face-to-face friend is provided on the profile screen of the friend or face-to-face friend. By selecting this relationship termination button, the user can perform a relationship termination operation for the designated friend or face-to-face friend.
[0106] Furthermore, on the friend screen, a present button B3 is arranged within each of the friend and meeting friend frames. By selecting this present button B3, the user performs a related game play operation specifying the friend or meeting friend. This allows a related game play in which presents are given to each other with the corresponding user. If the user is a friend, a related game play in which presents are given to each other with content set as friend-oriented game control information 561 can be performed, and if the user is a meeting friend, a related game play in which presents are given to each other with content set as meeting-oriented game control information 563 can be performed.
[0107] In the unapproved screen (not shown) of the unapproved tab T33, other users who have sent friend requests to the user and have not yet been approved or rejected by the user are displayed as a list of unapproved users. The user can approve or reject the friend requests of each unapproved user. When the user approves the request, the friend registration procedure is completed between the user and the relevant other user.
[0108] On the search screen of the search tab T35, the user can search for other users who the user wants to make friends with and proceed with the friend registration procedure, or proceed with the face-to-face meeting procedure with other users who the user actually meets. FIG. 11 is a diagram showing an example of the search screen.
[0109] 11, the search screen has a meet-and-greet registration button B41 for starting the meet-and-greet procedure. Also provided are an ID search button B43 for entering a user ID to search for other users, a follower search button B45 for searching for followers, and an invite button B47 for inviting the user to a game, allowing the user to start the friend registration procedure for the searched or invited other user and make a friend request.
[0110] On the other hand, when the face-to-face registration button B41 is selected, the face-to-face registration screen shown in FIG. 12 is displayed. The face-to-face registration screen has a display area A5 for a two-dimensional code C5 in the center, and the display area A5 can be switched to a reading area by selecting the camera start button B5. In the face-to-face registration procedure, first, a first user displays the two-dimensional code C5 on his / her user terminal (first user terminal) 1500. The second user selects the camera start button B5 on his / her user terminal (second user terminal) 1500. Then, the information of the two-dimensional code C5 is received from the first user terminal 1500 by reading the two-dimensional code C5 in the reading area.
[0111] Then, when confirmation is made through a confirmation process during the face-to-face procedure, the procedure ends, and if there is space in the registration slots for each user (if the limit on the number of people condition is met), a registration completion screen as shown in FIG. 13 is displayed, and the registration of the face-to-face friend is completed. On this registration completion screen, if the registration is due to the completion of a new face-to-face procedure (new registration), the contents of the face-to-face privilege are also notified. On the other hand, if there is no space in the registration slot, a face-to-face completion screen is displayed as shown in FIG. 14, notifying that the face-to-face procedure has ended and the "face-to-face meeting" has been completed. On this face-to-face completion screen, if the registration is due to the completion of a new face-to-face procedure, the contents of the face-to-face privilege are also notified.
[0112] [Function configuration] 1. Server system Fig. 15 is a block diagram showing an example of a functional configuration of a server system 1100. As shown in Fig. 15, the server system 1100 of this embodiment includes an operation input unit 100s, a server processing unit 200s, an image display unit 390s, a sound output unit 392s, a communication unit 394s, and a server storage unit 500s.
[0113] The operation input unit 100s is for inputting various operations for system management, maintenance, etc., and can be realized by, for example, a keyboard, a mouse, a touch panel, etc. In FIG.
[0114] The server processing unit 200s can be realized by a processor, which is an arithmetic circuit such as a CPU, GPU, ASIC, or FPGA, or an electronic component such as an IC memory, and controls input and output of data between each unit of the device including the operation input unit 100s and the server storage unit 500s. Then, various types of arithmetic processing are performed based on predetermined programs and data, operation input signals from the operation input unit 100s, data received from the user terminal 1500, etc., and the operation of the server system 1100 is centrally controlled. In FIG. 1, the control board 1150 and its CPU 1151 correspond to this.
[0115] The server processing unit 200s includes a user management unit 210, a billing processing unit 220, a game management unit 230, a timing unit 280s, an image generation unit 290s, a sound generation unit 292s, and a communication control unit 294s.
[0116] The user management unit 210 performs processes related to user registration and manages data of each registered user (player) linked to an account. For example, it can execute processes such as granting a unique account to a registered user, registration information management processes for registering and managing personal information for each account, and usage history management processes for managing login and logout history. Of course, it can also appropriately include management processes for other data linked to accounts.
[0117] The billing processing unit 220 performs billing processing in response to a user's operation to purchase game coins, and grants the user game coins equivalent to the purchase amount.
[0118] The game management unit 230 performs various processes related to game execution management. Since the multiplayer game of this embodiment is a client-server type online game, the game management unit 230 performs control to provide data necessary for game play while communicating with the user terminal 1500. This game management unit 230 includes a first type related user registration unit 231, a second type related user registration unit 233, a registration deletion unit 237, a benefit granting control unit 239, and a related game play control unit 241.
[0119] The first type related user registration unit 231 is a functional unit that performs a first type related user registration process, and determines whether a first condition is met and registers a friend.
[0120] The second type related user registration unit 233 is a functional unit that performs a second type related user registration process, and registers face-to-face friends by determining whether a second condition is met. The second type related user registration unit 233 has a confirmation process execution control unit 235 that executes a confirmation process to confirm that target users are within a predetermined distance range.
[0121] The registration deletion unit 237 is a functional unit that performs registration deletion processing, and deletes the registration of friends or meeting friends when a relationship dissolution operation in the user terminal 1500 is detected.
[0122] The privilege granting control unit 239 is a functional unit that performs privilege granting control processing, and performs control to grant a privilege to each user of a group for which face-to-face meeting data 530 has been generated as a result of completing a new face-to-face meeting procedure.
[0123] The related game play control unit 241 is a functional unit that performs related game play control processing. In this embodiment, the related game play control unit 241 performs control to execute related game play based on the first type game control by using friend-oriented game control information 561 between friends, and performs control to execute related game play based on the second type game control by using face-to-face friend-oriented game control information 563 between face-to-face friends.
[0124] The timekeeping unit 280s uses a system clock to keep track of the current date and time, time limit, and the like.
[0125] The image generating unit 290s generates images relating to system management of the server system 1100 and outputs them to the image display unit 390s.
[0126] The sound generation unit 292s is realized by executing an IC or software that generates or decodes audio data, and generates or decodes audio data such as operation sounds and BGM related to the system management and video distribution of the server system 1100. Audio signals related to system management are output to the sound output unit 392s.
[0127] The communication control unit 294s performs communication connection and data processing for data communication with an external device (eg, the user terminal 1500) via the communication unit 394s, and realizes data exchange with the external device.
[0128] The image display unit 390s displays various screens for system management and the like based on the image signal input from the image generation unit 290s. For example, this can be realized by an image display device such as a flat panel display, a projector, or a head mounted display. In FIG. 1, this corresponds to the touch panel 1108.
[0129] The sound output unit 392s emits the sound signal input from the sound generation unit 292s. In FIG. 1, this corresponds to a speaker (not shown) provided in the main device 1101 or the touch panel 1108.
[0130] The communication unit 394s realizes communication by connecting to the network N. For example, it can be realized by a wireless communication device, a modem, a TA (terminal adapter), a jack of a wired communication cable, a control circuit, etc. In FIG. 1, the communication device 1153 corresponds to this.
[0131] In the server storage unit 500s, programs for operating the server system 1100 and realizing various functions of the server system 1100, data used during execution of the programs, etc. are stored in advance or temporarily stored each time processing is performed. For example, it can be realized by IC memory such as RAM or ROM, a magnetic disk such as a hard disk, an optical disk such as a CD-ROM or DVD, etc. In FIG. 1, this corresponds to the IC memory 1152 and the storage 1140.
[0132] The server storage unit 500s also stores a server program 501, a distribution game client program 503, user management data 510, face-to-face data 530 described with reference to Fig. 8, game setting data 550, and play data 570. In addition, necessary data such as timers, counters, various tables, thresholds, flags, etc. are also appropriately stored.
[0133] The server program 501 is a program for causing the server processing unit 200s to function as the user management unit 210 and the game management unit 230. Note that this may also include programs for causing the server processing unit 200s to function as the image generation unit 290s, the sound generation unit 292s, and the communication control unit 294s, as appropriate.
[0134] The distribution game client program 503 is the original of the game client program 502 (see FIG. 17) that is downloaded to the user terminal 1500.
[0135] User management data 510 is prepared for each user who has completed user registration, and stores various data for management related to the game play of the user. Specifically, one user management data 510 includes the user ID 511 of the corresponding user, the user name 513 of the user, the user level 515, the payment medium ledger data 517, and the related user data 520 described with reference to Fig. 4, as shown in Fig. 16. In addition, the data includes play history such as play date and time, play time, personal information such as age, sex, birthday, save data related to play status, etc.
[0136] The payment medium ledger data 517 stores information on the income and expenditure of the electronic payment medium (game coins, which are the in-game currency in this embodiment) linked to the corresponding user, such as the purchase date and time and number of game coins purchased (charged amount), and the history of the consumption date and number of game coins consumed.
[0137] The game setting data 550 stores various setting data necessary for executing the game. For example, it stores character setting data that defines various ability parameter values, model data, motion data used for movement control of characters appearing in the game, object definition data related to game objects that the user can obtain during the game, etc. In addition, the game setting data 550 stores meeting privilege data 551 that defines the contents of meeting privileges for each meeting rank, and related game play control information 560 described with reference to FIG. 9.
[0138] Play data 570 is prepared for each user playing the game (i.e., for each user terminal 1500 connected to the server system 1100) and stores various data describing the progress of the user's game in addition to the positioning history 571.
[0139] 2. User Device Fig. 17 is a block diagram showing an example of a functional configuration of a user terminal 1500. As shown in Fig. 17, the user terminal 1500 includes an operation input unit 100, a device processing unit 200, an image display unit 390, a sound output unit 392, a communication unit 394, and a device storage unit 500.
[0140] The operation input unit 100 is for the user to input various operations, and can be realized by, for example, a button switch, a joystick, a touch pad, a track ball, an acceleration sensor, an angular velocity sensor, a CCD module, etc. In Fig. 2, this corresponds to the direction input key 1502, the home key 1504, and the touch panel 1506.
[0141] The device processing unit 200 can be realized by a processor, which is an arithmetic circuit such as a CPU, GPU, ASIC, or FPGA, or an electronic component such as an IC memory, and controls input and output of data between each unit of the device including the operation input unit 100 and the device storage unit 500. Then, it performs various arithmetic processing based on a predetermined program or data, an operation input signal from the operation input unit 100, data received from the server system 1100, and the like, and generally controls the operation of the user terminal 1500. In FIG. 2, the control board 1550 and its CPU 1551 correspond to this. And, the device processing unit 200 in this embodiment includes a user terminal arithmetic unit 270, a timer unit 280, an image generation unit 290, a sound generation unit 292, and a communication control unit 294.
[0142] The user terminal calculation unit 270 executes various calculation processes for causing the user terminal 1500 to function as a terminal for playing a game by the user. For example, the user terminal calculation unit 270 includes an operation signal transmission control unit 271 and a game screen display control unit 273.
[0143] The operation signal transmission control unit 271 performs processing for transmitting various data and request information to the server system 1100 in response to an operation input to the operation input unit 100 .
[0144] The game screen display control unit 273 performs control for displaying a game screen based on various data received from the server system 1100. For example, if the online game of this embodiment is realized as a web game, it can be realized using a web technology that actively controls screen display using HTML together with Java (registered trademark) and CSS (Cascading Style Sheets) based on a web browser, or a plug-in such as Adobe (registered trademark) Flash. Of course, other methods may be used. In addition, in the configuration of this embodiment, a game space image (e.g., 3DCG, etc.) that is the base of the game screen is generated by the server system 1100, but it is also possible to configure the game space image to be generated by the user terminal 1500. In that case, the game screen display control unit 273 controls objects arranged in a virtual three-dimensional space for generating the 3DCG.
[0145] The image generation unit 290 cooperates with the game screen display control unit 273 to generate an image signal for displaying one game screen per frame time (for example, 1 / 60 seconds) based on various data received from the server system 1100, and outputs the generated image signal to the image display unit 390. For example, this can be realized by a processor such as a GPU or a digital signal processor (DSP), a video signal IC, a program such as a video codec, an IC memory for drawing frames such as a frame buffer, and the like.
[0146] The sound generation unit 292 is realized, for example, by a digital signal processor (DSP), a processor such as a voice synthesis IC, an audio codec for playing audio files, etc., and generates audio signals for game sound effects, background music, and various operation sounds, and outputs them to the sound output unit 392.
[0147] The communication control unit 294 performs communication connection and data processing for data communication with an external device (eg, the server system 1100) via the communication unit 394, and realizes data exchange with the external device.
[0148] The image display unit 390 displays various screens such as a game screen based on the image signal input from the image generation unit 290. For example, this can be realized by an image display device such as a flat panel display, a projector, or a head mounted display. In FIG. 2, this corresponds to the touch panel 1506.
[0149] The sound output unit 392 emits sound effects, background music, and the like related to the game based on the audio signal input from the sound generation unit 292. In FIG.
[0150] The communication unit 394 realizes communication by connecting to the network N. For example, it can be realized by a wireless communication device, a modem, a TA, a jack for a wired communication cable, a control circuit, etc. In FIG. 2, the wireless communication module 1553 corresponds to this.
[0151] In the terminal storage unit 500, programs for operating the user terminal 1500 and realizing the functions of the user terminal 1500, data used during execution of the programs, etc. are stored in advance or temporarily stored each time processing is performed. For example, this can be realized by IC memory such as RAM or ROM, a magnetic disk such as a hard disk, an optical disk such as a CD-ROM or DVD, etc. In Fig. 2, this corresponds to the IC memory 1552 and the memory card 1540.
[0152] The terminal storage unit 500 also stores a game client program 502. The game client program 502 is a program for causing the terminal processing unit 200 to function as the user terminal computing unit 270. This game client program 502 may be a dedicated client program according to a technical method for realizing an online game, or may be configured by a web browser program and a plug-in for realizing interactive image display. In this embodiment, the game client program 502 is a copy of a distribution game client program 503 (see FIG. 15) provided by the server system 1100.
[0153] [Processing flow] 18 is a flowchart showing the flow of processing related to the related user registration function performed by the server system 1100, focusing on the execution of a game on one user terminal 1500. The processing described here is realized by the server processing unit 200s reading and executing the server program 501.
[0154] In the server system 1100, the first type related user registration unit 231 performs a first type related user registration process to monitor whether the first condition is satisfied, and the second type related user registration unit 233 performs a second type related user registration process to monitor whether the second condition is satisfied. When the user terminal 1500 completes the login procedure, the first type related user registration unit 231 adds the user terminal 1500 to the targets of monitoring and determines whether the first condition is satisfied. Also, the second type related user registration unit 233 adds the user terminal 1500 to the targets of monitoring and determines whether the second condition is satisfied.
[0155] Then, when the user of the user terminal 1500 completes the friend registration procedure with the user of another user terminal 1500 and satisfies the first condition (step S1: YES), the first type related user registration unit 231 determines whether or not face-to-face data 530 has been generated for the pair of users. If it has been generated (step S3: YES), the first type related user registration unit 231 proceeds to step S21 to re-register the face-to-face friend.
[0156] Furthermore, if there is no face-to-face data 530 for the pair of users (step S3: NO), and there is still space for each user to be registered and the limited number of users condition is met (step S5: YES), the first type related user registration unit 231 registers each user as a friend (step S7). If the limited number of users condition is not met (step S5: NO), the friend registration in step S7 is not performed.
[0157] Furthermore, when the user of the user terminal 1500 completes the face-to-face procedure together with the user of another user terminal 1500 and the second condition is satisfied (step S9: YES), the second type related user registration unit 233 determines whether face-to-face data 530 has been generated for the pair of users in question. If it has been generated (step S11: YES), the process proceeds to step S21 to re-register the face-to-face friend.
[0158] If there is no face-to-face data 530 for the pair of users (step S11: NO), the second type related user registration unit 233 proceeds to step S13 to perform new registration. After generating face-to-face data 530 (step S13), if there is a registration slot for each user remaining and the limited number of users condition is met (step S15: YES), the second type related user registration unit 233 newly registers each user as a face-to-face friend (step S17). Then, proceeds to step S19. If the limited number of users condition is not met (step S5: NO), the new registration of the face-to-face friend in step S17 is not performed and the process proceeds to step S19. Then, in step S19, the privilege granting control unit 239 performs a privilege granting control process to grant each user a privilege for face-to-face according to the face-to-face rank 5315, 5335.
[0159] On the other hand, in step S21, if there is a registration slot remaining for each user and the limited number condition is met (step S21: YES), the second type related user registration unit 233 re-registers each user as a face-to-face friend (step S23). If the limited number condition is not met (step S5: NO), the re-registration of the face-to-face friend in step S23 is not performed.
[0160] Furthermore, if a relationship cancellation operation is detected on the user terminal 1500 (step S25: YSE), the registration deletion unit 237 performs a registration deletion process and deletes the registration of the friend or face-to-face friend specified in the relationship cancellation operation (step S27).
[0161] Furthermore, when a related game play operation on the user terminal 1500 is detected (step S29: YES), the related game play control unit 241 performs a related game play control process. That is, if the related game play operation specifies a face-to-face friend (step S31: YES), the related game play control unit 241 selects and uses one of the game control information for face-to-face friends 563 to control the execution of the related game play (step S35). If the related game play operation specifies a friend (step S33: NO), the related game play control unit 241 selects and uses one of the game control information for friends 561 to control the execution of the related game play (step S37).
[0162] After that, the process returns to step S1 and repeats the above-mentioned processing until the game is ended (step S39: NO), and when the game is ended (step S39: YES), this processing ends.
[0163] As described above, according to this embodiment, in addition to friends (first type related users) who are registered by operating their own user terminals 1500 to perform friend request operations and approval operations, it is possible to register face-to-face friends (second type related users) who request a face-to-face meeting procedure when registering. When a face-to-face friend is registered, a face-to-face meeting benefit can be granted to each corresponding user. Then, different game controls can be performed for related game play involving friends and related game play involving face-to-face friends, and the execution of the related game play can be controlled. Therefore, it is possible to realize a method of classifying related users that is different from the conventional method.
[0164] The forms to which the present invention can be applied are not limited to the above-described embodiments, and constituent elements can be added, omitted, or modified as appropriate.
[0165] [Variation 1] In the above embodiment, the server system 1100 of the client-server type game system 1000 is taken as an example of the application of the present invention, but the present invention is not limited thereto. For example, the server system 1100 may be mainly responsible for managing data such as the account information, login information, and user management data 510 of the user 2, and each user terminal 1500 may be mainly responsible for processing such as game progress control and friend registration. In this case, the processing related to the registration of face-to-face friends may be realized by connecting multiple user terminals 1500 in a peer-to-peer manner. In that case, one of the user terminals 1500 is made to perform the function of the server system 1100 of the above embodiment. Alternatively, the function of the game management unit 230 may be shared among multiple user terminals 1500. In this manner, a computer system is configured by connecting multiple user terminals 1500.
[0166] Specifically, an example of the functional configuration of the user terminal 1500A that shares the functions of the server system 1100 of the above embodiment is shown in Fig. 19. In Fig. 19, the same components as those of the above embodiment are given the same reference numerals. In this case, the server system 1100 mainly performs user registration, management of the information, and matching, and provides the information in response to a request from the user terminal 1500A.
[0167] As shown in FIG. 19, in the user terminal 1500A of this modification, the device processing unit 200 has the game management unit 230, and the game screen display control unit 273 is omitted. That is, the user terminal 1500A of this modification does not acquire data for displaying an image of a game screen from the server system 1100, but the game management unit 230 executes processing related to game management to control the progress of the game and generate an image of the game screen. The device storage unit 500 of this user terminal 1500A stores a game program 504 for making the device processing unit 200 function as the user terminal calculation unit 270 and the game management unit 230 to cause the user terminal 1500A to execute an application having a related user registration function, and stores user management data 510 related to the user of the user terminal 1500A, play data 570 related to the user, face-to-face data 530 in which the user ID of the user (own user) is set as the user ID 5311 of the first user or the user ID 5331 of the second user, and game setting data 550.
[0168] The processing flow of the user terminal 1500A of this modification is basically the same as the flowcharts shown in Fig. 5 and Fig. 18, and each step may be interpreted as being executed by the game management unit 230 of the user terminal 1500A. Specifically, the user terminal 1500A performs necessary communication with the user terminal 1500A of the other party (other user) when registering a friend and registering a face-to-face friend, and performs the registration by determining the first condition and the second condition. If the related game play involves a friend but not a face-to-face friend, the related game play is executed based on the first type game control, and if the related game play involves a face-to-face friend but not a friend, the related game play is executed based on the second type game control.
[0169] According to this modification, the same effects as those of the above embodiment can be obtained. Note that the user terminal 1500 may be configured to take on only a part of the functions of the game management unit 230, rather than taking on all of the functions.
[0170] [Variation 2] In the above embodiment, the second condition for registering a meeting friend is "the meeting procedure is completed." The second condition is satisfied when confirmation is made in the confirmation process executed during the meeting procedure, and the meeting friend is registered. However, the second condition can include other conditions as appropriate.
[0171] For example, the second condition may include "having played a specific multiplayer game." For example, playing a music game against each other using idol characters that each user has trained, or playing a music game together. In that case, if the face-to-face procedure has been completed and the target users are playing a game together, they will be registered as face-to-face friends.
[0172] Furthermore, if the related user registration function of this embodiment is applied to a competitive game, the second condition can include "each of the target users has competed in the competitive game." This makes it possible to register the other user as a face-to-face friend after playing against the other user once and understanding the type of player character and play style used. In this case, after the competitive game is played, each user may be prompted to confirm whether or not to register as a face-to-face friend.
[0173] Alternatively, the level, playing history, type of player character used, etc. of the other party may be presented to each user at a predetermined timing before or after the completion of the face-to-face procedure. Then, the user may be prompted to confirm whether or not to register, and the second condition may include "each user choosing to register after the presentation."
[0174] Also, the second condition may be a combination of the first condition. For example, the second condition may be "satisfying the first condition and also satisfying a given additional condition." The additional condition may include at least "the face-to-face procedure has been completed (i.e., confirmation has been made in various confirmation processes)," which was the second condition in the above embodiment. In that case, by completing the face-to-face procedure in addition to the friend registration procedure, registration as a face-to-face friend is possible.
[0175] [Variation 3] Furthermore, the confirmation process executed during the face-to-face meeting procedure is not limited to a configuration in which all of the first to third confirmation processes described in the above embodiment are executed, but may be a configuration in which some of them are executed. For example, the first confirmation process and the second confirmation process may be executed, and the third confirmation process may not be executed. Also, a configuration in which confirmation processes different from the first to third confirmation processes exemplified are appropriately combined and executed is possible.
[0176] For example, instead of the configuration in which the first confirmation process and the second confirmation process are executed in combination, a fourth confirmation process may be executed in which short-distance wireless communication such as Bluetooth (registered trademark) communication or infrared communication is performed between the user terminal (first user terminal) 1500 of the first user and the user terminal (second user terminal) 1500 of the second user to confirm that each user is within a predetermined distance range. Alternatively, a fifth confirmation process may be executed in which communication is performed to confirm that the relay base station is the same, thereby confirming that each user is within a predetermined distance range. For example, this can be realized by transmitting a survey command such as "ping" or "traceroute (tracert)" and judging whether each relay base station is the same from the returned message.
[0177] Also, a selection operation of which confirmation process to execute during the face-to-face procedure may be accepted, and confirmation that the users have actually met each other (are within a predetermined distance range) may be confirmed by executing the confirmation process desired by each target user. For example, confirmation (A) performed by executing a combination of the first confirmation process and the second confirmation process, confirmation (B) performed by executing the fourth confirmation process, and confirmation (C) performed by executing the fifth confirmation process may be selectable. In that case, the face-to-face rank may reflect which confirmation was selected (which confirmation process was used for the face-to-face procedure). In that case, each option is ranked in advance and a score is determined. For example, the scores are set higher in the order of confirmation (B), confirmation (A), and confirmation (C). Then, when setting the face-to-face rank described in the above embodiment, points are added according to which confirmation was performed. In the case of the above-mentioned ranking, the face-to-face rank may be set higher for the selection of confirmation (B) than for the selection of confirmation (A).
[0178] [Variation 4] In the above embodiment, the meeting friends are registered in a plurality of stages by setting the meeting rank according to the type of exchange items exchanged as exchange information when registering the meeting friends. In contrast, the time that the two people spent together before and after the meeting procedure may be calculated as the meeting time, and the meeting rank may be set according to the calculated meeting time.
[0179] The face-to-face time is calculated as the time when each user was in close proximity to each other before and after the face-to-face procedure is completed. For example, it can be calculated by referring to the reception history of the positioning information from the user terminal 1500 of each user. The longer the face-to-face time, the higher the face-to-face rank is set. If the distance is increased immediately after the face-to-face procedure, the face-to-face rank is set to be low, and if the user was in close proximity for several hours before and after the face-to-face procedure, such as when the user met at an event venue and completed the face-to-face procedure, the face-to-face rank is set to be high. Conversely, the longer the face-to-face time, the lower the face-to-face rank may be set. For example, this can be achieved by determining the score of the face-to-face time according to the length of time and classifying the determined score into a rank. The distance range for the close distance may be the same as the distance range used as a reference in the second confirmation process, or may be a wider or narrower distance range than that.
[0180] In that case, the score may be adjusted using the difference in user level between the users. For example, when users with a small difference in user level (user levels of similar levels) register together, the score may be increased even if the meeting time is short, or conversely, decreased. This can be achieved by dividing the level difference into several stages and defining a score conversion formula for each stage.
[0181] Alternatively, the meeting rank may be set using both the type of information exchanged and the meeting time. In this case, the rank may be determined by adding up the points based on the type of information exchanged and the points based on the meeting time.
[0182] [Variation 5] In the above embodiment, when users who have already completed the face-to-face procedure perform the friend registration procedure, they are automatically registered as friends who meet, not as friends. Alternatively, the user may be notified that the face-to-face procedure has already been completed, and may be asked to select whether to register as friends or friends who meet.
[0183] [Variation 6] In the above embodiment, the registration of the face-to-face friend is performed on the condition that the face-to-face procedure is terminated in principle. In contrast, when registered friends approach each other within a predetermined short distance, the relationship may be changed to face-to-face friends without requesting the face-to-face procedure. In that case, the distance between the user positions of each pair of registered friends is monitored. For example, this can be realized by repeatedly executing the second confirmation process described with reference to FIG. 6 for each pair of users. Then, if there is a pair of users whose user positions are within a predetermined distance range, the registration of the friends between the users is deleted and the users are registered as face-to-face friends.
[0184] [Variation 7] In the above embodiment, the related gameplay is defined as the exchange of gifts such as stamina between friends or meeting friends, but the content of the related gameplay is not particularly limited.
[0185] For example, the content of the related game play may be "one of the friends or the meeting friends giving stamina to the other", or "one of the friends or the meeting friends sending a stamina request to the other, and the other responding by giving stamina", etc. In that case, the number of stamina that can be given at one time (or the upper limit) may be different between friends and between meeting friends (for example, more stamina can be given between meeting friends than between friends).
[0186] In this case, the related game play may include "granting a predetermined number of game points as a reward to the person who gave the stamina." In this configuration, the number of stamina that can be given at one time (or the upper limit) may be the same between friends and between friends meeting, while the game points received as a reward may be different between friends and between friends meeting (for example, more game points may be given between friends meeting than between friends).
[0187] In this modified example, stamina is exemplified as a gift to the other person, and game points are exemplified as a reward, but the contents of either are not particularly limited. For example, they can be set appropriately in the same way as the meeting benefits and presents mentioned in the above embodiment.
[0188] [Variation 8] Also, for example, related gameplay may include playing a game against a friend or a meet-up friend, or playing a game cooperatively. For example, if the related user registration function of this embodiment is applied to a competitive game, the presentation control performed in gameplay against a friend is the first type of game control. Also, the presentation control performed in gameplay against a meet-up friend is the second type of game control. Then, the execution of the related gameplay may be controlled by controlling the progress of the competitive game with different presentation controls for both.
[0189] In the case of a configuration in which groups compete against each other, the presentation control performed in gameplay when a group does not include a face-to-face friend but does include a friend is set as a first type game control, the presentation control performed in gameplay when a group does not include a friend but includes a face-to-face friend is set as a second type game control, and the presentation control performed in gameplay when a group includes both a friend and a face-to-face friend is set as a third type game control. Alternatively, the presentation control when a group is composed of only friends may be set as a first type game control, the presentation control when a group is composed of only face-to-face friends may be set as a second type game control, and the presentation control when a group is composed of friends and face-to-face friends may be set as a third type game control. Then, the execution of related gameplay may be controlled by controlling the progress of the competitive game with each of the first to third game controls being different presentation controls. The third type game control may be set to the same content as the second type game control and different from the first type game control.
[0190] In addition, the related game play can be "inviting other users to a room created / edited as the user's avatar space" or "visiting another user's room." In this case, the game control related to the related game play is the control of events occurring in the room, the control of the presentation, the control of the number of users that can be invited at one time (the upper limit of invitations), etc. The type 1 game control applied when friends visit each other's rooms and the type 1 game control applied when face-to-face friends visit each other's rooms may have different controls of events, presentations, the upper limit of invitations, etc.
[0191] [Variation 9] Moreover, the present invention is not limited to gameplay, but can also be applied to other actions (related actions) involving related users. For example, in a social networking service (SNS) that provides video distribution services, an example would be the act of watching a distributed video together with other users. When watching a distributed video, a user can use his or her own avatar to perform a related action, which is the provision of an item to the poster, called a "tipping" or "gift."
[0192] In that case, in addition to registering regular followers (related users), it will be possible to register special followers (face-to-face followers) who can be registered by meeting face-to-face. The types and number of items that can be provided as "tipping" etc. will be controlled as action control related to the related action. In other words, the content of the control of the types of items that can be provided etc. will be different between the first type of action control applied when regular followers watch together and the second type of action control applied when face-to-face followers watch together. For example, the types of items related to the second type of action control will be increased compared to the types related to the first type of action control, or expensive items will be included.
[0193] [Variation 10] In the above embodiment, when the first user and the second user perform the friend registration procedure or the face-to-face procedure, the remaining registration slots for both users are determined as the limit number condition, and if the limit number condition is satisfied, the users are registered as friends or face-to-face friends. In contrast, for the registration of face-to-face friends, even if there is no vacancy in the registration slot of one of the first user and the second user, if there is vacancy in the registration slot of the other user, the users may be registered as face-to-face friends. In that case, it is sufficient to determine that "there is vacancy in at least one of the registration slots of the first user (own user) and the second user (other user)." From the perspective of the first user (own user), even if there is no vacancy in the registration slot, if there is vacancy in the registration slot of the second user (other user), the second user can be registered as a face-to-face friend. In that case, the upper limit number of the first user (own user) itself may be changed by increasing it by one person.
[0194] Also, even if there is no vacancy in the registration frame of either user, if it is a registration of a face-to-face friend, each user may be registered as a face-to-face friend. That is, for example, as in the above embodiment, the limit number condition is that "there is a vacancy in the registration frame of the first user, and there is a vacancy in the registration frame of the second user." If the limit number condition is not met, a new friend is not registered. On the other hand, for registration of a face-to-face friend, the limit number condition is not applied and a new face-to-face friend is registered. In that case, if there is no vacancy in the registration frame of either user at the time of face-to-face registration, the upper limit number of the user itself may be increased by one person.
[0195] Alternatively, the permission of registration may be determined for each user. In other words, when there is a vacancy in the registration frame for the first user and there is no vacancy in the registration frame for the second user, the registration of the first user is permitted and the second user is registered as a face-to-face friend, but the registration of the second user with the first user as a face-to-face friend is not permitted.
[0196] In addition, as in the above embodiment, when the new meeting procedure is completed but registration as meeting friends is not completed because one of the users has no vacant registration slots, the pair of users may be automatically registered as meeting friends by waiting for a registration slot to become available for the relevant user.
[0197] [Variation 11] Also, data on the intimacy between each user and a user registered as a friend or face-to-face friend may be generated and managed for use in the game. Fig. 20 is a diagram showing an example of the data configuration of intimacy data 590 between a user and a user registered as a face-to-face friend. In the example of Fig. 20, the intimacy data 590 includes a user ID 591 of the user, a friend index value 593, a face-to-face friend index value 595, and an overall intimacy level 597.
[0198] The friend index value 593 is updated from time to time based on, for example, the number and frequency of chats exchanged with the user, the number and frequency of related games played together (in the example of the above embodiment, the number and frequency of gifts given to each other), the number and frequency of transfers and / or receipts of game objects, etc.
[0199] The face-to-face friend index value 595 is updated from time to time based on the number and frequency of meetings with the user, the number and frequency of information exchanges, the types of items exchanged at those times, and the like.
[0200] Overall intimacy level 597 indicates the overall intimacy with the user, and is set based on friend index value 593 and face-to-face friend index value 595. For example, the overall intimacy level 597 is set by calculating the sum of friend index value 593 and face-to-face friend index value 595 and classifying the calculated sum into a plurality of predetermined intimacy ranks. Note that when calculating the total value, the weight of face-to-face friend index value 595 may be increased and the sum may be added up, or conversely, the weight of friend index value 593 may be increased and the sum may be added up.
[0201] The execution of the related game play may be controlled using this intimacy data 590. For example, when a user plays a game in which the user teams up with a face-to-face friend or other user to defeat an enemy character as the related game play, the execution of the game (i.e., the related game play) may be controlled by making it easier for a face-to-face friend with a higher overall intimacy level 597 to activate a combo technique with the user.
[0202] [Variation 12] In addition, in the above embodiment, an example of a "friend" is described as a related user, but the related user is not limited to a "friend." For example, a candidate user who can be a buddy or partner in cooperative play may be a related user, or a candidate user who can be an opponent or rival in competitive play may be a related user. [Explanation of symbols]
[0203] 1000…Game System 1100...Server system 100s…Operation input section 200s…Server processing section 210...User Management Department 230…Game Management Department 231…Type 1 Related User Registration Department 233…Type 2 Related User Registration Department 235...Confirmation process execution control unit 237…Deregistration Department 239...Benefit granting control unit 241...Related game play control unit 290s…Image generation section 292s…sound generation section 294s…Communication control section 390s...Image display section 392s…Sound output section 394s…Communication Department 500s…Server storage 501...Server program 503...Streaming game client program 510...User management data 515...User level 520...Related user data 521…Maximum number of people 523…Friend List 525…Meeting Friend List 530…Face-to-face data 531...First user data 5311...User ID 5313…Exchange item type 5315…Meeting rank 533...Secondary user data 5331...User ID 5333…Exchange item type 5335…Meeting rank 535…Meeting date and time 537…Meeting place 550...Game setting data 551...Meeting bonus data 560...Related gameplay control information 561…Game control information for friends 563…Game control information for face-to-face friends 570...Play data 571...Positioning history 1500, 1500A...User terminal 100...Operation input section 200...Terminal processing section 270...user terminal computing unit 271...Operation signal transmission control unit 273...Game screen display control unit 290...Image generation unit 292...Sound generation section 294…Communication control unit 390...Image display section 392…Sound output section 394…Communications Department 500…Device memory section 502 - Game client program 504...Game program N…Network 2. User
Claims
1. A program for causing a user terminal of a user to execute an application having a related user registration function that allows the user to register other users as related users with whom the user is involved, a first type related user registration means for registering the other user who satisfies a first condition for being able to be registered as a first type related user as the first type related user; a second type related user registration means for registering the other user who satisfies a second condition different from the first condition as a condition for being able to be registered as a second type related user, as the second type related user; a related action control means for controlling the execution of a related action which is an action involving a related user in the application, the related action being 1) a related action based on a first type action control when the first type related user is involved but not the second type related user, and 2) a related action based on a second type action control when the second type related user is involved but not the first type related user; and causing the user terminal to function as The second type related user registration means includes: a confirmation process execution control means for executing a confirmation process including attempting a predetermined communication with a terminal of the other user as a destination, as a predetermined confirmation process determined for confirming that the other user is within a predetermined distance range; and determining whether the second condition is satisfied by including in the second condition that the other user has been confirmed by the confirmation process. program.
2. The related action control means 3) performs control to execute a related action based on a third type action control when the first type related user and the second type related user are involved. The program according to claim 1.
3. a privilege granting control means for controlling granting of a given privilege to a second-type related user and / or the user itself when a new second-type related user is registered by the second-type related user registration means; The program according to claim 1 or 2, for causing the user terminal to further function as a
4. a registration canceling means for canceling the registration of the second type related user; and causing the user terminal to further function as: the benefit granting control means grants the benefit only when the other user who has not been registered as the second type related user in the past is newly registered as the second type related user by the second type related user registration means. The program according to claim 3.
5. a registration canceling means for canceling the registration of the second type related user; and causing the user terminal to further function as: the second type related user registration means registers the other user who was previously registered as the second type related user and satisfies the first condition as the second type related user; The program according to any one of claims 1 to 4.
6. The confirmation process execution control means Displaying and controlling a given registration identifier on the user terminal; receiving information of the registration identifier from the terminal of the other user; performing said verification process including: The program according to any one of claims 1 to 5.
7. The user terminal includes a positioning unit, The confirmation process execution control means A communication for acquiring the location of another user from the terminal of the other user; determining whether a distance between the acquired other user's position and the position measured by the positioning unit is within the distance range; performing said verification process including: The program according to any one of claims 1 to 6.
8. The second type related user registration means registers the second type related user in association with the acquired other user position related to the second type related user. The program according to claim 7.
9. the second type related user registration means performs communication to acquire a first type related user position from a terminal of the first type related user, and when a distance between the first type related user position and a position measured by the positioning unit is within the distance range, registers the first type related user as the second type related user; The program according to claim 7 or 8.
10. the second type related user registration means registers the second type related users in a plurality of stages according to an elapsed time during which a distance between the other user's position and the position measured by the positioning unit is within the distance range. The program according to any one of claims 7 to 9.
11. The predetermined communication is short-range wireless communication or communication for confirming that the relay base station is the same. The program according to any one of claims 1 to 10.
12. the second type related user registration means determines whether or not the second condition is satisfied by including in the second condition that a predetermined multiplayer game in which the user and the other user participate has been executed. The program according to any one of claims 1 to 11.
13. the second type related user registration means permits registration of a new second type related user when a given limit on the number of registered users has not been reached; The program according to any one of claims 1 to 12.
14. The limited number of users is a number related to a total number of registered first type related users and second type related users, the second type related user registration means permits the registration of a new second type related user to the user terminal when a total number of registered first type related users and second type related users registered in association with the user of the user reaches the limited number and a total number of registered first type related users and second type related users registered in association with the other user does not reach the limited number; The program according to claim 13.
15. the first type related user registration means does not allow the registration of a new first type related user when a total number of registered first type related users and second type related users has reached a given limit number; the second type related user registration means permits the registration of a new second type related user regardless of whether or not the total number of registered first type related users and second type related users has reached the limited number. The program according to any one of claims 1 to 12.
16. The confirmation process execution control means performing communication between the terminal of the other user and the terminal of the user to exchange exchange information selected by the user; performing said verification process, the second type related user registration means registers the second type related users in a plurality of stages based on the exchange information selected by the user himself / herself. The program according to any one of claims 1 to 15.
17. There are multiple types of predetermined communication, the confirmation process execution control means is capable of executing the confirmation process by attempting different types of the predetermined communication; the second type associated user registration means registers the second type associated users in a plurality of stages based on the type of the predetermined communication attempted when confirmed by the confirmation process; The program according to any one of claims 1 to 15.
18. A server system communicatively connected to a first user terminal of a first user and a second user terminal of a second user, a first type related user registration means for registering the first user and the second user as the first type related user when a first condition for allowing the first user and the second user to be registered as a first type related user is satisfied; a second type related user registration means for registering the first user and the second user as the second type related user when a second condition different from the first condition is satisfied as a condition for the first user and the second user to be registered as a second type related user; a related action control means for controlling execution of the related action based on a first type action control when the first type related users are involved with each other, and based on a second type action control when the second type related users are involved with each other, as the related action; Equipped with The second type related user registration means includes: a confirmation process execution control means for executing a confirmation process including attempting a predetermined communication between the first user terminal and the second user terminal as a predetermined confirmation process defined for confirming that the first user and the second user are within a predetermined distance range; and determining whether or not the second condition is satisfied by including the fact that the confirmation has been made by the confirmation process in the second condition. Server system.
19. A server system according to claim 18; The first user terminal and the second user terminal; Equipped with an entertainment system.
Citation Information
Patent Citations
Game server, program for game server, and game system
JP2015156912A
Program and information processing unit
JP2017006270A
Vehicle
JP2017019460A
Game program, method, and information processing device
JP2020054725A
Game program, method, and information processing device
JP2020110446A