JP2015092356A - Management apparatus, management method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a management apparatus which provides improved convenience when inviting a user being in a friend relationship in one application to another application.SOLUTION: A management apparatus: controls an invitation process by a terminal device of a first user, which has run first and second applications before, for introducing the first application to a terminal device which has run the second application before, of a user who is in a prescribed relationship with the first user in the second application; extracts candidate users to be invited to the first application based on extraction conditions; and sends to the first user terminal invitation-candidate-user information representing extracted candidate users to be invited to the first application. Identification information for identifying users in the first application and identification information for identifying users in the second application are individually managed by respective applications.

Description

  The present invention relates to a management device, a management method, and a program.

  A social game provided to SNS (Social Networking Service) members is known (see, for example, Non-Patent Document 1). This SNS also functions as a portal site of a social game provided to members, and manages the user member information in the SNS and the user information of the user in each social game in association with each other. So, for example, if you have friends, you can know which games you are playing with each other, and there are games that you are playing but your friends are not playing It is also possible to invite the member to play the game via SNS.

“Social game general information magazine application STYLE Vol.2”, East Press Co., Ltd., April 1, 2011, p. 26-p. 29

  By the way, there is a social game (hereinafter referred to as an independent social game) that can be used even if it is not a SNS member but a social game provided to SNS members. An application such as this independent social game is a so-called native application that can be used by downloading it from a store site selling the application or a dedicated site of each application and installing it on the user terminal.

In such a native type application, when inviting another user to an application used by the user, a method of using social media, e-mail, or the like has been performed. In this method, the user ID of the user to be invited is notified (invitation notification), and the user who receives the invitation inputs the user ID of the inviter when starting the invited application, thereby inviting the user and the user to be invited Was associated with the user receiving the call.
By the way, there is a case where it is desired to invite a user who is in a friend relationship in one application to another application. However, in the above method, it may be unclear whether the user who wants to invite uses social media or does not know the e-mail address. In the first place, a user who has a friendship in an application does not necessarily have a friendship in the real world, but the user name (nickname) known in the application and the social media or email used in the real world. In many cases, the user name (account name) does not match. Therefore, the above method may not be able to effectively notify the user who wants to invite. Therefore, a mechanism that can invite a user between an inviting application and an invitation receiving application has been desired. However, since user information of users in each application is managed independently, the user information is not compatible between applications. For this reason, users who are friends with one application may not be able to be invited to another application.

  The present invention has been made in view of such a situation, and provides a management device, a management method, and a program capable of improving convenience when inviting a user who is in a friend relationship to another application in another application. provide.

  In the following, in order to facilitate understanding of the present invention, reference numerals in the accompanying drawings are added in parentheses for convenience, but the present invention is not limited to the illustrated embodiments.

  In order to solve the above-described problem, according to one aspect of the present invention, the first application is executed by the second application from the terminal device (100) of the first user who has executed the first application and the second application. A control unit (230) for controlling an invitation process for introducing the first application to a user terminal device having a predetermined relationship with the second application, wherein the control unit starts from the second application. An extraction unit (239) that extracts a user who is a candidate for invitation to the first application from among users included in the predetermined relationship user information when the predetermined relationship user information indicating a user in the list is acquired And invitation candidate user information indicating users who are candidates for invitation to the first application extracted by the extraction unit, Invitation candidate user notification section (240) to be transmitted to the terminal device of the first user, and invitation application information for applying for an invitation to the first application for the second user among the users indicated in the invitation candidate user information An invitation request receiving unit (233) that receives from the terminal device of the first user, and an invitation notification unit (236) that transmits invitation notification information based on the invitation request information to the terminal device of the second user. The management device (200) is characterized in that the identification information for identifying the user in the first application and the identification information for identifying the user in the second application are independently managed for each application. .

  Further, according to one aspect of the present invention, in the management device, the extraction unit may exclude a user who has applied for an invitation from the second application to the first application from the extraction target as the extraction condition. Features.

  Further, according to one aspect of the present invention, in the management device, the extraction unit may have made an invitation application for which an invitation application from the second application to the first application has been established as the extraction condition. A certain user is excluded from the extraction target.

  Further, according to one aspect of the present invention, in the management apparatus, the extraction unit is a user who has applied for an invitation from the second application to the first application as the extraction condition. The present invention is characterized in that a user who is applying for an invitation whose application has not been approved is excluded from extraction targets.

  Further, according to one aspect of the present invention, in the management device, the extraction unit excludes, as the extraction condition, a user who has rejected an invitation application from the second application to the first application from the extraction target. It is characterized by.

  In one aspect of the present invention, the management device includes an application management unit (231) that manages information related to each of a plurality of applications including the first application and the second application, and the application management unit includes: The information includes information indicating whether or not to permit re-invitation of the user to the first application, and the extraction unit refers to the application management unit as the extraction condition, and When re-invitation of a user to one application is permitted, a user who has rejected the invitation application to the first application is included in the extraction target.

  Further, according to one aspect of the present invention, in the management device, even if the extraction unit is a user who rejects the invitation application from the second application to the first application as the extraction condition, In the case of an invitation application from a different first user, the user is included in the extraction target.

  Moreover, one mode of the present invention is characterized in that, in the management device, the extraction unit excludes, as the extraction condition, a user who is set to reject an invitation request from the first user from an extraction target. .

  According to another aspect of the present invention, the management device includes an application management unit that manages information related to each of a plurality of applications including the first application and the second application, and the application management unit includes an invitation application. 1st prohibition information that combines a setting-side user who sets prohibition of the user and a set-side user who is prohibited from applying for an invitation to the setting-side user, and the extraction unit uses the application as the extraction condition Among the first prohibition information managed by the management unit, when there is first prohibition information in which the first user is set as the set-side user, the setting-side user indicated by the first prohibition information Is excluded from the extraction target as a user who is set to reject the invitation application from the first user.

  Moreover, one aspect of the present invention is characterized in that, in the management device, the extraction unit excludes, as the extraction condition, a user who is set to reject the invitation application to the first application from the extraction target. .

  According to another aspect of the present invention, the management device includes an application management unit that manages information related to each of a plurality of applications including the first application and the second application. 2nd prohibition information that combines a setting-side user that sets prohibition of the user and a set-side application that is prohibited from applying for an invitation to the setting-side user, and the extraction unit uses the application as the extraction condition. Among the second prohibition information managed by the management unit, when there is second prohibition information in which the first application is set as the set-side application, the setting-side user indicated by the second prohibition information Is a user who is set to reject the invitation application to the first application. Wherein the excluded from the extraction target.

  In addition, according to an aspect of the present invention, the management device transmits invitation establishment information indicating that an invitation from the second application corresponding to the invitation notification information to the first application has been established. An invitation establishment receiving unit (237) that receives from a device or a server device corresponding to the first application is provided.

  Another aspect of the present invention is a management method for a management apparatus, in which a first application and a second application are executed from a terminal device of a first user who has executed the first application and the second application. A control step of controlling an invitation process for introducing the first application to a terminal device of a user having a predetermined relationship, wherein the control step is a user having the predetermined relationship from the second application; Extracting the user who is a candidate for invitation to the first application among the users included in the predetermined related user information when the predetermined related user information is acquired, and the extracted first Invitation candidate user information indicating a user who is a candidate for invitation to one application, the first user's terminal Transmitting to the device, receiving from the terminal device of the first user invitation request information for requesting the second user of the users indicated in the invitation candidate user information to the first application, Transmitting invitation notification information based on the invitation application information to a terminal device of the second user, and identifying information for identifying the user in the first application, and identifying the user in the second application The identification information is a management method characterized by being managed uniquely for each application.

  In one aspect of the present invention, identification information for identifying a user in the first application and identification information for identifying a user in the second application are managed uniquely for each application, and the first application and the For introducing the first application from the terminal device of the first user who has executed the second application to the terminal device of the user having a predetermined relationship with the first user in the second application In the case of acquiring predetermined relationship user information indicating a user having the predetermined relationship from the second application to the computer that controls the invitation process, among the users included in the predetermined relationship user information, an invitation to the first application Extracting candidate users based on extraction conditions The step of transmitting invitation candidate user information indicating users who are candidates for invitation to the extracted first application to the terminal device of the first user, and among the users indicated in the invitation candidate user information A step of receiving invitation request information for inviting a second user to the first application from the terminal device of the first user, and sending invitation notification information based on the invitation request information to the terminal device of the second user; And a step for executing the program.

  As described above, according to the present invention, in order to extract invitation candidates to be invited to other applications from a user list that is in a friend relationship with a certain application based on a predetermined extraction condition, Convenience when inviting a user to another application can be improved.

It is a schematic block diagram which shows an example of a structure of the network system by 1st Embodiment. It is a schematic block diagram which shows an example of a structure of the user terminal by 1st Embodiment. It is explanatory drawing explaining an example of a structure and process of the mutual invitation system of 1st Embodiment. It is a figure which shows the example of a display of the display screen of the user terminal in an invitation process. It is a block diagram which shows an example of the function structure performed based on SDK of the user terminal by this embodiment. It is a block diagram which shows an example of a structure of the management server by 1st Embodiment. It is a figure which shows an example of the information memorize | stored in an application setting memory | storage part. It is a figure which shows an example of the information memorize | stored in an invitation application information storage part. It is a flowchart which shows the 1st example of operation | movement of the invitation process by 1st Embodiment. It is a flowchart which shows the 2nd example of operation | movement of the invitation process by 1st Embodiment. It is a block diagram which shows an example of a structure of the management server by 2nd Embodiment. It is a figure which shows an example of the information memorize | stored in a mutual invitation rejection setting memory | storage part. It is a flowchart which shows an example of the operation | movement of the invitation process by 3rd Embodiment. It is a block diagram which shows an example of a structure of the management server by 3rd Embodiment. It is a figure which shows an example of the information memorize | stored in an invitation application rejection user setting memory | storage part. It is a figure which shows an example of the information memorize | stored in an invitation application refusal application setting memory | storage part. It is a figure explaining the 1st example of the process filtered based on an invitation application record. It is a figure explaining the 2nd example of the process filtered based on an invitation application record. It is a figure explaining the 3rd example of the process filtered based on an invitation application record. It is a figure explaining the 4th example of the process filtered based on an invitation application record. It is a figure explaining the 5th example of the process filtered based on an invitation application record. It is a flowchart explaining the operation | movement of the establishment process of a communication session.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
<First Embodiment>

[Outline of mutual invitation system]
First, an overview of the mutual invitation system according to the present embodiment will be described. In this mutual invitation system, from a user terminal of a user in which different types of first application and second application are installed, to a user terminal of another user who has a predetermined relationship with the user in the second application , A system for inviting to install a first application.

  For example, in a social game provided to a member of an SNS (Social Networking Service), user information of the user in each social game and user member information of the SNS are managed in association with each other. Therefore, for example, members who are in a friend relationship can know which game is being played with each other by the association using this member information, and members who are in a friend relationship even if they are playing If there is a game that has not been played, it is possible to invite the member to play the game via SNS.

  By the way, there is a social game (hereinafter also referred to as an independent social game) that can be used even if it is not a SNS member but a social game provided to SNS members. An application such as this independent social game is a so-called native application that can be used by downloading it from a store site selling the application or a dedicated site of each application and installing it on the user terminal.

  However, in such a native type application, user information of the user in each application is managed independently, and thus the user information is not compatible between applications. Therefore, a user who is in a friend relationship with a certain application may not be able to be invited to another application. Therefore, in this embodiment, the purpose is to provide a mutual invitation system between applications with high convenience. Even among applications where user information is not compatible, users who are friends in a certain application can be Configure to be invited to other applications.

  The application installation includes not only newly introducing an application program that has not been introduced into the user terminal, but also updating (updating) the application program so as to correspond to the mutual invitation system. That is, it includes downloading and updating an update program for supporting the mutual invitation system for the application installed in the user terminal.

[Network system configuration]
FIG. 1 is a schematic configuration diagram showing an example of a configuration of a network system 1 according to the first embodiment of the present invention that realizes a mutual invitation system. The network system 1 includes a plurality of user terminals 100-N (N is a positive integer. User terminal 100-1, user terminal 100-2,...), A management server 200, and a plurality of application servers 300 (application servers). 310, application server 320,...) And application store 400, and these computer apparatuses are communicably connected via a network NW. Here, since the plurality of user terminals 100-N have the same configuration, the description of “−1”, “−2”, etc. will be omitted and described as the user terminal 100 unless otherwise distinguished.

  The management server 200 is a management device that manages information related to the application corresponding to the mutual invitation system of the present embodiment and controls the invitation information between applications and the invitation process by communicating with the user terminal 100. Specifically, the management server 200 receives the second application of another user who has a predetermined relationship with the user in the second application from the user terminal 100 of the user in which the first application and the second application are installed. The invitation process for installing the first application to the user terminal 100 in which is installed is controlled.

  The application server 300 is a server device corresponding to an application that can be installed in the user terminal 100. Here, taking as an example the case where the application installed in the user terminal 100 is a game, the application server 310 corresponding to the game A and the application server 320 corresponding to the game B are connected to the user terminal 100 via the network NW. Indicates that it is connected. The network system 1 includes not only the application server 310 and the application server 320 but also a plurality of application servers 300 corresponding to games that can be installed and played on the user terminal 100. Here, the application installed in the user terminal 100 means that the application program is installed in the user terminal 100 so that the user terminal 100 performs processing related to the application (for example, game processing) based on the installed program. This is a so-called native application. The user terminal 100 transmits user information corresponding to the user who plays the game to the application server 300, or information required during the game play and a user list of users who are in a predetermined relationship (for example, a friend relationship) in the game. From the application server 300.

  The application store 400 is a server device that provides a store site (download service site) where an application that can be installed in the user terminal 100 can be downloaded. The user downloads and installs the purchased application to his / her user terminal 100 by connecting to the app store 400 via the network NW from his / her user terminal 100 and purchasing a desired application for a fee or free of charge. Can do.

  The user terminal 100 is a terminal device used by a user. For example, a mobile phone, a smartphone, a tablet terminal, a personal computer, a game machine with a communication function, or the like is used. Here, the user terminal 100 will be described as a smartphone.

  FIG. 2 is a schematic configuration diagram illustrating an example of the configuration of the user terminal 100 according to the present embodiment. As shown in this figure, the user terminal 100 includes an input unit 110, a display unit 120, a terminal communication unit 130, a terminal storage unit 140, and a terminal control unit 150.

The input unit 110 is an input device that accepts a user instruction according to an operation from the user and generates input instruction information according to the instruction content. For example, a keyboard, a button, a touch panel, a mouse, a microphone, or the like can be applied to the input unit 110.
The display unit 120 is a display device that displays information such as images and characters. For example, an LCD (Liquid Crystal Display), an organic EL (Electro Luminescence) display, or the like can be applied. The input unit 110 and the display unit 120 can be applied as a touch panel that is configured integrally and receives an operation input from a user.
The terminal communication unit 130 communicates with the management server 200 or the application server 300 via the network NW.
The terminal storage unit 140 is configured using a recording medium such as a random access memory (RAM), a read only memory (ROM), a flash ROM, and a hard disk drive (HDD), or a combination thereof. A control program (for example, an OS (Operating System) for causing the terminal control unit 150 to perform a basic operation), an installed application program, various information, and the like are stored.

  The terminal control unit 150 includes an information processing device such as a CPU (Central Processing Unit) that functions as a control center of the user terminal 100 and controls each unit included in the user terminal 100. For example, the terminal control unit 150 executes basic operation processing based on the OS stored in the terminal storage unit 140 and also executes processing based on an application program (game program). In addition, the terminal control unit 150 performs processing for executing functions of various applications (such as a web browser and an application that displays a store page of a store site provided by the app store 400) that can operate on the OS via the OS. Do.

  The network NW includes, for example, a mobile phone network, a PHS (Personal Handy-phone System) network, a VPN (Virtual Private Network) network, a dedicated communication network, a WAN (Wide Area Network), a LAN (Local Area Network), and a PSTN (Public Switched Telephone Network (Public Switched Telephone Network), etc., or a combination thereof.

[Configuration and processing of mutual invitation system]
Next, the configuration and processing of the mutual invitation system of this embodiment will be described with reference to FIG.
FIG. 3 is an explanatory diagram illustrating an example of the configuration and processing of the mutual invitation system in the network system 1 of the present embodiment. In this figure, components corresponding to those in FIG. 1 are denoted by the same reference numerals. Here, the user terminal 100 of the user X is a user terminal 100-1, and the user terminal 100 of the user Y is a user terminal 100-2. The game A and the game B that can be installed on the user terminal 100 are applications corresponding to the mutual invitation system. The game A and the game B are installed on the user terminal 100-1, and the user terminal 100-2 Is assumed that game B is installed (game A is not installed). Further, it is assumed that the user X and the user Y are in a friend relationship in the game B.

  This figure installs the game A from the game A of the user terminal 100-1 of the user X (inviting user) to the user terminal 100-2 of the user Y (invited user) who is in a friend relationship in the game B. It is a figure explaining the invitation process which applies for an invitation. In other words, this invitation process is performed by sending an invitation request application (hereinafter referred to as an application destination application) to game A, which is an application of an invitation request source (hereinafter referred to as an application source application) played by user X (inviting user). This is a process of inviting a user Y (invited user) who is in a friend relationship in the game B. The application source application 10 (game A) and the application destination application 20 (game B) are not the application source and the application destination, respectively, before the invitation process is performed. The application application 20 will be described.

  In addition, although the example in case the game A is the application origin application 10 and the game B is the application destination application 20 is demonstrated, the game B may become the application origin application 10 and the game A may become the application destination application 20. FIG. “Mutual invitation” in the mutual invitation system means that users who are in a predetermined relationship (for example, a friend relationship) in each application can be invited to each other between the applications.

  Here, it is schematically shown that the application source application 10 (game A) and the application destination application 20 (game B) are installed in the user terminal 100-1. On the other hand, the application 20 (game B) is installed in the user terminal 100-2, the application 10 (game A) is not initially installed, and the user terminal 100-2 is based on an invitation request from the user X. It schematically shows that it will be installed.

  The application source application 10 (game A) transmits user information corresponding to the user who plays the game A to the application server 310 (game A), or transmits information necessary for playing the game A to the application server 310 (game A). ) Similarly, the application destination application 20 (game B) transmits user information corresponding to the user who plays the game B to the application server 320 (game B), or transmits information necessary for playing the game B to the application server 320. Or obtained from (Game B). Furthermore, in the mutual invitation system of this embodiment, the application destination application 20 (game B), for example, based on an instruction from the application source application 10 (game A), a user list in the application destination application 20 (game B). Obtained from the application server 320 (game B).

  In addition, the application server 310 (game A) and the application server 320 (game B) manage user information of each user in a unique format. Therefore, the user information of the application source application 10 (game A) and the application destination application 20 (game B) is not compatible. Here, the user information is, for example, identification information that uniquely identifies a user in each application, and is identification information (hereinafter referred to as “user ID”) that is uniquely managed for each application. The user ID may be invisible information (internal information) that the user cannot grasp. Further, the user ID and the user name registered by the user may be associated and registered as user information.

  The application corresponding to the mutual invitation system of this embodiment incorporates software for invitation processing (hereinafter referred to as SDK (Software Development Kit) 11). The SDK 11 is composed of, for example, a collection of APIs (Application Programming Interfaces) for mediating between applications corresponding to the mutual invitation system installed in the user terminal 100 and the management server 200. In this figure, the application 11 (game A) includes the SDK 11A, and the application 20 (game B) includes the SDK 11B. Each of the SDK 11A and the SDK 11B has a configuration for executing a function corresponding to each of the application source application 10 and the application destination application 20, and a necessary function is executed according to each application. Note that the application corresponding to the mutual invitation system can be either the application source application 10 or the application destination application 20, and therefore the SKD 11 having both the SDK 11A and the SDK 11B is incorporated.

  That is, if an application is configured so that the above-described SDK 11 can be incorporated, the application becomes an application corresponding to the mutual invitation system of the present embodiment. Note that an application in which the above-described SDK 11 is preliminarily incorporated may be provided so as to be downloadable, or an SDK 11 that can be incorporated later into an installed application may be provided.

  Among the applications corresponding to the mutual invitation system, there may be an application corresponding to only the application destination application 20. In that case, only the SDK 11B may be incorporated, or the SDK 11A may be incorporated so that the SDK 11A does not function. For example, an application that does not accept registration of a new user after the service provision by the application is terminated may not have the function as the application source application 10. Further, among the applications corresponding to the mutual invitation system, there may be an application corresponding to only the application source application 10. In that case, only the SDK 11A may be incorporated, or the SDK 11B may be incorporated so that the SDK 11B does not function. In these cases, “one-way invitation” is used instead of “mutual invitation”. In other words, the mutual invitation system can support either “mutual invitation” or “one-way invitation”, or can support either “mutual invitation” or “one-way invitation” depending on the application. it can.

  The configuration including the above-described SDK 11 (SDK 11A, SDK 11B in this figure) and the management server 200 is the main configuration of the mutual invitation system of the present embodiment (see reference numeral 500). And describe. In the following description, an application corresponding to the mutual invitation system 500 is also referred to as “corresponding application”. Further, identification information for uniquely identifying an application is referred to as an “application ID”.

  The management server 200 manages information related to the corresponding application. In addition, the management server 200 controls the invitation process by communicating with the SDK 11 incorporated in the corresponding application installed in the user terminal 100.

  As shown in this figure, the management server 200 includes a communication unit 210, a storage unit 220, and a control unit 230. The communication unit 210 communicates with the user terminal 100, the application server 310 (game A), or the application server 320 (game B) via the network NW. The storage unit 220 stores various types of information such as information about supported applications and information about invitation applications. The control unit 230 controls transmission / reception of invitation processing and invitation processing with the user terminal 100 or the application server 310 (game A).

Next, an outline flow of the invitation process in the mutual invitation system 500 will be described. Here, the application source application 10 (game A) and the application destination application 20 (game B) are installed in the user terminal 100-1 of the user X. On the other hand, it is assumed that application destination application 20 (game B) is installed in user terminal 100-2 of user Y (application source application 10 (game A) is not installed).
When the corresponding application is installed (executed) for the first time after the corresponding application is installed in the user terminal 100, for example, the application ID of the corresponding application and the user ID of the user of the corresponding application are set in the SDK 11 from the corresponding application main body. It shall be.

(1) Application list request from the application source application to the management server (user terminal of the invited user)
The SDK 11A of the application source application 10 (game A) installed in the user terminal 100-1 of the user X who is an invited user performs the first operation (user X) in the application source application 10 (game A) operating in the normal mode. Based on the operation), application list request information for requesting an application list including a part or all of a plurality of corresponding applications is transmitted to the management server 200 (REQ11). Here, the above-described first operation refers to, for example, the input unit 110 for acquiring an application list of compatible applications that can apply an invited user to the application source application 10 (selectable as the application destination application 20). It is an operation.

  When the management server 200 acquires the application list request information from the user terminal 100-1 (SDK 11A), the management server 200 displays the application list of the corresponding application that can apply for the invited user to the application source application 10 (game A). It transmits to terminal 100-1 (SDK11A) (RES11). When the user terminal 100-1 (SDK 11A) acquires the application list from the management server 200, the user terminal 100-1 (SDK11A) displays at least a part of the corresponding application installed in the user terminal 100-1 on the display unit 120 from the acquired application list. .

(2) Friend list display of application destination application (user terminal of invited user)
From the application list displayed on the display unit 120 of the user terminal 100-1, the corresponding application in which the user who wants to invite to the application source application 10 (game A) is registered is selected by the second operation of the user X. Here, the above-described second operation is an operation on the input unit 110, for example, for selecting one of a plurality of corresponding applications included in the application list displayed on the display unit 120.
When one of a plurality of corresponding applications included in the application list (here, application destination application 20 (game B)) is selected, the user terminal 100-1 (SDK11A) selects the selected application destination application 20 (game B). ) In a specific mode.

  Here, activation of the corresponding application includes “activation of normal mode” and “activation of specific mode”. “Activation in the normal mode” is activation for the purpose of using the corresponding application (for example, playing a game), and “activation in the specific mode” is a specific function among the functions of the corresponding application. It is a startup in the form of calling (executing). For example, when the application destination application 20 (game B) is activated in the specific mode, the application destination application 20 (game B) shifts to an operation state in the specific mode that executes a specific function among the functions of the application destination application 20 (game B). . The specific function here refers to a friend list corresponding to a user list of a user who has a predetermined relationship (for example, a friend relationship) with the invited user (user X) in the application destination application 20 (game B). 1 is a function to be displayed on one display unit 120.

  In addition, as an example of the operating state of the corresponding application, the non-operating state (Not running), the operating state in which some processing is executed (Active), and the background in which some processing is executed but not displayed on the screen There are a state (BackGround) and a suspended state (Suspended) where no processing is executed. Here, “activation of the corresponding application” refers to transition from the non-operating state (Not running), the suspended state (Suspended), or the suspended state (Suspended) to the operating state (Active). “End of corresponding application” refers to transition from an operating state (Active) to a non-operating state (Not running), a suspended state (Suspended), or a suspended state (Suspended).

  For example, starting the application destination application 20 (game B) in the specific mode refers to shifting the application destination application 20 (game B) to the operation state (Active) of the specific mode. At this time, the application source application 10 (game A) shifts from the normal mode operating state (Active) to the non-operating state (Not running), the suspended state (Suspended), or the suspended state (Suspended). In addition, when the operation of the application destination application 20 (game B) in the specific mode is ended, the application application 20 (game B) in the operation mode (Active) of the specific mode is changed to a non-operating state (Not running) or a suspended state. (Suspended) or transition to a suspended state (Suspended).

  In addition, when a plurality of compatible applications can be in an operating state at the same time, “activation of a compatible application” means, for example, that the compatible application is displayed on the forefront of the screen and can be operated by the user. The transition to a state.

  In user terminal 100-1, application destination application 20 (game B) activated in the specific mode displays a user list of users who have a predetermined relationship (for example, friend relationship) with user X in application destination application 20 (game B). The application server 320 (game B) is inquired and acquired. And SDK11B of the application destination application 20 (game B) of the user terminal 100-1 displays the friend list corresponding to the user list which the application destination application 20 (game B) acquired on the display part 120. FIG.

(3) Application for invitation from application to application to management server (user terminal of invited user)
When user X who is an invited user selects user Y who is an invited user invited to application source application 10 (game A) from the friend list displayed on display unit 120 of user terminal 100-1, the user The terminal 100-1 (SDK 11 </ b> B) transmits invitation application information for requesting the selected user Y to the application source application 10 (game A) to the management server 200 (REQ <b> 13). At this time, a plurality of invited users may be selected. When a plurality of invited users are selected, the user terminal 100-1 (SDK11B) transmits a plurality of invitation application information corresponding to each invited user to the management server 200. When receiving the invitation application information transmitted from the user terminal 100-1 (SDK11B), the management server 200 stores the received invitation application information in the storage unit 220 for management.

(4) Application inquiry from application to application to management server (user terminal of invited user)
The SDK 11B of the application destination application 20 (game B) installed in the user terminal 100-2 of the user Y who is the invited user is included in the invitation application information managed by the management server 200. Whether or not there is invitation application information to be obtained is inquired at a predetermined timing (eg, a predetermined time interval during activation or during activation) (REQ21). When invitation application information in which the invited user is the user Y is managed by the management server 200, the management server 200 is based on the invitation application information in response to the above inquiry from the user terminal 100-2 (SDK11B). The invitation notification information is transmitted to the user terminal 100-2 (SDK11B) (RES21). The user terminal 100-2 (SDK11B) acquires the invitation notification information transmitted from the management server 200.

  In addition, when the user terminal 100-2 (SDK11B) acquires the invitation notification information from the management server 200, the invitation notification information is displayed on the startup screen or a predetermined screen of the application destination application 20 (game B) displayed on the display unit 120. Invitation notification is displayed to indicate that has been acquired. Thereby, the user X is notified of the invitation application for inviting the user Y to the application source application 10 (game A) via the application destination application 20 (game B). Also, the user terminal 100-2 (SDK 11B) receives invitation information (information indicating an invited user, information indicating an application source application 10 (game A), etc.) indicating the contents of the invitation application based on the acquired invitation notification information. It is displayed on the display unit 120.

(5) Application source application installation (user terminal of invited user)
User Y who is an invited user can accept or reject the notified invitation application. In addition, when the application source application 10 (game A) of the notified invitation application is already installed in the user terminal 100-2, the user terminal 100-2 (SDK11B) displays the fact on the display unit 120. You may let them.
When the user Y accepts the notified invitation application, the user terminal 100-2 (SDK11B) stores the invitation notification information corresponding to the accepted invitation application in the terminal storage unit 140. In addition, the user terminal 100-2 displays a store page on the display unit 120 where the application source application 10 (game A) of the store site provided from the app store 400 can be downloaded.
The user Y downloads and installs the application source application 10 (game A) from the store page to the user terminal 100-2. When the application source application 10 (game A) installed in the user terminal 100-2 is activated by the operation of the user Y, the SDK 11A of the application source application 10 (game A) becomes the SDK 11B of the application destination application 20 (game B). Acquires the invitation notification information acquired from the management server 200 and stored in the terminal storage unit 140. Whether or not the corresponding application is installed based on the invitation request can be determined based on the presence or absence of the invitation notification information.

(6) Notification of invitation establishment from the application application to the management server (invited user terminal)
Based on the fact that the user Y has started the application source application 10 (game A) installed in the user terminal 100-2 based on the invitation request, or that the play has started and has reached a preset achievement point. The user terminal 100-2 (SDK11A) transmits invitation establishment information indicating that the invitation by the invitation application has been established to the management server 200 (REQ22). Here, the above-mentioned result point is a point where the game A has progressed (played) to some extent, and can be arbitrarily selected on the application side, such as the end of the tutorial or the end of a predetermined stage in the game progress or the acquisition of a predetermined point. This is a settable outcome point.

(7) Notification of invitation completion from the management server to the application server of the application source application When the management server 200 receives the invitation establishment information transmitted from the user terminal 100-2 (SDK11A), it indicates that the invitation by the invitation application has been completed. The invitation completion notification information shown is transmitted to the application server 310 (game A) (REQ23). When the application server 310 (game A) receives the invitation completion notification information transmitted from the management server 200, the application server 310 (game A) receives a predetermined reward (for example, incentive) for the invitation being completed (established). To user X in This predetermined reward is, for example, a virtual currency or an item that can be used in the application source application 10 (game A).

  Through such a processing flow, an invitation application to the application source application 10 (game A) is made via the application destination application 20 (game B). Here, in the mutual invitation system 500, the invitation user and the invited user have a predetermined relationship (for example, a friend relationship) with respect to the invitation application information for applying the invited user to the application source application 10 (game A). It can transmit with respect to the management server 200 via the application destination application 20 (game B). Therefore, the mutual invitation system 500 can invite users who have a predetermined relationship (for example, a friend relationship) in another application to another application even between applications whose user information is not compatible.

  Further, in the mutual invitation system 500, the management server 200 manages the above invitation application information record (invitation application record) to manage the invitation process when the user information is different between applications. It is different from managing each user's own user information. Therefore, the mutual invitation system 500 does not require a login operation to the SNS server with a member ID such as SNS, and the user can be invited to the application without having to be aware of the existence of the management server 200. Therefore, according to this embodiment, the convenience at the time of inviting a user between applications can be improved.

[Example of display screen of user terminal 100 in invitation process]
Next, an example of a display screen displayed on the display unit 120 of the user terminal 100 in the invitation process in the mutual invitation system 500 will be described with reference to FIG.
FIG. 4 is a diagram illustrating a display example of the display screen of the user terminal 100 in the invitation process. In this figure, the display screens indicated by reference numerals (a), (b), (c), and (d) are invited users in the process of the invitation process (the process of (1) to (3) in FIG. 3). The display screen displayed on the display part 120 of the user terminal 100-1 of a certain user X is shown. Further, the display screens indicated by reference numerals (e) and (f) are displayed on the user terminal 100-2 of the user Y who is the invited user in the process of the invitation process (the process of processes (4) to (5) in FIG. 3). The display screen displayed on the display part 120 is shown.

  Here, the area | region of the code | symbol 120a has shown the whole area | region of the display screen regarding an invitation process. The area 120a includes an area 120b where a title or the like is displayed and an area 120c where content or the like corresponding to the title is displayed.

First, a display screen displayed on the display unit 120 of the user terminal 100-1 of the user X who is an invited user will be described.
The display screen shown in (a) is an example of an invitation screen in the application source application 10 (game A) (example of display screen displayed in the process of (1) in FIG. 3). In the area denoted by reference numeral 120b, the title of the application source application 10 (game A) in operation (here, “game A”) is displayed. In the area indicated by reference numeral 120c, an “invite button” K1 for starting an invitation process for inviting a friend of another game is displayed. The “invite button” K1 is displayed as an operator for causing the application terminal request information to be transmitted from the user terminal 100-1 (SDK 11A) to the management server 200. For example, when the user X operates (first operation) on the “invite button” K1, the user terminal 100-1 (SDK 11A) transmits application list request information to the management server 200 (FIG. 3). (REQ11 of (1)).

  The display screen shown in (b) is an example of a display screen (application list screen) of a list of corresponding applications corresponding to the application list (example of display screen displayed in the process of (1) in FIG. 3). When the user terminal 100-1 (SDK11A) acquires the application list transmitted from the management server 200 (RES11 in (1) of FIG. 3) based on the operation on the “invite button” K1, the acquired application list is displayed. At least a part of the corresponding applications installed in the user terminal 100-1 is displayed as an application list screen on the display unit 120 by switching from the invitation screen. In the area denoted by reference numeral 120b, “application list” is displayed as the title of the display screen. In the area denoted by reference numeral 120c, information indicating a corresponding application that can be applied for invitation (selection of invited user) is displayed side by side. Here, each piece of information indicating the corresponding application displayed in the reference numeral 120c is displayed as an operator that can select the corresponding application in accordance with an operation (second operation) from the user X. Also, in the area indicated by reference numeral 120b, a “return button” K2 is displayed as an operator for returning to the previous display screen.

  In addition, when the corresponding application other than the application source application 10 (game A) is not installed in the user terminal 100-1, the user terminal 100-1 (SDK11A) And so on are displayed on the display unit 120.

  The display screen shown in (c) is an example of a display screen (friend list screen) on which a friend list is displayed (an example of a display screen displayed in the process of (2) in FIG. 3). When the application destination application 20 (game B) selected by the operation (second operation) of the user X from the application list screen shown in (b) is activated in the specific mode, the user terminal 100-1 (SDK11B) A friend list screen on which a friend list corresponding to a user list of a user who has a predetermined relationship (for example, a friend relationship) with the user X in 20 (game B) is displayed on the display screen in the application source application 10 (game A). Switching from an application list screen is displayed on the display unit 120. In the area denoted by reference numeral 120b, “game B friend list” is displayed as the title of the display screen. Information indicating users who can be selected as invited users is displayed side by side in the area denoted by reference numeral 120c. Here, each of the information indicating the user displayed in the reference numeral 120c is displayed as an operator that can select the invited user in accordance with an operation from the user X. Note that it is possible to select a plurality of invited users on this friend list screen. For example, it is possible to select one or a plurality of users as invited users by switching on and off (checked and unticked) check boxes displayed corresponding to information indicating a plurality of users. In the area denoted by reference numeral 120b, a “decision button” K3 is displayed as an operator for determining (selecting and confirming) the user selected in the area denoted by reference numeral 120c. Also, in the area indicated by reference numeral 120b, a “return button” K2 is displayed as an operator for returning to the previous display screen.

  When there is no user who has a predetermined relationship (for example, friend relationship) with the user X in the application destination application 20 (game B), the user terminal 100-1 (SDK11B) displays a message to that effect on the display unit 120. To display.

  The display screen shown in (d) is an example of a display screen (invitation application completion screen) indicating that the invitation application for the invited user has been completed (example of display screen displayed in the process of (3) in FIG. 3). . The user terminal 100-1 (SDK11B) uses the user (in this case, the user Y) selected from the friend list screen shown in (c) according to the operation of the user X as the invited user, and the user Y as the application source application 10. When invitation application information for an invitation application to (Game A) is transmitted to the management server 200 (REQ 13 in (3) of FIG. 3), the invitation list is displayed on the display unit 120 by switching from the friend list screen. In the area denoted by reference numeral 120b, "Invitation application complete" is displayed as the title of this display screen. In the area indicated by reference numeral 120c, an “end button” K4 is displayed as an operator for ending the invitation process by an operation from the user X, and a “continue button” K5 is displayed as an operator for continuing the invitation process.

  When the “Continue button” K5 is operated, the user terminal 100-1 (SDK11B) switches the display to a friend list screen shown in (c), for example. On the other hand, when the “end button” K4 is operated, the user terminal 100-1 (SDK11B) ends the display of the invitation application completion screen and the operation of the specific mode. And the display screen of the display part 120 returns to the display of the invitation screen in the application origin application 10 (game A).

  Here, the invitation screen shown in (a) and the application list screen shown in (b) are displayed by the user terminal 100-1 (SDK11A) in the normal mode operation of the application source application 10 (game A). It is a display screen. On the other hand, the friend list screen shown in the above (c) and the invitation application completion screen shown in (d) are displayed by the user terminal 100-1 (SDK11B) in the operation of the application destination application 20 (game B) in the specific mode. This is a display screen to be displayed. The application destination application 20 (game B) is in the operating state (Active) in the specific mode and the friend list screen shown in (c) or the invitation application completion screen shown in (d) The operation state of the application 10 (game A) is a non-operating state (Not running), a suspended state (Suspended), or a suspended state (Suspended).

  Next, the display screen displayed on the display part 120 of the user terminal 100-2 of the user Y who is an invited user is demonstrated. Invitation application notification with user Y as the invited user in application destination application 20 (game B) is activated when application destination application 20 (game B) is activated in the normal mode on user terminal 100-2 of user Y. User Y is notified.

  The display screen shown in (e) is an example of an invitation notification screen that is notified when there is an invitation application in which the invited user is the user Y (displayed in the process of (4) in FIG. 3). Display screen example). This invitation notification screen is, for example, a startup screen of the application destination application 20 (game B) (a screen that can start playing a game displayed when the application is started). In the area denoted by reference numeral 120b, the title (in this case, “game B”) of the application 20 (game B) in operation is displayed. The area denoted by reference numeral 120c includes a display area for a message (notification) that reaches the user Y, and displays an invitation notification message indicating that there is an invitation request for the invited user to be the user Y. This invitation notification message is displayed as an operator that switches to an invitation information list screen that displays a list of invitation information that has been delivered to the user Y in the application destination application 20 (game B) in response to an operation from the user Y. Is done.

  The display screen shown in (f) is an example of an invitation information list screen that displays a list of invitation information (example of display screen displayed in the process of (4) in FIG. 3). The user terminal 100-2 (SDK11B) switches from the invitation notification screen and displays the invitation information list screen on the display unit 120 in response to the operation of the user Y with respect to the invitation notification message displayed on the invitation notification screen shown in (e). To do. In the area indicated by reference numeral 120b, “invitation information list” is displayed as the title of the display screen. In the area indicated by reference numeral 120c, invitation information that has arrived at user Y in application destination application 20 (game B) is displayed side by side. Here, as the invitation information, information (for example, user X) indicating the inviting user and information (for example, game A) indicating the application source application 10 (game A) that is a corresponding application for inviting the user Y are displayed. Is done. Further, this invitation information is displayed on the display screen of the store page where the application store 400 can be downloaded and the application source application 10 (game A) can be downloaded in response to an operation (third operation) for accepting the invitation from the user Y. Displayed as a switch operator. Also, in the area indicated by reference numeral 120b, a “return button” K2 is displayed as an operator for returning to the previous display screen.

[Functional configuration of user terminal 100 (SDK11)]
Next, with reference to FIG. 5, the functional configuration of the invitation process executed by the user terminal 100 (SDK 11) in the mutual invitation system 500 will be described. FIG. 5 is a configuration diagram illustrating an example of a functional configuration of an invitation process performed by the terminal control unit 150 based on the SDK 11 in the user terminal 100 according to the present embodiment.

  The SDK 11 includes an application list acquisition unit 161, a specific mode activation unit 162 (activation unit), a user list acquisition unit 163, an invitation application notification unit 164, a specific mode end unit 165, an inquiry unit 166, and an invitation notification acquisition. Unit 167, presentation unit 168, screen transition unit 169, invitation information management unit 170, and invitation establishment notification unit 171.

  The application list acquisition unit 161 acquires from the management server 200 an application list including a part or all of a plurality of corresponding applications corresponding to the mutual invitation system 500. For example, the application list acquisition unit 161 sends application list request information for requesting the above application list to the management server 200 based on the above-described first operation in the corresponding application (application source application 10) operating in the normal mode. To send. Then, the application list acquisition unit 161 acquires from the management server 200 the application list transmitted from the management server 200 that acquired the application list request information.

  The specific mode activation unit 162 activates the application destination application 20 that is an application selected from the corresponding applications included in the application list in the specific mode. For example, the specific mode activation unit 162 of the SDK 11A of the application source application 10 activates the application destination application 20 selected from the corresponding applications included in the application list in the specific mode. As described above, starting the application destination application 20 in the specific mode means, for example, shifting the application destination application 20 to the operation state (Active) of the specific mode.

  In addition, the specific mode activation unit 162 notifies the SDK 11B of the application destination application 20 of the user ID of the invited user (for example, the user X) in the application source application 10 operating in the normal mode. As a result, the user ID of the invited user (for example, user X) in the application source application 10 can be notified from the SDK 11B of the application destination application 20 to the management server 200. Further, the specific mode activation unit 162 notifies the application destination application 20 of the application ID of the application source application 10 operating in the normal mode. As a result, the application ID of the application source application 10 can be notified from the SDK 11B of the application destination application 20 to the management server 200.

  In addition, the specific mode activation unit 162 directly or directly applies the user ID of the invited user (for example, the user X) in the application source application 10 or the application ID of the application source application 10 to the SDK 11B of the application destination application 20. Notification is indirectly made via the terminal storage unit 140 of the user terminal 100.

  The user list acquisition unit 163 is managed by the application server 300 corresponding to the application destination application 20 operating in the specific mode (for example, the application server 320 (game B) corresponding to the application destination application 20 (game B)). A user list of users who are in a predetermined relationship (for example, friend relationship) with the invited user (for example, user X) is acquired. Specifically, for example, the application destination application 20 acquires a user list from the application server 300 corresponding to the application destination application 20, and the user list acquired by the SDK 11B of the application destination application 20 includes the user list acquired by the application destination application 20. The part 163 acquires. That is, the user list acquisition unit 163 included in the SDK 11 </ b> B of the application destination application 20 acquires a user list from the application server 300 corresponding to the application destination application 20 via the application destination application 20.

  The invitation request notification unit 164 manages invitation request information indicating that an invited user (for example, user Y) selected from the user list acquired by the user list acquisition unit 163 is applied to the application source application 10. It transmits to the server 200. In this invitation application information, for example, the user ID of the invited user (for example, user X) in the application source application 10, the user ID of the invited user (for example, user X) in the application destination application 20 activated in the specific mode, or The user ID in the application destination application 20 of the invited user (for example, user Y) selected from the user list is included. Thereby, the invitation user (for example, user X) in the application origin application 10 is an invitation application with respect to the invited user (for example, user Y) selected from the user list as an invitation user in the application destination application 20. can do.

  The invitation application information may further include the application ID of the application source application 10. The invitation application information may further include the application ID of the application application 20.

  Here, the user ID of the invited user (for example, user X) or the application ID of the application source application 10 in the application source application 10 included in the invitation request information is applied at the user terminal 100 of the invited user (for example, user X). The destination application 20 is directly acquired from the application source application 10 or indirectly via the terminal storage unit 140 of the user terminal 100.

  The specific mode end unit 165 ends the application 20 that has been activated in the specific mode. For example, the specific mode end unit 165 included in the SDK 11B of the application destination application 20 activated in the specific mode, after the invitation application notification unit 164 included in the SDK 11B transmits the invitation application information, End the operation. Here, as described above, the end of the operation in the specific mode of the application destination application 20 means that the application destination application 20 (game B) in the operation state (Active) of the specific mode is changed to the non-operation state (Not running), Transition to the suspended state (Suspended) or the suspended state (Suspended).

  The inquiry unit 166 records, in the application 20 that is operating in the normal mode, invitation application information (that is, invitation application information for the user) that the invited user is the own user (for example, the user Y) (invitation application record). ) To the management server 200 (application inquiry). For example, the inquiry unit 166 receives invitation application information (invitation application) in which the user ID in the application destination application 20 of the invited user included in the invitation application information (invitation application record) is the user ID of the own user (for example, user Y). The management server 200 is inquired about the presence or absence of recording.

  As a result of the inquiry by the inquiry unit 166, the invitation notification acquisition unit 167 has invitation application information (invitation application record) in which the user ID of the own user (for example, the user Y) becomes the user ID of the invited user in the application destination application 20. In this case, invitation notification information based on the invitation application information (invitation application record) is acquired from the management server 200.

  The presentation unit 168 presents the various types of information by generating a display screen based on various types of information included in the acquired application list, user list, and the like and causing the display unit 120 to display the display screen. For example, the presentation unit 168 (first presentation unit, application list presentation unit) presents a corresponding application installed in the user terminal 100 from the application list acquired by the application list acquisition unit 161 ((b in FIG. 4). Refer to the application list screen example shown in)).

  Here, as a method for detecting the corresponding application installed in the user terminal 100 from the application list, for example, there is a method using a URL scheme. The URL scheme calls an application or a specific function in the application, and is defined for each application. Therefore, the corresponding application can be identified by using the URL scheme.

  For example, when the corresponding application is installed (executed) for the first time after the corresponding application is installed in the user terminal 100, the URL scheme of the corresponding application is set in the initialization process for the SDK 11 of the installed corresponding application. In addition to the application list, the application list acquisition unit 161 acquires URL schemes corresponding to the corresponding applications included in the application list. Then, the presentation unit 168 detects the corresponding application installed in the user terminal 100 based on the URL scheme of the installed corresponding application and the URL scheme of the corresponding application included in the application list, and detects the detected corresponding application. Present.

  When the list of compatible applications already installed in the user terminal 100 can be acquired by a standard function of the OS or the like, the presentation unit 168 uses the list of compatible applications already installed to The corresponding application installed in the user terminal 100 may be detected.

  The presentation unit 168 presents at least a part of users included in the user list acquired by the user list acquisition unit 163. For example, the presentation unit 168 causes the display unit 120 to display a user list screen (friend list screen) of a user who is in a predetermined relationship (for example, a friend relationship) with the invited user (for example, the user X) in the application destination application 20 ( (See the example of the friend list screen shown in FIG. 4C).

  The presentation unit 168 (second presentation unit, invitation information presentation unit) presents invitation information based on the invitation notification information acquired by the invitation notification acquisition unit 167. For example, the presentation unit 168 causes the display unit 120 to display an invitation information list screen that displays a list of invitation information in which the invited user is the own user (for example, the user Y) (invitation information illustrated in (f) of FIG. 4). Refer to the list screen example).

The screen transition unit 169 causes the application source application 10 indicated by the invitation information accepted by the invited user in the invitation information presented by the presentation unit 168 to transition to a screen on which installation is possible. For example, the screen transition unit 169 makes a transition to a screen on which the application source application 10 indicated by the invitation information can be installed based on the above-described third operation for the invitation information presented by the presentation unit 168.
For example, the screen transition unit 169 activates an application (application store) that displays a store page of a store site where the application source application 10 can be installed (downloadable). Then, the activated app store acquires a store page in which the application source application 10 can be installed from the app store 400 and causes the display unit 120 to display the store page.

  The invitation information management unit 170 displays the invitation notification information corresponding to the invitation information accepted by the invited user (for example, the user Y) in the invitation information presented by the presentation unit 168, in the terminal storage unit 140 of the user terminal 100. Remember me. In addition, the invitation information management unit 170 may store at least part of information included in the invitation notification information in the terminal storage unit 140 of the user terminal 100.

  When the predetermined condition is satisfied in the corresponding application operating in the normal mode, the invitation establishment notification unit 171 stores the invitation notification information corresponding to the corresponding application in operation in the terminal storage unit 140 of the user terminal 100. On the condition that the invitation has been made, invitation establishment information indicating that the invitation corresponding to the invitation notification information has been established is transmitted to the management server 200. Here, the case where the predetermined condition is satisfied in the above-described corresponding application is, for example, the case where the achievement point set in advance in the corresponding application is reached as described with reference to FIG. This result point may include a time when the corresponding application is installed (executed) for the first time after being installed. That is, a predetermined condition may be satisfied when the corresponding application is executed (activated) for the first time in the normal mode.

  Here, the invitation establishment information described above includes a part or all of the invitation notification information. Part or all of the invitation notification information is received by the SDK 11A of the application source application 10 at the user terminal 100 of the invited user directly from the SDK 11B of the application destination application 20 or via the terminal storage unit 140 of the user terminal 100. It is acquired indirectly. For example, in the user terminal 100 (for example, the user terminal 100-2) of the invited user (for example, the user Y), the invitation establishment notification unit 171 of the SDK 11A of the application source application 10 manages the invitation information of the SDK 11B of the application destination application 20. The unit 170 acquires at least a part of information included in the invitation notification information stored in the terminal storage unit 140.

  Among the functional configurations of the invitation process executed by the SDK 11 shown in FIG. 5, for example, an application list acquisition unit 161, a specific mode activation unit 162 (activation unit), a presentation unit 168, an invitation information management unit 170, The invitation establishment notification unit 171 corresponds to the functional configuration of the SDK 11A of the application source application 10 (that is, the functional configuration of the application source). In addition, for example, the user list acquisition unit 163, the invitation application notification unit 164, the specific mode end unit 165, the inquiry unit 166, the invitation notification acquisition unit 167, the presentation unit 168, and the screen transition unit 169 apply. This corresponds to the functional configuration of the SDK 11B of the destination application 20 (that is, the functional configuration of the application destination).

[Configuration of Management Server 200]
Next, details of the configuration of the management server 200 will be described with reference to FIG.
FIG. 6 is a configuration diagram illustrating an example of the configuration of the management server 200 according to the present embodiment. As described with reference to FIG. 3, the management server 200 includes the communication unit 210, the storage unit 220, and the control unit 230. Here, the management unit 200 includes the storage unit 220 and the control unit 230. The configuration will be described in detail.

  The storage unit 220 stores various information managed by the control unit 230. As shown in this figure, the storage unit 220 includes an application setting storage unit 221 and an invitation request information storage unit 222. Various types of information may be stored in a format suitable for the use of the information, such as a database table format or a JSON (Java Script (registered trademark) Object Notation) format.

The application setting storage unit 221 stores information (application information) related to the corresponding application corresponding to the mutual invitation system 500. FIG. 7 is a diagram illustrating an example of application information stored in the application setting storage unit 221. The application information includes an application ID (ApID) of the corresponding application, a notification destination URL (NoticeURL), a store URL (ApStoreURL), an application name (ApNAME) indicating the name of the corresponding application, and explanatory information about the corresponding application. Is an application description (ApDOC), an application icon image (ApICO) that is an icon image indicating the corresponding application, and a re-invite permission flag (FlagResultInvite).
The notification destination URL (NoticeURL) is the URL (Uniform Resource Locator) of the notification destination of the invitation completion notification information. For example, the URL of the application server 300 corresponding to the corresponding application is set. The store URL (ApStoreURL) is a URL of a page of a sales site (application store 400) where the corresponding application can be downloaded. As the application URL scheme (ApURI), a URL scheme defined in the corresponding application is set. The re-invitation permission flag (FlagResultInvite) is set with flag information indicating whether or not the corresponding application can be re-invited. For example, in the re-invite permission flag (FlagResultInvite), a flag “0” is set when re-invitation is impossible, and a flag “1” is set when re-invite is possible.
The application information is set in advance and stored in the application setting storage unit 221 before the corresponding application can be downloaded from the application store 400, for example.

  The invitation request information storage unit 222 stores information included in the invitation request information transmitted from the user terminal 100 and acquired by the management server 200 as an invitation request record. In other words, the invitation application information storage unit 222 is an invited user (e.g., user X) of the application source application 10 who is in a predetermined relationship (e.g., friend relationship) with the invited user in the application destination application 20 (e.g., friend relationship). The information included in the invitation application information for applying the user Y) to the requesting application 10 is stored as an invitation application record.

  For example, when the management server 200 acquires the invitation application information transmitted from the user terminal 100, the invitation application record includes a new record corresponding to the invitation application information (data for one invitation application information). It is generated and stored in the invitation request information storage unit 222 as a record of the invitation request information.

  The invitation application record includes information other than the information included in the invitation application information acquired from the user terminal 100, and the information includes information updated during the invitation process.

  FIG. 8 is a diagram illustrating an example of an invitation application record stored in the invitation application information storage unit 222. The invitation application record includes an invitation ID (InviteID), an application source application ID (ApIDfrom), an invitation user ID of the application source application (Apfrom_UIDfrom), an invited user ID of the application source application (Apfrom_UIDto), and an application destination application The ID (ApIDto), the invitation user ID of the application destination application (Apto_UIDfrom), the invited user ID of the application destination application (Apto_UIDto), and the invitation request status (StatusInvite) are associated with each other.

  The invitation ID (InviteID) is a management ID issued in the order in which the pieces of invitation application information are acquired so that each piece of invitation application information stored as an invitation application record can be identified. The application source application ID (ApIDfrom) is the application ID of the application source application 10, the invitation user ID of the application source application (Apfrom_UIDfrom) is the user ID in the application source application 10 of the invited user, and the application source application is invited. The user ID (Apfrom_UIDto) is a user ID in the application source application 10 of the invited user. The application destination application ID (ApIDto) is the application ID of the application destination application 20, the invitation user ID of the application destination application (Apto_UIDfrom) is the user ID of the invitation user application destination application 20, and the application destination application is invited. The user ID (Apto_UIDto) is a user ID in the application destination application 20 of the invited user.

  In the invitation application status (StatusInvite), flag information indicating the status of the degree of progress of the invitation process based on the invitation application information transmitted from the user terminal 100 is set. For example, in the status of invitation request (StatusInvite), a flag “0” (invitation application not notified) is set when the invitation notification information based on the invitation application information received by the management server 200 is not notified to the invited user. When it is notified to the invited user, the flag “0” is updated to the flag “1” (invitation application notified). When the management server 200 receives invitation establishment information corresponding to this invitation request information from the user terminal 100 of the invited user, the status of the invitation request (StatusInvite) is changed from the flag “1” to the flag “2” (invite (Not established). Furthermore, based on the invitation establishment information received by the management server 200, when invitation establishment notification information for notifying the application source application 10 that the invitation has been established is transmitted to the application server 300 corresponding to the application source application 10, The invitation request status (StatusInvite) is updated from the flag “2” to the flag “3” (notification of invitation establishment). Moreover, when the invitation application information received by the management server 200 is rejected by the invited user, and a state where the flag “0” or the flag “1” is set in the invitation application status (StatusInvite) is predetermined. When the time has passed or when the invitation request is rejected, the invitation request status (StatusInvite) is updated to a flag “−1” (failure) indicating that the invitation has failed.

  The invitation application record may further associate the invitation user name (Apto_NAMEfrom) of the application destination application and the invitation user image URL (Apto_URLfrom) of the application destination application. Here, the invitation user name (Apto_NAMEfrom) of the application destination application is a user name in the application destination application 20 of the invitation user, and the invitation user image URL (Apto_URLfrom) of the application destination application is a user in the application destination application 20 of the invitation user. This is a URL indicating the link destination of the image. These pieces of information are not necessarily required in the flow of the invitation process from (1) to (7) shown in FIG. 3, but by including these pieces of information in the invitation application record (invitation application information), the invitation notification information is displayed. In the application destination application 20 of the received user terminal 100 of the invited user, the user name and user image of the invited user can be displayed only by the processing of the SDK 11B.

  The control unit 230 sends the application destination application of the invited user who has a predetermined relationship with the invited user in the application destination application 20 from the user terminal 100 of the invited user in which the application source application 10 and the application destination application 20 are installed. An invitation process for installing the application source application 10 to the user terminal 100 in which 20 is installed is controlled. As shown in this figure, the control unit 230 includes an application management unit 231, an application list notification unit 232, an invitation application reception unit 233, an invitation application management unit 234, an application inquiry unit 235, an invitation notification unit 236, , An invitation establishment receiving unit 237 and an invitation establishment processing unit 238 are provided.

  The application management unit 231 manages information related to the corresponding application corresponding to the mutual invitation system 500. The information related to the corresponding application managed by the application management unit 231 is set in advance and stored in the application setting storage unit 221 before the corresponding application corresponding to the mutual invitation system 500 can be downloaded from the application store 400, for example.

  Based on the request from the user terminal 100, the application list notification unit 232 refers to the application management unit 231 and transmits the application list of the corresponding application to the user terminal 100. For example, the application list notification unit 232 can apply for an invitation to the application source application 10 for the application source application 10 of the user terminal 100 (for example, the user terminal 100-1) of the invited user (for example, the user X). Send an application list of supported applications.

  The invitation application receiving unit 233 receives the invitation application information transmitted from the user terminal 100. Specifically, the invitation request receiving unit 233 applies the invited user transmitted from the request destination application 20 activated (selected mode is activated) by being selected from the application list in the user terminal 100 of the invited user. Invitation application information for applying to the application 10 is received.

  For example, the invitation request receiving unit 233 is started (started in a specific mode) by being selected from the application list in the user terminal 100 (for example, the user terminal 100-1) of the invited user (for example, the user X). Invitation application information for requesting an invited user (for example, user Y) transmitted from the application 20 to the application source application 10 is received.

  Here, the invitation application information includes, for example, the user ID of the invited user (for example, user X) in the application source application 10, the user ID of the invited user (for example, user X) in the application destination application 20, and the application destination application. 20 includes a user ID of an invited user (for example, user Y) that is a selected user among users having a predetermined relationship (for example, friend relationship). Further, the invitation application information includes the application ID of the application source application 10 and the application ID of the application destination application 20. Then, the invitation application receiving unit 233 supplies the received invitation application information to the invitation application management unit 234.

  The invitation application management unit 234 associates each application ID and user ID included in the invitation application information received by the invitation application reception unit 233 and stores them in the invitation application information storage unit 222 as an invitation application record for management. For example, the invitation application management unit 234 generates a new record corresponding to the invitation application information and stores it in the invitation application information storage unit 222 as an invitation application record.

  The application inquiry unit 235 refers to the invitation application information storage unit 222 on the basis of the inquiry (application inquiry) from the application destination application 20 of the user terminal 100 of the invited user, with respect to the invited user in the application destination application 20. Queries the presence / absence of an invitation application record (record of invitation application information for the invited user). For example, the application inquiring unit 235 includes invited users (for example, the application destination application 20 included in an inquiry (application inquiry) from the user terminal 100 (for example, the user terminal 100-2) of the invited user (for example, the user Y)). , The presence or absence of an invitation application record (invitation application information) for the user ID of user Y) is inquired.

  The invitation notifying unit 236 is a user terminal of the invited user (for example, user Y) when there is an invitation application record (invitation application information) for the invited user (for example, user Y) as a result of the inquiry by the application inquiry unit 235. Invitation notification information based on the invitation application record (invitation application information) is transmitted to the application 20 of the application 100 of the user 100 (for example, the user terminal 100-2). The invitation notification information based on the invitation application record (invitation application information) is invitation notification information including at least a part of information included in the invitation application record (invitation application information).

  The invitation establishment receiving unit 237 is set in advance by the application source application 10 (invited corresponding application) being activated on the user terminal 100 (for example, the user terminal 100-2) of the invited user (for example, the user Y) or the like. The invitation establishment information indicating that the invitation corresponding to the invitation notification information has been established based on the fact that the achievement point has been reached, is sent to the user terminal 100 (for example, the user terminal 100- 2) received from the application source application 10.

  The invitation establishment processing unit 238 performs a predetermined process based on the invitation establishment information received by the invitation establishment receiving unit 237. For example, the invitation establishment processing unit 238 sends invitation establishment notification information for notifying that the invitation to the application source application 10 has been established based on the invitation establishment information received by the management server 200 to the application corresponding to the application source application 10. The data is transmitted to the server 300 (for example, the application server 310 (game A) corresponding to the application source application 10 (game A)).

[Details of invitation processing operations]
Next, with reference to FIG. 9 and FIG. 10, the details of the operation of the invitation process of the mutual invitation system 500 according to the present embodiment will be described. 9 and 10 are flowcharts showing an example of the operation of the invitation process according to the present embodiment. The processing shown in FIGS. 9 and 10 shows a detailed example of the flow of the schematic processing described with reference to FIG.

  First, with reference to FIG. 9, the process which the user terminal 100-1 of the user X who is an invitation user and the management server 200 perform is demonstrated. That is, a detailed example from the process (1) to the process (3) shown in FIG. 3 will be described.

(1) Application list request from the application source application to the management server (user terminal of the invited user)
The SDK 11A of the application source application 10 (game A) installed in the user terminal 100-1 of the user X who is an invited user invites an invitation screen for inviting friends of other games ((a in FIG. 4). ) Is displayed on the display unit 120 (step SA110).

  When an operation (first operation) by the user X is performed on the invitation screen displayed on the display unit 120, the application list acquisition unit 161 of the SDK 11A of the user terminal 100-1 may include some or all of the plurality of corresponding applications. Application list request information for requesting an inviteable application list is transmitted to the management server 200 (REQ11, step SA120). Here, the application list request information includes the application source application ID (ApIDfrom). Here, the application ID of the application source application 10 (game A) is set in the application source application ID (ApIDfrom).

  When the application list notification unit 232 of the management server 200 acquires the application list request information from the user terminal 100-1 (SDK 11A), the application list notification unit 232 refers to the application setting storage unit 221 managed by the application management unit 231 and applies the application list of the corresponding application. Is transmitted to the user terminal 100-1 (SDK11A). For example, in the application list notification unit 232, the application source application 10 (game A) that transmitted the application list request information to the mutual invitation system 500 based on the application source application ID (ApIDfrom) included in the acquired application list request information. Make sure you are participating. In response to a request from the application source application 10 (game A) participating in the mutual invitation system 500, the application list notification unit 232 transmits an application list of the corresponding application (RES11, step SE110).

  Here, the application list that the application list notification unit 232 transmits to the user terminal 100-1 (SDK11A) includes, for example, application IDs (ApIDs) of one or more corresponding applications. The application ID of the corresponding application included in the application list is set in the application ID (ApID) of the one or more corresponding applications.

  Note that the application list notifying unit 232 is a list of corresponding applications excluding the application source application 10 (game A) that transmitted the application list request information based on the application source application ID (ApIDfrom) included in the acquired application list request information. The application list may be transmitted to the user terminal 100-1 (SDK11A). Further, in the application list that the application list notification unit 232 transmits to the user terminal 100-1 (SDK11A), the URL scheme of each corresponding application is associated with the application ID (ApID) of one or more corresponding applications. You may send it.

  Next, the application list acquisition unit 161 of the SDK 11A of the user terminal 100-1 acquires the inviteable application list transmitted from the management server 200 (step SA130). The application list acquisition unit 161 supplies the acquired application list to the presentation unit 168.

  The presentation unit 168 of the SDK 11A of the user terminal 100-1 detects an application installed in the user terminal 100-1 from the corresponding applications included in the application list acquired by the application list acquisition unit 161. For example, the presentation unit 168 detects the corresponding application installed in the user terminal 100-1 using the URL scheme of each corresponding application included in the application list acquired by the application list acquisition unit 161 (step SA140).

  When the corresponding application installed in the user terminal 100-1 is detected from the corresponding applications included in the application list acquired by the application list acquiring unit 161 based on the detection result, the presenting unit 168 Then, at least a part thereof is displayed on the display unit 120 (see the example of the application list screen shown in FIG. 4B, step SA150). In addition, when a corresponding application other than the application source application 10 (game A) installed in the user terminal 100-1 is not detected, the presentation unit 168 displays a message to that effect on the display unit 120. Let

(2) Friend list display of application destination application (user terminal of invited user)
Assume that the application destination application 20 (game B) is selected by an operation (second operation) of the user X with respect to the application list displayed on the display unit 120 of the user terminal 100-1. In this case, the specific mode activation unit 162 of the SDK 11A of the user terminal 100-1 activates the application destination application 20 (game B) in the specific mode (step SA160).
At this time, the specific mode activation unit 162 sets the application source application ID (ApIDfrom) in which the application ID of the application source application 10 (game A) is set, and the user ID of the user X in the application source application 10 (game A). The invitation user ID (Apfrom_UIDfrom) of the applied application source application is notified to the SDK 11B of the application destination application 20 (game B).

  Next, the application 20 (game B) started in the specific mode acquires a user list from the application server 320 (game B). Note that the process of acquiring the user list (the process of steps SB110 and SB120 below) is not a process executed by the SDK 11A but a process executed by the application destination application 20 (game B).

  The application destination application 20 (game B) activated in the specific mode on the user terminal 100-1 requests a user list of users who have a predetermined relationship (for example, friend relationship) with the user X in the application destination application 20 (game B). To send the friend list request information to the application server 320 (game B) (step SB110). Here, the friend list request information includes the user ID of user X in application destination application 20 (game B) notified from SDK 11A to SDK 11B.

  When the application server 320 (game B) acquires the friend list request information from the application destination application 20 (game B) of the user terminal 100-1, the application server 320 (game B) in the application destination application 20 (game B) has a predetermined relationship (for example, The user list of the users who are friends is transmitted to the user terminal 100-1 (application destination application 20 (game B)) (step SD110).

  Application destination application 20 (game B) of user terminal 100-1 acquires a user list from application server 320 (game B) (step SB120). Further, the application destination application 20 (game B) passes the acquired user list to the SDK 11B. Thereby, the user list acquisition unit 163 of the SDK 11B of the user terminal 100-1 acquires the user list acquired by the application destination application 20 (game B).

  Next, the presentation unit 168 of the SDK 11B of the user terminal 100-1 causes the display unit 120 to display at least a part of the users included in the user list acquired by the application destination application 20 (game B) as a friend list. That is, the presentation unit 168 causes the display unit 120 to display a friend list corresponding to a user list of a user who has a predetermined relationship (for example, a friend relationship) with the user X (invited user) in the application destination application 20 (game B). (See the example of the friend list screen shown in FIG. 4C, step SB150).

(3) Application for invitation from application to application to management server (user terminal of invited user)
When user X selects a user (here, user Y) to be invited to application source application 10 (game A) from the friend list displayed on display unit 120 of user terminal 100-1, user terminal 100-1 The invitation application notifying unit 164 of the SDK 11B transmits, to the management server 200, invitation application information for applying to the application source application 10 (game A) with the selected user Y as an invited user (REQ13, step SB160). .

  Here, the invitation application information includes the user ID of the user X (inviting user) in the application source application 10 (game A), the user ID of the user X (inviting user) in the application destination application 20 (game B), and the application. The user ID of the user Y (invited user) in the destination application 20 (game B) is included. The invitation application information includes the application ID of the application source application 10 (game A) and the application ID of the application destination application 20 (game B).

  The invitation request receiving unit 233 of the management server 200 receives the invitation request information transmitted from the user terminal 100-1 (SDK11B). Then, the invitation application receiving unit 233 supplies the received invitation application information to the invitation application management unit 234. The invitation application management unit 234 generates a new record corresponding to the invitation application information received by the invitation application receiving unit 233, and stores the new record in the invitation application information storage unit 222 as an invitation application record (step SE130).

  Here, the new record of the invitation application information stored as the invitation application record in the invitation application information storage unit 222 is set as follows based on the information included in the invitation application information received by the invitation application receiving unit 233. Is done. The application ID of the application source application 10 (game A) is set in the application source application ID (ApIDfrom), and the user X (invitation user) in the application source application 10 (game A) is set in the invitation user ID (Apfrom_UIDfrom) of the application source application. ) Is set. The application ID of the application destination application 20 (game B) is set in the application destination application ID (ApIDto), and the user X (invited user) in the application destination application 20 (game B) is set in the invitation user ID (Apto_UIDfrom) of the application destination application. ) Is set, and the user ID of the user Y (invited user) in the application destination application 20 (game B) is set in the invited user ID (Apto_UIDto) of the application destination application.

  In addition, a flag “0” (invitation application not notified) is set in the status of the invitation application (StatusInvite). Since the invited user ID (Apfrom_UIDto) of the application source application is set after the user Y (invited user) installs the application source application 10 (game A) in the user terminal 100-2, a new record is generated. For example, “null” is set.

  Note that the presentation unit 168 of the SDK 11B of the user terminal 100-1 completes the invitation application indicating that the invitation application for the invited user is completed after the invitation application notification unit 164 transmits the invitation application information to the management server 200. The screen is displayed on the display unit 120 (see the example of the invitation completion screen shown in FIG. 4D).

  Next, the specific mode end unit 165 of the SDK 11B of the user terminal 100-1 ends the application destination application 20 (game B) activated in the specific mode (step SB170). As the application destination application 20 (game B) ends, the display on the display unit 120 of the user terminal 100-1 is displayed on the invitation screen of the application source application 10 (game A) (invitation screen displayed in step SA110). Return to (step SA170). At this time, when the application source application 10 (game A) is in a non-operating state (Not running), a suspended state (Suspended), or a suspended state (Suspended), the application state application 10 (game A) is shifted to an operating state (Active) in the normal mode.

  As described above, the process described so far with reference to FIG. 9 is performed so that the user X (invited user) is in the predetermined relationship (for example, friend relationship) in the application destination application 20 (game B). User) can be applied for an invitation to the application 10 (game A).

  Next, processing executed by the user terminal 100-2 of the user Y who is an invited user and the management server 200 will be described with reference to FIG. That is, a detailed example from the process (4) to the process (7) shown in FIG. 3 will be described.

(4) Application inquiry from application to application to management server (user terminal of invited user)
When the application destination application 20 (game B) installed in the user terminal 100-2 of the user Y who is the invited user is activated in the normal mode, the application destination application 20 (game B) displays the activation screen on the display unit 120. It is displayed (step SB210).

  When the application destination application 20 (game B) is activated in the normal mode on the user terminal 100-2, the inquiry unit 166 of the SDK 11B of the application destination application 20 (game B) invites the invited user to be the user Y (own user). The management server 200 is inquired (application inquiry) for the presence / absence of application information (invitation application record). For example, the inquiry unit 166 is application inquiry information for inquiring whether there is invitation application information (invitation application record) in which the invited user is the user Y (own user), and the application destination application ID (ApIDto) and the application destination application Application inquiry information including the invited user ID (Apto_UIDto) is transmitted to the management server 200 (REQ21, step SB220).

  Here, the application ID of the application destination application 20 (game B) is set in the application destination application ID (ApIDto), and the invited user ID (Apto_UIDto) of the application destination application is a user in the application destination application 20 (game B). A user ID of Y is set.

  When obtaining the application inquiry information from the user terminal 100-2 (SDK11B), the application inquiry unit 235 of the management server 200 refers to the invitation application record stored in the invitation application information storage unit 222, and the invitation application state ( StatusInvite) flag “0” (invitation application not notified), presence / absence of invitation application record (that is, invitation application record for user Y) in application destination application 20 (game B) as an invited user Query. Specifically, the application inquiry unit 235 adds the application destination application 20 to the application destination application ID (ApIDto) in the invitation application record stored in the invitation application information storage unit 222 based on the acquired application inquiry information. Whether there is an invitation application record in which the application ID of (Game B) is set and the user ID of the user Y in the application destination application 20 (Game B) is set in the invited user ID (Apto_UIDto) of the application destination application To inquire.

  As a result of the introduction of the application inquiry unit 235, when there is an invitation application record in which the user Y in the application destination application 20 (game B) is an invited user, the invitation notification unit 236 displays the user Y user terminal 100-2 ( Invitation notification information based on the invitation application record (invitation application information) is transmitted to the SDK 11B) (RES21, step SE210).

  In addition, the invitation application management unit 234 of the management server 200 sends an invitation stored in the invitation application information storage unit 222 when the invitation notification unit 236 transmits invitation notification information to the user terminal 100-2 (SDK11B) of the user Y. The status of the invitation application (StatusInvite) included in the application record is updated from the flag “0” (not notified of invitation application) to the flag “1” (notified of invitation application).

  Here, the invitation notification information includes at least a part of information included in the invitation application record (invitation application information). For example, the invitation notification information includes an invitation ID (InviteID) included in the invitation application record (invitation application information), an application source application ID (ApIDfrom), an application user invitation user ID (Apto_UIDfrom), and an application destination The invitation user name (Apto_NAMEfrom) of the application and the invitation user image URL (Apto_URLfrom) of the application destination application are included.

  Next, the invitation notification acquisition unit 167 of the SDK 11B of the user terminal 100-2 acquires the invitation notification information transmitted from the management server 200. That is, as a result of the inquiry by the inquiry unit 166, the invitation notification acquisition unit 167 has an invitation application information record in which the user ID of the user Y (own user) becomes the user ID of the invited user in the application destination application 20 (game B). In this case, invitation notification information based on the invitation application record (invitation application information) is acquired from the management server 200. (Step SB230).

  When there is an invitation application record in which the user Y is an invited user, the application destination application 20 (game B) of the user terminal 100-2 has an invitation notification indicating that there is an invitation application in which the user Y is an invited user. The startup screen (see the example of the invitation notification screen shown in FIG. 4E) on which the message is displayed is displayed on the display unit 120 (step SB240). This startup screen is the startup screen of the application destination application 20 (game B) displayed on the display unit 120 in step SB210, and is not displayed by the processing of the SDK 11B but by the processing of the application destination application 20 (game B). 120.

  Next, the presentation unit 168 of the SDK 11B of the user terminal 100-2 presents invitation information based on the invitation notification information acquired by the invitation notification acquisition unit 167. For example, the presentation unit 168 displays an invitation information list screen (see the example of the invitation information list screen shown in FIG. 4F) that displays a list of invitation information for which the user Y (own user) is an invited user. 120 is displayed (step SB250).

  Here, in the invitation information displayed on the invitation information list screen, the user name or user image of the invited user is displayed. In the present embodiment, since the invitation user name (Apto_NAMEfrom) and the invitation user image URL (Apto_URLfrom) are included in the invitation notification information, only the SDK 11B process of the user terminal 100-2 can be used to display the invitation user list on the invitation information list screen. It is possible to display a user name or a user image. For example, the example of the invitation information list screen shown in FIG. 4F shows an example in which the user name of the invited user is displayed. The user image of the invited user is associated with the user name of the invited user. May be displayed.

  If the invitation information does not include the user name or user image of the invited user, the user name or user image corresponding to the invitation user ID (Apto_UIDfrom) can be directly or applied from the application server 320, for example. Since it is necessary to obtain the destination application 20 (game B), the processing becomes complicated.

  The presentation unit 168 of the SDK 11B of the user terminal 100-2 is installed in the user terminal 100-2 using a URL scheme when presenting invitation information based on the invitation notification information acquired by the invitation notification acquisition unit 167. Corresponding application may be detected. Then, when it is detected that the application source application 10 (game A) to be invited is installed, the presentation unit 168 of the SDK 11B excludes the corresponding invitation information and displays an invitation information list screen. 120 may be displayed, or information indicating that installation has been completed may be added to the corresponding invitation information, and the invitation information list screen may be displayed on the display unit 120.

(5) Application source application installation (user terminal of invited user)
In the invitation information list screen displayed on the display unit 120, when the user Y who is an invited user performs an operation (third operation) for accepting an invitation to the application 10 (game A) (step SB260), The invitation information management unit 170 of the SDK 11B of the user terminal 100-2 stores at least a part of information included in the invitation notification information corresponding to the accepted invitation information in the terminal storage unit 140 of the user terminal 100 (step SB270). .

  Further, the screen transition unit 169 of the SDK 11B of the user terminal 100-2 accesses the app store 400 and activates an app store that displays a store page where the application source app 10 (game A) can be downloaded (step SB280).

(6) Notification of invitation establishment from the application application to the management server (invited user terminal)
Assume that the application source application 10 (game A) is activated in the normal mode after the application source application 10 (game A) is installed in the user terminal 100-2 based on the invitation application. For example, it is assumed that the user Y downloads the application source application 10 (game A) from the application store activated in step SB280 to the user terminal 100-2 and activates the installed application source application 10 (game A).

  The invitation information management unit 170 of the SDK 11A of the application source application 10 (game A) installed in the user terminal 100-2 acquires the invitation notification information stored in the terminal storage unit 140 (step SA210).

  In user terminal 100-2, user Y plays application source application 10 (game A) to advance the game (step SA220). Then, the application source application 10 (game A) determines whether or not a predetermined achievement point has been reached (step SA230). Note that the processes in step SA220 and step SA230 are not executed by the SDK 11A but executed by the application source application 10 (game A).

  When the predetermined achievement point is reached in accordance with the progress of the application source application 10 (game A) installed and activated on the user terminal 100-2 (step SA230: YES), the application source application 10 (game A) is Then, the information indicating the arrival is transferred to the SDK 11A of the application source application 10 (game A). On the other hand, if the predetermined achievement point has not been reached (step SA230: NO), the progress of the game in the application source application 10 (game A) is continued until the predetermined achievement point is reached.

  When the SDK 11A of the user terminal 100-2 receives information indicating that a predetermined result point has been reached from the application source application 10 (game A), the invitation establishment notification unit 171 of the SDK 11A receives the application source application 10 (game). On the condition that the invitation notification information corresponding to A) is stored in the terminal storage unit 140, invitation establishment information indicating that the invitation corresponding to the invitation notification information has been established is transmitted to the management server 200 ( RE22, step SA240). Here, the invitation establishment information includes, for example, an invitation ID (InviteID) and an invited user ID (Apfrom_UIDto) of the application source application. Invitation ID (InviteID) is set to the invitation ID (InviteID) included in the invitation notification information corresponding to this invitation establishment information. In the invited user ID (Apfrom_UIDto) of the application source application, the user ID of the user Y in the application source application 10 (game A) is set. The predetermined achievement point may include a time when the application source application 10 (game A) is installed (executed) for the first time in the user terminal 100-2.

(7) Invitation completion notification from the management server to the application server of the application originator The invitation establishment receiving unit 237 of the management server 200 establishes the invitation in the application source application 10 (game A) transmitted from the user terminal 100-2 (SDK11A). Information is received (step SE220). In addition, the invitation establishment receiving unit 237 supplies the invitation establishment information received by the invitation establishment receiving unit 237 to the invitation application management unit 234.
Based on the invitation establishment information, the invitation application management unit 234 assigns the invitation source application 10 ((pap_UIDto) to the invited user ID (Apfrom_UIDto) of the application source application included in the invitation application record stored in the invitation application information storage unit 222. The user ID of the user Y in the game A) is set. In addition, the invitation application management unit 234 updates the status of the invitation application (StatusInvite) from the flag “1” (invitation application notified) to the flag “2” (not yet received invitation application completion).

  Next, the invitation establishment processing unit 238 of the management server 200 performs a predetermined process based on the invitation establishment information received by the invitation establishment receiving unit 237. For example, the invitation establishment processing unit 238 establishes an invitation from the user X (inviting user) to the application source application 10 (game A) based on the invitation establishment information received by the management server 200 as the predetermined process. The invitation establishment notification information to notify this is transmitted to the application server 310 (game A) corresponding to the application source application 10 (game A) (REQ23, step SE230). Here, the invitation establishment notification information includes the user ID of the user X (inviting user) in the application source application 10 (game A). In addition, the invitation application management unit 234 updates the status of the invitation application (StatusInvite) from the flag “2” (not yet notified of invitation application completion) to the flag “3” (notification of invitation establishment completed). This flag may be updated when a response notification from the application server 310 (game A) with respect to the notification of the invitation establishment notification information is received.

  The invitation application management unit 234 sets the status of the invitation application (StatusInvite) to the flag “1” (Status Invite) based on the information indicating that the application source application 10 (game A) has been installed instead of the invitation establishment information. It may be updated from flag “2” (notification of invitation application completed) to “2” (not yet notified of invitation application completion). Further, the invitation establishment processing unit 238 receives the application source application 10 (inviting user) from the user X (inviting user) based on the information indicating that the application source application 10 (game A) has been installed received by the invitation establishment receiving unit 237. Invitation establishment notification information for notifying that the invitation to the game A) has been established may be transmitted to the application server 310 (game A) corresponding to the application source application 10 (game A).

  When the application server 310 (game A) receives the invitation completion notification information transmitted from the management server 200 (step SC210), the application server 310 (game A) includes a predetermined reward (for example, incentive) due to the completion of the invitation in the invitation establishment notification information. To the user X in the application source application 10 (game A) indicated by the user ID (step SC220). The predetermined reward is, for example, a virtual currency or an item that can be used by the user X in the application source application 10 (game A).

[Summary]
(1) As described above, the management server 200 (an example of a management device) of the present embodiment is installed by the application source application 10 (an example of the first application) and the application destination application 20 (an example of the second application). From the user terminal 100 (an example of the terminal device) of the invited user (an example of the first user), the application target application 20 (the second application) is in a predetermined relationship (for example, a friend relationship) with the invited user. A control unit 230 that controls an invitation process (an example of a second user) that causes the user terminal 100 in which the application destination application 20 is installed to install the application source application 10 is provided.
The control unit 230 includes an invitation application receiving unit 233, an application inquiry unit 235, and an invitation notification unit 236. The invitation application receiving unit 233 receives, from the user terminal 100 of the inviting user, invitation application information for inviting an invited user who is a selected user among users having a predetermined relationship to the application source application 10. The application inquiry unit 235 makes an inquiry about the presence or absence of invitation application information for the invited user based on the application inquiry from the user terminal 100 of the invited user. The invitation notification unit 236 transmits invitation notification information based on the invitation application information to the user terminal 100 of the invited user when there is invitation request information for the invited user as a result of the inquiry by the application inquiry unit 235. To do. Here, the invitation notification information includes, for example, information such as an invitation ID (InviteID) and token information (for example, an invitation application token) associated with the invitation ID (InviteID). Here, the associated information does not need to be permanently associated, and may be temporary. Further, instead of the invitation ID (InviteID) and the token information, for example, various information indicated by the invitation application record corresponding to the invitation ID (InviteID) may be used.
The token information (for example, invitation request token) associated with the invitation ID (InviteID) is generated by the management server 200, for example. The timing for generating the token information is, for example, when the management server 200 acquires the invitation application information.

  As a result, the management server 200 receives a predetermined relationship with the invited user in the application destination application 20 received from the invited user who uses the user terminal 100 in which the application source application 10 and the application destination application 20 are installed (for example, It is possible to notify the user terminal 100 of the invited user of an invitation application for inviting an invited user who is in a friend relationship) to the application source application 10. Therefore, the mutual invitation system 500 can invite users who have a predetermined relationship (for example, a friend relationship) in another application to another application even between applications whose user information is not compatible. In other words, the mutual invitation system 500 can easily invite a user between applications even if the user information is not compatible.

  Here, the user terminal 100 of the invited user in which the application source application 10 and the application destination application 20 are installed is, for example, the user terminal 100 in which the application source application 10 and the application destination application 20 have been installed and executed. That means. That is, in the user terminal 100 of the invited user, the application destination application 20 has been executed, and the executed application destination application 20 has a predetermined relationship (for example, a friend relationship) with at least one user. Yes. The application source application 10 is executed at least when a user (invited user) who has a predetermined relationship (for example, a friend relationship) in the application destination application 20 makes an invitation application to the application source application 10. In addition, the user terminal 100 in which the application destination application 20 of the invited user who has a predetermined relationship (for example, a friend relationship) with the invited user in the application destination application 20 is installed, for example, the application destination application 20 is installed. The user terminal 100 that has been executed. That is, in the user terminal 100 of the invited user, the application destination application 20 has been executed, and the executed application destination application 20 has at least a predetermined relationship (for example, a friend relationship) with the invited user. .

  For example, the management server 200 (an example of a management device) according to the present embodiment is an invited user who has executed an application source application 10 (an example of a first application) and an application destination application 20 (an example of a second application) ( From the user terminal 100 (an example of the first user) (an example of the first user) to the invited user among the users who are in a predetermined relationship (for example, a friend relationship) with the invited user in the application destination application 20 (the second application) The control part 230 which controls the invitation process for making the user terminal 100 of a user (an example of a 2nd user) introduce the said application origin application 10 is provided. In addition, since the invited user and the invited user have a predetermined relationship in the application destination application 20, the application destination application 20 is executed in the user terminal 100 of the invited user.

As described above, the application source application 10 or the application destination application 20 being executed means, for example, that the application source application 10 or the application destination application 20 has been installed and executed. In this case, the entire program executed by the application source application 10 or the application destination application 20 may be installed in the user terminal 100, or a part of the program is installed in the user terminal 100, and the remaining part of the program is the user. It is good also as a structure performed by apparatuses other than the terminal 100. FIG. For example, the program that executes the application source application 10 or the application destination application 20 installed in the user terminal 100 is only a program that is at least necessary for starting execution of the application source application 10 or the application destination application 20. Also good. The remaining program may be executed by a server device (for example, the application server 300) that can communicate with the user terminal 100 or another terminal device (for example, another user terminal 100).
Moreover, the structure by which all the programs of the application origin application 10 or the application destination application 20 performed by the user terminal 100 are performed by apparatuses other than the user terminal 100 may be sufficient. That is, a program for executing the application source application 10 or the application destination application 20 is not installed in the user terminal 100, but a server device (for example, the application server 300) or other terminal device (for example, the application device 300) that can communicate with the user terminal 100. It may be configured to be executed by another user terminal 100). For example, the application source application 10 or the application destination application 20 being executed on the user terminal 100 means that the application source application 10 or the application source application 10 or This includes the case where the application 20 is executed. In this case, information (for example, display information) indicating a result executed in the server device is displayed on the user terminal 100. That is, the application source application 10 or the application destination application 20 executed by the user terminal 100 may be a so-called cloud type or WEB type application.

  In addition, introducing the application source application 10 to the invited user's user terminal 100 may be causing the user terminal 100 to install a part or all of the program of the application source application 10. When the original application 10 is a so-called cloud-type or WEB-type application, the application source is transmitted to the server device that is a main body that executes the program of the application source application 10 via the communication network according to an instruction from the user terminal 100. Use registration (for example, user registration) may be performed so that the application 10 can be executed. For example, in the above embodiment, in order to introduce the application source application 10 to the invited user's user terminal 100, an example in which a screen on which the application source application 10 can be installed is displayed on the invited user's user terminal 100 will be described. However, instead of this, the use registration screen of the application source application 10 may be displayed on the user terminal 100 of the invited user.

  Moreover, even if there is no application inquiry from the user terminal 100 of the invited user, the management server 200 may transmit invitation notification information based on the invitation request information for the invited user to the user terminal 100 of the invited user. Good. For example, the management server 200 receives the invitation notification information based on the invitation application information for the invited user on the user terminal 100 of the invited user when the application destination application 20 is activated in the user terminal 100 of the invited user. You may transmit to. In addition, the management server 200 may transmit the invitation notification information to the user terminal 100 of the invited user at a predetermined time period or periodically at a predetermined time.

  That is, the control unit 230 may be configured to include at least the invitation application receiving unit 233 and the invitation notification unit 236. The invitation application receiving unit 233 invites the invited user (an example of the second user) among the users who have a predetermined relationship with the invited user (an example of the first user) to the application source application 10 (an example of the first application). Invitation application information to be applied is received from the user terminal 100 of the inviting user. And the invitation notification part 236 transmits the invitation notification information based on the invitation application information with respect to an invited user among the invitation application information which the invitation application reception part 233 received with respect to the user terminal 100 of the said invited user.

  As a result, the management server 200 receives a predetermined relationship with the invited user in the application destination application 20 received from the invited user who uses the user terminal 100 in which the application source application 10 and the application destination application 20 have been executed ( For example, it is possible to notify the invited user's user terminal 100 of an invitation application for inviting an invited user who is in a friend relationship) to the application source application 10. Therefore, the mutual invitation system 500 can invite users who have a predetermined relationship (for example, a friend relationship) in another application to another application even between applications whose user information is not compatible. In other words, the mutual invitation system 500 can easily invite a user between applications even if the user information is not compatible.

  For example, the invitation application receiving unit 233 includes, among the corresponding applications indicated by at least part of the information transmitted by the application list notification unit 232 (an example of the application information notification unit) in the application source application 10 of the user terminal 100 of the invited user. From the application destination application 20 (an example of the second application) started from the application source application 10, the invited user among the users who are in a predetermined relationship (for example, friend relationship) with the invited user is sent to the application source application 10. Receive invitation request information for invitation request. Then, the invitation notification unit 236 transmits the invitation notification information to the application destination application 20 of the user terminal 100 of the invited user. Thus, since the invitation destination application 20 is interposed from the invitation user application source application 10 and the invitation notification information is notified to the invited user application destination application 20, the application source application 10 and the application destination application 20 are notified. Thus, it is possible to easily invite a user even between applications whose user information is not compatible. In this case, the invitation notification information can be notified only to the invited user without using the social media used in the real world, so that it is possible to prevent unrelated users from being invited. In addition, if you use a messenger app (email software or chat) used in the real world, you can notify the invitation notification information only to the invited user. In this case, the destination in the user's messenger app Since it is not necessary to know (email address or account), it is possible to maintain a predetermined relationship closed by an application (virtual society).

In addition, as demonstrated in the said embodiment, the management server 200 inquires the presence or absence of the invitation application information with respect to an invited user based on the application inquiry from the user terminal 100 of an invited user (an example of a 2nd user). An application inquiry unit 235 may be provided. In this case, when the invitation notifying unit 236 has the invitation request information for the invited user as a result of the inquiry by the application inquiry unit 235, the invitation notification based on the invitation request information is sent to the user terminal 100 of the invited user. Send information.
Thereby, the management server 200 can notify the invited user's user terminal 100 of the invitation application from the invited user when receiving the application inquiry from the user terminal 100 of the invited user.

(2) The user terminal 100 (an example of a terminal device) is the application of the application source application 10 (an example of a first application) and the application destination application 20 (an example of a second application) installed in the user terminal 100. With respect to another user terminal 100 (an example of a terminal device) in which the application destination application 20 of another user who has a predetermined relationship with the own user in the destination application 20 is installed, the application source application 10 (first application) It is a terminal device which can communicate with the management server 200 which controls the invitation process to install.

  Accordingly, the user terminal 100 has a predetermined relationship (for example, a friend relationship) with the own user (an example of an invited user) in the application destination application 20 activated in the specific mode based on an operation in the application source application 10. An invitation application for inviting another user (an example of an invited user) to the application 10 can be transmitted to the management server 200. Then, the invitation request is notified to the user terminal 100 of the other user via the management server 200. Therefore, the mutual invitation system 500 can invite users who have a predetermined relationship (for example, a friend relationship) in another application to another application even between applications whose user information is not compatible. In other words, the mutual invitation system 500 can easily invite a user between applications even if the user information is not compatible.

(3) The user terminal 100 (an example of the own terminal device) includes a specific mode activation unit 162 (an example of an activation unit), a user list acquisition unit 163, and an invitation application notification unit 164.
In the corresponding application installed in the user terminal 100, the specific mode activation unit 162 activates another corresponding application installed in the user terminal 100 in the specific mode (performs a specific function).
The user list acquisition unit 163 obtains a user list of users who are in a predetermined relationship (for example, a friend relationship) with the user in the application 20 (an example of an application) that is operating in a specific mode (executing a specific function). get. This user list is managed by, for example, the application server 300 (an example of a server device) corresponding to the application destination application 20, and the user list acquisition unit 163 receives the user list from the application server 300 corresponding to the application destination application 20. To get.
The invitation application notifying unit 164 activates the application destination application 20 in the specific mode for the user (an example of the invited user) selected from the user list acquired by the user list acquisition unit 163 (of the application destination application 20). Invitation application information for applying for an invitation to a corresponding application (for example, the application source application 10) that has executed a specific function is transmitted to the management server 200 (an example of a management apparatus).

The above-described user list is an example of information indicating a user, and the form of the information may be any form. For example, each structure of the user list acquisition part 163 with which the user terminal 100 is provided, and the invitation application notification part 164 can be described as follows.
The user list acquisition unit 163 (an example of a user information acquisition unit) has a predetermined relationship (for example, a friend relationship) with the user in the application destination application 20 (an example of an application) that is operating in a specific mode (execution of a specific function). ) (For example, a user list) indicating the users in () is acquired. The invitation application notification unit 164 activates the application 20 in a specific mode among users indicated by information (for example, a user list) indicating users in a predetermined relationship acquired by the user list acquisition unit 163 (application) Invite user information invited to the application source application 10 (an example of an application) that has executed a specific function of the destination application 20 is sent to the management server 200 invitation application information for applying for an invitation to the application source application 10. To do. As described above, the invitation application information is not transmitted from the application source application 10 of the invited user to the management server 200, but the application destination application 20 is interposed (activated) from the application source application 10 to the management server 200. Since the transmission is made, the user can be easily invited even between applications whose user information is not compatible, such as the application source application 10 and the application destination application 20.

  Accordingly, the user terminal 100 has a predetermined relationship (for example, a friend relationship) with the own user (an example of an invited user) in the application destination application 20 activated in the specific mode based on an operation in the application source application 10. An invitation application for inviting another user (an example of an invited user) to the application 10 can be transmitted to the management server 200. Then, the invitation request is notified to the user terminal 100 of the other user via the management server 200. Therefore, the mutual invitation system 500 can invite users who have a predetermined relationship (for example, a friend relationship) in another application to another application even between applications whose user information is not compatible. In other words, the mutual invitation system 500 can easily invite a user between applications even if the user information is not compatible.

(4) The management server 200 includes an application management unit 231 that manages information related to the corresponding application corresponding to the mutual invitation system 500. That is, the application management unit 231 manages information regarding each of a plurality of corresponding applications including the application source application 10 (an example of a first application) and the application destination application 20 (an example of a second application). In addition, the management server 200 refers to the application management unit 231 and transmits an application list of compatible applications that can be applied for invitation to the application source application 10 to the user terminal 100 of the invited user (an example of the first user). An application list notification unit 232 is provided. For example, the application list notification unit 232 transmits the application list to the application source application 10 of the user terminal 100 of the invited user.

  Here, the application list described above may be information indicating at least one corresponding application among the corresponding applications corresponding to the mutual invitation system 500, and the form of the information may be any form. For example, the above-described application list may be data including information (for example, an application name, an application icon image, an application ID, etc.) indicating at least one corresponding application, or information indicating at least one corresponding application. Data of an application list screen displayed as display information may be used, or information indicating a link destination of the application list screen may be used. On the application list screen, information indicating a plurality of corresponding applications may be displayed in a vertical (vertical) direction (so-called list display) (see FIG. 4B), or in the horizontal direction (horizontal). Direction), or may be displayed in a grid (lattice) in the vertical and horizontal directions (so-called grid display).

  The application that can be applied for invitation may be a corresponding application corresponding to the mutual invitation system 500 (that is, an application for which the application management unit 231 manages information). For example, the application management unit 231 manages information indicating each of a plurality of applications including the application source application 10 (an example of a first application) and the second application. Then, the application list notification unit 232 (an example of the application information notification unit) invites at least a part (for example, an application list) of information managed by the application management unit 231 as the application list (an example of information indicating an application). It transmits with respect to the user terminal 100 of a user (an example of a 1st user).

  The application that can be applied for invitation may be a compatible application for which invitation application is not prohibited in the management server 200 among the compatible applications corresponding to the mutual invitation system 500. For example, the application management unit 231 may manage information indicating each of a plurality of corresponding applications and information regarding prohibition of an invitation application set for each of the corresponding applications. Then, the application list notification unit 232 (an example of the application information notification unit) refers to the application management unit 231 to determine whether or not an invitation application to the application source application 10 is possible (for example, prohibition of invitation application is set). May be determined), and an application list (an example of information indicating an application) indicating an application that can be applied for invitation may be transmitted to the user terminal 100 of the invited user (an example of the first user). As described above, the processing in the case where the corresponding application for which the invitation application is not prohibited is set as an application that can accept the invitation application will be described later in the second embodiment.

In addition, the user terminal 100 (an example of the own terminal device) includes an application list acquisition unit 161.
The application list acquisition unit 161 acquires, from the management server 200, an application list including a part or all of a plurality of corresponding applications corresponding to the invitation process. For example, the application list acquisition unit 161 includes a plurality of corresponding applications corresponding to the mutual invitation system 500 (an example of an invitation process) based on a first operation in the application source application 10 (an example of an application) operating in the normal mode. A part or all of the application list is acquired from the management server 200.
Then, the presentation unit 168 (an example of a first presentation unit, an example of an application list presentation unit) presents a corresponding application installed in the user terminal 100 from the application list acquired by the application list acquisition unit 161.

  Thereby, the management server 200 can manage information related to the corresponding application corresponding to the mutual invitation system 500. Moreover, since the management server 200 transmits the application list of the corresponding application to the user terminal 100 of the inviting user, and the user terminal 100 acquires and presents this application list, the inviting user selects the corresponding application for selecting the invited user. It is possible to easily select from the application list.

As described above, the application list may be information indicating one or a plurality of corresponding applications among the corresponding applications corresponding to the mutual invitation system 500, and the form of the information may be any form. .
That is, the application list acquisition unit 161 (an example of an application information acquisition unit) receives information indicating at least one application (an example of one or a plurality of applications) from the management server 200 among a plurality of corresponding applications corresponding to the invitation process. get. For example, the application list acquisition unit 161 acquires information indicating one or a plurality of corresponding applications from the management server 200 based on the first operation in the application source application 10 (an example of an application) operating in the normal mode.
Then, the presentation unit 168 (an example of a first display control unit) indicates information indicating the corresponding application installed in the user terminal 100 among the information indicating one or more corresponding applications acquired by the application list acquisition unit 161. Is displayed on the display unit 120.

(5) The application list acquisition unit 161 of the user terminal 100 (an example of the own terminal device) acquires a URL scheme corresponding to each of the corresponding applications included in the application list together with the application list. And the presentation part 168 (an example of a 1st presentation part, an example of an application list presentation part) detects the corresponding application installed in the user terminal 100 using the acquired URL scheme, and shows it to the own user.

  In addition, although the example which detects the corresponding application installed in the user terminal 100 using URL scheme was demonstrated, it is not restricted to this. For example, when the OS can acquire information indicating the corresponding application already installed in the user terminal 100, the OS is installed in the user terminal 100 using the information indicating the corresponding corresponding application already installed. Other applications may be detected.

  For example, the presentation unit 168 (an example of the first display control unit) is acquired by the application list acquisition unit 161 (an example of the application information acquisition unit) using a function included in the user terminal 100 (an example of the own terminal device). Alternatively, the corresponding application installed in the user terminal 100 may be detected from the corresponding applications indicated by the information indicating one or a plurality of corresponding applications, and information indicating the detected corresponding application may be displayed on the display unit 120.

  Thereby, the user terminal 100 can present only the corresponding application installed in the user terminal 100 from the corresponding application list acquired from the management server 200 (display on the display unit 120).

  Note that the presentation unit 168 (an example of the first display control unit) is activated on the user terminal 100 of the inviting user when displaying information indicating the corresponding application installed in the user terminal 100 of the inviting user on the display unit 120. Information indicating the corresponding application that has been determined to have been started on the user terminal 100 of the invited user by determining whether or not the corresponding application is a corresponding application installed in the user terminal 100 of the invited user You may display on the display part 120 as information which shows an application.

Moreover, the management server 200 is good also considering the corresponding application installed in the user terminal 100 of an inviting user among the corresponding applications corresponding to the mutual invitation system 500 as an application which can perform invitation application. For example, when the information indicating the corresponding application installed in the user terminal 100 is transmitted from the user terminal 100 to the management server 200, the management server 200 recognizes the application installed in the user terminal 100. Good.
For example, the application management unit 231 includes information on each of a plurality of corresponding applications including the application source application 10 (an example of a first application) and an application destination application 20 (an example of a second application) (respectively indicate a plurality of corresponding applications). Information and information indicating whether or not the user terminal 100 is installed) may be managed. Then, the application list notification unit 232 (an example of the application information notification unit) refers to the application management unit 231 and determines whether or not an invitation request to the application source application 10 is possible (for example, whether it is installed). ) And an application list (an example of information indicating an application) indicating an application that can be applied for invitation may be transmitted to the user terminal 100 of the invited user (an example of the first user).
Thereby, the management server 200 can notify only the corresponding application installed in the user terminal 100 of the inviting user among the corresponding applications corresponding to the mutual invitation system 500 to the user terminal 100 of the inviting user.

  In addition, when the management server 200 can acquire information indicating a corresponding application that has been started on the user terminal 100 of the invited user, the management server 200 uses the user terminal 100 of the invited user among the corresponding applications corresponding to the mutual invitation system 500. The corresponding application that has been activated may be an application that can be applied for invitation as the corresponding application installed in the user terminal 100 of the invited user.

(6) The specific mode activation unit 162 (an example of the activation unit) of the user terminal 100 performs the second operation from the corresponding applications presented by the presentation unit 168 (an example of the first presentation unit, an example of the application list presentation unit). First user information corresponding to the invited user (an example of the user) in the application source application 10 (an example of the application) operating in the normal mode with respect to the application destination application 20 that is the corresponding application selected based on , The selected application application 20 (an example of an application) is activated in a specific mode so that the management server 200 can be notified of the user ID (an example of identification information). In this way, by starting the application 20 in the specific mode, it can be different from the case where the user starts for the purpose of using the corresponding application, and a specific function among the functions of the corresponding application is called. Is possible.

  That is, the specific mode activation unit 162 (an example of the activation unit) is a corresponding application indicated by information indicating one or more corresponding applications displayed on the display unit 120 by the presentation unit 168 (an example of the first display control unit). Application destination application 20 (an example of the second application) selected based on the second operation is started in the specific mode.

The specific mode (an example of the specific function) described above is the user ID (an example of identification information) of the invited user (an example of the own user) in the application destination application 20 (an example of the second application) that has executed the specific mode. By transmitting to the application server 320 (an example of a server device) corresponding to the application destination application 20, a user list of users who are in a predetermined relationship (for example, a friend relationship) with the invited user in the application destination application 20 (predetermined It may have a function of acquiring an example of information indicating a user in a relationship, an example of predetermined relationship user information.
Thereby, the user terminal 100 can acquire the information of the user who is in a predetermined relationship (for example, friend relationship) with the invited user in the application destination application 20 from the application source application 10, and the user is regarded as the invited user. It is possible to invite to the application source application 10.

(7) The invitation application notifying unit 164 includes information (for example, a user ID (identification)) corresponding to the invited user (an example of the own user) in the application source application 10 (an application that executes a specific function for another application). Invitation application information further including information)) is transmitted to the management server 200.

  Note that the information corresponding to the invited user only needs to be associated with the invitation application information and may not be included in the invitation application information. For example, the invitation application notifying unit 164 includes a user ID (an example of identification information) corresponding to an invited user (an example of the own user) in the application source application 10 (an example of an application that executes a specific function for another application). , An example of information corresponding to the inviting user) may be transmitted to the management server 200 with further associated invitation request information.

  For example, the invitation application notification unit 164 includes a user ID (an example of identification information, an example of first user information) corresponding to an invited user (an example of the own user) in the application source application 10 (an example of the first application), Invitation application information associated with a user ID (an example of identification information, an example of second user information) corresponding to the invited user may be transmitted to the management server 200.

  Thereby, the user terminal 100 notifies the management server 200 of information (for example, user ID (identification information)) corresponding to the invited user in the application source application 10 via the application destination application 20 activated in the specific mode. Can do.

(8) The specific mode activation unit 162 (an example of the activation unit) has an application ID (an example of the application) of the application source application 10 (an example of the application) operating in the normal mode with respect to the application destination application 20 (an example of the selected application). The application application 20 may be activated in a specific mode so that application information indicating an example of identification information can be further notified. Then, the invitation application notification unit 164 includes invitation information that further includes application information indicating the application ID of the application source application 10 that is operating in the normal mode (an example of an application that has executed a specific function with respect to another application). May be transmitted to the management server 200.

  That is, the specific mode (specific function) includes the application ID (an example of identification information) of the application source application 10 (an example of application) that has executed the specific mode, and the invited user in the application source application 10 that has executed the specific mode. You may further have the function to notify the management server 200 of user ID (an example of identification information) of (an example of a self-user).

  Note that the application information indicating the application ID only needs to be associated with the invitation request information, and may not be included in the invitation request information. For example, the invitation application notifying unit 164 has an application ID (identification information) of the application source application 10 (an example of the first application, an example of an application that has executed a specific function with respect to another application) operating in the normal mode. For example, invitation request information associated with an example of information indicating the first application) may be transmitted to the management server 200.

  Thereby, the user terminal 100 can notify the management server 200 of the application ID of the application source application 10 (that is, the corresponding application to invite the invited user) via the application destination application 20 activated in the specific mode. . Therefore, the management server 200 can specify the corresponding application to which the invited user is invited by the application ID of the application source application 10.

(9) The invitation request notification unit 164 manages invitation request information including information (for example, user ID (an example of identification information)) corresponding to the invited user (an example of the selected user) in the application destination application 20. 200 may be transmitted.

  In addition, the information corresponding to the invited user (an example of the invited user) may be associated with the invitation request information and may not be included in the invitation request information. For example, the invitation application notification unit 164 transmits invitation application information associated with information (for example, user ID (an example of identification information)) corresponding to the invited user in the application 20 to the management server 200. Also good.

  Thereby, the user terminal 100 can notify the management server 200 of the user ID of the invited user in the application destination application 20, and therefore the management server 200 identifies the invited user based on the user ID of the invited user. And the user terminal 100 of the invited user can be specified.

(10) The invitation application notification unit 164 includes information (for example, user ID (an example of identification information)) corresponding to the user in the application destination application 20 (an example of an application that is executing a specific function), and the application destination application. Invitation request information including information (for example, user ID) corresponding to the invited user (an example of the selected user) in 20 may be transmitted to the management server 200.

  Note that the information corresponding to the user and the information corresponding to the invited user in the application to be applied 20 need only be associated with the invitation application information, and may not be included in the invitation application information. For example, the invitation application notifying unit 164 includes information (for example, user ID (an example of identification information)) corresponding to the user in the application destination application 20 (an example of an application that is executing a specific function), and the application destination application 20. Invitation request information associated with information (for example, a user ID) corresponding to the invited user in may be transmitted to the management server 200.

  Thereby, the user terminal 100 can further notify the user ID of the own user (an example of an invited user) in the application destination application 20 to the management server 200. Therefore, the management server 200 uses the user ID of the invited user, The user terminal 100 of the invited user can be notified of who the invitation application is from.

(11) Information corresponding to the invited user (an example of the first user) in the application source application 10 (an example of the first application) included in the invitation application information is applied to the application destination application 20 (the first application) at the user terminal 100 of the invited user. 2 application) is acquired directly from the application 10 and indirectly through the terminal storage unit 140 (an example of a storage unit) of the user terminal 100. Here, the information corresponding to the inviting user may be information that can identify the inviting user by the management server 200, such as a user ID (an example of identification information) or token information associated with the user ID (for example, an inviter token). That's fine. Thereby, the management server 200 can specify from whom the invitation application received from the application 20 (second application) is the invitation application.
The token information (for example, invitee token) associated with the user ID is generated by the management server 200, for example. The timing for generating the token information is, for example, predetermined information (for example, the selected application) from the application source application 10 when the management server 200 acquires the application list request information or until the invitation application information is acquired. This is when the information of the destination application 20 is acquired.

  In addition, the information corresponding to the invitation user in the application origin application 10 should just be linked | related with invitation application information, and does not need to be contained in the said invitation application information. For example, information corresponding to the invited user (an example of the first user) in the application source application 10 (an example of the first application) associated with the invitation application information is the application destination application 20 ( An example of the second application may be acquired directly from the application source application 10 or indirectly via the terminal storage unit 140 (an example of a storage unit) of the user terminal 100.

(12) The user terminal 100 includes a specific mode end unit 165 that ends the application 20 (an example of the selected application) started in the specific mode after the invitation application notification unit 164 transmits the invitation application information. .

  Thereby, the user terminal 100 can terminate the application destination application 20 activated in the specific mode after making an invitation application from the application destination application 20 activated in the specific mode. As described above, the user terminal 100 is able to specify a specific application destination application 20 that is temporarily started without making the inviting user aware of the series of operations of the inviting user with respect to the applying source application 10 operating in the normal mode. The invited user can be selected using the function.

(13) For example, the presenting unit 168 (an example of the user list presenting unit) of the user terminal 100 causes at least a part of the user list acquired by the user list acquiring unit 163 to execute the application source application 10 (specific function). It is presented as a user list of users who are candidates for invitation to an example of an application.

  In addition, the presentation unit 168 presents the user list to the invited user by causing the display unit 120 to display a user list of users who are invitation candidates, for example. For example, the presentation unit 168 (an example of the third display control unit) is at least one of the user lists (an example of information indicating users having a predetermined relationship) acquired by the user list acquisition unit 163 (an example of the user information acquisition unit). Are displayed on the display unit 120 as a user list of users who are candidates for invitation to the application 10 (an example of information indicating users who are candidates to be invited to an application that has executed a specific function).

  Accordingly, by executing a specific function of the application destination application 20 based on an operation in the application source application 10, the user list in the application destination application 20 that is a candidate for invitation to the application source application 10 is displayed on the user terminal 100. Can be displayed.

(14) At this time, the presentation unit 168 (an example of the user list presentation unit) displays the user list display screen including at least a part of the acquired user list as the application source application 10 (the application that has executed the specific function). For example, the display screen displayed on the display unit 120 is switched to be displayed.

  For example, the presentation unit 168 (an example of a third display control unit) displays a user list (an example of information including at least a part of information indicating users having a predetermined relationship) including at least a part of the acquired user list. The screen is displayed so as to be switched from the display screen displayed on the display unit 120 by the application source application 10 (an example of an application that has executed a specific function).

  As described above, the user terminal 100 switches the display between the display screen in the application source application 10 operating in the normal mode and the display screen in the application destination application 20 for selecting the invited user. It can be done without being aware of the switching of applications.

(15) The presentation unit 168 (an example of the second presentation unit, an example of the invitation information presentation unit) transmits the invitation application information to the management server 200 after the invitation application notification unit 164 transmits the application source application 10 (specific The display of the display screen of the user list displayed on the display unit 120 is terminated so as to switch to the display screen displayed according to an example of the application that executed the function.

  For example, the presentation unit 168 (an example of a third display control unit) transmits the invitation application information to the management server 200 after the invitation application notification unit 164 transmits the application source application 10 (the application that has executed a specific function). The display of the display screen of the user list (an example of information including at least a part of information indicating a user having a predetermined relationship) displayed on the display unit 120 is terminated so as to switch to the display screen displayed according to (example). .

  As described above, the user terminal 100 switches the display between the display screen in the application source application 10 operating in the normal mode and the display screen in the application destination application 20 for selecting the invited user. It can be done without being aware of the switching of applications. As a result, the user terminal 100, to the user who finished the invitation application, continue to be able to use an application based on application 10, for example, to the user, so as not to give rise to advance in stopping the use of the application destination application 20 Can be.

(16) The invitation application receiving unit 233 of the management server 200 is the application application 20 activated by being selected from the application list in the user terminal 100 of the invited user (an example of the first user) (an example of the second application). To receive invitation request information.
Here, the invitation application information includes information corresponding to the invited user in the application source application 10 (an example of the first application) and information corresponding to the invited user (an example of the second user) in the application destination application 20. ing.
The information corresponding to the invited user is information that can identify the invited user on the management server 200, such as a user ID (an example of identification information) or token information associated with the user ID (for example, an inviter token). Good. Further, when the information corresponding to the invited user is token information, not only the invited user but also the application source application 10 may be identified from the token information.
The information corresponding to the invited user may be information that can identify the invited user by the management server 200, such as a user ID or token information associated with the user ID.
The management server 200 includes an invitation application management unit 234 that associates each application ID and user ID included in the invitation application information and manages them as an invitation application record. That is, the invitation application management unit 234 of the management server 200 manages the invitation application record corresponding to the invitation application information.

  Further, the invitation application information may include a user ID (an example of identification information) of an invited user (an example of the first user) in the application destination application 20 (an example of the second application). In addition, when the communication session between the user terminal 100 (SDK11) and the management server 200 is established, the user (invitation user in the application destination application 20) that transmits the invitation application information is the information related to the communication session. Since information can be specified from (for example, session information), information that can be specified by session information, such as invited user information in the application 20 for application in the invitation request information, may not be included in the invitation request information. The information that can be specified by the session information is not limited to the invitation request information, but is also the same for other information.

  Thereby, the management server 200 can acquire the invitation request information transmitted from the user terminal 100 of the invited user and manage it as an invitation request record. Moreover, the management server 200 specifies the invited user in the application source application 10, the invited user in the application destination application 20, and the invited user in the application destination application 20 based on the user ID included in the acquired invitation application information. Can do.

In the above embodiment, the example in which the invitation application information includes information corresponding to the invited user in the application source application 10 and information corresponding to the invited user in the application destination application 20 has been described. It is not limited. For example, the information corresponding to the invited user in the application source application 10 and the information corresponding to the invited user in the application destination application 20 may be associated with the invitation application information, and either one is not included in the invitation application information. Both of them may not be included in the invitation request information.
For example, the invitation application receiving unit 233 includes invitation request information, information corresponding to the invited user (an example of the first user) in the application source application 10 (an example of the first application), and the application destination application 20 (an example of the second application). ) May be acquired in association with information corresponding to the invited user (an example of the second user). And the invitation application management part 234, the invitation application information which the invitation application reception part 233 acquired in association, the information corresponding to the invited user in the application origin application 10, and the information corresponding to the invited user in the application destination application 20 , May be managed as invitation request records.

Further, the invitation application receiving unit 233 may not acquire the invitation application information as information corresponding to the invited user in the application source application 10. For example, when not inviting the invited user to the invited user, or when not giving a reward to the invited user when the invitation is established, the management server 200 uses the application source application 10. There is no need to acquire information corresponding to the invited user, and it is only necessary to transmit the acquired invitation notification information to the user terminal 100 to the invited user.
For example, the invitation application receiving unit 233 may acquire the invitation application information in association with information corresponding to the invited user (an example of the second user) in the application destination application 20 (an example of the second application). Then, the invitation application management unit 234 may manage the invitation application information acquired by associating with the invitation application receiving unit 233 and the information corresponding to the invited user in the application destination application 20 as an invitation application record.

(17) The application inquiry unit 235 of the management server 200 is configured to apply the application destination application based on the application inquiry from the application destination application 20 (an example of the second application) of the user terminal 100 of the invited user (an example of the second user). 20, the presence / absence of an invitation application record for the invited user is inquired. For example, the application inquiry part 235 inquires about the presence or absence of the invitation application record corresponding to the information corresponding to the invited user in the application destination application 20 included in the application inquiry from the user terminal 100 of the invited user. As an example, the application inquiry part 235 inquires about the presence or absence of the invitation application record corresponding to the user ID (an example of identification information) of the invited user in the application destination application 20 included in the application inquiry.

  In addition, the information (for example, user ID) corresponding to the invited user of application destination application 20 should just be linked | related with the application inquiry, and does not need to be contained in the said application inquiry. For example, the application inquiry unit 235 includes information corresponding to the invited user in the application destination application 20 (an example of the second application) associated with the application inquiry from the user terminal 100 of the invited user (an example of the second user) ( For example, the presence / absence of the invitation application record corresponding to the user ID) may be inquired.

  Thereby, the management server 200 can inquire whether the invitation application record with respect to the said invited user is managed based on the application inquiry from the user terminal 100 of the invited user.

(18) The user terminal 100 receives information (for example, user ID (an example of identification information)) corresponding to the own user in the application destination application 20 (an example of the second application) operating in the normal mode to the invited user. An inquiry unit 166 that inquires of the management server 200 about presence / absence of invitation application information serving as corresponding information (an example of second user information, for example, a user ID) is provided.
And the invitation notification acquisition part 167 of the user terminal 100 is the invitation which the information (for example, user ID) corresponding to the own user becomes the information (for example, user ID) corresponding to the invited user as a result of the inquiry part 166 inquiring. When there is application information, invitation notification information based on the invitation application information is acquired from the management server 200.

  That is, the invitation notification acquisition unit 167 of the user terminal 100 is, for example, an invited user (selected) included in the invitation application information transmitted from the other user terminal 100 (an example of another terminal device) to the management server 200. Based on the user ID (an example of identification information) of the user (an example of the user), the user (an example of the invited user) who has been invited to the application source application 10 (an example of an application that has executed a specific function) Invitation notification information based on the invitation application information is acquired from the management server 200. In addition, the presentation unit 168 (an example of the second presentation unit, an example of the invitation information presentation unit) of the user terminal 100 presents invitation information based on the invitation notification information acquired by the invitation notification acquisition unit 167.

  In addition, the information corresponding to the invited user (an example of the invited user) may be associated with the invitation request information and may not be included in the invitation request information. For example, the invitation notification acquisition unit 167 of the user terminal 100 is the invited user (invited user) associated with the invitation application information transmitted from the other user terminal 100 (an example of another terminal device) to the management server 200. Based on the user ID (an example of identification information) of the user (an example of an invited user) that is applied to the application source application 10 (an example of an application that has executed a specific function) is the own user. Invitation notification information based on the invitation application information may be acquired from the management server 200.

  That is, the invitation notification acquisition unit 167 includes the invited user (an example of an invited user) among the invitation application information transmitted from the other user terminal 100 (an example of another terminal device) to the management server 200. Invitation notification information based on invitation application information to be a user may be acquired from the management server 200. Then, the presentation unit 168 (an example of a second display control unit) causes the display unit 120 to display invitation information based on the invitation notification information acquired by the invitation notification acquisition unit 167, for example.

  Thereby, the user terminal 100 acquires and notifies the invitation notification information based on the invitation application record when the invitation application record in which the user is an invited user is managed by the management server 200 (on the display unit 120). Display). That is, in the mutual invitation system 500, the invited user is notified of the invitation application from the invited user.

(19) The user terminal 100 can install the application source application 10 (example of application) indicated by the invitation information based on the third operation on the invitation information presented by the presentation unit 168 (example of the second presentation unit). A screen transition unit 169 that transitions to a screen is provided.

  For example, the screen transition unit 169 is configured to apply the application source application 10 (application of the application) indicated by the invitation information based on the third operation on the invitation information displayed on the display unit 120 by the presentation unit 168 (an example of the second display control unit). Transition to a screen that can be installed.

  Thereby, when the invitation information based on the invitation notification information acquired from the management server 200 is accepted, the user terminal 100 provides a special store page for the user to install the application source application 10 corresponding to the accepted invitation information. It can be displayed automatically without any operation.

(20) The user terminal 100 is included in the invitation notification information corresponding to the invitation information in which the third operation is performed among the invitation information presented by the presentation unit 168 (an example of the second presentation unit, an example of the invitation information presentation unit). An invitation information management unit 170 that stores at least a part of information stored in the terminal storage unit 140 (an example of the storage unit) of the user terminal 100 (an example of the own terminal device).

Note that the invitation information management unit 170 may store at least a part of information associated with the invitation notification information in the terminal storage unit 140 instead of at least a part of the information included in the invitation notification information.
For example, the invitation information management unit 170 associates with the invitation notification information corresponding to the invitation information for which the third operation is performed among the invitation information displayed on the display unit 120 by the presentation unit 168 (an example of the second display control unit). The at least part of the information may be stored in the terminal storage unit 140 (an example of the storage unit) of the user terminal 100 (an example of the own terminal device).

  Thereby, the user terminal 100 stores the invitation notification information corresponding to the accepted invitation information, so that when the application source application 10 corresponding to the invitation information is installed, the installed application source It can be specified that the application 10 has been applied for invitation.

(21) In the user terminal 100, the application source application 10 (an example of an application that executes a specific function) corresponding to any of the invitation information presented by the presentation unit 168 (an example of the invitation information presentation unit) is a user. An invitation establishment notification unit 171 that transmits invitation establishment information corresponding to the invitation information to the management server 200 when installed in the terminal 100 (an example of the own terminal device) and a predetermined condition is satisfied is provided. . This predetermined condition may include execution (startup) for the first time after the application source application 10 is installed.

  For example, the invitation establishment notification unit 171 executes the application source application 10 (executes a specific function) corresponding to any of the invitation information displayed on the display unit 120 by the presentation unit 168 (an example of the second display control unit). When the user application 100 is installed on the user terminal 100 (an example of the own terminal device) and a predetermined condition is satisfied, invitation establishment information corresponding to the invitation information is transmitted to the management server 200.

  For example, the invitation establishment notification unit 171 stores the application source application 10 (in the terminal storage unit 140 of the user terminal 100 in a case where a predetermined condition is satisfied in the application source application 10 (an example of an application) operating in the normal mode. The invitation establishment information corresponding to the invitation notification information is transmitted to the management server 200 on the condition that at least a part of the information included in the invitation notification information corresponding to the example of the operating application) is stored.

  Note that, as described above, the invitation information management unit 170 performs the third operation of the invitation information displayed on the display unit 120 by the presentation unit 168 (an example of the second display control unit, an example of the invitation information presentation unit). At least a part of information associated with the invitation notification information corresponding to the invited invitation information may be stored in the terminal storage unit 140 (an example of the storage unit) of the user terminal 100 (an example of the own terminal device). In this case, the invitation establishment notification unit 171 stores the application source in the terminal storage unit 140 of the user terminal 100 when a predetermined condition is satisfied in the application source application 10 (an example of the first application) operating in the normal mode. The invitation establishment information corresponding to the invitation notification information may be transmitted to the management server 200 on condition that at least a part of the information associated with the invitation notification information corresponding to the application 10 is stored.

  Thereby, the user terminal 100 notifies the management server 200 that the invitation has been established by the invitation application by the invited user installing and using the application source application 10 based on the invitation request from the invited user. be able to. Here, if the timing at which the invitation establishment information is transmitted to the management server 200 is a case where the application source application 10 satisfies a predetermined condition after using the application source application 10, the application source application 10 simply The conditions for accepting invitations can be removed if they are installed but not used.

(22) The management server 200 includes an invitation establishment receiving unit 237 and an invitation establishment processing unit 238. The invitation establishment receiving unit 237 establishes an invitation corresponding to the invitation notification information based on activation of the application source application 10 (an example of the first application) on the user terminal 100 of the invited user (an example of the second user). Invitation establishment information indicating that it has been received is received from the user terminal 100 of the invited user. For example, the invitation establishment receiving unit 237 receives invitation establishment information from the application source application 10 (an example of the first application) of the user terminal 100 of the invited user.
The invitation establishment processing unit 238 performs a predetermined process based on the invitation establishment information received by the invitation establishment receiving unit 237.

  Thereby, the management server 200 gives the predetermined reward (for example, incentive) with respect to the invitation user in the application origin application 10, for example, when invitation by the invitation application from an invitation user is materialized, for example. be able to.

The invitation establishment receiving unit 237 may acquire the invitation establishment information from the application server 310 (game A) corresponding to the application source application 10. For example, when the application source application 10 is activated on the user terminal 100 of the invited user, the application server 310 (game A) corresponding to the application source application 10 communicates with the user terminal 100 of the invited user. It is possible to recognize that the application source application 10 has been activated on the user terminal 100 of the invited user. Therefore, the invitation establishment information may be transmitted from the application server 310 (game A) corresponding to the application source application 10 to the management server 200.
For example, the invitation establishment receiving unit 237 receives the user terminal 100 of the invited user based on the activation of the application source application 10 (an example of the first application) on the user terminal 100 of the invited user (an example of the second user). Invitation establishment information transmitted from the application server 310 (an example of a server device) corresponding to the application source application 10 and indicating that the invitation corresponding to the invitation notification information has been established is received. Then, the invitation establishment processing unit 238 performs a predetermined process based on the invitation establishment information received by the invitation establishment receiving unit 237.

  Thereby, the management server 200 can recognize that it has been established when the invitation by the invitation user is established. In addition, when the management server 200 recognizes that an invitation by an invitation application from an invitation user has been established, for example, a predetermined reward can be given to the invitation user in the application source application 10.

For example, the invitation establishment processing unit 238 receives invitation completion notification information for notifying that the invitation corresponding to the invitation notification information has been established based on the invitation establishment information received by the invitation establishment receiving unit 237 as a predetermined process. It transmits to the application server 310 (an example of a server apparatus) corresponding to the user terminal 100 of the user (an example of a 1st user) or the application origin application 10 (an example of a 1st application).
Thereby, the application server 310 executed on the user terminal 100 of the invited user or the application server 310 corresponding to the application source application 10 gives a reward on the condition that the invitation corresponding to the invitation notification information has been established. be able to.

Specifically, the invitation establishment processing unit 238 rewards the invited user (an example of the first user) in the application source application 10 (an example of the first application) based on the invitation establishment information received by the invitation establishment receiving unit 237. To the application server 310 (an example of a server device) corresponding to the user terminal 100 of the inviting user or the application source application 10 with at least information corresponding to the inviting user in the application source application 10 as invitation completion notification information. Send.
Thereby, the application server 310 executed on the user terminal 100 of the inviting user or the application server 310 corresponding to the application source application 10 provides the invitation user with a condition that the invitation corresponding to the invitation notification information has been established. Can be rewarded.

  In addition, when the invitation by the invitation application from the invited user is established, the management server 200 may be configured to give a predetermined reward to the invited user in the application source application 10. In addition, the management server 200 may allow a predetermined reward to be given to an invited user or an invited user in the application destination application 20, or a reward that can be commonly used in a plurality of applications is an invited user or an invited user. You may make it provide with respect to a user.

  In addition, the above-mentioned reward is a reward that can be used in another application different from the application source application 10 and the application destination application 20, or a reward that can be used on a website (for example, buying and selling goods and services through communication via a communication network). Currency or points that can sometimes be used. In this case, for example, the management server 200 temporarily manages information related to a reward given to the user, and then a predetermined procedure is performed, thereby providing a reward that can be used by another application or a reward that can be used on a website. As described above, the managed reward information may be transmitted to a server device corresponding to another application or a server device corresponding to a website.

(23) Part or all of the invitation notification information is included in the invitation establishment information, and part or all of the invitation notification information is applied to the application source application at the user terminal 100 of the invited user (an example of the second user). 10 (an example of the first application) is acquired directly from the application 20 (an example of the second application) or indirectly via the terminal storage unit 140 (an example of the storage unit) of the user terminal 100. is there.

  Thereby, the user terminal 100 can transmit the invitation establishment information including part or all of the invitation notification information acquired in the application destination application 20 from the application source application 10.

In addition, part or all of the invitation notification information may be associated with the invitation establishment information and may not be included in the invitation establishment information. For example, a part or all of the invitation notification information is associated with the invitation establishment information, and part or all of the invitation notification information is applied by the user terminal 100 of the invited user (an example of the second user). An application 10 (an example of a first application) acquired directly from an application 20 (an example of a second application) or indirectly through a terminal storage unit 140 (an example of a storage unit) of the user terminal 100 It may be.
Thereby, the management server 200 can acquire invitation establishment information associated with a part or all of the invitation notification information.

(24) The function of the application list acquisition unit 161, the function of the specific mode activation unit 162, the function of the user list acquisition unit 163, the function of the invitation request notification unit 164, the function of the specific mode end unit 165, The function of the inquiry unit 166, the function of the invitation notification acquisition unit 167, the function of the presentation unit 168, the function of the screen transition unit 169, the function of the invitation information management unit 170, and the function of the invitation establishment notification unit 171 include: It is executed based on the SDK 11 (an example of a program (software)) incorporated in a program of a corresponding application (for example, each program of the application source application 10 and the application destination application 20) installed in the user terminal 100.

  That is, by executing SDK 11 (an example of a program (software)) incorporated in a corresponding application program (for example, each program of application source application 10 and application destination application 20) installed in user terminal 100, The function of the application list acquisition unit 161 described above, the function of the specific mode activation unit 162 (an example of the activation unit), the function of the user list acquisition unit 163 (an example of the invitation candidate user information acquisition unit), and the invitation application notification unit 164 , The function of the specific mode end unit 165, the function of the inquiry unit 166, the function of the invitation notification acquisition unit 167, and the presentation unit 168 (an example of the first display control unit, an example of the second display unit control unit) , The function of the screen transition unit 169, the function of the invitation information management unit 170, and the function of the invitation establishment notification unit 171 There is realized.

  For example, the SDK 11A incorporated in the application source application 10 has the function of the application list acquisition unit 161, the function of the specific mode activation unit 162, the partial function of the presentation unit 168, and the function of the invitation establishment notification unit 171. The SDK 11B, which is executed and incorporated in the application 20 for application, has the function of the user list acquisition unit 163, the function of the invitation request notification unit 164, the function of the specific mode end unit 165, the function of the inquiry unit 166, and the invitation notification. The function of the acquisition unit 167, a part of the function of the presentation unit 168, the function of the screen transition unit 169, and the function of the invitation information management unit 170 are executed. Note that the SDK 11A and the SDK 11B each have the same function, and execute a corresponding function depending on whether it is incorporated in the application source application 10 or the application destination application 20.

  For example, the specific mode activation unit 162 (an example of the activation unit) is executed by executing the SDK 11A (an example of the program (software)) incorporated in the program of the application source application 10 (an example of the application) installed in the user terminal 100. ) Is implemented, and SDK 11B (an example of a program (software)) embedded in a program of an application 20 (an example of another application) installed in the user terminal 100 is executed, thereby obtaining a user list. The function of the unit 163 (an example of the user information acquisition unit) and the function of the invitation request notification unit 164 are realized.

  Thus, by incorporating the SDK 11 into the application, a compatible application corresponding to the mutual invitation system 500 of the present embodiment can be obtained. Therefore, for example, even in an existing application or an application to be developed in the future, if the application program is updated or changed so that the SDK 11 can be incorporated, the application can be made a compatible application corresponding to the mutual invitation system 500. .

In the above embodiment, for example, the application list acquisition unit 161, the specific mode activation unit 162 (activation unit), the presentation unit 168, the invitation information management unit 170, and the invitation establishment notification unit 171 include the application source application. 10 SDK 11A, a user list acquisition unit 163, an invitation application notification unit 164, a specific mode end unit 165, an inquiry unit 166, an invitation notification acquisition unit 167, a presentation unit 168, a screen Although the transition part 169 demonstrated the example which is a function structure which SDK11B of the application destination application 20 performs, it is not restricted to this.
The functional configuration of the above-described invitation process executed by the SDK 11A incorporated in the application 10 and the SDK 11B incorporated in the application 20 is an example, and each of the SDK 11A and SDK 11B ”is executed. The functional configuration to be performed may be changed as appropriate. For example, the invitation application notification unit 164 may have a functional configuration executed by the SDK 11A.

<Second Embodiment>
Next, a second embodiment of the present invention will be described. The configuration of the mutual invitation system 500 of the present embodiment is different from the first embodiment in that an arbitrary corresponding application set in advance can be excluded from the application list of the corresponding applications that can select the invited user. To do.

  FIG. 11 is a configuration diagram illustrating an example of the configuration of the management server 200 according to the second embodiment. In the management server 200 shown in this figure, the storage unit 220 further includes an extraction condition storage unit 225, and the control unit 230 further includes an extraction unit 239 in the first embodiment shown in FIG. This is different from the configuration of the management server 200. In FIG. 11, the same reference numerals are given to the components corresponding to the respective parts shown in FIG. Hereinafter, the characteristic configuration and processing according to the present embodiment will be described with reference to FIG.

  The extraction condition storage unit 225 stores extraction conditions for extracting a corresponding application that can be applied for invitation to the application source application 10 (an example of the first application). For example, the extraction condition storage unit 225 includes a mutual invitation rejection setting storage unit 226 that stores mutual invitation prohibition setting information indicating a setting related to a combination of corresponding applications that are not to be invited to each other in the mutual invitation system 500 as the extraction condition. Yes.

  Specifically, the mutual invitation rejection setting storage unit 226 includes a mutual invitation prohibition setting in which a setting-side application that sets prohibition of an invitation application and a set-side application that is prohibited from applying for an invitation to the setting-side application. Information (third prohibition information) is stored. FIG. 12 is a diagram illustrating an example of mutual invitation prohibition setting information stored in the mutual invitation rejection setting storage unit 226. In the mutual invitation prohibition setting information, a filter ID (FilterID), a blocked application ID (ApIDfrom), and a blocked application ID (ApIDto) are associated.

  The filter ID (FilterID) is a management ID issued in the order in which each mutual invitation prohibition setting information is registered so that each mutual invitation prohibition setting information can be identified. In the blocked application ID (ApIDfrom), the application ID of the setting side application that sets prohibition of invitation application is set. In the blocked application ID (ApIDto), the application ID of the set-side application that is prohibited from applying for invitation is set.

  For example, when the application ID of the application 10 is set to the blocked application ID (ApIDto), the corresponding application set to the blocked application ID (ApIDfrom) is removed from the application list. That is, when it is desired to prohibit the invitation from the application source application 10 (game A) to the application destination application 20 (game B), the application ID of the application source application 10 (game A) is set in the blocked application ID (ApIDto). Then, the application ID of the application 20 to be applied may be set as the blocked application ID (ApIDfrom).

  In addition, when the application ID of the application source application 10 is set to the blocked application ID (ApIDfrom), the corresponding application set to the blocked application ID (ApIDto) may be removed from the application list. . That is, for the setting side application for setting prohibition of invitation application set for the blocked application ID (ApIDfrom) and the blocked application ID (ApIDto), and the set side application for which the invitation application is prohibited The invitation application may be prohibited in one direction, or the invitation application may be prohibited in both directions.

  Here, the mutual invitation prohibition setting information stored in the above-described mutual invitation rejection setting storage unit 226 is managed by the application management unit 231. In other words, the application management unit 231 manages mutual invitation prohibition setting information in which a setting-side application that sets prohibition of an invitation application and a set-side application that is prohibited from applying for an invitation to the setting-side application.

  The extraction unit 239 can apply for an invitation from the corresponding application to the application source application 10 (first application) based on the extraction condition based on the mutual invitation prohibition setting information stored in the mutual invitation rejection setting storage unit 226. Extract compatible applications.

  Then, the application list notifying unit 232 applies an application list including at least a part of the corresponding application extracted by the extracting unit 239 to the application list of the corresponding application that can apply for an invitation to the application source application 10 (an example of the first application). As the user terminal 100 of the invited user (an example of the first user).

  Thereby, by setting the invitation prohibition information in advance, any corresponding application can be excluded from the application list of the corresponding applications that can select the invited user.

[Summary]
As described above, the application management unit 231 manages information related to each of a plurality of corresponding applications including the application source application 10 (an example of a first application) and the application destination application 20 (an example of a second application). Here, the information regarding each of the plurality of corresponding applications managed by the application management unit 231 is, for example, information indicating each of the plurality of corresponding applications or information regarding prohibition of the invitation application set for each of the plurality of corresponding applications. is there.
Then, the application list notification unit 232 (an example of the application information notification unit) refers to the application management unit 231 to determine whether or not an invitation application to the application source application 10 is possible (for example, prohibition of invitation application is set). And an application list (an example of information indicating an application) indicating an application that can be applied for invitation is transmitted to the user terminal 100 of the invited user (an example of the first user).
Thereby, the management server 200 can transmit to the user terminal 100 of the inviting user an application list of only compatible applications that can be invited.

For example, the application management unit 231 manages invitation prohibition information that is a combination of a setting-side application that sets prohibition of invitation application and a set-side application that prohibits invitation application for the setting-side application.
The application list notification unit 232 (an example of the application information notification unit) refers to the invitation prohibition information managed by the application management unit 231 and sets the application source application 10 (an example of the first application) as a set-side application. If there is invitation prohibition information, the application list of the corresponding applications excluding the setting side application indicated by the invitation prohibition information (example of third prohibition information) is displayed as the user of the invited user (example of the first user). Transmit to terminal 100.

Specifically, the application list notification unit 232 uses the application list of the corresponding application extracted by the extraction unit 239 based on the extraction condition as the application list of the corresponding application that can be applied to the request source application 10. You may transmit with respect to the user terminal 100. FIG.
For example, it is assumed that there is invitation prohibition information in which the application source application 10 is set as a set-side application among the invitation prohibition information managed by the application management unit 231 as an extraction condition. In this case, the extraction unit 239 extracts a corresponding application that excludes the corresponding application corresponding to the setting-side application indicated by the invitation prohibition information as the corresponding application that is set to reject the invitation application to the application source application 10. To do. Then, the application list notifying unit 232 sends an application list to the user terminal 100 of the inviting user, excluding the corresponding application set to reject the invitation application to the application source application 10 based on the extraction result of the extracting unit 239. Send to.

  Thereby, in the mutual invitation system 500, the relationship of the corresponding application that is not desired to be invited to each other can be set in the management server 200. For example, if there is a corresponding application for which rating (age restriction) is set, the application source application 10 for which the rating is not set is invited to the application destination application 20 for which the rating is set. As a result, the application 20 to which the rating is set can be excluded from the application list.

  Thereby, the corresponding applications set in the setting-side application and the set-side application in the mutual invitation prohibition setting information can mutually (bidirectionally) be prohibited (blocked) from being listed in the application list.

  Note that the blocked application ID (application ID of the setting side application) and the blocked application ID (application ID of the set side application) in the inter-app filter information shown in FIG. Also good. That is, the application list notification unit 232 (an example of the application information notification unit) refers to the mutual invitation prohibition setting information managed by the application management unit 231 and invites the application source application 10 set as the setting-side application. When there is prohibition information, an application list (an example of information indicating an application) of applications other than the set-side application indicated by the invitation prohibition information may be transmitted to the user terminal 100 of the inviting user.

  In this way, by prohibiting invitation applications in both directions, it is not necessary to store mutual invitation prohibition setting information in one direction, so the storage capacity of the mutual invitation rejection setting storage unit 226 is reduced. be able to. Note that information indicating whether one-way is valid or two-way is valid may be added to the mutual invitation prohibition setting information stored in the mutual invitation rejection setting storage unit 226.

<Third Embodiment>
Next, a third embodiment of the present invention will be described. The configuration of the mutual invitation system 500 of the present embodiment is different from the first embodiment in that a preset user can be excluded from the user list of users that can be selected as invited users.

  In the first embodiment, the user list acquired from the application server 300 corresponding to the application destination application 20 operating in the specific mode (for example, the application server 320 (game B) corresponding to the application destination application 20 (game B)). A configuration has been described in which a friend list corresponding to is displayed on the display unit 120. In this embodiment, the user list is configured to be displayed on the display unit 120 as a new user list (hereinafter also referred to as an invitation candidate user list) after filtering the users included in the user list according to a predetermined extraction condition. This user list filtering process is performed in the management server 200 when the user list acquired from the application server 300 is notified to the management server 200 from the user terminal 100-1 (SDK11B).

[Description of user list filtering processing]
With reference to FIG. 13, the operation of the invitation process when the user list is filtered will be described. FIG. 13 is a flowchart showing an example of the operation of the invitation process according to the present embodiment. The invitation process shown in this figure is different from the invitation process of the first embodiment shown in FIG. 9 in that a user list filtering process (steps SB130, SE120, and SB140) is added. In FIG. 13, the same processes as those shown in FIG. 9 are denoted by the same reference numerals, and the description thereof is omitted.

  In step SB120, when the application destination application 20 (game B) of the user terminal 100-1 acquires the user list from the application server 320 (game B), the user list acquisition unit 163 of the SDK 11B of the application destination application 20 (game B). Acquires the user list from the application 20 (game B) and notifies the management server 200 of the acquired user list. For example, the user list acquisition unit 163 transmits filtering request information including the user ID of the user included in the user list to the management server 200 (REQ12, step SB130).

  Here, the filtering request information includes, for example, an application source application ID (ApIDfrom), an application destination application ID (ApIDto), an invitation user ID of the application destination application (Apto_UIDfrom), and an invited user ID of the application destination application ( Apto_UIDto).

  Next, when the management server 200 obtains the user list by receiving the filtering request information from the user terminal 100-1 (SDK11B), the management server 200 performs a filtering process according to a predetermined extraction condition, and the invitation candidate user list after filtering as a filtering result. Is transmitted to the user terminal 100-1 (SDK11B) (RES12, step SE120). This filtered invitation candidate user list (filtering result) includes the user ID of the user extracted by the predetermined extraction condition from the user list notified to the management server 200 from the user terminal 100-1 (SDK11B). It is.

  And user list acquisition part 163 of SDK11B of user terminal 100-1 acquires an invitation candidate user list after filtering as a filtering result corresponding to transmitted filtering request information (Step SB140).

  In step SB140, when the user list acquisition unit 163 acquires the invitation candidate user list after filtering, the presentation unit 168 of the SDK 11B of the user terminal 100-1 applies for at least a part of the users included in the invitation candidate user list. A friend list corresponding to the user list that is a candidate for invitation to the original application 10 (game A) is displayed on the display unit 120 (step SB150).

[Configuration of Management Server 200 of Third Embodiment]
Next, the configuration of the management server 200 that executes the above-described filtering process will be described.
FIG. 14 is a configuration diagram illustrating an example of the configuration of the management server 200 according to the present embodiment. In the management server 200 shown in this figure, the control unit 230 further includes a user list notification unit 240, an extraction condition storage unit 225 includes an invitation application rejection user setting storage unit 227, and an invitation application rejection application setting storage unit 228. Is different from the configuration of the management server 200 according to the second embodiment shown in FIG. In FIG. 14, components corresponding to those shown in FIG. Hereinafter, a characteristic configuration and processing according to the present embodiment will be described with reference to FIG.

  The user list notification unit 240 of the management server 200 acquires filtering request information for requesting user list filtering from the application 20 (SDK11B) operating in the specific mode in the user terminal 100. If acquired, the user list notifying unit 240, based on the filtering result (extraction result) by the extracting unit 239, among the users included in the user list, the user list (invitation of users who are candidates for invitation to the application source application 10) The candidate user list) is transmitted to the user terminal 100 (SDK11B).

  Moreover, in this embodiment, when the extraction part 239 acquires a user list from the application destination application 20 (SDK11B) of the user terminal 100, among the users included in the user list, an invitation candidate to the application source application 10 Are filtered (extracted) based on a predetermined extraction condition.

  The predetermined extraction condition extracted by the extraction unit 239 is managed by the application management unit 231, and specifically, is stored in the extraction condition storage unit 225. The extraction condition storage unit 225 includes an invitation application rejection user setting storage unit 227 and an invitation application rejection application setting storage unit 228.

[Invitation application rejection user setting]
The invitation application refusal user setting storage unit 227 stores, as the extraction condition of the extraction unit 239, invitation request refusal user setting information indicating settings regarding a user who does not want to accept an invitation in the mutual invitation system 500. For example, the invitation application refusal user setting storage unit 227 includes a setting side user who sets prohibition of invitation application, a set side user who is prohibited from inviting invitations to the setting side user, and a corresponding application that enables this setting. Invitation application refusal user setting information (first prohibition information) is stored.

  FIG. 15 is a diagram illustrating an example of invitation application rejection user setting information stored in the invitation application rejection user setting storage unit 227. In the invitation application refusal user setting information, a filter ID (FilterID), an application ID (FilterApID), a blocking user (UIDfrom), and a blocked user (UIDto) are associated. The filter ID (FilterID) is a management ID that is issued in the order in which each invitation application rejection user setting information is registered so that it can be identified for each invitation application rejection user setting information. In the application ID (FilterApID), the application ID of the corresponding application (application destination application 20) that enables this prohibition setting is set. The user ID of the setting side user who sets prohibition of invitation application is set to the user (UIDfrom) to block. For the blocked user (UIDto), the user ID of the set user who is prohibited from applying for invitation is set.

  For example, when the application destination application 20 is set to the application ID (FilterApID) and the user ID of the invited user is set to a blocked user (UIDto), the invitation candidate user in the invitation user application destination application 20 The user who is set as the blocking user (UIDfrom) is excluded from the list. Therefore, in the application destination application 20 (game B), when the user Y does not want to receive an invitation from the user X, for example, the application ID of the application destination application 20 (game B) is set in the application ID (FilterApID). The user ID of user X may be set for the blocked user (UIDto), and the user ID of user Y may be set for the blocked user (UIDfrom). Thereby, in the application destination application 20 (game B) of the user X, the user Y is excluded from the invitation candidate user list.

  If the application destination application 20 is set to the application ID (FilterApID) and the user ID of the invited user is set to a blocked user (UIDfrom), the invitation candidate user list in the application user application 20 of the invited user is set. From this, users set as blocked users (UIDto) may be excluded. That is, for the setting side user who sets prohibition of the invitation application set for the blocked user (UIDfrom) and the blocked user (UIDto), and the set side user who is prohibited from the invitation application, there is one. The invitation application may be prohibited with respect to the direction, or the invitation application may be prohibited with respect to the two directions.

  As a function of the SDK 11, a user who does not want to accept an invitation can be set from the user terminal 100. When the user (blocking user) performs the block setting in any of the corresponding applications, the application ID of the corresponding application as an application ID (FilterApID), the user ID of the user who performs the block setting as a blocking user (UIDfrom), Invitation application refusal user setting information in which user IDs of users who do not wish to accept invitations are set as blocked users (UIDto) is registered and stored in the invitation application refusal user setting storage unit 227.

[Invitation application rejection application setting]
The invitation application refusal application setting storage unit 228 stores, as the extraction condition of the extraction unit 239, invitation request refusal application setting information indicating settings related to a corresponding application that the user does not want to accept the invitation in the mutual invitation system 500.

  FIG. 16 is a diagram illustrating an example of invitation application rejection application setting information stored in the invitation application rejection application setting storage unit 228. In the invitation application rejection application setting information, a filter ID (FilterID), a blocked user (UIDfrom), and an application ID (FilterApID) of a corresponding application to be blocked are associated. The filter ID (FilterID) is a management ID that is issued in the order in which each invitation application rejection application setting information is registered so that it can be identified for each invitation application rejection application setting information. In the application ID (FilterApID), the application ID of the corresponding application that the user does not want to accept the invitation is set. The user ID of the user who does not want to accept the invitation in the corresponding application indicated by the application ID set in the application ID (FilterApID) is set in the user to be blocked (UIDfrom).

  As a function of the SDK 11, it is possible to set a corresponding application that the user does not want to accept the invitation from the user terminal 100. When a user (blocking user) performs the block setting in one of the corresponding applications, the application ID of the corresponding application as an application ID (FilterApID) and the user ID of the user who performs the block setting as a blocking user (UIDfrom) The invitation application rejection application setting information set for each is registered and stored in the invitation application rejection application setting storage unit 228.

  For example, it is assumed that the application 20 (game B) is set as an application ID (FilterApID) and the user ID of the user Y is set as a blocked user (UIDfrom). In this case, the user Y is excluded from the invitation candidate user list presented in the application 20 (game B) of the invited user (for example, the user X).

  Further, it is assumed that the application source application 10 (game A) is set to an application ID (FilterApID) and the user ID of the user Y is set to a blocked user (UIDfrom). In this case, the user Y is excluded from the friend list of the invitation candidate user invited to the application source application 10 (game A) in the invitation candidate friend list presented to the invited user (for example, the user X). . Thereby, for example, it is possible to block an invitation application to a corresponding application that has already been installed or to a corresponding application that has been uninstalled and then uninstalled.

[Summary]
(1) As described above, the user terminal 100 (an example of a terminal device) according to the present embodiment includes an application list acquisition unit 161, a specific mode activation unit 162 (an example of an activation unit), and a presentation unit 168 (first An example of a presentation unit, an example of a second presentation unit), a user list acquisition unit 163, an invitation application notification unit 164, an inquiry unit 166, an invitation notification acquisition unit 167, a screen transition unit 169, and an invitation information management unit 170.
Based on the first operation in the application source application 10 (an example of an application) that is operating in the normal mode, the application list acquisition unit 161 applies to the user terminal 100 in which the application destination application 20 (an example of a second application) is installed. Then, an application list including a part or all of a plurality of corresponding applications corresponding to a process (an example of an invitation process) for installing the application source application 10 (an example of a first application) is acquired from the management server 200. The presentation unit 168 (an example of a first presentation unit, an example of an application list presentation unit) is a corresponding application installed in the user terminal 100 (an example of the own terminal device) from the application list acquired by the application list acquisition unit 161. Present.
The specific mode activation unit 162 (an example of the activation unit) is selected based on the second operation from the corresponding applications presented by the presentation unit 168 (an example of the first presentation unit, an example of the application list presentation unit). The first user information (user ID or user ID) corresponding to the invited user (an example of the user) in the application source application 10 (an example of the application) operating in the normal mode with respect to the application destination application 20 that is a compatible application The selected application destination application 20 (an example of an application) is activated in a specific mode so that the management server 200 can be notified of the token information associated with ().

  The user list acquisition unit 163 acquires a user list of users who are candidates for invitation from the management server 200 while the application 20 (an example of an application) is operating in the specific mode. And the invitation application notification part 164 is 2nd user information (for example, user ID) corresponding to the user (an example of an invited user) selected from 1st user information and the user list which the user list acquisition part 163 acquired. ) Including invitation request information is transmitted to the management server 200.

  The inquiry unit 166 records, in the application 20 that is operating in the normal mode, invitation application information (that is, invitation application information for the user) that the invited user is the own user (for example, the user Y) (invitation application record). The management server 200 is inquired (an example of an application inquiry). Then, as a result of the inquiry by the inquiry unit 166, the invitation notification acquisition unit 167 has invitation application information in which the information corresponding to the user is second user information (for example, a user ID) corresponding to the invited user. Invitation notification information based on the invitation application information is acquired from the management server 200.

Moreover, the presentation unit 168 (an example of the second presentation unit, an example of the invitation information presentation unit) presents invitation information based on the invitation notification information acquired by the invitation notification acquisition unit 167. Based on the third operation for the invitation information presented by the presentation unit 168, the screen transition unit 169 transitions to a screen on which the application source application 10 indicated by the invitation information can be installed.
And the invitation information management part 170 is the invitation notification corresponding to the invitation information by which 3rd operation was carried out among the invitation information which the presentation part 168 showed (the invitation was accepted by the invited user (for example, user Y)). At least a part of the information included in the information is stored in the terminal storage unit 140 of the user terminal 100.

Note that the SDK 11 may include an application list of compatible applications. In this case, since the application list does not need to be acquired from the management server 200, the user terminal 100 does not have the configuration of the application list acquisition unit 161. Also good.
Even if the user terminal 100 of the invited user does not make an application inquiry to the management server 200, the user terminal 100 may acquire invitation notification information based on the invitation request information for the invited user transmitted from the management server 200. Good. For example, the management server 200 receives the invitation notification information based on the invitation application information for the invited user on the user terminal 100 of the invited user when the application destination application 20 is activated in the user terminal 100 of the invited user. You may transmit to. In addition, the management server 200 may transmit the invitation notification information to the user terminal 100 of the invited user at a predetermined time period or periodically at a predetermined time.

  Accordingly, the user terminal 100 (an example of a terminal device) of the present embodiment includes a specific mode activation unit 162 (an example of an activation unit) and a presentation unit 168 (an example of a first display control unit, an example of a second display control unit). And a user list acquisition unit 163 (an example of an invitation candidate user information acquisition unit), an invitation application notification unit 164, an invitation notification acquisition unit 167, and a screen transition unit 169. Can be described as follows.

  The presentation unit 168 (an example of the first display control unit) is based on the first operation in the application source application 10 (an example of the first application) installed in the user terminal 100 (an example of the own terminal device). Information indicating a plurality of corresponding applications is displayed on the display unit 120. The specific mode activation unit 162 (an example of an activation unit) is the application application 20 selected based on the second operation from the corresponding applications indicated by the information indicating one or more corresponding applications displayed by the presentation unit 168. (Example of second application) is activated as a specific mode. The user list acquisition unit 163 (an example of an invitation candidate user information acquisition unit) is a user list indicating users who are invitation candidates invited from the management server 200 to the application source application 10 in the application destination application 20 operating in the specific mode. (An example of invitation candidate user information) is acquired. The invitation application notifying unit 164 is an invitation application in which second user information (for example, a user ID) corresponding to an invited user invited to the application source application 10 in the invitation candidate user list acquired by the user list acquisition unit 163 is associated. Information is transmitted to the management server 200.

  In the invitation source acquisition unit 167, in the application source application 10 that is operating in the normal mode, when the management server 200 has invitation application information in which information corresponding to the user is second user information corresponding to the invited user, Invitation notification information based on the invitation application information is acquired from the management server 200. The presentation unit 168 (an example of a second display control unit) causes the display unit 120 to display invitation information based on the invitation notification information acquired by the invitation notification acquisition unit 167. Based on the third operation for the invitation information displayed on the display unit 120 by the presentation unit 168, the screen transition unit 169 transitions to an installable screen of the application indicated by the invitation information.

  Thereby, the user terminal 100 starts the application destination application 20 in the specific mode based on the operation of the invitation user in the application source application 10, thereby inviting candidate user lists indicating users who are candidates for invitation to the application source application 10. Can be acquired and displayed on the display unit 120. Here, the user shown by this invitation candidate user list was extracted as a user who becomes an invitation candidate from other users who are in a predetermined relationship (for example, friend relationship) with an invitation user in application destination application 20, for example. This is a user candidate who can be invited to the application 20 for application. Therefore, since the user terminal 100 can display only users that can be selected as invited users, the convenience when the invited users select the invited users can be improved.

  Further, the user terminal 100 can apply for an invited user whose invitation user has a predetermined relationship (for example, a friend relationship) in the application destination application 20 to the application source application 10, and therefore a predetermined relationship ( For example, users who are friends) can be invited to other applications. In addition, in the user terminal 100 of the invited user, when there is an invitation request from the invited user, since the invitation information to the application destination application 20 is displayed on the display unit 120 in the application destination application 20, the invited user is It is possible to easily recognize that the invitation application 20 has been invited. In addition, because the operation to the invitation information displayed on the display unit 120 causes a transition to a screen where the application destination application 20 can be installed, the invited user can easily install the invited application destination application 20. Can do.

(2) The user terminal 100 includes an invitation establishment notification unit 171. The invitation establishment notifying unit 171 receives the terminal storage unit 140 (memory) of the user terminal 100 (an example of the own terminal device) when a predetermined condition is satisfied in the application source application 10 (an example of an application) operating in the normal mode. Is established on the condition that at least a part of the information included in the invitation notification information corresponding to the application 10 of the application (an example of the active application) is stored in the application) Information is transmitted to the management server 200.

  As described in the first embodiment, the invitation information management unit 170 includes the invitation information displayed on the display unit 120 by the presentation unit 168 (an example of the second display control unit, an example of the invitation information presentation unit). The terminal storage unit 140 (an example of the storage unit) of the user terminal 100 (an example of the own terminal device) stores at least a part of the information associated with the invitation notification information corresponding to the invitation information for which the third operation has been performed. Also good. In this case, the invitation establishment notification unit 171 stores the application source in the terminal storage unit 140 of the user terminal 100 when a predetermined condition is satisfied in the application source application 10 (an example of the first application) operating in the normal mode. The invitation establishment information corresponding to the invitation notification information may be transmitted to the management server 200 on condition that at least a part of the information associated with the invitation notification information corresponding to the application 10 is stored.

Thereby, the user terminal 100 notifies the management server 200 that the invitation has been established by the invitation application by the invited user installing and using the application source application 10 based on the invitation request from the invited user. be able to. Furthermore, on condition that at least a part of information included in the invitation notification information is stored, for example, the user himself installs without using the mutual invitation system 500 (not based on the invitation request from the invited user) Installed items can be excluded. That is, it is possible to notify the management server 200 only of those that have been invited by invitation requests from invited users.
Here, if the timing at which the invitation establishment information is transmitted to the management server 200 is a case where a predetermined condition after use is satisfied in the application source application 10, it is used only when the application source application 10 is installed. The case where it is not done can be excluded from the conditions for accepting the invitation.

(3) The application list acquisition unit 161 of the user terminal 100 acquires URL schemes corresponding to the corresponding applications included in the application list together with the application list. Then, the presenting unit 168 (an example of the first presenting unit, an example of the application list presenting unit) detects a corresponding application installed in the user terminal 100 (an example of the own terminal device) using the acquired URL scheme. To the user.

  In addition, although the example which detects the corresponding application installed in the user terminal 100 using URL scheme was demonstrated, it is not restricted to this. For example, when the OS can acquire information indicating the corresponding application already installed in the user terminal 100, the OS is installed in the user terminal 100 using the information indicating the corresponding corresponding application already installed. Other applications may be detected.

  For example, the presentation unit 168 (an example of the first display control unit) is acquired by the application list acquisition unit 161 (an example of the application information acquisition unit) using a function included in the user terminal 100 (an example of the own terminal device). Alternatively, a corresponding application installed in the user terminal 100 may be detected from the corresponding applications indicated by information indicating one or a plurality of corresponding applications, and information indicating the detected applications may be displayed on the display unit 120.

  Thereby, the user terminal 100 presents only the corresponding application installed in the user terminal 100 (an example of the own terminal device) from the corresponding application list acquired from the management server 200 (displayed on the display unit 120). be able to.

(4) The user list acquisition unit 163 of the SDK 11 of the corresponding application installed in the user terminal 100 (an example of the terminal device) of the present embodiment corresponds to the application application 20 (an example of the application) that is operating in the specific mode. The user list acquired from the application server 300 (an example of a server device) may be notified to the management server 200 (an example of a management device). Then, the user list acquisition unit 163 acquires a list of users filtered (an example of extraction) from the notified user list based on a predetermined extraction condition from the management server 200, and creates a new user list (for example, invite candidate users). List).

  As described in the first embodiment, the user list is an example of information indicating a user, and the form of the information may be any form. For example, the user list acquisition unit 163 (invitation candidate user information acquisition unit) has a predetermined relationship with the invited user (an example of the own user) in the application destination application 20 (an example of the second application) operating in the specific mode (for example, The management server 200 may be notified of a user list (an example of predetermined relationship user information) indicating users who are in a friend relationship). And the user list acquisition part 163 acquires the information which shows the user extracted based on the predetermined extraction condition from the notified user list from the management server 200, and also serves as an invitation candidate user list (an example of invitation candidate user information). Good.

  Thereby, the user terminal 100 can select the invited user from the invitation candidate user list excluding the preset users among the users having a predetermined relationship (for example, a friend relationship) with the invited user in the application destination application 20. Can be presented to the invited user as a list of friends of the active user. Therefore, the invited user can select the invited user from the friend list from which the user who does not want to accept the invitation is removed.

(5) The control unit 230 of the management server 200 (an example of a management apparatus) includes an extraction unit 239, a user list notification unit 240, an invitation application reception unit 233, an invitation notification unit 236, and an invitation establishment reception unit 237. ing. When the extraction unit 239 acquires a user list of users who have a predetermined relationship (for example, a friend relationship) from the application destination application 20 (an example of the second application), the application unit application among the users included in the user list Users (candidates for invitation to 10 (an example of the first application)) are filtered (extracted) based on a predetermined extraction condition. The user list notification unit 240 displays an invitation candidate user list, which is a user list of users who are candidates for invitation to the application source application 10 (an example of the first application) extracted by the extraction unit 239, as an invited user (an example of the first user). ) To the user terminal 100. The invitation application receiving unit 233 receives invitation request information for inviting an invited user (an example of a second user), which is a selected user in the filtered invitation candidate user list, to the application source application 10. Receive from terminal 100. The invitation notification unit 236 transmits invitation notification information based on the invitation application information to the user terminal 100 of the invited user. The invitation establishment receiving unit 237 receives invitation establishment information indicating that the invitation from the application destination application 20 to the application source application 10 has been established from the user terminal 100 of the invited user.

  As a result, the management server 200 extracts from the user list of users who are in a predetermined relationship (for example, friend relationship) with the invited user in the application destination application 20 based on the extraction conditions set in advance, the user invitation candidate user list Can be notified to the user terminal 100. Therefore, it is possible to improve the convenience of the invited user when inviting a user who is in a friend relationship with another application to another application.

  The control unit 230 of the management server 200 (an example of a management device) may not include the invitation establishment receiving unit 237, and includes an extraction unit 239, a user list notification unit 240, an invitation application receiving unit 233, It is good also as a structure provided with the invitation notification part 236 at least. For example, the extraction unit 239 includes a user list of users who are in a predetermined relationship (for example, a friend relationship) from the application destination application 20 (an example of a second application) (an example of predetermined relationship user information indicating a user in a predetermined relationship). Are acquired, the users who are candidates for invitation to the application source application 10 (an example of the first application) among the users included in the user list are filtered (extracted) based on the extraction condition. The user list notification unit 240 (an example of an invitation candidate user notification unit) invites an invitation candidate user list (an example of invitation candidate user information) indicating users who are candidates for invitation to the application source application 10 extracted by the extraction unit 239. It transmits with respect to the user terminal 100 of a user (an example of a 1st user). The invitation application receiving unit 233 receives from the user terminal 100 of the inviting user the invitation application information for inviting the invited user (an example of the second user) among the users shown in the transmitted invitation candidate user list to the application source application 10. receive. The invitation notification unit 236 transmits invitation notification information based on the invitation application information to the user terminal 100 of the invited user.

  Thereby, the management server 200 extracts only the user who becomes the invitation candidate from the user list of the user who is in the predetermined relationship (for example, friend relationship) with the invited user in the application destination application 20, and the user terminal 100 of the invited user. Can be notified. Therefore, it is possible to improve the convenience of the invited user when inviting a user who is in a friend relationship with another application to another application.

  For example, when the extraction unit 239 acquires a user list of users who have a predetermined relationship from the application application 20 started from the application source application 10, the extraction unit 239 uses a user who is a candidate for invitation to the application source application 10 as an extraction condition. Extract based on. And the user list notification part 240 transmits an invitation candidate user list with respect to the application destination application 20 of the user terminal 100 of an invitation user. The invitation application receiving unit 233 receives invitation application information for requesting the invited user from the application source application 10 from the application destination application 20 of the user terminal 100 of the inviting user. As described above, since the invitation application information is not received from the application source application 10 of the inviting user but received from the application source application 10 via the application destination application 20, the application source application 10 and the application destination are received. A user can be easily invited even between applications whose user information is not compatible, such as the application 20.

In addition, the management server 200 displays invitation establishment information indicating that an invitation from the application destination application 20 (an example of the second application) to the application source application 10 (an example of the first application) has been established. It is good also as a structure provided with the invitation establishment reception part 237 received from the user terminal 100 of an example of a user.
According to this configuration, the management server 200 can recognize that an invitation has been established when an invitation by an invitation user is established. For example, when the management server 200 recognizes that an invitation by an invitation application from an invitation user has been established, the management server 200 may perform a process in which a predetermined reward is given to the invitation user in the application source application 10.

(6) For example, the extraction unit 239 excludes, as the extraction condition, a user who is set to reject an invitation application from an invited user (an example of a first user) from the extraction target.

  Thereby, the management server 200 can transmit to the user terminal 100 of an invitation user the invitation candidate user list | wrist except the user set to refuse the invitation application from an invitation user.

Specifically, for example, the application management unit 231 includes a blocking user (a setting-side user who sets prohibition of an invitation application) and a blocked user (a set-side user who is prohibited from an invitation application for a setting-side user). Invitation application refusal user setting information (an example of first prohibition information) is stored in the invitation application refusal user setting storage unit 227 for management.
And the extraction part 239 is a user (an example of a to-be-set side user) from which the invitation user (an example of a 1st user) is blocked among the invitation application refusal user setting information which the application management part 231 manages as extraction conditions. If there is invitation request rejection user setting information set in), the setting to reject the invitation request from the invited user for the blocking user (an example of the setting side user) indicated by the invitation application rejection user setting information is set. As a selected user.

  In addition, when there is invitation application refusal user setting information set for a user (an example of a setting side user) that blocks an invited user (an example of a first user), the invitation application refusal user setting information is blocked. May be excluded as a user who is set to reject an invitation request from an invited user. In other words, for the blocking user and the blocked user, the invitation application may be prohibited in one direction, or the invitation application may be prohibited in both directions. .

  Thereby, in the mutual invitation system 500, the user relationship in the corresponding application that is not desired to be invited to each other can be set in the management server 200. Therefore, the mutual invitation system 500 can prevent an invitation application from an invited user who does not want to accept an invitation in an arbitrary corresponding application from being invited to the invited user.

(7) As the extraction condition, the extraction unit 239 may exclude a user who is set to reject an invitation application to the application source application 10 (an example of the first application) from the extraction target.

Specifically, for example, the application management unit 231 includes a blocked user (a setting-side user who sets prohibition of an invitation application) and a corresponding application that is blocked (a set-side application that is prohibited from an invitation application for a setting-side user) ) And the invitation application rejection application setting information (an example of second prohibition information) are stored in the invitation application rejection application setting storage unit 228 for management.
And the extraction part 239 is an application (target side application) from which the application origin application 10 (an example of a 1st application) is blocked among the invitation application refusal application setting information which the application management part 231 manages as extraction conditions. If there is an invitation application refusal application setting information set in (example) of), a user (an example of a setting side user) to be blocked indicated by the invitation application refusal application setting information is sent to the application app 10 Excluded from extraction as a user who is set to be rejected.

  Thereby, the management server 200 can transmit to the user terminal 100 of an invitation user the invitation candidate user list | wrist except the user set to refuse the invitation application to the application origin application 10. FIG. Therefore, the mutual invitation system 500 can prevent an invitation application to a corresponding application that the user does not want to accept the invitation from. Therefore, in the mutual invitation system 500, for example, if the user performs a setting for rejecting an invitation application to a corresponding application that is already installed in the user terminal 100 or a corresponding application that has been played once, It is possible to block the user from being invited to the corresponding application.

<Fourth Embodiment>
Next, a fourth embodiment of the present invention will be described. Since the configuration of the mutual invitation system 500 of the present embodiment is the same as the configuration of the third embodiment, characteristic processing in the present embodiment will be described. In 3rd Embodiment, the process which filters a user list based on the invitation application rejection user setting information or the invitation application rejection application setting information memorize | stored in the extraction condition memory | storage part 225 was demonstrated. In the present embodiment, a process for filtering the user list based on the invitation application record stored in the invitation application information storage unit 222 will be described.

  For example, when the extraction unit 239 of the management server 200 acquires the user list from the application destination application 20 (SDK11B) of the user terminal 100, the extraction candidate 239 is selected from the users included in the user list as invitation candidates to the application source application 10. Are filtered (extracted) based on the invitation application record.

  The first purpose to be prioritized in the filtering process according to the present embodiment is to exclude the invitation candidate users who have already installed the application source application 10 and are already using it from the invitation candidate user list. The second purpose is to exclude invitation candidate users who are applying for invitation from the invitation candidate user list. Furthermore, the third purpose is to exclude invitation candidate users whose invitation has failed or rejected from the invitation candidate user list.

Below, with reference to FIGS. 17-21, the example of the process filtered based on an invitation application record is demonstrated. Here, the first to fifth examples will be described as examples of the filtering process. The first example and the second example are examples of the filtering process related to the first object, the third example is an example of the filtering process related to the second object, and the fourth example and the fifth example are the above-mentioned filtering processes. It is an example of the filtering process regarding 3 purposes.
Here, FIG. 17 to FIG. 21 show a part of information included in the invitation application record stored in the invitation application information storage unit 222. Moreover, in each figure, the information in which “=” among the information included in the invitation application record is set in the invitation application record that has been applied for in the past as an extraction condition when the extraction unit 239 performs filtering. It is shown that it is the same as the ID that has been set.

(1) FIG. 17 is a diagram illustrating a first example of a process for filtering based on an invitation application record. The process shown in the first example is performed so that an invitation application (re-invite) is not made to an invitation candidate user who has already used (played) the application source application 10 (game A). ) Is a filtering process for removing invitation candidate users who have applied for invitations from the invitation candidate user list. This invitation application is the same application source application 10 and the same application destination application 20, and means that the invitation candidate user is an invitation application.

  The extraction unit 239 of the management server 200 matches the application application ID (ApIDfrom) and the application destination application ID (ApIDto) with respect to the invitation application record stored in the invitation application information storage unit 222, and Invitation candidate users who satisfy this condition are excluded from the invitation candidate user list so that an invitation application (re-invitation) with a condition that the user ID of the invitation candidate user matches the invitation user ID (Apto_UIDfrom) of the application destination application is not made. In other words, the invitation user ID of the application destination application (in order to prevent an invitation application having the user ID set in the invitation user ID (Apto_UIDfrom) of the application destination application being the invited user ID (Apto_UIDto) of the application destination application) The invitation candidate user indicated by the user ID set in Apto_UIDfrom) is excluded from the invitation candidate user list.

(2) FIG. 18 is a diagram illustrating a second example of the invitation application filtering process. The processing shown in the second example is performed so that an invitation application (re-invite) is not made to an invitation candidate user who has already used (played) the application source application 10 (game A). ) Is a filtering process that excludes invitation candidate users who have been invited to the invitation candidate user list from the invitation candidate user list.

  The invitation application information shown in FIG. 18 indicates that one of the flags “2” and “3” is set in the status of the invitation application (StatusInvite), and this invitation application has been accepted. ing. The extraction unit 239 of the management server 200 makes an application source application ID (ApIDfrom), an application destination application ID (ApIDto), and an application destination application target for the invitation application record stored in the invitation application information storage unit 222. Invitation candidate users who satisfy this condition are excluded from the invitation candidate user list so that invitation requests with conditions that match the invitation user ID (Apto_UIDto) are not made.

  The process shown in the second example may be applied in addition to the process shown in the first example. In this case, the invitation candidate users who have already used (played) the application source application 10 (game A) are selected. It is a filtering process that is excluded from the invitation candidate user list.

(3) FIG. 19 is a diagram illustrating a third example of the invitation application filtering process. In the process shown in the third example, for example, an invitation candidate user whose invitation application from the application destination application 20 (game B) to the application source application 10 (game A) is being invited (inviting) is selected from the invitation candidate user list. Filtering processing is excluded.

  In the invitation application information shown in FIG. 19, either the flag “0” or “1” is set in the invitation application status (StatusInvite). Or invitation application notice completed). The extraction unit 239 of the management server 200 makes an application source application ID (ApIDfrom), an application destination application ID (ApIDto), and an application destination application target for the invitation application record stored in the invitation application information storage unit 222. Invitation candidate users who satisfy this condition are excluded from the invitation candidate user list so that invitation requests with conditions that match the invitation user ID (Apto_UIDto) are not made.

  The process shown in the third example may be applied in addition to the process shown in the first example or the second example. In this case, the application source application 10 (game A) has already been used (played). The filtering process removes the invitation candidate user or the invitation candidate user who is in the invitation request from the invitation candidate user list.

(4) FIG. 20 is a diagram illustrating a fourth example of the invitation application filtering process. The process shown in the fourth example is, for example, filtering that excludes invitation candidate users whose invitation application from the application destination application 20 (game B) to the application source application 10 (game A) has failed or rejected from the invitation candidate user list. It is processing.

  The process shown in the fourth example is applied to a corresponding application in which the re-invite permission flag (FlagResultInvite) of the application information stored in the application setting storage unit 221 is set to the flag “0” (non-re-invite). This is applied when the original application 10 or the application 20 is applied.

  In the invitation application information illustrated in FIG. 20, a flag “−1” is set in the invitation application status (StatusInvite), which indicates that the invitation application has failed or has been rejected. The extraction unit 239 of the management server 200 makes an application source application ID (ApIDfrom), an application destination application ID (ApIDto), and an application destination application target for the invitation application record stored in the invitation application information storage unit 222. Invitation candidate users who satisfy this condition are excluded from the invitation candidate user list so that invitation requests with conditions that match the invitation user ID (Apto_UIDto) are not made.

  In addition, when the corresponding application in which the re-invite permission flag (FlagResultInvite) is set to the flag “1” (re-invite allowed) is the application source application 10 and the application destination application 20, the invited users who satisfy the above conditions are selected. , Do not exclude from the invitation candidate user list.

  The process shown in the fourth example may be applied in addition to the processes shown in the first to third examples. In this case, the application source application 10 (game A) has already been used (played). The filtering process removes the invitation candidate user, the invitation candidate user who is applying for the invitation, or the failed or rejected invitation candidate user from the invitation candidate user list.

(5) FIG. 21 is a diagram for explaining a fifth example of the invitation application filtering process. In the process shown in the fifth example, in the process shown in the fourth example, the invitation application from the application destination application 20 (game B) to the application source application 10 (game A) fails when the invited user is the same. Filtering that excludes invited invitation users. That is, in the process shown in the fourth example, even if the invited user is not the invitation user from the application destination application 20 (game B) to the application source application 10 (game A), The invitation candidate user may not be excluded from the invitation candidate user list.

  In the invitation application information shown in FIG. 21, the flag “−1” is set in the invitation application status (StatusInvite), which indicates that the invitation application has failed. The extraction unit 239 of the management server 200 applies the application source application ID (ApIDfrom), the application destination application ID (ApIDto), and the invitation of the application destination application to the invitation application record stored in the invitation application information storage unit 222. Invitation candidate users that satisfy this condition are excluded from the invitation candidate user list so that the user ID (Apto_UIDfrom) and the invited user ID (Apto_UIDto) of the application to be applied are not matched.

[Summary]
As described above, in the present embodiment, as in the third embodiment, a list of users filtered (extracted) based on a predetermined extraction condition is used as a new user list (an example of an invitation candidate user list). To do. Here, in the present embodiment, filtering is performed under the extraction condition based on the invitation application record.

(1) The control unit 230 of the management server 200 (an example of a management device) according to the present embodiment includes an extraction unit 239, a user list notification unit 240, an invitation application reception unit 233, an invitation notification unit 236, and an invitation establishment reception. A portion 237 is provided. When the extraction unit 239 acquires a user list of users who have a predetermined relationship (for example, a friend relationship) from the application destination application 20 (an example of the second application), the application unit application among the users included in the user list Users (candidates for invitation to 10 (an example of the first application)) are filtered (extracted) based on a predetermined extraction condition. The user list notification unit 240 sends an invitation candidate user list, which is a user list of users who are candidates for invitation to the application source application 10 extracted by the extraction unit 239, to the user terminal 100 of the invited user (an example of the first user). To send. The invitation application receiving unit 233 receives invitation request information for inviting an invited user (an example of a second user), which is a selected user in the filtered invitation candidate user list, to the application source application 10. Receive from terminal 100. The invitation notification unit 236 transmits invitation notification information based on the invitation application information to the user terminal 100 of the invited user. The invitation establishment receiving unit 237 receives invitation establishment information indicating that the invitation from the application destination application 20 to the application source application 10 has been established from the user terminal 100 of the invited user.

  As a result, the management server 200 extracts from the user list of users who are in a predetermined relationship (for example, friend relationship) with the invited user in the application destination application 20 based on the extraction conditions set in advance, the user invitation candidate user list Can be notified to the user terminal 100. Therefore, it is possible to improve the convenience of the invited user when inviting a user who is in a friend relationship with another application to another application.

  The control unit 230 of the management server 200 (an example of a management device) may not include the invitation establishment receiving unit 237, and includes an extraction unit 239, a user list notification unit 240, an invitation application receiving unit 233, It is good also as a structure provided with the invitation notification part 236 at least. For example, the extraction unit 239 includes a user list of users who are in a predetermined relationship (for example, a friend relationship) from the application destination application 20 (an example of a second application) (an example of predetermined relationship user information indicating a user in a predetermined relationship). Are acquired, the users who are candidates for invitation to the application source application 10 (an example of the first application) among the users included in the user list are filtered (extracted) based on the extraction condition. The user list notification unit 240 (an example of an invitation candidate user notification unit) invites an invitation candidate user list (an example of invitation candidate user information) indicating users who are candidates for invitation to the application source application 10 extracted by the extraction unit 239. It transmits with respect to the user terminal 100 of a user (an example of a 1st user). The invitation application receiving unit 233 receives from the user terminal 100 of the inviting user the invitation application information for inviting the invited user (an example of the second user) among the users shown in the transmitted invitation candidate user list to the application source application 10. receive. The invitation notification unit 236 transmits invitation notification information based on the invitation application information to the user terminal 100 of the invited user.

  Thereby, the management server 200 extracts only the user who becomes the invitation candidate from the user list of the user who is in the predetermined relationship (for example, friend relationship) with the invited user in the application destination application 20, and the user terminal 100 of the invited user. Can be notified. Therefore, it is possible to improve the convenience of the invited user when inviting a user who is in a friend relationship with another application to another application.

(2) For example, the extraction unit 239 of the management server 200 has applied for an invitation from the application destination application 20 (an example of the second application) to the application source application 10 (an example of the first application) as the extraction condition. A user is excluded from the extraction target (first extraction condition). Here, the user who has applied for an invitation from the application destination application 20 to the application source application 10 indicates a user who has already used the application source application 10.

  Thereby, the management server 200 can suppress that the user who has already used the application origin application 10 is published in an invitation candidate user list. That is, the management server 200 can transmit the invitation candidate user list to the user terminal 100 of the inviting user, and can improve the convenience of the inviting user.

(3) The extraction unit 239 performs the invitation application in which an invitation application from the application destination application 20 (an example of the second application) to the application source application 10 (an example of the first application) is established as the extraction condition. The user who has been may be excluded from the extraction target (second extraction condition). Here, the user who has made the invitation application for which the invitation application from the application destination application 20 to the application source application 10 is an example of success indicates a user who has already used the application source application 10. .

Thereby, the management server 200 can suppress that the user who has already used the application origin application 10 is published in an invitation candidate user list. That is, the management server 200 can transmit the invitation candidate user list to the user terminal 100 of the inviting user, and can improve the convenience of the inviting user.
Further, by combining the first extraction condition and the second extraction condition, it is possible to further suppress the user who has already used the application source application 10 from being listed in the invitation candidate user list.

(4) The extraction unit 239 is a user who has applied for an invitation from the application destination application 20 (an example of the second application) to the application source application 10 (an example of the first application) as the extraction condition. A user who is in an invitation application for which the invitation application has not been established may be excluded from extraction targets (third extraction condition).

Accordingly, the management server 200 prevents users who have been invited from other users from being listed in the invitation candidate user list, so that users who may fail the invitation request are listed in the invitation candidate user list. Can be suppressed. That is, the management server 200 can transmit the invitation candidate user list to the user terminal 100 of the inviting user, and can improve the convenience of the inviting user.
Further, by combining the first extraction condition or the second extraction condition and the third extraction condition, a user who can easily establish the invitation application is placed in the invitation candidate user list.

(5) The extraction unit 239 extracts, as the extraction condition, a user who has rejected the invitation application from the application destination application 20 (an example of the second application) to the application source application 10 (an example of the first application). (Example of fourth extraction condition). Here, the user who has rejected the invitation application from the application destination application 20 to the application source application 10 is a user who has rejected the invitation application by the invited user, or a time during which the invitation application is in a predetermined time or more. Indicates a user who left the invitation application until it has passed.

A user who rejects the invitation application from the application destination application 20 to the application source application 10 may fail even if the user applies the invitation application to the application source application 10 again. Thereby, management server 200 can control that a user who may fail an invitation application is published in an invitation candidate user list. That is, the management server 200 can transmit the invitation candidate user list to the user terminal 100 of the inviting user, and can improve the convenience of the inviting user.
Further, by combining the fourth extraction condition with the first extraction condition, the second extraction condition, or the third extraction condition, a user who can easily establish the invitation application is listed in the invitation candidate user list. It becomes like this.

(6) The application management unit 231 of the management server 200 includes information indicating whether or not to permit re-invitation of the user to the application source application 10 (an example of the first application) in the information regarding a plurality of corresponding applications. To do. The extraction unit 239 of the management server 200 refers to the application management unit 231 as the extraction condition, and when the re-invitation of the user to the application source application 10 (an example of the first application) is permitted, the application source application 10 Include users who have rejected invitation requests for

  Thereby, the management server 200 can permit re-invitation in the case of an invitation request to the application source application 10 (first application) for which re-invitation is permitted.

(7) The extraction unit 239 may be a user who rejects the invitation application from the application destination application 20 (an example of the second application) to the application source application 10 (an example of the first application) under the above extraction conditions. In the case of an invitation application from an invitation user (an example of a first user) different from the invitation application, the user may be included in the extraction target.

  Thereby, even if it is the invited user who rejected the invitation application from the same corresponding application in the past, the management server 200 can permit the re-invitation when the invited users are different.

<Modification>
The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to the above-described embodiment, and includes a design and the like within a scope not departing from the gist of the present invention. For example, the functions described in the first, second, and third embodiments can be arbitrarily combined.

(1) In the above embodiment, the communication unit 210 (an example of the transmission / reception unit) of the management server 200 includes an application list (an example of at least part of information managed by the application management unit 231), invitation application information, invitation notification information, In addition, the example in which the invitation establishment information is directly communicated with the user terminal 100 of the invited user or the user terminal 100 of the invited user has been described. Similarly, the terminal communication unit 130 (an example of a transmission / reception unit) of the user terminal 100 directly manages an application list, a user list (an example of invitation candidate user information), invitation application information, invitation notification information, and invitation establishment information. An example of communicating with 200 has been described.

  Here, the communication unit 210 of the management server 200 passes through the application server 300 (an example of a server device) corresponding to the application source application 10 (an example of a first application) or the application destination application 20 (an example of a second application). After establishing the communication session, the user terminal 100 of the invited user or the user terminal 100 of the invited user may be directly communicated. Similarly, the terminal communication unit 130 of the user terminal 100 directly establishes a communication session via the application server 300 corresponding to the application source application 10 or the application destination application 20 (an example of a running application), and then directly You may communicate with the management server 200.

  In addition, when communicating with the management server 200 directly from the user terminal 100, you may make it establish a communication session as needed. In other words, both the case of directly communicating with the management server 200 before establishing the communication session and the case of directly communicating with the management server 200 after establishing the communication session may be included.

  FIG. 22 is a flowchart for explaining the operation of the communication session establishment process. This communication session establishment process (communication session establishment process) is a process that is performed as necessary before communication with the management server 200 after the application source application 10 or the application destination application 20 is activated on the user terminal 100. is there. FIG. 22 illustrates a communication session establishment process performed when communicating directly with the management server 200 from the SDK 11 </ b> A of the application source application 10 installed in the user terminal 100. The communication session establishment process can be performed in the same manner when communicating directly with the management server 200 from the SDK 11B of the application 20 to be applied. Note that it is assumed that a communication session has already been established between the user terminal 100 and the application server 310.

First, the SDK 11A of the user terminal 100 transmits one-time token acquisition request information for requesting acquisition of a one-time token to the application server 310 (step SA10). When the application server 310 acquires the one-time token acquisition request information from the user terminal 100 (SDK 11A), the application server 310 transmits the one-time token generation request information based on the acquired one-time token acquisition request information to the management server 200 (step SC10). ). When acquiring the one-time token generation request information from the application server 310, the management server 200 generates a one-time token and transmits the generated one-time token to the application server 310 (step SE10). When the application server 310 acquires the one-time token from the management server 200, the application server 310 transmits the acquired one-time token to the user terminal 100 (SDK11A) (step SC20). When acquiring the one-time token from the application server 310, the SDK 11A of the user terminal 100 transmits session establishment request information including the acquired one-time token to the management server 200 (step SA20). When the management server 200 acquires the session establishment request information from the user terminal 100 (SDK11A), when the one-time token included in the acquired session establishment request information is correct information (transmitted to the user terminal 100 (SDK11A) If it matches the one-time token), a communication session is established and communication by the mutual invitation system 500 is permitted (step SE20). Thereafter, for example, an invitation process by the mutual invitation system 500 described with reference to FIGS. 9, 10, and 13 is performed. Note that if the one-time token included in the session establishment request information acquired from the user terminal 100 (SDK 11A) is not correct information, the management server 200 generates a communication error and communication by the mutual invitation system 500 is not permitted. In addition, when the management server 200 cannot acquire the session establishment request information from the user terminal 100 (SDK11A), naturally, communication by the mutual invitation system 500 is not permitted.
As described above, after the communication session is established, the communication in the network system 1 including the mutual invitation system 500 can be improved by starting communication by the mutual invitation system 500.

  Note that some of the application list, invitation application information, invitation notification information, and invitation establishment information are not directly communicated with the management server 200 from the user terminal 100, but the application source application 10 (an example of the first application) or You may communicate with the user terminal 100 via the application server 300 (an example of a server apparatus) corresponding to the application destination application 20 (an example of a 2nd application). That is, the communication unit 210 (an example of a transmission / reception unit) of the management server 200 transmits an application list, invitation application information, invitation notification information, or invitation establishment information via the application server 300 corresponding to the application source application 10 or the application destination application 20. The user terminal 100 of the invited user or the user terminal 100 of the invited user may be communicated, or may be directly communicated with the user terminal 100 of the invited user or the user terminal 100 of the invited user. Similarly, the terminal communication unit 130 (an example of a transmission / reception unit) of the user terminal 100 receives the application list, the user list, the invitation application information, the invitation notification information, or the invitation establishment information from the application source application 10 or the application destination application 20 (in operation). May communicate with the management server 200 via the application server 300 corresponding to the application) or directly with the management server 200.

Furthermore, the communication unit 210 (an example of a transmission / reception unit) of the management server 200 sends an application list, invitation application information, invitation notification information, and invitation establishment information to the application source application 10 (an example of the first application) or the application destination application 20 ( You may communicate with the user terminal 100 of an invited user or the user terminal 100 of an invited user via the application server 300 (an example of a server apparatus) corresponding to an example of a 2nd application. Similarly, the terminal communication unit 130 (an example of a transmission / reception unit) of the user terminal 100 receives the application list, the user list, the invitation application information, the invitation notification information, and the invitation establishment information as the application source application 10 or the application destination application 20 (in operation). May communicate with the management server 200 via the application server 300 corresponding to an example of the application.
Thus, even if the user terminal 100 and the management server 200 communicate with each other via the application server 300, the mutual invitation system 500 can perform the same invitation process as in the above embodiment, and obtain the same effect. Can do.

(2) In the said 3rd Embodiment and 4th Embodiment, the application destination application 20 (game B) of the user terminal 100-1 acquires a user list from the application server 320 (game B), and acquired user Although the example which notifies the management server 200 of the filtering request information including the user ID of the user included in the list has been described, the present invention is not limited to this.

  For example, the application destination application 20 (game B) of the user terminal 100-1 notifies the management server 200 of the filtering request information without acquiring the user list from the application server 320 (game B). When the management server 200 receives the filtering request information from the user terminal 100-1 (SDK11B), the management server 200 has the user X who has a predetermined relationship (for example, a friend relationship) with the user X with respect to the application server 320 (game B). Friend list request information for requesting a user list is transmitted to the application server 320 (game B).

  Next, when the application server 320 (game B) acquires the friend list request information from the management server 200, the application server 320 (game B) sends a user list of users who have a predetermined relationship with the user X (for example, friend relationship) to the management server 200. Send. And the management server 200 will perform a filtering process according to a predetermined extraction condition, if a user list is acquired from the application server 320 (game B), and will display the invitation candidate user list after filtering as a filtering result in the user terminal 100-1 (SDK11B). Send to.

  Thus, when the management server 200 acquires a user list from the application server 320 (game B), directly from the application server 320 (game B) or indirectly via the user terminal 100-1 (SDK11B). You may get it.

(3) In the above embodiment, a game is described as an example of a corresponding application corresponding to the mutual invitation system 500. However, the corresponding application is not limited to a game, and may be any application other than a game.

  In the above embodiment, the user who has a predetermined relationship with the invited user in the application destination application 20 has been described as a user who has a friend relationship with the invited user, but this predetermined relationship is not limited to the friend relationship. For example, the predetermined relationship may be a relationship belonging to the same group in the application destination application 20, a company relationship, a relative relationship, or the like, or may simply be a user relationship registered in the application destination application 20.

  Further, the storage unit 220 of the management server 200 may be provided in a server device different from the management server 200. And the control part 230 of the management server 200 communicates via the network NW with respect to the memory | storage part 220 with which the server apparatus different from the management server 200 was used, and each information which each part with which the memory | storage part 220 comprises is memorize | stored. May be managed.

  In addition, the management server 200 and the application server 300 may be integrated as a server device.

  Moreover, although the said embodiment demonstrated the example whose corresponding application corresponding to the mutual invitation system 500 is a native type application, it is not restricted to this. For example, the corresponding application corresponding to the mutual invitation system 500 may be a so-called browser type (Web type) application in which the execution subject of the processing related to the corresponding application is not the user terminal 100 but the application server 300. .

  The program for realizing the functions of the control unit 230 or the SDK 11 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into the computer system and executed, thereby executing the above-described program. You may perform the process of each part. Here, “loading and executing a program recorded on a recording medium into a computer system” includes installing the program in the computer system. The “computer system” here includes an OS and hardware such as peripheral devices. Further, the “computer system” may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, and dedicated line. The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. As described above, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. The recording medium also includes a recording medium provided inside or outside that is accessible from the distribution server in order to distribute the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program that can be executed by the terminal device. That is, the format stored in the distribution server is not limited as long as it can be downloaded from the distribution server and installed in a form that can be executed by the terminal device. Note that the program may be divided into a plurality of parts, downloaded at different timings, and combined in the terminal device, or the distribution server that distributes each of the divided programs may be different. Furthermore, the “computer-readable recording medium” holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when the program is transmitted via a network. Including things. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, what is called a difference file (difference program) may be sufficient.

  In addition, some or all of the functions described above may be realized as an integrated circuit such as an LSI (Large Scale Integration). Each function described above may be individually made into a processor, or a part or all of them may be integrated into a processor. Further, the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. In addition, when an integrated circuit technology that replaces LSI appears due to the advancement of semiconductor technology, an integrated circuit based on the technology may be used.

1 network system, 10 application source application, 11, 11A, 11B SDK, 20 application destination application, 100 user terminal (terminal device), 110 input unit, 120 display unit, 130 terminal communication unit, 140 terminal storage unit (storage unit) , 150 terminal control unit, 161 application list acquisition unit, 162 specific mode activation unit (activation unit), 163 user list acquisition unit, 164 invitation application notification unit, 165 specific mode end unit, 166 inquiry unit, 167 invitation notification acquisition unit, 168 presentation unit, 169 screen transition unit, 170 invitation information management unit, 171 invitation establishment notification unit, 200 management server (management device), 210 communication unit, 220 storage unit, 221 application setting storage unit, 222 invitation application information storage unit, 225 Extraction condition storage unit, 226 Mutual invitation rejection setting 227 Invitation application rejection user setting storage unit 228 Invitation application rejection application setting storage unit 220 Control unit 231 Application management unit 231 Application list notification unit 233 Invitation application reception unit 234 Invitation application management unit 235 Application inquiry unit 236 invitation notifying unit, 237 invitation establishment receiving unit, 238 invitation establishment processing unit, 239 extracting unit, 240 user list notifying unit, 300 application server, 310 application server (game A), 320 application server (game B), 400 application store 500 mutual invitation system

Claims (10)

The first application is transmitted from the terminal device of the first user who has executed the first application and the second application to the terminal device of the user who has a predetermined relationship with the first user in the second application. Provided with a control unit that controls the invitation process for introduction,
The controller is
When the predetermined relationship user information indicating the user having the predetermined relationship is acquired from the second application, out of the users included in the predetermined relationship user information, a user who is an invitation candidate to the first application is selected as an extraction condition. An extraction unit for extracting based on;
An invitation candidate user notification unit for transmitting invitation candidate user information indicating users who are candidates for invitation to the first application extracted by the extraction unit to the terminal device of the first user;
An invitation request receiving unit that receives invitation request information for requesting the second user of the users indicated in the invitation candidate user information to the first application from the terminal device of the first user;
An invitation notification unit that transmits invitation notification information based on the invitation application information to the terminal device of the second user;
With
The management apparatus characterized in that identification information for identifying a user in the first application and identification information for identifying a user in the second application are independently managed for each application. The extraction unit includes:
The management apparatus according to claim 1, wherein a user who has applied for an invitation from the second application to the first application is excluded from the extraction target as the extraction condition. The extraction unit includes:
3. The user who has made an invitation application for which the invitation application from the second application to the first application has been established is excluded from the extraction target as the extraction condition. Management device. The extraction unit includes:
As the extraction condition, a user who has been invited from the second application to the first application and whose invitation application is not established is excluded from the extraction target. The management device according to any one of claims 1 to 3. The extraction unit includes:
5. The management apparatus according to claim 1, wherein, as the extraction condition, a user who has rejected the invitation application from the second application to the first application is excluded from the extraction target. . The extraction unit includes:
The management apparatus according to any one of claims 1 to 5, wherein, as the extraction condition, a user who is set to reject an invitation request from the first user is excluded from extraction targets. The extraction unit includes:
The management apparatus according to any one of claims 1 to 6, wherein, as the extraction condition, a user set to reject an invitation application to the first application is excluded from an extraction target. An invitation to receive invitation establishment information indicating that an invitation from the second application corresponding to the invitation notification information to the first application has been established from the terminal device of the second user or the server device corresponding to the first application. Accepted receipt department,
The management apparatus according to any one of claims 1 to 7, further comprising: A management device management method comprising:
The first application is transmitted from the terminal device of the first user who has executed the first application and the second application to the terminal device of the user who has a predetermined relationship with the first user in the second application. A control step for controlling an invitation process for introduction;
The control step includes
When the predetermined relationship user information indicating the user having the predetermined relationship is acquired from the second application, out of the users included in the predetermined relationship user information, a user who is an invitation candidate to the first application is selected as an extraction condition. Extracting based on;
Transmitting invitation candidate user information indicating users who are candidates for invitation to the extracted first application to the terminal device of the first user;
Receiving invitation request information for inviting a second user of the users indicated in the invitation candidate user information to the first application from the terminal device of the first user;
Transmitting invitation notification information based on the invitation application information to the terminal device of the second user;
Including
The management method characterized in that identification information for identifying a user in the first application and identification information for identifying a user in the second application are managed uniquely for each application. The identification information for identifying the user in the first application and the identification information for identifying the user in the second application are managed independently for each application, and the first application and the second application have been executed. From a certain first user's terminal device to a computer that controls the invitation process for introducing the first application to the user's terminal device having a predetermined relationship with the first user in the second application,
When the predetermined relationship user information indicating the user having the predetermined relationship is acquired from the second application, out of the users included in the predetermined relationship user information, a user who is an invitation candidate to the first application is selected as an extraction condition. Extracting based on;
Transmitting invitation candidate user information indicating users who are candidates for invitation to the extracted first application to the terminal device of the first user;
Receiving invitation request information for inviting a second user of the users indicated in the invitation candidate user information to the first application from the terminal device of the first user;
Transmitting invitation notification information based on the invitation application information to the terminal device of the second user;
A program for running

Images