JP2024029461A - Programs, information processing devices, and information processing systems - Google Patents

Abstract

The present invention provides a service that allows users to understand the history of association with other users. A program causes a computer to automatically associate a second user with the first user after deciding to share, during, or after sharing a predetermined experience with a first user within a predetermined service; , an association means capable of automatically making an application to the second user for associating the second user with the first user, and a memory that stores information regarding the history of association of the second user with the first user. To function as a means. [Selection diagram] Figure 9

Description

The present invention relates to a program, an information processing device, and an information processing system.

BACKGROUND ART Services such as games that allow each user to register or follow other users as friends have been known (for example, see Patent Document 1).

Japanese Patent Application Publication No. 2013-188456

By the way, in services that allow users to be associated with other users, such as friend registration and following, there is a problem in that it may become unclear what led to the association.

The present invention has been made in view of the above-mentioned circumstances, and an object of the present invention is to provide a service that allows users to understand the history of association with other users.

According to one embodiment presented in the present disclosure,
computer,
After deciding to share a predetermined experience with a first user within a predetermined service, automatically associating a second user with the first user during or after the sharing; an association means capable of automatically making an application to the second user for association with a user;
A program is provided that functions as a storage means for storing information regarding the history of association of the second user with the first user.

According to the present invention, a service is provided in which it is possible to understand the history of association with other users.

FIG. 1 is a diagram showing a schematic configuration of a system. FIG. 2 is a block diagram showing the functional configuration of the system. It is a figure showing an example of a related user list display screen. It is a figure which shows an example of a history information input screen. It is a figure which shows an example of a classification list display screen. FIG. 3 is a diagram illustrating an example of displaying a classification list. 12 is a flowchart illustrating an example of a process for automatically associating a user with another user. 12 is a flowchart illustrating an example of a process for automatically canceling associations of other users with a user. 3 is a flowchart illustrating an example of a process related to inputting history information. 3 is a flowchart illustrating an example of processing related to creation and display of a classification list. 3 is a flowchart illustrating an example of processing related to creation and display of a classification list.

Embodiments of the present invention will be described below with reference to the drawings.

<System hardware configuration>
As shown in FIG. 1, the system 1 of this embodiment includes a plurality of terminal devices 10 and a server 20.

The terminal device 10 and the server 20 are connected via a network 2. The network 2 is, for example, the Internet, a mobile communication system (for example, 3G, 4G, 5G, LTE (Long Term Evolution), etc.), WiFi (Wireless Fidelity), Bluetooth (registered trademark), other communication lines, or a combination thereof. It may be configured by any of the following. Furthermore, the connection between the terminal device 10 and the server 20 does not matter whether it is a wired connection or a wireless connection.

The server 20 (in other words, a computer, an information processing device) may be, for example, a general-purpose computer such as a workstation or a personal computer. The server 20 includes a processor 21, a memory 22, a storage 23, a communication IF (interface) 24, and an input/output IF 25. These components included in the server 20 are connected to each other by a communication bus.

The processor 21 controls the overall operation of the server 20. The processor 21 may include a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), and the like. The processor 21 reads the program from the storage 23 and expands it into the memory 22. The processor 21 executes the developed program.

Memory 22 is a main storage device. The memory 22 is configured by a storage device such as a ROM (Read Only Memory) and a RAM (Random Access Memory). The memory 22 provides a work area for the processor 21 by temporarily storing programs and various data that the processor 21 reads from the storage 23 . The memory 22 also temporarily stores various data generated while the processor 21 is operating according to a program.

Note that in this embodiment, the program may be a program for realizing a predetermined service (in other words, an application) such as a game on the terminal device 10. Further, the program may be a program that realizes the predetermined service through cooperation between the terminal device 10 and the server 20. Note that the predetermined service realized through cooperation between the terminal device 10 and the server 20 may be, for example, a service provided on a browser started on the terminal device 10. Further, the program may be a program that realizes the predetermined service through the cooperation of a plurality of terminal devices 10. Further, the various data include, for example, data related to services such as user information and service information, and instructions and notifications transmitted and received between the terminal device 10 and the server 20.

The storage 23 is an auxiliary storage device. The storage 23 is configured by a storage device such as a flash memory or an HDD (Hard Disk Drive), for example. The storage 23 stores various data related to services.

The communication IF 24 controls transmission and reception of various data via the network between the server 20 and the terminal device 10 and the like.

The input/output IF 25 is an interface through which the server 20 receives data input, and an interface through which the server 20 outputs data. The input/output IF 25 may include, for example, an input section that is an information input device such as a mouse and a keyboard, and a display section that is a device that displays and outputs images.

The terminal device 10 (in other words, a computer, an information processing device) may be, for example, a smartphone, a feature phone, a PDA (Personal Digital Assistant), a tablet computer, a personal computer, a wearable terminal, a game device, or the like. The terminal device 10 may be a mobile terminal. The terminal device 10 may be a portable terminal when the user receives a service (for example, when playing a game).

The terminal device 10 includes a processor 11 , a memory 12 , a storage 13 , a communication IF 14 , an input/output IF 15 , an input section 17 , and a display section 18 . These components included in the terminal device 10 are connected to each other by a communication bus.

The processor 11 controls the overall operation of the terminal device 10 . Processor 11 may include a CPU, MPU, GPU, and the like. The processor 11 reads the program from the storage 13 and expands it into the memory 12. The processor 11 executes the expanded program.

Memory 12 is a main storage device. The memory 12 is comprised of storage devices such as ROM and RAM, for example. The memory 12 provides a work area for the processor 11 by temporarily storing programs and various data that the processor 11 reads from the storage 13 . The memory 12 also temporarily stores various data generated while the processor 11 is operating according to a program.

The storage 13 is an auxiliary storage device. The storage 13 is configured by a storage device such as a flash memory or an HDD, for example. The storage 13 stores various data related to services.

The communication IF 14 controls transmission and reception of various data via the network between the terminal device 10 and the server 20 and the like.

The input/output IF 15 is an interface for the terminal device 10 to receive data input, and is an interface for the terminal device 10 to output data. The input/output IF 15 may input/output data via, for example, a USB (Universal Serial Bus). The input/output IF 15 may include an input section 17, a display section 18, and the like.

The input unit 17 receives input from the user. The input unit 17 may be, for example, a pointing device such as a touch pad. The display unit 18 displays images. The display unit 18 may be, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display. The terminal device 10 includes, for example, a touch screen 16 that is an electronic component that combines an input section 17 and a display section 18.

The input unit 17 detects a position input on the input screen by a user's operation (for example, a touch operation, a tap operation, a slide operation, a swipe operation, a flick operation, a pinch-in operation, a pinch-out operation, etc.). It has a function of transmitting information indicating the position as an input signal. The touch panel as the input unit 17 can employ a capacitive type, a resistive film type, or the like, but other types may be used.

Note that the input unit 17 may be, for example, a keyboard, various physical buttons, various sensors (for example, an acceleration sensor or an angular velocity sensor), an operation stick, a camera, a microphone, or the like. Further, the display unit 18 may be, for example, a projector.

<Functional configuration of the system>
FIG. 2 is a block diagram showing the functional configuration of the server 20 and the terminal device 10. The server 20 in this embodiment has, for example, a function of providing each terminal device 10 with various data and programs necessary to provide a service, a function of collecting and managing data related to the service from each terminal device 10, and a plurality of functions. It has a function to perform synchronization processing between terminal devices 10, etc.

Note that in this embodiment, the server 20 identifies each user and the terminal device 10 using user accounts registered in advance. The method of registering an account is not particularly limited. For example, the terminal device 10 or another device such as a personal computer transmits information necessary for user account registration to the server 20 based on the user's operation, and the server 20 sends information necessary for each user's account registration based on the received information. You may also create and save an account. Further, each user accesses the server 20 from his or her own terminal device 10, logs in with his or her own account, and uses the service (in other words, application) of this embodiment. In addition, below, when a certain user's terminal device 10 is referred to, it refers to the terminal device 10 etc. that the certain user logs in with his/her own account.

As shown in FIG. 2, the server 20 functions as a control unit 210 and a storage unit 220 through the cooperation of a processor 21, a memory 22, a storage 23, a communication IF (interface) 24, an input/output IF 25, and the like. The storage unit 220 stores various data used by the control unit 210. Various types of data include, for example, program 221, service information 222, and user information 223.

The program 221 is a program for realizing a service. Service information 222 and user information 223 are data referenced by control unit 210 when executing program 221.

Note that the program 221 may include, in addition to the program executed on the server 20 side, a program (program 121 to be described later) that is transmitted to the terminal device 10 and executed on the terminal device 10 side. Alternatively, the storage unit 220 may store the program 221 executed on the server 20 side and the program executed on the terminal device 10 side.

Service information 222 is information common between accounts. The service information 222 includes, for example, information for defining various virtual spaces. A virtual space is a space in which objects such as a user's character are placed. The service information 222 also includes, for example, the location, size, color, and shape of background objects such as buildings, trees, and stones placed in the virtual space, and non-player characters (NPCs) between accounts. Contains various configuration information regarding common objects. Further, the service information 222 includes, for example, setting values of various parameters of the non-player character. In the following, a character object placed in a virtual space may be simply referred to as a "character."

The user information 223 is information managed for each service account. The user information 223 includes, for example, information regarding the user's character, information regarding related users to be described later, information regarding owned assets, information indicating the degree of progress of the game, etc. Examples of held assets include currency and items in virtual space.

The control unit 210 controls various processes related to the service by executing a program 221 stored in the storage unit 220. The control unit 210 includes, for example, a transmitting/receiving unit 211, a server processing unit 212, a synchronization processing unit 214, and a related user management unit 215.

The transmitter/receiver 211 transmits or receives various data. The transmitting/receiving unit 211 receives, for example, requests for transmission of various data and programs, requests for synchronization processing to support a multiplayer function, data to be subjected to synchronization processing, etc. from each terminal device 10, and sends them to the server processing unit 212. give it to Further, the transmitting/receiving unit 211 transmits various data and programs including instructions for synchronization to each terminal device 10 under the control of the server processing unit 212 .

In this embodiment, the multiplay function is a function that provides services in a synchronized state for multiple accounts. The server 20 and the terminal device 10 of the system 1 are configured to support multiplayer functions when multiple accounts logged into the system 1 use predetermined content together (for example, when playing a game together). Executes various processes.

The server processing unit 212 provides services to the terminal device 10 by executing arithmetic processing described in the program 221 in response to requests from the terminal device 10 and the like. For example, when the server processing unit 212 receives a request for synchronization processing to support the multiplay function or data to be subjected to synchronization processing from the terminal device 10 via the transmission/reception unit 211, the server processing unit 212 performs synchronization processing to support the multiplay function. Execute processing. Further, the server processing unit 212 instructs the transmitting/receiving unit 211 to transmit the service information 222 or the user information 223.

The synchronization processing unit 214 executes synchronization processing to support the multiplayer function according to instructions from the server processing unit 212. For example, when the server 20 transmits information to a plurality of terminal devices 10, the synchronization processing unit 214 transmits information to each terminal device 10 at the same time, so that the synchronization processing unit 214 can prevent a game or the like that is progressing between each terminal device 10. Get in sync. Specifically, the synchronization processing unit 214 simultaneously transmits the operation information received within a predetermined period (for example, one frame) from the terminal device 10 corresponding to each account to each terminal device 10 every predetermined period. The operation information is information related to an operation input to the terminal device 10. The synchronization timing and information to be synchronized may be received from the server processing unit 212 at any time. By executing the synchronization process, it is possible to simultaneously reflect an event within a service caused by an operation input on one terminal device 10 on other terminal devices 10.

The related user management unit 215 performs control related to association between users. The related user management section 215 includes an association section 216, a cancellation section 217, a list creation section 218, and a history information management section 219. Control by the related user management unit 215 will be described in detail later.

The terminal device 10 in this embodiment has, for example, a function as an input device that receives input operations from a user, and a function as an output device that outputs images and sounds related to a service.

The terminal device 10 functions as a control unit 110 and a storage unit 120 through cooperation of a processor 11, a memory 12, a storage 13, a communication IF 14, an input/output IF 15, and the like. The storage unit 120 stores various data used by the control unit 110. Various types of data include, for example, program 121, service information 122, and user information 123.

The program 121 is a program for realizing a service on the terminal device 10 side. Service information 122 and user information 123 are data referenced by control unit 110 when executing program 121.

The service information 122 includes the same information as the service information 222 of the server 20 described above. Therefore, a description of the service information 122 will be omitted here.

The user information 123 is data related to the account of the user who uses the terminal device 10, and includes the same information as the user information 223 of the server 20 described above. Therefore, a description of the user information 123 will be omitted here.

The control unit 110 controls various processes related to services executed in the terminal device 10 by executing a program 121 stored in the storage unit 120. The control unit 110 includes, for example, an operation reception unit 111, a transmission/reception unit 112, a progress unit 113, and a display control unit 114.

The operation accepting unit 111 accepts an operation input by a user via the input unit 17 (hereinafter also referred to as an “input operation”). Specifically, when an input operation is performed on the input unit 17, the operation reception unit 111 detects the coordinates of the input position and the type of input operation. Examples of the types of input operations include various operations using fingers or the like, such as touch operation, tap operation, slide operation, swipe operation, flick operation, pinch-in operation, and pinch-out operation. The input operation is not limited to an operation that physically contacts the input unit 17 (for example, the touch screen 16), but may also include a non-contact operation. Note that an operation that ends a previously performed input operation, such as a touch-off operation that ends contact with the touch screen 16, can also be considered as one type of input operation.

Here, the operation reception unit 111 can also accept an input operation performed using an operation device connected via the input/output IF 15 in the same way as an input operation to the input unit 17.

The transmitter/receiver 112 transmits and receives various data. A specific example will be described below.

The transmitting/receiving unit 112 transmits service information 122 or user information 123, a synchronization request for supporting the multiplayer function, etc. to the server 20. The transmitting/receiving unit 112 receives various data, programs, data for synchronization to support the multiplay function, etc. from the server 20. The data for synchronization includes, for example, synchronization instruction data for instructing the terminal devices 10 participating in the multiplayer to synchronize. The synchronization instruction data includes, for example, data to be synchronized, the type of the data, data for specifying the timing of synchronization, and the like.

The transmitter/receiver 112 transmits operation information regarding the input operation accepted by the operation receiver 111 to the server 20 . The transmitting/receiving unit 112 receives operation information related to operations input by other users on other terminal devices 10 from the server 20 .

The progress unit 113 executes various processes related to the progress of the service (eg, progress of the game, etc.). A specific example will be described below.

The proceeding unit 113 defines a virtual space based on information included in the service information 122 for defining a virtual space. The proceeding unit 113 arranges the object in the virtual space based on the object setting information included in the service information 122. The progression unit 113 controls objects placed in the virtual space. Specifically, the progression unit 113 controls the object to change the position, orientation, shape, color, etc. of the object in the virtual space, and to cause the object to perform a predetermined action.

The progression unit 113 defines a virtual camera for specifying an area to be presented to the user in the virtual space. The proceeding unit 113 arranges the virtual camera in the virtual space by defining the position and orientation of the virtual camera in the virtual space. The proceeding unit 113 instructs the display control unit 114 to generate an image depicting a viewing area defined by the virtual camera and an object placed in this viewing area.

The position and orientation of the virtual camera can be determined as appropriate for each virtual space. For example, the advancing unit 113 uses the position and orientation of the specific object as a reference, and arranges the virtual camera so that the specific object is located in the center of the viewing area in a specific orientation. At this time, the advancing unit 113 adjusts the position and orientation of the virtual camera using the direction, distance, and angle with respect to the specific object. The specific object may be a dynamic object such as a user's character or a non-player character, or a static object such as a building, tree, or stone. Dynamic objects include characters that operate based on each user's operation, and characters that operate based on programs 121 and 221 (for example, non-player characters, etc.).

The progression unit 113 interprets the content of the user's instruction based on the coordinates of the input position detected by the operation reception unit 111, the type of input operation, and the like. The progress unit 113 executes various determination processes related to the progress of the service based on the interpreted instruction content and the like. The progression unit 113 advances the service while controlling objects, virtual cameras, etc. based on the results of the determination process and the like. The progress unit 113 updates, adds, or deletes the service information 122 and the user information 123 according to the progress of the service.

The display control unit 114 causes the display unit 18 to display an image. A specific example will be described below.

The display control unit 114 generates an image depicting the field of view of the virtual camera defined by the progression unit 113 and objects existing in the area in the virtual space, and causes the display unit 18 to display the image. The display control unit 114 superimposes and draws objects related to the UI (User Interface) necessary for various operations of the service, such as icons, buttons, and menus indicating various parameters, on the image to be displayed on the display unit 18. can do.

Note that the functions of the terminal device 10 and the server 20 shown in FIG. 2 are merely examples. Each of the terminal device 10 and the server 20 may have at least some of the functions of other devices. In other words, in this embodiment, the server 20 may include some or all of the functional blocks included in the terminal device 10, and the terminal device 10 may include some or all of the functional blocks included in the server 20. . Further, each device such as the terminal device 10 and the server 20 does not need to be realized by an integrated device, and may be realized by, for example, a plurality of devices connected via a network or the like. Further, the system 1 may be configured by only the terminal device 10 or the server 20, for example. In other words, the system 1 does not need to be realized by a plurality of devices connected via a network.

<Processing according to this embodiment>
Next, processing according to this embodiment will be explained. In this embodiment, the processor 11 of the terminal device 10 or the processor 21 of the server 20 executes a program stored in the system 1 to perform each process described below. However, at least a portion of the processing performed by the processor 11, which will be described later, may be performed by a processor other than the processor 11. Further, at least a part of the processing to be described later and performed by the processor 21 may be executed by a processor other than the processor 21. In other words, the computer that executes the program in this embodiment may be either the terminal device 10 or the server 20, or may be realized by a combination of multiple devices.

The service provided by the system 1 of this embodiment (in other words, the application executed by the system 1) may be, for example, a game, an SNS (Social Networking Service), something related to the metaverse, etc. It's okay.

In the service of this embodiment, a user can register other users as friends. A friend refers to a relationship in which the certain user and the other user are associated with each other. In other words, a friend refers to a relationship in which one user is associated with another user, and the other user is associated with one user. That is, if the second user is a friend from the perspective of the first user, the first user becomes a friend from the perspective of the second user. A friend may be a relationship established based on mutual consent between a certain user and another user.

With the service of this embodiment, users can follow other users. Following refers to a user registering another user in association with the user. That is, when a first user follows a second user, the second user does not necessarily follow the first user. Following may be a relationship that can be established based on the will of one party.

Information indicating other users associated with each user is stored in the storage unit 220 as user information 223. Note that this information may be stored in the storage unit 120 as the user information 123. Further, the information may be any information as long as it can identify users associated with each user (for example, each user's friends or following users). Specifically, for example, by using a user ID that can uniquely identify each user (in other words, identification information), each user's user ID is linked to the user ID of another user associated with each user. By storing each user's friends or following users, it is possible to manage each user's friends or following users. That is, when registering another user as a friend or a follower friend of a certain user, the user ID of the other user may be stored in the storage unit 220 in association with the user ID of the certain user.

Furthermore, each user has more information about his or her friends than users who are not friends (for example, information indicating whether the user is logged in, information issued by the user, information about the user, etc.). The user may be able to easily view (in other words, check) information regarding ranks (described later) on his or her own terminal device 10. In other words, when a user is friends with another user, the user may have an advantage in viewing information regarding the other user, compared to a case where the user is not friends with the other user. It should be noted that advantages in viewing information include cases where the effort required for viewing is small, such as a small number of operations on the terminal device 10 required for viewing, cases where there are few time restrictions on viewing, and other cases. This includes cases where you can view specific information that is otherwise not viewable. Further, within the service, for example, there may be a function that can only be used with one's own friends. Specifically, within the service, there may be specific functions, specific games, etc. that can only be played with one's own friends. Furthermore, within the service, it may be possible to send or receive certain messages only with one's own friends. Furthermore, within the service, it may be possible to exchange held assets (for example, exchange items) only with one's own friends. In other words, a friend is a predetermined function within the service that cannot be used with users who are not friends (for example, a function that cannot be used even with users who follow you). It may also refer to a user who can use the Note that the function may be a function that facilitates matching with friends (in other words, using specific content together (for example, participating in the same match or event)). .

In addition, each user can more easily view (confirm) information about users he/she follows on his/her own terminal device 10 than users he/she does not follow (and is not a friend of). It may be . In other words, when a user follows another user, the user may have an advantage in viewing information regarding the other user, compared to a case where the user does not follow the other user. Further, within the service, for example, there may be a function that can only be used with users that the user follows. In other words, a following user is a user who can use certain functions within the service that cannot be used with users who do not follow (and are not friends). It may be something. Note that there may be cases where one user is following the other user, and the other user is not following the one user. In this case, the one user may have an advantage over the other user in viewing information regarding the other party. Specifically, for example, one user may be able to view specific information regarding the other user, but the other user may not be able to view specific information regarding the one user.

(Automatic association)
The association unit 216 identifies other users who share a predetermined experience with a certain user (hereinafter also referred to as "first user") within the service. Further, the association unit 216 automatically registers the specified other user as a friend of the user. In other words, the association unit 216 automatically associates the specified other user and the user with each other. In other words, the association unit 216 performs an association process of associating the identified other user and the user with each other through an operation by the user to instruct the association and an operation by the other user to instruct the association. Do it without. Note that hereinafter, any user among the plurality of users who use the service may be referred to as a first user. Further, a user other than the first user, such as another user who is automatically registered as a friend of the first user, who is identified by the association unit 216, may be referred to as a second user.

Examples of sharing experiences within a service include: That is, sharing a predetermined experience may mean, for example, "playing the same quest in a game." Furthermore, sharing a predetermined experience may mean, for example, "participating in the same event in a virtual space." Furthermore, sharing a predetermined experience may mean, for example, "having a conversation in a virtual space (including, for example, a conversation by text message)." Moreover, sharing a predetermined experience may mean, for example, "viewing the same video (for example, a live video or a specific scene in a game)". Moreover, sharing a predetermined experience may mean, for example, "using content (for example, an event or video) in the same category." Moreover, sharing a predetermined experience may mean, for example, "visiting (in other words, staying) at the same place in a virtual space." Note that the user's position in the virtual space may be linked to (in other words, correspond to) the user's position in the real world (for example, the position of the user's terminal device 10).

Other users who share a predetermined experience with the user within the service may be, for example, other users who are currently sharing the predetermined experience, other users after the sharing, or users after the sharing decision. It may be another user. Here, other users who have decided to share a predetermined experience include, for example, other users who have been matched in the game, other users who have reserved participation in a predetermined event in the service, The association unit 216 determines whether the user is another user with whom it has been decided to share the predetermined experience, such as another user who is waiting for a predetermined event in the virtual space (for example, a so-called lobby). Possible other users (e.g., other users with whom plans have been made within the service to share a given experience), and users who have only made a promise in the real world to play a game together. Not included.

Further, another user who shares a predetermined experience with the user within the service may be, for example, another user who uses the predetermined content together with the user within the service. In other words, other users who share a predetermined experience with the user within the service may be, for example, other users who are using the predetermined content together, or other users who used the predetermined content together. It may also be another user who you have decided to use together.

Examples of using predetermined contents together within a service include the following. That is, using predetermined content together may mean, for example, "participating together in a predetermined match or quest in a game (for example, participating as an ally or an enemy)." Moreover, using predetermined content together may mean, for example, "participating in a predetermined event together in a virtual space." Moreover, using predetermined content together may mean, for example, "participating in the same group chat on SNS, a game, etc." Furthermore, using predetermined content together may mean, for example, "watching predetermined video (for example, live video or a specific scene in a game) together."

The association unit 216 identifies another user who shares a predetermined experience with the first user as another user to be automatically registered as a friend, but in this case, specifically, Another shared user who has a predetermined relationship with the first user within the service may be specified as the other user to be automatically registered. In other words, when automatically registering another user who shares a predetermined experience with the first user as a friend, the association unit 216 registers the other user who shares a predetermined experience with the first user on the condition that the other user has a predetermined relationship with the first user. You may also automatically register as a friend. An example of the predetermined relationship will be described below.

The predetermined relationship may be, for example, "a relationship in which the positional relationship within the service is a specific relationship." Specifically, the predetermined relationship may be, for example, "a relationship in which both parties belong to a group (for example, a so-called team, party, guild, etc.) that cooperates for a predetermined purpose." Furthermore, the predetermined relationship may be, for example, a “relationship in which the two parties are enemies.”

Further, the predetermined relationship may be, for example, "a relationship in which the relationship determined based on the attributes of at least one user is a specific relationship." Here, examples of the user's attributes include rank, gender, playing time, behavioral tendencies, and characters used (in other words, owned). Note that the rank can be said to indicate a user's proficiency level, and can also be said to indicate a relative position among users. The rank includes what is called a level in a general game. Note that the user's rank may be the user's own rank, or may be the rank of the character used by the user. Furthermore, the character includes a user's avatar and the like. That is, the predetermined relationship may be, for example, "a relationship in which the rank is higher than that of the first user." Further, the predetermined relationship may be, for example, "a relationship in which the genders match (or differ) within the service." Further, the predetermined relationship may be, for example, a "relationship in which the probability of a user performing a nuisance act is low (in other words, the user is not a user who performs a nuisance act)". In addition, whether or not the probability of being harassed is low is determined by, for example, when using the content in the past (for example, other users (here, the other user may be the first user, or other users other than the first user) The number of times the network connection was disconnected during a match or quest) is stored in the storage unit 220 of the server 20 as user information 223 for each user. , the association unit 216 may make the determination based on the number of times or the like. In addition, whether or not the probability of nuisance behavior is low can be determined by checking the user information 222 for each user, such as the number of times a preset prohibited word (in other words, a word to be monitored) is used in a chat within the service. may be stored in the storage unit 220 of the server 20, and the association unit 216 may make the determination based on the number of times or the like.

Moreover, the following is an example of the relationship determined based on the character being used as the user's attribute. That is, the predetermined relationship may be, for example, "a relationship in which the types of characters used do not overlap (in other words, different characters are used)". In addition, the predetermined relationship is, for example, "a relationship that improves the balance of a predetermined group (for example, a party) in terms of character attributes (in other words, user attributes) when a predetermined group (for example, a party) is formed." There may be. Specifically, the predetermined relationship is, for example, ``Characters with different attributes (in other words, strengths, etc.) are used (for example, in a role-playing game or FPS (First Person Shooter), The second user may use a character who is good at attacking, and the second user is using a character who is good at recovery. Further, the predetermined relationship may be, for example, "a relationship in which characters with common attributes (for example, the same) are used".

In other words, a predetermined relationship (for example, a relationship that improves the balance of a predetermined group) may be determined by, for example, one user's attributes (for example, attributes such as "good at attacking" or "good at recovery"), A relationship in which the attributes of the other user complement the attributes of the character used by the user (for example, a relationship such as "good at attacking" and "good at recovery". In other words, one user's The attributes of the user and the attributes of the other user may have a complementary relationship.). More specifically, the predetermined relationship is, for example, ``the attributes of one user, the content of the game (in other words, the achievement of a predetermined objective in the game (for example, defeating a predetermined enemy character, a predetermined It may be a relationship in which attributes that influence the clearing of a stage, victory of a team, etc.) are complemented by attributes of the other user that influence the content of the game.

Further, the predetermined relationship may be, for example, "a relationship in which a predetermined attribute regarding one user and a predetermined attribute regarding the other user are common." Specifically, the predetermined relationship may be, for example, "a relationship in which characters with common attributes are used." Furthermore, the predetermined relationship may be, for example, a “relationship in which rank bands match.” Further, the predetermined relationship may be, for example, a “gender matching relationship”. Further, the predetermined relationship may be, for example, a "relationship with similar behavioral tendencies." In other words, the predetermined relationship is, for example, "an attribute of one user, and the content of the game (in other words, the achievement of a predetermined objective in the game (for example, defeating a predetermined enemy character or completing a predetermined stage)" There may also be a relationship in which an attribute that affects the game (clear, team victory, etc.) and an attribute of the other user that affects the content of the game are common.

Further, the predetermined relationship may be, for example, "a relationship in which a specific relationship is determined based on an action taken by at least one user in content that is being used or used together." . Specifically, the predetermined relationship is, for example, ``a relationship in which someone performs an act of benefit (in other words, an assisting act) in the content they are using together,'' or ``a relationship in which they perform an act of benefit (in other words, an assisting act) in the content they are using together.'' In the content, it may be a relationship in which someone has done something beneficial. Here, the beneficial action includes, for example, an action that recovers the first user's character in a role-playing game, FPS, etc. (including, for example, an action that revives the character), or an enemy character that the first user is trying to defeat. Examples include the act of attacking someone (in other words, the act of assisting an attack). Further, the predetermined relationship may be, for example, "a relationship in which the network connection is broken (has been or has been severed) in content that is used together." In addition, the predetermined relationship is, for example, ``a relationship in which a statement was made (specifically, a statement made by one or both parties) in a group chat in which participants are participating together'' or ``a relationship in which a statement was made in a group chat in which participants are participating together.'' It may also be a relationship in which two people mention each other (or one person mentions the other).

Further, the predetermined relationship may be, for example, "a relationship in which the relationship determined based on the usage results of contents used together is a specific relationship." Specifically, the predetermined relationship may be, for example, ``a relationship in which you won or lost as a teammate in a game you played together,'' or ``a relationship in which you won or lost as an enemy in a game you played together.'' It may be a relationship that resulted in victory or defeat. Further, the predetermined relationship may be, for example, "a relationship in which a predetermined score in a game played together is better than that of the first user." In addition, a predetermined relationship can be defined as, for example, ``a team that has formed a team in a predetermined situation (for example, a predetermined stage (in other words, a map) in various games) that is judged based on the results of playing games together multiple times. In other words, the winning probability is high (in other words, it is higher than a predetermined value. Here, the predetermined value does not have to be a fixed value).

Further, the predetermined relationship may be, for example, "a relationship with a high degree of intimacy determined based on an act performed by at least one user (in other words, a predetermined degree or higher)". Here, the association unit 216 may, for example, determine the level of intimacy based on a friendly behavior performed by one user toward the other user. Specifically, for example, if the second user revives the first user's character in the game, the association unit 216 may be configured to perform actions that the second user has a high level of familiarity with (such as leaving the character alone without resuscitating it). It may be determined that the intimacy level is high (in other words, the intimacy level is higher than a predetermined level) based on the assumption that the intimacy level is high (in other words, the intimacy level is higher than a predetermined level). The association unit 216 also selects a fixed message from a plurality of fixed messages (for example, fixed sentences, so-called stamps, etc., specifically, for example, "Hello", "Nice play", "Let's do our best", etc.). In a service where one party can send a specific message to the other party (for example, "nice play"), it is assumed that the other party has acted in a manner that indicates a high level of intimacy. (In other words, it may be determined that it is more than a predetermined degree). Note that the association unit 216 determines whether the degree of familiarity is high, for example, by determining whether the degree of intimacy is high for each action performed by the user (for example, the action of reviving another user's character, the action of sending a specific fixed message, etc.) Information indicating whether or not the act is highly intimate may be attached, and the judgment may be made based on the information. Further, in this method, for example, a numerical value related to intimacy is assigned to each action performed by the user, and the storage unit 220 stores the cumulative value of the numerical value, and the association unit 216 The cumulative value is increased or decreased based on the user's actions within the site, and when the cumulative value exceeds a predetermined value, it is determined that the degree of intimacy is high (in other words, it is higher than a predetermined degree). etc. may be used.

Further, the predetermined relationship may be, for example, "a relationship in which the period of use of contents used together is longer than a predetermined period." Specifically, the predetermined relationship may be, for example, "a relationship in which both users participate in a group chat together for a predetermined period or longer."

Note that, when specifying another user who has a predetermined relationship with the first user within the service as another user to be automatically registered as a friend, the association unit 216 specifies that one of the relationships exemplified above is satisfied. Instead of specifying other users, it may be possible to specify other users who satisfy a plurality of relationships. In other words, for example, in a case where ``the association unit 216 automatically registers as a friend a user whose positional relationship within the service is a specific relationship with the first user'', the conditions for users to be automatically registered as friends. For example, a user whose relationship is determined based on the attributes of at least one of the users is automatically registered, and the relationship determined based on the attributes of at least one of the users is automatically registered. This may include a configuration in which users whose determined relationship is not a specific relationship are not automatically registered.

The association unit 216 may identify other users who satisfy conditions that can be arbitrarily set by the user (hereinafter referred to as "registration conditions") as other users to be automatically registered as friends. In other words, the predetermined relationship may be, for example, "a relationship that satisfies the registration conditions set by the first user." In other words, each user may be able to arbitrarily set the predetermined relationship (what kind of relationship should other users have with which they are automatically registered as friends). In other words, depending on the settings of the registration conditions, whether or not to automatically register as a friend when each of the above-mentioned relationships is satisfied may be changed.

Specifically, the association unit 216, for example, identifies other users who share a predetermined experience with the first user, and attributes (for example, rank, gender, play time) that the first user has specified as registration conditions. , behavioral tendencies, or characters (for example, character attributes)) may be automatically registered as friends of the first user.

In this way, when a user who satisfies registration conditions that can be arbitrarily set by a user is automatically registered as a friend, the association unit 216 determines whether the other user satisfies the registration conditions set by one user. In this case, if the one user satisfies the registration conditions set by the other user, the one user and the other user may be automatically registered as friends. In other words, when automatically registering another user with whom one user has a predetermined relationship as a friend of the other user, the association unit 216 automatically registers the other user as a friend of the other user. Both users may be registered as friends on the condition that they have a predetermined relationship with each other.

Note that if the registration conditions can be set arbitrarily by the user, the setting method is not particularly limited, but may be, for example, as follows. Specifically, each user may set the conditions of the user he or she wishes to become friends with from his/her own terminal device 10 as the registration conditions. In other words, it may be possible to set a white list that defines conditions for users who want to become friends. Furthermore, each user may set, as registration conditions, conditions for users who do not want to be friends from their own terminal device 10. In other words, it may be possible to set a blacklist that defines conditions for users who do not want to be friends. In other words, a user who satisfies the registration conditions may be a user who does not satisfy the conditions set as conditions for users who do not want to be friends.

Note that whether a certain user has a predetermined relationship with the first user may change depending on the attributes of the first user. Specifically, for example, in an FPS, if the first user is using a character who is good at attacking, the user with a predetermined relationship is the user who is using a character who is good at recovery. If the first user is using a character who is good at recovery, the user with a predetermined relationship may be a user who is using a character who is good at attack.

Furthermore, there may be a condition regarding the number of times the predetermined relationship is established. Specifically, for example, the association unit 216 automatically registers other users who share a predetermined experience within the service with the first user, specifically, other users who have participated in events in the same category, as friends. In this case, other users who have participated in events in the same category N times (where N is an integer of 1 or more) may be automatically registered as friends. Further, for example, when the association unit 216 automatically registers as a friend another user who uses predetermined content together with the first user, specifically, another user who participated in the same match in the game, the same Other users who have participated in the match N times (for example, participated N times in a row) may be automatically registered as friends. Also, for example, when the association unit 216 automatically registers as a friend another user who has performed a beneficial action in content that is used together, the association unit 216 may automatically register as a friend another user who has performed a beneficial action N times. Other users may be automatically registered as friends. Also, for example, when the association unit 216 automatically registers other users who have mutually mentioned each other (or one user has mentioned the other) as friends in a group chat in which they are participating together. Another user who has been mentioned N times may be automatically registered as a friend. Note that the conditions regarding the number of times (specifically, how many times should N be set, etc.) may be arbitrarily set by the user as a registration condition (specifically, at least a part of the registration conditions).

The timing at which the association unit 216 automatically registers a user who shares a predetermined experience (for example, uses a predetermined content together) as a friend may be, for example, while the predetermined experience is being shared; This may be later or when it is decided to share.

That is, for example, when automatically registering a second user who is using a predetermined content together with a first user, the second user who meets a specific condition while using the content is automatically registered. It is also possible to register automatically at the specified timing. The second user who meets the specific condition may be, for example, a second user who performs an act that benefits the first user (in other words, an assisting act) during the game. Further, the second user who meets the specific condition may be, for example, a user who is disconnected from the network during the game. In addition, a user who satisfies a specific condition is, for example, a second user who participates in the same group chat as the first user and who has made a comment in the group chat, or a user who has interacted with the user in the group chat. The user may be a second user who has mutually mentioned (or one user has mentioned the other). In addition, a second user who satisfies a specific condition is a second user who has performed the actions exemplified here multiple times (for example, a second user who has performed an action that benefits the first user multiple times, or a second user who has (a second user, etc.) who has attached (or attached) multiple times. Note that satisfying a specific condition may mean satisfying a condition for a predetermined relationship to be established, or it may mean satisfying a condition other than the condition for a predetermined relationship to be established. Good too.

Furthermore, for example, when automatically registering a second user who has used predetermined content together with the first user, it is possible to automatically register a second user who has met specific conditions while using the content, or who has specific information regarding the results of using the content. The second user who satisfies the conditions may be automatically registered at the timing when the use of the content is finished. Note that the second user who satisfies a specific condition regarding the result of using the content may be, for example, a user who obtained a victory or defeat as a friend or an enemy in a game; It may also be a user who has obtained a certain score and has achieved a predetermined result. Note that the timing of automatic registration is, for example, after the game ends, while the results (in other words, grades) are being displayed (for example, when the results are being displayed on the display unit 18 of the first user's terminal device 10, etc.) ) etc. may be used.

Furthermore, for example, when automatically registering a second user who has used predetermined content together with the first user, the second user who has met certain conditions while using the content, and the second user who has met certain conditions while using the content, and certain conditions regarding the content usage results. A second user who satisfies the above conditions or a second user who satisfies a specific condition after using the content may be automatically registered at a timing when a predetermined period of time has elapsed after the use of the content ends. Specifically, for example, if there is a second user with whom a predetermined relationship is established when the level is 10 or higher, even if the second user's level was level 1 at the end of the match they played together. If the second user reaches level 10 after a period of time has passed, the second user may be automatically registered as a friend based on the fact that the second user has reached level 10. In this case, the association unit 216 stores the second user as a friend candidate in the storage unit 220 of the server 20 from the end of the match until the second user reaches level 10. It is also possible to continue monitoring whether or not the relationship has been reached (whether a predetermined relationship is established).

In addition, for example, when automatically registering a second user as a friend who is expected to use predetermined content together with the first user, for example, automatically registering the second user as a friend immediately after matching is performed. It may also be possible to register automatically when a game or event that the user participates in together starts, or it may be possible to register automatically when both the first user and the second user participate in a group chat. good.

Note that the timing of automatically registering as a friend described here may be read as the timing of applying for friend registration or following, which will be described later (in other words, the timing of displaying the consent screen, which will be described later, related to the application).

Note that the timing at which the association unit 216 identifies the second user to be automatically registered as a friend of the first user and the timing at which the second user is automatically registered as a friend of the first user may be different.

Note that if an upper limit is set for the number of users that can be associated with each user (for example, the number of friends of each user), the association unit 216 may, for example, The automatic association may be performed when the number is less than a predetermined ratio with respect to the upper limit, and the automatic association may not be performed when the number is greater than or equal to the predetermined ratio. In other words, the conditions for the association unit 216 to automatically associate other users may be relaxed or made stricter depending on the number of other users associated.

Note that although the association unit 216 has been described here as automatically registering the identified second user as a friend of the first user, the association unit 216 also allows the first user to follow the identified second user. It is also possible to automatically register as a user. In other words, the association unit 216 may automatically associate the identified second user with the first user. In other words, the association unit 216 may perform the process of associating the identified second user with the first user without any operation by the first user to instruct the association. Further, the association unit 216 may automatically apply for friend registration or follow from the first user to the identified second user. In other words, the association unit 216 may automatically apply to the identified second user for association of the second user with the first user. In other words, the association unit 216 functions as an application unit that makes an application for association of the second user with the first user to the identified second user without any operation by the first user to instruct the application. You may. Note that if an application is made to the second user to associate the second user with the first user (specifically, an application for friend registration or an application for following), for example, if the second user When a predetermined input operation is performed to approve the application on the terminal device 10, the second user is associated with the first user (in other words, the first user and the second user become friends, or (The first user follows the second user).

In addition, each user can decide whether to automatically register other users as friends or users to follow, or whether to automatically register other users as friends or request to follow them, depending on their own terminal device. It may be possible to set from 10.

In addition, in this embodiment, when various processes are "performed without any user operation", it is sufficient that the user's operation is not required when performing the relevant process. The user may perform a setting operation in advance, such as an operation to set conditions for the process in advance, or an operation to enable automatic execution of the process. Specifically, in the case of ``the application for association of the second user with the first user is made without any operation by the first user to instruct the application,'' for example, if It is sufficient that the application can be made without the need for an operation such as tapping a button for applying for registration, and a prior setting operation or the like for automatically performing the application may be performed.

Note that the service of this embodiment may not have either the function of registering other users as friends or the function of registering them as users to follow. In addition, in cases where the function has both the function of registering other users as friends and the function of registering other users as users to follow, automatic registration or application for registration will be performed for either one, but automatic registration will be performed for the other. It is also possible that registration and application for registration will not be made. In addition, it has both a function to register other users as friends and a function to register other users as users to follow, and automatic registration or application for registration is performed for both, but there are conditions for automatic registration for each. may be different.

(Cancellation of association)
Up to this point, it has been explained that the second user identified by the association unit 216 is automatically registered as a friend, automatically followed, and automatically applied for friend registration or follow. In other words, it has been described that for the second user identified by the association unit 216, the process related to association between users is automatically performed. In the following, the process related to association is automatically performed in this way, and based on the process, a second user associated with the first user (i.e., a friend of the first user or a user who is following. Hereinafter, "related user") ), the operation of canceling the association with the first user will be explained. Note that related users include not only users who are automatically associated, but also users who, for example, apply for friend registration or follow from their own terminal device 10 by the first user, and the other user makes the request from their own terminal device 10. This may include users who have become friends after consenting, users who are following you, and the like. In other words, related users include users who have been manually associated (specifically, users whose friend registration or follow request has been made based on the first user's input operation and who have been associated based on the request). May be included. Note that here, if a friend registration or follow request is made based on the first user's input operation, the second user will register as a friend of the first user or a user to follow, without requiring consent from the second user. Alternatively, the registration may be performed with the consent of the second user. Note that hereinafter, a user who is registered as a friend, followed, or applied for these automatically and associated is also referred to as an "automatically associated user."

The storage unit 220 stores conditions related to cancellation of association between users (hereinafter referred to as “cancellation conditions”). The cancellation unit 217 identifies a user who satisfies the cancellation condition among the related users associated with each user as a user whose association is to be canceled (hereinafter referred to as a "cancellation user"). Further, the cancellation unit 217 cancels the association with the specified cancellation user.

The cancellation condition may be, for example, "the content has not been used together for a predetermined period of time (in other words, the content has not been played together for a predetermined period of time)". Further, the cancellation condition may be, for example, that "the related user (or the first user) has not logged in for a predetermined period of time (in other words, has not used the service)". In addition, the cancellation condition may be, for example, ``the frequency of message transmission is low (for example, the number of messages sent from one of the first user and the related user to the other within a predetermined period (or the number of messages sent from both The total number of times) may be less than or equal to a predetermined number of times). Further, the cancellation condition may be, for example, "the rank of the related user has not changed for a predetermined period". Further, the cancellation condition may be, for example, that "the chat within the service has been vandalized by a related user." Note that whether or not a chat has been vandalized may be determined based on, for example, whether or not a preset prohibited word (in other words, a word to be monitored) has been used a predetermined number of times or more. The determination may be made based on whether or not the number of times messages have been sent to the first user is excessive compared to the number of times messages have been sent from the first user to related users.

The cancellation conditions may be set arbitrarily by each user from his or her own terminal device 10. For example, the above-mentioned cancellation conditions are displayed as selection items on the display unit 18 of the terminal device 10, and the user performs an input operation to select the cancellation condition to be applied (or the cancellation condition to be discontinued). may be set.

Further, the cancellation condition may not be arbitrarily changed by the user. In other words, at least some of the cancellation conditions may not be arbitrarily changed by the user and may be applied to all users.

Furthermore, when a plurality of conditions are set as cancellation conditions, the cancellation unit 217 may cancel the association with a related user who satisfies one of the plurality of conditions, or cancel the association with a plurality of related users (for example, all ) The association with the related user who satisfies the conditions may be canceled.

The cancellation conditions related to automatic cancellation of associated users may be applied to users who are automatically associated, and may not be applied to users who are manually associated. Here, "applied to users who are automatically associated, but not applied to users who are manually associated" means, for example, (1) In the system, for manually associated users, automatic association based on cancellation conditions In the case of a configuration in which cancellation is not performed, and (2) for manually associated users, automatic cancellation based on second cancellation conditions that are different from the cancellation conditions for automatic cancellation of automatically associated users. This includes cases where the association is canceled. Regarding the configuration (2), it is possible to automatically cancel the association based on the same cancellation conditions for both manually associated users and automatically associated users, depending on the user's selection. Also included. According to such a configuration, other users who are voluntarily associated with the user and who are manually associated with a user who is likely to wish to maintain the association are not automatically canceled ( Alternatively, automatically associated users who are less likely to wish to maintain the association than manually associated users can be automatically canceled.

The cancellation conditions may be relaxed or strict depending on the number of related users associated with the user. In other words, the cancellation unit 217 may change the cancellation condition according to the number of related users associated with the user. Specifically, the cancellation unit 217 may, for example, relax the cancellation conditions (in other words, make the cancellation easier) as the number of related users increases. Here, the statement that the cancellation conditions are relaxed as the number of related users increases means that there are at least two states, a state where the cancellation conditions are strict and a state where the cancellation conditions are relaxed when a certain predetermined number is reached. Here, the predetermined number may be a constant number. Further, the predetermined number may be set arbitrarily by the user. Further, the predetermined number may vary depending on the situation. Further, the predetermined number may be, for example, in a case where an upper limit is provided for the number of related users that can be associated with one user, a number whose ratio to the upper limit is equal to or higher than the predetermined ratio. In other words, the cancellation unit 217 may, for example, relax the cancellation conditions (in other words, make the cancellation easier) as the number of related users associated with a certain user approaches the upper limit number. Note that the upper limit may be set separately for automatically associated users and manually associated users, or for the total number of automatically associated users and manually associated users. It may be of. Note that the state where the release condition is strict may be a state where automatic release is not performed. In other words, if the number of related users associated with a certain user is above the upper limit, the cancellation unit 217 may not automatically cancel the associated users. good.

Note that relaxing the cancellation conditions may mean, for example, reducing the number of conditions necessary to automatically cancel the association with the related user. Furthermore, relaxing the cancellation conditions may mean, for example, changing parameters related to each cancellation condition. For example, when automatically disassociating related users who meet certain conditions regarding a period, such as ``not using content together for a specified period of time,'' the parameters that define the period may be changed to It may also be possible to change it as follows.

As described above, the cancellation unit 217 identifies a related user who satisfies the cancellation conditions as a cancellation user, and cancels the association with the specified cancellation user. Further, the cancellation unit 217 automatically identifies the cancellation user. In other words, when specifying the canceling user whose association with the first user is to be canceled, the canceling unit 217 specifies the canceling user without involving the first user's operation to instruct the specification.

Further, the cancellation unit 217 automatically cancels the association with the specified cancellation user. In other words, when canceling the association of the canceled user with the first user, the cancellation unit 217 cancels the association of the canceled user without involving the first user's operation to instruct the cancellation.

Note that, for example, the canceling user identified by the canceling unit 217 as a related user whose association with the first user is to be canceled may be presented to the first user before the association is canceled. Specifically, for example, when the cancellation unit 217 identifies a cancellation user, the specified cancellation user is displayed on the display unit 18 of the first user's terminal device 10 before the association is canceled. Good too. Here, the specified canceled user may be displayed in a pop-up on the display unit 18, for example, when the first user uses the service for the first time (in other words, starts an application) after the canceled user is specified. Further, the identified cancellation users may be displayed in a list on the display unit 18. This list can be said to be a list of related users whose association is scheduled to be canceled, and is created, for example, by the list creation unit 218. In addition, on the screen that presents the canceled users to the first user by pop-up display, list display, etc., a display prompting the user to select whether or not to cancel the association of the canceled users is displayed, and the cancellation unit 217 , the association of the canceled user may be canceled when the first user performs an input operation to select the cancellation (in other words, an operation to instruct cancellation of the association). In other words, when canceling the association of the specified cancellation user with the first user, the cancellation unit 217 may cancel the association of the cancellation user through an operation by the first user instructing the cancellation.

In addition, when the cancellation unit 217 identifies a cancellation user and automatically cancels the association with the first user, the display unit 18 of the first user's terminal device 10 displays the cancellation user whose association has been canceled. It may also be displayed. Here, on the display unit 18, for example, when the first user uses the service for the first time (in other words, starts an application) after the association of the canceled user is canceled, a pop-up display of the canceled user is displayed. It's okay. Further, the display unit 18 may display a list of users whose association has been canceled. This list can be said to be a list of related users whose association has been canceled, and is created, for example, by the list creation unit 218. In addition, on the screen that presents the first user with the canceled user whose association has been canceled by pop-up display, list display, etc., it is possible to select whether to restore the association with the canceled user (re-associate) or not. When the first user performs an input operation to select the restoration (in other words, an operation to instruct reassociation), the cancellation unit 217 determines that the association has been canceled. The canceled user may be associated with the first user again.

In addition, in the list of canceled users whose association is scheduled to be canceled, a deadline is set for the posting period of each canceled user on the list, and when the predetermined period has passed, the first canceled user whose association has passed has passed. At the same time as the association with the user is canceled, the display of the canceled user on the list may be terminated. In addition, in the list of canceled users whose association has been canceled, there is a time limit for the posting period of each canceled user on the list, and after the specified period has passed, the canceled users whose association has been canceled will be posted on the list. The display may end. In other words, the list creation unit 218 may delete, from the lists, canceled users who have been included in these lists for a predetermined period of time. Note that each of these posting periods may change depending on the number of related users associated with the user (for example, the ratio to the upper limit number, etc.).

Note that the list of canceled users whose association is scheduled to be canceled or the list of canceled users whose association has been canceled is created by the list creation section 218 and stored in a predetermined storage section such as the storage section 220, and is displayed on the display section 18. It may also be transmitted to the terminal device 10 when displaying the information.

Note that whether or not the cancellation user identified by the cancellation unit 217 as a related user whose association with the first user is to be canceled is presented to the first user before the association is canceled (if the The first user may be able to set from his/her own terminal device 10 whether the cancellation is to be performed from the start or without the presentation. Further, the first user may be able to set whether or not to present the canceled user whose association has been canceled to the first user from his/her own terminal device 10 .

Note that it may be possible to exclude related users who do not want the association to be automatically canceled by the cancellation unit 217 from the targets of automatic association cancellation. Specifically, for example, a list of related users associated with the first user is displayed on the display unit 18 of the first user's terminal device 10, and from among the related users included in the list, the target of cancellation is selected. The input unit 17 receives an input operation (for example, a touch operation) to select a related user to be excluded from the list, and the cancellation unit 217 stores the selected user in the storage unit as a user to be excluded from the cancellation target based on the input operation. 220. The cancellation unit 217 automatically identifies the related user excluded from the cancellation target or automatically cancels the association even if the related user is a related user that satisfies the cancellation conditions. do not have. In other words, the related user management unit 215 may register the related user specified by the first user among the related users associated with the first user as a special related user to be excluded from the target of cancellation. In this case, compared to related users who are not specially related users (in other words, related users who have not been designated by the first user), the special related user is subject to restrictions regarding the cancellation of the association (for example, the ability to automatically release users (e.g., identification or cancellation is not carried out).

(List of related users)
From the terminal device 10 of each user, it is possible to view a list of related users associated with the user (hereinafter referred to as "related user list"). The display control unit 114 of each user's terminal device 10 causes the display unit 18 to display a related user list of related users associated with the user. FIG. 3 shows an example of a related user list display screen 50 on which a related user list is displayed.

For each related user, the related user list display screen 50 shown in FIG. A background information input button 52 that is operated when inputting data, and various buttons for making settings related to association are displayed. By looking at the related user list display screen 50 (specifically, the history information 51), each user can check the history of how each related user is associated with him/herself.

The history information 51 is input as follows, for example. First, when inputting history information 51 for a specific related user, the first user performs an input operation of selecting the history information input button 52. When the input operation is performed, the display control unit 114 displays the history information input screen 60 on the display unit 18. An example of the history information input screen 60 is shown in FIG.

On the history information input screen 60, for example, a plurality of tags 61 related to the history of association are displayed. The history information management unit 219 selects the tag 61 selected by the first user's input operation from among the plurality of tags 61 displayed on the history information input screen 60 as the history information 51 of the specific related user. It is stored in the storage unit 220 along with the related user. Note that it may be possible to attach a plurality of tags 61 to one related user.

Here, the tag 61 is, for example, something related to an event in an experience shared by the first user and the specific related user (for example, a game played together that led to the association between the two) (for example, the first user or related to the behavior of the specific related user, or the performance of the first user or the specific related user), or related to the relationship between the first user and the specific related user. There may be. Further, the tag 61 may be related to, for example, an event that caused the related users to be automatically associated. Specifically, the tags 61 are, for example, "healed me," "healed me," "gave me an assist attack," "gave me an assist attack," and "gave me an item." (For example, including when someone used a consumable item for me)," "I gave them an item," "I was good at it (in other words, I got a good grade)," "I wasn't good at it (in other words, I got a bad grade)." , "we fought together," "we fought against each other," "we won," "we lost," "we participated in a specific live together," or "we had several back-and-forth conversations in chat." Good too.

Note that on the background information input screen 60, assistance may be provided regarding the selection of tags 61 related to events that actually occurred in the experience shared by the first user and the specific related user. Specifically, for example, on the background information input screen 60, tags 61 related to events that actually occurred may be preferentially displayed. Here, preferentially may mean, for example, that only tags 61 related to events that actually occurred are displayed, and tags 61 related to events that actually occurred have a higher display priority (for example, , tags 61 related to events that actually occurred are displayed at the top, etc.). For example, when the display of the history information input screen 60 is started, the tag 61 related to the event that actually occurred is displayed in a selected state (for example, a check mark is attached in the example shown in FIG. 4). May be started.

Note that the background information input screen 60 displays, for example, the timing when the second user is automatically associated with the first user (the timing when the second user is automatically registered as a friend, the timing when the user is automatically followed, or the timing when the second user is automatically associated with the first user). The message may be displayed on the display unit 18 of the terminal device 10 of the first user (and the second user) at the timing when the second user accepts the friend registration or follow request of the user. Further, the background information input screen 60 is displayed when the first user (and the second user ) may be displayed on the display unit 18 of the terminal device 10. In other words, when automatically associating the second user with the first user, the history information management unit 219 provides the terminal device 10 with information for displaying the history information input screen 60 as a display prompting the input of the history information 51. The display control unit 114 may display the history information input screen 60 on the display unit 18 based on the information. Further, in this way, when the background information input screen 60 is displayed at a predetermined timing to prompt input of the background information 51, and the second user is automatically associated with the first user. On the other hand, when the second user is manually associated with the first user, a display prompting the first user (and the second user) to input the history information 51 is displayed on the terminal device 10 of the first user (and the second user). A display prompting the input of the history information 51 is not displayed on the terminal device 10 of the first user (and the second user) (in other words, the history information management unit 219 does not display information for displaying the history information input screen 60 on the terminal device 10). It may also be possible to do so (not send).

Note that tagging the second user may be possible while sharing the experience (for example, during a game being played together that causes the two to be associated). Specifically, when a first user and a second user are playing a game together and the second user revives the first user's character, the first user With the device 10, it is possible to perform an input operation to attach a tag 61 that says "resuscitated" to the second user (for example, the tag 61 is displayed on the display section 18, and an input operation to select it is performed). operation is possible), and the association unit 216 attaches the tag 61 to the second user as history information 51 of the second user and stores it in the storage unit 220 based on the input operation. Good too. Note that in this case, the tag 61 may be attached to the second user while the experience is being shared and before it is decided to associate the second user with the first user. Further, the association unit 216 may associate the second user with the first user based on the addition of the tag 61 (in other words, register as a friend, follow, or apply for these).

Note that here, on the background information input screen 60, the background information 51 is input based on the selection of the tag 61, but the background information 51 is inputted by text input on the background information input screen 60. It may be .

Furthermore, the history information 51 may be automatically input without any user operation, for example. For example, the event that caused the automatic association of related users may be automatically input as the history information 51. Specifically, for example, based on the fact that the second user performed an act of recovering (specifically, reviving) the first user's character three times in a certain match X during the game, When automatically registering the second user as a related user of the first user, the history information management unit 219 automatically provides the second user with history information 51 ( In other words, the information may be attached without any operation by the first user, and may be stored in the storage unit 220 as information regarding the related user. In other words, for example, an event during a play (such as a match) that triggered the automatic association of the second user, or the relationship between the first user and the second user, etc., is automatically input as the background information 51. It may be as follows. Further, the history information 51 automatically stored in the storage unit 220 may be editable based on the user's input operation on the terminal device 10. In this case, for example, the history information management unit 219 edits the history information 51 based on the input operation.

Further, when displaying the background information input screen 60 at a predetermined timing, the background information 51 is displayed in a state that has been automatically input, and in the background information input screen 60, the background information 51 that has been automatically input by the user is displayed. An input operation for editing may be accepted. The input operation may be, for example, a text input operation for editing the automatically input history information 51, and an automatically attached tag 61 (for example, a check mark is automatically attached in the example shown in FIG. 4). This may be an input operation such as deleting a tag 61 or adding another tag 61.

Various buttons displayed on the related user list display screen 50 for making settings related to association include, for example, a cancel button 53 that is operated when canceling the association of related users, and a cancel button 53 that is operated when registering related users as favorites. A favorites button 54 to be operated, a condition edit button 55 to be operated when editing the registration conditions of related users, a condition cancel button 56 to be operated to cancel the settings of the conditions, and registration conditions based on the history information 51. A condition setting object 57 that is operated when setting is included.

When an input operation is performed on the release button 53, the release unit 217 releases the association with the target related user. That is, the user can manually cancel the association with the related user by operating the release button 53. Note that when the release button 53 is operated, the display control unit 114 may cause the display unit 18 to display a confirmation screen or the like for confirming whether the association is really to be released.

When an input operation is performed on the favorites button 54, the related user management unit 215 registers the target related user (in other words, the related user associated with the operated favorites button 54) as a favorite. For related users registered as favorites, for example, even if the related user satisfies the cancellation conditions, the related users are not automatically identified as cancellation users or the association is not automatically canceled. Regarding related users registered as favorites, for example, when canceling the association based on an operation on the cancel button 53, the number of steps required for cancellation (for example, It may also be possible to increase the number of confirmations (such as the number of confirmations to confirm whether it is OK to cancel). In other words, the related user management unit 215 registers the related user designated by the first user as a special related user (in other words, a favorite) among the related users associated with the first user. Here, the special related user may be subject to restrictions on the cancellation of the association (for example, automatically (For example, the first user is not identified or canceled as a canceled user, or the first user has to perform a large number of steps when canceling, etc.).

Note that registration as a related user's favorites does not have to be based on an operation on the favorites button 54. For example, the related user management unit 215 may automatically register as a favorite a related user whose history information 51 has been input through an input operation by the user (for example, input by text input or input by selecting the tag 61, etc.). good.

When an input operation is performed on the condition editing button 55, the display control section 114 causes the display section 18 to display an editing screen (not shown) for editing the registered conditions. When the registration conditions are edited (in other words, set) on the editing screen, the association unit 216 automatically associates users who satisfy the edited registration conditions. In other words, in this embodiment, by editing the registration conditions on the editing screen, it is possible to change the conditions of the users to be automatically associated. In other words, in this embodiment, the registration conditions of related users can be edited based on an input operation on the condition editing button 55.

On the editing screen, for example, it may be possible to set detailed conditions of the registration conditions corresponding to the history information 51 of the target related user. Specifically, the condition edit button 55 related to the related user to which the background information 51 "He revived me three times in match X", that is, the background information 51 "He revived me" is operated. In this case, on the editing screen, the user who resuscitated the user will be automatically added as a related user, if the user who resuscitated the person has been resuscitated "how many times" as a detailed condition for the registration condition of "resuscitated". It is possible to set whether to register with . In other words, the edit screen may accept input operations related to setting the detailed conditions.

Furthermore, on the editing screen, for example, it may be possible to set registration conditions that are unrelated to the background information 51 of the relevant user. Specifically, when the condition edit button 55 related to a related user to which the background information 51 of "resuscitated" is operated, the registration of "resuscitated" is displayed on the editing screen. Instead of or in addition to the conditions, it may be possible to set a registration condition such as ``they gave me an item'' or a registration condition such as ``we fought together.''

Furthermore, in this embodiment, when an input operation is performed on the condition setting object 57, the association unit 216 generates a condition (conditions) that other users should satisfy in order to automatically associate in the future based on the history information 51 of the related user of interest. In other words, the registration conditions) are set. Specifically, on the related user list display screen 50, registration conditions extracted based on the history information 51 of each related user are displayed as a condition setting object 57. More specifically, for example, if the related user is attached with the background information 51 that says "he revived me three times in match X", the registration condition extracted based on the background information 51 is as follows: A condition setting object 57 related to the registration condition "resuscitated" is displayed on the related user list display screen 50. Then, when the user performs an input operation on the condition setting object 57, the association unit 216 automatically associates the registration condition of "resuscitated" with other users who have been resuscitated in the future. Set (in other words, enable). That is, in this embodiment, the registration conditions related to the history information 51 are displayed on the related user list display screen 50 as candidates for registration conditions to be set (in other words, to be enabled), and the setting of the registration conditions is suggested to the user. It is now possible to do so. Note that the display of the condition setting object 57 can be realized, for example, as follows. That is, a table showing the correspondence between keywords that can be included in the history information 51 (for example, "resuscitation" in the above example) and registration conditions is stored in the storage unit 220, If a keyword is included, the related user management unit 215 extracts the registration condition corresponding to the specific keyword, and also provides information for displaying the condition setting object 57 related to the extracted registration condition on the display unit 18. It may also be transmitted to the terminal device 10.

The condition release button 56 is a button operated when canceling (in other words, invalidating) the setting of the registration condition displayed as the condition setting object 57. When an input operation is performed on the condition cancellation button 56, the association unit 216 excludes the registration condition related to the condition setting object 57 of the target related user from the conditions that other users should satisfy in order to automatically associate the related user in the future. In other words, when an input operation is performed on the condition cancellation button 56, the association unit 216 determines the registration conditions extracted based on the background information 51 of the relevant user, which other users should satisfy in order to automatically associate them in the future. Exclude from conditions. Note that when an input operation is performed on the condition cancellation button 56, the association unit 216 determines whether the registration conditions that the relevant user has met when automatically associating the relevant user are to be met by other users in order to automatically associate the relevant user in the future. It is also possible to exclude it from the necessary conditions. Note that when an input operation is performed on the condition cancellation button 56 and the registration condition settings are canceled, the condition cancellation button 56 changes to a condition setting button (not shown), and when an input operation is performed on the condition setting button, the condition setting button 56 changes to a condition setting button (not shown). , a registration condition that has been canceled (in other words, invalidated) based on an input operation on the condition cancellation button 56 may be set (in other words, validated) again. In other words, the condition setting object 57 may be an object that simply displays predetermined registration conditions, rather than an object that accepts an operation for setting (in other words, validating) registration conditions.

Note that the information necessary for displaying the related user list, such as the history information 51, is stored in the storage unit 220 of the server 20, for example, and when displaying the related user list (for example, a predetermined information for the operation reception unit 111). (based on a request from the terminal device 10 to the server 20 based on an input operation), the related user management section 215 sends the request to the terminal device 10. Note that information necessary for displaying the related user list may be stored in the storage unit 120.

(classification list)
The list creation unit 218 creates a plurality of lists (hereinafter referred to as "classified lists") in which a plurality of related users associated with the user are classified according to the attributes of the related users. Further, the display control unit 114 of each user's terminal device 10 causes the display unit 18 to display a classification list of related users associated with the user. FIG. 5 shows an example of a classification list display screen 70 on which a classification list is displayed.

For example, the list creation unit 218 may create a plurality of classification lists in which related users associated with the first user are classified according to their compatibility with the first user. Note that one related user may be assigned to multiple classification lists. Furthermore, one related user may not be assigned to multiple classification lists (in other words, not be included in multiple classification lists). Furthermore, each related user is always assigned to one of the classification lists, and there may be no related users who are not assigned to any of the classification lists. Further, there may be a related user who is not assigned to any classification list.

Specifically, for example, assuming a predetermined game (specifically, a role-playing game, FPS, etc.), the list creation unit 218 may classify related users according to their compatibility with the first user. As a list, there is a classification list that summarizes related users who have the attribute "good at recovery" (see Figure 5 (a)), and a classification list that summarizes related users who have the attribute "good at attack" (see Figure 5 (b)). )) may be created. Here, whether you are good at recovery or attack may be determined based on the attributes (e.g., occupation) of the character used by each related user, or based on the items owned by each related user. You may. For example, related users whose characters use occupations are "recovery magician", "medic", etc. may be included in the classification list of related users who are good at recovery. Further, for example, related users whose characters are used as occupations such as "attack magician" or "swordsman" may be included in the classification list of related users who are good at attacks. Here, the character used may be, for example, the character that the user uses most frequently (in other words, the most), and may be the character that is used as the main character in a game where each user can select the main character. It may be a character that is set as a character to be used, or it may be a character that is registered as a favorite in a game where each user can register frequently used characters as favorites, and the character may be a character that has been used a predetermined number of times. It may be a character that has won more than a predetermined number of times using that character, or a character that has won more than a predetermined number of times using that character. Further, for example, related users who own a predetermined number or more of recovery items may be included in the classification list of related users who are good at recovery. In addition, for example, a related user who owns a weapon with higher attack performance than weapons owned by other users (in other words, other weapons existing in the game), such as the strongest gun in the game, may be assigned a weapon that is good at attacking. It may also be included in a classified list of related users.

In other words, the list creation unit 218 may create a classification list in which related users are classified according to their compatibility with the first user, and a classification list in which related users are classified according to the attributes of the characters used by the related users. good. The list creation unit 218 may, for example, create a classification list in which characters are classified according to their occupation or the like as described above, or may create a classification list in which characters are classified according to their rank or the like. Further, the list creation unit 218 may create, for example, a classification list of related users who use characters that do not overlap with the character used by the user. Such a classification list, etc. classified according to the attributes of characters, can be used to identify related users with whom the first user can easily play (for example, related users who have characters with attributes that are easy for the first user to play with, This makes it easier for the first user to search for related users in rank ranges with whom it is easy to play together, and related users with whom it is difficult to play together, and can be said to be a classification list classified according to compatibility with the first user.

In addition, the list creation unit 218 creates a classification list in which related users are classified according to their compatibility with the first user, based on the past play history between the first user and each related user. You may also create a classification list based on compatibility. Specifically, for example, when assuming a predetermined game (specifically, a game that aims to achieve a predetermined purpose (e.g., a competitive game), etc.), the list creation unit 218 may The number of times or the probability of achieving a predetermined objective by playing together with the user (here, together can mean playing as friends or playing as an enemy) (in other words, A classification list may be created in which related users are classified according to their winning percentage in competitive games, etc.). Furthermore, the list creation unit 218 classifies the related users according to, for example, the number of times one of the first user and the related user has given a highly rated reaction to the other (for example, the number of so-called "likes"). You may also create a classified list. Furthermore, the list creation unit 218 may create a classification list in which the related users are classified according to the number of times one of the first user and the related user has performed an act beneficial to the other, for example.

For example, the list creation unit 218 may create a classification list in which related users are classified according to their compatibility with the first user, or a classification list in which related users are classified according to their compatibility with each stage. Specifically, for example, when a plurality of stages (in other words, maps) including a first stage and a second stage are prepared in an FPS, the list creation unit 218 selects a relationship that is compatible with the first stage. A classification list of users and a classification list of related users who are compatible with the second stage may be created. Here, the compatibility of each related user with each stage can be determined by, for example, the winning rate of each related user in past battles at each stage (for example, if the winning rate is 70% or more, the compatibility is good, etc.), the number of wins ( For example, if the total number of wins has reached 100, the match is good, etc.) Or whether the player had a good performance in the previous match (For example, if the match was won, the match is good, etc.) ) may be used as a basis for judgment.

Furthermore, the list creation unit 218 may create a plurality of classification lists in which related users associated with the first user are classified according to the frequency with which they play together, for example. Specifically, the list creation unit 218 may create a plurality of classification lists in which related users are classified according to the number of times they have played together within a predetermined period, for example.

Further, the list creation unit 218 may create a plurality of classification lists in which related users associated with the first user are classified according to the history information 51 attached to the related users, for example. Specifically, the list creation unit 218 may create a plurality of classification lists in which related users are classified by tags 61 attached to the related users, for example.

Furthermore, the list creation unit 218 may create a plurality of classification lists in which related users associated with the first user are classified according to attributes based on the actions of the related users within the service, for example. Specifically, the list creation unit 218, for example, selects related users associated with the first user according to attributes based on actions of the related users in content (for example, a game) used together with the first user. A plurality of classified lists may be created. Note that attributes based on actions include attributes related to the results of actions. Specifically, the list creation unit 218, for example, associates the related users with actions performed by the related users (for example, healed the first user, gave an assist attack, gave an item, enemy character). the number of times a specific action was performed, the number of times a specific result (e.g., winning a match) was obtained (in other words, achieved) as a result of the action, the type of result obtained, Alternatively, a plurality of classification lists may be created that are classified according to the probability of obtaining a specific result (for example, winning rate, etc.). In addition, the list creation unit 218 classifies related users associated with the first user into a plurality of categories according to attributes based on actions of the related user within the service that are beneficial to the first user. You can also create a list. Specifically, the list creation unit 218 stores related users, for example, the type of action that the related user performed that benefits the first user, the number of times a specific action that benefits the first user is performed, and the result of the action that benefits the first user. A plurality of classification lists may be created that are classified according to the number of times a specific result has been obtained, the type of result obtained by a beneficial action, etc.

The plurality of classification lists created by the list creation section 218 are stored in the storage section 220 of the server 20, which serves as a classification list storage section. Further, each classification list stored in the storage unit 220 can be presented to the first user at a predetermined timing (can be displayed on the first user's terminal device 10 at a predetermined timing).

Note that each user may be able to set the conditions for related users to be included in each classification list from his or her own terminal device 10. In other words, each user may be able to set from his or her own terminal device 10 how to classify related users and what kind of classification list to create.

Further, as described above, the association unit 216 automatically associates other users who share a predetermined experience with the first user with the first user, but the list creation unit 218 Users may be automatically sorted into classification lists according to the attributes of the related users. Furthermore, each user may be able to manually select from his/her own terminal device 10 which classification list to which such automatically associated associated users are to be sorted.

Further, the association unit 216 automatically associates with the first user another user who shares a predetermined experience with the first user and who has a predetermined relationship with the first user within the service. , here, the predetermined relationship may be "a relationship that corresponds to any classification list." That is, for example, if a classification list of related users that is compatible with the first stage in an FPS is prepared as the classification list of the first user, the first user among the users who participated in the same match as the first user Users who are compatible with the stage may be automatically registered as friends of the first user. In other words, when a plurality of friend classifications are stored in the storage unit 220, the association unit 216 may automatically associate users who fall under any of the plurality of classifications.

Note that although the list creation unit 218 creates a plurality of classification lists and stores them in the storage unit 220, the plurality of classification lists need not be those in which a plurality of related users are classified according to the attributes of the related users. good. For example, the list creation unit 218 may create a classification list in which a plurality of related users associated with the first user are simply classified into a plurality of lists. Further, the first user may be able to select which related users to include in each classification list using his/her own terminal device 10. In other words, the list creation unit 218 may determine related users to be included in each classification list based on the user's operation. In other words, the storage unit 220 may be able to store a plurality of classification lists created based on user operations.

The classification list may be displayed on the display unit 18, for example, as follows. That is, for example, as shown in FIG. 5, on the classification list display screen 70 that displays the classification list displayed on the display unit 18, there is an object that accepts an operation for selecting a classification list to be displayed from among a plurality of classification lists. (For example, tab 71) may be displayed. Then, the display control unit 114 may cause the display unit 18 to display the classification list selected by the user's input operation for the object. Note that the classification list information necessary for displaying the classification list may be sent from the server 20 to the terminal device 10 based on a request from the terminal device 10, for example, when the classification list display screen 70 starts displaying. Often, a request may be made from the terminal device 10 to the server 20 based on a user's input operation to select a classification list to be displayed, and the request may be sent from the server 20 to the terminal device 10. Note that the plurality of classification lists may be stored in the storage unit 120 of the terminal device 10, and the display control unit 114 may cause the display unit 18 to display the classification list stored in the storage unit 120. Further, the control unit 110 of the terminal device 10 may include the list creation unit 218.

As described above, in this embodiment, the list creation unit 218 stores a plurality of classification lists in the storage unit, and each classification list among the plurality of classification lists stored in the storage unit is stored in the terminal device. It is displayed as 10. In other words, the configuration according to the present embodiment may only display the results of narrowing down a plurality of related users associated with a user based on predetermined search conditions input by the user, or may display only the results of narrowing down a plurality of related users associated with the user based on predetermined search conditions input by the user. , unlike those that simply display the results sorted based on predetermined conditions entered by the user, multiple classification lists are created in advance before the list of related users is displayed. The configuration is memorized.

Further, when displaying the classification list on the display unit 18, the display control unit 114 may preferentially display a classification list suitable for a predetermined situation within the service determined based on the user's selection. Note that preferentially may mean that only classification lists suitable for a predetermined situation are displayed, and a classification list suitable for a predetermined situation that has a higher display priority (for example, a predetermined In some cases, a classification list suitable for a situation is displayed first, and other classification lists are displayed based on an input operation that changes the classification list to be displayed (for example, selecting a tab as described above). (for example, the classified list may be displayed larger than other classified lists). Here, as a specific example, as shown in FIG. 6(a), in an FPS, a stage selection screen 75 on which various stages (in other words, a map) such as a first stage and a second stage can be selected is displayed on the display section 18. The following is an example of the case where this is displayed. Note that the stage selection screen 75 may be a screen where, for example, by selecting a stage, a battle on that stage is started, and by selecting a stage, information about that stage can be confirmed. It may be a screen that allows you to do so. When an input operation is performed to select the first stage on the stage selection screen 75, the display control unit 114 displays a classified list of related users who are compatible with the first stage, as shown in FIG. 6(b). A classification list display screen 70 is displayed on the display unit 18. On the other hand, when an input operation is performed to select the second stage on the stage selection screen 75, the display control unit 114 displays the classification list display screen 70 on which a classification list of related users who are compatible with the second stage is displayed. It is displayed on the display section 18. That is, the display control unit 114 displays on the display a classified list of related users having attributes suitable for a predetermined situation (in other words, the stage the user is trying to play) determined based on the user's selection from among the plurality of classified lists. 18. Note that, as described above, the stage selection screen 75 may be a screen where, by selecting a stage, a battle in that stage is started. For example, when an input operation is performed to select a stage on the stage selection screen 75 and an operation is performed to select one or more related users from the displayed classification list, the terminal device 10 of the selected user An invitation to participate in the play is sent to the terminal device 10 of the selected related user via the server 20, and when the related user performs an operation to accept the invitation, both parties can participate in the stage. The play may be started as follows.

Note that the situation determined based on the user's selection may be, for example, an event in which the user attempts to participate. For example, when a user performs an input operation to select a live event to participate in, the display control unit 114 displays a classified list of related users having attributes suitable for participating in the live event together (e.g., A classified list of related users who are determined to be likely to be interested in the live performance based on the event history may be displayed preferentially.

Note that the situation determined based on the user's selection may be related to the user's attributes, for example. Specifically, for example, when a user selects a character that is good at recovery as a character to use in a role-playing game, and the user performs a predetermined input operation to display a list of related users. In addition, the display control unit 114 displays a classification list of related users who use characters that are good at attacking (in other words, a classification list of related users who use characters that are good at attacking) as a classification list of related users who have attributes suitable for the situation of playing with a character that is good at recovery. A classified list of related users having attributes that complement the attributes may be displayed preferentially.

Note that here, the list creation unit 218 creates a plurality of classification lists in advance and stores them in the storage unit, and when displaying the classification list on the display unit 18, the display control unit 114 selects the plurality of classification lists. The explanation has been made assuming that a classification list selected from the list is displayed. However, the list creation section 218 may create a classification list when displaying it on the display section 18. Specifically, for example, when an input operation is performed to select the first stage on the stage selection screen 75 shown in FIG. 6(a), the list creation unit 218 selects related users who are compatible with the first stage. A classification list (in other words, a list of related users having attributes suitable for the situation determined based on the user's selection) may be created, and the display control unit 114 may cause the display unit 18 to display the classification list.

Next, the flow of processing executed by the system 1 will be described with reference to FIGS. 7 to 11. Note that here, an example will be described in which the system 1 according to the present embodiment is applied to a game (specifically, an FPS).

(Processing related to association)
A process of automatically associating a second user with a first user as a predetermined user who uses the system 1 will be described with reference to FIG.

First, the association unit 216 of the server 20 identifies a user who shares an experience with the first user (step S101). Specifically, the association unit 216 identifies, for example, a user who is participating in the same match as the first user.

Next, the association unit 216 determines whether there is a user who satisfies the registration conditions for automatically associating with the first user among the users participating in the same match as the first user (step S102). Here, it is assumed that the registration conditions are input in advance by the first user from his own terminal device 10 and are stored in the storage section 220 of the server 20 as the registration condition storage section. Further, here, it is assumed that the registration condition input and set by the first user is "the player was revived three or more times during one match."

If there is no user who satisfies the registration condition among the users participating in the same match as the first user (NO in step S102), the association unit 216 automatically associates another user with the first user. No processing is performed. Specifically, if there is no second user who has revived the first user three or more times before the end of one match, the association unit 216 may The process of automatically associating users is not performed.

On the other hand, if there is a user who satisfies the registration condition among the users participating in the same match as the first user (YES in step S102), the association unit 216 associates the first user with another user. Automatically performs predetermined processing. Specifically, if there is a second user who has revived the first user three or more times until the end of one match (YES in step S102), the association unit 216 The first user applies for friend registration to the two users (step S103). At this time, the association unit 216 automatically makes the application without requiring any input operation by the first user. Specifically, the association unit 216 transmits data related to the friend registration application to the second user's terminal device 10 (step S103). When the transmitter/receiver 112 of the second user's terminal device 10 receives the data, the display controller 114 of the second user's terminal device 10 displays a screen (hereinafter referred to as " A "consent screen") is displayed on the display unit 18 (step S104). On the consent screen, a message is displayed asking the second user whether or not to accept the friend registration application from the first user. In other words, while the consent screen is displayed, the operation reception unit 111 of the second user's terminal device 10 performs operations for accepting and rejecting the friend registration application as operations related to responses to the friend registration application. accept.

When the second user's terminal device 10 accepts an operation to accept or reject an application for friend registration, data indicating whether or not to accept the application for friend registration (in other words, a response to the application for friend registration) is sent from the transmission/reception unit 112 of the terminal device 10 to the association unit 216 (step S105).

Upon receiving the data sent from the second user's terminal device 10 indicating whether or not to approve the friend registration application, the association unit 216 determines whether or not the friend registration application is approved based on the data. Determination is made (step S106). That is, when the second user performs an operation to approve the friend registration application, it is determined that the friend registration application is approved (YES in step S106). On the other hand, if the second user performs an operation to reject the friend registration application, it is determined that the friend registration application is rejected (NO in step S106). If it is determined that the friend registration application is rejected (NO in step S106), the association unit 216 does not associate the second user with the first user.

If it is determined that the friend registration application has been approved (YES in step S106), the association unit 216 associates the first user and the second user with each other (step S107). In other words, if it is determined that the friend registration application has been approved, the association unit 216 registers the second user as the first user's friend. In other words, if it is determined that the friend registration application has been approved, the association unit 216 causes the storage unit 220 to store information indicating that the second user is a friend of the first user.

Further, when the first user and the second user are associated with each other, the association unit 216 transmits data indicating that the second user is registered as a friend of the first user to the terminal device 10 of the first user. (Step S108). In other words, the server 20 notifies the first user's terminal device 10 that the second user has been registered as a friend of the first user. When the transmitter/receiver 112 of the first user's terminal device 10 receives the data, the display controller 114 of the first user's terminal device 10 informs the first user that the second user has been registered as a friend of the first user. A registration notification screen for notification is displayed on the display unit 18 (step S109).

In addition, in the second user's terminal device 10, when there is an application for friend registration from another user, it is set in advance whether or not to receive the application (in other words, whether or not to display the consent screen). It may also be possible to keep it. Further, when the setting is made to reject the reception of the application, the association unit 216 may determine that the application for friend registration is rejected (NO in step S106). Furthermore, for example, on the second user's terminal device 10, it is possible to set a white list that defines the conditions of users who want to be friends, or a black list that defines conditions of users who do not want to be friends. Good too. Then, applications may be received from users who meet the conditions set in the whitelist. Further, applications from users who meet the conditions set in the blacklist may be refused.

Note that although the association unit 216 has been described here as applying for friend registration when the registration conditions are met, it may also apply for follow instead of applying for friend. Furthermore, for example, if the registration conditions are met, friend registration or follow-up may be performed automatically without applying. In other words, for example, if YES in step S102, the process in step S107 may be performed without going through the processes in steps S103 to S106.

(Processing related to cancellation of association)
Next, a process for automatically canceling the association of related users associated with the first user with the first user will be described with reference to FIG. 8.

First, the cancellation unit 217 of the server 20 determines whether there is any related user who satisfies the cancellation condition among the related users associated with the first user (step S201). Here, it is assumed that the cancellation condition is input in advance by the first user from his own terminal device 10 and is stored in the storage section 220 of the server 20 as the cancellation condition storage section.

If there is a related user who satisfies the cancellation conditions (YES in step S201), the cancellation unit 217 specifies the related user as a cancellation user, and transmits data informing the specified cancellation user to the first user's terminal device 10 ( Step S202). When the transmitting/receiving unit 112 of the first user's terminal device 10 receives the data, the display control unit 114 of the first user's terminal device 10 sends a cancellation confirmation prompting an answer as to whether or not to cancel the association with the canceled user. The screen is displayed on the display unit 18 (step S203). While the cancellation confirmation screen is being displayed, the operation reception unit 111 of the first user's terminal device 10 receives an operation to approve and an operation to reject the cancellation of the association with the cancellation user.

When the first user's terminal device 10 accepts an operation to approve or refuse the cancellation of the association with the cancellation user, data indicating whether or not to approve the cancellation of the association with the cancellation user (in other words, A reply regarding the cancellation of the association with the user) is sent from the transmitting/receiving unit 112 of the terminal device 10 to the canceling unit 217 (step S204).

When the cancellation unit 217 receives data sent from the first user's terminal device 10 indicating whether or not to approve the cancellation of the association with the cancellation user, the cancellation unit 217 cancels the association with the cancellation user based on the data. It is determined whether the request has been accepted (step S205). That is, when the first user performs an operation to approve the cancellation, it is determined that the cancellation of the association with the canceled user has been approved (YES in step S205). On the other hand, if the first user performs an operation to refuse the cancellation, it is determined that the cancellation of the association with the cancellation user is rejected (NO in step S205). If it is determined that the cancellation is rejected (NO in step S205), the cancellation unit 217 does not cancel the association of the cancellation user with the first user.

If it is determined that the cancellation of the association with the canceled user has been approved (YES in step S205), the cancellation unit 217 cancels the association of the canceled user with the first user (step S206).

(Processing related to input of background information)
Next, a process of inputting history information 51 regarding the second user as a related user associated with the first user will be described with reference to FIG. 9.

First, the history information management unit 219 determines the tag 61 to be displayed on the history information input screen 60 (step S301). Here, the history information management unit 219 stores the match that caused the second user to be associated with the first user (in other words, the registration condition for the second user to be set by the first user (here, the registration condition is "1 match"). The tag 61 to be displayed on the history information input screen 60 is determined based on the events in the match) that satisfied the following criteria: "He was revived three or more times during the match." Specifically, for example, based on the fact that the second user's character revived the first user's character in this match, the history information management unit 219 sets the tag 61 "Resuscitated". is determined as the tag 61 to be displayed. For example, in this match, if the second user's character attacks the opponent that the first user's character is attacking, a tag that displays the tag 61 that says "assist attack" Decided to be 61. Further, for example, if the first user and the second user fight together and win in this match, the tag 61 is determined to display the tag 61 that says "we fought together" and the tag 61 that says "we won." Regarding the process of step S301, a table showing the correspondence between events that may occur in a match and tags 61 to be displayed is stored in the storage unit 220, and the history information management unit 219 uses the table to , a tag 61 corresponding to an event that actually occurred in the match may be extracted and determined as the tag 61 to be displayed on the background information input screen 60.

Next, the history information management unit 219 transmits information necessary for displaying the history information input screen 60, including information about the tag 61 to be displayed, to the first user's terminal device 10 (step S302).

When the transmitter/receiver 112 of the first user's terminal device 10 receives the information, the display controller 114 of the first user's terminal device 10 displays the history information input screen 60 (step S303). The history information input screen 60 displays the tag 61 that was determined to be displayed in step S301.

Next, the operation receiving unit 111 of the first user's terminal device 10 receives an input operation for selecting a tag 61 to be attached as the history information 51 about the second user from among the tags 61 displayed on the history information input screen 60 ( Step S304). In other words, while the history information input screen 60 is displayed, an input operation for inputting the history information 51 is accepted.

When an input operation for selecting a tag 61 is accepted in the first user's terminal device 10, data indicating the selected tag 61 (in other words, data related to input history information) is transmitted from the transmitting/receiving unit 112 of the terminal device 10. The information is sent to the user management section 215 (step S305).

When the history information management unit 219 receives the data indicating the selected tag 61, it stores the selected tag 61 in the storage unit 220 by attaching it to the second user as the history information 51 of the second user (step S306 ). In other words, the history information management unit 219 registers the second user's history information 51 based on the input operation on the terminal device 10.

Note that here, the number of tags 61 selected may be one or more than one.

(Processing related to display of classification list)
Next, processing related to creating and displaying a classification list in which a plurality of related users associated with the first user are classified according to the attributes of the related users will be described with reference to FIG. 10.

First, the list creation unit 218 classifies a plurality of related users associated with the first user by attribute of the related users, and creates a classification list (step S401). Specifically, the list creation unit 218 classifies the relevant users by referring to the user information 223 of each relevant user, and creates a classification list. For example, the list creation unit 218 classifies related users whose characters are good at attacks as related users who are good at attacks, and creates a classification list of related users who are good at attacks. In addition, the list creation unit 218 classifies related users whose characters are good at recovery, for example, as related users who are good at recovery, and creates a classification list of related users who are good at recovery.

Further, the list creation unit 218 stores the created plurality of classification lists in the storage unit 220 as a classification list storage unit (step S402).

In displaying the classification list, the first user's terminal device 10 first requests the server 20 to transmit the classification list (step S403). Further, the related user management unit 215 transmits the classification list to the first user's terminal device 10 based on the request (step S404). Here, it is assumed that a classification list of related users who are good at attacks and a classification list of related users who are good at recovery are transmitted.

Next, the display control unit 114 of the first user's terminal device 10 selects the classification list to be displayed (for example, which of the classification list of related users who are good at attacks and the classification list of related users who are good at recovery) is selected. A screen (for example, the classification list display screen 70 shown in FIG. 5) is displayed on the display unit 18 (step S405). Further, while the screen is being displayed, the operation accepting unit 111 accepts an input operation for selecting a classification list to be displayed.

When an input operation is performed to select a classification list to be displayed, the display control unit 114 displays the selected classification list on the display unit 18 (step S406).

Note that the list creation unit 218 may be included in the terminal device 10. Further, the terminal device 10 may include a classification list storage unit (for example, the storage unit 120) that stores the classification list. In this case, the display control unit 114 may cause the display unit 18 to display the classification list selected by the user (steps S405 and S406) from among the plurality of classification lists stored in the terminal device 10.

(Variation example of processing related to display of classification list)
Next, a modification of the process for creating and displaying a classification list in which a plurality of related users associated with the first user are classified according to the attributes of the related users will be described with reference to FIG. 11.

First, the display control unit 114 of the first user's terminal device 10 causes the display unit 18 to display a screen that prompts selection of a situation (for example, a game situation that the first user is trying to play) (step S501). Further, while the screen is being displayed, the operation accepting unit 111 accepts an input operation for selecting a situation. Specifically, the operation reception unit 111 receives an input operation for selecting a stage (in other words, a map) as the situation.

Next, the first user's terminal device 10 requests the server 20 to transmit a classification list suitable for the selected situation (specifically, stage) (step S502). Further, based on the request, the related user management unit 215 transmits a classified list of related users having attributes suitable for the selected situation to the first user's terminal device 10 (step S503). Specifically, for example, when the first user performs an input operation to select the first stage from among a plurality of stages including the first stage and the second stage, the related user management unit 215 A classification list is sent to the terminal device 10 of the first user, which is a list of related users who have a high winning rate in past matches in the first stage, among the plurality of related users associated with the first stage. Note that the classification list sent from the related user management unit 215 to the terminal device 10 may be created by the list creation unit 218 based on the request, or it may be created in advance by the list creation unit 218 and stored in the storage unit. The classification list may be extracted from a plurality of classification lists stored in 220 based on the request. Note that the list creation unit 218 may be included in the terminal device 10. Further, the terminal device 10 may include a classification list storage unit (for example, the storage unit 120) that stores the classification list.

Next, the display control unit 114 of the first user's terminal device 10 causes the display unit 18 to display the classification list of related users having attributes suitable for the selected situation, which was sent from the server 20 (step S504).

Note that the present invention is not limited to the embodiments described above, and can be implemented with various modifications without departing from the gist thereof. Within the scope of the present invention, each component can be freely combined, any component can be modified, or any component can be omitted. Further, the process flow described in this specification is merely an example, and the order and configuration of each process may be different.

<Additional notes>
The matters described in the above embodiments may also be described as in the following additional notes.

(Additional note 1)
computer,
After deciding to share a predetermined experience with a first user within a predetermined service, automatically associating a second user with the first user during or after the sharing; an association means (for example, association unit 216) capable of automatically making an application to the second user for association with a user;
A program that functions as a storage means (for example, storage unit 220) that stores information regarding the history of association of the second user with the first user.
In such a configuration, since the number of users associated with the first user automatically increases, there is a possibility that it becomes unclear how each user was associated with the first user. According to this configuration, information regarding the history of the association is stored for the user associated with the first user, so it is possible to understand the history of the association with the user based on the information.

(Additional note 2)
The storage means is
Input on the terminal device of the first user (for example, the terminal device 10) from among a plurality of tags (for example, tag 61) related to the history of association of the second user to the first user displayed by the terminal device (for example, the terminal device 10). The program according to supplementary note 1, wherein the tag selected by the operation is stored as information regarding the history of association of the second user with the first user.
According to such a configuration, the first user can register information regarding the history of association by selecting a tag. Therefore, it is possible to facilitate the input of information regarding the history of the association and to promote the input of the information.

(Additional note 3)
On a screen displayed by the first user's terminal device and displaying the plurality of tags related to the selection, an event that actually occurred in the predetermined experience shared by the first user and the second user is displayed. The program according to supplementary note 2, wherein the tag related to is displayed preferentially.
According to such a configuration, tags related to events that actually occurred are displayed preferentially, and input of information related to the process is assisted, making it easier to input the information and promoting the input of the information. can.

(Additional note 4)
The computer further comprises:
When the second user is associated with the first user, information for displaying a display prompting for the input of information regarding the history of the association of the second user with the first user is provided to the first user when the second user is associated with the first user. The program according to supplementary note 1 is caused to function as a history information management unit (for example, history information management unit 219) that is transmitted to a user's terminal device.
According to such a configuration, it is possible to prompt the user to input information regarding the history of the association and to facilitate the input of the information.

(Appendix 5)
When the first user makes the application from the first user's terminal device and the second user is associated with the first user based on the application, the history information management means The program according to appendix 4, wherein information for displaying a prompting display is not transmitted to the first user's terminal device.
According to such a configuration, compared to a user who is automatically associated, a user who is manually associated is more likely to be able to remember the history of the association than a user who is automatically associated. In addition, since the user is not prompted to input information regarding the history of the association, it is possible to prevent the user from feeling uncomfortable due to being excessively prompted to input the information.

(Appendix 6)
The computer further comprises:
History information management means (e.g. , the history information management unit 219).
According to such a configuration, since information regarding the history of association is automatically input, the information can be reliably stored.

(Appendix 7)
The program according to supplementary note 6, wherein the history information management means edits the information regarding the history automatically stored in the storage means based on the first user's operation.
According to such a configuration, the information regarding the history of the association can be reliably stored, and the user can freely select the information regarding the history of the association that he or she wants to keep.

(Appendix 8)
After deciding to share a predetermined experience with a first user within a predetermined service, automatically associating a second user with the first user during or after the sharing; an association means (for example, association unit 216) capable of automatically making an application to the second user for association with a user;
An information processing apparatus, comprising: a storage unit (for example, a storage unit 220) that stores information regarding the history of association of the second user with the first user.
According to such a configuration, the same effects as those of the program described in Supplementary Note 1 can be achieved.

(Appendix 9)
After deciding to share a predetermined experience with a first user within a predetermined service, automatically associating a second user with the first user during or after the sharing; an association means (for example, association unit 216) capable of automatically making an application to the second user for association with a user;
An information processing system, comprising: a storage unit (for example, a storage unit 220) that stores information regarding the history of association of the second user with the first user.
According to such a configuration, the same effects as those of the program described in Supplementary Note 1 can be achieved.

1 system, 10 terminal device, 11 processor, 12 memory, 13 storage, 16 touch screen, 17 input section, 18 display section, 20 server, 21 processor, 22 memory, 23 storage, 50 related user list display screen, 51 history information , 60 history information input screen, 61 tag, 70 classification list display screen, 75 stage selection screen, 110 control unit, 111 operation reception unit, 112 transmission/reception unit, 113 progression unit, 114 display control unit, 120 storage unit, 210 control unit , 211 transmission/reception unit, 212 server processing unit, 214 synchronization processing unit, 215 related user management unit, 216 association unit, 217 cancellation unit, 218 list creation unit, 219 history information management unit, 220 storage unit

Claims (9)

computer,
After deciding to share a predetermined experience with a first user within a predetermined service, automatically associating a second user with the first user during or after the sharing; an association means capable of automatically making an application to the second user for association with a user;
A program that functions as a storage means for storing information regarding the history of association of the second user with the first user. The storage means is
The first user selects the tag selected by an input operation on the terminal device from among a plurality of tags related to the history of association of the second user with the first user displayed by the first user's terminal device. The program according to claim 1, wherein the program is stored as information regarding the history of association of the second user to the program. On a screen displayed by the first user's terminal device and displaying the plurality of tags related to the selection, an event that actually occurred in the predetermined experience shared by the first user and the second user is displayed. The program according to claim 2, wherein the tag related to is displayed preferentially. The computer further comprises:
When the second user is associated with the first user, information for displaying a display prompting for the input of information regarding the history of the association of the second user with the first user is provided to the first user when the second user is associated with the first user. The program according to claim 1, which functions as a history information management means to be transmitted to a user's terminal device. When the first user makes the application from the first user's terminal device and the second user is associated with the first user based on the application, the history information management means The program according to claim 4, wherein information for displaying a prompting display is not transmitted to the first user's terminal device. The computer further comprises:
Functions as a history information management means for automatically storing, in the storage means, an event that caused the association of the second user with the first user as information regarding the history of association of the second user with the first user. The program according to claim 1. The program according to claim 6, wherein the history information management means edits the information regarding the history automatically stored in the storage means based on an operation by the first user. After deciding to share a predetermined experience with a first user within a predetermined service, automatically associating a second user with the first user during or after the sharing; an association means capable of automatically making an application to the second user for association with a user;
An information processing apparatus, comprising: storage means for storing information regarding the history of association of the second user with the first user. After deciding to share a predetermined experience with a first user within a predetermined service, automatically associating a second user with the first user during or after the sharing; an association means capable of automatically making an application to the second user for association with a user;
An information processing system, comprising: storage means for storing information regarding the history of association of the second user with the first user.

Images